Detailed Description
The terminology used in the description of the embodiments section of the present application is for the purpose of describing particular embodiments of the present application only and is not intended to be limiting of the present application.
In order to facilitate understanding of the embodiments of the present application, first, application scenarios related to the present application are briefly described.
The cloud service is a product of development and fusion of traditional computer and Network technologies, such as Distributed Computing (Distributed Computing), parallel Computing (ParallelComputing), Utility Computing (Utility Computing), Network storage (Network storage technologies), Virtualization (Virtualization), Load balancing (Load Balance) Content distribution Network (Content Delivery Network), and the like. Cloud services are an augmentation, usage, and interaction model for internet-based related services, typically involving the provision of dynamically scalable and often virtualized resources over the internet. It is understood that the cloud is a metaphor for network and internet. In the past, telecommunications networks were often represented by clouds and later also by the abstract internet and underlying infrastructure. In practice, cloud services refer to obtaining desired services over a network in an on-demand, easily scalable manner. This service may be IT and software, internet related, or other service, meaning that computing power may also be circulated as a commodity through the internet.
In brief, a plurality of clients can share the system resources of a cloud service provider, and can enjoy professional IT services without erecting any equipment and allocating management personnel, so that the operation cost can be greatly reduced for general entrepreneurs and small and medium-sized enterprises, and for the cloud service provider, the system resources purchased by the cloud service provider can be used by the clients in an idle state, so that the resource utilization rate of the cloud service provider is improved.
Next, the architecture of the cloud service management platform according to the present application will be briefly described.
Fig. 1 is a schematic architecture diagram of a cloud service management platform provided in the present application. As shown in fig. 1, the cloud service management platform 100 may include a web portal 110, an order system 120, a billing system 130, and a resource management system 140. Where resource management system 140 is connected to resource pool 150, user 160 may purchase and use cloud service resources in resource pool 150 through web portal 110. It should be understood that fig. 1 only exemplifies one user and 6 cloud service resources, and the number of users and the number of cloud service resources are not specifically limited in the present application. Moreover, fig. 1 is only one possible implementation manner of the cloud service management platform, and in practical applications, the cloud service management platform 100 may further include more or fewer units, modules, or subsystems, which is not limited in this application.
Portal 110 may be a portal of a cloud service platform, and portal 110 may show a user the types, parameters, and prices of resources available for purchase in the current cloud service resource pool, for example, portal 110 may show user 160 that resource 1 available for use exists in current resource pool 150, resource 1 is a 2-core 8G cloud server, and is located in the south china data center, the operating system is Windows, the bandwidth is 1M, and the rental amount of 3 months is 300 yuan. It will be appreciated that web portal 110 may also provide for user queries for current account balances, billing, usage records, and the like. When a user selects to purchase a certain cloud service resource, the cloud service portal generates order information, which may include user information, the resource type ordered by the user, parameters, and price, and sends the order information to the order system 120. It should be understood that the above examples are illustrative only and are not to be construed as being particularly limiting.
The order system 120 may support the portal 110 to complete a purchase process of the user, for example, provide a payment interface of the cloud platform provider to the portal 110, so that the portal 110 displays a payment page to the user 160, and may drive the charging system 130 to generate a corresponding usage package after the user successfully pays. The method may further include other order management functions such as statistics and classification of orders that the user has successfully paid or not successfully paid, and the application is not limited in particular.
The billing system 130 may generate the usage package purchased this time by the user 160 and update the usage balance of the user, driven by the ordering system 120. When the charging system 130 receives the usage record of the user 160 pushed by the resource management system 140, the usage balance is deducted according to the usage record, and a bill is generated.
In a specific implementation, as shown in fig. 2, the billing system 140 may first generate an amount of the usage package purchased by the user this time according to the order information generated by the order system 120, and then update the usage balance of the current cloud service usage package of the user. When the charging system 130 receives the usage record (i.e., the usage record of the cloud service resource corresponding to the user) pushed by the resource management system 140, the charging system 130 may deduct the usage balance according to the usage record, thereby generating the bill a. It should be understood that bill a may be updated immediately after each time the resource management system 140 pushes a usage record, so if the resource management system 140 sends a usage record every T times, bill a is also updated every T times. As shown in fig. 2, the resource management system 140 at time T1 pushes the usage record from time T0 to time T1 to the charging system 130, so that the charging system generates a bill a1 and updates the usage record according to the usage balance and the usage record, and similarly, the resource management system 140 at time T2 pushes the usage record from time T1 to time T2 to the charging system 130, so that the charging system updates the bill a1 according to the current usage balance and the usage record, generates a bill a2 and updates the usage balance again, and so on, which is not described herein again. It is understood that when the user initiates a bill query request from the portal 110, the billing system 130 may also integrate the newly generated bill to generate historical bill details, and push the bill details to the portal for the user 160 to query and check.
The resource management system 140 may perform overall monitoring and management on various cloud service resources in the resource pool 150, generate usage records of the various cloud service resources according to the usage conditions of the user, and send the usage records to the charging system for processing. In a specific implementation, the resource management system 150 may periodically send the cloud service usage record to the charging system, for example, send the cloud service usage record every 1 hour, and a specific value of the period T may be modified according to a service usage condition, which is not specifically limited in this application. The resource management system 140 may also perform feedback to the web portal according to the overall situation of various cloud service resources in the resource pool 150, for example, feedback cloud computing resources that may be currently idle, and the like.
The resource pool 150 is used to provide various IAAS cloud services to users, such as cloud hosts, cloud storage, bandwidth, and the like, and may also provide Platform As A Service (PAAS) such as a Relational Database Service (RDS), Software As A Service (SAAS), and the like, and may also provide rich cloud services that can be used through a network, such as a Software development cloud, and the like, which is not limited in this application.
Generally, the charging type of the cloud service may be a unit price charging and a volume packet charging. The charging unit price refers to calculating the cost according to the unit price of the network traffic or the usage, for example, the price of the 1G traffic is 1 yuan, and the user needs to spend 60 yuan using the 60G traffic. The usage package charging refers to purchasing a cloud service usage package with a certain amount at one time, after a user uses the cloud service usage package, deducting the usage package according to a usage record, and using unit price charging if the usage package deducts the reduced excess usage, for example, the user spends 30 yuan to purchase 40G traffic, if the user uses 20G traffic, no additional charging is generated, if the user uses 40G traffic, no additional charging is generated, the user spends 30 yuan in total to use 40G traffic, if the user uses 60G traffic, the 40G traffic is not excess usage, no additional charging is generated, if the user uses 20G traffic as excess traffic, unit price charging is performed, and therefore the user needs to spend 30+20 yuan in total to 50 yuan to use 60G traffic. It should be understood that the above examples are illustrative only and are not to be construed as being particularly limiting.
It can be understood that the cost performance of the usage package of the cloud service is much higher than that of the usage-based individual charging, so that a user usually purchases a usage package of cloud computing resources in advance according to own business requirements. However, most users do not check the balance of their usage packages frequently when using the usage packages, so that the users can purchase new usage packages after the usage amount exceeds the usage package amount, and the new usage packages can take effect immediately, but the excess usage amount generates bills according to separate charging, which causes economic loss of the users and reduces the user experience.
For example, as shown in table 1, at time T0, a user spends 30 dollars to purchase a 40G CDN usage package, at time T1, the charging system 130 receives a CDN flow recorded as 20G for use at time T0-T1 sent by the resource manager 140, at this time, the charging system 130 will not generate additional charges, at time T2, the charging system 130 receives a CDN flow recorded as 40G for use, because the balance of the CDN usage package of the user is only 20G at time T2, 20G flow is an excess amount at time T3, the user needs to charge the 20G usage by a unit price, and the 1G flow price is 1 dollar, so the user needs to use 60G flow by 30+20 ═ 50 dollars in total. In fact, the user can purchase a 30-yuan 40G usage package and a 10-yuan 20G usage package to obtain 60G traffic by using 40 yuan, but when the user finds that the traffic is excessive, even if the user immediately purchases the 10-yuan 20G usage package, the excessive usage of 20G is already billed, so that economic loss of the user is caused, and the user experience is reduced. It is to be understood that the above examples are illustrative only and are not to be construed as limiting in any way.
TABLE 1 exemplary billing under an application scenario
| Time of day
|
Usage records
|
Deduction of pre-usage amount
|
Deducting the amount of the usage package
|
Excess amount of dosage
|
Total cost/yuan
|
| T0
|
0
|
40G
|
40G
|
0G
|
30
|
| T1
|
20G
|
40G
|
20G
|
0G
|
30
|
| T2
|
40G
|
20G
|
0G
|
20G
|
30+20×1=50 |
In order to solve the problem that economic loss causes poor user experience due to excess of usage packages, the application provides a cloud service usage package charging method, the option of the usage package effective time is added at a front-end portal website, and the usage package effective time selected when each user purchases a new usage package is recorded, so that the charging system deducts the excess usage according to the new usage package amount to generate an updated bill under the condition that the effective time is judged to be earlier than the purchase time, the economic loss caused by the excess of the usage packages of the user is reduced, and the user experience is improved.
Fig. 3 is a flowchart illustrating a charging method for a cloud service usage package provided in the present application. As shown in fig. 3, the method comprises the following steps:
s101: the charging system receives an order for a first cloud service usage package, wherein the order comprises the effective time, the purchase time and the amount of the first cloud service usage package and a user account for purchasing the first cloud service usage package.
S102: and determining whether the effective time is earlier than the purchasing time, if so, executing the step S103, and if not, executing the step S104.
S103: and updating the bill of the user account according to the amount of the cloud service usage package to generate an updated bill, wherein the bill record has the historically generated excess usage, and the updated bill is generated by deducting the excess usage generated after the effective time of the bill record according to the amount of the first cloud service usage package.
S104: and generating a bill according to the usage record before the validation time and the second cloud service usage package purchased in the history, and updating the bill according to the usage record after the validation time and the second cloud service usage package purchased in the history and the first cloud service usage package.
Referring to the system architecture shown in fig. 1, the order processing method provided by the present application is directed to a billing system, and specifically may be step 3 in fig. 1. That is to say, after the billing system receives the order information sent by the order system, the order processing method provided by the application is executed, and under the condition that the effective time of the usage package selected by the user in the order information is determined to be earlier than the purchase time, the excess usage can be recalculated according to the newly purchased first cloud service usage package, so as to generate an updated bill, reduce the economic loss of the user caused by the excess usage package, and improve the use experience of the user.
The following describes how to recalculate the excess usage according to the first cloud service usage package newly purchased by the user to generate an update bill in detail.
In this embodiment of the application, the order further includes a usage rule of the first cloud service usage package, and the updated bill may be obtained by recalculating the excess usage meeting the usage rule of the first cloud service usage package. It should be understood that, because of the variety of cloud service usage packages, each user may purchase many different types of cloud services in order to meet usage requirements, the charging type of each type of cloud service may also be classified into charging on demand and charging on usage package, and the usage package type in usage package charging may also be classified into a month package type, a year package type, a time package type, and the like. Therefore, when the user purchases a plurality of usage packages and the billing system 130 deducts the account balance according to the usage records of the user, it is necessary to deduct the corresponding usage packages according to the usage records in turn according to the usage rules of different usage packages. Here, the usage rule of the usage package may be determined according to the product type and the usage package type selected when the user purchases the usage package.
The product type may be a hard disk service, a hard disk backup service, and the like of a storage type product, a Content Delivery Network (CDN) service, a Virtual Private Network (VPN) service, and the like of a Network type product, an elastic cloud service, a Cloud Container Engine (CCE) service, and the like of a computing type product, and may also be a cloud service of other product types such as a security type, an application service type, a database type, a video type, an EI enterprise intelligent type, an internet of things type, and the like, which is not particularly limited in this application.
The usage package type may be the amount, duration, etc. of the usage package, for example, the usage package type of the hard disk usage package a purchased by the user is 100G/h/3 months, that is, the user has 100G of hard disk usage package amount every hour in 3 months, if the usage amount of the user in 1 st hour does not exceed 100G, no additional charging will be generated, if the usage amount of the user in 2 hours is 120G, 100G of which is not the excess amount, no additional charging will be generated, 20G of which is the excess amount will be charged at unit price, and if the usage amount of the user in 3 rd hour is 80G, no unit price charging will be generated yet. Similarly, if the usage packet type of the CND usage packet a is 10G/month/1 year, the user has 10G traffic per month in 1 year, if the user uses 10G traffic for the 1 st month, the unit price charging will not be generated, and if the user uses 12G traffic for the 2 nd month, the unit price charging will be performed if the 2G traffic is excess. It should be understood that the foregoing examples are illustrative only, and the present application is not limited thereto.
Therefore, in a specific implementation, the specific step of recalculating the excess usage meeting the usage rule of the first cloud service usage package when the validation time is earlier than the purchase time to generate the updated bill may be as follows:
s1031: querying usage records recorded in the bill that match the usage rules after the validation time.
As shown in FIG. 4, among the usage records, record C1Before the effective date, record C2、C3And C4After the expiration date, however, record C1And record C4Does not match the usage rule of the first cloud service usage package, so the usage record obtained in step S1031 is the record C of the shaded portion2And record C4The two records are usage records that are after the validation date and that match the usage rules of the first cloud service usage package. For example, if record C1And record C3Is a use record of a hard disk, C2And C4Is a usage record of the CDN traffic, and if the first cloud service usage package is a CDN usage package, the usage record that matches the usage rule after the validation time is record C2And record C4. It is to be understood that the above examples are illustrative only and are not to be construed as limiting in any way.
S1032: and deducting the excess usage generated by the usage record according to the amount of the first cloud service usage packet to generate the updated bill. As shown in fig. 4, step S1032 may first determine the excess usage, and then use the excess usage to deduct the first cloud service usage package.
Specifically, first, the second cloud service usage package (the current usage balance of the user account in the foregoing content) may be deducted with reference to the usage record, and the excess usage may be calculated. As shown in fig. 4, the usage record matching the usage rule after the validation time is obtained in step S1031 is record C2And record C4Thereafter, the billing system 130 may base the record C on2And record C4Deducting the second cloud service usage package, wherein, according to record C2And record C41(record C)4Is divided into records C41And record C42) After the second cloud service usage package is deducted, the remaining usage amount matched with the usage rule in the second cloud service usage package is zero, so that the record C which is not deducted in the usage record is used42For overdosing, deducted records C2And C41Is not used in excess.
For example, if record C2CDN traffic of 10G, record C4CDN flow of 15G, and CDN flow quota of the second cloud service usage package is 20G, then the excess usage is 15G and the non-excess usage is 20G, that is, record C at this time41Is 10G, record C42Is 15G. It should be understood that the above examples are illustrative only and are not to be construed as being particularly limiting.
Secondly, after calculating the excess amount, the excess amount may be deducted according to the amount of the first cloud service usage package to generate an updated bill, specifically, as shown in fig. 4, in the updated bill, the excess amount C is added42Deducting the first cloud service usage amount packet without excess usage amount C2And C41And deducting the second cloud service usage package. It should be noted that the usage records that do not match the usage rules of the first cloud service usage package newly purchased by the user, i.e., record C1 and record C3 in fig. 4, will still be subtracted from the second cloud service usage package. As can be appreciated, deducting excess usage from a first cloud service usage package newly purchased by a userThe bill is updated, so that economic loss of the user due to excessive use can be avoided, and the use experience of the user is improved.
In a specific implementation, as can be seen from the foregoing, the resource management system 140 pushes a usage record to the charging system 130 every period T, so that after the user purchases the first cloud service usage package, if the effective time is earlier than the purchase time, the excess usage after the effective time is immediately calculated, and the excess usage is subtracted from the first cloud service usage package again to generate an updated bill. For example, as shown in fig. 5, after the charging system 130 receives the usage record at the time T1-T2 sent by the resource management system 140 at the time T1, a bill a1 may be generated according to the current second cloud service usage package (the current usage balance of the user account), which may specifically refer to the embodiment in fig. 2 and is not described here again. After receiving the user order information sent by the order system at the time T2.5, the charging system 130 firstly generates a first cloud service usage package, determines that the effective time T1 of the first cloud service usage package is earlier than the purchase time T2.5, and secondly determines the excess usage and the non-excess usage of the user account according to the usage record (the usage record after the effective time) at the time T1-T2, thereby generating an updated bill a1 ', wherein in the updated bill a 1', the excess usage deducts the first cloud service usage package, and the non-excess usage deducts the second cloud service usage package, thereby avoiding economic loss of the user due to the excess usage and improving the user experience. The specific process of generating the updated bill a 1' may refer to the embodiment in fig. 4, and is not described herein again. Similarly, after the charging system receives the usage record at the time T2-T3 sent by the resource management system at the time T3, the charging system may deduct the current balance of the second cloud service usage package and the balance of the first cloud service usage package based on the usage record, so as to generate the bill a 2. And so on, the description is not expanded here.
Still taking the application scenario in table 1 as an example, a user spends 30 dollars in purchasing a 40G CDN usage package, the charging system 130 receives the CDN traffic recorded as 20G at the time T0-T1 sent by the resource manager 140 at the time T1, at this time, the charging system 130 does not generate additional charges, the charging system 130 receives the CDN traffic recorded as 40G at the time T2, because the balance of the CDN usage package of the user is only 20G at the time T2, if the charging method of the cloud service usage package provided by the present application is not used, 20G traffic at the time T2 is an excess amount and requires unit price charging. However, if the charging method of the cloud service usage package provided by the present application is used, after the user finds that the traffic is excessive, the user may purchase a 10-tuple 20G usage package at time T3, and set the effective time as time T2, the charging system 130 may deduct the 20G usage package newly purchased by the user according to the excessive usage, and generate an updated bill, where the total cost in the updated bill is only 30+ 10-40 tuples, and compared with the embodiment in table 1, the user reduces the economic loss of the extra 10 tuples due to the excessive usage, and improves the user experience. It should be understood that the above examples are illustrative only and are not to be construed as being particularly limiting.
Table 2 an example of a bill using the charging method of the cloud service usage package provided in the present application in an application scenario
| Time of day
|
Usage records
|
Deduction of pre-usage amount
|
Deducting the amount of the usage package
|
Excess amount of dosage
|
Total cost/yuan
|
| T0
|
0
|
40G
|
40G
|
0G
|
30
|
| T1
|
20G
|
40G
|
20G
|
0G
|
30
|
| T2
|
40G
|
20+20=40G
|
0
|
0
|
30+10=40 |
In this embodiment, if the effective time is not earlier than the purchase time, the billing system 130 may deduct the bill according to the embodiment of fig. 2, that is, generate a bill according to the usage record before the effective time and the second cloud service usage package purchased in the history, and update the bill according to the usage record after the effective time and the second cloud service usage package and the first cloud service usage package purchased in the history. For example, if a user purchases a usage package with a quota of 100 per hour, the purchase time is 8: 00: 00, since the usage package is not needed by the user from 8 o 'clock to 9 o' clock, the user can set the effective time of the usage package to 9: 00: 00, the previous usage record of the 9 points deducts the second cloud service usage package, and charges the excess unit price, and the usage record of the 9 points deducts the first cloud service usage package and the second cloud service usage package, and charges the excess unit price. It can be understood that the user flexibly sets the effective time of the purchase usage package, which not only can avoid the extra cost caused by the excess usage of the user, but also can avoid the waste caused by charging the duration between the purchase time (8 points) and the actual usage time (9 points) of the user, and improve the user experience.
In an embodiment of the present application, the method further includes: receiving a bill inquiry request sent by a client; and responding to the bill inquiry request and sending the updated bill to the client. That is, when the user queries the bill, the bill pushed to the web portal 110 by the charging system 130 is an updated bill that is deducted from the first cloud service usage package by using the excess usage. It can be understood that, as described above, the resource management system 140 pushes the usage record to the charging system 130 once every period T, and the charging system 130 also generates a bill once every period T, so that, in order to facilitate the user to perform the bill query, the charging system may generate a total bill detail once every hour, every month, every day, or every year, and count the bill generated in each period T, for example, if the charging system 130 generates the bill in the last hour once every hour, the 24 bills generated in the previous 24 hours every day may be summarized every zero point every day, and a daily bill detail is generated, and similarly, a monthly bill detail, an annual bill detail, and the like may also be generated, thereby facilitating the user query and improving the user experience.
In the embodiment of the present application, the cloud service management system 100 for implementing the order method of the cloud service usage package provided by the present application only needs to perform simple upgrade on the portal 110, add an effective time option for receiving the order information of the user and the effective time of the usage package, and then the charging system 130 executes step S101 to step S104 to re-charge the excess usage after the effective date of the user, so as to generate an updated bill, thereby avoiding additional charging caused by the excess usage of the user, and improving the user experience.
In a specific implementation, as shown in fig. 6, when portal 110 purchases a first cloud service usage package, portal 110 may display a page 601 as shown in fig. 6 to the user. The user can select a desired cloud service product type, such as a storage packet, a downlink traffic packet, a source return traffic packet, and the like, on the page 601, and after selecting the desired product type, the user can select the storage packet specification of each application traffic packet type, such as the storage packet quota 40GB, the downlink traffic packet quota 50GB, and the source return traffic packet quota 1TB in fig. 6. Then, the user may select the purchase duration, for example, 1 month shown in fig. 6, that is, the usage packet amount of the storage packet is 40GB, the downlink traffic packet amount is 50GB, and the source return traffic packet amount is 1TB in 1 month, and the excess part requires unit price charging. Finally, the user may set an effective time for the selected usage package, specifically, the effective date and time may be directly input in the input box 902, or the calendar may be expanded through the calendar button 903 to select the effective date and time, the effective time may be earlier than the current purchase time or not earlier than the current purchase time, and specifically, may be determined according to the user requirement, and the application is not particularly limited.
The method and the device have the advantages that the option of the usage package validation time is added at the front-end portal website, and the usage package validation time selected by each user when each user purchases a new usage package is recorded, so that the charging system deducts the excess usage according to the newly purchased first cloud service usage package under the condition that the life time is judged to be earlier than the purchase time, an updated bill is generated, the economic loss of the user caused by the excess usage package is reduced, and the use experience of the user is improved.
The following explains a part of the apparatus related to the present application. As shown in fig. 7, the present application provides a charging apparatus 700 for a cloud service volume package, which is applied to the charging system of the cloud service management platform 100 shown in fig. 1, the apparatus 700 includes a receiving unit 710 and an updating unit 720, wherein,
the receiving unit 710 is configured to receive an order for a first cloud service usage package, where the order includes validation time, purchase time, amount of the first cloud service usage package, and a user account for purchasing the first cloud service usage package;
the updating unit 720 is configured to update the bill of the user account according to the amount of the cloud service usage package to generate an updated bill if the validation time is earlier than the purchase time, where the bill records the historically generated excess usage, and the updated bill is generated by deducting the excess usage of the bill record generated after the validation time according to the amount of the first cloud service usage package.
In this embodiment of the application, the order further includes a usage rule of the first cloud service usage package, and the updating unit 720 is configured to query a usage record, recorded in the bill, that matches the usage rule after the validation time; the updating unit 720 is configured to deduct excess usage generated by the usage record according to the amount of the first cloud service usage package to generate the updated bill, wherein the excess usage is usage exceeding the amount of the historically purchased second cloud service usage package.
In this embodiment of the present application, the apparatus further includes a response unit 730, where the receiving unit 710 is configured to receive a bill query request sent by a client; the response unit 730 is configured to send the updated bill to the client in response to the bill query request.
In this embodiment, in the case that the validation time is not earlier than the purchase time, the updating unit 720 is further configured to generate a bill according to the usage record before the validation time and the second cloud service usage package of the historical purchase; the updating unit 720 is further configured to update the bill according to the usage record after the validation time and the second cloud service usage package and the first cloud service usage package purchased in history.
The method and the device have the advantages that the option of the usage package validation time is added at the front-end portal website, and the usage package validation time selected by each user when each user purchases a new usage package is recorded, so that the charging system deducts the excess usage according to the newly purchased first cloud service usage package under the condition that the life time is judged to be earlier than the purchase time, an updated bill is generated, the economic loss of the user caused by the excess usage package is reduced, and the use experience of the user is improved.
Referring to fig. 8, fig. 8 is a schematic structural diagram of an electronic device 800 according to an embodiment of the present disclosure. The electronic device 800 may be the charging system 130 in the foregoing, and as shown in fig. 8, the electronic device 800 includes one or more processors 803, a communication interface 802 and a memory 801. The processor 803, the communication interface 802, and the memory 801 may be connected by a bus system, or may communicate by other means such as wireless transmission. The present embodiment is exemplified by being connected by a bus 804, wherein the bus 804 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, and the like. The bus 804 may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 8, but this is not intended to represent only one bus or type of bus.
The Memory 801 may include a Volatile Memory (Volatile Memory), such as a Random Access Memory (RAM); the Memory 801 may also include a Non-volatile Memory (NVM), such as a Read-Only Memory (ROM), a Flash Memory (FM), a Hard Disk (HDD), or a Solid-State Drive (SSD). The memory 801 may also comprise a combination of memories of the kind described above. The memory 801 may store program codes and program data, among other things. Such as storing program code for generating an update bill based on the excess usage and the amount of the first cloud service usage package, program code for responding to a user query for order information, program code for determining whether the effective time is at the purchase time, etc., as well as storing usage records, bill particulars, and order information, etc.
The communication interface 802 may be a wired interface (e.g., an ethernet interface), may be an internal interface (e.g., a Peripheral Component Interconnect express (PCIe) bus interface), a wired interface (e.g., an ethernet interface), or a wireless interface (e.g., a cellular network interface or using a wireless local area network interface) for communicating with other devices or modules. For example, the communication interface 802 is used to support communication between the electronic device 800 and the order system 110 and the resource management system 140, and/or to perform other steps of the techniques described herein, which will not be described in detail herein.
The processor 803 includes one or more general-purpose processors, which may be any type of device capable of Processing electronic instructions, including a Central Processing Unit (CPU), microprocessor, microcontroller, host processor, controller, and ASIC, among others. The processor 803 is used to execute various types of digitally stored instructions, such as software or firmware programs stored in the memory 801, which enable the computing device to provide a wide variety of services.
Specifically, the processor 803 may at least include an updating unit and a response unit, where the updating unit may include the functions described in the updating unit in fig. 7, for example, in a case that the validation time is earlier than the purchase time, the bill of the user account is updated according to the quota of the cloud service usage package to generate an updated bill, and may also be used to perform other steps described in the embodiments of fig. 3 to fig. 6, which are not described again here; the response unit may include the functions described in the response unit in fig. 7, for example, the updated bill is sent to the client in response to the bill query request, or may be used to perform other steps described in the embodiments of fig. 3 to fig. 6, which are not described herein again. Moreover, for each functional module or unit not mentioned herein, reference may be made to the related explanations in the embodiments described in fig. 3 to fig. 6, and details are not described herein again.
It should be noted that fig. 8 is only one possible implementation manner of the embodiment of the present application, and in practical application, the electronic device 800 may also be a cloud service cluster, where the cloud service cluster includes at least one computing node, and each computing node may be the electronic device shown in fig. 8, which is not described here again. The electronic device may also include more or fewer components, which are not limited herein.
Embodiments of the present application also provide a computer-readable storage medium, which stores instructions that, when executed on a processor, implement the method flows shown in fig. 3-6.
Embodiments of the present application also provide a computer program product, and when the computer program product is run on a processor, the method flows shown in fig. 3-6 are implemented.
The above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded or executed on a computer, the procedures or functions according to the embodiments of the present invention are wholly or partially generated. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optics, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., Digital Video Disk (DVD)), or a semiconductor medium. The semiconductor medium may be an SSD.
While the invention has been described with reference to specific embodiments, the invention is not limited thereto, and various equivalent modifications and substitutions can be easily made by those skilled in the art without departing from the scope of the invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the claims.