Control resource set configurations for different device types

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive an indication of a control resource set (CORESET) configuration that indicates one or more CORESET parameters associated with a UE device type. The UE may monitor at least one physical downlink control channel (PDCCH) candidate location based at least in part on the CORESET configuration associated with the UE device type. Numerous other aspects are described.

Description

CONTROL RESOURCE SET CONFIGURATIONSFOR DIFFERENT DEVICE TYPESCROSS-REFERENCE TO RELATED APPLICATION

[0001] This Patent Application claims priority to U.S. Patent Application No. 18 / 787,849, filed on July 29, 2024, entitled “CONTROL RESOURCE SET CONFIGURATIONS FOR DIFFERENT DEVICE TYPES,” and assigned to the assignee hereof. The disclosure of the prior Application is considered part of and is incorporated by reference into this Patent Application.FIELD OF THE DISCLOSURE

[0002] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for control resource set configurations for different device types.BACKGROUND

[0003] Wireless communication systems are widely deployed to provide various services that may include carrying voice, text, messaging, video, data, and / or other traffic. The services may include unicast, multicast, and / or broadcast services, among other examples. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and / or device transmit power, among other examples). Examples of such multiple-access RATs include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single -carrier frequency division multiple access (SC- FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.

[0004] The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR). NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3 GPP). NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (loT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication), massive multiple-input multiple-output (MIMO), disaggregated network architectures and network topology expansions, multiple -subscriber implementations, high- precision positioning, and / or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The appended drawings illustrate some aspects of the present disclosure, but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements.

[0006] Fig. 1 is a diagram illustrating an example of a wireless network, in accordance with the present disclosure.

[0007] Fig. 2 is a diagram illustrating an example network node in communication with a user equipment (UE) in a wireless network, in accordance with the present disclosure.

[0008] Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

[0009] Fig. 4 is a diagram illustrating an example of a resource structure for wireless communication, including a control resource set (CORESET) for downlink control, in accordance with the present disclosure.

[0010] Fig. 5 is a diagram illustrating examples of CORESET configurations, in accordance with the present disclosure.

[0011] Figs. 6-11 are diagrams illustrating examples associated with CORESET configurations, in accordance with the present disclosure.

[0012] Fig. 12 is a flowchart illustrating an example process performed, for example, by a UE, in accordance with the present disclosure.

[0013] Fig. 13 is a flowchart illustrating an example process performed, for example, by a network node, in accordance with the present disclosure.

[0014] Figs. 14-15 are diagrams of example apparatuses for wireless communication, in accordance with the present disclosure.SUMMARY

[0015] Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving an indication of a control resource set (CORESET) configuration that indicates one or more CORESET parameters associated with a UE device type. The method may include monitoring at least one physical downlink control channel (PDCCH) candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0016] Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting, to a UE, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The method may include transmitting, to the UE, a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0017] Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The one or more processors may be configured to monitor at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0018] Some aspects described herein relate to a network node for wireless communication.The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to transmit, to a UE, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The one or more processors may be configured to transmit, to the UE, a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0019] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The set of instructions, when executed by one or more processors of the UE, may cause the UE to monitor at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0020] Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set ofinstructions, when executed by one or more processors of the network node, may cause the network node to transmit, to a UE, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, to the UE, a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0021] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The apparatus may include means for monitoring at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0022] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The apparatus may include means for transmitting, to the UE, a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0023] Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and / or processing system as substantially described with reference to, and as illustrated by, the specification and accompanying drawings.

[0024] The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings.DETAILED DESCRIPTION

[0025] Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in this disclosure.Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and / or functionalities in addition to or other than the structures and / or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

[0026] Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, apparatuses, and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

[0027] In a wireless network, different types of user equipments (UEs) may be utilized according to specific applications or use cases and / or according to specific desired properties and functionalities. For example, different UE device types may support different maximum bandwidths (e.g., wideband or narrowband) depending on the intended application or usage of the UE device type. Additionally, the maximum bandwidth that a specific UE device type supports may depend on a communication state of the UE (e.g., a given UE device type may support a relatively wider maximum bandwidth for receiving a system information block (SIB) or paging message in an idle or inactive mode, a relatively narrower maximum bandwidth for unicast data in a connected mode, or the like). For example, legacy or baseline UEs, reduced capability (RedCap) UEs, enhanced RedCap (eRedCap) UEs, and sub-5 MHz UEs may each operate in different and / or overlapping frequency bands, with differing maximum operating bandwidths for different applications or operation modes.

[0028] As a result of the differing UE device types and their underlying applications or operation modes, certain UE device types may not support certain resource allocations that are often used in wireless networks. For example, a narrowband UE device type (e.g., with a maximum bandwidth of 5 MHz or less) may not be compatible with a control resource set (CORESET) configuration designed for UE device types with wider maximum bandwidths. For example, technology advancements may lead to increased device specialization that results inUEs having smaller maximum bandwidths or other limited capabilities that are incompatible with CORESET configurations originally designed for UEs that support larger (e.g., 100 MHz) bandwidths or other more advanced capabilities.

[0029] Various aspects relate generally to flexible CORESET configurations that indicate CORESET parameters associated with different UE device types, thereby enabling CORESET configurations to support a variety of different UE device types. Some aspects more specifically relate to a CORESET configuration that enables more than three symbols in time domain resources and up to 12 symbols or 14 symbols per slot. Furthermore, the CORESET configuration may enable non-interleaving and / or interleaving in the frequency domain and / or the time domain among resource element group (REG) bundles and / or control channel elements (CCEs). The CORESET configuration may enable a flexible aggregation level within a slot, where the aggregation level may indicate the number of allocated CCEs for downlink control information (DCI). Additionally, the CORESET configuration may enable slot-level repetitions and / or frequency hopping (FH) for enhanced coverage.

[0030] Furthermore, the CORESET configuration may enable coexistence between different UE device types. For example, in non-UE-specific CORESETs, one or more REG bundles and / or CCEs may be shared between UEs of different device types. Alternatively, in UE- specific CORESETs, one or more REG bundles and / or CCEs may have independent configurations that are specific to different UE device types.

[0031] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by providing a flexible CORESET configuration that reuses basic resource structures associated with legacy CORESET designs, the described techniques may provide a CORESET configuration to support different UE device types with minimal changes to the legacy CORESET designs, as well as reduced complexity and enhanced coverage. By implementing only minimal changes to the legacy CORESET designs, the performance properties of a CORESET (e.g., higher spectral efficiency, lower power consumption, reduced network traffic, or the like) may be conserved with minimal, if any, alterations. In this way, a flexible CORESET configuration may offer backward capability with existing UE device types and may offer forward compatibility with other UE device types that may emerge in the future.

[0032] Multiple-access radio access technologies (RATs) have been adopted in various telecommunication standards to provide common protocols that enable wireless communication devices to communicate on a municipal, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP). 5G NR supports various technologies and use cases including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave(mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (loT) connectivity and management, and network function virtualization (NFV).

[0033] As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements may be adopted in or implemented for 5G NR or future RATs, such as 6G, to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, nonterrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, loT (including passive or ambient loT) networks, RedCap UE functionality, industrial connectivity, multiple -subscriber implementations, high- precision positioning, radio frequency (RF) sensing, and / or artificial intelligence or machine learning (AI / ML), among other examples. These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and / or aerial platforms, among other examples. The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies and / or support one or more of the foregoing use cases.

[0034] Fig. 1 is a diagram illustrating an example of a wireless communication network 100, in accordance with the present disclosure. The wireless communication network 100 may be or may include elements of a 5G (or NR) network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110, shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 1 lOd. The network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e.

[0035] The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and / or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless communication networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular RAT (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G / NRRAT, and / or a 6G RAT, among other examples. In some examples, when multiple RATs are deployed in a given geographic area, each RAT in the geographic area may operate on different frequencies to avoid interference with one another.

[0036] Various operating bands have been defined as frequency range designations FR1 (410 MHz through 7.125 GHz), FR2 (24.25 GHz through 52.6 GHz), FR3 (7.125 GHz through 24.25 GHz), FR4a or FR4-1 (52.6 GHz through 71 GHz), FR4 (52.6 GHz through 114.25 GHz), and FR5 (114.25 GHz through 300 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz), which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, “sub-6 GHz,” if used herein, may broadly refer to frequencies that are less than 6 GHz, that are within FR1, and / or that are included in mid-band frequencies. Similarly, the term “millimeter wave,” if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR4-a or FR4- 1, or FR5, and / or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and / or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS), in which multiple RATs (for example, 4G / Long Term Evolution (LTE) and 5G / NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges.

[0037] A network node 110 may include one or more devices, components, or systems that enable communication between a UE 120 and one or more devices, components, or systems of the wireless communication network 100. A network node 110 may be, may include, or may also be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, an eNB, a gNB, an access point (AP), a transmission reception point (TRP), a mobility element, a core, a network entity, a network element, a network equipment, and / or another type of device, component, or system included in a radio access network (RAN).

[0038] A network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures). For example, a network node 110 may be a device orsystem that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack), or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node (having an aggregated architecture), meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100. For example, an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.

[0039] Alternatively, and as also shown, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station), meaning that the network node 110 may implement a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same geographic location or in different geographic locations. For example, a disaggregated network node may have a disaggregated architecture. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance), or in a virtualized radio access network (vRAN), also known as a cloud radio access network (C-RAN), to facilitate scaling by separating base station functionality into multiple units that can be individually deployed.

[0040] The network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). A CU may host one or more higher layer control functions, such as radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, and / or service data adaptation protocol (SDAP) functions, among other examples. A DU may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and / or one or more higher physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host one or more lower PHY layer functions, such as a fast Fourier transform (FFT), an inverse FFT (iFFT), beamforming, physical random access channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, among other examples. An RU may host RF processing functions or lower PHY layer functions, such as an FFT, an iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer functional split. In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120.

[0041] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, a networknode 110 may include one or more Near-Real Time (Near-RT) RAN Intelligent Controllers (RICs) and / or one or more Non-Real Time (Non-RT) RICs. In some examples, a CU, a DU, and / or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU), among other examples. A virtual unit may be implemented as a virtual network function, such as associated with a cloud deployment.

[0042] Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG)). A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. In some examples, a cell may not necessarily be stationary. For example, the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or an NTN network node).

[0043] The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and / or disaggregated network nodes, among other examples. In the example shown in Fig. 1, the network node 110a may be a macro network node for a macro cell 130a, the network node 110b may be a pico network node for a pico cell 130b, and the network node 110c may be a femto network node for a femto cell 130c.Various different types of network nodes 110 may generally transmit at different power levels, serve different coverage areas, and / or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts), whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0. 1 to 2 watts).

