Edge computing is a new fashion of distributed computing bringing computation closer to data e.g., sensors and actuators. The consortium of ETSI is driving the standardization in the community of ICT. With Multi access Edge Computing (short MEC) the context, use case independent, becomes standardized via multiple specifications. also compare this talk http://wowmom2021.iit.cnr.it/include/panel-dario.pdf
Logical specification
- MEC 001: Terminology
- MEC 002: Use Cases and Requirements
- MEC 003: Reference Architecture, here
- MEC 009: General principals for MEC Service APIs, here
Platform specification
- MEC 010: MEC Application LifeCycle Management
- MEC 011: Edge Platform Application Environment
- MEC 012: Radio Network Information API
- MEC 013: Location API
API for specific services
- MEC 021: App Mobility Service API
- MEC 028: WLAN API
- MEC 029: Fixed Access API
- MEC 030: V2X API
- MEC 033: IoT API
e.g., the V2X API specifies additional pillar require for vehicle 2 everything (or vise-versa).
Technical specification (phase 3, not yet exist)
- MEC 036: Constrained Devices
- MEC 037: Application Package Format
- MEC 038: MEC in Park enterprises
- MEC 040: Federation enablement APIs
- MEC 041: MEC security
- MEC 043: Abstracted Radio Network Information for Industries
When we compare it, it falls in the same lots as cloud native approaches or todays software defined architectures:
- Edge Orchestrator = maybe e.g., Kubernetes
- Platform Manager = maybe e.g., Docker
- Virtual Infrastructure = maybe e.g., the respective Linux primitives
- Application = maybe e.g., ROS2 nodes
- Services = maybe e.e.g, ROS2 topics and services