[{"name":"S2-1904884","title":"LS from RAN WG2: Reply LS on supporting low latency and low jitter during handover procedure","source":"RAN WG2","contact":"Haitao Li","contact-id":73693,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for their LS S2-1811556 and S2-1813333 on supporting low latency and low jitter during handover procedure. For Key Issue#2, Solution #5 in S2-1811556, RAN WG2 has replied the LS regarding Question 1 in R2-1819065. Regarding Questions 2-4, in RAN WG2's discussion, some companies considered that SA WG2's bi-casting solution is beneficial to reduce latency and jitter due to data forwarding during handover procedure. However, some companies also noted that the most stringent URLLC latency and jitter requirements can only be met with special deployments. In such deployments it does not matter if the DL data is bi-casted or forwarded over Xn since the network transmission delay will anyway be negligible and therefore within the delay and jitter requirements defined for the URLLC use cases. Some concerns were raised that CN involvement prior to handover completion could delay handover. RAN WG2 would like to inform SA WG2 that RAN WG2 is now working on solutions for interruption time reduction during handover as part of the Rel-16 NR mobility enhancement WI, e.g. by means of UE maintaining simultaneous connectivity with source cell and target cell during handover to achieve 0ms interruption time. The simultaneous connectivity allows the PDCP packet duplication which may already effectively address the concern from SA WG2. RAN WG2 can't guarantee that any RAN WG2 aspects related to the SA WG2 solution can be completed in Rel-16's timeframe. Action: RAN WG2 kindly asks SA WG2 to take the above response into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25160,"status":"noted","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3","lsoriginalls":"R2-1905428","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904884.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904888","title":"LS from RAN WG2: Reply LS on Automatic Restoration of GFBR QOS","source":"RAN WG2","contact":"Manook Soghomonian","contact-id":69668,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for the LS on Automatic Restoration of GFBR QOS. RAN WG2 has analysed impacts on component B and component C in Annex B, and would like to provide the following feedback: In response to the questions raised in the incoming LS: i) The admission control concept outlined in component B. This question has already been answered by RAN WG3. ii) With regards to component C, whether RAN signalling (RRC or other RAN signalling) from the RAN to the UE is needed when a GFBR flow is no longer granted the 'guaranteed' radio resources. From AS point of view, RAN WG2 do not see any need for the UE to be informed that the QoS is not met in order for the UE to discard old packets, as the PDCP layer already has functionality for discarding of outdated packets. This functionality is based on Configurable PDCP Discard Timer which ranges from 10ms - 1.5s. Furthermore, RAN WG2 cannot comment whether there is any application layer that needs to be informed by the network that the QoS cannot be met. Action: RAN WG2 respectfully asks SA WG2 to take the above information into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25450,"status":"noted","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3","lsoriginalls":"R2-1905469","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904888.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904891","title":"LS from RAN WG3: Reply LS on Automatic Restoration of GFBR QoS","source":"RAN WG3","contact":"Philippe Godin","contact-id":68843,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 thanks SA WG2 to consult RAN WG3 on solutions targeting at automatic restoration of GFBR QoS. As requested by SA WG2 in S2-1902906, the feedback relating to Component B and Component C of one company's proposal solution described in the Annex B of S2-1902906 is provided below. Regarding Component B, from RAN WG3 perspective, the NG-RAN node shall be able to realize the guaranteed bit rate required by the QoS flow if it is admitted via the admission control. Therefore, the '3 steps admission control' described in the Annex B of S2-1902906 dilutes the meaning of admission control and GBR, the impacts from such deviation from the basic definition would eventually incapacitate these well-defined mechanisms. Moreover, RAN WG3 must point out that admission control design is a vendor implementation specific feature, so RAN WG3 is not able to assume that the admission control mechanism is designed in the way as elaborated in the Annex B of S2-1902906, or to guarantee that the prerequisites required by such solutions (e.g. prediction of future use of cell radio resources) can be fulfilled. Essentially, RAN WG3 would therefore like to suggest that the solutions for this issue should not contradict the existing definitions and framework of admission control and QoS model and would therefore eliminate this one company's proposal from the candidate solutions of key issue #7. Action: RAN WG3 kindly ask SA WG2 to take into account the above answers.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25460,"status":"noted","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2, RAN WG1","lsoriginalls":"R3-191991","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904891.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904897","title":"LS from RAN WG3: Reply LS on 5G_URLLC","source":"RAN WG3","contact":"Angelo Centonza","contact-id":35887,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 would like to thank SA WG2 for their LS on URLLC. With regards to Key Issue 4 and Action: 2 RAN WG3 thinks that the Uu delay and UE processing delay will be evaluated by RAN WG2 and would like to highlight that mechanisms for delay measurement over the F1-U interface were studied. RAN WG3 has concluded that TS28.552 contains feasible measurements that can represent the F1-U latency in UL and DL. The measurements identified are in Section 5.1.3.3 of TS28.552. RAN WG3 concluded that: - The 'average delay DL in CU-UP' and 'average delay DL in gNB-DU' in section 5.1.3.3 of TS 28.552 can be taken as baseline. RAN WG3 assumes that these measurements could be valid also for UL. Alternatively, specific UL measurements can be defined, on the basis of the DL measurements, to estimate gNB-DU and gNB-CU-UP internal UL delays. - The 'average delay on F1-U' measurement in section 5.1.3.3 of TS 28.552 already provides an estimate of the delay over the F1 interface for both UL and DL. Action: RAN WG3 kindly asks SA WG2 and RAN WG2 to take the above analysis and conclusion into account in their work on URLLC","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25230,"status":"noted","reservation_date":"2019-04-23 11:45:51","uploaded":"2019-04-23 13:14:44","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG2","Cc":"TSG RAN, SA WG5","lsoriginalls":"R3-192179","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1904897.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905042","title":"Generalized text for redundant user planes in RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Generalize RAN description, so that redundant user plane resources are provided based on RSN, no matter how NG-RAN control plane topology is realised or configured.","secretary_remarks":"Revised in parallel session to S2-1906516.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24870,"status":"revised","reservation_date":"2019-05-03 22:15:52","uploaded":"2019-05-07 14:17:45","revisionof":"","revisedto":"S2-1906516","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1307.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905042.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905043","title":"Generalized text for redundant user planes in RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Generalize description, so that redundant user plane resources are provided based on RSN, without restricting the description to Master\/secondary RAN nodes.","secretary_remarks":"Revised in parallel session to S2-1906517.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24900,"status":"revised","reservation_date":"2019-05-03 22:15:53","uploaded":"2019-05-07 04:32:04","revisionof":"","revisedto":"S2-1906517","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1323.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905043.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905073","title":"Implication of not requiring S6b from PGW-C+SMF for ePDG support","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"This paper discuss the implications to use N10 for S6b, and propose to keep S6b as it is.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":26530,"status":"noted","reservation_date":"2019-05-04 13:32:14","uploaded":"2019-05-07 04:33:34","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"TEI16"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905073.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905107","title":"UP connection Deactivation for URLLC PDU Session","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the Service Request and AN Release procedure to activate\/deactivate the User Plane of the PDU Sessions for URLLC or the (redundant) I-UPF(s) is to be added\/replaced\/removed. The PDU Session for URLLC is either with redundant I-UPFs or with redundant N3\/N9 tunnels.","secretary_remarks":"Revision of S2-1904822 from S2#132. Revised in parallel session to S2-1906518.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24950,"status":"revised","reservation_date":"2019-05-05 06:24:48","uploaded":"2019-05-07 09:59:37","revisionof":"S2-1904822","revisedto":"S2-1906518","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1138.0,"crrevision":4.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905107.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905111","title":"Clarification on redudant N3 tunnel solution -23.501","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN and UPF replicates the packet and assigns the same QoS Flow Id and GTP-U sequence number to them for the redundant transmission.","secretary_remarks":"Revised in parallel session to S2-1906519.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24970,"status":"revised","reservation_date":"2019-05-05 06:26:54","uploaded":"2019-05-07 11:21:00","revisionof":"","revisedto":"S2-1906519","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1320.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905111.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905112","title":"Update procedures related to redundant transmission","source":"Huawei?, HiSilicon?, OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Update PDU Session Modification procedure to support removal of redundancy tunnel. 2. Clarify that SMF shall release URLLC QoS Flows by triggering PDU Session Modification procedure after Xn\/N2 HO procedure if only one AN Tunnel Info is provided by Target NG-RAN. 3. This method applies only to the scenario where the redundant CN tunnels of the PDU Session connect to the same RAN node and UPF. 4. Editorial modifications.","secretary_remarks":"Revision of S2-1904763 from S2#132. Confirm sources! Revised in parallel session, merging S2-1905113, to S2-1906520.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25010,"status":"revised","reservation_date":"2019-05-05 06:33:27","uploaded":"2019-05-07 11:21:00","revisionof":"S2-1904763","revisedto":"S2-1906520","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1203.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905112.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905113","title":"Update procedures related to redundant transmission for PDU Session establishment","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This method applies only to the scenario where the redundant CN tunnels of the PDU Session connect to the same RAN node and UPF.","secretary_remarks":"Merged into S2-1906520","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25040,"status":"merged","reservation_date":"2019-05-05 06:39:22","uploaded":"2019-05-07 11:21:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1341.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905113.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905114","title":"Conclusion proposal on KI#2 Supporting low latency and low jitter during handover procedure","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a conclusion for KI#2.","secretary_remarks":"Revised in parallel session to S2-1906525.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25170,"status":"revised","reservation_date":"2019-05-05 06:46:52","uploaded":"2019-05-07 11:21:00","revisionof":"","revisedto":"S2-1906525","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":35.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905114.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905117","title":"New WID: S6b Optional for ePDG connected 5GS","source":"Cisco Systems, TMobile USA, Verizon, AT&T","contact":"Irfan Ali","contact-id":74090,"tdoctype":"WID new","for":"Approval","abstract":"Proposes to make S6b optional when ePDG is connected to SMF+PGW-C","secretary_remarks":"Revision of S2-1904565 from S2#132. Revised in parallel session to S2-1906369.","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":26540,"status":"revised","reservation_date":"2019-05-05 12:29:12","uploaded":"2019-05-07 13:27:27","revisionof":"S2-1904565","revisedto":"S2-1906369","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905117.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905118","title":"Discussion paper on making S6b optional for ePDG connected to SMF+PGW-C","source":"Cisco Systems Belgium","contact":"Irfan Ali","contact-id":74090,"tdoctype":"discussion","for":"Discussion","abstract":"Provides background and impacts for making S6b optional for ePDG connected to SMF+PGW-C.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":26520,"status":"noted","reservation_date":"2019-05-05 12:34:56","uploaded":"2019-05-07 13:27:27","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905118.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905119","title":"S6b optional for ePDG connected to 5GS","source":"Cisco Systems","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For the interworking scenario for ePDG connected to SMF+PGW-C, remove S6b interface between SMF+PGW-C and 3GPP AAA Server.","secretary_remarks":"Revised in parallel session to S2-1906368.","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":26560,"status":"revised","reservation_date":"2019-05-05 12:39:44","uploaded":"2019-05-07 13:27:27","revisionof":"","revisedto":"S2-1906368","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"TEI16"}],"crnumber":1323.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905119.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905120","title":"S6b optional for ePDG connected to 5GS","source":"Cisco Systems Belgium","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Updates specification for making S6b optional for ePDG connected to SMF+PGW-C.","secretary_remarks":"Revised in parallel session to S2-1906367.","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":26580,"status":"revised","reservation_date":"2019-05-05 12:42:21","uploaded":"2019-05-07 13:28:14","revisionof":"","revisedto":"S2-1906367","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"TEI16"}],"crnumber":1342.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905120.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905126","title":"Introduce the QoS monitoring policy related PCC rules information","source":"China Telecom","contact":"Zhao Song","contact-id":71667,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The QoS monitoring can be generally devided into two parts: the monitoring part and the reporting part. Therefore, the information contained in the PCF QoS monitoring policy includes two sets of information, which are corrsponding to the monitoring and the reporting, respectively. The monitoring related information includes: QoS parameter to be measured, i.e. UL\/DL packet delay or round trip packet delay Measurement mode, which defines the frequency of the requested monitoring. The monitoring can be performed immediately, or can be performed periodically. Measurement periodicity, which defines the period with which the periodical measurement is performed. The reporting related information includes: Report mode, which defines the frequency of the report. The reporting can be performed immediately when the measurement result is available or it can be performed based on some specific thresholds. Report threshold, which defines the measurement threshold of the reporting, when the threshold is exceeded, the report is performed. Therefor, we proposed to introduce the PCC rules information related to the QoS montioring policy, including: QoS parameter to be measured, Measurement mode, Measurement periodicity, Report mode and Report threshold.","secretary_remarks":"Merged into S2-1906650","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25240,"status":"merged","reservation_date":"2019-05-05 16:03:47","uploaded":"2019-05-06 15:16:05","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":262.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905126.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905280","title":"Evaluation and Conclusion for Key Issue #7: Automotic GBR Service recovery after HO","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Overall evaluation of solutions for Key issue #7. - Conclusion proposal for Key issue #7.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25490,"status":"postponed","reservation_date":"2019-05-06 14:30:39","uploaded":"2019-05-07 12:56:08","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":36.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905280.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905284","title":"Update of Solution#22 for KI#7","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are made: 1) Resolve the following EN: Editor's note: It is FFS whether and how the UE's NAS layer is informed that GBR radio resource has not been allocated for the GBR QoS Flow non-accepted in the target NG-RAN. No notification to the UE is proposed because the benefit or use of notification to the UE is not clear. 2) Add solution evaluation. 3) Add some texts for clarity.","secretary_remarks":"Not Handled","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25480,"status":"not treated","reservation_date":"2019-05-06 14:34:33","uploaded":"2019-05-07 08:33:22","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":37.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905284.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905356","title":"Simplified version of solution #24 QoS monitoring for URLLC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This solution provides means for QoS monitoring for URLLC on the GTP based interaces, i.e. on N3 interface between UPF and NG-RAN as well as on the N9 interface between the UPF (PSA) and I-UPF. This solution is based on the specification of the measurements specified for GTP based N3 interface in TS 28.552 [1]. This measurement provides the average (arithmetic mean) GTP packet delay on the N3 interface. The measurement is optionally split into subcounters per QoS level (5QI). This measurement is obtained as: the time when receiving a GTP Echo Response message from the gNB at the egress GTP termination, minus time when sending\u00a0the GTP Echo Request to gNB at the\u00a0GTP ingress termination, obtained result is divided by two. OAM adjusts the N3 delay measurements by removal of the internal delay time in gNB [note: measurements defined in 28.552 [1] already specify gNB-CU internal delays, hence the internal delay at gNB-CU is available]. Each measurement is an integer representing the mean delay in microseconds. The number of measurements is equal to one. Measurement taken at UPF. Measurements are provided to OAM. QoS monitoring within NG-RAN and between NG-RAN and UE (Uu) will be specified by RAN WGs.","secretary_remarks":"Revision of S2-1904740 from S2#132. Revised in parallel session to S2-1906651.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25280,"status":"revised","reservation_date":"2019-05-06 20:12:05","uploaded":"2019-05-07 14:11:42","revisionof":"S2-1904740","revisedto":"S2-1906651","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":34.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905356.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905358","title":"Conclusion proposal for Key Issue #4","source":"Ericsson, Huawei, HiSilicon, China Telecom, Motorola Mobility, Lenovo, China Mobile, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper proposes conclusion for KI#4. Proposal #1: Using the sampled actual service packets as the monitoring packet in the QoS Monitoring solution. Proposal #2: The UL\/DL packet delay between UE and PSA UPF for per UE per QoS Flow are divided to the UL\/DL packet delay between UE and RAN and the UL\/DL packet delay between RAN and PSA UPF. The measurement mechanism for the UL\/DL packet delay of Uu interface depends on RAN decision, and RAN provides the UL\/DL packet delay result of Uu interface to the UPF via N3 interface. The PSA UPF calculates the UL\/DL packet delay between UE and UPF as the sum of i) the packet delay measurement result of Uu interface and ii) the packet delay of N3 (and possibly N9) interface. Proposal #3: The PCC framework is enhanced to activate or deactivate the QoS Monitoring for the QoS Flow. Changes in Rev1: Reference to solution 19 agreed at last meeting is added in the conclusion part. Conclude that the UE is activated to initiate packet delay measurement based on the instruction received from the RAN. Changes in Rev2: Revert the addition of the description on UE side in Rev1, and clarify that RAN node initiates the packet delay measurement of UL\/DL packet delay on Uu interface, based on the QoS Monitoring policy received from the SMF. Solution #X (Accumulated packet delay estimation for QoS monitoring and division of PDB) is also concluded for normative work. Changes in Rev3: Clarify that the QoS Monitoring can be performed on different granularities, i.e. per QoS Flow per UE level, or per node level, subject to the operators' configuration, and\/or 3rd party application request, and\/or PCF policy control. Accordingly, two alternative solutions are concluded. Changes in Rev4: Wording updates and cleanup. Changes in Rev5: Further clarify that SA WG2 conclude not to proceed to normative work until receiving feedback from RAN WGs. Changes in Rev6: SMF can determine QoS flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for a given QoS flow. Changes in Rev7: Clarify that the per node level measurement can use GTP packet delivery status message as defined in the 3GPP TS 28.552 [x]. Changes in Rev8: Correct evaluation of Method 2 aligned with S5 agreed CR in S5-193383.","secretary_remarks":"Revision of S2-1904684 from S2#132. Revised in parallel session to S2-1906652.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25250,"status":"revised","reservation_date":"2019-05-06 20:21:02","uploaded":"2019-05-07 14:11:42","revisionof":"S2-1904684","revisedto":"S2-1906652","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":5.0,"crrevision":8.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905358.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905363","title":"Inclusion of soln #24 QoS monitoring for URLLC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This solution provides means for QoS monitoring for URLLC on the GTP based interfaces, i.e. on N3 interface between UPF and NG-RAN as well as on the N9 interface between the UPF (PSA) and I-UPF. This solution is based on the specification of the measurements specified for GTP based N3 interface in TS 28.552 [1]. This measurement provides the average (arithmetic mean) GTP packet delay on the N3 interface. This measurement is obtained as: the time when receiving a GTP Echo Response message from the gNB at the egress GTP termination, minus time when sending\u00a0the GTP Echo Request message to gNB at the\u00a0GTP ingress termination, obtained result is divided by two. OAM adjusts the N3 delay measurements by removal of the internal delay time in gNB [note: measurements defined in 28.552 [1] already specify gNB-CU internal delays, hence the internal delay at gNB-CU is available]. Each measurement is an integer representing the mean delay in microseconds. Measurements taken at UPF. Measurements are provided to to OAM. QoS monitoring within NG-RAN and between NG-RAN and UE (Uu) will be specified by RAN WGs.","secretary_remarks":"Merged into S2-1906654","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25310,"status":"merged","reservation_date":"2019-05-06 20:50:41","uploaded":"2019-05-07 14:11:42","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1380.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905363.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905517","title":"5G URLLC: Optimizing Redundancy","source":"Nokia?, Nokia Shanghai Bell? , Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Alternative 1: Introduce the means for application\/UE to indicate to the network (SMF) the UE applies traffic redundancy at PDU Session level (traffic redundancy indication at PDU Session level). The UE can provide the traffic redundancy indication within the PDU Session establishment or PDU Session modification request. Alternative 2: PCF can be configured with the indication that redundant transmission is performed at UE level (traffic redundancy indication) for a given PDU Session (identified by the couple (DNN, S-NSSAI)) or for a set of applications or traffic flow(s) within a PDU Session. Information derived by SMF from PCF policies and\/or the UE indication within the PDU Session Establishment\/Modification request can be provided to the RAN and UPF as 'URLLC assistance information'. Other corrections proposed: Dual GTP-U approach - trigger for two N3 tunnels should be from SMF\/UPF, not from the NG-RAN. RAN should rather respond with two TEIDs based on decision by SMF\/UPF for duplicated GTP-U tunnels. Otherwise, this setup will not be synchronized if it is triggered by both. Transport layer redundancy - for DL, it erroneously states that the RAN sends it to the UPF. DL packet should be sent towards the UE. Changing Redundant functionality -> Redundancy functionality in the UPF\/RAN (to avoid negative connotation by the use of term redundant functionality). Rev 3(highlighted with green color): 1, In clause 5.33.2.1, change 'policies provided by PCF for redundant PDU session for the given application' to 'policies provided by PCF for the PDU session'. 2, In clause 5.33.2.3, proposes that capability of supporting redundant transmission at transport layer can be configured in SMF or UPF, and for latter case the SMF obtain this information via N4 negotiation.","secretary_remarks":"Revision of S2-1904696 from S2#132. Confirm Sources! Revised in parallel session to S2-1906521.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25050,"status":"revised","reservation_date":"2019-05-07 09:16:12","uploaded":"2019-05-07 13:37:43","revisionof":"S2-1904696","revisedto":"S2-1906521","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1217.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905517.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905518","title":"Correction on the late notification in simultaneous change of Branching Point\/ULCL and additional PSA","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: (1) Update the procedure about late notification, step 9 in clause 4.3.5.7 is moved forward to step 5a. Renumbering steps 10-12 to 9-11. (2) Remove the description about notification in step 3 in clause 4.3.6.3.","secretary_remarks":"Revised in parallel session to S2-1906526.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25200,"status":"revised","reservation_date":"2019-05-07 09:16:13","uploaded":"2019-05-07 13:37:43","revisionof":"","revisedto":"S2-1906526","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1416.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905518.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905519","title":"Clarifications on URLLC support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, Clarify that in this release URLLC is only supported for 3GPP access. No functionality is specified for URLLC in order to support Home Routed roaming scenario. PDU session serving URLLC should be always-on PDU session. 2, editorial modifications. Rev 2 Allow the UE or SMF to change a PDU Session from non always-on to always-on PDU session during PDU Session Modification.","secretary_remarks":"Revision of S2-1904651 from S2#132. Revised in parallel session to S2-1906522.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25070,"status":"revised","reservation_date":"2019-05-07 09:16:14","uploaded":"2019-05-07 13:37:43","revisionof":"S2-1904651","revisedto":"S2-1906522","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1141.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905519.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905520","title":"Update procedures related with always-on PDU session for URLLC service","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, During the PDU Session establishment and modification procedure, add descriptions that SMF can establish or modify the PDU session as an always-on PDU session. 2, editorial changes.","secretary_remarks":"Revised in parallel session to S2-1906523.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25100,"status":"revised","reservation_date":"2019-05-07 09:16:15","uploaded":"2019-05-07 13:37:43","revisionof":"","revisedto":"S2-1906523","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1417.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905520.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905521","title":"Update procedures to support PDB division","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update related procedures to support the provision of the CN PDB to the NG-RAN node.","secretary_remarks":"Revision of S2-1903740 from S2#132. Wait for RAN. Postponed.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25400,"status":"postponed","reservation_date":"2019-05-07 09:16:16","uploaded":"2019-05-07 13:37:43","revisionof":"S2-1903740","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1277.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905521.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905525","title":"Introduction of QoS Monitoring to assist URLLC Service","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of QoS Monitoring to assist URLLC service.","secretary_remarks":"Revision of S2-1903735 from S2#132. Revised in parallel session to S2-1906653.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25320,"status":"revised","reservation_date":"2019-05-07 09:19:27","uploaded":"2019-05-07 09:48:32","revisionof":"S2-1903735","revisedto":"S2-1906653","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":990.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905525.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905570","title":"Update description for E2E PDB division","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of description for E2E PDB division according to above reason for change: Change 'dynamic CN component of the PDB'\u00a0\u00a0to 'CN PDB', added abbreviation. Clarify the usage of CN PDB is to obtain more accurate PDB for RAN\u00a0; Clarify CN PDB is delivered per QoS Flow\u00a0; Add the CN PDB to the 5G QoS characteristics description\u00a0; Improve the description for better differentiation between CN PDB and dynamic CN PDB\u00a0; Mandate the the signaling of the dynamic CN PDB whenever an I-UPF is inserted by the SMF as well as the NG-RAN behavior when receiving it.","secretary_remarks":"Revision of S2-1904695 from S2#132. Revised in parallel session to S2-1906527.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25410,"status":"revised","reservation_date":"2019-05-07 09:40:29","uploaded":"2019-05-07 14:31:33","revisionof":"S2-1904695","revisedto":"S2-1906527","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1142.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905570.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905595","title":"QoS monitoring based on GTP-U paths","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS monitoring procedure is based on RTT estimation of GTP-U path and user plane functoin processing time. A cummulated estimated packet delay is calcualted as the sum of RTT\/2 of GTP-U path, estimated processing delay of GTP-U sender and the value of accumulated estimated packet dealy received from an upstream GTP-U end-point. QoS monitoring is performed by a GTP-U end-point that receive and store QoS including a packet delay budget parameter for QoS flow by comparing a received accumulated packet delay with the stored QoS parameter","secretary_remarks":"Revised in parallel session, merging S2-1905363, to S2-1906654.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25340,"status":"revised","reservation_date":"2019-05-07 10:00:42","uploaded":"2019-05-07 12:03:13","revisionof":"","revisedto":"S2-1906654","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1414.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905595.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905596","title":"QoS Notification control update - automatic GBR services recovery","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Soften the phrase by removing the term 'permanent'","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25510,"status":"postponed","reservation_date":"2019-05-07 10:00:43","uploaded":"2019-05-07 12:03:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1415.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905596.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905627","title":"Update PDU Session Establishment procedure regarding solution 4 in 23.725","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update PDU Session establishment procedure to support redundant transmission between UPF and RAN by supporting two I-UPFs. The SMF indicates the I-UPFs to forward the packet with the same GTP-U sequence number which receives from the PSA UPF to NG-RAN. The SMF indicates the I-UPFs to forward the packet with the same GTP-U sequence number which receives from the NG-RAN to UPF (PSA).","secretary_remarks":"Revision of S2-1904694 from S2#132. Noted in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25130,"status":"noted","reservation_date":"2019-05-07 10:23:42","uploaded":"2019-05-07 11:50:31","revisionof":"S2-1904694","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1265.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905627.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905672","title":"Update PDU Session Modification procedure regarding solution 4","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update PDU Session Modification procedure to support redundant transmission between PSA UPF and NG-RAN by supporting two I-UPFs.","secretary_remarks":"Revised in parallel session to S2-1906524.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25140,"status":"revised","reservation_date":"2019-05-07 10:49:42","uploaded":"2019-05-07 11:50:31","revisionof":"","revisedto":"S2-1906524","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1437.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905672.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905702","title":"QoS Monitoring to assist URLLC Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Information","abstract":"Summary of change: Add description of QoS Monitoring to assist URLLC service.","secretary_remarks":"Revision of S2-1902999 from S2#132. Revised in parallel session to S2-1906655.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25360,"status":"revised","reservation_date":"2019-05-07 11:05:55","uploaded":"2019-05-07 14:57:24","revisionof":"S2-1902999","revisedto":"S2-1906655","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1126.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905702.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905703","title":"QoS Monitoring to assist URLLC Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Information","abstract":"Summary of change: Introduction of QoS Monitoring to assist URLLC service.","secretary_remarks":"Revision of S2-1903000 from S2#132. Revised in parallel session, merging S2-1905126, to S2-1906650.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25380,"status":"revised","reservation_date":"2019-05-07 11:05:56","uploaded":"2019-05-07 14:57:24","revisionof":"S2-1903000","revisedto":"S2-1906650","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":227.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905703.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905704","title":"Update PDU Session Establishment procedure regarding solution 1 in TR 23.725","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Discussion","abstract":"Discusses the selection of an appropriate UPF based on the identity of the Secondary RAN node for the secondary PDU session for redundant handling during PDU Session establishing procedure. The proposal is that the secondary PDU session is established aft","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24920,"status":"noted","reservation_date":"2019-05-07 11:05:57","uploaded":"2019-05-07 14:57:24","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905704.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905705","title":"Update PDU Session Establishment procedure regarding solution 1 in TR 23.725","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The establishment of PDU Session requiring redundant handling for which the user plane goes via the Secondary RAN node is initiated after the Dual Connectivity is activated for the UE, e.g. triggered by the RAN when receiving the first RSN sent by the SMF. - The Master RAN shall report the Secondary RAN node information (i.e. PSCell Information) to the AMF if Dual Connectivity is activated for the UE. When establishing the PDU Session requiring redundant handling whose user plane goes via the Secondary RAN node, the AMF notifies the Secondary RAN node information to the SMF and the SMF can select an appropriate UPF as the PSA based on this information.","secretary_remarks":"Not Handled","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24930,"status":"not treated","reservation_date":"2019-05-07 11:05:57","uploaded":"2019-05-07 14:57:24","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1435.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905705.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905706","title":"Update PDU Session Establishment procedure regarding solution 1 in TR 23.725","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The establishment of PDU Session requiring redundant handling for which the user plane goes via the Secondary RAN node is initiated after the Dual Connectivity is activated for the UE, e.g. triggered by the RAN when receiving the first RSN sent by the SMF. - The Master RAN shall report the Secondary RAN node information (i.e., PSCell Information) to the AMF if Dual Connectivity is activated for the UE. When establishing the PDU Session requiring redundant handling whose user plane goes via the Secondary RAN node, the AMF notifies the Secondary RAN node information to the SMF and the SMF can select an appropriate UPF as the PSA based on this information.","secretary_remarks":"Not Handled","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24940,"status":"not treated","reservation_date":"2019-05-07 11:05:58","uploaded":"2019-05-07 14:57:24","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1443.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905706.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905772","title":"Update of Key Issue #7: 'Automatic GBR service recovery'","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The key issue is expanded to explain in more detail the problems that are likely to occur if the RAN does not adopt a different approach to admission control.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25470,"status":"noted","reservation_date":"2019-05-07 12:59:36","uploaded":"2019-05-07 14:54:37","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":38.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905772.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1905789","title":"Evaluation and conclusion for Key Issue #7 Automatic GBR service recovery after handover","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Overall evaluation and conclusions for key issue #7 are made.","secretary_remarks":"Revision of S2-1902113 from S2#131. Postponed in parallel session","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25500,"status":"postponed","reservation_date":"2019-05-07 13:58:18","uploaded":"2019-05-07 14:55:32","revisionof":"S2-1902113","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":32.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1905789.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906367","title":"S6b optional for ePDG connected to 5GS","source":"Cisco Systems Belgium","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Updates specification for making S6b optional for ePDG connected to SMF+PGW-C.","secretary_remarks":"Revision of S2-1905120.","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":26930,"status":"revised","reservation_date":"2019-05-16 17:56:45","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905120","revisedto":"S2-1906782","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"TEI16"}],"crnumber":1342.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906367.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906368","title":"S6b optional for ePDG connected to 5GS","source":"Cisco Systems, T-Mobile USA, AT&T","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For the interworking scenario for ePDG connected to SMF+PGW-C, make S6b interface optional between SMF+PGW-C and 3GPP AAA Server. The figures are updated to replace PCF+PCRF to PCF.","secretary_remarks":"Revision of S2-1905119. This CR was agreed","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":27000,"status":"agreed","reservation_date":"2019-05-16 17:56:46","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905119","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_S6b_Optional"}],"crnumber":1323.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-190418","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906368.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906369","title":"New WID: S6b Optional for ePDG connected 5GS","source":"Cisco Systems, TMobile USA, Verizon, AT&T","contact":"Irfan Ali","contact-id":74090,"tdoctype":"WID new","for":"Approval","abstract":"Proposes to make S6b optional when ePDG is connected to SMF+PGW-C","secretary_remarks":"Revision of S2-1905117.","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":26890,"status":"available","reservation_date":"2019-05-16 17:56:47","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905117","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906369.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906516","title":"Generalized text for redundant user planes in RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Generalize RAN description, so that redundant user plane resources are provided based on RSN, no matter how NG-RAN control plane topology is realised or configured.","secretary_remarks":"Revision of S2-1905042.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25490,"status":"revised","reservation_date":"2019-05-15 17:18:43","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905042","revisedto":"S2-1906731","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1307.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906516.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906517","title":"Generalized text for redundant user planes in RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Generalize description, so that redundant user plane resources are provided based on RSN, without restricting the description to Master\/secondary RAN nodes.","secretary_remarks":"Revision of S2-1905043. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25320,"status":"agreed","reservation_date":"2019-05-15 17:18:44","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905043","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1323.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906517.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906518","title":"UP connection Deactivation for URLLC PDU Session","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the Service Request and AN Releasae procedure to activate\/deactivate the User Plane of the PDU Sessions for URLLC or the (redundant) I-UPF(s) is to be added\/replaced\/removed. The PDU Session for URLLC is either with redudant I-UPFs or with redudant N3\/N9 tunnels.","secretary_remarks":"Revision of S2-1905107. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25370,"status":"agreed","reservation_date":"2019-05-15 17:18:45","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905107","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1138.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906518.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906519","title":"Clarification on redudant N3 tunnel solution -23.501","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN and UPF replicates the packet and assigns the same QoS Flow Id and GTP-U sequence number to them for the redundant transmission.","secretary_remarks":"Revision of S2-1905111.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25580,"status":"revised","reservation_date":"2019-05-15 17:18:46","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905111","revisedto":"S2-1906732","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1320.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906519.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906520","title":"Update procedures related to redundant transmission","source":"Huawei, HiSilicon, OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Update PDU Session Modification procedure to support removal of redundancy tunnel. 2. Clarify that SMF shall release URLLC QoS Flows by triggering PDU Session Modification procedure after Xn\/N2 HO procedure if only one AN Tunnel Info is provided by Target NG-RAN. 3. This method applies only to the scenario where the redundant CN tunnels of the PDU Session connect to the same RAN node and UPF. 4. Editorial modifications.","secretary_remarks":"Revision of S2-1905112, merging S2-1905113.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25600,"status":"revised","reservation_date":"2019-05-15 17:18:47","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905112","revisedto":"S2-1906733","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1203.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906520.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906521","title":"5G URLLC: Optimizing Redundancy","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Alternative 1: Introduce the means for application\/UE to indicate to the network (SMF) the UE applies traffic redundancy at PDU Session level (traffic redundancy indication at PDU Session level). The UE can provide the traffic redundancy indication within the PDU Session establishment or PDU Session modification request. Alternative 2: PCF can be configured with the indication that redundant transmission is performed at UE level (traffic redundancy indication) for a given PDU Session (identified by the couple (DNN, S-NSSAI)) or for a set of applications or traffic flow(s) within a PDU Session. Information derived by SMF from PCF policies and\/or the UE indication within the PDU Session Establishment\/Modification request can be provided to the RAN and UPF as 'URLLC assistance information'. Other corrections proposed: Dual GTP-U approach - trigger for two N3 tunnels should be from SMF\/UPF, not from the NG-RAN. RAN should rather respond with two TEIDs based on decision by SMF\/UPF for duplicated GTP-U tunnels. Otherwise, this setup will not be synchronized if it is triggered by both. Transport layer redundancy - for DL, it erroneously states that the RAN sends it to the UPF. DL packet should be sent towards the UE. Changing Redundant functionality -> Redundancy functionality in the UPF\/RAN (to avoid negative connotation by the use of term redundant functionality). Rev 3(highlighted with green color): 1, In clause 5.33.2.1, change 'policies provided by PCF for redundant PDU session for the given application' to 'policies provided by PCF for the PDU session'. 2, In clause 5.33.2.3, proposes that capability of supporting redundant transmission at transport layer can be configured in SMF or UPF, and for latter case the SMF obtain this information via N4 negotiation.","secretary_remarks":"Revision of S2-1905517. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25470,"status":"agreed","reservation_date":"2019-05-15 17:18:48","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905517","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1217.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906521.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906522","title":"Clarifications on URLLC support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, Clarify that in this release URLLC is only supported for 3GPP access. No functionality is specified for URLLC in order to support Home Routed roaming scenario. PDU session serving URLLC should be always-on PDU session. 2, editorial modifications. Rev 2 Allow the UE or SMF to change a PDU Session from non always-on to always-on PDU session during PDU Session Modification.","secretary_remarks":"Revision of S2-1905519.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25650,"status":"revised","reservation_date":"2019-05-15 17:18:49","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905519","revisedto":"S2-1906734","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1141.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906522.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906523","title":"Update procdures related with always-on PDU session for URLLC service","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, During the PDU Session establishment and modification procedure, add descriptions that SMF can establish or modify the PDU session as an always-on PDU session. 2, editorial changes.","secretary_remarks":"Revision of S2-1905520.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25670,"status":"revised","reservation_date":"2019-05-15 17:18:50","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905520","revisedto":"S2-1906735","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1417.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906523.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906524","title":"Update PDU Session Modification procedure regarding solution 4","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update PDU Session Modification procedure to support redundant transmission between PSA UPF and NG-RAN by supporting two I-UPFs.","secretary_remarks":"Revision of S2-1905672. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25560,"status":"agreed","reservation_date":"2019-05-15 17:18:51","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905672","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1437.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906524.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906525","title":"Conclusion proposal on KI#2 Supporting low latency and low jitter during handover procedure","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a conclusion for KI#2.","secretary_remarks":"Revision of S2-1905114.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25730,"status":"revised","reservation_date":"2019-05-15 17:18:52","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905114","revisedto":"S2-1906736","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":35.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906525.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906526","title":"Correction on the late notification in simultaneous change of Branching Point\/ULCL and additional PSA","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: (1) Update the procedure about late notification, step 9 in clause 4.3.5.7 is moved forward to step 5a. Renumbering steps 10-12 to 9-11. (2) Remove the description about notification in step 3 in clause 4.3.6.3.","secretary_remarks":"Revision of S2-1905518.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25750,"status":"revised","reservation_date":"2019-05-15 17:18:53","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905518","revisedto":"S2-1906737","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1416.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906526.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906527","title":"Update description for E2E PDB division","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of description for E2E PDB division according to above reason for change: Change 'dynamic CN component of the PDB'\u00a0\u00a0to 'CN PDB', added abbreviation. Clarify the usage of CN PDB is to obtain more accurate PDB for RAN\u00a0; Clarify CN PDB is delivered per QoS Flow\u00a0; Add the CN PDB to the 5G QoS characteristics description\u00a0; Improve the description for better differentiation between CN PDB and dynamic CN PDB\u00a0; Mandate the the signaling of the dynamic CN PDB whenever an I-UPF is inserted by the SMF as well as the NG-RAN behavior when receiving it.","secretary_remarks":"Revision of S2-1905570.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25870,"status":"revised","reservation_date":"2019-05-15 17:18:54","uploaded":"2019-05-19 20:07:54","revisionof":"S2-1905570","revisedto":"S2-1906730","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1142.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906527.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906618","title":"Exception sheet for 5G_URLLC","source":"Huawei","contact":"Maurice Pope","contact-id":648,"tdoctype":"WI exception request","for":"Approval","abstract":"Exception sheet for 5G_URLLC","secretary_remarks":"Created at meeting","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":26010,"status":"revised","reservation_date":"2019-05-16 17:56:59","uploaded":"2019-05-21 05:17:55","revisionof":"","revisedto":"S2-1906739","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906618.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906650","title":"QoS Monitoring to assist URLLC Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Information","abstract":"Summary of change: Introduction of QoS Monitoring to assist URLLC service.","secretary_remarks":"Revision of S2-1905703, merging S2-1905126","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":26170,"status":"available","reservation_date":"2019-05-16 18:41:39","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905703","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":227.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906650.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906651","title":"Simplified version of solution #24 QoS monitoring for URLLC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This solution provides means for QoS monitoring for URLLC on the GTP based interaces, i.e. on N3 interface between UPF and NG-RAN as well as on the N9 interface between the UPF (PSA) and I-UPF. This solution is based on the specification of the measurements specified for GTP based N3 interface in TS 28.552 [1]. This measurement provides the average (arithmetic mean) GTP packet delay on the N3 interface. The measurement is optionally split into subcounters per QoS level (5QI). This measurement is obtained as: the time when receiving a GTP Echo Response message from the gNB at the egress GTP termination, minus time when sending\u00a0the GTP Echo Request to gNB at the\u00a0GTP ingress termination, obtained result is divided by two. OAM adjusts the N3 delay measurements by removal of the internal delay time in gNB [note: measurements defined in 28.552 [1] already specify gNB-CU internal delays, hence the internal delay at gNB-CU is available]. Each measurement is an integer representing the mean delay in microseconds. The number of measurements is equal to one. Measurement taken at UPF. Measurements are provided to OAM. QoS monitoring within NG-RAN and between NG-RAN and UE (Uu) will be specified by RAN WGs.","secretary_remarks":"Revision of S2-1905356.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":26080,"status":"revised","reservation_date":"2019-05-16 18:41:40","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905356","revisedto":"S2-1906778","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":34.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906651.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906652","title":"Conclusion proposal for Key Issue #4","source":"Ericsson, Huawei, HiSilicon, China Telecom, Motorola Mobility, Lenovo, China Mobile, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper proposes conclusion for KI#4. Proposal #1: Using the sampled actual service packets as the monitoring packet in the QoS Monitoring solution. Proposal #2: The UL\/DL packet delay between UE and PSA UPF for per UE per QoS Flow are divided to the UL\/DL packet delay between UE and RAN and the UL\/DL packet delay between RAN and PSA UPF. The measurement mechanism for the UL\/DL packet delay of Uu interface depends on RAN decision, and RAN provides the UL\/DL packet delay result of Uu interface to the UPF via N3 interface. The PSA UPF calculates the UL\/DL packet delay between UE and UPF as the sum of i) the packet delay measurement result of Uu interface and ii) the packet delay of N3 (and possibly N9) interface. Proposal #3: The PCC framework is enhanced to activate or deactivate the QoS Monitoring for the QoS Flow. Changes in Rev1: Reference to solution 19 agreed at last meeting is added in the conclusion part. Conclude that the UE is activated to initiate packet delay measurement based on the instruction received from the RAN. Changes in Rev2: Revert the addition of the description on UE side in Rev1, and clarify that RAN node initiates the packet delay measurement of UL\/DL packet delay on Uu interface, based on the QoS Monitoring policy received from the SMF. Solution #X (Accumulated packet delay estimation for QoS monitoring and division of PDB) is also concluded for normative work. Changes in Rev3: Clarify that the QoS Monitoring can be performed on different granularities, i.e. per QoS Flow per UE level, or per node level, subject to the operators' configuration, and\/or 3rd party application request, and\/or PCF policy control. Accordingly, two alternative solutions are concluded. Changes in Rev4: Wording updates and cleanup. Changes in Rev5: Further clarify that SA WG2 conclude not to proceed to normative work until receiving feedback from RAN WGs. Changes in Rev6: SMF can determine QoS flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for a given QoS flow. Changes in Rev7: Clarify that the per node level measurement can use GTP packet delivery status message as defined in the 3GPP TS 28.552 [x]. Changes in Rev8: Correct evaluation of Method 2 aligned with S5 agreed CR in S5-193383.","secretary_remarks":"Revision of S2-1905358.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":26060,"status":"revised","reservation_date":"2019-05-16 18:41:41","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905358","revisedto":"S2-1906777","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":5.0,"crrevision":9.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906652.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906653","title":"Introduction of QoS Monitoring to assist URLLC Service","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of QoS Monitoring to assist URLLC service.","secretary_remarks":"Revision of S2-1905525.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":26110,"status":"available","reservation_date":"2019-05-16 18:41:42","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905525","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":990.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906653.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906654","title":"QoS monitoring based on GTP-U paths","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS monitoring procedure is based on RTT estimation of GTP-U path and user plane functoin processing time. A cummulated estimated packet delay is calcualted as the sum of RTT\/2 of GTP-U path, estimated processing delay of GTP-U sender and the value of accumulated estimated packet dealy received from an upstream GTP-U end-point. QoS monitoring is performed by a GTP-U end-point that receive and store QoS including a packet delay budget parameter for QoS flow by comparing a received accumulated packet delay with the stored QoS parameter","secretary_remarks":"Revision of S2-1905595, merging S2-1905363","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":26130,"status":"available","reservation_date":"2019-05-16 18:41:43","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905595","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1414.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906654.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906655","title":"QoS Monitoring to assist URLLC Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Information","abstract":"Summary of change: Add description of QoS Monitoring to assist URLLC service.","secretary_remarks":"Revision of S2-1905702.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":26150,"status":"available","reservation_date":"2019-05-16 18:41:44","uploaded":"2019-05-19 20:07:55","revisionof":"S2-1905702","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1126.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906655.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906730","title":"Update description for E2E PDB division","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of description for E2E PDB division according to above reason for change: Change 'dynamic CN component of the PDB'\u00a0\u00a0to 'CN PDB', added abbreviation. Clarify the usage of CN PDB is to obtain more accurate PDB for RAN\u00a0; Clarify CN PDB is delivered per QoS Flow\u00a0; Add the CN PDB to the 5G QoS characteristics description\u00a0; Improve the description for better differentiation between CN PDB and dynamic CN PDB\u00a0; Mandate the the signaling of the dynamic CN PDB whenever an I-UPF is inserted by the SMF as well as the NG-RAN behavior when receiving it.","secretary_remarks":"Revision of S2-1906527. Revised to S2-1906776.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":27220,"status":"available","reservation_date":"2019-05-19 19:38:19","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906527","revisedto":"S2-1906776","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1142.0,"crrevision":5.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906730.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906731","title":"Generalized text for redundant user planes in RAN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Generalize RAN description, so that redundant user plane resources are provided based on RSN, no matter how NG-RAN control plane topology is realised or configured.","secretary_remarks":"Revision of S2-1906516. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25300,"status":"agreed","reservation_date":"2019-05-19 19:38:21","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906516","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1307.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906731.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906732","title":"Clarification on redudant N3 tunnel solution -23.501","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN and UPF replicates the packet and assigns the same QoS Flow Id and GTP-U sequence number to them for the redundant transmission.","secretary_remarks":"Revision of S2-1906519. Revised in parallel session to S2-1906738.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":26780,"status":"available","reservation_date":"2019-05-19 19:38:22","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906519","revisedto":"S2-1906738","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1320.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906732.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906733","title":"Update procedures related to redundant transmission","source":"Huawei, HiSilicon, OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Update PDU Session Modification procedure to support removal of redundancy tunnel. 2. Clarify that SMF shall release URLLC QoS Flows by triggering PDU Session Modification procedure after Xn\/N2 HO procedure if only one AN Tunnel Info is provided by Target NG-RAN. 3. In the 1st change and 4th chage, clarify the redundant GTP-U tunnels are terminated at the same RAN node and UPF. 4. Editorial modifications.","secretary_remarks":"Revision of S2-1906520. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25440,"status":"agreed","reservation_date":"2019-05-19 19:38:23","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906520","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1203.0,"crrevision":5.0,"crcategory":"C","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906733.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906734","title":"Clarifications on URLLC support","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1, Clarify that in this release URLLC is only supported for 3GPP access. No functionality is specified for URLLC in order to support Home Routed roaming scenario. PDU session serving URLLC should be always-on PDU session. 2, editorial modifications.","secretary_remarks":"Revision of S2-1906522. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25500,"status":"agreed","reservation_date":"2019-05-19 19:38:25","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906522","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1141.0,"crrevision":4.0,"crcategory":"C","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906734.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906735","title":"Update procdures related with always-on PDU session for URLLC service","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: editorial changes.","secretary_remarks":"Revision of S2-1906523. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25530,"status":"agreed","reservation_date":"2019-05-19 19:38:26","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906523","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1417.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906735.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906736","title":"Conclusion on KI#2 Supporting low latency and low jitter during handover procedure","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a conclusion for KI#2.","secretary_remarks":"Revision of S2-1906525. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25600,"status":"agreed","reservation_date":"2019-05-19 19:38:28","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906525","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":35.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190432","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906736.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906737","title":"Correction on the late notification procedures of simultaneous change of Branching Point\/ULCL and additional PSA for a PDU session","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added early notification in step 2, and clarify in step 6 and 7. Late notification is covered in step 4, so notification in step 3 is only the notification discussed in URLLC WI, i.e. the notification sent before UPF activated. This should be clarified.","secretary_remarks":"Revision of S2-1906526. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25630,"status":"agreed","reservation_date":"2019-05-19 19:38:30","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906526","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1416.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906737.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906738","title":"Clarification on redundant N3 tunnel solution","source":"OPPO, Huawei, HiSilicon, China Telecom, China Unicom","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that RAN and UPF replicates the packet and assigns the same QoS Flow Id and GTP-U sequence number to them for the redundant transmission.","secretary_remarks":"Revision of S2-1906732. Agreed in parallel session. This was Block approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25410,"status":"agreed","reservation_date":"2019-05-19 19:38:32","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906732","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1320.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906738.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906739","title":"Exception sheet for 5G_URLLC","source":"Huawei","contact":"Maurice Pope","contact-id":648,"tdoctype":"WI exception request","for":"Approval","abstract":"Exception sheet for 5G_URLLC","secretary_remarks":"Revision of S2-1906618.","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":27320,"status":"revised","reservation_date":"2019-05-19 19:38:33","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906618","revisedto":"S2-1906809","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906739.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906776","title":"Update description for E2E PDB division","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of description for E2E PDB division according to above reason for change: Change 'dynamic CN component of the PDB' to 'CN PDB', added abbreviation. Clarify the usage of CN PDB is to obtain more accurate PDB for RAN ; Clarify CN PDB is delivered per QoS Flow ; Add the CN PDB to the 5G QoS characteristics description ; Improve the description for better differentiation between CN PDB and dynamic CN PDB ; Mandate the the signaling of the dynamic CN PDB whenever an I-UPF is inserted by the SMF.","secretary_remarks":"Revision of S2-1906730. This CR was agreed","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25850,"status":"agreed","reservation_date":"2019-05-19 19:39:04","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906730","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1142.0,"crrevision":6.0,"crcategory":"C","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906776.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906777","title":"Conclusion proposal for Key Issue #4","source":"Ericsson, Huawei, HiSilicon, China Telecom, Motorola Mobility, Lenovo, China Mobile, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper proposes conclusion for KI#4. Proposal #1: Using the sampled actual service packets as the monitoring packet in the QoS Monitoring solution. Proposal #2: The UL\/DL packet delay between UE and PSA UPF for per UE per QoS Flow are divided to the UL\/DL packet delay between UE and RAN and the UL\/DL packet delay between RAN and PSA UPF. The measurement mechanism for the UL\/DL packet delay of Uu interface depends on RAN decision, and RAN provides the UL\/DL packet delay result of Uu interface to the UPF via N3 interface. The PSA UPF calculates the UL\/DL packet delay between UE and UPF as the sum of i) the packet delay measurement result of Uu interface and ii) the packet delay of N3 (and possibly N9) interface. Proposal #3: The PCC framework is enhanced to activate or deactivate the QoS Monitoring for the QoS Flow. Changes in Rev1: Reference to solution 19 agreed at last meeting is added in the conclusion part. Conclude that the UE is activated to initiate packet delay measurement based on the instruction received from the RAN. Changes in Rev2: Revert the addition of the description on UE side in Rev1, and clarify that RAN node initiates the packet delay measurement of UL\/DL packet delay on Uu interface, based on the QoS Monitoring policy received from the SMF. Solution #X (Accumulated packet delay estimation for QoS monitoring and division of PDB) is also concluded for normative work. Changes in Rev3: Clarify that the QoS Monitoring can be performed on different granularities, i.e. per QoS Flow per UE level, or per node level, subject to the operators' configuration, and\/or 3rd party application request, and\/or PCF policy control. Accordingly, two alternative solutions are concluded. Changes in Rev4: Wording updates and cleanup. Changes in Rev5: Further clarify that SA WG2 conclude not to proceed to normative work until receiving feedback from RAN WGs. Changes in Rev6: SMF can determine QoS flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for a given QoS flow. Changes in Rev7: Clarify that the per node level measurement can use GTP packet delivery status message as defined in the 3GPP TS 28.552 [x]. Changes in Rev8 and higher: Correct evaluation of Method 2 aligned with S5 agreed CR in S5-193383.","secretary_remarks":"Revision of S2-1906652. This CR was agreed","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25680,"status":"agreed","reservation_date":"2019-05-19 19:39:06","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906652","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":5.0,"crrevision":10.0,"crcategory":"B","tsg_crp":"SP-190432","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906777.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906778","title":"Simplified version of solution #24 QoS monitoring for URLLC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This solution provides means for QoS monitoring for URLLC on the GTP based interaces, i.e. on N3 interface between UPF and NG-RAN as well as on the N9 interface between the UPF (PSA) and I-UPF. This solution is based on the specification of the measurements specified for GTP based N3 interface in TS 28.552 [1]. This measurement provides the average (arithmetic mean) GTP packet delay on the N3 interface. The measurement is optionally split into subcounters per QoS level (5QI). This measurement is obtained as: the time when receiving a GTP Echo Response message from the gNB at the egress GTP termination, minus time when sending the GTP Echo Request to gNB at the GTP ingress termination, obtained result is divided by two. OAM adjusts the N3 delay measurements by removal of the internal delay time in gNB [note: measurements defined in 28.552 [1] already specify gNB-CU internal delays, hence the internal delay at gNB-CU is available]. Each measurement is an integer representing the mean delay in microseconds. The number of measurements is equal to one. Measurement taken at UPF. Measurements are provided to OAM. QoS monitoring within NG-RAN and between NG-RAN and UE (Uu) will be specified by RAN WGs.","secretary_remarks":"Revision of S2-1906651. This CR was agreed","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25710,"status":"agreed","reservation_date":"2019-05-19 19:39:07","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906651","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":34.0,"crrevision":5.0,"crcategory":"C","tsg_crp":"SP-190432","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906778.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906782","title":"S6b optional for ePDG connected to 5GS","source":"Cisco Systems, T-Mobile USA, AT&T","contact":"Irfan Ali","contact-id":74090,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the IWK procedure with ePDG to use N10 instead of S6b to register and de-register the PGW-C when UE connects via ePDG.","secretary_remarks":"Revision of S2-1906367. This CR was agreed","agenda_item_sort_order":50,"ainumber":"6.","ainame":"Draft WI: N10 for PGW registration in HSS+UDM for ePDG connected to 5GS (N10_PGWReg)","tdoc_agenda_sort_order":27030,"status":"agreed","reservation_date":"2019-05-19 19:39:11","uploaded":"2019-05-19 20:07:57","revisionof":"S2-1906367","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5GS_S6b_Optional"}],"crnumber":1342.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-190418","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906782.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1906809","title":"Exception sheet for 5G_URLLC","source":"Huawei (5G_URLLC rapporteur)","contact":"Hui Ni","contact-id":48076,"tdoctype":"WI exception request","for":"Approval","abstract":"Exception sheet for 5G_URLLC","secretary_remarks":"e-mail revision 11 of S2-1906724. Approved","agenda_item_sort_order":44,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25950,"status":"available","reservation_date":"2019-05-24 14:08:24","uploaded":"2019-05-24 14:10:05","revisionof":"S2-1906739","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_133_Reno\/Docs\/S2-1906809.zip","group":"S2","meeting":"S2-133","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]