BWP configuration for UEs with different capabilities

Abstract

We provide equipment for wireless communications based on BWP configurations for UEs with different capabilities. [Solution] A user device (UE) having a first capability associated with a maximum UE bandwidth lower than the second capability performs at least part of the initial access based on an initial downlink bandwidth portion (BWP) shared between the UE having the first capability and the UE having the second capability. After the initial access, the UE switches to an active downlink BWP and an active uplink BWP, which are dedicated to the UE having the first capability, in order to perform random access, paging, system acquisition, measurement, and data communication procedures.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims the benefit and priority of U.S. Provisional Application No. 63 / 234,674, entitled "BWP Configurations for UEs Having Different Capabilities", filed on Aug. 18, 2021, and U.S. Non - provisional Application No. 17 / 871,879, entitled "BWP CONFIGURATIONS FOR UES HAVING DIFFERENT CAPABILITIES", filed on Jul. 22, 2022, which are hereby incorporated by reference in their entirety.

[0002] This disclosure generally relates to communication systems, and more particularly to wireless communication based on bandwidth parts (BWPs).

Background Art

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunication services, including telephone, video, data, messaging, and broadcast. Typical wireless communication systems can utilize multiple access technologies that enable communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] These multiple access technologies are being adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and global levels. An exemplary telecommunications standard is 5G New Radio (NR). 5G NR is part of the ongoing evolution of mobile broadband announced by the Third Generation Partnership Project (3GPP®) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things, IoT), and other requirements. 5G NR includes services related to enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements are needed in 5G NR technology. These improvements may also be applicable to other multiple access technologies and the telecommunications standards that utilize them. [Overview of the project]

[0005] The following provides a simplified overview of one or more embodiments to provide a basic understanding of those embodiments. This overview is not a comprehensive overview of all intended embodiments. This overview does not identify the main or important elements of all embodiments, nor does it describe the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments in a simplified form as a prelude to the more detailed explanations that will be presented later.

[0006] In addition to higher-capacity devices, wireless communications may support lower-capacity devices. In some examples, a lower-capacity UE may have a reduced transmit or receive bandwidth compared to other UEs. The embodiments presented herein provide configurations and signaling support for lower-capacity UEs that enable joint optimization of DL / UL BWP configurations, coexistence of different UE capacities, power savings for lower-capacity UEs, mitigation of resource fragmentation on DL / UL, and / or reduction of signaling overhead. [Means for solving the problem]

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

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

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

[0010] To achieve the above-mentioned and related objectives, one or more embodiments shall have features that are fully described below and, in particular, indicated in the claims. The following description and accompanying drawings shall detail some exemplary features of one or more embodiments. However, these features shall represent only a few of the various ways in which the principles of various embodiments may be employed, and this description is intended to include all such embodiments and their equivalents. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows examples of wireless communication systems and access networks according to various embodiments presented herein. [Figure 2A] This figure shows an example of the first frame according to various aspects of the present disclosure. [Figure 2B] This figure shows an example of a DL channel within a subframe according to various aspects of this disclosure. [Figure 2C] This figure shows an example of a second frame according to various aspects of the present disclosure. [Figure 2D] This figure shows an example of a UL channel within a subframe according to various aspects of this disclosure. [Figure 3] This figure shows examples of base stations and user equipment (UEs) in an access network according to various embodiments presented herein. [Figure 4]This is an exemplary resource diagram showing exemplary bandwidth portions (BWPs) within a carrier bandwidth according to various embodiments presented herein. [Figure 5A] Examples of downlink (DL)BWP and uplink (UL)BWP in carrier bandwidth according to various embodiments presented herein are shown. [Figure 5B] This specification shows time diagrams illustrating the guard periods for switching between UL BWP and DL BWP according to various embodiments presented herein. [Figure 6] This specification presents exemplary embodiments of BWPs for reduction capability UEs, including shared initial DL BWPs, according to various embodiments. [Figure 7] This specification presents exemplary embodiments of BWPs for reduction capability UEs, including shared initial DL BWPs, according to various embodiments. [Figure 8] This specification presents exemplary embodiments of BWPs for reduction capability UEs, including shared initial DL BWPs, according to various embodiments. [Figure 9] This specification presents an exemplary communication flow between a UE and a base station, including the use of a shared initial DL BWP and a dedicated active DL BWP for a reduction capability UE, in various embodiments described herein. [Figure 10] This specification presents exemplary embodiments of BWPs for reduction capability UE, including shared initial DL BWPs and dedicated initial DL BWPs, according to various embodiments presented herein. [Figure 11] This specification presents exemplary communication flows between a UE and a base station, including the use of shared initial DL BWP and dedicated initial DL BWP for a reduction capability UE, in various embodiments described herein. [Figure 12] This specification presents exemplary embodiments of BWPs for reduction capability UE, including shared initial DL BWPs and dedicated initial DL BWPs, according to various embodiments presented herein. [Figure 13] This is a flowchart illustrating various methods of wireless communication in a UE as presented herein. [Figure 14] A flowchart of a method of wireless communication in a UE according to various aspects presented in this specification. [Figure 15] A diagram illustrating an example of a hardware implementation form for an exemplary apparatus according to various aspects presented in this specification. [Figure 16] A flowchart of a method of wireless communication in a network entity according to various aspects presented in this specification. [Figure 17] A flowchart of a method of wireless communication in a network entity according to various aspects presented in this specification. [Figure 18] A diagram illustrating an example of a hardware implementation form for an exemplary network entity according to various aspects presented in this specification. [Figure 19] [[ID=?]]A diagram showing an example of a non - aggregated base station architecture according to various aspects presented in this specification.

Embodiments for Carrying Out the Invention

[0012] Note: There seems to be a problem with ID=16 in the original text. I've made a best - guess translation based on the context. It might be better if the original text for that ID is corrected.In addition to higher-capability devices, wireless communication can support reduced-capability devices. In some examples, a reduced-capability UE may have a reduced transmit bandwidth or receive bandwidth compared to other UEs. The aspects presented herein provide configuration and signaling support for reduced-capability UEs that enable joint optimization of DL / UL BWP configurations, coexistence of different UE capabilities, power savings for reduced-capability UEs, mitigation of resource fragmentation on DL / UL, and / or reduction of signaling overhead. In some aspects, UEs having different levels of capabilities, such as reduced-capability UEs and non-reduced (or higher) -capability UEs, may share an initial DL BWP and CORESET 0 for initial access. The UE may, for example, monitor the resources of CORESET 0 to receive system information that enables the UE to perform initial access. In some aspects, a shared CORESET 0, for example, and a shared system information block (SIB) may carry information for UEs having a larger bandwidth capability and UEs having a reduced bandwidth capability. In some aspects, a separate initial BWP, for example, a dedicated initial downlink BWP and / or a dedicated initial uplink BWP, may be provided to UEs with reduced bandwidth. In some aspects, a reduced-capability UE may use a dedicated initial BWP to transmit a random access message, such as a random access preamble. The aspects presented herein may provide an initial access and subsequent BWP configuration that supports a reduced bandwidth according to a reduced-capability UE while maintaining flexibility in configuring the bandwidth for higher-capability UEs.

[0013] The detailed descriptions provided below in relation to the drawings describe various configurations and are not intended to represent only the configurations in which the concepts described herein can be put into practice. The detailed descriptions include specific details for the purpose of giving a complete understanding of the various concepts. However, these concepts can be put into practice without these specific details. In some cases, well-known structures and components are shown in the form of block diagrams to avoid obscuring such concepts.

[0014] Several embodiments of telecommunications systems are presented with reference to various devices and methods. These devices and methods are described in the following detailed description and are shown in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0015] For example, an element, any part of an element, or any combination of elements may be implemented as a “processing system” comprising one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on a chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software shall be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., or any combination thereof, whether they are called software, firmware, middleware, microcode, hardware description language, or otherwise.

[0016] Accordingly, in one or more exemplary embodiments, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable medium includes computer storage medium. The storage medium may be any available medium accessible by a computer. Such computer-readable medium may include, but not limited to, random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of types of computer-readable medium, or any other medium that can be used to store computer executable code in the form of instructions or data structures accessible by a computer.

[0017] While embodiments, implementations, and / or use cases are described in this application by example to several embodiments, additional or different embodiments, implementations, and / or use cases may arise in many different configurations and scenarios. The embodiments, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging configurations. For example, implementations and / or applications may arise from integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI)-enabled devices, etc.). Some examples may or may not specifically target use cases or applications, but may result in a wide range of applicability for the embodiments described. Embodiments, implementations, and / or use cases can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more embodiments of the technology herein. In some practical settings, devices incorporating the embodiments and features described may also include additional components and features for implementations and practices of the claims and embodiments described. For example, wireless signal transmission and reception necessarily involve several components (hardware components including, for example, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) for analog and digital purposes. The techniques described herein can be put into practice in a wide variety of devices, chip-level components, systems, distributed configurations, aggregated or unaggregated components, end-user devices, etc., of various sizes, shapes, and structures.

[0018] Figure 1 shows an example of a wireless communication system and access network 100. The wireless communication system (also called a wireless wide area network (WWAN)) includes a base station 102, an UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include macrocells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macrocells include base stations. Small cells include femtocells, picocells, and microcells.

[0019] In some embodiments, UE 104 may have a first capability associated with a maximum UE bandwidth lower than a second capability. In some embodiments, the UE may be a reduced capability UE. UE 104 may include a BWP component 198, which is configured to perform at least part of the initial access with base station 102 or 180 based on an initial downlink 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 an active uplink BWP dedicated to the UE having the first capability.

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

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

[0022] Base station 102 can communicate wirelessly with UE 104. Each base station 102 may provide communication coverage to its respective geographical coverage area 110. There may be overlapping geographical coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network containing both small cells and macro cells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node B (eNB) (HeNB) which can serve a limited group known as a closed subscriber group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also called reverse link) transmissions from UE 104 to base station 102, and / or downlink (DL) (also called forward link) transmissions from base station 102 to UE 104. The communication link 120 may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be through one or more carriers. The base station 102 / UE 104 may use a spectrum with bandwidths of up to Y MHz per carrier (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) allocated in carrier aggregation up to a total of Yx MHz (x constituent carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. The carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL than to UL). The constituent carriers may include primary constituent carriers and one or more secondary constituent carriers. Primary constituent carriers may be called primary cells (PCells), and secondary constituent carriers may be called secondary cells (SCells).

