Two-stage DCI multiplexing in PDSCH

Abstract

An apparatus, a method, and a computer program product for wireless communication are provided. An example method may include receiving, from a network node, a first level of downlink control information (DCI) associated with a second level of DCI, where the first level of DCI includes information about a set of time and frequency resources associated with a physical downlink shared channel (PDSCH), and where the second level of DCI includes decoding information associated with the PDSCH. The example method may also include receiving, from the network node, a transmission including a second level DCI and a PDSCH based on the information about the time and frequency resource set, where the second level DCI is multiplexed with the PDSCH, and where the second level DCI overlaps in time with the PDSCH. The example method may also include decoding the PDSCH based on the second level DCI.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. non-provisional patent application No. 18 / 500,038, filed November 1, 2023, entitled “TWO-STAGE DCI MULTIPLEXING INPDSCH (Two-Stage DCI Multiplexing in PDSCH),” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0002] This disclosure relates generally to communication systems, and more specifically to wireless communication systems having two levels of downlink control information (DCI). Background Technology

[0003] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol that enables different wireless devices to communicate at the city, national, regional, and even global levels. An example telecommunications standard is 5G New Radio (NR). 5G NR is part of the Continuous Evolution of Mobile Broadband (CEM) program issued by the 3rd Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT),) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR can be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. Furthermore, these improvements can also be applied to other multiple access technologies and telecommunications standards that adopt these technologies. Summary of the Invention

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

[0006] In one aspect of this disclosure, methods, computer-readable media, and apparatus are provided at a user equipment (UE). The apparatus may include at least one memory and at least one processor coupled to the at least one memory. At least partially based on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to receive from a network node a first-level DCI associated with second-level downlink control information (DCI), wherein the first-level DCI includes information about a set of time and frequency resources associated with a physical downlink shared channel (PDSCH), and wherein the second-level DCI includes decoding information associated with the PDSCH. At least partially based on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to receive from a network node a transmission including the second-level DCI and the PDSCH based on information about the time and frequency resource sets, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time. At least partially based on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to decode the PDSCH based on the second-level DCI.

[0007] In another aspect of this disclosure, methods, computer-readable media, and apparatuses are provided at a network entity. The apparatus may include at least one memory and at least one processor coupled to the at least one memory. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to transmit a first-level DCI associated with a second-level DCI to a UE, wherein the first-level DCI includes information about a set of time and frequency resources associated with a PDSCH, and wherein the second-level DCI includes decoding information associated with the PDSCH. Based at least in part on information stored in the at least one memory, the at least one processor is configured, individually or in any combination, to transmit a transmission including a second-level DCI and a PDSCH to a UE based on information about a set of time and frequency resources, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time.

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

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

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

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

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

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

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

[0015] Figure 4 This is a diagram illustrating a two-level downlink control information (DCI) example.

[0016] Figure 5 This is a diagram illustrating a two-level DCI, where a single first-level DCI is associated with multiple second-level DCIs.

[0017] Figure 6 This is an example diagram of a two-level DCI, where the first-level DCI is transmitted based on a first beam, and the associated second-level DCI is transmitted based on a second beam different from the first beam.

[0018] Figure 7A This is an example diagram of a two-level DCI, where the first-level DCI is associated with the second-level DCI, and the PDSCH is rate-matched around the second-level DCI.

[0019] Figure 7B This is an example diagram of a two-level DCI, where the first-level DCI is associated with the second-level DCI, and the PDSCH performs rate matching around the second-level DCI and the first-level DCI.

[0020] Figure 8 This is a diagram illustrating an example of communication between a network node and a UE.

[0021] Figure 9 This is a flowchart of a wireless communication method.

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

[0023] Figure 11 These are illustrations illustrating specific hardware implementations used for example devices and / or network entities.

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

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

[0026] Various apparatuses and methods are presented with reference to several aspects of a telecommunications system. These apparatuses and methods are described in detail below and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively, “elements”). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.

[0027] User equipment (UE) can blindly detect and decode Level 1 downlink control information (DCI) (e.g., similar to single-level DCI detection). After the Level 1 DCI is decoded, the UE can decode the Level 2 DCI with minimal additional UE processing. For the transmission of the Level 2 DCI, it can be (1) carried in a scheduled physical downlink shared channel (PDSCH) or (2) transmitted in a configured search space (SS). Some wireless communication systems support PDSCH rate matching around the scheduled DCI. In some aspects provided herein, the PDSCH can be rate matched around the Level 2 DCI. For example, to rate match the PDSCH around the Level 2 DCI, network nodes can encode the PDSCH based on a rate matching pattern and avoid conflicts between the Level 2 DCI and the PDSCH (e.g., transmission in the same time and frequency resources). The Level 2 DCI can overlap in time and can use different frequency domain resources. Interleaved control channel element (CCE) to resource element group (REG) mappings can be used for the Level 2 DCI, which can provide better frequency diversity than contiguous resource mappings. In some respects, a separate SS set for Level 2 DCI can exist, which can be specified as an aggregation level, and the DCI format can be provided in the SS set configuration associated with the SS set. Multiplexing Level 2 DCI and scheduled PDSCH within the same physical resources can be beneficial, allowing Level 2 DCI and PDSCH to be transmitted in the same narrow beam. Multiplexing Level 2 DCI and scheduled PDSCH within the same physical resources allows for easier resource management for multi-UE scheduling by allocating the Level 2 DCI and PDSCH of the same UE in the same symbol and resource block (RB) segments without gaps between them.

[0028] As an example, an element, any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. When multiple processors are implemented, the multiple processors may perform functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionalities described throughout this disclosure. One or more processors in the processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, or any combination thereof.

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

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

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

[0032] Aggregated base stations can be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. Decentralized base stations can be configured to utilize a protocol stack that is physically or logically distributed across two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, the CU may be implemented within a RAN node, and one or more DUs may co-located with the CU, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DUs may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, namely a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

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

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

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

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

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

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

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

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

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

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

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

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

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

