RAN1 / #120 / NR_AIML_air / Verify

Huawei · 9.1.2

Specification support for positioning accuracy enhancement · RAN1#120 · Source verification
Claude's delta shifted vs RAN1#119
Huawei shifted their argument against phase information, now citing that double phase difference cannot mitigate phase errors in NLOS scenarios and that timing/power suffices. They added a new technical case against the associated ID for TRP location consistency, arguing that TRP locations change infrequently and UE-side burden from combinatorial model training would be excessive. They preserved their stance on reusing legacy IEs for LOS/NLOS indicators and added a proposal to distinguish Rel-19 timing information via timing quality indicators or a specific Rel-19 type indicator.
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

R1-2500090 discussion not treated 3gpp.org ↗
Discussion on AI/ML for positioning accuracy enhancement
Position extracted by Claude
Huawei argues against the necessity of phase information for AI/ML model input, citing that double phase difference cannot mitigate phase errors in NLOS scenarios and that timing/power suffices for performance. They oppose the introduction of an 'associated ID' for TRP location consistency (Alternative 1/2), presenting a technical case that TRP locations are infrequent to change and that UE-side burden from combinatorial model training would be excessive; instead, they support Alternative 3 where Info #7 is not provided. For model output, Huawei proposes reusing legacy IEs for LOS/NLOS indicators and suggests distinguishing Rel-19 timing information via timing quality indicators or a specific Rel-19 type indicator. Regarding monitoring, they propose that label-free monitoring be up to implementation and that for Case 3a, the reporting of measured versus non-measured results can implicitly signal model activation or fallback. Finally, they support functionality-based lifecycle management for UE-side models using legacy capability reporting procedures.
Summary
This Huawei contribution addresses open issues for AI/ML-based positioning in NR Rel-19, covering model input/output, training data collection, consistency, monitoring, and lifecycle management. The document contains 28 proposals and 11 observations, primarily arguing for the reuse of legacy signaling mechanisms and opposing the introduction of new complex identifiers or phase-based inputs.

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

R1-2409396 discussion not treated 3gpp.org ↗
Discussion on AI/ML for positioning accuracy enhancement
Position extracted by Claude
Huawei argues that ambiguity in sample-based measurements for Case 3b can be avoided by implementation rather than strict specification, proposing that gNBs flexibly determine selection window parameters (Nt, Nt', k) while capping Nt' at 16 and Nt at 64 to protect proprietary channel estimation. They support enhancing legacy path-based reporting by increasing the number of reported paths to 16, citing simulation results showing sub-meter accuracy improvements. For Case 3a, they propose reusing the legacy 'LoS/NLoS Information' IE and distinguishing AI/ML timing outputs via timing quality indicators or new Rel-19 indicators. Regarding Case 1, they oppose introducing new positioning methods or implicit signaling, insisting on reusing legacy DL-TDOA assistance data explicitly. For monitoring, they argue that LMF involvement in Case 1 metric calculation is unnecessary and that Case 3a monitoring should rely on measured/non-measured result reporting to imply activation/fallback.
Summary
This Huawei contribution discusses AI/ML for positioning accuracy enhancement in NR, covering model input, output, training, consistency, monitoring, and lifecycle management. It contains 30 proposals and 17 observations, arguing for implementation flexibility, reuse of legacy mechanisms, and protection of proprietary channel estimation methods.
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#120 against their stance at RAN1#119 and classified the change as shifted. Always verify critical claims against the original Tdocs linked above.