Core set 0 for wideband and narrowband ues

Abstract

Method and apparatus for CORESET configuration for broadband and narrowband UEs. The apparatus transmits an indication of a CORESET0 configuration to one or more types of UEs, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving. The apparatus communicates with one or more types of UEs based on at least one of the first CORESET0 configuration or the second CORESET0 configuration. The apparatus may transmit CORESET0 based on the first CORESET0 configuration and with frequency interleaving within each of M RB sets.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. non-provisional patent application No. 18 / 394,670, filed on December 22, 2023, entitled “CORESET0 FOR WIDEBAND ANDNARROWBAND UES”, the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to communication systems, and more specifically to the configuration of control resource sets (CORESET) for broadband and narrowband user equipment (UE). Background Technology

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems employ 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.

[0005] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CWB) program issued by the 3rd 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 associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR are based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

[0006] The following is a simplified summary of one or more aspects to provide a basic understanding of these aspects. This summary is not a comprehensive overview of all conceived aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0007] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a device at a UE. The device may be a processor and / or modem at the UE, or the UE itself. The apparatus receives from a network entity an indication of a Control Resource Set 0 (CORESET0) configuration, the CORESET0 configuration including a first CORESET0 configuration based on one or more resource block (RB) sets or a second CORESET0 configuration without frequency interleaving. The apparatus monitors CORESET0 transmissions based on at least one of the first or second CORESET0 configurations.

[0008] In one aspect of this disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may be a device at a network node. The device may be a processor and / or modem at the network node or the network node itself. The apparatus sends instructions to one or more types of user equipment (UEs) regarding a control resource set 0 (CORESET0) configuration, which includes a first CORESET0 configuration based on one or more resource block (RB) sets or a second CORESET0 configuration without frequency interleaving. The apparatus communicates with one or more types of UEs based on at least one of the first or second CORESET0 configurations.

[0009] To achieve the foregoing and related objectives, one or more aspects may include the features fully described below and specifically pointed out in the claims. The following description and drawings set forth some exemplary features of one or more aspects in detail. However, these features indicate only a few of the various ways in which the principles of the various aspects may be employed. Attached Figure Description

[0010] Figure 1 This is a diagram illustrating an example of a wireless communication system and an access network.

[0011] Figure 2A This is an illustration of an example of the first frame according to various aspects of this disclosure.

[0012] Figure 2BThis is a diagram illustrating examples of downlink (DL) channels within a subframe according to various aspects of this disclosure.

[0013] Figure 2C This is an illustration of an example of a second frame according to various aspects of this disclosure.

[0014] Figure 2D This is a diagram illustrating examples of uplink (UL) channels within a subframe according to various aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating examples of base stations and user equipment (UEs) in an access network.

[0016] Figure 4A An example CORESET0 for a broadband UE is shown.

[0017] Figure 4B An example CORESET0 is shown for both broadband and narrowband UEs.

[0018] Figure 5 Example CORESET0 for broadband and narrowband UEs is illustrated according to various aspects of this disclosure.

[0019] Figure 6 Example CORESET0 for broadband and narrowband UEs is illustrated according to various aspects of this disclosure.

[0020] Figure 7 Example CORESET0 for broadband and narrowband UEs is illustrated according to various aspects of this disclosure.

[0021] Figure 8 Example CORESET0 for broadband and narrowband UEs is illustrated according to various aspects of this disclosure.

[0022] Figure 9 This is a call flow diagram of signaling between the UE and the base station.

[0023] Figure 10 This is a flowchart of a wireless communication method.

[0024] Figure 11 This is a flowchart of a wireless communication method.

[0025] Figure 12 This is a diagram illustrating an example of a hardware implementation used for an example network entity.

[0026] Figure 13 This is a flowchart of a wireless communication method.

[0027] Figure 14 This is a flowchart of a wireless communication method.

[0028] Figure 15 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities. Detailed Implementation

[0029] Wireless communication (e.g., 5G NR) can include different types of UEs, wideband UEs, and narrowband UEs. Wideband UEs, or non-redcap UEs, can support a maximum bandwidth of 100 MHz for Frequency Range (FR) 1 and a maximum bandwidth of 400 MHz for FR2. Narrowband UEs, or redcap UEs, can support a maximum bandwidth of 20 MHz for FR1 and 100 MHz for FR2. Wideband UEs can support CORESET0, which can be configurable or adapted for support by narrowband UEs.

[0030] In some instances, the CORESET0 configuration may be configured to have, for example, a 40 MHz bandwidth with frequency interleaving of R=2 within that 40 MHz bandwidth. Wideband UEs (e.g., non-redcap UEs) can utilize or detect the 40 MHz CORESET0 configuration. However, narrowband UEs (e.g., redcap UEs) may not be configured to utilize or detect the 40 MHz CORESET0 configuration. In some instances, the CORESET0 configuration may be adjusted to support both wideband and narrowband UEs. In such instances, both wideband and narrowband UEs can utilize or detect CORESET0, such that CORESET0 is configured to be shared by both wideband and narrowband UEs. However, in instances where CORESET0 is shared by both wideband and narrowband UEs, CORESET0 is configured within the maximum bandwidth of the narrowband UE, which may result in limited or reduced Physical Downlink Control Channel (PDCCH) capacity. Limited or reduced PDCCH capacity may lead to an increased probability of blocking, and the number of UEs supported in the same time slot may be reduced or limited.

[0031] The aspects presented in this document provide CORESET0 configurations that can be supported by both wideband and narrowband UEs. For example, a CORESET0 configuration may include a first CORESET0 configuration and a second CORESET0 configuration, wherein the first CORESET0 configuration may be configured to support narrowband or redcap UEs, while the second CORESET0 configuration may be configured to support wideband or non-redcap UEs.

[0032] The aspects presented in this document provide CORESET0 configurations that can be supported by both wideband and narrowband UEs. For example, a CORESET0 configuration may include a first CORESET0 configuration and a second CORESET0 configuration, wherein the first CORESET0 configuration may be configured to support narrowband or redcap UEs, while the second CORESET0 configuration may be configured to support wideband or non-redcap UEs.

[0033] The detailed descriptions following, illustrated with reference to the accompanying drawings, describe various configurations and do not represent the only configurations in which the concepts described herein can be practiced. To provide a thorough understanding of the various concepts, the detailed descriptions include specific details. However, these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.

[0034] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “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 system as a whole.

[0035] By way of example, an element, any part of an element, or any combination of elements may be implemented as a “processing system” including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (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 the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

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

[0037] While aspects, implementations, and / or use cases are described herein by way of example, additional or different aspects, implementations, and / or use cases may arise in many different arrangements and scenarios. The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects, implementations, and / or use cases may arise via integrated chip implementations and other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to a use case or application, the described examples may exhibit broad applicability. Aspects, 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 of the technologies described herein. In some practical settings, devices incorporating the described aspects and features may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user equipment, etc., of various sizes, shapes, and configurations.

[0038] The deployment of communication systems such as 5G NR systems can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, network nodes, network entities, network mobility elements, radio access network (RAN) nodes, core network nodes, network elements or network equipment (such as base stations (BS)) or one or more units (or components) performing base station functions can be implemented in aggregated or decomposed architectures. For example, BSs (such as Node B (NB), evolved NB (eNB), NR BS, 5G NB, access point (AP), transmit / receive point (TRP), or cell, etc.) can be implemented as aggregated base stations (also known as standalone BS or monolithic BS) or decomposed base stations.

[0039] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across 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) (i.e., central or distributed units). In some respects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0040] Base station operation or network design can take into account the aggregation characteristics of base station functionality. For example, decomposed base stations can be utilized in Integrated Access Backhaul (IAB) networks, Open Radio Access Networks (O-RAN (such as network configurations initiated by the O-RAN Alliance)), or Virtualized Radio Access Networks (vRAN, also known as Cloud Radio Access Networks (C-RAN)). Decomposition can include distributing functionality across two or more units in various physical locations, as well as virtually distributing the functionality of at least one unit, which enables flexibility in network design. The various units of a decomposed base station or decomposed RAN architecture can be configured to communicate wirelessly with at least one other unit.

[0041] Figure 1Figure 100 illustrates an example of a wireless communication system and access network. The illustrated wireless communication system includes a decomposed base station architecture. The decomposed base station architecture may include one or more CUs 110, which may communicate directly with the core network 120 via a backhaul link, or indirectly with the core network 120 via one or more decomposed base station units, such as a near real-time (near-RT) RAN Intelligent Controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a Service Management and Orchestration (SMO) framework 105, or both. CUs 110 may communicate with one or more DUs 130 via a corresponding midhaul link (such as an F1 interface). DUs 130 may communicate with one or more RUs 140 via a corresponding fronthaul link. RUs 140 may communicate with a corresponding UE 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0042] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO frame 105) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals via wired transmission media or transmit signals to one or more other units. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as RF transceivers) configured to receive signals via wireless transmission media or transmit signals to one or more other units, or both.

[0043] In some aspects, the CU 110 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), or Service Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions managed by the CU 110. The CU 110 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 110 can be implemented to communicate with the DU 130 for network control and signaling, as needed.

