- What's New
- Product Bulletin
- Service Overview
- Billing
-
Getting Started
-
Quick Device Access - Property Reporting and Command Receiving
- Subscribing to IoTDA
- Connecting a Smart Smoke Detector to the Platform (Quick Usage)
- Registering a Simulated Smart Street Light Device
- Using MQTT.fx to Simulate Communication Between the Smart Street Light and the Platform
- Using a Virtual Smart Street Light to Communicate with the Platform (Java SDK)
- Using a Virtual Smart Street Light to Communicate with the Platform (C SDK)
- Quick Device Access - Message Sending and Receiving
- Quick Application Access
-
Quick Device Access - Property Reporting and Command Receiving
-
User Guide
- Overview
- IoTDA Instances
- Resource Spaces
- Device Access
- Message Communications
- Device Management
-
Rules
- Overview
- Data Forwarding Process
- SQL Statements
- Connectivity Tests
- Data Forwarding to Huawei Cloud Services
- Data Forwarding to Third-Party Applications
- Data Forwarding Channel Details
- Data Forwarding Stack Policies
- Data Forwarding Flow Control Policies
- Abnormal Data Target
- Device Linkage
- Monitoring and O&M
- Granting Permissions Using IAM
-
Best Practices
- Introduction
-
Device Access
- Developing an MQTT-based Simulated Smart Street Light Online
- Developing a Smart Street Light Using NB-IoT BearPi
- Developing a Smart Smoke Detector Using NB-IoT BearPi
- Connecting and Debugging an NB-IoT Smart Street Light Using a Simulator
- Developing a Protocol Conversion Gateway for Access of Generic-Protocol Devices
- Connecting a Device That Uses the X.509 Certificate Based on MQTT.fx
- Connecting to IoTDA Based on the BearPi-HM_Nano Development Board and OpenHarmony 3.0
- Testing MQTT Performance Using JMeter
- Device Management
- Data Forwarding
- Device Linkage
-
Developer Guide
- Before You Start
- Obtaining Resources
- Product Development
- Development on the Device Side
- Development on the Application Side
-
API Reference
-
API Reference on the Application Side
- Before You Start
- Calling APIs
- API Overview
-
API
- Product Management
- Device Management
- Device Message
- Device Command APIs
- Device Property
- AMQP Queue Management
- Access Credential Management
- Data Forwarding Rule Management
-
Transition Data
- Push a Device Status Change Notification
- Push a Device Property Reporting Notification
- Push a Device Message Status Change Notification
- Push a Batch Task Status Change Notification
- Push a Device Message Reporting Notification
- Push a Device Addition Notification
- Push a Device Update Notification
- Push a Device Deletion Notification
- Push a Product Addition Notification
- Push a Product Update Notification
- Push a Product Deletion Notification
- Push an Asynchronous Device Command Status Change Notification
- Rule Management
- Device Shadow
- Group Management
- Tag Management
- Instance Management
- Resource Space Management
- Batch Task
- Device CA Certificate Management
- OTA Upgrade Package Management
- Message Broadcasting
- Device Tunnel Management
- Stack policy management
- Flow control policy management
- Device Proxy
- Device Policy Management
- Bridge Management
- Pre-provisioning Template Management
- Custom Authentication
- Codec Function Management
- Permissions and Supported Actions
- Examples
- Appendix
-
MQTT or MQTTS API Reference on the Device Side
- Before You Start
- Communication Modes
- Topics
- Device Connection Authentication
- Device Commands
- Device Messages
- Device Properties
-
Gateway and Child Device Management
- Platform Notifying a Gateway of New Child Device Connection
- Platform Notifying a Gateway of Child Device Deletion
- Gateway Synchronizing Child Device Information
- Gateway Updating Child Device Status
- Responding to a Request for Updating Child Device Statuses
- Gateway Requesting for Adding Child Devices
- Platform Responding to a Request for Adding Child Devices
- Gateway Requesting for Deleting Child Devices
- Platform Responding to a Request for Deleting Child Devices
- Software and Firmware Upgrade
- File Upload and Download
- Device Time Synchronization
- Device Reporting Information
- Device Log Collection
- Remote Configuration
- Device Tunnel Management
- HTTPS API Reference on the Device Side
- LwM2M API Reference on the Device Side
- Security Tunnel WebSocket API Reference
- Module AT Command Reference
- Change History
-
API Reference on the Application Side
- SDK Reference
-
FAQs
- Top FAQs
-
Solution Consulting
- In What Scenarios Can the IoT Platform Be Applied?
- What Are the Changes Brought by the Integration of IoT Device Management and IoTDA?
- Can I Enable IoTDA for IAM Users or Sub-Projects?
- Which Regions of Huawei Cloud Are Supported by the IoT Platform?
- Does Huawei Provide Modules, Hardware Devices, and Application Software?
- What Should I Do If I Want to Call an API But Have No Permissions to Do So as an IAM User? (Is It Edition-specific?)
- Why Was I Prompted to Grant Security Administrator Permissions When I Create a Rule or Set Resource File Storage?
- Which Resource Space Will Be Set As Default on the IoT Platform?
- How Does IoTDA Obtain Device Data?
- Is There Any Limitation on the Number of Resource Spaces and Devices I Can Add on the IoT Platform?
- Does the IoTDA Support Device Registration in Batches?
- Are There Any Limitations on the Use of the IoT Platform?
- What DTLS Encryption Algorithms Are Supported by the IoT Platform?
- Does the IoT Platform Support Conversion Between Big Endian and Little Endian for Binary Data?
- What Is NB-IoT?
- What Are the Components of the IoT Platform and What Hardware Architectures Does It Support?
- How Do I Obtain the Platform Access Address?
- Device Integration
- IoT Device SDKs
- LwM2M/CoAP Device Access
- MQTT-based Device Access
- Products Models
- Message Communications
- Subscription and Push
- Codecs
- OTA Upgrades
- Application Integration
- General Reference
Show all
Copied.
Overview
Huawei Cloud IoT Device Access (IoTDA) allows you to connect your physical devices to the cloud, where you can collect device data and deliver commands to devices for remote control. It can also work with other Huawei Cloud services to help you quickly develop IoT solutions.
A complete IoT solution consists of the IoT platform, devices, and applications.
- The IoT platform is located between applications and devices. It harmonizes differences between device interfaces to enable quick device access. It provides robust capabilities to help you develop diverse IoT solutions.
- Devices can access the platform via fixed broadband (FBB), 2G/3G/4G/5G, Narrowband Internet of Things (NB-IoT), and Wi-Fi networks. They can report service data to the platform using mainstream protocols or industry protocols, such as Message Queuing Telemetry Transport (MQTT), Lightweight Machine-to-Machine (LwM2M) over Constrained Application Protocol (CoAP), and Hypertext Transfer Protocol Secure (HTTPS). Devices can also receive commands from the platform.
- Applications call application programming interfaces (APIs) provided by the platform to implement services such as data collection, command delivery, and device management.
![Click to enlarge](https://support.huaweicloud.com/intl/en-us/productdesc-iothub/figure/en-us_image_0000001130147031.png)
Features
Devices can connect to the platform directly or through industrial gateways or home gateways. The platform supports multi-network access, multi-protocol access, and serialized Agent access, preventing issues caused by complex, diversified, and fragmented device access. It also provides comprehensive device management capabilities, simplifies management of device fleets, and improves management efficiency. The following table describes the IoTDA functions.
Category |
Function |
Description |
---|---|---|
Device access |
Native protocol access |
You can connect devices to the platform using MQTT, CoAP, LwM2M, and HTTPS protocols. |
Serial device SDKs |
IoT Device SDK and IoT Device SDK Tiny in languages such as C and Java are supported. For details, see Introduction to IoT Device SDKs. |
|
Industry protocol access |
You can connect devices to the platform through edge gateways using Modbus and OPC Unified Architecture (OPC UA) and using industry protocols based on plug-ins. |
|
Device access authentication |
Authentication modes such as one-device-one-secret and X.509 certificates are supported. |
|
- |
- |
|
Device management |
Device lifecycle management |
You can add, delete, modify, and query devices, manage device status, freeze and unfreeze devices, and manage child devices. |
Groups and tags |
You can group devices or add tags to them. For details, see Groups. |
|
Product models |
You can define a product model (profile) for devices. For details, see Product Model Definition. |
|
Device shadows |
You can configure and query device shadows. For details, see Device Shadow. |
|
OTA upgrade |
You can upgrade device software and firmware. For details, see OTA Upgrade. |
|
Device file upload |
Devices can upload files to OBS and request files from the cloud. For details, see File Uploads. |
|
Batch device operations |
You can perform batch operations on devices, including device registration, software/firmware upgrades, and command delivery. For details, see Create a Batch Task. |
|
Message communications |
Bidirectional transparent transmission |
Device messages can be pushed to applications using HTTP and AMQP. Applications can deliver messages to devices asynchronously. |
Product model topic communications |
Applications and devices communicate with each other based on the properties, commands, and events defined in the product model in a decoupled mode. |
|
Custom topic communications |
You can customize topics for bidirectional message communications. |
|
Data parsing and conversion |
You can develop codecs online to parse and convert device data. |
|
Command delivery |
Commands can be delivered to online devices in synchronous mode. In the NB-IoT scenario, commands can be delivered in asynchronous mode. For details, see Command Delivery. |
|
Rules |
Data forwarding |
Data can be forwarded to Huawei Cloud Kafka, Object Storage Service (OBS), GaussDB, Data Ingestion Service (DIS), Distributed Message Service (DMS), and ROMA Connect. For details, see Rules. |
Device linkage |
You can create rules for device linkage control. For details, see Rules. |
|
Data forwarding |
The platform can forward data reported by devices to applications through HTTP or AMQP. |
|
Monitoring and O&M |
Logging |
The console provides message tracing, integrates with Log Tank Service (LTS) for log analysis, and integrates with Cloud Trace Service (CTS) for log audit. For details, see Monitoring and O&M. |
Alarm reporting |
The platform provides notifications and management of system alarms (such as threshold alarms) and alarms triggered by device rules by integrating with Application Operations Management (AOM). For details, see Alarms. |
|
Metric monitoring |
The platform provides monitoring reports of tenant-level service metrics (such as device status, commands, subscription and push, and message transfer) by integrating with AOM. For details, see Reports. |
Security and Data Protection
IoTDA established an end-to-end trustworthy security system. It is graded level-4 of China's Multi-Level Protection Scheme 2.0 and obtains international security certifications such as ISO27001, ISO27017, ISO27018, and CSA STAR. It complies with European Union's General Data Protection Regulations (GDPR).
- Device security: It provides a one-device-one-secret authentication mechanism to prevent unauthorized access and supports device security check.
- Data transmission: Secure transmission channels are provided based on Transport Layer Security (TLS), Datagram Transport Layer Security (DTLS), and DTLS+.
- Platform security: Threat defense is performed on the entire Huawei Cloud. Huawei Cloud security service products or components and security D&R department are fully leveraged to build a comprehensive security defense system that covers security analysis, design, coding, testing, and defense.
- Data protection: It complies with GDPR.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot