Difference between revisions of "MEC Ecosystem"

From MECwiki
Jump to: navigation, search
Line 56: Line 56:
|MEC Device application interface over Mx2
|MEC Device application interface over Mx2
|[https://github.com/ccicconetti/serverlessonedge Link]
|[https://github.com/ccicconetti/serverlessonedge Link]
|Claudio Cicconetti [[Mailto:c.cicconetti@iit.cnr.it|c.cicconetti@iit.cnr.it]]
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]

Revision as of 16:10, 29 May 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

MEC Solutions

List of MEC Solutions made available by third parties. 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
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 Device application interface over Mx2 Link Claudio Cicconetti

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.