[0046] The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR studies have identified the operating bands used for these mid-band frequencies as the frequency range designation FR3 (7.125 GHz to 24.25 GHz). Bands falling within FR3 can inherit FR1 and / or FR2 characteristics, thus effectively extending the features of FR1 and / or FR2 to mid-band frequencies. Furthermore, higher frequency bands are currently being explored to extend 5G NR operation beyond 52.6 GHz. For example, three higher operating bands have been identified as the frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

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

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

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

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

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

[0052] Refer again Figure 1 In some aspects, UE 104 may include a PDSCH component 198. In some aspects, the PDSCH component 198 may be configured to receive from a network node a first-level DCI associated with a second-level DCI, wherein the first-level DCI includes information about a set of time and frequency resources associated with the PDSCH, and wherein the second-level DCI includes decoding information associated with the PDSCH. In some aspects, the PDSCH component 198 may also be configured to receive transmissions including the second-level DCI and the PDSCH from a network node based on information about the time and frequency resource sets, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time. In some aspects, the PDSCH component 198 may also be configured to decode the PDSCH based on the second-level DCI.

[0053] In some aspects, base station 102 may include PDSCH component 199. In some aspects, PDSCH component 199 may be configured to transmit a first-level DCI associated with a second-level DCI to a UE, wherein the first-level DCI includes information about a time and frequency resource set associated with the PDSCH, and wherein the second-level DCI includes decoding information associated with the PDSCH. In some aspects, PDSCH component 199 may also be configured to transmit a transmission including a second-level DCI and PDSCH to a UE based on information about the time and frequency resource set, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time.

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

[0055] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be included in, or may be a component of: a base station (e.g., any base station described herein), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote / radio unit (RU) (which may also be referred to as a remote radio unit (RRU)), and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. As yet another example, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In still other aspects of this example, the first network node, the second network node, and the third network node may be different from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first set of one or more components, or a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second set of one or more components, or a second processing entity, etc.

[0056] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

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

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

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

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

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

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

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

[0064] Figure 2D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), pre-decoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUCCH carries data and may additionally be used to carry buffer status reports (BSR), power clearance reports (PHR), and / or UCIs.

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

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

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

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

[0069] Similar to the functionality described in conjunction with DL transmission performed by base station 310, controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connectivity, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with upper-layer PDU delivery, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel priority ordering.

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

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

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

[0073] At least one of the TX processor 368, RX processor 356, and controller / processor 359 can be configured to combine Figure 1 The PDSCH component 198 is used to perform various aspects.

[0074] At least one of the TX processor 316, RX processor 370, and controller / processor 375 can be configured to combine Figure 1 The PDSCH component 199 is used to perform various aspects.

[0075] In some wireless communication systems, a two-level DCI can be used, with the first and second levels jointly providing complete scheduling information for the data channel. The first-level DCI may include demodulation-related parameters such as MIMO-related information, antenna information, modulation order, resource allocation, demodulation reference signal (DMRS) configuration, and resource locations for the second-level DCI, enabling the UE to capture digital samples, perform channel estimation, and equalization. The second-level DCI may include decoding-related information for the data channel (PDSCH), such as HARQ process ID, redundancy version identifier (RVID), new data indicator (NDI), code rate, modulation and decoding scheme (MCS), power control information, and beam information, enabling the UE to decode (e.g., in the data channel) the information content and perform HARQ combining. The UE can blindly detect and decode the first-level DCI (e.g., similar to single-level DCI detection). After the first-level DCI is decoded, the UE can use a small amount of additional UE processing to decode the second-level DCI. For the transmission of the second-level DCI, the second-level DCI can be (1) carried in the scheduled PDSCH, or (2) transmitted in a configured search space (SS). Some wireless communication systems support PDSCH rate matching around the scheduled DCI. In some aspects provided herein, the PDSCH can be rate matched around the second-level DCI. For example, in order to rate match the PDSCH around the second-level DCI, network nodes can encode the PDSCH based on a rate matching pattern and avoid conflicts between the second-level DCI and the PDSCH (e.g., transmission in the same time and frequency resources).

[0076] Level 2 DCI can overlap with PDSCH in both time-domain and frequency-domain resources. Interleaved CCE-to-Resource Element Group (REG) mapping can be used for Level 2 DCI, providing better frequency diversity than contiguous resource mapping. In some aspects, independent SS sets can exist for Level 2 DCI, which can be specified as an aggregation level (which can be the number of CCEs allocated for Level 2 DCI), and the DCI format can be provided in the SS set configuration associated with the SS set. Multiplexing Level 2 DCI and scheduled PDSCH in the same physical resources can be beneficial, allowing Level 2 DCI and PDSCH to be transmitted in the same narrow beam. Multiplexing Level 2 DCI and scheduled PDSCH in the same physical resources allows for easier resource management for multi-UE scheduling by allocating the second DCI and PDSCH of the same UE in the same symbols and RB segments without gaps between them.

[0077] For the uplink, once the UE receives the first-level DCI (e.g., with less information than a single-level DCI), the UE can begin preparing UL data so that data can be transmitted immediately after the second-level DCI is decoded. In some respects, the DCI size can be aligned between different first-level DCI formats (e.g., the same or with a specified increment), making blind detection less demanding.

[0078] Figure 4 This is an example diagram 400 illustrating a two-level DCI. For example... Figure 4 As illustrated, the first-level DCI 402 may include demodulation-related parameters, such as MIMO-related information, antenna information, modulation order, resource allocation, DMRS configuration, and resource locations for the second-level DCI, to enable the UE to capture digital samples, perform channel estimation, and equalization.

