Piggyback DCI's information (DCII) in pdsch

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) may receive first downlink control information (DCI) via a physical downlink control channel (PDCCH), and the first DCI may include information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The UE may receive at least one of the instances of second DCI in accordance with the information. In some cases, the information included in the first DCI includes an indication of DCI resource information in a physical downlink shared channel (PDSCH), and the DCI resource information in the PDSCH may indicate the resources for second DCI (e.g., of one or more other PDCCH transmissions). Additionally, or alternatively, the information included in the first DCI may include an indication of a presence of second DCI in a physical downlink shared channel (PDSCH).

Description

Qualcomm Ref. No. 2500778WO1PIGGYBACK DCI’S INFORMATION (DCII) IN PDSCHCROSS REFERENCE

[0001] The present Application for Patent claims priority to Israel Patent Application No. 319120 by UZIEL et al., entitled “PIGGYBACK DCI’S INFORMATION (DCII) IN PDSCH,” filed February 20, 2025, which is assigned to the assignee hereof, and expressly incorporated by reference in its entirety herein.FIELD OF TECHNOLOGY

[0002] The following relates to wireless communications, including resource indications for instances of downlink control information (DCI) (e.g., piggyback DCI’s information (DCII) in physical downlink shared channel (PDSCH)).BACKGROUND

[0003] Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power). Examples of such multiple-access systems include fourth generation (4G) systems such as Long Term Evolution (LTE) systems, LTE- Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems which may be referred to as New Radio (NR) systems. These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal FDMA (OFDMA), or discrete Fourier transform spread orthogonal frequency division multiplexing (DFT-S-OFDM). A wireless multiple-access communications system may include one or more base stations, each supporting wireless communication for communication devices, which may be known as user equipment (UE).SUMMARY

[0004] The systems, methods, and devices of this disclosure each have several innovative aspects, no single one of which is solely responsible for the desirable attributes disclosed herein.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO2

[0005] A method for wireless communications by a user equipment (UE) is described. The method may include receiving first downlink control information (DCI) via a physical downlink control channel (PDCCH), the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI and receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0006] A UE for wireless communications is described. The UE may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the UE to receive first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI and receive at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0007] Another UE for wireless communications is described. The UE may include means for receiving first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI and means for receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0008] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to receive first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI and receive at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0009] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the information included in the first DCI includes an indication of DCI resource information in a physical downlink shared channel (PDSCH) Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO3scheduled by the first DCI and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for receiving the DCI resource information in the PDSCH based on the indication of DCI resource information, where receiving the at least one of the one or more instances of second DCI may be in accordance with resources indicated by the DCI resource information in the PDSCH.

[0010] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the PDCCH may be received in a first resource block, and the DCI resource information in the PDSCH indicates resources of a second resource block for receiving second DCI, the second resource block associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both.

[0011] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the DCI resource information in the PDSCH indicates one or more control resource sets (CORESETs) for receiving second DCI.

[0012] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the DCI resource information in the PDSCH indicates at least one control channel element (CCE) associated with receiving second DCI.

[0013] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first DCI includes a single bit that indicates a presence of the DCI resource information in the PDSCH scheduled by the first DCI and the PDSCH includes one or more bits that indicate a quantity of instances of second DCI that may be indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0014] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the first DCI includes one or more bits that indicate a quantity of instances of second DCI that may be indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0015] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, before receiving the first DCI, configuration information indicating whether the DCI resource information indicates a frequency resource,Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO4indicates a time resource, indicates one or more CORESETs, indicates at least one CCE, or a combination thereof.

[0016] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the PDSCH includes the DCI resource information based on one or more periodicities, one or more rules, one or more conditions, or any combination thereof.

[0017] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the information included in the first DCI includes an indication of a presence of second DCI in an PDSCH scheduled by the first DCI and receiving the at least one of the one or more instances of second DCI may be based on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.

[0018] In some examples of the method, UEs, and non-transitory computer-readable medium described herein, the information included in the first DCI includes an indication of a presence of additional control information in an PDSCH scheduled by the first DCI, receiving the additional control information may be based on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the additional control information in the PDSCH and, and the additional control information may be non-allocation control information.

[0019] Some examples of the method, UEs, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting an uplink acknowledgment that indicates successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI.

[0020] A method for wireless communications by a network entity is described. The method may include transmitting first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI and transmitting at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO5

[0021] A network entity for wireless communications is described. The network entity may include one or more memories storing processor executable code, and one or more processors coupled with the one or more memories. The one or more processors may individually or collectively be operable to execute the code to cause the network entity to transmit first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI and transmit at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0022] Another network entity for wireless communications is described. The network entity may include means for transmitting first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI and means for transmitting at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0023] A non-transitory computer-readable medium storing code for wireless communications is described. The code may include instructions executable by one or more processors to transmit first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI and transmit at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0024] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the information included in the first DCI includes an indication of DCI resource information in an PDSCH scheduled by the first DCI and the method, apparatuses, and non-transitory computer-readable medium may include further operations, features, means, or instructions for transmitting the DCI resource information in the PDSCH based on the indication of DCI resource information, where transmitting the at least one of the one or more instances of second DCI may be in accordance with resources indicated by the DCI resource information in the PDSCH.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO6

[0025] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the PDCCH may be transmitted in a first resource block, and the DCI resource information in the PDSCH indicates resources of a second resource block for transmitting second DCI, the second resource block associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both.

[0026] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the DCI resource information in the PDSCH indicates one or more CORESETs for receiving second DCI.

[0027] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the DCI resource information in the PDSCH indicates at least one CCE associated with receiving second DCI.

[0028] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first DCI includes a single bit that indicates a presence of the DCI resource information in the PDSCH scheduled by the first DCI and the PDSCH includes one or more bits that indicate a quantity of instances of second DCI that may be indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0029] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the first DCI includes one or more bits that indicate a quantity of instances of second DCI that may be indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0030] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, before receiving the first DCI, configuration information indicating whether the DCI resource information indicates a frequency resource, indicates a time resource, indicates one or more CORESETs, indicates at least one CCE, or a combination thereof.

[0031] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the PDSCH includes the DCI resourceAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO7information based on one or more periodicities, one or more rules, one or more conditions, or any combination thereof.

[0032] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the information included in the first DCI includes an indication of a presence of second DCI in an PDSCH scheduled by the first DCI and transmitting the at least one of the one or more instances of second DCI may be based on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.

[0033] In some examples of the method, network entities, and non-transitory computer-readable medium described herein, the information included in the first DCI includes an indication of a presence of additional control information in an PDSCH scheduled by the first DCI, transmitting the additional control information may be based on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the additional control information in the PDSCH and, and the additional control information may be non-allocation control information.

[0034] Some examples of the method, network entities, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving an uplink acknowledgment that indicates successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI.

[0035] Details of one or more implementations of the subject matter described in this disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages will become apparent from the description, the drawings, and the claims. Note that the relative dimensions of the following figures may not be drawn to scale.BRIEF DESCRIPTION OF THE DRAWINGS

[0036] FIGs. 1 and 2 show examples of wireless communications systems that support resource indications for instances of downlink control information (DCI) in accordance with one or more aspects of the present disclosure.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO8

[0037] FIG. 3 shows an example of a resource configuration that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.

[0038] FIG. 4 shows an example of a process flow that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.

[0039] FIGs. 5 and 6 show block diagrams of devices that support resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.

[0040] FIG. 7 shows a block diagram of a communications manager that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.

[0041] FIG. 8 shows a diagram of a system including a device that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.

[0042] FIGs. 9 and 10 show block diagrams of devices that support resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.

[0043] FIG. 11 shows a block diagram of a communications manager that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.

[0044] FIG. 12 shows a diagram of a system including a device that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.

[0045] FIGs. 13 through 15 show flowcharts illustrating methods that support resource indications for instances of DCI in accordance with one or more aspects of the present disclosure.DETAILED DESCRIPTION

[0046] In some wireless communication systems, a user equipment (UE) may receive downlink control information (DCI) via a physical downlink control channel (PDDCH). To receive a PDCCH including DCI for the UE, the UE may perform blind detection and decoding within a search space to attempt to receive the PDCCH (e.g.,Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO9evaluating whether given instances of PDCCH are intended for reception by the UE). For example, the UE may not know the specific resources that a network entity uses to transmit a PDCCH for the UE, and the UE may perform blind detection of PDCCH candidates of the search space to attempt to receive the PDCCH. However, performing blind detection of PDCCH candidates may involve processing and power consumption, because the UE may use power to detect and decode PDCCH candidates that may not include a PDCCH intended for the UE.

[0047] In some implementations, a network entity may indicate, within an instance of DCI received by a UE in a first PDCCH, information about the location of future or accompanying instances of DCI in a subsequent PDCCH. For example, the UE may detect a first DCI (e.g., via blind detection, non-blind detection), which may include DCI information (DCII) indicating information about other DCIs (e.g., a quantity of DCIs, resource allocations associated with the other DCIs, size indications associated with the other DCIs). The UE may use the DCII received in the first DCI to support detecting the other DCIs, and may thus reduce blind detection operations. However, including DCII within DCI (e.g., of a PDCCH) may increase the payload of the DCI (e.g., of the PDCCH), which may reduce performance between the UE and the network entity. Additionally, or alternatively, the UE may not have an indication that DCII is included in the DCI, including if the UE misses a detection of the DCI including the DCII.

[0048] In some wireless communications systems, a UE may piggyback DCI in a physical downlink shared channel (PDSCH) that is scheduled by a DCI (e.g., a first DCI, a scheduling DCI, of a PDCCH). For example, the payload of one or more instances of DCI may be included (e.g., inserted, multiplexed, piggybacked) on a PDSCH by multiplexing DCI data in the PDSCH. Because the PDSCH may be scheduled, inserting the payload of the DCI into the PDSCH may reduce a quantity of misdetections for the DCI and reduce PDCCH blocking. However, inserting DCI in a PDSCH may lead to a substantial consumption of PDSCH resource elements (REs) in order to accommodate the DCI payload. Further, a scheduling DCI (e.g., of a PDCCH) for the PDSCH may indicate information about the piggybacked DCI in order for the UE to successfully decode the piggybacked DCI, which may increase the payload of the scheduling DCI.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO10

[0049] The techniques described herein support a network entity implementing (e.g., multiplexing, inserting, piggybacking) DCII, special DCI, or both in a PDSCH, which may reduce power consumption associated with blind detection and decoding operations, and may provide solutions for the issues related to the inclusion of DCII in a DCI, the inclusion of DCI in a PDSCH, or both. In some implementations, a network entity may insert DCII in a PDSCH. For example, a first DCI may schedule a PDSCH. In some cases, the first DCI may indicate that the PDSCH includes one or more instances of DCII, and each instance of DCII may indicate information about one or more instances of second DCI (e.g., future or accompanying instances of DCI). By inserting DCII in the PDSCH, the size of the first DCI may be maintained or increased by a small quantity of bits (e.g., with minimal reduction or no reduction in performance due to an increased DCI payload compared to including DCII within the first DCI). Further, a UE may transmit an uplink acknowledgment to a network entity to indicate successful detection of the PDSCH (e.g., acknowledgment, ACK), or unsuccessful detection of the PDSCH (e.g., negative acknowledgment, NACK), which may indicate any misdetections of the DCII to the network entity. Additionally, or alternatively, piggybacking DCII in the PDSCH may reduce overhead on PDSCH REs (e.g., compared to piggybacking entire DCI payloads on the PDSCH). Additionally, or alternatively, piggybacking DCII on the PDSCH may decrease the payload of the scheduling DCI (e.g., the first DCI), compared to piggybacking an entire DCI on the PDSCH, because a DCII size may be pre-configured.

[0050] Additionally, or alternatively, a first DCI (e.g., scheduling DCI) may indicate that a PDSCH includes additional control information. For example, a first DCI may indicate that a PDSCH includes one or more fields from one or more second instances of DCI, including second DCI that may be broadcast by the network entity (e.g., a special broadcasted DCI, DCI intended for multiple UEs, DCI intended for general reception by UEs served by the network entity). Instead of, or in addition to, broadcasting the second DCI, the network entity may piggyback the second DCI (e.g., special DCI, broadcasted DCI) on a respective instance of PDSCH for one or more UEs. In some other cases, a first DCI may indicate that a PDSCH includes one or more portions of DCI grants that may indicate additional information, which may not be related to DCI allocation (e.g., bandwidth part (BWP) switch information, antenna portAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO11information). For example, the PDSCH may include one or more fields from other DCI, where the one or more fields may not be related to DCI allocation (e.g., DCII) and may not be an entire other DCI (e.g., a full DCI included in a PDSCH). For examples in which a UE receives such second DCI in a PDSCH, the UE may refrain from blind decoding for the second DCI (e.g., which may be blindly decoded by other UEs that may not have received the second DCI in a respective PDSCH).

[0051] Aspects of the disclosure are initially described in the context of wireless communications systems, resource diagrams, and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to resource indications for instances of DCI.

[0052] FIG. 1 shows an example of a wireless communications system 100 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The wireless communications system 100 may include one or more devices, such as one or more network devices (e.g., network entities 105), one or more UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) network, an LTE-Advanced (LTE- A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating in accordance with other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0053] The network entities 105 may be dispersed throughout a geographic area to form the wireless communications system 100 and may include devices in different forms or having different capabilities. In various examples, a network entity 105 may be referred to as a network element, a mobility element, a radio access network (RAN) node, or network equipment, among other nomenclature. In some examples, network entities 105 and UEs 115 may wirelessly communicate via communication link(s) 125 (e.g., a radio frequency (RF) access link). For example, a network entity 105 may support a coverage area 110 (e.g., a geographic coverage area) over which the UEs 115 and the network entity 105 may establish the communication link(s) 125. The coverage area 110 may be an example of a geographic area over which a network entity 105 and a UE 115 may support the communication of signals according to one or more radio access technologies (RATs).Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO12

