هذه الصفحة غير متوفرة حاليًا بلغتك المحلية. نحن نعمل جاهدين على إضافة المزيد من اللغات. شاكرين تفهمك ودعمك المستمر لنا.
- 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.
Buying an Instance
Procedure
- In the navigation pane, choose IoTDA Instances, click Buy Instance, and select Enterprise.
- Enter configuration information about the instance. The system automatically calculates the fee based on Instance Specifications and Required Duration.
Parameter
Description
Billing Mode
Billing mode of an instance. The value is fixed at Yearly/Monthly.
Region
Region where IoTDA is deployed. Currently, CN North-Beijing4, CN East-Shanghai1, and CN South-Guangzhou are supported.NOTE:
Select a nearby region to ensure the lowest latency possible.
Network
Select an available VPC and subnet.
Create a VPC on the VPC console.
Security Group
Select a security group. Create a security group on the VPC console.
Public Network Access
Set this parameter based on your requirements. If configured, devices can access the platform via the Internet.
Private Network Access
- If you select Create Provide Network Access Point, a VPC endpoint is automatically purchased and an access address is automatically allocated.
- If it is not selected, private network ingestion is still required. You can purchase VPC endpoints for connection.
Access Ports
You can configure access ports or use the default ports. The following ports are provided:
Application access: HTTPS (443) and AMQPS (5671)
Device access: CoAP (5683), CoAPS (5684), MQTT (1883), MQTTS (8883), and HTTPS (443)
Instance Version
Select Enterprise.
Enterprise Project
This parameter is displayed only for enterprise users who have enabled the enterprise project function. Enterprise projects let you manage cloud resources and users by project. For details, see Enterprise Center Overview.
Tags
Tags are key-value pairs, which are used to identify, classify, and search for instances. Instance tags are used to filter and manage instances only. For details, see Instance Tag Management.
Instance Name
Set a name for easy management. The value can contain a maximum of 64 characters consisting of letters, numbers, underscores (_), and hyphens (-).
Cryptographic Algorithm
General cryptographic algorithms (such as RSA and SHA-256) and SM series commercial cryptographic algorithms (Chinese cryptographic algorithms such as SM2, SM3, and SM4) are available.
Description
Provide a description for the instance, which can be a brief description based on the instance user and usage.
Required Duration
Select a duration as required.
You can select Auto-renew so the instance will be automatically renewed when it expires.
- Click Buy.
- Confirm the specifications and click Pay.
- On the payment page, select a payment method and click Pay.
Buying a Standard Edition Instance
The standard instance provides configurable instance specifications. You can purchase more economical instances based on your service model.
Before the purchase, browse the overall process for a more efficient operation.
Procedure
- In the navigation pane, choose IoTDA Instances, click Buy Instance, and select Standard.
- Enter configuration information about the instance. The system automatically calculates the fee based on instance specifications and the pay-per-use mode.
Parameter
Description
Billing Mode
Billing mode of an instance. Currently, only Pay-per-use is supported..
Region
Region where IoTDA is available. Currently, AP-Bangkok, AP-Singapore, AF-Johannesburg, LA-Sao Paulo1, and CN-Hong Kong are supported.NOTE:
Select a nearby region to ensure the lowest latency possible.
Specifications
SUF unit with free specifications, SU1 unit with small specifications, SU2 unit with medium specifications, SU3 unit with large specifications, and SU4 unit with ultra-large specifications are available. You can obtain the recommended instance specifications based on the required upstream and downstream TPS.
NOTE:
- Instance specifications of Standard Edition = Number of units in the instance x Specifications of each unit
- A Standard Edition instance can contain multiple units of the same type. The maximum number of units in a single instance is 100, and the maximum TPS of upstream and downstream messages of a single instance is 100,000. For example, even if an instance contains 100 S3 units, the maximum TPS of the instance is 100,000.
- You can increase the number of units in the instance online, for example, upgrading a standard instance from three SU1 units to five SU2 units.
- An instance cannot contain different types of units, for example, M SU1 units and N SU2 units.
Enterprise Project
This parameter is displayed only for enterprise users who have enabled the enterprise project function. Enterprise projects let you manage cloud resources and users by project. For details, see Enterprise Center Overview.
Tags
Tags are key-value pairs, which are used to identify, classify, and search for instances. Instance tags are used to filter and manage instances only. For details, see Instance Tag Management.
Instance Name
Enter a name for easy management. The value can contain a maximum of 64 characters consisting of letters, numbers, underscores (_), and hyphens (-).
Description
Provide a description for the instance, which can be a brief description based on the instance user and usage.
- Click Buy.
- Confirm the specifications and click Submit.
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