Custom charging report generation and management method based on modular architecture

Abstract

The invention discloses a customized charging report generation and management method based on a modular architecture, and aims to solve the problems of insufficient flexibility and poor adaptability of a traditional charging system. According to the method, by constructing a modular charging system, charging elements, entities, rules and conditions are independently designed, and flexible configuration and dynamic binding are supported; a user can customize report fields and dimensions according to business requirements, and the system automatically generates and exports multi-format reports to meet diversified requirements; according to the design, the flexibility, the maintainability and the expansibility of the system are remarkably improved, and variable business environments are effectively coped with.

Description

Technical Field

[0001] The present invention relates to the technical field of intelligent report generation, and particularly to a method for generating and managing custom billing reports based on a modular architecture. Background Art

[0002] Existing billing systems usually rely on fixed report formats, lacking flexibility and adaptability, and unable to effectively support diverse and complex billing requirements. In traditional billing models, billing rules are highly coupled with business documents, resulting in the need for large-scale system reconstruction or manual calculation every time a billing rule is modified or a new business is added. This not only has low efficiency but is also error-prone. In addition, the complex relationships between different billing objects and the variable fee calculation logics also increase the complexity of the system.

[0003] Therefore, a flexible and scalable billing design solution is needed that can quickly adapt to different billing rules and report requirements in a changing business environment and can automatically generate custom reports that meet the requirements. Summary of the Invention

[0004] The purpose of this part is to outline some aspects of the embodiments of the present invention and briefly introduce some preferred embodiments. Some simplifications or omissions may be made in this part, as well as in the abstract and title of the present application, to avoid obscuring the purpose of this part, the abstract, and the title. However, such simplifications or omissions shall not be used to limit the scope of the present invention.

[0005] In view of the above existing problems, the present invention is proposed. Therefore, the present invention provides a method for generating and managing custom billing reports based on a modular architecture to solve the problems raised in the background art.

[0006] To solve the above technical problems, the present invention provides the following technical solution: A method for generating and managing custom billing reports based on a modular architecture, comprising:

[0007] Obtaining billing elements, billing entities, billing rules, and billing conditions, and constructing a modular billing system;

[0008] Configuring the billing rules and billing conditions according to business requirements, and binding them to the billing elements and billing entities;

[0009] Establishing a data model, defining billing contracts, billing sheets, and billing objects in the data model, and associating them with the modular billing system to obtain business documents. According to the configured billing rules and billing conditions, calculating the fees for the business documents to generate billing details;

[0010] Summarizing the billing details into the billing sheet and calculating the amount of the billing sheet;

[0011] Dynamically generate a custom report according to the report fields and dimensions selected by the user, and export the custom report in multiple formats to achieve the management of the report.

[0012] As a preferred solution of the custom billing report generation and management method based on a modular architecture according to the present invention, wherein: construct a modular billing system, including:

[0013] Create independently maintainable data tables or enumeration tables for the billing elements, billing entities, billing rules, and billing conditions respectively.

[0014] As a preferred solution of the custom billing report generation and management method based on a modular architecture according to the present invention, wherein: configure the billing rules and billing conditions, including:

[0015] Use the calculation method of fees, billing cycle, and billing unit as billing rules, use the billing events or status as billing conditions, and classify the billing conditions into categories based on user behavior, resource usage, and time.

[0016] As a preferred solution of the custom billing report generation and management method based on a modular architecture according to the present invention, wherein: define billing contracts, billing sheets, and billing objects in the data model, and associate them with the modular billing system to obtain business documents, including:

[0017] There is a one-to-many relationship between the billing contract and the billing sheet;

[0018] There is a one-to-one relationship between the billing contract and the billing object;

[0019] There is a one-to-many relationship between the billing contract and the billing rules;

[0020] There is a one-to-many relationship between the billing sheet and the billing entity.

[0021] As a preferred solution of the custom billing report generation and management method based on a modular architecture according to the present invention, wherein: generate billing details by calculating the fees of the business documents according to the configured billing rules and billing conditions, including:

[0022] The billing details = planned billing amount - preferential amount - adjusted amount;

[0023] Among them, the planned billing amount = billing price × billing value, the preferential amount = planned billing amount × preferential rate, and the adjusted amount is entered manually.

[0024] As a preferred solution of the custom billing report generation and management method based on a modular architecture according to the present invention, wherein: summarizing the billing details into a billing statement and calculating the amount of the billing statement, including:

[0025] The amount of the billing statement is corrected based on a preferential policy or manual adjustment.

[0026] As a preferred solution of the custom billing report generation and management method based on a modular architecture according to the present invention, wherein: dynamically generating a custom report according to the report fields and dimensions selected by the user, including:

