Versions Compared

Key

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

...

The edge layer which this blueprint targets is the Telco Edge

Below are the high-level features which this blueprint will go on to implement in phase-wise.

  • Lightweight MEP Solution
  • Autonomous MEP Edge Sites. 
  • 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 Compliant Compliant.

Use Case

Lightweight MEC platform, enable real-time enterprise applications on 5G telco edge.

...

Diverse types of applications in various sectors, not limited to below:
● Gaming Applications, VR Live broadcasting
Industrial The industrial park, Campus office etc.
● Video Orchestration and Optimization
● Latency Senstive Sensitive Application for Enterprise scenarios Etc

...

Use Case 3

Business Drivers

The EALT EALTEdge Blueprint is for the Telco Edge, it targets the telecom operators to leverage this blueprint platform services and provide value added service, in return for better revenue generation. It also provide an Application Development Ecosystem by providing open SDK to developer community to develop application which can be tested and deployed easily on the MEP sites. 

...

The Enterprise Applications on Lightweight 5G Telco Edge platform architecture consists of a MECM (Controller) Cluster  (Cloud) and single to multiple MEP Edge MEC Host  Sites .

The MECM Cluster is a Central Cloud Server which controls the deployment of applications on MEP SitesMEC Hosts.  The MECM node can be a single node or a multiple node K8S Cluster.

Overall architecture diagram of the blueprint.

MECM Components:

  • User Management Portal
  • Application Management 
  • Dashboard for Monitoring MEP Sites.
  • Workflow
  • IAAS Adapter
  • Policy
  • FCAPS
  • Host Selection

Image Added

Figure 1 – EALTEdge R3 Architecture

MECM: 

MEC Manager is the central entity in the MEC system responsible for application and service deployment in an highly distributed computing environment, it provides overall view of hosts and applications deployed in the hosts. MEC Manager is the central entity in the MEC system responsible for application and service deployment in an highly distributed computing
environment, it provides overall view of hosts and applications deployed in the hosts.
MECM comprises of MEP manager which performs the following tasks
➢ Application Package Management: On-boarding of application packages and if necessary adjusting them to comply with operator policies, keeping a record of on-boarded packages
➢ Applicatin LCM: Selecting appropriate MEC host(s) for application instantiation based on user inputs, keeping record of instantiated applications on specified hosts. Also carries out other LCM operations like query, deletion, termination etc.

MEC Host:

The MEC Host The MEP Sites are the components where the real action takes place. MEP MEC Host components manages  the execution of various Telco Edge Applications, it provides various services which can be leveraged by edge applications for smooth functioning and its planned to provide additional aPaas services like 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 the MECM Application Management module. The MEP MEC Host will be hosted on a light weight OS.

MEP Components:

  • MEP Services – Location , RNI , Bandwidth , DNS. 
  • Event BUS
  • Service Registry
  • Monitoring


API: EALTEdge Blurprint provides ETSI compliance interfaces specified below for mentioned functionalities:

  • MP1 : It is a interfaces between applications and MEP for Service Registry , Discovery and Service Availability Notification.
  • MM3: It is a interface between Mobile Edge Orchestrator and the Mobile Edge Platform Manager is used for the management of the application lifecycle and keeping track of available mobile edge services.

Platform Architecture

The below diagram gives a overall architecture of the Enterprise Application on Lightweight 5G Telco Edge blueprint which will be finally commissionedas given in Release 3

In the current release the  components released are 

In MECM :

  • Dashboard
  • APP Mgmt
  • Common DB

In MEP :

  • Monitoring
  • Service Registry
  • Event Bus
  • CNI
  • Lightweight Kubernetes EcoSystem. 

...

Image Added

Note: EALTEdge Blueprint Deployment has been tested on Cloud VM and is not tested on Bare-Metal Environment. Though, theoretically deployment should work in bare metal,  provided hardware and software prerequisites are met. Kindly refer R3 - Test Documentation of Enterprise Applications on Lightweight 5G Telco Edge (EALTEdge) to get details on the tested deployment.


MECM Components:

  • Application LCM: Handles the application life cycle management of Applications. 
  • Catalog: Provides application package management
  • Monitoring: Monitoring and Visualisation of platform and applications.
  • Common DB: Persistent Database.

MEC  Host Components:

  • MEP Agent: Client Libraries for application developer for service registry and discovery.
  • API Gateway: Single entry point for MEP Services.
  • Certificate Management: Cloud Native Certificate Creation and Management.
  • Secret Management: Cloud Native Secret Generation and Management.
  • Event BUS: Message BUS Service offered to applications.
  • CNI: Container Network.
  • Service Registry: The service registry provides visibility of the services available on the MEC server.
  • Monitoring: Monitoring and Visualisation of platform and applications.
  • Common DB: Persistent Database.

Software Platform Architecture

The below image shows the software platform distribution and architecture for Release 3.0.

Image RemovedImage Added


EALT EALTEdge Software Components 

Unified CLI: Command Line Interface provides the user interface to install the EALT EALTEdge environment.

MEPM: 

  • APPLCM: Handles the application life cycle management including Application Creation, Instantiation, Termination, Deletion, Query etc. on one or multiple MEC Hosts. 
  • Catalog: Provides application package management including Application package Upload, Query, Deletion, etc. 

MEP:MECM Module to deploy applications on MEP Cluster.

  • Service Registry : The service registry provides visibility of the services available on the MEC server. It uses the concept of loose coupling of services, providing flexibility in application deployment. In addition, the service registry presents service availability (status of the service) together with the related interfaces and versions. It is used by applications to discover and locate the end-points for the services they require, and to publish their own service end-point for other applications to use. The access to the service registry is controlled (authenticated and

...

  • authorised).

MEP Agent: Client Libraries for application developer for service registry and discovery.


Below are details Details of Upstream and Opensource softwares used software's used in various nodes of EALT EALTEdge Environment.

OCD Node

S. No.

Software Name

Category

Version Number

Remarks

1.

Ubuntu

OS18.04

Supports both 16.04  and 18.04

2.GITVersion Control2.17.1
3.AnsibleScripting Tool> 2.5
4.GoLangLanguage> 1.12
5.KubeSprayTool2.13


MECM Node

S. No.

Software Name

Category

Version Number

Remarks

1.

Ubuntu

OS18.04

Supports both 16.04  and 18.04

2.KubernetesOrchestration1.16.02
3.DockerCRI1819.0603
4.Helm

Application Package

Manager 

3.0.2

Running as Bin in MECM

For ARM - 64 and X86 

5.GrafanaAnalytics Dashboard68.57Running as POD in K8S Cluster
6.Postgres SQLDatabase9.6

MEC Host MEP Node

S. No.

Software Name

Category

Version Number

Remarks

1.UbuntuOS18.04Supports both 16.04 and 18.04
2.DockerCRI
18
19.
06
03
3.K3SOrchestration1.18.2
4.Helm

Application Package Manager

3.0.2
Running as bin in MEP

5.PrometheusMonitoring2.18
Running in a POD in K3S Cluster.

6.
cAdvisor
CAdvisorContainer Metrics
Running in a POD in K3S cluster
0.36
7.RabbitMQMessage Queue
Running in a POD in K3S Cluster

APIs

3.7
8.Cert-ManagerCertification Management0.15.0
9.KongAPI Gateway1.5.1
10.VaultSecret Management0.5.0
11Postgres SQLDatabase9.6

APIs

Please refer the API Documentation link : R3 - API Documentation Enterprise Application on Lightweight 5G Telco Edge (EALTEdge)Currently no API are available.

Hardware and Software Management

...