Control resource set with larger allocation in time domain for devices with reduced bandwidth

By receiving and monitoring the CORESET configuration at the user equipment (UE), allocating more than three OFDM symbols in the time domain and allocating a bandwidth of 5MHz or less in the frequency domain, the problem of low communication efficiency of devices with reduced bandwidth in 5G-NR technology is solved, and effective communication performance is improved.

CN117480755BActive Publication Date: 2024-11-19QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280042162.4
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2021-06-24
Filing Date
2022-06-09
Publication Date
2024-11-19
Estimated Expiration
2042-06-09

AI Technical Summary

Technical Problem

Existing 5G-NR technology suffers from interference and performance degradation when supporting devices with reduced bandwidth, especially due to the fact that CORESET resource allocation is not adapted to bandwidths of 20MHz or less, resulting in low communication efficiency.

Method used

At the user equipment (UE), the CORESET configuration is received, more than three OFDM symbols are allocated in the time domain and a bandwidth of 5 MHz or less is allocated in the frequency domain, and the time-frequency resource set is monitored to receive downlink control information, including additional details of the CORESET configuration such as REG index, CCE-REG mapping and DMRS location.

Benefits of technology

It enables efficient communication with 5G-NR networks on devices with reduced bandwidth, improving communication efficiency and performance, and is suitable for operation with bandwidths of 20MHz or less.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN117480755B_ABST
    Figure CN117480755B_ABST
Patent Text Reader

Abstract

The present disclosure provides systems, methods, and devices for wireless communication of devices supporting reduced bandwidth, and in particular, allocating more than three orthogonal frequency division multiplexing (OFDM) symbols in the time domain to a control resource set (CORESET). In a first aspect, a method for wireless communication includes: receiving, at a user equipment (UE), from a base station a first message indicating a CORESET configuration. The CORESET configuration allocates more than three OFDM symbols in the time domain to the CORESET. The method also includes monitoring a time-frequency resource set to receive a second message from the base station at the UE. The time-frequency resource set has the CORESET configuration. Other aspects and features are also claimed and described.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application No. 17 / 357,611, filed on June 24, 2021, entitled “CONTROL RESOURCE SET WITH LARGER ALLOCATION IN THE TIME DOMAIN FOR REDUCED BANDWIDTH DEVICES,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] Aspects of the present disclosure relate generally to wireless communication systems, and more particularly to systems that support reduced bandwidth devices, such as devices that support bandwidths of 20 megahertz (20 MHz) or less. Some features enable and provide improved communications, including allocating more than three orthogonal frequency division multiplexing (OFDM) symbols in the time domain to a control resource set (CORESET) for reduced bandwidth operation. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks may be multiple-access networks capable of supporting communication for multiple users by sharing the available network resources.

[0005] A wireless communication network may include several components. These components may include wireless communication devices, such as a base station (or Node B) that may support communication of several user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a UE, and an uplink (or reverse link) refers to a communication link from a UE to a base station.

[0006] A base station may send data and control information to a UE on a downlink, or receive data and control information from a UE on an uplink. On the downlink, transmissions from a base station may encounter interference caused by transmissions from neighboring base stations or other wireless radio frequency (RF) transmitters. On the uplink, transmissions from a UE may encounter interference from other UEs communicating with neighboring base stations or uplink transmissions from other wireless RF transmitters. Such interference may degrade performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks grows with more UEs accessing long-range wireless communication networks and more short-range wireless systems deployed in communities. Research and development continues to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience with mobile communications.

[0008] The fifth generation of new air interface (5G-NR) wireless communication provides improved quality communication and enhanced features by using higher bandwidths such as "millimeter wave" bandwidth. Although such improvements have been implemented in smart phones and other devices, some benefits of the technology have not yet been extended to less complex devices. For illustration, research on supporting the concept of 5G-NR in "reduced capability" (RedCap) devices, "NR-light" devices, and "NR-ultra-light" devices is ongoing. Such research focuses on relaxing the peak throughput, latency, and reliability requirements associated with typical 5G-NR to extend the benefits to devices with less complex processors and smaller battery life, such as wireless sensors, metering devices, asset tracking devices, and personal Internet of Things (IoT) devices as non-limiting examples. In addition to utilizing low-power and low-complexity sidelink communications, research goals also include supporting low-power wide area (LPWA) networks and devices via improvements in coverage, complexity, and power consumption. One focus of NR ultra-light device research is to support devices that communicate via reduced bandwidths, such as 20 megahertz (MHz) or less. However, this reduced bandwidth operation may cause problems when trying to support 5G-NR features designed for larger bandwidth operation. Summary of the invention

[0009] Some aspects of the present disclosure are summarized below to provide a basic understanding of the discussed technology. This summary is not an exhaustive overview of all expected features of the present disclosure, and is neither intended to identify key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to provide some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to more specific embodiments that will be provided later.

[0010] In one aspect of the present disclosure, a method for wireless communication includes: receiving a first message at a user equipment (UE) from a base station, the first message indicating a control resource set (CORESET) configuration. The CORESET configuration allocates more than three orthogonal frequency division multiplexing (OFDM) symbols in a time domain to the CORESET. The method also includes monitoring the time-frequency resource set to receive a second message at the UE from the base station. The time-frequency resource set has the CORESET configuration.

[0011] In an additional aspect of the present disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to receive a first message from a base station, the first message indicating a CORESET configuration. The CORESET configuration allocates more than three OFDM symbols in a time domain to the CORESET. The at least one processor is also configured to monitor a time-frequency resource set to receive a second message from the base station. The time-frequency resource set has a CORESET configuration.

[0012] In an additional aspect of the present disclosure, an apparatus includes: means for receiving a first message indicating a CORESET configuration from a base station. The CORESET configuration allocates more than three OFDM symbols in a time domain to the CORESET. The apparatus also includes means for monitoring a set of time-frequency resources to receive a second message from the base station. The set of time-frequency resources has the CORESET configuration.

[0013] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: receiving, at a UE, a first message from a base station indicating a CORESET configuration. The CORESET configuration allocates more than three OFDM symbols in a time domain to the CORESET. The operations also include monitoring a time-frequency resource set to receive, at the UE, a second message from the base station. The time-frequency resource set has the CORESET configuration.

[0014] In an additional aspect of the present disclosure, a method for wireless communication includes generating, at a base station, a first message indicating a CORESET configuration. The CORESET configuration allocates more than three OFDM symbols in a time domain to the CORESET. The method also includes transmitting the first message to a UE.

[0015] In an additional aspect of the present disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to generate a first message indicating a CORESET configuration. The CORESET configuration allocates more than three OFDM symbols in a time domain to the CORESET. The at least one processor is also configured to initiate transmission of the first message to a UE.

[0016] In an additional aspect of the present disclosure, an apparatus includes means for generating a first message indicating a CORESET configuration. The CORESET configuration allocates more than three OFDM symbols in a time domain to the CORESET. The apparatus also includes means for transmitting the first message to a UE.

[0017] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include: generating a first message indicating a CORESET configuration at a base station. The CORESET configuration allocates more than three OFDM symbols in a time domain to the CORESET. The operations also include initiating transmission of a first message to a UE.

[0018] The features and technical advantages of the examples according to the present disclosure have been summarized quite extensively above. Additional features and advantages will be described later. The disclosed concepts and specific examples can be easily used as the basis for modifying or designing other structures for the same purpose of achieving the present disclosure. Such equivalent constructions do not depart from the scope of protection of the appended claims. When considered in conjunction with the accompanying drawings, the characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood from the description below. Each of the accompanying drawings is provided for the purpose of illustration and description, not as a definition of the limitations of the claims.

[0019] Although aspects and implementations are described in this application by illustrations of some examples, it will be understood by those skilled in the art that additional implementations and use cases may be generated in many other arrangements and scenarios. The innovation described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, various aspects and / or uses can be implemented via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of described innovations may occur. The scope of each implementation can range from chip-level or module components to non-module, non-chip-level implementations, and further to aggregated, distributed or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovation. In some practical environments, the equipment incorporating the various aspects and features described may also necessarily include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include several components for analog and digital purposes (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, (multiple) processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. In addition, various components of the same type may be distinguished by adding a dash and a second reference numeral after the reference numeral to distinguish between similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components having the same first reference numeral, regardless of the second reference numeral.

[0021] Figure 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects.

[0022] Figure 2 is a block diagram illustrating an example of a base station and a user equipment (UE) according to one or more aspects.

[0023] Figure 3 is a block diagram of an example wireless communication system that supports control resource sets (CORESETs) for use by devices with reduced bandwidth in accordance with one or more aspects.

[0024] Figure 4

[0013] A first configuration of a control resource set bandwidth reduction (CORESET-BR) and a physical downlink shared channel (PDSCH) scheduled by the CORESET-BR according to one or more aspects is shown.

[0025] Figure 5 A second configuration of a CORESET BR and a PDSCH scheduled by the CORESET BR according to one or more aspects is shown.

[0026] Figure 6

[0013] Illustrated are examples of resource element group (REG) indexing and REG to control channel element (CCE) assignments in accordance with one or more aspects.

[0027] Fig. 7A A first example of REG indexing and REG-to-CCE assignment in accordance with one or more aspects is illustrated.

[0028] Figure 7B A second example of REG indexing and REG-to-CCE assignment in accordance with one or more aspects is illustrated.

[0029] Fig. 8A A first example of CORESET, PDSCH, and demodulation reference signal (DMRS) allocations in accordance with one or more aspects is illustrated.

[0030] Figure 8B A second example of CORESET, PDSCH, and DMRS allocation according to one or more aspects is illustrated.

[0031] Fig. 9 is a flow chart illustrating an example process for allocating more than three orthogonal frequency division multiplexing (OFDM) symbols in the time domain to a CORESET in support of a reduced bandwidth device in accordance with one or more aspects.

[0032] Fig.10 is a block diagram of an example user equipment (UE) that supports allocating more than three OFDM symbols in the time domain to a CORESET for a reduced bandwidth device in accordance with one or more aspects.

[0033] Fig.11 is a flow chart illustrating an example process that supports generating a CORESET of more than three OFDM symbols in the time domain for a reduced bandwidth device in accordance with one or more aspects.

[0034] Fig.12 is a block diagram of an example base station that supports allocating more than three OFDM symbols to a CORESET for a reduced bandwidth device in accordance with one or more aspects.

[0035] The same reference numbers and designations in different drawings represent the same elements. DETAILED DESCRIPTION

[0036] The "Detailed Description" set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Instead, the "Detailed Description" includes specific details for providing a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0037] The present disclosure provides systems, apparatuses, methods, and computer-readable media that support devices with reduced bandwidth, such as devices that communicate via a bandwidth of 20 megahertz (MHz) or less, particularly 5 MHz or less, in a fifth generation new radio (5G-NR) wireless network. Specifically, the techniques described herein support a control resource set (CORESET) having a larger dimension in the time domain and a smaller dimension in the frequency domain for use by devices with reduced bandwidth. For example, the CORESET described herein may be allocated more than three orthogonal frequency division multiplexing (OFDM) symbols in the time domain and a bandwidth of 5 MHz or less in the frequency domain. Wireless communication devices configured for operation at 5 MHz or less (referred to herein as "ultralight" or "NR-ultralight" devices) may support physical broadcast channel (PBCH) resource allocations used by typical non-reduced bandwidth devices, but may not support CORESET resource allocations used by such devices because the CORESET is allocated a bandwidth larger than the maximum operating bandwidth of the ultralight device. Therefore, a CORESET that is designated for other devices and configured by a master information block (MIB) sent within a physical broadcast channel (PBCH) may not be usable by an ultralight device. Instead, an ultralight device may be configured to receive a separate message indicating a different CORESET configuration that may be used by the ultralight device, or the CORESET configuration may be determined based on pre-configuration information stored at the ultralight device and based on one or more communication parameters that may be determined by the ultralight device or indicated by the PBCH. This CORESET configuration allocates a larger dimension in the time domain (e.g., more than three OFDM symbols, such as four to fourteen OFDM symbols) and a smaller dimension in the frequency domain (e.g., 5 MHz or less) to the CORESET of the ultralight device. In some implementations, additional parameters such as physical downlink shared channel (PDSCH) mapping, demodulation reference signal (DMRS) positioning for PDSCH, resource element group (REG) indexing, and control channel element (CCE)-REG mapping may be configured for the CORESET of the ultralight device.

