Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 38.331  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.2.2.4…   5.3…   5.3.3…   5.3.5…   5.3.5.5…   5.3.5.6…   5.3.5.7…   5.3.5.13…   5.3.5.17…   5.3.6…   5.3.8…   5.3.13…   5.3.14…   5.4…   5.5…   5.5.3…   5.5.4…   5.5.4.15…   5.5.4.23…   5.5.5…   5.5a…   5.7…   5.7.4…   5.7.8…   5.7.12…   5.8…   5.8.9…   5.8.9.2…   5.8.9.8…   5.8.10…   5.8.11…   5.9…   5.10…   6…   6.2.2…   6-2-2-23…   6-2-2-27…   6-2-2-43…   6-2-2-47…   6.3…   6.3.2…   6-3-2-27…   6-3-2-49…   6-3-2-73…   6-3-2-95…   6-3-2-108…   6-3-2-134…   6-3-2-162…   6-3-2-188…   6-3-2-213…   6-3-2-243…   6-3-2-271…   6-3-2-297…   6-3-2-341…   6.3.3…   6-3-3-25…   6-3-3-51…   6.3.4…   6.3.5…   6-3-5-25…   6.3.6…   6.4…   7…   9…   11…   A…   A.4…   B…

 

 –  PHR-Configp. 903

The IE PHR-Config is used to configure parameters for power headroom reporting.
PHR-Config information element
PHR-Config field descriptions
dummy
This field is not used in this version of the specification and the UE ignores the received value.
mpe-ProhibitTimer
Value in number of subframes for MPE reporting, as specified in TS 38.321. Value sf10 corresponds to 10 subframes, and so on.
mpe-Reporting-FR2
Indicates whether the UE shall report MPE P-MPR in the PHR MAC control element, as specified in TS 38.321.
mpe-Threshold
Value of the P-MPR threshold in dB for reporting MPE P-MPR when FR2 is configured, as specified in TS 38.321. The same value applies for each serving cell (although the associated functionality is performed independently for each cell).
multiplePHR
Indicates if power headroom shall be reported using the Single Entry PHR MAC control element or Multiple Entry PHR MAC control element defined in TS 38.321. True means to use Multiple Entry PHR MAC control element and False means to use the Single Entry PHR MAC control element defined in TS 38.321. The network configures this field to true for MR-DC and UL CA for NR, and to false in all other cases.
numberOfN
Number of reported P-MPR values in a PHR MAC CE.
phr-ModeOtherCG
Indicates the mode (i.e. real or virtual) used for the PHR of the activated cells that are part of the other Cell Group (i.e. MCG or SCG), when DC is configured. If the UE is configured with only one cell group (no DC), it ignores the field.
phr-PeriodicTimer
Value in number of subframes for PHR reporting as specified in TS 38.321. Value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on.
phr-ProhibitTimer
Value in number of subframes for PHR reporting as specified in TS 38.321. Value sf0 corresponds to 0 subframe, value sf10 corresponds to 10 subframes, value sf20 corresponds to 20 subframes, and so on.
phr-Tx-PowerFactorChange
Value in dB for PHR reporting as specified in TS 38.321. Value dB1 corresponds to 1 dB, dB3 corresponds to 3 dB and so on. The same value applies for each serving cell (although the associated functionality is performed independently for each cell).
phr-Type2OtherCell
If set to true, the UE shall report a PHR type 2 for the SpCell of the other MAC entity. See clause 5.4.6 of TS 38.321. Network sets this field to false if the UE is not configured with an E-UTRA MAC entity.
twoPHRMode
Indicates if the power headroom shall be reported as two PHRs (each PHR associated with a SRS resource set) is enabled or not.
Up

 –  PhysCellIdp. 904

The PhysCellId identifies the physical cell identity (PCI).
PhysCellId information element

 –  PhysicalCellGroupConfigp. 905

