Blueprint overview/Introduction

...

•     IOT sensor application
•     OPC-UA over TSN application  
•     AI Camera Application

Industry Sector: WAN edge, enterpriseEnterprise, diverse IoT applications in various vertical market segments, Carrier

...

Note: ELIOT IotGateway 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 R4 ELIOT R5 - Test Documentation of ELIOT IotGatewayIoT Gateway Test Document to get details on the tested deployment.

...

• aPaaS:
  • Rules Engine: Drools by EdgeX foundry
• GPaaS & IoTPaaS:
  • Software Rolling update: ELIOT includes Hawkbit from Eclipse community to provide software rolling update to Edge Sites / IotGateway nodes
  • IOT Data store: storing data coming from IOT devices and which further IOT application can consume.
  • Basic Device Twin: device profile, configuration, metadata(cmds for devcies) etc. 
  • IOT Protocol: OPC-UA industrial IOT protocol
  • Data Export: export data to Cloud applications and other on Prem applications
  • Monitoring: Graphana , promethous agents to collect and display edge healths
  • CNI: k8s based networking for multi interface support in a POD for SFC scenarios, network policies etc.
• MEP Server:
  • DNS: DNS server and DNS record management service
  • Service Registry: Service registry and discovery, availability notifications
  • AppLCM: applications life cycle management
  • Network Isolation:  Provides separation of control, management and data plan
• API Gateway: Provides secure End points for MEP services as well as producer Applications.

Lightweight Kubernetes (k3s): K3s for lightweight container orchestration. K3s is a highly available, certified Kubernetes distribution designed for production workloads in unattended, resource-constrained, remote locations or inside IoT appliances.

Software Platform Architecture

...

• Eclipse hawkBit is an domain independent back end solution for rolling out software updates to constrained edge devices as well as more powerful controllers and gateways connected to IP based networking infrastructure.
• We are using Hawkbit container environment with latest version.

IOT Portal:

• ELIOT Portal  is currently applicable for both IoT Gateway and uCPE Blueprint. ELIOT Portal main objective is  to have a dashboard for operations and management of ELIOT Cluster. It consists of ELIOT UI and ELIOT API Gateway. Functionalities includes (Dashboard, Application Deployment, Network Management - Managing and viewing Pods, Nodes)

MECM Services: 

• Front End: The MECM-FE management plane mainly provides the registration of edge nodes, APPLCM, and application distribution and deployment functions from the user interface perspective, which is divided into three functional areas. Map area provides switch between nodes in different regions. The KPI, MEP capabilities and application capabilities are displayed in detail according to the currently selected node.
• AppO:  Application orchestra tor is the core module responsible for orchestrating life cycle maintenance operation of application. AppO orchestrates application deployment by executing specified process and automated sequence of tasks, rules and policies. AppO is responsible for retrieving the application instance information, edge host performance statistics and edge host platform capabilities.
• Inventory : Responsible for registrations like MEC Host, AppLCM, AppStore, application. Retrieves all the APPLCM records, MEC host records and applications.
• APM: Application package manager responsible for application package management including On boarding, distributing package to edge , retrieves the application package information and download the application package CSAR.
• Postgres DB: Open source PostgreSQL database is being used to store modules specific information.

...

• aPaaS:
  • Drools - Rules engine.  It is a part of EdgeX foundry services.  In time sensitive use cases or environment where a lot of data is being generated by the connected things, rules engine will be connected to the data coming directly out of core data which will be generated by the gateway node.
• GPaaS & IOTPaaS:
  • Hawkbit:   Eclipse hawkBit is an domain independent back end solution for rolling out software updates to constrained edge devices as well as more powerful controllers and gateways connected to IP based networking infrastructure.
  • EdgeX: EdgeX is opensource , vendor neutral Edge IOT Middleware platform under the LF Edge umbrella.  It collects data from sensors at the edge and acts as a dual transormation engine sending and receiving data to and from enterprise, cloud and on-premise applications.  EdgeX enables autonomous operations and intelligence(AI) at the edge.  EdgeX translates and transforms the infromation coming from ELIOT edge sites i.e from sensors and devices and delivers it to applications over network based protocols in formats and structures that meet the needs of customers.  It also takes data from applications and delivers it to the iotgateway nodes to control and actuation.  
  • OPC-UA: OPC Unified Architecture is a machine to machine communication protocol for industrial automation developed by OPC Foundation which primarily focus on communicating with industrial equipment and systems for data collection and control.   OPC-UA installed on IOTGateway node. 
  • Prometheus Agent: is an open-source systems monitoring and alerting toolkit.  Main features include building a multidimensional data model with time series data identified by metric name and key/value pairs, PromQL to leverage monitoring, time series data collection , nodes are discovered via service discovery or static configuration.  Prometheus is installed on IOT-Gateway node to collect primarily node metrics and to monitor the cluster.
• MEP Services:
  • DNS:  The MEP platform provides the domain name resolution services to the applications deployed in the EdgeGallery MEC, which can be utilized by the device applications in UE. MEC platform receives the DNS configurations from the MEC management, which includes the FQDN (Fully Qualified Domain Name), IP address and related entries. MEC applications can later query or modify the state of these configurations.
  • MEP server: MEP platform services like service registry, discovery, DNS, traffic rules etc.  MEP provides service registration, update, delete, and query related API interfaces. Applications can register, update, delete, and query services through MEP.  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).
• AppLCM: LCM controller and K8s plugin.  Handles the application life cylce, where lcmController is mainly communicates with K8s plugin to upload config, remove config, instantiate, terminate,and query an application. It also provides APIs to query mep capabilities and kpi information from prometheus.

Lightweight Kubernetes ecosystem:

...

• .

...

Below are details of Upstream and Opensource software's used in various nodes of ELIOT Environment.

...

...

Please refer the API Documentation link : ELIOT R5 - API Documentation ELIOT IoTGateway (ELIOT)IOTGateway API documentation

Hardware and Software Management

...

Below table is to capture information and alignment with EdgeX community for better collaboration.

Due to K8s deployment, currently using older version.

This table can be used for track alignment with EdgeX

...