[{"name":"S2-2201930","title":"LS from CT WG1: LS on ECS provider identification in ECS address provisioning","source":"CT WG1","contact":"Lazaros Gkatzikis","contact-id":78831,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 while working on stage-3 protocol implementation of the ECS Address Configuration Information provisioning to the UE (over PCO with Session Management procedures) has identified the following conflict on stage-2 specifications: 1. TS 23.548 Subclau","secretary_remarks":"Revision of Postponed S2-2200196 from S2#149E. Postponed","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11510,"status":"postponed","reservation_date":"2022-03-25 17:03:58","uploaded":"2022-03-28 08:00:13","revisionof":"S2-2200196","revisedto":"S2-2203626","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2, CT WG3","lsoriginalls":"C1-220854","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201930.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201966","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,"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":"Noted","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11520,"status":"noted","reservation_date":"2022-03-25 17:03:59","uploaded":"2022-03-29 16:30:37","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\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201966.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201967","title":"Reply LS on follow-up on EAS definition","source":"SA WG6","contact":"Nishant Gupta","contact-id":62473,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks SA WG4 for their LS in S6-220012 (S4-211658). SA WG6 discussed the follow-up questions and would like to provide the following feedback: SA WG4: 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. SA WG6 response: EDGEAPP work does not ensure that sets of related EAS instance(s) offering a service to the Application Client can be executed, discovered, and relocated together. SA WG6 has decided to study this requirement in Rel-18 FS_eEDGEAPP. SA WG4: 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 WG6 response: EELManagedACR procedure (as defined in clause 8.8.3.6 of TS 23.558) allows sharing of application context by reference. Storage location for the application context is decided between the EASs and their registrar EESs. When required the S-EES obtains the application context from the pre-decided storage location and transfers it to the T-EES, which then notifies the T-EAS about its availability at the storage location decided between T-EES and the T-EAS. SA WG6 kindly requests SA WG4 to take the above feedback into account. Also, SA WG6 requests SA WG4 to provide any feedback or additional requirements to study as part of the Rel-18 study.","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11530,"status":"noted","reservation_date":"2022-03-25 17:03:59","uploaded":"2022-03-29 16:30:37","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2","lsoriginalls":"S6-220351","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201967.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2201969","title":"Reply LS on further Operator Platform Group questions following SDO Workshop","source":"SA WG6","contact":"Basavaraj (Basu) Pattan","contact-id":61285,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks GSMA OPAG for the workshop held on January 21st, to discuss the details of the Operator Platform API mapping and the feedback from 3GPP. SA WG6 has reviewed the follow-up questions (in incoming LS S6-220120) from GSMA OPAG and prepared the below responses for inclusion into a consolidated response from SA#95e to GSMA OPAG. 1. Which are the security mechanisms\/procedures proposed for UNI authentication? [SA WG6 Response] 3GPP TS 23.558 references 3GPP TS 33.558 for UNI authentication and authorization procedures. SA WG6 recommends SA WG3 to provide additional details related to 3GPP TS 33.558. 2. Are there any additional details regarding the availability of specifications related to EWBI TR 23.700-98? [SA WG6 Response] Based on Rel-18 eEDGEAPP study, a number of key issues and solutions related to EWBI covering Roaming and Federation, Service Continuity and Synchronization are included in the latest 3GPP TR 23.700-98 v0.5.0. The study is expected to complete in June 2022, and subsequent normative work is expected to be completed within Rel-18 timeframe. 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. [SA WG6 Response] In addition to the service continuity management at the network layer defined in SCEF\/NEF, 3GPP TS 23.558 specifies application layer service continuity at Edge Enabler Layer (EEL), which supports 5 different scenarios (see clause 8.8 of 3GPP TS 23.558). APIs related to Application layer service continuity at EEL are available directly to Edge Application Server (EAS) via EDGE-3. These APIs internally leverage SCEF\/NEF APIs as described in 3GPP TS 23.501 and 3GPP TS 23.502 e.g. for capabilities exposed by the 3GPP core network such as AF traffic influence, the location information, QoS monitoring. SA WG6 recommends additional response from SA WG2 in related SCEF\/NEF. 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. [SA WG6 Response] SA WG6 recommends SA WG2 respond to this question. 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. [SA WG6 Response] An AF can get UE IP address from the received IP packets. The AF can then use the UE IP address to UE ID translation service (provided by 5GC as specified in clause 4.15.10 of 3GPP TS 23.502 or as provided by the EEL as specified in clause 8.6.5 of 3GPP TS 23.558) to translate the UE IP address to UE ID and use it for API invocation. However, if a NAT is deployed between the AF and the UE, the AF would see the public IP address of the UE, that cannot be translated to the UE ID. To allow translation while NAT is deployed, SA WG6 is studying Key Issue #16 in the 3GPP TR 23.700-98. SA WG6 recommends SA WG2 also provide response to this question. 6. As the 3GPP defines interaction between NEF and AF via Northbound APIs, does it impose any kind of timing constraints (soft or hard d","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11540,"status":"noted","reservation_date":"2022-03-25 17:03:59","uploaded":"2022-03-29 16:30:37","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG5, SA WG3, SA WG2","lsoriginalls":"S6-220432","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2201969.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202063","title":"Outcome of UE Policies delivery procedure","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to specify the outcome of the UE Policy delivery procedure in Npcf_EventExposure_Notify in 5.2.5.7.4.","secretary_remarks":"r01 agreed. Revised to S2-2203427","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11610,"status":"revised","reservation_date":"2022-03-28 09:35:53","uploaded":"2022-03-29 07:31:05","revisionof":"","revisedto":"S2-2203427","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3423.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202063.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202064","title":"Outcome of UE Policies delivery procedure","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to specify the outcome of the UE Policy delivery procedure in Event reporting description in 6.1.3.8.","secretary_remarks":"r01 agreed. Revised to S2-2203428","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11630,"status":"revised","reservation_date":"2022-03-28 09:39:09","uploaded":"2022-03-29 07:31:05","revisionof":"","revisedto":"S2-2203428","release":"Rel-17","crspec":"23.503","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":708.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202064.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202089","title":"Discovery and selection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding text that API discovery can be done by CAPIF","secretary_remarks":"Postponed","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11650,"status":"postponed","reservation_date":"2022-03-28 15:23:26","uploaded":"2022-03-29 21:04:35","revisionof":"","revisedto":"S2-2203874","release":"Rel-17","crspec":"23.501","crspecversion":"17.4.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":3587.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202089.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202090","title":"AF specific UE ID retrieval procedure correction","source":"Ericsson, Qualcomm Incorporated","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the interaction between NEF and BSF is mandatory for the AD specific UE ID retrieval","secretary_remarks":"Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11660,"status":"agreed","reservation_date":"2022-03-28 15:23:27","uploaded":"2022-03-29 21:04:35","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":3427.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220397","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202090.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202091","title":"Correction related to EAS IP Address in EDI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Point out that IP4 Subnet and\/or IPv6 prefixes may also be used.","secretary_remarks":"r01 agreed. Revised to S2-2203429","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11670,"status":"revised","reservation_date":"2022-03-28 15:23:28","uploaded":"2022-03-29 21:04:35","revisionof":"","revisedto":"S2-2203429","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":52.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202091.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202273","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: Change the description '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.' to '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 AF triggered EAS IP replacement procedure.'. Correct a editorial error.","secretary_remarks":"Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11690,"status":"agreed","reservation_date":"2022-03-29 02:40:40","uploaded":"2022-03-29 04:32:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":53.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202273.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202374","title":"Correction of EAS Deployment Information Management procedures and services","source":"Tencent, Tencent Cloud","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.1.1, the DNS response message should be from the DNS server. Delete 'UE' in the related description. In clause 6.2.3.4.3 step 3-4, change 'DNAI(s)' to 'S-NSSAI(s)'. In clause 6.2.3.4.3 step 3-4 and clause 6.2.3.4.4 step 1, clarify that the parameter 'application(s)' should be 'application identifier'. In clause 7.1.1, change the service name Neasdf_NodeLevelDNSHandlingInfo to Neasdf_BaselineDNSPattern.","secretary_remarks":"r04 agreed. Revised to S2-2203430","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11700,"status":"revised","reservation_date":"2022-03-29 07:40:06","uploaded":"2022-03-29 13:32:45","revisionof":"","revisedto":"S2-2203430","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":54.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202374.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202397","title":"Alignment to SA WG6 on ECS Configuration Information","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refers to the definition of ECS configuration information in TS 23.558.","secretary_remarks":"Postponed","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11720,"status":"postponed","reservation_date":"2022-03-29 08:00:56","uploaded":"2022-03-29 14:19:30","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":55.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202397.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202398","title":"Alignment to SA WG6 on ECS Configuration Information","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refers to the definition of ECS configuration information in TS 23.558. Adds TS 23.558 as reference.","secretary_remarks":"Postponed","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11730,"status":"postponed","reservation_date":"2022-03-29 08:00:57","uploaded":"2022-03-29 14:19:30","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3443.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202398.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202741","title":"Parameter supplement of EDI","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding DNAI in EAS Deployment Information to clarify that which DNAI that DNS server can server for.","secretary_remarks":"r06 agreed. Revised to S2-2203602.","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11740,"status":"revised","reservation_date":"2022-03-29 14:28:32","uploaded":"2022-03-29 14:29:59","revisionof":"","revisedto":"S2-2203602","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":56.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202741.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202779","title":"LS on AF specific UE ID retrieval","source":"CT WG3","contact":"Tianmei Liang","contact-id":69846,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 observes some misalignment on AF specific UE ID retrieval in TS 23.501, TS 23.502 and TS 23.558, would like to share CT WG3 observations and questions(Q) for aligned solution and requirement from stage 2. {. . .} Action: CT WG3 asks SA WG2, SA WG3 and SA WG6 to kindly consider and reply above questions and consider the needed updates in the related specifications.","secretary_remarks":"Response drafted in S2-2202964. Final response in S2-2203426","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11550,"status":"replied to","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6, SA WG3, SA WG2","Cc":"CT WG4","lsoriginalls":"C3-221735","lsreply":"S2-2203426, S2-2203426","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202779.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202796","title":"LS from SA WG3: Reply LS on Further Operator Platform Group questions following SDO Workshop","source":"SA WG3","contact":"Rajavelsamy Rajadurai","contact-id":33521,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank GSMA OPAG for their LS on Operator Platform Group questions following SDO Workshop (S3-220443). SA WG3 would like to provide answers to security related questions raised: 1. Which are the security mechanisms\/procedures proposed for UNI authentication? [SA WG3] SA WG3 has agreed the attached pCRs (S3-220553 and S3-220554) for the security mechanisms proposed for EDGE-1 and EDGE-4 interfaces.","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11580,"status":"noted","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG5, SA WG6, SA WG2","lsoriginalls":"S3-220571","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202796.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202797","title":"LS from TSG SA: Reply LS to GSMA OPG on Further Operator Platform Group questions following SDO Workshop","source":"TSG SA","contact":"Suresh Chitturi","contact-id":61003,"tdoctype":"LS in","for":"Information","abstract":"TSG SA thanks GSMA OPAG for the workshop held on January 21st, to discuss the details of the Operator Platform API mapping and the feedback from 3GPP. SA has reviewed the follow-up questions from GSMA OPAG and prepared the below responses from 3GPP (with inputs from SA WG2, SA WG3 and SA WG6 working groups). {. . .} TSG SA kindly asks GSMA OPAG to take into account the above responses.","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11590,"status":"noted","reservation_date":"2022-03-29 15:34:29","uploaded":"2022-03-29 17:47:55","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, ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"SP-220346","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202797.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202845","title":"Clarification for Edge Relocation Triggered by AF","source":"Lenovo, Motorola Mobility","contact":"Tingfang Tang","contact-id":81429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Mainly Clarify the Nnef_TrafficInfluence_Create\/Update Request to the NEF, or Npcf_PolicyAuthorization_Create\/Update Request to include Indication for EAS Relocation, target DNAI, traffic descriptor information and N6 routing information at target DNAI. One editorial correction.","secretary_remarks":"r01 agreed. Revised to S2-2203431","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11760,"status":"revised","reservation_date":"2022-03-29 16:11:18","uploaded":"2022-03-29 16:30:04","revisionof":"","revisedto":"S2-2203431","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3460.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202845.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202846","title":"Clarification on EAS Deployment Information","source":"Lenovo, Motorola Mobility","contact":"Tingfang Tang","contact-id":81429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification on EAS Deployment Information to support the following: applying the DNAI onto FQDN(s) within the EDI Supporting EDI provided for more than one application","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11780,"status":"noted","reservation_date":"2022-03-29 16:11:18","uploaded":"2022-03-29 16:30:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":57.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202846.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202847","title":"Clarification on EAS Deployment Information","source":"Lenovo, Motorola Mobility","contact":"Tingfang Tang","contact-id":81429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the related Nnef_EASDeployment service for Supporting EDI provided for more than one application sharing the same EDI.","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11790,"status":"noted","reservation_date":"2022-03-29 16:11:19","uploaded":"2022-03-29 16:30:04","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3461.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202847.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202851","title":"Update of EASDF functional description and clarication on scope of EAS in EAS discovey and selection procedure","source":"IIT Delhi","contact":"Ashish Singh Patel","contact-id":94406,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change the functional description of the EASDF in clause 5.1.1 about EAS discovery and selection. Add a sentence in Note 3 in clause 6.2.3 to clarify the scope of EAS(s) with reference to EES(s) and ECS (s).","secretary_remarks":"Noted","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11800,"status":"noted","reservation_date":"2022-03-29 16:30:05","uploaded":"2022-03-29 16:41:00","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":58.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202851.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202963","title":"Correction to the Service Specific Authorization procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removes 'for Application guidance for URSP determination'","secretary_remarks":"Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11810,"status":"agreed","reservation_date":"2022-03-29 21:16:50","uploaded":"2022-03-29 21:20:35","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3464.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202963.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2202964","title":"[DRAFT] Reply LS on AF specific UE ID retrieval","source":"Qualcomm Incorporated, Ericsson","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG3, SA WG6, CT WG4","secretary_remarks":"Response to S2-2202779. r02 agreed. Revised to S2-2203426","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11560,"status":"revised","reservation_date":"2022-03-29 21:20:26","uploaded":"2022-03-29 22:01:37","revisionof":"","revisedto":"S2-2203426","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG3, SA WG6, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2202964.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203426","title":"[DRAFT] Reply LS on AF specific UE ID retrieval","source":"Qualcomm Incorporated, Ericsson","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG3, SA WG6, CT WG4","secretary_remarks":"Revision of S2-2202964r02. Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11570,"status":"approved","reservation_date":"2022-04-13 09:55:23","uploaded":"2022-04-13 15:41:15","revisionof":"S2-2202964","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2202779","lsto":"CT WG3","Cc":"SA WG3, SA WG6, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203426.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203427","title":"Outcome of UE Policies delivery procedure","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to specify the outcome of the UE Policy delivery procedure in Npcf_EventExposure_Notify in 5.2.5.7.4.","secretary_remarks":"Revision of S2-2202063r01. Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11620,"status":"agreed","reservation_date":"2022-04-13 09:55:23","uploaded":"2022-04-14 09:01:24","revisionof":"S2-2202063","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3423.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203427.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203428","title":"Outcome of UE Policies delivery procedure","source":"Samsung","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to specify the outcome of the UE Policy delivery procedure in Event reporting description in 6.1.3.8.","secretary_remarks":"Revision of S2-2202064r01. Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11640,"status":"agreed","reservation_date":"2022-04-13 09:55:24","uploaded":"2022-04-14 09:01:24","revisionof":"S2-2202064","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":708.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203428.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203429","title":"Correction related to EAS IP Address in EDI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Point out that IP4 Subnet and\/or IPv6 prefixes may also be used.","secretary_remarks":"Revision of S2-2202091r01. Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11680,"status":"agreed","reservation_date":"2022-04-13 09:55:25","uploaded":"2022-04-14 09:01:24","revisionof":"S2-2202091","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":52.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203429.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203430","title":"Correction of EAS Deployment Information Management procedures and services","source":"Tencent, Tencent Cloud, Ericsson, Huawei, HiSilicon","contact":"Zhuoyun Zhang","contact-id":78278,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.1.1, Delete 'response' in the related description. In clause 6.2.3.4.3 step 3-4, remove 'DNN and\/or S-NSSAI and\/or application(s)'. In clause 6.2.3.4.4 step 1, remove 'DNN and\/or S-NSSAI and\/or application(s)'. In clause 7.1","secretary_remarks":"Revision of S2-2202374r04. Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11710,"status":"agreed","reservation_date":"2022-04-13 09:55:26","uploaded":"2022-04-14 09:01:24","revisionof":"S2-2202374","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":54.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203430.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203431","title":"Clarification for Edge Relocation Triggered by AF","source":"Lenovo, Motorola Mobility, Ericsson","contact":"Tingfang Tang","contact-id":81429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Mainly Clarify the Nnef_TrafficInfluence_Create\/Update Request to the NEF, or Npcf_PolicyAuthorization_Create\/Update Request to include Indication for EAS Relocation, target DNAI, traffic descriptor information and N6 routing informatio","secretary_remarks":"Revision of S2-2202845r01. Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11770,"status":"agreed","reservation_date":"2022-04-13 09:55:27","uploaded":"2022-04-14 09:01:24","revisionof":"S2-2202845","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3460.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203431.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2203602","title":"Parameter supplement of EDI","source":"China Mobile, Huawei, Ericsson","contact":"Dan Wang","contact-id":87155,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the DNAI(s) in the EAS Deployment Information to clarify for which DNAI(s) thed DNS server(s) can be used.","secretary_remarks":"Revision of S2-2202741r06. Approved","agenda_item_sort_order":11,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11750,"status":"agreed","reservation_date":"2022-04-13 09:55:43","uploaded":"2022-04-14 09:01:26","revisionof":"S2-2202741","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.2.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":56.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220398","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_150E_Electronic_2022-04\/Docs\/S2-2203602.zip","group":"S2","meeting":"S2-150-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]