[{"name":"S2-2001778","title":"LS from SA WG5: LS Reply to LS Reply to LS to SA WG2 Introduction of CHF Address from PCF","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 would like to thank SA WG2 for having considered the description on charging for 5G connection and mobility domain in their TS 23.501 specification. SA WG5 has reviewed the corresponding approved SA WG2 CR and has no specific comment. As requested by SA WG2, SA WG5 would like to provide further clarification on the motivation for the solution of CHF address(es) being provided to AMF by the PCF as part of Access and mobility policy control during registration as follows: At UE initial registration, the step after which the AMF has exchanged with the PCF for Access and mobility policy association has been determined by SA WG5 as the appropriate step for the AMF to interact with a CHF for charging the registration in some scenario. For this reason, the solution would allow the CHF Address(es) to be dynamically allocated by PCF as part of the same procedure and as an alternative of using NRF based selection. Note that CHF(s) to be selected by the AMF at UE registration may be independent from CHF(s) subsequently selected by SMF(s) on a per PDU session basis for UE registered in this AMF. Action: SA WG5 kindly asks SA WG2 to take into account the answer above in order to decide on whether and how to define the feature in their TS 23.503 specification.","secretary_remarks":"Postponed S2-2000026 from S2#136AH. Postponed","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10810,"status":"postponed","reservation_date":"2020-02-05 08:38:29","uploaded":"2020-02-05 08:39:25","revisionof":"S2-2000026","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"S5-197495","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001778.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001834","title":"Use of AppID and OSID in URSP","source":"AT&T, Orange, Charter Communications, Verizon, Telecom Italia, Telstra, Vodafone, China Mobile, NTT DOCOMO, Deutsch Telecom, Ericsson, Samsung","contact":"Farooq Bari","contact-id":57133,"tdoctype":"discussion","for":"Endorsement","abstract":"This contribution proposes way forward on use of AppID and OSID in URSP policies.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10820,"status":"noted","reservation_date":"2020-02-13 21:22:47","uploaded":"2020-02-14 20:04:01","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001834.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001868","title":"Clarification on support of UE policies by the UE","source":"Motorola Mobility, Lenovo, Ericsson","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The change alligns with the decision made in CT WG1 (3GPP TS 24.501) where it is clarified that provisioning of URSP rules and the UE Policy Delivery procedure by the PCF are mandatory supported at the UE. No additional work is needed in stage 3","secretary_remarks":"Revision of agreed S2-2001571 from SA2#136AH. Revised to S2-2002431.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10920,"status":"revised","reservation_date":"2020-02-14 11:24:41","uploaded":"2020-02-17 17:10:39","revisionof":"S2-2001571","revisedto":"S2-2002431","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":397.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001868.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001930","title":"Replace the reference to 23.203 to the clause in 23.503 in 4.3.6","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 4.3.6 to include content defined in clause 4.7 of TS 23.203. Changes in rev.2: New subclause to define requirements for service capability exposure of non session management policy control functionality. Replace the list of procedures by requirements for service capability exposure of session management policy control functionality. Extend UE Policy requirements to include V2X Policies.","secretary_remarks":"Revision of agreed S2-2001197 from SA2#136AH. Revised, merging S2-2002129, to S2-2002432.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10940,"status":"revised","reservation_date":"2020-02-16 19:24:03","uploaded":"2020-02-18 17:40:10","revisionof":"S2-2001197","revisedto":"S2-2002432","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":400.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001930.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001932","title":"PCC reference architecture clarification","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Reference archiatecture is updated to show both deployment options.","secretary_remarks":"Postponed","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11110,"status":"postponed","reservation_date":"2020-02-16 19:24:04","uploaded":"2020-02-18 17:40:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":409.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001932.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001955","title":"Clarification for evaluation on URSP","source":"OPPO","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The 'Allowed SSC mode' received from PDU Session rejection should also be considered for UE's evaluation on URSP rule The Rejection cause and allowed SSC mode (if any) applies to the evaluation of another RSD in the same URSP rule and also applies to other URSP rule.","secretary_remarks":"Postponed","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10990,"status":"postponed","reservation_date":"2020-02-17 07:37:01","uploaded":"2020-02-18 10:37:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":410.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001955.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001962","title":"Clarification on UE Policy Association establishment","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the AMF can decide to establish UE Policy Association based on local policy when UE Policy Container is not included in registration request. It is also clarified how PCF determines what information is to be updated to UE when PSI is not received.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11000,"status":"noted","reservation_date":"2020-02-17 08:32:35","uploaded":"2020-02-18 06:40:46","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2102.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001962.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2001963","title":"Correction on UE Policy Association Establishment procedure","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description regarding the scenario that no UE Policy Container is received during UE Policy Association Establishment procedure. Add description regarding UE Policy Association Establish procedure for the roaming scenario","secretary_remarks":"Revision of agreed S2-2001569 from S2#136AH. Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11010,"status":"noted","reservation_date":"2020-02-17 08:32:43","uploaded":"2020-02-18 10:18:17","revisionof":"S2-2001569","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1685.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2001963.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002033","title":"Clarifications on the OSId and AppId in the URSP rule","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that there are no standarized values of the OSid and AppId in the URSP values, and then including them in the URSP rule is possible if the UE vendor, the application provider and the MNO reach an agrement.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10890,"status":"noted","reservation_date":"2020-02-17 17:02:02","uploaded":"2020-02-18 17:40:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":"23.503","crspecversion":"15.8.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":411.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002033.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002034","title":"Clarifications on the OSId and AppId in the URSP rule","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Rel-16 mirror CR: Summary of change: Clarify that there are no standarized values of the OSid and AppId in the URSP values, and then including them in the URSP rule is possible if the UE vendor, the application provider and the MNO reach an agrement.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10900,"status":"noted","reservation_date":"2020-02-17 17:02:02","uploaded":"2020-02-18 17:40:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":412.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002034.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002035","title":"Clarifications on the OSId and AppId in the ATSSS rule","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that there are no standarized values of the OSid and AppId in the ATSSS values, and then including them in the ATSSS rule is possible if the UE vendor, the application provider and the MNO reach an agrement.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10910,"status":"noted","reservation_date":"2020-02-17 17:02:03","uploaded":"2020-02-18 17:40:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2116.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002035.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002071","title":"AFsessionWithQoS update","source":"vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the AFsessionWithQoS_Update procedure based on last meeting comments.","secretary_remarks":"Revised to S2-2002436.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11070,"status":"revised","reservation_date":"2020-02-18 02:48:29","uploaded":"2020-02-18 12:05:33","revisionof":"","revisedto":"S2-2002436","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2122.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002071.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002072","title":"Updates to the AFsessionWithQoS setup","source":"vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Move the behaviours of PCF for deriving required QoS from step 3 to step4.","secretary_remarks":"Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11090,"status":"agreed","reservation_date":"2020-02-18 02:48:33","uploaded":"2020-02-18 12:05:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2123.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200079","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002072.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002079","title":"Correction on the binding mechanism","source":"OPPO, Huawei, HiSilicon","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are proposed: Extend binding parameters with the Alternative QoS Parameter Sets, so that PCC Rules with or without Alternative QoS Parameter Sets are bound to different QoS flows even if the other binding parameters in the PCC rules are the same. Changes (highlighted in cyan) in REV 4: Change the binding parameter 'Alternative QoS Parameter Set(s)' to' 5QI(s) of the Alternative QoS Parameter Set(s)'. The reason is the GBR\/MBR will not be considered as the binding parameter. Editorial","secretary_remarks":"Revision of agreed S2-2001690 from S2#136AH. Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11100,"status":"noted","reservation_date":"2020-02-18 03:32:12","uploaded":"2020-02-18 10:37:40","revisionof":"S2-2001690","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":390.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002079.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002122","title":"Correction on flow binding about CN PDB","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: CN PDB should be considered during QoS Flow Binding.","secretary_remarks":"Postponed","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11020,"status":"postponed","reservation_date":"2020-02-18 07:57:46","uploaded":"2020-02-18 13:06:09","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":416.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002122.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002123","title":"Correction on QoS Flow Binding for QoS Flow Behaviour","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the following aspects which are unclear\/missing: - Correct reference to 23.501 for the establishment as well as modification of QoS Flow. - A modification of the same binding parameters in all PCC rules that are bound to the same QoS Flow should result in a QoS Flow modification but not in a re-evaluation of the binding of the PCC rules (as otherwise, a new QoS Flow would be established and the existing one removed) - If the last PCC rule that is bound to a QoS Flow is removed, the SMF shall delete the QoS Flow. - When a QoS Flow is removed, the SMF shall remove the PCC rules bound to this QoS Flow and report them to the PCF","secretary_remarks":"Revised to S2-2002434.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11030,"status":"revised","reservation_date":"2020-02-18 07:57:46","uploaded":"2020-02-18 13:06:09","revisionof":"","revisedto":"S2-2002434","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":417.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002123.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002124","title":"Discussion on Application Descriptor.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper aims at discussing how to deal with the Application Descriptor.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10840,"status":"noted","reservation_date":"2020-02-18 07:57:47","uploaded":"2020-02-18 15:16:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002124.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002125","title":"[DRAFT] LS on Application Descriptor Definition","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"An LS to GSMA on how to define Application Descriptor in URSP.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10850,"status":"noted","reservation_date":"2020-02-18 07:57:47","uploaded":"2020-02-18 15:16:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002125.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002126","title":"Change the definition of Application Descriptor","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change the definition of Application Descriptor. Delete the description on OSid and OSappid.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10860,"status":"noted","reservation_date":"2020-02-18 07:57:47","uploaded":"2020-02-18 15:16:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":418.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002126.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002129","title":"Replace the reference to 23.203 to the clause in 23.503 in 4.3.6","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 4.3.6 to include content defined in clause 4.7 of TS 23.203. A new subclause is added for the non-session management related service capability exposure scenarios.","secretary_remarks":"Revision of agreed S2-2001197 from S2#136AH. Merged into S2-2002432","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10960,"status":"merged","reservation_date":"2020-02-18 07:57:50","uploaded":"2020-02-18 14:40:46","revisionof":"S2-2001197","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":400.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002129.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002130","title":"Replace the reference to 23.203 to the clause in 23.503 in 6.2.3","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 6.2.3 to include content defined in clause 6.2.3 of TS 23.203.","secretary_remarks":"Revision of agreed S2-2001572 from S2#136AH. Revised to S2-2002433.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10970,"status":"revised","reservation_date":"2020-02-18 07:57:51","uploaded":"2020-02-18 14:40:46","revisionof":"S2-2001572","revisedto":"S2-2002433","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":401.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002130.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002131","title":"Corrections for event reporting from the PCF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The missing statements are added to clause 6.1.3.18 Event reporting from the PCF. The missing event Resource allocation outcome is added, too. Furthermore, details about the event reporting from the PCF are removed from clauses 6.1.3.5 and 6.1.3.6 as they are documented in clause 6.1.3.18. The table is removed from Annex C as the events relevant for Rx are already documented in the table in clause 6.1.3.18.","secretary_remarks":"Revised to S2-2002435.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11050,"status":"revised","reservation_date":"2020-02-18 07:57:52","uploaded":"2020-02-18 14:40:46","revisionof":"","revisedto":"S2-2002435","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":419.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002131.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002185","title":"Correction on Application Descriptor in ATSSS rule","source":"Huawei, Hisilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete the Application Descriptor in ATSSS Rule.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10870,"status":"noted","reservation_date":"2020-02-18 10:00:29","uploaded":"2020-02-18 15:16:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"},{"winame":"ATSSS"}],"crnumber":2193.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002185.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002186","title":"Change the definition of Application Descriptor","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delete the description on OSid and OSappid.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10880,"status":"noted","reservation_date":"2020-02-18 10:00:32","uploaded":"2020-02-18 15:16:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2141.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002186.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002282","title":"Selecting the same PCF for AMF and an SMF in interworking scenarios","source":"Ericsson?, China Telecom?, Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a NOTE for PCF selection to allow selecting the same PCF in a [S-NSSAI, DNN] for the AMF and for a SMF based on SUPI range.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11120,"status":"noted","reservation_date":"2020-02-18 16:27:51","uploaded":"2020-02-18 17:47:24","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2215.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002282.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002303","title":"Support of OSID and OSAppID as traffic descriptors based on stage 3 agreements.","source":"Motorola Mobility, Lenovo","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"discussion","for":"Endorsement","abstract":"","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10830,"status":"noted","reservation_date":"2020-02-18 20:47:56","uploaded":"2020-02-18 20:59:32","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002303.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002431","title":"Clarification on support of UE policies by the UE","source":"Motorola Mobility, Lenovo, Ericsson","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The change alligns with the decision made in CT WG1 (3GPP TS 24.501) where it is clarified that provisioning of URSP rules and the UE Policy Delivery procedure by the PCF are mandatory supported at the UE. No additional work is needed in stage 3","secretary_remarks":"Revision R01 of S2-2001868. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10930,"status":"agreed","reservation_date":"2020-02-28 13:23:11","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2001868","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":397.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-200080","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002431.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002432","title":"Replace the reference to 23.203 to the clause in 23.503 in 4.3.6","source":"Ericsson, Huawei, HiSilicon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 4.3.6 to include content defined in clause 4.7 of TS 23.203. Changes in rev.3: New subclause to define requirements for network capability exposure of non session management policy control functionality. Include or extend the references for requirements for network capability exposure of (non-) session management policy control functionality. Extend UE Policy requirements to include V2X Policies.","secretary_remarks":"Revision R03 of S2-2001930, merging S2-2002129. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10950,"status":"agreed","reservation_date":"2020-02-28 13:23:12","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2001930","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":400.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-200080","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002432.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002433","title":"Replace the reference to 23.203 to the clause in 23.503 in 6.2.3","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 6.2.3 to include content defined in clause 6.2.3 of TS 23.203.","secretary_remarks":"Revision R04 of S2-2002130. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":10980,"status":"agreed","reservation_date":"2020-02-28 13:23:13","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2002130","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":401.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-200080","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002433.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002434","title":"Correction on QoS Flow Binding for QoS Flow Behaviour","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the following aspects which are unclear\/missing: - Correct reference to 23.501 for the establishment as well as modification of QoS Flow. - A modification of the same binding parameters in all PCC rules that are bound to the same QoS Flow should result in a QoS Flow modification but not in a re-evaluation of the binding of the PCC rules (as otherwise, a new QoS Flow would be established and the existing one removed) - If the last PCC rule that is bound to a QoS Flow is removed, the SMF shall delete the QoS Flow. - When a QoS Flow is removed, the SMF shall remove the PCC rules bound to this QoS Flow and report them to the PCF","secretary_remarks":"Revision R03 of S2-2002123. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11040,"status":"agreed","reservation_date":"2020-02-28 13:23:14","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2002123","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":417.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200080","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002434.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002435","title":"Corrections for event reporting from the PCF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The missing statements are added to clause 6.1.3.18 Event reporting from the PCF. The missing event Resource allocation outcome is added, too. Furthermore, details about the event reporting from the PCF are removed from clause 6.1.3.6 as they are documented in clause 6.1.3.18.","secretary_remarks":"Revision R02 of S2-2002131. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11060,"status":"agreed","reservation_date":"2020-02-28 13:23:15","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2002131","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":419.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200080","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002435.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002436","title":"AFsessionWithQoS update","source":"vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce the AFsessionWithQoS_Update procedure based on last meeting comments.","secretary_remarks":"Revision R02 of S2-2002071. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11080,"status":"agreed","reservation_date":"2020-02-28 13:23:16","uploaded":"2020-02-29 09:46:33","revisionof":"S2-2002071","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.3.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2122.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200079","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_137e_Electronic\/Docs\/S2-2002436.zip","group":"S2","meeting":"S2-ah-37776","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]