RAN1 / Changes
Position changes
Recent cross-meeting position evolution across every work item and sub-topic in RAN1.
61
Position changes
2
Meetings
AI-synthesized from contributions · all text is paraphrased
9.1.1
-
CATT strengthenedCATT refined their stance on associated ID configuration, specifying it should be at the CSI-Report level rather than requiring similar DL Tx beam properties. They hardened their opposition to extending Rel-17 TCI state activation for multiple future time instances in BM-Case 2, citing complexity. New technical arguments were added regarding the benefit of aligning Rx beam information for NW-sided models and the introduction of an enhanced CPU pool distinct from legacy CPUs. Their support for event-based performance monitoring linked to inference reports is a new addition.
-
FUTUREWEI strengthenedFUTUREWEI hardened their opposition to supporting Opt 3 and Opt 4 for UE-sided model inference reports, explicitly arguing that defining probability and confidence metrics is difficult and offers unclear benefits. They added a new requirement to increase the maximum number of reported beams (M) for network-sided models from 4 to 8. Their support for using RS ID as an implicit beam ID indicator is preserved. They added a preference for Option B for RSRP reporting, which prioritizes measured L1-RSRP over predicted values when measurements are available.
New contributors
- Huawei — Proposes expanding CSI-RS resource set sizes to 256 beams, limits associated ID to single cell, opposes Rel-17 TCI extension, defines BAI metric, and proposes discontinuous CPU occupation.
- InterDigital — Proposes clarifying data collection signaling, separate CSI-ResourceConfig Ids for Set A/B, shared CPU counter, and overhead reduction via X dB gap reporting.
- Kyocera — Proposes distinct config strategies for UE/NW models, explicit Set B config, opposes full beam index reporting, requires consistency between training/inference, and deprioritizes Alt 4.
- Lenovo — Proposes UE-initiated beam management for data collection, combines associated ID with performance monitoring, proposes overhead reduction techniques, and introduces AI Process Units (APUs).
- LG Electronics — Proposes extending Rel-18 NES sub-configuration, configuring only Set B for UE inference, defines similar properties based on spatial filters, opposes Aperiodic CSI-RS for Set B, and introduces APUs.
- NEC — Proposes UE capability reporting with timing conditions, requires P/SP NZP-CSI-RS for rate matching, supports associated ID across multiple cells, separates CPU counting, and defines performance metrics.
- Spreadtrum — Opposes configuring only Set B for UE inference, prefers reusing CRI/SSBRI and TCI frameworks, presents technical case against probability metrics, and requires associated ID in CSI-ReportConfig.
- Tejas Networks Limited — Proposes Associated ID in CSI-Report Config, weighted BAI calculation, Differential L1-RSRP with larger quantization, max beam count M=256, and extending Rel-17 TCI activation.
- vivo — Proposes mandatory Associated ID in inference parameter set and CSI framework, Pattern ID for Set B, cell indicator for Associated ID, quasi-best Rx beams, and TRI/differential quantization for overhead reduction.
- ZTE — Proposes functionality-based LCM without model ID, bitmap-based beam reporting, L1 signaling for NW data collection, and optional associated ID configuration for NW-side conditions.
9.1.2
-
Google shiftedGoogle shifted their focus from general flexible channel measurements to specifically proposing the extension of enhanced path-based measurement to the UE side to reduce reporting overhead. They added a new proposal to report L1-SINR alongside path-based measurements to enable network filtering. For model performance monitoring in Case 1, they refined their support for UE-side monitoring (Option A) by specifying a simple 1-bit failure indication and explicitly opposing Option B due to functional redundancy and privacy concerns. They also added support for Alternative 4, requiring explicit provision of TRP geographical coordinates from the LMF.
-
Huawei shiftedHuawei 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.
-
Ericsson strengthenedEricsson hardened their stance on measurement inputs, moving from a compromise position supporting both sample-based and path-based measurements to explicitly opposing multi-port PDP due to doubled signaling size and marginal performance gains. They consolidated their technical case against phase information and CIR inputs, citing random initial phase issues and high signaling overhead. Additionally, they refined the monitoring framework by establishing self-monitoring as the baseline, with the inference entity responsible for metric calculation, rather than the broader label-free self-monitoring proposal from the prior meeting.
New contributors
- Lenovo — Proposes extending sample-based measurement definitions to UE-based Cases 1 and 2b, supports CIR and legacy measurements as inputs, and proposes a new UE-based positioning method for Direct AI/ML Case 1.
- NEC — Proposes deferring second-priority cases to Rel-20, requires LMF to determine consistent sampling parameters, and supports reporting phase information from gNB to LMF.
- OPPO — Opposes phase information reporting, proposes using associated ID for consistency, and argues against dedicated enhancements for performance monitoring without ground-truth labels.
- Sony — Proposes supporting CIR reporting for data collection, requires association of data sample parts, and supports model transfer from LMF to UE/gNB.
- TCL — Prefers Option A-2 for label-based monitoring, proposes signaling monitoring outcomes only upon deterioration, and introduces AI-specific reference signal configurations.
- Tejas Networks Limited — Proposes specific parameter sets for sample-based measurements, requires redefining LoS/NLoS indication for Case-3a, and supports reusing existing Release-17/18 frameworks.
- vivo — Supports sample-based channel measurements for Case 2b, proposing specific candidate sets for Nt and k. Requires reusing existing IEs for quality indicators and supports using phase information to enhance positioning accuracy.
- ZTE — Proposes reusing existing legacy signaling structures for timestamps and quality indicators. Supports inclusion of phase information (CIR) as model input, presenting technical evidence of superior accuracy. Opposes reporting transmit offset from gNB to LMF in Case 3b.
9.1.3
-
CATT shiftedCATT preserved its stance on negligible impact of tilt/TXRU but refined its position by adding specific proposals for a new processing unit type or enhanced CPU separate from the legacy pool. They added a requirement to distinguish AI/ML CSI reports via a new report quantity or identifier. Their monitoring preference was consolidated to explicitly prefer SGCS for Type 1 and Type 3 while deprioritizing Type 2, moving from general monitoring advocacy to specific metric and resource definitions.
-
CMCC shiftedCMCC softened its stance on associated IDs, moving from proposing a combined solution to preferring no specification of consistency unless degradation is proven. They refined their Type 3 monitoring proposal by explicitly naming SGCS and NMSE as intermediate KPIs. They added new specifics for Type 1 monitoring, proposing two alternatives: calculation/comparison outcomes based on thresholds or recommended LCM decisions. The position shifted from exploring ID mechanisms to focusing on conditional consistency and specific monitoring outputs.
-
Google shiftedGoogle shifted from proposing specific associated ID management to supporting the reuse of the broader Beam Management inference and monitoring frameworks. They added a new specific metric proposal: CQI offset between predicted and ground-truth CSI. They refined their resource configuration proposal by specifying separate CSI-RS resource sets for inference and monitoring. They also added a preference for NW-triggered reports via UCI while deprioritizing event-triggered reports.
-
Huawei shiftedHuawei preserved its core argument against network-side associated IDs but refined its monitoring proposal by adding specific priority rules where monitoring reports take precedence over inference reports. They added new technical requirements for separating CPU counting between legacy and AI/ML CSI reporting and advocating for L1 signaling for monitoring results to address latency. The position shifted from general feasibility arguments to specific signaling layer (L1) and resource management (CPU separation) proposals.
-
LG Electronics shiftedLG Electronics refined its position from high-level consistency arguments to specific implementation mechanisms, adding proposals for reusing the typeIIDoppler-r18' codebook and the existing CPU mechanism. They preserved their opposition to Type 2 monitoring overhead but added a new technical constraint regarding the specification of time limits or buffering windows for inference results linked to monitoring reports. The earlier focus on tilt angle consensus was dropped in favor of these concrete resource and timing definitions.
-
Ericsson strengthenedEricsson hardened its opposition to consistency enhancements by consolidating per-aspect arguments into a blanket conclusion of inapplicability. They refined their proposal by specifying the reuse of the functionality-based LCM framework and requiring the typeII-Doppler-r18' codebook format for both predicted and ground-truth CSI. They narrowed the intermediate KPI scope to SGCS only, explicitly excluding NMSE, and maintained their opposition to Type 2 monitoring.
New contributors
- InterDigital — Argues Associated ID is unnecessary due to high complexity and negligible degradation. Proposes dropping Associated ID requirement, relying on model performance monitoring. Opposes Type 2, supports Type 3. Proposes out-of-distribution metrics alongside intermediate KPIs.
- Lenovo — Proposes reusing AI/ML framework for Beam Management. Requires urgent decision on NW-side additional conditions. Argues against model training at NW with transfer to UE. Prefers deprioritizing model identification techniques, focusing on associated ID and monitoring-based techniques.
- NEC — Proposes reusing associated ID from BM-Case 1/2. Requires support for UE-initiated data collection requests. Proposes configuring distinct observation/prediction windows for P/SP CSI reports. Focuses on Type 1/3 monitoring with SGCS/NMSE, defining fallback criteria.
- OPPO — Argues no consistency issue for UE-sided CSI prediction, rendering associated ID unnecessary. Prioritizes UE-side data collection. Supports reusing Rel-18 MIMO frameworks. Opposes Type 2, proposes average NMSE for Type 3 with configurable averaging.
- Sony — Proposes framework allowing UE to carry out predictions for [N] slots simultaneously. Presents options for slot selection. Proposes specifying CSI-RS values with NMSE or channel matrices with NMSE/SGCS. Emphasizes ground truth availability in prediction slot.
- Spreadtrum — Proposes using associated ID within CSI framework to ensure consistency. Prefers UE-side data collection. Supports Type 1/3 monitoring with SGCS, deprioritizing Type 2. Suggests gNB indicate association between prediction and ground-truth CSI-RS resources.
- TCL — Proposes UE-requested data collection for training, NW-indicated collection for inference/monitoring, and reusing legacy feedback mechanism for TypeII-Doppler-r18'.
- Tejas Networks Limited — Proposes using an associated ID, AI/ML model identification via Model ID in LCM mode, and prioritizing Type 1 performance monitoring with SGCS/NMSE.
- ZTE — Argues against treating tilt/TXRU as NW-side conditions, proposes reusing Rel-18 MIMO CSI prediction codebook, and supports Type 2/3 monitoring.
9.1.1
-
Spreadtrum shiftedSpreadtrum shifted from emphasizing UE-initiated control to favoring network-provided configurations while maintaining opposition to complex new metrics.
-
Huawei strengthenedHuawei shifted from a conservative approach emphasizing reuse of existing frameworks to a more aggressive stance pushing for significant enhancements and expanded capabilities.
New contributors
- CMCC — Advocates for comprehensive AI/ML beam management support with flexible configuration options for both network-side and UE-side models, pushing for enhanced UE capabilities beyond current 64 RS limits and Top-K beam sweeping procedures.
- InterDigital — Strongly advocates for Option 2 applicability approach for UE-side models to avoid excessive configuration overhead, supporting single CSI-ResourceConfigId configuration and UE-assisted performance monitoring over network-only approaches.
- Quectel — Advocates for UE autonomous control in AI/ML beam management, supporting UE-initiated data collection and model management while extending existing CSI frameworks rather than creating entirely new signaling structures.
- Samsung — Advocates for a comprehensive framework supporting both network-side and UE-side models with flexible configuration options, separate CPU counting for AI/ML vs legacy CSI reports, and enhanced signaling mechanisms.
9.1.2
-
Huawei strengthenedHuawei strengthened their position by expanding opposition from general complex signaling to specifically opposing tight specification of sample-based measurements and mandatory phase information.
-
ZTE strengthenedZTE strengthened their position by providing specific quantitative evidence (1.2-2.2x performance improvement) to support their advocacy for CIR with phase information.
New contributors
- CMCC — Advocates for sample-based measurements over path-based measurements and pushes for reusing existing legacy mechanisms where possible to minimize specification impact.
- New H3C Technologies Co. — Strongly advocates for using CIR as AI/ML model input despite higher overhead, arguing it preserves more channel information, and specifically supports relative phase methods over double differential methods.
- Samsung — Advocates for a comprehensive AI/ML positioning framework that balances performance with overhead reduction, supporting flexible data collection approaches and UE autonomy in data provider decisions.
9.1.3
-
ZTE strengthenedZTE evolved from a systematic approach with conditional support to a stronger opposition stance, now emphasizing model generalization capabilities as sufficient without additional consistency mechanisms.
New contributors
- CMCC — Advocates for maximum reuse of existing AI/ML beam management mechanisms for CSI prediction and supports hybrid approaches combining associated IDs with performance monitoring, favoring intermediate KPIs over eventual KPIs.
- Ericsson — Argues against extensive specification enhancements for training/inference consistency, claiming UE-sided CSI prediction models demonstrate sufficient generalization capability across various network conditions.
- Samsung — Strongly advocates for network-assisted AI/ML model training consistency with TRP-related signaling, emphasizing critical need to address severe performance degradation from antenna configuration mismatches.
9.1.4.1
-
Huawei strengthenedHuawei maintained their support for Direction A but strengthened their position by specifically favoring Option 4-1 and adding strong opposition to Direction C based on practical implementation concerns.
New contributors
- CMCC — Advocates for prioritizing Direction A and B over Direction C for inter-vendor collaboration, supporting temporal domain CSI compression with demonstrated performance gains and promoting existing R16 eType-II and Rel-18 Doppler codebooks as starting points.
- Ericsson — Strongly advocates for Direction C (fully standardized reference models) as the most feasible inter-vendor solution, supporting 3GPP channel model-based synthetic data while opposing over-the-air delivery for Direction A due to complexity concerns.
- Samsung — Strongly advocates for angle-delay (W2) domain compression over spatial-frequency (W) domain compression due to superior generalizability, and pushes for temporal aspects in CSI compression (Cases 2 and 3) with specific focus on basis vector refresh.
9.1.4.2
-
Huawei strengthenedHuawei expanded their opposition to cross-vendor collaboration from just Case z1 to Cases z1, z2, z3, and z5, taking a stronger stance against complexity.
-
ZTE strengthenedZTE provided more specific technical justification for opposing MI-Option 2 with concrete resource overhead figures (1-10GB transfers) and added explicit support for Case z4.
New contributors
- CMCC — Advocates for prioritizing MI-Option 2 and MI-Option 3 for model identification while opposing MI-Option 4 due to limited performance gains and high specification efforts. Supports studying model transfer Case z4 with standardized reference model structures.
- Samsung — Advocates for simplified model identification approaches that avoid complex cross-vendor collaboration, supporting network-side additional condition indicators, standardized reference models (MI-Option 4), and restricting data collection to 3GPP network entities.