RAN1 / #120 / NR_AIML_air / Verify

NEC · 9.1.1

Specification support for beam management · RAN1#120 · Source verification
the AI's delta new vs RAN1#119
NEC is a new contributor in this meeting. They propose that UE capability reporting must include detailed timing conditions for Set B measurements and Set A predictions to enable correct model selection. They require that P/SP NZP-CSI-RS resources for Set A be available for PDSCH rate matching during inference to prevent throughput degradation. They support the use of an associated ID to ensure consistency of NW-side additional conditions across multiple cells, rather than restricting them to a single cell. New proposals include separating CPU counting for AI/ML inference (ACPU) from legacy CSI processing and defining specific performance monitoring metrics including RSRP difference and probability 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

R1-2500590 discussion not treated 3gpp.org ↗
Discussion on specification support for beam management
Position extracted by AI
NEC proposes that UE capability reporting must include detailed timing conditions for Set B measurements and Set A predictions to enable correct model selection. They require that P/SP NZP-CSI-RS resources for Set A be available for PDSCH rate matching during inference to prevent throughput degradation. NEC supports the use of an associated ID to ensure consistency of NW-side additional conditions across multiple cells, rather than restricting them to a single cell. They propose separating CPU counting for AI/ML inference (ACPU) from legacy CSI processing and define specific performance monitoring metrics, including RSRP difference (Alt 3) and probability reporting (Alt 4). Furthermore, NEC argues for enhancing the TCI framework to support predicted beams via QCL references to similar measured patterns and proposes using single MAC CE/DCI commands to activate multiple future TCI states for BM-Case 2.
Summary
NEC presents 46 proposals and 15 observations regarding AI/ML beam management for NR Rel-19, focusing on lifecycle management (LCM) signaling, model inference configurations, and performance monitoring. The document addresses specific technical gaps in UE capability reporting, resource efficiency for Set A/B measurements, and the integration of AI/ML predictions with legacy TCI states and beam failure recovery procedures.

Prior contributions at RAN1#119 · 1 doc · Nov 18, 2024

R1-2409855 discussion not treated 3gpp.org ↗
Discussion on specification support for beam management
Position extracted by AI
NEC advocates FOR UE-centric beam prediction with flexible UE-determined reporting (K-value selection, confidence reporting), comprehensive performance monitoring using RSRP difference metrics, and enhanced TCI framework extensions. They push AGAINST rigid network-only control of prediction parameters and favor Option 3 for UE-initiated applicability reporting, while strongly supporting backward compatibility through simultaneous legacy BM configuration and AI/ML beam management coexistence.
Summary
NEC's technical document on AI/ML enhancements for NR beam management presents comprehensive specifications for both UE-sided and NW-sided models across spatial and temporal beam prediction cases. The document contains 39 proposals and 14 observations covering beam management lifecycle management, performance monitoring, beam indication enhancements, and beam failure recovery improvements.
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 NEC'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.