[{"name":"S2-1906879","title":"LS from RAN WG3: LS on Solution 1 of 5G_URLLC","source":"RAN WG3","contact":"Zijiang Ma","contact-id":36270,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 has discussed solution 1 related to Higher Layer Multi-Connectivity, then RAN WG3 asks the following questions. Q1: We understand that the value of the RSN parameter is an index that indicates redundant user plane requirements for the PDU Sessions. Does it mean this index points to a particular UPF and a particular NG-RAN User Plane (UP) pair? Or it is only at the UPF side, i.e. NG-RAN is free to choose the user plane? For example, does it mean that UPF1\/NG-RAN UP 1 are always selected when NG-RAN node receives RSN equals 1 and UPF2\/NG-RAN UP 2 are always selected when NG-RAN node receives RSN equals 2 (i.e. UPF1\/NG-RAN UP1 used by PDU session with RSN=1 for all pairs subject of redundancy) Q2: TS 23.501 says that 'NG RAN notifies CN about failure to establish dual connectivity and SMF based on local policy decides whether to continue with the PDU session or initiate release of the PDU session.' If NG-RAN receives PDU session setup for the second PDU session and the indicated RSN is not possible to be setup, RAN WG3 discussed two possibilities in NG-RAN: Alternative 1: NG-RAN node configures the second PDU session to the same RSN as the first PDU session (e.g. MN) Alternative 2: NG-RAN shall fail the second PDU session setup. Is alternative 1 allowed? If it is allowed, should SMF be notified and further decide whether to continue with the second PDU session or initiate release of the second PDU session? Q3: If the two SMFs are involved, how do the two SMFs coordinate the following? (PDU Session 1 and 2 are redundant) 1. RSN settings when the PDU Session1 is setup by SMF 1, and when PDU session 2 is setup by SMF 2; 2. When NG-RAN notifies SMF2 the failure of PDU Session 2, how does SMF1 know which one is PDU session 1 and makes the decision to release or continue the PDU session 1. Action: RAN WG3 kindly asks SA WG2 to take the above information into account, and provide the feedback on the questions listed above.","secretary_remarks":"Response drafted in S2-1907077. Final response in S2-1908633","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24370,"status":"replied to","reservation_date":"2019-06-10 18:36:17","uploaded":"2019-06-12 11:37:53","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-193271","lsreply":"S2-1908633","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1906879.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907075","title":"Failure handling for redundancy based on dual connectivity","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new indication, RIT, is sent from CN to RAN which determines whether to keep the PDU Session or not in case the user plane resources as requested by the CN cannot be assigned.","secretary_remarks":"Revised in parallel session to S2-1908296.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":23970,"status":"revised","reservation_date":"2019-06-14 15:33:54","uploaded":"2019-06-18 14:01:52","revisionof":"","revisedto":"S2-1908296","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1489.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907075.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907076","title":"Failure handling for redundancy based on dual connectivity","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A new indication, RIT, is sent from CN to RAN which determines whether to keep the PDU Session or not in case the user plane resources as requested by the CN cannot be assigned.","secretary_remarks":"Revised in parallel session to S2-1908297.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":23990,"status":"revised","reservation_date":"2019-06-14 15:33:55","uploaded":"2019-06-18 14:01:52","revisionof":"","revisedto":"S2-1908297","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1499.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907076.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907077","title":"[DRAFT] Reply LS on Solution 1 of 5G_URLLC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 provides feedback on RAN WG3 questions regarding redundancy handling based on dual connectivity","secretary_remarks":"Response to S2-1906879. Revised in parallel session to S2-1908298.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24020,"status":"revised","reservation_date":"2019-06-14 15:33:56","uploaded":"2019-06-18 14:01:52","revisionof":"","revisedto":"S2-1908298","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_134_Sapporo\/Docs\/S2-1907077.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907078","title":"Clarification on reordering requirement with GTP-U redundancy","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that reordering is not performed for the redundancy function.","secretary_remarks":"Revised in parallel session to S2-1908352.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24090,"status":"revised","reservation_date":"2019-06-14 15:33:56","uploaded":"2019-06-18 03:21:21","revisionof":"","revisedto":"S2-1908352","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1490.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907078.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907160","title":"Clarifications on URLLC support","source":"OPPO","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resubmit the CR S2-1906522 agreed in last meeting but missed to be implemented, and addtinoally clarify that How the UE knows whether this PDU Session is for URLLC service is up to UE implementation.","secretary_remarks":"Merged into S2-1908351.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24080,"status":"merged","reservation_date":"2019-06-16 06:34:29","uploaded":"2019-06-17 12:09:56","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1512.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907160.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907281","title":"Improvement for support of redundant transmission on N3\/N9 interfaces","source":"Lenovo, Motorola Mobility","contact":"Tingfang Tang","contact-id":81429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates the description for supporting Redundant transmission on N3\/N9 interfaces as following: Restucture the description to make the mechanism having general description for the common parts for all the cases. Modify the description to include the case for establishing redundant transmission tunnel after the URLLC QoS flow establishment.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24530,"status":"agreed","reservation_date":"2019-06-17 07:30:32","uploaded":"2019-06-17 09:02:52","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1547.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907281.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907282","title":"Update of AN release procedure for URLLC service","source":"Lenovo, Motorola Mobility","contact":"Tingfang Tang","contact-id":81429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updates the description of AN release procedure to avoid removal of N3 UPF for deactivation of PDU session for URLLC service.","secretary_remarks":"Revised in parallel session to S2-1908353.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24120,"status":"revised","reservation_date":"2019-06-17 07:30:33","uploaded":"2019-06-17 09:02:52","revisionof":"","revisedto":"S2-1908353","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1530.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907282.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907632","title":"Clarification 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":"Requested by MCC to resubmit unimplemented CR. Revised in parallel session, merging S2-1907160, to S2-1908351.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24050,"status":"revised","reservation_date":"2019-06-18 08:04:39","uploaded":"2019-06-18 11:39:54","revisionof":"","revisedto":"S2-1908351","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1643.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907632.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907633","title":"Clarification and correction to AF response","source":"Huawei, HiSilicon, CATT","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.6.7: Clarify the SMF's waiting behaviour with respect to early\/late notification. Reword the description of AF resposne using standard launguage. Clarify the SMF's behavior after receiving a positvie or negative AF response. Describe the SMF's activating behaviour is not clear. Remove inconsistency in terminology.","secretary_remarks":"Revised in parallel session to S2-1908354.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24140,"status":"revised","reservation_date":"2019-06-18 08:04:40","uploaded":"2019-06-18 11:39:54","revisionof":"","revisedto":"S2-1908354","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1644.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907633.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907634","title":"Clarification and correction to AF response","source":"Huawei, HiSilicon, CATT","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make corrections and clarificaitons with resepct to clause 5.6.7.2, TS 23.501.","secretary_remarks":"Revised in parallel session to S2-1908355.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24160,"status":"revised","reservation_date":"2019-06-18 08:04:42","uploaded":"2019-06-18 11:39:54","revisionof":"","revisedto":"S2-1908355","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1625.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907634.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907635","title":"Correction on the AF subscribed notification procedures of session & service cotinuity and UP path management scenarios","source":"Huawei, Hisilicon, CATT","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify description of early\/late notification in clause 4.3.5.2-4.3.5.4 and 4.3.5.6-4.3.5.7.","secretary_remarks":"Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24600,"status":"agreed","reservation_date":"2019-06-18 08:04:43","uploaded":"2019-06-18 11:39:54","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1626.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907635.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907689","title":"Discussion on RSN allocation between two SMFs","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses how the different RSNs are allocated in case of two SMFs are used.","secretary_remarks":"Not Handled","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24190,"status":"not treated","reservation_date":"2019-06-18 10:49:48","uploaded":"2019-06-18 11:07:20","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_134_Sapporo\/Docs\/S2-1907689.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907691","title":"Clarification on RSN allocation between two SMFs (Option 1)","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added a clarification that in case of two SMFs are used, the SMFs have different RSN pool based on operator configuration.","secretary_remarks":"Revised in parallel session to S2-1908356.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24200,"status":"revised","reservation_date":"2019-06-18 10:55:36","uploaded":"2019-06-18 11:06:39","revisionof":"","revisedto":"S2-1908356","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1655.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907691.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1907692","title":"Clarification on RSN allocation between two SMFs (Option 2)","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added a description of UE requested PDU session establishment procedure to avoid reuse of same RSN by different SMFs.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24220,"status":"noted","reservation_date":"2019-06-18 10:58:19","uploaded":"2019-06-18 11:06:39","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1640.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1907692.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908296","title":"Failure handling for redundancy based on dual connectivity","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add that RAN local configuration decides how the failure of establishing RSN marked PDU session with redundant user plane case.","secretary_remarks":"Revision of S2-1907075. Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24390,"status":"agreed","reservation_date":"2019-07-04 09:15:08","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1907075","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1489.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908296.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908297","title":"Failure handling for redundancy based on dual connectivity","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify NG-RAN handles PDU session setup decision in case redudndant user plane can not be established.","secretary_remarks":"Revision of S2-1907076. Revised in parallel session to S2-1908450.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24000,"status":"revised","reservation_date":"2019-07-04 09:15:09","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1907076","revisedto":"S2-1908450","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1499.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908297.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908298","title":"[DRAFT] Reply LS on Solution 1 of 5G_URLLC","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachments: Agreed version of CR#1489, TS23.501","secretary_remarks":"Revision of S2-1907077. Revised in parallel session to S2-1908452.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24030,"status":"revised","reservation_date":"2019-07-04 09:15:10","uploaded":"2019-07-04 09:17:59","revisionof":"S2-1907077","revisedto":"S2-1908452","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_134_Sapporo\/Docs\/S2-1908298.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908351","title":"Clarification 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-1907632, merging S2-1907160. Revised in parallel session to S2-1908451.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24060,"status":"revised","reservation_date":"2019-07-04 09:16:09","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907632","revisedto":"S2-1908451","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1643.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908351.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908352","title":"Clarification on reordering requirement with GTP-U redundancy","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that reordering is not performed for the redundancy function.","secretary_remarks":"Revision of S2-1907078. Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24520,"status":"agreed","reservation_date":"2019-07-04 09:16:10","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907078","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1490.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908352.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908353","title":"Update of AN release procedure for URLLC service","source":"Lenovo, Motorola Mobility","contact":"Tingfang Tang","contact-id":81429,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Moving the description for URLLC in AN release procedure from step 5 to step 6a.","secretary_remarks":"Revision of S2-1907282. Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24550,"status":"agreed","reservation_date":"2019-07-04 09:16:11","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907282","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1530.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908353.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908354","title":"Clarification and correction to AF response","source":"Huawei, HiSilicon, CATT, Samsung, Nokia, Nokia Shanghai Bell","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.6.7: Clarify the SMF's waiting behaviour with respect to early\/late notification. Reword the description of AF resposne using standard launguage. Clarify the SMF's behavior after receiving a positvie or negative AF response. Describe the SMF's activating behaviour is not clear. Remove inconsistency in terminology.","secretary_remarks":"Revision of S2-1907633. Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24570,"status":"agreed","reservation_date":"2019-07-04 09:16:12","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907633","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1644.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908354.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908355","title":"Clarification and correction to AF response","source":"Huawei, HiSilicon, CATT, Samsung, Nokia, Nokia Shanghai Bell","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Make corrections and clarificaitons with resepct to clause 5.6.7.2, TS 23.501.","secretary_remarks":"Revision of S2-1907634. Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24590,"status":"agreed","reservation_date":"2019-07-04 09:16:13","uploaded":"2019-07-04 09:18:00","revisionof":"S2-1907634","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1625.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908355.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908356","title":"Clarification on RSN allocation between two SMFs (Option 1)","source":"LG Electronics","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Added a clarification that in case of two SMFs are used, the SMFs have different RSN pool based on operator configuration.","secretary_remarks":"Revision of S2-1907691. This was withdrawn.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24210,"status":"withdrawn","reservation_date":"2019-07-04 09:16:15","uploaded":null,"revisionof":"S2-1907691","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1655.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908450","title":"Failure handling for redundancy based on dual connectivity","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify NG-RAN handles PDU session setup decision in case redudndant user plane can not be established.","secretary_remarks":"Revision of S2-1908297. Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24420,"status":"agreed","reservation_date":"2019-07-04 09:18:18","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908297","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.1.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1499.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908450.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908451","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-1908351. Agreed in parallel session. This was Block approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24490,"status":"agreed","reservation_date":"2019-07-04 09:18:20","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908351","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1643.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-190608","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908451.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908452","title":"[DRAFT] Reply LS on Solution 1 of 5G_URLLC","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachments: Agreed version of CR#1489, TS23.501","secretary_remarks":"Revision of S2-1908298. For e-mail approval. e-mail approved. Revised to remove 'draft' in S2-1908633.","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24450,"status":"revised","reservation_date":"2019-07-04 09:18:21","uploaded":"2019-07-04 09:27:56","revisionof":"S2-1908298","revisedto":"S2-1908633","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_134_Sapporo\/Docs\/S2-1908452.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1908633","title":"Reply LS on Solution 1 of 5G_URLLC","source":"SA WG2","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. Attachments: S2-1908296 (CR#1489, TS23.501)","secretary_remarks":"Revision of S2-1908452. Approved","agenda_item_sort_order":49,"ainumber":"6.20.2","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC) - Maintenance","tdoc_agenda_sort_order":24460,"status":"approved","reservation_date":"2019-07-10 09:00:46","uploaded":"2019-07-10 09:17:56","revisionof":"S2-1908452","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"5G_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1906879","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_134_Sapporo\/Docs\/S2-1908633.zip","group":"S2","meeting":"S2-134","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]