PUSCH-Config
PUSCH-Config is an RRC information element of 3GPP TS 38.331 (38331), the 5G NR Radio Resource Control (RRC) protocol.
Definition
The IE PUSCH-Config is used to configure the UE specific PUSCH parameters applicable to a particular BWP.
PUSCH-Config ::= SEQUENCE {
dataScramblingIdentityPUSCH INTEGER (0..1023) OPTIONAL, -- Need S
txConfig ENUMERATED {codebook, nonCodebook} OPTIONAL, -- Need S
dmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M
dmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M
pusch-PowerControl PUSCH-PowerControl OPTIONAL, -- Need M
frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S
frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1)
OPTIONAL, -- Need M
resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},
pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need M
pusch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need S
mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S
codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}
OPTIONAL, -- Cond codebookBased
maxRank INTEGER (1..4) OPTIONAL, -- Cond codebookBased
rbg-Size ENUMERATED { config2} OPTIONAL, -- Need S
uci-OnPUSCH SetupRelease { UCI-OnPUSCH} OPTIONAL, -- Need M
tp-pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need S
...,
[[
minimumSchedulingOffsetK2-r16 SetupRelease { MinSchedulingOffsetK2-Values-r16 } OPTIONAL, -- Need M
ul-AccessConfigListDCI-0-1-r16 SetupRelease { UL-AccessConfigListDCI-0-1-r16 } OPTIONAL, -- Need M
-- Start of the parameters for DCI format 0\_2 introduced in V16.1.0
harq-ProcessNumberSizeDCI-0-2-r16 INTEGER (0..4) OPTIONAL, -- Need R
dmrs-SequenceInitializationDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
numberOfBitsForRV-DCI-0-2-r16 INTEGER (0..2) OPTIONAL, -- Need R
antennaPortsFieldPresenceDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M
dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } OPTIONAL, -- Need M
frequencyHoppingDCI-0-2-r16 CHOICE {
pusch-RepTypeA ENUMERATED {intraSlot, interSlot},
pusch-RepTypeB ENUMERATED {interRepetition, interSlot}
} OPTIONAL, -- Need S
frequencyHoppingOffsetListsDCI-0-2-r16 SetupRelease { FrequencyHoppingOffsetListsDCI-0-2-r16} OPTIONAL, -- Need M
codebookSubsetDCI-0-2-r16 ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent}
OPTIONAL, -- Cond codebookBased
invalidSymbolPatternIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
maxRankDCI-0-2-r16 INTEGER (1..4) OPTIONAL, -- Cond codebookBased
mcs-TableDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
mcs-TableTransformPrecoderDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
priorityIndicatorDCI-0-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
pusch-RepTypeIndicatorDCI-0-2-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need R
resourceAllocationDCI-0-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}
OPTIONAL, -- Need M
resourceAllocationType1GranularityDCI-0-2-r16 ENUMERATED { n2,n4,n8,n16 } OPTIONAL, -- Need S
uci-OnPUSCH-ListDCI-0-2-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-2-r16} OPTIONAL, -- Need M
pusch-TimeDomainAllocationListDCI-0-2-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 }
OPTIONAL, -- Need M
-- End of the parameters for DCI format 0\_2 introduced in V16.1.0
-- Start of the parameters for DCI format 0\_1 introduced in V16.1.0
pusch-TimeDomainAllocationListDCI-0-1-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 }
OPTIONAL, -- Need M
invalidSymbolPatternIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
priorityIndicatorDCI-0-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
pusch-RepTypeIndicatorDCI-0-1-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} OPTIONAL, -- Need R
frequencyHoppingDCI-0-1-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB
uci-OnPUSCH-ListDCI-0-1-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } OPTIONAL, -- Need M
-- End of the parameters for DCI format 0\_1 introduced in V16.1.0
invalidSymbolPattern-r16 InvalidSymbolPattern-r16 OPTIONAL, -- Need S
pusch-PowerControl-v1610 SetupRelease {PUSCH-PowerControl-v1610} OPTIONAL, -- Need M
ul-FullPowerTransmission-r16 ENUMERATED {fullpower, fullpowerMode1, fullpowerMode2} OPTIONAL, -- Need R
pusch-TimeDomainAllocationListForMultiPUSCH-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 }
OPTIONAL, -- Need M
numberOfInvalidSymbolsForDL-UL-Switching-r16 INTEGER (1..4) OPTIONAL -- Cond RepTypeB2
]],
[[
ul-AccessConfigListDCI-0-2-r17 SetupRelease { UL-AccessConfigListDCI-0-2-r17 } OPTIONAL, -- Need M
betaOffsetsCrossPri0-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, -- Need M
betaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } OPTIONAL, -- Need M
betaOffsetsCrossPri0DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, -- Need M
betaOffsetsCrossPri1DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } OPTIONAL, -- Need M
mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} OPTIONAL, -- Cond SRSsets
secondTPCFieldDCI-0-1-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
secondTPCFieldDCI-0-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
sequenceOffsetForRV-r17 INTEGER (0..3) OPTIONAL, -- Need R
ul-AccessConfigListDCI-0-1-r17 SetupRelease { UL-AccessConfigListDCI-0-1-r17 } OPTIONAL, -- Need M
minimumSchedulingOffsetK2-r17 SetupRelease { MinSchedulingOffsetK2-Values-r17 } OPTIONAL, -- Need M
availableSlotCounting-r17 ENUMERATED { enabled } OPTIONAL, -- Need S
dmrs-BundlingPUSCH-Config-r17 SetupRelease { DMRS-BundlingPUSCH-Config-r17 } OPTIONAL, -- Need M
harq-ProcessNumberSizeDCI-0-2-v1700 INTEGER (5) OPTIONAL, -- Need R
harq-ProcessNumberSizeDCI-0-1-r17 INTEGER (5) OPTIONAL, -- Need R
mpe-ResourcePoolToAddModList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-Resource-r17 OPTIONAL, -- Need N
mpe-ResourcePoolToReleaseList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-ResourceId-r17 OPTIONAL -- Need N
]],
[[
maxRank-v1810 INTEGER (5..8) OPTIONAL, -- Need R
sTx-2Panel-r18 ENUMERATED {enabled} OPTIONAL, -- Need R
multipanelSchemeSDM-r18 SDM-Scheme-r18 OPTIONAL, -- Need R
multipanelSchemeSFN-r18 SFN-Scheme-r18 OPTIONAL, -- Need R
codebookTypeUL-r18 SetupRelease { CodebookTypeUL-r18 } OPTIONAL, -- Need M
applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL, -- Need R
dynamicTransformPrecoderFieldPresenceDCI-0-1-r18 ENUMERATED {enabled} OPTIONAL, -- Need R
dynamicTransformPrecoderFieldPresenceDCI-0-2-r18 ENUMERATED {enabled} OPTIONAL, -- Need R
pusch-ConfigDCI-0-3-r18 SetupRelease { PUSCH-ConfigDCI-0-3-r18 } OPTIONAL -- Need M
]],
[[
mg-CancellationDCI-0-1-r19 ENUMERATED {enabled} OPTIONAL, -- Need R
mg-CancellationDCI-0-2-r19 ENUMERATED {enabled} OPTIONAL, -- Need R
mg-CancellationDCI-0-3-r19 ENUMERATED {enabled} OPTIONAL, -- Need R
pusch-TimeDomainAllocationListForMultiPUSCH-DCI-0-3-r19 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 }
OPTIONAL, -- Need M
harq-ProcessNumberSizeDCI-0-1-Ext-r19 INTEGER (5) OPTIONAL, -- Need R
harq-ProcessNumberSizeDCI-0-2-Ext-r19 INTEGER (0..5) OPTIONAL, -- Need R
pusch-ConfigDCI-0-3-v1900 SetupRelease { PUSCH-ConfigDCI-0-3-v1900 } OPTIONAL, -- Need M
frequencyHoppingOffsetLists-SBFD-r19 SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)
OPTIONAL, -- Need M
frequencyHoppingOffsetListsDCI-0-2-SBFD-r19 SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1)
OPTIONAL, -- Need M
pusch-MutingResources-r19 PUSCH-MutingResources-r19 OPTIONAL -- Need R
]]
}Candidate change requests of v19.0.0
The CRs whose title or cover names this change, strong and likely matches only.
- CR 5400 r1 (strong): Introduction of Rel-19 Multi-carrier enhancements
- CR 5290 r3 (likely): Introduction on the SRS frequency hopping for non-RedCap UE in 38331 [Pos_SRSHop]
Fields (88)
| Field | Description |
|---|---|
| dataScramblingIdentityPUSCH INTEGER (0..1023) · OPTIONAL Need S since v15.1.0 | Identifier used to initialise data scrambling (c_init) for PUSCH. If the field is absent, the UE applies the physical cell ID. (see TS 38.211 [16], clause 6.3.1.1). |
| txConfig ENUMERATED {codebook, nonCodebook} · OPTIONAL Need S since v15.1.0 | Whether UE uses codebook based or non-codebook based transmission (see TS 38.214 [19], clause 6.1.1). If the field is absent, the UE transmits PUSCH on one antenna port, see TS 38.214 [19], clause 6.1.1. |
| dmrs-UplinkForPUSCH-MappingTypeA SetupRelease { DMRS-UplinkConfig } · OPTIONAL Need M since v15.1.0 | 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 formats 0_1 and 0_3, and the field dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
| dmrs-UplinkForPUSCH-MappingTypeB SetupRelease { DMRS-UplinkConfig } · OPTIONAL Need M since v15.1.0 | 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 formats 0_1 and 0_3, and the field dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
| pusch-PowerControl PUSCH-PowerControl · OPTIONAL Need M since v15.1.0 | Configures power control parameters PUSCH transmission. |
| frequencyHopping ENUMERATED {intraSlot, interSlot} · OPTIONAL Need S | 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 TS 38.214 [19], clause 6.3). The field frequencyHopping applies to DCI formats 0_0, 0_1 and 0_3 for 'pusch-RepTypeA'. |
| frequencyHoppingOffsetLists SEQUENCE (SIZE (1..4)) OF INTEGER (1.. maxNrofPhysicalResourceBlocks-1) · OPTIONAL Need M since v15.1.0 | Set of frequency hopping offsets used when frequency hopping is enabled for granted transmission (not msg3) and type 2 configured grant activation (see TS 38.214 [19], clause 6.3). The field frequencyHoppingOffsetLists applies to DCI formats 0_0, 0_1 and 0_3, and the field frequencyHoppingOffsetListsDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.3). |
| resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch} since v15.1.0 | Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 6.1.2). The field resourceAllocation applies to DCI format 0_1 and the field resourceAllocationDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2). |
| pusch-TimeDomainAllocationList SetupRelease { PUSCH-TimeDomainResourceAllocationList } · OPTIONAL Need M since v15.2.0 | List of time domain allocations for timing of UL assignment to UL data (see TS 38.214 [19], table 6.1.2.1.1-1). The field pusch-TimeDomainAllocationList applies to DCI format 0_0, or DCI formats 0_1 and 0_3 when the field pusch-TimeDomainAllocationListDCI-0-1 is not configured (see TS 38.214 [19], table 6.1.2.1.1-1 and tables 6.1.2.1.1-1A and 6.1.2.1.1-1C). 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-AggregationFactor ENUMERATED { n2, n4, n8 } · OPTIONAL Need S since v15.1.0 | Number of repetitions for data (see TS 38.214 [19], clause 6.1.2.1). If the field is absent the UE applies the value 1. |
| mcs-Table ENUMERATED {qam256, qam64LowSE} · OPTIONAL Need S | Indicates which MCS table the UE shall use for PUSCH without transform precoder (see TS 38.214 [19], clause 6.1.4.1). If the field is absent the UE applies the value 64QAM. The field mcs-Table applies to DCI formats 0_0, 0_1 and 0_3, and the field mcs-TableDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1). |
| mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} · OPTIONAL Need S | Indicates which MCS table the UE shall use for PUSCH with transform precoding (see TS 38.214 [19], clause 6.1.4.1) If the field is absent the UE applies the value 64QAM. The field mcs-TableTransformPrecoder applies to DCI formats 0_0, 0_1 and 0_3, and the field mcs-TableTransformPrecoderDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1). |
| transformPrecoder ENUMERATED {enabled, disabled} · OPTIONAL Need S | The UE specific selection of transformer precoder for PUSCH (see TS 38.214 [19], clause 6.1.3). 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 ). |
| codebookSubset ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent} · OPTIONAL Cond codebookBased since v15.1.0 | Subset of PMIs addressed by TPMI, where PMIs are those supported by UEs with maximum coherence capabilities (see TS 38.214 [19], clause 6.1.1.1). The field codebookSubset applies to DCI formats 0_1 and 0_3, and the field codebookSubsetDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). |
| maxRank INTEGER (1..4) · OPTIONAL Cond codebookBased since v15.1.0 | Subset of PMIs addressed by TRIs from 1 to ULmaxRank (see TS 38.214 [19], clause 6.1.1.1). The field maxRank applies to DCI formats 0_1 and 0_3, and the field maxRankDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). If network configures maxRank-v1810 UE ignores maxRank (without suffix). |
| rbg-Size ENUMERATED { config2} · OPTIONAL Need S | Selection between configuration 1 and configuration 2 for RBG size for PUSCH except PUSCH scheduled by DCI format 0_3. 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 TS 38.214 [19], clause 6.1.2.2.1). |
| uci-OnPUSCH SetupRelease { UCI-OnPUSCH} · OPTIONAL Need M since v15.1.0 | |
| tp-pi2BPSK ENUMERATED {enabled} · OPTIONAL Need S since v15.2.0 | Enables pi/2-BPSK modulation with transform precoding if the field is present and disables it otherwise. |
| minimumSchedulingOffsetK2-r16 SetupRelease { MinSchedulingOffsetK2-Values-r16 } · OPTIONAL Need M since v16.0.0 | List of minimum K2 values. Minimum K2 parameter denotes minimum applicable value(s) for the Time domain resource assignment table for PUSCH (see TS 38.214 [19], clause 6.1.2.1). |
| ul-AccessConfigListDCI-0-1-r16 SetupRelease { UL-AccessConfigListDCI-0-1-r16 } · OPTIONAL Need M since v16.2.0 | List of the combinations of cyclic prefix extension, channel access priority class (CAPC), and UL channel access type (see TS 38.212 [17], clause 7.3.1) 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 [17], 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 [17], Table 7.3.1.1.2-35A). |
| harq-ProcessNumberSizeDCI-0-2-r16 INTEGER (0..4) · OPTIONAL Need R since v16.2.0 | Configure the number of bits for the field "HARQ process number" in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). Only one of this field and harq-ProcessNumberSizeDCI-0-2-Ext is configured by network. |
| dmrs-SequenceInitializationDCI-0-2-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | 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 TS 38.212 [17], clause 7.3.1). |
| numberOfBitsForRV-DCI-0-2-r16 INTEGER (0..2) · OPTIONAL Need R since v16.2.0 | Configures the number of bits for "Redundancy version" in the DCI format 0_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 6.1.2.1). |
| antennaPortsFieldPresenceDCI-0-2-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | 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 TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 nor dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 is configured, this field is absent. |
| dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } · OPTIONAL Need M since v16.2.0 | 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 formats 0_1 and 0_3, and the field dmrs-UplinkForPUSCH-MappingTypeA-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
| dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2-r16 SetupRelease { DMRS-UplinkConfig } · OPTIONAL Need M since v16.2.0 | 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 formats 0_1 and 0_3, and the field dmrs-UplinkForPUSCH-MappingTypeB-DCI-0-2 applies to DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). |
| frequencyHoppingDCI-0-2-r16 CHOICE { · OPTIONAL Need S since v16.2.0 | 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 TS 38.214 [19], clause 6.3). |
| pusch-RepTypeA ENUMERATED {intraSlot, interSlot} since v16.2.0 | |
| pusch-RepTypeB ENUMERATED {interRepetition, interSlot} since v16.2.0 | |
| frequencyHoppingOffsetListsDCI-0-2-r16 SetupRelease { FrequencyHoppingOffsetListsDCI-0-2-r16} · OPTIONAL Need M since v16.2.0 | Set of frequency hopping offsets used when frequency hopping is enabled for granted transmission (not msg3) and type 2 configured grant activation (see TS 38.214 [19], clause 6.3). The field frequencyHoppingOffsetLists applies to DCI formats 0_0, 0_1 and 0_3, and the field frequencyHoppingOffsetListsDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.3). |
| codebookSubsetDCI-0-2-r16 ENUMERATED {fullyAndPartialAndNonCoherent, partialAndNonCoherent,nonCoherent} · OPTIONAL Cond codebookBased since v16.2.0 | Subset of PMIs addressed by TPMI, where PMIs are those supported by UEs with maximum coherence capabilities (see TS 38.214 [19], clause 6.1.1.1). The field codebookSubset applies to DCI formats 0_1 and 0_3, and the field codebookSubsetDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). |
| invalidSymbolPatternIndicatorDCI-0-2-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | 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 TS 38.214 [19] clause 6.1). If the field is absent, the UE behaviour is specified in TS 38.214 [19], clause 6.1.2.1. |
| maxRankDCI-0-2-r16 INTEGER (1..4) · OPTIONAL Cond codebookBased since v16.2.0 | Subset of PMIs addressed by TRIs from 1 to ULmaxRank (see TS 38.214 [19], clause 6.1.1.1). The field maxRank applies to DCI formats 0_1 and 0_3, and the field maxRankDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). If network configures maxRank-v1810 UE ignores maxRank (without suffix). |
| mcs-TableDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} · OPTIONAL Need S since v16.2.0 | |
| mcs-TableTransformPrecoderDCI-0-2-r16 ENUMERATED {qam256, qam64LowSE} · OPTIONAL Need S since v16.2.0 | Indicates which MCS table the UE shall use for PUSCH with transform precoding (see TS 38.214 [19], clause 6.1.4.1) If the field is absent the UE applies the value 64QAM. The field mcs-TableTransformPrecoder applies to DCI formats 0_0, 0_1 and 0_3, and the field mcs-TableTransformPrecoderDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.4.1). |
| priorityIndicatorDCI-0-2-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | 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 TS 38.212 [17] clause 7.3.1 and TS 38.213 [13] clause 9). |
| pusch-RepTypeIndicatorDCI-0-2-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} · OPTIONAL Need R since v16.2.0 | 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 TS 38.214 [19], clause 6.1.2.1). |
| resourceAllocationDCI-0-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch} · OPTIONAL Need M since v16.2.0 | Configuration of resource allocation type 0 and resource allocation type 1 for non-fallback DCI (see TS 38.214 [19], clause 6.1.2). The field resourceAllocation applies to DCI format 0_1 and the field resourceAllocationDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2). |
| resourceAllocationType1GranularityDCI-0-2-r16 ENUMERATED { n2,n4,n8,n16 } · OPTIONAL Need S since v16.2.0 | 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 TS 38.214 [19], clause 6.1.2.2.2). |
| uci-OnPUSCH-ListDCI-0-2-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-2-r16} · OPTIONAL Need M since v16.2.0 | 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 TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3). |
| pusch-TimeDomainAllocationListDCI-0-2-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } · OPTIONAL Need M since v16.2.0 | Configuration of the time domain resource allocation (TDRA) table for DCI format 0_2 (see TS 38.214 [19], clause 6.1.2, table 6.1.2.1.1-1B). |
| pusch-TimeDomainAllocationListDCI-0-1-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } · OPTIONAL Need M since v16.2.0 | Configuration of the time domain resource allocation (TDRA) table for DCI formats 0_1 and 0_3 (see TS 38.214 [19], clause 6.1, tables 6.1.2.1.1-1A and 6.1.2.1.1-1C). |
| invalidSymbolPatternIndicatorDCI-0-1-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | 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 TS 38.214 [19] clause 6.1). If the field is absent, the UE behaviour is specified in TS 38.214 [19], clause 6.1.2.1. |
| priorityIndicatorDCI-0-1-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | 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 TS 38.212 [17] clause 7.3.1 and TS 38.213 [13] clause 9). |
| pusch-RepTypeIndicatorDCI-0-1-r16 ENUMERATED { pusch-RepTypeA, pusch-RepTypeB} · OPTIONAL Need R since v16.2.0 | 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 TS 38.214 [19], clause 6.1.2.1). |
| frequencyHoppingDCI-0-1-r16 ENUMERATED {interRepetition, interSlot} · OPTIONAL Cond RepTypeB since v16.2.0 | 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 TS 38.214 [19], clause 6.1). |
| uci-OnPUSCH-ListDCI-0-1-r16 SetupRelease { UCI-OnPUSCH-ListDCI-0-1-r16 } · OPTIONAL Need M since v16.2.0 | 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 TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9.3). |
| invalidSymbolPattern-r16 InvalidSymbolPattern-r16 · OPTIONAL Need S since v16.0.0 | 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 TS 38.214 [19] clause 6.1). |
| pusch-PowerControl-v1610 SetupRelease {PUSCH-PowerControl-v1610} · OPTIONAL Need M since v16.1.0 | Configures power control parameters PUSCH transmission. |
| ul-FullPowerTransmission-r16 ENUMERATED {fullpower, fullpowerMode1, fullpowerMode2} · OPTIONAL Need R since v16.0.0 | Configures the UE with UL full power transmission mode as specified in TS 38.213 [13]. |
| pusch-TimeDomainAllocationListForMultiPUSCH-r16 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } · OPTIONAL Need M since v16.1.0 | Configuration of the time domain resource allocation (TDRA) table for multiple PUSCH (see TS 38.214 [19], clause 6.1.2). 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 if extendedK2 is not configured. 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 . For a cell within a cell set configured to be schedulable by a DCI format 0_3, the network does not configure pusch-TimeDomainAllocationListForMultiPUSCH-DCI-0-3 simultaneously with the numberOfSlotsTBoMS-r17 and/or pusch-AggregationFactor . |
| numberOfInvalidSymbolsForDL-UL-Switching-r16 INTEGER (1..4) · OPTIONAL Cond RepTypeB2 since v16.1.0 | 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 TS 38.214 [19], clause 6.1). |
| ul-AccessConfigListDCI-0-2-r17 SetupRelease { UL-AccessConfigListDCI-0-2-r17 } · OPTIONAL Need M since v17.0.0 | List of the combinations of cyclic prefix extension, channel access priority class (CAPC), and UL channel access type (see TS 38.212 [17], clause 7.3.1) 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 [17], 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 [17], Table 7.3.1.1.2-35A). |
| betaOffsetsCrossPri0-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } · OPTIONAL Need M since v17.0.0 | Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK on dynamically scheduled PUSCH with different priorities, see TS 38.213 [13], clause 9.3. 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. |
| betaOffsetsCrossPri1-r17 SetupRelease { BetaOffsetsCrossPriSel-r17 } · OPTIONAL Need M since v17.0.0 | Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK on dynamically scheduled PUSCH with different priorities, see TS 38.213 [13], clause 9.3. 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. |
| betaOffsetsCrossPri0DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } · OPTIONAL Need M since v17.0.0 | Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK on dynamically scheduled PUSCH with different priorities, see TS 38.213 [13], clause 9.3. 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. |
| betaOffsetsCrossPri1DCI-0-2-r17 SetupRelease { BetaOffsetsCrossPriSelDCI-0-2-r17 } · OPTIONAL Need M since v17.0.0 | Selection between and configuration of dynamic and semi-static beta-offset for multiplexing HARQ-ACK on dynamically scheduled PUSCH with different priorities, see TS 38.213 [13], clause 9.3. 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. |
| mappingPattern-r17 ENUMERATED {cyclicMapping, sequentialMapping} · OPTIONAL Cond SRSsets since v17.0.0 | 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. |
| secondTPCFieldDCI-0-1-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | 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, |
| secondTPCFieldDCI-0-2-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | 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-r17 INTEGER (0..3) · OPTIONAL Need R since v17.0.0 | 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'. |
| ul-AccessConfigListDCI-0-1-r17 SetupRelease { UL-AccessConfigListDCI-0-1-r17 } · OPTIONAL Need M since v17.0.0 | List of the combinations of cyclic prefix extension, channel access priority class (CAPC), and UL channel access type (see TS 38.212 [17], clause 7.3.1) 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 [17], 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 [17], Table 7.3.1.1.2-35A). |
| minimumSchedulingOffsetK2-r17 SetupRelease { MinSchedulingOffsetK2-Values-r17 } · OPTIONAL Need M since v17.0.0 | List of minimum K2 values. Minimum K2 parameter denotes minimum applicable value(s) for the Time domain resource assignment table for PUSCH (see TS 38.214 [19], clause 6.1.2.1). |
| availableSlotCounting-r17 ENUMERATED { enabled } · OPTIONAL Need S since v17.0.0 | 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. |
| dmrs-BundlingPUSCH-Config-r17 SetupRelease { DMRS-BundlingPUSCH-Config-r17 } · OPTIONAL Need M since v17.0.0 | Configure the parameters for DMRS bundling for PUSCH (see TS 38.214 [19], clause 6.1.7). In this release, this is not applicable to FR2-2. |
| harq-ProcessNumberSizeDCI-0-2-v1700 INTEGER (5) · OPTIONAL Need R since v17.0.0 | Configure the number of bits for the field "HARQ process number" in DCI format 0_2 (see TS 38.212 [17], clause 7.3.1). Only one of this field and harq-ProcessNumberSizeDCI-0-2-Ext is configured by network. |
| harq-ProcessNumberSizeDCI-0-1-r17 INTEGER (5) · OPTIONAL Need R since v17.0.0 | |
| mpe-ResourcePoolToAddModList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-Resource-r17 · OPTIONAL Need N since v17.1.0 | 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. |
| mpe-ResourcePoolToReleaseList-r17 SEQUENCE (SIZE(1..maxMPE-Resources-r17)) OF MPE-ResourceId-r17 · OPTIONAL Need N since v17.1.0 | |
| maxRank-v1810 INTEGER (5..8) · OPTIONAL Need R since v18.1.0 | Subset of PMIs addressed by TRIs from 1 to ULmaxRank (see TS 38.214 [19], clause 6.1.1.1). The field maxRank applies to DCI formats 0_1 and 0_3, and the field maxRankDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.1.1). If network configures maxRank-v1810 UE ignores maxRank (without suffix). |
| sTx-2Panel-r18 ENUMERATED {enabled} · OPTIONAL Need R since v18.0.0 | Parameter to enable PUSCH+PUSCH multiple panel simultaneous uplink transmission, as specified in TS 38.214 [19], clause 6.1. |
| multipanelSchemeSDM-r18 SDM-Scheme-r18 · OPTIONAL Need R since v18.1.0 | Configures UE with a multiple panel simultaneous uplink transmission SDM scheme for PUSCH, as specified in TS 38.214 [19], clause 6.1. Network does not configure multipanelSchemeSDM with multipanelSchemeSFN . When this parameter is configured, two SRS resource sets with usage for codebook or noncodebook are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 . |
| multipanelSchemeSFN-r18 SFN-Scheme-r18 · OPTIONAL Need R since v18.1.0 | Configures UE with a multiple panel simultaneous uplink transmission SFN scheme for PUSCH, as specified in TS 38.214 [19], clause 6.1. Network does not configure multipanelSchemeSFN with multipanelSchemeSDM . When this parameter is configured, two SRS resource sets with usage for codebook or noncodebook are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 . |
| codebookTypeUL-r18 SetupRelease { CodebookTypeUL-r18 } · OPTIONAL Need M since v18.0.0 | Configures a codebook and the corresponding number of antenna port groups for codebook-based transmission of PUSCH with 8 antenna ports, see TS 38.211 [16], tables 6.3.1.5-9 to 6.3.1.5-47, and table 6.3.1.5-8 respectively). The values ng1n4n1 and ng1n2n2 correspond to codebooks with one antenna port group (Ng=1), while ng2, ng4 , and ng8 correspond to codebooks with Ng=2, 4, and 8 antenna port groups, respectively. |
| applyIndicatedTCI-State-r18 ENUMERATED {first, second} · OPTIONAL Need R since v18.0.0 | This field indicates, for a PUSCH transmission, if UE applies the first or the second "indicated" UL only TCI or joint TCI as specified in TS 38.214 [19], clause 6.1. |
| dynamicTransformPrecoderFieldPresenceDCI-0-1-r18 ENUMERATED {enabled} · OPTIONAL Need R since v18.0.0 | Configure the presence of "Dynamic Transform Precoder" field in DCI format 0_1. When the field is configured, then the "Dynamic Transform Precoder" field is present in DCI format 0_1. Otherwise, the field size is set to 0 for DCI format 0_1 (See TS 38.212 [17]). The network ensures dynamicTransformPrecoderFieldPresenceDCI-0-1-r18 and twoPHRMode-r17 cannot be configured at the same time for a UE. |
| dynamicTransformPrecoderFieldPresenceDCI-0-2-r18 ENUMERATED {enabled} · OPTIONAL Need R since v18.0.0 | Configure the presence of "Dynamic Transform Precoder" field in DCI format 0_2. When the field is configured, then the "Dynamic Transform Precoder" field is present in DCI format 0_2. Otherwise, the field size is set to 0 for DCI format 0_2 (See TS 38.212 [17]). The network ensures dynamicTransformPrecoderFieldPresenceDCI-0-2-r18 and twoPHRMode -r17 cannot be configured at the same time for a UE. |
| pusch-ConfigDCI-0-3-r18 SetupRelease { PUSCH-ConfigDCI-0-3-r18 } · OPTIONAL Need M since v18.0.0 | |
| mg-CancellationDCI-0-1-r19 ENUMERATED {enabled} · OPTIONAL Need R since v19.0.0 | Indicates the presence of Measurement gap cancellation in DCI format 0_1 as specified in TS 38.212 [17]. |
| mg-CancellationDCI-0-2-r19 ENUMERATED {enabled} · OPTIONAL Need R since v19.0.0 | Indicates the presence of Measurement gap cancellation in DCI format 0_2 as specified in TS 38.212 [17]. |
| mg-CancellationDCI-0-3-r19 ENUMERATED {enabled} · OPTIONAL Need R since v19.0.0 | Indicates the presence of Measurement gap cancellation in DCI format 0_3 as specified in TS 38.212 [17]. The field could only be configured if the co-scheduled cells are intra-band and have the same sub-carrier spacing. |
| pusch-TimeDomainAllocationListForMultiPUSCH-DCI-0-3-r19 SetupRelease { PUSCH-TimeDomainResourceAllocationList-r16 } · OPTIONAL Need M since v19.0.0 | Configuration of the time domain resource allocation (TDRA) table for multiple PUSCH (see TS 38.214 [19], clause 6.1.2). 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 if extendedK2 is not configured. 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 . For a cell within a cell set configured to be schedulable by a DCI format 0_3, the network does not configure pusch-TimeDomainAllocationListForMultiPUSCH-DCI-0-3 simultaneously with the numberOfSlotsTBoMS-r17 and/or pusch-AggregationFactor . |
| harq-ProcessNumberSizeDCI-0-1-Ext-r19 INTEGER (5) · OPTIONAL Need R since v19.0.0 | Configure the number of bits for the field "HARQ process number" in DCI format 0_1 in TN (see TS 38.212 [17], clause 7.3.1). This field can only be configured when the maximum number of layers configured for PUSCH is no more than 4. |
| harq-ProcessNumberSizeDCI-0-2-Ext-r19 INTEGER (0..5) · OPTIONAL Need R since v19.0.0 | Configure the number of bits for the field "HARQ process number" in DCI format 0_2 for TN (see TS 38.212 [17], clause 7.3.1). This field can only be configured when the maximum number of layers configured for PUSCH is no more than 4. Only one of this field and harq-ProcessNumberSizeDCI-0-2 is configured by network. |
| pusch-ConfigDCI-0-3-v1900 SetupRelease { PUSCH-ConfigDCI-0-3-v1900 } · OPTIONAL Need M since v19.0.0 | |
| frequencyHoppingOffsetLists-SBFD-r19 SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1) · OPTIONAL Need M since v19.0.0 | Configure the frequency hopping offset lists for PUSCH scheduled by DCI and Type 2 configured grant PUSCH in SBFD symbols, and the field frequencyHoppingOffsetListsDCI-0-2-SBFD applies to DCI format 0_2 (see TS 38.214 [19], clause 6.3.3). |
| frequencyHoppingOffsetListsDCI-0-2-SBFD-r19 SEQUENCE (SIZE (1..4)) OF INTEGER (1..maxNrofPhysicalResourceBlocks-1) · OPTIONAL Need M since v19.0.0 | Configure the frequency hopping offset lists for PUSCH scheduled by DCI and Type 2 configured grant PUSCH in SBFD symbols, and the field frequencyHoppingOffsetListsDCI-0-2-SBFD applies to DCI format 0_2 (see TS 38.214 [19], clause 6.3.3). |
| pusch-MutingResources-r19 PUSCH-MutingResources-r19 · OPTIONAL Need R since v19.0.0 | Configures the time location and frequency location of UL muting resources for dynamic grant PUSCH transmission and Type 2 configured grant PUSCH transmission. |
Used by (2)
Uses (29)
- BetaOffsetsCrossPriSel-r17
- BetaOffsetsCrossPriSelDCI-0-2-r17
- CodebookTypeUL-r18
- DMRS-BundlingPUSCH-Config-r17
- DMRS-UplinkConfig
- FrequencyHoppingOffsetListsDCI-0-2-r16
- InvalidSymbolPattern-r16
- MPE-Resource-r17
- MPE-ResourceId-r17
- MinSchedulingOffsetK2-Values-r16
- MinSchedulingOffsetK2-Values-r17
- PUSCH-ConfigDCI-0-3-r18
- PUSCH-ConfigDCI-0-3-v1900
- PUSCH-MutingResources-r19
- PUSCH-PowerControl
- PUSCH-PowerControl-v1610
- PUSCH-TimeDomainResourceAllocationList
- PUSCH-TimeDomainResourceAllocationList-r16
- SDM-Scheme-r18
- SFN-Scheme-r18
- SetupRelease
- UCI-OnPUSCH
- UCI-OnPUSCH-ListDCI-0-1-r16
- UCI-OnPUSCH-ListDCI-0-2-r16
- UL-AccessConfigListDCI-0-1-r16
- UL-AccessConfigListDCI-0-1-r17
- UL-AccessConfigListDCI-0-2-r17
- maxMPE-Resources-r17
- maxNrofPhysicalResourceBlocks-1