[{"name":"S1-204008","title":"Reply LS to SA2 on Use Cases for providing IMS services to SNPN","source":"Ericsson, Vivo","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"A1: This scenario is covered by the requirement from 3GPP TS 22.261, chapter 6.25.2:\/\/A2: 3GPP TS 22.228 has a requirement that 5G system shall be able to support IMS in non-public networks. It also illustrates some of the possible deployment scenarios for IMS but this is not an exhaustive list, so SA1 do not have a limitation in the number of variants for IMS authentication\/IMS identifiers.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-10-30 09:08:16","uploaded":"2020-11-03 18:05:10","revisionof":"","revisedto":"S1-204381","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204008.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204028","title":"Reply LS on MINT requirements (C1-206649)","source":"LG Electronics Inc.","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"LG's proposed answers are:\/\/Q1: all services should be supported.\/\/Q2: yes\/\/Q3: yes","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-02 03:54:36","uploaded":"2020-11-03 01:55:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204028.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204029","title":"Rel-18 CR to 22.011 on network selection for PLMN and NPN","source":"LG Electronics Inc.","contact":"SungDuck Chun","contact-id":30755,"tdoctype":"CR","for":"Agreement","abstract":"Related to incoming LS S2-2006030. This contibution is proposal for Rel-18.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"available","reservation_date":"2020-11-02 03:54:36","uploaded":"2020-11-03 01:55:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":22.011,"crspecversion":"17.2.0","workitem":[{"winame":"TEI"}],"crnumber":316.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204029.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204032","title":"LS on FRMCS Evolution","source":"Union Inter. Chemins de Fer","contact":"Alain Sultan","contact-id":10343,"tdoctype":"other","for":"Discussion","abstract":"LS from UIC FRMCS Steering Committee to TSG SA and WG SA1 on FRMCS Evolution\/\/SA and SA1 are asked to consider the aspects on FRMCS evolutions presented here and inform UIC if SA can perform the study as appropriate.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-02 09:14:23","uploaded":"2020-11-03 17:15:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":22.989,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204032.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204068","title":"Discussion Paper on credentials for SNPN service continuity","source":"Deutsche Telekom AG","contact":"Alain Sultan","contact-id":10343,"tdoctype":"discussion","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-02 16:58:28","uploaded":"2020-11-03 08:16:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204068.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204069","title":"Reply LS to SA2 on credentials for SNPN service continuity","source":"Deutsche Telekom AG","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answers:\/\/A1: No, there are no requirements for access to services provided by another (e.g. home) SNPN. As such, there are no requirements for service continuity, either.\/\/A2: Yes, only PLMN credentials can be used to register to target networks including SNPNs and PLMNs.\/\/A3: Yes for target SNPNs only.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-02 17:01:45","uploaded":"2020-11-03 08:16:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204069.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204070","title":"Reply LS to CT1 (cc SA3) on MuDe functionality","source":"vivo Mobile Com. (Chongqing)","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to see the CR in 4071.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-02 17:26:27","uploaded":"2020-11-03 21:28:27","revisionof":"","revisedto":"S1-204380","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204070.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204071","title":"Clarification on MuDE activation \/ deactivation","source":"vivo Mobile Com. (Chongqing)","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"The CR adds requirements to explicity state that an authorised user may modify the status of an indentity on another UE.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-02 17:42:27","uploaded":"2020-11-03 21:28:27","revisionof":"","revisedto":"S1-204328","release":"Rel-17","crspec":22.173,"crspecversion":"17.1.0","workitem":[{"winame":"MuDE"}],"crnumber":131.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204071.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204072","title":"Discussion paper on extending PLMN selection to include SNPN selection for UEs with a PLMN subscription","source":"Deutsche Telekom AG, LG Electronics","contact":"Alain Sultan","contact-id":10343,"tdoctype":"discussion","for":"Discussion","abstract":"Discussion to clarify why PLMN selection extention is not needed in Rel17","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-02 17:43:40","uploaded":"2020-11-03 17:36:31","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204072.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204073","title":"reply LS to SA2 on extending PLMN selection to include SNPN selection for UEs with a PLMN subscription","source":"Deutsche Telekom AG","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed Answer:\/\/SA1 has discussed under Rel16 extending the PLMN selection to also support SNPN selection and concluded it is not needed. In Rel17 work on further enhancements on NPN did not include PLMN selection optimizations to include SNPN selection for UEs with a PLMN subscription. \/\/SA1 may consider further alignment gaps, or potential new requirements in a future release.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-02 17:50:56","uploaded":"2020-11-03 17:36:31","revisionof":"","revisedto":"S1-204382","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204073.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204079","title":"reply LS to CT1 on high priority service exempt from release due to SOR","source":"Nokia, Nokia Shanghai Bell","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Nokia proposes to answer respectively \"yes\" and, on the 2nd part, provides a CR to clarify the requirement.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-02 21:13:48","uploaded":"2020-11-03 17:09:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204079.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204080","title":"Clarification of high priority service for Steering of Roaming","source":"Nokia, Nokia Shanghai Bell","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-02 21:15:59","uploaded":"2020-11-03 17:09:55","revisionof":"","revisedto":"","release":"Rel-17","crspec":22.261,"crspecversion":"17.4.0","workitem":[{"winame":"SMARTER_Ph2"}],"crnumber":477.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204080.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204142","title":"Reply LS to SA2 on use cases for providing IMS services to SNPN","source":"China Mobile Com. Corporation","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"A1: Yes, this requirement can be covered by the following in TS 22.261 chapter 6.25.2:\/\/A2: Regarding the scenario, SA1 does not have limitation on the IMS authentication\/IMS identifiers.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 06:33:51","uploaded":"2020-11-03 09:29:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204142.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204143","title":"reply LS to SA2 on SNPN determination on the PLMN subscription","source":"China Mobile Com. Corporation","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed China Mobile's answer:\/\/The current stage-1 requirements do not cover this scenario. However, SA1 has agreed that the 5G system should support either the PLMN or the NPN to indicate to the UE with both PLMN and NPN subscriptions to select a different network from the one that the UE is currently registered. The corresponding requirement is added to TS 22.261 as follows:\/\/\/\/Subject to an agreement between the operators and service providers, operator policies and the regional or national regulatory requirements, the 5G system shall support for non-public network subscribers to use PLMN subscriptions instructed by a non-public network, or to use non-public network subscriptions instructed by a PLMN for network selection.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 06:54:47","uploaded":"2020-11-03 09:29:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204143.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204144","title":"Addition of NPN determination on the PLMN subscription","source":"China Mobile Com. Corporation","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 07:03:08","uploaded":"2020-11-03 09:29:07","revisionof":"","revisedto":"","release":"Rel-17","crspec":22.261,"crspecversion":"17.4.0","workitem":[{"winame":"FS_eNPN"}],"crnumber":485.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204144.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204146","title":"reply LS to SA2 on credentials for SNPN service continuity","source":"China Mobile Com. Corporation","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"China Mobile's proposed answers are:\/\/A1: Yes.\/\/A2: According to TS 22.261, clause 6.25 and 8.3, only PLMN credentials can be used to register to a PLMN. Both PLMN credential and non-3GPP identities and credentials can be used to register to a non-public network (so: \"yes\" in some cases).\/\/A3: Non-3GPP identities and credentials can only be used to register to a non-public network. (so: \"yes\" in some cases)","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 07:18:55","uploaded":"2020-11-03 09:29:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204146.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204180","title":"Reply LS to SA2 on SNPN determination on the PLMN subscription to use for PLMN","source":"Ericsson LM","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"A1: Yes, SA1 has a requirement that allows a PLMN to update the subscription of an authorized UE in order to allow the UE to connect to a desired NPN, which means that the PLMN can instruct the UE to use a SNPN subscription to select an SNPN, (i.e. the second bullet above).\/\/Regarding the first bullet, SA1 do not have a Rel-17 requirement for allowing a SNPN to do a similar activity. SA1 would like to inform SA2 that is has an agreed Rel-18 TR for Localized Services that might study this scenario.\/\/A2: The stage 1 requirement listed above is not limited to the home network.\/\/A3: SA1 do not have a requirement for this scenario in Rel-17.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 13:31:34","uploaded":"2020-11-03 18:05:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204180.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204186","title":"Clarification of a steering of roaming requirement","source":"NTT DOCOMO","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-03 13:41:51","uploaded":"2020-11-03 14:12:02","revisionof":"","revisedto":"S1-204377","release":"Rel-17","crspec":22.261,"crspecversion":"17.4.0","workitem":[{"winame":"eCPSOR_CON"}],"crnumber":488.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204186.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204187","title":"Clarification of a steering of roaming requirement","source":"NTT DOCOMO","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-03 13:41:52","uploaded":"2020-11-03 14:12:02","revisionof":"","revisedto":"S1-204378","release":"Rel-18","crspec":22.261,"crspecversion":"18.0.0","workitem":[{"winame":"eCPSOR_CON"}],"crnumber":489.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204187.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204188","title":"Reply LS to SA2 on extending PLMN selection to include SNPN selection for UEs with a PLMN subscription","source":"Ericsson LM","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Answer: Based on the above description, SA1 do not have any requirements in Rel-17 for extending PLMN selection to also support SNPN selection for the scenario where PLMN subscription is used with 3GPP identifiers and credentials.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 13:48:12","uploaded":"2020-11-03 18:05:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204188.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204189","title":"Reply LS to SA2 on credentials for SNPN service continuity","source":"Ericsson LM","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"A1: Based on the above requirement it shall be supported to access PLMN service via a non-public network (and vice versa) but there is no similar requirement for access to service in an SNPN separate to the serving SNPN.\/\/A2: Only PLMN credentials can be used to register to a target network in order to achieve service continuity for a PDU session anchored in a PLMN. Non-3GPP identities and credentials can only be used for SNPNs and there is no requirement to access a SNPN via another serving SNPN (as answered for Q1) and also there is no requirement in 22.261 that enables the usage of SNPN credentials to access a PLMN network (for the scenario that UE moves from SNPN to PLMN using non-3GPP credentials). This implies that there is no scenario where non-3GPP identities can be used to register to a target network in order to achieve service continuity for a PDU session anchored in a SNPN. \/\/A3: No (see A2).","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 13:56:23","uploaded":"2020-11-03 18:05:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204189.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204212","title":"Addition of new Core Network RAT types for satellite access","source":"TNO, Thales","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"This CR adds the new core network RAT types for satellite access to the list of access type identifiers examples.\/\/The CR adds \"NR(LEO), NR(MEO), NR(GEO), NR(OTHERSAT),\" to the sentence: \"It shall be possible to have an associated Access Technology identifier e.g., N G-RAN, \"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 16:02:35","uploaded":"2020-11-03 17:42:23","revisionof":"","revisedto":"","release":"Rel-17","crspec":22.011,"crspecversion":"17.2.0","workitem":[{"winame":"TEI17"}],"crnumber":317.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204212.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204213","title":"Reply LS to SA2 on extending PLMN selection to include SNPN selection for UEs with a PLMN subscription","source":"Intel","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Intel's approach is to add the requirement for Rel-17.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 16:18:06","uploaded":"2020-11-03 22:40:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204213.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204214","title":"Clarification of network selection for PLMN or NPN","source":"Intel","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"This CR:\/\/- adds reference to TS 22.261 where it provides the service requirements for non-public network\/\/- adds the abbreviation of non-public network (NPN)\/\/- clarifies that PLMN selection includes both PLMN and NPN selection","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 16:20:53","uploaded":"2020-11-03 22:40:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":22.011,"crspecversion":"17.2.0","workitem":[{"winame":"TEI17"}],"crnumber":318.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204214.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204215","title":"Reply LS to SA2 on credentials for SNPN service continuity","source":"Intel","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answers:\/\/A1: Yes, service continuity shall be supported.\/\/At this meeting, SA1 has agreed the attached CR (from Rel-16 onward) adding a new requirement on credentials for SNPN service continuity.\/\/A2: Service continuity when UE moves between PLMN and NPN coverage shall be supported for UE with only PLMN subscription.\/\/A3: Service continuity when UE moves between PLMN and NPN coverage shall be supported for UE with only PLMN subscription.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 16:22:48","uploaded":"2020-11-03 22:40:47","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204215.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204216","title":"Clarification for credentials for SNPN service continuity","source":"Intel","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-03 16:24:50","uploaded":"2020-11-03 22:40:47","revisionof":"","revisedto":"S1-204291","release":"Rel-17","crspec":22.261,"crspecversion":"17.4.0","workitem":[{"winame":"TEI17"}],"crnumber":491.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204216.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204218","title":"Reply LS to CT1 (cc SA2) on New satellite radio access technologies for PLMN selection","source":"TNO","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answers:\/\/Q1: no (added by the CR).\/\/Q2: left to SA2.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 16:28:35","uploaded":"2020-11-03 22:29:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204218.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204250","title":"Draft LS to CT1 reply on services exempt from release due to SOR","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Qualcomm proposes to answer \"yes\" and, for the 2nd part, they clarify that a user should be able to configure the UE to set preferences about which services should not be interrupted by SOR, including e.g. MMTEL voice\/video.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 19:19:44","uploaded":"2020-11-03 22:57:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204250.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204251","title":"Draft LS to CT1 (cc SA2) reply on MINT requirements","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Qualcomm's proposed answers are:\/\/Q1: full set of services\/\/Q2: NA\/\/Q3: yes","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-03 19:20:55","uploaded":"2020-11-03 22:57:43","revisionof":"","revisedto":"S1-204329","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204251.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204252","title":"Draft LS to CT1 (cc SA2, RAN2) reply on Satellite RAT for PLMN-RAT selection","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answers:\/\/Q1: it should be \"yes\" (added by the CR).\/\/Q2: not clear at this stage. Given the above, SA1 agreed CR assumes that there is no need for further granularity of satellites RAT prioritization for PLMN selection.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-03 19:22:03","uploaded":"2020-11-03 22:57:43","revisionof":"","revisedto":"S1-204379","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA2, RAN2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204252.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204253","title":"Discussion on Satellite RAT for PLMN selection","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"other","for":"Discussion","abstract":"This introduces the CR 4254.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 19:23:55","uploaded":"2020-11-03 22:57:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204253.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204254","title":"Satellite access RAT identifier for PLMN selection","source":"Qualcomm","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"Here, only \"satellite NG-RAN\" is added, without distinction LEO\/MEO\/GEO\/etc.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-03 19:27:35","uploaded":"2020-11-03 22:57:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":22.011,"crspecversion":"17.2.0","workitem":[{"winame":"TEI17"}],"crnumber":319.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-201029","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204254.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204256","title":"Draft LS to SA2 reply on SNPN selection","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"SA1 agreed to extend PLMN selection requirements to also support SNPN selection using a PLMN subscription with 3GPP identifiers and credentials, as per attached CR.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 20:26:23","uploaded":"2020-11-03 23:10:22","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204256.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204257","title":"Considerations on SNPN selection for UEs with PLMN subscription","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"other","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 20:28:00","uploaded":"2020-11-03 23:10:22","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204257.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204258","title":"Requirements on SNPN selection for UEs with PLMN subscription","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 20:34:50","uploaded":"2020-11-03 23:10:22","revisionof":"","revisedto":"","release":"Rel-17","crspec":22.011,"crspecversion":"17.2.0","workitem":[{"winame":"TEI17"}],"crnumber":320.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204258.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204259","title":"Draft LS to SA2 reply on providing IMS services to SNPN","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Qualcomm's proposed answer is different since they propose to answer that \"there are no service requirements supporting those specific scenarios and use cases.\"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-03 20:36:05","uploaded":"2020-11-03 22:57:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204259.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204260","title":"Draft LS to SA2 reply on SNPN subscription for PLMN selection","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answers:\/\/A1: No, there are no service requirements related to the described scenario and options. Q2 and Q3, therefore. do not apply.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-03 20:38:57","uploaded":"2020-11-03 22:57:43","revisionof":"","revisedto":"S1-204344","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204260.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204261","title":"Draft LS reply on credentials for SNPN service continuity","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2020-11-03 20:44:14","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204266","title":"[DRAFT] Reply LS to CT1 on high priority service exempt from release due to SOR","source":"NTT DOCOMO INC.","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"DoCoMo answers \"yes\" and \"That is possible: Interruption of e.g. MMTEL voice\/video is based on HPLMN policy and user subscription. See the related CRs.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"revised","reservation_date":"2020-11-03 22:11:27","uploaded":"2020-11-03 22:18:08","revisionof":"","revisedto":"S1-204376","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204266.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204274","title":"LS on high priority service exempt from release due to SOR","source":"C1-204941","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"CT1 asking confirmation about what is meant by \"a UE engaged in high priority service\" and What are \u201cother sessions defined by the user to be of high priority?\u201d Do those sessions include MMTEL voice\/video calls or SMS?","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204274.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204275","title":"New satellite radio access technologies for PLMN selection","source":"C1-206507","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"CT1 ask the following questions to SA1:\/\/Q1: Is there a service requirement to differentiate between \u201cNG-RAN\u201d and \u201csatellite access to 5GC\" for the purpose of PLMN selection?\/\/Q2: Does SA1 intend to introduce new associated Access Technology identifier(s) for \"satellite access\" for the Operator Controlled PLMN Selector list and a User Controlled PLMN Selector list (stored on the SIM\/USIM card). If yes, how many different identifiers?","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204275.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204276","title":"LS on MuDe functionality","source":"C1-206625","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"CT1 has started working on the Rel-17 functionality for multi-device and multi-identity enhancements and requires clarification on the following issues:\/\/1) Is it a requirement for a user to be able to from one of its UEs (UEa) activate or deactivate an identity on another of its UEs (UEb)?\/\/2) If the answer to 1) is yes, what is the granularity of the activation, is it sufficient to deactivate all identities at UEb, e.g. to avoid a forgotten phone to ring.\/\/3) What is the impact on a session in progress when a public user identity is deactivated (e.g. terminated, modified, maintained, etc.)?\/\/4) Should the activation \/ deactivation of the identity impact both mobile originated and mobile terminated services?","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204276.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204277","title":"LS on MINT (Minimization of service Interruption) requirements","source":"C1-206649","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"3 questions from CT1 to SA1:\/\/Q1: Which level of services are the PLMNs not subject to disaster required to provide to \u201cDisaster Inbound Roamers\u201d? Emergency services only, a limited set of services hosted by the PLMN not subject to disaster, or the same set of services that the \u201cDisaster Inbound Roamers\u201d would receive in their HPLMN?\/\/Q2: If the answer to Q1 is: a limited set of services, can it be assumed that the NFs of the PLMM subject to disaster required to support those services (the UDM and the AUSF) are still operational?\/\/Q3: If the answer to Q1 is: the same set of services, can it be assumed that the NFs of the PLMM subject to disaster required to support those services (the UDM, the AUSF, the SMF and UPF for any DNN requiring home-routed PDU session, and the IMS) are still operational?","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204277.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204278","title":"Reply LS on 3GPP NR Rel-16 URLLC and IIoT performance evaluation","source":"RP-202097","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204278.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204279","title":"Reply LS on human-readable network name (HRNN)","source":"S2-2005911","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 has received the CT's LS on \"human-readable network name (HRNN)\" and SA1's reply.\/\/SA2 has discussed the CT LS and agreed to let SA1 take the lead in responding to the CT1 question. SA2 will update its specifications accordingly.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204279.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204280","title":"LS on Use Cases for providing IMS services to SNPN","source":"S2-2006029","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 asks SA1 the following:\/\/Q1: Whether there are service requirement where the SNPN can have an SLA agreement with a third party (different Administrative Domain) IMS provider to provide IMS services.\/\/Q2: For the scenario where the SNPN provides the IMS network, if there is need to consider additional variants regarding the IMS authentication\/IMS identifiers similar to what exists today.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204280.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204281","title":"LS on extending PLMN selection to include SNPN selection for UEs with a PLMN subscription","source":"S2-2006030","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 ask SA1 to clarify whether PLMN selection can be extended to also support SNPN selection using a PLMN subscription with 3GPP identifiers and credentials and if so, to specify the respective requirements for that.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204281.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204282","title":"LS on credentials for SNPN service continuity","source":"S2-2007828","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 ask the following questions to SA1: \/\/Q1: is there a requirement to support for access to (and related service continuity) for services provided by an SNPN separate from the serving SNPN (i.e. services provided by the SNPN that issued the UE's subscription). \/\/If yes, then 2 more questions: \/\/Q2: whether only PLMN credentials (and respective authentication methods) can be used to register to a target network (i.e. which may be an SNPN with or without credentials being owned by separate entities, or a PLMN), given the various service continuity scenarios.\/\/Q3: whether in addition to PLMN credentials, also non-3GPP identities and credentials (and respective alternative authentication methods) can be used to register to a target network, given the various service continuity scenarios.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204282.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204283","title":"LS on Use of Survival Time for Deterministic Applications in 5GS","source":"S2-2007880","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204283.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204284","title":"LS on SNPN determination on the PLMN subscription to use for PLMN selection","source":"S2-2007959","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"SA2 ask SA1 whether any related requirements exist: \/\/Q1: Assuming the UE has both subscription of one or more PLMNs and one or more SNPNs, is there a current stage 1 requirement to \/\/- Allow an SNPN to instruct the UE to use a PLMN subscription to select a PLMN for VIAPA?\/\/- Allow a PLMN to instruct the UE to use a SNPN subscription to select an SNPN for VIAPA? \/\/Q2: If the answer to Q1 is yes, is the above action limited to the Home network?\/\/Q3: If the answer to Q1 is yes, does it also involve the user to decide whether to reselect the PLMN for VIAPA service?","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204284.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204285","title":"Clarifications on LI requirements applicable to FS_PALS","source":"S3i200625","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"SA3-LI asks SA1 to ensure the lawful interception requirements will also apply and be met in FS_PALS (5G Networks Providing Access to Localized Services).","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204285.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204286","title":"Reply LS on request for information from IALA","source":"SP-200877","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204286.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204287","title":"LS on Rel-17 schedule","source":"SP-200888","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"SA acknowledges that the current Rel-17 Stage 2 freeze date (i.e. Dec 2020) is unrealistic and agrees that a shift in stage-2 freeze dates is required. \/\/The decision on new Rel-17 Stage-2 freeze dates will be taken at SA#90-e as part of the discussion on the overall Rel-17 timeline, in coordination with RAN and CT.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204287.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204288","title":"LS response to TCCA on Public Safety","source":"GSMA 5GJA14_121","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204288.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204289","title":"Support of UAVs in 3GPP system and interfacing with USS\/UTM","source":"GSMA ACJA","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS in","for":"Discussion","abstract":"GSMA informs that Aerial Connectivity Joint Activity (ACJA) is the first initiative to result from the cooperation agreement signed last year by the GSMA and the Global UTM Association (GUTMA)1.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-04 08:53:17","uploaded":"2020-11-04 09:23:46","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_92_Electronic_Meeting\/Docs\/S1-204289.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204290","title":"[DRAFT] LS to CT1 (SA2, RAN3) on Satellite RATs for PLMN selection","source":"Thales S.A. [SA1]","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2020-11-23 16:34:33","uploaded":"2020-11-24 10:07:06","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA2, RAN3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204290.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204291","title":"Clarification for credentials for SNPN service continuity","source":"Intel","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"Replaces S1-204216","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-23 16:34:33","uploaded":"2020-11-24 10:05:59","revisionof":"S1-204216","revisedto":"","release":"Rel-17","crspec":22.261,"crspecversion":"17.4.0","workitem":[{"winame":"TEI17"}],"crnumber":491.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204291.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204294","title":"LS to UIC on FRMCS Evolution","source":"Union Inter. Chemins de Fer","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Proposed answer to S1-204032","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2020-11-23 16:34:37","uploaded":"2020-11-24 10:05:59","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"UIC","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204294.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204325","title":"LS on Clarification on problematic UAV","source":"S6-202227","contact":"Alain Sultan","contact-id":10343,"tdoctype":"other","for":"Discussion","abstract":"Q1: From a general perspective, any UAV\/UAV controller deviating from its expected operations is a problematic UAV. What is the definition of a \u201cproblematic UAV\/UAV Controller\u201d in a 3GPP context?\/\/Q2: Are there specific use cases or examples of data needed to be exchanged between the UTM and the 3GPP system for this requirement?","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"postponed","reservation_date":"2020-11-23 16:34:46","uploaded":"2020-11-24 10:08:39","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_92_Electronic_Meeting\/Docs\/S1-204325.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204326","title":"[DRAFT] Reply LS to SA6 (cc SA2, ACJA) on clarification on problematic UAV","source":"Qualcomm","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"QC prop answer to S1-204325: \/\/A1: In SA1, the concept of a \u201cproblematic UAV\u201d was intended to cover a UAV which is a UAV flying without successful authorization from UTM.\/\/A2: Originally the use case was for an MNO to identify a UAS which may seek to operate without initial authorization from the UTM. In addition, a UAS may attempt to avoid detection from the 3GPP system and being identified as UAS-capable UE. For instance, the UAV may embed a terrestrial 3GPP UE and identify as a regular 3GPP UE (rather than a UAS-capable UE).\/\/\/\/The 3GPP system may expose existing 3GPP system information towards the UTM via existing mechanisms such as NEF in order to help the UTM identify problematic UAV and UAV controllers. Please see clause 6.2 of TS 22.125 for further requirements.\/\/SA1 has no requirements on the 3GPP system receiving data from the UTM in order for the 3GPP system to identify problematic UAV or UAV controllers.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-23 16:34:46","uploaded":"2020-11-24 10:08:39","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204326.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204327","title":"[DRAFT] Reply LS to SA6 (cc SA2) on clarification on problematic UAV","source":"Samsung","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Samsung prop answer to S1-204325:\/\/A1: From 3GPP\u2019s perspective, any UAV\/UAV controller deviating from its expected operations (for the events monitored on the 3GPP system exposes to the UTM) is a problematic UAV. \/\/In SA1, the concept of a \u2018problematic UAV\u2019 was intended to cover a UAV which is flying without successful authorization from the UTM. SA1 also studied the case of a UAV deviating from its expected Location and geo-fence. While it is possible that other conditions known to the 3GPP System could constitute problems, this can only be determined by the UTM.\/\/A2: Originally the use case was for an MNO to identify a UAS which may seek to operate without initial authorization from the UTM. In addition, a UAS may attempt to avoid detection from the 3GPP system and be identified as a UAS-capable UE. For instance, the UAV may embed a terrestrial 3GPP UE and identify as a regular 3GPP UE (rather than a UE with a UAS-capable UE).\/\/There may be additional information that the 3GPP System can expose that would be useful to the UTM to determine whether a given UAV operates problematically. There are general stage 1 requirements for network exposure in 22.261, 6.10.2. It is up to SA6 to determine how to expose additional information to the UTM.","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2020-11-23 16:34:46","uploaded":"2020-11-24 10:08:39","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204327.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204328","title":"Clarification on MuDE activation \/ deactivation","source":"Vivo","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"Revision of S1-204071","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:34:46","uploaded":"2020-11-24 10:08:39","revisionof":"S1-204071","revisedto":"","release":"Rel-17","crspec":22.173,"crspecversion":"17.1.0","workitem":[{"winame":"MuDE"}],"crnumber":131.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-201026","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204328.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204329","title":"Draft LS reply on MINT requirements","source":"Qualcomm","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Revision of S1-204251","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:34:48","uploaded":"2020-11-24 10:08:39","revisionof":"S1-204251","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204329.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204344","title":"LS to SA2 reply on SNPN subscription for PLMN selection","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Revision of S1-204260","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:34:50","uploaded":"2020-11-24 10:08:39","revisionof":"S1-204260","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204344.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204376","title":"Reply LS to CT1 on high priority service exempt from release due to SOR","source":"NTT DOCOMO INC.","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Replaces S1-204266","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:35:04","uploaded":"2020-11-24 10:10:25","revisionof":"S1-204266","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204376.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204377","title":"Clarification of a steering of roaming requirement","source":"NTT DOCOMO","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"Replaces S1-204186","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:35:04","uploaded":"2020-11-24 10:10:25","revisionof":"S1-204186","revisedto":"","release":"Rel-17","crspec":22.261,"crspecversion":"17.4.0","workitem":[{"winame":"eCPSOR_CON"}],"crnumber":488.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-201025","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204377.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204378","title":"Clarification of a steering of roaming requirement","source":"NTT DOCOMO","contact":"Alain Sultan","contact-id":10343,"tdoctype":"CR","for":"Agreement","abstract":"Replaces S1-204187","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:35:06","uploaded":"2020-11-24 10:10:25","revisionof":"S1-204187","revisedto":"","release":"Rel-18","crspec":22.261,"crspecversion":"18.0.0","workitem":[{"winame":"eCPSOR_CON"}],"crnumber":489.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"SP-201025","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204378.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204379","title":"LS to CT1 (cc SA2, RAN) reply on Satellite RAT for PLMN-RAT selection","source":"Qualcomm Incorporated","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Replaces S1-204252","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:35:07","uploaded":"2020-11-24 10:10:25","revisionof":"S1-204252","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA2, RAN2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204379.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204380","title":"Reply LS to CT1 (cc SA3) on MuDe functionality","source":"vivo Mobile Com. (Chongqing)","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Replaces S1-204070","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:35:07","uploaded":"2020-11-24 10:11:18","revisionof":"S1-204070","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT1","Cc":"SA3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204380.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204381","title":"Reply LS to SA2 on Use Cases for providing IMS services to SNPN","source":"Ericsson, Vivo","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Replaces S1-204008","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:35:07","uploaded":"2020-11-24 10:11:18","revisionof":"S1-204008","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204381.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S1-204382","title":"reply LS to SA2 on extending PLMN selection to include SNPN selection for UEs with a PLMN subscription","source":"Deutsche Telekom AG","contact":"Alain Sultan","contact-id":10343,"tdoctype":"LS out","for":"Approval","abstract":"Replaces S1-204073","secretary_remarks":"","agenda_item_sort_order":3,"ainumber":"3","ainame":"Liaison Statements (including related contributions)","tdoc_agenda_sort_order":0,"status":"agreed","reservation_date":"2020-11-23 16:35:07","uploaded":"2020-11-24 10:11:18","revisionof":"S1-204073","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG1_Serv\/TSGS1_92_Electronic_Meeting\/Docs\/S1-204382.zip","group":"S1","meeting":"S1-92-e","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]