[0023] Some UE104s 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 sidelink channels, such as the physical sidelink broadcast channel (PSBCH), physical sidelink discovery channel (PSDCH), physical sidelink shared channel (PSSCH), and physical sidelink control channel (PSCCH). D2D communication may be via various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[0025] Small cell 102' may operate in licensed and / or unlicensed frequency spectra. When operating in unlicensed frequency spectra, small cell 102' may employ NR and use the same unlicensed frequency spectrum (e.g., 5 GHz) used by Wi-Fi AP150. Small cell 102' utilizing NR in unlicensed frequency spectra may enhance coverage to the access network and / or increase the capacity of the access network.

[0026] The electromagnetic spectrum is often subdivided into various classes, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands are identified as frequency range designations FR1 (410 MHz to 7.125 GHz) and FR2 (24.25 GHz to 52.6 GHz). Although a portion of FR1 is above 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and papers. A similar nomenclature issue sometimes arises with FR2, which is often referred to (interchangeably) as the "millimeter wave" band in documents and papers, even though it is different from the extremely high frequency (EHF) band (30 GHz to 300 GHz) which is identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0027] The frequencies between FR1 and FR2 are often referred to as intermediate band frequencies. Recent 5G NR research has identified the operating band for these intermediate band frequencies as frequency range designation FR3 (7.125 GHz to 24.25 GHz). The frequency bands falling within FR3 may inherit the FR1 and / or FR2 characteristics, and thus, in effect, the features of FR1 and / or FR2 may be extended to the intermediate band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR4a or FR4-1 (52.6 GHz to 71 GHz), FR4 (52.6 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

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

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

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

[0031] EPC160 may include a Mobility Management Entity (MME) 162, another MME 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. MME 162 is a control node that handles signaling between UE 104 and EPC160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are forwarded through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and BM-SC 170 are connected to the IP service 176. IP service 176 may include the Internet, intranet, IP Multimedia Subsystem (IMS), PS streaming service, and / or other IP services. BM-SC170 may provide functionality for MBMS user service provisioning and distribution. BM-SC170 may act as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions.The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and collecting eMBMS-related billing information.

[0032] The core network 190 may include an Access and Mobility Management Function (AMF) 192, another AMF 193, a Session Management Function (SMF) 194, and a User Plane Function (UPF) 195. AMF 192 may communicate with Unified Data Management (UDM) 196. AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Generally, AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are forwarded through UPF 195. UPF 195 provides IP address allocation for the UE and other functions. UPF 195 is connected to IP service 197. IP services 197 may include the Internet, intranets, IP multimedia subsystems (IMS), packet switching (PS), packet switching streaming (PSS) services, and / or other IP services.

[0033] A base station may include and / or be referred to as a gNB, node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), transmit reception point (TRP), or any other preferred term. Base station 102 provides UE 104 with an access point to EPC 160 or core network 190. Examples of UE 104 include cellular phones, smartphones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similar functional devices. Some UE104s are sometimes referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, cardiac monitors, etc.). UE104s may also be called stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, handsets, user agents, mobile clients, clients, or any other suitable term. In some scenarios, the term UE may also apply to one or more companion devices in a device constellation configuration, for example. One or more of these devices may access the network collectively and / or individually.

[0034] The deployment of communication systems such as 5G New Radio (NR) systems can be configured in multiple ways using various components or parts. In a 5G NR system or network, network equipment such as network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements, or base stations (BS), or one or more units (or components) that perform base station functionality, can be implemented in an aggregated or unaggregated architecture. For example, a BS (such as a Node B (NB), an advanced NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit / receive point (TRP), or a cell) can be implemented as an aggregated base station (also known as a standalone BS or monolithic BS) or an unaggregated base station.

[0035] An aggregated base station can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A non-aggregated base station can be configured to utilize a protocol stack that is physically or logically distributed among 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 embodiments, a CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, geographically or virtually distributed across one or more other RAN nodes. A DU can be implemented to communicate with one or more RUs. Each of a CU, DU, and RU can also be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

[0037] Figure 19 shows an exemplary unaggregated base station 1900 architecture. The unaggregated base station 1900 architecture may include one or more central units (CUs) 1910, which may communicate directly with the core network 1920 via backhaul links, or indirectly with the core network 1920 via one or more unaggregated base station units (such as a quasi-real-time (quasi-RT) RAN Intelligent Controller (RIC) 1925 via an E2 link, or a non-real-time (non-RT) RIC 1915 associated with a Service Management and Orchestration (SMO) framework 1905, or both). The CUs 1910 may communicate with one or more distributed units (DUs) 1930 via their respective midhaul links, such as an F1 interface. The DUs 1930 may communicate with one or more radio units (RUs) 1940 via their respective fronthaul links. An RU1940 can communicate with each UE104 via one or more radio frequency (RF) access links. In some implementations, the UE104 may be serviced simultaneously by multiple RU1940s.

[0038] Each of the units, namely CU1910, DU1930, RU1940, and the quasi-RT RIC1925, non-RT RIC1915, and SMO framework 1905, may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) over a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interface of a unit, may be configured to communicate with one or more other units over a transmission medium. For example, a unit may include a wired interface configured to receive or transmit signals over a wired transmission medium with one or more other units. Additionally, a unit 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, or both, signals over a wireless transmission medium with one or more other units.

[0039] In some embodiments, the CU1910 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 using an interface configured to communicate signals with other control functions hosted by the CU1910. The CU1910 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some implementations, the CU1910 may be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units may communicate bidirectionally with the CU-CP units via an interface such as the E1 interface. The CU1910 can be implemented to communicate with the DU1930 as needed for network control and signaling.

[0040] The DU1930 may correspond to a logic unit containing one or more base station functions for controlling the operation of one or more RU1940s. In some embodiments, the DU1930 may host one or more of the following, at least in part, a functional decomposition, such as that defined by the Third Generation Partnership Project (3GPP®): a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) coding and decoding, scrambling, modulation and demodulation). In some embodiments, the DU1930 may further host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU1930, or with control functions hosted by the CU1910.

[0041] Lower-layer functionality can be implemented by one or more RU1940s. In some deployments, the RU1940 controlled by the DU1930 may correspond to logical nodes hosting RF processing functions, or low-PHY layer functions (such as fast Fourier transform (FFT), inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering), or both, at least partially based on functional partitioning such as lower-layer functional partitioning. In such architectures, the RU1940 can be implemented to handle over-the-air (OTA) communication with one or more UE104s. In some implementations, the real-time and non-real-time modes of control plane and user plane communication with the RU1940 can be controlled by the corresponding DU1930. In some scenarios, this configuration can enable the DU1930 and CU1910 to be implemented in cloud-based RAN architectures such as vRAN architectures.

[0042] The SMO framework 1905 can be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 1905 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operational and maintenance interfaces (such as the O1 interface). For virtualized network elements, the SMO framework 1905 can be configured to interact with cloud computing platforms (such as Open Cloud (O-Cloud) 1990) and perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces (such as the O2 interface). Such virtualized network elements may include, but are not limited to, CU1910, DU1930, RU1940, and Near-RT RIC1925. In some implementations, the SMO framework 1905 can communicate with 4G RAN hardware embodiments such as Open eNB (O-eNB) 1911 via the O1 interface. Additionally, in some implementations, the SMO framework 1905 can communicate directly with one or more RU1940s via the O1 interface. The SMO framework 1905 may also include non-RT RIC1915s configured to support the functionality of the SMO framework 1905.

[0043] Non-RT RIC1915 may be configured to include logical 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 for applications / features in quasi-RT RIC1925. Non-RT RIC1915 may be coupled to or communicate with quasi-RT RIC1925 (e.g., via the A1 interface). Quasi-RT RIC1925 may be configured to include logical functions that enable quasi-real-time control and optimization of RAN elements and resources via data acquisition and actions via an interface connecting one or more CU1910s, one or more DU1930s, or both, and the O-eNB to quasi-RT RIC1925 (e.g., via the E2 interface).

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

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

[0046] Figures 2A to 2D show frame structures, and aspects of this disclosure may be applicable to other wireless communication techniques that may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 subframes (1 ms) of equal size. Each subframe may contain one or more time slots. Subframes may also contain minislots that may contain 7, 4, or 2 symbols. Each slot may contain 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. With a normal CP, each slot may contain 14 symbols, and with an extended CP, each slot may contain 12 symbols. Symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) symbols (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 called 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 numerology. Numerology defines the subcarrier spacing (SCS), which effectively defines a symbol length / duration equal to 1 / SCS.

[0047] [Table 1]

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

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

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

[0051] Figure 2B shows an example of various DL channels within a frame subframe. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., one, two, four, eight, or sixteen CCEs), each CCE containing six RE groups (REGs), each REG containing twelve consecutive REs within the OFDM symbols of the RB. A PDCCH within a single BWP may be called 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 PDCCH monitoring opportunities on the CORESET, where PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be located within symbol 2 of a specific subframe of the frame. The PSS is used by UE104 to determine the subframe / symbol timing and physical layer identification information. The secondary synchronization signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by UE to determine the physical layer cell identification information group number and wireless frame timing. Based on the physical layer identification information and physical layer cell identification information group number, UE can determine the physical cell identifier (PCI). Based on the PCI, UE can determine the location of the DM-RS.A physical broadcast channel (PBCH) carrying a master information block (MIB) can be logically grouped with PSS and SSS to form a synchronization signal (SS) / PBCH block (also called an SS block (SSB)). The MIB provides the number of RBs and the system frame number (SFN) within the system bandwidth. A physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs), and paging messages.

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

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

[0054] Figure 3 is a block diagram showing base station 310 communicating with UE350 in an access network. In DL, IP packets can be provided to controller / processor 375. Controller / processor 375 implements Layer 3 and Layer 2 functionality. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptive Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Medium Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection correction, and RRC connection release), mobility between radio access technologies (RATs), and broadcasting of measurement configurations for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with forwarding upper layer packet data units (PDUs), error correction by ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto transport blocks (TBs), demultiplexing MAC SDUs from TBs, scheduling information reporting, error correction by HARQ, priority processing, and logical channel prioritization.

[0055] The transmit (TX) processor 316 and the receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols can then be divided into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then synthesized together using an inverse fast Fourier transform (IFFT) to generate a physical channel that carries a time-domain OFDM symbol stream. The OFDM streams are spatially precoded to generate multiple spatial streams. Channel estimates from channel estimator 374 may be used to determine the coding and modulation scheme, and for spatial processing. Channel estimates may be derived from a reference signal and / or channel state feedback transmitted by UE350. Each spatial stream may then be fed to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can modulate a radio frequency (RF) carrier on its respective spatial stream for transmission.

