[{"name":"S2-2403866","title":"LS from RAN WG3: RAN feedback during handover","source":"RAN WG3","contact":"Feng Han","contact-id":73581,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 kindly inform SA WG2 that the TRS_URLLC-NR-Core WI is completed in RAN WG3. RAN WG3 would also like to inform SA WG2 that RAN WG3 made the following decisions on the RAN feedback during handover: - For proactive RAN feedback, the proactive parameters (including the Burst Arrival Time Window and Periodicity Range) are not signalled during handover, i.e. not provided by the source gNB to the target gNB during the Xn based handover, and are not provided by the AMF to the target gNB during the NG based handover. - For reactive RAN feedback, the reactive parameter (i.e. Capability for BAT Adaptation) is signalled from the source gNB to the target gNB. Action: RAN WG3 kindly asks SA WG2 to take the above into account.","secretary_remarks":"Revision of postponed S2-2401852 from S2#161. Response drafted in S2-2404089. Final response in S2-2405535","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14150,"status":"replied to","reservation_date":"2024-03-26 09:41:09","uploaded":"2024-03-26 09:50:50","revisionof":"S2-2401855","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R3-238038","lsreply":"S2-2405535, S2-2405535","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403866.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403871","title":"LS from CT WG1: LS on LCS user plane connection binding to the UE","source":"CT WG1","contact":"Sunghoon Kim","contact-id":87382,"tdoctype":"LS in","for":"Action","abstract":"As part of the work on 5G_eLCS_Ph3, CT WG1 has specified protocol solutions for location service over user plane as defined in new TS 24.572: Step 1) UPP-CM procedure during which the LMF provides the user plane connection information to the UE. Step 2) The UE performs user plane connection establishment with the LMF (i.e., TLS connection) based on the information received from Step 1. Step 3) LCS-UPP procedure to transfer location service messages between the UE and the LMF. CT WG1 has found following issues: 1. After the TLS connection is established, the UE and the LMF initiate LPP or LCS-SS procedure. For the LMF-initiated case, given that multiple UEs are served by the LMF and multiple TLS connections are active, the LMF needs to determine a TLS connection for the target UE. However, it has not been specified how to link the association between the TLS connection and the UE, e.g., how the LMF knows which TLS connection is for the UE who has received the UPP-CM command message. If the TLS connection can be linked to the wrong UE then there could be a risk of location related data from one UE which is sent to another UE. 2. Once the binding of the TLS connection to the UE is done, if there is a new LCS service request (e.g., MT-LR) for the same UE, the AMF invokes Nlmf_location_determinelocation service operation to the LMF. However, it has not been specified how the LMF associates the LCS service request to the TLS connection of the UE. In this case, the LMF cannot determine which TLS connection can be used for the LCS service request. Therefore, the LMF cannot reuse the TLS connection of this UE for subsequent LCS service request(s). Action: CT WG1 kindly asks SA WG2 to provide a resolution for above-described issues and feedback to CT WG1.","secretary_remarks":"Responses drafted in S2-2404044, S2-2404131, S2-2404166, S2-2404664, S2-2404713, S2-2404773, S2-2404868. Final response in S2-2405797","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14360,"status":"replied to","reservation_date":"2024-03-26 09:41:10","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C1-241722","lsreply":"S2-2405797, S2-2405797","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403871.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403872","title":"LS from CT WG1: LS on identifiers of 5G ProSe end UEs for 5G ProSe UE-to-UE relay discovery","source":"CT WG1","contact":"Xiaoyan Duan","contact-id":85499,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 has the following understanding regarding the identifier(s) of the 5G ProSe end UE(s) in 5G ProSe UE-to-UE relay discovery procedures: The application layer ID(s) of the 5G ProSe end UE(s) are the identifiers included in the protected direct discovery set, for the following reasons: - the direct discovery set is for end-to-end discovery between the 5G ProSe end UEs; - the 5G ProSe end UE cannot know the provisioned\/configured user info ID(s) of other 5G ProSe end UE(s) for 5G ProSe UE-to-UE relay discovery, e.g. if the user info ID is provided by the PCF, provisioned in the ME or configured in the UICC. Based on the above understanding, the provisioned\/configured user info ID in the 5G ProSe end UE for 5G ProSe UE-to-UE relay discovery is not needed and CT WG1 has decided to remove it. Action: CT WG1 kindly asks SA WG2 and SA WG3 to take the above information into consideration, and update their specifications accordingly or provide feedback if any.","secretary_remarks":"Response drafted in S2-2404661. Postponed in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14230,"status":"postponed","reservation_date":"2024-03-26 09:41:10","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"S2-2405843","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"C1-241787","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403872.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403882","title":"LS from CT WG3: Reply LS on XRM and TSC QoS requirements","source":"CT WG3","contact":"Parthasarathi Ravindran","contact-id":68434,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 thanks SA WG2 for QoS Monitoring parameters for XR service answers. {. . .} CT WG3 would like to ask SA WG2: Question 1: Besides the Periodicity and N6 Jitter Information, are there any other parameters included in TSCAI applicable to XR service? i.e., which are the TSCAC parameters as defined in TS 23.501 table 5.27.2-2 applicable to XR service? Question 2: Can the bold parameters be included in one message which is used to request XR service and Time sensitive communication? Action: CT WG3 kindly request SA WG2 to answer the above question.","secretary_remarks":"Responses drafted in S2-2404022, S2-2404150, S2-2404459, S2-2404648, S2-2404776, S2-2404938. Final response in S2-2405495","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14620,"status":"replied to","reservation_date":"2024-03-26 09:41:10","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C3-241716","lsreply":"S2-2405495, S2-2405495","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403882.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403886","title":"LS from RAN WG2: Reply LS on coverage condition for Ranging\/Sidelink Positioning","source":"RAN WG2","contact":"Yu Pan","contact-id":87666,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed the SA WG2 s question in the LS and provides the following answer: Question 1: Is there any potential RAN WG2 impact to support network based or network assisted SL positioning as defined in the 23.273 clause 6.20 when the target UE is in coverage while some of the SL reference UE(s) are out of coverage or does not have connection to a LMF? RAN WG2 s answer: there is no any stage-3 RAN WG2 impact to support partial coverage scenarios in network assisted SL positioning. Question 2: Is there any potential RAN WG2 impact to support UE only SL positioning as defined in 23.586 clause 6.8 when the target UE is out of coverage while some of the SL reference\/Located UE(s) are in coverage of a network that supports Ranging\/Sidelink Positioning? RAN WG2 s answer: there is no any stage-3 RAN WG2 impact to support partial coverage scenarios in UE only SL positioning. In addition, RAN WG2 have determined to remove the NOTE excluding partial coverage in stage 2. Action: RAN WG2 kindly requests SA WG2 to take the above information into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14970,"status":"noted","reservation_date":"2024-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG3","lsoriginalls":"R2-2401629","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403886.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403890","title":"LS from RAN WG2: LS on U2U relay selection","source":"RAN WG2","contact":"Gy\u00f6rgy Wolfner","contact-id":68507,"tdoctype":"LS in","for":"Action","abstract":"In Rel-18 as a part of the NR_SL_relay_enh-Core work item RAN WG2 has specified triggers for U2U relay selection and reselection in 5.8.17.3 of TS 38.331. Triggering U2U relay selection enables to move a connection from a direct PC5 connection to a U2U relay connection and triggering U2U relay reselection enables to move a connection from one U2U relay to another U2U relay. Some companies in RAN WG2 think that the corresponding SA WG2 specification in clause 6.7.4.1 of TS 23.304 only covers the U2U relay reselection, while the procedure for U2U relay selection that enables to move a connection from a direct PC5 connection to a U2U relay connection has not been specified. RAN WG2 would like to ask the following questions from SA WG2: Question 1: Do SA WG2 specifications cover the relay selection that enables to move a connection from a direct PC5 connection to a U2U relay connection? If the answer for question 1 is NO, then: Question 2: Can SA WG2 extend SA WG2 specifications with a relay selection mechanism that enables to move a connection from a direct PC5 connection to a U2U relay connection? Action: RAN WG2 respectfully asks SA WG2 to reply to the above questions and update their specifications if necessary.","secretary_remarks":"Responses drafted in S2-2404317, S2-2404675. Final response in S2-2405531","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14270,"status":"replied to","reservation_date":"2024-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"R2-2401916","lsreply":"S2-2405531, S2-2405531","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403890.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403891","title":"LS from RAN WG2: Reply LS to SA2 on L2ID and user info","source":"RAN WG2","contact":"Jianhua Liu","contact-id":96314,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG2 for the reply LS on L2ID and User Info for L2 based U2U. In regards of SA WG2 reply, RAN WG2 discussed which Remote UE ID should be used in AS layer when assigning Local ID and related interactions between AS layer and ProSe layer, and achieved the following agreements. Agreements: There are no concurrent PC5 connection setup procedures between a single source remote UE and different target remote UEs via the same relay UE. RAN WG2 will not capture this in a spec and it is left to SA WG2 to decide if there is something to capture. Before receiving Layer-2 ID from AS layer, source Remote UE does not trigger PC5 connection setup procedure towards another target Remote UE via the same relay UE. During Local ID assignment, Relay UE indicates to the source Remote UE layer-2 ID of the target Remote UE ID in RRCReconfigurationSidelink. Source Remote UE indicates layer-2 ID of the target Remote UE to ProSe layer. Source Remote UE AS layer maintains Layer-2 ID and local ID mapping per relay UE. RAN WG2 respectfully asks SA WG2 and CT WG1 to take the above agreements into account, and provide feedback if having any concerns. Action: RAN WG2 respectfully asks SA WG2 to take the above information into account, and provide feedback if having any concerns.","secretary_remarks":"Response drafted in S2-2404319. Final response in S2-2405379","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14190,"status":"replied to","reservation_date":"2024-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG1","Cc":"","lsoriginalls":"R2-2401918","lsreply":"S2-2405379, S2-2405379","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403891.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403905","title":"LS from SA WG3: Reply LS on Ranging\/SL Positioning service exposure security and privacy check","source":"SA WG3","contact":"Longhua Guo","contact-id":80179,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for the LS on Ranging\/SL Positioning service exposure security and privacy check. SA WG3 would like to bring SA WG2 attention that SA WG3 performed a similar WID in Rel-18 SNAAPPY for authorization of UE-originated API invocation related to SA WG6 SNAAPP WID on resource owner authorization. No normative security work for accessing resources from a UE different from resource owner s UE were specified in Rel-18. In addition, the authentication of UE acting as API invoker towards NEF is not supported. Action: SA WG2 is kindly requested to take the above information into account.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14960,"status":"noted","reservation_date":"2024-03-26 09:41:11","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG1, SA WG6","lsoriginalls":"S3-240836","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403905.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403909","title":"LS from SA WG3: LS on Issues related Analytics context transfer between AnLF(s)","source":"SA WG3","contact":"Wu Rong","contact-id":49499,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 kindly ask SA WG2 to consider the following information. SA WG3 noticed that in procedure of Transfer of analytics context and analytics subscription, as description in clause 6.1B of TS23.288, the Source AnLF may send the address (e.g. URL or FQDN) of Model file directly to the consumer(Target AnLF). Optionally, file address(es) of the trained ML model(s), which is included only when the source NWDAF itself provides the trained ML model(s) for the analytics subscription(s) for which the related analytics context is requested. A potential security issue is that the Target AnLF is not authorized by the NRF, since it uses Nnwdaf_AnalyticsInfo_ContextTransfer service, not the Nnwdaf_MLModelProvision service. The source AnLF could send the Model file address to the unauthorized AnLF. Regarding this, SA WG3 suggests that if SA WG2 wants Model information to be transferred, another information is needed to be transferred from source NWDAF to target NWDAF, but remove the possibility to send Model file address. If the target NWDAF then wants to get the address of the model that the source NWDAF uses, it shall use the Nnwdaf_MLModelProvision service to request the model address from the MTLF model provider. Action: SA WG2 is kindly requested to take the above information into account.","secretary_remarks":"Responses drafted in S2-2404001, S2-2404070, S2-2404898. Postponed in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14720,"status":"postponed","reservation_date":"2024-03-26 09:41:12","uploaded":"2024-03-26 18:43:10","revisionof":"","revisedto":"S2-2405849","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S3-240912","lsreply":"S2-2406490","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403909.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2403915","title":"LS from TSG SA: LS on removing Ranging\/SL Positioning service exposure to Client UE through 5GC","source":"TSG SA","contact":"Yang Shen","contact-id":68465,"tdoctype":"LS in","for":"Action","abstract":"TSG SA plenary has agreed to remove the feature of Ranging\/SL Positioning service exposure to Client UE through 5GC for Rel-18 in both TS 23.586 and TS 33.533, and all the related solution developments will not be considered for Rel-18. Additionally, TSG SA plenary also agreed to define UE Ranging\/SL Positioning privacy profile in TS 33.533. For details, please check the attached 3 CRs. Action: SA kindly asks SA WG2, SA WG3, CT WG1 and CT WG4 to take above TSG SA agreements into account to update related specifications.","secretary_remarks":"Response drafted in S2-2404129. Postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14830,"status":"postponed","reservation_date":"2024-03-26 09:41:12","uploaded":"2024-04-02 12:11:27","revisionof":"","revisedto":"S2-2405850","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, CT WG1, CT WG4","Cc":"","lsoriginalls":"SP-240497","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2403915.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404001","title":"[DRAFT] Reply LS on issues related to analytics context transfer between AnLF(s)","source":"CATT","contact":"Xiaoyan Duan","contact-id":85499,"tdoctype":"LS out","for":"Approval","abstract":"Draft reply LS to SA WG3 on issues related to analytics context transfer between AnLF(s).","secretary_remarks":"Response to S2-2403909 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14790,"status":"not treated","reservation_date":"2024-03-29 08:08:06","uploaded":"2024-04-05 08:29:26","revisionof":"","revisedto":"S2-2405979","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNA_Ph3_SEC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404001.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404002","title":"Clarification on analytics transfer","source":"CATT","contact":"Xiaoyan Duan","contact-id":85499,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the source NWDAF provides ML model file address to the target NWDAF only if the source NWDAF contains MTLF and produces the ML model by itself for the analytics being transferred. Clarify that the source NWDAF can decide to send the file address(es) of the trained ML Model(s) for the analytics to the target NWDAF, if both the NWDAFs belong to the same vendor, based on configuration, or based on the NF consumer information (such as Vendor ID) of the target NWDAF if received before or during the analytics subscription\/context transfer procedure.","secretary_remarks":"Merged into S2-2405801.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14780,"status":"merged","reservation_date":"2024-03-29 08:08:08","uploaded":"2024-04-05 08:29:26","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.288","crspecversion":"18.5.0","workitem":[{"winame":"eNA_Ph3"}],"crnumber":1078.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404002.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1B.2.2, 6.1B.3, 6.1B.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404022","title":"[DRAFT] LS reply on CT WG3 Reply LS on XRM and TSC QoS requirements","source":"China Mobile","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"LS reply on CT WG3 Reply LS on XRM and TSC QoS requirements","secretary_remarks":"Response to S2-2403882. Revised in parallel session to S2-2405495.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14630,"status":"revised","reservation_date":"2024-03-30 03:36:48","uploaded":"2024-04-05 17:43:13","revisionof":"","revisedto":"S2-2405495","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404022.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404043","title":"Discussion on user plane positioning binding issue","source":"vivo","contact":"Hang Yu","contact-id":93029,"tdoctype":"discussion","for":"Discussion","abstract":"-","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14480,"status":"not treated","reservation_date":"2024-01-04 10:06:09","uploaded":"2024-04-05 10:53:12","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_162_Changsha_2024-04\/Docs\/S2-2404043.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404044","title":"[DRAFT] LS reply on LCS user plane connection binding to the UE","source":"vivo","contact":"Hang Yu","contact-id":93029,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4. Attachments: TS 23.273 CR#0515","secretary_remarks":"Response to S2-2403871 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14380,"status":"not treated","reservation_date":"2024-01-04 10:06:09","uploaded":"2024-04-05 10:53:12","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_162_Changsha_2024-04\/Docs\/S2-2404044.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404045","title":"Resolution of LCS-UP binding issue","source":"Vivo","contact":"Hang Yu","contact-id":93029,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update TS 23.273 to capture the above points.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14490,"status":"not treated","reservation_date":"2024-01-04 10:06:09","uploaded":"2024-04-05 10:53:12","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":515.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404045.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.7, 5.1, 5.10, 6.18.0, 6.18.1, 6.18.2, 8.3.2.2, 8.3.2.7, 8.3.2.9","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404070","title":"[DRAFT] Reply LS on Issues related to Analytics context transfer between AnLF(s)","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS reply to SA WG3 LS regarding model sharing between AnLFs during Analytics context transfer","secretary_remarks":"Response to S2-2403909. Merged into S2-2405383.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14800,"status":"merged","reservation_date":"2024-02-04 06:52:55","uploaded":"2024-04-05 11:46:52","revisionof":"","revisedto":"S2-2406490","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNA_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404070.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404071","title":"Correction of ML Model sharing in the scenario of Analytics context transfer","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing the ML Model address from the contents of Analytics context Adding ML Model Identifier in the ML model related information in the Analytics context information. Adding ML Model Identifier as an optional input parameter of Nnwdaf_MLModelProvision\/Info service request","secretary_remarks":"Revised in parallel session, merging S2-2404903, to S2-2405382.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14730,"status":"revised","reservation_date":"2024-02-04 06:52:55","uploaded":"2024-04-05 11:46:52","revisionof":"","revisedto":"S2-2405382","release":"Rel-18","crspec":"23.288","crspecversion":"18.5.0","workitem":[{"winame":"eNA_Ph3"}],"crnumber":1081.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404071.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.2A.2, 6.1B.4, 7.5.2, 7.6.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404089","title":"[DRAFT] LS Reply on RAN feedback during handover","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to reply the LS on RAN feedback during handover (R3-238038)","secretary_remarks":"Response to S2-2403866. Revised in parallel session to S2-2405493.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14160,"status":"revised","reservation_date":"2024-02-04 09:29:17","uploaded":"2024-04-05 11:46:52","revisionof":"","revisedto":"S2-2405493","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404089.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404102","title":"Update on function services for Ranging","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The content on Positioning service exposure to client UE through 5GC is removed.","secretary_remarks":"Confirm Specification Number - CR states 23.273!. If 23.273, then new CR number is required! Merged into S2-2405385.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14860,"status":"merged","reservation_date":"2024-02-04 10:12:48","uploaded":"2024-04-05 07:52:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":130.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404102.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404111","title":"Removal of Ranging exposure service to Client UE through 5GC","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove from the subscription that a UE is allowed to use the Ranging\/SL Positioning exposure service (UE can receive Ranging\/SL positioning result related to other UE subscribers). Remove Client UE identification from the GMLC service, as GMLC will not support exposure\/privacy checking of a Client UE as the feature is removed from Rel-18.","secretary_remarks":"Revised in parallel session, merging S2-2404869 and S2-2404102, to S2-2405385.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14870,"status":"revised","reservation_date":"2024-02-04 12:45:35","uploaded":"2024-04-05 13:34:29","revisionof":"","revisedto":"S2-2405385","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":516.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404111.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"7.1, 8.4.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404112","title":"Support for UE Ranging\/SL Positioning privacy profile","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds support of the new UE Ranging\/SL Positioning privacy profile specified in TS 33.533. New Ranging\/SL Positioning Privacy Indication provisioning GMLC\/UDM support of new privacy profile Clarification when the different privacy profile is used (LCS, Ranging\/local).","secretary_remarks":"This was postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":15020,"status":"postponed","reservation_date":"2024-02-04 12:55:18","uploaded":"2024-04-05 13:34:29","revisionof":"","revisedto":"S2-2405991","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":517.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404112.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.2, 4.1, 4.3.3, 4.3.6, 4.3.9, 5.4.1, 5.4.2.x (new), 5.4.3a (new), 5.4.5, 5.4.6, 6.12.1, 6.20.1, 6.20.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404128","title":"Support for UE Ranging\/SL Positioning privacy profile","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adds support of the new UE Ranging\/SL Positioning privacy profile specified in TS 33.533. New Ranging\/SL Positioning Privacy Indication provisioning UDR\/UDM related services to support the new Ranging\/Sidelink privacy data.","secretary_remarks":"This was postponed in parallel session.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":15030,"status":"postponed","reservation_date":"2024-02-04 13:00:17","uploaded":"2024-04-05 13:34:29","revisionof":"","revisedto":"S2-2405992","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":4775.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404128.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"2, 4.15.6.2, 5.2.3.3.1, 5.2.3.6.1, 5.2.3.6.2, 5.2.12.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404129","title":"[DRAFT] Reply LS on removing Ranging\/SL Positioning service exposure to Client UE through 5GC","source":"Sony","contact":"Lars Nord","contact-id":82070,"tdoctype":"LS out","for":"Approval","abstract":"Provide CT WG1 and CT WG4 with information of changes needed to remove the feature of Ranging\/SL Positioning service exposure to Client UE through 5GC and to define the UE Ranging\/SL Positioning privacy profile.","secretary_remarks":"Response to S2-2403915. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14910,"status":"noted","reservation_date":"2024-02-04 13:09:55","uploaded":"2024-04-05 13:34:56","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"Ranging_SL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"TSG SA, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404129.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404131","title":"[DRAFT] Reply LS on LCS user plane connection binding to the UE","source":"Xiaomi EV Technology","contact":"Yang Shen","contact-id":88433,"tdoctype":"LS out","for":"Approval","abstract":"Draft Reply LS on LCS user plane connection binding to the UE","secretary_remarks":"Response to S2-2403871 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14390,"status":"not treated","reservation_date":"2024-02-04 15:58:53","uploaded":"2024-04-05 19:31:40","revisionof":"","revisedto":"","release":"","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_162_Changsha_2024-04\/Docs\/S2-2404131.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404132","title":"LCS user plane connection binding to the UE","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Option 1 is reflected in the 1st to 4th changes, Option 2 is reflected in the 5th to 6th changes, and Option 3 is reflected in the 7th to 8th changes.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14500,"status":"not treated","reservation_date":"2024-02-04 16:06:40","uploaded":"2024-04-05 19:31:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":518.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404132.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404133","title":"Discussion on LCS user plane connection binding to the UE.","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"discussion","for":"Approval","abstract":"This contribution is an evaluation on the solutions of LCS user plane connection binding to the UE with the proposed way forward.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14510,"status":"not treated","reservation_date":"2024-02-04 16:09:28","uploaded":"2024-04-05 19:31:40","revisionof":"","revisedto":"","release":"","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_162_Changsha_2024-04\/Docs\/S2-2404133.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404150","title":"[DRAFT] Reply LS on XRM and TSC QoS requirements","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on XRM and TSC QoS requirements","secretary_remarks":"Response to S2-2403882 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14680,"status":"not treated","reservation_date":"2024-03-04 06:41:23","uploaded":"2024-04-05 11:46:52","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404150.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404166","title":"[DRAFT] LS reply on LCS user plane connection binding to the UE","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS reply on LCS user plane connection binding to the UE","secretary_remarks":"Response to S2-2403871 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14400,"status":"not treated","reservation_date":"2024-03-04 07:44:09","uploaded":"2024-04-05 07:52:36","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_162_Changsha_2024-04\/Docs\/S2-2404166.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404167","title":"Support of LCS user plane connection binding to the UE","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update LMF and UE initiated User Plane Connection procedure to add a temporary LCS-UP UE ID included in the user plane positioning information sent to UE; Update Nlmf_Location_DetermineLocation service operation to add UE identifier (GPSI, SUPI) as an optional input parameter. AMF functionality description is also updated to clarify AMF should provide the UE identifier to LMF in the request if UE supports user plane positioning.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14520,"status":"not treated","reservation_date":"2024-03-04 07:44:09","uploaded":"2024-04-05 07:52:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":519.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404167.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.3.7, 6.18.1, 6.18.2, 8.3.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404168","title":"Discussion on LCS user plane connection binding to the UE.","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"discussion","for":"Information","abstract":"To solve issues spotted by CT WG1 about LCS user plane connection binding to the UE, this paper provides a principle on a way forward.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14530,"status":"not treated","reservation_date":"2024-03-04 07:44:10","uploaded":"2024-04-05 07:52:36","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_162_Changsha_2024-04\/Docs\/S2-2404168.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404317","title":"[DRAFT] Reply LS on U2U relay selection","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2403890\/R2-2401916","secretary_remarks":"Response to S2-2403890. Revised in parallel session, merging S2-2404675 and S2-2405002, to S2-2405499.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14280,"status":"revised","reservation_date":"2024-04-04 05:28:53","uploaded":"2024-04-05 12:53:36","revisionof":"","revisedto":"S2-2405499","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_relay_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_162_Changsha_2024-04\/Docs\/S2-2404317.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404318","title":"Clarification on triggering PC5 connection setup procedure via same U2U Relay","source":"OPPO, LG Electronics, Apple, Samsung, CATT","contact":"Fei Lu","contact-id":87831,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is clarified that there are no concurrent PC5 connection setup procedures between a single source End UE and different target End UEs via the same relay UE.","secretary_remarks":"Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14200,"status":"agreed","reservation_date":"2024-04-04 05:28:53","uploaded":"2024-04-05 12:53:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.5.1","workitem":[{"winame":"5G_ProSe_Ph2"},{"winame":" NR_SL_relay_enh-Core"}],"crnumber":435.0,"crrevision":"","crcategory":"F","tsg_crp":"SP-240588","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404318.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.7.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404319","title":"[DRAFT] Reply LS on L2ID and user info for L2 based U2U","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2403891\/R2-2401918","secretary_remarks":"Response to S2-2403891. Revised in parallel session to S2-2405379.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14210,"status":"revised","reservation_date":"2024-04-04 05:28:53","uploaded":"2024-04-05 12:53:36","revisionof":"","revisedto":"S2-2405379","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_relay_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404319.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404459","title":"[DRAFT] Reply LS on XRM and TSC QoS requirements","source":"OPPO","contact":"Boren Guo","contact-id":100775,"tdoctype":"LS out","for":"Approval","abstract":"Draft Reply LS on XRM and TSC QoS requirements","secretary_remarks":"Response to S2-2403882 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14690,"status":"not treated","reservation_date":"2024-04-04 17:31:14","uploaded":"2024-04-05 15:32:03","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404459.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404648","title":"[DRAFT] Reply LS on XRM and TSC QoS requirements","source":"SAMSUNG","contact":"Youngkyo Baek","contact-id":46395,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3","secretary_remarks":"Response to S2-2403882 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14700,"status":"not treated","reservation_date":"2024-05-04 09:00:41","uploaded":"2024-04-05 09:06:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404648.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404660","title":"Alignment with stage 3 specification on configured End UE User Info ID and Direct discovery set","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the provisioned\/configured User Info ID of End UE and clarify Application Layer ID should be used. Clarify that the Direct Discovery Set includes a list of protected User Info IDs.","secretary_remarks":"Revised in parallel session to S2-2405494 (withdrawn). Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14240,"status":"noted","reservation_date":"2024-05-04 09:06:11","uploaded":"2024-04-05 09:18:47","revisionof":"","revisedto":"S2-2405494","release":"Rel-18","crspec":"23.304","crspecversion":"18.5.1","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":438.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404660.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 5.1.5.1, 6.3.2.4.2, 6.3.2.4.3, 6.3.2.4.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404661","title":"[DRAFT] Reply LS on identifiers of 5G ProSe end UEs for 5G ProSe UE-to-UE relay discovery","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on identifiers of 5G ProSe end UEs for 5G ProSe UE-to-UE relay discovery","secretary_remarks":"Response to S2-2403872. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14260,"status":"noted","reservation_date":"2024-05-04 09:06:11","uploaded":"2024-04-05 09:18:47","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404661.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404663","title":"Update about the UE role in PC-5 service exposure scenario","source":"OPPO","contact":"Yaxin Wang","contact-id":99608,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 5.6.2.2, 5.11, 6.7.1.1, 6.8 to align that UE1 can only be the target UE.","secretary_remarks":"Revised in parallel session to S2-2405386.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14920,"status":"revised","reservation_date":"2024-05-04 09:14:40","uploaded":"2024-04-05 10:40:10","revisionof":"","revisedto":"S2-2405386","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":131.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404663.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.6.2.2, 5.11, 6.7.1.1, 6.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404664","title":"[DRAFT] Reply LS to LS on LCS user plane connection binding to the UE","source":"OPPO","contact":"Yaxin Wang","contact-id":99608,"tdoctype":"LS out","for":"Approval","abstract":"Draft reply LS to LS on LCS user plane connection binding to the UE (S2-2403871\/ C1-241722)","secretary_remarks":"Response to S2-2403871 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14410,"status":"not treated","reservation_date":"2024-05-04 09:14:41","uploaded":"2024-04-05 10:40:10","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_162_Changsha_2024-04\/Docs\/S2-2404664.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404665","title":"User plane positioning update for user plane connection binding","source":"OPPO","contact":"Yaxin Wang","contact-id":99608,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 6.18.1 and 6.18.2 to support the LMF and UE side context synchonization for user plane connection binding. Update clause 8.3.2.2 and 8.3.2.9 accordingly.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14540,"status":"not treated","reservation_date":"2024-05-04 09:14:41","uploaded":"2024-04-05 10:40:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":520.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404665.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.18.1, 6.18.2, 8.3.2.2, 8.3.2.9","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404675","title":"[DRAFT] Reply to LS on U2U relay selection","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN WG2 to inform then about resuing U2U relay re-selection for U2U relay selection.","secretary_remarks":"Response to S2-2403890. Merged into S2-2405499.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14310,"status":"merged","reservation_date":"2024-05-04 09:21:00","uploaded":"2024-04-05 13:57:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"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_162_Changsha_2024-04\/Docs\/S2-2404675.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404676","title":"Update on U2U Relay selection","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add a new clause to support the 5G ProSe UE-to-UE Relay reselection when the end UEs have direct PC5 connection.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14350,"status":"noted","reservation_date":"2024-05-04 09:21:00","uploaded":"2024-04-05 13:57:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.5.1","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":439.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404676.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.7.x.1 (new), 6.7.x.2 (new)","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404712","title":"Add the binding mechanism between LCS user plane connection and the UE","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF always includes the SUPI or GPSI in the Nlmf_Location_DetermineLocation Request if the target UE supports the capability of user plane positioning using LCS-UPP. The LMF allocates binding ID for target UE and includes the binding ID in the user plane information sent to UE. After the secure user plane connection is established, the UE sends binding message including the binding ID to the LMF. The LMF stores the mapping between SUPI\/GPSI and user plane connection.","secretary_remarks":"Revised in parallel session to S2-2405380.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14550,"status":"revised","reservation_date":"2024-05-04 10:15:54","uploaded":"2024-04-05 10:41:28","revisionof":"","revisedto":"S2-2405380","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":521.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404712.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.2, 6.2, 6.18.1, 6.18.2, 8.3.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404713","title":"[DRAFT] LS reply on LCS user plane connection binding to the UE","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to send the LS reply to S2-2403871 (C1-241722)","secretary_remarks":"Response to S2-2403871. Revised in parallel session to S2-2405381.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14420,"status":"revised","reservation_date":"2024-05-04 10:15:56","uploaded":"2024-04-05 10:41:28","revisionof":"","revisedto":"S2-2405381","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_162_Changsha_2024-04\/Docs\/S2-2404713.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404773","title":"[DRAFT] Reply LS on LCS user plane connection binding to the UE","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a Reply LS on LCS user plane connection binding to the UE","secretary_remarks":"Response to S2-2403871 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14460,"status":"not treated","reservation_date":"2024-05-04 11:24:32","uploaded":"2024-04-05 12:38:05","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404773.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404774","title":"Clarification on the session binding in the U-plane","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An LCS-UP session id is used to bind the user plane connection with the UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14580,"status":"not treated","reservation_date":"2024-05-04 11:24:32","uploaded":"2024-04-05 12:38:05","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":523.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404774.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.18.0, 6.18.1, 6.18.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404775","title":"Clarification on the partial coverage issue","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove partial coverage condition in the Located UE and SL Reference UE Discovery and selection.","secretary_remarks":"Revised in parallel session, merging S2-2404889, to S2-2405497.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14980,"status":"revised","reservation_date":"2024-05-04 11:24:33","uploaded":"2024-04-05 12:38:05","revisionof":"","revisedto":"S2-2405497","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":132.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404775.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.2.2, 5.2.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404776","title":"[DRAFT] Reply LS on XRM and TSC QoS requirements","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"LS out","for":"Approval","abstract":"Proposes a Reply LS on XRM and TSC QoS requirements","secretary_remarks":"Response to S2-2403882 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14710,"status":"not treated","reservation_date":"2024-05-04 11:24:33","uploaded":"2024-04-05 12:38:05","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404776.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404777","title":"Clarification on the TSCAI\/TSCAC parameters for XR","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify which parameters in the TSCAC\/TSCAI can be applied to XR.","secretary_remarks":"Revised in parallel session to S2-2405496.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14650,"status":"revised","reservation_date":"2024-05-04 11:24:33","uploaded":"2024-04-05 12:38:05","revisionof":"","revisedto":"S2-2405496","release":"Rel-18","crspec":"23.501","crspecversion":"18.5.0","workitem":[{"winame":"XRM"}],"crnumber":5391.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404777.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.27.2.1, 5.37.8.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404857","title":"Correction on LCS user plane connection binding to the UE","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update procedures in clauses of 6.18 to include the LCS-UP connection ID to help binding the connection to a UE. Add the LCS-UP connection ID as an optional input parameter to the Nlmf_Location_DetermineLocation and Nlmf_Location_UPNotify service operations and as an optional output parameter to the Nlmf_Location_UPConfig service operation.","secretary_remarks":"Check WI Code: Requested 5G_eLCS_Ph3. CR States: eLCS_Ph3! Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14590,"status":"not treated","reservation_date":"2024-05-04 14:05:05","uploaded":"2024-04-05 19:34:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":524.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404857.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404865","title":"Addition of LCS-UP connection ID for transfer of a supplementary services LCS message","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Add an LCS-UP connection ID as an optional input parameter for an Namf_Communication_N1MessageNotify service operation.","secretary_remarks":"Check WI Code: Requested 5G_eLCS_Ph3. CR States: eLCS_Ph3! Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14600,"status":"not treated","reservation_date":"2024-05-04 14:13:23","uploaded":"2024-04-05 19:34:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.502","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":4803.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404865.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404868","title":"[DRAFT] Reply LS on LCS user plane connection binding to the UE","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on LCS user plane connection binding to the UE.","secretary_remarks":"Response to S2-2403871 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14470,"status":"not treated","reservation_date":"2024-05-04 14:19:27","uploaded":"2024-04-05 19:34:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"CT WG4, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404868.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404869","title":"Removal of Ranging\/SL Positioning exposure service from the LCS Mobile Originated data for a UE Subscriber","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Ranging\/SL Positioning exposure service is removed from the LCS Mobile Originated data for a UE Subscriber.","secretary_remarks":"Merged into S2-2405385.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14840,"status":"merged","reservation_date":"2024-05-04 14:20:57","uploaded":"2024-04-05 19:31:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":525.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404869.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"7.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404874","title":"Discussion on LCS user plane connection binding to UE","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"discussion","for":"Discussion","abstract":"Discussion on LCS user plane connection binding to UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14610,"status":"not treated","reservation_date":"2024-05-04 14:25:17","uploaded":"2024-04-05 19:34:55","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_162_Changsha_2024-04\/Docs\/S2-2404874.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404888","title":"Removal of Ngmlc_Location_ProvideRanging service operation","source":"Xiaomi","contact":"Yang Shen","contact-id":88433,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Ngmlc_Location_ProvideRanging service operation is removed. More parameters are added based on procedures defined in clause 6.20 of TS 23.273.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14850,"status":"noted","reservation_date":"2024-05-04 14:32:08","uploaded":"2024-04-05 19:31:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":526.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404888.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"8.4.1, 8.4.2.2, 8.4.2.8, 8.3.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404889","title":"Correction on UE coverage status support","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the selection of reference UE and other operation constrains regarding the Reference UE's coverage status.","secretary_remarks":"Merged into S2-2405497.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":15010,"status":"merged","reservation_date":"2024-05-04 14:35:14","uploaded":"2024-04-05 19:34:55","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":133.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404889.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.4, 5.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404898","title":"[DRAFT] Reply LS on Issues related Analytics context transfer between AnLF(s)","source":"Samsung Electronics France SA","contact":"Jungshin Park","contact-id":65750,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Issues related Analytics context transfer between AnLF(s)","secretary_remarks":"Response to S2-2403909. Revised in parallel session, merging S2-2404070, to S2-2405383.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14810,"status":"revised","reservation_date":"2024-05-04 14:57:09","uploaded":"2024-04-05 16:33:18","revisionof":"","revisedto":"S2-2405383, S2-2406338","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNA_Ph3_SEC"},{"winame":" eNA_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404898.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404903","title":"Removal of a security issues on Analytics context transfer","source":"Samsung","contact":"Jungshin Park","contact-id":65750,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to remove the possibility to send Model file address from Nnwdaf_AnalyticsInfo_ContextTransfer service.","secretary_remarks":"Merged into S2-2405382.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14770,"status":"merged","reservation_date":"2024-05-04 15:08:38","uploaded":"2024-04-05 16:33:18","revisionof":"","revisedto":"S2-2406343","release":"Rel-18","crspec":"23.288","crspecversion":"18.5.0","workitem":[{"winame":"eNA_Ph3"}],"crnumber":1085.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404903.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1B.2.2, 6.1B.3, 6.1B.4","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2404938","title":"[DRAFT] Reply LS on clarification for Issues on QoS Monitoring parameters for XR service","source":"Nokia","contact":"Georgios Gkellas","contact-id":68310,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on clarification for Issues on QoS Monitoring parameters for XR service","secretary_remarks":"Response to S2-2403882 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14670,"status":"not treated","reservation_date":"2024-05-04 16:29:27","uploaded":"2024-04-05 16:56:29","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"XRM"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2404938.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405001","title":"U2U Direct and Indirect NOTE","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added a NOTE to address the concern from RAN WG2","secretary_remarks":"Revised in parallel session to S2-2405498 (withdrawn). Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14330,"status":"noted","reservation_date":"2024-05-04 23:41:43","uploaded":"2024-04-05 23:56:16","revisionof":"","revisedto":"S2-2405498","release":"Rel-18","crspec":"23.304","crspecversion":"18.5.1","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":441.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405001.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.4.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405002","title":"[DRAFT] Reply LS of S2-2403890_R2-2401916","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2403890_R2-2401916","secretary_remarks":"Response to S2-2403890. Merged into S2-2405499.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14320,"status":"merged","reservation_date":"2024-05-04 23:41:44","uploaded":"2024-04-05 23:56:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"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_162_Changsha_2024-04\/Docs\/S2-2405002.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405261","title":"Results of drafting session on Contribution summary and way forward proposal for LCS user plane connection binding to the UE","source":"Drafting Rapporteur (CATT)","contact":"Ming Ai","contact-id":40862,"tdoctype":"discussion","for":"Information","abstract":"Results of Drafting session on Generic Rel-18 LSs. Way forward proposal: Summary and supporting company of mechanism to solve Q1 Alternative#1 : LMF allocates a new ID and includes the new ID in the User Plane Information to UE. After the user plane conne","secretary_remarks":"Created at meeting. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14370,"status":"noted","reservation_date":"2024-04-22 09:38:31","uploaded":"2024-04-22 10:01:20","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405261.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405379","title":"Reply LS on L2ID and user info for L2 based U2U","source":"SA WG2","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2, CT WG1. Attachments: TS 23.304 CR0435","secretary_remarks":"Revision of S2-2404319. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14220,"status":"approved","reservation_date":"2024-04-22 09:39:29","uploaded":"2024-04-22 10:01:16","revisionof":"S2-2404319","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_relay_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2403891","lsto":"RAN WG2, CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405379.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405380","title":"Add the binding mechanism between LCS user plane connection and the UE","source":"CATT,Huawei, HiSilicon,vivo,Qualcomm Incorporated,ZTE,Ericsson","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF always includes the SUPI in the Nlmf_Location_DetermineLocation Request if the target UE supports the capability of user plane positioning using LCS-UPP. The LMF allocatesthe LCS UP connection ID for target UE and includes the L","secretary_remarks":"Revision of S2-2404712. Revised in parallel session to S2-2405532.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14560,"status":"revised","reservation_date":"2024-04-22 09:39:29","uploaded":"2024-04-22 10:01:22","revisionof":"S2-2404712","revisedto":"S2-2405532","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":521.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405380.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.2, 6.2, 6.18.1, 6.18.2, 8.3.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405381","title":"[DRAFT] LS reply on LCS user plane connection binding to the UE","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to send the LS reply to S2-2403871 (C1-241722)","secretary_remarks":"Revision of S2-2404713. Revised in parallel session to S2-2405533.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14430,"status":"revised","reservation_date":"2024-04-22 09:39:30","uploaded":"2024-04-22 10:01:22","revisionof":"S2-2404713","revisedto":"S2-2405533","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_162_Changsha_2024-04\/Docs\/S2-2405381.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405382","title":"Correction of ML Model sharing in the scenario of Analytics context transfer","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that Removing the ML Model address can be only provided to a R17 target AnLF based on source AnLF local configuration. from the contents of Analytics context Adding ML Model Identifier in the ML model related information in the","secretary_remarks":"Revision of S2-2404071, merging S2-2404903. Revised in parallel session to S2-2405534.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14740,"status":"revised","reservation_date":"2024-04-22 09:39:30","uploaded":"2024-04-22 10:01:22","revisionof":"S2-2404071","revisedto":"S2-2405534","release":"Rel-18","crspec":"23.288","crspecversion":"18.5.0","workitem":[{"winame":"eNA_Ph3"}],"crnumber":1081.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405382.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1B.2.2, 6.2A.2, 6.1B.4, 7.2.5, 7.5.2, 7.6.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405383","title":"[DRAFT] Reply LS on Issues related Analytics context transfer between AnLF(s)","source":"Samsung Electronics France SA","contact":"Jungshin Park","contact-id":65750,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Issues related Analytics context transfer between AnLF(s)","secretary_remarks":"Revision of S2-2404898, merging S2-2404070. Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14820,"status":"postponed","reservation_date":"2024-04-22 09:39:31","uploaded":"2024-04-22 10:01:20","revisionof":"S2-2404898","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNA_Ph3_SEC"},{"winame":" eNA_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405383.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405385","title":"Removal of Ranging exposure service to Client UE through 5GC","source":"Sony, Xiaomi, Huawei, HiSilicon","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove from the subscription that a UE is allowed to use the Ranging\/SL Positioning exposure service (UE can receive Ranging\/SL positioning result related to other UE subscribers). Remove GMLC ProvideRanging service operation. Remove SL","secretary_remarks":"Revision of S2-2404111, merging S2-2404869 and S2-2404102. Revised in parallel session to S2-2405536.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14880,"status":"revised","reservation_date":"2024-04-22 09:39:33","uploaded":"2024-04-22 10:01:22","revisionof":"S2-2404111","revisedto":"S2-2405536","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":516.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405385.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.20.3, 7.1, 8.4.1, 8.4.2.7, 8.4.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405386","title":"Update about the UE role in PC-5 service exposure scenario","source":"OPPO","contact":"Yaxin Wang","contact-id":99608,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 5.6.2.2, 5.11, 6.7.1.1, 6.8 to align that UE1 can only be the target UE.","secretary_remarks":"Revision of S2-2404663. Revised off-line to S2-2405652.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14930,"status":"revised","reservation_date":"2024-04-22 09:39:33","uploaded":"2024-04-22 10:01:22","revisionof":"S2-2404663","revisedto":"S2-2405652","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":131.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405386.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.6.2.2, 5.11, 6.7.1.1, 6.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405493","title":"[DRAFT] LS Reply on RAN feedback during handover","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to reply the LS on RAN feedback during handover (R3-238038)","secretary_remarks":"Revision of S2-2404089. Revised in parallel session to S2-2405535.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14170,"status":"revised","reservation_date":"2024-04-22 09:40:32","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2404089","revisedto":"S2-2405535","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405493.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405494","title":"Alignment with stage 3 specification on configured End UE User Info ID and Direct discovery set","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Remove the provisioned\/configured User Info ID of End UE and clarify Application Layer ID should be used. Clarify that the Direct Discovery Set includes a list of protected User Info IDs.","secretary_remarks":"Revision of S2-2404660. WITHDRAWN","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14250,"status":"withdrawn","reservation_date":"2024-04-22 09:40:33","uploaded":null,"revisionof":"S2-2404660","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.5.1","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":438.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405495","title":"Reply LS on CT WG3 Reply LS on XRM and TSC QoS requirements","source":"SA WG2","contact":"Dan Wang","contact-id":87155,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3","secretary_remarks":"Revision of S2-2404022. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14640,"status":"approved","reservation_date":"2024-04-22 09:40:34","uploaded":"2024-04-22 10:01:17","revisionof":"S2-2404022","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2403882","lsto":"CT WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405495.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405496","title":"Clarification on the TSCAI parameters for XR","source":"ZTE","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing the TSC in the flow direction of TSCAI.","secretary_remarks":"Revision of S2-2404777. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14660,"status":"agreed","reservation_date":"2024-04-22 09:40:34","uploaded":"2024-04-22 10:01:19","revisionof":"S2-2404777","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.5.0","workitem":[{"winame":"XRM"}],"crnumber":5391.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"SP-240605","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405496.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"5.27.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405497","title":"Clarification on the partial coverage issue","source":"ZTE, Qualcomm Incorporated","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove partial coverage condition in the Located UE and SL Reference UE Discovery and selection.","secretary_remarks":"Revision of S2-2404775, merging S2-2404889. Revised in parallel session to S2-2405799.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14990,"status":"revised","reservation_date":"2024-04-22 09:40:36","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2404775","revisedto":"S2-2405799","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":132.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405497.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.2.2, 5.2.4, 5.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405498","title":"U2U Direct and Indirect NOTE","source":"Nokia, Nokia Shanghai Bell","contact":"Mao Cai","contact-id":89487,"tdoctype":"CR","for":"Approval","abstract":"WITHDRAWN: Summary of change: Added a NOTE to address the concern from RAN WG2","secretary_remarks":"Revision of S2-2405001. WITHDRAWN","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14340,"status":"withdrawn","reservation_date":"2024-04-22 09:40:37","uploaded":null,"revisionof":"S2-2405001","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.5.1","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":441.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405499","title":"[DRAFT] Reply LS on U2U relay selection","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2403890\/R2-2401916","secretary_remarks":"Revision of S2-2404317, merging S2-2404675 and S2-2405002. Revised in parallel session to S2-2405531.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14290,"status":"revised","reservation_date":"2024-04-22 09:40:38","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2404317","revisedto":"S2-2405531","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_relay_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_162_Changsha_2024-04\/Docs\/S2-2405499.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405531","title":"Reply LS on U2U relay selection","source":"SA WG2","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1","secretary_remarks":"Revision of S2-2405499. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14300,"status":"approved","reservation_date":"2024-04-22 09:40:50","uploaded":"2024-04-22 10:01:17","revisionof":"S2-2405499","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_relay_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2403890","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405531.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405532","title":"Add the binding mechanism between LCS user plane connection and the UE","source":"CATT, Huawei, HiSilicon, vivo, Qualcomm Incorporated, ZTE, Ericsson, Nokia","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The AMF always includes the UE identity in the Nlmf_Location_DetermineLocation Request if the target UE supports the capability of user plane positioning using LCS-UPP. The LMF allocatesthe LCS UP connection ID for target UE and include","secretary_remarks":"Revision of S2-2405380. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14570,"status":"agreed","reservation_date":"2024-04-22 09:40:50","uploaded":"2024-04-22 10:01:19","revisionof":"S2-2405380","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":521.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-240587","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405532.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1.2, 6.2, 6.18.1, 6.18.2, 8.3.2.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405533","title":"[DRAFT] LS reply on LCS user plane connection binding to the UE","source":"CATT","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"LS out","for":"Approval","abstract":"It is proposed to send the LS reply to S2-2403871 (C1-241722)","secretary_remarks":"Revision of S2-2405381. Revised in parallel session to S2-2405797.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14440,"status":"revised","reservation_date":"2024-04-22 09:40:51","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2405381","revisedto":"S2-2405797","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_162_Changsha_2024-04\/Docs\/S2-2405533.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405534","title":"Correction of ML Model sharing in the scenario of Analytics context transfer","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the ML Model address can be provided to a target AnLF if the target AnLF is allowed to get the ML model file address(es), e.g., based on source AnLF s local configuration. Adding ML Model Identifier in the ML model related","secretary_remarks":"Revision of S2-2405382. Revised in parallel session, merging S2-2404002, to S2-2405801.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14750,"status":"revised","reservation_date":"2024-04-22 09:40:51","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2405382","revisedto":"S2-2405801","release":"Rel-18","crspec":"23.288","crspecversion":"18.5.0","workitem":[{"winame":"eNA_Ph3"}],"crnumber":1081.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405534.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1B.2.2, 6.2A.2, 6.1B.4, 7.2.5, 7.5.2, 7.6.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405535","title":"LS on RAN feedback during handover","source":"SA WG2","contact":"Haiyang Sun","contact-id":79579,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3","secretary_remarks":"Revision of S2-2405493. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14180,"status":"approved","reservation_date":"2024-04-22 09:40:52","uploaded":"2024-04-22 10:01:18","revisionof":"S2-2405493","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"TRS_URLLC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2403866","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405535.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405536","title":"Removal of Ranging exposure service to Client UE through 5GC","source":"Sony, Xiaomi, Huawei, HiSilicon","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove from the subscription that a UE is allowed to use the Ranging\/SL Positioning exposure service (UE can receive Ranging\/SL positioning result related to other UE subscribers). Remove GMLC ProvideRanging service operation. Remove SL","secretary_remarks":"Revision of S2-2405385. Revised in parallel session to S2-2405798.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14890,"status":"revised","reservation_date":"2024-04-22 09:40:53","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2405385","revisedto":"S2-2405798","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":516.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405536.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.20.3, 7.1, 8.4.1, 8.4.2.7, 8.4.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405652","title":"Update about the UE role in PC-5 service exposure scenario","source":"OPPO","contact":"Yaxin Wang","contact-id":99608,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 5.6.2.2, 5.11, 6.7.1.1, 6.8 to align that UE1 can only be the target UE.","secretary_remarks":"Revision of S2-2405386. Revised in parallel session to S2-2405800.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14940,"status":"revised","reservation_date":"2024-04-22 09:41:41","uploaded":"2024-04-22 10:01:21","revisionof":"S2-2405386","revisedto":"S2-2405800","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":131.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405652.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.6.2.2, 5.11, 6.7.1.1, 6.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405797","title":"LS reply on LCS user plane connection binding to the UE","source":"SA WG2","contact":"Yunjing Hou","contact-id":46707,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: CT WG4, RAN WG2. Attachments: TS 23.273 CR 0521.","secretary_remarks":"Revision of S2-2405533. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14450,"status":"approved","reservation_date":"2024-04-22 09:42:41","uploaded":"2024-04-22 10:01:18","revisionof":"S2-2405533","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_eLCS_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2403871","lsto":"CT WG1","Cc":"CT WG4, RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405797.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405798","title":"Removal of Ranging exposure service to Client UE through 5GC","source":"Sony, Xiaomi, Huawei, HiSilicon","contact":"Lars Nord","contact-id":82070,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove from the subscription that a UE is allowed to use the Ranging\/SL Positioning exposure service (UE can receive Ranging\/SL positioning result related to other UE subscribers). Remove GMLC ProvideRanging service operation. Remove SL","secretary_remarks":"Revision of S2-2405536. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14900,"status":"agreed","reservation_date":"2024-04-22 09:42:42","uploaded":"2024-04-22 10:01:19","revisionof":"S2-2405536","revisedto":"","release":"Rel-18","crspec":"23.273","crspecversion":"18.5.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":516.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-240601","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405798.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.20.3, 7.1, 8.4.1, 8.4.2.2, 8.4.2.7, 8.4.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405799","title":"Clarification on the partial coverage issue","source":"ZTE, Qualcomm Incorporated","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove partial coverage condition in the Located UE and SL Reference UE Discovery and selection.","secretary_remarks":"Revision of S2-2405497. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":15000,"status":"agreed","reservation_date":"2024-04-22 09:42:43","uploaded":"2024-04-22 10:01:19","revisionof":"S2-2405497","revisedto":"","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":132.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-240601","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405799.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.2, 5.2.4, 5.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405800","title":"Update about the UE role in PC-5 service exposure scenario","source":"OPPO","contact":"Yaxin Wang","contact-id":99608,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update clause 5.6.2.2, 5.11, 6.7.1.1, 6.8 to align that UE1 can only be the target UE.","secretary_remarks":"Revision of S2-2405652. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14950,"status":"agreed","reservation_date":"2024-04-22 09:42:44","uploaded":"2024-04-22 10:01:19","revisionof":"S2-2405652","revisedto":"","release":"Rel-18","crspec":"23.586","crspecversion":"18.3.0","workitem":[{"winame":"Ranging_SL"}],"crnumber":131.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-240601","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405800.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.6.2.2, 5.11, 6.7.1.1, 6.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2405801","title":"Correction of ML Model sharing in the scenario of Analytics context transfer","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Endorsement","abstract":"Summary of change: Clarify that the ML Model address can be provided to a target AnLF if the target AnLF is allowed to get the ML model file address(es), e.g., based on source AnLF s local configuration. Adding ML Model Identifier in the ML model related","secretary_remarks":"Revision of S2-2405534, merging S2-2404002. Postponed.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LSs","tdoc_agenda_sort_order":14760,"status":"postponed","reservation_date":"2024-04-22 09:42:45","uploaded":"2024-04-22 10:01:20","revisionof":"S2-2405534","revisedto":"S2-2406491","release":"Rel-18","crspec":"23.288","crspecversion":"18.5.0","workitem":[{"winame":"eNA_Ph3"}],"crnumber":1081.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_162_Changsha_2024-04\/Docs\/S2-2405801.zip","group":"S2","meeting":"S2-162","year":2024,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"6.1B.2.2, 6.2A.2, 6.1B.4, 7.2.5, 7.5.2, 7.6.2","crsinpack":null,"crsinpacknumber":0}]