[0079] The second-level DCI 404 can be associated with the first-level DCI 402 and may include decoding-related information for the data channel (e.g., PDSCH 406), such as HARQ process ID, RVID, NDI, code rate, MCS, power control information, beam information, etc., for the UE to decode (e.g., in the data channel) the information content and perform HARQ combining. In the uplink channel, a HARQ report 408 may exist. Figure 4 As illustrated, the network can schedule resources before the HARQ-ACK (e.g., in HARQ report 408) for past PDSCHs (e.g., received before the first-level DCI 402), allowing the UE to begin RS processing and channel estimation before the second-level DCI 404 is decoded.

[0080] Figure 5This is an example diagram 500 illustrating a two-level DCI, where a single first-level DCI is associated with multiple second-level DCIs. A single first-level DCI can provide common scheduling information for multiple transmissions, and each second-level DCI can provide link-adaptive scheduling information for different transmissions. For example... Figure 5 As illustrated, the first-level DCI 502 may include demodulation-related parameters, such as MIMO-related information, antenna information, modulation order, resource allocation, DMRS configuration, and resource locations for the second-level DCI, to enable the UE to capture digital samples, perform channel estimation, and equalization.

[0081] An initial second-level DCI 504A may be associated with a first-level DCI 502 and may include decoding-related information for the data channel (e.g., PDSCH 506A), such as HARQ process ID, RVID, NDI, code rate, MCS, power control information, beam information, etc., for the UE to decode (e.g., in the data channel) the information content and perform HARQ combination. A subsequent second-level DCI 504B may be associated with a first-level DCI 502 and may include decoding-related information for the data channel (e.g., PDSCH 506B), such as HARQ process ID, RVID, NDI, code rate, MCS, power control information, beam information, etc., for the UE to decode (e.g., in the data channel) the information content and perform HARQ combination. Because multiple second-level DCIs can share a first-level DCI, information in the shared first-level DCI can be transmitted once instead of multiple times, potentially reducing the signaling overhead of the control channel.

[0082] Figure 6 The diagram 600 illustrates an example of a two-stage DCI, where the first-stage DCI is transmitted based on a first beam, and the associated second-stage DCI is transmitted based on a second beam different from the first beam. The first beam may be a wider beam than the second beam to allow the second-stage DCI to be transmitted more spectrally efficient (e.g., in a narrower beam) while maintaining the easier detectability of the first-stage DCI.

[0083] like Figure 6 As illustrated, the first-level DCI 602 may include demodulation-related parameters such as MIMO-related information, antenna information, modulation order, resource allocation, DMRS configuration, and resource locations for the second-level DCI, so that the UE can capture digital samples, perform channel estimation, and equalization.

[0084] The second-level DCI 604 may be associated with the first-level DCI 602 and may include decoding-related information for the data channel (e.g., PDSCH 606), such as HARQ process ID, RVID, NDI, code rate, MCS, power control information, beam information, etc., for the UE to decode (e.g., in the data channel) information content and perform HARQ combining.

[0085] Figure 7A This is an example diagram 700 illustrating a two-level DCI, where the first-level DCI is associated with the second-level DCI, and the PDSCH performs rate matching around the second-level DCI. For example... Figure 7A As illustrated, the first-level DCI 702 may include demodulation-related parameters, such as MIMO-related information, antenna information, modulation order, resource allocation, DMRS configuration, and resource locations for the second-level DCI, for the UE to capture digital samples, perform channel estimation, and equalization, etc. The PDSCH 706 may perform rate matching around the first portion 704A and the second portion 704B of the second-level DCI. The second-level DCI may be configured using an interleaved CCE-to-REG mapping (the mapping type may be included in the control resource set associated with the search space set) for the search space set in which the DCI is configured. In some aspects, the first-level DCI 702 allocates resources for the PDSCH 706. The timing of the search space set for the second-level DCI (PDCCH monitoring timing) may completely overlap with the resources used for the PDSCH 706. After mapping the second-level DCI (e.g., the first portion 704A and the second portion 704B of the second-level DCI), the PDSCH 706 may be populated with the remaining resources. In some respects, the interleaved CCE-to-REG mapping is configurable, and the second-level DCI can be distributed across discontinuous resources (e.g., in the first part 704A of the second-level DCI and the second part 704B of the second-level DCI). In some respects, the second-level DCI and PDSCH 706 can be transmitted with the same power and the same beam.

[0086] In some respects, if the UE supports rate matching around a single-level DCI, and if the first-level DCI also overlaps with the scheduled PDSCH, then both the first-level DCI and the second-level DCI can be rate matched around the scheduled PDSCH. Figure 7B This is an example diagram 750 illustrating a two-level DCI, where the first-level DCI is associated with the second-level DCI, and the PDSCH performs rate matching around the second-level DCI and the first-level DCI.

[0087] like Figure 7BAs illustrated, the first-level DCI 752 may include demodulation-related parameters, such as MIMO-related information, antenna information, modulation order, resource allocation, DMRS configuration, and resource locations for the second-level DCI, to enable the UE to capture digital samples, perform channel estimation, and equalization. The PDSCH 756 may perform rate matching around the first portion 754A of the second-level DCI, the second portion 754B of the second-level DCI, and the first-level DCI 752.

[0088] In some aspects, the search space set timing (PDCCH monitoring timing) for the second-level DCI and the first-level DCI may overlap with the resources used for PDSCH 756. After mapping the second-level DCI (e.g., the first portion 754A of the second-level DCI and the second portion 754B of the second-level DCI) and the first-level DCI 752, PDSCH 756 can be populated in the remaining resources. In some aspects, interleaved CCE-to-REG mapping can be configured, and the second-level DCI can be distributed across discontinuous resources (e.g., in the first portion 754A of the second-level DCI and the second portion 754B of the second-level DCI). In some aspects, the second-level DCI, the first-level DCI 752, and PDSCH 756 can be transmitted using the same power and the same beam.

