PDSCH-Config
PDSCH-Config is an RRC information element of 3GPP TS 38.331 (38331), the 5G NR Radio Resource Control (RRC) protocol.
Definition
The PDSCH-Config IE is used to configure the UE specific PDSCH parameters. If this IE is used for MBS CFR, the following fields shall be absent: tci-StatesToAddModList , tci-StatesToReleaseList , zp-CSI-RS-ResourceToAddModList , minimumSchedulingOffsetK0 , antennaPortsFieldPresenceDCI-1-2 , aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2 , aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2 , dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 , dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 , dmrs-SequenceInitializationDCI-1-2 , harq-ProcessNumberSizeDCI-1-2 , mcs-TableDCI-1-2 , numberOfBitsForRV-DCI-1-2 , pdsch-AggregationFactor , pdsch-TimeDomainAllocationListDCI-1-2 , prb-BundlingTypeDCI-1-2 , priorityIndicatorDCI-1-2 , rateMatchPatternGroup1DCI-1-2 , rateMatchPatternGroup2DCI-1-2 , resourceAllocationType1GranularityDCI-1-2 , vrb-ToPRB-InterleaverDCI-1-2 , referenceOfSLIVDCI-1-2 , resourceAllocationDCI-1-2 , dataScramblingIdentityPDSCH2-r16 , repetitionSchemeConfig , pdsch-ConfigDCI-1-3 , pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 .
PDSCH-Config ::= SEQUENCE {
dataScramblingIdentityPDSCH INTEGER (0..1023) OPTIONAL, -- Need S
dmrs-DownlinkForPDSCH-MappingTypeA SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M
dmrs-DownlinkForPDSCH-MappingTypeB SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M
tci-StatesToAddModList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State OPTIONAL, -- Need N
tci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId OPTIONAL, -- Need N
vrb-ToPRB-Interleaver ENUMERATED {n2, n4} OPTIONAL, -- Need S
resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},
pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList } OPTIONAL, -- Need M
pdsch-AggregationFactor ENUMERATED { n2, n4, n8 } OPTIONAL, -- Need S
rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N
rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N
rateMatchPatternGroup1 RateMatchPatternGroup OPTIONAL, -- Need R
rateMatchPatternGroup2 RateMatchPatternGroup OPTIONAL, -- Need R
rbg-Size ENUMERATED {config1, config2},
mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
maxNrofCodeWordsScheduledByDCI ENUMERATED {n1, n2} OPTIONAL, -- Need R
prb-BundlingType CHOICE {
staticBundling SEQUENCE {
bundleSize ENUMERATED { n4, wideband } OPTIONAL -- Need S
},
dynamicBundling SEQUENCE {
bundleSizeSet1 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, -- Need S
bundleSizeSet2 ENUMERATED { n4, wideband } OPTIONAL -- Need S
}
},
zp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-Resource
OPTIONAL, -- Need N
zp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-ResourceId
OPTIONAL, -- Need N
aperiodic-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet
OPTIONAL, -- Need N
aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId
OPTIONAL, -- Need N
sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet
OPTIONAL, -- Need N
sp-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId
OPTIONAL, -- Need N
p-ZP-CSI-RS-ResourceSet SetupRelease { ZP-CSI-RS-ResourceSet }
OPTIONAL, -- Need M
...,
[[
maxMIMO-Layers-r16 SetupRelease { MaxMIMO-LayersDL-r16 } OPTIONAL, -- Need M
minimumSchedulingOffsetK0-r16 SetupRelease { MinSchedulingOffsetK0-Values-r16 } OPTIONAL, -- Need M
-- Start of the parameters for DCI format 1\_2 introduced in V16.1.0
antennaPortsFieldPresenceDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet
OPTIONAL, -- Need N
aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId
OPTIONAL, -- Need N
dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M
dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } OPTIONAL, -- Need M
dmrs-SequenceInitializationDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
harq-ProcessNumberSizeDCI-1-2-r16 INTEGER (0..4) OPTIONAL, -- Need R
mcs-TableDCI-1-2-r16 ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S
numberOfBitsForRV-DCI-1-2-r16 INTEGER (0..2) OPTIONAL, -- Need R
pdsch-TimeDomainAllocationListDCI-1-2-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 }
OPTIONAL, -- Need M
prb-BundlingTypeDCI-1-2-r16 CHOICE {
staticBundling-r16 SEQUENCE {
bundleSize-r16 ENUMERATED { n4, wideband } OPTIONAL -- Need S
},
dynamicBundling-r16 SEQUENCE {
bundleSizeSet1-r16 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } OPTIONAL, -- Need S
bundleSizeSet2-r16 ENUMERATED { n4, wideband } OPTIONAL -- Need S
}
} OPTIONAL, -- Need R
priorityIndicatorDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
rateMatchPatternGroup1DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, -- Need R
rateMatchPatternGroup2DCI-1-2-r16 RateMatchPatternGroup OPTIONAL, -- Need R
resourceAllocationType1GranularityDCI-1-2-r16 ENUMERATED {n2,n4,n8,n16} OPTIONAL, -- Need S
vrb-ToPRB-InterleaverDCI-1-2-r16 ENUMERATED {n2, n4} OPTIONAL, -- Need S
referenceOfSLIVDCI-1-2-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
resourceAllocationDCI-1-2-r16 ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch}
OPTIONAL, -- Need M
-- End of the parameters for DCI format 1\_2 introduced in V16.1.0
priorityIndicatorDCI-1-1-r16 ENUMERATED {enabled} OPTIONAL, -- Need S
dataScramblingIdentityPDSCH2-r16 INTEGER (0..1023) OPTIONAL, -- Need R
pdsch-TimeDomainAllocationList-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } OPTIONAL, -- Need M
repetitionSchemeConfig-r16 SetupRelease { RepetitionSchemeConfig-r16} OPTIONAL -- Need M
]],
[[
repetitionSchemeConfig-v1630 SetupRelease { RepetitionSchemeConfig-v1630} OPTIONAL -- Need M
]],
[[
pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
pdsch-HARQ-ACK-EnhType3DCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
pdsch-HARQ-ACK-EnhType3DCI-Field-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
pdsch-HARQ-ACK-RetxDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
pucch-sSCellDynDCI-1-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R
dl-OrJointTCI-StateList-r17 CHOICE {
explicitlist SEQUENCE {
dl-OrJointTCI-StateToAddModList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-State
OPTIONAL, -- Need N
dl-OrJointTCI-StateToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-StateId
OPTIONAL -- Need N
},
unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17
} OPTIONAL, -- Need R
beamAppTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336, spare2,
spare1} OPTIONAL, -- Need R
dummy SetupRelease { Dummy-TDRA-List } OPTIONAL, -- Need M
dmrs-FD-OCC-DisabledForRank1-PDSCH-r17 ENUMERATED {true} OPTIONAL, -- Need R
minimumSchedulingOffsetK0-r17 SetupRelease { MinSchedulingOffsetK0-Values-r17 } OPTIONAL, -- Need M
harq-ProcessNumberSizeDCI-1-2-v1700 INTEGER (0..5) OPTIONAL, -- Need R
harq-ProcessNumberSizeDCI-1-1-r17 INTEGER (5) OPTIONAL, -- Need R
mcs-Table-r17 ENUMERATED {qam1024} OPTIONAL, -- Need R
mcs-TableDCI-1-2-r17 ENUMERATED {qam1024} OPTIONAL, -- Need R
xOverheadMulticast-r17 ENUMERATED {xOh6, xOh12, xOh18} OPTIONAL, -- Need S
priorityIndicatorDCI-4-2-r17 ENUMERATED {enabled} OPTIONAL, -- Need S
sizeDCI-4-2-r17 INTEGER (20..maxDCI-4-2-Size-r17) OPTIONAL -- Need R
]],
[[
pdsch-TimeDomainAllocationListForMultiPDSCH-r17 SetupRelease { MultiPDSCH-TDRA-List-r17 } OPTIONAL -- Need M
]],
[[
advancedReceiver-MU-MIMO-r18 SetupRelease { AdvancedReceiver-MU-MIMO-r18 } OPTIONAL, -- Need M
pdsch-ConfigDCI-1-3-r18 SetupRelease { PDSCH-ConfigDCI-1-3-r18 } OPTIONAL -- Need M
]],
[[
pdsch-ConfigDCI-1-3-v1860 SetupRelease { PDSCH-ConfigDCI-1-3-v1860 } OPTIONAL -- Need M
]],
[[
mg-CancellationDCI-1-1-r19 ENUMERATED {enabled} OPTIONAL, -- Need R
mg-CancellationDCI-1-2-r19 ENUMERATED {enabled} OPTIONAL, -- Need R
mg-CancellationDCI-1-3-r19 ENUMERATED {enabled} OPTIONAL, -- Need R
pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3-r19 SetupRelease { MultiPDSCH-TDRA-List-r17 } OPTIONAL, -- Need M
harq-ProcessNumberSizeDCI-1-1-Ext-r19 INTEGER (5) OPTIONAL, -- Need R
harq-ProcessNumberSizeDCI-1-2-Ext-r19 INTEGER (0..5) OPTIONAL, -- Need R
pdsch-ConfigDCI-1-3-v1900 SetupRelease { PDSCH-ConfigDCI-1-3-v1900 } OPTIONAL -- Need M
]]
}
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
Fields (91)
| Field | Description |
|---|---|
| dataScramblingIdentityPDSCH INTEGER (0..1023) · OPTIONAL Need S since v15.1.0 | Identifier(s) used to initialize data scrambling (c_init) for PDSCH as specified in TS 38.211 [16], clause 7.3.1.1. The dataScramblingIdentityPDSCH2 is configured if coresetPoolIndex is configured with 1 for at least one CORESET in the same BWP. |
| dmrs-DownlinkForPDSCH-MappingTypeA SetupRelease { DMRS-DownlinkConfig } · OPTIONAL Need M since v15.1.0 | DMRS configuration for PDSCH transmissions using PDSCH mapping type A (chosen dynamically via PDSCH-TimeDomainResourceAllocation ). Only the fields dmrs-Type , dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeA applies to DCI formats 1_1 and 1_3, and the field dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). |
| dmrs-DownlinkForPDSCH-MappingTypeB SetupRelease { DMRS-DownlinkConfig } · OPTIONAL Need M since v15.1.0 | DMRS configuration for PDSCH transmissions using PDSCH mapping type B (chosen dynamically via PDSCH-TimeDomainResourceAllocation ). Only the fields dmrs-Type , dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeB applies to DCI formats 1_1 and 1_3, and the field dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). |
| tci-StatesToAddModList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-State · OPTIONAL Need N since v15.1.0 | A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports (see TS 38.214 [19], clause 5.1.5). If unifiedTCI-StateType is configured for the serving cell, no element in this list is configured. |
| tci-StatesToReleaseList SEQUENCE (SIZE(1..maxNrofTCI-States)) OF TCI-StateId · OPTIONAL Need N since v15.1.0 | |
| vrb-ToPRB-Interleaver ENUMERATED {n2, n4} · OPTIONAL Need S since v15.1.0 | Interleaving unit configurable between 2 and 4 PRBs (see TS 38.211 [16], clause 7.3.1.6). When the field is absent, the UE performs non-interleaved VRB-to-PRB mapping. |
| 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 5.1.2.2). The field resourceAllocation applies to DCI format 1_1, and the field resourceAllocationDCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.2.2). |
| pdsch-TimeDomainAllocationList SetupRelease { PDSCH-TimeDomainResourceAllocationList } · OPTIONAL Need M since v15.2.0 | List of time-domain configurations for timing of DL assignment to DL data. The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0, DCI format 1_1 and DCI format 1_3 (see table 5.1.2.1.1-1 in TS 38.214 [19]), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214 [19]). The field pdsch-TimeDomainAllocationListForMultiPDSCH applies to DCI format 1_1. The field pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 applies to DCI format 1_3. The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config . |
| pdsch-AggregationFactor ENUMERATED { n2, n4, n8 } · OPTIONAL Need S since v15.1.0 | Number of repetitions for data (see TS 38.214 [19], clause 5.1.2.1). When the field is absent in PDSCH-Config which is not used for MBS CFR, the UE applies the value 1. |
| rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern · OPTIONAL Need N since v15.1.0 | Resources patterns which the UE should rate match PDSCH around. The UE rate matches around the union of all resources indicated in the rate match patterns (see TS 38.214 [19], clause 5.1.4.1). If a RateMatchPattern with the same RateMatchPatternId is configured in both MBS CFR and its associated BWP, the entire RateMatchPattern configuration, including the set of RBs/REs indicated by the patterns for the rate matching around, shall be the same and they are counted as a single rate match pattern in the total configured rate match patterns as defined in TS 38.214 [19]. |
| rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId · OPTIONAL Need N since v15.1.0 | |
| rateMatchPatternGroup1 RateMatchPatternGroup · OPTIONAL Need R since v15.1.0 | The IDs of a first group of RateMatchPatterns defined in PDSCH-Config -> rateMatchPatternToAddModList (BWP level) or in ServingCellConfig -> rateMatchPatternToAddModLis t (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup1 applies to DCI formats 1_1 and 1_3, and the field rateMatchPatternGroup1DCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1). |
| rateMatchPatternGroup2 RateMatchPatternGroup · OPTIONAL Need R since v15.1.0 | The IDs of a second group of RateMatchPatterns defined in PDSCH-Config -> rateMatchPatternToAddModList (BWP level) or in ServingCellConfig -> rateMatchPatternToAddModLis t (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup2 applies to DCI formats 1_1 and 1_3, and the field rateMatchPatternGroup2DCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1). |
| rbg-Size ENUMERATED {config1, config2} | Selection between config 1 and config 2 for RBG size for PDSCH except PDSCH scheduled by DCI format 1_3. The UE ignores this field if resourceAllocation is set to resourceAllocationType1 (see TS 38.214 [19], clause 5.1.2.2.1). |
| mcs-Table ENUMERATED {qam256, qam64LowSE} · OPTIONAL Need S | Indicates which MCS table the UE shall use for PDSCH for DCI formats 1_0, 1_1 and 1_3 (see TS 38.214 [19], clause 5.1.3.1). If all fields are absent the UE applies the value 64QAM. If the field mcs-Table-r17 is present for DCI formats 1_1 and 1_3, the network does not configure the field mcs-Table (without suffix). For an (e)RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH. |
| maxNrofCodeWordsScheduledByDCI ENUMERATED {n1, n2} · OPTIONAL Need R | Maximum number of code words that a single DCI may schedule. This changes the number of MCS/RV/NDI bits in the DCI message from 1 to 2. |
| prb-BundlingType CHOICE { since v15.1.0 | Indicates the PRB bundle type and bundle size(s) (see TS 38.214 [19], clause 5.1.2.3). If dynamic is chosen, the actual bundleSizeSet1 or bundleSizeSet2 to use is indicated via DCI. Constraints on bundleSize(Set) setting depending on vrb-ToPRB-Interleaver and rbg-Size settings are described in TS 38.214 [19], clause 5.1.2.3. If a bundleSize(Set) value is absent, the UE applies the value n2 . The field prb-BundlingType applies to DCI formats 1_1 and 1_3, and the field prb-BundlingTypeDCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.3). |
| staticBundling SEQUENCE { since v15.2.0 | |
| bundleSize ENUMERATED { n4, wideband } · OPTIONAL Need S since v15.2.0 | |
| dynamicBundling SEQUENCE { since v15.2.0 | |
| bundleSizeSet1 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } · OPTIONAL Need S since v15.2.0 | |
| bundleSizeSet2 ENUMERATED { n4, wideband } · OPTIONAL Need S since v15.2.0 | |
| zp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-Resource · OPTIONAL Need N since v15.1.0 | A list of Zero-Power (ZP) CSI-RS resources used for PDSCH rate-matching. Each resource in this list may be referred to from only one type of resource set, i.e., aperiodic, semi-persistent or periodic (see TS 38.214 [19]). |
| zp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-Resources)) OF ZP-CSI-RS-ResourceId · OPTIONAL Need N since v15.1.0 | |
| aperiodic-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet · OPTIONAL Need N since v15.1.0 | AddMod/Release lists for configuring aperiodically triggered zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList ). The network configures the UE with at most 3 aperiodic ZP-CSI-RS-ResourceSets and it uses only the ZP-CSI-RS-ResourceSetId 1 to 3. The network triggers a set by indicating its ZP-CSI-RS-ResourceSetId in the DCI payload. The DCI codepoint '01' triggers the resource set with ZP-CSI-RS-ResourceSetId 1, the DCI codepoint '10' triggers the resource set with ZP-CSI-RS-ResourceSetId 2 , and the DCI codepoint '11' triggers the resource set with ZP-CSI-RS-ResourceSetId 3 (see TS 38.214 [19], clause 5.1.4.2). The field aperiodic-ZP-CSI-RS-ResourceSetsToAddModList applies to DCI format 1_1 and the field aperiodic-ZP-CSI-RS-ResourceSetsToAddModListDCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.2 and TS 38.212 [17] clause 7.3.1). |
| aperiodic-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId · OPTIONAL Need N since v15.1.0 | |
| sp-ZP-CSI-RS-ResourceSetsToAddModList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet · OPTIONAL Need N since v15.1.0 | AddMod/Release lists for configuring semi-persistent zero-power CSI-RS resource sets. Each set contains a ZP-CSI-RS-ResourceSetId and the IDs of one or more ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList ) (see TS 38.214 [19], clause 5.1.4.2). |
| sp-ZP-CSI-RS-ResourceSetsToReleaseList SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId · OPTIONAL Need N since v15.1.0 | |
| p-ZP-CSI-RS-ResourceSet SetupRelease { ZP-CSI-RS-ResourceSet } · OPTIONAL Need M since v15.2.0 | A set of periodically occurring ZP-CSI-RS-Resources (the actual resources are defined in the zp-CSI-RS-ResourceToAddModList). The network uses the ZP-CSI-RS-ResourceSetId=0 for this set. If p-ZP-CSI-RS-ResourceSet is configured in both PDSCH-Config for MBS CFR and PDSCH-Config for the assoicated BWP, it is subject to UE capability whether the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config for MBS CFR can be different from the p-ZP-CSI-RS-ResourceSet configured in PDSCH-Config for the assoicated BWP. |
| maxMIMO-Layers-r16 SetupRelease { MaxMIMO-LayersDL-r16 } · OPTIONAL Need M since v16.0.0 | Indicates the maximum number of MIMO layers to be used for PDSCH in this DL BWP. If not configured, the UE uses the maxMIMO-Layers configuration in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs, when the UE operates in this BWP. The value of maxMIMO-Layers for a DL BWP shall be smaller than or equal to the value of maxMIMO-Layers configured in IE PDSCH-ServingCellConfig of the serving cell to which this BWP belongs. For MBS multicast, indicates the maximum number of MIMO layers to be used for group-common PDSCH of MBS multicast in this CFR. If not configured for CFR, the UE applies value 1. The value of maxMIMO-Layers for a CFR shall be smaller than or equal to the value of maxMIMO-Layers configured in PDSCH-ServingCellConfig IE of the serving cell to which this CFR belongs. |
| minimumSchedulingOffsetK0-r16 SetupRelease { MinSchedulingOffsetK0-Values-r16 } · OPTIONAL Need M since v16.0.0 | List of minimum K0 values. Minimum K0 parameter denotes minimum applicable value(s) for the TDRA table for PDSCH and for A-CSI RS triggering Offset(s) (see TS 38.214 [19], clause 5.3.1). |
| antennaPortsFieldPresenceDCI-1-2-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | Configure the presence of "Antenna ports" field in DCI format 1_2. When the field is configured, then the "Antenna ports" field is present in DCI format 1_2. Otherwise, the field size is set to 0 for DCI format 1_2 (See TS 38.212 [17], clause 7.3.1.1.3). If neither dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 nor dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 is configured, this field is absent. |
| aperiodicZP-CSI-RS-ResourceSetsToAddModListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSet · OPTIONAL Need N since v16.2.0 | |
| aperiodicZP-CSI-RS-ResourceSetsToReleaseListDCI-1-2-r16 SEQUENCE (SIZE (1..maxNrofZP-CSI-RS-ResourceSets)) OF ZP-CSI-RS-ResourceSetId · OPTIONAL Need N since v16.2.0 | |
| dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } · OPTIONAL Need M since v16.2.0 | DMRS configuration for PDSCH transmissions using PDSCH mapping type A (chosen dynamically via PDSCH-TimeDomainResourceAllocation ). Only the fields dmrs-Type , dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeA applies to DCI formats 1_1 and 1_3, and the field dmrs-DownlinkForPDSCH-MappingTypeA-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). |
| dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2-r16 SetupRelease { DMRS-DownlinkConfig } · OPTIONAL Need M since v16.2.0 | DMRS configuration for PDSCH transmissions using PDSCH mapping type B (chosen dynamically via PDSCH-TimeDomainResourceAllocation ). Only the fields dmrs-Type , dmrs-AdditionalPosition and maxLength may be set differently for mapping type A and B. The field dmrs-DownlinkForPDSCH-MappingTypeB applies to DCI formats 1_1 and 1_3, and the field dmrs-DownlinkForPDSCH-MappingTypeB-DCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). |
| dmrs-SequenceInitializationDCI-1-2-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | |
| harq-ProcessNumberSizeDCI-1-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 1_2 (see TS 38.212 [17], clause 7.3.1). Only one of this field and harq-ProcessNumberSizeDCI-1-2-Ext is configured by network. |
| mcs-TableDCI-1-2-r16 ENUMERATED {qam256, qam64LowSE} · OPTIONAL Need S since v16.2.0 | Indicates which MCS table the UE shall use for PDSCH for DCI format 1_2 (see TS 38.214 [19], clause 5.1.3.1). If all fields are absent the UE applies the value 64QAM. If the field mcs-TableDCI-1-2-r17 is present, the network does not configure the field mcs-TableDCI-1-2-r16 . For an (e)RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH. |
| numberOfBitsForRV-DCI-1-2-r16 INTEGER (0..2) · OPTIONAL Need R since v16.2.0 | Configures the number of bits for "Redundancy version" in the DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.1). |
| pdsch-TimeDomainAllocationListDCI-1-2-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } · OPTIONAL Need M since v16.2.0 | List of time-domain configurations for timing of DL assignment to DL data. The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0, DCI format 1_1 and DCI format 1_3 (see table 5.1.2.1.1-1 in TS 38.214 [19]), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214 [19]). The field pdsch-TimeDomainAllocationListForMultiPDSCH applies to DCI format 1_1. The field pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 applies to DCI format 1_3. The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config . |
| prb-BundlingTypeDCI-1-2-r16 CHOICE { · OPTIONAL Need R since v16.2.0 | Indicates the PRB bundle type and bundle size(s) (see TS 38.214 [19], clause 5.1.2.3). If dynamic is chosen, the actual bundleSizeSet1 or bundleSizeSet2 to use is indicated via DCI. Constraints on bundleSize(Set) setting depending on vrb-ToPRB-Interleaver and rbg-Size settings are described in TS 38.214 [19], clause 5.1.2.3. If a bundleSize(Set) value is absent, the UE applies the value n2 . The field prb-BundlingType applies to DCI formats 1_1 and 1_3, and the field prb-BundlingTypeDCI-1-2 applies to DCI format 1_2 (see TS 38.212 [17], clause 7.3.1 and TS 38.214 [19], clause 5.1.2.3). |
| staticBundling-r16 SEQUENCE { since v16.2.0 | |
| bundleSize-r16 ENUMERATED { n4, wideband } · OPTIONAL Need S since v16.2.0 | |
| dynamicBundling-r16 SEQUENCE { since v16.2.0 | |
| bundleSizeSet1-r16 ENUMERATED { n4, wideband, n2-wideband, n4-wideband } · OPTIONAL Need S since v16.2.0 | |
| bundleSizeSet2-r16 ENUMERATED { n4, wideband } · OPTIONAL Need S since v16.2.0 | |
| priorityIndicatorDCI-1-2-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | Configure the presence of "priority indicator" in DCI format 1_1/1_2/4_2. When the field is absent in the IE, then 0 bit for "priority indicator" in DCI format 1_1/1_2/4_2. The field priorityIndicatorDCI-1-1 applies to DCI format 1_1, the field priorityIndicatorDCI-1-2 applies to DCI format 1_2 and the field priorityIndicatorDCI-4-2 applies to DCI format 4_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9). |
| rateMatchPatternGroup1DCI-1-2-r16 RateMatchPatternGroup · OPTIONAL Need R since v16.2.0 | The IDs of a first group of RateMatchPatterns defined in PDSCH-Config -> rateMatchPatternToAddModList (BWP level) or in ServingCellConfig -> rateMatchPatternToAddModLis t (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup1 applies to DCI formats 1_1 and 1_3, and the field rateMatchPatternGroup1DCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1). |
| rateMatchPatternGroup2DCI-1-2-r16 RateMatchPatternGroup · OPTIONAL Need R since v16.2.0 | The IDs of a second group of RateMatchPatterns defined in PDSCH-Config -> rateMatchPatternToAddModList (BWP level) or in ServingCellConfig -> rateMatchPatternToAddModLis t (cell level). These patterns can be activated dynamically by DCI (see TS 38.214 [19], clause 5.1.4.1). The field rateMatchPatternGroup2 applies to DCI formats 1_1 and 1_3, and the field rateMatchPatternGroup2DCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.4.1). |
| resourceAllocationType1GranularityDCI-1-2-r16 ENUMERATED {n2,n4,n8,n16} · OPTIONAL Need S since v16.2.0 | Configure the scheduling granularity applicable for both the starting point and length indication for resource allocation type 1 in DCI format 1_2. If this field is absent, the granularity is 1 PRB (see TS 38.214 [19], clause 5.1.2.2.2). |
| vrb-ToPRB-InterleaverDCI-1-2-r16 ENUMERATED {n2, n4} · OPTIONAL Need S since v16.2.0 | Interleaving unit configurable between 2 and 4 PRBs (see TS 38.211 [16], clause 7.3.1.6). When the field is absent, the UE performs non-interleaved VRB-to-PRB mapping. |
| referenceOfSLIVDCI-1-2-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | Enable using the starting symbol of the PDCCH monitoring occasion in which the DL assignment is detected as the reference of the SLIV for DCI format 1_2. When the RRC parameter enables the utilization of the new reference, the new reference is applied for TDRA entries with K0=0. For other entries (if any) in the same TDRA table, the reference is slot boundary as in Rel-15. PDSCH mapping type A is not supported with the new reference. The new reference of SLIV is not configured for a serving cell configured to be scheduled by cross-carrier scheduling on a scheduling cell with different numerology (see TS 38.212 [17] clause 7.3.1 and TS 38.214 [19] clause 5.1.2.1). |
| resourceAllocationDCI-1-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 5.1.2.2). The field resourceAllocation applies to DCI format 1_1, and the field resourceAllocationDCI-1-2 applies to DCI format 1_2 (see TS 38.214 [19], clause 5.1.2.2). |
| priorityIndicatorDCI-1-1-r16 ENUMERATED {enabled} · OPTIONAL Need S since v16.2.0 | Configure the presence of "priority indicator" in DCI format 1_1/1_2/4_2. When the field is absent in the IE, then 0 bit for "priority indicator" in DCI format 1_1/1_2/4_2. The field priorityIndicatorDCI-1-1 applies to DCI format 1_1, the field priorityIndicatorDCI-1-2 applies to DCI format 1_2 and the field priorityIndicatorDCI-4-2 applies to DCI format 4_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9). |
| dataScramblingIdentityPDSCH2-r16 INTEGER (0..1023) · OPTIONAL Need R since v16.0.0 | Identifier(s) used to initialize data scrambling (c_init) for PDSCH as specified in TS 38.211 [16], clause 7.3.1.1. The dataScramblingIdentityPDSCH2 is configured if coresetPoolIndex is configured with 1 for at least one CORESET in the same BWP. |
| pdsch-TimeDomainAllocationList-r16 SetupRelease { PDSCH-TimeDomainResourceAllocationList-r16 } · OPTIONAL Need M since v16.1.0 | List of time-domain configurations for timing of DL assignment to DL data. The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0, DCI format 1_1 and DCI format 1_3 (see table 5.1.2.1.1-1 in TS 38.214 [19]), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214 [19]). The field pdsch-TimeDomainAllocationListForMultiPDSCH applies to DCI format 1_1. The field pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 applies to DCI format 1_3. The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config . |
| repetitionSchemeConfig-r16 SetupRelease { RepetitionSchemeConfig-r16} · OPTIONAL Need M since v16.0.0 | Configure the UE with repetition schemes. The network does not configure repetitionSchemeConfig-r16 and repetitionSchemeConfig-v1630 simultaneously to setup in the same PDSCH-Config . The network does not configure this parameter and sfnSchemePDSCH in MIMOParam-r17 simultaneously in the same serving cell. |
| repetitionSchemeConfig-v1630 SetupRelease { RepetitionSchemeConfig-v1630} · OPTIONAL Need M since v16.3.0 | Configure the UE with repetition schemes. The network does not configure repetitionSchemeConfig-r16 and repetitionSchemeConfig-v1630 simultaneously to setup in the same PDSCH-Config . The network does not configure this parameter and sfnSchemePDSCH in MIMOParam-r17 simultaneously in the same serving cell. |
| pdsch-HARQ-ACK-OneShotFeedbackDCI-1-2-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | When configured, DCI format 1_2 can request the UE to report A/N for all HARQ processes and all component carriers configured in the PUCCH group (see TS 38.212 [17], clause 7.3.1). |
| pdsch-HARQ-ACK-EnhType3DCI-1-2-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | When configured, enhanced Type 3 HARQ-ACK codebook triggering by DCI format 1_2 is enabled. |
| pdsch-HARQ-ACK-EnhType3DCI-Field-1-2-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | Enables the enhanced Type 3 codebook through a new DCI field to indicate the enhanced Type 3 HARQ-ACK codebook in DCI format 1_2 if the more than one enhanced Type 3 HARQ-ACK codebook is configured for the primary PUCCH cell group. |
| pdsch-HARQ-ACK-RetxDCI-1-2-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | When configured, DCI format 1_2 can request the UE to perform a HARQ-ACK re-transmission on a PUCCH resource (see TS 38.213 [13], clause 9.1.5). |
| pucch-sSCellDynDCI-1-2-r17 ENUMERATED {enabled} · OPTIONAL Need R since v17.0.0 | When configured, PUCCH cell switching based on dynamic indication in DCI format 1_2 is enabled (see TS 38.213 [13], clause 9.A). |
| dl-OrJointTCI-StateList-r17 CHOICE { · OPTIONAL Need R since v17.3.0 | |
| explicitlist SEQUENCE { since v17.3.0 | |
| dl-OrJointTCI-StateToAddModList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-State · OPTIONAL Need N since v17.3.0 | A list of Transmission Configuration Indicator (TCI) states indicating a transmission configuration which includes QCL-relationships between the DL RSs in one RS set and the PDSCH DMRS ports, PDCCH DMRS ports, and CSI-RS, and in case of joint mode, also the PUSCH, PUCCH and SRS (see TS 38.214 [19], clause 5.1.5). |
| dl-OrJointTCI-StateToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofTCI-States)) OF TCI-StateId · OPTIONAL Need N since v17.3.0 | |
| unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17 since v17.3.0 | Provides the serving cell and BWP where the configuration for dl-OrJointTCI-StateToAddModList-r17 are defined. When this field is present, dl-OrJointTCI-StateToAddModList and dl-OrJointTCI-StateToReleaseList are not present. The value of unifiedTCI-StateType of current serving cell is the same in the serving cell indicated by unifiedTCI-StateRef. |
| beamAppTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336, spare2, spare1} · OPTIONAL Need R since v17.0.0 | Indicates the first slot to apply the unified TCI indicated by DCI as specified in TS 38.214 Clause 5.1.5. The value n1 means 1 symbol, n2 two symbols and so on. The first slot is at least Y symbols indicated by beamAppTime parameter after the last symbol of the acknowledgment of the joint or separate DL/UL beam indication. The same value shall be configured for all serving cells in any one of the simultaneousU-TCI-UpdateListN configured in IE CellGroupConfig based on the smallest SCS of the active BWP. |
| dummy SetupRelease { Dummy-TDRA-List } · OPTIONAL Need M since v17.3.0 | This field is not used in the specification. If received it shall be ignored by the UE. |
| dmrs-FD-OCC-DisabledForRank1-PDSCH-r17 ENUMERATED {true} · OPTIONAL Need R since v17.0.0 | If configured, the UE may assume that the set of remaining orthogonal antenna ports, which are within the same code division multiplexing (CDM) group and have different frequency domain orthogonal cover codes (FD-OCC), are not associated with the PDSCH of another UE (see TS 38.214 [19], clause 5.1.6.2). It is applicable for PDSCH SCS of 480 and 960 kHz when rank 1 PDSCH with type-1 or type-2 DMRS is scheduled. If dmrs-TypeEnh-r18 is configured, this field is not configured. |
| minimumSchedulingOffsetK0-r17 SetupRelease { MinSchedulingOffsetK0-Values-r17 } · OPTIONAL Need M since v17.0.0 | List of minimum K0 values. Minimum K0 parameter denotes minimum applicable value(s) for the TDRA table for PDSCH and for A-CSI RS triggering Offset(s) (see TS 38.214 [19], clause 5.3.1). |
| harq-ProcessNumberSizeDCI-1-2-v1700 INTEGER (0..5) · OPTIONAL Need R since v17.0.0 | Configure the number of bits for the field "HARQ process number" in DCI format 1_2 (see TS 38.212 [17], clause 7.3.1). Only one of this field and harq-ProcessNumberSizeDCI-1-2-Ext is configured by network. |
| harq-ProcessNumberSizeDCI-1-1-r17 INTEGER (5) · OPTIONAL Need R since v17.0.0 | |
| mcs-Table-r17 ENUMERATED {qam1024} · OPTIONAL Need R since v17.0.0 | Indicates which MCS table the UE shall use for PDSCH for DCI formats 1_0, 1_1 and 1_3 (see TS 38.214 [19], clause 5.1.3.1). If all fields are absent the UE applies the value 64QAM. If the field mcs-Table-r17 is present for DCI formats 1_1 and 1_3, the network does not configure the field mcs-Table (without suffix). For an (e)RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH. |
| mcs-TableDCI-1-2-r17 ENUMERATED {qam1024} · OPTIONAL Need R since v17.0.0 | Indicates which MCS table the UE shall use for PDSCH for DCI format 1_2 (see TS 38.214 [19], clause 5.1.3.1). If all fields are absent the UE applies the value 64QAM. If the field mcs-TableDCI-1-2-r17 is present, the network does not configure the field mcs-TableDCI-1-2-r16 . For an (e)RedCap UE, the 256QAM MCS table for PDSCH is only supported if the UE indicates support of 256QAM for PDSCH. |
| xOverheadMulticast-r17 ENUMERATED {xOh6, xOh12, xOh18} · OPTIONAL Need S since v17.0.0 | Accounts for an overhead from CSI-RS, CORESET etc. If the field is absent, the UE applies value xOh0 (see TS 38.214 [19]). |
| priorityIndicatorDCI-4-2-r17 ENUMERATED {enabled} · OPTIONAL Need S since v17.0.0 | Configure the presence of "priority indicator" in DCI format 1_1/1_2/4_2. When the field is absent in the IE, then 0 bit for "priority indicator" in DCI format 1_1/1_2/4_2. The field priorityIndicatorDCI-1-1 applies to DCI format 1_1, the field priorityIndicatorDCI-1-2 applies to DCI format 1_2 and the field priorityIndicatorDCI-4-2 applies to DCI format 4_2, respectively (see TS 38.212 [17], clause 7.3.1 and TS 38.213 [13] clause 9). |
| sizeDCI-4-2-r17 INTEGER (20..maxDCI-4-2-Size-r17) · OPTIONAL Need R since v17.0.0 | Indicates the size of DCI format 4-2 (see TS 38.213 [13], clause 10.1). |
| pdsch-TimeDomainAllocationListForMultiPDSCH-r17 SetupRelease { MultiPDSCH-TDRA-List-r17 } · OPTIONAL Need M since v17.0.0 | List of time-domain configurations for timing of DL assignment to DL data. The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0, DCI format 1_1 and DCI format 1_3 (see table 5.1.2.1.1-1 in TS 38.214 [19]), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214 [19]). The field pdsch-TimeDomainAllocationListForMultiPDSCH applies to DCI format 1_1. The field pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 applies to DCI format 1_3. The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config . |
| advancedReceiver-MU-MIMO-r18 SetupRelease { AdvancedReceiver-MU-MIMO-r18 } · OPTIONAL Need M since v18.0.0 | A set of assistance information for R-ML (reduced complexity ML) receivers with enhanced inter-user interference suppression for MU-MIMO transmissions. |
| pdsch-ConfigDCI-1-3-r18 SetupRelease { PDSCH-ConfigDCI-1-3-r18 } · OPTIONAL Need M since v18.0.0 | |
| pdsch-ConfigDCI-1-3-v1860 SetupRelease { PDSCH-ConfigDCI-1-3-v1860 } · OPTIONAL Need M since v18.6.0 | |
| mg-CancellationDCI-1-1-r19 ENUMERATED {enabled} · OPTIONAL Need R since v19.0.0 | Indicates the presence of Measurement gap cancellation in DCI format 1_1 as specified in TS 38.212 [17]. |
| mg-CancellationDCI-1-2-r19 ENUMERATED {enabled} · OPTIONAL Need R since v19.0.0 | Indicates the presence of Measurement gap cancellation in DCI format 1_2 as specified in TS 38.212 [17]. |
| mg-CancellationDCI-1-3-r19 ENUMERATED {enabled} · OPTIONAL Need R since v19.0.0 | Indicates the presence of Measurement gap cancellation in DCI format 1_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. |
| pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3-r19 SetupRelease { MultiPDSCH-TDRA-List-r17 } · OPTIONAL Need M since v19.0.0 | List of time-domain configurations for timing of DL assignment to DL data. The field pdsch-TimeDomainAllocationList (with or without suffix) applies to DCI format 1_0, DCI format 1_1 and DCI format 1_3 (see table 5.1.2.1.1-1 in TS 38.214 [19]), and if the field pdsch-TimeDomainAllocationListDCI-1-2 is not configured, to DCI format 1_2. If the field pdsch-TimeDomainAllocationListDCI-1-2 is configured, it applies to DCI format 1_2 (see table 5.1.2.1.1-1A in TS 38.214 [19]). The field pdsch-TimeDomainAllocationListForMultiPDSCH applies to DCI format 1_1. The field pdsch-TimeDomainAllocationListForMultiPDSCH-DCI-1-3 applies to DCI format 1_3. The network does not configure the pdsch-TimeDomainAllocationList-r16 simultaneously with the pdsch-TimeDomainAllocationList (without suffix) in the same PDSCH-Config . |
| harq-ProcessNumberSizeDCI-1-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 1_1 in TN (see TS 38.212 [17], clause 7.3.1). For FR1, this field can only be configured when the maximum number of layers configured for PDSCH is no more than 4. |
| harq-ProcessNumberSizeDCI-1-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 1_2 in TN (see TS 38.212 [17], clause 7.3.1). For FR1, this field can only be configured when the maximum number of layers configured for PDSCH is no more than 4. Only one of this field and harq-ProcessNumberSizeDCI-1-2 is configured by network. |
| pdsch-ConfigDCI-1-3-v1900 SetupRelease { PDSCH-ConfigDCI-1-3-v1900 } · OPTIONAL Need M since v19.0.0 |
Used by (3)
Uses (30)
- AdvancedReceiver-MU-MIMO-r18
- DMRS-DownlinkConfig
- Dummy-TDRA-List
- MaxMIMO-LayersDL-r16
- MinSchedulingOffsetK0-Values-r16
- MinSchedulingOffsetK0-Values-r17
- MultiPDSCH-TDRA-List-r17
- PDSCH-ConfigDCI-1-3-r18
- PDSCH-ConfigDCI-1-3-v1860
- PDSCH-ConfigDCI-1-3-v1900
- PDSCH-TimeDomainResourceAllocationList
- PDSCH-TimeDomainResourceAllocationList-r16
- RateMatchPattern
- RateMatchPatternGroup
- RateMatchPatternId
- RepetitionSchemeConfig-r16
- RepetitionSchemeConfig-v1630
- ServingCellAndBWP-Id-r17
- SetupRelease
- TCI-State
- TCI-StateId
- ZP-CSI-RS-Resource
- ZP-CSI-RS-ResourceId
- ZP-CSI-RS-ResourceSet
- ZP-CSI-RS-ResourceSetId
- maxDCI-4-2-Size-r17
- maxNrofRateMatchPatterns
- maxNrofTCI-States
- maxNrofZP-CSI-RS-ResourceSets
- maxNrofZP-CSI-RS-Resources