ASSOCIATING MULTIPLE-STAGE DOWNLINK CONTROL INFORMATION

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may receive an indication of an association between first-stage downlink control information (DCI) and second-stage DCI. The UE may recover the second-stage DCI based at least in part on the indication of the association. Numerous other aspects are described.

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for associating multiple-stage downlink control information.

BACKGROUND

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE). The method may include receiving an indication of an association between first-stage downlink control information (DCI) and second-stage DCI. The method may include recovering the second-stage DCI based at least in part on the indication of the association.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include transmitting an indication of an association between first-stage DCI and second-stage DCI. The method may include transmitting at least the first-stage DCI based at least in part on the association.

Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or collectively, to receive an indication of an association between first-stage DCI and second-stage DCI. The one or more processors may be configured to recover the second-stage DCI based at least in part on the indication of the association.

Some aspects described herein relate to an apparatus for wireless communication at a network node. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured, individually or collectively, to transmit an indication of an association between first-stage DCI and second-stage DCI. The one or more processors may be configured to transmit at least the first-stage DCI based at least in part on the association.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive an indication of an association between first-stage DCI and second-stage DCI. The set of instructions, when executed by one or more processors of the UE, may cause the UE to recover the second-stage DCI based at least in part on the indication of the association.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit an indication of an association between first-stage DCI and second-stage DCI. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit at least the first-stage DCI based at least in part on the association.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving an indication of an association between first-stage DCI and second-stage DCI. The apparatus may include means for recovering the second-stage DCI based at least in part on the indication of the association.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting an indication of an association between first-stage DCI and second-stage DCI. The apparatus may include means for transmitting at least the first-stage DCI based at least in part on the association.

DETAILED DESCRIPTION

“Single-stage downlink control information (DCI)” may denote DCI that indicates transmission information in a single transmission, and “multiple-stage (multi-stage) DCI” may denote DCI that indicates the transmission information in multiple transmissions. Single-stage DCI may use a less amount of signaling relative to multi-stage DCI, and multi-stage DCI may provide more flexibility, use fewer air interface resources, utilize less decoding power, and/or support more features (e.g., legacy features and/or new features) relative to multiple single-stage DCI, such as an ability to configure each stage of a multi-stage DCI with different transmission configurations.

To illustrate, each transmission associated with multi-stage DCI may have different operating criteria and/or different operating priorities from one another such that a network node uses different transmission configurations for each stage to satisfy the different operating criteria. As one example, each stage of a multi-stage DCI may be associated with a respective control resource set (CORESET) and/or a respective a search space (SS) set configuration. However, different CORESET configurations and/or different SS set configurations for the stages of multi-stage DCI may make DCI detection and/or recovery by a UE difficult. Without a mechanism to associate the stages, a UE may fail to detect and/or recover the correct second-stage DCI that is associated with a first-stage DCI. Failure to recover first-stage DCI and/or the related second-stage DCI may result in the UE failing to obtain transmission information and, subsequently, fail to transmit and/or receive communications with a network node.

Various aspects described herein generally relate to associating two-stage DCI. Some aspects more specifically relate to a network node indicating the association to a UE. In some aspects, a UE may receive an indication of an association between first-stage DCI and second-stage DCI. Based at least in part on receiving the indication of the association, the UE may recover the second stage DCI. That is, the UE may recover the correct second-stage DCI that is associated with a first-stage DCI and, subsequently, recover transmission information that is synchronized with a network node.

Indicating an association between first-stage DCI and second-stage DCI may enable a network node to configure the stages of multi-stage DCI differently to satisfy operating criteria and/or to preserve air interface resources. Alternatively, or additionally, indicating the association provide a UE with an ability to detect and/or recover the correct second-stage DCI that is associated with first-stage DCI and, subsequently, transmit and/or receive communications with the network node.

In some aspects, a UE (e.g., a UE120) may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may receive an indication of an association between first-stage DCI and second-stage DCI; and recover the second-stage DCI based at least in part on the indication of the association. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, a network node (e.g., a network node110) may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may transmit an indication of an association between first-stage DCI and second-stage DCI; and transmit at least the first-stage DCI based at least in part on the association. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

The network controller130may include a communication unit294, a controller/processor290, and a memory292. For visual clarity,FIG.2shows the memory292as a single memory, but other examples of the memory292may include multiple memories (e.g., two or more memory components). The network controller130may include, for example, one or more devices in a core network. The network controller130may communicate with the network node110via the communication unit294.

At the network node110, the uplink signals from UE120and/or other UEs may be received by the antennas234, processed by the modem232(e.g., a demodulator component, shown as DEMOD, of the modem232), detected by a MIMO detector236if applicable, and further processed by a receive processor238to obtain decoded data and control information sent by the UE120. The receive processor238may provide the decoded data to a data sink239and provide the decoded control information to the controller/processor240. The network node110may include a communication unit244and may communicate with the network controller130via the communication unit244. The network node110may include a scheduler246to schedule one or more UEs120for downlink and/or uplink communications. In some examples, the modem232of the network node110may include a modulator and a demodulator. In some examples, the network node110includes a transceiver. The transceiver may include any combination of the antenna(s)234, the modem(s)232, the MIMO detector236, the receive processor238, the transmit processor220, and/or the TX MIMO processor230. The transceiver may be used by a processor (e.g., the controller/processor240) and a memory242to perform aspects of any of the methods described herein (e.g., with reference toFIGS.4-11). For visual clarity,FIG.2shows the memory242as a single memory, but other examples of the memory242may include multiple memories (e.g., two or more memory components).

In some aspects, a UE (e.g., a UE120) includes means for receiving an indication of an association between first-stage DCI and second-stage DCI; and/or means for recovering the second-stage DCI based at least in part on the indication of the association. The means for the UE to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, a network node (e.g., a network node110) includes means for transmitting an indication of an association between first-stage DCI and second-stage DCI; and/or means for transmitting at least the first-stage DCI based at least in part on the association. The means for the network node to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

FIG.4is a diagram illustrating an example400of DCI that schedules one or more communications with a UE, in accordance with the present disclosure. As shown inFIG.4, a network node110may communicate DCI to a UE120directly, but other examples may include the network node110communicating the DCI to the UE120via one or more network nodes.

The network node110may transmit, to the UE120(e.g., directly or via one or more network nodes), DCI405that schedules one or more communications for the UE120. In some aspects, the network node110may transmit the DCI405in a physical downlink control channel (PDCCH) and/or using Layer 1 signaling. “Downlink DCI” may refer to DCI that schedules a downlink communication (e.g., a physical downlink shared channel (PDSCH) communication and/or a channel state information reference signal (CSI-RS)) to the UE120, and “uplink DCI” may refer to DCI that schedules an uplink communication (e.g., a physical uplink shared channel (PUSCH) communication or a sounding reference signal (SRS)) from the UE. The DCI405may indicate any combination of transmission information, such as a transmission format, an MCS, a resource allocation, and/or other types of information used by a transmitter to encode, and/or receiver to decode, transmitted data.

The DCI405may be configured in a variety of DCI formats that partition the DCI405into different bitfields that may be of varying length. Each DCI format may be associated with a different transmission direction and/or communication channel. As one example, “DCI Format 0_1” may be associated with a first communication configuration for a PUSCH communication and “DCI Format 0_2” may be associated with a second communication configuration for a PUSCH communication. “DCI Format 1_0” may be associated with a third communication configuration for a PDSCH communication and “DCI Format 1_1” may be associated with a fourth communication configuration for a PDSCH communication. “DCI Format 0_1” and “DCI Format 0_2” may both be referred to as uplink DCI, and DCI Format 1_0″ and “DCI Format 1_1” may both be referred to as downlink DCI.

Each format may partition the DCI405differently such that each DCI format includes a different combination of bitfields relative to the other DCI formats. In some aspects, at least two DCI formats (e.g., one or more uplink DCI formats and/or one or more downlink DCI formats) may include a same bitfield (e.g., a same bit length in a same location of the DCI), such as a DCI format indicator field. Alternatively, or additionally, at least two DCI formats may include bitfields that indicate same transmission information and are positioned at different locations in the DCI and/or have a different bit length. For example, “DCI Format 1_0” and “DCI Format 0_1” may each include a respective MCS bitfield that is positioned at different locations in the DCI. In some aspects, uplink DCI formats (e.g., “DCI Format 0_1” and/or “DCI Format 0_2”) may include one or more bitfields that are associated with uplink transmission information, and downlink DCI formats (e.g., “DCI Format 1_0” and/or “DCI Format 1_1”) may include one or more bitfields that are associated with downlink transmission information.

“Single-stage DCI” may denote DCI that indicates transmission information in a single transmission, and “multiple-stage (multi-stage) DCI” may denote DCI that indicates the transmission information in multiple transmissions. As one example of multi-stage DCI, two-stage DCI may indicate transmission information based at least in part on using two transmissions: a first-stage DCI transmission and a second-stage DCI transmission. Single-stage DCI may use a less amount of signaling relative to multi-stage DCI, and multi-stage DCI may provide more flexibility, use fewer air interface resources, utilize less decoding power, and/or support more features (e.g., legacy features and/or new features) relative to multiple single-stage DCI. As one example, multi-stage DCI may provide flexibility in how each transmission is configured.

