Bill data generation method and device, computer equipment, readable storage medium and program product

By receiving and analyzing the bill message of the target account, automatically judge the billing mode conversion conditions and generate bills, it solves the problem that changes in billing methods in traditional cloud computing services require manual reprocessing, and improves the flexibility and efficiency of bill generation.

CN119537657APending Publication Date: 2025-02-28CHINA TELECOM CLOUD TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411762803.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-12-03
Publication Date
2025-02-28

AI Technical Summary

Technical Problem

In traditional cloud computing business, changes in billing methods require business personnel to reprocess the process manually, resulting in poor flexibility and low efficiency.

Method used

By receiving the call message of the target account, based on the resource identification of the target account and the target resource, it is determined whether the billing mode conversion conditions are met. When the conditions are met, query the target billing mode of the target resource to generate corresponding billing data.

Benefits of technology

It realizes automatic judgment of billing mode conversion conditions and generates bills, reducing manual entry and processing procedures, and improving the flexibility and efficiency of bill generation.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119537657A_ABST
    Figure CN119537657A_ABST
Patent Text Reader

Abstract

The invention relates to a bill data generation method and device, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps of receiving a ticket message sent by a target account number, determining whether a charging mode conversion condition is satisfied based on a resource identifier of the target account number and a resource identifier of the target resource, querying a target charging mode corresponding to the target resource under the condition that the charging mode conversion condition is satisfied, and sending the target charging mode to the target account number, and generating bill data corresponding to the target account based on the target charging mode and the use information of the target resource. By adopting the method, the bill generation efficiency can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of cloud computing technology, and in particular to a method, apparatus, computer device, computer-readable storage medium, and computer program product for generating billing data. Background Art

[0002] In traditional cloud computing services, when users use certain cloud resources, the service provider will charge them according to the pre-agreed billing method.

[0003] In traditional technology, when a user needs to use a service, relevant business personnel will accept the user's service request, match the corresponding cloud resources based on the user's needs, and configure the billing method, so as to generate the user's relevant bill based on the billing method for charging. However, in actual usage scenarios, the billing method may change based on the time or demand at different stages. At this time, business personnel need to manually re-complete the business processing process to make changes to ensure the correctness of the bill, resulting in poor flexibility and low efficiency. Summary of the invention

[0004] Based on this, it is necessary to provide a method, apparatus, computer device, computer-readable storage medium and computer program product for generating billing data in response to the above technical problems.

[0005] In a first aspect, the present application provides a method for generating billing data, comprising:

[0006] Receiving a call record message of a target account, wherein the call record message includes usage information of the target account and target resources;

[0007] Determining whether a billing mode switching condition is met based on the target account and the resource identifier of the target resource;

[0008] When the billing mode conversion condition is met, the target billing mode corresponding to the target resource is queried, and based on the target billing mode and usage information of the target resource, bill data corresponding to the target account is generated.

[0009] In one of the embodiments, determining whether a billing mode switching condition is met based on the target account and the resource identifier of the target resource includes:

[0010] Based on the resource identifier of the target resource, determine the target product object identifier, and obtain a list of names corresponding to the target product object identifier;

[0011] In the case that the target account number is included in the list, the billing configuration information corresponding to the target product object identifier is obtained, and it is determined whether the billing mode conversion condition is met based on the billing configuration information.

[0012] In one of the embodiments, the billing configuration information at least includes a mode conversion tag, and determining whether a billing mode conversion condition is met based on the billing configuration information includes:

[0013] Parsing the billing configuration information to obtain a mode conversion tag corresponding to the target account;

[0014] If the mode conversion tag indicates that the mode conversion is allowed, determining that the charging mode conversion condition is met;

[0015] If the mode conversion tag indicates that the mode conversion is not allowed, it is determined that the charging mode conversion condition is not met.

[0016] In one embodiment, generating billing data corresponding to the target account based on the target billing mode and the usage information of the target resource includes:

[0017] Determining target unit billing data corresponding to the target resource based on the billing rule information corresponding to the target billing mode;

[0018] Based on the target unit billing data and the usage information of the target resource, billing data corresponding to the target account is generated.

[0019] In one embodiment, the method further comprises:

[0020] Displaying an account configuration interface, wherein the account configuration interface includes account configuration options;