[0054] The UEs 115 may be dispersed throughout a coverage area 110 of the wireless communications system 100, and each UE 115 may be stationary, or mobile, or both at different times. The UEs 115 may be devices in different forms or having different capabilities. Some example UEs 115 are illustrated in FIG. 1. The UEs 115 described herein may be capable of supporting communications with various types of devices in the wireless communications system 100 (e.g., other wireless communication devices, including UEs 115 or network entities 105), as shown in FIG. 1.

[0055] As described herein, a node of the wireless communications system 100, which may be referred to as a network node, or a wireless node, may be a network entity 105 (e.g., any network entity described herein), a UE 115 (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be a UE 115. As another example, a node may be a network entity 105. As another example, a first node may be configured to communicate with a second node or a third node. In one aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a UE 115. In another aspect of this example, the first node may be a UE 115, the second node may be a network entity 105, and the third node may be a network entity 105. In yet other aspects of this example, the first, second, and third nodes may be different relative to these examples. Similarly, reference to a UE 115, network entity 105, apparatus, device, computing system, or the like may include disclosure of the UE 115, network entity 105, apparatus, device, computing system, or the like being a node. For example, disclosure that a UE 115 is configured to receive information from a network entity 105 also discloses that a first node is configured to receive information from a second node.

[0056] In some examples, network entities 105 may communicate with a core network 130, or with one another, or both. For example, network entities 105 may communicate with the core network 130 via backhaul communication link(s) 120 (e.g., in accordance with an SI, N2, N3, or other interface protocol). In some examples, network entities 105 may communicate with one another via backhaul communication link(s) 120 (e.g., in accordance with an X2, Xn, or other interface protocol) either directly (e.g., directly between network entities 105) or indirectly (e.g., via the coreAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO13network 130). In some examples, network entities 105 may communicate with one another via a midhaul communication link 162 (e.g., in accordance with a midhaul interface protocol) or a fronthaul communication link 168 (e.g., in accordance with a fronthaul interface protocol), or any combination thereof. The backhaul communication link(s) 120, midhaul communication links 162, or fronthaul communication links 168 may be or include one or more wired links (e.g., an electrical link, an optical fiber link) or one or more wireless links (e.g., a radio link, a wireless optical link), among other examples or various combinations thereof. A UE 115 may communicate with the core network 130 via a communication link 155.

[0057] One or more of the network entities 105 or network equipment described herein may include or may be referred to as a base station 140 (e.g., a base transceiver station, a radio base station, an NR base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next-generation NodeB or giga-NodeB (either of which may be referred to as a gNB), a 5GNB, a next-generation eNB (ng-eNB), a Home NodeB, a Home eNodeB, or other suitable terminology). In some examples, a network entity 105 (e.g., a base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture, which may be configured to utilize a protocol stack that is physically or logically integrated within one network entity (e.g., a network entity 105 or a single RAN node, such as a base station 140).

[0058] In some examples, a network entity 105 may be implemented in a disaggregated architecture (e.g., a disaggregated base station architecture, a disaggregated RAN architecture), which may be configured to utilize a protocol stack that is physically or logically distributed among multiple network entities (e.g., network entities 105), such as an integrated access and backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, a network entity 105 may include one or more of a central unit (CU), such as a CU 160, a distributed unit (DU), such as a DU 165, a radio unit (RU), such as an RU 170, a RAN Intelligent Controller (RIC), such as an RIC 175 (e.g., a Near-Real Time RIC (Near-RT RIC), a Non-Real Time RIC (Non-RT RIC)), a Service Management and Orchestration (SMO) system, such as an SMO system 180, or any combination thereof. An RU 170 may also be referred to as a radio head, a smart radio head, a remote radio head (RRH), a remoteAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO14radio unit (RRU), or a transmission reception point (TRP). One or more components of the network entities 105 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more of the network entities 105 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU), a virtual DU (VDU), a virtual RU (VRU)).

[0059] The split of functionality between a CU 160, a DU 165, and an RU 170 is flexible and may support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, or any combinations thereof) are performed at a CU 160, a DU 165, or an RU 170. For example, a functional split of a protocol stack may be employed between a CU 160 and a DU 165 such that the CU 160 may support one or more layers of the protocol stack and the DU 165 may support one or more different layers of the protocol stack. In some examples, the CU 160 may host upper protocol layer (e.g., layer 3 (L3), layer 2 (L2)) functionality and signaling (e.g., Radio Resource Control (RRC), service data adaptation protocol (SDAP), Packet Data Convergence Protocol (PDCP)). The CU 160 (e.g., one or more CUs) may be connected to a DU 165 (e.g., one or more DUs) or an RU 170 (e.g., one or more RUs), or some combination thereof, and the DUs 165, RUs 170, or both may host lower protocol layers, such as layer 1 (LI) (e.g., physical (PHY) layer) or L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU 160. Additionally, or alternatively, a functional split of the protocol stack may be employed between a DU 165 and an RU 170 such that the DU 165 may support one or more layers of the protocol stack and the RU 170 may support one or more different layers of the protocol stack. The DU 165 may support one or multiple different cells (e.g., via one or multiple different RUs, such as an RU 170). In some cases, a functional split between a CU 160 and a DU 165 or between a DU 165 and an RU 170 may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU 160, a DU 165, or an RU 170, while other functions of the protocol layer are performed by a different one of the CU 160, the DU 165, or the RU 170). A CU 160 may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions. A CU 160 may be connected to a DU 165 via a midhaul communication linkAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO15162 (e.g., Fl, Fl-c, Fl-u), and a DU 165 may be connected to an RU 170 via a fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, a midhaul communication link 162 or a fronthaul communication link 168 may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities (e.g., one or more of the network entities 105) that are in communication via such communication links.

[0060] In some wireless communications systems (e.g., the wireless communications system 100), infrastructure and spectral resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, providing an IAB network architecture (e.g., to a core network 130). In some cases, in an IAB network, one or more of the network entities 105 (e.g., network entities 105 or IAB node(s) 104) may be partially controlled by each other. The IAB node(s) 104 may be referred to as a donor entity or an IAB donor. A DU 165 or an RU 170 may be partially controlled by a CU 160 associated with a network entity 105 or base station 140 (such as a donor network entity or a donor base station). The one or more donor entities (e.g., IAB donors) may be in communication with one or more additional devices (e.g., IAB node(s) 104) via supported access and backhaul links (e.g., backhaul communication link(s) 120). IAB node(s) 104 may include an IAB mobile termination (IAB-MT) controlled (e.g., scheduled) by one or more DUs (e.g., DUs 165) of a coupled IAB donor. An IAB-MT may be equipped with an independent set of antennas for relay of communications with UEs 115 or may share the same antennas (e.g., of an RU 170) of IAB node(s) 104 used for access via the DU 165 of the IAB node(s) 104 (e.g., referred to as virtual IAB-MT (vIAB-MT)). In some examples, the IAB node(s) 104 may include one or more DUs (e.g., DUs 165) that support communication links with additional entities (e.g., IAB node(s) 104, UEs 115) within the relay chain or configuration of the access network (e.g., downstream). In such cases, one or more components of the disaggregated RAN architecture (e.g., the IAB node(s) 104 or components of the IAB node(s) 104) may be configured to operate according to the techniques described herein.

[0061] In the case of the techniques described herein applied in the context of a disaggregated RAN architecture, one or more components of the disaggregated RAN architecture may be configured to support resource indications for instances of DCI asAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO16described herein. For example, some operations described as being performed by a UE 115 or a network entity 105 (e.g., a base station 140) may additionally, or alternatively, be performed by one or more components of the disaggregated RAN architecture (e.g., components such as an IAB node, a DU 165, a CU 160, an RU 170, an RIC 175, an SMO system 180).

[0062] A UE 115 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where the “device” may also be referred to as a unit, a station, a terminal, or a client, among other examples. A UE 115 may also include or may be referred to as a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, a UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (loT) device, an Internet of Everything (loE) device, or a machine type communications (MTC) device, among other examples, which may be implemented in various objects such as appliances, vehicles, or meters, among other examples.

[0063] The UEs 115 described herein may be able to communicate with various types of devices, such as UEs 115 that may sometimes operate as relays, as well as the network entities 105 and the network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, among other examples, as shown in FIG. 1.

[0064] The UEs 115 and the network entities 105 may wirelessly communicate with one another via the communication link(s) 125 (e.g., one or more access links) using resources associated with one or more carriers. The term “carrier” may refer to a set of RF spectrum resources having a defined PHY layer structure for supporting the communication link(s) 125. For example, a carrier used for the communication link(s) 125 may include a portion of an RF spectrum band (e.g., a BWP) that is operated according to one or more PHY layer channels for a given RAT (e.g., LTE, LTE-A, LTE-A Pro, NR). Each PHY layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling that coordinates operation for the carrier, user data, or other signaling. The wireless communications system 100 may support communication with a UE 115 using carrier aggregation or multi-carrier operation. A UE 115 may be configured with multiple downlinkAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO17component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplexing (FDD) and time division duplexing (TDD) component carriers. Communication between a network entity 105 and other devices may refer to communication between the devices and any portion (e.g., entity, sub-entity) of a network entity 105. For example, the terms “transmitting,” “receiving,” or “communicating,” when referring to a network entity 105, may refer to any portion of a network entity 105 (e.g., a base station 140, a CU 160, a DU 165, a RU 170) of a RAN communicating with another device (e.g., directly or via one or more other network entities, such as one or more of the network entities 105).

[0065] The communication link(s) 125 of the wireless communications system 100 may include downlink transmissions (e.g., forward link transmissions) from a network entity 105 to a UE 115, uplink transmissions (e.g., return link transmissions) from a UE 115 to a network entity 105, or both, among other configurations of transmissions. Carriers may carry downlink or uplink communications (e.g., in an FDD mode) or may be configured to carry downlink and uplink communications (e.g., in a TDD mode).

[0066] Signal waveforms transmitted via a carrier may be made up of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may refer to resources of one symbol period (e.g., a duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The quantity of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both), such that a relatively higher quantity of resource elements (e.g., in a transmission duration) and a relatively higher order of a modulation scheme may correspond to a relatively higher rate of communication. A wireless communications resource may refer to a combination of an RF spectrum resource, a time resource, and a spatial resource (e.g., a spatial layer, a beam), and the use of multiple spatial resources may increase the data rate or data integrity for communications with a UE 115.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO18

[0067] The time intervals for the network entities 105 or the UEs 115 may be expressed in multiples of a basic time unit which may, for example, refer to a sampling period of Ts= l / (A / max■ Nf) seconds, for which fmaxmay represent a supported subcarrier spacing, and Nf may represent a supported discrete Fourier transform (DFT) size. Time intervals of a communications resource may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0068] Each frame may include multiple consecutively-numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into a quantity of slots. Alternatively, each frame may include a variable quantity of slots, and the quantity of slots may depend on subcarrier spacing. Each slot may include a quantity of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communications systems, such as the wireless communications system 100, a slot may further be divided into multiple mini-slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., Ay) sampling periods. The duration of a symbol period may depend on the subcarrier spacing or frequency band of operation.

[0069] A subframe, a slot, a mini-slot, or a symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communications system 100 and may be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., a quantity of symbol periods in a TTI) may be variable. Additionally, or alternatively, the smallest scheduling unit of the wireless communications system 100 may be dynamically selected (e.g., in bursts of shortened TTIs (sTTIs)).

[0070] Physical channels may be multiplexed for communication using a carrier according to various techniques. A physical control channel and a physical data channel may be multiplexed for signaling via a downlink carrier, for example, using one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region (e.g., a control resource set (CORESET)) for a physical control channel may be defined by a set of symbol periods and may extend across the system bandwidth or a subset of the system Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO19bandwidth of the carrier. One or more control regions (e.g., CORESETs) may be configured for a set of the UEs 115. For example, one or more of the UEs 115 may monitor or search control regions for control information according to one or more search space sets, and each search space set may include one or multiple control channel candidates in one or more aggregation levels arranged in a cascaded manner. An aggregation level for a control channel candidate may refer to an amount of control channel resources (e.g., control channel elements (CCEs)) associated with encoded information for a control information format having a given payload size. Search space sets may include common search space sets configured for sending control information to UEs 115 (e.g., one or more UEs) or may include UE-specific search space sets for sending control information to a UE 115 (e.g., a specific UE).

[0071] In some examples, a network entity 105 (e.g., a base station 140, an RU 170) may be movable and therefore provide communication coverage for a moving coverage area, such as the coverage area 110. In some examples, coverage areas 110 (e.g., different coverage areas) associated with different technologies may overlap, but the coverage areas 110 (e.g., different coverage areas) may be supported by the same network entity (e.g., a network entity 105). In some other examples, overlapping coverage areas, such as a coverage area 110, associated with different technologies may be supported by different network entities (e.g., the network entities 105). The wireless communications system 100 may include, for example, a heterogeneous network in which different types of the network entities 105 support communications for coverage areas 110 (e.g., different coverage areas) using the same or different RATs.

[0072] The wireless communications system 100 may be configured to support ultra-reliable communications or low-latency communications, or various combinations thereof. For example, the wireless communications system 100 may be configured to support ultra-reliable low-latency communications (URLLC). The UEs 115 may be designed to support ultra-reliable, low-latency, or critical functions. Ultra-reliable communications may include private communication or group communication and may be supported by one or more services such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general commercial applications. The termsAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO20ultra-reliable, low-latency, and ultra-reliable low-latency may be used interchangeably herein.

[0073] In some examples, a UE 115 may be configured to support communicating directly with other UEs (e.g., one or more of the UEs 115) via a device-to-device (D2D) communication link, such as a D2D communication link 135 (e.g., in accordance with a peer-to-peer (P2P), D2D, or sidelink protocol). In some examples, one or more UEs 115 of a group that are performing D2D communications may be within the coverage area 110 of a network entity 105 (e.g., a base station 140, an RU 170), which may support aspects of such D2D communications being configured by (e.g., scheduled by) the network entity 105. In some examples, one or more UEs 115 of such a group may be outside the coverage area 110 of a network entity 105 or may be otherwise unable to or not configured to receive transmissions from a network entity 105. In some examples, groups of the UEs 115 communicating via D2D communications may support a one-to-many (1 :M) system in which each UE 115 transmits to one or more of the UEs 115 in the group. In some examples, a network entity 105 may facilitate the scheduling of resources for D2D communications. In some other examples, D2D communications may be carried out between the UEs 115 without an involvement of a network entity 105.

