specviewer.org TS 38.331 ASN.1 index PUSCH-ServingCellConfig

PUSCH-ServingCellConfig

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

PUSCH-ServingCellConfig 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 v18.1.0 (2024-04)

Definition

The IE PUSCH-ServingCellConfig is used to configure UE specific PUSCH parameters that are common across the UE's BWPs of one serving cell.

PUSCH-ServingCellConfig ::=             SEQUENCE {
    codeBlockGroupTransmission              SetupRelease { PUSCH-CodeBlockGroupTransmission }       OPTIONAL,   -- Need M
    rateMatching                            ENUMERATED {limitedBufferRM}                            OPTIONAL,   -- Need S
    xOverhead                               ENUMERATED {xoh6, xoh12, xoh18}                         OPTIONAL,   -- Need S
    ...,
    [[
        maxMIMO-Layers                          INTEGER (1..4)                                          OPTIONAL,   -- Need M
        processingType2Enabled                  BOOLEAN                                                 OPTIONAL    -- Need M
    ]],
    [[
        maxMIMO-LayersDCI-0-2-r16               SetupRelease { MaxMIMO-LayersDCI-0-2-r16}               OPTIONAL    -- Need M
    ]],
    [[
        nrofHARQ-ProcessesForPUSCH-r17          ENUMERATED {n32}                                        OPTIONAL,   -- Need R
        uplinkHARQ-mode-r17                     SetupRelease { UplinkHARQ-mode-r17}                     OPTIONAL    -- Need M
    ]],
    [[
        maxMIMO-Layers-v1810                    INTEGER (5..8)                                          OPTIONAL,   -- Need R
        maxMIMO-LayersforSDM-r18                INTEGER (1..2)                                          OPTIONAL,   -- Need R
        maxMIMO-LayersforSDM-DCI-0-2-r18        INTEGER (1..2)                                          OPTIONAL,   -- Need R
        maxMIMO-LayersforSFN-r18                INTEGER (1..2)                                          OPTIONAL,   -- Need R
        maxMIMO-LayersforSFN-DCI-0-2-r18        INTEGER (1..2)                                          OPTIONAL    -- Need R
    ]]
}

Fields (13)

FieldDescription
codeBlockGroupTransmission
SetupRelease { PUSCH-CodeBlockGroupTransmission } · OPTIONAL Need M
Enables and configures code-block-group (CBG) based transmission (see TS 38.214 [19], clause 6.1.5). The network does not configure this field if the SCS of at least one UL BWP configured in the cell is 480 or 960 kHz.
rateMatching
ENUMERATED {limitedBufferRM} · OPTIONAL Need S
Enables LBRM (Limited buffer rate-matching). When the field is absent the UE applies FBRM (Full buffer rate-matchingLBRM) (see TS 38.212 [17], clause 5.4.2).
xOverhead
ENUMERATED {xoh6, xoh12, xoh18} · OPTIONAL Need S
If the field is absent, the UE applies the value 0 (see TS 38.214 [19], clause 6.1.4.2).
maxMIMO-Layers
INTEGER (1..4) · OPTIONAL Need M
since v15.4.0
Indicates the maximum MIMO layer to be used for PUSCH in all BWPs of the corresponding UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRank to the same value. The field maxMIMO-Layers refers to DCI format 0_1. If network configures maxMIMO-Layers-v1810 the UE ignores maxMIMO-Layers (without suffix).
processingType2Enabled
BOOLEAN · OPTIONAL Need M
since v15.4.0
Enables configuration of advanced processing time capability 2 for PUSCH (see 38.214 [19], clause 6.4).
maxMIMO-LayersDCI-0-2-r16
SetupRelease { MaxMIMO-LayersDCI-0-2-r16} · OPTIONAL Need M
since v16.2.0
Indicates the maximum MIMO layer to be used for PUSCH for DCI format 0_2 in all BWPs of the corresponding UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRankDCI-0-2 to the same value.
nrofHARQ-ProcessesForPUSCH-r17
ENUMERATED {n32} · OPTIONAL Need R
since v17.0.0
The number of HARQ processes to be used on the PUSCH of a serving cell. Value n32 corresponds to 32 HARQ processes. If the field is absent, the UE uses 16 HARQ processes (see TS 38.214 [19], clause 6.1).
uplinkHARQ-mode-r17
SetupRelease { UplinkHARQ-mode-r17} · OPTIONAL Need M
since v17.0.0
Used to set the HARQ mode per HARQ process ID, see TS 38.321 [3]. The first/leftmost bit corresponds to HARQ process ID 0, the next bit to HARQ process ID 1 and so on. Bits corresponding to HARQ process IDs that are not configured shall be ignored. A bit set to one identifies a HARQ process with HARQmodeA and a bit set to zero identifies a HARQ process with HARQ modeB . This field applies for SRBs and DRBs.
maxMIMO-Layers-v1810
INTEGER (5..8) · OPTIONAL Need R
since v18.1.0
Indicates the maximum MIMO layer to be used for PUSCH in all BWPs of the corresponding UL of this serving cell (see TS 38.212 [17], clause 5.4.2.1). If present, the network sets maxRank to the same value. The field maxMIMO-Layers refers to DCI format 0_1. If network configures maxMIMO-Layers-v1810 the UE ignores maxMIMO-Layers (without suffix).
maxMIMO-LayersforSDM-r18
INTEGER (1..2) · OPTIONAL Need R
since v18.0.0
Parameter to indicate maximal number of MIMO layers of each panel for PUSCH with SDM scheme for NCB PUSCH
maxMIMO-LayersforSDM-DCI-0-2-r18
INTEGER (1..2) · OPTIONAL Need R
since v18.0.0
Parameter to indicate maximal number of MIMO layers of each panel for PUSCH with SDM scheme for DCI format 0_2 for NCB PUSCH
maxMIMO-LayersforSFN-r18
INTEGER (1..2) · OPTIONAL Need R
since v18.0.0
Parameter to indicate maximal number of MIMO layers of each panel for PUSCH with SFN scheme for NCB PUSCH
maxMIMO-LayersforSFN-DCI-0-2-r18
INTEGER (1..2) · OPTIONAL Need R
since v18.0.0
Parameter to indicate maximal number of MIMO layers of each panel for PUSCH with SFN scheme for DCI format 0_2 for NCB PUSCH

Used by (1)

Uses (4)

In the viewer