[{"name":"SP-220006","title":"LS from ITU-R WP5D: Development of a draft new Report ITU-R M.[IMT.INDUSTRY] -Applications of IMT for specific societal, industrial and enterprise usages","source":"ITU-R WP5D","contact":"Uwe Loewenstein","contact-id":11941.0,"tdoctype":"LS in","for":"Information","abstract":"'Applications of IMT for specific societal, industrial and enterprise usages'. The scope of this draft new Report ITU-R M.[IMT.INDUSTRY] addresses, inter alia, the usage, technical and operational aspects and capabilities of IMT for meeting specific needs of societal, industrial and enterprise usages. Current preliminary draft working document being developed in the WP 5D is enclosed for reference (TEMP\/463Rev.2 published as 5D\/886 (Annex 3.3)). This work has been initiated under Question ITU-R 262\/5. WP 5D would like to invite the External Organizations to provide information on industrial and enterprise on its usage, applications, required capabilities, technical and operational aspects, and any other related material that would facilitate in completion of this Report. External Organizations are invited to provide material preferably to the 40th meeting of WP 5D but no later than 41st meeting of WP 5D, as appropriate. Working Party 5D looks forward to collaborating with External Organizations on this matter. Working Party 5D will keep the External Organizations informed of the progress and outcomes of relevant studies in future WP 5D meetings.","secretary_remarks":"Revision of Postponed SP-211412 from SA#94-e. Final response to PCG in SP-220337","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10250,"status":"replied to","reservation_date":"2022-01-19 14:13:41","uploaded":"2022-01-19 14:14:22","revisionof":"SP-211412","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"EXTERNAL ORGANIZATIONS","Cc":"","lsoriginalls":"ITU_R_WP5D_TEMP_464rev3","lsreply":"SP-220337, SP-220337","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220006.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220021","title":"Reply LS on further Operator Platform Group questions following SDO Workshop","source":"SA WG6","contact":"Basavaraj (Basu) Pattan","contact-id":61285.0,"tdoctype":"LS in","for":"Action","abstract":"SA WG6 thanks GSMA OPAG for the workshop held on January 21st, to discuss the details of the Operator Platform API mapping and the feedback from 3GPP. SA WG6 has reviewed the follow-up questions (in incoming LS S6-220120) from GSMA OPAG and prepared the below responses for inclusion into a consolidated response from SA#95e to GSMA OPAG. 1. Which are the security mechanisms\/procedures proposed for UNI authentication? [SA WG6 Response] 3GPP TS 23.558 references 3GPP TS 33.558 for UNI authentication and authorization procedures. SA WG6 recommends SA WG3 to provide additional details related to 3GPP TS 33.558. 2. Are there any additional details regarding the availability of specifications related to EWBI TR 23.700-98? [SA WG6 Response] Based on Rel-18 eEDGEAPP study, a number of key issues and solutions related to EWBI covering Roaming and Federation, Service Continuity and Synchronization are included in the latest 3GPP TR 23.700-98 v0.5.0. The study is expected to complete in June 2022, and subsequent normative work is expected to be completed within Rel-18 timeframe. 3. Has the support for service continuity management been defined in the SCEF\/NEF specification? From the 3gpp references provided, it seems to be supported only in TS 23.558|29.588. [SA WG6 Response] In addition to the service continuity management at the network layer defined in SCEF\/NEF, 3GPP TS 23.558 specifies application layer service continuity at Edge Enabler Layer (EEL), which supports 5 different scenarios (see clause 8.8 of 3GPP TS 23.558). APIs related to Application layer service continuity at EEL are available directly to Edge Application Server (EAS) via EDGE-3. These APIs internally leverage SCEF\/NEF APIs as described in 3GPP TS 23.501 and 3GPP TS 23.502 e.g. for capabilities exposed by the 3GPP core network such as AF traffic influence, the location information, QoS monitoring. SA WG6 recommends additional response from SA WG2 in related SCEF\/NEF. 4. Do 3GPP specifications cover scenarios including session continuity support for handover from 5G networks to 4G and other non-3GPP access technologies? From 3GPP Release 15 onwards, the service and session continuity is described for 5G to 5G handover scenarios with the provision of SSC modes 1, 2 and 3 and an OP is expected to interact with the mobile network over its SBI-NR interface using NEF and SCEF APIs to support end-to-end application session continuity. We would like to know if similar support is envisioned for session continuity for the previously mentioned scenarios, i.e. UE session handovers between 4G or non-3GPP access and 5G. [SA WG6 Response] SA WG6 recommends SA WG2 respond to this question. 5. The Northbound APIs (NEF T8 interfaces) require information like UE IP address, MAC address etc. which is typically managed by 5G core networks. Is there any guidance available on how an external application function (AF) can have access to such information when placed outside of the 5G core network? As the information like UE IP address is internal to mobile network, it may be an issue for external AFs outside the trust zone of mobile networks to get such information and refer to it when using NEF APIs. [SA WG6 Response] An AF can get UE IP address from the received IP packets. The AF can then use the UE IP address to UE ID translation service (provided by 5GC as specified in clause 4.15.10 of 3GPP TS 23.502 or as provided by the EEL as specified in clause 8.6.5 of 3GPP TS 23.558) to translate the UE IP address to UE ID and use it for API invocation. However, if a NAT is deployed between the AF and the UE, the AF would see the public IP address of the UE, that cannot be translated to the UE ID. To allow translation while NAT is deployed, SA WG6 is studying Key Issue #16 in the 3GPP TR 23.700-98. SA WG6 recommends SA WG2 also provide response to this question. 6. As the 3GPP defines interaction between NEF and AF via Northbound APIs, does it impose any kind of timing constraints (soft or hard d","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10330,"status":"noted","reservation_date":"2022-02-28 09:51:59","uploaded":"2022-02-28 10:22:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG5, SA WG3, SA WG2","lsoriginalls":"S6-220432","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220021.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220022","title":"LS from GSMA OPAG: Further Operator Platform Group questions following SDO Workshop","source":"GSMA OPAG","contact":"Maurice Pope","contact-id":648.0,"tdoctype":"LS in","for":"Action","abstract":"Introduction: GSMA OPG Operator Platform API Group (OPAG) would like to thank TSG SA, SA WG2, SA WG5, and SA WG6 delegates, as well as ETSI ISG MEC members, for supporting and attending the workshop on the mapping of SDO specifications to APIs to be exposed or used by the Operator Platform to realise its required interfaces. For delegates that were unable to attend, OPAG would like to inform that a recording of the webinar as well as the slides used are now available at [2] Following the input provided prior to and during the workshop a number of questions came up in the OPAG related to the 3GPP specifications that were referred to. OPAG would like to seek clarification on those to confirm its understanding and ensure that it moves forward on the correct basis. Discussion: Following questions were raised on aspects related to 3GPP's feedback that were unclear to OPAG members: 1. Which are the security mechanisms\/procedures proposed for UNI authentication? 2. Are there any additional details regarding the availability of specifications related to EWBI TR 23.700-98? 3. Has the support for service continuity management been defined in the SCEF\/NEF specification? From the 3gpp references provided, it seems to be supported only in TS 23.558|29.588. 4. Do 3GPP specifications cover scenarios including session continuity support for handover from 5G networks to 4G and other non-3GPP access technologies? From 3GPP Release 15 onwards, the service and session continuity is described for 5G to 5G handover scenarios with the provision of SSC modes 1, 2 and 3 and an OP is expected to interact with the mobile network over its SBI-NR interface using NEF and SCEF APIs to support end-to-end application session continuity. We would like to know if similar support is envisioned for session continuity for the previously mentioned scenarios, i.e. UE session handovers between 4G or non-3GPP access and 5G. 5. The Northbound APIs (NEF T8 interfaces) require information like UE IP address, MAC address etc. which is typically managed by 5G core networks. Is there any guidance available on how an external application function (AF) can have access to such information when placed outside of the 5G core network? As the information like UE IP address is internal to mobile network, it may be an issue for external AFs outside the trust zone of mobile networks to get such information and refer to it when using NEF APIs. 6. As the 3GPP defines interaction between NEF and AF via Northbound APIs, does it impose any kind of timing constraints (soft or hard duration) for AF when AF needs to acknowledge back to 5G Core? As some of the 3GPP network procedures also expect assistance information from external AF e.g. 'the indication of 'AF acknowledgment to be expected' (3GPP TS 23.502 V16.9.0 , 'Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions') included in AF subscription to SMF events, the SMF waits for a notification response from the AF'. It is important to understand if such acknowledgements from external AF are to be strictly bound by timing constraints so that mobile core network procedures may also work correctly. Action: To provide clarity on the questions raised in section 2.","secretary_remarks":"Response drafted in SP-220334. Final Response in SP-220334_rev1 (to be revised)","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10280,"status":"replied to","reservation_date":"2022-02-28 09:51:59","uploaded":"2022-02-28 10:22:52","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA, SA WG2, SA WG5, SA WG6","Cc":"ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"OPAG_09_Doc_04","lsreply":"SP-220334","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220022.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220023","title":"Reply LS on Further GSMA OPAG questions following SDO Workshop","source":"SA WG2","contact":"Hui Ni","contact-id":79738.0,"tdoctype":"LS in","for":"Action","abstract":"SA WG2 has discussed the LS from GSMA OPAG (S2-2201266) and would like to provide the following answers to the questions. SA WG2 kindly asks TSG SA plenary to consider the inputs for a consolidated reply to GSMA OPAG. 1. Which are the security mechanisms\/procedures proposed for UNI authentication? [SA WG2 answer] SA WG3 and SA WG6 are recommended to provide answers to this question. 2. Are there any additional details regarding the availability of specifications related to EWBI TR 23.700-98? [SA WG2 answer] SA WG6 is recommended to provide answers to this question. 3. Has the support for service continuity management been defined in the SCEF\/NEF specification? From the 3gpp references provided, it seems to be supported only in TS 23.558|29.588. [SA WG2 answer] Besides TS 23.558 and 29.588, mechanisms for supporting service continuity are also defined in TS 23.501 and TS 23.548, including e.g. SSC modes, AF influenced traffic routing, Edge relocation. Some of the procedures, .e.g. AF influenced traffic routing, leverage NEF for interaction between AF and 5GS. 4. Do 3GPP specifications cover scenarios including session continuity support for handover from 5G networks to 4G and other non-3GPP access technologies? From 3GPP Release 15 onwards, the service and session continuity is described for 5G to 5G handover scenarios with the provision of SSC modes 1, 2 and 3 and an OP is expected to interact with the mobile network over its SBI-NR interface using NEF and SCEF APIs to support end-to-end application session continuity. We would like to know if similar support is envisioned for session continuity for the previously mentioned scenarios, i.e. UE session handovers between 4G or non-3GPP access and 5G. [SA WG2 answer] PDU Sessions of SSC mode 1, 2, 3 can handover between 3GPP access and non-3GPP access connecting to 5GC. At handover during interworking between 5GC and EPC all PDU sessions are handled as SSC mode 1. 5. The Northbound APIs (NEF T8 interfaces) require information like UE IP address, MAC address etc. which is typically managed by 5G core networks. Is there any guidance available on how an external application function (AF) can have access to such information when placed outside of the 5G core network? As the information like UE IP address is internal to mobile network, it may be an issue for external AFs outside the trust zone of mobile networks to get such information and refer to it when using NEF APIs. [SA WG2 answer] The AF may obtain UE IP address and\/or MAC address via user plane packet or application layer negotiation. If a NAT is deployed between the AF and the UE, the AF may not be able to obtain the UE IP address assigned by the 5GC. Besides IP address or MAC address, an external AF may also use other public identifiers, e.g., GPSI (Generic Public Subscription Identifier), to invoke NEF services. 6. As the 3GPP defines interaction between NEF and AF via Northbound APIs, does it impose any kind of timing constraints (soft or hard duration) for AF when AF needs to acknowledge back to 5G Core? As some of the 3GPP network procedures also expect assistance information from external AF e.g. 'the indication of 'AF acknowledgment to be expected' (3GPP TS 23.502 V16.9.0 , 'Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions') included in AF subscription to SMF events, the SMF waits for a notification response from the AF'. It is important to understand if such acknowledgements from external AF are to be strictly bound by timing constraints so that mobile core network procedures may also work correctly. [SA WG2 answer] Regarding the indicated case on 'the indication of 'AF acknowledgment to be expected'', according to 3GPP TS 23.501 clause 5.6.7.2, the SMF can assume, according to local policy, a negative response if a response is expected but not received from the AF within a certain time window. Action: SA WG2 kindly asks TSG SA plenary to consider the inputs for a consolidated reply to GSMA OPAG.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10310,"status":"noted","reservation_date":"2022-02-28 09:51:59","uploaded":"2022-02-28 10:22:52","revisionof":"","revisedto":"","release":"Rel-17","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG6, SA WG5, SA WG3","lsoriginalls":"S2-2201721","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220023.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220030","title":"LS from SA WG1: LS on Alignment concerning 5G RG requirements and its remote management","source":"SA WG1","contact":"Kurt Bischinger","contact-id":26063.0,"tdoctype":"LS in","for":"Action","abstract":"Action: SA WG1 asks TSG SA to review the attached LS to BBF, amend it as needed, and send it to BBF, with copy to SA WG1.","secretary_remarks":"Response drafted in SP-220338. Final response in SP-220338_rev1","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10340,"status":"replied to","reservation_date":"2022-02-28 09:51:59","uploaded":"2022-02-28 11:16:56","revisionof":"","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"S1-220188","lsreply":"SP-220338","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220030.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220263","title":"LS from SA WG3: Reply LS on Further Operator Platform Group questions following SDO Workshop","source":"SA WG3","contact":"Rajavelsamy Rajadurai","contact-id":33521.0,"tdoctype":"LS in","for":"Action","abstract":"SA WG3 would like to thank GSMA OPAG for their LS on Operator Platform Group questions following SDO Workshop (S3-220443). SA WG3 would like to provide answers to security related questions raised: 1. Which are the security mechanisms\/procedures proposed for UNI authentication? SA WG3 has agreed the attached pCRs (S3-220553 and S3-220554) for the security mechanisms proposed for EDGE-1 and EDGE-4 interfaces. Action: SA WG3 asks TSG SA to take the above information into consideration for inclusion into the consolidated reply from TSG SA to GSMA OPAG.","secretary_remarks":"Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10320,"status":"noted","reservation_date":"2022-03-07 08:10:15","uploaded":"2022-03-07 08:45:58","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"SA WG5, SA WG6, SA WG2","lsoriginalls":"S3-220571","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220263.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220290","title":"LS from 5GAA WG4: LS on provision of inputs to the online ITS communication standards database from ITU","source":"5GAA WG4","contact":"Tao Cai","contact-id":78292.0,"tdoctype":"LS in","for":"Action","abstract":"5GAA would like to inform that ITU is requesting inputs to the ITU-T Data Base related to the Collaboration on ITS Communication Standards. 5GAA noticed, since last correspondence (RP-201285), with the help of MCC, that two new documents related to V2X and CITS were identified: - TR 37.875 v0.6.0 Band combinations for Uu and V2X con-current operation - TR 23.700-64 Study on enhancements to application layer support for V2X services; Phase 2 5GAA understood that the internal TRs of 3GPP should not be populated into the ITU Data Base. Could 3GPP confirm if any of the two documents should be communicated to ITU for the CITS Data Base?. Action: 5GAA WG4 kindly ask TSG RAN, TSG SA to provide feedback on the proposal to send inputs to the ITU-T Data Base and also to advice if anything is missing.","secretary_remarks":"Response drafted in SP-220339. Final response in SP-220339_rev1 (To be revised)","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10370,"status":"replied to","reservation_date":"2022-03-09 08:28:28","uploaded":"2022-03-09 08:38:57","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG RAN, TSG SA","Cc":"TSG CT","lsoriginalls":"5GAA_S-220014","lsreply":"SP-220339","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220290.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220323","title":"LS from SA WG1: LS on Text Proposal for ITU-R draft Report ITU-R M.[IMT.INDUSTRY]","source":"SA WG1","contact":"Francesco Pica","contact-id":57089.0,"tdoctype":"LS in","for":"Action","abstract":"SA WG1 asks TSG SA to review the attached LS and Annex (Text Proposal), amend it as needed, and send it to ITU-R WP5D, with copy to SA WG1 and SA WG6.","secretary_remarks":"Contains draft LS OUT to ITU-R. Response to ITU-R WP5D in SP-220337. Attached LS was allocated to SP-220337. Noted","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10260,"status":"noted","reservation_date":"2022-03-10 10:03:03","uploaded":"2022-03-10 10:04:11","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"TSG SA","Cc":"","lsoriginalls":"S1-220182","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220323.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220334","title":"[DRAFT] Reply LS to GSMA OPG on Further Operator Platform Group questions following SDO Workshop","source":"TSG SA","contact":"Suresh Chitturi","contact-id":61003.0,"tdoctype":"LS out","for":"Approval","abstract":"To: . CC: . Attachments: .","secretary_remarks":"Response to SP-220022. CC#1: rev1 approved. Revised to SP-220346.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10290,"status":"revised","reservation_date":"2022-03-14 09:50:47","uploaded":"2022-03-14 09:57:12","revisionof":"","revisedto":"SP-220346","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"GSMA OPG, GSMA OPAG","Cc":"SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220334.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220337","title":"Reply LS to LS on Text Proposal for ITU-R draft Report ITU-R M.[IMT.INDUSTRY]","source":"TSG SA","contact":"Francesco Pica","contact-id":57089.0,"tdoctype":"LS out","for":"Approval","abstract":"To: PCG (to forward to ITU-R WP5D). CC: SA WG1, SA WG6, TSG RAN. Attachment: Annex_TP toward 5D draft report.docx","secretary_remarks":"Created at CC#1. Response to SP-220006. This should be sent to PCG for endorsement and forwarding to ITU-R","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10270,"status":"approved","reservation_date":"2022-03-16 07:35:57","uploaded":"2022-03-17 05:24:28","revisionof":"","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-220006","lsto":"PCG (to forward to ITU-R WP5D)","Cc":"SA WG1, SA WG6, TSG RAN","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220337.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220338","title":"LS on Alignment concerning 5G RG requirements and its remote management","source":"TSG SA","contact":"Kurt Bischinger","contact-id":26063.0,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF. CC: SA WG1, SA WG2","secretary_remarks":"Created at CC#1. Response to SP-220030. rev1 approved. Revised to SP-220347.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10350,"status":"revised","reservation_date":"2022-03-16 07:35:57","uploaded":"2022-03-16 07:36:38","revisionof":"","revisedto":"SP-220347","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIRates"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"BBF","Cc":"SA WG1, SA WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220338.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220339","title":"[DRAFT] Reply LS on provision of inputs to the online ITS communication standards database from ITU","source":"TSG SA","contact":"Johannes Achter","contact-id":5595.0,"tdoctype":"LS out","for":"Approval","abstract":"To: 5GAA WG4. CC: TSG RAN, SA WG6","secretary_remarks":"Created at CC#1. Response to SP-220290. rev1 was approved. Revised to SP-220348.","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10380,"status":"revised","reservation_date":"2022-03-16 07:35:57","uploaded":"2022-03-17 05:04:09","revisionof":"","revisedto":"SP-220348","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"","lsto":"5GAA WG4","Cc":"","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220339.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220346","title":"Reply LS to GSMA OPG on Further Operator Platform Group questions following SDO Workshop","source":"TSG SA","contact":"Suresh Chitturi","contact-id":61003.0,"tdoctype":"LS out","for":"Approval","abstract":"To: . CC: . Attachments: .","secretary_remarks":"Revision of SP-220334_rev1. This LS OUT was approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10300,"status":"approved","reservation_date":"2022-03-18 17:40:14","uploaded":"2022-03-18 17:41:11","revisionof":"SP-220334","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-220022","lsto":"GSMA OPG, GSMA OPAG","Cc":"SA WG2, SA WG5, SA WG6, ETSI ISG MEC, ETSI ISG NFV","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220346.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220347","title":"LS on Alignment concerning 5G RG requirements and its remote management","source":"TSG SA","contact":"Kurt Bischinger","contact-id":26063.0,"tdoctype":"LS out","for":"Approval","abstract":"To: BBF. CC: SA WG1, SA WG2","secretary_remarks":"Revision of SP-220338_rev1. This LS OUT was approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10360,"status":"approved","reservation_date":"2022-03-18 17:40:14","uploaded":"2022-03-18 17:41:11","revisionof":"SP-220338","revisedto":"","release":"Rel-18","crspec":"","crspecversion":"","workitem":[{"winame":"PIRates"}],"crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-220030","lsto":"BBF","Cc":"SA WG1, SA WG2","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220347.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0},
{"name":"SP-220348","title":"Reply LS on provision of inputs to the online ITS communication standards database from ITU","source":"TSG SA","contact":"Johannes Achter","contact-id":5595.0,"tdoctype":"LS out","for":"Approval","abstract":"To: 5GAA WG4. CC: TSG RAN, SA WG6","secretary_remarks":"Revision of SP-220339_rev1. This LS OUT was approved","agenda_item_sort_order":10,"ainumber":"2.2","ainame":"Incoming LSs which need an outgoing LS","tdoc_agenda_sort_order":10390,"status":"approved","reservation_date":"2022-03-18 17:40:14","uploaded":"2022-03-18 17:41:11","revisionof":"SP-220339","revisedto":"","release":"","crspec":"","crspecversion":"","workitem":"","crnumber":"","crrevision":"","crcategory":"","tsg_crp":"","lsreplyto":"SP-220290","lsto":"5GAA WG4","Cc":"TSG RAN, SA WG6","lsoriginalls":"","lsreply":"","link":"https:\/\/www.3gpp.org\/ftp\/tsg_sa\/TSG_SA\/TSGS_95E_Electronic_2022_03\/Docs\/SP-220348.zip","group":"SP","meeting":"SP-95-e","year":2022,"uicc_affected":null,"me_affected":null,"ran_affected":null,"cn_affected":null,"clauses_affected":null,"crsinpack":null,"crsinpacknumber":0}]