What's New

1

Agency permission optimization

Scenario-based agency authorization is supported.

Commercial use

Agency Authorization

2

Experience optimization

1. The device details page now displays all services and properties available in the product model data.

2. The issue of excessive buttons on the multi-table interface has been addressed and optimized.

3. When a user is restricted or frozen, the displayed message is clearer and more actionable.

4. A port description has been added for MQTT connection parameters.

Commercial use

/

1

Experience optimization

Functions optimized:

1. Model file examples are added to the product.

2. Millisecond-level message tracing is supported.

Fixed issues:

1. We fixed the issue that only the first 100 SMN topics can be selected when a notification sending action is created for a linkage rule.

Commercial use

/

1

Online debugging upgrade

1. Online debugging supports the search function for message tracing.

2. Online debugging supports message reporting and delivery.

Commercial use

/

2

AMQP Android SDK access

An example for Android SDK access is provided to describe how to forward data to an AMQP queue.

Commercial use

Android SDK Access Example

1

Console upgrade

An intuitive, integrated, reliable, and responsive console is available. You can easily manage instances and devices, monitor exceptions, and implement efficient O&M.

Commercial use

/

2

Experience optimization

1. The instance description supported more character types.

2. The basic edition can be unsubscribed.

3. Up to 5,000 devices can be deleted in batches from the device list.

4. MQTT connection parameters can be obtained from the device list.

5. The creation time is added to the product list.

Commercial use

/

3

Abnormal data forwarding channel

The platform rule engine forwards data to an abnormal channel if the data fails to be forwarded to other Huawei Cloud services or third-party applications.

Commercial use

Abnormal Data Target

1

Device tunnel management

The platform delivers security tunnel information to the device. The device can use the information to establish a WebSocket connection with the platform. You can remotely log in to the device using the secure tunnel on the application side (remote SSH login service), and perform operations such as device configuration update, diagnosis, and O&M change.

Commercial use

Device tunnel management

2

Security tunnel WebSocket interface reference

The platform offers secure tunnels that enable communication between applications and devices. By using the secure tunnel communication protocol, a WebSocket channel can be established to remotely connect to IoT platform devices on the enterprise intranet from an external network.

Commercial use

Security tunnel WebSocket interface reference

3

Custom device domain name

With a custom domain name, you can manage your own server certificates, including the root certificate authority (CA), signature algorithms, and certificate lifecycles.

Commercial use

Custom Device Domain Name

4

Experience optimization

1. The script-based development supported auto saving.

2. The console supported batch operations.

3. The device version number can be displayed when a device is selected for software/firmware upgrade.

4. The display of operation result feedback is optimized.

5. The Chinese display of message tracing is optimized.

6. The message tracing export file is optimized.

Commercial use

/

1

Device certificates

For a device using MQTTS X.509 certificates, when it connects to the platform for the first time, IoTDA utilizes the uploaded and verified device CA certificate to authenticate the device certificate. After the authentication is successful, the platform automatically saves the device certificate. You can check and disable device certificates, and receive expiration warnings.

Commercial use

Device Certificates

2

Custom functions for device authentication

Before connecting a device to the platform, you can use the application to configure custom authentication information on the console, and then configure custom authentication functions by using FunctionGraph. When the device connects to IoT platform, the platform obtains parameters such as the device ID and custom authentication function name, and sends an authentication request to FunctionGraph. The user implements the authentication logic to complete access authentication.

Commercial use

MQTT(S) Custom Authentication

3

Experience optimization

1. Enterprise projects can be searched.

2. Virtual device names can be customized.

3. The online debugging page is optimized.

Commercial use

/

1

M2M communications

You can create a rule to forward messages reported by devices to other devices, enabling message communications between devices.

Commercial use

M2M Communications

2

Experience optimization

1. The specification calculation capability is added for the standard edition.

2. Enterprise projects can be selected for run logs.

3. The function of saving device information is optimized.

Commercial use

/

3

Custom templates for device authentication

You can use a custom authentication template to orchestrate internal functions provided by the platform and flexibly customize triplet parameters ClientId, Username, and Password for MQTT device authentication.

Commercial use

MQTT(S) Custom Template Authentication

4

Python\Node.js\Go\C# language demos for MQTT subscription push

The Python\Node.js\Go\C# language demos are added for MQTT subscription push to receive messages subscribed by the server.

Commercial use

Python Demo

GO Demo

Node.js Demo

C# Demo

1

Custom topic communications

You can customize topics for publishing and subscription. Usage and scenarios of topics starting with $oc and not starting with $oc are described.

Commercial use

Custom topic communications

1

Pushing metric data to DMS for Kafka

IoTDA provides various data reports, which you can integrate into your O&M system. You can use the subscription function of Application Operations Management (AOM) to push metric data from IoTDA to DMS for Kafka, and then consume and display the data.

Commercial use

Pushing Metric Data to DMS for Kafka

2

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 Go SDK to connect to IoTDA and receive subscribed messages from the platform based on AMQP.

Commercial use

Go SDK Access Example

2

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

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

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

2

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