[{"name":"S2-2002609","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-2001778 from S2#137E. Postponed","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11190,"status":"postponed","reservation_date":"2020-03-26 10:57:36","uploaded":"2020-03-27 13:44:13","revisionof":"S2-2001778","revisedto":"S2-2003515","release":"","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_138e_Electronic\/Docs\/S2-2002609.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002663","title":"LS from SA WG5: LS reply on Reply LS on supporting simultaneous online and offline reporting level access","source":"SA WG5","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 thanks SA WG2 for the LS 'Reply LS on supporting simultaneous online and offline reporting level'. SA WG5 would like to address the following questions from SA WG2: SA WG2 Question 1: SA WG2 would request SA WG5 to confirm that simultaneous online and offline charging for a given PCC rule is supported in 5GS for a given PCC rule. SA WG5 answer: Even though within 5G Data Connectivity charging, simultaneous handling of distinct 'online service data flows' and 'offline service data flows' for a given PDU session is supported by the 5GS Convergent Charging service, it is not appropriate for a given service data flow to be set with both 'online' and 'offline' PCC Rule charging methods. The PCC Rule charging method value shall be used to determine whether quota supervision is needed (i.e. online), or not (i.e. offline) for a service data flow. In 5GS context the 'online' behavior could be seen as a superset of the 'offline' behavior as it implicitly includes the usage reporting. SA WG2 Question 2: SA WG2 requests SA WG5 to confirm if a single reporting level in PCC rule is sufficient for generation of usage reports to satisfy the usage reporting requirements for online and offline usage reporting. SA WG5 answer: Since the behavior for 'online' charging method implicitly includes the usage reporting, as indicated in SA WG5 answer to SA WG2 question 1, the single reporting level is sufficient. SA WG5 would like to also confirm that for usage reporting, as supported by 5GS Convergent Charging service, a given service data flow usage only needs to be reported once. Action: SA WG5 kindly asks SA WG2 to take into account the answer above.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11200,"status":"noted","reservation_date":"2020-03-26 10:57:38","uploaded":"2020-03-27 15:57:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"S5-201457","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002663.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002726","title":"Reallocation of credit reporting to the AF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add 'Reallocation of credit' to the list of Events relevant for the AF.","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003299.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11210,"status":"revised","reservation_date":"2020-04-07 20:33:31","uploaded":"2020-04-10 19:29:05","revisionof":"","revisedto":"S2-2003299","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":434.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002726.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002731","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":"Revision of (postponed) S2-2001932 from S2#137E. Postponed","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11230,"status":"postponed","reservation_date":"2020-04-07 20:33:44","uploaded":"2020-04-10 19:29:05","revisionof":"S2-2001932","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":409.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002731.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002752","title":"Completion of description in general PCF clause","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The missing important statements about the PCF functionality are added. Subclauses are added and the detailed description related to usage monitoring and sponsored data connectivity is moved into separate new clauses. Furthermore, the PCF actions for usage monitoring are corrected with respect to the total and the remaining allowed usage.","secretary_remarks":"Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11240,"status":"agreed","reservation_date":"2020-04-08 15:48:46","uploaded":"2020-04-10 11:40:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":438.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200552","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002752.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002753","title":"Corrections for AF Session with QoS procedure","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Both procedures are corrected by moving the notification about the outcome of the establishment\/notification of the transmission resources corresponding to the QoS to later steps. The AF session with required QoS update procedure is updated by adding a description for the optional parameters period of time or a traffic volume. In both procedures, small clarifications for the Alternative Service Requirements were added.","secretary_remarks":"Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11250,"status":"agreed","reservation_date":"2020-04-08 15:48:47","uploaded":"2020-04-10 11:40:19","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":2186.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200552","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002753.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002794","title":"Clarification on Access Type Preferrence in RSD of URSP rule","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Multi-Access for the Access Type Preference in the RSD description.","secretary_remarks":"e-meeting r02 agreed. Revised to S2-2003300.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11260,"status":"revised","reservation_date":"2020-04-09 04:02:33","uploaded":"2020-04-10 06:44:57","revisionof":"","revisedto":"S2-2003300","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":442.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002794.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002795","title":"Correct the wrong placement of UE-AMBR","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Move the UE-AMBR out of the RFSP Index in table 6.5-1","secretary_remarks":"Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11280,"status":"agreed","reservation_date":"2020-04-09 04:02:34","uploaded":"2020-04-10 06:44:57","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":443.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002795.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002801","title":"Correction on the QoS Flow binding with Alternative QoS Parameter Set(s)","source":"OPPO","contact":"Yali Guo","contact-id":85844,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: GBR and MBR in the Alternative QoS Parameter Set are not used as binding parameters for QoS Flow binding Clarify if the Alternative QoS Parameter Set doesn't include 5QI, the QoS Flow binding will not consider the Alternative QoS Parameter Set. Clarify If the Alternative QoS Parameter Set includes 5QI, the prioritized order of the Alternative QoS Parameter Set in the PCC rule should also be considered as the binding parameter.","secretary_remarks":"Postponed","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11330,"status":"postponed","reservation_date":"2020-04-09 06:31:43","uploaded":"2020-04-10 06:25:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"eV2XARC"}],"crnumber":445.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002801.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002920","title":"The clarification for PDU session establishment based on URSP rule","source":"OPPO","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updating TS23.503 for URSP evaluation using different RSDs.","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003301.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11290,"status":"revised","reservation_date":"2020-04-10 04:30:06","uploaded":"2020-04-10 12:39:15","revisionof":"","revisedto":"S2-2003301","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":447.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002920.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002939","title":"Correction on QoS Flow Binding for CN PDB","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: CN PDB has to be considered during QoS Flow Binding. The SMF shall ensure that PCC rules with the same above binding parameters but different PDU Session anchors are not bound to the same QoS Flow. Add a NOTE for the relationship between DNAI and PSA UPF, which will also clarify how CN PDB is relevant with a PCC rule.","secretary_remarks":"Revision of (postponed) S2-2002122 from S2#137E. e-meeting r03 agreed. Revised to S2-2003302.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11310,"status":"revised","reservation_date":"2020-04-10 06:35:31","uploaded":"2020-04-10 11:29:19","revisionof":"S2-2002122","revisedto":"S2-2003302","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":416.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002939.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2002940","title":"Correction on QoS Flow Binding for general SMF behaviour and Alternative QoS Parameter Sets","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes and rewordings are proposed: Update of the SMF description on the binding of a PCC rule to an existing QoS Flow by clarifying that the recently added requirements as well as local policies may lead to a new QoS Flow establishment. Move the MA PDU Session and AQP related part to one single paragraph on the QoS Flow Binding principle. Remove AQP as a binding parameter and add a requirement that PCC rule with AQP needs to be bound to a separate QoS Flow to avoid the starvation.","secretary_remarks":"e-meeting r03 agreed. Revised to S2-2003303.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11340,"status":"revised","reservation_date":"2020-04-10 06:35:32","uploaded":"2020-04-10 11:29:19","revisionof":"","revisedto":"S2-2003303","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.0","workitem":[{"winame":"eV2XARC"}],"crnumber":449.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2002940.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003073","title":"Update to Reporting and Credit management","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 6.1.3.4 to align with credit management defined in TS 32.255 and refer to TS 32.255. Update 6.1.3.3 and Annex D to align with usage reporting defined in TS 32.255 and refer to TS 32.255.","secretary_remarks":"e-meeting r02 agreed. Revised to S2-2003304.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11360,"status":"revised","reservation_date":"2020-04-10 11:09:32","uploaded":"2020-04-10 17:48:07","revisionof":"","revisedto":"S2-2003304","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":459.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003073.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003108","title":"Correction on UE Policy Association Establishment procedure","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: UE Policy Association Establishment based on home PLMN's subscription","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11380,"status":"noted","reservation_date":"2020-04-10 12:45:22","uploaded":"2020-04-10 12:56:33","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.4.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":2286.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003108.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003152","title":"Update to align UE policy terminology","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove UE Policy in the title. Update the texts to restrict the scope to UE access selection and PDU Session selection related policy control.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11390,"status":"noted","reservation_date":"2020-04-10 16:03:33","uploaded":"2020-04-10 17:42:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":462.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003152.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003186","title":"Clarification on the of online charging and offline charging indication on N7 interface","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correction of PCC Rule table to show that online or offline charging (not both) or neither methods are set in a PCC rule on N7 interface.","secretary_remarks":"e-meeting r01 agreed. Revised to S2-2003305.","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11400,"status":"revised","reservation_date":"2020-04-10 19:30:54","uploaded":"2020-04-10 21:13:41","revisionof":"","revisedto":"S2-2003305","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":465.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003186.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003188","title":"Clarification of PCF behaviour to honor UE provided maximum packet filter support","source":"Apple","contact":"Krisztian Kiss","contact-id":57762,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PCF shall ensure that the sum of the packet filters used by all PCC rules which trigger the generation of signalled QoS rules does not exceed the number of supported packet filters for signalled QoS rules indicated by the UE for the PDU Session, if SMF has provided the UE's support to the PCF.","secretary_remarks":"Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11420,"status":"agreed","reservation_date":"2020-04-10 19:47:32","uploaded":"2020-04-10 21:24:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":466.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003188.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003189","title":"Clarification of UE behaviour when number of UE policies stored in the UE exceeds maximum value","source":"Apple","contact":"Krisztian Kiss","contact-id":57762,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the number of UE policies stored in the UE for any PLMN (including HPLMN) exceeds the maximum value allocated by UE for storage of UE policies, it is up to UE implementation on how to handle this.","secretary_remarks":"Noted","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11430,"status":"noted","reservation_date":"2020-04-10 19:55:39","uploaded":"2020-04-10 21:24:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"}],"crnumber":467.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003189.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003299","title":"Reallocation of credit reporting to the AF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add 'Reallocation of credit' to the list of Events relevant for the AF.","secretary_remarks":"Revision of S2-2002726. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11220,"status":"agreed","reservation_date":"2020-04-27 09:08:43","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002726","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":434.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003299.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003300","title":"Clarification on Access Type Preferrence in RSD of URSP rule","source":"Intel, Deutsche Telekom","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add Multi-Access for the Access Type Preference in the RSD description.","secretary_remarks":"Revision of S2-2002794. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11270,"status":"agreed","reservation_date":"2020-04-27 09:08:44","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002794","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.0","workitem":[{"winame":"ATSSS"}],"crnumber":442.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200428","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003300.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003301","title":"The clarification for PDU session establishment based on URSP rule","source":"OPPO","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updating TS23.503 for URSP evaluation using different RSDs","secretary_remarks":"Revision of S2-2002920. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11300,"status":"agreed","reservation_date":"2020-04-27 09:08:45","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002920","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":447.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003301.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003302","title":"Correction on QoS Flow Binding for CN PDB","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: CN PDB has to be considered during QoS Flow Binding. The SMF shall ensure that PCC rules with the same above binding parameters but different PDU Session anchors are not bound to the same QoS Flow. Add a NOTE for the relationship between DNAI and PSA UPF, which will also clarify how CN PDB is relevant with a PCC rule.","secretary_remarks":"Revision of S2-2002939. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11320,"status":"agreed","reservation_date":"2020-04-27 09:08:46","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002939","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":416.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-200425","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003302.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003303","title":"Correction on QoS Flow Binding for general SMF behaviour and Alternative QoS Parameter Sets","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes and rewordings are proposed: Update of the SMF description on the binding of a PCC rule to an existing QoS Flow by clarifying that the recently added requirements as well as local policies may lead to a new QoS Flow establishment. Move the MA PDU Session and AQP related part to one single paragraph on the QoS Flow Binding principle. Remove AQP as a binding parameter and add a requirement that PCC rule with AQP needs to be bound to a separate QoS Flow to avoid the starvation.","secretary_remarks":"Revision of S2-2002940. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11350,"status":"agreed","reservation_date":"2020-04-27 09:08:47","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2002940","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.0","workitem":[{"winame":"eV2XARC"}],"crnumber":449.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200434","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003303.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003304","title":"Update to Reporting and Credit management","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update 6.1.3.4 to align with credit management defined in TS 32.255 and refer to TS 32.255.","secretary_remarks":"Revision of S2-2003073. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11370,"status":"agreed","reservation_date":"2020-04-27 09:08:48","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003073","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":459.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200551","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003304.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2003305","title":"Clarification on the of online charging and offline charging indication on N7 interface","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correction of PCC Rule table to show that online or offline charging (not both) or neither methods are set in a PCC rule on N7 interface.","secretary_remarks":"Revision of S2-2003186. Approved","agenda_item_sort_order":17,"ainumber":"6.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":11410,"status":"agreed","reservation_date":"2020-04-27 09:08:49","uploaded":"2020-04-28 06:57:52","revisionof":"S2-2003186","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.4.1","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":465.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-200552","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_138e_Electronic\/Docs\/S2-2003305.zip","group":"S2","meeting":"S2-ah-35701","year":2020,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]