Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.
- 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.
Forwarding Data to MySQL for Storage
Scenarios
IoTDA can forward data reported by devices to RDS for MySQL for storage. You can use device data for service processing without developing additional code to store data.
In this example, data reported by all devices is forwarded to a MySQL database.
Prerequisites
- You have purchased an IoTDA Enterprise or Standard edition instance.
- You have purchased an RDS for MySQL instance.
Creating a MySQL Database
- Log in to the Huawei Cloud official website, visit RDS for MySQL, and purchase an instance. IoTDA enterprise edition instances support connecting to an RDS for MySQL DB instance through a private network. IoTDA standard edition instances support connecting to an RDS for MySQL DB instance through a public network.
- When you purchase a MySQL instance, design database tables by referring to Data Transfer APIs to enable editing of forwarded data using filter statements. In this example, the default formats in Push a Device Property Reporting Notification are used to store the resource, event, notify_data, and event_time fields in the forwarded data to the resource, event, content, and event_time fields in the database table.
Figure 1 Example of creating a database table
Configuring IoTDA
Using IoTDA, you can create a product model, register a device, and set a data forwarding rule to forward data reported by the device to MySQL.
- Access the IoTDA service page and click Access Console. Click the target instance card.
- In the navigation pane, choose Products. Click Create Product and select the resource space to which the new product will belong.
NOTE:
The product model and device used in this topic are only examples. You can use your own product model and device.
- Click Create Product to create a product using MQTT. Set the parameters and click OK.
Basic Information
Product Name
Enter a value, for example, MQTT_Device.
Protocol Type
Select MQTT.
Data Type
Select JSON.
Industry
Set the parameters as required.
Device Type
- Click here to download a sample product model.
- On the Basic Information tab page, click Import from Local. In the displayed dialog box, load the local product model and click OK.
Figure 2 Product - Uploading a product model
- In the navigation pane, choose Devices > All Devices. Click Register Device, set device registration parameters, and click OK. Save the device ID and secret returned after the registration.
Figure 3 Device - Registering a secret device
Parameter
Description
Resource Space
Select the resource space (created in step 3) to which the product will belong.
Product
Select the product created in step 3.
Node ID
Set this parameter to the IMEI, MAC address, or serial number of the device. If the device is not a physical one, set this parameter to a custom character string that contains letters and digits.
Device Name
Customize the product name.
Device ID
Customize the value. You can leave it empty, then the platform will automatically generate a device ID.
Authentication Type
Select Secret.
Secret
Customize the secret used for device access. If the secret is left blank, the platform automatically generates one.
- In the navigation pane, choose Rules > Data Forwarding, and click Create Rule in the upper left corner.
NOTE:
You can also add a MySQL database as the forwarding target on the details page of a created rule.
- Set the parameters based on the table below. The following parameter values are only examples. You can configure parameters of data forwarding rules by referring to Data Forwarding. After configuring the parameters, click Create Rule.
Parameter
Description
Rule Name
Customize a name, for example, iotda-mysql.
Description
Enter a rule description, for example, forwarding data to MySQL for storage.
Data Source
Select Device property.
Trigger
Device property reported is automatically populated.
Resource Spaces
Select a resource space to which the data source to be forwarded belongs or all resource spaces.
- Click the Set Forwarding Target tab, and then click Add to set a forwarding target.
Parameter
Description
Forwarding Target
Select MySQL (RDS).
Database Instance Address
Enter the IP address (or port number) for connecting the database instance.
Database Name
Enter the name of the destination database in the database instance.
Access Account
Enter the account of the database instance.
Access Password
Enter the password of the database instance.
SSL
Select whether to connect to the database in SSL mode. You are advised to use SSL for connection. If not, security risks may exist during data transmission. To use the SSL mode, configure an SSL connection in the database instance first.
Certificate ID
Truststore certificate, which is used by the client to verify the server certificate. If this parameter is left blank, the default certificate provided by RDS for MySQL is used. For RDS for MySQL instances using custom certificates, upload the custom CA on the Rules > Server Certificates page and complete the binding.
- Click Next. IoTDA will connect to the database during the process.
- Select the target table and configure the mapping between the data to forward and the database table.
- Forwarding Field: JSON key of the data to forwarded.
- Target Field: field in the database table. After a target field is selected, the field type is automatically matched.
Figure 4 Setting MySQL field mapping - Click Enable Rule to activate the configured data forwarding rule.
Verifying the Configurations
An event (for example, device property reporting) triggers data forwarding.
Expected result:
Log in to the RDS for MySQL console and open the target table. Data forwarded to the target fields is displayed in the table.

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