[{"name":"S2-2200038","title":"LS from GSMA OPAG: Reply LS from GSMA Operator Platform API Group to 3GPP SA, SA2, SA5, SA6 and ETSI ISG MEC on edge computing definition and integration","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"The OPAG would like to invite feedback to that mapping at the joint workshop that has been planned for 21st January 2022, see [2], targeting a conclusion of that mapping allowing work to close the gaps identified to start shortly after. Action: Based on the mapping presented during the webinar, the OPAG wishes to continue the multi-party discussion with ETSI ISG and 3GPP. For this a follow-up workshop has been agreed on 21 January 2022, 13:00-15:00 GMT [2], for 3GPP and ETSI to provide feedback based on OPAG mapping and review\/discuss\/align. GSMA wishes to invite all delegates of the involved groups to join this workshop.","secretary_remarks":"Response from TSG SA in S2-2200078. Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13050,"status":"noted","reservation_date":"2022-01-10 14:20:56","uploaded":"2022-01-10 16:05:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG5, SA WG6, ETSI ISG MEC","Cc":"ETSI ISG NFV","lsoriginalls":"OPAG_04_Doc_02","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200038.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200039","title":"LS from GSMA OPG: Reply LS from GSMA Operator Platform Group to 3GPP SA, SA2, SA5, SA6 and ETSI ISG MEC on edge computing definition and integration","source":"GSMA OPG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"As a first phase, GSMA OPAG is mapping Operator Platform requirements against specifications available from 3GPP and ETSI. The intent is to reuse existing standards, where appropriate, and to address gaps through API contributions based on existing OP trials and POCs. For these, the OPAG plans to work with the Linux Foundation on the development on the OP APIs. Action: Based on the above mapping the GSMA wishes to start a multi-party discussion with ETSI ISG and 3GPP in order to:- - align on mapping of requirements, APIs and SDOs to ensure standard development of the defined interfaces and avoid duplication of works or divergences - invite 3GPP and ETSI members to join an informational webinar on 2 December, 13:00-15:00 GMT [2]. This will be for OPAG to share an overview of required OP APIs and their mapping to SDO solutions. - A follow-up workshop on 21 January 2022, 13:00-15:00 GMT [3], for 3GPP and ETSI to provide feedback based on OPAG mapping and review\/discuss\/align - Build the governance and collaboration model between GSMA, 3GPP, ETSI ISG to guarantee E2E delivery of the Operator Platform standardisation.","secretary_remarks":"Response from TSG SA in S2-2200078. Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13060,"status":"noted","reservation_date":"2022-01-10 14:20:56","uploaded":"2022-01-10 16:05:25","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG5, SA WG6, ETSI ISG MEC","Cc":"ETSI ISG NFV","lsoriginalls":"OPG_72_Doc_04","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200039.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200071","title":"LS from SA WG4: LS on follow-up on EAS definition","source":"SA WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG4 would like to thank SA WG6 for their detailed responses to the questions about the EAS definition. Based on the received answers and upon further discussions, SA WG4 would like to ask the following follow-up questions: 1. Is a mechanism defined to ensure that sets of related EAS instance(s) offering a service to the Application Client can be executed, discovered and relocated together in cases where this is necessary for the proper operation of the service? Independent discovery and relocation may not address the requirements of certain media services. 2. For managed application context transfer of an EAS instance, is it possible to pass the application context by reference, i.e. for the source EAS instance to store its application context in a shared location, and to share the information needed to access this application context (such as the address, acceptable protocol(s), required security) with the target EAS instance via the source EES and target EES? SA WG4 would like to kindly request SA WG6 to provide their insight on the above issues, which SA WG4 considers useful for application context relocation.","secretary_remarks":"Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13080,"status":"noted","reservation_date":"2022-01-10 14:20:57","uploaded":"2022-01-11 07:09:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2","lsoriginalls":"S4-211658","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200071.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200073","title":"LS from SA WG5: Reply LS on Prioritized Vehicle to Cloud Technical Solutions (Automotive Edge Computing Consortium (AECC))","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank Automotive Edge Computing Consortium (AECC) for the LS about Prioritized Vehicle to Cloud Technical Solutions. SA WG5 is currently responsible for: \u00d8 Management and Orchestration, which covers aspects such as operation, assurance, fulfillment and automation, including management interaction with entities external to the network operator (e.g. verticals). \u00d8 Charging, which covers aspects such as Quota Management and Charging Data Records (CDRs) generation, related to end-user and service-provider. The following Rel-17 work items (normative) \/ study items (non-normative) may be of interest to you: WI\/SI Related Specifications Management of non-public networks TS 28.557 Enhancement on Management Aspects of 5G Service-Level Agreement TS 28.531\/28.541 Management of the enhanced tenant concept TS28.531 \/ 28.532 \/ 28.533 \/ 28.541 network slice provisioning enhancement TS 28.531 \/ 28.541 Enhancements of 5G performance measurements and KPIs TS 28.552 \/ 28.554 Enhancements of Management Data Analytics Service TS 28.104 Edge Computing Management TS 28.538 Study on management aspects of network slice management capability exposure TR 28.824 All documents are available at: https:\/\/www.3gpp.org\/DynaReport\/TSG WG--S5.htm SA WG5 is looking forward to further information exchange with AECC if needed.","secretary_remarks":"Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13090,"status":"noted","reservation_date":"2022-01-10 14:20:57","uploaded":"2022-01-11 07:09:44","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Automotive Edge Computing Consortium (AECC)","Cc":"SA WG1, SA WG2, SA WG6","lsoriginalls":"S5-216412","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200073.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200078","title":"LS from TSG SA: Reply LS to GSMA Operator Platform Group on edge computing definition and integration","source":"TSG SA","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks GSMA OPG for the continued dialogue with 3GPP in relation to the Operator Platform Group activities. TSG SA is happy to note the launch of the new GSMA OPAG (Operator Platform API Group) sub-group within GSMA OPG. In fact, SA would like to thank GSMA for organizing the informational webinar on Dec 02nd outlining the overview and the current status of the GSMA OPG and OPAG initiatives, where a number of 3GPP delegates are known to have participated. TSG SA has reviewed the OPAG APIs and the SDO mapping highlighted during the informational webinar, and observed that the ongoing 3GPP work related to Edge Computing in various working groups is not fully reflected in the current GSMA assessment. In the attached document, 3GPP inputs are provided against each of the OPAG API blocks\/categories with the appropriate references to 3GPP specifications, and as well as additional feedback\/remarks for your consideration (please see the last two columns). TSG SA intends to continue the close collaboration with GSMA OPG\/OPAG on this important initiative and looks forward to the follow-up workshop to be held on January 21st, to further discuss the details of the API mapping and address any clarifications. It is expected that related SA WGs will continue to work on GSMA OPG requirements (in both Rel-17 and Rel-18) based on the planned activities (i.e. work items and workplan) within the respective working groups.","secretary_remarks":"TSG SA response to S2-2200039 and S2-2200038. Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13070,"status":"noted","reservation_date":"2022-01-10 14:20:57","uploaded":"2022-01-24 06:58:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG, GSMA OPAG","Cc":"SA WG2, SA WG3, SA WG5, SA WG6, CT WG1, CT WG3, ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"SP-220003","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200078.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200114","title":"Aligning 23.501 and 23.548 wording about the DN accessed via a L-UPF","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refer to forwarding traffic to the Local part of the DN (as defined in TS 23.548 [130]) and not to local Data Network","secretary_remarks":"r04 agreed. Revised to S2-2201708.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13100,"status":"revised","reservation_date":"2022-01-24 14:57:20","uploaded":"2022-01-28 18:13:50","revisionof":"","revisedto":"S2-2201708","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3464.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200114.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200159","title":"Corrections on enabling EAS IP Replacement procedure by AF","source":"China Unicom","contact":"TianQi Xing","contact-id":89168,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing 'If AF is not notified by 5GC that the 5GC supports EAS IP replacement mechanism, the AF does not include the target EAS identifier and does not initiate the EAS relocation.' in clause 6.3.3.1.1 Step4. Adding the description that the SMF should reject the AF request if 5GC does not support EAS IP replacement capability. Correct that AF may additionally include Source and Target EAS IP address(es) and Port number(s) in the Nnef_TrafficInfluence_Create\/Update or Nnef_TrafficInfluence_AppRelocationInfo\/Nsmf_EventExposure_AppRelocationInfo request.","secretary_remarks":"r02 agreed. Revised to S2-2201709.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13120,"status":"revised","reservation_date":"2022-01-25 07:36:45","uploaded":"2022-01-26 08:28:30","revisionof":"","revisedto":"S2-2201709","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":43.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200159.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200160","title":"Corrections on notification of user plane management event procedure","source":"China Unicom","contact":"TianQi Xing","contact-id":89168,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description 'SMF may indicate capability of supporting EAS IP replacement in 5GC' in Notification of User Plane Management Events procedure step2a, step4c of Figure 4.3.6.3-1.","secretary_remarks":"Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13140,"status":"agreed","reservation_date":"2022-01-25 07:46:33","uploaded":"2022-01-26 08:28:30","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3322.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200160.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200207","title":"Clarify FQDN in Traffic Influence","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the usage of FQDN ranges. Describe the deferred UP path change handling.","secretary_remarks":"r04 agreed. Revised to S2-2201711.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13150,"status":"revised","reservation_date":"2022-01-25 16:32:56","uploaded":"2022-01-28 20:47:04","revisionof":"","revisedto":"S2-2201711","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3472.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200207.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200208","title":"Local NEF discovery via CAPIF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description for L-NEF discovery using CAPIF.","secretary_remarks":"Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13170,"status":"noted","reservation_date":"2022-01-25 16:32:58","uploaded":"2022-01-28 20:47:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":44.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200208.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200210","title":"Correction related to EDI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding a note to Table 6.2.3.4-1 Adding External Application ID Adding what is required to be sent by AF Removing event id","secretary_remarks":"Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13180,"status":"noted","reservation_date":"2022-01-25 16:33:00","uploaded":"2022-01-28 20:47:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":45.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200210.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200211","title":"Correction related to EDI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding what is required to be sent by AF Editorial in 6.2.3.2.2 Removing event id Removing text related to EDI via PCF Fixing Nnef_UEId_Get operation","secretary_remarks":"CC#4: r00 + changes agreed. Revised to S2-2201847.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13190,"status":"revised","reservation_date":"2022-01-25 16:33:01","uploaded":"2022-01-28 20:47:04","revisionof":"","revisedto":"S2-2201847","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3327.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200211.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200283","title":"Correction related EHE in EC architecture","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding that EASs are deployed in a DN within a EHE","secretary_remarks":"r01 agreed. Revised to S2-2201712.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13210,"status":"revised","reservation_date":"2022-01-26 15:38:25","uploaded":"2022-01-28 20:47:05","revisionof":"","revisedto":"S2-2201712","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":46.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200283.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200433","title":"Feature control for eEDGE_5GC functionality","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"Source: Ericsson Title: Feature control for eEDGE_5GC functionality Document for: Discussion and decision Agenda Item: 8.3 Work Item \/ Release: eEDGE_5GC \/Rel-17 Abstract of the contribution: Enhanced Edge Computing specifies a variety of functionality that has different purpose and can target different scenarios. Specifications should allow individual implementation and deployment decisions for each of them.","secretary_remarks":"Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13230,"status":"noted","reservation_date":"2022-01-27 15:58:26","uploaded":"2022-01-28 20:48:14","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200433.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200524","title":"Correction on notification on the outcome of UE Policies delivery due to service specific parameter provisioning","source":"Orange","contact":"Antoine Mouquet","contact-id":38438,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 'AF' replaced by 'NEF' in this sentence.","secretary_remarks":"Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13240,"status":"agreed","reservation_date":"2022-01-27 23:08:10","uploaded":"2022-01-28 16:14:40","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3358.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200524.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200609","title":"UE indicates the EDC capability in PCO","source":"vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UE indicates the EDC capablitity in PCO to 5GC","secretary_remarks":"Revision of (Noted) S2-2108548 from S2#148E. Merged into S2-2201720","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13250,"status":"merged","reservation_date":"2022-01-28 07:11:35","uploaded":"2022-01-28 14:12:14","revisionof":"S2-2108548","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3254.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200609.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200610","title":"Add UE capability to SMF decision for ECS address delivery","source":"vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a consideration into SMF about UE capability.","secretary_remarks":"r03 agreed. Revised to S2-2201713.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13260,"status":"revised","reservation_date":"2022-01-28 07:11:37","uploaded":"2022-01-28 14:12:14","revisionof":"","revisedto":"S2-2201713","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3366.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200610.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200611","title":"Add UPF capability that supports QoS monitoring event exposure in registration procedure to NRF","source":"vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add UPF capability of direct event notification into NRF when registers to NRF.","secretary_remarks":"r04 agreed. Revised to S2-2201714.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13280,"status":"revised","reservation_date":"2022-01-28 07:11:38","uploaded":"2022-01-28 14:12:14","revisionof":"","revisedto":"S2-2201714","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3367.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200611.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200612","title":"AF guides URSP policy determination via Npcf","source":"vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the actions about AF can request to influence UE policy.","secretary_remarks":"r01 agreed. Revised to S2-2201715.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13300,"status":"revised","reservation_date":"2022-01-28 07:11:40","uploaded":"2022-01-28 14:12:14","revisionof":"","revisedto":"S2-2201715","release":"Rel-17","crspec":"23.503","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":695.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200612.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200734","title":"Update of EAS discovery procedure and BaselineDNSPattern management in EASDF","source":"Tencent, Tencent Cloud","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the sentence about the SMF requesting EASDF information from NEF in clause 6.2.3.2.2. In clause 6.2.3.2.2, add the description that the SMF could also enable the EASDF to restart the reports of the DNS messages after the change of the L-PSA. In clause 6.2.3.4.4, change the DNAI to S-NSSAI. Other editorial changes in clause 6.2.3.4.4.","secretary_remarks":"r03 agreed. Revised to S2-2201716.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13320,"status":"revised","reservation_date":"2022-01-28 09:28:30","uploaded":"2022-01-28 09:54:41","revisionof":"","revisedto":"S2-2201716","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":47.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200734.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2200914","title":"Add missing EASDF descriptions","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Add EASDF in clause 4.2.2. 2. Add descriptions about the interface between SMF and EASDF.","secretary_remarks":"r02 agreed. Revised to S2-2201717.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13340,"status":"revised","reservation_date":"2022-01-28 11:57:35","uploaded":"2022-01-28 14:26:21","revisionof":"","revisedto":"S2-2201717","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3548.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2200914.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201087","title":"Editorial update for EDC functionality","source":"Lenovo, Motorola Mobility","contact":"Tingfang Tang","contact-id":81429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 'EDC' with 'EDC functionality' where it is not aligned in the clauses of 5.2.1, 6.2.3.2.2 and 6.2.3.2.3.","secretary_remarks":"Merged into S2-2201719","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13360,"status":"merged","reservation_date":"2022-01-28 14:53:17","uploaded":"2022-01-28 15:23:27","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":49.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201087.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201188","title":"Correction to the UE Policies delivery notification","source":"Nokia, Nokia Shanghai Bell","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correction to align with 4.15.6.7 of TS 23.502 - it is clarified that the proposed reporting is for cases where the AF request targets a single UE.","secretary_remarks":"Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13370,"status":"agreed","reservation_date":"2022-01-28 18:53:54","uploaded":"2022-01-28 18:59:24","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":706.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201188.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201244","title":"Corrections of EDC functionality description","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Swapped order of the statement of sentence in clause 5.2.1 to remove ambiguity. Clarified that the UE sends its EDC capability support indication and that the SMF can send the indication of 'EDC allowed' or 'EDC required' also at PDU Session Modification. Applied other editorial corrections.","secretary_remarks":"r03 agreed. Revised to S2-2201719, merging S2-2201087","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13380,"status":"revised","reservation_date":"2022-01-28 22:53:29","uploaded":"2022-01-28 23:46:26","revisionof":"","revisedto":"S2-2201719","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":51.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201244.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201245","title":"Corrections of EDC functionality description","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Described that the UE sends its EDC capability support indication and that the SMF can send the indication of 'EDC allowed' or 'EDC required' at PDU Session Establishment as well as PDU Session Modification.","secretary_remarks":"r03 agreed. Revised to S2-2201720, merging S2-2200609","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13400,"status":"revised","reservation_date":"2022-01-28 22:53:30","uploaded":"2022-01-28 23:46:26","revisionof":"","revisedto":"S2-2201720","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3419.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201245.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201266","title":"LS from GSMA OPAG: Further Operator Platform Group questions following SDO Workshop","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"Introduction: GSMA OPG Operator Platform API Group (OPAG) would like to thank TSG SA, SA WG2, SA WG5, and SA WG6 delegates, as well as ETSI ISG MEC members, for supporting and attending the workshop on the mapping of SDO specifications to APIs to be exposed or used by the Operator Platform to realise its required interfaces. For delegates that were unable to attend, OPAG would like to inform that a recording of the webinar as well as the slides used are now available at [2] Following the input provided prior to and during the workshop a number of questions came up in the OPAG related to the 3GPP specifications that were referred to. OPAG would like to seek clarification on those to confirm its understanding and ensure that it moves forward on the correct basis. Discussion: Following questions were raised on aspects related to 3GPP's feedback that were unclear to OPAG members: 1. Which are the security mechanisms\/procedures proposed for UNI authentication? 2. Are there any additional details regarding the availability of specifications related to EWBI TR 23.700-98? 3. Has the support for service continuity management been defined in the SCEF\/NEF specification? From the 3gpp references provided, it seems to be supported only in TS 23.558|29.588. 4. Do 3GPP specifications cover scenarios including session continuity support for handover from 5G networks to 4G and other non-3GPP access technologies? From 3GPP Release 15 onwards, the service and session continuity is described for 5G to 5G handover scenarios with the provision of SSC modes 1, 2 and 3 and an OP is expected to interact with the mobile network over its SBI-NR interface using NEF and SCEF APIs to support end-to-end application session continuity. We would like to know if similar support is envisioned for session continuity for the previously mentioned scenarios, i.e. UE session handovers between 4G or non-3GPP access and 5G. 5. The Northbound APIs (NEF T8 interfaces) require information like UE IP address, MAC address etc. which is typically managed by 5G core networks. Is there any guidance available on how an external application function (AF) can have access to such information when placed outside of the 5G core network? As the information like UE IP address is internal to mobile network, it may be an issue for external AFs outside the trust zone of mobile networks to get such information and refer to it when using NEF APIs. 6. As the 3GPP defines interaction between NEF and AF via Northbound APIs, does it impose any kind of timing constraints (soft or hard duration) for AF when AF needs to acknowledge back to 5G Core? As some of the 3GPP network procedures also expect assistance information from external AF e.g. 'the indication of 'AF acknowledgment to be expected' (3GPP TS 23.502 V16.9.0 , 'Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions') included in AF subscription to SMF events, the SMF waits for a notification response from the AF'. It is important to understand if such acknowledgements from external AF are to be strictly bound by timing constraints so that mobile core network procedures may also work correctly. Actions: To provide clarity on the questions raised in section 2.","secretary_remarks":"Response to TSG SA drafted in S2-2201682. Final LS in S2-2201721","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13420,"status":"replied to","reservation_date":"2022-02-08 09:41:28","uploaded":"2022-02-08 09:44:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG5, SA WG6","Cc":"ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"OPAG_09_Doc_04","lsreply":"S2-2201721","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201266.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201682","title":"[DRAFT] LS on Further GSMA OPG questions following SDO Workshop","source":"SA WG2","contact":"Hui Ni","contact-id":79738,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: SA WG3, SA WG5, SA WG6","secretary_remarks":"Created at CC#2. LS related to S2-2201266 for TSG SA collation.. r05 agreed. Revised to S2-2201721.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13430,"status":"revised","reservation_date":"2022-02-23 07:39:13","uploaded":"2022-03-01 08:41:22","revisionof":"","revisedto":"S2-2201721","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG3, SA WG5, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201682.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201708","title":"Aligning 23.501 and 23.548 wording about the DN accessed via a L-UPF","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refer to forwarding traffic to the Local part of the DN (as defined in TS 23.548 [130]) and not to local Data Network","secretary_remarks":"Revision of S2-2200114r04. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13110,"status":"agreed","reservation_date":"2022-03-01 08:30:19","uploaded":"2022-03-01 08:41:19","revisionof":"S2-2200114","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3464.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201708.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201709","title":"Corrections on enabling EAS IP Replacement procedure by AF","source":"China Unicom","contact":"TianQi Xing","contact-id":89168,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the description that the SMF should reject the AF request if 5GC does not support EAS IP replacement capability. Correct that AF may additionally include Source and Target EAS IP address(es) and Port number(s) in the Nnef_TrafficInfluence_Create\/Update or Nnef_TrafficInfluence_AppRelocationInfo\/Nsmf_EventExposure_AppRelocationInfo request.","secretary_remarks":"Revision of S2-2200159r02. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13130,"status":"agreed","reservation_date":"2022-03-01 08:30:21","uploaded":"2022-03-01 08:41:19","revisionof":"S2-2200159","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":43.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201709.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201711","title":"Clarify FQDN in Traffic Influence","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Describe the usage of FQDN ranges. Describe the deferred UP path change handling.","secretary_remarks":"Revision of S2-2200207r04. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13160,"status":"agreed","reservation_date":"2022-03-01 08:30:23","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2200207","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3472.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201711.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201712","title":"Correction related EHE in EC architecture","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding that EASs are deployed in a DN within a EHE","secretary_remarks":"Revision of S2-2200283r01. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13220,"status":"agreed","reservation_date":"2022-03-01 08:30:25","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2200283","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":46.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201712.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201713","title":"Add UE capability to SMF decision for ECS address delivery","source":"Vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a consideration into SMF about UE capability. Removed normative wording in NOTE 4 of 4.15.6.2","secretary_remarks":"Revision of S2-2200610r03. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13270,"status":"agreed","reservation_date":"2022-03-01 08:30:27","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2200610","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3366.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201713.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201714","title":"Add UPF event exposure that supports direct QoS monitoring","source":"Vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add UPF event exposure that supports direct QoS monitoring.","secretary_remarks":"Revision of S2-2200611r04. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13290,"status":"agreed","reservation_date":"2022-03-01 08:30:28","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2200611","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3367.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201714.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201715","title":"AF guides URSP policy determination via Npcf","source":"Vivo","contact":"Huazhang Lyu","contact-id":88594,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the actions about AF can request to influence UE policy.","secretary_remarks":"Revision of S2-2200612r01. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13310,"status":"agreed","reservation_date":"2022-03-01 08:30:30","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2200612","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":695.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201715.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201716","title":"Update of EAS discovery procedure and BaselineDNSPattern management in EASDF","source":"Tencent, Tencent Cloud","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the sentence about the SMF requesting EASDF information from NEF in clause 6.2.3.2.2. In clause 6.2.3.2.2, add the description that the SMF could also enable the EASDF to restart the reports of the DNS messages after the change of the L-PSA. In clause 6.2.3.4.4, change the DNAI to S-NSSAI. Other editorial changes in clause 6.2.3.4.4.","secretary_remarks":"Revision of S2-2200734r03. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13330,"status":"agreed","reservation_date":"2022-03-01 08:30:32","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2200734","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":47.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201716.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201717","title":"Add missing EASDF descriptions","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Add EASDF in clause 4.2.2 and 4.2.3. 2. Add descriptions about the interface between SMF and EASDF.","secretary_remarks":"Revision of S2-2200914r02. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13350,"status":"agreed","reservation_date":"2022-03-01 08:30:34","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2200914","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3548.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201717.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201719","title":"Corrections of EDC functionality description","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Swapped order of the statement of sentence in clause 5.2.1 to remove ambiguity. Clarified that the UE sends its EDC capability support indication and that the SMF can send the indication of 'EDC allowed' or 'EDC required' also at PDU Session Modification. Applied other editorial corrections.","secretary_remarks":"Revision of S2-2201244r03, merging S2-2201087. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13390,"status":"agreed","reservation_date":"2022-03-01 08:30:37","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2201244","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.1.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":51.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201719.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201720","title":"Corrections of EDC functionality description","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Described that the UE sends its EDC capability support indication and that the SMF can send the indication of 'EDC allowed' or 'EDC required' at PDU Session Establishment as well as PDU Session Modification.","secretary_remarks":"Revision of S2-2201245r03, merging S2-2200609. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13410,"status":"agreed","reservation_date":"2022-03-01 08:30:39","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2201245","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3419.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201720.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201721","title":"Reply LS on Further GSMA OPAG questions following SDO Workshop","source":"SA WG2","contact":"Hui Ni","contact-id":79738,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: SA WG3, SA WG5, SA WG6","secretary_remarks":"Revision of S2-2201682r05. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13440,"status":"approved","reservation_date":"2022-03-01 08:30:41","uploaded":"2022-03-01 08:41:15","revisionof":"S2-2201682","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2201266","lsto":"TSG SA","Cc":"SA WG3, SA WG5, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201721.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201847","title":"Correction related to EDI","source":"Ericsson, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing text related to EDI via PCF Fixing Nnef_UEId_Get operation","secretary_remarks":"Revision of S2-2200211r00 + changes. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":13200,"status":"agreed","reservation_date":"2022-03-01 08:32:10","uploaded":"2022-03-01 08:41:16","revisionof":"S2-2200211","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3327.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220055","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_149E_Electronic_2022-02\/Docs\/S2-2201847.zip","group":"S2","meeting":"S2-149-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]