[0056] In UE350, each receiver 354Rx receives signals via its respective antenna 352. Each receiver 354Rx reconstructs the information modulated on the RF carrier and provides this information to the receiver (RX) processor 356. The TX processor 368 and RX processor 356 implement Layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to reconstruct any spatial stream destined for UE350. Multiple spatial streams, if destined for UE350, can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then uses a Fast Fourier Transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal contains a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are reconstructed and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions may be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to reconstruct the data and control signals initially transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements Layer 3 and Layer 2 functionality.

[0057] The controller / processor 359 can be associated with memory 360, which stores program code and data. Memory 360 is sometimes referred to as computer-readable media. In UL, the controller / processor 359 performs demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to reconstruct IP packets. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operation.

[0058] Similar to the functionality described in relation to DL transmission by 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 (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper layer PDU transfer, error correction by ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing MAC SDUs onto TB, demultiplexing MAC SDUs from TB, scheduling information reporting, error correction by HARQ, priority processing, and logical channel prioritization.

[0059] The channel estimate derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx can modulate the RF carrier in its respective spatial stream for transmission.

[0060] UL transmission is processed at base station 310 in a manner similar to that described in relation to the receiver function in UE350. Each receiver 318Rx receives the signal via its respective antenna 320. Each receiver 318Rx reconstructs the information modulated on the RF carrier and provides this information to RX processor 370.

[0061] The controller / processor 375 can be associated with memory 376, which stores program code and data. Memory 376 is sometimes referred to as computer-readable media. In UL, the controller / processor 375 performs demultiplexing between transport and logical channels, packet reassembly, decoding, header decompression, and control signal processing to reconstruct IP packets. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operation.

[0062] At least one of the TX processor 368, RX processor 356, and controller / processor 359 may be configured to implement an embodiment related to the BWP component 198 in Figure 1.

[0063] At least one of the TX processor 316, RX processor 370, and controller / processor 375 may be configured to implement an embodiment related to the BWP component 199 in Figure 1.

[0064] In addition to higher-capacity devices, wireless communications can support lower-capacity devices. Examples of higher-capacity devices include premium smartphones, vehicle-to-everything (V2X) devices, URLLC devices, and eMBB devices. Lower-capacity devices may include lower-capacity and mid-capacity devices and use cases. Among other examples, lower-capacity devices may include wearables, industrial wireless sensor networks (IWSNs), surveillance cameras, and low-end smartphones. Communication systems, such as NR communication systems, can support both higher-capacity and lower-capacity devices. Lower-capacity devices are sometimes referred to as RedCap devices, NR light devices, low-tier devices, or lower-tier devices. Lower-capacity UEs can communicate based on various types of wireless communications. For example, smart wearables may transmit or receive communications based on low-power wide-area (LPWA) / mMTC, relaxed IoT devices may transmit or receive communications based on URLLC, and sensors / cameras may transmit or receive communications based on eMBB, and so on.

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

[0066] As another example, a reduction capability UE may have uplink transmit power at least 10 dB lower than a higher capability UE. Further as an example, a reduction capability UE may have a reduced number of receiving antennas compared to other UEs. For instance, a reduction capability UE may have only a single receiving antenna and experience a lower equivalent signal-to-noise ratio (SNR) compared to a higher capability UE that may have multiple antennas. A reduction capability UE may also have reduced computational complexity compared to other UEs.

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

[0068] The carrier bandwidth may, for example, extend to a contiguous set of PRBs from a common resource block for a given numerology on a given carrier. A base station may configure one or more bandwidth parts (BWPs) having a bandwidth span smaller than the carrier bandwidth. One or more of the BWPs may be configured for downlink communication and are sometimes called downlink (DL) BWPs. Figure 4 shows resource diagram 400, which illustrates multiple BWPs (e.g., BWP1, BWP2, and BWP3) configured within the frequency span of the carrier bandwidth. Only one DL BWP may be active at a time, and the UE may not expect to receive PDSCH, PDCCH, CSI-RS, or TRS outside the active BWP without a measurement gap or BWP switching gap. Each DL BWP may contain at least one control resource set (CORESET). In Figure 4, a BWP may be a DL BWP and is shown as having a CORESET within it. In other examples, a BWP may be a UL BWP and may not contain a CORESET configuration. One or more BWPs may be configured for uplink communication and are sometimes called uplink (UL) BWPs. Only one UL BWP may be active for a UE at a time, and the UE may not transmit PUSCH or PUCCH outside of the active BWP. The use of BWPs may reduce bandwidth, which can help the UE conserve battery power, and is monitored and / or used for transmission by the UE.

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

[0070] Figure 5A shows an example 500 in which a DL BWP 504 within the TDD carrier bandwidth 502 configured for a reduction capability UE is not matched with an UL BWP 506 for a reduction capability UE. If the DL BWP and UL BWP are not matched, for example, at the center frequency, a guard time period may be provided between the downlink resource and the uplink resource to allow the UE to switch between the BWPs. For example, the UE can switch between downlink reception on DL BWP 504 and uplink transmission on UL BWP 506 at 508. Similarly, the UE can switch between uplink transmission on UL BWP 506 and downlink reception on DL BWP 504 at 510.

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

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

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

[0074] The UE continues to measure the serving cell's SSS or TRS after initial access for synchronization purposes, for example, to maintain synchronization with the serving cell. To support cell-level mobility, the UE may measure the serving cell's SSB and one or more neighboring cells. As shown in Figure 6, if a reduction capability UE operates within an active DL BWP in the SSB, and the SSB resource is in the initial DL BWP 604 rather than in the active DL BWPs 606 and 608, for example, if the SSB is not transmitted within the active downlink BWP as shown in Figure 6, the UE may be configured with an in-frequency L3 measurement gap to allow 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. The network may configure a periodic measurement gap for the UE, for example, via RRC signaling. When a measurement gap begins, the reduction capability UE may suspend downlink control and / or data reception in the active DL BWP 606 and switch to another BWP configured with DL RS, such as the initial DL BWP. Periodic or semi-static TRS / CSI-RS / PRS may be transmitted within the active DL BWP 606 and may be used as a QCL source for time / frequency / frequency tracking, L1 measurement for link maintenance, or for paging, monitoring and reception of wake-up signals (WUS). In some embodiments, 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, load imbalance may occur across the frequency of the carrier bandwidth 602, for example, due to a measurement gap.

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

[0076] In some embodiments, BWPs such as DL BWP and / or UL BWP may be configured separately for mitigation capability UEs. BWPs may be configured separately for mitigation capability UEs in different connection states, such that different BWP configurations may exist for UEs in the RRC idle state, RRC inactive state, and / or RRC connected state.

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

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

[0079] After initial access, a reduction capability UE may operate in an active DL BWP714 and active UL BWP712 specifically for reduction capability UEs, rather than for higher capability UEs. Active DL BWP714 and active UL BWP712 are sometimes referred to as being dedicated to reduction capability UEs. An active DL BWP714 for a reduction capability UE may include configurations for periodic or semi-static TRS and / or periodic CSI-RS and / or PRS. An active DL BWP714 for a reduction capability UE may include configurations for a common search space (CSS) for the UE to monitor and receive WUS, paging, and system information updates from the network, among other downlink signals. If SSB is not transmitted in the active DL BWP714, an L3 in-frequency measurement gap may be provided to allow the UE to switch to measuring SSB in the initial DL BWP704, as described in relation to Figure 6. As shown in Figure 7, the UE may receive an RRC message in the active DL BWP714, which provides system information (SI) updates to lower-capacity UEs.

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

[0081] Figure 8 shows an example 800 similar to Figure 7, in which an active DL BWP814 dedicated to reduction capability UEs may have a different center frequency than an active UL BWP812 dedicated to reduction capability UEs. Additionally or alternatively, a shared initial DL BWP804 for initial access, which may be common to both reduction capability UEs and higher capability UEs, may have a different center frequency than a shared initial UL BWP806 for initial access, which may be common to both reduction capability UEs and higher capability UEs.

[0082] Figure 9 shows an exemplary communication flow 900 between a reduced-capability UE 902 and a base station 904, based on initial DL BWP and UL BWP shared between a reduced-capability UE and a higher-capability UE, as described, for example, in relation to Figures 7 and / or 8. The reduced capability of UE 902 may include a reduced operating bandwidth, or a lower maximum UE bandwidth that is smaller than that of a higher-capability UE. UE 902 may operate on a TDD basis, where the UE monitors downlink communication or transmits uplink communication, and does not transmit and receive at overlapping times. At 906, UE 902 may receive system information 906. The system information may be for carrier bandwidth, for example, for wireless communication with base station 904 in 802 in Figure 8. The system information may indicate BWP as a subset of the frequency resources of carrier bandwidth for the UE to perform initial access. The system information may be specific to the reduced-capability UE, for example, including information applicable to the reduced-capability UE but not to the higher-capability UE. UE902 may receive system information 906 in a separate SIB for reduced capability UEs, distinct from the SIB that has system information applicable to higher capability UEs. UE902 may also receive system information 906 in an SIB that carries 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 (e.g., in initial DL BWP704 or 804) that is shared by reduced capability UEs and higher capability UEs.

[0083] In 908, UE902 may perform initial access procedures, such as the RACH procedure, in the initial DL BWP (e.g., shared initial DL BWP704 or 804) and initial UL BWP (e.g., shared initial UL BWP706 or 806) which are common to reduced capability UEs and higher capability UEs. As part of the initial access, UE902 may send and receive random access messages 910 with the base station 904. For example, in the shared initial DL BWP and shared initial UL BWP, as described in relation to Figure 7 or Figure 8, UE may send random access Msg1 with a preamble to base station 904, receive Msg2 from the base station, send Msg3 to the base station, and / or receive Msg4 from the base station. In 910, UE902 may send random access messages such as Msg1 during random access occasions based on the SSB-to-RO mapping for reduced capability UEs. The mapping from SSB to RO may be based on the CD-SSB received in the shared initial DL BWP. The mapping from SSB to RO and the mapping from SSB to preamble may be based on mapping patterns configured separately for the reduction capability UE. The separate configurations may be received in system information 906 in the shared initial DL BWP. Similar to UE 902, the base station may, in 912, perform an initial access procedure with the UE based on the shared initial DL BWP and shared initial UL BWP which are common to both the reduction capability UE and the higher capability UE.

[0084] UE may receive instructions or configurations for active DL BWPs and active UL BWPs that are dedicated to reduced capability UEs rather than higher capability UEs. Active DL BWPs and active UL BWPs may correspond to 712 and 714, or 812 and 814, in Figure 7 or Figure 8. UE 902 may receive configurations for dedicated active DL BWPs and dedicated active UL BWPs in the system information for reduced capability UEs, for example in 906 of the shared initial DL BWP. System information 906 may be broadcast for reception by any reduced capability UE. UE 902 may receive configurations for dedicated active DL BWPs and active UL BWPs in RRC signaling from base station 904, for example in 914. RRC signaling may be directed to UE 902 in unicast signaling from base station 904. In some embodiments, UE902 may determine or identify dedicated active DL BWP and active UL BWP configurations based on rules, lookup tables, or previously known information without explicit signaling of configuration from base station 904. The use of lookup tables or rules may reduce signaling overhead while enabling a reduced-capability UE to communicate based on active DL / UL BWP supported by the UE's bandwidth capability.

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

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

[0087] As shown in 922, UE902 may monitor and / or receive PDSCH, PDCCH, TRS, CSI-RS, PRS, or non-CD SSB in an active DL BWP dedicated to a reduction capability UE. In 926, UE902 may transmit PUSCH, PUCCH, and / or SRS in an active UL BWP for a reduction capability UE.

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

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

[0090] After initial access, the reduction capability UE may operate in the active DL BWP1014 and active UL BWP1012 for the reduction capability UE, rather than for the higher capability UE. Similar to the active DL BWP714 in Figure 7, the BWP1014 for the reduction capability UE may include configurations for periodic or semi-static TRS and / or periodic CSI-RS. The active DL BWP1014 for the reduction capability UE may include configurations for CSS, among other downlink signals, for the UE to monitor and receive WUS, paging, or system information updates from the network. If SSB is not transmitted in the active DL BWP1014, the L3 in-frequency measurement gap allows the UE to switch to measuring SSB (e.g., 1010) in the initial DL BWP1004, as described in relation to Figure 6, if SSB is not transmitted in the active downlink BWP as shown in Figure 10. As shown in Figure 10, the UE may receive an RRC message in the active DL BWP1014, which provides SI updates to lower-capacity UEs.

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

[0092] The shared initial DL BWP1004 may carry some information that enables the reduced-capacity UE to initiate access to the network and provides information about dedicated initial BWP resources for the reduced-capacity UE. For example, a dedicated initial DL BWP for a reduced-capacity UE, rather than a higher-capacity UE, may carry system information that is specific to the reduced-capacity UE and may differ from the system information in the DL BWP1004 for the higher-capacity UE.

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

[0094] UE1102 may receive system information 1105, for example, in a shared initial DL BWP. System information 1105 may be for carrier bandwidth, for example, for wireless communication with base station 1104 in 1002 in Figure 10. System information 1105 may indicate BWP as a subset of frequency resources of carrier bandwidth for UEs to perform initial access. System information 1105 may be dedicated to a reduction capability UE, for example, containing information applicable to a reduction capability UE but not to a higher capability UE. UE1102 may receive system information 1105 in a separate SIB for the reduction capability UE, distinct from the SIB that has system information applicable to the higher capability UE. UE1102 may receive system information 1105 in an SIB that carries system information for both the reduction capability UE and the higher capability UE. The common SIB may have different information elements for the higher capability UE and the reduction capability UE. For example, base station 1104 may transmit a common or shared SIB in CORESET 0, which is shared by a reduced-capability UE and a higher-capability UE (for example, in the initial DL BWP 1004).

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

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

[0097] In 1108, UE 1102 may perform at least part of the initial access procedure, such as the 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) which is dedicated to a reduction capability UE. As part of the initial access, UE 1102 may send and receive random access messages 1110 with the base station 1104. For example, in a dedicated initial DL BWP (e.g., 1013) and a dedicated initial UL BWP (e.g., 1011), the UE may send random access Msg1 with a preamble to the base station 904, receive Msg2 from the base station, send Msg3 to the base station, and / or receive Msg4 from the base station. In some embodiments, a dedicated physical random access channel (PRACH) resource may be configured for a reduced-capability UE, thereby enabling the network to identify the UE's reduced-capability during initial access and schedule Msg3 / PUCCH within the UL BWP supported by the UE. UE 1102 may, in 1110, transmit random access messages such as Msg1 during a random access occasion (RO) based on the SSB-to-RO mapping for the reduced-capability UE. Base station 1104 may configure SSB-to-RO mapping patterns separately for reduced-capability UEs and higher-capability UEs, for example, in separate system information or other signaling. In some embodiments, a 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 for non-CD SSB, such as periodicity, block index, power offset, center frequency, and numerology, may be the same as those for CD-SSB. Shared parameters may be configured in relation to CD-SSB or separately. The configuration for non-CD SSB may be selected to help ensure the measurement accuracy of a reduced capability UE with reduced receive branch and / or reduced antenna efficiency.If the parameters of a non-CD SSB (e.g., periodicity, block index, power offset, center frequency, numerology, etc.) are configured separately from or different from those of a CD-SSB, the parameters may be presented to the reduction capability UE in various ways. As a first example, the parameters of a non-CD SSB that form the basis of the SSB-to-RO or SSB-to-preamble mapping may be configured in system information 1105 (e.g., in a separate SIB from that for higher capability UEs, or in the same SIB but in a different IE than that for higher capability UEs). The parameters of a non-CD SSB may be configured in the broadcast PDCCH. The UE 1102 may determine one or more of the parameters of a non-CD SSB based on rules or lookup tables, or based on information known to the UE. The parameters of a non-CD SSB may be presented to or determined by the UE based on any combination of system information, PDCCH, lookup tables, or rules.

