Domorela's Blog: Intranet of Things Private Cloud Service deployment (I)

As said in our first article speaking about Intranet of Things, IoT is constructed merging ICT technologies. After deployment of the TCP/IP next step is deployment of Private Cloud Service that publishes a WWW service.

In order to deploy a Private Cloud, first thing we must do is to pay attention to the size of the environment we are facing: small, medium or large.

A Private Cloud Service publishes a WWW service. In other words, publishes a web that serves as User Interface or Management Portal and gives the possibility to manage the Intranet of Things Network. Deployment of such a service involves several components:

1. Core components:
   1. Database: stores all the data received, and metadata generated, by engine
   2. Engine: processes data received from other components and generates metadata
   3. Managemen Portal: implements managing capabilities for users
   4. Communications Gateway: provides M2M and H2M (human to machine) communications
2. Edge components:
   1. Database: stores data from end devices
   2. Engine: processes data from end devices
   3. Communications Gateway: provides M2M communications, may provide H2M communications
3. End components:
   1. Engine: processes local data
   2. Communications Gateway: provides M2M communications, may provide H2M communications

Core components can be communicated with edge and/or end components, depending of size and needs of the environment. Edge usually gathers data from end devices and provides them to core, but can only serve as a link between the Core and End components to exchange data directly. End components can be IP compatible or not, if not then the Edge must include an IP-link between End and the rest of Edge and Core components.

There are many strategies and products to implement all of the above. Below table briefly explain how can be combined in order to achieve a deployment of Intranet of Things with an x86 computer and IoT software bundle solution compared to a deployment with Domorela in small, medium and large environments.

The advantages of using Domorela to implement Intranet of Things are that Domorela is providing Core and Edge components in a single device, also that can directly communicate with non-IP segments. Thus can be used to manage non-IP end components and/or link them to the rest of IP compatible components.

Domorela includes all components embedded in his internal application, so it isn't necessary to install them separately in order to put into service a Domorela unit. This leads to a faster and cheaper deployment of the IoT insfrastructure, allowing to focus on the management part of the project.

(1) Modbus hardware support already included, software module will be supported in future version of Domorela

(2) one edge gateway for each remote IoT site network attached to core IoT network