[{"name":"S2-1902997","title":"Draft LS on QoS Monitoring","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS sent to RAN WG2\/RAN WG3 to update the SA WG2 progress on QoS Monitoring.","secretary_remarks":"Revised in parallel session to S2-1904685.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24700,"status":"revised","reservation_date":"2019-03-28 11:33:20","uploaded":"2019-04-02 14:05:38","revisionof":"","revisedto":"S2-1904685","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2, RAN3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902997.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902998","title":"Conclusion proposal for Key Issue #4","source":"Huawei, HiSilicon, China Telecom, Motorola Mobility, Lenovo, China Mobile, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper proposes conclusion for KI#4. Proposal #1: Using the sampled actual service packets as the monitoring packet in the QoS Monitoring solution. Proposal #2: The UL\/DL packet delay between UE and PSA UPF for per UE per QoS Flow are divided to the UL\/DL packet delay between UE and RAN and the UL\/DL packet delay between RAN and PSA UPF. The measurement mechanism for the UL\/DL packet delay of Uu interface depends on RAN decision, and RAN provides the UL\/DL packet delay result of Uu interface to the UPF via N3 interface. The PSA UPF calculates the UL\/DL packet delay between UE and UPF as the sum of i) the packet delay measurement result of Uu interface and ii) the packet delay of N3 (and possibly N9) interface. Proposal #3: The PCC framework is enhanced to activate or deactivate the QoS Monitoring for the QoS Flow. Changes in Rev1: Reference to solution 19 agreed at last meeting is added in the conclusion part. Conclude that the UE is activated to initiate packet delay measurement based on the instruction received from the RAN. Changes in Rev2: Revert the addition of the description on UE side in Rev1, and clarify that RAN node initiates the packet delay measurement of UL\/DL packet delay on Uu interface, based on the QoS Monitoring policy received from the SMF. Solution #X (Accumulated packet delay estimation for QoS monitoring and division of PDB) is also concluded for normative work. Changes in Rev3: Clarify that the QoS Monitoring can be performed on different granularities, i.e. per QoS Flow per UE level, or per node level, subject to the operators' configuration, and\/or 3rd party application request, and\/or PCF policy control. Accordingly, two alternative solutions are concluded. Changes in Rev4: Wording updates and cleanup. Changes in Rev5: Further clarify that SA WG2 conclude not to proceed to normative work until receiving feedback from RAN WGs.","secretary_remarks":"Revision of S2-1902858 from S2#131. Revised off-line to S2-1904670.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24640,"status":"revised","reservation_date":"2019-03-28 11:33:21","uploaded":"2019-04-02 14:05:38","revisionof":"S2-1902858","revisedto":"S2-1904670","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":5.0,"crrevision":5.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902998.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1902999","title":"QoS Monitoring to assist URLLC Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add descriptino of QoS Monitoring to assist URLLC service.","secretary_remarks":"Not Handled","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24680,"status":"not treated","reservation_date":"2019-03-28 11:33:31","uploaded":"2019-04-02 14:05:38","revisionof":"","revisedto":"S2-1905702","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1126.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902999.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903000","title":"QoS Monitoring to assist URLLC Service","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of QoS Monitoring to assist URLLC service.","secretary_remarks":"Not Handled","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24690,"status":"not treated","reservation_date":"2019-03-28 11:33:46","uploaded":"2019-04-02 14:05:38","revisionof":"","revisedto":"S2-1905703","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":227.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903000.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903095","title":"UP connection Deactivation for URLLC PDU Session","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update CN-initiated selective deactivation of UP connection of an existing PDU Session procedure to release the dual UPFs or dual tunnels.","secretary_remarks":"Revised in parallel session to S2-1904652.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24730,"status":"revised","reservation_date":"2019-03-29 09:43:19","uploaded":"2019-04-02 14:51:00","revisionof":"","revisedto":"S2-1904652","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1138.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903095.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903196","title":"Evaluation and Conclusion for Key Issue #7: Automotic GBR Service recovery after HO","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Overall evaluation of solutions for Key issue #7. - Conclusion proposal for Key issue #7.","secretary_remarks":"Revision of S2-1901711 from S2#131. Not Handled","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24580,"status":"not treated","reservation_date":"2019-03-31 16:12:31","uploaded":"2019-04-02 11:45:46","revisionof":"S2-1901711","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":21.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903196.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903199","title":"CN PDB is configured per UL and DL direction","source":"OPPO, China Telecom, China Unicom","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the PDB for a delay critical GBR 5QI is configured to RAN per Downlink and Uplink.","secretary_remarks":"Revised in parallel session to S2-1904689.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25150,"status":"revised","reservation_date":"2019-03-31 16:41:30","uploaded":"2019-04-02 11:50:23","revisionof":"","revisedto":"S2-1904689","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1069.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903199.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903200","title":"Clarification to support associating URLLC traffic to redundant PDU sessions -23.501","source":"OPPO, Ericsson","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: in 23.501, describe in order to setup two redundant PDU sessions with different combination of DNN\/S-NSSAI, the two redundant PDU sessions are corresponding to different URSP Traffic descriptors in normative text; with the possible parameters given in a NOTE in 23.503, describe the use of different Traffic Descriptors of URSP rules, so that the setup of two redundant PDU sessions will be performed using the RSD(s) of different URSP rules.","secretary_remarks":"Revised in parallel session to S2-1904656.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24850,"status":"revised","reservation_date":"2019-03-31 16:45:00","uploaded":"2019-04-02 11:50:23","revisionof":"","revisedto":"S2-1904656","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1070.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903200.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903201","title":"Clarification to support associating URLLC traffic to redundant PDU sessions -23.503","source":"OPPO, Ericsson","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: in 23.501, describe in order to setup two redundant PDU sessions with different combination of DNN\/S-NSSAI, the two redundant PDU sessions are corresponding to different URSP Traffic descriptors in normative text; with some examples given in a NOTE in 23.503, describe the use of different Traffic Descriptors of URSP rules, so that the setup of two redundant PDU sessions will be performed using the RSD(s) of different URSP rules.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24890,"status":"noted","reservation_date":"2019-03-31 16:47:15","uploaded":"2019-04-02 11:50:23","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":234.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903201.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903270","title":"Correction to the user plane redundancy handling","source":"NEC","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes an alternative behaviour to the PDU session rejection due to user redundancy not supported or not allowed by the target SMF. The proposed alternative behaviour is the UE falling to or establishing a PDU session without user redundancy..","secretary_remarks":"Revised in parallel session to S2-1904653.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24770,"status":"revised","reservation_date":"2019-04-01 11:33:59","uploaded":"2019-04-01 18:58:50","revisionof":"","revisedto":"S2-1904653","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1171.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903270.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903433","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. HR roaming and UP deactivation are not supported for PDU session serving URLLC. 2, editorial modifications.","secretary_remarks":"Revised in parallel session to S2-1904651.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24560,"status":"revised","reservation_date":"2019-04-02 01:05:06","uploaded":"2019-04-02 14:04:56","revisionof":"","revisedto":"S2-1904651","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1141.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903433.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903434","title":"Update procedure related to redundant transmission","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Remove texts related with URLLC in UE Triggered SR procedure. 2. Clarify that redundant N3 tunnel can be established during PDU Session Establishment procedure without indicating UPF\/RAN to perform packet duplication and elimination. 3. Update PDU Session Modification procedure to support removal of redundancy tunnel. 4. Clarify that SMF shall release URLLC QoS Flows by triggering PDU Session Modification procedure after Xn\/N2 HO procedure if only one AN Tunnel Info is provided by Target NG-RAN. 5. Editorial modifications.","secretary_remarks":"Revised in parallel session to S2-1904654.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24790,"status":"revised","reservation_date":"2019-04-02 01:05:07","uploaded":"2019-04-02 14:04:56","revisionof":"","revisedto":"S2-1904654","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1203.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903434.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903435","title":"Update description for E2E PDB division","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of description for E2E PDB division according to above reason for change\u00a0: Change 'dynamic CN component of the PDB'\u00a0\u00a0to 'CN PDB'; Clarify the usage of CN PDB is to obtain more accurate PDB for RAN\u00a0; Clarify CN PDB is delivered per QoS Flow\u00a0; Remove PDU session establishment and Service request from the procedures that need to consider CN PDB update.","secretary_remarks":"Revised in parallel session to S2-1904690.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25170,"status":"revised","reservation_date":"2019-04-02 01:05:08","uploaded":"2019-04-02 14:04:56","revisionof":"","revisedto":"S2-1904690","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1142.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903435.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903437","title":"Explicit indication of AF response for runtime coordination with AF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The paper proposes to add a separate indication in the AF request as part of AF subscription, for indicating AF response to be expected. When the indicaiton is included, the SMF may accordingly determine to perform coordination with the AF and to wait for AF response.","secretary_remarks":"Revised in parallel session to S2-1904686.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25060,"status":"revised","reservation_date":"2019-04-02 01:05:10","uploaded":"2019-04-02 14:04:56","revisionof":"","revisedto":"S2-1904686","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1144.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903437.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903438","title":"Explicit indication of AF response for runtime coordination with AF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 6.3.1 to include indication of AF response to be expected as part of AF subscription information.","secretary_remarks":"Revised in parallel session to S2-1904687.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25090,"status":"revised","reservation_date":"2019-04-02 01:05:12","uploaded":"2019-04-02 14:04:56","revisionof":"","revisedto":"S2-1904687","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":243.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903438.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903472","title":"Discussion on how to trigger redundant PDU Session establishment for the same application","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses how to trigger redundant PDU Session establishment for the same application.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24900,"status":"noted","reservation_date":"2019-04-02 01:45:10","uploaded":"2019-04-02 13:37:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903472.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903473","title":"Redundant PDU Session establishment for the same application","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Refer to TS 23.503 on trigger to establish redundant PDU Sessions for one application. Note that operators could use different traffic descriptors to describe this service if a URLLC service is identified by IP descriptors, Domain descriptors, non-IP descriptors or DNNs. In that case, UE will treat the URLLC service as different applications.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24910,"status":"noted","reservation_date":"2019-04-02 01:45:10","uploaded":"2019-04-02 13:37:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1153.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903473.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903474","title":"Redundant PDU Session establishment for the same application","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add an example of Connection Capabilities as 'redundant PDU Sessions'. Clarify a URSP rule with an application demanding of redundant PDU Sessions has at least two Route Selection Descriptors with different DNNs or S-NSSAIs. If the URSP rule is determined to be applicable for such an application requesting redundant PDU sessions (i.e. a value of Connection Capability identical to 'redundant PDU sessions'), the UE shall select two Route Selection Descriptors within this URSP rule to associate the application to two PDU Sessions.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24920,"status":"noted","reservation_date":"2019-04-02 01:45:12","uploaded":"2019-04-02 13:37:29","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":247.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903474.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903506","title":"Clarification on the CN PDB configured in each NG-RAN node","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification is made that the dynamic CN component of the PDB configured in each NG-RAN node may or may not be per delay critical GBR 5QI.","secretary_remarks":"Revised in parallel session to S2-1904691.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25210,"status":"revised","reservation_date":"2019-04-02 05:19:39","uploaded":"2019-04-02 10:16:24","revisionof":"","revisedto":"S2-1904691","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1163.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903506.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903515","title":"Update of Solution#22 for KI#7","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are made: 1) Resolve the following EN: Editor's note: It is FFS whether and how the UE's NAS layer is informed that GBR radio resource has not been allocated for the GBR QoS Flow non-accepted in the target NG-RAN. No notification to the UE is proposed because the benefit or use of notification to the UE is not clear. 2) Add solution evaluation. 3) Add some texts for clarity.","secretary_remarks":"Not Handled","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24590,"status":"not treated","reservation_date":"2019-04-02 05:41:47","uploaded":"2019-04-02 10:26:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":33.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903515.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903535","title":"Redundant PDU session handling","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the SMF may deactivate the redundant PDU sessions if DC is not supported.","secretary_remarks":"Revised in parallel session to S2-1904657.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24930,"status":"revised","reservation_date":"2019-04-02 06:57:40","uploaded":"2019-04-02 11:35:02","revisionof":"","revisedto":"S2-1904657","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1173.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903535.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903625","title":"Redundant PDU Sessions using Dual Connectivity","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Agreement","abstract":"S2-1902825, S2-1902744 introduce redundant PDU Sessions using Dual Connectivity, but not only puts undue complexity on the UE, in contradiction with the conclusion of the study, it also describes a solution that is not deemed workable. This contribution proposes to keep the trigger on the network side","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24960,"status":"noted","reservation_date":"2019-04-02 08:39:47","uploaded":"2019-04-02 11:16:46","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_132_XiAn\/Docs\/S2-1903625.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903626","title":"Correction to Redundant PDU Sessions using Dual Connectivity","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UE triggers the establishment\/modification of a first PDU Session normally. The SMF determines whether a redundant PDU Session is required and informs the UE accordingly. The UE requests the establishment of a second PDU Session","secretary_remarks":"Not Handled","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24970,"status":"not treated","reservation_date":"2019-04-02 08:39:47","uploaded":"2019-04-02 11:16:46","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1203.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903626.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903627","title":"Correction to Redundant PDU Sessions using Dual Connectivity","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The UE triggers the establishment\/modification of a first PDU Session normally. The SMF determines whether a redundant PDU Session is required and informs the UE accordingly. The UE requests the establishment of a second redundant PDU Session","secretary_remarks":"Not Handled","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24980,"status":"not treated","reservation_date":"2019-04-02 08:39:49","uploaded":"2019-04-02 11:16:46","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1257.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903627.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903657","title":"5G URLLC: The Issue of Failing UE","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"discussion","for":"Agreement","abstract":"5G URLLC: The Issue of Failing UE","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25020,"status":"noted","reservation_date":"2019-04-02 09:35:02","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903657.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903658","title":"5G URLLC: Optimizing Redundancy","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Alternative 1: Introduce the means for application\/UE to indicate to the network (SMF) the UE applies traffic redundancy at PDU Session level (traffic redundancy indication at PDU Session level). The UE can provide the traffic redundancy indication within the PDU Session establishment or PDU Session modification request. Alternative 2: PCF can be configured with the indication that redundant transmission is performed at UE level (traffic redundancy indication) for a given PDU Session (identified by the couple (DNN, S-NSSAI)) or for a set of applications or traffic flow(s) within a PDU Session. Information derived by SMF from PCF policies and\/or the UE indication within the PDU Session Establishment\/Modification request can be provided to the RAN and UPF as 'URLLC assistance information'. Other corrections proposed: Dual GTP-U approach - trigger for two N3 tunnels should be from SMF\/UPF, not from the NG-RAN. RAN should rather respond with two TEIDs based on decision by SMF\/UPF for duplicated GTP-U tunnels. Otherwise, this setup will not be synchronized if it is triggered by both. Transport layer redundancy - for DL, it erroneously states that the RAN sends it to the UPF. DL packet should be sent towards the UE. Changing Redundant functionality -> Redundancy functionality in the UPF\/RAN (to avoid negative connotation by the use of term redundant functionality).","secretary_remarks":"Revised in parallel session to S2-1904659.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25030,"status":"revised","reservation_date":"2019-04-02 09:35:02","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"S2-1904659","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1217.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903658.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903659","title":"5G URLLC QoS Monitoring solution","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"discussion","for":"Agreement","abstract":"5G URLLC: The Issue of Failing UE","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24600,"status":"noted","reservation_date":"2019-04-02 09:35:03","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903659.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903685","title":"Update PDU Session Esstablsihment procedure regarding solution 4 in 23.725","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update PDU Session establishment procedure to support redundant transmission between UPF and RAN by supporting two I-UPFs.","secretary_remarks":"Revised in parallel session to S2-1904655.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24820,"status":"revised","reservation_date":"2019-04-02 09:44:40","uploaded":"2019-04-02 09:55:25","revisionof":"","revisedto":"S2-1904655","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1265.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903685.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903735","title":"Introduction of QoS Monitoring to assist URLLC Service","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduction of QoS Monitoring to assist URLLC service.","secretary_remarks":"Revision of S2-1901937 from S2#131. Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24670,"status":"noted","reservation_date":"2019-04-02 10:56:23","uploaded":"2019-04-02 12:53:14","revisionof":"S2-1901937","revisedto":"S2-1905525","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":990.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903735.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903740","title":"Update procedures to support PDB division","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update related procedures to support the provision of the CN PDB to the NG-RAN node.","secretary_remarks":"Postponed in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25200,"status":"postponed","reservation_date":"2019-04-02 11:06:59","uploaded":"2019-04-02 14:04:56","revisionof":"","revisedto":"S2-1905521","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1277.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903740.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903798","title":"PCF handling for redundant PDU sessions","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The SMF uses the S-NSSAI and DNN to select the same PCF for the two redundant PDU session. The PCF uses the S-NSSAI and DNN to know these two PDU sessions is to be handled redundantly and generates the same PCC rules for these two PDU Session, except the different UE IP addresses in the PCC rules for IP PDU Session. When PCF decides to update the PCC rules it sends the latest PCC rules to both SMFs simutanously. The two redundant PDU Sessions have same PDU Session AMBR. UE-AMBR is enforced as defined in clause 5.7.2.6. The SMF establishes QoS flows based on the PCC rules. If the SMF determines this PDU Session should go via Secondary NG-RAN, the SMF may not establishes the QoS Flows which are not subject to redundantly handling.","secretary_remarks":"Revised in parallel session to S2-1904658.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24990,"status":"revised","reservation_date":"2019-04-02 11:32:57","uploaded":"2019-04-02 13:19:27","revisionof":"","revisedto":"S2-1904658","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1254.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903798.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903799","title":"Clarification on Nsmf_EventExposure_AppRelocationInfo","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When acknowledgment is expected the SMF also provides Notification Correlation Information to the consumer NF in the event notification.","secretary_remarks":"Revised in parallel session to S2-1904688.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25120,"status":"revised","reservation_date":"2019-04-02 11:32:58","uploaded":"2019-04-02 13:19:27","revisionof":"","revisedto":"S2-1904688","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1294.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903799.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903861","title":"Simplified version of solution #24 QoS monitoring for URLLC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This solution provides means for QoS monitoring for URLLC on the GTP based interaces, i.e. on N3 interface between UPF and NG-RAN as well as on the N9 interface between the UPF (PSA) and I-UPF. This solution is based on the specification of the measurements specified for GTP based F1 interface in TS 28.522 [1]. This measurement provides the average (arithmetic mean) GTP packet delay on the N3 interface. The measurement is optionally split into subcounters per QoS level (5QI). This measurement is obtained as: the time when receiving a GTP packet delivery status message from the gNB at the egress GTP termination, minus time when sending\u00a0the same packet to gNB at the\u00a0GTP ingress termination, minus feedback delay time in gNB [note: measurements defined in 28.522 [1]already specify gNB-CU internal delays, hence the internal delay at gNB-CU is available], obtained result is divided by two. Each measurement is an integer representing the mean delay in microseconds. The number of measurements is equal to one. If the optional QoS level measurement is perfomed, the number of measurements is equal to the number of QoS level parameters. Measurement taken at UPF. Measurememnt are provided to SMF and to OAM. QoS monitoring within NG-RAN and between NG-RAN and UE (Uu) will be specified by RAN WGs.","secretary_remarks":"Revised in parallel session to S2-1904683.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24610,"status":"revised","reservation_date":"2019-04-02 13:55:04","uploaded":"2019-04-02 14:10:35","revisionof":"","revisedto":"S2-1904683","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":34.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903861.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1903866","title":"Clarify the definition of the CN component PDB","source":"China Telecom","contact":"Zhao Song","contact-id":71667,"tdoctype":"CR","for":"Agreement","abstract":"Summary of change: Use the term delay budget to replace the term delay in the description in clause 5.7.3.4 in TS 23.501.","secretary_remarks":"Revised in parallel session to S2-1904692.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25230,"status":"revised","reservation_date":"2019-04-02 14:37:45","uploaded":"2019-04-02 14:44:39","revisionof":"","revisedto":"S2-1904692","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1272.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903866.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904651","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-1903433. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24570,"status":"agreed","reservation_date":"2019-04-15 10:43:11","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903433","revisedto":"S2-1905519","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1141.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904651.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904652","title":"UP connection Deactivation for URLLC PDU Session","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the Service Request and AN Releasae procedure to activate\/deactivate the User Plane of the PDU Sessions for URLLC. The PDU Session for URLLC is either with redudant I-UPFs or with redudant N3\/N9 tunnels.","secretary_remarks":"Revision of S2-1903095. Revised in parallel session to S2-1904762.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24740,"status":"revised","reservation_date":"2019-04-15 10:43:12","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903095","revisedto":"S2-1904762","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1138.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904652.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904653","title":"Correction to the user plane redundancy handling","source":"NEC","contact":"Iskren Ianev","contact-id":59515,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes an alternative behaviour to the PDU session rejection due to user redundancy not supported or not allowed by the target SMF. The proposed alternative behaviour is the UE falling to or establishing a PDU session without user redundancy.","secretary_remarks":"Revision of S2-1903270. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24780,"status":"agreed","reservation_date":"2019-04-15 10:43:13","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903270","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1171.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904653.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904654","title":"Update procedure related to redundant transmission","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Remove texts related with URLLC in UE Triggered SR procedure. 2. Clarify that redundant N3 tunnel can be established during PDU Session Establishment procedure without indicating UPF\/RAN to perform packet duplication and elimination. 31. Update PDU Session Modification procedure to support removal of redundancy tunnel. 42. Clarify that SMF shall release URLLC QoS Flows by triggering PDU Session Modification procedure after Xn\/N2 HO procedure if only one AN Tunnel Info is provided by Target NG-RAN. 53. Editorial modifications.","secretary_remarks":"Revision of S2-1903434. Revised in parallel session to S2-1904763.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24800,"status":"revised","reservation_date":"2019-04-15 10:43:14","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903434","revisedto":"S2-1904763","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1203.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904654.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904655","title":"Update PDU Session Esstablsihment procedure regarding solution 4 in 23.725","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update PDU Session establishment procedure to support redundant transmission between UPF and RAN by supporting two I-UPFs.","secretary_remarks":"Revision of S2-1903685. Revised in parallel session to S2-1904694.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24830,"status":"revised","reservation_date":"2019-04-15 10:43:15","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903685","revisedto":"S2-1904694","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1265.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904655.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904656","title":"Clarification to support associating URLLC traffic to redundant PDU sessions -23.501","source":"OPPO, Ericsson","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: in 23.501, describe in order to setup two redundant PDU sessions with different combination of DNN\/S-NSSAI, the two redundant PDU sessions are corresponding to different URSP Traffic descriptors in normative text; with the possible parameters given in a NOTE","secretary_remarks":"Revision of S2-1903200. Revised in parallel session to S2-1904764.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24860,"status":"revised","reservation_date":"2019-04-15 10:43:16","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903200","revisedto":"S2-1904764","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1070.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904656.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904657","title":"Redundant PDU session handling","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the SMF may deactivate the redundant PDU sessions if DC is not supported during handover procedure.","secretary_remarks":"Revision of S2-1903535. Revised in parallel session to S2-1904765.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24940,"status":"revised","reservation_date":"2019-04-15 10:43:17","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903535","revisedto":"S2-1904765","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1173.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904657.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904658","title":"PCF handling for redundant PDU sessions","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add note: NOTE\u00a03: The SMF can select same PCF via NRF for the two redundant PDU sessions if needed.","secretary_remarks":"Revision of S2-1903798. Revised in parallel session to S2-1904766.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25000,"status":"revised","reservation_date":"2019-04-15 10:43:18","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903798","revisedto":"S2-1904766","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1254.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904658.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904659","title":"5G URLLC: Optimizing Redundancy","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Alternative 1: Introduce the means for application\/UE to indicate to the network (SMF) the UE applies traffic redundancy at PDU Session level (traffic redundancy indication at PDU Session level). The UE can provide the traffic redundancy indication within the PDU Session establishment or PDU Session modification request. Alternative 2: PCF can be configured with the indication that redundant transmission is performed at UE level (traffic redundancy indication) for a given PDU Session (identified by the couple (DNN, S-NSSAI)) or for a set of applications or traffic flow(s) within a PDU Session. Information derived by SMF from PCF policies and\/or the UE indication within the PDU Session Establishment\/Modification request can be provided to the RAN and UPF as 'URLLC assistance information'. Other corrections proposed: Dual GTP-U approach - trigger for two N3 tunnels should be from SMF\/UPF, not from the NG-RAN. RAN should rather respond with two TEIDs based on decision by SMF\/UPF for duplicated GTP-U tunnels. Otherwise, this setup will not be synchronized if it is triggered by both. Transport layer redundancy - for DL, it erroneously states that the RAN sends it to the UPF. DL packet should be sent towards the UE. Changing Redundant functionality -> Redundancy functionality in the UPF\/RAN (to avoid negative connotation by the use of term redundant functionality).","secretary_remarks":"Revision of S2-1903658. Revised in parallel session to S2-1904696.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25040,"status":"revised","reservation_date":"2019-04-15 10:43:18","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903658","revisedto":"S2-1904696","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1217.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904659.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904670","title":"Conclusion proposal for Key Issue #4","source":"Huawei, HiSilicon, China Telecom, Motorola Mobility, Lenovo, China Mobile, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper proposes conclusion for KI#4. Proposal #1: Using the sampled actual service packets as the monitoring packet in the QoS Monitoring solution. Proposal #2: The UL\/DL packet delay between UE and PSA UPF for per UE per QoS Flow are divided to the UL\/DL packet delay between UE and RAN and the UL\/DL packet delay between RAN and PSA UPF. The measurement mechanism for the UL\/DL packet delay of Uu interface depends on RAN decision, and RAN provides the UL\/DL packet delay result of Uu interface to the UPF via N3 interface. The PSA UPF calculates the UL\/DL packet delay between UE and UPF as the sum of i) the packet delay measurement result of Uu interface and ii) the packet delay of N3 (and possibly N9) interface. Proposal #3: The PCC framework is enhanced to activate or deactivate the QoS Monitoring for the QoS Flow. Changes in Rev1: Reference to solution 19 agreed at last meeting is added in the conclusion part. Conclude that the UE is activated to initiate packet delay measurement based on the instruction received from the RAN. Changes in Rev2: Revert the addition of the description on UE side in Rev1, and clarify that RAN node initiates the packet delay measurement of UL\/DL packet delay on Uu interface, based on the QoS Monitoring policy received from the SMF. Solution #X (Accumulated packet delay estimation for QoS monitoring and division of PDB) is also concluded for normative work. Changes in Rev3: Clarify that the QoS Monitoring can be performed on different granularities, i.e. per QoS Flow per UE level, or per node level, subject to the operators' configuration, and\/or 3rd party application request, and\/or PCF policy control. Accordingly, two alternative solutions are concluded. Changes in Rev4: Wording updates and cleanup. Changes in Rev5: Further clarify that SA WG2 conclude not to proceed to normative work until receiving feedback from RAN WGs. Changes in Rev6: SMF can determine QoS flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for a given QoS flow.","secretary_remarks":"Revision of S2-1902998. Revised in parallel session to S2-1904684.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24650,"status":"revised","reservation_date":"2019-04-15 10:43:28","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1902998","revisedto":"S2-1904684","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":5.0,"crrevision":6.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904670.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904683","title":"Simplified version of solution #24 QoS monitoring for URLLC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This solution provides means for QoS monitoring for URLLC on the GTP based interaces, i.e. on N3 interface between UPF and NG-RAN as well as on the N9 interface between the UPF (PSA) and I-UPF. This solution is based on the specification of the measurements specified for GTP based F1 interface in TS 28.552 [1]. This measurement provides the average (arithmetic mean) GTP packet delay on the N3 interface. The measurement is optionally split into subcounters per QoS level (5QI). This measurement is obtained as: the time when receiving a GTP packet delivery status message from the gNB at the egress GTP termination, minus time when sending\u00a0the same packet to gNB at the\u00a0GTP ingress termination, minus feedback delay time in gNB [note: measurements defined in 28.552 [1]already specify gNB-CU internal delays, hence the internal delay at gNB-CU is available], obtained result is divided by two. Each measurement is an integer representing the mean delay in microseconds. The number of measurements is equal to one. If the optional QoS level measurement is perfomed, the number of measurements is equal to the number of QoS level parameters. Measurement taken at UPF. Measurememnt are provided to SMF and to OAM. QoS monitoring within NG-RAN and between NG-RAN and UE (Uu) will be specified by RAN WGs.","secretary_remarks":"Revision of S2-1903861. Revised off-line to S2-1904740.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24620,"status":"revised","reservation_date":"2019-04-15 10:43:43","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903861","revisedto":"S2-1904740","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":34.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904683.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904684","title":"Conclusion proposal for Key Issue #4","source":"Huawei, HiSilicon, China Telecom, Motorola Mobility, Lenovo, China Mobile, Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This paper proposes conclusion for KI#4. Proposal #1: Using the sampled actual service packets as the monitoring packet in the QoS Monitoring solution. Proposal #2: The UL\/DL packet delay between UE and PSA UPF for per UE per QoS Flow are divided to the UL\/DL packet delay between UE and RAN and the UL\/DL packet delay between RAN and PSA UPF. The measurement mechanism for the UL\/DL packet delay of Uu interface depends on RAN decision, and RAN provides the UL\/DL packet delay result of Uu interface to the UPF via N3 interface. The PSA UPF calculates the UL\/DL packet delay between UE and UPF as the sum of i) the packet delay measurement result of Uu interface and ii) the packet delay of N3 (and possibly N9) interface. Proposal #3: The PCC framework is enhanced to activate or deactivate the QoS Monitoring for the QoS Flow. Changes in Rev1: Reference to solution 19 agreed at last meeting is added in the conclusion part. Conclude that the UE is activated to initiate packet delay measurement based on the instruction received from the RAN. Changes in Rev2: Revert the addition of the description on UE side in Rev1, and clarify that RAN node initiates the packet delay measurement of UL\/DL packet delay on Uu interface, based on the QoS Monitoring policy received from the SMF. Solution #X (Accumulated packet delay estimation for QoS monitoring and division of PDB) is also concluded for normative work. Changes in Rev3: Clarify that the QoS Monitoring can be performed on different granularities, i.e. per QoS Flow per UE level, or per node level, subject to the operators' configuration, and\/or 3rd party application request, and\/or PCF policy control. Accordingly, two alternative solutions are concluded. Changes in Rev4: Wording updates and cleanup. Changes in Rev5: Further clarify that SA WG2 conclude not to proceed to normative work until receiving feedback from RAN WGs. Changes in Rev6: SMF can determine QoS flow mapping to the appropriate {Network instance, DSCP} considering {5QI, QoS characteristics, ARP} for a given QoS flow. Changes in Rev7: Clarify that the per node level measurement can use GTP packet delivery status message as defined in the 3GPP TS 28.552 [x].","secretary_remarks":"Revision of S2-1904670. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24660,"status":"agreed","reservation_date":"2019-04-15 10:43:44","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1904670","revisedto":"S2-1905358","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"FS_5G_URLLC"}],"crnumber":5.0,"crrevision":7.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904684.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904685","title":"Draft LS on QoS Monitoring","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"LS out","for":"Approval","abstract":"Draft LS sent to RAN WG2\/RAN WG3 to update the SA WG2 progress on QoS Monitoring.","secretary_remarks":"Revision of S2-1902997. Revised in parallel session to S2-1904761.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24710,"status":"revised","reservation_date":"2019-04-15 10:43:45","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1902997","revisedto":"S2-1904761","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN2, RAN3","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904685.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904686","title":"Explicit indication of AF response for runtime coordination with AF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The paper proposes to add a separate indication in the AF request as part of AF subscription, for indicating AF response to be expected. When the indicaiton is included, the SMF may accordingly determine to perform coordination with the AF and to wait for AF response.","secretary_remarks":"Revision of S2-1903437. Revised in parallel session to S2-1904767.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25070,"status":"revised","reservation_date":"2019-04-15 10:43:45","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903437","revisedto":"S2-1904767","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1144.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904686.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904687","title":"Explicit indication of AF response for runtime coordination with AF","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 6.3.1 to include indication of AF response to be expected as part of AF subscription information.","secretary_remarks":"Revision of S2-1903438. Revised in parallel session to S2-1904768.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25100,"status":"revised","reservation_date":"2019-04-15 10:43:46","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903438","revisedto":"S2-1904768","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":243.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904687.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904688","title":"Clarification on Nsmf_EventExposure_AppRelocationInfo","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When acknowledgment is expected the SMF also provides Notification Correlation Information to the consumer NF in the event notification.","secretary_remarks":"Revision of S2-1903799. Revised in parallel session to S2-1904693.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25130,"status":"revised","reservation_date":"2019-04-15 10:43:47","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903799","revisedto":"S2-1904693","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1294.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904688.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904689","title":"CN PDB is configured per UL and DL direction","source":"OPPO, China Telecom, China Unicom","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Clarify that the PDB for a delay critical GBR 5QI is configured to RAN per Downlink and Uplink.","secretary_remarks":"Revision of S2-1903199. Withdrawn","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25160,"status":"withdrawn","reservation_date":"2019-04-15 10:43:48","uploaded":null,"revisionof":"S2-1903199","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1069.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904690","title":"Update description for E2E PDB division","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of description for E2E PDB division according to above reason for change: Change 'dynamic CN component of the PDB'\u00a0\u00a0to 'CN PDB', added abbreviation. Clarify the usage of CN PDB is to obtain more accurate PDB for RAN\u00a0; Clarify CN PDB is delivered per QoS Flow\u00a0; Remove PDU session establishment and Service request from the procedures that need to consider CN PDB update.","secretary_remarks":"Revision of S2-1903435. Revised in parallel session to S2-1904695.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25180,"status":"revised","reservation_date":"2019-04-15 10:43:49","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903435","revisedto":"S2-1904695","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1142.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904690.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904691","title":"Clarification on the CN PDB configured in each NG-RAN node","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification is made that 'per delay critical GBR 5QI' configuration in each NG-RAN node is optional.","secretary_remarks":"Revision of S2-1903506. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25220,"status":"agreed","reservation_date":"2019-04-15 10:43:50","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903506","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1163.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904691.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904692","title":"Clarify the definition of the CN component PDB","source":"China Telecom","contact":"Zhao Song","contact-id":71667,"tdoctype":"CR","for":"Agreement","abstract":"Summary of change: Clarify that the delay between the UPF terminating N6 and the 5G-AN shall not exceed the given PDB in clause 5.7.3.4 in TS 23.501.","secretary_remarks":"Revision of S2-1903866. Noted in parallel session","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25240,"status":"noted","reservation_date":"2019-04-15 10:43:50","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903866","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1272.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904692.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904693","title":"Clarification on Nsmf_EventExposure_AppRelocationInfo service operation","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When acknowledgment is expected the SMF also provides Notification Correlation Information to the consumer NF in the event notification.","secretary_remarks":"Revision of S2-1904688. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25140,"status":"agreed","reservation_date":"2019-04-15 10:43:51","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1904688","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1294.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904693.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904694","title":"Update PDU Session Establishment procedure regarding solution 4 in 23.725","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update PDU Session establishment procedure to support redundant transmission between UPF and RAN by supporting two I-UPFs.","secretary_remarks":"Revision of S2-1904655. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24840,"status":"agreed","reservation_date":"2019-04-15 10:43:53","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1904655","revisedto":"S2-1905627","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1265.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904694.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904695","title":"Update description for E2E PDB division","source":"Huawei, Hisilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of description for E2E PDB division according to above reason for change: Change 'dynamic CN component of the PDB'\u00a0\u00a0to 'CN PDB', added abbreviation. Clarify the usage of CN PDB is to obtain more accurate PDB for RAN\u00a0; Clarify CN PDB is delivered per QoS Flow\u00a0; Remove PDU session establishment and Service request from the procedures that need to consider CN PDB update.","secretary_remarks":"Revision of S2-1904690. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25190,"status":"agreed","reservation_date":"2019-04-15 10:43:54","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1904690","revisedto":"S2-1905570","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1142.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904695.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904696","title":"5G URLLC: Optimizing Redundancy","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Alternative 1: Introduce the means for application\/UE to indicate to the network (SMF) the UE applies traffic redundancy at PDU Session level (traffic redundancy indication at PDU Session level). The UE can provide the traffic redundancy indication within the PDU Session establishment or PDU Session modification request. Alternative 2: PCF can be configured with the indication that redundant transmission is performed at UE level (traffic redundancy indication) for a given PDU Session (identified by the couple (DNN, S-NSSAI)) or for a set of applications or traffic flow(s) within a PDU Session. Information derived by SMF from PCF policies and\/or the UE indication within the PDU Session Establishment\/Modification request can be provided to the RAN and UPF as 'URLLC assistance information'. Other corrections proposed: Dual GTP-U approach - trigger for two N3 tunnels should be from SMF\/UPF, not from the NG-RAN. RAN should rather respond with two TEIDs based on decision by SMF\/UPF for duplicated GTP-U tunnels. Otherwise, this setup will not be synchronized if it is triggered by both. Transport layer redundancy - for DL, it erroneously states that the RAN sends it to the UPF. DL packet should be sent towards the UE. Changing Redundant functionality -> Redundancy functionality in the UPF\/RAN (to avoid negative connotation by the use of term redundant functionality).","secretary_remarks":"Revision of S2-1904659. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25050,"status":"agreed","reservation_date":"2019-04-15 10:43:55","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1904659","revisedto":"S2-1905517","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1217.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904696.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904740","title":"Simplified version of solution #24 QoS monitoring for URLLC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This solution provides means for QoS monitoring for URLLC on the GTP based interaces, i.e. on N3 interface between UPF and NG-RAN as well as on the N9 interface between the UPF (PSA) and I-UPF. This solution is based on the specification of the measurements specified for GTP based F1 interface in TS 28.552 [1]. This measurement provides the average (arithmetic mean) GTP packet delay on the N3 interface. The measurement is optionally split into subcounters per QoS level (5QI). This measurement is obtained as: the time when receiving a GTP packet delivery status message from the gNB at the egress GTP termination, minus time when sending\u00a0the same packet to gNB at the\u00a0GTP ingress termination, minus feedback delay time in gNB [note: measurements defined in 28.552 [1]already specify gNB-CU internal delays, hence the internal delay at gNB-CU is available], obtained result is divided by two. Each measurement is an integer representing the mean delay in microseconds. The number of measurements is equal to one. If the optional QoS level measurement is perfomed, the number of measurements is equal to the number of QoS level parameters. Measurement taken at UPF. Measurememnt are provided to SMF and to OAM. QoS monitoring within NG-RAN and between NG-RAN and UE (Uu) will be specified by RAN WGs.","secretary_remarks":"Revision of S2-1904683. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24630,"status":"agreed","reservation_date":"2019-04-15 10:44:36","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904683","revisedto":"S2-1905356","release":"Rel-16","crspec":23.725,"crspecversion":"16.1.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":34.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904740.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904761","title":"LS on QoS Monitoring","source":"SA WG2","contact":"Susan Shi","contact-id":37231,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, RAN WG3. CC: SA WG5. Attachments: S2-1904684","secretary_remarks":"Revision of S2-1904685. Approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24720,"status":"approved","reservation_date":"2019-04-15 10:44:37","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904685","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, RAN WG3","Cc":"SA WG5","lsoriginalls":"","lsreply":"R3-192591, R3-193248, R3-193282","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904761.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904762","title":"UP connection Deactivation for URLLC PDU Session","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the Service Request and AN Releasae procedure to activate\/deactivate the User Plane of the PDU Sessions for URLLC. The PDU Session for URLLC is either with redudant I-UPFs or with redudant N3\/N9 tunnels.","secretary_remarks":"Revision of S2-1904652. Revised to S2-1904822.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24750,"status":"revised","reservation_date":"2019-04-15 10:44:37","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904652","revisedto":"S2-1904822","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1138.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904762.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904763","title":"Update procedures related to redundant transmission","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Update PDU Session Modification procedure to support removal of redundancy tunnel. 2. Clarify that SMF shall release URLLC QoS Flows by triggering PDU Session Modification procedure after Xn\/N2 HO procedure if only one AN Tunnel Info is provided by Target NG-RAN. 3. Editorial modifications.","secretary_remarks":"Revision of S2-1904654. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24810,"status":"agreed","reservation_date":"2019-04-15 10:44:38","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904654","revisedto":"S2-1905112","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1203.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904763.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904764","title":"Clarification to support associating URLLC traffic to redundant PDU sessions -23.501","source":"OPPO, Ericsson","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: in 23.501, describe in order to setup two redundant PDU sessions with different combination of DNN\/S-NSSAI, the two redundant PDU sessions are corresponding to different URSP Traffic descriptors in normative text; with the possible parameters given in a NOTE","secretary_remarks":"Revision of S2-1904656. Revised in parallel session to S2-1904769.","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24870,"status":"revised","reservation_date":"2019-04-15 10:44:39","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904656","revisedto":"S2-1904769","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":1070.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904764.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904765","title":"Redundant PDU session handling","source":"CATT","contact":"Hucheng Wang","contact-id":56627,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the SMF can keep both PDU sessions or release one PDU session or both PDU sessions.","secretary_remarks":"Revision of S2-1904657. For e-mail approval. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24950,"status":"agreed","reservation_date":"2019-04-15 10:44:40","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904657","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1173.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904765.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904766","title":"PCF handling for redundant PDU sessions","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: The SMF uses the S-NSSAI and DNN to select the same PCF for the two redundant PDU session. The PCF uses the S-NSSAI and DNN to know these two PDU sessions is to be handled redundantly and generates the same PCC rules for these two PDU Session, except the different UE IP addresses in the PCC rules for IP PDU Session. When PCF decides to update the PCC rules it sends the latest PCC rules to both SMFs simutanously. The two redundant PDU Sessions have same PDU Session AMBR. UE-AMBR is enforced as defined in clause 5.7.2.6. The SMF establishes QoS flows based on the PCC rules. If the SMF determines this PDU Session should go via Secondary NG-RAN, the SMF may not establishes the QoS Flows which are not subject to redundantly handling.","secretary_remarks":"Revision of S2-1904658. WITHDRAWN","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25010,"status":"withdrawn","reservation_date":"2019-04-15 10:44:41","uploaded":null,"revisionof":"S2-1904658","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1254.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904767","title":"Explicit indication of AF response to be expected for runtime coordination with AF","source":"Huawei, Hisilicon, Samsung","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The paper proposes to add a separate indication in the AF request as part of AF subscription, for indicating AF response to be expected. When the indicaiton is included, the SMF may accordingly determine to perform coordination with the AF and to wait for AF response.","secretary_remarks":"Revision of S2-1904686. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25080,"status":"agreed","reservation_date":"2019-04-15 10:44:42","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904686","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1144.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904767.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904768","title":"Explicit indication of AF response to be expected for runtime coordination with AF","source":"Huawei, Hisilicon, Samsung","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 6.3.1 to include indication of AF response to be expected as part of AF subscription information.","secretary_remarks":"Revision of S2-1904687. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":25110,"status":"agreed","reservation_date":"2019-04-15 10:44:43","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904687","revisedto":"","release":"Rel-16","crspec":23.503,"crspecversion":"16.0.0","workitem":[{"winame":"5G_URLLC"}],"crnumber":243.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904768.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904769","title":"Clarification to support associating URLLC traffic to redundant PDU sessions","source":"OPPO, Ericsson","contact":"Yang Xu","contact-id":63572,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: in 23.501, describe in order to setup two redundant PDU sessions with different combination of DNN\/S-NSSAI, the two redundant PDU sessions are corresponding to different URSP Traffic descriptors in normative text; with the possible parameters given in a NOTE","secretary_remarks":"Revision of S2-1904764. Agreed in parallel session This was Block approved","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24880,"status":"agreed","reservation_date":"2019-04-15 10:44:44","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904764","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"5G_URLLC"}],"crnumber":1070.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-190412","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904769.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1904822","title":"UP connection Deactivation for URLLC PDU Session","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the Service Request and AN Releasae procedure to activate\/deactivate the User Plane of the PDU Sessions for URLLC. The PDU Session for URLLC is either with redudant I-UPFs or with redudant N3\/N9 tunnels.","secretary_remarks":"Revision of S2-1904762. For e-mail approval. This CR was agreed","agenda_item_sort_order":43,"ainumber":"6.","ainame":"Enhancement of URLLC supporting in 5GC (5G_URLLC)","tdoc_agenda_sort_order":24760,"status":"agreed","reservation_date":"2019-04-15 10:49:40","uploaded":"2019-04-15 11:18:03","revisionof":"S2-1904762","revisedto":"S2-1905107","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1138.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904822.zip","group":"S2","meeting":"S2-132","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]