name: PUSCH
full_form: Physical Uplink Shared Channel
context: not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, and the PUSCH transmission is in a slot for PUSCH transmission of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots. - When pusch-WindowRestart is enabled, the start of a new actual TDW is the first symbol of the PUSCH transmission after the event which causes power consistency and phase continuity not to be maintained across PUSCH transmissions of PUSCH repetition type A scheduled by DCI format 0_1 or 0_2, or PUSCH repetition Type A with a configured grant, or PUSCH repetition type B or TB processing over multiple slots within the nominal TDW, and the PUSCH transmission is in a slot for PUSCH transmission of PUSCH
description: The Physical Uplink Shared Channel (PUSCH) is a communication link between the user equipment (UE) and the base station (eNodeB or gNB) in the uplink direction, used for transmitting uplink data and control information. It is a shared channel, meaning multiple UEs can share the same PUSCH resource.
explanation: PUSCH is classified as a Connection because it facilitates communication between the UE and the base station in the uplink direction, enabling the transmission of data and control information.
section_title: 6.1.7UE procedure for determining time domain windows for bundling DM-RS
biotag_Context: O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,B-Message,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,B-Message,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,B-Connection,O,O,O,O,O,B-Message,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,B-Connection
biotag_Description: O,B-Connection,I-Connection,I-Connection,I-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,O,O,O,O,O,O,O,O,O,O,O,O,B-Device,O,O,O,O,B-Connection,O