BWP-UplinkDedicated

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

BWP-UplinkDedicated 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.1.0 (2026-01)

Definition

The IE BWP-UplinkDedicated is used to configure the dedicated (UE specific) parameters of an uplink BWP.

BWP-UplinkDedicated ::=             SEQUENCE {
    pucch-Config                        SetupRelease { PUCCH-Config }                                           OPTIONAL,   -- Need M
    pusch-Config                        SetupRelease { PUSCH-Config }                                           OPTIONAL,   -- Need M
    configuredGrantConfig               SetupRelease { ConfiguredGrantConfig }                                  OPTIONAL,   -- Need M
    srs-Config                          SetupRelease { SRS-Config }                                             OPTIONAL,   -- Need M
    beamFailureRecoveryConfig           SetupRelease { BeamFailureRecoveryConfig }                              OPTIONAL,   -- Cond SpCellOnly
    ...,
    [[
        sl-PUCCH-Config-r16                 SetupRelease { PUCCH-Config }                                           OPTIONAL,   -- Need M
        cp-ExtensionC2-r16                  INTEGER (1..28)                                                         OPTIONAL,   -- Need R
        cp-ExtensionC3-r16                  INTEGER (1..28)                                                         OPTIONAL,   -- Need R
        useInterlacePUCCH-PUSCH-r16         ENUMERATED {enabled}                                                    OPTIONAL,   -- Need R
        pucch-ConfigurationList-r16         SetupRelease { PUCCH-ConfigurationList-r16 }                            OPTIONAL,   -- Need M
        lbt-FailureRecoveryConfig-r16       SetupRelease { LBT-FailureRecoveryConfig-r16 }                          OPTIONAL,   -- Need M
        configuredGrantConfigToAddModList-r16                 ConfiguredGrantConfigToAddModList-r16                 OPTIONAL,   -- Need N
        configuredGrantConfigToReleaseList-r16                ConfiguredGrantConfigToReleaseList-r16                OPTIONAL,   -- Need N
        configuredGrantConfigType2DeactivationStateList-r16   ConfiguredGrantConfigType2DeactivationStateList-r16   OPTIONAL    -- Need R
    ]],
    [[
        ul-TCI-StateList-r17                CHOICE {
            explicitlist                        SEQUENCE {
                ul-TCI-ToAddModList-r17             SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-State-r17          OPTIONAL,   -- Need N
                ul-TCI-ToReleaseList-r17            SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-StateId-r17        OPTIONAL    -- Need N
            },
            unifiedTCI-StateRef-r17         ServingCellAndBWP-Id-r17
        }                                                                                                           OPTIONAL,  -- Need R
        ul-powerControl-r17                Uplink-powerControlId-r17                                                OPTIONAL,  -- Cond NoTCI-PC
        pucch-ConfigurationListMulticast1-r17  SetupRelease { PUCCH-ConfigurationList-r16 }                         OPTIONAL,  -- Need M
        pucch-ConfigurationListMulticast2-r17  SetupRelease { PUCCH-ConfigurationList-r16 }                         OPTIONAL   -- Need M
    ]],
    [[
        pucch-ConfigMulticast1-r17          SetupRelease { PUCCH-Config }                                           OPTIONAL,  -- Need M
        pucch-ConfigMulticast2-r17          SetupRelease { PUCCH-Config }                                           OPTIONAL   -- Need M
    ]],
    [[
        pathlossReferenceRSToAddModList-r17     SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-r17
        OPTIONAL, -- Need N
        pathlossReferenceRSToReleaseList-r17    SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-Id-r17
        OPTIONAL  -- Need N
    ]],
    [[
        sbfd-Config2-Transmission-r19       ENUMERATED {enabled}                                                    OPTIONAL,   -- Need S
        sbfd-Config2-PUSCH-RB-Offset-r19    INTEGER(0..maxNrofPhysicalResourceBlocks-1)                             OPTIONAL,   -- Need R
        ul-Muting-NonSBFD-Symbol-r19        ENUMERATED {enabled}                                                    OPTIONAL,   -- Need S
        twoTA-Without-MultiDCI-MultiTRP-r19  ENUMERATED {enabled}                                                   OPTIONAL   -- Need R
    ]]
}

