[{"name":"SP-231207","title":"LS from SA WG4: Reply LS on alignment of activities on UE data collection, reporting and event exposure","source":"SA WG4","contact":"Richard Bradbury","contact-id":82569,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 acknowledges TSG SA LS on the topic of alignment of activities on UE data collection, reporting and event exposure and provides the following answers to the questions posed.","secretary_remarks":"Revision of postponed SP-230786 from TSG SA#101. Related input contributions were requested for this meeting. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"SP-230786","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2","lsoriginalls":"S4-231092","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231207.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231214","title":"LS from ETSI SAI: LS to SA, SA3 and SA5 on potential collaboration between 3GPP SA3\/SA5 and ETSI SAI ISG","source":"ETSI SAI","contact":"Scott Cadzow","contact-id":19494,"tdoctype":"LS in","for":"Information","abstract":"The primary responsibility of ETSI Industry Specification Group on Securing Artificial Intelligence (ISG SAI) is to develop technical specifications that mitigate against threats arising from the deployment of AI and threats to AI systems from both other AIs and from conventional sources. The group s work is intended to frame the security concerns arising from AI. It will also build the foundations of a longer-term response to the threats to AI in sponsoring the future development of normative technical specifications. {. . .} Action: ETSI SAI kindly asks TSG SA to review the information in this LS and reply with potential areas of interest that need ETSI SAI ISG involvement.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2023-11-07 10:19:15","uploaded":"2023-11-07 10:20:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG3, SA WG5","Cc":"ITU-T SG13, SG17, ITU-R","lsoriginalls":"SAI(23)18a007r4","lsreply":"SP-240273","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231214.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231226","title":"LS from SA WG3: Reply LS on potential collaboration between 3GPP SA3 and ETSI SAI","source":"SA WG3","contact":"Alec Brusilovsky","contact-id":72017,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank ETSI SAI for their incoming LS in S3-234496 (SAI(23)18a007r4, LS to SA, SA WG3, and SA WG5 on potential collaboration between SA WG3\/SA WG5 and ETSI SAI ISG). Collaboration and coordination with the Security of AI activities in ETSI is the way to avoid duplication of efforts. In Rel-18, SA WG3 had the following two AI\/ML security studies without normative work: TR 33.877 Study on the security aspects of Artificial Intelligence (AI)\/Machine Learning (ML) for the Next Generation Radio Access Network (NG-RAN) TR 33.898 Study on security and privacy of Artificial Intelligence\/Machine Learning (AI\/ML)-based services and applications in 5G and the following eNA study with normative work: TR 33.738 Study on security aspects of enablers for Network Automation for 5G - phase 3 SA WG3 will keep ETSI SAI informed if there are other AI\/ML-related security aspects and associated Study and\/or Work Items which may need cooperation with ETSI SAI.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2023-11-07 10:19:16","uploaded":"2023-11-24 07:46:23","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG SA, SA WG5","lsoriginalls":"S3-235007","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231226.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231287","title":"LS from SA WG5: Reply LS to LS to 3GPP re Monitoring of Encrypted 5GS Signalling Traffic","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 received an LS from GSMA 5GPKIWP on Monitoring of Encrypted 5GS Signalling Traffic. SA WG5 discussed the potential GSMA 5GPKIWP solutions aimed at addressing mobile operators' implementation issues with the monitoring of their 5GS signalling traffic. SA WG5 would like to provide their feedback to GSMA 5GPKIWP on solutions falling under the scope of SA WG5. The solution 2 identified by GSMA 5GPKIWP is known in 3GPP as Subscriber and Equipment Trace (see 3GPP TSs 32.421, 32.422 and 32.423). The Subscriber and Equipment Trace was originally introduced in 3GPP Rel-6 and has been actively maintained and evolved since. Starting from 3GPP Rel-10 the Trace functionality is re-used for reporting of per-UE measurements (collected either at the UE and\/or at the BTS) currently known as Minimization of Drive Testing (MDT). In 3GPP Rel-15, with the introduction of Service Based Management Architecture (SBMA), Trace has been extended with the real-time high volume streaming reporting (see 3GPP TSs 28.532 and 32.423). As a high-level overview, the 5G Trace relies on Network Functions collecting a copy of the signalling traffic matching the trace job activation criteria (e.g. all subscribers or only certain identities, all or certain interfaces, all or certain Network Functions), the collected data is streamed to the Management Service (MnS) consumer via TLS protected WebSocket with ASN.1 or GPB serialization. A known implementation of 3GPP Trace MnS consumer in ONAP DCAE receives the streaming Trace data from a WebSocket and publishes it on an internal Kafka bus for multiple applications interested in said data. The SBMA specifications do not restrict what entities can play the role(s) of MnS consumer - any authorized entity (e.g. 'GSMA monitoring system') can play said role. Regarding the reply from SA WG3, 'SA WG3 has noted that Option 2 solution capabilities, interfaces, and techniques reside within virtualization infrastructure that is outside the scope of 3GPP.', we would like to clarify that Subscriber and Equipment Trace, corresponding to GSMA 5GPKIWP 'option 2' solution, is within the scope of 3GPP (specifically addressed by SA WG5 specifications) and applies to both virtualization and non-virtualization scenarios. Focusing on the solution 4 (i.e. use of CDRs), SA WG5 Charging found that it was important to inform GSMA 5GPKIWP on a few key evolutions of 3GPP charging framework from 3GPP Rel-15 (see TS 32.290): in 5GS, a dedicated NF (namely the CHF) is responsible to generate the Charging Data records (CDRs) associated to active elements (e.g. SMF) and their services, i.e. CDRs generation by NF is no more applicable. This is achieved by CHF interacting with NFs using SBI, in addition to the control of service(s) usage in real-time (via quota management). Although the produced CDRs are more for post-processing , they include details captured during the service(s) usage control (and not only at service or call release). Action: SA WG5 kindly requests SA to coordinate the reply LS to GSMA 5GPKIWP considering that Subscriber and Equipment Trace is within the scope of 3GPP and applies to both virtualization and non-virtualization scenarios.","secretary_remarks":"LS to GSMA 5GPKIWP drafted in SP-231533. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2023-11-24 07:57:26","uploaded":"2023-11-24 08:12:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG3","Cc":"","lsoriginalls":"S5-238140","lsreply":"SP-231668","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231287.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231289","title":"LS from SA WG6: LS on collaboration and alignment of 3GPP defined application enablers with GSMA Open Gateway","source":"SA WG6","contact":"Basavaraj (Basu) Pattan","contact-id":99644,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 is making continuous efforts to align 3GPP defined EDGEAPP architecture with GSMA Operator Platform (OP) architecture and requirements. SA WG6 believes that such collaboration and alignment with GSMA has been extremely useful, and is keen to explore similar alignment with the GSMA Open Gateway initiative taking into consideration the SA WG6 Application Enablement standards such as CAPIF, SEAL services (including NSCE, ADAE, SEALDD), V2XAPP, UASAPP, 5GMARCH, and PINAPP. In this spirit, SA WG6 has agreed to the below proposed LS content to be sent to GSMA and would like to request SA to liaise with GSMA on behalf of SA WG6. Action: SA WG6 kindly asks SA to liaise the below proposed LS content with GSMA on behalf of SA WG6.","secretary_remarks":"This was noted and the content left for off-line discussion and an LS from TSG SA created in SP-231669","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2023-11-24 07:57:26","uploaded":"2023-11-24 08:12:04","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"S6-234063","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231289.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231533","title":"[DRAFT] Reply LS to GSMA on Monitoring of Encrypted 5GS Signalling Traffic","source":"SA WG5 Chair","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS out","for":"Approval","abstract":"Proposed coordinated response to GSMA 5GPKIWP","secretary_remarks":"Response to request in SP-231287. Revised to SP-231668.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2023-12-02 12:43:32","uploaded":"2023-12-06 13:04:02","revisionof":"","revisedto":"SP-231668","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GPKIWP","Cc":"SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231533.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231585","title":"Discussion Paper on traffic monitoring","source":"Vodafone","contact":"Sergio Pozo","contact-id":89751,"tdoctype":"discussion","for":"Endorsement","abstract":"The current tracing solution does not cover the requirements of traffic monitoring requested by the GSMA","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10280,"status":"noted","reservation_date":"2023-12-04 19:27:36","uploaded":"2023-12-05 09:59:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231585.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231668","title":"Reply LS to GSMA on Monitoring of Encrypted 5GS Signalling Traffic","source":"TSG SA","contact":"Lan Zou","contact-id":35534,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA 5GPKIWP. CC: SA WG2, SA WG5, SA WG3","secretary_remarks":"Revision of SP-231533. 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":10300,"status":"approved","reservation_date":"2023-12-11 18:26:57","uploaded":"2023-12-15 16:01:09","revisionof":"SP-231533","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-231287","lsto":"GSMA 5GPKIWP","Cc":"SA WG2, SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231668.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231669","title":"LS on collaboration and alignment of 3GPP defined application enablers with GSMA Open Gateway","source":"TSG SA","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA Open Gateway CC: GSMA OPG, SA WG2, SA WG5, SA WG6","secretary_remarks":"Created at the meeting. Revised to SP-231778.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10330,"status":"revised","reservation_date":"2023-12-11 18:26:57","uploaded":"2023-12-15 16:01:09","revisionof":"","revisedto":"SP-231778","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Open Gateway","Cc":"GSMA OPG, SA WG2, SA WG5, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231669.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-231778","title":"LS on collaboration and alignment of 3GPP defined application enablers with GSMA Open Gateway","source":"TSG SA","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA Open Gateway CC: GSMA OPG, SA WG2, SA WG5, SA WG6, TSG CT","secretary_remarks":"Revision of SP-231669. 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":10340,"status":"approved","reservation_date":"2023-12-15 13:20:10","uploaded":"2023-12-15 16:01:09","revisionof":"SP-231669","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Open Gateway","Cc":"GSMA OPG, SA WG2, SA WG5, SA WG6, TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_102_Edinburgh_2023-12\/Docs\/SP-231778.zip","group":"SP","meeting":"SP-102","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]