[0044] In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link). The radio access link may include a downlink and an uplink. “Downlink” (or “DL”) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL”) refers to a communication direction from a UE 120 to a network node 110. Downlink channels may include one or more control channels and one or more data channels. A downlink control channel may be used to transmit DCI (for example, scheduling information, reference signals, and / or configuration information) from a network node 110 to a UE 120. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCHs), and downlink data channels may include one or more physical downlink shared channels (PDSCHs). A CORESET may include a set of physical resources used to transmit a PDCCH and / or DCI from a network node 110 to a UE 120. Uplink channels may similarly include one or more control channels and one or more data channels. An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and / or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include one or more physical uplink control channels (PUCCHs), and uplink data channels may include one or more physical uplink shared channels (PUSCHs). The downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate.

[0045] Downlink and uplink resources may include time domain resources (frames, subframes, slots, and / or symbols), frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial domain resources (particular transmit directions and / or beam parameters). A CORESET may include one or more CCEs that may span a portion of a system bandwidth and one or more symbols in a time domain. Each CCE may include a fixed or variable quantity of REGs. The quantity of REGs included in a CCE may be specified by an REG bundle size. An REG may include a resource block, which may include resource elements (REs) within a symbol. An RE may occupy one subcarrier in the frequency domain and one orthogonal frequency division multiplexing (OFDM) symbol in the time domain.

[0046] Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs). A BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP andthe downlink BWP may be the same BWP or different BWPs). A BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and / or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor), leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.

[0047] As described above, in some aspects, the wireless communication network 100 may be, may include, or may be included in, an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. An anchor network node 110 may also be referred to as an IAB donor (or “lAB-donor”). The anchor network node 110 may connect to the core network via a wired backhaul link. For example, an Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF). An IAB network also generally includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply as IAB nodes (or “lAB-nodes”). Each nonanchor network node 110 may communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or may communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network node 110 or other non-anchor network node 110 may also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication (such as time resources, frequency resources, and / or spatial resources) may be shared between access links and backhaul links.

[0048] In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a “multi-hop network.” In the example shown in Fig. 1, the network node 1 lOd (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communicationbetween the network node 110a and the UE 120d. Additionally or alternatively, a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples.

[0049] The UEs 120 may be physically dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone), a personal digital assistant (PDA), a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and / or smart jewelry, such as a smart ring or a smart bracelet), an entertainment device (for example, a music device, a video device, and / or a satellite radio), an XR device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that may communicate via a wireless medium.

[0050] A UE 120 and / or a network node 110 may include one or more chips, system -on- chips (SoCs), chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs) and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASIC), programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs)), or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry”). One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions.

[0051] The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as random-accessmemory (RAM) or read-only memory (ROM), or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry”). One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, Institute of Electrical and Electronics Engineers (IEEE) compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem). In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers. The UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system.

[0052] Some UEs 120 may be considered machine-type communication (MTC) UEs, evolved or enhanced machine-type communication (eMTC), UEs, further enhanced eMTC (feMTC) UEs, enhanced feMTC (efeMTC) UEs, reduced capability (RedCap) UEs, enhanced RedCap (e RedCap) UEs, non-RedCap UEs having a maximum bandwidth of 100 MHz for FR1 and a maximum bandwidth of 400 MHz for FR2, sub-5 MHz UEs, and / or additional device types with greater and / or lesser capabilities that may be developed in the future, or further evolutions thereof, all of which may be simply referred to as “MTC UEs”. An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and / or a location tag. Some UEs 120 may be considered loT devices and / or may be implemented as NB-IoT (narrowband loT) devices. An loT UE or NB-IoT device may be, may include, or may be included in or coupled with an industrial machine, an appliance, a refrigerator, a doorbell camera device, a home automation device, and / or a light fixture, among other examples. Some UEs 120 may be considered Customer Premises Equipment, which may include telecommunications devices that are installed at a customer location (such as a home or office) to enable access to a service provider's network (such as included in or in communication with the wireless communication network 100).

[0053] Some UEs 120 may be classified according to different categories in association with different complexities and / or different capabilities. UEs 120 in a first category may facilitate massive loT in the wireless communication network 100, and may offer low complexity and / or cost relative to UEs 120 in a second category. UEs 120 in a second category may include mission-critical loT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, fullcapability UEs, and / or premium UEs that are capable of URLLC, eMBB, and / or precise positioning in the wireless communication network 100, among other examples. A third category of UEs 120 may have mid-tier complexity and / or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability). A UE 120 of the third category may include a RedCap UE, an eRedCapUE, a mid-tier UE, an NR-Light UE, and / or an NR-Lite UE, among other examples. RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and / or eMTC UEs, and mission-critical loT devices and / or premium UEs. RedCap UEs may include, for example, wearable devices, loT devices, industrial sensors, and / or cameras that are associated with a limited bandwidth, power capacity, and / or transmission range, among other examples. RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and / or smart city deployments, among other examples.

[0054] In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary). As an example, the UE 120a may directly transmit data, control information, or other signaling as a sidelink communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the data to the UE 120e in a DL communication. In various examples, the UEs 120 may transmit and receive sidelink communications using peer-to-peer (P2P) communication protocols, device-to- device (D2D) communication protocols, vehicle -to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols. In some deployments and configurations, a network node 110 may schedule and / or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and / or other operations for sidelink communications.

[0055] In various examples, some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full -duplex operation in addition to halfduplex operation. A network node 110 or a UE 120 operating in a half-duplex mode mayperform only one of transmission or reception during particular time resources, such as during particular slots, symbols, or other time periods. Half-duplex operation may involve timedivision duplexing (TDD), in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time). In contrast, a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources). By operating in a full-duplex mode, network nodes 110 and / or UEs 120 may generally increase the capacity of the network and the radio access link. In some examples, full- duplex operation may involve frequency-division duplexing (FDD), in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for a UE 120 but not for a network node 110. For example, a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for a network node 110 but not for a UE 120. For example, a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both a network node 110 and a UE 120.

[0056] In some examples, the UEs 120 and the network nodes 110 may perform MIMO communication. “MIMO” generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO). Some RATs may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs), reciprocity in the time domain or the frequency domain, single-frequency-network (SFN) transmission, or non-coherent joint transmission (NC-JT).

[0057] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type; and monitor at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

[0058] In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may transmit, to a UE 120, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type; and transmit, to the UE 120, a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

[0059] As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

[0060] Fig. 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network, in accordance with the present disclosure.

[0061] As shown in Fig. 2, the network node 110 may include a data source 212, a transmit processor 214, atransmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a through 232t, where t > I), a set of antennas 234 (shown as 234a through 234v, where v > I), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, among other examples. In some configurations, one or a combination of the antenna(s) 234, the modem(s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and / orthe TX MIMO processor 216 may be included in a transceiver of the network node 110. The transceiver may be under control of and used by one or more processors, such as the controller / processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and / or operations described herein. In some aspects, the network node 110 may include one or more interfaces, communication components, and / or other components that facilitate communication with the UE 120 or another network node.

[0062] The terms “processor,” “controller,” or “controller / processor” may refer to one or more controllers and / or one or more processors. For example, reference to “a / the processor,” “a / the controller / processor,” or the like (in the singular) should be understood to refer to any one or more of the processors described in connection with Fig. 2, such as a single processor or a combination of multiple different processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Fig. 2. For example, one or more processors of the network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.

[0063] In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Fig. 2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

[0064] For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data (“downlink data”) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue). In some examples, the transmit processor 214 may select one or more modulation and coding schemes (MCSs) for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS(s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI)) and / or control information (for example, CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and / or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS), a demodulation reference signal (DMRS), or a channel state information (CSI) reference signal (CSI-RS)) and / or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS)).

[0065] The TX MIMO processor 216 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to the set of modems 232. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 232. Each modem 232 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time domain downlink signal. The modems 232a through 232t may together transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234.

[0066] A downlink signal may include a DCI communication, a MAC control element (MAC-CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication. Downlink signals may be transmitted on a PDCCH, a PDSCH, and / or on another downlink channel. A downlink signal may carry one or more transport blocks (TBs) of data. A TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100. A data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The quantity of TBs used to carry the data associated with a particular data stream may be associated with a TB size common to the multiple TBs. The TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and / or another parameter. In general, the larger the TB size, the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead. However, larger TB sizes may be more prone to transmission and / or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques.

[0067] For uplink communication from the UE 120 to the network node 110, uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232), may be detected by the MIMO detector 236 (for example, a receive (Rx) MIMO processor) if applicable, and / or may be further processed by the receive processor 238 to obtain decoded data and / or control information. The receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and / or another type of data sink) and provide the decoded control information to a processor, such as the controller / processor 240.

[0068] The network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some aspects, the scheduler 246 may use DCI to dynamically schedule DL transmissions to the UE 120 and / or UL transmissions from the UE 120. In some examples, the scheduler 246 may allocate recurring time domain resources and / or frequency domain resources that the UE 120 may use to transmit and / or receive communications using an RRC configuration (for example, a semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure a configured grant (CG) for the UE 120.

[0069] One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and / or the controller / processor 240 may be included in an RF chain of the network node 110. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or moreprocessors of the network node 110). In some aspects, the RF chain may be or may be included in a transceiver of the network node 110.

[0070] In some examples, the network node 110 may use the communication unit 244 to communicate with a core network and / or with other network nodes. The communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, optical fiber, common public radio interface (CPRI), and / or a wired or wireless backhaul, among other examples. The network node 110 may use the communication unit 244 to transmit and / or receive data associated with the UE 120 or to perform network control signaling, among other examples. The communication unit 244 may include a transceiver and / or an interface, such as a network interface.

[0071] The UE 120 may include a set of antennas 252 (shown as antennas 252a through 252r, where r > 1), a set of modems 254 (shown as modems 254a through 254u, where u > 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, among other examples. One or more of the components of the UE 120 may be included in a housing 284. In some aspects, one or a combination of the antenna(s) 252, the modem(s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120. The transceiver may be under control of and used by one or more processors, such as the controller / processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein. In some aspects, the UE 120 may include another interface, another communication component, and / or another component that facilitates communication with the network node 110 and / or another UE 120.

[0072] For downlink communication from the network node 110 to the UE 120, the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254. For example, each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use the respective demodulator component to condition (for example, filter, amplify, downconvert, and / or digitize) a received signal to obtain input samples. Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. The receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and / or an application executed on theUE 120), and may provide decoded control information and system information to the controller / processor 280.

[0073] For uplink communication from the UE 120 to the network node 110, the transmit processor 264 may receive and process data (“uplink data”) from a data source 262 (such as a data pipeline, a data queue, and / or an application executed on the UE 120) and control information from the controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receive processor 258 and / or the controller / processor 280 may determine, for a received signal (such as received from the network node 110 or another UE), one or more parameters relating to transmission of the uplink communication. The one or more parameters may include a reference signal received power (RSRP) parameter, a received signal strength indicator (RS SI) parameter, a reference signal received quality (RSRQ) parameter, a CQI parameter, or a transmit power control (TPC) parameter, among other examples. The control information may include an indication of the RSRP parameter, the RS SI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and / or another parameter. The control information may facilitate parameter selection and / or scheduling for the UE 120 by the network node 110.

[0074] The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink sounding reference signal (SRS), and / or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM). The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.

