[{"name":"S2-1908667","title":"LS from CT WG3: LS on N6 routing information in AF acknowledgement","source":"CT WG3","contact":"Yali Yan","contact-id":66362,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is specifying Nsmf_EventExposure service to support the AF acknowledgement of UP path change event notification. In 3GPP TS 23.502, Subclause 5.6.7.2 for Enhancement of UP path management based on the coordination with AFs, it states: The AF can include N6 traffic routing information related to the new DNAI in a positive response sent to the SMF. Once the SMF receives the positive AF response, the SMF activates the UP path toward the new DNAI. When activating the UP path, the SMF configures the N6 traffic routing information in the AF response into the PSA on the UP path. After the UP path toward the new DNAI is activated, data is routed toward the new DNAI. If the SMF receives a negative response at any time, the SMF keeps using the original DNAI and may cancel related PSA relocation. CT WG3 understands that if the SMF receives the AF acknowledgement indicates successful but not include N6 traffic routing information for the target DNAI, it means the N6 traffic routing information remains the same. Accordingly, CT WG3 would like to ask SA WG2 the following questions: 1. Whether CT WG3's understanding aligns with stage 2? 2. If yes, then in the case as follows: if the AF does not provide the N6 routing information but just subscribe the event of UP path change notification in the previous traffic influence message via NEF and PCF, when the event is detected by the SMF, the SMF will notify the AF directly or via NEF of the UP path change event. If the AF includes the N6 traffic routing information in the acknowledgement to the SMF, then the SMF will access to the indicated N6 data network. After that, for instance, if the PDU session is re-established and the SMF is changed, the new SMF is not aware of the N6 traffic routing information, because it is unclear how the new SMF retrieve such information from the old SMF. in this case, the AF acknowledgement does not include the N6 traffic routing information, how the new SMF access to the desired AF?. Action: CT WG3 kindly asks SA WG2 to answer above question and to update their specifications if necessary.","secretary_remarks":"Responses drafted in S2-1908938 and S2-1909043. Final response in S2-1910592","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23310,"status":"replied to","reservation_date":"2019-09-16 19:37:37","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-193643","lsreply":"S2-1910592","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908667.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908698","title":"LS from RAN WG3: LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity","source":"RAN WG3","contact":"Nianshan Shi","contact-id":45408,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has discussed Solution #1 of KI 1, especially about how the RSN is to be used by NG-RAN node, and if PDU Session pair information (i.e. the two PDU sessions are indicated as the redundant pair) is needed. There is consensus that RSN may work. However, if PDU session pair information is not provided (within RSN or otherwise), this may imply a change in the way the MN selects the SN for DC: according to current principles, this selection shall ultimately be based on radio and RAN load conditions (which is available to RAN and not to core network). The same considerations apply when one gNB-CU and two gNB-DUs are used. RAN WG3 sees benefit if 5GC can provide the PDU session pair information to gain more flexibility in NG-RAN node, but RAN WG3 is not sure if the 5GC would be able to provide this information to NG-RAN node without adding too much complexity. Action: RAN WG3 kindly asks SA WG2 to clarify the above.","secretary_remarks":"Response drafted in S2-1909599. Postponed in parallel session","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23380,"status":"postponed","reservation_date":"2019-09-16 19:37:38","uploaded":"2019-09-16 21:37:53","revisionof":"","revisedto":"S2-1910861","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-194794","lsreply":"S2-1911101","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908698.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908885","title":"Update N4 rules for QoS Monitoring","source":"Huawei, HiSilicon","contact":"Shufeng Shi","contact-id":56675,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Update the N4 rules to support QoS Monitoring. - Update the description of QoS Monitoring to assist URLLC service. - Clarify that if the redundant transmission on N3\/N9 interfaces is activated, the UPF and NG-RAN performs QoS monitoring for both UP paths. The UPF takes the best QoS measurement, e.g. the smallest packet delay, of the two UP paths as the QoS monitoring result.","secretary_remarks":"Revised in parallel session, merging S2-1909627, to S2-1910088.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23500,"status":"revised","reservation_date":"2019-09-30 03:19:40","uploaded":"2019-10-02 23:55:04","revisionof":"","revisedto":"S2-1910088","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1716.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908885.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908886","title":"Update on services\/procedures for QoS Monitoring","source":"Huawei, HiSilicon","contact":"Shufeng Shi","contact-id":56675,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides the QoS Monitoring reporting frequency to RAN by SMF. Clarify that the UPF reports to the SMF the smallest packet delay measured on the two UP paths in case of redundant transmission. Similar as Early and\/or late notifications about UP path management events, update Npcf_PolicyAuthorization_Create\/Update to support the subscription of QoS Monitoring Parateters event.","secretary_remarks":"Revised in parallel session to S2-1910089.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23520,"status":"revised","reservation_date":"2019-09-30 03:19:41","uploaded":"2019-10-02 23:55:04","revisionof":"","revisedto":"S2-1910089","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1691.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908886.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908887","title":"Correction on Policy Control information to support QoS Monitoring","source":"Huawei, HiSilicon","contact":"Shufeng Shi","contact-id":56675,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS Parameters Monitoring is added into the Policy Control Request Triggers supported by the SMF. Information from the AF for QoS Monitoring Parameters is added as input for PCC decision. Description of the QoS Monitoring parameters for URLLC is updated to make it clearer.","secretary_remarks":"WI Code should be 5G_URLLC. Revised in parallel session to S2-1910090.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23540,"status":"revised","reservation_date":"2019-09-30 03:19:42","uploaded":"2019-10-02 23:55:04","revisionof":"","revisedto":"S2-1910090","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":320.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908887.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908938","title":"[DRAFT] Reply LS on N6 routing information in AF acknowledgement","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS reply to S2-1908667\/C3-193643 on AF ack.","secretary_remarks":"Response to S2-1908667. Revised in parallel session to S2-1910085.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23320,"status":"revised","reservation_date":"2019-09-30 08:39:08","uploaded":"2019-10-04 08:54:10","revisionof":"","revisedto":"S2-1910085","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1908938.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909042","title":"Enhancement of UP path management based on the coordination with AFs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the SMF shall not be changed in the enhanced UP path management.","secretary_remarks":"Revised in parallel session to S2-1910591.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23360,"status":"revised","reservation_date":"2019-10-01 01:29:45","uploaded":"2019-10-04 14:04:06","revisionof":"","revisedto":"S2-1910591","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1742.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909042.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909043","title":"[DRAFT] Reply LS on N6 routing information in AF acknowledgement","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This CR responds to CT WG3 that SMF is not changed for enhancement of UP path management","secretary_remarks":"Response to S2-1908667 Not Handled","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23350,"status":"not treated","reservation_date":"2019-10-01 01:29:46","uploaded":"2019-10-04 14:04:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909043.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909059","title":"Establish redundant N3\/N9 transmission for an existing QoS Flow","source":"Intel","contact":"Changhong Shan","contact-id":45586,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enable SMF to activate redundant N3\/N9 transmission for an existing QoS Flow, e.g. a handovered QoS Flow.","secretary_remarks":"Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23580,"status":"agreed","reservation_date":"2019-10-01 05:07:09","uploaded":"2019-10-01 05:45:36","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1726.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909059.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909161","title":"Delivery of SMF waiting time to AF for session continuity","source":"Samsung Electronics","contact":"Yoonseon Han","contact-id":76429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delivery SMF's waiting time to AF using an early\/late notification for service and session continuity.","secretary_remarks":"WI Code should be 5G_URLLC. Revised in parallel session to S2-1910594.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23590,"status":"revised","reservation_date":"2019-10-02 05:03:54","uploaded":"2019-10-04 08:35:54","revisionof":"","revisedto":"S2-1910594","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1768.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909161.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909162","title":"Delivery of SMF waiting time to AF for session continuity","source":"Samsung Electronics","contact":"Yoonseon Han","contact-id":76429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delivery SMF's waiting time to AF using an early\/late notification for service and session continuity.","secretary_remarks":"WI Code should be 5G_URLLC. Not Handled","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23620,"status":"not treated","reservation_date":"2019-10-02 05:07:03","uploaded":"2019-10-04 08:35:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1765.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909162.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909433","title":"Clarification on the Standardized or pre-configured 5QI parameters modification","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding clause 5.7.3.4 as a condition to trigger sending the standardized or pre-configured 5G QoS characteristics.","secretary_remarks":"Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23630,"status":"agreed","reservation_date":"2019-10-03 04:32:17","uploaded":"2019-10-04 16:21:01","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1816.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909433.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909597","title":"Clarifications to Dual Connectivity based Redundancy","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"We discuss the questions raised in RAN WG3's incoming LS and propose a way forward.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23410,"status":"noted","reservation_date":"2019-10-03 20:43:20","uploaded":"2019-10-04 16:39:27","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_135_Split\/Docs\/S2-1909597.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909598","title":"Clarifications to dual connectivity based redundancy","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the RSN parameter, in combination with RAN configuration, determines the user plane resources to be used.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23420,"status":"postponed","reservation_date":"2019-10-03 20:43:20","uploaded":"2019-10-04 16:39:27","revisionof":"","revisedto":"S2-1911099","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1856.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909598.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909599","title":"[DRAFT] Reply LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 would like to give the following in response to RAN WG3's LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity.","secretary_remarks":"Response to S2-1908698. Revised in parallel session to S2-1910087.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23390,"status":"revised","reservation_date":"2019-10-03 20:43:21","uploaded":"2019-10-04 16:39:27","revisionof":"","revisedto":"S2-1910087","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909599.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909626","title":"Updating the User Plane Function Selection for supporting redundant transmission","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the UPF Selection regarding supporting URLLC service.","secretary_remarks":"Merged into S2-1910091","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23640,"status":"merged","reservation_date":"2019-10-04 01:05:51","uploaded":"2019-10-04 14:40:38","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1862.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909626.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909627","title":"Correction on Per QoS Flow UE QoS Monitoring","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add 'UL monitoring packet' in the sentence.","secretary_remarks":"Merged into S2-1910088","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23680,"status":"merged","reservation_date":"2019-10-04 01:07:45","uploaded":"2019-10-04 14:40:38","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1863.0,"crrevision":"","crcategory":"D","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909627.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909713","title":"5G URLLC Handling PDU Session Failure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify all the points above: Clarify that the RAN rejects or accepts the request to establish dual connectivity based on RSN parameter, considering RAN resources availability. Then SMF uses this to determine whether PDU Session is rejected or not. Clarify that the request is rejected when the RAN decides not to accept the request to establish UP resources for PDU Session. Clearly clarify that the failure to establish subsequent (redundant) PDU Session shall not impact the previously established PDU Session with the RSN parameter set.","secretary_remarks":"Revised in parallel session to S2-1910092.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23690,"status":"revised","reservation_date":"2019-10-04 07:40:11","uploaded":"2019-10-04 12:44:05","revisionof":"","revisedto":"S2-1910092","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1878.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909713.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909714","title":"5G URLLC Handling PDU Session Failure - 23.502","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify all the points above: Clarify that the RAN rejects or accepts the request to establish dual connectivity based on RSN parameter, considering RAN resources availability. Then SMF uses this to determine whether PDU Session is rejected or not. Clarify that the request is rejected when the RAN decides not to accept the request to establish UP resources for PDU Session. Clearly clarify that the failure to establish subsequent (redundant) PDU Session shall not impact the previously established PDU Session with the RSN parameter set.","secretary_remarks":"Wrong CR rev number on cover sheet. Revised in parallel session to S2-1910093.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23720,"status":"revised","reservation_date":"2019-10-04 07:40:13","uploaded":"2019-10-04 12:44:05","revisionof":"","revisedto":"S2-1910093","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1847.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909714.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909715","title":"UPF selection for 5G URLLC PDU Sessions","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that an SMF should select a UPF (e.g. based on the need to activate redundant GTP-U\/Transport paths). Also clarify that the NRF based discovery\/selection is not precluded for UPF (considering redundant path), which is already supported for UPF anyhow.","secretary_remarks":"Revised in parallel session, merging S2-1909626, to S2-1910091.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23650,"status":"revised","reservation_date":"2019-10-04 07:40:14","uploaded":"2019-10-04 12:44:05","revisionof":"","revisedto":"S2-1910091","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1879.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909715.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909769","title":"5G URLLC Handling redundant PDU Sessions","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Analysis: SMF will not have PDU Session pair information when first PDU Session information. This is not available at the UE nor provided by the UE. At the time of second PDU Session establishment, old PDU Session ID is available. If there are multiple SMFs, this is not available at the SMF. Thus the following are the only possible options: - UE provides the old PDU Session ID information as part of second request. It is assumed that there is always only one SMF that manages the redundant PDU Session. Since UE impact was rejected \/ ruled out in the past, it is proposed that we state that the assumption is that there is only one SMF always for this approach to work. For the first PDU Session, only RSN is available to indicate to the RAN. Thus it is proposed to use RSN for 1st session request, both RSN and old PDU Session ID for 2nd session request.","secretary_remarks":"Revised in parallel session to S2-1910086.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23430,"status":"revised","reservation_date":"2019-10-04 10:45:52","uploaded":"2019-10-04 12:44:05","revisionof":"","revisedto":"S2-1910086","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1896.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909769.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909850","title":"Discussion on PDU session pair information between two SMFs","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses how the PDU session pair information is provided to the NG-RAN in case of two SMFs are used.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23450,"status":"noted","reservation_date":"2019-10-04 15:50:13","uploaded":"2019-10-04 16:10:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909850.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909852","title":"Clarification on PDU session pair information to NG-RAN (Option 1)","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added a clarification that the SMF determines the PDU session pair information on which PDU Sessions are paired for redundant transmission. When the paired PDU Session is served by other SMF, the SMF obtains the PDU session pair information for the paired PDU Session from the UDM.","secretary_remarks":"Not Handled","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23460,"status":"not treated","reservation_date":"2019-10-04 15:52:23","uploaded":"2019-10-04 16:10:57","revisionof":"","revisedto":"S2-1911234","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1908.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909852.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909855","title":"Clarification on PDU session pair information to NG-RAN (Option 1)","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added a clarification that the SMF determines the PDU session pair information on which PDU Sessions are paired for redundant transmission. When the paired PDU Session is served by other SMF, the SMF obtains the PDU session pair information for the paired PDU Session from the UDM.","secretary_remarks":"Not Handled","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23470,"status":"not treated","reservation_date":"2019-10-04 15:54:32","uploaded":"2019-10-04 16:10:57","revisionof":"","revisedto":"S2-1911235","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1862.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909855.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909856","title":"Clarification on PDU session pair information to NG-RAN (Option 2)","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added a clarification that the SMF determines the PDU session pair information on which PDU Sessions are paired for redundant transmission. When the paired PDU Session is served by other SMF, the SMF obtains the PDU session pair information for the paired PDU Session from the PCF.","secretary_remarks":"Not Handled","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23480,"status":"not treated","reservation_date":"2019-10-04 15:56:36","uploaded":"2019-10-04 16:10:57","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1909.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909856.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909859","title":"Clarification on PDU session pair information to NG-RAN (Option 2)","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added a clarification that the SMF determines the PDU session pair information on which PDU Sessions are paired for redundant transmission. When the paired PDU Session is served by other SMF, the SMF obtains the PDU session pair information for the paired PDU Session from the PCF.","secretary_remarks":"Not Handled","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23490,"status":"not treated","reservation_date":"2019-10-04 15:59:16","uploaded":"2019-10-04 16:10:57","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1863.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909859.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1909960","title":"LS from CT WG4: LS on QoS monitoring in GTP-U","source":"CT WG4","contact":"Caixia Qi","contact-id":56676,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 has discussed how to implement the GTP-U impacts to support the stage 2 requirements on Per QoS Flow per UE QoS Monitoring mechanism, and agreed that extending the current PDU Session Container extension header to include the information for packet delay measurement together with the QFI, e.g. timestamp of NG-RAN\/UPF, delay value on Uu interface, is a preferred way forward. CT WG4 kindly requests RAN WG3 to consider updating the definition of PDU Session Container extension header accordingly, if agreeable to RAN WG3. Besides, the solution specified in TS 23.501 when NG-RAN and UPF are not synchronized requires the PSA UPF to store a downlink timestamp and to correlate the uplink packet using a new sequence number sent forth and back for this purpose in DL and UL G-PDUs. It was pointed out during the discussion that the UPF (PSA) could alternatively include the timestamp of when it sends the downlink packet in the GTP-U header of the DL packet (like also done in the time synchronised solution) with the NG-RAN sending back this timestamp to the PSA UPF in the UL packets. The PSA UPF would then not need to store the downlink timestamp nor to correlate downlink and uplink packets for QoS monitoring, as all the information would then be included in the uplink packet sent by NG-RAN. CT WG4 kindly asks SA WG2 whether they have considered the alternative solution and if not, whether this solution would be acceptable. Action: CT WG4 kindly requests RAN WG3 and SA WG2 to take the information above into account and provide feedback.","secretary_remarks":"Response drafted in S2-1910084. Final response in S2-1910084","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23290,"status":"replied to","reservation_date":"2019-10-11 13:25:15","uploaded":"2019-10-11 13:25:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, SA WG2","Cc":"","lsoriginalls":"C4-194501","lsreply":"S2-1910084, S2-1910084","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1909960.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910084","title":"Reply LS on QoS monitoring in GTP-U","source":"SA WG2","contact":"Susan Shi","contact-id":37231,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, RAN WG3. Attachments: S2-1910088 (23.501 CR 1716)","secretary_remarks":"Created at meeting. Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23300,"status":"approved","reservation_date":"2019-10-15 06:40:35","uploaded":"2019-10-19 07:48:02","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1909960","lsto":"CT WG4, RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910084.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910085","title":"[DRAFT] Reply LS on N6 routing information in AF acknowledgement","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS reply to S2-1908667\/C3-193643 on AF ack.","secretary_remarks":"Revision of S2-1908938. Revised in parallel session to S2-1910592.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23330,"status":"revised","reservation_date":"2019-10-15 06:40:35","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1908938","revisedto":"S2-1910592","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910085.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910086","title":"5G URLLC Handling redundant PDU Sessions","source":"Nokia, Nokia Shanghai Bell, Samsung","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Analysis: SMF will not have PDU Session pair information when first PDU Session information. This is not available at the UE nor provided by the UE. At the time of second PDU Session establishment, old PDU Session ID is available. If there are multiple SMFs, this is not available at the SMF. Thus the following are the only possible options: - UE provides the old PDU Session ID information as part of second request. It is assumed that there is always only one SMF that manages the redundant PDU Session. Since UE impact was rejected \/ ruled out in the past, it is proposed that we state that the assumption is that there is only one SMF always for this approach to work. For the first PDU Session, only RSN is available to indicate to the RAN. Thus it is proposed to use RSN for 1st session request, both RSN and old PDU Session ID for 2nd session request.","secretary_remarks":"Revision of S2-1909769. Postponed in parallel session","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23440,"status":"postponed","reservation_date":"2019-10-15 06:40:35","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1909769","revisedto":"S2-1910965","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1896.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910086.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910087","title":"[DRAFT] Reply LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 would like to give the following in response to RAN WG3's LS on Solution #1 of Key Issue 1: Redundant user plane paths based on dual connectivity.","secretary_remarks":"Revision of S2-1909599. Withdrawn","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23400,"status":"withdrawn","reservation_date":"2019-10-15 06:40:36","uploaded":null,"revisionof":"S2-1909599","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910088","title":"Update N4 rules for QoS Monitoring","source":"Huawei, HiSilicon","contact":"Shufeng Shi","contact-id":56675,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Update the N4 rules to support QoS Monitoring. - Update the description of QoS Monitoring to assist URLLC service. - Clarify that if the redundant transmission on N3\/N9 interfaces is activated, the UPF and NG-RAN performs QoS monitoring for both UP paths. The UPF takes the best QoS measurement, e.g. the smallest packet delay, of the two UP paths as the QoS monitoring result.","secretary_remarks":"Revision of S2-1908885, merging S2-1909627. Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23510,"status":"agreed","reservation_date":"2019-10-15 06:40:36","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1908885","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1716.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910088.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910089","title":"Update on services\/procedures for QoS Monitoring","source":"Huawei, HiSilicon","contact":"Shufeng Shi","contact-id":56675,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Provides the QoS Monitoring reporting frequency to RAN by SMF. Clarify that the UPF reports to the SMF the smallest packet delay measured on the two UP paths in case of redundant transmission. Similar as Early and\/or late notifications about UP path management events, update Npcf_PolicyAuthorization_Create\/Update to support the subscription of QoS Monitoring Parateters event.","secretary_remarks":"Revision of S2-1908886. Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23530,"status":"agreed","reservation_date":"2019-10-15 06:40:38","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1908886","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1691.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910089.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910090","title":"Correction on Policy Control information to support QoS Monitoring","source":"Huawei, HiSilicon","contact":"Shufeng Shi","contact-id":56675,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS Parameters Monitoring is added into the Policy Control Request Triggers supported by the SMF. Information from the AF for QoS Monitoring Parameters is added as input for PCC decision. Description of the QoS Monitoring parameters for URLLC is updated to make it clearer.","secretary_remarks":"Revision of S2-1908887. Revised in parallel session to S2-1910593.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23550,"status":"revised","reservation_date":"2019-10-15 06:40:39","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1908887","revisedto":"S2-1910593","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":320.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910090.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910091","title":"UPF selection for 5G URLLC PDU Sessions","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that an SMF should select a UPF (e.g. based on the need to activate redundant GTP-U\/Transport paths). Also clarify that the NRF based discovery\/selection is not precluded for UPF (considering redundant path), which is already supported for UPF anyhow.","secretary_remarks":"Revision of S2-1909715, merging S2-1909626. Revised in parallel session to S2-1910595.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23660,"status":"revised","reservation_date":"2019-10-15 06:40:40","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1909715","revisedto":"S2-1910595","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1879.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910091.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910092","title":"5G URLLC Handling PDU Session Failure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify all the points above: Clarify that the RAN rejects or accepts the request to establish dual connectivity based on RSN parameter, considering RAN resources availability. Then SMF uses this to determine whether PDU Session is rejected or not. Clarify that the request is rejected when the RAN decides not to accept the request to establish UP resources for PDU Session. Clearly clarify that the failure to establish subsequent (redundant) PDU Session shall not impact the previously established PDU Session with the RSN parameter set.","secretary_remarks":"Revision of S2-1909713. Revised in parallel session to S2-1910596.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23700,"status":"revised","reservation_date":"2019-10-15 06:40:41","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1909713","revisedto":"S2-1910596","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1878.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910092.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910093","title":"5G URLLC Handling PDU Session Failure - 23.502","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify all the points above: Clarify that the RAN rejects or accepts the request to establish dual connectivity based on RSN parameter, considering RAN resources availability. Then SMF uses this to determine whether PDU Session is rejected or not. Clarify that the request is rejected when the RAN decides not to accept the request to establish UP resources for PDU Session. Clearly clarify that the failure to establish subsequent (redundant) PDU Session shall not impact the previously established PDU Session with the RSN parameter set.","secretary_remarks":"Revision of S2-1909714. Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23730,"status":"agreed","reservation_date":"2019-10-15 06:40:43","uploaded":"2019-10-19 07:48:02","revisionof":"S2-1909714","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1847.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910093.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910591","title":"Enhancement of UP path management based on the coordination with AFs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the SMF shall not be changed in the enhanced UP path management.","secretary_remarks":"Revision of S2-1909042. This was left for e-mail approval. This CR was agreed","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23370,"status":"agreed","reservation_date":"2019-10-19 05:42:21","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1909042","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1742.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910591.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910592","title":"Reply LS on N6 routing information in AF acknowledgement","source":"SA WG2","contact":"Hui Ni","contact-id":48076,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4. Cc: RAN WG3. Attachments: S2-1910498 (TS 23.502 CR#1868)","secretary_remarks":"Revision of S2-1910085. Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23340,"status":"approved","reservation_date":"2019-10-19 05:42:22","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910085","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1908667","lsto":"RAN WG2, RAN WG3","Cc":"TSG RAN","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910592.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910593","title":"Correction on Policy Control information to support QoS Monitoring","source":"Huawei, HiSilicon","contact":"Shufeng Shi","contact-id":56675,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS Parameters Monitoring is added into the Policy Control Request Triggers supported by the SMF. Information from the AF for QoS Monitoring Parameters is added as input for PCC decision. Description of the QoS Monitoring parameters for URLLC is updated to make it clearer.","secretary_remarks":"Revision of S2-1910090. This was left for e-mail approval. This CR was agreed. e-mail revision 1 approved. Revised to S2-1910794.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23560,"status":"revised","reservation_date":"2019-10-19 05:42:22","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910090","revisedto":"S2-1910794","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":320.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910593.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910594","title":"Delivery of SMF waiting time to AF for session continuity","source":"Samsung Electronics, Huawei, HiSilicon","contact":"Yoonseon Han","contact-id":76429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delivery SMF's waiting time to AF using an early\/late notification for service and session continuity.","secretary_remarks":"Revision of S2-1909161. Revised in parallel session to S2-1910597.","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23600,"status":"revised","reservation_date":"2019-10-19 05:42:24","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1909161","revisedto":"S2-1910597","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1768.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910594.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910595","title":"UPF selection for 5G URLLC PDU Sessions","source":"Nokia, Nokia Shanghai Bell, Samsung","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that an SMF should select a UPF (e.g. based on the need to activate redundant GTP-U\/Transport paths). Also clarify that the NRF based discovery\/selection is not precluded for UPF (considering redundant path), which is already supported for UPF anyhow.","secretary_remarks":"Revision of S2-1910091. Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23670,"status":"agreed","reservation_date":"2019-10-19 05:42:25","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910091","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1879.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910595.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910596","title":"5G URLLC Handling PDU Session Failure","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to clarify all the points above: Clarify that the RAN rejects or accepts the request to establish dual connectivity based on RSN parameter, considering RAN resources availability. Then SMF uses this to determine whether PDU Session is rejected or not. Clarify that the request is rejected when the RAN decides not to accept the request to establish UP resources for PDU Session. Clearly clarify that the failure to establish subsequent (redundant) PDU Session shall not impact the previously established PDU Session with the RSN parameter set.","secretary_remarks":"Revision of S2-1910092. Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23710,"status":"agreed","reservation_date":"2019-10-19 05:42:27","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910092","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1878.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910596.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910597","title":"Delivery of SMF waiting time to AF for session continuity","source":"Samsung Electronics, Huawei, HiSilicon","contact":"Yoonseon Han","contact-id":76429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Delivery SMF's waiting time to AF using an early\/late notification for service and session continuity.","secretary_remarks":"Revision of S2-1910594. Agreed in parallel session This was Block approved","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23610,"status":"agreed","reservation_date":"2019-10-19 05:42:28","uploaded":"2019-10-19 07:48:13","revisionof":"S2-1910594","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1768.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910597.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910794","title":"Correction on Policy Control information to support QoS Monitoring","source":"Huawei, HiSilicon","contact":"Shufeng Shi","contact-id":56675,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: QoS Parameters Monitoring is added into the Policy Control Request Triggers supported by the SMF. Information from the AF for QoS Monitoring Parameters is added as input for PCC decision. Description of the QoS Monitoring parameters for URLLC is updated to make it clearer.","secretary_remarks":"e-mail revision 1 of.S2-1910593. This CR was agreed","agenda_item_sort_order":38,"ainumber":"7.10.1","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":23570,"status":"agreed","reservation_date":"2019-10-28 11:11:19","uploaded":"2019-10-28 15:13:49","revisionof":"S2-1910593","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":320.0,"crrevision":3.0,"crcategory":"C","tsg_crp":"SP-191073","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_135_Split\/Docs\/S2-1910794.zip","group":"S2","meeting":"S2-135","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]