Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the following detailed description of specific embodiments of the present application is given with reference to the accompanying drawings. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the matters related to the present application are shown in the accompanying drawings. Before discussing exemplary embodiments in more detail, it should be mentioned that some exemplary embodiments are described as processes or methods depicted as flowcharts. Although a flowchart depicts operations (or steps) as a sequential process, many of the operations can be performed in parallel, concurrently, or at the same time. Furthermore, the order of the operations may be rearranged. The process may be terminated when its operations are completed, but may have additional steps not included in the figures. The processes may correspond to methods, functions, procedures, subroutines, and the like.
The terms first, second and the like in the description and in the claims, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged, as appropriate, such that embodiments of the present application may be implemented in sequences other than those illustrated or described herein, and that the objects identified by "first," "second," etc. are generally of a type, and are not limited to the number of objects, such as the first object may be one or more. Furthermore, in the description and claims, "and/or" means at least one of the connected objects, and the character "/", generally means that the associated object is an "or" relationship.
In a more common existing implementation manner, bill data is generally downloaded from each cloud platform of the multi-cloud environment manually, and manually checked according to the bill data to determine whether service charge of the multi-cloud environment is accurate. However, the cloud platform has a plurality of service types and different calculation modes, and the efficiency and accuracy of bill checking are difficult to ensure by manual checking. The formats of the bill data provided by the cloud platforms are not uniform, errors are easy to occur when the bill data are checked, the account checking difficulty is high, and the efficiency and accuracy of bill checking are affected.
In order to solve the above-mentioned problems, the present embodiment provides a method for checking a multi-cloud bill, so as to check the bill data and bill detail data of cloud resources provided by cloud manufacturers with the locally recorded resource data of cloud resources, accurately and rapidly detect the bill with abnormal charge in the bill data and bill detail data, effectively improve the efficiency and accuracy of bill checking, and ensure the accuracy of service charging in a multi-cloud environment.
The method for checking the multi-cloud bill provided in the embodiment may be performed by a multi-cloud bill checking device, and the multi-cloud bill checking device may be implemented in a software and/or hardware manner, and the multi-cloud bill checking device may be configured by two or more physical entities or may be configured by one physical entity. For example, the multi-cloud bill checking device can be a checking server, and the checking server can check the cost bill in the multi-cloud environment to determine the cloud resources with abnormal charge in the cost bill, so that the enterprise is prevented from paying extra cost on the cloud resources.
The cloud bill checking device is provided with at least one type of operating system, wherein the operating system comprises, but is not limited to, an android system, a Linux system and a Windows system. The cloud bill checking device may install at least one application program based on the operating system, and the application program may be an application program of the operating system, or may be an application program downloaded from a third party device or a server. In this embodiment, the multi-cloud bill collation apparatus has at least an application program that can execute the multi-cloud bill collation method.
For ease of understanding, the present embodiment will be described taking the accounting server as an example of a main body that performs the multi-cloud bill checking method.
Fig. 1 shows a flowchart of a multi-cloud bill checking method according to an embodiment of the present application. Referring to fig. 1, the multi-cloud bill checking method specifically includes:
s110, calling interfaces of all cloud platforms to obtain first bill data of all cloud platforms, and obtaining first bill detail data uploaded by all cloud platforms.
The first billing data is billing data generated by the cloud platform according to the usage data of the corresponding deployed cloud resources in the settlement period, and the first billing data comprises resource identifiers of the corresponding cloud resources, resource usage time periods in the settlement period, resource expense in the settlement period, order identifiers, charging modes, discount information, project names, product names and the like. The settlement period is set by the cloud platform, and generally, the cost of cloud resources is calculated once in each month, and correspondingly, the resource use time period in the first bill data is the time period of cloud resource use in the corresponding month, and the resource cost in the first bill data is the total cost in the corresponding month. The present embodiment is described taking the settlement period as an example of month.
The cloud platform may calculate, based on a charging mode of the cloud resource, a charge of the cloud resource in a current month corresponding to the deployment, and generate, according to the charge of the cloud resource and other information, first billing data corresponding to the current month of the cloud resource. Further, the cloud platform provides an API interface for calling first billing data of the cloud resource, and the billing server is provided with a cloud platform SDK. At the beginning of month, the account checking server can generate a bill acquisition request according to cloud platform account numbers registered by enterprises and resource identifiers of cloud resources deployed on a cloud platform by the enterprises, the cloud platform SDK sends the bill acquisition request to an API (application program interface) cloud platform of the cloud platform to perform identity verification on the enterprise account numbers in the bill acquisition request received by the API, after the identity verification is passed, first bill data corresponding to the last month of the cloud resources are acquired according to the cloud resource identifiers in the bill acquisition request, and the acquired first bill data are sent to the account checking server through the API. The reconciliation server may invoke an API interface provided by each cloud platform to obtain first billing data for a last month of cloud resources deployed by the enterprise on each cloud platform.
The first bill detail data is bill data of the cloud platform for counting the cost of the cloud resource in unit time according to the enterprise requirement, wherein the unit time is set by the enterprise, and the unit time is also days or hours under the condition that the settlement period is month. The present embodiment is described taking the number of hours per unit time as an example. The first bill specification data comprises a resource identifier of the cloud resource, a resource use time period in unit time length, a resource expense in unit time length, an order identifier, a charging mode, discount information, a project name and a product name, and further comprises expense of the cloud resource in unit time length and other more detailed information such as associated receipts, price attributes and the like. It can be appreciated that, compared to the total cost of the cloud resource recorded in the first billing data in the corresponding month, the first billing data records the cost of the cloud resource in the corresponding month corresponding to the hours, and since one month can be divided into a plurality of hours, the cloud platform correspondingly generates a plurality of first billing data in each month. The embodiment aims at checking bill data and bill detail data, determining whether the total cost and unit time length cost of cloud resources are accurate or not, and guaranteeing the accuracy of service charging in a cloud environment.
For example, during use of the cloud resource, the cloud platform may calculate a cost of the cloud resource correspondingly deployed for each hour in the current month based on a charging mode of the cloud resource, and generate first billing details data of the cloud resource corresponding to each hour according to the cost of each hour and other information. At the beginning of the month, each cloud platform uploads the first bill detail data of each hour of the last month of the cloud resource to the reconciliation server through an API interface provided by the reconciliation server, and the reconciliation server acquires the first bill detail data uploaded by each cloud platform.
S120, analyzing the first bill data and the first bill detail data of each cloud platform into a lightweight data exchange format according to a preset field name to obtain second bill data and second bill detail data.
The first bill data of each cloud platform is converted into bill data in a unified field format through a preset field name, and then the bill data in the unified field format is analyzed into a lightweight data exchange format to obtain second bill data. And converting the first bill detail data of each cloud platform into bill detail data in a unified field format through a preset field name, and analyzing the bill detail data in the unified field format into a lightweight data exchange format to obtain second bill detail data. It can be understood that the formats of the first bill data generated by different cloud platforms are different from those of the data table of the cloud resource collected in advance, if the first bill data is directly checked with the data table of the cloud resource, the complexity of checking accounts is increased, and even error checking accounts are easily caused, so that the checking account efficiency and the checking account accuracy are affected. Similarly, the formats of the first bill detail data generated by different cloud platforms are different from each other and are different from the formats of the data tables of the cloud resources collected in advance, if the first bill detail data and the data tables of the cloud resources are directly checked, the complexity of checking the accounts can be increased, even error checking accounts are easily caused, and the checking account efficiency and the checking account accuracy are affected. Therefore, in order to facilitate subsequent reconciliation of the first bill data and the first bill detail data, each first bill data and each first bill detail data can be converted into data unified with the field format of the data table, so that the reconciliation accuracy is ensured while the reconciliation efficiency is improved.
In this embodiment, fig. 2 is a flowchart of generating second bill data and second bill specification data provided by an embodiment of the present application. As shown in fig. 2, the step of generating the second bill data and the second bill specification data specifically includes S1201-S1202:
s1201, renaming field names of the same field type in the first bill data according to preset field names, and analyzing the first bill data after field renaming into a lightweight data exchange format to obtain second bill data.
The preset field names are names of various fields in a predefined unified field format, and comprise field names of resource identifiers, field names of resource fees, field names of resource use time periods, field names of charging modes and the like. It can be understood that, different cloud platforms have different names for fields such as a resource identifier, a resource cost, a resource usage period, and a charging mode in the first bill data, for example, the cloud platform a will name the field of the resource identifier as XID, and the cloud platform B will name the field of the resource identifier as YID. In order to facilitate the subsequent direct positioning of the resource identifier in the first bill data, the field name of the resource identifier in the first bill data can be renamed to be the field name of the resource identifier in the preset field name, and if the field name of the resource identifier in the preset field name is the resource ID, the field names of the resource identifiers in the renamed first bill data are uniformly named as the resource ID. Similarly, the field names of the resource cost, the resource use time period, the charging mode and the like in the first bill data are respectively renamed as the field names of the resource cost, the resource use time period and the charging mode in the preset field names.
After renaming the field name of the first bill data to obtain first bill data in a unified field format, analyzing the first bill data in the unified field format into a lightweight data exchange format, namely analyzing the first bill data in the unified field format into a JSON format to obtain second bill data. Because the second bill data in the JSON format is presented in the form of key value pairs, the structure is clear, and the data can be positioned and understood more quickly in the reconciliation process, so that the accuracy and the efficiency of the comparison are improved.
S1202, renaming field names of the same field type in the first bill detail data according to preset field names, and analyzing the first bill detail data after field renaming into a lightweight data exchange format to obtain second bill detail data.
Similarly, the different cloud platforms name the fields such as the resource identifier, the resource cost, the resource usage time period, the charging mode and the like in the first bill detail data, so that the resource identifier in the first bill detail data can be directly positioned later for convenience, and the field names of the resource identifier, the resource cost, the resource usage time period and the charging mode in the first bill detail data can be renamed to be the field names of the resource identifier, the resource cost, the resource usage time period and the charging mode in the preset field names.
After renaming the field name of the first bill detail data to obtain first bill detail data in a unified field format, analyzing the first bill detail data in the unified field format into a lightweight data exchange format, namely analyzing the first bill detail data in the unified field format into a JSON format to obtain second bill detail data. Because the second bill detail data in the JSON format is presented in the form of key value pairs, the structure is clear, and the data can be positioned and understood more quickly in the reconciliation process, so that the accuracy and the efficiency of the reconciliation are improved.
According to the cloud platform bill checking method and device, the first bill data and the field names of the first bill detail data of each cloud platform are renamed through preset field names, so that the first bill data and the first bill detail data of each cloud platform are converted into unified field formats, bill checking is conducted on the basis of field information of the same field names, and bill checking efficiency and accuracy are improved. And analyzing the first bill data and the first bill detail data in the unified field format into the JSON format to obtain second bill data and second bill detail data, so that bill checking can be performed on the follow-up second bill data and the second bill detail data based on the JSON format, and the efficiency and accuracy of reconciliation are further improved.
S130, integrating the second bill data of each cloud platform to obtain a first bill table, and integrating the second bill detail data of each cloud platform to obtain a second bill table.
For example, all second bill data of each cloud platform are integrated into the same bill table to obtain a first bill table, so that the bill check is performed on the first bill table based on a data table of cloud resources collected in advance, and abnormal bills in the first bill table are detected. And integrating all second bill detail data of each cloud platform into the same bill table to obtain a second bill table, so that the second bill table is subjected to bill checking based on a data table of cloud resources collected in advance, and abnormal bills in the second bill table are detected. Further, in order to improve the fine granularity of bill checking, the second bill data of the same item may be integrated into the same bill table according to the item name of the second bill data of each cloud platform to obtain a first bill table corresponding to the item, and accordingly, after the second bill data of each cloud platform is integrated according to the item granularity, the first bill tables corresponding to a plurality of items may be obtained. And integrating the second bill detail data of the same instance into the same bill list according to the project names of the second bill detail data of each cloud platform to obtain a second bill list corresponding to the project, and correspondingly, integrating the second bill detail data of each cloud platform according to the project granularity to obtain a plurality of second bill lists corresponding to the projects. It can be appreciated that the projects are divided according to the business, and the second bill data and the second bill detail data of the same project are respectively integrated into the same first bill table and the second bill table, so that the cost of the projects is calculated while checking the bill of the project, and cloud resource cost of each project is assisted to be optimized.
In this embodiment, fig. 3 is a flowchart of generating a first bill table and a second bill table according to an embodiment of the present application. As shown in fig. 3, the step of generating the first bill table and the second bill table specifically includes S1301-S1302:
s1301, merging the second bill data of each cloud platform, and performing de-duplication processing on the bill list obtained by merging the second bill data to obtain a first bill list.
And combining and placing all the second bill data of each cloud platform in the same bill table, and performing de-duplication processing on the second bill data in the bill table to obtain a first bill table. And deleting repeated second bill data until only one second bill data is reserved when the second bill data is subjected to the deduplication processing. It can be understood that when the accounting server pulls the first bill data through the API interface of the cloud platform, it may repeatedly pull a plurality of first bill data due to network fluctuation or other reasons, so that a plurality of identical second bill data exist in the bill table, and if no duplicate removal processing is performed, the identical second bill data are repeatedly checked with the data table of the cloud resource, thereby affecting the accounting efficiency and accuracy. Therefore, the duplicate removal processing is performed on the second bill data in the bill table so as to delete a plurality of same second bill data to the remaining one, so that only the remaining second bill data is checked against the data table of the cloud resource in the follow-up process, and the checking efficiency and accuracy are improved.
And S1302, merging the second bill detail data of each cloud platform, and performing de-duplication processing on the bill list obtained by merging the second bill detail data to obtain a second bill list.
And combining and placing all the second bill detail data of each cloud platform in the same bill table, and performing de-duplication processing on the second bill detail data in the bill table to obtain a second bill table. And deleting the repeated second bill detail data until only one second bill detail data is reserved when the second bill detail data is subjected to the de-duplication processing. It can be understood that when the cloud platform uploads the first bill detail data to the reconciliation server through the API interface of the reconciliation server, a plurality of first bill detail data may be repeatedly uploaded due to network fluctuation or other reasons, so that a plurality of identical second bill detail data exist in the bill table, and if no duplicate removal processing is performed, the identical second bill detail data are repeatedly reconciled with the data table of the cloud resource, thereby affecting the reconciliation efficiency and accuracy. Therefore, the duplicate removal processing is performed on the second bill detail data in the bill table so as to delete a plurality of same second bill detail data to the rest one, so that only the rest second bill detail data and the data table of the cloud resource are checked in the follow-up process, and the checking efficiency and accuracy are improved.
According to the embodiment, the second bill data and the second bill detail data of each cloud platform are respectively combined, and duplicate removal processing is carried out on the combined bill list, so that a first bill list for storing non-duplicate second bill data and a second bill list for storing non-duplicate second bill detail data are generated, and the billing efficiency and accuracy are improved.
S140, acquiring a data table of cloud resources deployed by each cloud platform from a basic resource database, checking the first bill table and the data table according to a preset checking rule, checking the second bill table and the data table, and determining abnormal bills in the first bill table and the second bill table.
The management server can monitor the running condition of cloud resources deployed by each cloud platform and acquire various data of the cloud resources, such as resource identification, use time period, resource type, charging mode, purchase time, SN number, public network IP, external network IP, location of a machine room, configuration specification, belonged project name and the like. The management server collects various data of each cloud resource in the current month and gathers the data to generate a data table containing resource data of each cloud resource, and the data table of the cloud resource is stored in the basic resource database. And at the beginning of the month, the account checking server acquires the first bill data and the first bill detail data of the last month from the cloud platform, respectively generates a first bill table and a second bill table of the last month according to the first bill data and the first bill detail data, acquires a data table of the last month of each cloud resource from the basic resource database, respectively checks the first bill table and the second bill table of the last month according to the data table of the last month, and determines abnormal bills in the first bill table and the second bill table.
The preset reconciliation rules are used for indicating conditions met by the normal bill, and abnormal bills which do not meet the conditions in the first bill table and the second bill table can be determined according to the reconciliation rules and the data table of the cloud resources.
In this embodiment, the reconciliation rule may be that the data table of the cloud resource of the normal bill is the same as the usage period of the same cloud resource in the first bill table and the second bill table. Accordingly, fig. 4 is a flowchart of determining abnormal bills of the first bill table and the second bill table according to an embodiment of the present application. As shown in fig. 4, the step of determining abnormal bills of the first bill table and the second bill table specifically includes S1401-S1405:
s1401, determining second bill data corresponding to and matched with the resource data according to the resource identification of each resource data in the data table and the resource identification of each second bill data in the first bill table.
In an exemplary embodiment, the resource identifier of each resource data in the data table of the cloud resource is compared with the resource identifier of each second bill data in the first bill table, and if the resource identifier of the resource data is the same as the resource identifier of the second bill data, it is determined that the resource data and the second bill data correspond to the same cloud resource, and then the second bill data are determined as second bill data corresponding to the resource data, so that bill checking can be performed on the corresponding matched second bill data based on the resource data.
S1402, comparing the first resource use time period of the resource data with the second resource use time period of the corresponding matched second bill data, and determining that the corresponding matched second bill data of the resource data is an abnormal bill when the first resource use time period and the second resource use time period are different.
The first resource use time period is a use time period of the cloud resource which the management server monitors to the corresponding resource data belongs to in the last month, and the second resource use time period is a use time period of the cloud platform which the cloud platform monitors to the corresponding second bill data belongs to in the last month. It can be understood that the cloud resources may be taken out of use during the use period, and the cloud platform cannot know that the cloud resources are taken out of use and charging is continued, and the use period of the cloud resources monitored by the management server is different from the use period of the cloud resources monitored by the cloud platform, so that the resource cost of the second bill data is additionally counted in the unused period of the cloud resources, that is, the resource cost in the second bill data is inaccurate, and the second bill data is an abnormal bill. In this regard, the first resource usage time period of the resource data may be compared with the second resource usage time period of the corresponding matched second billing data, and if the first resource usage time period and the second resource usage time period are different, the second billing data is determined to be an abnormal bill.
Further, under the condition that the first resource using time period and the second resource using time period are the same, determining first resource cost corresponding to the resource data according to charging rules in the resource data, comparing the first resource cost with second resource cost in the corresponding matched second bill data, and under the condition that the first resource cost and the second resource cost are different, determining the corresponding matched second bill data of the resource data as an abnormal bill. For example, the first resource usage period and the second resource usage period being the same only indicates that the usage period of the cloud resource monitored by the management server and the cloud platform in the last month is the same, but the resource cost of the cloud resource in the second bill data calculated by the cloud platform is not accurate. In this regard, in this embodiment, when it is determined that the first resource usage period and the second resource usage period of the same cloud resource are the same, a first resource cost of the cloud resource corresponding to the resource data in the first resource usage period is calculated according to the charging rule in the resource data. Comparing the first resource expense with the second resource expense in the second bill data correspondingly matched with the resource data, and when the first resource expense is the same as the second resource expense, indicating that the account checking server and the cloud platform have the same resource expense for the last month calculated by the same cloud resource, determining that the second resource expense in the second bill data calculated by the cloud platform has no problem, and further determining that the second bill data is a normal bill. When the first resource cost and the second resource cost are different, the account checking server and the cloud platform are indicated to be different in resource cost calculated for the same cloud resource, and the second resource cost in the second bill data calculated by the cloud platform can be determined to be abnormal, so that the second bill data is determined to be an abnormal bill.
The charging rules in the resource data include charging mode, discount information and coupon information of the resource data. When the first resource expense is calculated, the total expense of the cloud resource under the configuration in the first resource use time can be calculated according to the charging mode, the first resource use time period and the configuration specification in the resource data, and discount calculation and preferential calculation are carried out on the total expense according to discount information and preferential information, so that the first resource expense is obtained.
According to the method and the device for identifying the abnormal bill, the abnormal bill with errors in time in the first bill list is rapidly and accurately identified by comparing the first resource using time period of the same cloud resource in the resource data with the second resource using time period in the second bill data. Under the condition that the charging time is not wrong, the first resource cost of the cloud resource in the first resource use time period is accurately calculated through the charging rule in the resource data, the first resource cost and the second resource cost of the same cloud resource are compared, an abnormal bill with the wrong resource cost in the first bill list is rapidly and accurately identified, and the billing efficiency and accuracy are effectively improved.
S1403, determining a plurality of second bill detail data corresponding to and matched with the resource data according to the resource identification of each resource data in the data table and the resource identification of each second bill detail data in the second bill table.
The method includes the steps of comparing a resource identifier of each resource data in a data table of the cloud resource with a resource identifier of each second bill detail data in a second bill table, and determining that the resource data and the second bill detail data correspond to the same cloud resource when the resource identifier of the resource data is the same as the resource of the second bill detail data, and determining the second bill detail data as second bill detail data corresponding to and matched with the resource data. Because the second bill list comprises a plurality of second bill detail data with the same resource identification and different resource use time periods, after the comparison of the resource identifications, a plurality of second bill detail data corresponding to and matched with the resource data can be determined in the second bill list, so that bill checking can be carried out on the corresponding matched plurality of second bill detail data based on the resource data.
And S1404, summarizing the third resource use time periods of the plurality of second bill detail data correspondingly matched according to the resource data to obtain a fourth resource use time period, and comparing the first resource use time period with the fourth resource use time period.
The third resource use time period is a use time period of cloud resources corresponding to the second bill detail data in the corresponding hours of the last month, after the third resource use of the plurality of second bill detail data corresponding to and matched with the resource data is summarized to obtain a fourth resource use time period, the fourth resource use time period is a use time period of cloud resources corresponding to the second bill detail data in the last month, which is monitored by the cloud platform. Similarly, the cloud resource may be taken out of use during the use period, and the cloud platform cannot know that the cloud resource has taken out of use and is continuously charged to generate the second bill detail data, and the management server monitors that the use time period of the cloud resource is different from the use time period of the cloud resource monitored by the cloud platform, so that the resource cost of part of the second bill detail data is additionally counted into the unused time period of the cloud resource, that is, the part of the second bill detail data is an abnormal bill. In this regard, the first resource usage time period and the fourth resource usage time period of the resource data may be compared, and if the first resource usage time period and the fourth resource usage time period are different, it is determined that an abnormal bill exists in the plurality of second bill detail data that are correspondingly matched.
S1405, determining redundant second bill detail data in the plurality of second bill detail data correspondingly matched with the resource data under the condition that the first resource use time period and the fourth resource use time period are different, and determining the redundant second bill detail data as an abnormal bill.
In an exemplary case where the first resource usage period and the fourth resource usage period are different, second bill detail data in which the third resource usage period is not within the range of the first resource usage period may be determined from among the plurality of second bill detail data corresponding to and matched with the resource data, and the second bill detail data may be determined as an abnormal bill.
Further, under the condition that the first resource using time period is the same as the fourth resource using time period, determining first resource cost corresponding to the resource data according to charging rules in the resource data, summarizing third resource cost of a plurality of second bill detail data corresponding to the resource data to obtain fourth resource cost, under the condition that the first resource cost is different from the third resource cost, determining fifth resource cost corresponding to each matched second bill detail data according to charging rules in the resource data, comparing the third resource cost of each second bill detail data with the corresponding fifth resource cost, and under the condition that the third resource cost of the second bill detail data is different from the corresponding fifth resource cost, determining the second bill detail data as an abnormal bill.
For example, the first resource usage period and the fourth resource usage period are the same, which only indicates that the usage period of the cloud resource monitored by the management server and the cloud platform in the last month is the same, but the resource cost of the cloud resource in each second bill detail data calculated by the cloud platform is not accurate. In this regard, when it is determined that the first resource usage period and the fourth resource usage period of the same cloud resource are the same, the embodiment calculates, according to the charging rule in the resource data, the first resource cost of the cloud resource corresponding to the resource data in the first resource usage period, and adds up the third resource cost in the plurality of second bill detail data corresponding to and matched with the resource data to obtain the fourth resource cost. When the first resource cost and the fourth resource cost are the same, the account checking server and the cloud platform show that the resource cost of the last month calculated by the same cloud resource is the same, and then the third resource cost in the plurality of second bill detail data corresponding to and matched with the resource data can be determined to be free of problems, and further the plurality of second bill detail data matched with the resource data are determined to be normal bills. When the first resource cost and the fourth resource cost are different, the account checking server and the cloud platform indicate that the resource cost of the same cloud resource calculated in the last month is different, and then it can be determined that the abnormality exists in part of the third resource cost in the plurality of second bill detail data correspondingly matched with the resource data, further the fifth resource cost of each second bill detail data correspondingly matched with the account checking server can be determined according to the charging rule in the resource data, and the fifth resource cost and the third resource cost of the second bill detail data are compared. If the fifth resource cost is the same as the third resource cost, the resource cost of the second bill detail data calculated by the cloud platform corresponding to the number of hours is not problematic, and if the fifth resource cost is different from the third resource cost, the resource cost of the second bill detail data calculated by the cloud platform corresponding to the number of hours is abnormal, and then the second bill detail data is determined to be an abnormal bill.
When calculating the fifth resource fee, the total fee of the cloud resource under the configuration in the third resource using time can be calculated according to the charging mode of the resource data, the third resource using time period of the second bill detail data and the configuration specification in the resource data, and discount calculation and preferential calculation are performed on the total fee according to discount information and preferential roll information, so that the fifth resource fee is obtained.
According to the embodiment, the abnormal bill with errors in time in the second bill list is rapidly and accurately identified by comparing the first resource use time period of the same cloud resource in the resource data with the fourth resource use time period summarized by the plurality of second bill detail data. Under the condition that the charging time is not wrong, the fifth resource cost of the cloud resource in the third resource using section is accurately calculated through the charging rule in the resource data, and compared with the fifth resource cost and the second resource cost of the same cloud resource in the same third resource using section, the abnormal bill with the wrong resource cost in the second bill list is rapidly and accurately identified, so that the billing efficiency and the billing accuracy are effectively improved.
In an embodiment, after determining the abnormal bill, a bill abnormal report may be generated based on the abnormal bill, and the bill abnormal report is sent to the cloud platform, so that the cloud platform corrects the abnormal bill and feeds back the corrected bill to the reconciliation server for reconciliation, thereby ensuring the accuracy of calculating the cost of the cloud resource. Fig. 5 is a flowchart illustrating generation and uploading of a billing abnormality report according to an embodiment of the present application. As shown in fig. 5, the step of generating and uploading the bill anomaly report specifically includes S1501-S1502:
S1501, determining a corresponding abnormal reason according to the abnormal bill, and generating a bill abnormal report according to the abnormal bill and the corresponding abnormal reason.
For example, when the resource usage time of the abnormal bill is different from the resource usage time of the corresponding matched resource data, determining the abnormal cause of the abnormal bill as a billing time error, and when the resource cost of the abnormal bill is different from the resource cost calculated based on the corresponding matched resource data, determining the abnormal cause of the abnormal bill as a resource cost error. And adding the abnormal bill and the corresponding abnormal reason into a preset report template, and automatically generating a corresponding bill abnormal report.
S1502, sending the bill abnormality report to a cloud platform corresponding to the abnormal bill, so that the cloud platform corrects the abnormal bill according to the abnormality reason in the bill abnormality report, and issuing bill data or bill detail data obtained through correction.
Illustratively, according to the cloud platform identification in the abnormal bill, an API interface of the cloud platform is called to upload the bill abnormal report to the cloud platform. After receiving the bill abnormality report, the cloud platform corrects the resource use time period or the resource cost of the abnormal bill according to the abnormality reasons in the bill abnormality report, and re-issues the corrected bill data or bill detail data to the reconciliation server. And the reconciliation server rechecks the corrected bill data or bill detail data according to the resource data, so as to ensure the calculation accuracy of the cost of the cloud resource.
In an embodiment, when the reconciliation server determines that the first reconciliation table and the second reconciliation table have no abnormal bill, a payment bill can be generated according to the first reconciliation table, the second reconciliation table and the data table, and an API (application program interface) of the financial system is called to transmit the payment bill to the financial system, so that the financial system pays for the cloud resources of the last month, the processes of independently starting the payment bill and uploading the certificate by the financial system are saved, and the payment efficiency is improved.
In summary, the multi-cloud bill checking method provided by the embodiment of the application includes the steps of acquiring first bill data of each cloud platform by calling interfaces of each cloud platform, acquiring first bill data uploaded by each cloud platform, analyzing the first bill data and the first bill data of each cloud platform into a lightweight data exchange format, respectively converting the first bill data and the first bill data of the lightweight data exchange format into second bill data and second bill data of a preset field format, integrating the second bill data of each cloud platform to obtain a first bill table, integrating the second bill data of each cloud platform to obtain a second bill table, acquiring a data table of cloud resources deployed by each cloud platform in a basic resource database, checking the first bill table and the data table according to preset checking rules, checking the second bill table and the data table, and determining abnormal bills in the first bill table and the second bill table. Through the technical means, the bill data obtained from the cloud platform and the bill detail data provided by the cloud manufacturer can be converted into the standard data format, so that the bill data and the bill detail data in the standard data format can be subjected to bill checking with a locally recorded data table of cloud resources, and the accuracy of bill checking is ensured. And integrating the bill data and the bill detail data into a first bill table and a second bill table respectively, so that the first bill table and the second bill table can be directly and respectively checked with the data table in the follow-up process, and the bill checking efficiency is improved. According to the preset checking rules, the first bill list and the data list are checked, the second bill list and the data list are checked, the bill with abnormal charge in the bill data and the bill detail data is accurately and rapidly detected, the problem that checking efficiency and accuracy of manual checking of the bill are difficult to guarantee in the prior art is solved, checking efficiency and accuracy of the bill are effectively improved, and service charging accuracy of a cloud environment is guaranteed.
On the basis of the above embodiments, fig. 6 is a schematic structural diagram of a multi-cloud bill checking device according to an embodiment of the present application. Referring to fig. 6, the multi-cloud bill checking device provided in this embodiment specifically includes a bill obtaining module 21, a bill format converting module 22, a bill integrating module 23, and a bill checking module 24.
The bill obtaining module 21 is configured to call an interface of each cloud platform to obtain first bill data of each cloud platform, and obtain first bill detail data uploaded by each cloud platform;
The bill format conversion module 22 is configured to parse the first bill data and the first bill detail data of each cloud platform into a lightweight data exchange format according to a preset field name, so as to obtain second bill data and second bill detail data;
The bill integrating module 23 is configured to integrate the second bill data of each cloud platform to obtain a first bill table, and integrate the second bill detail data of each cloud platform to obtain a second bill table;
The bill checking module 24 is configured to obtain the data table of the cloud resources deployed by each cloud platform from the base resource database, check the first bill table with the data table and check the second bill table with the data table according to a preset check rule, and determine abnormal bills in the first bill table and the second bill table.
On the basis of the embodiment, the bill checking module 24 includes a first bill matching unit configured to determine second bill data corresponding to and matching the resource data according to the resource identifier of each resource data in the data table and the resource identifier of each second bill data in the first bill table, a first bill checking unit configured to compare a first resource usage period of the resource data with a second resource usage period of the corresponding and matching second bill data, determine that the second bill data corresponding to and matching the resource data is an abnormal bill when the first resource usage period and the second resource usage period are different, a second bill matching unit configured to determine a plurality of second bill data corresponding to and matching the resource data according to the resource identifier of each resource data in the data table and the resource identifier of each second bill data in the second bill table, and a second bill checking unit configured to summarize a plurality of second bill data corresponding and matching the resource data according to the first resource usage period to obtain a fourth resource usage period, and compare the first resource usage period and the second bill data corresponding to the second bill data as an unnecessary bill data when the first resource usage period and the second resource usage period are different, and the second bill matching unit is a redundant bill data.
On the basis of the embodiment, the first bill checking unit further comprises a first fee calculating subunit configured to compare the first resource usage time period of the resource data with the second resource usage time period of the corresponding matched second bill data, determine the first resource fee corresponding to the resource data according to the charging rule in the resource data when the first resource usage time period is the same as the second resource usage time period, and compare the first resource fee with the second resource fee in the corresponding matched second bill data, and a first abnormal bill determining subunit configured to determine the second bill data corresponding to the resource data as an abnormal bill when the first resource fee and the second resource fee are different.
On the basis of the embodiment, the second bill checking unit comprises a second expense calculating subunit, a second abnormal bill determining subunit and a second abnormal bill determining subunit, wherein the second expense calculating subunit is configured to determine fifth resource expense corresponding to each matched second bill detail data according to charging rules in the resource data when the first resource use time period is the same as the fourth resource use time period, determine first resource expense corresponding to the resource data according to the charging rules in the resource data, and summarize third resource expense corresponding to the matched plurality of second bill detail data to obtain fourth resource expense when the third resource expense is different from the third resource expense, and determine fifth resource expense corresponding to each matched second bill detail data according to the charging rules in the resource data when the third resource expense is different from the fifth resource expense.
On the basis of the embodiment, the multi-cloud bill checking device comprises an abnormal report generating unit and an abnormal report uploading unit, wherein the abnormal report generating unit is configured to determine corresponding abnormal reasons according to the abnormal bills after determining the abnormal bills in the first bill table and the second bill table, generate bill abnormal reports according to the abnormal bills and the corresponding abnormal reasons, and the abnormal report uploading unit is configured to send the bill abnormal reports to a cloud platform corresponding to the abnormal bills so that the cloud platform corrects the abnormal bills according to the abnormal reasons in the bill abnormal reports and sends bill data or bill detail data obtained through correction.
On the basis of the embodiment, the bill format conversion module 22 includes a first format conversion unit configured to rename field names of the same field type in the first bill data according to preset field names, parse the field renamed first bill data into a lightweight data exchange format to obtain second bill data, and a second format conversion unit configured to rename field names of the same field type in the first bill detail data according to preset field names, parse the field renamed first bill detail data into a lightweight data exchange format to obtain the second bill detail data.
On the basis of the embodiment, the bill integrating module 23 includes a first integrating unit configured to combine the second bill data of each cloud platform, and perform deduplication processing on the bill table obtained by combining the second bill data to obtain a first bill table, and a second integrating unit configured to combine the second bill detail data of each cloud platform, and perform deduplication processing on the bill table obtained by combining the second bill detail data to obtain a second bill table.
The multi-cloud bill checking device provided by the embodiment of the application acquires the first bill data of each cloud platform by calling the interfaces of each cloud platform, acquires the first bill data uploaded by each cloud platform, analyzes the first bill data and the first bill data of each cloud platform into a lightweight data exchange format, respectively converts the first bill data and the first bill data of the lightweight data interaction format into second bill data and second bill data of a preset field format, integrates the second bill data of each cloud platform to obtain a first bill table, integrates the second bill data of each cloud platform to obtain a second bill table, acquires the data table of cloud resources deployed by each cloud platform in a basic resource database, checks the first bill table with the data table according to a preset check rule, checks the second bill table with the data table, and determines abnormal bills in the first bill table and the second bill table. Through the technical means, the bill data obtained from the cloud platform and the bill detail data provided by the cloud manufacturer can be converted into the standard data format, so that the bill data and the bill detail data in the standard data format can be subjected to bill checking with a locally recorded data table of cloud resources, and the accuracy of bill checking is ensured. And integrating the bill data and the bill detail data into a first bill table and a second bill table respectively, so that the first bill table and the second bill table can be directly and respectively checked with the data table in the follow-up process, and the bill checking efficiency is improved. According to the preset checking rules, the first bill list and the data list are checked, the second bill list and the data list are checked, the bill with abnormal charge in the bill data and the bill detail data is accurately and rapidly detected, the problem that checking efficiency and accuracy of manual checking of the bill are difficult to guarantee in the prior art is solved, checking efficiency and accuracy of the bill are effectively improved, and service charging accuracy of a cloud environment is guaranteed.
The multi-cloud bill checking device provided by the embodiment of the application can be used for executing the multi-cloud bill checking method provided by the embodiment, and has corresponding functions and beneficial effects.
Fig. 7 is a schematic structural diagram of a multi-cloud bill checking apparatus according to an embodiment of the present application, and referring to fig. 7, the multi-cloud bill checking apparatus includes a processor 31, a memory 32, a communication device 33, an input device 34, and an output device 35. The number of processors 31 in the multi-cloud bill checking apparatus may be one or more, and the number of memories 32 in the multi-cloud bill checking apparatus may be one or more. The processor 31, memory 32, communication means 33, input means 34 and output means 35 of the cloud bill checking device may be connected by bus or other means.
The memory 32 is used as a computer readable storage medium for storing software programs, computer executable programs, and modules, such as program instructions/modules corresponding to the method of checking a multi-cloud bill according to any embodiment of the present application (e.g., the bill acquisition module 21, the bill format conversion module 22, the bill integration module 23, and the bill checking module 24 in the multi-cloud bill checking device). The memory 32 may mainly include a storage program area that may store an operating system, application programs required for at least one function, and a storage data area that may store data created according to the use of the device, etc. In addition, memory 32 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage device. In some examples, the memory may further include memory remotely located with respect to the processor, the remote memory being connectable to the device through a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.
The communication means 33 are for data transmission.
The processor 31 executes various functional applications of the device and data processing by running software programs, instructions and modules stored in the memory 32, i.e., implements the above-described multi-cloud bill collation method.
The input means 34 may be used to receive entered numeric or character information and to generate key signal inputs related to user settings and function control of the device. The output means 35 may comprise a display device such as a display screen.
The cloud bill checking device provided by the embodiment can be used for executing the cloud bill checking method provided by the embodiment, and has corresponding functions and beneficial effects.
The embodiment of the application also provides a storage medium containing computer executable instructions, wherein the computer executable instructions are used for executing a multi-cloud bill checking method when being executed by a computer processor, the multi-cloud bill checking method comprises the steps of calling interfaces of all cloud platforms to obtain first bill data of all cloud platforms, obtaining the first bill data uploaded by all cloud platforms, analyzing the first bill data and the first bill data of all cloud platforms into lightweight data exchange formats, respectively converting the first bill data and the first bill data of the lightweight data exchange formats into second bill data and second bill data of preset field formats, integrating the second bill data of all cloud platforms to obtain a first bill table, integrating the second bill data of all cloud platforms to obtain a second bill table, obtaining a data table of cloud resources deployed by all cloud platforms in a basic resource database, checking the first bill table and the data table according to preset checking rules, and determining abnormal bill tables in the first bill table and the second bill table.
Storage media-any of various types of memory devices or storage devices. The term "storage medium" is intended to include mounting media such as CD-ROM, floppy disk or tape devices, computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, lanbas (Rambus) RAM, etc., non-volatile memory such as flash memory, magnetic media (e.g., hard disk or optical storage), registers or other similar types of memory elements, etc. The storage medium may also include other types of memory or combinations thereof. In addition, the storage medium may be located in a first computer system in which the program is executed, or may be located in a second, different computer system connected to the first computer system through a network such as the internet. The second computer system may provide program instructions to the first computer for execution. The term "storage medium" may include two or more storage media residing in different locations (e.g., in different computer systems connected by a network). The storage medium may store program instructions (e.g., embodied as a computer program) executable by one or more processors.
Of course, the storage medium containing the computer executable instructions provided in the embodiments of the present application is not limited to the above method for checking a multi-cloud bill, and may also perform the related operations in the method for checking a multi-cloud bill provided in any embodiment of the present application.
The multi-cloud bill checking device, the storage medium and the multi-cloud bill checking apparatus provided in the above embodiments may perform the multi-cloud bill checking method provided in any embodiment of the present application, and technical details not described in detail in the above embodiments may be referred to the multi-cloud bill checking method provided in any embodiment of the present application.
The foregoing description is only of the preferred embodiments of the application and the technical principles employed. The present application is not limited to the specific embodiments described herein, but is capable of numerous modifications, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the application. Therefore, while the application has been described in connection with the above embodiments, the application is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit of the application, the scope of which is set forth in the following claims.