[0098] When a non-CD SSB is configured in a dedicated initial DL BWP (e.g., 1013) or a dedicated active DL BWP (e.g., 1014), UE1102, and higher-capacity UEs, may use the SSB for L1 and / or L3 measurements. Reduced-capacity UE1102, and higher-capacity UEs, may use the SSB to perform time / frequency tracking and / or other link maintenance procedures in an RRC connection state. Reduced-capacity UEs, and higher-capacity UEs, may use the non-CD SSB to perform timing advance (TA), resource mapping, and beam management in small data transmissions (SDT).

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

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

[0101] 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, which are dedicated to the reduced capability UE. Base station 1104 may perform the corresponding switch at 1120 for communication with UE 1102. UE 1102 may perform the switch at 1118 after completing the exchange of capability signaling 1114 in the dedicated initial DL BWP (e.g., 1013). The switch may be triggered at 1118 by a signal 1116 from base station 1104. Signal 1116 may include a MAC-CE which is broadcast, multicast, or unicast. Signal 1116 may include an RRC reconfiguration from base station 1104. The RRC reconfiguration may be a unicast to UE 1102. Signal 1116 may include DCI which is multicast or broadcast to the reduction capability UE. In some embodiments, the UE may switch in 1118 without signal 1116 from the base station. In such examples, UE 1102 may perform the switch in 1118 based on a timer. UE 1102 may receive a timer configuration in system information 1106, for example, in system information that is dedicated to the reduction capability UE. The timer may indicate that the UE will perform the switch after a configured number of subframes, a configured number of slots, or a configured amount of time following a reference time, such as following a capability exchange message, a RACH message, or another signal transmitted by the UE or received from the base station.

[0102] An active DL BWP dedicated to a reduction capability UE, e.g., 1014, may have associated configurations for CSS and one or more RS 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 and receive paging from the network, system information updates, WUS from base station 1104, or group common power control for PUCCH / PUSCH / SRS. The active DL BWP may include configured periodic or semi-static TRS and / or periodic CSI-RS and / or PRS. The active DL BWP may include configured non-CD SSB. The active DL BWP may include a CORESET and CSS configured for system information updates of the reduction capability UE. The active DL BWP may include a configured resynchronization reference signal indicating a system information update for the reduction capability UE.

[0103] As shown in 1122, UE1102 may monitor and / or receive PDSCH, PDCCH, TRS, CSI-RS, PRS, or non-CD SSB in an active DL BWP dedicated to a reduction capability UE. In 1126, UE1102 may transmit PUSCH, PUCCH, and / or SRS in an active UL BWP for a reduction capability UE.

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

[0105] In 1302, the UE performs at least part of the initial access based on an initial downlink BWP shared between the UE having a first capability and the UE having a second capability. The "UE having a first capability" or "UE with first capability" may refer to a UE supporting the first capability. The "UE having a second capability" or "UE with second capability" may refer to a UE supporting the second capability. Initial access may be performed, for example, by the BWP component 198 and / or initial BWP component 1540 of device 1504 in Figure 15. Figure 9 shows an example of UE902 performing initial access in a shared initial DL BWP. Figure 11 shows an example of UE1102 performing part of the initial access in a shared initial DL BWP and part of the initial access in a dedicated DL BWP for a reduced capability UE.

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

[0107] A UE may perform initial access based on an initial uplink BWP which is exclusive to UEs with first capability. Performing initial access may involve transmitting a random access preamble during an RO which has an SSB-to-RO mapping for UEs with first capability (sometimes called a spatial reference for random access procedures), which is different from that for UEs with second capability. The RO-to-SSB mapping provides a spatial reference for the RO. The SSB-to-RO mapping for UEs with first capability is based on a non-CD SSB. One or more parameters for the non-CD SSB may be configured independently of the CD-SSB, and one or more parameters include at least one of periodicity, block index, spatial reference for random access procedures, power offset, center frequency, or numerology. One or more parameters for the non-CD SSB may be the same as those for the CD-SSB, and one or more parameters include at least one of periodicity, block index, spatial reference for random access procedures, power offset, center frequency, or numerology. One or more parameters may come from at least one of the following: system information, broadcast physical downlink control channel, lookup table, or rule. Non-CD SSB may be configured in at least one of the second initial downlink BWP or active downlink BWP and is common to measurements by the first-capable UE and the second-capable UE. At least one of the second initial downlink BWP or 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 first-capable UE and the second-capable UE, and the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are less than or equal to the lower maximum UE bandwidth of the first-capable UE and the second-capable UE.The initial uplink BWP and the second initial downlink BWP can be at the edge of the carrier bandwidth.

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

[0109] In some embodiments, the UE may further receive system information or system information updates in the initial downlink BWP, and the system information is contained within a SIB that is exclusive to the UE of the first capability. In some embodiments, the UE may further receive system information or system information updates in the initial downlink BWP, and the system information contains separate information exclusive to the UE of the first capability within an SIB that carries information for the UE of the first capability and the UE of the second capability.

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

[0111] In some embodiments, the UE may further receive configurations for active downlink BWP and active uplink BWP. Configurations 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, paging, WUS, system information update, or CSS or CORESET for group common power control, non-CD SSB, additional CORESET or additional CSS for system information update, resynchronization reference signal for UE synchronization in DRX mode or indicating system information update, or L3 in-frequency measurement gap. Configurations may be received in system information that is exclusive to the UE having a first capability. Configurations may be received in RRC signaling for the UE. Configurations for active downlink BWP or active uplink BWP may be based on rules or lookup tables.

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

