[{"name":"S6-223087","title":"Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. Overall Description:\nSA2 thanks SA6 on their LS (S2-2205458 \/ S6-221953) and provides the following feedback on the SA6 questions.\n\n-\tAs mentioned in KI#16 about AF (e.g. EES) with a NATted UE IP address, can SA2 support taking NATted UE IP address as input and then exposing the UE External ID to EES?\n\nCurrently (in Rel-17) there is no specification support for NAT devices controlled by 5GS, as indicated in the following NOTE in TS 23.501 clause 5.6.10.1:\nNOTE 2:\tAn operator can deploy NAT functionality in the network; the support of NAT is not specified in this release of the specification.\nAs well as in the following NOTE in TS 23.502 clause 4.15.10:\nNOTE 3:\tThe case where UE IP address provided by the AF to the NEF corresponds to an IP address that has been NATed (Network and Port Address Translation) is not supported in this release.\nAs a consequence, there is currently no specification support for exposure of UE External ID based on the NATted UE IP address.\nSA2 would like to point out that there is a related work as part of the ongoing Rel-18 study FS_UPEAS. However SA2 has not yet concluded or agreed any solution for normative work.\n\n-\tIn solution #23, EES (as AF) invokes Nnef_UEID API with UE private IP address allocated by 3GPP CN. In certain deployment when multiple UEs are allocated with the same private IP address, can SA2 support addressing IPv4 address overlap issue?\n\nThe case where multiple UEs are allocated with the same private 5GC IP address is currently addressed as follows \n-\twhen this same private IP address is allocated to different UE(s) for different DNN and S-NSSAI(s) by associating the AF with a DNN and S-NSSAI\n-\tOtherwise and furthermore, the \"ipDomain\" attribute as defined in TS 29.514 clause 4.2.2.2 Note 3 may be leveraged \nThe above DNN\/S-NSSAI or ipDomain attribute is not expected to be exposed outside the 5GC network.\n\n\n2. Actions:\nTo SA6 group.\nACTION: \tSA2 respectfully asks SA6 to take into account the feedback above.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":30870,"status":"replied to","reservation_date":"2022-10-31 21:50:30","uploaded":"2022-11-01 10:48:16","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eEDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA3","lsoriginalls":"S2-2207394","lsreply":"S6-223198","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223087.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223088","title":"LS reply to 3GPP SA6 on Clarification of Edge Node Sharing","source":"GSMA OPG","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"Question for 3GPP SA6: \nThe edge sharing procedure defined in OPG OPAG is shown in the Figure 3 below:\n Only one registration is performed between the UE-A and OP\u2013A. The UE-A is then redirected towards the content hosted by OP - B with who edge sharing is performed.  GSMA OPG would like to receive 3GPP SA6 feedback if the current procedure is acceptable.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":30880,"status":"replied to","reservation_date":"2022-10-31 21:50:30","uploaded":"2022-11-01 10:51:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA, SA2","lsoriginalls":"OPG_103","lsreply":"S6-223211, S6-223211","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223088.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223089","title":"LS reply to GSMA OPAG on E\/WBI","source":"ETSI ISG MEC","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":30890,"status":"noted","reservation_date":"2022-10-31 21:50:31","uploaded":"2022-11-01 10:51:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG, OPAG","Cc":"3GPP SA, SA2, SA6","lsoriginalls":"MEC(22)000430r2","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223089.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223090","title":"5G capabilities exposure for factories of the future \u2013 identified gaps","source":"5G Alliance for Connected Industries and Automation (5G-ACIA)","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":30900,"status":"noted","reservation_date":"2022-10-31 21:50:31","uploaded":"2022-11-01 10:51:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP TSG SA, 3GPP TSG CT","Cc":"3GPP TSG SA1, SA2, SA3, SA5, SA6","lsoriginalls":"2022 09 06 5G-ACIA-LS 05","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223090.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223091","title":"3GPP TR 23.700-98 V1.2.0 Analysis","source":"OPG Operator Platform API Group","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":30910,"status":"withdrawn","reservation_date":"2022-10-31 21:50:31","uploaded":"2022-11-01 10:51:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"OPG","lsoriginalls":"OPAG 41 Doc 04","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223091.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223092","title":"Reply LS on 5MBS User Services","source":"SA4","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":30920,"status":"noted","reservation_date":"2022-10-31 21:50:31","uploaded":"2022-11-01 10:50:25","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBUSA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"SA2, SA6, CT4","lsoriginalls":"S4aI221402","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223092.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223093","title":"Reply LS on Security Requirements for the MSGin5G Service","source":"SA3","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":30930,"status":"noted","reservation_date":"2022-10-31 21:50:31","uploaded":"2022-11-01 10:50:36","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"5GMARCH_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"CT1","lsoriginalls":"S3-222525","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223093.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223094","title":"LS on SNAAPP requirements clarifications","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nDuring discussion of the SA1 defined requirements for SNAAPP security, SA3 noticed that there were different interpretations possible. Therefore, SA3 would like to request clarifications.\nTS 22.261 contains the following two requirements:\n1: provide a third-party with secure access to APIs (e.g. triggered by an application that is visible to the 5G system), by authenticating and authorizing both the third-party and the UE using the third-party's service.\n2: provide a UE with secure access to APIs (e.g. triggered by an application that is not visible to the 5G system), by authenticating and authorizing the UE.\nSA3 would like to request for clarification of requirement 1:\nFrom security point of view, the third party may use any authorization that is given to any triggerer by a specific resource owner. Thus the requirement 1 seems to place some amount of trust into the third party. \nQ1a: What is the purpose of requiring: authenticating and authorizing both the third-party and the UE using the third-party's service?\nQ1b: What would be a use case for this requirement? \nQ1c: Would the third party AF be considered trusted or not trusted in this use case?\nQ1d: Does this requirement also include cases that one UE uses the third party's service to get access to resources from another UE? (Example: In the context of a (hiking) game one UE is receiving the location of another UE.)\nSA3 would like to request for clarification of requirement 2:\nQ2a: Could you please give an example in which a UE is provided with secure access to APIs, triggered by an application that is not visible to the 5G system?\nQ2b: How would the 3GPP system allow access on application level if the applications are not visible to the 3GPP system? \nQ2c: Would at least the UE be aware of which application is triggering the UE to access the API? \nQ2d: Would this requirement also be relevant for a UE requesting resources of another UE?\nSA3 would like to request for clarification that applies to both requirements:\nIt is not clear to SA3 whether the \"application\" in the requirements 1 and 2 indicate an application on the UE or an application on the third party AF. According to Figure 4.1.1-1 and Figure 4.2.1-1 in TR 23.700-95, \"Application\" resides on the UE.\nIn case of Figure 4.1.1-1, the \"Application\" seems to be visible to the 5G system, as opposed to the relevant requirement's description, \"triggered by an application that is not visible to the 5G system\".\nOn the other hand, in case of Figure 4.2.1-1, the \"Application\" seems to be invisible to the 5G system, as opposed to the relevant requirement's description, \"triggered by an application that is visible to the 5G system\".\nQ3a: What does the \"application\" in the two requirements indicate? Is it an application on the UE or an application on the third party AF?\nQ3b: What is the meaning of \"application that is visible to the 5G system\"? Does this mean that the application has a direct communication with an entity of the 5G system, or any other meaning?\n\n2. \tActions\nTo SA1 \nACTION: \tSA3 would kindly request SA1 to clarify the above questions.\nTo SA6\nACTION: \tSA3 would kindly request SA6 to point out their interpretation of requirement 1 and 2 in their use cases.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":30940,"status":"replied to","reservation_date":"2022-10-31 21:50:31","uploaded":"2022-11-01 10:50:46","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_SNAAPPY"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA1, SA6","Cc":"","lsoriginalls":"S3-222970","lsreply":"S6-223184, S6-223184","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223094.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223095","title":"Draft LS reply on CAPIF authorization roles related to FS_SNAAPP","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nSA3 would like to thank SA6 for their LS on CAPIF authorization roles related to FS_SNAAPP.\nSA3 has just started studying in TR 33.884  security aspects of the SA6 study on enhancements to the existing CAPIF functional model so that the CAPIF can support the subscriber-aware northbound API access (SNA). \nSince it is mentioned in the description on SA6's LS, SA3 would like to ask whether for the current release of the standard resource owner+ in the scenarios considered by SA6 is always the user .  \nSA3 would like to provide the following preliminary feedback to SA6 questions. :\n1.\tSA6 would like to receive feedback on the solutions in the TR that are identified with SA3 dependency.\nAnswer: SA3 will study the solutions for which  SA6 has identified an SA3 dependency. \n2.\tClause 6.2 of TR 23.700-95 contains potential functional models for SNAAPP. SA6 would like SA3 to assess the functional models and provide feedback on their viability. Especially, SA6 would like SA3 to provide feedback on the following points:\n....","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":30950,"status":"replied to","reservation_date":"2022-10-31 21:50:31","uploaded":"2022-11-01 10:50:58","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_SNAAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S3-222972","lsreply":"S6-223185, S6-223185","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223095.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223096","title":"Reply LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1\t. Overall description\nSA3 would like to thank the SA6 for their LS on FS_eEDGEAPP Solution for Support of NAT deployed within the edge data network.\nRegarding \u201cwhether there is security issue if the EEC share its private IP address with a trusted 3rd party EES. If yes, could SA3 address security issues related to this\u201d, SA3 agreed that, in general, it is not desirable for the network to rely on unverifiable\/unverified information provided by the UE. The security issue is that such information can be faked and thus can be used to impersonate a UE.\nMoreover, SA3 has observed that the solution suggested by SA6 is incomplete. A private IP address can be shared by multiple UEs. In order to disambiguate this IP address, additional information needs to be used\/provided. Providing\/disclosing this \u2013 as yet unspecified \u2013 additional information may have its own security risks. Without further information on the intended complete solution, however, SA3 cannot assess these risks.\n\n2. \tActions\nTo SA6\nACTION: \tSA3 would like to ask the SA6 to consider the above reply.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":30960,"status":"replied to","reservation_date":"2022-10-31 21:50:31","uploaded":"2022-11-01 10:51:22","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":[{"winame":"FS_eEDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA2","lsoriginalls":"S3-223018","lsreply":"S6-223331","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223096.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223103","title":"3GPP TR 23.700-98 V1.2.0 Analysis","source":"OPG Operator Platform API Group","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"1. \tIntroduction\nGSMA Operator Platform API Group (OPAG) has been working on the analysis of 3GPP TR 23.700-98 V1.2.0 (2022-09) to understand its relationship to Federation, Edge Sharing and Roaming and the work GSMA OPAG is doing.\n2\t. Enhanced Application Architecture\nThe target architectures to be analysed are presented in the sections 6.1 and 6.2 of the 3GPP TR 23.700-98 V1.2.0 (2022-09). \nGSMA OPAG identified that these architectures might be related to the proposed solutions for the following key issues:\n\u2022\tKey Issue #6: Edge services support across ECSPs.\n\u2022\tKey Issue #9: Enhancement of dynamic EAS instantiation triggering.\n \u2022 \tKey Issue #10: Support for roaming UEs.\n \u2022 \tKey Issue #17: Discovery of a common EAS.\n \u2022 \tKey Issue #20: Method of supporting federated EAS service\n \u2022 \tKey Issue #22: EAS discovery in Edge Node sharing scenario\nConsidering the description in the 3GPP TR 23.700-98, it is clear that the EDGE-10 interface has an important role in the proposed architectures and solutions, for example:\n \u2022 \tSolution #5: ECS enhancement to discover EESs via other ECSs to support edge services across ECSPs.\n \u2022 \tSolution #14: V-ECS Discovery via the H-ECS.\nAs a part of the analysis, GSMA OPAG would like to understand if 3GPP EDGE-10 interface can be endorsed as part of the OPAG EWBI. However, we could not find a formal definition for EDGE-10 interface in 3GPP specifications. \n\n3. \tConclusion and actions\nGSMA OPAG kindly ask 3GPP SA6 to provide a detailed description of the services and capabilities offered by the EDGE-10 interface and its relation to Federation, Edge Sharing and Roaming scenarios. \nGSMA OPAG would also like to understand whether 3GPP SA6 is considering the EWBI defined in GSMA PRD OPG.04  for the realisation of the Edge-10 interface.","secretary_remarks":"","agenda_item_sort_order":9,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":31030,"status":"replied to","reservation_date":"2022-11-02 13:23:01","uploaded":"2022-11-02 13:26:17","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"OPG","lsoriginalls":"OPAG 41 Doc 04","lsreply":"S6-223335, S6-223613","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223103.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-223115","title":"LS on GSMA OPG PRDs publication","source":"GSMA OPG","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":31150,"status":"noted","reservation_date":"2022-11-02 17:42:53","uploaded":"2022-11-02 18:33:24","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA2, SA6, ETSI ISG MEC","Cc":"3GPP SA","lsoriginalls":"OPG 111 Doc 03","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052_Toulouse\/Docs\/S6-223115.zip","group":"S6","meeting":"S6-52","year":2022,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230007","title":"Reply LS on 5MBS User Services","source":"SA4","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"5MBUSA"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"SA2, SA6, CT4","lsoriginalls":"S4-221415","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230007.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230008","title":"LS on EAS type attribute for EAS discovery","source":"CT3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"replied to","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"EDGEAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"CT1","lsoriginalls":"C3-225657","lsreply":"S6-230452","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230008.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230009","title":"Reply LS on user\u2019s consent for EDGEAPP","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":[{"winame":"eEDGE_5GC"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"CT3","Cc":"SA2, SA6, CT4","lsoriginalls":"S3-223904","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230009.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230010","title":"Reply LS on Network Parameters Configuration for IoT Platforms","source":"SA2","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_ACE_IOT"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S2-2211128","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230010.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230011","title":"Reply LS on Network federation interface for Telco edge consideration","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_EDGE_Ph2"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GPP SA, SA6, SA2, SA5.","Cc":"3GPP CT, CT1, CT3, CT4","lsoriginalls":"S3-223914","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230011.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230012","title":"Reply LS on Support PIN application architecture and interaction","source":"SA3","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PINAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"S3-224068","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230012.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230013","title":"Reply LS on QoS Sustainability analytics and V2X service adaptations","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA","Cc":"SA2, SA6","lsoriginalls":"S1-223734","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230013.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230014","title":"Reply LS on PIN Management","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"FS_PINAPP"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA2","lsoriginalls":"S1-223538","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230014.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230015","title":"Reply LS on DN energy efficiency data analytics","source":"SA1","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Action","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"SA5","lsoriginalls":"S1-223542","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230015.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230016","title":"Reply LS to S5-226028 on Network federation interface for Telco edge consideration and proposals to answer GSMA LSs 5-226016 and S5-226017 from SA","source":"SA5","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eECM"},{"winame":" FS_NSCE"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"3GGP SA, SA6","Cc":"3GPP SA2, SA3","lsoriginalls":"S5-227039","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230016.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230017","title":"Reply LS on QoS Sustainability analytics and V2X service adaptations","source":"SA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"eNA_Ph3"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5GAA Working Group 4, Working Group 1, Working Group 2","Cc":"3GPP SA1, SA2, SA6","lsoriginalls":"SP-221320","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230017.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230018","title":"Reply LS on Network federation interface for Telco edge consideration","source":"SA","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Information","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-02-01 23:15:04","uploaded":"2023-01-06 15:38:30","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPAG, GSMA OPG","Cc":"3GPP SA2, SA3, SA5,  SA6, ETSI ISG MEC","lsoriginalls":"SP-221321","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230018.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0},
{"name":"S6-230283","title":"LS on the consent of draft new Recommendation ITU-T Q.3647 \u201cSignalling requirements for emergency service in IMS roaming environment\u201d","source":"ITU-T Study Group 11","contact":"Bernt Mattsson","contact-id":14585,"tdoctype":"LS in","for":"Discussion","abstract":"","secretary_remarks":"","agenda_item_sort_order":7,"ainumber":"4.1","ainame":"Incoming LSs","tdoc_agenda_sort_order":0,"status":"noted","reservation_date":"2023-11-01 09:51:20","uploaded":"2023-01-11 09:52:43","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"SA6","Cc":"","lsoriginalls":"SG11-LS42","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/WG6_MissionCritical\/TSGS6_052-bis-e\/Docs\/S6-230283.zip","group":"S6","meeting":"S6-52-bis-e","year":2023,"uicc_affected":"","me_affected":"","ran_affected":"","cn_affected":"","clauses_affected":"","crsinpack":null,"crsinpacknumber":0}]