Content for  TS 38.331  Word version:  17.4.0

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)

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).

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.

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).

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).

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)

The maximum number of UL PTRS ports for CP-OFDM (see clause 6.2.3.1 of TS 38.214).

UL PTRS power boosting factor per PTRS port (see clause 6.1 of TS 38.214, table 6.2.3.1.3).

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).

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.

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)

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)

Configuration of UL PTRS without transform precoder (with CP-OFDM).

Configuration of UL PTRS with transform precoder (DFT-S-OFDM).

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.

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).

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.

This field is used for PUCCH formats 3 and 4 according to clause 6.4.1.3.3.1 of TS 38.211.

Parameters that are common for all PUCCH resources of format 0.

Parameters that are common for all PUCCH resources of format 1.

Parameters that are common for all PUCCH resources of format 2.

Parameters that are common for all PUCCH resources of format 3.

Parameters that are common for all PUCCH resources of format 4.

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).

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).

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.

Configures power control parameters PUCCH transmission. This field is not configured if unifiedTCI-StateType is configured for the serving cell.

Lists for adding and releasing groups of PUCCH resources that can be updated simultaneously for spatial relations with a MAC CE.

Lists for adding and releasing PUCCH resource sets (see clause 9.2 of TS 38.213).

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.

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.

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.

Lists of spatial relation configurations between a reference RS and PUCCH to be released by the UE.

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.

The field is used to configure the list of PUCCH resources per HARQ ACK codebook for MBS multicast.

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.

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).

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.

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.

If the field is present, the UE enables inter-slot frequency hopping when PUCCH Format 0, 1, 3 or 4 is repeated over multiple slots. For long PUCCH over multiple slots, the intra and inter slot frequency hopping cannot be enabled at the same time for a UE. The field is not applicable for format 2. See clause 9.2.6 of TS 38.213.

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.

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.

Number of slots with the same PUCCH. When the field is absent the UE applies the value n1. The field is not applicable for format 2. See clause 9.2.6 of TS 38.213.

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.

Indicates the RB set where PUCCH resource is allocated.

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.

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.

This is the only interlace of interlaced PUCCH Format 0 and 1 and the first interlace for interlaced PUCCH Format 2 and 3.

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.

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.

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.

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.

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.

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.

Identifier of the PUCCH resource.

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).

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.

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.

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.

Cell-specific scrambling ID for group hopping and sequence hopping if enabled, see clause 6.3.2.2 of TS 38.211.

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.

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.

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).

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).

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).

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).

P0 value for PUCCH with 1dB step size.

deltaF for PUCCH format 0 with 1dB step size (see clause 7.2 of TS 38.213).

deltaF for PUCCH format 1 with 1dB step size (see clause 7.2 of TS 38.213).

deltaF for PUCCH format 2 with 1dB step size (see clause 7.2 of TS 38.213).

deltaF for PUCCH format 3 with 1dB step size (see clause 7.2 of TS 38.213).

deltaF for PUCCH format 4 with 1dB step size (see clause 7.2 of TS 38.213).

A set with dedicated P0 values for PUCCH, i.e., {P01, P02,... } (see clause 7.2 of TS 38.213).

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.

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).

When pucch-PathLossReferenceRS-Id-v1610 is configured, the UE shall ignore pucch-PathLossReferenceRS-Id (without suffix).

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).

If the field is absent, the UE applies the ServCellId of the serving cell in which this PUCCH-SpatialRelationInfo is configured

An index determining the position of the first bit of TPC command (applicable to the SpCell) inside the DCI format 2-2 payload.

An index determining the position of the first bit of TPC command (applicable to the PUCCH SCell) inside the DCI format 2-2 payload.

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.

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.

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.

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.

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).

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).

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.

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 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 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).

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'.

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).

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).

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).

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).

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).

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.

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.

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).

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).

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).

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).

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.

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).

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)

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).

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.

Configures power control parameters PUSCH transmission. This field is not configured if unifiedTCI-StateType is configured for the serving cell.

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).

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.

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).

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).

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 16 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.

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).

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).

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).

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,

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'.

Enables pi/2-BPSK modulation with transform precoding if the field is present and disables it otherwise.

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).

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.

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).

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).

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.

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).

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).

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).

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).

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).

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).

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.

Power offset between msg3 and RACH preamble transmission. Actual value = field value * 2 [dB] (see clause 7.1 of TS 38.213).

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.

