CMCC · 9.1.1
Specification support for beam management ·
RAN1#119 · Source verification
the AI's delta
new
vs RAN1#118bis
CMCC newly joined the discussions with a comprehensive approach advocating for enhanced capabilities and flexible configurations.
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#119 · 1 doc
Discussion on specification support for beam management
Position extracted by AI
CMCC proposes that L1 signaling be supported for NW-sided training data collection and that Top-K beam sweeping be supported for NW-side inference to enhance prediction accuracy. They require that for UE-side models, the overall CPU be separately counted between legacy CSI reporting and AI/ML-based CSI reporting, while being shared among AI/ML features. CMCC prefers Option 1 for BM-Case 2 differential RSRP reporting, which includes CRI of top-K predicted beams per instance. They support dedicated resource sets and report configurations for UE-side model monitoring (Type 1 Option 2), linking the monitoring configuration to an inference report configuration via CSI-ReportConfig ID. Additionally, they propose that the granularity of UE capability reporting for AI/ML be at the sub-use case level, including details on Set A/B size, RS type, and model outputs.
Summary
CMCC presents 49 proposals and 2 observations regarding the specification impacts of AI/ML-based beam management for NR, covering data collection, inference, and monitoring for both NW-side and UE-side models. The document addresses configuration of Set A and Set B, reporting content for training and inference, Top-K beam sweeping procedures, and performance monitoring mechanisms including KPI definitions and resource set configurations.
Prior contributions
CMCC has no prior contributions to 9.1.1 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 CMCC's consolidated stance at RAN1#119
against their stance at RAN1#118bis and classified the change as
new.
Always verify critical claims against the original Tdocs linked above.