R1-2500016
LS in
Reply LS to SA2 on AIML data collection
From InterDigital
InterDigital's prior position on
5
at
RAN1#118bis
· AI-synthesized, paraphrased
verify sources →
Advocates for a comprehensive framework balancing MNO control with standardized AI/ML data collection, pushing for solutions ensuring full MNO controllability and visibility while maintaining privacy compliance.
Summary
This document is a Reply Liaison Statement from RAN2 to SA2 regarding AI/ML data collection for NR Air Interface, specifically addressing UE-side model training. It contains six distinct answers to SA2's questions concerning NG-RAN involvement in data controllability, the definition of standardized data, and MNO visibility, with no new technical proposals but rather clarifications of existing RAN2 agreements and scope boundaries.
Position
InterDigital, representing RAN2, clarifies that NG-RAN involvement in UE-side data collection is limited to providing radio measurement configuration, specifically for the beam management use case, while explicitly stating that RAN2 has not concluded on the level of NG-RAN involvement in the actual data transfer process. They define standardized data as content explicitly defined in 3GPP specifications, ensuring the network can understand its meaning, and assert that full MNO visibility allows verification of collected versus reported data without requiring an SLA. RAN2 opposes the assumption that gNB or LMF are in charge of 'initiating, terminating and fully managing data transfer,' restricting their role to configuration provision. They state that roaming considerations are outside RAN2 scope and that the impact of full controllability on UE normal operation has not been evaluated. The position emphasizes that data collection initiation and configuration remain under network control, with the specific determination method still FFS.
Key proposals
- Clarification (Sec 1, Q1): Data collection refers to UE performing measurements (e.g., radio measurements), while data transfer refers to sending collected data from UE to Server for UE-side model training.
- Clarification (Sec 1, Q1): NG-RAN is involved in providing radio measurement configuration for UE-side data collection, at least for the beam management use case, as agreed in RAN2-127bis.
- Clarification (Sec 1, Q1): Data collection initiation and configuration are under network control, though the method for network determination (e.g., via UE requests) is FFS.
- Clarification (Sec 1, Q1): Data transfer can occur at any time under network control if data is available, but RAN2 has not concluded on the specific level of NG-RAN involvement in the transfer process itself.
- Clarification (Sec 1, Q2): gNB is involved in providing radio measurement configuration for beam management, and LMF is involved in providing PRS measurement configuration, but neither is agreed to be in charge of 'initiating, terminating and fully managing data transfer'.
- Clarification (Sec 1, Q3): RAN2 has not evaluated or analyzed the impact on UE normal operation resulting from the full controllability of the data collection process.
- Clarification (Sec 1, Q4): Standardized data is defined as data whose format and content are explicitly defined in 3GPP specifications, allowing the network to understand its content and meaning.
- Clarification (Sec 1, Q5): Roaming considerations for data collection are explicitly stated to be outside the scope of RAN2.
- Clarification (Sec 1, Q6): Full visibility for the MNO means the MNO can be aware of, access, and comprehend the content of collected/reported data without needing an SLA.
- Clarification (Sec 1, Q6): Full visibility allows the MNO to verify and match the data specified/configured to be collected against the data actually being reported.
- Action (Sec 2): RAN2 requests SA2 to take the provided answers into consideration for further discussion on AIML data collection.
- Administrative (Sec 3): Lists upcoming RAN2 meeting dates including Athens (Feb 2025), China (Apr 2025), and Malta (May 2025).
- Scope Definition (Sec 1, Q1): RAN2 requests SA2/SA5 input on the data transfer process, indicating this aspect is not fully resolved within RAN2.
- Use Case Specificity (Sec 1, Q2): Clarifies that controllability roles are defined per use case, specifically distinguishing between beam management (gNB) and positioning (LMF/PRS) configurations.
- Terminology Distinction (Sec 1, Q1): Explicitly distinguishes between 'Data collection' (measurement performance) and 'Data transfer' (sending data to server) to clarify NG-RAN involvement boundaries.