[{"name":"S2-180036","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":"Action","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":"This LS was postponed. Revised at S2#126 in S2-181425.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14140,"status":"revised","reservation_date":"2017-12-19 11:54:36","uploaded":"2017-12-19 11:58:34","revisionof":"","revisedto":"S2-181425","release":"Rel-15","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_125_Gothenburg\/Docs\/S2-180036.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180219","title":"Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This paper proposes solutions how to handle DL only QoS Flow in 5GS","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14180,"status":"noted","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:38:49","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_125_Gothenburg\/Docs\/S2-180219.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180220","title":"23.501: Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In clause 5.7.1.4, refer to clause 5.7.6.1 for the definition of Packet Filter Set to ensure the consistency. In clause 5.7.1.5, clarify that a QoS rule containing Packet Filter Set with no UL filter means no UL packets allowed for the QoS Flow associated with that QoS rule. In clause 5.7.6.1, add a note when the DL filter may be needed by the UE.","secretary_remarks":"Revised to S2-181151.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14190,"status":"revised","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:38:49","revisionof":"","revisedto":"S2-181151","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180220.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180221","title":"23.502: Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In clause 4.11.1.1, clarify how SMF+PGW-C generates TFT for EPS bearer mapped from downly only QoS Flow.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14230,"status":"endorsed","reservation_date":"2018-01-14 14:36:23","uploaded":"2018-01-16 13:38:49","revisionof":"","revisedto":"S2-181626","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180221.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180246","title":"23.501: QFI in N9","source":"Samsung","contact":"Jicheol Lee","contact-id":51554,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add N9 reference point to relay RQI to the RAN.","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":14390,"status":"approved","reservation_date":"2018-01-15 01:55:46","uploaded":"2018-01-16 07:04:46","revisionof":"","revisedto":"S2-181655","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180246.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180252","title":"23.501: QoS rule generation","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Clarify if dynamic PCC is deployed, each QoS rule provided by SMF is generated from a PCC rule. The default QoS rule is generated by SMF based on the authorized default 5QI and ARP received from PCF, if a Packet Filter Set is included in the default QoS rule, the SMF may set the Packet Filter Set based on local policy or by the instruction of PCF.","secretary_remarks":"Merged into S2-181152.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14290,"status":"merged","reservation_date":"2018-01-15 05:44:54","uploaded":"2018-01-16 11:52:46","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180252.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180283","title":"23.501: Clarification on usage of additional Priority Level","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The additional Priority Level parameter together with the standardized 5QI is replaced with ARP priority level.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14490,"status":"noted","reservation_date":"2018-01-15 09:26:26","uploaded":"2018-01-16 13:10:37","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180283.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180308","title":"23.502: Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","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":"Revised to S2-181193.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14400,"status":"revised","reservation_date":"2018-01-15 13:02:47","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181193","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180308.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180309","title":"23.503: Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","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":"Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14420,"status":"approved","reservation_date":"2018-01-15 13:02:47","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181569","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180309.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180310","title":"23.502: Reflective QoS Timer transmission during PDU Session establishment","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","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":"Revised to S2-181155.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14300,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181155","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180310.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180311","title":"23.503: Addition of Reflective QoS Timer in PDU session related policy information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the Reflective QoS Timer as part of PDU Session related policy information..","secretary_remarks":"Revised to S2-181156.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14320,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181156","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180311.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180312","title":"23.501: Corrections and clarifications for the usage of Packet Filter Set","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","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":"Revised to S2-181152, merging S2-180252.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14210,"status":"revised","reservation_date":"2018-01-15 13:02:48","uploaded":"2018-01-16 14:11:54","revisionof":"","revisedto":"S2-181152","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180312.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180366","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","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14340,"status":"noted","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09: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_125_Gothenburg\/Docs\/S2-180366.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180367","title":"23.501: Draft CR 23.501 Number of QoS rules and packet filters","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Number of concurrent QoS rules and packet filters is defined through a ref. to TS 24.501.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14350,"status":"noted","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180367.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180368","title":"23.501: Draft CR 23.501 Reflective QoS support indication at PDU Session Establishment \/ Modification","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","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 limit the further use of RQoS for a PDU Session.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14360,"status":"postponed","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180368.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180369","title":"23.502: Draft CR 23.502 Reflective QoS support indication at PDU Session Establishment \/ Modification","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The UE triggers a PDU Session Modification to limit the further use of RQoS for a PDU Session.","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14370,"status":"not treated","reservation_date":"2018-01-15 14:05:38","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180369.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180371","title":"23.501: Draft CR 23.501 Corrections to RQoS logic when receiving DL packet with RQI","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"draftCR","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":14380,"status":"approved","reservation_date":"2018-01-15 14:26:27","uploaded":"2018-01-16 13:09:53","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180371.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180421","title":"Default QoS Rule discussion","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"Discussion on the Default QoS implications","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14240,"status":"noted","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 15:04:15","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180421.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180422","title":"23.501: Introduction of 'Maximum Data Burst Volume for all GBR flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In last meeting it was agreed that a new QoS characteristics Parameter, Maximum Data Burst Volume', is introduced for GBR flows with PDB<20 ms. However, there is also a need to specify what data volume can be served for GBR flows with higher PDB. In S2-178049 values for Default Averaging Window are proposed for the standardized GBR 5QI's. The values are rather large, 2, and 3 s long, which correspond to unreasonable high requirements for the instantaneous bitrate in RAN. The instantaneous bitrate needed in RAN in order to serve the largest bursts that are within the GFBR requirement can be estimated by: GFBR*AW\/PDB The table below shows the largest burst size within the GFBR requirement, and the instantaneous bitrate that would be required in RAN to serve it within the PDB. 5QI PDB Averaging Window (AW) Largest data burst within GFBR Instantaneous bitrate 1 100 ms 2 s 2 * GFBR 20 * GFBR 2 150 ms 2 s 2 * GFBR 13 * GFBR 3 50 ms 3 s 3 * GFBR 60 * GFBR 4 300 ms 3 s 3 * G","secretary_remarks":"Revised to S2-181150.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14150,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:45:17","revisionof":"","revisedto":"S2-181150","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180422.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180423","title":"23.501: ARP usage clean-ups","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The characteristics may be signalled, in two cases: - A special 5QI is used where all characteristics are signalled. - For any 5QI, the parameters priority, Averaging window, and\/or Maximum Data Burst Volume may be signalled in order to override the default values. In section 5.7.1.2 it is stated: 'The 5QI value may indicate that a QoS flow have signalled QoS characteristics, and if so, the QoS characteristics are included in the QoS profile.' This text does not cover the second alternative, and should be re-formulated in order to avoid confusion. Proposal 1: Reformulate text, so that all signaled characteristics parameters are included","secretary_remarks":"Revised to S2-181194.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14430,"status":"revised","reservation_date":"2018-01-15 17:00:06","uploaded":"2018-01-16 14:45:17","revisionof":"","revisedto":"S2-181194","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180423.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180452","title":"23.501: Correction for the usage of RQI bit","source":"InterDigital Inc.","contact":"Xiaoyan Shi","contact-id":72162,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: It replaces the conditions whether RQI is included to conditions whether RQI bit is set.","secretary_remarks":"Endorsed in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14450,"status":"endorsed","reservation_date":"2018-01-15 21:28:07","uploaded":"2018-01-16 14:36:58","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180452.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180474","title":"23.501: 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","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.","secretary_remarks":"Revised to S2-181195.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14460,"status":"revised","reservation_date":"2018-01-15 23:44:35","uploaded":"2018-01-16 14:57:01","revisionof":"","revisedto":"S2-181195","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180474.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180770","title":"23.501: Default QoS Rule cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: A note that UE does not need to know which QoS rule is","secretary_remarks":"LATE DOC: Rx 19\/01, 22:30 Revised to S2-181153.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14250,"status":"revised","reservation_date":"2018-01-17 13:42:29","uploaded":"2018-01-20 06:52:09","revisionof":"","revisedto":"S2-181153","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180770.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-180771","title":"23.502: Default QoS Rule cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introducing sending an indication which EBI refer to the default EPS bearer","secretary_remarks":"LATE DOC: Rx 19\/01, 22:30 Revised to S2-181154.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14270,"status":"revised","reservation_date":"2018-01-17 13:42:29","uploaded":"2018-01-20 06:52:09","revisionof":"","revisedto":"S2-181154","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-180771.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181150","title":"23.501: Introduction of 'Maximum Data Burst Volume for all GBR flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In last meeting it was agreed that a new QoS characteristics Parameter, Maximum Data Burst Volume', is introduced for GBR flows with PDB<20 ms. However, there is also a need to specify what data volume can be served for GBR flows with higher PDB. In S2-178049 values for Default Averaging Window are proposed for the standardized GBR 5QI's. The values are rather large, 2, and 3 s long, which correspond to unreasonable high requirements for the instantaneous bitrate in RAN. The instantaneous bitrate needed in RAN in order to serve the largest bursts that are within the GFBR requirement can be estimated by: GFBR*AW\/PDB The table below shows the largest burst size within the GFBR requirement, and the instantaneous bitrate that would be required in RAN to serve it within the PDB. 5QI PDB Averaging Window (AW) Largest data burst within GFBR Instantaneous bitrate 1 100 ms 2 s 2 * GFBR 20 * GFBR 2 150 ms 2 s 2 * GFBR 13 * GFBR 3 50 ms 3 s 3 * GFBR 60 * GFBR 4 300 ms 3 s 3 * G","secretary_remarks":"Revision of S2-180422. Revised to S2-181196.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14160,"status":"revised","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180422","revisedto":"S2-181196","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181150.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181151","title":"23.501: Traffic mapping information that disallows uplink packets","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In clause 5.7.1.4, refer to clause 5.7.6.1 for the definition of Packet Filter Set to ensure the consistency. In clause 5.7.1.5, clarify that a QoS rule containing Packet Filter Set with no UL filter means no UL packets allowed for the QoS Flow associated with that QoS rule. In clause 5.7.6.1, add a note when the DL filter may be needed by the UE.","secretary_remarks":"Revision of S2-180220. Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14200,"status":"approved","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180220","revisedto":"S2-181620","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181151.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181152","title":"23.501: Corrections and clarifications for the usage of Packet Filter Set","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","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 S2-180312, merging S2-180252. Endorsed in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14220,"status":"endorsed","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180312","revisedto":"S2-181572","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181152.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181153","title":"23.501: Default QoS Rule cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: A note that UE does not need to know which QoS rule is","secretary_remarks":"Revision of S2-180770. WITHDRAWN","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14260,"status":"withdrawn","reservation_date":"2018-01-23 16:34:30","uploaded":null,"revisionof":"S2-180770","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181154","title":"23.502: Default QoS Rule cleanup","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Introducing sending an indication which EBI refer to the default EPS bearer","secretary_remarks":"Revision of S2-180771. WITHDRAWN","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14280,"status":"withdrawn","reservation_date":"2018-01-23 16:34:30","uploaded":null,"revisionof":"S2-180771","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181155","title":"23.502: Reflective QoS Timer transmission during PDU Session establishment","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","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 S2-180310. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14310,"status":"approved","reservation_date":"2018-01-23 16:34:30","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180310","revisedto":"S2-181570","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181155.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181156","title":"23.503: Addition of Reflective QoS Timer in PDU session related policy information","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: Add the Reflective QoS Timer as part of PDU Session related policy information..","secretary_remarks":"Revision of S2-180311. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14330,"status":"approved","reservation_date":"2018-01-23 16:34:31","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180311","revisedto":"S2-181571","release":"Rel-15","crspec":23.503,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181156.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181193","title":"23.502: Correction on Notification control for GBR QoS flow","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"draftCR","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-180308. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14410,"status":"approved","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180308","revisedto":"S2-181568","release":"Rel-15","crspec":23.502,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181193.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181194","title":"23.501: ARP usage clean-ups","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: The characteristics may be signalled, in two cases: - A special 5QI is used where all characteristics are signalled. - For any 5QI, the parameters priority, Averaging window, and\/or Maximum Data Burst Volume may be signalled in order to override the default values. In section 5.7.1.2 it is stated: 'The 5QI value may indicate that a QoS flow have signalled QoS characteristics, and if so, the QoS characteristics are included in the QoS profile.' This text does not cover the second alternative, and should be re-formulated in order to avoid confusion. Proposal 1: Reformulate text, so that all signaled characteristics parameters are included","secretary_remarks":"Revision of S2-180423. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14440,"status":"approved","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180423","revisedto":"S2-181621","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181194.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181195","title":"23.501: 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","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.","secretary_remarks":"Revision of S2-180474. Revised to S2-181281.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14470,"status":"revised","reservation_date":"2018-01-24 13:38:23","uploaded":"2018-01-26 18:07:53","revisionof":"S2-180474","revisedto":"S2-181281, S2-181759","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181195.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181196","title":"23.501: Introduction of 'Maximum Data Burst Volume for all GBR flows","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"draftCR","for":"Approval","abstract":"Summary of change: In last meeting it was agreed that a new QoS characteristics Parameter, Maximum Data Burst Volume', is introduced for GBR flows with PDB<20 ms. However, there is also a need to specify what data volume can be served for GBR flows with higher PDB. In S2-178049 values for Default Averaging Window are proposed for the standardized GBR 5QI's. The values are rather large, 2, and 3 s long, which correspond to unreasonable high requirements for the instantaneous bitrate in RAN. The instantaneous bitrate needed in RAN in order to serve the largest bursts that are within the GFBR requirement can be estimated by: GFBR*AW\/PDB The table below shows the largest burst size within the GFBR requirement, and the instantaneous bitrate that would be required in RAN to serve it within the PDB. 5QI PDB Averaging Window (AW) Largest data burst within GFBR Instantaneous bitrate 1 100 ms 2 s 2 * GFBR 20 * GFBR 2 150 ms 2 s 2 * GFBR 13 * GFBR 3 50 ms 3 s 3 * GFBR 60 * GFBR 4 300 ms 3 s 3 * G","secretary_remarks":"Revision of S2-181150. Postponed in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14170,"status":"postponed","reservation_date":"2018-01-24 14:19:37","uploaded":"2018-01-26 18:07:53","revisionof":"S2-181150","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181196.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-181281","title":"23.501: 5G QoS fixes for URLLC services related attributes - PDB, PER, MDB, 5QI","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"draftCR","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.","secretary_remarks":"Revision of S2-181195. Agreed in parallel session. Block Approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":14480,"status":"approved","reservation_date":"2018-01-25 11:34:50","uploaded":"2018-01-26 18:07:54","revisionof":"S2-181195","revisedto":"S2-181737","release":"Rel-15","crspec":23.501,"crspecversion":"15.0.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_125_Gothenburg\/Docs\/S2-181281.zip","group":"S2","meeting":"S2-125","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]