The IE PhysicalCellGroupConfig is used to configure cell-group specific L1 parameters.
PhysicalCellGroupConfig information element
PhysicalCellGroupConfig field descriptions
ackNackFeedbackMode
Indicates which among the joint and separate ACK/NACK feedback modes to use within a slot as specified in clause 9 of TS 38.213.
bdFactorR
Parameter for determining and distributing the maximum numbers of BD/CCE for mPDCCH based mPDSCH transmission as specified in clause 10.1 of TS 38.213.
cs-RNTI
RNTI value for downlink SPS (see SPS-Config) and uplink configured grant (see ConfiguredGrantConfig).
downlinkAssignmentIndexDCI-0-2
Indicates if "Downlink assignment index" is present or absent in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is absent, then 0 bit for "Downlink assignment index" in DCI format 0_2. If the field "downlinkAssignmentIndexDCI-0-2" is present, then the bitwidth of "Downlink assignment index" in DCI format 0_2 is defined in the same was as that in DCI format 0_1 (see clause 7.3.1 of TS 38.212 and clause 9.1 of TS 38.213).
downlinkAssignmentIndexDCI-1-2
Configures the number of bits for "Downlink assignment index" in DCI format 1_2. If the field is absent, then 0 bit is applied for "Downlink assignment index" in DCI format 1_2. Note that 1 bit and 2 bits are applied if only one serving cell is configured in the DL and pdsch-HARQ-ACK-Codebook is set to dynamic. 4 bits is applied if more than one serving cell are configured in the DL and pdsch-HARQ-ACK-Codebook is set to dynamic (see clause 7.3.1 of TS 38.212 and clause 9.1 of TS 38.213).
harq-ACK-SpatialBundlingPUCCH
Enables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUCCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUCCH HARQ ACKs for the primary PUCCH group is disabled (see clause 9.1.2.1 of TS 38.213). If the field harq-ACK SpatialBundlingPUCCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUCCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.
harq-ACK-SpatialBundlingPUCCH-secondaryPUCCHgroup
Indicates whether spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see clause 9.1.2.1 of TS 38.213). When the field is absent, the use of spatial bundling of PUCCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUCCH. See clause 9.1.2.1 of TS 38.213. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.
harq-ACK-SpatialBundlingPUSCH
Enables spatial bundling of HARQ ACKs. It is configured per cell group (i.e. for all the cells within the cell group) for PUSCH reporting of HARQ-ACK. It is only applicable when more than 4 layers are possible to schedule. When the field is absent, the spatial bundling of PUSCH HARQ ACKs for the primary PUCCH group is disabled (see clauses 9.1.2.2 and 9.1.3.2 of TS 38.213). If the field harq-ACK SpatialBundlingPUSCH-secondaryPUCCHgroup is present, harq-ACK-SpatialBundlingPUSCH is only applied to primary PUCCH group. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.
harq-ACK-SpatialBundlingPUSCH-secondaryPUCCHgroup
Indicates whether spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is enabled or disabled. The field is only applicable when more than 4 layers are possible to schedule (see clauses 9.1.2.2 and 9.1.3.2 of TS 38.213). When the field is absent, the use of spatial bundling of PUSCH HARQ ACKs for the secondary PUCCH group is indicated by harq-ACK-SpatialBundlingPUSCH. See clauses 9.1.2.2 and 9.1.3.2 of TS 38.213. Network does not configure for a UE both spatial bundling of HARQ ACKs and codeBlockGroupTransmission within the same cell group.
intraBandNC-PRACH-simulTx
Enables parallel PRACH and SRS/PUCCH/PUSCH transmissions across CCs in intra-band non-contiguous CA (see clause 8.1 of TS 38.213, and clause 6.2.1 of TS 38.214). This field is absent in the IE CellGroupConfig when provided as part of RRCSetup message.
mcs-C-RNTI
RNTI to indicate use of qam64LowSE for grant-based transmissions. When the mcs-C-RNTI is configured, RNTI scrambling of DCI CRC is used to choose the corresponding MCS table.
nfi-TotalDAI-Included
Indicates whether the NFI and total DAI fields of the non-scheduled PDSCH group is included in the non-fallback DL grant DCI (see clause 7.3.1 of TS 38.212). The network configures this only when enhanced dynamic codebook is configured (pdsch-HARQ-ACK-Codebook is set to enhancedDynamic).
nrdc-PCmode-FR1
Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 1 (FR1) (see clause 7.6 of TS 38.213).
nrdc-PCmode-FR2
Indicates the uplink power sharing mode that the UE uses in NR-DC in frequency range 2 (FR2) (see clause 7.6 of TS 38.213).
pdcch-BlindDetection, pdcch-BlindDetection2, pdcch-BlindDetection3, pdcch-BlindDetection4
Indicates the reference number of cells for PDCCH blind detection for the CG. Network configures the field for each CG when the UE is in NR DC and sets the value in accordance with the constraints specified in TS 38.213. The network configures pdcch-BlindDetection only if the UE is in NR-DC. The network configures pdcch-BlindDetection2 only if the UE is in NR-DC with at least one downlink cell using Rel-16 PDCCH monitoring capability. The network configures pdcch-BlindDetection3 only if the UE is in NR-DC with at least one downlink cell using Rel-15 PDCCH monitoring capability. The network configures pdcch-BlindDetection4 only if the UE is in NR-DC with at least one downlink cell using Rel-17 PDCCH monitoring capability.
pdcch-BlindDetectionCA-CombIndicator
Configure one combination of pdcch-BlindDetectionCA1 (for R15) and pdcch-BlindDetectionCA2 (for R16) for UE to use for scaling PDCCH monitoring capability if the number of serving cells configured to a UE is larger than the reported capability, and if UE reports more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 as UE capability. The combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 configured by pdcch-BlindDetectionCA-CombIndicator is from the more than one combination of pdcch-BlindDetectionCA1 and pdcch-BlindDetectionCA2 reported by UE (see clause 10 of TS 38.213).
pdcch-BlindDetectionCA-CombIndicator-r17 is used to configure one combination of pdcch-BlindDetectionCA1 (for R15), pdcch-BlindDetectionCA2 (for R16) and pdcch-BlindDetectionCA3 (for R17) for UE to use for scaling PDCCH monitoring capability if the number of serving cells configured to a UE is larger than the reported capability, and if UE reports more than one combination of pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 as UE capability. The combination of pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 configured by pdcch-BlindDetectionCA-CombIndicator-r17 is from the more than one combination of pdcch-BlindDetectionCA1, pdcch-BlindDetectionCA2 and pdcch-BlindDetectionCA3 reported by UE (see clause 10 of TS 38.213).
pdcch-BlindDetectionCA-CombIndicator-r16 and pdcch-BlindDetectionCA-CombIndicator-r17 are not configured simultaneously.
p-NR-FR1
The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 1 (FR1). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-UE-FR1 (configured total for all serving cells operating on FR1).
p-NR-FR2
The maximum total transmit power to be used by the UE in this NR cell group across all serving cells in frequency range 2 (FR2). The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-UE-FR2 (configured total for all serving cells operating on FR2). This field is only used in NR-DC. A UE does not expect to be configured with this parameter in this release of the specification.
prioLowDG-HighCG
Enable PHY prioritization for the case where low-priority dynamic grant-PUSCH collides with high-priority configured grant-PUSCH on a BWP of a serving cell (see clause 9 of TS 38.213), when the UE has generated transport blocks for both DG-PUSCH and CG-PUSCH as described in TS 38.321.
prioHighDG-LowCG
Enable PHY prioritization for the case where high-priority dynamic grant PUSCH collides with low-priority configured grant PUSCH on a BWP of a serving cell (see clause 9 of TS 38.213), when the UE has generated transport blocks for both DG-PUSCH and CG-PUSCH as described in TS 38.321.
ps-RNTI
RNTI value for scrambling CRC of DCI format 2-6 used for power saving (see clause 10.1 of TS 38.213).
ps-Offset
The start of the search-time of DCI format 2-6 with CRC scrambled by PS-RNTI relative to the start of the drx-onDurationTimer of Long DRX (see clause 10.3 of TS 38.213). Value in multiples of 0.125ms (milliseconds). 1 corresponds to 0.125 ms, 2 corresponds to 0.25 ms, 3 corresponds to 0.375 ms and so on.
ps-WakeUp
Indicates the UE to wake-up if DCI format 2-6 is not detected outside active time (see clause 5.7 of TS 38.321). If the field is absent, the UE does not wake-up if DCI format 2-6 is not detected outside active time.
ps-PositionDCI-2-6
Starting position of UE wakeup and SCell dormancy indication in DCI format 2-6 (see clause 10.3 of TS 38.213).
ps-TransmitPeriodicL1-RSRP
Indicates the UE to transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start (see clause 5.7 of TS 38.321). If the field is absent, the UE does not transmit periodic L1-RSRP report(s) when the drx-onDurationTimer does not start.
ps-TransmitOtherPeriodicCSI
Indicates the UE to transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start (see clause 5.7 of TS 38.321). If the field is absent, the UE does not transmit periodic CSI report(s) other than L1-RSRP reports when the drx-onDurationTimer does not start.
p-UE-FR1
The maximum total transmit power to be used by the UE across all serving cells in frequency range 1 (FR1) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-NR-FR1 (configured for the cell group).
p-UE-FR2
The maximum total transmit power to be used by the UE across all serving cells in frequency range 2 (FR2) across all cell groups. The maximum transmit power that the UE may use may be additionally limited by p-Max (configured in FrequencyInfoUL) and by p-NR-FR2 (configured for the cell group). A UE does not expect to be configured with this parameter in this release of the specification.
pdsch-HARQ-ACK-Codebook
The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to both CA and non-CA operation (see clauses 9.1.2 and 9.1.3 of TS 38.213). If pdsch-HARQ-ACK-Codebook-r16 is signalled, UE shall ignore the pdsch-HARQ-ACK-Codebook (without suffix). For the HARQ-ACK for sidelink, if pdsch-HARQ-ACK-Codebook-r16 is signalled, the UE uses pdsch-HARQ-ACK-Codebook (without suffix) and ignores pdsch-HARQ-ACK-Codebook-r16. If the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary PUCCH group. Otherwise, this field is applied to the cell group (i.e. for all the cells within the cell group). For the HARQ-ACK for sidelink, if the field pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup is present, pdsch-HARQ-ACK-Codebook is applied to primary and secondary PUCCH group and the UE ignores pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup.
pdsch-HARQ-ACK-CodebookList
A list of configurations for one or two HARQ-ACK codebooks. Each configuration in the list is defined in the same way as pdsch-HARQ-ACK-Codebook (see clause 7.3.1.2.2 of TS 38.212, and clauses 7.2.1, 9.1.2, 9.1.3 and 9.2.1 of TS 38.213). If this field is present, the field pdsch-HARQ-ACK-Codebook is ignored. If this field is present, the value of this field is applied for primary PUCCH group and for secondary PUCCH group (if configured). For the HARQ-ACK for sidelink, the UE uses pdsch-HARQ-ACK-Codebook and ignores pdsch-HARQ-ACK-CodebookList if this field is present.
pdsch-HARQ-ACK-Codebook-secondaryPUCCHgroup
The PDSCH HARQ-ACK codebook is either semi-static or dynamic. This is applicable to CA operation (see clauses 9.1.2 and 9.1.3 of TS 38.213). It is configured for secondary PUCCH group.
pdsch-HARQ-ACK-EnhType3DCI-Field, pdsch-HARQ-ACK-EnhType3DCI-FieldSecondaryPUCCHgroup
Indicates the enhanced Type 3 codebook through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in the primary PUCCH group if the more than one enhanced Type 3 HARQ-ACK codebook is configured for the primary PUCCH group, or in the secondary PUCCH group if the more than one enhanced Type 3 HARQ-ACK code is configured for the secondary PUCCH group, respectively.
pdsch-HARQ-ACK-EnhType3ToAddModList, pdsch-HARQ-ACK-EnhType3SecondaryToAddModList
Configure the list of enhanced Type 3 HARQ-ACK codebooks for the primary PUCCH group and the secondary PUCCH group, respectively. When configured, DCI format 1_1 can request the UE to report A/N for one of the configured enhanced Type 3 HARQ-ACK codebooks in the corresponding PUCCH group (see clause 9.1.4 of TS 38.213). The network can configure pdsch-HARQ-ACK-EnhType3SecondaryToAddModList only if secondary PUCCH group is configured.
pdsch-HARQ-ACK-OneShotFeedback
When configured, the DCI format 1_1 can request the UE to report A/N for all HARQ processes and all CCs configured in the PUCCH group (see clause 7.3.1 of TS 38.212).
pdsch-HARQ-ACK-OneShotFeedbackCBG
When configured, the DCI format 1_1 can request the UE to include CBG level A/N for each CC with CBG level transmission configured. When not configured, the UE will report TB level A/N even if CBG level transmission is configured for a CC. The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured.
pdsch-HARQ-ACK-OneShotFeedbackNDI
When configured, the DCI format 1_1 can request the UE to include NDI for each A/N reported. The network configures this only when pdsch-HARQ-ACK-OneShotFeedback is configured.
pdsch-HARQ-ACK-Retx, pdsch-HARQ-ACK-RetxSecondaryPUCCHgroup
When configured, the DCI format 1_1 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource in the primary PUCCH group and the secondary PUCCH group, respectively (see clause 9.1.5 of TS 38.213).
pucch-sSCell, pucch-sSCellSecondaryPUCCHgroup
indictates the alternative PUCCH cells for PUCCH cell switching in the primary and the secondary PUCCH group, respectively. For the primary PUCCH group, it is configured for cells on top of SpCell. For the secondary PUCCH group, it is configured for cell on top of the PUCCH SCell.
pucch-sSCellDyn, pucch-sSCellDynsecondaryPUCCHgroup
When configured, PUCCH cell switching based on dynamic indication in DCI format 1_1 is enabled (see clause 9.A, clause 9.1.5 of TS 38.213), respectively for the primary PUCCH group and the secondary PUCCH group.
pucch-sSCellPattern, pucch-sSCellPatternSecondaryPUCCHgroup
When configured, the UE applies the semi-static PUCCH cell switching (see clause 9.A of TS 38.213) using the time domain pattern of applicable PUCCH cells indicated by this field, respectively for the primary PUCCH group and the secondary PUCCH group.
simultaneousPUCCH-PUSCH, simultaneousPUCCH-PUSCH-SecondaryPUCCHgroup
Enables simultaneous PUCCH and PUSCH transmissions with different priorities for the primary PUCCH group and the secondary PUCCH group, respectively.
simultaneousSR-PUSCH-diffPUCCH-Groups
Enables simultaneous SR and PUSCH transmissions in different PUCCH groups (see clause 5.4.1, clause 5.4.4 of TS 38.321).
sizeDCI-2-6
Size of DCI format 2-6 (see clause 10.3 of TS 38.213).
sp-CSI-RNTI
RNTI for Semi-Persistent CSI reporting on PUSCH (see CSI-ReportConfig) (see clause 5.2.1.5.2 of TS 38.214 ). Network always configures the UE with a value for this field when at least one CSI-ReportConfig with reportConfigType set to semiPersistentOnPUSCH is configured.
tpc-PUCCH-RNTI
RNTI used for PUCCH TPC commands on DCI (see clause 10.1 of TS 38.213).
tpc-PUSCH-RNTI
RNTI used for PUSCH TPC commands on DCI (see clause 10.1 of TS 38.213).
tpc-SRS-RNTI
RNTI used for SRS TPC commands on DCI (see clause 10.1 of TS 38.213).
twoQCLTypeDforPDCCHRepetition
Indicates whether a UE is expected UE to identify and monitor two QCL-TypeD properties for multiple overlapping CORESETs in the case of PDCCH repetition.
uci-MuxWithDiffPrio, uci-MuxWithDiffPrio-secondaryPUCCHgroup
When configured, enables multiplexing a high-priority (HP) HARQ-ACK UCI and a low-priority (LP) HARQ-ACK UCI into a PUCCH or PUSCH for the primary PUCCH group and the secondary PUCCH group, respectively.
ul-TotalDAI-Included
Indicates whether the total DAI fields of the additional PDSCH group is included in the non-fallback UL grant DCI (see clause 7.3.1 of TS 38.212). The network configures this only when enhanced dynamic codebook is configured (pdsch-HARQ-ACK-Codebook is set to enhancedDynamic).
xScale
The UE is allowed to drop NR only if the power scaling applied to NR results in a difference between scaled and unscaled NR UL of more than xScale dB (see TS 38.213). If the value is not configured for dynamic power sharing, the UE assumes default value of 6 dB.
MulticastConfig field descriptions
pdsch-HARQ-ACK-CodebookListMulticast
A list of configurations for one or two HARQ-ACK codebooks for MBS multicast. Each configuration in the list is defined in the same way as pdsch-HARQ-ACK-Codebook (see clause 7.3.1.2.2 of TS 38.212, and clauses 7.2.1, 9.1.2, 9.1.3 and 9.2.1 of TS 38.213). If this field is present, the field pdsch-HARQ-ACK-Codebook is ignored. If this field is present, the value of this field is applied for primary PUCCH group and for secondary PUCCH group (if configured).
type1CodebookGenerationMode
Indicates the mode of Type-1 HARQ-ACK codebook generation, as specified in TS 38.213. Mode 1 is based on the k1 values that are in the intersection of K1 set for unicast and K1 set for multicast. Mode 2 is based on the k1 values that are in the union of K1 set for unicast and K1 set for multicast.
PDSCH-HARQ-ACK-EnhType3 field descriptions
pdsch-HARQ-ACK-EnhType3CBG
When configured, the DCI format 1_1 or DCI format 1_2 can request the UE to include CBG level A/N for each CC with CBG level transmission configured of the enhanced Type 3 HARQ-ACK codebook. When not configured, the UE will report TB level A/N even if CBG level transmission is configured for a CC.
pdsch-HARQ-ACK-EnhType3NDI
When configured, the DCI format 1_1 or DCI format 1_2 can request the UE to include NDI for each A/N reported of the enhanced Type 3 HARQ-ACK codebook.
perCC
Configures enhanced Type 3 HARQ-ACK codebook using per CC configuration.
perHARQ, perHARQ-Ext
Configures enhanced Type 3 HARQ-ACK codebook using per HARQ process and CC configuration. perHARQ-Ext is present only when nrofHARQ-ProcessesForPDSCH-v1700 is present in pdsch-ServingCellConfig of at least one serving cell in the PUCCH group. If perHARQ-Ext is present, the UE ignores perHARQ.
Conditional Presence Explanation
MCG-OnlyThis field is optionally present, Need R, in the PhysicalCellGroupConfig of the MCG. It is absent otherwise.
SCG-OnlyThis field is optionally present, Need S, in the PhysicalCellGroupConfig of the SCG in (NG)EN-DC as defined in TS 38.213. It is absent otherwise.
twoPUCCHgroupThis field is optionally present, Need R, if secondary PUCCH group is configured. It is absent otherwise, Need R.
Up

 –  PLMN-Identityp. 914

The IE PLMN-Identity identifies a Public Land Mobile Network. Further information regarding how to set the IE is specified in TS 23.003.
PLMN-Identity information element
PLMN-Identity field descriptions
mcc
The first element contains the first MCC digit, the second element the second MCC digit and so on. If the field is absent, it takes the same value as the mcc of the immediately preceding IE PLMN-Identity. See TS 23.003.
mnc
The first element contains the first MNC digit, the second element the second MNC digit and so on. See TS 23.003.
Conditional Presence Explanation
MCCThis field is mandatory present when PLMN-Identity is not used in a list or if it is the first entry of PLMN-Identity in a list. Otherwise it is optionally present, Need S.
Up

 –  PLMN-IdentityInfoListp. 914

