Yearly/Monthly Billing

If you expect to use resources for a longer period, you can save money by selecting yearly/monthly billing. This section describes the billing rules for yearly/monthly CPH resources.

Application 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

Billed Items

A cloud phone server consists of EVS disks and an EIP. You are billed for the following items on a yearly/monthly basis.

**Table 1** Items billed on a yearly/monthly basis
Billed Item	Description
Cloud phone server	You obtain cloud phones only after purchasing a server. You pay for all resources on the server. Server for general-purpose cloud phones: CPU, memory, and local disk Server for gaming cloud phones: CPU, memory, local disk, and cloud mobile gaming access software
(Optional) EIP	If the number of EIPs is not 0 in the instance specifications, pay for the EIP traffic or bandwidth. The billing standard varies depending on the bandwidth type. Dedicated bandwidth: billed based on total traffic irrespective of usage duration; configurable maximum bandwidth size Shared bandwidth: billed based on the bandwidth size by the hour
(Optional) EVS disk	Servers of the following flavors do not have local disks: physical.kg1.4xlarge.cp, physical.kg1.4xlarge.cg, physical.rx2.32xlarge.4, and physical.rx3.32xlarge.4. By default, the system purchases one or more ultra-high I/O EVS disks that will be billed based on the disk capacity by the hour.

Impact of Expiration

Figure 1 shows the statuses a yearly/monthly CPH resource can go through throughout its lifecycle. After a cloud phone server is purchased, it enters the valid period and runs normally during this period. If the cloud phone server is not renewed after it expires, before being deleted, it first enters a grace period and then a retention period.

Figure 1 Lifecycle of a yearly/monthly CPH resource

Expiration Reminder

The system will send you a reminder (by email, SMS, or in-app message) 7 days before a yearly/monthly CPH resource expires to remind you to renew the subscription.

Impact of Expiration

If your yearly/monthly CPH resource is not renewed after it expires, it changes to the Expired state and enters a grace period. During the grace period, you can access CPH resources but cannot:
- Change the cloud phone server flavor
- Change the OS
- Expand the EVS disk capacity
- Change the bandwidth size
If the yearly/monthly CPH 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.
If the yearly/monthly CPH resource is not renewed by the time the retention period ends, the compute resources (vCPUs and memory), EVS disks, and EIPs will be released and data cannot be restored.