- What's New
- Function Overview
- Service Overview
- Billing
- Getting Started
-
User Guide
- Service Provisioning
- Allowing or Disallowing Access to Cloud Assets
- Asset Map
- Asset Management
- Sensitive Data Identification
- Policy Center
- Data Asset Protection
- Data Security Operations
- Alarm Notifications
- Multi-Account Management
- Permissions Management
- Key DSC Operations
- Best Practices
-
API Reference
- Before You Start
- Calling APIs
-
API Description
- Data Watermarking
- Resource Management
- Dynamic Data Masking
- Alarm Notifications
-
Image Watermarking
- Injecting Invisible Watermarks into Images
- Extracting Invisible Text Watermarks
- Extracting Invisible Watermarks from Images
- Injecting Invisible Watermarks into Images (Image Addresses)
- Extracting Dark Watermarks from Images (Image Addresses)
- Extracting Invisible Image Watermarks from Images (Image Addresses)
- Asset Management
- Document Watermarking
-
Sensitive Data Discovery
- Querying the Identification Task List
- Querying the Result of an Identification Task
- Viewing the Rule List
- Creating a Sensitive Data Scanning Rule
- Modifying a Sensitive Data Scanning Rule
- Deleting a Sensitive Data Scanning Rule
- Querying Sensitive Data Scanning Rule Groups
- Creating a Sensitive Data Scanning Rule Group
- Deleting a Sensitive Data Scanning Rule Group
- Creating a Sensitive Data Scanning Task
- Deleting a Sensitive Data Scanning Task
- Static Data Masking
- API Call Records
- Appendixes
- SDK Reference
-
FAQs
- Product Consulting
- Regions and AZs
- Asset Authorization
-
Sensitive Data Identification and Masking
- What Services Can Use DSC to Scan for Sensitive Data?
- How Long Does It Take for DSC to Identify and Mask Sensitive Data?
- What Are the Built-in Identification Rules of DSC?
- What Are the Identification Rules in the Built-in Identification Template of DSC?
- Does Data Masking Affect My Raw Data?
- Does DSC Have Specific Requirements on the Character Set for Which Sensitive Data Is to Be Identified and Masked?
- Why Cannot I Find a Table in an Existing Database When Creating a Database Data Masking Task?
- Data Watermarking
- Data Usage Audit
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Service Provisioning
- Assets
- Overview
- Sensitive Data Identification
- Data Masking
- Data Watermarking
- Alarm Notifications
- Permissions Management
-
FAQs
- Product Consulting
- Adding Data Assets
-
Sensitive Data Identification and Masking
- What Services Can Use DSC to Scan for Sensitive Data?
- How Long Does It Take for DSC to Identify and Mask Sensitive Data?
- Which Types of Sensitive Data Can Be Identified by DSC?
- Does Data Masking Affect My Raw Data?
- Does DSC Have Specific Requirements on the Character Set for Which Sensitive Data Is to Be Identified and Masked?
- How Do I Add Multiple Identification Rule Groups?
- Data Watermarking
- Change History
-
API Reference (ME-Abu Dhabi Region)
- Before You Start
- Calling APIs
-
API Description
- Data Watermarking
- Resource Management
- Dynamic Data Masking
- Alarm Notifications
-
Image Watermarking
- Injecting Invisible Watermarks into Images
- Extracting Invisible Text Watermarks
- Extracting Invisible Watermarks from Images
- Injecting Invisible Watermarks into Images (Image Addresses)
- Extracting Dark Watermarks from Images (Image Addresses)
- Extracting Invisible Image Watermarks from Images (Image Addresses)
- Asset Management
- Document Watermarking
-
Sensitive Data Discovery
- Querying the Identification Task List
- Querying the Result of an Identification Task
- Viewing the Rule List
- Creating a Sensitive Data Scanning Rule
- Modifying a Sensitive Data Scanning Rule
- Deleting a Sensitive Data Scanning Rule
- Querying Sensitive Data Scanning Rule Groups
- Creating a Sensitive Data Scanning Rule Group
- Deleting a Sensitive Data Scanning Rule Group
- Creating a Sensitive Data Scanning Task
- Querying the Database Lineage Graph
- Querying the Table Lineage Graph in Pages
- Querying Data Linage Graph at the Column Level
- Querying the OBS Bucket Lineage Graph
- Querying the OBS File Linage Graph in Pages
- Static Data Masking
- API Call Records
- Appendixes
- Change History
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Copied.
Pay-Per-Use
Pay-per-use billing is a postpaid mode in which you pay for what you use. This billing mode requires no upfront or long-term commitments. This document describes the billing rules of pay-per-use APIs (data masking and watermarking APIs).
Application Scenario
Pay-per-use billing is suitable for applications or services that cannot be interrupted but have unpredictable or sudden traffic surges, such as flash sale activities on e-commerce platforms, temporary testing, and scientific computing.
Applicable Billing Items
- Watermark APIs
- Data masking APIs
Constraints
If you purchase the DSC professional edition, you can enjoy over 1 million watermark API calls free of charge every month.
Billing Period
Pay-per-use DSC API calls are charged by month. The fee is settled once a month (calendar month). After the settlement is complete, a new billing period starts. The billing start time is the time when the API is successfully called for the first time, and the end time is the time when the API is called for the last time in the month.
For example, if you call the watermarking API for the first time at 2023/03/08 15:50:04 and then call the watermark API for the last time at 2023/04/08 23:59:59, the billing period is from 2023/03/08 15:50:04 to 2023/04/08 23:59:59. During this period, no fee is generated for 0 to 1 million API calls. If the number of API calls exceeds 1 million, you will be charged by the extra number of calls.
Billing Examples
If you call the watermarking API for the first time at 2023/03/08 15:50:04 and then for the last time at 2023/04/08 23:59:59, the billing period is from 2023/03/08 15:50:04 to 2023/04/08 23:59:59.
- The first billing period is 0 to 1 million calls.
- The second billing period is 1 million to 1.1 million calls, which cost 34.6 USD.
Figure 1 shows the billing calculation.
Impact of Arrears
Figure 2 describes the status of pay-per-use DSC resources in different periods. After you purchase DSC resources, the period during which the resources run properly within the billing period is the validity period. If your account is in arrears due to failed payments for the pay-per-use DSC resources, the resources enter the grace period and then retention period.
Arrears notifications
The system deducts fees from your account balance for pay-per-use resources at the end of each billing cycle. If your account is in arrears, we will notify you by email, SMS, or internal message.
Arrears impacts
Your account may fall into arrears after pay-per-use fees for DSC are deducted from the account balance. If you are in arrears, you cannot call APIs for updating operations but can call APIs for viewing information. You need to pay the fees of your pay-per-use resource incurred during the grace period. To view the fees, go to the Billing Center > Overview page. Huawei Cloud will deduct the fees after you top up your account.
If you do not pay arrears within the grace period, the resource enters the retention period and its status changes to Frozen. In this case, you cannot call APIs for updating operations but can call APIs for viewing information.
If you do not pay arrears after the retention period expires, the data will be deleted and cannot be restored.
Huawei Cloud offers a 15-day grace period and a 15-day retention period.
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