MEC Sandbox Help - Revision history

Garciay at 07:38, 6 May 2026

2026-05-06T07:38:17Z

Garciay: Editorial changes

2024-11-19T08:13:43Z

Editorial changes

← Older revision		Revision as of 09:13, 19 November 2024
Line 2:		Line 2:
	MEC Sandbox is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardized 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 is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardized 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) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behavior and capabilities of the Location (MEC013), Radio Network Information (MEC012), WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs, 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).		MEC Sandbox provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behavior and capabilities of the Location (MEC013), Radio Network Information (MEC012), WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs, WLAN Information (MEC028) and V2X Information API (MEC030) service API and MEC Federation Service API (MEC040). 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).		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).

Garciay: Add MEC011/CAPIF and review versionning

2024-11-18T13:26:34Z

Add MEC011/CAPIF and review versionning

Garciay: Add MEC040 service description

2024-11-18T13:14:52Z

Add MEC040 service description

← Older revision		Revision as of 14:14, 18 November 2024
Line 252:		Line 252:
	* Gathering of PC5 V2X relevant information from the 3GPP network.		* Gathering of PC5 V2X relevant information from the 3GPP network.
	MEC Sandbox supports a subset of the VIS API endpoints. For more details on the supported endpoints access the SwaggerUI client in a MEC Sandbox.		MEC Sandbox supports a subset of the VIS API endpoints. For more details on the supported endpoints access the SwaggerUI client in a MEC Sandbox.

			==== MEC040 - V2X Information Service ====
			MEC Sandbox supports version v3.2.1 of the MEC040 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/030/02.02.01_60/gs_mec030v020201p.pdf ETSI website]

			Federation enablement APIs enable the shared usage of MEC services and applications across different systems (e.g. MEC system, Cloud system), such as:
			* MEC System discovery.
			* MEC service discovery.
			* MEC application instance discovery.
			For more details on the supported endpoints access the SwaggerUI client in a MEC Sandbox.

	= Usage =		= Usage =

Garciay: Add network scenario with MEC Federation

2024-11-18T13:09:28Z

Add network scenario with MEC Federation

← Older revision		Revision as of 14:09, 18 November 2024
Line 137:		Line 137:

	<br>		<br>
			==== 4G-5G Macro V2X Network (single MEP) with Federation ====
			* Similar to 4G-5G-WiFi Macro V2X Network but adds MEC Federation support
			* Network has a centrally located MEP

	==== 4G-5G-WiFi Macro Network (dual MEP) ====		==== 4G-5G-WiFi Macro Network (dual MEP) ====
	* Baselined on the 4G-5G-WiFi Macro Network		* Baselined on the 4G-5G-WiFi Macro Network

Garciay: Update feature of experimental MEC Sandbox

2024-11-18T09:52:21Z

Update feature of experimental MEC Sandbox

← Older revision		Revision as of 10:52, 18 November 2024
Line 2:		Line 2:
	MEC Sandbox is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardized 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 is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardized 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) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behavior and capabilities of the Location (MEC013), Radio Network Information (MEC012), WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs, 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 provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behavior and capabilities of the Location (MEC013), Radio Network Information (MEC012), WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs, 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).

	<b>Important Note:</b> 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.		<b>Important Note:</b> 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.

Garciay at 09:51, 18 November 2024

2024-11-18T09:51:42Z

← Older revision		Revision as of 10:51, 18 November 2024
Line 2:		Line 2:
	MEC Sandbox is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardized 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 is an interactive environment that enables users to learn & experiment with ETSI MEC Service APIs. These standardized 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) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behavior and capabilities of the Location (MEC013), Radio Network Information (MEC012), WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs. Such contextual information can offer significant differential performance for edge based MEC applications.		MEC Sandbox provides the user with a choice of scenarios combining different network technologies (4G, 5G, Wi-Fi) and terminal types. Combining these assets in a geolocated environment, a user can gain hands-on experience on the behavior and capabilities of the Location (MEC013), Radio Network Information (MEC012), WLAN Information (MEC028), Edge Platform Application Enablement (MEC011) and Application Mobility (MEC021) service APIs, 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.

			<b>Important Note:</b> 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.

	== MEC Sandbox Concepts & Usage ==		== MEC Sandbox Concepts & Usage ==

Velez at 15:25, 30 June 2022

2022-06-30T15:25:16Z

← Older revision		Revision as of 16:25, 30 June 2022
Line 130:		Line 130:
	* Network has a centrally located MEP		* Network has a centrally located MEP

	[[File:~~Network~~-4g-5g-~~wifi~~.~~png~~\|border\|500px]]		[[File:4G-5G-Macro-V2X-Network-Topology.PNG\|border\|500px]]

	<br>		<br>

Velez at 15:23, 30 June 2022

2022-06-30T15:23:05Z

← Older revision		Revision as of 16:23, 30 June 2022
Line 122:		Line 122:
	* Builds on 4G-WiFi Macro Network by adding 19 small cell 5G-PoAs distributed throughout the city		* Builds on 4G-WiFi Macro Network by adding 19 small cell 5G-PoAs distributed throughout the city
	* Network has a centrally located MEP (same as 4G Scenario)		* Network has a centrally located MEP (same as 4G Scenario)

			[[File:Network-4g-5g-wifi.png\|border\|500px]]

			<br>
			==== 4G-5G Macro V2X Network (single MEP) ====
			* Similar to 4G-5G-WiFi Macro Network but adds V2X service
			* Network has a centrally located MEP

	[[File:Network-4g-5g-wifi.png\|border\|500px]]		[[File:Network-4g-5g-wifi.png\|border\|500px]]

Velez at 09:08, 30 June 2022

