[{"name":"S2-2205396","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-2203642 from S2#151E. Response drafted in S2-2205632. Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11560,"status":"postponed","reservation_date":"2022-06-17 13:06:18","uploaded":"2022-06-17 14:33:19","revisionof":"S2-2203642","revisedto":"S2-2208102","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-222419","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205396.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205414","title":"LS from CT WG3: LS on user s consent for EDGEAPP","source":"CT WG3","contact":"Tianmei Liang","contact-id":69846,"tdoctype":"LS in","for":"Information","abstract":"To: SA WG3. CC: SA WG2","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":11580,"status":"noted","reservation_date":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"C3-223780","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205414.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205435","title":"LS from SA WG3: Reply LS on AF specific UE ID retrieval","source":"SA WG3","contact":"Ferhat Karakoc","contact-id":86196,"tdoctype":"LS in","for":"Information","abstract":"To: CT WG3. CC: SA WG2","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":11590,"status":"noted","reservation_date":"2022-06-17 13:06:19","uploaded":"2022-06-20 10:59:53","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2","lsoriginalls":"S3-221161","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205435.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205627","title":"Clarification on Authorization of Service Specific parameter provisioning","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The procedure for authorization of service specific parameter provisioning is described as a standalone procedure that can be included within the procedure for Service specific parameter provisioning (clause 4.15.6.7) and referred from any of the use cases that make use of the service specific parameter provisioning if needed (e.g. it can be referred to by the procedures for application guidance for URSP determination). When the NEF executes the authorization procedure of service parameter provisioning, the NEF omits the GPSI\/External Group Id mapping operation with UDM. The procedure and services for authorization of service specific parameter provisioning is further completed\/corrected: Parameters of the authorization request\/responses (NEF-UDM): Update notification address for sending notifications to NEF is defined as mandatory. AF Id is optional input in the authorization request to UDM. SUPI\/Internal Group ID are included in the authorization response. Validity time provided by UDM to NEF in response to authorization request of service parameter provisioning is removed. Parameters in update authorization notification (UDM-NEF): SUPI\/Internal Group ID are included in the request. Cause of the update authorization notification is defined as part of the request and not the response. Service type is defined as mandatory input in the request. MTC provider and AF id are included as optional input in the request. Parameters in the service parameter notify request (NEF-AF): Update authorization information is included in the request to AF. When the AF informs the NEF that previously provisioned service specific params are no longer valid, there is no possibility (missing operation) for the NEF to remove the authorization in UDM. A new operation to remove authorization in UDM is added. In clause 4.15.6.10 the precedence order description for a list of URSP rules of the same AF is added","secretary_remarks":"Revision (Postponed) of S2-2203722 from S2#151E. r03 agreed. Revised to S2-2207397.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11600,"status":"revised","reservation_date":"2022-08-08 19:52:04","uploaded":"2022-08-10 17:50:57","revisionof":"S2-2203722","revisedto":"S2-2207397","release":"Rel-17","crspec":"23.502","crspecversion":"17.5.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3470.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205627.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205628","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: Inclusion of a the new indicator Dynamic SM Policy control required","secretary_remarks":"Revision (Postponed) of S2-2203878 from S2#151E. Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11620,"status":"noted","reservation_date":"2022-08-08 19:52:05","uploaded":"2022-08-10 17:50:57","revisionof":"S2-2203878","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":59.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205628.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205629","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: New indication for EAS discovery. Removal of FQDNs as Traffic Descriptors.","secretary_remarks":"Revision (Postponed) of S2-2203875 from S2#151E. Confirm Spec version used - CR states 17.4.0! Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11630,"status":"postponed","reservation_date":"2022-08-08 19:52:07","uploaded":"2022-08-10 17:50:57","revisionof":"S2-2203875","revisedto":"S2-2208370","release":"Rel-17","crspec":"23.501","crspecversion":"17.5.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3634.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205629.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205630","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: New indication for EAS discovery. Transfer of EASDF subscription information from SMF to PCF.","secretary_remarks":"Revision (Postponed) of S2-2203876 from S2#151E. Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11640,"status":"noted","reservation_date":"2022-08-08 19:52:08","uploaded":"2022-08-10 17:50:57","revisionof":"S2-2203876","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.5.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3474.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205630.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205631","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: New indication for EAS discovery.","secretary_remarks":"Revision (Postponed) of S2-2203877 from S2#151E. Noted","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11650,"status":"noted","reservation_date":"2022-08-08 19:52:09","uploaded":"2022-08-10 17:50:57","revisionof":"S2-2203877","revisedto":"","release":"Rel-17","crspec":"23.503","crspecversion":"17.5.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":721.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205631.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205632","title":"[DRAFT] Reply to CT WG3 LS on handling of FQDN ranges in AF influence on traffic routing procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3","secretary_remarks":"Revision (Postponed) of S2-2203880 from S2#151E. Response to S2-2205396. Postponed","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11570,"status":"postponed","reservation_date":"2022-08-08 19:52:10","uploaded":"2022-08-10 17:50:57","revisionof":"S2-2203880","revisedto":"","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_152E_Electronic_2022-08\/Docs\/S2-2205632.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205730","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":"Agreement","abstract":"This DP is triggered by the LS S2-2205396\/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":11660,"status":"noted","reservation_date":"2022-08-09 11:16:51","uploaded":"2022-08-10 17:50:57","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_152E_Electronic_2022-08\/Docs\/S2-2205730.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2205733","title":"Adding the EAS rediscovery indication on the PDU session modification procedure","source":"China Unicom","contact":"TianQi Xing","contact-id":89168,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding that the SMF may decide to modify PDU Session to send the EAS rediscovery indication to the UE in Step 1d of clause 4.3.3.2.","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":11670,"status":"agreed","reservation_date":"2022-08-09 12:01:29","uploaded":"2022-08-10 06:19:26","revisionof":"","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.5.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3512.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-220777","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2205733.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2206891","title":"Corrections related to EDNS Client Subnet option","source":"Nokia, Nokia Shanghai Bell","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: EASDF behaviour is corrected to properly handle DNS query and DNS Response messages in cases where ECS option is added by the UE in the DNS query and when ECS option is not added by the UE in the DNS query","secretary_remarks":"r06 agreed. Revised to S2-2207398.","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11680,"status":"revised","reservation_date":"2022-08-10 19:02:39","uploaded":"2022-08-10 19:06:52","revisionof":"","revisedto":"S2-2207398","release":"Rel-17","crspec":"23.548","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":62.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2206891.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2207397","title":"Clarification on Authorization of Service Specific parameter provisioning","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The procedure for authorization of service specific parameter provisioning is described as a standalone procedure that can be included within the procedure for Service specific parameter provisioning (clause 4.15.6.7) and referred from any of the use cases that make use of the service specific parameter provisioning if needed (e.g. it can be referred to by the procedures for application guidance for URSP determination). When the NEF executes the authorization procedure of service parameter provisioning, the NEF omits the GPSI\/External Group Id mapping operation with UDM. The procedure and services for authorization of service specific parameter provisioning is further completed\/corrected: Parameters of the authorization request\/responses (NEF-UDM): Update notification address for sending notifications to NEF is defined as mandatory. AF Id is optional input in the authorization request to UDM. SUPI\/Internal Group ID are included in the authorization response. Validity time provided by UDM to NEF in response to authorization request of service parameter provisioning is removed. Parameters in update authorization notification (UDM-NEF): SUPI\/Internal Group ID are included in the request. Cause of the update authorization notification is defined as part of the request and not the response. Service type is defined as mandatory input in the request. MTC provider and AF id are included as optional input in the request. Parameters in the service parameter notify request (NEF-AF): Update authorization information is included in the request to AF. When the AF informs the NEF that previously provisioned service specific params are no longer valid, there is no possibility (missing operation) for the NEF to remove the authorization in UDM. A new operation to remove authorization in UDM is added.","secretary_remarks":"Revision of S2-2205627r03. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11610,"status":"agreed","reservation_date":"2022-08-25 04:52:08","uploaded":"2022-08-30 09:51:09","revisionof":"S2-2205627","revisedto":"","release":"Rel-17","crspec":"23.502","crspecversion":"17.5.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":3470.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-220777","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2207397.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2207398","title":"EDNS Client Subnet option correction","source":"Nokia, Nokia Shanghai Bell, Ericsson, Huawei, HiSilicon","contact":"Shubhranshu Singh","contact-id":86758,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: EASDF behaviour is corrected to properly handle DNS query and DNS Response messages in cases where ECS option is added by the UE in the DNS query and when ECS option is not added by the UE in the DNS query","secretary_remarks":"Revision of S2-2206891r06. Approved","agenda_item_sort_order":46,"ainumber":"8.3","ainame":"Enhancement of support for Edge Computing in 5GC (eEDGE_5GC)","tdoc_agenda_sort_order":11690,"status":"agreed","reservation_date":"2022-08-25 04:52:09","uploaded":"2022-08-30 09:51:09","revisionof":"S2-2206891","revisedto":"","release":"Rel-17","crspec":"23.548","crspecversion":"17.3.0","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":62.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-220777","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_152E_Electronic_2022-08\/Docs\/S2-2207398.zip","group":"S2","meeting":"S2-152-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]