Candidate change requests of v19.1.0

The CRs whose title or cover names this change, strong and likely matches only.

CR 5499 r3 (strong): Corrections to WI SBFD

Fields (30)

Field	Description
pucch-Config SetupRelease { PUCCH-Config } · OPTIONAL Need M	PUCCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL, the network configures PUCCH only on the BWPs of one of the uplinks (normal UL or SUL). The network configures PUCCH-Config at least on non-initial BWP(s) for SpCell and on all BWP(s) for PUCCH SCell. If supported by the UE, the network may configure at most one additional SCell of a cell group with PUCCH-Config (i.e. PUCCH SCell). If PUCCH cell switching is supported by the UE, the network may configure two TDD serving cells with PUCCH-Config within each PUCCH group. For supporting PUCCH cell switching in the PUCCH group with the SpCell, the TDD SpCell and one TDD SCell shall have PUCCH-Config on their normal UL. For supporting PUCCH cell switching in the PUCCH group with only SCells, two TDD SCells shall have PUCCH-Config on their normal UL. In (NG)EN-DC and NE-DC, the NW configures at most one serving cell per frequency range with PUCCH. In (NG)EN-DC and NE-DC, if two PUCCH groups are configured, the serving cells of the NR PUCCH group in FR2 use the same numerology. For NR-DC, the maximum number of PUCCH groups in each cell group is one, and only the same numerology is supported for the cell group with carriers only in FR2. The NW may configure PUCCH for a BWP when setting up the BWP. The network may also add/remove the pucch-Config in an RRCReconfiguration with reconfigurationWithSync (for SpCell or PUCCH SCell) or with SCell release and add (for PUCCH SCell) to move the PUCCH between the UL and SUL carrier of one serving cell. In other cases, only modifications of a previously configured pucch-Config are allowed. If one (S)UL BWP of a serving cell is configured with PUCCH, all other (S)UL BWPs must be configured with PUCCH, too.
pusch-Config SetupRelease { PUSCH-Config } · OPTIONAL Need M	PUSCH configuration for one BWP of the normal UL or SUL of a serving cell. If the UE is configured with SUL and if it has a PUSCH-Config for both UL and SUL, an UL/SUL indicator field in DCI indicates which of the two to use. See TS 38.212 [17], clause 7.3.1.
configuredGrantConfig SetupRelease { ConfiguredGrantConfig } · OPTIONAL Need M	A Configured-Grant of type1 or type2 . It may be configured for UL or SUL but in case of type1 not for both at a time. Except for reconfiguration with sync, the NW does not reconfigure configuredGrantConfig when there is an active configured uplink grant Type 2 (see TS 38.321 [3]). However, the NW may release the configuredGrantConfig at any time. Network can only configure configured grant in one BWP using either this field or configuredGrantConfigToAddModList.
srs-Config SetupRelease { SRS-Config } · OPTIONAL Need M	Uplink sounding reference signal configuration.
beamFailureRecoveryConfig SetupRelease { BeamFailureRecoveryConfig } · OPTIONAL Cond SpCellOnly	Configuration of beam failure recovery. If supplementaryUplink is present, the field is present only in one of the uplink carriers, either UL or SUL.
sl-PUCCH-Config-r16 SetupRelease { PUCCH-Config } · OPTIONAL Need M since v16.1.0	Indicates the UE specific PUCCH configurations used for the HARQ-ACK feedback reporting for NR sidelink communication.
cp-ExtensionC2-r16 INTEGER (1..28) · OPTIONAL Need R since v16.0.0	Configures the cyclic prefix (CP) extension (see TS 38.211 [16], clause 5.3.1). For 15 kHz SCS, {1..28} are valid for both cp-ExtensionC2 and cp-ExtensionC3 . For 30 kHz SCS, {1..28} are valid for cp-ExtensionC2 and {2..28} are valid for cp-ExtensionC3. For 60 kHz SCS, {2..28} are valid for cp-ExtensionC2 and {3..28} are valid for cp-ExtensionC3 .
cp-ExtensionC3-r16 INTEGER (1..28) · OPTIONAL Need R since v16.0.0	Configures the cyclic prefix (CP) extension (see TS 38.211 [16], clause 5.3.1). For 15 kHz SCS, {1..28} are valid for both cp-ExtensionC2 and cp-ExtensionC3 . For 30 kHz SCS, {1..28} are valid for cp-ExtensionC2 and {2..28} are valid for cp-ExtensionC3. For 60 kHz SCS, {2..28} are valid for cp-ExtensionC2 and {3..28} are valid for cp-ExtensionC3 .
useInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} · OPTIONAL Need R since v16.0.0	If the field is present, the UE uses uplink frequency domain resource allocation Type 2 for PUSCH (see TS 38.213 [13], clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0, 1, 2, and 3 for PUCCH (see TS 38.213 [13], clause 9.2.1).
pucch-ConfigurationList-r16 SetupRelease { PUCCH-ConfigurationList-r16 } · OPTIONAL Need M since v16.0.0	PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks (see TS 38.213 [13], clause 9.1). Different PUCCH Resource IDs are configured in different PUCCH-Config within the pucch-ConfigurationList if configured.
lbt-FailureRecoveryConfig-r16 SetupRelease { LBT-FailureRecoveryConfig-r16 } · OPTIONAL Need M since v16.1.0	Configures parameters used for detection of consistent uplink LBT failures for operation with shared spectrum channel access, as specified in TS 38.321 [3].
configuredGrantConfigToAddModList-r16 ConfiguredGrantConfigToAddModList-r16 · OPTIONAL Need N since v16.1.0	Indicates a list of one or more configured grant configurations to be added or modified for one BWP. Except for reconfiguration with sync, the NW does not reconfigure a Type 2 configured grant configuration when it is active (see TS 38.321 [3]). The network configures multiple CG configurations for one BWP with either all configurations or no configuration configured with cg-RetransmissionTimer-r16 .
configuredGrantConfigToReleaseList-r16 ConfiguredGrantConfigToReleaseList-r16 · OPTIONAL Need N since v16.1.0	Indicates a list of one or more UL Configured Grant configurations to be released. The NW may release a configured grant configuration at any time.
configuredGrantConfigType2DeactivationStateList-r16 ConfiguredGrantConfigType2DeactivationStateList-r16 · OPTIONAL Need R since v16.1.0	Indicates a list of the deactivation states in which each state can be mapped to a single or multiple Configured Grant type 2 configurations to be deactivated when the corresponding deactivation DCI is received, see clause 7.3.1 in TS 38.212 [17] and clause 10.2 in TS 38.213 [13].
ul-TCI-StateList-r17 CHOICE { · OPTIONAL Need R since v17.1.0	Indicates the applicable UL TCI states for PUCCH, PUSCH and SRS.
explicitlist SEQUENCE { since v17.1.0
ul-TCI-ToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-State-r17 · OPTIONAL Need N since v17.1.0	Indicates a list of UL TCI states.
ul-TCI-ToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-StateId-r17 · OPTIONAL Need N since v17.1.0
unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17 since v17.1.0	Provides the serving cell and UL BWP where UL TCI states applicable to this UL BWP are defined. The value of unifiedTCI-StateType of current serving cell is the same in the serving cell indicated by unifiedTCI-StateRef.
ul-powerControl-r17 Uplink-powerControlId-r17 · OPTIONAL Cond NoTCI-PC since v17.0.0	Configures power control parameters for PUCCH, PUSCH and SRS when UE is configured with unifiedTCI-StateType for this serving cell. For each serving cell, ul-powerControl is either configured in all BWP-UplinkDedicated or it is not configured in any BWP-UplinkDedicated . When unifiedTCI-StateRef in the BWP-UplinkDedicated or in the PDSCH-Config if the unifiedTCI-StateType is set to joint, of a serving cell refers to another serving cell, ul-powerControl is either configured in all BWP-UplinkDedicated of these two serving cells or it is not configured in any BWP-UplinkDedicated of these two serving cells.
pucch-ConfigurationListMulticast1-r17 SetupRelease { PUCCH-ConfigurationList-r16 } · OPTIONAL Need M since v17.0.0	PUCCH configurations for two simultaneously constructed HARQ-ACK codebooks for MBS multicast (see TS 38.213, clause 9).
pucch-ConfigurationListMulticast2-r17 SetupRelease { PUCCH-ConfigurationList-r16 } · OPTIONAL Need M since v17.0.0	PUCCH configurations for two simultaneously constructed NACK-only feedback for MBS multicast (see TS 38.213, clause 9).
pucch-ConfigMulticast1-r17 SetupRelease { PUCCH-Config } · OPTIONAL Need M since v17.2.0	PUCCH configuration for the HARQ-ACK codebook for MBS multicast when multicast feedback is not configured with a priority value (see TS 38.213 [13], clause 9). If the field is not configured, pucch-Config applies.
pucch-ConfigMulticast2-r17 SetupRelease { PUCCH-Config } · OPTIONAL Need M since v17.2.0	PUCCH configuration for the NACK-only feedback for MBS multicast when multicast feedback is not configured with a priority value (see TS 38.213 [13], clause 9). If the field is not configured, pucch-Config applies.
pathlossReferenceRSToAddModList-r17 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-r17 · OPTIONAL Need N since v17.3.0	A list of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for path loss estimation for PUSCH, PUCCH and SRS for unified TCI state operation. If unifiedTCI-StateType is not configured for the serving cell, no element in this list is configured.
pathlossReferenceRSToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-Id-r17 · OPTIONAL Need N since v17.3.0
sbfd-Config2-Transmission-r19 ENUMERATED {enabled} · OPTIONAL Need S since v19.0.0	Indicates that the PUCCH and PUSCH transmissions can be in SBFD symbols and non-SBFD symbols in different slots in a given UL BWP (see TS 38.213 [13], clause 11 and TS 38.214 [19], clause 6).If not enabled, the restriction that the transmissions are restricted to SBFD symbols only or non-SBFD symbols only is applied for PUCCH and PUSCH transmissions in the given UL BWP.
sbfd-Config2-PUSCH-RB-Offset-r19 INTEGER(0..maxNrofPhysicalResourceBlocks-1) · OPTIONAL Need R since v19.0.0	Indicates the RB offset to determine the starting PRB for Type 2 configured grant and dynamic grant PUSCH transmissions in SBFD symbols when the PUSCH transmissions can be in SBFD symbols and non-SBFD symbols in different slots in a given UL BWP (see TS 38.214 [19], clause 6).
ul-Muting-NonSBFD-Symbol-r19 ENUMERATED {enabled} · OPTIONAL Need S since v19.0.0	Indicates whether a UE may apply UL resource muting in non-SBFD symbols if SBFD symbols are configured for the UE. If configured as ‘ enabled ’, UL muting is applicable in both SBFD symbols and non-SBFD symbols. Otherwise, UL resource muting is applicable only in SBFD symbols. This parameter does not apply for a UE configured with UL resource muting if SBFD symbols are not configured for the UE. In this case, UL resource muting is applicable in both flexible symbols and UL symbols.
twoTA-Without-MultiDCI-MultiTRP-r19 ENUMERATED {enabled} · OPTIONAL Need R since v19.0.0	Enables two TA for intra-cell without multi-DCI multi-TRP operation or inter-cell without multi-DCI multi-TRP operation.

BWP-UplinkDedicated

Definition

Candidate change requests of v19.1.0

Fields (30)

Used by (2)

Uses (20)

In the viewer