In some aspects, each transmission associated with multi-stage DCI may have different operating criteria and/or different operating priorities from one another. For instance, a UE120may use blind detection (alternatively referred to as blind decoding) to detect first-stage DCI, and an associated operating priority may be reducing an amount of blind detection performed by a UE to preserve a battery life of the UE and/or reducing an acquisition time by the UE (e.g., detection and recovery). Alternatively, or additionally, the second-stage DCI may be associated with an operating priority to avoid having the UE perform blind detection to detect the second-stage DCI. Accordingly, and based at least in part on the associated operating priorities, the first-stage DCI may be associated with a reduced number of PDCCH candidates within a PDCCH monitoring occasion (PMO), a reduced number of PMOs, and/or a reduced number of control channel elements (CCEs) relative to the second-stage DCI. Alternatively, or additionally, the second-stage DCI may be associated with a higher number of PDCCH candidates within a PMO, a higher number of PMOs, and/or a higher number of CCEs relative to the first-stage DCI to provide a network node with more flexibility on transmitting second-stage DCI to one or more UEs.

A bandwidth for PDCCH monitoring that is associated with monitoring for a DCI transmission may be based at least in part on a CORESET configuration. Alternatively, or additionally, a number of PDCCH candidates and/or a time domain pattern of PMOs (e.g., a number of PMOs and/or respective time spans of the PMOs) associated with the transmission of DCI may be based at least in part on an SS set configuration. A CORESET may refer to a control region of resources that is structured to support an efficient use of the resources, such as by flexible configuration or reconfiguration of the resources for one or more PDCCHs associated with a UE. An SS set may refer to an area and/or particular resources within the CORESET that are associated with PDCCH and/or DCI transmissions. That is, an SS set may indicate which regions of the CORESET to monitor for PDCCH and/or DCI transmissions. Accordingly, a first CORESET configuration and/or a first SS set configuration may be more suitable for first-stage DCI than second-stage DCI (and/or vice versa with a second CORESET configuration and/or second SS set configuration) to provide efficient use of air interface resources within a wireless network and, subsequently, increase a capacity of the wireless network. That is, using a same CORESET configuration and/or same SS set configuration for first-stage DCI and second-stage DCI may result in inefficient use of air interface resources and decrease the capacity of the wireless network. However, different CORESET configurations and/or different SS set configurations for the stages of multi-stage DCI may make DCI detection and/or recovery by a UE difficult. Without a mechanism to associate the stages, a UE may fail to detect and/or recover the correct second-stage DCI that is associated with the first-stage DCI. Failure to recover first-stage DCI and/or the related second-stage DCI may result in the UE failing to obtain transmission information and, subsequently, fail to transmit and/or receive communications with a network node.

Some techniques and apparatuses described herein provide associating two-stage DCI. In some aspects, a UE may receive an indication of an association between first-stage DCI and second-stage DCI. As one example, the UE may receive first PDCCH configuration information that is associated with the first-stage DCI and second PDCCH configuration information that is associated with the second-stage DCI. To illustrate, the UE may receive the first PDCCH configuration information and/or the second PDCCH configuration information in an RRC message. In some aspects, the first PDCCH configuration information and the second PDCCH configuration may specify a same identifier (e.g., a two-stage DCI identifier as described below). That is, the indication of the association between the first-stage DCI and the second-stage DCI may be the first PDCCH configuration information and the second PDCCH configuration information specifying the same identifier. Based at least in part on receiving the indication of the association, the UE may recover the second stage DCI.

Indicating an association between first-stage DCI and second-stage DCI may enable a network node to configure the first-stage DCI and the second-stage DCI with different resources to meet operating criteria and/or preserve air interface resource. Indicating an association between first-stage DCI and second-stage DCI may also provide a UE with an ability to detect and/or recover the correct second-stage DCI that is associated with first-stage DCI and, subsequently, transmit and/or receive communications with the network node.

As one example, the ability to indicate an association between first-stage DCI and second-stage DCI may enable the network node to configure the first-stage DCI and the second-stage DCI based at least in part on different CORESETs and/or different SS sets in a manner that preserves air interface resources in a wireless network and/or increases capacity of the wireless network. For instance, the network node may select a first configuration for the first-stage DCI that has fewer air interface resource relative to a second configuration for the second-stage DCI. To illustrate, the network node may select, as at least part of the first configuration, a first CORESET that has a reduced bandwidth relative to a second CORESET associated with the second-stage DCI. In some aspects, the first-stage DCI and/or the first configuration may be based at least in part on reducing blind detection performed by the UE to preserve a battery life of the UE, such as by reducing a number of CCEs, a number of configured PDCCH candidates within a PMO, and/or a number of PMOs associated with the first-stage DCI as described above. In some aspects, the ability to configure the multi-stage DCI with on different CORESETs and/or different SS sets may enable the network node to increase a number of configured PDCCH candidates per PMO, a number of PMOs (e.g., one PMO per slot and/or one PMO per mini-slot), and/or a number of CCEs of the second configuration (e.g., relative to the first configuration) to provide more options for transmitting the second-stage DCI that may improve the transmission (e.g., by selecting resources that may increase a power level, may reduce interference, and/or may be optimized for a particular UE implementation).

FIGS.5A,5B,5C,5D, and5Eare diagrams illustrating a first example500, a second example502, a third example504, a fourth example506, and a fifth example508, respectively, of associating multiple stages of multi-stage DCI, in accordance with the present disclosure.

Multi-stage DCI may provide more flexibility and/or support more features (e.g., legacy features and/or new features) relative to single-stage DCI. For instance, and as described above, each transmission of the multi-stage DCI may be configured based at least in part on different operating criteria and/or different operating priorities. A first-stage DCI transmission may be configured to use fewer air interface resources, use a smaller bandwidth, reduce blind detection performed by a UE, and/or shorten an acquisition time (e.g., detection and/or decoding) by a UE relative to a second-stage DCI transmission. A second-stage DCI transmission may be configured to provide more transmission options and/or enable parallel processing at a UE. To illustrate, a network node may schedule one or more downlink resources via first-stage DCI (e.g., of a two-stage DCI) before receiving a hybrid automatic repeat request (HARQ) acknowledgement that is associated with a prior PDSCH communication. A UE receiving the first-stage DCI may begin generating a channel estimation (e.g., based at least in part on analyzing a reference signal) before receiving a second-stage DCI of the two-stage DCI. That is, the UE may perform some processing in parallel with the network node preparing and/or transmitting the second-stage DCI based at least in part on information included in the first-stage DCI. Alternatively, or additionally, the UE may begin preparing uplink data based at least in part on receiving first-stage DCI that is associated with an uplink communication. Accordingly, the UE may perform processing for an uplink communication in parallel with the network node preparing and/or transmitting the second-stage DCI, resulting in a reduce processing time relative to serial processing.

In some aspects, and as described above, multi-stage DCI may reduce an amount of blind detection performed by a UE based at least in part on configuration of the first-stage DCI (e.g., a number of associated resources, a number of PMOs, a number of PDCCH candidates, and/or a periodicity). Alternatively, or additionally, multi-stage DCI may enable a network node to reduce control signaling overhead in a wireless network (e.g., relative to single-stage DCI). To illustrate, the network node may indicate common scheduling information and/or common transmission information in the first-stage DCI for multiple UEs (e.g., common to multiple second-stage DCI associated with multiple UEs) and transmission-specific scheduling information (e.g., specific to a scheduled transmission) and/or joint scheduling information in the second-stage DCI. In some aspects, a network node may use different transmission characteristics for first-stage DCI and a related second-stage DCI. To illustrate, the network node may transmit the first-stage DCI using first transmission configuration that is more robust relative to a second transmission configuration associated with the second-stage DCI. As one example, the first transmission configuration may use a wider beam configuration relative to the second transmission configuration to increase a probability of a UE receiving the first DCI. Alternatively, or additionally, the second transmission configuration may use a narrower beam relative to the first transmission configuration to increase a spectral efficiency of the second-stage DCI transmission. Accordingly, a network node may use different transmission configurations for multi-stage DCI to reduce resource waste, increase a detection probability, and/or preserve a battery life of a UE (e.g., by reduce UE processing, such as an amount of blind detection). In some aspects, and based at least in part on using different transmission configurations for the multi-stage DCI (e.g., different CORESETs and/or different SS sets), the network node may transmit an indication of an association between first-stage DCI and second-stage DCI to enable a UE to detect and/or recover an entirety of transmission information.