2022-06-30T09:08:01Z

← Older revision		Revision as of 14:26, 18 November 2024
Line 182:		Line 182:
	<br>		<br>
	==== MEC011 - Edge Platform Application Enablement (Mp1) ====		==== MEC011 - Edge Platform Application Enablement (Mp1) ====
	MEC Sandbox supports version v2.2.1 of the MEC011 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.02.01_60/gs_MEC011v020201p.pdf ETSI website]		MEC Sandbox supports version v3.2.1 of the MEC011 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.02.01_60/gs_MEC011v020201p.pdf ETSI website]

	Mp1 reference point provides two different APIs: MEC Application Support and MEC Service Management		Mp1 reference point provides two different APIs: MEC Application Support and MEC Service Management
Line 191:		Line 191:
	* Event notifications about service and application availability		* Event notifications about service and application availability
	* Traffic rules, DNS rules and time of day		* Traffic rules, DNS rules and time of day
			* MEC Profile for CAPIF: MEC Sandbox provides 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)
	MEC Sandbox supports a subset of Mp1 API endpoints and subscription types; for more details on the supported endpoints access the SwaggerUI client in a MEC Sandbox.		MEC Sandbox supports a subset of Mp1 API endpoints and subscription types; for more details on the supported endpoints access the SwaggerUI client in a MEC Sandbox.

Line 206:		Line 207:
	<br>		<br>
	==== MEC013 - Location Service ====		==== MEC013 - Location Service ====
	MEC Sandbox supports version v2.2.1 of the MEC013 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/013/02.02.01_60/gs_mec013v020201p.pdf ETSI website]		MEC Sandbox supports version v3.1.1 of the MEC013 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/013/02.02.01_60/gs_mec013v020201p.pdf ETSI website]

	Location Service provides geospatial and network location information to edge applications, such as:		Location Service provides geospatial and network location information to edge applications, such as:
Line 235:		Line 236:
	<br>		<br>
	==== MEC028 - WLAN Access Information Service (WAIS) ====		==== MEC028 - WLAN Access Information Service (WAIS) ====
	MEC Sandbox supports version v2.2.1 of the MEC028 specifications, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/028/02.02.01_60/gs_mec028v020201p.pdf ETSI website]		MEC Sandbox supports version v2.3.1 of the MEC028 specifications, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/028/02.02.01_60/gs_mec028v020201p.pdf ETSI website]

	WAIS provides WLAN radio network information to edge applications, such as:		WAIS provides WLAN radio network information to edge applications, such as:
Line 245:		Line 246:
	<br>		<br>
	==== MEC030 - V2X Information Service ====		==== MEC030 - V2X Information Service ====
	MEC Sandbox supports version v2.2.1 of the MEC030 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/030/02.02.01_60/gs_mec030v020201p.pdf ETSI website]		MEC Sandbox supports version v3.2.1 of the MEC030 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/030/02.02.01_60/gs_mec030v020201p.pdf ETSI website]

	V2X Information Service provides V2X related information to the edge applications in a multi-vendor, multi-network and multi-access environment, such as:		V2X Information Service provides V2X related information to the edge applications in a multi-vendor, multi-network and multi-access environment, such as:

← Older revision		Revision as of 10:08, 30 June 2022
Line 167:		Line 167:
	<br>		<br>
	==== MEC011 - Edge Platform Application Enablement (Mp1) ====		==== MEC011 - Edge Platform Application Enablement (Mp1) ====
	MEC Sandbox supports version v2.1.1 of the MEC011 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.01.01_60/~~gs_MEC011v020101p~~.pdf ETSI website]		MEC Sandbox supports version v2.2.1 of the MEC011 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.02.01_60/gs_MEC011v020201p.pdf ETSI website]

	Mp1 reference point provides two different APIs: MEC Application Support and MEC Service Management		Mp1 reference point provides two different APIs: MEC Application Support and MEC Service Management
Line 180:		Line 180:
	<br>		<br>
	==== MEC012 - Radio Network Information Service (RNIS) ====		==== MEC012 - Radio Network Information Service (RNIS) ====
	MEC Sandbox supports version v2.1.1 of the MEC012 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/012/02.01.01_60/~~gs_mec012v020101p~~.pdf ETSI website]		MEC Sandbox supports version v2.2.1 of the MEC012 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/012/02.02.01_60/gs_MEC012v020201p.pdf ETSI website]

	RNIS provides cellular radio network information to edge applications, such as:		RNIS provides cellular radio network information to edge applications, such as:
Line 191:		Line 191:
	<br>		<br>
	==== MEC013 - Location Service ====		==== MEC013 - Location Service ====
	MEC Sandbox supports version v2.1.1 of the MEC013 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/013/02.01.01_60/~~gs_mec013v020101p~~.pdf ETSI website]		MEC Sandbox supports version v2.2.1 of the MEC013 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/013/02.02.01_60/gs_mec013v020201p.pdf ETSI website]

	Location Service provides geospatial and network location information to edge applications, such as:		Location Service provides geospatial and network location information to edge applications, such as:
Line 200:		Line 200:
	<br>		<br>
	==== MEC021 - Application Mobility Service (AMS) ====		==== MEC021 - Application Mobility Service (AMS) ====
	MEC Sandbox supports version v2.1.1 of the MEC021 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/02.01.01_60/~~gs_mec021v020101p~~.pdf ETSI website]		MEC Sandbox supports version v2.2.1 of the MEC021 specification, available on [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/021/02.02.01_60/gs_mec021v020201p.pdf ETSI website]

	Application Mobility Service provides support for relocation of user context and/or application instance between MEC hosts.		Application Mobility Service provides support for relocation of user context and/or application instance between MEC hosts.