[{"name":"S2-1910891","title":"LS from RAN WG2: Reply LS on potential improvements for delay critical QoS flows","source":"RAN WG2","contact":"Chong Lou","contact-id":72227,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for the LS and provide the following answers. Q1) SA WG2 would like to ask RAN WG2 whether for QoS Flows of Delay critical GBR resource type a new QoS profile parameter (Delayed Packet Discarding) for controlling the handling of delayed packets at the RAN node is considered to be helpful to avoid wasting RAN resources. [RAN WG2 answer]: RAN WG2 discussed the late packets issues and agreed that inconsistent handling of late packets across RAN nodes and even within the same RAN node may cause errors in the application layer for certain delay-critical QoS flows. RAN WG2 understands that the potential RAN resource waste that can be avoided is to continuously deliver one out of 10^5 packets after it has not been delivered within the delay budget. Q2) SA WG2 would like to ask RAN WG2 whether for QoS Flows of Delay critical GBR resource type a recommendation to deliver packets that are delayed more than the delay budget for the radio interface is acceptable as long as the other QoS requirements of this QoS Flow can be fulfilled or other QoS Flows are not affected. [RAN WG2 answer]: See the answer above. Q3) SA WG2 would like to ask RAN WG2 whether for QoS Flows of Delay critical GBR resource type direction-specific values for the CN component of the PDB can be used by the NG-RAN to operate with different delay budgets for the uplink and the downlink direction and helpful to improve the resource scheduling for the NG-RAN. [RAN WG2 answer]: RAN WG2 thinks that it is helpful to improve the resource scheduling for the uplink and downlink scheduling for the RAN respectively. Action: RAN WG2 respectfully asks SA WG2 to take the feedback into account and provide feedback if any.","secretary_remarks":"Reply to S2-1906832 from S2#133. Noted in parallel session","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11420,"status":"noted","reservation_date":"2019-10-30 09:03:47","uploaded":"2019-11-04 09:40:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3","lsoriginalls":"R2-1914201","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910891.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911047","title":"Support for Application \/ Service Layer Rate Adaptation","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description for Application \/ Service Layer Rate Adaptation","secretary_remarks":"Revision of S2-1909602 from S2#135. Revised in parallel session, merging S2-1911538, to S2-1912050.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11480,"status":"revised","reservation_date":"2019-11-06 00:10:28","uploaded":"2019-11-08 04:33:35","revisionof":"S2-1909602","revisedto":"S2-1912050","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1858.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911047.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911075","title":"CN component of the PDB is configured per UL and DL","source":"OPPO, China Telecom, China Unicom","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PDB for a delay critical GBR 5QI is configured to RAN per Downlink and Uplink.","secretary_remarks":"Revised in parallel session to S2-1912275.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11620,"status":"revised","reservation_date":"2019-11-06 10:11:03","uploaded":"2019-11-08 10:44:36","revisionof":"","revisedto":"S2-1912275","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1926.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911075.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911316","title":"Corrections on Session-AMBR setting and enforcement","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are proposed: A general statement about Session-AMBR enforcement in UPF is added to clause 5.7.1.8. The statements about the subscribed Session-AMBR are moved from clause 5.7.2.6 to 5.7.2.7. The description in 5.8.2.7 is simplified and a reference to clause 5.7.1.8 (which describes the details of the enforcement) is added. A sentence in clause 6.3.3.3 is slightly reworded to avoid the usage of 'per PDU Session AMBR enforcement' as this could be confused with Session-AMBR.","secretary_remarks":"Revision of S2-1909111 from S2#135. Revised in parallel session to S2-1912052.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11540,"status":"revised","reservation_date":"2019-11-07 18:32:13","uploaded":"2019-11-08 16:57:51","revisionof":"S2-1909111","revisedto":"S2-1912052","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1755.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911316.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911317","title":"Handling of delayed packets of delay critical GBR QoS flows","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to introduce a new QoS parameter for delay critical GBR QoS Flows by which the RAN can be instructed to drop delayed packets in DL direction. When this QoS parameter is absent, the RAN discards or delivers the delayed packets according to local decision (as it is already described). If the SMF received the instruction to drop delayed packets in PCC rule, the SMF includes this instruction in QoS Profile for the RAN.","secretary_remarks":"Revision of S2-1903476 from S2#132. Revised in parallel session to S2-1912048.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11430,"status":"revised","reservation_date":"2019-11-07 18:32:15","uploaded":"2019-11-08 16:57:51","revisionof":"S2-1903476","revisedto":"S2-1912048","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1154.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911317.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911318","title":"Handling of delayed packets of delay critical GBR QoS flows","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that the PCF may determine whether to add an instruction in the PCC rule to drop delayed packets based on application logic provided by the OAM or AF. If the SMF received the instruction to drop delayed packets in PCC rule, the SMF includes this instruction in the QoS Profile of the corresponding QoS Flow.","secretary_remarks":"Revision of S2-1903477 from S2#132. Revised in parallel session to S2-1912049.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11450,"status":"revised","reservation_date":"2019-11-07 18:32:17","uploaded":"2019-11-08 16:57:51","revisionof":"S2-1903477","revisedto":"S2-1912049","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":248.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911318.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911538","title":"Support for Application Rate Adaptation and Explicit Congestion Notification","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the ECN RFC and TS 26.114 in the reference part. The NG-RAN and the UE support the RFC 3168 Explicit Congestion Notification (ECN), as described in TS 38.300, TS 36.300 and TS 26.114. Clarify that QNC and ECN can not be used at the same time, if the QNC is used, the ECN is not used. Otherwise the ECN is used. Clarify the Application \/ Service Layer Rate Adaptation based on QNC and ECN.","secretary_remarks":"Revision of S2-1909127 from S2#135. Merged into S2-1912050","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11500,"status":"merged","reservation_date":"2019-11-08 09:16:21","uploaded":"2019-11-08 11:48:58","revisionof":"S2-1909127","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":1503.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911538.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911676","title":"Reflective QoS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified how the SMF generates the UL PDR for the QoS authorization of the UL traffic of the SDF and how the SMF removes the UL PDR for the UL traffic of the SDF after an operator configurable time.","secretary_remarks":"Revision of S2-1908984 from S2#135. Revised in parallel session to S2-1912053.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11570,"status":"revised","reservation_date":"2019-11-08 11:52:14","uploaded":"2019-11-08 16:57:51","revisionof":"S2-1908984","revisedto":"S2-1912053","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1732.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911676.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911771","title":"ECN support in 5GS.","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"discussion","for":"Approval","abstract":"Does a historical overview of the 3GPP defined rate adaptation mechanisms and proposes to send LS to RAN WG2 and SA WG4 for the use of ECN in 5GS.","secretary_remarks":"","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11520,"status":"available","reservation_date":"2019-11-08 14:50:25","uploaded":"2019-11-08 18:40:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","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_136_Reno\/Docs\/S2-1911771.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911772","title":"[DRAFT] LS on the support for ECN in 5GS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"LS asks the following questions: - To SA4: Is there expected support for ECN when UE\u2019s MTSI client is operating over NR?- To RAN2: Is there any other any other use of ECN beyond bitrate adaptation for MTSI that was foreseen by RAN2?","secretary_remarks":"Revised in parallel session to S2-1912051.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11510,"status":"revised","reservation_date":"2019-11-08 14:53:38","uploaded":"2019-11-08 18:40:56","revisionof":"","revisedto":"S2-1912051","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG4","Cc":"RAN WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911772.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911913","title":"MTU size discovery and fragmentation","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the reference to TS 23.060 clause 9.3 on the MTU size and corresponding operation considerations.","secretary_remarks":"Revised in parallel session to S2-1912054.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11600,"status":"revised","reservation_date":"2019-11-08 20:42:27","uploaded":"2019-11-08 22:25:22","revisionof":"","revisedto":"S2-1912054","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2002.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911913.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912048","title":"Handling of delayed packets of delay critical GBR QoS flows","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to introduce a new QoS parameter for delay critical GBR QoS Flows by which the RAN can be instructed to drop delayed packets in DL direction. When this QoS parameter is absent, the RAN discards or delivers the delayed packets according to local decision (as it is already described). If the SMF received the instruction to drop delayed packets in PCC rule, the SMF includes this instruction in QoS Profile for the RAN.","secretary_remarks":"Revision of S2-1911317. Postponed in parallel session","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11440,"status":"postponed","reservation_date":"2019-11-19 22:35:26","uploaded":"2019-11-25 15:57:54","revisionof":"S2-1911317","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1154.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912048.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912049","title":"Handling of delayed packets of delay critical GBR QoS flows","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that the PCF may determine whether to add an instruction in the PCC rule to drop delayed packets based on application logic provided by the OAM or AF. If the SMF received the instruction to drop delayed packets in PCC rule, the SMF includes this instruction in the QoS Profile of the corresponding QoS Flow.","secretary_remarks":"Revision of S2-1911318. Postponed in parallel session","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11460,"status":"postponed","reservation_date":"2019-11-19 22:35:27","uploaded":"2019-11-25 15:57:54","revisionof":"S2-1911318","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":248.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912049.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912050","title":"Support for Application \/ Service Layer Rate Adaptation","source":"Ericsson, Tencent","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the description for Application \/ Service Layer Rate Adaptation Text mainly taken and adapted from 23.401 clause 4.3.9.3 and 4.7.4 Reasons for change of text and clause heading text: ECN in 23.401 is specified in 2 clauses Reason for removing 500 ms: ECN is end2end, and thus allowing a graceful period for a specific time is not only a RAN question, not all forwarding entities (routers) in the path may follow this recommendation. Furthermore it is not specified in the RFC3168. RTT may also be different, e.g. packet delay budget may be different for different applications. Adding note for guidance. Reason for removing NG-RAN should not drop packets when it has triggered setting of ECN: NG-RAN will always try to fulfil the required QoS characteristics, thus no need to specify anyting extra. Adding note stating that notification control is independent on ECN.","secretary_remarks":"Revision of S2-1911047, merging S2-1911538. Postponed in parallel session","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11490,"status":"postponed","reservation_date":"2019-11-19 22:35:28","uploaded":"2019-11-25 15:57:54","revisionof":"S2-1911047","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":1858.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912050.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912051","title":"[DRAFT] LS on the support for ECN in 5GS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"LS asks the following questions: - To SA4: Is there expected support for ECN when UE\u2019s MTSI client is operating over NR?- To RAN2: Is there any other any other use of ECN beyond bitrate adaptation for MTSI that was foreseen by RAN2?","secretary_remarks":"Revision of S2-1911772. Revised in parallel session to S2-1912535.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11520,"status":"revised","reservation_date":"2019-11-19 22:35:29","uploaded":"2019-11-25 15:57:54","revisionof":"S2-1911772","revisedto":"S2-1912535","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG4","Cc":"RAN WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912051.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912052","title":"Corrections on Session-AMBR setting and enforcement","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are proposed: A general statement about Session-AMBR enforcement in UPF is added to clause 5.7.1.8 together with references to the clauses describing the details of the N4 signaling. The statements about the subscribed Session-AMBR are moved from clause 5.7.2.6 to 5.7.2.7. The description in 5.8.2.7 is corrected by removing the UE related statements. A sentence in clause 6.3.3.3 is slightly reworded to avoid the usage of 'per PDU Session AMBR enforcement' as this could be confused with Session-AMBR.","secretary_remarks":"Revision of S2-1911316. Revised in parallel session to S2-1912536.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11550,"status":"revised","reservation_date":"2019-11-19 22:35:29","uploaded":"2019-11-25 15:57:54","revisionof":"S2-1911316","revisedto":"S2-1912536","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1755.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912052.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912053","title":"Reflective QoS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified how the SMF generates the UL PDR for the QoS authorization of the UL traffic of the SDF and how the SMF removes the UL PDR for the UL traffic of the SDF after an operator configurable time.","secretary_remarks":"Revision of S2-1911676. Noted","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11580,"status":"noted","reservation_date":"2019-11-19 22:35:30","uploaded":"2019-11-25 15:57:54","revisionof":"S2-1911676","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1732.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912053.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912054","title":"MTU size discovery and fragmentation","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Add the reference to TS 23.060 clause 9.3 on the MTU size and corresponding operation considerations.","secretary_remarks":"Revision of S2-1911913. Withdrawn","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11610,"status":"withdrawn","reservation_date":"2019-11-19 22:35:31","uploaded":null,"revisionof":"S2-1911913","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5GS_Ph1"},{"winame":"TEI16"}],"crnumber":2002.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912275","title":"CN component of the PDB is configured per UL and DL","source":"OPPO, China Telecom, China Unicom","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PDB for a delay critical GBR 5QI is configured to RAN per Downlink and Uplink.","secretary_remarks":"Revision of S2-1911075. Revised in parallel session to S2-1912554.","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11630,"status":"revised","reservation_date":"2019-11-21 16:37:58","uploaded":"2019-11-25 15:57:55","revisionof":"S2-1911075","revisedto":"S2-1912554","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1926.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912275.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912535","title":"[DRAFT] LS on the support for ECN in 5GS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"LS asks the following questions: - To SA4: Is there expected support for ECN when UE\u2019s MTSI client is operating over NR?- To RAN2: Is there any other any other use of ECN beyond bitrate adaptation for MTSI that was foreseen by RAN2?","secretary_remarks":"Revision of S2-1912051. For e-mail approval","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11530,"status":"revised","reservation_date":"2019-11-25 15:20:51","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912051","revisedto":"S2-1912765","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG4","Cc":"RAN WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912535.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912536","title":"Corrections on Session-AMBR setting and enforcement","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are proposed: A general statement about Session-AMBR enforcement in UPF is added to clause 5.7.1.8 together with references to the clauses describing the details of the N4 signaling. The statements about the subscribed Session-AMBR are moved from clause 5.7.2.6 to 5.7.2.7. The description in 5.8.2.7 is corrected by removing the UE related statements. A sentence in clause 6.3.3.3 is slightly reworded to avoid the usage of 'per PDU Session AMBR enforcement' as this could be confused with Session-AMBR.","secretary_remarks":"Revision of S2-1912052. Agreed in parallel session. Block approved","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11620,"status":"agreed","reservation_date":"2019-11-25 15:20:51","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912052","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":1755.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191090","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912536.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912537","title":"[DRAFT] LS on proposed reflective QoS update","source":"Huawei, HiSilicon","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"LS out","for":"Approval","abstract":"To:","secretary_remarks":"Created at meeting. For e-mail approval","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11590,"status":"revised","reservation_date":"2019-11-25 15:20:52","uploaded":"2019-11-25 16:07:54","revisionof":"","revisedto":"S2-1912766","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912537.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912554","title":"CN component of the PDB is configured per UL and DL","source":"OPPO, China Telecom, China Unicom, Qualcomm Incorporated","contact":"Yang Xu","contact-id":74478,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The PDB for a delay critical GBR 5QI is configured to RAN per Downlink and Uplink.","secretary_remarks":"Revision of S2-1912275. Postponed","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11640,"status":"postponed","reservation_date":"2019-11-25 15:21:04","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912275","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1926.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912554.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912765","title":"LS on the support for ECN in 5GS","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"LS asks the following questions: - To SA4: Is there expected support for ECN when UE\u2019s MTSI client is operating over NR?- To RAN2: Is there any other any other use of ECN beyond bitrate adaptation for MTSI that was foreseen by RAN2?","secretary_remarks":"-e-mail revision 3 of S2-1912535. Approved","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11590,"status":"available","reservation_date":"2019-11-28 05:47:21","uploaded":"2019-11-28 08:00:20","revisionof":"S2-1912535","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG4","Cc":"RAN WG3, CT WG1","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912765.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912766","title":"LS on proposed reflective QoS update","source":"SA WG2","contact":"Mirko Schramm","contact-id":23396,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. Attachments: S2-1912053.","secretary_remarks":"e-mail evision 3 of S2-1912537. Approved","agenda_item_sort_order":17,"ainumber":"6.5","ainame":"QoS concept and functionality","tdoc_agenda_sort_order":11660,"status":"available","reservation_date":"2019-11-28 05:47:21","uploaded":"2019-11-28 08:00:20","revisionof":"S2-1912537","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"},{"winame":"5GS_Ph1"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912766.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]