FIG.5Aillustrates a first example500of associating the stages of multi-stage DCI. “Associating the stages” may denote associating at least a first transmission to at least a second transmission. In the first example500, the multi-stage DCI is in the form of two-stage DCI, a horizontal axis represents time, and a vertical axis represents frequency. First-stage DCI PMOs are shown in solid white and second-stage DCI PMOs are shown with a diagonal pattern. The first-stage DCI PMOs may be based at least in part on a first CORESET bandwidth shown by reference number510and the second-stage DCI PMOs may be based at least in part on a second CORESET bandwidth shown by reference number512. In some aspects, the first CORESET bandwidth may be smaller than the second CORESET bandwidth. Over a duration shown by reference number514, the first-stage DCI may be associated with a first number of PMOs (shown as one) and the second-stage DCI may be associated with a second number of PMOs (shown as three). As one example, one first-stage DCI transmitted in a first-stage DCI PMO may be associated with three second-stage DCIs that are each transmitted in a respective second-stage DCI PMO. In some aspects, a network node (e.g., a network node110) may configure the first number of PMOs to be fewer than the second number of PMOs to reduce a number of blind detections performed by a UE. As one example, the network node may transmit configuration information that indicates a respective configuration (e.g., time resources and/or frequency resources) for any combination of the first-stage DCI PMOs, the second-stage DCI PMOs, the first CORESET bandwidth, and/or the second CORESET bandwidth.

As one example, the network node may transmit first SS set configuration information that indicates which time resources and/or frequency resources of a first CORESET to monitor for the first-stage DCI and second SS set configuration information that indicates which time resources and/or frequency resources of a second CORESET to monitor for the second-stage DCI. To illustrate, the network node may transmit one or more search space information elements (IE) in one or more RRC messages, and each search space IE may indicate respective SS set configuration information. Alternatively, or additionally, the network node may transmit first CORESET configuration information and/or second CORESET configuration information (e.g., information that indicates the respective frequency resources included in the first CORESET and/or the second CORESET), such as by indicating the respective CORESET configuration information via one or more CORESET IEs included in one or more RRC messages.

To indicate an association between first-stage DCI and second-stage DCI, the network node may include a two-stage DCI association identifier (ID) in each of the search space IEs and/or each of the CORESET IEs and may set the respective two-stage DCI association IDs to a same value and/or a same ID. As one example, the network node may transmit a first search space IE that is associated with the first-stage DCI and a second search space IE that is associated with the second-stage DCI. In some aspects, each search space set indicated by the respective search space IE may be associated with a single (respective) CORESET. The network node may include, in each search space IE, a respective two-stage DCI search space association ID field (e.g., twoStageDCISSAssociationID). To indicate an association between the first-stage DCI and the second-stage DCI, the network node may set the respective two-stage DCI search space association ID fields to a same value and/or a same ID. Accordingly, the network node may configure first-stage DCI PMOs based at least in part on a first CORESET with a first bandwidth and second-stage DCI PMOs based at least in part on a second CORESET with a second bandwidth. That is, a network node may associate two CORESETs with different bandwidths to two-stage DCI and/or two-stage DCI monitoring (e.g., PMOs).

As another example, the network node may transmit a first CORESET IE that is associated with the first-stage DCI and a second CORESET IE that is associated with the second-stage DCI. The network node may include, in each CORESET IE, a respective two-stage DCI CORESET association ID field (e.g., twoStageDCICORESETAssociationID). To indicate an association between the first-stage DCI and the second-stage DCI, the network node may set the respective two-stage DCI CORESET association ID fields to a same value and/or a same ID. In some aspects, the respective SS sets associated with the two CORESETs may be configured with a same SS ID, but may have different and/or independent configurations for one or more other first-stage DCI and second-stage DCI parameters. That is, the SS ID may be used to indicate a two-stage DCI association without the addition of an association field (e.g., a twoStageDCISSAssociationID field) in the search space IE. Example parameters that may be different between a first-stage DCI search space set and a second-stage DCI search space set may include an aggregation level, a number of PDCCH candidates for each configured aggregation level, a duration of a PMO in a number of OFDM symbols, and/or a starting symbol of a PMO in a slot.

As described above, the network node may indicate common scheduling information via the first-stage DCI (e.g., common to multiple second-stage DCIs) and/or long-term scheduling information (e.g., scheduling information that changes less frequently relative to other scheduling information). The long-term scheduling information may be UE-specific scheduling information or common scheduling information. Alternatively, or additionally, the network node may indicate transmission-specific scheduling information via the second-stage DCI. The network node may transmit the first-stage DCI using a first beamwidth that is wider than a second beamwidth that the network node may use to transmit the second-stage DCI. The wider beamwidth may enable the network node to transmit the first-stage DCI with more spatial coverage relative to the second beamwidth and increase a probability that the UE detects the first-stage DCI.

FIG.5Billustrates a second example502of associating the stages of multi-stage DCI. In the second example502, the multi-stage DCI is in the form of two-stage DCI, a horizontal axis represents time, and a vertical axis represents frequency. In some aspects, first-stage DCI may be associated with multiple second-stage DCIs. As one example, each second-stage DCI of the multiple second-stage DCI may be transmitted by a respective network node, such as a respective TRP. To illustrate, a first network node (e.g., a first TRP) may be configured to transmit the first-stage DCI and/or may be associated with first-stage DCI PMOs (shown in solid white). Alternatively, or additionally, the first network node may be associated with first second-stage DCI PMOs (shown with a diagonal pattern) and a second network node (e.g., a second TRP) may be associated with second second-stage DCI PMOs (shown with a dotted pattern). That is, the first network node may transmit a first second-stage DCI based at least in part on the first second-stage DCI PMOs and the second network node may transmit a second second-stage DCI based at least in part on the second second-stage PMOs. The first second-stage DCI PMOs that are associated with the first network node may be based at least in part on a first CORESET that is configured based at least in part on a first bandwidth as shown by reference number512, and the second second-stage DCI PMOs may be based at least in part on a second CORESET that is configured based at least in part on a second bandwidth as shown by reference number516. Accordingly, the second-stage DCI PMOs may be based at least in part on a different CORESET bandwidths.

To illustrate, one or more network nodes (e.g., the first network node and/or the second network node) may transmit one or more search set IEs that indicate respective search space configuration information associated with the first-stage DCI PMOs, the first second-stage DCI PMOs, and/or the second second-stage DCI PMOs. To indicate an association between the first-stage DCI PMOs, the first second-stage DCI PMOs, and the second second-stage DCI PMOs, each search set IE may include a respective two-stage DCI search space association ID field (e.g., twoStageDCISSAssociationID) that is set to a same value and/or same ID in a similar manner as described above. Alternatively, or additionally, the network node(s) may transmit one or more CORESET IEs that indicate respective CORESET configuration information associated with the first-stage DCI PMOs, the first second-stage DCI PMOs, and/or the second second-stage DCI. To indicate an association between the first-stage DCI PMOs, the first second-stage DCI PMOs, and the second second-stage DCI PMOs, each CORESET IE may include a respective two-stage DCI CORESET association ID field (e.g., twoStageDCICORESETAssociationID) that is set to a same value and/or a same ID. Accordingly, in some aspects, first-stage DCI may be associated with multiple second-stage DCIs (e.g., from multiple network nodes, from multiple TRPs, and/or in multiple second-stage DCI PMOs on each network node).

FIG.5Cillustrates a third example504of associating the stages of multi-stage DCI. In the third example504, the multi-stage DCI is in the form of two-stage DCI, a horizontal axis represents time, and a vertical axis represents frequency. In some aspects, two-stage DCI as shown by reference number518may be cross-carrier two-stage DCI. To illustrate, a scheduling network node (e.g., a first network node) may transmit first-stage DCI based at least in part on a first carrier520(shown as fc1), and a scheduled network node (e.g., a second network node that may be scheduled by the scheduling network node) may transmit second-stage DCI based at least in part on a second carrier522(shown as fc2). That is, the first-stage DCI and the second-stage DCI may be cross-carrier two-stage DCI that based at least in part on at least two different carrier frequencies. By configuring the scheduled network node to transmit the second-stage DCI (e.g., via the second carrier522), the scheduling network node may offload control signaling to the scheduled network node and/or free resources at the scheduling network node for other tasks to increase a capacity of the wireless network. In some aspects, the association between the first-stage DCI and the second-stage DCI of the cross-carrier two-stage DCI may be based at least in part on the first-stage DCI and the second-stage DCI being configured with a same SS set ID. To illustrate, the scheduling network node may transmit first SS set configuration information that is associated with the first-stage DCI and indicates a particular SS set ID. A UE may identify the SS set ID in the first SS set configuration information and determine to recover the second-stage DCI based at least in part on the SS set ID indicated in the first SS set configuration information. That is, the SS set ID indicated in the first configuration information may implicitly indicate a SS set ID for the second-stage DCI. Alternatively, or additionally, the scheduling network node may transmit second SS set configuration information that is associated with the second-stage DCI and indicates the same particular SS set ID.

In some aspects, first-stage DCI and second-stage DCI may be based at least in part on dedicated DCI formats that jointly provide complete scheduling information for a data transmission (shown with a diamond pattern) as shown by reference number524. To illustrate, the first-stage DCI may be based at least in part on a first DCI format (e.g., a first-stage DCI format) and the second-stage DCI may be based at least in part on a second DCI format (e.g., a second-stage DCI format). To calculate a location of and/or recover the data transmission, a UE may detect the first DCI format and, based at least in part on detecting the first DCI format, may detect and/or recover the second-stage DCI using the second DCI format. That is, detecting the presence of the first DCI format may implicitly indicate a pending transmission of second-stage DCI and/or that the second-stage DCI will be based at least in part on the second DCI format. The UE may recover the data transmission based at least in part on recovering the joint information (i.e., information that is used together) included in the first-stage DCI and the second-stage DCI.

