[{"name":"SP-230787","title":"LS from Advanced Television Systems Committee, Inc. (ATSC): RE: Liaison about ATSC 3.0 and 5G","source":"Advanced Television Systems Committee, Inc. (ATSC)","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Action","abstract":"Dear 3GPP Liaison, On behalf of ATSC, I would like to respectfully offer the attached document as a liaison input to the upcoming TSG RAN and TSG SA rel-19 workshops taking place next week. ATSC greatly values cooperative relationships with sister standards development organizations. Many thanks in advance for your kind consideration of the attached document. We welcome any comments or questions you may have. Best regards, Madeleine","secretary_remarks":"Refers to June 2023 Workshops. Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2023-07-31 13:47:12","uploaded":"2023-07-31 13:48:09","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA","Cc":"","lsoriginalls":"ATSC liaison to 3GPP re TG3 input on ATSC 3 and 5G","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230787.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230788","title":"LS from ITU-R WP4B: REPLY LIAISON STATEMENT TO THE ALLIANCE FOR TELECOMMUNICATIONS INDUSTRY SOLUTIONS (ATIS) AND EUROPEAN TELECOMMUNICATIONS STANDARDS INSTITUTE (ETSI) ON 3GPP SUBMISSION TOWARDS IMT-2020 SATELLITE","source":"ITU-R WP4B","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"ITU-R Working Party (WP) 4B would like to thank ATIS and ETSI for their liaison statement (Document 4B\/138) informing on the 3GPP Study Item to prepare submission for radio interface technologies for the satellite component of IMT-2020 and carry-out their self-evaluation. Working Party 4B is pleased to be informed about these developments, and is looking forward to receiving the results of these efforts. The next meeting of WP 4B is planned for 10 January 2024, and will consider the acknowledgement of the submissions received by the 31st December 2023 deadline. Working Party 4B remains committed for continued information exchange with ATIS\/ETSI\/3GPP during the evaluation phase.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2023-07-31 13:47:12","uploaded":"2023-07-31 13:48:09","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ATIS, ETSI, 3GPP","Cc":"","lsoriginalls":"R19-WP4B-230626-TD-0041","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230788.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230789","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ENGAGED IN RECOMMENDATION ITU-R M.2012 ON THE SCHEDULE FOR UPDATING RECOMMENDATION ITU-R M.2012 TO REVISION 7","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"Working Party (WP) 5D thanks the relevant External Organizations for their on-going work regarding the Revision 6 of Recommendation ITU-R M.2012 Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-Advanced (IMT-Advanced) which will be available as a published ITU-R Recommendation. WP 5D wishes to inform the relevant External Organizations that it is commencing the cycle for the development of the Revision 7 of Recommendation ITU-R M.2012 and provides a detailed schedule for Revision 7 of Recommendation ITU R M.2012 .","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2023-07-31 13:47:12","uploaded":"2023-07-31 13:48:09","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"R19-WP5D-230612-TD-0895","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230789.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230791","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS: DRAFT NEW REPORT ITU-R M.[IMT.MULTIMEDIA]","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941,"tdoctype":"LS in","for":"Information","abstract":"Working Party (WP) 5D has finalized the draft new Report ITU-R M.[IMT.MULTIMEDIA] in June 2023 meeting which has been submitted to the parent Study Group 5 for approval (Document 5\/140) and is attached herewith for your reference. Working Party 5D would like to thank the external organisations for their active inputs during the developing process of the draft new Report.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2023-07-31 13:47:12","uploaded":"2023-07-31 13:48:09","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"R19-WP5D-230612-TD-0904!R1!MSW-E_rev_OUT.","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230791.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230792","title":"LS from GSMA OPG: LS on GSMA OPG PRDs publication and document name change","source":"GSMA OPG","contact":"Sandra Ondrusova","contact-id":77474,"tdoctype":"LS in","for":"Information","abstract":"GSMA OPG would like to notify 3GPP and ETSI of the recent release of several GSMA PRDs: OPG.02 Operator Platform: Requirements and Architecture version 5.0. OPG.03 Southbound Interface Network Resources APIs version 3.0. OPG.04 East-Westbound Interface APIs version 3.0. Action: GSMA OPG kindly ask 3GPP and ETSI to take the above into consideration.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-02 11:43:12","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","Cc":"TSG SA","lsoriginalls":"OPG_142_Doc_03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230792.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230793","title":"LS from IEEE 802.1: Liaison response to work items related to deterministic networking in ITU-T SG13","source":"IEEE 802.1","contact":"Glenn Parsons","contact-id":17960,"tdoctype":"LS in","for":"Information","abstract":"The IEEE 802.1 Working Group would like to thank ITU-T Study Group 13 for the information provided in liaison statement SG13-LS86 about Recommendations ITU-T Y.3120 and Y.3121. We would like to inform you that the IEEE 802.1 Working Group has completed its work on the P802.1Qcj Automatic. Attachment to Provider Backbone Bridging (PBB) Services and P802.1Qcw YANG Data Models for Scheduled Traffic, Frame Preemption, and Per-Stream Filtering and Policing projects and has initiated the approval process. Respectfully submitted, Glenn Parsons Chair, IEEE 802.1 Working Group","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-30 06:18:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG13","Cc":"ITU-T SG12, IETF DetNet WG, TSG SA","lsoriginalls":"SP-230793","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230793.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230794","title":"LS from ITU-R WP5D: DRAFT NEW REPORT ITU-R M.[IMT.APPLICATIONS]","source":"ITU-R WP5D","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"At its June 2023 meeting, Working Party (WP) 5D has completed its work towards the development of a Draft New Report ITU-R M.[IMT.APPLICATIONS] on Applications of the terrestrial component of IMT for specific societal, industrial and other usages . The agreed version of the Report has been submitted to the parent Study Group 5 for approval (Document 5\/139) and is attached herewith. Working Party 5D would like to thank the external organisations for their inputs and comments during the development of the report.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-30 06:18:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"R19-WP5D-230612-TD-0888","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230794.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230795","title":"LS from ITU-R WP5D: LIAISON STATEMENT TO EXTERNAL ORGANIZATIONS ON THE SCHEDULE FOR UPDATING RECOMMENDATION ITU-R M.2150 TO REVISION 3","source":"ITU-R WP5D","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"Working Party (WP) 5D thanks the relevant External Organizations for their work regarding Recommendation ITU-R M.2150 Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-2020 (IMT-2020) . As formally announced in ITU-R Circular Letter 5\/LCCE\/109, WP 5D wishes to inform the relevant External Organizations that it is commencing the cycle for the development of the Revision 3 of Recommendation ITU-R M.2150 and provides a detailed schedule for Revision 3 of Recommendation ITU R M.2150 . {. . .} This liaison provides guidance on the revision procedure and the detailed step-by-step schedule to External Organizations regarding updates of the terrestrial radio interfaces in the development of Revision 3 of Recommendation ITU-R M.2150 'Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications-2020 (IMT-2020)'.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-30 06:18:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"R19-WP5D-230612-TD-0917R1","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230795.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230796","title":"LS from CT WG4: IETF HTTP RFCs obsoleted by RFCs 9110, 9111 and 9113","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"5GC specifications refer to several HTTP RFCs that have been obsoleted by new IETF RFCs: - IETF RFC 9110 ('HTTP Semantics', published in June 2022) obsoletes RFCs 7230, 7231, 7232, 7235, 7694. - IETF RFC 9111 ('HTTP Caching', published in June 2022) obsoletes RFC 7234. - IETF RFC 9112 ('HTTP\/1.1', published in June 2022) obsoletes RFC 7230. - IETF RFC 9113 ('HTTP\/2', published in June 2022) obsoletes RFC 7540. Following an analysis of the changes introduced in the new RFCs, CT WG4 has agreed the attached 29.500 CR uplifting the obsoleted HTTP references to the new IETF RFCs from Rel-18 onwards. CT WG4 plans to update the HTTP references of all its TSs for 5GC SBIs in Q4 (TS Rapporteurs have been tasked to bring a related CR to their specifications). CT WG4 kindly asks CT WG1, CT WG3, SA WG3, SA WG4 and SA WG5 to take the above information into account and consider uplifting the HTTP references in their own specifications for 5GC SBIs from Rel-18 onwards.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10120,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-30 06:18:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG3, SA WG3, SA WG4, SA WG5","Cc":"TSG CT, TSG SA, SA WG2","lsoriginalls":"C4-233513","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230796.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230797","title":"LS from SA WG2: Reply LS on support of no-transmit zones for UAVs","source":"SA WG2","contact":"Laeyoung Kim","contact-id":58611,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 would like to thank RAN regarding the LS on support of no-transmit zones for UAVs. SA WG2 discussed potential work on NTZ (no-transmit zone) requirement. The European Conference of Postal and Telecommunications Administrations, Considering l) that a no-transmit zone in this Decision is defined as a geographical area where aerial UE are not allowed to transmit for spectrum compatibility purposes in a given harmonised MFCN band or part of it; m) that national studies are needed, as appropriate, to define no-transmit zones for spectrum compatibility purposes, for aerial UE operating in the relevant frequency bands; n) that a mechanism is necessary to ensure that aerial UE respect no-transmit zones; DECIDES . that no-transmit zones as described in this Decision should be defined and implemented at national level and where necessary coordinated with neighbouring countries; TSG RAN agreed that the above requirement will be addressed. But in order to know if and what the impact might be to RAN WGs, TSG RAN would like to know whether and how SA WG2 intends to address these operational requirements for geographical no-transmit zones (e.g. at application layer). Action: Given the need to respond to ECC, TSG RAN respectfully asks SA WG2 for their view on solutions to support geographical no-transmit zones for UAVs according to the operational restrictions outlined in CEPT Decision 22(07), including whether and how SA WG2 intends to address this and\/or whether RAN WGs should consider solutions. SA WG2 would like to provide the following feedback: SA WG2 has not discussed about the NTZ requirement under Rel-18 study and normative phases for UAS_Ph2 because this requirement is not in the scope of Rel-18 UAS_Ph2, and has no plan to do work related to the NTZ requirement in Rel-18. SA WG2 is considering the NTZ requirement in the potential Rel-19 study item to discuss and consider it from system perspective.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-30 06:18:49","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN","Cc":"TSG SA","lsoriginalls":"S2-2310000","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230797.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230799","title":"LS from SA WG5: Reply to LS on customer acceptance of limited QoS degradation to save energy in the network","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG1 for your Reply LS on customer acceptance of limited QoS degradation to save energy in the network. SA WG5 acknowledges that: 1. no compromise on user experience while achieving energy efficiency has been considered so far in SA WG1; 2. 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 best-effort communication service; 3. 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). SA WG5 understanding of the use case described in TR 22.882 clause 5.1 is that, based on its own policies, the CSP \/ Network Operator may trigger energy saving actions in its network, while respecting agreed SLA. In the SA WG5 potential use case, the energy saving actions are triggered upon request from the customer: QoS degradation (also within agreed SLA) is requested by the customer, provided a) it results in energy savings in the Network Operator s network and b) these energy savings can be measured, imputable and reported to the customer. SA WG5 would like to have further exchange with SA WG1 on this topic during our respective R19 work.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-30 06:18:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"TSG SA, SA WG2","lsoriginalls":"S5-235364","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230799.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230801","title":"LS from SA WG5: Reply to LS on 3GPP work on energy efficiency","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG4 for your Reply LS on 3GPP work on energy efficiency. SA WG5 would like to provide the following replies to SA WG4 questions: 0. SA WG4 statement: SA WG4 suggests that SA WG5 clarify that the work on Energy Efficiency also includes measurement and evaluation of UE performance SA WG5 reply: SA WG5 has no Rel-18 work on the energy efficiency of the UE. Other WGs are welcome to inform us in case they have any work on UE energy efficiency. 1. 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. 2. SA WG4 request: A request for more details on whether the 3GPP\/SA WG5 Rel-18 work item will focus on: a. What can be done now with options\/settings in the implementation and deployments of already existing specifications. b. What more we can do in Rel-18. c. Extending this work to a broader and perpetual Work Item in every release from Rel-18 onwards or an introduce an umbrella work item like the TEI that encourages all the 3GPP WGs to develop features to address the climate emergency and tracking these features. SA WG5 reply: SA WG5 Rel-18 study item on energy efficiency had one of its objectives focusing on digital sobriety which included a) studying which forms digital sobriety could take in SA WG5, e.g. minimize the volume of OA&M data (number of operation parameters, input data to MDAF, etc.) to be processed and\/or transported and\/or stored and b) studying if any metrics could be defined to compare different alternative solutions with regards to digital sobriety. This Rel-18 study on EE has been completed in June 2023; no potential solution has been agreed and therefore has been pushed to the normative work. 3. SA WG4 proposal: A proposal that builds on the efforts in the SA WG1 Study on Energy Efficiency as service criteria (FS_EnergyServ) to develop technology to achieve energy savings and other green objectives potentially at the expense of some level of degradation of QoE. To provide truly effective solutions, networks and devices should be equipped with technologies that enable operating points that can trade-off some level of QoE and other KPIs for energy efficiency and other green objectives, i.e., providing the 3GPP equivalents of a bicycle option, instead of automobile transportation for users. SA WG5 reply: SA WG5 would like to inform SA WG4 that we have sent out a LS to SA WG1 (S5-232758 on customer acceptance of limited QoS degradation to save energy in the network from SA WG5 - attached). This LS describes a use case where some customers (e.g. from Verticals) may be willing to cooperate with their service providers to reduce their Scope 3 emissions. In the context of 5G services and, in particular, the network slice(s) they get from their Network Slice Provider (NSP), they could decide to accept some limited QoS degradation from their NSP. 4. SA WG4 statement: Continue to investigate how we can address the above issues as part of our regular wo","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10160,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-30 06:18:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"TSG SA, SA WG1, SA WG2, SA WG3, SA WG6","lsoriginalls":"S5-235778","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230801.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"SP-230802","title":"LS from SA WG5: LS to CT4 on documenting code in Forge-GitLab","source":"SA WG5","contact":"Balazs Lengyel","contact-id":81420,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 intends to facilitate the specification of the optional new methodology of storing code normatively in Forge, based on attachment 1. For some of its documents SA WG5 intends to start storing code normatively in Forge. SA WG5 sees major advantages in storing code normatively in Forge. This should not impact other groups. The intent is to get the attached draftCR for 29.501 converted to a real CR and get it approved.","secretary_remarks":"Noted","agenda_item_sort_order":9,"ainumber":"2.1","ainame":"Incoming LSs - proposed to note","tdoc_agenda_sort_order":10150,"status":"noted","reservation_date":"2023-07-31 13:53:13","uploaded":"2023-08-30 06:18:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1, CT WG3, TSG CT, SA WG4, TSG SA","lsoriginalls":"S5-235855","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/TSG_SA\/TSG_SA\/TSGs_101_Bangalore_2023-09\/Docs\/SP-230802.zip","group":"SP","meeting":"SP-101","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]