name: CG-DFI
full_form: CG - Downlink Feedback Information
context: transmission, by a number of symbols provided by cg-minDFI-Delay. For an initial transmission by a UE of a transport block in a PUSCH configured by ConfiguredGrantConfig, if the UE receives a CG-DFI that provides HARQ-ACK information for the transport block, the UE assumes that the transport block was correctly decoded if the HARQ-ACK information value is ACK; otherwise, the UE assumes that the transport block was not correctly decoded. For a PUSCH transmission scheduled by a DCI format, if the UE receives a CG-DFI that provides HARQ-ACK information for the transport block, the UE assumes that the transport block was correctly decoded if the HARQ-ACK information value is ACK; otherwise, the UE assumes that the transport block was not correctly decoded. For a PUSCH transmission scheduled by a DCI format, HARQ-ACK information for a transport block of a corresponding HARQ process number is valid if a first symbol of the PDCCH reception is after a last symbol of the PUSCH transmission by
description: CG-DFI (CG - Downlink Feedback Information) is a signaling message sent in the downlink direction. It provides feedback on the decoding status of transport blocks transmitted over the Physical Uplink Shared Channel (PUSCH). This information is essential for Hybrid Automatic Repeat Request-Acknowledgment (HARQ-ACK) procedures, allowing the User Equipment (UE) to confirm if the base station successfully decoded a transport block.
explanation: The text describes CG-DFI as a message carrying feedback information about decoding status. It's involved in HARQ-ACK procedures, which are communication mechanisms between network components. This clearly classifies it as a Message entity type.
section_title: 10.5HARQ-ACK information for PUSCH transmissions
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Device,O,O,B-Message,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Message,O,O,O,B-Device,O,O,B-Message,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Message,O,B-Protocol,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Connection,O,O
biotag_Description: B-Message,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,O,B-Connection,I-Connection,I-Connection,I-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O