List of time domain allocations for timing of UL assignment to UL data (see TS 38.214, table 6.1.2.1.1-1).

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 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.

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).

Configure the index of a p0-PUSCH-Set (see clause 7 of TS 38.213 and clause 7.3.1 of TS 38.212).

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).

This field is not used in the specification. If received it shall be ignored by the UE.

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.

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).

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 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).

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).

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).

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).

Lists of reference signals for PUSCH path loss estimation to be released by the UE.

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).

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.

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).

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).

The ID of a P0-PUSCH-AlphaSet as configured in p0-AlphaSets in PUSCH-PowerControl.

The index of the closed power control loop associated with this SRI-PUSCH-PowerControl.

The ID of PUSCH-PathlossReferenceRS as configured in the pathlossReferenceRSToAddModList in PUSCH-PowerControl.

The ID of this SRI-PUSCH-PowerControl configuration. It is used as the codepoint (payload) in the SRI DCI field.

Maximum number of code-block-groups (CBGs) per TB (see clause 9.1 of TS 38.213).

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 is 480 or 960 kHz.

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.

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)

Enables configuration of advanced processing time capability 2 for PUSCH (see 38.214 [19], clause 6.4).

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).

If the field is absent, the UE applies the value 'xoh0' (see clause 5.1.3.2 of TS 38.214).

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.

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.

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.

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.

Indicates the length allocated for PUSCH for DCI format 0_1/0_2 (see clause 6.1.2.1 of TS 38.214).

Mapping type (see clause 6.1.2.1 of TS 38.214).

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.

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.

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 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.

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).

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).

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.

An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload.

An index determining the position of the first bit of TPC command inside the DCI format 2-2 payload.

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).

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).

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.

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.

Specifies L3 filter coefficient for FDD UTRAN CPICH_RSCP measuement results from L1 filter.

Specifies L3 filter coefficient for FDD UTRAN CPICH_EcN0 measuement results from L1 filter.

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.

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)

Subcarrier spacing of PRACH (see clause 5.3.2 of TS 38.211). Only the following values are applicable depending on the used frequency: 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).

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).

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 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:

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.

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).

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).

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).

Parameters which apply to configure prioritized CBRA 4-step random access type for slicing.

RACH parameters for both regular random access and beam failure recovery.

Configuration of an unrestricted set or one of two types of restricted sets, see clause 6.3.3.1 of TS 38.211.

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).

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.

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.

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.

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.

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.

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.

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:

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.

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.

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).

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.

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.

Subcarrier spacing of PRACH (see clause 5.3.2 of TS 38.211). Only the following values are applicable depending on the used frequency: 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).

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.

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.

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.

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).

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.

Parameters which apply to configure prioritized CBRA 2-step random access type for slicing.

2-step random access type parameters for both regular random access and beam failure recovery.

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).

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.

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).

The ID of a CSI-RS resource defined in the measurement object associated with this serving cell.

RA occasions that the UE shall use when performing CF-RA upon selecting the candidate beam identified by this CSI-RS. The network ensures that the RA occasion indexes provided herein are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is sequentially numbered, first, in increasing order of frequency resource indexes for frequency multiplexed PRACH occasions; second, in increasing order of time resource indexes for time multiplexed PRACH occasions within a PRACH slot and Third, in increasing order of indexes for PRACH slots.

The RA preamble index to use in the RA occasions associated with this CSI-RS.

RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommon in the first active UL BWP.

Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321. The mask is valid for all SSB resources signalled in ssb-ResourceList.

Configuration of contention free random access occasions for CFRA. The UE shall ignore preambleReceivedTargetPower, preambleTransMax, powerRampingStep, ra-ResponseWindow signaled within this field and use the corresponding values provided in RACH-ConfigCommon.

Number of SSBs per RACH occasion.

Total number of preambles used for contention free random access in the RACH resources defined in CFRA, excluding preambles used for other purposes (e.g. for SI request). If the field is absent but the field occasions is present, the UE may assume all the 64 preambles are for RA. The setting should be consistent with the setting of ssb-perRACH-Occasion, if present, i.e. it should be a multiple of the number of SSBs per RACH occasion.

