MEC Ecosystem - Revision history

Velez at 16:53, 26 March 2024

2024-03-26T16:53:19Z

← Older revision		Revision as of 17:53, 26 March 2024
Line 1:		Line 1:
	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:		This page provides information very much related to the work of the ETSI ISG MEC Deployment and ECOsystem DEvelopment ([//portal.etsi.org//tb.aspx?tbid=874&SubTB=874#/ DECODE]) Working Group, whose aim is to accelerate the development of the MEC ecosystem:

	*'''[~~https:~~//mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions		*'''[//mecwiki.etsi.org/index.php?title=MEC_Ecosystem#MEC_Applications MEC Applications]''': 3rd party solutions
	*'''[[MEC Ecosystem#MEC Solutions\|MEC Solutions]]''': 3rd party solutions		*'''[[MEC Ecosystem#MEC Solutions\|MEC Solutions]]''': 3rd party solutions
	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.		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.
Line 23:		Line 23:
	\|MEC 011 (Mp1)		\|MEC 011 (Mp1)
	\|NA		\|NA
	\|[~~https:~~//github.com/berdav/unibo-test-mec Link]		\|[//github.com/berdav/unibo-test-mec Link]
	\|[mailto:davide.berardi6@unibo.it Davide Berardi]		\|[mailto:davide.berardi6@unibo.it Davide Berardi]
	\|-		\|-
Line 31:		Line 31:
	\|		\|
	\|MEC Analytics API		\|MEC Analytics API
	\|[~~https:~~//github.com/marags-web/marags-web/tree/main/IDS%20on%20Edge%20with%20MEC%20API Link]		\|[//github.com/marags-web/marags-web/tree/main/IDS%20on%20Edge%20with%20MEC%20API Link]
	\|[mailto:Maragatham.muthusamy@intel.com Maragatham Muthusamy]		\|[mailto:Maragatham.muthusamy@intel.com Maragatham Muthusamy]
	\|}		\|}
Line 50:		Line 50:
	\|MEC Platform		\|MEC Platform
	\| MEC 012 Radio Network Information<br />MEC 013 Location<br />MEC 028 WLAN Information		\| MEC 012 Radio Network Information<br />MEC 013 Location<br />MEC 028 WLAN Information
	\|[~~https:~~//github.com/InterDigitalInc/AdvantEDGE Link]		\|[//github.com/InterDigitalInc/AdvantEDGE Link]
	\|[mailto:AdvantEDGE@InterDigital.com AdvantEDGE]		\|[mailto:AdvantEDGE@InterDigital.com AdvantEDGE]
	\|-		\|-
Line 57:		Line 57:
	\|MEC Platform(s), MEC Platform Manager		\|MEC Platform(s), MEC Platform Manager
	\|MEC 011 Mp1 & Mm5		\|MEC 011 Mp1 & Mm5
	\|[~~https:~~//wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]		\|[//wiki.akraino.org/pages/viewpage.action?pageId=9601601 Link]
	\|[mailto:yargyang@tencent.com Yarg Yang]		\|[mailto:yargyang@tencent.com Yarg Yang]
	\|-		\|-
Line 64:		Line 64:
	\|MEC Orchestrator		\|MEC Orchestrator
	\|MEC 010-2 Application descriptor information model		\|MEC 010-2 Application descriptor information model
	\|[~~https:~~//fog05.io/ Link]		\|[//fog05.io/ Link]
	\|[~~https:~~//gitter.im/atolab/fog05 Gitter community channel]		\|[//gitter.im/atolab/fog05 Gitter community channel]
	\|-		\|-
	\|'''Eclipse zenoh''' [[File:zenoh.png\|center\|frameless\|150x150px]]		\|'''Eclipse zenoh''' [[File:zenoh.png\|center\|frameless\|150x150px]]
Line 72:		Line 72:
	\|MEC 011 Mp1		\|MEC 011 Mp1
	\|[http://zenoh.io/ Link]		\|[http://zenoh.io/ Link]
	\|[~~https:~~//gitter.im/atolab/zenoh Gitter community channel]		\|[//gitter.im/atolab/zenoh Gitter community channel]
	\|-		\|-
	\|'''EdgeGallery''' [[File:Edgegallery.png\|center\|frameless\|200x200px]]		\|'''EdgeGallery''' [[File:Edgegallery.png\|center\|frameless\|200x200px]]
Line 78:		Line 78:
	\|MEC Platform		\|MEC Platform
	\|MEC 010-2，MEC 011，MEC 009，and will support more ETSI APIs in further releases		\|MEC 010-2，MEC 011，MEC 009，and will support more ETSI APIs in further releases
	\|[~~https:~~//www.edgegallery.org/en/ Link]		\|[//www.edgegallery.org/en/ Link]
	\|[~~https:~~//edgegallery.groups.io/g/main Maillist]		\|[//edgegallery.groups.io/g/main Maillist]
	\|-		\|-
	\|'''Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)''' [[File:akraino.png\|center\|frameless\|200x200px]]		\|'''Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge)''' [[File:akraino.png\|center\|frameless\|200x200px]]
Line 85:		Line 85:
	\|MEC Platform(s), MEC Platform Manager		\|MEC Platform(s), MEC Platform Manager
	\|MEC 011 Mp1 & Mm3		\|MEC 011 Mp1 & Mm3
	\|[~~https:~~//wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]		\|[//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 94:		Line 94:
	\|MEC app, MEC platform		\|MEC app, MEC platform
	\|MEC 011 Mp1, MEC 10-2, MEC 012 RNIS		\|MEC 011 Mp1, MEC 10-2, MEC 012 RNIS
	\|[~~https:~~//gitlab.eurecom.fr/oai/orchestration/blueprints/-/blob/master/mep/README.md Link]		\|[//gitlab.eurecom.fr/oai/orchestration/blueprints/-/blob/master/mep/README.md Link]
	\|[Mailto:netsoft@eurecom.fr Eurecom]		\|[Mailto:netsoft@eurecom.fr Eurecom]
	\|-		\|-
Line 101:		Line 101:
	\|MEC Platform		\|MEC Platform
	\|MEC011 Mp1, Mm5 proprietary API, Mp2 proprietary API (OpenFlow based)		\|MEC011 Mp1, Mm5 proprietary API, Mp2 proprietary API (OpenFlow based)
	\|[~~https:~~//www.italtel.com/products/multi-access-edge-computing-mec-platform/ Link]		\|[//www.italtel.com/products/multi-access-edge-computing-mec-platform/ Link]
	\|[Mailto:marketing_technology@italtel.com Italtel]		\|[Mailto:marketing_technology@italtel.com Italtel]
	\|-		\|-
Line 115:		Line 115:
	\| MEC013 accessible APIs (with an engine to simulate mobile users’ movement)		\| MEC013 accessible APIs (with an engine to simulate mobile users’ movement)
	\| MEC 013 Location		\| MEC 013 Location
	\|[~~https:~~//networkbuilders.intel.com/commercial-applications/links-foundation Link]		\|[//networkbuilders.intel.com/commercial-applications/links-foundation Link]
	\|[mailto:daniele.brevi@linksfoundation.com Daniele Brevi]		\|[mailto:daniele.brevi@linksfoundation.com Daniele Brevi]
	\|-		\|-
Line 122:		Line 122:
	\|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 013 Location API		\|MEC 013 Location API
	\|[~~https:~~//wiki.akraino.org/display/AK/Public+Cloud+Edge+Interface+%28PCEI%29+Blueprint+Family Link]		\|[//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 129:		Line 129:
	\|User app LCM proxy		\|User app LCM proxy
	\|MEC 016 Device application interface (Mx2)		\|MEC 016 Device application interface (Mx2)
	\|[~~https:~~//github.com/ccicconetti/serverlessonedge Link]		\|[//github.com/ccicconetti/serverlessonedge Link]
	\|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]		\|[Mailto:c.cicconetti@iit.cnr.it Claudio Cicconetti]
	\|-		\|-
Line 155:		Line 155:

	Criteria for the inclusion into the Ecosystem page are:		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 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 [//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.		* The proposed description or text is not offensive and is fit for publication, in line with the purpose of the MEC wiki.

Velez at 08:23, 28 March 2023

2023-03-28T08:23:23Z

← Older revision		Revision as of 09:23, 28 March 2023
Line 95:		Line 95:
	\|MEC 011 Mp1, MEC 10-2, MEC 012 RNIS		\|MEC 011 Mp1, MEC 10-2, MEC 012 RNIS
	\|[https://gitlab.eurecom.fr/oai/orchestration/blueprints/-/blob/master/mep/README.md Link]		\|[https://gitlab.eurecom.fr/oai/orchestration/blueprints/-/blob/master/mep/README.md Link]
	\|[Mailto:Eurecom]		\|[Mailto:netsoft@eurecom.fr Eurecom]
	\|-		\|-
	\|'''i-MEC''' [[File:Italtel RGB.jpg\|center\|frameless\|200x200px]]		\|'''i-MEC''' [[File:Italtel RGB.jpg\|center\|frameless\|200x200px]]

Velez at 08:27, 22 March 2023

2023-03-22T08:27:12Z

← Older revision		Revision as of 09:27, 22 March 2023
Line 75:		Line 75:
	\|-		\|-
	\|'''EdgeGallery''' [[File:Edgegallery.png\|center\|frameless\|200x200px]]		\|'''EdgeGallery''' [[File:Edgegallery.png\|center\|frameless\|200x200px]]
	\|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.		\|The EdgeGallery community focuses on providing an open source 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.
	\|MEC Platform		\|MEC Platform
	\|MEC 010-2，MEC 011，MEC 009，and will support more ETSI APIs in further releases		\|MEC 010-2，MEC 011，MEC 009，and will support more ETSI APIs in further releases

Velez at 08:26, 22 March 2023

2023-03-22T08:26:30Z

← Older revision		Revision as of 09:26, 22 March 2023
Line 9:		Line 9:

	== MEC Applications ==		== MEC Applications ==
	List of ~~'''open source'''~~ MEC Applications made available by third parties		List of MEC Applications made available by third parties
	{\| class="wikitable" style="width: 130%;"		{\| class="wikitable" style="width: 130%;"
	\|+		\|+
Line 36:		Line 36:

	== MEC Solutions ==		== MEC Solutions ==
	List of ~~'''open source'''~~ MEC solutions made available by third parties		List of MEC solutions made available by third parties
	{\| class="wikitable" style="width: 130%;"		{\| class="wikitable" style="width: 130%;"
	\|+		\|+

Velez at 08:24, 22 March 2023

2023-03-22T08:24:29Z

← Older revision		Revision as of 09:24, 22 March 2023
Line 9:		Line 9:

	== MEC Applications ==		== MEC Applications ==
	List of open source MEC Applications made available by third parties		List of '''open source''' MEC Applications made available by third parties
	{\| class="wikitable" style="width: 130%;"		{\| class="wikitable" style="width: 130%;"
	\|+		\|+
Line 36:		Line 36:

	== MEC Solutions ==		== MEC Solutions ==
	List of open source MEC solutions made available by third parties		List of '''open source''' MEC solutions made available by third parties
	{\| class="wikitable" style="width: 130%;"		{\| class="wikitable" style="width: 130%;"
	\|+		\|+

Velez at 08:23, 22 March 2023

2023-03-22T08:23:22Z

← Older revision		Revision as of 09:23, 22 March 2023
Line 9:		Line 9:

	== MEC Applications ==		== MEC Applications ==
	List of MEC Applications made available by third parties		List of open source MEC Applications made available by third parties
	{\| class="wikitable" style="width: 130%;"		{\| class="wikitable" style="width: 130%;"
	\|+		\|+
Line 36:		Line 36:

	== MEC Solutions ==		== MEC Solutions ==
	List of MEC solutions made available by third parties		List of open source MEC solutions made available by third parties
	{\| class="wikitable" style="width: 130%;"		{\| class="wikitable" style="width: 130%;"
	\|+		\|+

Velez at 08:22, 22 March 2023

2023-03-22T08:22:33Z

← Older revision		Revision as of 09:22, 22 March 2023
Line 12:		Line 12:
	{\| class="wikitable" style="width: 130%;"		{\| class="wikitable" style="width: 130%;"
	\|+		\|+
	!style="width: 20%" center\| Name of the App		! style="width: 20%" center \| Name of the App
	! style="width: 40%"\|Description		! style="width: 40%" \|Description
	!MEC Consumed APIs		!MEC Consumed APIs
	!MEC API provided		!MEC API provided
Line 34:		Line 34:
	\|[mailto:Maragatham.muthusamy@intel.com Maragatham Muthusamy]		\|[mailto:Maragatham.muthusamy@intel.com Maragatham Muthusamy]
	\|}		\|}


	== MEC Solutions ==		== MEC Solutions ==
Line 40:		Line 39:
	{\| class="wikitable" style="width: 130%;"		{\| class="wikitable" style="width: 130%;"
	\|+		\|+
	!style="width: 15%"\| Project		! style="width: 15%" \| Project
	!style="width: 40%"\| Description		! style="width: 40%" \| Description
	!style="width: 15%"\| MEC Components provided		! style="width: 15%" \| MEC Components provided
	!style="width: 5%"\| MEC APIs supported		! style="width: 5%" \| MEC APIs supported
	!style="width: 5%"\| Link		! style="width: 5%" \| Link
	!style="width: 15%"\| Contact		! style="width: 15%" \| Contact
	\|-		\|-
	\|'''AdvantEdge''' [[File:advantedge.png\|center\|frameless\|200x200px]]		\|'''AdvantEdge''' [[File:advantedge.png\|center\|frameless\|200x200px]]
Line 77:		Line 76:
	\|'''EdgeGallery''' [[File:Edgegallery.png\|center\|frameless\|200x200px]]		\|'''EdgeGallery''' [[File:Edgegallery.png\|center\|frameless\|200x200px]]
	\|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.		\|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.
	\|MEC ~~Open Source~~ Platform		\|MEC Platform
	\|MEC 010-2，MEC 011，MEC 009，and will support more ETSI APIs in further releases		\|MEC 010-2，MEC 011，MEC 009，and will support more ETSI APIs in further releases
	\|[https://www.edgegallery.org/en/ Link]		\|[https://www.edgegallery.org/en/ Link]
Line 142:		Line 141:
	\|-		\|-
	\|}		\|}



	=== Request your project to be listed ===		=== Request your project to be listed ===

Velez at 14:24, 16 March 2023

2023-03-16T14:24:26Z

← Older revision		Revision as of 15:24, 16 March 2023
Line 95:		Line 95:
	\|MEC app, MEC platform		\|MEC app, MEC platform
	\|MEC 011 Mp1, MEC 10-2, MEC 012 RNIS		\|MEC 011 Mp1, MEC 10-2, MEC 012 RNIS
	\|[https://gitlab.eurecom.fr/oai/orchestration/~~oai~~-~~mec~~ Link]		\|[https://gitlab.eurecom.fr/oai/orchestration/blueprints/-/blob/master/mep/README.md Link]
	\|[Mailto:Eurecom]		\|[Mailto:Eurecom]
	\|-		\|-

Velez at 16:50, 15 March 2023

2023-03-15T16:50:05Z

@@ Line 88: / Line 88: @@
 |[https://wiki.akraino.org/display/AK/Enterprise+Applications+on+Lightweight+5G+Telco+Edge Link]
 |[Mailto:gaurav.agrawal@huawei.com Gaurav Agrawal]
 |-
 |'''i-MEC''' [[File:Italtel RGB.jpg|center|frameless|200x200px]]
@@ Line 130: / Line 139: @@
 |[http://simu5g.org/MEC.html Link]
 |[Mailto:giovanni.nardini@unipi.it Giovanni Nardini, University of Pisa]
 |-
 |-

Velez at 16:41, 15 March 2023

2023-03-15T16:41:59Z

← Older revision		Revision as of 17:41, 15 March 2023
Line 130:		Line 130:
	\|[http://simu5g.org/MEC.html Link]		\|[http://simu5g.org/MEC.html Link]
	\|[Mailto:giovanni.nardini@unipi.it Giovanni Nardini, University of Pisa]		\|[Mailto:giovanni.nardini@unipi.it Giovanni Nardini, University of Pisa]
			\|-
			\|'''Multi-access Edge Computing Platform'''[[File:Simu5G logo.png\|center\|frameless\|200x200px]]
			\|This open source implementation of MEC platform (MEP) allows different MEC applications to discover MEP hosted services and register their own service which can be discovered by other MEC applications.
			OAI-MEP follows ETSI GS MEC 003 V3.1.1. MEC applications communicate with MEP via mp1 interface and applications hosted at MEP communicate with Radio Access Network (RAN) and Core Network (CN) components via mp2 interface.
			The MEP provides service discovery and registry for other MEC applications via mp1 interface. We have implemented MEC Radio Network Information Service (RNIS), ETSI GS MEC 012. It collects the radio network information via mp2 interface. We are working on adding traffic rules control service via communicating with Policy Control Function.
			\|User App LCM proxy, MEC platform
			\|MEC 011 Mp1, MEC 10-2, MEC 012 RNIS
			\|[https://gitlab.eurecom.fr/oai/orchestration/oai-mec Link]
			\|[Mailto:Eurecom]
	\|-		\|-
	\|-		\|-