[0075] The modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252. An uplink signal may include a UCI communication, a MAC-CE communication, an RRC communication, or another type of uplink communication. Uplink signals may be transmitted on a PUSCH, a PUCCH, and / or another type of uplink channel. An uplink signal may carry one or more TBs of data. Sidelink data and control transmissions (that is, transmissions directly between two ormore UEs 120) may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0076] One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Fig. 2. As used herein, “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. “Antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas. “Antenna module” may refer to circuitry including one or more antennas, which may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.

[0077] In some examples, each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. A spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam). For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, a half wavelength, or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference patterns of signals transmitted by the separate antenna elements within that expected range.

[0078] The amplitudes and / or phases of signals transmitted via antenna elements and / or subelements may be modulated and shifted relative to each other (such as by manipulating phase shift, phase offset, and / or amplitude) to generate one or more beams, which is referred to as beamforming. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. “Beam” may also generally referto a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and / or a vertical direction), and / or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and / or a set of directional resources associated with the signal. In some implementations, antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and / or phases of the signal(s) to form one or more beams. The shape of a beam (such as the amplitude, width, and / or presence of side lobes) and / or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of the multiple signals relative to each other.

[0079] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements. As another example, a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements.Generally, a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements. Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmitted using the same time and frequency resources with spatial multiplexing.

[0080] While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and / or the TX MIMO processor 266 may be performed by or under the control of the controller / processor 280.

[0081] Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. One or more components of the example disaggregated base station architecture 300 may be, may include, or may be included in one or more network nodes (such one or more network nodes 110). The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or that can communicate indirectly with the core network 320 via one or more disaggregated control units, such as a Non-RT RIC 350 associated with a Service Management and Orchestration (SMO) Framework 360 and / or a Near-RT RIC 370 (for example, via an E2 link). The CU 310 may communicate with one or more DUs 330 viarespective midhaul links, such as via Fl interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs 340.

[0082] Each of the components of the disaggregated base station architecture 300, including the CUs 310, the DUs 330, the RUs 340, the Near-RT RICs 370, the Non-RT RICs 350, and the SMO Framework 360, may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium.

[0083] In some aspects, the CU 310 may be logically split into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. A CU-UP unit may communicate bidirectionally with a CU-CP unit via an interface, such as the El interface when implemented in an O-RAN configuration. The CU 310 may be deployed to communicate with one or more DUs 330, as necessary, for network control and signaling. Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, a DU 330 may host various layers, such as an RLC layer, a MAC layer, or one or more PHY layers, such as one or more high PHY layers or one or more low PHY layers. Each layer (which also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310. Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU(s) 340 may be controlled by the corresponding DU 330.

[0084] The SMO Framework 360 may support RAN deployment and provisioning of nonvirtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an 01 interface. For virtualized network elements, the SMO Framework 360 may interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an 02 interface. A virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and / or a Near-RT RIC 370. In some aspects, the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, a 5G NR RAN, and / or a 6G RAN, such as an open eNB (O- eNB) 380, via an 01 interface. Additionally or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective 01 interface. In somedeployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0085] The Non-RT RIC 350 may include or may implement a logical function that enables non-real-time control and optimization of RAN elements and resources, AI / ML workflows including model training and updates, and / or policy-based guidance of applications and / or features in the Near-RT RIC 370. The Non-RT RIC 350 may be coupled to or may communicate with (such as via an Al interface) the Near-RT RIC 370. The Near-RT RIC 370 may include or may implement a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, and / or an O-eNB with the Near-RT RIC 370.

[0086] In some aspects, to generate AI / ML models to be deployed in the Near-RT RIC 370, the Non-RT RIC 350 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 370 and may be received at the SMO Framework 360 or the Non-RT RIC 350 from non-network data sources or from network functions. In some examples, the Non-RT RIC 350 or the Near-RT RIC 370 may tune RAN behavior or performance. For example, the Non-RT RIC 350 may monitor long-term trends and patterns for performance and may employ AI / ML models to perform corrective actions via the SMO Framework 360 (such as reconfiguration via an 01 interface) or via creation of RAN management policies (such as Al interface policies).

[0087] The network node 110, the controller / processor 240 of the network node 110, the UE 120, the controller / processor 280 of the UE 120, the CU 310, the DU 330, the RU 340, or any other componcnt(s) of Figs. 1, 2, or 3 may implement one or more techniques or perform one or more operations associated with CORESET configurations for different device types, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, any other component(s) of Fig.2, the CU 310, the DU 330, or the RU 340 may perform or direct operations of, for example, process 1200 of Fig. 12, process 1300 of Fig. 13, or other processes as described herein (alone or in conjunction with one or more other processors). The memory 242 may store data and program codes for the network node 110, the network node 110, the CU 310, the DU 330, or the RU 340. The memory 282 may store data and program codes for the UE 120. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing a set of instructions (for example, code or program code) for wireless communication. The memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). The memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types). For example, the set of instructions, when executed (forexample, directly, or after compiling, converting, or interpreting) by one or more processors of the network node 110, the UE 120, the CU 310, the DU 330, or the RU 340, may cause the one or more processors to perform process 1200 of Fig. 12, process 1300 of Fig. 13, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and / or interpreting the instructions, among other examples.

[0088] In some aspects, the UE 120 includes means for receiving an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type; and / or means for monitoring at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type. The means for the UE 120 to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller / processor 280, or memory 282.

[0089] In some aspects, the network node 110 includes means for transmitting, to a UE 120, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type; and / or means for transmitting, to the UE 120, a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type. The means for the network node 110 to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller / processor 240, memory 242, or scheduler 246.

[0090] As indicated above, Fig. 3 is provided as an example. Other examples may differ from what is described with regard to Fig. 3.

[0091] Fig. 4 is a diagram illustrating an example resource structure 400 for wireless communication, in accordance with the present disclosure. Resource structure 400 shows an example of various groups of resources described herein. As shown, resource structure 400 may include a subframe 405. Subframe 405 may include multiple slots 410. While resource structure 400 is shown as including 2 slots per subframe, a different number of slots may be included in a subframe (e.g., 4 slots, 8 slots, 16 slots, 32 slots, or another quantity of slots). In some aspects, different types of transmission time intervals (TTIs) may be used, other than subframes and / or slots. A slot 410 may include multiple symbols 415, such as 14 symbols per slot.

[0092] The potential control region of a slot 410 may be referred to as a CORESET 420 and may be structured to support an efficient use of resources, such as by flexible configuration orreconfiguration of resources of the CORESET 420 for one or more PDCCHs and / or one or more PDSCHs. However, legacy CORESETs 420 are constrained in their ability to support flexible configuration or reconfiguration in low-complexity UEs 120, in narrowband UE 120 device types, MTC and / or NB-IoT UE 120 device types, and / or among other different device types. In some aspects, the CORESET 420 may occupy the first symbol 415 of a slot 410, the first two symbols 415 of a slot 410, or the first three symbols 415 of a slot 410. Thus, a CORESET 420 may include multiple resource blocks (RBs) or physical resource blocks (PRBs) in the frequency domain, and either one, two, or three symbols 415 in the time domain. In some cases, a quantity of resources included in the CORESET 420 may be flexibly configured, such as by using RRC signaling to indicate a frequency domain region (e.g., a quantity of resource blocks), a time domain region (e.g., a quantity of symbols) for the CORESET 420, and / or a transmission type (e.g., interleaved or non-interleaved).

[0093] As illustrated, a symbol 415 that includes CORESET 420 may include one or more CCEs 425, shown as two CCEs 425 as an example, that span a portion of the system bandwidth. A CCE 425 may include DCI that is used to provide control information for wireless communication. A network node may transmit DCI during multiple CCEs 425 (as shown), where the quantity of CCEs 425 used for transmission of DCI represents an aggregation level used by the network node for the transmission of DCI. In Fig. 4, an aggregation level of two is shown as an example, corresponding to two CCEs 425 in a slot 410. In some aspects, different aggregation levels may be used, such as 1, 2, 4, 8, 16, or another aggregation level.

[0094] Each CCE 425 may include a fixed quantity of REGs 430, shown as 6 REGs 430, or may include a variable quantity of REGs 430. In some aspects, the quantity of REGs 430 included in a CCE 425 may be specified by an REG bundle size. An REG 430 may include one resource block, which may include 12 REs 435 within a symbol 415. Accordingly, in some aspects, one CCE 425 may include 6 REGs 430 for a total of 72 REs 435. An RE 435 may occupy one subcarrier in the frequency domain and one OFDM symbol in the time domain.

[0095] A search space may include all possible locations (e.g., in time and / or frequency) where a PDCCH may be located. A CORESET 420 may include one or more search spaces, such as a UE-specific search space, a group-common search space, and / or a common search space. A search space may indicate a set of CCE locations that a UE may monitor to detect PDCCHs that can potentially be used to transmit control information to the UE. The possible locations for a PDCCH may depend on whether the PDCCH is a UE-specific PDCCH (e.g., for a single UE), a group-common PDCCH (e.g., for multiple UEs), and / or a common search space (e.g., for all UEs in a cell), and / or may depend on an aggregation level being used. A possible location (e.g., in time and / or frequency) for a PDCCH may be referred to as a PDCCH candidate location, and the set of all possible PDCCH candidate locations at an aggregation level may be referred to as a search space. For example, the set of all possible PDCCHcandidate locations for a particular UE may be referred to as a UE-specific search space. Similarly, the set of all possible PDCCH candidate locations across all UEs may be referred to as a common search space. The set of all possible PDCCH candidate locations for a particular group of UEs may be referred to as a group-common search space. One or more search spaces across aggregation levels may be referred to as a search space (SS) set. In some aspects, the PDCCH candidate location may be based on an index associated with a TTI or an identifier associated with a UE. Additionally, the PDCCH may be mapped to a specific SS set according to the DCI.

[0096] A CORESET 420 may be interleaved or non-interleaved. An interleaved CORESET 420 may have a CCE-to-REG mapping such that adjacent CCEs 425 are mapped to scattered REG bundles in the frequency domain (e.g., adjacent CCEs 425 are not mapped to consecutive REG bundles of the CORESET 420). A non-interleaved CORESET 420 may have a CCE-to- REG mapping such that all CCEs 425 are mapped to consecutive REG bundles (e.g., in the frequency domain) of the CORESET 420.

[0097] As indicated above, Fig. 4 is provided as an example. Other examples may differ from what is described with respect to Fig. 4.

[0098] Fig. 5 is a diagram illustrating an example 500 of CORESET configurations, in accordance with the present disclosure.

