Spreadtrum · 9.1.3
Specification support for CSI prediction ·
RAN1#120 · Source verification
Claude's delta
new
vs RAN1#119
Spreadtrum is a new contributor. They propose using an associated ID configured within the CSI framework to ensure consistency, arguing that monitoring-based approaches cause unacceptable performance loss. They prefer UE-side data collection and support Type 1 and Type 3 monitoring using SGCS, while deprioritizing Type 2. They added a proposal for the gNB to indicate the association between prediction and ground-truth CSI-RS resources.
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 AIML for CSI prediction
Position extracted by Claude
Spreadtrum proposes using an associated ID, configured within the CSI framework, to ensure consistency between training and inference for UE-sided CSI prediction models, arguing that performance monitoring-based approaches cause unacceptable performance loss due to trial-and-error processes. They prefer UE-side data collection over network-side collection to avoid significant reporting overhead and model transfer complexities, suggesting that NW configuration or UE requests should trigger this collection. For inference, they propose reusing Rel-18 MIMO CSI-RS configurations to reduce specification impact. Regarding monitoring, they support Type 1 and Type 3 monitoring using intermediate KPIs like SGCS, while explicitly deprioritizing Type 2 monitoring due to the high overhead of reporting ground-truth CSI to the gNB. They further suggest that gNB should indicate the association between prediction and ground-truth CSI-RS resources to facilitate accurate metric calculation.
Summary
Spreadtrum presents eight proposals for 3GPP RAN1 regarding AI/ML-based CSI prediction in NR, focusing on ensuring consistency between training and inference, defining data collection procedures, and establishing performance monitoring mechanisms. The document argues for reusing existing Rel-18 CSI-RS configurations and prioritizing UE-side data collection to minimize specification impact and signaling overhead.
Prior contributions at RAN1#119 · 1 doc · Nov 18, 2024
Discussion on AIML for CSI prediction
Position extracted by Claude
Spreadtrum argues that the 'associated ID' mechanism, previously introduced for Beam Management (AI-BM), should be reused for CSI prediction to ensure consistency of network-side additional conditions across training and inference. They present a technical case against 'performance monitoring based' approaches (Option 2), arguing that such methods require a trial-and-error process causing significant performance loss and cannot distinguish consistency issues from other degradation factors. Consequently, they prefer Option 1, where the UE assumes consistency is guaranteed if training and inference data share the same associated ID. Furthermore, they propose that the associated ID for CSI prediction should be configured within the existing CSI framework, leveraging the fact that reference resources for channel measurement are already defined there.
Summary
Spreadtrum discusses the consistency of training and inference for UE-sided CSI prediction models, proposing the reuse of the 'associated ID' mechanism from Beam Management to ensure network-side conditions remain consistent. The document contains two main proposals: using the associated ID to guarantee consistency and configuring it within the existing CSI framework.
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 Spreadtrum'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.