Alternatively, or additionally, the UE may detect that the first-stage DCI is formatted based at least in part on a first DCI format (e.g., a first-stage DCI includes a first set of scheduling fields in the DCI format) and subsequently determine that the second-stage DCI is formatted based at least in part on a second DCI format (e.g., a second-stage DCI includes a second set of scheduling fields in the DCI format) and/or uses a same DCI format as the first-stage DCI. For example, the UE may receive an indication of two-stage DCI (e.g., via a two-stage DCI association ID as described with regard toFIGS.5A and5B), detect that the first-stage DCI is formatted based at least in part on a particular DCI format, and determine to recover the second-stage DCI using the same particular DCI format. That is, the UE may recover information (e.g., joint information, common information, and/or transmission specific information) from the first-stage DCI and the second-stage DCI using a same DCI format to recover the information from both stages based at least in part on the first-stage DCI and the second-stage DCI being part of a same multi-stage DCI (e.g., a same two-stage DCI). Alternatively, or additionally, the UE may recover information from the first-stage DCI based at least in part on the first DCI format and recover information from the second-stage DCI based at least in part on the second DCI format.

FIG.5Dillustrates a fourth example506of associating the stages of multi-stage DCI. In the fourth example506, the multi-stage DCI is in the form of two-stage DCI, a horizontal axis represents time, and a vertical axis represents frequency. In some aspects, and as shown by reference number526, first-stage DCI may indicate one or more second-stage DCI PMOs for a second-stage DCI that is part of a same multi-stage DCI. That is, the first-stage DCI may indicate an association with the second-stage DCI based at least in part on indicating one or more second-stage DCI PMOs to monitor for detecting the second-stage DCI. As one example, the first-stage DCI may include an offset field that indicates a starting PMO of the second-stage DCI PMOs and/or a length field that indicates a number of PMOs associated with the second-stage DCI PMOs. In some aspects, an offset indicated by the offset field may be relative to the first-stage DCI. For instance, an offset of zero may indicate to start monitoring for the second-stage DCI in a first second-stage DCI PMO that occurs after the first-stage DCI (e.g., second-stage DCI PMO528), and an offset of one may indicate to start monitoring for the second-stage DCI in a second second-stage DCI PMO that occurs after the first-stage DCI (e.g., second-stage DCI PMO530). Accordingly, the offset field and/or the length field may indicate an integer value that has a unit of second-stage DCI PMOs. In the fourth example506, the first-stage DCI indicates an association with one or more second-stage DCIs that may be located in the three PMOs included in a monitoring window532.

FIG.5Eillustrates a fifth example508of associating the stages of multi-stage DCI. In the fifth example508, the multi-stage DCI is in the form of two-stage DCI, a horizontal axis represents time, and a vertical axis represents frequency. In some aspects, an association between first-stage DCI and second-stage DCI of a same multi-stage DCI (e.g., a two-stage DCI) may be based at least in part on a monitoring window534. That is, and in a similar manner as described with regard to the fourth example506, the second-stage DCI that is associated with the first-stage DCI may be a second-stage DCI that UE detects within the monitoring window534. Characteristics of the monitoring window534(e.g., a start time, a duration, and/or an end time) may be indicated by a network node and/or may be specified by a communication standard. As one example, the network node may transmit an indication of a start time and/or a duration of the monitoring window534in RRC signaling. As another example, the communication standard may specify a value for the start time and/or the duration of the monitoring window534. In a similar manner as described with regard to the fourth example506, the network node and/or the communication standard may indicate and/or specify the characteristics based at least in part on using an integer and/or a unit of second-stage DCI PMOs. Alternatively, or additionally, the characteristics may be based at least in part on the first-stage DCI.

To illustrate, a reference time536(shown as t) may be associated with an end transmission time of first-stage DCI (shown in solid white), and the network node and/or communication standard may specify an offset of one to indicate that the monitoring window534starts at the second second-stage PMO538that occurs after the reference time536. Alternatively, or additionally, the network node and/or the communication standard may indicate a second offset value and/or length that specifies an ending PMO associated with the monitoring window534. In some aspects, the duration of the monitoring window534and/or a number of PMOs included in the monitoring window may be implicit and/or based at least in part on a start time of a second first-stage DCI PMO540. For instance, an end of the monitoring window534may be based at least in part on a last second-stage DCI PMO that completes prior to a start transmission time of the second first-stage DCI PMO540and/or an end transmission time of the second first-stage DCI PMO540. Accordingly, the association between a first-stage DCI and a second-stage DCI may be based at least in part on second-stage DCI PMOs that occur in between first-stage DCI PMOs.

Indicating of an association between the stages of a multi-stage DCI may enable a UE to correctly detect and/or recover each stage and, subsequently, transmit and/or receive communications with the network node. The use of multi-stage DCI, and the indication of an association between the stages, may enable a network node to configure each stage transmission differently (e.g., with different CORESETs and/or different SS sets) to meet operating criteria and preserve air interface resources in a wireless network. Preserving air interface resources may also enable the network node to increase a capacity of the wireless network and/or serve more UEs.

As indicated above,FIGS.5A,5B,5C,5D, and5Eare provided as examples. Other examples may differ from what is described with respect toFIGS.5A,5B,5C,5D, and5E.

FIG.6is a diagram illustrating an example600of configuring blind detection for multi-stage DCI, in accordance with the present disclosure.

How a UE calculates a number of blind detections to perform for multi-stage DCI may differ from how a UE calculates a number of blind detections for single-stage DCI. To illustrate, for single-stage DCI, the UE may calculate a maximum number of blind detections based at least in part on a time partition, such as a slot and/or a sub-slot, and/or a number of PDCCH candidates in a PMO that is included in the time partition. For multi-stage DCI, the time partition may include multiple PMOs associated with different stages, such as a first-stage DCI PMO and/or a second-stage DCI PMO.

In some aspects, a total number of blind detections may include a first number of blind detections associated with first-stage DCI, a second number of blind detections associated with second-stage DCI, and/or a third number of blind detections associated with single-stage DCI. Accordingly, for multi-stage DCI, a UE may calculate a number of blind detections to perform based at least in part on a time partition (e.g., a slot and/or a sub-slot) that includes a second-stage DCI PMO. To illustrate, the UE may calculate the number of blind detections based at least in part on a number of PDCCH candidates that are configured for a second-stage DCI PMO based at least in part on a search space configuration. For instance, the UE may calculate the number of blind detections for the second-stage DCI as the same number of PDCCH candidates that are configured for the second-stage DCI PMO based at least in part on the search space configuration (e.g., the total number of PDCCH candidates for the second-stage DCI).

As another example, the UE may calculate the number of blind detections to perform based at least in part on a maximum number of DCIs that the UE may be capable of receiving and/or decoding in a time duration. To illustrate, the UE may obtain, based at least in part on decoded first-stage DCI, information that indicates which second-stage DCI PDCCH candidates to decode. The number of second-PDCCH candidates indicated based at least in part on the decoded first-stage DCI may be configured to not exceed a maximum number of DCIs that the UE may be specified to receive and/or is capable of receiving. In some aspects, the maximum number of DCIs that the UE is capable of and/or supports receiving and/or decoding may be equal to the total number of PDCCH candidates configured for and/or associated with the second-stage DCI PMO (e.g., via the search space configuration). In other aspects, the maximum number of DCIs that the UE supports receiving may be fewer and/or smaller than the total number of PDCCH candidates configured for and/or associated with the second-stage DCI PMO. To illustrate, the maximum number of DCIs that the UE supports receiving in a time duration may be based at least in part on a UE capability, such as a UE capability associated with uplink data scheduling and/or a UE capability associated with downlink data scheduling. As one example, for frequency division duplex (FDD), the UE may be directed to receive a maximum number of one downlink DCI and one uplink DCI in a time duration. For time division duplex (TDD), the UE may be directed to receive a maximum number of one downlink DCI and two uplink DCIs and/or two downlink DCIs and one uplink DCI in the time duration.

Alternatively, or additionally, the maximum number of DCIs that the UE supports receiving and/or decoding may be based at least in part on first-stage DCI received and/or decoded by the UE that indicates one or more PDCCH candidates associated with the second-stage DCI. That is, the maximum number of DCIs that the UE supports receiving and/or decoding may be independent of whether the DCI is a first-stage DCI and/or second-stage DCI.

