Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- 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
Copied.
Device Access Guide
Device Access Mode
The Huawei Cloud IoTDA provides multiple access modes to meet the requirements of device fleets in different access scenarios. You can select a proper development mode based on the device type.
|
Development Mode |
Feature |
Scenario |
Difficulty Level |
|---|---|---|---|
|
Certificated MCU development |
The IoT Device SDK Tiny has been pre-integrated into the main control unit (MCU) and can call methods to connect to the platform. |
Devices need to be quickly put into commercial use, with low R&D costs. Devices are connected to the platform directly, without using gateways. |
|
|
Certificated module development |
The IoT Device SDK Tiny has been pre-integrated into the module and can invoke AT commands to connect to the platform. |
There are few MCU resources. Devices are connected to the platform directly, without using gateways. |
|
|
LiteOS development |
Devices run LiteOS that manages MCU resources. In addition, LiteOS has a built-in IoT Device SDK Tiny that can call functions to connect to the platform. This development mode shortens the device development duration and reduces the development difficulty. |
No operating system is required. Devices are connected to the platform directly, without using gateways. |
|
|
Common development |
The IoT Device SDK Tiny is integrated into the MCU and calls the SDK functions to connect to the platform. This type of call is more convenient than API access. |
There is sufficient time for devices to put into commercial use, and the flash and RAM resources of the MCU meet the conditions for integrating the IoT Device SDK Tiny. |
|
|
OpenCPU development |
Use the MCU capability in the common module, and compile and run device applications on the OpenCPU. |
Devices with a small size have high security requirements and need to be quickly put into commercial use. |
|
|
Gateway development |
The IoT Device SDK is pre-integrated into the CPU or MPU and can call functions to connect to the platform. |
Child devices connected to the platform using gateways. |
|
Device Development Resources
You can connect devices to IoTDA using MQTT, LwM2M/CoAP, and HTTPS, as well as connect devices that use Modbus, OPC UA, and OPC DA through IoT Edge. You can also connect devices to IoTDA by calling APIs or integrating SDKs.
|
Resource Package |
Description |
Download Link |
|---|---|---|
|
IoT Device SDK (Java) |
Devices can connect to the platform by integrating the IoT Device SDK (Java). The demo provides the sample code for calling SDK APIs. For details, see IoT Device SDK (Java). |
|
|
IoT Device SDK (C) |
Devices can connect to the platform by integrating the IoT Device SDK (C). The demo provides the sample code for calling SDK APIs. For details, see IoT Device SDK (C). |
|
|
IoT Device SDK (C#) |
Devices can connect to the platform by integrating the IoT Device SDK (C#). The demo provides the sample code for calling SDK APIs. For details, see IoT Device SDK (C#). |
|
|
IoT Device SDK (Android) |
Devices can connect to the platform by integrating the IoT Device SDK (Android). The demo provides the sample code for calling SDK APIs. For details, see IoT Device SDK (Android). |
|
|
IoT Device SDK (Go) |
Devices can connect to the platform by integrating the IoT Device SDK (Go). The demo provides the code sample for calling the SDK APIs. For details, see IoT Device SDK (Go) User Guide. |
|
|
IoT Device SDK(Python) |
Devices can connect to the platform by integrating the IoT Device SDK (Python). The demo provides the code sample for calling the SDK APIs. For details, see |
|
|
IoT Device SDK Tiny (C) |
Devices can connect to the platform by integrating the IoT Device SDK Tiny (C). The demo provides the sample code for calling SDK APIs. For details, see IoT Device Tiny SDK (C). |
|
|
Native MQTT or MQTTS access example |
Devices can be connected to the platform using the native MQTT or MQTTS protocol. The demo provides the sample code for SSL-encrypted link setup, TCP link setup, data reporting, and topic subscription. |
|
|
Product model template |
Product model templates of typical scenarios are provided. You can customize product models based on the templates. For details, see Developing a Product Model Offline. |
|
|
Codec example |
Demo codec projects are provided for you to perform secondary development. |
|
|
Codec test tool |
The tool is used to check whether the codec developed offline is normal. |
|
|
NB-IoT device simulator |
The tool is used to simulate the access of NB-IoT devices to the platform using LwM2M over CoAP for data reporting and command delivery. For details, see Connecting and Debugging an NB-IoT Device Simulator. |
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
