Multi-Access Edge Computing (MEC): Architecture, Flow, Interfaces, and Protocols

Multi-access Edge Computing (MEC) is a key enabler in 5G networks, bringing computation and storage resources closer to the end user. By deploying cloud-like capabilities at the network edge (e.g., base stations, aggregation sites), MEC minimizes latency, optimizes traffic routing, and supports innovative services such as AR/VR, connected cars, and IoT applications.

1. MEC Standard Architecture

The ETSI MEC framework defines the standard reference architecture:

• MEC Host: Provides compute, storage, and networking resources at the edge. It runs virtualized MEC applications and has a MEC Platform for service exposure, traffic rules, and APIs.

• MEC Platform: Middleware layer responsible for service discovery, application lifecycle management, and policy enforcement.

• MEC Applications: Edge services (e.g., video caching, AR rendering, gaming engines) that run inside the MEC host.

• OSS/BSS & Orchestrator: Centralized functions that handle MEC app onboarding, policy control, and lifecycle management, often integrated with NFV MANO.

• User Equipment (UE): Devices that consume MEC services with ultra-low latency.

2. MEC Data Flow (Simplified)

1. UE connects via RAN (gNB in 5G or eNB in 4G).

2. Traffic classification happens at the Uplink Classifier (UL-CL) or Local Breakout (LBO) function.

3. Packets are steered locally to the MEC application instead of going through the full core network.

4. MEC application processes data, may respond directly, or forward selective traffic back to the 5GC/Internet.

5. Results are delivered to the UE with significantly reduced latency.

3. MEC Interfaces

• Mp1: Between MEC platform and MEC applications, using RESTful APIs.

• Mm1: Between MEC orchestrator and MEC platform for management.

• Service Exposure APIs: Location, bandwidth management, radio network information, etc.

• N6 / SGi interface: Connects MEC platform to the 5GC (UPF) or EPC (PGW) for data-plane integration.

4. MEC Protocols

• HTTP/REST APIs: For service discovery, application lifecycle, and service exposure.

• DNS/HTTP redirection: To steer UE traffic to MEC applications.

• GTP-U: Data plane tunneling between RAN, UPF, and MEC host.

• NFV/Orchestration protocols: e.g., ETSI MANO, often leveraging OpenStack or Kubernetes for resource allocation.

• Container/VM protocols: Docker/K8s for MEC app lifecycle management.

5. Added Value of MEC

• Ultra-Low Latency: Critical for autonomous driving, AR/VR, and industrial IoT.

• Efficient Backhaul Usage: Local breakout prevents flooding the core and transport with unnecessary traffic.

• Context-Aware Services: APIs expose RAN/user context for optimized applications.

• Scalability & Flexibility: Supports both VM-based and containerized deployments, fitting well with 5G’s service-based architecture (SBA).

✅ In short: MEC acts as a bridge between cloud and telecom, enabling operators to push intelligence closer to the edge. Its standardized architecture (ETSI MEC) defines how applications, platforms, interfaces, and protocols interact to unlock new 5G use cases.