Alignment of EDGEAPP and ETSI MEC for Edge Computing Standards
At a recent joint workshop, 3GPP and ETSI MEC discussed aligning standards to prevent duplication of work and enable interoperability. The collaboration aims to harmonize API definitions, reuse existing specifications, and prioritize normative work for seamless integration. The ultimate goal is to support edge platforms that are compliant with both 3GPP and ETSI MEC, fostering adoption of edge computing technologies.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
3GPP Alignment of EDGEAPP and ETSI MEC - EDGEAPP external TR Presented by: Samar Shailendra (Intel) Supporters: Nokia, SK Telecom, Qualcomm
Motivation of EDGEAPP and ETSI MEC alignment At the Joint Workshop with OPG (21/01/2022), 3GPP and ETSI MEC have presented their feedback on the SDO mapping. Also, ETSI MEC has presented its approach on the joint work. This approach is composed of 3 steps: We need to acknowledge ETSI MEC on the usage of the synergized arch., as a common place for defining the SDO mapping Step#1 - Based on the API list and OP definitions, define a more detailed mapping and worksplit between ETSI MEC and 3GPP, by using as a starting point the synergized architecture (from the TS 23.558 here), and build on top of that Step#2 For the normative work (stage 2 sequence diagrams) reuse existing specs from 3GPP and ETSI MEC We need to work together with ETSI MEC. An example of proposed packaging approach could help a common understanding, also from OPG Step#3 - Prioritize the normative work in SDOs to fill the remaining gaps (for compliance to OP interfaces) We need also to communicate with ETSI MEC on the worksplit and coordination of the future normative work. A suitable tool for that would be an external TR in 3GPP that could capture this coordination work (we need formal documents in 3GPP!) 2
Scope of the ETSI/3GPP alignment on Edge computing General goal on aligning these standards, as asked by the industry, is to avoid duplication of work (or land to conflicting/diverging standards that would lead to market fragmentation), and to openly enable edge platforms and products that can be 1) compliant with 3GPP 2) ETSI MEC 3) both. In particular, the third option (although not mandatory) can provide added value to the edge ecosystem, decrease implementation and deployment costs, and encourage adoption of edge computing. Edge computing Notes: Standards In 5G, alignment of the 2 standards is the key. Open Source General consensus to align ETSI and 3GPP in order to avoid duplication of work. MEC in 5G ETSI MEC Anyway, alignment doesn t mean equivalence 3GPP (Note: ETSI MEC is Multi-access Edge Computing, thus including also Wi-Fi, fixed access, etc..) 3
Proposed Collaboration between 3GPP and ETSI MEC Main idea is to coordinate the future normative work, and also to faciliate the technical understanding on how this approach can show complementarity of SDOs specs. Delegates from two SDOs can be then encouraged to work to avoid duplication efforts, and they can see also the specs in the other body as a tool to promote their own assets towards the bigger edge community. For example, ETSI MEC (and the MEC 040 hosting the NBI and EWBI standards) can be an asset to underline the 3GPP technical enablers of the OP APIs. Specific topics for alignment can be the following: Topic 1: study and better define the synergy between Mp1 and EDGE-3, as they are both relevant for NBI. Similarly, a clarification on the relationship between Mx1 and Provisioning Mns is needed (with SA5 !). Mp1 and EDGE-3 communicate with ETSI MEC ISG and subsequent normative work at ETSI MEC ISG Topic 2: It is convenient that ETSI MEC hosts NBI standard (e.g. in MEC 040), subject to feedback from 3GPP, GSMA OPG and other SDOs. Clarify with ETSI MEC the synergies also in this perspective. Mx1 is the identified reference point for OP-NBI, leveraging Provisioning Mns SA6 can provide feedback; ETSI MEC can communicate with SA5 and subsequent normative work in Rel.18 Topic 3: Converged architecture for Federation. In fact, still TS 23.558 doesn t capture the latest advancements, that need to be inserted in the next Rel.18 version. BTW, these need proper motivation by means of a suitable Study in 3GPP. SA6 may adopt a top-down approach identify the converged architecture and align with ETSI MEC. 4
Ongoing alignment effort in SA6 Approved Contributions: KI#5: Alignment of EDGEAPP and ETSI MEC Sol#11: A deployment option for alignment with ETSI MEC using CAPIF Annex B.2: Deployment options Postponed Contributions S6-212738: Dual Application Registration S6-220302: Updates in EAS Profile for accessing EES/EAS APIs from MEC App Instance 5
Proposal The previous slides clarified the motivation for an external TR in 3GPP. Possible Approaches SA6 to agree for external TR as part of eEDGEAPP study A collaborative external TR jointly from SA6/SA5/SA2, SA6 can lead the effort ! 6