[0027] The user selects report fields and dimensions through a graphical interface and binds the selected report fields and dimensions to the billing data source.

[0028] Compared with the prior art, the beneficial effects of the invention are:

[0029] 1. The present invention independently designs billing elements, entities, rules, and conditions, which can be flexibly combined, reducing the system coupling and enhancing the flexibility and maintainability;

[0030] 2. It supports users to dynamically configure billing rules and conditions according to actual needs to adapt to different billing scenarios and requirements;

[0031] 3. Through an optimized calculation logic and data processing architecture, high-efficiency calculation and report generation under a large amount of data are achieved;

[0032] 4. It supports multiple billing types and business documents, and can flexibly configure and adapt to multi-dimensional fee calculation logics, generating personalized billing reports according to different business requirements, reducing the complexity of manual intervention, and improving the calculation efficiency and scalability of the system. Description of the Drawings

[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts. Among them:

[0034] Figure 1 It is the overall flowchart of the custom billing report generation and management method based on a modular architecture according to an embodiment of the present invention;

[0035] Figure 2 It is the architecture diagram of the billing system of the custom billing report generation and management method based on a modular architecture according to an embodiment of the present invention;

[0036] Figure 3The flowchart of report generation for the custom billing report generation and management method based on a modular architecture according to an embodiment of the present invention;

[0037] Figure 4 The data model structure diagram of the custom billing report generation and management method based on a modular architecture according to an embodiment of the present invention. Detailed implementation manners

[0038] To make the above objects, features, and advantages of the present invention more obvious and understandable, the following will describe the detailed implementation manners of the present invention with reference to the accompanying drawings of the specification. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the scope of protection of the present invention.

[0039] In the following description, many specific details are set forth to fully understand the present invention. However, the present invention can also be implemented in other ways different from those described herein. Those skilled in the art can make similar extensions without departing from the connotation of the present invention. Therefore, the present invention is not limited by the specific embodiments disclosed below.

[0040] Secondly, the so-called "one embodiment" or "embodiment" herein refers to a specific feature, structure, or characteristic that can be included in at least one implementation manner of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it an individual or alternative embodiment mutually exclusive with other embodiments.

[0041] The present invention is described in detail with reference to the schematic diagrams. When detailing the embodiments of the present invention, for the sake of convenience of explanation, the cross-sectional views showing the device structure will be enlarged locally out of the general scale, and the schematic diagrams are only examples, which should not limit the scope of protection of the present invention herein. In addition, in actual production, three-dimensional spatial dimensions including length, width, and depth should be included.

[0042] At the same time, in the description of the present invention, it should be noted that the orientation or positional relationships indicated by terms such as "upper, lower, inner, and outer" are based on the orientation or positional relationships shown in the drawings. They are only for the convenience of describing the present invention and simplifying the description, rather than indicating or implying that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation. Therefore, it cannot be understood as a limitation to the present invention. In addition, the terms "first, second, or third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance.

[0043] Unless otherwise clearly defined and limited in the present invention, the terms "installation, connection, and coupling" shall be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral connection; it can also be a mechanical connection, an electrical connection, or a direct connection, and can also be indirectly connected through an intermediate medium, or can be the communication inside two components. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0044] Embodiment 1

[0045] Referring to Figures 1 to 4 , which is the first embodiment of the present invention. This embodiment provides a method for generating and managing customized billing reports based on a modular architecture, including:

[0046] S1. Obtain billing elements, billing entities, billing rules, and billing conditions, and construct a modular billing system;

[0047] Furthermore, create independently maintainable data tables or enumeration tables for the billing elements, billing entities, billing rules, and billing conditions respectively;

[0048] Specifically, create data tables for the billing elements, billing entities, billing rules, and billing conditions through a database management system, and set a primary key constraint for each table to ensure data uniqueness. For each field, an index can be added as needed to improve query efficiency;

[0049] Specifically, insert initial data into each table. For example, billing elements (such as "traffic fee"), billing entities (such as "User A"), billing rules (such as "charging by quantity"), and billing conditions (such as "usage exceeds 100GB") to ensure that the initial data covers typical business scenarios and is convenient for use when the system starts;

[0050] S2. Configure the billing rules and billing conditions according to business requirements, and bind them to the billing elements and billing entities;

[0051] Furthermore, use the calculation method of fees, billing cycle, and billing unit as billing rules, use the events or states of billing as billing conditions, and classify the billing conditions into categories based on user behavior, resource usage, and time;

[0052] Specifically, the calculation methods of the fees are as follows:

[0053] Charging by quantity: Calculate fees according to the actual usage. For example, a certain fee is charged per GB of traffic;

