[{"name":"SP-230397","title":"LS from SA WG6: LS on SA6 V2X service support","source":"SA WG6","contact":"Emmanouil Pateromichelakis","contact-id":94983,"tdoctype":"LS in","for":"Action","abstract":"In SA WG6#52-bis-e, SA WG6 received (in cc) a Reply LS on QoS Sustainability analytics and V2X service adaptations (SP-221320) which provided a consolidated answers from SA WG1 and SA WG2 on the 5GAA LS on QoS Sustainability analytics and V2X service adaptations (S-220077). The 5GAA LS was pointing to a technical report (5GAA_T-220058_WI-PRESA-Technical-Report), which included some requirements and assumptions on the current 3GPP support to support these requirements. After careful review of the technical report and the questions, we found that some concepts described in the technical report and some requirements for 3GPP can be applicable to SA WG6 work. Therefore, we would like to provide the latest updates of SA WG6 related work. Action: SA WG6 kindly requests TSG SA to take into account SA WG6 status related to supporting 5GAA requirements and provide the content of this LS on behalf of 3GPP to 5GAA.","secretary_remarks":"Postponed SP-230028 from SP-99E. Response drafted in SP-230734. 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-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"SP-230028","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2","lsoriginalls":"S6-231091","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230397.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230399","title":"LS from GSMA 5GMRR: LS to 3GPP (SA, SA1, SA2, SA3, CT4) on GSMA requirements regarding intermediaries in the roaming ecosystem","source":"GSMA 5GMRR","contact":"Kathleen Leach","contact-id":87129,"tdoctype":"LS in","for":"Action","abstract":"Overall Description: 5GMRR would like to provide 3GPP with requirements, as requested by 3GPP, for the major intermediaries and services (Roaming Hub, IPX and RVAS Providers) needed within the roaming ecosystem. The requirements outline support for the use cases that are established in roaming to date and that are also required in 5G SA roaming and interconnect. Actions: GSMA NRG 5GMRR kindly requests 3GPP to consider the above entities in their specifications and the related service requirements for roaming ecosystem intermediaries per role (RH, IPX Provider, RVAS Provider) as provided per separate LSs. Please provide advice on how they can be supported using current specifications. Moreover, the group kindly requests SA WG1, SA WG2 and SA WG3 and CT WG4 to also consider updating their specifications at the earliest possible release in order to support requirements that are currently not covered. This will allow the GSMA to support the use cases that are established in roaming currently and that should be provided for 5G SA roaming and interconnect, too. Please note that the above roles can have overlapping requirements. 5GMRR would like to work together with 3GPP in order to develop solutions that meet these requirements while complying to the 5GS architecture and security specifications.","secretary_remarks":"Postponed SP-230350 from SP-99E. Response drafted in SP-230740. Final response in SP-230763","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10300,"status":"replied to","reservation_date":"2023-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"SP-230350","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG1, SA WG2, SA WG3","Cc":"CT WG4","lsoriginalls":"5GMRR Doc 41_37r2","lsreply":"SP-230763","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230399.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230400","title":"LS from CT WG1: Reply LS on 3GPP work on Energy Efficiency","source":"CT WG1","contact":"Christian Herrero-Veron","contact-id":45210,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank SA WG5 for their LS on 3GPP work on Energy Efficiency. CT WG1 would like to inform that at present, there is not any CT WG1-led Rel-18 work item related to Energy Efficiency.","secretary_remarks":"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":"2023-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, TSG RAN, TSG CT, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, CT WG3, CT WG4","lsoriginalls":"C1-232650","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230400.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230401","title":"LS from CT WG3: Reply LS on 3GPP work on Energy Efficiency","source":"CT WG3","contact":"Abdessamad EL MOATAMID","contact-id":89270,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 thanks SA WG5 for their LS on 3GPP work on Energy Efficiency. CT WG3 would like to inform SA WG5 that it is currently not undertaking any work related to energy efficiency, energy saving and\/or digital sobriety in Rel-18. CT WG3 will keep SA WG5 informed if there is any change.","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":"2023-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"CT WG1, CT WG3, CT WG4, TSG CT, TSG SA, TSG RAN, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4","lsoriginalls":"C3-231470","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230401.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230403","title":"LS from SA WG3: LS on Roaming architecture updates","source":"SA WG3","contact":"Alf Zugenmaier","contact-id":52494,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 is discussing the following LSs from GSMA 5GMRR on requirements in 5GS roaming. {. . .} SA WG3 asks SA WG2 to define a solution that allows to provide the additional services requested by 5GMRR. SA WG3 is open for this to be a collaborative effort between SA WG2 and SA WG3. SA WG3 will then work to provide a security solution. SA WG3 would also like to ask SA WG1 whether they plan to document the service requirements to be supported by 5G for roaming as formulated by 5GMRR in the recent LSs (and in Rel-16 by GSMA) or whether SA WG2 and SA WG3 could proceed without SA WG1 being involved. So far, N32 security and roaming requirements have been handled between GSMA and SA WG3 directly leading to the current e2e security roaming architecture.","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":"2023-04-27 14:31:54","uploaded":"2023-05-02 16:10:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG1","Cc":"TSG SA, CT WG4","lsoriginalls":"S3-232155","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230403.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230415","title":"LS from CT WG1: Reply LS on having OpenAPI changes only in GitLab","source":"CT WG1","contact":"Christian Herrero-Veron","contact-id":45210,"tdoctype":"LS in","for":"Action","abstract":"CT1 thanks CT3 and CT4 from their jointly provided LS on having OpenAPI changes only in GitLab.CT1 has discussed the information provided by CT3 and CT4 and CT1 would also like to continue using the existing method of handling source code in 3GPP documentation for specifications under its remit.Finally, CT1 wants also to continue applying the same methodology and process as per CT3 and CT4.2. Actions:To CT, SA, CT WG3, CT WG4 groups.ACTION: CT WG1 requests CT, SA, CT WG3 and CT WG4 to take the information provided by this LS into account in their discussion on defining a Forge-based method of handling source code in 3GPP documentation.","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":"2023-04-27 14:31:54","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, TSG SA, CT WG3, CT WG4","Cc":"SA WG5","lsoriginalls":"C1-234390","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230415.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230416","title":"LS from CT WG3, CT WG4: LS on having OpenAPI changes only in GitLab","source":"CT WG3, CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"CT3\/CT4 have briefly discussed the proposal submitted to TSG SA#99 of defining a Forge-based method of handling source code in 3GPP documentation and whether it could be applicable to CT3 and CT4 APIs. See SP-230391 (Using Forge-Git as the primary storage for Code).While CT3\/CT4 do not challenge that SA5 may adopt the new methodology, CT3\/CT4 want to stick to the existing method (which does not modify the existing 3GPP CR process) of handling source code in 3GPP documentation for specifications under their remit, i.e.:- with technical specifications containing the formal interface definition (e.g. OpenAPI definition) in normative annexes of the specification in MS Word text; and - with self-contained CRs including changes to the main body of the TS and to the normative annexes.The existing process has proven to work satisfactorily in CT3\/CT4 during the last 4 years of intensive usage of the 3GPP Forge\/GitLab, which has lowered the number of syntax faults in the OpenAPI specifications to essentially zero. It also ensures that tracking of changes in OpenAPI \"code\" is always possible (maybe after many years after the actual CR approval). A tool (at the disposal of MCC) can be run to check that the contents of OpenAPI definitions are identical in normative annexes and zip files of TSs and in 3GPP GitLab.The Forge-based method (i.e., having CRs without explicit track-marked changes on the code, and replacing it with a link to a GitLab commit or Merge Request) would not remove the need for TS Rapporteurs to validate that all the CRs approved during a Plenary cycle result in technically correct OpenAPI files. CT3\/CT4 also recommend using the same methodology within CT WGs for consistency and simplification of the processes and tooling in 3GPP GitLab for CT WGs. 2. Actions:To CT and SA groups.ACTION: CT3\/CT4 ask CT and SA 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":10430,"status":"noted","reservation_date":"2023-04-27 14:31:54","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT","Cc":"CT WG1","lsoriginalls":"C3-232461","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230416.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230419","title":"LS from CT WG4: Reply LS on 3GPP work on Energy Efficiency","source":"CT WG4","contact":"Hao Jing","contact-id":93660,"tdoctype":"LS in","for":"Information","abstract":"CT4 would like to thank SA5 for their LS on 3GPP work on Energy Efficiency.CT4 would like to inform SA5 that there is not any CT4 Rel-18 work item related to Energy Efficiency. CT4 will keep SA5 informed if there is any change.","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":"2023-04-27 14:31:54","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA","lsoriginalls":"C4-232465","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230419.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230420","title":"LS from SA WG1: Reply LS on customer acceptance of limited QoS degradation to save energy in the network","source":"SA WG1","contact":"Xiaonan Shi","contact-id":87257,"tdoctype":"LS in","for":"Information","abstract":"SA1 thanks SA5 for this LS on customer acceptance of limited QoS degradation to save energy in the network. SA1 would like to inform that there is currently no active study nor work item on Rel-18 addressing the requested topics. However, SA1 has an ongoing study in Rel-19 named \u201cFS_EnergyServ\u201d focused on energy efficiency as service criteria. In this study, SA1 follows the guidance from SA LS on energy efficiency sent at SA #94e 12.21 (SP-211621), which is further referenced in TR 22.882 [1] (currently in v1.0.0), clause 5.1.1: \"The EE-specific efforts so far undertaken e.g., in SA5 have aimed mostly at improving the energy efficiency by impacting the operations of the system. As we now are starting to specify the 5G-Advanced features, TSG SA kindly requests the recipient WGs and TSGs to consider EE even more as a guiding principle when developing new solutions and evolving the 3GPP systems specification, in addition to the other established principles of 3GPP system design.TSG SA clarifies that in addition to EE, other system level criteria shall continue to be met (i.e. the energy efficiency aspects of a solution defined in 3GPP is not to be interpreted to take priority or to be alternative to security, privacy, complexity etc. and to meeting the requirements and performance targets of the specific feature(s) the solution addresses).\"So no compromise on user experience while achieving energy efficiency has been considered so far in SA1. However, there are some use cases in TR 22.882, such as in clause 5.1, where a maximum energy utilization rate can be defined to limit the energy consumption of a \u201cbest-effort\u201d communication service. And clause 5.2 defines potential requirements so that the 5G system can support different energy states of network elements and network functions, e.g., in different timeslots. In general, FS_EnergyServ has considered user\/vertical\u2019s preferences in energy saving. All adjustments in QoS or other actions influencing user experience are considered under the scope of pre-configured SLA (e.g. within the boundaries of an acceptable QoS provided to end user applications).Potential benefits of such use case may be evaluated, in particular for the end user. In order to discuss this topic, SA1 would like to invite individual companies to submit use case proposals as contributions to the relevant SA1 study\/work items.","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":"2023-04-27 14:31:54","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"GSMA ENSWI","lsoriginalls":"S1-231468","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230420.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230421","title":"LS from SA WG1: LS on Metaverse requirements and KPIs","source":"SA WG1","contact":"Laurent Walter Goix","contact-id":99061,"tdoctype":"LS in","for":"Information","abstract":"3GPP TSG SA WG1 (SA1, Services) considers and studies new and enhanced services, features, and capabilities and identifies any corresponding stage 1 requirements to be met by 3GPP specifications.SA1 has an ongoing feasibility study in Rel-19 on Localized Mobile Metaverse Services. As part of this study, whose results are captured in 3GPP Technical Report 22.856 [1], there are new consolidated requirements and KPIs defined in clauses 7.1 and 7.2 respectively.In addition, SA1 has already specified XR-related requirements as part of its 3GPP Technical Specification 22.261 \u201cService requirements for the 5G system; Stage 1\u201d [2], in particular in clauses 6.43, 7.6 and 7.11.SA1 would also like to share that the normative requirements that will derive from this study are likely to be specified by the end of 2023 (expected 3GPP Rel-19 stage 1 freeze). However, Metaverse-related topics may be further addressed by SA1 at a later stage.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10390,"status":"noted","reservation_date":"2023-04-27 14:31:54","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Metaverse Standards Forum (MSF)","Cc":"TSG SA","lsoriginalls":"S1-231729","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230421.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230422","title":"LS from SA WG1: LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"SA WG1","contact":"Kurt Bischinger","contact-id":26063,"tdoctype":"LS in","for":"Action","abstract":"SA1 has discussed the LSs from GSMA 5GMRR, S1-231055, 056, 057 and 058 as well as the LS from SA3 S1-231034, and concluded that a SA1 study would be needed to describe and discuss the use cases and derive potential service requirements. SA1 suggest SA to inform GSMA 5GMRR that SA1 welcomes all interested parties to contribute in SA1 with their use cases and requirements.2 ActionsTo SA ACTION: SA1 asks SA to take the above information into account when replying to GSMA 5GMRR.","secretary_remarks":"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-04-27 14:31:54","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG2","lsoriginalls":"S1-231776","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230422.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230423","title":"LS from SA WG1: Reply LS on 3GPP work on Energy Efficiency","source":"SA WG1","contact":"Laurent Walter Goix","contact-id":99061,"tdoctype":"LS in","for":"Information","abstract":"SA1 thanks SA5 for their LS S5-232903, and questions. SA1 answers and clarifications are provided below:Q1: Please correct and\/or complement the table present in the attached document if and where deemed appropriate. [SA1 answer]: SA1 would like to inform that there is no ongoing study related to Rel-18 anymore. However, SA1 provides an update to the table provided by SA5 here below. Note that the ongoing SID on \u201cEnergy Efficiency as service criteria\u201d (SP-230235) relates to Rel-19 and not Rel-18.For SA5 convenience, changes below are provided as highlighted text (new text in red, old text strikethrough).. . .Q2: Please keep SA5 informed in case of new Rel-18 SI\/WI addressing energy efficiency and\/or energy saving and\/or digital sobriety, so that SA5 can maintain such information for the Rel-18 or later release timeframe.[SA1 answer]: SA1 has currently no active study nor work item on Rel-18 addressing the requested topics. However, SA1 has an ongoing study in Rel-19 named \u201cEnergyServ\u201d focused on energy efficiency as service criteria. There is no plan in SA1 to study the requested topics in further studies within Rel-19.","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":"2023-04-27 14:31:54","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, TSG RAN, TSG CT, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, CT WG3","lsoriginalls":"S1-231805","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230423.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230424","title":"LS from SA WG2: LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"SA WG2","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"LS in","for":"Action","abstract":"SA2 has discussed the LSs from GSMA 5GMRR, S2-2306270, 6271, 6272, 6273, and LS in S2-2306304 from SA3 and concluded that use cases and service requirements need to be clarified by SA1 before work can be started in SA2 and SA2 will then analyze whether and which agreed requirements and use cases can be supported by the current specifications or require extensions. Any such work is expected to follow the usual 3GPP process.2 ActionsTo SA ACTION: SA2 asks SA to provide guidance to SA2 how to proceed and to take the above information into account when replying to GSMA 5GMRR.","secretary_remarks":"Noted","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-04-27 14:31:55","uploaded":"2023-06-01 12:56:19","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1","lsoriginalls":"S2-2307983","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230424.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230425","title":"LS from SA WG3: LS on Further input to address GSMA LS on requirements for intermediaries in the roaming ecosystem (S3-232344)","source":"SA WG3","contact":"Anja Jerichow","contact-id":68341,"tdoctype":"LS in","for":"Action","abstract":"In addition to SA3 response in LS S3-232155, SA3 would like to provide further input to 3GPP working groups in preparation of a consolidated 3GPP response to GSMA.Document S3-233349 provides an overview of related requirements captured in 3GPP. After having reviewed the requirements, SA3 believes that further refinement and clarification is needed, as follows. . . .2 ActionsTo SA, SA1, SA2, CT4 ACTION: SA1 to consider specific studies for the use cases and consolidate the requirements provided by GSMA. SA2 to take the above information into account also in the context of LS S3-232155 and provide SA1 with an initial evaluation on architecture impact of the new solutions in the table above. SA plenary to prioritize work on N32\/SEPP topics to study which requirements may be enabled with the current 5G architecture. SA plenary to develop a position regarding requirements that are within\/outside 3GPP scope and to ask 5GMRR to- provide feedback on above position,- consolidate the set of requirements, - provide a statement on regional legislative requirements on privacy and data protection,- point out, for each requirement separately, whether PRINS as currently specified can be used to meet the requirement and, if not, what the problem appears to be. For example, many requirements appear to be satisfied if most IEs are sent in clear text (PRINS scheme allows for this).- provide feedback with respect to S3-231419, i.e., whether the proposed enhancements for PRINS cover the requirements as they enable middle box to trigger their own signalling (see Enhanced PRINS summary). A response per each individual requirement would be desirable for this question, too. - explain how to handle IEs in any hop-by-hop approach if confidentiality of IEs is required., given that any hop-by-hop solution will not be able to achieve this (e.g., in the light of legislative regional requirements on privacy).CT4 to take the information into account and if applicable, provide additional input.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10340,"status":"noted","reservation_date":"2023-04-27 14:31:55","uploaded":"2023-06-01 12:56:19","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2","lsoriginalls":"S3-233308","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230425.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230426","title":"LS from SA WG4: LS on Metaverse Standards Forum (MSF)","source":"SA WG4","contact":"Frederic Gabin","contact-id":104857,"tdoctype":"LS in","for":"Action","abstract":"SA4 would like to inform SA1, SA, RAN and CT about the Metaverse Standards Forum Standards register.The Metaverse Standards Forum as launched in mid of 2022 is moving ahead. The global participation in the Forum enables a unique opportunity for metaverse standards cooperation, coordination and leadership for Forum members to accelerate their objectives. . . .2 ActionsTo SA, RAN, CTSA4 recommends SA, RAN and CT to identify and inform the relevant 3GPP WGs and ask them to designate at least one representative for the MSF Register. The representative would then be responsible to collect the respective WG related Metaverse specifications and projects and submit the information to the Metaverse Standards Register.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10400,"status":"noted","reservation_date":"2023-04-27 14:31:55","uploaded":"2023-06-01 12:56:19","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, TSG SA, TSG RAN","Cc":"","lsoriginalls":"S4-231082","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230426.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230427","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":"SA4 acknowledges 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":"Postponed","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10370,"status":"postponed","reservation_date":"2023-04-27 14:31:55","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"SP-230786","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_100_Taipei_2023-06\/Docs\/SP-230427.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230428","title":"LS from SA WG4: LS on 3GPP work on Energy Efficiency","source":"SA WG4","contact":"Nikolai Leung","contact-id":38562,"tdoctype":"LS in","for":"Action","abstract":"SA4 fully supports SA5\u2019s and 3GPP\u2019s overall efforts addressing energy efficiency and the ongoing climate emergency.","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":"2023-04-27 14:31:55","uploaded":"2023-06-01 12:56:18","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, TSG SA, TSG RAN","Cc":"SA WG1, SA WG2, SA WG3, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, CT WG1, CT WG3","lsoriginalls":"S4-231111","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230428.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230717","title":"Using Forge-Git as the primary storage for Code","source":"SA WG5 Chair","contact":"Thomas Tovinger","contact-id":3654,"tdoctype":"discussion","for":"Endorsement","abstract":"This is an update of SP-230391 from SA#99 with Annex B added to provide answers to the questions raised at SA#99.","secretary_remarks":"Noted. SA WG5 will bring a proposal for endorsement at the next meeting","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":"2023-06-05 16:57:30","uploaded":"2023-06-07 21:21:44","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_100_Taipei_2023-06\/Docs\/SP-230717.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230718","title":"Transfer the ownership of EVEX specifications","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"discussion","for":"Approval","abstract":"Discusses the ownership of EVEX framework specifications up to rel.18 and in rel.19 and beyond.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10380,"status":"noted","reservation_date":"2023-06-06 19:03:18","uploaded":"2023-06-07 16:53:36","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"EVEX"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230718.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230734","title":"[DRAFT] Reply LS on QoS Sustainability analytics and V2X service adaptations (SA WG6 aspects)","source":"Lenovo","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"LS out","for":"Approval","abstract":"To: 5GAA Working Group 4, Working Group 1, Working Group 2. CC: SA WG6","secretary_remarks":"Response to SP-230397. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10290,"status":"noted","reservation_date":"2023-06-07 16:33:18","uploaded":"2023-06-07 16:41:56","revisionof":"","revisedto":"SP-231104","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5GAA Working Group 4, Working Group 1, Working Group 2","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230734.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230740","title":"Reply LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"TSG SA","contact":"Johannes Achter","contact-id":94365,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA 5GMRR. CC: SA WG1, SA WG2, SA WG3, SA WG5, CT WG4","secretary_remarks":"Created at meeting. Response to SP-230399. Revised to SP-230763.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2023-06-13 09:59:35","uploaded":"2023-06-16 00:11:05","revisionof":"","revisedto":"SP-230763","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GMRR","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230740.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230741","title":"LS on 3GPP related Metaverse specifications and activities","source":"TSG SA","contact":"Frederic Gabin","contact-id":104857,"tdoctype":"LS out","for":"Approval","abstract":"To: Metaverse Standards Forum (MSF). CC: SA WG1, SA WG4, TSG RAN, TSG CT","secretary_remarks":"Created at meeting. 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":"2023-06-13 09:59:35","uploaded":"2023-06-16 00:11:05","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Metaverse Standards Forum (MSF)","Cc":"SA WG1, SA WG4, TSG RAN, TSG CT","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230741.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230763","title":"Reply LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"TSG SA","contact":"Johannes Achter","contact-id":94365,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA 5GMRR. CC: SA WG1, SA WG2, SA WG3, SA WG5, CT WG4","secretary_remarks":"Revision of SP-230740. Approved. Guidance to WGs agreed.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10360,"status":"approved","reservation_date":"2023-06-15 23:59:52","uploaded":"2023-06-16 00:11:05","revisionof":"SP-230740","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-230399","lsto":"GSMA 5GMRR","Cc":"SA WG1, SA WG2, SA WG3, SA WG5, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGS_100_Taipei_2023-06\/Docs\/SP-230763.zip","group":"SP","meeting":"SP-100","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]