[0021] In response to the triggering operation of the account configuration option, obtaining a target account to be configured, and performing verification processing on the target account;

[0022] When the target account passes the verification, the target account is added to a preset list.

[0023] In one embodiment, the method further comprises:

[0024] In response to a query operation on a target product object identifier, displaying description information of the target product object;

[0025] Based on the description information of the target product object, a mode conversion tag is set in the billing configuration information corresponding to the target product object.

[0026] In a second aspect, the present application further provides a device for generating bill data, the device comprising:

[0027] A receiving module, configured to receive a call bill message of a target account, wherein the call bill message includes usage information of the target account and target resources;

[0028] A determination module, configured to determine whether a billing mode conversion condition is met based on the target account and the resource identifier of the target resource;

[0029] A generation module is used to query the target billing mode corresponding to the target resource when the billing mode conversion condition is met, and generate bill data corresponding to the target account based on the target billing mode and usage information of the target resource.

[0030] In one embodiment, the determining module is specifically used to:

[0031] Based on the resource identifier of the target resource, determine the target product object identifier, and obtain a list of names corresponding to the target product object identifier;

[0032] In the case that the target account number is included in the list, the billing configuration information corresponding to the target product object identifier is obtained, and it is determined whether the billing mode conversion condition is met based on the billing configuration information.

[0033] In one embodiment, the charging configuration information at least includes a mode conversion tag, and the determining module is specifically configured to:

[0034] Parsing the billing configuration information to obtain a mode conversion tag corresponding to the target account;

[0035] If the mode conversion tag indicates that the mode conversion is allowed, determining that the charging mode conversion condition is met;

[0036] If the mode conversion tag indicates that the mode conversion is not allowed, it is determined that the charging mode conversion condition is not met.

[0037] In one embodiment, the generating module is specifically used for:

[0038] Determining target unit billing data corresponding to the target resource based on the billing rule information corresponding to the target billing mode;

[0039] Based on the target unit billing data and the usage information of the target resource, billing data corresponding to the target account is generated.

[0040] In one embodiment, the device further comprises:

[0041] A first display module is used to display an account configuration interface, wherein the account configuration interface includes account configuration options;

[0042] A first configuration module, configured to obtain a target account to be configured in response to a triggering operation of the account configuration option, and perform verification processing on the target account;

[0043] The adding module is used to add the target account to a preset list when the target account passes the verification.

[0044] In one embodiment, the device further comprises:

[0045] A second display module, configured to display description information of the target product object in response to a query operation on the target product object identifier;

[0046] The second configuration module is used to set a mode conversion tag in the billing configuration information corresponding to the target product object based on the description information of the target product object.

[0047] In a third aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the method steps of the first aspect when executing the computer program.

[0048] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the method steps of the first aspect when executed by a processor.

[0049] In a fifth aspect, the present application further provides a computer program product, comprising a computer program, which implements the method steps of the first aspect when executed by a processor.

[0050] The above-mentioned bill data generation method, device, computer equipment, computer-readable storage medium and computer program product can receive a call bill message sent by a target account, the call bill message contains the usage information of the target account and the target resource, and determine whether the billing mode conversion condition is met based on the resource identifier of the target account and the target resource. If the billing mode conversion condition is met, query the target billing mode corresponding to the target resource, and generate bill data corresponding to the target account based on the target billing mode and the usage information of the target resource. In this solution, it is possible to automatically determine whether the billing mode conversion condition is currently met through the resource identifier of the target account and the target resource, and if the billing mode conversion condition is met, automatically generate a bill according to the converted billing mode, without manual entry or processing, thereby improving the flexibility and efficiency of bill generation. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0052] FIG1 is a schematic diagram of a process for generating bill data in one embodiment;

[0053] FIG2 is a flow chart of an example of a method for generating bill data in one embodiment;

[0054] FIG3 is a structural block diagram of a device for generating bill data in one embodiment;

[0055] FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0057] An embodiment of the present application provides a method for generating billing data. This embodiment uses the method applied to a server as an example for illustration. It can be understood that the method can also be applied to a terminal, and can also be applied to a system including a terminal and a server, and is implemented through the interaction between the terminal and the server.

