[{"name":"S2-2208102","title":"LS from CT WG3: LS on handling of FQDN ranges in AF influence on traffic routing procedures","source":"CT WG3","contact":"Susana Fernandez","contact-id":42321,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is discussing the support of FQDN ranges as defined in TS 23.501 for AF influence on traffic routing procedures. According to that TS the FQDN range is considered one example of traffic filtering information and when provided, 'it may be used by SMF as one of the triggers for retrieving EAS Deployment Information from NEF. Retrieval of EAS Deployment Information is defined in TS 23.548 [130]'. CT WG3 has the following questions: Question 1: Is the FQDN range only used as a trigger to initiate the retrieval of EAS Deployment Information from NEF or is it also used to identify the traffic for influencing SMF routing decisions? Question 2: If it is used to identify the traffic for influencing SMF routing decisions, can SA WG2 clarify how it works? Is the FQDN range(s) used to identify the sessions\/users for which the EDIs apply, and if yes, how is this applicability exactly determined? Question 3: If it is only used as a trigger for the retrieval of EAS Deployment Information, why an FQDN range is required? Could a specific indicator or the application identifier included to identify the traffic satisfy the same purpose?. Action: CT WG3 kindly requests SA WG2 to answer the questions above and update their Specifications if considered necessary.","secretary_remarks":"Revision of Postponed S2-2205396 from S2#152-e. Response drafted in S2-2208372. Final response in S2-2209269","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11170,"status":"replied to","reservation_date":"2022-09-21 05:20:39","uploaded":"2022-09-21 08:06:27","revisionof":"S2-2205396","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-222419","lsreply":"S2-2209269, S2-2209269","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208102.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208160","title":"LS from SA WG6: Reply LS to OPAG_34_Doc_07_OPAG_LS ETSI-3GPP-Network integration","source":"SA WG6","contact":"Basavaraj (Basu) Pattan","contact-id":61285,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank GSMA OPAG for the LS, and sharing the draft Operator Platform's (OP) Network Integration Support APIs definition document that includes SBI-NR and NEF NBI usage for SBI-NR. SA WG6 thanks OPAG for taking into account the work of SA WG6 (3GPP TS 23.558, and corresponding stage 3 work by CT WG3 in 3GPP TS 29.558), namely the definition of Application Relocation API and Confirm User Location API. SA WG6 believes these APIs should be listed as NBI APIs (and not SBI-NR) in clause 1.1 (Table 1) and in clause 1.7, of the Operator Platform's (OP) Network Integration Support APIs definition document, since these APIs are not directly exposed by the core network, but rather at the Edge Enablement Layer (EEL) in reference to the EDGEAPP architecture, which is mapped to OP as specified in Annex D.2 of 3GPP TS 23.558. Further, SA WG6 would like to bring to OPAG s attention that: 1) Network capabilities (some of which are considered in your current document) are also available via EES, where EES may re-expose the network capabilities of the 3GPP core network to the EAS(s) via NB APIs as specified in clause 8.7.3 of 3GPP TS 23.558 with additional EEL abstraction 2) Furthermore, you may like to consider the additional EES capabilities that are available to Edge Application Server (EAS) via NBI APIs as specified in clause 8.6 of 3GPP TS 23.558, in meeting the OP requirements. SA WG6 agrees that collaboration among SDOs (3GPP, ETSI ISG MEC, and GSMA) is essential to avoid market fragmentation. As part of Release 18, SA WG6 is currently studying on enhancements to architecture for enabling Edge Applications in 3GPP TR 23.700-98, which includes additional NBI APIs in new R18 functionality e.g. to support federation and roaming. Should you have any queries or further clarifications on these APIs, SA WG6 is happy to elaborate and provide more information.","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":11200,"status":"noted","reservation_date":"2022-09-21 08:54:33","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPAG","Cc":"TSG SA, SA WG2, SA WG3, SA WG5, ETSI ISG MEC","lsoriginalls":"S6-222337","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208160.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208162","title":"LS from SA WG6: Forward on S6-222332, LS on Network federation interface for Telco edge consideration","source":"SA WG6","contact":"Niranth Amogh","contact-id":39608,"tdoctype":"LS in","for":"Action","abstract":"Background: GSMA OPG has developed PRD for Operator Platform Telco Edge Requirements which specifies architectural requirement and a corresponding reference architecture for Operator Platform. GSMA OPAG is developing the API specifications for interfaces or the Operator Platform. GSMA OPG, 3GPP and ETSI MEC ISG are coordinating to develop a single harmonized system architecture for edge computing. In this context, SA WG6, SA WG2 and SA WG5 have received the attached LS from GSMA OPAG about East West Bound Interface (EWBI) APIs PRD for feedback. The EWBI APIs PRD may have impacts to the edge computing work for Rel.18 in SA and CT WGs and hence a coordinated response to GSMA OPAG is required. SA WG6 is currently reviewing the EWBI APIs PRD and may provide detailed technical response for December Plenary to enable a coordinated LS response by TSG SA to GSMA OPAG. SA WG6 asks SA WG2, SA WG3 and SA WG5 to review the EWBI PRD and provide any technical response to TSG SA by December Plenary for a coordinated LS response by TSG SA to GSMA OPAG. SA WG6 asks SA to create a coordinated response, if necessary, based upon the inputs to the December plenary from the SA WGs. Action: SA WG6 asks SA WG2, SA WG3 and SA WG5 to review the EWBI PRD and provide any technical response to TSG SA by December Plenary for a coordinated LS response by TSG SA to GSMA OPAG.","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11210,"status":"postponed","reservation_date":"2022-09-21 08:54:33","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"S2-2210179","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, SA WG2, SA WG5","Cc":"TSG CT, CT WG1, CT WG3","lsoriginalls":"S6-222543","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208162.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208163","title":"LS from SA WG6: Reply LS on user\u2019s consent for EDGEAPP","source":"SA WG6","contact":"Wenliang Xu","contact-id":67079,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks CT WG3 for the LS on EDGEAPP user s consent observations and related questions. Question 1 to SA WG6: For the Eees_UEIdentfier API, whether a trusted EES can directly utilize the relevant 3GPP 5GC services or can only utilize the relevant 3GPP 5GC services via the NEF? Answer 1: Before replying to CT WG3, SA WG6 would like to check with SA WG2 for AF interaction with NFs. SA WG6 will further update CT WG3 after receiving feedback from SA WG2. Question to SA WG2: Since TS 23.502 clause 4.15.10 describes AF utilizing NEF service to obtain AF specific UE ID and clause 6.2.10 of TS 23.501 describes that a trusted AF can be allowed to directly interact with relevant NFs instead of using NEF, SA WG6 would like to ask SA WG2 whether a trusted AF can directly utilize UDM and BSF services to obtain AF specific UE ID in Rel-17. If so, what are the interaction details among those NFs without using NEF? Question 2 to SA WG3, SA WG6: Whether the External Identifier used as GPSI needs user s consent or not? Answer 2: As mentioned in an editor s note in clause 8.6.5.2 of TS 23.558, SA WG6 believe this is falling into SA WG3 remit to answer the question. Question 3 to SA WG3, SA WG6: Whether the token is needed or not for the user s consent mechanism required in SA WG3 specification? Answer 3: Regarding EDGE-3 Eees_UELocation API, the EAS may retrieve user consent before invoking EES service. Such a case is under study in TR 23.700-95 in Rel-18. Therefore, it is not supported in TS 23.558 in Rel-17 (see attached CR for clarification). Action: SA WG6 asks SA WG2 to provide answer for above question related to SA WG2.","secretary_remarks":"Response drafted in S2-2208373. Final response in S2-2209270","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11220,"status":"replied to","reservation_date":"2022-09-21 08:54:33","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG3","lsoriginalls":"S6-222555","lsreply":"S2-2209270, S2-2209270","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208163.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208164","title":"LS from SA WG6: Reply LS to Network federation interface for Telco edge consideration","source":"SA WG6","contact":"Samar Shailendra","contact-id":93216,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 would like to thank GSMA OPAG for the LS, the draft EWBI APIs interface definition document and the YAML file. SA WG6 has noted the interface definition document and the YAML file and we are currently studying the impact of the same on Edge Enabler Layer involving multiple ECSPs in Release 18 (see TR 23.700-98). Should we have any queries post our analysis, we will revert to GSMA OPAG for further clarifications. SA WG6 acknowledges that collaboration among SDOs (3GPP, ETSI ISG MEC, and GSMA) is essential to avoid market fragmentation. As part of Release 18, SA WG6 also intends to develop an external TR to capture alignment aspects of EDGEAPP with ETSI MEC and GSMA OP.","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":11250,"status":"noted","reservation_date":"2022-09-21 08:54:34","uploaded":"2022-09-22 05:01:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPAG","Cc":"TSG SA, SA WG2, SA WG3, SA WG5, ETSI ISG MEC","lsoriginalls":"S6-222557","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208164.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208368","title":"Correction related to traffic correlation in PCC rule","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding reference to TS 23.503 and relevant relation to the flows","secretary_remarks":"Revision of (Postponed) S2-2205633 from S2#152E. r04 agreed. Revised to S2-2209271.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11260,"status":"revised","reservation_date":"2022-09-29 11:53:05","uploaded":"2022-09-30 11:13:10","revisionof":"S2-2205633","revisedto":"S2-2209271","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":3663.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208368.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208369","title":"Correction related to traffic correlation in PCC rule","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding note stating when traffic correlation applies.","secretary_remarks":"Revision of (Postponed) S2-2205635 from S2#152E. r01 agreed. Revised to S2-2209272.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11280,"status":"revised","reservation_date":"2022-09-29 11:53:07","uploaded":"2022-09-30 11:13:10","revisionof":"S2-2205635","revisedto":"S2-2209272","release":"Rel-17","crspec":"23.503","crspecversion":"17.6.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":732.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208369.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208370","title":"Correction to clarify role of PCC in authorization of EAS Discovery procedure with EASDF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of FQDN Adding that also EAS Discovery with EASDF procedure described in 3GPP TS 23.548 can be used for SSC mode 3.","secretary_remarks":"Revision of (Postponed) S2-2205629 from S2#152E. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11300,"status":"agreed","reservation_date":"2022-09-29 11:53:08","uploaded":"2022-09-30 11:13:10","revisionof":"S2-2205629","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3634.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-221069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208370.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208371","title":"DP on role of PCC in authorization of EAS Discovery procedure with EASDF.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This DP is triggered by the LS S2-220xxxx\/C3-222419 and discusses how and what PCF can influence EAS discovery procedure based on AF influence traffic.","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":11310,"status":"noted","reservation_date":"2022-09-29 11:53:10","uploaded":"2022-09-30 11:13:10","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_153E_Electronic_2022-10\/Docs\/S2-2208371.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208372","title":"[DRAFT] Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures","source":"Ericsson [to be SA2]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures","secretary_remarks":"Response to S2-2208102. r02 agreed. Revised to S2-2209269.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11180,"status":"revised","reservation_date":"2022-09-29 11:53:10","uploaded":"2022-09-30 11:13:10","revisionof":"","revisedto":"S2-2209269","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208372.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208373","title":"[DRAFT] Response LS on Clarifications for AF specific UE ID retrieval","source":"Ericsson [to be SA2]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Response LS on Clarifications for AF specific UE ID retrieval","secretary_remarks":"Response to S2-2208163. r00 agreed. Revised to S2-2209270.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11230,"status":"revised","reservation_date":"2022-09-29 11:53:10","uploaded":"2022-09-30 11:13:10","revisionof":"","revisedto":"S2-2209270","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"CT WG3, CT WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208373.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2208576","title":"Clarifications for local event notification control","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Npcf_PolicyAuthorization_Subscribe service is replaced by the Npcf_PolicyAuthorization_Create or Update service as this is the correct service for subscription to QoS monitoring. Further references are added to clause 6.1.3.21 of TS 23.503 [4] and clause 5.33.3.1 of TS 23.501 [2] where the details of the parameters for the control of the QoS monitoring as well as the PCF and SMF behaviour are described. Parameter names and terminology is aligned within the clauses and with the parameter names used in 23.501 and 23.503. Some unclear or duplicated text is removed.","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":11320,"status":"agreed","reservation_date":"2022-09-30 07:46:08","uploaded":"2022-09-30 16:00:41","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.4.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":63.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-221069","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2208576.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209171","title":"Correction to clarify uses of FQDN Range in the AF request","source":"Nokia, Nokia Shanghai Bell","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: FQDN range is added as a new information in Nnef_TrafficInfluence and then in Session level policy information sent by PCF. This information is used by SMF to determine which EDI targeting a DNN + S-NSSAI applies to a PDU Session set up towards this DNN + S-NSSAI. If the SMF does not receive FQDN information in Session level policy information sent by PCF then no EDI applies to this PDU Session unless the application Id received in a PCC rule matches the application id in an EDI targeting the DNN + S-NSSAI. If the FQDN range of an EDI targeting the DNN + S-NSSAI of a PDU session does not include the the FQDN range in PDU Session level policy information sent by PCF then this EDI does not apply to the PDU Session","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11330,"status":"postponed","reservation_date":"2022-09-30 19:59:43","uploaded":"2022-09-30 20:03:43","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3751.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209171.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209172","title":"Correction to clarify uses of FQDN Range in the AF request","source":"Nokia, Nokia Shanghai Bell","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: FQDN range is added as a new information in Nnef_TrafficInfluence and then in Session level policy information sent by PCF. This information is used by SMF to determine which EDI targeting a DNN + S-NSSAI applies to a PDU Session set up towards this DNN + S-NSSAI. If the SMF does not receive FQDN information in Session level policy information sent by PCF then no EDI applies to this PDU Session unless the application Id received in a PCC rule matches the application id in an EDI targeting the DNN + S-NSSAI. If the FQDN range of an EDI targeting the DNN + S-NSSAI of a PDU session does not include the the FQDN range in PDU Session level policy information sent by PCF then this EDI does not apply to the PDU Session","secretary_remarks":"Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11340,"status":"postponed","reservation_date":"2022-09-30 20:05:37","uploaded":"2022-09-30 20:10:48","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.6.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":759.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209172.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209269","title":"Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures","source":"SA WG2","contact":"Magnus Olsson","contact-id":74324,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. Attachments: S2-2208370","secretary_remarks":"Revision of S2-2208372r02. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11190,"status":"approved","reservation_date":"2022-10-18 14:16:42","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208372","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208102","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209269.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209270","title":"Response LS on Clarifications for AF specific UE ID retrieval","source":"SA WG2","contact":"Magnus Olsson","contact-id":74324,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: CT WG3, CT WG4, SA WG3","secretary_remarks":"Revision of S2-2208373r00. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11240,"status":"approved","reservation_date":"2022-10-18 14:16:42","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208373","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2208163","lsto":"SA WG6","Cc":"CT WG3, CT WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209270.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209271","title":"Correction related to traffic correlation in PCC rule","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding descriptions about the usage of traffic correlation.","secretary_remarks":"Revision of S2-2208368r04. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11270,"status":"agreed","reservation_date":"2022-10-18 14:16:42","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208368","revisedto":"","release":"Rel-17","crspec":"23.501","crspecversion":"17.6.0","workitem":[{"winame":"Vertical_LAN"},{"winame":" TEI17"}],"crnumber":3663.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-221080","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209271.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2209272","title":"Correction related to traffic correlation in PCC rule","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding note stating when traffic correlation applies.","secretary_remarks":"Revision of S2-2208369r01. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11290,"status":"agreed","reservation_date":"2022-10-18 14:16:44","uploaded":"2022-10-18 14:31:16","revisionof":"S2-2208369","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.6.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI17"}],"crnumber":732.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-221079","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_153E_Electronic_2022-10\/Docs\/S2-2209272.zip","group":"S2","meeting":"S2-153-e","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]