This may take a few seconds...
You will automatically be redirected to the sandbox page when ready.
Sign in
Configure MEC Sandbox
Experiment with MEC APIs
Observe MEC API behavior
If you need more help using the platform
Are you sure you want to delete the selected MEC Application instance?
Create a unique Application Instance Id in the MEC Sandbox.
Every instance of the same MEC Application should consistently have
the same MEC Application Name across MEC platforms.
v1.10 • 2023-02-22
AdvantEDGE baseline upgrade to v1.10.0
STF678 Final:v1.9 • 2023-02-22
AdvantEDGE baseline upgrade to v1.9.0
STF625 Final:v1.8 • 2022-09-29
STF625 update 2:v1.7 • 2022-06-20
STF625 update:v1.6 • 2021-12-16
Final STF599 update:v1.5.3 (beta) • 2021-11-22
Maintenance Release:v1.5.2 (beta) • 2021-11-08
MEC028 WebSockets:v1.5.1 (beta) • 2021-10-30
MEC API Maintenance:v1.5 (beta) • 2021-09-30
New MEC APIs:v1.4.1 • 2021-08-06
MEC Service Maintenance:v1.4 (beta) • 2021-07-20
MEC Service Enhancements:v1.3 • 2021-06-03
Long-term Sandbox Analytics Storage:v1.2 • 2021-05-11
MEC Sandbox VM Upgrade:v1.1 • 2021-03-23
Monitoring & Analytics:MEC Sandbox is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardised RESTful APIs are targeted towards MEC application developers to expose the value added services offered by MEC, including real time access to network and context information, as well as location awareness. The design principles for developing the APIs have also been specified in ETSI GS MEC 009, along with http methods, templates, conventions and patterns. The MEC service APIs are available in YAML and JSON format at https://forge.etsi.org, presented via OpenAPI compliant descriptions.
MEC Sandbox provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi, MEC Federation) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behaviour and capabilities of the Location (MEC013), Radio Network Information (MEC012), Traffic Management APIs (MEC015), Device application interface (MEC016), Application Mobility (MEC021), WLAN Information (MEC028) and V2X Information API (MEC030) service API and MEC Federation Service API (MEC040) service APIs. MEC Sandbox provides also a support for Edge Native Connector (3GPP TS 29.222: 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Common API Framework for 3GPP Northbound APIs).
Such contextual information can offer significant differential performance for edge based MEC applications. MEC Sandbox also provides the support of capabilities described by Edge Platform Application Enablement (MEC011) and Device Application Interface (MEC016).
Important Note: If MEC Federation Service API (MEC040) is used (e.g. by activation 4g-5g-wifi-macro-v2x-fed network scenarion), MEC services and MEC applications will be visible from other MEC Platform using also MEC Federation Service API (MEC040). If you choose to use MEC Federation Service API (MEC040), you accept to establish MEC federation between two partners as specified in ETSI GS MEC 040 V3.2.1 (2024-03) Clause 5.2.4.1 Introduction.
Users can use the MEC Sandbox API to develop their own MEC applications to access and use the live MEC APIs running an instance of the MEC Sandbox. The demo6 example illustrates how to use the MEC Sandbox API.
But wait - MEC Sandbox is not only a browser experience!
Users with existing applications can configure them to access and use the live MEC APIs running in their own test environment.
Interested to learn more?
Follow the help menu links (Webinar, Wiki, Community, etc.) to get started or simply sign-in and try-it!
The following resources provide more information on ETSI MEC:
- Multi-access Edge Computing
- ETSI MEC Portal
- ETSI Forge
- ETSI MEC Slide Deck