[{"name":"SP-210275","title":"LS from SA WG1: LS on support of PWS over SNPN","source":"SA WG1","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 has discussed for some time about the lack of service requirements, and stage-2\/3 support, for PWS over SNPN, so far missing in Rel-16 and Rel-17 specs. SA WG1 has identified and discussed impacts of certain PWS regulatory requirements for mobile network deployments in venues or areas with large numbers of users (e.g. football stadiums or campus areas), affecting both PLMN and NPNs. In fact, some regulations (e.g. related to EU\/NL-Alert PWS systems in Europe) indicate that SNPNs with more than e.g. 25000 users will not be exempt from PWS regulations pertaining to public mobile networks. Thus, the lack of SNPN support for PWS would prevent the possibility to deploy a SNPN network in those type of scenarios. Therefore, SA WG1 sees the need to introduce support of PWS over SNPN in Rel-17. Action: SA WG1 would like to inform TSG groups that SA WG1 sees the need to introduce support of PWS over SNPN in Rel-17, and kindly ask to provide any feedback in case proper stage-2\/3 work is deemed not feasible to complete within the Rel-17 timeframe.","secretary_remarks":"Revision of Postponed SP-210019 from SP-91E. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10450,"status":"noted","reservation_date":"2021-04-21 13:38:29","uploaded":"2021-05-03 12:46:50","revisionof":"SP-210019","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1, RAN WG2, RAN WG3, TSG SA, TSG CT, TSG RAN","Cc":"SA WG3","lsoriginalls":"S1-210368","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210275.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210281","title":"LS from 5G-ACIA: 5G capabilities exposure for factories of the future - revised","source":"5G-ACIA","contact":"Andreas Mueller","contact-id":81087,"tdoctype":"LS in","for":"Action","abstract":"5G-ACIA published a white paper in June 2020 on the exposed 5G capabilities that are needed by factory operators to manage and maintain industrial 5G devices and 5G Non-Public Networks (NPN) in a simple and efficient manner. That white paper has now been enhanced to include additional capabilities and some clarification to the capabilities and functions from the previous version of the white paper. In particular, device-centric requirements have been clarified and a few new ones added in accordance with SA WG1 requirements of Release 17. Concerning net-work-centric requirements, network monitoring have been detailed in the Annex of the white paper. Also, the Annex now lists parameters for QoS monitoring. Since 5G-ACIA believes that these service exposure requirements are valuable to be considered in ongoing work in 3GPP, we would like to make this new white paper availa-ble to you: - White paper title: Exposure of 5G capabilities for connected industries and automa-tion applications - Link www.5g-acia.org\/publications - PDF copy: attached to this liaison statement 5G-ACIA would be eager to receive 3GPP's feedback on these new exposure interface requirements and related Stage-2 and Stage-3 work.","secretary_remarks":"Response drafted in SP-210556. Postponed. This LS was postponed. Related LSs in SP-210457, SP-210462 and SP-210560 postponed.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10530,"status":"postponed","reservation_date":"2021-05-03 14:02:58","uploaded":"2021-05-16 00:01:09","revisionof":"","revisedto":"SP-210802","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3, SA WG6","Cc":"TSG SA, SA WG5, CT WG3, ETG, IEC TC 65, IEEE 802.1, oneM2M TP, OPC Foundation, PI","lsoriginalls":"5G-ACIA_LS_3GPP_Exposure_18032021","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210281.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210285","title":"LS from GSMA OPG: LS from GSMA Operator Platform Group on edge computing definition and integration","source":"GSMA OPG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"1 Introduction The GSMA, one of the Market Representation Partners of 3GPP and participant of ETSI ISG MEC, has launched a project, Operator Platform, to define a platform to expose and monetize network and services capabilities such as edge computing, network slicing or IP COMs. The first focus set for this activity is to define architectural requirements and concept for Telco Edge Cloud. After having issued a white paper to outline a common concept agreed among operators, Operator Platform Group has been created to define architectural capabilities required to achieve the agreed objective and identify the actions to be taken by the industry to ensure a full standardisation and development of the operator platform. 2 Discussion The whitepaper's [3] intention is aiming all the Industry, including operators, vendors, OEMs and service providers, to define a common solution for network and services capability exposure. As a first phase, GSMA is drafting a PRD (Permanent Reference Document) that will provide an end-to-end (E2E) definition of the Operator Platform for edge computing support allowing the GSMA to ensure delivery of this E2E vision across the Industry and the different SDOs. {. . .}","secretary_remarks":"Responses drafted in SP-210551 and SP-210563. Final response in SP-210583","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10360,"status":"replied to","reservation_date":"2021-05-03 14:02:58","uploaded":"2021-05-16 00:01:10","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI ISG MEC, TSG SA, SA WG2, SA WG5, SA WG6","Cc":"ETSI ISG NFV","lsoriginalls":"OPG_52_Doc_03","lsreply":"SP-210583","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210285.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210288","title":"Reply LS on support of PWS over SNPN","source":"RAN WG2","contact":"Ozcan Ozturk","contact-id":42607,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG1 for their LS informing RAN WG2 that SA WG1 'sees the need to introduce support of PWS over SNPN in Rel-17.' RAN WG2 has discussed relevant specification impact, as requested by SA WG1. RAN WG2 understanding is that support of PWS over SNPN is feasible in Rel-17 and minimal impact to the RAN WG2 specifications is foreseen.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10460,"status":"noted","reservation_date":"2021-05-03 14:02:58","uploaded":"2021-05-16 00:01:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG3, TSG RAN, TSG CT, TSG SA, RAN WG3, CT WG1, SA WG2","lsoriginalls":"R2-2104640","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210288.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210291","title":"LS from SA WG2: Reply LS on support of PWS over SNPN","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 thanks SA WG1 for the LS on support of PWS over SNPN. SA WG2 is not impacted by the stage-2 work on PWS and does not expect any impact on specifications under its responsibility. Action: SA WG2 asks recipient groups to take the above information into account","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10470,"status":"noted","reservation_date":"2021-05-03 14:02:58","uploaded":"2021-05-16 00:01:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, CT WG1, RAN WG2, RAN WG3, SA, CT, RAN, SA WG3","Cc":"","lsoriginalls":"S2-2102963","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210291.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210294","title":"LS from SA WG6: 3GPP Edge Computing coordination","source":"SA WG6","contact":"Nishant Gupta","contact-id":62473,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 would like to bring to the attention of SA, the incoming LS from GSMA Operator Platform Group (OPG) in S6-210744, in which GSMA OPG shares their architecture and GSMA OPG's agreement on the interface mapping with 3GPP and ETSI ISG MEC. In this context, SA WG6 in their brief reply LS (S6-210871_RevX) has confirmed their interest to the GSMA initiative to support the alignment of SA WG6 EDGEAPP and the GSMA OP architecture. While some aspects of the agreement on the interface mapping from GSMA OPG directly relate to SA WG6 EDGEAPP architecture (indicated below), SA WG6 believes certain aspects may fall within the scope of SA WG2 and SA WG5. SA WG6 would like to therefore, request SA to coordinate the technical inputs within 3GPP and liaise with GSMA OP including the aspects that relate to the governance and collaboration model for a multi-party alignment effort involving 3GPP, GSMA OPG and ETSI ISG MEC. SA WG6 would like to confirm the following on the interface mapping from GSMA: - UNI: EDGE-1 and EDGE-4 interfaces, between the Edge Enabler Client (EEC) and the Edge Enabler Server (EES) and the Edge Configuration Server (ECS) respectively, can support the requirements of the UNI interface. - SBI-NR: EDGE-2, EDGE-7 and EDGE-8 interfaces, providing access to the 3GPP core network capabilities and services to the EES, the Edge Application Server (EAS) and the ECS respectively, can support the requirements of the SBI-NR interface. - EWBI: EDGE-9 interface, allowing the edge enabler layer interconnection within an ECSP domain and between different ECSP domains e.g. between operator platforms, can support some requirements of EWBI interface. Further, SA WG6 intends to enhance the EDGEAPP architecture with services such as support for roaming in future releases of the work. - NBI: EDGE-3 interface, exposing the capabilities of EES to the EASs, can support some requirements of the NBI interface. EDGE-3 also supports 3GPP's Common API Framework (CAPIF) for API discovery and API invoker's authentication and authorization for API invocation. Above mapping is also captured in Annex D of TS 23.558. SA WG6 EDGEAPP also supports deployments of 3GPP's Service Enabler Architecture Layer (SEAL) allowing ease of vertical application's developments and deployments over Edge. SA WG6 kindly requests SA to include these interface mapping details, along with other such details if provided by SA WG2 and SA WG5, in their communication with GSMA OPG. Action: SA WG6 kindly requests SA to take the above information and liaise with GSMA OPG with coordinated inputs from SA WG6, SA WG2 and SA WG5, including the aspects that relate to the governance and collaboration model for a multi-party alignment effort involving 3GPP, GSMA OPG and ETSI ISG MEC.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10420,"status":"noted","reservation_date":"2021-05-03 14:02:58","uploaded":"2021-05-16 00:01:10","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG5","Cc":"SA WG3","lsoriginalls":"S6-2109783","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210294.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210305","title":"LS from SA WG2: Reply LS on the conclusion of FS_MINT-CT","source":"SA WG2","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 thanks CT WG1 for the LS [S2-2103748\/ C1-212598] on the conclusion of FS_MINT-CT. SA WG2 has discussed the interim conclusions of TR 24.811 v1.1.0 in their SA WG2#145E meeting. SA WG2 agreed that the SA WG2 specification would be expected to be updated based on the final conclusion when the CT WG1 study is completed. To align with the final conclusion of FS_MINT-CT, SA WG2 will update the SA WG2 specifications using WI code of MINT-CT in 3Q 2021. Action: SA WG2 asks CT WG1 and SA to take the information above into account.","secretary_remarks":"Response drafted in SP-210543. Final response in SP-210581","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10310,"status":"replied to","reservation_date":"2021-06-01 06:30:57","uploaded":"2021-06-01 06:50:15","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, TSG SA","Cc":"","lsoriginalls":"S2-2104994","lsreply":"SP-210581","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210305.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210382","title":"Way Forward on PWS over NPN","source":"Qualcomm Finland RFFE Oy","contact":"Francesco Pica","contact-id":57089,"tdoctype":"discussion","for":"Discussion","abstract":"Presentation on Way Forward on PWS over NPN","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10500,"status":"noted","reservation_date":"2021-06-04 05:25:35","uploaded":"2021-06-09 22:44:01","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\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210382.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210385","title":"[DRAFT] LS-reply on PWS over NPN","source":"Qualcomm Finland RFFE Oy","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1, CT WG1, RAN WG2, RAN WG3, SA WG2, TSG RAN, TSG CT. CC: SA WG3","secretary_remarks":"Response to SP-210275. SP 210385_Rev1 (pre-) approved. Revised to SP-210584.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10510,"status":"revised","reservation_date":"2021-06-04 05:33:11","uploaded":"2021-06-09 22:44:01","revisionof":"","revisedto":"SP-210584","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, CT WG1, RAN WG2, RAN WG3, SA WG2, TSG RAN, TSG CT","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210385.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210453","title":"LS from CT WG1: Reply LS on support of PWS over SNPN","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks SA WG1 for their LS on support of PWS over SNPN. CT WG1 would like to inform SA WG1 that support of PWS over SNPN will require updates to TS 23.041 and TS 23.122, and that it is feasible to complete these updates within the Rel-17 time frame. Additionally, CT WG1 would like to ask SA WG1 the following questions: Question-1 to SA WG1: Can an SNPN support emergency services but not support PWS, in a country where PWS is deployed? Question-2 to SA WG1: Is there a need for the UE to prioritize SNPNs supporting PWS over SNPNs not supporting PWS for SNPN selection: - when the UE is in limited service state and SNPN-1 supporting PWS and SNPN-2 not supporting PWS, are available; or - when the UE is not in limited service state, SNPN-1 supporting PWS and SNPN-2 not supporting PWS are available, and SNPN-1 and SNPN-2 are otherwise of the same priority for SNPN selection by the UE?","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10480,"status":"noted","reservation_date":"2021-06-05 05:38:50","uploaded":"2021-06-07 13:18:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2, SA WG3, RAN WG2, RAN WG3, TSG SA, TSG CT, TSG RAN","lsoriginalls":"C1-213640","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210453.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210454","title":"LS on the final conclusion of FS_MINT-CT","source":"CT WG1","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has studied the CT aspects of MINT (Minimization of Service Interruption) based on the service requirements that SA WG1 had specified for Rel-17. As decided in TSG SA#89 (as described in SP-200880), it was confirmed that CT WG1 is responsible for the stage 2 aspects of MINT, but that CT WG1 should consult with SA and SA WG2 on how to proceed with normative work CT WG1's study for six WG meetings including two WG meetings in Q4 2020 before the SID was approved in TSG#90 resulted in 9 Key Issues with 60 solutions described in TR 24.811. In CT WG1#130-e meeting, CT WG1 agreed on the conclusions of all 9 Key Issues, including the aspects that SA had included in their LS in SP-200880, as specified in clause 8 of 3GPP TR 24.811. CT WG1 would like to ask SA and SA WG2 to take the above information into consideration. CT WG1 also would like to ask SA WG2 to update their specifications accordingly, if deemed necessary. Action: CT WG1 kindly asks SA to take above information into consideration and to provide feedback, if any.","secretary_remarks":"Response drafted in SP-210543. Final response in SP-210581","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10320,"status":"replied to","reservation_date":"2021-06-05 05:38:50","uploaded":"2021-06-07 13:18:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, TSG SA","Cc":"TSG CT","lsoriginalls":"C1-213908","lsreply":"SP-210581","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210454.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210456","title":"LS from RAN WG3: Reply LS on support of PWS over SNPN in R17","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks SA WG1 for the LS on support of PWS over SNPN. RAN WG3 has made initial analysis to introduce PWS support for SNPN and RAN WG3 anticipates minor impact. Therefore, RAN WG3 considers feasible to support it within the Rel-17 time frame, subject to RAN decision.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10490,"status":"noted","reservation_date":"2021-06-05 05:38:50","uploaded":"2021-06-07 13:18:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, TSG RAN","Cc":"SA WG2, CT WG1, RAN WG2, TSG SA, TSG CT, SA WG3","lsoriginalls":"R3-212863","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210456.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210457","title":"LS from SA WG2: LS on 5G capabilities exposure for factories of the future","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 discussed the LS from 5G-ACIA, and would like to: 1. Suggest that TSG SA co-ordinates the answers from SA WG1, SA WG2, SA WG3 and SA WG6 to provide a single response from 3GPP perspective, 2. Inform SA plenary that SA WG2 plans to provide its technical input from SA WG2#146E August meeting i.e. for the September TSG SA plenary. Action: SA WG2 kindly asks TSG SA, SA WG1, SA WG3 and SA WG6 to take the above suggestion into account.","secretary_remarks":"CC#3: Postponed","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10540,"status":"postponed","reservation_date":"2021-06-05 05:38:50","uploaded":"2021-06-07 13:18:43","revisionof":"","revisedto":"SP-210803","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG1, SA WG3, SA WG6","Cc":"SA WG5, CT WG3","lsoriginalls":"S2-2104794","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210457.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210458","title":"LS from SA WG2: LS reply to SA on GSMA 3GPP Edge Computing coordination","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 asks TSG SA to provide a consolidated response to the GSMA OPG LS on 'LS on edge computing definition and integration' (S2-2103728) taking into consideration technical input from SA WG2, SA WG5 and SA WG6. SA WG2 is currently working on Rel-17 enhancement for edge computing to be published in TS 23.548 and with updates with TS 23.501, TS 23.502 and TS 23.503 for 5GS enhancement for supporting edge computing features. Since Rel-15, SA WG2 specifications support traffic offloading and AF influence to impact the routing path selection. For Rel-17, SA WG2 specifications support EAS(Edge Application Server) discovery using DNS, EAS (re)discovery, mobility (with and without EAS relocation), and local network information exposure. SA WG2 considers that the AF (Application Function) as defined in 3GPP TS 23.501, 23.502 and 23.548 is an abstraction that can represent SA WG6 EDGEAPP (e.g. ECS, EES or EAS) and\/or ETSI MEC defined entities. Such AF entities can use 5GC API(s) defined by SA WG2 such as NEF API(s). SA WG2 would like to provide the following brief analysis of the proposed interface mapping from GSMA OPG: - SBI-NR: The 5G Core Network provides interfaces beween 5GC NFs (Network Functions) and AF (Application Function) that can be mapped to GSMA Operation Platform's SBI-NR to support features such as network capability exposure, traffic routing, etc. - UNI: May or may not have some impacts on SA WG2 e.g. enhancements of NAS for support of OP would fall into SA WG2's scope. - EWBI: Operator Federation has not been studied in SA WG2 and it is not known if there would or would not be impacts on SA WG2 specifications. - NBI, SBI-CHF, SBI-CR: Seems outside the scope of SA WG2. SA WG2 asks TSG SA to handle the questions regarding governance and collaboration model for a multi-party alignment effort involving 3GPP, GSMA OPG and ETSI ISG MEC. Action: SA WG2 kindly requests SA to take the above information into consideration and liaise with GSMA OPG.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10430,"status":"noted","reservation_date":"2021-06-05 05:38:50","uploaded":"2021-06-07 13:18:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG5, SA WG6","lsoriginalls":"S2-2105034","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210458.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210459","title":"LS from SA WG5: Reply LS on Edge computing definition and integration","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 would like to bring to the attention of TSG SA, the incoming LS from GSMA Operator Platform Group (OPG) in S5-213029, in which GSMA OPG shares their architecture and GSMA OPG's agreement on the interface mapping with 3GPP and ETSI ISG MEC. SA WG5 supports SA WG6 opinion on SA to corordinate the technical inputs within 3GPP and liaise with GSMA OP accordingly. SA WG5 would like to provide it input as follows. SA WG5 would like to confirm the following on the management related interface mapping from GSMA: - SBI-CHF: SA WG5 is conducting a study on charging aspect of edge computing expected to be completed by September 2021. GSMA OPG requirements could be considered by the study or during the resulting normative Rel-17 work. - SBI-CR: SA WG5 would like to inform that cloud resource management is defined by ETSI NFV ISG. SA WG5 refers to NFV ISG for the same. - NBI: The study on management aspects of edge computing, in SA WG5, is in its final stages. SA WG5 plans to initiate a work item to define the normative provisions covering the same. SA WG5 would study the NBI requirements and confirm what all requiremets can be supported by SA WG5 defined management solutions. SA WG5 kindly requests SA to include these interface mapping details, along with other such details if provided by SA WG6 and SA WG2, in their communication with GSMA OPG. Action: SA WG5 kindly requests TSG SA to take the above information and liaise with GSMA OPG with coordinated inputs from SA WG5, SA WG6 and SA WG2, including the aspects that relate to the governance and collaboration model for a multi-party alignment effort involving 3GPP, GSMA OPG and ETSI ISG MEC.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10370,"status":"noted","reservation_date":"2021-06-05 05:38:50","uploaded":"2021-06-07 13:18:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2, SA WG6","lsoriginalls":"S5-213443","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210459.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210462","title":"LS from SA WG5: LS to SA for a coordinated reply to 5G ACIA on \u20185G capabilities exposure for factories of the future\u2019","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 has received the LS 'S5-213024: LS (5G-ACIA-LS-2020-WI039)' from 5G-ACIA on 5G capabilities exposure for factories of the future, and we wish to inform SA of our view to be taken into account in a coordinated reply from TSG SA. SA WG5 specifies 5G network management capabilities including: a) Network Element \/ Network Function management, e.g. RAN and CN NE\/NF management b) Network management (including network slice management in a scenario such as 'NOP internals' - cf. TS 28.530), c) Service management (including network slice management in a scenario such as 'Network Slice as a Service' (NSaaS) - cf. TS 28.530). 3GPP 5G Management Services (MnS) offered by the 5G management system act on network elements \/ network functions, networks and services, and may be exposed to external consumers. The 3GPP exposure governance management function is in charge of management service exposure governance. 3GPP MnS consumers may be in the Network Operator (NOP) domain or outside the NOP domain (e.g. in the Vertical domain). SA WG5 is responsible for the specification of the 5G Management Services, as well as for the specification of the access control and exposure of 5G management services. Regarding the reference points in 5G-ACIA, both En and Nm reference points are related to SA WG5, and we believe they are used to address management exposure aspects. ? 5G-ACIA 5G exposure reference point En supports interactions between 3GPP MnS producers and their consumers for network monitoring as described in section 4.3.1 and 9.2.1 of 5G-ACIA White Paper. The 3GPP Fault Supervision MnS and Performance management MnS can be used to support network monitoring. This also includes monitoring of a logical network e.g. network slice. ? 5G-ACIA 5G exposure reference point Nm supports interactions between 3GPP MnS producers and their consumers for network configuration and maintenance as described in section 4.3.2 of 5G-ACIA White Paper. The 3GPP Provisioning MnS can be used to support network configuration and maintenance. This also includes the add, modify and remove logical networks e.g. network slice. Actions: 1. Please take the above information into account in the coordinated reply to 5G ACIA. 2. Please keep SA WG5 informed of the progress of their work on 5G capabilities exposure for factories of the future, especially on the network management related topics.","secretary_remarks":"CC#3: Postponed","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10550,"status":"postponed","reservation_date":"2021-06-05 05:38:50","uploaded":"2021-06-07 13:18:43","revisionof":"","revisedto":"SP-210804","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"S5-213448","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210462.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210463","title":"LS from SA WG5: LS reply to SA on GSMA 3GPP Edge Computing coordination","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 would like to bring to the attention of SA, the incoming LS from GSMA Operator Platform Group (OPG) in S5-213029, in which GSMA OPG shares their architecture and GSMA OPG's agreement on the interface mapping with 3GPP and ETSI ISG MEC. SA WG5 supports SA WG6 opinion on SA to corordinate the technical inputs within 3GPP and liaise with GSMA OP accordingly. SA WG5 would like to provide it input as follows. SA WG5 would like to confirm the following on the management related interface mapping from GSMA: - SBI-CHF: SA WG5 is conducting a study on charging aspect of edge computing expected to be completed by September 2021. GSMA OPG requirements could be considered by the study or during the resulting normative Rel-17 work. - SBI-CR: SA WG5 would like to inform that cloud resource management is defined by ETSI NFV ISG. SA WG5 refers to NFV ISG for the same. - NBI: The study on management aspects of edge computing, in SA WG5, is in its final stages. SA WG5 plans to initiate a work item to define the normative provisions covering the same. SA WG5 would study the NBI requirements and confirm what all requiremets can be supported by SA WG5 defined management solutions. SA WG5 kindly requests SA to include these interface mapping details, along with other such details if provided by SA WG6 and SA WG2, in their communication with GSMA OPG. Action: SA WG5 kindly requests SA to take the above information and liaise with GSMA OPG with coordinated inputs from SA WG5, SA WG6 and SA WG2, including the aspects that relate to the governance and collaboration model for a multi-party alignment effort involving 3GPP, GSMA OPG and ETSI ISG MEC.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10440,"status":"noted","reservation_date":"2021-06-05 05:38:50","uploaded":"2021-06-07 13:18:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG6","Cc":"","lsoriginalls":"S5-213449","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210463.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210540","title":"Discussion on the normative work for R17 MINT","source":"LG Electronics, KT Corp., LG Uplus, SK Telecom, ETRI, Samsung, Huawei, HiSilicon, Qualcomm","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"discussion","for":"Decision","abstract":"Way forward (1) Agree MINT will be specified in Rel.17 (2) Decide the plan for MINT normative work. - Alternative plan (A) or (B) (3) Send a reply LS to CT WG1 and SA WG2","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2021-06-09 00:48:47","uploaded":"2021-06-09 08:50:39","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_MINT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210540.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210543","title":"[DRAFT] Reply LS on the conclusion of FS_MINT-CT","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"SA guidance for the normative work","secretary_remarks":"Response to SP-210305 and SP-210454. conditionally (pre-) approved, if the related WID in SP-210541 is approved. SP-210543_rev3 (pre-) approved. Revised to SP-210581.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10340,"status":"revised","reservation_date":"2021-06-09 01:00:17","uploaded":"2021-06-09 08:50:39","revisionof":"","revisedto":"SP-210581","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_MINT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG2","Cc":"TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210543.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210551","title":"[DRAFT] Reply LS to GSMA Operator Platform Group on edge computing definition and integration","source":"Samsung","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to GSMA Operator Platform Group on edge computing definition and integration, based on inputs from SA WG2, SA WG5 and SA WG6.","secretary_remarks":"Response to SP-210285. SP-210551_rev4 (pre-) approved. Revised to SP-210583.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10400,"status":"revised","reservation_date":"2021-06-09 14:11:57","uploaded":"2021-06-09 17:19:21","revisionof":"","revisedto":"SP-210583","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG","Cc":"SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210551.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210556","title":"[DRAFT] Reply LS to 5G-ACIA on 5G capabilities exposure for factories of the future","source":"Samsung","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS out","for":"Approval","abstract":"To: 5G-ACIA. CC: SA WG1, SA WG2, SA WG3, SA WG5, SA WG6, CT WG3, ETG, IEC TC 65, IEEE 802.1, oneM2M TP, OPC Foundation, PI (PROFIBUS & PROFINET International), TM Forum","secretary_remarks":"Response to SP-210281. Postponed","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10570,"status":"postponed","reservation_date":"2021-06-09 18:33:07","uploaded":"2021-06-09 18:37:03","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5G-ACIA","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, SA WG6, CT WG3, ETG, IEC TC 65, IEEE 802.1, oneM2M TP, OPC Foundation, PI (PROFIBUS & PROFINET International), TM Forum","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210556.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210560","title":"LS from SA WG6: LS on 5G capabilities exposure for factories of the future","source":"SA WG6","contact":"Camilo Solano","contact-id":80091,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 discussed the incoming LS from 5G-ACIA on 5G capabilities exposure for factories of the future - revised in SA WG6#43-e, and decided: 1) Follow the decision of other involved WGs and request SA to provide a coordinated reply to 5G-ACIA; 2) Provide an input to SA about the work SA WG6 has addressed related to the 5G-ACIA white paper to be considered for the coordinated SA reply. Therefore, SA WG6 would like to request SA to coordinate such a reply to 5G-ACIA and take into consideration the following input about the related SA WG6 work. SA WG6 has addressed service layer exposure requirements for industrial applications within Release 17 in the study on application layer support for Factories of the Future in 5G network. This study was done based on 5G network exposure capabilities and SA WG1 requirements. The SA WG6 study is documented in the technical report 3GPP TR 23.745. As described in the latest version of 3GPP TR 23.745, identified key issues, solutions and conclusions at the application enablement layer have been addressed which may be of interest of 5G-ACIA. For instance, device management requirements on device identity management, device connectivity management (e.g. for time sensitive communication support, TSN support, QoS monitoring), device connectivity monitoring, device group management (e.g. 5GLAN group management) and device location information are some of the addressed key issues within the SA WG6 study. Other requirements have also been addressed within this study, e.g. clock synchronization. Also, some of the concluded solutions in 3GPP TR 23.745 have already been specified in Release 17 as part of enhancements to the Service Enabler Architecture Layer for Verticals (SEAL) in the technical specification 3GPP TS 23.434. Besides, SA WG6 would like to request 5G-ACIA to provide any feedback on the completed work in 3GPP TR 23.745 and the solutions introduced in SEAL in order to continue the collaboration on service exposure capabilities for industrial applications. Likewise, SA WG6 would like to ask 5G-ACIA to encourage its members to actively engage in the related SA WG6 activities.","secretary_remarks":"CC#3: Postponed","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10560,"status":"postponed","reservation_date":"2021-06-09 20:56:09","uploaded":"2021-06-09 21:16:56","revisionof":"","revisedto":"SP-210805","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, CT WG3","lsoriginalls":"S6-211497","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210560.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210562","title":"[DRAFT] LS reply to GSMA Operator Platform Group on edge computing definition and integration","source":"Ericsson LM","contact":"Magnus Olsson","contact-id":14562,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA OPG. CC: ETSI ISG MEC, ETSI ISG NFV, SA WG2, SA WG5, SA WG6","secretary_remarks":"Revised to SP-210563","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10380,"status":"revised","reservation_date":"2021-06-09 21:39:07","uploaded":"2021-06-09 21:43:20","revisionof":"","revisedto":"SP-210563","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG","Cc":"ETSI ISG MEC, ETSI ISG NFV, 3GPP TSG SA2, 3GPP TSG SA WG5, 3GPP TSG SA WG6","lsoriginalls":"OPG_52_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210562.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210563","title":"[DRAFT] LS reply to GSMA Operator Platform Group on edge computing definition and integration","source":"Ericsson, Vodafone","contact":"Magnus Olsson","contact-id":14562,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA OPG. CC: ETSI ISG MEC, ETSI ISG NFV, SA WG2, SA WG5, SA WG6","secretary_remarks":"Revision of SP-210562. Response to SP-210285. Merged into the revision of SP 210551.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10390,"status":"merged","reservation_date":"2021-06-09 22:02:14","uploaded":"2021-06-09 22:05:16","revisionof":"SP-210562","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG","Cc":"ETSI ISG MEC, ETSI ISG NFV, 3GPP TSG SA2, 3GPP TSG SA WG5, 3GPP TSG SA WG6","lsoriginalls":"OPG_52_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210563.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210574","title":"LS from TSG CT: LS on OAuth2 misalignments between SA WG3 and CT WG4 specifications","source":"TSG CT","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"TSG CT kindly asks SA WG3 to prioritize the resolution of the OAuth2 misalignments between the SA WG3 and CT WG4 specifications in Q3 2021, regarding: - the mandate of the use of the NFManagement_NFRegister service operation for Oauth2.0 client registration; and - the use of Oauth2.0 access token when a NF consumes the NRF APIs, i.e. NFManagement and NFDiscovery.","secretary_remarks":"Noted. OAuth 2.0 issue will be discussed and hopefully resolved by SA WG3 during Q3\/2021","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10580,"status":"noted","reservation_date":"2021-06-16 07:04:44","uploaded":"2021-06-16 07:05:24","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"TSG SA","lsoriginalls":"CP-211326","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210574.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210581","title":"Reply LS on the conclusion of FS_MINT-CT","source":"TSG SA","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, SA WG2, SA WG3, TSG RAN. CC: TSG CT. Attachments: SP-210582","secretary_remarks":"Revision of SP-210543_rev3. Response to SP-210305 and SP-210454. This LS OUT was approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10350,"status":"approved","reservation_date":"2021-06-18 17:48:00","uploaded":"2021-06-18 17:50:29","revisionof":"SP-210543","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"FS_MINT-CT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-210305","lsto":"CT WG1, SA WG2, SA WG3, TSG RAN","Cc":"TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210581.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210583","title":"Reply LS to GSMA Operator Platform Group on edge computing definition and integration","source":"TSG SA","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA OPG. CC: SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","secretary_remarks":"Revision of SP-210551_rev4. This LS OUT was approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10410,"status":"approved","reservation_date":"2021-06-18 17:48:01","uploaded":"2021-06-18 17:50:29","revisionof":"SP-210551","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-210285","lsto":"GSMA OPG","Cc":"SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210583.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-210584","title":"Reply LS on support of PWS over NPN","source":"TSG SA","contact":"Francesco Pica","contact-id":57089,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG1, SA WG3, CT WG1, RAN WG2, RAN WG3. CC: SA WG2, TSG CT, TSG RAN. Attachments: SP-210585, SP-210586","secretary_remarks":"Revision of SP-210385_rev1. This LS OUT was approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10520,"status":"approved","reservation_date":"2021-06-18 17:48:01","uploaded":"2021-06-18 17:50:30","revisionof":"SP-210385","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG3, CT WG1, RAN WG2, RAN WG3","Cc":"SA WG2, TSG CT, TSG RAN","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGs_92E_Electronic_2021_06\/Docs\/SP-210584.zip","group":"SP","meeting":"SP-92-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]