[0089] Figure 8 This is diagram 800 illustrating example communication between network node 804 and UE 802. (See diagram 800 for example.) Figure 8 As illustrated, network node 804 may send a control resource set (CORESET) configuration 806A and an SS set configuration 806B to UE 802. Network node 804 may also send a first-level DCI 808 to UE 802. The first-level DCI 808 may include demodulation-related parameters, such as MIMO-related information, antenna information, modulation order, resource allocation, DMRS configuration, and resource locations for the second-level DCI, for the UE to capture digital samples, perform channel estimation, and equalization. Network node 804 may also send a second-level DCI 810, which may be associated with the first-level DCI 808, and may include decoding-related information for the data channel (e.g., PDSCH 812), such as HARQ process ID, RVID, NDI, code rate, MCS, power control information, beam information, etc., for UE 802 to decode (e.g., in the data channel) information content and perform HARQ combining. In some respects, the PDSCH 812 can be rate-matched around the second-level DCI 810 (e.g., as... Figure 7A (As illustrated). In some respects, the PDSCH 812 can be rate-matched around the second-level DCI 810 and the first-level DCI 808 (e.g., as shown). Figure 7B exemplified).

[0090] In some respects, the frequency domain resource allocation for the second-level DCI 810 is compatible with the frequency domain resource allocation (FDRA) for the PDSCH 812. In some respects, for compatibility, the second-level DCI 810 may be fully contained by the scheduled FDRA of the PDSCH 812.

[0091] In some aspects, the range of frequency domain resources for the second-level DCI 810 can be determined by the explicit configuration in the CORESET for the second-level DCI 810 (e.g., in 806A). For example, the frequency domain resources for the CORESET can be indicated by a bitmap, with each bit indicating whether a set of a number (e.g., six) of consecutive RBs can be used. In some aspects, the configuration (e.g., in 806A) can be compatible with the frequency domain resource allocation for the PDSCH used for scheduling by being the same as or within the PDSCH frequency resources. In some aspects, the range of frequency domain resources for the second-level DCI 810 can be determined by the frequency domain resources for the PDSCH 812. In some aspects, the frequency domain resources allocated to the PDSCH 812 (e.g., the starting RB and size of each segment of consecutive RBs in the FDRA) can be further quantized with a certain number (e.g., six) of RB granularities.

[0092] In some aspects, the time-domain resource allocation for the second-level DCI 810 may also be compatible with PDSCH 812. For example, in some aspects, the symbols for the second-level DCI 810 may be included by the time-domain resource allocation (TDRA) of the scheduled PDSCH 812. In some aspects, the time-domain resources for the second-level DCI 810 are determined by the explicit configuration of the search space set (e.g., 806B) for the second-level DCI (e.g., 810). In some aspects, the search space timing for the second-level DCI may or may not be aligned with the scheduled PDSCH (e.g., one and only one search space timing is fully included by the symbols allocated for the scheduled PDSCH). In some aspects, a first search space set timing fully included by the symbols for PDSCH 812 may be used for the second-level DCI 810.

[0093] In some aspects, the time-domain resources used for the second-level DCI 810 are determined by the configuration symbols of the PDSCH 812. In some aspects, the search space configuration for the second-level DCI 810 (e.g., 806B) can provide a certain number of symbols, and the start of the search space set timing can be aligned with the starting symbol of the PDSCH (e.g., or a different symbol). For example, the floating start of the second-level DCI search space timing, the number of symbols used for the second-level DCI, can be the minimum of the number of symbols configured for the second-level DCI 810 or the number of symbols used for the PDSCH 812.

[0094] In some respects, Level 2 DCI 810 is multiplexed with PDSCH 812. In some respects, if some of the allocated PDSCH resources belong to PDSCH rate-matching resources that include SSB, RB symbol-level rate-matching resources, and RE-level rate-matching resources (such as CSI-RS or other RS), then these resources cannot be used for PDSCH transmission. In some respects, if a PDCCH candidate overlaps with a PDSCH rate-matching resource, network node 804 may not use the PDCCH candidate for Level 2 DCI transmission (e.g., if any part of the entire PDCCH candidate belongs to a PDSCH rate-matching resource, then the entire PDCCH candidate may be skipped). As used herein, the term "PDSCH rate-matching resource" may refer to SSB, RB symbol-level rate-matching resources, and RE-level rate-matching resources (such as CSI-RS or another RS).

[0095] In some respects, if the monitoring timing of the second-level DCI 810 overlaps with the resources allocated for PDSCH, the second-level DCI 810 will not transmit in any PDCCH candidate that overlaps with the rate-matching resources used for PDSCH 812 (other than the second-level DCI itself being a rate-matching resource).

[0096] In some aspects, to map second-level DCI PDCCH candidates to resources, PDSCH rate-matching resources may be removed first. In some aspects, if the monitoring timing of second-level DCI 810 overlaps with the resources allocated for PDSCH, network node 804 may remove resources belonging to PDSCH rate-matching resources and then map the second-level DCI 810's PDCCH candidates to the remaining resources. In some aspects, the remaining resources (including the starting RB and size of each segment of consecutive RBs) may be further quantized at a specific RB granularity (e.g., six).

[0097] In some aspects, at 814, UE 802 can decode PDSCH 812 based on Level 2 DCI 810. In some aspects, if Level 2 DCI 810 is transmitted on a fixed PDCCH candidate during Level 2 DCI monitoring, PDCCH decoding effort can be minimized for Level 2 DCI 810. In some aspects, the entire resource block used by Level 2 DCI 810 and PDSCH 812 can be considered as both being user data, and there may be no further randomization of resource allocation for Level 2 DCI beyond the interleaved CCE-to-REG mapping and slot-dependent CCE offset configured for CORESET. In some aspects, if multiple PDCCH candidates per aggregation level are configured in the Level 2 DCI search space set (e.g., configured by 806A), Level 2 DCI 810 is transmitted in the first PDCCH candidate available for Level 2 DCI transmission. In some respects, PDCCH candidates that conflict with PDSCH rate matching resources may not be available for Level 2 DCI transmission (excluding additional conditions that prevent Level 2 DCI transmission on certain PDCCH candidates). Network node 804 can be configured with multiple PDCCH candidates (even if no more than one PDCCH candidate is used) such that at least one of the PDCCH candidates does not conflict with PDSCH rate matching resources.