The IE PLMN-IdentityInfoList includes a list of PLMN identity information.
PLMN-IdentityInfoList information element
PLMN-IdentityInfo field descriptions
cellReservedForOperatorUse
Indicates whether the cell is reserved for operator use (per PLMN), as defined in TS 38.304. This field is ignored by IAB-MT.
gNB-ID-Length
Indicates the length of the gNB ID out of the 36-bit long cellIdentity.
iab-Support
This field combines both the support of IAB and the cell status for IAB. If the field is present, the cell supports IAB and the cell is also considered as a candidate for cell (re)selection for IAB-node; if the field is absent, the cell does not support IAB and/or the cell is barred for IAB-node.
trackingAreaCode
Indicates Tracking Area Code to which the cell indicated by cellIdentity field belongs. The absence of the field indicates that the cell only supports PSCell/SCell functionality (per PLMN) or is an NTN cell.
trackingAreaList
List of Tracking Areas to which the cell indicated by cellIdentity field belongs. If this field is present, network does not configure trackingAreaCode. Total number of different TACs across different PLMN-IdentityInfos shall not exceed maxTAC. This field is only present in an NTN cell.
Up

 –  PLMN-IdentityList2p. 916

Includes a list of PLMN identities.
PLMN-IdentityList2 information element
Up

 –  PRB-Idp. 916

The IE PRB-Id identifies a Physical Resource Block (PRB) position within a carrier.
PRB-Id information element

 –  PTRS-DownlinkConfigp. 916

The IE PTRS-DownlinkConfig is used to configure downlink phase tracking reference signals (PTRS) (see clause 5.1.6.3 of TS 38.214).
PTRS-DownlinkConfig information element
PTRS-DownlinkConfig field descriptions
epre-Ratio
EPRE ratio between PTRS and PDSCH. Value 0 corresponds to the codepoint "00" in Table 4.1-2. Value 1 corresponds to codepoint "01", and so on. If the field is not provided, the UE applies value 0 (see clause 4.1 of TS 38.214)
frequencyDensity
Presence and frequency density of DL PT-RS as a function of Scheduled BW. If the field is absent, the UE uses K_PT-RS = 2 (see clause 5.1.6.3 of TS 38.214, Table 5.1.6.3-2).
maxNrofPorts
The maximum number of DL PTRS ports specified in clause 5.1.6.3 of TS 38.214. 2 PT-RS ports can only be configured for a DL BWP that is configured, as specified in clause 5.1 of TS 38.214, with a mode where a single PDSCH has association between the DM-RS ports and the TCI states as defined in clause 5.1.6.2 of TS 38.214.
resourceElementOffset
Indicates the subcarrier offset for DL PTRS. If the field is absent, the UE applies the value offset00 (see clause 7.4.1.2.2 of TS 38.211).
timeDensity
Presence and time density of DL PT-RS as a function of MCS. The value 29 is only applicable for MCS Table 5.1.3.1-1 (TS 38.214). If the field is absent, the UE uses L_PT-RS = 1 (see clause 5.1.6.3 of TS 38.214, table 5.1.6.3-1).
Up

 –  PTRS-UplinkConfigp. 917

The IE PTRS-UplinkConfig is used to configure uplink Phase-Tracking-Reference-Signals (PTRS).
PTRS-UplinkConfig information element
PTRS-UplinkConfig field descriptions
frequencyDensity
Presence and frequency density of UL PT-RS for CP-OFDM waveform as a function of scheduled BW If the field is absent, the UE uses K_PT-RS = 2 (see clause 6.1 of TS 38.214)
maxNrofPorts
The maximum number of UL PTRS ports for CP-OFDM (see clause 6.2.3.1 of TS 38.214).
ptrs-Power
UL PTRS power boosting factor per PTRS port (see clause 6.1 of TS 38.214, table 6.2.3.1.3).
resourceElementOffset
Indicates the subcarrier offset for UL PTRS for CP-OFDM. If the field is absent, the UE applies the value offset00 (see clause 6.4.1.2.2 of TS 38.211).
sampleDensity
Sample density of PT-RS for DFT-s-OFDM, pre-DFT, indicating a set of thresholds T={NRBn, n=0,1,2,3,4}, that indicates dependency between presence of PT-RS and scheduled BW and the values of X and K the UE should use depending on the scheduled BW, see clause 6.1 of TS 38.214, table 6.2.3.2-1.
timeDensity
Presence and time density of UL PT-RS for CP-OFDM waveform as a function of MCS If the field is absent, the UE uses L_PT-RS = 1 (see clause 6.1 of TS 38.214)
timeDensityTransformPrecoding
Time density (OFDM symbol level) of PT-RS for DFT-s-OFDM. If the field is absent, the UE applies value d1 (see clause 6.1 of TS 38.214)
transformPrecoderDisabled
Configuration of UL PTRS without transform precoder (with CP-OFDM).
transformPrecoderEnabled
Configuration of UL PTRS with transform precoder (DFT-S-OFDM).
Up

 –  PUCCH-Configp. 918

