[{"name":"S2-2100262","title":"LS from SA WG4: LS on Server Domain Name Usage for Application Traffic Detection","source":"SA WG4","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 has specified the 5G Media Streaming (5GMS) architecure within Release 16, which enables usage of some Network Features using N5 or N33. For dynamic policy invocation, an ASP can configure one or more Policy Templates within the 5GMSd AF, which can then be individually invoked by a 5GMSd Client. The 5GMSd Client provides a Service Data Flow description (IP Packet Filter Set or server domain name(s)) when activating a dynamic policy to be applied by the 5GMSd AF. The 5GMSd AF then acts as AF towards the PCF or NEF. For using server domain names within a Service Data Flow description, SA WG4 understands that the 5GMSd AF first needs to provision a Packet Flow Description (PFD) containing a domain name using the PFD Management API, and then it selects the provisioned PFD (part of a PfdData object) using either the N5 Npcf_PolicyAuthorization API or else via the N33 AfSessionWithQos or ChargeableParty APIs. Note that a single 5GMSd AF might provision multiple PfdData objects, each containing one or more PFDs. Furthermore, SA WG4 understands that in the subsequent dynamic policy invocation procedures defined for the 5FMSd AF, previously provisioned PFDs can be referenced as an alternative traffic detection parameter to full flow descriptions. - When the Policy Template relates to QoS, the 5GMSd AF may use the Nnef_AFsessionWithQoS service as defined in TS 23.502 [3] clause 5.2.6.9. (The complete call flow is described in TS 23.502 clause 4.15.6.6); - When the Policy Template relates to a different charging scheme, the 5GMSd AF may use the Nnef_ChargeableParty service as defined in TS 23.502 [3] clause 5.2.6.8. Based on the above assumptions, SA WG4 would like to ask the following clarification questions to SA WG2 and CT WG3: 1: When invoking the Nnef_AFSessionWithQoS method, is it possible to use the application identifier (as a reference to a set of PFDs) instead of the flow description? 2: What is the relationship between the AF Identifer (SCS\/AS ID in 4G) and the AF application ID and\/or the application identifier? 3: When invoking a particular policy using Nnef_AFSessionWithQoS, is it possible to provide the DNN, the S-NSSAI, and\/or a reference to the server domain name for the purposes of traffic identification? NOTE: The same questions apply to Nnef_ChargeableThird Party API. Action: SA WG4 kindly asks SA WG2 to provide feedback for question 1 and question 3.","secretary_remarks":"Responses drafed in S2-2100296 and S2-2100672. Postponed","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11470,"status":"postponed","reservation_date":"2021-02-15 16:06:05","uploaded":"2021-02-15 16:24:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3","Cc":"","lsoriginalls":"S4-210311","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100262.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100269","title":"QoS control in the VPLMN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 4.16 and clause 5.2.5.4 to include the QoS constraints from the VPLMN to the PCF.","secretary_remarks":"r02 agreed. Revised to S2-2101561.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11430,"status":"revised","reservation_date":"2021-02-15 23:34:47","uploaded":"2021-02-18 16:39:33","revisionof":"","revisedto":"S2-2101561","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2487.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100269.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100270","title":"QoS control in the VPLMN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In home routed roaming case the H-PCF generates both the Authorized and Subsequent Session-AMBR within the limits supported by the VPLMN. In home routed roaming case the H-PCF generates both the Authorized and Subsequent 5QI\/ARP within the limits supported by the VPLMN.","secretary_remarks":"r04 agreed. Revised to S2-2101562.","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11450,"status":"revised","reservation_date":"2021-02-15 23:34:51","uploaded":"2021-02-18 16:39:33","revisionof":"","revisedto":"S2-2101562","release":"Rel-16","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":516.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100270.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100293","title":"Application Identifier for SCEF API ChargebleParty and AS Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce Application Identifier for AS session with required QoS case in clause 5.11 Introduce Application Identifier for chargeable party case in clause 5.12","secretary_remarks":"Noted","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11490,"status":"noted","reservation_date":"2021-02-15 23:46:36","uploaded":"2021-02-18 16:40:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.682","crspecversion":"16.8.0","workitem":[{"winame":"TEI16"},{"winame":" 5GMS3"}],"crnumber":475.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100293.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100294","title":"Application Identifier for NEF API ChargebleParty and AF Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce Application Identifier in AF requests to influence traffic routing flow, in clause 4.3.6.2 Introduce Application Identifier for Chargeble Party at AF session setup, in clause 4.15.6.4\/5 Introduce Application ID for AF session with QoS procedures, in clause 4.15.6.6\/6a Introduce Application Identifier in ChargeableParty service operations in clause 5.2.6.8 Introduce Application Identifier in AFSessionWithQoS service operations in clause 5.2.6.9","secretary_remarks":"Noted","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11500,"status":"noted","reservation_date":"2021-02-15 23:46:37","uploaded":"2021-02-18 16:40:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"TEI16"},{"winame":" 5GMS3"}],"crnumber":2490.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100294.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100295","title":"DNN and S-NSSAI for NEF API ChargebleParty and AF Session with QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce DNN and S-NSSAI for Chargeble Party at AF session setup, in clause 4.15.6.4\/5 Introduce DNN and S-NSSAI for AF session with QoS procedures, in clause 4.15.6.6\/6a Introduce DNN and S-NSSAI in ChargeableParty service operations Introduce DNN and S-NSSAI in AFSessionWithQoS service operations","secretary_remarks":"Noted","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11510,"status":"noted","reservation_date":"2021-02-15 23:46:39","uploaded":"2021-02-18 16:40:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"TEI16"},{"winame":" 5GMS3"}],"crnumber":2491.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100295.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100296","title":"[DRAFT] Reply LS on Server Domain Name Usage for Application Traffic Detection","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS to SA WG4 provider SA WG2 conclusions on NEF related service API","secretary_remarks":"Response to S2-2100262. Noted","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11480,"status":"noted","reservation_date":"2021-02-15 23:46:40","uploaded":"2021-02-18 16:40:21","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GMS3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100296.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100330","title":"Remove the NEF pre-configuration option for PFD push and correct the handling of Allowed Delay","source":"Nokia, Nokia Shanghai Bell","contact":"Apostolos Papageorgiou","contact-id":87439,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The statement that 'The NEF (PFDF) may be configured with the list of SMFs where PFD(s) should be distributed' is removed as the feature is incomplete and not implementable in Rel-16. Clarify that the Allowed Delay is handled as described, not only if the PLMN support only pull, but even if the PLMN supports push but not for a certain application identifier.","secretary_remarks":"Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11530,"status":"agreed","reservation_date":"2021-02-16 21:39:28","uploaded":"2021-02-18 16:47:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":523.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-210243","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100330.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100331","title":"PFD provisioning correction to exclude pre-configuration","source":"Nokia, Nokia Shanghai Bell","contact":"Apostolos Papageorgiou","contact-id":87439,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: AF authorisation by NEF (as usual) and PFD authorisation by PFDF are specified explicitly. In call flow 4.18.3.2-1, subscription is added, 'NEF' is replaced by 'NEF(PFDF)', and notification ACK is removed. Figure 4.18.3.1-1 is updated to align it with the text.","secretary_remarks":"Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11540,"status":"agreed","reservation_date":"2021-02-16 21:39:29","uploaded":"2021-02-18 16:47:02","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2495.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-210243","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100331.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2100672","title":"[DRAFT] LS Reply on Server Domain Name Usage for Application Traffic Detection","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to the LS on Server Domain Name Usage for Application Traffic Detection","secretary_remarks":"Response to S2-2100262. Noted","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11520,"status":"noted","reservation_date":"2021-02-18 09:51:51","uploaded":"2021-02-18 10:40:04","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GMS3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2100672.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101561","title":"QoS control in the VPLMN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 4.16 and clause 5.2.5.4 to include the QoS constraints from the VPLMN to the PCF.","secretary_remarks":"Revision of S2-2100269r02. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11440,"status":"agreed","reservation_date":"2021-03-05 08:05:07","uploaded":"2021-03-05 08:31:19","revisionof":"S2-2100269","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.7.1","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":2487.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210082","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101561.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2101562","title":"QoS control in the VPLMN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In home routed roaming case the H-PCF generates both the Authorized and Subsequent Session-AMBR within the limits supported by the VPLMN. In home routed roaming case the H-PCF generates both the Authorized and Subsequent 5QI\/ARP within the limits supported by the VPLMN.","secretary_remarks":"Revision of S2-2100270r04. Approved","agenda_item_sort_order":19,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11460,"status":"agreed","reservation_date":"2021-03-05 08:05:08","uploaded":"2021-03-05 08:31:19","revisionof":"S2-2100270","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.7.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI16"}],"crnumber":516.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-210082","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_143e_Electronic\/Docs\/S2-2101562.zip","group":"S2","meeting":"S2-143-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]