[0074] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or 5G core (5GC), which may include at least one control plane entity that manages access and mobility (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) and at least one user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW), a Packet Data Network (PDN) gateway (P-GW), or a user plane function (UPF)). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UEs 115 served by the network entities 105 (e.g., base stations 140) associated with the core network 130. User IP packets may be transferred through the user plane entity, which may provide IP address allocation as well as other functions. The user plane entity may be connected to IP services 150 for one or more network operators. The IP services 150 may include access to the Internet,Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO21Intranet(s), an IP Multimedia Subsystem (IMS), or a Packet-Switched Streaming Service.

[0075] The wireless communications system 100 may operate using one or more frequency bands, which may be in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or decimeter band because the wavelengths range from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, which may be referred to as clusters, but the waves may penetrate structures sufficiently for a macro cell to provide service to the UEs 115 located indoors. Communications using UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than one hundred kilometers) compared to communications using the smaller frequencies and longer waves of the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz.

[0076] The wireless communications system 100 may utilize both licensed and unlicensed RF spectrum bands. For example, the wireless communications system 100 may employ License Assisted Access (LAA), LTE-Unlicensed (LTE-U) RAT, or NR technology using an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. While operating using unlicensed RF spectrum bands, devices such as the network entities 105 and the UEs 115 may employ carrier sensing for collision detection and avoidance. In some examples, operations using unlicensed bands may be based on a carrier aggregation configuration in conjunction with component carriers operating using a licensed band (e.g., LAA). Operations using unlicensed spectrum may include downlink transmissions, uplink transmissions, P2P transmissions, or D2D transmissions, among other examples.

[0077] A network entity 105 (e.g., a base station 140, an RU 170) or a UE 115 may be equipped with multiple antennas, which may be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of a network entity 105 or a UE 115 may be located within one or more antenna arrays or antenna panels, which may support MIMO operations or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as anAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO1antenna tower. In some examples, antennas or antenna arrays associated with a network entity 105 may be located at diverse geographic locations. A network entity 105 may include an antenna array with a set of rows and columns of antenna ports that the network entity 105 may use to support beamforming of communications with a UE 115. Likewise, a UE 115 may include one or more antenna arrays that may support various MIMO or beamforming operations. Additionally, or alternatively, an antenna panel may support RF beamforming for a signal transmitted via an antenna port.

[0078] Beamforming, which may also be referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that may be used at a transmitting device or a receiving device (e.g., a network entity 105, a UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming may be achieved by combining the signals communicated via antenna elements of an antenna array such that some signals propagating along particular orientations with respect to an antenna array experience constructive interference while others experience destructive interference. The adjustment of signals communicated via the antenna elements may include a transmitting device or a receiving device applying amplitude offsets, phase offsets, or both to signals carried via the antenna elements associated with the device. The adjustments associated with each of the antenna elements may be defined by a beamforming weight set associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or receiving device, or with respect to some other orientation).

[0079] The wireless communications system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP -based. An RLC layer may perform packet segmentation and reassembly to communicate via logical channels. A MAC layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer also may implement error detection techniques, error correction techniques, or both to support retransmissions to improve link efficiency. In the control plane, an RRC layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network entity 105 or a core network 130Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO23supporting radio bearers for user plane data. A PHY layer may map transport channels to physical channels.