In some aspects, the UE may calculate the maximum number of DCIs to detect based at least in part on a minimum offset between the first-stage DCI's PMO and the associated second-stage DCI PMOs.FIG.6illustrates the example600that includes multi-stage DCI in the form of two-stage DCI, a horizontal axis of the example600represents time, and a vertical axis of the example600represents frequency. First-stage DCI PMOs are shown in solid white, and second-stage DCI PMOs are shown with a diagonal pattern. In some aspects, for a first duration602, a UE may calculate a maximum number of blind detections based at least in part on a number of configured PDCCH candidates that occur within the first duration602. For a second duration604, the UE may calculate the maximum number of blind detections based at least in part on a maximum number of DCI for the UE to receive. In some aspects, the UE may be configured with and/or directed to receive (e.g., via a network node and/or a communication standard) the maximum number of DCI to receive. Alternatively, or additionally, the UE may utilize a minimum offset606to calculate the maximum number of DCIs. For example, a network node may transmit an indication of the minimum offset, a communication standard may specify the minimum offset, and/or the UE may calculate the minimum offset based at least in part on a processing time by the UE that is associated with decoding an instance of first-stage DCI. To illustrate, the network node, the communication standard, and/or the UE may specify and/or calculate the minimum offset as an integer value that has a unit of second-stage DCI PMOs and/or is an offset that is based at least in part on a first-stage DCI PMO. In the example600, the minimum offset606has a value of one.

In some aspects, the a UE may calculate the maximum number of blind detections based at least in part on the second-stage DCI PMOs shown by reference number608that occur after the minimum offset604and/or are within a time partition610(e.g., a slot and/or a sub-slot) that is located within the second duration604. In some aspects, and as shown byFIG.6, the UE may refrain from performing a blind detection on at least one of the configured PDCCH candidates associated with second-stage DCI within the second duration610and, subsequently, preserve a battery life of the UE.

FIG.7is a diagram illustrating an example700of a wireless communication process between a network node110and a UE120, in accordance with the present disclosure.

As shown by reference number710, a network node110may transmit, and a UE120may receive, an indication of an association between two or more stages of multi-stage DCI. As one example, the association may be between first-stage DCI and second-stage DCI of two-stage DCI. Other examples may include more than two stages.

In some aspects, the network node110may transmit first PDCCH configuration information that is associated with first-stage DCI, such as PDCCH configuration information that indicates a CORESET configuration associated with the first-stage DCI and/or an SS set configuration associated with the first-stage DCI. Alternatively, or additionally, the network node110may transmit second PDCCH configuration information that is associated with second-stage DCI. As one example, the network node110may transmit PDCCH configuration information in a system information block (SIB). In other examples, a second network node (e.g., another network node110) that is different from the network node110may transmit the second PDCCH configuration information.

To indicate an association between the first-stage DCI and the second-stage DCI, the network node110configure the first PDCCH configuration information and the second PDCCH configuration information with a same identifier (e.g., a two-stage DCI association identifier). To illustrate, the first PDCCH configuration information and the second PDCCH configuration information may each specify respective SS set configuration information as described with regard toFIG.5A, and the respective SS set configuration may include a two-stage DCI SS association ID. The network node110may indicate an association between the first-stage DCI and the second-stage DCI based at least in part on setting each respective two-stage DCI SS association identifier to a same value and/or a same ID. The respective SS set configuration information that is associated with the first-stage DCI may indicate a different SS set configuration (e.g., a different PMO configuration) relative to the respective SS set configuration information that is associated with the second-stage DCI.

Alternatively, or additionally, the network node110may indicate a first CORESET configuration as at least part of the first PDCCH configuration information and/or a second CORESET configuration as at least in part of the second PDCCH configuration information, and the first CORESET configuration may indicate same and/or different resources than the second CORESET configuration. To illustrate, a first CORESET may be configured (e.g., via the first CORESET configuration) with a first bandwidth and the second CORESET may be configured (e.g., via the second CORESET configuration) with a second bandwidth that has a different size than the first bandwidth (e.g., the second bandwidth may be larger than the first bandwidth). To indicate an association between the first-stage DCI and the second-stage DCI, the network node110indicate a same value and/or same ID for a respective two-stage DCI CORESET association ID included in the first CORESET configuration and the second CORESET configuration. In some aspects, and based at least in part on indicating a same two-stage DCI CORESET association ID in the respective PDCCH configuration information (e.g., the respective CORESET configuration included in the PDCCH configuration information), the network node110may indicate a particular SS set ID in the first PDCCH configuration information and the same particular SS set ID in the second PDCCH configuration information.

In some aspects, first-stage DCI may be associated with multiple second-stage DCI as described with regard toFIG.5B. For instance, the network node110may transmit first PDCCH configuration information that is associated with first-stage DCI, second PDCCH configuration information that is associated with a first second-stage DCI, and/or third PDCCH configuration information that is associated with a second second-stage DCI. To indicate an association between the first-stage DCI and the multiple second-stage DCI, each respective PDCCH configuration information may indicate a same particular two-stage DCI association (e.g., a two-stage DCI SS association ID and/or a two-stage DCI CORESET association ID). That is, the respective PDCCH configuration information may indicate a same value and/or same ID for a respective two-stage DCI association ID. The first PDCCH configuration information, the second PDCCH configuration information, and/or the third PDCCH configuration information may indicate different configurations (e.g., different bandwidths and/or PMOs) from one another as described above.

In some aspects, the indication of an association between first-stage DCI and second-stage DCI may be based at least in part on a SS set ID. To illustrate, the network node110may transmit first PDCCH configuration information that includes first SS set configuration information that is associated with first-stage DCI and indicates a particular SS set identifier. As described above, the UE120may identify the SS set ID in the first SS set configuration information and determine to recover the second-stage DCI based at least in part on the SS set ID indicated in the first SS set configuration information. That is, the association between the first-stage DCI and the second-stage DCI may be based at least in part on the first-stage DCI and the second-stage DCI being configured and/or associated with a same SS set ID. Alternatively, or additionally, the network node110may transmit second PDCCH configuration information second SS set configuration information that is associated with the second-stage DCI and indicates the same particular SS set ID.

In some aspects, to indicate an association between first-stage DCI and second-stage DCI, the network node110may transmit an indication of a monitoring window as described with regard toFIGS.5D and/or5E. That is, a monitoring window may be RRC configured by the network node110. However, in other examples, the monitoring window may be specified by a communication standard. To illustrate, the communication standard may specify one or rules that characterize the monitoring window (e.g., a communication standard rule-based monitoring window).

As shown by reference number720, the network node110may transmit, and the UE120may receive, first-stage DCI that is associated with multi-stage DCI. The network node110may transmit the first-stage DCI based at least in part on first PDCCH configuration information as described with regard to reference number710.

WhileFIG.7shows the network node110transmitting the first-stage DCI separately from the indication of the association between the first-stage DCI and the second-stage DCI, other examples may include the network node110transmitting the indication of the association in the first-stage DCI, such as via an offset field that that indicates a monitoring occasion and/or a monitoring window as described with regard toFIG.5D. That is, instead of transmitting a two-stage DCI association identifier in respective PDCCH configuration information as described with regard to reference number710, the network node110may indicate the association in the first-stage DCI. To illustrate, the offset field may indicate a starting PMO of second-stage DCI PMOs and/or a length field that indicates a number of second-stage DCI to monitor for associated second-stage DCI as described with regard toFIG.5D.

In some aspects, the network node110may transmit the first-stage DCI based at least in part on using a first beamwidth that is different from a second beamwidth used to transmit associated second-stage DCI as described with regard toFIG.5A. Alternatively, or additionally, the first-stage DCI may indicate common scheduling information that is associated with multiple UEs, common scheduling information that is associated with multiple second-stage DCIs and/or UE-specific scheduling information that is associated with a single UE. As described with regard toFIG.5C, the network node110may transmit the first-stage DCI based at least in part on a first carrier that is at a different frequency than a second carrier that is used to transmit second-stage DCI (e.g., by the network node110and/or a second network node110).

As shown by reference number730, the network node110may transmit, and the UE120may receive, second-stage DCI that is associated with the first-stage DCI. In some aspects, the UE120may receive and/or recover the second-stage DCI based at least in part on the indication of an association between the first-stage DCI and the second-stage DCI, such as an indication that is based at least in part on a two-stage DCI association ID, an indication carried in first-stage DCI, and/or an indication that is based at least in part on a rule specified by a communication standard.

As one example, the UE120may receive and/or recover the second-stage DCI based at least in part on a monitoring occasion and/or a monitoring window that is based at least in part on the first-stage DCI, specified by the first-stage DCI and/or a communication standard as described with regard toFIGS.5D and5E. Alternatively, or additionally, the UE120may receive the second-stage DCI based at least in part on a second beamwidth that is narrower than the first beamwidth and/or a second carrier that is different from a first carrier as described above. The second-stage DCI may include transmission-specific scheduling information (e.g., specific to a scheduled transmission) and/or joint scheduling information that is based at least in part on the first-stage DCI.

For visual brevity,FIG.7shows the same network node transmitting the first-stage DCI and the second-stage DCI, but in other examples, different network nodes may transmit the first-stage DCI and the second-stage DCI. For example, and as described with regard toFIG.5B, the second-stage DCI may be one of multiple second-stage DCIs (e.g., transmitted by different network nodes and/or TRPs) and/or may be transmitted by a second network node that is scheduled by a first network node that transmitted the first-stage DCI as described with regard toFIG.5C.

