[{"name":"S2-2108276","title":"Reply LS on more efficient PMIC\/UMIC signalling exchange for time synchronization","source":"CT WG1","contact":"Thomas Luetzenkirchen","contact-id":37722,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks SA WG2 for their LS on more efficient PMIC\/UMIC signalling exchange for time synchronization. Specific to the SA WG2 questions in C1-215544\/S2-2106767 CT WG1 would like to provide the following feedback: Q1: SA WG2 would like to ask CT WG1 to consider whether such a solution is possible and provide feedback. Answer: CT WG1 has agreed in the attached CR to TS 24.539 (see C1-216245) on enhancements to Port management and User plane node management operations for supporting read parameter, and subscribe-notify parameter using only a subset of parameter value. Q2: Specific to the Write operation, when TSN AF (or TSCTSF) is sending UMIC or PMIC to a TT containing only partial PTP instance information, SA WG2 could not clearly understand the consequences from such operation. Can CT WG1 inform SA WG2 what happens in terms of the status of the PTP information available in the TT that is not included in the UMIC or PMIC? Answer: CT WG1 understanding is that the PTP instance list port parameter and DS-TT port time synchronization information list user plane node parameter already supports setting of individual PTP instance parameters without changing PTP instance parameters stored at the TT previous to the operation and not included in the UMIC or PMIC. Action: CT WG1 asks SA WG2 to take the above feedback into account.","secretary_remarks":"Postponed","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14860,"status":"postponed","reservation_date":"2021-10-29 06:41:19","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"S2-2200011","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-216069","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108276.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108288","title":"LS from CT WG4: Reply LS on UPF reporting for redundant transmission on transport layer","source":"CT WG4","contact":"Caixia Qi","contact-id":56676,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 would like to thank SA WG5 for their LS on UPF reporting for redundant transmission on transport layer. CT WG4 can provide the following feedback on the question raised by SA WG5: Can the SMF be aware on whether the usage reported by UPF is with or without redundant counts when redundant transmission at transport layer is used? Answer: Like for the case of redundant transmission on N3\/N9 interfaces specified in clause 5.2.2.3.3 of TS 29.244, the UPF does not count redundant packets in Usage Reports sent to the SMF when redundant transmission is used on transport layer. CT WG4 will clarify so in TS 29.244 at the next CT WG4 meeting.","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14870,"status":"noted","reservation_date":"2021-10-29 06:41:20","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5, SA WG2","Cc":"","lsoriginalls":"C4-215505","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108288.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108292","title":"LS from IEEE: RE: LS on Correction Field update for Transparent Clock","source":"IEEE","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"Methods to limit the error of Transparent Clock corrections, as specified in IEEE 1588-2019, include: 1. Use of an accurate and stable oscillator in the timestamping clock of the Transparent Clock, such that the worst-case residence time results in a sufficiently small error. 2. Syntonizing to the frequency of the Grandmaster clock. Note that it is not necessary to steer the timestamping clock oscillator to this frequency. Instead, an estimate of the current frequency offset can be maintained and used to correct residence time calculations. 3. The Cumulative Rate Ratio feature of PTP can be used. Note that this requires that all PTP nodes in the path from the Grandmaster support this feature. Method 3 requires the use of peer-delay. Methods 1 and 2 will work for either peer-delay or end-to-end networks. There might be other methods not listed. The use case of a network acting as a distributed Transparent Clock has not been studied in detail by the IEEE 1588 working group. If additional mechanisms are needed for this use case, participants in 3GPP are welcome to bring technical contributions to the IEEE 1588 working group. We recommend a careful error analysis to make sure that the requirements of any use case can be met. We look forward to continued communication and coordination with 3GPP.","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14880,"status":"noted","reservation_date":"2021-10-29 06:41:20","uploaded":"2021-10-29 07:49:49","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP","Cc":"Chunshan Xiong","lsoriginalls":"Reply to 3GPP liaison correction field","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108292.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108308","title":"Deletion of selected enrties in UMIC\/PMIC data structures","source":"Intel, NTT DOCOMO","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the use of PMIC and UMIC for the deletion of selected entries in the UMIC\/PMIC data structures that are lists of variable size.","secretary_remarks":"r02 agreed. Revised to S2-2109278.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14890,"status":"revised","reservation_date":"2021-11-04 10:43:38","uploaded":"2021-11-08 19:27:12","revisionof":"","revisedto":"S2-2109278","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3357.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108308.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108309","title":"Clarification on Static Filtering Entries","source":"Intel, NTT DOCOMO, Ericsson","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) It is clarified that the SFE can indicate that an ingress frame matching the (MAC address, VID) pair can be forwarded to more than one egress port. 2) The references to 'uplink traffic' in Table 5.28.3.1-2 NOTE 3 are removed. The DS-TT egress port is added besides the existing NW-TT port.","secretary_remarks":"r05 agreed. Revised to S2-2109279.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14910,"status":"revised","reservation_date":"2021-11-04 10:48:55","uploaded":"2021-11-08 19:27:12","revisionof":"","revisedto":"S2-2109279","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"Vertical_LAN"},{"winame":" IIoT"}],"crnumber":3358.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108309.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108315","title":"Improved PTP instance configuration management","source":"Intel, NTT DOCOMO, Ericsson","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the creation of PTP instance in DS-TT or NW-TT is achieved by using the 'Set parameter' operation as described in TS 24.539. For deletion of PTP Instance the text also refers to TS 24.539. Rev2: Change the 'Upon detection of a DS-TT port' to 'To add a DS-TT port into a PTP instance in 5GS', for a condition to create a new PTP instance in DS-TT. Remove the cases 'PTP instance is not available in 5GS' and 'PTP instance is already available in 5GS'.","secretary_remarks":"Revision of (Agreed) S2-2108126 from S2#147E. r02 agreed. Revised to S2-2109280.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14930,"status":"revised","reservation_date":"2021-11-05 09:47:43","uploaded":"2021-11-08 19:27:12","revisionof":"S2-2108126","revisedto":"S2-2109280","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3242.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108315.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108426","title":"Updating the description of UE-DS-TT Residence Time delivery to the PCF","source":"Ericsson, [Nokia, Nokia Shanghai Bell, CATT]","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) The description of the procedures for set up\/update of AF session with required QoS is corrected to reflect that the AF request can use either Option 1 or Option\u00a02 (exclusive, not combinational). Option 1: The AF may provide (1) QoS reference, (2) (optional) Alternative Service Requirements that consist of one or more QoS reference parameters in a prioritized order, and they may be provided in addition to the QoS Reference, and (3) a subset of individual QoS parameters that constitute the TSC Assistance Container information, specifically, flow direction, Burst Size (optional), Burst Arrival Time (optional) at UE (uplink) or UPF (downlink), Periodicity (optional), Time domain (optional), Survival Time (optional). Option 2: Instead of QoS Reference and (optional) Alternative Service Requirements, the AF may provide the individual QoS parameters that can include Requested 5GS delay (optional), priority (optional), Requested GFBR, Requested MFBR, Burst Size (optional) and TSC Assistance Container information (specified when describing Option 1). 2) We clarify that Alternative Service Requirements can be provided only when the AF request a specific QoS via a QoS Reference (Option 1), i.e., Alternative Service Requirements can not be used when the AF request is done using the Individual QoS parameters (Option\u00a02). 3) We provide the reference to clause 6.1.3.22 of TS 23.503 to clearly specify which QoS reference parameters may be included in the Alternative Service Requirements as there were many interpretations\/discussions about that. The QoS reference parameters in the Alternative Service Requirements indicates the preference of the QoS requirement with which the service can operate (per 6.1.3.22 of TS 23.503), and these 'QoS Reference parameters' are subsequently used to establish Alternative QoS Profile(s) that is\/are represented a combination of PDB, PER and GFBR to which the application traffic is able to adapt (as described in clause 5.7.1.2a of TS 23.501). So, the QoS reference parameters lead to those Alternative QoS Profile's parameters. 4) The ENs on whether and how the PCF uses the priority values specfied by an AF other than a TSN-AF is resolved. The AF requested priority may be used by the PCF to set priority of a QoS Flow as specfied in 23.501 clause 5.7.1.2a.","secretary_remarks":"Revision of (revised and approved) S2-2107132 from S2#147E. Merged into S2-2109285","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14950,"status":"merged","reservation_date":"2021-11-07 13:36:10","uploaded":"2021-11-08 21:37:06","revisionof":"S2-2107132","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3131.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108426.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108427","title":"Parameter handling for an AF requesting a specific QoS","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1) In its request, the AF may provide either QoS Reference or Individual QoS parameters (i.e., exclusive options) 2) Alternative Service Requirements can be provided only when the AF request a specific QoS via a QoS Reference 3) Alternative Service Requirements contain one or more QoS Rreference parameters in a prioritized order indicating the preference of the QoS requirements with which the service can operate. (They do not include a subset of individual QoS parameters (in addition or separately) to QoS Reference parameters)","secretary_remarks":"Merged into S2-2109286","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14960,"status":"merged","reservation_date":"2021-11-07 13:36:14","uploaded":"2021-11-08 21:37:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":674.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108427.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108428","title":"Completing funtional description for TSC","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Add a new clause describing the support for TSC. - Address imprecisions in clause 6.1.3.22 regarding TSN AF and the general case of TSC. - Move a note in clause 6.1.3.23.","secretary_remarks":"Confirm Specification Number - CR states 23.503! Merged into S2-2109296","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14970,"status":"merged","reservation_date":"2021-11-07 13:36:15","uploaded":"2021-11-08 21:37:06","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3370.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108428.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108429","title":"Adding Trusted AF in Time Synchronization procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Add that a trusted AF may invoke services directly to the TSCTSF in Time Synchronization procedures. - Correct reference mistake to the Table about Time Synchronization capability event parameters.","secretary_remarks":"r01 agreed. Revised to S2-2109281.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14980,"status":"revised","reservation_date":"2021-11-07 13:36:16","uploaded":"2021-11-08 21:37:06","revisionof":"","revisedto":"S2-2109281","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3235.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108429.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108434","title":"Policy for Handling of PMIC exchange with UE(s) in idle mode","source":"Samsung[, Huawei, Ericsson]","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove TSCTSF from the clause 6.1.3.23 (undo changes), since it does not apply for TSN. Add new clause on support for TSC. Revise the text in clause 6.1.3.22 regarding use of TSN AF. The statement related to the TSC Assistance Container is corrected by referring to the new clause. - TSCTSF or TSN AF may indicate that the AMF is allowed to use ATC when it sends PMIC. Furthermore, a note is moved to its corresponding paragraph.","secretary_remarks":"Revision of (Agreed) S2-2108136 from S2#147E. Merged into S2-2109296","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15000,"status":"merged","reservation_date":"2021-11-08 00:31:56","uploaded":"2021-11-08 11:25:41","revisionof":"S2-2108136","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":660.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108434.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108475","title":"23.501: TSCTSF Discovery and Selection","source":"Nokia, Nokia Shangai Bell, Huawei, HiSilicon","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that a single TSCTSF instance is associated to a given DNN\/S-NSSAI. TSC TSF discovery section - to clarify that the GPSI, SUPI, Internal Group ID can also be used for discovery and selection. Add GPSI - in case the NF consumer uses GPSI for TSC TSF discovery and selection. Add SUPI or Internal Group ID - in case the NF consumer is only aware of the SUPI or Internal Group ID, it uses SUPI or Internal Group ID for TSC TSF discovery and selection. These parameters are in principle available already with NRF framework thus it should be straight forward to use them also for TSC TSF discovery selection.","secretary_remarks":"Revised to S2-2108961","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15010,"status":"revised","reservation_date":"2021-11-08 04:16:08","uploaded":"2021-11-08 18:47:20","revisionof":"","revisedto":"S2-2108961","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3375.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108475.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108476","title":"23.502: TSCTSF Discovery and Selection","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - (Option 2) Remove the UDR based TSCTSF instance discovery and selection for AF session with required QoS procedure and Time Synchronization service procedure - Updates for TSCTSF instance discovery for SMF initiated SM Policy Association Modification procdure, i.e., remove the repeated text and refer to clause 6.3.24 of TS 23.501 [2] - udpate the Npcf_Policy Authorization service, Nnef_AFsessionWithQoS and Ntsctsf_QoSandTSCAssistance","secretary_remarks":"r05 agreed. Revised to S2-2109283.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15040,"status":"revised","reservation_date":"2021-11-08 04:16:09","uploaded":"2021-11-08 18:47:20","revisionof":"","revisedto":"S2-2109283","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3246.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108476.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108477","title":"23.502: Time Sync exposure procedure","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updating the figure 4.15.9.2 to correct the service names with the ones in the procedure description and service operation (Nnef_TimeSynchronization_CapsSubscribe' vs 'Nnef_TimeSynchronizationCaps_Subscribe') Also, fix the use of UDR","secretary_remarks":"r05 agreed. Revised to S2-2109284.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15060,"status":"revised","reservation_date":"2021-11-08 04:16:10","uploaded":"2021-11-08 18:47:20","revisionof":"","revisedto":"S2-2109284","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3247.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108477.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108478","title":"Fixes for AF session with required QoS update procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1 - UDR storage of TSCTSF address for TSC QoS is eliminated. It is assumed that in TSCTSF discovery & selection (or local configuration) there is only one TSCTSF or TSCTSF set per UE\/S-NSSAI\/DNN. Hence the same TSCTSF (or set) is selected when the PCF sends 5GS Bridge Information (with UE residence time) to the TSCTSF and when an NEF sends an AF request for QoS. This significantly simplifies the QoS procedures and resolves the issue of always selecting a correct UDR (where a TSCTSF address is stored). 3 - A QoS Reference may or may not be specified with Individual QoS Parameters and Alternative QoS Related Parameters in the AF request. When a QoS Reference is provided, AF specified QoS Parameters or Alternative QoS Related Parameters over-ride the corresponding parameters associated with the QoS reference (which may be considered the default parameters). If no QoS reference is provided, then the AF must specify a complete set of Individual QoS Parameters \/ Alternative QoS Related Parameters to specify what it wants. 4 - In step 1 (AF request), a reference is corrected. The currently referenced clause 5.7.1.2a of TS23.501 refers to Alternative QoS Profies (provided by the SMF to the RAN) not Alternative QoS Related parameters provided by the AF to the PCF. Instead a reference is given to 23.503 clause 6.1.3.22. Clarifying text is added at the end of step 1 with the 23.501 reference. 5 - Step 3 should only be executed when individual parameters for Alt QoS (Alternative QoS Related parameter set(s)) are not specified. A condition is added to the beginning of step 3 and a reference is added to point to 23.503 clause 6.1.3.22 6 - In steps 3a and 3b, the Alternative QoS Related parameters (ie: the individual parameters specified by the AF for a Alternative QoS Reference) are also part of the Alternative Service Requirements sent to the TSCTSF (3a) and PCF (3b). Note that the Alternative QoS Related Parameters (which are sent from AF to the PCF) and specify individual QoS Parameters for Alt QoS references (as per 23.503 clause 6.1.3.22) are not the same as the Alternative QoS parameter set(s) in the PCC rules, which are unchanged from Rel. 16. 7 - In step 4 text refering to Alternative QoS Related parameter sets is removed and in step 4a, the PCF may use the Alternative QoS Related parameter sets (that are part of the Alternative Service Requirements and originated at the AF) to determine the Alternative QoS parameter set(s) in the PCC rules. Note there is no change to the contents of the PCC rules - they already contain Alternative QoS parameter Set(s). 8 - The ENs on whether and how the PCF uses priority values specfied by an AF other than a TSN-AF is resolved. The AF requested priority may be used by the PCF to set priority of a QoS Flow as specfied in 23.501 clause 5.7.1.2a. 9 - Requested Priority and Requested PER parameters are added to Nnef_AFsessionWithQoS and Ntsctsf_QoSandTSCAssistance service operations to be consistent with text in clause 4.15.6.6 and 4.15.6.6a","secretary_remarks":"r05 agreed. Revised to S2-2109285, merging S2-2108426 and S2-2108819","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15080,"status":"revised","reservation_date":"2021-11-08 04:16:11","uploaded":"2021-11-08 18:47:20","revisionof":"","revisedto":"S2-2109285","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3248.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108478.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108479","title":"Fixes for AF session with required QoS update procedure","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 23.503 clause 6.1.3.22 is updated for consistency with 23.501 and 23.502 and to allow an AF to specify individual QoS Related Parameters","secretary_remarks":"r04 agreed. Revised to S2-2109286, merging S2-2108427 and S2-2108740","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15100,"status":"revised","reservation_date":"2021-11-08 04:16:12","uploaded":"2021-11-08 18:47:20","revisionof":"","revisedto":"S2-2109286","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":675.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108479.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108539","title":"Update the correction field for the end-to-end Transparent Clock","source":"Tencent, Tencent Cloud, CATT","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the 5GS operates as a end-to-end Transparent Clock, the residence time (TSe - TSi) is the time based on the 5GS time and is converted into the PTP GM time based on the factor as specified in Equation (6) of clause 12.2.2 in IEEE\u00a0Std\u00a01588-2019, and the calculated residence time expressed in PTP GM is added to the correction field. 'Pdelay_Resp_Follow_UP' is changed to 'Pdelay_Resp_Follow_Up'.","secretary_remarks":"r07 agreed. Revised to S2-2109287.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15120,"status":"revised","reservation_date":"2021-11-08 08:40:43","uploaded":"2021-11-08 13:36:08","revisionof":"","revisedto":"S2-2109287","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3386.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108539.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108540","title":"Time Synchronization of the 5GS as IEEE 1588 Boundary Clock","source":"Tencent, Tencent Cloud, CATT","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the GM is external, the operation of 5GS as Boundary Clock assumes that profiles that are supported by the 5GS allows the exemption specified in clauses 9.5.9 and 9.5.10 of IEEE\u00a0Std\u00a01588\u00a0[126] where the originTimestamp (or preciseOriginTimestamp in case of two-step operation) is updated to the sum of the received originTimestamp (or preciseOriginTimestamp in case of two-step operation), the received correction field of Sync and Follow_Up (in case of two-step operation), residence time expressed in PTP GM time and link delay expressed in PTP GM time. After the originTimestamp (or preciseOriginTimestamp in case of two-step operation) is updated, the correction field of Sync and Follow_Up (in case of two-step operation) can be set to zero. After the originTimestamp (or preciseOriginTimestamp in case of two-step operation) is updated, the corretionField of Sync is set to zero. As described in clause\u00a05.27.1.2.2, the originTimestamp (or preciseOriginTimestamp in case of two-step operation) is updated with the correction field(s), 5GS residence time and link delay. A mathematically and functionally equivalent operation is specified for the time-aware system in clause 11.1.3 of IEEE\u00a0Std\u00a0802.1AS\u00a0[104]. If the 5GS operates as a Boundary Clock and the ingress TT is DS-TT, the UPF\/NW-TT then regenerates the Sync and Follow_Up (for two-step operation) messages with the updated originTimestamp (or preciseOriginTimestamp) as described by the exemption in clause\u00a05.27.1.1 based on the received Sync and Follow_Up messages for the PTP ports in Master state in NW-TT and DS-TT(s) within this PTP instance. The NW-TT\/UPF forwards the regenerated Sync and Follow_Up messages to the PDU session(s) related to the Master ports in the DS-TT(s) within this PTP instance. Due to the exemption described in clause 5.27.1.1, when the PTP instance in 5GS is configured to operate as a Boundary Clock, the 5GS does not need to synchronize its Local PTP Clock to the external PTP grandmaster. The ingress TT in 5GS measures the link delay expressed in PTP GM time and updatethe correction field with the measured link delay expressed in PTP GM time. The egress TT converts the 5GS residence time into the residence time expressed in PTP GM time and updates the originTimestamp (or preciseOriginTimestamp) to the sume of the received originTimestamp (or preciseOriginTimestamp), the corrected field which has been updated by the ingress TT and the residence time expressed in PTP GM time. The egress TT sets the corrected field to zero for the Sync and Follow_Up message (for two-step operation). The externally observable behaviour of 5GS still conforms to the specifications for a Boundary Clock as described in IEEE\u00a0Std\u00a01588\u00a0[126].","secretary_remarks":"Revision of (Noted) S2-2107343 from S2#147E. Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15140,"status":"noted","reservation_date":"2021-11-08 08:40:45","uploaded":"2021-11-08 13:36:08","revisionof":"S2-2107343","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3286.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108540.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108626","title":"Principle for Handling of PMIC exchange with UE(s) in idle mode","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - TSCTSF may indicate that the AMF is allowed to use ATC when it sends PMIC.","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15150,"status":"noted","reservation_date":"2021-11-08 10:02:02","uploaded":"2021-11-08 11:25:41","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3404.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108626.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108627","title":"Procedure for Handling of PMIC exchange with UE(s) in idle mode","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - TSCTSF may indicate that the AMF is allowed to use ATC when it sends PMIC.","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15160,"status":"noted","reservation_date":"2021-11-08 10:05:16","uploaded":"2021-11-08 11:25:41","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3267.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108627.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108630","title":"Relationship between Sync Exposure and Time Distribution","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Add relationship between Synchronization Activation\/Modification\/Deactivation and Time Distribution.","secretary_remarks":"r03 agreed. Revised to S2-2109288.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15170,"status":"revised","reservation_date":"2021-11-08 10:08:35","uploaded":"2021-11-08 11:25:41","revisionof":"","revisedto":"S2-2109288","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3405.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108630.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108632","title":"Correction on 5G access stratum time distribution parameters","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add conditions for 5G access stratum time distribution indication and mark Uu interface time synchronization error budget as optional.","secretary_remarks":"r04 agreed. Revised to S2-2109289.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15190,"status":"revised","reservation_date":"2021-11-08 10:09:36","uploaded":"2021-11-08 16:16:59","revisionof":"","revisedto":"S2-2109289","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":680.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108632.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108633","title":"Correction on 5G access stratum time distribution","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the time synchronization error budget is used for both the 5G access stratum time distribution method and (g)PTP based synchronization method. Add Nnef_TimeSynchronization service to the table of NF Services provided by NEF.","secretary_remarks":"r02 agreed. Revised to S2-2109290, merging S2-2108821","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15210,"status":"revised","reservation_date":"2021-11-08 10:09:37","uploaded":"2021-11-08 15:00:57","revisionof":"","revisedto":"S2-2109290","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3406.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108633.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108634","title":"Correction on 5G access stratum time distribution","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the description for Nnef_TimeSynchronization_ CapsUnsubscribe. Clarify that the 'Current state of the time synchronization configuration' in the input of the Ntsctsf_TimeSynchronization_ConfigUpdateNotify\/ Nnef_TimeSynchronization_ConfigUpdateNotify operation is the time synchronization information for the PTP instance as described in Table 5.28.3.1-2 of TS 23.501. And it is optional in steps 7-8 of the procedures in clause 4.15.9.3.2 and 4.15.9.3.3. Clarify that steps 5 to 10 of the procedure are used by the TSCTSF to manage the 5G access stratum time distribution for the UEs that are part of a PTP instance. Change '5G clock sync' to '5G access stratum time distribution method'.","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15230,"status":"noted","reservation_date":"2021-11-08 10:09:38","uploaded":"2021-11-08 15:00:57","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3268.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108634.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108635","title":"Clarifications on the use of DS-TT port MAC address","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifications are added to align with 23.501.","secretary_remarks":"r02 agreed. Revised to S2-2109291.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15240,"status":"revised","reservation_date":"2021-11-08 10:09:39","uploaded":"2021-11-08 15:00:57","revisionof":"","revisedto":"S2-2109291","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3269.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108635.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108636","title":"Clarifications on the use of DS-TT port MAC address","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifications are added to support time sensitive communication and time synchronization scenario.","secretary_remarks":"r01 agreed. Revised to S2-2109292.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15260,"status":"revised","reservation_date":"2021-11-08 10:09:40","uploaded":"2021-11-08 16:16:59","revisionof":"","revisedto":"S2-2109292","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":681.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108636.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108646","title":"Clarifications on Policy for AF","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Change 'Interacting with TSCTSF for Time synchronization service (see clause 5.27.1)' to 'Interacting with TSCTSF for Time synchronization service (see clause 5.27.1 of TS 23.501[2])' - Add specification numbers to the other clause references in the same way.","secretary_remarks":"r01 agreed. Revised to S2-2109293.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15280,"status":"revised","reservation_date":"2021-11-08 10:11:16","uploaded":"2021-11-08 11:25:41","revisionof":"","revisedto":"S2-2109293","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":682.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108646.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108705","title":"Processing (g)PTP messages for domain numbers and while in Disabled state","source":"NTT DOCOMO, Intel","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. In 5.27.1.2.2, when 5GS is operating as BC or PTP Relay, clarify that the NW-TT discards the message if the NW-TT does not have a matching PTP instance. In 5.27.1.2.2.2, remove the verification of domain number and sdoId when 5GS is operating as a Transparent Clock. 2. In 5.27.1.6, it is clarified that the DS-TT maintains the Disabled state for the PTP ports in DS-TT, and this state can be read by the TSCTSF or TSN AF from the DS-TT via PMIC. The DS-TT discards all (g)PTP messages while in Disabled state. The duplicate NOTE is removed from 5.27.1.5.","secretary_remarks":"Revision of (Postponed) S2-2107617 from S2#147E. r01 agreed. Revised to S2-2109294.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15300,"status":"revised","reservation_date":"2021-11-08 10:58:00","uploaded":"2021-11-08 17:05:28","revisionof":"S2-2107617","revisedto":"S2-2109294","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3322.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108705.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108738","title":"QoS parameter handling for TSC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description is updated as follows: The UE egress terminology and the UE-DS-TT Residence Time definition are updated by refereing to the SDAP layer to clarify the relation to the UE internal processing of PDUs. Clause 5.27.2 is renamed to also reflect the TSC Assistance Container The text in clause 5.27.2.1 is simplified a bit and a table listing the content of the TSC Assistance Container is added as well. Terminology is aligned and references are added in several places.","secretary_remarks":"Revision of (Endorsed) S2-2108139 from S2#147E. r04 agreed. Revised to S2-2109295.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15320,"status":"revised","reservation_date":"2021-11-08 11:24:16","uploaded":"2021-11-08 16:16:59","revisionof":"S2-2108139","revisedto":"S2-2109295","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3107.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108738.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108739","title":"QoS parameter handling for TSC","source":"Huawei, HiSilicon, Samsung","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is therefore proposed to update and restructure the description: The description of the TSC Assistance Container handling is described in a new clause (Support of Time Sensitive Communication and Time Synchronization). The description of the interaction between TSCTSF and PCF is added to the new clause. The description of the TSC Assistance Container content is replaced by a reference to 23.501 to have the definition in one place only.","secretary_remarks":"Revision of (Endorsed) S2-2108140 from S2#147E. r01 agreed. Revised to S2-2109296, merging S2-2108428 and S2-2108434","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15340,"status":"revised","reservation_date":"2021-11-08 11:24:17","uploaded":"2021-11-08 16:16:59","revisionof":"S2-2108140","revisedto":"S2-2109296","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":634.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108739.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108740","title":"QoS parameter handling for TSC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is therefore proposed to update and restructure the description by: Clarifying that either a QoS reference or a set of individual QoS parameters is provided by the AF (including the Alternative Service Requirements). The Requested 5GS Error Ratio is added as another QoS parameter that can be provided by the AF (as this is an important input for the 5QI selection). The mapping of AF provided QoS parameters to PCC rule QoS parameters is described explicitly. The principle for the selection of the 5QI is described explicitly. The possibility for a rejection of the AF request is added so that the PCF can respond appropriately if the QoS requirements (represented by the AF provided QoS parameters) cannot be fulfilled.","secretary_remarks":"Merged into S2-2109286","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15360,"status":"merged","reservation_date":"2021-11-08 11:24:18","uploaded":"2021-11-08 16:16:59","revisionof":"","revisedto":"S2-2200685","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":686.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108740.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108819","title":"Fix the EN on the priority in the AF session with required QoS procedure","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing the ENs on whether and how the PCF uses the Priority value provided by AF. And clarify that the Priority value provided by an AF is used by PCF to determine the Qos parameters.","secretary_remarks":"Revision of (Postponed) S2-2107661 from S2#147E. Merged into S2-2109285","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15370,"status":"merged","reservation_date":"2021-11-08 13:33:20","uploaded":"2021-11-08 14:09:21","revisionof":"S2-2107661","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3208.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108819.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108820","title":"Clarification on the time synchronization","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The configuration of the time synchronization service in 5GS for for options 1-4 by AF\/NEF and TSCTSF. Clarifying how the NW-TT determine the PTP instance. NW-TT forwards (g)PTP message to NW-TT port in Leader state.","secretary_remarks":"Revision of (Postponed) S2-2107664 from S2#147E. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15380,"status":"agreed","reservation_date":"2021-11-08 13:33:21","uploaded":"2021-11-08 14:09:21","revisionof":"S2-2107664","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3330.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108820.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108821","title":"Removing the PDU session description in 5G access stratum time synchronization distribution method","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing this method is applicable for both IP and Ethernet PDU Sessions","secretary_remarks":"Merged into S2-2109290","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15390,"status":"merged","reservation_date":"2021-11-08 13:33:22","uploaded":"2021-11-08 14:09:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3435.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108821.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108822","title":"Clarification on the Ntsctsf_QoSandTSCAssistance related service operation","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Replace NEF withTSCTSF in Ntsctsf_QoSandTSCAssistance_Notify service operation. Adding Transaction Reference ID as input. Removing the Transaction Reference ID in the output of Ntsctsf_QoSandTSCAssistance_Unsubscribe service operation","secretary_remarks":"Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15490,"status":"agreed","reservation_date":"2021-11-08 13:33:23","uploaded":"2021-11-08 14:09:21","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3291.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108822.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108847","title":"Multiple PTP instances supported in 5GS","source":"Tencent, Tencent Cloud","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The 5GS can be configured to operate in one or multiple PTP instances to operate in different mode or different types(i.e. PTP relay instance, Boundary Clock, end-to-end Transparent Clock, peer-to-peer Transparent Clock) for each PTP instance in clause 5.27.1.1 and 5.27.1.4. The time aware system is replaced with PTP relay instance in the clause 5.27 and its subclauses, annex H and K. For the gPTP sync and Follow_Up messages, it is supported only by the PTP relay instance in clause 5.27.1.2.2.1. In clause 5.27.1.2.2.2 , it is explicitly described the PTP instance is Boundary Clock or Transparent Clock. In clause 5.27.1.3, the (g)PTP event messages with the matching domains are forwarded. In clause 5.27.1.3, the 5GS supports multiple (g)PTP domains, also the 5GS shall support multiple PTP instances. And more PTP instances can be supported for the same (g)PTP domain, and the PTP instance can be differented by the ingress port number with the same (g)PTP domain.","secretary_remarks":"r01 agreed. Revised to S2-2109297.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15400,"status":"revised","reservation_date":"2021-11-08 14:01:31","uploaded":"2021-11-08 14:07:03","revisionof":"","revisedto":"S2-2109297","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3438.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108847.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108849","title":"Clarifications regarding TSCTSF discovery and selection","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarify that the TSCTSF notification address that is stored to the UDR is used only for time-sync PTP service. This means the PCF does not need to notify the TSCTSF for a PDU Session, unless the TSCTSF has received a prior AF-request for time-sync capability subscription. 2. Remove the storing of TSCTSF NF instance in the UDR. Note that the storing of TSCTSF notification address for a time-sync capability subscription is still necessary so that the PCF can notify the TSCTSF for a PDU Session matching to the time-sync capability subscription. 3. Separate the ASTI-related service operations into a separate service. This means that a different TSCTSF instance may be selected for ASTI and time-sync services. 4. Add a possibility for the TSCTSF to use _Update service operation if an AF-session already exists with the PCF. 5. Clarify that the SMF stores the '5GS Bridge information' until the PCF subscribes for it. This is the same principle as with any other events that are reported from the SMF to the PCF. Remove the storing in PCF. In case of QoS-request: the PCF may receive a subscription for the '5GS Bridge information' from the TSCTSF while the PCF does not have the 5GS Bridge information for the PDU Session. In this case the PCF triggers the PCF initiated SM policy association modification and subscribes for it from the SMF. The SMF reports the 5GS Bridge information to the PCF, and PCF reports it to the TSCTSF. In case of time-sync request before a PDU Session: During the SM policy association establishment, the PCF retrieves the TSCTSF notification address in UDR, or uses the local configuration of the TSCTSF address, to determine that the PCF needs to subscribe for the 5GS bridge information event from the SMF. The SMF initiates an SM policy association modification and reports the 5GS Bridge information to the PCF, and PCF reports it to the TSCTSF. In case of time-sync request after a PDU Session: During the SM policy association establishment, the PCF subscribes for the TSCTSF notification address in UDR. Upon the time-sync request, the TSCTSF updates the notification address to UDR, and UDR notifies the PCF. PCF triggers PCF initiated SM policy modification to subscribe for the 5GS bridge information from the SMF. The SMF reports the 5GS Bridge information to the PCF, and PCF reports it to the TSCTSF. 6. It is proposed to remove the ovelapping description in clause 4.15.6.6.a and refer to steps in clause 4.15.6.6 instead.","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15420,"status":"noted","reservation_date":"2021-11-08 14:02:06","uploaded":"2021-11-08 17:05:28","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3296.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108849.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108850","title":"Updates on AS time distribution","source":"CATT","contact":"Yuan Tao","contact-id":82804,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the Nnef_TimeSynchronization_ASTIDelete service operation used by AF. Clarify the use of PTP instance reference. Update the parameter Time synchronization configuration Id to PTP instance reference in Ntsctsf_TimeSynchronization_ASTI service operations","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15430,"status":"noted","reservation_date":"2021-11-08 14:02:09","uploaded":"2021-11-08 14:12:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3297.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108850.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108851","title":"Clafication on bridge information notification","source":"CATT","contact":"Yuan Tao","contact-id":82804,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the report on the event of the 5GS Bridge information Notification for TSCTSF. Add the interaction with TSCTSF for TSC Assistance Information and TSC QoS in description of AF functions.","secretary_remarks":"r02 agreed. Revised to S2-2109298.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15440,"status":"revised","reservation_date":"2021-11-08 14:02:10","uploaded":"2021-11-08 14:12:25","revisionof":"","revisedto":"S2-2109298","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":689.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108851.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108852","title":"Update on configuration for Sync and Announce reception timeouts","source":"CATT","contact":"Yuan Tao","contact-id":82804,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the Announce Interval attributes for time-aware system. To clarify the TSCTSF or TSN AF uses the 'Time synchronization information for each DS-TT port' element in UMIC for DS-TT ports.","secretary_remarks":"Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15460,"status":"agreed","reservation_date":"2021-11-08 14:02:11","uploaded":"2021-11-08 14:12:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3439.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108852.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108877","title":"Correction on PTP message handling in Boundary Clock","source":"Intel","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following is clarified in clause 5.27.1.2.2.2: a) The Boundary Clock in NW-TT\/UPF adds a timestamp (TSi) in the Suffix field of the regenerated Sync message and forwards it to the Master port(s) in NW-TT and to PDU Session(s) related to Master ports in the DS-TT(s). b) The yellow text is removed.","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15470,"status":"noted","reservation_date":"2021-11-08 14:22:56","uploaded":"2021-11-08 19:27:12","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3448.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108877.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108933","title":"Clarifications regarding TSCTSF discovery and selection","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. Clarify that the TSCTSF notification address that is stored to the UDR is used only for time-sync PTP service. This means the PCF does not need to notify the TSCTSF for a PDU Session, unless the TSCTSF has received a prior AF-request for time-sync capability subscription. 2. Remove the storing of TSCTSF NF instance in the UDR. Note that the storing of TSCTSF notification address for a time-sync capability subscription is still necessary so that the PCF can notify the TSCTSF for a PDU Session matching to the time-sync capability subscription. 3. Separate the ASTI-related service operations into a separate service. This means that a different TSCTSF instance may be selected for ASTI and time-sync services. 4. Clarify that TSCTSF deletes the TSCTSF Notification Target Address from the UDR after the subscriptions for '5GS and UE availability and capabilities for time synchronization service' are cancelled.","secretary_remarks":"Noted","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15480,"status":"noted","reservation_date":"2021-11-08 16:57:29","uploaded":"2021-11-08 17:05:28","revisionof":"","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3456.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108933.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2108961","title":"23.501: TSCTSF Discovery and Selection","source":"Nokia, Nokia Shangai Bell, Huawei, HiSilicon, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that a single TSCTSF instance is associated to a given DNN\/S-NSSAI. TSC TSF discovery section - to clarify that the GPSI, SUPI, Internal Group ID can also be used for discovery and selection. Add GPSI - in case the NF consumer uses GPSI for TSC TSF discovery and selection. Add SUPI or Internal Group ID - in case the NF consumer is only aware of the SUPI or Internal Group ID, it uses SUPI or Internal Group ID for TSC TSF discovery and selection. These parameters are in principle available already with NRF framework thus it should be straight forward to use them also for TSC TSF discovery selection.","secretary_remarks":"Revision of S2-2108475. r05 agreed. Revised to S2-2109282.","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15020,"status":"revised","reservation_date":"2021-11-08 19:24:06","uploaded":"2021-11-08 20:31:13","revisionof":"S2-2108475","revisedto":"S2-2109282","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3375.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2108961.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109278","title":"Deletion of selected enrties in UMIC\/PMIC data structures","source":"Intel, NTT DOCOMO","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifies the use of PMIC and UMIC for the deletion of selected entries in the UMIC\/PMIC data structures that are lists of variable size.","secretary_remarks":"Revision of S2-2108308r02. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14900,"status":"agreed","reservation_date":"2021-11-22 09:39:09","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108308","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3357.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109278.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109279","title":"Clarification on Static Filtering Entries","source":"Intel, NTT DOCOMO, Ericsson","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the SFE can indicate that an ingress frame matching the (MAC address, VID) pair can be forwarded to more than one egress port. Reworded NOTE4 in clause 5.8.2.5.3 by replacing 'routing in all directions' with 'forwarding of Ethernet frames to one or more egress ports'.","secretary_remarks":"Revision of S2-2108309r05. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14920,"status":"agreed","reservation_date":"2021-11-22 09:39:10","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108309","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"},{"winame":" Vertical_LAN"}],"crnumber":3358.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109279.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109280","title":"Improved PTP instance configuration management","source":"Intel, NTT DOCOMO, Ericsson, Nokia","contact":"Saso Stojanovski","contact-id":24932,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that the creation of PTP instance in DS-TT or NW-TT is achieved by using the 'Set parameter' operation as described in TS 24.539. For deletion of PTP Instance the text also refers to TS 24.539. Rev2: Change the 'Upon detection of a DS-TT port' to 'To add a DS-TT port into a PTP instance in 5GS', for a condition to create a new PTP instance in DS-TT. Remove the cases 'PTP instance is not available in 5GS' and 'PTP instance is already available in 5GS'.","secretary_remarks":"Revision of S2-2108315r02. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14940,"status":"agreed","reservation_date":"2021-11-22 09:39:12","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108315","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3242.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109280.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109281","title":"Adding Trusted AF in Time Synchronization procedures","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Add that a trusted AF may invoke services directly to the TSCTSF in Time Synchronization procedures. - Correct reference mistake to the Table about Time Synchronization capability event parameters.","secretary_remarks":"Revision of S2-2108429r01. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":14990,"status":"agreed","reservation_date":"2021-11-22 09:39:13","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108429","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3235.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109281.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109282","title":"23.501: TSCTSF Discovery and Selection","source":"Nokia, Nokia Shangai Bell, Huawei, HiSilicon, Ericsson, ZTE","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that a single TSCTSF instance is associated to a given DNN\/S-NSSAI.Clarify that the GPSI, SUPI, Internal Group ID can also be used for discovery and selection. Add GPSI - in case the NF consumer uses GPSI for TSCTSF discovery and selection. Add SUPI or Internal Group ID - in case the NF consumer is only aware of the SUPI or Internal Group ID, it uses SUPI or Internal Group ID for TSCTSF discovery and selection. These parameters are in principle available already with NRF framework thus it should be straight forward to use them also for TSC TSF discovery selection.","secretary_remarks":"Revision of S2-2108961r05. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15030,"status":"agreed","reservation_date":"2021-11-22 09:39:14","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108961","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3375.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109282.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109283","title":"23.502: TSCTSF Discovery and Selection","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the UDR based TSCTSF instance discovery and selection for SM policy association procedure","secretary_remarks":"Revision of S2-2108476r05. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15050,"status":"agreed","reservation_date":"2021-11-22 09:39:16","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108476","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3246.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109283.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109284","title":"23.502: Time Sync exposure procedure","source":"Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Ericsson","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Updating the figure 4.15.9.2 to correct the service names with the ones in the procedure description and service operation (Nnef_TimeSynchronization_CapsSubscribe' vs 'Nnef_TimeSynchronizationCaps_Subscribe') Also, fix the use of UDR","secretary_remarks":"Revision of S2-2108477r05. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15070,"status":"agreed","reservation_date":"2021-11-22 09:39:17","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108477","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3247.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109284.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109285","title":"Fixes for AF session with required QoS update procedure","source":"Nokia, Nokia Shanghai Bell, Huawei, Ericsson, ZTE","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1 - UDR storage of TSCTSF address for TSC QoS is eliminated. It is assumed that in TSCTSF discovery & selection (or local configuration) there is only one TSCTSF or TSCTSF set per UE\/S-NSSAI\/DNN. Hence the same TSCTSF (or set) is selected when the PCF sends 5GS Bridge Information (with UE residence time) to the TSCTSF and when an NEF sends an AF request for QoS. This significantly simplifies the QoS procedures and resolves the issue of always selecting a correct UDR (where a TSCTSF address is stored). 3 - A QoS Reference may not be specified with Individual QoS Parameters and Alternative QoS Related Parameters in the AF request. 4 - In step 1 (AF request), a reference is corrected. The currently referenced clause 5.7.1.2a of TS23.501 refers to Alternative QoS Profies (provided by the SMF to the RAN) not Alternative QoS Related parameters provided by the AF to the PCF. Instead a reference is given to 23.503 clause 6.1.3.22. Clarifying text is added at the end of step 1 with the 23.501 reference. 5 - Step 3 should only be executed when individual parameters for Alt QoS (Alternative QoS Related parameter set(s)) are not specified. A condition is added to the beginning of step 3 and a reference is added to point to 23.503 clause 6.1.3.22 6 - In steps 3a and 3b, the Alternative QoS Related parameters (ie: the individual parameters specified by the AF for a Alternative QoS Reference) are also part of the Alternative Service Requirements sent to the TSCTSF (3a) and PCF (3b). Note that the Alternative QoS Related Parameters (which are sent from AF to the PCF) and specify individual QoS Parameters for Alt QoS references (as per 23.503 clause 6.1.3.22) are not the same as the Alternative QoS parameter set(s) in the PCC rules, which are unchanged from Rel. 16. 7 - In step 4 text refering to Alternative QoS Related parameter sets is removed and in step 4a, the PCF may use the Alternative QoS Related parameter sets (that are part of the Alternative Service Requirements and originated at the AF) to determine the Alternative QoS parameter set(s) in the PCC rules. Note there is no change to the contents of the PCC rules - they already contain Alternative QoS parameter Set(s). 8 - The ENs on whether and how the PCF uses priority values specfied by an AF other than a TSN-AF is resolved. The AF requested priority may be used by the PCF to set priority of a QoS Flow as specfied in 23.501 clause 5.7.1.2a. 9 - Requested Priority is added to Nnef_AFsessionWithQoS and Ntsctsf_QoSandTSCAssistance service operations to be consistent with text in clause 4.15.6.6 and 4.15.6.6a The CR also includes aspects from CR#3131 (S2-2108426) merged in.","secretary_remarks":"Revision of S2-2108478r05, merging S2-2108426 and S2-2108819. CC#2: Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15090,"status":"agreed","reservation_date":"2021-11-22 09:39:18","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108478","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3248.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109285.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109286","title":"Fixes for AF session with required QoS update procedure","source":"Nokia, Nokia Shanghai Bell, Ericsson, ZTE","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 23.503 clause 6.1.3.22 is updated for consistency with 23.501 and 23.502 and to allow an AF to specify individual QoS Related Parameters Also merged in aspect from CR#0674 (S2-2108427).","secretary_remarks":"Revision of S2-2108479r04, merging S2-2108427 and S2-2108740. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15110,"status":"agreed","reservation_date":"2021-11-22 09:39:19","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108479","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":675.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109286.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109287","title":"Update the correction field for the end-to-end Transparent Clock","source":"Tencent, Tencent Cloud, CATT","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If the 5GS operates as a end-to-end Transparent Clock, the residence time (TSe - TSi) is the time based on the 5GS time and is converted into the PTP GM time based on the factor as specified in Equation (6) of clause 12.2.2 in IEEE Std 1588-2019 if needed, and the calculated residence time is added to the correction field.","secretary_remarks":"Revision of S2-2108539r07. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15130,"status":"agreed","reservation_date":"2021-11-22 09:39:20","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108539","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3386.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109287.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109288","title":"Relationship between Sync Exposure and Time Distribution","source":"Samsung, Ericsson","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Add relationship between Synchronization Activation\/Modification\/Deactivation and Time Distribution.","secretary_remarks":"Revision of S2-2108630r03. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15180,"status":"agreed","reservation_date":"2021-11-22 09:39:21","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108630","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3405.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109288.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109289","title":"Correction on 5G access stratum time distribution parameters","source":"Huawei, HiSilicon, Nokia, Nokia Shanghai Bell","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add conditions for 5G access stratum time distribution indication and mark Uu interface time synchronization error budget as optional.","secretary_remarks":"Revision of S2-2108632r04. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15200,"status":"agreed","reservation_date":"2021-11-22 09:39:22","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108632","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":680.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109289.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109290","title":"Correction on 5G access stratum time distribution","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the time synchronization error budget is used for both the 5G access stratum time distribution method and (g)PTP based synchronization method. Add Nnef_TimeSynchronization service to the table of NF Services provided by NEF.","secretary_remarks":"Revision of S2-2108633r02, merging S2-2108821. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15220,"status":"agreed","reservation_date":"2021-11-22 09:39:24","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108633","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3406.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109290.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109291","title":"Clarifications on the use of DS-TT port MAC address","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifications are added to align with 23.501.","secretary_remarks":"Revision of S2-2108635r02. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15250,"status":"agreed","reservation_date":"2021-11-22 09:39:25","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108635","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.2.1","workitem":[{"winame":"IIoT"}],"crnumber":3269.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109291.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109292","title":"Clarifications on the use of DS-TT port MAC address","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifications are added to support time sensitive communication and time synchronization scenario.","secretary_remarks":"Revision of S2-2108636r01. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15270,"status":"agreed","reservation_date":"2021-11-22 09:39:26","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108636","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":681.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109292.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109293","title":"Clarifications on Policy for AF","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: void the clause 6.2.10","secretary_remarks":"Revision of S2-2108646r01. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15290,"status":"agreed","reservation_date":"2021-11-22 09:39:27","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108646","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":682.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109293.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109294","title":"Processing (g)PTP messages for domain numbers and while in Disabled state","source":"NTT DOCOMO, Intel","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 1. In 5.27.1.2.2, when 5GS is operating as BC, TC or PTP Relay, clarify that the NW-TT discards the message if the NW-TT does not have a matching PTP instance. 2. In 5.27.1.6, it is clarified that the DS-TT maintains the Disabled state for the PTP ports in DS-TT, and this state can be read by the TSCTSF or TSN AF from the DS-TT via PMIC. The DS-TT discards all (g)PTP messages while in Disabled state. The duplicate NOTE is removed from 5.27.1.5.","secretary_remarks":"Revision of S2-2108705r01. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15310,"status":"agreed","reservation_date":"2021-11-22 09:39:28","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108705","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3322.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109294.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109295","title":"QoS parameter handling for TSC","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The description is updated as follows: Clause 5.27.2 is renamed to also reflect the TSC Assistance Container The text in clause 5.27.2.1 is simplified a bit and a table listing the content of the TSC Assistance Container is added as well. Terminology is aligned and references are added in several places.","secretary_remarks":"Revision of S2-2108738r04. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15330,"status":"agreed","reservation_date":"2021-11-22 09:39:30","uploaded":"2021-11-23 15:31:12","revisionof":"S2-2108738","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3107.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109295.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109296","title":"QoS parameter handling for TSC","source":"Huawei, HiSilicon, Samsung, Ericsson","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is therefore proposed to update and restructure the description: The description of the interaction between TSCTSF and PCF is added as a new clause (Support of Time Sensitive Communication and Time Synchronization). The description of the TSC Assistance Container content is replaced by a reference to 23.501 to have the definition in one place only.","secretary_remarks":"Revision of S2-2108739r01, merging S2-2108428 and S2-2108434. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15350,"status":"agreed","reservation_date":"2021-11-22 09:39:31","uploaded":"2021-11-23 15:31:13","revisionof":"S2-2108739","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":634.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109296.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109297","title":"Multiple PTP instances supported in 5GS","source":"Tencent, Tencent Cloud","contact":"Chunshan Xiong","contact-id":79110,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The 5GS can be configured to operate in one or multiple PTP instances to operate in different mode or different types(i.e. time-aware system, Boundary Clock, end-to-end Transparent Clock, peer-to-peer Transparent Clock) for each PTP instance in clause 5.27.1.1","secretary_remarks":"Revision of S2-2108847r01. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15410,"status":"agreed","reservation_date":"2021-11-22 09:39:33","uploaded":"2021-11-23 15:31:13","revisionof":"S2-2108847","revisedto":"","release":"Rel-17","crspec":23.501,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":3438.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211299","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109297.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2109298","title":"Clafication on bridge information notification","source":"CATT","contact":"Yuan Tao","contact-id":82804,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the report on the event of the 5GS Bridge information Notification for TSCTSF.","secretary_remarks":"Revision of S2-2108851r02. Approved","agenda_item_sort_order":48,"ainumber":"8.5","ainame":"Enhanced support of Industrial IoT - TSC\/URLLC enhancements (IIoT)","tdoc_agenda_sort_order":15450,"status":"agreed","reservation_date":"2021-11-22 09:39:34","uploaded":"2021-11-23 15:31:13","revisionof":"S2-2108851","revisedto":"","release":"Rel-17","crspec":23.503,"crspecversion":"17.2.0","workitem":[{"winame":"IIoT"}],"crnumber":689.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-211300","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_148E_Electronic_2021-11\/Docs\/S2-2109298.zip","group":"S2","meeting":"S2-148-e","year":2021,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]