TCL · 9.1.3
Specification support for CSI prediction ·
RAN1#120 · Source verification
the AI's delta
new
vs RAN1#119
TCL is a new contributor in the current meeting data. They propose a split approach for data collection: UE-requested for training and NW-indicated for inference/monitoring. They argue for reusing the legacy feedback mechanism for codebook type TypeII-Doppler-r18' and supporting dynamic updates to the number of predicted CSIs. They prefer Type 3 monitoring as the baseline and propose real-time monitoring with periodic, semi-persistent, aperiodic, and event-driven reporting.
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 the AI 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 CSI Prediction
Position extracted by AI
TCL proposes that data collection for model training should be requested by the UE, citing that the UE possesses more model information than the network, while data collection for inference and performance monitoring should be indicated by the NW. They argue for reusing the legacy feedback mechanism for codebook type 'TypeII-Doppler-r18' and supporting dynamic updates to the number of predicted CSIs based on performance deterioration. For performance monitoring, TCL prefers Type 3 as the baseline over Type 2 due to lower reporting overhead, and supports real-time monitoring with periodic, semi-persistent, aperiodic, and event-driven reporting. They further propose that CSI processing criteria and timelines require further discussion for different model operation stages.
Summary
TCL presents 13 proposals regarding AI-based CSI prediction using UE-side models, covering data collection, model inference, and performance monitoring. The document argues for UE-initiated data collection for training, NW-indicated collection for inference and monitoring, and the reuse of legacy Rel-18 Doppler codebook mechanisms.
Prior contributions
TCL has no prior contributions to 9.1.3 in the meetings currently tracked. This is either a new contributor to this sub-topic or the earliest meeting in our history.
How this was derived
The AI extracted the "position extracted" field above directly from each Tdoc during summarization.
For the delta summary at the top, the AI compared TCL's consolidated stance at RAN1#120
against their stance at RAN1#119 and classified the change as
new.
Always verify critical claims against the original Tdocs linked above.