[{"name":"S6-252007","title":"LS to 3GPP TSG SA About New Procedures and API Development","source":"GSMA TSG IMSDCAS [IMSDCAS22_011]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. \tBackground \nGSMA TSG IMSDCAS and GSMA NG UPG wishes to thank for SP-241404 provided clarifications and the confirmation that there is no relationship, conflict or overlaps between the Application Programming Interface (API) specified by GSMA TSG IMSDCAS and the APIs already existing or planned to be specified by 3GPP SA6. And for outlining the work that has been undertaken with 3GPP TR 23.700-92 and 3GPP TS 23.392. GSMA TSG IMSDCAS and GSMA NG UPG finds most interesting and relevant 3GPP SA6 work related to the UE profile definition and the use of such profile to control the data channel content download to DCMTSI client in terminal. Those aspects are directly related to the mobile device functionalities and the content delivery over User Network Interface which are the key interest of both groups.\nIn addressing 3GPP SA6 questions GSMA TSG IMSDCAS, jointly with GSMA NG UPG,  would like to provide the following clarifications: \n\n  1.\t GSMA invites collaboration with 3GPP SA6 on aspects related to downloading procedures of data channel applications referred in SP-241404. The Terminal Steering Group should be contacted on UE related aspects of the procedures in question, including the definition of specific UE profiles to control such download. Network Group and specifically GSMA NG UPG should be contacted when network UNI aspects of the download need to be defined and GSMA NG NRG should be contacted when cooperation is required on the roaming aspects. \n\n  2. \tGSMA NG has NO plans to develop any network side Application Programming Interfaces (API) including APIs used by External Server\/content or APIs used by other elements to interact or control the External server. And in general NG and its subgroups don\u2019t develop network side APIs.\n\n  3. \tGSMA NG and GSMA TSG are not able to provide the list of standardisation gaps in the APIs needed by the External Server. The process to establish the related requirements and use cases is still to be initiated.  UPG#13 decided that a separate LS will be prepared to 3GPP explaining some specific implementation aspects linked to the external content access. The external access use case, once described and agreed, will be captured in GSMA PRD NG.129.\n\n  4. During the technical analysis and development of Annex C and Annex D of GSMA PRD NG.134 the main and broad conclusion concerned the lack of standards allowing data channel content interworking between 3GPP TS 26.114 defined IMS Data Channel subsystem and non-3GPP systems that might host such content, e.g. HTTP Server, from  the public internet and\/or in any private network. \n2\tRequest to 3GPP TSG SA\nGSMA TSG IMSDCAS and GSMA NG UPG jointly request 3GPP TSG SA and 3GPP SA6 to note the above responses. Further information will be provided at a later time.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":20070,"status":"noted","reservation_date":"2025-02-05 10:58:26","uploaded":"2025-05-02 11:03:29","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA, SA6","Cc":"","lsoriginalls":"IMSDCAS22_011","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_067_Fukuoka\/docs\/S6-252007.zip","group":"S6","meeting":"S6-67","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-252008","title":"LS on withdrawal of Rel-17 version of TS 24.549","source":"CT [CP-250261]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nDuring CT1#153, CT1 had a discussion on TS 24.549 (Network slice capability enablement- Service Enabler Architecture Layer for Verticals (SEAL); Protocol specification; Stage 3) and concluded that the Rel-17 and the Rel-18 versions of that specification are incompatible, due to the following:\n-\tTS 24.549 was introduced in Rel-17 under the eSEAL Work Item and followed the same structure and design layout as any other SEAL-related specification, i.e., procedures based on HTTP and CoAP were described.\n\n-\tIn Rel-18, TS 24.549 was updated under the NSCALE Work item. As part of this update, the structure and layout of the specification were changed to be based on 3GPP northbound interfaces and application layer APIs (NBI) specification. This means that the Rel-18 version of TS 24.549 defines APIs based on the OpenAPI specification and provides corresponding representations of all APIs defined in YAML format. At the same time, the procedures based on HTTP and CoAP were removed.\nCT1 discussed how to address this and concluded that CT1\u2019s preference is to withdraw the Rel-17 version of TS 24.549.\n\nSince the stage 2 for the stage 3 in TS 24.549 comes from SA6, CT would like to get SA6\u2019s feedback before proceeding with the withdrawal of the Rel-17 version of TS 24.549.\n\n2. Actions:\nTo SA6 group.\nACTION: \tCT asks SA6 to provide feedback on CT1\u2019s preference to withdraw the Rel-17 version of TS 24.549, and, if this preference is acceptable to SA6, to consider aligning their Rel-17 stage 2 specification accordingly.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":20080,"status":"replied to","reservation_date":"2025-02-05 10:58:26","uploaded":"2025-05-02 11:03:29","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eSEAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"CT1, CT3, SA","lsoriginalls":"CP-250261","lsreply":"S6-252247","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_067_Fukuoka\/docs\/S6-252008.zip","group":"S6","meeting":"S6-67","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-252009","title":"LS for information about NTZ support configuration procedure being updated","source":"CT1 [C1-252549]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nCT1 agreed in C1-251072 (CR#0050) the procedure for UAE-S to configure the No-Transmit Zone (NTZ) information in the UAE-C. The CR aligns the format of the NTZ information provided to the UAE-C with the format specified for the AT command to provide NTZ assistance information to the lower layers, which consists of mandatory restricted frequency bands with geographical area, and optional time restrictions for each restricted frequency band.\n\nCT1 requests SA6 to take above information into consideration and to align their specifications as necessary.\n\n2. Actions:\nTo SA6\nACTION: CT1 kindly asks SA6 to take above information into consideration to update their specification based on the agreements for TS 24.257.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":20090,"status":"replied to","reservation_date":"2025-02-05 10:58:26","uploaded":"2025-05-02 11:03:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"UASAPP_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"CT3","lsoriginalls":"C1-252549","lsreply":"S6-252103","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_067_Fukuoka\/docs\/S6-252009.zip","group":"S6","meeting":"S6-67","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-252010","title":"LS on SL Ranging and Short-range based positioning management procedures","source":"CT3 [C3-251572]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nCT3 is working on the protocol design of \"Support for sidelink positioning \/ ranging management\" and \"Short-Range based positioning information\" procedures defined in clauses 9.3.24 and 9.3.25 respectively of TS 23.434. CT3 has the following questions.\n\n1. Questions on the Sidelink positioning \/ ranging management\n\nQuestion 1a: What is the purpose of \"SL positioning parameters\" IE defined in the Table 9.3.2.61-1? How does the LMS utilize them in the Procedure of SL positioning \/ranging management service? Should any of the parameters included in this attribute be reported in SL positioning management notification?\n\nQuestion 1b: What are the contents of the \"VAL UE selection criteria\" and \"Triggering criteria\" IEs defined in the Table 9.3.2.61-1 of TS 23.434? How they should be used?\n\nQuestion 1c: What are the contents of the \"Triggering event\" and \"Reason\" IEs defined in the Table 9.3.2.63-1 and the relationship between them? How they should be used?\n\n\n2. Questions on the Short-Range based positioning information\n\nQuestion 2a: What is the purpose of \"Reporting events\" IE defined in the Table 9.3.2.65-1? Since Short-Range based positioning information is request \/ response and not subscribe\/notify service.\n\nQuestion 2b: Can you please clarify the description of the \"UE list\" IE defined in the Table 9.3.2.65-1? What does \"a list of reference UE including client, target and reference UEs\" actually imply? \n\nQuestion 2c: What is the exact content of the \"Short-Range based positioning information\" IE in the Table  9.3.2.66-1?\n\n\n2. Actions:\nTo SA6 group.\nACTION: \tCT3 kindly asks SA6 to provide feedback on above questions.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":20100,"status":"replied to","reservation_date":"2025-02-05 10:58:26","uploaded":"2025-05-02 11:03:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"eLSAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"CT1","lsoriginalls":"C3-251572","lsreply":"S6-252150","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_067_Fukuoka\/docs\/S6-252010.zip","group":"S6","meeting":"S6-67","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-252011","title":"LS reply on generation of AF specific UE ID","source":"SA2 [S2-2504396]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall description\nSA2 thanks SA6 for the question in the LS S2-2502845 (S6-250286) seeking clarification on the assignment of AF specific UE IDs. \nSA2 discussed the question and would like to provide the following clarifications. \nSA2 would like to clarify that AF specific UE IDs associated to a given SUPI are defined as subscription data stored in UDM\/UDR. Operator provisioning of AF specific UE IDs in UDM\/UDR is required. The procedure to provision subscription data in UDM\/UDR is outside the scope of 3GPP.\nRegarding the dynamic generation of AF specific UE Identifiers, SA2 has approved CR 6168 for 3GPP TS 23.501 and CR 5413 for 3GPP TS 23.502. These CRs provide the possibility for UDM, based on operator policies, to generate an AF specific UE ID when there is no AF specific UE ID stored in UDR for the SUPI and the requesting AF is authorized to receive an AF specific UE identifier. In this way, only UDM internal logic is impacted and no other NF or interface is impacted. This allows CRs to be agreed for Release 19.\nThe error code returned by NEF (as defined in Stage 3 specification 3GPP TS 29.522) for a failed AF Specific UE Identifier retrieval is necessary to handle potential error cases even in case of dynamic generation of identifiers (e.g., situation where the requesting AF is not authorized to receive an AF specific UE identifier). \n\n2. \tActions\nACTION: \t\nSA2 requests SA6 to take the above information into account.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":20110,"status":"noted","reservation_date":"2025-02-05 10:58:26","uploaded":"2025-05-02 11:03:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"CT3","lsoriginalls":"S2-2504396","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_067_Fukuoka\/docs\/S6-252011.zip","group":"S6","meeting":"S6-67","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-252012","title":"LS reply on User authentication for IOPS","source":"SA3 [S3-251672]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. \tOverall description\nSA3 would like to thank SA6 for their LS on user authentication for IOPS. In that regard, SA3 have the following answer to the question provided.\n\nTo authenticate a MC user to access the MC system, procedures defined in TS 33.180 clause 5.1.3 can be reused. SA6 shall be aware, that the required functions for authentication and authorisation shall be available in the isolated operations domain.\n\n2. \tActions\nTo SA WG6 \nACTION: \tSA3 kindly asks SA6 to take the answer into account.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":20120,"status":"noted","reservation_date":"2025-02-05 10:58:26","uploaded":"2025-05-02 11:03:29","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"MCXSec4"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA3","lsoriginalls":"S3-251672","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_067_Fukuoka\/docs\/S6-252012.zip","group":"S6","meeting":"S6-67","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]