[0098] Figure 9 This is a flowchart 900 of a wireless communication method. The method can be performed by a UE (e.g., UE 104, UE 802; device 1104).

[0099] At 902, the UE may receive from a network node a first-level DCI associated with a second-level DCI, wherein the first-level DCI includes information about the time and frequency resource set associated with the PDSCH, and wherein the second-level DCI includes decoding information associated with the PDSCH. For example, UE 802 may receive from network node 804 a first-level DCI 808 associated with a second-level DCI 810, wherein the first-level DCI includes information about the time and frequency resource set associated with the PDSCH 812, and wherein the second-level DCI includes decoding information associated with the PDSCH 812. In some aspects, 902 may be performed by the PDSCH component 198.

[0100] At 904, the UE may receive transmissions including a second-level DCI and PDSCH from the network node based on information about the time and frequency resource set (e.g., included in the first-level DCI), wherein the second-level DCI is multiplexed with the PDSCH and wherein the second-level DCI overlaps with the PDSCH in time. For example, UE 802 may receive transmissions including a second-level DCI 810 and PDSCH 812 from network node 804 based on information about the time and frequency resource set, wherein the second-level DCI is multiplexed with the PDSCH and wherein the second-level DCI overlaps with the PDSCH in time (e.g., partially overlaps in time). In some aspects, 904 may be performed by the PDSCH component 198.

[0101] At 906, the UE can decode the PDSCH based on the Level 2 DCI. For example, at 814, UE 802 can decode the PDSCH based on the Level 2 DCI. In some respects, 906 can be performed by the PDSCH component 198.

[0102] Figure 10 This is a flowchart 1000 of a wireless communication method. The method can be performed by network nodes (e.g., base station 102, network node 804, network entity 1102, network entity 1202).

[0103] At 1002, a network node may transmit to the UE a first-level DCI associated with a second-level DCI, wherein the first-level DCI includes information about the time and frequency resource set associated with the PDSCH, and wherein the second-level DCI includes decoding information associated with the PDSCH. For example, network node 804 may transmit to the UE 802 a first-level DCI 808 associated with a second-level DCI 810, wherein the first-level DCI 808 includes information about the time and frequency resource set associated with the PDSCH 812, and wherein the second-level DCI 810 includes decoding information associated with the PDSCH 812. In some aspects, 1002 may be performed by the PDSCH component 199.

[0104] At 1004, the network node may transmit a transmission including a second-level DCI and PDSCH for UE 802 based on information about the time and frequency resource set (e.g., included in the first-level DCI), wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time. For example, network node 804 may transmit a transmission including a second-level DCI 810 and PDSCH 812 for UE 802 based on information about the time and frequency resource set, wherein the second-level DCI 810 is multiplexed with the PDSCH 812, and wherein the second-level DCI overlaps with the PDSCH in time (e.g., partially overlaps in time). In some aspects, 1004 may be performed by PDSCH component 199.

[0105] Figure 11Figure 1100 illustrates an example of a hardware implementation for device 1104. Device 1104 may be a UE, a component of a UE, or implement UE functionality. In some aspects, device 1104 may include at least one cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., cellular RF transceivers). Cellular baseband processor 1124 may include at least one on-chip memory 1124'. In some aspects, device 1104 may also include one or more Subscriber Identity Module (SIM) cards 1120 and at least one application processor 1106 coupled to a Secure Digital Card (SD) card 1108 and a screen 1110. Application processor 1106 may include on-chip memory 1106'. In some aspects, device 1104 may also include a Bluetooth module 1112, a WLAN module 1114, an SPS module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (e.g., a barometric pressure sensor / altimeter; motion sensors such as an inertial measurement unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-assisted detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1126, a power supply 1130, and / or a camera 1132. Bluetooth module 1112, WLAN module 1114, and SPS module 1116 may include on-chip transceivers (TRX) (or in some cases, only receivers (RX)). Bluetooth module 1112, WLAN module 1114, and SPS module 1116 may include their own dedicated antennas and / or communicate using antenna 1180. Cellular baseband processor 1124 communicates with UE 104 and / or RU associated with network entity 1102 via transceiver 1122 through one or more antennas 1180. Cellular baseband processor 1124 and application processor 1106 may each include computer-readable media / memory 1124', 1106'. Additional memory module 1126 may also be considered computer-readable media / memory. Each computer-readable media / memory 1124', 1106', 1126 may be non-transitory. Cellular baseband processor 1124 and application processor 1106 are each responsible for general processing, including executing software stored on the computer-readable media / memory. When executed by cellular baseband processor 1124 / application processor 1106, the software causes cellular baseband processor 1124 / application processor 1106 to perform the various functions described above. The computer-readable media / memory can also be used to store data manipulated by cellular baseband processor 1124 / application processor 1106 during software execution.Cellular baseband processor 1124 / application processor 1106 may be a component of UE 350 and may include at least one of memory 360 and / or TX processor 368, RX processor 356 and controller / processor 359. In one configuration, device 1104 may be at least one processor chip (modem and / or application) and may only include cellular baseband processor 1124 and / or application processor 1106, while in another configuration, device 1104 may be the entire UE (e.g., see below). Figure 3 The UE 350 includes an additional module of the device 1104.

[0106] As discussed above, PDSCH component 198 can be configured to receive from a network node a first-level DCI associated with a second-level DCI, wherein the first-level DCI includes information about the time and frequency resource set associated with the PDSCH, and wherein the second-level DCI includes decoding information associated with the PDSCH. In some aspects, PDSCH component 198 can also be configured to receive transmissions including the second-level DCI and PDSCH from a network node based on information about the time and frequency resource set, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time. In some aspects, PDSCH component 198 can also be configured to decode the PDSCH based on the second-level DCI. PDSCH component 198 may reside within cellular baseband processor 1124, application processor 1106, or both cellular baseband processor 1124 and application processor 1106. Component 198 may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, and stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated process / algorithm individually or in combination. As shown, device 1104 may include a variety of components configured for various functions. In one configuration, device 1104, and specifically cellular baseband processor 1124 and / or application processor 1106, may include components for receiving first-level DCI associated with second-level DCI from a network node, wherein the first-level DCI includes information about time and frequency resource sets associated with PDSCH, and wherein the second-level DCI includes decoding information associated with PDSCH. In some aspects, apparatus 1104 may include components for receiving transmissions including a second-level DCI and a PDSCH from a network node based on information about time and frequency resource sets, wherein the second-level DCI is multiplexed with the PDSCH and wherein the second-level DCI overlaps with the PDSCH in time. In some aspects, apparatus 1104 may include components for decoding the PDSCH based on the second-level DCI. The components may be components 198 of apparatus 1104 configured to perform functions described therein. As described above, apparatus 1104 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, these components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform functions described therein.

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

[0108] As discussed above, PDSCH component 199 can be configured to transmit a first-level DCI associated with a second-level DCI to a UE, wherein the first-level DCI includes information about the time and frequency resource set associated with the PDSCH, and wherein the second-level DCI includes decoding information associated with the PDSCH. In some aspects, PDSCH component 199 can also be configured to transmit a transmission including a second-level DCI and PDSCH to a UE based on information about the time and frequency resource set, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time. PDSCH component 199 can be located in one or more processors of one or more of CU 1210, DU 1230, and RU 1240. Component 199 can be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors configured to execute the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may execute the stated procedures / algorithms individually or in combination. Network entity 1202 may include various components configured for various functions. In one configuration, network entity 1202 may include components for transmitting a first-level DCI associated with a second-level DCI to a UE, wherein the first-level DCI includes information about a time and frequency resource set associated with a PDSCH, and wherein the second-level DCI includes decoding information associated with the PDSCH. In some aspects, network entity 1202 may include components for transmitting a transmission including a second-level DCI and a PDSCH to a UE based on information about the time and frequency resource set, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time. The component may be component 199 of network entity 1202 configured to perform the functions described therein. As described above, network entity 1202 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Therefore, in one configuration, these components may be configured to perform the functions described therein as TX processor 316, RX processor 370 and / or controller / processor 375.

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

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

[0111] As used in this article, the phrase “based on” should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) should be interpreted as “based on at least A”, unless specifically stated differently.

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

