About EnOS Device Connectivity & Management¶
EnOS Device Connectivity & Management(abbr. DCM) helps you quickly and securely connect physical devices to EnOS Cloud and start to transfer data, manage device lifecycle, and map the physical asset structure to the digital world.
Device Connectivity¶
Bi-Directional Connectivity to Devices¶
Device Connectivity & Management enables you to quickly establish bi-directional communication between the device and the cloud:
Data ingestion from device to cloud
Remote control from cloud to device
For the message flow and an overview of the technical components, see Device and Data Connectivity.
Communication Protocols¶
Device Connectivity & Management supports device communication with EnOS Cloud through the following protocols:
For IoT devices capable of maintaining a long connection, the MQTT protocol is supported to meet real-time connection needs.
For devices that cannot maintain a persistent connection due to network limitations, or that need to continuously upload file-type data (e.g., cameras continuously sending video files), the HTTP protocol is supported.
Supported Data Formats¶
Device Connectivity and Management supports the collection and management of structured data (standard JSON format) and unstructured data (file, video, and audio formats).
Device SDKs¶
Simple device-end development is needed to enable the device to communicate with EnOS by following EnOS standard device protocol. EnOS provides SDKs for C, Java, and Python programming languages for the device-end development.
For more information, see Using EnOS Device SDKs for Device Development.
Device Simulators¶
In situations where there are no actual devices available, Device Connectivity & Management provides users the capability to simulate data for testing and debugging purposes. For more information, see Device Simulators or Online Debugging.
Connectivity Solutions¶
Device Connectivity & Management supports various connection schemes and provides solutions to meet the requirements of various scenarios for the heterogeneous network enterprise devices. For more information, see Connection Protocols.
Integration to 3rd-party Systems¶
In addition to supporting direct device connections and gateway forwarding, EnOS also supports obtaining device data from third-party systems or clouds through data integration. Non-IoT system integration support: SQL, MySQL, Redis, GitLab, S3, Blob, MongoDB, SFTP, and PostgreSQL. For more information, see Device Data Integration Service.
Device and Cloud Security¶
Device Connectivity & Management ensures device and cloud security in the areas below.
Device Connection Security
The device needs to be connected to EnOS through the device triple. Each time it connects, the device needs to use the SHA256 to calculate the connection password based on the secret keys.
For devices accessed through the MQTT protocol, supports the secure, two-way authentication based on TLS.
For devices accessed through the HTTP protocol, supports HTTPS as the access scheme.
Device Security Management and Auditing
For connection through proxy gateway devices, EnOS provides topology management. The device can only connect to EnOS through the pre-configured gateway.
Provides a mechanism to detect duplicate connections to a device, to ensure that only one connection to EnOS is established for the same device at any given moment.
Ensures that dynamically activated devices cannot be repeatedly activated.
Provides audit logs for device behaviour.
For more information, see Device Security Schemes.
Device Lifecycle Management¶
Device Connectivity and Management provides comprehensive device lifecycle management, including:
Device identity registration
Device activation
Enabling and disabling devices
Deleting devices
Asset tree management
Statistics for devices and messages
Device firmware over-the-air(OTA) updates
Real-time monitoring
Device dashboard
For more information, see Device Lifecycle Management.
Target Users¶
Device Connectivity & Management primarily serves the following roles:
IoT Engineer: performs the on-site installation (including installing the edge gateway devices and connecting the cables between edge gateways and devices) sets up device connections and debugs the communication between the devices and the cloud.
Device Manager: creates the asset hierarchy (asset tree) and manages assets based on the business case scenarios.
Application Developer: develops applications to acquire device telemetry and configuration information via EnOS APIs and SDKs to meet the requirements of specific business case scenarios.