[{"name":"S2-187656","title":"LS from RAN WG2: Reply LS on MDBV for delay critical QoS flows","source":"RAN WG2","contact":"Benoist SEBIRE","contact-id":68461,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their LS on MDBV for delay critical QoS flows. SA WG2 asked 'RAN WG2 to confirm that the PDB and PER requirements are satisfied in the UL and DL for all delay critical QoS flows that do not exceed the MDBV, even if other delay critical QoS Flows (which may also be of higher priority) for the same UE or other UE exceeds the MDBV.' RAN WG2 has discussed the issue and would like to inform SA WG2 of the following: 1. In the downlink, RAN WG2 confirms that it is always possible. 2. In the uplink, RAN WG2 cannot confirm as RAN WG2 did not achieve consensus on whether changes are needed in order to guarantee the above in all possible configurations. RAN WG2 has agreed not to introduce any new mechanisms for this feature in Rel-15. Action: RAN WG2 respectfully asks SA WG2 to take the above into account.","secretary_remarks":"This LS was postponed.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12660,"status":"postponed","reservation_date":"2018-07-30 09:25:20","uploaded":"2018-07-30 09:27:51","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-1810956","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187656.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187795","title":"Alignment with CT WG1 to use QoS Flow Description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.7.1.1 Clarify that QoS Flow Description may be sent associated with the QoS rule.  Clause 5.7.1.2 Clarify that QoS profile is sent to the (R)AN.  Clause 5.7.1.2A (new) Introduce QoS Flow Description to describe the set of QoS Flow level parameters which are sent to the UE separately from the QoS rule(s).  Clause 5.7.1.4 and clause 5.7.1.5,  Use QoS Flow Decription for 'QoS Flow level QoS parametersDescription (e.g. 5QI, GFBR, MFBR, Averaging Window'.   Clause 5.7.2.5  Clarify that the SMF signals the GFBR\/MFBR parameters to RAN in QoS Profile and to UE in QoS Flow Description.","secretary_remarks":"Revised in parallel session to S2-188738.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12670,"status":"revised","reservation_date":"2018-08-12 14:24:05","uploaded":"2018-08-14 12:45:32","revisionof":"","revisedto":"S2-188738","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":559.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187795.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187883","title":"Discussion on the Usage of QoS Notification Control","source":"China Telecom","contact":"Zhao Song","contact-id":71667,"tdoctype":"discussion","for":"Information","abstract":"The limitation of the usage of QoS Notification Control is discussed.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12770,"status":"noted","reservation_date":"2018-08-13 10:20:38","uploaded":"2018-08-14 10:50:34","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_128BIS_Sophia_Antipolis\/Docs\/S2-187883.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187983","title":"Guidance on when and how to apply 5QI Priority Level","source":"Vencore Labs, OEC, Sprint, AT&T, Verizon UK Ltd., T-Mobile USA","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added that the Priority Level is applied when PDB can't be met for one or more QoS Flows and how the relative priority of different QoS Flows are handled.","secretary_remarks":"Merged into S2-188741.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12840,"status":"merged","reservation_date":"2018-08-13 17:40:07","uploaded":"2018-08-13 19:17:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":581.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187983.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-187985","title":"Consistent Description of 5QI","source":"Vencore Labs, OEC, Sprint, Verizon UK. Ltd., AT&T, T-Mobile USA","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that pre-configured 5QI can also have certain default values overridden. Clarified what is included in the QoS profile for dynamic 5QIs and standardized\/pre-configured 5QIs with overridden values. Added that QoS rules rules may contain Priority Level. Clause 5.7.2.7 made consistent with clause 5.22.2 by adding that the default values retrieved from the UDM can include Priority Level. Other editorial corrections.","secretary_remarks":"Revised in parallel session to S2-188737.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12700,"status":"revised","reservation_date":"2018-08-13 17:44:25","uploaded":"2018-08-13 19:17:19","revisionof":"","revisedto":"S2-188737","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":583.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-187985.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188027","title":"Missing requirements to trigger Notification Control","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Notifications are sent when the QoS targets of the QoS Flow can not be guaranteed by RAN. A note is added clarifying what RAN can base the notification on.","secretary_remarks":"Revised in parallel session, merging S2-188272, to S2-188740.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12790,"status":"revised","reservation_date":"2018-08-13 23:03:10","uploaded":"2018-08-14 12:45:32","revisionof":"","revisedto":"S2-188740","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":587.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188027.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188147","title":"Clarification for pre-configured QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the QFI and Packet Filter Set of the pre-configured QoS rule can be configured at SMF and UPF serving the whole PLMN\/DNN\/slice, or SMF retrieves them from UDM for a specific UE and provides them to UPF.","secretary_remarks":"Revision of (revised and postponed) S2-186699 from S2#128. Revised in parallel session to S2-188742.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12900,"status":"revised","reservation_date":"2018-08-14 06:31:47","uploaded":"2018-08-14 09:08:22","revisionof":"S2-186699","revisedto":"S2-188742","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":501.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188147.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188148","title":"Clarification for QoS flow associated with the default QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify If the QoS Flow associated with the default QoS rule is a GBR QoS Flow, the network shall indicate the QoS Flow associated with the default QoS rule to AN, if the GFBR of the QoS Flow associated with the default QoS rule can't be guaranteed, AN rejects the PDU Session establishment or initiates the release of the PDU Session.","secretary_remarks":"Revised in parallel session to S2-188743.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12930,"status":"revised","reservation_date":"2018-08-14 06:45:49","uploaded":"2018-08-14 09:08:22","revisionof":"","revisedto":"S2-188743","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":602.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188148.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188149","title":"Clarification for QoS flow associated with the default QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify If the QoS Flow associated with the default QoS rule is a GBR QoS Flow, the network shall indicate the QoS Flow associated with the default QoS rule to AN, if the GFBR of the QoS Flow associated with the default QoS rule can't be guaranteed, AN rejects the PDU Session establishment or initiates the release of the PDU Session.","secretary_remarks":"Revised in parallel session to S2-188745.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12990,"status":"revised","reservation_date":"2018-08-14 06:49:50","uploaded":"2018-08-14 09:08:22","revisionof":"","revisedto":"S2-188745","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":699.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188149.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188206","title":"Clarifications for signaled QoS characteristics","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that for non-standardized 5QIs the complete 5G QoS characteristics has to be signalled\/pre-configured. Furthermore, the signaling of partial 5G QoS characteristics (e.g. only the Averaging window) is restricted to QoS Flows with standardized 5QIs. The wording for the usage of signaled Averaging window or MDBV for standardized 5QIs is updated.","secretary_remarks":"Revised in parallel session to S2-188739.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12740,"status":"revised","reservation_date":"2018-08-14 09:06:24","uploaded":"2018-08-14 14:27:06","revisionof":"","revisedto":"S2-188739","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":606.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188206.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188207","title":"Clarifications for 5QI priority level","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A definition for the usage of the 5QI priority level is added. In addition, a few words\/sentences are moved around to improve readability.","secretary_remarks":"Revised in parallel session, merging S2-187983, to S2-188741.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12850,"status":"revised","reservation_date":"2018-08-14 09:06:26","uploaded":"2018-08-14 14:27:06","revisionof":"","revisedto":"S2-188741","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":607.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188207.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188208","title":"The resource type of QoS Flow associated with the default QoS rule","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A description is added about the SMF configuration that enables the establishment of a default GBR QoS Flow for a PDU Session.  The SMF behavior is clarified for the case that the GBR QoS Flow cannot be established successfully or AN resources onto which a QoS Flow is mapped are released later on.","secretary_remarks":"Revision of (agreed) S2-187507 from S2#128. Revised in parallel session to S2-188744.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12950,"status":"revised","reservation_date":"2018-08-14 09:06:27","uploaded":"2018-08-14 14:27:06","revisionof":"S2-187507","revisedto":"S2-188744","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":473.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188208.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188272","title":"CR on QoS Notification Control in 23501","source":"China Telecom","contact":"Zhao Song","contact-id":71667,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replace the GFBR with QoS target in the overall description of the QoS Notification Control.","secretary_remarks":"Merged into S2-188740.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12780,"status":"merged","reservation_date":"2018-08-14 10:34:09","uploaded":"2018-08-14 10:50:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":613.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188272.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188361","title":"LS from SA WG4: LS on QoS Handling for Media Distribution over 5G","source":"SA WG4","contact":"Imed Bouazizi","contact-id":73336,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 is studying media distribution over the new 5G system as part of the FS_5GMedia_Distribution study item documented in TR 26.891. This study covers issues around mapping existing and new media distribution services to the 5G architecture and identifying potential optimizations and gaps to leverage the full set of capabilities of the 5G system towards offering a service-customized traffic handling for media distribution services. As part of this exercise, a set of questions and open issues have been identified and SA WG4 would like to seek guidance from SA WG2 on these issues. The questions are as follows: 1. SA WG4 identified a set of application functions that would require processing of the user plane data. However, the current definition of the AF function only specifies the control plane procedures and interfaces. Which function in the 5G System is responsible for performing application-specific user plane processing? Does the 5G System consider the Edge Compute node as being","secretary_remarks":"Response drafted in S2-188363. Final response in S2-189036","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13040,"status":"replied to","reservation_date":"2018-08-17 07:20:59","uploaded":"2018-08-17 07:27:52","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S4-AHI806","lsreply":"S2-189036, S2-189036","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188361.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188363","title":"Reply to LS on QoS Handling for Media Distribution over 5G","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4","secretary_remarks":"LATE DOC: Rx 17\/08, 10:30. Response to S2-188361. Revised in parallel session to S2-188746.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13050,"status":"revised","reservation_date":"2018-08-21 05:57:30","uploaded":"2018-08-21 05:57:51","revisionof":"","revisedto":"S2-188746","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188363.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188365","title":"Response analysis to S2-187983 and S2-188207: On Scheduling in RAN - Controlling Delay for TCP traffic.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This paper proposes not to standardize the scheduling algorithm in RAN as response to the proposals in S2-187983 and S2-188207.","secretary_remarks":"LATE REQ. LATE DOC: Rx 17\/08, 21:45. Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12830,"status":"not treated","reservation_date":"2018-08-17 19:42:58","uploaded":"2018-08-17 19:51:16","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_128BIS_Sophia_Antipolis\/Docs\/S2-188365.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188737","title":"Consistent Description of 5QI","source":"Vencore Labs, OEC, Sprint, Verizon UK. Ltd., AT&T, T-Mobile USA, FirstNet","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that pre-configured 5QI can also have certain default values overridden. Clarified what is included in the QoS profile for dynamic 5QIs and standardized\/pre-configured 5QIs with overridden values. Added that QoS rules rules may contain Priority Level. Clause 5.7.2.7 made consistent with clause 5.22.2 by adding that the default values retrieved from the UDM can include Priority Level. Other editorial corrections.","secretary_remarks":"Revision of S2-187985. Revised in parallel session to S2-188934.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12710,"status":"revised","reservation_date":"2018-08-22 08:08:15","uploaded":"2018-08-26 10:27:51","revisionof":"S2-187985","revisedto":"S2-188934","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":583.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188737.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188738","title":"Alignment with CT WG1 to use QoS Flow Description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.7.1.1 Clarify that QoS Flow Description may be sent associated with the QoS rule.  Clause 5.7.1.2 Clarify that QoS profile is sent to the (R)AN.  Clause 5.7.1.2A (new) Introduce QoS Flow Description to describe the set of QoS Flow level parameters which are sent to the UE separately from the QoS rule(s).  Clause 5.7.1.4 and clause 5.7.1.5,  Use QoS Flow Decription for 'QoS Flow level QoS parametersDescription (e.g. 5QI, GFBR, MFBR, Averaging Window'.   Clause 5.7.2.5  Clarify that the SMF signals the GFBR\/MFBR parameters to RAN in QoS Profile and to UE in QoS Flow Description.","secretary_remarks":"Revision of S2-187795. Revised in parallel session to S2-188916.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12680,"status":"revised","reservation_date":"2018-08-22 08:08:16","uploaded":"2018-08-26 10:27:51","revisionof":"S2-187795","revisedto":"S2-188916","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":559.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188738.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188739","title":"Clarifications for signaled QoS characteristics","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that for non-standardized 5QIs the complete 5G QoS characteristics has to be signalled\/pre-configured. Furthermore, the signaling of partial 5G QoS characteristics (e.g. only the Averaging window) is restricted to QoS Flows with standardized 5QIs. The wording for the usage of signaled Averaging window or MDBV for standardized 5QIs is updated.","secretary_remarks":"Revision of S2-188206. Revised in parallel session to S2-188935.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12750,"status":"revised","reservation_date":"2018-08-22 08:08:17","uploaded":"2018-08-26 10:27:51","revisionof":"S2-188206","revisedto":"S2-188935","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":606.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188739.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188740","title":"Missing requirements to trigger Notification Control","source":"Ericsson, China Telecom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Notifications are sent when the QoS targets of the QoS Flow can not be guaranteed by RAN. A note is added clarifying what RAN can base the notification on.","secretary_remarks":"Revision of S2-188027, merging S2-188272. Revised in parallel session to S2-188932.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12800,"status":"revised","reservation_date":"2018-08-22 08:08:19","uploaded":"2018-08-26 10:27:51","revisionof":"S2-188027","revisedto":"S2-188932","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":587.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188740.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188741","title":"Clarifications for 5QI priority level","source":"Huawei, HiSilicon, Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon UK Ltd., Sprint","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A definition for the usage of the 5QI priority level is added. In addition, a few words\/sentences are moved around to improve readability.","secretary_remarks":"Revision of S2-188207, merging S2-187983. Revised in parallel session to S2-188933.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12860,"status":"revised","reservation_date":"2018-08-22 08:08:20","uploaded":"2018-08-26 10:27:51","revisionof":"S2-188207","revisedto":"S2-188933","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":607.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188741.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188742","title":"Clarification for pre-configured QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the QFI and Packet Filter Set of the pre-configured QoS rule can be configured at SMF and UPF serving the whole PLMN\/DNN\/slice, or SMF retrieves them from UDM for a specific UE and provides them to UPF.","secretary_remarks":"Revision of S2-188147. Revised in parallel session to S2-188936.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12910,"status":"revised","reservation_date":"2018-08-22 08:08:21","uploaded":"2018-08-26 10:27:51","revisionof":"S2-188147","revisedto":"S2-188936","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":501.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188742.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188743","title":"Clarification for QoS flow associated with the default QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify If the QoS Flow associated with the default QoS rule is a GBR QoS Flow, the network shall indicate the QoS Flow associated with the default QoS rule to AN, if the GFBR of the QoS Flow associated with the default QoS rule can't be guaranteed, AN rejects the PDU Session establishment or initiates the release of the PDU Session.","secretary_remarks":"Revision of S2-188148. WITHDRAWN","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12940,"status":"withdrawn","reservation_date":"2018-08-22 08:08:22","uploaded":null,"revisionof":"S2-188148","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":602.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188744","title":"The resource type of QoS Flow associated with the default QoS rule","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A description is added about the SMF configuration that enables the establishment of a default GBR QoS Flow for a PDU Session.  The SMF behavior is clarified for the case that the GBR QoS Flow cannot be established successfully or AN resources onto which a QoS Flow is mapped are released later on.","secretary_remarks":"Revision of S2-188208. Revised in parallel session to S2-188937.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12960,"status":"revised","reservation_date":"2018-08-22 08:08:24","uploaded":"2018-08-26 10:27:51","revisionof":"S2-188208","revisedto":"S2-188937","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":473.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188744.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188745","title":"Clarification for QoS flow associated with the default QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify If the QoS Flow associated with the default QoS rule is a GBR QoS Flow, the network shall indicate the QoS Flow associated with the default QoS rule to AN, if the GFBR of the QoS Flow associated with the default QoS rule can't be guaranteed, AN rejects the PDU Session establishment or initiates the release of the PDU Session.","secretary_remarks":"Revision of S2-188149. Revised off-line to S2-189003.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13000,"status":"revised","reservation_date":"2018-08-22 08:08:25","uploaded":"2018-08-26 10:27:51","revisionof":"S2-188149","revisedto":"S2-189003","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":699.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188745.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188746","title":"Reply to LS on QoS Handling for Media Distribution over 5G","source":"SA WG2","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4","secretary_remarks":"Revision of S2-188363. Revised in parallel session to S2-188938.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13060,"status":"revised","reservation_date":"2018-08-22 08:08:26","uploaded":"2018-08-26 10:27:51","revisionof":"S2-188363","revisedto":"S2-188938","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188746.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188916","title":"Alignment with CT WG1 on the QoS Flow Description","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.7.1.1 Clarify that QoS Flow Description may be sent associated with the QoS rule.  Clause 5.7.1.2 Clarify that QoS profile is sent to the (R)AN.  Clause 5.7.1.2A (new) Introduce QoS Flow Description to describe the set of QoS Flow level parameters which are sent to the UE separately from the QoS rule(s).  Clause 5.7.1.4 and clause 5.7.1.5,  Use QoS Flow Decription for 'QoS Flow level QoS parametersDescription (e.g. 5QI, GFBR, MFBR, Averaging Window'.   Clause 5.7.2.5  Clarify that the SMF signals the GFBR\/MFBR parameters to RAN in QoS Profile and to UE in QoS Flow Description.","secretary_remarks":"Revision of S2-188738. Agreed in parallel session Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12700,"status":"agreed","reservation_date":"2018-08-26 08:40:42","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188738","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":559.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180715","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188916.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188932","title":"Missing requirements to trigger Notification Control","source":"Ericsson, China Telecom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Notifications are sent when the QoS targets of the QoS Flow can not be guaranteed by RAN. A note is added clarifying what RAN can base the notification on.","secretary_remarks":"Revision of S2-188740. Revised to S2-189009.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12810,"status":"revised","reservation_date":"2018-08-26 08:40:43","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188740","revisedto":"S2-189009","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":587.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188932.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188933","title":"Clarifications for 5QI priority level","source":"Huawei, HiSilicon, Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon UK Ltd., Sprint","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A definition for the usage of the 5QI priority level is added. In addition, a few words\/sentences are moved around to improve readability.","secretary_remarks":"Revision of S2-188741. Revised to S2-189010.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12870,"status":"revised","reservation_date":"2018-08-26 08:40:43","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188741","revisedto":"S2-189010","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":607.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188933.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188934","title":"Consistent Description of 5QI","source":"Vencore Labs, OEC, Sprint, Verizon UK. Ltd., AT&T, T-Mobile USA, FirstNet","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that pre-configured 5QI can also have certain default values overridden. Clarified what is included in the QoS profile for dynamic 5QIs and standardized\/pre-configured 5QIs with overridden values. Added that QoS rules rules may contain Priority Level. Clause 5.7.2.7 made consistent with clause 5.22.2 by adding that the default values retrieved from the UDM can include Priority Level. Other editorial corrections.","secretary_remarks":"Revision of S2-188737. Revised to S2-189012.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12720,"status":"revised","reservation_date":"2018-08-26 08:40:44","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188737","revisedto":"S2-189012","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":583.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188934.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188935","title":"Clarifications for signaled QoS characteristics","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that for non-standardized 5QIs the complete 5G QoS characteristics has to be signalled\/pre-configured. Furthermore, the signaling of partial 5G QoS characteristics (e.g. only the Averaging window) is restricted to QoS Flows with standardized 5QIs. The wording for the usage of signaled Averaging window or MDBV for standardized 5QIs is updated.","secretary_remarks":"Revision of S2-188739. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12770,"status":"agreed","reservation_date":"2018-08-26 08:40:46","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188739","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":606.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180716","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188935.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188936","title":"Clarification for pre-configured QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the QFI and Packet Filter Set of the pre-configured QoS rule can be configured at SMF and UPF serving the whole PLMN\/DNN\/slice, or SMF retrieves them from UDM for a specific UE and provides them to UPF.","secretary_remarks":"Revision of S2-188742. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12930,"status":"agreed","reservation_date":"2018-08-26 08:40:47","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188742","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":501.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180713","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188936.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188937","title":"The resource type of QoS Flow associated with the default QoS rule","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A description is added about the SMF configuration that enables the establishment of a default GBR QoS Flow for a PDU Session.  The SMF behavior is clarified for the case that the GBR QoS Flow cannot be established successfully or AN resources onto which a QoS Flow is mapped are released later on.","secretary_remarks":"Revision of S2-188744. Revised to S2-189011.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12970,"status":"revised","reservation_date":"2018-08-26 08:40:48","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188744","revisedto":"S2-189011","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":473.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188937.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-188938","title":"Reply to LS on QoS Handling for Media Distribution over 5G","source":"SA WG2","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4","secretary_remarks":"Revision of S2-188746. This was left for e-mail approval. e-mail revision 2 approved. Revised to S2-189036.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13070,"status":"revised","reservation_date":"2018-08-26 08:40:48","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188746","revisedto":"S2-189036","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-188938.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189003","title":"Clarification for QoS flow associated with the default QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify If the QoS Flow associated with the default QoS rule is a GBR QoS Flow, the network shall indicate the QoS Flow associated with the default QoS rule to AN, if the GFBR of the QoS Flow associated with the default QoS rule can't be guaranteed, AN rejects the PDU Session establishment or initiates the release of the PDU Session.","secretary_remarks":"Revision of S2-188745. Revised to S2-189016.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13010,"status":"revised","reservation_date":"2018-08-26 09:45:13","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188745","revisedto":"S2-189016","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":699.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189003.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189009","title":"Missing requirements to trigger Notification Control","source":"Ericsson, China Telecom","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Notifications are sent when the QoS targets of the QoS Flow can not be guaranteed by RAN. A note is added clarifying what RAN can base the notification on.","secretary_remarks":"Revision of S2-188932. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12830,"status":"agreed","reservation_date":"2018-08-26 09:45:15","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188932","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":587.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180715","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189009.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189010","title":"Clarifications for 5QI priority level","source":"Huawei, HiSilicon, Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon UK Ltd., Sprint","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A definition for the usage of the 5QI priority level is added. In addition, a few words\/sentences are moved around to improve readability.","secretary_remarks":"Revision of S2-188933. Revised to S2-189024.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12880,"status":"revised","reservation_date":"2018-08-26 09:45:16","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188933","revisedto":"S2-189024","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":607.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189010.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189011","title":"The resource type of QoS Flow associated with the default QoS rule","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A description is added about the SMF configuration that enables the establishment of a default GBR QoS Flow for a PDU Session.  The SMF behavior is clarified for the case that the GBR QoS Flow cannot be established successfully or AN resources onto which a QoS Flow is mapped are released later on.","secretary_remarks":"Revision of S2-188937. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12990,"status":"agreed","reservation_date":"2018-08-26 09:45:17","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188937","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":473.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"SP-180713","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189011.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189012","title":"Consistent Description of 5QI","source":"Vencore Labs, OEC, Sprint, Verizon UK. Ltd., AT&T, T-Mobile USA, FirstNet","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarified that pre-configured 5QI can also have certain default values overridden. Clarified what is included in the QoS profile for dynamic 5QIs and standardized\/pre-configured 5QIs with overridden values. Added that QoS rules rules may contain Priority Level. Clause 5.7.2.7 made consistent with clause 5.22.2 by adding that the default values retrieved from the UDM can include Priority Level. Other editorial corrections.","secretary_remarks":"Revision of S2-188934. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12740,"status":"agreed","reservation_date":"2018-08-26 09:45:19","uploaded":"2018-08-26 10:27:52","revisionof":"S2-188934","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":583.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180715","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189012.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189016","title":"Clarification for QoS flow associated with the default QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify If the QoS Flow associated with the default QoS rule is a GBR QoS Flow, the network shall indicate the QoS Flow associated with the default QoS rule to AN, if the GFBR of the QoS Flow associated with the default QoS rule can't be guaranteed, AN rejects the PDU Session establishment or initiates the release of the PDU Session.","secretary_remarks":"Revision of S2-189003. Revised to S2-189032.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13020,"status":"revised","reservation_date":"2018-08-26 09:48:11","uploaded":"2018-08-26 10:27:52","revisionof":"S2-189003","revisedto":"S2-189032","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":699.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189016.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189024","title":"Clarifications for 5QI priority level","source":"Huawei, HiSilicon, Vencore Labs, OEC, AT&T, T-Mobile USA, Verizon UK Ltd., Sprint","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A definition for the usage of the 5QI priority level is added. In addition, a few words\/sentences are moved around to improve readability.","secretary_remarks":"Revision of S2-189010. This was left for e-mail approval. Noted","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":12890,"status":"noted","reservation_date":"2018-08-26 09:48:16","uploaded":"2018-08-26 10:27:52","revisionof":"S2-189010","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":607.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189024.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189032","title":"Clarification for QoS flow associated with the default QoS rule","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify If the QoS Flow associated with the default QoS rule is a GBR QoS Flow, the network shall indicate the QoS Flow associated with the default QoS rule to AN, if the GFBR of the QoS Flow associated with the default QoS rule can't be guaranteed, AN rejects the PDU Session establishment or initiates the release of the PDU Session.","secretary_remarks":"Revision of S2-189016. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13040,"status":"agreed","reservation_date":"2018-08-26 09:48:44","uploaded":"2018-08-26 10:27:52","revisionof":"S2-189016","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":699.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180721","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189032.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-189036","title":"Reply to LS on QoS Handling for Media Distribution over 5G","source":"SA WG2","contact":"Andy Bennett","contact-id":70253,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4","secretary_remarks":"e-mail revision 2 of S2-188938. e-mail approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":13071,"status":"approved","reservation_date":"2018-08-31 11:20:52","uploaded":"2018-08-31 11:27:52","revisionof":"S2-188938","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-188361","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_128BIS_Sophia_Antipolis\/Docs\/S2-189036.zip","group":"S2","meeting":"S2-128","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]