[0080] The UEs 115 and the network entities 105 may support retransmissions of data to increase the likelihood that data is received successfully. Hybrid automatic repeat request (HARQ) feedback is one technique for increasing the likelihood that data is received correctly via a communication link (e.g., the communication link(s) 125, a D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ may improve throughput at the MAC layer in relatively poor radio conditions (e.g., low signal -to-noise conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific slot for data received via a previous symbol in the slot. In some other examples, the device may provide HARQ feedback in a subsequent slot, or according to some other time interval.

[0081] In some implementations, a UE 115 may receive DCI via a PDCCH. To receive a PDCCH including DCI for the UE 115, the UE 115 may perform blind detection and decoding within a search space (e.g., one or more search space sets). For example, the UE 115 may not know the specific resources that a network entity 105 uses to transmit a PDCCH for the UE 115, and the UE 115 may perform blind detection of PDCCH candidates of the search space to attempt to receive the PDCCH. However, performing blind detection of PDCCH candidates may involve processing and power consumption, because the UE 115 may use power to detect and decode PDCCH candidates that may not include the PDCCH intended for the UE 115.

[0082] In some implementations, a network entity 105 may indicate, within an instance of DCI received by a UE 115, information about the location of future or accompanying DCIs in a subsequent PDCCH. For example, the UE 115 may detect a first DCI (e.g., via blind detection, non-blind detection), which may include DCII indicating information about other DCIs (e.g., other instances of DCI). The UE 115 may use the DCII received in the first DCI to support detecting the other DCIs, and may thus reduce the blind detection operations. However, including DCII within DCI may increase the payload of the DCI (e.g., of the PDCCH), which may reduce performance between the UE 115 and the network entity 105. Additionally, or alternatively, the UEAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO24115 may not have an indication that the DCII is included in the DCI, including if the UE 115 misses a detection of the DCI including the DCII.

[0083] In some wireless communications systems 100, a UE 115 may piggyback DCI in a PDSCH that is scheduled by a DCI (e.g., a first DCI, a scheduling DCI, of a PDCCH). For example, the payload of one or more DCIs may be included (e.g., inserted, multiplexed, piggybacked) on a PDSCH by multiplexing the DCI data in the PDSCH. Because the PDSCH may be scheduled, inserting the payload of the DCI into the PDSCH may reduce a quantity of misdetections for the DCI and reduce PDCCH blocking. However, inserting DCI in a PDSCH may lead to a substantial consumption of PDSCH REs in order to accommodate the DCI payloads. Further, a scheduling DCI (e.g., of a PDCCH) for the PDSCH may indicate information about the piggybacked DCI in order for the UE 115 to successfully decode the piggybacked DCI, which may increase the payload of the scheduling DCI.

[0084] The techniques described herein support a network entity 105 implementing (e.g., multiplexing, inserting, piggybacking) DCII, special DCI, or both in a PDSCH, which may reduce power consumption associated with blind detection and decoding operations. In some implementations, a network entity 105 may insert DCII in a PDSCH. For example, a first DCI may schedule a PDSCH. In some cases, the first DCI may indicate that the PDSCH includes one or more DCIIs (e.g., one or more instances of DCII), and each DCII may indicate information about one or more second DCIs (e.g., instances of second DCI, future or accompanying DCIs). By inserting DCII in the PDSCH, the size of the first DCI may be maintained or increased by a small quantity of bits (e.g., with minimal reduction or no reduction in performance due to an increased DCI payload compared to including DCII within the first DCI). Further, the UE 115 may transmit an uplink acknowledgment to a network entity 105 to indicate successful detection of the PDSCH (e.g., acknowledgment, ACK), or unsuccessful detection of the PDSCH (e.g., negative acknowledgment, NACK), which may indicate any misdetections of the DCII to the network entity 105. Additionally, or alternatively, piggybacking DCII in the PDSCH may reduce overhead on PDSCH REs (e.g., compared to piggybacking entire DCI payloads on the PDSCH). Additionally, or alternatively, piggybacking DCII on the PDSCH may decrease the payload of theAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO25scheduling DCI (e.g., the first DCI), compared to piggybacking an entire DCI on the PDSCH, because a DCII size may be pre-configured.

[0085] Additionally, or alternatively, a first DCI (e.g., scheduling DCI) may indicate that a PDSCH includes additional control information. For example, a first DCI may indicate that a PDSCH includes one or more fields from one or more second instances of DCI, including second DCI that may be broadcast by a network entity 105 (e.g., a special broadcasted DCI, DCI intended for multiple UEs 115, DCI intended for general reception by UEs 115 served by the network entity 105). Instead of, or in addition to, broadcasting the second DCI, the network entity 105 may piggyback the second DCI on a respective instance of PDSCH for one or more UEs 115. In some other cases, a first DCI may indicate that a PDSCH includes one or more portions of DCI grants that may indicate additional information, which may not be related to DCI allocation (e.g., BWP switch information, antenna port information). For examples in which a UE 115 receives such second DCI in a PDSCH, the UE 115 may refrain from blind decoding for the second DCI (e.g., which may be blindly decoded by other UEs 115 that may not have received the second DCI in a respective PDSCH).

[0086] FIG. 2 shows an example of a wireless communications system 200 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The wireless communications system 200 may implement, or be implemented by, aspects of the wireless communications system 100. For example, the wireless communications system 200 may include one or more network entities 105 and one or more UEs 115, including at least the network entity 105-a and UE 115-a. The techniques described in the context of the wireless communications system 200 may support a network entity 105-a to piggyback DCII, one or more unicast field DCIs, or both in a PDSCH.

[0087] The UE 115-a and the network entity 105-a may communicate via a downlink 205 and an uplink 210 of a communication link (e.g., a communication link 125). The network entity 105-a may send transmissions, such as DCI, via the downlink 205. In some implementations, the UE 115-a may perform one or more blind detections to receive a DCI (e.g., via a PDCCH) from the network entity 105-a. For example, the UE 115-a may perform blind decoding on a search space in an attempt to detect or decode a PDCCH including DCI for the UE 115-a. However, blind decoding may beAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO26associated with power consumption, because the UE 115-a may perform blind decoding on multiple candidates before successfully decoding a PDCCH that includes DCI for the UE 115-a.

[0088] In some implementations, to support reducing processing, blocking, and other challenges associated with blind detections, a network entity 105-a may indicate information (e.g., a quantity of DCIs, resource allocations, size indications, or any combination thereof) associated with future or accompanying DCIs (e.g., second DCI 225). Information associated with the future or accompanying DCIs may be known as DCI information (DCII). In some cases, the network entity 105-a may include DCII in a first DCI 215 (e.g., a received DCI, of a first PDCCH). In some examples, the first DCI 215 may be blindly detected (e.g., a blind DCI). In some other examples, the first DCI 215 may not be blindly detected (e.g., may be indicated, may be scheduled, may be a non-blind DCI).

[0089] Including DCII in a first DCI 215 may reduce processing and power consumption associated with blind decoding of second DCI 225. For example, the UE 115-a may, based on the DCII, detect and decode second DCIs 225 (e.g., informed DCIs, instances of second DCI). For example, the first DCI 215 may indicate some information about resources associated with a second DCI 225-b (e.g., of a second PDCCH). The UE 115-a may use the information to detect the second DCI 225-b without or with a reduced quantity of blind detections (e.g., partial blind detection). For example, in some examples, the detection of the second DCI 225-b may be non-blind, as the DCII may indicate the resources with which to receive the second DCI 225. In some cases, detection performance may be increased or enhanced. For example, the DCII may indicate to the UE 115-a where to receive the second DCI 225-b, reducing misdetections and a quantity of blind decodings (e.g., based on knowledge of existing PDCCH-DMRS, reduced pruning decisions, adapted signal-to-noise ratio threshold, reduced false alarms (FA)). In some cases, the DCII may also indicate information that may enable rate matching for the second DCI 225 (e.g., future DCIs, non-scheduling DCI, or Ko > 0, where Ko may indicate a future slot). In some cases, indicating DCII may enable the network entity to transmit more DCIs within a slot, as the UE 115-a may use fewer blind detection attempts in order to receive each DCI. Additionally, or alternatively, indicating DCII to the UE 115-a may reduce collisions between differentAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO27DCI. Additionally, or alternatively, indicating DCII may allow for a dynamic allocation of resources for DCI, which may reduce PDCCH blocking (e.g., compared to using a formula for allocating resources in blind decoding).

[0090] Including DCII in the first DCI 215 may increase the payload of the first DCI 215. For example, to include the DCII, the first DCI 215 may include more fields than if DCII is not included. Increasing the payload of the first DCI 215 may reduce performance of communications between the UE 115-a and the network entity 105-a. Additionally, or alternatively, the network entity 105-a may determine one or more DCIs, such as the first DCI 215, in which to include the DCII. However, the UE 115-a may have no indication of the one or more DCIs. For example, the UE 115-a may not know where to find a reference DCI that includes DCII. In some examples, the network entity 105-a may include DCII in each DCI, including the first DCI 215, which may result in multiple DCIs with increased payloads. In some other examples, the network entity 105-a may include the DCII in a fewer than all instances of DCIs, such as the first DCI 215. The UE 115-a may fail to detect or decode a reduced quantity of DCIs, however. Additionally, or alternatively, the network entity 105-a may link DCIs together. In some examples, indicating multiple DCI in DCII may use a substantial quantity of bits or resources. Instead, the network entity may link DCI together such that each DCI may include DCII associated with one future DCI. For example, the first DCI 215 may include some DCII that pertains to the second DCI 225-b, and the second DCI 225-b may include other DCII that pertains to a third DCI. However, if one of the instances of DCI is not successfully received, such as the second DCI 225-b, the UE 115-a may be unable to implement the DCII associated with the next DCI (e.g., the third DCI). For example, the UE 115-a may default to blind decoding.

[0091] In some wireless communications systems 200, one or more instances of DCI may be piggybacked in a PDSCH. For example, the network entity 105-a may multiplex the payload (e.g., all DCI fields) of one or more DCIs within the PDSCH. For example, the PDSCH may be a blend of shared and control information. Piggybacking one or more instances of DCI in a PDSCH may allow the UE 115-a to receive multiple DCIs while maintaining the blind decoding procedure for the PDCCH. For example, because a PDSCH may be scheduled (e.g., by DCI of an accompanying PDCCH), piggybacked DCI may be likely to be detected and decoded. For example, in someAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO28cases, piggybacking DCI on a PDSCH may reduce DCI misdetections, as compared to blind detection. Additionally, or alternatively, piggybacking DCI on a PDSCH may enable the network entity 105-a to transmit multiple DCIs to the UE 115-a in a single PDSCH. Additionally, or alternatively, piggybacking DCI on the PDSCH may reduce PDCCH blocking allocations, as the network entity 105-a may be able to schedule the UE 115-a via a PDSCH. For example, the resources within a control channel region may be limited, and the network entity 105-a may be able to schedule a limited quantity of UEs 115, and PDCCH transmissions, within a slot. By piggybacking DCI on a PDSCH, the network entity 105-a may implement resources in the data region, while freeing resources in the control region.

[0092] In some implementations, piggybacking DCI on a PDSCH may consume a substantial quantity of PDSCH REs. For example, DCI may use resources within a PDSCH that may have been otherwise used for data. In some cases, a DCI payload may be a relatively large quantity of bits (e.g., tens of bits), which may consume a large quantity of REs in the data region for the piggybacked DCIs. Further, a PDSCH may be scheduled by a DCI. In order to decode the PDSCH with the piggybacked DCIs, the UE 115-a may rely on some information about the piggybacked DCIs. A DCI may be expanded to include information related to the piggybacked DCIs (e.g., payload size of inserted DCI for multiplexing with data in PDSCH, quantity of piggybacked DCIs). This may increase the payload of DCI, which may reduce performance within the wireless communications system 200, among other challenges.

[0093] In some implementations, DCII 220 may be included (e.g., multiplexed, inserted, piggybacked) in a PDSCH 230. For example, a first DCI 215 (e.g., of a PDCCH) may schedule a PDSCH 230 (e.g., of a same resource block or other associated resource as the PDCCH). In some implementations, the first DCI 215 may indicate whether the PDSCH 230 includes DCII 220. The network entity 105-a may insert (e.g., piggyback, multiplex) DCII 220 in the PDSCH 230. The DCII 220 may indicate information about one or more second DCIs 225-b (e.g., one or more instances of second DCI, DCI of one or more other instances of a PDCCH, different than a PDCCH that includes the first DCI 215), such as the second DCI 225-b. By including the DCII 220 in the PDSCH 230, the size of the first DCI 215 may be maintained. For example, there may be no little to no reduction in performance due to an increased DCIAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO29payload (e.g., as compared to including DCII in the first DCI 215). Additionally, or alternatively, a PDSCH 230 that includes the DCII 220 may act as a single reference point for the one or more second DCIs 225 (e.g., future DCIs, accompanying DCIs). For example, the PDSCH 230 may be simpler to decode at the UE 115-a, so the network entity 105-a may be able to insert DCII 220 pertaining to multiple second DCIs 225-b. For example, no linking may be implemented between DCI.

[0094] In some implementations, the UE 115-a may be configured to transmit an uplink acknowledgment 235 after receiving the PDSCH 230 (e.g., responsive to the PDSCH 230). For example, the UE 115-a may transmit the uplink acknowledgment 235 to the network entity 105-a to indicate successful detection or decoding of the PDSCH 230 (e.g., acknowledgment, ACK), or unsuccessful detection or decoding of the PDSCH 230 (e.g., negative acknowledgment, NACK). The uplink acknowledgment 235 may indicate to the network entity 105-a whether the UE 115-a received the PDSCH 230, which may include the DCII 220 (e.g., indicating whether the DCII 220 was received). In contrast, the UE 115-a may be unable to determine a misdetection for a blind decoded DCI that may carry DCII, because the UE 115-a may not know whether such DCI is transmitted by the network entity 105-a. In some cases, DCII 220 that provides a DCI allocation for the one or more second DCIs 225 may be used for future PDCCH (e.g., second DCI 225 in future or following slots).

[0095] In some cases, inserting DCII 220 in a PDSCH 230 may reduce overhead on PDSCH REs (e.g., as compared to piggybacking entire DCIs on the PDSCH 230). For example, as compared to inserting fields of a DCI in a PDSCH 230, inserting DCII 220 (e.g., indicating allocations of second DCI 225-b) may use fewer PDSCH REs.Additionally, or alternatively, a PDSCH coding rate (CR) may be reduced by inserting DCII 220 in the PDSCH 230, rather than inserting an entire DCI in the PDSCH 230. Additionally, or alternatively, the PDSCH block error rate (BLER) may be reduced by inserting DCII 220 in the PDSCH 230, rather than inserting an entire DCI in the PDSCH 230.

[0096] In some cases, inserting DCII 220 in the PDSCH 230 may decrease the payload of the scheduling DCI (e.g., the first DCI 215), as compared to inserting an entire DCI in the PDSCH 230. For example, for inserting entire DCIs on the PDSCH 230, the first DCI 215 may include the expected size for each inserted DCI (e.g.,Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO30piggybacked DCI), because the size of the DCIs may vary. However, the DCII bitsize may be pre-configured (e.g., via RRC signaling) or otherwise known at the UE 115-a. For example, the network entity 105-a may not dynamically indicate the size of the DCII 220, because it may be a pre-configured value. Additionally, or alternatively, an allocation of CCEs for receiving the PDSCH 230 with the inserted DCII 220 may be derivable from parameters associated with the allocation indicated by the first DCI 215 (e.g., the BWP of the CORESET that may be indicated by the first DCI 215). In some cases, multiple DCIIs 220 may be multiplexed (e.g., piggybacked) on the PDSCH 230. The payload of the first DCI 215 may be increased by introducing a field indicating the quantity of DCIIs 220 that are inserted in the PDSCH 230. However, in some examples, the scheduling DCI (e.g., the first DCI 215) may include this field, and other DCI may not be included this field, and may not be increased (e.g., not a per-DCI payload).Additionally, or alternatively, the first DCI 215 (e.g., the scheduling DCI) may be increased (e.g., by a single bit) to indicate whether the PDSCH 230 includes DCII 220. The PDSCH 230 may include a quantity of bits (e.g., constant A bits) that indicate the quantity of DCIIs 220 that are multiplexed on the PDSCH 230.

[0097] In some implementations, a first DCI 215 may indicate whether a PDSCH 230 includes control information that is not related to DCI allocation. For example, a first DCI 215 may indicate that a PDSCH 230 includes one or more fields from other DCI (e.g., special DCI), such as second DCI 225-a. In some implementations, such other DCI may be DCI that is broadcast by the network entity 105-a (e.g., a special broadcasted DCI, DCI intended for reception by multiple UEs 115 including the UE 115-a, non-allocated DCI). Instead of, or in addition to (e.g., duplicating the broadcasted DCI), broadcasting such DCI, the network entity 105-a may piggyback second DCI 225-a on the PDSCH 230. In some examples, a first DCI 215 may indicate that the PDSCH 230 includes one or more portions of DCI grants that may indicate additional information, which may not be related to DCI allocation (e.g., BWP switch information, antenna port information).

[0098] FIG. 3 shows an example of a resource configuration 300 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The resource configuration 300 may implement, or be implemented by, aspects of the wireless communications systems 100 and 200. The techniquesAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO31described herein in the context of the resource configuration 300 may support a network entity 105 to insert DCII 320, second DCI 325 (e.g., unicast field DCI, broadcasted DCI), or both in a PDSCH.

[0099] A UE 115 and a network entity 105 may support communications in accordance with resource blocks 305 (e.g., physical resource blocks (PRBs)). In some implementations, a resource block 305 may correspond to a set of symbol durations (e.g., a slot) in the time domain and a set of subcarriers (e.g., twelve subcarriers) in the frequency domain. However, the described techniques may be performed in accordance with other definitions of a resource block 305 or other groups of allocated resources. Each resource block 305 may include resources (e.g., REs) for a UE 115 and a network entity 105 to transmit or receive messages. In some implementations, a resource block 305 may be divided (e.g., in the time domain, in the frequency domain, or both) into a control region 310 and a data region 330. A control region 310 may include resources (e.g., of a PDCCH) for communication of control information, such as DCI. A data region 330 may include resources (e.g., of a PDSCH) for communication of data or shared information. For example, a first DCI 315 (e.g., an example of first DCI 215) may be received via resources (e.g., PDCCH resources) of a control region 310-a of a resource block 305-a. The first DCI 315 may include a downlink grant that schedules PDSCH resources 335 of a data region 330-a of the resource block 305-a.

[0100] In some implementations, aspects of control information may be multiplexed (e.g., piggybacked) in a physical channel sent in the data region 330-a. For example, DCII 320 (e.g., DCI information associated with one or more second DCIs 325, examples of DCII 220), second DCI 325 itself (e.g., second DCI 325-a and 325-b, examples of second DCI 225-a), or both may be inserted PDSCH resources 335 in the data region 330-a. In some cases, a first DCI 315 may indicate that a PDSCH of the data region 330-a includes DCII 320, such as the DCII 320-a and DCII 320-b. In some examples, the DCI 315 may indicate a quantity of DCIIs 320 that may be piggybacked on the PDSCH (e.g., two DCIIs, corresponding to DCII 320-a and DCII 320-b). In some examples, the DCI 315 may include one or more bits that may indicate the quantity of DCIIs 320 that may be piggybacked in the PDSCH of the data region 330-a. The DCII 320 may indicate information about future or accompanying DCI (e.g., DCI 325-c, anAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO32example of second DCI 225-b), such as second DCI 325 in a different resource block 305.

[0101] Additionally, or alternatively, a network entity 105 may insert (e.g., multiplex, piggyback) control information that may not be related to the DCI allocation in the PDSCH in the data region 330-a (e.g., information different from the DCII 320). For example, a network entity 105 may insert control information intended for a UE 115 in the PDSCH resources 335, which may include duplication of control information transmitted via other signaling, such as DCIs. In some implementations, a network entity may broadcast some DCI (e.g., special DCI) for reception by multiple UEs 115. For example, some broadcasted DCIs may include fields indicating pre-emption, cancellation, and availability indications for a UE 115 (e.g., DCI format 2 1, 2 4, and 2 5). Additionally, or alternatively, some broadcasted DCIs may include closed loop power control (CLPC) information for physical uplink control channels (PUCCH) and physical uplink shared channels (PUSCH), as well as sounding reference signal (SRS) indications for the UE (e.g., DCI format 2 2 and 2 3). Additionally, or alternatively, some broadcasted DCIs may include wakeup signal (WUS) and paging early indication (PEI) information for the UE (e.g., DCI format 2 6 and 2 7). In some cases, a network entity 105 may be unable to determine whether a UE 115 successfully receives and decodes such broadcasted control information.

[0102] In some implementations, instead of, or in addition to, broadcasting such control information, a network entity 105 may insert such control information in unicast fields in the PDSCH resources 335. For example, one or more instances of a PDSCH in PDSCH resources 335 may include second DCI 325-a and the second DCI 325-b, which may be special DCIs (e.g., unicast field DCIs, non-allocated DCIs). Additionally, or alternatively, a network entity 105 may insert (e.g., multiplex, piggyback) one or more parts of one or more DCI grants in a PDSCH. For example, a network entity 105 may insert additional information that may otherwise be indicated as part of a DCI, such as the first DCI 315, the second DCIs 325, or other DCIs, in the PDSCH. For example, the additional information (e.g., additional DCII 320, different DCII 320, additional DCI control information) may include a bandwidth part switch (e.g., BWP indicator field) or a change in an antenna port (e.g., antenna port field).Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO33

[0103] DCII 320 may indicate information (e.g., resource information) about future or accompanying DCI, such as the second DCI 325-c in the resource block 305-c. For example, DCII 320 may include DCI allocation information that indicates location or resource allocation information for one or more second DCIs 325. In some examples, DCII 320 may indicate the resources of the second DCI 325-c, such that the second DCI 325-c may be a non-blind DCI (e.g., received without a blind decoding). In some examples, DCII 320 may indicate a resource block 305 for receiving second DCI 325 (e.g., indicating the resource block 305-c), which may be different from the resource block 305-a (e.g., associated with a different frequency resource from the resource block 305-a, associated with a different time resource from the resource block 305-a, or both).

[0104] In some cases, a DCII 320 may indicate a starting CCE and a duration of CCEs (e.g., one or more CCEs) associated with the second DCI 325-c. A UE 115 may search (e.g., blind decode or detect) for the second DCI 325-c within the duration of CCEs, as defined from the starting CCE (e.g., partial blind decode). In some examples, the DCII 320 may indicate a starting CCE associated with a second DCI 325, such as the second DCI 325-c, and a UE 115 may (e.g., based on an aggregation level (AL)) determine one or more candidate CCEs that may include the second DCI 325-c (e.g., in accordance with a partial or reduced blind decoding). For example, the AL (e.g., 1, 2, 4, 8, 16) may be associated with a quantity of CCEs, counted from a starting CCE, that may include the second DCI 325-c. A UE 115 may perform blind detection and decoding on the indicated CCEs based on the starting CCE and the AL. In some examples, a DCII 320 indicating resources for the second DCI 325-c may indicate that the second DCI 325-c is transmitted by the network entity (e.g., that the second DCI 325-c exists). For example, for a blind detection within a control region 310 a UE 115 may not know if there is any DCI (e.g., whether a DCI is transmitted during the slot, an existence or nonexistence of DCI). Receiving a DCII 320 may indicate a transmission of the second DCI 325-c, even if the DCII 320 may not indicate the specific resources with which to receive the instance of second DCI 325-c. For example, depending on an AL, a UE 115 may still perform detection over multiple CCEs in order to receive the second DCI 325-c, but the UE 115 may know that the network entity 105 has transmitted the second DCI 325-c within the indicated CCEs. In some examples, the possible CCEsAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO34(e.g., hypotheses) may be blindly checked or may be pre-checked (e.g., via demodulation reference signal (DMRS) carrier-to-interference-plus-noise ratio (CINR)). In some examples, although the DCII 320 may not indicate the specific resources for the second DCI 325-c, the UE 115 may perform fewer blind detections to receive the second DCI 325-c, based on the indicated range of resources, than without the DCII 320. In some implementations, indicating a starting CCE may support a smaller DCII 320 than indicating a specific resource for the second DCI 325-c, which may consume fewer PDSCH REs, among other benefits.

[0105] In some examples, a DCII 320 may indicate one or more CORESET identifiers (IDs) associated with one or more CORESETs. The second DCI 325-c may be included in a CORESET of the one or more CORESETs. For example, a UE 115 may be configured to monitor up to a threshold quantity of CORESETs (e.g., three CORESETs), and CORESETs may be grouped together (e.g., three CORESETs) under one CORESET ID based on the threshold quantity. A CORESET ID (e.g., 2 bits in the DCII 320) may be provided in addition to or instead of a resource allocation (e.g., a starting CCE, a starting CCE and a duration of CCEs). Each CORESET may be associated with a configuration, which may include a bitmap, a quantity of CCEs, a mapping between CCEs and resource element groups (REGs), a BWP, or any combination thereof. A CORESET configuration may indicate a quantity of CCEs within the CORESET. The DCII 320 may indicate a CORESET ID, which may provide a network entity 105 flexibility to indicate second DCI 325 from any CORESET in the same resource block 305 as the DCII 320 is received (e.g., resource block 305-a) or in future resource blocks (e.g., resource block 305-c).

[0106] In some implementations, a UE 115 may perform rate matching on a PDSCH (e.g., in the data region 330-a). In some cases, a UE 115 may rate match the PDSCH including the inserted DCII 320. For example, a UE 115 may rate match DCII 320 and any data in a PDSCH. In some other cases, a UE 115 may rate match around DCII 320. For example, a UE 115 may rate match any shared information (e.g., data) in a PDSCH and may not rate match DCII 320 included in the PDSCH. In some cases, DCII 320 may include information for future or accompanying DCI, and may not be relevant to rate matching at the PDSCH that carries the DCII 320. In some other cases, DCII 320 may include some information that may be used for rate matching associatedAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO35with a PDSCH. For example, a PDSCH including (e.g., multiplexed with) a DCII 320 may be scheduled (e.g., by a DCI, by DCII within a different PDSCH), and may be rate matched with different DCI (e.g., not the scheduling DCI, different than first DCI 315) that may be indicated in the DCII 320. However, because the DCII 320 may be included in the PDSCH, the information in the DCII 320 may not be used for rate matching the PDSCH. For example, a DCII 320 that relies on rate matching of a PDSCH may not be inserted into the PDSCH that it may rate match. For example, PDSCHs may be able to rate match around DCI locations indicated by the DCII 320 that may be inserted in the PDSCH after the PDSCH is decoded. In some examples, a UE 115 may be preconfigured (e.g., in accordance with RRC signaling, in accordance with MAC signaling, per UE, per cell) with an indication of whether DCII 320 is inserted in a PDSCH, which may not rely on rate matching, or whether the DCII 320 is sent via PDSCH, which may allow for rate matching. In some examples, a network entity 105 and a UE 115 may coordinate the order of PDSCH reception such that DCIs associated with other (e.g., future, accompanying) PDSCHs may be received via a first PDSCH. For example, DCII 320 may be inserted in a first candidate in a CORESET, and a UE 115 may be configured to decode (e.g., blindly, in accordance with a reduced set of candidates) based on the order of the candidates. Additionally, or alternatively, DCII 320 may be inserted in a first component carrier (CC) for cross carrier scheduling, and a UE 115 may be configured to decode based on the order of CCs, or CC groups (CCGs).Additionally, or alternatively, DCII 320 may be inserted for transmission by a first TRP for multi-TRP (mTRP) scheduling, and a UE 115 may be configured to blind decode based on the order of TRPs (e.g., based on an order of identifiers, such as radio network temporary identifiers (RNTIs), IDs)

[0107] In some implementations, a first DCI 315 may indicate that a PDSCH (e.g., of a data region 330, of a same resource block 305 as the first DCI 315) includes DCII 320 (e.g., piggybacked DCII 320), DCI 325 (e.g., piggybacked DCI 325), or both. For example, information associated with inserting the DCII 320 in the PDSCH may be included in (e.g., added to) fields of the first DCI 315 (e.g., the scheduling DCI). In some cases, a bitsize of the DCII 320 may be known (e.g., configured, pre-configured, indicated, specified, in accordance with a quantity A bits). For example, information included in DCII 320 (e.g., one or more starting CCEs for a DCI grant, closed loopAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO36power control for a PUCCH) may be pre-configured (e.g., in RRC signaling, in MAC signaling) for each UE 115. The size of the fields that the DCII 320 contains may also be known. In some examples, a CCE allocation may be derived from parameters of a first DCI 315 (e.g., a BWP of a CORESET that is indicated by the first DCI 315), which may be a determination similar to those for DCI grants (e.g., DCI formats 1 1 and 0 1). Additionally, or alternatively, CLPC for PUCCH may be derived and known (e.g., in a manner similar to DCI format 2 2). In some cases, the size of the first DCI 315 may be increased with a quantity of bits (e.g., K bits) for a field that indicates the quantity of DCIIs 320 that are multiplexed on the PDSCH. In some examples, the quantity of bits for the field may be configured (e.g., RRC, MAC) or may be set to indicate a range of DCII 320. For example, the quantity of bits may be used to indicate a range of quantities of DCII 320 from 0 to 2 / ;_|DCIIs 320 (e.g., three bits may indicate up to seven DCIIs 320, ‘000’ may indicate no DCII 320). A UE 115 may parse 1 to 2 / ;_|consecutive DCIIs 320 based on the indicated quantity of DCIIs 320, which may each contain Abits, as pre-configured.

[0108] In some other implementations, first DCI 315 may be increased with a single bit that indicates whether DCII 320 is included in a PDSCH. For example, if a PDSCH does include DCII 320, the field may be set to a value of ‘ 1’ . In some examples, a field may be included in the PDSCH to indicate a quantity of DCIIs 320 in the PDSCH. For example, a field within the first of a piggybacked DCII 320 (e.g., DCII 320-a) (e.g., a K-bit field) may indicate the quantity of DCIIs in the PDSCH, from a range of 1 to 2KDCIIs 320. A UE 115 may parse another 1 to 2 / ;_|consecutive DCIIs 320 based on the indicated quantity of DCIIs 320, and each DCII 320 may contain bits (e.g., as preconfigured).

[0109] In some other implementations, a network entity 105 may include DCII 320 in a PDSCH without including an indication in first DCI 315. For example, an inclusion of DCII 320 in a PDSCH may not be triggered by a downlink grant (e.g., of the first DCI 315) that schedules the PDSCH. In some examples, DCII 320 may be included in a PDSCH based on a configuration (e.g., UE 115 may be pre-configured), under some conditions, for some periodic instances of the PDSCH, for all instances of PDSCH, or any combination thereof. For example, a network entity 105 may include DCII 320 in a PDSCH according to some periodicity, which may be known at a UE 115. In someAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO37cases, DCII 320 may be included in a PDSCH with a preconfigured size, a quantity of fields, a type of fields, or any combination thereof (e.g., similar to piggybacking uplink control information (UCI) in PUSCH, or piggybacking configured grant (CG) UCI in CG-PUSCH).

[0110] FIG. 4 shows an example of a process flow 400 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The process flow 400 may implement, or be implemented by, aspects of the wireless communications systems 100 and 200, and the resource configuration 300. For example, the process flow 400 may include one or more network entities 105 and one or more UEs 115, including at least the network entity 105-b and UE 115-b. The techniques described herein may support the network entity 105-b indicating, to the UE 115-b, resources for other instances of DCI.[OHl] In some implementations, at 405, the network entity 105-b may transmit configuration information (e.g., in RRC signaling, in MAC signaling), which may be received by the UE 115-b. The configuration information of 405 may indicate whether DCI resource information (e.g., DCII 220, DCII 320) in a PDSCH (e.g., PDSCH 230) indicates a frequency resource, indicates a time resource, indicates one or more CORESETs, indicates at least one CCE, or a combination thereof. The configuration information of 405 may be communicated before receiving DCI (e.g., a scheduling DCI, first DCI 215, first DCI 315) that is associated with indicating such DCI resource information.

[0112] At 410, the network entity 105-b may transmit first DCI (e.g., scheduling DCI, first DCI 215, first DCI 315) via a PDCCH, which may be received by the UE 115-b. The first DCI may include information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. In some cases, the information included in the first DCI includes an indication of DCI resource information in a PDSCH scheduled by the first DCI. For example, the first DCI may indicate that the PDSCH includes DCII (e.g., DCII 220, DCII 320). In some cases, the PDCCH may be communicated in a first resource block (e.g., resource block 305-a). In some cases, the first DCI may include a single bit that indicates a presence of a DCI resource information in a PDSCH scheduled by the first DCI. In some other cases, the first DCI may include one or more bits that indicate a quantity of instances of secondAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO38DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI. For example, the first DCII may include one or more bits that indicate a quantity of DCIIs inserted in the PDSCH. In some implementations, the information included in the first DCI may include an indication of a presence of second DCI (e.g., second DCI 225-a, second DCIs 325-a and 325-b) in a PDSCH scheduled by the first DCI. For example, the first DCI may indicate whether one or more DCI (e.g., special DCI, broadcasted DCI, unicast field DCI, second DCI 225-a, second DCIs 325-a and 325-b) are inserted in the PDSCH. In some implementations, the information included in the first DCI 315 may include an indication of a presence of additional control information in the PDSCH scheduled by the first DCI 315.

[0113] In some implementations, at 415, the network entity 105-b may transmit DCI resource information (e.g., multiplexed in a PDSCH, in accordance with the indication of DCI resource information of 410), which may be received by the UE 115-b. In some cases, the UE 115-b may receive at least one instance of second DCI (e.g., second DCI 225-b, second DCI 325-c, at 425) in accordance with resources indicated by the DCI resource information in the PDSCH. In some cases, the DCI of 410, the DCI resource information of 415, or both may be communicated in a first resource block, and the DCI resource information in the PDSCH may indicate resources of a second resource block (e.g., resource block 305-c) for receiving second DCI (e.g., at 425). The second resource block may be associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both. In some cases, the DCI resource information in the PDSCH indicates one or more CORESETs for communicating second DCI, as described at 425. In some cases, the DCI resource information in the PDSCH indicates at least one CCE associated with communicating second DCI, as described at 425. For example, the DCI resource information may indicate a starting CCE, a duration of CCEs, or both associated with communicating second DCI, as described at 425. In some cases, the types of resources indicated by the DCI resource information may be indicated in the configuration information (e.g., at 405). In some cases, the first DCI 315 may include a single bit that indicates the presence of the DCI resource information in the PDSCH, and the PDSCH may include one or more bits that indicate a quantity of instances of second DCI in the PDSCH. The PDSCH may include the DCI resource information based on one or moreAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO39periodicities, one or more rules, one or more conditions, or any combination thereof. For example, the DCI resource information may be included in the PDSCH based on some periodicity, may always be included in the PDSCH, or may be included in the PDSCH based on some other condition or rule.

[0114] In some implementations, the PDSCH that includes the DCI resource information of 415 may also include additional control information. In some cases, the UE 115-b may receive the additional control information based on receiving the PDSCH scheduled by the first DCI 315 in accordance with an indication of the additional control information in the PDSCH. In some cases, the additional control information may be non-allocation control information (e.g., a BWP switch indication, an antenna port switch indication).

[0115] In some implementations, at 420, the UE 115-b may transmit an uplink acknowledgment (e.g., ACK, NACK, feedback message, uplink acknowledgment 235), which may be received by the network entity 105-b. The uplink acknowledgment of 420 may indicate successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI. For example, the UE 115-b may transmit an uplink acknowledgment indicating successful reception of a PDSCH scheduled by the first DCI, which may have been received at 415 (e.g., including DCII) or at 425 (e.g., including second DCI). For example, although the uplink acknowledgment is depicted prior to reception of the second DCI at 425, in some examples, the uplink acknowledgment may be transmitted after reception of the second DCI at 425. In other examples, the uplink acknowledgment may be transmitted after reception of the PDSCH at 415.

[0116] At 425, the network entity 105-b may transmit at least one of the one or more instances of second DCI (e.g., second DCI 225, second DCI 325), which may be received by the UE 115-b. The instance(s) of second DCI may be communicated in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI, as described at 410. In some cases, communicating the second DCI of 425 is (e.g., based on the first DCI of 410) in accordance with fewer resources than a blind decoding for the second DCI. In some cases, the network entity 105-b and the UE 115-b may communicate at least one of the instances of second DCI (e.g., second DCI 225-b, second DCI 325-c) in accordanceAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO40with resources indicated by the DCI resource information in the PDSCH, as described at 415. Additionally, or alternatively, the network entity 105-b and the UE 115-b may communicate at least one of the instances of second DCI (e.g., second DCI 225-a, second DCIs 325-a and 325-b) based on communication of PDSCH (e.g., multiplexed in the PDSCH, which may accompany DCI resource information in the PDSCH) scheduled by the first DCI (e.g., in accordance with an indication of the presence of second DCI in the PDSCH). For example, one or more instances of second DCI at 425 may be second DCI that is multiplexed or piggybacked in the PDSCH.

[0117] FIG. 5 shows a block diagram 500 of a device 505 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a transmitter 515, and a communications manager 520. The device 505, or one or more components of the device 505 (e.g., the receiver 510, the transmitter 515, the communications manager 520), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0118] The receiver 510 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource indications for instances of DCI). Information may be passed on to other components of the device 505. The receiver 510 may utilize a single antenna or a set of multiple antennas.