The IE PUCCH-Config is used to configure UE specific PUCCH parameters (per BWP).
PUCCH-Config information element
PUCCH-Config field descriptions
dl-DataToUL-ACK, dl-DataToUL-ACK-DCI-1-2
List of timing for given PDSCH to the DL ACK (see clause 9.1.2 of TS 38.213). The field dl-DataToUL-ACK applies to DCI format 1_1 and the field dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2 (see clause 7.3.1 of TS 38.212 and clause 9.2.3 of TS 38.213). The dl-DataToUL-ACK-v1700 is applicable for NTN and dl-DataToUL-ACK-r17 is applicable for up to 71 GHz. If dl-DataToUL-ACK-r16 or dl-DataToUL-ACK-r17 or dl-DataToUL-ACK-v1700 is signalled, UE shall ignore the dl-DataToUL-ACK (without suffix). The value -1 corresponds to "inapplicable value" for the case where the A/N feedback timing is not explicitly included at the time of scheduling PDSCH. The fields dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 are only applicable for SCS of 480 kHz or 960 kHz.
dl-DataToUL-ACK-MulticastDCI-Format4-1
List of timing for given group-common PDSCH to the DL ACK (see clause 9.1.2 of TS 38.213). The field dl-DataToUL-ACK-MulticastDciFormat4-1 applies to DCI format 4_1 for MBS multicast (see clause 7.3.1 of TS 38.212 and clause 9.2.3 of TS 38.213).
dmrs-BundlingPUCCH-Config
Configuration of the parameters for DMRS bundling for PUCCH (see clause 6.1.7 of TS 38.214). DMRS bundling for PUCCH is not supported for PUCCH format 0/2. In this release, this is not applicable to FR2-2.
dmrs-UplinkTransformPrecodingPUCCH
This field is used for PUCCH formats 3 and 4 according to clause 6.4.1.3.3.1 of TS 38.211.
format0
Parameters that are common for all PUCCH resources of format 0.
format1
Parameters that are common for all PUCCH resources of format 1.
format2
Parameters that are common for all PUCCH resources of format 2.
format3
Parameters that are common for all PUCCH resources of format 3.
format4
Parameters that are common for all PUCCH resources of format 4.
mappingPattern
Indicates whether the UE should follow Cyclical mapping pattern or Sequential mapping pattern for when a PUCCH resource used for repetitions of a PUCCH transmission includes first and second spatial settings for FR2, or first and second sets of power control parameters for FR1 (see clause 9.2.6 of TS 38.213).
numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2
Configuration of the number of bits for "PUCCH resource indicator" in DCI format 1_2 (see clause 7.3.1 of TS 38.212 and clause 9.2.3 of TS 38.213).
powerControlSetInfoToAddModList
Configures power control sets for repetition of a PUCCH transmission in FR1. This field is not configured if ul-powerControl is configured in the BWP-UplinkDedicated in which the PUCCH-Config is included.
pucch-PowerControl
Configures power control parameters PUCCH transmission. This field is not configured if unifiedTCI-StateType is configured for the serving cell.
resourceGroupToAddModList, resourceGroupToReleaseList
Lists for adding and releasing groups of PUCCH resources that can be updated simultaneously for spatial relations with a MAC CE.
resourceSetToAddModList, resourceSetToReleaseList
Lists for adding and releasing PUCCH resource sets (see clause 9.2 of TS 38.213).
resourceToAddModList, resourceToAddModListExt, resourceToReleaseList
Lists for adding and releasing PUCCH resources applicable for the UL BWP and serving cell in which the PUCCH-Config is defined. The resources defined herein are referred to from other parts of the configuration to determine which resource the UE shall use for which report. If the network includes of resourceToAddModListExt, it includes the same number of entries, and listed in the same order, as in resourceToAddModList.
secondTPCFieldDCI-1-1, secondTPCFieldDCI-1-2
A second TPC field can be configured via RRC for DCI-1-1 and DCI-1-2. Each TPC field is for each closed-loop index value respectively (i.e., 1st /2nd TPC fields correspond to "closedLoopIndex" value = 0 and 1.
spatialRelationInfoToAddModList, spatialRelationInfoToAddModListSizeExt , spatialRelationInfoToAddModListExt
Configuration of the spatial relation between a reference RS and PUCCH. Reference RS can be SSB/CSI-RS/SRS. If the list has more than one element, MAC-CE selects a single element (see clause 5.18.8 of TS 38.321, and clause 9.2.2 of TS 38.213). The UE shall consider entries in spatialRelationInfoToAddModList and in spatialRelationInfoToAddModListSizeExt as a single list, i.e. an entry created using spatialRelationInfoToAddModList can be modified using spatialRelationInfoToAddModListSizeExt (or deleted using spatialRelationInfoToReleaseListSizeExt) and vice-versa. If the network includes spatialRelationInfoToAddModListExt, it includes the same number of entries, and listed in the same order, as in the concatenation of spatialRelationInfoToAddModList and of spatialRelationInfoToAddModListSizeExt. If unifiedTCI-StateType is configured for the serving cell, no element in this list is configured.
spatialRelationInfoToReleaseList, spatialRelationInfoToReleaseListSizeExt, spatialRelationInfoToReleaseListExt
Lists of spatial relation configurations between a reference RS and PUCCH to be released by the UE.
sps-PUCCH-AN-List
Indicates a list of PUCCH resources for DL SPS HARQ ACK. The field maxPayloadSize is absent for the first and the last SPS-PUCCH-AN in the list. If configured, this overrides n1PUCCH-AN in SPS-config.
sps-PUCCH-AN-ListMulticast
The field is used to configure the list of PUCCH resources per HARQ ACK codebook for MBS multicast.
subslotLengthForPUCCH
Indicates the sub-slot length for sub-slot based PUCCH feedback in number of symbols (see clause 9 of TS 38.213). Value n2 corresponds to 2 symbols, value n6 corresponds to 6 symbols, value n7 corresponds to 7 symbols. For normal CP, the value is either n2 or n7. For extended CP, the value is either n2 or n6.
ul-AccessConfigListDCI-1-1, ul-AccessConfigListDCI-1-2
List of the combinations of cyclic prefix extension and UL channel access type (see clause 7.3.1 of TS 38.212) applicable, respectively, to DCI format 1_1 and DCI format 1_2. The fields ul-AccessConfigListDCI-1-1-r16 and ul-AccessConfigListDCI-1-2-r17 are only applicable for FR1 (see TS 38.212, Table 7.3.1.2.2-6). The field ul-AccessConfigListDCI-1-1-r17 indicates a list which only contains UL channel access types and is only applicable for FR2-2 (see TS 38.212, Table 7.3.1.2.2-6A).
PUCCH-format3 field descriptions
nrofPRBs
The supported values are 1,2,3,4,5,6,8,9,10,12,15 and 16. The UE shall ignore this field when format-v1610 is configured.
PUCCH-FormatConfig, PUCCH-FormatConfigExt field descriptions
additionalDMRS
If the field is present, the UE enables 2 DMRS symbols per hop of a PUCCH Format 3 or 4 if both hops are more than X symbols when FH is enabled (X=4). And it enables 4 DMRS symbols for a PUCCH Format 3 or 4 with more than 2X+1 symbols when FH is disabled (X=4). The field is not applicable for format 0, 1 and 2. See clause 9.2.2 of TS 38.213.
interslotFrequencyHopping
If the field is present, the UE enables inter-slot frequency hopping when PUCCH Format 0, 1, 2, 3 or 4 is repeated over multiple slots. For a PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. See clause 9.2.6 of TS 38.213.
maxCodeRate
Max coding rate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. The field is not applicable for format 0 and 1. See clause 9.2.5 of TS 38.213.
maxCodeRateLP
Max coding rate to determine how to feedback UCI on PUCCH for format 2, 3 or 4. The field is not applicable for format 0 and 1. This field configures additional max code rate in the second entry of PUCCH-ConfigurationList-r16 for multiplexing low-priority (LP) HARQ-ACK and high-priority (HP) UCI in a PUCCH as described in clause 9.2.5.3 of TS 38.213. The field is absent for the first entry of PUCCH-ConfigurationList-r16.
nrofSlots
Number of slots with the same PUCCH. When the field is absent the UE applies the value n1. See clause 9.2.6 of TS 38.213.
pi2BPSK
If the field is present, the UE uses pi/2 BPSK for UCI symbols instead of QPSK for PUCCH. The field is not applicable for format 0, 1 and 2. See clause 9.2.5 of TS 38.213.
rb-SetIndex
Indicates the RB set where PUCCH resource is allocated.
simultaneousHARQ-ACK-CSI
If the field is present, the UE uses simultaneous transmission of CSI and HARQ-ACK feedback with or without SR with PUCCH Format 2, 3 or 4. See clause 9.2.5 of TS 38.213. When the field is absent the UE applies the value off. The field is not applicable for format 0 and 1.
PUCCH-Resource, PUCCH-ResourceExt field descriptions
format
Selection of the PUCCH format (format 0 - 4) and format-specific parameters, see clause 9.2 of TS 38.213. format0 and format1 are only allowed for a resource in a first PUCCH resource set. format2, format3 and format4 are only allowed for a resource in non-first PUCCH resource set. The network can only configure format-v1610 when format is set to format2 or format3. The network only configures format-v1700 when format is set to format0, format1 or format4.
interlace0
This is the only interlace of interlaced PUCCH Format 0 and 1 and the first interlace for interlaced PUCCH Format 2 and 3.
interlace1
A second interlace, in addition to interlace 0, as specified in clause 9.2.1 of TS 38.213. For 15kHz SCS, values {0..9} are applicable; for 30kHz SCS, values {0..4} are applicable. For 15kHz SCS, the values of interlace1 shall satisfy interlace1=mod(interlace0+X,10) where X=1, -1, or 5.
intraSlotFrequencyHopping
Enabling intra-slot frequency hopping, applicable for all types of PUCCH formats. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. See clause 9.2.1 of TS 38.213.
nrofPRBs
Indicates the number of PRBs used per PUCCH resource for the PUCCH format, see clause 9.2.1 of TS 38.213. This field is applicable for PUCCH format0, format1, and format4 in FR2-2. The supported values for format4 are 1,2,3,4,5,6,8,9,10,12,15 and 16.
occ-Index
Indicates the orthogonal cover code index (see clause 9.2.1 of TS 38.213). This field is applicable when useInterlacePUCCH-PUSCH-16 is configured.
occ-Length
Indicates the orthogonal cover code length (see clause 9.2.1 of TS 38.213). This field is applicable when useInterlacePUCCH-PUSCH-16 is configured.
pucch-RepetitionNrofSlots
Configuration of PUCCH repetition factor per PUCCH resource with associated scheduling DCI corresponding to Rel-17 dynamic PUCCH repetition. For a PUCCH resource, if both the field pucch-RepetitionNrofSlots and the field nrofSlots are present, the field nrofSlots is ignored and apply the value of pucch-RepetitionNrofSlots corresponding to Rel-17 dynamic PUCCH repetition. If this field is absent in a PUCCH resource with associated scheduling DCI, the UE applies the value of field nrofSlots.
pucch-ResourceId
Identifier of the PUCCH resource.
secondHopPRB
Index of first PRB after frequency hopping of PUCCH. This value is applicable for intra-slot frequency hopping (see clause 9.2.1 of TS 38.213) or inter-slot frequency hopping (see clause 9.2.6 of TS 38.213).
PUCCH-ResourceSet field descriptions
maxPayloadSize
Maximum number of UCI information bits that the UE may transmit using this PUCCH resource set (see clause 9.2.1 of TS 38.213). In a PUCCH occurrence, the UE chooses the first of its PUCCH-ResourceSet which supports the number of bits that the UE wants to transmit. The field is absent in the first set (Set0) and in the last configured set since the UE derives the maximum number of UCI information bits as specified in clause 9.2.1 of TS 38.213. This field can take integer values that are multiples of 4.
resourceList
PUCCH resources of format0 and format1 are only allowed in the first PUCCH resource set, i.e., in a PUCCH-ResourceSet with pucch-ResourceSetId = 0. This set may contain between 1 and 32 resources. PUCCH resources of format2, format3 and format4 are only allowed in a PUCCH-ResourceSet with pucch-ResourceSetId > 0. If present, these sets contain between 1 and 8 resources each. The UE chooses a PUCCH-Resource from this list as specified in clause 9.2.3 of TS 38.213. Note that this list contains only a list of resource IDs. The actual resources are configured in PUCCH-Config.
Conditional Presence Explanation
PI2-BPSKThe field is optionally present, Need R, if format3 and/or format4 are configured and pi2BPSK is configured in each of them. It is absent, Need R otherwise.
Up

 –  PUCCH-ConfigCommonp. 927

The IE PUCCH-ConfigCommon is used to configure the cell specific PUCCH parameters.
PUCCH-ConfigCommon information element
PUCCH-ConfigCommon field descriptions
additionalPRBOffset
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.
hoppingId
Cell-specific scrambling ID for group hopping and sequence hopping if enabled, see clause 6.3.2.2 of TS 38.211.
intra-SlotFH-r17
In case a separate initial UL BWP is configured for 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 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.
nrofPRBs
Indicates the number of PRBs used per PUCCH resource for PUCCH format 0 and format 1 in FR2-2, see clause 9.2.1 of TS 38.213.
p0-nominal
Power control parameter P0 for PUCCH transmissions. Value in dBm. Only even values (step size 2) allowed (see clause 7.2 of TS 38.213).
pucch-GroupHopping
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 clause 6.3.2.2 of TS 38.211).
pucch-ResourceCommon
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 clause 9.2 of TS 38.213).
pucch-ResourceCommonRedCap
An entry into a 16-row table where each row configures a set of cell-specific PUCCH resources/parameters for 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 clause 9.2 of TS 38.213).
Conditional Presence Explanation
InitialBWP-OnlyThe field is mandatory present in the PUCCH-ConfigCommon of the initial BWP (BWP#0) in SIB1. It is absent in other BWPs including the RedCap-specific initial uplink BWP, if configured.
InitialBWP-RedCapThe field is mandatory present in the PUCCH-ConfigCommon of the RedCap-specific initial BWP. It is optional present, Need R, in the PUCCH-ConfigCommon of the initial BWP configured by initialUplinkBWP. It is absent in other BWPs.
InitialBWP-RedCapOnlyThe field is optional present, Need S, in the PUCCH-ConfigCommon of the RedCap-specific initial BWP. It is absent in other BWPs.
Up

 –  PUCCH-ConfigurationListp. 928

The IE PUCCH-ConfigurationList is used to configure UE specific PUCCH parameters (per BWP) for two simultaneously constructed HARQ-ACK codebooks. See clause 9.1 of TS 38.213.
PUCCH-ConfigurationList information element
Up

 –  PUCCH-CSI-Resourcep. 929

 –  PUCCH-PathlossReferenceRS-Idp. 929

The IE PUCCH-PathlossReferenceRS-Id is an ID for a reference signal (RS) configured as PUCCH pathloss reference (see clause 7.2 of TS 38.213).
PUCCH-PathlossReferenceRS-Id information element
Up

 –  PUCCH-PowerControlp. 930

The IE PUCCH-PowerControl is used to configure UE-specific parameters for the power control of PUCCH.
PUCCH-PowerControl information element
P0-PUCCH field descriptions
p0-PUCCH-Value
P0 value for PUCCH with 1dB step size.
PUCCH-PowerControl field descriptions
deltaF-PUCCH-f0
deltaF for PUCCH format 0 with 1dB step size (see clause 7.2 of TS 38.213).
deltaF-PUCCH-f1
deltaF for PUCCH format 1 with 1dB step size (see clause 7.2 of TS 38.213).
deltaF-PUCCH-f2
deltaF for PUCCH format 2 with 1dB step size (see clause 7.2 of TS 38.213).
deltaF-PUCCH-f3
deltaF for PUCCH format 3 with 1dB step size (see clause 7.2 of TS 38.213).
deltaF-PUCCH-f4
deltaF for PUCCH format 4 with 1dB step size (see clause 7.2 of TS 38.213).
p0-Set
A set with dedicated P0 values for PUCCH, i.e., {P01, P02,... } (see clause 7.2 of TS 38.213).
pathlossReferenceRSs, pathlossReferenceRSs-v1610
A set of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for PUCCH pathloss estimation. Up to maxNrofPUCCH-PathlossReference-RSs may be configured. If the field is not configured, the UE uses the SSB as reference signal (see clause 7.2 of TS 38.213). The set includes Reference Signals indicated in pathlossReferenceRSs (without suffix) and in pathlossReferenceRSs-v1610. The UE maintains pathlossReferenceRSs and pathlossReferenceRSs-v1610 separately: Receiving pathlossReferenceRSs-v1610 set to release releases only the entries that were configured by pathlossReferenceRSs-v1610, and receiving pathlossReferenceRSs-v1610 set to setup replaces only the entries that were configured by pathlossReferenceRSs-v1610 with the newly signalled entries.
twoPUCCH-PC-AdjustmentStates
Number of PUCCH power control adjustment states maintained by the UE (i.e., g(i)). If the field is present (n2) the UE maintains two power control states (i.e., g(i,0) and g(i,1)). If the field is absent, it maintains one power control state (i.e., g(i,0)) (see clause 7.2 of TS 38.213).
Up

 –  PUCCH-SpatialRelationInfop. 932

The IE PUCCH-SpatialRelationInfo is used to configure the spatial setting for PUCCH transmission and the parameters for PUCCH power control, see clause 9.2.2 of TS 38.213.
PUCCH-SpatialRelationInfo information element
PUCCH-SpatialRelationInfo field descriptions
pucch-PathLossReferenceRS-Id
When pucch-PathLossReferenceRS-Id-v1610 is configured, the UE shall ignore pucch-PathLossReferenceRS-Id (without suffix).
pucch-SpatialRelationInfoId
When pucch-SpatialRelationInfoId-v1610 is configured, the UE shall ignore pucch-SpatialRelationInfoId (without suffix). If pucch-SpatialRelationInfoId-v1610 is absent, the UE shall use the pucch-SpatialRelationInfoId (without suffix).
servingCellId
If the field is absent, the UE applies the ServCellId of the serving cell in which this PUCCH-SpatialRelationInfo is configured
Up

 –  PUCCH-SpatialRelationInfo-Idp. 933

The IE PUCCH-SpatialRelationInfo-Id is used to identify a PUCCH-SpatialRelationInfo
PUCCH-SpatialRelationInfo-Id information element
Up

 –  PUCCH-TPC-CommandConfigp. 933

The IE PUCCH-TPC-CommandConfig is used to configure the UE for extracting TPC commands for PUCCH from a group-TPC messages on DCI.
PUCCH-TPC-CommandConfig information element
PUCCH-TPC-CommandConfig field descriptions
tpc-IndexPCell
An index determining the position of the first bit of TPC command (applicable to the SpCell) inside the DCI format 2-2 payload.
tpc-IndexPUCCH-SCell
An index determining the position of the first bit of TPC command (applicable to the PUCCH SCell) inside the DCI format 2-2 payload.
tpc-IndexPUCCH-sSCell, tpc-IndexPUCCH-sSCellSecondaryPUCCHgroup
An index determining the position of the first bit of TPC command (applicable to the alternative PUCCH cell for PUCCH cell switching) inside the DCI format 2-2 payload, for the primary PUCCH group and the secondary PUCCH group respectively.
Conditional Presence Explanation
PDCCH-OfSpcellThe field is mandatory present if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the SpCell. Otherwise, the field is absent, Need R.
PDCCH-ofSpCellOrPUCCH-SCellThe field is mandatory present if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the PUCCH-SCell.
The field is optionally present, need R, if the UE is configured with a PUCCH SCell in this cell group and if the PUCCH-TPC-CommandConfig is provided in the PDCCH-Config for the SpCell.
Otherwise, the field is absent, Need R.
twoPUCCHgroupThis field is optionally present, Need R, if secondary PUCCH group is configured. It is absent otherwise.
Up

 –  PUSCH-Configp. 934

The IE PUSCH-Config is used to configure the UE specific PUSCH parameters applicable to a particular BWP.
PUSCH-Config information element
PUSCH-Config field descriptions
antennaPortsFieldPresenceDCI-0-2
Configure the presence of "Antenna ports" field in DCI format 0_2. When the field is configured, then the "Antenna ports" field is present in DCI format 0_2. Otherwise, the field size is set to 0 for DCI format 0_2 (See clause 7.3.1.1.3 of TS 38.212). If neither dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 nor dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 is configured, this field is absent.
availableSlotCounting
Indicate whether PUSCH repetitions counted on the basis of available slots is enabled. If the field is absent, PUSCH repetitions counted on the basis of available slots is disabled.
betaOffsetsCrossPri0, betaOffsetsCrossPri1, betaOffsetsCrossPri0DCI-0-2, betaOffsetsCrossPri1DCI-0-2
Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK on dynamically scheduled PUSCH with different priorities, see clause 9.3 of TS 38.213.
The field betaOffsetsCrossPrio0 indicates multiplexing low priority (LP) HARQ-ACK on dynamically scheduled high priority (HP) PUSCH.
The field betaOffsetsCrossPrio1 indicates multiplexing HP HARQ-ACK on dynamically scheduled LP PUSCH.
The field betaOffsetsCrossPrio0DCI-0-2 indicates multiplexing LP HARQ-ACK on dynamically scheduled HP PUSCH by DCI format 0_2.
The field betaOffsetsCrossPrio1DCI-0-2 indicates multiplexing HP HARQ-ACK on dynamically scheduled LP PUSCH by DCI format 0_2.
codebookSubset, codebookSubsetDCI-0-2
Subset of PMIs addressed by TPMI, where PMIs are those supported by UEs with maximum coherence capabilities (see clause 6.1.1.1 of TS 38.214). The field codebookSubset applies to DCI format 0_1 and the field codebookSubsetDCI-0-2 applies to DCI format 0_2 (see clause 6.1.1.1 of TS 38.214).
dataScramblingIdentityPUSCH
Identifier used to initialise data scrambling (c_init) for PUSCH. If the field is absent, the UE applies the physical cell ID. (see clause 6.3.1.1 of TS 38.211).
dmrs-BundlingPUSCH-Config
Configure the parameters for DMRS bundling for PUSCH (see clause 6.1.7 of TS 38.214). In this release, this is not applicable to FR2-2.
dmrs-SequenceInitializationDCI-0-2
Configure whether the field "DMRS Sequence Initialization" is present or not in DCI format 0_2. If the field is absent, then 0 bit for the field "DMRS Sequence Initialization" in DCI format 0_2. If the field is present, then the number of bits is determined in the same way as DCI format 0_1 (see clause 7.3.1 of TS 38.212).
dmrs-UplinkForPUSCH-MappingTypeA, dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2
DMRS configuration for PUSCH transmissions using PUSCH mapping type A (chosen dynamically via PUSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeA applies to DCI format 0_1 and the field dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 applies to DCI format 0_2 (see clause 7.3.1 of TS 38.212).
dmrs-UplinkForPUSCH-MappingTypeB, dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2
DMRS configuration for PUSCH transmissions using PUSCH mapping type B (chosen dynamically via PUSCH-TimeDomainResourceAllocation). Only the fields dmrs-Type, dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-UplinkForPUSCH-MappingTypeB applies to DCI format 0_1 and the field dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 applies to DCI format 0_2 (see clause 7.3.1 of TS 38.212).
frequencyHopping
The value intraSlot enables 'Intra-slot frequency hopping' and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for 'pusch-RepTypeA' (see clause 6.3 of TS 38.214). The field frequencyHopping applies to DCI format 0_0 and 0_1 for 'pusch-RepTypeA'.
frequencyHoppingDCI-0-1
Indicates the frequency hopping scheme for DCI format 0_1 when pusch-RepTypeIndicatorDCI-0-1 is set to 'pusch-RepTypeB', The value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured for DCI format 0_1 for 'pusch-RepTypeB' (see clause 6.1 of TS 38.214).
frequencyHoppingDCI-0-2
Indicate the frequency hopping scheme for DCI format 0_2. The value intraSlot enables 'intra-slot frequency hopping', and the value interRepetition enables 'Inter-repetition frequency hopping', and the value interSlot enables 'Inter-slot frequency hopping'. When pusch-RepTypeIndicatorDCI-0-2 is not set to 'pusch-RepTypeB', the frequency hopping scheme can be chosen between 'intra-slot frequency hopping' and 'inter-slot frequency hopping' if enabled. When pusch-RepTypeIndicatorDCI-0-2 is set to 'pusch-RepTypeB', the frequency hopping scheme can be chosen between 'inter-repetition frequency hopping' and 'inter-slot frequency hopping' if enabled. If the field is absent, frequency hopping is not configured for DCI format 0_2 (see clause 6.3 of TS 38.214).
frequencyHoppingOffsetLists, frequencyHoppingOffsetListsDCI-0-2
Set of frequency hopping offsets used when frequency hopping is enabled for granted transmission (not msg3) and type 2 configured grant activation (see clause 6.3 of TS 38.214). The field frequencyHoppingOffsetLists applies to DCI format 0_0 and DCI format 0_1 and the field frequencyHoppingOffsetListsDCI-0-2 applies to DCI format 0_2 (see clause 6.3 of TS 38.214).
harq-ProcessNumberSizeDCI-0-2
Configure the number of bits for the field "HARQ process number" in DCI format 0_2 (see clause 7.3.1 of TS 38.212).
invalidSymbolPattern
Indicates one pattern for invalid symbols for PUSCH transmission repetition type B applicable to both DCI format 0_1 and 0_2. If InvalidSymbolPattern is not configured, semi-static flexible symbols are used for PUSCH. Segmentation occurs only around semi-static DL symbols (see clause 6.1 of TS 38.214).
invalidSymbolPatternIndicatorDCI-0-1, invalidSymbolPatternIndicatorDCI-0-2
Indicates the presence of an additional bit in the DCI format 0_1/0_2. If invalidSymbolPattern is absent, then both invalidSymbolPatternIndicatorDCI-0-1 and invalidSymbolPatternIndicatorDCI-0-2 are absent. The field invalidSymbolPatternIndicatorDCI-0-1 applies to the DCI format 0_1 and the field invalidSymbolPatternIndicatorDCI-0-2 applies to DCI format 0_2 (see clause 6.1 of TS 38.214). If the field is absent, the UE behaviour is specified in clause 6.1.2.1 of TS 38.214.
mappingPattern
Indicates whether the UE should follow Cyclical mapping pattern or Sequential mapping pattern for when two SRS resource sets are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook' for PUSCH transmission and the PUSCH transmission occasions are associated with both SRS resource sets.
maxRank, maxRankDCI-0-2
Subset of PMIs addressed by TRIs from 1 to ULmaxRank (see clause 6.1.1.1 of TS 38.214). The field maxRank applies to DCI format 0_1 and the field maxRankDCI-0-2 applies to DCI format 0_2 (see clause 6.1.1.1 of TS 38.214).
mcs-Table, mcs-TableFormat0-2m
Indicates which MCS table the UE shall use for PUSCH without transform precoder (see clause 6.1.4.1 of TS 38.214). If the field is absent the UE applies the value 64QAM. The field mcs-Table applies to DCI format 0_0 and DCI format 0_1 and the field mcs-TableDCI-0-2 applies to DCI format 0_2 (see clause 6.1.4.1 of TS 38.214).
mcs-TableTransformPrecoder, mcs-TableTransformPrecoderDCI-0-2
Indicates which MCS table the UE shall use for PUSCH with transform precoding (see clause 6.1.4.1 of TS 38.214) If the field is absent the UE applies the value 64QAM. The field mcs-TableTransformPrecoder applies to DCI format 0_0 and DCI format 0_1 and the field mcs-TableTransformPrecoderDCI-0-2 applies to DCI format 0_2 (see clause 6.1.4.1 of TS 38.214).
minimumSchedulingOffsetK2
List of minimum K2 values. Minimum K2 parameter denotes minimum applicable value(s) for the Time domain resource assignment table for PUSCH (see clause 6.1.2.1 of TS 38.214).
mpe-ResourcePoolToAddModList
List of SSB/CSI-RS resources for P-MPR reporting. Each resource is configured with serving cell index where the resource is configured for the UE. The additionalPCI is configured only if the resource is SSB. For each resource, if neither cell nor additionalPCI is present, the SSB/CSI-RS resource is from the serving cell where the PUSCH-Config is configured.
numberOfBitsForRV-DCI-0-2
Configures the number of bits for "Redundancy version" in the DCI format 0_2 (see clause 7.3.1 of TS 38.212 and clause 6.1.2.1 of TS 38.214).
numberOfInvalidSymbolsForDL-UL-Switching
Indicates the number of symbols after the last semi-static DL symbol that are invalid symbols for PUSCH repetition Type B. If it is absent, no symbol is explicitly defined for DL-to-UL switching (see clause 6.1 of TS 38.214)
priorityIndicatorDCI-0-1, priorityIndicatorDCI-0-2
Configures the presence of "priority indicator" in DCI format 0_1/0_2. When the field is absent in the IE, then the UE shall apply 0 bit for "Priority indicator" in DCI format 0_1/0_2. The field priorityIndicatorDCI-0-1 applies to DCI format 0_1 and the field priorityIndicatorDCI-0-2 applies to DCI format 0_2 (see clause 7.3.1 of TS 38.212 and clause 9 of TS 38.213).
pusch-AggregationFactor
Number of repetitions for data (see clause 6.1.2.1 of TS 38.214). If the field is absent the UE applies the value 1.
pusch-PowerControl
Configures power control parameters PUSCH transmission. This field is not configured if unifiedTCI-StateType is configured for the serving cell.
pusch-RepTypeIndicatorDCI-0-1, pusch-RepTypeIndicatorDCI-0-2
Indicates whether UE follows the behavior for "PUSCH repetition type A" or the behavior for "PUSCH repetition type B" for the PUSCH scheduled by DCI format 0_1/0_2 and for Type 2 CG associated with the activating DCI format 0_1/0_2.The value pusch-RepTypeA enables the 'PUSCH repetition type A' and the value pusch-RepTypeB enables the 'PUSCH repetition type B'. The field pusch-RepTypeIndicatorDCI-0-1 applies to DCI format 0_1 and the field pusch-RepTypeIndicatorDCI-0-2 applies to DCI format 0_2 (see clause 6.1.2.1 of TS 38.214).
pusch-TimeDomainAllocationList
List of time domain allocations for timing of UL assignment to UL data (see TS 38.214, table 6.1.2.1.1-1). The field pusch-TimeDomainAllocationList applies to DCI formats 0_0 or DCI format 0_1 when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured (see TS 38.214, table 6.1.2.1.1-1 and table 6.1.2.1.1-1A). The network does not configure the pusch-TimeDomainAllocationList (without suffix) simultaneously with the pusch-TimeDomainAllocationListDCI-0-2-r16 or pusch-TimeDomainAllocationListDCI-0-1-r16 or pusch-TimeDomainAllocationListForMultiPUSCH-r16.
pusch-TimeDomainAllocationListDCI-0-1
Configuration of the time domain resource allocation (TDRA) table for DCI format 0_1 (see clause 6.1 of TS 38.214, table 6.1.2.1.1-1A).
pusch-TimeDomainAllocationListDCI-0-2
Configuration of the time domain resource allocation (TDRA) table for DCI format 0_2 (see clause 6.1.2 of TS 38.214, table 6.1.2.1.1-1B).
pusch-TimeDomainAllocationListForMultiPUSCH
Configuration of the time domain resource allocation (TDRA) table for multiple PUSCH (see clause 6.1.2 of TS 38.214). The network configures at most 64 rows in this TDRA table in PUSCH-TimeDomainResourceAllocationList-r16 configured by this field. This field is not configured simultaneously with pusch-AggregationFactor. The network does not configure the pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the pusch-TimeDomainAllocationListDCI-0-1-r16. The network does not configure the pusch-TimeDomainAllocationListForMultiPUSCH-r16 simultaneously with the numberOfSlotsTBoMS-r17.
rbg-Size
Selection between configuration 1 and configuration 2 for RBG size for PUSCH. The UE does not apply this field if resourceAllocation is set to resourceAllocationType1. Otherwise, the UE applies the value config1 when the field is absent (see clause 6.1.2.2.1 of TS 38.214).
resourceAllocation, resourceAllocationDCI-0-2
Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see clause 6.1.2 of TS 38.214). The field resourceAllocation applies to DCI format 0_1 and the field resourceAllocationDCI-0-2 applies to DCI format 0_2 (see clause 6.1.2 of TS 38.214).
resourceAllocationType1GranularityDCI-0-2
Configures the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 0_2. If this field is absent, the granularity is 1 PRB (see clause 6.1.2.2.2 of TS 38.214).
secondTPCFieldDCI-0-1, secondTPCFieldDCI-0-2
A second TPC field can be configured via RRC for DCI-0-1 and DCI-0-2. Each TPC field is for each closed-loop index value respectively (i.e., 1st /2nd TPC fields correspond to "closedLoopIndex" value = 0 and 1,
sequenceOffsetForRV
Configures the RV offset for the starting RV for the first repetition (first actual repetition in PUSCH repetition Type B) towards the second 'SRS resource set' for PUSCH configured in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage 'codebook' or 'noncodebook'.
tp-pi2BPSK
Enables pi/2-BPSK modulation with transform precoding if the field is present and disables it otherwise.
transformPrecoder
The UE specific selection of transformer precoder for PUSCH (see clause 6.1.3 of TS 38.214). When the field is absent the UE applies the value of the field msg3-transformPrecoder from rach-ConfigCommon included directly within BWP configuration (i.e., not included in additionalRACH-ConfigList).
txConfig
Whether UE uses codebook based or non-codebook based transmission (see clause 6.1.1 of TS 38.214). If the field is absent, the UE transmits PUSCH on one antenna port, see clause 6.1.1 of TS 38.214.
uci-OnPUSCH-ListDCI-0-1, uci-OnPUSCH-ListDCI-0-2
Configuration for up to 2 HARQ-ACK codebooks specific to DCI format 0_1/0_2. The field uci-OnPUSCH-ListDCI-0-1 applies to DCI format 0_1 and the field uci-OnPUSCH-ListDCI-0-2 applies to DCI format 0_2 (see clause 7.3.1 of TS 38.212 and clause 9.3 of TS 38.213).
ul-AccessConfigListDCI-0-1, ul-AccessConfigListDCI-0-2
List of the combinations of cyclic prefix extension, channel access priority class (CAPC), and UL channel access type (see clause 7.3.1 of TS 38.212) applicable for DCI format 0_1 and DCI format 0_2, respectively. The fields ul-AccessConfigListDCI-0-1-r16 and ul-AccessConfigListDCI-0-2-r17 are only applicable for FR1 (see TS 38.212, Table 7.3.1.1.2-35). The field ul-AccessConfigListDCI-0-1-r17 only contains a list of UL channel access types and is only applicable for FR2-2 (see TS 38.212, Table 7.3.1.1.2-35A).
ul-FullPowerTransmission
Configures the UE with UL full power transmission mode as specified in TS 38.213. This field is not configured if ul-powerControl is configured in the BWP-UplinkDedicated in which the PUCCH-Config is included.
UCI-OnPUSCH field descriptions
betaOffsets
Selection between and configuration of dynamic and semi-static beta-offset for DCI formats other than DCI format 0_2. If the field is not configured, the UE applies the value 'semiStatic' (see clause 9.3 of TS 38.213).
scaling
Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI formats other than DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on. The value configured herein is applicable for PUSCH with configured grant (see clause 6.3 of TS 38.212).
UCI-OnPUSCH-DCI-0-2 field descriptions
betaOffsetsDCI-0-2
Configuration of beta-offset for DCI format 0_2. If semiStaticDCI-0-2 is chosen, the UE shall apply the value of 0 bit for the field of beta offset indicator in DCI format 0_2. If dynamicDCI-0-2 is chosen, the UE shall apply the value of 1 bit or 2 bits for the field of beta offset indicator in DCI format 0_2 (see clause 7.3.1 of TS 38.212 and clause 9.3 of TS 38.213).
dynamicDCI-0-2
Indicates the UE applies the value 'dynamic' for DCI format 0_2 (see clause 7.3.1 of TS 38.212 and clause 9.3 of TS 38.213).
semiStaticDCI-0-2
Indicates the UE applies the value 'semiStatic' for DCI format 0_2. (see clause 7.3.1 of TS 38.212 and see clause 9.3 of TS 38.213).
scalingDCI-0-2
Indicates a scaling factor to limit the number of resource elements assigned to UCI on PUSCH for DCI format 0_2. Value f0p5 corresponds to 0.5, value f0p65 corresponds to 0.65, and so on (see clause 6.3 of TS 38.212).
Conditional Presence Explanation
codebookBasedThe field is mandatory present if txConfig is set to codebook and absent otherwise.
RepTypeBThe field is optionally present, Need S, if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeB. It is absent otherwise.
RepTypeB2The field is optionally present, Need S, if pusch-RepTypeIndicatorDCI-0-1 or pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB. It is absent otherwise.
SRSsetsThis field is mandatory present when UE is configured with two SRS sets in either srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with usage codebook or non-codebook.
Up

 –  PUSCH-ConfigCommonp. 944

The IE PUSCH-ConfigCommon is used to configure the cell specific PUSCH parameters.
PUSCH-ConfigCommon information element
PUSCH-ConfigCommon field descriptions
groupHoppingEnabledTransformPrecoding
For DMRS transmission with transform precoder, the NW may configure group hopping by this cell-specific parameter, see clause 6.4.1.1.1.2 of TS 38.211.
msg3-DeltaPreamble
Power offset between msg3 and RACH preamble transmission. Actual value = field value * 2 [dB] (see clause 7.1 of TS 38.213).
p0-NominalWithGrant
P0 value for PUSCH with grant (except msg3). Value in dBm. Only even values (step size 2) allowed (see clause 7.1 of TS 38.213) This field is cell specific.
pusch-TimeDomainAllocationList
List of time domain allocations for timing of UL assignment to UL data (see TS 38.214, table 6.1.2.1.1-1).
Up

 –  PUSCH-PowerControlp. 945

The IE PUSCH-PowerControl is used to configure UE specific power control parameter for PUSCH.
PUSCH-PowerControl information element
P0-PUSCH-AlphaSet field descriptions
alpha
alpha value for PUSCH with grant (except msg3) (see clause 7.1 of TS 38.213). When the field is absent the UE applies the value 1.
p0
P0 value for PUSCH with grant (except msg3) in steps of 1dB (see clause 7.1 of TS 38.213). When the field is absent the UE applies the value 0.
P0-PUSCH-Set field descriptions
p0-List
Configuration of {p0-PUSCH, p0-PUSCH} sets for PUSCH. If SRI is present in the DCI, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and both olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 are configured to be 1 bit, then one p0-PUSCH can be configured in P0-PUSCH-Set. If SRI is not present in the DCI, and if any of olpc-ParameterSetDCI-0-1 and olpc-ParameterSetDCI-0-2 is configured to be 2 bits, then two p0-PUSCH values can be configured in P0-PUSCH-Set (see clause 7 of TS 38.213 and clause 7.3.1 of TS 38.212).
p0-PUSCH-SetId
Configure the index of a p0-PUSCH-Set (see clause 7 of TS 38.213 and clause 7.3.1 of TS 38.212).
PUSCH-PowerControl field descriptions
deltaMCS
Indicates whether to apply delta MCS. When the field is absent, the UE applies Ks = 0 in delta_TFC formula for PUSCH (see clause 7.1 of TS 38.213).
dummy
This field is not used in the specification. If received it shall be ignored by the UE.
msg3-Alpha
Dedicated alpha value for msg3 PUSCH (see clause 7.1 of TS 38.213). When the field is absent the UE applies the value 1.
olpc-ParameterSetDCI-0-1, olpc-ParameterSetDCI-0-2
Configures the number of bits for Open-loop power control parameter set indication for DCI format 0_1/0_2 in case SRI is not configured in the DCI. 2 bits is applicable only if SRI is not present in the DCI format 0_1. The field olpc-ParameterSetDCI-0-1 applies to DCI format 0_1 and the field olpc-ParameterSetDCI-0-2 applies to DCI format 0_2 (see clause 7.3.1 of TS 38.212 and clause 11 of TS 38.213).
p0-AlphaSets
Configuration {p0-pusch, alpha} sets for PUSCH (except msg3 and msgA PUSCH), i.e., { {p0,alpha,index1}, {p0,alpha,index2},...} (see clause 7.1 of TS 38.213). When no set is configured, the UE uses the P0-nominal for msg3/msgA PUSCH, P0-UE is set to 0 and alpha is set according to either msg3-Alpha or msgA-Alpha (see clause 7.1 of TS 38.213).
p0-NominalWithoutGrant
P0 value for UL grant-free/SPS based PUSCH. Value in dBm. Only even values (step size 2) allowed (see clause 7.1 of TS 38.213).
p0-PUSCH-SetList
Configure one additional P0-PUSCH-Set per SRI. If present, the one bit or 2 bits in the DCI is used to dynamically indicate among the P0 value from the existing P0-PUSCH-AlphaSet and the P0 value(s) from the P0-PUSCH-Set (See clause 7.3.1 of TS 38.212 and clause 17 of TS 38.213).
p0-PUSCH-SetList2
For indicating per-TRP OLPC set in DCI format 0_1/0_2 with the legacy field, a second p0-PUSCH-SetList-r16 is used. When this field is present the p0-PUSCH-SetList corresponds to the first SRS resource set (see TS 38.213).
pathlossReferenceRSToAddModList, pathlossReferenceRSToAddModListSizeExt
A set of Reference Signals (e.g. a CSI-RS config or a SS block) to be used for PUSCH path loss estimation. The set consists of Reference Signals configured using pathLossReferenceRSToAddModList and Reference Signals configured using pathlossReferenceRSToAddModListSizeExt. Up to maxNrofPUSCH-PathlossReferenceRSs may be configured (see clause 7.1 of TS 38.213).
pathlossReferenceRSToReleaseList, pathlossReferenceRSToReleaseListSizeExt
Lists of reference signals for PUSCH path loss estimation to be released by the UE.
sri-PUSCH-MappingToAddModList
A list of SRI-PUSCH-PowerControl elements among which one is selected by the SRI field in DCI (see clause 7.1 of TS 38.213).
sri-PUSCH-MappingToAddModList2
A list of SRI-PUSCH-PowerControl elements for second SRS-resource set, among which one is selected by the SRI field in DCI (see clause 7.1 of TS 38.213). When this field is present the sri-PUSCH-MappingToAddModList corresponds to the first SRS resource set for PUSCH.
tpc-Accumulation
If enabled, UE applies TPC commands via accumulation. If not enabled, UE applies the TPC command without accumulation. If the field is absent, TPC accumulation is enabled (see clause 7.1 of TS 38.213).
twoPUSCH-PC-AdjustmentStates
Number of PUSCH power control adjustment states maintained by the UE (i.e., fc(i)). If the field is present (n2) the UE maintains two power control states (i.e., fc(i,0) and fc(i,1)). If the field is absent, it maintains one power control state (i.e., fc(i,0)) (see clause 7.1 of TS 38.213).
SRI-PUSCH-PowerControl field descriptions
sri-P0-PUSCH-AlphaSetId
The ID of a P0-PUSCH-AlphaSet as configured in p0-AlphaSets in PUSCH-PowerControl.
sri-PUSCH-ClosedLoopIndex
The index of the closed power control loop associated with this SRI-PUSCH-PowerControl.
sri-PUSCH-PathlossReferenceRS-Id
The ID of PUSCH-PathlossReferenceRS as configured in the pathlossReferenceRSToAddModList in PUSCH-PowerControl.
sri-PUSCH-PowerControlId
The ID of this SRI-PUSCH-PowerControl configuration. It is used as the codepoint (payload) in the SRI DCI field.
Up

 –  PUSCH-ServingCellConfigp. 949

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 information element
PUSCH-CodeBlockGroupTransmission field descriptions
maxCodeBlockGroupsPerTransportBlock
Maximum number of code-block-groups (CBGs) per TB (see clause 9.1 of TS 38.213).
PUSCH-ServingCellConfig field descriptions
codeBlockGroupTransmission
Enables and configures code-block-group (CBG) based transmission (see clause 5.1.5 of TS 38.214).
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.
maxMIMO-Layers
Indicates the maximum MIMO layer to be used for PUSCH in all BWPs of the corresponding UL of this serving cell (see clause 5.4.2.1 of TS 38.212). If present, the network sets maxRank to the same value. The field maxMIMO-Layers refers to DCI format 0_1.
nrofHARQ-ProcessesForPUSCH
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 clause 6.1 of TS 38.214)
processingType2Enabled
Enables configuration of advanced processing time capability 2 for PUSCH (see 38.214 [19], clause 6.4).
rateMatching
Enables LBRM (Limited buffer rate-matching). When the field is absent the UE applies FBRM (Full buffer rate-matchingLBRM) (see clause 5.4.2 of TS 38.212).
xOverhead
If the field is absent, the UE applies the value 'xoh0' (see clause 5.1.3.2 of TS 38.214).
maxMIMO-LayersDCI-0-2
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 clause 5.4.2.1 of TS 38.212). If present, the network sets maxRankDCI-0-2 to the same value.
uplinkHARQ-mode
Used to set the HARQ mode per HARQ process ID, see TS 38.321. 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.
Up

 –  PUSCH-TimeDomainResourceAllocationListp. 951