[0044] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 140s. In some aspects, DU 130 may at least partially host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, or demodulation) according to functional splits (such as those defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signaling with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0045] Lower-layer functionality can be implemented by one or more RU 140s. In some deployments, an RU140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low-PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, or Physical Random Access Channel (PRACH) extraction and filtering, or both, at least in part based on functional decomposition (such as lower-layer functional decomposition). In this architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration allows the DU130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0046] SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, SMO framework 105 can be configured to interact with a cloud computing platform such as Open Cloud (O-Cloud) 190 to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface such as the O2 interface. Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, SMO framework 105 can communicate with hardware aspects of the 4G RAN, such as Open eNB (O-eNB) 111, via the O1 interface. Additionally, in some implementations, SMO framework 105 can communicate directly with one or more RU 140s via the O1 interface. SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of SMO framework 105.

[0047] The non-RT RIC 115 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence (AI) / machine learning (ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 125. The non-RT RIC 115 can be coupled to or communicate with the near-RT RIC 125, such as via an A1 interface. The near-RT RIC 125 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via data collection and actions through an interface such as an E2 interface, connecting one or more CU 110s, one or more DU 130s, or both, and O-eNBs to the near-RT RIC 125.

[0048] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 125 and may be received from non-network data sources or network functions at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns in performance and use AI / ML models to perform corrective actions via the SMO framework 105 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0049] At least one of CU 110, DU 130, and RU 140 may be referred to as base station 102. Therefore, base station 102 may include one or more of CU 110, DU 130, and RU 140 (each component is indicated by a dashed line to indicate that each component may or may not be included in base station 102). Base station 102 provides UE 104 with an access point to core network 120. Base station 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Small cells include femtocells, picocells, and microcells. A network that includes both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include evolved home node B (eNB) (HeNB), which can provide service to restricted groups referred to as closed subscriber groups (CSGs). The communication link between RU 140 and UE 104 may include uplink (UL) transmission (also known as reverse link) from UE 104 to RU 140 and / or downlink (DL) transmission (also known as forward link) transmission from RU 140 to UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna techniques, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may use one or more carriers. For each direction, the total number of carriers used for transmission can be up to [number missing]. Yx MHz ( x For each carrier allocated in carrier aggregation (of component carriers), base station 102 / UE 104 can use up to [number] carriers. Y A spectrum with a bandwidth of MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.). Carriers may be adjacent to each other or may not be adjacent to each other. Carrier allocation may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). Component carriers may include primary component carriers and one or more secondary component carriers. The primary component carrier may be referred to as the primary cell (PCell) and the secondary component carrier may be referred to as the secondary cell (SCell).

[0050] Some UEs 104 can communicate with each other using device-to-device (D2D) communication link 158. D2D communication link 158 can use DL / UL wireless wide area network (WWAN) spectrum. D2D communication link 158 can use one or more sidelink channels, such as Physical Sidelink Broadcast Channel (PSBCH), Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Control Channel (PSCCH). D2D communication can be performed through various wireless D2D communication systems, such as Bluetooth. ™ (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG), and is based on the IEEE 802.11 standard for Wi-Fi.) ™ (Wi-Fi is a trademark of the Wi-Fi Alliance), LTE, or NR.

[0051] The wireless communication system may also include a Wi-Fi AP 150, which communicates with the UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in an unlicensed spectrum such as 5 GHz. When communicating in unlicensed spectrum, the UE 104 / AP 150 may perform a free channel assessment (CCA) to determine whether the channel is available before communication.

[0052] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc., based on frequency / wavelength. In 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz to 7.125GHz) and FR2 (24.25GHz to 52.6GHz). Although a portion of FR1 is greater than 6GHz, FR1 is generally (interchangeably) referred to as the "sub-6GHz" band in various documents and articles. Similar naming issues sometimes occur with FR2, which is generally (interchangeably) referred to as the "millimeter wave" band in documents and articles, although this is distinct from the Extremely High Frequency (EHF) band (30GHz to 300GHz) designated as "millimeter wave" by the International Telecommunication Union (ITU).

[0053] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-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 the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0054] In view of the above, unless otherwise specifically stated, the term "below 6 GHz" as used herein can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, the term "millimeter wave" as used herein can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, FR4, FR2-2 and / or FR5, or within the EHF band.

[0055] Base station 102 and UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Base station 102 may transmit beamformed signals 182 to UE 104 in one or more transmit directions. UE 104 may receive beamformed signals from base station 102 in one or more receive directions. UE 104 may also transmit beamformed signals 184 to base station 102 in one or more transmit directions. Base station 102 may receive beamformed signals from UE 104 in one or more receive directions. Base station 102 / UE 104 may perform beamforming training to determine the optimal receive and transmit directions for each of base station 102 / UE 104. The transmit and receive directions of base station 102 may be the same or different. The transmit and receive directions of UE 104 may be the same or different.

[0056] Base station 102 may include and / or be referred to as gNB, Node B, eNB, access point, base transceiver, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP, network node, network entity, network equipment, or some other suitable terminology. Base station 102 may be implemented as an integrated access and backhaul (IAB) node, relay node, sidelink node, aggregated (monolithic) base station with baseband units (BBU) (including CU and DU) and RU, or may be implemented as a decomposed base station including one or more of CU, DU, and / or RU. A collection of base stations that may include decomposed base stations and / or aggregated base stations may be referred to as Next Generation (NG) RAN (NG-RAN).

[0057] The core network 120 may include Access and Mobility Management Function (AMF) 161, Session Management Function (SMF) 162, User Plane Function (UPF) 163, Unified Data Management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is the control node that processes signaling between UE 104 and the core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports authentication and key agreement (AKA) credential generation, user identity processing, access authorization, and subscription management. One or more location servers 168 are exemplified as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the following: GMLC 165, LMF 166, Position Determination Entity (PDE), Serving Mobile Location Center (SMLC), or Mobile Location Center (MPC). GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE location information. LMF 166 receives measurement and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may utilize one or more positioning methods to determine the location of UE 104. Positioning UE 104 may involve signal measurements, location estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or the base station 102 serving UE 104. The measured signals may be based on one or more of the following: Satellite Positioning System (SPS) 170 (e.g., one or more of Global Navigation Satellite System (GNSS), Global Positioning System (GPS), Non-Terrestrial Network (NTN) or other satellite positioning / location systems), LTE signals, Wireless Local Area Network (WLAN) signals, Bluetooth signals, Terrestrial Beacon System (TBS), sensor-based information (e.g., barometric pressure sensor, motion sensor), NR Enhanced Cell ID (NR E-CID) method, NR signals (e.g., multiple round-trip time (multiple RTT), DL departure angle (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning) and / or other systems / signals / sensors.

[0058] Examples of UE 104 include cellular phones, smartphones, Session Initiation Protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, GPS devices, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet devices, smart devices, wearable devices, vehicles, electricity meters, air pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some UEs in UE 104 may be referred to as IoT devices (e.g., parking timers, air pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, mobile phone, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network together and / or individually.

[0059] Refer again Figure 1 In some respects, UE 104 may include CORESET component 198, which may be configured to receive an indication of CORESET0 configuration from a network entity, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving; and to monitor CORESET0 transmission based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

[0060] Refer again Figure 1 In some aspects, base station 102 may include CORESET component 199, which may be configured to send an indication of CORESET0 configuration to one or more types of UEs, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving; and to communicate with one or more types of UEs based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

[0061] While the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0062] Figure 2AFigure 200 illustrates an example of the first subframe within a 5G NR frame structure. Figure 2B Figure 230 illustrates an example of a DL channel within a 5G NR subframe. Figure 2C Figure 250 is an example of a second subframe within a 5G NR frame structure. Figure 2D Figure 280 illustrates an example of a UL channel within a 5G NR subframe. The 5G NR frame structure can be Frequency Division Duplex (FDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to either DL or UL) or Time Division Duplex (TDD) (where subframes within a specific set of subcarriers (carrier system bandwidth) are dedicated to both DL and UL). Figure 2A , Figure 2C In the provided example, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible and can be used between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28 respectively, any particular subframe can be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and UL, respectively. Other slot formats 2-61 include a mixture of DL, UL, and flexible symbols. The slot format is configured for the UE via the received Slot Format Indicator (SFI) (dynamically configured via DL Control Information (DCI) or semi-statically / statically configured via Radio Resource Control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

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

[0064]

[0065] Table 1: Parameter Set, SCS, and CP

[0066] For a normal CP (14 symbols / slot), different parameter sets µ 0 through 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For an extended CP, parameter set 2 allows 4 slots per subframe. Therefore, for a normal CP and parameter set µ, there are 14 symbols / slot and 2... µ One time slot / subframe. Subcarrier spacing can be equal to ,in The parameter sets are 0 to 4. Therefore, the subcarrier spacing is 15 kHz for parameter set µ=0 and 240 kHz for parameter set µ=4. The symbol length / duration is negatively correlated with the subcarrier spacing. Figures 2A to 2D Examples of a normal frequency division multiplexing (CP) with 14 symbols per time slot and a parameter set of µ=2 with 4 time slots per subframe are provided. The time slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within the frame set, there may be one or more distinct bandwidth portions (BWPs) of frequency division multiplexing (see [link to relevant documentation]). Figure 2B Each BWP can have a specific set of parameters and CP (normal or extended).

[0067] A resource grid can be used to represent the frame structure. Each time slot consists of a resource block (RB) extending for 12 consecutive subcarriers (also known as a physical RB (PRB)). The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0069] Figure 2B Examples of various DL channels within a subframe of a frame are illustrated. The Physical Downlink Control Channel (PDCCH) carries the DCI within one or more Control Channel Elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE Groups (REGs), each REG comprising 12 coherent REs in the OFDM symbol of the RB. A PDCCH within a BWP may be referred to as a Control Resource Set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during PDCCH monitoring timing 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 on 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 UE 104 to determine subframe / symbol timing and physical layer identification. The Secondary Synchronization Signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the Physical Layer Cell Identifier Group Number and radio frame timing. Based on the Physical Layer Identifier and the Physical Layer Cell Identifier Group Number, the UE can determine the Physical Cell Identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The Physical Broadcast Channel (PBCH), carrying the Master Information Block (MIB), can be logically grouped with the PSS and SSS to form a Synchronization Signal (SS) / PBCH block (also known as an SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the System Frame Number (SFN). The Physical Downlink Shared Channel (PDSCH) carries user data, broadcast system information not transmitted via the PBCH (such as System Information Block (SIB)), and paging messages.

[0070] like Figure 2CAs illustrated, some REs in the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE can transmit DM-RS for the Physical Uplink Control Channel (PUCCH) and DM-RS for the Physical Uplink Shared Channel (PUSCH). The PUSCH DM-RS can be transmitted in the first or first two symbols of the PUSCH. Depending on whether a short or long PUCCH is transmitted and depending on the specific PUCCH format used, the PUCCH DM-RS can be transmitted in different configurations. The UE can transmit a Sounding Reference Signal (SRS). The SRS can be transmitted in the last symbol of a subframe. The SRS can have a comb structure, and the UE can transmit the SRS on one of the comb teeth. The SRS can be used by the base station for channel quality estimation to enable frequency-dependent scheduling of the UL.

[0071] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (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 be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

[0072] Figure 3This is a block diagram illustrating communication between base station 310 and UE 350 in the access network. In the DL, Internet Protocol (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 Adaptation Protocol (SDAP) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-Radio Access Technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with the delivery of upper-layer packet data units (PDUs), error correction via ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs), resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0073] Transmit (TX) processor 316 and receive (RX) processor 370 implement Layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) decoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Each stream can then be mapped to OFDM subcarriers, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domains, and then combined using inverse fast Fourier transform (IFFT) to produce a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream undergoes spatial pre-decoding to generate multiple spatial streams. A channel estimate from channel estimator 374 is used to determine the decoding and modulation scheme, as well as for spatial processing. This channel estimate can be derived from a reference signal transmitted by UE 350 and / or channel condition feedback. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx can use the corresponding spatial stream to modulate a radio frequency (RF) carrier for transmission.

[0074] At UE 350, each receiver 354Rx receives signals via its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides that information to the receive (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 can perform spatial processing on the information to recover any spatial stream destined for UE 350. If multiple spatial streams are destined for UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a Fast Fourier Transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal consists of a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, along with the reference signal, are recovered and demodulated by determining the most probable signal constellation points transmitted by base station 310. These soft decisions can be based on channel estimates calculated by channel estimator 358. Subsequently, the soft decision is decoded and deinterleaved to recover the data and control signals originally transmitted by base station 310 on the physical channel. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0075] The controller / processor 359 may be associated with at least one memory 360 storing program code and data. The at least one memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0076] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, 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 delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