[0099] The resource structure for wireless communication may include a potential control region, referred to as a CORESET. As described herein, the CORESET may be structured to support an efficient use of resources for one or more PDCCHs. A CORESET may also be used to transmit a PDCCH and / or DCI that includes a scheduling configurations for one or more PDSCHs. A CORESET may include multiple RBs or PRBs in the frequency domain, and in some aspects, as shown by reference numbers 510, 520, and 530, a CORESET may include one, two, or three symbols in the time domain. A symbol that includes a CORESET may include one or more CCEs that span a portion of the system bandwidth. Each CCE within the CORESET may include one or more REGs, where the quantity of REGs included in a CCE may be specified by an REG bundle size.

[0100] A CORESET configuration may include frequency domain resources that may or may not be contiguous. In one aspect, the CORESET configuration may include a frequency domain resource allocation that may be configured using a bitmap (e.g., a DL random access (RA) Type 0 bitmap) in units of 6 RBs with no restrictions on the maximum number of segments for a given CORESET.

[0101] A CORESET configuration may include a time duration of 1, 2, or 3 contiguous OFDM symbols. In some aspects, the CORESET configuration may include a maximum of 2 symbols if a first DMRS position of a PDSCH with slot-based scheduling is on a third symbol,or else the CORESET configuration may include up to 3 symbols. In some aspects, for slotbased scheduling (e.g., where the CORESET schedules a PDSCH in the same slot), the starting OFDM symbol of a CORESET can be symbol number 0, number 1, or number 2 in a slot, and the ending OFDM symbol of the CORESET may be not later than symbol number 2 in a slot. Additionally, a CORESET may be associated with an interleaved or non-interleaved transmission type. In the case of an interleaved CORESET, the interleaving pattern may be derived by a specific CORESET configuration and may be independent from other CORESET configurations.

[0102] As shown in Fig. 5, for example, a CCE is typically defined as including 6 REGs, and an REG may be defined as one RB (or PRB) in one OFDM symbol (e.g., 12 subcarriers). In some cases, a CCE may be mapped to REGs with interleaved or non-interleaved REG indexes within a CORESET. Similarly, an REG bundle size of CORESETO (e.g., for SIB scheduling) may be 6 REGs and / or an REG bundle size of a UE-specific CORESET may be configurable to 2, 3, or 6 REGs. Additionally, a UE may assume that the same precoder is used for the REGs in an REG bundle and that the REGs in an REG bundle are contiguous in frequency and / or time.

[0103] For example, Fig. 5 illustrates examples of CORESETs that include one, two, or three symbols and utilize interleaving of REG bundles in the frequency domain (e.g., within a 5 MHz bandwidth). For example, and as shown by reference number 510, an REG bundle 0 may span one symbol (e.g., symbol 0) and six RBs (e.g., RBs 0-5), providing for six REGs (e.g., one symbol x six RBs). Each REG bundle illustrated in reference number 510 spans one symbol and six RBs. For example, REG bundle 1 may span one symbol (e.g., symbol 0) and six RBs (e.g., RBs 12-17), providing for six REGs (e.g., one symbol x six RBs). Interleaving of the REG bundles may result in consecutively-indexed REG bundles being non-adjacent.

[0104] As shown by reference number 520, for example, a CORESET may include two symbols and utilize interleaving of REG bundles across the frequency domain (e.g., 5 MHz). Each REG bundle illustrated in reference number 520 spans two symbols and three RBs. For example, and as shown by reference number 520, an REG bundle 0 may include two symbols (e.g., symbol 0 and symbol 1) and three RBs (e.g., RBs 0-2) per symbol, providing for six REGs (e.g., two symbols x three RBs). Similarly, for example, REG bundle 1 may include two symbols (e.g., symbol 0 and symbol 1) and three RBs (e.g., RBs 12-14), providing for six REGs (e.g., two symbols x three RBs). Interleaving of the REG bundles may result in consecutively- indexed REG bundles being non-adjacent. The interleaving opportunities in a CORESET configuration are based on the number of symbols in the CORESET configuration. For example, because the CORESET configuration of reference number 520 includes REG bundles mapped across two symbols in the time domain, there is more opportunity for interleaving in the time domain when compared, for example, to the one-symbol CORESET configuration in reference number 510.

[0105] As shown by reference number 530, for example, a CORESET may include three symbols and utilize interleaving of REG bundles across the frequency domain (e.g., 5 MHz). For example, and as shown by reference number 530, an REG bundle 0 may include three symbols (e.g., symbols 0-2) and two RBs (e.g., RB 0 and RB 1), providing for six REGs (e.g., three symbols x two RBs). Similarly, an REG bundle 1 may include three symbols (e.g., symbols 0-2) and two RBs (e.g., RB 12 and RB 13), providing for six REGs (e.g., three symbols x two RBs). An REG bundle 2 may include three symbols (e.g., symbol 0, symbol 1, and symbol 2) and two RBs (e.g., RB2 and RB 3), providing for six REGs (e.g., three symbols x two RBs). An REG bundle 3 may include three symbols (e.g., symbols 0-2) and two RBs (e.g., RB 14 and RB 15), providing for six REGs (e.g., three symbols x two RBs).

[0106] Interleaving of the REG bundles may result in consecutively-indexed REG bundles being non-adjacent. The interleaving opportunities in a CORESET configuration are based on the number of symbols in the CORESET configuration. For example, because the CORESET configuration of reference number 530 includes REG bundles mapped across three symbols in the time domain, there is more opportunity for interleaving in the time domain when compared, for example, to the CORESET configurations in reference number 510 and in reference number 520.

[0107] As described herein, typical CORESET configurations are designed for wideband and narrowband UEs that support maximum bandwidths of at least (and typically greater than) 5 MHz. For example, Non-RedCap UEs may have a maximum bandwidth of 100 MHz for FR1 and a maximum bandwidth of 400 MHZ for FR2, and RedCap UEs may have an RF maximum bandwidth of 20 MHz for FR1 and a maximum bandwidth of 100 MHz for FR2. Additionally, eRedCap UEs may have an RF maximum bandwidth of 20 MHz for FR1 and a maximum bandwidth of 100 MHz for FR2, but eRedCap UEs may have a smaller maximum bandwidth of 20 MHz for SIB and / or paging in an idle and / or inactive mode and a maximum bandwidth of only 5 MHz for unicast data in a connected mode. Furthermore, sub-5 MHz UEs utilize RF bandwidths as low as 3 MHz or 5 MHz, wherein the maximum bandwidth may be 12 PRBs or 15 PRBs for 3 MHz or 20 PRBs for 5 MHz. Accordingly, a sub-5 MHz device is not supported by a CORESET designed to span 5 MHz or more because the maximum bandwidth of the sub-5 MHz device could be as small as 3 MHz. Additionally, and as described herein, a maximum bandwidth of a UE could be as small as 1.08 MHz (for example, 6 PRBs with a subcarrier spacing of 15 kilohertz) for baseband.

[0108] Accordingly, changes to CORESET designs are needed for different UE device types that may have different (e.g., constrained) maximum bandwidths and / or other limited capabilities.

[0109] As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

[0110] Fig. 6 is a diagram illustrating an example 600 associated with CORESET configurations for different device types, in accordance with the present disclosure. As shown in Fig. 6, example 600 includes communication between a network node 110 and a UE 120. In some aspects, the network node 110 and the UE 120 may be included in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.[OHl] In some aspects, the network node 110 may indicate a CORESET configuration to the UE 120, where the CORESET configuration includes a set of CORESET parameters associated with a device type of the UE 120. The UE 120 may utilize the CORESET configuration as part of the UE 120 monitoring of one or more PDCCH candidate locations, wherein the UE 120 may then receive one or more PDCCH communications from the network node 110 in at least one of the PDCCH candidate locations, based at least in part on the CORESET configuration including the CORESET parameters associated with the UE 120 device type.

[0112] As shown by reference number 610, the network node 110 may transmit an indication of a CORESET configuration with CORESET parameters associated with the UE 120 device type. The UE 120 may receive the CORESET configuration.

[0113] In some aspects, the CORESET configuration may generally include one or more REGs, REG bundles, and CCEs. The CORESET configuration may also include 6 PRBs as the minimum unit of frequency resources in the frequency domain. Furthermore, the basic unit of an REG bundle may include 6 REGs (e.g., 2 PRBs x 3 symbols, 3 PRBs x 2 symbols, and / or 6 PRBs x 1 symbol). In addition, the CORESET configuration may include a set of parameters that can be flexibly configured based at least in part on the device type of the UE 120. For example, in some aspects, the CORESET configuration may enable more than three symbols in a time domain and may enable up to 12 or 14 symbols per slot. For example, if an REG bundle includes (3 PRBs x 2 symbols), the CORESET configuration may enable up to 12 symbols (e.g., 2 x (3 PRBs x 2 symbols) x 6 = 72 REGs). If an REG bundle includes (2 PRBs x 3 symbols), the CORESET configuration may enable up to 12 symbols (e.g., 3 x (2 PRBs x 3 symbols) x 4 = 72 REGs). If an REG bundle includes (6 PRBs x 1 symbol), the CORESET configuration may enable up to 12 symbols (e.g., (6 PRBs x 1 symbol) x 12 = 72 REGs) or up to 14 symbols (e.g., (6 PRBs x 1 symbol) x 14 = 84 REGs.)

[0114] In addition, the CORESET configuration may enable non-interleaving or interleaving in a frequency domain and / or a time domain among REG bundles and / or CCEs. For example, the CORESET configuration may enable a time-first RE mapping within an REG bundle and / or may utilize an REG bundle mapping within 6 PRBs. By enabling the flexibility of, for example,the number of symbols in the time domain and the number of symbols per slot, a CORESET configuration may be adapted to support UE devices of different types. As discussed herein, spanning a CORESET configuration across more than 3 symbols results in a reduced CORESET bandwidth. For example, instead of spanning 12 REG bundles across 3 symbols and a 5 MHz bandwidth, spanning the 12 REG bundles over 12 symbols results in a reduced CORESET bandwidth of 1.08 MHz for a UE 120 with a maximum bandwidth of less than 5 MHz.

[0115] In some aspects, the CORESET configuration may enable a flexible aggregation level within a slot. For example, in an REG bundle that includes 3 PRBs across 2 symbols or 2 PRBs across 3 symbols, the CORESET configuration may support an aggregation level of 12. Similarly, in an REG bundle that includes 6 PRBs across 1 symbol, the CORESET configuration may support an aggregation level of 12 or 14.

[0116] In some aspects, the CORESET configuration may enable coexistence between UEs 120 of different device types (e.g., non-MTC and MTC UEs, wideband UEs such as eMBB or URLLC UEs, RedCap UEs, eRedCap UEs, sub-5MHz UEs, or the like.) For example, in non- UE specific CORESETs, equivalent REG bundle(s) and / or CCE(s) in the first symbol(s) may be shared for different UE device types. Similarly, for example, in UE-specific CORESETs, the REG bundle(s) and / or CCEs may be independently configured as between different UE device types.

