Esta página ainda não está disponível no idioma selecionado. Estamos trabalhando para adicionar mais opções de idiomas. Agradecemos sua compreensão.
- 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.
Bills
To learn about your fees, go to the bills page, and check the transactions and detailed bills.
Bill Generation
After yearly/monthly resources are paid, a bill is reported to the billing system for settlement.
The usage of pay-per-use resources is reported to the billing system at a fixed interval. Pay-per-use IoTDA resources are settled by day.
You are not billed immediately after a record is generated. On the Billing Center > Billing > Transactions and Detailed Bills > Transaction Bills page, Expenditure Time indicates the time when a pay-per-use product is used.
Viewing Bills of a Specific Resource
Example 1: Use the resource ID to search for the bill. The resource ID is the same as that in the bill.
- Log in to the console, choose IoT > IoTDA Device Access in the navigation pane. Go to the IoTDA instance list page and go to the details page of the target instance.
- Copy the resource ID as shown in the figure.
Figure 1 IoTDA instance - Obtaining the resource ID
- On the top menu bar, choose Billing > Bills. The Bills page is displayed.
- Choose Transactions and Detailed Bills > Bill Details. On the displayed page, select Resource ID as the filter condition, paste the resource ID copied in 2, and search for the bill of the resource.
Figure 2 Querying resource bills
By default, bill details are displayed by usage and billing cycle. You can also select other statistical dimensions or periods.
Check the Consistency of the Actual Usage and Billed Usage
Assume that you purchased two IoTDA SU1 units at 10:09:06 on April 8, 2023, and delete the them at 10:09:06 on April 10, 2023.
- IoTDA transaction bills
Pay-per-use IoTDA instances are billed by day and settled at 00:00 (UTC+08:00) every day. You can check the transaction records against the actual information. For details, see Table 1.
Table 1 IoTDA transaction bills Service
IoTDA
Product
IoTDA standard instance
Billing Mode
Pay-per-use billing
Expenditure Time
From 10:09:06 on April 8, 2023 to 10:09:06 on April 10, 2023, 3 transaction bills were generated:
- April 8, 2023, 10:09:06 to April 9, 2023, 00:00:00
- April 9, 2023, 00:00:00 to April 10, 2023, 00:00:00
- April 10, 2023, 00:00:00 to April 10, 2023, 10:09:00
List Price
List price = Usage x Unit price
In this example, you use IoTDA for 36,546 seconds in the first billing cycle. You can query the unit price on the IoTDA Pricing Details page. For example, if the daily price is USD0.81 for a SU1 unit and the number of units is 2, the list price is USD0.6852375. Calculation: (36,546/86,400) × 2 × 0.81 = USD0.6852375.
Discounted Amount
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. Discounts are based on the list prices.
Truncated Amount
Huawei Cloud bills a resource with the price (USD) accurate to the 8th decimal place. However, the amount due is truncated to the 2nd decimal place, while the third and later decimal places are referred to as the truncated amount.
Taking the first billing cycle as an example, the truncated amount is USD0.0052375.
Amount Due
Amount due = List price – Discount amount – Truncated amount
Take the first billing cycle as an example. If the discount amount is 0, the amount due is USD0.68 (0.6852375 – 0 – 0.0052375).
- IoTDA bill details
Bill details can display in multiple ways. By default, the bill details of a resource are displayed by usage and by billing cycle. Table 2 illustrates the IoTDA bill details, which can be used to check against the actual usage.
Table 2 IoTDA bill details Service
IoTDA
Product
IoTDA standard instance
Billing Mode
Pay-per-use billing
Resource Name/ID
Name and ID of an IoTDA instance.
Example: iotda-test-instance, 4cdeb1cd-7071-4890-9ce4-e6c2299e960e
Specifications
Example: IoTDA standard instance | Small package SU1
Usage type
Duration
Unit Price
In the pay-per-use billing mode, the unit price is provided only when the amount is equal to the usage multiplied by the unit price. No unit price is provided in other pricing modes, for example, tiered pricing.
For details about the unit price of pay-per-use IoTDA instances, see IoTDA Pricing Details.
Price Unit
Unit price in IoTDA Pricing Details: USD/day.
Usage
The usage is displayed by the unit price, which is USD/day for IoTDA. The usage is measured by day. In this example, the usage duration from 10:09:06 on April 8, 2023 to 10:09:06 on April 10, 2023 is two days, and the number of units is 2. Therefore, the total usage is 4 (2 x 2).
Usage Unit
day
List Price
List price = Usage x Unit price
In this example, the usage is 2 days, and the unit price can be queried in IoTDA Price Details. For example, if the price is USD0.81 per unit per day and the number of units is 2, the list price is USD3.24 (0.81 × 2 × 2).
Discounted Amount
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. Discounts are based on the list prices.
Amount Due
Amount that should be paid for used cloud services after discounts are applied.
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