[{"name":"S2-181425","title":"LS from RAN WG2: Reply LS on LS on default values for 5GS QoS averaging window for standardised 5QIs","source":"RAN WG2","contact":"Benoist SEBIRE","contact-id":68461,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 has discussed the averaging window for standardised 5QIs and understands that the suggested default values of 2s and 3s are generally fine but views were also expressed that in some cases the window would either need to be shorter (in the order of a few PDBs for services with tight delay requirements) or longer (up to 10s for services with infrequent data transmissions). RAN WG2 also understands that the default value can always be overwritten through configuration. For URLLC, RAN WG2 also believes that a maximum burst size should be introduced for GBR resources. The maximum burst size would define the largest amount of data that the application can expect to be transmitted within the radio portion of the PDB. Action: RAN WG2 respectfully asks SA WG2 to take the above response into account.","secretary_remarks":"Postponed S2-180036 from S2#125. Noted in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15480,"status":"noted","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-01 17:35:41","revisionof":"S2-180036","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG4, SA WG6, CT WG1","lsoriginalls":"R2-1714245","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181425.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181448","title":"LS from RAN WG2: LS on QoS","source":"RAN WG2","contact":"Benoist SEBIRE","contact-id":68461,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed notification control for GBR QoS flows and would like to re-iterate the questions asked earlier in R2-1706143 (May 2017). 3GPP TS 23.501 states the following: 'It is up to the AN to establish the necessary AN resources that QoS Flows can be mapped to, and to release them. The AN shall indicate to the SMF when the AN resources onto which a QoS flow is mapped are released. [\u2026] If, for a given GBR QoS Flow, notification control is enabled and the NG-RAN determines that the GFBR cannot be fulfilled, RAN shall send a notification towards SMF. The RAN shall keep the QoS Flow, and should try to fulfil the GFBR. Upon receiving a notification from the RAN that the GFBR cannot be fulfilled, the 5GC may initiate N2 signalling to modify or remove the QoS Flow. When applicable, NG-RAN sends a new notification, informing SMF that the GFBR can be fulfilled again. After a configured time, the NG-RAN may send a subsequent notification that the GFBR cannot be fulfilled.' In RAN WG2","secretary_remarks":"Response drafted in S2-181904. Final response in S2-182856","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15550,"status":"replied to","reservation_date":"2018-01-29 17:29:48","uploaded":"2018-02-02 14:51:41","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"R2-1801645","lsreply":"S2-182856, S2-182856","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181448.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181472","title":"Corrections to RQoS logic when receiving DL packet with RQI","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The condition of QFI change is set after the re-start of the RQ Timer.","secretary_remarks":"Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15260,"status":"agreed","reservation_date":"2018-02-01 09:05:04","uploaded":"2018-02-20 12:15:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":11.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181472.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181473","title":"Draft LS to CT WG1 on Number of concurrent QoS rules\/packet filters","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"LS out","for":"Approval","abstract":"This draft LS recommends CT WG1 to proceed with defining the number of concurrent QoS rules\/packet filters the UE shall support in order to ensure consistent, predictable UE behavior.","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15750,"status":"not treated","reservation_date":"2018-02-01 09:05:05","uploaded":"2018-02-20 12:15:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181473.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181474","title":"UE Impact of Reflective QoS","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Agreement","abstract":"This discussion paper follows discussions that took place in CT WG1 and that need conclusions in SA WG2 regarding mitigation of UE impact of RQoS. It is an updated from S2-180366 seen at SA WG2#125","secretary_remarks":"Withdrawn (not provided).","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15890,"status":"withdrawn","reservation_date":"2018-02-01 09:05:05","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181475","title":"Reflective QoS support indication at PDU Session Establishment \/ Modification","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The UE supporting RQoS functionality selectively indicates whether RQoS is supported for a PDU Session - The UE triggers a PDU Session Modification to temporarily restrict the further use of RQoS for a PDU Session.  - The UE silently starts deriving new QoS rules when conditions allow","secretary_remarks":"This was left for off-line discussion. Noted in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15710,"status":"noted","reservation_date":"2018-02-01 09:05:05","uploaded":"2018-02-20 12:15:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":12.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181475.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181476","title":"Reflective QoS support indication at PDU Session Establishment \/ Modification","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UE triggers a PDU Session Modification to temporarily restrict the use of RQoS for a PDU Session, with a RQoS restriction indication that can be forwarded by the SMF to the UPF for adequate policing of UL packets.","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15730,"status":"not treated","reservation_date":"2018-02-01 09:05:06","uploaded":"2018-02-20 12:15:33","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":7.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181476.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181490","title":"LS from SA WG6: Reply LS to SA WG2 on default values for 5GS QoS averaging window","source":"SA WG6","contact":"Dominic Lazara","contact-id":49677,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 thanks SA WG2 for LS on default values for 5GS QoS averaging window for standardised 5QIs. Certain MC services such as MCPTT (QCI = 65) have short duration media transmissions (typically 3 to 5 seconds). As such, SA WG6 suggests the MCPTT service may benefit from an even shorter (less than the currently proposed 2000 ms) default average window size. Action: SA WG6 respectfully asks SA WG2 to take the above information into account.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15490,"status":"postponed","reservation_date":"2018-02-05 14:17:42","uploaded":"2018-02-05 15:20:40","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, CT WG1, SA WG4","lsoriginalls":"S6-180222","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181490.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181568","title":"Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the handling about the case when QoS targets can be fulfilled again to the PDU session modification procedure.","secretary_remarks":"Revision of approved DRAFTCR S2-181193. Revised to S2-182744.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15290,"status":"revised","reservation_date":"2018-02-12 14:18:15","uploaded":"2018-02-13 16:31:21","revisionof":"S2-181193","revisedto":"S2-182744","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":52.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181568.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181569","title":"Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Add the case when applicable, access network sends a new notification informing SMF that GFBR can be fulfilled again. And the SMF sends the new notification to PCF which will be sent to AF. 2. Update access independent event trigger 'QoS targets of the QoS Flow cannot be fulfilled' to 'QoS targets of the QoS Flow cannot be fulfilled or can be fulfilled again' .","secretary_remarks":"Revision of approved DRAFTCR S2-180309. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15310,"status":"agreed","reservation_date":"2018-02-12 14:18:17","uploaded":"2018-02-13 16:31:21","revisionof":"S2-180309","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":4.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180093","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181569.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181570","title":"Reflective QoS Timer transmission during PDU Session establishment","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the PCF(if applied) and SMF should provide Reflective QoS Timer during PDU Session establishment procedures.","secretary_remarks":"Revision of approved DRAFTCR S2-181155. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15320,"status":"agreed","reservation_date":"2018-02-12 14:18:18","uploaded":"2018-02-13 16:31:21","revisionof":"S2-181155","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":53.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180093","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181570.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181571","title":"Addition of Reflective QoS Timer in PDU session related policy information","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the Reflective QoS Timer as part of PDU Session related policy information..","secretary_remarks":"Revision of approved DRAFTCR S2-181156. Revised to S2-182731.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15330,"status":"revised","reservation_date":"2018-02-12 14:18:19","uploaded":"2018-02-13 16:31:21","revisionof":"S2-181156","revisedto":"S2-182731","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":5.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181571.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181572","title":"Corrections and clarifications for the usage of Packet Filter Set","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The direction of the packet filters in the Packet Filter Set is clarified in some places. For the description of the interaction with the UPF, SDF template is replaced by PDR. The QoS Flow mapping description is restructured and the corresponding figure updated.","secretary_remarks":"Revision of endorsed DRAFTCR S2-181152. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15350,"status":"agreed","reservation_date":"2018-02-12 14:18:20","uploaded":"2018-02-13 16:31:21","revisionof":"S2-181152","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":35.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180097","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181572.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181588","title":"Clarification on non-Standardized 5QI provided over N2 interface","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the 5QI is a mandatory parameter of a QoS profile only when the standardized or pre-configured 5QI is used. For a QoS Flow with a dynamically assigned 5QI, the dynamically assigned 5QI value is not used at AN, so it is also not needed to be signalled to AN in the QoS Profile.","secretary_remarks":"Noted in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15400,"status":"noted","reservation_date":"2018-02-13 02:33:43","uploaded":"2018-02-13 08:54:32","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":42.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181588.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181589","title":"Clarification on Notification Control","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify RAN may at any time decide to release the radio resources on which a QoS flow is mapped even notification control is enabled for this QoS flow, and send an indication to SMF.","secretary_remarks":"Merged into S2-182736.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15560,"status":"merged","reservation_date":"2018-02-13 02:39:20","uploaded":"2018-02-13 08:54:32","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":43.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181589.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181620","title":"Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.7.1.4,  refer to clause 5.7.6.1 for the definition of Packet Filter Set to ensure the consistency. Introduce 'match-all filter', and add a note that it's defined in TS 24.501. Clarify for unstructued PDU Session Type that default QoS rule does not contain an PFS In clause 5.7.1.5, add 'UL filter' for UL packet evaluation. In clause 5.7.6.1, add a note when the DL filter may be needed by the UE.","secretary_remarks":"Revision of approved DRAFTCR S2-181151. Revised to S2-182732.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15360,"status":"revised","reservation_date":"2018-02-13 14:21:49","uploaded":"2018-02-20 01:46:36","revisionof":"S2-181151","revisedto":"S2-182732","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":53.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181620.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181621","title":"Clean-up of Characteristics signalling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Reformulate text, so that all signalled characteristics parameters are included","secretary_remarks":"Revision of approved DRAFTCR S2-181194. Revised to S2-182733.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15380,"status":"revised","reservation_date":"2018-02-13 14:27:01","uploaded":"2018-02-20 01:46:36","revisionof":"S2-181194","revisedto":"S2-182733","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":54.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181621.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181626","title":"Traffic mapping information that disallows UL packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.11.1.1, clarify how SMF+PGW-C generates TFT for EPS bearer mapped from downly only QoS Flow.","secretary_remarks":"Revision of endorsed DRAFTCR S2-180221. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15410,"status":"agreed","reservation_date":"2018-02-13 14:47:37","uploaded":"2018-02-20 01:46:36","revisionof":"S2-180221","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":69.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180102","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181626.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181644","title":"Traffic mapping information that disallows UL packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 6.1.3.9, replace the reference specification from TS23.501 with TS23.502.","secretary_remarks":"Revision of not handled DRAFTCR S2-180222. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15760,"status":"agreed","reservation_date":"2018-02-13 22:24:05","uploaded":"2018-02-20 01:46:36","revisionof":"S2-180222","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":14.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180107","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181644.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181655","title":"QFI in N9","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add N9 reference point to relay RQI to the RAN.","secretary_remarks":"Revision of approved DRAFTCR S2-180246. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15420,"status":"agreed","reservation_date":"2018-02-14 07:30:14","uploaded":"2018-02-20 08:48:33","revisionof":"S2-180246","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":62.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180098","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181655.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181735","title":"Discussion on Max Data Burst Volume for GBR QoS Flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution introduces new characteristic to 5QI for GBR bearer.","secretary_remarks":"Noted in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15790,"status":"noted","reservation_date":"2018-02-16 20:01:19","uploaded":"2018-02-20 01:46:36","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_126_Montreal\/Docs\/S2-181735.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181736","title":"Introduction of Maximum Data Burst Volume for all GBR flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In order to clarify that RAN is not required to serve large bursts within the period of PDB, we propose that a maximum burst volume is defined for all GBR flows.  Proposal 1: Apply the characteristics parameter 'Maximum Data Burst Volume' for all GBR flows. Proposal 2: The default value of the maximum burst size is set to PDB*MFBR.","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15800,"status":"not treated","reservation_date":"2018-02-16 20:01:19","uploaded":"2018-02-20 14:21:31","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":79.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181736.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181737","title":"23.501: 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Introducing clarifications on PDB","secretary_remarks":"Revision of approved DRAFTCR S2-181281. Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15460,"status":"not treated","reservation_date":"2018-02-16 20:01:20","uploaded":"2018-02-20 01:46:36","revisionof":"S2-181281","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_126_Montreal\/Docs\/S2-181737.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181738","title":"Implications from UE Max Data Burst Volume enforcement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses implications from UE Max Data Burst Volume enforcement.","secretary_remarks":"LATE DOC: Rx 25\/02, 15:20. Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15810,"status":"not treated","reservation_date":"2018-02-16 20:01:20","uploaded":"2018-02-25 21:57:53","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_126_Montreal\/Docs\/S2-181738.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181739","title":"Clarification on Notification Control","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that for GBR QoS Flows with Notification Control enabled, RAN may remove the resources for that QoS Flow when RAN internal conditions, e.g. RLF, require it.","secretary_remarks":"Merged into S2-182855.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15570,"status":"merged","reservation_date":"2018-02-16 20:01:20","uploaded":"2018-02-20 01:46:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":80.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181739.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181741","title":"Draft LS reply to LS from RAN WG2: LS on QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Proposed reply LS to RAN WG2 on aspects of Notification Control","secretary_remarks":"Response to S2-181448. Revised to S2-182735.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15630,"status":"revised","reservation_date":"2018-02-16 20:01:22","uploaded":"2018-02-20 01:46:36","revisionof":"","revisedto":"S2-182735","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181741.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181759","title":"5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) PDB\/PER - clarify the condition for adding the packet to the PER. Current text is a bit ambiguous as it uses GBR as a boundary condition. It is ambiguous for implementation to determine the exact condition for considering the packets as lost and adding it to the PER. 2) Maximum Data Burst Volume - State the conditions for enforcing it in the UE for UL and UPF for DL. Otherwise, there is a possibility that huge amount of packets are sent \/ received causing the RAN not to be able to meet the necessary latency and relaibility requirement for delay critical 5QIs. 3) 5QI table - remove the 1ms note as it is not necessary to assume 1ms backhaul delay just for certain set of 5QIs, also removing reference to PCEF. 4) QoS characeteristics for Non-standardized 5QI is expected to be provided dynamically over signaling. Thus the minimum allowed ranges need not be specified. It is proposed to simply remove the EN. Revision: 1) Remove UPF enforcement option for Max. Data Burst","secretary_remarks":"Revision of revised DRAFTCR S2-181195 (the revision in S2-181281 was approved). Revised to S2-182745.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15430,"status":"revised","reservation_date":"2018-02-18 01:44:36","uploaded":"2018-02-20 14:31:19","revisionof":"S2-181195","revisedto":"S2-182745","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":87.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181759.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181760","title":"QoS Notification control and Release","source":"Nokia, Nokia Shanghai Bell, Mediatek","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN can release the AN resources when notification control is enabled, then it shall notify the SMF that the AN resources to which the QoS flow is mapped to is released. If the AN decides to keep the AN resources when RAN cannot fulfil the GBR resources when the notification control is enabled, then the AN shall notify the SMF and keep trying to fulfill the requested QoS. Thus both implementation options are allowed.  It is proposed to make them sequential to avoid the standardized 5QI value hindering support for certain functionality (i.e. efficient user plane processing for option 1, reflective QoS etc)","secretary_remarks":"Revised, merging S2-181589, to S2-182736.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15580,"status":"revised","reservation_date":"2018-02-18 01:44:37","uploaded":"2018-02-20 14:31:19","revisionof":"","revisedto":"S2-182736","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":88.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181760.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181761","title":"Reply LS on QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on QoS","secretary_remarks":"Response to S2-181448. Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15660,"status":"not treated","reservation_date":"2018-02-18 01:44:38","uploaded":"2018-02-20 14:31:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181761.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181775","title":"QoS Notification control and Release - TS 23.502","source":"Nokia, Nokia Shanghai Bell, Mediatek","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN can release the AN resources when notification control is enabled, then it shall notify the SMF that the AN resources to which the QoS flow is mapped to is released. If the AN decides to keep the AN resources when RAN cannot fulfil the GBR resources when the notification control is enabled, then the AN shall notify the SMF and keep trying to fulfill the requested QoS. Thus both implementation options are allowed.  It is proposed to make them sequential to avoid the standardized 5QI value hindering support for certain functionality (i.e. efficient user plane processing for option 1, reflective QoS etc)","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15670,"status":"not treated","reservation_date":"2018-02-18 02:18:52","uploaded":"2018-02-20 14:31:19","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":119.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181775.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181839","title":"LS from SA WG4: Reply LS on default values for 5GS QoS averaging window for standardised 5QIs","source":"SA WG4","contact":"Ozgur Oyman","contact-id":44803,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG2 for confirming SA WG4's interpretation of the averaging window for active speech and DTX, and sharing the information on the signalling of the MaxPLR as part of the QoS Profile. Regarding SA WG2's question on whether there is any plan to provide some guidelines or examples on determining the MaxPLR value at PCF, SA WG4 would like to acknowledge that this is indeed part of the SA WG4 study FS_eVoLP. In particular, Table 5.1 of the attached TR 26.959 contains MaxPLR operating points for various codec configurations. Moreover, in clause 7.2.1 of TR 26.959, further guidance on how to set MaxPLR at the PCRF is provided based on the availability of the newly introduced 'adapt' parameter in the SDP. In addition, SA WG4 is also investigating and plans to document in TR 26.959 any MaxPLR recommendations taking into account the impact of application layer redundancy. Action: SA WG4 kindly asks SA WG2 to consider the information above.","secretary_remarks":"Noted in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15500,"status":"noted","reservation_date":"2018-02-19 09:33:19","uploaded":"2018-02-19 10:27:56","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, RAN WG2, SA WG6","lsoriginalls":"S4-180254","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181839.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181841","title":"LS from SA WG4: LS on QoS for Live Uplink Streaming (FLUS)","source":"SA WG4","contact":"Thorsten Lohmar","contact-id":59317,"tdoctype":"LS in","for":"Action","abstract":"As part of Release 15, SA WG4 has specified the Framework for Live Uplink Streaming (FLUS, TS 26.238), which can be beneficial e.g. for a professional media production vertical, in particular when the EPS or 5GS can ensure a certain QoS. Professional media production typically requires fairly high media bitrates at rather (configurable) low latencies. The service may compromise on latency in order to increase the media quality at a given bitrate. Note that the service bitrate for video services may vary to a high degree, since the compression level depends, for example, on the movement within the scene. In the following discussion, we assume a bitrate adaptive FLUS solution, where the FLUS source can adjust the service bitrate to the currently measured link bitrate. The figure below illustrates the desired video quality properties (and the resulting bitrates) and the resulting GFBR as an example. {...} The service bitrate of the video should be typically and preferably in the area of t","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15860,"status":"postponed","reservation_date":"2018-02-19 09:33:19","uploaded":"2018-02-19 10:37:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"-","lsoriginalls":"S4-180301","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181841.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181902","title":"Discussion on options to limit the size of QFI to 6 bits in RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses alternatives for limiting the QFI size to 6 bits in RAN.","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15530,"status":"not treated","reservation_date":"2018-02-19 13:34:53","uploaded":"2018-02-20 01:46:36","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_126_Montreal\/Docs\/S2-181902.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181903","title":"Use of priority parameters in scheduling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When configured by the operator, ARP PL is used to prioritize sufficient resources in scheduling to fulfil the QoS requirements. In that case, 5QI PL is used to define the priority to get more resources once GFBR is fulfilled.","secretary_remarks":"This was left for off-line discussion and revised in S2-182737. Revised to S2-182737.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15770,"status":"revised","reservation_date":"2018-02-19 13:34:53","uploaded":"2018-02-20 01:46:36","revisionof":"","revisedto":"S2-182737","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":117.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-181903.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181904","title":"[DRAFT] LS reply to LS from SA WG4: QoS for Live Uplink Streaming (FLUS)","source":"Ericsson","contact":"Paul Schliwa-Bertling","contact-id":37748,"tdoctype":"LS out","for":"Approval","abstract":"Proposed reply LS to SA WG2 on how to define priority to get more than GFBR","secretary_remarks":"Response to S2-181448. LATE DOC: Rx 22\/02, 19:30. Revised to S2-182742.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15870,"status":"revised","reservation_date":"2018-02-19 13:34:54","uploaded":"2018-02-22 18:41:27","revisionof":"","revisedto":"S2-182742","release":"Rel-15","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_126_Montreal\/Docs\/S2-181904.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182021","title":"Correction for the usage of RQI bit","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Change RQI bit instances in the subclause to RQI","secretary_remarks":"Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15470,"status":"agreed","reservation_date":"2018-02-19 20:54:41","uploaded":"2018-02-20 14:08:56","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":133.0,"crrevision":"","crcategory":"D","tsg_crp":"SP-180096","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182021.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182036","title":"Clarifications for QoS Framework","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed an note on per SDF enforcement as it is misleading (MFBR is not per SDF) Clarification on MFBR and GFBR role for GBR flows, Clarified what are the compliance requirements for QoS flows, and possible enforcement points. Calrified the MDBV applies only to delay critical Resource type Moved E and F 5QI to delay critical GBR resource type Renumbered the 5QIs so letters are not used (good to have uniform way to identify 5QIs for our Stage 3 colleagues) Adjusted the PER fo a delay critical 5QI to be aligned to stage 1 new requirement (from 10^-6 to 10^-5). Added the possibility to signal the PDB to the RAN.","secretary_remarks":"Revised to S2-182741.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15820,"status":"revised","reservation_date":"2018-02-20 00:14:00","uploaded":"2018-02-20 14:31:19","revisionof":"","revisedto":"S2-182741","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":134.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182036.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182077","title":"Removal of notification control","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposes to remove Notification Control functionality","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15680,"status":"not treated","reservation_date":"2018-02-20 03:24:15","uploaded":"2018-02-20 13:02:42","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":142.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182077.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182079","title":"Removal of notification control","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposes to remove Notification Control functionality","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15690,"status":"not treated","reservation_date":"2018-02-20 03:28:55","uploaded":"2018-02-20 13:02:55","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":201.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182079.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182184","title":"Temporary restriction of Reflective QoS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to to clarify that UE shall be able to indicate to the network: 1) the number of supported packet filters for Reflective QoS upon PDU Session establishment 2) that it is unable to create additional Reflective QoS rules for a specific PDU Session due to insufficient resources (using PDU Session Modification) 3) that it is able to resume the creation of additional Reflective QoS rules for a specific PDU Session (using PDU Session Modification)","secretary_remarks":"This was left for off-line discussion. This was postponed in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15720,"status":"postponed","reservation_date":"2018-02-20 09:24:08","uploaded":"2018-02-20 14:24:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":169.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182184.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182185","title":"Temporary restriction of Reflective QoS","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to to clarify that UE shall be able to indicate to the network: 1) the number of supported packet filters for Reflective QoS upon PDU Session establishment 2) that it is unable to use Reflective QoS for a specific PDU Session due to insufficient resources (using PDU Session Modification) 3) that it is able to resume the use of Reflective QoS for a specific PDU Session (using PDU Session Modification)","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15740,"status":"not treated","reservation_date":"2018-02-20 09:26:13","uploaded":"2018-02-20 14:24:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":224.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182185.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182186","title":"Discussion of impacts of 6 bits for QFI","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"discussion","for":"Discussion","abstract":"Discussion of the impacts of having 6 bits for the QFI on the use of 5QI for the QFI value","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15540,"status":"not treated","reservation_date":"2018-02-20 09:30:01","uploaded":"2018-02-20 09:49:43","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182186.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182194","title":"Remove QFI equals 5QI option","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The option to use the 5QI as the QFI is removed.","secretary_remarks":"Revised to S2-182734.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15510,"status":"revised","reservation_date":"2018-02-20 09:33:49","uploaded":"2018-02-20 09:49:43","revisionof":"","revisedto":"S2-182734","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":175.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182194.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182198","title":"Allow removal of QoS Flow by RAN after notification sent to SMF","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The text is changed to state that the RAN may decide to release the QoS Flow.","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15700,"status":"not treated","reservation_date":"2018-02-20 09:43:24","uploaded":"2018-02-20 09:49:43","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":176.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182198.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182731","title":"Addition of Reflective QoS Timer in PDU session related policy information","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the Reflective QoS Timer as part of PDU Session related policy information..","secretary_remarks":"Revision of S2-181571. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15340,"status":"agreed","reservation_date":"2018-02-28 02:03:41","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181571","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":5.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180093","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182731.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182732","title":"Traffic mapping information that disallows UL packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.7.1.4,  refer to clause 5.7.6.1 for the definition of Packet Filter Set to ensure the consistency. Introduce 'match-all filter', and add a note that it's defined in TS 24.501. Clarify for unstructued PDU Session Type that default QoS rule does not contain an PFS In clause 5.7.1.5, add 'UL filter' for UL packet evaluation. In clause 5.7.6.1, add a note when the DL filter may be needed by the UE.","secretary_remarks":"Revision of S2-181620. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15370,"status":"agreed","reservation_date":"2018-02-28 02:03:42","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181620","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":53.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180098","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182732.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182733","title":"Clean-up of Characteristics signalling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Reformulate text, so that all signalled characteristics parameters are included","secretary_remarks":"Revision of S2-181621. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15390,"status":"agreed","reservation_date":"2018-02-28 02:03:44","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181621","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":54.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180098","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182733.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182734","title":"Remove QFI equals 5QI option","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The option to use the 5QI as the QFI is removed.","secretary_remarks":"Revision of S2-182194. Withdrawn (not provided).","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15520,"status":"withdrawn","reservation_date":"2018-02-28 02:03:45","uploaded":null,"revisionof":"S2-182194","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":175.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182735","title":"[DRAFT] LS reply to LS from RAN WG2: LS on QoS","source":"SA WG2","contact":"Paul Schliwa-Bertling","contact-id":37748,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, CT WG1, RAN WG3","secretary_remarks":"Revision of S2-181741. Revised to S2-182856.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15640,"status":"revised","reservation_date":"2018-02-28 02:03:46","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181741","revisedto":"S2-182856","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182735.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182736","title":"QoS Notification control and Release","source":"Nokia, Nokia Shanghai Bell, Mediatek","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN can release the AN resources when notification control is enabled, then it shall notify the SMF that the AN resources to which the QoS flow is mapped to is released. If the AN decides to keep the AN resources when RAN cannot fulfil the GBR resources when the notification control is enabled, then the AN shall notify the SMF and keep trying to fulfill the requested QoS. Thus both implementation options are allowed.  It is proposed to make them sequential to avoid the standardized 5QI value hindering support for certain functionality (i.e. efficient user plane processing for option 1, reflective QoS etc)","secretary_remarks":"Revision of S2-181760, merging S2-181589. Revised off-line, merging S2-181739, to S2-182855.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15590,"status":"revised","reservation_date":"2018-02-28 02:03:46","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181760","revisedto":"S2-182855","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":88.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182736.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182737","title":"Use of priority parameters in scheduling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When configured by the operator, ARP PL is used to prioritize sufficient resources in scheduling to fulfil the QoS requirements. In that case, 5QI PL is used to define the priority to get more resources once GFBR is fulfilled.","secretary_remarks":"Revision of S2-181903. Withdrawn (not provided).","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15780,"status":"withdrawn","reservation_date":"2018-02-28 02:03:47","uploaded":null,"revisionof":"S2-181903","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":117.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182738","title":"Discussion on Reflective QoS","source":"Drafting group","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Endorsement","abstract":"Background:  (S2-181473) S2-181475, S2-181476 S2-181484, S2-181485  Issues  Nr. of packet filters supported by the UE  Alt 1: Yes (with LS to CT WG1)  Alt 2: No  RQoS on a PDU Session basis  RQoS Support not indicated for all PDU Session establishments  Temporary Restriction of RQoS  Restriction ON: PDU Session Modification  UE behaviour during restriction   Alt 1: Existing UE-derived QoS rules continue   Alt 2: UE Implementation  Restriction OFF   Alt 1: Silent   Alt 2: PDU Session Modification.","secretary_remarks":"Revised to S2-182743.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15270,"status":"revised","reservation_date":"2018-02-28 02:03:48","uploaded":"2018-03-05 11:37:53","revisionof":"","revisedto":"S2-182743","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182738.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182741","title":"Clarifications for QoS Framework","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed an note on per SDF enforcement as it is misleading (MFBR is not per SDF) Clarification on MFBR and GFBR role for GBR flows, Clarified what are the compliance requirements for QoS flows, and possible enforcement points. Calrified the MDBV applies only to delay critical Resource type Moved E and F 5QI to delay critical GBR resource type Renumbered the 5QIs so letters are not used (good to have uniform way to identify 5QIs for our Stage 3 colleagues) Adjusted the PER fo a delay critical 5QI to be aligned to stage 1 new requirement (from 10^-6 to 10^-5). Added the possibility to signal the PDB to the RAN.","secretary_remarks":"Revision of S2-182036. Revised to S2-182858.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15830,"status":"revised","reservation_date":"2018-02-28 02:03:49","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182036","revisedto":"S2-182858","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":134.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182741.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182742","title":"[DRAFT] LS reply to LS from SA WG4: QoS for Live Uplink Streaming (FLUS)","source":"Ericsson","contact":"Paul Schliwa-Bertling","contact-id":37748,"tdoctype":"LS out","for":"Approval","abstract":"Proposed reply LS to SA WG2 on how to define priority to get more than GFBR","secretary_remarks":"Revision of S2-181904. Withdrawn (not provided).","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15880,"status":"withdrawn","reservation_date":"2018-02-28 02:03:50","uploaded":null,"revisionof":"S2-181904","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182743","title":"Discussion on Reflective QoS","source":"Drafting group","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Endorsement","abstract":"Background:  (S2-181473) S2-181475, S2-181476 S2-181484, S2-181485  Issues  Nr. of packet filters supported by the UE  Alt 1: Yes (with LS to CT WG1)  Alt 2: No  RQoS on a PDU Session basis  RQoS Support not indicated for all PDU Session establishments  Temporary Restriction of RQoS  Restriction ON: PDU Session Modification  UE behaviour during restriction   Alt 1: Existing UE-derived QoS rules continue   Alt 2: UE Implementation  Restriction OFF   Alt 1: Silent   Alt 2: PDU Session Modification.","secretary_remarks":"Revision of S2-182738. Proposal endorsed.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15280,"status":"endorsed","reservation_date":"2018-02-28 02:26:49","uploaded":"2018-03-05 11:37:53","revisionof":"S2-182738","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182743.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182744","title":"Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the handling about the case when QoS targets can be fulfilled again to the PDU session modification procedure.","secretary_remarks":"Revision of S2-181568. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15300,"status":"agreed","reservation_date":"2018-02-28 02:26:50","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181568","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":52.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180093","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182744.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182745","title":"5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Telecom Italia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) PDB\/PER - clarify the condition for adding the packet to the PER. Current text is a bit ambiguous as it uses GBR as a boundary condition. It is ambiguous for implementation to determine the exact condition for considering the packets as lost and adding it to the PER. 2) Maximum Data Burst Volume - State the conditions for enforcing it in the UE for UL and UPF for DL. Otherwise, there is a possibility that huge amount of packets are sent \/ received causing the RAN not to be able to meet the necessary latency and relaibility requirement for delay critical 5QIs. 3) 5QI table - remove the 1ms note as it is not necessary to assume 1ms backhaul delay just for certain set of 5QIs, also removing reference to PCEF. 4) QoS characeteristics for Non-standardized 5QI is expected to be provided dynamically over signaling. Thus the minimum allowed ranges need not be specified. It is proposed to simply remove the EN. Revision: 1) Remove UPF enforcement option for Max. Data Burst","secretary_remarks":"Revision of S2-181759. Revised to S2-182854.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15440,"status":"revised","reservation_date":"2018-02-28 02:26:53","uploaded":"2018-03-05 11:37:53","revisionof":"S2-181759","revisedto":"S2-182854","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":87.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182745.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182854","title":"5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) PDB\/PER - clarify the condition for adding the packet to the PER. Current text is a bit ambiguous as it uses GBR as a boundary condition. It is ambiguous for implementation to determine the exact condition for considering the packets as lost and adding it to the PER. 2) Maximum Data Burst Volume - State the conditions for enforcing it in the UE for UL and UPF for DL. Otherwise, there is a possibility that huge amount of packets are sent \/ received causing the RAN not to be able to meet the necessary latency and relaibility requirement for delay critical 5QIs. 3) 5QI table - remove the 1ms note as it is not necessary to assume 1ms backhaul delay just for certain set of 5QIs, also removing reference to PCEF. 4) QoS characeteristics for Non-standardized 5QI is expected to be provided dynamically over signaling. Thus the minimum allowed ranges need not be specified. It is proposed to simply remove the EN. Revision: 1) Remove UPF enforcement option for Max. Data Burst","secretary_remarks":"Revision of S2-182745. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15450,"status":"agreed","reservation_date":"2018-03-02 14:38:56","uploaded":"2018-03-05 14:47:55","revisionof":"S2-182745","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":87.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180099","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182854.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182855","title":"QoS Notification control and Release","source":"Nokia, Nokia Shanghai Bell, Mediatek, Ericsson, CATT","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN can release the AN resources when notification control is enabled, then it shall notify the SMF that the AN resources to which the QoS flow is mapped to is released. If the AN decides to keep the AN resources when RAN cannot fulfil the GBR resources when the notification control is enabled, then the AN shall notify the SMF and keep trying to fulfill the requested QoS. Thus both implementation options are allowed.  It is proposed to make them sequential to avoid the standardized 5QI value hindering support for certain functionality (i.e. efficient user plane processing for option 1, reflective QoS etc)","secretary_remarks":"Revision of S2-182736, merging S2-181739. Revised to S2-182859.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15600,"status":"revised","reservation_date":"2018-03-02 14:38:57","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182736","revisedto":"S2-182859","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":88.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182855.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182856","title":"LS reply to LS from RAN WG2: LS on QoS","source":"SA WG2","contact":"Paul Schliwa-Bertling","contact-id":37748,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, CT WG1, RAN WG3. Attachment: TS 23.501 CR0088 (S2-182862)","secretary_remarks":"Revision of S2-182735. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15650,"status":"approved","reservation_date":"2018-03-02 14:38:58","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182735","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-181448","lsto":"RAN WG2, CT WG1, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182856.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182858","title":"Clarifications for QoS Framework","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed an note on per SDF enforcement as it is misleading (MFBR is not per SDF) Clarification on MFBR and GFBR role for GBR flows, Clarified what are the compliance requirements for QoS flows, and possible enforcement points. Calrified the MDBV applies only to delay critical Resource type Moved E and F 5QI to delay critical GBR resource type Renumbered the 5QIs so letters are not used (good to have uniform way to identify 5QIs for our Stage 3 colleagues) Adjusted the PER fo a delay critical 5QI to be aligned to stage 1 new requirement (from 10^-6 to 10^-5). Added the possibility to signal the PDB to the RAN.","secretary_remarks":"Revision of S2-182741. Revised to S2-182863.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15840,"status":"revised","reservation_date":"2018-03-02 14:38:59","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182741","revisedto":"S2-182863","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":134.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182858.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182859","title":"QoS Notification control and Release","source":"Nokia, Nokia Shanghai Bell, Mediatek, Ericsson, CATT","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN can release the AN resources when notification control is enabled, then it shall notify the SMF that the AN resources to which the QoS flow is mapped to is released. If the AN decides to keep the AN resources when RAN cannot fulfil the GBR resources when the notification control is enabled, then the AN shall notify the SMF and keep trying to fulfill the requested QoS. Thus both implementation options are allowed.  It is proposed to make them sequential to avoid the standardized 5QI value hindering support for certain functionality (i.e. efficient user plane processing for option 1, reflective QoS etc)","secretary_remarks":"Revision of S2-182855. Revised to S2-182862.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15610,"status":"revised","reservation_date":"2018-03-02 14:39:00","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182855","revisedto":"S2-182862","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":88.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182859.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182862","title":"QoS Notification control and Release","source":"Nokia, Nokia Shanghai Bell, Mediatek, Ericsson, CATT","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN can release the AN resources when notification control is enabled, then it shall notify the SMF that the AN resources to which the QoS flow is mapped to is released. If the AN decides to keep the AN resources when RAN cannot fulfil the GBR resources when the notification control is enabled, then the AN shall notify the SMF and keep trying to fulfill the requested QoS. Thus both implementation options are allowed.  It is proposed to make them sequential to avoid the standardized 5QI value hindering support for certain functionality (i.e. efficient user plane processing for option 1, reflective QoS etc)","secretary_remarks":"Revision of S2-182859. Agreed in parallel session. Block approved.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15620,"status":"agreed","reservation_date":"2018-03-02 14:39:01","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182859","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":88.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180099","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182862.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182863","title":"Clarifications for QoS Framework","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed an note on per SDF enforcement as it is misleading (MFBR is not per SDF) Clarification on MFBR and GFBR role for GBR flows, Clarified what are the compliance requirements for QoS flows, and possible enforcement points. Calrified the MDBV applies only to delay critical Resource type Moved E and F 5QI to delay critical GBR resource type Renumbered the 5QIs so letters are not used (good to have uniform way to identify 5QIs for our Stage 3 colleagues) Adjusted the PER fo a delay critical 5QI to be aligned to stage 1 new requirement (from 10^-6 to 10^-5). Added the possibility to signal the PDB to the RAN.","secretary_remarks":"Revision of S2-182858. Revised to S2-182992.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15850,"status":"revised","reservation_date":"2018-03-02 14:39:02","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182858","revisedto":"S2-182992","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":134.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182863.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-182992","title":"Clarifications for QoS Framework","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed an note on per SDF enforcement as it is misleading (MFBR is not per SDF) Clarification on MFBR and GFBR role for GBR flows, Clarified what are the compliance requirements for QoS flows, and possible enforcement points. Calrified the MDBV applies only to delay critical Resource type Moved E and F 5QI to delay critical GBR resource type Renumbered the 5QIs so letters are not used (good to have uniform way to identify 5QIs for our Stage 3 colleagues) Adjusted the PER fo a delay critical 5QI to be aligned to stage 1 new requirement (from 10^-6 to 10^-5). Added the possibility to signal the PDB to the RAN.","secretary_remarks":"Revision of S2-182863. Revised to S2-183013.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15851,"status":"revised","reservation_date":"2018-03-05 10:37:28","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182863","revisedto":"S2-183013","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":134.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-182992.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-183013","title":"Clarifications for QoS Framework","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removed an note on per SDF enforcement as it is misleading (MFBR is not per SDF) Clarification on MFBR and GFBR role for GBR flows, Clarified what are the compliance requirements for QoS flows, and possible enforcement points. Calrified the MDBV applies only to delay critical Resource type Moved E and F 5QI to delay critical GBR resource type Renumbered the 5QIs so letters are not used (good to have uniform way to identify 5QIs for our Stage 3 colleagues) Adjusted the PER fo a delay critical 5QI to be aligned to stage 1 new requirement (from 10^-6 to 10^-5). Added the possibility to signal the PDB to the RAN.","secretary_remarks":"Revision of S2-182992. This CR was agreed.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15852,"status":"agreed","reservation_date":"2018-03-05 10:40:39","uploaded":"2018-03-05 11:37:54","revisionof":"S2-182992","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":134.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-180099","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_126_Montreal\/Docs\/S2-183013.zip","group":"S2","meeting":"S2-126","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]