[{"name":"S2-2200083","title":"LS from CT WG1: LS on lists of 5GS forbidden tracking area for non-3GPP access","source":"CT WG1","contact":"Xingyue Zhou","contact-id":42680,"tdoctype":"LS in","for":"Action","abstract":"Two facts are identified in SA WG2 and CT WG1 respectively as below: 1) In SA WG2, TEI17_N3SLICE introduces a new requirement on TAI configuration for non-3GPP access as excerpted below in clause 5.3.2.3 of TS 23.501: 'TAI(s) dedicated to Non-3GPP access may be defined in a PLMN and apply within this PLMN. Each N3IWF, TNGF, TWIF and W-AGF is locally configured with one TAI value. Each N3IWF, TNGF, TWIF and W-AGF may be configured with a different TAI value or with the same TAI value as other N3IWFs, TNGFs, TWIFs and\/or W-AGFs. The TAI is provided to the AMF during N2 interface setup as described in TS 38.413 [34].' In addition, a NOTE as excerpted below in clause 5.3.4.1.1 of TS 23.501 clarifies: 'NOTE 1: If a TAI (see clause 5.3.2.3) is configured in a N3IWF, TNGF, TWIF or W-AGF and this TAI is forbidden, access via that N3IWF, TNGF, TWIF or W-AGF is forbidden. If a single TAI is configured in all N3IWF, TNGF, TWIF and W-AGF and if this TAI is forbidden in a PLMN, non-3GPP Access is forbidden altogether in this PLMN.' 2) In CT WG1, for lists of 5GS forbidden tracking areas, there is a requirement for the UE that 'Within the 5GS, these lists are managed independently per access type, i.e., 3GPP access or non-3GPP access.' as specified in clause 5.3.13 of TS 24.501. Based on the above, CT WG1 would like to ask SA WG2 the following questions: When each N3IWF, TNGF, TWIF and W-AGF is configured with a different TAI value (or a group of them shares a certain value), and the UE needs to update the list of 5GS forbidden tracking areas if receiving the 5GMM cause #12 'tracking area not allowed' or #13 'roaming not allowed in this tracking area', a) how does the UE know the current TAI for non-3GPP access in order to add this specific TAI into the list of 5GS forbidden tracking areas? and b) does the UE need to keep track of multiple non-3GPP TAIs within the list of 5GS forbidden tracking areas for the non-3GPP access?. Action: CT WG1 kindly asks SA WG2 to provide the answer to the questions above.","secretary_remarks":"Response drafted in S2-2201028. Final response in S2-2201745","agenda_item_sort_order":67,"ainumber":"8.24","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":17090,"status":"replied to","reservation_date":"2022-01-10 14:20:57","uploaded":"2022-01-25 15:36:02","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-220810","lsreply":"S2-2201745","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200083.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200548","title":"Clarification on non-3gpp AN selection","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following change is proposed: It is proposed that N3IWF identifier onfiguration and WLANSP rules should have only information about supported slice of UE's subscribed S-NSSAI","secretary_remarks":"Approved","agenda_item_sort_order":67,"ainumber":"8.24","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":17120,"status":"agreed","reservation_date":"2022-01-28 03:41:08","uploaded":"2022-01-28 10:38:31","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":3518.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220067","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200548.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200549","title":"Clarification on non-3gpp AN selection","source":"Samsung","contact":"Ashok Kumar Nayak","contact-id":90702,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following change is proposed: It is proposed that N3IWF identifier onfiguration and WLANSP rules should have only information about supported slice of UE's subscribed S-NSSAI","secretary_remarks":"Approved","agenda_item_sort_order":67,"ainumber":"8.24","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":17130,"status":"agreed","reservation_date":"2022-01-28 03:43:10","uploaded":"2022-01-28 10:38:50","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":3363.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220067","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200549.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201028","title":"[DRAFT] Reply LS on lists of 5GS forbidden tracking area for non-3GPP access","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-2200083. r05 agreed. Revised to S2-2201745.","agenda_item_sort_order":67,"ainumber":"8.24","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":17100,"status":"revised","reservation_date":"2022-01-28 14:17:44","uploaded":"2022-01-28 15:11:22","revisionof":"","revisedto":"S2-2201745","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201028.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201029","title":"Clarification on TAI configured for Non 3GPP access","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that same RAT-specific TAI is configured in N3IWF, TNGF and TWIF?","secretary_remarks":"r10 agreed. Revised to S2-2201746.","agenda_item_sort_order":67,"ainumber":"8.24","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":17140,"status":"revised","reservation_date":"2022-01-28 14:17:44","uploaded":"2022-01-28 15:11:22","revisionof":"","revisedto":"S2-2201746","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":3556.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201029.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201745","title":"Reply LS on lists of 5GS forbidden tracking area for non-3GPP access","source":"SA WG2","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. Attachments: TS 23.501 CR 3556","secretary_remarks":"Revision of S2-2201028r05. Approved","agenda_item_sort_order":67,"ainumber":"8.24","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":17110,"status":"approved","reservation_date":"2022-03-01 08:31:15","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2201028","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2200083","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201745.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201746","title":"Clarification on TAI configured for Non 3GPP access","source":"ZTE, Nokia, Nokia Shanghai Bell, LG Electronics","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Forbidden Areas are not used for Trusted \/ UnTrusted non 3GPP access?","secretary_remarks":"Revision of S2-2201029r10. Approved","agenda_item_sort_order":67,"ainumber":"8.24","ainame":"Support of different slices over different Non-3GPP access (TEI17_N3SLICE)","tdoc_agenda_sort_order":17150,"status":"agreed","reservation_date":"2022-03-01 08:31:15","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2201029","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"TEI17_N3SLICE"}],"crnumber":3556.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220067","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201746.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]