[0113] Aspect 1 is a method of wireless communication performed by a user equipment (UE), the method comprising: receiving from a network node a first-level DCI associated with second-level downlink control information (DCI), wherein the first-level DCI includes information about a set of time and frequency resources associated with a physical downlink shared channel (PDSCH), and wherein the second-level DCI includes decoding information associated with the PDSCH; receiving from the network node, based on the information about the time and frequency resource sets, a transmission including the second-level DCI and the PDSCH, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time; and decoding the PDSCH based on the second-level DCI.

[0114] Aspect 2 is the method according to aspect 1, wherein rate matching is performed around the second-level DCI based on the PDSCH, and the second-level DCI is multiplexed with the PDSCH.

[0115] Aspect 3 is the method according to any one of Aspects 1 to 2, wherein the second-level DCI is associated with a search space (SS) set, the search space (SS) set is associated with an interleaved control channel element (CCE) to resource element group (REG) mapping, and wherein the second-level DCI is carried in a non-contiguous resource set.

[0116] Aspect 4 is the method according to any one of Aspects 1 to 3, wherein the first-level DCI overlaps with the PDSCH, and wherein the PDSCH is rate-matched around the first-level DCI.

[0117] Aspect 5 is the method according to any one of Aspects 1 to 4, wherein the range of frequency domain resources for the second-level DCI is based on the configuration of the control resource set (CORESET) for the second-level DCI.

[0118] Aspect 6 is the method according to any one of Aspect 5, wherein the configuration in the CORESET for the second-level DCI includes a bitmap that indicates the resource block (RB) set as the range of the frequency domain resources for the second-level DCI.

[0119] Aspect 7 is the method according to any one of aspects 1 to 6, wherein the range of frequency domain resources for the second-level DCI is based on the set of frequency domain resources for the PDSCH.

[0120] Aspect 8 is a method according to any one of aspects 1 to 7, wherein the temporal resource set for the second-level DCI is based on a configuration associated with a search space (SS) set for the second-level DCI, and wherein the configuration indicates the temporal resource set.

[0121] Aspect 9 is the method according to any one of Aspects 1 to 8, wherein a first time-domain resource set for the second-level DCI is based on a second time-domain resource set for the PDSCH, and wherein the first time-domain resource set and the second time-domain resource set overlap in time.

[0122] Aspect 10 is the method according to any one of Aspect 9, wherein the first time-domain resource set and the second time-domain resource set share the same start symbol.

[0123] Aspect 11 is the method according to any one of aspects 1 to 10, wherein the monitoring timing associated with the second-level DCI overlaps with the resource set used for the PDSCH, and wherein the second-level DCI is not carried in resources that overlap with one or more rate-matching resources used for the PDSCH.

[0124] Aspect 12 is the method according to any one of Aspects 1 to 11, wherein the monitoring timing associated with the second-level DCI overlaps with the resource set for the PDSCH, and wherein one or more rate-matching resources for the PDSCH are removed for the second-level DCI.

[0125] Aspect 13 is a method according to any one of Aspects 1 to 12, the method further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to receive the first level DCI, the at least one processor is configured individually or in combination to receive the first level DCI via at least one of the transceiver or the antenna, and wherein the second level DCI is carried in a first PDCCH candidate resource in a set of physical downlink control channel (PDCCH) candidate resources available for the second level DCI.