[0058] The following will describe in detail the method for generating bill data provided by this application in combination with a specific implementation method. As shown in Figure 1, the method includes the following steps:

[0059] Step 102: Receive a call record message of the target account, where the call record message includes usage information of the target account and target resources.

[0060] The target resource may be a cloud resource, and the target account may be an account logged in by the user when using the cloud resource.

[0061] In the embodiment of the present application, the user can log in to the target account and access and use the cloud resources through the target account. In the process of the user using the cloud resources, the cloud resource device will generate a call list message of the target account and send it to the server. Among them, the call list message at least contains the usage information of the target account and the target resource. After receiving the call list message, the server can parse the call list message to obtain the target account, the resource identifier of the target resource, and the usage information of the target resource. The usage information can be the usage duration and / or usage amount, etc.

[0062] Step 104: Determine whether a billing mode switching condition is met based on the target account and the resource identifier of the target resource.

[0063] In an embodiment of the present application, the server can determine whether the billing mode conversion condition is met based on the target account, the resource identifier of the target resource, and a preset judgment strategy. Among them, there can be multiple billing modes. For example, the billing mode can include at least on-demand billing and package cycle billing. In actual usage scenarios, the billing mode may change based on the time or situation in different stages. Therefore, after receiving the call bill message, the server can determine whether the billing mode conversion condition is met. If the billing mode conversion condition is met, step 106 is executed. If not, the bill data can be generated according to the default billing mode. Optionally, the default billing mode can be on-demand billing.

[0064] Step 106: When the billing mode conversion condition is met, query the target billing mode corresponding to the target resource, and generate bill data corresponding to the target account based on the target billing mode and the usage information of the target resource.

[0065] In an embodiment of the present application, when the billing mode conversion conditions are met, the server can query the target billing mode corresponding to the target resource. The target billing mode is the converted billing mode. For example, the default billing mode can be on-demand billing, and the target billing mode is package period billing. The embodiment of the present application does not limit the default billing mode and the target billing mode. The server can determine that the target billing mode is mapped to the resource billing parameters (such as unit billing data) under the default billing model, and then generate the billing data corresponding to the target account based on the mapped resource billing parameters and the usage information of the target resources.

[0066] In this solution, the resource identifiers of the target account and the target resource can be used to automatically determine whether the billing mode conversion conditions are currently met. If the billing mode conversion conditions are met, a bill is automatically generated according to the converted billing mode without the need for manual entry or processing, thereby improving the flexibility and efficiency of bill generation.

[0067] Optionally, based on the resource identifier of the target account and the target resource, determine whether the billing mode conversion conditions are met, including: based on the resource identifier of the target resource, determine the target product object identifier, and obtain a list corresponding to the target product object identifier; when the list contains the target account, obtain the billing configuration information corresponding to the target product object identifier, and determine whether the billing mode conversion conditions are met based on the billing configuration information.

[0068] In an embodiment of the present application, the server can query the target product object identifier corresponding to the resource identifier of the target resource based on the correspondence between the pre-stored resource identifier and the product object identifier, and then obtain a list corresponding to the target product object identifier. The list is used to record accounts with billing mode conversion authority. The server can determine whether the list contains the target account. If not, billing data can be generated according to the default billing mode. If included, the billing configuration information corresponding to the target product object identifier is obtained, and based on the billing configuration information, it is further confirmed whether the target product object meets the billing mode conversion conditions.

[0069] In this solution, based on information of multiple dimensions such as the billing configuration information corresponding to the target account and the target product object identifier, it is possible to identify whether the billing mode conversion conditions are met, thereby improving the accuracy of the judgment and ensuring the accuracy of the ultimately generated bill data.

[0070] Optionally, the billing configuration information includes at least a mode conversion tag, and determining whether the billing mode conversion condition is met based on the billing configuration information includes: parsing the billing configuration information to obtain the mode conversion tag corresponding to the target account; if the mode conversion tag indicates that the mode conversion is allowed, determining that the billing mode conversion condition is met; if the mode conversion tag indicates that the mode conversion is not allowed, determining that the billing mode conversion condition is not met.

[0071] In the embodiment of the present application, the billing configuration information may be as shown in Table 1.

[0072] Table 1

