หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
- 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 DIS
Scenarios
Forwarding data to Data Ingestion Service (DIS) allows you to collect, process, and distribute real-time streaming data efficiently. DIS interconnects with multiple third-party data collection tools and provides cloud service connectors, agents, and SDKs. You can also dump data to other cloud services for subsequent data processing like data storage and analysis.
Purchasing a DIS Stream (Example: Forwarding Data to DIS and Dumping Data to OBS)
- Log in to Huawei Cloud and access the Object Storage Service (OBS) console.
- Click Create Bucket, configure the parameters as required, and click Create Now.
- In the bucket list, click the created bucket. The Objects page is displayed. Click Create Folder and enter a folder name as prompted.
- Log in to Huawei Cloud and access Data Ingestion Service (DIS).
- Click Access Console to go to the DIS console.
- Click Buy Stream in the upper right corner, configure parameters as required, and click Next.
Figure 1 Buying a DIS stream
- In the navigation pane, choose Stream Management and click a purchased stream. Click the Dump Tasks tab. Click Create Dump Task. Set Dump Destination to OBS, Dump Bucket to the bucket created in step 2, and File Directory to the folder created in step 3. Click Create Now.
Figure 2 Selecting a streamFigure 3 Accessing the dump task tabFigure 4 Configuring a dump task
Configuring IoTDA
You can configure data forwarding rules in IoTDA to forward data reported by devices to DIS.
- Go to the IoTDA service page and click Access Console. Click the target instance card.
- In the navigation pane, choose Rules > Data Forwarding, and click Create Rule in the upper left corner.
- Configure the parameters based on the following table. The following parameter values are only examples. You can configure the parameters by referring to Data Forwarding Overview and click Create Rule.
Table 1 Rule parameters Parameter
Description
Rule Name
Customize a name, for example, iotda-dis.
Description
Enter a rule description, for example, forwarding data to DIS.
Data Source
Select Device property.
Trigger
Device property reported is automatically configured.
Resource Space
Select All resource spaces.
- Click the Set Forwarding Target tab, click Add to set a forwarding target, and click OK.
Table 2 Forwarding target parameters Parameter
Description
Forwarding Target
Choose Data Ingestion Service (DIS).
Region
Currently, you can only forward data to DIS in the same region. If IoTDA is not authorized to access the service in this region, configure cloud service access authorization as prompted.
Stream Homing
Select either of the in-house stream or the stream Delegated by others.
Stream
Select a stream.
Figure 5 Creating a forwarding target - to DIS - Click Enable Rule to activate the configured data forwarding rule.
Verifying Configurations
- You can use a registered physical device to access the platform and enable the device to report data.
- You can also use a simulator to simulate a device to report data. For details, see Developing an MQTT-based Smart Street Light Online.
Expected result:
Log in to the OBS console, click the bucket created in 2, and click the folder created in 3 to view the latest data forwarded from DIS to OBS.

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