Identifies the index of the PUSCH resource used for MSGA CFRA. The PUSCH resource index indicates a valid PUSCH occasion (as specified in clause 8.1A of TS 38.213) and the associated DMRS resources corresponding to a PRACH slot. The PUSCH resource indexes are sequentially numbered and are mapped to valid PUSCH occasions corresponding to a PRACH slot which are ordered, first, in increasing order of frequency resource indexes for frequency multiplexed PUSCH occasions; second, in increasing order of DMRS resource indexes within a PUSCH occasion, where a DMRS resource index DMRS_id is determined first in an ascending order of a DMRS port index and then in an ascending order of a DMRS sequence index, third in increasing order of time resource indexes for time multiplexed PUSCH occasions within a PUSCH slot and fourth, in increasing order of indexes for PUSCH slots. For the case of contention free 2-step random access type, if this field is absent, the UE shall use the value 0.

The preamble index that the UE shall use when performing CF-RA upon selecting the candidate beams identified by this SSB.

The ID of an SSB transmitted by this serving cell.

PUSCH resource configuration(s) for msgA CFRA.

Max number of MsgA preamble transmissions performed before switching to 4-step type 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 in cfra-TwoStep, switching from 2-step RA type to 4-step RA type is not allowed.

RA occasions for contention free random access. If the field is absent, the UE uses the RA occasions configured in RACH-ConfigCommonTwoStepRA in the first active UL BWP.

Explicitly signalled PRACH Mask Index for RA Resource selection in TS 38.321. The mask is valid for all SSB resources signalled in ssb-ResourceList.

Configuration of contention free random access occasions for CFRA 2-step random access type.

Number of SSBs per RACH occasion for 2-step random access type.

Parameters for contention free random access to a given target cell. If this field and cfra-TwoStep are absent, the UE performs contention based random access.

Parameters for contention free 2-step random access type to a given target cell. Network ensures that cfra and cfra-TwoStep are not configured at the same time. If this field and cfra are absent, the UE performs contention based random access. This field may only be present if msgA-ConfigCommon is configured on the BWP.

Parameters which apply for prioritized random access procedure to a given target cell (see clause 5.1.1 of TS 38.321).

Parameters which apply for prioritized 2-step random access type procedure to a given target cell (see clause 5.1.1 of TS 38.321).

The number of PRACH transmission occasions FDMed in one time instance. (see clause 6.3.3.2 of TS 38.211).

Offset of lowest PRACH transmission occasion in frequency domain with respective to PRB 0. The value is configured so that the corresponding RACH resource is entirely within the bandwidth of the UL BWP. (see clause 6.3.3.2 of TS 38.211).

Power ramping steps for PRACH (see clause 5.1.3 of TS 38.321).

Frame offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see clause 6.3.3.2 of TS 38.211).

PRACH configuration index. For prach-ConfigurationIndex configured under beamFailureRecoveryConfig, the prach-ConfigurationIndex can only correspond to the short preamble format, (see clause 6.3.3.2 of TS 38.211). If the field prach-ConfigurationIndex-v1610 is present, the UE shall ignore the value provided in prach-ConfigurationIndex (without suffix).

Scaling factor to extend the periodicity of the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. Value scf1 corresponds to scaling factor of 1 and so on. (see clause 6.3.3.2 of TS 38.211).

Subframe/Slot offset for ROs defined in the baseline configuration indicated by prach-ConfigurationIndex and is used only by the IAB-MT. (see clause 6.3.3.2 of TS 38.211).

The target power level at the network receiver side (see clause 7.4 of TS 38.213, clauses 5.1.2, 5.1.3 of TS 38.321). Only multiples of 2 dBm may be chosen (e.g. -202, -200, -198, ...).

Max number of RA preamble transmission performed before declaring a failure (see clauses 5.1.4, 5.1.5 of TS 38.321).

Msg2 (RAR) window length in number of slots. The network configures a value lower than or equal to 10 ms when Msg2 is transmitted in licensed spectrum and a value lower than or equal to 40 ms when Msg2 is transmitted with shared spectrum channel access (see clause 5.1.4 of TS 38.321). UE ignores the field if included in SCellConfig. If ra-ResponseWindow-v1610 or ra-ResponseWindow-v1700 is signalled, UE shall ignore the ra-ResponseWindow (without suffix). The field ra-ResponseWindow-v1700 is applicable to SCS 480 kHz and SCS 960 kHz.

N-CS configuration, see Table 6.3.3.1-5 in TS 38.211.