[0073] Product Identification Product Name Price per demand Unit of measurement Monthly price Mode conversion tags Discount Rate 123 8-core 32G cloud host 197.64 Hour 0 no 0.15 234 1 core 1G cloud host 1.4 Hour 672 yes 0.15

[0074] The server can parse the billing configuration information to obtain the mode conversion tag corresponding to the target account. If the mode conversion tag indicates that the mode conversion is allowed (for example, yes, or 1), it is determined that the billing mode conversion condition is met; if the mode conversion tag indicates that the mode conversion is not allowed (for example, no, or 0), it is determined that the billing mode conversion condition is not met.

[0075] In this solution, the server can automatically calculate the converted unit billing data based on the rule mapping relationship between the target billing model and the default billing model, and then generate the bill data. The technicians only need to configure the labels and list, without having to perform repeated business processing procedures, which improves the efficiency of bill generation.

[0076] Optionally, based on the target billing model and the usage information of the target resources, billing data corresponding to the target account is generated, including: determining the target unit billing data corresponding to the target resources based on the billing rule information corresponding to the target billing model; generating billing data corresponding to the target account based on the target unit billing data and the usage information of the target resources.

[0077] In an embodiment of the present application, the server can calculate the target unit billing data after the conversion of the billing model of the target resource based on the billing rule information corresponding to the target billing mode and the rule mapping relationship between the target billing mode and the default billing mode. For example, the default billing mode can be on-demand billing, the unit time is hours, and the target billing mode is monthly billing (X), then the unit billing data can be calculated as X / 30 / 24. The server can calculate the product of the target unit billing data and the usage information of the target resource to obtain the billing data corresponding to the target account. Among them, the discount in Table 1 is an optional item. If there is a discount item, the product needs to be multiplied by the discount parameter to obtain the billing data corresponding to the target account.

[0078] In an example, if the default billing mode is on-demand (second) billing, the billing data is: usage * standard monthly unit price * 12 / 365 / 24 / 3600 * discount; if the default billing mode is on-demand (hour) billing, the billing data is: usage * standard monthly unit price * 12 / 365 / 24 * discount; if the default billing mode is on-demand (day) billing, the billing data is: usage * standard monthly unit price * 12 / 365 * discount; if the default billing mode is on-demand (month) billing, the billing data is: usage * standard monthly unit price * discount.

[0079] In this solution, the server can automatically calculate the converted unit billing data based on the rule mapping relationship between the target billing model and the default billing model, and then generate the bill data. The technicians only need to configure the labels and list, without having to perform repeated business processing procedures, which improves the efficiency of bill generation.

[0080] Optionally, the method also includes: displaying an account configuration interface, which includes account configuration options; in response to a trigger operation of the account configuration options, obtaining a target account to be configured, and verifying the target account; if the target account passes the verification, adding the target account to a preset list.

[0081] In an embodiment of the present application, the server can respond to the trigger operation of the account configuration option of the business personnel, obtain the target account to be configured, and verify the target account. For example, the security of the target account, whether it is an available account, etc. can be verified. If the target account passes the verification, the target account is added to the preset list. If the target account fails the verification, an alarm prompt message is output, and the alarm prompt message includes the verification failure reason corresponding to the target account, such as the target account is a risky account, or the target account is unavailable, etc.

[0082] In this solution, the server can automatically calculate the converted unit billing data based on the rule mapping relationship between the target billing mode and the default billing mode, and then generate the bill data. The technicians only need to configure the labels and the list, without having to perform repeated business processing procedures, which improves the efficiency of bill generation. In addition, when the business personnel configure the list, the server can automatically verify the account to ensure that the configured account is reliable and valid.

[0083] Optionally, the method further includes: displaying description information of the target product object in response to a query operation on the target product object identifier; and setting a mode conversion tag in the billing configuration information corresponding to the target product object based on the description information of the target product object.

[0084] In an embodiment of the present application, the server may display the description information of the target product object in response to a query operation for the target product object identifier, wherein the description information may refer to Table 1 and include relevant parameter information of the default billing mode. Then, based on the description information of the target product object, it may be determined whether the target product object can switch the billing mode, and a mode conversion label may be configured according to the determination result. Among them, if the target product object can switch the billing mode, the target billing model corresponding to the target product object may be further determined and associated. For example, relevant information of the target billing model may be added to the description information, such as relevant parameter information of the package period billing model.