In some aspects, the UE120may recover the recover the second-stage DCI using a second DCI format that is based at least in part on a DCI format association between the first-stage DCI and the second-stage DCI. For instance, and as described above with regard toFIG.5C, the first-stage DCI may be based at least in part on a first DCI format and, based at least in part on detecting the first DCI format, the UE120determine to recover the second-stage DCI using a second DCI format that is the same DCI format or a different DCI format than the first DCI. That is, detecting the presence of the first DCI format may implicitly indicate a pending transmission of second-stage DCI and/or a DCI format associated with the second-stage. Alternatively, or additionally, the UE120may identify, receive, and/or recover an associated second-stage DCI based at least in part on a monitoring window that is based at least in part on the first-stage DCI.

In some aspects, the UE120may receive and/or recover the second-stage DCI based at least in part on determining and/or calculating a blind detection threshold as described with regard toFIG.6. For example, the blind detection threshold based at least in part on a monitoring duration associated with the second-stage DCI, a number of configured PDCCH candidates associated with a search space configuration for the second-stage DCI (e.g., one or more second-stage PMOs), and/or a maximum number of DCIs that the UE120is configured to receive in the monitoring duration. For example, the maximum numbers of DCIs that the UE120is configured and/or able to receive during the monitoring duration may be based at least in part on any combination of a UE capability, a PDCCH candidate indicated by the first-stage DCI, and/or a minimum offset associated with the first-stage DCI and second-stage DCI as described above.

As shown by reference number740, the network node110and the UE120may communicate with one another based at least in part on the first-stage DCI and the associated second-stage DCI. As one example, the UE120may recovering user data based at least in part on the first-stage DCI and the second-stage DCI. Alternatively, or additionally, the UE120may transmit user data based at least in part on the first-stage DCI and the second-stage DCI.

Indicating of an association between the stages of a multi-stage DCI may enable a UE to correctly detect and/or recover each stage and, subsequently, transmit and/or receive communications with the network node. The use of multi-stage DCI, and the indication of an association between the stages, may enable a network node to configure each stage transmission differently (e.g., with different CORESETs and/or different SS sets) to meet operating criteria and preserve air interface resources in a wireless network. Preserving air interface resources may also enable the network node to increase a capacity of the wireless network and/or serve more UEs.

FIG.8is a diagram illustrating an example process800performed, for example, by a UE, in accordance with the present disclosure. Example process800is an example where the UE (e.g., UE120) performs operations associated with associating multi-stage DCI.

As shown inFIG.8, in some aspects, process800may include receiving an indication of an association between first-stage DCI and second-stage DCI (block810). For example, the UE (e.g., using reception component1002and/or communication manager1006, depicted inFIG.10) may receive an indication of an association between first-stage DCI and second-stage DCI, as described above.

As further shown inFIG.8, in some aspects, process800may include recovering the second-stage DCI based at least in part on the indication of the association (block820). For example, the UE (e.g., using communication manager1006, depicted inFIG.10) may recover the second-stage DCI based at least in part on the indication of the association, as described above.

In a first aspect, process800includes receiving first PDCCH configuration information that is associated with the first-stage DCI, and receiving second PDCCH configuration information that is associated with the second-stage DCI, the indication of the association between the first-stage DCI and the second-stage DCI includes the first PDCCH configuration information and the second PDCCH configuration information specifying a same identifier.

In a second aspect, the same identifier is a two-stage DCI SS association identifier, the first PDCCH configuration information includes a first SS set configuration that indicates the two-stage DCI SS association identifier, and the second PDCCH configuration information includes a second SS set configuration that indicates the two-stage DCI SS association identifier.

In a third aspect, the first SS set configuration is different from the second SS set configuration.

In a fourth aspect, the first PDCCH configuration information indicates a first CORESET, and the second PDCCH configuration information indicates a second CORESET that includes one or more different resources than the first CORESET.

In a fifth aspect, the first CORESET is configured with a first bandwidth, and the second CORESET is configured with a second bandwidth that has a different size than the first bandwidth.

In a sixth aspect, the same identifier is a two-stage DCI CORESET association identifier, the first PDCCH configuration information includes a first CORESET configuration that specifies the two-stage DCI CORESET association identifier, and the second PDCCH configuration information includes a second CORESET configuration that specifies the two-stage DCI CORESET association identifier.

In a seventh aspect, the first PDCCH configuration information includes a first SS set configuration that indicates a particular SS set identifier, and the second PDCCH configuration information includes a second SS set configuration that indicates the particular SS set identifier.

In an eighth aspect, process800includes receiving the first-stage DCI based at least in part on a first beamwidth, and receiving the second-stage DCI based at least in part on a second beamwidth that is narrower than the first beamwidth.

In a ninth aspect, process800includes receiving common scheduling information in the first-stage DCI, and receiving transmission-specific scheduling information in the second-stage DCI.

In a tenth aspect, the second-stage DCI is one of multiple second-stage DCIs, and the indication of the association indicates that the first-stage DCI is associated with each second-stage DCI of the multiple second-stage DCIs.

In an eleventh aspect, process800includes receiving first PDCCH configuration information that is associated with the first-stage DCI and the first PDCCH configuration information indicates a particular two-stage DCI association identifier, receiving second PDCCH configuration information for a first second-stage DCI of the multiple second-stage DCI, and the second PDCCH configuration information indicates the particular two-stage DCI association identifier, and receiving third PDCCH configuration information for a second second-stage DCI of the multiple second-stage DCI and the third PDCCH configuration information indicates the particular two-stage DCI association identifier.

In a twelfth aspect, the particular two-stage DCI association identifier includes at least one of a two-stage DCI SS association identifier, or a two-stage DCI CORESET association identifier.

In a thirteenth aspect, the second PDCCH configuration information is different from the third PDCCH configuration information.

In a fourteenth aspect, process800includes receiving the first-stage DCI in a first carrier, and receiving the second-stage DCI in a second carrier.

In a fifteenth aspect, process800includes receiving first PDCCH configuration information for the first-stage DCI that indicates a particular SS set identifier, and receiving second PDCCH configuration information for the second-stage DCI that indicates the particular SS set identifier, the indication of the association being based at least in part on the particular SS set identifier.

In a sixteenth aspect, process800includes recovering user data in the second carrier based at least in part on the first-stage DCI and the second-stage DCI.

In a seventeenth aspect, process800includes recovering the first-stage DCI based at least in part on a first DCI format, and recovering the second-stage DCI is based at least in part on a second DCI format and a DCI format association between the first-stage DCI and the second-stage DCI.

In an eighteenth aspect, process800includes receiving the first-stage DCI, the first-stage DCI indicates a monitoring occasion associated with receiving the second-stage DCI, and receiving the second-stage DCI is based at least in part on the monitoring occasion.

In a nineteenth aspect, the first-stage DCI indicates the monitoring occasion based at least in part on an offset field.

In a twentieth aspect, the offset field indicates a first monitoring occasion and a number of monitoring occasions.

In a twenty-first aspect, process800includes receiving the first-stage DCI, and receiving the second-stage DCI based at least in part on a monitoring window that is based at least in part on the first-stage DCI.

In a twenty-second aspect, process800includes determining a blind detection threshold based at least in part on a monitoring duration associated with the second-stage DCI, and recovering the second-stage DCI based at least in part on the blind detection threshold.

In a twenty-third aspect, determining the blind detection threshold includes determining the blind detection threshold based at least in part on a number of configured PDCCH candidates associated with a search space configuration for the second-stage DCI.

In a twenty-fourth aspect, determining the blind detection threshold includes determining the blind detection threshold based at least in part on a maximum number of DCIs that the UE is configured to receive in the monitoring duration.

In a twenty-fifth aspect, determining the blind detection threshold is based at least in part on at least one of a UE capability, a PDCCH candidate indicated by the first-stage DCI, or a minimum offset associated with the first-stage DCI and second-stage DCI.

FIG.9is a diagram illustrating an example process900performed, for example, by a network node, in accordance with the present disclosure. Example process900is an example where the network node (e.g., network node110) performs operations associated with associating multi-stage DCI.

As shown inFIG.9, in some aspects, process900may include transmitting an indication of an association between first-stage DCI and second-stage DCI (block910). For example, the network node (e.g., using transmission component1104and/or communication manager1106, depicted inFIG.11) may transmit an indication of an association between first-stage DCI and second-stage DCI, as described above.

As further shown inFIG.9, in some aspects, process900may include transmitting at least the first-stage DCI based at least in part on the association (block920). For example, the network node (e.g., using transmission component1104and/or communication manager1106, depicted inFIG.11) may transmit at least the first-stage DCI based at least in part on the association, as described above.

In a first aspect, process900includes transmitting the second-stage DCI based at least in part on the association.

In a second aspect, process900includes transmitting first PDCCH configuration information that is associated with the first-stage DCI, and transmitting second PDCCH configuration information that is associated with the second-stage DCI, the indication of the association between the first-stage DCI and the second-stage DCI includes the first PDCCH configuration information and the second PDCCH configuration information specifying a same identifier.

In a third aspect, the same identifier is a two-stage DCI SS association identifier, the first PDCCH configuration information includes a first SS set configuration that indicates the two-stage DCI SS association identifier, and the second PDCCH configuration information includes a second SS set configuration that indicates the two-stage DCI SS association identifier.

In a fourth aspect, the first SS set configuration is different from the second SS set configuration.

