[{"name":"S6-151005","title":"LS reply on ProSe Priorities","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"TSG CT, TSG RAN, TSG SA and PCG\/OP","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-09-30 15:09:30","uploaded":"2015-10-01 14:16:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_007_Belgrade\/Docs\/S6-151005.zip","group":"S6","meeting":"S6-7","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-151006","title":"Reply LS on status for MCPTT in SA6 and questions on Rx interface usage","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"TSG CT, TSG RAN, TSG SA and PCG\/OP","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-09-30 15:09:30","uploaded":"2015-10-01 14:16:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_007_Belgrade\/Docs\/S6-151006.zip","group":"S6","meeting":"S6-7","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-151007","title":"Reply LS on Rel-13 ProSe UE-to-Network Relay work","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"TSG CT, TSG RAN, TSG SA and PCG\/OP","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2015-09-30 15:09:30","uploaded":"2015-10-01 14:16:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_007_Belgrade\/Docs\/S6-151007.zip","group":"S6","meeting":"S6-7","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-151008","title":"Clarification on SA6 Architecture","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"TSG CT, TSG RAN, TSG SA and PCG\/OP","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2015-09-30 15:09:30","uploaded":"2015-10-01 14:16:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_007_Belgrade\/Docs\/S6-151008.zip","group":"S6","meeting":"S6-7","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-151009","title":"LS to SA6 on MCPTT support over MBMS","source":"SA4","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"TSG CT, TSG RAN, TSG SA and PCG\/OP","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2015-09-30 15:09:30","uploaded":"2015-10-01 14:16:26","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"http:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_007_Belgrade\/Docs\/S6-151009.zip","group":"S6","meeting":"S6-7","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-151010","title":"Response LS on proposed method of restricting access to IOPS cells","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"TSG CT, TSG RAN, TSG SA and PCG\/OP","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2015-09-30 15:09:30","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S6","meeting":"S6-7","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-151011","title":"Response LS on progress of IOPS in SA2 and security study dependencies","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Decision","abstract":"","secretary_remarks":"","agenda_item_sort_order":6,"ainumber":"4.1","ainame":"TSG CT, TSG RAN, TSG SA and PCG\/OP","tdoc_agenda_sort_order":0,"status":"withdrawn","reservation_date":"2015-09-30 15:09:30","uploaded":null,"revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"","Cc":"","lsoriginalls":"","lsreply":"","link":"","group":"S6","meeting":"S6-7","year":2015,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"S6-255008","title":"LS  to 3GPP about the external data channel content access requirements","source":"GSMA NG UPG","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":50080,"status":"replied to","reservation_date":"2025-02-11 13:57:52","uploaded":"2025-11-03 08:44:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA1, SA2,SA3, SA4 ,SA6, CT","Cc":"","lsoriginalls":"UPG14_109r3","lsreply":"S6-255222","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_070_Dallas\/Docs\/S6-255008.zip","group":"S6","meeting":"S6-70","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-255009","title":"LS reply regarding LS on Application user consent SID","source":"GSMA OPG [OPG_244_Doc_05]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":50090,"status":"noted","reservation_date":"2025-02-11 13:57:52","uploaded":"2025-11-03 08:46:05","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG, SA6","Cc":"","lsoriginalls":"OPG_244_Doc_05","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_070_Dallas\/Docs\/S6-255009.zip","group":"S6","meeting":"S6-70","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-255010","title":"Reply LS on N6 measurement exposure","source":"SA2 [S2-2509811]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":50100,"status":"replied to","reservation_date":"2025-02-11 13:57:52","uploaded":"2025-11-03 08:46:05","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"TEI20"},{"winame":" EDGEAPP_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S2-2509811","lsreply":"S6-255122, S6-255322, S6-255642","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_070_Dallas\/Docs\/S6-255010.zip","group":"S6","meeting":"S6-70","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-255011","title":"Reply LS on digital assets authentication","source":"SA3 [S3-253665]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":50110,"status":"noted","reservation_date":"2025-02-11 13:57:53","uploaded":"2025-11-03 08:46:05","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"Metaverse_Ph2-APP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S3-253665","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_070_Dallas\/Docs\/S6-255011.zip","group":"S6","meeting":"S6-70","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-255012","title":"Reply LS on Security risk of usage permission management of Digital Asset","source":"SA3 [S3-253666]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":50120,"status":"noted","reservation_date":"2025-02-11 13:57:53","uploaded":"2025-11-03 08:46:05","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S3-253666","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_070_Dallas\/Docs\/S6-255012.zip","group":"S6","meeting":"S6-70","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-255318","title":"Reply LS on IMS Data Channel","source":"SA3-LI","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":53180,"status":"noted","reservation_date":"2025-10-11 17:16:56","uploaded":"2025-11-10 17:42:37","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"LI19"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, CT1, CT4, SA3","Cc":"SA6","lsoriginalls":"s3i250674","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_070_Dallas\/Docs\/S6-255318.zip","group":"S6","meeting":"S6-70","year":2025,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-260009","title":"Clarification on the reporting threshold on the number of matched events","source":"CT3 [C3-255559]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. \tOverall description\nIn CT3 #144 meeting, CT3 was discussing the encoding of \"Event reporting information\" information element defined in Table 8.8.2.1-2 of 23.222.\nCT3 would like to ask the following questions:\nQuestion 1: For which CAPIF events defined in Table 8.8.6-1 of 23.222 the event reporting information may include a reporting threshold on number of matched events, optionally within a time window, that indicates how many times an event must be matched to trigger a notification?\nQuestion 2: Can SA6 provide more details on the content of this IE and how it expects it to work, and also if relevant, an example of its usage?\n\n2\t. Actions\nTo SA6 group\nACTION: \tCT3 kindly asks SA6 to reply to the question and update the specifications (if needed).","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":10,"status":"replied to","reservation_date":"2026-01-19 00:35:50","uploaded":"2026-01-21 00:20:40","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"CAPIF_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"C3-255559","lsreply":"S6-260143, S6-260143, S6-260375, S6-260759","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_071_Goa\/Docs\/S6-260009.zip","group":"S6","meeting":"S6-71","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-260010","title":"LS reply regarding feedback on 3GPP enabler layer exposure services","source":"OPG [OPG_248_Doc_06]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Summary\nGSMA Operator Platform Group (OPG) thanks 3GPP TSG SA WG6 for the LS regarding 3GPP enabler layer exposure services.   \n\n2. \tDetails\nIn the context of the referred study, 3GPP TSG SA WG6 requested OPG for more information about the following point:\n3GPP kindly requests 5GAA, 5GACIA, GSMA OPG to review the listed specifications and would like to have the feedback to help us improve the contents of these specifications.\nOPG answer:\nThe GSMA OPG relies on CAMARA APIs for Operator Platform (OP) North Bound Interface (NBI) exposure to application developers. Those can consume the CAMARA APIs that operators offer through GSMA Open Gateway for solving their use cases. As an open-source Linux Foundation project, CAMARA is open to participation by parties in every industry to assure that the APIs defined are aligned with their needs, capabilities and ecosystem architecture.\n3GPP APIs (NEF\/CAPIF, possibly SEAL) can be considered as an option for the South Bound Interface (SBI) of the OP to enable offering the CAMARA APIs on the NBI of the OP in operator networks. It is up to the operator to decide whether to use this option or to adopt alternative approaches that may better align with their internal architecture. This choice should have no impact on the APIs and functionality exposed to application developers. \nThe OPG does not use 3GPP APIs for northbound exposure towards application developers. No need was identified in the OPG to document how SEAL APIs can be used in the SBI. \n\n3. \tActions\nGSMA OPG kindly requests 3GPP TSG SA WG6, 5GAA and 5GACIA to take the above information into account.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":20,"status":"noted","reservation_date":"2026-01-19 00:35:50","uploaded":"2026-01-21 00:20:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG SA WG6, 5GAA, 5GACIA","Cc":"","lsoriginalls":"OPG_248_Doc_06","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_071_Goa\/Docs\/S6-260010.zip","group":"S6","meeting":"S6-71","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-260011","title":"Reply LS to SA (cc SA2, SA3, SA4, SA6, CT) on external data channel content access requirements","source":"SA1 [S1-254509]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"1\t. Overall description\nSA1 thanks NG UPG for their LS on the external data channel access. SA1 would like to answer Question 6:\n6. Question 6 to SA1: \nGiven the fact that IMS telephony services are subject to telecom regulation while HTML and JavaScript content is not a subject to such regulation what is 3GPP SA1 view on if and what regulatory exceptions apply to 3GPP TS 26.114 defined IMS Data Channel applications in general and specifically when those applications are mixed with the external content. \n\nSA1 answer: \nWhen lMS Data Channel is used as a part of lMS telephony services, lMS Data Channel applications, including their HTML and JavaScript content, are expected to be subject to local telecom regulation, when used for other services, e.g. standalone Data Channel, they are subject to applicable regulations which could also include local telecom regulations. The existence of any exceptions is likewise contingent upon these regulations. However, it is not up to SA1 to decide to which specific regulation(s) HTML and JavaScript content would be subject to.\n\n2. \tActions\nTo SA: \nACTION: SA1 kindly asks SA to consolidate SA1 reply and replies from other working groups, and respond to GSMA NG UPG.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":30,"status":"noted","reservation_date":"2026-01-19 00:35:50","uploaded":"2026-01-21 00:20:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA2, SA3, SA4, SA6, CT","lsoriginalls":"S1-254509","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_071_Goa\/Docs\/S6-260011.zip","group":"S6","meeting":"S6-71","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-260012","title":"Reply LS on URL for downloading the DC Application list","source":"SA4 [S4-251998]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nSA4 thanks SA6 for their liaison on URL for downloading DC Application list in S4-251676 (S6-254794), and would like to provide the following answers to the questions in that document, for SA6\u2019s information and further consideration:\nQuestion 1:\tCould SA4 clarify whether this URL can be modified to carry query parameters to support SA6's study on DC application list search?\nAnswer 1:\tSA4 would like to emphasize that it is only the very first URL that is restricted to the root (\u201c\/\u201d) URL and believes that such well-defined starting point is a desirable feature for security and trust purposes. SA4 further notes that such approach does not need to change to enable more advanced web functionality, for example searching.\nSuch restricted and well-defined starting point:\n 1) \tdoes not require downloading a full list of applications, i.e., the returned content is not standardized and is not even in any way restricted to be an \"application list\" or \u201cmenu\u201d\n 2) \tis a web page with all the user interface, hyperlinking properties, and functional possibilities of a modern web page\n 3) \tin current specification does not mandate that only a single URL is ever used for managing and selecting applications, but there may be multiple, subsequent HTTP requests\/responses using other URLs (that are not restricted) sent over the same bootstrap data channel\n 4) \tdoes not in any way prevent the returned \"application list\" content from being, e.g., a categorized, multi-level and\/or search page that contains user interface constructs such as edit boxes, buttons, etc., that could trigger HTTP requests with other URLs, e.g., with query parameters to facilitate any desired search functionality\nQuestion 2:\t If the answer to Question 1 is No, then could SA4 update the above clause to support the use case of DC Application list search?\nAnswer 2:\tSA4 believes that no functional update to current specification is necessary to enable the desired functionality, and it should already be possible to support the use case of DC Application list search, as described above. SA4 has updated TS 26.114 to make the above clearer and attaches the agreed CR.\n\n2\t. Actions\nTo SA6:\nACTION:\tSA4 kindly asks SA6 to take the above answers into account, which in SA4 opinion should address the questions in the LS. If not, SA4 kindly requests SA6 to clarify their use cases further.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":50,"status":"noted","reservation_date":"2026-01-19 00:35:50","uploaded":"2026-01-21 00:20:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_MMTel_Ph2_APP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA2","lsoriginalls":"S4-251998","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_071_Goa\/Docs\/S6-260012.zip","group":"S6","meeting":"S6-71","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-260013","title":"LS Response on external data channel content access requirements","source":"SA [SP-251693]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"1. Overall Description:\nSA thanks GSMA NG UPG for their LS on external data channel content access requirements.\nBased on input from SA WGs, SA would like to provide a consolidated reply covering SA1, SA3, SA4 and SA6. SA2 has already provided a separate reply directly to GSMA NG UPG. \nFeedback from SA1\n\nWhen lMS Data Channel is used as a part of lMS telephony services, lMS Data Channel applications, including their HTML and JavaScript content, are expected to be subject to local telecom regulation, when used for other services, e.g. standalone Data Channel, they are subject to applicable regulations which could also include local telecom regulations. The existence of any exceptions is likewise contingent upon these regulations. However, it is not up to SA1 to decide to which specific regulation(s) HTML and JavaScript content would be subject to.\n\nFeedback from SA3\n\nSA3 does not currently have plans to standardize security architecture and measures for content and source validation including the method to compute trust towards external hosts and content. SA3 will keep GSMA NG UPG informed if there is any update in the future.\n\nFeedback from SA4\n\nSA4 thanks GSMA NG UPG for their Liaison Statement (UPG14_109r3) highlighting the important issue regarding the ambiguity and potential confusion in handling external resource access in IMS Data Channel applications.\nSA4 acknowledges the gaps pointed out by GSMA NG UPG and agrees that the current specification (TS 26.114) does not explicitly address scenarios involving external resource mashups clearly enough. Originally, SA4 assumed that the Data Channel Signalling Function (DCSF) and the Data Channel Application Server (DC AS) would be the exclusive hosts for all content and thus, did not anticipate scenarios involving external resources.\nAs such, 3GPP SA4 plans to study this issue and provide the necessary clarifications as part of the DC Enhancements (FS_DCE_MED) study in Release 20.\n\nFeedback from SA6\n\nSA6 has not yet studied the procedures and architecture for interworking between the IMS domain and external (non-IMS) content sources.\n\nIn the CAPIF framework defined by SA6 in 3GPP TS 23.222, third-party API providers are introduced. In this scenario, third-party API providers can securely expose their capabilities to other services under the control of the PLMN, meaning that the resources of third-party API providers can be securely utilized by other services. The architecture and corresponding procedures for these third-party API providers in non-3GPP systems could potentially serve as a reference for the procedures of interworking between the IMS session and external (non-IMS) content sources.\n\nSA6 will keep GSMA NG UPG informed of their progress.\n\n\n2. Actions:\nTo GSMA NG UPG\nAction: SA kindly asks GSMA NG UPG to take the above feedbacks into account.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":40,"status":"noted","reservation_date":"2026-01-19 00:35:50","uploaded":"2026-01-21 00:20:40","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA NG UPG","Cc":"TSG CT, SA1, SA2, SA3, SA4, SA6","lsoriginalls":"SP-251693","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_071_Goa\/Docs\/S6-260013.zip","group":"S6","meeting":"S6-71","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-260014","title":"LS on Completion of AIML_CAL Study","source":"SA [SP-251699]","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nTSG SA conducted the Study on AI\/ML consistency alignment in TR 22.850 and the TR was approved in SA#110. \n\nThe CR to TR 21.905 attached was approved and corresponds with these findings to define a consistent terminology to be used across all groups.\n\nThere is no further work planned on this activity.\n\n\n2. Actions:\nTo TSG RAN, TSG CT, \tSA WG1, SA WG2, SA WG3, SA WG4, SA WG5, SA WG6, RAN WG1, RAN WG2, RAN WG3, RAN WG4, RAN WG5, CT WG1, CT WG3, CT WG4, CT WG6 \nACTION: \t\nTSG SA asks to take the above into account.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":60,"status":"noted","reservation_date":"2026-01-19 00:35:50","uploaded":"2026-01-21 00:20:40","revisionof":"","revisedto":"","release":"Rel-19","crspec":"","crspecversion":"","workitem":[{"winame":"FS_AIML_CAL"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, RAN1, RAN2, RAN3, RAN4, RAN5 TSG CT, CT1, CT3, CT4, CT6  \nSA1, SA2, SA3, SA4, SA5, SA6","Cc":"","lsoriginalls":"SP-251699","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_071_Goa\/Docs\/S6-260014.zip","group":"S6","meeting":"S6-71","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-260374","title":"LS on LI requirements","source":"SA3-LI","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nAs part of its 6G discussion, SA3-LI has determined that all of the currently defined LI requirements contained in TS 33.126 shall still apply, and may be expanded to accommodate changes related to 6G work in SA2.\n\nWhile it is SA3-LI\u2019s task to specify the LI solution for 6G, SA3-LI kindly requests that SA2, SA3, SA4 and SA6 send LSs to SA3-LI on potential topics within SA2, SA3, SA4 and SA6 that may require input from SA3-LI before the 6G architecture is fully confirmed. It is the experience of SA3-LI that fully formed architecture with LI considerations made after development has the potential to cause issues and the system design may not be able to support LI requirements in all jurisdictions or legal frameworks.\n\nSA3-LI kindly requests that SA2, SA4 and SA6 take LI requirements, as they exist in TS 33.126 and any future 6G expansion into account as the 6G architecture is defined.\n\nSA3-LI kindly requests to include the following text at the end of clause 4.2 of TR 23.801-01 and to the TRs\/TSs under development for 6G in other WGs:\n-\tLawful interception requirements shall be taken into account for all WTs and corresponding key issues in this study. For more details on LI requirements, see TS 33.126.\n\n\n2. Actions:\nTo SA2 group.\nACTION:\tSA3-LI kindly requests the SA2 group to add reference to LI requirements to clause 4.2 of TR 23.801-01 with the text above.\nSA3-LI kindly requests SA2 to ask SA3-LI if SA2 requires clarification on any aspects of TS 33.126.\nSA3-LI kindly requests SA2 to inform SA3-LI if SA2 is aware of any issues in the solutions being considered in TR 23.801-01 which, in SA2's view, may prevent SA3-LI from defining solutions that comply with TS 33.126.\n\nTo SA3, SA4 and SA6 groups.\nACTION:\tSA3-LI kindly requests the SA3, SA4 and SA6 groups to add reference to LI requirements to 6G studies with the text above.\nSA3-LI kindly requests SA3, SA4 and SA6 to ask SA3-LI if any among SA3, SA4 and SA6 requires clarification on any aspects of TS 33.126.\nSA3-LI kindly requests SA3, SA4 and SA6 to inform SA3-LI if any among SA3, SA4 and SA6 is aware of any issues in the solutions being considered in their 6G studies which, in their view, may prevent SA3-LI from defining solutions that comply with TS 33.126.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":70,"status":"postponed","reservation_date":"2026-06-02 10:20:33","uploaded":"2026-02-07 05:14:35","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA2, SA3, SA4, SA6","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_071_Goa\/Docs\/S6-260374.zip","group":"S6","meeting":"S6-71","year":2026,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]