[0117] In some aspects, the CORESET configuration may enable slot-level repetitions and / or frequency hopping to provide enhanced coverage (e.g., a repetition factor (R) may have a value of 1, 2, 4, 8, 16, 32, 64, or 256).

[0118] As shown by reference number 620, the UE 120 may monitor at least one PDCCH candidate location based at least in part on the CORESET configuration. The PDCCH candidate location may be a possible location (e.g., in a time domain and / or in a frequency domain) for a PDCCH and may be associated with the CORESET parameters that are associated with the UE device type. Additionally, the PDCCH candidate locations may depend on a slot, a radio network temporary identifier (RNTI) assigned to the UE 120, and / or other parameters.

[0119] As shown by reference number 630, the network node 110 may transmit a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration. The UE 120 may receive the PDCCH communication in, for example, at least one of the PDCCH candidate locations.

[0120] Accordingly, a CORESET configuration that include parameters associated with a specific UE device type may support a variety of UE device types, including for example, previously unsupported device types and / or new device types that may be developed for specific use cases or applications. In some aspects, a CORESET configuration may enable a UE 120 toreceive a PDCCH communication in a PDCCH candidate location based in part on a received CORESET configuration that includes CORESET parameters associated with the device type of the UE 120. A PDCCH is used to transfer DCI, and the PDCCH may be utilized for a downlink grant scheduling a PDSCH, an uplink grant scheduling a PUSCH, indicating a slot format, indicating a transmit power control command, or the like.

[0121] As indicated above, Fig. 6 is provided as an example. Other examples may differ from what is described with respect to Fig. 6.

[0122] Fig. 7 is a diagram illustrating an example 700 associated with CORESET configurations for different device types, in accordance with the present disclosure. As shown in Fig. 7, example 700 includes an example legacy CORESET configuration having CCEs and / or REG bundles limited to three symbols in a time domain and flexible CORESET configurations that may support different UE device types (e.g., by enabling CCEs and / or REG bundles to occupy more than three symbols in a slot). In some aspects, example 700 illustrates CORESET configurations that may be transmitted from a network node 110 to one or more UEs 120 in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0123] As shown by reference number 710, an example legacy CORESET configuration includes twelve REG bundles (e.g., REG bundles 0-11) mapped across three symbols (e.g., symbols 0-2) in the time domain and across twenty-four RBs (e.g., RBs 0-23) in the frequency domain, wherein the twenty-four RBs occupy 5 MHz in total bandwidth. As shown, each REG bundle may include 6 REGs mapped across three symbols in the time domain and across two RBs in the frequency domain. For example, REG bundle 0 is mapped across symbols 0-2 and across RBs 0-1. Additionally, REG bundles 0-11 are shown as interleaved in the frequency domain, wherein REG bundles with consecutive indexes are not adjacent another across the frequency domain.

[0124] Alternatively, as shown by reference number 720, for example, a CORESET configuration may include REG bundles that occupy more than 3 symbols to support a UE device type with a maximum bandwidth of less than 5 MHz (e.g., as small as 1.08 MHz). For example, as shown by reference number 720, equivalent REG bundles 0-11 may be mapped across twelve symbols (e.g., symbols 0-11) in the time domain and across six RBs (e.g., RBs 0- 5) in the frequency domain. In this way, the size of each REG bundle in reference number 710 is maintained, where each REG bundle of reference number 720 is mapped across three symbols in the time domain and across two RBs in the frequency domain. The CORESET configuration of reference number 720 thus includes a total of 72 REGs that is equivalent to the total of 72 REGs included in the CORESET configuration of reference number 710. In some aspects, as shown by reference number 720, the CORESET configuration (e.g., RBs 0-5) may occupy 1.08 MHz in the frequency domain to encompass a relatively narrower bandwidth when compared tothe CORESET configuration shown by reference number 710. The CORESET configuration shown by reference number 720 may, for example, enable compatibility with UE 120 device types that operate on a relatively narrow bandwidth when compared to the CORESET configuration bandwidth shown by reference number 710.

[0125] In some aspects, the CORESET configuration of reference number 720 may include interleaving in the time domain among REG bundles. In some aspects, because the CORESET configuration of reference number 720 includes REG bundles mapped across twelve symbols in the time domain, there is more opportunity for interleaving in the time domain when compared, for example, to the CORESET configuration in reference number 710 that includes REG bundles mapped across three symbols in the time domain.

[0126] Alternatively, as shown by reference number 730, for example, a CORESET configuration may include REG bundles that occupy more than 3 symbols to support a UE device type with a maximum bandwidth of less than 5 MHz (e.g., as small as 1.08 MHz). For example, as shown by reference number 730, equivalent REG bundles 0-11 may be mapped across twelve symbols (e.g., symbols 0-11) in the time domain and across six RBs (e.g., RBs 0- 5) in the frequency domain. In this way, the size of each REG bundle in reference number 710 is maintained, where each REG bundle of reference number 730 is mapped across three symbols in the time domain and across two RBs in the frequency domain. For example, and as shown by reference number 730, a UE may first capture REG bundle 1 and may subsequently capture REG bundle 0 and REG bundle 2. The CORESET configuration shown by reference number 730 thus includes a total of 72 REGs that is equivalent to the total of 72 REGs included in the CORESET configuration shown by reference number 710. In some aspects, as shown by reference number 730, the CORESET configuration (e.g., RBs 0-5) may occupy 1.08 MHz in the frequency domain to encompass a relatively narrower bandwidth when compared to the CORESET configuration of reference number 710. The CORESET configuration shown by reference number 730 may, for example, enable compatibility with UE 120 device types that operate on a relatively narrow bandwidth when compared to the CORESET configuration bandwidth shown by reference number 710.

[0127] In some aspects, the CORESET configuration of reference number 730 may include interleaving in the time domain among REG bundles. In some aspects, because the CORESET configuration of reference number 730 includes REG bundles mapped across twelve symbols in the time domain, there is more opportunity for interleaving in the time domain when compared, for example, to the CORESET configuration in reference number 710 that includes REG bundles mapped across three symbols in the time domain.

[0128] Additionally, in the CORESET configurations shown by reference numbers 720 and 730, a CORESET configuration may enable intra-slot or inter-slot DMRS bundling of the REG bundles to improve channel estimation for different UE 120 device types.

[0129] Accordingly, a CORESET configuration that supports, for example, mapping REG bundles across more than three symbols in the time domain may span a smaller bandwidth than a CORESET configuration limited to a maximum of three symbols, which may enable support for different UE 120 device types (e.g., UEs 120 supporting different maximum bandwidths). For example, CORESET configurations for a wideband UE 120 device type may be adaptable to a CORESET configuration for a narrowband UE 120 device type and vice versa, thus enabling coexistence between different UE 120 device types.

[0130] As indicated above, Fig. 7 is provided as an example. Other examples may differ from what is described with respect to Fig. 7.

[0131] Fig. 8 is a diagram illustrating an example 800 associated with CORESET configurations for different device types, in accordance with the present disclosure. As shown in Fig. 8, example 800 includes an example legacy CORESET configuration having CCEs and / or REG bundles limited to three symbols in a time domain and flexible CORESET configurations that may support different UE device types (e.g., by enabling CCEs and / or REG bundles to occupy more than three symbols in a slot). In some aspects, example 800 illustrates CORESET configurations that may be transmitted from a network node 110 to one or more UEs 120 in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0132] As shown by reference number 810, an example legacy CORESET configuration includes twelve REG bundles (e.g., REG bundles 0-11) mapped across three symbols (e.g., symbols 0-2) in the time domain and across twenty-four RBs (e.g., RBs 0-23) in the frequency domain, wherein the twenty-four RBs occupy 5 MHz in total bandwidth. Each REG bundle may include REGs mapped across three symbols and across two RBs. As shown, each REG bundle may include 6 REGs mapped across three symbols in the time domain and across two RBs in the frequency domain. For example, REG bundle 0 is mapped across symbols 0-2 and across RBs 0-1. Additionally, the CORESET configuration illustrated in reference number 810 is not interleaved across the frequency domain where, for example, the PDCCH is localized. Alternatively, as shown by reference number 820, for example, a CORESET configuration may include REG bundles that occupy more than 3 symbols to support a UE device type with a maximum bandwidth of less than 5 MHz (e.g., as small as 1.08 MHz). For example, as shown by reference number 820, equivalent REG bundles 0-11 may be mapped across twelve symbols (e.g., symbols 0-11) in the time domain and across six RBs (e.g., RBs 0-5) in the frequency domain. In this way, the size of each REG bundle in reference number 810 is maintained, where each REG bundle of reference number 820 is mapped across three symbols in the time domain and across two RBs in the frequency domain. The CORESET configuration of reference number 820 thus includes a total of 72 REGs that is equivalent to the total of 72 REGs included in the CORESET configuration of reference number 810. In some aspects of referencenumber 820, the CORESET configuration (e.g., RBs 0-5) may occupy E08 MHz in the frequency domain to encompass a relatively narrower bandwidth when compared to the CORESET configuration of reference number 810. The CORESET configuration of reference number 820 may, for example, enable compatibility with UE 120 device types that operate on a relatively narrow bandwidth when compared to the CORESET configuration bandwidth in reference number 810.

[0133] In some aspects, when a UE 120 frequency band overlaps with the REG bundles for a common set of REG bundles (e.g., a BWP allocated to a UE BWP covers the REG bundles), then interleaving across a time domain may be unnecessary, as illustrated in the CORESET configuration of reference number 820.

[0134] Alternatively, as shown by reference number 830, for example, a CORESET configuration may include interleaved REG bundles that occupy more than 3 symbols to support a UE device type with a maximum bandwidth of less than 5 MHz (e.g., as small as 1.08 MHz). For example, as shown by reference number 830, equivalent REG bundles 0-11 may be mapped across twelve symbols (e.g., symbols 0-11) in the time domain and across six RBs (e.g., RBs 0- 5) in the frequency domain. In this way, the size of each REG bundle in reference number 810 is maintained, where each REG bundle of reference number 830 is mapped across three symbols in the time domain and across two RBs in the frequency domain. For example, and as shown by reference number 830, a UE may first capture REG bundle 6 and may subsequently capture REG bundle 0, REG bundle 1, and REG bundle 2. The CORESET configuration of reference number 830 thus includes a total of 72 REGs that is equivalent to the total of 72 REGs included in the CORESET configuration of reference number 810. In some aspects of reference number 830, the CORESET configuration (e.g., RBs 0-5) may occupy 1.08 MHz in the frequency domain to encompass a relatively narrower bandwidth when compared to the CORESET configuration of reference number 810. The CORESET configuration of reference number 830 may, for example, enable compatibility with UE 120 device types that operate on a relatively narrow bandwidth when compared to the CORESET configuration bandwidth in reference number 810.