In a fifth aspect, the first PDCCH configuration information indicates a first CORESET, and the second PDCCH configuration information indicates a second CORESET that includes one or more different resources than the first CORESET.

In a sixth aspect, the first CORESET is configured with a first bandwidth, and the second CORESET is configured with a second bandwidth that has a different size than the first bandwidth.

In a seventh aspect, the same identifier is a two-stage DCI CORESET association identifier, the first PDCCH configuration information includes a first CORESET configuration that specifies the two-stage DCI CORESET association identifier, and the second PDCCH configuration information includes a second CORESET configuration that specifies the two-stage DCI CORESET association identifier.

In an eighth aspect, the first PDCCH configuration information includes a first SS set configuration that indicates a particular SS set identifier, and the second PDCCH configuration information includes a second SS set configuration that indicates the particular SS set identifier.

In a ninth aspect, process900includes transmitting the first-stage DCI based at least in part on a first beamwidth, and transmitting the second-stage DCI based at least in part on a second beamwidth that is narrower than the first beamwidth.

In a tenth aspect, process900includes transmitting common scheduling information in the first-stage DCI, and transmitting transmission-specific scheduling information in the second-stage DCI.

In an eleventh aspect, process900includes transmitting the first-stage DCI, the first-stage DCI indicates a monitoring occasion associated with receiving the second-stage DCI, and transmitting the second-stage DCI based at least in part on the monitoring occasion.

In a twelfth aspect, the first-stage DCI indicates the monitoring occasion based at least in part on an offset field.

In a thirteenth aspect, the offset field indicates a first monitoring occasion and a number of monitoring occasions.

In a fourteenth aspect, the offset field indicates a first monitoring occasion that is associated with a monitoring window.

FIG.10is a diagram of an example apparatus1000for wireless communication, in accordance with the present disclosure. The apparatus1000may be a UE, or a UE may include the apparatus1000. In some aspects, the apparatus1000includes a reception component1002, a transmission component1004, and/or a communication manager1006, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager1006is the communication manager140described in connection withFIG.1. As shown, the apparatus1000may communicate with another apparatus1008, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component1002and the transmission component1004.

The communication manager1006may support operations of the reception component1002and/or the transmission component1004. For example, the communication manager1006may receive information associated with configuring reception of communications by the reception component1002and/or transmission of communications by the transmission component1004. Additionally, or alternatively, the communication manager1006may generate and/or provide control information to the reception component1002and/or the transmission component1004to control reception and/or transmission of communications.

The communication manager1006may receive, by way of the reception component1002, an indication of an association between first-stage DCI and second-stage DCI. The communication manager1006may recover the second-stage DCI based at least in part on the indication of the association.

The communication manager1006may receive, by way of the reception component1002, first PDCCH configuration information that is associated with the first-stage DCI. Alternatively, or additionally, the communication manager1006may receive, by way of the reception component1002, second PDCCH configuration information that is associated with the second-stage DCI, and the indication of the association between the first-stage DCI and the second-stage DCI includes the first PDCCH configuration information and the second PDCCH configuration information specifying a same identifier.

The reception component1002may receive the first-stage DCI based at least in part on a first beamwidth. Alternatively, or additionally, the reception component1002may receive the second-stage DCI based at least in part on a second beamwidth that is narrower than the first beamwidth.

The communication manager1006may receive, by way of the reception component1002, common scheduling information in the first-stage DCI. Alternatively, or additionally, the communication manager1006may receive, by way of the reception component1002, transmission-specific scheduling information in the second-stage DCI. In some aspects, the communication manager1006may receive, by way of the reception component1002, first PDCCH configuration information that is associated with the first-stage DCI, and the first PDCCH configuration information indicates a particular two-stage DCI association identifier. In some aspects, the communication manager1006may receive, by way of the reception component1002, second PDCCH configuration information for a first second-stage DCI of the multiple second-stage DCI, and the second PDCCH configuration information indicates the particular two-stage DCI association identifier. At times, the communication manager1006may receive, by way of the reception component1002, third PDCCH configuration information for a second second-stage DCI of the multiple second-stage DCI, and the third PDCCH configuration information indicates the particular two-stage DCI association identifier.

The reception component1002may receive the first-stage DCI in a first carrier. Alternatively, or additionally, the reception component1002may receive the second-stage DCI in a second carrier.

The communication manager1006may receive, by way of the reception component1002, first PDCCH configuration information for the first-stage DCI that indicates a particular SS set identifier. Alternatively, or additionally, the communication manager1006may receive, by way of the reception component1002, second PDCCH configuration information for the second-stage DCI that indicates the particular SS set identifier, and the indication of the association is based at least in part on the particular SS set identifier.

The communication manager1006may recover user data in the second carrier based at least in part on the first-stage DCI and the second-stage DCI. In some aspects, the communication manager1006may recover the first-stage DCI based at least in part on a first DCI format. Alternatively, or additionally, the communication manager1006may recover the second-stage DCI based at least in part on a second DCI format and a DCI format association between the first-stage DCI and the second-stage DCI.

The communication manager1006may receive, by way of the reception component1002, the first-stage DCI, and the first-stage DCI indicates a monitoring occasion associated with receiving the second-stage DCI. The communication manager1006may receive, by way of the reception component1002, the second-stage DCI based at least in part on the monitoring occasion. The communication manager1006may receive, by way of the reception component1002, the first-stage DCI, and the second-stage DCI based at least in part on a monitoring window that is based at least in part on the first-stage DCI.

The communication manager1006may determine a blind detection threshold based at least in part on a monitoring duration associated with the second-stage DCI. Alternatively, or additionally, the communication manager1006may recover the second-stage DCI based at least in part on the blind detection threshold.

FIG.11is a diagram of an example apparatus1100for wireless communication, in accordance with the present disclosure. The apparatus1100may be a network node, or a network node may include the apparatus1100. In some aspects, the apparatus1100includes a reception component1102, a transmission component1104, and/or a communication manager1106, which may be in communication with one another (for example, via one or more buses and/or one or more other components). In some aspects, the communication manager1106is the communication manager150described in connection withFIG.1. As shown, the apparatus1100may communicate with another apparatus1108, such as a UE or a network node (such as a CU, a DU, an RU, or a base station), using the reception component1102and the transmission component1104.

The reception component1102may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus1108. The reception component1102may provide received communications to one or more other components of the apparatus1100. In some aspects, the reception component1102may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus1100. In some aspects, the reception component1102may include one or more antennas, a modem, a demodulator, a MIMO detector, a receive processor, a controller/processor, one or more memories, or a combination thereof, of the network node described in connection withFIG.2. In some aspects, the reception component1102and/or the transmission component1104may include or may be included in a network interface. The network interface may be configured to obtain and/or output signals for the apparatus1100via one or more communications links, such as a backhaul link, a midhaul link, and/or a fronthaul link.

The communication manager1106may support operations of the reception component1102and/or the transmission component1104. For example, the communication manager1106may receive information associated with configuring reception of communications by the reception component1102and/or transmission of communications by the transmission component1104. Additionally, or alternatively, the communication manager1106may generate and/or provide control information to the reception component1102and/or the transmission component1104to control reception and/or transmission of communications.

The communication manager1106may transmit, by way of the transmission component1104, an indication of an association between first-stage DCI and second-stage DCI. The communication manager may transmit, by way of the transmission component1104, at least the first-stage DCI based at least in part on the association. In some aspects, the communication manager1106may transmit, by way of the transmission component1104, the second-stage DCI based at least in part on the association.

The communication manager may transmit, by way of the transmission component1104, first PDCCH configuration information that is associated with the first-stage DCI and second PDCCH configuration information that is associated with the second-stage DCI. In some aspects, the indication of the association between the first-stage DCI and the second-stage DCI includes the communication manager1106specifying a same identifier in the first PDCCH configuration information and the second PDCCH configuration information.

The transmission component1104may transmit the first-stage DCI based at least in part on a first beamwidth. Alternatively, or additionally, the transmission component1104may transmit the second-stage DCI based at least in part on a second beamwidth that is narrower than the first beamwidth.

The communication manager may transmit, by way of the transmission component1104, common scheduling information in the first-stage DCI. Alternatively, or additionally, the communication manager may transmit, by way of the transmission component1104, transmission-specific scheduling information in the second-stage DCI.

The communication manager may transmit, by way of the transmission component1104, the first-stage DCI, and the first-stage DCI indicates a monitoring occasion associated with receiving the second-stage DCI. Alternatively, or additionally, the communication manager may transmit, by way of the transmission component1104, the second-stage DCI based at least in part on the monitoring occasion.

Aspect 1: A method of wireless communication performed by a user equipment (UE), comprising: receiving an indication of an association between first-stage downlink control information (DCI) and second-stage DCI; and recovering the second-stage DCI based at least in part on the indication of the association.

Aspect 2: The method of Aspect 1, further comprising: receiving first physical downlink control channel (PDCCH) configuration information that is associated with the first-stage DCI; and receiving second PDCCH configuration information that is associated with the second-stage DCI, wherein the indication of the association between the first-stage DCI and the second-stage DCI comprises the first PDCCH configuration information and the second PDCCH configuration information specifying a same identifier.

