Hetrogenous StayTM Platform

High Level Design

Introduction
This document provides the short description for Hetrogenous six-layer model of end to end IoT
architecture.
Six Layers

Layer 1 – Device
One or more MCUs and firmware (sensors and actuators) are connected to the gateway. MPUs are
used as smart devices which would directly communicate with the cloud. As is shown in the
architecture, there would one or more gateways and smart devices may participate in the solution.

Layer 2 – Communication
MQTT is the defacto communication protocol to be used in the solution. As of now Eclipse
Mosquitto has been identified to be used as the message broker between the device layer and the
cloud

Layer 3 – Cloud Services

Data ingestion, analysis and interpretation that generates insights are done in this layer.
 RAW data storage
 Device Management through Digital Twin
 Event Processing
 Batch Proccessing
 Basic and Advanced Analytics
Above all the modules are available in this layer. All these modules are capable of distributed
processing.
When data is received by Kafka, raw data is directly stored in Cassandra (NoSQL). In parallel,
based on the configured rules in the rule engine, Spark stream processor would process the data in
near real time and generates actions for every event that received from the devices. The actions
could be Push notification to the end user, and/or passing control signal back to the respective
device.
Spark batch processing processes the raw data in cassandra and populates the reports database.
The Digital Twin represents the state and operations of a device and takes part in data simulation

Layer 4 – Application/Data Service Layer

Application logic and data would be exposed as micro services.
Layer 5 – Applications
This layer will constitute the visualization applications, business system integration and the
development environments for Rapid application development. The visualization has been planned
to be developed in serverless architecture using nodejs and reactjs.

Layer 6 – Security
The device layer will be provided with physical protections in terms of firmware modification and
tamper proof. In the communication layer, data would be encrypted end to end using SSL, TLS or
X.509 certificates. Data at rest and data at motion would be encrypted. All users, applications and
devices taking part in the solution would go through administration and access management. It has
been planned to use O-Auth2 as the IAM framework.