https://mecwiki.etsi.org/api.php?action=feedcontributions&user=Featherston&feedformat=atomMECwiki - User contributions [en]2024-03-28T11:47:56ZUser contributionsMediaWiki 1.39.3https://mecwiki.etsi.org/index.php?title=MEC_Tech_Series&diff=3527MEC Tech Series2022-02-01T14:48:29Z<p>Featherston: </p>
<hr />
<div>__TOC__<br />
<br />
<br><br />
{| <br />
|[[File:Youtube-subscribe-button-6030373 1280.png|100px|left|top|link=https://www.youtube.com/playlist?list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h]] <br />
<br />
These videos are also available in the '''MEC Tech Series''' playlist on ETSI YouTube channel. <br />
<br />
Why not share your insights by volunteering to produce a MEC Tech Series episode on a topic of your choice. Please email [mailto:CTI_support@etsi.org?Subject=ISG_MEC_TECH_SERIES_enquiry ETSI CTI] for more information. <br />
|}<br />
<br><br />
<br />
== Episode 0 - Chair's Teaser ==<br />
by Dario Sabella (Intel)<br />
{{#evu:https://www.youtube.com/watch?v=wunoMBersKQ&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep0_-_Chair%27s_Teaser.pdf MEC-TECH-SERIES_ep0 - Chair's Teaser]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_0_-_Chairs_Teaser.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 1 - MEC OpenAPIs ==<br />
by Walter Featherstone (Samsung R&D Institute UK)<br />
{{#evu:https://www.youtube.com/watch?v=s-QPZ6jsqWo&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=2<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep1_-_MEC_OpenAPIs.pdf MEC-TECH-SERIES_ep1 - MEC OpenAPIs]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_1_-_MEC_OpenAPIs.mp3 audio]<br />
<br />
<br><br />
<br><br />
<br />
== Episode 2 - Overview of MEC Federation == <br />
by Dario Sabella (Intel)<br />
{{#evu:https://www.youtube.com/watch?v=LuLs0fknW70&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=3<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep2_-_Overview_of_MEC_Federation.pdf MEC-TECH-SERIES_ep2 - Overview of MEC Federation]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_2_-_Overview_of_MEC_Federation.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 3 - Edge enablement APIs == <br />
by Alice Li (Huawei Technology UK)<br />
{{#evu:https://www.youtube.com/watch?v=t8NTOCKcUhs&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=4<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep3_-_Edge_enablement_APIs.pdf MEC-TECH-SERIES_ep3 - Edge enablement APIs]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_3_-_Edge_enablement_APIs.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 4 - MEC Sandbox == <br />
by Robert Gadza (InterDigital)<br />
{{#evu:https://www.youtube.com/watch?v=IMDN4VSIgLU&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=5<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [https://mecwiki.etsi.org/images/MEC-TECH-SERIES_ep4_-_MEC_Sandbox.pdf MEC-TECH-SERIES ep4 - MEC Sandbox]<br />
<br />
The Podcast mp3 version is available here: [https://mecwiki.etsi.org/images/Episode_4_-_MEC_Sandbox.mp3 audio]<br />
<br />
<br />
<br><br />
<br></div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Tech_Series&diff=3526MEC Tech Series2022-02-01T14:44:33Z<p>Featherston: </p>
<hr />
<div>__TOC__<br />
<br />
<br><br />
{| <br />
|[[File:Youtube-subscribe-button-6030373 1280.png|100px|left|top|link=https://www.youtube.com/playlist?list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h]] <br />
<br />
These videos are also available in the '''MEC Tech Series''' playlist on ETSI YouTube channel. <br />
<br />
Why not share your insights by volunteering to produce a MEC Tech Series episode on a topic of your choice. Please email [[Mailto:CTI support@etsi.org?Subject=ISG MEC WIKI request|ETSI CTI]] for more information. <br />
|}<br />
<br><br />
<br />
== Episode 0 - Chair's Teaser ==<br />
by Dario Sabella (Intel)<br />
{{#evu:https://www.youtube.com/watch?v=wunoMBersKQ&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep0_-_Chair%27s_Teaser.pdf MEC-TECH-SERIES_ep0 - Chair's Teaser]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_0_-_Chairs_Teaser.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 1 - MEC OpenAPIs ==<br />
by Walter Featherstone (Samsung R&D Institute UK)<br />
{{#evu:https://www.youtube.com/watch?v=s-QPZ6jsqWo&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=2<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep1_-_MEC_OpenAPIs.pdf MEC-TECH-SERIES_ep1 - MEC OpenAPIs]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_1_-_MEC_OpenAPIs.mp3 audio]<br />
<br />
<br><br />
<br><br />
<br />
== Episode 2 - Overview of MEC Federation == <br />
by Dario Sabella (Intel)<br />
{{#evu:https://www.youtube.com/watch?v=LuLs0fknW70&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=3<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep2_-_Overview_of_MEC_Federation.pdf MEC-TECH-SERIES_ep2 - Overview of MEC Federation]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_2_-_Overview_of_MEC_Federation.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 3 - Edge enablement APIs == <br />
by Alice Li (Huawei Technology UK)<br />
{{#evu:https://www.youtube.com/watch?v=t8NTOCKcUhs&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=4<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep3_-_Edge_enablement_APIs.pdf MEC-TECH-SERIES_ep3 - Edge enablement APIs]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_3_-_Edge_enablement_APIs.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 4 - MEC Sandbox == <br />
by Robert Gadza (InterDigital)<br />
{{#evu:https://www.youtube.com/watch?v=IMDN4VSIgLU&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=5<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [https://mecwiki.etsi.org/images/MEC-TECH-SERIES_ep4_-_MEC_Sandbox.pdf MEC-TECH-SERIES ep4 - MEC Sandbox]<br />
<br />
The Podcast mp3 version is available here: [https://mecwiki.etsi.org/images/Episode_4_-_MEC_Sandbox.mp3 audio]<br />
<br />
<br />
<br><br />
<br></div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Tech_Series&diff=3525MEC Tech Series2022-02-01T14:42:39Z<p>Featherston: </p>
<hr />
<div>__TOC__<br />
<br />
<br><br />
{| <br />
|[[File:Youtube-subscribe-button-6030373 1280.png|100px|left|top|link=https://www.youtube.com/playlist?list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h]] <br />
<br />
These videos are also available in the '''MEC Tech Series''' playlist on ETSI YouTube channel. <br />
<br />
Why not share your insights by volunteering to produce a MEC Tech Series episode on a topic of your choice. Please email CTI_Support@etsi.org for more information. <br />
|}<br />
<br><br />
<br />
== Episode 0 - Chair's Teaser ==<br />
by Dario Sabella (Intel)<br />
{{#evu:https://www.youtube.com/watch?v=wunoMBersKQ&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep0_-_Chair%27s_Teaser.pdf MEC-TECH-SERIES_ep0 - Chair's Teaser]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_0_-_Chairs_Teaser.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 1 - MEC OpenAPIs ==<br />
by Walter Featherstone (Samsung R&D Institute UK)<br />
{{#evu:https://www.youtube.com/watch?v=s-QPZ6jsqWo&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=2<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep1_-_MEC_OpenAPIs.pdf MEC-TECH-SERIES_ep1 - MEC OpenAPIs]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_1_-_MEC_OpenAPIs.mp3 audio]<br />
<br />
<br><br />
<br><br />
<br />
== Episode 2 - Overview of MEC Federation == <br />
by Dario Sabella (Intel)<br />
{{#evu:https://www.youtube.com/watch?v=LuLs0fknW70&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=3<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep2_-_Overview_of_MEC_Federation.pdf MEC-TECH-SERIES_ep2 - Overview of MEC Federation]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_2_-_Overview_of_MEC_Federation.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 3 - Edge enablement APIs == <br />
by Alice Li (Huawei Technology UK)<br />
{{#evu:https://www.youtube.com/watch?v=t8NTOCKcUhs&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=4<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [//mecwiki.etsi.org/images/MEC-TECH-SERIES_ep3_-_Edge_enablement_APIs.pdf MEC-TECH-SERIES_ep3 - Edge enablement APIs]<br />
<br />
The Podcast mp3 version is available here: [//mecwiki.etsi.org/images/Episode_3_-_Edge_enablement_APIs.mp3 audio]<br />
<br><br />
<br><br />
<br />
== Episode 4 - MEC Sandbox == <br />
by Robert Gadza (InterDigital)<br />
{{#evu:https://www.youtube.com/watch?v=IMDN4VSIgLU&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=5<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
The PDF slides set is available here: [https://mecwiki.etsi.org/images/MEC-TECH-SERIES_ep4_-_MEC_Sandbox.pdf MEC-TECH-SERIES ep4 - MEC Sandbox]<br />
<br />
The Podcast mp3 version is available here: [https://mecwiki.etsi.org/images/Episode_4_-_MEC_Sandbox.mp3 audio]<br />
<br />
<br />
<br><br />
<br></div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Tech_Series&diff=3448MEC Tech Series2021-12-10T09:48:08Z<p>Featherston: Missing closing bracket</p>
<hr />
<div>__TOC__<br />
<br />
<br><br />
{| <br />
|[[File:Youtube-subscribe-button-6030373 1280.png|100px|left|top|link=https://www.youtube.com/playlist?list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h]] <br />
<br />
These videos are also available in the '''MEC Tech Series''' playlist on ETSI YouTube channel <br />
|}<br />
<br><br />
<br />
== Episode 0 - Chair's Teaser ==<br />
by Dario Sabella (Intel)<br />
{{#evu:https://www.youtube.com/watch?v=wunoMBersKQ&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
<br><br />
== Episode 1 - MEC OpenAPIs ==<br />
by Walter Featherstone (Samsung R&D Institute UK)<br />
{{#evu:https://www.youtube.com/watch?v=s-QPZ6jsqWo&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=2<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
<br />
<br><br />
== Episode 2 - Overview of MEC Federation == <br />
by Dario Sabella (Intel)<br />
{{#evu:https://www.youtube.com/watch?v=LuLs0fknW70&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=3<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
<br><br />
== Episode 3 - Edge enablement APIs == <br />
by Alice Li (Huawei Technology UK)<br />
{{#evu:https://www.youtube.com/watch?v=t8NTOCKcUhs&list=PLlNY888NYhGA_qOP_-dflG12xo37xEw7h&index=4<br />
|alignment=inline<br />
|dimensions="120"<br />
}}<br />
<br></div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=3033MEC Ecosystem2021-06-14T10:00:47Z<p>Featherston: Added statement with regards to ETSI not making statements of compliance</p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''[https://try-mec.etsi.org/ MEC Sandbox]''': MEC Service API playground<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
Please note that ETSI does not make statements of compliance with regards to implementations. However, MEC Applications and MEC Solutions listed on this page have been recognised by ISG MEC as having relevance to parts of the MEC system or more generally the overall MEC ecosystem.<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|'''Unibo MEC API Tester'''[[File:Unibo mec api tester.png|center|frameless|200x200px]]<br />
|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).<br />
|MEC 011 (Mp1)<br />
|NA<br />
|[https://github.com/berdav/unibo-test-mec Link]<br />
|[mailto:davide.berardi6@unibo.it Davide Berardi]<br />
|}<br />
<br />
== MEC Solutions ==<br />
<br />
List of MEC Solutions made available by third parties (in alphabetical order). 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).<br />
<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|'''AdvantEdge''' [[File:advantedge.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform <br />
| MEC 012 Radio Network Information<br />MEC 013 Location<br />MEC 028 WLAN Information<br />
|[https://github.com/InterDigitalInc/AdvantEDGE Link]<br />
|[mailto:AdvantEDGE@InterDigital.com AdvantEDGE] <br />
|-<br />
|'''Connected Vehicle Blueprint (Aka CVB)''' [[File:akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager <br />
|MEC 011 Mp1 & Mm5 <br />
|[https://wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]<br />
|[mailto:yargyang@tencent.com Yarg Yang] <br />
|-<br />
|'''Eclipse zenoh''' [[File:zenoh.png|center|frameless|200x200px]]<br />
|Eclipse zenoh unifies data in motion, data in-use, data at rest and computations. It carefully blends traditional pub/sub with geo-distributed storages, queries and computations, while retaining a level of time and space efficiency that is well beyond any of the mainstream stacks. It is a perfect fit as an alternative transport protocol for MEC applications as well as technological stack to build distributed MEC platforms.<br />
|Alternative transport protocol for MEC Platform<br />
|MEC 011 Mp1 <br />
|[http://zenoh.io/ Link]<br />
|[https://gitter.im/atolab/zenoh Gitter community channel]<br />
|-<br />
|'''EdgeGallery''' [[File:Edgegallery.png|center|frameless|200x200px]]<br />
|The EdgeGallery community focuses on providing a MEC platform framework at a carrier’s network edge, whilst adopting the de facto standard of network service openness through open source collaboration. The framework enables MEC edge resources and applications, whilst providing both security and management capabilities. It also offers interconnectivity with the public cloud. The result is the creation of unified MEC application ecosystem, which is designed to be compatible across a carrier’s heterogeneous edge infrastructure.<br />
|MEC Open Source Platform<br />
|MEC 010-2,MEC 011,MEC 009,and will support more ETSI APIs in further releases <br />
|[https://www.edgegallery.org/en/ Link]<br />
|[https://edgegallery.groups.io/g/main Maillist]<br />
|-<br />
|'''Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)''' [[File:akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager<br />
|MEC 011 Mp1 & Mm3<br />
|[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]<br />
|[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]<br />
|-<br />
|'''i-MEC''' [[File:Italtel RGB.jpg|center|frameless|200x200px]]<br />
|Italtel MEC platform i-MEC brings high value in the network enabling a wide set of services which leverage reduced end-to-end latency (uRLLC), pre-processing at the edge (mMTC) and broadband services (eMBB). i-MEC contributes to reduce the traffic load on the backhauling transport network with relevant saving of cost for the Service Operator.<br />
|MEC Platform<br />
|MEC011 Mp1, Mm5 proprietary API, Mp2 proprietary API (OpenFlow based)<br />
|[https://www.italtel.com/products/multi-access-edge-computing-mec-platform/ Link]<br />
|[Mailto:marketing_technology@italtel.com Italtel]<br />
|-<br />
|'''LightEdge''' [[File:lightedge-logo.png|center|frameless|150x150px]]<br />
|LightEdge is a lightweight, ETSI-compliant MEC solution for 4G and 5G networks. It is designed to work natively on top of Kubernetes and is transparent to the existing components of a 4G network, therefore requiring zero modifications to the MNO’s environment.<br />
| MEC Platform <br />
| RNI (MEC-012), WIA (MEC-028), partially Application Enablement (MEC-011) <br />
|[http://lightedge.github.io/ Link]<br />
|[mailto:roberto.riggio@gmail.com Roberto Riggio] <br />
|-<br />
|'''MEC Location API Simulator''' [[File:LINKS_Logo.png|center|frameless|200x200px]]<br />
|The Location API simulator helps developers to create applications that use MEC Location API. It provides a MEC Location Service accessible via Location API as specified in the ETSI GS MEC013 document, available as a RESTful web service. It has a Graphical User Interface enabling developers to simulate mobile users' movements by feeding the simulator with a GPS track in .gpx format. The first release implements a subset of MEC013 API but the full set of APIs and an improved engine to simulate cars, VRU and more will be part of future releases.<br />
| MEC013 accessible APIs (with an engine to simulate mobile users’ movement) <br />
| MEC 013 Location<br />
|[https://networkbuilders.intel.com/commercial-applications/links-foundation Link]<br />
|[mailto:daniele.brevi@linksfoundation.com Daniele Brevi] <br />
|-<br />
|'''Public Cloud Edge Interface (PCEI)''' [[File:akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|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<br />
|MEC 013 Location API<br />
|[https://wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]<br />
|[mailto:oberzin@equinix.com Oleg Berzin]<br />
|-<br />
|'''ServerlessOnEdge'''[[File:Logo-small.png|center|frameless|200x200px]]<br />
|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).<br />
|User app LCM proxy<br />
|MEC 016 Device application interface (Mx2)<br />
|[https://github.com/ccicconetti/serverlessonedge Link]<br />
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]<br />
|-<br />
|}<br />
<br />
=== Request your project to be listed ===<br />
<br />
<big><br />
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please [Mailto:CTI_support@etsi.org?Subject=ISG+MEC+WIKI+Ecosystem+request contact ETSI CTI], with title "ISG MEC WIKI Ecosystem request".<br />
<u>'''Any'''</u> organization (ETSI member or not) is entitled to send the request.<br />
</big><br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2981MEC Ecosystem2021-01-11T12:04:19Z<p>Featherston: Added MEC Sandbox link</p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''[https://try-mec.etsi.org/ MEC Sandbox]''': MEC Service API playground<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|'''Unibo MEC API Tester'''[[File:Unibo mec api tester.png|center|frameless|200x200px]]<br />
|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).<br />
|MEC 011 (Mp1)<br />
|NA<br />
|[https://github.com/berdav/unibo-test-mec Link]<br />
|[mailto:davide.berardi6@unibo.it Davide Berardi]<br />
|}<br />
<br />
== MEC Solutions ==<br />
<br />
List of MEC Solutions made available by third parties (in alphabetical order). 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).<br />
<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|'''AdvantEdge''' [[File:advantedge.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform <br />
| MEC 012 Radio Network Information<br />MEC 013 Location<br />MEC 028 WLAN Information<br />
|[https://github.com/InterDigitalInc/AdvantEDGE Link]<br />
|[mailto:AdvantEDGE@InterDigital.com AdvantEDGE@InterDigital.com] <br />
|-<br />
|'''Connected Vehicle Blueprint (Aka CVB)''' [[File:akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager <br />
|MEC 011 Mp1 & Mm5 <br />
|[https://wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]<br />
|[mailto:yargyang@tencent.com Yarg Yang] <br />
|-<br />
|'''Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)''' [[File:akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager<br />
|MEC 011 Mp1 & Mm3<br />
|[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]<br />
|[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]<br />
|-<br />
|'''i-MEC''' [[File:Italtel RGB.jpg|center|frameless|200x200px]]<br />
|Italtel MEC platform i-MEC brings high value in the network enabling a wide set of services which leverage reduced end-to-end latency (uRLLC), pre-processing at the edge (mMTC) and broadband services (eMBB). i-MEC contributes to reduce the traffic load on the backhauling transport network with relevant saving of cost for the Service Operator.<br />
|MEC Platform<br />
|MEC011 Mp1, Mm5 proprietary API, Mp2 proprietary API (OpenFlow based)<br />
|[https://www.italtel.com/products/multi-access-edge-computing-mec-platform/ Link]<br />
|[Mailto:marketing_technology@italtel.com Italtel]<br />
|-<br />
|'''Public Cloud Edge Interface (PCEI)''' [[File:akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|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<br />
|MEC 013 Location API<br />
|[https://wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]<br />
|[mailto:oberzin@equinix.com Oleg Berzin]<br />
|-<br />
|'''ServerlessOnEdge'''[[File:Logo-small.png|center|frameless|200x200px]]<br />
|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).<br />
|User app LCM proxy<br />
|MEC 016 Device application interface (Mx2)<br />
|[https://github.com/ccicconetti/serverlessonedge Link]<br />
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]<br />
|-<br />
|}<br />
<br />
=== Request your project to be listed ===<br />
<br />
<big><br />
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please [Mailto:CTI_support@etsi.org?Subject=ISG+MEC+WIKI+Ecosystem+request contact ETSI CTI], with title "ISG MEC WIKI Ecosystem request".<br />
<u>'''Any'''</u> organization (ETSI member or not) is entitled to send the request.<br />
</big><br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2924MEC Ecosystem2020-10-21T05:59:44Z<p>Featherston: /* MEC Solutions */</p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|'''Unibo MEC API Tester'''[[File:Unibo mec api tester.png|center|frameless|200x200px]]<br />
|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).<br />
|MEC 011 (Mp1)<br />
|NA<br />
|[https://github.com/berdav/unibo-test-mec Link]<br />
|[mailto:davide.berardi6@unibo.it Davide Berardi]<br />
|}<br />
<br />
== MEC Solutions ==<br />
<br />
List of MEC Solutions made available by third parties (in alphabetical order). 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).<br />
<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|'''AdvantEdge''' [[File:advantedge.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform <br />
| MEC 012 Radio Network Information<br />MEC 013 Location<br />MEC 028 WLAN Information<br />
|[https://github.com/InterDigitalInc/AdvantEDGE Link]<br />
|[mailto:AdvantEDGE@InterDigital.com AdvantEDGE@InterDigital.com] <br />
|-<br />
|'''Connected Vehicle Blueprint (Aka CVB)'''<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager <br />
|MEC 011 Mp1 & Mm5 <br />
|[https://wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]<br />
|[mailto:yargyang@tencent.com Yarg Yang] <br />
|-<br />
|'''Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)'''<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager<br />
|MEC 011 Mp1 & Mm3<br />
|[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]<br />
|[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]<br />
|-<br />
|'''Public Cloud Edge Interface (PCEI)'''<br />
|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.<br />
|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<br />
|MEC 013 Location API<br />
|[https://wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]<br />
|[mailto:oberzin@equinix.com Oleg Berzin]<br />
|-<br />
|'''ServerlessOnEdge'''[[File:Logo-small.png|center|frameless|200x200px]]<br />
|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).<br />
|User app LCM proxy<br />
|MEC 016 Device application interface (Mx2)<br />
|[https://github.com/ccicconetti/serverlessonedge Link]<br />
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]<br />
|-<br />
|}<br />
<br />
=== Request your project to be listed ===<br />
<br />
<big><br />
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please [Mailto:CTI_support@etsi.org?Subject=ISG+MEC+WIKI+Ecosystem+request contact ETSI CTI], with title "ISG MEC WIKI Ecosystem request".<br />
<u>'''Any'''</u> organization (ETSI member or not) is entitled to send the request.<br />
</big><br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2923MEC Ecosystem2020-10-20T14:44:46Z<p>Featherston: /* MEC Solutions */</p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|'''Unibo MEC API Tester'''[[File:Unibo mec api tester.png|center|frameless|200x200px]]<br />
|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).<br />
|MEC 011 (Mp1)<br />
|NA<br />
|[https://github.com/berdav/unibo-test-mec Link]<br />
|[mailto:davide.berardi6@unibo.it Davide Berardi]<br />
|}<br />
<br />
== MEC Solutions ==<br />
<br />
List of MEC Solutions made available by third parties (in alphabetical order). 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).<br />
<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|'''AdvantEdge''' [[File:advantedge.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform <br />
| MEC 012 Radio Network Information<br />MEC 013 Location<br />MEC 028 WLAN Information<br />
|[https://github.com/InterDigitalInc/AdvantEDGE Link]<br />
|[mailto:AdvantEDGE@InterDigital.com AdvantEDGE@InterDigital.com] <br />
|-<br />
|'''Connected Vehicle Blueprint (Aka CVB)''' [[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager <br />
|MEC 011 Mp1 & Mm5 <br />
|[https://wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]<br />
|[mailto:yargyang@tencent.com Yarg Yang] <br />
|-<br />
|'''Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)'''[[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager<br />
|MEC 011 Mp1 & Mm3<br />
|[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]<br />
|[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]<br />
|-<br />
|'''Public Cloud Edge Interface (PCEI)'''[[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|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<br />
|MEC 013 Location API<br />
|[https://wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]<br />
|[mailto:oberzin@equinix.com Oleg Berzin]<br />
|-<br />
|'''ServerlessOnEdge'''[[File:Logo-small.png|center|frameless|200x200px]]<br />
|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).<br />
|User app LCM proxy<br />
|MEC 016 Device application interface (Mx2)<br />
|[https://github.com/ccicconetti/serverlessonedge Link]<br />
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]<br />
|-<br />
|}<br />
<br />
=== Request your project to be listed ===<br />
<br />
<big><br />
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please [Mailto:CTI_support@etsi.org?Subject=ISG+MEC+WIKI+Ecosystem+request contact ETSI CTI], with title "ISG MEC WIKI Ecosystem request".<br />
<u>'''Any'''</u> organization (ETSI member or not) is entitled to send the request.<br />
</big><br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2919MEC Ecosystem2020-10-20T07:24:24Z<p>Featherston: /* MEC Solutions */</p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|'''Unibo MEC API Tester'''[[File:Unibo mec api tester.png|center|frameless|200x200px]]<br />
|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).<br />
|MEC 011 (Mp1) APIs<br />
|NA<br />
|[https://github.com/berdav/unibo-test-mec Link]<br />
|[mailto:davide.berardi6@unibo.it Davide Berardi]<br />
|}<br />
<br />
== MEC Solutions ==<br />
<br />
List of MEC Solutions made available by third parties (in alphabetical order). 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).<br />
<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|'''Connected Vehicle Blueprint (Aka CVB)''' [[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager <br />
|Mp1 & Mm5 <br />
|[https://wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]<br />
|[mailto:yargyang@tencent.com Yarg Yang] <br />
|-<br />
|'''Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)'''[[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager<br />
|Mp1 & Mm3<br />
|[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]<br />
|[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]<br />
|-<br />
|'''Public Cloud Edge Interface (PCEI)'''[[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|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<br />
|MEC Location API<br />
|[https://wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]<br />
|[mailto:oberzin@equinix.com Oleg Berzin]<br />
|-<br />
|'''ServerlessOnEdge'''[[File:Logo-small.png|center|frameless|200x200px]]<br />
|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).<br />
|User app LCM proxy<br />
|MEC Device application interface over Mx2<br />
|[https://github.com/ccicconetti/serverlessonedge Link]<br />
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]<br />
|-<br />
|}<br />
<br />
=== Request your project to be listed ===<br />
<br />
<big><br />
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please [Mailto:CTI_support@etsi.org?Subject=ISG+MEC+WIKI+Ecosystem+request contact ETSI CTI], with title "ISG MEC WIKI Ecosystem request".<br />
<u>'''Any'''</u> organization (ETSI member or not) is entitled to send the request.<br />
</big><br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2918MEC Ecosystem2020-10-20T07:21:33Z<p>Featherston: /* MEC Solutions */</p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|'''Unibo MEC API Tester'''[[File:Unibo mec api tester.png|center|frameless|200x200px]]<br />
|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).<br />
|MEC 011 (Mp1) APIs<br />
|NA<br />
|[https://github.com/berdav/unibo-test-mec Link]<br />
|[mailto:davide.berardi6@unibo.it Davide Berardi]<br />
|}<br />
<br />
== MEC Solutions ==<br />
<br />
List of MEC Solutions made available by third parties (in alphabetical order). 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).<br />
<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|'''Connected Vehicle Blueprint(Aka CVB)''' [[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager <br />
|Mp1 & Mm5 <br />
|[https://wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]<br />
|[mailto:yargyang@tencent.com Yarg Yang] <br />
|-<br />
|'''Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)'''[[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|MEC Platform(s), MEC Platform Manager<br />
|Mp1 & Mm3<br />
|[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]<br />
|[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]<br />
|-<br />
|'''Public Cloud Edge Interface (PCEI)'''[[File:Akraino.png|center|frameless|200x200px]]<br />
|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.<br />
|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<br />
|MEC Location API<br />
|[https://wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]<br />
|[mailto:oberzin@equinix.com Oleg Berzin]<br />
|-<br />
|'''ServerlessOnEdge'''[[File:Logo-small.png|center|frameless|200x200px]]<br />
|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).<br />
|User app LCM proxy<br />
|MEC Device application interface over Mx2<br />
|[https://github.com/ccicconetti/serverlessonedge Link]<br />
|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]<br />
|-<br />
|}<br />
<br />
=== Request your project to be listed ===<br />
<br />
<big><br />
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please [Mailto:CTI_support@etsi.org?Subject=ISG+MEC+WIKI+Ecosystem+request contact ETSI CTI], with title "ISG MEC WIKI Ecosystem request".<br />
<u>'''Any'''</u> organization (ETSI member or not) is entitled to send the request.<br />
</big><br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=Main_Page&diff=2907Main Page2020-05-22T12:22:50Z<p>Featherston: </p>
<hr />
<div>__NOTOC__<br />
<br />
<div style="width:100%;display:block; overflow: overlay"><br />
<br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Ecosystem ==<br />
* [https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem '''MEC Ecosystem'''] main page: Covers API Testing, [https://forge.etsi.org Forge] (OpenAPI descriptions), MEC Sandbox (API playground) and details of relevant external projects <br />
</div><br />
<br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Testing ==<br />
* [https://www.etsi.org/deliver/etsi_gr/MEC-DEC/001_099/025/02.01.01_60/gr_MEC-DEC025v020101p.pdf '''Testing Framework''']: Methodology, guidelines and framework<br />
* '''API Conformance Test Suites'''<br />
** [https://forge.etsi.org/rep/mec/gs032p2-test-purposes '''Test Purposes''']<br />
** [https://forge.etsi.org/rep/mec/gs032p3-ttcn-test-suite '''TTCN-3''']: Testing and Test Control Notation version 3 testing language<br />
** [https://forge.etsi.org/rep/mec/gs032p3-robot-test-suite '''Robot Framework''']<br />
</div><br />
<br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Proof of Concept Activity ==<br />
<br />
* '''[[Ongoing PoCs]]''' Information about ongoing ISG MEC PoCs.<br />
* '''[[PoC Topics]]''' Information about ISG MEC PoC Topics.<br />
* '''[[PoC Framework]]''' Information about ISG MEC PoC Framework (process, criteria, templates....).<br />
* '''[[Logos and guidelines]]''' Information and guidelines on the use of ETSI and MEC PoC logo.<br />
* '''[[Q&A]]''' Usual questions (and answers) on ISG MEC PoCs.<br />
</div><br />
<br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Hackathons ==<br />
* '''[[MEC Hackathon Framework]]''': Guidelines and call for proposals of hackathons for MEC<br />
</div><br />
<br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Deployment Trials ==<br />
* '''[[MEC Deployment Trials Framework]]''': Discover MDTs and how to participate.<br />
* [[Ongoing MDTs|'''Check the list of MDT''']]<br />
<br />
</div><br />
</div><br />
<br />
<div style="display:block; width:100%"><br />
This Wiki is provided as a tool for the use of ISG MEC participants.<br />
You may need to login to access some information<br />
<br />
''' >>> ISG MEC participants can login with their ETSI OnLine (EOL) account <<<'''<br />
<br />
If you are an ISG MEC participant and do not have an EOL account yet, <br />
you can [http://webapp.etsi.org/createaccount apply for an EOL account], or send a request to [mailto:helpdesk@etsi.org ETSI helpdesk]<br />
<br />
For any other wiki related request, please [mailto:CTI_support@etsi.org?Subject=ISG_MEC_WIKI_request contact ETSI CTI]<br />
<br />
<center><br />
'''[http://mecwiki.etsi.org/index.php?title=Special%3AUserLogin&returnto=Main+Page Login with your EOL account!]'''<br />
</center><br />
<br />
</div></div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2906MEC Ecosystem2020-05-22T12:01:35Z<p>Featherston: </p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== MEC Solutions ==<br />
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).<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please [Mailto:CTI_support@etsi.org?Subject=ISG+MEC+WIKI+Ecosystem+request contact ETSI CTI], with title "ISG MEC WIKI Ecosystem request" <u>'''Any'''</u> organization (ETSI member or not) is entitled to send the request.<br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2905MEC Ecosystem2020-05-22T12:00:26Z<p>Featherston: </p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== MEC Solutions ==<br />
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).<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
A request to add a new entry to either the MEC Applications or MEC Solutions should be sent to please [Mailto:CTI&#x20;support@etsi.org?Subject=ISG&#x20;MEC&#x20;WIKI&#x20;Ecosystem&#x20;request contact ETSI CTI], with title "ISG MEC WIKI Ecosystem request" <u>'''Any'''</u> organization (ETSI member or not) is entitled to send the request.<br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2904MEC Ecosystem2020-05-22T11:53:34Z<p>Featherston: </p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions<br />
*'''[[MEC Ecosystem#MEC Solutions|MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== MEC Solutions ==<br />
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).<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
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.<br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2903MEC Ecosystem2020-05-22T11:14:22Z<p>Featherston: </p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[[MEC Applications]]''': 3rd party solutions<br />
*'''[[MEC Solutions]]''': 3rd party solutions<br />
<br />
== MEC Applications ==<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
== MEC Solutions ==<br />
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).<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
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.<br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2902MEC Ecosystem2020-05-22T11:12:33Z<p>Featherston: Updates according to MEC(20)000151 (was MECDECODE(20)000005)</p>
<hr />
<div>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: <br />
*[https://forge.etsi.org/ '''Forge Projects''']: Includes OpenAPI/Swagger & Protobuf descriptions of the APIs specified by ISG MEC.<br />
**[https://mecwiki.etsi.org/index.php?title=OpenAPI_development_guidelines OpenAPI development guidelines]: How can I contribute to the API development?<br />
*'''MEC Sandbox''': MEC Service API playground (in development)<br />
**[https://forge.etsi.org/rep/stf-587/mec-sandbox-scenarios MEC Sandbox Scenarios] (EOL account required): Macro/micro network emulation scenarios<br />
*'''[[MEC Applications]]''': 3rd party solutions<br />
*'''[[MEC Solutions]]''': 3rd party solutions<br />
<br />
=== MEC Applications ===<br />
List of MEC Applications made available by third parties<br />
{| class="wikitable"<br />
|+<br />
!Name of the App & logo<br />
!Description<br />
!MEC Consumed APIs<br />
!MEC API provided<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
<br />
=== MEC Solutions ===<br />
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).<br />
{| class="wikitable"<br />
|+<br />
!Name of the project & logo<br />
!Description<br />
!MEC Components provided<br />
!MEC APIs supported<br />
!Link<br />
!Contact<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|<br />
|}<br />
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.<br />
<br />
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.<br />
<br />
The chairman of DECODE WG and ETSI Secretariat will review the proposal and publish it.<br />
<br />
Criteria for the inclusion into the Ecosystem page are:<br />
* 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].<br />
* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.</div>Featherstonhttps://mecwiki.etsi.org/index.php?title=Main_Page&diff=2901Main Page2020-05-22T10:45:13Z<p>Featherston: Updates according to MEC(20)000151 (was MECDECODE(20)000005)</p>
<hr />
<div>__NOTOC__<br />
<br />
<div style="width:100%;display:block; overflow: overlay"><br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Ecosystem ==<br />
* [https://mecwiki.etsi.org/index.php?title=MEC_Ecosystem '''MEC Ecosystem'''] main page: Covers API Testing, [https://forge.etsi.org Forge] (OpenAPI descriptions), MEC Sandbox (API playground) and details of relevant external projects <br />
</div><br />
<br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Proof of Concept Activity ==<br />
<br />
* '''[[Ongoing PoCs]]''' Information about ongoing ISG MEC PoCs.<br />
* '''[[PoC Topics]]''' Information about ISG MEC PoC Topics.<br />
* '''[[PoC Framework]]''' Information about ISG MEC PoC Framework (process, criteria, templates....).<br />
* '''[[Logos and guidelines]]''' Information and guidelines on the use of ETSI and MEC PoC logo.<br />
* '''[[Q&A]]''' Usual questions (and answers) on ISG MEC PoCs.<br />
</div><br />
<br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Hackathons ==<br />
* '''[[MEC Hackathon Framework]]''': Guidelines and call for proposals of hackathons for MEC<br />
</div><br />
<br />
<div style="width:45%; min-width: 100px; padding:20px;float:left; font-size:12pt"><br />
== MEC Deployment Trials ==<br />
* '''[[MEC Deployment Trials Framework]]''': Discover MDTs and how to participate.<br />
* [[Ongoing MDTs|'''Check the list of MDT''']]<br />
<br />
</div><br />
</div><br />
<br />
<div style="display:block; width:100%"><br />
This Wiki is provided as a tool for the use of ISG MEC participants.<br />
You may need to login to access some information<br />
<br />
''' >>> ISG MEC participants can login with their ETSI OnLine (EOL) account <<<'''<br />
<br />
If you are an ISG MEC participant and do not have an EOL account yet, <br />
you can [http://webapp.etsi.org/createaccount apply for an EOL account], or send a request to [mailto:helpdesk@etsi.org ETSI helpdesk]<br />
<br />
For any other wiki related request, please [mailto:CTI_support@etsi.org?Subject=ISG_MEC_WIKI_request contact ETSI CTI]<br />
<br />
<center><br />
'''[http://mecwiki.etsi.org/index.php?title=Special%3AUserLogin&returnto=Main+Page Login with your EOL account!]'''<br />
</center><br />
<br />
</div></div>Featherstonhttps://mecwiki.etsi.org/index.php?title=MEC_Ecosystem&diff=2900MEC Ecosystem2020-05-22T10:28:38Z<p>Featherston: Created page with "Covering Testing, Forge, MEC Sandbox and Links to relevant external projects Forge Projects: Includes OpenAPI/Swagger & Protobuf descriptions OpenAPI development guidelines..."</p>
<hr />
<div>Covering Testing, Forge, MEC Sandbox and Links to relevant external projects<br />
<br />
Forge Projects: Includes OpenAPI/Swagger & Protobuf descriptions<br />
OpenAPI development guidelines<br />
MEC Sandbox: MEC Service API playground (in development)<br />
MEC Sandbox Scenarios (EOL account required): Macro/micro network emulation scenarios<br />
MEC Applications: 3rd party solutions<br />
MEC Solutions: 3rd party solutions</div>Featherston