3GPP TSG-RAN WG2 Meeting #130 R2-2504130
St Julian’s, Malta, May 19 - 23, 2025
Agenda Item: 8.1.1
Source: Qualcomm Incorporated (Rapporteur)
Title: LPP open issues for feature "AI/ML for NR air interface"
Document for: Discussion, Decision
|
Conclusions
The following proposals have been provided based on feedback to the above document:
[Proposals for easy agreement]
Proposal LPP-1 (6/6): The field dl-PRS-ResourcePrioritySubset in IE NR-DL-PRS-Info should be ignored for NR AI/ML positioning. Remove corresponding 'Editor's Note' from the running CR.
Proposal LPP-2 (6/6): Regarding the applicability of IE NR-DL-PRS-ProcessingCapability to NR AI/ML positioning Case 1, wait for further RAN1 input and keep the current "Editor's Note" in the running CR for now.
Proposal LPP-3 (6/6): Regarding the applicability of IE NR-DL-PRS-QCL-ProcessingCapability to NR AI/ML positioning Case 1, wait for further RAN1 input and keep the current "Editor's Note" in the running CR for now.
Proposal LPP-4 (6/6): Regarding the applicability of IE NR-DL-PRS-ResourcesCapability to NR AI/ML positioning Case 1, wait for further RAN1 input and keep the current "Editor's Note" in the running CR for now.
Proposal LPP-5 (5/6): The IE NR-On-Demand-DL-PRS-Configurations-Selected-IndexList is also applicable to NR AI/ML positioning Case 1. The corresponding Editor's Notes in clause 6.4.3, 6.5.10.1, and 6.5.11.1 can be removed.
Proposal LPP-8 (5/6): The IE NR-AI-ML-PositioningProvideAssistanceData contains (at least) all assistance data elements from UE-based DL-TDOA as starting point. This will be revised when additional RAN1 input is available. The current Editor's Note is kept for now.
Proposal LPP-9 (5/6): The IE NR-AI-ML-PositioningRequestAssistanceData contains (at least) all assistance data elements from UE-based DL-TDOA as starting point. This will be revised when additional RAN1 input is available. The current Editor's Note is kept for now.
Proposal LPP-10 (6/6): The IE NR-AI-ML-PositioningProvideLocationInformation contains (at least) the time stamp for the location coordinates (which are reported in CommonIEsProvideLocationInformation). This will be revised when additional RAN1 input is available. The current Editor's Note is kept for now.
Proposal LPP-11 (6/6): The IE NR-AI-ML-PositioningRequestLocationInformation contains (at least) the AssistanceAvailability flag. Additional details/information can be discussed via company contributions.
Proposal LPP-12 (4/6): The IE NR-AI-ML-PositioningProvideCapabilities contains (at least) all capabilities from UE-based DL-TDOA as starting point, except the capability related to DL-PRS processing (see #LPP-2/3/4). This will be revised when additional RAN1 input is available. The current Editor's Note is kept for now.
NOTE: Per discussion in "R2-250xxxx_([POST129bis][015][AI PHY] Discussion)_v05_Rap.docx", the IE names for
AI/ML positioning in the above Proposals have been changed as follows:
NR-AI-ML-PositioningProvideAssistanceData NR-DL-AIML-ProvideAssistanceData
NR-AI-ML-PositioningRequestAssistanceData NR-DL-AIML-RequestAssistanceData
NR-AI-ML-PositioningProvideLocationInformation NR-DL-AIML-ProvideLocationInformation
NR-AI-ML-PositioningRequestLocationInformation NR-DL-AIML-RequestLocationInformation
NR-AI-ML-PositioningProvideCapabilities NR-DL-AI-ML-ProvideCapabilities
NR-AI-ML-PositioningRequestCapabilities NR-DL-AIML-RequestCapabilities
NR-AI-ML-Positioning-Error NR-DL-AIML-Positioning-Error
[Open Issues for further discussion (e.g., based company contributions and further RAN1 input)]
Open Issue LPP-6: Applicability of NR-PRU-DL-Info
Open issue LPP-7: Applicability of NR-SelectedDL-PRS-IndexList
Open issue LPP-10a: Applicability of "batch reporting" for AI/ML positioning.
Open issue LPP-13: Location server error causes
Open issue LPP-14: Target device error causes
[New Issues]
Open issue LPP-15: Applicability of Positioning Integrity to AI/ML positioning
Open issue LPP-16: Signalling of Monitoring Outcome
Open issue LPP-17: Signalling of "ground-truth label" information
|
3GPP RAN WG2 Meeting #130 R2-2504350
St. Julian’s, Malta, May 19th – 23rd, 2025
Agenda Item: 8.1.1
Source: Ericsson
Title: Remaining RRC open issues in feature AIML PHY
Document for: Discussion, Decision
|
Conclusions
The following proposals are made based on the list of open issues above:
For LCM for BM, the Rapporteur suggests to prioritize the following open issues for RAN2#130: RRC-1, RRC-2, RRC-3, RRC-4, RRC-5, RRC-6. Open issues RRC-7 and RRC-8 can be discussed with lower priority.
For LCM for BM, the Rapporteur suggests to discuss after the next RAN2 meeting the following open issues: RRC-9, RRC-10, RRC-11, RRC-12, RRC-13, RRC-14, RRC-15, RRC-16, RRC-17.
For NW-side data collection, the Rapporteur suggests to prioritize the following open issues for RAN2#130: RRC-18, RRC-19, RRC-20, RRC-21, RRC-22, RRC-23, RRC-24, RRC-25, RRC-26, RRC-27, RRC-28. Open issue RRC-29 can be discussed with lower priority.
The Rapporteur suggests to treat the following open issues after the next RAN2 meeting: RRC-30, RRC-31, RRC-32, RRC-33, RRC-34, RRC-35, RRC-36, RRC-37, RRC-38, RRC-39.
|