[{"name":"S2-184652","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 S2-183058 from S2#127. Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15890,"status":"noted","reservation_date":"2018-05-04 06:13:09","uploaded":"2018-05-04 06:17:56","revisionof":"S2-183058","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_127BIS_Newport_Beach\/Docs\/S2-184652.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184807","title":"Temporary restriction of Reflective QoS","source":"Intel, MediaTek Inc., InterDigital Inc.","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to to clarify that: 1) the supporting UE should (previously 'shall') indicate RQoS support upon PDU Session establishment 2) UE may revoke previously indicated support for RQoS","secretary_remarks":"Revision of (Agreed) S2-184544 from S2#127. Merged into S2-186003","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15940,"status":"merged","reservation_date":"2018-05-18 13:24:12","uploaded":"2018-05-22 13:56:03","revisionof":"S2-184544","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":169.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184807.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184809","title":"Fixing the definition of signalled QoS rule","source":"Intel, MediaTek Inc.","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that QoS parameters are not signalled as part of QoS rules. Instead, they are signalled on per QoS Flow basis.","secretary_remarks":"Revised in parallel session, merging S2-184888, to S2-186005.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16040,"status":"revised","reservation_date":"2018-05-18 13:40:54","uploaded":"2018-05-22 13:56:03","revisionof":"","revisedto":"S2-186005","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":346.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184809.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184868","title":"Further QoS clean-up","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 3.2 Abbreviation MDBV added. Clause 5.7.1.2  'non-standardized 5QI' changed to 'dynamically assigned 5QI' The text stating that signalled characteristics is included in the QoS Profile is moved to the end of the paragraph, so that it is clear that it valid for all signalled characteristics.  Clause 5.7.2.1 Clarify that it is the characteristics for the QoS Flow that is signalled.  Clause 5.7.2.4 CN behavior when receiving Notification is clarified.  Clause 5.7.3.4, 5.7.3.5, 5.7.3.7 and 5.7.4 Maximum Data Burst Volume -> MDBV. Clause 5.7.3.4 Missing 'and' added. Clause 5.7.3.5 Repetition removed.","secretary_remarks":"Revised in parallel session to S2-186007.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16140,"status":"revised","reservation_date":"2018-05-18 20:28:15","uploaded":"2018-05-22 12:49:04","revisionof":"","revisedto":"S2-186007","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":355.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184868.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184887","title":"QoS rule structure improvement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This paper propose to move the QoS Flow level parameters out of QoS rule(s) to improve N1 signaling efficiency","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16060,"status":"noted","reservation_date":"2018-05-18 20:33:03","uploaded":"2018-05-22 13:57:31","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_127BIS_Newport_Beach\/Docs\/S2-184887.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184888","title":"QoS rule structure improvement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.7.1.1 Clarify that QoS Flow Description may be sent associated with the QoS rule.  Clause 5.7.1.2 Clarify that QoS profile is sent to the (R)AN.  Clause 5.7.1.2A(new) Introduce QoS Flow Description to describe the set of QoS Flow level parameters which are proposed to be sent to the UE separately from the QoS rule(s).  Clause 5.7.1.4 Align with the introduction of QoS Flow Description.   Clause 5.7.1.5 Align with the introduction of QoS Flow Description. Clarify that GFBR\/MFBR (instead of GBR\/MBR) is signalled to the UE.   Clause 5.7.2.5  Clarify how SMF signal the GFBR\/MFBR parameters to RAN in QoS Profile and to UE in QoS Flow Description.","secretary_remarks":"Merged into S2-186005","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16070,"status":"merged","reservation_date":"2018-05-18 20:33:03","uploaded":"2018-05-22 01:37:30","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":361.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184888.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184889","title":"QoS rule structure improvement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the description related to QoS rule to reflect the QoS Flow Description.","secretary_remarks":"Revised in parallel session to S2-186006.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16080,"status":"revised","reservation_date":"2018-05-18 20:33:05","uploaded":"2018-05-22 01:37:30","revisionof":"","revisedto":"S2-186006","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":412.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184889.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184890","title":"Correlation between EBI and QFI","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provide the association to the UE.","secretary_remarks":"Revision of (Agreed) S2-184166 from S2#127. Withdrawn in parallel session.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16100,"status":"withdrawn","reservation_date":"2018-05-18 20:33:07","uploaded":"2018-05-22 01:37:30","revisionof":"S2-184166","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":286.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184890.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-184928","title":"Averaging Window Resolution","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: RAN WG2 LS received in S2-181425. It states: 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. Based on this, it is proposed to assume a default value of 2000ms (but also allow signaling in order to override averaging window) as stated in the LS. For delay critical GBR, LS hints that the averaging window should be shorter in the order of a few PDBs for services with tight delay critical requirements. However since this is just a default value that can be overwritten by signaling, here the target is just to state some initial value but not expecti","secretary_remarks":"Merged into S2-186002","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15910,"status":"merged","reservation_date":"2018-05-21 01:29:21","uploaded":"2018-05-22 14:18:12","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":369.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-184928.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185046","title":"Clarification on the support of Delay Critical resource type","source":"Nokia, Nokia Shanghai Bell, MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Clarified the MDBV enforcement UL and DL is required and that the averaging window for MFBR enforcement for the delay critical is smaller than the Averaging Window for the GFBR for delay critical QoS flows if we allow MFBR >GFBR. - GBR QoS Flows can be with GBR resource type or Delay-critical resource type. The term 'Delay-critical (GBR) QoS flow' is no longer used.","secretary_remarks":"Revision of (Agreed) S2-184545 from S2#127. Revised in parallel session to S2-186008.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16160,"status":"revised","reservation_date":"2018-05-21 10:49:34","uploaded":"2018-05-22 10:03:53","revisionof":"S2-184545","revisedto":"S2-186008","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":254.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185046.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185082","title":"Bit rate enforcement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.7.1.8, add description for MFBR, and clarify which entity (entities) to enforce the bit rate. Clause 5.7.2.6, remove the description regarding where to enforce AMBR as the enforcement is already described in clause 5.7.1.8","secretary_remarks":"Revised in parallel session to S2-186009.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16180,"status":"revised","reservation_date":"2018-05-21 14:06:41","uploaded":"2018-05-22 01:37:30","revisionof":"","revisedto":"S2-186009","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":398.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185082.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185150","title":"Support for UAC Access Identity in Visited PLMNs","source":"Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added that if the UE is subscribed to MPS, the AMF receives MPS priority indication from the UDM and, based on operator policy, the AMF includes it in the REGISTRATION ACCEPT message.","secretary_remarks":"Revised in parallel session to S2-186015.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16350,"status":"revised","reservation_date":"2018-05-21 21:15:24","uploaded":"2018-05-22 12:13:03","revisionof":"","revisedto":"S2-186015","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":463.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185150.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185151","title":"SMF exemption to NAS level congestion control for high priority access","source":"Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF includes Priority Access in the Nsmf_PDUSession_CreateSMContext Request message sent to the SMF if the AMF received an Establishment Cause as part of AN parameters during the Registration procedure or Service Request procedure where the Establishment Cause indicates high priority access. The SMF uses the Priority Access indication to determine if the UE request is subject to exemption from NAS level congestion control.","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":16370,"status":"agreed","reservation_date":"2018-05-21 21:29:47","uploaded":"2018-05-22 12:13:03","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":464.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-180488","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185151.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185204","title":"Clarify the relationship between GFBR and MDBV","source":"CATT","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For a delay critical QoS flow, the GFBR setting shouldn't conflict with the MDBV limit. I.e.the GFBR shouldn't be too large, so that it's possible for the traffic not exceeding GFBR can meet the MDBV limit.","secretary_remarks":"Revised in parallel session to S2-186010.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16200,"status":"revised","reservation_date":"2018-05-22 03:20:01","uploaded":"2018-05-22 08:25:17","revisionof":"","revisedto":"S2-186010","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":416.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185204.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185218","title":"Clarification on support of MFBR greater than GFBR","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the clarification that for present release the network may set MFBR bigger than GFBR for certain QoS flows based on operator policy and the knowledge that the rate adaptations are supported based on UE implementation.","secretary_remarks":"Revised in parallel session to S2-186011.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16230,"status":"revised","reservation_date":"2018-05-22 04:00:52","uploaded":"2018-05-22 12:54:19","revisionof":"","revisedto":"S2-186011","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":417.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185218.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185287","title":"Reflective QoS discussion","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"discussion","for":"Agreement","abstract":"Discussion of proposal that the algorithm for setting the RQI bit should change","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16020,"status":"noted","reservation_date":"2018-05-22 08:32:16","uploaded":"2018-05-22 13:06:34","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_127BIS_Newport_Beach\/Docs\/S2-185287.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185373","title":"Clarification on 5QI and related parameters","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Add the description on the signalled priority level with 5QI in the current TS  2) Delete the wrong description of QoS Flow.","secretary_remarks":"Revised in parallel session to S2-186012.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16260,"status":"revised","reservation_date":"2018-05-22 09:55:19","uploaded":"2018-05-22 14:48:43","revisionof":"","revisedto":"S2-186012","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":488.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185373.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185374","title":"Clarification on 5QI and related parameters","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description on the signalled priority level with 5QI in the current TS.","secretary_remarks":"Revised in parallel session to S2-186013.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16280,"status":"revised","reservation_date":"2018-05-22 09:55:20","uploaded":"2018-05-22 14:48:43","revisionof":"","revisedto":"S2-186013","release":"Rel-15","crspec":23.503,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":92.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185374.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185377","title":"QNC during Handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During a handover, the Source NG-RAN shall inform the Target NG-RAN about those QoS Flows for which a notification that the GFBR cannot be fulfilled has been sent. For any such QoS Flow which is successfully handed over, the Target NG-RAN shall send a notification that the GFBR can be fulfilled again. The Target NG-RAN may send a subsequent notification that the GFBR cannot be fulfilled whenever necessary, i.e. even during the configured time described above. The admission control at the Target NG-RAN decides based on the QoS parameters of the QoS Flow, i.e. without taking into account that the Source NG-RAN was not delivering the requested GFBR for this QoS Flow.","secretary_remarks":"Revised in parallel session to S2-186014.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16300,"status":"revised","reservation_date":"2018-05-22 09:55:24","uploaded":"2018-05-22 14:48:43","revisionof":"","revisedto":"S2-186014","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":436.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185377.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185378","title":"Temporary restriction of Reflective QoS","source":"Huawei,Intel, MediaTek Inc., InterDigital Inc.","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to clarify that: 1) The UE indication of support of Reflecitve QoS shall be only provided during the PDU Session Establishment procedure (unless the UE is connected via EPC as defined in clause 5.17.2). The UE as well as the network shall store the information whether or not the UE indicated support of Reflective QoS throughout the lifetime of the PDU Session. 2) Under exceptional circumstances, the UE shall delete all derived QoS rules for this PDU Session and the network shall stop any user plane enforcement actions related to Reflective QoS for this PDU Session. In addition, the network may provide signalled QoS rules for the SDFs for which Reflective QoS was used before.  3) the supporting UE should (previously 'shall') indicate RQoS support upon PDU Session establishment  4) UE may revoke previously indicated support for RQoS","secretary_remarks":"Revision of (Agreed) S2-184544 from S2#127. Revised in parallel session, merging S2-184807, to S2-186003.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15950,"status":"revised","reservation_date":"2018-05-22 09:55:25","uploaded":"2018-05-22 14:48:43","revisionof":"S2-184544","revisedto":"S2-186003","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":169.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185378.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185379","title":"Reflective QoS in interworking","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description in clause 5.17.2.2.2 is updated by clarifying the conditions when the UE indication for support of Reflective QoS has to be provided in the PDU session modification procedure. It is also added that UE as well as network shall store this indication so that subsequent mobility events do not require another signaling of this indication.","secretary_remarks":"Revised in parallel session to S2-186004.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15980,"status":"revised","reservation_date":"2018-05-22 09:55:27","uploaded":"2018-05-22 14:48:43","revisionof":"","revisedto":"S2-186004","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":437.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185379.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185420","title":"Adding default value for Averaging Window","source":"Huawei, HiSillicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Adding default value for Averaging Window to the 5QI characteristics table in clause 5.7.4 for GBR 5QIs. - Aligning the default priority of some services to those in TS 23.203. - Adding standard 5QI for 'Mission Critical Video user plane'.","secretary_remarks":"Revised in parallel session, merging S2-184928, to S2-186002.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15920,"status":"revised","reservation_date":"2018-05-22 11:51:11","uploaded":"2018-05-22 14:34:56","revisionof":"","revisedto":"S2-186002","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":447.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185420.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185429","title":"Add indication of Notification Control to QoS rules sent to UE","source":"Huawei, HiSilicon, Nokia","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that Notification Control is signalled to the NG-RAN.","secretary_remarks":"Revision of (Agreed) S2-184549 from S2#127. Revised in parallel session to S2-186077.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16110,"status":"revised","reservation_date":"2018-05-22 12:11:00","uploaded":"2018-05-22 14:10:06","revisionof":"S2-184549","revisedto":"S2-186077","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":296.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185429.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185437","title":"Change to the conditions for setting the RQI","source":"Samsung","contact":"Andy Bennett","contact-id":70253,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The RQI bit is set for the first DL packet, and if the QFI has changed. The bit is also set as necessary to avoid expiry of the RQ Timer for the derived QoS rule, but when to do this is left to implementation.","secretary_remarks":"Not Handled","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16030,"status":"not treated","reservation_date":"2018-05-22 12:33:32","uploaded":"2018-05-22 13:06:34","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":449.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185437.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-185502","title":"LS from RAN WG3: LS on signalling of dynamic 5QI values","source":"RAN WG3","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to inform SA WG2 that RAN WG3 has finalized the coding of the QoS Profile over NGAP taking section 5.7.1.3 of TS 23.501 as guideline. However, for the particular case where the full QoS characteristics are sent for a QoS flow by 5GC, RAN WG3 could not see a benefit or use to signal an associated dynamically 5QI to NG-RAN as mentioned in case 2 of section 5.7.1.3 but instead some associated constraint. Therefore, RAN WG3 has decided to not include a 5QI value in the QoS profile for this case. Action: RAN WG3 kindly ask SA WG2 to take RAN WG3 agreement into account and feedback if any show stopper is found regarding this decision.","secretary_remarks":"Postponed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15900,"status":"postponed","reservation_date":"2018-05-27 13:46:18","uploaded":"2018-05-27 13:57:54","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-183409","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-185502.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186002","title":"Adding default value for Averaging Window","source":"Huawei, HiSillicon, Nokia, Nokia Shanghai Bell","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Adding default value for Averaging Window to the 5QI characteristics table in clause 5.7.4 for GBR 5QIs. - Aligning the default priority of some services to those in TS 23.203. - Adding standard 5QI for 'Mission Critical Video user plane'.","secretary_remarks":"Revision of S2-185420, merging S2-184928. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15930,"status":"agreed","reservation_date":"2018-05-30 19:40:40","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185420","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":447.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180478","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186002.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186003","title":"Temporary restriction of Reflective QoS","source":"Intel, MediaTek Inc., InterDigital Inc. ,Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to clarify that: 1) The UE indication of support of Reflecitve QoS shall be only provided during the PDU Session Establishment procedure (unless the UE is connected via EPC as defined in clause 5.17.2). The UE as well as the network shall store the information whether or not the UE indicated support of Reflective QoS throughout the lifetime of the PDU Session. 2) Under exceptional circumstances, the UE shall delete all derived QoS rules for this PDU Session and the network shall stop any user plane enforcement actions related to Reflective QoS for this PDU Session. In addition, the network may provide signalled QoS rules for the SDFs for which Reflective QoS was used before.  3) the supporting UE should (previously 'shall') indicate RQoS support upon PDU Session establishment  4) UE may revoke previously indicated support for RQoS","secretary_remarks":"Revision of S2-185378, merging S2-184807. Revised in parallel session to S2-186155.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15960,"status":"revised","reservation_date":"2018-05-30 19:40:41","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185378","revisedto":"S2-186155","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":169.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186003.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186004","title":"Reflective QoS in interworking","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description in clause 5.17.2.2.2 is updated by clarifying the conditions when the UE indication for support of Reflective QoS has to be provided in the PDU session modification procedure. It is also added that UE as well as network shall store this indication so that subsequent mobility events do not require another signaling of this indication.","secretary_remarks":"Revision of S2-185379. Revised in parallel session to S2-186156.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15990,"status":"revised","reservation_date":"2018-05-30 19:40:42","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185379","revisedto":"S2-186156","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":437.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186004.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186005","title":"Fixing the definition of signalled QoS rule","source":"Intel, MediaTek Inc.","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies that QoS parameters are not signalled as part of QoS rules. Instead, they are signalled on per QoS Flow basis.","secretary_remarks":"Revision of S2-184809, merging S2-184888. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16050,"status":"agreed","reservation_date":"2018-05-30 19:40:43","uploaded":"2018-06-02 18:27:54","revisionof":"S2-184809","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":346.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180485","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186005.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186006","title":"QoS rule structure improvement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the description related to QoS rule to reflect the QoS Flow Description.","secretary_remarks":"Revision of S2-184889. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16090,"status":"agreed","reservation_date":"2018-05-30 19:40:44","uploaded":"2018-06-02 18:27:54","revisionof":"S2-184889","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":412.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180487","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186006.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186007","title":"Further QoS clean-up","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 3.2 Abbreviation MDBV added. Clause 5.7.1.2  'non-standardized 5QI' changed to 'dynamically assigned 5QI' The text stating that signalled characteristics is included in the QoS Profile is moved to the end of the paragraph, so that it is clear that it valid for all signalled characteristics.  Clause 5.7.2.1 Clarify that it is the characteristics for the QoS Flow that is signalled.  Clause 5.7.2.4 CN behavior when receiving Notification is clarified.  Clause 5.7.3.4, 5.7.3.5, 5.7.3.7 and 5.7.4 Maximum Data Burst Volume -> MDBV. Clause 5.7.3.4 Missing 'and' added. Clause 5.7.3.5 Repetition removed.","secretary_remarks":"Revision of S2-184868. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16150,"status":"agreed","reservation_date":"2018-05-30 19:40:46","uploaded":"2018-06-02 18:27:54","revisionof":"S2-184868","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":355.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180485","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186007.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186008","title":"Clarification on the support of Delay Critical resource type","source":"Nokia, Nokia Shanghai Bell, MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Clarified the MDBV enforcement UL and DL is required and that the averaging window for MFBR enforcement for the delay critical is smaller than the Averaging Window for the GFBR for delay critical QoS flows if we allow MFBR >GFBR. - GBR QoS Flows can be with GBR resource type or Delay-critical resource type. The term 'Delay-critical (GBR) QoS flow' is no longer used.","secretary_remarks":"Revision of S2-185046. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16170,"status":"agreed","reservation_date":"2018-05-30 19:40:47","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185046","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":254.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180481","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186008.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186009","title":"Bit rate enforcement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clause 5.7.1.8, add description for MFBR, and clarify which entity (entities) to enforce the bit rate. Clause 5.7.2.6, remove the description regarding where to enforce AMBR as the enforcement is already described in clause 5.7.1.8","secretary_remarks":"Revision of S2-185082. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16190,"status":"agreed","reservation_date":"2018-05-30 19:40:48","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185082","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":398.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180479","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186009.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186010","title":"Clarify the relationship between GFBR and MDBV","source":"CATT, Huawei","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For a delay critical QoS flow, the GFBR setting shouldn't conflict with the MDBV limit. I.e.the GFBR shouldn't be too large, so that it's possible for the traffic not exceeding GFBR can meet the MDBV limit.","secretary_remarks":"Revision of S2-185204. Revised in parallel session to S2-186158.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16210,"status":"revised","reservation_date":"2018-05-30 19:40:49","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185204","revisedto":"S2-186158","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":416.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186010.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186011","title":"Clarification on support of MFBR greater than GFBR","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the clarification that for present release the network may set MFBR bigger than GFBR for certain QoS flows based on operator policy and the knowledge that the rate adaptations are supported based on UE implementation.","secretary_remarks":"Revision of S2-185218. Revised in parallel session to S2-186159.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16240,"status":"revised","reservation_date":"2018-05-30 19:40:50","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185218","revisedto":"S2-186159","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":417.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186011.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186012","title":"Clarification on 5QI and related parameters","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Add the description on the signalled priority level with 5QI in the current TS  2) Delete the wrong description of QoS Flow.","secretary_remarks":"Revision of S2-185373. WITHDRAWN","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16270,"status":"withdrawn","reservation_date":"2018-05-30 19:40:51","uploaded":null,"revisionof":"S2-185373","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":488.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186013","title":"Clarification on 5QI and related parameters","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description on the signalled priority level with 5QI in the current TS.","secretary_remarks":"Revision of S2-185374. Noted","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16290,"status":"noted","reservation_date":"2018-05-30 19:40:52","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185374","revisedto":"","release":"Rel-15","crspec":23.503,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":92.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186013.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186014","title":"QNC during Handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During a handover, the Source NG-RAN shall inform the Target NG-RAN about those QoS Flows for which a notification that the GFBR cannot be fulfilled has been sent. For any such QoS Flow which is successfully handed over, the Target NG-RAN shall send a notification that the GFBR can be fulfilled again. The Target NG-RAN may send a subsequent notification that the GFBR cannot be fulfilled whenever necessary, i.e. even during the configured time described above. The admission control at the Target NG-RAN decides based on the QoS parameters of the QoS Flow, i.e. without taking into account that the Source NG-RAN was not delivering the requested GFBR for this QoS Flow.","secretary_remarks":"Revision of S2-185377. Revised in parallel session to S2-186160.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16310,"status":"revised","reservation_date":"2018-05-30 19:40:54","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185377","revisedto":"S2-186160","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":436.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186014.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186015","title":"Support for UAC Access Identity in Visited PLMNs","source":"Vencore Labs, OEC, AT&T, T-Mobile USA, Sprint","contact":"Vijay Varma","contact-id":74475,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added that if the UE is subscribed to MPS, the AMF receives MPS priority indication from the UDM and, based on operator policy, the AMF includes it in the REGISTRATION ACCEPT message.","secretary_remarks":"Revision of S2-185150. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16360,"status":"agreed","reservation_date":"2018-05-30 19:40:55","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185150","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":463.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-180489","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186015.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186077","title":"Add indication of Notification Control to QoS rules sent to UE","source":"Huawei, HiSilicon, Nokia, MediaTek Inc.","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that Notification Control is signalled to the NG-RAN.","secretary_remarks":"Revision of S2-185429. Revised in parallel session to S2-186157.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16120,"status":"revised","reservation_date":"2018-05-31 18:43:00","uploaded":"2018-06-02 18:27:54","revisionof":"S2-185429","revisedto":"S2-186157","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":296.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186077.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186155","title":"Temporary restriction of Reflective QoS","source":"Intel, MediaTek Inc., InterDigital Inc. ,Huawei","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to clarify that: 1) The UE indication of support of Reflecitve QoS shall be only provided during the PDU Session Establishment procedure (unless the UE is connected via EPC as defined in clause 5.17.2). The UE as well as the network shall store the information whether or not the UE indicated support of Reflective QoS throughout the lifetime of the PDU Session. 2) Under exceptional circumstances, the UE shall delete all derived QoS rules for this PDU Session and the network shall stop any user plane enforcement actions related to Reflective QoS for this PDU Session. In addition, the network may provide signalled QoS rules for the SDFs for which Reflective QoS was used before.  3) the supporting UE should (previously 'shall') indicate RQoS support upon PDU Session establishment  4) UE may revoke previously indicated support for RQoS","secretary_remarks":"Revision of S2-186003. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":15970,"status":"agreed","reservation_date":"2018-06-02 16:42:37","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186003","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":169.0,"crrevision":8.0,"crcategory":"F","tsg_crp":"SP-180489","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186155.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186156","title":"Reflective QoS in interworking","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description in clause 5.17.2.2.2 is updated by clarifying the conditions when the UE indication for support of Reflective QoS has to be provided in the PDU session modification procedure. It is also added that UE as well as network shall store this indication so that subsequent mobility events do not require another signaling of this indication.","secretary_remarks":"Revision of S2-186004. Revised to S2-186261.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16000,"status":"revised","reservation_date":"2018-06-02 16:42:38","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186004","revisedto":"S2-186261","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":437.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186156.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186157","title":"Add indication of Notification Control to QoS rules sent to UE","source":"Huawei, HiSilicon, Nokia, MediaTek Inc.","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that Notification Control is signalled to the NG-RAN.","secretary_remarks":"Revision of S2-186077. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16130,"status":"agreed","reservation_date":"2018-06-02 16:42:39","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186077","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":296.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180478","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186157.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186158","title":"Clarify the relationship between GFBR and MDBV","source":"CATT, Huawei","contact":"Yali Guo","contact-id":67048,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For a delay critical QoS flow, the GFBR setting shouldn't conflict with the MDBV limit. I.e.the GFBR shouldn't be too large, so that it's possible for the traffic not exceeding GFBR can meet the MDBV limit.","secretary_remarks":"Revision of S2-186010. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16220,"status":"agreed","reservation_date":"2018-06-02 16:42:39","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186010","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":416.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180481","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186158.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186159","title":"Clarification on support of MFBR greater than GFBR","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the clarification that for present release the network may set MFBR bigger than GFBR for certain QoS flows based on operator policy and the knowledge that the rate adaptations are supported based on UE implementation.","secretary_remarks":"Revision of S2-186011. Agreed in parallel session. Block approved","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16250,"status":"agreed","reservation_date":"2018-06-02 16:42:40","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186011","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":417.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-180480","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186159.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186160","title":"QNC during Handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During a handover, the Source NG-RAN shall inform the Target NG-RAN about those QoS Flows for which a notification that the GFBR cannot be fulfilled has been sent. For any such QoS Flow which is successfully handed over, the Target NG-RAN shall send a notification that the GFBR can be fulfilled again. The Target NG-RAN may send a subsequent notification that the GFBR cannot be fulfilled whenever necessary, i.e. even during the configured time described above. The admission control at the Target NG-RAN decides based on the QoS parameters of the QoS Flow, i.e. without taking into account that the Source NG-RAN was not delivering the requested GFBR for this QoS Flow.","secretary_remarks":"Revision of S2-186014. Revised to S2-186262.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16320,"status":"revised","reservation_date":"2018-06-02 16:42:41","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186014","revisedto":"S2-186262","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":436.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186160.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186261","title":"Reflective QoS in interworking","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description in clause 5.17.2.2.2 is updated by clarifying the conditions when the UE indication for support of Reflective QoS has to be provided in the PDU session modification procedure. It is also added that UE as well as network shall store this indication so that subsequent mobility events do not require another signaling of this indication.","secretary_remarks":"Revision of S2-186156. This CR was agreed.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16010,"status":"agreed","reservation_date":"2018-06-02 16:43:14","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186156","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":437.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-180487","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186261.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186262","title":"QNC during Handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During a handover, the Source NG-RAN shall inform the Target NG-RAN about those QoS Flows for which a notification that the GFBR cannot be fulfilled has been sent. For any such QoS Flow which is successfully handed over, the Target NG-RAN shall send a notification that the GFBR can be fulfilled again. The Target NG-RAN may send a subsequent notification that the GFBR cannot be fulfilled whenever necessary, i.e. even during the configured time described above. The admission control at the Target NG-RAN decides based on the QoS parameters of the QoS Flow, i.e. without taking into account that the Source NG-RAN was not delivering the requested GFBR for this QoS Flow.","secretary_remarks":"Revision of S2-186160. Revised to S2-186268.","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16330,"status":"revised","reservation_date":"2018-06-02 16:43:16","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186160","revisedto":"S2-186268","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":436.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186262.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-186268","title":"QNC during Handover","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During a handover, the Source NG-RAN shall inform the Target NG-RAN about those QoS Flows for which a notification that the GFBR cannot be fulfilled has been sent. For any such QoS Flow which is successfully handed over, the Target NG-RAN shall send a notification that the GFBR can be fulfilled again. The Target NG-RAN may send a subsequent notification that the GFBR cannot be fulfilled whenever necessary, i.e. even during the configured time described above. The admission control at the Target NG-RAN decides based on the QoS parameters of the QoS Flow, i.e. without taking into account that the Source NG-RAN was not delivering the requested GFBR for this QoS Flow.","secretary_remarks":"Revision of S2-186262. This CR was agreed","agenda_item_sort_order":22,"ainumber":"6.5.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":16340,"status":"agreed","reservation_date":"2018-06-02 16:43:17","uploaded":"2018-06-02 18:27:55","revisionof":"S2-186262","revisedto":"","release":"Rel-15","crspec":23.501,"crspecversion":"15.1.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":436.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-180487","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_127BIS_Newport_Beach\/Docs\/S2-186268.zip","group":"S2","meeting":"S2-127","year":2018,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]