Difference between revisions of "MEC Ecosystem"

From MECwiki
Jump to: navigation, search
(MEC Solutions)
Line 20: Line 20:
 
|'''Unibo MEC API Tester'''[[File:Unibo mec api tester.png|center|frameless|200x200px]]
 
|'''Unibo MEC API Tester'''[[File:Unibo mec api tester.png|center|frameless|200x200px]]
 
|The Unibo MEC API Tester is a web-based application that can be used to test the capability of a MEC Platform to support the MEC 011 defined APIs (mec_app_support & mec_service_mgmt).
 
|The Unibo MEC API Tester is a web-based application that can be used to test the capability of a MEC Platform to support the MEC 011 defined APIs (mec_app_support & mec_service_mgmt).
|MEC 011 (Mp1) APIs
+
|MEC 011 (Mp1)
 
|NA
 
|NA
 
|[https://github.com/berdav/unibo-test-mec Link]
 
|[https://github.com/berdav/unibo-test-mec Link]
Line 41: Line 41:
 
|'''AdvantEdge''' [[File:advantedge.png|center|frameless|200x200px]]
 
|'''AdvantEdge''' [[File:advantedge.png|center|frameless|200x200px]]
 
|AdvantEDGE is a Mobile Edge Emulation Platform (MEEP) that runs on Docker & Kubernetes. AdvantEDGE provides an emulation environment, enabling experimentation with Edge Computing Technologies, Applications, and Services. The platform facilitates exploring edge / fog deployment models and their impact on applications and services in short and agile iterations.
 
|AdvantEDGE is a Mobile Edge Emulation Platform (MEEP) that runs on Docker & Kubernetes. AdvantEDGE provides an emulation environment, enabling experimentation with Edge Computing Technologies, Applications, and Services. The platform facilitates exploring edge / fog deployment models and their impact on applications and services in short and agile iterations.
|MEC 012 - Radio Network Information<br/>MEC 013 Location<br/>MEC 028 - WLAN Information  
+
|MEC Platform
| MEC Platform
+
| MEC 012 Radio Network Information<br />MEC 013 Location<br />MEC 028 WLAN Information
|[https://github.com/InterDigitalInc/AdvantEDGE Link]
+
|[https://github.com/InterDigitalInc/AdvantEDGE Link]
 
|[mailto:AdvantEDGE@InterDigital.com AdvantEDGE@InterDigital.com]  
 
|[mailto:AdvantEDGE@InterDigital.com AdvantEDGE@InterDigital.com]  
 
|-
 
|-
Line 49: Line 49:
 
|CVB provides a V2X focused MEC platform, which offers services to connected vehicles. These services are delivered to applications hosted on vehicles based on a set of policies for data dispatch and response. As the blueprint continues to be developed, further connected-vehicle applications and services are being incorporated into the blueprint.
 
|CVB provides a V2X focused MEC platform, which offers services to connected vehicles. These services are delivered to applications hosted on vehicles based on a set of policies for data dispatch and response. As the blueprint continues to be developed, further connected-vehicle applications and services are being incorporated into the blueprint.
 
|MEC Platform(s), MEC Platform Manager  
 
|MEC Platform(s), MEC Platform Manager  
|Mp1 & Mm5  
+
|MEC 011 Mp1 & Mm5  
 
|[https://wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]
 
|[https://wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]
 
|[mailto:yargyang@tencent.com Yarg Yang]  
 
|[mailto:yargyang@tencent.com Yarg Yang]  
Line 56: Line 56:
 
|Lightweight telco edge platform, enabling Enterprise applications on telco edge. Offering a: Unified Portal for platform management and for App developers; Sandbox with SDKs and tools chains for MEC app developers; Heterogeneous deployment on Multi-Arch; ETSI MEC Compliance.
 
|Lightweight telco edge platform, enabling Enterprise applications on telco edge. Offering a: Unified Portal for platform management and for App developers; Sandbox with SDKs and tools chains for MEC app developers; Heterogeneous deployment on Multi-Arch; ETSI MEC Compliance.
 
|MEC Platform(s), MEC Platform Manager
 
|MEC Platform(s), MEC Platform Manager
|Mp1 & Mm3
+
|MEC 011 Mp1 & Mm3
 
|[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]
 
|[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]
 
|[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]
 
|[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]
Line 63: Line 63:
 
|The purpose of Public Cloud Edge Interface (PCEI) Blueprint family is to specify a set of open APIs for enabling Multi-Domain Inter-working across  functional domains that provide Edge capabilities/applications and require close cooperation between the Mobile Edge, the Public Cloud Core and Edge, the 3rd-Party Edge functions as well as the underlying infrastructure such as Data Centers and Networks.
 
|The purpose of Public Cloud Edge Interface (PCEI) Blueprint family is to specify a set of open APIs for enabling Multi-Domain Inter-working across  functional domains that provide Edge capabilities/applications and require close cooperation between the Mobile Edge, the Public Cloud Core and Edge, the 3rd-Party Edge functions as well as the underlying infrastructure such as Data Centers and Networks.
 
|Provides an enabler layer that facilitates interworking between Edge Computing platforms, including Multi-Access Edge Compute, Public Cloud and 3rd-Party Edge Compute, and Mobile Networks
 
|Provides an enabler layer that facilitates interworking between Edge Computing platforms, including Multi-Access Edge Compute, Public Cloud and 3rd-Party Edge Compute, and Mobile Networks
|MEC Location API
+
|MEC 013 Location API
 
|[https://wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]
 
|[https://wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]
 
|[mailto:oberzin@equinix.com Oleg Berzin]
 
|[mailto:oberzin@equinix.com Oleg Berzin]
Line 70: Line 70:
 
|Decentralized framework for the distribution of lambda functions to multiple serverless platforms, with Apache OpenWhisk connectors, supporting the ETSI MEC Device application interface (MEC 016).
 
|Decentralized framework for the distribution of lambda functions to multiple serverless platforms, with Apache OpenWhisk connectors, supporting the ETSI MEC Device application interface (MEC 016).
 
|User app LCM proxy
 
|User app LCM proxy
|MEC Device application interface over Mx2
+
|MEC 016 Device application interface (Mx2)
 
|[https://github.com/ccicconetti/serverlessonedge Link]
 
|[https://github.com/ccicconetti/serverlessonedge Link]
 
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]
 
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]

Revision as of 14:44, 20 October 2020

This page provides information very much related to the work of the ETSI ISG MEC Deployment and ECOsystem DEvelopment (DECODE) Working Group, whose aim is to accelerate the development of the MEC ecosystem:

MEC Applications

List of MEC Applications made available by third parties

Name of the App & logo Description MEC Consumed APIs MEC API provided Link Contact
Unibo MEC API Tester
Unibo mec api tester.png
The Unibo MEC API Tester is a web-based application that can be used to test the capability of a MEC Platform to support the MEC 011 defined APIs (mec_app_support & mec_service_mgmt). MEC 011 (Mp1) NA Link Davide Berardi

MEC Solutions

List of MEC Solutions made available by third parties (in alphabetical order). Such solutions may offer all components (functional entities) of the MEC architecture, or a subset (for instance a MEC Platform, or API implementation).

Name of the project & logo Description MEC Components provided MEC APIs supported Link Contact
AdvantEdge
Advantedge.png
AdvantEDGE is a Mobile Edge Emulation Platform (MEEP) that runs on Docker & Kubernetes. AdvantEDGE provides an emulation environment, enabling experimentation with Edge Computing Technologies, Applications, and Services. The platform facilitates exploring edge / fog deployment models and their impact on applications and services in short and agile iterations. MEC Platform MEC 012 Radio Network Information
MEC 013 Location
MEC 028 WLAN Information
Link AdvantEDGE@InterDigital.com
Connected Vehicle Blueprint (Aka CVB)
Akraino.png
CVB provides a V2X focused MEC platform, which offers services to connected vehicles. These services are delivered to applications hosted on vehicles based on a set of policies for data dispatch and response. As the blueprint continues to be developed, further connected-vehicle applications and services are being incorporated into the blueprint. MEC Platform(s), MEC Platform Manager MEC 011 Mp1 & Mm5 Link Yarg Yang
Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)
Akraino.png
Lightweight telco edge platform, enabling Enterprise applications on telco edge. Offering a: Unified Portal for platform management and for App developers; Sandbox with SDKs and tools chains for MEC app developers; Heterogeneous deployment on Multi-Arch; ETSI MEC Compliance. MEC Platform(s), MEC Platform Manager MEC 011 Mp1 & Mm3 Link Gaurav Agrawal
Public Cloud Edge Interface (PCEI)
Akraino.png
The purpose of Public Cloud Edge Interface (PCEI) Blueprint family is to specify a set of open APIs for enabling Multi-Domain Inter-working across functional domains that provide Edge capabilities/applications and require close cooperation between the Mobile Edge, the Public Cloud Core and Edge, the 3rd-Party Edge functions as well as the underlying infrastructure such as Data Centers and Networks. Provides an enabler layer that facilitates interworking between Edge Computing platforms, including Multi-Access Edge Compute, Public Cloud and 3rd-Party Edge Compute, and Mobile Networks MEC 013 Location API Link Oleg Berzin
ServerlessOnEdge
Logo-small.png
Decentralized framework for the distribution of lambda functions to multiple serverless platforms, with Apache OpenWhisk connectors, supporting the ETSI MEC Device application interface (MEC 016). User app LCM proxy MEC 016 Device application interface (Mx2) Link Claudio Cicconetti

Request your project to be listed

A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please contact ETSI CTI, with title "ISG MEC WIKI Ecosystem request".
Any organization (ETSI member or not) is entitled to send the request.

The request should contain the information to be included in the table. "Contact" in the table is not mandatory, but a contact point is required to allow communication of changes or future developments on the page.

The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.

Criteria for the inclusion into the Ecosystem page are:

  • The referenced activity is relevant to ETSI MEC i.e. it claims to implement at least one MEC Component from the MEC Architecture as defined in ETSI GS MEC 003.
  • The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.