[{"name":"S1-193090","title":"Draft reply LS on NPN clarifications","source":"Qualcomm Incorporated","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS out","for":"","abstract":"It is proposed to answer:\nOverall, SA1 cannot provide an exact quantitative answer to SA1\u2019s question. One general guideline, based on the above considerations, would be that the number of CAG Identifiers to be supported (per PLMN per UE) can be in the order of a few dozens.","secretary_remarks":"","agenda_item_sort_order":48,"ainumber":"4.3","ainame":"LS on Non-Public Networks","tdoc_agenda_sort_order":3215000,"status":"revised","reservation_date":"2019-11-08 11:10:18","uploaded":"2019-11-08 22:35:50","revisionof":"","revisedto":"S1-193459","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910803","lsto":"SA2, RAN3","Cc":"RAN2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_88_Reno\/Docs\/S1-193090.zip","group":"S1","meeting":"S1-88","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-193158","title":"Number of CAG Identifiers per PLMN per UE","source":"Deutsche Telekom","contact":"Vasil Aleksiev","contact-id":63195,"tdoctype":"discussion","for":"Agreement","abstract":"SA2 has send a LS with question on the number of CAG Identifiers per PLMN per UE.\nIt is proposed to answer that there is no need to have more than 20 positions in the Allowed CAG list per PLMN per UE.","secretary_remarks":"","agenda_item_sort_order":48,"ainumber":"4.3","ainame":"LS on Non-Public Networks","tdoc_agenda_sort_order":315800,"status":"noted","reservation_date":"2019-11-08 18:10:30","uploaded":"2019-11-08 21:50:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"cyberCAV"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_88_Reno\/Docs\/S1-193158.zip","group":"S1","meeting":"S1-88","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-193215","title":"Reply LS on clarifications on Private Networks","source":"S2-1910803","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"The question for SA1 is Q2:\nQ2: should we consider the case that the size of the UE allowed CAG ID could be so large that the AMF may need to filter it based on the CAG IDs supported in the (registration) area where UE is located?\nSA2 Answer: SA2 assumes that RAN3 is referring to the AMF signaling a UE's Allowed CAG list to NG-RAN as part of the Mobility Restrictions. As per current Stage 2 specifications, SA2 does not assume AMF to perform any filtering.\nHowever, SA2 invites SA1 to provide additional guidance on the number of CAG Identifiers per PLMN per UE to be supported.","secretary_remarks":"","agenda_item_sort_order":48,"ainumber":"4.3","ainame":"LS on Non-Public Networks","tdoc_agenda_sort_order":309000,"status":"noted","reservation_date":"2019-11-26 11:04:30","uploaded":"2019-11-26 11:07:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_88_Reno\/Docs\/S1-193215.zip","group":"S1","meeting":"S1-88","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-193459","title":"LS to SA2, RAN3 (cc RAN2) on NPN clarifications","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"","abstract":"The LS clarifies several aspects of private networks and CAG Identifiers.","secretary_remarks":"","agenda_item_sort_order":48,"ainumber":"4.3","ainame":"LS on Non-Public Networks","tdoc_agenda_sort_order":3215010,"status":"revised","reservation_date":"2019-11-26 11:06:37","uploaded":"2019-11-26 11:07:55","revisionof":"S1-193090","revisedto":"S1-193524","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910803","lsto":"SA2, RAN3","Cc":"RAN2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_88_Reno\/Docs\/S1-193459.zip","group":"S1","meeting":"S1-88","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-193520","title":"CAG definition and related requirements","source":"Deutsche Telekom","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"The CR introduces CAG definition and related requirements.","secretary_remarks":"","agenda_item_sort_order":48,"ainumber":"4.3","ainame":"LS on Non-Public Networks","tdoc_agenda_sort_order":3520000,"status":"noted","reservation_date":"2019-11-26 11:07:17","uploaded":"2019-11-26 11:07:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":22.261,"crspecversion":"16.9.0","workitem":[{"winame":"TEI16"}],"crnumber":433.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_88_Reno\/Docs\/S1-193520.zip","group":"S1","meeting":"S1-88","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-193524","title":"LS to SA2, RAN3 (cc RAN2, SA3) on NPN clarifications","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"","abstract":"It now states: \"SA1 cannot provide an exact quantitative answer to the SA2\u2019s question, since SA1 specifications do not define a maximum number of PNI-NPNs (per PLMN per UE). An estimation would be in the order of a few dozens.\"","secretary_remarks":"","agenda_item_sort_order":48,"ainumber":"4.3","ainame":"LS on Non-Public Networks","tdoc_agenda_sort_order":3215020,"status":"revised","reservation_date":"2019-11-26 11:07:22","uploaded":"2019-11-26 11:07:56","revisionof":"S1-193459","revisedto":"S1-193594","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910803","lsto":"SA2, RAN3","Cc":"RAN2, SA3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_88_Reno\/Docs\/S1-193524.zip","group":"S1","meeting":"S1-88","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-193594","title":"LS to SA2, RAN3 (cc RAN2, SA3) on NPN clarifications","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":48,"ainumber":"4.3","ainame":"LS on Non-Public Networks","tdoc_agenda_sort_order":3215021,"status":"revised","reservation_date":"2019-11-26 11:08:21","uploaded":"2019-11-26 11:17:54","revisionof":"S1-193524","revisedto":"S1-193605","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910803","lsto":"SA2, RAN3","Cc":"RAN2, SA3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_88_Reno\/Docs\/S1-193594.zip","group":"S1","meeting":"S1-88","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-193605","title":"LS to SA2, RAN3 (cc RAN2, SA3) on NPN clarifications","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"","abstract":"","secretary_remarks":"","agenda_item_sort_order":48,"ainumber":"4.3","ainame":"LS on Non-Public Networks","tdoc_agenda_sort_order":3215022,"status":"agreed","reservation_date":"2019-11-26 11:08:25","uploaded":"2019-11-26 11:17:54","revisionof":"S1-193594","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910803","lsto":"SA2, RAN3","Cc":"RAN2, SA3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_88_Reno\/Docs\/S1-193605.zip","group":"S1","meeting":"S1-88","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]