[0119] The transmitter 515 may provide a means for transmitting signals generated by other components of the device 505. For example, the transmitter 515 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource indications for instances of DCI). In some examples, the transmitter 515 may be co-located with a receiver 510 in a transceiver module. The transmitter 515 may utilize a single antenna or a set of multiple antennas.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO41

[0120] The communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be examples of means for performing various aspects of resource indications for instances of DCI as described herein. For example, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0121] In some examples, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a digital signal processor (DSP), a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0122] Additionally, or alternatively, the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 520, the receiver 510, the transmitter 515, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0123] In some examples, the communications manager 520 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 510, the transmitterAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO42515, or both. For example, the communications manager 520 may receive information from the receiver 510, send information to the transmitter 515, or be integrated in combination with the receiver 510, the transmitter 515, or both to obtain information, output information, or perform various other operations as described herein.

[0124] The communications manager 520 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 520 is capable of, configured to, or operable to support a means for receiving first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The communications manager 520 is capable of, configured to, or operable to support a means for receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0125] By including or configuring the communications manager 520 in accordance with examples as described herein, the device 505 (e.g., at least one processor controlling or otherwise coupled with the receiver 510, the transmitter 515, the communications manager 520, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources.

[0126] FIG. 6 shows a block diagram 600 of a device 605 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The device 605 may be an example of aspects of a device 505 or a UE 115 as described herein. The device 605 may include a receiver 610, a transmitter 615, and a communications manager 620. The device 605, or one or more components of the device 605 (e.g., the receiver 610, the transmitter 615, the communications manager 620), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0127] The receiver 610 may provide a means for receiving information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource indications for instances of DCI). Information may be Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO43passed on to other components of the device 605. The receiver 610 may utilize a single antenna or a set of multiple antennas.