The IE PUSCH-TimeDomainResourceAllocation is used to configure a time domain relation between PDCCH and PUSCH. PUSCH-TimeDomainResourceAllocationList contains one or more of such PUSCH-TimeDomainResourceAllocations. The network indicates in the UL grant which of the configured time domain allocations the UE shall apply for that UL grant. The UE determines the bit width of the DCI field based on the number of entries in the PUSCH-TimeDomainResourceAllocationList. Value 0 in the DCI field refers to the first element in this list, value 1 in the DCI field refers to the second element in this list, and so on.
PUSCH-TimeDomainResourceAllocation information element
PUSCH-TimeDomainResourceAllocationList field descriptions
extendedK2
Corresponds to L1 parameter 'K2' (see clause 6.1.2.1 of TS 38.214) configurable per PUSCH allocation. Only values {0..32} are applicable for PUSCH SCS of 120 kHz. When the field is absent for the first PUSCH if multiple PUSCH are configured per PDCCH, or when the field is absent and only one PUSCH is configured per PDCCH, the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, the value 3 when PUSCH SCS is 120 kHz, the value 11 when PUSCH SCS is 480 kHz, and the value 21 when PUSCH SCS is 960 kHz.
k2
Corresponds to L1 parameter 'K2' (see clause 6.1.2.1 of TS 38.214). When the field is absent the UE applies the value 1 when PUSCH SCS is 15/30 kHz; the value 2 when PUSCH SCS is 60 kHz, and the value 3 when PUSCH SCS is 120 kHz. k2 is absent/ignored if extendedK2 is present.
length
Indicates the length allocated for PUSCH for DCI format 0_1/0_2 (see clause 6.1.2.1 of TS 38.214).
mappingType
Mapping type (see clause 6.1.2.1 of TS 38.214).
numberOfRepetitions
Number of repetitions for DCI format 0_1/0_2 (see clause 6.1.2.1 of TS 38.214). When numberOfSlotsTBoMS-r17 is set to 2, 4 or 8 (i.e. TB processing over multi-slot (TBoMS) PUSCH is enabled), it indicates the number of repetitions of a single TBoMS.
numberOfRepetitionsExt
Number of repetitions for DCI format 0_1/0_2 if pusch-RepTypeIndicatorDCI-0-1/pusch-RepTypeIndicatorDCI-0-2 is not set to pusch-RepTypeB (see clause 6.1.2.1 of TS 38.214). If this field is present, the field numberOfRepeitions-r16 is ignored for PUSCH repetition Type A.
numberOfSlotsTBoMS
Number of slots allocated for TB processing over multi-slot PUSCH for DCI format 0_1/0_2. If a number of repetitions K is configured by numberOfRepetitions or numberOfRepetitionsExt, the network configures numberOfSlotsTBoMS (N) and K such that N*K ≤ 32 (see clause 6.1.2.1 of TS 38.214). The network does not configure the numberOfSlotsTBoMS-r17 simultaneously with the pusch-TimeDomainAllocationListForMultiPUSCH-r16.
puschAllocationList
The field puschAllocationList-r16 indicates one or multiple PUSCH continuous in time domain which share a common k2 (see clause 6.1.2.1 of TS 38.214). The field pusch-AllocationList-r17 configures one or multiple PUSCH that may be in consecutive or non-consecutive slots (see clause 6.1.2.1 of TS 38.214). The puschAllocationList-r16 only has one element in pusch-TimeDomainAllocationListDCI-0-1-r16 and in pusch-TimeDomainAllocationListDCI-0-2-r16.
startSymbol
Indicates the index of start symbol for PUSCH for DCI format 0_1/0_2 (see clause 6.1.2.1 of TS 38.214).
startSymbolAndLength
An index giving valid combinations of start symbol and length (jointly encoded) as start and length indicator (SLIV). The network configures the field so that the allocation does not cross the slot boundary. (see clause 6.1.2.1 of TS 38.214).
Conditional Presence Explanation
Format01-02In pusch-TimeDomainAllocationListForMultiPUSCH-r16, the field is absent. In pusch-TimeDomainAllocationListDCI-0-1 and in pusch-TimeDomainAllocationListDCI-0-2, the field is mandatory present.
Format01-02-For-TypeAIn pusch-TimeDomainAllocationListForMultiPUSCH-r16, the field is absent.
In pusch-TimeDomainAllocationListDCI-0-1, the field is optionally present if pusch-RepTypeIndicatorDCI-0-1 is not set to pusch-RepTypeB, Need R. It is absent otherwise, Need R.
In pusch-TimeDomainAllocationListDCI-0-2, the field is optionally present if pusch-RepTypeIndicatorDCI-0-2 is not set to pusch-RepTypeB, Need R. It is absent otherwise, Need R.
NotFormat01-02-Or-TypeAIn pusch-TimeDomainAllocationListForMultiPUSCH-r16, the field is mandatory present.
In pusch-TimeDomainAllocationListDCI-0-1, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-1 is not set to pusch-RepTypeB. It is absent otherwise, Need R.
In pusch-TimeDomainAllocationListDCI-0-2, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-2 is not sRepTypeB
In pusch-TimeDomainAllocationListForMultiPUSCH-r16, the field is absent.
In pusch-TimeDomainAllocationListDCI-0-1, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-1 is set to pusch-RepTypeB. It is absent otherwise, Need R.
In pusch-TimeDomainAllocationListDCI-0-2, the field is mandatory present if pusch-RepTypeIndicatorDCI-0-2 is set to pusch-RepTypeB. It is absent otherwise, Need R.et to pusch-RepTypeB. It is absent otherwise, Need R.
MultiPUSCHIn case size of puschAllocationList is higher than 1, the field extendedK2(n) corresponding to k2 of the n-th PUSCH, n>1, is mandatory present. Otherwise, it is optionally present, Need S.
Up

 –  PUSCH-TPC-CommandConfigp. 954

