[{"name":"SP-220005","title":"LS from APT Wireless Group: APT REPORT ON EMERGING CRITICAL APPLICATIONS & USE CASES OF IMT FOR INDUSTRIAL, SOCIETAL AND ENTERPRISE USERS","source":"APT Wireless Group","contact":"BHARAT BHATIA","contact-id":46829.0,"tdoctype":"LS in","for":"Action","abstract":"The AWG is developing a working document towards an APT Report on 'EMERGING CRITICAL APPLICATIONS & USE CASES OF IMT FOR INDUSTRIAL, SOCIETAL AND ENTERPRISE USERS' The scope of the report is on new\/emerging critical applications and use cases of IMT-Advanced and IMT-2020 for industrial, societal and enterprise users, both 4G LTE and NR. Current draft working document being developed in the AWG is enclosed for reference. As SA WG6 (SA WG6) is the application enablement and critical communication applications group for critical applications of IMT, AWG would kindly invite the 3GPP to provide relevant materials, use cases and any other related material that would facilitate in completion of this Report. AWG would appreciate 3GPP to provide any feedback before the next 29th APT Wireless Group (AWG-29) meeting, scheduled in March\/April 2022, if any. For technical queries please contact: Mr. Bharat Bhatia ITU-APT Foundation of India +91 9810173737 Email: Bharat.bhatia@itu-apt.org AWG will keep 3GPP informed of the progress and outcomes of relevant studies in future AWG meetings. Mr. Le Van Tuan Chairman APT Wireless Group","secretary_remarks":"Revision of Postponed SP-211247 from SA#94-e. CC#2: 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":"2022-01-19 14:13:41","uploaded":"2022-01-19 14:14:22","revisionof":"SP-211247","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG6","Cc":"","lsoriginalls":"AWG28\/OUT03 (Rev.1)","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220005.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220007","title":"LS from ETSI BOARD TREND: ETSI Technology Radar, status and request for feed-back","source":"ETSI BOARD TREND","contact":"Christian Toche","contact-id":23029.0,"tdoctype":"LS in","for":"Action","abstract":"Overall description: During the period 2020-2021, the ETSI BOARD TREND group performed a thorough analysis of various market reports, analyst papers, market surveys and other relevant literature in order to identify the most relevant future technology trends relating to the ICT sector. The result of this work can be found in the ETSI Technology Radar (ETR), published as a whitepaper in April 2021. https:\/\/www.etsi.org\/images\/files\/ETSIWhitePapers\/etsi_wp45_ETSI_technology_radar.pdf The ETR describes, from a relatively high perspective, the 10 most predominant ICT trends for the coming years. For each selected technology trend, the ETR identifies; - affinities and\/or eventual gaps with respect to current ETSI activities as documented in the ETSI Work Programme 2020\/21, - the definition of an estimated time frame of maturity for standardization activities, - a set of recommendations for future more detailed analysis at ETSI OCG and\/or ETSI Board level on the eventual way forward to fill the identified standards gaps. The ETSI Technology Radar is intended to be updated at regular intervals, with the next edi-tion being planned for the end of 2022. The revision will include updates to the already se-lected (10) technology trends as well as the addition of new trends as they become relevant in the ICT space. The ETR was recently presented to the OCG and the presentation can be accessed from the ETSI portal https:\/\/docbox.etsi.org\/OCG\/OCG\/05-CONTRIBUTIONS\/2021\/OCG(21)000005_Presenting_the_ETR_to_the_OCG.pptx. Actions: BOARD_TREND would like to invite your group and\/or individuals within your group to con-sider and possibly review the identified technology trends and to provide any observations back to the BOARD_TREND group. Comments and suggestions are encouraged on the exist-ing (10) trends (see next figure).","secretary_remarks":"CC#2: 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":"2022-01-19 14:13:41","uploaded":"2022-01-19 14:14:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"All ETSI TBs, ISGs, oneM2M TC, TSG SA, SA WG1","Cc":"OCG","lsoriginalls":"BOARDTREND(21)010005r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220007.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220009","title":"LS from SMPTE: PTP device monitoring Public Committee Draft To: 3GPP","source":"SMPTE","contact":"Maurice Pope","contact-id":648.0,"tdoctype":"LS in","for":"Information","abstract":"Dear 3GPP Liaison Officer, As previously informed in our April 2021 liaison, SMPTE Drafting Group on PTP monitoring (TC-32NF-80 DG on ST 2059-2 PTP Device Monitoring) is developing an engineering document that will provide guidance on implementing PTP monitoring in professional media equipment. The intention is to provide a data set that enables the monitoring of elements found in PTP systems with parameters that are specific to SMPTE clearly identified and separated from parameters that are common to generic PTP systems. The group has designed a YANG Data Model based upon the IETF RFC 8575 that has been adapted to align with the SMPTE ST 2059-2 PTP profile. The group has included PTP monitoring elements from IEEE 1588:2019 that are not defined in 1588:2008 (and by extension are not available in RFC 8575) and has worked to ensured that the PTP container is closely aligned with the ongoing work of the IEEE 1588e group. For the wider PTP Ecosystem the group has then extended this work to include additional containers covering further parameters that are outside the scope of the IEEE 1588 syntax but are essential to the monitoring of the overall health of the wider PTP ecosystem. These additional containers have been included at root level and describe parameter sets relating to the monitoring of GNSS, antenna systems, and grandmaster equipment which are common to many PTP systems and not specific to SMPTE. Parameters specific to SMPTE are defined in a separate container. The collective feedback we received from numerous sources across the media and timing related industries has been taken onboard thereby contributing to define a new revision of the SMPTE RP 2059-15 Public Committee Draft 2 (PCD2) publicly accessible online at the following location: https:\/\/github.com\/SMPTE\/rp2059-15 Additionally, a webcast was recorded to provide further insight into the goals and objectives of the RP 2059-15 initiative. The recording has been posted and made publicly available at the following location: https:\/\/www.smpte.org\/webcast\/rp-2059-15-unify-monitoring-smpte-st-2059-2-ptp-network-devices To finalize RP 2059-15, SMPTE is seeking further feedback on the proposed data model to ensure it will match industry expectations in terms of capabilities and usability across several use cases. SMPTE would appreciate feedback on the proposed PTP monitoring YANG data model, from 3GPP and its membership, via the GitHub tools, conventional correspondence, and the online survey available at the following location: https:\/\/www.surveymonkey.com\/r\/29GGT87 Please send conventional correspondence to svp@smpte.org with cc: to liaisons-chair@smpte.org. Many thanks & best regards, Florian Schleich SMPTE Standards Vice-President","secretary_remarks":"CC#2: 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":"2022-01-24 10:17:48","uploaded":"2022-01-24 10:18:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"","lsoriginalls":"SLC04-smpte-to-3GPP-PCD-RP2059-15-PCD2-2022-01-18","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220009.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220011","title":"LS from CT WG1: LS on spoofing using national numbers","source":"CT WG1","contact":"J\u00f6rgen Axell","contact-id":36534.0,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has received an LS from ITU-T SG2 that they have started work on call spoofing. CT WG1 wants to provide information to TSG CT and TSG SA about work carried out in CT WG1 that TSG CT and TSG SA may use to provide feedback to ITU-T SG2. CT WG1 started in rel-14 (WI SPECTRE), and continued in rel-15 (WI eSPECTRE) to work on call spoofing prevention based on the work in IETF STIR WG. While ITU-T work is focussed on barring calls from potentially fraudulent sources, CT WG1 work has been focussed on ensuring that the originating identity can be verified at the terminating network and is based on the Identity header field specified in IETF RFC 8224, using PASSPorTs defined in RFC 8588 and RFC 8946. The 3GPP solution has been specified in 3GPP TS 24.229 from rel-15. 3GPP currently has an ongoing WI (TEI17_SAPES) to extend the mechanism for originating identity verification to also protect values in the Resource-Priority header field and the 'psap-callback' value in the Priority header field. Action: CT WG1 asks TSG CT and TSG SA to take the information into account and if seen needed provide this information along with information from other WGs to ITU-T.","secretary_remarks":"CC#2: 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":"2022-02-09 08:09:55","uploaded":"2022-02-09 08:11:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, TSG SA","Cc":"","lsoriginalls":"C1-220845","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220011.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220012","title":"LS from SA WG5: Reply LS on autonomous network levels (reply to S5-221478)","source":"SA WG5","contact":"Xi Cao","contact-id":83332.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank ITU-T SG2 for the LS\/r on autonomous network levels (reply to SA WG5-S5-215539). Thank you for clarifying the scope of M.il-AITOM and sharing the progress of ITU-T draft Recommendation M.il-AITOM to SA WG5. SA WG5 would also like to inform ITU-T SG2 that SA WG5 has completed the Release 17 work on autonomous network levels, the study output is captured in TR 28.810 V17.0.0, and the normative work is captured in TS 28.100 V17.0.0. Reference documents are: - 3GPP TR 28.810 (Study on concept, requirements and solutions for levels of autonomous network). Availabe at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3683 - 3GPP TS 28.100 (Management and orchestration; Levels of autonomous network). Availabe at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3756 Further more, SA WG5 has decided to continue the study on evaluation and enhancement of autonomous network levels in Release 18. Two corresponding study items are approved and the study output will be captured in TR 28.909 and TR 28.910. SA WG5 would also be happy to share the progress of them in the future. Reference documents are: - SP-211445 (New Study on evaluation of autonomous network levels). Availabe at: https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211445.zip - SP-211446 (New Study on enhancement of autonomous network levels). Availabe at: https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211446.zip","secretary_remarks":"CC#2: 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":"2022-02-09 08:09:55","uploaded":"2022-02-09 08:11:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2","Cc":"TSG SA","lsoriginalls":"S5-221492","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220012.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220013","title":"LS from SA WG5: Reply to TM Forum Liaison AN LS22","source":"SA WG5","contact":"Volodymyr Malashnyak","contact-id":87599.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank TM Forum for the liaisons 'AN LS22: 0001 TM Forum, AN team Response, to liaison S5'. We agree that we can progress with MSDO meetings as well as starting with meetings between individual SDOs. At the individual TM-Forum \/ 3GPP meeting we can share experience from both groups and try to align intent work including concept, models etc. much better. A conference call is organized by SA WG5 for such individual meeting as follows: SA WG5 - TMF conference call Wed, Feb 23, 2022 12:00 PM - 2:00 PM (CET) Please join my meeting from your computer, tablet or smartphone. https:\/\/www.gotomeet.me\/MirkoCano\/sa5-tmf New to GoToMeeting? Get the app now and be ready when your first meeting starts: This is a proposed agenda for the meetings: - Share views on intent concept, model progress from both groups - Open discussion on benefits from Model federation and obstacles o Division of responsibilities and eliminating dependencies o Model versions handling, compatibility rules, etc - Open discussion on cooperation mechanism o Coordinate the work plan: align the time plan of relevant intent project stage 2 (IG1253 suit) and stage 3 (TMF921) in TM Forum, with work plan in 3GPP R17 (TS 28.312, including stage2 and stage3) and R18 intent study item (TR 28.912) . o Mechanisms on alignment\/collaboration between 3GPP and TM Forum: open discussion o How 3GPP can influence definition of Intent Common Model if it is administrated by TM Forum - AOB","secretary_remarks":"CC#2: 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":"2022-02-09 08:09:55","uploaded":"2022-02-09 08:11:34","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum","Cc":"TSG SA","lsoriginalls":"S5-221493","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220013.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220014","title":"LS from SA WG5: Reply LS on energy efficiency as guiding principle for new solutions","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599.0,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 would like to thank TSG SA for your LS on energy efficiency as guiding principle for new solutions. SA WG5 would also like to inform TSG SA that we will initiate our Release 18 work on energy efficiency and energy saving in 5G networks at SA WG5#142e. In relation to your LS on Energy Efficiency as guiding principle for new solutions, amongst many objectives, our Rel-18 work on EE aims to investigate on digital sobriety applied to SA WG5 OA&M solutions. Given that a) the cheapest energy is the energy which is not used and b) the energy consumed by network elements \/ network functions has some dependency on data or signaling volumes processed and\/or transported and\/or stored by the network elements \/ network functions, we aim to: - study which forms digital sobriety could take in SA WG5, e.g. by minimizing the volume of OA&M data (number and type of operation parameters, input data to MDAF (Management Data Analytics Function), etc.) to be processed and\/or transported and\/or stored, - study if any metrics can be defined so as to compare different alternative solutions with regards to digital sobriety. Reference documents are: o SP-211440 (New Study on new aspects of EE for 5G networks Phase 2). Available at: https:\/\/portal.3gpp.org\/ngppapp\/TdocList.aspx?meetingId=60223 o SP-211441 (New WID on Enhancements of EE for 5G Phase 2). Available at: https:\/\/portal.3gpp.org\/ngppapp\/TdocList.aspx?meetingId=60223. Actions: To TSG SA, TSG RAN, TSG CT, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, RAN WG5, CT WG1, CT WG3, CT WG4, CT WG6: please take the above information into account.","secretary_remarks":"CC#2: 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":"2022-02-09 08:09:55","uploaded":"2022-02-09 08:11:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"TSG RAN, TSG CT, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, RAN WG5, CT WG1, CT WG3, CT WG4, CT WG6","lsoriginalls":"S5-221501","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220014.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220015","title":"LS from SA WG5: Reply LS on the Consent of Recommendation ITU-T M.3381","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599.0,"tdoctype":"LS in","for":"Action","abstract":"The SA WG5 would like to thank ITU-T Q5\/2 for your LS on the Consent of Recommendation ITU-T M.3381 (ex. M.resm-AI), 'Requirements for energy saving management of 5G RAN system with AI'. SA WG5 would like to inform that it has completed its Release 17 work on the energy efficiency of 5G networks. The main outcome includes, amongst others, specification of the following energy saving use cases and solutions: - Capacity booster cell partially overlaid by candidate cell(s) - Capacity booster cell fully overlaid by candidate cell(s) - Switch off edge UPFs during off-peak traffic hours. Reference document is: - TS 28.310 (Management and orchestration; Energy efficiency of 5G). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3550 SA WG5 is about to start its Release 18 work on energy efficiency and energy saving in 5G networks. The main objectives include the specification of new use cases, requirements and solutions for energy saving in NG-RAN, 5GC and network slicing, including AI\/ML assisted energy saving. Reference documents are: - SP-211440 (New Study on new aspects of EE for 5G networks Phase 2). Available at: https:\/\/portal.3gpp.org\/ngppapp\/TdocList.aspx?meetingId=60223 - SP-211441 (New WID on Enhancements of EE for 5G Phase 2). Available at: https:\/\/portal.3gpp.org\/ngppapp\/TdocList.aspx?meetingId=60223 With regard to the usage of AI\/ML, SA WG5 is working on MDA (Management Data Analytics) in Rel-17, including MDA functionality and service framework, MDA capabilities with corresponding analytics inputs and analytics outputs (reports), MDAS (Management Data Analytics Service), as well as ML model training. MDA assisted energy saving is one of the MDA capabilities being worked on. MDA, as a key enabler of automation and intelligence, is considered a foundational capability for mobile networks and services management and orchestration. The MDA specific aspects are being defined in TS 28.104, while ML model training is being defined in TS 28.105. SA WG5 also started a Release 18 study on AI\/ML management, which will address other AI\/ML management capabilities than ML model training to enable and support AI\/ML in 5GS (including 5GC, NG-RAN and management system). Reference documents are: - TS 28.104 (Management and orchestration; Management Data Analytics (MDA)). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3877 - TS 28.105 (Management and orchestration; Artificial Intelligence \/ Machine Learning (AI\/ML) management). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3970 - SP-211443 (New study on AI\/ML management). Available at: https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_94E_Electronic_2021_12\/Docs\/SP-211443.zip Last but not least, it is worth highlighting that from 5G onwards, the SA WG5 has started to adopt a Service-Based Management Architecture (SBMA). The fundamental building block of SBMA is the Management Service (MnS). A MnS is a set of offered capabilities for management and orchestration of network and services. The entity producing a MnS is called MnS producer. The entity consuming a MnS is called MnS consumer. A MnS provided by a MnS producer can be consumed by any entity with appropriate authorization and authentication. The traditional terms NMS and EMS are not used in SBMA. Reference documents are: - TS 28.533 (Management and orchestration; Architecture framework). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3416 - TS 28.532 (Management and orchestration; Generic management services). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3427. Actions: To ITU-T SG2, ITU-T SG5, ITU-R WP 5D, TSG SA: please take the above information into account.","secretary_remarks":"CC#2: 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":"2022-02-09 08:09:55","uploaded":"2022-02-09 08:11:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITUT SG2","Cc":"ITUT SG5, ITUR WP 5D, TSG SA","lsoriginalls":"S5-221502","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220015.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220016","title":"LS from SA WG5: Reply LS on slicing management aspects in relation to SEAL","source":"SA WG5","contact":"Kai Zhang","contact-id":66365.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank SA WG6 for their LS on slicing management aspects in relation to SEAL. SA WG5 provides the following feedback on the SA WG6 LS: - Views of SA WG5 about the exposure of slicing management aspects to SEAL (Service Enabler Architecture Layer for Verticals - TS 23.434) as a means to address requirements from third party applications 1) The 3GPP exposure governance management function is defined as 'Management Function entity with the role of management service exposure governance' in clause 3.1 of TS 28.533. TS 28.533, provides an informative annex A.3 which gives an example of utilization of management services by EGMF. 3GPP MnS consumers may be in the Network Operator (NOP) domain or outside the NOP domain (e.g. in the Vertical domain). 2) SA WG5 is responsible for the specification of the 5G Management and Charging Services, as well as for the specification of the access control and exposure of 5G management services. 3) To fulfil the management capabilities exposure requirements from third party applications which are outside the NOP domain, SA WG5 management capability exposure governance feature (see TS 28.533) exposes management capabilities to external third party applications acting as AF defined in TS 23.501. 4) It is specified in TS 28.202 the Converged Charging System (CCS) support to Network Slice Management Charging. - Views of SA WG5 about interactions with ongoing work in SA WG5, in particular 1) Exposure of management capability in the context of non-public networks (see draft TS 28.557 WI OAM-NPN 870023) is about the consumption of management services provided by an NPN-SP (NPN Service Provider) to an NPN-SC (NPN Service consumer), where the NPN-SC maybe be viewed as an external third party. 2) FS_MNSAC is about access control of an internal or external consumer that wants to access the management services (MnS) provided by an MnS producer. 3) SA WG5 is currently initiating a Rel-18 study phase for network slice capability exposure (Revised SID S5-221740 pending for SA#95 approval). The study will discuss how SA WG5 management capability can be exposed to an external consumer and controlled by SA WG5 access control mechanism. - SA WG5 agrees with SA WG6 as the highlighted need to coordinate with each other WG to avoid overlapping specifications and ensure complementary approaches.","secretary_remarks":"CC#2: 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":"2022-02-09 08:09:55","uploaded":"2022-02-09 08:11:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2, TSG SA","lsoriginalls":"S5-221548","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220016.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220017","title":"LS from SA WG5: LS on 3GPP SA5 work on 5G network energy efficiency and energy saving","source":"SA WG5","contact":"Jean Michel Cornily","contact-id":7599.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to inform that it has completed its Release 17 work on the energy efficiency of 5G networks. Main outcomes include (non-exhaustive list): - Definition of Energy Efficiency (EE) KPIs for: o gNBs, both split and non-split, o 5G core network o 5G network slice of the following types: eMBB, URLLC, MIoT - Definition of the Energy Consumption (EC) of: o 5G network o 5G Network Function (NF). In case a 5G NF is composed of Virtualized Network Function(s) (VNF), the EC of the VNF is estimated (as there is no means to measure it yet) based on its virtual CPU usage (measurement collected from NFV MANO) - Energy saving use cases and solutions: o Capacity booster cell partially overlaid by candidate cell(s) o Capacity booster cell fully overlaid by candidate cell(s) o Switch off edge UPFs during off-peak traffic hours. Reference documents are: - TS 28.310 (Management and orchestration; Energy efficiency of 5G). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3550 - TS 28.554 (Management and orchestration; 5G end to end Key Performance Indicators (KPI)) - clause 6.7. Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3415 - 3GPP TS 28.552 (Management and orchestration; 5G performance measurements) - clause 5.1.1.19. Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3413 - TS 28.541 (Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3) - clauses 4.3.58 and 4.3.63. Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3400 SA WG5 has now initiated its Release 18 work on energy efficiency and energy saving in 5G networks. The main objectives are to: - Specify new EE KPIs for network slices, e.g.: o EE KPI for V2X, o EE KPI for URLLC based on reliability - Specify further the EC of a 5G NF when it is composed of VNF(s), by e.g.: o Include additional measurements obtained from NFV MANO, such as e.g. virtual disk usage, virtual link usage, in addition to the virtual CPU usage - Define the EC of a 5G NF when it is composed of Containerized VNFs (in Release 17, only VM-based VNFs have been considered) - Specify new use cases, requirements and solutions for energy saving in NG-RAN, 5GC and network slicing, including AI\/ML assisted energy saving - Investigate on digital sobriety applied to SA WG5 OA&M solutions. Given that a) the cheapest energy is the energy which is not used and b) the energy consumed by network elements \/ network functions has some dependency on data or signaling volumes processed and\/or transported and\/or stored by the network elements \/ network functions: o Study which forms digital sobriety could take in SA WG5, e.g. minimize the volume of OA&M data (number and type of operation parameters, input data to MDAF, etc.) to be processed and\/or transported and\/or stored, o Study if any metrics can be defined to compare different alternative solutions with regards to digital sobriety. Reference documents are: o SP-211440 (New Study on new aspects of EE for 5G networks Phase 2). Available at: https:\/\/portal.3gpp.org\/ngppapp\/TdocList.aspx?meetingId=60223 o SP-211441 (New WID on Enhancements of EE for 5G Phase 2). Available at: https:\/\/portal.3gpp.org\/ngppapp\/TdocList.aspx?meetingId=60223","secretary_remarks":"CC#2: 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":"2022-02-09 08:09:55","uploaded":"2022-02-09 08:11:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA, NGMN, ITUT SG5, ETSI TC EE, ETSI ISG NFV","Cc":"TSG SA, SA WG2, TSG RAN","lsoriginalls":"S5-221680","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220017.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220018","title":"LS from CT WG1: Reply LS on EPS support for IoT NTN in Rel-17","source":"CT WG1","contact":"Marko Niemi","contact-id":16608.0,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 would like to thank SA WG2 for their LSs on EPS support for IoT NTN in Rel-17 and would like to inform SA WG2 that it will update stage3 according to the latest updates in the SA WG2 WID. Considering changes to TS 23.401 (CR attached S2-2109197) e.g. to sc. 5.3.2.1: 'In case of satellite access for Cellular IoT, the MME may verify the UE location as described in clause 4.X.4. If the UE receives an Attach Reject message with the country in which the UE is located, the UE shall attempt to register to a PLMN that is allowed to operate in the country for the UE location as specified in TS 23.122 [10]'. CT WG1#133bis would like to highlight received LS from SA WG1 (C1-217122) stating that 'There is no impact of the 'indicated country of UE location' on the PLMN selection procedures'. Therefore CT WG1 would kindly ask SA WG2 to consider of rewording of these additions in TS 23.401.","secretary_remarks":"CC#2: 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":"2022-02-09 08:09:55","uploaded":"2022-02-09 08:11:34","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN, TSG CT, RAN WG2, SA WG2","Cc":"RAN WG3, CT WG4","lsoriginalls":"C1-220532","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220018.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220024","title":"LS from SA WG2: Reply LS on MINT functionality for Disaster Roaming","source":"SA WG2","contact":"Hyunsook Kim","contact-id":42013.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 thanks SA WG3 for reply LS, (S2-2200028 \/ S3-214342) and (S2-2200066 \/ S3-214416). SA WG2 made the following agreements in SA WG2#149E: - specify two options during the authentication and subscription information checking, Option 1: 'Disaster Roaming indication' is transferred from AMF to AUSF\/UDM Option 2: The configuration via OAM based on operator policy and the request by the government agencies when the disaster roaming occurs (No additional signalling) SA WG2 respectfully asks SA WG3 and CT WG4 to take above information into consideration and to update their specifications accordingly.","secretary_remarks":"CC#2: 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":"2022-02-28 09:51:59","uploaded":"2022-02-28 10:22:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, CT WG4","Cc":"SA WG5, CT WG1, CT WG6, RAN WG2, TSG SA, TSG CT, TSG RAN","lsoriginalls":"S2-2201514","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220024.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220025","title":"Reply LS on progress of FS_eIMS5G2","source":"SA WG2","contact":"Thomas Belling","contact-id":68266.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG2 informs CT WG4 that SA WG2 has not been able to agree proposed Rel-17 CRs to add normative requirements based on key issue 1 conclusions in TR 23.700-12 for FS_eIMS5G2 study, as suggested by CT WG4\u00b4s incoming LS S2-2200204. SA WG2 may perform related work in Rel-18 if a related TEI-18 WID can be agreed.","secretary_remarks":"CC#2: 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":"2022-02-28 09:51:59","uploaded":"2022-02-28 10:22:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, CT WG3","Cc":"TSG SA, TSG CT, CT WG1","lsoriginalls":"S2-2201548","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220025.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220027","title":"LS from SA WG6: Reply LS on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC))","source":"SA WG6","contact":"Emmanouil Pateromichelakis","contact-id":89215.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks AECC for their LS in S6-212501 and for providing the material related to the AECC vision and ongoing work. SA WG6 is the application enablement and critical communications applications group for vertical markets. The main objective of SA WG6 is to provide application layer architecture specifications for 3GPP verticals, including architecture requirements and functional architecture for supporting the integration of verticals to 3GPP systems. With respect to application enablement, the main focus is on enablers for vertical applications (e.g. automotive) and service frameworks (e.g. Common API Framework, Service Enabler Architecture Layer, Edge Application enablement). SA WG6 has completed Rel-17 work items which may be of interest to AECC. In particular: - EDGEAPP (3GPP TS 23.558) provides an edge enabling layer and application architecture for enabling Edge Applications on the Edge Data Network, including the exposure of northbound APIs towards Edge Applications, integration with the 3GPP Network, and to facilitate communication between the Application Clients running on the UE and the Edge Application Servers deployed on the Edge Data Network with capabilities such as service provisioning, rich application discovery, and service continuity - eV2XAPP (3GPP TS 23.286) - Application layer support for V2X services: enables the efficient use and deployment of V2X applications over 3GPP systems including Platooning, Advanced Remote Driving, and High Definition Maps. The focus of eV2XAPP is to provide key capabilities such as message distribution, service continuity, application resource management, and dynamic group management In addition, SA WG6 has started Rel-18 study items which may be of particular interest of AECC. In particular: - eEDGEAPP (3GPP TR 23.700-98) studies architecture and procedure enhancements to improve the Rel-17 EDGEAPP architecture for enabling edge applications, and to support emerging industry requirements. - eV2XAPP2 (3GPP TR 23.700-64) studies architecture and procedure enhancements over eV2XAPP to capture mainly capabilities to Vehicle-to-Pedestrian (V2P) communications and advanced driving use cases (e.g. ToD). - ADAES (3GPP TR 23.700-36) - study on Application data analytics Enablement services: aims to investigate the support for application data analytics for vertical scenarios and edge data analytics enablement aspects. All documents are available at: https:\/\/www.3gpp.org\/dynareport\/TSG WG--S6.htm?Itemid=682 SA WG6 is looking forward to further information exchange with AECC; and would be interested to receive updates on requirements related to Vehicle to Cloud solutions which fall within the scope of the application enablement layer.","secretary_remarks":"CC#2: 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":"2022-02-28 09:51:59","uploaded":"2022-02-28 10:22:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Automotive Edge Computing Consortium (AECC)","Cc":"TSG SA, SA WG1, SA WG2, SA WG5","lsoriginalls":"S6-220265","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220027.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220028","title":"LS from SA WG1: Reply LS about new SID on Application Enablement for Data Integrity Verification Service in IOT","source":"SA WG1","contact":"Betsy Covell","contact-id":86567.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks SA WG3 for their LS on reply to SA WG6 about new SID on Application Enablement for Data Integrity Verification Service in IOT. In response to the request to clarify the intention, main use cases, scope, and main requirements of the service for data integrity verification service introduced in TS 22.261, SA WG1 provides the following. The requirement related to data integrity verification service in TS 22.261 states: 'Subject to regulatory requirements and based on operator policy, the 5G system shall provide a mechanism to support data integrity verification service to assure the integrity of the data exchanged between the 5G network and a third-party service provider. NOTE: This requirement could apply to mechanisms supported over the interface between 5G core network and an external application, with no impact on RAN and UE.' This requirement applies to data integrity verification service applied to the data exchanged between the 5G network and a third-party service provider. Additionally, in the WID, SP-210213, and CR, 22.261 CR0496R1, which introduced this requirement, neither the boxes for the UE or RAN were checked.","secretary_remarks":"CC#2: 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":"2022-02-28 09:51:59","uploaded":"2022-02-28 11:16:56","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG6","Cc":"TSG SA","lsoriginalls":"S1-220185","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220028.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220029","title":"LS from SA WG1: Reply LS on User Controlled PLMN Selector with Access Technology in Control plane solution for steering of roaming in 5GS","source":"SA WG1","contact":"Francesco Pica","contact-id":57089.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for their LS (C1-217358) on User Controlled PLMN Selector with Access Technology in Control plane solution for steering of roaming in 5GS. With regard to the specific use case under discussion, and corresponding question: CT WG1 is discussing the use case when the selected PLMN is a VPLMN which is in the 'User Controlled PLMN Selector with Access Technology' list and the UE in automatic network selection mode receives SOR information, and the security check of the received SOR information fails in the UE. Question: CT WG1 kindly asks SA WG1 whether, in the use case above, the VPLMN still has higher priority than the steered-to-PLMN or the VPLMN should be considered as lowest priority? SA WG1 could not reach consensus.","secretary_remarks":"CC#2: 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":"2022-02-28 09:51:59","uploaded":"2022-02-28 11:16:56","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3, TSG SA","lsoriginalls":"S1-220187","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220029.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220262","title":"LS from SA WG3: Reply LS on MINT functionality for Disaster Roaming","source":"SA WG3","contact":"Dongjoo Kim","contact-id":84882.0,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks SA WG2 for the reply LS(S3-220499\/S2-2201514) on MINT functionality for Disaster Roaming. SA WG3 would like to inform SA WG2 that based on SA WG2 decision, SA WG3 agreed the attached CR for TS 33.501, which updates the initiation procedures of the primary authentication and corresponding services provided by AUSF and UDM.","secretary_remarks":"CC#2: 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":"2022-03-07 08:10:14","uploaded":"2022-03-07 08:45:58","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG5, CT WG1, CT WG4, CT WG6, RAN WG2, TSG SA, TSG CT, TSG RAN","lsoriginalls":"S3-220518","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220262.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220264","title":"LS from ITU-R WP5D: Information on the completion of revision of Recommendation ITU-R M.2150 on radio interface technologies for the terrestrial component of IMT-2020","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941.0,"tdoctype":"LS in","for":"Information","abstract":"Working Party (WP) 5D thanks the RIT\/SRIT Proponents, GCS Proponents and Transposing Organizations as well as the registered Independent Evaluation Groups for their active participation in the IMT-2020 development process. The two candidate technologies, on a one-time exceptional basis, had continued in the IMT-2020 process, rewinding to the start of Step 4 in order to consider additional material as announced in the Circular Letter 5\/LCCE\/89. The process to evaluate these candidates has completed, and focused revision of Recommendation ITU-R M.2150 ('Detailed specifications of the terrestrial radio interfaces of International Mobile Telecommunications 2020(IMT-2020)') has been successfully concluded. The attached Addendum 1 to the Circular Letter 5\/LCCE\/89 provides information on the completion and approval of the focused revision of Recommendation ITU-R M.2150. Working Party 5D takes this opportunity to express appreciation to the work carried out by the external organizations and would welcome further opportunity in the future to engage with the external organizations in the development of IMT.","secretary_remarks":"CC#2: 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":"2022-03-07 08:10:15","uploaded":"2022-03-09 08:38:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"R19-WP5D-220207","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220264.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220331","title":"LS from EUWENA: LS on presentation of EUWENA and involvement in 3GPP on Non Public Network","source":"EUWENA","contact":"Thierry Berisot","contact-id":77639.0,"tdoctype":"LS in","for":"Action","abstract":"EUWENA (European Users Wireless Enterprise Network Association, https:\/\/www.euwena.eu) has been established in 2021, as a vehicle to entice and promote private wireless networks (Non Public Network for 3GPP) or services for industries and verticals. EUWENA clearly recognizes the need for mobile connectivity in a wide range of public and private enterprises and organisations related to the particular area where the enterprise or organization operates. This need can be geographically determined: from a confined, local area, all the way up to a nationwide and even global footprint; indoor and\/or outdoor; application-related such as voice, data or video, from modest IoT messages up to 8k-video-streams, and diverse levels of criticality and latency from basic non-real-time data transmission to the steering of a crane. In multiple scenarios, a best effort solution is simply not good enough, as critical services require high availability with guaranteed service levels. EUWENA mission statement [1] is: 'Working together with all interested parties, EUWENA acts as a catalyst for the wider adoption of feature-rich private mobile networks across Europe. It advocates sufficient, accessible, affordable, harmonised spectrum and promotes an open, multi-vendor approach to advanced services and applications running in these networks. EUWENA's ultimate goal through its actions is to make the adoption of such solutions as easy as possible for as many organisations as possible, thereby creating enhanced and sustained value for enterprises and wider society.' In this context, EUWENA intends to represent verticals and sees its roles as following: - To speed up the availability and harmonisation of sufficient frequency spectrum for private wireless networks in Europe, stimulating the creation of an open ecosystem. - To exchange knowledge and experience on the technology, demand and supply market, to contribute to the digital transformation process, accelerating the adoption of mobile broadband technology by enterprises in Europe and supporting the specific needs of vertical sectors. - To inform, advise and represent European enterprise users in established European spectrum, regulatory and related organisations and in international interest groups for private networks. - To help enterprise customers define and deploy the best spectrum and private mobile network strategies Within EUWENA, there are currently 4 technical workgroups which have specific focus areas: - Standards Working Group: It is the main body within EUWENA feeding industry and enterprise private wireless network requirements into regional and global standards organisations, liaising closely with 3GPP, ETSI and other relevant and related bodies, as well as informing our members of latest developments, standards releases and main future trends which will impact their businesses - Working Group on Alliances and Associations: Some countries already have national business-critical user wireless solution associations. In addition, there are already a few international bodies and associations, either horizontally oriented or vertically oriented towards a specific sector. - Spectrum harmonisation Working Group: Wireless networks and solutions start with the availability of appropriate frequency spectrum. EUWENA advocates sufficient, accessible, affordable, harmonized spectrum for private broadband networks in Europe. EUWENA will develop the approach, strategy and undertake necessary actions to achieve this goal. - Supply Ecosystem Working Group: Supply and availability of a diverse eco-system of technology will enable the full benefits of private 4G\/5G spectrum for the users A 5th Working group related to 'use cases' is under definition. In relation to the Standards Working Group and 3GPP, EUWENA members, who are as well 3GPP members, are committed to actively contribute in the 3GPP activities related to Private Cellular Networks or Non Public Networks in particular in the following 3GPP work","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":"2022-03-11 13:02:23","uploaded":"2022-03-11 13:03:03","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, TSG RAN, TSG CT","Cc":"SA WG1, SA WG2, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, CT WG1, CT WG6","lsoriginalls":"LS EUWENA.doc","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220331.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]