[0126] Aspect 14 is a method of wireless communication performed by a network node, the method comprising: transmitting to a user equipment (UE) a first-level DCI associated with second-level downlink control information (DCI), wherein the first-level DCI includes information about a set of time and frequency resources associated with a physical downlink shared channel (PDSCH), and wherein the second-level DCI includes decoding information associated with the PDSCH; and transmitting to the UE, including the second-level DCI and the PDSCH, based on the information about the time and frequency resource sets, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time.

[0127] Aspect 15 is the method according to aspect 14, wherein rate matching is performed around the second-level DCI based on the PDSCH, and the second-level DCI is multiplexed with the PDSCH.

[0128] Aspect 16 is the method according to aspect 15, wherein the second-level DCI is associated with a search space (SS) set, the search space (SS) set is associated with an interleaved control channel element (CCE) to resource element group (REG) mapping, and wherein the second-level DCI is carried in a non-contiguous resource set.

[0129] Aspect 17 is the method according to any one of aspects 15 to 16, wherein the first-level DCI overlaps with the PDSCH, and wherein the PDSCH is rate-matched around the first-level DCI.

[0130] Aspect 18 is the method according to any one of aspects 14 to 17, wherein the range of frequency domain resources for the second-level DCI is based on the configuration of the control resource set (CORESET) for the second-level DCI.

[0131] Aspect 19 is the method according to aspect 18, wherein the configuration in the CORESET for the second level DCI includes a bitmap that indicates the resource block (RB) set as the range of the frequency domain resources for the second level DCI.

[0132] Aspect 20 is the method according to any one of aspects 14 to 19, wherein the range of frequency domain resources for the second-level DCI is based on the set of frequency domain resources for the PDSCH.

[0133] Aspect 21 is the method according to any one of aspects 14 to 22, wherein the temporal resource set for the second-level DCI is based on a configuration associated with a search space (SS) set for the second-level DCI, and wherein the configuration indicates the temporal resource set.

[0134] Aspect 22 is a method according to any one of aspects 14 to 21, wherein a first time-domain resource set for the second-level DCI is based on a second time-domain resource set for the PDSCH, and wherein the first time-domain resource set and the second time-domain resource set overlap in time.

[0135] Aspect 23 is the method according to any one of Aspect 22, wherein the first time-domain resource set and the second time-domain resource set share the same start symbol.

[0136] Aspect 24 is the method according to any one of aspects 14 to 23, wherein the monitoring timing associated with the second-level DCI overlaps with the resource set used for the PDSCH, and wherein the second-level DCI is not carried in resources that overlap with one or more rate-matching resources used for the PDSCH.

[0137] Aspect 25 is the method according to any one of aspects 14 to 24, wherein the monitoring timing associated with the second-level DCI overlaps with the resource set for the PDSCH, and wherein one or more rate-matching resources for the PDSCH are removed for the second-level DCI.

[0138] Aspect 26 is the method of any one of aspects 14 to 25, the method further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to transmit the first level DCI, the at least one processor is configured individually or in combination to transmit the first level DCI via at least one of the transceiver or the antenna, and wherein the second level DCI is carried in a first PDCCH candidate resource in a set of physical downlink control channel (PDCCH) candidate resources available for the second level DCI.

[0139] Aspect 27 is an apparatus for wireless communication at a UE, the apparatus comprising at least one memory and at least one processor coupled to said at least one memory, and based at least in part on information stored in said at least one memory, said at least one processor being configured individually or in combination to implement any one of aspects 1 to 13.

[0140] Aspect 28 is the apparatus according to aspect 27, the apparatus further comprising one or more transceivers or one or more antennas coupled to the at least one processor.

[0141] Aspect 29 is an apparatus for wireless communication at a UE, the apparatus including components for implementing any one of aspects 1 to 13.

[0142] Aspect 30 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any one of aspects 1 to 13.

[0143] Aspect 31 is an apparatus for wireless communication at a network node, the apparatus comprising at least one memory and at least one processor coupled to said at least one memory, and based at least in part on information stored in said at least one memory, said at least one processor being configured individually or in combination to implement any one of aspects 14 to 26.

[0144] Aspect 32 is the apparatus according to aspect 31, the apparatus further comprising one or more transceivers or one or more antennas coupled to the at least one processor.

[0145] Aspect 33 is an apparatus for wireless communication at a network node, the apparatus comprising: components for implementing any one of aspects 14 to 26.

[0146] Aspect 34 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer-executable code, wherein the code, when executed by at least one processor, causes the at least one processor to implement any one of aspects 14 to 26.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to cause the UE to: Receive a first-level DCI associated with a second-level downlink control information (DCI) from a network node, wherein the first-level DCI includes information about a set of time and frequency resources associated with a physical downlink shared channel (PDSCH), and wherein the second-level DCI includes decoding information associated with the PDSCH. Based on the information regarding the time and frequency resource set, the network node receives transmissions including the second-level DCI and the PDSCH, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time; and The PDSCH is decoded based on the second-level DCI.

2. The apparatus of claim 1, wherein rate matching is performed around the second-level DCI based on the PDSCH, and the second-level DCI is multiplexed with the PDSCH.

3. The apparatus of claim 2, wherein the second-level DCI is associated with a search space (SS) set, the search space (SS) set is associated with an interleaved control channel element (CCE) to resource element group (REG) mapping, and wherein the second-level DCI is carried in a non-contiguous resource set.

4. The apparatus of claim 2, wherein the first-level DCI overlaps with the PDSCH, and wherein the PDSCH is rate-matched around the first-level DCI.

5. The apparatus of claim 1, wherein the range of frequency domain resources for the second-level DCI is based on the configuration of the control resource set (CORESET) for the second-level DCI.

6. The apparatus of claim 5, wherein the configuration in the CORESET for the second-level DCI includes a bitmap that indicates the resource block (RB) set as the range of the frequency domain resources for the second-level DCI.

7. The apparatus of claim 1, wherein the range of frequency domain resources for the second-level DCI is based on the set of frequency domain resources for the PDSCH.

8. The apparatus of claim 1, wherein the temporal resource set for the second-level DCI is based on a configuration associated with a search space (SS) set for the second-level DCI, and wherein the configuration indicates the temporal resource set.