[0077] The TX processor 368 can use the reference signal transmitted from the base station 310 or the channel estimate derived from feedback by the channel estimator 358 to select an appropriate decoding and modulation scheme and facilitate spatial processing. The spatial stream generated by the TX processor 368 can be provided to different antennas 352 via individual transmitters 354Tx. Each transmitter 354Tx can use the corresponding spatial stream to modulate an RF carrier for transmission.

[0078] UL transmission is processed at base station 310 in a manner similar to that described in conjunction with the receiver function at UE 350. Each receiver 318Rx receives signals via its corresponding antenna 320. Each receiver 318Rx recovers the information modulated onto the RF carrier and provides that information to RX processor 370.

[0079] The controller / processor 375 may be associated with at least one memory 376 storing program code and data. The at least one memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operation.

[0080] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to perform coupling. Figure 1 The various aspects of the CORESET component 198.

[0081] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to perform coupling. Figure 1 The various aspects of the CORESET component 199.

[0082] Wireless communications (such as 5G NR) can include different types of UEs, wideband UEs, and narrowband UEs. Wideband UEs or non-redcap UEs can support a maximum bandwidth of 100 MHz for Frequency Range (FR) 1 and a maximum bandwidth of 400 MHz for FR2. Narrowband UEs or redcap UEs can support a maximum bandwidth of 20 MHz for FR1 and 100 MHz for FR2. In some instances, narrowband UEs can include enhanced redcap (eredcap) UEs, which may have a similar maximum bandwidth to redcap UEs. In some instances, eredcap UEs may have a maximum bandwidth of 20 MHz for System Information Blocks (SIBs) or paging in RRC_IDLE or RRC_INACTIVE modes, or a maximum bandwidth of 5 MHz for unicast in RRC_CONNECTED mode. Wideband UEs can support CORESET0, which can be configurable or adapted for support by narrowband UEs.

[0083] In some instances, PBCH or MIB may indicate a CORESET0 configuration with 40MHz, for example, frequency interleaving with R=2 within 40MHz, such as in... Figure 4A As shown in Figure 400, a wideband UE (e.g., a non-redcap UE) can utilize or detect a CORESET0 configuration with 40 MHz. However, a narrowband UE (e.g., a redcap UE or a redcap UE) may not be configured to utilize or detect a CORESET0 configuration with 40 MHz. In some instances, the PBCH or MIB may indicate a CORESET0 configuration with 20 MHz, for example, frequency interleaving with R=2 within 20 MHz, such as in... Figure 4BAs shown in Figure 410. In such instances, both wideband and narrowband UEs can utilize or detect CORESET0 with 20MHz, such that CORESET0 is configured to be shared by both wideband and narrowband UEs. However, in instances where CORESET0 is shared by both wideband and narrowband UEs, CORESET0 is configured within the maximum bandwidth of the narrowband UE, which may result in limited or reduced PDCCH capacity. Limited or reduced PDCCH capacity may lead to an increased probability of blocking, and the number of UEs supported in the same time slot may be reduced or limited. Furthermore, the PDSCH scheduled by the narrowband CORESET0 may be limited or constrained within the maximum bandwidth of the narrowband UE, such as, for example Figure 4B As shown in Figure 410.

[0084] The aspects presented in this document provide CORESET0 configurations that can be supported by both wideband and narrowband UEs. For example, a CORESET0 configuration may include a first CORESET0 configuration and a second CORESET0 configuration, wherein the first CORESET0 configuration may be configured to support narrowband or redcap UEs, while the second CORESET0 configuration may be configured to support wideband or non-redcap UEs.

[0085] In some aspects, the CORESET0 configuration can be configured to support both wideband and narrowband UEs. In some aspects, the wideband CORESET0 can be configured with multiple RB sets. The wideband channel bandwidth can include M×N RBs, which can be divided into M RB sets, and each RB set has N RBs, where M and / or N > 0, and the N RBs are no greater than the maximum bandwidth supported by the narrowband UE. The size of the RB sets according to the number N RBs can be predefined per frequency range or can be configured by the PBCH / MIB. In some aspects, network entities (e.g., base stations) can be configured with a CORESET0 configuration having M RB sets, and each RB set has the same configuration, including at least one of the parameters for SS / PBCH blocks and CORESET multiplexing modes, the number of RBs, the number of symbols, interleaving modes, etc. For example, CORESET0 interleaving can be within each RB set, rather than within the wideband RB set, as shown in example... Figure 5As shown in Figure 500. In some aspects, the number of RB sets M can be indicated by PBCH / MIB (e.g., by adding a new parameter in the CORESET0 table) or by SIB (e.g., in the CSS associated with CORESET0). The CORESET0 RB offset can be defined as the RB offset of the first RB set, which is the RB offset between the lowest RB in the first RB set of CORESET0 and the lowest RB of the SSB. The RB offset of the lowest RB in the m-th RB set relative to the lowest RB of the SSB can be predefined as (RB offset of the first RB set - m). N), where m = 1, ..., M-1. In some aspects, a narrowband UE can be configured to use the first RB set, where the SSB is transmitted within the first RB set. In some aspects, a wideband UE can be configured to use all RB sets in the RB set of CORESET0. The network entity can configure which RB set of CORESET0 can be assigned to a wideband UE (e.g., a non-RedCap UE), as indicated by the RB set bitmap in the associated CSS. In some aspects, the network entity can configure the first RB set for non-redcap UEs (e.g., CORESET0 configuration for narrowband or redcap UEs) via PBCH / MIB. Additional RB sets of CORESET0 can be configured for non-redcap UEs in PBCH / MIB (e.g., parameters of the CORESET0 table) or via SIB (e.g., parameters of the CSS associated with CORESET0).