[0054] Charging by time: Calculate fees according to the usage time. For example, a fixed rate per hour;

[0055] Fixed fees: A fixed amount is charged regardless of usage volume or time, such as a monthly subscription fee;

[0056] Tiered billing: Billing is based on usage volume in segments. For example, the first 100 GB is charged at a lower rate, and the amount exceeding this is charged at a higher rate;

[0057] Specifically, the billing cycles are divided into the following types:

[0058] Monthly billing: Calculated on a monthly basis, and the fees for the previous month are settled on a fixed date each month (such as the 1st);

[0059] Annual billing: Calculated on an annual basis and settled on a fixed date each year;

[0060] Usage-based billing: Without a fixed cycle, it is settled in real-time or regularly according to the actual usage volume;

[0061] Customized cycle: Set according to business requirements, such as quarterly or bi-weekly;

[0062] Specifically, the billing units are divided into the following types:

[0063] Time units: Such as hours, days, weeks;

[0064] Resource units: Such as GB (traffic), MB (storage), number (number of users);

[0065] Service units: Such as the number of API calls, the number of messages sent;

[0066] Specifically, the billing conditions based on user behavior are as follows:

[0067] Trigger events: User registration, login, file upload, message sending, etc.;

[0068] Behavior frequency: The number of user operations. For example, logging in more than 10 times per month triggers additional billing;

[0069] For example, when a user sends a message each time, it is billed per message;

[0070] Specifically, the billing conditions based on resource usage are as follows:

[0071] Trigger status: Reaching a certain value in terms of storage space occupancy, bandwidth consumption, CPU usage rate, etc.;

[0072] Resource threshold: Triggered when the usage volume exceeds a preset value. For example, when the traffic exceeds 100 GB;

[0073] For example, for every 1 GB increase in storage space, a fixed fee is charged;

[0074] Specifically, the billing conditions based on time are as follows:

[0075] Trigger time: Fixed date (e.g., the 1st of each month), specific time period (e.g., peak hours);

[0076] Duration: Service usage duration, for example, continuous usage exceeding 1 hour;

[0077] For example, when using the service from 8:00 to 18:00 on weekdays, it is billed by the hour;

[0078] It should be noted that the configuration process associates the billing rules with the billing conditions to ensure that the rules are accurately applied when the conditions are met; for example, billing rule: billed by the hour, 5 yuan per hour, billing condition: based on time, from 8:00 to 18:00 every day; configuration result: within the working hours, 5 yuan is charged for each hour of service usage;

[0079] S3. Establish a data model, define a billing contract, a billing statement, and a billing object in the data model, and associate them with the modular billing system to obtain business documents. According to the configured billing rules and billing conditions, generate billing details by calculating the fees for the business documents;

[0080] Specifically, the data model contains the following relationships:

[0081] There is a one-to-many relationship between the billing contract and the billing statement;

[0082] There is a one-to-one relationship between the billing contract and the billing object;

[0083] There is a one-to-many relationship between the billing contract and the billing rules;

[0084] There is a one-to-many relationship between the billing statement and the billing entity;

[0085] Specifically, for the "one-to-many relationship between the billing contract and the billing statement" explanation, that is, one billing contract can correspond to multiple billing statements, but each billing statement can only correspond to one billing contract; for example, a customer signs a one-year service contract, and a billing statement will be generated monthly to record the monthly fees. The contract is fixed, but multiple billing statements will be generated over time;

[0086] Specifically, for the "one-to-one relationship between the billing contract and the billing object" explanation, that is, each billing contract is only associated with one billing object, and vice versa; for example, a customer signs an independent billing contract, and the contract corresponds one-to-one with the customer;

[0087] Specifically, for the "one-to-many relationship between the billing contract and the billing rules" explanation, that is, one billing contract can apply multiple billing rules, and each billing rule can be used by multiple contracts; for example, a contract may include both billing by flow and billing by time, and these two billing methods are defined by different billing rules respectively;

[0088] Specifically, for the description of "one-to-many relationship between the billing statement and the billing entity", that is, one billing statement can include multiple billing entities, and each billing entity can appear in multiple billing statements; for example, the billing statement for one month includes data traffic fees, storage fees, and user license fees, and these fees correspond to different billing entities respectively;

[0089] It should be noted that by establishing these relationships, the billing system can efficiently manage the associations among contracts, bills, rules, and entities, meeting complex business requirements;

[0090] S4. Summarize the billing details into the billing statement and calculate the amount of the billing statement;

[0091] Specifically, the billing details = the amount of the billing plan - the amount of the discount - the adjusted amount;

