[{"name":"S2-2310069","title":"LS from SA WG5: LS on the provisioning services specified in SA WG5","source":"SA WG5","contact":"Song Zhao","contact-id":87845,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 is responsible for specification of various management and orchestration aspects related to 3GPP systems. As part of the on-going study on management aspects of NWDAF (FS_MANWDAF), we observed in TS 23.288-i00 the service, procedure and capability containing the term of 'provision' in their names, such as: - Nnwdaf_MLModelProvision services - Procedure for ML Model Provisioning - analytics metadata provisioning capability In OAM terminology the term 'provisioning' represents a combination of Life Cycle Management (LCM) and Configuration Management (CM). According to the SA WG5 TOR, the important areas where SA WG5 is actively involved include CM and LCM. Therefore, we perceive that specification of provisioning is within the scope of SA WG5. The specifications related to provisioning services include (but not limited to): TS 28.531, TS 28.532, TS 28.541. SA WG5 would like to know what provisioning requirements (to be satisfied by OAM specifications\/solutions) have been identified by SA WG2. Action: SA WG5 kindly requests SA WG2 to take into account the scope of responsibilities of SA WG5 (documented in the SA WG5 TOR) and share their expectations\/requirements for specification of provisioning services.","secretary_remarks":"Revision of Postponed S2-2308276 from SA WG2#158. Response drafted in S2-2311255. Final response in S2-2311892","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"replied to","reservation_date":"2023-09-19 06:36:02","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308276","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-232774","lsreply":"S2-2311892","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310069.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310072","title":"LS from CT WG4: Reply LS on Proposed new draft Recommendation Signalling requirements and procedures for bypassing network elements of IMS","source":"CT WG4","contact":"Liu Liu","contact-id":76788,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 thanks ITU Study Group 11 for their LS on Proposed new draft Recommendation 'Signalling requirements and procedures for bypassing network elements of IMS'. CT WG4 acknowledges that how to deal with the network element (such as IMS HSS) with service interruption to alleviate the impact to the served user is not specified. CT WG4 would like to point to ITU Study Group 11 that the IMS Restoration Procedures for the SCC-AS service interruption is specified in clause 6 of 3GPP TS 23.380. Action: CT WG4 kindly asks SA WG2 for SA WG2 s view from normative Stage 2 perspective on the ITU-T LS (C4-231011), and to provide feedback to ITU-T SG11 and CT WG4.","secretary_remarks":"Revision of Postponed S2-2308280 from SA WG2#158. Response drafted in S2-2311188. Final response in S2-2311812","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"replied to","reservation_date":"2023-09-19 06:36:02","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308280","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T Study Group 11, SA WG2","Cc":"ITU-T Study Group 2, CT WG1","lsoriginalls":"C4-231396","lsreply":"S2-2311812","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310072.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310076","title":"LS from CT WG3: Reply LS on removal of unspecified QoS monitoring control option","source":"CT WG3","contact":"Xiaoyun Zhou","contact-id":77294,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 thanks SA WG2 for their LS on removal of unspecified QoS monitoring control option, and would like to inform SA WG2 that CT WG3 agrees to remove the option to report when the PDU Session is released from Rel-16 onwards. Action: CT WG3 asks SA WG2 to take the above information into account.","secretary_remarks":"Revision of Postponed S2-2308296 from SA WG2#158. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2023-09-19 06:36:02","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308296","revisedto":"","release":"Rel-16","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG4","lsoriginalls":"C3-232192","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310076.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310077","title":"LS from CT WG3: LS on Support of multiple UEs in Northbound APIs","source":"CT WG3","contact":"Narendranath Durga Tangudu","contact-id":73161,"tdoctype":"LS in","for":"Action","abstract":"CT WG3 is currently working under NBI18 WID (which is a stage 3 only WI), on specifying the technical enhancements to the 3GPP Northbound and Application Layer interfaces and APIs. In this regard, CT WG3 is discussing the support of list of UE(s) in various northbound APIs like NEF APIs in TS 29.522, SCEF APIs in TS 29.122, SEAL APIs in TS 29.549 etc. Currently, various northbound APIs only support either single UE information (external Identifier, MSISDN, Gpsi etc) or group of UEs (external group identifier, VAL group Identifier, etc). The northbound function (NEF, SCEF, Edge Enabler Server, SEAL server, etc) receiving the API request, may use the UE(s) information to further invoke the downstream 3GPP network services to fulfil the AF s request. When the AF has to invoke a northbound API targetting multiple UE(s) that do not belong to same group (identified by a group identifier like external group identifier), then the AF can either invoke the multiple northbound API individually for each UE or modify\/create an external group for this set of UE(s) and invoke the northbound API for the created\/modified group. CT WG3 has also observed that other APIs allow a third option, namely providing a list of UE(s) as the target of the request (instead of a GPSI or a group id). Question 1: Do SA WG2 and SA WG6 believe that the addition of this option (i.e. the option to provide a list of UE(s) as the target) to any API can be implemented by stage 3 as a signalling optimization or are there pros and cons that render it necessary to determine the existence (or not) of this option in stage 2 on a case by case basis? The implications on the E2E procedures (whether downstream APIs, e.g. 5GC APIs, should also be updated to support this list of UE(s) mechanism) should also be considered. Action: CT WG3 kindly asks SA WG2 and SA WG6 to clarify on the above question and update the specifications accordingly (if required).","secretary_remarks":"Revision of Postponed S2-2308299 from SA WG2#158. Response drafted in S2-2310302. Final response in S2-2311257","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"replied to","reservation_date":"2023-09-19 06:36:02","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308299","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG6","Cc":"","lsoriginalls":"C3-232510","lsreply":"S2-2311257","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310077.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310082","title":"LS from SA WG6: Reply LS on Alignment of SA3 security aspects for Personal IoT Networks","source":"SA WG6","contact":"Michel Roy","contact-id":72161,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 thanks SA WG3 for kindly discussing LS S6-230792\/S3-231714 and providing the LS response. SA WG6 provides the following guidance to SA WG3 to consider and develop appropriate security solutions addressing PINAPP. {. . .}","secretary_remarks":"Revision of Postponed S2-2308346 from SA WG2#158. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10080,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308346","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG2","lsoriginalls":"S6-232076","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310082.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310083","title":"LS from GSMA TSGUEWIFI: LS reply to SA WG2 on 3GPP and non-3GPP interworking information in VoWiFi","source":"GSMA TSGUEWIFI","contact":"Di Zhang","contact-id":96672,"tdoctype":"LS in","for":"Action","abstract":"GSMA TSG UEWIFI would like to thank SA WG2 for the reply LS in S2-2307898\/UEWiFi10_003 on 3GPP and non-3GPP interworking capabilities. SA WG2 pointed out that specifications 3GPP TS 24.167 already have mechanisms that indicate to the UE which types of handovers are allowed, i.e., Allow_Handover_PDN_connection_WLAN_and_EPS, Allow_Handover_PDU_session_non-3GPP_and_NG-RAN, Allow_Handover_PDN_connection_non-3GPP_and_NG-RAN. However, 3GPP TS 24.167 does not completely address the problem statement that the UEWIFI group formulated. Firstly, configuration of Management Objects that inform the UE of the supported handovers are cumbersome and prone to failures. That is: These Management Objects are pre-configured by OEM and\/or configured with OTA (over the Air) methods by OEM. This makes these Management Objects static . Therefore, whenever network policy changes the MNO has to share the parameters with the OEM and the OEM needs to update this with OTA methods. Updating Management Objects this way has a number of limitations, e.g., it can take a long time to update all devices in the affected operators network, OEM may not support such updates after some time. OTA upgrade is not a reliable way as end users may ignore OTA upgrade notification. The update success rate is not guaranteed. If the operator doesn t support Device Management protocol, configurations cannot be updated by using OTA methods, then UE will encounter a handover failure and call drop when choose an undesired target network. Secondly, configuration of Management Objects that inform the UE of the supported handovers do not allow different handover policy for different parts of the network. The Management Objects don t allow for differentiating policies between different regions of a country served by the operator. It is difficult for operator to deploy nationwide 5G coverage in the near future (or in some cases never). Operators may want to have different cellular and Wi-Fi handover policy in different parts of the network, e.g. allow HO to VoNR in sub-set of the regions covered by their network. The Management Objects only apply to IMS PDN connection, non-IMS services which use other PDN connections will also need the interworking indication to make handover decision. Thirdly, configuration of Management Objects that inform the UE of the supported handovers are not useful in roaming scenarios. The Management Objects don t allow for differentiation handover capability when cellular and WLAN network belongs to different operators. When UE roams to cellular network of PLMN B and simultaneously connected to ePDG of PLMN A, there is no way to decide whether handover of IMS PDN connection from ePDG of PLMN A to SMF of PLMN B is supported depends on these parameters. In addition, though the procedures specified in 3GPP TS 23.502 for transfer of PDU session from non-3GPP access (WLAN) to 5GS or EPS using EPS fallback provides a solution when network doesn t support VoNR. However, when UE initiates a IMS voice call over WiFi and it is camped on NR simutaneously, this solution can not solve the handover issue when network doesn t support the handover from VoWiFi to VoNR but support VoNR. Therefore, we propose to convey the 3GPP and non-3GPP interworking handover indications from cellular network and\/or Wi-Fi network to UE rather than using Management Objects. {. . .} Actions: GSMA TSG UEWIFI kindly requests SA WG2 to take the information above into account and define possible solutions for the proposals.","secretary_remarks":"Revision of Postponed S2-2308349 from SA WG2#158. Response drafted in S2-2311138. Final response in S2-2311813","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"replied to","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308349","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"UEWIFI11_005","lsreply":"S2-2311813","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310083.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310085","title":"LS from SA WG3: Reply LS on Alignment of SA3 security aspects for Personal IoT Networks","source":"SA WG3","contact":"Longhua Guo","contact-id":80179,"tdoctype":"LS in","for":"Information","abstract":"SA WG3 thanks SA WG6 for the reply LS on Alignment of SA WG3 security aspects for Personal IoT Networks. SA WG3 has not considered developing security mechanisms addressing PINAPP security requirements specified in TS 23.542.","secretary_remarks":"Revision of Postponed S2-2308353 from SA WG2#158. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 15:04:36","revisionof":"S2-2308353","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2","lsoriginalls":"S3-234158","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310085.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310088","title":"LS from ITU-T SG11: LS on initiation of new work item Q.SP-twqos 'Signalling Requirements and Protocol procedures for two-way QoS mechanism between access networks and core networks in IMT-2020 network and beyond'","source":"ITU-T SG11","contact":"Ritu Ranjan Mittar","contact-id":71891,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the initiation of new work item 'Signalling Requirements and Protocol procedures for two-way QoS mechanism between access networks and core networks in IMT-2020 network and beyond' in Q6\/11.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10040,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG13, SA WG2","Cc":"","lsoriginalls":"SG11-LS86","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310088.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310090","title":"LS from CT WG1: Reply LS on applicability of UAC for Network Controlled Repeater","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":85785,"tdoctype":"LS in","for":"Information","abstract":"CT WG1 thanks RAN WG2 for their LS. CT WG1 would like to inform RAN WG2 of the agreement that an NCR-MT node skips UAC as per the attached.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10050,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"SA WG2","lsoriginalls":"C1-236447","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310090.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310106","title":"LS from CT WG4: IETF HTTP RFCs obsoleted by RFCs 9110, 9111 and 9113","source":"CT WG4","contact":"Bruno Landais","contact-id":68755,"tdoctype":"LS in","for":"Information","abstract":"5GC specifications refer to several HTTP RFCs that have been obsoleted by new IETF RFCs: - IETF RFC 9110 ('HTTP Semantics', published in June 2022) obsoletes RFCs 7230, 7231, 7232, 7235, 7694. - IETF RFC 9111 ('HTTP Caching', published in June 2022) obsoletes RFC 7234. - IETF RFC 9112 ('HTTP\/1.1', published in June 2022) obsoletes RFC 7230. - IETF RFC 9113 ('HTTP\/2', published in June 2022) obsoletes RFC 7540. Following an analysis of the changes introduced in the new RFCs, CT WG4 has agreed the attached 29.500 CR uplifting the obsoleted HTTP references to the new IETF RFCs from Rel-18 onwards. CT WG4 plans to update the HTTP references of all its TSs for 5GC SBIs in Q4 (TS Rapporteurs have been tasked to bring a related CR to their specifications). CT WG4 kindly asks CT WG1, CT WG3, SA WG3, SA WG4 and SA WG5 to take the above information into account and consider uplifting the HTTP references in their own specifications for 5GC SBIs from Rel-18 onwards.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10060,"status":"noted","reservation_date":"2023-09-19 06:36:03","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG3, SA WG3, SA WG4, SA WG5","Cc":"TSG CT, TSG SA, SA WG2","lsoriginalls":"C4-233513","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310106.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310116","title":"LS from RAN WG2: LS to SA2 on TX Profile for SL CA","source":"RAN WG2","contact":"Zhibin Wu","contact-id":92895,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 has discussed the backward compatibility issue for groupcast\/broadcast of Rel-18 SL CA and reached the following agreement on TX profile extension for SL CA: When the upper layer provides multiple carriers in service to carrier mapping information to AS, we need TX profile extension to inform whether the transmission corresponding the service is backward compatible or not. If backward compatible is needed, only legacy carrier is used for transmission when PDCP duplication is not used. If PDCP duplication is used, at least legacy carrier is used. FFS whether to use PDCP duplication or not is up to UE implementation. RAN WG2 respectfully asks SA WG2 to take the above agreement into account in SA WG2 work.","secretary_remarks":"Responses drafted in S2-2310190, S2-2310829. Final response in S2-2311811","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"replied to","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2309155","lsreply":"S2-2311811","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310116.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310117","title":"LS from RAN WG2: Reply LS on carrier mapping for unicast SL CA","source":"RAN WG2","contact":"Giwon Park","contact-id":80146,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 would like to thank SA WG2 regarding the response LS on carrier mapping for unicast SL CA. RAN WG2 discussed the answers provided by SA WG2 during RAN WG2#123 and would like to provide the following RAN WG2 agreements on SA WG2 s question and carrier mapping for unicast SL CA. Question 1: According to TS 24.588, V2X layer is only provisioned with a mapping between service identifier and initial L2 address used for unicast. But service identifier is invisible to AS-layer, and the initial L2 ID will only be used in DCR and be replaced by a self-chosen L2 ID in PC5-S link establishment procedure. Then, after L2 ID changes, whether\/how can UE's AS layer obtain the mapping between L2 ID and frequencies? Agreement on SA WG2 question: 1: On Question 1 of S2-2307794, reply SA WG2 'RAN WG2's question 1 is intended to discuss after PC5 link establishment. And RAN WG2 assume that the AS layer may maintain a mapping between old L2 ID (before PC5 link establishment) and new L2 ID (after PC5 link establishment) by its implementation'. Agreement on SL CA before UC link is established: 1: SL CA is not applied before UC link is established. Action: To SA WG2: RAN WG2 respectfully asks SA WG2 to take the above information into account in related work and whether any issue on the RAN WG2 assumption is observed by SA WG2.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"R2-2309156","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310117.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310124","title":"LS from RAN WG3: Reply LS on DTLS for SCTP next steps and request for input","source":"RAN WG3","contact":"Gino Masini","contact-id":23120,"tdoctype":"LS in","for":"Information","abstract":"RAN WG3 thanks IETF TSVWG for the update on this issue. RAN WG3 would like to provide answers to the following questions. Q1. Confirm whether implementation possibilities in both userland and kernel implementations of SCTP are required for the solution, and whether any additional concerns with implementing either of the solutions are perceived. A1. SCTP implementation details are typically not discussed in RAN WG3. Q2. Confirm that the interpretation of the requirements is correct, i.e., which SCTP message size would be required to be supported. In other words, are the theoretical maximum message size mentioned above relevant to be supported, or would it be sufficient that a smaller message size is supported? [IETF TSVWG text] A2. RAN WG3 would like to confirm our previous LS: we do not expect to limit the maximum message size of application protocols. For this reason, any solution with a limit on message size will not meet RAN WG3 requirements.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10070,"status":"noted","reservation_date":"2023-09-19 06:36:04","uploaded":"2023-09-20 14:43:36","revisionof":"","revisedto":"","release":"Rel-15","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IETF TSVWG","Cc":"SA WG3, SA WG2, CT WG1, CT WG4","lsoriginalls":"R3-234497","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310124.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310186","title":"Discussion about LS from RAN WG2 on TX Profile for SL CA.","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"discussion","for":"Discussion","abstract":"This paper discusses the LS from RAN WG2 on TX Profile for SL CA (S2-2310116\/R2-2309155).","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"noted","reservation_date":"2023-09-26 02:08:37","uploaded":"2023-09-29 13:24:19","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310186.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310190","title":"[DRAFT] Reply LS on TX Profile for SL CA","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on TX Profile for SL CA","secretary_remarks":"Response to S2-2310116. Revised in parallel session to S2-2311808.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"revised","reservation_date":"2023-09-26 02:10:32","uploaded":"2023-09-29 13:24:19","revisionof":"","revisedto":"S2-2311808","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310190.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310191","title":"Support of sidelink carrier aggregation and the related TX Profile extension","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 3.1 - Extend 'NR Tx Profile' for SL CA. 5.1.2.1 - Make NR Tx Profile for broadcast and groupcast associated with GeoArea. - Add NOTE about that configuration related to PC5 DRX in the NR Tx Profile for BC\/GC does not have to be associated with GeoArea. 5.4.1.1.3 - Clarify that the radio frequencies are determined based on the V2X service type associated with the PC5 QoS Flow based on the configuration as described in clause 5.1.2.1 and the radio frequencies for the PC5 QoS Flow are provided to the AS layer (as explained by Answer 2 in S2-2307794 'Reply LS to RAN WG2 on carrier mapping for unicast SL CA'). - Describe NR Tx Profile provided by the V2X layer to the AS layer. 5.X - Describe support of SL CA operations 6.3.1 and 6.3.2 - Clarify that the radio frequency information is provided by the V2X layer to the AS layer.","secretary_remarks":"Revised in parallel session to S2-2311809.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"revised","reservation_date":"2023-09-26 02:14:12","uploaded":"2023-09-29 13:24:35","revisionof":"","revisedto":"S2-2311809","release":"Rel-18","crspec":"23.287","crspecversion":"18.1.0","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":191.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310191.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 5.1.2.1, 5.4.1.1.3, 5.X (new), 6.3.1, 6.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310302","title":"[DRAFT] LS on Support of multiple UEs in Northbound APIs","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"LS on Support of multiple UEs in Northbound APIs","secretary_remarks":"Response to S2-2310077. Revised to S2-2311257.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"revised","reservation_date":"2023-09-27 12:32:46","uploaded":"2023-09-29 12:48:58","revisionof":"","revisedto":"S2-2311257","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NBI18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310302.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310757","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the format of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AFs within agreed SLAs and allowed by local policy\/regulation.","secretary_remarks":"Revised to S2-2311259.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"revised","reservation_date":"2023-09-28 17:14:14","uploaded":"2023-09-29 20:28:45","revisionof":"","revisedto":"S2-2311259","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":5011.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310757.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.20, 7.2.8","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310758","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the format of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AFs within agreed SLAs and allowed by local policy\/regulation.","secretary_remarks":"Revised to S2-2311260.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"revised","reservation_date":"2023-09-28 17:14:15","uploaded":"2023-09-29 20:28:45","revisionof":"","revisedto":"S2-2311260","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"TEI18"},{"winame":" EDGEAPP"}],"crnumber":4509.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310758.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.3.2.13, 4.15.10A(new), 5.2.6.27.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310828","title":"TX Profile for SL CA","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: An extended Tx profile is introduced to indicate whether the service supports SL CA.","secretary_remarks":"Merged into S2-2311810.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"merged","reservation_date":"2023-09-29 02:02:47","uploaded":"2023-09-29 15:23:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.287","crspecversion":"18.1.0","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":192.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310828.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 5.1.2.1, 5.4.1.1.3","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310829","title":"[DRAFT] Reply LS on Tx Profile for SL CA","source":"OPPO","contact":"Fei Lu","contact-id":87831,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2310116\/R2-2309155","secretary_remarks":"Response to S2-2310116. Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"noted","reservation_date":"2023-09-29 02:02:55","uploaded":"2023-09-29 15:23:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310829.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2310852","title":"Support of sidelink carrier aggregation and the related TX Profile extension (new one)","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 3.1 - Add 'NR Tx Profile for Backward Compatibility' for SL CA. 5.1.2.1 - Add 'NR Tx Profile for Backward Compatibility' 5.4.1.1.3 - Clarify that the radio frequencies are determined based on the V2X service type associated with the PC5 QoS Flow based on the configuration as described in clause 5.1.2.1 and the radio frequencies for the PC5 QoS Flow are provided to the AS layer (as explained by Answer 2 in S2-2307794 'Reply LS to RAN WG2 on carrier mapping for unicast SL CA'). - Describe that NR Tx Profile for Backward Compatibility provided by the V2X layer to the AS layer. 5.X - Describe support of SL CA operations 6.3.1 and 6.3.2 - Describe that the NR Tx Profile for Backward Compatibility provided by the V2X layer to the AS layer. - Clarify that the radio frequency information is provided by the V2X layer to the AS layer.","secretary_remarks":"Noted in parallel session","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2023-09-29 05:42:18","uploaded":"2023-09-29 13:24:35","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.287","crspecversion":"18.1.0","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":193.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2310852.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":true,"clauses_affected":"3.1, 5.1.2.1, 5.4.1.1.3, 5.X (new), 6.3.1, 6.3.2","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311138","title":"[DRAFT] Reply LS on 3GPP and non-3GPP interworking information in VoWiFi","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Responds to LSs from GSMA NG and GSMA TSGUEWIFI on 3GPP and non-3GPP interworking information in VoWiFi","secretary_remarks":"Response to S2-2310083. Revised to S2-2311258.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2023-09-29 15:01:33","uploaded":"2023-09-29 19:06:08","revisionof":"","revisedto":"S2-2311258","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Network Group(NG), GSMA TSG UEWIFI","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311138.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311188","title":"[DRAFT] Reply LS on Proposed new draft Recommendation 'Signalling requirements and procedures for bypassing network elements of IMS'","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Proposed new draft Recommendation 'Signalling requirements and procedures for bypassing network elements of IMS'","secretary_remarks":"Response to S2-2310072. Revised to S2-2311256.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"revised","reservation_date":"2023-09-29 17:12:00","uploaded":"2023-09-29 17:14:02","revisionof":"","revisedto":"S2-2311256","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, ITU-T STUDY GROUP 11","Cc":"ITU-T Study Group 2, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311188.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311231","title":"NR Tx profile extension for support of SL CA groupcast\/broadcast","source":"Apple","contact":"Sudeep M Vamanan","contact-id":103491,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Added the description that when a V2X service is mapped to more than one frequencies, the NR Tx profile contains information on backward compatibility requirement of the service.","secretary_remarks":"Merged into S2-2311810.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"merged","reservation_date":"2023-09-29 20:17:58","uploaded":"2023-09-29 22:39:34","revisionof":"","revisedto":"","release":"Rel-18","crspec":"23.287","crspecversion":"18.1.0","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":194.0,"crrevision":"","crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311231.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311255","title":"Reply LS on the provisioning services specified in SA5","source":"SA WG2","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: . CC: . Attachments: .","secretary_remarks":"Created at meeting. Response to S2-2310069. Revised in parallel session to S2-2311892.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"revised","reservation_date":"2023-10-10 06:01:30","uploaded":"2023-10-16 11:31:12","revisionof":"","revisedto":"S2-2311892","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_MANWDAF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311255.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311256","title":"[DRAFT] Reply LS on Proposed new draft Recommendation 'Signalling requirements and procedures for bypassing network elements of IMS'","source":"Nokia, Nokia Shanghai Bell","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on Proposed new draft Recommendation 'Signalling requirements and procedures for bypassing network elements of IMS'","secretary_remarks":"Revision of S2-2311188. Revised in parallel session to S2-2311812.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2023-10-10 06:01:30","uploaded":"2023-10-16 11:31:12","revisionof":"S2-2311188","revisedto":"S2-2311812","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4, ITU-T STUDY GROUP 11","Cc":"ITU-T Study Group 2, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311256.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311257","title":"LS on Support of multiple UEs in Northbound APIs","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG3. CC: SA WG6","secretary_remarks":"Revision of S2-2310302. This LS OUT was approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"approved","reservation_date":"2023-10-10 06:01:30","uploaded":"2023-10-16 11:31:12","revisionof":"S2-2310302","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NBI18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310077","lsto":"CT WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311257.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311258","title":"[DRAFT] Reply LS on 3GPP and non-3GPP interworking information in VoWiFi","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Responds to LSs from GSMA NG and GSMA TSGUEWIFI on 3GPP and non-3GPP interworking information in VoWiFi","secretary_remarks":"Revision of S2-2311138. Revised in parallel session to S2-2311813.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2023-10-10 06:01:30","uploaded":"2023-10-16 11:31:12","revisionof":"S2-2311138","revisedto":"S2-2311813","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA Network Group (NG), GSMA TSG UEWIFI","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311258.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311259","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the format of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AFs within agreed SLAs and allowed by local policy\/regulation.","secretary_remarks":"Revision of S2-2310757. Postponed in parallel session.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"postponed","reservation_date":"2023-10-10 06:01:30","uploaded":"2023-10-16 11:31:12","revisionof":"S2-2310757","revisedto":"S2-2312545","release":"Rel-18","crspec":"23.501","crspecversion":"18.3.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":5011.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311259.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311260","title":"Corrections to remove Nnef_UEId Service restrictions","source":"Ericsson, Verizon","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Adding exposure of GPSI in the format of MSISDN in the Nnef_UEId API by mapping the UE address for trusted AFs within agreed SLAs and allowed by local policy\/regulation.","secretary_remarks":"Revision of S2-2310758. Postponed in parallel session.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"postponed","reservation_date":"2023-10-10 06:01:34","uploaded":"2023-10-16 11:31:12","revisionof":"S2-2310758","revisedto":"S2-2312546","release":"Rel-18","crspec":"23.502","crspecversion":"18.3.0","workitem":[{"winame":"EDGEAPP"},{"winame":" TEI18"}],"crnumber":4509.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311260.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311537","title":"[DRAFT] LS on MSISDN exposure to trusted AF","source":"Ericsson","contact":"Magnus Olsson","contact-id":14562,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: SA WG6","secretary_remarks":"Created at meeting. Revised in parallel session to S2-2311814.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"revised","reservation_date":"2023-10-16 08:38:06","uploaded":"2023-10-16 11:31:15","revisionof":"","revisedto":"S2-2311814","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311537.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311808","title":"[DRAFT] Reply LS on TX Profile for SL CA","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on TX Profile for SL CA","secretary_remarks":"Revision of S2-2310190. Revised in parallel session to S2-2311811.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"revised","reservation_date":"2023-10-16 08:40:02","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310190","revisedto":"S2-2311811","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311808.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311809","title":"Support of sidelink carrier aggregation and the related TX Profile extension","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 3.1 - Extend 'NR Tx Profile' for SL CA. 5.1.2.1 - Make NR Tx Profile for broadcast and groupcast associated with GeoArea. - Add NOTE about that configuration related to PC5 DRX in the NR Tx Profile for BC\/GC does not have to be associated with GeoArea. 5.4.1.1.3 - Clarify that the radio frequencies are determined based on the V2X service type associated with the PC5 QoS Flow based on the configuration as described in clause 5.1.2.1 and the radio frequencies for the PC5 QoS Flow are provided to the AS layer (as explained by Answer 2 in S2-2307794 'Reply LS to RAN WG2 on carrier mapping for unicast SL CA'). - Describe NR Tx Profile provided by the V2X layer to the AS layer. 5.X - Describe support of SL CA operations 6.3.1 and 6.3.2 - Clarify that the radio frequency information is provided by the V2X layer to the AS layer.","secretary_remarks":"Revision of S2-2310191. Revised in parallel session to S2-2311810, merging S2-2311231 and S2-2310828.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"revised","reservation_date":"2023-10-16 08:40:02","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2310191","revisedto":"S2-2311810","release":"Rel-18","crspec":"23.287","crspecversion":"18.1.0","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":191.0,"crrevision":1.0,"crcategory":"B","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311809.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311810","title":"Support of sidelink carrier aggregation and the related TX Profile extension","source":"LG Electronics, Apple, OPPO, MediaTek Inc.","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 3.1 - Extend 'NR Tx Profile' for SL CA with Editor's note saying that coding of NR Tx Profile related to backward compatibility is left to Stage 3. 5.1.2.1 - Add NOTE about that Configuration related to backward compatibility requirements for V2X service types in the NR Tx Profiles for broadcast and groupcast can be set per geographical area. 5.4.1.1.3 - Clarify that the radio frequencies are determined based on the V2X service type associated with the PC5 QoS Flow based on the configuration as described in clause 5.1.2.1 and the radio frequencies for the PC5 QoS Flow are provided to the AS layer (as explained by Answer 2 in S2-2307794 'Reply LS to RAN WG2 on carrier mapping for unicast SL CA'). - Describe NR Tx Profile provided by the V2X layer to the AS layer. 5.X - Describe support of SL CA operations 6.3.1 and 6.3.2 - Clarify that the radio frequency information is provided by the V2X layer to the AS layer.","secretary_remarks":"Revision of S2-2311809, merging S2-2311231 and S2-2310828. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"agreed","reservation_date":"2023-10-16 08:40:03","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311809","revisedto":"","release":"Rel-18","crspec":"23.287","crspecversion":"18.1.0","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":191.0,"crrevision":2.0,"crcategory":"B","tsg_crp":"SP-231268","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311810.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311811","title":"Reply LS on TX Profile for SL CA","source":"SA WG2","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on TX Profile for SL CA","secretary_remarks":"Revision of S2-2311808. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"approved","reservation_date":"2023-10-16 08:40:03","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311808","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310116","lsto":"RAN WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311811.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311812","title":"Reply LS on Proposed new draft Recommendation 'Signalling requirements and procedures for bypassing network elements of IMS'","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4, ITU-T Study Group 11. CC: ITU-T Study Group 2, CT WG1","secretary_remarks":"Revision of S2-2311256. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"approved","reservation_date":"2023-10-16 08:40:03","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311256","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310072","lsto":"CT WG4, ITU-T STUDY GROUP 11","Cc":"ITU-T Study Group 2, CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311812.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311813","title":"Reply LS on 3GPP and non-3GPP interworking information in VoWiFi","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA TSG UEWIFI. CC: GSMA Network Group (NG)","secretary_remarks":"Revision of S2-2311258. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"approved","reservation_date":"2023-10-16 08:40:03","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311258","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310083","lsto":"GSMA TSG UEWIFI","Cc":"GSMA Network Group (NG)","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311813.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311814","title":"[DRAFT] LS on MSISDN exposure to trusted AF","source":"Ericsson","contact":"Magnus Olsson","contact-id":14562,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3. CC: SA WG6","secretary_remarks":"Revision of S2-2311537. Revised in parallel session to S2-2311893.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"revised","reservation_date":"2023-10-16 08:40:03","uploaded":"2023-10-16 11:31:16","revisionof":"S2-2311537","revisedto":"S2-2311893","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311814.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311892","title":"Reply LS on the provisioning services specified in SA5","source":"SA WG2","contact":"Juan Zhang","contact-id":73274,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG5","secretary_remarks":"Revision of S2-2311255. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"approved","reservation_date":"2023-10-16 08:40:22","uploaded":"2023-10-16 11:31:17","revisionof":"S2-2311255","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_MANWDAF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2310069","lsto":"SA WG5","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311892.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2311893","title":"LS on MSISDN exposure to trusted AF","source":"SA WG2","contact":"Magnus Olsson","contact-id":14562,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG3, GSMA OPG. CC: SA WG6","secretary_remarks":"Revision of S2-2311814. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10440,"status":"approved","reservation_date":"2023-10-16 08:40:22","uploaded":"2023-10-16 11:31:17","revisionof":"S2-2311814","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG3, GSMA OPG","Cc":"SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_159_Xiamen_2023-10\/Docs\/S2-2311893.zip","group":"S2","meeting":"S2-159","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]