9. The apparatus of claim 1, wherein the first time-domain resource set for the second-level DCI is based on the second time-domain resource set for the PDSCH, and wherein the first time-domain resource set and the second time-domain resource set overlap in time.

10. The apparatus of claim 9, wherein the first time-domain resource set and the second time-domain resource set share the same start symbol.

11. The apparatus of claim 1, wherein the monitoring timing associated with the second-level DCI overlaps with the resource set used for the PDSCH, and wherein the second-level DCI is not carried in resources that overlap with one or more rate-matching resources used for the PDSCH.

12. The apparatus of claim 1, wherein the monitoring timing associated with the second-level DCI overlaps with the resource set for the PDSCH, and wherein one or more rate-matching resources for the PDSCH are removed for the second-level DCI.

13. The apparatus of claim 1, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to receive the first-level DCI, the at least one processor is configured individually or in combination to receive the first-level DCI via at least one of the transceiver or the antenna, and wherein the second-level DCI is carried in a first PDCCH candidate resource in a set of physical downlink control channel (PDCCH) candidate resources available for the second-level DCI.

14. An apparatus for wireless communication at a network node, the apparatus comprising: At least one memory; and At least one processor, coupled to at least one memory, and configured individually or in any combination, based at least in part on information stored in the at least one memory, to enable the network node to: For a User Equipment (UE), a first-level DCI associated with second-level downlink control information (DCI) is transmitted, wherein the first-level DCI includes information about a set of time and frequency resources associated with a Physical Downlink Shared Channel (PDSCH), and wherein the second-level DCI includes decoding information associated with the PDSCH; and Based on the information about the time and frequency resource set, a transmission including the second-level DCI and the PDSCH is transmitted for the UE, wherein the second-level DCI is multiplexed with the PDSCH and wherein the second-level DCI overlaps with the PDSCH in time.

15. The apparatus of claim 14, wherein rate matching is performed around the second-level DCI based on the PDSCH, and the second-level DCI is multiplexed with the PDSCH.

16. The apparatus of claim 15, wherein the second-level DCI is associated with a search space (SS) set, the search space (SS) set being associated with an interleaved control channel element (CCE) to resource element group (REG) mapping, and wherein the second-level DCI is carried in a non-contiguous resource set.

17. The apparatus of claim 15, wherein the first-level DCI overlaps with the PDSCH, and wherein the PDSCH is rate-matched around the first-level DCI.

18. The apparatus of claim 14, wherein the range of frequency domain resources for the second-level DCI is based on the configuration of the control resource set (CORESET) for the second-level DCI.

19. The apparatus of claim 18, wherein the configuration in the CORESET for the second-level DCI includes a bitmap that indicates a set of resource blocks (RBs) as the range of the frequency domain resources for the second-level DCI.

20. The apparatus of claim 14, wherein the range of frequency domain resources for the second-level DCI is based on the set of frequency domain resources for the PDSCH.

21. The apparatus of claim 14, wherein the temporal resource set for the second-level DCI is based on a configuration associated with a search space (SS) set for the second-level DCI, and wherein the configuration indicates the temporal resource set.

22. The apparatus of claim 14, wherein the first time-domain resource set for the second-level DCI is based on the second time-domain resource set for the PDSCH, and wherein the first time-domain resource set and the second time-domain resource set overlap in time.

23. The apparatus of claim 22, wherein the first time-domain resource set and the second time-domain resource set share the same start symbol.

24. The apparatus of claim 14, wherein the monitoring timing associated with the second-level DCI overlaps with the resource set used for the PDSCH, and wherein the second-level DCI is not carried in resources that overlap with one or more rate-matching resources used for the PDSCH.

25. The apparatus of claim 14, wherein the monitoring timing associated with the second-level DCI overlaps with the resource set for the PDSCH, and wherein one or more rate-matching resources for the PDSCH are removed for the second-level DCI.

26. The apparatus of claim 14, further comprising at least one of a transceiver or an antenna coupled to the at least one processor, wherein, in order to transmit the first-level DCI, the at least one processor is configured individually or in combination to transmit the first-level DCI via at least one of the transceiver or the antenna, and wherein the second-level DCI is carried in a first PDCCH candidate resource in a set of physical downlink control channel (PDCCH) candidate resources available for the second-level DCI.

27. A method for wireless communication performed by a user equipment (UE), the method comprising: Receive a first-level DCI associated with a second-level downlink control information (DCI) from a network node, wherein the first-level DCI includes information about a set of time and frequency resources associated with a physical downlink shared channel (PDSCH), and wherein the second-level DCI includes decoding information associated with the PDSCH. Based on the information regarding the time and frequency resource set, the network node receives transmissions including the second-level DCI and the PDSCH, wherein the second-level DCI is multiplexed with the PDSCH, and wherein the second-level DCI overlaps with the PDSCH in time; and The PDSCH is decoded based on the second-level DCI.

28. The method of claim 27, wherein rate matching is performed around the second-level DCI based on the PDSCH, and the second-level DCI is multiplexed with the PDSCH.

29. The method of claim 28, wherein the second-level DCI is associated with a search space (SS) set, the search space (SS) set being associated with an interleaved control channel element (CCE) to resource element group (REG) mapping, and wherein the second-level DCI is carried in a non-contiguous resource set.

30. A method for wireless communication performed by a network node, the method comprising: For a User Equipment (UE), a first-level DCI associated with second-level downlink control information (DCI) is transmitted, wherein the first-level DCI includes information about a set of time and frequency resources associated with a Physical Downlink Shared Channel (PDSCH), and wherein the second-level DCI includes decoding information associated with the PDSCH; and Based on the information about the time and frequency resource set, a transmission including the second-level DCI and the PDSCH is transmitted for the UE, wherein the second-level DCI is multiplexed with the PDSCH and wherein the second-level DCI overlaps with the PDSCH in time.

Images