[0113] In some embodiments, the UE may receive a first configuration of a second initial downlink BWP that is exclusive to the UE having the first capability, and may also receive a second configuration of an active downlink BWP. In some embodiments, the first configuration of the second initial downlink BWP may be received in the first initial downlink BWP within an SIB that is exclusive to the UE having the first capability. In some embodiments, the first configuration of the second initial downlink BWP may be received in the first initial downlink BWP as information exclusive to the UE having the first capability within an SIB that carries information for the UEs having the first capability and the UEs having the second capability. In some embodiments, the first configuration of the second initial downlink BWP may be received in system information within CORESET 0, and this system information is exclusive to the UE having the first capability. In some embodiments, the second configuration of an active downlink BWP may be received in the second initial downlink BWP. In some embodiments, the configuration of the second initial downlink BWP may be based on a lookup table or rules.

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

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

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

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

[0118] In 1406, the UE may switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability. The BWP switching for 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 Figure 15. Figures 9 and 11 show examples of UEs 902 and 1102 switching to a dedicated active DL BWP for the reduced capability UE. In some embodiments, in 1302, the UE may perform initial access based on an initial downlink BWP and an initial uplink BWP shared between the UE having the first capability and the UE having the second capability, and after performing initial access, the UE may switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability. Figure 9 shows an exemplary embodiment of a UE using a shared initial DL BWP and a shared initial UL BWP. The initial downlink BWP may include CORESET 0 or CD-SSB configured for a first-capacity UE and a second-capacity UE, and the initial downlink BWP and initial uplink BWP have bandwidth at the center frequency of the carrier bandwidth, and the bandwidth is less than or equal to the lower maximum UE bandwidth of the first-capacity UE.

[0119] In 1408, the UE may perform at least one of layer 1 (L1) measurements or layer 3 (L3) measurements for a non-CD SSB in an active downlink BWP dedicated to the UE having a first capability. Reception and measurement may be performed, for example, by a BWP component 198 of UE 104, 350, or device 1504.

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

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

[0122] Performing initial access may involve transmitting a random access preamble during RO, which has an SSB-to-RO mapping for a first-capacity UE that differs from that for a second-capacity UE. The SSB-to-RO mapping for a first-capacity UE is based on a non-CD SSB. One or more parameters for the non-CD SSB may be configured independently of the CD-SSB, and one or more parameters include at least one of periodicity, block index, spatial reference for random access procedures, power offset, center frequency, or numerology. One or more parameters for the non-CD SSB may be the same as those for the CD-SSB, and one or more parameters include at least one of periodicity, block index, spatial reference for random access procedures, power offset, center frequency, or numerology. One or more parameters may come from at least one of system information, broadcast physical downlink control channels, lookup tables, or rules. Non-CD SSB may be configured in at least one of the second initial downlink BWP or active downlink BWP and is common to measurements by the first capability UE and the second capability UE. At least one of the second initial downlink BWP or 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 first capability UE and the second capability UE, and the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are less than or equal to the lower maximum UE bandwidth of the first capability UE. The initial uplink BWP and the second initial downlink BWP may be at the edge of the carrier bandwidth.

[0123] In some embodiments, the UE may further receive system information or system information updates in the initial downlink BWP, and the system information is contained within a SIB that is exclusive to the UE of the first capability. In some embodiments, the UE may further receive system information or system information updates in the initial downlink BWP, and the system information contains separate information exclusive to the UE of the first capability within an SIB that carries information for the UE of the first capability and the UE of the second capability.

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

[0125] In some embodiments, the UE may further receive configurations for active downlink BWP and active uplink BWP. Configurations 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, paging, WUS, system information update, or CSS or CORESET for group common power control, non-CD SSB, additional CORESET or additional CSS for system information update, resynchronization reference signal for UE synchronization in DRX mode or indicating system information update, or L3 in-frequency measurement gap when SSB is not transmitted in the active downlink BWP. Configurations may be received in system information that is exclusive to the UE having a first capability. Configurations may be received in RRC signaling for the UE. Configurations for active downlink BWP or active uplink BWP may be based on rules or lookup tables.

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

[0127] In some embodiments, the UE may receive a first configuration of a second initial downlink BWP that is exclusive to the UE having the first capability, and may also receive a second configuration of an active downlink BWP. In some embodiments, the first configuration of the second initial downlink BWP may be received in the first initial downlink BWP within an SIB that is exclusive to the UE having the first capability. In some embodiments, the first configuration of the second initial downlink BWP may be received in the first initial downlink BWP as information exclusive to the UE having the first capability within an SIB that carries information for the UEs having the first capability and the UEs having the second capability. In some embodiments, the first configuration of the second initial downlink BWP may be received in system information within CORESET 0, and this system information is exclusive to the UE having the first capability. In some embodiments, the second configuration of an active downlink BWP may be received in the second initial downlink BWP. In some embodiments, the configuration of the second initial downlink BWP may be based on a lookup table or rules.

[0128] Figure 15 is Figure 1500, which shows an example of a hardware implementation for device 1504. Device 1504 may be a UE, a component of a UE, or implement UE functionality. In some embodiments, device 1504 may include a cellular baseband processor 1524 (also called 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 embodiments, device 1504 may further include one or more subscriber identity module (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some embodiments, the device 1504 may further include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., motion sensors such as a barometric pressure sensor / altimeter, an inertial management unit (IMU), a gyroscope, and / or an accelerometer, light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies used for positioning), an additional memory module 1526, a power supply 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include an on-chip transceiver (TRX) (or, in some cases, simply a receiver (RX)).The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include their own dedicated antennas and / or utilize antenna 1580 for communication. The cellular baseband processor 1524 communicates with the RU associated with the UE 104 and / or network entity 1502 via transceiver 1522 through one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include computer-readable media / memory 1524', 1506', respectively. An additional memory module 1526 may also be considered computer-readable media / memory. Each computer-readable media / memory 1524', 1506', 1526 may be non-transient. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including the execution of software stored in the computer-readable media / memory. When the software is executed by the cellular baseband processor 1524 / application processor 1506, it causes the cellular baseband processor 1524 / application processor 1506 to perform the various functions described above. Computer-readable media / memory may also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 when the software is executed. 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 the TX processor 368, RX processor 356, and controller / processor 359. In one configuration, the device 1504 may be a processor chip (modem and / or application) and may include only the cellular baseband processor 1524 and / or application processor 1506, while in another configuration, the device 1504 may be the entire UE (see, for example, 350 in Figure 3) and may include additional modules of the device 1504.

[0129] The cellular baseband processor 1524 and / or the application processor 1506 may include a BWP component 198, which is configured to perform at least part of the initial access based on an initial downlink BWP shared between a first-capacity UE and a second-capacity UE, as described, for example, in relation to 1302 in Figure 13, and to switch to an active downlink BWP and an active uplink BWP that are exclusive to the first-capacity UE, as described, for example, in relation to 1304 in Figure 13. As an example, the BWP component 198 may include, for example, an initial BWP component 1540, which is configured to perform at least part of the initial access based on an initial downlink BWP shared between a first-capacity UE and a second-capacity UE, as described, as described, in relation to 1302 in Figure 13. The BWP component 198 may be further configured to perform any of the embodiments of the algorithm in the flowcharts of Figures 13 and 14, and / or the embodiments performed by the UE in Figures 9 and / or 11.

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

[0131] As shown, the device 1504 may include various components configured for various functions. In one configuration, the device 1504, in particular the cellular baseband processor 1524 and / or application processor 1506, may include means for performing at least part of the initial access based on an initial downlink BWP shared between a first-capacity UE and a second-capacity UE, and means for switching to an active downlink BWP and an active uplink BWP exclusively for the first-capacity UE. The device 1504 may further include means for receiving system information in the initial downlink BWP, the system information contained in an SIB exclusively for the first-capacity UE. The device 1504 may further include means for receiving system information in the initial downlink BWP, the system information containing separate information exclusively for the first-capacity UE in an SIB carrying information for the first-capacity UE and the second-capacity UE. The device 1504 may further include means for receiving configurations for the active downlink BWP and the active uplink BWP. Device 1504 may further include means for performing capability signaling procedures indicating that a UE has a first capability. Device 1504 may further include means for receiving a first configuration of a second initial downlink BWP which is dedicated to UEs having the first capability, and means for receiving a second configuration of an active downlink BWP. Device 1504 may include means for receiving a first configuration of a second initial downlink BWP which is dedicated to UEs having the first capability, the first configuration of the second initial downlink BWP being received in the first initial downlink BWP within an SIB carrying information for UEs having the first capability and UEs having the second capability. Device 1504 may also include means for receiving a configuration for a non-CD SSB in an active downlink BWP which is dedicated to UEs having the first capability, and means for performing at least one of L1 or L3 measurements for a non-CD SSB in an active downlink BWP which is dedicated to UEs having the first capability.Device 1504 may include means for implementing each of the algorithm blocks in the flowcharts of Figures 13 and 14, and / or the embodiments implemented by the UE in Figures 9 and / or 11. The means may be one or more components of Device 1504 configured to implement the functions enumerated by the means. As described above, Device 1504 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and the controller / processor 359, configured to implement the functions enumerated by the means.

[0132] Figure 16 is a flowchart 1600 of a wireless communication method. This method can be implemented 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). This method can provide an initial access and subsequent BWP configuration that provides reduced bandwidth supported by reduced-capacity UEs while maintaining flexibility in configuring bandwidth for higher-capacity UEs. A network entity implementing this method may support communication with one or more UEs having a first capability associated with a maximum UE bandwidth lower than a second capability, and with one or more UEs having a second capability. For example, a base station may communicate with reduced-capacity UEs and higher-capacity UEs.

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

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

[0135] Performing initial access may involve receiving a random access preamble during RO, which has an SSB-to-RO mapping for a first-capacity UE that differs from that for a second-capacity UE. The SSB-to-RO mapping for a first-capacity UE is based on a non-CD SSB. One or more parameters for the non-CD SSB may be configured independently of the CD-SSB, and one or more parameters include at least one of periodicity, block index, spatial reference for random access procedures, power offset, center frequency, or numerology. One or more parameters for the non-CD SSB may be the same as those for the CD-SSB, and one or more parameters include at least one of periodicity, block index, spatial reference for random access procedures, power offset, center frequency, or numerology. One or more parameters may come from at least one of system information, broadcast physical downlink control channels, lookup tables, or rules. Non-CD SSB may be configured in at least one of the second initial downlink BWP or active downlink BWP and is common to measurements by the first capability UE and the second capability UE. At least one of the second initial downlink BWP or 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 first capability UE and the second capability UE, and the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are less than or equal to the lower maximum UE bandwidth of the first capability UE and the second capability UE. The initial uplink BWP and the second initial downlink BWP may be at the edge of the carrier bandwidth.

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

