name: PDSCH
full_form: Physical Downlink Shared Channel
context: with a semi-static CFI for a given TTI length, the UE is not expected to decode PCFICH for that TTI length. PDSCH repetition To improve the reliability of the DL data channel, PDSCH (Physical Downlink Shared Channel) repetition can be configured to a UE for a given TTI length. If configured, the PDSCH DCI format 1A or 7-1x monitored by the UE on the user specific search space indicates K consecutive PDSCH transmissions with the same Resource Block (RB) allocation, Modulation and Coding Scheme (MCS) and HARQ process, where K takes a value in {1, 2, 3, 4 or 6}. Thus, the number of PDSCH transmissions for a given transport block is changed dynamically as shown in the figure below. The HARQ-ACK feedback for the transport block is sent only once with the timing given by the Kth PDSCH transmission. Only the Redundancy Version (RV) can be different within the window of K transmissions, if configured accordingly. A maximum rank of 2 is supported with slot/subslot PDSCH repetition and DMRS
description: The Physical Downlink Shared Channel (PDSCH) is a communication link between the eNodeB and the User Equipment (UE) in the downlink direction, used for transmitting shared channel data. It is characterized by its ability to repeat transmissions to improve reliability.
explanation: Given the context of PDSCH repetition for improving reliability of DL data channel, it is clear that PDSCH refers to a communication link or connection between network endpoints, making it a Connection entity type.
section_title: 6.2	Highly Reliable Low Latency Communication for LTE
biotag_Context: O,O,O,O,O,O,O,B-Parameter,O,O,B-Device,O,O,O,O,O,B-Connection,O,O,B-Parameter,O,B-Connection,O,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,B-Connection,O,O,O,O,O,O,O,O,B-Device,O,O,O,B-Parameter,O,O,O,O,B-Connection,B-Message,O,O,O,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Parameter,I-Parameter,I-Parameter,I-Parameter,O,O,B-Protocol,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,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,B-Parameter,I-Parameter,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,B-Technology
biotag_Description: O,B-Connection,I-Connection,I-Connection,I-Connection,O,O,O,O,O,O,O,B-Network Function,O,O,B-Device,I-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O