RAN1 / #119 / NR_AIML_air / Verify

Samsung · 9.1.1

Specification support for beam management · RAN1#119 · Source verification
Claude's delta new vs RAN1#118bis
Samsung newly participated with a comprehensive framework approach including specific technical proposals like separate CPU counting.
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 · 9 docs

R1-2409581 discussion not treated 3gpp.org ↗
Discussion for supporting AI/ML based beam management
Position extracted by Claude
Samsung proposes specific data collection contents for NW-side training, including L1-RSRPs for Set A and Set B and timestamps, conveyed via high-layer signaling. For UE-side inference, they support configurability between Alt 1 and Alt 3 for CSI-ReportConfig and introduce DL Tx IDs to ensure consistent spatial domain transmission filters between Set A and Set B. They propose introducing a Beam Accuracy Indicator (BAI) for Type 1 Option 2 performance monitoring, calculated over X CSI reports, and prefer dedicated CSI report configurations for monitoring resources. Regarding CPU handling, Samsung proposes separate CPU counting for AI/ML-based CSI reports and scaling the legacy Z timeline based on UE capability.
Summary
Samsung presents 30 proposals and 1 observation regarding AI/ML-based beam management for NR, covering both NW-side and UE-side models. The document addresses data collection for training and inference, spatial and temporal enhancements for beam reporting, consistency mechanisms via DL Tx IDs and associated IDs, performance monitoring metrics like BAI, and CPU/timeline considerations for UE-side inference.
R1-2410733 discussion noted 3gpp.org ↗
FL summary #0 for AI/ML in beam management
Position extracted by Claude
Samsung advocates for a flexible framework combining multiple options for UE-side model applicability (merging Options 1 and 2), supports dedicated monitoring configurations separate from inference configurations, and pushes for practical beam accuracy indicators with multiple definition alternatives. They oppose overly restrictive single-option approaches and advocate for reusing existing CSI framework mechanisms where possible while introducing necessary AI/ML-specific enhancements.
Summary
This Samsung-moderated 3GPP RAN1 document (Tdoc R1-2410733) presents a comprehensive summary of AI/ML beam management contributions from meeting #118, containing over 100 proposals across multiple technical areas. The document covers UE-side and network-side models for both spatial (BM-Case1) and temporal (BM-Case2) beam prediction, addressing configuration, performance monitoring, inference reporting, and beam indication frameworks.
R1-2410734 discussion noted 3gpp.org ↗
FL summary #1 for AI/ML in beam management
Position extracted by Claude
Samsung advocates for a flexible approach supporting multiple options for UE-sided model applicability reporting, favoring dedicated monitoring configurations separate from inference configurations, and supporting enhanced quantization steps for overhead reduction. They push for practical solutions that maintain consistency between training and inference while enabling both spatial and temporal beam prediction capabilities.
Summary
This Samsung-moderated FL summary document for RAN1#119 contains over 250 proposals and observations across 9 main sections covering AI/ML beam management, including RAN2 LS handling, performance monitoring, configuration aspects, and inference reporting. The document addresses both UE-sided and NW-sided AI/ML models for spatial (BM-Case1) and temporal (BM-Case2) beam prediction use cases.
R1-2410735 discussion noted 3gpp.org ↗
FL summary #2 for AI/ML in beam management
Position extracted by Claude
Samsung advocates for a comprehensive framework supporting both UE-side and NW-side AI/ML models with emphasis on: 1) Flexible applicability reporting combining multiple options rather than forcing single approach, 2) Dedicated monitoring configurations separate from inference to avoid complexity, 3) Practical reference time definitions based on actual transmission occasions rather than abstract timing, 4) Rich content options for data collection including multiple types to support different model requirements, and 5) Reuse of existing CSI framework mechanisms where possible to minimize specification impact.
Summary
This 3GPP RAN1 technical document (Tdoc R1-2410735) from Samsung serves as FL summary #2 for AI/ML in beam management, containing over 200 proposals and observations across multiple technical areas including performance monitoring, configuration methods, inference reporting, and beam indication mechanisms.
R1-2410736 discussion noted 3gpp.org ↗
FL summary #3 for AI/ML in beam management
Position extracted by Claude
Samsung, as the document moderator, advocates for: (1) merging applicability options to give RAN2 flexibility in container design while supporting both CSI-ReportConfig and inference parameter approaches, (2) comprehensive performance monitoring with beam accuracy indicators and dedicated monitoring configurations, (3) flexible reference time definition based on actual measurement occasions rather than reporting slots, (4) supporting multiple resource sets for temporal beam prediction, and (5) reusing existing CSI framework where possible while allowing necessary enhancements. Samsung pushes against overly restrictive designs that limit implementation flexibility.
Summary
This document is Samsung's FL summary #3 for AI/ML in beam management from RAN1 #119, containing over 40 proposals and observations covering UE-side and NW-side model configurations, performance monitoring, data collection, inference reporting, and beam indication frameworks.
R1-2410737 discussion noted 3gpp.org ↗
FL summary #4 for AI/ML in beam management
Position extracted by Claude
Samsung advocates for practical AI/ML beam management implementations that reuse existing CSI frameworks while introducing minimal spec impact. They push FOR: reusing legacy CSI-ReportConfig structures, supporting both UE-side and NW-side models with clear associated ID mechanisms, and practical performance monitoring with beam accuracy indicators. They push AGAINST: overly complex new signaling frameworks and support maintaining compatibility with existing beam management procedures.
Summary
This is Samsung's summary document (R1-2410737) for AI/ML in beam management from RAN1 #119 meeting, containing over 200 proposals and observations from multiple companies covering UE-side and NW-side model configurations, performance monitoring, data collection, and beam indication frameworks.
R1-2410892 discussion noted 3gpp.org ↗
FL summary #5 for AI/ML in beam management
Position extracted by Claude
Samsung, as the moderator, advocates for a comprehensive AI/ML beam management framework supporting both UE-sided and NW-sided models with practical implementation considerations. They push for flexible configuration options (supporting multiple alternatives rather than premature down-selection), reuse of existing CSI frameworks where possible, and clear separation between AI/ML and legacy processing. Samsung opposes overly complex signaling mechanisms and premature standardization of implementation-specific details, favoring solutions that provide network flexibility while maintaining UE implementation freedom.
Summary
This is Samsung's FL summary #5 for AI/ML in beam management (Tdoc R1-2410892), containing over 100 proposals addressing UE-sided and NW-sided models, performance monitoring, configuration frameworks, and beam indication mechanisms across multiple technical issues.
R1-2410893 LS out revised 3gpp.org ↗
[DRAFT] Reply LS on applicable functionality reporting for beam management UE-sided model
Position extracted by Claude
Samsung/RAN1 advocates for a flexible AI/ML functionality reporting framework that supports both CSI-ReportConfig-based inference configuration and separate inference parameter sets for applicability reporting. They push for optional network-side additional conditions and support associated ID mechanisms while maintaining that activation timing and mandatory/optional status of various parameters remain under discussion.
Summary
This is a liaison statement from RAN1 to RAN2 responding to questions about beam management UE-sided AI/ML model functionality reporting. The document provides answers to 9 detailed questions and includes 2 agreements and 1 conclusion about the configuration and activation procedures for AI/ML-enabled beam management features.
R1-2410898 LS out approved 3gpp.org ↗
Reply LS on applicable functionality reporting for beam management UE-sided model
Position extracted by Claude
Samsung advocates FOR a flexible CSI framework-based approach to AI/ML functionality management with clear separation between supported, applicable, and activated functionalities. They push FOR allowing multiple CSI reports for inference based on UE capability and support associated ID usage for consistency. They are AGAINST immediate activation of CSI report configurations upon receiving Step 3, insisting on proper applicability reporting procedures first.
Summary
Samsung's response to RAN2's liaison statement regarding applicable functionality reporting for beam management UE-sided AI/ML models, containing 4 key observations about terminology definitions and 3 agreements/conclusions on configuration procedures and CSI reporting mechanisms.

Prior contributions

Samsung 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
Claude extracted the "position extracted" field above directly from each Tdoc during summarization. For the delta summary at the top, Claude compared Samsung'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.