[0038] To illustrate the operation of an ultralight device, a user equipment (UE) configured for 5 MHz or less operation (or as another example, 20 MHz or less) may receive a message from a base station. The message may indicate a CORESET configuration that allocates more than three OFDM symbols in the time domain and a bandwidth of 5 MHz or less in the frequency domain to the CORESET for the UE. The UE may then monitor the set of time-frequency resources allocated to the CORESET (e.g., a search space allocated by the CORESET configuration) to receive a second message from the base station. The second message may include downlink control information (DCI) transmitted from the base station in a physical downlink control channel (PDCCH) within the time-frequency resources allocated to the CORESET. The second message may indicate a resource allocation for a PDSCH that includes additional downlink data from the base station.

[0039] Specific implementations of the subject matter described in the present disclosure may be implemented to achieve one or more of the following potential advantages or benefits. In some aspects, the present disclosure provides techniques for allocating time-frequency resources to a CORESET for wireless communication devices that support reduced bandwidth operation. For example, instead of using a CORESET configuration (e.g., allocation of time-frequency resources) used by other types of devices (e.g., non-reduced bandwidth devices), a reduced bandwidth device such as a reduced bandwidth UE may receive a message indicating a CORESET configuration for the reduced bandwidth device. For example, the CORESET configuration may indicate an allocation of fewer frequency resources (e.g., less than 5 MHz bandwidth) and more time resources (e.g., more than 3 OFDM symbols) to the CORESET for the reduced bandwidth device as compared to the CORESET for the other types of devices (e.g., non-ultralight devices). Thus, the reduced bandwidth device may be able to receive the same amount of information in the CORESET as other types of devices while operating at a reduced bandwidth compared to the other types of devices. In addition, the CORESET configuration for reduced bandwidth may also include additional details about CORESET resource allocation, such as REG index, CCE-REG mapping, and DMRS location for PDSCH. In this way, wireless communication devices configured for reduced bandwidth operation (such as 5 MHz or less bandwidth) may be able to establish effective communication with a 5G-NR network that is generally designed for larger bandwidth operation.

[0040] The present disclosure generally relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various implementations, various techniques and apparatuses may be used in wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems, or devices), and other communication networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0041] A CDMA network may implement, for example, a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0042] For example, a TDMA network can implement radio technologies such as the Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standards for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of the network of GSM / EDGE together with connecting base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents the component of the GSM network, through which telephone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to subscriber phones (also known as user terminals or user equipment (UE)) and from subscriber phones to the PSTN and the Internet. The network of a mobile phone operator may include one or more GERANs, which may be coupled to the UTRAN in the case of a UMTS / GSM network. In addition, the operator network may also include one or more LTE networks, or one or more other networks. Various network types may use different radio access technologies (RATs) and RANs.

[0043] OFDMA network can realize radio technology such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA and GSM are part of Universal Mobile Telecommunication System (UMTS). In particular, Long Term Evolution (LTE) is a version of UMTS using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration between telecommunication association groups with the goal of defining a globally applicable third generation (3G) mobile phone specification. 3GPP LTE is a 3GPP plan with the goal of improving the UMTS mobile phone standard. 3GPP can define the specifications of next generation mobile networks, mobile systems and mobile devices. The present disclosure may describe certain aspects with reference to LTE, 4G or 5G NR technology; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. In addition, one or more aspects of the present disclosure may relate to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0044] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new air interface technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5GNR will be able to scale to provide coverage for the massive Internet of Things (IoT) with ultra-high density (e.g., approximately 1M nodes / km2), ultra-low complexity (e.g., approximately 10s of bits / second), ultra-low energy (e.g., approximately 10+ years of battery life); (1) deep coverage with the ability to reach challenging locations; (2) mission-critical control including strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., approximately 99.9999% reliability), ultra-low latency (e.g., approximately 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) take advantage of enhanced mobile broadband, including extremely high capacity (e.g., approximately 10Tbps / km2), extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep awareness with advanced discovery and optimization.

[0045] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified with the frequency range names FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes arise for FR2, which is often (interchangeably) referred to as the "millimeter wave" (mmWave) band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) band identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0046] In view of the above aspects, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz" and the like, if used herein, can broadly refer to frequencies that can be less than 6 GHz, can be within FR1, or can include mid-band frequencies. In addition, unless otherwise explicitly stated, it should be understood that the term "millimeter wave" and the like, if used herein, can broadly refer to frequencies that can include mid-band frequencies, can be within FR2, or can be within the EHF band.

[0047] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform features. These features can include scalable digital parameters and transmission time intervals (TTIs); a common, flexible framework that efficiently multiplexes services and features using dynamic, low-latency time division duplex (TDD) designs or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave transmission, advanced channel coding, and device-centric mobility. The scalability of digital parameters in 5G NR and the scaling of subcarrier spacing can effectively address the operation of various services across different spectrums and different deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing may appear at 15kHz, such as over bandwidths of 1MHz, 5MHz, 10MHz, 20MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3GHz, the subcarrier spacing may appear at 30kHz over 80 / 100MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5GHz band, subcarrier spacing may occur at 60kHz over a 160MHz bandwidth. Finally, for various deployments transmitting over mmWave components at 28GHz TDD, subcarrier spacing may occur at 120kHz over a 500MHz bandwidth.

[0048] 5G NR's scalable digital parameters facilitate scalable TTIs for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design in which uplink or downlink scheduling information, data, and acknowledgments are in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic needs.

[0049] For clarity, certain aspects of the devices and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0050] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate using any combination of licensed spectrum or unlicensed spectrum depending on load and availability. Therefore, it will be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications beyond the specific examples provided.

[0051] Although aspects and implementations are described in this application by illustrations of some examples, it will be understood by those skilled in the art that additional implementations and use cases may be generated in many other arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, implementations or uses can be implemented via integrated chip implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail devices or purchasing devices, medical devices, AI-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of various types of the described innovations may occur. The range of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems containing one or more aspects of the described innovations. In some practical environments, the devices incorporating the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. It is intended that the innovations described herein may be practiced in a wide variety of implementations of different sizes, shapes, and configurations, including large or small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, and the like.

[0052] Figure 1 1 is a block diagram illustrating details of an exemplary wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 Components appearing in are likely to have related corresponding components in other network arrangements (including, for example, cellular-style network arrangements and non-cellular-style network arrangements (e.g., device-to-device or peer-to-peer or ad hoc network arrangements, etc.)).

[0053] Figure 1The wireless network 100 shown in includes many base stations 105 and other network entities. A base station may be a station that communicates with a UE, and may also be referred to as an evolved Node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may refer to the specific geographic coverage area of ​​a base station or a base station subsystem serving the coverage area, depending on the context in which the term is used. In the implementation of the wireless network 100 herein, the base station 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). In addition, in the implementation of the wireless network 100 herein, the base station 105 may provide wireless communication using one or more of the same frequencies as neighboring cells (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof). In some examples, a single base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0054] A base station may provide communication coverage for a macro cell or a small cell (e.g., a pico cell or a femto cell), or other types of cells. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs that have a service subscription with a network provider. Small cells (such as pico cells) will generally cover a relatively small geographic area and may allow unrestricted access by UEs that have a service subscription with a network provider. Small cells (e.g., femto cells) will also typically cover a relatively small geographic area (e.g., a home), and in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c use their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0055] Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some cases, the network may be enabled or configured to handle dynamic switching between synchronous or asynchronous operation.

[0056] UE 115 is dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that, although in the standards and specifications promulgated by 3GPP, mobile devices are generally referred to as UEs, such devices may be referred to as mobile stations (MS), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices or vehicle modules, or some other suitable terminology by those skilled in the art. In this document, a "mobile" device or UE does not necessarily have the ability to move and may be stationary. Some non-limiting examples of mobile devices, such as implementations that may include one or more UE 115, include mobile phones, cellular phones, smart phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smart books, tablet computers, and personal digital assistants (PDAs). The mobile device may also be an IoT or "Internet of Things" (IoE) device, such as a car or other means of transportation, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-rotor helicopter, a quadcopter, a smart energy or security device, a solar panel or solar array, city lighting, tap water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammal implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE may be a device that includes a universal integrated circuit card (UICC). On the other hand, a UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UEs 115a-115d of the implementation shown in FIG are examples of mobile smartphone-type devices accessing the wireless network 100. A UE may also be a machine specifically configured for connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 The UEs 115e-115k shown in FIG. 1 are examples of various machines configured for communication that access the wireless network 100.

[0057] A mobile device such as UE 115 may be able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the figure, the communication link (represented by a lightning arrow) indicates a wireless transmission between a UE and a serving base station (which is a base station designated to serve the UE on a downlink or uplink), or an expected transmission between base stations and a backhaul transmission between base stations. The UE may operate as a base station or other network node in some scenarios. Backhaul communications between base stations of the wireless network 100 may be performed using wired or wireless communication links.

[0058] In operation, at the wireless network 100, base stations 105a-105c use 3D beamforming and coordinated spatial techniques (e.g., coordinated multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cells (base station 105f). Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber alerts or gray alerts.

[0059] The wireless network 100 of the implementation supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e as a drone. The redundant communication links with UE 115e include links from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device) can communicate directly with base stations such as small cell base station 105f and macro base station 105e through the wireless network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which then reports it to the network through small cell base station 105f. The wireless network 100 may also provide additional network efficiency through dynamic, low latency TDD communications or low latency FDD communications (eg, in a vehicle-to-vehicle (V2V) mesh network between UEs 115i - 115k communicating with a macro base station 105e ).

[0060] Figure 2 1 is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 may be Figure 1 For a restricted association scenario (as described above), base station 105 may be any one of the base stations in the UE and one of the UEs. Figure 1 The small cell base station 105f in the example of FIG. 105 and the UE 115 may be a UE 115c or 115d operating in the service area of ​​the base station 105f, which will be included in the list of accessible UEs of the small cell base station 105f in order to access the small cell base station 105f. The base station 105 may also be some other type of base station. Figure 2 As shown in FIG. 1 , the base station 105 may be equipped with antennas 234a through 234t and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communication.

[0061] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller 240 (e.g., a processor). The control information may be used for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid-ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be used for a physical downlink shared channel (PDSCH), etc. In addition, the transmit processor 220 may process (e.g., encode and symbol map) the data and the control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS), and a cell-specific reference signal. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, or reference symbols (if applicable), and may provide an output symbol stream to modulators (MODs) 232a to 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include precoding. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0062] At UE 115, antennas 252a to 252r may receive downlink signals from base station 105 and may provide received signals to demodulators (DEMOD) 254a to 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from demodulators 254a to 254r, perform MIMO detection on the received symbols when necessary, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 115 to a data sink 260, and provide decoded control information to a controller 280 (e.g., a processor).

[0063] On the uplink, at the UE 115, the transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from the controller 280 (e.g., for a physical uplink control channel (PUCCH)). In addition, the transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266 if necessary, further processed by the modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 if necessary, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 115. The receive processor 238 may provide the decoded data to the data sink 239 and the decoded control information to the controller 240.

