[{"name":"S2-1910892","title":"LS from RAN WG2: LS to SA2 on reference time delivery","source":"RAN WG2","contact":"Zhenhua Zou","contact-id":73815,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has agreed to transmit the 5G internal system clock to UE to support TSN time synchronization solution developed by SA WG2 and specified in clause 5.27 of TS 23.501. From RAN point of view, it is useful for RAN to know whether a connected UE requires getting the 5G internal system clock. The motivation is that RAN does not need to transmit the reference timing information, if there is no UEs requiring such information. RAN WG2 would like to ask SA WG2 to provide information on whether and how the need for reference timing information can be determined for any given connected UE in Rel-16. Action: RAN WG2 respectfully asks SA WG2 to provide feedbacks on the above question.","secretary_remarks":"Response drafted in S2-1911362. Final response in S2-1912769","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18460,"status":"replied to","reservation_date":"2019-10-30 09:03:47","uploaded":"2019-11-04 09:40:45","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-1914213","lsreply":"S2-1912769","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910892.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910924","title":"TSN parameters","source":"NTT DOCOMO, Nokia, Nokia Shanghai Bell","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) Change the 'TSN QoS parameters' to 'TSN QoS information' 2) Add a summary of all TSN parameters from AF to PCF to 6.1.3.23. Replace the 'Manageable Ethernet Port' with '5GS Bridge information' in parameters from SMF to PCF and from PCF to AF, as the information needs to convey also the Bridge ID, etc. The Delay Requirement from AF to PCF must be in reference to 5G time, since PCF cannot convert the TSN time to 5G time. 3) Add TSN time domain to TSN AF QoS container from AF to PCF and from PCF to SMF. 4) Add TSC Burst Size to the QoS information from AF to PCF. 5) UE-DS-TT residence time","secretary_remarks":"Revision of S2-1909810 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18990,"status":"available","reservation_date":"2019-11-01 12:58:21","uploaded":"2019-11-08 13:48:41","revisionof":"S2-1909810","revisedto":"S2-2000075","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":344.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910924.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910925","title":"UPF reporting the time comparison","source":"NTT DOCOMO, Nokia, Nokia Shanghai Bell","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Introduces Session Reporting Rule that can be used to instruct the UPF to measure and report TSC time offset and cumulative rateRatio","secretary_remarks":"Revision of S2-1909783 from S2#135. Postponed","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18510,"status":"postponed","reservation_date":"2019-11-01 13:42:36","uploaded":"2019-11-08 13:48:41","revisionof":"S2-1909783","revisedto":"S2-1912367","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1898.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910925.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910926","title":"UPF reporting the time comparison","source":"NTT DOCOMO, Nokia, Nokia Shanghai Bell","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) The SMF may adjust the TSCAI based on the measured time offset reported by UPF. This procedure needs to be introduced to TS 23.502 (PDU session establishment and modification procedures, and N4 session level reporting procedures). 2) In the case the UPF reports the change of the cumulative rateRatio between TSN time and 5G time to SMF, the SMF updates the TSCAI to RAN. 3) In Npcf_PolicyAuthorization_Create\/Update definitions, the correct reference to TSN AF parameters is 6.1.3.23 in TS 23.503. 4) Add the 5GS bridge information as an input parameter to the Npcf_SMPolicyControl_Update service operation. This construct contains all TSN related parameters that the SMF needs to be able to report to the PCF.","secretary_remarks":"Revision of S2-1908786 from S2#135. Revised in parallel session, merging S2-1911540, to S2-1912368.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18530,"status":"revised","reservation_date":"2019-11-01 13:52:51","uploaded":"2019-11-08 13:48:41","revisionof":"S2-1908786","revisedto":"S2-1912368","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1673.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910926.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910957","title":"5GS Bridge Delay Reporting","source":"Nokia, Nokia Shanghai Bell, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: There might be a drift and delta in the clock between 5G GM and TSN GM. Only UPF has access to both clocks and it is able to report the delta\/drift when it exceeds a certain threshold towards SMF. Thus, only SMF is able to consider this drift for the calculation of residence time based TSN GM and report it to the PCF\/AF. TSN AF can use the configured packet delay (UE-UPF) to compute 5GS Bridge delay. Then it can compute IEEE TSN parameters such as min\/max dependent\/independent delay parameters and report them to CNC.","secretary_remarks":"Revision of S2-1909729 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18810,"status":"available","reservation_date":"2019-11-04 02:53:06","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909729","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1884.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910957.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910958","title":"Delay budget for 5GS Bridge","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that the PCF should be able to make use of UE Mobility Restriction information, including CAG and Service Area restrictions and one or both of per (UPF, NG-RAN node) dynamic values of CN-PDB information and QoS Monitoring information to determine the maximum delay over the subset of network interfaces that will be used by a UE. That delay is used by the PCF to select the 5QI with its corresponding PDB, which is subsequently used by the SMF to determine the 5GS Bridge delay as specfied in TS23.501 clause 5.27.5.","secretary_remarks":"Revision of S2-1909730 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18870,"status":"available","reservation_date":"2019-11-04 02:53:07","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909730","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":341.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910958.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910959","title":"5GS Bridge Management","source":"Qualcomm Incorporated ?, Samsung ?, Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that LLDP is only supported in NW-TT (i.e. NW-TT also performs LLDP. In line with the analysis and proposal in S2-190xxyy, remove following Editor's notes\u00a0: - Clause 4.4.8.2: Editor's note: Whether both DS-TT and NW-TT or only NW-TT support Link layer connectivity discovery and reporting is FFS. - Clause 5.28.3.1: Editor's note: Whether TSN AF can write DS-TT and NW-TT port neighbour discovery configuration is FFS. Editor's note: Whether TSN AF needs to be able to read port management information and needs to be able to get port management capabilities is FFS. [\u2026] Clean up table 5.28.3.1-1 (remove duplicated row, add missing NOTEs in table). Revision to SA WG2#136: It is proposed to agree to following changes: The terms Bridge Address and relation to Bridge ID as well as Port Addresses and relation to Port numbers and Port MAC addresses build the basic bridge information as defined in IEEE 802.1Q-2018, clause 12.4.1 '(a) Bridge Address\u2014the MAC address for the Bridge from which the Bridge Identifiers used by STP, RSTP, and MSTP are derived (8.13.8, 13.26). (b) Bridge Name\u2014a text string of up to 32 characters, of locally determined significance. (c) Number of Ports\u2014the number of Bridge Ports (MAC Entities). (d) Port Addresses\u2014a list specifying the following for each Port: (a1) Port Number\u2014the number of the Bridge Port (13.27). (a2) Port Address\u2014the specific MAC address of the individual MAC Entity associated with the Port (8.13.2)' and clause 8.13.8 'A unique EUI-48 Universally Administered MAC address, termed the Bridge Address, shall be assigned to each Bridge. The Bridge Address may be the individual MAC address of a Bridge Port; in which case, use of the address of the lowest numbered Bridge Port (Port 1) is recommended'. Adding relevant information for LLDP support as defined in IEEE 802.1AB-2016 clause 8.5.2 'There are several ways in which a chassis may be identified and a chassis ID subtype is used to indicate the type of component being referenced by the chassis ID field.', clause 8.5.3 'A port ID subtype is used to indicate how the port is being referenced in the port ID field.', clause 8.5.4 'The Time To Live TLV indicates the number of seconds that the recipient LLDP agent is to regard the information associated with this MSAP identifier to be valid. (a) When the TTL field is non-zero the receiving LLDP agent is notified to completely replace all information associated with this MSAP identifier with the information in the received LLDPDU. (b) When the TTL field is set to zero, the receiving LLDP agent is notified to delete all system information associated with the LLDP agent\/port. This TLV may be used, for example, to signal that the sending port has initiated a port shutdown procedure. The Time To Live TLV is mandatory and shall be the third TLV in the LLDPDU.', clause 9.2.5.1 'adminStatus This variable indicates whether or not the LLDP agent is enabled. The defined values for this variable are as follows: (a) enabledRxTx: The LLDP agent is enabled for reception and transmission of LLDPDUs. This is the recommended default value. (b) enabledTxOnly: The LLDP agent is enabled for transmission of LLDPDUs only. (c) enabledRxOnly: The LLDP agent is enabled for reception of LLDPDUs only. (d) disabled: The LLDP agent is disabled for both reception and transmission.' And Table 11-2 (Management Attributes). The relevant information consists of the Chassis ID subtype (defined in IEEE spec), Chassis ID (it could be a MAC address, string or a name), Port ID subtype (defined in IEEE spec), Port ID (it could be a MAC address, string or a name), TTL and the Admin Status definition, which is required for the LLDP handling at the TSN AF and to perform the LLDP Frame validation and generation at the TSN translators DS-TT and NW-TT. (Note: Admin Status is defined for a LLDP Agent and is valid for all ports that belongs to the LLDP Agent). This information is necessary only if the bridge advertises towards th","secretary_remarks":"Revision of S2-1910625 from S2#135. Confirm Sources! Revised in parallel session to S2-1912360.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18220,"status":"revised","reservation_date":"2019-11-04 02:53:09","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1910625","revisedto":"S2-1912360","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1747.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910959.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910960","title":"5GS Time Sync corrections","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove references to M and S in the figure and corresponding reference below in the text.","secretary_remarks":"Revision of S2-1909732 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19080,"status":"available","reservation_date":"2019-11-04 02:53:10","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909732","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1886.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910960.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910961","title":"N4 Impacts - Bridge Management","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update N4 section to include the ability for UPF to report Mac Address, NW-TT\/DS-TT Port Number towards SMF. Also include exchange of Port management container transparently.","secretary_remarks":"Revision of S2-1909733 from S2#135. Revised in parallel session, merging S2-1911449, to S2-1912370.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18600,"status":"revised","reservation_date":"2019-11-04 02:53:12","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909733","revisedto":"S2-1912370","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1887.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910961.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910962","title":"TSC PDU Session Restrictions","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR precludes Home Routed Roaming for TSC PDU Sessions, EPS interworking with service continuity","secretary_remarks":"Revision of S2-1909735 from S2#135. Revised in parallel session to S2-1912365.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18440,"status":"revised","reservation_date":"2019-11-04 02:53:13","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909735","revisedto":"S2-1912365","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1889.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910962.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910963","title":"UPF selection for TSC PDU Sessions","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that an SMF should select a UPF (e.g. based on requested DNN\/S-NSSAI) that supports NW-TT functionality.","secretary_remarks":"Revision of S2-1909738 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18800,"status":"available","reservation_date":"2019-11-04 02:53:14","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909738","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1892.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910963.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910964","title":"UPF functional update for TSC","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR adds agreed upon UPF TSC functionalities to section 6.2.3","secretary_remarks":"Revision of S2-1909739 from S2#135. Revised in parallel session to S2-1912366.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18460,"status":"revised","reservation_date":"2019-11-04 02:53:15","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1909739","revisedto":"S2-1912366","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1893.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910964.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1910997","title":"Corrections for acronyms and general part on Time Sensitive Communication","source":"Nokia, Nokia Shanghai Bell","contact":"Yannick Lair","contact-id":76350,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1\/ Adding acronyms in clause 3.2. 2\/ Rephrasing for clause 4.4.8.1. 3\/ Replacement of 'CNC' occurences with 'TSN system'.","secretary_remarks":"Revision of S2-1909209 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19180,"status":"available","reservation_date":"2019-11-05 12:29:40","uploaded":"2019-11-08 21:02:40","revisionof":"S2-1909209","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1780.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1910997.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911125","title":"Correction on the bridge mangement and port management","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Add MAC addresses into the bridge information and add the information used to construct Bridge information. - Remove the subscribed traffic classes and VLANs. - Add per traffic class AdminIdleSlope, Static Filtering Entry, VID configuration to the port. - UPF doesn't trigger the transmission of the Port Management Information Container provided by NW-TT until the related PDU session established.","secretary_remarks":"Revision of S2-1909073 from S2#135. Revised in parallel session to S2-1912414.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18640,"status":"revised","reservation_date":"2019-11-07 03:33:31","uploaded":"2019-11-08 18:55:10","revisionof":"S2-1909073","revisedto":"S2-1912414","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1749.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911125.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911126","title":"Correction on bridge management and port management","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Remove the port number of NW-TT port in the response of port number allocation for DS-TT port - Clarify the port container transmission between SMF and PCF. - Remove Editor's note: Whether UE-DS-TT Residence Time is sent to AF is FFS.","secretary_remarks":"Revision of S2-1909074 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19120,"status":"available","reservation_date":"2019-11-07 03:33:34","uploaded":"2019-11-08 18:55:10","revisionof":"S2-1909074","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1730.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911126.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911128","title":"Correction on TSN parameters transmission","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Complete the transmission of TSN parameters in the related procedures.","secretary_remarks":"Revision of S2-1909077 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19000,"status":"available","reservation_date":"2019-11-07 03:33:40","uploaded":"2019-11-08 18:55:10","revisionof":"S2-1909077","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1731.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911128.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911129","title":"QoS mapping for uplink TSC communication","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - By means of common infomation between PSFP for ingress port and Traffic Forwarding information for egress port, associating the egress port for ingress port and reusing the TSN QoS parameter of the egress port as the TSN QoS paramenter of ingress port. - Clarify TSN parameters. - Corrections to alignment with 23.501.","secretary_remarks":"Revision of S2-1909078 from S2#135. Revised in parallel session to S2-1912412.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18780,"status":"revised","reservation_date":"2019-11-07 03:33:42","uploaded":"2019-11-08 18:55:10","revisionof":"S2-1909078","revisedto":"S2-1912412","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":325.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911129.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911171","title":"Updates for Bridge Dealy information reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The SMF maps the UE-DS-TT Residence Time and PDBs supported by the PDU Session from the 5G clock to a TSN clock based on the cumulative reteRatio between TSN time and 5G time, and the he SMF reports the UE-DS-TT Residence Time and PDBs (and the corresponding 5QIs) in reference to TSN time to the AF via PCF. The cumulative rateRatio is reported from the UPF which can measure the cumulative rateRatio between TSN time and 5G time. If the SMF received a cumulative rateRatio update from the UPF, it determines whether to update the 5GS Bridge delay information to the PCF.","secretary_remarks":"Revision of S2-1908940 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18820,"status":"available","reservation_date":"2019-11-07 09:02:38","uploaded":"2019-11-08 14:47:07","revisionof":"S2-1908940","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1727.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911171.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911172","title":"Updates for Bridge Delay information reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The SMF maps the UE-DS-TT Residence Time and PDBs supported by the PDU Session from the 5G clock to a TSN clock based on the cumulative rateRatio between the TSN time and 5G time, and the SMF reports the UE-DS-TT Residence Time and PDBs (and the corresonding 5QIs) in reference to TSN time to the AF via PCF.","secretary_remarks":"Revision of S2-1908941 from S2#135","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18830,"status":"available","reservation_date":"2019-11-07 09:02:41","uploaded":"2019-11-08 14:47:07","revisionof":"S2-1908941","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1700.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911172.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911358","title":"Clarifying gPTP message forwarding for multiple TSN PDU sessions","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove 'Only one PDU session per UE per UPF is used for sending gPTP messages regardless of how many external TSN working domains have their clock information delivered through a given UPF serving that UE.'","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19090,"status":"available","reservation_date":"2019-11-07 22:36:15","uploaded":"2019-11-08 17:46:40","revisionof":"","revisedto":"S2-2000081","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1951.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911358.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911359","title":"Clarifying gPTP support by NW-TT","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify in clause 5.27.1.3 that - NW-TT sends gPTP messages on N6 and inside PDU sessions towards DS-TT - NW-TT sends gPTP messages based on local configuration (e.g. configured per DNN\/S-NSSAI)","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19100,"status":"available","reservation_date":"2019-11-07 22:39:56","uploaded":"2019-11-08 17:46:40","revisionof":"","revisedto":"S2-2000083, S2-2000526","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1952.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911359.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911360","title":"Determining need for reference time delivery.","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"discussion","for":"Decision","abstract":"This paper discusses how to determine and signal need for reference time delivery to connected UEs.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18360,"status":"noted","reservation_date":"2019-11-07 22:43:25","uploaded":"2019-11-08 17:46:40","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_136_Reno\/Docs\/S2-1911360.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911361","title":"Control of delivery of 5G system time reference information","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a Note into 5.27.1.2.1 stating 'gNBs can determine whether to provide 5G system time reference information to UEs based on local configuration and the S-NSSAIs of PDU sessions of UEs being served by the gNB.'","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18510,"status":"available","reservation_date":"2019-11-07 22:45:36","uploaded":"2019-11-08 17:46:40","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1953.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911361.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911362","title":"[DRAFT] Reply LS on reference time delivery","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Response to S2-1910892. Revised in parallel session to S2-1912364.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18370,"status":"revised","reservation_date":"2019-11-07 22:50:15","uploaded":"2019-11-08 17:46:40","revisionof":"","revisedto":"S2-1912364","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911362.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911447","title":"Correction on hold and forward mechanism for PSFP","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR adds IEEE 802.1Qci PSFP for the hold and forward mechanism.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19160,"status":"available","reservation_date":"2019-11-08 05:43:19","uploaded":"2019-11-08 05:53:20","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1958.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911447.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911449","title":"Port Management Information Container over N4 reference point","source":"ETRI","contact":"Yooah Kang","contact-id":63871,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR adds Port Management Information Container to the PDR atrributes.","secretary_remarks":"Merged into S2-1912370","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18620,"status":"merged","reservation_date":"2019-11-08 05:45:26","uploaded":"2019-11-08 05:53:20","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1959.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911449.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911539","title":"Update the TSN Time Drift Threshold","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In order to prevent frequent offset updates from the UPF, the UPF sends the offset only when the time drift is larger than a drift threshold. The determination of the drift threshold by the SMF is based on information received from the TSN AF via PCF and is provided to the UPF by the SMF during the QoS Flow establishment or modification procedure. The SMF stores the drift threshold, if a smaller drift threshold is received from PCF, the SMF updates the stored drift threshold and provides the UPF with the new drift threshold.","secretary_remarks":"Revision of S2-1909135 from S2#135. Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18570,"status":"noted","reservation_date":"2019-11-08 09:16:23","uploaded":"2019-11-08 11:48:58","revisionof":"S2-1909135","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1764.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911539.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911540","title":"Support of the TSN Time Drift Threshold","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: During the PDU Session Modification procedure, the SMF may provide the UPF with the drift threshold between TSN time and 5G time as described in TS 23.501 [2] clause 5.27.2. When the time drift between TSN time and 5G time is larger than the drift threshold, the UPF shall provide the time offset to the SMF in the N4 Session Level Reporting Procedure.","secretary_remarks":"Revision of S2-1909136 from S2#135. Merged into S2-1912368","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18580,"status":"merged","reservation_date":"2019-11-08 09:16:25","uploaded":"2019-11-08 11:48:58","revisionof":"S2-1909136","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1761.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911540.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911541","title":"Support of the TSN Time Drift Threshold","source":"Tencent","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TSN AF provides time drift threshold of the TSN packet's arrival time (in reference to TSN GM) needed to update the time offset between TSN GM and 5G time as described in clauses 5.27.2 of TS 23.501 [2]. TSN AF QoS container includes the time drift threshold. Time drift threshold is sent to the SMF to indicate indicates the maximum time drift of the TSN packet's arrival time in reference to TSN GM; It is used by the SMF to request the UPF to provide the new time offset between TSN GM and 5G time as described in clauses 5.27.2 of TS 23.501 [2] to assist transmission of deterministic flows on Uu;","secretary_remarks":"Revision of S2-1909137 from S2#135. Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18590,"status":"noted","reservation_date":"2019-11-08 09:16:28","uploaded":"2019-11-08 11:48:58","revisionof":"S2-1909137","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":328.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911541.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911556","title":"Definition for TSC traffic forwarding rule","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Define the usage of TSC Traffic forwarding information. For UL TSC stream, the egress port number should be indicated in FAR for forwarding packets.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18630,"status":"noted","reservation_date":"2019-11-08 09:17:01","uploaded":"2019-11-08 16:32:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1963.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911556.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911557","title":"Procedures for PDU Session establishment and Bridge based information reporting","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Providing the 5GS Bridge ID and DS-TT port number to the DS-TT. 2. Desciding and reporting port pair information together with Bridge delay. 3. Selecting UPF and serving NW-TT port based on traffic class and VLAN information.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19150,"status":"available","reservation_date":"2019-11-08 09:17:02","uploaded":"2019-11-08 16:32:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1920.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911557.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911579","title":"Sync Indication Alt1 - UE","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A UE capability of TSN time synchronization is added.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18400,"status":"noted","reservation_date":"2019-11-08 10:13:16","uploaded":"2019-11-08 12:49:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1965.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911579.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911580","title":"Sync Indication Alt2 - PDU Session","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: PDU Session TSN Sync Indication is added to 5GSM CN Capability.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18410,"status":"noted","reservation_date":"2019-11-08 10:16:01","uploaded":"2019-11-08 12:49:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1966.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911580.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911604","title":"Sync Indication Alt1 - UE Procedure","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: A UE capability of TSN time synchronization is added to the registration procedure.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18540,"status":"available","reservation_date":"2019-11-08 10:30:18","uploaded":"2019-11-08 12:49:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1921.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911604.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911605","title":"Sync Indication Alt2 - PDU Session Procedure","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: PDU Session TSN Sync Indication is added to the PDU session establishment procedure.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18550,"status":"available","reservation_date":"2019-11-08 10:33:12","uploaded":"2019-11-08 12:49:06","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1922.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911605.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911674","title":"Revision on MDBV mapping","source":"Ericsson, NTT Docomo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that if a new 5QI matches the MDBV with the maximum burst size of the TSC QoS flows, then the 5QI PDB shall be in accordance to the bridge delay requirements of the corresponding traffic class. Define what is maximum busrt size which is calculated within a time interval of 5G-AN PDB. Remove text that impose requirements on the TSC flows. Modify text such that the MDBV is not set, but the maximum burst size for the TSC flows is mapped to a MDBV in a 5QI. A note added clarifying 5QI selection from QoS mapping table. REV4: Move the explanation of the TSC Burst Size from TSCAI section to 5.27.3 (Support for TSC QoS Flows). Correct the TSCAI Burst Size to TSC Burst Size. Change the wording 'TSC Burst Size is calculated \u2026' to TSC Burst Size is considered', as AF does not calculate the TSC Burst Size.","secretary_remarks":"Revision of S2-1910760 from S2#135. Revised in parallel session to S2-1912363.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18330,"status":"revised","reservation_date":"2019-11-08 11:51:28","uploaded":"2019-11-08 18:23:09","revisionof":"S2-1910760","revisedto":"S2-1912363","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1806.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911674.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911695","title":"Addressing open issues for Ethernet port management","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In line with the analysis and proposal in S2-190xxyy, remove both Editor's notes and update Annex F1 to reflect that AF can read and write port management information and can subscribe for notifications when port management information in DS-TT or NW-TT changes. Add the TSN time comparison reporting rule configuration from SMF to UPF, and the report from UPF to SMF.","secretary_remarks":"Revision of S2-1910626 from S2#135. Revised in parallel session to S2-1912369.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18550,"status":"revised","reservation_date":"2019-11-08 12:15:43","uploaded":"2019-11-08 13:48:41","revisionof":"S2-1910626","revisedto":"S2-1912369","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1729.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911695.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911698","title":"Clarification about periodicity of TSN streams in a traffic class .","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"Based on TS22.104 and IEEE 802.1Q specification, this paper clarifies the 5GS end-to-end delay, periodicity of TSN streams in a traffic class.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19010,"status":"available","reservation_date":"2019-11-08 12:31:56","uploaded":"2019-11-08 21:51:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911698.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911699","title":"Session binding for TSN.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"The paper propose a model where the TSN specific extra functionality is logically separated from the non-TSN specific functionality such as LLDP support.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19020,"status":"available","reservation_date":"2019-11-08 12:31:56","uploaded":"2019-11-08 21:51:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911699.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911700","title":"Session binding using DS-TT MAC and bridgeID","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For time sensitive communicaiton, MAC address and port number of a DS-TT port, and Bridge ID are used by PCF for session binding, UE MAC address is not needed at at TSN AF. SMF provides port numbers and MAC addresses associated with the NW-TT and DS-TT, and bridge ID to PCF as defined in TS 23. 501, clause 5.28.1. This is an implicit indication to PCF that the PDU session is for Time Sencitive Communication. PCF stores information about bridge ID, MAC addresses and port numbers of DS-TT ports and NW-TT ports. This information shall be provided to TSN AF first, prior to PCF can receive a request from the TSN AF. TSN AF address is configured at PCF based on DNN and NSSAI. PCF shall support transparently exchange of port management information container between TSN AF and DS-TT or NW-TT, as defined in TS 23.501 [2] clause 5.28.3. PCF shall support transparently transfer of TSCAI received from TSN AF to SMF and 5G-AN as defined in TS 23.501 [2] clause 5.27.2.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19130,"status":"available","reservation_date":"2019-11-08 12:31:56","uploaded":"2019-11-08 21:51:28","revisionof":"","revisedto":"S2-2000523","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":371.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911700.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911701","title":"Clarification for MDBV report and mapping.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"The paper clarifies the MDBV report and mapping.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19030,"status":"available","reservation_date":"2019-11-08 12:31:57","uploaded":"2019-11-08 21:51:28","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911701.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911702","title":"MDBV mapping and configuration for TSC QoS Flow","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case the Maximum Burst Size of the aggregated TSC streams in the traffic class is provided by CNC via TSN AF to PCF, PCF can derive the required MDBV taking the Maximum Burst Size and TSCAI as input. If the default MDBV associated with a 5QI in the QoS mapping table can't satisfy the aggregated TSC Burst Size, the PCF provides the derived MDBV in the PCC rule and then the SMF performs QoS Flow binding.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19040,"status":"available","reservation_date":"2019-11-08 12:31:57","uploaded":"2019-11-08 21:51:28","revisionof":"","revisedto":"S2-2000524","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":372.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911702.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911703","title":"MDBV mapping and configuration for TSC QoS Flow","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In case the Maximum Burst Size of the aggregated TSC streams in the traffic class is provided by CNC via TSN AF to PCF, PCF can derive the required MDBV taking the Maximum Burst Size and TSCAI as input. If the default MDBV associated with a 5QI in the QoS mapping table can't satisfy the aggregated TSC Burst Size, the PCF provides the derived MDBV in the PCC rule and then the SMF performs QoS Flow binding.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19050,"status":"available","reservation_date":"2019-11-08 12:31:59","uploaded":"2019-11-08 21:51:28","revisionof":"","revisedto":"S2-2000525","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1980.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911703.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911704","title":"TSCAI for aggregated TSN Streams.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"The TSCAI for an aggregated set of TSN Streams belonging to the same TSN traffic class can be calculated using Per-Stream Filtering and Policing (PSFP). In this contribution we show that it is possible to perform such calculations and that the TSCAI for this aggregated set of TSN Streams can be mapped into a single QoS flow.","secretary_remarks":"Revised to S2-1911929","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18760,"status":"revised","reservation_date":"2019-11-08 12:32:00","uploaded":"2019-11-08 21:59:11","revisionof":"","revisedto":"S2-1911929","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911704.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911705","title":"Applying Per-Stream Filtering and Policing","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the calculation of traffic pattern parameters based on specific PSFP parameters performed by the TSN AF. The SMF will use those parameters to determine the TSCAI. Note the assumption that there is a single PSFP filter linked to a single PSFP gate, and every PSFP filter specifies a unique Stream ID value. Add relevant PSFP parameters to the Port Management Information container, such that ingress ports (i.e., DS-TT and NW-TT ports) can emulate PSFP.","secretary_remarks":"Revised to S2-1911934.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18810,"status":"revised","reservation_date":"2019-11-08 12:32:00","uploaded":"2019-11-08 21:51:28","revisionof":"","revisedto":"S2-1911934","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1981.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911705.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911706","title":"Single NW-TT port","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to limit the scope of Release 16 to a single NW-TT port per UPF. This assumption is captured, and the text related to multiple NW-TTs per UPF is removed. The paragraph on Traffic Forwarding information is deleted since there is a single option for uplink forwarding. Also in this case there is no need for AF influence in the traffic routing.","secretary_remarks":"Confirm Specification Number! Confirm CR Number! Revised to S2-1911935.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18490,"status":"revised","reservation_date":"2019-11-08 12:32:01","uploaded":"2019-11-08 21:51:28","revisionof":"","revisedto":"S2-1911935","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1982.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911706.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911717","title":"Corrections to TSC QoS Mapping Table clause","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to clarify text in section 28.4 QoS mapping tables. The text is rewritten in chronological order. The roles of AF and PCF are clarified. The QoS mapping tables are renamed as AF QoS mapping table and PCF QoS mapping table.","secretary_remarks":"Revision of S2-1910623 from S2#135. Merged into S2-1912362.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18300,"status":"merged","reservation_date":"2019-11-08 13:06:36","uploaded":"2019-11-08 13:48:41","revisionof":"S2-1910623","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1888.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911717.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911727","title":"Clarification on the Qos mapping and session binding and reporting","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The session binding use the DS-TT MAC address. Rx interface is not used for TSC communication. DS-TT Residence time is reuqired for the AF.","secretary_remarks":"Confirm Specification Number!","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19060,"status":"available","reservation_date":"2019-11-08 13:42:53","uploaded":"2019-11-08 15:24:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":374.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911727.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911728","title":"Update the Annex F.2 5GS Bridge configuration","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Modify 5GS Bridge configuration procedure in the Annex F.2 to add the PSFP information.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19140,"status":"available","reservation_date":"2019-11-08 13:42:55","uploaded":"2019-11-08 15:24:13","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1937.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911728.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911750","title":"Complete hold and forward buffering mechanism","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The SMF provides the stream based 802.1Qci configuration on ingress port with modified the AdminBaseTime of the configuration to add the bridge delay to the DS-TT or NW-TT. The configuration is used to hold and forward buffering the traffic to guarantee the bridge delay.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19170,"status":"available","reservation_date":"2019-11-08 14:07:51","uploaded":"2019-11-08 16:32:10","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1988.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911750.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911775","title":"Clarification for TSC QoS Mapping clause","source":"Nokia, Nokia Shanghai Bell, Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to clarify text in section 5.28.4 QoS mapping tables.","secretary_remarks":"Revision of S2-1910623 from S2#135. Revised in parallel session, merging S2-1911717, to S2-1912362.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18310,"status":"revised","reservation_date":"2019-11-08 14:58:29","uploaded":"2019-11-08 21:51:28","revisionof":"S2-1910623","revisedto":"S2-1912362","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1888.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911775.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911877","title":"TSCAI granularity","source":"Nokia (?), Nokia Shanghai Bell (?), NTT DOCOMO (?), Tencent (?), Samsung (?), Huawei (?), Ericsson (?), ZTE (?), Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following are the main technical changes proposed: As per recommendation in the IEEE LS, assuming the ability to receive multiple sets of TSN AF QoS parameters which can be translated to one set of TSCAI parameters. Fix to MDBV description - We should avoid an incorrect interpretation that Period-1 is within Period-2, and hence only one burst of maximum size MDBV has to be sent within the AN-PDB. Thus, clarifying the text accordingly Other updates are mainly moving around text to fit the clause title and\/or clarifying descriptions further. Clarifies TSN streams mapping to QoS flow, TSCAI is only one per QoS Flow. Discussion about which entity in 5GC maps the TSCAI will be considered in SA WG2 future meeting. Changes in Rev4: Clarified that 5GS support for IEEE 802.1Q PSFP is optional.","secretary_remarks":"Revision of S2-1910758 from S2#135. Confirm Sources!. Noted","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18260,"status":"noted","reservation_date":"2019-11-08 17:35:01","uploaded":"2019-11-08 18:09:09","revisionof":"S2-1910758","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1890.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911877.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911886","title":"TSCAI granularity","source":"Nokia, Nokia Shanghai Bell, Tencent?, Samsung?, Huawei?, Ericsson?, ZTE?, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following are the main technical changes proposed: As per recommendation in the IEEE LS, assuming the ability to receive multiple sets of TSN AF QoS parameters which can be translated to one set of TSCAI parameters. Fix to MDBV description - We should avoid an incorrect interpretation that Period-1 is within Period-2, and hence only one burst of maximum size MDBV has to be sent within the AN-PDB. Thus, clarifying the text accordingly Other updates are mainly moving around text to fit the clause title and\/or clarifying descriptions further. Clarifies TSN streams mapping to QoS flow, TSCAI is only one per QoS Flow. Discussion about which entity in 5GC maps the TSCAI will be considered in SA WG2 future meeting. REV4: Describe the calculation of TSCAI per TSN working domain","secretary_remarks":"Revision of S2-1910758 from S2#135. Confirm Sources!. Revised in parallel session to S2-1912361.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18270,"status":"revised","reservation_date":"2019-11-08 18:19:04","uploaded":"2019-11-08 20:14:35","revisionof":"S2-1910758","revisedto":"S2-1912361","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1890.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911886.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911888","title":"Time Sync: gPTP Optimization","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed that the 2-step SYNC and SYNC Follow_Up are always combined at ingress (UPF\/NW-TT) to 1-step SYNC message to improve system efficiency. This will reduce also complexity when only one SYNC scenario is applied through 5GS. In this case the the latency would be similar to case where 1-step is applied at egress port and would meet","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":19110,"status":"available","reservation_date":"2019-11-08 18:31:39","uploaded":"2019-11-08 20:14:35","revisionof":"","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1998.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911888.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911909","title":"Discussion on time conversion between TSN clock and 5GS clock.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution analyse appending issue on the time conversion between TSN clock and 5GS clock and give the proposal.","secretary_remarks":"","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18840,"status":"available","reservation_date":"2019-11-08 20:23:21","uploaded":"2019-11-08 22:02:30","revisionof":"","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911909.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911910","title":"Clarificatin on the time conversion between 5GS clock and TSN clock.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TSN AF perform the time convertion between TSN clock and 5GS clock.","secretary_remarks":"Revised in parallel session to S2-1912415.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18730,"status":"revised","reservation_date":"2019-11-08 20:23:21","uploaded":"2019-11-08 22:02:30","revisionof":"","revisedto":"S2-1912415","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2000.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911910.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911929","title":"TSCAI for aggregated TSN Streams.","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"discussion","for":"Decision","abstract":"The TSCAI for an aggregated set of TSN Streams belonging to the same TSN traffic class can be calculated using Per-Stream Filtering and Policing (PSFP). In this contribution we show that it is possible to perform such calculations and that the TSCAI for this aggregated set of TSN Streams can be mapped into a single QoS flow.","secretary_remarks":"Revision of S2-1911704. Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18770,"status":"noted","reservation_date":"2019-11-08 22:31:29","uploaded":"2019-11-08 22:33:48","revisionof":"S2-1911704","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911929.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911934","title":"Applying Per-Stream Filtering and Policing","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the calculation of traffic pattern parameters based on specific PSFP parameters performed by the TSN AF. The SMF will use those parameters to determine the TSCAI. Note the assumption that there is a single PSFP filter linked to a single PSFP gate, and every PSFP filter specifies a unique Stream ID value. Add relevant PSFP parameters to the Port Management Information container, such that ingress ports (i.e., DS-TT and NW-TT ports) can emulate PSFP.","secretary_remarks":"Revision of S2-1911705. LATE DOC: Rx 12\/11, 15:00. Revised to S2-1912390.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18820,"status":"revised","reservation_date":"2019-11-12 14:54:48","uploaded":"2019-11-12 14:55:51","revisionof":"S2-1911705","revisedto":"S2-1912390","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1981.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911934.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911935","title":"Single NW-TT port","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to limit the scope of Release 16 to a single NW-TT port per UPF. This assumption is captured, and the text related to multiple NW-TTs per UPF is removed. The paragraph on Traffic Forwarding information is deleted since there is a single option for uplink forwarding. Also in this case there is no need for AF influence in the traffic routing.","secretary_remarks":"Revision of S2-1911706. LATE DOC: Rx 12\/11, 15:00. Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18500,"status":"noted","reservation_date":"2019-11-12 14:54:56","uploaded":"2019-11-12 14:55:51","revisionof":"S2-1911706","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1982.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911935.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1911948","title":"LS from CT WG1: LS on gPTP message delivery to DS-TT","source":"CT WG1","contact":"Sung Hwan Won","contact-id":70307,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 started protocol design for gPTP message delivery towards the DS-TT and a question was raised. Question: If there exist multiple PDU sessions for TSC between a UE and a UPF, is the UE expected to distribute a gPTP message received over a PDU session to: 1) a single DS-TT associated with the PDU session; or 2) a single DS-TT associated with the PDU session and DS-TT(s) associated with other PDU sessions?. Action: CT WG1 kindly asks SA WG2 to provide an answer to the question above.","secretary_remarks":"This LS was postponed.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18950,"status":"postponed","reservation_date":"2019-11-16 06:41:54","uploaded":"2019-11-16 06:42:42","revisionof":"","revisedto":"S2-2000018","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-198748","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1911948.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912360","title":"5GS Bridge Management","source":"Qualcomm Incorporated, Samsung , Nokia, Nokia Shanghai Bell, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that LLDP is only supported in NW-TT (i.e. NW-TT also performs LLDP. In line with the analysis and proposal in S2-190xxyy, remove following Editor's notes\u00a0: - Clause 4.4.8.2: Editor's note: Whether both DS-TT and NW-TT or only NW-TT support Link layer connectivity discovery and reporting is FFS. - Clause 5.28.3.1: Editor's note: Whether TSN AF can write DS-TT and NW-TT port neighbour discovery configuration is FFS. Editor's note: Whether TSN AF needs to be able to read port management information and needs to be able to get port management capabilities is FFS. [\u2026] Clean up table 5.28.3.1-1 (remove duplicated row, add missing NOTEs in table). Revision to SA WG2#136: It is proposed to agree to following changes: The terms Bridge Address and relation to Bridge ID as well as Port Addresses and relation to Port numbers and Port MAC addresses build the basic bridge information as defined in IEEE 802.1Q-2018, clause 12.4.1 '(a) Bridge Address\u2014the MAC address for the Bridge from which the Bridge Identifiers used by STP, RSTP, and MSTP are derived (8.13.8, 13.26). (b) Bridge Name\u2014a text string of up to 32 characters, of locally determined significance. (c) Number of Ports\u2014the number of Bridge Ports (MAC Entities). (d) Port Addresses\u2014a list specifying the following for each Port: (a1) Port Number\u2014the number of the Bridge Port (13.27). (a2) Port Address\u2014the specific MAC address of the individual MAC Entity associated with the Port (8.13.2)' and clause 8.13.8 'A unique EUI-48 Universally Administered MAC address, termed the Bridge Address, shall be assigned to each Bridge. The Bridge Address may be the individual MAC address of a Bridge Port; in which case, use of the address of the lowest numbered Bridge Port (Port 1) is recommended'. Adding relevant information for LLDP support as defined in IEEE 802.1AB-2016 clause 8.5.2 'There are several ways in which a chassis may be identified and a chassis ID subtype is used to indicate the type of component being referenced by the chassis ID field.', clause 8.5.3 'A port ID subtype is used to indicate how the port is being referenced in the port ID field.', clause 8.5.4 'The Time To Live TLV indicates the number of seconds that the recipient LLDP agent is to regard the information associated with this MSAP identifier to be valid. (a) When the TTL field is non-zero the receiving LLDP agent is notified to completely replace all information associated with this MSAP identifier with the information in the received LLDPDU. (b) When the TTL field is set to zero, the receiving LLDP agent is notified to delete all system information associated with the LLDP agent\/port. This TLV may be used, for example, to signal that the sending port has initiated a port shutdown procedure. The Time To Live TLV is mandatory and shall be the third TLV in the LLDPDU.', clause 9.2.5.1 'adminStatus This variable indicates whether or not the LLDP agent is enabled. The defined values for this variable are as follows: (a) enabledRxTx: The LLDP agent is enabled for reception and transmission of LLDPDUs. This is the recommended default value. (b) enabledTxOnly: The LLDP agent is enabled for transmission of LLDPDUs only. (c) enabledRxOnly: The LLDP agent is enabled for reception of LLDPDUs only. (d) disabled: The LLDP agent is disabled for both reception and transmission.' And Table 11-2 (Management Attributes). The relevant information consists of the Chassis ID subtype (defined in IEEE spec), Chassis ID (it could be a MAC address, string or a name), Port ID subtype (defined in IEEE spec), Port ID (it could be a MAC address, string or a name), TTL and the Admin Status definition, which is required for the LLDP handling at the TSN AF and to perform the LLDP Frame validation and generation at the TSN translators DS-TT and NW-TT. (Note: Admin Status is defined for a LLDP Agent and is valid for all ports that belongs to the LLDP Agent). This information is necessary only if the bridge advertises towards th","secretary_remarks":"Revision of S2-1910959. Revised in parallel session to S2-1912596.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18230,"status":"revised","reservation_date":"2019-11-19 22:36:51","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1910959","revisedto":"S2-1912596","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1747.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912360.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912361","title":"TSCAI granularity","source":"Nokia, Nokia Shanghai Bell, Tencent?, Samsung?, Huawei?, Ericsson, ZTE?, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following are the main technical changes proposed: As per recommendation in the IEEE LS, assuming the ability to receive multiple sets of TSN AF QoS parameters which can be translated to one set of TSCAI parameters. Other updates are mainly moving around text to fit the clause title and\/or clarifying descriptions further. Clarifies TSN streams mapping to QoS flow, TSCAI is only one per QoS Flow. Discussion about which entity in 5GC maps the TSCAI will be considered in SA WG2 future meeting. REV4: Describe the calculation of TSCAI per TSN working domain Which entity in 5GC converts from TSN GM to 5G GM is FFS.","secretary_remarks":"Revision of S2-1911886. Revised in parallel session to S2-1912597.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18280,"status":"revised","reservation_date":"2019-11-19 22:36:52","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911886","revisedto":"S2-1912597","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1890.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912361.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912362","title":"Clarification for TSC QoS Mapping clause","source":"Nokia, Nokia Shanghai Bell, Ericsson, NTT DOCOMO","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR proposes to clarify text in section 5.28.4 QoS mapping tables.","secretary_remarks":"Revision of S2-1911775, merging S2-1911717. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18430,"status":"agreed","reservation_date":"2019-11-19 22:36:53","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911775","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1888.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912362.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912363","title":"Revision on MDBV mapping","source":"Ericsson, NTT Docomo","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Specify that if a new 5QI matches the MDBV with the maximum burst size of the TSC QoS flows, then the 5QI PDB shall be in accordance to the bridge delay requirements of the corresponding traffic class. Define what is maximum busrt size which is calculated within a time interval of 5G-AN PDB. Remove text that impose requirements on the TSC flows. Modify text such that the MDBV is not set, but the maximum burst size for the TSC flows is mapped to a MDBV in a 5QI. A note added clarifying 5QI selection from QoS mapping table. REV4: Move the explanation of the TSC Burst Size from TSCAI section to 5.27.3 (Support for TSC QoS Flows). Correct the TSCAI Burst Size to TSC Burst Size. Change the wording 'TSC Burst Size is calculated \u2026' to TSC Burst Size is considered', as AF does not calculate the TSC Burst Size. REV5: Removal of the sentence 'If AF can't provide TSC Burst \u2026'.","secretary_remarks":"Revision of S2-1911674. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18450,"status":"agreed","reservation_date":"2019-11-19 22:36:54","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911674","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1806.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912363.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912364","title":"[DRAFT] Reply LS on reference time delivery","source":"Qualcomm Incorporated","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Revision of S2-1911362. For e-mail approval","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18380,"status":"revised","reservation_date":"2019-11-19 22:36:56","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911362","revisedto":"S2-1912769","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912364.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912365","title":"TSC PDU Session Restrictions","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR precludes Home Routed Roaming for TSC PDU Sessions, EPS interworking with service continuity","secretary_remarks":"Revision of S2-1910962. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18570,"status":"agreed","reservation_date":"2019-11-19 22:36:56","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1910962","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1889.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912365.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912366","title":"UPF functional update for TSC","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR adds agreed upon UPF TSC functionalities to section 6.2.3","secretary_remarks":"Revision of S2-1910964. Revised in parallel session to S2-1912727.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18470,"status":"revised","reservation_date":"2019-11-19 22:36:57","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1910964","revisedto":"S2-1912727","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1893.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912366.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912367","title":"UPF reporting the time comparison","source":"NTT DOCOMO, Nokia, Nokia Shanghai Bell","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Introduces Session Reporting Rule that can be used to instruct the UPF to measure and report TSC time offset and cumulative rateRatio","secretary_remarks":"Revision of S2-1910925. WITHDRAWN","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18520,"status":"withdrawn","reservation_date":"2019-11-19 22:36:58","uploaded":null,"revisionof":"S2-1910925","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1898.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912368","title":"UPF reporting the time comparison","source":"NTT DOCOMO, Nokia, Nokia Shanghai Bell, Tencent","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) The SMF may adjust the TSCAI based on the measured time offset reported by UPF. This procedure needs to be introduced to Annex F. 2) In the case the UPF reports the change of the cumulative rateRatio between TSN time and 5G time to SMF, the SMF updates the TSCAI to RAN. 3) In Npcf_PolicyAuthorization_Create\/Update definitions, the correct reference to TSN AF parameters is 6.1.3.23 in TS 23.503. 4) Add the 5GS bridge information as an input parameter to the Npcf_SMPolicyControl_Update service operation. This construct contains all TSN related parameters that the SMF needs to be able to report to the PCF.","secretary_remarks":"Revision of S2-1910926, merging S2-1911540. This was postponed.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18540,"status":"postponed","reservation_date":"2019-11-19 22:36:59","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1910926","revisedto":"S2-2000875","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1673.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912368.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912369","title":"Addressing open issues for Ethernet port management","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In line with the analysis and proposal in S2-190xxyy, remove both Editor's notes and update Annex F1 to reflect that AF can read and write port management information and can subscribe for notifications when port management information in DS-TT or NW-TT changes. Add the TSN clock drift report provisioning from SMF to UPF, and the report from UPF to SMF.","secretary_remarks":"Revision of S2-1911695. Postponed.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18560,"status":"postponed","reservation_date":"2019-11-19 22:37:00","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911695","revisedto":"","release":"Rel-16","crspec":"23.502","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1729.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912369.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912370","title":"N4 Impacts - Bridge Management","source":"Nokia, Nokia Shanghai Bell, ETRI","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update N4 section to include the ability for UPF to report Mac Address, NW-TT\/DS-TT Port Number towards SMF. Also include exchange of Port management container transparently.","secretary_remarks":"Revision of S2-1910961, merging S2-1911449. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18730,"status":"agreed","reservation_date":"2019-11-19 22:37:01","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1910961","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1887.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912370.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912390","title":"Applying Per-Stream Filtering and Policing","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the calculation of traffic pattern parameters based on specific PSFP parameters performed by the TSN AF. The SMF will use those parameters to determine the TSCAI. Note the assumption that there is a single PSFP filter linked to a single PSFP gate, and every PSFP filter specifies a unique Stream ID value. Add relevant PSFP parameters to the Port Management Information container, such that ingress ports (i.e., DS-TT and NW-TT ports) can emulate PSFP. Rev 2: Clarification that an optimal selection of the TSN Streams to be aggregated is left for implementation, however, Streams should share same traffic class, same periodicity, and terminate in the same egress port.","secretary_remarks":"Revision of S2-1911934. Revised in parallel session to S2-1912413.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18830,"status":"revised","reservation_date":"2019-11-19 22:40:59","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911934","revisedto":"S2-1912413","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1981.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912390.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912411","title":"Vertical-LAN TSN Drafting Session report","source":"Nokia","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"other","for":"Information","abstract":"Vertical-LAN TSN Drafting Session report","secretary_remarks":"Created at meeting. Agreed in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18210,"status":"approved","reservation_date":"2019-11-20 19:44:17","uploaded":"2019-11-25 16:07:54","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912411.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912412","title":"QoS mapping for uplink TSC communication","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - For downlink TSC communication, deciding the TSN QoS parameters based on the bridge delay and the TSN information for egress port (e.g.802.1Qbv informantion). - For uplink TSC communication, deciding the TSN QoS parameters based on the bridge delay, the PSFP information for ingress port and the TSN information for egress port (e.g.802.1Qbv informantion). - Corrections for alignment with 23.501.","secretary_remarks":"Revision of S2-1911129. Revised in parallel session to S2-1912594.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18790,"status":"revised","reservation_date":"2019-11-20 19:44:17","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911129","revisedto":"S2-1912594","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":325.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912412.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912413","title":"Applying Per-Stream Filtering and Policing","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the calculation of traffic pattern parameters based on specific PSFP parameters performed by the TSN AF. The SMF will use those parameters to determine the TSCAI. Note the assumption that there is a single PSFP filter linked to a single PSFP gate, and every PSFP filter specifies a unique Stream ID value. Add relevant PSFP parameters to the Port Management Information container, such that ingress ports (i.e., DS-TT and NW-TT ports) can emulate PSFP. Rev 2: Clarification that an optimal selection of the TSN Streams to be aggregated is left for implementation, however, Streams should share same traffic class, same periodicity, and terminate in the same egress port.","secretary_remarks":"Revision of S2-1912390. Revised in parallel session to S2-1912595.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18840,"status":"revised","reservation_date":"2019-11-20 19:44:19","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912390","revisedto":"S2-1912595","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1981.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912413.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912414","title":"Correction on the bridge mangement and port management","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Add per traffic class AdminIdleSlope to the port. - Add Static Filtering Entry in the port management container and is transfer to NW-TT.","secretary_remarks":"Revision of S2-1911125. Revised in parallel session to S2-1912593.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18650,"status":"revised","reservation_date":"2019-11-20 19:44:20","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911125","revisedto":"S2-1912593","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1749.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912414.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912415","title":"Clarificatin on the time conversion between 5GS clock and TSN clock.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: TSN AF perform the time convertion between TSN clock and 5GS clock.","secretary_remarks":"Revision of S2-1911910. Time conversion in the TSN AF: Yes: 4 Time conversion in the SMF: Yes: 4 Noted in parallel session","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18740,"status":"noted","reservation_date":"2019-11-20 19:44:21","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1911910","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":2000.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912415.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912593","title":"Correction on the bridge mangement and port management","source":"Vivo, ZTE, Ericsson, Huawei, HiSilicon","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Remove the association between the PDU session and NW-TT port. - Add Static Filtering Entry in the port management container and is transfer to NW-TT.","secretary_remarks":"Revision of S2-1912414. Revised in parallel session to S2-1912728.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18660,"status":"revised","reservation_date":"2019-11-25 15:21:11","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912414","revisedto":"S2-1912728","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1749.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912593.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912594","title":"QoS mapping for uplink TSC communication","source":"Vivo","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - The TSN AF decides the TSN QoS information (i.e. priority and maximum delay) based on the received the configuration information of 5GS Bridge from the CNC as defined in 5.28.2 of TS 23.501 [2] and the bridge delay information at the TSN AF. - Corrections for alignment with 23.501.","secretary_remarks":"Revision of S2-1912412. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18920,"status":"agreed","reservation_date":"2019-11-25 15:21:12","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912412","revisedto":"","release":"Rel-16","crspec":"23.503","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":325.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912594.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912595","title":"Applying Per-Stream Filtering and Policing","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the calculation of traffic pattern parameters based on specific PSFP parameters performed by the TSN AF. The SMF will use those parameters to determine the TSCAI. Note the assumption that there is a single PSFP filter linked to a single PSFP gate, and every PSFP filter specifies a unique Stream ID value. Add relevant PSFP parameters to the Port Management Information container, such that ingress ports (i.e., DS-TT and NW-TT ports) can emulate PSFP. Rev 2: Clarification that an optimal selection of the TSN Streams to be aggregated is left for implementation, however, Streams should share same traffic class, same periodicity, and terminate in the same egress port.","secretary_remarks":"Revision of S2-1912413. Revised in parallel session to S2-1912729.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18850,"status":"revised","reservation_date":"2019-11-25 15:21:14","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912413","revisedto":"S2-1912729","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1981.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912595.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912596","title":"5GS Bridge Management","source":"Qualcomm Incorporated, Samsung , Nokia, Nokia Shanghai Bell, Ericsson, ZTE","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that LLDP is only supported in NW-TT (i.e. NW-TT also performs LLDP. In line with the analysis and proposal in S2-190xxyy, remove following Editor's notes\u00a0: - Clause 4.4.8.2: Editor's note: Whether both DS-TT and NW-TT or only NW-TT support Link layer connectivity discovery and reporting is FFS. - Clause 5.28.3.1: Editor's note: Whether TSN AF can write DS-TT and NW-TT port neighbour discovery configuration is FFS. Editor's note: Whether TSN AF needs to be able to read port management information and needs to be able to get port management capabilities is FFS. [\u2026] Clean up table 5.28.3.1-1 (remove duplicated row, add missing NOTEs in table). Revision to SA WG2#136: It is proposed to agree to following changes: The terms Bridge Address and relation to Bridge ID as well as Port Addresses and relation to Port numbers and Port MAC addresses build the basic bridge information as defined in IEEE 802.1Q-2018, clause 12.4.1 '(a) Bridge Address\u2014the MAC address for the Bridge from which the Bridge Identifiers used by STP, RSTP, and MSTP are derived (8.13.8, 13.26). (b) Bridge Name\u2014a text string of up to 32 characters, of locally determined significance. (c) Number of Ports\u2014the number of Bridge Ports (MAC Entities). (d) Port Addresses\u2014a list specifying the following for each Port: (a1) Port Number\u2014the number of the Bridge Port (13.27). (a2) Port Address\u2014the specific MAC address of the individual MAC Entity associated with the Port (8.13.2)' and clause 8.13.8 'A unique EUI-48 Universally Administered MAC address, termed the Bridge Address, shall be assigned to each Bridge. The Bridge Address may be the individual MAC address of a Bridge Port; in which case, use of the address of the lowest numbered Bridge Port (Port 1) is recommended'. Adding relevant information for LLDP support as defined in IEEE 802.1AB-2016 clause 8.5.2 'There are several ways in which a chassis may be identified and a chassis ID subtype is used to indicate the type of component being referenced by the chassis ID field.', clause 8.5.3 'A port ID subtype is used to indicate how the port is being referenced in the port ID field.', clause 8.5.4 'The Time To Live TLV indicates the number of seconds that the recipient LLDP agent is to regard the information associated with this MSAP identifier to be valid. (a) When the TTL field is non-zero the receiving LLDP agent is notified to completely replace all information associated with this MSAP identifier with the information in the received LLDPDU. (b) When the TTL field is set to zero, the receiving LLDP agent is notified to delete all system information associated with the LLDP agent\/port. This TLV may be used, for example, to signal that the sending port has initiated a port shutdown procedure. The Time To Live TLV is mandatory and shall be the third TLV in the LLDPDU.', clause 9.2.5.1 'adminStatus This variable indicates whether or not the LLDP agent is enabled. The defined values for this variable are as follows: (a) enabledRxTx: The LLDP agent is enabled for reception and transmission of LLDPDUs. This is the recommended default value. (b) enabledTxOnly: The LLDP agent is enabled for transmission of LLDPDUs only. (c) enabledRxOnly: The LLDP agent is enabled for reception of LLDPDUs only. (d) disabled: The LLDP agent is disabled for both reception and transmission.' And Table 11-2 (Management Attributes). The relevant information consists of the Chassis ID subtype (defined in IEEE spec), Chassis ID (it could be a MAC address, string or a name), Port ID subtype (defined in IEEE spec), Port ID (it could be a MAC address, string or a name), TTL and the Admin Status definition, which is required for the LLDP handling at the TSN AF and to perform the LLDP Frame validation and generation at the TSN translators DS-TT and NW-TT. (Note: Admin Status is defined for a LLDP Agent and is valid for all ports that belongs to the LLDP Agent). This information is necessary only if the bridge advertises towards th","secretary_remarks":"Revision of S2-1912360. Revised in parallel session to S2-1912726.","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18240,"status":"revised","reservation_date":"2019-11-25 15:21:15","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912360","revisedto":"S2-1912726","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1747.0,"crrevision":6.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912596.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912597","title":"TSCAI granularity","source":"Nokia, Nokia Shanghai Bell, Tencent, Samsung, Ericsson, ZTE, NTT DOCOMO, Huawei, HiSilicon","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Following are the main technical changes proposed: As per recommendation in the IEEE LS, assuming the ability to receive multiple sets of TSN AF QoS parameters which can be translated to one set of TSCAI parameters. Other updates are mainly moving around text to fit the clause title and\/or clarifying descriptions further. Clarifies TSN streams mapping to QoS flow, TSCAI is only one per QoS Flow.","secretary_remarks":"Revision of S2-1912361. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18400,"status":"agreed","reservation_date":"2019-11-25 15:21:16","uploaded":"2019-11-25 16:07:54","revisionof":"S2-1912361","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1890.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912597.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912726","title":"5GS Bridge Management","source":"Qualcomm Incorporated, Samsung , Nokia, Nokia Shanghai Bell, Ericsson, ZTE","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that LLDP is only supported in NW-TT (i.e. NW-TT also performs LLDP. In line with the analysis and proposal in S2-190xxyy, remove following Editor's notes\u00a0: - Clause 4.4.8.2: Editor's note: Whether both DS-TT and NW-TT or only NW-TT support Link layer connectivity discovery and reporting is FFS. - Clause 5.28.3.1: Editor's note: Whether TSN AF can write DS-TT and NW-TT port neighbour discovery configuration is FFS. Editor's note: Whether TSN AF needs to be able to read port management information and needs to be able to get port management capabilities is FFS. [\u2026] Clean up table 5.28.3.1-1 (remove duplicated row, add missing NOTEs in table). Revision to SA WG2#136: Following aspects are proposed: The terms Bridge Address and relation to Bridge ID as well as Port Addresses and relation to Port numbers and Port MAC addresses build the basic bridge information as defined in IEEE 802.1Q-2018, clause 12.4.1 '(a) Bridge Address\u2014the MAC address for the Bridge from which the Bridge Identifiers used by STP, RSTP, and MSTP are derived (8.13.8, 13.26). (b) Bridge Name\u2014a text string of up to 32 characters, of locally determined significance. (c) Number of Ports\u2014the number of Bridge Ports (MAC Entities). (d) Port Addresses\u2014a list specifying the following for each Port: (a1) Port Number\u2014the number of the Bridge Port (13.27). (a2) Port Address\u2014the specific MAC address of the individual MAC Entity associated with the Port (8.13.2)' and clause 8.13.8 'A unique EUI-48 Universally Administered MAC address, termed the Bridge Address, shall be assigned to each Bridge. The Bridge Address may be the individual MAC address of a Bridge Port; in which case, use of the address of the lowest numbered Bridge Port (Port 1) is recommended'. Adding relevant information for LLDP support as defined in IEEE 802.1AB-2016 clause 8.5.2 'There are several ways in which a chassis may be identified and a chassis ID subtype is used to indicate the type of component being referenced by the chassis ID field.', clause 8.5.3 'A port ID subtype is used to indicate how the port is being referenced in the port ID field.', clause 8.5.4 'The Time To Live TLV indicates the number of seconds that the recipient LLDP agent is to regard the information associated with this MSAP identifier to be valid. (a) When the TTL field is non-zero the receiving LLDP agent is notified to completely replace all information associated with this MSAP identifier with the information in the received LLDPDU. (b) When the TTL field is set to zero, the receiving LLDP agent is notified to delete all system information associated with the LLDP agent\/port. This TLV may be used, for example, to signal that the sending port has initiated a port shutdown procedure. The Time To Live TLV is mandatory and shall be the third TLV in the LLDPDU.', clause 9.2.5.1 'adminStatus This variable indicates whether or not the LLDP agent is enabled. The defined values for this variable are as follows: (a) enabledRxTx: The LLDP agent is enabled for reception and transmission of LLDPDUs. This is the recommended default value. (b) enabledTxOnly: The LLDP agent is enabled for transmission of LLDPDUs only. (c) enabledRxOnly: The LLDP agent is enabled for reception of LLDPDUs only. (d) disabled: The LLDP agent is disabled for both reception and transmission.' And Table 11-2 (Management Attributes). The relevant information consists of the Chassis ID subtype (defined in IEEE spec), Chassis ID (it could be a MAC address, string or a name), Port ID subtype (defined in IEEE spec), Port ID (it could be a MAC address, string or a name), TTL and the Admin Status definition, which is required for the LLDP handling at the TSN AF and to perform the LLDP Frame validation and generation at the TSN translators DS-TT and NW-TT. (Note: Admin Status is defined for a LLDP Agent and is valid for all ports that belongs to the LLDP Agent). This information is necessary only if the bridge advertises towards the neighbors. (","secretary_remarks":"Revision of S2-1912596. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18360,"status":"agreed","reservation_date":"2019-11-25 15:22:31","uploaded":"2019-11-25 16:07:57","revisionof":"S2-1912596","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1747.0,"crrevision":7.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912726.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912727","title":"UPF functional update for TSC","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: This CR adds agreed upon UPF TSC functionalities to section 6.2.3","secretary_remarks":"Revision of S2-1912366. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18600,"status":"agreed","reservation_date":"2019-11-25 15:22:32","uploaded":"2019-11-25 16:07:57","revisionof":"S2-1912366","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1893.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912727.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912728","title":"Correction on the bridge mangement and port management","source":"Vivo, ZTE, Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell, Samsung","contact":"xiaowan ke","contact-id":74585,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Remove the association between the PDU session and NW-TT port. - Add Static Filtering Entry in the port management container and is transfer to NW-TT.","secretary_remarks":"Revision of S2-1912593. For e-mail approval","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18670,"status":"available","reservation_date":"2019-11-25 15:22:34","uploaded":"2019-11-25 16:07:57","revisionof":"S2-1912593","revisedto":"S2-2000130","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1749.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912728.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912729","title":"Applying Per-Stream Filtering and Policing","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the calculation of traffic pattern parameters based on specific PSFP parameters performed by the TSN AF. The SMF will use those parameters to determine the TSCAI. Note the assumption that there is a single PSFP filter linked to a single PSFP gate, and every PSFP filter specifies a unique Stream ID value. Add relevant PSFP parameters to the Port Management Information container, such that ingress ports (i.e., DS-TT and NW-TT ports) can emulate PSFP. Rev 2: Clarification that an optimal selection of the TSN Streams to be aggregated is left for implementation, however, Streams should share same traffic class, same periodicity, and terminate in the same egress port.","secretary_remarks":"Revision of S2-1912595. Agreed in parallel session. Block approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18980,"status":"agreed","reservation_date":"2019-11-25 15:22:35","uploaded":"2019-11-25 16:07:57","revisionof":"S2-1912595","revisedto":"","release":"Rel-16","crspec":"23.501","crspecversion":"16.2.0","workitem":[{"winame":"Vertical_LAN"}],"crnumber":1981.0,"crrevision":5.0,"crcategory":"F","tsg_crp":"SP-191092","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912729.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-1912769","title":"Reply LS on reference time delivery","source":"SA WG2","contact":"Sebastian Speicher","contact-id":72922,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"e-mail revision 2 of S2-1912364. Approved","agenda_item_sort_order":33,"ainumber":"7.7.2","ainame":"5GS Enhanced support of Vertical and LAN Services - TSN aspects","tdoc_agenda_sort_order":18500,"status":"available","reservation_date":"2019-11-28 05:47:22","uploaded":"2019-11-28 08:00:20","revisionof":"S2-1912364","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":[{"winame":"Vertical_LAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-1910892","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_136_Reno\/Docs\/S2-1912769.zip","group":"S2","meeting":"S2-136","year":2019,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]