[0086] In some respects, the broadband CORESET0 configuration can be configured with multiple RB sets, such as, for example, in Figure 6As shown in Figure 600. For example, CORESET0 601 may be configured with PDCCH 602, which schedules PDSCH 608 for narrowband UEs. In this respect, the FDRA of the DCI format for the scheduled PDSCH 608 may be equal to the range of an RB set. The DCI format may be only for PDSCH 608 scheduled within an RB set for narrowband UEs, or it may be common to both wideband and narrowband UEs. In another example, CORESET0 601 may be configured with PDCCH (e.g., 604, 606), which schedules PDSCH (e.g., 610, 612, 614) for wideband UEs. In such instances, the FDRA of the DCI format for the scheduled PDSCH (e.g., 610, 612, 614) may be equal to the range of an RB set. In some aspects, a common PDCCH can be scheduled as a common PDSCH transmitted within a single RB set for both wideband and narrowband UEs, for example, a common SIB scheduled by DCI format 1_0 associated with SI-RNTI. In some aspects, the FDRA of the DCI format for the scheduled PDSCH can be equal to the range of a single RB set, and PDSCH repetition across multiple RB sets can be scheduled directly via a DCI field or via the configuration of the associated CSS using a single PDCCH from a single RB set. Bits in the DCI format for the wideband UE or a bitmap of the RB set in the CSS can be used to indicate repetition. For example, bits in the DCI format can be reserved bits or new fields of the DCI format. In some aspects, the FDRA of the DCI format for the scheduled PDSCH can be scaled across multiple RB sets. A PDCCH (e.g., 606) can schedule PDSCH transmitted across multiple RB sets (e.g., 614) only for wideband UEs (separate from narrowband UEs). For example, the PDCCH used for UE-specific paging and random access channel (RACH) procedures can be scheduled exclusively for the PDSCH of a wideband UE; or the PDCCH used for high data rate MBS can be scheduled exclusively for the PDSCH of a wideband UE. In some respects, to differentiate between PDCCH used for narrowband and wideband UEs, the search space configuration of the DCI format, the RNTI, or the DCI size can be different.

[0087] In some respects, the CORESET0 configuration can be configured to not have frequency interleaving. Wideband UEs can use all RBs for CCE mapping, while narrowband UEs can use a subset of RBs for CCE mapping in a wideband CORESET0 without interleaving, such as... Figure 7 As shown in Figure 700.

[0088] In some respects, the CORESET0 configuration can be configured to not have frequency interleaving, such as, for example Figure 8As shown in Figure 800. For example, CORESET0 801 may be configured with PDCCH 804, which schedules PDSCH 808 for a wideband UE. In such an instance, the FDRA of the DCI format used for the scheduled PDSCH 808 may be equal to the range of the wideband bandwidth, which may be the same as the frequency range of CORESET0 801. In some aspects, PDCCH 804 may schedule PDSCH 808 to be transmitted within the wideband bandwidth. In another example, CORESET0 801 may be configured with PDCCH 802, which schedules PDSCH 806 for a narrowband UE. In such an instance, the FDRA of the DCI format used for the scheduled PDSCH 806 may be equal to the range of the wideband bandwidth or the same as the frequency range of CORESET0 801. However, PDCCH 802 may schedule PDSCH 806 to be transmitted within the narrowband bandwidth. In some respects, the FDRA of the DCI format used for scheduled PDSCHs can be equal to or less than the frequency range of CORESET0 801. The DCI format can schedule PDSCHs transmitted within a narrow bandwidth.

[0089] Figure 9 This is a call flowchart 900 showing the signaling between UE 902 and base station 904. Base station 904 can be configured to provide at least one cell. UE 902 can be configured to communicate with base station 904. For example, in Figure 1 In the context of UE 904, base station 904 may correspond to base station 102, and UE 902 may at least correspond to UE 104. In another example, in Figure 3 In the context of UE 904, UE 904 may correspond to UE 310, and UE 902 may correspond to UE 350.

[0090] At position 906, base station 904 can send instructions for configuring CORESET0, such as in conjunction with... Figures 5 to 8As shown in either of the above. Base station 904 may send an indication of CORESET0 configuration to UE 902. UE 902 may receive an indication of CORESET0 configuration from base station 904. UE 902 may consist of one or more types of UEs. For example, the UE may be a first type of UE or a second type of UE. In some aspects, the first type of UE may be a narrowband UE supporting reduced bandwidth, and the second type of UE may be a wideband UE supporting a bandwidth greater than the reduced bandwidth supported by the first type of UE. CORESET0 configuration may include a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving. In some aspects, the first CORESET0 configuration configures M RB sets, where each RB set in the M RB sets includes N RBs, where M and / or N > 0. In some respects, one RB set (such as the first RB set) in the M RB sets can be configured for a first type of UE that supports reduced bandwidth similar to or greater than that of the N RBs in the first RB set, and one or more RB sets in the M RB sets can be configured for a second type of UE that supports reduced bandwidth similar to or greater than that of the M RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than their non-reduced bandwidth. SSBs shared by the first type of UE and the second type of UE can be transmitted within the RB set of CORESET0 used by the first type of UE. The first CORESET0 configuration indicates that the first RB set can be used by the first type of UE, and one or more RB sets in the M RB sets can be used by the second type of UE. In some aspects, the frequency domain resource allocation (FDRA) for the PDCCH that schedules the PDSCH can be based on the range of the first RB set in the M RB sets, where the PDSCH can be scheduled within the first RB set in the M RB sets. In such instances, the PDCCH can be monitored by both the first type of UE and the second type of UE. Scheduled PDSCHs within the first RB set can be repeated in other RB sets in the M RB sets within the same time slot. In some aspects, PDSCH repetition can be configured by the CORESET0 configuration via at least one of the Master Information Block (MIB), Physical Broadcast Channel (PBCH), or can be indicated via the PDCCH. In some aspects, the FDRA for PDCCH scheduling PDSCH can be based on a range of M RB sets, where the PDSCH can be scheduled across multiple RB sets within the M RB sets. In such instances, the PDCCH can be monitored by a second type of UE using a search space configuration, RNTI, or DCI format size separate from that of a first type of UE. In some aspects, the CORESET0 configuration can be based on a second CORESET0 configuration without frequency interleaving, such that the control channel element (CCE) indexes of the CORESET0 PDCCH are sequentially mapped to the frequency resources of the CORESET0 configuration, where a subset of RBs within the second CORESET0 configuration is configured for a first type of UE that supports reduced bandwidth, and all RBs within the second CORESET0 configuration are configured for a second type of UE that supports non-reduced bandwidth. In some aspects, the FDRA for PDCCH scheduling PDSCH can be based on a range of RBs configured for the CORESET0 configuration, where the PDSCH is scheduled across one or more RBs. In such instances, the PDCCH can be monitored by a second type of UE using a search space configuration, RNTI or DCI format size separate from that of the first type of UE. In some aspects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of RBs configured for the CORESET0 configuration, where the PDSCH is scheduled within a subset of RBs. In such instances, the PDCCH can be monitored by both a first type of UE and a second type of UE.In some respects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of a subset of RBs, where the PDSCH is scheduled within that subset. In such instances, the PDCCH can be monitored by both Type 1 and Type 2 UEs.

[0091] At 908, UE 902 can monitor CORESET0 transmissions from base station 904. CORESET0 transmissions can be based on at least one of a first CORESET0 configuration or a second CORESET0 configuration, such as in combination. Figures 5 to 8 As shown in either of them.

[0092] At point 910, base station 904 can send a CORESET0 transmission to UE 902. UE 902 can receive the CORESET0 transmission from base station 904. The CORESET0 transmission can be based on at least one of a first CORESET0 configuration or a second CORESET0 configuration, such as in combination. Figures 5 to 8 As shown in either of them.

[0093] At 912, UE 902 and base station 904 can communicate with each other based on either a first CORESET0 configuration or a second CORESET0 configuration, such as in combination. Figures 5 to 8 As shown in either of them.

[0094] Figure 10 This is a flowchart 1000 of a method for performing wireless communication at a network entity. The method can be performed by a base station (e.g., base station 102; network entities 1202, 1502). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. This method allows for CORESET configuration for both broadband and narrowband UEs.