[0085] In this solution, the server can automatically calculate the converted unit billing data based on the rule mapping relationship between the target billing model and the default billing model, and then generate the bill data. The technicians only need to maintain the labels and list without having to perform repeated business processing procedures, which improves the efficiency of bill generation.

[0086] As shown in FIG. 2 , the embodiment of the present application provides an example of a method for generating bill data, including the following steps:

[0087] Step 201: Receive a call bill message sent by a target account.

[0088] The call record message includes the usage information of the target account and target resources.

[0089] Step 202: determine the target product object identifier based on the resource identifier of the target resource, and obtain a list of names corresponding to the target product object identifier.

[0090] Step 203, determining whether the name list contains the target account.

[0091] If yes, execute step 204 , otherwise, execute step 207 .

[0092] Step 204, obtain and parse the billing configuration information corresponding to the target product object identifier to obtain the mode conversion tag corresponding to the target account.

[0093] Step 205: determine whether to perform mode conversion according to the mode conversion tag.

[0094] If yes, execute step 206 , otherwise, execute step 207 .

[0095] Step 206, querying the target billing mode corresponding to the target resource, and determining the target unit billing data corresponding to the target resource based on the billing rule information corresponding to the package period billing mode.

[0096] Step 207: Determine the target unit billing data corresponding to the target resource according to the billing rule information corresponding to the on-demand billing mode.

[0097] Step 208: Generate billing data corresponding to the target account based on the target unit billing data and the target resource usage information.

[0098] It should be understood that, although the steps in the flowcharts involved in the above embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0099] Based on the same inventive concept, the embodiment of the present application also provides a billing data generation device for implementing the billing data generation method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the one or more billing data generation device embodiments provided below can refer to the limitations of the billing data generation method above, and will not be repeated here.

[0100] In an exemplary embodiment, as shown in FIG3 , a bill data generating device is provided, comprising: a receiving module 310, a determining module 320 and a generating module 330, wherein:

[0101] A receiving module, configured to receive a call bill message of a target account, wherein the call bill message includes usage information of the target account and target resources;

[0102] A determination module, configured to determine whether a billing mode conversion condition is met based on the target account and the resource identifier of the target resource;

[0103] A generation module is used to query the target billing mode corresponding to the target resource when the billing mode conversion condition is met, and generate bill data corresponding to the target account based on the target billing mode and usage information of the target resource.

[0104] In one embodiment, the determining module 320 is specifically configured to:

[0105] Based on the resource identifier of the target resource, determine the target product object identifier, and obtain a list of names corresponding to the target product object identifier;

[0106] In the case that the target account number is included in the list, the billing configuration information corresponding to the target product object identifier is obtained, and it is determined whether the billing mode conversion condition is met based on the billing configuration information.

[0107] In one embodiment, the charging configuration information at least includes a mode conversion tag, and the determination module 320 is specifically configured to:

[0108] Parsing the billing configuration information to obtain a mode conversion tag corresponding to the target account;

[0109] If the mode conversion tag indicates that the mode conversion is allowed, determining that the charging mode conversion condition is met;

[0110] If the mode conversion tag indicates that the mode conversion is not allowed, it is determined that the charging mode conversion condition is not met.

[0111] In one embodiment, the generating module 330 is specifically used for:

[0112] Determining target unit billing data corresponding to the target resource based on the billing rule information corresponding to the target billing mode;

[0113] Based on the target unit billing data and the usage information of the target resource, billing data corresponding to the target account is generated.

[0114] In one embodiment, the device further comprises:

[0115] A first display module is used to display an account configuration interface, wherein the account configuration interface includes account configuration options;

[0116] A first configuration module, configured to obtain a target account to be configured in response to a triggering operation of the account configuration option, and perform verification processing on the target account;

[0117] The adding module is used to add the target account to a preset list when the target account passes the verification.

[0118] In one embodiment, the device further comprises:

[0119] A second display module, configured to display description information of the target product object in response to a query operation on the target product object identifier;

[0120] The second configuration module is used to set a mode conversion tag in the billing configuration information corresponding to the target product object based on the description information of the target product object.

