name: DCI
full_form: Downlink Control Information
context: In Multiple Transmit/Receive Point (multi-TRP) operation, a serving cell can schedule the UE from two TRPs, providing better coverage, reliability and/or data rates for PDSCH, PDCCH, PUSCH, and PUCCH. There are two different operation modes to schedule multi-TRP PDSCH transmissions: single-DCI and multi-DCI. For both modes, control of uplink and downlink operation can be done by physical layer and MAC layer, within the configuration provided by the RRC layer. In single-DCI mode, the UE is scheduled by the same DCI for both TRPs and in multi-DCI mode, the UE is scheduled by independent DCIs from each TRP. There are two different operation modes for multi-TRP PDCCH: PDCCH repetition as in Clause 5.2.3 and Single Frequency Network (SFN) based PDCCH transmission. In both modes, the UE can receive two PDCCH transmissions, one from each TRP, carrying the same DCI. In PDCCH repetition mode, the UE can receive the two PDCCH transmissions carrying the same DCI from two linked search spaces each associated with a different CORESET. In SFN based PDCCH transmission mode, the UE can receive the two PDCCH transmissions carrying the same DCI from a single search space/CORESET using different TCI states. For multi-TRP PUSCH repetition, according to indications in a single DCI or in a semi-static configured grant provided over RRC, the UE performs PUSCH transmission of the same contents toward two TRPs with corresponding beam directions associated with different spatial relations. For multi-TRP PUCCH repetition, the UE performs PUCCH transmission of the same contents toward two TRPs with corresponding beam directions associated with different spatial relations. For inter-cell multi-TRP operation, for multi-DCI PDSCH transmission, one or more TCI states can be associated with SSB with a PCI different from the serving cell PCI. The activated TCI states can be associated with at most one PCI different from the serving cell PCI at a time. For inter-cell and intra-cell multi-DCI multi-TRP operation, up to two TAGs with associated TAG IDs can be configured per serving cell. Each UL/Joint TCI state is associated with a TAG ID and the UE applies the timing advance of the TAG ID associated with the UL/joint TCI state utilized for UL transmission. For single-DCI multi-TRP Simultaneous Transmission with Multi-Panel (STxMP) Spatial Domain Multiplexing (SDM) PUSCH transmission, different layers of one PUSCH are separately transmitted towards two TRPs. For single-DCI multi-TRP STxMP SFN PUSCH transmission, same layers of one PUSCH are transmitted towards two TRPs. For multi-DCI based multi-TRP STxMP PUSCH+PUSCH transmission, two PUSCHs are transmitted towards two TRPs. For single-DCI multi-TRP STxMP SFN PUCCH transmission, one PUCCH is transmitted towards two TRPs.
description: Downlink Control Information (DCI) refers to the control signaling data transmitted from a base station to user equipment in the downlink direction. It contains essential information for the UE to properly receive and process downlink data transmissions, such as resource allocation, modulation scheme, and transmission format. In the context of multi-TRP operation, DCI plays a crucial role in scheduling and controlling multiple transmit/receive points for improved coverage, reliability, and data rates.
explanation: DCI is classified as a Message because it represents specific signaling data exchanged between network components (base station and UE) to manage downlink transmissions. The provided context highlights the importance of DCI in multi-TRP operations, where it enables efficient scheduling and control of multiple transmit/receive points.
section_title: 6.12 Multiple Transmit/Receive Point Operation
biotag_Context: O,O,B-Network Function,I-Network Function,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Device,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Technology,I-Technology,I-Technology,O,O,B-Connection,O,O,O,O,O,B-Device,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Device,O,O,O,O,B-Connection,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,B-Connection,O,O,O,B-Device,O,O,O,O,B-Connection,O,O,O,O,B-Message,O,O,O,O,O,O,O,B-Parameter,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,B-Device,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Device,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Parameter,O,O,O,O,O,B-Miscellaneous,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Miscellaneous,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,B-Miscellaneous,B-Parameter,O,O,B-Device,O,O,O,O,O,O,B-Miscellaneous,B-Parameter,O,O,O,O,B-Parameter,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Connection,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,B-Connection,O,O,B-Connection,O,O,O,O,O
biotag_Description: B-Message,I-Message,I-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Message,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O