[0135] In some aspects, the CORESET configuration of reference number 830 may include interleaving in the time domain among REG bundles (e.g., when a BWP allocated to a UE 120 does not cover a common set of REG bundles with the legacy CORESET configuration of reference number 810). In some aspects, because the CORESET configuration of reference number 830 includes REG bundles mapped across twelve symbols in the time domain, there is more opportunity for interleaving in the time domain when compared, for example, to the CORESET configuration in reference number 810 that includes REG bundles mapped across three symbols in the time domain.

[0136] Additionally, in the CORESET configurations shown by reference numbers 820 and 830, a CORESET configuration may enable intra-slot or inter-slot DMRS bundling of the REG bundles to improve channel estimation for different UE 120 device types.

[0137] Accordingly, a CORESET configuration that supports, for example, mapping REG bundles across more than three symbols in the time domain may span a smaller bandwidth than a CORESET configuration limited to a maximum of three symbols, which may enable support for different UE 120 device types (e.g., UEs 120 supporting different maximum bandwidths). For example, CORESET configurations for a wideband UE 120 device type may be adaptable to a CORESET configuration for a narrowband UE 120 device type and vice versa, thus enabling coexistence between different UE 120 device types.

[0138] As indicated above, Fig. 8 is provided as an example. Other examples may differ from what is described with respect to Fig. 8.

[0139] Fig. 9 is a diagram illustrating an example 900 associated with CORESET configurations for different device types, in accordance with the present disclosure. As shown in Fig. 9, example 900 includes an example legacy CORESET configuration having CCEs and / or REG bundles limited to two symbols in a time domain and flexible CORESET configurations that may support different UE device types (e.g., by enabling CCEs and / or REG bundles to occupy more than two symbols in a slot). In some aspects, example 900 illustrates CORESET configurations that may be transmitted from a network node 110 to one or more UEs 120 in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0140] As shown by reference number 910, an example legacy CORESET configuration includes REG bundles mapped across two symbols (e.g., symbols 0-1) in the time domain and across twenty-four RBs (e.g., RBs 0-23) in the frequency domain, wherein the twenty-four RBs occupy 5MHz in total bandwidth. As shown, each REG bundle may include REGs mapped across two symbols in the time domain and across three RBs in the frequency domain. For example, REG bundle 0 is illustrated as mapped across symbols 0-1 and across RBs 0-2.Additionally, the REG bundles are shown as interleaved in the frequency domain, wherein REG bundles with consecutive indexes are not adjacent another across the frequency domain.

[0141] Alternatively, as shown by reference number 920, for example, a CORESET configuration may include REG bundles that occupy more than 3 symbols to support a UE device type with a maximum bandwidth of less than 5 MHz (e.g., as small as 1.08 MHz). For example, as shown by reference number 920, equivalent REG bundles may be mapped across twelve symbols (e.g., symbols 0-11) in the time domain and across six RBs (e.g., RBs 0-5) in the frequency domain. In this way, the size of each REG bundle is maintained between the CORESET configuration of reference number 910 and the CORESET configuration ofreference number 920, where each REG bundle is mapped across two symbols in the time domain and across three RBs in the frequency domain. The CORESET configuration of reference number 920 may include a total of 72 REGs. In some aspects of reference number 920, the CORESET configuration (e.g., RBs 0-5) may occupy 1.08 MHz in the frequency domain to encompass a relatively narrower bandwidth when compared to the CORESET configuration of reference number 910. The CORESET configuration of reference number 920 may, for example, enable compatibility with UE 120 device types that operate on a relatively narrow bandwidth when compared to the CORESET configuration bandwidth in reference number 910.

[0142] In some aspects, the CORESET configuration of reference number 920 may include interleaving in the time domain among REG bundles. In some aspects, because the CORESET configuration of reference number 920 includes REG bundles mapped across twelve symbols in the time domain, there is more opportunity for interleaving in the time domain when compared, for example, to the CORESET configuration in reference number 910 that includes REG bundles mapped across two symbols in the time domain.

[0143] Alternatively, as shown by reference number 930, for example, a non-interleaved CORESET configuration may include REG bundles that occupy more than 3 symbols to support a UE device type with a maximum bandwidth of less than 5 MHz (e.g., as small as 1.08 MHz). For example, as shown by reference number 930, equivalent REG bundles may be mapped across twelve symbols (e.g., symbols 0-11) in the time domain and across six RBs (e.g., RBs 0- 5) in the frequency domain. In this way, the size of each REG bundle is maintained between the CORESET configuration of reference number 910 and the CORESET configuration of reference number 930, where each REG bundle is mapped across two symbols in the time domain and across three RBs in the frequency domain. The CORESET configuration of reference number 930 may include a total of 72 REGs. In some aspects of reference number 930, the CORESET configuration (e.g., RBs 0-5) may occupy 1.08 MHz in the frequency domain to encompass a relatively narrower bandwidth when compared to the CORESET configuration of reference number 910. The CORESET configuration of reference number 930 may, for example, enable compatibility with UE 120 device types that operate on a relatively narrowband when compared to the CORESET configuration bandwidth in reference number 910.

[0144] In some aspects, the CORESET configuration of reference number 930 does not include interleaving in the time domain among REG bundles.

[0145] Additionally, the CORESET configurations shown by reference numbers 920 and 930, a CORESET configuration may enable intra-slot or inter-slot DMRS bundling of the REG bundles to improve channel estimation for different UE 120 device types.

[0146] Accordingly, a CORESET configuration that supports, for example, mapping REG bundles across more than three symbols in the time domain may span a smaller bandwidth than a CORESET configuration limited to a maximum of two symbols, which may enable support for different UE 120 device types (e.g., UEs 120 supporting different maximum bandwidths). For example, CORESET configurations for a wideband UE 120 device type may be adaptable to a CORESET configuration for a narrowband UE 120 device type and vice versa, thus enabling coexistence between different UE 120 device types.

[0147] As indicated above, Fig. 9 is provided as an example. Other examples may differ from what is described with respect to Fig. 9.

[0148] Fig. 10 is a diagram illustrating an example 1000 associated with CORESET configurations for different device types, in accordance with the present disclosure. As shown in Fig. 10, example 1000 includes an example legacy CORESET configuration having CCEs and / or REG bundles limited to one symbol in a time domain and flexible CORESET configurations that may support different UE device types (e.g., by enabling CCEs and / or REG bundles to occupy more than three symbols in a slot, with up to fourteen symbols.) In some aspects, example 1000 illustrates CORESET configurations that may be transmitted from a network node 110 to one or more UEs 120 in a wireless network, such as wireless network 100. The network node 110 and the UE 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0149] As shown by reference number 1010, an example legacy CORESET configuration includes REG bundles mapped across one symbol (e.g., symbol 0) in the time domain and across twenty-four RBs (e.g., RBs 0-23) in the frequency domain, wherein the twenty-four RBs occupy 5MHz in total bandwidth. As shown, each REG bundle may include REGs mapped across one symbol in the time domain and across 6 RBs in the frequency domain. For example, REG bundle 0 is mapped across symbol 0 and across RBs 0-5. Additionally, REG bundles are shown as interleaved in the frequency domain, wherein REG bundles with consecutive indexes are not adjacent another across the frequency domain.

[0150] Alternatively, as shown by reference number 1020, for example, a CORESET configuration may include REG bundles that occupy more than 3 symbols to support a UE device type with a maximum bandwidth of less than 5 MHz (e.g., as small as 1.08 MHz). For example, as shown by reference number 1020, equivalent REG bundles may be mapped across up to fourteen symbols (e.g., symbols 0-13) in the time domain and across six RBs (e.g., RBs 0- 5) in the frequency domain. In this way, the size of each REG bundle is maintained between the CORESET configuration of reference number 1010 and the CORESET configuration of reference number 1020, where each REG bundle is mapped across one symbol in the time domain and across six RBs in the frequency domain. The CORESET configuration of referencenumber 1020 thus includes a total of 84 REGs. In some aspects, the CORESET configuration of reference number 1020 may alternatively include up to twelve symbols, thus including a total of 72 REGs. In some aspects of reference number 1020, the CORESET configuration (e.g., RBs 0-5) may occupy 1.08 MHz in the frequency domain to encompass a relatively narrower bandwidth when compared to the CORESET configuration of reference number 1010. The CORESET configuration of reference number 1020 may, for example, enable compatibility with UE 120 device types that operate on a relatively narrowband when compared to the CORESET configuration bandwidth in reference number 1010.

[0151] In some aspects, the CORESET configuration of reference number 1020 may include interleaving in the time domain among REG bundles. In some aspects, because the CORESET configuration of reference number 1020 includes REG bundles mapped across up to fourteen symbols in the time domain, there is more opportunity for interleaving in the time domain when compared, for example, to the CORESET configuration in reference number 1010 that includes REG bundles mapped across one symbol in the time domain.

[0152] Alternatively, as shown by reference number 1030, for example, a CORESET configuration may include REG bundles that occupy more than 3 symbols to support a UE device type with a maximum bandwidth of less than 5 MHz (e.g., as small as 1.08 MHz). For example, as shown by reference number 1030, equivalent REG bundles may be mapped across up to fourteen symbols (e.g., symbols 0-13) in the time domain and across six RBs (e.g., RBs 0- 5) in the frequency domain. In this way, the size of each REG bundle is maintained between the CORESET configuration of reference number 1010 and the CORESET configuration of reference number 1030, where each REG bundle is mapped across one symbol in the time domain and across six RBs in the frequency domain. The CORESET configuration of reference number 1030 thus includes a total of 84 REGs. In some aspects, the CORESET configuration of reference number 1030 may alternatively include up to twelve symbols, thus including a total of 72 REGs. In some aspects of reference number 1030, the CORESET configuration (e.g., RBs 0-5) may occupy 1.08 MHz in the frequency domain to encompass a relatively narrower bandwidth when compared to the CORESET configuration of reference number 1010. The CORESET configuration of reference number 1030 may, for example, enable compatibility with UE 120 device types that operate on a relatively narrow bandwidth when compared to the CORESET configuration bandwidth in reference number 1010.

[0153] In some aspects, the CORESET configuration of reference number 1030 does not include interleaving in the time domain among REG bundles.

[0154] Additionally, in the CORESET configurations shown by reference numbers 1020 and 1030, a CORESET configuration may enable intra-slot or inter-slot DMRS bundling of the REG bundles to improve channel estimation for different UE 120 device types.

[0155] Accordingly, a CORESET configuration that supports, for example, mapping REG bundles across more than one symbol in the time domain may span a smaller bandwidth than a CORESET configuration limited to a maximum of one symbol, which may enable support for different UE 120 device types (e.g., UEs 120 supporting different maximum bandwidths). For example, CORESET configurations for a wideband UE 120 device type may be adaptable to a CORESET configuration for a narrowband UE 120 device type and vice versa, thus enabling coexistence between different UE 120 device types.

[0156] As indicated above, Fig. 10 is provided as an example. Other examples may differ from what is described with respect to Fig. 10.

