RAN1 / #119 / NR_AIML_air / Verify

Huawei · 9.1.1

Specification support for beam management · RAN1#119 · Source verification
Claude's delta strengthened vs RAN1#118bis
Huawei shifted from a conservative approach emphasizing reuse of existing frameworks to a more aggressive stance pushing for significant enhancements and expanded capabilities.
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#119 · 1 doc

R1-2409395 discussion not treated 3gpp.org ↗
Discussion on AI/ML for beam management
Position extracted by Claude
Huawei proposes studying mechanisms to support beam sets exceeding 64 resources, either through multiple legacy sets or a single set up to 256 resources. They require the associated ID for UE-side models to be limited to a cell-specific manner to avoid proprietary disclosure and NW burden, and propose applying the ID to a pair of Set A and Set B. Huawei opposes extending Rel-17 TCI state activation for BM-Case 2 future time instances, citing insignificant overhead savings and substantial implementation complexity. They propose reusing existing TCI state timelines for predicted beams and support reporting more than 4 predicted beams (K>4) for UE-side inference. For monitoring, they prefer dedicated CSI report configurations (Option 2) to separate inference and monitoring processes, and propose defining CPU/memory requirements per AI/ML functionality.
Summary
This Huawei Tdoc (R1-2409395) addresses AI/ML for NR Air Interface beam management, presenting 40 proposals and 9 observations across data collection, NW-side and UE-side models, inference, monitoring, and LCM. Key technical stances include supporting larger beam sets (up to 256), reusing legacy TCI timelines for predicted beams, limiting associated IDs to cell-specific scopes, and defining specific CPU/memory handling for UE-side AI/ML functionalities.

Prior contributions at RAN1#118bis · 1 doc · Oct 14, 2024

R1-2407653 discussion not treated 3gpp.org ↗
Discussion on AI/ML for beam management
Position extracted by Claude
Huawei advocates FOR pragmatic reuse of existing CSI framework and signaling mechanisms while pushing AGAINST overly complex new procedures. They strongly support expanding beam measurement capabilities (up to 256 beams vs legacy 64) and unified solutions that work across BM-Case 1/2. They oppose introducing dedicated AI/ML activation signaling and extending TCI state mechanisms for future time instances, arguing these add complexity without significant benefit. Their stance emphasizes cell-specific rather than cross-cell associated IDs to preserve proprietary information and reduce network management burden.
Summary
This Huawei document presents a comprehensive analysis of AI/ML for beam management in NR, containing 38 detailed proposals and 9 observations covering data collection, inference procedures, performance monitoring, and UE capability reporting for both network-side and UE-side AI/ML models.
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 Huawei's consolidated stance at RAN1#119 against their stance at RAN1#118bis and classified the change as strengthened. Always verify critical claims against the original Tdocs linked above.