Device Protocol Selection


EnOS supports device access through the following protocols:

  • MQTT

  • HTTP

You can select the appropriate protocol to connect devices to EnOS Cloud based on device characteristics and business requirements.

Device Characteristics


First, you need to determine whether the device meets the following two conditions:

  • Supports TCP/UDP communication

  • Can support the data format of EnOS device access protocols through firmware upgrades

If the device meets both conditions, it can connect to EnOS either directly or via a gateway.

If the device does not meet either condition and is already connected to another system or cloud platform, it can be integrated into EnOS through device data integration. For more information, see EnOS Device Data Integration Service.

Protocol Capabilities


You can use the table below to compare the capabilities of each protocol and choose the appropriate access protocol.

Function

MQTT

HTTP

Static Activation

Supported

Supported

Dynamic Activation

Supported

Not Supported

Certificate-Based Bidirectional Authentication

Supported

Only supports certificate-based unidirectional authentication (EnOS Cloud authenticates the device)

Data Security

Optional Transport Layer Security (TLS) protocol transmission with certificates

Optional TLS protocol transmission with certificates

Reporting Device Tags, Attributes, and Measurement Points

Supported

Supported

File-Type Data Reporting

Not Supported

Supported

Batch Reporting of Measurement Points and Offline Measurement Point Data

Supported

Not Supported

Setting Measurement Points and Service Invocation

Supported

Not Supported

Device Registration, Sub-Device Online/Offline Status, Device Lifecycle Management

Supported

Not Supported

Firmware OTA Updates

Supported

Not Supported