[0137] In some embodiments, the network entity may further transmit system information or system information updates in the initial downlink BWP, and the system information is contained within a SIB that is exclusive to the UE of the first capability. In some embodiments, the network entity may further transmit system information or system information updates in the initial downlink BWP, and the system information contains separate information exclusive to the UE of the first capability within an SIB that carries information for the UE of the first capability and the UE of the second capability.

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

[0139] In some embodiments, a network entity may further transmit configurations for active downlink BWPs and active uplink BWPs. Configurations for active downlink BWPs 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 updates, WUS or group common power control, non-CD SSB, additional CORESET or additional CSS for system information updates, a resynchronization reference signal indicating a system information update for UE synchronization in discontinuous reception (DRX) mode, or an in-frequency measurement gap in Layer 3 (L3). Configurations may be transmitted in system information that is exclusive to UEs having a first capability. Configurations may be transmitted in RRC signaling for UEs. Configurations for active downlink BWPs or active uplink BWPs may be based on rules or lookup tables.

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

[0141] In some embodiments, a network entity may further transmit a first configuration of a second initial downlink BWP that is exclusive to a UE having a first capability, and may receive a second configuration of an active downlink BWP. In some embodiments, the first configuration of the second initial downlink BWP may be transmitted in the first initial downlink BWP within a SIB that is exclusive to the UE having the first capability. In some embodiments, the first configuration of the second initial downlink BWP may be transmitted in the first initial downlink BWP as information exclusive to the UE having the first capability within a SIB that carries information for the UEs having the first capability and the UEs having the second capability. In some embodiments, the first configuration of the second initial downlink BWP may be transmitted in system information within CORESET 0, and this system information is exclusive to the UE having the first capability. In some embodiments, the second configuration of an active downlink BWP may be received in the second initial downlink BWP. In some embodiments, the configuration of the second initial downlink BWP may be based on a lookup table or rules.

[0142] Figure 17 is a flowchart 1700 of a wireless communication method. This method can be implemented 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). This method can provide an initial access and subsequent BWP configuration that provides reduced bandwidth supported by reduced-capacity UEs while maintaining flexibility in configuring bandwidth for higher-capacity UEs. A network entity implementing this method may support communication with one or more UEs having a first capability associated with a maximum UE bandwidth lower than a second capability, and with one or more UEs having a second capability. For example, a base station may communicate with reduced-capacity UEs and higher-capacity UEs.

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

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

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

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

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

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

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

[0150] Performing initial access may involve receiving a random access preamble during RO, which has an SSB-to-RO mapping for a first-capacity UE that differs from that for a second-capacity UE. The SSB-to-RO mapping for a first-capacity UE is based on a non-CD SSB. One or more parameters for the non-CD SSB may be configured independently of the CD-SSB, and one or more parameters include at least one of periodicity, block index, spatial reference for random access procedures, power offset, center frequency, or numerology. One or more parameters for the non-CD SSB may be the same as those for the CD-SSB, and one or more parameters include at least one of periodicity, block index, spatial reference for random access procedures, power offset, center frequency, or numerology. One or more parameters may come from at least one of system information, broadcast physical downlink control channels, lookup tables, or rules. Non-CD SSB may be configured in at least one of the second initial downlink BWP or active downlink BWP and is common to measurements by the first capability UE and the second capability UE. At least one of the second initial downlink BWP or 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 first capability UE and the second capability UE, and the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the bandwidth of the initial DL BWP and the bandwidth of the initial UL BWP are less than or equal to the lower maximum UE bandwidth of the first capability UE and the second capability UE. The initial uplink BWP and the second initial downlink BWP may be at the edge of the carrier bandwidth.

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

[0152] In some embodiments, the network entity may further output system information or system information updates in the initial downlink BWP, for example for transmission, and the system information is contained within a SIB that is exclusive to the UE of the first capability. In some embodiments, the network entity may further transmit system information or system information updates in the initial downlink BWP, and the system information contains separate information exclusive to the UE of the first capability within an SIB that carries information for the UE of the first capability and the UE of the second capability.

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

[0154] In some embodiments, the base station may further transmit configurations for active downlink BWP and active uplink BWP. Configurations 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 updates, WUS or group common power control, non-CD SSB, additional CORESET or additional CSS for system information updates, a resynchronization reference signal indicating a system information update for UE synchronization in intermittent receive (DRX) mode, or an L3 in-frequency measurement gap when SSB is not transmitted in the active downlink BWP. Configurations may be transmitted in system information that is exclusive to UEs having a first capability. Configurations may be transmitted in RRC signaling for UEs. Configurations for active downlink BWP or active uplink BWP may be based on rules or lookup tables.

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

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

[0157] Figure 18 is Figure 1800, which shows an example of a hardware implementation for a network entity 1802. The network entity 1802 may be a base station, a component of a base station, or can implement base station functionality. The network entity 1802 may include at least one of CU1810, DU1830, or RU1840. For example, depending on the layer functionality handled by component 199, the network entity 1802 may include CU1810, both CU1810 and DU1830, each of CU1810, DU1830, and RU1840, both DU1830, DU1830, and RU1840, or RU1840. CU1810 may include a CU processor 1812. The CU processor 1812 may include on-chip memory 1812'. In some embodiments, CU1810 may further include an additional memory module 1814 and a communication interface 1818. CU1810 communicates with DU1830 via a midhall link such as an F1 interface. Device 1830 may include a DU processor 1832. The DU processor 1832 may include on-chip memory 1832'. In some embodiments, DU1830 may further include an additional memory module 1834 and a communication interface 1838. DU1830 communicates with RU1840 via a fronthall link. RU1840 may include an RU processor 1842. The RU processor 1842 may include on-chip memory 1842'. In some embodiments, RU1840 may further include an additional memory module 1844, one or more transceivers 1846, an antenna 1880, and a communication interface 1848. RU1840 communicates with UE104. The on-chip memories 1812', 1832', 1842' and the additional memory modules 1814, 1834, 1844 can each be considered computer-readable media / memory. Each computer-readable media / memory may be non-temporary. Each of the processors 1812, 1832, and 1842 is responsible for general processing, including the execution of software stored in computer-readable media / memory. When the software is executed by the corresponding processor, it causes the processor to perform the various functions described above.Computer-readable media / memory can also be used to store data that is manipulated by the processor when software is running.

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

[0159] Network entity 1802 may include additional components that implement each of the algorithm blocks in the flowcharts of Figures 16 and 17, and / or the embodiments implemented by the base station in Figure 9 or Figure 11. Thus, each block in the flowcharts of Figures 16 and 17, and / or the embodiments implemented by the base station in Figure 9 or Figure 11, may be implemented by components, and the device may include one or more of those components. A component may be one or more hardware components specifically configured to perform the described process / algorithm, implemented by a processor configured to perform the described process / algorithm, stored in a computer-readable medium for a processor-based implementation, or any combination thereof.

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

[0161] It should be understood that the specific order or hierarchy of blocks in the disclosed process / flowchart is illustrative of an exemplary technique. It should also be understood that the specific order or hierarchy of blocks in the process / flowchart may be rearranged based on design preferences. Furthermore, some blocks may be combined or omitted. The attached claims for the method present various block elements in an exemplary order, and are not limited to the specific order or hierarchy presented.

[0162] The foregoing description is provided to enable any person skilled in the art to practice the various embodiments described herein. Various modifications of these embodiments will be readily apparent to a person skilled in the art, and the general principles defined herein may be applied to other embodiments. Accordingly, the claims should not be limited to the embodiments described herein, but should be given the entire scope consistent with the wording of the claims. References to singular elements mean "one or more" and not "unique" unless otherwise explicitly stated. Terms such as "if," "when," and "while" indicate "under the condition that," rather than implying an immediate temporal relationship or response. That is, these phrases, for example, "when," do not imply an immediate action in response to or during the occurrence of an action, but merely imply that an action will occur if the condition is met, but without requiring any specific or immediate time constraint for the action to occur. The word "exemplary" is used herein to mean "to serve as an example, case, or illustration." Any embodiment described herein as “exemplary” should not necessarily be construed as being preferable or more advantageous than any other embodiment. Unless otherwise specified, the term “some” means one or more. Combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” include any combination of A, B, and / or C, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as “at least one of A, B, or C,” “one or more of A, B, or C,” “at least one of A, B, and C,” “one or more of A, B, and C,” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, and any such combination may include one or more members of A, B, or C.A set should be interpreted as a set of elements having one or more elements. Thus, in the case of a set of X, X will contain one or more elements. When the first device receives data from or transmits data to the second device, the data may be received / transmitted directly between the first and second devices, or indirectly between the first and second devices through a set of devices. All structural and functional equivalents of the various aspects of the elements described throughout this disclosure, known to those skilled in the art or to be known thereafter, are expressly incorporated herein by reference and are encompassed by the claims. Furthermore, nothing disclosed herein is made public, whether such disclosure is expressly enumerated in the claims or not. The terms “module,” “mechanism,” “element,” and “device” may not be substitutes for the term “means.” Thus, no claimed element should be interpreted as means plus function unless it is expressly enumerated using the phrase “means for.”

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

[0164] The following embodiments are illustrative and may be combined with other embodiments or teachings described herein without limitation.

[0165] Embodiment 1 is a method for wireless communication in a UE having a first capability associated with a maximum UE bandwidth lower 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 that are dedicated to the UE having the first capability.

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

[0167] In Embodiment 3, the method of Embodiment 1 or Embodiment 2 further comprises a first initial downlink BWP including a CORESET 0 or CD-SSB configured for a first-capacity UE and a second-capacity UE, 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 first bandwidth of the first initial downlink BWP and the second bandwidth of the initial uplink BWP are less than or equal to the lower maximum UE bandwidth of the first-capacity UE and the second-capacity UE.

[0168] In Embodiment 4, any of the methods in Embodiments 1 to 3 further includes receiving system information or system information updates in the first initial downlink BWP, the system information being contained within an SIB that is dedicated to the UE of the first capability.

[0169] In Embodiment 5, any of the methods in Embodiments 1 to 3 further includes receiving system information or system information updates in a first initial downlink BWP, wherein the system information includes separate information exclusive to the first capability UE within an SIB carrying information for the first capability UE and the second capability UE.

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