[0157] Fig. 11 is a diagram illustrating an example 1100 associated with CORESET configurations for different device types, in accordance with the present disclosure. As shown in Fig. 11, example 1100 includes communication between, for example, a network node 110 and a first UE device type 1110 and communication between the network node 110 and a second UE device type 1120. In some aspects, the first UE device type 1110 and the second UE device type 1120 may share one or more CCEs in a shared time domain.

[0158] The network node 110 and the UE(s) 120 of the first UE device type 1110 and the UE(s) 120 of the second UE device type 1120 may be included in a wireless network, such as wireless network 100. The network node 110 and the UEs 120 may communicate via a wireless access link, which may include an uplink and a downlink.

[0159] In some aspects, the first UE device type 1110 may include a UE 120 operating in a wideband configuration and the second UE device type 1120 may include a UE 120 operating in a narrowband configuration. The first UE device type 1110 and the second UE device type 1120 may share one or more CCEs in at least one symbol of a time domain. For example, the first UE device type 1110 and the second UE device type 1120 may share one or more CCEs 1130 in the first symbol or in the first two symbols of a time domain.

[0160] In some aspects, for the non-shared portion of the time domain, a second UE device type 1120 (e.g., a narrowband UE 120 device) may utilize the exemplary techniques illustrated in Figs. 6-10 for CORESET configurations to support PDCCH communications in the extended CORESET. Additionally, in some aspects, the PDCCH candidate locations in the extended CORESET (e.g., the extended time domain portion) of, for example, a narrowband device may depend on the slot index, RNTI, or other suitable parameter associated with the UE 120 device type.

[0161] Accordingly, CORESET configurations that include sharing of CCEs may facilitate network compatibility with UEs 120 of different device types. For example, a CORESET configuration may enable a narrowband device to receive a PDCCH communication in a CCE shared with a wideband device, or else the narrowband device may receive a PDCCHcommunication in non-shared CCE located in an extended time domain (e.g., an extended CORESET). Additionally, the sharing of CCEs between different UE 120 device types may reduce network congestion and may conserve frequency, power, and / or processing resources at a UE 120 and / or a network node 110.

[0162] As indicated above, Fig. 11 is provided as an example. Other examples may differ from what is described with respect to Fig. 11.

[0163] Fig. 12 is a diagram illustrating an example process 1200 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 1200 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with CORESET configurations for different device types.

[0164] As shown in Fig. 12, in some aspects, process 1200 may include receiving an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type (block 1210). For example, the UE (e.g., using reception component 1402 and / or communication manager 1406, depicted in Fig. 14) may receive an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type, as described above.

[0165] As further shown in Fig. 12, in some aspects, process 1200 may include monitoring at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type (block 1220). For example, the UE (e.g., using communication manager 1406, depicted in Fig. 14) may monitor at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type, as described above.

[0166] Process 1200 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0167] In a first aspect, the one or more CORESET parameters configure more than three symbols in a time domain.

[0168] In a second aspect, alone or in combination with the first aspect, the one or more CORESET parameters configure up to 12 or 14 symbols per slot based at least in part on an REG bundle size.

[0169] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more CORESET parameters configure non-interleaving among at least one of REG bundles or CCEs in at least one of a frequency domain or a time domain.

[0170] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the one or more CORESET parameters configure interleaving among at least one of REG bundles or CCEs in at least one of a frequency domain or a time domain.

[0171] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the one or more CORESET parameters configure an aggregation level up to 12 or 14 within a slot based at least in part on an REG bundle size.

[0172] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the CORESET configuration is compatible with the UE device type and with a different UE device type.

[0173] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the one or more CORESET parameters configure slot-level repetitions.

[0174] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the one or more CORESET parameters configure frequency hopping.

[0175] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the one or more CORESET parameters configure an intra-slot or an inter-slot DMRS bundling pattern.

[0176] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the one or more CORESET parameters configure sharing of at least one CCE between the UE device type and one or more other UE device types in one or more initial symbols.

[0177] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the at least one PDCCH candidate location is based on an index associated with a TTI or an identifier associated with the UE.

[0178] Although F ig . 12 shows example blocks of process 1200, in some aspects, process 1200 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 12. Additionally, or alternatively, two or more of the blocks of process 1200 may be performed in parallel.

[0179] Fig. 13 is a diagram illustrating an example process 1300 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process 1300 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with control resource set configurations for different device types.

[0180] As shown in Fig. 13, in some aspects, process 1300 may include transmitting, to a UE, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type (block 1310). For example, the network node (e.g., using transmission component 1504 and / or communication manager 1506, depicted in Fig. 15) may transmit, to a UE, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type, as described above.

[0181] As further shown in Fig. 13, in some aspects, process 1300 may include transmitting, to the UE, a PDCCH communication in at least one PDCCH candidate location based at least inpart on the CORESET configuration associated with the UE device type (block 1320). For example, the network node (e.g., using transmission component 1504 and / or communication manager 1506, depicted in Fig. 15) may transmit, to the UE, a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type, as described above.

[0182] Process 1300 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0183] In a first aspect, the one or more CORESET parameters configure more than three symbols in a time domain.

[0184] In a second aspect, alone or in combination with the first aspect, the one or more CORESET parameters configure up to 12 or 14 symbols per slot based at least in part on an REG bundle size.

[0185] In a third aspect, alone or in combination with one or more of the first and second aspects, the one or more CORESET parameters configure non-interleaving among at least one of REG bundles or CCEs in at least one of a frequency domain or a time domain.

[0186] In a fourth aspect, alone or in combination with one or more of the first through third aspects, the one or more CORESET parameters configure interleaving among at least one of REG bundles or CCEs in at least one of a frequency domain or a time domain.

[0187] In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the one or more CORESET parameters configure an aggregation level up to 12 or 14 within a slot based at least in part on an REG bundle size.

[0188] In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the CORESET configuration is compatible with the UE device type and with a different UE device type.

[0189] In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the one or more CORESET parameters configure slot-level repetitions.

[0190] In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the one or more CORESET parameters configure frequency hopping.

[0191] In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the one or more CORESET parameters configure an intra-slot or an inter-slot DMRS bundling pattern.

[0192] In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the one or more CORESET parameters configure sharing of at least one CCE between the UE device type and one or more other UE device types in one or more initial symbols.

[0193] In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, the at least one PDCCH candidate location is based on an index associated with a TTI or an identifier associated with the UE.

[0194] Although Fig. 13 shows example blocks of process 1300, in some aspects, process 1300 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Fig. 13. Additionally, or alternatively, two or more of the blocks of process 1300 may be performed in parallel.

[0195] Fig. 14 is a diagram of an example apparatus 1400 for wireless communication, in accordance with the present disclosure. The apparatus 1400 may be a UE, or a UE may include the apparatus 1400. In some aspects, the apparatus 1400 includes a reception component 1402, a transmission component 1404, and / or a communication manager 1406, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 1406 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 1400 may communicate with another apparatus 1408, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1402 and the transmission component 1404.

[0196] In some aspects, the apparatus 1400 may be configured to perform one or more operations described herein in connection with Figs. 6-11. Additionally, or alternatively, the apparatus 1400 may be configured to perform one or more processes described herein, such as process 1200 of Fig. 12. In some aspects, the apparatus 1400 and / or one or more components shown in Fig. 14 may include one or more components of the UE described in connection with Fig. 1 and Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 14 may be implemented within one or more components described in connection with Fig. 1 and Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0197] The reception component 1402 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1408. The reception component 1402 may provide received communications to one or more other components of the apparatus 1400. In some aspects, the reception component 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may providethe processed signals to the one or more other components of the apparatus 1400. In some aspects, the reception component 1402 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, one or more memories, or a combination thereof, of the UE described in connection with Fig. 1 and Fig. 2.

[0198] The transmission component 1404 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1408. In some aspects, one or more other components of the apparatus 1400 may generate communications and may provide the generated communications to the transmission component 1404 for transmission to the apparatus 1408. In some aspects, the transmission component 1404 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1408. In some aspects, the transmission component 1404 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or a combination thereof, of the UE described in connection with Fig. 1 and Fig. 2. In some aspects, the transmission component 1404 may be co-located with the reception component 1402 in one or more transceivers.

[0199] The communication manager 1406 may support operations of the reception component 1402 and / or the transmission component 1404. For example, the communication manager 1406 may receive information associated with configuring reception of communications by the reception component 1402 and / or transmission of communications by the transmission component 1404. Additionally, or alternatively, the communication manager 1406 may generate and / or provide control information to the reception component 1402 and / or the transmission component 1404 to control reception and / or transmission of communications.

[0200] The reception component 1402 may receive an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The communication manager 1406 may monitor at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0201] The number and arrangement of components shown in Fig. 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 14. Furthermore, two or more components shown in Fig. 14 may be implemented within a single component, or a single component shown in Fig. 14 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 14 may performone or more functions described as being performed by another set of components shown in Fig. 14.

[0202] Fig. 15 is a diagram of an example apparatus 1500 for wireless communication, in accordance with the present disclosure. The apparatus 1500 may be a network node, or a network node may include the apparatus 1500. In some aspects, the apparatus 1500 includes a reception component 1502, a transmission component 1504, and / or a communication manager 1506, which may be in communication with one another (for example, via one or more buses and / or one or more other components). In some aspects, the communication manager 1506 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 1500 may communicate with another apparatus 1508, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component 1502 and the transmission component 1504.

[0203] In some aspects, the apparatus 1500 may be configured to perform one or more operations described herein in connection with Figs. 6-11. Additionally, or alternatively, the apparatus 1500 may be configured to perform one or more processes described herein, such as process 1300 of Fig. 13. In some aspects, the apparatus 1500 and / or one or more components shown in Fig. 15 may include one or more components of the network node described in connection with Fig. 1 and Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 15 may be implemented within one or more components described in connection with Fig. 1 and Fig. 2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

[0204] The reception component 1502 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 1508. The reception component 1502 may provide received communications to one or more other components of the apparatus 1500. In some aspects, the reception component 1502 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus 1500. In some aspects, the reception component 1502 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers / processors, one or more memories, or a combination thereof, of the network node described in connection with Fig. 1 and Fig. 2. In some aspects, the reception component 1502 and / or the transmission component 1504 may include or may beincluded in a network interface. The network interface may be configured to obtain and / or output signals for the apparatus 1500 via one or more communications links, such as a backhaul link, a midhaul link, and / or a fronthaul link.

[0205] The transmission component 1504 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 1508. In some aspects, one or more other components of the apparatus 1500 may generate communications and may provide the generated communications to the transmission component 1504 for transmission to the apparatus 1508. In some aspects, the transmission component 1504 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus 1508. In some aspects, the transmission component 1504 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or a combination thereof, of the network node described in connection with Fig. 1 and Fig. 2. In some aspects, the transmission component 1504 may be co-located with the reception component 1502 in one or more transceivers.

