[{"name":"S2-1902953","title":"LS from RAN WG2: LS on assistance information for TSN traffic flows","source":"RAN WG2","contact":"Dawid Koziol","contact-id":68362,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has studied TSN traffic patterns, their characteristics and potential impact on QoS and scheduling in RAN. Considering the deterministic nature of TSN traffic, RAN WG2 has agreed that the knowledge of TSN traffic pattern is useful for the gNB to allow it to more efficiently schedule traffic either via Configured Grants, Semi-Persistent Scheduling or with dynamic grants. Therefore, it would be beneficial for the gNB to receive from the Core Network the following assistance information describing TSN traffic flow, e.g. upon QoS flow establishment: - message periodicity - message size - message arrival time at gNB (DL) and UE (UL). Action: RAN WG2 respectfully asks SA WG2 to perform required normative work to specify the procedures allowing the gNB to receive assistance information describing established traffic flow as described above.","secretary_remarks":"Postponed S2-1902723 from S2#131. Postponed.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22980,"status":"postponed","reservation_date":"2019-03-19 06:14:10","uploaded":"2019-03-29 07:20:31","revisionof":"S2-1902723","revisedto":"S2-1904856","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG1, RAN WG3","lsoriginalls":"R2-1902354","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1902953.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-1903003","title":"Discussion on solutions for key issue#3.2 TSN Time Synchronization","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"discussion","for":"Approval","abstract":"This contribution analyses the existing options for TSN time synchronization and gives the conclusion proposal.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22510,"status":"not treated","reservation_date":"2019-03-28 13:16:41","uploaded":"2019-04-02 14:14:49","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-1903003.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-1903004","title":"Conclusion proposal for key issue#3.2 TSN Time Synchronization","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To enable support for TSN time synchronization, it is recommended to select solution11#2 as the basis for normative work.","secretary_remarks":"Revised in parallel session to S2-1904619.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22420,"status":"revised","reservation_date":"2019-03-28 13:16:41","uploaded":"2019-04-02 14:14:49","revisionof":"","revisedto":"S2-1904619","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":18.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-1903004.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-1903051","title":"LS from RAN WG2: Reply LS on RAN Impact analysis due to TSN","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 for the LS on RAN impacts analysis due to TSN. RAN WG2 has discussed feasibility and scalability impacts of identified TSN Time synchronization solutions and has come to the following conclusions. Feasibility aspects: Deterministic gNB-UE delay required by Solution #17 presents feasibility challenges. Solution #28.X1 seems similar to Solution #17 and the same feasibility concerns applies to it. Otherwise, all other solutions seem feasible from RAN WG2 perspective, although the details of each solution are not known from the TR 23.734. Additionally, RAN WG2 would prefer that the User Plane AS protocol stack does not need to interpret\/understand information inside (g)PTP packet. Solution #19 is not preferred since it seems to have significant impact due to (g)PTP time-stamping in the User Plane AS protocol stack. On the other hand, Solution #28.X2, Solution #11 Option 2, Solution #11 Option 3 and Solution #11 Option 4 can be candidate solutions from RAN WG2 perspective, assuming that for each solution (g)PTP timestamping (if any) is done outside the User Plane AS protocol stack. Scalability aspects: RAN WG2 has not concluded whether there are scalability issues or not for solutions that require transport over the air of gPTP time synchronization messages using per-UE unicast. Action: RAN WG2 asks SA WG2 group to take RAN WG2 feedback into further consideration.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22340,"status":"noted","reservation_date":"2019-03-29 08:08:04","uploaded":"2019-03-29 10:31:48","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG1, RAN WG3, TSG RAN, TSG SA","lsoriginalls":"R2-1902369","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903051.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-1903052","title":"LS from RAN WG2: Reply LS on TSN integration in the 5G System","source":"RAN WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Action","abstract":"In S2-189051 SA WG2 requested RAN WGs to analyze whether KPIs relating to latency, reliability and synchronization accuracy set for TSN use cases and captured in TR 22.804 can be met. Action: SA WG2 would like to ask RAN WG1, RAN WG2 and RAN WG3 whether using the existing 3GPP defined synchronisation, prioritisation and scheduling mechanisms, potentially with some enhancements within RAN, can fulfil the performance requirements defined in clause 8.1 of TR 22.804. RAN WG2 responded tentatively to S2-189051 in R2-1816043. Additionally, in S1-163707, SA WG1 further clarified some of the TSN requirements and informed that after finalizing the related normative work, requirements of TSN use cases captured in TS 22.104 take precedence over those captured in TR 22.804. RAN WGs have now completed the evaluation related to the request from SA WG2 and would like to provide a reply as below. With respect to synchronization requirements: - The following feedback has been already provided to SA WG2: o Synchronization accuracy achievable over the Uu interface was analyzed by RAN WG1 and the feedback is provided in R1-1901470 o Synchronization accuracy between TSN GM clock and gNB was analyzed by RAN WG3 and the feedback is provided in R3-187252 - Additionally, RAN WG2 agreed that the granularity of timing information provided via RRC signalling (i.e. SIB and\/or unicast RRC message) will be no higher than 50 ns. - Considering the above and assuming 100 ns time error between TSN GM clock and gNB as well as the sub-carrier spacing (SCS) of 15 kHz, the overall synchronization accuracy error between a clock source and UE clock would be equal to 665 ns (i.e. 540ns (air interface accuracy) + 100ns (network accuracy) + 25 ns (granularity\/2)). RAN WG2 would like to point out that most UEs will achieve smaller errors when the network configures higher SCSs (as per RAN WG1 input in LS R1-1901470). - The above calculation assumes the propagation delay is either negligible (i.e. small service areas) or is compensated for in larger service areas. Without propagation delay compensation, for inter-site distances >200m, the gNB-to-UE timing synchronization accuracy may be worse than 1us. - RAN WG2 would like to point out that the synchronization requirement analysis above is a generic analysis and does not assume any particular SA WG2 solution. With respect to latency\/reliability requirements: - RAN WG1 has provided their feedback on the latency and reliability achievable on Uu interface in R1-1901470 - RAN WG2 would like to point out that, as indicated previously in R2-1816043, further gains with respect to reliability can be achieved by using PDCP duplication, e.g. if two links operate with 10-4 reliability in PHY\/MAC layer, then it is possible to achieve 10-8 reliability for a transmission on PDCP layer. PDCP duplication requires Carrier Aggregation or Dual-Connectivity support by the network and the UEs. - With respect to latency on RAN interfaces, RAN WG3 feedback is provided in R3-187252 In general, it can be concluded that NR, with some additional enhancements introduced in Rel-16, can meet the requirements in TS 22.104 with respect to latency, reliability and synchronization accuracy, as discussed above, for some network configurations and deployments. However, the performance depends on such aspects as utilized subcarrier spacing, FDD or TDD network type, backhaul type, cell density etc. For further details, SA WG2 can refer to TR 38.825, which will be submitted for approval to RAN#83 meeting in March 2019. Action: RAN WG2 respectfully asks SA WG2 to take the information provided above into account in their related work.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22350,"status":"noted","reservation_date":"2019-03-29 08:08:04","uploaded":"2019-03-29 10:31:48","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG1, RAN WG3, SA WG1, TSG RAN","lsoriginalls":"R2-1902371","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1903052.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-1903219","title":"TSN Integration Enhancement to Support TSN Pre-emption","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To support the Co-exist TSC traffic and non-TSC traffic in the UE and UPF, the UE and UPF needs to support the IEEE 802.1Qbu[YY] in N6 interface or the interface between the device (behind the UE) and the UE and map the Non-TSC traffic to non-SC QoS Flow and map the TSC traffic to TSC QoS Flow.","secretary_remarks":"Revised in parallel session to S2-1904626.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22800,"status":"revised","reservation_date":"2019-04-01 07:09:17","uploaded":"2019-04-02 14:31:42","revisionof":"","revisedto":"S2-1904626","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1076.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-1903219.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-1903241","title":"Procedures for support of Time Sensing Network","source":"vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the PDU session setup with the DNN for 5GS bridge, the UE reports the bridge related information at the UE side and the UPF reports the bridge related information at the UPF side. As long as the traffic class associated QoS flow is successfully setup, SMF deduces the 5GS bridge delay for the traffic class based on the received bridge delay between the UE and the TT at the UE side, the received bridge delay between the UPF and the TT at the UPF side, and the PDB of the QoS flow associated with the traffic class. The SMF exposes the bridge related information of the 5GS Bridge to the AF (directly or via NEF).","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22940,"status":"not treated","reservation_date":"2019-04-01 09:17:52","uploaded":"2019-04-02 14:14:49","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.502,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1162.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-1903241.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-1903273","title":"Addressing open issues for TSN","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Discussion","abstract":"This paper proposes a way forward for various open issues for TSN support.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22550,"status":"noted","reservation_date":"2019-04-01 12:49:30","uploaded":"2019-04-02 13:31:37","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-1903273.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-1903274","title":"Addressing Editor's notes on TSN","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce new terminology for TSN translator Clarifies - that link layer discovery as defined in IEEE 802.1AB is supported by TSN translator; - hybrid model is not supported in this release of the specification; - DS-TT and NW-TT are outside of UE and UPF; respectively; - 5GS provides AdminControlList and AdminBaseTime as defined in IEEE 802.1Qbv to the hold and forward buffer in DS-TT and NW-TT on a per Ethernet port basis;","secretary_remarks":"Revised in parallel session, merging S2-1903629 and S2-1903655, to S2-1904620.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22560,"status":"revised","reservation_date":"2019-04-01 12:52:25","uploaded":"2019-04-02 13:31:37","revisionof":"","revisedto":"S2-1904620","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1095.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-1903274.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-1903326","title":"TSN Time Synchronization Solutions: Down-selection","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":57197,"tdoctype":"discussion","for":"Agreement","abstract":"Discusses options for time synchronisation for TSN and proposes a way forward","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22520,"status":"not treated","reservation_date":"2019-04-01 18:35:58","uploaded":"2019-04-02 11:45:46","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-1903326.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-1903364","title":"5G bridge granularity","source":"Ericsson, China Mobile","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"We address the granularity of 5G virtual bridge integration with TSN, and recommend per UPF virtual bridges.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22880,"status":"not treated","reservation_date":"2019-04-01 20:59:38","uploaded":"2019-04-02 14:10:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"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-1903364.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-1903365","title":"Principle of 5G bridge port configuration","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"Bridge port configuration","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22890,"status":"not treated","reservation_date":"2019-04-01 20:59:38","uploaded":"2019-04-02 14:10:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"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-1903365.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-1903366","title":"Granularity of TSN bridge","source":"Ericsson, China Mobile","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the granularity of the TSN bridge","secretary_remarks":"Revised in parallel session, merging S2-1903613, to S2-1904627.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22840,"status":"revised","reservation_date":"2019-04-01 20:59:38","uploaded":"2019-04-02 14:10:35","revisionof":"","revisedto":"S2-1904627","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1119.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-1903366.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-1903371","title":"Comparison & Evaluation of Soln 11 Option 2 and 3","source":"Ericsson, Huawei, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Discussion","abstract":"Comparison of soln 11 option 2 and merged option 3 components with Soln #28.2 for Sync","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22450,"status":"noted","reservation_date":"2019-04-01 20:59:41","uploaded":"2019-04-02 14:35:00","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-1903371.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-1903372","title":"Conclusion for TSN time Sync Key issue 3.2","source":"Ericsson, Huawei, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Approval","abstract":"Proposes Soln#28.2B and soln 11 option 3 merged as way forward","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22330,"status":"not treated","reservation_date":"2019-04-01 20:59:41","uploaded":"2019-04-02 14:35:00","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.734,"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-1903372.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-1903373","title":"Support of TSN Time Sync for 5G","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Introduction of TSN Time Sync in 5GS","secretary_remarks":"LATE DOC: WITHDRAWN","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22990,"status":"withdrawn","reservation_date":"2019-04-01 20:59:41","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1121.0,"crrevision":"","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-1903374","title":"TSN-5GS QoS mapping partly at AF and PCF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"Analysis of the EN on AF vs. PCF QoS mapping for TSN, select partly in AF and PCF","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22950,"status":"not treated","reservation_date":"2019-04-01 20:59:42","uploaded":"2019-04-02 14:10:35","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-1903374.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-1903375","title":"TSN-5GS QoS mapping partly at AF and PCF","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The TSN AF is responsible for interacting with TSN network to collect the related information and mapping these information into appropriate service requirements towards PCF using existing AF to PCF communication. AF may provide additional information, so combined with this and PCF internal mapping table, PCF provides the appropriate 5QI value(s) towards the PDU session.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22960,"status":"not treated","reservation_date":"2019-04-01 20:59:42","uploaded":"2019-04-02 14:10:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1122.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-1903375.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-1903376","title":"TSN-5GS QoS mapping","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses the issues of QoS mapping between 5GS and TSN. We address the editor's note in Solution#30 'Mapping TSN parameters to 3GPP 5G QoS'.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22900,"status":"not treated","reservation_date":"2019-04-01 20:59:44","uploaded":"2019-04-02 14:10:35","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-1903376.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-1903377","title":"TSN-5GS QoS mapping","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Identify specific parameters from TSN standards as a minimum requirements for 5G QoS to be able to fulfil the service requirements. Specify the fundaments to build the TSN-5GS mapping table.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22910,"status":"not treated","reservation_date":"2019-04-01 20:59:44","uploaded":"2019-04-02 14:10:35","revisionof":"","revisedto":"S2-1905759","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1123.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-1903377.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-1903378","title":"Support for IEEE 802.1Qbv scheduling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Agreement","abstract":"Abstract of the contribution: This contribution discusses the issues of QoS mapping between 5GS and TSN. We address on Solution#30 TSN scheduling related parameters.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22970,"status":"not treated","reservation_date":"2019-04-01 20:59:45","uploaded":"2019-04-02 14:10:35","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-1903378.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-1903379","title":"Support for IEEE 802.1Qbv scheduling","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Include additional set of parameters to be Qvb compliant with minimal set feasible.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":23000,"status":"not treated","reservation_date":"2019-04-01 20:59:45","uploaded":"2019-04-02 14:10:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1124.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-1903379.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-1903441","title":"Discussionon on 5GS logical bridge management and QoS mapping","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"discussion","for":"Agreement","abstract":"Discuss on editor's notes on 5GS bridge management and QoS mapping.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22920,"status":"not treated","reservation_date":"2019-04-02 01:11:12","uploaded":"2019-04-02 14:07:20","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-1903441.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-1903442","title":"Granularity of 5GS logical TSN bridge and topology discovery","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: the granularity of 5GS Bridge is per UPF per TSN network the ports of 5GS Bridge supports LLDP as defined in 802.1AB","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22930,"status":"not treated","reservation_date":"2019-04-02 01:11:12","uploaded":"2019-04-02 14:07:20","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1145.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-1903442.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-1903443","title":"QoS parameters mapping of 5GS logical TSN bridge","source":"Huawei, HiSilicon","contact":"Runze Zhou","contact-id":60945,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: bind the MAC address used by the PDU Session with 5GS Bridge ID and port ID on UE\/TT side in order to deliver the traffic scheduling information to the correct PCF. PCF performs QoS mapping for 5GS bridge configuration","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":23010,"status":"not treated","reservation_date":"2019-04-02 01:11:13","uploaded":"2019-04-02 14:07:20","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1146.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-1903443.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-1903610","title":"Discussion on the TSN traffic for the 5G LAN group","source":"ZTE, China Southern Power Grid Co., Ltd","contact":"Zhendong Li","contact-id":38521,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses the scenario where the 5G LAN group traffic with the TSN requirement and gives the proposal.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22610,"status":"noted","reservation_date":"2019-04-02 08:21:53","uploaded":"2019-04-02 09:52:05","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-1903610.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-1903611","title":"Adding the TSN support for the 5G LAN group and communication between TSN end station.","source":"ZTE, China Southern Power Grid Co., Ltd","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding TSN Translator (TT) may both be UE side for TSN traffic. Modifying logical TSN bridge management to cover the communication between TSN end stations.","secretary_remarks":"Revised in parallel session to S2-1904621.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22620,"status":"revised","reservation_date":"2019-04-02 08:21:53","uploaded":"2019-04-02 09:52:05","revisionof":"","revisedto":"S2-1904621","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1196.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-1903611.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-1903612","title":"Discussion and proposal on the ENs in the TSC","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses the EN on NF mapping, traffic pattern and Bridge granularity, and give the proposal.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22710,"status":"noted","reservation_date":"2019-04-02 08:21:54","uploaded":"2019-04-02 14:38: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-1903612.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-1903613","title":"Resolving the EN on the bridge management","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose the per UPF bridge granularity. And propose the virtual port between UPF(PSA)","secretary_remarks":"Merged into S2-1904627","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22870,"status":"merged","reservation_date":"2019-04-02 08:21:54","uploaded":"2019-04-02 14:38:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1197.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-1903613.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-1903614","title":"Resolving the EN on traffic pattern to the TT","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing EN, and describe the how to use TSCAI. Also the TSN pattern information shall be provided to the TSN translator in the UE side.","secretary_remarks":"Revised in parallel session to S2-1904624.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22720,"status":"revised","reservation_date":"2019-04-02 08:21:55","uploaded":"2019-04-02 14:00:48","revisionof":"","revisedto":"S2-1904624","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1198.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-1903614.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-1903628","title":"TSC Synchronization between 5GS and TSN","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution discusses the time synchronization issues between 5GS as a TSN Bridge and TSN systems","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22530,"status":"not treated","reservation_date":"2019-04-02 08:39:51","uploaded":"2019-04-02 11:16:46","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-1903628.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-1903629","title":"TSN Translator and 5GS in TSC Architecture","source":"MediaTek Inc.","contact":"Guillaume Sebire","contact-id":45073,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TT residing inside\/outside the UPF or UE is left to implementation N60 is not specified in this release","secretary_remarks":"Merged into S2-1904620.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22590,"status":"merged","reservation_date":"2019-04-02 08:39:51","uploaded":"2019-04-02 11:16:46","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1204.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-1903629.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-1903635","title":"Enhancements to 5GS for support of TSC","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"discussion","for":"Agreement","abstract":"This contribution proposes how burst size is mapped to MDBV, the need of survival time, the clock the periodicity and burst arrival time refer to, and Burst Arrival Time usage.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22640,"status":"noted","reservation_date":"2019-04-02 09:08:26","uploaded":"2019-04-02 11:00:10","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-1903635.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-1903639","title":"How Burst size maps to MDBV","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution proposes how burst size is mapped to MDBV.","secretary_remarks":"Merged into S2-1904622","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22660,"status":"merged","reservation_date":"2019-04-02 09:12:26","uploaded":"2019-04-02 11:00:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1208.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-1903639.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-1903640","title":"The Need for survival time in TSC Assistance Information","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution proposes the need of survival time in TSC Assistance Information.","secretary_remarks":"Revised in parallel session to S2-1904623.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22690,"status":"revised","reservation_date":"2019-04-02 09:16:33","uploaded":"2019-04-02 11:00:10","revisionof":"","revisedto":"S2-1904623","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1209.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-1903640.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-1903641","title":"The clock the periodicity and burst arrival time should refer to","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution proposes which clock the periodicity and burst arrival time refer to.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22650,"status":"not treated","reservation_date":"2019-04-02 09:19:31","uploaded":"2019-04-02 11:00:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1210.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-1903641.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-1903642","title":"How the Burst Arrival Time is used by 5G System","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution proposes how the Burst Arrival Time is used by 5G System to determine information that can be used by NG-RAN for efficient scheduling.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22820,"status":"not treated","reservation_date":"2019-04-02 09:22:35","uploaded":"2019-04-02 11:00:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1211.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-1903642.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-1903646","title":"Evaluation for time synchronisation using TSN (key issue 3.2)","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It specifies the category and basic behaviors for each category of the time synchronisation using TSN.","secretary_remarks":"Revision of S2-1901924 from S2#131. Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22500,"status":"not treated","reservation_date":"2019-04-02 09:34:27","uploaded":"2019-04-02 11:00:10","revisionof":"S2-1901924","revisedto":"","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"FS_Vertical_LAN"}],"crnumber":2.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-1903646.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-1903647","title":"Study on enhanced support of Industrial IoT","source":"Nokia, Nokia Shanghai Bell, NTT DoCoMo, Interdigital, Verizon, ETRI, SK Telecom, NICT, AT&T, Telecom Italia, BMWi, KDDI, Siemens","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"SID new","for":"Approval","abstract":"Study on enhanced support of Industrial IoT","secretary_remarks":"Postponed","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22320,"status":"postponed","reservation_date":"2019-04-02 09:34:54","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"S2-1905587","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-1903647.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-1903649","title":"Updates to synchronization solution #11.2","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Supporting IEEE802.1AS compliance with preserving precision timestamp and support for gPTP slave port in UE. Clarifications and corrections related to robustness against realistic industrial working clock grand masters.","secretary_remarks":"Revised in S2-1903864","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22380,"status":"revised","reservation_date":"2019-04-02 09:34:54","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"S2-1903864","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":19.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-1903649.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-1903650","title":"Evaluation for TSN Time Synchronization Solution","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: --","secretary_remarks":"Add Summary of change. Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22490,"status":"not treated","reservation_date":"2019-04-02 09:34:55","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":20.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-1903650.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-1903651","title":"Conclusion for TSN Time Synchronization Solution","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Propose to specify Solution #11: Option 2 and solution #28 variant 1","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22360,"status":"not treated","reservation_date":"2019-04-02 09:34:56","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":21.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-1903651.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-1903652","title":"Update to Support TSAI for TSC Deterministic QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In 23.501, section 5.27.3 MDBV has already been defined for TSC QoS by the clause: 'Within each Period (defined by periodicity), TSC QoS flows are required to transmit only one burst of maximum size MDBV within the AN-PDB' The required burst size used to set the MDBV is a function of the TSN stream characteristics, which may be obtained by the AF\/Translator via several means that are out-of-scope for 3GPP.\u00a0\u00a0 Those may include: 1 - Directly from a CUC 2\u00a0- From The 801.Qbv Gate Parameters sent by the CNC to the AF\/Translator and port attributes known to the translator. 3 - Provisioned on the AF Furthermore, the TSCAI parameters defined in Table 5.27.2-1 are also characteristic of the TSN stream and the 5GS egress port schedules supplied by the CNC. It is therefore proposed that: 1 - For TSC QoS flows, MDBV is set to the TSC Burst Size obtained from the AF. If the AF does not provide a TSC Burst Size, then the MDBV is set to the default value for the TSC GBR 5QI. 2 - The TSCAI parameters provided by the SMF are set according to corresponding parameters obtained from the PCF\/AF.","secretary_remarks":"Revised in parallel session, merging S2-1903639, to S2-1904622.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22670,"status":"revised","reservation_date":"2019-04-02 09:34:57","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"S2-1904622","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1212.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-1903652.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-1903653","title":"Update to Support TSAI for TSC Deterministic QoS - Clock domain","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For efficient scheduling support in the RAN, TSCAI parameters are used to generate traffic pattern. In order for RAN to be able to generate traffic pattern based on burst arrival time and periodicity, it needs to know the clock domain that can be used as the reference and this is also under the assumption that RAN is connected to both 5G GM and external TSN GM. If the RAN is connected to 5G GM only, then by default, RAN uses that as a reference. If the RAN is connected to external domain and 5G GM, then it needs to know which of the clock domain can be used as a reference.","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22830,"status":"not treated","reservation_date":"2019-04-02 09:34:58","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"S2-1905589","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1213.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-1903653.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-1903654","title":"Introducing support for UE and UPF Residence Time for TSC Deterministic QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Residence time: In deterministic TSN networks, 802.1Qbv bridges have gate schedules that specify precise times (sub-millisecond accuracy) when frames for periodic deterministic traffic are transmitted. In the fully centralized model, which was adopted for R16 in S2-1902852, the CNC calculates these schedules based on an 802.1Qcc Bridge Delay managed object it obtains from the bridges. The Bridge Delay Managed Object contains minimum and maximum delays between ingress and egress ports, both independent and dependent of frame length. Every bridge, including the 5GS bridge must provide these delays per-traffic class to the CNC if it is to be a candidate to participate in the path between talker and listener. In the 5GS, the bridge, ingress port to egress port delay is comprised of three components: A UE Residence - the time to forward a packet between the UE port egress and Uu, including TSN Translator delay. The current PDB - From TS 23.501, section 5.7.3.4: 'The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the UPF that terminates the N6 interface.' UPF Residence Time - the time to forward a packet between the UPF port egress and N3, including TSN Translator delay. Since Residence times may vary among UEs and among UPFs, the 5GS bridge delay can be most accurately formulated after the UE is known and the UPF has been selected in PDU Session Establishment. The UE and UPF Residence times may be reported respectively from the UE and UPF\/SMF and exposed to the AF\/TSN Translator. The AF\/Translator may then calculate the bridge delay using the PDB it expects will be required for the TSN Streams. Residence times are also needed for the 5GS to make meaningful use of CNC provided transmission schedules. The CNC provided schedules correspond to transmission times from the UE\/Translator egress port (downlink) or a UPF\/Translator port (uplink). Burst Arrival Time TSC Assistance Information useful to the RAN must correspond to times on Uu. To derive Uu relevant times from egress port schedules the UE and UPF residence times are needed. With the introduction of residence times to adjust schedules, the EN: It is FFS how the Burst Arrival Time is used by 5G System to determine information that can be used by NG-RAN for efficient scheduling can be removed. Suggested timing related parameters are shown in figure 1. Figure 1 - Timing diagram for 5GS QoS (uplink example) To enable interaction with the CNC and derivation of TSC Assistance Information, this contribution introduces 23.501 text for UE and UPF residence times in the 5GS","secretary_remarks":"Revised in parallel session to S2-1904625.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22760,"status":"revised","reservation_date":"2019-04-02 09:34:59","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"S2-1904625","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1214.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-1903654.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-1903655","title":"TSC deployment configuration - resolution of EN","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify Hybrid Model is not supported in Rel-16","secretary_remarks":"CR Cover sheet corrupted! Merged into S2-1904620.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22600,"status":"merged","reservation_date":"2019-04-02 09:35:00","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1215.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-1903655.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-1903656","title":"Update to Support PDU Session Binding","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In 23.501, section 5.29.1 the following operations has been specified: In order to support TSN traffic scheduling over 5GS Bridge, the 5GS supports the following functions: - Report the bridge information of 5GS Bridge to TSN network. - Map the configuration information obtained from TSN network for 5GS Bridge into 5GS QoS within PDU Session and TSC Assistance Information for efficient time-aware scheduling, as defined at clause\u00a05.29.2. Bridge information reported to the CNC includes 802.1Qcc bridge delay attributes for the 5GS ports to be used for the path through the 5GS. Since these ports correspond to the UE and UPF, the UE must register, and establish a PDU Session for which one or more UPFs are selected. Once the UE and UPF are known, the 5GS can report bridge information to the TSN network, and the CNC can calculate port configuration using 802.1Qbv (as stipulated in 23.501, 5.29.2). There are two options for supporting 5GS QoS. 1 - Pre-Configured\/Static QoS: 5GS QoS for TSC streams is pre-configured or setup at PDU Session Establishment, prior to receiving path configuration information from the CNC. In this case TCSAI and other stream specific characteristics are not known, there is no TSC stream specific QoS applied in the 5GS, and default QoS parameters for the TSC 5QI must be used. AF triggered PDU Session Modification due to reception of 802.1Qbv Gate Parameter Tables is not required. 2 - Dynamic QoS: QoS for TSC streams is established via PDU Session Modification after the CNC has determined the e2e path and provided 802.1Qbv Gate Parameter Tables for the Egress port, and optionally other information has been provided to the AF that indicates the TSC stream QoS requirements (eg: information sent directly from a CUC to the AF). To modify the PDU session after receiving configuration information from the TSN network, a binding must be established between the PDU Session and Bridge Configuration information provided by 802.1Qbv. That way when the configuration information is received from the CNC, the PDU session to be modified is known. 802.1Qbv provides a Gate Parameter Table for 5GS bridge egress ports. For each traffic class on the port, a Gate Control List specifies a transmission gate state of 'open' or 'closed' as a function of time, independent of TSN Stream ingress ports. Furthermore, while the CNC calculations accommodate all TSN Streams for all UEs\/PDU Sessions on an egress Port, the bridge only receives per-port, per-traffic class information. 802.1Qbv does not provide stream level and ingress port information to the bridge. Hence the possible identifiers from the CNC that may be used to identify the PDU session are egress port Bridge ID and Port ID. We assume Traffic Class will be mapped to QoS Flow, as has been suggested in several contributions. There are two cases to consider: Downlink streams at the UE Egress Port: At PDU Session Establishment, the PDU Session may be uniquely bound to the Port ID assigned to the UE. When the CNC provides 802.1Qbv configuration information for that UE Port, a PDU Session Modification may be triggered based on the binding. Note that the gate states for a traffic class carrying a TSN Stream(s) will reflect the open\/closed needs of that stream(s) as a function of time. A 5GS QoS Flow that is mapped to a traffic class carrying the TSN traffic may be modified accordingly. Uplink Streams at a UPF Egress Port: Several bridge configuration options have been considered in S2-190172 and subsequent revisions. If the 5GS Bridge is configured as a 'per PDU Session based 5G bridge' (Option 4, where each UE\/PDU Session is a logical bridge), then at PDU Session Establishment, the PDU Session may be uniquely bound to the Bridge ID. When the CNC provides 802.1Qbv configuration information for that that Bridge ID, a PDU Session Modification may be triggered based on the binding. If the 5GS Bridge is configured as a 'per UE based 5G bridge' (Option 3, where eac","secretary_remarks":"Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":23020,"status":"not treated","reservation_date":"2019-04-02 09:35:01","uploaded":"2019-04-02 13:34:50","revisionof":"","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"5G_URLLC"}],"crnumber":1216.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-1903656.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-1903676","title":"Conclusion for time synchronisation using TSN (key issue 3.2)","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It specifies conclusion for time synchronisation using TSN.","secretary_remarks":"Revision of S2-1901927 from S2#131. Not Handled","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22540,"status":"not treated","reservation_date":"2019-04-02 09:37:32","uploaded":"2019-04-02 11:00:10","revisionof":"S2-1901927","revisedto":"","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"FS_Vertical_LAN"}],"crnumber":14.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-1903676.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-1903864","title":"Updates to synchronization solution #11.2","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Supporting IEEE802.1AS compliance with preserving precision timestamp and support for gPTP slave port in UE as per [x] IEEE\u00a0P802.1AS-Rev\/D7,5 ' Draft Standard for Local and Metropolitan Area Networks - Timing and Synchronization for Time-Sensitive Applications'. Origin time stamp (80 bits) can be copied to SIB message from received gPTP SYNC message. To convey TSN time, information of reference SFN (10 bits) and time offset within the reference SFN (20 bits) which define the point of NR time related to TSN time indicated in the origin times stamp. If BMCA founds best GM in UE side with considering also GM location impacts, then UE can support a gPTP slave port, where RRC signalling is used to convey TSN time from UE to gNB. This exploits greatly same IEs and mechanism used for conveying time information via SIB. Clarifications and corrections related to robustness against realistic industrial working clock grand masters characterized in [y] IEEE 802.1ASbt Industrial Requirements: 'White Paper about Industrial Requirements and Concepts @ Time Synchronization, Dual Time Scale in Factory & Energy Automation V1.02' and [z] Schriegel and Jasperneite: 'Investigation of Industrial Environmental Influences on Clock Sources and their Effect on the Synchronization Accuracy of IEEE 1588 ', 2007 IEEE International Symposium on Precision Clock Synchronization for Measurement, Control and Communication","secretary_remarks":"Revision of S2-1903649. CR number incorrect. Revised in parallel session to S2-1904618.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22390,"status":"revised","reservation_date":"2019-04-02 13:59:13","uploaded":"2019-04-02 14:10:13","revisionof":"S2-1903649","revisedto":"S2-1904618","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":19.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-1903864.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-1904566","title":"Merger of soln11.3 and Soln 28","source":"Ericsson, Huawei, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of soln 28 to incorporate option 3 aspects of soln 11 and provide a common soln.","secretary_remarks":"Revised in parallel session to S2-1904617.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22460,"status":"revised","reservation_date":"2019-04-15 10:39:30","uploaded":"2019-04-15 11:18:01","revisionof":"","revisedto":"S2-1904617","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":22.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-1904566.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-1904616","title":"Report on Drafting session on TSN","source":"Nokia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"report","for":"Discussion","abstract":"Report on Drafting session on TSN","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22370,"status":"noted","reservation_date":"2019-04-15 10:42:42","uploaded":"2019-04-15 11:18:01","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-1904616.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-1904617","title":"Merger of soln11.3 and Soln 28","source":"Ericsson, Huawei, ZTE, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of soln 28 to incorporate option 3 aspects of soln 11 and provide a common soln.","secretary_remarks":"Revision of S2-1904566. Revised in parallel session to S2-1904716.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22470,"status":"revised","reservation_date":"2019-04-15 10:42:42","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1904566","revisedto":"S2-1904716","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"FS_Vertical_LAN"}],"crnumber":22.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-1904617.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-1904618","title":"Updates to synchronization solution #11.2","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Supporting IEEE802.1AS compliance with preserving precision timestamp and support for gPTP slave port in UE as per [x] IEEE\u00a0P802.1AS-Rev\/D7,5 ' Draft Standard for Local and Metropolitan Area Networks\u2014 Timing and Synchronization for Time-Sensitive Applications'. Origin time stamp (80 bits) can be copied to SIB message from received gPTP SYNC message. To convey TSN time, information of reference SFN (10 bits) and time offset within the reference SFN (20 bits) which define the point of NR time related to TSN time indicated in the origin times stamp. If BMCA founds best GM in UE side with considering also GM location impacts, then UE can support a gPTP slave port, where RRC signalling is used to convey TSN time from UE to gNB. This exploits greatly same IEs and mechanism used for conveying time information via SIB. Clarifications and corrections related to robustness against realistic industrial working clock grand masters characterized in [y] IEEE 802.1ASbt Industrial Requirements: 'White Paper about Industrial Requirements and Concepts @ Time Synchronization, Dual Time Scale in Factory & Energy Automation V1.02' and [z] Schriegel and Jasperneite: 'Investigation of Industrial Environmental Influences on Clock Sources and their Effect on the Synchronization Accuracy of IEEE 1588 ', 2007 IEEE International Symposium on Precision Clock Synchronization for Measurement, Control and Communication","secretary_remarks":"Revision of S2-1903864. Revised in parallel session to S2-1904715.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22400,"status":"revised","reservation_date":"2019-04-15 10:42:43","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903864","revisedto":"S2-1904715","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"FS_Vertical_LAN"}],"crnumber":19.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-1904618.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-1904619","title":"Conclusion proposal for key issue#3.2 TSN Time Synchronization","source":"Vivo, Nokia, Nokia Shanghai Bell","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To enable support for TSN time synchronization, it is recommended to agree the new merged Solution#28A as the WA for normative work. As part of normative work, it needs to be determined whether the reference time of the TSCAI parameters is based on the 5G GM clock or the external TSN GM clock.","secretary_remarks":"Revision of S2-1903004. Revised in parallel session to S2-1904717.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22430,"status":"revised","reservation_date":"2019-04-15 10:42:44","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903004","revisedto":"S2-1904717","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":18.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-1904619.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-1904620","title":"Addressing Editor's notes on TSN","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce new terminology for TSN translator Clarifies - that link layer discovery as defined in IEEE 802.1AB is supported by TSN translator; - hybrid model is not supported in this release of the specification; - DS-TT and NW-TT are outside of UE and UPF; respectively; - 5GS provides AdminControlList and AdminBaseTime as defined in IEEE 802.1Qbv to the hold and forward buffer in DS-TT and NW-TT on a per Ethernet port basis;","secretary_remarks":"Revision of S2-1903274, merging S2-1903629 and S2-1903655. Revised in parallel session to S2-1904718.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22570,"status":"revised","reservation_date":"2019-04-15 10:42:45","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903274","revisedto":"S2-1904718","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.1","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1095.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-1904620.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-1904621","title":"Adding the TSN support for the 5G LAN group and communication between TSN end station.","source":"ZTE, China Southern Power Grid Co., Ltd","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding TSN Translator (TT) may both be UE side for TSN traffic. Modifying logical TSN bridge management to cover the communication between TSN end stations.","secretary_remarks":"Revision of S2-1903611. Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22630,"status":"noted","reservation_date":"2019-04-15 10:42:46","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903611","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1196.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-1904621.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-1904622","title":"Update to Support TSAI for TSC Deterministic QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In 23.501, section 5.27.3 MDBV has already been defined for TSC QoS by the clause: 'Within each Period (defined by periodicity), TSC QoS flows are required to transmit only one burst of maximum size MDBV within the AN-PDB' The required burst size used to set the MDBV is a function of the characteristics of the TSN streams that will be allocated to the same 5G QoS flow in a PDU session, which may be obtained by the AF\/Translator via several means that are out-of-scope for 3GPP.\u00a0\u00a0 Those may include: 1 - Directly from a CUC 2 - Provisioned on the AF Furthermore, the TSCAI parameters defined in Table 5.27.2-1 are also characteristic of the TSN stream and the 5GS egress port schedules supplied by the CNC. It is therefore proposed that: 1 - For TSC QoS flows, MDBV is set to the TSC Maximum Burst Size of the aggregated TSC streams obtained from the AF. If the AF does not provide a TSC Burst Size, then the MDBV is set to the default value for the TSC GBR 5QI. 2 - The TSCAI parameters provided by the SMF are set according to corresponding parameters obtained from the PCF\/AF. Qbv does not provide information per TSC stream","secretary_remarks":"Revision of S2-1903652, merging S2-1903639. Agreed in parallel session This was Block approved","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22680,"status":"agreed","reservation_date":"2019-04-15 10:42:47","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903652","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1212.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"SP-190428","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904622.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-1904623","title":"The Need for survival time in TSC Assistance Information","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This contribution proposes the need of survival time in TSC Assistance Information.","secretary_remarks":"Revision of S2-1903640. Postponed","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22700,"status":"postponed","reservation_date":"2019-04-15 10:42:48","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903640","revisedto":"S2-1905626","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1209.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-1904623.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-1904624","title":"Resolving the EN on traffic pattern to the TT","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing EN, and describe the how to use TSCAI.","secretary_remarks":"Revision of S2-1903614. Revised in parallel session to S2-1904720.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22730,"status":"revised","reservation_date":"2019-04-15 10:42:49","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903614","revisedto":"S2-1904720","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1198.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-1904624.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-1904625","title":"Introducing support for UE and UPF Residence Time for TSC Deterministic QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Residence time: In deterministic TSN networks, 802.1Qbv bridges have gate schedules that specify precise times (sub-millisecond accuracy) when frames for periodic deterministic traffic are transmitted. In the fully centralized model, which was adopted for R16 in S2-1902852, the CNC calculates these schedules based on an 802.1Qcc Bridge Delay managed object it obtains from the bridges. The Bridge Delay Managed Object contains minimum and maximum delays between ingress and egress ports, both independent and dependent of frame length. Every bridge, including the 5GS bridge must provide these delays per-traffic class to the CNC if it is to be a candidate to participate in the path between talker and listener. In the 5GS, the bridge, ingress port to egress port delay is comprised of three components: A UE Residence - the time to forward a packet between the UE port egress and Uu, including TSN Translator delay. The current PDB - From TS 23.501, section 5.7.3.4: 'The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the UPF that terminates the N6 interface.' UPF Residence Time - the time to forward a packet between the UPF port egress and N3, including TSN Translator delay. Since Residence times may vary among UEs and among UPFs, the 5GS bridge delay can be most accurately formulated after the UE is known and the UPF has been selected in PDU Session Establishment. The UE and UPF Residence times may be reported respectively from the UE and UPF\/SMF and exposed to the AF\/TSN Translator. The AF\/Translator may then calculate the bridge delay using the PDB it expects will be required for the TSN Streams. Residence times are also needed for the 5GS to make meaningful use of CNC provided transmission schedules. The CNC provided schedules correspond to transmission times from the UE\/Translator egress port (downlink) or a UPF\/Translator port (uplink). Burst Arrival Time TSC Assistance Information useful to the RAN must correspond to times on Uu. To derive Uu relevant times from egress port schedules the UE and UPF residence times are needed. With the introduction of residence times to adjust schedules, the EN: It is FFS how the Burst Arrival Time is used by 5G System to determine information that can be used by NG-RAN for efficient scheduling can be removed. Suggested timing related parameters are shown in figure 1. Figure 1 - Timing diagram for 5GS QoS (uplink example) To enable interaction with the CNC and derivation of TSC Assistance Information, this contribution introduces 23.501 text for UE and UPF residence times in the 5GS","secretary_remarks":"Revision of S2-1903654. Revised in parallel session to S2-1904719.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22770,"status":"revised","reservation_date":"2019-04-15 10:42:50","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903654","revisedto":"S2-1904719","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1214.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-1904625.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-1904626","title":"TSN Integration Enhancement to Support TSN Pre-emption","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To support the Co-exist TSC traffic and non-TSC traffic in the UE and UPF, the UE and UPF needs to support the IEEE 802.1Qbu[YY] in N6 interface or the interface between the device (behind the UE) and the UE and map the Non-TSC traffic to non-SC QoS Flow and map the TSC traffic to TSC QoS Flow.","secretary_remarks":"Revision of S2-1903219. Noted in parallel session","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22810,"status":"noted","reservation_date":"2019-04-15 10:42:51","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903219","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1076.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-1904626.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-1904627","title":"Granularity of TSN bridge","source":"Ericsson, China Mobile, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the granularity of the TSN bridge","secretary_remarks":"Revision of S2-1903366, merging S2-1903613. Revised in parallel session to S2-1904721.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22850,"status":"revised","reservation_date":"2019-04-15 10:42:52","uploaded":"2019-04-15 11:18:01","revisionof":"S2-1903366","revisedto":"S2-1904721","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1119.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-1904627.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-1904715","title":"Updates to synchronization solution #11.2","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Supporting IEEE802.1AS compliance with preserving precision timestamp and support for gPTP slave port in UE as per [x] IEEE\u00a0P802.1AS-Rev\/D7,5 ' Draft Standard for Local and Metropolitan Area Networks\u2014 Timing and Synchronization for Time-Sensitive Applications'. Origin time stamp (80 bits) can be copied to SIB message from received gPTP SYNC message. To convey TSN time, information of reference SFN (10 bits) and time offset within the reference SFN (20 bits) which define the point of NR time related to TSN time indicated in the origin times stamp. If BMCA founds best GM in UE side with considering also GM location impacts, then UE can support a gPTP slave port, where RRC signalling is used to convey TSN time from UE to gNB. This exploits greatly same IEs and mechanism used for conveying time information via SIB. Clarifications and corrections related to robustness against realistic industrial working clock grand masters characterized in [y] IEEE 802.1ASbt Industrial Requirements: 'White Paper about Industrial Requirements and Concepts @ Time Synchronization, Dual Time Scale in Factory & Energy Automation V1.02' and [z] Schriegel and Jasperneite: 'Investigation of Industrial Environmental Influences on Clock Sources and their Effect on the Synchronization Accuracy of IEEE 1588 ', 2007 IEEE International Symposium on Precision Clock Synchronization for Measurement, Control and Communication","secretary_remarks":"Revision of S2-1904618. Agreed in parallel session This was Block approved","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22410,"status":"agreed","reservation_date":"2019-04-15 10:44:10","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904618","revisedto":"","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"FS_Vertical_LAN"}],"crnumber":19.0,"crrevision":3.0,"crcategory":"B","tsg_crp":"SP-190432","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904715.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-1904716","title":"Merger of soln11.3 and Soln 28","source":"Ericsson, Huawei, ZTE, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update of soln 28 to incorporate option 3 aspects of soln 11 and provide a common soln.","secretary_remarks":"Revision of S2-1904617. Agreed in parallel session This was Block approved","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22480,"status":"agreed","reservation_date":"2019-04-15 10:44:11","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904617","revisedto":"","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"FS_Vertical_LAN"}],"crnumber":22.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-190432","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904716.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-1904717","title":"Conclusion proposal for key issue#3.2 TSN Time Synchronization","source":"Vivo, Nokia, Nokia Shanghai Bell, Ericsson, Huawei, Samsung, ZTE, Qualcomm Incorporated, MediaTek Inc.","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To enable support for TSN time synchronization, it is recommended to agree the new merged Solution#28A as the WA for normative work. Whether the reference time of the TSC AI parameters, is based on the 5G GM clock or the external TSN GM clock will be resolved in normative phase.","secretary_remarks":"Revision of S2-1904619. This CR was endorsed as a working assumption.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22440,"status":"endorsed","reservation_date":"2019-04-15 10:44:12","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904619","revisedto":"","release":"Rel-16","crspec":23.734,"crspecversion":"16.1.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":18.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-1904717.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-1904718","title":"Addressing Editor's notes on TSN","source":"Qualcomm Incorporated, Nokia, Nokia Shanghai Bell","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduce new terminology for TSN translator Clarifies - that link layer discovery as defined in IEEE 802.1AB is supported by TSN translator; - hybrid model is not supported in this release of the specification; - DS-TT and NW-TT are outside of UE and UPF; respectively; - 5GS provides AdminControlList and AdminBaseTime as defined in IEEE 802.1Qbv to the hold and forward buffer in DS-TT and NW-TT on a per Ethernet port basis;","secretary_remarks":"Revision of S2-1904620. This CR was agreed","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22580,"status":"agreed","reservation_date":"2019-04-15 10:44:13","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904620","revisedto":"S2-1905222","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1095.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-1904718.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-1904719","title":"Introducing support for UE and UPF Residence Time for TSC Deterministic QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Residence time: In deterministic TSN networks, 802.1Qbv bridges have gate schedules that specify precise times (sub-millisecond accuracy) when frames for periodic deterministic traffic are transmitted. In the fully centralized model, which was adopted for R16 in S2-1902852, the CNC calculates these schedules based on an 802.1Qcc Bridge Delay managed object it obtains from the bridges. The Bridge Delay Managed Object contains minimum and maximum delays between ingress and egress ports, both independent and dependent of frame length. Every bridge, including the 5GS bridge must provide these delays per-traffic class to the CNC if it is to be a candidate to participate in the path between talker and listener. In the 5GS, the bridge, ingress port to egress port delay is comprised of three components: A UE Residence - the time to forward a packet between the UE port egress and Uu, including TSN Translator delay. The current PDB - From TS 23.501, section 5.7.3.4: 'The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the UPF that terminates the N6 interface.' UPF Residence Time - the time to forward a packet between the UPF port egress and N3, including TSN Translator delay. Since Residence times may vary among UEs and among UPFs, the 5GS bridge delay can be most accurately formulated after the UE is known and the UPF has been selected in PDU Session Establishment. The UE and UPF Residence times may be reported respectively from the UE and UPF\/SMF and exposed to the AF\/TSN Translator. The AF\/Translator may then calculate the bridge delay using the PDB it expects will be required for the TSN Streams. Residence times are also needed for the 5GS to make meaningful use of CNC provided transmission schedules. The CNC provided schedules correspond to transmission times from the UE\/Translator egress port (downlink) or a UPF\/Translator port (uplink). Burst Arrival Time TSC Assistance Information useful to the RAN must correspond to times on Uu. To derive Uu relevant times from egress port schedules the UE and UPF residence times are needed. With the introduction of residence times to adjust schedules, the EN: It is FFS how the Burst Arrival Time is used by 5G System to determine information that can be used by NG-RAN for efficient scheduling can be removed. Suggested timing related parameters are shown in figure 1. Figure 1 - Timing diagram for 5GS QoS (uplink example) To enable interaction with the CNC and derivation of TSC Assistance Information, this contribution introduces 23.501 text for UE and UPF residence times in the 5GS","secretary_remarks":"Revision of S2-1904625. Revised to S2-1904801.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22780,"status":"revised","reservation_date":"2019-04-15 10:44:14","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904625","revisedto":"S2-1904801","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1214.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-1904719.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-1904720","title":"Resolving the EN on traffic pattern to the TT","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing EN, and describe the how to use TSCAI.","secretary_remarks":"Revision of S2-1904624. Revised to S2-1904820.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22740,"status":"revised","reservation_date":"2019-04-15 10:44:15","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904624","revisedto":"S2-1904820","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1198.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-1904720.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-1904721","title":"Granularity of TSN bridge","source":"Ericsson, China Mobile, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the granularity of the TSN bridge","secretary_remarks":"Revision of S2-1904627. Agreed in parallel session This was Block approved","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22860,"status":"agreed","reservation_date":"2019-04-15 10:44:16","uploaded":"2019-04-15 11:18:02","revisionof":"S2-1904627","revisedto":"","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1119.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-190428","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_132_XiAn\/Docs\/S2-1904721.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-1904801","title":"Introducing support for UE and UPF Residence Time for TSC Deterministic QoS","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Residence time: In deterministic TSN networks, 802.1Qbv bridges have gate schedules that specify precise times (sub-millisecond accuracy) when frames for periodic deterministic traffic are transmitted. In the fully centralized model, which was adopted for R16 in S2-1902852, the CNC calculates these schedules based on an 802.1Qcc Bridge Delay managed object it obtains from the bridges. The Bridge Delay Managed Object contains minimum and maximum delays between ingress and egress ports, both independent and dependent of frame length. Every bridge, including the 5GS bridge must provide these delays per-traffic class to the CNC if it is to be a candidate to participate in the path between talker and listener. In the 5GS, the bridge, ingress port to egress port delay is comprised of three components: A UE Residence - the time to forward a packet between the UE port egress and Uu, including TSN Translator delay. The current PDB - From TS 23.501, section 5.7.3.4: 'The Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed between the UE and the UPF that terminates the N6 interface.' UPF Residence Time - the time to forward a packet between the UPF port egress and N3, including TSN Translator delay. Since Residence times may vary among UEs and among UPFs, the 5GS bridge delay can be most accurately formulated after the UE is known and the UPF has been selected in PDU Session Establishment. The UE and UPF Residence times may be reported respectively from the UE and UPF\/SMF and exposed to the AF\/TSN Translator. The AF\/Translator may then calculate the bridge delay using the PDB it expects will be required for the TSN Streams. Residence times are also needed for the 5GS to make meaningful use of CNC provided transmission schedules. The CNC provided schedules correspond to transmission times from the UE\/Translator egress port (downlink) or a UPF\/Translator port (uplink). Burst Arrival Time TSC Assistance Information useful to the RAN must correspond to times on Uu. To derive Uu relevant times from egress port schedules the UE and UPF residence times are needed. With the introduction of residence times to adjust schedules, the EN: It is FFS how the Burst Arrival Time is used by 5G System to determine information that can be used by NG-RAN for efficient scheduling can be removed. Suggested timing related parameters are shown in figure 1. Figure 1 - Timing diagram for 5GS QoS (uplink example) To enable interaction with the CNC and derivation of TSC Assistance Information, this contribution introduces 23.501 text for UE and UPF residence times in the 5GS","secretary_remarks":"Revision of S2-1904719. This CR was agreed","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22790,"status":"agreed","reservation_date":"2019-04-15 10:49:22","uploaded":"2019-04-15 11:18:03","revisionof":"S2-1904719","revisedto":"S2-1905223, S2-1905361, S2-1905523, S2-1905677, S2-1905717","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1214.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-1904801.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-1904820","title":"Resoving the EN on traffic patern to the TT","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing EN, and describe the how to use TSCAI.","secretary_remarks":"Revision of S2-1904720. For e-mail approval. e-mail revision 3 approved. Revised to S2-1904841.","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22750,"status":"revised","reservation_date":"2019-04-15 10:49:38","uploaded":"2019-04-15 11:18:03","revisionof":"S2-1904720","revisedto":"S2-1904841","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1198.0,"crrevision":3.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-1904820.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-1904841","title":"Resoving the EN on traffic patern to the TT","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing EN, and describe the how to use TSCAI.","secretary_remarks":"e-mail revision 3 of S2-1904820. This CR was agreed","agenda_item_sort_order":39,"ainumber":"6.15.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":22751,"status":"agreed","reservation_date":"2019-04-19 10:27:32","uploaded":"2019-04-19 10:29:50","revisionof":"S2-1904820","revisedto":"S2-1905362, S2-1905524","release":"Rel-16","crspec":23.501,"crspecversion":"16.0.2","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1198.0,"crrevision":4.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-1904841.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}]