CMCC · 9.1.3
Specification support for CSI prediction ·
RAN1#120 · Source verification
Claude's delta
shifted
vs RAN1#119
CMCC softened its stance on associated IDs, moving from proposing a combined solution to preferring no specification of consistency unless degradation is proven. They refined their Type 3 monitoring proposal by explicitly naming SGCS and NMSE as intermediate KPIs. They added new specifics for Type 1 monitoring, proposing two alternatives: calculation/comparison outcomes based on thresholds or recommended LCM decisions. The position shifted from exploring ID mechanisms to focusing on conditional consistency and specific monitoring outputs.
AI-synthesized from contributions · all text is paraphrased
Every position summary on this site is generated by an AI from the actual Tdoc contributions. This page shows you the exact source documents Claude read to produce the summary above, so you can verify it yourself. Click any Tdoc ID to view its detail page, or click "3gpp.org ↗" to read the original on the official 3GPP server.
Contributions at RAN1#120 · 1 doc
Discussion on AI/ML for CSI prediction
Position extracted by Claude
CMCC prefers not to specify consistency of training/inference regarding NW-side additional conditions (such as tilt angle and TXRU mapping) unless sufficient simulation results demonstrate non-negligible degradation on model generalization performance, citing current observations of negligible impact. For performance monitoring, CMCC proposes using intermediate KPIs (e.g., SGCS, NMSE) as the starting point for Type 3 monitoring, arguing that eventual KPIs are inappropriate due to dependency on external factors like scheduling. For Type 1 monitoring, CMCC presents two alternatives for performance output: calculation/comparison outcomes based on thresholds or recommended LCM decisions reported to the NW. CMCC supports reusing the data collection mechanism from AI/ML-based beam management for CSI prediction to minimize specification overhead. Finally, CMCC proposes reusing Rel-18 CSI parameters (e.g., measurement and reporting windows) with necessary modifications to adapt to AI/ML-enabled CSI prediction, rather than defining entirely new parameters.
Summary
CMCC discusses specification impacts for AI/ML-based CSI prediction in Rel-19, focusing on training/inference consistency, performance monitoring, data collection, and inference parameters. The document presents five proposals, arguing against specifying NW-side condition consistency unless significant degradation is proven, favoring intermediate KPIs for monitoring, and suggesting reuse of Rel-18 mechanisms with modifications.
Prior contributions at RAN1#119 · 1 doc · Nov 18, 2024
Discussion on AI/ML for CSI prediction
Position extracted by Claude
CMCC proposes studying two options for ensuring consistency of NW-side additional conditions across training and inference for AI-based CSI prediction: one based on associated ID and another based on performance monitoring. They propose combining these solutions, where the associated ID preliminarily guarantees consistency without exposing proprietary information, while performance monitoring handles residual issues. CMCC requires that if associated ID is supported, the UE assumes consistency of NW-side additional conditions with the same ID at least within a cell, and that the ID is configured within the CSI framework. For performance monitoring, they propose using intermediate KPIs as a starting point for Type 3 monitoring and present two alternatives for Type 1 monitoring involving UE-calculated metrics or UE-recommended LCM decisions. Finally, CMCC proposes reusing data collection mechanisms from AI/ML beam management and adapting Rel-18 CSI parameters, such as measurement and reporting windows, for AI/ML-enabled CSI prediction.
Summary
CMCC discusses specification impacts for AI/ML-based CSI prediction in Rel-19, focusing on ensuring consistency between training and inference phases. The document presents 8 proposals covering consistency mechanisms via associated IDs and performance monitoring, data collection reuse from beam management, and adaptation of Rel-18 CSI parameters.
How this was derived
Claude extracted the "position extracted" field above directly from each Tdoc during summarization.
For the delta summary at the top, Claude compared CMCC's consolidated stance at RAN1#120
against their stance at RAN1#119 and classified the change as
shifted.
Always verify critical claims against the original Tdocs linked above.