[0095] At position 1002, the network entity can send instructions for the CORESET0 configuration, such as in conjunction with... Figures 5 to 8As shown in either of the above. For example, 1002 can be performed by the CORESET component 199 of network entity 1202. The network entity can send an indication of CORESET0 configuration to one or more types of UEs. CORESET0 configuration may include a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving. In some aspects, the first CORESET0 configuration configures M RB sets, wherein each RB set in the M RB sets includes N RBs, where M and / or N > 0. In some aspects, one RB set in the M RB sets (such as the first RB set) may be configured for a first type of UE that supports reduced bandwidth similar to or greater than the bandwidth of the N RBs in the first RB set, and one or more RB sets in the M RB sets are configured for a second type of UE that supports reduced bandwidth similar to or greater than the bandwidth of the N RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than their non-reduced bandwidth. A first CORESET0 configuration indicates that a first RB set can be used for a first type of UE, and one or more RB sets in the M RB sets can be used for a second type of UE. In some aspects, the frequency domain resource allocation (FDRA) for the PDCCH that schedules the PDSCH can be based on the range of the first RB set in the M RB sets, where the PDSCH can be scheduled within the first RB set in the M RB sets. In such instances, the PDCCH can be monitored by both the first and second type of UEs. The scheduled PDSCH within the first RB set can be repeated in other RB sets in the M RB sets within the same time slot. In some aspects, PDSCH repetition can be configured by the CORESET0 configuration via at least one of the Master Information Block (MIB), Physical Broadcast Channel (PBCH), or can be indicated via the PDCCH. In some aspects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of the M RB sets, where the PDSCH can be scheduled across multiple RB sets in the M RB sets. In such instances, the PDCCH can be monitored by a second type of UE using a search space configuration, a Radio Network Temporary Identifier (RNTI) or DCI format size separate from that of the first type of UE. In some aspects, the CORESET0 configuration can be based on a second CORESET0 configuration without frequency interleaving, such that the control channel element (CCE) indexes of the CORESET0 PDCCH are sequentially mapped to the frequency resources of the CORESET0 configuration, wherein a subset of RBs within the second CORESET0 configuration is configured for a first type of UE that supports reduced bandwidth, and all RBs within the second CORESET0 configuration are configured for a second type of UE that supports non-reduced bandwidth. In some aspects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of RBs configured for the CORESET0 configuration, wherein the PDSCH is scheduled across one or more RBs. In such instances, the PDCCH can be monitored by a second type of UE using a search space configuration, a search space configuration, and an RNTI or DCI format size separate from that of the first type of UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH can be based on the range of RBs configured for CORESET0, where the PDSCH is scheduled within a subset of RBs. In such instances, the PDCCH can be monitored by a first-type UE and a second-type UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH can be based on the range of a subset of RBs, where the PDSCH is scheduled within a subset of RBs.In such instances, the PDCCH can be monitored by both Type 1 and Type 2 UEs.

[0096] At point 1004, the network entity can communicate with one or more types of UEs. For example, 1004 can be performed by the CORESET component 199 of network entity 1202. The network entity can communicate with one or more types of UEs based on at least one of a first CORESET0 configuration or a second CORESET0 configuration, such as in combination. Figures 5 to 8 As shown in either of them.

[0097] Figure 11 This is a flowchart 1100 of a method for performing wireless communication at a network entity. This method can be performed by a base station (e.g., base station 102; network entities 1202, 1502). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. This method allows for CORESET configuration for both broadband and narrowband UEs.

[0098] At 1102, the network entity can send instructions on the CORESET0 configuration, such as in conjunction with Figures 5 to 8 As shown in either of the above. For example, 1102 can be performed by the CORESET component 199 of network entity 1202. The network entity can send an indication of CORESET0 configuration to one or more types of UEs. CORESET0 configuration may include a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving. In some aspects, the first CORESET0 configuration configures M RB sets, wherein each RB set in the M RB sets includes N RBs, where M and / or N > 0. In some aspects, the first RB set in the M RB sets may be configured for a first type of UE that supports reduced bandwidth similar to or greater than the bandwidth of the N RBs in the first RB set, and one or more RB sets in the M RB sets may be configured for a second type of UE that supports reduced bandwidth similar to or greater than the bandwidth of the N RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than their non-reduced bandwidth. A first CORESET0 configuration indicates that a first RB set can be used for a first type of UE, and one or more RB sets in the M RB sets can be used for a second type of UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH can be based on the range of the first RB set in the M RB sets, where the PDSCH can be scheduled within the first RB set in the M RB sets. In such instances, the PDCCH can be monitored by both the first and second type of UEs. Scheduled PDSCHs within the first RB set can be repeated in other RB sets within the M RB sets in the same time slot. In some aspects, PDSCH repetition can be configured by the CORESET0 configuration via at least one of the MIB, PBCH, or can be indicated via the PDCCH. In some aspects, the FDRA for a PDCCH that schedules a PDSCH can be based on the range of the M RB sets, where the PDSCH can be scheduled across multiple RB sets in the M RB sets. In such instances, the PDCCH can be monitored by a second type of UE using a search space configuration separate from the search space configuration, RNTI or DCI format size, and RNTI or DCI format size of the first type of UE. In some aspects, the CORESET0 configuration can be based on a second CORESET0 configuration without frequency interleaving, such that the CCE index of the CORESET0 PDCCH is sequentially mapped to the frequency resources of the CORESET0 configuration, wherein a subset of RBs within the second CORESET0 configuration is configured for a first type of UE that supports reduced bandwidth, and all RBs within the second CORESET0 configuration are configured for a second type of UE that supports non-reduced bandwidth. In some aspects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of RBs configured for the CORESET0 configuration, wherein the PDSCH is scheduled across one or more RBs. In such instances, the PDCCH can be monitored by a second type of UE using a search space configuration separate from the search space configuration, RNTI or DCI format size, and RNTI or DCI format size of the first type of UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH can be based on the range of an RB configured for CORESET0, where the PDSCH is scheduled within a subset of RBs. In such instances, the PDCCH can be monitored by both a first-type UE and a second-type UE.

[0099] At 1104, the network entity may send a CORESET0 transmission. For example, 1104 may be performed by the CORESET component 199 of network entity 1202. The network entity may send the CORESET0 transmission based on a first CORESET0 configuration and with frequency interleaving within each of the M RB sets, as combined with Figures 5 to 8 As shown in either of them. In some aspects, network entities may send CORESET0 transmissions based on a second CORESET0 configuration.

[0100] At 1106, the network entity can communicate with one or more types of UEs. For example, 1106 can be performed by the CORESET component 199 of network entity 1202. The network entity can communicate with one or more types of UEs based on at least one of a first CORESET0 configuration or a second CORESET0 configuration, such as in combination. Figures 5 to 8 As shown in either of them.

[0101] Figure 12Figure 1200 illustrates an example of a hardware implementation for network entity 1202. Network entity 1202 may be a BS, a component of a BS, or implement BS functionality. Network entity 1202 may include at least one of CU 1210, DU 1230, or RU 1240. For example, depending on the layer functionality processed by component 199, network entity 1202 may include: CU 1210; both CU 1210 and DU 1230; each of CU 1210, DU 1230, and RU 1240; DU 1230; both DU 1230 and RU 1240; or RU 1240. CU 1210 may include at least one CU processor 1212. CU processor 1212 may include on-chip memory 1212'. In some aspects, CU 1210 may also include an additional memory module 1214 and a communication interface 1218. CU 1210 communicates with DU 1230 via a midhaul link such as an F1 interface. DU 1230 may include at least one DU processor 1232. DU processor 1232 may include on-chip memory 1232'. In some aspects, DU 1230 may also include an additional memory module 1234 and a communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 may include at least one RU processor 1242. RU processor 1242 may include on-chip memory 1242'. In some aspects, RU 1240 may also include an additional memory module 1244, one or more transceivers 1246, an antenna 1280, and a communication interface 1248. RU 1240 communicates with UE 104. On-chip memories 1212', 1232', 1242' and additional memory modules 1214, 1234, 1244 may each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1212, 1232, and 1242 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor, the software causes that processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor while executing the software.

[0102] As discussed above, component 199 may be configured to send an indication of a CORESET0 configuration to one or more types of UEs, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving; and to communicate with one or more types of UEs based on at least one of the first CORESET0 configuration or the second CORESET0 configuration. Component 199 may be located within one or more processors of one or more of CU 1210, DU 1230, and RU 1240. Component 199 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. Network entity 1202 may include a variety of components configured for various functions. In one configuration, network entity 1202 may include components for transmitting an indication of a CORESET0 configuration to one or more types of UEs, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving. The network entity includes components for communicating with one or more types of UEs based on at least one of the first or second CORESET0 configurations. The network entity also includes components for transmitting CORESET0 based on the first CORESET0 configuration and having frequency interleaving within each of the M RB sets. This component may be component 199 of network entity 1202 configured to perform the functions described therein. As described above, network entity 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, this component may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions described therein.

[0103] Figure 13 This is a flowchart 1300 of a wireless communication method. This method can be performed by a UE (e.g., UE 104; device 1504). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. This method allows for CORESET configuration for both broadband and narrowband UEs.