[0128] The transmitter 615 may provide a means for transmitting signals generated by other components of the device 605. For example, the transmitter 615 may transmit information such as packets, user data, control information, or any combination thereof associated with various information channels (e.g., control channels, data channels, information channels related to resource indications for instances of DCI). In some examples, the transmitter 615 may be co-located with a receiver 610 in a transceiver module. The transmitter 615 may utilize a single antenna or a set of multiple antennas.

[0129] The device 605, or various components thereof, may be an example of means for performing various aspects of resource indications for instances of DCI as described herein. For example, the communications manager 620 may include a DCI indication component 625 a DCI reception component 630, or any combination thereof. The communications manager 620 may be an example of aspects of a communications manager 520 as described herein. In some examples, the communications manager 620, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 610, the transmitter 615, or both. For example, the communications manager 620 may receive information from the receiver 610, send information to the transmitter 615, or be integrated in combination with the receiver 610, the transmitter 615, or both to obtain information, output information, or perform various other operations as described herein.

[0130] The communications manager 620 may support wireless communications in accordance with examples as disclosed herein. The DCI reception component 630, the DCI indication component 625, or a combination thereof is capable of, configured to, or operable to support a means for receiving first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The DCI reception component 630 is capable of, configured to, or operable to support a means for receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO44

[0131] FIG. 7 shows a block diagram 700 of a communications manager 720 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The communications manager 720 may be an example of aspects of a communications manager 520, a communications manager 620, or both, as described herein. The communications manager 720, or various components thereof, may be an example of means for performing various aspects of resource indications for instances of DCI as described herein. For example, the communications manager 720 may include a DCI indication component 725, a DCI reception component 730, an PDSCH reception component 735, an acknowledgment component 740, a configuration component 745, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses).

[0132] The communications manager 720 may support wireless communications in accordance with examples as disclosed herein. The DCI reception component 730, the DCI indication component 725, or a combination thereof is capable of, configured to, or operable to support a means for receiving first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The DCI reception component 730 is capable of, configured to, or operable to support a means for receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0133] In some examples, receiving the at least one of the one or more instances of second DCI is, based on the information indicating the respective resource of one or more instances of second DCI, in accordance with fewer resources than a blind decoding for the second DCI.

[0134] In some examples, the information included in the first DCI includes an indication of DCI resource information in an PDSCH scheduled by the first DCI, and the PDSCH reception component 735 is capable of, configured to, or operable to support a means for receiving the DCI resource information in the PDSCH based on the indication of DCI resource information, where receiving the at least one of the one orAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO45more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH.

[0135] In some examples, the PDCCH is received in a first resource block, and the DCI resource information in the PDSCH indicates resources of a second resource block for receiving second DCI, the second resource block associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both.

[0136] In some examples, the DCI resource information in the PDSCH indicates one or more CORESETs for receiving second DCI.

[0137] In some examples, the DCI resource information in the PDSCH indicates at least one CCE associated with receiving second DCI.

[0138] In some examples, the first DCI includes a single bit that indicates a presence of the DCI resource information in the PDSCH scheduled by the first DCI and the PDSCH comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0139] In some examples, the first DCI includes one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0140] In some examples, the configuration component 745 is capable of, configured to, or operable to support a means for receiving, before receiving the first DCI, configuration information indicating whether the DCI resource information indicates a frequency resource, indicates a time resource, indicates one or more CORESETs, indicates at least one CCE, or a combination thereof.

[0141] In some examples, the PDSCH includes the DCI resource information based on one or more periodicities, one or more rules, one or more conditions, or any combination thereof.

[0142] In some examples, the information included in the first DCI includes an indication of a presence of second DCI in an PDSCH scheduled by the first DCI. In some examples, receiving the at least one of the one or more instances of second DCI isAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO46based on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.

[0143] In some examples, the information included in the first DCI includes an indication of a presence of additional control information in a PDSCH scheduled by the first DCI. In some examples, receiving the additional control information is based on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the additional control information in the PDSCH. In some examples, the additional control information is non-allocation control information

[0144] In some examples, the acknowledgment component 740 is capable of, configured to, or operable to support a means for transmitting an uplink acknowledgment that indicates successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI.

[0145] FIG. 8 shows a diagram of a system 800 including a device 805 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The device 805 may be an example of or include components of a device 505, a device 605, or a UE 115 as described herein. The device 805 may communicate (e.g., wirelessly) with one or more other devices (e.g., network entities 105, UEs 115, or a combination thereof). The device 805 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, such as a communications manager 820, an input / output (VO) controller, such as an I / O controller 810, a transceiver 815, one or more antennas 825, at least one memory 830, code 835, and at least one processor 840. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 845).

[0146] The I / O controller 810 may manage input and output signals for the device 805. The I / O controller 810 may also manage peripherals not integrated into the device 805. In some cases, the I / O controller 810 may represent a physical connection or port to an external peripheral. In some cases, the VO controller 810 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS / 2®, UNIX®, LINUX®, or another known operating system. Additionally, or alternatively, the VO controller 810 may represent or interact with a modem, a keyboard, a mouse, a Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO47touchscreen, or a similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as the at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0147] In some cases, the device 805 may include a single antenna. However, in some other cases, the device 805 may have more than one antenna, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The transceiver 815 may communicate bi-directionally via the one or more antennas 825 using wired or wireless links as described herein. For example, the transceiver 815 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 815 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 825 for transmission, and to demodulate packets received from the one or more antennas 825. The transceiver 815, or the transceiver 815 and one or more antennas 825, may be an example of a transmitter 515, a transmitter 615, a receiver 510, a receiver 610, or any combination thereof or component thereof, as described herein.

[0148] The at least one memory 830 may include random access memory (RAM) and read-only memory (ROM). The at least one memory 830 may store computer-readable, computer-executable, or processor-executable code, such as the code 835. The code 835 may include instructions that, when executed by the at least one processor 840, cause the device 805 to perform various functions described herein. The code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 835 may not be directly executable by the at least one processor 840 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 830 may include, among other things, a basic I / O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

[0149] The at least one processor 840 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processorsAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO48(DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into the at least one processor 840. The at least one processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., the at least one memory 830) to cause the device 805 to perform various functions (e.g., functions or tasks supporting resource indications for instances of DCI). For example, the device 805 or a component of the device 805 may include at least one processor 840 and at least one memory 830 coupled with or to the at least one processor 840, the at least one processor 840 and the at least one memory 830 configured to perform various functions described herein.

[0150] In some examples, the at least one processor 840 may include multiple processors and the at least one memory 830 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions described herein. In some examples, the at least one processor 840 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 840) and memory circuitry (which may include the at least one memory 830)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 840 or a processing system including the at least one processor 840 may be configured to, configurable to, or operable to cause the device 805 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code 835 (e.g., processor-executable code) stored in the at least one memory 830 or otherwise, to perform one or more of the functions described herein.

[0151] The communications manager 820 may support wireless communications in accordance with examples as disclosed herein. For example, the communicationsAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO49manager 820 is capable of, configured to, or operable to support a means for receiving first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The communications manager 820 is capable of, configured to, or operable to support a means for receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0152] By including or configuring the communications manager 820 in accordance with examples as described herein, the device 805 may support techniques for communication reliability, improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, and longer battery life.

[0153] In some examples, the communications manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the transceiver 815, the one or more antennas 825, or any combination thereof. Although the communications manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 820 may be supported by or performed by the at least one processor 840, the at least one memory 830, the code 835, or any combination thereof. For example, the code 835 may include instructions executable by the at least one processor 840 to cause the device 805 to perform various aspects of resource indications for instances of DCI as described herein, or the at least one processor 840 and the at least one memory 830 may be otherwise configured to, individually or collectively, perform or support such operations.

[0154] FIG. 9 shows a block diagram 900 of a device 905 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The device 905 may be an example of aspects of a network entity 105 as described herein. The device 905 may include a receiver 910, a transmitter 915, and a communications manager 920. The device 905, or one or more components of the device 905 (e.g., the receiver 910, the transmitter 915, the communications manager 920), may include at least one processor, which may be coupled with at least one memory, to, individually or collectively, support or enable the described techniques.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO50Each of these components may be in communication with one another (e.g., via one or more buses).

[0155] The receiver 910 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 905. In some examples, the receiver 910 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 910 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0156] The transmitter 915 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 905. For example, the transmitter 915 may output information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 915 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 915 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 915 and the receiver 910 may be co-located in a transceiver, which may include or be coupled with a modem.

[0157] The communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be examples of means for performing various aspects of resource indications for instances of DCI as described herein. For example, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be capable of performing one or more of the functions described herein.

[0158] In some examples, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO51hardware (e.g., in communications management circuitry). The hardware may include at least one of a processor, a DSP, a CPU, an ASIC, an FPGA or other programmable logic device, a microcontroller, discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure. In some examples, at least one processor and at least one memory coupled with the at least one processor may be configured to perform one or more of the functions described herein (e.g., by one or more processors, individually or collectively, executing instructions stored in the at least one memory).

[0159] Additionally, or alternatively, the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by at least one processor (e.g., referred to as a processor-executable code). If implemented in code executed by at least one processor, the functions of the communications manager 920, the receiver 910, the transmitter 915, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a CPU, an ASIC, an FPGA, a microcontroller, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting, individually or collectively, a means for performing the functions described in the present disclosure).

[0160] In some examples, the communications manager 920 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 910, the transmitter 915, or both. For example, the communications manager 920 may receive information from the receiver 910, send information to the transmitter 915, or be integrated in combination with the receiver 910, the transmitter 915, or both to obtain information, output information, or perform various other operations as described herein.

[0161] The communications manager 920 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 920 is capable of, configured to, or operable to support a means for transmitting first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances ofAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO52second DCI. The communications manager 920 is capable of, configured to, or operable to support a means for transmitting at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0162] By including or configuring the communications manager 920 in accordance with examples as described herein, the device 905 (e.g., at least one processor controlling or otherwise coupled with the receiver 910, the transmitter 915, the communications manager 920, or a combination thereof) may support techniques for reduced processing, reduced power consumption, and more efficient utilization of communication resources.

[0163] FIG. 10 shows a block diagram 1000 of a device 1005 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The device 1005 may be an example of aspects of a device 905 or a network entity 105 as described herein. The device 1005 may include a receiver 1010, a transmitter 1015, and a communications manager 1020. The device 1005, or one or more components of the device 1005 (e.g., the receiver 1010, the transmitter 1015, the communications manager 1020), may include at least one processor, which may be coupled with at least one memory, to support the described techniques. Each of these components may be in communication with one another (e.g., via one or more buses).

[0164] The receiver 1010 may provide a means for obtaining (e.g., receiving, determining, identifying) information such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). Information may be passed on to other components of the device 1005. In some examples, the receiver 1010 may support obtaining information by receiving signals via one or more antennas. Additionally, or alternatively, the receiver 1010 may support obtaining information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0165] The transmitter 1015 may provide a means for outputting (e.g., transmitting, providing, conveying, sending) information generated by other components of the device 1005. For example, the transmitter 1015 may output information such as userAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO53data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). In some examples, the transmitter 1015 may support outputting information by transmitting signals via one or more antennas. Additionally, or alternatively, the transmitter 1015 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, the transmitter 1015 and the receiver 1010 may be co-located in a transceiver, which may include or be coupled with a modem.

[0166] The device 1005, or various components thereof, may be an example of means for performing various aspects of resource indications for instances of DCI as described herein. For example, the communications manager 1020 may include a DCI indication component 1025 a DCI transmission component 1030, or any combination thereof. The communications manager 1020 may be an example of aspects of a communications manager 920 as described herein. In some examples, the communications manager 1020, or various components thereof, may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the receiver 1010, the transmitter 1015, or both. For example, the communications manager 1020 may receive information from the receiver 1010, send information to the transmitter 1015, or be integrated in combination with the receiver 1010, the transmitter 1015, or both to obtain information, output information, or perform various other operations as described herein.

[0167] The communications manager 1020 may support wireless communications in accordance with examples as disclosed herein. The DCI transmission component 1030, the DCI indication component 1025, or a combination thereof is capable of, configured to, or operable to support a means for transmitting first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The DCI transmission component 1030 is capable of, configured to, or operable to support a means for transmitting at least one of the one or more instances of second DCI inAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO54accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0168] FIG. 11 shows a block diagram 1100 of a communications manager 1120 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The communications manager 1120 may be an example of aspects of a communications manager 920, a communications manager 1020, or both, as described herein. The communications manager 1120, or various components thereof, may be an example of means for performing various aspects of resource indications for instances of DCI as described herein. For example, the communications manager 1120 may include a DCI indication component 1125, a DCI transmission component 1130, an PDSCH transmission component 1135, an acknowledgment component 1140, a configuration component 1145, or any combination thereof. Each of these components, or components or subcomponents thereof (e.g., one or more processors, one or more memories), may communicate, directly or indirectly, with one another (e.g., via one or more buses). The communications may include communications within a protocol layer of a protocol stack, communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack, within a device, component, or virtualized component associated with a network entity 105, between devices, components, or virtualized components associated with a network entity 105), or any combination thereof.

