BWP-UplinkCommon
BWP-UplinkCommon is an RRC information element of 3GPP TS 38.331 (38331), the 5G NR Radio Resource Control (RRC) protocol.
Definition
The IE BWP-UplinkCommon is used to configure the common parameters of an uplink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell, excluding additionalRACH-perPCI-ToAddModList and additionalRACH-perPCI-ToReleaseList , are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling.
BWP-UplinkCommon ::= SEQUENCE {
genericParameters BWP,
rach-ConfigCommon SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need M
pusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon } OPTIONAL, -- Need M
pucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon } OPTIONAL, -- Need M
...,
[[
rach-ConfigCommonIAB-r16 SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need M
useInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R
msgA-ConfigCommon-r16 SetupRelease { MsgA-ConfigCommon-r16 } OPTIONAL -- Cond SpCellOnly2
]],
[[
enableRA-PrioritizationForSlicing-r17 BOOLEAN OPTIONAL, -- Cond RA-PrioSliceAI
additionalRACH-ConfigList-r17 SetupRelease { AdditionalRACH-ConfigList-r17 } OPTIONAL, -- Cond SpCellOnly2
rsrp-ThresholdMsg3-r17 RSRP-Range OPTIONAL, -- Need R
numberOfMsg3-RepetitionsList-r17 SEQUENCE (SIZE (4)) OF NumberOfMsg3-Repetitions-r17 OPTIONAL, -- Cond Msg3Rep
mcs-Msg3-Repetitions-r17 SEQUENCE (SIZE (8)) OF INTEGER (0..31) OPTIONAL -- Cond Msg3Rep
]],
[[
additionalRACH-perPCI-ToAddModList-r18 SEQUENCE (SIZE (1.. maxNrofAdditionalPRACHConfigs-r18)) OF RACH-ConfigTwoTA-r18
OPTIONAL, -- Cond 2TA-Only
additionalRACH-perPCI-ToReleaseList-r18 SEQUENCE (SIZE (1.. maxNrofAdditionalPRACHConfigs-r18)) OF AdditionalPCIIndex-r17
OPTIONAL, -- Need N
rsrp-ThresholdMsg1-RepetitionNum2-r18 RSRP-Range OPTIONAL, -- Need R
rsrp-ThresholdMsg1-RepetitionNum4-r18 RSRP-Range OPTIONAL, -- Need R
rsrp-ThresholdMsg1-RepetitionNum8-r18 RSRP-Range OPTIONAL, -- Need R
preambleTransMax-Msg1-Repetition-r18 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL -- Cond Msg1Rep1
]],
[[
preambleTransMaxRO-Type-r19 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Need R
sbfd-RO-Type-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL, -- Need S
sbfd-RSRP-ThresholdRO-Type-r19 RSRP-Range OPTIONAL, -- Need S
sbfd-RSRP-ThresholdRO-TypeUsage-r19 ENUMERATED {above,below} OPTIONAL, -- Need S
sbfd-RSRP-ThresholdMsg1-RepetitionNum2-r19 RSRP-Range OPTIONAL, -- Need R
sbfd-RSRP-ThresholdMsg1-RepetitionNum4-r19 RSRP-Range OPTIONAL, -- Need R
sbfd-RSRP-ThresholdMsg1-RepetitionNum8-r19 RSRP-Range OPTIONAL, -- Need R
sbfd-RACH-Config-r19 CHOICE {
sbfd-RACH-SingleConfig-r19 NULL,
sbfd-RACH-DualConfig-r19 SBFD-RACH-DualConfig-r19
} OPTIONAL -- Need R
]]
}Candidate change requests of v19.0.0
The CRs whose title or cover names this change, strong and likely matches only.
- CR 5414 r2 (likely): Introduction of Rel-19 Evolution of NR duplex operation (SBFD)
Fields (28)
| Field | Description |
|---|---|
| genericParameters BWP | |
| rach-ConfigCommon SetupRelease { RACH-ConfigCommon } · OPTIONAL Need M | Configuration of cell specific random access parameters which the UE uses for contention based and contention free random access as well as for contention based beam failure recovery in this BWP. The NW configures SSB-based RA (and hence RACH-ConfigCommon ) only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial DL BWP or DL BWPs associated with nonCellDefiningSSB or, for (e)RedCap UEs, the RedCap-specific initial downlink BWP. The network configures rach-ConfigCommon (without suffix) and/or rach-ConfigCommon-r17 , whenever it configures contention free 4-step random access (e.g. for reconfiguration with sync or for beam failure recovery or PDCCH order), the UE then applies the corresponding configuration depending on the RACH resource set selected upon RACH initialization, as specified in TS 38.321 [3]. For RedCap-specific initial uplink BWP, rach-ConfigCommon is always configured when msgA-ConfigCommon is configured in this BWP. |
| pusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon } · OPTIONAL Need M | Cell specific parameters for the PUSCH of this BWP. |
| pucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon } · OPTIONAL Need M | Cell specific parameters for the PUCCH of this BWP. |
| rach-ConfigCommonIAB-r16 SetupRelease { RACH-ConfigCommon } · OPTIONAL Need M since v16.0.0 | Configuration of cell specific random access parameters for the IAB-MT. The IAB specific IAB RACH configuration is used by IAB-MT, if configured. |
| 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 cell-specific PUSCH, e.g., PUSCH scheduled by RAR UL grant (see TS 38.213 [13] clause 8.3 and TS 38.214 [19], clause 6.1.2.2) and uses interlaced PUCCH Format 0 and 1 for cell-specific PUCCH (see TS 38.213 [13], clause 9.2.1). |
| msgA-ConfigCommon-r16 SetupRelease { MsgA-ConfigCommon-r16 } · OPTIONAL Cond SpCellOnly2 since v16.1.0 | Configuration of the cell specific PRACH and PUSCH resource parameters for transmission of MsgA in 2-step random access type procedure. The NW can configure msgA-ConfigCommon only for UL BWPs if the linked DL BWPs (same bwp-Id as UL-BWP) are the initial DL BWPs or DL BWPs containing the SSB associated to the initial DL BWP or DL BWPs associated with nonCellDefiningSSB or, for (e)RedCap UEs, the RedCap-specific initial downlink BWP. The network configures msgA-ConfigCommon (without suffix) and/or msgA-ConfigCommon-r17 , whenever it configures contention free 2-step random access, the UE then applies the corresponding configuration depending on the RACH resource set selected upon RACH initialization, as specified in TS 38.321 [3]. |
| enableRA-PrioritizationForSlicing-r17 BOOLEAN · OPTIONAL Cond RA-PrioSliceAI since v17.0.0 | Indicates whether or not the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep should override the ra-PrioritizationForAccessIdentity . The field is applicable only when the UE is configured by upper layers with both NSAG and Access Identity 1 or 2. If value TRUE is configured, the UE should only apply the ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep . If value FALSE is configured, the UE should only apply ra-PrioritizationForAccessIdentity . If the field is absent, whether to use ra-PrioritizationForSlicing/ra-PrioritizationForSlicingTwoStep or ra-PrioritizationForAccessIdentity is up to UE implementation. |
| additionalRACH-ConfigList-r17 SetupRelease { AdditionalRACH-ConfigList-r17 } · OPTIONAL Cond SpCellOnly2 since v17.1.0 | List of feature or feature combination-specific RACH configurations, i.e. the RACH configurations configured in addition to the one configured by rach-ConfigCommon and by msgA-ConfigCommon . The network associates all possible preambles of an additional RACH configuration to one or more feature(s) or feature combination(s). The network does not configure this list to have more than 16 entries. If both rach-ConfigCommon and msgA-ConfigCommon are configured for a specific FeatureCombination , the network always provides them in the same additionalRACH-Config . If both rach-ConfigCommon and sbfd-RACH-DualConfig are configured for the same FeatureCombination , rach-ConfigCommon and sbfd-RACH-DualConfig are configured in the same AdditionalRACH-Config . |
| rsrp-ThresholdMsg3-r17 RSRP-Range · OPTIONAL Need R since v17.1.0 | Threshold used by the UE for determining whether to select resources indicating Msg3 repetition in this BWP, as specified in TS 38.321 [3]. The field is mandatory if both set(s) of Random Access resources with MSG3 repetition indication and set(s) of Random Access resources without MSG3 repetition indication are configured in the BWP. It is absent otherwise. |
| numberOfMsg3-RepetitionsList-r17 SEQUENCE (SIZE (4)) OF NumberOfMsg3-Repetitions-r17 · OPTIONAL Cond Msg3Rep since v17.1.0 | The number of repetitions for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. This field is only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon , the UE shall apply the values {n1, n2, n3, n4} (see TS 38.214 [19], clause 6.1.2.1). |
| mcs-Msg3-Repetitions-r17 SEQUENCE (SIZE (8)) OF INTEGER (0..31) · OPTIONAL Cond Msg3Rep since v17.1.0 | Configuration of eight candidate MCS indexes for PUSCH transmission scheduled by RAR UL grant and DCI format 0_0 with CRC scrambled by TC-RNTI. Only the first 4 configured or default MCS indexes are used for PUSCH transmission scheduled by RAR UL grant. This field is only applicable when the UE selects Random Access resources indicating Msg3 repetition in this BWP. If this field is absent when the set(s) of Random Access resources with MSG3 repetition indication are configured in the BWP-UplinkCommon , the UE shall apply the values {0, 1, 2, 3, 4, 5, 6, 7} (see TS 38.214 [19], clause 6.1.4). |
| additionalRACH-perPCI-ToAddModList-r18 SEQUENCE (SIZE (1.. maxNrofAdditionalPRACHConfigs-r18)) OF RACH-ConfigTwoTA-r18 · OPTIONAL Cond 2TA-Only since v18.0.0 | List of RACH configurations for the additional PCIs. The RACH configuration for an additional PCI is applied for Random Access procedure initiated by PDCCH order towards to the additional PCI, as specified in TS 38.321 clause 5.1.1b. This list includes the same number of elements like additionalPCI-ToAddModList for this serving cell and the n -th element of this list is for the PCI in the n -th element of additionalPCI-ToAddModList . Either the network does not configure any RACH configuration for any additional PCI, or the network configures a RACH configuration for each additional PCI. When the network releases an additional PCI of a serving cell, the network also explicitly releases the associated random access configuration in every UL BWP of the serving cell. This configuration may be different for different UEs. |
| additionalRACH-perPCI-ToReleaseList-r18 SEQUENCE (SIZE (1.. maxNrofAdditionalPRACHConfigs-r18)) OF AdditionalPCIIndex-r17 · OPTIONAL Need N since v18.0.0 | List of RACH configurations for the additional PCIs. The RACH configuration for an additional PCI is applied for Random Access procedure initiated by PDCCH order towards to the additional PCI, as specified in TS 38.321 clause 5.1.1b. This list includes the same number of elements like additionalPCI-ToAddModList for this serving cell and the n -th element of this list is for the PCI in the n -th element of additionalPCI-ToAddModList . Either the network does not configure any RACH configuration for any additional PCI, or the network configures a RACH configuration for each additional PCI. When the network releases an additional PCI of a serving cell, the network also explicitly releases the associated random access configuration in every UL BWP of the serving cell. This configuration may be different for different UEs. |
| rsrp-ThresholdMsg1-RepetitionNum2-r18 RSRP-Range · OPTIONAL Need R since v18.0.0 | Threshold used by the UE for determining whether to select resources indicating Msg1 repetition number 2, 4 or 8 in this BWP, as specified in TS 38.321 [3]. The value applies to all the BWPs and all RACH configurations. For a given MSG1 repetition number, this corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP. It is absent otherwise. |
| rsrp-ThresholdMsg1-RepetitionNum4-r18 RSRP-Range · OPTIONAL Need R since v18.0.0 | Threshold used by the UE for determining whether to select resources indicating Msg1 repetition number 2, 4 or 8 in this BWP, as specified in TS 38.321 [3]. The value applies to all the BWPs and all RACH configurations. For a given MSG1 repetition number, this corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP. It is absent otherwise. |
| rsrp-ThresholdMsg1-RepetitionNum8-r18 RSRP-Range · OPTIONAL Need R since v18.0.0 | Threshold used by the UE for determining whether to select resources indicating Msg1 repetition number 2, 4 or 8 in this BWP, as specified in TS 38.321 [3]. The value applies to all the BWPs and all RACH configurations. For a given MSG1 repetition number, this corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP. It is absent otherwise. |
| preambleTransMax-Msg1-Repetition-r18 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} · OPTIONAL Cond Msg1Rep1 since v18.0.0 | Max number of transmissions of MSG1 repetitions number (2, 4 and 8) performed before switching to higher repetition number (see TS 38.321 [3], clauses 5.1.1). This field is only applicable when more than one repetition numbers are configured in shared RO. If the field is absent, switching from lower repetition number to higher repetition number is not allowed. |
| preambleTransMaxRO-Type-r19 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} · OPTIONAL Need R since v19.0.0 | Max number of RA preamble transmissions performed before switching to another RO type (i.e., from the second PRACH occasions to the first PRACH occasions, as specified in TS 38.213 [13] clause 8, and vice versa). |
| sbfd-RO-Type-r19 ENUMERATED {sbfd, non-sbfd} · OPTIONAL Need S since v19.0.0 | Indicates which RO type (the first or the second PRACH occasions as specified in TS 38.213 [13], clause 8) to be used for a SBFD aware UE (see TS 38.300 [2], clause 23.1) in the initial PRACH transmission . If absent, the RO type is determined based on sbfd-RSRP-ThresholdRO-Type and sbfd-RSRP-ThresholdRO-TypeUsage . |
| sbfd-RSRP-ThresholdRO-Type-r19 RSRP-Range · OPTIONAL Need S since v19.0.0 | Threshold used by the SBFD aware UE for choosing RACH occasion type (the first or the second PRACH occasions as specified in TS 38.213 [13], clause 8) for the initial PRACH preamble transmissions. |
| sbfd-RSRP-ThresholdRO-TypeUsage-r19 ENUMERATED {above,below} · OPTIONAL Need S since v19.0.0 | Indicate how the SBFD aware UE chooses RACH occasion type (the first or the second PRACH occasions as specified in TS 38.213 [13], clause 8) using sbfd- RSRP -ThresholdRO-Type for the initial PRACH preamble transmissions and is always configured together with sbfd-RSRP-ThresholdRO-Type. With value above , the SBFD aware UE chooses the second PRACH occasions if the measured downlink pathloss reference RSRP is above sbfd-RSRP-ThresholdRO-Type and chooses the first PRACH occasions otherwise. With value below , the SBFD aware UE chooses the second PRACH occasions if the measured downlink pathloss reference RSRP is below sbfd-RSRP-ThresholdRO-Type and chooses the first PRACH occasions otherwise. If all of sbfd-RO-Type , sbfd-RSRP-ThresholdRO-Type and sbfd-RSRP-ThresholdRO-TypeUsage are absent, it is up to UE implementation to determine the RO type. |
| sbfd-RSRP-ThresholdMsg1-RepetitionNum2-r19 RSRP-Range · OPTIONAL Need R since v19.0.0 | Threshold used by the UE for determining whether to select resources indicating Msg1 repetition number 2, 4 or 8 within the second PRACH occasions (see TS 38.213 [13], clause 8). If sbfd-RACH-DualConfig is configured, for a given MSG1 repetition number, this corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP. If sbfd-RACH-DualConfig is configured, it is absent otherwise. When the separate configuration of sbfd-RSRP-ThresholdMsg1-RepetitionNum2/4/8 is configued together with sbfd-RACH-SingleConfig , for a given MSG1 repetition number, the corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP, it is absent otherwise. When the separate configuration of sbfd-RSRP-ThresholdMsg1-RepetitionNum2/4/8 is not configured together with sbfd-RACH-SingleConfig , rsrp-ThresholdMsg1-RepetitionNum2/4/8 is reused within the second PRACH occasions. |
| sbfd-RSRP-ThresholdMsg1-RepetitionNum4-r19 RSRP-Range · OPTIONAL Need R since v19.0.0 | Threshold used by the UE for determining whether to select resources indicating Msg1 repetition number 2, 4 or 8 within the second PRACH occasions (see TS 38.213 [13], clause 8). If sbfd-RACH-DualConfig is configured, for a given MSG1 repetition number, this corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP. If sbfd-RACH-DualConfig is configured, it is absent otherwise. When the separate configuration of sbfd-RSRP-ThresholdMsg1-RepetitionNum2/4/8 is configued together with sbfd-RACH-SingleConfig , for a given MSG1 repetition number, the corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP, it is absent otherwise. When the separate configuration of sbfd-RSRP-ThresholdMsg1-RepetitionNum2/4/8 is not configured together with sbfd-RACH-SingleConfig , rsrp-ThresholdMsg1-RepetitionNum2/4/8 is reused within the second PRACH occasions. |
| sbfd-RSRP-ThresholdMsg1-RepetitionNum8-r19 RSRP-Range · OPTIONAL Need R since v19.0.0 | Threshold used by the UE for determining whether to select resources indicating Msg1 repetition number 2, 4 or 8 within the second PRACH occasions (see TS 38.213 [13], clause 8). If sbfd-RACH-DualConfig is configured, for a given MSG1 repetition number, this corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP. If sbfd-RACH-DualConfig is configured, it is absent otherwise. When the separate configuration of sbfd-RSRP-ThresholdMsg1-RepetitionNum2/4/8 is configued together with sbfd-RACH-SingleConfig , for a given MSG1 repetition number, the corresponding field is mandatory if both set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources without MSG1 repetition indication are configured in the BWP, or if the set(s) of Random Access resources with MSG1 repetition indication associated with this MSG1 repetition number and set(s) of Random Access resources with MSG1 repetition indication associated with a lower repetition number are configured in the BWP, it is absent otherwise. When the separate configuration of sbfd-RSRP-ThresholdMsg1-RepetitionNum2/4/8 is not configured together with sbfd-RACH-SingleConfig , rsrp-ThresholdMsg1-RepetitionNum2/4/8 is reused within the second PRACH occasions. |
| sbfd-RACH-Config-r19 CHOICE { · OPTIONAL Need R since v19.0.0 | Indicated SBFD RACH configuration type, see clause 5 in TS 38.211 [16] and clause 8 in TS 38.213 [13]. Value sbfd-RACH-SingleConfig indicates the single RACH configuration for SBFD random access operation is enabled in this BWP, and value sbfd-RACH-DualConfig is used to enable dual RACH configurations and configure random access parameters in SBFD symbols by setting up one additional RACH configuration and including all parameters in rach-ConfigCommon except rsrp-ThresholdSSB-SUL . If present and the UE is indicated to use SBFD random access operation for CFRA in the same BWP, the UE shall derive the locations of the second PRACH occasions based on this field. |
| sbfd-RACH-SingleConfig-r19 NULL since v19.0.0 | |
| sbfd-RACH-DualConfig-r19 SBFD-RACH-DualConfig-r19 since v19.0.0 |
Used by (5)
- BWP-Uplink
- UplinkConfigCommon
- UplinkConfigCommon-v1700
- UplinkConfigCommonSIB
- UplinkConfigCommonSIB-v1700
Uses (13)
- AdditionalPCIIndex-r17
- AdditionalRACH-ConfigList-r17
- BWP
- MsgA-ConfigCommon-r16
- NumberOfMsg3-Repetitions-r17
- PUCCH-ConfigCommon
- PUSCH-ConfigCommon
- RACH-ConfigCommon
- RACH-ConfigTwoTA-r18
- RSRP-Range
- SBFD-RACH-DualConfig-r19
- SetupRelease
- maxNrofAdditionalPRACHConfigs-r18