The IE PUSCH-TPC-CommandConfig is used to configure the UE for extracting TPC commands for PUSCH from a group-TPC messages on DCI.
PUSCH-TPC-CommandConfig information element
PUSCH-TPC-CommandConfig field descriptions
targetCell
The serving cell to which the acquired power control commands are applicable. If the value is absent, the UE applies the TPC commands to the serving cell on which the command has been received.
tpc-Index
An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload.
tpc-IndexSUL
An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload.
Conditional Presence Explanation
SUL-OnlyThe field is optionally present, Need R, if supplementaryUplink is configured within ServingCellConfig. It is absent otherwise.
SULThe field is optionally present, Need R, if supplementaryUplink is configured within ServingCellConfig. It is mandatory present otherwise.
Up

 –  Q-OffsetRangep. 955

The IE Q-OffsetRange is used to indicate a cell, beam or measurement object specific offset to be applied when evaluating candidates for cell re-selection or when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, dB-22 corresponds to -22 dB and so on.
Q-OffsetRange information element
Up

 –  Q-QualMinp. 955

The IE Q-QualMin is used to indicate for cell selection/ re-selection the required minimum received RSRQ level in the (NR) cell. Corresponds to parameter Qqualmin in TS 38.304. Actual value Qqualmin = field value [dB].
Q-QualMin information element
Up

 –  Q-RxLevMinp. 956