Aspect 3: The method of Aspect 2, wherein the same identifier is a two-stage DCI search space (SS) association identifier, wherein the first PDCCH configuration information comprises a first SS set configuration that indicates the two-stage DCI SS association identifier, and wherein the second PDCCH configuration information comprises a second SS set configuration that indicates the two-stage DCI SS association identifier.

Aspect 4: The method of Aspect 3, wherein the first SS set configuration is different from the second SS set configuration.

Aspect 5: The method of Aspect 3, wherein the first PDCCH configuration information indicates a first control resource set (CORESET), and wherein the second PDCCH configuration information indicates a second CORESET that includes one or more different resources than the first CORESET.

Aspect 6: The method of Aspect 5, wherein the first CORESET is configured with a first bandwidth, and wherein the second CORESET is configured with a second bandwidth that has a different size than the first bandwidth.

Aspect 7: The method of Aspect 2, wherein the same identifier is a two-stage DCI control resource set (CORESET) association identifier, wherein the first PDCCH configuration information comprises a first CORESET configuration that specifies the two-stage DCI CORESET association identifier, and wherein the second PDCCH configuration information comprises a second CORESET configuration that specifies the two-stage DCI CORESET association identifier.

Aspect 8: The method of Aspect 7, wherein the first PDCCH configuration information comprises a first search space (SS) set configuration that indicates a particular SS set identifier, and wherein the second PDCCH configuration information comprises a second SS set configuration that indicates the particular SS set identifier.

Aspect 9: The method of any of Aspects 1-8, further comprising: receiving the first-stage DCI based at least in part on a first beamwidth; and receiving the second-stage DCI based at least in part on a second beamwidth that is narrower than the first beamwidth.

Aspect 10: The method of any of Aspects 1-9, further comprising: receiving common scheduling information in the first-stage DCI; and receiving transmission-specific scheduling information in the second-stage DCI.

Aspect 11: The method of any of Aspects 1-10, wherein the second-stage DCI is one of multiple second-stage DCIs, and wherein the indication of the association indicates that the first-stage DCI is associated with each second-stage DCI of the multiple second-stage DCIs.

Aspect 12: The method of Aspect 11, further comprising: receiving first physical downlink control channel (PDCCH) configuration information that is associated with the first-stage DCI, wherein the first PDCCH configuration information indicates a particular two-stage DCI association identifier; receiving second PDCCH configuration information for a first second-stage DCI of the multiple second-stage DCI, wherein the second PDCCH configuration information indicates the particular two-stage DCI association identifier; and receiving third PDCCH configuration information for a second second-stage DCI of the multiple second-stage DCI, wherein the third PDCCH configuration information indicates the particular two-stage DCI association identifier.

Aspect 13: The method of Aspect 12, wherein the particular two-stage DCI association identifier comprises at least one of: a two-stage DCI search space (SS) association identifier, or a two-stage DCI control resource set (CORESET) association identifier.

Aspect 14: The method of Aspect 12, wherein the second PDCCH configuration information is different from the third PDCCH configuration information.

Aspect 15: The method of any of Aspects 1-14, further comprising: receiving the first-stage DCI in a first carrier; and receiving the second-stage DCI in a second carrier.

Aspect 16: The method of Aspect 14, further comprising: receiving first physical downlink control channel (PDCCH) configuration information for the first-stage DCI that indicates a particular search space (SS) set identifier; and receiving second PDCCH configuration information for the second-stage DCI that indicates the particular SS set identifier, wherein the indication of the association is based at least in part on the particular SS set identifier.

Aspect 17: The method of Aspect 15, further comprising: recovering user data in the second carrier based at least in part on the first-stage DCI and the second-stage DCI.

Aspect 18: The method of any of Aspects 1-17, further comprising: recovering the first-stage DCI based at least in part on a first DCI format; and recovering the second-stage DCI based at least in part on a second DCI format and a DCI format association between the first-stage DCI and the second-stage DCI.

Aspect 19: The method of any of Aspects 1-18, further comprising: receiving the first-stage DCI, wherein the first-stage DCI indicates a monitoring occasion associated with receiving the second-stage DCI; and receiving the second-stage DCI based at least in part on the monitoring occasion.

Aspect 20: The method of Aspect 19, wherein the first-stage DCI indicates the monitoring occasion based at least in part on an offset field.

Aspect 21: The method of Aspect 20, wherein the offset field indicates a starting monitoring occasion and a number of monitoring occasions.

Aspect 22: The method of any of Aspects 1-21, further comprising: receiving the first-stage DCI; and receiving the second-stage DCI based at least in part on a monitoring window that is based at least in part on the first-stage DCI.

Aspect 23: The method of Aspect 22, wherein the monitoring window comprises: a radio resource control (RRC) configured monitoring window, or a communication standard rule-based monitoring window.

Aspect 24: The method of any of Aspects 1-23, further comprising: determining a blind detection threshold based at least in part on a monitoring duration associated with the second-stage DCI; and recovering the second-stage DCI based at least in part on the blind detection threshold.

Aspect 25: The method of Aspect 24, wherein determining the blind detection threshold comprises: determining the blind detection threshold based at least in part on a number of configured physical downlink control channel (PDCCH) candidates associated with a search space configuration for the second-stage DCI.

Aspect 26: The method of Aspect 24, wherein determining the blind detection threshold comprises: determining the blind detection threshold based at least in part on a maximum number of DCIs that the UE is configured to receive in the monitoring duration.

Aspect 27: The method of Aspect 26, wherein determining the blind detection threshold is based at least in part on at least one of: a UE capability, a PDCCH candidate indicated by the first-stage DCI, or a minimum offset associated with the first-stage DCI and second-stage DCI.

Aspect 28: A method of wireless communication performed by a network node, comprising: transmitting an indication of an association between first-stage downlink control information (DCI) and second-stage DCI; and transmitting at least the first-stage DCI based at least in part on the association.

Aspect 29: The method of Aspect 28, further comprising: transmitting the second-stage DCI based at least in part on the association.

Aspect 30: The method of any of Aspects 28-29, further comprising: transmitting first physical downlink control channel (PDCCH) configuration information that is associated with the first-stage DCI; and transmitting second PDCCH configuration information that is associated with the second-stage DCI, wherein the indication of the association between the first-stage DCI and the second-stage DCI comprises the first PDCCH configuration information and the second PDCCH configuration information specifying a same identifier.

Aspect 31: The method of Aspect 30, wherein the same identifier is a two-stage DCI search space (SS) association identifier, wherein the first PDCCH configuration information comprises a first SS set configuration that indicates the two-stage DCI SS association identifier, and wherein the second PDCCH configuration information comprises a second SS set configuration that indicates the two-stage DCI SS association identifier.

Aspect 32: The method of Aspect 31, wherein the first SS set configuration is different from the second SS set configuration.

Aspect 33: The method of Aspect 31, wherein the first PDCCH configuration information indicates a first control resource set (CORESET), and wherein the second PDCCH configuration information indicates a second CORESET that includes one or more different resources than the first CORESET.

Aspect 34: The method of Aspect 33, wherein the first CORESET is configured with a first bandwidth, and wherein the second CORESET is configured with a second bandwidth that has a different size than the first bandwidth.

Aspect 35: The method of Aspect 30, wherein the same identifier is a two-stage DCI control resource set (CORESET) identifier, wherein the first PDCCH configuration information comprises a first CORESET configuration that specifies the two-stage DCI CORESET association identifier, and wherein the second PDCCH configuration information comprises a second CORESET configuration that specifies the two-stage DCI CORESET association identifier.

Aspect 36: The method of Aspect 35, wherein the first PDCCH configuration information comprises a first search space (SS) set configuration that indicates a particular SS set identifier, and wherein the second PDCCH configuration information comprises a second SS set configuration that indicates the particular SS set identifier.

Aspect 37: The method of any of Aspects 28-36, further comprising: transmitting the first-stage DCI based at least in part on a first beamwidth; and transmitting the second-stage DCI based at least in part on a second beamwidth that is narrower than the first beamwidth.

Aspect 38: The method of any of Aspects 28-37, further comprising: transmitting common scheduling information in the first-stage DCI; and transmitting transmission-specific scheduling information in the second-stage DCI.

Aspect 39: The method of any of Aspects 28-38, further comprising: transmitting the first-stage DCI, wherein the first-stage DCI indicates a monitoring occasion associated with receiving the second-stage DCI; and transmitting the second-stage DCI based at least in part on the monitoring occasion.

Aspect 40: The method of Aspect 39, wherein the first-stage DCI indicates the monitoring occasion based at least in part on an offset field.

Aspect 41: The method of Aspect 40, wherein the offset field indicates a first monitoring occasion and a number of monitoring occasions.

Aspect 42: The method of Aspect 40, wherein the offset field indicates a first monitoring occasion that is associated with a monitoring window.

Aspect 45: A device for wireless communication, comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured, individually or collectively, to perform the method of one or more of Aspects 1-27.

Aspect 46: A device for wireless communication, comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured, individually or collectively, to perform the method of one or more of Aspects 28-42.