[0121] Each module in the above-mentioned bill data generation device can be implemented in whole or in part by software, hardware or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute the operations corresponding to each module.

[0122] In an exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be shown in FIG4. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected via a system bus, and the communication interface is connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for generating billing data is implemented.

[0123] Those skilled in the art will understand that the structure shown in FIG. 4 is merely a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0124] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0125] Receiving a call record message of a target account, wherein the call record message includes usage information of the target account and target resources;

[0126] Determining whether a billing mode switching condition is met based on the target account and the resource identifier of the target resource;

[0127] When the billing mode conversion condition is met, the target billing mode corresponding to the target resource is queried, and based on the target billing mode and usage information of the target resource, bill data corresponding to the target account is generated.

[0128] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0129] Based on the resource identifier of the target resource, determine the target product object identifier, and obtain a list of names corresponding to the target product object identifier;

[0130] In the case that the target account number is included in the list, the billing configuration information corresponding to the target product object identifier is obtained, and it is determined whether the billing mode conversion condition is met based on the billing configuration information.

[0131] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0132] Parsing the billing configuration information to obtain a mode conversion tag corresponding to the target account;

[0133] If the mode conversion tag indicates that the mode conversion is allowed, determining that the charging mode conversion condition is met;

[0134] If the mode conversion tag indicates that the mode conversion is not allowed, it is determined that the charging mode conversion condition is not met.

[0135] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0136] Determining target unit billing data corresponding to the target resource based on the billing rule information corresponding to the target billing mode;

[0137] Based on the target unit billing data and the usage information of the target resource, billing data corresponding to the target account is generated.

[0138] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0139] Displaying an account configuration interface, wherein the account configuration interface includes account configuration options;

[0140] In response to the triggering operation of the account configuration option, obtaining a target account to be configured, and performing verification processing on the target account;

[0141] When the target account passes the verification, the target account is added to a preset list.

[0142] In one embodiment, when the processor executes the computer program, the processor further implements the following steps:

[0143] In response to a query operation on a target product object identifier, displaying description information of the target product object;

[0144] Based on the description information of the target product object, a mode conversion tag is set in the billing configuration information corresponding to the target product object.

[0145] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0146] Receiving a call record message of a target account, wherein the call record message includes usage information of the target account and target resources;

[0147] Determining whether a billing mode switching condition is met based on the target account and the resource identifier of the target resource;

[0148] When the billing mode conversion condition is met, the target billing mode corresponding to the target resource is queried, and based on the target billing mode and usage information of the target resource, bill data corresponding to the target account is generated.

[0149] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0150] Based on the resource identifier of the target resource, determine the target product object identifier, and obtain a list of names corresponding to the target product object identifier;

[0151] In the case that the target account number is included in the list, the billing configuration information corresponding to the target product object identifier is obtained, and it is determined whether the billing mode conversion condition is met based on the billing configuration information.

[0152] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0153] Parsing the billing configuration information to obtain a mode conversion tag corresponding to the target account;

[0154] If the mode conversion tag indicates that the mode conversion is allowed, determining that the charging mode conversion condition is met;

[0155] If the mode conversion tag indicates that the mode conversion is not allowed, it is determined that the charging mode conversion condition is not met.

[0156] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0157] Determining target unit billing data corresponding to the target resource based on the billing rule information corresponding to the target billing mode;

[0158] Based on the target unit billing data and the usage information of the target resource, billing data corresponding to the target account is generated.

[0159] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0160] Displaying an account configuration interface, wherein the account configuration interface includes account configuration options;

[0161] In response to the triggering operation of the account configuration option, obtaining a target account to be configured, and performing verification processing on the target account;

[0162] When the target account passes the verification, the target account is added to a preset list.

[0163] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0164] In response to a query operation on a target product object identifier, displaying description information of the target product object;

[0165] Based on the description information of the target product object, a mode conversion tag is set in the billing configuration information corresponding to the target product object.

[0166] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0167] Receiving a call record message of a target account, wherein the call record message includes usage information of the target account and target resources;

[0168] Determining whether a billing mode switching condition is met based on the target account and the resource identifier of the target resource;

