Way forward for FS_eNPN_Ph2 KI#1 Ericsson
Description: Way forward for FSeNPNPh2 KI1 Ericsson (Rapporteur) Background KI1 S2-2205796 proposes evaluation and conclusion for KI1, but there is an open issue for which the P-CR includes two options as how to move forward i.e. open issue is: It
Related Topics
Download Presentation
"Way forward for FS_eNPN_Ph2 KI#1 Ericsson" is the property of its rightful owner. Permission is granted to download and print the materials on this website for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Presentation Transcript
slide1. Way forward for FS_eNPN_Ph2 KI#1 Ericsson (Rapporteur)<br>
slide2. Background KI#1 S2-2205796 proposes evaluation and conclusion for KI#1, but there is an open issue for which the P-CR includes two options as how to move forward i.e. open issue is:
It is FFS whether equivalent SNPNs, with different SNPN IDs, within an RA is to be part of the normative work
Option 1
Equivalent SNPNs, with different SNPN IDs, within an RA is supported by extensions to NAS and NGAP. Furthermore, the SNPN IDs in the Equivalent SNPNs should be unique (e.g. by using Coordinated assignment mode) to ensure the Equivalent SNPN within RA could work for the UE.
Option 2
Equivalent SNPNs, with different SNPN IDs, within an RA is not supported for SNPNs.
The new WID in S2-2205806 includes normative work for KI#1, and above issue is kept open in an editor’s note in the WID.<br>
slide3. KI#1 It is FFS whether equivalent SNPNs, with different SNPN IDs, within an RA is to be part of the normative work
Option 1 in S2-2205796
Equivalent SNPNs, with different SNPN IDs, within an RA is supported by extensions to NAS and NGAP. Furthermore, the SNPN IDs in the Equivalent SNPNs should be unique (e.g. by using Coordinated assignment mode) to ensure the Equivalent SNPN within RA could work for the UE.
Option 2 in S2-2205796
Equivalent SNPNs, with different SNPN IDs, within an RA is not supported for SNPNs.
It is proposed to have a SoH on:
Q1: Can Option 1 be agreed?
Yes:
No:
Q2: Can Option 2 be agreed?
Yes:
No:<br>
slide2. Background KI#1 S2-2205796 proposes evaluation and conclusion for KI#1, but there is an open issue for which the P-CR includes two options as how to move forward i.e. open issue is:
It is FFS whether equivalent SNPNs, with different SNPN IDs, within an RA is to be part of the normative work
Option 1
Equivalent SNPNs, with different SNPN IDs, within an RA is supported by extensions to NAS and NGAP. Furthermore, the SNPN IDs in the Equivalent SNPNs should be unique (e.g. by using Coordinated assignment mode) to ensure the Equivalent SNPN within RA could work for the UE.
Option 2
Equivalent SNPNs, with different SNPN IDs, within an RA is not supported for SNPNs.
The new WID in S2-2205806 includes normative work for KI#1, and above issue is kept open in an editor’s note in the WID.<br>
slide3. KI#1 It is FFS whether equivalent SNPNs, with different SNPN IDs, within an RA is to be part of the normative work
Option 1 in S2-2205796
Equivalent SNPNs, with different SNPN IDs, within an RA is supported by extensions to NAS and NGAP. Furthermore, the SNPN IDs in the Equivalent SNPNs should be unique (e.g. by using Coordinated assignment mode) to ensure the Equivalent SNPN within RA could work for the UE.
Option 2 in S2-2205796
Equivalent SNPNs, with different SNPN IDs, within an RA is not supported for SNPNs.
It is proposed to have a SoH on:
Q1: Can Option 1 be agreed?
Yes:
No:
Q2: Can Option 2 be agreed?
Yes:
No:<br>