[0104] At 1302, the UE can receive instructions on the CORESET0 configuration, such as in conjunction with Figures 5 to 8As shown in either of the above. For example, 1302 may be performed by the CORESET component 198 of device 1504. The UE may receive an indication of CORESET0 configuration from a network entity. CORESET0 configuration may include a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving. In some aspects, the first CORESET0 configuration may include M RB sets, wherein each RB set in the M RB sets includes N RBs. In some aspects, the first CORESET0 configuration may include frequency interleaving within each RB set in the M RB sets. In some aspects, the first CORESET0 configuration may indicate that the first RB set can be configured for a first type of UE that supports reduced bandwidth similar to or greater than the bandwidth of the N RBs in the first RB set, and one or more RB sets in the M RB sets are configured for a second type of UE that supports reduced bandwidth similar to or greater than the bandwidth of the N RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than the non-reduced bandwidth. In such instances, the UE can monitor one or more RB sets in the first RB set or the M RB sets based on the capabilities supported by the UE. In some aspects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of the first RB set in the M RB sets, where the PDSCH is scheduled within the first RB set in the M RB sets. In such instances, the PDCCH can be monitored by a first type of UE and a second type of UE, where the first type of UE supports reduced bandwidth and the second type of UE supports non-reduced bandwidth. In such aspects, the UE can monitor PDSCH duplication within multiple RB sets in the M RB sets within the CORESET0 transmission. In some aspects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of the M RB sets, where the PDSCH is scheduled across multiple RB sets in the M RB sets. In such instances, the UE may include a second type of UE, and the PDCCH is monitored using a search space configuration, RNTI or DCI format size separate from the search space configuration, RNTI or DCI format size of the first type of UE.

[0105] At point 1304, the UE can monitor CORESET0 transmission. For example, 1304 can be performed by the CORESET component 198 of device 1504. The UE can monitor CORESET0 transmission from a network entity. CORESET0 transmission can be based on at least one of a first CORESET0 configuration or a second CORESET0 configuration, such as in combination. Figures 5 to 8As shown in either of the above. In some aspects, to monitor CORESET0 transmissions, the UE may monitor a subset of RBs or one or more RBs within a second CORESET0 configuration based on the bandwidth supported by the UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH may be based on the range of RBs configured for CORESET0 transmissions, where the PDSCH is scheduled across one or more RBs. In such instances, the UE may be a second type of UE and monitor the PDCCH using a search space configuration, RNTI or DCI format size separate from that of a first type of UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH may be based on the range of RBs configured for CORESET0 transmissions, where the PDSCH is scheduled within a subset of RBs. In such aspects, the PDCCH may be monitored by both a first type of UE and a second type of UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH may be based on the range of a subset of RBs, where the PDSCH is scheduled within a subset of RBs. In such instances, the PDCCH can be monitored by both Type 1 and Type 2 UEs.

[0106] Figure 14 This is a flowchart 1400 of a wireless communication method. This method can be performed by a UE (e.g., UE 104; device 1504). One or more of the illustrated operations can be omitted, interchanged, or performed simultaneously. This method allows for CORESET configuration for both broadband and narrowband UEs.

[0107] At 1402, the UE can receive instructions on the CORESET0 configuration, such as in conjunction with Figures 5 to 8 As shown in either of the above. For example, 1402 may be performed by the CORESET component 198 of device 1504. The UE may receive an indication of CORESET0 configuration from a network entity. CORESET0 configuration may include a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving. In some aspects, the first CORESET0 configuration may include M RB sets, wherein each RB set in the M RB sets includes N RBs. In some aspects, the first CORESET0 configuration may include frequency interleaving within each RB set in the M RB sets. In some aspects, the first CORESET0 configuration may indicate that the first RB set can be configured for a first type of UE that supports reduced bandwidth similar to or greater than the bandwidth of the N RBs in the first RB set, and one or more RB sets in the M RB sets are configured for a second type of UE that supports reduced bandwidth similar to or greater than the bandwidth of the N RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than the non-reduced bandwidth. In such instances, the UE can monitor one or more RB sets in the first RB set or the M RB sets based on the capabilities supported by the UE. In some aspects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of the first RB set in the M RB sets, where the PDSCH is scheduled within the first RB set in the M RB sets. In such instances, the PDCCH can be monitored by a first type of UE and a second type of UE, where the first type of UE supports reduced bandwidth and the second type of UE supports non-reduced bandwidth. In such aspects, the UE can monitor PDSCH duplication within multiple RB sets in the M RB sets within the CORESET0 transmission. In some aspects, the FDRA for the PDCCH that schedules the PDSCH can be based on the range of the M RB sets, where the PDSCH is scheduled across multiple RB sets in the M RB sets. In such instances, the UE may include a second type of UE, and the PDCCH is monitored using a search space configuration, RNTI or DCI format size separate from the search space configuration, RNTI or DCI format size of the first type of UE.

[0108] At 1404, the UE can monitor CORESET0 transmission. For example, 1404 can be performed by CORESET component 198 of device 1504. The UE can monitor CORESET0 transmission from a network entity. CORESET0 transmission can be based on at least one of a first CORESET0 configuration or a second CORESET0 configuration, such as in combination. Figures 5 to 8As shown in either of the above. In some aspects, to monitor CORESET0 transmissions, the UE may monitor a subset of RBs or one or more RBs within a second CORESET0 configuration based on the bandwidth supported by the UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH may be based on the range of RBs configured for CORESET0 transmissions, where the PDSCH is scheduled across one or more RBs. In such instances, the UE may be a second type of UE and monitor the PDCCH using a search space configuration, RNTI or DCI format size separate from that of a first type of UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH may be based on the range of RBs configured for CORESET0 transmissions, where the PDSCH is scheduled within a subset of RBs. In such aspects, the PDCCH may be monitored by both a first type of UE and a second type of UE. In some aspects, the FDRA for a PDCCH that schedules a PDSCH may be based on the range of a subset of RBs, where the PDSCH is scheduled within a subset of RBs. In such instances, the PDCCH can be monitored by both Type 1 and Type 2 UEs.

[0109] At point 1406, the UE can communicate with a network entity. For example, 1406 can be performed by the CORESET component 198 of device 1504. The UE can communicate with the network entity based on at least one of a first CORESET0 configuration or a second CORESET0 configuration, such as in combination. Figures 5 to 8 As shown in either of them.

[0110] Figure 15Figure 1500 illustrates 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 aspects, device 1504 may include at least one cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., cellular RF transceivers). Cellular baseband processor 1524 may include at least one on-chip memory 1524'. In some aspects, device 1504 may also include one or more Subscriber Identity Module (SIM) cards 1520 and at least one application processor 1506 coupled to a Secure Digital Card (SD) card 1508 and a screen 1510. Application processor 1506 may include on-chip memory 1506'. In some aspects, device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), gyroscope, and / or accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power supply 1530, and / or a camera 1532. Bluetooth module 1512, WLAN module 1514, and SPS module 1516 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1512, WLAN module 1514, and SPS module 1516 may include their own dedicated antennas and / or communicate using antenna 1580. Cellular baseband processor 1524 communicates with UE 104 and / or RU associated with network entity 1502 via transceiver 1522 through one or more antennas 1580. Cellular baseband processor 1524 and application processor 1506 may each include computer-readable media / memory 1524', 1506' respectively. Additional memory module 1526 may also be considered as computer-readable media / memory. Each computer-readable media / memory 1524', 1506', 1526 may be non-transitory. Cellular baseband processor 1524 and application processor 1506 are each responsible for general processing, including the execution of software stored on the computer-readable media / memory. When executed by cellular baseband processor 1524 / application processor 1506, the software causes cellular baseband processor 1524 / application processor 1506 to perform the various functions described above. Cellular baseband processor 1524 and application processor 1506 are configured to perform the various functions described above based at least in part on information stored in memory.That is, the cellular baseband processor 1524 and application processor 1506 can be configured to perform a first subset of the various functions described above without information stored in memory, and can be configured to perform a second subset of the various functions described above based on information stored in memory. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 during software execution. The cellular baseband processor 1524 / application processor 1506 can be a component of the UE 350 and can include at least one of a memory 360 and / or at least one of a TX processor 368, an RX processor 356, and a controller / processor 359. In one configuration, the device 1504 can be at least one processor chip (modem and / or application) and includes only the cellular baseband processor 1524 and / or application processor 1506, while in another configuration, the device 1504 can be the entire UE (e.g., see below). Figure 3 The UE350 includes an additional module of the device 1504.

[0111] As discussed above, component 198 may be configured to receive an indication of a CORESET0 configuration from a network entity, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving; and to monitor CORESET0 transmission based on at least one of the first or second CORESET0 configuration. Component 198 may reside within cellular baseband processor 1524, application processor 1506, or both cellular baseband processor 1524 and application processor 1506. Component 198 may be one or more hardware components specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, apparatus 1504 may include a variety of components configured for various functions. In one configuration, device 1504 (and specifically cellular baseband processor 1524 and / or application processor 1506) may include components for receiving an indication of a CORESET0 configuration from a network entity, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving. The device includes components for monitoring CORESET0 transmissions based on at least one of the first or second CORESET0 configurations. The device also includes components for communicating with the network entity based on at least one of the first or second CORESET0 configurations. This component may be component 198 of device 1504 configured to perform the functions described therein. As described above, device 1504 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, the component may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions described therein.

[0112] It should be understood that the specific order or hierarchy of the boxes in the disclosed process / flowcharts is merely an example of the exemplary method. It should be understood that the specific order or hierarchy of the boxes in the process / flowcharts may be rearranged based on design preferences. Furthermore, some boxes may be combined or omitted. The appended method claims present the elements of various boxes in a sample order, but are not limited to the given specific order or hierarchy.