[0169] When the billing mode conversion condition is met, the target billing mode corresponding to the target resource is queried, and based on the target billing mode and usage information of the target resource, bill data corresponding to the target account is generated.

[0170] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0171] Based on the resource identifier of the target resource, determine the target product object identifier, and obtain a list of names corresponding to the target product object identifier;

[0172] In the case that the target account number is included in the list, the billing configuration information corresponding to the target product object identifier is obtained, and it is determined whether the billing mode conversion condition is met based on the billing configuration information.

[0173] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0174] Parsing the billing configuration information to obtain a mode conversion tag corresponding to the target account;

[0175] If the mode conversion tag indicates that the mode conversion is allowed, determining that the charging mode conversion condition is met;

[0176] If the mode conversion tag indicates that the mode conversion is not allowed, it is determined that the charging mode conversion condition is not met.

[0177] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0178] Determining target unit billing data corresponding to the target resource based on the billing rule information corresponding to the target billing mode;

[0179] Based on the target unit billing data and the usage information of the target resource, billing data corresponding to the target account is generated.

[0180] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0181] Displaying an account configuration interface, wherein the account configuration interface includes account configuration options;

[0182] In response to the triggering operation of the account configuration option, obtaining a target account to be configured, and performing verification processing on the target account;

[0183] When the target account passes the verification, the target account is added to a preset list.

[0184] In one embodiment, when the computer program is executed by a processor, the following steps are also implemented:

[0185] In response to a query operation on a target product object identifier, displaying description information of the target product object;

[0186] Based on the description information of the target product object, a mode conversion tag is set in the billing configuration information corresponding to the target product object.

[0187] It should be noted that the user information (including but not limited to user device identification, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0188] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0189] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0190] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for generating billing data, characterized in that: The method comprises: Receiving a call record message of a target account, wherein the call record message includes usage information of the target account and target resources; Determining whether a billing mode switching condition is met based on the target account and the resource identifier of the target resource; When the billing mode conversion condition is met, the target billing mode corresponding to the target resource is queried, and based on the target billing mode and usage information of the target resource, bill data corresponding to the target account is generated.

2. The method according to claim 1, characterized in that: The determining whether a billing mode switching condition is met based on the target account and the resource identifier of the target resource includes: Based on the resource identifier of the target resource, determine the target product object identifier, and obtain a list of names corresponding to the target product object identifier; In the case that the target account number is included in the list, the billing configuration information corresponding to the target product object identifier is obtained, and it is determined whether the billing mode conversion condition is met based on the billing configuration information.

3. The method according to claim 2, characterized in that The charging configuration information at least includes a mode conversion tag, and determining whether a charging mode conversion condition is met based on the charging configuration information includes: Parsing the billing configuration information to obtain a mode conversion tag corresponding to the target account; If the mode conversion tag indicates that the mode conversion is allowed, determining that the billing mode conversion condition is met; If the mode conversion tag indicates that the mode conversion is not allowed, it is determined that the charging mode conversion condition is not met.

4. The method according to claim 1, characterized in that The generating, based on the target billing mode and the usage information of the target resource, bill data corresponding to the target account includes: Determining target unit billing data corresponding to the target resource based on the billing rule information corresponding to the target billing mode; Based on the target unit billing data and the usage information of the target resource, billing data corresponding to the target account is generated.

5. The method according to claim 2, characterized in that: The method further comprises: Displaying an account configuration interface, wherein the account configuration interface includes account configuration options; In response to the triggering operation of the account configuration option, obtaining a target account to be configured, and performing verification processing on the target account; When the target account passes the verification, the target account is added to a preset list.

6. The method according to claim 3, characterized in that The method further comprises: In response to a query operation on a target product object identifier, displaying description information of the target product object; Based on the description information of the target product object, a mode conversion tag is set in the billing configuration information corresponding to the target product object.

7. A bill data generating device, characterized in that: The device comprises: A receiving module, configured to receive a call bill message of a target account, wherein the call bill message includes usage information of the target account and target resources; A determination module, configured to determine whether a billing mode conversion condition is met based on the target account and the resource identifier of the target resource; A generation module is used to query the target billing mode corresponding to the target resource when the billing mode conversion condition is met, and generate bill data corresponding to the target account based on the target billing mode and usage information of the target resource.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.