What's New

1

Automatic device registration

You can set a self-registration template, with which the device can connect to the platform without registering on the platform in advance. The platform parses the template content based on the device connection information and automatically registers the settings.

Commercial use

Device Self-Registration

1

Stacked forwarding data clearance

When the rule engine forwards messages to a third-party application, if the application cannot process the data in real time, the data will be stacked on the platform. You can clear the data stacked in the forwarding channel for timely processing.

Commercial use

Data Forwarding Channel Details

1

SMN notification templates for linkage rules

When setting a device linkage rule and selecting notification sending as the rule action, you can use the template defined by Simple Message Notification (SMN).

Commercial use

Cloud Rules

1

Authentication credential switchover

You need to update a device access credential in some scenarios, for example, when an X.509 certificate is about to expire. IoTDA provides master/sub fingerprints and secrets to prevent device authentication failure and service interruption during credential update and resetting. For example, when you add a new certificate fingerprint, the platform sets the fingerprint as a backup (sub fingerprint). In this way, the corresponding device can use both the old certificate (if not updated on the device side timely) and the new certificate to connect to the platform smoothly.

Commercial use

Authentication Credentials

1

M2M communications

IoTDA supports MQTT-based M2M communications among devices.

Commercial use

M2M Communications

1

Message Broadcasting

This API is used by an application to broadcast a message to all online devices that subscribe to a specified topic.

Commercial use

Broadcasting a Message

1

Remote Device Configuration

The platform allows you to perform remote configuration. You can remotely update device configuration items such as system and running parameters without interrupting device running.

Commercial use

Remote Device Configuration

1

Restrictions on device shadow specifications

Added limitations on device shadow specifications to the Message communications category.

Commercial use

Limitations

1

Monitoring and O&M

IoTDA allows you to remotely log in to devices from the console over the Secure Shell Protocol (SSH). You can enter commands supported by devices to debug functions and locate faults. This facilitates device management and remote O&M.

Commercial use

Remote Login

1

AMQP subscription/push

You can use a Python 3 SDK to connect to IoTDA and receive subscribed messages from the platform based on AMQP.

Commercial use

Python SDK Access Example

2

AMQP subscription/push

You can use a Go SDK to connect to IoTDA and receive subscribed messages from the platform based on AMQP.

Commercial use

Go SDK Access Example

3

Device-side rules

Cloud rules are parsed and executed on the cloud. IoTDA determines whether triggering conditions are met and triggers corresponding device linkage actions. Device-side rules are device linkage rules delivered to devices, where the device-side rule engine parses and executes the rules. Device-side rules can still run on devices when the network is interrupted or devices cannot communicate with the platform.

Commercial use

Device-side rules

1

Rules

If the forwarding target (such as a third-party application server) cannot process data forwarded by IoTDA in a timely manner due to insufficient performance, unprocessed data will be stacked (cached) on IoTDA. By default, the maximum stack (cache) size of data to forward for a single forwarding rule is 1 GB, and the maximum stack duration is 24 hours. If the maximum stack size or stack duration is exceeded, the earliest unprocessed data will be discarded to meet the stack size and duration requirements.

Commercial use

Data Forwarding Flow Control Policies

2

Rules

You can create flow control policies in different dimensions on IoTDA based on your service scenarios and performance of the forwarding target (such as a third-party application server) to control data forwarding flows.

Commercial use

Data Forwarding Stack Policies