CSI-ReportConfig
CSI-ReportConfig is an RRC information element of 3GPP TS 38.331 (38331), the 5G NR Radio Resource Control (RRC) protocol.
Definition
The IE CSI-ReportConfig is used to configure either (see TS 38.214 [19], clause 5.2.1):
CSI-ReportConfig ::= SEQUENCE {
reportConfigId CSI-ReportConfigId,
carrier ServCellIndex OPTIONAL, -- Need S
resourcesForChannelMeasurement CSI-ResourceConfigId,
csi-IM-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R
nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId OPTIONAL, -- Need R
reportConfigType CHOICE {
periodic SEQUENCE {
reportSlotConfig CSI-ReportPeriodicityAndOffset,
pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource
},
semiPersistentOnPUCCH SEQUENCE {
reportSlotConfig CSI-ReportPeriodicityAndOffset,
pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource
},
semiPersistentOnPUSCH SEQUENCE {
reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320},
reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32),
p0alpha P0-PUSCH-AlphaSetId
},
aperiodic SEQUENCE {
reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32)
}
},
reportQuantity CHOICE {
none NULL,
cri-RI-PMI-CQI NULL,
cri-RI-i1 NULL,
cri-RI-i1-CQI SEQUENCE {
pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S
},
cri-RI-CQI NULL,
cri-RSRP NULL,
ssb-Index-RSRP NULL,
cri-RI-LI-PMI-CQI NULL
},
reportFreqConfiguration SEQUENCE {
cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI } OPTIONAL, -- Need R
pmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI } OPTIONAL, -- Need R
csi-ReportingBand CHOICE {
subbands3 BIT STRING(SIZE(3)),
subbands4 BIT STRING(SIZE(4)),
subbands5 BIT STRING(SIZE(5)),
subbands6 BIT STRING(SIZE(6)),
subbands7 BIT STRING(SIZE(7)),
subbands8 BIT STRING(SIZE(8)),
subbands9 BIT STRING(SIZE(9)),
subbands10 BIT STRING(SIZE(10)),
subbands11 BIT STRING(SIZE(11)),
subbands12 BIT STRING(SIZE(12)),
subbands13 BIT STRING(SIZE(13)),
subbands14 BIT STRING(SIZE(14)),
subbands15 BIT STRING(SIZE(15)),
subbands16 BIT STRING(SIZE(16)),
subbands17 BIT STRING(SIZE(17)),
subbands18 BIT STRING(SIZE(18)),
...,
subbands19-v1530 BIT STRING(SIZE(19))
} OPTIONAL -- Need S
} OPTIONAL, -- Need R
timeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured},
timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured},
codebookConfig CodebookConfig OPTIONAL, -- Need R
dummy ENUMERATED {n1, n2} OPTIONAL, -- Need R
groupBasedBeamReporting CHOICE {
enabled NULL,
disabled SEQUENCE {
nrofReportedRS ENUMERATED {n1, n2, n3, n4} OPTIONAL -- Need S
}
},
cqi-Table CQI-Table OPTIONAL, -- Need R
subbandSize ENUMERATED {value1, value2},
non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks OPTIONAL, -- Need R
...,
[[
semiPersistentOnPUSCH-v1530 SEQUENCE {
reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16}
} OPTIONAL -- Need R
]],
[[
semiPersistentOnPUSCH-v1610 SEQUENCE {
reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R
reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R
} OPTIONAL, -- Need R
aperiodic-v1610 SEQUENCE {
reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL, -- Need R
reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) OPTIONAL -- Need R
} OPTIONAL, -- Need R
reportQuantity-r16 CHOICE {
cri-SINR-r16 NULL,
ssb-Index-SINR-r16 NULL
} OPTIONAL, -- Need R
codebookConfig-r16 CodebookConfig-r16 OPTIONAL -- Need R
]],
[[
cqi-BitsPerSubband-r17 ENUMERATED {bits4} OPTIONAL, -- Need R
groupBasedBeamReporting-v1710 SEQUENCE {
nrofReportedGroups-r17 ENUMERATED {n1, n2, n3, n4}
} OPTIONAL, -- Need R
codebookConfig-r17 CodebookConfig-r17 OPTIONAL, -- Need R
sharedCMR-r17 ENUMERATED {enable} OPTIONAL, -- Need R
csi-ReportMode-r17 ENUMERATED {mode1, mode2} OPTIONAL, -- Need R
numberOfSingleTRP-CSI-Mode1-r17 ENUMERATED {n0, n1, n2} OPTIONAL, -- Need R
reportQuantity-r17 CHOICE {
cri-RSRP-Index-r17 NULL,
ssb-Index-RSRP-Index-r17 NULL,
cri-SINR-Index-r17 NULL,
ssb-Index-SINR-Index-r17 NULL
} OPTIONAL -- Need R
]],
[[
semiPersistentOnPUSCH-v1720 SEQUENCE {
reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R
reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R
reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL -- Need R
} OPTIONAL, -- Need R
aperiodic-v1720 SEQUENCE {
reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R
reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL, -- Need R
reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) OPTIONAL -- Need R
} OPTIONAL -- Need R
]],
[[
codebookConfig-v1730 CodebookConfig-v1730 OPTIONAL -- Need R
]],
[[
groupBasedBeamReporting-v1800 SEQUENCE {
reportingMode-r18 ENUMERATED {jointULDL, onlyUL}
} OPTIONAL, -- Need R
reportQuantity-r18 TDCP-r18 OPTIONAL, -- Need R
codebookConfig-r18 CodebookConfig-r18 OPTIONAL, -- Need R
csi-ReportSubConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfig-r18
OPTIONAL, -- Need N
csi-ReportSubConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfigId-r18
OPTIONAL -- Need N
]],
[[
nrofReportedCLImeasResources-r19 ENUMERATED {n1, n2, n3, n4} OPTIONAL, -- Need R
pucch-CSI-ResourceListExt-r19 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-ResourceExt-v1900 OPTIONAL, -- Need R
symbolType-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL, -- Need R
nrofReportedRS-v1900 ENUMERATED {n6, n8} OPTIONAL, -- Need S
predictionConfiguration-r19 CHOICE {
csi-InferencePrediction-r19 NULL,
configurationForBM-PredictionAndDataCollection-r19 SEQUENCE {
resourcesForChannelPrediction-r19 CSI-ResourceConfigId,
associatedIdForChannelPrediction-r19 AssociatedId-r19 OPTIONAL, -- Need R
associatedIdForChannelMeasurement-r19 AssociatedId-r19 OPTIONAL, -- Need R
nrofReportedPredictedRS-r19 ENUMERATED {n1, n2, n3, n4} OPTIONAL, -- Need R
nrofTimeInstance-r19 ENUMERATED {n1, n2, n4, n8} OPTIONAL, -- Need R
timeGap-r19 ENUMERATED {ms10, ms20, ms40, ms80, ms160, spare3, spare2, spare1}
OPTIONAL, -- Need R
...
},
configurationForBM-Monitoring-r19 SEQUENCE {
refToPredictionConfig-r19 CSI-ReportConfigId,
nrofBestBeamForMonitoring-r19 ENUMERATED {n1, n2} OPTIONAL, -- Need R
nrofTransmissionOccasion-r19 ENUMERATED {n1, n3, n7, n15} OPTIONAL, -- Need R
timeInstanceForRS-PAI-r19 ENUMERATED {n1, n2, n3, n4, n5, n6, n7, n8} OPTIONAL, -- Need R
mappingToResourcesForChannelPrediction-r19
BIT STRING (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OPTIONAL, -- Need R
...
},
configurationForCSI-Monitoring-r19 SEQUENCE {
refToPredictionConfig-r19 CSI-ReportConfigId,
timeInstanceForCSI-PAI-r19 ENUMERATED {n1, n2, n3, n4, n5, n6, n7, n8} OPTIONAL, -- Need R
...
}
} OPTIONAL, -- Need R
codebookConfig-r19 CodebookConfig-r19 OPTIONAL, -- Need R
portMappingMethod-r19 ENUMERATED {method1, method2} OPTIONAL, -- Cond codebookBased
valueOfM-r19 INTEGER(1..4) OPTIONAL, -- Need R
reportQuantity-r19 CHOICE {
noneBM-r19 NULL,
noneCSI-r19 NULL,
p-CRI-r19 NULL,
p-SSB-Index-r19 NULL,
p-CRI-RSRP-r19 NULL,
p-SSB-Index-RSRP-r19 NULL,
rs-PAI-r19 NULL,
csi-PAI-r19 NULL,
cjtc-Dd-r19 NULL,
cjtc-F-r19 NULL,
cjtc-P-r19 NULL,
cjtc-Dd-F-r19 NULL,
cli-RSSI-r19 NULL,
cli-SRS-RSRP-r19 NULL
} OPTIONAL, -- Need R
csi-ReportCJTC-r19 CSI-ReportCJTC-r19 OPTIONAL, -- Need R
csi-ReportSubConfigToAddModListExt-r19 SEQUENCE (SIZE (1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18))
OF CSI-ReportSubConfig-v1900 OPTIONAL, -- Need N
csi-ReportUE-Initiated-r19 CSI-ReportUE-Initiated-r19 OPTIONAL -- Need R
]]
}Candidate change requests of v19.1.0
The CRs whose title or cover names this change, strong and likely matches only.
- CR 5597 r1 (likely): Miscellaneous non-controversial corrections Set XXVI
- CR 5593 r2 (likely): Corrections on RRC for mobility enhancements Phase 4
- CR 5561 r4 (likely): Corrections to AIML for NR air interface
- CR 5544 r2 (likely): Correction on dependency of group-based beam reporting
Fields (142)
| Field | Description |
|---|---|
| reportConfigId CSI-ReportConfigId | |
| carrier ServCellIndex · OPTIONAL Need S since v15.1.0 | Indicates in which serving cell the CSI-ResourceConfig indicated below are to be found. If the field is absent, the resources are on the same serving cell as this report configuration. |
| resourcesForChannelMeasurement CSI-ResourceConfigId since v15.1.0 | Resources for channel measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources and/or SSB resources. This CSI-ReportConfig is associated with the DL BWP indicated by bwp-Id in that CSI-ResourceConfig . For the UE initiated CSI reporting, this field indicates the new beam resource set (see TS 38.214 [19], clause 5.2.1.5.4). |
| csi-IM-ResourcesForInterference CSI-ResourceConfigId · OPTIONAL Need R since v15.1.0 | CSI IM resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only CSI-IM resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement . |
| nzp-CSI-RS-ResourcesForInterference CSI-ResourceConfigId · OPTIONAL Need R since v15.1.0 | NZP CSI RS resources for interference measurement. csi-ResourceConfigId of a CSI-ResourceConfig included in the configuration of the serving cell indicated with the field "carrier" above. The CSI-ResourceConfig indicated here contains only NZP-CSI-RS resources. The bwp-Id in that CSI-ResourceConfig is the same value as the bwp-Id in the CSI-ResourceConfig indicated by resourcesForChannelMeasurement . |
| reportConfigType CHOICE { | Time domain behavior of reporting configuration. |
| periodic SEQUENCE { | |
| reportSlotConfig CSI-ReportPeriodicityAndOffset | Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix). |
| pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource since v15.1.0 | Indicates which PUCCH resource to use for reporting on PUCCH. |
| semiPersistentOnPUCCH SEQUENCE { since v15.1.0 | |
| reportSlotConfig CSI-ReportPeriodicityAndOffset since v15.1.0 | Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix). |
| pucch-CSI-ResourceList SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource since v15.1.0 | Indicates which PUCCH resource to use for reporting on PUCCH. |
| semiPersistentOnPUSCH SEQUENCE { since v15.1.0 | |
| reportSlotConfig ENUMERATED {sl5, sl10, sl20, sl40, sl80, sl160, sl320} since v15.1.0 | Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix). |
| reportSlotOffsetList SEQUENCE (SIZE (1.. maxNrofUL-Allocations)) OF INTEGER(0..32) since v15.1.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| p0alpha P0-PUSCH-AlphaSetId since v15.1.0 | Index of the p0-alpha set determining the power control for this CSI report transmission (see TS 38.214 [19], clause 6.2.1.2). |
| aperiodic SEQUENCE { | |
| reportSlotOffsetList SEQUENCE (SIZE (1..maxNrofUL-Allocations)) OF INTEGER(0..32) since v15.1.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| reportQuantity CHOICE { | The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 is present, UE shall ignore reportQuantity (without suffix). Network does not configure reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 simultaneously . |
| none NULL since v15.1.0 | |
| cri-RI-PMI-CQI NULL since v15.1.0 | |
| cri-RI-i1 NULL since v15.1.0 | |
| cri-RI-i1-CQI SEQUENCE { since v15.1.0 | |
| pdsch-BundleSizeForCSI ENUMERATED {n2, n4} · OPTIONAL Need S since v15.1.0 | PRB bundling size to assume for CQI calculation when reportQuantity is CRI/RI/i1/CQI. If the field is absent, the UE assumes that no PRB bundling is applied (see TS 38.214 [19], clause 5.2.1.4.2). |
| cri-RI-CQI NULL since v15.1.0 | |
| cri-RSRP NULL since v15.1.0 | |
| ssb-Index-RSRP NULL since v15.1.0 | |
| cri-RI-LI-PMI-CQI NULL since v15.1.0 | |
| reportFreqConfiguration SEQUENCE { · OPTIONAL Need R | Reporting configuration in the frequency domain. (see TS 38.214 [19], clause 5.2.1.4). |
| cqi-FormatIndicator ENUMERATED { widebandCQI, subbandCQI } · OPTIONAL Need R | Indicates whether the UE shall report a single (wideband) or multiple (subband) CQI (see TS 38.214 [19], clause 5.2.1.4). |
| pmi-FormatIndicator ENUMERATED { widebandPMI, subbandPMI } · OPTIONAL Need R | Indicates whether the UE shall report a single (wideband) or multiple (subband) PMI. (see TS 38.214 [19], clause 5.2.1.4). |
| csi-ReportingBand CHOICE { · OPTIONAL Need S | Indicates a contiguous or non-contiguous subset of subbands in the bandwidth part which CSI shall be reported for. Each bit in the bit-string represents one subband in order of frequency position in the BWP. The right-most bit in the bit string represents the lowest subband with the lowest frequency position in the BWP. The choice determines the number of subbands (subbands3 for 3 subbands, subbands4 for 4 subbands, and so on) (see TS 38.214 [19], clause 5.2.1.4). This field is absent if there are less than 24 PRBs (no sub band) and present otherwise (see TS 38.214 [19], clause 5.2.1.4). NOTE: In TS 38.212 [17] clause 6.3.1.1.2 and TS 38.214 [19] clause 5.2.1.4, only subbands to be reported are numbered, e.g. subband #0 is the subband corresponding to the right-most bit set to 1. |
| subbands3 BIT STRING(SIZE(3)) since v15.1.0 | |
| subbands4 BIT STRING(SIZE(4)) since v15.1.0 | |
| subbands5 BIT STRING(SIZE(5)) since v15.1.0 | |
| subbands6 BIT STRING(SIZE(6)) since v15.1.0 | |
| subbands7 BIT STRING(SIZE(7)) since v15.1.0 | |
| subbands8 BIT STRING(SIZE(8)) since v15.1.0 | |
| subbands9 BIT STRING(SIZE(9)) since v15.1.0 | |
| subbands10 BIT STRING(SIZE(10)) since v15.1.0 | |
| subbands11 BIT STRING(SIZE(11)) since v15.1.0 | |
| subbands12 BIT STRING(SIZE(12)) since v15.1.0 | |
| subbands13 BIT STRING(SIZE(13)) since v15.1.0 | |
| subbands14 BIT STRING(SIZE(14)) since v15.1.0 | |
| subbands15 BIT STRING(SIZE(15)) since v15.1.0 | |
| subbands16 BIT STRING(SIZE(16)) since v15.1.0 | |
| subbands17 BIT STRING(SIZE(17)) since v15.1.0 | |
| subbands18 BIT STRING(SIZE(18)) since v15.1.0 | |
| subbands19-v1530 BIT STRING(SIZE(19)) since v15.3.0 | |
| timeRestrictionForChannelMeasurements ENUMERATED {configured, notConfigured} since v15.1.0 | Time domain measurement restriction for the channel (signal) measurements (see TS 38.214 [19], clause 5.2.1.1). |
| timeRestrictionForInterferenceMeasurements ENUMERATED {configured, notConfigured} since v15.1.0 | Time domain measurement restriction for interference measurements (see TS 38.214 [19], clause 5.2.1.1). |
| codebookConfig CodebookConfig · OPTIONAL Need R | Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network can only configure one of codebookConfig , codebookConfig-r16, codebookConfig-r17, codebookConfig-r18 or codebookConfig-r19 (if codebookType is configured in codebookConfig-r19 ) in a CSI-ReportConfig . The network includes codebookConfig-v1730 only if codebookConfig-r17 is configured. For codebookConfig-r19 , cri-TypeI-SinglePanel can only be configured when typeI-SinglePanel is configured in codebookConfig and cri-TypeII can only be configured when typeII-r16 is configured in codebookConfig-r16 . |
| dummy ENUMERATED {n1, n2} · OPTIONAL Need R since v15.4.0 | This field is not used in the specification. If received it shall be ignored by the UE. |
| groupBasedBeamReporting CHOICE { | Turning on/off group beam based reporting (see TS 38.214 [19], clause 5.2.1.4). If groupBasedBeamReporting (without suffix) is set to disabled, groupBasedBeamReporting-v1710 and groupBasedBeamReporting-v1800 is absent. The network configures groupBasedBeamReporting-v1800 only if groupBasedBeamReporting-v1710 is configured. |
| enabled NULL | |
| disabled SEQUENCE { | |
| nrofReportedRS ENUMERATED {n1, n2, n3, n4} · OPTIONAL Need S | The number (N) of measured RS resources to be reported per report setting in a non-group-based report. N <= N_max, where N_max is 2, 4, 6 or 8 depending on UE capability. (see TS 38.214 [19], clause 5.2.1.4) When the field is absent the UE applies the value 1. Network does not configure nrofReportedRS-v1900 at the same time as nrofReportedRS (without suffix). |
| cqi-Table CQI-Table · OPTIONAL Need R | |
| subbandSize ENUMERATED {value1, value2} | Indicates one out of two possible BWP-dependent values for the subband size as indicated in TS 38.214 [19], table 5.2.1.4-2 . If csi-ReportingBand is absent, the UE shall ignore this field. |
| non-PMI-PortIndication SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerConfig)) OF PortIndexFor8Ranks · OPTIONAL Need R since v15.1.0 | Port indication for RI/CQI calculation. For each CSI-RS resource in the linked ResourceConfig for channel measurement, a port indication for each rank R, indicating which R ports to use. Applicable only for non-PMI feedback (see TS 38.214 [19], clause 5.2.1.4.2). The first entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the CSI-ResourceConfig whose CSI-ResourceConfigId is indicated in a CSI-MeasId together with the above CSI-ReportConfigId ; the second entry in non-PMI-PortIndication corresponds to the NZP-CSI-RS-Resource indicated by the second entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig , and so on until the NZP-CSI-RS-Resource indicated by the last entry in nzp-CSI-RS-Resources in the in the NZP-CSI-RS-ResourceSet indicated in the first entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig . Then the next entry corresponds to the NZP-CSI-RS-Resource indicated by the first entry in nzp-CSI-RS-Resources in the NZP-CSI-RS-ResourceSet indicated in the second entry of nzp-CSI-RS-ResourceSetList of the same CSI-ResourceConfig and so on. |
| semiPersistentOnPUSCH-v1530 SEQUENCE { · OPTIONAL Need R since v15.3.0 | |
| reportSlotConfig-v1530 ENUMERATED {sl4, sl8, sl16} since v15.3.0 | Periodicity and slot offset (see TS 38.214 [19], clause 5.2.1.4). If the field reportSlotConfig-v1530 is present, the UE shall ignore the value provided in reportSlotConfig (without suffix). |
| semiPersistentOnPUSCH-v1610 SEQUENCE { · OPTIONAL Need R since v16.1.0 | |
| reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) · OPTIONAL Need R since v16.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) · OPTIONAL Need R since v16.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| aperiodic-v1610 SEQUENCE { · OPTIONAL Need R since v16.1.0 | |
| reportSlotOffsetListDCI-0-2-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) · OPTIONAL Need R since v16.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| reportSlotOffsetListDCI-0-1-r16 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..32) · OPTIONAL Need R since v16.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| reportQuantity-r16 CHOICE { · OPTIONAL Need R since v16.0.0 | The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 is present, UE shall ignore reportQuantity (without suffix). Network does not configure reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 simultaneously . |
| cri-SINR-r16 NULL since v16.0.0 | |
| ssb-Index-SINR-r16 NULL since v16.0.0 | |
| codebookConfig-r16 CodebookConfig-r16 · OPTIONAL Need R since v16.0.0 | Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network can only configure one of codebookConfig , codebookConfig-r16, codebookConfig-r17, codebookConfig-r18 or codebookConfig-r19 (if codebookType is configured in codebookConfig-r19 ) in a CSI-ReportConfig . The network includes codebookConfig-v1730 only if codebookConfig-r17 is configured. For codebookConfig-r19 , cri-TypeI-SinglePanel can only be configured when typeI-SinglePanel is configured in codebookConfig and cri-TypeII can only be configured when typeII-r16 is configured in codebookConfig-r16 . |
| cqi-BitsPerSubband-r17 ENUMERATED {bits4} · OPTIONAL Need R since v17.0.0 | This field can only be present if cqi-FormatIndicator is set to subbandCQI . If the field is configured with bits4 , the UE uses 4-bit sub-band CQI. If the field is not present and cqi-FormatIndicator is set to subbandCQI , the UE uses 2-bit sub-band differential CQI. |
| groupBasedBeamReporting-v1710 SEQUENCE { · OPTIONAL Need R since v17.1.0 | Turning on/off group beam based reporting (see TS 38.214 [19], clause 5.2.1.4). If groupBasedBeamReporting (without suffix) is set to disabled, groupBasedBeamReporting-v1710 and groupBasedBeamReporting-v1800 is absent. The network configures groupBasedBeamReporting-v1800 only if groupBasedBeamReporting-v1710 is configured. |
| nrofReportedGroups-r17 ENUMERATED {n1, n2, n3, n4} since v17.1.0 | Number of reported resource groups per CSI-report. Value n1 means one resource group, n2 means 2 resource groups, and so on. If nrofReportedGroups is configured, the UE ignores groupBasedBeamReporting (without suffix). |
| codebookConfig-r17 CodebookConfig-r17 · OPTIONAL Need R since v17.0.0 | Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network can only configure one of codebookConfig , codebookConfig-r16, codebookConfig-r17, codebookConfig-r18 or codebookConfig-r19 (if codebookType is configured in codebookConfig-r19 ) in a CSI-ReportConfig . The network includes codebookConfig-v1730 only if codebookConfig-r17 is configured. For codebookConfig-r19 , cri-TypeI-SinglePanel can only be configured when typeI-SinglePanel is configured in codebookConfig and cri-TypeII can only be configured when typeII-r16 is configured in codebookConfig-r16 . |
| sharedCMR-r17 ENUMERATED {enable} · OPTIONAL Need R since v17.0.0 | Enables sharing of channel measurement resources between different CSI measurement hypotheses when (1) csi-ReportMode is set to 'Mode1' and numberOfSingleTRP-CSI-Mode1 is set to 1 or 2; or (2) csi-ReportMode is set to 'Mode2' (see TS 38.214 [19], clause 5.2.1.4.2). |
| csi-ReportMode-r17 ENUMERATED {mode1, mode2} · OPTIONAL Need R since v17.0.0 | Configures the CSI report modes Mode1 or Mode 2 (see TS 38.214 [19], clause 5.2.1.4.2) |
| numberOfSingleTRP-CSI-Mode1-r17 ENUMERATED {n0, n1, n2} · OPTIONAL Need R since v17.0.0 | Configures the number of reported X CSIs when csi-ReportMode is set to 'Mode 1' as described in TS 38.214 [19], clause 5.2.1.4.2. The field is present only if csi-ReportMode configures Mode 1. |
| reportQuantity-r17 CHOICE { · OPTIONAL Need R since v17.0.0 | The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 is present, UE shall ignore reportQuantity (without suffix). Network does not configure reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 simultaneously . |
| cri-RSRP-Index-r17 NULL since v17.1.0 | |
| ssb-Index-RSRP-Index-r17 NULL since v17.1.0 | |
| cri-SINR-Index-r17 NULL since v17.1.0 | |
| ssb-Index-SINR-Index-r17 NULL since v17.1.0 | |
| semiPersistentOnPUSCH-v1720 SEQUENCE { · OPTIONAL Need R since v17.2.0 | |
| reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) · OPTIONAL Need R since v17.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) · OPTIONAL Need R since v17.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) · OPTIONAL Need R since v17.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| aperiodic-v1720 SEQUENCE { · OPTIONAL Need R since v17.2.0 | |
| reportSlotOffsetList-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) · OPTIONAL Need R since v17.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| reportSlotOffsetListDCI-0-2-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) · OPTIONAL Need R since v17.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| reportSlotOffsetListDCI-0-1-r17 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER(0..128) · OPTIONAL Need R since v17.2.0 | Timing offset Y for semi persistent reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on. The first report is transmitted in slot n+Y, second report in n+Y+P, where P is the configured periodicity. Timing offset Y for aperiodic reporting using PUSCH. This field lists the allowed offset values. This list must have the same number of entries as the pusch-TimeDomainAllocationList in PUSCH-Config . A particular value is indicated in DCI. The network indicates in the DCI field of the UL grant, which of the configured report slot offsets the UE shall apply. The DCI value 0 corresponds to the first report slot offset in this list, the DCI value 1 corresponds to the second report slot offset in this list, and so on (see TS 38.214 [19], clause 6.1.2.1). The field reportSlotOffsetListDCI-0-1 applies to DCI format 0_1 and the field reportSlotOffsetListDCI-0-2 applies to DCI format 0_2 (see TS 38.214 [19], clause 6.1.2.1). The fields reportSlotOffsetList-r17 , reportSlotOffsetListDCI-0-1-r17 and reportSlotOffsetListDCI-0-2-r17 are only applicable for SCS 480 kHz and 960 kHz and if they are configured, the UE shall ignore the fields reportSlotOffsetList (without suffix), reportSlotOffsetListDCI-0-1 (without suffix) and reportSlotOffsetListDCI-0-2 (without suffix) for SCS 480 kHz and 960 kHz. |
| codebookConfig-v1730 CodebookConfig-v1730 · OPTIONAL Need R since v17.3.0 | Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network can only configure one of codebookConfig , codebookConfig-r16, codebookConfig-r17, codebookConfig-r18 or codebookConfig-r19 (if codebookType is configured in codebookConfig-r19 ) in a CSI-ReportConfig . The network includes codebookConfig-v1730 only if codebookConfig-r17 is configured. For codebookConfig-r19 , cri-TypeI-SinglePanel can only be configured when typeI-SinglePanel is configured in codebookConfig and cri-TypeII can only be configured when typeII-r16 is configured in codebookConfig-r16 . |
| groupBasedBeamReporting-v1800 SEQUENCE { · OPTIONAL Need R since v18.0.0 | Turning on/off group beam based reporting (see TS 38.214 [19], clause 5.2.1.4). If groupBasedBeamReporting (without suffix) is set to disabled, groupBasedBeamReporting-v1710 and groupBasedBeamReporting-v1800 is absent. The network configures groupBasedBeamReporting-v1800 only if groupBasedBeamReporting-v1710 is configured. |
| reportingMode-r18 ENUMERATED {jointULDL, onlyUL} since v18.0.0 | Configures the UE with reporting mode for group based reporting.(see TS 38.214 [19] clause 5.2.1.4). |
| reportQuantity-r18 TDCP-r18 · OPTIONAL Need R since v18.0.0 | The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 is present, UE shall ignore reportQuantity (without suffix). Network does not configure reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 simultaneously . |
| codebookConfig-r18 CodebookConfig-r18 · OPTIONAL Need R since v18.0.0 | Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network can only configure one of codebookConfig , codebookConfig-r16, codebookConfig-r17, codebookConfig-r18 or codebookConfig-r19 (if codebookType is configured in codebookConfig-r19 ) in a CSI-ReportConfig . The network includes codebookConfig-v1730 only if codebookConfig-r17 is configured. For codebookConfig-r19 , cri-TypeI-SinglePanel can only be configured when typeI-SinglePanel is configured in codebookConfig and cri-TypeII can only be configured when typeII-r16 is configured in codebookConfig-r16 . |
| csi-ReportSubConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfig-r18 · OPTIONAL Need N since v18.0.0 | List of CSI-ReportSubConfiguration(s) in a CSI report configuration to add or modify. No simultaneous configuration of a1-parameters (including a1-Parameters-v1900 ) and a2-parameters in a same CSI report sub-configuration. The number of elements in a list is at least 2. If the network includes csi-ReportSubConfigToAddModListExt , it includes the same number of entries, and listed in the same order, as in csi-ReportSubConfigToAddModList . |
| csi-ReportSubConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfigId-r18 · OPTIONAL Need N since v18.0.0 | List of CSI-ReportSubConfiguration(s) in a CSI report configuration to release. |
| nrofReportedCLImeasResources-r19 ENUMERATED {n1, n2, n3, n4} · OPTIONAL Need R since v19.0.0 | |
| pucch-CSI-ResourceListExt-r19 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-ResourceExt-v1900 · OPTIONAL Need R since v19.0.0 | |
| symbolType-r19 ENUMERATED {sbfd, non-sbfd} · OPTIONAL Need R since v19.0.0 | Configures the symbol type of periodic/semi-persistent CSI-RS resources for CSI derivation for a CSI report associated with periodic/semi-persistent CSI-RS (see TS 38.214 [19], clause 5). |
| nrofReportedRS-v1900 ENUMERATED {n6, n8} · OPTIONAL Need S since v19.0.0 | The number (N) of measured RS resources to be reported per report setting in a non-group-based report. N <= N_max, where N_max is 2, 4, 6 or 8 depending on UE capability. (see TS 38.214 [19], clause 5.2.1.4) When the field is absent the UE applies the value 1. Network does not configure nrofReportedRS-v1900 at the same time as nrofReportedRS (without suffix). |
| predictionConfiguration-r19 CHOICE { · OPTIONAL Need R since v19.0.0 | Configures the UE with parameters for prediction: - csi-InferencePrediction-r19 indicates inference for CSI prediction; - configurationForBM-PredictionAndDataCollection-r19 can only be configured when reportQuantity-r19 is present and indicates inference for beam management (i.e., reportQuantity-r19 is set to p-CRI , p-SSB-Index , p-CRI-RSRP or p-SSB-Index-RSRP ) or indicates UE-side data collection for beam management (i.e., reportQuantity-r19 is set to noneBM ); - configurationForBM-Monitoring-r19 can only be configured when reportQuantity-r19 is present and indicates monitoring for beam management (i.e., reportQuantity-r19 is set to rs-PAI ); - configurationForCSI-Monitoring-r19 can only be configured when reportQuantity-r19 is present and indicates monitoring for CSI prediction (i.e., reportQuantity-r19 is set to csi-PAI ). |
| csi-InferencePrediction-r19 NULL since v19.0.0 | |
| configurationForBM-PredictionAndDataCollection-r19 SEQUENCE { since v19.1.0 | |
| resourcesForChannelPrediction-r19 CSI-ResourceConfigId since v19.1.0 | Indicates resources to be predicted based on measurements performed on resourcesForChannelMeasurement . The UE is not expected to measure the resources to be predicted, unless the reportQuantity-r19 is set to noneBM . |
| associatedIdForChannelPrediction-r19 AssociatedId-r19 · OPTIONAL Need R since v19.1.0 | Indicates the associated ID for resourcesForChannelPrediction. |
| associatedIdForChannelMeasurement-r19 AssociatedId-r19 · OPTIONAL Need R since v19.1.0 | Indicates the associated ID for resourcesForChannelMeasurement . This field is absent if all NZP-CSI-RS-ResourceId / SSB-Index (es) in resourcesForChannelMeasurement are the same as or a subset of all NZP-CSI-RS-ResourceId / SSB-Index (es) in resourcesForChannelPrediction . |
| nrofReportedPredictedRS-r19 ENUMERATED {n1, n2, n3, n4} · OPTIONAL Need R since v19.1.0 | Indicates the number (K) of predicted RS resources to be reported per report setting, if nrofTimeInstance is not configured. Indicates the number (K) of predicted RS resources per time instance to be reported per report setting, if nrofTimeInstance is configured. This field is present only if reportQuantity-r19 is set to p-CRI , p-SSB-Index , p-CRI-RSRP or p-SSB-Index-RSRP. |
| nrofTimeInstance-r19 ENUMERATED {n1, n2, n4, n8} · OPTIONAL Need R since v19.1.0 | When reportQuantity-r19 is set to p-CRI , p-SSB-Index , p-CRI-RSRP or p-SSB-Index-RSRP , this field indicates the number of future time instance(s) N for prediction to be reported per report setting. When reportQuantity-r19 is set to noneBM , this field indicates the number of expected future time instance(s) N of prediction per report setting. This field is not configured together with other reportQuantity-r19 settings. This field is present only if timeGap is configured. |
| timeGap-r19 ENUMERATED {ms10, ms20, ms40, ms80, ms160, spare3, spare2, spare1} · OPTIONAL Need R since v19.1.0 | When reportQuantity-r19 is set to p-CRI , p-SSB-Index , p-CRI-RSRP or p-SSB-Index-RSRP : - if nrofTimeInstance-r19 is set to 1, this field indicates the time gap between the reference time and the first future time instance for prediction; - if nrofTimeInstance-r19 is set to >1, this field indicates the time gap between two consecutive future time instances for prediction and the time gap between the reference time and the first future time instance for prediction. When reportQuantity-r19 is set to noneBM : - if nrofTimeInstance-r19 is set to 1, this field indicates the expected time gap between the reference time and the first future time instance of prediction; - if nrofTimeInstance-r19 is set to >1, this field indicates the expected time gap between two consecutive future time instances of prediction and the time gap between the reference time and the first future time instance for prediction. This field is present only if nrofTimeInstance-r19 is configured. |
| configurationForBM-Monitoring-r19 SEQUENCE { since v19.1.0 | |
| refToPredictionConfig-r19 CSI-ReportConfigId since v19.1.0 | Indicates the linked CSI-ReportConfigId corresponding to a prediction report configuration. |
| nrofBestBeamForMonitoring-r19 ENUMERATED {n1, n2} · OPTIONAL Need R since v19.1.0 | Indicates the number of best M beam(s) based on L1-RSRP measurements of the resource set(s) for monitoring for performance metric calculation. |
| nrofTransmissionOccasion-r19 ENUMERATED {n1, n3, n7, n15} · OPTIONAL Need R since v19.1.0 | Indicates the number of (N) latest transmission occasion(s) of monitoring resources for performance metric calculation. |
| timeInstanceForRS-PAI-r19 ENUMERATED {n1, n2, n3, n4, n5, n6, n7, n8} · OPTIONAL Need R since v19.1.0 | Indicates the f-th time instance which is used for the performance metric calculation. |
| mappingToResourcesForChannelPrediction-r19 BIT STRING (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) · OPTIONAL Need R since v19.1.0 | If configured, this field indicates the resources included in resourcesForChannelMeasurement to be used for monitoring the channel predictions in the resources resourcesForChannelPrediction included within the linked prediction report configuration indicated by refToPredictionConfig. This field indicates Y non-zero bits in a X-bit bitmap, where X is the size of resourcesForChannelPrediction included within the linked prediction report configuration indicated by refToPredictionConfig and Y is the size of the resource set for monitoring in resourcesForChannelMeasurement . The x-th MSB of the bitmap corresponds to x-th resource in resourcesForChannelPrediction in the linked prediction report configuration indicated by refToPredictionConfig . The y-th nonzero bit of the bitmap corresponds to the y-th entry of associated nzp-CSI-RS-Resources or csi-SSB-ResourceList in the resourcesForChannelMeasurement set for monitoring, 1≤y≤Y. This field is mandatory present only if the size of resourcesForChannelMeasurement is smaller than the size of resourcesForChannelPrediction in the linked prediction report configuration indicated by refToPredictionConfig . If the size of resourcesForChannelMeasurement for monitoring is equal to the size of resourcesForChannelPrediction in the linked prediction report configuration indicated by refToPredictionConfig , the n-th resource in resourcesForChannelMeasurement for monitoring is mapped to the n-th resource in resourcesForChannelPrediction in the linked prediction report configuration indicated by refToPredictionConfig . |
| configurationForCSI-Monitoring-r19 SEQUENCE { since v19.1.0 | |
| refToPredictionConfig-r19 CSI-ReportConfigId since v19.1.0 | Indicates the linked CSI-ReportConfigId corresponding to a prediction report configuration. |
| timeInstanceForCSI-PAI-r19 ENUMERATED {n1, n2, n3, n4, n5, n6, n7, n8} · OPTIONAL Need R since v19.1.0 | Indicates the f-th doppler domain unit which is used for the performance metric calculation for N4>1. |
| codebookConfig-r19 CodebookConfig-r19 · OPTIONAL Need R since v19.0.0 | Codebook configuration for Type-1 or Type-2 including codebook subset restriction. Network can only configure one of codebookConfig , codebookConfig-r16, codebookConfig-r17, codebookConfig-r18 or codebookConfig-r19 (if codebookType is configured in codebookConfig-r19 ) in a CSI-ReportConfig . The network includes codebookConfig-v1730 only if codebookConfig-r17 is configured. For codebookConfig-r19 , cri-TypeI-SinglePanel can only be configured when typeI-SinglePanel is configured in codebookConfig and cri-TypeII can only be configured when typeII-r16 is configured in codebookConfig-r16 . |
| portMappingMethod-r19 ENUMERATED {method1, method2} · OPTIONAL Cond codebookBased since v19.0.0 | Indicates the mapping from CSI-RS resource index/port index per resource to port index for CSI/PMI calculation (see TS 38.214 [19], clause 5.2.1.4). |
| valueOfM-r19 INTEGER(1..4) · OPTIONAL Need R since v19.0.0 | This field is used in clause 5.1, 5.2 and 5.4 in TS 38.214 [19]. This field is configured up to value 4 if codebookType is set to typeI-SinglePanel and up to value 2 if codebookType is set to typeII-r16 . |
| reportQuantity-r19 CHOICE { · OPTIONAL Need R since v19.0.0 | The CSI related quantities to report. see TS 38.214 [19], clause 5.2.1. If the field reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 is present, UE shall ignore reportQuantity (without suffix). Network does not configure reportQuantity-r16, reportQuantity-r17 , reportQuantity-r18 or reportQuantity-r19 simultaneously . |
| noneBM-r19 NULL since v19.1.0 | |
| noneCSI-r19 NULL since v19.1.0 | |
| p-CRI-r19 NULL since v19.0.0 | |
| p-SSB-Index-r19 NULL since v19.0.0 | |
| p-CRI-RSRP-r19 NULL since v19.0.0 | |
| p-SSB-Index-RSRP-r19 NULL since v19.0.0 | |
| rs-PAI-r19 NULL since v19.0.0 | |
| csi-PAI-r19 NULL since v19.1.0 | |
| cjtc-Dd-r19 NULL since v19.0.0 | |
| cjtc-F-r19 NULL since v19.0.0 | |
| cjtc-P-r19 NULL since v19.0.0 | |
| cjtc-Dd-F-r19 NULL since v19.0.0 | |
| cli-RSSI-r19 NULL since v19.0.0 | |
| cli-SRS-RSRP-r19 NULL since v19.0.0 | |
| csi-ReportCJTC-r19 CSI-ReportCJTC-r19 · OPTIONAL Need R since v19.0.0 | Configures parameters used for CJT calibration. |
| csi-ReportSubConfigToAddModListExt-r19 SEQUENCE (SIZE (1..maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18)) OF CSI-ReportSubConfig-v1900 · OPTIONAL Need N since v19.0.0 | List of CSI-ReportSubConfiguration(s) in a CSI report configuration to add or modify. No simultaneous configuration of a1-parameters (including a1-Parameters-v1900 ) and a2-parameters in a same CSI report sub-configuration. The number of elements in a list is at least 2. If the network includes csi-ReportSubConfigToAddModListExt , it includes the same number of entries, and listed in the same order, as in csi-ReportSubConfigToAddModList . |
| csi-ReportUE-Initiated-r19 CSI-ReportUE-Initiated-r19 · OPTIONAL Need R since v19.1.0 | Configures parameters used for the UE initiated CSI reporting. When this field is configured, the UE ignores reportConfigType . |
Used by (1)
Uses (28)
- AssociatedId-r19
- CQI-Table
- CSI-ReportCJTC-r19
- CSI-ReportConfigId
- CSI-ReportPeriodicityAndOffset
- CSI-ReportSubConfig-r18
- CSI-ReportSubConfig-v1900
- CSI-ReportSubConfigId-r18
- CSI-ReportUE-Initiated-r19
- CSI-ResourceConfigId
- CodebookConfig
- CodebookConfig-r16
- CodebookConfig-r17
- CodebookConfig-r18
- CodebookConfig-r19
- CodebookConfig-v1730
- P0-PUSCH-AlphaSetId
- PUCCH-CSI-Resource
- PUCCH-CSI-ResourceExt-v1900
- PortIndexFor8Ranks
- ServCellIndex
- TDCP-r18
- maxNrofBWPs
- maxNrofCSI-ReportSubconfigPerCSI-ReportConfig-r18
- maxNrofNZP-CSI-RS-ResourcesPerConfig
- maxNrofNZP-CSI-RS-ResourcesPerSet
- maxNrofUL-Allocations
- maxNrofUL-Allocations-r16