The IE Q-RxLevMin is used to indicate for cell selection/ re-selection the required minimum received RSRP level in the (NR) cell. Corresponds to parameter Qrxlevmin in TS 38.304. Actual value Qrxlevmin = field value * 2 [dBm].
Q-RxLevMin information element
Up

 –  QuantityConfigp. 956

The IE QuantityConfig specifies the measurement quantities and layer 3 filtering coefficients for NR and inter-RAT measurements.
QuantityConfig information element
QuantityConfigNR field descriptions
quantityConfigCell
Specifies L3 filter configurations for cell measurement results for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR).
quantityConfigRS-Index
Specifies L3 filter configurations for measurement results per RS index for the configurable RS Types (e.g. SS/PBCH block and CSI-RS) and the configurable measurement quantities (e.g. RSRP, RSRQ and SINR).
QuantityConfigRS field descriptions
csi-RS-FilterConfig
CSI-RS based L3 filter configurations:
Specifies L3 filter configurations for CSI-RSRP, CSI-RSRQ and CSI-SINR measurement results from the L1 filter(s), as defined in TS 38.215.
ssb-FilterConfig
SS Block based L3 filter configurations:
Specifies L3 filter configurations for SS-RSRP, SS-RSRQ and SS-SINR measurement results from the L1 filter(s), as defined in TS 38.215.
QuantityConfigUTRA-FDD field descriptions
filterCoefficientRSCP
Specifies L3 filter coefficient for FDD UTRAN CPICH_RSCP measuement results from L1 filter.
filterCoefficientEcN0
Specifies L3 filter coefficient for FDD UTRAN CPICH_EcN0 measuement results from L1 filter.
Up

 –  RACH-ConfigCommonp. 958

