Versions Compared

Old Version 48

changes.mady.by.user Gaurav Agrawal

Saved on

compared with

New Version 49

changes.mady.by.user Gaurav Agrawal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Blueprint Overview

Introduction & Purpose of EALTEdge

Enterprise Application on Lightweight 5G Telco Edge is a blueprint under 5G/MEC system blueprint family. It intends to provide a edge computing platform along with application orchestration & management to host enterprise applications on lightweight 5G Telco Edge. Provided edge computing platform and management is meant to be implemented in compliance with reference to ETSI MEC (please refer ETSI MEC for further details - https://www.etsi.org/technologies/multi-access-edge-computing) For details kindly refer "Targeted Architecture section". BP also intend to provide platform for enterprise application developers to develop, test, package & onboard their applications easily & quickly, thereby empowering developers to innovate & ship faster. Also eventually BP aims to provide platform capabilities and features like Multi-Tenancy, Network-Isolation, Dynamic Orchestration, Network Capabilities exposure, enhanced identification etc. as needed for "MEC in an Enterprise Setting"

...

  • MEO: Maintains system level view of edges and carries out the Application orchestration to the desired Edge based on Application requirements and Edge node resource availability.  
  • MEPM: It is MEP manager which carries out application life cycle management and element management for specific Edge(s).  
  • Edge Connector: Enable flexible traffic offloading from the aspects of control interaction with mobile network exposed capabilities.

AppStore: It is like a market place for Application developer to launch their applications.

Developer platform: It is a platform for developer to carry out development and test their applications.

Edge Node (Located at Telco Edge)

  •   There could be a single or multiple instances of MEPM (along with its sub-components) and it could be deployed in cloud or edge depending on deployment needs (like need for Autonomous edges etc.)
    • APPLCM
      • LCMController: Controls life cycle of applications
      • Infra Plugins: Plugin for a specific infrastructure. Objective is to support Kubernetes & Openstack, but architecture would be extensive to add new Infra Manager with plugins.
    • AppRuleMgr: Manages Traffic and DNS rules
    • Edge Connector: Enable flexible traffic offloading from the aspects of control interaction with mobile network exposed capabilities.

AppStore: It is like a market place for Application developer to launch their applications.

Developer platform: It is a platform for developer to carry out development and test their applications.


Edge Node (Located at Telco Edge)

Edge Node components manages  the execution of various enterprise Applications, it provides various services Edge Node components manages  the execution of various enterprise Applications, it provides various services which can be leveraged by edge applications for smooth functioning and its planned to provide additional aPaas services required for Machine Vision, Video Analytics , IoT Analytics etc in future releases. The MEP sites will be a single node  or a multiple node K3s Cluster, on which applications will be deployed by MECM module. The MEC Host will be hosted on a light weight OS. Edge Node will comprise of following:

  • aPaaS: Producer services for Enterprise applications to consume.
  • PaaS: Platform services needed by enterprise application as well as platform components 
  • MEP Services: 
    • DNS: DNS server and DNS record management service
    • Service Registry: Service registry and discovery, availability notifications
    • AppLCM & AppRuleMgr: Applications life cycle management & application rule managementTraffic Rule Control: Performs traffic rule control
  • Network Capabilities: Network capabilities like location, bandwidth for application to consume
  • Edge Gateway: Enable the traffic offloading from the aspects of data plane with local traffic routing, traffic management and so on

By leveraging upstream projects like EdgeGallery and In collaboration with other BP in same family "5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting" (5G MEC/Slice System to Support Cloud Gaming, HD Video and Live Broadcasting Blueprint - Tentative roadmap of integration other BP is Q3 2021), this BP intends to deliver targeted architecture.. 

Release 4 Architecture

In this release, BP has been targeted to provide Orchestration capability and application developer platform & store for easy & faster app development & onboarding, along with features like multi-tenancy, network-isolation, DNS, LB. Also have added ROBO retail enterprise specific capabilities along with sample application.

Leverage EdgeGallery as an upstream to add following components to the Stack

  • Application/MEC Edge Orchestrator
  • Developer Platform & Application Store.
  • Developer & Tenant Portals
  • Add features like network isolation, DNS support, LB.

ROBO use case integration on EALTEdge:

  • PaaS: Light weight storage. Backup and Restore (scheduled backup/ disaster recovery) for Remote sites
  • aPaaS: Object Detection service for Retail store Inventory
  • Example App: Retail store inventory management

Below is release 4 architecture for details kindly refer platform architecture section.

Image Removed

Note: In release 4 to use BP, UPF (external entity to this BP) needs to be pre-configured with DNS redirection rules and traffic rules to ensure connectivity.

ETSI MEC Alignment Status

Please refer the below figure for EALTEdge components and reference points alignment with respect to ETSI MEC as of Release 4. For API alignment, please refer API document.

Image Removed


SDO Compliance/Reference

ETSI MEC

BP leverages EdgeGallery as an upstream which follows the reference architecture as defined in "section 6 Reference architecture" of "https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/02.01.01_60/gs_mec003v020101p.pdf". Following are components which are available/planned

  1. MEO (Mobile Edge Orchestrator): Mapping to EALTEdge MECM MEO Components
  2. MEPM (Mobile Edge Platform Manager): Mapping to EALTEdge MECM MEPM Components
    1. ME app lifecycle mgmt: Mapping to EALTEdge APPLCM component
    2. ME app rules & reqts mgmt: Mapping to EALTEdge AppRuleMgr component 
  3. MEP
    1. Service Registry: Mapping to EALTEdge MEP-Server sub module
    2. DNS Handler: Mapping to EALTEdge MEP-Server sub module
    3. Traffic Rule Control: Mapping to EALTEdge MEP-Server sub module 

EdgeGallery intends to comply with Application Enablement API as defined in ETSI MEC 011 https://www.etsi.org/deliver/etsi_gs/MEC/001_099/011/02.01.01_60/gs_mec011v020101p.pdf & present @ https://forge.etsi.org/rep/mec/gs011-app-enablement-api. 

Release 4 Architecture

In this release, BP has been targeted to provide Orchestration capability and application developer platform & store for easy & faster app development & onboarding, along with features like multi-tenancy, network-isolation, DNS, LB. Also have added ROBO retail enterprise specific capabilities along with sample application.

Leverage EdgeGallery as an upstream to add following components to the Stack

  • Application/MEC Edge Orchestrator
  • Developer Platform & Application Store.
  • Developer & Tenant Portals
  • Add features like network isolation, DNS support, LB.

ROBO use case integration on EALTEdge:

  • PaaS: Light weight storage. Backup and Restore (scheduled backup/ disaster recovery) for Remote sites
  • aPaaS: Object Detection service for Retail store Inventory
  • Example App: Retail store inventory management

Below is release 4 architecture for details kindly refer platform architecture section.

Image Added

Note:

  1. For release 4, Kubernetes based Infra management is supported.
  2. In release 4 to use BP, UPF (external entity to this BP) needs to be pre-configured with DNS redirection rules and traffic rules to ensure connectivity.

SDO Compliance/Reference

ETSI MEC

BP leverages EdgeGallery v0.9 version which deliver implementation referring some part of ETSI MEC reference architecture as defined in "section 6 Reference architecture" of "https://www.etsi.org/deliver/etsi_gs/MEC/001_099/003/02.01.01_60/gs_mec003v020101p.pdf". Following are components which are available as part of release 4

  1. MEO (Mobile Edge Orchestrator): Mapping to EALTEdge MECM MEO Components
  2. MEPM (Mobile Edge Platform Manager): Mapping to EALTEdge MECM MEPM Components
    1. ME app lifecycle mgmt: Mapping to EALTEdge APPLCM component
  3. MEP
    1. Service Registry: Mapping to EALTEdge MEP-Server sub module
    2. DNS Handler: Mapping to EALTEdge MEP-Server sub module

For Application Enablement API compliance details kindly check http://docs.edgegallery.org/zh_CN/release-v0.9/Projects/MEP/MEP_Interfaces.html#mep-serverNote: For release 4, Kubernetes based Infra management is supported.

Platform Architecture

The below diagram gives a overall architecture of the Enterprise Application on Lightweight 5G Telco Edge blueprint as given in Release 4. 

...