[0206] The communication manager 1506 may support operations of the reception component 1502 and / or the transmission component 1504. For example, the communication manager 1506 may receive information associated with configuring reception of communications by the reception component 1502 and / or transmission of communications by the transmission component 1504. Additionally, or alternatively, the communication manager 1506 may generate and / or provide control information to the reception component 1502 and / or the transmission component 1504 to control reception and / or transmission of communications.

[0207] The transmission component 1504 may transmit, to a UE, an indication of a CORESET configuration that indicates one or more CORESET parameters associated with a UE device type. The transmission component 1504 may transmit, to the UE, a PDCCH communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0208] The number and arrangement of components shown in Fig. 15 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Fig. 15. Furthermore, two or more components shown in Fig. 15 may be implemented within a single component, or a single component shown in Fig. 15 may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown in Fig. 15 may perform one or more functions described as being performed by another set of components shown in Fig. 15.

[0209] The following provides an overview of some Aspects of the present disclosure:

[0210] Aspect 1 : A method of wireless communication performed by a user equipment (UE), comprising: receiving an indication of a control resource set (CORESET) configuration that indicates one or more CORESET parameters associated with a UE device type; and monitoring at least one physical downlink control channel (PDCCH) candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0211] Aspect 2: The method of Aspect 1, wherein the one or more CORESET parameters configure more than three symbols in a time domain.

[0212] Aspect 3: The method of Aspect 2, wherein the one or more CORESET parameters configure up to 12 or 14 symbols per slot based at least in part on a resource element group (REG) bundle size.

[0213] Aspect 4: The method of any of Aspects 1-3, wherein the one or more CORESET parameters configure non-interleaving among at least one of resource element group (REG) bundles or control channel element (CCEs) in at least one of a frequency domain or a time domain.

[0214] Aspect 5: The method of any of Aspects 1-4, wherein the one or more CORESET parameters configure interleaving among at least one of resource element group (REG) bundles or control channel element (CCEs) in at least one of a frequency domain or a time domain.

[0215] Aspect 6: The method of any of Aspects 1-5, wherein the one or more CORESET parameters configure an aggregation level up to 12 or 14 within a slot based at least in part on a resource element group (REG) bundle size.

[0216] Aspect 7: The method of any of Aspects 1-6, wherein the CORESET configuration is compatible with the UE device type and with a different UE device type.

[0217] Aspect 8: The method of any of Aspects 1-7, wherein the one or more CORESET parameters configure slot-level repetitions.

[0218] Aspect 9: The method of any of Aspects 1-8, wherein the one or more CORESET parameters configure frequency hopping.

[0219] Aspect 10: The method of any of Aspects 1-9, wherein the one or more CORESET parameters configure an intra-slot or an inter-slot demodulation reference signal (DMRS) bundling pattern.

[0220] Aspect 11: The method of any of Aspects 1-10, wherein the one or more CORESET parameters configure sharing of at least one control channel element (CCE) between the UE device type and one or more other UE device types in one or more initial symbols.

[0221] Aspect 12: The method of any of Aspects 1-11, wherein the at least one PDCCH candidate location is based on an index associated with a transmission time interval (TTI) or an identifier associated with the UE.

[0222] Aspect 13: A method of wireless communication performed by a network node, comprising: transmitting, to a user equipment (UE), an indication of a control resource set (CORESET) configuration that indicates one or more CORESET parameters associated with a UE device type; and transmitting, to the UE, a physical downlink control channel (PDCCH) communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

[0223] Aspect 14: The method of Aspect 13, wherein the one or more CORESET parameters configure more than three symbols in a time domain.

[0224] Aspect 15: The method of Aspect 14, wherein the one or more CORESET parameters configure up to 12 or 14 symbols per slot based at least in part on a resource element group (REG) bundle size.

[0225] Aspect 16: The method of any of Aspects 13-15, wherein the one or more CORESET parameters configure non-interleaving among at least one of resource element group (REG) bundles or control channel element (CCEs) in at least one of a frequency domain or a time domain.

[0226] Aspect 17: The method of any of Aspects 13-16, wherein the one or more CORESET parameters configure interleaving among at least one of resource element group (REG) bundles or control channel element (CCEs) in at least one of a frequency domain or a time domain.

[0227] Aspect 18: The method of any of Aspects 13-17, wherein the one or more CORESET parameters configure an aggregation level up to 12 or 14 within a slot based at least in part on a resource element group (REG) bundle size.

[0228] Aspect 19: The method of any of Aspects 13-18, wherein the CORESET configuration is compatible with the UE device type and with a different UE device type.

[0229] Aspect 20: The method of any of Aspects 13-19, wherein the one or more CORESET parameters configure slot-level repetitions.

[0230] Aspect 21: The method of any of Aspects 13-20, wherein the one or more CORESET parameters configure frequency hopping.

[0231] Aspect 22: The method of any of Aspects 13-21, wherein the one or more CORESET parameters configure an intra-slot or an inter-slot demodulation reference signal (DMRS) bundling pattern.

[0232] Aspect 23: The method of any of Aspects 13-22, wherein the one or more CORESET parameters configure sharing of at least one control channel element (CCE) between the UE device type and one or more other UE device types in one or more initial symbols.

[0233] Aspect 24: The method of any of Aspects 13-23, wherein the at least one PDCCH candidate location is based on an index associated with a transmission time interval (TTI) or an identifier associated with the UE.

[0234] Aspect 25: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-24.

[0235] Aspect 26: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-24.

[0236] Aspect 27: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-24.

[0237] Aspect 28: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-24.

[0238] Aspect 29: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-24.

[0239] Aspect 30: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-24.

[0240] Aspect 31 : An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-24.

[0241] The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

[0242] As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent thatsystems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.

[0243] As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.

[0244] As used herein, a phrase referring to “at least one of’ a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c).

[0245] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more.” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more.” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has,” “have,” “having,” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B). Further, the phrase “based on” is intended to mean “based on or otherwise in association with” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or,” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of’). It should be understood that “one or more” is equivalent to “at least one.”

[0246] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claimsor disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.

Claims

WHAT IS CLAIMED IS:

1. A method of wireless communication performed by a user equipment (UE), comprising: receiving an indication of a control resource set (CORESET) configuration that indicates one or more CORESET parameters associated with a UE device type; and monitoring at least one physical downlink control channel (PDCCH) candidate location based at least in part on the CORESET configuration associated with the UE device type.

2. The method of claim 1, wherein the one or more CORESET parameters configure more than three symbols in a time domain.

3. The method of claim 2, wherein the one or more CORESET parameters configure up to 12 or 14 symbols per slot based at least in part on a resource element group (REG) bundle size.

4. The method of claim 1, wherein the one or more CORESET parameters configure noninterleaving among at least one of resource element group (REG) bundles or control channel element (CCEs) in at least one of a frequency domain or a time domain.

5. The method of claim 1, wherein the one or more CORESET parameters configure interleaving among at least one of resource element group (REG) bundles or control channel element (CCEs) in at least one of a frequency domain or a time domain.

6. The method of claim 1, wherein the one or more CORESET parameters configure an aggregation level up to 12 or 14 within a slot based at least in part on a resource element group (REG) bundle size.

7. The method of claim 1, wherein the CORESET configuration is compatible with the UE device type and with a different UE device type.

8. The method of claim 1, wherein the one or more CORESET parameters configure slotlevel repetitions.

9. The method of claim 1, wherein the one or more CORESET parameters configure frequency hopping.

10. The method of claim 1, wherein the one or more CORESET parameters configure an intra-slot or an inter-slot demodulation reference signal (DMRS) bundling pattern.

11. The method of claim 1, wherein the one or more CORESET parameters configure sharing of at least one control channel element (CCE) between the UE device type and one or more other UE device types in one or more initial symbols.

12. The method of claim 1, wherein the at least one PDCCH candidate location is based on an index associated with a transmission time interval (TTI) or an identifier associated with the UE.

13. A method of wireless communication performed by a network node, comprising: transmitting, to a user equipment (UE), an indication of a control resource set(CORESET) configuration that indicates one or more CORESET parameters associated with a UE device type; and transmitting, to the UE, a physical downlink control channel (PDCCH) communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

14. The method of claim 13, wherein the one or more CORESET parameters configure more than three symbols in a time domain.

15. The method of claim 14, wherein the one or more CORESET parameters configure up to 12 or 14 symbols per slot based at least in part on a resource element group (REG) bundle size.

16. The method of claim 13, wherein the one or more CORESET parameters configure noninterleaving among at least one of resource element group (REG) bundles or control channel element (CCEs) in at least one of a frequency domain or a time domain.

17. The method of claim 13, wherein the one or more CORESET parameters configure interleaving among at least one of resource element group (REG) bundles or control channel element (CCEs) in at least one of a frequency domain or a time domain.

18. The method of claim 13, wherein the one or more CORESET parameters configure an aggregation level up to 12 or 14 within a slot based at least in part on a resource element group (REG) bundle size.

19. The method of claim 13, wherein the CORESET configuration is compatible with the UE device type and with a different UE device type.

20. The method of claim 13, wherein the one or more CORESET parameters configure slotlevel repetitions.

21. The method of claim 13, wherein the one or more CORESET parameters configure frequency hopping.

22. The method of claim 13, wherein the one or more CORESET parameters configure an intra-slot or an inter-slot demodulation reference signal (DMRS) bundling pattern.

23. The method of claim 13, wherein the one or more CORESET parameters configure sharing of at least one control channel element (CCE) between the UE device type and one or more other UE device types in one or more initial symbols.

24. The method of claim 13, wherein the at least one PDCCH candidate location is based on an index associated with a transmission time interval (TTI) or an identifier associated with the UE.

25. A user equipment (UE) for wireless communication, comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to cause the UE to: receive an indication of a control resource set (CORESET) configuration that indicates one or more CORESET parameters associated with a UE device type; and monitor at least one physical downlink control channel (PDCCH) candidate location based at least in part on the CORESET configuration associated with the UE device type.

26. The UE of claim 25, wherein the one or more CORESET parameters configure more than three symbols in a time domain.

27. The UE of claim 25, wherein the one or more CORESET parameters configure sharing of at least one control channel element (CCE) between the UE device type and one or more other UE device types in one or more initial symbols.

28. A network node for wireless communication, comprising: one or more memories; andone or more processors, coupled to the one or more memories, configured to cause the network node to: transmit, to a user equipment (UE), an indication of a control resource set (CORESET) configuration that indicates one or more CORESET parameters associated with a UE device type; and transmit, to the UE, a physical downlink control channel (PDCCH) communication in at least one PDCCH candidate location based at least in part on the CORESET configuration associated with the UE device type.

29. The network node of claim 28, wherein the CORESET configuration is compatible with the UE device type and with a different UE device type.

30. The network node of claim 28, wherein the one or more CORESET parameters configure an intra-slot or an inter-slot demodulation reference signal (DMRS) bundling pattern.

Images