name: PUCCH
full_form: Physical Uplink Control Channel
context: PUCCH repetition, up to two sets of power control parameters in FR1 or up to two PUCCH-SpatialRelationInfo in FR2 can be activated per PUCCH resource or per PUCCH resource group via MAC-CE. In addition, multi-TRP PUCCH repetition can be configured by intra-slot PUCCH repetition as well as inter-slot PUCCH repetition for all PUCCH formats. Based on the number of activated PUCCH-SpatialRelationInfo or set of power control parameters for the scheduled PUCCH resource, dynamic switching between single-TRP PUCCH repetition and multi-TRP PUCCH repetition can be supported. Separate power control for multi-TRP PUCCH repetition is supported by two activated PUCCH-SpatialRelationInfo or two activated sets of power control parameters. Furthermore, up to two TPC field for PUCCH can be supported and each TPC field is applied for each closed loop index. In Rel-17, multi-TRP PUSCH repetition is supported with up to two SRS resource sets with usage set to âcodebookâ or ânonCodebookâ. If UE is provided
description: The Physical Uplink Control Channel (PUCCH) is a communication link in the uplink direction, used for transmitting control information from the user equipment (UE) to the base station. It plays a crucial role in the 5G New Radio (NR) system, enabling the UE to send control signals such as scheduling requests, channel state information, and hybrid automatic repeat request (HARQ) acknowledgments.
explanation: The context provided highlights PUCCH's role in transmitting control information from the UE to the base station, which justifies its classification as a Connection. The text mentions various aspects of PUCCH configuration and operation, such as repetition, power control parameters, and spatial relation information, further emphasizing its function as a communication link.
section_title: 11.1	Further enhancements on MIMO for NR
biotag_Context: B-Connection,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,B-Measurement,O,O,O,O,B-Connection,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,B-Connection,O,O,O,O,O,B-Connection,O,O,O,B-Connection,O,O,O,O,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,B-Connection,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,B-Protocol,O,O,B-Connection,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Connection,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O,B-Device,O,O
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,B-Technology,B-Technology,I-Technology,O,O,O,O,B-Device,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O