[{"name":"S2-2100067","title":"Support of different slices over different Non 3GPP access","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Support the possibility for operators to allocate a TAI per non 3GPP 5G AN (e.g. N3IWF \/ TNGF \/ W-AGF) : each non 3GPP access gateway is locally configured with its own TAI and the slices it supports. The TAI value is provided (as in case of 3GPP access) to AMF over N2 in NG SET UP message. There is one TAI value per non 3GPP access gateway. Different non 3GPP access gateways (e.g. different N3IWF \/ TNGF \/ W-AGF) can thus advertise different TAI values, and can support different slices. As TAI values are not advertised over Non 3GPP access, UE(s) do not need to be aware of the fact that different non 3GPP access gateways may correspond to a different TAI beyond the fact that they (UE) may receive different TAI values within the TAI list sent by the network over successive registration over non 3GPP access.","secretary_remarks":"Revised to S2-2102064.","agenda_item_sort_order":75,"ainumber":"8.21","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":24030,"status":"revised","reservation_date":"2021-01-18 09:17:59","uploaded":"2021-02-18 08:04:05","revisionof":"","revisedto":"S2-2102064","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":2525.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100067.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100068","title":"Support of different slices over different Non 3GPP access","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Support the possibility for operators to allocate a TAI per non 3GPP 5G AN (e.g. N3IWF \/ TNGF \/ W-AGF) : each non 3GPP access gateway is locally configured with its own TAI and the slices it supports. The TAI value is provided (as in case of 3GPP access) to AMF over N2 in NG SET UP message. There is one TAI value per non 3GPP access gateway. Different non 3GPP access gateways (e.g. different N3IWF \/ TNGF \/ W-AGF) can thus advertise different TAI values, and can support different slices. As TAI values are not advertised over Non 3GPP access, UE(s) do not need to be aware of the fact that different non 3GPP access gateways may correspond to a different TAI beyond the fact that they (UE) may receive different TAI values within the TAI list sent by the network over successive registration over non 3GPP access.","secretary_remarks":"Approved","agenda_item_sort_order":75,"ainumber":"8.21","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":24050,"status":"agreed","reservation_date":"2021-01-18 09:18:00","uploaded":"2021-02-18 08:04:05","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":2455.0,"crrevision":"","crcategory":"B","tsg_crp":"SP-210088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100068.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100879","title":"Registration procedure for trusted non-3GPP access with TNGF relocation","source":"Lenovo, Motorola Mobility, Broadcom","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The registration procedure for trusted non-3GPP access is extended, so that TNGF relocation can be supported. The proposed changes do not affect the UE.","secretary_remarks":"CC#3b: will be raised in CC#4 if time permits. CC#4: r07 with modifications agreed. Revised to S2-2101106.","agenda_item_sort_order":75,"ainumber":"8.21","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":24060,"status":"revised","reservation_date":"2021-02-18 14:11:01","uploaded":"2021-02-18 16:18:26","revisionof":"","revisedto":"S2-2101106","release":"Rel-17","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":2577.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100879.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100898","title":"Update to N3IWF selection for N3SLICE","source":"Lenovo, Motorola Mobility","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is specified that if the different N3IWFs in the HPLMN support different TAs and different S-NSSAIs, then the HPLMN provides an N3IWF identifier to UE by taking into account the subscribed S-NSSAIs of the UE. This way, a UE can select an N3IWF in the HPLMN that supports the allowed slices for this UE.","secretary_remarks":"Revised to S2-2102065.","agenda_item_sort_order":75,"ainumber":"8.21","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":24080,"status":"revised","reservation_date":"2021-02-18 14:33:27","uploaded":"2021-02-18 16:18:26","revisionof":"","revisedto":"S2-2102065","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":2662.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100898.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101106","title":"Registration procedure for trusted non-3GPP access with TNGF relocation","source":"Lenovo, Motorola Mobility, Broadcom, Deutsche Telekom, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To mitigate the above issue, it is assumed that, when the trusted non-3GPP access is a trusted WLAN access: The UE is configured (e.g. with the WLANSP rules defined in TS 23.003 [20]) to select an SSID that supports one or more of the UE's subscribed S-NSSAIs for non-3GPP access. Each SSID is associated with one non-3GPP tracking area and one set of S-NSSAIs. The TNAP selects a TNGF based on the realm provided by the UE and also based on the SSID selected by the UE. All TNGFs associated with the SSID selected by the UE support the same non-3GPP tracking area and the same set of S-NSSAIs.","secretary_remarks":"Revision of S2-2100879r07. Approved","agenda_item_sort_order":75,"ainumber":"8.21","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":24070,"status":"agreed","reservation_date":"2021-03-11 07:55:21","uploaded":"2021-03-11 08:21:20","revisionof":"S2-2100879","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":2577.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101106.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102064","title":"Support of different slices over different Non 3GPP access","source":"Nokia, Nokia Shanghai Bell, Deutsche Telecom, Ericsson","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Support the possibility for operators to allocate a TAI per non 3GPP 5G AN (e.g. N3IWF \/ TNGF \/ W-AGF) : each non 3GPP access gateway is locally configured with its own TAI and the slices it supports. The TAI value is provided (as in case of 3GPP access) to AMF over N2 in NG SET UP message. There is one TAI value per non 3GPP access gateway. Different non 3GPP access gateways (e.g. different N3IWF \/ TNGF \/ W-AGF) can thus advertise different TAI values, and can support different slices. As TAI values are not advertised over Non 3GPP access, UE(s) do not need to be aware of the fact that different non 3GPP access gateways may correspond to a different TAI beyond the fact that they (UE) may receive different TAI values within the TAI list sent by the network over successive registration over non 3GPP access.","secretary_remarks":"Revision of S2-2100067r10. Approved","agenda_item_sort_order":75,"ainumber":"8.21","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":24040,"status":"agreed","reservation_date":"2021-03-11 08:08:46","uploaded":"2021-03-11 08:31:27","revisionof":"S2-2100067","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":2525.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2102064.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2102065","title":"Update to N3IWF selection for N3SLICE","source":"Lenovo, Motorola Mobility, Nokia, Nokia Shanghai Bell, AT&T, Deutsche Telekom","contact":"Apostolis Salkintzis","contact-id":22112,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is specified that if the different N3IWFs in the HPLMN support different TAs and different S-NSSAIs, then the HPLMN provides an N3IWF identifier to UE by taking into account the subscribed S-NSSAIs on non-3GPP access for the UE. This way, a UE can select an N3IWF in the HPLMN that supports the subscribed slices on non-3GPP access for this UE.","secretary_remarks":"Revision of S2-2100898r07. Approved","agenda_item_sort_order":75,"ainumber":"8.21","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":24090,"status":"agreed","reservation_date":"2021-03-11 08:08:47","uploaded":"2021-03-11 08:31:27","revisionof":"S2-2100898","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"16.7.0","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":2662.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-210088","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2102065.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]