[0169] The communications manager 1120 may support wireless communications in accordance with examples as disclosed herein. The DCI transmission component 1130, the DCI indication component 1125, or a combination thereof is capable of, configured to, or operable to support a means for transmitting first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The DCI transmission component 1130 is capable of, configured to, or operable to support a means for transmitting at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO55

[0170] In some examples, transmitting the at least one of the one or more instances of second DCI is, based on the information indicating the respective resource of one or more instances of second DCI, in accordance with fewer resources than a blind decoding for the second DCI.

[0171] In some examples, the information included in the first DCI includes an indication of DCI resource information in an PDSCH scheduled by the first DCI, and the PDSCH transmission component 1135 is capable of, configured to, or operable to support a means for transmitting the DCI resource information in the PDSCH based on the indication of DCI resource information, where transmitting the at least one of the one or more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH.

[0172] In some examples, the PDCCH is transmitted in a first resource block, and the DCI resource information in the PDSCH indicates resources of a second resource block for transmitting second DCI, the second resource block associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both.

[0173] In some examples, the DCI resource information in the PDSCH indicates one or more CORESETs for receiving second DCI.

[0174] In some examples, the DCI resource information in the PDSCH indicates at least one CCE associated with receiving second DCI.

[0175] In some examples, the first DCI includes a single bit that indicates a presence of the DCI resource information in the PDSCH scheduled by the first DCI and the PDSCH comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0176] In some examples, the first DCI includes one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0177] In some examples, the configuration component 1145 is capable of, configured to, or operable to support a means for receiving, before receiving the first DCI, configuration information indicating whether the DCI resource informationAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO56indicates a frequency resource, indicates a time resource, indicates one or more CORESETs, indicates at least one CCE, or a combination thereof.

[0178] In some examples, the PDSCH includes the DCI resource information based on one or more periodicities, one or more rules, one or more conditions, or any combination thereof.

[0179] In some examples, the information included in the first DCI includes an indication of a presence of second DCI in an PDSCH scheduled by the first DCI. In some examples, transmitting the at least one of the one or more instances of second DCI is based on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.

[0180] In some examples, the information included in the first DCI includes an indication of a presence of additional control information in a PDSCH scheduled by the first DCI. In some examples, transmitting the additional control information is based on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the additional control information in the PDSCH. In some examples, the additional control information is non-allocation control information

[0181] In some examples, the acknowledgment component 1140 is capable of, configured to, or operable to support a means for receiving an uplink acknowledgment that indicates successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI.

[0182] FIG. 12 shows a diagram of a system 1200 including a device 1205 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The device 1205 may be an example of or include components of a device 905, a device 1005, or a network entity 105 as described herein. The device 1205 may communicate with other network devices or network equipment such as one or more of the network entities 105, UEs 115, or any combination thereof. The communications may include communications over one or more wired interfaces, over one or more wireless interfaces, or any combination thereof. The device 1205 may include components that support outputting and obtaining communications, such as a communications manager 1220, a transceiver 1210, one or more antennas 1215, at least one memory 1225, code 1230, and at least one processor 1235. These components mayAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO57be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more buses (e.g., a bus 1240).

[0183] The transceiver 1210 may support bi-directional communications via wired links, wireless links, or both as described herein. In some examples, the transceiver 1210 may include a wired transceiver and may communicate bi-directionally with another wired transceiver. Additionally, or alternatively, in some examples, the transceiver 1210 may include a wireless transceiver and may communicate bidirectionally with another wireless transceiver. In some examples, the device 1205 may include one or more antennas 1215, which may be capable of transmitting or receiving wireless transmissions (e.g., concurrently). The transceiver 1210 may also include a modem to modulate signals, to provide the modulated signals for transmission (e.g., by one or more antennas 1215, by a wired transmitter), to receive modulated signals (e.g., from one or more antennas 1215, from a wired receiver), and to demodulate signals. In some implementations, the transceiver 1210 may include one or more interfaces, such as one or more interfaces coupled with the one or more antennas 1215 that are configured to support various receiving or obtaining operations, or one or more interfaces coupled with the one or more antennas 1215 that are configured to support various transmitting or outputting operations, or a combination thereof. In some implementations, the transceiver 1210 may include or be configured for coupling with one or more processors or one or more memory components that are operable to perform or support operations based on received or obtained information or signals, or to generate information or other signals for transmission or other outputting, or any combination thereof. In some implementations, the transceiver 1210, or the transceiver 1210 and the one or more antennas 1215, or the transceiver 1210 and the one or more antennas 1215 and one or more processors or one or more memory components (e.g., the at least one processor 1235, the at least one memory 1225, or both), may be included in a chip or chip assembly that is installed in the device 1205. In some examples, the transceiver 1210 may be operable to support communications via one or more communications links (e.g., communication link(s) 125, backhaul communication link(s) 120, a midhaul communication link 162, a fronthaul communication link 168).Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO58

[0184] The at least one memory 1225 may include RAM, ROM, or any combination thereof. The at least one memory 1225 may store computer-readable, computerexecutable, or processor-executable code, such as the code 1230. The code 1230 may include instructions that, when executed by one or more of the at least one processor 1235, cause the device 1205 to perform various functions described herein. The code 1230 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, the code 1230 may not be directly executable by a processor of the at least one processor 1235 but may cause a computer (e.g., when compiled and executed) to perform functions described herein. In some cases, the at least one memory 1225 may include, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices. In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories which may, individually or collectively, be configured to perform various functions herein (for example, as part of a processing system).

[0185] The at least one processor 1235 may include one or more intelligent hardware devices (e.g., one or more general-purpose processors, one or more DSPs, one or more CPUs, one or more graphics processing units (GPUs), one or more neural processing units (NPUs) (also referred to as neural network processors or deep learning processors (DLPs)), one or more microcontrollers, one or more ASICs, one or more FPGAs, one or more programmable logic devices, discrete gate or transistor logic, one or more discrete hardware components, or any combination thereof). In some cases, the at least one processor 1235 may be configured to operate a memory array using a memory controller. In some other cases, a memory controller may be integrated into one or more of the at least one processor 1235. The at least one processor 1235 may be configured to execute computer-readable instructions stored in a memory (e.g., one or more of the at least one memory 1225) to cause the device 1205 to perform various functions (e.g., functions or tasks supporting resource indications for instances of DCI). For example, the device 1205 or a component of the device 1205 may include at least one processor 1235 and at least one memory 1225 coupled with one or more of the at least one processor 1235, the at least one processor 1235 and the at least one memoryAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO591225 configured to perform various functions described herein. The at least one processor 1235 may be an example of a cloud-computing platform (e.g., one or more physical nodes and supporting software such as operating systems, virtual machines, or container instances) that may host the functions (e.g., by executing code 1230) to perform the functions of the device 1205. The at least one processor 1235 may be any one or more suitable processors capable of executing scripts or instructions of one or more software programs stored in the device 1205 (such as within one or more of the at least one memory 1225).

[0186] In some examples, the at least one processor 1235 may include multiple processors and the at least one memory 1225 may include multiple memories. One or more of the multiple processors may be coupled with one or more of the multiple memories, which may, individually or collectively, be configured to perform various functions herein. In some examples, the at least one processor 1235 may be a component of a processing system, which may refer to a system (such as a series) of machines, circuitry (including, for example, one or both of processor circuitry (which may include the at least one processor 1235) and memory circuitry (which may include the at least one memory 1225)), or components, that receives or obtains inputs and processes the inputs to produce, generate, or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. For example, the at least one processor 1235 or a processing system including the at least one processor 1235 may be configured to, configurable to, or operable to cause the device 1205 to perform one or more of the functions described herein. Further, as described herein, being “configured to,” being “configurable to,” and being “operable to” may be used interchangeably and may be associated with a capability, when executing code stored in the at least one memory 1225 or otherwise, to perform one or more of the functions described herein.

[0187] In some examples, a bus 1240 may support communications of (e.g., within) a protocol layer of a protocol stack. In some examples, a bus 1240 may support communications associated with a logical channel of a protocol stack (e.g., between protocol layers of a protocol stack), which may include communications performed within a component of the device 1205, or between different components of the device 1205 that may be co-located or located in different locations (e.g., where the deviceAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO601205 may refer to a system in which one or more of the communications manager 1220, the transceiver 1210, the at least one memory 1225, the code 1230, and the at least one processor 1235 may be located in one of the different components or divided between different components).

[0188] In some examples, the communications manager 1220 may manage aspects of communications with a core network 130 (e.g., via one or more wired or wireless backhaul links). For example, the communications manager 1220 may manage the transfer of data communications for client devices, such as one or more UEs 115. In some examples, the communications manager 1220 may manage communications with one or more other network entities 105, and may include a controller or scheduler for controlling communications with UEs 115 (e.g., in cooperation with the one or more other network devices). In some examples, the communications manager 1220 may support an X2 interface within an LTE / LTE-A wireless communications network technology to provide communication between network entities 105.

[0189] The communications manager 1220 may support wireless communications in accordance with examples as disclosed herein. For example, the communications manager 1220 is capable of, configured to, or operable to support a means for transmitting first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The communications manager 1220 is capable of, configured to, or operable to support a means for transmitting at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0190] By including or configuring the communications manager 1220 in accordance with examples as described herein, the device 1205 may support techniques for improved user experience related to reduced processing, reduced power consumption, more efficient utilization of communication resources, improved coordination between devices, longer battery life, and improved utilization of processing capability.

[0191] In some examples, the communications manager 1220 may be configured to perform various operations (e.g., receiving, obtaining, monitoring, outputting, transmitting) using or otherwise in cooperation with the transceiver 1210, the one orAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO61more antennas 1215 (e.g., where applicable), or any combination thereof. Although the communications manager 1220 is illustrated as a separate component, in some examples, one or more functions described with reference to the communications manager 1220 may be supported by or performed by the transceiver 1210, one or more of the at least one processor 1235, one or more of the at least one memory 1225, the code 1230, or any combination thereof (for example, by a processing system including at least a portion of the at least one processor 1235, the at least one memory 1225, the code 1230, or any combination thereof). For example, the code 1230 may include instructions executable by one or more of the at least one processor 1235 to cause the device 1205 to perform various aspects of resource indications for instances of DCI as described herein, or the at least one processor 1235 and the at least one memory 1225 may be otherwise configured to, individually or collectively, perform or support such operations.

[0192] FIG. 13 shows a flowchart illustrating a method 1300 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The operations of the method 1300 may be implemented by a UE or its components as described herein. For example, the operations of the method 1300 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0193] At 1305, the method may include receiving first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The operations of 1305 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed by a DCI indication component 725 as described with reference to FIG. 7.

[0194] At 1310, the method may include receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI. The operations of 1310 may be performed in accordance with examples as disclosed herein. In someAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO62examples, aspects of the operations of 1310 may be performed by a DCI reception component 730 as described with reference to FIG. 7.

[0195] FIG. 14 shows a flowchart illustrating a method 1400 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The operations of the method 1400 may be implemented by a UE or its components as described herein. For example, the operations of the method 1400 may be performed by a UE 115 as described with reference to FIGs. 1 through 8. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the described functions. Additionally, or alternatively, the UE may perform aspects of the described functions using special-purpose hardware.

[0196] At 1405, the method may include receiving first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI, wherein the information included in the first DCI comprises an indication of DCI resource information in a PDSCH scheduled by the first DCI. The operations of 1405 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1405 may be performed by a DCI indication component 725 as described with reference to FIG. 7.

[0197] At 1410, the method may include receiving the DCI resource information in the PDSCH based on the indication of DCI resource information, where receiving the at least one of the one or more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH. The operations of 1410 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1410 may be performed by an PDSCH reception component 735 as described with reference to FIG. 7.

[0198] At 1415, the method may include receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI. The operations of 1415 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1415 may be performed by a DCI reception component 730 as described with reference to FIG. 7.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO63

[0199] FIG. 15 shows a flowchart illustrating a method 1500 that supports resource indications for instances of DCI in accordance with one or more aspects of the present disclosure. The operations of the method 1500 may be implemented by a network entity or its components as described herein. For example, the operations of the method 1500 may be performed by a network entity as described with reference to FIGs. 1 through 4 and 9 through 12. In some examples, a network entity may execute a set of instructions to control the functional elements of the network entity to perform the described functions. Additionally, or alternatively, the network entity may perform aspects of the described functions using special-purpose hardware.

[0200] At 1505, the method may include transmitting first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI. The operations of 1505 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1505 may be performed by a DCI indication component 1125 as described with reference to FIG. 11.

[0201] At 1510, the method may include transmitting at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI. The operations of 1510 may be performed in accordance with examples as disclosed herein. In some examples, aspects of the operations of 1510 may be performed by a DCI transmission component 1130 as described with reference to FIG. 11.

[0202] The following provides an overview of aspects of the present disclosure:

[0203] Aspect 1 : A method for wireless communications at a UE, comprising: receiving first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI; and receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0204] Aspect 2: The method of aspect 1, wherein the information included in the first DCI comprises an indication of DCI resource information in an PDSCH scheduled by the first DCI, the method further comprising: receiving the DCI resource informationAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO64in the PDSCH based at least in part on the indication of DCI resource information, wherein receiving the at least one of the one or more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH.

[0205] Aspect 3 : The method of aspect 2, wherein the PDCCH is received in a first resource block, and the DCI resource information in the PDSCH indicates resources of a second resource block for receiving second DCI, the second resource block associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both.

