[{"name":"S2-2502797","title":"LS from GSMA TSGNS: OSAppID usage by AppToken use case","source":"GSMA TSGNS","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS in","for":"Information","abstract":"GSMA TSGNS is a working group of GSMA in charge of maintaining PRD TS.62 'UE requirements related to Network Slicing using URSP'. PRD TS.62 provides requirements to the mobile industry on the design, development, and implementation of network slicing using URSP in 5G UEs. In the context of the wider activity on network slicing, GSMA recently approved the specification of the App Token. App Token was introduced in PRD TS.43 'Service Entitlement' which defines the MNOs Entitlement Server procedures. An Entitlement Server builds the interface between an MNO and a devices OS, and is used globally for e.g., eSIM activation, VoLTE\/VoWiFi configuration, DataPlan Info, and more configuration data. A device is expected to interact with its home MNO's Entitlement Server, also when roaming or in wifi, using HTTP REST. The App Token is a piece of information that the UE OS can obtain from specific applications and allows to uniquely identify an application across the complete ecosystem (application developer, MNO, subscriber UE) whilst protecting the end user privacy. This means that the UE OS does not need to use the information it has about the identity of an application when comparing against the OSAppID field from the URSP rules received from the MNO, but to use an anonymous identifier received from the MNO through TS.43 interface for that comparison. GSMA TSGNS is currently working to define in TS.62 how UE OS should behave when managing App Tokens with applications. The proposed end-to-end flow is as follows (boxes in green reflects standard procedures already defined by 3GPP or by GSMA in TS.43, red box is the CR to TS.62 being discussed in GSMA TSGNS): {. . .}","secretary_remarks":"Revision of S2-2501377. Responses drafted in S2-2502926, S2-2503081, S2-2503424, S2-2503617, S2-2503747, S2-2503855. An LS to TSG SA for a consolidated response to GSMA was agreed in S2-2504468. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10130,"status":"noted","reservation_date":"2025-03-22 07:08:23","uploaded":"2025-03-22 07:54:36","revisionof":"S2-2501377","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG3","Cc":"","lsoriginalls":"TSGNS44_003v6","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502797.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502798","title":"LS from CEN TC 278 WG 15: LS on Next Generation eCall","source":"CEN TC 278 WG 15","contact":"Matthias Moerbe","contact-id":80942,"tdoctype":"LS in","for":"Action","abstract":"CEN\/TC 278\/WG 15 would like to thank SA WG1, SA WG2, CT WG1, TSG SA, TSG CT and ETSI TC MSG for the received replies to the CEN LS on Next Generation eCall. We noticed the rapid progress of the work by SA WG1, SA WG2, CT WG1, TSG SA and TSG CT in relation to the LS from CEN on Next Generation eCall. The CEN LS on Next Generation eCall contained in total 9 cases. It seems as if currently only the cases 1 to 5 have been considered by 3GPP for the alignment of affected 3GPP specifications. Is the alignment of the cases 6 to 9 also foreseen in 3GPP Release 19? CEN considers these cases as a worthwhile improvement and would appreciate if 3GPP would check feasibility of implementing them. Action: SA WG1, SA WG2, CT WG1 , TSG SA and TSG CT are kindly asked to also take into consideration the cases 6 to 9 from the initial CEN LS on Next Generation eCall in 3GPP Release 19.","secretary_remarks":"Revision of S2-2501381. Postponed","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10120,"status":"postponed","reservation_date":"2025-03-22 07:08:23","uploaded":"2025-03-22 07:54:36","revisionof":"S2-2501381","revisedto":"S2-2504571","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG1, SA WG2, CT WG1, TSG SA, TSG CT, ETSI TC MSG","Cc":"","lsoriginalls":"3GPP_LS_reply_2025-02-05","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502798.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502801","title":"LS from RAN WG2: Reply LS on Time Synchronization for MBS","source":"RAN WG2","contact":"Martin Van Der Zee","contact-id":58600,"tdoctype":"LS in","for":"Action","abstract":"RAN WG2 thanks SA WG4 for the LS and SA WG2 for their reply LS on Time Synchronization for MBS. RAN WG2 would like to provide the following feedback: The use of SNTP for time synchronization in MBS is outside RAN WG2 scope RAN WG2 confirms that the UTC time with 10 ms granularity in SIB9 (i.e. timeInfo IE including timeInfoUTC) can be used for time synchronization between gNB and UE. It is optional for the UE to support timeInfoUTC in SIB9 without UE capability signalling. It is up to SA WG4 to decide whether to use SIB9 for time synchronization for MBS. Action: RAN WG2 kindly asks SA WG4 and SA WG2 to take the information above into account.","secretary_remarks":"Revision of S2-2501386. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10470,"status":"noted","reservation_date":"2025-03-22 07:08:23","uploaded":"2025-03-22 07:54:36","revisionof":"S2-2501386","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4, SA WG2","Cc":"","lsoriginalls":"R2-2501509","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502801.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502809","title":"LS from CT WG3: LS reply on FS_IMS_RES outcome and future work plan","source":"CT WG3","contact":"Susana Fernandez","contact-id":42321,"tdoctype":"LS in","for":"Information","abstract":"CT WG3 thanks CT WG4 for the LS (C3-250018\/C4-244485) on FS_IMS_RES outcome and future work plan. CT WG3 has discussed solutions 6, 8 and 9 as the solutions with (potentially) impacts in CT WG3 WG and would like to provide the answer to the following question: {. .}","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":"2025-03-22 07:08:23","uploaded":"2025-03-22 13:14:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG1","lsoriginalls":"C3-250657","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502809.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502823","title":"LS from RAN WG2: Inclusion of NTN intended service area in the Service Announcement","source":"RAN WG2","contact":"Ignacio Pascual Pelayo","contact-id":97825,"tdoctype":"LS in","for":"Information","abstract":"RAN WG2 is working on a solution to provide UEs with geographical information of where within an NTN cell an MBS broadcast service is applicable. This area is called the 'intended service area' (ISA) whose geographical definition is provided to the UE via SIB and is associated with an identifier (ISA ID). The attached CR includes the changes introduced by SA WG2 to adopt the ISA for NTN access. RAN WG2 would like to ask whether including the ISA in the Service Announcement would impact in SA WG4 specifications and would kindly request SA WG4 to confirm this can be supported within the Rel-19 timeframe.","secretary_remarks":"Response drafted in S2-2502898. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10090,"status":"noted","reservation_date":"2025-03-22 07:08:23","uploaded":"2025-03-22 13:14:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG4","Cc":"SA WG2","lsoriginalls":"R2-2501583","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502823.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502838","title":"LS from SA WG4: LS on Advanced Media Delivery","source":"SA WG4","contact":"Thomas Stockhammer","contact-id":60397,"tdoctype":"LS in","for":"Information","abstract":"During SA WG4#131, SA WG4 completed the Work Item on 'Stage 2 for Advanced Media Delivery'. The work item is based on a feasibility study FS_AMD. Relevant CRs were agreed during the recent SA WG4 meeting and will be sent to SA#107 for approval. Impacted specifications are: - TS 26.501 for 5G Media Streaming - TS 26.502 for MBS User services SA WG4 also agreed a stage-3 work item 'AMD_PRO-MED' to address the relevant protocol and format extensions for Advanced Media Delivery. However, for a subset of the new features, impacts to stage-3 specifications under change control of CT WG3 and\/or CT WG4 are identified in the following tables. SA WG4 kindly asks CT WG3 and CT WG4 to take the following into account and update the respective stage-3 specifications.","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":"2025-03-22 07:08:23","uploaded":"2025-03-22 13:14:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG3","Cc":"SA WG2","lsoriginalls":"S4-250412","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502838.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502845","title":"LS from SA WG6: LS on Generation of AF specific UE ID","source":"SA WG6","contact":"Shahram Mohajeri","contact-id":62911,"tdoctype":"LS in","for":"Action","abstract":"As part of the EDGEAPP work item, SA WG6 in 23.558 clause 8.6.5 defined the 'UE Identifier API' which resulted in having SA WG2 specify NEF's 'AF specific UE ID retrieval' procedure in 23.502 clause 4.15.10 (and associated Nnef_UEId_Get operation). SA WG6 have noted that Step 10 of the 'AF specific UE ID retrieval' procedure doesn't specify the case where UDM may not be able to find the AF specific UE ID in the subscriber's record. '10. The UDM responds to the NEF with an AF specific UE Identifier represented as an External Identifier for the UE which is uniquely associated with the Application Port ID, MTC Provider Information or AF Identifier.' On the other hand, stage 3 in 29.522 clause 4.4.32.2 'Retrieve AF specific UE ID service operation' states that UDM would reply to NEF with a '404 Not Found' error status code if AF specific UE ID is not available (see related paragraph from clause 4.4.32.2 copy\/pasted below): 'If the UDM indicates that the requested UE Identifier is not available in the subscription data, the NEF shall respond to the AF with a '404 Not Found' error status code.' Based on this observation, SA WG6 asks SA WG2 to provide insight into the assignment of the AF specific UE ID, for instance whether support is provided for its dynamic generation in scenarios in which the UDM is unable to find it. Action: SA WG6 asks SA WG2 to kindly provide insight into the assignment of AF Specific UE IDs.","secretary_remarks":"Responses drafted in S2-2502871, S2-2502924, S2-2502951, S2-2503091, S2-2503620. Final response in S2-2504396.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10230,"status":"replied to","reservation_date":"2025-03-22 07:08:24","uploaded":"2025-03-22 13:14:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2","Cc":"CT WG3","lsoriginalls":"S6-250286","lsreply":"S2-2504396","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502845.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502846","title":"LS from TSG SA: Reply LS on support of multiple access technologies based on the IMS service type","source":"TSG SA","contact":"Jicheol Lee","contact-id":87580,"tdoctype":"LS in","for":"Information","abstract":"TSG SA would like to thank GSMA NG regarding the LS sent to SA WG1 on support of multiple access technologies based on the IMS service type. {. . .} Action: TSG SA kindly asks GSMA NG to take above information into consideration.","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":"2025-03-22 07:08:24","uploaded":"2025-03-22 13:14:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG","Cc":"SA WG1, SA WG2","lsoriginalls":"SP-250329","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502846.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502848","title":"LS from ETSI ISG NFV: Publication of ETSI NFV group report on architectural support for NFV evolution","source":"ETSI ISG NFV","contact":"Manchang Ju","contact-id":72810,"tdoctype":"LS in","for":"Action","abstract":"The ETSI ISG NFV would like to inform 3GPP that ETSI GR NFV-IFA 054 (Release 6 group report on architectural support for NFV evolution) has been published. The publication of ETSI GR NFV-IFA 054 (v6.1.1) is available at the following location: https:\/\/www.etsi.org\/deliver\/etsi_gr\/NFV-IFA\/001_099\/054\/06.01.01_60\/gr_nfv-ifa054v060101p.pdf {. . .} Actions: ETSI ISG NFV kindly requests your organization to - Take the above information into account when proceeding future architecture of mobile communication network in the timeline of 3GPP Release 20; - Provide feedback to the published ETSI GR NFV-IFA 054 document; - Furthermore, consider to arrange joint workshop during NFV#50 meeting for exchanging information and views on future mobile communication network and telco cloud.","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":"2025-03-22 07:08:24","uploaded":"2025-03-26 16:12:16","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, SA WG5","Cc":"TSG SA","lsoriginalls":"NFV(25)000019r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502848.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502849","title":"LS from CT WG4: LS on Optimizations to UPF event subscriptions and reporting","source":"CT WG4","contact":" Anonymous","contact-id":4132,"tdoctype":"LS in","for":"Action","abstract":"CT WG4 started a study on Protocol for AI Data Collection from UPF and one of the key issues is to address: {. . .} Action: CT WG4 kindly requests SA WG2 and CT WG3 to review solutions #2, #4 and #5 and provide their feedback.","secretary_remarks":"Responses drafted in S2-2503095, S2-2503739, S2-2503769. Final response in S2-2504469.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10400,"status":"replied to","reservation_date":"2025-03-22 07:08:24","uploaded":"2025-03-26 16:12:16","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG2, CT WG3","Cc":"","lsoriginalls":"C4-250455","lsreply":"S2-2504469","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502849.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502870","title":"Generation of AF specific UE Identifier .","source":"Apple","contact":"Sudeep M Vamanan","contact-id":103491,"tdoctype":"discussion","for":"Discussion","abstract":"This discussion paper analyzes the generation of AF Specific UE identifier in 5GC","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10240,"status":"noted","reservation_date":"2025-03-24 12:49:02","uploaded":"2025-03-28 18:01:32","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502870.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502871","title":"[DRAFT] Reply LS on generation of AF specific UE ID","source":"Apple","contact":"Sudeep M Vamanan","contact-id":103491,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: CT WG3","secretary_remarks":"Response to S2-2502845. Revised, merging S2-2502924, S2-2503091, S2-2503620 and S2-2502951, to S2-2504095.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10250,"status":"revised","reservation_date":"2025-03-24 12:50:20","uploaded":"2025-03-28 18:01:32","revisionof":"","revisedto":"S2-2504095","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502871.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502898","title":"[DRAFT] Reply LS on Inclusion of NTN intended service area in the Service Announcement","source":"Nokia","contact":"Thomas Belling","contact-id":68266,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG4. CC: SA WG2","secretary_remarks":"Response to S2-2502823. Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10100,"status":"noted","reservation_date":"2025-03-25 17:05:04","uploaded":"2025-03-28 23:39:45","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"NR_NTN_Ph3-Core"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"RAN WG2, SA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502898.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502924","title":"[DRAFT] Reply LS on generation of AF specific UE ID","source":"Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: CT WG3, CT WG4. Attachments: TBD (CR6174, CR5398)","secretary_remarks":"Response to S2-2502845. Merged into S2-2504095.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10280,"status":"merged","reservation_date":"2025-03-26 01:35:49","uploaded":"2025-03-28 11:17:06","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502924.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502926","title":"[DRAFT] Reply LS on OSAppID usage by AppToken use case","source":"Telefonica Germany GmbH","contact":"Jesus Martin","contact-id":48535,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on OSAppID usage by AppToken use case","secretary_remarks":"Response to S2-2502797. Revised, merging S2-2503424, S2-2503617, S2-2503747 and S2-2503855, to S2-2504094.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10150,"status":"revised","reservation_date":"2025-03-26 01:58:38","uploaded":"2025-03-28 22:06:02","revisionof":"","revisedto":"S2-2504094","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSGNS","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502926.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502927","title":"Discussion paper on GSMA TSGNS AppToken use case.","source":"Telefonica S.A., Verizon, Deutsche Telekom, KDDI, Ericsson, Nokia","contact":"Jesus Martin","contact-id":48535,"tdoctype":"discussion","for":"Discussion","abstract":"The paper provides clarifications about various questions raised related to the AppToken functionality of GSMA TSGNS group.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10140,"status":"noted","reservation_date":"2025-03-26 02:09:20","uploaded":"2025-03-28 22:06:52","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502927.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502951","title":"[DRAFT] LS Reply on Generation of AF specific UE ID","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"LS Reply on Generation of AF specific UE ID","secretary_remarks":"Response to S2-2502845. Merged into S2-2504095.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10310,"status":"merged","reservation_date":"2025-03-26 14:39:29","uploaded":"2025-03-28 18:31:33","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"CT WG3, CT WG4","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502951.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2502953","title":"Handling of AF Specific UE IDs","source":"Ericsson, AT&T, Nokia, Deutsche Telekom, KPN, NTT DOCOMO","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to include an alternative for UDM to generate, via implementation specific means, an AF specific UE ID when there is no AF specific UE ID defined in UDR for the SUPI and if the requesting AF is authorized. In this case, the UDM generates the AF specific UE ID via implementation specific means so that it is also possible for the UDM to also translate the generated AF specific UE ID to its corresponding SUPI. This way, only UDM business logic is impacted, and thus, the CR is proposed for the Rel-19 of the TS as no other NF or API is impacted.","secretary_remarks":"Revised, merging S2-2503024, to S2-2504096.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10320,"status":"revised","reservation_date":"2025-03-26 14:39:29","uploaded":"2025-03-28 18:31:33","revisionof":"","revisedto":"S2-2504096","release":"Rel-19","crspec":"23.501","crspecversion":"19.3.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":6168.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2502953.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503024","title":"AF specific UE ID generation","source":"Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Support generation of the AF specific UE ID","secretary_remarks":"Merged into S2-2504096.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10380,"status":"merged","reservation_date":"2025-03-27 06:14:29","uploaded":"2025-03-28 11:17:06","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.3.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":6174.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503024.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503025","title":"AF specific UE ID generation","source":"Samsung","contact":"Hyesung Kim","contact-id":83054,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: Support generation of the AF specific UE ID","secretary_remarks":"Merged into S2-2504097.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10390,"status":"merged","reservation_date":"2025-03-27 06:18:01","uploaded":"2025-03-28 11:17:06","revisionof":"","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.3.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":5398.0,"crrevision":"","crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503025.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":false,"me_affected":false,"ran_affected":false,"cn_affected":true,"clauses_affected":"4.15.10","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503091","title":"[DRAFT] LS on Generation of AF specific UE ID","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on Generation of AF specific UE ID","secretary_remarks":"Response to S2-2502845. Merged into S2-2504095.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10290,"status":"merged","reservation_date":"2025-03-27 12:12:51","uploaded":"2025-03-28 10:19:37","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503091.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503092","title":"Generation of AF specific UE ID","source":"Nokia, AT&T, KPN, NTT DOCOMO, Deutsche Telekom","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If there is no available AF specific UE Identifier matching the AF information provided by the NEF to the UDM in step 9 of clause 4.15.10, based on the operator's policy associated with the AF, the UDM can generate an AF specific UE Identifier, store it and provide it back to the AF.","secretary_remarks":"Revised, merging S2-2503025, to S2-2504097.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2025-03-27 12:12:51","uploaded":"2025-03-28 10:19:37","revisionof":"","revisedto":"S2-2504097","release":"Rel-19","crspec":"23.502","crspecversion":"19.3.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":5413.0,"crrevision":"","crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503092.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503095","title":"[DRAFT] LS on Optimizations to UPF event subscriptions and reporting","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on Optimizations to UPF event subscriptions and reporting","secretary_remarks":"Response to S2-2502849. Revised, merging S2-2503739 and S2-2503769 to S2-2504098.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10410,"status":"revised","reservation_date":"2025-03-27 12:12:53","uploaded":"2025-03-28 10:19:37","revisionof":"","revisedto":"S2-2504098","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503095.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503424","title":"[DRAFT] Reply LS to 'OSAppID usage by AppToken use case'","source":"Apple","contact":"Krisztian Kiss","contact-id":102932,"tdoctype":"LS out","for":"Approval","abstract":"To: GSMA TSGNS. CC: SA WG3. Attachments: None.","secretary_remarks":"Revision of (Unhandled) S2-2502143. Response to S2-2502797. Merged into S2-2504094","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10190,"status":"merged","reservation_date":"2025-03-28 07:08:49","uploaded":"2025-03-28 23:55:44","revisionof":"S2-2502143","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503424.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503617","title":"[DRAFT] Reply LS for OSAppID usage by AppToken use case","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: SA. CC: SA WG3","secretary_remarks":"Response to S2-2502797. Merged into S2-2504094","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10200,"status":"merged","reservation_date":"2025-03-28 10:33:00","uploaded":"2025-03-28 11:04:37","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503617.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503620","title":"[DRAFT] LS Response on Generation of AF specific UE ID","source":"ZTE","contact":"Jinguo Zhu","contact-id":32987,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: CT WG3","secretary_remarks":"Response to S2-2502845. Merged into S2-2504095.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10300,"status":"merged","reservation_date":"2025-03-28 10:33:01","uploaded":"2025-03-28 11:04:37","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503620.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503739","title":"[DRAFT] LS Reply on Optimizations to UPF event subscriptions and reporting","source":"Ericsson","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"LS out","for":"Approval","abstract":"Proposed response to CT4","secretary_remarks":"Response to S2-2502849. Merged into S2-2504098","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10450,"status":"merged","reservation_date":"2025-03-28 12:38:33","uploaded":"2025-03-28 18:24:44","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503739.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503747","title":"[DRAFT] Reply LS on OSAppID usage by AppToken use case","source":"Samsung","contact":"Dongeun Suh","contact-id":84836,"tdoctype":"LS out","for":"Approval","abstract":"To: SA. CC: SA WG3","secretary_remarks":"Response to S2-2502797. Merged into S2-2504094","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10210,"status":"merged","reservation_date":"2025-03-28 12:48:38","uploaded":"2025-03-28 12:50:15","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503747.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503769","title":"[DRAFT] Reply LS on Optimizations to UPF event subscriptions and reporting","source":"China Mobile","contact":"Yi Jiang","contact-id":40863,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS to CT4 LS on Optimizations to UPF event subscriptions and reporting","secretary_remarks":"Response to S2-2502849. Merged into S2-2504098","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10460,"status":"merged","reservation_date":"2025-03-28 13:01:31","uploaded":"2025-03-28 14:27:19","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503769.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503855","title":"[DRAFT] Reply LS on OSAppID usage by AppToken use case","source":"Google Korea LLC","contact":"Pavan Nuggehalli","contact-id":109471,"tdoctype":"LS out","for":"Approval","abstract":"To: SA. CC: SA WG3","secretary_remarks":"Response to S2-2502797. Merged into S2-2504094","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10220,"status":"merged","reservation_date":"2025-03-28 16:56:34","uploaded":"2025-03-28 20:38:35","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503855.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2503877","title":"6G specification format modernization: towards Automation-Native.","source":"Nokia","contact":"Yannick Lair","contact-id":76350,"tdoctype":"discussion","for":"Information","abstract":"For four generations, 3GPP specifications have been written using Microsoft Word. This contribution provides some information about consideration that is starting on the possibility of moving to an improved way of doing specifications for 6G from Rel-21.","secretary_remarks":"Noted","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10480,"status":"noted","reservation_date":"2025-03-28 20:07:05","uploaded":"2025-03-28 20:09:19","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2503877.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504094","title":"[DRAFT] Reply LS on OSAppID usage by AppToken use case","source":"Telefonica Germany GmbH","contact":"Jesus Martin","contact-id":48535,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on OSAppID usage by AppToken use case","secretary_remarks":"Revision of S2-2502926, merging S2-2503424, S2-2503617, S2-2503747 and S2-2503855. Revised in parallel session to S2-2504393.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10160,"status":"revised","reservation_date":"2025-08-04 15:43:04","uploaded":"2025-04-15 07:31:10","revisionof":"S2-2502926","revisedto":"S2-2504393","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA TSGNS","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504094.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504095","title":"[DRAFT] Reply LS on generation of AF specific UE ID","source":"Apple","contact":"Sudeep M Vamanan","contact-id":103491,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6. CC: CT WG3","secretary_remarks":"Revision of S2-2502871, merging S2-2502924, S2-2503091, S2-2503620 and S2-2502951. Revised in parallel session to S2-2504396.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10260,"status":"revised","reservation_date":"2025-08-04 15:43:04","uploaded":"2025-04-15 07:31:10","revisionof":"S2-2502871","revisedto":"S2-2504396","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA WG6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504095.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504096","title":"Handling of AF Specific UE IDs","source":"Ericsson, AT&T, Nokia, Deutsche Telekom, KPN, NTT DOCOMO, Apple, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to include an alternative for UDM to generate, via implementation specific means, an AF specific UE ID when there is no AF specific UE ID defined in UDR for the SUPI and if the requesting AF is authorized. In this case, the UDM generates the AF specific UE ID via implementation specific means so that it is also possible for the UDM to also translate the generated AF specific UE ID to its corresponding SUPI. This way, only UDM business logic is impacted, and thus, the CR is proposed for the Rel-19 of the TS as no other NF or API is impacted.","secretary_remarks":"Revision of S2-2502953, merging S2-2503024. Revised in parallel session to S2-2504394.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10330,"status":"revised","reservation_date":"2025-08-04 15:43:04","uploaded":"2025-04-15 07:31:10","revisionof":"S2-2502953","revisedto":"S2-2504394","release":"Rel-19","crspec":"23.501","crspecversion":"19.3.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":6168.0,"crrevision":1.0,"crcategory":"C","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504096.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504097","title":"Generation of AF specific UE ID","source":"Nokia, AT&T, KPN, NTT DOCOMO, Deutsche Telekom","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If there is no available AF specific UE Identifier matching the AF information provided by the NEF to the UDM in step 9 of clause 4.15.10, based on the operator's policy associated with the AF, the UDM can generate an AF specific UE Identifier, store it and provide it back to the AF.","secretary_remarks":"Revision of S2-2503092, merging S2-2503025. Revised in parallel session to S2-2504395.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10360,"status":"revised","reservation_date":"2025-08-04 15:43:06","uploaded":"2025-04-15 07:31:10","revisionof":"S2-2503092","revisedto":"S2-2504395","release":"Rel-19","crspec":"23.502","crspecversion":"19.3.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":5413.0,"crrevision":1.0,"crcategory":"F","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504097.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504098","title":"[DRAFT] LS on Optimizations to UPF event subscriptions and reporting","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on Optimizations to UPF event subscriptions and reporting","secretary_remarks":"Revision of S2-2503095, merging S2-2503739 and S2-2503769. Revised in parallel session to S2-2504397.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10420,"status":"revised","reservation_date":"2025-08-04 15:43:07","uploaded":"2025-04-15 07:31:10","revisionof":"S2-2503095","revisedto":"S2-2504397","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504098.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504393","title":"[DRAFT] Reply LS on OSAppID usage by AppToken use case","source":"Telefonica Germany GmbH","contact":"Jesus Martin","contact-id":48535,"tdoctype":"LS out","for":"Approval","abstract":"Reply LS on OSAppID usage by AppToken use case","secretary_remarks":"Revision of S2-2504094. Revised in parallel session to S2-2504468.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10170,"status":"revised","reservation_date":"2025-04-15 06:21:06","uploaded":"2025-04-15 07:41:17","revisionof":"S2-2504094","revisedto":"S2-2504468","release":"Rel-19","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504393.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504394","title":"Handling of AF Specific UE IDs","source":"Ericsson, AT&T, Nokia, Deutsche Telekom, KPN, NTT DOCOMO, Apple, Samsung","contact":"Shabnam Sultana","contact-id":21207,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: It is proposed to include an alternative for UDM to generate, via implementation specific means, an AF specific UE ID when there is no AF specific UE ID defined in UDR for the SUPI and if the requesting AF is authorized. In this case, the UDM generates the AF specific UE ID via implementation specific means so that it is also possible for the UDM to also translate the generated AF specific UE ID to its corresponding SUPI. This way, only UDM business logic is impacted, and thus, the CR is proposed for the Rel-19 of the TS as no other NF or API is impacted.","secretary_remarks":"Revision of S2-2504096. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10340,"status":"agreed","reservation_date":"2025-04-15 06:21:07","uploaded":"2025-04-15 07:41:17","revisionof":"S2-2504096","revisedto":"","release":"Rel-19","crspec":"23.501","crspecversion":"19.3.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":6168.0,"crrevision":2.0,"crcategory":"C","tsg_crp":"SP-250466","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504394.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504395","title":"Generation of AF specific UE ID","source":"Nokia, AT&T, KPN, NTT DOCOMO, Deutsche Telekom, Ericsson, Samsung","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"CR","for":"Approval","abstract":"Summary of change: If there is no available AF specific UE Identifier matching the AF information provided by the NEF to the UDM in step 9 of clause 4.15.10, based on the operator's policy associated with the AF, the UDM can generate an AF specific UE Identifier, store it and provide it back to the AF.","secretary_remarks":"Revision of S2-2504097. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10370,"status":"agreed","reservation_date":"2025-04-15 06:21:07","uploaded":"2025-04-15 07:41:17","revisionof":"S2-2504097","revisedto":"","release":"Rel-19","crspec":"23.502","crspecversion":"19.3.0","workitem":[{"winame":"EDGEAPP"}],"crnumber":5413.0,"crrevision":2.0,"crcategory":"F","tsg_crp":"SP-250466","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504395.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504396","title":"Reply LS on generation of AF specific UE ID","source":"SA WG2","contact":"Sudeep M Vamanan","contact-id":103491,"tdoctype":"LS out","for":"Approval","abstract":"To: SA WG6 CC: CT WG3 Attachments: 23.501 CR 6168, 23.502 CR 5413","secretary_remarks":"Revision of S2-2504095. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10270,"status":"approved","reservation_date":"2025-04-15 06:21:08","uploaded":"2025-04-15 07:41:17","revisionof":"S2-2504095","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2502845","lsto":"SA WG6","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504396.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504397","title":"[DRAFT] LS on Optimizations to UPF event subscriptions and reporting","source":"Nokia","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"[draft] LS on Optimizations to UPF event subscriptions and reporting","secretary_remarks":"Revision of S2-2504098. Revised in parallel session to S2-2504469.","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10430,"status":"revised","reservation_date":"2025-04-15 06:21:08","uploaded":"2025-04-15 07:41:17","revisionof":"S2-2504098","revisedto":"S2-2504469","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504397.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504468","title":"Reply LS on OSAppID usage by AppToken use case","source":"SA WG2","contact":"Maurice Pope","contact-id":648,"tdoctype":"LS out","for":"Approval","abstract":"To: TSG SA. CC: SA WG3","secretary_remarks":"Revision of S2-2504393. Agreed in parallel session. Block approved","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"Common issues and Incoming LSs","tdoc_agenda_sort_order":10180,"status":"approved","reservation_date":"2025-04-15 06:21:31","uploaded":"2025-04-15 07:41:18","revisionof":"S2-2504393","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"TEI19"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2502797","lsto":"TSG SA","Cc":"SA WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504468.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S2-2504469","title":"LS on Optimizations to UPF event subscriptions and reporting","source":"SA WG2","contact":"Laurent Thiebaut","contact-id":68713,"tdoctype":"LS out","for":"Approval","abstract":"To: CT WG4 CC: CT WG3","secretary_remarks":"Revision of S2-2504397. 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":"2025-04-15 06:21:31","uploaded":"2025-04-15 07:41:18","revisionof":"S2-2504397","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PAIDC_UPF"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"S2-2502849","lsto":"CT WG4","Cc":"CT WG3","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG2_Arch\/TSGS2_168_Goteborg_2025-04\/Docs\/S2-2504469.zip","group":"S2","meeting":"S2-168","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]