[{"name":"SP-240003","title":"LS from GSMA OPAG: LS to 3GPP_Correlation information for API volume based charging","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"The Operator Platform (OP) allows Operators to charge for the services and capabilities that are exposed by an Operator to Application Providers, subscribers and Other Operator Partners. Services and capabilities exposed by the Operator Platform have been classified into a set of different service categories from a charging perspective. In particular there is a service category called Network capabilities exposure services with impact on the device s data usage (e.g. CAMARA Quality on Demand API) where an Operator could choose to do the rating and charging depending on the data traffic usage in the Operator s Network (volume based charging model) as a result of API\/service invocation of that type. Considering that in this case the Operator s Charging Engine would need to identify the data sessions that are impacted by an API\/service invocation, GSMA Operator Platform API Group (OPAG) would like to ask assistance from SA WG5 on understanding what information could be used by the Operator s Charging engine in the charging requests (Diameter\/SBI) coming from the Operator s Network to enable this charging model.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2024-02-27 11:28:28","uploaded":"2024-02-27 11:31:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA","lsoriginalls":"OPAG_94_Doc_07","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240003.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240004","title":"LS from GSMA OPAG: LS to 3GPP_Reservation of Edge Resources","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"GSMA Operator Platform API Group (OPAG) would like to ask assistance from SA WG5 on understanding how to be able to charge for reservation of Edge Resources.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2024-02-27 11:28:28","uploaded":"2024-02-27 11:31:07","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA","lsoriginalls":"OPAG_94_Doc_08","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240004.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240005","title":"LS from GSMA 5GMRR: LS to 3GPP on data plane control by roaming hubs","source":"GSMA 5GMRR","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"Introduction: GSMA 5GMRR would like to draw the attention of 3GPP to the following requirements again: 1. The RH shall have the ability to intervene in roaming data sessions at any time, in order to limit roaming data usage by limiting throughput and\/or stopping ongoing data sessions as agreed with the client HPMN. This ability to intervene requires anchoring the media in this intermediary. 2. All N32 messages between client MNOs are transferred via the RH. This shall include the ability for the RH to prevent the establishment of, and the termination of N32-c and N32-f connections, for example if this is required due to contractual reasons. As a clarification to requirement 1: The RH shall be able to intervene on roaming data sessions on the basis of individual PDU sessions and across all PDU sessions of the roamers of a given roaming relationship between two PLMNs.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2024-02-27 11:28:28","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2","Cc":"SA WG3, SA WG5, TSG SA, CT WG4","lsoriginalls":"5GMRR Doc 47_14r1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240005.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240006","title":"LS from GSMA PTQN TF: LS regarding the publication of the Post Quantum Cryptography - Guidelines for Telecom Use Cases document in Feb 24","source":"GSMA PTQN TF","contact":"Yolanda Sanz","contact-id":45969,"tdoctype":"LS in","for":"Information","abstract":"On 24th September 2022, GSMA members agreed to create a new task force called Post Quantum Telco Network (PQTN) to identify the impact of Post Quantum Cryptography in the context of the Telco Industry. Since then, the PQTN TF has released two documents: - Post Quantum Telco Network Impact Assessment Whitepaper - Guidelines for Quantum Risk Assessment for Telco Now, PQTN TF would like to inform about the publication of Post Quantum Cryptography Guidelines for Telecom Use Cases by end of February 2024. The scope of this document is to provide a set of best practice guidelines that can be used to support the journey to Quantum safe cryptography in the context of the telecom ecosystem. Action: Please note that the GSMA PQTN Task Force will publish PQ.03 Post Quantum Cryptography Guidelines for Telecom Use Cases by the end of February 2024. The document shared is still draft. This is the first detailed, telco sector-specific, analysis of the implications of the transition to Post Quantum Cryptography for the telecom industry. We trust you will find this document valuable. We request that you consider the implications of this document as input and requirements for the standards\/recommendations you are developing. The GSMA PQTN can work with you to clarify these requirements. We request that you acknowledge this liaison statement, and we are happy to receive any feedback.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2024-02-27 11:28:28","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG3, SA WG3-LI","Cc":"","lsoriginalls":"PQTN_52_Doc_004R01","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240006.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240007","title":"Reply LS on CAPIF extensibility","source":"CT WG3","contact":"Abdessamad EL MOATAMID","contact-id":89270,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 thanks ETSI ISG MEC on their reply LS on CAPIF extensibility and alignment with ETSI ISG MEG. CT WG3 would like to inform ETSI ISG MEC, SA WG6 and SA WG3 that CT WG3 completed the definition of the extensibility of the security methods as per the agreed CR#0301 (TS 29.222, C3-240220) attached to this LS. With this, CT WG3 would like to inform ETSI ISG MEC, SA WG6 and SA WG3 that CT WG3 completed the definition of the CAPIF extensibility and alignment with ETSI ISG MEG requirements, i.e.: - Extensibility of the data model, with in particular the extensibility of the protocols, data formats and security methods for AEFs defined outside 3GPP. - Extensibility of the query parameters for AEFs defined outside 3GPP. Regarding the question on the service API category, CT WG3 is still discussing it and will provide a feedback in its future meetings.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG6, ETSI ISG MEC","Cc":"TSG CT, TSG SA","lsoriginalls":"C3-240155","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240007.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240009","title":"LS from RAN WG5: Reply-LS on Prohibition of GEA1 & GEA2 Support in all releases","source":"RAN WG5","contact":"Petra Rauer","contact-id":16070,"tdoctype":"LS in","for":"Information","abstract":"RAN WG5 would like to thank TSG SA for the liaison statement notifying updates made to the latest version of all releases of TS 43.020 and TS 03.20 to prohibit the implementation of GEA1 and GEA2 in Mobile Stations of all releases. RAN WG5 also noted SA request to facilitate verification of non-support of GEA1 and GEA2 through RAN WG5 test specifications. RAN WG5 is pleased to inform that Change Requests (CRs) proposing removal of testing of GEA1 and GEA2 from all RAN WG5 test specifications have been agreed by RAN WG5#102 Meeting. RAN WG5 had already defined the Test Case (TC) 44.2.5.2.5 in TS 51.010-1 to verify non-support of GEA1. A CR proposing to update TC 44.2.5.2.5 to also verify non-support of GEA2 has been agreed by RAN WG5#102 Meeting. RAN WG5 agreed CRs shall be submitted for approval to TSG RAN#103 Plenary meeting scheduled March 17 21 2024 at Maastricht. RAN WG5 expects TC 44.2.5.2.5 verifying non-support of GEA1 and GEA2 to be included in the next version of TS 51.010-1 scheduled to be published in March 2024 following TSG RAN#103 meeting.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, GCF Steering Group","Cc":"SA WG3, TSG RAN, PTCRB Plenary","lsoriginalls":"R5-240020","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240009.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240010","title":"LS from SA WG1: Reply LS on energy states in TS\u00a022.261","source":"SA WG1","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 would like to thank SA WG5 regarding the LS on energy states in TS 22.261. SA WG1 has discussed the matter during SA WG1#105 meeting and would like to provide the following - SA WG1 does not have the scope to review the suitability of solutions (such as SA WG5-defined energySavingState attribute) to service requirements. - It is up to Stage 2 working groups to decide on the definition and number of states to support requirements in clause 6.15a.3 of TS 22.261 by the 5G System.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, SA WG2","lsoriginalls":"S1-240299","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240010.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240011","title":"LS from SA WG1: Reply LS to S1-240153\/ RP-234075 on Robust Notification Alert for NTN-NR","source":"SA WG1","contact":"Munira Jaffar","contact-id":77683,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks TSG RAN for the LS in S1-240153\/RP-234075. SA WG1 does not have requirement relating to the Robust Notification Alert for NTN-NR. SA has frozen the stage 1 of Release 19. SA WG1 has agreed the study on Satellite Access Phase 4 for Release 20 (FS_5GSAT_Ph4), a study for 5G system with satellite access, where one of the objectives include to study ability to notify the user that a mobile terminated communication (e.g. MMTel call) had failed when the UE was unreachable in satellite access.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG2","Cc":"TSG SA","lsoriginalls":"S1-240309","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240011.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240012","title":"LS from SA WG2: Reply LS on Coordination of work for UAS_Ph3","source":"SA WG2","contact":"Laeyoung Kim","contact-id":58611,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to thank SA WG6 regarding the LS on Coordination of work for UAS_Ph3 and provide the feedback as below. The SID for Study on Phase 3 for UAS, UAV and UAM (FS_UAS_Ph3), SP-231801 approved at SA#102 includes the following work task related to UAV flight path monitoring. So, SA WG2's understanding is that the SA WG6 objective related to real time UAV flight path monitoring may have some overlap with the SA WG2 objective related to WT#1. - WT#1: Based on SA WG1 requirements and input from aviation fora, study whether and how to enhance NEF services to support service exposure and interactions between MNOs and UTM functions for i.e. pre-mission flight planning, in-mission flight monitoring, C2 communication reliability, interfacing with UTM (e.g. supporting the scenario of multiple USS serving the geographical areas corresponding to UAV flight path). The CR attached in the SA WG6 LS (S6-233453) reads the interaction between the UAS application specific server and the UAE server, and between the UAE server and the UAE client to support real time UAV flight path monitoring where there is no direct involvement of RAN or any 5GC NFs such as NEF. Therefore, SA WG2's understanding is that no overlap with SA WG2 work is expected from a mechanism perspective. SA WG2 believes that it is acceptable to develop and specify both application layer based mechanisms in SA WG6 and 5GS based mechanisms in SA WG2 as long as the two mechanisms are not conflicting. SA WG2 has just started FS_UAS_Ph3 at this meeting and its completion target date is TSG#104 (June 2024). Therefore, SA WG2 cannot assess whether there is any dependency between SA WG2 and SA WG6 mechanisms. SA WG2's opinion is that SA WG6 needs to make sure that any 5GS impact is not assumed when progressing UASAPP_Ph3 work until the SA WG2 study is complete.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"TSG SA","lsoriginalls":"S2-2401812","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240012.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240013","title":"LS from SA WG2: LS on No-Transmit Zones according to ECC decision 22(07)","source":"SA WG2","contact":"Stefano Faccin","contact-id":57487,"tdoctype":"LS in","for":"Information","abstract":"With reference to the ECC decision 22(07) and the identification of No-Transmit Zones (NTZs), SA WG2 has initiated a study item on FS_UAS_Ph3 to address the definition of mechanisms regarding the support of NTZs. SA WG2 has identified the following questions regarding the support of NTZs: 1. It is SA WG2 understanding that the aerial UE would be forbidden from transmitting in protected frequency band(s) of cells in a NTZ while the aerial UE can operate as normal in allowed frequency band(s) of cells within an NTZ. In case all available frequency bands in a cell are protected is the aerial UE forbidden to transmit for any services, including emergency services and high priority services? 2. The ECC Decision 22(07) states that a non-transmit zone in the Decision is defined as a geographical area where aerial UE are not allowed to transmit for spectrum compatibility reasons in a given harmonized MFCN band or part of it . SA WG2 would like to clarify whether the UE is allowed to receive data while in the NTZ in the protected frequency band(s), or is the NTZ restriction applicable to both downlink and uplink? 3. Cellular coverage in areas where an NTZ is located may include large cells overlapping with the NTZ. What is the expectation from the UEs behavior in relation to the NTZ(s), if any?","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI MSGTFES, ETSI MSGTFES","Cc":"SA WG1, TSG SA, TSG RAN","lsoriginalls":"S2-2401813","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240013.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240015","title":"LS from SA WG2: LS on per UE energy consumption in RAN","source":"SA WG2","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS in","for":"Information","abstract":"Based on Rel-19 stage 1 requirements in TS 22.261 clause 6.15a, SA WG2 are studying Energy Efficiency and Energy Saving (TR 23.700-66) including how to expose information about the amount of network energy consumed by UEs. In general, operators can already (pre-Rel-19) generate an approximate energy consumption per UE by taking the complete energy consumption for the network over a period of time; the complete data traffic for the network over that period of time; and the amount of data used by the UE over that period of time. However, it is clear this is only a very rough piece of information that may not be suitable for the identification of the UEs using a disproportionately large or small amount of network energy for the data they receive. At the moment, no one (operator, subscriber, chipset maker, base station vendor, CN vendor) knows this information. Hence, e.g., network optimisation cannot be done to reduce energy consumption, nor enterprises encouraged to mount IoT devices in less energy-consuming locations, nor consumers nudged to modify their habits, etc. SA WG2 are interested whether the RAN can estimate and report the network energy consumption for connected mode mobiles. While some of this energy consumption (e.g., in the base-band unit) is probably relatively easy to compute based on the UE s data volume, the majority is consumed by the remote radio heads and is likely to vary with the radio conditions and require more complex estimation. SA WG2 invites RAN working groups (e.g., RAN WG1, 2, 4) to identify an appropriate estimation mechanism for this. With regard to the granularity of reporting, SA WG2 invites RAN working groups (e.g., RAN WG2) to indicate whether per-UE-per-network slice, and per-UE-per-QoS flow reporting is possible for the network energy consumption including the energy consumption that varies with radio conditions. With regard to how the information about the UE s RAN energy consumption is reported to the CN, SA WG2 are studying various mechanisms (e.g., similar to DC s secondary RAT data volume reporting , or GTP-U header extensions, etc).","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN WG1, RAN WG2, RAN WG4","Cc":"TSG SA, SA WG1, SA WG5, RAN WG3","lsoriginalls":"S2-2403733","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240015.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240016","title":"LS from SA WG2: Reply LS on Robust Notification Alert","source":"SA WG2","contact":"Peng Tan","contact-id":99889,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks TSG RAN for the Liaison (S2-2401850\/RP-234075) on Robust Notification Alert. Regarding the below question raised by TSG RAN, SA WG2 would like to provide the following feedback: {. . .}","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, SA WG1","Cc":"TSG SA","lsoriginalls":"S2-2403843","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240016.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240021","title":"LS from SA WG4: Reply to LS on 3GPP work on energy efficiency","source":"SA WG4","contact":"Nikolai Leung","contact-id":38562,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 thanks SA WG5 for your Reply LS on 3GPP work on energy efficiency. SA WG4 provides the following in response to the SA WG5 responses: Proposed changes to 3GPP templates for Work Item Descriptions and Specifications Original SA WG4 proposal: A proposal to modify the 3GPP Work Item Description and Specification templates to include a clause on Impact on Climate or How can impact on energy efficiency and\/or energy saving and\/or digital sobriety be considered in the work that would identify and collect relevant information. The end goal is to have the new clause be a consideration similar to the way Security is considered in any 3GPP effort or feature. To enable this, SA WG4 is considering to study developing guidelines on how this new clause would be populated. The hope is that such a clause may increase the awareness and considerations for any climate impact where this applies, while we hope it would not become a platform for green washing. SA WG5 reply: SA WG5 supports the proposal to modify the 3GPP Work Item Description and Specification templates to include a clause on Impact on Climate or How the impact on energy efficiency and\/or energy saving and\/or digital sobriety is considered in the work that would identify and collect relevant information. SA WG5 joins SA WG4 wishes that this would not become a platform for green washing. SA WG4 appreciates the support. Some member companies in SA WG4 are planning to propose to add the following clause to the 3GPP Work Item Description template via company contributions into SA#103:","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, SA WG1, SA WG2, SA WG3, SA WG6","lsoriginalls":"S4-240517","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240021.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240022","title":"LS from SA WG5: LS reply to LS on Reply LS on documenting code normatively in 3GPP Forge","source":"SA WG5","contact":"Sean Sun","contact-id":92711,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG4 for the Reply LS on documenting code normatively in 3GPP Forge in document S4-231915, with following the questions. {. . .]","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10170,"status":"noted","reservation_date":"2024-02-27 11:28:29","uploaded":"2024-03-07 06:45:04","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"TSG SA","lsoriginalls":"S5-240076","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240022.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240210","title":"LS from SA WG5: LS on progress of 3GPP SA5 R18 and R19 work on intent driven management","source":"SA WG5","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"LS in","for":"Information","abstract":"Intent driven management for mobile networks is an important topic introduced in SA WG5 as friendly used API to allow a customer to provide intents as the desired state of the network or its services, without any detailed information of how to get to the desired state. SA WG5 started the work item intent driven management for mobile networks since 2018, and completed its Release 17 work on the intent driven management services for mobile networks in June 2022, corresponding published specification is TS 28.312 (Management and orchestration; Intent driven management services for mobile networks). SA WG5 would like to inform that it has completed its Release 18 work on the intent driven management services for mobile networks phase 2. Main outcomes include (non-exhaustive list): {. . .}","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10180,"status":"noted","reservation_date":"2024-03-06 17:43:58","uploaded":"2024-03-07 07:11:11","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum, ETSI ZSM, ETSI NFV IFA, ITUT SG2, ITUT SG13, GSMA OPG","Cc":"TSG SA","lsoriginalls":"S5-240339","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240210.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240211","title":"LS from SA WG5: Reply LS to ITU-T SG13 on the consent of draft new Recommendation ITU-T Y.3161 (ex ITU-T Y.IMT2020-IBNMO) 'Intent-based network management and orchestration for network slicing in IMT-2020 networks and beyond'","source":"SA WG5","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank ITU-T SG13 for your LS on the consent of draft new Recommendation ITU-T Y.3161 (ex ITU-T Y.IMT2020-IBNMO) Intent-based network management and orchestration for network slicing in IMT-2020 networks and beyond . SA WG5 would like to inform ITU-T SG13 that SA WG5 has already developed the intent driven management service which is the interface for the management of mobile network (including radio network, core network and network slicing). The standardized management services are captured in published specification TS 28.312 (Management and orchestration; Intent driven management services for mobile networks). TS 28.312 specifies the stage 1 (concept, use cases and requirements), stage 2 (information set and procedure) and stage3 (YAML solution set) for intent driven management service for mobile network. {. . .}","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2024-03-06 17:43:58","uploaded":"2024-03-07 07:11:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITUT SG 13","Cc":"TSG SA, ITUT SG2, SG11, ETSI ISG ZSM, IRTF NMRG","lsoriginalls":"S5-240386","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240211.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240212","title":"LS from SA WG5: Reply LS to ITU-T SG2 on work progress of M.fidtom Framework of intent driven telecom operation and management and orchestration","source":"SA WG5","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank ITU-T SG2 for your LS\/r on work progress of M.fidtom, Framework of intent driven telecom operation and management and the response on suggestions in the liaison statement S5-233545. Following are SA WG5 further responses 1st Response in the liaison statement S5-233545: Considering the intent definition in TS 28.312 v17.3.1 has been updated in TS 28.312 v18.0.0, ITU-T Study Group 2 will use this term defined in TS 28.312 v18.0.0. SA WG5 Answer: Thanks ITU-T SG 2 for the confirmation to use the intent term defined in TS 28.312 v18.0.0. For your information, the intent definition in TS 28.312 v17.3.1 is same as term definition in TS 28.312 v18.0.0. 2nd Response in the liaison statement S5-233545: ITU-T Study Group 2 agrees with SA WG5 that the intent driven MnS may also be provided by intent driven management as defined in ITU-T M.fidtom, so ITU-T Study Group 2 will consider to reuse the 3GPP intent driven MnS where appropriate. SA WG5 Answer: Thanks ITU-T SG2 to consider to reuse the 3GPP intent driven MnS where appropriate. SA WG5 will continue Rel-19 intent driven management phase 3 work from January 2024 and welcome to collaborate with ITU-T SG2 and exchange information on the intent driven management topic.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2024-03-06 17:43:58","uploaded":"2024-03-07 07:11:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITUT SG2","Cc":"TSG SA","lsoriginalls":"S5-240387","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240212.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240213","title":"LS from SA WG5: LS on energy states in TS 22.261","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"In TS 22.261, the term energy state is defined as state of a cell, a network element and\/or a network function with respect to energy, e.g. (not) energy saving states, which are defined in TS 28.310 [47] . Furthermore, TS 22.261 clause 6.15a.3 (Support of energy states) captures requirements for the 5G system to: support different energy states of network elements and network functions support dynamic changes of energy states of network elements and network functions SA WG5 has been working on energy saving related states for several releases (see energy saving definitions and concepts in TS 28.310 clauses 3.1 and 4.3) and has defined one energy saving related state attribute named energySavingState (see TS 28.541 clause 4.4.1), with two allowed values: isEnergySaving (state in which some functions of a cell or network function are powered-down), isNotEnergySaving (state when no energy saving in progress). Therefore, SA WG5 would like to know whether the SA WG5-defined energySavingState attribute satisfies TS 22.261 clause 6.15a.3 requirements.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10210,"status":"noted","reservation_date":"2024-03-06 17:43:58","uploaded":"2024-03-07 07:11:11","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"TSG SA, SA WG2","lsoriginalls":"S5-240807","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240213.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240214","title":"LS from SA WG5: LS on new definitions of energy efficiency and energy consumption","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to inform SA WG1, SA WG2, RAN WG1, RAN WG2 and RAN WG3 that we have recently introduced definitions of the following terms into TS 28.310: Energy Efficiency (EE): ratio between performance and energy consumption. NOTE: the performance may be measured based on e.g. data volume, latency, number of active users, etc. Energy Consumption (EC): integral of power consumption over time.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10220,"status":"noted","reservation_date":"2024-03-06 17:43:59","uploaded":"2024-03-07 07:11:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, RAN WG1, RAN WG2, RAN WG3","Cc":"TSG SA","lsoriginalls":"S5-240816","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240214.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240215","title":"LS from SA WG5: LS to 5G-ACIA on Management of non-public networks","source":"SA WG5","contact":"Kai Zhang","contact-id":97593,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to inform that it has completed its Release-18 normative work on enhanced management of non-public networks. The main outcomes include (non-exhaustive list): - Specify requirements and solutions for shared and dedicated resources demand for NPN service customers. - Specify requirements and solutions for management of the related information for NPN service customer context information (e.g., identifier of tenant, role, permitted MnSs), which can be applied by NPN service provider to restrict the management capabilities and corresponding managed network resources exposed to NPN service customer. - Specify requirements and solutions for fault management capabilities scoping NPN and UEs representing 5G industry terminals, taking 5G ACIA requirements (such as requirements on network monitoring and network configuration and maintenance for 5G NPN, see 5G-ACIA White Paper: Exposure of 5G Capabilities for Connected Industries and Automation Applications) into account. - Specify requirements and solutions for SLA monitoring and evaluation in NPN scenarios.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10230,"status":"noted","reservation_date":"2024-03-06 17:43:59","uploaded":"2024-03-07 07:11:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5G-ACIA","Cc":"TSG SA, SA WG2","lsoriginalls":"S5-240910","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240215.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240216","title":"LS from SA WG5: LS on metrics to estimate containerized VNF\/VNFC energy consumption","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 has started its Rel-19 study on energy efficiency and energy saving aspects of 5G networks and services. Amongst others, one of the key issues being investigated concerns containerized VNF\/VNFCs estimated energy consumption. In previous releases, SA WG5 defined the KPI for estimated VNF\/VNFC Energy Consumption (cf. TS 28.554 clauses 6.7.3.1.3 to 6.7.3.1.7), based on ETSI NFV-defined metrics such as vCPU usage, vDisk usage, vMemory usage and I\/O traffic of virtual compute resources, defined in clause 7.1 of ETSI GS NFV-IFA 027 V4.0.2 (2020-11) and collected by the 3GPP management system from ETSI MANO. This KPI was considered as valid for VM-based VNF\/VNFCs only, since ETSI NFV had not issued its specifications for containerized VNF\/VNFCs at that time. In our Release 19, we plan to also address containerized VNF\/VNFCs. In this context, we d like to ask ETSI NFV if aforementioned ETSI NFV-defined metrics remain valid for containerized VNF\/VNFCs or if new metrics are planned to be defined. In the latter case, SA WG5 would like to know by when the definition of these new metrics will be publicly available. SA WG5 would like to emphasize that we will continuously do our best to align with ETSI NFV where applicable.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2024-03-06 17:43:59","uploaded":"2024-03-07 07:11:11","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ETSI NFV","Cc":"TSG SA","lsoriginalls":"S5-241059","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240216.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240290","title":"LS from RAN WG2: Reply LS on issues with Packet Uu Loss Rate with delay threshold in the DL per DRB per UE","source":"RAN WG2","contact":"Vinay Shrivastava","contact-id":73424,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 thanks SA WG5 for providing the LS related to Packet Uu Loss Rate with delay threshold. RAN WG2 acknowledges SA WG5 s concern for a potential ambiguity with RAN WG2 specification TS 38.314 clause 4.2.1.5.2 referring to TS 28.552 clause 5.1.1.1.1 that pertains to a measurement for the average (arithmetic mean) time it takes for packet transmission over the air-interface in the downlink direction. However, RAN WG2 specification TS 38.314 clause 4.2.1.5.2 is intended to address the downlink delay of a RLC SDU and not average packet delay. Specifically, it considers 'point in time when the last part of an RLC SDU packet was sent to the UE which was consequently confirmed by reception of HARQ ACK from UE for UM mode or point in time when the last part of an RLC SDU packet was sent to the UE which was consequently confirmed by reception of RLC ACK for AM mode, minus time when corresponding RLC SDU part arriving at MAC layer'. To address the SA WG5 s concern, RAN WG2 has omitted the reference to TS 28.552 clause 5.1.1.1.1 in TS 38.314, while no change in the procedural specification is required. Related CR to TS 38.314 is attached for SA WG5 reference.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10250,"status":"noted","reservation_date":"2024-03-11 15:33:27","uploaded":"2024-03-11 15:36:13","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, RAN WG3","lsoriginalls":"R2-2401676","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240290.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240434","title":"LS from ETSI ISG ISAC: Approval of ETSI ISG ISAC Work Items","source":"ETSI ISG ISAC","contact":"Alain Mourad","contact-id":72138,"tdoctype":"LS in","for":"Information","abstract":"ETSI s Industry Specification Group (ISG) on Integrated Sensing And Communications (ISAC) was officially launched on the 19th September 2023 for an initial phase of two-year duration. During this first phase, ETSI ISG ISAC will prepare systematic output on 6G use cases, channel models, architecture and deployment considerations, KPIs and evaluation assumptions, for subsequent evaluation by standards organizations such as 3GPP future 6G releases and ITU-R IMT-2030 deliverables, thus paving the way for future standardization of this technology. After the kick-off meeting and a first Plenary meeting, ETSI ISG ISAC has approved the first set of four work items (WIs) following from suitable proposals from the Rapporteurs that led to an agreed Work Programme. The group within the first phase of the ISG will be focused on defining use cases and deployment scenarios; covering ISAC channel modeling, measurements and evaluation methodology; discussing System and RAN architectures; and studying the relevant security, privacy, trustworthiness and sustainability aspects of ISAC. A summary of the approved first set of WIs is provided in Table 1. A timeline of execution of the agreed Work Programme in the period 2024-2025 is also provided in Figure 1. ETSI ISG ISAC will consider these reports, which will be streamlined from global pre-standards research efforts, to be instrumental for any further study or specification work in the relevant SDOs (including TSG RAN). {. . .} ETSI ISG ISAC will focus on informative work in this first period including assessing the technology potential of ISAC and providing technical requirements. Further information on the ETSI ISG ISAC terms of reference, work programme, planned deliverables, and other documentations are available through the ISG portal: Link to ISG ISAC Portal.","secretary_remarks":"This was for information block noted.","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2024-03-14 09:40:00","uploaded":"2024-03-14 09:40:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA, External Bodies","Cc":"","lsoriginalls":"ISAC(24)000032","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240434.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-240435","title":"LS from AECC: LS on Updated AECC Publications for Future Connected Vehicle Services","source":"AECC","contact":"Lei Zhong","contact-id":85285,"tdoctype":"LS in","for":"Information","abstract":"The Automotive Edge Computing Consortium (AECC, https:\/\/aecc.org\/) would like to share the recent publications with TSG SA and corresponding WGs for alignment of the potential connected vehicle services in the future. AECC is greatly interested in accelerating the deployment of connected vehicle services based on distributed computing infrastructure. Such a goal is also achieved by identifying, developing and accessing functional and performance requirements of mobile networks and compute platforms, that are deemed important to enable prioritized and high-value automotive services. To this extent, AECC will require standardized solutions which are industry-wide aligned and introduced in the market. {. . .} Action to WGs: AECC kindly invites SA WGs to review and provide feedback to the new contents of AECC publications.","secretary_remarks":"WGs were asked to coordinate any replies to this LS through TSG SA. Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10270,"status":"noted","reservation_date":"2024-03-14 09:40:00","uploaded":"2024-03-14 09:40:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2, SA WG5, SA WG6","lsoriginalls":"AECC_3GPP_LS_Mar2024","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_103_Maastricht_2024-03\/Docs\/SP-240435.zip","group":"SP","meeting":"SP-103","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]