R2-2504133 Further Thoughts on IDC issue between GNSS and NTN UL.docx
3GPP TSG-RAN WG2 Meeting #130 R2-2504133 St. Julians, Malta, 19th - 23rd of May 2025 Agenda item: 7.0.2.17 Source: Nokia, Nokia Shanghai Bell Title: Further Thoughts on IDC issue between GNSS and NTN UL WID/SID: NR_NTN_enh-Core - Release 18 Document for: Discussion and Decision 1
Conclusion This document has made the following observations and proposals: Observation 1: RAN2 attempted to understand what kind of periodicity and duration of IDC free time could be required for the UE to measure GNSS. Observation 2: RAN2 could not conclude without consulting other WGs, so sent the LS to RAN4, asking this group on the periodicity and duration of IDC free time to help the UE read the GNSS. Observation 3: The LS from RAN2 has been discussed at RAN4#114bis, but without any consensus regarding the requirements to be indicated to RAN2. Observation 4: It might turn out, RAN2 needs to proceed without the feedback from RAN4. Observation 5: When multiple UEs use IDC-TDM scheme with maximum values of activeDuration and cycle length, it results in 15% of UL transmissions that might be avoided. This brings a serious complexity to NW’s scheduler. Proposal 1: Do not consider an extension of autonomousDenialSlots which would increase the number of slots the UE can autonomously deny and bring additional complexity to UL scheduling. Proposal 2: If a specification change to address the IDC issue is needed, consider extending the length of the activeDuration in IDC-TDM solution.

R2-2504133 Further Thoughts on IDC issue between GNSS and NTN UL.docx

3GPP TSG-RAN WG2 Meeting #130	R2-2504133
St. Julians, Malta, 19th - 23rd of May 2025	


Agenda item:	7.0.2.17
Source:	Nokia, Nokia Shanghai Bell
Title:	Further Thoughts on IDC issue between GNSS and NTN UL 
WID/SID:	NR_NTN_enh-Core - Release 18
Document for:	Discussion and Decision
1

Conclusion
This document has made the following observations and proposals:
Observation 1: RAN2 attempted to understand what kind of periodicity and duration of IDC free time could be required for the UE to measure GNSS.
Observation 2: RAN2 could not conclude without consulting other WGs, so sent the LS to RAN4, asking this group on the periodicity and duration of IDC free time to help the UE read the GNSS.
Observation 3: The LS from RAN2 has been discussed at RAN4#114bis, but without any consensus regarding the requirements to be indicated to RAN2.
Observation 4: It might turn out, RAN2 needs to proceed without the feedback from RAN4.
Observation 5: When multiple UEs use IDC-TDM scheme with maximum values of activeDuration and cycle length, it results in 15% of UL transmissions that might be avoided. This brings a serious complexity to NW’s scheduler.
Proposal 1: Do not consider an extension of autonomousDenialSlots which would increase the number of slots the UE can autonomously deny and bring additional complexity to UL scheduling.
Proposal 2: If a specification change to address the IDC issue is needed, consider extending the length of the activeDuration in IDC-TDM solution.