[0206] Aspect 4: The method of any of aspects 2 through 3, wherein the DCI resource information in the PDSCH indicates one or more CORESETs for receiving second DCI.

[0207] Aspect 5: The method of any of aspects 2 through 3, wherein the DCI resource information in the PDSCH indicates at least one CCE associated with receiving second DCI.

[0208] Aspect 6: The method of any of aspects 2 through 5, wherein the first DCI comprises a single bit that indicates a presence of the DCI resource information in the PDSCH scheduled by the first DCI and the PDSCH comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0209] Aspect 7: The method of any of aspects 2 through 5, wherein the first DCI comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0210] Aspect 8: The method of any of aspects 2 through 7, further comprising: receiving, before receiving the first DCI, configuration information indicating whether the DCI resource information indicates a frequency resource, indicates a time resource, indicates one or more CORESETs, indicates at least one CCE, or a combination thereof.

[0211] Aspect 9: The method of any of aspects 2 through 8, wherein the PDSCH includes the DCI resource information based at least in part on one or more periodicities, one or more rules, one or more conditions, or any combination thereof.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO65

[0212] Aspect 10: The method of aspect 1, wherein the information included in the first DCI comprises an indication of a presence of second DCI in an PDSCH scheduled by the first DCI, and receiving the at least one of the one or more instances of second DCI is based at least in part on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.

[0213] Aspect 11 : The method of any of aspects 1 through 10, wherein the information included in the first DCI comprises an indication of a presence of additional control information in an PDSCH scheduled by the first DCI, and receiving the additional control information is based at least in part on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the additional control information in the PDSCH and the additional control information is non-allocation control information.

[0214] Aspect 12: The method of any of aspects 1 through 11, further comprising: transmitting an uplink acknowledgment that indicates successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI.

[0215] Aspect 13 : A method for wireless communications at a network entity, comprising: transmitting first DCI via a PDCCH, the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI; and transmitting at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

[0216] Aspect 14: The method of aspect 13, wherein the information included in the first DCI comprises an indication of DCI resource information in an PDSCH scheduled by the first DCI, the method further comprising: transmitting the DCI resource information in the PDSCH based at least in part on the indication of DCI resource information, wherein transmitting the at least one of the one or more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH.

[0217] Aspect 15: The method of aspect 14, wherein the PDCCH is transmitted in a first resource block, and the DCI resource information in the PDSCH indicatesAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO66resources of a second resource block for transmitting second DCI, the second resource block associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both.

[0218] Aspect 16: The method of any of aspects 14 through 15, wherein the DCI resource information in the PDSCH indicates one or more CORESETs for receiving second DCI.

[0219] Aspect 17: The method of any of aspects 14 through 15, wherein the DCI resource information in the PDSCH indicates at least one CCE associated with receiving second DCI.

[0220] Aspect 18: The method of any of aspects 14 through 17, wherein the first DCI comprises a single bit that indicates a presence of the DCI resource information in the PDSCH scheduled by the first DCI and the PDSCH comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0221] Aspect 19: The method of any of aspects 14 through 17, wherein the first DCI comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

[0222] Aspect 20: The method of any of aspects 14 through 19, further comprising: receiving, before receiving the first DCI, configuration information indicating whether the DCI resource information indicates a frequency resource, indicates a time resource, indicates one or more CORESETs, indicates at least one CCE, or a combination thereof.

[0223] Aspect 21 : The method of any of aspects 14 through 20, wherein the PDSCH includes the DCI resource information based at least in part on one or more periodicities, one or more rules, one or more conditions, or any combination thereof.

[0224] Aspect 22: The method of aspect 13, wherein the information included in the first DCI comprises an indication of a presence of second DCI in an PDSCH scheduled by the first DCI, and transmitting the at least one of the one or more instances of second DCI is based at least in part on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO67

[0225] Aspect 23: The method of any of aspects 13 through 22, wherein the information included in the first DCI comprises an indication of a presence of additional control information in an PDSCH scheduled by the first DCI, and transmitting the additional control information is based at least in part on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the additional control information in the PDSCH and the additional control information is non-allocation control information.

[0226] Aspect 24: The method of any of aspects 13 through 23, further comprising: receiving an uplink acknowledgment that indicates successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI.

[0227] Aspect 25: A UE for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to perform a method of any of aspects 1 through 12.

[0228] Aspect 26: A UE for wireless communications, comprising at least one means for performing a method of any of aspects 1 through 12.

[0229] Aspect 27: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 1 through 12.

[0230] Aspect 28: A network entity for wireless communications, comprising one or more memories storing processor-executable code, and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to perform a method of any of aspects 13 through 24.

[0231] Aspect 29: A network entity for wireless communications, comprising at least one means for performing a method of any of aspects 13 through 24.

[0232] Aspect 30: A non-transitory computer-readable medium storing code for wireless communications, the code comprising instructions executable by one or more processors to perform a method of any of aspects 13 through 24.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO68

[0233] It should be noted that the methods described herein describe possible implementations. The operations and the steps may be rearranged or otherwise modified and other implementations are possible. Further, aspects from two or more of the methods may be combined.

[0234] Although aspects of an LTE, LTE-A, LTE-A Pro, or NR system may be described for purposes of example, and LTE, LTE-A, LTE-A Pro, or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applicable to various other wireless communications systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, as well as other systems and radio technologies not explicitly mentioned herein.

[0235] Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0236] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general-purpose processor, a DSP, an ASIC, a CPU, a graphics processing unit (GPU), a neural processing unit (NPU), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor but, in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration). Any functions or operations described herein as being capable of being performed by a processor may be performed by multiple processors that, individually or collectively, are capable of performing the described functions or operations.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO69

[0237] The functions described herein may be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions may be stored as or transmitted using one or more instructions or code of a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.

[0238] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one location to another. A non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc. Disks may reproduce data magnetically, and discs may reproduce data optically using lasers.Combinations of the above are also included within the scope of computer-readable media. Any functions or operations described herein as being capable of beingAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO70performed by a memory may be performed by multiple memories that, individually or collectively, are capable of performing the described functions or operations.

[0239] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on.”

[0240] As used herein, including in the claims, the article “a” before a noun is open-ended and understood to refer to “at least one” of those nouns or “one or more” of those nouns. Thus, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” may be interchangeable. For example, if a claim recites “a component” that performs one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “a component” having characteristics or performing functions may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent reference to a component introduced with the article “a” using the terms “the” or “said” may refer to any or all of the one or more components. For example, a component introduced with the article “a” may be understood to mean “one or more components,” and referring to “the component” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.” Similarly, subsequent reference to a component introduced as “one or more components” using the terms “the” or “said” may refer to any or all of the one or more components. For example, referring to “the one or more components” subsequently in the claims may be understood to be equivalent to referring to “at least one of the one or more components.”

[0241] The term “determine” or “determining” encompasses a variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database, or another dataAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO71structure), ascertaining, and the like. Also, “determining” can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), and the like. Also, “determining” can include resolving, obtaining, selecting, choosing, establishing, and other such similar actions.

[0242] In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label or other subsequent reference label.

[0243] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some figures, known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

[0244] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.Attorney Docket No. PY2983IL.WO (114958.6159)

Claims

Qualcomm Ref. No. 2500778WO72CLAIMSWhat is claimed is:

1. A user equipment (UE), comprising:one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the UE to:receive first downlink control information (DCI) via a physical downlink control channel (PDCCH), the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI; andreceive at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

2. The UE of claim 1, wherein the information included in the first DCI comprises an indication of DCI resource information in a physical downlink shared channel (PDSCH) scheduled by the first DCI, and the one or more processors are individually or collectively further operable to execute the code to cause the UE to:receive the DCI resource information in the PDSCH based at least in part on the indication of DCI resource information, wherein receiving the at least one of the one or more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH.

3. The UE of claim 2, wherein the PDCCH is received in a first resource block, and the DCI resource information in the PDSCH indicates resources of a second resource block for receiving second DCI, the second resource block associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both.

4. The UE of claim 2, wherein:the DCI resource information in the PDSCH indicates one or more control resource sets for receiving second DCI.

5. The UE of claim 2, wherein:Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO73the DCI resource information in the PDSCH indicates at least one control channel element associated with receiving second DCI.

6. The UE of claim 2, wherein the first DCI comprises a single bit that indicates a presence of the DCI resource information in the PDSCH scheduled by the first DCI and wherein the PDSCH comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

7. The UE of claim 2, wherein the first DCI comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

8. The UE of claim 2, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:receive, before receiving the first DCI, configuration information indicating whether the DCI resource information indicates a frequency resource, indicates a time resource, indicates one or more control resource sets, indicates at least one control channel element, or a combination thereof.

9. The UE of claim 2, wherein the PDSCH includes the DCI resource information based at least in part on one or more periodicities, one or more rules, one or more conditions, or any combination thereof.

10. The UE of claim 1, wherein:the information included in the first DCI comprises an indication of a presence of second DCI in a physical downlink shared channel (PDSCH) scheduled by the first DCI, andreceiving the at least one of the one or more instances of second DCI is based at least in part on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.

11. The UE of claim 1, wherein:Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO74the information included in the first DCI comprises an indication of a presence of additional control information in a physical downlink shared channel (PDSCH) scheduled by the first DCI, andreceiving the additional control information is based at least in part on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the additional control information in the PDSCH and wherein the additional control information is non-allocation control information.

12. The UE of claim 1, wherein the one or more processors are individually or collectively further operable to execute the code to cause the UE to:transmit an uplink acknowledgment that indicates successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI.

13. A network entity, compri sing :one or more memories storing processor-executable code; and one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the network entity to:transmit first downlink control information (DCI) via a physical downlink control channel (PDCCH), the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI; andtransmit at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

14. The network entity of claim 13, wherein the information included in the first DCI comprises an indication of DCI resource information in a physical downlink shared channel (PDSCH) scheduled by the first DCI, and the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:transmit the DCI resource information in the PDSCH based at least in part on the indication of DCI resource information, wherein transmitting the at least oneAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO75of the one or more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH.

15. The network entity of claim 14, wherein the PDCCH is transmitted in a first resource block, and the DCI resource information in the PDSCH indicates resources of a second resource block for transmitting second DCI, the second resource block associated with a frequency resource different from the first resource block, associated with a time resource different from the first resource block, or both.

16. The network entity of claim 14, wherein:the DCI resource information in the PDSCH indicates one or more control resource sets for receiving second DCI.

17. The network entity of claim 14, wherein:the DCI resource information in the PDSCH indicates at least one control channel element associated with receiving second DCI.

18. The network entity of claim 14, wherein the first DCI comprises a single bit that indicates a presence of the DCI resource information in the PDSCH scheduled by the first DCI and wherein the PDSCH comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

19. The network entity of claim 14, wherein the first DCI comprises one or more bits that indicate a quantity of instances of second DCI that are indicated by the DCI resource information in the PDSCH scheduled by the first DCI.

20. The network entity of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:receive, before receiving the first DCI, configuration information indicating whether the DCI resource information indicates a frequency resource, indicates a time resource, indicates one or more control resource sets, indicates at least one control channel element, or a combination thereof.Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO7621. The network entity of claim 14, wherein the PDSCH includes the DCI resource information based at least in part on one or more periodicities, one or more rules, one or more conditions, or any combination thereof.

22. The network entity of claim 13, wherein:the information included in the first DCI comprises an indication of a presence of second DCI in a physical downlink shared channel (PDSCH) scheduled by the first DCI, andtransmitting the at least one of the one or more instances of second DCI is based at least in part on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.

23. The network entity of claim 13, wherein:the information included in the first DCI comprises an indication of a presence of additional control information in a physical downlink shared channel (PDSCH) scheduled by the first DCI, andtransmitting the additional control information is based at least in part on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the additional control information in the PDSCH and wherein the additional control information is non-allocation control information.

24. The network entity of claim 13, wherein the one or more processors are individually or collectively further operable to execute the code to cause the network entity to:receive an uplink acknowledgment that indicates successful reception of the information associated with indicating the respective resource of the one or more instances of second DCI.

25. A method for wireless communications at a user equipment (UE), comprising:receiving first downlink control information (DCI) via a physical downlink control channel (PDCCH), the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI; andAttorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO77receiving at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

26. The method of claim 25, wherein the information included in the first DCI comprises an indication of DCI resource information in a physical downlink shared channel (PDSCH) scheduled by the first DCI, the method further comprising:receiving the DCI resource information in the PDSCH based at least in part on the indication of DCI resource information, wherein receiving the at least one of the one or more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH.

27. The method of claim 25, wherein:the information included in the first DCI comprises an indication of a presence of second DCI in a physical downlink shared channel (PDSCH) scheduled by the first DCI, andreceiving the at least one of the one or more instances of second DCI is based at least in part on receiving the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.

28. A method for wireless communications at a network entity, comprising:transmitting first downlink control information (DCI) via a physical downlink control channel (PDCCH), the first DCI including information associated with indicating a respective resource, different from the PDCCH, of one or more instances of second DCI; andtransmitting at least one of the one or more instances of second DCI in accordance with the information associated with indicating the respective resource of the one or more instances of second DCI.

29. The method of claim 28, wherein the information included in the first DCI comprises an indication of DCI resource information in a physical downlink shared channel (PDSCH) scheduled by the first DCI, the method further comprising:Attorney Docket No. PY2983IL.WO (114958.6159)Qualcomm Ref. No. 2500778WO78transmitting the DCI resource information in the PDSCH based at least in part on the indication of DCI resource information, wherein transmitting the at least one of the one or more instances of second DCI is in accordance with resources indicated by the DCI resource information in the PDSCH.

30. The method of claim 28, wherein:the information included in the first DCI comprises an indication of a presence of second DCI in a physical downlink shared channel (PDSCH) scheduled by the first DCI, andtransmitting the at least one of the one or more instances of second DCI is based at least in part on transmitting the PDSCH scheduled by the first DCI in accordance with the indication of the presence of second DCI in the PDSCH.Attorney Docket No. PY2983IL.WO (114958.6159)

Images