The IE RACH-ConfigCommon is used to specify the cell specific random-access parameters.
RACH-ConfigCommon information element
RACH-ConfigCommon field descriptions
featureCombinationPreamblesList
Specifies a series of preamble partitions each associated to a combination of features and 4-step RA. The network does not configure this list to have more than 16 entries.
messagePowerOffsetGroupB
Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to -infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see clause 5.1.2 of TS 38.321)
msg1-SubcarrierSpacing
Subcarrier spacing of PRACH (see clause 5.3.2 of TS 38.211).
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz
If absent, the UE applies the SCS as derived from the prach-ConfigurationIndex in RACH-ConfigGeneric (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211). The value also applies to contention free random access (RACH-ConfigDedicated), to SI-request and to contention-based beam failure recovery (CB-BFR). But it does not apply for contention free beam failure recovery (CF-BFR) (see BeamFailureRecoveryConfig).
msg3-transformPrecoder
Enables the transform precoder for Msg3 transmission according to clause 6.1.3 of TS 38.214. If the field is absent, the UE disables the transformer precoder (see clause 8.3 of TS 38.213).
numberOfRA-PreamblesGroupA
The number of CB preambles per SSB in group A. This determines implicitly the number of CB preambles per SSB available in group B. (see clause 5.1.1 of TS 38.321). The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB.
prach-RootSequenceIndex
PRACH root sequence index (see clause 6.3.3.1 of TS 38.211). The value range depends on whether L=839 or L=139 or L=571 or L=1151. The length of the root sequence corresponding with the index indicated in this IE should be consistent with the one indicated in prach-ConfigurationIndex in the RACH-ConfigDedicated (if configured). If prach-RootSequenceIndex-r16 is signalled, UE shall ignore the prach-RootSequenceIndex (without suffix).
For FR2-2, only the following values are applicable depending on the used subcarrier spacing:
120 kHz: L=139, L=571, and L=1151
480 kHz: L=139, and L=571
960 kHz: L=139
ra-ContentionResolutionTimer
The initial value for the contention resolution timer (see clause 5.1.5 of TS 38.321). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on.
ra-Msg3SizeGroupA
Transport Blocks size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see clause 5.1.2 of TS 38.321).
ra-Prioritization
Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see clause 5.1.1a of TS 38.321).
ra-PrioritizationForAI
Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 indicates that the field ra-Prioritization-r16 applies otherwise the field does not apply (see TS 23.501).
ra-PrioritizationForSlicing
Parameters which apply to configure prioritized CBRA 4-step random access type for slicing.
rach-ConfigGeneric
RACH parameters for both regular random access and beam failure recovery.
restrictedSetConfig
Configuration of an unrestricted set or one of two types of restricted sets, see clause 6.3.3.1 of TS 38.211.
rsrp-ThresholdSSB
UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213).
rsrp-ThresholdSSB-SUL
The UE selects SUL carrier to perform random access based on this threshold (see clause 5.1.1 of TS 38.321). The value applies to all the BWPs and all RACH configurations.
ssb-perRACH-OccasionAndCB-PreamblesPerSSB
The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEighth corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion). See TS 38.213.
totalNumberOfRA-Preambles
Total number of preambles used for contention based and contention free 4-step or 2-step random access in the RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g. for SI request). If the field is absent, all 64 preambles are available for RA. The setting should be consistent with the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, i.e. it should be a multiple of the number of SSBs per RACH occasion.
Conditional Presence Explanation
AdditionalRACHThe field is mandatory present if the RACH-ConfigCommon is included in an AdditionalRACH-Config. When included in initialUplinkBWP-RedCap to indicate other feature(s) than redcap, this field is mandatory present with at least two FeatureCombinationPreambles list entries: one list entry indicating only redcap and the other(s) indicating both redcap and one or multiple other feature(s) (e.g. smallData, nsag or msg3-Repetitions).
Otherwise, it is optional, Need R.
InitialBWP-OnlyThis field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise, the field is absent.
L139The field is mandatory present if prach-RootSequenceIndex L=139, otherwise the field is absent, Need S.
SULThe field is mandatory present in rach-ConfigCommon in initialUplinkBWP if supplementaryUplink is configured in ServingCellConfigCommonSIB or if supplementaryUplinkConfig is configured in ServingCellConfigCommon; otherwise, the field is absent. This field is not configured in additionalRACH-Config.
Up

 –  RACH-ConfigCommonTwoStepRAp. 961

The IE RACH-ConfigCommonTwoStepRA is used to specify cell specific 2-step random-access type parameters.
RACH-ConfigCommonTwoStepRA information element
RACH-ConfigCommonTwoStepRA field descriptions
featureCombinationPreamblesList
Specifies a series of preamble partitions each associated to a combination of features and 2-step RA. The network does not configure this list to have more than 16 entries.
groupB-ConfiguredTwoStepRA
Preamble grouping for 2-step random access type. If the field is absent then there is only one preamble group configured and only one msgA PUSCH configuration.
msgA-CB-PreamblesPerSSB-PerSharedRO
Number of contention-based preambles used for 2-step RA type from the non-CBRA 4-step type preambles associated with each SSB for RO shared with 4-step type RA. The number of preambles for 2-step RA type shall not exceed the number of preambles per SSB minus the number of contention-based preambles per SSB for 4-step type RA. The possible value range for this parameter needs to be aligned with value range for the configured SSBs per RACH occasion in ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. The field is only applicable for the case of shared ROs with 4-step type random access.
msgA-PRACH-RootSequenceIndex
PRACH root sequence index. If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e., not within AdditionalRACH-Config), the UE applies the value in field prach-RootSequenceIndex in RACH-ConfigCommon in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE applies the corresponding value of prach-RootSequenceIndex in RACH-ConfigCommon in the same AdditionalRACH-Config. When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access.
For FR2-2, only the following values are applicable depending on the used subcarrier spacing:
120 kHz: L=139, L=571, and L=1151
480 kHz: L=139, and L=571
960 kHz: L=139
msgA-RestrictedSetConfig
Configuration of an unrestricted set or one of two types of restricted sets for 2-step random access type preamble. If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config), the UE applies the value in field restrictedSetConfig in RACH-ConfigCommon in the configured BWP. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE applies the value of restrictedSetConfig in RACH-ConfigCommon in the same AdditionalRACH-Config. When both 2-step and 4-step type random access is configured, this field is only configured for the case of separate ROs between 2-step and 4-step type random access.
msgA-RSRP-Threshold
The UE selects 2-step random access type to perform random access based on this threshold (see clause 5.1.1 of TS 38.321). This field is only present if both 2-step and 4-step RA type are configured for the BWP.
msgA-RSRP-ThresholdSSB
UE may select the SS block and corresponding PRACH resource for path-loss estimation and (re)transmission based on SS blocks that satisfy the threshold (see TS 38.213).
msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB
The meaning of this field is twofold: the CHOICE conveys the information about the number of SSBs per RACH occasion. Value oneEight corresponds to one SSB associated with 8 RACH occasions, value oneFourth corresponds to one SSB associated with 4 RACH occasions, and so on. The ENUMERATED part indicates the number of Contention Based preambles per SSB. Value n4 corresponds to 4 Contention Based preambles per SSB, value n8 corresponds to 8 Contention Based preambles per SSB, and so on. The total number of CB preambles in a RACH occasion is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion). If the field is not configured in RACH-ConfigCommonTwoStepRA which is configured directly within a BWP (i.e. not within AdditionalRACH-Config) and both 2-step and 4-step are configured for the BWP, the UE applies the value in the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon. If the field is not configured in AdditionalRACH-Config and both 2-step and 4-step are configured in AdditionalRACH-Config, the UE applies the value in the field ssb-perRACH-OccasionAndCB-PreamblesPerSSB in RACH-ConfigCommon in the same AdditionalRACH-Config. The field is not present when RACH occasions are shared between 2-step and 4-step type random access in the BWP.
msgA-SSB-SharedRO-MaskIndex
Indicates the subset of 4-step type ROs shared with 2-step random access type for each SSB. This field is configured when there is more than one RO per SSB. If the field is absent, and 4-step and 2-step has shared ROs, then all ROs are shared.
msgA-SubcarrierSpacing
Subcarrier spacing of PRACH (see clause 5.3.2 of TS 38.211).
Only the following values are applicable depending on the used frequency:
FR1: 15 or 30 kHz
FR2-1: 60 or 120 kHz
FR2-2: 120, 480, or 960 kHz.
If the field is absent, the UE applies the SCS as derived from the msgA-PRACH-ConfigurationIndex in RACH-ConfigGenericTwoStepRA (see tables Table 6.3.3.1-1, Table 6.3.3.1-2, Table 6.3.3.2-2 and Table 6.3.3.2-3, TS 38.211) in case of 2-step only BWP, otherwise the UE applies the same SCS as Msg1 derived from RACH-ConfigCommon. The value also applies to contention free 2-step random access type (RACH-ConfigDedicated).
msgA-TotalNumberOfRA-Preambles
Indicates the total number of preambles used for contention-based and contention-free 2-step random access type when ROs for 2-step are not shared with 4-step. If the field is absent, and 2-step and 4-step does not have shared ROs, all 64 preambles are available for 2-step random access type.
msgA-TransMax
Max number of MsgA preamble transmissions performed before switching to 4-step random access (see clause 5.1.1 of TS 38.321). This field is only applicable when 2-step and 4-step RA type are configured and switching to 4-step type RA is supported. If the field is absent, switching from 2-step RA type to 4-step RA type is not allowed.
ra-ContentionResolutionTimer
The initial value for the contention resolution timer for fallback RAR in case no 4-step random access type is configured (see clause 5.1.5 of TS 38.321). Value sf8 corresponds to 8 subframes, value sf16 corresponds to 16 subframes, and so on. If both 2-step and 4-step random access type resources are configured on the BWP, then this field is absent. If the field is absent in RACH-ConfigCommonTwoStepRA in AdditionalRACH-Config, the UE shall apply the corresponding value in RACH-ConfigCommon in the same AdditionalRACH-Config.
ra-Prioritization
Parameters which apply for prioritized random access procedure on any UL BWP of SpCell for specific Access Identities (see clause 5.1.1a of TS 38.321).
ra-PrioritizationForAI
Indicates whether the field ra-Prioritization-r16 applies for Access Identities. The first/leftmost bit corresponds to Access Identity 1, the next bit corresponds to Access Identity 2. Value 1 for an Access Identity indicates that the field ra-Prioritization-r16 applies, otherwise the field does not apply.
ra-PrioritizationForSlicingTwoStep
Parameters which apply to configure prioritized CBRA 2-step random access type for slicing.
rach-ConfigGenericTwoStepRA
2-step random access type parameters for both regular random access and beam failure recovery.
GroupB-ConfiguredTwoStepRA field descriptions
messagePowerOffsetGroupB
Threshold for preamble selection. Value is in dB. Value minusinfinity corresponds to -infinity. Value dB0 corresponds to 0 dB, dB5 corresponds to 5 dB and so on. (see clause 5.1.1 of TS 38.321).
numberOfRA-PreamblesGroupA
The number of CB preambles per SSB in group A for idle/inactive or connected mode. The setting of the number of preambles for each group should be consistent with msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB or msgA-CB-PreamblesPerSSB-PerSharedRO if configured.
ra-MsgA-SizeGroupA
Transport block size threshold in bits below which the UE shall use a contention-based RA preamble of group A. (see clause 5.1.1 of TS 38.321).
Conditional Presence Explanation
2Step4StepThe field is mandatory present if both 2-step random access type and 4-step random access type are configured in the BWP, otherwise the field is not present.
The field is mandatory present in msgA-ConfigCommon field in AdditionalRACH-Config if both 2-step random access type and 4-step random access type are configured for the same feature combination in the BWP.
2StepOnlyL139The field is mandatory present if msgA-PRACH-RootSequenceIndex L=139 and no 4-step random access type is configured, otherwise the field is absent, Need S.
2StepOnlyThe field is mandatory present in msgA-ConfigCommon field in BWP-UplinkCommon if rach-ConfigCommon field is absent in this BWP-UplinkCommon, otherwise the field is optionally present in msgA-ConfigCommon field in BWP-UplinkCommon, Need S.
The field is mandatory present in msgA-ConfigCommon field in AdditionalRACH-Config if rach-ConfigCommon field is absent in this AdditionalRACH-Config, otherwise the field is optionally present in msgA-ConfigCommon field in AdditionalRACH-Config, Need S.
AdditionalRACHThe field is mandatory present if the msgA-ConfigCommon is included in an AdditionalRACH-Config. When included in initialUplinkBWP-RedCap to indicate other feature(s) than redcap, this field is mandatory present with at least two FeatureCombinationPreambles list entries: one list entry indicating only redcap and the other(s) indicating both redcap and one or multiple other feature(s) (e.g. smallData, nsag or msg3-Repetitions).
Otherwise, it is optional, Need R.
InitialBWP-OnlyThis field is optionally present, Need R, if this BWP is the initial BWP of SpCell. Otherwise, the field is absent.
SharedROThe field is mandatory present if the 2-step random access type occasions are shared with 4-step random access type, otherwise the field is not present.
Up

Up   Top   ToC