[0064] The controllers 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105, or the controller 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as performing or directing Fig. 9 and Fig.11 1 or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0065] In some cases, the UE 115 and the base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 105 may traditionally perform a medium sensing process to contend for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk or listen-before-transmit (LBT) process (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. In some implementations, the CCA may include an energy detection process to determine whether there are any other active transmissions. For example, the device may infer that a change in the received signal strength indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, the signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence indicating the use of the channel. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets (as a manifestation of a collision).

[0066] Figure 3 is a block diagram of an exemplary wireless communication system 300 supporting a CORESET for use by a device with reduced bandwidth according to one or more aspects. The CORESET may be allocated a larger dimension in the time domain (e.g., more than three OFDM symbols) and a smaller dimension in the frequency domain (e.g., 20 MHz or less in the frequency domain) than resource allocations for other devices, such as devices configured to communicate via a wider channel bandwidth (e.g., greater than 20 MHz) and three or less OFDM symbols. The device with reduced bandwidth may also be referred to as an "ultralight" or "NR-ultralight" device. In some implementations, the ultralight device may be configured to communicate via a reduced bandwidth communication such as a bandwidth of 5 MHz or less. In some other implementations, the ultralight device may be configured to communicate via a wider but still reduced bandwidth (e.g., 20 MHz or less) or other bandwidths. In some examples, the wireless communication system 300 may implement aspects of the wireless network 100. The wireless communication system 300 includes a UE 115 and a base station 105. Although one UE 115 and one base station 105 are shown, in some other implementations, the wireless communication system 300 may generally include multiple UEs 115 and may include more than one base station 105 .

[0067] The UE 115 may include various components (e.g., structures, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 302 (hereinafter collectively referred to as "processors 302"), one or more memory devices 304 (hereinafter collectively referred to as "memory 304"), one or more transmitters 316 (hereinafter collectively referred to as "transmitters 316"), and one or more receivers 318 (hereinafter collectively referred to as "receivers 318"). The processor 302 may be configured to execute instructions stored in the memory 304 to perform the operations described herein. In some implementations, the processor 302 includes or corresponds to one or more of the receive processor 258, the transmit processor 264, and the controller 280, and the memory 304 includes or corresponds to the memory 282.

[0068] The memory 304 includes or is configured to store resource allocation data 306 and monitored time-frequency resource data 308. The resource allocation data 306 may indicate details about the CORESET resource allocation for the UE 115. For example, the resource allocation data 306 may include the time-frequency resources allocated to the CORESET for the UE 115. In some implementations, these time-frequency resources allocated to the CORESET may include larger dimensions in the time domain (e.g., more than three OFDM symbols) and smaller dimensions in the frequency domain (e.g., 20 MHz or less in the frequency domain) than resources allocated to CORESETs for other types of devices (e.g., non-ultralight devices). The resource allocation data 306 may also indicate additional details about the CORESET resource allocation, such as REG bundling data, CCE-REG mapping data, REG index data, and DMRS data (e.g., DMRS locations in the time domain for the CORESET). The CCE-REG mapping data may indicate the mapping of CCEs to REGs for various CORESETs. The REG index data may indicate the indexes of REGs for various CORESETs. The DMRS may indicate DMRS assignments for various CORESETs, as further described below. In some implementations, resource allocation data 306 may be received by UE 115 from another node (e.g., base station 105) in wireless communication system 300 and may then be stored at memory 304. Monitored time-frequency resource data 308 may indicate a set of time-frequency resources monitored by UE 115 to receive one or more messages from base station 105, as further described herein.

[0069] The transmitter 316 is configured to transmit reference signals, control information, and data to one or more other devices, and the receiver 318 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, the transmitter 316 can transmit signaling, control information, and data to the base station 105, and the receiver 318 can receive signaling, control information, and data from the base station 105. In some implementations, the transmitter 316 and the receiver 318 can be integrated into one or more transceivers. Additionally or alternatively, the transmitter 316 or the receiver 318 may include or correspond to a reference signal. Figure 2 One or more components of UE 115 are described.

[0070] The base station 105 may include various components (such as structures, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 352 (hereinafter collectively referred to as "processor 352"), one or more memory devices 354 (hereinafter collectively referred to as "memory 354"), one or more transmitters 356 (hereinafter collectively referred to as "transmitters 356"), and one or more receivers 358 (hereinafter collectively referred to as "receivers 358"). The processor 352 may be configured to execute instructions stored in the memory 354 to perform the operations described herein. In some implementations, the processor 352 includes or corresponds to one or more of the receive processor 238, the transmit processor 220, and the controller 240, and the memory 354 includes or corresponds to the memory 242.

[0071] The memory 354 includes or is configured to store CORESET configuration data 360 and PDSCH resource allocation data 362. In some implementations, the CORESET configuration data 360 may indicate CCE-REG mapping data 364, REG index data 366, and DMRS data 368. The CCE-REG mapping data 364 may indicate a mapping of REGs to CCEs for allocating resources to the CORESET. In some implementations, each CCE includes six REGs, and each REG corresponds to one PRB in the frequency domain and one OFDM symbol in the time domain. As non-limiting examples, the assignment of PRBs to REGs may be based on a fixed dimension in the time domain, a fixed dimension in the frequency domain, or a continuous pattern in the frequency domain rather than the time domain. The REG index data 366 may indicate a pattern for assigning indexes to REGs for various CORESETs. For example, the indexes may be assigned based on a pattern for a fixed dimension in the time domain or a continuous pattern in the frequency domain rather than the time domain. The DMRS data 368 may indicate OFDM symbols allocated to the DMRS. In some implementations, the DMRS 368 may indicate a relationship between a CORESET and a DMRS in the time domain. For example, the DMRS data 368 may indicate which of the resources allocated to the CORESET are designated for communication of the DMRS.

[0072] Although CCE-REG mapping data 364, REG index data 366, and DMRS data 368 are Figure 3 105 and is described herein as being transmitted to the UE 115 via the first message 370, but in other implementations, one or more of the CCE-REG mapping data 364, the REG index data 366, and the DMRS data 368 may be predefined in part or in whole and stored at the UE 115. For example, one or more of the CCE-REG mapping data 364, the REG index data 366, and the DMRS data 368 may be stored in part or in whole at the memory 304 during manufacture, setup, or deployment of the UE 115. Additionally or alternatively, one or more of the CCE-REG mapping data 364, the REG index data 366, and the DMRS data 368 may be received in part or in whole from another device, such as being included in a software or firmware update for the UE 115. In some implementations, one or more of the CCE-REG mapping data 364, the REG index data 366, and the DMRS data 368 may be defined in one or more wireless communication standard specifications, such as 3GPP standards, as non-limiting examples.

[0073] The transmitter 356 is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and the receiver 358 is configured to receive reference signals, control information, and data from one or more other devices. For example, the transmitter 356 can transmit signaling, control information, and data to the UE 115, and the receiver 358 can receive signaling, control information, and data from the UE 115. In some implementations, the transmitter 356 and the receiver 358 can be integrated into one or more transceivers. Additionally or alternatively, the transmitter 356 or the receiver 358 can include or correspond to a reference signal. Figure 2 One or more components of base station 105 are described.

[0074] In some implementations, the wireless communication system 300 implements a 5G NR network. For example, the wireless communication system 300 may include a plurality of 5G-capable UEs 115 and a plurality of 5G-capable base stations 105, such as UEs and base stations configured to operate according to a 5G NR network protocol such as defined by 3GPP. In addition, the wireless communication system 300 may support devices with reduced bandwidth (e.g., ultra-light). For example, as a non-limiting example, the UE 115 and the base station 105 may be configured to communicate via a reduced bandwidth (e.g., channel bandwidth) (such as 5 MHz or less, or 20 MHz or less), and as a non-limiting example, the base station 105 may be configured to communicate with other UEs via a larger bandwidth (such as 50 MHz, 100 MHz, 200 MHz, or 400 MHz).

[0075] During operation of the wireless communication system 300, the base station 105 determines CORESET configuration data 360 and broadcasts a first message 370 including the CORESET configuration data 360 to enable ultralight devices searching for cells to receive information of additional messages scheduled for connection to the base station 105. The base station 105 may determine the CORESET configuration data 360 based on the device type of the intended receiving devices, such as whether the devices are ultralight devices associated with a reduced operating bandwidth, or whether the devices are other types of devices that do not have such a reduced operating bandwidth. The base station 105 may transmit the first message 370 to devices within the coverage of the base station 105 within a physical broadcast channel (PBCH). In some implementations, the first message 370 includes a radio resource control (RRC) message, such as a master information block (MIB). The first message 370 (e.g., MIB and PBCH) may define a CORESET for ultralight devices, such as CORESET0-Bandwidth Reduced (CORESET0-BR). Alternatively, in addition to including some information (such as CORESET configuration data 360) and defining CORESET0-BR for ultralight devices, the first message 370 may also define CORESET0 for other device types. In some such implementations, the CORESET configuration data 360 may be selected by the UE 115 from a plurality of pre-stored (e.g., pre-configured or pre-defined) CORESET configurations based on one or more communication parameters (such as subcarrier spacing) that may be indicated by the first message 370 for ultralight devices and non-ultralight devices. For illustration, if the subcarrier spacing indicated by the first message 370 has a first value, the UE 115 may select as the CORESET configuration data 360 a first configuration that allocates a first number of OFDM symbols, and if the subcarrier spacing has a second value, the UE 115 may select as the CORESET configuration data 360 a second configuration that allocates a second number of OFDM symbols.

[0076] The UE 115 may receive a first message 370 including the CORESET configuration data 360 and may store the CORESET configuration data 360 in the memory 304. The UE 115 may be configured to receive and process the first message 370 and extract the CORESET configuration data 360 based on the UE 115 being configured as an ultra-light device, such as being configured to communicate with the base station 105 via a bandwidth or bandwidth portion (BWP) of less than 5 MHz. In some implementations, the CORESET configuration data 360 is stored in the memory 304 as resource allocation data 306. The CORESET configuration data 360 allocates fewer frequency domain resources and more time domain resources to the CORESET0-BR than the time-frequency resources allocated to the CORESET0 for other devices. For example, the CORESET configuration data 360 may allocate 4 to 14 OFDM symbols in the time domain to the CORESET for the UE 115. Although described herein as allocating a reference to an initial CORESET (e.g., CORESET0-BR) for an ultralight device, in other implementations, the CORESET configuration data 360 may allocate resources to a different CORESET for an ultralight device. The CORESET configuration data 360 defines a set of time-frequency resources on which additional communications from the base station 105 to the UE 115 are scheduled to occur. As an illustrative, non-limiting example, the CORESET configuration data 360 may define a set of time-frequency resources on which the base station 105 transmits a message, such as the second message 374, to the UE 115.

[0077] In addition to defining the time-frequency resources allocated to the CORESET0-BR (e.g., a CORESET for ultralight devices), the CORESET configuration data 360 may also indicate other communication parameters. For example, the CORESET configuration data 360 may define a subcarrier spacing (SCS) value for the UE 115. The SCS represents the frequency difference between subcarriers in a PRB, and the SCS may have one of a plurality of values ​​in a 5G NR system. The UE 115 may be configured to perform all communications according to a single SCS value, or the UE 115 may be configured to communicate with different devices or in different operating modes according to different SCS values. For example, the UE 115 may be configured to use an SCS of 15 kilohertz (kHz) in a first operating mode and an SCS of 30 kHz in a second operating mode. Although described as being used for communication, the SCS value may be used for specific types of communication, such as synchronization signal blocks (SSBs), PDCCHs, and others, and different types of communications may correspond to different SCS values. For example, as a non-limiting example, an SSB may correspond to a different SCS than a PDCCH. In some implementations, the CORESET configuration data 360 may allocate specific time-frequency resources to the CORESET0-BR based on the SCS value. As an illustrative, non-limiting example, the CORESET configuration data 360 may allocate up to 14 OFDM symbols in the time domain and up to 24 PRBs in the frequency domain to the CORESET0-BR for communication with an SCS of 15 kHz. As another illustrative, non-limiting example, the CORESET configuration data 360 may allocate up to 14 OFDM symbols in the time domain and up to 12 PRBs in the frequency domain to the CORESET0-BR for communication with an SCS of 30 kHz.

[0078] In addition to or in lieu of defining an SCS value, the CORESET configuration data 360 may indicate CCE-REG mapping data 364, REG index data 366, DMRS data 368, or a combination thereof. In some implementations, resource elements allocated to CORESET0-BR may be organized into REGs, each REG including a resource block (e.g., PRB) including twelve resource elements in the frequency domain and one OFDM symbol in the time domain, and each resource element including one subcarrier in the frequency domain. In such implementations, REGs may be organized into CCEs such that each CCE includes six REGs. A PDCCH defined within a CORESET typically corresponds to 1, 2, 4, 8, or 16 CCEs, however, because CORESET0-BR is allocated to a longer duration in the time domain than CORESET0 for other types of devices, in some implementations, a PDCCH defined within CORESET0-BR may correspond to more than 16 CCEs. CORESET configuration data 360 may indicate an organization of REGs and CCEs to enable a device such as UE 115 to identify which time-frequency resources allocated to CORESET0-BR are assigned to the PDCCH. CCE-REG mapping data 364 may indicate a mapping of CCEs to REGs for CORESET0-BR for UE 115. For example, CCE-REG mapping information 364 may indicate an index of a REG for each of one or more CCEs assigned to CORESET0-BR. This mapping of CCEs to REGs may be interleaved or non-interleaved.

[0079] REG index data 366 may indicate which PRBs of the CORESET are assigned to each REG and the index of each REG. As non-limiting examples, the PRB to REG assignment may be based on a fixed dimension in the time domain, a fixed dimension in the frequency domain, or based on a continuous pattern in the frequency domain but not in the time domain, as shown in FIG. Figure 6 The PRB to REG assignment may be based on the number of OFDM symbols allocated to CORESET0-BR, a pattern of contiguousness in the time domain for REGs with the same frequency, a pattern of contiguousness in the frequency domain for REG pairs with different frequencies, other parameters or patterns, or a combination thereof.

[0080] The DMRS data 368 may indicate the OFDM symbols allocated to the DMRS. In some implementations, the DMRS data 368 may indicate the relationship between the CORESET and the DMRS for the PDSCH in the time domain. For example, the DMRS 368 may indicate which time resources (e.g., OFDM symbols) of those time resources allocated to the CORESET (e.g., CORESET0-BR) are designated for transmitting the PDSCH DMRS by the base station 105. In some implementations, the DMRS data 368 may also indicate the starting symbol of the PDSCH DMRS. To illustrate, for PDSCH mapping of type A, the PDSCH DMRS associated with a CORESET configured for other types of devices (e.g., non-ultralight devices) typically starts at 0, 1, 2, or 3 OFDM symbols in the time domain, however, because CORESET0-BR is assigned to a longer duration in the time domain than CORESET0 for other types of devices, the PDSCH DMRS associated with CORESET0-BR may start at any one of 0-12 OFDM symbols in the time domain. Similarly, for PDSCH mapping of type B, the PDSCH DMRS associated with CORESET0-BR may be assigned to any one of 0-12 OFDM symbols in the time domain. As used herein, PDSCH mapping of type A refers to a configuration in which the DMRS is fixed to the third or fourth position of the PDSCH in the time domain, and PDSCH mapping of type B refers to a configuration in which the DMRS is fixed to the first position of the PDSCH in the time domain, as defined in the 3GPP specifications. Some non-limiting examples of DMRS parameters are given in Tables 1 and 2 below, where S is the index of the PDSCH start symbol, L is the PDSCH length, the normal cyclic prefix refers to each time slot divided into 7 OFDM symbols in the time domain, and the extended cyclic prefix refers to each time slot divided into 6 OFDM symbols.

[0081]

[0082] Table 1 - PDSCH DMRS parameters for normal cyclic prefix

[0083]

[0084] Table 2 - PDSCH DMRS parameters for extended cyclic prefix

[0085] The DMRS data 368 may also include information corresponding to a repetition pattern for the PDSCH DMRS. The repetition pattern may indicate that the PDSCH DMRS may be repeated after a CORESET0-BR resource allocation (e.g., a time-frequency resource set allocated to the CORESET0-BR), or the repetition pattern may indicate that the PDSCH DMRS may be repeated during the time-frequency resources allocated to the CORESET0-BR, as described below with respect to Fig. 8A and Figure 8B Further description.

[0086] After receiving and processing the first message 370, the UE 115 may monitor the set of time-frequency resources to receive the second message 374 from the base station 105. For example, after receiving and processing the CORESET configuration data 360, the UE 115 may monitor the set of time-frequency resources having the CORESET configuration (e.g., as indicated by the resource allocation data 306). The set of time-frequency resources is monitored to receive the second message 374 from the base station 105. The monitored time-frequency resources may include time resources such as a starting time (e.g., an initial OFDM symbol or time slot) and a duration (e.g., a total number of OFDM symbols or time slots), and frequency resources such as an initial frequency (e.g., a starting frequency or index of an initial PRB) and a total number of PRBs. The base station 105 may transmit the second message 374 within the time-frequency resources that match the time-frequency resources monitored by the UE 115. In some implementations, the base station 105 may transmit the second message 374 using a portion of the set of time-frequency resources established by the CORESET configuration data 360. For example, as a non-limiting example, CORESET0-BR defined by the CORESET configuration data 360 may be assigned to the PDCCH for transmitting the second message 374 and additional messages (such as DMRS).

[0087] The second message 374 may include downlink control information (DCI) transmitted from the base station 105 within the PDCCH and indicating to the UE 115 information for determining additional resource allocations (e.g., scheduling or configuration) for downlink or uplink communications connected to the base station 105. For example, the second message 374 may include PDSCH resource allocation data 362 that allocates a second set of time-frequency resources (e.g., a different set of time-frequency resources from the set of time-frequency resources allocated by the CORESET configuration data 360) from the base station 105 to the PDSCH. In some implementations, the PDSCH resource allocation data 362 may include additional downlink data from the base station, such as paging information, random access response messages, and delivery of partial system information. After receiving and processing the second message 374, the UE 115 may monitor the time-frequency resource set according to the PDSCH resource allocation data 362 to receive additional messages such as downlink data packets or other information from the base station 105 via the PDSCH. Additionally or alternatively, the second message 374 may indicate allocation of resources to one or more uplink channels for use by the UE 115 when sending a message to the base station 105. For example, the second message 374 may include resource allocations (e.g., time-frequency resource sets) for a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).

[0088] For other types of devices, the PDSCH is typically scheduled after CORESET0 in the time domain. However, because CORESET0-BR is allocated to a longer duration in the time domain than CORESET0 for other devices (e.g., non-ultralight devices), the resources allocated to the PDSCH by the PDSCH resource allocation data 362 may be scheduled after CORESET0-BR in the time domain, or may partially or completely overlap with CORESET0-BR in the time domain. Additionally or alternatively, the resources allocated to the PDSCH by the PDSCH resource allocation data 362 may be resources in the frequency domain that are different from the resources allocated to CORESET0-BR (e.g., different PRBs), or the PDSCH may partially or completely overlap with CORESET0-BR in the frequency domain. Figure 4 and Figure 5 Examples of PDSCH resource allocation and CORESET0-BR resource allocation are described.

[0089] As reference Figure 3As described, the present disclosure provides a technique for allocating time-frequency resources for a CORESET (e.g., CORESET0-BR) for a wireless communication device that supports reduced bandwidth operation. For example, instead of using a CORESET configuration (e.g., allocation of time-frequency resources) used by other types of devices (e.g., non-ultralight devices), the UE 115 may receive a message indicating CORESET configuration data 360, or the CORESET configuration data 360 may be determined based on information stored at the UE 115 and information such as one or more communication parameters (such as SCS) indicated by the first message 370. Since fewer PRBs in the frequency domain are allocated to the CORESET0-BR based on the reduced operating bandwidth of the UE 115, the CORESET configuration data 360 may allocate more than 3 OFDM symbols to the CORESET0-BR in the time domain. Therefore, the CORESET0-BR may be configured to include the same amount of information as the CORESET0 (e.g., DCI in the PDCCH) without exceeding the operating bandwidth of the ultralight device. In this way, wireless communication devices configured for reduced bandwidth operation (e.g., 20 MHz or less bandwidth, or 5 MHz or less bandwidth) may be able to establish effective communications with a 5G-NR network, which is generally designed for larger bandwidth operation.

[0090] Figure 4 and Figure 5 Example resource allocations for PDSCH and CORESET in time and frequency domains according to one or more aspects are shown. Figure 4 and Figure 5 The CORESET of ("CORESET-BR") may be an initial CORESET (e.g., may have an index of 0) or other CORESET defined for ultra-light devices (e.g., devices configured to receive a CORESET configuration that allocates more than three OFDM symbols in the time domain and 20 MHz or less or 5 MHz or less in the frequency domain). As described above with reference to Figure 3 As described, CORESET-BR can be allocated to 4-14 OFDM symbols in the time domain and to 20 MHz or less (or 5 MHz or less) in the frequency domain. Figure 4-Figure 5 An example of relative resource allocation of CORESET-BR and PDSCH for different CORESET-BR sizes (eg, the number of OFDM symbols occupied by a CORESET-BR in the time domain) is shown in FIG.

[0091] Figure 4 A first configuration 400 of a CORESET-BR and a PDSCH scheduled by the CORESET-BR is shown. Figure 4In the embodiment, CORESET-BR 410, 420 and 430 and their associated PDSCH 412, 422, 424 and 432 are allocated to 14 OFDM symbols in the time domain and to 5 MHz or less in the frequency domain. Figure 4 In the example shown, CORESET-BR 410 may schedule (e.g., indicate to it the allocation of time-frequency resources) PDSCH 412, CORESET-BR 420 may schedule PDSCH 422 and PDSCH 424, and CORESET-BR 430 may schedule PDSCH 432. In one aspect of this example, the time-frequency resource sets allocated to the CORESET-BR and the corresponding (multiple) PDSCHs may not overlap each other in the time domain or the frequency domain. For example, CORESET-BR 410 may be allocated 14 OFDM symbols in a first time slot (e.g., time slot #1), and PDSCH 412 may be allocated 14 OFDM symbols in a second time slot (e.g., time slot #2) different from the first time slot. In addition, the CORESET-BR and the corresponding PDSCH may not overlap in the frequency domain. For example, the CORESET-BR 410 may be allocated PRBs in a first frequency range, and the PDSCH 412 may be allocated PRBs having a second frequency range different from the first frequency range. Figure 4 In another aspect of the example shown in FIG. 1 , the time-frequency resource sets allocated to the CORESET-BR and the corresponding PDSCH may overlap at least partially in the frequency domain or the time domain. For example, although 14 OFDM symbols may be allocated to the CORESET-BR 420 and the PDSCH 422 in different time slots (e.g., the CORESET-BR 420 may be allocated OFDM symbols in time slot #3, and the PDSCH 424 may be allocated OFDM symbols in time slot #6), the PRBs allocated to the CORESET-BR 420 and the PDSCH 422 may overlap in the frequency domain. Figure 4 As shown in , the PRBs allocated to the CORESET-BR 420 and the PDSCH 422 are allocated in completely overlapping frequency ranges, however, in some implementations, the PRBs allocated to the CORESET-BR and the corresponding PDSCH may be allocated in partially overlapping frequency ranges. Figure 4 In another aspect of the example shown in , the time-frequency resource sets allocated to the CORESET-BR and the corresponding PDSCH may overlap at least partially in the time domain, but not in the frequency domain. For example, the CORESET-BR 430 and the PDSCH 432 may be allocated 14 OFDM symbols in the same time slot (e.g., both the CORESET-BR 430 and the PDSCH 432 may be allocated 14 symbols in time slot #6).

[0092] exist Figure 4 In the example shown, PDSCHs corresponding to different CORESET-BRs may be allocated OFDM symbols in the same time slot and different non-overlapping frequency ranges. For example, CORESET-BR 420 may be allocated OFDM symbols in time slot #3, and the corresponding PDSCH 424 may be allocated OFDM symbols in time slot #6. CORESET-BR 430 may be allocated OFDM symbols in time slot #6, and the corresponding PDSCH 432 may also be allocated OFDM symbols in time slot #6, resulting in PDSCHs corresponding to different CORESET-BRs being allocated the same OFDM symbols and time slots but different PRBs in the frequency domain.

[0093] Figure 5 A second configuration 500 of a CORESET-BR and a PDSCH scheduled by the CORESET-BR is shown. Figure 5 In the example shown, CORESET-BR 510 schedules PDSCH 512 and 514, and CORESET-BR 520 schedules PDSCH 522 and 524. CORESET-BR 510 and 520 and PDSCH 512, 514, 522, and 524 are allocated to at least 7 OFDM symbols in the time domain and to 5 MHz or less in the frequency domain. Figure 5 In the example shown, CORESET-BR 510 can schedule PDSCH 512 and 514, and CORESET-BR 520 can schedule PDSCH 522 and 524. In one aspect of this example, the resources allocated to the CORESET-BR and at least one of the corresponding PDSCHs can overlap with the CORESET-BR in the time domain or the frequency domain. For example, CORESET-BR 510 can be allocated the first 7 OFDM symbols in time slot #1, PDSCH 514 can be allocated the last 7 OFDM symbols in time slot #1, and PDSCH 512 can be allocated all 14 OFDM symbols in time slot #1. In these aspects, CORESET-BR 510 overlaps with PDSCH 512 in the time domain (i.e., the OFDM symbols allocated to CORESET-510 and at least some of the OFDM symbols allocated to PDSCH 512 are scheduled at the same time). In addition, as Figure 5As shown, the CORESET-BR and the corresponding PDSCH may overlap in the frequency domain. For example, CORESET-BR 510 and PDSCH 514 overlap in the frequency domain (i.e., the PRBs allocated to CORESET-BR 510 and PDSCH 514 are allocated within at least partially overlapping frequency ranges). In another aspect of this example, the resources allocated to the CORESET-BR and the corresponding PDSCH may overlap at least partially in both the time domain and the frequency domain. For example, CORESET-BR 520 may be allocated the first 7 OFDM symbols in time slot #2, and PDSCH 522 may be allocated all 14 OFDM symbols in time slot #2. In this example, the OFDM symbol allocated to CORESET-BR 520 is a portion of the OFDM symbol allocated to PDSCH 522. In addition, the PRBs allocated to CORESET-BR 520 and PDSCH 522 may be allocated within overlapping frequency ranges, as shown in FIG. Figure 5 shown.

[0094] Figure 6 An example of REG indexing and REG to CCE assignment according to one or more aspects is illustrated. In some implementations, Figure 6 The REG index can be obtained by Figure 3 The REG index data 366 is indicated, and the REG to CCE assignment can be indicated by Figure 3 The CCE-REG mapping data 364 is indicated. REG (which may also be referred to as PRB for a single OFDM symbol) is Figure 6 are shown as blocks. Figure 6 In the example shown, REGs may be indexed in order of increasing time resources, increasing frequency resources, starting with index 0 for the first OFDM symbol and the lowest numbered PRB (e.g., the lowest frequency range assigned to a PRB or REG). As a non-limiting example, every six consecutive REGs may form a CCE, such that REGs from REG0 to REG5 form CCE0 and REGs from REG6 to REG11 form CCE1. Figure 6A first example 600 of REG indexes and REG to CCE assignments, a second example 610 of REG indexes and REG to CCE assignments, a third example 620 of REG indexes and REG to CCE assignments, and a fourth example 630 of REG indexes and REG to CCE assignments are shown, where each CCE includes six consecutively numbered REGs. The first example 600 corresponds to REG indexes and assignments for a 1-symbol CORESET. For example, because a CORESET is assigned to a single OFDM symbol in the time domain, the REG index may start at 0 for the lowest numbered REG (e.g., PRB), and the index may continue in ascending order (e.g., from 0 to 5) in the frequency domain. The first six REGs (e.g., REGs 0-5) may be assigned to the first CCE. The next six REGs (at the same OFDM symbol and the next six highest frequency ranges) may be assigned to the second CCE, and the assignment of REGs to CCEs continues in this manner for the entire bandwidth assigned to the CORESET.

[0095] The foregoing example is illustrated in a second example 610, which corresponds to REG indexing and assignment for a 2-symbol CORESET. For example, the REG indexing may start at 0 for a first OFDM symbol and a REG at a first frequency range, and it may continue in ascending order in the time domain such that index 1 is assigned to a second OFDM symbol and a REG at the first frequency range. Once all REGs in the first frequency range are indexed, the indexing may continue to a REG at the first OFDM symbol and a second frequency range at a higher frequency than the first frequency range, followed by the next REG at the second OFDM symbol and the second frequency range. This pattern of assigning increasing indices to REG pairs at the same frequency range may continue until all REGs are indexed, and the REGs are then assigned to CCEs in groups of six consecutive REGs in ascending order of indices, as indicated by the different shading of the CCEs in the second example 610.

[0096] The third example 620 corresponds to REG indexing and assignment for a 3-symbol CORESET. The indexing pattern of the REGs in the third example 620 is similar to the indexing pattern associated with the second example 610, where three REGs are assigned in ascending time order for each frequency range (e.g., the indexing progresses from the third REG at the third OFDM symbol and the first frequency range to the fourth REG at the first OFDM symbol and the second frequency range). The fourth example 630 corresponds to REG indexing and assignment for a 14-symbol CORESET. The indexing pattern of the REGs in the fourth example 630 is similar to the indexing pattern associated with the second example 610 and the third example 620, where 14 REGs are assigned in ascending time order for each frequency range (e.g., the indexing progresses from the fourteenth REG at the fourteenth OFDM symbol and the first frequency range to the fifteenth REG at the first OFDM symbol and the second frequency range). In the third example 620 and the fourth example 630, as Figure 6 As indicated by the different shading of the CCEs in FIG, REGs are assigned to CCEs in groups of six consecutively indexed REGs in ascending order. This type of REG indexing and REG to CCE assignment technique may be referred to as following a consecutive pattern in the time domain.

[0097] Fig. 7A and Figure 7B Additional examples of REG indexing and REG to CCE assignment according to one or more aspects are illustrated. In some implementations, Fig. 7A and Figure 7B The REG index can be obtained by Figure 3 The REG index data 366 is indicated, and the REG to CCE assignment can be indicated by Figure 3 The CCE-REG mapping data 364 indicates that as a non-limiting example, each of six consecutive REGs may form a CCE, such that REGs from REG0 to REG5 form CCE0 and REGs from REG6 to REG11 form CCE1.

[0098] Fig. 7A A first example 700 of REG indexing and REG to CCE assignment is illustrated. The first example 700 corresponds to REG indexing and assignment for a 14 symbol CORESET. For reference Figure 6As an alternative to the continuous indexing pattern in the time domain described, the first example 700 is indexed according to a discontinuous pattern in the time domain, which may also be referred to as a "zigzag" pattern. For example, the REG indexing may start with index 0 for the REG at the first OFDM symbol and the first frequency range, and may continue in ascending order in the time domain until the REG at the fourteenth OFDM symbol and the same frequency range is indexed as 13. Then, the indexing may continue to the REG at the same OFDM symbol (i.e., the fourteenth OFDM symbol) and the second frequency range higher than the first frequency range. For the REGs at the second frequency range, the indexing may also continue in the opposite order in the time domain. For illustration, the REGs may be indexed in ascending order from the REG at the fourteenth OFDM symbol and the second frequency range with an index of 14 to the REG at the first OFDM symbol and the second frequency range with an index of 27. The indexing may then continue to the REGs at the next frequency range (e.g., a third frequency range greater than the second frequency range), such that the indexing progresses in ascending order in the time domain from the first OFDM symbol indexed at 28 and the REG at the third frequency range to the fourteenth OFDM symbol indexed at 41 and the REG at the third frequency range. This indexing pattern (interleaving of indexing in ascending time order with indexing in descending time order for alternating frequency ranges) may continue for any remaining higher frequencies. After indexing the REGs, the REGs may be indexed with reference to the REGs. Figure 6 The REGs are assigned to CCEs in a manner similar to that described above, such that each group of 6 consecutive REGs is assigned to a CCE (eg, Fig. 7A ). Because REGs are assigned to CCEs based on this non-contiguous pattern in the time domain, the CCEs may include REGs (e.g., PRBs) that at least partially overlap in the time domain but do not overlap in the frequency domain. For example, the CCEs in the CORESET configuration may include a first number of REGs (e.g., REGs 12 and 13) in ascending order in the time domain and the first frequency range and a second number of REGs (e.g., REGs 14-17) in descending order in the time domain and the second frequency range. In this example, REGs 12 and 13 overlap with REGs 14 and 15 in the time domain. In addition, in this example, the number of REGs in the first frequency range is different from the number of REGs in the second frequency range.

[0099] Figure 7B A second example 720 of REG indexing and REG to CCE assignment is shown. The second example 720 corresponds to REG indexing and assignment for a 6-symbol CORESET. Fig. 7AAs an alternative to the non-continuous indexing pattern in the time domain described, the second example 720 is indexed according to a block-based continuous pattern in the time domain, which may also be referred to as a "block index" pattern. For example, the REG index may start at 0 for the first OFDM symbol and the REG at the first frequency range, and may continue in ascending order (or ascending order) in the time domain until an inflection point OFDM symbol (e.g., a boundary OFDM symbol) that is not the last OFDM symbol in the first frequency range. This inflection point OFDM symbol may facilitate the formation of a "block" in the block-based pattern because it is the last OFDM symbol of the block before the boundary between the block and another block, and as an illustrative, non-limiting example, may be located at a multiple of three OFDM symbols. For example, in a 6-symbol CORESET, the indexing may continue in ascending order in the time domain until the third OFDM symbol that is a multiple of 3, and this REG is indexed as 2 in the second example 720. Similar to the description of Figure 6 The indexing described, the indexing can then continue to the first OFDM symbol indexed as 3 and the REG at the second frequency range higher than the first frequency range. The indexing can also continue in ascending order from the first OFDM symbol in the second frequency range until the inflection point OFDM symbol and the second frequency range, that is, the third OFDM symbol and the second frequency range. For illustration, the REGs can be indexed in ascending order from the first OFDM symbol indexed as 3 and the REG at the second frequency range to the third OFDM symbol indexed as 5 and the REG at the second frequency range. This aforementioned indexing in the first frequency range and the second frequency range starting from the first OFDM symbol to the third OFDM symbol in both the first frequency range and the second frequency range to cover a block of 6 REGs in ascending order is called a "block indexing" mode. The indexing may then continue to a second block that includes indexing the remaining REGs after the inflection OFDM symbol in both the first frequency range and the second frequency range, i.e., the indexing may continue in ascending order from the fourth OFDM symbol indexed at 6 and the REG at the first frequency range to the sixth OFDM symbol indexed at 8 and the REG at the first frequency range, and then from the fourth OFDM symbol indexed at 9 and the REG at the second frequency range to the sixth OFDM symbol indexed at 11 and the REG at the second frequency range. This block indexing pattern may continue for the remaining OFDM symbols and frequencies. After indexing the REGs, the indexing may be performed in the same manner as the reference REG. Figure 6 and Fig. 7A The REGs are assigned to the CCEs in a manner similar to that described above, such that each group of 6 consecutively indexed REGs is assigned to a CCE (eg, Figure 7B This block REG to CCE assignment can also be applied to 9-symbol CORESET or 12-symbol CORESET.

[0100] Fig. 8A and Figure 8B An example of CORESET, PDSCH, and DMRS resource allocation for a CORESET (e.g., CORESET0-BR) for ultralight devices according to one or more aspects is shown. In some implementations, the PDSCH and DMRS resource allocation may be indicated by a DCI received via a PDCCH within the resources allocated to the CORESET, such as Figure 3 The second message 374.

[0101] Fig. 8A A first example 800 of CORESET, PDSCH, and DMRS allocation is shown. In some implementations, DMRS may be allocated to one or more time resources (e.g., OFDM symbols) after the time resources allocated to the CORESET. To illustrate, in the first example 800, DMRS 811 may be allocated to the first OFDM symbol after the last OFDM symbol allocated to the CORESET 810. In addition to the DMRS allocated to the first OFDM symbol after the last OFDM symbol allocated to the CORESET, in some implementations, a DMRS (e.g., DMRS 813) may be repeated at a second OFDM symbol (different from the first OFDM symbol) within a time slot that may be allocated to PDSCH 812. Repeating DMRS may improve demodulation of signals within the PDSCH, particularly PDSCH scheduled for a long duration in the time domain.

[0102] Figure 8B A second example 850 of CORESET, PDSCH, and DMRS allocation is illustrated. In some implementations, the DMRS may be repeated during one or more time resources allocated to the CORESET in addition to the time resources of the first example 800. To illustrate, in an implementation where the PDSCH 822 is scheduled to overlap with the CORESET 820 in the time domain and the CORESET size in the time domain is greater than 3 OFDM symbols, additional DMRS (e.g., DMRS 821) repetitions may be allocated to the first OFDM symbol allocated to both the PDSCH 822 and the CORESET 820. Additional repetitions of the DMRS at different times may improve demodulation of signals received within the PDSCH.

[0103] Fig. 9 900 is a flow chart illustrating an example process 900 for supporting allocation of CORESETs to more than three OFDM symbols in the time domain for reduced bandwidth (eg, ultralight) devices in accordance with one or more aspects. The operations of process 900 may be performed by a UE (such as described above with reference to Figure 1 , Figure 2, Figure 3 UE 115 described or referenced Figure 5 For example, according to one or more aspects, the example operations (also referred to as "blocks") of process 900 may enable UE 115 to support CORESET for use with reduced bandwidth devices.

[0104] In block 902, the UE receives a first message from a base station indicating a CORESET configuration that allocates more than three OFDM symbols in the time domain to a CORESET (e.g., CORESET0-BR). For example, the CORESET configuration may include or correspond to Figure 3 CORESET configuration data 360. In some implementations, the first message includes an RRC message, such as a MIB communicated within a PBCH. For example, the first message may include or correspond to Figure 3 In block 904, the UE monitors a time-frequency resource set to receive a second message from the base station. The time-frequency resource set is allocated based on the CORESET configuration. For example, the monitored time-frequency resource set may include or correspond to Figure 3 The monitored time-frequency resource data 308. In some implementations, the second message includes a DCI communicated within a PDCCH.

[0105] In some implementations, process 900 may include receiving, by the UE, from the base station a second message indicating resource allocation for the PDSCH via a portion of the time-frequency resource set allocated based on the CORESET configuration. For example, the resource allocation for the PDSCH may include or correspond to Figure 3 The CORESET configuration may indicate PDSCH resource allocation data 362. Additionally or alternatively, the CORESET configuration may indicate other communication parameters, such as an SCS value for the UE, and based on the SCS value, the CORESET configuration may allocate different resource sets to the UE. For example, the CORESET configuration may allocate up to 14 OFDM symbols in the time domain and up to 24 PRBs in the frequency domain to the CORESET for communication with an SCS of 15 kHz. As another example, the CORESET configuration may allocate up to 14 OFDM symbols in the time domain and up to 12 PRBs in the frequency domain to the CORESET for communication with an SCS of 30 kHz.

[0106] In some implementations, the CORESET configuration may indicate or allocate a first time slot and one or more PRBs within a first frequency range. Figure 4, the PRBs indicated or allocated by the CORESET configuration may include or correspond to CORESET-BR 410, and the first time slot may include or correspond to time slot #1. In some such implementations, CORESET-BR 410 may schedule the corresponding PDSCH 412 at time slot #2. In such implementations, the first time slot (e.g., time slot #1) may be different from any time slot (e.g., time slot #2) included in the resource allocation for PDSCH. In addition, in such implementations, Figure 4 As illustrated in relation to CORESET-BR 410 and PDSCH 412 in FIG. 1 , the first frequency range may be different from the second frequency range included in the resource allocation for the PDSCH. Additionally or alternatively, the CORESET configuration may indicate or allocate the first time slot and one or more PRBs within the first frequency range. For example, with respect to Figure 4 , the CORESET configuration may indicate the CORESET-BR 420 as being in time slot #3 and the first frequency range, and the CORESET-BR 420 may schedule the corresponding PDSCH 422 in time slot #5. In such implementations, the time slot of the CORESET-BR 420 may be different from any time slot included in the resource allocation for the PDSCH 422. Furthermore, in some such implementations, the first frequency range at least partially overlaps with the second frequency range included in the resource allocation for the PDSCH. For example, Figure 4 As shown in , the PDSCH 422 may be in a first frequency range that overlaps with the frequency range associated with the CORESET-BR 420. Alternatively, the CORESET configuration may indicate or allocate a first frequency range and one or more PRBs within a first time slot included in the resource allocation for the PDSCH, and the first frequency range is different from a second frequency range included in the resource allocation for the PDSCH. For example, referring to Figure 4 , the CORESET-BR 430 and the corresponding PDSCH 432 may both be in the same time slot (ie, time slot #6) but in different frequency ranges (eg, in a first frequency range and a second frequency range, respectively), as shown in FIG. Figure 4 As illustrated in relation to CORESET-BR 430 and PDSCH 432 in FIG. Alternatively, the first frequency range and the second frequency range may at least partially overlap each other, such as Figure 5 As illustrated in FIG. 5 , regarding the CORESET-BR 520 and the corresponding PDSCH 522 .

[0107] In some implementations, the CCEs in the CORESET configuration include a first number of REGs in ascending order in a first frequency range and a second number of REGs in descending order in a second frequency range. Fig. 7A , the third CCE may include REGs 12 and 13 in ascending order in the first frequency range and REGs 14-17 in descending order in the second frequency range (for example, the ascending order and the descending order may refer to the time domain). In such an implementation, some REGs in the CCE (for example, REGs 12 and 13) may overlap with other REGs in the CCE (for example, REGs 14-17) in the time domain. Additionally or alternatively, the number of REGs in the first frequency range (for example, REGs 12 and 13) and the number of REGs in the second frequency range (for example, REGs 14-17) may be different. In some other implementations, the CCEs in the CORESET configuration may include a first number of REGs in ascending order in the first frequency range and a second number of REGs in ascending order in the second frequency range. For example, referring to Figure 7B , the first CCE may include REGs 0-2 in ascending order in the first frequency range and REGs 3-5 in ascending order in the second frequency range (e.g., both ascending orders may refer to the time domain). In such implementations, each REG in the first frequency range (e.g., REGs 0-2) is in the same OFDM symbol in the time domain as the corresponding REG in the second frequency range (e.g., REGs 3-5). In some such implementations, the CORESET configuration may allocate multiples of three OFDM symbols to the CORESET, such as Figure 7B As shown in the figure, three OFDM symbols are allocated to each OFDM symbol in CCE (and CORESET corresponds to one or more CCEs).

[0108] In some implementations, process 900 includes monitoring a DMRS at a first OFDM symbol after a last OFDM symbol allocated to the CORESET by the CORESET configuration. Fig. 8A , DMRS 811 may be allocated at the first OFDM symbol after the last OFDM symbol allocated to CORESET 810. In some such implementations, process 900 includes monitoring an additional portion of the DMRS at the second OFDM symbol in the time slot allocated to the PDSCH. For example, referring to Fig. 8A, DMRS 813 may be repeated at a second OFDM symbol (different from the first OFDM symbol) within a time slot that may be allocated to PDSCH 812. In some implementations, process 900 includes monitoring DMRS at a first OFDM symbol allocated to the CORESET by the CORESET configuration and a first OFDM symbol after a last OFDM symbol allocated to the CORESET by the CORESET configuration based on the number of OFDM symbols allocated to the CORESET by the CORESET configuration satisfying a threshold. For example, referring to Figure 8B Because PDSCH 822 is scheduled to overlap with CORESET 820 in the time domain, and the CORESET size in the time domain is greater than 3 OFDM symbols, the UE may monitor DMRS 821 (eg, DMRS repetition) at the first OFDM symbol allocated to both PDSCH 822 and CORESET 820.

[0109] Fig.10 1 is a block diagram of an example UE 1000 that supports allocating CORESETs to more than three OFDM symbols in the time domain for reduced bandwidth (e.g., ultra-light) devices according to one or more aspects. In some implementations, the UE 1000 may be a reduced bandwidth (e.g., ultra-light) device. The UE 1000 may be configured to perform operations, including reference to Fig. 9 In some implementations, the UE 1000 includes a block of the process 900 described above. Figure 1-Figure 3 1000. For example, the UE 1000 includes a controller 280 that operates to execute logic or computer instructions stored in a memory 282 and controls components of the UE 1000 for providing the features and functions of the UE 1000. Under the control of the controller 280, the UE 1000 transmits and receives signals via the radios 1001a-r and the antennas 252a-r. The radios 1001a-r include, for example, Figure 2 Various components and hardware are shown for UE 115 in FIG. 1 , including modulators and demodulators 254a - r , MIMO detector 256 , receive processor 258 , transmit processor 264 , and TX MIMO processor 266 .

[0110] As shown, the memory 282 may include PBCH receiving logic 1002 and CORESET monitoring logic 1003. The PBCH receiving logic 1002 may be configured to receive a first message indicating a CORESET configuration within a PBCH. The CORESET configuration allocates more than three OFDM symbols in the time domain to the CORESET. The CORESET monitoring logic 1003 may be configured to monitor a time-frequency resource set to receive a second message from the base station. The time-frequency resource set has a CORESET configuration. The UE 1000 may receive a second message from one or more network entities (such as Figure 1-Figure 3 Base station 105 or Fig.12 The base station shown in the figure may receive signals or transmit signals to one or more network entities.

[0111] Fig.11 1 is a flow chart illustrating an example process 1100 for supporting generation of a CORESET of more than three OFDM symbols in the time domain for a reduced bandwidth (eg, ultralight) device in accordance with one or more aspects. The operations of process 1100 may be performed by a base station (such as described above with reference to Figure 1-Figure 3 Base station 105 described or referred to below Fig.12 The base station described above) is used for execution.

[0112] At block 1102, a base station generates a first message indicating a CORESET configuration that allocates more than three OFDM symbols in the time domain to a CORESET (e.g., CORESET0-BR). For example, the CORESET configuration may include or correspond to Figure 3 In some implementations, the first message includes an RRC message, such as a MIB communicated within a PBCH. In block 1104, the base station transmits the first message to the UE. For example, the first message may include or correspond to Figure 3 The first message 370.

[0113] In some implementations, process 1100 may also include transmitting a second message to the UE via the time-frequency resource set having the CORESET configuration. The second message indicates resource allocation for the PDSCH. For example, the second message may include or correspond to Figure 3 The second message 374, and the resource allocation of the PDSCH may include or correspond to Figure 3 PDSCH resource allocation data 362.

[0114] In some implementations, process 1100 includes transmitting DCI to a UE via a time-frequency resource set having a CORESET configuration. For example, the DCI may include or correspond to Figure 3In such an implementation, the DCI indicates resource allocation for the PDSCH, and the starting symbol of the PDSCH includes one of the fourth OFDM symbol to the twelfth OFDM symbol of the time slot allocated to the PDSCH by the resource allocation. Figure 3 , the second message 374 includes the PDSCH resource allocation data 362 and includes information about the starting symbol of the PDSCH, which may indicate the starting OFDM symbol of the PDSCH as shown in Table 1 and Table 2.

[0115] In some implementations, process 1100 includes transmitting a DMRS at a first OFDM symbol after a last OFDM symbol allocated to the CORESET by the CORESET configuration. Fig. 8A , DMRS 811 may be allocated at the first OFDM symbol after the last OFDM symbol allocated to CORESET 810. In some such implementations, process 1100 includes transmitting an additional portion of the DMRS at the second OFDM symbol in the time slot allocated to the PDSCH. For example, referring to Fig. 8A , the DMRS 813 may be repeated at a second OFDM symbol (different from the first OFDM symbol) within a time slot that may be allocated to the PDSCH 812. Additionally or alternatively, the process 1100 may include transmitting a DMRS at a first OFDM symbol allocated to the CORESET by the CORESET configuration and at a first OFDM symbol after a last OFDM symbol allocated to the CORESET by the CORESET configuration based on the number of OFDM symbols allocated to the CORESET by the CORESET configuration satisfying a threshold. For example, referring to Figure 8B , if the number of OFDM symbols allocated to CORESET 820 meets a threshold, DMRS 821 (e.g., additional DMRS repetitions) may be allocated to the first OFDM symbol, which is allocated to both PDSCH 822 and CORESET 820. In some such implementations, the threshold may be 3, or any integer between 3 and 12.

[0116] Fig.12 is a block diagram of an example base station 1200 that supports generating a CORESET of more than three OFDM symbols in the time domain for a reduced bandwidth (e.g., ultra-light) device according to one or more aspects. The base station 1200 may be configured to perform operations, including referring to Fig.11 In some implementations, the base station 1200 includes a block of the process 1100 described in detail. Figure 1-Figure 3The structure, hardware, and components shown and described for base station 105 of the present invention are shown and described in detail. For example, base station 1200 may include controller 240 that operates to execute logic or computer instructions stored in memory 1242 and control components of base station 1200 that provide features and functionality of base station 1200. Base station 1200 transmits and receives signals via radios 1201a-t and antennas 1234a-t under the control of controller 240. Figure 2 As shown, the radios 1201a - t include various components and hardware for the base station 105 , including modulators and demodulators 232a - t , a transmit processor 220 , a TX MIMO processor 230 , a MIMO detector 236 , and a receive processor 238 .

[0117] As shown, the memory 1242 may include CORESET configuration logic 1202, PDSCH resource allocation logic 1203, and transmission logic 1204. The CORESET configuration logic 1202 may be configured to generate a first message indicating a CORESET configuration. The CORESET configuration allocates more than three OFDM symbols in the time domain to the CORESET. The PDSCH resource allocation logic 1203 may be configured to generate a PDSCH resource allocation to be included in a second message. The PDSCH resource allocation may indicate the time-frequency resources allocated to the PDSCH. The transmission logic 1204 may be configured to transmit the first message and the second message to the UE. The base station 1200 may receive information from one or more network entities (such as Figure 1-Figure 3 UE 115 or Fig.10 UE 1000) receives signals or transmits signals to it.

[0118] It should be noted that, referring to Fig. 9 and Fig.11 One or more blocks (or operations) described in one or more figures may be combined with one or more blocks (or operations) described in another figure with reference to the figure. Fig. 9 One or more boxes (or operations) of Fig.11 As another example, with Fig. 9 and Fig.11 One or more boxes can be associated with Figure 1-Figure 3 One or more associated boxes (or operations) are combined. Additionally or alternatively, the above reference Figure 1-Figure 3 One or more of the operations described may be combined with reference to Fig.10 or Fig.12 Describes a combination of one or more operations.

[0119] In one or more aspects, techniques for supporting allocation of more than three OFDM symbols in the time domain to CORESETS for devices with reduced bandwidth may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a first aspect, supporting allocation of more than three OFDM symbols in the time domain to a CORESET for devices with reduced bandwidth (e.g., ultralight) may include an apparatus configured to receive a first message indicating a CORESET configuration from a base station. The CORESET configuration allocates more than three OFDM symbols in the time domain to the CORESET. The apparatus is also configured to monitor a time-frequency resource set to receive a second message from the base station. The time-frequency resource set has a CORESET configuration. In addition, the apparatus may be performed or operated according to one or more aspects as described below. In some implementations, the apparatus includes a wireless device, such as a UE. In some implementations, the apparatus may include at least one processor, and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other implementations, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, and the program code may be executable by a computer for causing the computer to perform the operations described herein with reference to the apparatus. In some implementations, the apparatus may include one or more units configured to perform the operations described herein. In some implementations, the method of wireless communication may include one or more operations described herein with reference to the apparatus.

[0120] In a second aspect, in combination with the first aspect, the first message includes an RRC message and the second message includes a DCI.

[0121] In a third aspect, in combination with one or more of the first aspect or the second aspect, the apparatus is configured to receive a second message indicating resource allocation for the PDSCH from a base station via a portion of the time-frequency resource set having a CORESET configuration.

[0122] In a fourth aspect, in combination with one or more of the first to third aspects, a CORESET configuration is associated with communication between a device and a base station via a BWP of less than 5 MHz. The CORESET configuration allocates 4 to 14 OFDM symbols in the time domain to the CORESET.

[0123] In a fifth aspect, in combination with one or more of the first to fourth aspects, a CORESET configuration allocates up to 14 OFDM symbols in the time domain and up to 24 PRBs in the frequency domain to the CORESET for communication with an SCS of 15 kHz.

[0124] In a sixth aspect, in combination with one or more of the first to fifth aspects, a CORESET configuration allocates up to 14 OFDM symbols in the time domain and up to 12 PRBs in the frequency domain to the CORESET for communication with an SCS of 30 kHz.

[0125] In a seventh aspect, in combination with one or more of the first to sixth aspects, the second message indicates a resource allocation for PDSCH. The CORESET configuration allocates at least one of the following: a first time slot and one or more PRBs in a first frequency range, wherein the first time slot is different from any time slot included in the resource allocation for PDSCH, and wherein the first frequency range is different from a second frequency range included in the resource allocation for PDSCH; a first time slot and one or more PRBs in a first frequency range, wherein the first time slot is different from any time slot included in the resource allocation for PDSCH, and wherein the first frequency range at least partially overlaps with the second frequency range included in the resource allocation for PDSCH; a first time slot and one or more PRBs in a first frequency range, wherein the first time slot is included in the resource allocation for PDSCH, and wherein the first frequency range is different from the second frequency range included in the resource allocation for PDSCH; or a first time slot and one or more PRBs in a first frequency range, wherein the first time slot is included in the resource allocation for PDSCH, and wherein the first frequency range at least partially overlaps with the second frequency range included in the resource allocation for PDSCH.

[0126] In an eighth aspect, in combination with one or more of the first to seventh aspects, a CCE in a CORESET configuration includes a specific number of REGs. A first number of REGs in ascending order in a first frequency range and a second number of REGs in descending order in a second frequency range form the CCE. At least some of the first REGs and the second REGs overlap in the time domain.

[0127] In a ninth aspect, in combination with the eighth aspect, the first number of REGs is different from the second number of REGs.

[0128] In a tenth aspect, in combination with one or more of the first to seventh aspects, a CCE in a CORESET configuration includes a specific number of REGs. A first number of REGs in ascending order in a first frequency range and a second number of REGs in ascending order in a second frequency range form the CCE. Each REG in the first number of REGs is within the same OFDM symbol in the time domain as a corresponding REG in the second number of REGs.

[0129] In an eleventh aspect, in combination with the tenth aspect, a CORESET configuration allocates multiples of three OFDM symbols to the CORESET.

[0130] In the twelfth aspect, in combination with one or more of the first to eleventh aspects, the second message indicates resource allocation for PDSCH. The starting symbol of PDSCH includes one OFDM symbol from the fourth to twelfth OFDM symbols of the time slot allocated to PDSCH by resource allocation.

[0131] In a thirteenth aspect, in combination with one or more of the first to twelfth aspects, the apparatus is configured to monitor a DMRS at a first OFDM symbol after a last OFDM symbol allocated to the CORESET by the CORESET configuration.

[0132] In a fourteenth aspect, in combination with the thirteenth aspect, the apparatus is configured to monitor an additional portion of a DMRS at a second OFDM symbol within a time slot, which is allocated to the PDSCH by a resource allocation for the PDSCH included in the second message.

[0133] In the fifteenth aspect, in combination with one or more of the first to fourteenth aspects, the apparatus is configured to monitor the DMRS at the first OFDM symbol allocated to the CORESET by the CORESET configuration and the first OFDM symbol after the last OFDM symbol allocated to the CORESET by the CORESET configuration based on the number of OFDM symbols allocated to the CORESET by the CORESET configuration satisfying a threshold.

[0134] In a sixteenth aspect, supporting allocation of more than three OFDM symbols in a time domain to a CORESET by a device for bandwidth reduction (e.g., ultralight) may include: a device configured to generate a first message indicating a CORESET configuration. The CORESET configuration allocates more than three OFDM symbols in a time domain to the CORESET. The device is also configured to: transmit a first message to a UE. In addition, the device may be performed or operated according to one or more aspects as described below. In some implementations, the device includes a wireless device, such as a base station. In some implementations, the device may include at least one processor, and a memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the device. In some other implementations, the device may include a non-transitory computer-readable medium having program code recorded thereon, and the program code may be executable by a computer for causing the computer to perform the operations described herein with reference to the device. In some implementations, the device may include one or more units configured to perform the operations described herein. In some implementations, a method of wireless communication may include one or more operations described herein with reference to the device.

[0135] In a seventeenth aspect, in combination with the sixteenth aspect, the apparatus is configured to transmit a second message to the UE via a time-frequency resource set having a CORESET configuration. The second message indicates resource allocation for the PDSCH.

[0136] In the eighteenth aspect, in combination with the seventeenth aspect, the CORESET configuration allocates: one or more PRBs in a first time slot and a first frequency range, wherein the first time slot is different from any time slot included in the resource allocation for PDSCH, and wherein the first frequency range is different from a second frequency range included in the resource allocation for PDSCH; one or more PRBs in a first time slot and a first frequency range, wherein the first time slot is different from any time slot included in the resource allocation for PDSCH, and wherein the first frequency range at least partially overlaps with the second frequency range included in the resource allocation for PDSCH; one or more PRBs in a first time slot and a first frequency range, wherein the first time slot is included in the resource allocation for PDSCH, and wherein the first frequency range is different from the second frequency range included in the resource allocation for PDSCH; or one or more PRBs in a first time slot and a first frequency range, wherein the first time slot is included in the resource allocation for PDSCH, and wherein the first frequency range at least partially overlaps with the second frequency range included in the resource allocation for PDSCH.

[0137] In a nineteenth aspect, in combination with one or more of the sixteenth to eighteenth aspects, a CCE in a CORESET configuration includes a specific number of REGs. A first number of REGs in ascending order in a first frequency range and a second number of REGs in descending order in a second frequency range form the CCE. At least some of the first REGs and the second REGs overlap in the time domain.

[0138] In a twentieth aspect, in combination with one or more of the sixteenth to eighteenth aspects, a CCE in a CORESET configuration includes a specific number of REGs. A first number of REGs in ascending order in a first frequency range and a second number of REGs in ascending order in a second frequency range form the CCE. Each REG in the first number of REGs is within the same OFDM symbol in the time domain as a corresponding REG in the second number of REGs.

[0139] In the twenty-first aspect, in combination with one or more of the sixteenth to twentieth aspects, the apparatus is configured to transmit a DCI to a UE via a time-frequency resource set having a CORESET configuration. The DCI indicates resource allocation for a PDSCH. The starting symbol of the PDSCH includes one of the fourth to twelfth OFDM symbols of the time slot allocated to the PDSCH by resource allocation.

[0140] In a twenty-second aspect, in combination with one or more of the sixteenth to twenty-first aspects, the apparatus is configured to transmit to the UE a DMRS at a first OFDM symbol after a last OFDM symbol allocated to the CORESET by the CORESET configuration.

[0141] In a twenty-third aspect, in combination with one or more of aspects 16 to 22, the apparatus is configured to transmit a second message to the UE via a time-frequency resource set with a CORESET configuration. The second message indicates a resource allocation for the PDSCH. The apparatus is further configured to transmit to the UE an additional portion of the DMRS at a second OFDM symbol within a time slot allocated to the PDSCH.

[0142] In the twenty-fourth aspect, in combination with one or more of the sixteenth to twenty-third aspects, the apparatus is configured to transmit to the UE a DMRS at the first OFDM symbol allocated to the CORESET by the CORESET configuration and at the first OFDM symbol after the last OFDM symbol allocated to the CORESET by the CORESET configuration based on the number of OFDM symbols allocated to the CORESET by the CORESET configuration satisfying a threshold.

[0143] It will be appreciated by those skilled in the art that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0144] This article is about Figures 1 to 12 The components, functional blocks and modules described include processors, electronic devices, hardware devices, electronic components, logical circuits, memories, software codes, firmware codes, etc., or any combination thereof. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, and / or functions, etc., whether referred to in software, firmware, middleware, microcode, hardware description language or other terms. In addition, the features discussed herein can be implemented via dedicated processor circuits, via executable instructions or a combination thereof.

[0145] The technician will further understand that the various schematic logic boxes, modules, circuits and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various exemplary components, boxes, modules, circuits and steps have been roughly described in terms of their functionality. Whether this functionality is implemented as hardware or software depends on specific applications and the design constraints proposed to the entire system. Those skilled in the art can implement the described functions in different ways for each specific application, but such implementation decisions should not be interpreted as causing deviations from the scope of the present disclosure. The technician will also easily recognize that the order or combination of components, methods or interactions described herein are merely examples, and the components, methods or interactions of various aspects of the present disclosure can be combined or performed in a manner other than the manner illustrated and described herein.

[0146] The various illustrative logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the implementations disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and illustrated in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0147] The hardware and data processing apparatus for implementing the various illustrative logics, logic blocks, modules and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller or state machine. In some implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some implementations, specific processes and methods may be performed by circuits specific to a given function.

[0148] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or in any combination thereof. Implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on computer storage media for execution by data processing apparatus or for controlling the operation of data processing apparatus.

[0149] If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium or transmitted by a computer-readable medium. The process of the method or algorithm disclosed herein can be implemented in a processor executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that can be implemented to transfer a computer program from one place to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such a computer-readable medium may include a random access memory (RAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a CD-ROM or other optical disk storage device, a magnetic disk storage device or other magnetic storage device, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. And, any connection can also be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and blue discs, wherein disks usually magnetically replicate data, and optical discs optically replicate data with lasers. The above combination should also be included in the scope of computer-readable media. In addition, the operations of a method or algorithm may be located as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0150] Various modifications to the implementations described in this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to some other implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the implementations shown herein, but are to be consistent with the broadest scope consistent with this disclosure, the principles and novel features disclosed herein.

[0151] In addition, those skilled in the art will readily appreciate that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions corresponding to the orientation of the drawings on a correctly oriented page, and may not reflect the correct orientation of any device as implemented.

[0152] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations separately or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be removed from the combination, and a claimed combination may be directed to a subcombination, or variations of a subcombination.

[0153] Similarly, although the operations are depicted in a specific order in the figure, this should not be understood as requiring such operations to be performed in the specific order shown or in a sequential order, or to perform all the operations shown to achieve the desired result. Further, the accompanying drawings may schematically depict one or more example processes in the form of a flow chart. However, other operations not depicted may be incorporated into the schematically illustrated example process. For example, one or more additional operations may be performed before, after, simultaneously or between any illustrated operations. In some environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the implementation described above should not be understood as requiring such separation in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. In addition, some other implementations also fall within the scope of the appended claims. In some cases, the actions described in the claims can be performed in different orders and still achieve the desired result.

[0154] As used herein, including in the claims, the term "or" used in a list of two or more items means that any one of the listed items may be employed alone, or any combination of two or more of the listed items may be employed. For example, if a composition is described as comprising components A, B, or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; a combination of A, B, and C. In addition, as used herein, including in the claims, "or" as used in a list of items beginning with "at least one" means a disjunctive list, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these. The term "substantially" is defined as being largely, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed implementation, the term “substantially” may be replaced with “within [percent] of” a specified content, where the percentage includes 0.1%, 1%, 5%, or 10%.

[0155] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein, but to be consistent with the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication, the method comprising: receiving, at a user equipment UE, from a base station, a first message indicating a control resource set CORESET configuration, the CORESET configuration corresponding to communication between the UE and the base station via a bandwidth part BWP of less than 5 megahertz MHz, the CORESET configuration allocating 4 to 14 orthogonal frequency division multiplexing OFDM symbols in the time domain to the CORESET; monitoring a time-frequency resource set to receive a second message from the base station at the UE, the time-frequency resource set having the CORESET configuration; and The first message comprises a radio resource control (RRC) message, and the second message comprises downlink control information (DCI).

2. The method according to claim 1, further comprising: The second message is received at the UE from the base station via a portion of the time-frequency resource set having the CORESET configuration, the second message indicating resource allocation for a physical downlink shared channel (PDSCH).

3. The method according to claim 1, wherein: The CORESET configuration allocates up to 14 OFDM symbols in the time domain and up to 24 physical resource blocks PRBs in the frequency domain to the CORESET for communication with a subcarrier spacing SCS of 15 kHz.

4. The method according to claim 1, wherein: The CORESET configuration allocates up to 14 OFDM symbols in the time domain and up to 12 physical resource blocks PRBs in the frequency domain to the CORESET for communication with a subcarrier spacing SCS of 30 kHz.

5. The method of claim 1 , wherein the second message indicates resource allocation for a physical downlink shared channel (PDSCH), and wherein the CORESET configuration allocates at least one of: one or more physical resource blocks (PRBs) in a first time slot and a first frequency range, wherein the first time slot is different from any time slot included in the resource allocation for the PDSCH, and wherein the first frequency range is different from a second frequency range included in the resource allocation for the PDSCH; one or more physical resource blocks (PRBs) in a first time slot and a first frequency range, wherein the first time slot is different from any time slot included in the resource allocation for the PDSCH, and wherein the first frequency range at least partially overlaps with a second frequency range included in the resource allocation for the PDSCH; one or more physical resource blocks (PRBs) in a first time slot and a first frequency range, wherein the first time slot is included in the resource allocation for the PDSCH, and wherein the first frequency range is different from a second frequency range included in the resource allocation for the PDSCH; or One or more physical resource blocks (PRBs) in a first time slot and a first frequency range, wherein the first time slot is included in the resource allocation for the PDSCH, and wherein the first frequency range at least partially overlaps with a second frequency range included in the resource allocation for the PDSCH.

6. The method according to claim 1, wherein: The control channel element CCE in the CORESET configuration includes a specific number of resource element groups REGs, wherein a first number of REGs in an ascending order in a first frequency range and a second number of REGs in a descending order in a second frequency range form the CCE, and wherein at least some of the first number of REGs and the second number of REGs overlap in the time domain.

7. The method according to claim 6, wherein: The first number of REGs is different from the second number of REGs.

8. The method according to claim 1, wherein: The control channel element CCE in the CORESET configuration includes a specific number of resource element groups REGs, wherein a first number of REGs in ascending order in a first frequency range and a second number of REGs in ascending order in a second frequency range form the CCE, and wherein each REG of the first number of REGs is in the same OFDM symbol as a corresponding REG of the second number of REGs in the time domain.

9. The method of claim 8, wherein the CORESET configuration allocates multiples of three OFDM symbols to the CORESET.

10. The method according to claim 1, wherein the second message indicates resource allocation for a physical downlink shared channel (PDSCH), and wherein a starting symbol of the PDSCH includes one of a fourth OFDM symbol to a twelfth OFDM symbol of a time slot allocated to the PDSCH by the resource allocation.

11. The method of claim 1 , wherein the CORESET configuration corresponds to a reduced bandwidth device, and wherein the first message further defines a second CORESET configuration for a non-reduced bandwidth device.

12. An apparatus for wireless communication, the apparatus comprising: at least one processor; and a memory coupled to the at least one processor, wherein the at least one processor is configured to: receiving, from a base station, a first message indicating a control resource set CORESET configuration, the CORESET configuration corresponding to communication with the base station via a bandwidth part BWP less than 5 megahertz MHz, the CORESET configuration allocating 4 to 14 orthogonal frequency division multiplexing OFDM symbols in the time domain to the CORESET; monitoring a time-frequency resource set to receive a second message from the base station, the time-frequency resource set having the CORESET configuration; monitoring a demodulation reference signal (DMRS) at a first OFDM symbol after a last OFDM symbol allocated to the CORESET by the CORESET configuration; as well as An additional portion of the DMRS at a second OFDM symbol within a time slot allocated to a physical downlink shared channel (PDSCH) by a resource allocation for the PDSCH included in the second message is monitored.

13. The device according to claim 12, wherein: The CORESET configuration allocates 14 OFDM symbols in the time domain and 24 physical resource blocks PRBs in the frequency domain to the CORESET for communication with a subcarrier spacing SCS of 15 kHz; or the CORESET configuration allocates 14 OFDM symbols in the time domain and 12 physical resource blocks PRBs in the frequency domain to the CORESET for communication with a subcarrier spacing SCS of 30 kHz.

14. The apparatus of claim 12, wherein the second message indicates a resource allocation for a physical downlink shared channel (PDSCH), wherein the CORESET configuration allocates one or more physical resource blocks (PRBs) in a first time slot and a first frequency range, wherein the first time slot is included in the resource allocation for the PDSCH, and wherein the first frequency range is different from a second frequency range included in the resource allocation for the PDSCH.

15. The device according to claim 12, wherein: The control channel element CCE in the CORESET configuration includes a specific number of resource element groups REGs, wherein a first number of REGs in an ascending order in a first frequency range and a second number of REGs in a descending order in a second frequency range form the CCE, and wherein at least some of the first number of REGs and the second number of REGs overlap in the time domain.

16. The device according to claim 15, wherein: The first number of REGs is different from the second number of REGs.

17. A wireless communication method, the method comprising: generating, at a base station, a first message indicating a control resource set CORESET configuration, the CORESET configuration corresponding to communication between a user equipment UE and the base station via a bandwidth part BWP less than 5 megahertz MHz, the CORESET configuration allocating 4 to 14 orthogonal frequency division multiplexing OFDM symbols in the time domain to the CORESET; transmitting the first message to the UE; as well as A second message is transmitted to the UE via the time-frequency resource set having the CORESET configuration, the second message indicating resource allocation for a physical downlink shared channel (PDSCH).

18. The method according to claim 17, wherein: The CORESET configuration assigns: one or more physical resource blocks (PRBs) in a first time slot and a first frequency range, wherein the first time slot is different from any time slot included in the resource allocation for the PDSCH, and wherein the first frequency range is different from a second frequency range included in the resource allocation for the PDSCH; one or more PRBs within a first time slot and a first frequency range, wherein the first time slot is different from any time slot included in the resource allocation for the PDSCH, and wherein the first frequency range at least partially overlaps with a second frequency range included in the resource allocation for the PDSCH; one or more PRBs within a first time slot and a first frequency range, wherein the first time slot is included in the resource allocation for the PDSCH, and wherein the first frequency range is different from a second frequency range included in the resource allocation for the PDSCH; or One or more PRBs within a first time slot and a first frequency range, wherein the first time slot is included in the resource allocation for the PDSCH, and wherein the first frequency range at least partially overlaps with a second frequency range included in the resource allocation for the PDSCH.

19. The method according to claim 17, wherein: The control channel element CCE in the CORESET configuration includes a specific number of resource element groups REGs, wherein a first number of REGs in an ascending order in a first frequency range and a second number of REGs in a descending order in a second frequency range form the CCE, and wherein at least some of the first number of REGs and the second number of REGs overlap in the time domain.

20. The method according to claim 17, wherein: The control channel element CCE in the CORESET configuration includes a specific number of resource element groups REGs, wherein a first number of REGs in ascending order in a first frequency range and a second number of REGs in ascending order in a second frequency range form the CCE, and wherein each REG of the first number of REGs is in the same OFDM symbol as a corresponding REG of the second number of REGs in the time domain.

21. An apparatus for wireless communication, the apparatus comprising: at least one processor; and a memory coupled to the at least one processor, wherein the at least one processor is configured to: generating a first message indicating a control resource set CORESET configuration, the CORESET configuration corresponding to communication with a user equipment UE via a bandwidth part BWP less than 5 megahertz MHz, the CORESET configuration allocating 4 to 14 orthogonal frequency division multiplexing OFDM symbols in the time domain to the CORESET; Initiate transmission of the first message to the UE; and The at least one processor is further configured to initiate transmission of a demodulation reference signal DMRS to the UE at a first OFDM symbol after a last OFDM symbol allocated to the CORESET by the CORESET configuration.

22. The apparatus of claim 21, wherein the at least one processor is further configured to: Initiate transmission of a second message to the UE via the time-frequency resource set having the CORESET configuration, the second message indicating resource allocation for a physical downlink shared channel PDSCH; and Transmission of an additional portion of the DMRS at a second OFDM symbol within a slot allocated to the PDSCH is initiated to the UE.