[{"name":"S2-180029","title":"LS from CT WG3: LS on Clarification on Npcf_SMPolicyControl service","source":"CT WG3","contact":"Fuencisla Garcia Azorero","contact-id":43873,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 has different interpretations of Npcf_SMPolicyControl service defined in TS 23.502 subclause 5.2.5.4 and different understandings of how it is used in the procedures and flows described for the policy framework in TS 23.502 subclause 4.16. Specifically, CT WG3 has identified the following potential options: - Option 1 The Npcf_SMPolicyControl_Get service operation can be invoked by the SMF after the PDU session establishment during the PDU session lifetime (e.g. at PDU session modification) to request policies from the PCF or to update PDU session information in the PCF, as the current Npcf_SMPolicyControl_Get service operation description allows, or - Option 2 Subsequent interactions from the SMF to the PCF to request policies or to update PDU session information in the PCF only take place by invoking Nsmf_EventExposure_Notify service operation, or - Option 1 in combination with Option 2 is also possible. Action: CT WG3 asks SA WG2 to kindly indicate which of the options above","secretary_remarks":"Response drafted in S2-180234. This LS was postponed. Revised at S2#126 in S2-181424.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14500,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181424","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"C3-176376","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180029.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180050","title":"LS from SA WG5: Reply to LS from CT WG4 to SA WG5 on Reply LS on 5G Charging Study Phase 1 on N4","source":"SA WG5","contact":"Robert T\u00f6rnkvist","contact-id":35172,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to inform that the study TR 32.899 on charging aspects of 5G system architecture phase 1 has now been completed, and will be sent for approval to the next plenary SA#78. The result of the study shows no new requirements compared to Sx. The current conclusion in the study has one solution using a subset of the current Sx.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14530,"status":"noted","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"SA WG2","lsoriginalls":"S5-176369","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180050.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180076","title":"23.503: BSF storing the selected PCF Address in UDR Structured data should be optional.","source":"Cisco Systems","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarifyed that storage of binding information in UDR should be optional for BSF.","secretary_remarks":"Merged into S2-181005","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15570,"status":"merged","reservation_date":"2018-01-11 09:02:48","uploaded":"2018-01-16 10:41:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"PCC"}],"crnumber":"","crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180076.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180078","title":"23.501: Moving Network Analytics functionality into 23.501","source":"Ericsson, KDDI, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding the network analytics architecture in clause 6.2.9 and moving NWDAF description into 23.501.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15970,"status":"not treated","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181643","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180078.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180079","title":"23.502: Moving Network Analytics functionality into 23.501","source":"Ericsson, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding the Analytics Type ID and Context ID and then define that in Rel-15 Analytics Type ID corresponds to Load Level and the Context ID corresponds to Network Slice Instance. Only one Analytics Type ID is defined. Defining one Nwdaf service that includes subscribe\/notify and request\/reponse.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15980,"status":"not treated","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181647","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180079.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180080","title":"23.503: Moving Network Analytics functionality into 23.501","source":"Ericsson, KDDI, AT&T","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Moving NWDAF to 23.501. Include NWDAF in the LBO architecture. Define the feature for policy control using analytics.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15990,"status":"not treated","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-181646","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180080.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180081","title":"23.501: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update clause 5.22 to indicate that the service layer can provide instructions on how to perform pre-emption of media flows when no resources are available.","secretary_remarks":"Revised in parallel session to S2-180995.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15420,"status":"revised","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-180995","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180081.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180082","title":"23.503: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: PCF functional description of resource reservation for service sharing priority is updated to align with the functional description of this feature in TS 23.203.","secretary_remarks":"Revised in parallel session to S2-180996.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15440,"status":"revised","reservation_date":"2018-01-11 15:47:34","uploaded":"2018-01-16 13:18:57","revisionof":"","revisedto":"S2-180996","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180082.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180112","title":"23.503: Correction for background data transfer","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Change to Npcf_BDTPolicyControl_Get","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15710,"status":"not treated","reservation_date":"2018-01-11 17:18:37","uploaded":"2018-01-16 13:08:52","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180112.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180129","title":"23.503: Description of components in URSP","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Filling the description of the components. 2. Multiple Route Selection Descriptors in one URSP rule.  3. Non-Seamless Offload indication doesn't coexist with other component.","secretary_remarks":"Revised in parallel session, merging S2-180404, to S2-180966.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14610,"status":"revised","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"S2-180966","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180129.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180130","title":"23.503: Additional PDU Session Type in Route Selection Descriptor","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the PDU Type as a component in the URSP rule.","secretary_remarks":"Revised in parallel session to S2-180967.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14640,"status":"revised","reservation_date":"2018-01-12 09:24:48","uploaded":"2018-01-16 11:38:48","revisionof":"","revisedto":"S2-180967","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180130.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180132","title":"23.503: Remove EN related with Session binding","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 6.1.3.2.2: Session Binding applies only for PDU Sessions of IP type 2. \u00a7 6.1.1.2: remove the EN and add that S-NSSAI is part of the data used for session binding 3. Clarifications and Editorials:.","secretary_remarks":"Revised in parallel session, merging S2-180076, to S2-181005.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15630,"status":"revised","reservation_date":"2018-01-12 09:35:56","uploaded":"2018-01-16 09:24:47","revisionof":"","revisedto":"S2-181005","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180132.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180133","title":"23.502: Npcf_Policy Authorization Create Service Definition Correction","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the description of the Npcf_PolicyAuthorization_Create service operation to include  a list of information elements in the optional output section","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15920,"status":"not treated","reservation_date":"2018-01-12 10:48:41","uploaded":"2018-01-16 10:50:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180133.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180134","title":"23.502: Npcf_Policy Authorization Delete Service Definition Correction","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the description of the Npcf_PolicyAuthorization_Delete service operation to include a list of information elements in the optional output section.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15930,"status":"not treated","reservation_date":"2018-01-12 10:52:21","uploaded":"2018-01-16 10:50:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180134.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180138","title":"23.501: Correction to Providing AF request to multiple PCFs","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This paper makes clarificaiton and correction in clauses 5.6.7 and 6.3.7.2 so that the solution in 6.3.7.2 is applicable to AF requests that target non-specific PDU Sessions of a single UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15740,"status":"not treated","reservation_date":"2018-01-12 16:24:15","uploaded":"2018-01-16 02:31:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180138.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180154","title":"23.501: Clarification on Area of Interest for Presence Area Reporting","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify how area of interest can be used for subscribing and getting notified of UE location change into or out of a Presence Reporting Area. The proposal is as follows 1. When PCF subscribes to SMF event notification, the PCF provides PRA ID(s) or a UE specific PRA list (e.g list of TAs). 2. SMF subscribes to AMF for UE location change event notification on area of interest by providing the PRA ID and\/or the list of TAs \/ cell IDs as the area of interest. 3. For core-network predefined PRA, the configuration of the PRA ID to list of TAs \/ cell IDs \/ NG-RAN node IDs is at the AMF. Use of priorities and overload control of PRA reporting by setting some low priority PRAs as inactive, is done at the AMF.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15870,"status":"postponed","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180154.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180156","title":"23.503: Resolve the Editor's Note on Presence Reporting Area","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Remove the Editor's Note on PRA and Area of Interest relation. 2. Add a clarification with reference to TS 23.502 \/ TS 23.501 on how area of interest is used in relation to PRA. 3. Normative text in NOTE2 is moved as normative paragraph. 4. Move the text related to event triggers from AMF to PCF that are not session related from clause 6.1.3.5 to clause 6.1.2.X","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15880,"status":"postponed","reservation_date":"2018-01-12 16:43:27","uploaded":"2018-01-16 11:30:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180156.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180166","title":"Discussion on optimization for PCF services","source":"Oracle Corporation, ZTE","contact":"Uri Baniel","contact-id":58644,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper evaluates the basic operation of the PCF services in conjunction with the SMF\/AMF event exposure related services. It identifies several key issues and proposes optimization for PCF services.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14830,"status":"noted","reservation_date":"2018-01-12 18:50:55","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180166.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180168","title":"23.502: Update of Npcf_SMPolicyControl service","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_SMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Nsmf_EventExposure Service! AMF, AF\/NEF and\/or any other consumer can still use this service as is, as long as the SMF simply notifies subscribers of events in a 'fire and forget' fashion. Update 23.502 Npcf_SMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the SMF:  - Update the optional input parameters of the Npcf_SMPolicyControl_Get service operation to provide event notification (in the case of SMF initiated modifications). - Update the optional output parameters of the Npcf_SMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_SMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180969.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14840,"status":"revised","reservation_date":"2018-01-12 19:08:52","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180969","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180168.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180170","title":"23.502: Update of Npcf_AMPolicyControl service","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_AMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Namf_EventExposure Service! SMF, AF\/NEF, UDM, GMLC and\/or any other consumer can still use this service as is, as long as the AMF simply notifies subscribers of events in a 'fire and forget' fashion.  Update 23.502 Npcf_AMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the AMF:  - Update the optional input parameters of the Npcf_AMPolicyControl_Get service operation to provide event notification (in the case of AMF initiated modifications). - Update the optional output parameters of the Npcf_AMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_AMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180970.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14870,"status":"revised","reservation_date":"2018-01-12 19:17:15","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180970","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180170.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180171","title":"23.502: Update of Session Management Policy Establishment procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Establishment procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service.doc'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. This can be done in step 5. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180971.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14900,"status":"revised","reservation_date":"2018-01-12 19:24:06","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180971","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180171.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180173","title":"23.502: Update of Session Management Policy Modification procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Modification procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. Specifically event notification from SMF to PCF can be done in step 1a by using the Npcf_SMPolicyControl_Get service operation. Step 2a may include subscription by the PCF to Event Triggers by using the response to the Npcf_SMPolicyControl_Get service operation. Similarly, Step 5 may include subscription by the PCF to Event Triggers by using the pcf_SMPolicyControl_UpdateNotify service operation.Consequently steps 7 and 8 are not needed, and so are removed from the procedure. On top of that it makes more sense now to split the procedure into two procedures: Session Management Policy Modifi","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180972.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14930,"status":"revised","reservation_date":"2018-01-12 19:31:50","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180972","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180173.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180174","title":"23.502: Update of Policy Association Establishment during Registration procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Establishment during Registration procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in step 3. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180973.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14960,"status":"revised","reservation_date":"2018-01-12 19:39:00","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180973","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180174.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180175","title":"23.502: Update of Policy Association Establishment during AMF relocation procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Establishment during AMF relocation procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in step 3. Consequently steps 5 and 6 are not needed, and so are removed from the procedure.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180974.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14980,"status":"revised","reservation_date":"2018-01-12 19:46:58","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180974","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180175.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180176","title":"23.502: Update of Policy Association Modification for Mobility Policy procedure","source":"Oracle, ZTE, Ericsson? ,Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Associationt Modification for Mobility Policy procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in steps 1(receive event notifications) and 2(subscribe to event notifications) respectively. Consequently steps 4 and 5 are not needed, and so are removed from the procedure. The policy decision is made right after step 1, and is denoted as step 2. Thus original step 2 is now step 3.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180975.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15000,"status":"revised","reservation_date":"2018-01-12 19:53:25","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180975","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180176.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180177","title":"23.502: Update of Policy Association Modification for UE Policy and Access and Mobility control procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Modification for UE Policy and Access and Mobility control procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. Consequently, the procedure is split up into two procedures: 1. Update of Policy Association Modification for UE Policy and Access and Mobility control procedure triggered by the AMF 2. Update of Policy Association Modification for UE Policy and Access and Mobility control procedure triggered by the PCF. As part of it section numbers and step numbers were adjusted.","secretary_remarks":"Confirm Sources! Revised in parallel session to S2-180976.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15020,"status":"revised","reservation_date":"2018-01-12 19:58:08","uploaded":"2018-01-15 21:08:31","revisionof":"","revisedto":"S2-180976","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180177.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180182","title":"23.502: Handling of AMF and PCF interaction when there is a PLMN change during AMF relocation.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the registration procedure to reflect that when there is AMF relocation and the new AMF is in a different PLMN, the old AMF does not transfer the PCF ID nor the AM policy information and the event triggers subscribed by the PCF. The old AMF terminates the policy association to the PCF.","secretary_remarks":"Revised in parallel session to S2-180990.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15270,"status":"revised","reservation_date":"2018-01-12 22:43:26","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180990","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180182.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180183","title":"23.502: Cleanup of NamfEventExposure and NsmfEventExposure services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Definition of a services, Namf_EventExposure and Nsmf_EventExposure are clarified.","secretary_remarks":"Revised in parallel session to S2-180992.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15330,"status":"revised","reservation_date":"2018-01-12 22:43:26","uploaded":"2018-01-16 13:18:58","revisionof":"","revisedto":"S2-180992","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180183.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180210","title":"23.502: Add Nocs_SpendingLimitControl service, service operations and information flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding OCS service and service operations to transfer subscriber spending limits from OCS to the NF consumer. Information flows are also added.","secretary_remarks":"Technically endorsed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15660,"status":"endorsed","reservation_date":"2018-01-13 16:42:57","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181627","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180210.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180211","title":"23.503: Add Nocs service in service base representation architecture","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Adding Nocs service in service base representation architecture of PCC framework for the 5GS.","secretary_remarks":"Technically endorsed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15670,"status":"endorsed","reservation_date":"2018-01-13 16:42:58","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-181635","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180211.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180222","title":"23.503: Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In clause 6.1.3.9, replace the reference specification from TS23.501 with TS23.502.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15940,"status":"not treated","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:38:49","revisionof":"","revisedto":"S2-181644","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180222.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180232","title":"23.502: Proposed resolution of Editor\u00b4s Notes in 23.502","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The proposal to resolve 1) above is to remove the Editor\u00b4s note. The reason is that the Access and Mobility related policy control the V-PCF generates the service area restrictions, those are not received from H-PCF as defined in clause 6.2.1.4 in TS 23.503.  The proposal to resolve 2) above is to remove the Editor\u00b4s note. The reason is that the functional description of the AF interactions described in 23.501 and 23.503 are either related to request for resources, prioritization of services, requires to steer to traffic to a DNAI(s), or request to charge traffic to the sponsor. These features require to provision PCC Rules to SMF.  The proposal to resolve 3) above is to extend the number of scenarios when the policy association termination procedure applies to include the notification of the removal of the policy profile from UDR. In addition, it is proposed to add a new procedure for (policy) session management termination when the UDR notifies the PCF that the pol","secretary_remarks":"Revised in parallel session to S2-181052.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15200,"status":"revised","reservation_date":"2018-01-14 18:59:39","uploaded":"2018-01-16 14:40:25","revisionof":"","revisedto":"S2-181052","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180232.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180234","title":"[DRAFT] LS reply on Clarification on Npcf_SMPolicyControl service","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3 LS proposing to select Option 1, i.e. use Npcf_SMPolicyControlGet to report modification of the association between the SMF and the PCF","secretary_remarks":"Response to S2-180029 Revised in parallel session to S2-180977.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14510,"status":"revised","reservation_date":"2018-01-14 18:59:39","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-180977","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180234.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180250","title":"23.502: Selecting a common PCF for UE and Session Policies","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Optionally, passing the selected PCF Id by AMF to SMF.","secretary_remarks":"Revised in parallel session to S2-180997.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15470,"status":"revised","reservation_date":"2018-01-15 04:12:49","uploaded":"2018-01-16 10:41:13","revisionof":"","revisedto":"S2-180997","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180250.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180253","title":"23.503: QoS rule generation","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify each QoS rule provided by SMF is generated from a PCC rule. The default QoS rule is generated by SMF based on the authorized default 5QI and ARP received from PCF, if a Packet Filter Set is included in the default QoS rule, the PCF may provide a default Packet Filter Set in the PDU Session related policy information to SMF. Clarify for a PDU session of unstructured type, no PCC Rule is provided to SMF. SMF generates the default QoS rule based on the authorized default 5QI and ARP received in the PDU Session related policy information.","secretary_remarks":"Revised in parallel session to S2-180994.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15390,"status":"revised","reservation_date":"2018-01-15 05:50:51","uploaded":"2018-01-16 11:52:46","revisionof":"","revisedto":"S2-180994","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180253.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180254","title":"23.502: Correction for event trigger report from SMF","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify the affected PCC rules and the QoS request for specific SDFs received from UE may be included in the Nsmf_EventExposure_Notify service","secretary_remarks":"Revised in parallel session to S2-181007.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15750,"status":"revised","reservation_date":"2018-01-15 05:54:06","uploaded":"2018-01-16 11:52:46","revisionof":"","revisedto":"S2-181007","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180254.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180269","title":"23.501: Add the description on the support of PRA","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: PRA is defined the same as in TS 23.401\/5.9.2.2, and the only difference is that PCF subscribes the event of PRA change from the AMF directly in the context of SBA.  It also clarifies that the area of interest and Presence Reporting Area are equivalent for AMF.  For acquiring AMF address if the AMF is not controlled by the PCF, it is proposed that the SMF stores the AMF address to the UDM during the PDU session establishment, and the PCF responsible for the PCC control of the UE PDU session fetches the AMF address from the UDM for the subscription of PRA change.   When the AMF is changed, the subscription of PRA change is transferred from the old AMF to the new AMF and the new AMF notifies the PCF with the current status related to the subscription of PRA change.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15850,"status":"postponed","reservation_date":"2018-01-15 08:36:04","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"S2-181796","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180269.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180274","title":"23.503: Clarification on the PRA support","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Removed the PRA change event triger from the SMF event table and removed description on management of PRA in the SMF for PCF subscribing the PRA change.  Clarified that PRA and area of interest are equivalent.  Added the description on how a PCF get the AMF address for subscribing event notification.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15860,"status":"postponed","reservation_date":"2018-01-15 08:49:12","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180274.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180275","title":"23.503: Update on the event subscription","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: All the event reporting are subject to NF consumer subscription. And the column 'Conditions for reporting' is removed.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15780,"status":"postponed","reservation_date":"2018-01-15 08:56:10","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180275.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180276","title":"23.503: Add content for Management of packet flow descriptions","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the content of PFD management requirments to 4.2.4","secretary_remarks":"Merged into S2-180989","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15260,"status":"merged","reservation_date":"2018-01-15 09:09:56","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180276.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180277","title":"23.503: Remove some ENs","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the above referred ENs.","secretary_remarks":"Revised in parallel session to S2-180988.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15220,"status":"revised","reservation_date":"2018-01-15 09:13:10","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"S2-180988","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180277.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180278","title":"23.501: Clarification on enforcement of Application Detection","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Description is added for Application Detection and Control.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15690,"status":"not treated","reservation_date":"2018-01-15 09:26:26","uploaded":"2018-01-16 13:10:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180278.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180279","title":"23.503: Clarification on enforcement of Application Detection Control","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Correction on description related to Application detection and control.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15700,"status":"not treated","reservation_date":"2018-01-15 09:26:26","uploaded":"2018-01-16 13:10:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180279.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180284","title":"23.503: Influence of additional non-standardized QoS parameters on QoS Flow Binding","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The additional AW\/MDBV added into PCC Rule information and considered during QoS Flow Binding.","secretary_remarks":"Revised in parallel session to S2-180993.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15360,"status":"revised","reservation_date":"2018-01-15 09:26:26","uploaded":"2018-01-16 13:10:38","revisionof":"","revisedto":"S2-180993","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180284.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180302","title":"Discussion on PCF","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"discussion","for":"Decision","abstract":"This paper shows the questions and issues about PCF. Based on the agreements about these issues, we need to agree the draft CRs.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15040,"status":"noted","reservation_date":"2018-01-15 10:45:24","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180302.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180303","title":"23.501: Clarification on PCF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Updating the PCF selection with the following proposals - The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF. - The SMF sends the PCF selected by the AMF to the SMF during the PDU session establishment procedure Fixing the typo in the clause 6.3.7.0","secretary_remarks":"Revised in parallel session to S2-180978.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15050,"status":"revised","reservation_date":"2018-01-15 10:45:24","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-180978","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180303.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180304","title":"23.502: Clarification on PCF association","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2.2.2-1: Registration, step 5: Removing 'PCF ID' because it is already included in UE context exchanged for inter-AMF mobility. Step 16: change 'PCF ID' into '(V-)PCF ID' - 4.16.1.2: Policy Association Establishment during Registration, step 2: proposal for the roaming case: The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF - 4.16.1.3: Policy Association Establishment during AMF relocation, step 2: proposal for the roaming case: The V-PCF receiving the PCF ID from old AMF shall include the H-PCF ID in the Npcf_AMPolicyControl Get operation. - 4.16.3.2: AMF-initiated Policy Association Termination, step 1: removing the unnecessary text based on the agreement at SA WG2#124. - 5.2.2.2.2: Table 5.2.2.2.2-1: UE Context in AMF - adding 'PCF ID' based on the agreement at SA WG2#124, and additionally 'H-PCF ID' based on the proposal on V\/H-PCF selection by AMF","secretary_remarks":"Revised in parallel session, merging S2-180644, to S2-180979.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15090,"status":"revised","reservation_date":"2018-01-15 10:45:24","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-180979","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180304.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180305","title":"23.503: Clarification PCF interaction","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2: general clarification - 5.3.3: general clarification - 5.3.4: clarification on unclear description about roaming options, LBO and HR. HR or LBO should be referring to a particular PDU session instead of per UE. \u00e8 Proposing two alternatives. One should be selected. - 6.1.2.1: removing the unnecessary text based on the agreement at SA WG2#124. - 6.1.2.2, 6.1.2.2.1: general clarification","secretary_remarks":"Revised in parallel session to S2-180980.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15120,"status":"revised","reservation_date":"2018-01-15 10:45:24","uploaded":"2018-01-16 10:46:05","revisionof":"","revisedto":"S2-180980","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180305.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180313","title":"23.503: Clean up for BSF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Revise all the PCF Binding Support Functionality to Binding Support Function. 2) Delete the S-NSSAI in the tuple of selected PCF discovery. 3) Delete the EN: 'Additional information needed by the network functionality, e.g. for network slicing, is FFS.'","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15550,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180313.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180314","title":"23.501: Clean up for BSF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add BSF description and service in TS 23.501. Delete the EN: 'Potential relation with slicing are FFS.'","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15560,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180314.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180315","title":"Discussion on Session Binding Mechanism for non-IP PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution proposes to discuss how to support Session Binding Mechanism for non-IP PDU Sessions.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15600,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180315.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180316","title":"23.503: Session Binding mechanism for non-IP PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The PCF uses the MAC address of the UE, the UE identity (e.g. SUPI), if present and DNN, if present to enforce the Session Binding. Add the access independent event trigger 'UE MAC address change' .","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15610,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180316.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180317","title":"23.501: Session Binding mechanism for non-IP PDU Session","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: To be able to provide traffic detection information to the UPF, the SMF shall request the detection of UE MAC address allocation\/deactivation and reporting from the UPF. The UPF shall store the MAC addresses, detected in the UL traffic received from the UE, and report those for the PDU Session. The UPF shall remove a UE MAC address when there is no corresponding UL traffic for a specified Inactivity period (provided by the SMF) and report the deactivation.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15620,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180317.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180318","title":"23.502: Clean up for PCC related flows","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) General description instead of parameters for PCF to SMF. 2) Add the exact clause. 3) Add correct service description.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15910,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180318.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180319","title":"23.502: UE Policy Delivery","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Store the UE Policy status in the UDR. Update the UDR services.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14800,"status":"noted","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180319.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180320","title":"23.503: UE Policy Delivery","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Store the UE Policy status in the UDR. There is no need to add a UE Policy ID.","secretary_remarks":"Revised in parallel session to S2-180926.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14810,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"S2-180926","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180320.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180321","title":"23.502: Correction on the Policy association procedure during AMF relocation","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Reclassified the Policy Association Establishment procedure into two cases: a) Policy Association Establishment procedure with new PCF (No UE context); b) Policy Association Establishment procedure with old PCF (Has UE context). 2. Update the existing description for the procedure that old PCF is used. 3. Update the description about the Policy Association Establishment procedure in registration.","secretary_remarks":"Revised in parallel session to S2-180991.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15290,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"S2-180991","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180321.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180322","title":"23.502: PCF selection for AMF during inter NG-RAN node N2 based handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: During the inter NG-RAN node N2 handover procedure, the S-AMF should provides the PCF ID to T-AMF for PCF selection.","secretary_remarks":"Revised in parallel session to S2-180998.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15500,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"S2-180998","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180322.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180323","title":"23.502: Correction on PCF selection in SMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add description about the AMF provide PCF information to SMF for PCF selection in PDU session management related procedures. 2. Correct the service name of step 3a and 5 in figure 4.3.2.2.1.","secretary_remarks":"Revised in parallel session to S2-180999.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15520,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:56","revisionof":"","revisedto":"S2-180999","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180323.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180324","title":"23.503: Removal of editor's notes and addition of references to empty sections","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to remove those editor's notes.  The following empty sections are proposed to be filled with a description or reference to a description in TS 23.203:  - 4.2.4 Management of packet flow descriptions,  - 6.1.3.16 3GPP PS Data Off,  - 6.2.4 Unified Data Repository,  - 6.2.7 Network Exposure Function.","secretary_remarks":"Revised in parallel session, merging S2-180276, to S2-180989.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15240,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:57","revisionof":"","revisedto":"S2-180989","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180324.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180325","title":"23.503: Update of event trigger section","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to clarify that the RAT Type is reported together with the Access Type if applicable, i.e. the Access Type supports one or more RAT Types. Further relevant description from 23.203 is proposed to be added into the event trigger section","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15770,"status":"not treated","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180325.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180357","title":"23.503: Clarification on AF using legacy Rx binding with relevant PCF","source":"China Mobile","contact":"Jiang Yi","contact-id":56358,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: New texts are added to clarify DRA is used to address and query BSF for relevant PCF, and to store binding information, for AFs using legacy Rx interface.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15590,"status":"noted","reservation_date":"2018-01-15 14:03:25","uploaded":"2018-01-16 13:05:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180357.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180370","title":"23.502: Mobility restrictions (service area) when roaming","source":"NEC","contact":"Sivasubramaniam Ramanan","contact-id":28064,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 4.16.1.2 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during Registration 4.16.1.3 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during AMF relocation 4.16.2.1 subclause title; minor correction 4.16.2.2; Npcf_AMPolicyControl_UpdateNotify in case of roaming scenario","secretary_remarks":"Revised in parallel session to S2-181039.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15820,"status":"revised","reservation_date":"2018-01-15 14:25:22","uploaded":"2018-01-16 10:59:04","revisionof":"","revisedto":"S2-181039","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180370.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180380","title":"Updating UE Route Selection Policy - DP","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"discussion","for":"Approval","abstract":"Discussion the proposals to further update URSP","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14540,"status":"noted","reservation_date":"2018-01-15 15:23:43","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180380.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180404","title":"23.503: Updating UE Route Selection Policy - CR","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - Updating the RSD table for URSP Rule structure to introduce the Index parameter and how to use it - Proposing to update URSP in Policy\/Rule\/RSD level - Describe how to prioritize the rule to use considering both precedence and rule id - Describing UE can try to establish PDU Session based on rejection cause","secretary_remarks":"Merged into S2-180966","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14550,"status":"merged","reservation_date":"2018-01-15 16:07:56","uploaded":"2018-01-16 10:16:02","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180404.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180408","title":"23.503: Corrections to description of session management related policy enforcement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1) Move description of non-session management related event triggesr from 6.1.3 to 6.1.2.  2) Remove duplicate definition\/reference of SDF filter and correct the description for Ethernet PDU Session type 3) Add a description of predefined vs dynamic PCC rules (in line with definitojn in 23.203)","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15790,"status":"not treated","reservation_date":"2018-01-15 17:00:05","uploaded":"2018-01-16 14:20:13","revisionof":"","revisedto":"S2-181645, S2-181935","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180408.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180419","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"Revised in parallel session, merging S2-180619 and S2-180564, to S2-180924.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14560,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180924","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180419.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180420","title":"23.502: UE assisted UE policies calculation in PCF","source":"Ericsson, NEC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The UE includes in the Initial Registration procedure a list of ruleIds identifying the UE Policy rules (WLANSP and URSP rules) stored in the UE. At initial registration the PCF calculates the UE policy rules that apply to the UE in the current conditions and compares this information with the one received from the UE to determine the UE policy rules that need to be downloaded to the UE (avoiding the sending of duplicated UE policy rules to the UE).","secretary_remarks":"Revised in parallel session, merging S2-180618 and S2-180566, to S2-180965.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14740,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 04:45:42","revisionof":"","revisedto":"S2-180965","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180420.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180434","title":"Discussion on PCC support of EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"discussion","for":"Discussion","abstract":"This paper evaluates the options on policy control for EPC IWK with the proposals.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15150,"status":"noted","reservation_date":"2018-01-15 19:19:33","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180434.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180435","title":"23.501: Clarification on PCC support of EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF unsubscribes the policy notification when UE doesn't camp on 5GS.  The combined PCF\/PCRF needs to provide PCC rule or policy information applied to EPC only in addition.  The combined SMF\/PGW-C performs the PCC rule or policy adaptation so that only the PCC rules or policy applied to either EPC or 5GC are enforced.","secretary_remarks":"Revised in parallel session to S2-180981.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15160,"status":"revised","reservation_date":"2018-01-15 19:24:08","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"S2-180981","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180435.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180436","title":"23.503: Remove EN related with EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Removes the EN in 6.1.3.5 2. Removes the EN in 6.3.1 and adds a NOTE to the removed attibutes for the clarification that they are provided for EPC IWK in Table 6.3.1 3. Adds 6.1.3.18 for the description on EPC IWK","secretary_remarks":"Revised in parallel session to S2-180982.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15180,"status":"revised","reservation_date":"2018-01-15 19:27:17","uploaded":"2018-01-16 14:36:00","revisionof":"","revisedto":"S2-180982","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180436.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180457","title":"23.503: Support for MCX Services in the PCC of 5G System","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution proposes new subclause '6.1.3.xx Mission Critical Services support' to describe the support for MCX Services in the PCC of 5G System.","secretary_remarks":"Should be a DRAFTCR Revised in parallel session to S2-180927.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15890,"status":"revised","reservation_date":"2018-01-15 22:12:47","uploaded":"2018-01-15 22:31:34","revisionof":"","revisedto":"S2-180927","release":"Rel-15","crspec":23.503,"crspecversion":"1.0.0","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_125_Gothenburg\/Docs\/S2-180457.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180469","title":"23.502: UE polices ack from UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following solution is proposed:  - - The UE sends back to the AMF a NAS message acknowledging the reception and storage of the UE policies.  - - In addition, to cover those error cases where the UE receives the NAS message from the AMF but has some error in the storing of the UE policies information, the UE may include in the ACK message with additional information about the error. If this optional IE is present in the ACK message, the AMF will send this error to the PCF (stage 3 will decide the message) and this will handle the error, e.g. updating UE context in the PCF accordingly and reattempting the sending of UE policies later on.","secretary_remarks":"Revised in parallel session to S2-180925.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14760,"status":"revised","reservation_date":"2018-01-15 23:43:16","uploaded":"2018-01-16 14:52:43","revisionof":"","revisedto":"S2-180925","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180469.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180475","title":"UE providing assistance information to PCF for UE Policy decision & delivery","source":"Motorola Mobility, Lenovo","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"discussion","for":"Approval","abstract":"Addresses the open point from SA WG2#124 on UE Policy provisioning. Namely, UE providing information to assist the PCF to determine whether a UE requires updated UE Policies.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14680,"status":"noted","reservation_date":"2018-01-15 23:53:49","uploaded":"2018-01-16 10:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180475.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180563","title":"Handling of Policy synchronization between UE and PCF using policy ID","source":"Qualcomm Inc","contact":"Miguel Griot","contact-id":57486,"tdoctype":"discussion","for":"Approval","abstract":"This paper proposes a way forward for policy sync between UE and PCF using policy ID.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14710,"status":"noted","reservation_date":"2018-01-16 06:19:50","uploaded":"2018-01-16 06:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180563.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180564","title":"23.503: Policy ID definition and handling proposal to split UE policies in sections","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduce Policy ID = Policy Section ID + Sectoin Version ID Describe the handling of policy sections and partial modification of policies in the PCF and UE.","secretary_remarks":"Merged into S2-180924.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14720,"status":"merged","reservation_date":"2018-01-16 06:24:06","uploaded":"2018-01-16 06:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180564.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180566","title":"23.502: Including uplink aspects of UE policy signalling between UE and PCF","source":"Qualcomm Incorporated","contact":"Miguel Griot","contact-id":57486,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introduce UE uplink policy signalling requesting UE policy synchrnizatoin from UE transparently transported over NAS, and from AMF to PCF.","secretary_remarks":"Merged into S2-180965.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14730,"status":"merged","reservation_date":"2018-01-16 06:27:30","uploaded":"2018-01-16 06:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180566.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180617","title":"23.502: Clarification on Network data analytics procedure","source":"China Mobile","contact":"Aihua Li","contact-id":58162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the Nnwdaf_Analytics_Info_Response service","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":16000,"status":"not treated","reservation_date":"2018-01-16 08:12:07","uploaded":"2018-01-16 12:07:10","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180617.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180618","title":"23.502: UE providing assistance information for UE Policy decision and delivery","source":"Motorola Mobility, Lenovo","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: UE includes in initial registration request the version ID of the UE Policies installed. The version ID is sent transparently by the AMF to the PCF using the Policy association establishment procedure. The PCF decides, based on feedback from the UDR, if the policies installed at the UE, are still applicable. If new Policies are required, the PCF and\/or V-PCF in the roaming case, provides new policies by using the UE Policy Delivery mechanism. The new policies include a new version ID for new ANDSP and\/or a new version ID for new URSP policies.","secretary_remarks":"Merged into S2-180965.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14690,"status":"merged","reservation_date":"2018-01-16 08:14:03","uploaded":"2018-01-16 10:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180618.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180619","title":"23.503: UE providing assistance information for UE Policy decision & delivery","source":"Motorola Mobility, Lenovo","contact":"Dimitrios Karampatsis","contact-id":70692,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: UE includes in initial registration request the version ID of the UE Policies installed. The version ID is sent transparently by the AMF to the PCF using the Policy association establishment procedure. The PCF decides, based on feedback from the UDR, if the policies installed at the UE, are is still applicable. If new Policies are required, the PCF and\/or V-PCF in the roaming case, provides new policies by using the UE Policy Delivery mechanism. The new policies include a new version ID for new ANDSP and new version ID for new URSP policies.","secretary_remarks":"Merged into S2-180924.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14700,"status":"merged","reservation_date":"2018-01-16 08:19:47","uploaded":"2018-01-16 10:35:00","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180619.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180634","title":"23.502: Correction of Npcf_BDTPolicyControl (background data transfer)","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Added the Background Data Transfer policy reference ID and the description for step 9","secretary_remarks":"Revised in parallel session to S2-181008.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15720,"status":"revised","reservation_date":"2018-01-16 08:48:01","uploaded":"2018-01-16 13:16:34","revisionof":"","revisedto":"S2-181008","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180634.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180654","title":"23.503: 503 NSSP clarification","source":"Samsung","contact":"Hoyeon Lee","contact-id":62489,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Proposed to clarify that NSSP is an association of the matching applications and Subscribed S-NSSAIs","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14670,"status":"not treated","reservation_date":"2018-01-16 09:07:57","uploaded":"2018-01-16 11:09:06","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180654.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180656","title":"23.502: Update to BSF operations","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. . \u00a7: add that S-NSSAI is part of the data used for session binding 2. Clarifications and Editorials:.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15580,"status":"postponed","reservation_date":"2018-01-16 09:18:02","uploaded":"2018-01-16 09:24:47","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180656.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180672","title":"Discussion - Clarify policy update from PCF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discuss the issue of session management policy modification procedure.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15800,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"","crspec":23.502,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180672.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180673","title":"23.502: Clarify policy update procedures","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: (1) Make alignments between clause 4.3.5.4 to 4.3.5.7 and clause 4.16.5. This part is hightlighted in green color. (2) Clarify the PCF behaviour in clause 4.16.5. This part is highlighted in blue color. (3) Correct wrong references in clause 5.2.5.4 and 5.2.8.3","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15810,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180673.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180674","title":"23.503: Add LADN indicator to DNN selection policy","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add an indicator in DNN selection policy to indicate a DNN is a LADN DNN.","secretary_remarks":"Not Handled","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14660,"status":"not treated","reservation_date":"2018-01-16 09:26:48","uploaded":"2018-01-16 12:25:28","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180674.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180757","title":"23.502: Correction of UDR usage in policy related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that PCF invoke UDR services are clarified in policy related procedures.","secretary_remarks":"Revised in parallel session to S2-181009.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15950,"status":"revised","reservation_date":"2018-01-16 14:28:10","uploaded":"2018-01-16 15:29:38","revisionof":"","revisedto":"S2-181009","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180757.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180924","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC, Lenovo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"Revision of S2-180419, merging S2-180619 and S2-180564. Revised in parallel session, merging S2-180926, to S2-181040.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14570,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180419","revisedto":"S2-181040","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180924.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180925","title":"23.502: UE polices ack from UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following solution is proposed:  - - The UE sends back to the AMF a NAS message acknowledging the reception and storage of the UE policies.  - - In addition, to cover those error cases where the UE receives the NAS message from the AMF but has some error in the storing of the UE policies information, the UE may include in the ACK message with additional information about the error. If this optional IE is present in the ACK message, the AMF will send this error to the PCF (stage 3 will decide the message) and this will handle the error, e.g. updating UE context in the PCF accordingly and reattempting the sending of UE policies later on.","secretary_remarks":"Revision of S2-180469. Revised in parallel session to S2-180968.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14770,"status":"revised","reservation_date":"2018-01-23 13:27:50","uploaded":"2018-01-26 18:07:52","revisionof":"S2-180469","revisedto":"S2-180968","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180925.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180926","title":"23.503: UE Policy Delivery","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Store the UE Policy status in the UDR. There is no need to add a UE Policy ID.","secretary_remarks":"Revision of S2-180320. Merged into S2-181040. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14820,"status":"withdrawn","reservation_date":"2018-01-23 13:27:51","uploaded":null,"revisionof":"S2-180320","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180927","title":"23.503: Support for MCX Services in the PCC of 5G System","source":"FirstNet, AT&T, Motorola Solutions, Airwave","contact":"Ihab Guirguis","contact-id":65302,"tdoctype":"draftCR","for":"Approval","abstract":"This contribution proposes new subclause '6.1.3.xx Mission Critical Services support' to describe the support for MCX Services in the PCC of 5G System.","secretary_remarks":"Revision of S2-180457. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15900,"status":"approved","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180457","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180927.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180965","title":"23.502: UE assisted UE policies calculation in PCF","source":"Ericsson, NEC","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The UE includes in the Initial Registration procedure a list of ruleIds identifying the UE Policy rules (WLANSP and URSP rules) stored in the UE. At initial registration the PCF calculates the UE policy rules that apply to the UE in the current conditions and compares this information with the one received from the UE to determine the UE policy rules that need to be downloaded to the UE (avoiding the sending of duplicated UE policy rules to the UE).","secretary_remarks":"Revision of S2-180420, merging S2-180618 and S2-180566. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14750,"status":"approved","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180420","revisedto":"S2-181888","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180965.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180966","title":"23.503: Description of components in URSP","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Filling the description of the components. 2. Multiple Route Selection Descriptors in one URSP rule.  3. Non-Seamless Offload indication doesn't coexist with other component.","secretary_remarks":"Revision of S2-180129, merging S2-180404. Revised in parallel session to S2-181041.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14620,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180129","revisedto":"S2-181041","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180966.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180967","title":"23.503: Additional PDU Session Type in Route Selection Descriptor","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the PDU Type as a component in the URSP rule.","secretary_remarks":"Revision of S2-180130. Postponed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14650,"status":"postponed","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180130","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180967.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180968","title":"23.502: UE polices ack from UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following solution is proposed:  - - The UE sends back to the AMF a NAS message acknowledging the reception and storage of the UE policies.  - - In addition, to cover those error cases where the UE receives the NAS message from the AMF but has some error in the storing of the UE policies information, the UE may include in the ACK message with additional information about the error. If this optional IE is present in the ACK message, the AMF will send this error to the PCF (stage 3 will decide the message) and this will handle the error, e.g. updating UE context in the PCF accordingly and reattempting the sending of UE policies later on.","secretary_remarks":"Revision of S2-180925. Revised in parallel session to S2-181042.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14780,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180925","revisedto":"S2-181042","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180968.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180969","title":"23.502: Update of Npcf_SMPolicyControl service","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_SMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Nsmf_EventExposure Service! AMF, AF\/NEF and\/or any other consumer can still use this service as is, as long as the SMF simply notifies subscribers of events in a 'fire and forget' fashion. Update 23.502 Npcf_SMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the SMF:  - Update the optional input parameters of the Npcf_SMPolicyControl_Get service operation to provide event notification (in the case of SMF initiated modifications). - Update the optional output parameters of the Npcf_SMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_SMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Revision of S2-180168. Revised in parallel session to S2-181010.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14850,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180168","revisedto":"S2-181010","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180969.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180970","title":"23.502: Update of Npcf_AMPolicyControl service","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_AMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Namf_EventExposure Service! SMF, AF\/NEF, UDM, GMLC and\/or any other consumer can still use this service as is, as long as the AMF simply notifies subscribers of events in a 'fire and forget' fashion.  Update 23.502 Npcf_AMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the AMF:  - Update the optional input parameters of the Npcf_AMPolicyControl_Get service operation to provide event notification (in the case of AMF initiated modifications). - Update the optional output parameters of the Npcf_AMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_AMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Revision of S2-180170. Revised in parallel session to S2-181011.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14880,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180170","revisedto":"S2-181011","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180970.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180971","title":"23.502: Update of Session Management Policy Establishment procedure","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Establishment procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service.doc'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. This can be done in step 5. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Revision of S2-180171. Revised in parallel session to S2-181012.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14910,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180171","revisedto":"S2-181012","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180971.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180972","title":"23.502: Update of Session Management Policy Modification procedure","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Modification procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. Specifically event notification from SMF to PCF can be done in step 1a by using the Npcf_SMPolicyControl_Get service operation. Step 2a may include subscription by the PCF to Event Triggers by using the response to the Npcf_SMPolicyControl_Get service operation. Similarly, Step 5 may include subscription by the PCF to Event Triggers by using the pcf_SMPolicyControl_UpdateNotify service operation.Consequently steps 7 and 8 are not needed, and so are removed from the procedure. On top of that it makes more sense now to split the procedure into two procedures: Session Management Policy Modifi","secretary_remarks":"Revision of S2-180173. Revised in parallel session to S2-181013.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14940,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180173","revisedto":"S2-181013","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180972.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180973","title":"23.502: Update of Policy Association Establishment during Registration procedure","source":"SA WG2","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Establishment during Registration procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in step 3. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Revision of S2-180174. Postponed in parallel session.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14970,"status":"postponed","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180174","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180973.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180974","title":"23.502: Update of Policy Association Establishment during AMF relocation procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Establishment during AMF relocation procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in step 3. Consequently steps 5 and 6 are not needed, and so are removed from the procedure.","secretary_remarks":"Revision of S2-180175. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14990,"status":"withdrawn","reservation_date":"2018-01-24 10:28:33","uploaded":null,"revisionof":"S2-180175","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180975","title":"23.502: Update of Policy Association Modification for Mobility Policy procedure","source":"Oracle, ZTE, Ericsson? ,Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Associationt Modification for Mobility Policy procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. This can be done in steps 1(receive event notifications) and 2(subscribe to event notifications) respectively. Consequently steps 4 and 5 are not needed, and so are removed from the procedure. The policy decision is made right after step 1, and is denoted as step 2. Thus original step 2 is now step 3.","secretary_remarks":"Revision of S2-180176. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15010,"status":"withdrawn","reservation_date":"2018-01-24 10:28:33","uploaded":null,"revisionof":"S2-180176","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180976","title":"23.502: Update of Policy Association Modification for UE Policy and Access and Mobility control procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Policy Association Modification for UE Policy and Access and Mobility control procedure based on the Npcf_AMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_AMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the AMF by using the Npcf_AMPolicyControl service. Consequently, the procedure is split up into two procedures: 1. Update of Policy Association Modification for UE Policy and Access and Mobility control procedure triggered by the AMF 2. Update of Policy Association Modification for UE Policy and Access and Mobility control procedure triggered by the PCF. As part of it section numbers and step numbers were adjusted.","secretary_remarks":"Revision of S2-180177. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15030,"status":"withdrawn","reservation_date":"2018-01-24 10:28:33","uploaded":null,"revisionof":"S2-180177","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180977","title":"[DRAFT] LS reply on Clarification on Npcf_SMPolicyControl service","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply to CT WG3 LS proposing to select Option 1, i.e. use Npcf_SMPolicyControlGet to report modification of the association between the SMF and the PCF","secretary_remarks":"Revision of S2-180234. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14520,"status":"withdrawn","reservation_date":"2018-01-24 10:28:33","uploaded":null,"revisionof":"S2-180234","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180978","title":"23.501: Clarification on PCF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Updating the PCF selection with the following proposals - The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF. - The SMF sends the PCF selected by the AMF to the SMF during the PDU session establishment procedure Fixing the typo in the clause 6.3.7.0","secretary_remarks":"Revision of S2-180303. Revised in parallel session to S2-181043.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15060,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180303","revisedto":"S2-181043","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180978.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180979","title":"23.502: Clarification on PCF association","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2.2.2-1: Registration, step 5: Removing 'PCF ID' because it is already included in UE context exchanged for inter-AMF mobility. Step 16: change 'PCF ID' into '(V-)PCF ID' - 4.16.1.2: Policy Association Establishment during Registration, step 2: proposal for the roaming case: The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF - 4.16.1.3: Policy Association Establishment during AMF relocation, step 2: proposal for the roaming case: The V-PCF receiving the PCF ID from old AMF shall include the H-PCF ID in the Npcf_AMPolicyControl Get operation. - 4.16.3.2: AMF-initiated Policy Association Termination, step 1: removing the unnecessary text based on the agreement at SA WG2#124. - 5.2.2.2.2: Table 5.2.2.2.2-1: UE Context in AMF - adding 'PCF ID' based on the agreement at SA WG2#124, and additionally 'H-PCF ID' based on the proposal on V\/H-PCF selection by AMF","secretary_remarks":"Revision of S2-180304, merging S2-180644. Revised in parallel session to S2-181050.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15100,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180304","revisedto":"S2-181050","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180979.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180980","title":"23.503: Clarification PCF interaction","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2: general clarification - 5.3.3: general clarification - 5.3.4: clarification on unclear description about roaming options, LBO and HR. HR or LBO should be referring to a particular PDU session instead of per UE. \u00e8 Proposing two alternatives. One should be selected. - 6.1.2.1: removing the unnecessary text based on the agreement at SA WG2#124. - 6.1.2.2, 6.1.2.2.1: general clarification","secretary_remarks":"Revision of S2-180305. Revised in parallel session to S2-181051.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15130,"status":"revised","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180305","revisedto":"S2-181051","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180980.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180981","title":"23.501: Clarification on PCC support of EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: AMF unsubscribes the policy notification when UE doesn't camp on 5GS.  The combined PCF\/PCRF needs to provide PCC rule or policy information applied to EPC only in addition.  The combined SMF\/PGW-C performs the PCC rule or policy adaptation so that only the PCC rules or policy applied to either EPC or 5GC are enforced.","secretary_remarks":"Revision of S2-180435. Noted in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15170,"status":"noted","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180435","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180981.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180982","title":"23.503: Remove EN related with EPC IWK","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Removes the EN in 6.1.3.5 2. Removes the EN in 6.3.1 and adds a NOTE to the removed attibutes for the clarification that they are provided for EPC IWK in Table 6.3.1 3. Adds 6.1.3.18 for the description on EPC IWK","secretary_remarks":"Revision of S2-180436. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15190,"status":"approved","reservation_date":"2018-01-24 10:28:33","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180436","revisedto":"S2-181790","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180982.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180988","title":"23.503: Remove some ENs","source":"Nokia, Nokia Shanghai Bell","contact":"Yang Shen","contact-id":68465,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Remove the above referred ENs.","secretary_remarks":"Revision of S2-180277. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15230,"status":"approved","reservation_date":"2018-01-25 06:55:17","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180277","revisedto":"S2-181791","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180988.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180989","title":"23.503: Removal of editor's notes and addition of references to empty sections","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It is proposed to remove those editor's notes.  The following empty sections are proposed to be filled with a description or reference to a description in TS 23.203:  - 4.2.4 Management of packet flow descriptions,  - 6.1.3.16 3GPP PS Data Off,  - 6.2.4 Unified Data Repository,  - 6.2.7 Network Exposure Function.","secretary_remarks":"Revision of S2-180324, merging S2-180276. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15250,"status":"approved","reservation_date":"2018-01-25 06:55:17","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180324","revisedto":"S2-181576","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180989.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180990","title":"23.502: Handling of AMF and PCF interaction when there is a PLMN change during AMF relocation.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update the registration procedure to reflect that when there is AMF relocation and the new AMF is in a different PLMN, the old AMF does not transfer the PCF ID nor the AM policy information and the event triggers subscribed by the PCF. The old AMF terminates the policy association to the PCF.","secretary_remarks":"Revision of S2-180182. Merged into S2-181054","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15280,"status":"merged","reservation_date":"2018-01-25 06:55:17","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180182","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180990.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180991","title":"23.502: Correction on the Policy association procedure during AMF relocation","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Reclassified the Policy Association Establishment procedure into two cases: a) Policy Association Establishment procedure with new PCF (No UE context); b) Policy Association Establishment procedure with old PCF (Has UE context). 2. Update the existing description for the procedure that old PCF is used. 3. Update the description about the Policy Association Establishment procedure in registration.","secretary_remarks":"Revision of S2-180321. Revised in parallel session, merging S2-180990, to S2-181054.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15300,"status":"revised","reservation_date":"2018-01-25 06:55:17","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180321","revisedto":"S2-181054","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180991.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180992","title":"23.502: Cleanup of NamfEventExposure and NsmfEventExposure services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Definition of a services, Namf_EventExposure and Nsmf_EventExposure are clarified.","secretary_remarks":"Revision of S2-180183. Revised to S2-181387.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15340,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180183","revisedto":"S2-181387","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180992.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180993","title":"23.503: Influence of additional non-standardized QoS parameters on QoS Flow Binding","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The additional AW\/MDBV added into PCC Rule information and considered during QoS Flow Binding.","secretary_remarks":"Revision of S2-180284. Revised in parallel session to S2-181055.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15370,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180284","revisedto":"S2-181055","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180993.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180994","title":"23.503: QoS rule generation","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify each QoS rule provided by SMF is generated from a PCC rule. The default QoS rule is generated by SMF based on the authorized default 5QI and ARP received from PCF, if a Packet Filter Set is included in the default QoS rule, the PCF may provide a default Packet Filter Set in the PDU Session related policy information to SMF. Clarify for a PDU session of unstructured type, no PCC Rule is provided to SMF. SMF generates the default QoS rule based on the authorized default 5QI and ARP received in the PDU Session related policy information.","secretary_remarks":"Revision of S2-180253. Revised in parallel session to S2-181056.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15400,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180253","revisedto":"S2-181056","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180994.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180995","title":"23.501: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Update clause 5.22 to indicate that the service layer can provide instructions on how to perform pre-emption of media flows when no resources are available.","secretary_remarks":"Revision of S2-180081. Endorsed","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15430,"status":"endorsed","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180081","revisedto":"S2-181615","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180995.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180996","title":"23.503: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: PCF functional description of resource reservation for service sharing priority is updated to align with the functional description of this feature in TS 23.203.","secretary_remarks":"Revision of S2-180082. Agreed in parallel session.  Wrong document uploaded. Revised to S2-181391","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15450,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180082","revisedto":"S2-181391","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180996.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180997","title":"23.502: Selecting a common PCF for UE and Session Policies","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Optionally, passing the selected PCF Id by AMF to SMF.","secretary_remarks":"Revision of S2-180250. For e-mail approval. e-mail revision 1 approved. Revised to S2-181401.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15480,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180250","revisedto":"S2-181401","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180997.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180998","title":"23.502: PCF selection for AMF during inter NG-RAN node N2 based handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: During the inter NG-RAN node N2 handover procedure, the S-AMF should provides the PCF ID to T-AMF for PCF selection.","secretary_remarks":"Revision of S2-180322. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15510,"status":"approved","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180322","revisedto":"S2-181574","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180998.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180999","title":"23.502: Correction on PCF selection in SMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add description about the AMF provide PCF information to SMF for PCF selection in PDU session management related procedures. 2. Correct the service name of step 3a and 5 in figure 4.3.2.2.1.","secretary_remarks":"Revision of S2-180323. Revised to S2-181388.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15530,"status":"revised","reservation_date":"2018-01-25 06:55:18","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180323","revisedto":"S2-181388","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-180999.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181005","title":"23.503: Remove EN related with Session binding","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 6.1.3.2.2: Session Binding applies only for PDU Sessions of IP type 2. \u00a7 6.1.1.2: remove the EN and add that S-NSSAI is part of the data used for session binding 3. Clarifications and Editorials:.","secretary_remarks":"Revision of S2-180132, merging S2-180076. Revised to S2-181389.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15640,"status":"revised","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180132","revisedto":"S2-181389","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181005.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181006","title":"LS on the definition of the Nocs spending limit report service","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG5. CC: CT WG3. Attachments: S2-180211, S2-180210","secretary_remarks":"Created in parallel session. For e-mail approval. Noted","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15680,"status":"noted","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181006.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181007","title":"23.502: Correction for event trigger report from SMF","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify the affected PCC rules and the QoS request for specific SDFs received from UE may be included in the Nsmf_EventExposure_Notify service","secretary_remarks":"Revision of S2-180254. This was withdrawn.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15760,"status":"withdrawn","reservation_date":"2018-01-25 14:56:19","uploaded":null,"revisionof":"S2-180254","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181008","title":"23.502: Correction of Npcf_BDTPolicyControl (background data transfer)","source":"KDDI","contact":"Takeshi Usui","contact-id":59388,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Added the Background Data Transfer policy reference ID and the description for step 9","secretary_remarks":"Revision of S2-180634. This was endorsed.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15730,"status":"endorsed","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180634","revisedto":"S2-181480","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181008.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181009","title":"23.502: Correction of UDR usage in policy related procedures","source":"China Mobile","contact":"Tao Sun","contact-id":54129,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The flows that PCF invoke UDR services are clarified in policy related procedures.","secretary_remarks":"Revision of S2-180757. This was endorsed.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15960,"status":"endorsed","reservation_date":"2018-01-25 14:56:19","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180757","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181009.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181010","title":"23.502: Update of Npcf_SMPolicyControl service","source":"Oracle, ZTE, Ericsson, Sandvine, Openet","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_SMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Nsmf_EventExposure Service! AMF, AF\/NEF and\/or any other consumer can still use this service as is, as long as the SMF simply notifies subscribers of events in a 'fire and forget' fashion. Update 23.502 Npcf_SMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the SMF:  - Update the optional input parameters of the Npcf_SMPolicyControl_Get service operation to provide event notification (in the case of SMF initiated modifications). - Update the optional output parameters of the Npcf_SMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_SMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Revision of S2-180969. Postponed in parallel session.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14860,"status":"postponed","reservation_date":"2018-01-25 14:56:31","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180969","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181010.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181011","title":"23.502: Update of Npcf_AMPolicyControl service","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes the addition of event subscription and event notification to the Npcf_AMPolicyControl service to address the concerns raised above. NOTE: This does NOT impact the Namf_EventExposure Service! SMF, AF\/NEF, UDM, GMLC and\/or any other consumer can still use this service as is, as long as the AMF simply notifies subscribers of events in a 'fire and forget' fashion.  Update 23.502 Npcf_AMPolicyControl service to enable the PCF to subscribe to event notifications and to receive event notifications from the AMF:  - Update the optional input parameters of the Npcf_AMPolicyControl_Get service operation to provide event notification (in the case of AMF initiated modifications). - Update the optional output parameters of the Npcf_AMPolicyControl_Get service operation to subscribe to event triggers. - Update the optional input parameters of the Npcf_AMPolicyControl_UpdateNotify service operation with subscription to event triggers.","secretary_remarks":"Revision of S2-180970. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14890,"status":"withdrawn","reservation_date":"2018-01-25 14:56:31","uploaded":null,"revisionof":"S2-180970","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181012","title":"23.502: Update of Session Management Policy Establishment procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Establishment procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service.doc'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. This can be done in step 5. Consequently steps 6 and 7 are not needed, and so are removed from the procedure.","secretary_remarks":"Revision of S2-180971. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14920,"status":"withdrawn","reservation_date":"2018-01-25 14:56:31","uploaded":null,"revisionof":"S2-180971","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181013","title":"23.502: Update of Session Management Policy Modification procedure","source":"Oracle, ZTE, Ericsson?, Sandvine","contact":"Uri Baniel","contact-id":58644,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: This document proposes updating 23.502 Session Management Policy Modification procedure based on the Npcf_SMPolicyControl service optimization(s) introduced in an accompanying paper 'Update of Npcf_SMPolicyControl service'. This optimization enables the PCF to subscribe to event notifications and to receive event notifications from the SMF by using the Npcf_SMPolicyControl service. Specifically event notification from SMF to PCF can be done in step 1a by using the Npcf_SMPolicyControl_Get service operation. Step 2a may include subscription by the PCF to Event Triggers by using the response to the Npcf_SMPolicyControl_Get service operation. Similarly, Step 5 may include subscription by the PCF to Event Triggers by using the pcf_SMPolicyControl_UpdateNotify service operation.Consequently steps 7 and 8 are not needed, and so are removed from the procedure. On top of that it makes more sense now to split the procedure into two procedures: Session Management Policy Modifi","secretary_remarks":"Revision of S2-180972. Postponed in parallel session. WITHDRAWN","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14950,"status":"withdrawn","reservation_date":"2018-01-25 14:56:31","uploaded":null,"revisionof":"S2-180972","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181039","title":"23.502: Mobility restrictions (service area) when roaming","source":"NEC","contact":"Sivasubramaniam Ramanan","contact-id":28064,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 4.16.1.2 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during Registration 4.16.1.3 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during AMF relocation 4.16.2.1 subclause title; minor correction 4.16.2.2; Npcf_AMPolicyControl_UpdateNotify in case of roaming scenario","secretary_remarks":"Revision of S2-180370. Revised in parallel session to S2-181053.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15830,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180370","revisedto":"S2-181053","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181039.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181040","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC, Lenovo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"Revision of S2-180924, merging S2-180926. Revised to S2-181386.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14580,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180924","revisedto":"S2-181386","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181040.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181041","title":"23.503: Description of components in URSP","source":"Huawei, HiSilicon","contact":"Guowei Ouyang","contact-id":47206,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Filling the description of the components. 2. Multiple Route Selection Descriptors in one URSP rule.  3. Non-Seamless Offload indication doesn't coexist with other component.","secretary_remarks":"Revision of S2-180966. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14630,"status":"approved","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180966","revisedto":"S2-181580","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181041.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181042","title":"23.502: UE polices ack from UE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The following solution is proposed:  - - The UE sends back to the AMF a NAS message acknowledging the reception and storage of the UE policies.  - - In addition, to cover those error cases where the UE receives the NAS message from the AMF but has some error in the storing of the UE policies information, the UE may include in the ACK message with additional information about the error. If this optional IE is present in the ACK message, the AMF will send this error to the PCF (stage 3 will decide the message) and this will handle the error, e.g. updating UE context in the PCF accordingly and reattempting the sending of UE policies later on.","secretary_remarks":"Revision of S2-180968. This was withdrawn.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14790,"status":"withdrawn","reservation_date":"2018-01-26 07:39:41","uploaded":null,"revisionof":"S2-180968","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181043","title":"23.501: Clarification on PCF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Updating the PCF selection with the following proposals - The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF. - The SMF sends the PCF selected by the AMF to the SMF during the PDU session establishment procedure Fixing the typo in the clause 6.3.7.0","secretary_remarks":"Revision of S2-180978. Revised in parallel session to S2-181049.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15070,"status":"revised","reservation_date":"2018-01-26 07:39:41","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180978","revisedto":"S2-181049","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181043.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181049","title":"23.501: Clarification on PCF selection","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Updating the PCF selection with the following proposals - The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF. - The SMF sends the PCF selected by the AMF to the SMF during the PDU session establishment procedure Fixing the typo in the clause 6.3.7.0","secretary_remarks":"Revision of S2-181043. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15080,"status":"approved","reservation_date":"2018-01-26 13:52:02","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181043","revisedto":"S2-181500","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181049.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181050","title":"23.502: Clarification on PCF association","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2.2.2-1: Registration, step 5: Removing 'PCF ID' because it is already included in UE context exchanged for inter-AMF mobility. Step 16: change 'PCF ID' into '(V-)PCF ID' - 4.16.1.2: Policy Association Establishment during Registration, step 2: proposal for the roaming case: The AMF may select both PCFs. Based on operator policies, the AMF may send the H-PCF address to the V-PCF, and V-PCF uses it unless locally configured on V-PCF - 4.16.1.3: Policy Association Establishment during AMF relocation, step 2: proposal for the roaming case: The V-PCF receiving the PCF ID from old AMF shall include the H-PCF ID in the Npcf_AMPolicyControl Get operation. - 4.16.3.2: AMF-initiated Policy Association Termination, step 1: removing the unnecessary text based on the agreement at SA WG2#124. - 5.2.2.2.2: Table 5.2.2.2.2-1: UE Context in AMF - adding 'PCF ID' based on the agreement at SA WG2#124, and additionally 'H-PCF ID' based on the proposal on V\/H-PCF selection by AMF","secretary_remarks":"Revision of S2-180979. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15110,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180979","revisedto":"S2-181528, S2-182163","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181050.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181051","title":"23.503: Clarification PCF interaction","source":"LG Electronics","contact":"Hyunsook Kim","contact-id":42013,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: - 4.2.2: general clarification - 5.3.3: general clarification - 5.3.4: clarification on unclear description about roaming options, LBO and HR. HR or LBO should be referring to a particular PDU session instead of per UE. \u00e8 Proposing two alternatives. One should be selected. - 6.1.2.1: removing the unnecessary text based on the agreement at SA WG2#124. - 6.1.2.2, 6.1.2.2.1: general clarification","secretary_remarks":"Revision of S2-180980. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15140,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180980","revisedto":"S2-181499","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181051.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181052","title":"23.502: Proposed resolution of Editor\u00b4s Notes in 23.502","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The proposal to resolve 1) above is to remove the Editor\u00b4s note. The reason is that the Access and Mobility related policy control the V-PCF generates the service area restrictions, those are not received from H-PCF as defined in clause 6.2.1.4 in TS 23.503.  The proposal to resolve 2) above is to remove the Editor\u00b4s note. The reason is that the functional description of the AF interactions described in 23.501 and 23.503 are either related to request for resources, prioritization of services, requires to steer to traffic to a DNAI(s), or request to charge traffic to the sponsor. These features require to provision PCC Rules to SMF.  The proposal to resolve 3) above is to extend the number of scenarios when the policy association termination procedure applies to include the notification of the removal of the policy profile from UDR. In addition, it is proposed to add a new procedure for (policy) session management termination when the UDR notifies the PCF that the pol","secretary_remarks":"Revision of S2-180232. Agreed in parallel session. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15210,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180232","revisedto":"S2-181632","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181052.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181053","title":"23.502: Mobility restrictions (service area) when roaming","source":"NEC","contact":"Sivasubramaniam Ramanan","contact-id":28064,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 4.16.1.2 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during Registration 4.16.1.3 step 3; Npcf_AMPolicyControl_Get response for Policy Association Establishment during AMF relocation 4.16.2.1 subclause title; minor correction 4.16.2.2; Npcf_AMPolicyControl_UpdateNotify in case of roaming scenario","secretary_remarks":"Revision of S2-181039. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15840,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181039","revisedto":"S2-181676","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181053.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181054","title":"23.502: Correction on the Policy association procedure during AMF relocation","source":"Huawei, HiSilicon,Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Reclassified the Policy Association Establishment procedure into two cases: a) Policy Association Establishment procedure with new PCF (No UE context); b) Policy Association Establishment procedure with old PCF (Has UE context). 2. Update the existing description for the procedure that old PCF is used. 3. Update the description about the Policy Association Establishment procedure in registration.","secretary_remarks":"Revision of S2-180991, merging S2-180990. For e-mail approval. e-mail revision 2 approved. Revised to S2-181400.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15310,"status":"revised","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-29 10:17:52","revisionof":"S2-180991","revisedto":"S2-181400","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181054.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181055","title":"23.503: Influence of additional non-standardized QoS parameters on QoS Flow Binding","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The additional AW\/MDBV added into PCC Rule information and considered during QoS Flow Binding.","secretary_remarks":"Revision of S2-180993. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15380,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180993","revisedto":"S2-181577","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181055.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181056","title":"23.503: QoS rule generation","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify each QoS rule provided by SMF is generated from a PCC rule. The default QoS rule is generated by SMF based on the authorized default 5QI and ARP received from PCF, if a Packet Filter Set is included in the default QoS rule, the PCF may provide a default Packet Filter Set in the PDU Session related policy information to SMF. Clarify for a PDU session of unstructured type, no PCC Rule is provided to SMF. SMF generates the default QoS rule based on the authorized default 5QI and ARP received in the PDU Session related policy information.","secretary_remarks":"Revision of S2-180994. Agreed in parallel session","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15410,"status":"approved","reservation_date":"2018-01-26 13:52:03","uploaded":"2018-01-26 18:07:54","revisionof":"S2-180994","revisedto":"S2-181604","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181056.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181386","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC, Lenovo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"Revision of S2-181040. For e-mail approval. e-mail revision 4 approved. Revised to S2-181399.","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14590,"status":"revised","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-29 07:57:53","revisionof":"S2-181040","revisedto":"S2-181399","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181386.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181387","title":"23.502: Cleanup of NamfEventExposure and NsmfEventExposure services","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Definition of a services, Namf_EventExposure and Nsmf_EventExposure are clarified.","secretary_remarks":"Revision of S2-180992. For e-mail approval. Noted","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15350,"status":"noted","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-29 13:27:54","revisionof":"S2-180992","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181387.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181388","title":"23.502: Correction on PCF selection in SMF","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Add description about the AMF provide PCF information to SMF for PCF selection in PDU session management related procedures. 2. Correct the service name of step 3a and 5 in figure 4.3.2.2.1.","secretary_remarks":"Revision of S2-180999. For e-mail approval. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15540,"status":"approved","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-29 10:17:52","revisionof":"S2-180999","revisedto":"S2-181575, S2-182169","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181388.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181389","title":"23.503: Remove EN related with Session binding","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. \u00a7 6.1.3.2.2: Session Binding applies only for PDU Sessions of IP type 2. \u00a7 6.1.1.2: remove the EN and add that S-NSSAI is part of the data used for session binding 3. Clarifications and Editorials:.","secretary_remarks":"Revision of S2-181005. For e-mail approval. Postponed","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15650,"status":"postponed","reservation_date":"2018-01-26 17:55:41","uploaded":"2018-01-26 18:07:55","revisionof":"S2-181005","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181389.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181391","title":"23.503: Resource reservation for services sharing priority","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: PCF functional description of resource reservation for service sharing priority is updated to align with the functional description of this feature in TS 23.203.","secretary_remarks":"Revision of S2-180996. Block Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15460,"status":"approved","reservation_date":"2018-01-30 08:49:39","uploaded":"2018-01-30 08:57:58","revisionof":"S2-180996","revisedto":"S2-181634","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181391.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181399","title":"23.503: UE policies granularity and UE assistance for policy evaluation.","source":"Ericsson, NEC, Lenovo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify that a URSP\/WLANSP rule contains an identifier and that the PCF can perform operations (add\/delete\/replace) per individual URSP\/WLANSP rule. The UE sends at initial registration the list of UE policies currently stored in the device and the PCF uses this information as input for policy decisitions.","secretary_remarks":"e-mail revision 4 of S2-181386. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":14600,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181386","revisedto":"S2-181612","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181399.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181400","title":"23.502: Correction on the Policy association procedure during AMF relocation","source":"Huawei, HiSilicon,Ericsson","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: 1. Reclassified the Policy Association Establishment procedure into two cases: a) Policy Association Establishment procedure with new PCF (No UE context); b) Policy Association Establishment procedure with old PCF (Has UE context). 2. Update the existing description for the procedure that old PCF is used. 3. Update the description about the Policy Association Establishment procedure in registration.","secretary_remarks":"e-mail revision 2 of S2-181054. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15320,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-181054","revisedto":"S2-181573","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","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_125_Gothenburg\/Docs\/S2-181400.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181401","title":"23.502: Selecting a common PCF for UE and Session Policies","source":"Cisco Systems, Inc","contact":"Ravi Shekhar","contact-id":71185,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Optionally, passing the selected PCF Id by AMF to SMF.","secretary_remarks":"e-mail revision 1 of S2-180997. Approved","agenda_item_sort_order":23,"ainumber":"6.5.6","ainame":"Policy and charging control","tdoc_agenda_sort_order":15490,"status":"approved","reservation_date":"2018-02-02 10:04:25","uploaded":"2018-02-02 10:30:31","revisionof":"S2-180997","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181401.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]