ETSI releases new edge-computing specifications

The European Telecommunications Standards Institute (ETSI) has announced a new set of Multi-access Edge Computing (MEC) specifications and a technical white paper as part of its Phase 4 work programme, aiming to strengthen alignment between formal standards and open-source edge-cloud initiatives.

The release, developed in collaboration with the Linux Foundation’s CAMARA project and TM Forum, seeks to make it easier for application developers to work across different network environments by harmonising API frameworks and offering guidance on universal API access.

Bridging standards and open-source projects

The white paper outlines how ETSI MEC service APIs complement open-source implementations such as CAMARA APIs. It focuses on common terminology, interoperability, and best practices for exposing network capabilities to developers. ETSI says the work supports consistent approaches across 3GPP, CAMARA and GSMA efforts, a priority as operators prepare for more edge-native services in 5G and future networks.

Among the tools highlighted is the ‘Edge Native Connector,’ an evolution of the MEC Sandbox, intended to help developers test and build applications that operate across heterogeneous networks and edge platforms.

Specifications targeting developer usability

ETSI’s latest deliverables include:

• ETSI GR MEC 043 – proposing simplified, abstracted APIs to expose network information to industry verticals without requiring deep telecom-network expertise
• ETSI GS MEC 011 – updates to the MEC application-enablement framework
• MEC architecture enhancements through ETSI GS MEC 003
• research into distributed edge computing via ETSI GR MEC 047
• expanded focus on IoT and device-edge scenarios under ETSI GR MEC 036

The group says the updates are designed to help developers access network intelligence more easily while supporting interoperability across different edge environments.

Next step: developer tools and federation testing

The release includes enhancements to the MEC Sandbox (now at version 1.10), adding support for 3GPP CAPIF and early EDGEAPP-related features such as service provisioning and app discovery. Work planned for 2026 includes expanded radio-network emulation and improved federation capabilities, alongside collaboration with ETSI’s Open CAPIF and operator-platform initiatives.

Developer focus and future priorities

ETSI MEC Chair Dario Sabella said the latest work is meant to help developers navigate standards-based and open-source APIs. He noted continued focus on data exposure, security, privacy and regulatory considerations as edge services mature.

Walter Featherstone, who chairs the group’s DECODE working group, described the transition from MEC Sandbox to the Edge Native Connector as a key step toward enabling cross-network developer testing environments.

Why does it matter?

With more specifications and support material expected as Phase 4 progresses, ETSI positions the work as part of a broader effort to standardise edge computing while ensuring compatibility with software-driven development ecosystems.