หน้านี้ยังไม่พร้อมใช้งานในภาษาท้องถิ่นของคุณ เรากำลังพยายามอย่างหนักเพื่อเพิ่มเวอร์ชันภาษาอื่น ๆ เพิ่มเติม ขอบคุณสำหรับการสนับสนุนเสมอมา
- 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.
Limitations
The following table lists the technical specifications of IoTDA. If the specifications cannot meet your service requirements, submit a service ticket to describe your requirements.
Category |
Object |
Description |
Limit |
---|---|---|---|
Instance management |
Standard edition instance |
Number of units purchased for a standard instance (see Specifications of Standard Edition) |
100 |
Resource space management |
Number of resource spaces supported by an instance |
10 |
|
Device access |
MQTT |
MQTT protocol standard |
Supported: MQTT v3.1, v3.1.1, and v5.0; not supported: QoS 2, and will, and retained messages |
Security levels supported by MQTT |
TLS 1.1, TLS 1.2, and TLS 1.3 |
||
Heartbeat interval of MQTT connections (see Establishing a Connection) |
Range: 30s to 1200s; recommended: 120s (If the heartbeat interval is not within the range, the server will reject the connection request.) |
||
Maximum timeout interval = Heartbeat interval x 1.5 (If no device message is received within the maximum timeout interval, the server automatically disconnects from the device.) |
|||
Number of connections established between a device and IoTDA |
1 |
||
Length of a custom MQTT topic |
128 bytes |
||
Size of a message reported by an MQTT device |
1 MB (A message larger than this size is rejected.) |
||
Number of subscriptions for an MQTT connection |
50 |
||
Bandwidth of an MQTT connection |
1 Mbit/s |
||
Number of upstream messages per second for an MQTT connection |
50 |
||
Number of connection requests created per second for an instance |
|||
Number of upstream requests for an instance per second on the device side (assuming that the average payload of a message is 512 bytes) |
|||
CoAP/LwM2M |
CoAP version |
RFC 7252 standard 3 |
|
LwM2M version |
V1.0.2 |
||
Transport layer protocol |
User Datagram Protocol (UDP) |
||
Security level supported by CoAP |
DTLS v1.2 |
||
Size of a CoAP message packet |
1 KB |
||
Number of messages per minute for a device |
300 |
||
HTTP |
HTTP versions |
HTTP 1.0 and HTTP 1.1 |
|
TLS versions |
TLS 1.1 and TLS 1.2 |
||
Size of a message body |
1 MB |
||
Device management |
Product |
Number of products in a resource space |
1,000 |
Size of the service capability JSON file in a product |
500 KB |
||
Number of services in a product |
500 |
||
Number of properties, events, or commands in a service capability |
500 |
||
Custom topic |
Number of custom topics for a product |
50 |
|
Number of devices in a standard instance |
Number of devices registered for a standard edition (SU1, SU2, SU3, and SU4) |
2,000,000 (If you want to increase the limit, submit a service ticket.) |
|
Number of devices registered for an SUF |
1,000 |
||
Device |
Number of child devices added to a gateway |
50,000 |
|
Depth of the gateway structure |
2 levels |
||
Device tag |
Number of tags added to a device |
10 |
|
Group |
Depth of a group |
5 levels |
|
Number of groups in a resource space |
1,000 |
||
Number of devices in a group |
20,000 |
||
Number of groups that a device can be added to |
10 |
||
Batch task |
Number of devices registered at a time |
100,000 |
|
Codec |
Number of codecs allowed in a product |
1 |
|
Size of the codec package uploaded offline |
4 MB |
||
Length of the codec script |
1 MB |
||
Timeout interval for a codec invoking request |
5s |
||
Device linkage rule |
Number of rules added for an instance |
Basic/Standard edition: 20 |
|
Enterprise edition: 200 |
|||
Number of actions supported by a rule |
10 |
||
Number of rule actions executed by devices per second for an instance |
Basic/Standard edition: 10 |
||
Enterprise edition: 100 |
|||
Number of waiting tasks for an instance |
Basic/Standard edition: 100 |
||
Enterprise edition: 1,000 |
|||
Batch task |
Number of batch tasks concurrently processed in a resource space |
10 |
|
Size of a batch task file |
2 MB |
||
Number of lines in a batch task file |
100,000 |
||
Number of batch task files supported by an instance |
10 |
||
OTA upgrade |
Size of an upgrade package |
Package uploaded to IoTDA: 20 MB; package uploaded to OBS: no limit |
|
Number of upgrade packages uploaded to a resource space |
200 |
||
Size of a file uploaded to a resource space |
File uploaded to IoTDA: 500 MB; file uploaded to OBS: no limit |
||
Message communications |
Synchronous command |
Response time of a device to a synchronous command |
20 seconds |
Device message |
Aging time of a message delivered to a device |
24 hours |
|
Size of a message delivered to a device |
256 KB |
||
Number of cached messages to be delivered to a device |
20 |
||
Device property |
Number of child devices of which properties can be reported by a gateway at a time |
100 |
|
Asynchronous command |
Aging time of an asynchronous command delivered to a device |
48 hours |
|
Size of an asynchronous command delivered to a device |
256 KB |
||
Number of cached asynchronous commands delivered to a device |
20 |
||
Message forwarding |
Forwarding rule and action |
Number of rules configured for an instance |
100 |
Number of actions supported by a rule |
10 |
||
Length of the select parameter in a forwarding rule |
0.5 KB |
||
Length of the where parameter in a forwarding rule |
0.5 KB |
||
Cache policy for message forwarding |
Message cache size |
1 GB |
|
Message cache duration |
24 hours |
||
AMQP |
AMQP version |
AMQP 1.0 |
|
TLS version |
TLS 1.2 |
||
Number of queues configured for an instance |
100 |
||
Number of queues listened on for a connection |
10 |
||
Number of connections allowed in an instance |
32 |
||
Flow control and stack policies |
Number of data forwarding stack policies |
1 |
|
Number of data forwarding flow control policies |
4 |
||
Certificate management |
Certificate configuration |
Number of device CA certificates supported by an instance. |
100 |
Number of application CA certificates supported by an instance. |
10 |
Application API limitations:
Unless otherwise specified, an API can be called up to 100 times per second for an account (standard edition).
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