Technical capabilities of an edge computing solution: Bosch

#Discussion(IoTStack) [ via IoTForIndiaGroup ]

Features of an edge computing solution

A key purpose of an edge gateway is to enable connectivity with the sensors and actuators. There are many industry protocols that facilitate different styles of device communication. An edge solution should support the most common protocols. For example, these include Z-Wave, ZigBee, KNX, Bluetooth LE, HomeConnect, Modbus, ONVIF, EnOcean, BACnet, OPC UA, LoRa, Siemens S7.

The ability to locally run applications is the key to enable local data processing. Depending on the domain, example applications include analytics algorithms, threshold-based notifications and alarms, diagnostic and monitoring applications, and any other custom software code that is executed on the gateway.
In addition to local processing, a gateway should have the ability to store data locally. This is key to allowing a gateway to run autonomously. The combination of local computation and local storage should allow the gateway to operate in a disconnected mode.

Security needs to be integrated into the edge solution. An edge solution should allow for permission based access control, secure encrypted communication, certificate management and integration into existing security solutions.
Edge gateways require a way to remotely manage and access each individual gateway. The remote management features should allow to remotely start, stop, configure, and update a gateway and the devices attached to it. An open API should allow remote applications to communicate with the gateway via REST, WebSockets, or JSON-RPC.

Finally, the software for an edge solution should be portable to different hardware platforms. You don’t want to be in a situation where you are locked in to a specific vendor’s hardware and software solution.

Read More..