[0171] In Embodiment 7, any of the methods in Embodiments 1 to 5 further includes transmitting a random access preamble into an RO having an SSB-to-RO mapping or an SSB-to-preamble mapping configured for a UE having a first capability.

[0172] In aspect 8, any method of aspects 1 to 7 further includes receiving a configuration for an active downlink BWP and an active uplink BWP, the configuration for the active downlink BWP including 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, system information update, WUS or group common power control, non-CD SSB, additional CORESET or additional CSS for system information update, a resynchronization reference signal indicating a system information update for UE synchronization in DRX mode, or an L3 in-frequency measurement gap when SSB is not transmitted in the active downlink BWP.

[0173] In aspect 9, the method of aspect 8 further includes the configuration being received in system information which is exclusive to the UE having the first capability.

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

[0175] In embodiment 11, any of the methods in embodiments 1 to 7 further includes the configuration of the active downlink BWP or active uplink BWP being based on rules or lookup tables.

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

[0177] In Embodiment 13, the method of Embodiment 1 further includes the UE performing initial access on partly a first initial downlink BWP shared between the UE having first capability and the UE having second capability, and on partly a second initial downlink BWP that is exclusive to the UE having first capability.

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

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

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

[0181] In embodiment 17, the method of embodiment 13, 15, or 16 further comprises one or more parameters for non-CD SSB being the same as those for CD-SSB, and one or more parameters including at least one of periodicity, block index, spatial reference for random access procedure, power offset, center frequency, or numerology.

[0182] In embodiment 18, the method of embodiment 13, 15, or 16 further comprises one or more parameters for non-CD SSB being configured independently of 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 numerology.

[0183] In embodiment 19, the method of embodiment 18 further includes that one or more parameters are from at least one of system information, broadcast physical downlink control channels, lookup tables, or rules.

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

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

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

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

[0188] In embodiment 24, the method of embodiment 23 further includes the first configuration of the second initial downlink BWP being received in the first initial downlink BWP within an SIB which is dedicated to the UE of the first capability.

[0189] In embodiment 25, the method of embodiment 23 further includes the first configuration of the second initial downlink BWP being received in the first initial downlink BWP as information exclusive to the first capability UE within an SIB that carries information for the first capability UE and the second capability UE.

[0190] In aspect 26, the method of aspect 23 further includes that the first configuration of the second initial downlink BWP is received in system information within CORESET 0, and that this system information is dedicated to the UE of the first capability.

[0191] In embodiment 27, the method of embodiment 23 further includes the fact that the second configuration of the active downlink BWP is received in the second initial downlink BWP.

[0192] In embodiment 28, the method of embodiment 1 or any of 13 to 22 further includes the configuration of the second initial downlink BWP being based on a lookup table or rule.

[0193] In Embodiment 29, the method of Embodiment 1 further includes performing the initial access on partly a first initial downlink BWP shared between a first-capable UE and a second-capable UE, and on partly a second initial downlink BWP that is exclusive to the first-capable UE.

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

[0195] In embodiment 31, the method of embodiment 29 or embodiment 30 further includes receiving a first configuration of a second initial downlink BWP which is dedicated to UEs having a first capability, the first configuration of the second initial downlink BWP being received in the first initial downlink BWP within an SIB that carries information about UEs having a first capability and UEs having a second capability.

[0196] In embodiment 32, any of the methods in embodiments 29 to 31 further includes the fact that a second initial downlink BWP, which is dedicated to the UE having the first capability, does not include CORESET 0 or CD-SSB.

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

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

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

[0200] In embodiment 36, any of the methods in embodiments 29 to 35 further includes receiving system information updates in RRC signaling on an active downlink BWP that is dedicated to a UE having the first capability.

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

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

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

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

[0205] Embodiment 41 is a non-temporary computer-readable medium for storing computer-executable code in a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, wherein the code, when executed by a processor, causes the processor to carry out the method according to any one of claims 1 to 37.

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

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

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

[0209] In aspect 45, any method of aspects 42 to 44 further includes transmitting system information in a first initial downlink BWP, the system information being contained within an SIB that is dedicated to the UE of the first capability.

[0210] In embodiment 46, any of the methods in embodiments 42 to 44 further includes transmitting system information in a first initial downlink BWP, the system information including separate information dedicated to the first capability UE within an SIB that carries information for the first capability UE and the second capability UE.

[0211] In embodiment 47, any of the methods in embodiments 42 to 46 further includes performing initial access by receiving a random access preamble from the UE during RO, which has an SSB-to-RO mapping based on CD-SSB.

[0212] In embodiment 48, any method of embodiments 42 to 46 further includes performing initial access by receiving a random access preamble from a UE while an RO has an SSB-to-RO mapping or an SSB-to-preamble mapping configured for a UE having a first capability.

[0213] In aspect 49, any method of aspects 42 to 48 further includes transmitting a configuration for an active downlink BWP and an active uplink BWP, the configuration for the active downlink BWP including 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, system information update, WUS or group common power control, non-CD SSB, a resynchronization reference signal indicating a system information update for UE synchronization in DRX mode, or an L3 in-frequency measurement gap when SSB is not transmitted in the active downlink BWP.

[0214] In embodiment 50, the method of embodiment 49 further includes the transmission in system information which is exclusive to the UE having the first capability.

[0215] In embodiment 51, the method of embodiment 49 further includes the transmission of the configuration to the UE in RRC signaling.

[0216] In embodiment 52, any of the methods in embodiments 42 to 48 further includes the configuration of the active downlink BWP or active uplink BWP being based on rules or lookup tables.

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

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

[0219] In embodiment 55, the method of embodiment 42 or 54 further includes the fact that initial access is further based on an initial uplink BWP which is dedicated to a UE having the first capability.

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

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

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

[0223] In embodiment 59, the method of embodiment 57 further comprises one or more parameters for non-CD SSB being configured independently of 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 numerology.

[0224] In embodiment 60, any of the methods in embodiments 57 to 59 further includes the fact that one or more parameters are from at least one of system information, broadcast physical downlink control channels, lookup tables, or rules.

[0225] In embodiment 61, any of the methods in embodiments 57 to 59 further includes the fact that the non-CD SSB is configured in at least one of the second initial downlink BWP or the active downlink BWP and is common to the measurements by the first capability UE and the second capability UE.

[0226] In embodiment 62, any of the methods in embodiments 54 to 61 further includes the fact that at least one of the second initial downlink BWP or active downlink BWP overlaps in frequency with the CD-SSB or CORESET 0 of the first initial downlink BWP.

[0227] In embodiment 63, any method of embodiments 54 to 62 further comprises a first initial downlink BWP having a CORESET 0 and a CD-SSB configured for a first-capacity UE and a second-capacity UE, wherein the first initial downlink BWP has a bandwidth at the center frequency of the carrier bandwidth, the bandwidth being less than or equal to the lower maximum UE bandwidth of the first-capacity UE, and the initial uplink BWP and the second initial downlink BWP are at the edge of the carrier bandwidth.

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

[0229] In aspect 65, the method of aspect 64 further includes the transmission in the first initial downlink BWP within an SIB that is dedicated to the UE of the first capability.

[0230] In embodiment 66, the method of embodiment 64 further includes the first configuration of the second initial downlink BWP being transmitted in the first initial downlink BWP as information exclusive to the first capability UE within an SIB that carries information for the first capability UE and the second capability UE.

[0231] In aspect 67, any of the methods in aspects 64 to 66 further includes that the first configuration of the second initial downlink BWP is transmitted in system information within CORESET 0, and that this system information is dedicated to the UE of the first capability.

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

[0233] In embodiment 69, any of the methods in embodiments 42 to 63 further includes the configuration of the second initial downlink BWP being based on a lookup table or rule.

[0234] In embodiment 70, the method of embodiment 42 further includes performing initial access on a first initial downlink BWP shared between a first-capacity UE and a second-capacity UE, and on a second initial downlink BWP dedicated to the first-capacity UE, wherein the first initial downlink BWP includes CORESET 0 and a cell CD-SSB configured for the first-capacity UE and the second-capacity UE.

[0235] In embodiment 71, the method of embodiment 70 further comprises outputting for transmission a first configuration of a second initial downlink BWP which is dedicated to a first-capacity UE, the first configuration of the second initial downlink BWP being received in the SIB, which carries information for the first-capacity UE and the second-capacity UE in the first initial downlink BWP, and the second initial downlink BWP which is dedicated to the first-capacity UE does not include CORESET 0 or CD-SSB.

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

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

[0238] In embodiment 74, any of the methods in embodiments 70 to 73 further includes outputting a system information update for transmission in RRC signaling on an active downlink BWP that is dedicated to a UE having the first capability.

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

[0240] Embodiment 76 is an apparatus for wireless communication in a network entity, the apparatus comprising means for carrying out the method described in any of claims 42 to 74.

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

[0242] Embodiment 78 is a non-temporary computer-readable medium for storing computer-executable code in a network entity, wherein, when the code is executed by a processor, the processor causes the processor to perform the method according to any one of claims 42 to 74.

[0243] Embodiment 79 is a computer program product for wireless communication in a network entity, wherein, when the program is executed by a computer, the computer program product includes instructions that cause the network entity to perform the method described in any of Embodiments 42 to 74.

[0244] Embodiment 80 is a computer program product for wireless communication in a UE, the computer program product includes instructions that cause the UE to perform the method according to any one of claims 1 to 37 when the program is executed by a computer.

[0245] Embodiment 81 is a device for wireless communication in a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, the device comprising a memory and at least one processor coupled to the memory, wherein at least in part, based on information stored in the memory, the at least one processor is configured to perform at least a portion of the 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, to switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability.

[0246] In embodiment 82, the apparatus of embodiment 81 further includes that at least one processor is configured to perform initial access on partly a first initial downlink BWP shared between a UE having first capability and a UE having second capability, and on partly a second initial downlink BWP which is exclusive to the UE having first capability.

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

[0248] In embodiment 84, the apparatus of embodiment 82 or 83 further includes that at least one processor is configured to receive a first configuration of a second initial downlink BWP which is dedicated to a first-capacity UE, the first configuration of the second initial downlink BWP is received in the first initial downlink BWP within an SIB that carries information about the first-capacity UE and the second-capacity UE.

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

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

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

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

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

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

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

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

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

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

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

[0260] In embodiment 96, the apparatus of embodiment 95 further includes receiving the first configuration of the second initial downlink BWP in either an SIB dedicated to a first capable UE within the first initial downlink BWP, or system information dedicated to a first capable UE within CORESET 0.

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

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

