[{"name":"S2-2311936","title":"LS from RAN WG2: LS on misalignment between PTW and Coverage Window","source":"RAN WG2","contact":"Bin Xu","contact-id":96153,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed the issue of possible misalignment between PTW and Coverage Window in IoT NTN when eDRX is configured (e.g., due to the eDRX configuration, the PTW for a particular PO does not coincide with the coverage). Specifically, RAN WG2 would like to ask SA WG2 the following questions: 1) Whether the issue of misalignment between PTW and Coverage Window is valid from SA WG2 s point of view? 2) If the answer to Q1) is yes, whether it can be solved by any method that SA WG2 has already specified or by network implementation, or there is need for further enhancement?. Action: RAN WG2 respectfully asks SA WG2 to provide feedback on the questions above.","secretary_remarks":"Revision of (postponed) S2-2310122 from SA WG2#159. Responses drafted in S2-2312436, S2-2312788, S2-2313060, S2-2313113. Final response in S2-2313795","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24510,"status":"replied to","reservation_date":"2023-10-18 06:54:12","uploaded":"2023-10-18 07:21:59","revisionof":"S2-2310122","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2309283","lsreply":"S2-2313795","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311936.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311940","title":"LS from SA WG1: Reply LS on access to stand-alone non-public network services via PLMN and vice versa","source":"SA WG1","contact":"Xiaonan Shi","contact-id":87257,"tdoctype":"LS in","for":"Information","abstract":"SA WG1 thanks CT WG1 for this LS on access to stand-alone non-public network services via PLMN and vice versa. Please see the answer as following: Q1: Whether a UE needs to take into account the non-public network services the UE is currently using when the UE selects a PLMN to access these non-public network services, to ensure service continuity (and vice versa)? Answer1: There are no such specific service requirements. Q2: Whether a UE needs to take into account which non-public network services the UE intends to access when the UE selects a PLMN to access the non-public network services, to ensure the selected PLMN has agreement\/SLA with the non-public network (and vice versa)? Answer 2: There are no such specific service requirements. Q3: Can the UE use any RAT of a PLMN to access non-public network services via the PLMN or take into account RAT for service experience consistency of the non-public network services? Answer 3: There are no service requirements that a UE can use any RAT of a PLMN to access non-public network services via the PLMN or to take into account the RAT. By answering no to Question 1 and 2, SA WG1 did not reach agreement whether these specific scenarios are valuable to be discussed further.","secretary_remarks":"Revision of (postponed) S2-2310128 from SA WG2#159. Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24550,"status":"noted","reservation_date":"2023-10-18 06:54:12","uploaded":"2023-10-18 07:21:59","revisionof":"S2-2310128","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S1-232607","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311940.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311951","title":"LS from CT WG1: LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"CT WG1","contact":"Xiaoyan Duan","contact-id":85499,"tdoctype":"LS in","for":"Action","abstract":"CT WG1 is working on stage 3 procedures for 5G ProSe UE-to-UE relay discovery taking into account of the security requirements from SA WG3 (see TS 33.503 clause 6.1.3.3). Considering the impacts of the security requirements on the current 5G ProSe UE-to-UE relay discovery procedures as specified by SA WG2, CT WG1 would like to check with SA WG2 on the following aspect: - As specified in TS 33.503 clause 6.1.3.3.3.2, for 5G ProSe UE-to-UE Relay Discovery with Model B, the User Info IDs of the discoverer 5G ProSe End UE and discoveree 5G ProSe End UE are included in a protected direct discovery set and sent between the discoverer 5G ProSe End UE and the discoveree 5G ProSe End UE via the 5G ProSe UE-to-UE Relay UE. Question: How does the 5G ProSe UE-to-UE Relay UE send the UE-to-UE Relay Discovery Response message from the discoveree 5G ProSe End UE to the corresponding discoverer 5G ProSe End UE, considering 1) the User Info IDs of the discoverer 5G ProSe End UE and discoveree 5G ProSe End UE in the protected direct discovery set are transparent to the 5G ProSe UE-to-UE Relay UE and 2) the 5G ProSe UE-to-UE Relay UE may serve more than one discoverer 5G ProSe End UE simultaneously?. ACTION 1: CT WG1 kindly asks SA WG2 to provide answer to the above question.","secretary_remarks":"Responses drafted in S2-2312055, S2-2312086, S2-2312250, S2-2312662, S2-2312676, S2-2312975, S2-2312976, S2-2313039, S2-2313176, S2-2312794. Postponed.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23870,"status":"postponed","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"S2-2400009","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG3","lsoriginalls":"C1-237897","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311951.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311954","title":"LS from CT WG1: LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"CT WG1","contact":"Taimoor Abbas","contact-id":90799,"tdoctype":"LS in","for":"Action","abstract":"If the PC5 link is used for Ethernet traffic between source 5G ProSe layer-3 end UE and target 5G ProSe layer-3 end UE via 5G ProSe Layer-3 UE-to-UE relay, the source 5G ProSe Layer-3 End UE sends its Ethernet MAC address to the 5G ProSe Layer-3 UE-to-UE Relay in PROSE DIRECT LINK SECURITY MODE COMPLETE message after the security protection is enabled. According to TS 23.304 [3], the relay may detect that the source 5G ProSe end UE is using a non-unique MAC address and may send a message to the source 5G ProSe Layer-3 End UE indicating there is Ethernet MAC address conflict. {. . .} Action: CT WG1 would like to ask feedback, if any, for the above agreement.","secretary_remarks":"Responses drafted in S2-2312205, S2-2312253, S2-2312971, S2-2313181. Final response in S2-2313799","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24160,"status":"replied to","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-237943","lsreply":"S2-2313799","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311954.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311959","title":"LS from CT WG4: Reply LS on Enhancement on the attribute for 5GLAN management","source":"CT WG4","contact":"RONG WANG","contact-id":87346,"tdoctype":"LS in","for":"Information","abstract":"CT WG4 thanks SA WG5 for their liaison S5-235780 (C4-234376) in which SA WG5 asks CT WG4 two questions. Q1: Please clarify which identifiers is used to support 5G LAN-type services, as stated in TS 29.510, the attribute of internalGroupId has already defined and supported by the trusted AF in Table 6.1.6.2.96-1: Definition of type TrustAfInfo. However, 5g-vn-groups is used in TS 29.503. A: SA WG2 specified that the External Group ID and Internal Group ID are used to identify the 5G VN group (refer to clause 5.29.2 of 3GPP TS23.501). For Internal Group ID, CT WG4 defined the internalGroupIdentifier to uniquely identify a 5G VN group in UDM (Please refer to clause 6.5.6.2.6 of 3GPP TS29.503). {. . .} Q2: SA WG5 would kindly ask CT WG4 to make the necessary updates to their specifications to enable 5G LAN-type services (e.g., enhancement for the AmfInfo\/SmfInfo\/NrfInfo). A: CT WG4 didn t see the need to define the 5G LAN-type service in NRF for AmfInfo\/SmfInfo\/NrfInfo, since such information is not used for node selection.","secretary_remarks":"Postponed.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24660,"status":"postponed","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"S2-2400012","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"SA WG2","lsoriginalls":"C4-234414","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311959.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311962","title":"LS from CT WG4: Reply LS on SNPN Identifier based N3IWF FQDN","source":"CT WG4","contact":"Jayeeta SAHA","contact-id":98476,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 during their last meeting has sent a liaison statement to CT WG4. The Liaison Statement requests CT WG4 to address the issue for a missing definition of SNPN Identifier based N3IWF FQDN in Clause 28.3.2.2.6.1 of 3GPP TS 23.003. The addition of the definition would help the former to resolve one of the Editor's note in 3GPP TS 23.501. Accordingly, CT WG4 has defined the SNPN Identifier based N3IWF FQDN in Clause 28.3.2.2.6.1 of 3GPP TS 23.003 Version 18.3.0. The Agreed CR (CR#0687 revision 2) is attached with this LS. Action: SA WG2 is requested to refer to the abovesaid clause in 3GPP TS 23.003 in order to resolve the Editor's Note in 23.501 as necessary.","secretary_remarks":"Responses drafted in S2-2312215, S2-2312506. Final response in S2-2313718","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24560,"status":"replied to","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-234655","lsreply":"S2-2313718, S2-2313718","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311962.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311965","title":"LS from RAN WG3: LS on handling of location information in multi-path operation","source":"RAN WG3","contact":"Seokjung Kim","contact-id":70180,"tdoctype":"LS in","for":"Action","abstract":"For the Multi-path operation in SL Relay Enhancement WI, RAN WG3 discussed the aspect on whether the NG-RAN node reports both the cell ID of the direct path and the cell ID of the indirect path to the AMF, in case the direct path and the indirect path connect with different cells of same gNB. RAN WG3 observed that the NG-RAN node can also report to the AMF the cell identity of PSCell in the dual connectivity. Because it is the 5GC to use the User Location Information, RAN WG3 would like to request SA WG2 answer the following question: Question: Whether it is required for NG-RAN node to report both cell IDs of direct path and indirect path to AMF, in case the direct path and the indirect path connect with different cells of same gNB?. Action: RAN WG3 kindly asks SA WG2 to provide feedback on the above question.","secretary_remarks":"Responses drafted in S2-2312081, S2-2312255, S2-2312661, S2-2312678, S2-2312892, S2-2313184, S2-2313211. Final response in S2-2313800","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24300,"status":"replied to","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"RAN WG2","lsoriginalls":"R3-235761","lsreply":"S2-2313800","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311965.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311966","title":"LS from RAN WG3: Reply LS on the usage of paging subgrouping information in RAN in case of abnormal scenario","source":"RAN WG3","contact":"Feng Han","contact-id":73581,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks to CT WG1 for their LS on the usage of paging subgrouping information in RAN in case of abnormal scenario. RAN WG3 discussed the two abnormal scenarios identified by CT WG1, and concluded that the handling of the abnormal scenarios can be left to the AMF implementation for paging the UE and therefore don t need RAN WG3 action. {. . .}","secretary_remarks":"Postponed.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24670,"status":"postponed","reservation_date":"2023-10-18 06:54:13","uploaded":"2023-10-18 16:42:50","revisionof":"","revisedto":"S2-2400014","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2, RAN WG2","lsoriginalls":"R3-235883","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311966.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311980","title":"LS from RAN WG2: LS on L2ID and User Info for L2 based U2U","source":"RAN WG2","contact":"Youngdae Lee","contact-id":59040,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has been discussing Layer-2 based UE-to-UE relay between source and target Remote UEs for Release 18. In RAN WG2#123, RAN WG2 agreed that, instead of a L2 ID, a Local ID is used as a UE ID in a SRAP header for L2 based U2U relay and two Local IDs are included in the SRAP header to identify source and target Remote UE respectively. In RAN WG2#123bis, RAN WG2 also agreed that the RRCReconfigurationSidelink message is used to indicate the Local ID pair from relay UE to source and target Remote UEs respectively. RAN WG2 further discussed how to link the User Info ID with the Local ID at the remote UE, based on two options that are both feasible from RAN WG2 perspective, and then RAN WG2 made a working assumption that the RRCReconfigurationSidelink message carries both the L2 ID and the Local ID of the peer Remote UE and assumes that the association between the User Info ID and the L2 ID of the peer Remote UE is done at the Remote UE ProSe layer. Therefore, RAN WG2 would ask SA WG2 if the above working assumption is feasible from SA WG2 perspective. RAN WG2 will appreciate timely response from SA WG2 before TSG RAN#102. RAN WG2 intend to implement this working assumption if SA WG2 indicate it is feasible. Action: RAN WG2 respectfully requests SA WG2 to give their feedback on whether the above working assumption is feasible from SA WG2 perspective.","secretary_remarks":"Responses drafted in S2-2312053, S2-2312084, S2-2312247, S2-2312660, S2-2313183. Final response in S2-2313796","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23720,"status":"replied to","reservation_date":"2023-10-18 16:41:40","uploaded":"2023-10-19 12:19:16","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"R2-2311566","lsreply":"S2-2313796","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311980.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311982","title":"LS from RAN WG2: Reply LS on paging","source":"RAN WG2","contact":"Lili Zheng","contact-id":80379,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 would like to thank RAN WG3 for their LS on the enhancements to restricting paging in a limited area. RAN WG2 discussed Q1 and would like to provide the following answer. {. . .}","secretary_remarks":"Postponed.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24680,"status":"postponed","reservation_date":"2023-10-18 16:41:40","uploaded":"2023-10-19 12:19:16","revisionof":"","revisedto":"S2-2400019","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"SA WG2","lsoriginalls":"R2-2311591","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311982.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311985","title":"LS from RAN WG2: LS to CT WG1 on emergency cause value for relay","source":"RAN WG2","contact":"Bingxue Leng","contact-id":90619,"tdoctype":"LS in","for":"Information","abstract":"For the cause value setting for RRC connection establishment\/resumption of L2 U2N Relay UE, in R17, the L2 U2N Relay UE can base on its implementation to set it, but can only set to emergency if the same value is received from the SL-RLC0 message as the following NOTE in TS 38.331: {. . .} RAN WG2 respectfully asks CT WG1 to decide which approach to use, and feedback to RAN WG2, so the following question is to check CT WG1 s decision: Q1: Which approach is to be adopted by CT WG1 for the emergency cause value setting for SL_RLC1 case?","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24450,"status":"noted","reservation_date":"2023-10-18 16:41:40","uploaded":"2023-10-30 08:22:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"R2-2311600","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2311985.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312052","title":"[DRAFT] Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"InterDigital Communications","contact":"Jung Je Son","contact-id":96448,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","secretary_remarks":"Response to S2-2311954. Revised in parallel session to S2-2313724.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24210,"status":"revised","reservation_date":"2023-10-31 18:10:51","uploaded":"2023-11-03 18:14:08","revisionof":"","revisedto":"S2-2313724","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312052.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312053","title":"[DRAFT] Reply LS on L2ID and User Info for L2 based U2U","source":"InterDigital Communications","contact":"Jung Je Son","contact-id":96448,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on L2ID and User Info for L2 based U2U","secretary_remarks":"Response to S2-2311980. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23810,"status":"not treated","reservation_date":"2023-10-31 18:14:56","uploaded":"2023-11-03 18:14:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_relay_enh"},{"winame":" 5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312053.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312054","title":"Discussion on L2ID and User Info for L2 based U2U in LS from RAN WG2.","source":"Interdigital","contact":"Jung Je Son","contact-id":96448,"tdoctype":"discussion","for":"Discussion","abstract":"This contribution discusses and proposes a way forward on the questions asked by RAN WG2.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23730,"status":"not treated","reservation_date":"2023-10-31 18:18:55","uploaded":"2023-11-03 18:14:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312054.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312055","title":"[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"InterDigital Communications","contact":"Jung Je Son","contact-id":96448,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","secretary_remarks":"Response to S2-2311951 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23900,"status":"not treated","reservation_date":"2023-10-31 18:22:09","uploaded":"2023-11-03 18:14:08","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312055.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312056","title":"Correction on 5G ProSe UE-to-UE relay discovery with security aspects","source":"InterDigital Communications","contact":"Jung Je Son","contact-id":96448,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Direct Discovery Solicitation ID is added in the message from solicitation message from UE-to-UE Relay for association of soliciation message from discoverer UE and response message from discoveree UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24010,"status":"not treated","reservation_date":"2023-10-31 18:27:19","uploaded":"2023-11-03 18:14:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":385.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312056.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.3.2.4.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312057","title":"Update on Layer2 link establishment procedure relating to MAC address conflict.","source":"InterDigital Communications","contact":"Jung Je Son","contact-id":96448,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Layer2 Link establishment procedure is updated relating to conflict of MAC address from target UE. Added a NOTE that additional scenarios for MAC address confliction are to be dealt at Stage 3.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24240,"status":"not treated","reservation_date":"2023-10-31 18:31:58","uploaded":"2023-11-03 18:14:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":386.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312057.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.4.3.7.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312058","title":"Update on Layer-2 link management over PC5 for 5G ProSe Layer-2 UE-to-UE Relay","source":"InterDigital Communications","contact":"Jung Je Son","contact-id":96448,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: LIU between peer Layer-2 End UEs are clarified.","secretary_remarks":"Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23830,"status":"postponed","reservation_date":"2023-10-31 18:38:57","uploaded":"2023-11-03 18:14:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":387.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312058.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.4.3.7.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312080","title":"Discussion about LS on handling of location information in multi-path operation.","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the LS from RAN WG3 on handling of location information in multi-path operation (S2-2311965\/R3-235761).","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24400,"status":"not treated","reservation_date":"2023-01-11 04:46:34","uploaded":"2023-11-03 09:37:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312080.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312081","title":"[DRAFT] Reply LS on handling of location information in multi-path operation","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on handling of location information in multi-path operation","secretary_remarks":"Response to S2-2311965. Revised in parallel session to S2-2313725.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24310,"status":"revised","reservation_date":"2023-01-11 04:48:00","uploaded":"2023-11-03 09:37:17","revisionof":"","revisedto":"S2-2313725","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312081.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312082","title":"Clarification on handling location information from NG-RAN in multi-path operation","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 6.9.3 - Clarify that how for NG-RAN to handle location information for the case of difference cells in multi-path operation.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24410,"status":"noted","reservation_date":"2023-01-11 04:50:11","uploaded":"2023-11-03 09:37:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":388.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312082.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.9.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312084","title":"[DRAFT] Reply LS on L2ID and User Info for L2 based U2U","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on L2ID and User Info for L2 based U2U","secretary_remarks":"Response to S2-2311980. Revised in parallel session to S2-2313719.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23760,"status":"revised","reservation_date":"2023-01-11 04:52:17","uploaded":"2023-11-03 12:40:19","revisionof":"","revisedto":"S2-2313719","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_160_Chicago_2023-11\/Docs\/S2-2312084.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312086","title":"[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"Samsung Research America","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: SA WG3","secretary_remarks":"Response to S2-2311951 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23910,"status":"not treated","reservation_date":"2023-01-11 05:11:28","uploaded":"2023-11-02 06:09:07","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312086.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312199","title":"Correction on 5G ProSe UE-to-UE Relay Discovery with Source Layer-2 ID of Discoveree UE","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Including the Source Layer-2 ID of the discoveree 5G ProSe End UE in the 5G ProSe UE-to-UE Relay Discovery Solicitation message toward the discoveree 5G ProSe End UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24020,"status":"not treated","reservation_date":"2023-02-11 05:23:04","uploaded":"2023-11-02 06:09:07","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":389.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312199.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312201","title":"Correction on 5G ProSe UE-to-UE Relay Discovery with Source Layer-2 ID of Discoverer UE","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Including the Source Layer-2 ID of the discoverer 5G ProSe End UE in the 5G ProSe UE-to-UE Relay Discovery Solicitation message toward the discoveree 5G ProSe End UE.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24030,"status":"not treated","reservation_date":"2023-02-11 05:26:59","uploaded":"2023-11-02 06:09:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":390.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312201.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312202","title":"Correction on 5G ProSe UE-to-UE Relay Discovery with Index","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Including the Index associated with the RSC and the Source Layer-2 ID of the discoverer 5G ProSe End UE in the 5G ProSe UE-to-UE Relay Discovery Solicitation message toward the discoveree 5G ProSe End UE.","secretary_remarks":"Revised in parallel session to S2-2313721.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24040,"status":"revised","reservation_date":"2023-02-11 05:30:55","uploaded":"2023-11-02 06:09:06","revisionof":"","revisedto":"S2-2313721","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":391.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312202.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312203","title":"Correction on Common identifiers for 5G ProSe UE-to-UE Relay Discovery","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarification on Common identifiers for 5G ProSe UE-to-UE Relay Discovery.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24070,"status":"not treated","reservation_date":"2023-02-11 05:34:07","uploaded":"2023-11-02 06:09:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":392.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312203.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312204","title":"Discussion on 5G ProSe UE-to-UE relay discovery with security aspects.","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper is to discuss the Issues of 5G ProSe UE-to-UE relay discovery with security aspects and the potential options to fix the issues.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23880,"status":"not treated","reservation_date":"2023-02-11 05:39:37","uploaded":"2023-11-02 06:09:07","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312204.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312205","title":"[DRAFT] Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"Samsung Research America","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-2311954 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24170,"status":"not treated","reservation_date":"2023-02-11 05:46:18","uploaded":"2023-11-02 09:06:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312205.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312206","title":"Correction on Layer-2 link establishment for PC5 communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: When the MAC address of source 5G ProSe End UE is not unique, 5G ProSe UE-to-UE rejects this procedure.","secretary_remarks":"Merged into S2-2313801","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24250,"status":"merged","reservation_date":"2023-02-11 05:48:56","uploaded":"2023-11-02 09:06:48","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":393.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312206.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312215","title":"[DRAFT] Reply LS on SNPN Identifier based N3IWF FQDN","source":"Samsung","contact":"Naman Gupta","contact-id":93866,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4","secretary_remarks":"Response to S2-2311962. Revised in parallel session, merging S2-2312506, to S2-2313718.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24570,"status":"revised","reservation_date":"2023-02-11 06:27:07","uploaded":"2023-11-03 23:03:57","revisionof":"","revisedto":"S2-2313718","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312215.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312216","title":"Clarifications on terminology for SNPN Identifier based N3IWF FQDN","source":"Samsung","contact":"Naman Gupta","contact-id":93866,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removal of 4 Editor s Notes in clause 5.30.2.12 Alignement of the terminology used in TS 23.003 Minor Clarifications for the case of Onboarding according to clause 28.3.2.2.7.2 of TS 23.003","secretary_remarks":"Merged into S2-2313717","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24620,"status":"merged","reservation_date":"2023-02-11 06:29:57","uploaded":"2023-11-03 23:03:57","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":5092.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312216.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.30.2.12","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312246","title":"Discussion on RAN WG2 LS on L2ID and User Info for L2 based U2U.","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the LS from RAN WG2 on L2ID and User Info for L2 based U2U (S2-2311980\/R2-2311566).","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23740,"status":"not treated","reservation_date":"2023-02-11 08:28:14","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312246.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312247","title":"[DRAFT] Reply LS on L2ID and User Info for L2 based U2U","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on L2ID and User Info for L2 based U2U","secretary_remarks":"Response to S2-2311980. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23790,"status":"not treated","reservation_date":"2023-02-11 08:28:14","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312247.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312248","title":"Convey Layer-2 ID of target Layer-2 End UE to source Layer-2 End UE","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the Direct Communication Accept message over the first hop to include the Layer-2 ID of target Layer-2 End UE to the source Layer-2 End UE.","secretary_remarks":"Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23840,"status":"postponed","reservation_date":"2023-02-11 08:28:14","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":394.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312248.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.4.3.7.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312249","title":"Discussion about LS on 5G ProSe UE-to-UE relay discovery with security aspects.","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the LS from CT WG1 on 5G ProSe UE-to-UE relay discovery with security aspects (S2-2311951\/C1-237897).","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23890,"status":"not treated","reservation_date":"2023-02-11 08:28:15","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312249.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312250","title":"[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","secretary_remarks":"Response to S2-2311951. Revised in parallel session to S2-2313722.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23920,"status":"revised","reservation_date":"2023-02-11 08:28:15","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"S2-2313722","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312250.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312251","title":"Clarification on sending U2U Relay Discovery Response message using unicast Layer-2 ID","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that UE-to-UE Relay Discovery Response message is sent to all discoverer UEs that have sent UE-to-UE Relay Solicitation message to the UE-to-UE Relay, if the RSC contained in the UE-to-UE Relay Discovery Response message received from the discoveree End UE matches any of the (pre)configured RSC(s).","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24080,"status":"not treated","reservation_date":"2023-02-11 08:28:15","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":395.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312251.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.3.2.4.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312252","title":"Clarification on sending U2U Relay Discovery Response message using default Layer-2 ID","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The Destination Layer-2 ID is set to the new defined Default Destination Layer-2 ID and the UE-to-UE Relay sends the UE-to-UE Relay Discovery Response message using the Default Destination Layer-2 ID, if the RSC contained in the UE-to-UE Relay Discovery Response message received from the discoveree End UE matches any of the (pre)configured RSC(s).","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24090,"status":"not treated","reservation_date":"2023-02-11 08:28:16","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":396.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312252.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.1.5.1, 5.8.4.2, 6.3.2.4.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312253","title":"[DRAFT] Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","secretary_remarks":"Response to S2-2311954 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24180,"status":"not treated","reservation_date":"2023-02-11 08:28:17","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312253.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312254","title":"NG-RAN Location reporting for multi-path communication via direct Uu path and via Layer-2 UE-to-Network Relay","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding requirement for Cell ID information of 5G ProSe Layer-2 UE-to-Network Relay path reporting when supported.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24420,"status":"not treated","reservation_date":"2023-02-11 08:28:17","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":397.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312254.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.9.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312255","title":"[DRAFT] Reply LS on handling of location information in multi-path operation","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on handling of location information in multi-path operation","secretary_remarks":"Response to S2-2311965 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24340,"status":"not treated","reservation_date":"2023-02-11 08:28:18","uploaded":"2023-11-03 01:37:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312255.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312436","title":"[DRAFT] Reply LS on misalignment between PTW and Coverage Window","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"This paper proposes a reply to RAN WG2 LS on misalignment between PTW and Coverage Window","secretary_remarks":"Response to S2-2311936. Merged into S2-2313483","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24520,"status":"merged","reservation_date":"2023-02-11 15:39:53","uploaded":"2023-11-03 21:22:41","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312436.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312506","title":"[DRAFT] Reply LS on SNPN Identifier based N3IWF FQDN","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Confirms that SA WG2 align with CT WG4 on the FQDNs for N3IWF selection","secretary_remarks":"Response to S2-2311962. Merged into S2-2313718","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24590,"status":"merged","reservation_date":"2023-02-11 19:09:30","uploaded":"2023-11-03 21:20:40","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312506.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312507","title":"SNPN N3WIF FQDN terminology alignment with stage 3","source":"Ericsson, Huawei, Qualcomm","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the editor s note, and align the terminology with 23.003.","secretary_remarks":"Revision of S2-2309673 from S2#158. Revised in parallel session, merging S2-2312216 and S2-2312617, to S2-2313717.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24600,"status":"revised","reservation_date":"2023-02-11 19:09:30","uploaded":"2023-11-03 21:20:40","revisionof":"S2-2309673","revisedto":"S2-2313717","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":4786.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312507.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.30.2.12","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312617","title":"Clarification on SNPN Identifier based N3IWF FQDN for Access to SNPN services via Untrusted non-3GPP access","source":"Nokia, Nokia Shanghai Bell","contact":"Pallab Gupta","contact-id":87959,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Resolve EN s on SNPN Identifier based N3IWF FQDN used for emergency services and UE onboarding.","secretary_remarks":"Merged into S2-2313717","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24630,"status":"merged","reservation_date":"2023-03-11 04:50:17","uploaded":"2023-11-03 10:42:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":5139.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312617.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.30.2.12","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312659","title":"Layer-2 IDs of End UEs","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: The L2 ID of one End UE is sent to another End UE in the link management message.","secretary_remarks":"Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23850,"status":"postponed","reservation_date":"2023-03-11 06:47:58","uploaded":"2023-11-03 09:50:18","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"},{"winame":" NR_SL_relay_enh"}],"crnumber":398.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312659.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312660","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-2311980","secretary_remarks":"Response to S2-2311980. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23800,"status":"not treated","reservation_date":"2023-03-11 06:47:58","uploaded":"2023-11-03 09:50:18","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"},{"winame":" NR_SL_relay_enh"}],"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_160_Chicago_2023-11\/Docs\/S2-2312660.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312661","title":"[DRAFT] Reply LS on handling of location information in multi-path operation","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2311965","secretary_remarks":"Response to S2-2311965 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24350,"status":"not treated","reservation_date":"2023-03-11 06:47:58","uploaded":"2023-11-03 09:50:18","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_relay_enh-Core"},{"winame":" 5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312661.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312662","title":"[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2311951","secretary_remarks":"Response to S2-2311951 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23940,"status":"not treated","reservation_date":"2023-03-11 06:47:58","uploaded":"2023-11-03 09:50:18","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312662.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312676","title":"[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: SA WG3","secretary_remarks":"Response to S2-2311951 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23950,"status":"not treated","reservation_date":"2023-03-11 07:20:34","uploaded":"2023-11-03 09:54:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312676.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312677","title":"Updates to U2U relay discovery with model B","source":"Vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: In step2, the U2U relay UE addtionally includes the Layer-2 ID of the discoverer 5G ProSe End UE (UE-1) (it can be detected in step1) in the discovery solicitiation message In step3, the discoveree 5G ProSe End UE needs to add the recived Layer-2 ID of the discoverer 5G ProSe End UE (UE-1) in the Discovery Response message to the U2U relay UE In step4, the U2U relay UE sends the 5G ProSe UE-to-UE Relay Discovery Response message which destination Layer-2 ID is set to Layer-2 ID of the discoverer 5G ProSe End UE received in step3.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24100,"status":"not treated","reservation_date":"2023-03-11 07:20:34","uploaded":"2023-11-03 09:54:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":399.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312677.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.3.2.4.3.","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312678","title":"[DRAFT] Reply LS on handling of location information in multi-path operation","source":"vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2","secretary_remarks":"Response to S2-2311965 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24360,"status":"not treated","reservation_date":"2023-03-11 07:20:35","uploaded":"2023-11-03 09:54:51","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312678.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312747","title":"Discussion about LS on L2ID and User Info for L2 based U2U.","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the LS from RAN WG2 on L2ID and User Info for L2 based U2U (S2-2311980\/R2-2311566).","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23750,"status":"not treated","reservation_date":"2023-03-11 08:21:34","uploaded":"2023-11-03 12:40:19","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312747.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312788","title":"[DRAFT] LS on misalignment between PTW and Coverage Window","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN WG2 that eDRX and DisCo is already handled by the MME\/AMF.","secretary_remarks":"Response to S2-2311936. Revised in parallel session, merging S2-2313060, S2-2313113 and S2-2312436, to S2-2313483.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24460,"status":"revised","reservation_date":"2023-03-11 08:52:07","uploaded":"2023-11-03 13:44:20","revisionof":"","revisedto":"S2-2313483","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312788.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312792","title":"U2U Relay RAN alignment for Layer-2 IDs","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Enhance the per-hop PC5-S message to include the Layer-2 ID of End UE to the peer End UE.","secretary_remarks":"Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23860,"status":"postponed","reservation_date":"2023-03-11 09:00:08","uploaded":"2023-11-03 13:44:20","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":400.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312792.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.4.3.7.2, 6.7.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312793","title":"Rejection of L3 U2U Connection Setup when Ethernet MAC address conflict is detected","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To clarify that if L3 Relay UE detects a MAC address conflict, it rejects the direct link establishment rather than accepts the direct link establishment.","secretary_remarks":"Revised in parallel session, merging S2-2312936, to S2-2313723.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24260,"status":"revised","reservation_date":"2023-03-11 09:00:09","uploaded":"2023-11-03 13:44:20","revisionof":"","revisedto":"S2-2313723","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":401.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312793.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.7.1.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312794","title":"[DRAFT] LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"LS to SA WG3 about the security aspects identified by CT WG1 and DCR\/DCA.","secretary_remarks":"Response to S2-2311951 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24000,"status":"not treated","reservation_date":"2023-03-11 09:00:10","uploaded":"2023-11-03 13:44:20","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312794.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312892","title":"[DRAFT] Reply LS on handling of location information in multi-path operation","source":"Nokia, Nokia Shanghai Bell","contact":"Saubhagya Baliarsingh","contact-id":98717,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on handling of location information in multi-path operation - S2-2311965","secretary_remarks":"Response to S2-2311965 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24370,"status":"not treated","reservation_date":"2023-03-11 10:55:03","uploaded":"2023-11-03 12:34:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312892.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312895","title":"Clarification on Cell Reporting in multi-path L2 U2N case","source":"Nokia, Nokia Shanghai Bell","contact":"Saubhagya Baliarsingh","contact-id":98717,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: NG-RAN to report location information for the case of different cells in multi-path operation.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24430,"status":"not treated","reservation_date":"2023-03-11 10:58:28","uploaded":"2023-11-03 12:32:11","revisionof":"","revisedto":"S2-2400160","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":402.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312895.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.9.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312929","title":"Adding architectures on supporting authentication for NSWO using CH with AAA Server via 5GC","source":"ZTE, CableLabs","contact":"Zhendong Li","contact-id":38521,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding the architectures on NSWO support in SNPN using CH AAA server.","secretary_remarks":"Revision of S2-2311816 from S2#159. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24640,"status":"agreed","reservation_date":"2023-03-11 11:47:54","uploaded":"2023-11-03 12:13:42","revisionof":"S2-2311816","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":4987.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-231259","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312929.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.2.15","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312936","title":"Update wording for MAC address conflict","source":"Xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the wording for Ethernet MAC address conflict as above In step 6, also add MAC address conflict detection description as in step 4","secretary_remarks":"Merged into S2-2313723","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24290,"status":"merged","reservation_date":"2023-03-11 11:51:48","uploaded":"2023-11-03 12:26:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":403.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312936.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.7.1.1;","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312971","title":"[DRAFT] Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"Xiaomi Communications","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-2311954 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24190,"status":"not treated","reservation_date":"2023-03-11 11:58:29","uploaded":"2023-11-03 12:26:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312971.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312973","title":"Correction on Layer-2 ID for UE-to-UE Relay Discovery","source":"Xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the different Source Layer-2 IDs are used for 5G ProSe UE-to-UE Relay to distinguish the multiple response messages from multiple Discoveree 5G ProSe End UEs.","secretary_remarks":"Revised in parallel session to S2-2313720.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24110,"status":"revised","reservation_date":"2023-03-11 12:02:12","uploaded":"2023-11-03 12:26:17","revisionof":"","revisedto":"S2-2313720","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":404.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312973.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":" 6.3.2.4.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312975","title":"[DRAFT] Reply LS on LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"Xiaomi Communications","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"LS out","for":"Approval","abstract":"WITHDRAWN: To: CT WG1. CC: SA WG3","secretary_remarks":"Response to S2-2311951. WITHDRAWN","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23960,"status":"withdrawn","reservation_date":"2023-03-11 12:05:01","uploaded":null,"revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2312976","title":"[DRAFT] Reply LS on LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"Xiaomi Communications","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1. CC: SA WG3","secretary_remarks":"Response to S2-2311951 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23970,"status":"not treated","reservation_date":"2023-03-11 12:05:02","uploaded":"2023-11-03 12:26:17","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2312976.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313039","title":"[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Reply to the LS on 5G ProSe UE-to-UE relay discovery with security aspects (S2-2311951)","secretary_remarks":"Response to S2-2311951 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23980,"status":"not treated","reservation_date":"2023-03-11 13:13:22","uploaded":"2023-11-03 21:18:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313039.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313040","title":"Updates for 5G ProSe UE-to-UE Relay Discovery with Model B","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding an additional parameter to the Solicitation and Response messages sent between the 5G ProSe UE-to-UE Relay and the Discoveree 5G ProSe End UE. Updated the list of Terms with the new parameter.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24140,"status":"not treated","reservation_date":"2023-03-11 13:13:22","uploaded":"2023-11-03 21:18:49","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":405.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313040.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"3.1, 5.8.4.2, 6.3.2.4.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313059","title":"DP on misalignment between PTW and Satellite Coverage Window.","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"discussion","for":"Discussion","abstract":"Discusses the issue and solution of the misalignment between PTW and Coverage Window.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24530,"status":"noted","reservation_date":"2023-03-11 13:19:10","uploaded":"2023-11-03 14:26:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313059.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313060","title":"[DRAFT] Reply LS on misalignment between PTW and Coverage Window","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2","secretary_remarks":"Response to S2-2311936. Merged into S2-2313483","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24490,"status":"merged","reservation_date":"2023-03-11 13:19:10","uploaded":"2023-11-03 14:26:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313060.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313061","title":"EDRX parameters determination in satellite discontinous coverage","source":"Xiaomi","contact":"Yuxin MAO","contact-id":91413,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify to make clearly that eDRX parameters determination can combine with the Unavailability Period Duration and Start of Unavailability Period to ensure there is at least one paging occasion(PTW) within the coverage period.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24540,"status":"noted","reservation_date":"2023-03-11 13:19:10","uploaded":"2023-11-03 14:26:23","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.401","crspecversion":"18.3.0","workitem":[{"winame":"IoT_SAT_ARCH_EPS"}],"crnumber":3759.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313061.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.13.8.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313113","title":"[DRAFT] Reply LS on misalignment between PTW and Coverage Window","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Provides answer to LS on misalignment between PTW and Coverage Window from RAN WG2","secretary_remarks":"Response to S2-2311936. Merged into S2-2313483","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24500,"status":"merged","reservation_date":"2023-03-11 14:16:04","uploaded":"2023-11-03 19:02:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313113.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313176","title":"[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects.","secretary_remarks":"Response to S2-2311951 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23990,"status":"not treated","reservation_date":"2023-03-11 18:12:43","uploaded":"2023-11-03 18:29:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313176.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313177","title":"Correction of the Destination Layer-2 ID for UE-to-UE Relay disocvery response message","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To add clarifications to clause 5.8.4.2 on the setting of Destination Layer-2 ID, in case the User Info IDs of the discoverer 5G ProSe End UE and discoveree 5G ProSe End UE are in the protected direct discovery set of the UE-to-UE Relay Discovery Response message.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24150,"status":"not treated","reservation_date":"2023-03-11 18:15:31","uploaded":"2023-11-03 18:29:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":406.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313177.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.8.4.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313181","title":"[DRAFT] Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay.","secretary_remarks":"Response to S2-2311954 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24200,"status":"not treated","reservation_date":"2023-03-11 18:20:16","uploaded":"2023-11-03 18:29:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313181.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313183","title":"[DRAFT] Reply LS on L2ID and User Info for L2 based U2U","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on L2ID and User Info for L2 based U2U.","secretary_remarks":"Response to S2-2311980. Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23820,"status":"not treated","reservation_date":"2023-03-11 18:23:07","uploaded":"2023-11-03 18:29:42","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_160_Chicago_2023-11\/Docs\/S2-2313183.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313184","title":"[DRAFT] Reply LS on handling of location information in multi-path operation","source":"Qualcomm Incorporated","contact":"Hong Cheng","contact-id":25668,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on handling of location information in multi-path operation.","secretary_remarks":"Response to S2-2311965 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24380,"status":"not treated","reservation_date":"2023-03-11 18:25:40","uploaded":"2023-11-03 18:29:42","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313184.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313211","title":"[DRAFT] Reply LS on handling of location information in multi-path operation","source":"Philips International B.V.","contact":"Walter Dees","contact-id":54701,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2","secretary_remarks":"Response to S2-2311965 Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24390,"status":"not treated","reservation_date":"2023-03-11 20:52:58","uploaded":"2023-11-03 23:37:05","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_relay_enh-Core"},{"winame":" 5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313211.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313212","title":"Addition of Location Reporting for multi-path L2 U2N Relay","source":"Philips International B.V.","contact":"Walter Dees","contact-id":54701,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding specification text to clause 6.9.3 about NG-RAN reporting both cell IDs of direct path and indirect path, and an identifier of the Layer-2 U2N Relay UE to AMF, in case of multi-path L2 U2N Relay communication.","secretary_remarks":"Not Handled","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24440,"status":"not treated","reservation_date":"2023-03-11 20:55:06","uploaded":"2023-11-03 23:37:05","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":407.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313212.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":true,"cn_affected":true,"clauses_affected":"6.9.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313232","title":"LS from SA WG3: Reply LS on providing a new 5G-GUTI in the REGISTRATION REJECT message to the UE","source":"SA WG3","contact":"Saurabh Khare","contact-id":90999,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 would like to thank CT WG1 for their LS C1-236521\/S3-234448 LS on providing a new 5G-GUTI in the REGISTRATION REJECT message to the UE SA WG3 would like CT WG1 to know that SA WG3 discussed the LS in C1-236521\/S3-234448 and decided to remove the GUTI from the Registration Reject and updated the SA WG3 specs. Agreed CR is available on the S3 235045.","secretary_remarks":"Postponed.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24690,"status":"postponed","reservation_date":"2023-12-11 18:08:10","uploaded":"2023-11-12 18:09:06","revisionof":"","revisedto":"S2-2400024","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"SA WG2","lsoriginalls":"S3-235071","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313232.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313239","title":"LS from SA WG3: Reply LS on NSWO support in SNPN using CH AAA server","source":"SA WG3","contact":"Tao Wan","contact-id":79074,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 thanks SA WG2 for the reply LS. SA WG3 has taken SA WG2 comments into consideration and agreed the attached SA WG3 CR (S3-235077). Regarding SA WG2 question on decorated NAI, SA WG3 does not have any additional feedback. SA WG3 kindly asks SA WG2 to take the above information into consideration and update TS 23.501 accordingly. Action: SA WG3 kindly asks SA WG2 to take the above feedback into consideration and update TS 23.501 accordingly.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24650,"status":"noted","reservation_date":"2023-12-11 18:08:10","uploaded":"2023-11-12 18:09:06","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1, CT WG4","lsoriginalls":"S3-235109","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313239.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313483","title":"[DRAFT] LS on misalignment between PTW and Coverage Window","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN WG2 that eDRX and DisCo is already handled by the MME\/AMF.","secretary_remarks":"Revision of S2-2312788, merging S2-2313060, S2-2313113 and S2-2312436. Revised in parallel session to S2-2313795.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24470,"status":"revised","reservation_date":"2023-11-16 19:56:47","uploaded":"2023-11-20 12:31:11","revisionof":"S2-2312788","revisedto":"S2-2313795","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313483.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313717","title":"SNPN N3WIF FQDN terminology alignment with stage 3","source":"Ericsson, Huawei, Qualcomm","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Remove the editor s note, and align the terminology with 23.003.","secretary_remarks":"Revision of S2-2312507, merging S2-2312216 and S2-2312617. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24610,"status":"agreed","reservation_date":"2023-11-16 19:57:47","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312507","revisedto":"","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":4786.0,"crrevision":3.0,"crcategory":"F","tsg_crp":"SP-231259","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313717.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.30.2.12","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313718","title":"Reply LS on SNPN Identifier based N3IWF FQDN (Tdoc: S2-2311962\/C4-234369)","source":"SA WG2","contact":"Naman Gupta","contact-id":93866,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4","secretary_remarks":"Revision of S2-2312215, merging S2-2312506. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24580,"status":"approved","reservation_date":"2023-11-16 19:57:48","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312215","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNPN_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2311962","lsto":"CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313718.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313719","title":"[DRAFT] Reply LS on L2ID and User Info for L2 based U2U","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on L2ID and User Info for L2 based U2U","secretary_remarks":"Revision of S2-2312084. Revised in parallel session to S2-2313796.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23770,"status":"revised","reservation_date":"2023-11-16 19:57:48","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312084","revisedto":"S2-2313796","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"CT WG1, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313719.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313720","title":"Correction on Layer-2 ID for UE-to-UE Relay Discovery","source":"Xiaomi, CATT","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the different Source Layer-2 IDs are used for 5G ProSe UE-to-UE Relay to distinguish the multiple response messages from multiple Discoveree 5G ProSe End UEs.","secretary_remarks":"Revision of S2-2312973. Revised in parallel session to S2-2313797. Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24120,"status":"revised","reservation_date":"2023-11-16 19:57:48","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312973","revisedto":"S2-2313797, S2-2400946","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":404.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313720.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":" 6.3.2.4.3; 5.8.4.2;","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313721","title":"Correction on 5G ProSe UE-to-UE Relay Discovery with Index","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Including the Index associated with the RSC and the Source Layer-2 ID of the discoverer 5G ProSe End UE in the 5G ProSe UE-to-UE Relay Discovery Solicitation message toward the discoveree 5G ProSe End UE.","secretary_remarks":"Revision of S2-2312202. Revised in parallel session to S2-2313798. Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24050,"status":"revised","reservation_date":"2023-11-16 19:57:49","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312202","revisedto":"S2-2313798","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":391.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313721.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313722","title":"[DRAFT] Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","source":"CATT","contact":"Qiang Deng","contact-id":74437,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on 5G ProSe UE-to-UE relay discovery with security aspects","secretary_remarks":"Revision of S2-2312250. Postponed","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23930,"status":"postponed","reservation_date":"2023-11-16 19:57:49","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312250","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313722.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313723","title":"Rejection of L3 U2U Connection Setup when Ethernet MAC address conflict is detected","source":"Huawei, HiSilicon, Samsung, Xiaomi, Interdigital","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To clarify that if L3 Relay UE detects a MAC address conflict, it rejects the direct link establishment rather than accepts the direct link establishment and note that a MAC address conflict can be detected for the Target UE.","secretary_remarks":"Revision of S2-2312793, merging S2-2312936. Revised in parallel session, merging S2-2312206, to S2-2313801.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24270,"status":"revised","reservation_date":"2023-11-16 19:57:49","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312793","revisedto":"S2-2313801","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":401.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313723.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"6.7.1.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313724","title":"[DRAFT] Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"InterDigital Communications","contact":"Jung Je Son","contact-id":96448,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","secretary_remarks":"Revision of S2-2312052. Revised in parallel session to S2-2313799.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24220,"status":"revised","reservation_date":"2023-11-16 19:57:50","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312052","revisedto":"S2-2313799","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313724.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313725","title":"[DRAFT] Reply LS on handling of location information in multi-path operation","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on handling of location information in multi-path operation","secretary_remarks":"Revision of S2-2312081. Revised in parallel session to S2-2313800.","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24320,"status":"revised","reservation_date":"2023-11-16 19:57:50","uploaded":"2023-11-20 12:41:09","revisionof":"S2-2312081","revisedto":"S2-2313800","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313725.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313795","title":"Reply LS on misalignment between PTW and Coverage Window","source":"SA WG2","contact":"Steven Wenham","contact-id":75794,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN WG2 that eDRX and DisCo is already handled by the MME\/AMF.","secretary_remarks":"Revision of S2-2313483. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24480,"status":"approved","reservation_date":"2023-11-20 10:54:25","uploaded":"2023-11-20 12:41:11","revisionof":"S2-2313483","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"IoT_NTN_enh-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2311936","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313795.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313796","title":"Reply LS on L2ID and User Info for L2 based U2U","source":"SA WG2","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on L2ID and User Info for L2 based U2U","secretary_remarks":"Revision of S2-2313719. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":23780,"status":"approved","reservation_date":"2023-11-20 10:54:25","uploaded":"2023-11-20 12:41:11","revisionof":"S2-2313719","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2311980","lsto":"RAN WG2","Cc":"CT WG1, SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313796.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313797","title":"Correction on Layer-2 ID for UE-to-UE Relay Discovery","source":"Xiaomi","contact":"Jianning(Carry) LIU","contact-id":88587,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify that the different Source Layer-2 IDs are used for 5G ProSe UE-to-UE Relay to distinguish the multiple response messages from multiple Discoveree 5G ProSe End UEs.","secretary_remarks":"Revision of S2-2313720. WITHDRAWN","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24130,"status":"withdrawn","reservation_date":"2023-11-20 10:54:25","uploaded":null,"revisionof":"S2-2313720","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":404.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313798","title":"Correction on 5G ProSe UE-to-UE Relay Discovery with Index","source":"Samsung","contact":"Kisuk Kweon","contact-id":80126,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Including the Index associated with the RSC and the Source Layer-2 ID of the discoverer 5G ProSe End UE in the 5G ProSe UE-to-UE Relay Discovery Solicitation message toward the discoveree 5G ProSe End UE.","secretary_remarks":"Revision of S2-2313721. WITHDRAWN","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24060,"status":"withdrawn","reservation_date":"2023-11-20 10:54:25","uploaded":null,"revisionof":"S2-2313721","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"FS_5G_ProSe_Ph2"}],"crnumber":391.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313799","title":"Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","source":"SA WG2","contact":"Jung Je Son","contact-id":96448,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Ethernet MAC address conflict in 5G ProSe Communication via 5G ProSe Layer-3 UE-to-UE Relay","secretary_remarks":"Revision of S2-2313724. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24230,"status":"approved","reservation_date":"2023-11-20 10:54:26","uploaded":"2023-11-20 12:41:11","revisionof":"S2-2313724","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2311954","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313799.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313800","title":"Reply LS on handling of location information in multi-path operation","source":"SA WG2","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[Draft] Reply LS on handling of location information in multi-path operation","secretary_remarks":"Revision of S2-2313725. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24330,"status":"approved","reservation_date":"2023-11-20 10:54:26","uploaded":"2023-11-20 12:41:11","revisionof":"S2-2313725","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2311965","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313800.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2313801","title":"Rejection of L3 U2U Connection Setup when Ethernet MAC address conflict is detected","source":"Huawei, HiSilicon, Samsung, Xiaomi, Interdigital","contact":"Marco Spini","contact-id":8356,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: To clarify that if L3 Relay UE detects a MAC address conflict, it rejects the direct link establishment rather than accepts the direct link establishment and note that a MAC address conflict can be detected for the Target UE.","secretary_remarks":"Revision of S2-2313723, merging S2-2312206. Agreed in parallel session. Block approved","agenda_item_sort_order":109,"ainumber":"9.37","ainame":"Generic Rel-18 LS","tdoc_agenda_sort_order":24280,"status":"agreed","reservation_date":"2023-11-20 10:54:26","uploaded":"2023-11-20 12:41:11","revisionof":"S2-2313723","revisedto":"","release":"Rel-18","crspec":"23.304","crspecversion":"18.3.0","workitem":[{"winame":"5G_ProSe_Ph2"}],"crnumber":401.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-231247","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_160_Chicago_2023-11\/Docs\/S2-2313801.zip","group":"S2","meeting":"S2-160","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]