name: PUCCH
full_form: Physical Uplink Control Channel
context: The IE PUCCH-ConfigCommon is used to configure the cell specific PUCCH parameters. PUCCH-ConfigCommon information element -- ASN1START -- TAG-PUCCH-CONFIGCOMMON-START PUCCH-ConfigCommon ::= SEQUENCE { pucch-ResourceCommon INTEGER (0..15) OPTIONAL, -- Cond InitialBWP-Only pucch-GroupHopping ENUMERATED { neither, enable, disable }, hoppingId INTEGER (0..1023) OPTIONAL, -- Need R p0-nominal INTEGER (-202..24) OPTIONAL, -- Need R ..., [[ nrofPRBs INTEGER (1..16) OPTIONAL, -- Need R intra-SlotFH-r17 ENUMERATED {fromLowerEdge, fromUpperEdge} OPTIONAL, -- Cond InitialBWP-RedCapOnly pucch-ResourceCommonRedCap-r17 INTEGER (0..15) OPTIONAL, -- Cond InitialBWP-RedCap additionalPRBOffset-r17 ENUMERATED {n2, n3, n4, n6, n8, n9, n10, n12} OPTIONAL -- Cond InitialBWP-RedCapOnly ]] } -- TAG-PUCCH-CONFIGCOMMON-STOP -- ASN1STOP
description: The Physical Uplink Control Channel (PUCCH) is a channel in the uplink direction used for transmitting control information from the user equipment to the base station. It carries crucial data such as scheduling requests, Hybrid Automatic Repeat Request (HARQ) acknowledgments, and Channel State Information (CSI). The configuration of PUCCH parameters at the cell level is facilitated through the PUCCH-ConfigCommon information element, which includes settings for resource allocation, hopping patterns, transmission power control, and more. These configurations are essential for efficient use of radio resources and maintaining optimal network performance.
explanation: PUCCH is classified as a Channel because it refers to a specific path or medium through which data is transmitted in the uplink direction within the context of 3GPP specifications. The detailed configuration options provided further emphasize its role as a communication channel, highlighting aspects such as resource allocation and transmission characteristics.
section_title: â PUCCH-ConfigCommon
biotag_Context: O,B-Message,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,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,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
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,B-Protocol,I-Protocol,I-Protocol,I-Protocol,O,O,O,B-Parameter,I-Parameter,I-Parameter,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,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O