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.
Yearly/Monthly Billing
If you expect to use resources for a longer period, you can save money with yearly/monthly billing. This section describes the billing rules of yearly/monthly IoTDA.
Scenarios
If you want to ensure resource stability over a certain period of time, yearly/monthly billing is a good choice for the following types of workloads:
- Long-term workloads with stable resource requirements, such as official websites, online malls, and blogs
- Long-term projects, such as scientific research projects and large-scale events
- Workloads with predictable traffic bursts, for example, e-commerce promotions or festivals.
- Workloads with high data security requirements.
Billing Items
The following billing items support yearly/monthly billing.
Billing Item |
Description |
---|---|
Standard instance |
You are billed based on the instance specifications and required duration. |
Billing Method
A yearly/monthly IoTDA resource is billed by the subscription duration. The billing cycle begins when you activate or renew your subscription and ends at 23:59:59 on the expiration date of the following calendar month or year. To determine the expiration date, you can increment the month or year by 1.
Example:
- If you subscribed to a standard instance for one month on March 8, 2023, 15:50:04, the billing cycle is from March 8, 2023, 15:50:04 to April 8, 2023, 23:59:59.
- If you subscribed to a standard instance for one month on February 8, 2023, 15:50:04, the billing cycle is from February 8, 2023, 15:50:04 to March 8, 2023, 23:59:59.
- If you subscribed to a standard instance for one year on February 8, 2024 (leap year), 15:50:04, the billing cycle is from February 8, 2024, 15:50:04 to February 8, 2025, 23:59:59.
Billing Examples
Assume that you subscribed to a standard S1 unit at 15:50:04 on March 8, 2023. If you manually renew the subscription for one month before the subscription expires:
- Billing cycle 1: March 8, 2023, 15:50:04 to April 8, 2023, 23:59:59
- Billing cycle 2: April 9, 2023, 00:00:00 to May 8, 2023, 23:59:59
You need to prepay for each billing cycle. Table 2 list the billing formula.
Resource |
Formula |
Price |
---|---|---|
IoTDA standard instance |
Unit price x Unit quantity x Purchase duration |
Visit Price Calculator. Select Yearly/Monthly for Billing Mode, select Standard for Instance Edition, and select the unit type, quantity, and required duration. The estimated price is displayed in the lower part of the page. |
Impact on Billing After Specifications Change
If the specifications of a yearly/monthly instance no longer meet your needs, you can change the specifications on the console. The system will recalculate the price and either bill or refund you the difference.
- If you upgrade the specifications, you need to pay the difference in price.
- If you downgrade the specifications, Huawei Cloud will refund you the difference.
Assume that you subscribed to one low-frequency unit S1 of the standard instance on April 8, 2023 for one month. You plan to change the specifications to intermediate frequency unit S2 on April 18, 2023, the number of units is 1. The price for the old specifications is 800/month, and that for the new specification is 3,000/month. The calculation formula is as follows:
Price difference for the specifications upgrade = Price for the new specifications × Remaining period - Price for the original specifications × Remaining period
The remaining period in the formula is the number of days remaining in each calendar month divided by the maximum number of days in that month. In this example, the remaining period = 12 (the remaining days in April, excluding the change day)/30 (the maximum number of days in April) + 8 (the remaining days in May)/31 (the maximum number of days in May) = 0.6581. Cost of specification upgrade = 3,000 × 0.6581 - 800 × 0.6581 = 1447.82.
For details, see Pricing of a Changed Specification.
Impact of Expiration
Figure 1 shows the statuses of a yearly/monthly IoTDA resource in each phase. After a resource is purchased, it enters a valid period and runs normally during this period. If the resource is not renewed after it expires, it first enters a grace period and then a retention period.
- Expiration warning: The system will send you a reminder (by email, SMS, or in-app message) 7 days before a yearly/monthly IoTDA resource expires to remind you to renew the subscription.
- Impact of expiration:
- If your yearly/monthly IoTDA resource is not renewed after it expires, it changes to the Expired status and enters a grace period. During the grace period, you can use IoTDA.
- If the yearly/monthly IoTDA resource is not renewed after the grace period ends, its status turns to Frozen and it enters a retention period. You cannot perform any operations on the resource while it is in the retention period.
- After the retention period expires, if the yearly/monthly IoTDA resource is not renewed, the resource will be released, and data cannot be restored
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