MEC Ecosystem: Difference between revisions

From MECwiki
Jump to: navigation, search
(Created page with "Covering Testing, Forge, MEC Sandbox and Links to relevant external projects Forge Projects: Includes OpenAPI/Swagger & Protobuf descriptions OpenAPI development guidelines...")
 
(Updates according to MEC(20)000151 (was MECDECODE(20)000005))
Line 1: Line 1:
Covering Testing, Forge, MEC Sandbox and Links to relevant external projects
This page provides information very much related to the work of the ETSI ISG MEC Deployment and ECOsystem DEvelopment ([https://portal.etsi.org//tb.aspx?tbid=874&SubTB=874#/ DECODE]) Working Group, whose aim is to accelerate the development of the MEC ecosystem:
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?
*'''MEC Sandbox''': MEC Service API playground (in development)
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios
*'''[[MEC Applications]]''': 3rd party solutions
*'''[[MEC Solutions]]''': 3rd party solutions


Forge Projects: Includes OpenAPI/Swagger & Protobuf descriptions
=== MEC Applications ===
OpenAPI development guidelines
List of MEC Applications made available by third parties
MEC Sandbox: MEC Service API playground (in development)
{| class="wikitable"
MEC Sandbox Scenarios (EOL account required): Macro/micro network emulation scenarios
|+
MEC Applications: 3rd party solutions
!Name of the App & logo
MEC Solutions: 3rd party solutions
!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 [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/02.01.01_60/gs_MEC003v020101p.pdf MEC architecture], or a subset (for instance a MEC Platform, or API implementation).
{| class="wikitable"
|+
!Name of the project & logo
!Description
!MEC Components provided
!MEC APIs supported
!Link
!Contact
|-
|
|
|
|
|
|
|-
|
|
|
|
|
|
|-
|
|
|
|
|
|
|}
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to cti_support@etsi.org,.with title "MEC Ecosystem request" <u>'''Any'''</u> 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 [https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/02.01.01_60/gs_MEC003v020101p.pdf 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.

Revision as of 11:12, 22 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

A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to cti_support@etsi.org,.with title "MEC 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.