Hack2022 1st Prize: Difference between revisions

From MECwiki
Jump to: navigation, search
(Created page with "<p class="center" style="font-size:34px;"><b> MEC Service Federation for Location-aware IoT withDevOps MEC Infra Orchestration </b><p> <br> = Organization and scope=")
 
No edit summary
Line 3: Line 3:
<br>
<br>


= Organization and scope=
= Team=
Team DOMINO solution submission
Oleg Berzin, Equinix,
oberzin@equinix.com
Vivekanandan Muthukrishnan, Aarna Networks,
vmuthukrishnan@aarnanetworks.com
 
= Introduction =
<p>
In our solution we use Akraino Public Cloud Edge Interface (PCEI) blueprint and MEC Location API service to demonstrate orchestration of federated MEC infrastructure and services, including:
Bare metal, interconnection, virtual routing for MEC and Public Cloud IaaS/SaaS, across two operators/providers (a 5G operator and a MEC provider)
5G Control and User Plane Functions
Deployment and operation of end-to-end cloud native IoT application making use of 5G access and distributed both across geographic locations and across hybrid MEC (edge cloud) and Public Cloud (SaaS) infrastructure
By orchestrating, bare metal servers and their software stack, 5G control plane and user plane functions, interconnection between the 5G provider and MEC provider, connectivity to a public cloud as well as the IoT application and the MEC Location API service, we show how it is possible for providers to enable sharing of their services in a MEC Federation environment.
</p>
 
= Use Case Description =
 
 
= contributions and innovations =
<p>
 
 
</p>

Revision as of 14:22, 24 October 2022

MEC Service Federation for Location-aware IoT withDevOps MEC Infra Orchestration


Team

Team DOMINO solution submission Oleg Berzin, Equinix, oberzin@equinix.com Vivekanandan Muthukrishnan, Aarna Networks, vmuthukrishnan@aarnanetworks.com

Introduction

In our solution we use Akraino Public Cloud Edge Interface (PCEI) blueprint and MEC Location API service to demonstrate orchestration of federated MEC infrastructure and services, including: Bare metal, interconnection, virtual routing for MEC and Public Cloud IaaS/SaaS, across two operators/providers (a 5G operator and a MEC provider) 5G Control and User Plane Functions Deployment and operation of end-to-end cloud native IoT application making use of 5G access and distributed both across geographic locations and across hybrid MEC (edge cloud) and Public Cloud (SaaS) infrastructure By orchestrating, bare metal servers and their software stack, 5G control plane and user plane functions, interconnection between the 5G provider and MEC provider, connectivity to a public cloud as well as the IoT application and the MEC Location API service, we show how it is possible for providers to enable sharing of their services in a MEC Federation environment.

Use Case Description

contributions and innovations