[{"name":"S2-2300319","title":"KI #1: Update to address ENs","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing the following Editor s Note and adding a proposal to deliver information to the UE using SIB in Annex A, and adding it to the conclusion in clause 8.5: Editor's note: The details of which existing\/new SIB information the UE uses to determine that the RAN timing synchronization status has changed is FFS and will be coordinated with RAN WGs. Removing the following Editor s Note and adding Note to indicate that UEs in Connected mode can be provided with more accurate timing information, and that there are risks to consider Idle or Inactive UE states given that SIB messages are unprotected and broadcasted. Editor's note: Providing RAN timing synchronization status information to the UE in RRC_Idle and RRC_Inactive state is FFS. Removing the following Editor s Note and adding a proposal on the needed clock quality parameters to be provided to UE, or to be used by RAN to determine whether the clock quality is acceptable or not. Editor's note: Which clock quality metrics (e.g. clock accuracy, traceability to UTC, frequency stability) will be provided to the UE and will be used to determine whether the clock quality is acceptable or not is FFS.","secretary_remarks":"Not Handled","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22110,"status":"not treated","reservation_date":"2023-06-01 13:20:33","uploaded":"2023-01-09 23:33:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":1.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300319.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"8.5, A.1.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300407","title":"TR 23.700 KI#1 conclusion update","source":"Nokia, Nokia Shanghai Bell, Qualcomm","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are introduced in the conclusions for KI#1: - Including Alternative 1 from Annex A in the conclusions for UEs in RRC_INACTIVE\/IDLE. - Updating the naming used in KI#1 conclusions to further clarify when it refers to RAN timing synchronization status to TSCTSF (via OAM or control plane) or Clock quality information to UE. - Removal of open ENs.","secretary_remarks":"CC#4: r20 was agreed and was revised to S2-2301461","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22060,"status":"revised","reservation_date":"2023-07-01 18:35:06","uploaded":"2023-01-07 19:37:39","revisionof":"","revisedto":"S2-2301461","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"FS_5TRS_URLLC"}],"crnumber":2.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300407.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"8.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300414","title":"TR 23.700 KI#6 conclusion update","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of open ENs related to periodicity feedback","secretary_remarks":"r05 agreed. Revised to S2-2301419.","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22040,"status":"revised","reservation_date":"2023-07-01 18:35:14","uploaded":"2023-01-07 19:37:39","revisionof":"","revisedto":"S2-2301419","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"FS_5TRS_URLLC"}],"crnumber":3.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300414.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300782","title":"Conclusion for FS_5TRS_URLLC KI#6","source":"Samsung","contact":"Sang-Jun Moon","contact-id":30993,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Conclusion for FS_5TRS_URLLC KI#6 is updated.","secretary_remarks":"Not Handled","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22100,"status":"not treated","reservation_date":"2023-09-01 09:44:42","uploaded":"2023-01-09 10:52:09","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"FS_5TRS_URLLC"}],"crnumber":4.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300782.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"8.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300947","title":"KI1 conclusion update","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For editor s note: Providing RAN timing synchronization status information to the UE in RRC_Idle and RRC_Inactive state is FFS. Time status reporting to TSCTSF includes RAN time status reporting and UPF time status reporting. It is assumed that NG-RAN and UPF can locally detect time synchronization degradation\/improvement\/failures. For RRC_Connected UE, RAN provides timing synchronization status information. The timing synchronization status information can be the clock quality detail level or clock quality acceptance criteria. The specified values are based on agreement between the 5G network operator and the client network operator. The open issue here is whether to provide RAN timing synchronization status information to the UE in RRC_Idle and RRC_Inactive state. For RRC_Idle and RRC_Inactive UE, SIB broadcast information is used to enable UEs to determine that the timing synchronization status of the cell the UE camping on has changed. If the UE is going to receive additional time synchronzaition status information, it can performs a registration or the UE Triggered Connection Resume in RRC Inactive procedure for RAN timing synchronization status information. Also, the error budget is an essential parameter to evaluate the time synchronization service requirement. For UE in idle or inactive, the time sycnhronization information would not be as accurate as UE in connected state. Therefore, if the UE is in RRC_IDLE or RRC_INACTIVE state, RAN cannot determine whether Uu error budget can still be filfilled or not when the degradation\/improvement\/failure happens. So that delivering RAN timing synchronization status information to idle\/inactive UE handling should not supported for Release 18. RAN can uses a status report ID and a timestamp to notify idle\/inactive UE the RAN time sycnhronization status. For more additional RAN time synchronization status information based on the clock quality detail level or clock quality acceptance criteria., UE can enter connected status. This proposal aligns with the content of key issue 3 and the latter focuses on subscription based on per UE level service. Thus, the paper proposes to use Anlex 1.1 or 1.2 as the baseline to notify RAN time synchronization status towards the UE. Proposal 1: Idle or inactive UE uses status report ID plus a flag or timestamp to determine whether there is a new time synchronization status report available. For editor s note: Editor's note: Whether alternatively NG-RAN can be responsible for determining the impacted UE(s) and sending the NG-RAN timing synchronization status reports to the AMF via NG-AP signalling, together with the impacted UE(s) is FFS. One alternatives is that TSCTSF subscribes to receive location information from AMF for UEs that AF requested time synchronization for. If the UE is in CM-IDLE, TSCTSF can request UEs for which an AF requested time synchronization to perform a Registration. Then TSCTSF correlates the latest timing synchronization status of RAN nodes and the UE location information received from AMF to determine the UE ID(s) impacted by RAN node timing status degradation\/improvement\/failure. The other alternative is using node level signaling between TSCTSF and RAN to determine impacted UEs. TSCTSF subscribes to RAN timing synchronization status from AMF for UEs and TSCTSF receives RAN timing synchronization status information by NGAP method when timing synchronization status changes (degradation\/improvement\/failure). When the NG-RAN time sychronization status changes, the NG-RAN is responsible for determining the impacted serving UE(s) and reporting the UE(s) to the AMF. Then the AMF forwards the notification to the TSCTSF. This alternative is feasible because the NG-RAN can determine that the 5G access stratum time is delivered to and received by the serving UE(s). Same with the option one, if the UE is in CM-IDLE, the UE will be requested to performed a registration. Both of the two alternatives are feasible t","secretary_remarks":"Not Handled","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22090,"status":"not treated","reservation_date":"2023-09-01 12:57:06","uploaded":"2023-01-09 15:34:22","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"FS_5TRS_URLLC"}],"crnumber":6.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300947.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2300948","title":"KI3 conclusion update","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: For editor s note: Editor's note: How to enable an AF to request ASTI service if there is also an ASTI subscription in the Access and Mobility Subscription data is FFS. The Editor s Note is to clarify that if there is 'Access Stratum Time Synchronization Service Authorization' in the 'Access and Mobility Subscription data', the 'AF request Authorization' for ASTI based in the 'Time Synchronization Subscription data' should not be set to 'not allowed'. The AF-requested ASTI service should be fulfilled if it is agreed as per SLA. This proposal aligns with the conclusion part in key issue 1. Therefore, it is assumed that the UDM subscription does not preclude AF requested time sync service, in terms of Uu time synchronization error budget, coverage area, periods of Start and stop times defining active times of Access Stratum Time Synchronization Service that is agreed as per SLA. In addition, If there is an SLA between operator and AF, AF can provision a list of UE(s) to receive the time synchronization service. For those UE(s), it is assumed that in the Time Synchronization Subscription data, the bullet 'allowed' or 'not allowed' for ASTI based time synchronization services (per UE identity) should always be set to 'allowed'. Based on this, the Note below is removed and two new Notes for proceeding the agreed SLA service are added .","secretary_remarks":"CC#5: Noted","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22030,"status":"noted","reservation_date":"2023-09-01 12:57:07","uploaded":"2023-01-09 15:34:22","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"FS_5TRS_URLLC"}],"crnumber":7.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2300948.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2301110","title":"KI#1, update the conclusion for the KI#1 to resovle the ENs on providing the time sync status to UE.","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The CR resolves Editor's note in the conclusion for the KI#1.","secretary_remarks":"Not Handled","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22080,"status":"not treated","reservation_date":"2023-09-01 15:25:45","uploaded":"2023-01-09 22:42:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":8.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2301110.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2301419","title":"TR 23.700 KI#6 conclusion update","source":"Nokia, Nokia Shanghai Bell, Samsung","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of open ENs related to periodicity feedback","secretary_remarks":"Revision of S2-2300414r05. Approved","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22050,"status":"agreed","reservation_date":"2023-01-24 07:43:34","uploaded":"2023-01-24 08:01:05","revisionof":"S2-2300414","revisedto":"","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"FS_5TRS_URLLC"}],"crnumber":3.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-230066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2301419.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"8.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2301461","title":"TR 23.700 KI#1 conclusion update","source":"Nokia, Nokia Shanghai Bell, Qualcomm, Huawei, ZTE, Samsung","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The following changes are introduced in the conclusions for KI#1: - Including Alternative 1 from Annex A in the conclusions for UEs in RRC_INACTIVE\/IDLE. - Updating the naming used in KI#1 conclusions to further clarify when it refers to RAN timing synchronization status to TSCTSF (via OAM or control plane) or Clock quality information to UE. - Removal of open ENs.","secretary_remarks":"Revision of S2-2300407r20. Approved","agenda_item_sort_order":107,"ainumber":"9.18.1","ainame":"Study on 5G Timing Resiliency and TSC & URLLC enhancements (FS_5TRS_URLLC)","tdoc_agenda_sort_order":22070,"status":"agreed","reservation_date":"2023-01-24 07:44:16","uploaded":"2023-01-24 08:01:06","revisionof":"S2-2300407","revisedto":"","release":"Rel-18","crspec":"23.700-25","crspecversion":"18.0.0","workitem":[{"winame":"FS_5TRS_URLLC"}],"crnumber":2.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"SP-230066","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_154AHE_Electronic_2023-01\/Docs\/S2-2301461.zip","group":"S2","meeting":"S2-154-AH-e","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"8.5","crsinpack":null,"crsinpacknumber":0}]