[0263] In embodiment 99, the apparatus of embodiment 98 is further configured to receive system information or system information updates in a first initial downlink BWP, wherein the system information is contained in a first SIB that is exclusive to a first capability UE, or to receive system information or system information updates in a first initial downlink BWP, wherein the system information contains separate information exclusive to a first capability UE in a second SIB that carries separate information for a first capability UE and additional information for a second capability UE.

[0264] In embodiment 100, the apparatus of embodiment 98 or 99 further includes being configured to transmit a random access preamble into a first RO having a first SSB-to-RO mapping based on a CD-SSB, or into a second RO having a second SSB-to-RO mapping or SSB-to-preamble mapping configured for a first capability UE.

[0265] In embodiment 101, the apparatus of embodiment 81 further comprises at least one processor configured to receive configurations for an active downlink BWP and an active uplink BWP, the configuration for the active downlink BWP including 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, system information update, WUS or group common power control, non-CD SSB, additional CORESET or additional CSS for system information update, a resynchronization reference signal indicating a system information update for UE synchronization in DRX mode, or an L3 in-frequency measurement gap when SSB is not transmitted in the active downlink BWP.

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

[0267] In embodiment 103, the apparatus of embodiment 81 further includes that the configuration of the active downlink BWP or active uplink BWP is based on rules or lookup tables.

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

[0269] Embodiment 105 is a device for wireless communication in a network entity, the device comprising a memory and at least one processor coupled to the memory, wherein at least in part, based on information stored in the memory, the at least one processor is configured to perform an initial access to a UE having a first capability associated with a maximum UE bandwidth lower than a second capability, at least in part of the initial access being performed 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, to switch to an active downlink BWP and an active uplink BWP that are dedicated to the UE having the first capability for communication with the UE.

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

[0271] In embodiment 107, the apparatus of embodiment 106 further includes outputting for transmission a first configuration of a second initial downlink BWP which is dedicated to a first-capacity UE, the first configuration of the second initial downlink BWP being received in the SIB, which carries information for the first-capacity UE and the second-capacity UE in the first initial downlink BWP, and the second initial downlink BWP which is dedicated to the first-capacity UE does not include CORESET 0 or CD-SSB.

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

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

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

Claims

1. A device for wireless communication in user equipment (UE) having a first capability associated with a maximum UE bandwidth lower than a second capability, Memory and The system comprises at least one processor coupled to the memory, wherein the at least one processor operates based at least partially on the information stored in the memory. Based on a first initial downlink bandwidth portion (BWP) shared between the UE having the first capability and the UE having the second capability, at least a portion of the initial access is performed. A device configured to switch after the initial access to an active downlink BWP and an active uplink BWP, which are dedicated to the UE and have the first capability.

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

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

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

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

6. The apparatus according to claim 3, wherein, in order 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, and the RO has a mapping from a synchronous signal block (SSB) to the CD-SSB in the first initial downlink BWP.

7. The aforementioned at least one processor, The apparatus according to claim 2, wherein the active downlink BWP, which is dedicated to the UE having the first capability, is further configured to receive a configuration for a non-cell defined SSB (non-CD SSB).

8. The aforementioned at least one processor, The apparatus according to claim 7, wherein the active downlink BWP, which is dedicated to the UE having the first capability, is further configured to perform at least one of layer 1 (L1) measurement or layer 3 (L3) measurement on the non-CD SSB.

9. The aforementioned at least one processor, The apparatus according to claim 2, further configured to receive system information updates in the radio resource control (RRC) signaling in the active downlink BWP dedicated to the UE having the first capability.

10. The apparatus according to claim 2, wherein, in order 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, and the RO has a mapping from a synchronization signal block (SSB) based on a non-cell-defined SSB (non-CD SSB) to the RO.

11. One or more parameters for a non-cell-defined SSB (non-CD SSB) in the second initial downlink BWP or the active downlink BWP, which is exclusive to the UE having the first capability, include the same parameters as those for a CD-SSB, and the one or more parameters are periodicity, block index, Spatial criteria for random access procedures, Power offset Center frequency, or The apparatus according to claim 2, comprising at least one of the numerologies.

12. The apparatus according to 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 by the UE having the first capability and the UE having the second capability.

13. The apparatus according to 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 first initial downlink BWP has a bandwidth at the center frequency of the carrier bandwidth, and the bandwidth is less than or equal to the lower maximum UE bandwidth of the UE having the first capability. The apparatus according to claim 2, wherein the initial uplink BWP and the second initial downlink BWP are located at the edge of the carrier bandwidth.

15. The aforementioned at least one processor, The first configuration of the second initial downlink BWP, which is dedicated to the UE having the first capability, and The apparatus according to claim 2, wherein the second initial downlink BWP is further configured to receive the second configuration of the active downlink BWP.

16. The first configuration of the second initial downlink BWP is A system information block (SIB) within the first initial downlink BWP that is dedicated to the UE and has the first capability, or The apparatus according to claim 15, which is received in one of the system information exclusive to the UE having the first capability within the control resource set 0 (CORESET 0).

17. The apparatus according to claim 2, wherein the configuration of the second initial downlink BWP is based on a lookup table or rule.

18. The at least one processor is configured to perform the initial access based on the first initial downlink BWP and the initial uplink BWP shared between the UE having the first capability and the UE having the second capability, and after the initial access, to switch to the active downlink BWP and the active uplink BWP which are dedicated to the UE having the first capability, wherein the BWP switching of the UE is configured for time-division duplex (TDD) mode, full-duplex frequency-division duplex (FD-FDD) mode, or half-duplex frequency-division duplex (HD-FDD) mode, and the first initial downlink BWP is configured for the control resource set 0 (CORESET) configured for the UE having the first capability and the UE having the second capability. 0) The apparatus according to claim 1, comprising a cell-defined synchronization signal block (CD-SSB), wherein the first initial downlink BWP and the initial uplink BWP have the same or different center frequencies and the same or different bandwidths, and the first bandwidth of the first initial downlink BWP and the second bandwidth of the initial uplink BWP are less than or equal to the lower maximum UE bandwidth of the UE having the first and second capabilities.

19. The aforementioned at least one processor, Receiving system information or system information updates in the first initial downlink BWP, wherein the system information is included in a first system information block (SIB) that is exclusive to the UE having the first capability, or The apparatus according to claim 18, further configured to receive the system information or the system information update in the first initial downlink BWP, wherein the system information includes the separate information which is exclusive to the first capable UE, in a second SIB that carries separate information for the first capable UE and additional information for the second capable UE.

20. In order to perform the initial access, at least one processor, A random access preamble is transmitted during a first random access occasion (RO) which has a mapping from a first synchronization signal block (SSB) based on a cell-defined SSB (CD-SSB) to the RO, or The apparatus according to claim 18, wherein the random access preamble is configured to be transmitted into a second RO having a second SSB-to-RO mapping or an SSB-to-preamble mapping, configured for the UE having the first capability.

21. The aforementioned at least one processor, It is further configured to receive the configuration for the active downlink BWP and the configuration for the active uplink BWP, and the configuration for the active downlink BWP is Periodic or semi-static tracking reference signal (TRS), Periodic or semi-static channel state information reference signal (CSI-RS), Periodic or semi-static positioning reference signal (PRS), A common search space (CSS) or control resource set (CORESET) for paging, system information updates, wake-up signals (WUS), or group-wide power control. Non-cell-defined synchronization signal block (non-CD SSB), For updating the aforementioned system information, additional CORESET or additional CSS, A resynchronization reference signal indicating the system information update for UE synchronization in intermittent reception (DRX) mode, or The apparatus according to claim 1, wherein if SSB is not transmitted in the active downlink BWP, it includes one or more measurement gaps within the Layer 3 (L3) frequency.

22. The apparatus according to claim 21, wherein the configuration is included in system information that is exclusive to the UE having the first capability, or in radio resource control (RRC) signaling for the UE.

23. The apparatus according to claim 1, wherein the configuration of the active downlink BWP or the active uplink BWP is based on rules or a lookup table.

24. The aforementioned at least one processor, The UE is further configured to perform a capability signaling procedure indicating that it has the first capability, and the at least one processor, after completing the capability signaling procedure, Media access control element (MAC-CE), Radio Resource Control (RRC) Reconfiguration, Downlink control information (DCI), or The apparatus according to claim 1, configured to switch to the active downlink BWP and the active uplink BWP based on at least one of the timers configured in the system information for the UE having the first capability.

25. A device for wireless communication in a network entity, Memory and The system comprises at least one processor coupled to the memory, wherein the at least one processor operates based at least partially on the information stored in the memory. Performing initial access to a user equipment (UE) having a first capability associated with a maximum UE bandwidth lower than a second capability, wherein at least a portion of the initial access is performed based on a first initial downlink bandwidth portion (BWP) shared between the UE having the first capability and the UE having the second capability. A device configured to, after the initial access, switch to an active downlink BWP and an active uplink BWP, which are dedicated to the UE and have the first capability, for communication with the UE.

26. The apparatus according to claim 25, wherein the at least one processor is configured to perform the initial access on partly a first initial downlink BWP shared between the first-capable UE and the second-capable UE, and on partly a second initial downlink BWP dedicated to the first-capable UE, the first initial downlink BWP comprising a control resource set 0 (CORESET 0) and a cell-defined synchronization signal block (CD-SSB) configured for the first-capable UE and the second-capable UE.

27. The aforementioned at least one processor, The apparatus according to claim 26, wherein the first configuration of the second initial downlink BWP, which is dedicated to the UE having the first capability, is further configured to output for transmission, and the first configuration of the second initial downlink BWP is received in the first initial downlink BWP in a system information block (SIB) that carries information for the UE having the first capability and the UE having the second capability, and the second initial downlink BWP, which is dedicated to the UE having the first capability, does not include the CORESET 0 or the CD-SSB.

28. The apparatus according to claim 26, wherein, in order to perform the initial access, at least one processor is configured to acquire a random access preamble during a random access occasion (RO) in the second initial downlink BWP, and the RO has a mapping from a synchronization signal block (SSB) to the CD-SSB in the first initial downlink BWP.

29. The aforementioned at least one processor, The apparatus according to claim 26, wherein the active downlink BWP, which is dedicated to the UE having the first capability, is further configured to output a configuration for non-cell defined SSB (non-CD SSB) for transmission, the non-CD SSB being for at least one of layer 1 (L1) measurement or layer 3 (L3) measurement for the UE having the first capability.

30. The aforementioned at least one processor, The apparatus according to claim 26, further configured to output for transmission system information updates in radio resource control (RRC) signaling in the active downlink BWP dedicated to the UE having the first capability.

Images