...

This document describes the use of Public Cloud Edge Interface (PCEI) implemented based on Edge Multi-Cluster Orchestrator (EMCO) for deployment of Public Cloud Edge (PCE) Apps from multiple clouds (Azure and AWS), deployment of a 3rd-Party Edge (3PE) App (an implementation of ETSI MEC Location API App), as well as the end-to-end operation of the deployed PCE Apps using simulated Low Power Wide Area (LPWA) IoT client.

Functional Roles

Developers

Individuals/entities that:

• Create the PCE/3PE Apps
• Provision services in Public Clouds (PCC)
  • Note that valid Public Cloud subscriptions/accounts are required
• Package PCE/3PE Apps using Helm Charts
• Access PCEI/EMCO Orchestrator using UI or APIs to onboard PCE/3PE services/apps
  • PCEI R4 supports UI access only

Operators

Entities that:

• Provide network functions and services such as:
  • Access (mobile or fixed)
  • Network connectivity
  • Devices (e.g. LPWA IoT)
• Access PCEI/EMCO Orchestrator using UI or APIs to deploy PCE/3PE apps
• Connecto to Edge Providers/Clusters and Public Clouds using Public Internet or Private Interconnect
  • PCEI R4 supports Public Internet connectivity only

Edge Providers

Entities that:

• Provide edge infrastructure, such as:
  • Edge Data Centers
  • Edge Compute/Network/Storage hardware
  • Edge Virtualization layer/software, such as Kubernetes, Openstack
    • PCEI R4 supports Kubernetes only
• Provide Public Peering and Private Interconnection
  • Between Operators and Edge Providers
  • Between Operators and Public Clouds
  • Between Edge Providers and Public Clouds

Public Cloud Providers

Entities that:

• Provide Iaas/SaaS services

PCEI Enabler

• Orchestration Software and APIs
• May be provided by:
  • Operators
  • Edge Providers
  • Public Cloud Providers

End-to-End Validation Environment

...