specviewer.org TS 38.331 ASN.1 index PUCCH-ConfigCommon

PUCCH-ConfigCommon

RRC IE · TS 38.331 v19.4.0 (2026-09) · clause 6.3.2

PUCCH-ConfigCommon is an RRC information element of 3GPP TS 38.331 (38331), the 5G NR Radio Resource Control (RRC) protocol.

First seen v15.1.0 (2018-04) · Last changed v19.0.0 (2025-10)

Definition

The IE PUCCH-ConfigCommon is used to configure the cell specific PUCCH parameters.

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
    ]],
    [[
        p0-nominal-SBFD-r19                 INTEGER (-202..24)                                   OPTIONAL    -- Need R
    ]]
}

Fields (9)

FieldDescription
pucch-ResourceCommon
INTEGER (0..15) · OPTIONAL Cond InitialBWP-Only
An entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters. The UE uses those PUCCH resources until it is provided with a dedicated PUCCH-Config (e.g. during initial access) on the initial uplink BWP. Once the network provides a dedicated PUCCH-Config for that bandwidth part the UE applies that one instead of the one provided in this field (see TS 38.213 [13], clause 9.2).
pucch-GroupHopping
ENUMERATED { neither, enable, disable }
Configuration of group- and sequence hopping for all the PUCCH formats 0, 1, 3 and 4. Value neither implies neither group or sequence hopping is enabled. Value enable enables group hopping and disables sequence hopping. Value disable disables group hopping and enables sequence hopping (see TS 38.211 [16], clause 6.3.2.2).
hoppingId
INTEGER (0..1023) · OPTIONAL Need R
Cell-specific scrambling ID for group hopping and sequence hopping if enabled, see TS 38.211 [16], clause 6.3.2.2.
p0-nominal
INTEGER (-202..24) · OPTIONAL Need R
Power control parameter P0 for PUCCH transmissions. Value in dBm. Only even values (step size 2) allowed (see TS 38.213 [13], clause 7.2).
nrofPRBs
INTEGER (1..16) · OPTIONAL Need R
since v17.0.0
Indicates the number of PRBs used per PUCCH resource for PUCCH format 0 and format 1 in FR2-2, see TS 38.213 [13], clause 9.2.1.
intra-SlotFH-r17
ENUMERATED {fromLowerEdge, fromUpperEdge} · OPTIONAL Cond InitialBWP-RedCapOnly
since v17.0.0
In case a separate initial UL BWP is configured for (e)RedCap UEs, the presence of this parameter indicates whether intra-slot PUCCH frequency hopping within the separate initial UL BWP in the common PUCCH resource is enabled for (e)RedCap UEs. If this field is absent, intra-slot PUCCH frequency hopping within RedCap-specific initial UL BWP is enabled. If this field is present, intra-slot PUCCH frequency hopping within RedCap-specific initial UL BWP is disabled and each PUCCH resource is mapped to a single PRB on one side of the UL BWP and this parameter determines whether the PRB index in the PRB mapping is counted in increasing order from the lower edge or in decreasing order from the upper edge of the UL BWP.
pucch-ResourceCommonRedCap-r17
INTEGER (0..15) · OPTIONAL Cond InitialBWP-RedCap
since v17.2.0
An entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters for (e)RedCap UEs. The UE uses those PUCCH resources until it is provided with a dedicated PUCCH-Config (e.g. during initial access) on the initial uplink BWP. Once the network provides a dedicated PUCCH-Config for that bandwidth part the UE applies that one instead of the one provided in this field (see TS 38.213 [13], clause 9.2).
additionalPRBOffset-r17
ENUMERATED {n2, n3, n4, n6, n8, n9, n10, n12} · OPTIONAL Cond InitialBWP-RedCapOnly
since v17.1.0
When intra-slot PUCCH frequency hopping within RedCap-specific initial UL BWP is disabled, each common PUCCH resource is mapped to a single PRB on one side of the UL BWP. This parameter determines an additional PRB offset in the PRB mapping for the PUCCH resource. If the field is not configured, the UE shall assume an additional PRB offset of zero.
p0-nominal-SBFD-r19
INTEGER (-202..24) · OPTIONAL Need R
since v19.0.0
Configures separate power control parameter P0 for PUCCH transmissions in SBFD symbols.

Used by (1)

In the viewer