[0113] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein but should be given the full scope consistent with the language of the claims. Unless specifically stated otherwise, references to elements in the singular form do not mean “one and only one” but rather “one or more.” Terms such as “if,” “when,” and “simultaneously” do not imply a direct temporal relationship or reaction. That is, these phrases, such as “when,” do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply suggest that if a condition is met, then the action will occur, without requiring a specific or immediate time limit for the occurrence of the action. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or superior to other aspects. Unless otherwise specifically stated, the term “some” refers to one or more. Combinations such as "at least one of A, B, or C", "one or more of A, B, or C", "at least one of A, B, and C", "one or more of A, B, and C", and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, and may include multiple 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" can be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a collection of elements with a number of one or more elements. Therefore, for a set of X, X will include one or more elements. When at least one processor is configured to execute a set of functions, the at least one processor is configured to execute the set of functions individually or in any combination. Therefore, each of the at least one processor can be configured to perform a specific subset of the set of functions, wherein the subset is the complete set, a suitable subset of the set, or an empty subset of the set. If the first device receives data from or sends data to the second device, data can be received / sent directly between the first and second devices, or indirectly between the first and second devices through a set of devices. A device configured to "output" data (such as transmission, signaling, or messaging) can, for example, transmit the data using a transceiver, or can transmit the data to the device that sent the data. A device configured to "receive" data (such as transmission, signaling, or messaging) can, for example, receive the data using a transceiver, or can obtain the data from the device that received the data.Information stored in memory includes instructions and / or data. All structural and functional equivalents of the elements throughout the various aspects described herein that are known to or will later be known to a person skilled in the art are expressly incorporated herein by reference and are covered by the claims. Furthermore, nothing disclosed herein is intended to be offered to the public, whether or not such disclosure is explicitly recited in the claims. The terms “module,” “mechanism,” “element,” “device,” etc., cannot replace the word “component.” Therefore, no claim element will be construed as a functional component unless the element is explicitly described using the phrase “component for…”.

[0114] As used herein, the phrase “based on” should not be interpreted as referring 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” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless otherwise specified.

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

[0116] Aspect 1 is a method for wireless communication at a network entity, the method comprising: sending an indication of a CORESET0 configuration to one or more types of UEs, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving; and communicating with the one or more types of UEs based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

[0117] Aspect 2, according to the method of aspect 1, further includes: the first CORESET0 configuration configuring M RB sets, wherein each RB set in the M RB sets includes N RBs.

[0118] Aspect 3 is the method according to any one of aspects 1 and 2, the method further comprising: for communicating with the one or more types of UEs, the method further comprising: transmitting CORESET0 based on the first CORESET0 configuration and having the frequency interleaving in each of the M RB sets.

[0119] Aspect 4 is the method according to any one of Aspects 1 to 3, the method further comprising: a first set of RBs in the M RB sets being configured for a first type of UE, the first type of UE supporting reduced bandwidth similar to or greater than that of N RBs in the first RB set; and one or more RB sets in the M RB sets being configured for a second type of UE, the second type of UE supporting reduced bandwidth similar to or greater than that of N RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than their non-reduced bandwidth, wherein the first CORESET0 configuration indicates that the first RB set is used for the first type of UE and one or more RB sets in the M RB sets are used for the second type of UE.

[0120] Aspect 5 is the method according to any one of aspects 1 to 4, the method further comprising: FDRA for a PDCCH that schedules a PDSCH based on a range of a first RB set in the M RB sets, wherein the PDSCH is scheduled within the first RB set in the M RB sets.

[0121] Aspect 6 is the method according to any one of aspects 1 to 5, the method further comprising: the PDCCH being monitored by a first type of UE and a second type of UE.

[0122] Aspect 7 is the method according to any one of aspects 1 to 6, the method further comprising: the scheduled PDSCH within the first RB set is repeated in other RB sets of M RB sets in the same time slot, wherein the PDSCH repetition is configured by the CORESET0 configuration via MIB, PBCH, or indicated via the PDCCH.

[0123] Aspect 8 is the method according to any one of aspects 1 to 7, the method further comprising: FDRA for scheduling PDSCH based on the range of the M RB sets, wherein the PDSCH is scheduled across multiple RB sets in the M RB sets, wherein the PDCCH is monitored by a second type of UE using a search space configuration, RNTI or DCI format size separate from that of a first type of UE.

[0124] Aspect 9 is the method according to any one of aspects 1 to 8, the method further comprising: the CORESET0 configuration based on a second CORESET0 configuration without the frequency interleaving, such that the CCE indexes of the CORESET0 PDCCH are sequentially mapped to the frequency resources of the CORESET0 configuration, wherein a subset of RBs within the second CORESET0 configuration is configured for a first type of UE that supports reduced bandwidth, and all RBs within the second CORESET0 configuration are configured for a second type of UE that supports non-reduced bandwidth.

[0125] Aspect 10 is the method according to any one of aspects 1 to 9, the method further comprising: FDRA for scheduling PDSCH of PDCCH based on the range of RBs configured for the CORESET0 configuration, wherein the PDSCH is scheduled across one or more RBs.

[0126] Aspect 11 is the method according to any one of aspects 1 to 10, the method further comprising: the PDCCH being monitored by the second type of UE using a search space configuration, RNTI or DCI format size separate from the search space configuration, RNTI or DCI format size of the first type of UE.

[0127] Aspect 12 is the method according to any one of aspects 1 to 11, the method further comprising: FDRA for scheduling PDSCH based on the range of RBs configured for the CORESET0 configuration, wherein the PDSCH is scheduled within a subset of the RBs, wherein the PDCCH is monitored by the first type of UE and the second type of UE.

[0128] Aspect 13 is the method according to any one of aspects 1 to 12, the method further comprising: FDRA for scheduling PDSCH based on the range of the RB subset, wherein the PDSCH is scheduled within the RB subset, wherein the PDCCH is monitored by the first type of UE and the second type of UE.

[0129] Aspect 14 is an apparatus for wireless communication at a network entity, the apparatus including at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 1 to 13.

[0130] Aspect 15 is an apparatus for wireless communication at a network entity, the apparatus including components for implementing any one of aspects 1 to 13.

[0131] Aspect 16 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 13.

[0132] Aspect 17 is a method for wireless communication at a UE, the method comprising: receiving from a network entity an indication of a CORESET0 configuration, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without frequency interleaving; and monitoring CORESET0 transmission based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

[0133] Aspect 18 is the method according to aspect 17, the method further comprising: the first CORESET0 configuration comprising M RB sets, wherein each RB set in the M RB sets comprises N RBs.

[0134] Aspect 19 is the method according to any one of aspects 17 and 18, the method further comprising: the first CORESET0 configuration including the frequency interleaving in each of the M RB sets.

[0135] Aspect 20 is the method according to any one of Aspects 17 to 19, wherein the first CORESET0 configuration indicates that a first RB set is configured for a first type of UE, the first type of UE supporting reduced bandwidth similar to or greater than that of N RBs in the first RB set, and one or more RB sets in the M RB sets are configured for a second type of UE, the second type of UE supporting reduced bandwidth similar to or greater than that of M RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than their non-reduced bandwidth, wherein monitoring the CORESET0 transmission includes: monitoring one or more RB sets in the first RB set or the M RB sets based on the capabilities supported by the UE.

[0136] Aspect 21 is the method according to any one of aspects 17 to 20, the method further comprising: FDRA for scheduling PDSCH of PDCCH based on the range of a first RB set in the M RB sets, wherein the PDSCH is scheduled within the first RB set in the M RB sets, wherein the PDCCH is monitored by a first type of UE and a second type of UE.

[0137] Aspect 22 is the method according to any one of aspects 17 to 21, the method further comprising: monitoring the CORESET0 transmission including monitoring PDSCH repetitions within multiple RB sets in the M RB sets.

[0138] Aspect 23 is the method according to any one of aspects 17 to 22, the method further comprising: FDRA for scheduling PDSCH based on the range of the M RB sets, wherein the PDSCH is scheduled across multiple RB sets in the M RB sets, wherein the UE is a second type of UE, and the PDCCH is monitored using a search space configuration, RNTI or DCI format size separate from the search space configuration, RNTI or DCI format size of the first type of UE.

[0139] Aspect 24 is the method according to any one of aspects 17 to 23, the method further comprising: monitoring the CORESET0 transmission including monitoring a subset of RBs or one or more RBs within the second CORESET0 configuration based on bandwidth supported by the UE.

[0140] Aspect 25 is the method according to any one of aspects 17 to 24, the method further comprising: FDRA for scheduling PDSCH of PDCCH based on the range of RBs configured for CORESET0 transmission, wherein the PDSCH is scheduled across the one or more RBs.

[0141] Aspect 26 is the method according to any one of aspects 17 to 25, the method further comprising: the UE is a second type of UE, and the PDCCH is monitored using a search space configuration, RNTI or DCI format size separate from the search space configuration, RNTI or DCI format size of the first type of UE.

[0142] Aspect 27 is the method according to any one of aspects 17 to 26, the method further comprising: FDRA for scheduling PDSCH of PDCCH based on the range of RBs configured for transmission of the CORESET0, wherein the PDSCH is scheduled within a subset of the RBs, wherein the PDCCH is monitored by a first type of UE and a second type of UE.

