[{"name":"S2-2306265","title":"LS from CT WG1: LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"CT WG1","contact":"Robert Zaus","contact-id":85311,"tdoctype":"LS in","for":"Action","abstract":"At CT WG1#139e, CT WG1 discussed certain requirements related to the UE behaviour in a non-allowed service area. CT WG1 would like to ask SA WG2 for guidance on an issue. The scenario is as follows: 1) The UE is registered to an AMF both via 3GPP and non-3GPP access. The UE is currently in a non-allowed area. The registration area (TAI list) for 3GPP access includes both TAs from the UE's non-allowed area and TAs from the allowed area. The UE is currently in a non-allowed area. 2) The UE has at least 1 PDU session activated via non-3GPP access which cannot be transferred to 3GPP access. 3) The UE is in IDLE mode both for 3GPP and non-3GPP access, when it receives a paging via 3GPP access indicating non-3GPP access and responds with a Service Request. CT WG1 understands that if the UE responds to the paging when it is in a TA belonging to the allowed area, then the UE needs to include the Allowed PDU session status IE (in 23.502 terminology: 'List Of Allowed PDU Sessions') indicating which of the PDU sessions associated with non-3GPP access can be transferred to 3GPP access and may include the Uplink data status IE if it has uplink data pending. Question 1: Does the UE need to include the Allowed PDU session status IE also if it responds to the paging when it is in a non-allowed area? Question 2: Is the UE allowed to include the Uplink data status IE if it has uplink data pending if it responds to the paging when it is in a non-allowed area?. Action: CT WG1 kindly ask SA WG2 to answer CT WG1's question.","secretary_remarks":"Revision of Postponed S2-2303916 from S2#156E. Responses drafted in S2-2306759, S2-2307181, S2-2307367. Final response in S2-2307790","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"replied to","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303916","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-227197","lsreply":"S2-2307790, S2-2403709","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306265.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306270","title":"LS from GSMA 5GMRR: LS to 3GPP on GSMA requirements regarding intermediaries in the roaming ecosystem (Roaming Hub, IPX and RVAS Providers)","source":"GSMA 5GMRR","contact":"Kathleen Leach","contact-id":87129,"tdoctype":"LS in","for":"Action","abstract":"5GMRR would like to provide 3GPP with requirements, as requested by 3GPP, for the major intermediaries and services (Roaming Hub, IPX and RVAS Providers) needed within the roaming ecosystem. The requirements outline support for the use cases that are established in roaming to date and that are also required in 5G SA roaming and interconnect. Actions: GSMA NRG 5GMRR kindly requests 3GPP to consider the above entities in their specifications and the related service requirements for roaming ecosystem intermediaries per role (RH, IPX Provider, RVAS Provider) as provided per separate LSs. Please provide advice on how they can be supported using current specifications. Moreover, the group kindly requests SA WG1, SA WG2 and SA WG3 and CT WG4 to also consider updating their specifications at the earliest possible release in order to support requirements that are currently not covered. This will allow the GSMA to support the use cases that are established in roaming currently and that should be provided for 5G SA roaming and interconnect, too. Please note that the above roles can have overlapping requirements. 5GMRR would like to work together with 3GPP in order to develop solutions that meet these requirements while complying to the 5GS architecture and security specifications.","secretary_remarks":"Revision of Postponed S2-2303923 from S2#156E. Response drafted in S2-2306495. Final response in S2-2307983","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"replied to","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303923","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG1, SA WG2, SA WG3","Cc":"CT WG4","lsoriginalls":"5GMRR Doc 41_37r2","lsreply":"S2-2307983","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306270.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306271","title":"LS from GSMA 5GMRR: LS to 3GPP on IPX Requirements for 5GS Roaming","source":"GSMA 5GMRR","contact":"PRADEEP BHARDWAJ","contact-id":78621,"tdoctype":"LS in","for":"Action","abstract":"GSMA 5GMRR thanks SA WG3 for their reply LS (S3-231389) on PRINS middle boxes. This LS response focuses on the requirements from IPX providers, one of the roles in the roaming eco-system. Actions: GSMA 5GMRR kindly asks 3GPP to take the following actions: SA WG1 to update their specifications in order to support IPX provider requirements that are currently not covered. SA WG2 to enhance the 5G architecture to meet the IPX provider requirements. SA WG3 to define a security solution that includes the IPX providers requirements","secretary_remarks":"Revision of Postponed S2-2303924 from S2#156E. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"postponed","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303924","revisedto":"S2-2308271","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3","Cc":"TSG SA, CT WG4","lsoriginalls":"5GMRR#41 Doc 38r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306271.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306272","title":"LS from GSMA 5GMRR: LS Roaming Value Added Service Requirements","source":"GSMA 5GMRR","contact":"Gery Verwimp","contact-id":20103,"tdoctype":"LS in","for":"Action","abstract":"This LS focusses on one of the three roles in the roaming eco-system, namely roaming value-added service (RVAS) providers. Actions: GSMA NRG 5GMRR kindly requests 3GPP to consider the attached service requirements from RVAS providers. GSMA 5GMRR kindly asks 3GPP to determine how the 5G specifications can be adapted to support these requirements. GSMA 5GMRR asks 3GPP to take note of the current sponsored roaming facilitation using dual or multi-IMSI profiles on the SIM, and advise on any concerns with respect to authentication or concealment algorithms. SA WG1, SA WG2, and SA WG3 are kindly asked to take into account the above requirements of GSMA 5GMRR to enable RVAS providers.","secretary_remarks":"Revision of Postponed S2-2303925 from S2#156E. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"postponed","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303925","revisedto":"S2-2308272","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3","Cc":"TSG SA, CT WG4","lsoriginalls":"5GMRR Doc 41_39r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306272.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306273","title":"LS from GSMA 5GMRR: LS with Roaming Hubbing requirements and LS response to 3GPP SA3 LS (S3-214456) on 5GS Roaming Hubbing","source":"GSMA 5GMRR","contact":"Pieter Veenstra","contact-id":86411,"tdoctype":"LS in","for":"Action","abstract":"This LS lists Roaming Hubbing specific requirements and responds to SA WG3 LS on 5GS roaming hubbing (S3-214456). Actions: GSMA NRG 5GMRR kindly requests 3GPP to consider the above service requirements for roaming hubs and to provide advice on how these requirements can be supported using current specifications. Moreover, the group kindly requests SA WG1, SA WG2 and SA WG3, and CT WG4 to update their specifications in order to support requirements that are currently not covered to support the RH use cases that are established in roaming to date and that should be provided for 5G SA roaming and interconnect, too. 5GMRR would like to work together with 3GPP in order to develop solutions that meet these requirements while complying to the 5GS architecture and security specifications.","secretary_remarks":"Revision of Postponed S2-2303926 from S2#156E. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"postponed","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303926","revisedto":"S2-2308273","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, SA WG3","Cc":"TSG SA, CT WG4","lsoriginalls":"5GMRR Doc 41_40r4","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306273.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306274","title":"LS from GSMA 5GMRR: LS on GSMA 5GMRR Working solution assumption on L-PRINS and Data Session Control","source":"GSMA 5GMRR","contact":"Ahmad Muhanna","contact-id":84435,"tdoctype":"LS in","for":"Action","abstract":"This LS describes a working solution assumption aiming to converge the needs of a service provider and the security architecture as put forward in the 5G SA roaming eco-system. Action to SA WG2: GSMA 5GMRR kindly requests SA WG2 to consider the Service Provider Data Session Control call flow in this LS and to provide feedback.","secretary_remarks":"Revision of Postponed S2-2303927 from S2#156E. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"postponed","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303927","revisedto":"S2-2308274","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3, CT WG4","Cc":"TSG SA, SA WG1","lsoriginalls":"5GMRR Doc 41_41r3","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306274.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306276","title":"LS from CT WG4: LS on UE memory available for SMS","source":"CT WG4","contact":"Ulrich Wiehe","contact-id":105524,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 have agreed the attached CR to TS 29.503, allowing the SMSF to report the 'UE-Memory-available' indication to the UDM by means of the SMSF Registration Update service operation, as a trigger for the SMS Alerting. CT WG4 have noted that 23.502 in table 4.15.3.1-1 suggests that the 'UE memory available for SMS' event is determined and reported to UDM by the AMF, while actually this can only be done by the SMSF. Action: CT WG4 kindly ask SA WG2 to update 23.502 inline with the agreed attached CR.","secretary_remarks":"Revision of Postponed S2-2303938 from S2#156E. Response drafted in S2-2307058. Final response in S2-2307793","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10600,"status":"replied to","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303938","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C4-230625","lsreply":"S2-2307793","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306276.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306279","title":"LS from SA WG3: LS Reply on PRINS middle boxes","source":"SA WG3","contact":"Alf Zugenmaier","contact-id":52494,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank GSMA 5GMRR for the LS on PRINS middle boxes (5GMRR#40 Doc 05 \/ S3-230606, see attached). 5GMRR LS states that: Sometimes, RHs are tasked with per-subscriber bandwidth management. In the event of exhaustion of a subscriber s data quota, the RH may need to trigger appropriate signalling, both towards the VPLMN SEPP and the HPLMN SEPP, without undue delay, that results in the disconnection of the subscriber s PDU session. SA WG3 would like to point out that this kind of session management as well as the concept of intermediaries originating signalling messages are not covered by the current 5G architecture. More generally, if there is a requirement for intermediaries to generate arbitrary messages within the context of other use cases that are currently not described, there may be further security issues, e.g. with subscriber privacy, if intermediaries are allowed to ask for subscriber location. SA WG3 would like to request SA WG2 to verify whether this kind of message injection would be aligned with 5G system architecture and procedures. Independently, SA WG3 would like to inform 5GMRR that SA WG3 believes that the potential for state mismatch between cNF and pNF may also have security impacts. SA WG3 would like to inform GSMA 5GMRR that SA WG3 is willing to work with 5GMRR to enable an end to end secure solution. However, a stable and comprehensive set of requirements is necessary. SA WG3 has included a potential solution (see attached S3-231419) that is under discussion (i.e. not agreed yet) to understand, whether this would provide the required features as required by GSMA 5GMRR. Further analysis of the solution will take place in SA WG3 to fully understand the security and privacy impact. As the error handling is considered stage 3 work, SA WG3 would like to request CT WG4 to consider specifying the mechanisms necessary for the error reporting requested by 5GMRR. Action: SA WG3 would like to kindly ask SA WG2 to consider whether the procedure proposed by GSMA is aligned with the 5G system architecture.","secretary_remarks":"Revision of Postponed S2-2303969 from S2#156E. Response drafted in S2-2307900. Final response in S2-2307789","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"replied to","reservation_date":"2023-04-25 07:34:53","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303969","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA 5GMRR, CT WG4, SA WG2","Cc":"GSMA DESS","lsoriginalls":"S3-231389","lsreply":"S2-2307789","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306279.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306281","title":"LS from SA WG4: An Invitation to the SA WG4 Gender Diversity Committee Meetings","source":"SA WG4","contact":"Nikolai Leung","contact-id":38562,"tdoctype":"LS in","for":"Action","abstract":"The SA WG4 Gender Diversity Committee is an informal group that was initiated in 2018 by some delegates and an SA WG4 Vice Chair to discuss and improve gender diversity in SA WG4 and the industry at large. The Committee had been meeting regularly since then until COVID travel restrictions prevented in person meetings. Now, with face-to-face meetings resuming, the Committee has re-started its regular dinner meetings and also invited the SA WG2 and SA WG3 WGs to join at SA WG4#122 in Athens. The attached Tdoc provides the Committee meeting report provided as FYI. Based on interest expressed at this week s meeting, the Committee plans to meet every Tuesday evening (7:30-10:00pm) of our face-to-face meetings and invites everyone attending other co-located 3GPP WGs to join our dinner meetings. One instantiation of this effort is SA WG4 planning to send out an invitation for May 23, 2023 (7:30-10:00pm CEST) to the SA WGs co-located at the Berlin meetings. We would appreciate you sharing this information with your members so that we can gauge the level of interest soon. We are asking the meeting host to reserve us a hotel meeting room to have our dinner meeting on the 23rd. Action: The SA WG4 Gender Diversity Committee asks the SA WGs to take our invitation into consideration and, if interested, RSVP to any upcoming invitations at future co-located meetings.","secretary_remarks":"Revision of Postponed S2-2303975 from S2#156E. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"noted","reservation_date":"2023-04-25 07:34:54","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303975","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG1, SA WG2, SA WG3, SA WG5, SA WG6","Cc":"","lsoriginalls":"S4-230431","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306281.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306282","title":"LS on management of AS by AF","source":"SA WG4","contact":"Richard Bradbury","contact-id":82569,"tdoctype":"LS in","for":"Action","abstract":"As part of its study on extensions to the 5G Media Streaming (5GMS) architecture, SA WG4 has identified a requirement for a 5GMS Application Function to manage a population of 5GMS Application Servers. During the course of the study, it has become apparent that the management relationship is also generally applicable to other classes of Application Function (AF) managing a population of Application Server (AS) instances. This relationship is particularly relevant in deployments where the AS and AF are supplied by different vendors and interoperability is therefore a relevant topic for standardisation. At SA WG4#122, it was agreed to add a Key Issue on this topic to TR 26.804 in Rel 18 and the relevant Change Request is attached for you reference. {. . .} Action: SA WG4 kindly requests SA WG2 to comment on the above proposal to define a generic, reusable service-based architecture and API for AS instance management by an AF. Action: SA WG4 kindly requests SA WG2 to inform it of any existing or planned work in this area.","secretary_remarks":"Revision of Postponed S2-2303976 from S2#156E. Responses drafted in S2-2306684, S2-2306282. Final response in S2-2307789","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"replied to","reservation_date":"2023-04-25 07:34:54","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303976","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"SA WG6","lsoriginalls":"S4-230436","lsreply":"S2-2307789","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306282.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306283","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-2303979 from S2#156E. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"postponed","reservation_date":"2023-04-25 07:34:54","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303979","revisedto":"S2-2308276","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"S5-232774","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306283.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306285","title":"LS from SA WG6: LS on SA WG6 V2X service support","source":"SA WG6","contact":"Emmanouil Pateromichelakis","contact-id":94983,"tdoctype":"LS in","for":"Information","abstract":"In SA WG6#52-bis-e, SA WG6 received (in cc) a Reply LS on QoS Sustainability analytics and V2X service adaptations (SP-221320) which provided a consolidated answers from SA WG1 and SA WG2 on the 5GAA LS on QoS Sustainability analytics and V2X service adaptations (S-220077). The 5GAA LS was pointing to a technical report (5GAA_T-220058_WI-PRESA-Technical-Report), which included some requirements and assumptions on the current 3GPP support to support these requirements. {. . .}","secretary_remarks":"Revision of Postponed S2-2303988 from S2#156E. 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-04-25 07:34:54","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303988","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG2","lsoriginalls":"S6-231091","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306285.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306286","title":"LS from GSMA TSGUEWIFI: LS to 3GPP SA WG2 on 3GPP and non-3GPP interworking information for VoWiFi","source":"GSMA TSGUEWIFI","contact":"Di Zhang","contact-id":96672,"tdoctype":"LS in","for":"Information","abstract":"GSMA TSG UEWiFi work item is currently working on GSMA PRD 'TS.63 UE Wi-Fi calling specification requirements'. This document defines the minimum mandatory set of features that a 5G device is required to implement in order to guarantee high quality Wi-Fi calling service. Specifically, during the work on GSMA PRD TS.63, it has been found that there is gap existing between 3GPP\/GSMA specification and UE VoWiFi implementation when considering different network deployment. Different operators may have different cellular and Wi-Fi interoperability policy and this interoperability policy may evolve as time goes on. Some typical network deployments are listed as below: {. . .} Action: GSMA TSG UEWIFI group kindly requests SA WG2 to take the information above into account and provide standardized solutions.","secretary_remarks":"Revision of Postponed S2-2303991 from S2#156E (uses revised input provided). Responses drafted in S2-2306809, S2-2307171, S2-2307422. Final response in S2-2307898","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"replied to","reservation_date":"2023-04-25 07:34:54","uploaded":"2023-04-25 07:35:59","revisionof":"S2-2303991","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"GSMA NG","lsoriginalls":"UEWIFI07_003_rev","lsreply":"S2-2307898","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306286.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306289","title":"LS from CT WG1: Reply LS on 3GPP work on Energy Efficiency","source":"CT WG1","contact":"Christian Herrero-Veron","contact-id":45210,"tdoctype":"LS in","for":"Information","abstract":"","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-04-25 07:34:54","uploaded":"2023-04-25 07:39:21","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"TSG SA, TSG RAN, TSG CT, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, CT WG3","lsoriginalls":"C1-232650","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306289.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306290","title":"LS from CT WG1: LS on applicability of IWK to mixture of control plane only PDU session and non-control plane only PDU session","source":"CT WG1","contact":"Mahmoud Watfa","contact-id":85785,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"Responses drafted in S2-2306756, S2-2307250, S2-2307365. Final response in S2-2307792","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10530,"status":"replied to","reservation_date":"2023-04-25 07:34:54","uploaded":"2023-04-25 07:39:21","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"C1-232702","lsreply":"S2-2307792","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306290.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306292","title":"LS from CT WG1: LS on periodic attempts for re-selection to a higher priority SNPN when access for localized services in SNPN is enabled","source":"CT WG1","contact":"Ivo Sedlacek","contact-id":41880,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"postponed","reservation_date":"2023-04-25 07:34:54","uploaded":"2023-04-25 07:39:21","revisionof":"","revisedto":"S2-2308277","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2","lsoriginalls":"C1-232888","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306292.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306296","title":"LS from CT WG1: LS on access to stand-alone non-public network services via PLMN and vice versa","source":"CT WG1","contact":"Xu Chen","contact-id":87045,"tdoctype":"LS in","for":"Information","abstract":"","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-04-25 07:34:54","uploaded":"2023-04-25 07:39:21","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1","Cc":"SA WG2","lsoriginalls":"C1-232971","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306296.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306297","title":"LS from CT WG3: Reply LS on 3GPP work on Energy Efficiency","source":"CT WG3","contact":"Abdessamad EL MOATAMID","contact-id":89270,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"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-04-25 07:34:54","uploaded":"2023-04-25 07:39:21","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG5","Cc":"CT WG1, CT WG3, CT WG4, TSG CT, TSG SA, TSG RAN, SA WG1, SA WG2, SA WG3, SA WG4, SA WG6, RAN WG1, RAN WG2, RAN WG3","lsoriginalls":"C3-231470","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306297.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306301","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":"","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"postponed","reservation_date":"2023-04-25 07:34:54","uploaded":"2023-04-25 07:39:21","revisionof":"","revisedto":"S2-2308280","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":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306301.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306304","title":"LS from SA WG3: LS on Roaming architecture updates","source":"SA WG3","contact":"Alf Zugenmaier","contact-id":52494,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 is discussing the following LSs from GSMA 5GMRR on requirements in 5GS roaming. S3-231717 \/ 5GMRR Doc 41_37r2: LS to 3GPP on GSMA requirements regarding intermediaries in the roaming ecosystem (Roaming Hub, IPX and RVAS Providers); S3-231718 \/ 5GMRR Doc 41_38r2 LS response to 3GPP on IPX Requirements for 5GS Roaming; S3-231719 \/ 5GMRR Doc 41_39r2 LS Roaming Value Added Service Requirements; S3-231720 \/ 5GMRR Doc 41_40r4 LS with Roaming Hubbing requirements and LS response to SA WG3 LS(S3-214456) on 5GS Roaming Hubbing; S3-231721 \/ 5GMRR Doc 41_41r3 LS on GSMA 5GMRR Working Solution Assumption L-PRINS and Data Session Control). The following considerations are an initial view by SA WG3 to accommodate the SA plenary request, i.e. requesting the WGs addressed in the GSMA LSs to prepare input for a joint reply from TSG SA. {. . .} Action: SA WG3 kindly asks SA WG2 to provide a solution that supports GSMA requirements as communicated in the LSs above.","secretary_remarks":"Response drafted in S2-2307313. Response to be included in S2-2307899. Final response in S2-2307983.","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-04-25 10:01:18","uploaded":"2023-04-27 06:26:47","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG1","Cc":"TSG SA, CT WG4","lsoriginalls":"S3-232155","lsreply":"S2-2307983","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306304.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306308","title":"LS from SA WG4: Reply LS on the reuse of EVEX as specified in TS 26.531","source":"SA WG4","contact":"Richard Bradbury","contact-id":82569,"tdoctype":"LS in","for":"Action","abstract":"SA WG4 thanks SA WG6 for its LS on possible reuse of the SA WG4-defined EVEX framework in the context of the Application Data Analytics Enablement Services (ADAES) and application service management in eSEAL2 work items in order to avoid duplication of effort. {. . .} Action: In relation to requirement 1, SA WG4 asks SA WG2 to comment on the possibility of extending the Naf_EventExposure service to include a query operation in support of the stated SA WG6 requirement.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"postponed","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-04-27 06:26:47","revisionof":"","revisedto":"S2-2308282","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"SA WG2, CT WG3","lsoriginalls":"S4-230683","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306308.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306311","title":"LS from RAN WG3: LS on the enhancements to restricting paging in a limited area","source":"RAN WG3","contact":"Hakon Helmers","contact-id":69127,"tdoctype":"LS in","for":"Action","abstract":"RAN WG3 is currently working on enhancements to restrict paging in a limited area as described in TR 38.864 clause 6.5.4, and has made the following agreements for RAN-initiated paging: a) It is gNB s implementation to decide to which UEs the paging enhancement technique is applied. b) Introduce the recommended paging SSB list in the F1AP PAGING message sent from the gNB-CU to the gNB-DU. c) Introduce the recommended paging SSB list in the F1AP UE CONTEXT RELEASE COMPLETE message sent from the gNB-DU to the gNB-CU. According to above agreements, paging for UEs in RRC INACTIVE state may be restricted to a limited number of beams within a cell. RAN WG3 would respectfully like to ask RAN WG2 the following question: Q1: Whether RAN WG3 s agreements have any impact on, or could be impacted by, TS 38. 304 clause 7 Paging, e.g., related to the following paragraph. TS 38.304 clause 7.1: In multi-beam operations, the UE assumes that the same paging message and the same Short Message are repeated in all transmitted beams and thus the selection of the beam(s) for the reception of the paging message and Short Message is up to UE implementation. The paging message is same for both RAN initiated paging and CN initiated paging. RAN WG3 also discussed the enhancements to restrict paging in a limited area for UEs in RRC IDLE state based on the following mechanism: 1) The signalling procedure of the paging enhancement for UEs in RRC_IDLE state is given as follows: a) The last serving gNB reports a list of recommended beams (e.g., last few served SSBs) of the gNB to the AMF in UE CONTEXT RELEASE COMPLETE message over NGAP b) The AMF stores the list of recommended beams while UE is in RRC_IDLE state c) During idle mode paging, the AMF sends the stored recommended beams back to the last serving gNB in the NGAP Paging message. 2) To assist in NGAP Paging, it is expected that the gNB shall provide the list of recommended beams to the CN only for UEs that are known to be stationary, but it is up to gNB s implementation to decide to which UEs the paging enhancement technique is applied. 3) RAN WG3 assumes that the list of recommended beams will be transparent to AMF. Q2: RAN WG3 would respectfully like to ask SA WG2 if there are any issues from CN perspective with this mechanism. Action: RAN WG3 kindly asks SA WG2 to provide answer to Q2.","secretary_remarks":"Responses drafted in S2-2307061, S2-2307185, S2-2307233. Final response in S2-2307984","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10680,"status":"replied to","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-04-28 05:15:53","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG2","Cc":"","lsoriginalls":"R3-232084","lsreply":"S2-2307984","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306311.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306314","title":"LS from ITU-T SG13: LS on initiation of new work item ITU-T Y.REOUPF: 'Resource efficiency optimization for managing user plane function in IMT-2020 networks and beyond'","source":"ITU-T SG13","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Information","abstract":"This liaison statement informs about the initiation of new work item Resource efficiency optimization for managing user plane function in IMT-2020 networks and beyond in Q21\/13.","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-04-25 10:01:18","uploaded":"2023-04-28 05:43:30","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"ITU-T SG2, SG11, SA WG1, SA WG2, SA WG5, ETSI ISG MEC","Cc":"","lsoriginalls":"SG13-LS79","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306314.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306315","title":"LS from ITU-T SG13: LS on Y.3159 'Framework for classifying network slice level in future networks including IMT-2020'","source":"ITU-T SG13","contact":"Yushuang Hu","contact-id":96973,"tdoctype":"LS in","for":"Action","abstract":"This liaison statement informs about the consented Recommendation ITU-T Y.3159 'Framework for classifying network slice level in future networks including IMT-2020'.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"postponed","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-05-02 14:58:22","revisionof":"","revisedto":"S2-2308283","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5, GSMA","Cc":"","lsoriginalls":"SG13-LS80","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306315.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306317","title":"LS from RAN WG2: LS on carrier mapping for unicast SL CA","source":"RAN WG2","contact":"Peng Cheng","contact-id":96130,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 discussed NR SL CA in RAN WG2#121bis-e, and agreed that the carrier mapping configured by V2X layer can be used for NR broadcast\/groupcast SL CA, as in LTE SL CA. Agreement: Proposal 3: For groupcast\/broadcast, as in LTE SL CA, the carrier(s) that can be used for transmitting data are configured by V2X layer for the L2 destination. FFS on backwards compatibility issue. RAN WG2 also discussed NR unicast SL CA. Based on the observation, as section 6.1.2.12 of TS 24.587-v18.0.0 has captured, that V2X layer can be provisioned with service to frequency mapping for unicast, RAN WG2 assumes that it is applicable to PC5 unicast SL CA after the link has been established. However, RAN WG2 also identified below 2 questions to ask for SA WG2 s input: 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? Question 2: According to TS 24.587, PC5 unicast allows UEs to add\/modify\/remove V2X services\/PC5 QoS flows to the same L2 ID pair. Then, given service info is invisible to AS layer, how can the UE ensure the modified V2X services to be transmitted only on the corresponding frequencies mapped in the V2X layer?. Action: RAN WG2 respectfully asks SA WG2 to provide responses on the questions described above.","secretary_remarks":"Responses drafted in S2-2306356, S2-2306755, S2-2306885. Final response in S2-2307794","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10750,"status":"replied to","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-05-03 10:36:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG1","lsoriginalls":"R2-2304236","lsreply":"S2-2307794","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306317.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306324","title":"LS from SA WG5: LS on progress of 3GPP SA5 R18 work on intent driven management","source":"SA WG5","contact":"Ruiyue Xu","contact-id":61969,"tdoctype":"LS in","for":"Action","abstract":"SA WG5 is responsible for Management and Orchestration which covers aspects such as operation, assurance, fulfillment and automation, including management interaction with entities external to the network operator (e.g. service providers and verticals). Intent driven management for mobile networks is an important topic introduced in SA WG5 as friendly used API to allow a customer to provide intents as the desired state of the network or its services, without any detailed information of how to get to the desired state. SA WG5 started the work item intent driven management for mobile networks since 2018, and completed its Release 17 work on the intent driven management services for mobile networks in June 2022, corresponding published specification is TS 28.312 (Management and orchestration; Intent driven management services for mobile networks). TS 28.312 specifies the concept, use cases, requirements and solutions (including intent management operations and intent model) for the intent driven management for service or network management. TS 28.312 (Management and orchestration; Intent driven management services for mobile networks). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3554 SA WG5 would like to inform that it has completed its Release 18 study work on the enhanced intent driven management services for mobile networks. Main outcomes include (non-exhaustive list): New capabilities, including intent report, intent conflict, Intent handling capability obtaining, intent driven closed loop, etc. New scenarios, including intent driven approach for RAN energy saving, 5GC related intent expectation, etc. Solutions for the requirements documented in TS 28.312, including solution for radio service intent expectation. Solutions for collaboration\/alignment with other SDOs, including potential deployment scenarios for intent interface. Reference documents are: TR 28.912 (Study on enhanced intent driven management services for mobile networks). Available at: https:\/\/portal.3gpp.org\/desktopmodules\/Specifications\/SpecificationDetails.aspx?specificationId=3969 SA WG5 has now initiated its Release 18 worktem on Intent driven Management Service for mobile network phase 2 based on R17 intent work and outcome of R18 study work on the enhanced intent driven management services for mobile networks. Reference documents are: o SP-230180 (New WID on Intent driven Management Service for mobile network phase 2). Available at: https:\/\/portal.3gpp.org\/ngppapp\/CreateTdoc.aspx?mode=view&contributionUid=SP-230180. Action: Please take the above information into account.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"noted","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-05-03 10:36:36","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TM Forum, ETSI ZSM, ETSI NFV IFA, ITU-T SG2, ITU FG-AN, GSMA OPG, SA WG2","Cc":"TSG SA","lsoriginalls":"S5-233276","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306324.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306329","title":"LS from SA WG6: LS reply on management of AS by AF","source":"SA WG6","contact":"Emmanouil Pateromichelakis","contact-id":94983,"tdoctype":"LS in","for":"Information","abstract":"SA WG6 has provided the application layer architecture specifications for verticals, including architecture requirements and functional architecture for supporting the integration of verticals to 3GPP systems. As part of SA WG6 work, the application enablement layer includes vertical specific service enablers (e.g. V2XAPP, UASAPP, FFAPP) as well as common service platforms (CAPIF, SEAL) and edge enablement frameworks. Such enablement layer sits on top of the 3GPP network and aims to support the exposure of network services as well as to provide value-added capabilities related to discovery, service continuity, application portability, AS service API management etc. SA WG6 would like to provide feedback to this LS, since the direction of SA WG4 seems to be overlapping with SA WG6 coverage, since SA WG6 entities at the network side include AF functionality, and the AS-to-AF interface which is indicated in the LS is already specified in SA WG6. The following considerations are presented below: {. . .}","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2023-04-25 10:01:18","uploaded":"2023-05-03 14:35:19","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2","lsoriginalls":"S6-231605","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306329.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306350","title":"LS from ITU-T SG13: LS\/r on work items related to deterministic networking and deterministic communication service in ITU-T SG13","source":"ITU-T SG13","contact":"Taesang Choi","contact-id":34826,"tdoctype":"LS in","for":"Information","abstract":"This LS answers the liaison statements from IEEE 802.1 on deterministic networking and deterministic communication.","secretary_remarks":"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-08-05 12:29:25","uploaded":"2023-05-08 12:35:15","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"IEEE 802.1 TSN WG","Cc":"ITU-T Study Group 12, IETF DetNet WG, SA WG2","lsoriginalls":"SG13-LS86","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306350.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306356","title":"[DRAFT] Reply LS on carrier mapping for unicast SL CA","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on carrier mapping for unicast SL CA","secretary_remarks":"Response to S2-2306317. Revised to S2-2307897.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10770,"status":"revised","reservation_date":"2023-09-05 07:13:53","uploaded":"2023-05-12 13:58:19","revisionof":"","revisedto":"S2-2307897","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"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_157_Berlin_2023-05\/Docs\/S2-2306356.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306357","title":"Clarification on radio frequency information to AS layer","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: 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. 6.3.3.1 - Clarify that during the Layer-2 link establishment procedure, the V2X layer also provides the radio frequencies mapped to the V2X service type(s) for the Layer-2 link establishment when passing PC5-S message (e.g. Direct Communication Request, etc.) to the AS layer.","secretary_remarks":"Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10820,"status":"postponed","reservation_date":"2023-09-05 07:16:00","uploaded":"2023-05-12 13:58:19","revisionof":"","revisedto":"","release":"Rel-18","crspec":23.287,"crspecversion":"18.0.0","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":189.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306357.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.4.1.1.3, 6.3.3.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306495","title":"[DRAFT] LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"Deutsche Telekom AG","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: SA WG1, SA WG3, CT WG4","secretary_remarks":"Response to S2-2306270. Revised to S2-2307899.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"revised","reservation_date":"2023-11-05 10:40:28","uploaded":"2023-05-12 14:22:05","revisionof":"","revisedto":"S2-2307899","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306495.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306665","title":"Non-allowed area clarification","source":"Ericsson, Samsung, LG Electronics, Nokia, Nokia Shanghai Bell","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Clarify the 3GPP access UP resource handling in non-allowed area. PDU and IE encoding is to be specified in stage 3 TS but it is an architectural requirement that the UE in Non-allowed Area shall not request UP resources except for applicable regulatory prioritised services.","secretary_remarks":"Revision of S2-2304189. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"not treated","reservation_date":"2023-11-05 19:16:41","uploaded":"2023-05-12 19:27:51","revisionof":"S2-2304189","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"5GProtoc18"},{"winame":" TEI18"}],"crnumber":3846.0,"crrevision":4.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306665.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.3.4.1.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306670","title":"AF influence data key correction","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Removing 'or' in data key for DNN and S-NSSAI","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10830,"status":"not treated","reservation_date":"2023-11-05 19:21:31","uploaded":"2023-05-12 19:35:24","revisionof":"","revisedto":"","release":"Rel-15","crspec":23.502,"crspecversion":"15.16.0","workitem":[{"winame":"5GS_Ph1"}],"crnumber":4184.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306670.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"5.2.12.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306684","title":"[DRAFT] Reply LS on management of AS by AF","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4, SA WG6","secretary_remarks":"Response to S2-2306282, S2-2306329. Response to S2-2306282. Revised to S2-2307900.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2023-11-05 22:34:15","uploaded":"2023-05-12 20:03:34","revisionof":"","revisedto":"S2-2307900","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GMS_Ph2"},{"winame":" CAPIF"},{"winame":" SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306684.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306755","title":"[DRAFT] Reply LS on carrier mapping for unicast SL CA","source":"OPPO","contact":"Fei Lu","contact-id":108577,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2306317\/R2-2304236","secretary_remarks":"Response to S2-2306317. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10800,"status":"not treated","reservation_date":"2023-12-05 03:59:09","uploaded":"2023-05-12 08:39:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"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_157_Berlin_2023-05\/Docs\/S2-2306755.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306756","title":"[DRAFT] Reply LS on applicability of IWK to mixture of control plane only PDU session and non-control plane only PDU session","source":"OPPO","contact":"Fei Lu","contact-id":108577,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS of S2-2306290\/C1-232702","secretary_remarks":"Response to S2-2306290. Merged into S2-2307775","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10550,"status":"merged","reservation_date":"2023-12-05 03:59:09","uploaded":"2023-05-12 08:39:10","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306756.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306759","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"LG Electronics","contact":"Myungjune Youn","contact-id":60905,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-2306265. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"not treated","reservation_date":"2023-12-05 04:30:06","uploaded":"2023-05-12 13:41:32","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306759.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306809","title":"[DRAFT] LS reply on Voice over WiFi Handover","source":"Huawei, HiSilicon","contact":"Marco Spini","contact-id":8356,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA TSG UEWIFI","secretary_remarks":"Response to S2-2306286. Revised to S2-2307898.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"revised","reservation_date":"2023-12-05 05:46:35","uploaded":"2023-05-12 16:49:26","revisionof":"","revisedto":"S2-2307898","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSG UEWIFI","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2306809.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306844","title":"Discussion about LS from RAN WG2 on carrier mapping for unicast 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 carrier mapping for unicast SL CA (S2-2306317\/R2-2304236).","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10760,"status":"noted","reservation_date":"2023-12-05 06:51:05","uploaded":"2023-05-12 13:58: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_157_Berlin_2023-05\/Docs\/S2-2306844.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2306885","title":"[DRAFT] Reply LS on carrier mapping for unicast SL CA","source":"vivo","contact":"Wen Wang","contact-id":75748,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1. Attachments: xxxx","secretary_remarks":"Response to S2-2306317. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10810,"status":"not treated","reservation_date":"2023-12-05 07:44:06","uploaded":"2023-05-12 09:52:11","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"},{"winame":" eV2XARC"}],"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_157_Berlin_2023-05\/Docs\/S2-2306885.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307056","title":"SMS memory available","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the description of unsuccessful MT SMS delivery re-attempt when the delivery failure was due to UE memory capacity exceeded. SMSF indicates UE memory available for SMS to the UDM as part of Nudm_UECM_Registration message, which triggers the UDM to send the corresponding notification event. Clarify the SMSF and UDM requirements by reference to TS 23.040. Editorials in clause 4.13.3.9.","secretary_remarks":"Revision of S2-2304379. Revised to S2-2307777.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10640,"status":"revised","reservation_date":"2023-12-05 11:16:29","uploaded":"2023-05-12 12:04:28","revisionof":"S2-2304379","revisedto":"S2-2307777","release":"Rel-17","crspec":23.502,"crspecversion":"17.8.0","workitem":[{"winame":"SMS_SBI"}],"crnumber":3996.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307056.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.13.3.9, 4.15.3.1, 5.2.3.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307057","title":"SMS memory available","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: Update the description of unsuccessful MT SMS delivery re-attempt when the delivery failure was due to UE memory capacity exceeded. SMSF indicates UE memory available for SMS to the UDM as during registration procedure by using Nudm_UECM_Registration service operation or during update procedure using Nudm_UECM_Update service operation. Clarify the SMSF and UDM requirements by reference to TS 23.040. Editorials in clause 4.13.3.9.","secretary_remarks":"Revision of S2-2304380. Revised to S2-2307776.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10660,"status":"revised","reservation_date":"2023-12-05 11:16:30","uploaded":"2023-05-12 12:04:28","revisionof":"S2-2304380","revisedto":"S2-2307776","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"SMS_SBI"}],"crnumber":3997.0,"crrevision":1.0,"crcategory":"A","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307057.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307058","title":"[DRAFT] Reply LS on UE memory available for SMS","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Inform CT1 and CT4 on UE memory available for SMS CRs","secretary_remarks":"Response to S2-2306276. Revised to S2-2307778.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10610,"status":"revised","reservation_date":"2023-12-05 11:16:31","uploaded":"2023-05-12 12:04:28","revisionof":"","revisedto":"S2-2307778","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"SMS_SBI"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307058.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307061","title":"[DRAFT] Reply LS on the enhancements to restricting paging in limited area","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Reply to RAN3 proposal with open questions arising","secretary_remarks":"Response to S2-2306311. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10690,"status":"not treated","reservation_date":"2023-12-05 11:16:32","uploaded":"2023-05-12 12:04:28","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"Netw_Energy_NR-Core"}],"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_157_Berlin_2023-05\/Docs\/S2-2307061.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307151","title":"Transfer of emergency PDU session from non-3GPP to 3GPP access","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - clarifies that the procedure also applies to when the UE is normally registered - clarifies that the procedure is mandatory","secretary_remarks":"Revised to S2-2307774.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"revised","reservation_date":"2023-12-05 13:27:05","uploaded":"2023-05-12 18:19:58","revisionof":"","revisedto":"S2-2307774","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":4659.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307151.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.16.4.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307153","title":"Non-Allowed areas clarifications related to MPS","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - Clarify the 3GPP access UP resource handling in non-allowed area - Clarify the exceptions for MPS","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10510,"status":"not treated","reservation_date":"2023-12-05 13:31:02","uploaded":"2023-05-12 18:19:58","revisionof":"","revisedto":"S2-2311002","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"},{"winame":" MPS_WLAN"}],"crnumber":4660.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307153.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":false,"cn_affected":false,"clauses_affected":"5.3.4.1.1, 5.16.5","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307171","title":"[DRAFT] Reply LS to SA WG2 on 3GPP and non-3GPP interworking information in VoWiFi","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"Response to S2-2306286. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"not treated","reservation_date":"2023-12-05 13:36:58","uploaded":"2023-05-12 18:19:58","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSGUEWIFI","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307171.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307181","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Replies to LS C1-227197","secretary_remarks":"Response to S2-2306265. Revised to S2-2307759.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"revised","reservation_date":"2023-12-05 13:40:11","uploaded":"2023-05-12 18:19:58","revisionof":"","revisedto":"S2-2307759","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307181.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307185","title":"[DRAFT] Reply LS on the enhancements to restricting paging in a limited area","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on the enhancements to restricting paging in a limited area","secretary_remarks":"Response to S2-2306311. Revised to S2-2307779.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10700,"status":"revised","reservation_date":"2023-12-05 13:43:48","uploaded":"2023-05-12 18:19:58","revisionof":"","revisedto":"S2-2307779","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"Netw_Energy_NR-Core"}],"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_157_Berlin_2023-05\/Docs\/S2-2307185.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307188","title":"Indication to the UE whether MPS is supported","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Proposes that N3IWF and TNGF provide to the UE indication that 'MPS is supported' in the IKE_AUTH response if the UE indicated its MPS subscription and N3IWF or TNGF support MPS","secretary_remarks":"Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10520,"status":"not treated","reservation_date":"2023-12-05 13:48:41","uploaded":"2023-05-12 18:19:58","revisionof":"","revisedto":"S2-2311013","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"MPS_WLAN"}],"crnumber":4226.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307188.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":false,"me_affected":true,"ran_affected":true,"cn_affected":true,"clauses_affected":"4.12.2.2.1, 4.12a.2.2.1","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307221","title":"Handling of the Allowed PDU session status IE in Non-allowed service area","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"discussion","for":"Information","abstract":"","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"noted","reservation_date":"2023-12-05 14:43:34","uploaded":"2023-05-12 18:19:58","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GS_Ph1"},{"winame":" MPS_WLAN"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307221.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307233","title":"[DRAFT] Reply LS on the enhancements to restricting paging in a limited area","source":"Vodafone","contact":"Chris Pudney","contact-id":1122,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"Response to S2-2306311. Corrupt file replaced on FTP server. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10740,"status":"not treated","reservation_date":"2023-12-05 14:53:02","uploaded":"2023-05-12 15:00:09","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","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_157_Berlin_2023-05\/Docs\/S2-2307233.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307250","title":"Reply LS on applicability of IWK to mixture of control plane only PDU session and non-control plane only PDU session","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":94901,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"Response to S2-2306756. Revised to S2-2307775, merging S2-2307365","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10560,"status":"revised","reservation_date":"2023-12-05 15:29:09","uploaded":"2023-05-12 16:23:14","revisionof":"","revisedto":"S2-2307775","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307250.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307303","title":"Further discussion on 3GPP and non-3GPP interworking indication for VoWiFi.","source":"China Telecom","contact":"Ting Zhang","contact-id":81763,"tdoctype":"discussion","for":"Decision","abstract":"","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10110,"status":"noted","reservation_date":"2023-12-05 17:00:39","uploaded":"2023-05-12 17:03:05","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_157_Berlin_2023-05\/Docs\/S2-2307303.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307313","title":"[DRAFT] Reply LS on Roaming architecture updates","source":"VODAFONE","contact":"Susana Sabater","contact-id":31269,"tdoctype":"LS out","for":"Approval","abstract":"","secretary_remarks":"Response to S2-2306304. Merged into S2-2307899.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"merged","reservation_date":"2023-12-05 17:08:42","uploaded":"2023-05-12 17:10:47","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG3","Cc":"SA WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307313.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307363","title":"Discussion on applicability of IWK to mixture of CP only and non-CP only PDU session.","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"discussion","for":"Discussion","abstract":"CT WG1 sent an LS to SA WG2 in S2-2306290\/C1-232702 and requested SA WG2 to answer the questions on the scenario described by CT WG1 LS. This paper discusses the scenario w.r.t SA WG2 specs and proposes the way forward.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10540,"status":"noted","reservation_date":"2023-12-05 19:25:29","uploaded":"2023-05-12 19:33:44","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_157_Berlin_2023-05\/Docs\/S2-2307363.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307365","title":"[DRAFT] Reply LS on applicability of IWK to mixture of control plane only PDU session and non-control plane only PDU session","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-2306290. Merged into S2-2307775","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10590,"status":"merged","reservation_date":"2023-12-05 19:28:40","uploaded":"2023-05-12 19:33:44","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5G_CIoT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307365.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307367","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"Samsung","contact":"Lalith Kumar","contact-id":80547,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Response to S2-2306265. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"not treated","reservation_date":"2023-12-05 19:41:02","uploaded":"2023-05-12 19:44:27","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307367.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307422","title":"[DRAFT] Reply LS on 3GPP and non-3GPP interworking information in VoWiFi","source":"Apple","contact":"Krisztian Kiss","contact-id":102932,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA TSG UEWIFI Group. CC: GSMA Network Group (NG)","secretary_remarks":"Response to S2-2306286. Not Handled","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"not treated","reservation_date":"2023-12-05 23:45:59","uploaded":"2023-05-12 23:57:14","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSG UEWIFI Group","Cc":"GSMA Network Group (NG)","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307422.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307759","title":"[DRAFT] Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Replies to LS C1-227197","secretary_remarks":"Revision of S2-2307181. Revised to S2-2307790.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"revised","reservation_date":"2023-05-30 10:07:22","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307181","revisedto":"S2-2307790","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307759.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307774","title":"Transfer of emergency PDU session from non-3GPP to 3GPP access","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - clarifies that the procedure also applies to when the UE is normally registered - clarifies that the conditions upon which the procedure is triggered","secretary_remarks":"Revision of S2-2307151. Revised to S2-2307791.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10490,"status":"revised","reservation_date":"2023-05-30 10:07:32","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307151","revisedto":"S2-2307791","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":4659.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307774.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307775","title":"Reply LS on applicability of IWK to mixture of control plane only PDU session and non-control plane only PDU session","source":"Qualcomm","contact":"Sebastian Speicher","contact-id":94901,"tdoctype":"LS out","for":"Approval","abstract":"-","secretary_remarks":"Revision of S2-2307250, merging S2-2307365 and S2-2306756. Revised to S2-2307792.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10570,"status":"revised","reservation_date":"2023-05-30 10:07:33","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307250","revisedto":"S2-2307792","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307775.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307776","title":"SMS memory available","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Rel-18 mirror CR: Summary of change: Update the description of unsuccessful MT SMS delivery re-attempt when the delivery failure was due to UE memory capacity exceeded. SMSF indicates UE memory available for SMS to the UDM as part of the TS 23.540 Alert procedure. Clarify the SMSF and UDM requirements by reference to TS 23.040.","secretary_remarks":"Revision of S2-2307057. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10670,"status":"agreed","reservation_date":"2023-05-30 10:07:33","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307057","revisedto":"","release":"Rel-18","crspec":23.502,"crspecversion":"18.1.1","workitem":[{"winame":"SMS_SBI"}],"crnumber":3997.0,"crrevision":2.0,"crcategory":"A","tsg_crp":"SP-230487","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307776.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307777","title":"SMS memory available","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Update the description of unsuccessful MT SMS delivery re-attempt when the delivery failure was due to UE memory capacity exceeded. SMSF indicates UE memory available for SMS to the UDM as part of the TS 23.540 Alert procedure. Clarify the SMSF and UDM requirements by reference to TS 23.040.","secretary_remarks":"Revision of S2-2307056. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10650,"status":"agreed","reservation_date":"2023-05-30 10:07:34","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307056","revisedto":"","release":"Rel-17","crspec":23.502,"crspecversion":"17.8.0","workitem":[{"winame":"SMS_SBI"}],"crnumber":3996.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-230487","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307777.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307778","title":"[DRAFT] Reply LS on UE memory available for SMS","source":"Nokia, Nokia Shanghai Bell","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"Inform CT1 and CT4 on UE memory available for SMS CRs","secretary_remarks":"Revision of S2-2307058. Revised to S2-2307793.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10620,"status":"revised","reservation_date":"2023-05-30 10:07:36","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307058","revisedto":"S2-2307793","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"SMS_SBI"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307778.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307779","title":"[DRAFT] Reply LS on the enhancements to restricting paging in a limited area","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on the enhancements to restricting paging in a limited area","secretary_remarks":"Revision of S2-2307185. Revised to S2-2307795.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10710,"status":"revised","reservation_date":"2023-05-30 10:07:36","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307185","revisedto":"S2-2307795","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"Netw_Energy_NR-Core"}],"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_157_Berlin_2023-05\/Docs\/S2-2307779.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307780","title":"[DRAFT] LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"Deutsche Telekom AG","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: SA WG1, SA WG3, CT WG4","secretary_remarks":"Revision of S2-2307899. Revised to S2-2307983.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"revised","reservation_date":"2023-05-30 10:07:36","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307899","revisedto":"S2-2307983","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307780.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307789","title":"Reply LS on management of AS by AF","source":"SA WG2","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4, SA WG6","secretary_remarks":"Revision of S2-2307900. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"approved","reservation_date":"2023-05-30 10:07:40","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307900","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GMS_Ph2"},{"winame":" CAPIF"},{"winame":" SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306282","lsto":"SA WG4, SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307789.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307790","title":"Reply LS on Handling of the Allowed PDU session status IE in Non-allowed service area","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-2307759. 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-05-30 10:07:40","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307759","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306265","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307790.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307791","title":"Transfer of emergency PDU session from non-3GPP to 3GPP access","source":"Qualcomm Incorporated","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: - clarifies that the procedure also applies to when the UE is normally registered - clarifies that the conditions upon which the procedure is triggered","secretary_remarks":"Revision of S2-2307774. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10500,"status":"agreed","reservation_date":"2023-05-30 10:07:41","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307774","revisedto":"","release":"Rel-18","crspec":23.501,"crspecversion":"18.1.0","workitem":[{"winame":"5GS_Ph1"},{"winame":" TEI18"}],"crnumber":4659.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-230490","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307791.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307792","title":"Reply LS on applicability of IWK to mixture of control plane only PDU session and non-control plane only PDU session","source":"SA WG2","contact":"Sebastian Speicher","contact-id":94901,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1","secretary_remarks":"Revision of S2-2307775. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10580,"status":"approved","reservation_date":"2023-05-30 10:07:41","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307775","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GProtoc18"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306290","lsto":"CT WG1","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307792.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307793","title":"LS on UE memory available for SMS","source":"SA WG2","contact":"Hannu Hietalahti","contact-id":69922,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG1, CT WG4. Attachments: TS 23.502 CR 3996 (Rel-17) (S2-2307777), CR 3997 (Rel-18) (S2-2307776)","secretary_remarks":"Revision of S2-2307778. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10630,"status":"approved","reservation_date":"2023-05-30 10:07:41","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307778","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"SMS_SBI"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306276","lsto":"CT WG1, CT WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307793.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307794","title":"Reply LS on carrier mapping for unicast SL CA","source":"SA WG2","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG2. CC: CT WG1","secretary_remarks":"Revision of S2-2307897. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10790,"status":"approved","reservation_date":"2023-05-30 10:07:42","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307897","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306317","lsto":"RAN WG2","Cc":"CT WG1","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307794.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307795","title":"[DRAFT] Reply LS on the enhancements to restricting paging in a limited area","source":"Qualcomm","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on the enhancements to restricting paging in a limited area","secretary_remarks":"Revision of S2-2307779. Revised to S2-2307984.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10720,"status":"revised","reservation_date":"2023-05-30 10:07:42","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2307779","revisedto":"S2-2307984","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"Netw_Energy_NR-Core"}],"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_157_Berlin_2023-05\/Docs\/S2-2307795.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307897","title":"[DRAFT] Reply LS on carrier mapping for unicast SL CA","source":"LG Electronics","contact":"Laeyoung Kim","contact-id":40613,"tdoctype":"LS out","for":"Approval","abstract":"[DRAFT] Reply LS on carrier mapping for unicast SL CA","secretary_remarks":"Revision of S2-2306356. Revised to S2-2307794.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10780,"status":"revised","reservation_date":"2023-05-30 10:09:10","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306356","revisedto":"S2-2307794","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"NR_SL_enh2"}],"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_157_Berlin_2023-05\/Docs\/S2-2307897.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307898","title":"LS reply on Voice over WiFi Handover","source":"SA WG2","contact":"Michele Zarri","contact-id":96831,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA TSG UEWIFI","secretary_remarks":"Revision of S2-2306809. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"approved","reservation_date":"2023-05-30 10:09:10","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306809","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306286","lsto":"GSMA TSG UEWIFI","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307898.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307899","title":"[DRAFT] LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"Deutsche Telekom AG","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: SA WG1, SA WG3, CT WG4","secretary_remarks":"Revision of S2-2306495. Revised to S2-2307780.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"revised","reservation_date":"2023-05-30 10:09:10","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306495","revisedto":"S2-2307780","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG1, SA WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307899.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307900","title":"[DRAFT] Reply LS on management of AS by AF","source":"Qualcomm Incorporated","contact":"Dario Serafino Tonesi","contact-id":88932,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4, SA WG6","secretary_remarks":"Revision of S2-2306684. Revised to S2-2307789.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"revised","reservation_date":"2023-05-30 10:09:10","uploaded":"2023-05-30 16:41:15","revisionof":"S2-2306684","revisedto":"S2-2307789","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"5GMS_Ph2"},{"winame":" CAPIF"},{"winame":" SEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307900.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307983","title":"LS on GSMA requirements regarding intermediaries in the roaming ecosystem and related LSs","source":"SA WG2","contact":"Dieter Gludovacz","contact-id":38203,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA, SA WG3. CC: SA WG1, CT WG4","secretary_remarks":"Revision of S2-2307780. Response to S2-2306270 and S2-2306304. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"approved","reservation_date":"2023-05-30 10:10:09","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2307780","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306270","lsto":"TSG SA, SA WG3","Cc":"SA WG1, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307983.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2307984","title":"Reply LS on the enhancements to restricting paging in a limited area","source":"SA WG2","contact":"Haris Zisimopoulos","contact-id":84603,"tdoctype":"LS out","for":"Approval","abstract":"To: RAN WG3. CC: RAN WG2","secretary_remarks":"Revision of S2-2307795. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10730,"status":"approved","reservation_date":"2023-05-30 10:10:10","uploaded":"2023-05-30 16:41:16","revisionof":"S2-2307795","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"Netw_Energy_NR-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2306311","lsto":"RAN WG3","Cc":"RAN WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_157_Berlin_2023-05\/Docs\/S2-2307984.zip","group":"S2","meeting":"S2-157","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]