[0092] Among them, the amount of the billing plan = the billing price × the billing quantity, the amount of the discount = the amount of the billing plan × the discount rate, and the adjusted amount is entered manually;

[0093] Specifically, the amount of the billing statement is corrected based on the discount policy or manual adjustment;

[0094] It should be noted that the manual entry method of the adjusted amount allows the system to handle special situations, such as fee reduction after customer complaints;

[0095] S5. Dynamically generate a custom report according to the report fields and dimensions selected by the user, and export the custom report in multiple formats to manage the report;

[0096] Specifically, the user selects the report fields and dimensions through the graphical interface and binds the selected report fields and dimensions to the billing data source;

[0097] Specifically, the multiple-format export provides multiple export options such as PDF, Excel, and CSV;

[0098] It should be noted that the user can save the current selection of fields and dimensions for quickly generating the same report in the future. In addition, it supports setting the time for automatic report generation (such as daily or weekly), and notifying the user by email or other means to achieve the sharing function among users.

[0099] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code. The solutions in the embodiments of the present application can be implemented in various computer languages. For example, object-oriented programming languages such as Java and interpreted scripting languages such as JavaScript, etc.

[0100] This application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram, and the combination of flows and / or blocks in the flowchart and / or block diagram, can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for realizing the functions specified in one Figure 1 flow or multiple flows and / or blocks Figure 1 or a device for realizing the functions specified in one block or multiple blocks.

[0101] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured product including an instruction device, and the instruction device realizes the functions specified in one Figure 1 flow or multiple flows and / or blocks Figure 1 or a device for realizing the functions specified in one block or multiple blocks.

[0102] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for realizing the functions specified in one Figure 1 flow or multiple flows and / or blocks Figure 1 or a device for realizing the functions specified in one block or multiple blocks.

[0103] Although the preferred embodiments of the present application have been described, those skilled in the art can make additional changes and modifications to these embodiments once they know the basic creative concept. Therefore, the appended claims are intended to be construed to include the preferred embodiments as well as all changes and modifications falling within the scope of the present application.

[0104] Obviously, those skilled in the art can make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalent technologies, this application is also intended to cover these changes and modifications.

Claims

1. A method for generating and managing customized billing reports based on a modular architecture, characterized in that, Including: Obtain charging elements, charging entities, charging rules, and charging conditions, and construct a modular charging system; According to business requirements, configure the charging rules and charging conditions, and bind them to the charging elements and charging entities; Establish a data model, define charging contracts, charging bills, and charging objects in the data model, associate them with the modular charging system to obtain business documents, and generate charging details by calculating the fees for the business documents according to the configured charging rules and charging conditions; Summarize the charging details into the charging bill and calculate the amount of the charging bill; Dynamically generate a custom report according to the report fields and dimensions selected by the user, and export the custom report in multiple formats to realize the management of the report.

2. The custom billing statement generation and management method based on a modular architecture according to claim 1, characterized in that Construct a modular charging system, including: Create independently maintainable data tables or enumeration tables for the charging elements, charging entities, charging rules, and charging conditions respectively.

3. The custom billing report generation and management method based on a modular architecture according to claim 1, characterized in that Configure the charging rules and charging conditions, including: Use the calculation method of fees, charging cycle, and charging unit as the charging rules, use the charging events or status as the charging conditions, and classify the charging conditions into categories based on user behavior, resource usage, and time.

4. The custom billing statement generation and management method based on a modular architecture according to claim 1 or 2, characterized in that Define charging contracts, charging bills, and charging objects in the data model, and associate them with the modular charging system to obtain business documents, including: There is a one-to-many relationship between the charging contract and the charging bill; There is a one-to-one relationship between the charging contract and the charging object; There is a one-to-many relationship between the charging contract and the charging rules; There is a one-to-many relationship between the charging bill and the charging entity.

5. The custom billing statement generation and management method based on a modular architecture according to claim 1, characterized in that, Generate charging details by calculating the fees for the business documents according to the configured charging rules and charging conditions, including: The charging details = planned charging amount - preferential amount - adjustment amount; Among them, the planned charging amount = charging price × charging value, the preferential amount = planned charging amount × preferential rate, and the adjustment amount is entered manually.

6. The custom billing report generation and management method based on a modular architecture according to claim 1, wherein Summarize the charging details into the charging bill and calculate the amount of the charging bill, including: The amount of the charging bill is corrected based on the preferential policy or manual adjustment.

7. The custom billing report generation and management method based on a modular architecture according to claim 1, wherein Dynamically generate a custom report according to the report fields and dimensions selected by the user, including: The user selects the report fields and dimensions through the graphical interface and binds the selected report fields and dimensions to the charging data source.

Images