[0143] Aspect 28 is the method according to any one of aspects 17 to 27, the method further comprising: FDRA for scheduling PDSCH based on the range of the RB subset, wherein the PDSCH is scheduled within the RB subset, wherein the PDCCH is monitored by a first type of UE and a second type of UE.

[0144] Aspect 29 is the method according to any one of aspects 17 to 28, the method further comprising: communicating with the network entity based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

[0145] Aspect 30 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one processor coupled to a memory; and at least one transceiver configured to implement any one of aspects 17 to 29.

[0146] Aspect 31 is an apparatus for wireless communication at a UE, the apparatus comprising: components for implementing any one of aspects 17 to 29.

[0147] Aspect 32 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 17 to 29.

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the device to: Sending an instruction for a control resource set 0 (CORESET0) configuration to one or more types of user equipment (UE), the control resource set 0 (CORESET0) configuration including a first CORESET0 configuration based on one or more resource block (RB) sets or a second CORESET0 configuration without frequency interleaving; as well as The communication is made with the one or more types of UEs based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

2. The apparatus according to claim 1, further comprising: A transceiver, coupled to the at least one processor, is configured to: Send the indication of the CORESET0 configuration to one or more types of UEs, the CORESET0 configuration including a first CORESET0 configuration based on one or more RB sets or a second CORESET0 configuration without the frequency interleaving; as well as Communicating with one or more types of UEs based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

3. The apparatus of claim 1, wherein the first CORESET0 configuration configures M sets of RBs, wherein each of the M sets of RBs comprises N RBs.

4. The apparatus of claim 3, wherein, in order to communicate with the one or more types of UEs, the at least one processor is configured to: Based on the first CORESET0 configuration and with the frequency interleaving in each of the M RB sets, CORESET0 is transmitted.

5. The apparatus of claim 3, wherein a first set of RBs in the M RB sets is configured for a first type of UE, the first type of UE supporting reduced bandwidth similar to or greater than the bandwidth of N RBs in the first RB set, and one or more RB sets in the M RB sets are configured for a second type of UE, the second type of UE supporting reduced bandwidth similar to or greater than the bandwidth of N RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than their non-reduced bandwidth, wherein the first CORESET0 configuration indicates that the first RB set is used for the first type of UE and one or more RB sets in the M RB sets are used for the second type of UE.

6. The apparatus of claim 3, wherein the frequency domain resource allocation (FDRA) of the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on the range of a first RB set in the M RB sets, wherein the PDSCH is scheduled within the first RB set in the M RB sets.

7. The apparatus of claim 6, wherein the PDCCH is monitored by a first type of UE and a second type of UE.

8. The apparatus of claim 6, wherein the scheduled PDSCH within the first RB set is repeated in other RB sets of the M RB sets in the same time slot, wherein the PDSCH repetition is configured by the CORESET0 via the Master Information Block (MIB), Physical Broadcast Channel (PBCH), or indicated via the PDCCH.

9. The apparatus of claim 3, wherein the frequency domain resource allocation (FDRA) of the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on the range of the M RB sets, wherein the PDSCH is scheduled across multiple RB sets in the M RB sets, wherein the PDCCH is monitored by a second type of UE using a search space configuration, RNTI or DCI format size that is separate from the search space configuration, radio network temporary identifier (RNTI) or downlink control information (DCI) format size of the first type of UE.

10. The apparatus of claim 1, wherein the CORESET0 configuration is based on a second CORESET0 configuration without the frequency interleaving, such that the CCE indices of the CORESET0 physical downlink control channel (PDCCH) are sequentially mapped to the frequency resources of the CORESET0 configuration, wherein a subset of RBs within the second CORESET0 configuration is configured for a first type of UE that supports reduced bandwidth, and all RBs within the second CORESET0 configuration are configured for a second type of UE that supports non-reduced bandwidth.

11. The apparatus of claim 10, wherein the frequency domain resource allocation (FDRA) for the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on the range of RBs configured for the CORESET0 configuration, wherein the PDSCH is scheduled across one or more RBs.

12. The apparatus of claim 11, wherein the PDCCH is monitored by the second type of UE using a search space configuration, RNTI or DCI format size that is separate from the search space configuration, radio network temporary identifier (RNTI) or downlink control information (DCI) format size of the first type of UE.

13. The apparatus of claim 10, wherein the frequency domain resource allocation (FDRA) for the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on a range of RBs configured for the CORESET0 configuration, wherein the PDSCH is scheduled within a subset of the RBs, and wherein the PDCCH is monitored by the first type of UE and the second type of UE.

14. The apparatus of claim 10, wherein the frequency domain resource allocation (FDRA) for the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on the range of the RB subset, wherein the PDSCH is scheduled within the RB subset, and wherein the PDCCH is monitored by the first type of UE and the second type of UE.

15. A method for wireless communication at a network entity, the method comprising: Sending an instruction for a control resource set 0 (CORESET0) configuration to one or more types of user equipment (UE), the control resource set 0 (CORESET0) configuration including a first CORESET0 configuration based on one or more resource block (RB) sets or a second CORESET0 configuration without frequency interleaving; as well as The communication is made with the one or more types of UEs based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

16. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to the at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the device to: Receive an indication of the configuration of the control resource set 0 (CORESET0) from a network entity, the control resource set 0 (CORESET0) configuration including a first CORESET0 configuration based on one or more resource block (RB) sets or a second CORESET0 configuration without frequency interleaving; as well as CORESET0 transmission is monitored based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

17. The apparatus of claim 16, further comprising: A transceiver, coupled to the at least one processor, is configured to: The network entity receives the indication of the CORESET0 configuration, which includes a first CORESET0 configuration based on the one or more RB sets or a second CORESET0 configuration without the frequency interleaving.

18. The apparatus of claim 16, wherein the first CORESET0 configuration comprises M sets of RBs, wherein each of the M sets of RBs comprises N RBs.

19. The apparatus of claim 18, wherein the first CORESET0 configuration includes the frequency interleaving in each of the M RB sets.

20. The apparatus of claim 18, wherein the first CORESET0 configuration indicates that a first RB set is configured for a first type of UE, the first type of UE supporting reduced bandwidth similar to or greater than the bandwidth of N RBs in the first RB set, and one or more RB sets in the M RB sets are configured for a second type of UE, the second type of UE supporting reduced bandwidth similar to or greater than the bandwidth of M RBs in the M RB sets. The bandwidth of N RBs is similar to or greater than their non-reduced bandwidth, wherein monitoring the CORESET0 transmission includes: Based on the capabilities supported by the UE, monitor the first RB set or one or more RB sets in the M RB sets.

21. The apparatus of claim 18, wherein the frequency domain resource allocation (FDRA) for the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on the range of a first RB set in the M RB sets, wherein the PDSCH is scheduled within the first RB set in the M RB sets, wherein the PDCCH is monitored by a first type of UE and a second type of UE.

22. The apparatus of claim 21, wherein monitoring the CORESET0 transmission comprises: Monitor the repetition of PDSCH within multiple RB sets in the M RB sets.

23. The apparatus of claim 18, wherein the frequency domain resource allocation (FDRA) of the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on the range of the M RB sets, wherein the PDSCH is scheduled across multiple RB sets in the M RB sets, wherein the UE is a second type of UE, and the PDCCH is monitored using a search space configuration, RNTI or DCI format size that is separate from the search space configuration, radio network temporary identifier (RNTI) or downlink control information (DCI) format size of the first type of UE.

24. The apparatus of claim 16, wherein monitoring the CORESET0 transmission comprises: The RB subset or one or more RBs within the second CORESET0 configuration are monitored based on the bandwidth supported by the UE.

25. The apparatus of claim 24, wherein the frequency domain resource allocation (FDRA) for the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on the range of RBs configured for the CORESET0 transmission, wherein the PDSCH is scheduled across the one or more RBs.

26. The apparatus of claim 25, wherein the UE is a second type of UE, and the PDCCH is monitored using a search space configuration, RNTI or DCI format size that is separate from the search space configuration, radio network temporary identifier (RNTI) or downlink control information (DCI) format size of the first type of UE.

27. The apparatus of claim 24, wherein the frequency domain resource allocation (FDRA) for the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on a range of RBs configured for transmission of the CORESET0, wherein the PDSCH is scheduled within a subset of the RBs, and wherein the PDCCH is monitored by a first type of UE and a second type of UE.

28. The apparatus of claim 24, wherein the frequency domain resource allocation (FDRA) for the physical downlink control channel (PDCCH) for scheduling the physical downlink shared channel (PDSCH) is based on the range of the RB subset, wherein the PDSCH is scheduled within the RB subset, and wherein the PDCCH is monitored by a first type of UE and a second type of UE.

29. The apparatus of claim 16, wherein the at least one processor is configured to: The network entity is communicated based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

30. A method for conducting wireless communication at a user equipment (UE), the method comprising: Receive an indication of the configuration of the control resource set 0 (CORESET0) from a network entity, the control resource set 0 (CORESET0) configuration including a first CORESET0 configuration based on one or more resource block (RB) sets or a second CORESET0 configuration without frequency interleaving; as well as CORESET0 transmission is monitored based on at least one of the first CORESET0 configuration or the second CORESET0 configuration.

Images