5.1 Deploying oneM2M with ETSI MEC
Introduction of 4 deployment options which basic architectur
The services in this clause are fundamentally based on an edge computing compliant deployment, where oneM2M and ETSI MEC platforms are central to the architecture. Such an integration can consider several deployment options, each presenting distinct technical and business implications. In June 2023, oneM2M and ETSI MEC collaboratively developed a white paper titled "Enabling Multi-access Edge Computing in Internet-of-Things: how to deploy ETSI MEC and oneM2M." [i.15] This white paper proposes four distinct deployment options for how oneM2M and MEC can be integrated and operated.
5.1.1 Option A
oneM2M CSE is deployed in a cloud platform and MEC in an Edge platform. This deployment scenario positions the IoT platform itself primarily on the cloud side, with MEC functioning at the edge. It represents one of the most common deployment configurations for cloud-based IoT platforms integrating with edge computing. While it allows for some benefits of edge computing through localized network and processing, it doesn't fully leverage the advantages of a 100% edge computing environment, as the cloud remains the ultimate endpoint for data storage and management.
architecture may require an IPE to convert from MEC api to oneM2M primitives
5.1.2 Option B
oneM2M CSE and MEC as Edge Nodes hosted on different physical Nodes. In this option, both oneM2M and MEC are deployed as edge nodes, but they reside on physically separate edge hardware. Compared to Option A, this setup allows for all data and information exchange between oneM2M and MEC to be performed locally at the edge, resulting in faster processing. Despite oneM2M IoT service providers and ETSI MEC entities potentially being distinct, this scenario is viable, particularly in the nascent stages of the edge computing market.
5.1.3 Option C
oneM2M and MEC are deployed on the same physical Edge Node. This scenario involves the oneM2M and MEC platforms being installed and operated on the very same physical edge node. This co-location can significantly enhance service performance by eliminating unnecessary data and information exchange between separate nodes. Implementing this option typically necessitates a Service Level Agreement (SLA) between the respective platform providers, and both platforms must support dynamic deployment capabilities across various edge nodes.
5.1.4 Option D
oneM2M and ETSI MEC are tightly coupled within the same edge node. This represents the deepest level of integration, where oneM2M and MEC platforms are physically coupled, often through direct API-level interworking. In this setup, the oneM2M platform can be recognized and function as an MEC application, fully leveraging all services and functions provided by the MEC environment to deliver a truly 100% edge computing solution. Conversely, the MEC platform can directly offer data source, processing, and multi-access networking capabilities by hosting oneM2M as an integrated application. Achieving this level of tight coupling necessitates the development of standard documents defining clear interoperability and interworking specifications between the oneM2M and ETSI MEC platforms.
