[{"name":"S2-2310084","title":"LS from CT WG4: Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 is specifying in a new stage 3 specification (TS 29.585) the protocol used between the SMF\/CUC and the (R)AN\/AN-TL and UPF\/CN-TL, to retrieve the End Station (ES) capabilities and configure TSN features (TN streams) in the ES. This corresponds to the Get Request\/Response and Set Request\/Response specified in TS 23.501\/23.502 that are transferred in TL-Containers in NGAP over N2 and in PFCP over N4. {. . .} Action: CT WG4 kindly asks SA WG2 to answer the above questions and clarify stage 2 requirements accordingly, where necessary.","secretary_remarks":"Revision of Postponed S2-2308351 from SA WG2#158. Responses drafted in S2-2310322, S2-2310847. Final response in S2-2311886","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22490,"status":"replied to","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308351","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3","lsoriginalls":"C4-233170","lsreply":"S2-2311886","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310084.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310087","title":"LS from CT WG6: Reply LS on UICC configuration for IMS Data Channel","source":"CT WG6","contact":"Weijing Huo","contact-id":81408,"tdoctype":"LS in","for":"Action","abstract":"CT WG6 thanks SA WG2 for the LS (S2-2307533). It is not very clear for CT WG6 which parameters need to be stored on the UICC to allow the UE to decide when to establish a Data Channel via SIP\/SDP, and CT WG6 kindly asks SA WG2 to specify the parameters that the UICC needs to store. Action: CT WG6 kindly asks SA WG2 to take the above information into account and to provide feedback to CT WG6.","secretary_remarks":"Revision of Postponed S2-2308357 from SA WG2#158. Responses drafted in S2-2310835, S2-2310921. Final response in S2-2311773","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22850,"status":"replied to","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308357","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"C6-230469","lsreply":"S2-2311773","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310087.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310092","title":"LS from CT WG1: LS on the scope of LCS-SS messages transferred via the LCS user plane","source":"CT WG1","contact":"Hang Yu","contact-id":93029,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has been discussing the LCS user plane protocol to transfer LCS supplementary service (LCS-SS) messages in stage 3 specifications. Currently, different messages (e.g., MO-LR, event reporting, location privacy setting) can be encapsulated in the LCS-SS message. As per the statement in clause 5.10 of TS 23.273, the LCS-SS messages and LPP messages can be transferred via the user plane. However, only the event reporting message is stated in clause 6.18 of TS 23.273. CT WG1 would like to ask SA WG2 to confirm the scope of LCS-SS messages transferred via the user plane. Action: CT WG1 kindly asks SA WG2 to answer the above question and update the stage 2 specification if needed.","secretary_remarks":"Responses drafted in S2-2310569, S2-2310762. Final response in S2-2311915","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22900,"status":"replied to","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-236453","lsreply":"S2-2311915","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310092.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310093","title":"LS from CT WG1: LS on defining PIN ID format","source":"CT WG1","contact":"Sang Min Park","contact-id":95530,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has worked on the protocol aspects of PIN work item for Rel-18. One of the points that are not finalized yet is the format of PIN ID. CT WG1 assumes that the format should be defined in the stage 2, so that CT WG1 refers and designs protocol accordingly. So CT WG1 would like to ask SA WG2 to define or provide the format of PIN ID. Action: CT WG1kindly ask SA WG2 to define or provide the format of PIN ID.","secretary_remarks":"Responses drafted in S2-2310782, S2-2310381, S2-2310436, S2-2310834. Final response in S2-2311776","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23110,"status":"replied to","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3, CT WG4","lsoriginalls":"C1-236503","lsreply":"S2-2311776","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310093.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310094","title":"LS from CT WG1: LS on extension of operator specific connection capabilities in URSP","source":"CT WG1","contact":"Lin Shu","contact-id":43310,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to inform SA WG2 that CT WG1 has agreed attached CR to extend the value range of the operator specific connection capabilities in URSP to match against operator specific traffic categories. Action: CT WG1 kindly asks SA WG2 to take above information into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23210,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"GSMA URSPWI, GSMA UPG, GSMA NRG, GSMA TSG","lsoriginalls":"C1-236519","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310094.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310095","title":"LS from CT WG1: Reply LS on Traffic Categories","source":"CT WG1","contact":"Vivek Gupta","contact-id":96764,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 thanks GSMA for their LS (C1-230713) on Traffic Categories. CT WG1 has considered the traffic categories specified by GSMA PRD NG.135, version 3.0 in clause 3.1.9 and has updated the list of connection capabilities in TS 24.526 as per the agreed attached CR. Action: CT WG1 kindly asks SA WG2 to take the above response into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23220,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA URSPWI, SA WG2","Cc":"","lsoriginalls":"C1-236520","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310095.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310098","title":"LS from CT WG1: LS on LPP message and supplementary service event report over a user plane connection between UE and LMF","source":"CT WG1","contact":"Mikael Wass","contact-id":42217,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 would like to thank SA WG2 for the LS on LPP message and supplementary service event report over a user plane connection between UE and LMF. In addition to the initial response provided in reply-LS C1-231129 CT WG1 would like to add the following response. SA WG2 Question: SA WG2 kindly asks CT WG1 and CT WG4 to comment on suitable types of user plane address for the LMF supporting user plane positioning (e.g. such as an IP address and\/or FQDN) and whether, which or what the transport protocols and application level messages to transfer LPP messages and supplementary service event report could be identified or defined by CT WG1 or CT WG4. CT WG1 Answer: For specification of transport of LPP messages and supplementary service event reports over a user plane connection between UE and LMF, CT WG1 has decided to specify a new protocol, LCS-UPP, in 3GPP TS 24.572. The LCS-UPP protocol provides connectivity on a secure user plane connection and supports both LPP and supplementary services. CT WG1 further noted that user plane positioning using SUPL is described in 3GPP TS 38.305 and 3GPP TS 23.271 since Rel15, and it is the view of CT WG1 that this option remains unchanged even after introducing the user plane positioning based on LCS-UPP. CT WG1 intends to specify requirements for co-existence between the SUPL option and the LCS-UPP option as part of 3GPP TS 24.572. Action: CT WG1 asks SA WG2 group to take the above information into account and, if needed, update related specification accordingly.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23080,"status":"postponed","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311926","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3, RAN WG2, CT WG4","lsoriginalls":"C1-236562","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310098.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310099","title":"LS from CT WG1: LS on the requirements for slice-based PLMN selection","source":"CT WG1","contact":"Amer Catovic","contact-id":39766,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 has initiated a work item on Slice-based PLMN selection (SbPS). The stage 1 requirement that this work is based on is in TS 22.261: {. . .}","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22430,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG CT, TSG SA, SA WG1","Cc":"SA WG2","lsoriginalls":"C1-236565","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310099.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310100","title":"LS from CT WG1: LS on the service requirement of restricting satellite access RAT type","source":"CT WG1","contact":"Sang Min Park","contact-id":95530,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 is progressing with the stage 3 aspects of 5GSAT_Ph2 work for Rel-18. CT WG1 is considering a scenario whereby an operator, who operates both satellite access and non-satellite access in a same PLMN (using same MCC\/MNC), might not wish to allow the user with a UE capable of satellite access to be served via satellite cells while it is allowed to be served via non-satellite cells based on the subscription, i.e. the operator wishes to limit provision of service to a user under certain terrestrial access but not NTN access. One of the potential solutions is to reject the UE s NAS request sent via a satellite cell with a certain cause code. Therefore, CT WG1 would like to ask SA WG1 whether, in terms of the service requirement, a network operator should be able to restrict the usage of satellite access in a network (in the PLMN) when the user is not allowed to use the satellite access by subscription.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22440,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2, RAN WG2","lsoriginalls":"C1-236567","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310100.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310103","title":"LS from CT WG3: LS on clarification for list of UEs parameter handling","source":"CT WG3","contact":"Parthasarathi Ravindran","contact-id":68434,"tdoctype":"LS in","for":"Action","abstract":"As per TS 23.502 clause 5.2.6.9.2 Nnef_AFsessionWithQoS_Create service operation {. . .} It is not clear about for Flow description information(s) where the flow description information is per UE or it is the common flow description information(s) for list of UE. CT WG3 would like to ask SA WG2: Question 1: In case list of UE is provided, whether the flow description information(s) will be provided per UE or the flow description information(s) is common for list of UEs?. Action: CT WG3 kindly asks SA WG2 to answer above questions and amend the SA WG2 specifications accordingly.","secretary_remarks":"Responses drafted in S2-2310228, S2-2310536. Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23230,"status":"postponed","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311928","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-233721","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310103.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310107","title":"LS On EAC Mode Subscription Optimization","source":"CT WG4","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Action","abstract":"During implementation of the NSAC, CT WG4 has observed certain limitations of the current service operations: 1. In the current design, the AMF implicitly subscribes to the NSACF for the EAC mode status and change of certain S-NSSAI in the service operation to perform NSAC for certain UE. The AMF cannot get the EAC mode from the NSACF before the first UE NSAC service operation for the S-NSSAI. After the subscription was established, when the AMF needs to update the EAC notification URI or is no longer interested in receiving EAC modes, the AMF can only make the change via a subsequent service operation to perform UE NSAC. Before the NSACF is aware of the change, the NSACF may retry the EAC notification to the AMF and continuously receive negative responses or timeouts. 2. When Access Type specific NSAC is configured in NSACF, the number of UEs per S-NSSAI is counted per access type, but EAC mode currently is access type agnostic. CT WG4 has the following questions to SA WG2 for clarification: Q1: Whether the AMF should be allowed to create and\/or modify the EAC mode subscription independently, instead of always relying on a service operation for UE NSAC? Q2: Will it be considered to have EAC Mode per access type, when per access type NSAC is configured in the NSACF?. Action: CT WG4 kindly asks SA WG2 to answer the listed questions.","secretary_remarks":"Responses drafted in S2-2310374, S2-2310909, S2-2310984. Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23320,"status":"postponed","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311929","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-233550","lsreply":"S2-2312708","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310107.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310109","title":"LS from CT WG4: LS On Multiple QoS Class Handling During Service Continuity from 5GS to EPS","source":"CT WG4","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Action","abstract":"When implementing of stage 2 requirements of eLCS_Ph3 for Multiple QoS class handling during Service Continuity from 5GS to EPS, CT WG4 has discovered some inconsistences in stage 2 specification. According to TS 23.273 v18.2.0, when Multiple QoS class is used for a deferred location request in 5GS, either the LMF or the UE shall perform a mapping from the Multiple QoS class to LCS QoS class that are supported in EPS (Best Efforts\/Assured): {. . .} To continue the stage 3 implementation, CT WG4 has the following questions: Q1: Is the Multiple QoS Class expected to be provided to the UE in deferred MT-LR procedure? If yes, how should the UE use the multiple QoS class for event reporting? Q2: If the Multiple QoS Class is not to be provided to the UE in deferred MT-LR procedure, how could UE and\/or LMF perform Multiple QoS class mapping to EPS supported QoS classes during the Service Continuity from 5GS to EPS?. Action: CT WG4 kindly asks SA WG2 to answer the listed questions, and possibly make necessary clarification or corrections in stage 2 specifications.","secretary_remarks":"Response drafted in S2-2310567. Final response in S2-2311775","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23020,"status":"replied to","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-233619","lsreply":"S2-2311775","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310109.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310110","title":"LS from CT WG4: Reply LS on INACTIVE eDRX above 10.24sec and SDT","source":"CT WG4","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks RAN WG3 for the Reply LS on INACTIVE eDRX above 10.24sec and SDT. RAN WG3 question: Furthermore, RAN WG3 has discussed the need to signal the DL data size in the DL DATA NOTIFICATION message to help NG-RAN making decision if MT-SDT paging can be performed based on the QFI associated with the configured SDT radio bearer. RAN WG3 would like to ask SA WG2 and CT WG4 whether it is feasible that DL data size can be signalled to the NG-RAN (e.g. for QoS flows that have buffered data in the CN) along with the paging differentiation parameters to assist NG-RAN for MT-SDT paging decision. CT WG4 discussed the matter and agreed it is feasible to request the UPF to report the DL data size to the SMF over N4 interface. Similar function has been specified for an SGW-U reporting DL data size to the SGW-C over Sxa interface to support the MT-EDT feature in EPS. Action: CT WG4 kindly asks RAN WG3 and SA WG2 to take above information in account.","secretary_remarks":"Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23370,"status":"postponed","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311930","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, RAN WG3","Cc":"RAN WG2","lsoriginalls":"C4-233691","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310110.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310111","title":"LS from CT WG4: Reply LS on Proposed method for AMF discovery and subscription by the TSCTSF","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks SA WG2 for their LS on Proposed method for AMF discovery and subscription by the TSCTSF. SA WG2 question: There were concerns related to excessive signaling and failure issues thus SA WG2 would like to kindly request CT WG4 to provide feedback regarding the two methods from stage 3 perspective. Both alternatives a) (NRF based AMF discovery and subscription) and b) (UDM based AMF discovery and subscription) described in the SA WG2 LS (S2-2308233) can be used by the TSCTSF to discover and subscribe to AMFs, and which one is preferable may depend on deployment and service-related factors. {. . .}. Action: CT WG4 asks SA WG2 group to take the above information into account.","secretary_remarks":"Responses drafted in S2-2311010, S2-2311085. Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22610,"status":"postponed","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311931","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"C4-233692","lsreply":"S2-2313074","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310111.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310113","title":"LS from RAN WG1: Reply LS on PRU Procedures","source":"RAN WG1","contact":"Ren Da","contact-id":70182,"tdoctype":"LS in","for":"Action","abstract":"RAN WG1 thanks SA WG2 for their LS on PRU procedures, which includes the following request: {. . .}. Action: RAN WG1 respectfully asks SA WG2 to take the above reply into account for future work.","secretary_remarks":"Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23380,"status":"postponed","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311933","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3, RAN WG2, SA WG2","Cc":"RAN WG4","lsoriginalls":"R1-2308644","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310113.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310114","title":"LS from RAN WG1: LS on the resource selection window for Scheme 2 in a dedicated resource pool for positioning","source":"RAN WG1","contact":"Alexandros Manolakos","contact-id":104384,"tdoctype":"LS in","for":"Information","abstract":"In the Rel-18 WI Expanded and Improved NR Positioning, with regards to Sidelink Positioning, RAN WG1 discussed the derivation of the resource selection window for Scheme 2 in a dedicated resource pool and made the following working assumption: Working assumption For Scheme 2, in a dedicated resource pool, using Rel-16 resource (re)-selection procedure as the starting point, support the following modification: Modification 2: For the resource selection window: o Option 1: for the derivation of the window, using the legacy approach as a starting point, substitute the Packet Delay Budget (PDB) with a Delay Budget for SL-PRS","secretary_remarks":"Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23390,"status":"postponed","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311934","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2","lsoriginalls":"R1-2308651","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310114.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310120","title":"LS from RAN WG2: LS on Event ID broadcast in SIB9","source":"RAN WG2","contact":"Chunli Wu","contact-id":84444,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed RAN timing synchronization status reporting and agreed the gNB always broadcasts Event ID in SIB9 if it supports and uses the feature. Action: RAN WG2 respectfully asks SA WG2 to take the RAN WG2 agreement into account.","secretary_remarks":"Response drafted in S2-2311008. Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22790,"status":"postponed","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311935","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2309264","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310120.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310122","title":"LS from RAN WG2: LS on misalignment between PTW and Coverage Window","source":"RAN WG2","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed the issue of possible misalignment between PTW and Coverage Window in IoT NTN when eDRX is configured (e.g., due to the eDRX configuration, the PTW for a particular PO does not coincide with the coverage). Specifically, RAN WG2 would like to ask SA WG2 the following questions: 1) Whether the issue of misalignment between PTW and Coverage Window is valid from SA WG2 s point of view? 2) If the answer to Q1) is yes, whether it can be solved by any method that SA WG2 has already specified or by network implementation, or there is need for further enhancement?. Action: RAN WG2 respectfully asks SA WG2 to provide feedback on the questions above.","secretary_remarks":"Responses drafted in S2-2310400, S2-2310940, S2-2311023, S2-2311198. Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23400,"status":"postponed","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:36","revisionof":"","revisedto":"S2-2311936","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2309283","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310122.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310127","title":"LS from RAN WG3: LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"RAN WG3","contact":"Filip Barac","contact-id":76369,"tdoctype":"LS in","for":"Action","abstract":"To ensure signalling-based and management-based QoE measurement continuity for MBS across RRC states, RAN WG3 agreed that the QoE measurement configuration information should be made available to the gNB serving the UE when the UE transits from the RRC_IDLE to RRC_CONNECTED state. In that respect, RAN WG3 is discussing whether the QoE measurement configuration information should be stored at the UE or at the AMF while the UE is in RRC_IDLE state. After the UE transits from the RRC_IDLE to RRC_CONNECTED state, this information should be provided to the serving gNB. The QoE measurement configuration information to be stored includes the following, per QoE configuration: QoE reference. The IP address or ID of the Measurement Collection Entity. The measConfigAppLayerID. Service type. QoE measurement type (s-based or m-based measurement) for MBS broadcast service. (Working Assumption): available RAN visible QoE metrics. Additional information to be stored is FFS. In addition, RAN WG3 agreed that, after a UE configured for QoE measurements transits from the RRC_IDLE to the RRC_CONNECTED state, the gNB serving of the UE should be aware of the status of MBS QoE measurement session. Action: RAN WG3 respectfully asks SA WG2 to inform RAN WG3 whether there are any technical issues with storing the above listed QoE measurement configuration information at the AMF. The QoE measurement configuration information stored at the AMF would be transparent to the AMF.","secretary_remarks":"Responses drafted in S2-2310637, S2-2310623, S2-2310740. Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23460,"status":"postponed","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:36","revisionof":"","revisedto":"S2-2311939","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"SA WG5, SA WG3","lsoriginalls":"R3-234745","lsreply":"S2-2312951","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310127.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310132","title":"LS from SA WG5: Reply to LS on customer acceptance of limited QoS degradation to save energy in the network","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG1 for your Reply LS on customer acceptance of limited QoS degradation to save energy in the network. SA WG5 acknowledges that: 1. no compromise on user experience while achieving energy efficiency has been considered so far in SA WG1; 2. there are some use cases in TR 22.882, such as in clause 5.1, where a maximum energy utilization rate can be defined to limit the energy consumption of a best-effort communication service; 3. all adjustments in QoS or other actions influencing user experience are considered under the scope of pre-configured SLA (e.g. within the boundaries of an acceptable QoS provided to end user applications). SA WG5 understanding of the use case described in TR 22.882 clause 5.1 is that, based on its own policies, the CSP \/ Network Operator may trigger energy saving actions in its network, while respecting agreed SLA. In the SA WG5 potential use case, the energy saving actions are triggered upon request from the customer: QoS degradation (also within agreed SLA) is requested by the customer, provided a) it results in energy savings in the Network Operator s network and b) these energy savings can be measured, imputable and reported to the customer. SA WG5 would like to have further exchange with SA WG1 on this topic during our respective R19 work.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22470,"status":"noted","reservation_date":"2023-09-20 14:39:57","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"TSG SA, SA WG2","lsoriginalls":"S5-235364","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310132.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310133","title":"LS from SA WG5: Reply LS to SA2 on improved KPIs involving end-to-end data volume transfer time analytics","source":"SA WG5","contact":"Yizhi Yao","contact-id":66963,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 thanks SA WG2 for the LS on improved KPIs involving end-to-end data volume transfer time analytics. SA WG5 confirms that SA WG5 would like to provide support for the per UE measurements for the RAN part UL\/DL packet delay and UL\/DL packet delay between PSA_UPF and UE. SA WG5 is presently discussing the options (i.e., PM or MDT) to support these per UE measurements, and would be happy to inform SA WG2 when these per UE measurements will be supported by the SA WG5 specs, targeted for the Rel-18 timeframe. Action: SA WG5 requests SA WG2 to take the information mentioned above into consideration.","secretary_remarks":"Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23570,"status":"postponed","reservation_date":"2023-09-20 14:39:57","uploaded":"2023-09-20 15:06:31","revisionof":"","revisedto":"S2-2311941","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-235454","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310133.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310135","title":"LS from SA WG5: LS on charging aspects of AI\/ML traffic","source":"SA WG5","contact":"Maryse Gardella","contact-id":68914,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 thanks SA WG2 for their LS on charging aspects of AI\/ML. SA WG5 can confirm the need, for the purpose of end user charging as well as AI\/ML service provider charging, to differentiate between the application usage traffic and the AI\/ML traffic the application is associated to . SA WG5 assumes the existing Flow Based Charging (FBC) can be used, to apply differentiated charging for the AI\/ML traffic from any other applications traffic, under appropriate data flow filters and dedicated AI\/ML rating group (i.e. charging key) or rating group + service-id. However, to the best of SA WG5 knowledge, there is no capability specified, to allow on a per application basis, charging differentiation between the application usage and the AI\/ML traffic the application is associated to. SA WG5 would like SA WG2 to confirm whether this capability on a per application basis as mentioned above is not specified. In such a case, SA WG5 would like SA WG2 to consider SA WG5 charging need expressed above during their work on AI\/ML. In addition, SA WG5 has identified the particular charging requirement i.e. 'The 5G system shall be able to support collection of charging information for a group of UEs, e.g. UEs of a AI\/ML FL group' in clause 9.1 of TS 22.261, and understands this is associated to Assistance to AI\/ML Operations in the Application Layer introduced in 5G system per clause 5.46 of SA WG2 TS 23.501. SA WG5 can confirm to SA WG2 the NEF charging framework specified under SA WG5 TS 32.254 'Exposure function northbound Application Program Interfaces (APIs) charging' may need to evolve for covering this particular charging requirement in the AI\/ML context, and also for addressing further charging requirements determined as relevant by SA WG5 for charging. Action: SA WG5 kindly asks SA WG2 to take the above information into account during their work on AI\/ML.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23310,"status":"postponed","reservation_date":"2023-09-20 14:39:57","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"S2-2311943","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1","lsoriginalls":"S5-235752","lsreply":"S2-2312039","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310135.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310137","title":"LS from SA WG5: Reply LS for LS on Multiple Trace\/MDT configurations","source":"SA WG5","contact":"Sivaramakrishnan Swaminathan","contact-id":92909,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank RAN WG3 for informing about the limitation in the NGRAN node for the mentioned scenario of multiple trace and MDT configurations. SA WG5 believes support of multiple configurations is beneficial, and would like to request RAN WG3 to investigate feasibility of forwarding all the multiple configurations to the target NG-RAN, e.g. in Rel-18.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22450,"status":"noted","reservation_date":"2023-09-20 14:39:57","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2","lsoriginalls":"S5-235775","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310137.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310139","title":"LS from SA WG5: Reply to LS on 3GPP work on energy efficiency","source":"SA WG5","contact":"Jean-Michel CORNILY","contact-id":96535,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 thanks SA WG4 for your Reply LS on 3GPP work on energy efficiency. SA WG5 would like to provide the following replies to SA WG4 questions: {. . .}","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22460,"status":"noted","reservation_date":"2023-09-20 14:39:57","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"TSG SA, SA WG1, SA WG2, SA WG3, SA WG6","lsoriginalls":"S5-235778","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310139.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310141","title":"LS from SA WG5: LS reply to LS from WSOLU to 3GPP SA5 - 5G charging architecture for wholesale scenarios","source":"SA WG5","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Information","abstract":"SA WG5 would like to thank GSMA WSOLU for their LS on 5G charging architecture for wholesale scenarios. SA WG5 has completed the first part of the work item on 5G roaming charging architecture for wholesale and retail within 3GPP Rel-17 timeframe, and are planning a second part, building on the work done on Rel-17, of the work within 3GPP Rel-18 timeframe.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22480,"status":"noted","reservation_date":"2023-09-20 14:39:57","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA WSOLU","Cc":"GSMA IDS, GSMA NG, SA WG2","lsoriginalls":"S5-235800","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310141.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310227","title":"R18 AIMLsys_clarification that flow description info is per UE","source":"Nokia, Nokia Shanghai Bell","contact":"Dongjoo Kim","contact-id":97472,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarifying the flow description information(s) is provided per UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23270,"status":"not treated","reservation_date":"2023-09-27 00:39:15","uploaded":"2023-09-27 00:57:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"AIMLsys"}],"crnumber":4457.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310227.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.9.2, 5.2.6.9.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310228","title":"[DRAFT] Reply LS on LS on clarification for list of UEs parameter handling","source":"Nokia, Nokia Shanghai Bell","contact":"Dongjoo Kim","contact-id":97472,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: -. Attachments: -","secretary_remarks":"Response to S2-2310103. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23240,"status":"noted","reservation_date":"2023-09-27 00:44:17","uploaded":"2023-09-27 00:57:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_AIMLsys"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310228.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310322","title":"[DRAFT] LS Reply on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","secretary_remarks":"Response to S2-2310084. Merged into S2-2311521","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22500,"status":"merged","reservation_date":"2023-09-27 13:28:58","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310322.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310323","title":"Correction on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add description the RAN may determine a dynamic value of 5G-AN PDB in UL direction for the QoS Flow Upon receiving the TSCAI but no dynamic value for the CN PDB for a QoS Flow from the SMF. Add TN Stream Identification Information for DataFrameSpecification and TN Stream Identification Information for mask-and-match in the set-request. Remove the note on additional parameters.","secretary_remarks":"Revised in parallel session to S2-2311522, merging S2-2310848.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22560,"status":"revised","reservation_date":"2023-09-27 13:28:58","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"S2-2311522, S2-2312291","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4955.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310323.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.28a.2, M.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310324","title":"Correction on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the description on not supporting TLs and change Step 11~13 to Conditional.","secretary_remarks":"Merged into S2-2311523.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22600,"status":"merged","reservation_date":"2023-09-27 13:28:59","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4470.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310324.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"F.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310361","title":"AMF discovery and subscription by TSCTSF for Time Synchronization Coverage Area","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Three new event filters are introduced for UE mobility on Area of Interest procedures: 'Do not propogate the event subscription to another AMF', 'Notify the consumer if an event is triggered by a UE having an ASTI subscription', 'Notify the consumer considering UE identify or DNN\/S-NSSAI'. These event filters may be provided by Namf_EventExposure_Subscribe service consumer, TSCTSF, together with Area Of Interest information.","secretary_remarks":"Merged into S2-2311524","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22750,"status":"merged","reservation_date":"2023-09-27 18:28:06","uploaded":"2023-09-29 20:34:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4959.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310361.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.3.4.4, 5.27.1.10","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310362","title":"AMF discovery and subscription by TSCTSF for Time Synchronization Coverage Area","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Three new event filters are introduced for UE mobility on Area of Interest procedures: 'Do not propogate the event subscription to another AMF', 'Notify the consumer if an event is triggered by a UE having an ASTI subscription', 'Notify the consumer considering UE identify or DNN\/S-NSSAI'. These event filters may be provided by Namf_EventExposure_Subscribe service consumer, TSCTSF, together with Area Of Interest information.","secretary_remarks":"Revised in parallel session to S2-2311525, merging S2-2311012, S2-2311087 and S2-2311066.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22760,"status":"revised","reservation_date":"2023-09-27 18:28:08","uploaded":"2023-09-29 20:34:08","revisionof":"","revisedto":"S2-2311525","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4477.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310362.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310374","title":"[DRAFT] Reply LS on EAC Mode Subscription Optimization","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS answering CT WG4 questions on AMF subscription to NSACF","secretary_remarks":"Response to S2-2310107. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23330,"status":"noted","reservation_date":"2023-09-27 19:00:32","uploaded":"2023-09-29 20:24:46","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"-","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310374.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310381","title":"[DRAFT] Reply LS on defining PIN ID format","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Provides SA WG2 view on the PIN ID format","secretary_remarks":"Response to S2-2310093. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23150,"status":"noted","reservation_date":"2023-09-27 19:18:42","uploaded":"2023-09-29 20:31:25","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310381.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310382","title":"PIN ID clarification","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the description of PIN ID to refer to TS 23.542.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23180,"status":"not treated","reservation_date":"2023-09-27 19:18:42","uploaded":"2023-09-29 20:31:25","revisionof":"","revisedto":"S2-2312166","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"PIN"}],"crnumber":4961.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310382.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310399","title":"Handling of eDRX with discontinous coverage","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that implementations can handle this by ensuring that the eDRX parameters are taking into account the coverage periods. There is already text on the MME may take unavailability periods into account, but no text that the UE may do the same when providing eDRX paramaters to the network.","secretary_remarks":"Revised to S2-2311238","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23550,"status":"revised","reservation_date":"2023-09-28 01:01:53","uploaded":"2023-09-29 20:28:45","revisionof":"","revisedto":"S2-2311238","release":"Rel-18","crspec":"23.401","crspecversion":"18.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3747.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310399.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310400","title":"[DRAFT] Reply LS on misalignment between PTW and Coverage Window","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper proposes a reply to RAN WG2 LS on misalignment between PTW and Coverage Window","secretary_remarks":"Response to S2-2310122. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23410,"status":"not treated","reservation_date":"2023-09-28 01:01:54","uploaded":"2023-09-29 20:28:45","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310400.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310436","title":"[DRAFT] Reply LS on defining PIN ID format","source":"vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG3, CT WG4. Attachments: -","secretary_remarks":"Response to S2-2310093. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23160,"status":"noted","reservation_date":"2023-09-28 05:27:15","uploaded":"2023-09-29 03:41:14","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310436.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310437","title":"Define PIN ID","source":"Vivo","contact":"Zhenhua Xie","contact-id":83004,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Define format of PIN ID","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23190,"status":"not treated","reservation_date":"2023-09-28 05:29:16","uploaded":"2023-09-29 03:41:14","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"PIN"}],"crnumber":4973.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310437.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.44.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310536","title":"[DRAFT] Reply LS on clarification for list of UEs parameter handling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on clarification for list of UEs parameter handling from CT WG3","secretary_remarks":"Response to S2-2310103. Revised in parallel session to S2-2311643.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23250,"status":"revised","reservation_date":"2023-09-28 09:39:03","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"S2-2311643","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"AIMLsys"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310536.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310537","title":"Clarification for list of UEs parameter handling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the following NOTE: NOTE 1: When a list of UE addresses is provided, the Flow description information is common for all UE addresses in the list, i.e., the Flow description information can only include the IP address and the port number of the application server (as well as the protocol information).","secretary_remarks":"Revised in parallel session to S2-2311644.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23280,"status":"revised","reservation_date":"2023-09-28 09:39:03","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"S2-2311644","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"AIMLsys"}],"crnumber":4490.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310537.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.6.9.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310563","title":"[DRAFT] Response LS to CT WG1 on the scope of LCS-SS messages transferred via the LCS user plane","source":"CATT","contact":"Xiaoxue Zhao","contact-id":97471,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: -. Attachments: -","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22960,"status":"not treated","reservation_date":"2023-09-28 09:56:31","uploaded":"2023-09-28 10:04:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310563.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310564","title":"Clarification on the supplementary service messages over user plane","source":"CATT","contact":"Xiaoxue Zhao","contact-id":97471,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification of supplementary service messages transferred over the user plane includes event reporting and others(i.e. MO-LR, event reporting, location privacy setting and so on).","secretary_remarks":"Merged into S2-2311639.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23010,"status":"merged","reservation_date":"2023-09-28 10:03:05","uploaded":"2023-09-28 10:04:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.3.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":446.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310564.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.18.1, 6.18.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310566","title":"Clarification and correction on multiple QoS Class Handling During Service Continuity from 5GS to EPS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify LMF determines whether or not provide the GMLC provided mapped QoS to UE based the access type allowed for the UE for event reporting for the mutiple QoS, but not perfom the mutiple QoS mapping or providng QoS Class to UE.","secretary_remarks":"Revised in parallel session to S2-2311641.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23060,"status":"revised","reservation_date":"2023-09-28 10:11:01","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"S2-2311641","release":"Rel-18","crspec":"23.273","crspecversion":"18.3.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":447.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310566.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.19.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310567","title":"[DRAFT] LS reply on Multiple QoS Class Handling During Service Continuity from 5GS to EPS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS reply on Multiple QoS Class Handling During Service Continuity from 5GS to EPS","secretary_remarks":"Response to S2-2310109. Revised in parallel session to S2-2311642.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23030,"status":"revised","reservation_date":"2023-09-28 10:11:02","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"S2-2311642","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310567.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310568","title":"Clarification on scope of LCS-SS message transferred via the LCS-UP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify in clause 5.10 to make sure only the event reporting message is in the scope of LCS-SS messages transferred via the user plane.","secretary_remarks":"Merged into S2-2311639.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22970,"status":"merged","reservation_date":"2023-09-28 10:11:02","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.3.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":448.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310568.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.10","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310569","title":"[DRAFT] LS reply on scope of LCS-SS message transferred via the LCS-UP","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS reply on scope of LCS-SS message transferred via the LCS-UP","secretary_remarks":"Response to S2-2310092. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22910,"status":"not treated","reservation_date":"2023-09-28 10:11:03","uploaded":"2023-09-28 14:28:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310569.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310622","title":"Discussion on support of QMC in SA WG2.","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses the supportive of QMC in SA WG2 for Rel-17 and Rel-18.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23500,"status":"not treated","reservation_date":"2023-09-28 13:34:04","uploaded":"2023-09-28 14:25:26","revisionof":"","revisedto":"S2-2313002, S2-2313003","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310622.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310623","title":"[DRAFT] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"Qualcomm Technologies Int","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2, SA WG5, SA WG3. Attachments: -","secretary_remarks":"Response to S2-2310127. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23480,"status":"not treated","reservation_date":"2023-09-28 13:36:27","uploaded":"2023-09-28 14:25:26","revisionof":"","revisedto":"S2-2313009","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_QoE_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310623.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310624","title":"Support of QMC configuration information","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Adding TS 28.405 as new reference in clause 2 - Adding a new clause about 5GS support QMC","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23510,"status":"not treated","reservation_date":"2023-09-28 13:41:08","uploaded":"2023-09-28 14:25:26","revisionof":"","revisedto":"S2-2312450","release":"Rel-17","crspec":"23.501","crspecversion":"17.10.0","workitem":[{"winame":"TEI18"},{"winame":" NR_QoE_enh-Core"}],"crnumber":4991.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310624.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2; 5.25.x (new clause)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310625","title":"Support of QMC configuration information","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: - Adding TS 28.405 as new reference in clause 2 - Adding a new clause about 5GS support QMC","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23520,"status":"not treated","reservation_date":"2023-09-28 13:44:09","uploaded":"2023-09-28 14:25:26","revisionof":"","revisedto":"S2-2312451","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TEI18"},{"winame":" NR_QoE_enh-Core"}],"crnumber":4992.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310625.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2; 5.25.x (new clause)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310626","title":"Support of QMC configuration information","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - adding TS 28.405 as a new reference in clause 2 - adding AMF provides QMC Configuration information to 5G-AN in N2 signalling in registration procedure in clause 4.2.2.2.2 - adding AMF provides QMC Configuration information to 5G-AN in N2 signalling in Service Request procedure in clause 4.2.3.2 - adding QMC Configuration information as UE subscription in clause 5.2.3.3.1","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23530,"status":"not treated","reservation_date":"2023-09-28 13:48:38","uploaded":"2023-09-28 14:25:26","revisionof":"","revisedto":"S2-2313012","release":"Rel-17","crspec":"23.502","crspecversion":"17.10.0","workitem":[{"winame":"TEI18"},{"winame":" NR_QoE_enh-Core"}],"crnumber":4495.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310626.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2; 4.2.2.2.2, 4.2.3.2, 5.2.3.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310632","title":"Support of QMC configuration information","source":"Qualcomm Incorporated","contact":"Juan Zhang","contact-id":73274,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: - adding TS 28.405 as a new reference in clause 2 - adding AMF provides QMC Configuration information to 5G-AN in N2 signalling in registration procedure in clause 4.2.2.2.2 - adding AMF provides QMC Configuration information to 5G-AN in N2 signalling in Service Request procedure in clause 4.2.3.2 - adding QMC Configuration information as UE subscription in clause 5.2.3.3.1","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23540,"status":"not treated","reservation_date":"2023-09-28 13:51:55","uploaded":"2023-09-28 14:25:26","revisionof":"","revisedto":"S2-2313015","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TEI18"},{"winame":" NR_QoE_enh-Core"}],"crnumber":4499.0,"crrevision":"","crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310632.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2; 4.2.2.2.2, 4.2.3.2, 5.2.3.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310637","title":"[DRAFT] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","secretary_remarks":"Response to S2-2310127. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23470,"status":"not treated","reservation_date":"2023-09-28 14:15:16","uploaded":"2023-09-29 06:21:28","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG5, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310637.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310740","title":"[DRAFT] Reply LS on QMC support in RRC_IDLE and RRC_INACTIVE","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"The LS informa that QoE measurement configuration information is feasible to be stored at the AMF.","secretary_remarks":"Response to S2-2310127. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23490,"status":"not treated","reservation_date":"2023-09-28 15:49:08","uploaded":"2023-09-29 20:35:28","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_QoE_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2, SA WG3, SA WG5","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310740.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310762","title":"[DRAFT] Reply LS on the scope of LCS-SS messages transferred via LCS user plane","source":"vivo","contact":"Amy Zhang","contact-id":96452,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4. Attachments: -","secretary_remarks":"Response to S2-2310092. Revised in parallel session to S2-2311640.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22920,"status":"revised","reservation_date":"2023-09-28 17:25:10","uploaded":"2023-09-29 08:36:41","revisionof":"","revisedto":"S2-2311640","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310762.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310763","title":"Discussion on the scope of LCS-SS messages transferred via the LCS user plane.","source":"Vivo","contact":"Amy Zhang","contact-id":96452,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution analyzes all kinds of LCS-SS messages and gives an ovewriew on the scope of messages via the user plane.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22980,"status":"noted","reservation_date":"2023-09-28 17:25:10","uploaded":"2023-09-29 08:36:41","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310763.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310764","title":"Clarification on the scope of LCS-SS messages transferred via the LCS user plane","source":"Vivo","contact":"Amy Zhang","contact-id":96452,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the above scope of LCS-SS message via LCS-UP.","secretary_remarks":"Revised in parallel session to S2-2311639, merging S2-2310568 and S2-2310564.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22990,"status":"revised","reservation_date":"2023-09-28 17:25:10","uploaded":"2023-09-29 08:36:41","revisionof":"","revisedto":"S2-2311639","release":"Rel-18","crspec":"23.273","crspecversion":"18.3.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":451.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310764.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.10, 6.18.1, 6.18.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310782","title":"[DRAFT] LS reply on defining PIN ID format from CT1 WG","source":"Google Inc.","contact":"Ellen C. Liao","contact-id":96126,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4. CC: CT WG3. Attachments: -","secretary_remarks":"Response to S2-2310093. Revised in parallel session to S2-2311520.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23120,"status":"revised","reservation_date":"2023-09-28 18:58:52","uploaded":"2023-09-29 19:45:54","revisionof":"","revisedto":"S2-2311520","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310782.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310834","title":"[DRAFT] Reply LS on PIN ID","source":"Qualcomm Incorporated","contact":"Kefeng ZHANG","contact-id":91388,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 suggests CT WG1 to consider the principles in defining the format of PIN ID.","secretary_remarks":"Response to S2-2310093. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23170,"status":"noted","reservation_date":"2023-09-29 02:20:55","uploaded":"2023-09-29 02:41:29","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"Reply LS on PIN ID","Cc":"CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310834.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310835","title":"[DRAFT] Reply LS on UICC configuration for IMS Data Channel","source":"Qualcomm Incorporated","contact":"Kefeng ZHANG","contact-id":91388,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 provides clarification for UICC configuration in CT WG6.","secretary_remarks":"Response to S2-2310087. Revised in parallel session to S2-2311638, merging S2-2310921.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22860,"status":"revised","reservation_date":"2023-09-29 02:29:23","uploaded":"2023-09-29 02:41:30","revisionof":"","revisedto":"S2-2311638","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG6","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310835.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310837","title":"Update of PIN ID descriptor in URSP","source":"Qualcomm Incorporated","contact":"Kefeng ZHANG","contact-id":91388,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add information of the associated AF identifier in the traffic descriptor component for PIN ID to make sure the PIN ID is unique in a PLMN.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23200,"status":"not treated","reservation_date":"2023-09-29 02:36:10","uploaded":"2023-09-29 02:41:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.503","crspecversion":"18.3.0","workitem":[{"winame":"PIN"}],"crnumber":1178.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310837.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.6.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310847","title":"[DRAFT] Reply LS on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"Nokia, Nokia Shanghai Bell","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","secretary_remarks":"Response to S2-2310084. Revised in parallel session to S2-2311521, merging S2-2310322.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22510,"status":"revised","reservation_date":"2023-09-29 05:27:43","uploaded":"2023-09-29 09:38:36","revisionof":"","revisedto":"S2-2311521","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310847.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310848","title":"Corrections on KI#5 TL-Container parameters and TL-Container exchange","source":"Nokia, Nokia Shanghai Bell","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the two F-TEID associations in the get response in clause 5.28a.2, add the missing MacAdress as parameter of the InterfaceConfiguration in Table M.2-1, indent the respective headlines TN Stream Identification Information for DataFrameSpecification , and InterfaceConfiguration of End Station in Table M.2-1, and to remove the IEEE802-MacAddresses and IEEE802-VlanTag parameters from DataFrameSpecification in Table M.2-1. In section 5.28a.1, the NG-RAN providing the dynamic value of AN PDB to the SMF\/CUC in a response to the QoS Flow request, to adapt EarliestTransmitOffset is removed. Proposed to include the Stream ID and Add \/ Delete indication based on the feedback from CT.","secretary_remarks":"Merged into S2-2311522.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22550,"status":"merged","reservation_date":"2023-09-29 05:27:56","uploaded":"2023-09-29 09:38:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5020.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310848.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 5.27.2.5.2, 5.28a, 5.28a.1, 5.28a.2, Annex M.1, Annex M.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310849","title":"Updates and clarifications related to PDU Session procedures in context to get and set messages for KI#5","source":"Nokia, Nokia Shanghai Bell","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Revise information to be stored by the SMF\/CUC after receiving the get response. Update the PDU Session modification procedure to handle the release of streams in the TSN enabled TN. Update the PDU session release procedure to allow the exchange of Set-Request\/Response TL-Container","secretary_remarks":"Revised in parallel session to S2-2311523, merging S2-2310324.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22580,"status":"revised","reservation_date":"2023-09-29 05:27:57","uploaded":"2023-09-29 09:38:36","revisionof":"","revisedto":"S2-2311523","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4519.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310849.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.2.2.1, 4.3.3.2, 4.3.4.2, Annex F.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310863","title":"Clarification on the support for AMF discovery at the TSCTSF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding options 1) and 2) to the related TSCTSF discovering AMF in clauses 5.27.1.10 and 6.2.29.","secretary_remarks":"Revised in parallel session to S2-2311524, merging S2-2311011, S2-2311086, S2-2311063 and S2-2310361.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22720,"status":"revised","reservation_date":"2023-09-29 06:50:19","uploaded":"2023-09-29 12:04:52","revisionof":"","revisedto":"S2-2311524","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5024.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310863.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310864","title":"Discussion on Event ID in SIB .","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the broadcast of Event ID in SIB.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22810,"status":"not treated","reservation_date":"2023-09-29 06:50:20","uploaded":"2023-09-29 12:04:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310864.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310909","title":"[DRAFT] Response LS On EAC Mode Subscription Optimization","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Response LS On EAC Mode Subscription Optimization","secretary_remarks":"Response to S2-2310107. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23340,"status":"noted","reservation_date":"2023-09-29 08:22:19","uploaded":"2023-09-29 12:44:38","revisionof":"","revisedto":"S2-2312319","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TEI18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310909.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310921","title":"[DRAFT] Reply LS on UICC configuration for IMS Data Channel","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on UICC configuration for IMS Data Channel to CT WG6 incoming LS C6-230469","secretary_remarks":"Response to S2-2310087. Merged into S2-2311638","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22890,"status":"merged","reservation_date":"2023-09-29 08:37:56","uploaded":"2023-09-29 11:52:05","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310921.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310940","title":"[DRAFT] LS Reply on misalignment between PTW and Coverage Window","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN WG2 that eDRX and DisCo is already handled by the MME\/AMF.","secretary_remarks":"Response to S2-2310122. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23420,"status":"not treated","reservation_date":"2023-09-29 08:58:59","uploaded":"2023-09-29 13:11:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310940.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310984","title":"[DRAFT] LS Response on EAC Mode Subscription Optimization","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: -. Attachments: -","secretary_remarks":"Response to S2-2310107. Revised in parallel session to S2-2311645.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23350,"status":"revised","reservation_date":"2023-09-29 10:08:14","uploaded":"2023-09-29 10:35:45","revisionof":"","revisedto":"S2-2311645","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310984.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311004","title":"Solution update on user plane positioning","source":"Huawei","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposal 1: Convert the EN It is stage 3 to check and decide the protocol used by LMF to notify UE through the known UE IP address. to a NOTE: User Plane protocol (LCS-UPP) to support generic transport between the UE and the LMF is defined in TS 24.572. Proposal 2: In clause 6.18.1, step 7 Clarify the LMF may retrive the UE IP address by invoking SMF eventexposure service.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23090,"status":"postponed","reservation_date":"2023-09-29 10:36:57","uploaded":"2023-09-29 14:03:42","revisionof":"","revisedto":"S2-2313068","release":"Rel-18","crspec":"23.273","crspecversion":"18.3.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":452.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311004.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.18.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311008","title":"[DRAFT] LS reply on Event ID broadcast in SIB9","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: -. Attachments: -","secretary_remarks":"Response to S2-2310120. Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22800,"status":"postponed","reservation_date":"2023-09-29 10:37:00","uploaded":"2023-09-29 14:03:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311008.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311009","title":"Clarifications of Event ID broadcast in SIB9","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the descriptions and terminology in TS 23.501 for consistency and clarification. Moving the definition of event ID from bullet to a general place for clarification.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22820,"status":"not treated","reservation_date":"2023-09-29 10:37:00","uploaded":"2023-09-29 14:03:42","revisionof":"","revisedto":"S2-2313075","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5039.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311009.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.27.1.12","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311010","title":"[DRAFT] Reply LS on Proposed method for AMF discovery and subscription by the TSCTSF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: -. Attachments: -","secretary_remarks":"Response to S2-2310111. Revised in parallel session to S2-2311526, merging S2-2311085.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22620,"status":"revised","reservation_date":"2023-09-29 10:37:00","uploaded":"2023-09-29 14:03:42","revisionof":"","revisedto":"S2-2311526","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311010.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311011","title":"Update description for AMF discovery and subscription by the TSCTSF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correction of the AMF discovery and subscription in 5.27.1.10.","secretary_remarks":"Merged into S2-2311524","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22660,"status":"merged","reservation_date":"2023-09-29 10:37:00","uploaded":"2023-09-29 14:03:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5040.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311011.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":" 5.27.1.10","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311012","title":"Solution update for AMF discovery and subscription by the TSCTSF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Correct the AMF discovery and subscription and add the conditions for selecting different methods of AMF discovery in 4.15.9.4 and 4.15.9.3.2. Enhance the NRF based AMF discovery and subscription in 4.15.9.4. Clarify the new indication and enhancement of Namf_EventExposure in 5.2.2.3.2","secretary_remarks":"Merged into S2-2311525","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22670,"status":"merged","reservation_date":"2023-09-29 10:37:01","uploaded":"2023-09-29 14:03:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4531.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311012.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.9.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311022","title":"DP on misalignment between PTW and Satellite coverage window.","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"discussion","for":"Discussion","abstract":"Discusses the issue and solution of the misalignment between PTW and Coverage Window.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23440,"status":"not treated","reservation_date":"2023-09-29 11:10:41","uploaded":"2023-09-29 13:38:15","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311022.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311023","title":"[DRAFT] Reply LS on misalignment between PTW and Coverage Window","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: -. Attachments: -","secretary_remarks":"Response to S2-2310122. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23450,"status":"not treated","reservation_date":"2023-09-29 11:10:41","uploaded":"2023-09-29 13:38:15","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GSAT_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311023.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311063","title":"AMF discovery and subscription by the TSCTSF","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.3.4.4, if the target of the Namf_EventExposure Subscribe request is Any UE, the request may include a list of applicable UEs that limits the subscription to apply only to the UEs in the list. In clauses 5.27.1.10 and 5.27.1.12, the TSCTSF may include the list of applicable UEs into the subscribe request.","secretary_remarks":"Merged into S2-2311524","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22700,"status":"merged","reservation_date":"2023-09-29 13:02:34","uploaded":"2023-09-29 15:14:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5045.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311063.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.3.4.4, 5.27.1.10, 5.27.1.12","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311066","title":"AMF discovery and subscription by the TSCTSF","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 5.2.2.3.2, if the target of the Namf_EventExposure Subscribe request is Any UE, the request may include a list of applicable UEs that limits the subscription to apply only to the UEs in the list. In clauses 4.15.9.3.2 and 4.15.9.4, clarify that the AMF discovery is not done on UE basis. In clause 4.15.9.5.1, describe the use of Parameter Type = RAN timing synchronization status change event.","secretary_remarks":"Merged into S2-2311525","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22710,"status":"merged","reservation_date":"2023-09-29 13:08:41","uploaded":"2023-09-29 15:14:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4534.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311066.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.9.3.2, 4.15.9.4, 4.15.9.5.1, 5.2.2.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311071","title":"Broadcasting the Event ID","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The gNB will always broadcast an Event ID in the reference report ID. The reference report ID consist of Event threshold indicator, Event ID and the scope. If any of the pre-configured thresholds are exceeded in gNB, the gNB sets the Event threshold indicator in the reference report ID, otherwise it is not set. The UE reconnection indication includes a threshold indicator. If the threshold indicator is included into the UE reconnection indication, To enable Scenario 2), if the AMF receives the clock quality detail level = metrics from TSCTSF or UDM, the AMF sets the purpose = metrics when the AMF configures the UE reconnection indication to the UE. In addition, clause 5.27.1.8 is corrected by removing the condition of ASTI service; the TSCTSF provides the clock quality reporting control information to AMF also in case of (g)PTP service.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22830,"status":"not treated","reservation_date":"2023-09-29 13:15:14","uploaded":"2023-09-29 15:14:55","revisionof":"","revisedto":"S2-2312392","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5049.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311071.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.27.1.8, 5.27.1.12","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311073","title":"Broadcasting the Event ID","source":"NTT DOCOMO","contact":"Jari Mutikainen","contact-id":38346,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In clause 4.15.9.5.2, add a reference to clause 5.27.1.12 in TS 23.501 on the details when and how the NG-RAN broadcasts the reference report ID, and how the UE reacts upon it. Remove the duplicate description from clause 4.15.9.5.2. In clauses 4.2.2.2.2 and 4.15.9.4, the UE reconnection indication may include a threshold indicator. If the clock quality detail level received by the AMF is set to 'acceptable\/not acceptable', the AMF includes a threshold indicator into the UE reconnection indication. Clarify how the TSCTSF determines whether the clock status report from a RAN node is for clock failure or recovery.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22840,"status":"not treated","reservation_date":"2023-09-29 13:21:57","uploaded":"2023-09-29 15:14:55","revisionof":"","revisedto":"S2-2312397","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4536.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311073.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.2.2.2.2, 4.15.9.4, 4.15.9.5.1, 4.15.9.5.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311085","title":"Reply LS on Proposed method for AMF discovery and subscription by the TSCTSF","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a Reply LS on Proposed method for AMF discovery and subscription by the TSCTSF","secretary_remarks":"Response to S2-2310111. Merged into S2-2311526.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22650,"status":"merged","reservation_date":"2023-09-29 13:43:17","uploaded":"2023-09-29 14:45:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311085.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311086","title":"Clarification on the AMF determination for the coverage area based time sync service","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the option that the TSCTSF determine the serving AMF for each of the targeted UE(s).","secretary_remarks":"Merged into S2-2311524","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22680,"status":"merged","reservation_date":"2023-09-29 13:43:17","uploaded":"2023-09-29 14:45:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5052.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311086.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.27.1.10","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311087","title":"Clarification on the AMF determination for the coverage area based time sync service","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the option that the TSCTSF determine the serving AMF for each of the targeted UE(s).","secretary_remarks":"Merged into S2-2311525","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22690,"status":"merged","reservation_date":"2023-09-29 13:43:18","uploaded":"2023-09-29 14:45:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4538.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311087.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.9.3.2, 4.15.9.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311185","title":"Feature Synchronization of User Plane","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Synchronize the SA WG2 specification with the UP progress in CT WG1.","secretary_remarks":"Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23100,"status":"postponed","reservation_date":"2023-09-29 17:04:32","uploaded":"2023-09-29 17:30:20","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.3.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":460.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311185.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 3.2, 4.3.8, 4.3.7, 4.3.12, 5.1, 6.X, 8.3.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311198","title":"[DRAFT] Reply LS on misalignment between PTW and Coverage Window","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Replies to LS S2-2310122","secretary_remarks":"Response to S2-2310122. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23430,"status":"not treated","reservation_date":"2023-09-29 17:36:11","uploaded":"2023-09-29 19:06:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311198.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311238","title":"Handling of eDRX with discontinous coverage","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that implementations can handle this by ensuring that the eDRX parameters are taking into account the coverage periods. There is already text on the MME may take unavailability periods into account, but no text that the UE may do the same when providing eDRX paramaters to the network.","secretary_remarks":"Revision of S2-2310399. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23560,"status":"not treated","reservation_date":"2023-09-29 20:41:37","uploaded":"2023-09-29 20:43:57","revisionof":"S2-2310399","revisedto":"","release":"Rel-18","crspec":"23.401","crspecversion":"18.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3747.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311238.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.13.8.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311520","title":"[DRAFT] LS reply on defining PIN ID format from CT1 WG","source":"Google Inc.","contact":"Ellen C. Liao","contact-id":96126,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4. CC: CT WG3. Attachments: -","secretary_remarks":"Revision of S2-2310782. Revised in parallel session to S2-2311776.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23130,"status":"revised","reservation_date":"2023-11-10 04:17:27","uploaded":"2023-10-16 11:31:14","revisionof":"S2-2310782","revisedto":"S2-2311776","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG3, CT WG4, CT WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311520.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311521","title":"[DRAFT] Reply LS on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"Nokia, Nokia Shanghai Bell","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","secretary_remarks":"Revision of S2-2310847, merging S2-2310322. Revised in parallel session to S2-2311883.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22520,"status":"revised","reservation_date":"2023-11-10 04:17:27","uploaded":"2023-10-16 11:31:14","revisionof":"S2-2310847","revisedto":"S2-2311883","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311521.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311522","title":"Correction on Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add DataFrameSpecification and TN Stream Identification Information for mask-and-match in the set-request. Remove the note on additional parameters. Update the reference to IEEE Std P802.1Qdj based on latest progress. Refer to IEEE 902.1Q for DataFrameSpecification and InterfaceConfiguration. Add an EN to further discuss the details in InterfaceConfiguration. Clarify get request happens in PDU Session Establishment while set request happens in PDU Session Modification\/Release.","secretary_remarks":"Revision of S2-2310323, merging S2-2310848. Endorsed as a basis for further work. Revised at S2#160 in S2-2312746 and S2-2312291","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22570,"status":"revised","reservation_date":"2023-11-10 04:17:27","uploaded":"2023-10-16 11:31:14","revisionof":"S2-2310323","revisedto":"S2-2312746","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4955.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311522.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311523","title":"Updates and clarifications related to PDU Session procedures in context to get and set messages for KI#5","source":"Nokia, Nokia Shanghai Bell","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Revise information to be stored by the SMF\/CUC after receiving the get response. Update the PDU Session modification procedure to handle the release of streams in the TSN enabled TN. Update the PDU session release procedure to allow the exchange of Set-Request\/Response TL-Container","secretary_remarks":"Revision of S2-2310849, merging S2-2310324. Endorsed in parallel session as a basis for further work. Endorsed as a basis for further work. Revised at S2#160 in S2-2312753","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22590,"status":"revised","reservation_date":"2023-11-10 04:17:28","uploaded":"2023-10-16 11:31:14","revisionof":"S2-2310849","revisedto":"S2-2312753, S2-2312869","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4519.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311523.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311524","title":"Clarification on the support for AMF discovery at the TSCTSF","source":"Nokia, Nokia Shanghai Bell","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding options 1) and 2) to the related TSCTSF discovering AMF in clauses 5.27.1.10 and 6.2.29.","secretary_remarks":"Revision of S2-2310863, merging S2-2311011, S2-2311086, S2-2311063 and S2-2310361. Revised in parallel session to S2-2311778.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22730,"status":"revised","reservation_date":"2023-11-10 04:17:29","uploaded":"2023-10-16 11:31:14","revisionof":"S2-2310863","revisedto":"S2-2311778","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5024.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311524.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311525","title":"AMF discovery and subscription by TSCTSF for Time Synchronization Coverage Area","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Three new event filters are introduced for UE mobility on Area of Interest procedures: 'Do not propogate the event subscription to another AMF', 'Notify the consumer if an event is triggered by a UE having an ASTI subscription', 'Notify the consumer considering UE identify or DNN\/S-NSSAI'. These event filters may be provided by Namf_EventExposure_Subscribe service consumer, TSCTSF, together with Area Of Interest information.","secretary_remarks":"Revision of S2-2310362, merging S2-2311012, S2-2311087 and S2-2311066. Revised in parallel session to S2-2311779.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22770,"status":"revised","reservation_date":"2023-11-10 04:17:30","uploaded":"2023-10-16 11:31:15","revisionof":"S2-2310362","revisedto":"S2-2311779","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4477.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311525.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311526","title":"[DRAFT] Reply LS on Proposed method for AMF discovery and subscription by the TSCTSF","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: -. Attachments: -","secretary_remarks":"Revision of S2-2311010, merging S2-2311085. Revised in parallel session to S2-2311780.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22630,"status":"revised","reservation_date":"2023-11-10 04:17:31","uploaded":"2023-10-16 11:31:15","revisionof":"S2-2311010","revisedto":"S2-2311780","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311526.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311638","title":"[DRAFT] Reply LS on UICC configuration for IMS Data Channel","source":"Qualcomm Incorporated","contact":"Kefeng ZHANG","contact-id":91388,"tdoctype":"LS out","for":"Approval","abstract":"SA WG2 provides clarification for UICC configuration in CT WG6.","secretary_remarks":"Revision of S2-2310835, merging S2-2310921. Revised in parallel session to S2-2311773.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22870,"status":"revised","reservation_date":"2023-10-16 08:39:06","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310835","revisedto":"S2-2311773","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG6","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311638.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311639","title":"Clarification on the scope of LCS-SS messages transferred via the LCS user plane","source":"Vivo, CATT, Huawei, HiSilicon","contact":"Amy Zhang","contact-id":96452,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the above scope of LCS-SS message via LCS-UP.","secretary_remarks":"Revision of S2-2310764, merging S2-2310568 and S2-2310564. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23000,"status":"agreed","reservation_date":"2023-10-16 08:39:06","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310764","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.3.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":451.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-231246","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311639.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311640","title":"[DRAFT] Reply LS on the scope of LCS-SS messages transferred via LCS user plane","source":"vivo","contact":"Amy Zhang","contact-id":96452,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4. Attachments: -","secretary_remarks":"Revision of S2-2310762. Revised in parallel session to S2-2311774.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22930,"status":"revised","reservation_date":"2023-10-16 08:39:07","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310762","revisedto":"S2-2311774","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311640.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311641","title":"Clarification and correction on multiple QoS Class Handling During Service Continuity from 5GS to EPS","source":"Huawei, HiSilicon, Samsung","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify LMF determines whether or not provide the GMLC provided mapped QoS to UE based the access type allowed for the UE for event reporting for the mutiple QoS, but not perfom the mutiple QoS mapping or providng QoS Class to UE.","secretary_remarks":"Revision of S2-2310566. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23070,"status":"agreed","reservation_date":"2023-10-16 08:39:07","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310566","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.3.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":447.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-231246","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311641.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311642","title":"[DRAFT] LS reply on Multiple QoS Class Handling During Service Continuity from 5GS to EPS","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS reply on Multiple QoS Class Handling During Service Continuity from 5GS to EPS","secretary_remarks":"Revision of S2-2310567. Revised in parallel session to S2-2311775.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23040,"status":"revised","reservation_date":"2023-10-16 08:39:08","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310567","revisedto":"S2-2311775","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311642.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311643","title":"Reply LS on clarification for list of UEs parameter handling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on clarification for list of UEs parameter handling from CT WG3","secretary_remarks":"Revision of S2-2310536. Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23260,"status":"postponed","reservation_date":"2023-10-16 08:39:08","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310536","revisedto":"S2-2312276","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"AIMLsys"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311643.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311644","title":"Clarification for list of UEs parameter handling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the following NOTE: NOTE 1: When a list of UE addresses is provided, the Flow description information is common for all UE addresses in the list, i.e., the Flow description information can only include the IP address and the port number of the application server (as well as the protocol information).","secretary_remarks":"Revision of S2-2310537. Revised in parallel session to S2-2311777.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23290,"status":"revised","reservation_date":"2023-10-16 08:39:08","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310537","revisedto":"S2-2311777, S2-2312277","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"AIMLsys"}],"crnumber":4490.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311644.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311645","title":"[DRAFT] LS Response on EAC Mode Subscription Optimization","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: -. Attachments: -","secretary_remarks":"Revision of S2-2310984. Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23360,"status":"postponed","reservation_date":"2023-10-16 08:39:08","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310984","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eNS_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311645.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311773","title":"Reply LS on UICC configuration for IMS Data Channel","source":"SA WG2","contact":"Kefeng ZHANG","contact-id":91388,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG6. CC: CT WG1","secretary_remarks":"Revision of S2-2311638. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22880,"status":"approved","reservation_date":"2023-10-16 08:39:49","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311638","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NG_RTC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310087","lsto":"CT WG6","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311773.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311774","title":"Reply LS on the scope of LCS-SS messages transferred via LCS user plane","source":"SA WG2","contact":"Amy Zhang","contact-id":96452,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4. Attachments: -","secretary_remarks":"Revision of S2-2311640. Revised to S2-2311915.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22940,"status":"revised","reservation_date":"2023-10-16 08:39:49","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311640","revisedto":"S2-2311915","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311774.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311775","title":"LS reply on Multiple QoS Class Handling During Service Continuity from 5GS to EPS","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: CT WG1. Attachments: S2-2311641 (23.273 CR0447)","secretary_remarks":"Revision of S2-2311642. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23050,"status":"approved","reservation_date":"2023-10-16 08:39:49","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311642","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310109","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311775.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311776","title":"Reply LS on defining PIN ID format","source":"SA WG2","contact":"Ellen C. Liao","contact-id":96126,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG3, CT WG4, SA WG6.","secretary_remarks":"Revision of S2-2311520. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23140,"status":"approved","reservation_date":"2023-10-16 08:39:49","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311520","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310093","lsto":"CT WG1, CT WG3, CT WG4, SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311776.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311777","title":"Clarification for list of UEs parameter handling","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add the following NOTE: NOTE 1: When a list of UE addresses is provided, the Flow description information is common for all UE addresses in the list, i.e., the Flow description information can only include the IP address and the port number of the application server (as well as the protocol information).","secretary_remarks":"Revision of S2-2311644. WITHDRAWN","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23300,"status":"withdrawn","reservation_date":"2023-10-16 08:39:50","uploaded":null,"revisionof":"S2-2311644","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"AIMLsys"}],"crnumber":4490.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311778","title":"Clarification on the support for AMF discovery at the TSCTSF","source":"Nokia, Nokia Shanghai Bell, NTT DOCOMO","contact":"Devaki Chandramouli","contact-id":68275,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding options 1) and 2) to the related TSCTSF discovering AMF in clauses 5.27.1.10 and 6.2.29.","secretary_remarks":"Revision of S2-2311524. Endorsed in parallel session as a basis for further work. Endorsed as a basis for further work. Revised at S2#160 in S2-2312065","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22740,"status":"revised","reservation_date":"2023-10-16 08:39:50","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311524","revisedto":"S2-2312065, S2-2312381, S2-2312757","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":5024.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311778.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311779","title":"AMF discovery and subscription by TSCTSF for Time Synchronization Coverage Area","source":"Ericsson, Nokia, Nokia Shanghai Bell, NTT DoCoMo, Huawei, ZTE","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Three new event filters are introduced for UE mobility on Area of Interest procedures: 'Do not propogate the event subscription to another AMF', 'Notify the consumer if an event is triggered by a UE having an ASTI subscription', 'Notify the consumer considering UE identify or DNN\/S-NSSAI'. These event filters may be provided by Namf_EventExposure_Subscribe service consumer, TSCTSF, together with Area Of Interest information.","secretary_remarks":"Revision of S2-2311525. Endorsed in parallel session as a basis for further work. Endorsed as a basis for further work. Revised at S2#160 in S2-2312382","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22780,"status":"revised","reservation_date":"2023-10-16 08:39:51","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311525","revisedto":"S2-2312382, S2-2312463, S2-2312766","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TRS_URLLC"}],"crnumber":4477.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311779.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311780","title":"Reply LS on Proposed method for AMF discovery and subscription by the TSCTSF","source":"SA WG2","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: -. Attachments: -","secretary_remarks":"Revision of S2-2311526. Postponed in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22640,"status":"postponed","reservation_date":"2023-10-16 08:39:52","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311526","revisedto":"S2-2313074","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311780.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311883","title":"Reply LS Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"SA WG2","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","secretary_remarks":"Revision of S2-2311521. Revised in parallel session to S2-2311886.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22530,"status":"revised","reservation_date":"2023-10-16 08:40:16","uploaded":"2023-10-16 11:31:17","revisionof":"S2-2311521","revisedto":"S2-2311886","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311883.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311886","title":"Reply LS Support of Time Sensitive Networking (TSN) enabled Transport Network (TN)","source":"SA WG2","contact":"Srinivas Garikipati","contact-id":100437,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4. CC: RAN WG3. Attachments: S2-2311522 (23.501 CR 4955), S2-2311523 (23.502 CR 4519)","secretary_remarks":"Revision of S2-2311883. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22540,"status":"approved","reservation_date":"2023-10-16 08:40:18","uploaded":"2023-10-16 11:31:17","revisionof":"S2-2311883","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310084","lsto":"CT WG4","Cc":"RAN WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311886.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311915","title":"Reply LS on the scope of LCS-SS messages transferred via the LCS user plane","source":"SA WG2","contact":"Amy Zhang","contact-id":96452,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4. Attachments: S2-2311639 (TS 23.273 CR0451)","secretary_remarks":"Revision of S2-2311774. This was approved.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":22950,"status":"approved","reservation_date":"2023-10-16 08:40:45","uploaded":"2023-10-16 11:31:17","revisionof":"S2-2311774","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310092","lsto":"CT WG1","Cc":"CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311915.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]