Bill generation method and device

Abstract

The embodiment of the invention provides a bill generation method and device. The bill generation method comprises the following steps: firstly, in response to a plurality of pieces of charging data sent by a plurality of charging systems, obtaining a plurality of pieces of standard data corresponding to the plurality of charging systems based on a pre-configured data conversion standard, and then in response to a received summarizing instruction sent by a settlement system, obtaining a plurality of pieces of standard data corresponding to the plurality of charging systems; to-be-settled data corresponding to the summarizing instruction is selected from the multiple standard data, then a summarizing task corresponding to the to-be-settled data is generated, finally, the to-be-settled data is settled and summarized based on the summarizing task, and a summarizing bill corresponding to the to-be-settled data is generated. According to the invention, the charging data scattered in each charging system can be accessed by using a simple standard process, and the charging data is converted into the standard data by using the pre-configured data conversion standard, so that the aggregation of massive charging data in different forms is realized.

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the fields of computer technology and Internet technology, specifically to the fields of bill aggregation technology and data processing technology, and especially to a bill generation method and device. Background Art

[0002] Each production system in logistics has its own billing and settlement module, and the business operates independently to form a closed loop. With the opening of logistics, various business departments began to integrate and adjust, and the financial settlement scattered across various business lines was merged into one department. Since each business line has a settlement system, every time the settlement and reconciliation with the merchant, the settlement staff needs to switch operations between different systems, and each system has different operating procedures and inconsistent bill templates, which seriously affects the efficiency of settlement work and wastes settlement resources.

[0003] In view of this problem, the settlement system was finally integrated. Due to the price contracts of the signed merchants, each contract has a different price model and operation model, which requires the use of a high-performance ORACLE database that can support massive data calculations. However, the hardware procurement cost of the ORACLE database server used in core businesses such as finance is high, and high-performance disk storage is required. For example, the initial procurement cost of using an independent FC SAN optical disk is around one million. In addition to the procurement cost, ORACLE operation and maintenance costs, software license fees, etc. are also a large cost investment. Summary of the invention

[0004] Embodiments of the present disclosure provide a bill generation method, apparatus, electronic device, and computer-readable medium.

[0005] In a first aspect, an embodiment of the present disclosure provides a bill generation method, the method comprising: in response to receiving multiple billing data sent by multiple billing systems, based on a pre-configured data conversion standard, obtaining multiple standard data corresponding to the multiple billing systems; in response to receiving a summary instruction sent by a settlement system, selecting data to be settled corresponding to the summary instruction from the multiple standard data; generating a summary task corresponding to the data to be settled; based on the summary task, performing settlement summary processing on the data to be settled, and generating a summary bill corresponding to the data to be settled.

[0006] In some embodiments, in response to receiving multiple billing data sent by multiple billing systems, multiple standard data corresponding to the multiple billing systems are obtained based on a pre-configured data conversion standard, including: in response to receiving multiple billing data sent by multiple billing systems based on a standard interface, the multiple billing data are determined as multiple standard data corresponding to the multiple billing systems; or, in response to receiving multiple billing data sent by multiple billing systems based on a message queue, based on a pre-configured data conversion standard, the multiple billing data are subjected to standard conversion to obtain multiple standard data corresponding to the multiple billing data.

[0007] In some embodiments, based on the summary task, settlement summary processing is performed on the data to be settled, and a summary bill corresponding to the data to be settled is generated, including: based on the summary task, using the review task model to perform data verification on the data to be settled; in response to determining that the data to be settled passes the data verification, using the special task model to perform special nature judgment on the data to be settled; in response to determining that the data to be settled is not a special type of data, settlement summary processing is performed on the data to be settled based on the bill summary model, and a summary bill corresponding to the data to be settled is generated.

[0008] In some embodiments, based on the summary task, settlement summary processing is performed on the data to be settled, and a summary bill corresponding to the data to be settled is generated, which also includes: in response to determining that the data to be settled is a special type of data, data processing is performed on the data to be settled based on a special task model; settlement summary processing is performed on the processed data to be settled based on a bill summary model, and a summary bill corresponding to the data to be settled is generated.

[0009] In some embodiments, a summary task includes multiple sub-summary tasks; and, generating a summary task corresponding to the data to be settled includes: determining whether the data to be settled meets the task splitting conditions; splitting the data to be settled in response to determining that the data to be settled meets the task splitting conditions; generating multiple sub-summary tasks based on multiple split data corresponding to the data to be settled; and, based on the summary task, performing settlement summary processing on the data to be settled, and generating a summary bill corresponding to the data to be settled, including: based on multiple sub-summary tasks, performing settlement summary processing on multiple split data respectively, and generating multiple sub-bills for multiple split data; generating a summary bill corresponding to the data to be settled based on multiple sub-bills.

[0010] In some embodiments, the method also includes: calling back the summary bill based on the callback task model to determine whether the summary bill is settled successfully; in response to determining that the summary bill is settled successfully, generating a bill change task corresponding to the data to be settled; based on the bill change task, sending a prompt message indicating that the settlement of the data to be settled is completed to the billing system corresponding to the data to be settled.

[0011] In some embodiments, the method further includes: in response to determining that the summary bill settlement has failed, generating a bill cancellation task corresponding to the data to be settled; based on the bill cancellation task, sending a prompt message indicating that the settlement of the data to be settled has failed to the billing system corresponding to the data to be settled.

[0012] In some embodiments, the method further includes: in response to determining to perform settlement summary processing on the data to be settled, counting the number of failures of the summary task; determining whether the number of failures exceeds a preset threshold; in response to the number of failures indeed exceeding the preset threshold, terminating the summary task, and sending an alarm message corresponding to the summary task.

[0013] In some embodiments, the method also includes: in response to generating a summary bill corresponding to the data to be settled, obtaining access frequencies of multiple standard data; based on the access frequencies of the multiple standard data, determining data statuses of the multiple standard data; and based on the data statuses of the multiple standard data, storing the multiple standard data in layers.

[0014] In some embodiments, the method further includes: determining whether the current system information satisfies the expansion condition; in response to the current system information indeed satisfying the expansion condition, performing expansion processing on the application containers corresponding to the plurality of standard data through the elastic platform.

[0015] In some embodiments, the method further includes: in response to obtaining multiple summary bills corresponding to the multiple billing data, performing wide table processing on the multiple billing data and the multiple summary bills respectively to generate multiple honeycomb processed wide tables.

[0016] In some embodiments, the method further includes: in response to receiving a data processing operation from a user, determining target standard data corresponding to the data processing operation; and based on the data processing operation, performing data processing on the target standard data to obtain new standard data.

[0017] In a second aspect, an embodiment of the present disclosure provides a bill generating device, which includes: an acquisition module, configured to, in response to receiving multiple billing data sent by multiple billing systems, acquire multiple standard data corresponding to multiple billing systems based on a pre-configured data conversion standard; a selection module, configured to, in response to receiving a summary instruction sent by a settlement system, select data to be settled corresponding to the summary instruction from multiple standard data; a generation module, configured to generate a summary task corresponding to the data to be settled; based on the summary task, perform settlement summary processing on the data to be settled, and generate a summary bill corresponding to the data to be settled.

[0018] In some embodiments, the acquisition module is further configured to: in response to receiving multiple billing data sent by multiple billing systems based on a standard interface, determine the multiple billing data as multiple standard data corresponding to the multiple billing systems; or, in response to receiving multiple billing data sent by multiple billing systems based on a message queue, perform standard conversion on the multiple billing data based on a pre-configured data conversion standard to obtain multiple standard data corresponding to the multiple billing data.

[0019] In some embodiments, the generation module is further configured to: based on the summary task, perform data verification on the data to be settled using the review task model; in response to determining that the data to be settled passes the data verification, perform special nature judgment on the data to be settled using the special task model; in response to determining that the data to be settled is not special type data, perform settlement summary processing on the data to be settled based on the bill summary model, and generate a summary bill corresponding to the data to be settled.

[0020] In some embodiments, the generation module is further configured to: in response to determining that the data to be settled is a special type of data, perform data processing on the data to be settled based on a special task model; perform settlement summary processing on the processed data to be settled based on a bill summary model, and generate a summary bill corresponding to the data to be settled.

[0021] In some embodiments, the summary task includes multiple sub-summary tasks; and the generation module is further configured to: determine whether the data to be settled meets the task splitting conditions; in response to determining that the data to be settled meets the task splitting conditions, split the data to be settled; based on the multiple split data corresponding to the data to be settled, generate multiple sub-summary tasks; and, based on the multiple sub-summary tasks, respectively perform settlement summary processing on the multiple split data to generate multiple sub-bills for the multiple split data; based on the multiple sub-bills, generate a summary bill corresponding to the data to be settled.

[0022] In some embodiments, the device also includes: a judgment module, configured to call back the summary bill based on the callback task model to determine whether the summary bill is settled successfully; a generation module, further configured to generate a bill change task corresponding to the data to be settled in response to determining that the summary bill is settled successfully; a sending module, configured to send a prompt message indicating that the settlement of the data to be settled is completed to the billing system corresponding to the data to be settled based on the bill change task.

[0023] In some embodiments, the generation module is further configured to generate a bill cancellation task corresponding to the data to be settled in response to determining that the summary bill settlement has failed; the sending module is further configured to send a prompt message indicating the failure of settlement of the data to be settled to the billing system corresponding to the data to be settled based on the bill cancellation task.

[0024] In some embodiments, the device also includes: a statistical module, configured to count the number of failures of the summary task in response to determining that settlement summary processing is to be performed on the data to be settled; a judgment module, configured to judge whether the number of failures exceeds a preset threshold; a sending module, configured to terminate the summary task in response to the number of failures actually exceeding the preset threshold, and send an alarm message corresponding to the summary task.

[0025] In some embodiments, the device also includes: an acquisition module, configured to acquire access frequencies of multiple standard data in response to generating a summary bill corresponding to the data to be settled; a determination module, configured to determine data statuses of multiple standard data based on the access frequencies of multiple standard data; and a storage module, configured to perform hierarchical storage of multiple standard data based on the data statuses of multiple standard data.

[0026] In some embodiments, the device also includes: a judgment module configured to judge whether the current system information meets the expansion conditions; an expansion module configured to expand the application containers corresponding to multiple standard data through an elastic platform in response to the current system information meeting the expansion conditions.

[0027] In some embodiments, the generation module is further configured to: in response to obtaining multiple summary bills corresponding to multiple billing data, perform wide table processing on the multiple billing data and the multiple summary bills respectively to generate multiple honeycomb processed wide tables.

[0028] In some embodiments, the device also includes: a determination module, configured to determine the target standard data corresponding to the data processing operation in response to receiving the user's data processing operation; a processing module, configured to perform data processing on the target standard data based on the data processing operation to obtain new standard data.

[0029] In a third aspect, an embodiment of the present disclosure provides an electronic device, comprising: one or more processors; a storage device on which one or more programs are stored; when the one or more programs are executed by one or more processors, the one or more processors implement the bill generation method described in any embodiment of the first aspect.

[0030] In a fourth aspect, an embodiment of the present disclosure provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the bill generation method as described in any embodiment of the first aspect.

[0031] The bill generation method provided by the embodiment of the present disclosure, the above-mentioned execution subject first responds to receiving multiple billing data sent by multiple billing systems, obtains multiple standard data corresponding to the multiple billing systems based on a pre-configured data conversion standard, and then responds to receiving a summary instruction sent by the settlement system, selects the data to be settled corresponding to the summary instruction from the multiple standard data, and then generates a summary task corresponding to the data to be settled. Finally, based on the summary task, the data to be settled is settled and summarized, and a summary bill corresponding to the data to be settled is generated. The billing data scattered in various billing systems can be connected using a simple standard process, and the billing data can be converted into standard data using a pre-configured data conversion standard, so that massive billing data in different forms can be aggregated, and the settlement and aggregation of massive data can be completed without the support of ORACLE database. The storage cost and computing cost are controlled within a certain range, so that the settlement and aggregation for each billing system can be efficiently carried out in one system, thereby improving the efficiency and flexibility of bill generation. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Other features, objects and advantages of the present disclosure will become more apparent from the detailed description of non-limiting embodiments made with reference to the following drawings:

[0033] Figure 1 is an exemplary system architecture diagram in which an embodiment of the present disclosure may be applied;

[0034] Figure 2 is a flow chart of an embodiment of a bill generation method according to the present disclosure;

[0035] Figure 3 is a flow chart of an embodiment of performing settlement aggregation processing on data to be settled according to the present disclosure;

[0036] Figure 4 is a flow chart of another embodiment of a bill generation method according to the present disclosure;

[0037] Figure 5 is a flow chart of an embodiment of sending prompt information according to the present disclosure;

[0038] Figure 6 is a flow chart of an embodiment of sending alarm information according to the present disclosure;

[0039] Figure 7 is a flow chart of an embodiment of hierarchical storage of multiple standard data according to the present disclosure;

[0040] Figure 8 is a structural schematic diagram of an embodiment of a bill generating device according to the present disclosure;

[0041] Fig. 9 It is a schematic diagram of the structure of an electronic device suitable for implementing the embodiments of the present disclosure. DETAILED DESCRIPTION

[0042] The present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the relevant disclosure, rather than to limit the disclosure. It is also necessary to explain that, for ease of description, only the parts related to the relevant disclosure are shown in the accompanying drawings.

[0043] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present disclosure may be combined with each other. The present disclosure will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0044] Figure 1 An exemplary system architecture 100 is shown to which the bill generation method and apparatus according to the embodiments of the present disclosure can be applied.

[0045] like Figure 1 As shown, the system architecture 100 may include terminal devices 101, 102, a network 103, and servers 104, 105. The network 103 is used to provide a medium for communication links between the terminal devices 101, 102 and the servers 104, 105. The network 103 may include various connection types, such as wired, wireless communication links or optical fiber cables, etc.

[0046] Terminal devices 101 and 102 can be terminal devices used by price personnel, accounting personnel, and settlement personnel. In this case, the terminal devices can be hardware or software. When the terminal device is hardware, it can be various electronic devices with a display screen and supporting communication with a server, including but not limited to smart phones, tablet computers, laptop computers, and desktop computers. When the terminal device is software, it can be installed in the electronic devices listed above. It can be implemented as multiple software or software modules, or it can be implemented as a single software or software module. No specific limitation is made here.

[0047] The terminal devices 101 and 102 can receive input operations from price personnel, accounting personnel, and settlement personnel, and send instructions corresponding to the input operations to the servers 104 and 105.

[0048] Servers 104 and 105 may be servers that provide various services, such as a backend server that receives a request sent by a terminal device that establishes a communication connection with the backend server. The backend server may receive and analyze the request sent by the terminal device and generate a processing result.

[0049] Servers 104 and 105 can receive multiple billing data sent by multiple billing systems, obtain multiple standard data corresponding to the multiple billing systems based on pre-configured data conversion standards, and then select the data to be settled corresponding to the summary instruction from the multiple standard data in response to receiving the summary instruction sent by the settlement system, and then generate a summary task corresponding to the data to be settled, and finally perform settlement summary processing on the data to be settled based on the summary task, and generate a summary bill corresponding to the data to be settled. Servers 104 and 105 can display the summary bill through terminal devices 101 and 102.

[0050] It should be noted that the server can be hardware or software. When the server is hardware, it can be various electronic devices that provide various services to the terminal device. When the server is software, it can be implemented as multiple software or software modules that provide various services to the terminal device, or it can be implemented as a single software or software module that provides various services to the terminal device. No specific limitation is made here.

[0051] It should be noted that the bill generation method provided in the embodiment of the present disclosure can be executed by the servers 104 and 105. Accordingly, the bill generation device is disposed in the servers 104 and 105.

[0052] It should be understood that Figure 1 The number of terminal devices, networks and servers in the embodiment is only for illustration. Any number of terminal devices, networks and servers may be provided according to implementation requirements.

[0053] refer to Figure 2 , shows a process 200 of an embodiment of a bill generation method according to the present disclosure. The bill generation method comprises the following steps:

[0054] Step 210: in response to receiving a plurality of billing data sent by a plurality of billing systems, based on a pre-configured data conversion standard, obtaining a plurality of standard data corresponding to the plurality of billing systems.

[0055] In this step, the execution entity on which the bill generation method runs (e.g. Figure 1 The servers 104 and 105 in the system have interfaces that can provide data standard services, and can receive multiple billing data, summary instructions of billing data, and cancellation summary instructions sent by multiple billing systems; they can also provide support for merchants to verify detailed data, support data repair and data recalculation of unsettled business data within the compliance scope, and support billing or other systems to perform business logic judgments (unsettled data can be used as a basis for claims and recalculation).

[0056] The above-mentioned execution subject can communicate with multiple billing systems, and can obtain the billing data generated in each billing system based on the communication connection. The billing data can be a plurality of billing information to be settled and summarized in each billing system. Since the billing mode in each billing system is different, the data format of the billing data in each billing system is also different. After receiving the billing data of multiple billing systems, the above-mentioned execution subject can use the pre-configured data conversion standard to judge the data format of the billing data sent by each billing system, and judge whether the data format of the billing data sent by each billing system meets the data conversion standard. If it is determined that the data format of the billing data meets the data conversion standard, the billing data is converted into a data format to obtain the standard data corresponding to the billing data; if it is determined that the data format of the billing data does not meet the data conversion standard, the billing data is determined as standard data. Thus, the above-mentioned execution subject judges and converts the data format of the billing data of each billing system through the pre-configured data conversion standard, and obtains multiple standard data corresponding to multiple billing systems.

[0057] Furthermore, after the above-mentioned execution subject obtains multiple standard data corresponding to multiple billing systems, the standard data of each billing system can be stored and hashed into 64 libraries and 1024 MYSQL tables. MYSQL is a relational database used to store data in the system.

[0058] As an optional implementation, the above step 210, in response to receiving multiple billing data sent by multiple billing systems, obtaining multiple standard data corresponding to the multiple billing systems based on a pre-configured data conversion standard, may include the following steps:

[0059] In response to receiving multiple billing data sent by multiple billing systems based on a standard interface, the multiple billing data are determined as multiple standard data corresponding to the multiple billing systems; or, in response to receiving multiple billing data sent by multiple billing systems based on a message queue, the multiple billing data are subjected to standard conversion based on a pre-configured data conversion standard to obtain multiple standard data corresponding to the multiple billing data.

[0060] Specifically, the above-mentioned execution entity can be set with different ways of receiving billing data, and can be set with a standard interface, and use the standard interface to receive the billing data of the billing system. The standard interface can be an RPG interface, etc. The standard interface only receives billing data in a standard data format, that is, billing data that does not meet the data conversion standards and does not require data format conversion; the billing data of the billing system can also be received through the data transmission method of the message queue.

[0061] The above-mentioned execution entity can receive multiple billing data sent by multiple billing systems through a standard interface. The standard interface only allows billing data in standard data format to pass through. If the data format of the billing data sent by the billing system does not meet the requirements of the standard interface, a prompt message will be sent to prompt the modification of the data format of the billing data. The above-mentioned execution entity can directly determine the billing data received using the standard interface as standard data, thereby obtaining multiple standard data corresponding to multiple billing systems.

[0062] Alternatively, the above-mentioned execution entity may receive the billing data sent by the billing system through a message queue. The billing data received in this manner is determined to be non-standard data. The billing data is first filtered and verified, and then the received billing data needs to be converted to a standard using a pre-configured data conversion standard to obtain standard data corresponding to the billing data. Thus, the above-mentioned execution entity can use the pre-configured data conversion standard to perform standard conversion on multiple billing data to obtain multiple standard data corresponding to the multiple billing data.

[0063] In this implementation, by setting different data receiving methods and setting standard interfaces and message queues, the billing system can select different methods to send billing data, thereby improving the flexibility of data transmission. The data format can be set for the standard interface, and only billing data in the standard format is allowed to pass through. The billing data in the message queue can be converted to a standard format, so that the billing data received by each billing system and various data transmission methods can be converted to a standard format to obtain standard data.

[0064] Step 220, in response to receiving the summary instruction sent by the settlement system, selecting the to-be-settled data corresponding to the summary instruction from a plurality of standard data.

[0065] In this step, after the execution subject obtains multiple standard data of multiple billing systems, the multiple standard data can be stored. Then the execution subject can receive a summary instruction sent by the settlement system, which can be an instruction issued for the standard data of a certain billing system. One summary instruction can correspond to all the standard data of a billing system, or can correspond to part of the standard data of a billing system.

[0066] The above-mentioned execution entity can parse the received summary instruction to determine the summary data information corresponding to the summary instruction. The summary data information can represent the standard information identifier corresponding to the summary instruction. Then the above-mentioned execution entity selects the standard data corresponding to the summary instruction from multiple standard data based on the summary data information, and determines the selected standard data as the data to be settled corresponding to the summary instruction.

[0067] Among them, each summary instruction will correspond to a set of data to be settled. When the above-mentioned execution entity receives multiple summary instructions, it is necessary to determine the data to be settled corresponding to each summary instruction respectively.

[0068] Step 230: Generate a summary task corresponding to the data to be settled.

[0069] In this step, after the execution subject determines the data to be settled corresponding to the summary instruction, it can determine the summary type corresponding to the data to be settled according to the billing system corresponding to the data to be settled. The summary type can be a variety of settlement requirements such as the settlement summary method and summary bill type corresponding to the billing data. Then, the execution subject can generate a summary task corresponding to the data to be settled according to the data to be settled and the summary type. The summary task can be a task to be executed for settling the data to be settled, and can include a settlement summary processing flow for the data to be settled. Different data to be settled can correspond to different summary tasks.

[0070] The execution subject may simultaneously receive multiple aggregation instructions, determine multiple data to be settled, and generate multiple aggregation tasks, and these aggregation tasks may be executed asynchronously.

[0071] Step 240: Based on the summary task, the data to be settled is processed for settlement summary, and a summary bill corresponding to the data to be settled is generated.

[0072] In this step, after the above-mentioned execution entity generates a summary task corresponding to the data to be settled, it can perform settlement summary processing on the data to be settled according to the summary task, that is, the summary task can include a settlement summary processing flow for the data to be settled, and settlement summary processing is performed on the data to be settled based on the settlement summary processing flow to generate a summary bill corresponding to the data to be settled.

[0073] Among them, after the above-mentioned execution entity generates multiple summary tasks at the same time, it uses an asynchronous processing flow to simultaneously execute the multiple summary tasks, respectively performs settlement summary processing on the multiple data to be settled, and generates multiple summary bills corresponding to the multiple data to be settled.

[0074] The bill generation method provided by the embodiment of the present disclosure, the above-mentioned execution subject first responds to receiving multiple billing data sent by multiple billing systems, obtains multiple standard data corresponding to the multiple billing systems based on a pre-configured data conversion standard, and then responds to receiving a summary instruction sent by the settlement system, selects the data to be settled corresponding to the summary instruction from the multiple standard data, and then generates a summary task corresponding to the data to be settled. Finally, based on the summary task, the data to be settled is settled and summarized, and a summary bill corresponding to the data to be settled is generated. The billing data scattered in various billing systems can be connected using a simple standard process, and the billing data can be converted into standard data using a pre-configured data conversion standard, so that massive billing data in different forms can be aggregated, and the settlement and aggregation of massive data can be completed without the support of ORACLE database. The storage cost and computing cost are controlled within a certain range, so that the settlement and aggregation for each billing system can be efficiently carried out in one system, thereby improving the efficiency and flexibility of bill generation.

[0075] See also Figure 3 , Figure 3 A flowchart 300 of an embodiment of performing settlement summary processing on the data to be settled is shown, that is, the above step 240, based on the summary task, performing settlement summary processing on the data to be settled, and generating a summary bill corresponding to the data to be settled, may include the following steps:

[0076] Step 310: Based on the summary task, the data to be settled is verified using the back-check task model.

[0077] In this step, the execution subject generates a summary task corresponding to the data to be settled according to the data to be settled and the summary type of the data to be settled, and the summary task includes the settlement summary processing flow of the data to be settled. The execution subject can process the data to be settled according to the settlement summary processing flow of the summary task, and first use the back-check task model to verify the data to be settled to determine whether the data to be settled is correct.

[0078] Step 320: In response to determining that the data to be settled passes the data verification, the special task model is used to perform speciality judgment on the data to be settled.

[0079] In this step, the execution subject determines that the data to be settled has passed the data verification, and uses the special task model to determine the special nature of the data to be settled. It can determine whether the data to be settled corresponds to a special task and is not a regular settlement summary task based on the billing system corresponding to the data to be settled and the settlement requirements of the data to be settled. If it is determined that the data to be settled corresponds to a special task, it is determined that the data to be settled is a special type of data; if it is determined that the data to be settled does not have a special task, it is determined that the data to be settled is not a special type of data.

[0080] If it is determined that the data to be settled is not special data, step 330 is executed. In response to determining that the data to be settled is not special data, settlement summary processing is performed on the data to be settled based on the bill summary model to generate a summary bill corresponding to the data to be settled.

[0081] In this step, if the execution entity determines that the data to be settled is not special data, it can use the bill summary model to perform settlement summary processing on the data to be settled, perform settlement calculations on the data to be settled, and generate a summary bill corresponding to the data to be settled.

[0082] Among them, different billing systems need to correspond to different bill types, so the above-mentioned execution entity can generate different types of summary bills for different billing systems.

[0083] In this implementation, through a series of standard asynchronous process processing, data review and bill aggregation, the data to be settled are processed and aggregated into different types of summary bills for different merchants. While realizing chain processing, it is also possible to first determine whether the data to be settled corresponds to a special task, thereby improving the pertinence and accuracy of bill summary generation.

[0084] Continue to refer Figure 3 , Figure 3 A flowchart 300 of an embodiment of performing settlement summary processing on the data to be settled is shown, that is, the above step 240, based on the summary task, performs settlement summary processing on the data to be settled, and generates a summary bill corresponding to the data to be settled, and may also include the following steps:

[0085] If it is determined that the data to be settled is special type data, step 340 is executed. In response to determining that the data to be settled is special type data, data processing is performed on the data to be settled based on the special task model.

[0086] In this step, the execution subject determines that the data to be settled is a special type of data, and first uses the special task model to process the data to be settled to obtain the data after special processing.

[0087] Step 350: Perform settlement summary processing on the processed data to be settled based on the bill summary model to generate a summary bill corresponding to the data to be settled.

[0088] In this step, after the above-mentioned execution entity uses the special task model to process the data to be settled, it can use the bill summary model to perform settlement summary processing on the processed data to be settled, perform settlement calculations on the processed data to be settled, and generate a summary bill corresponding to the data to be settled.

[0089] In this implementation, by processing special types of data to be settled and utilizing a series of standard asynchronous process processing, data review and bill aggregation are performed to aggregate the data to be settled into different types of aggregate bills for different merchants, thereby achieving chain processing and improving the pertinence and accuracy of bill aggregation generation.

[0090] refer to Figure 4 , Figure 4 A flowchart 400 is shown of another embodiment of a bill generation method, which may include the following steps:

[0091] The summary task includes multiple sub-summary tasks.

[0092] Step 410: In response to receiving a plurality of billing data sent by a plurality of billing systems, a plurality of standard data corresponding to the plurality of billing systems is acquired based on a pre-configured data conversion standard.

[0093] Step 410 of this embodiment can be performed according to Figure 2 Step 210 in the illustrated embodiment is performed in a similar manner and will not be described in detail here.

[0094] Step 420, in response to receiving the summary instruction sent by the settlement system, selecting the to-be-settled data corresponding to the summary instruction from a plurality of standard data.

[0095] Step 420 of this embodiment can be performed according to Figure 2 Step 220 in the illustrated embodiment is performed in a similar manner and will not be described in detail here.

[0096] Step 430, determining whether the data to be settled meets the task splitting conditions.

[0097] In this step, after the above-mentioned execution entity obtains the data to be settled corresponding to the summary instruction, it can judge the data to be settled to determine whether the data volume of the data to be settled exceeds the preset quantity, or calculate the data to be settled according to the big data scoring model to determine whether the data to be settled meets the task splitting condition. The task splitting condition can represent the condition that the current data volume of the data to be settled is too large and the data to be settled needs to be split and summarized, for example, the details of the data to be settled are in millions or tens of millions of data.

[0098] If it is determined that the data to be settled meets the task splitting condition, step 440 is executed. In response to determining that the data to be settled meets the task splitting condition, the data to be settled is split.

[0099] In this step, if the above-mentioned execution entity determines that the data to be settled meets the task splitting conditions, the data to be settled can be split and processed and classified into a preset number of data. The preset number can be the number set by the settlement personnel based on experience, and this application does not make any specific restrictions on this.

[0100] Step 450: Generate multiple sub-aggregation tasks based on multiple split data corresponding to the data to be settled.

[0101] In this step, the execution subject obtains multiple split data corresponding to the data to be settled through data splitting, and then generates a sub-aggregation task corresponding to each split data according to each split data and the aggregation type.

[0102] Alternatively, the above-mentioned execution entity obtains multiple split data corresponding to the data to be settled after data splitting, and then generates a preset number of sub-summary tasks according to each split data and the summary type. For example, 64 sub-summary tasks are generated for each split data, and the preset number of sub-summary tasks are used to process the corresponding split data and perform settlement summary processing on the split data.

[0103] Step 460, based on the multiple sub-aggregation tasks, respectively perform settlement aggregation processing on the multiple split data to generate multiple sub-bills for the multiple split data.

[0104] In this step, after the above-mentioned execution entity obtains multiple sub-aggregation tasks, it performs settlement aggregation processing on the split data corresponding to the sub-aggregation task according to each sub-aggregation task, that is, the sub-aggregation task may include a settlement aggregation processing flow for the split data corresponding to the sub-aggregation task, and performs settlement aggregation processing on the split data corresponding to the sub-aggregation task based on the settlement aggregation processing flow to generate a sub-bill corresponding to the split data corresponding to the sub-aggregation task.

[0105] The above-mentioned execution entity can perform settlement summary processing on the corresponding split data according to each sub-summary task, generate a sub-bill corresponding to each split data, and thus generate multiple sub-bills for multiple split data.

[0106] Step 470: Generate a summary bill corresponding to the data to be settled based on the multiple sub-bills.

[0107] In this step, after the execution subject generates multiple sub-bills for the split data, it generates a reverse call function, calls back each sub-bill, summarizes and merges each sub-bill, and generates a summary bill corresponding to the data to be settled.

[0108] If it is determined that the data to be settled does not meet the task splitting condition, step 480 is executed. In response to determining that the data to be settled does not meet the task splitting condition, a summary task corresponding to the data to be settled is generated.

[0109] In this step, the execution entity determines that the data to be settled does not meet the task splitting conditions, and then uses steps similar to step 230 to generate a summary task corresponding to the data to be settled.

[0110] Step 490: Based on the summary task, the data to be settled is processed for settlement summary, and a summary bill corresponding to the data to be settled is generated.

[0111] Step 490 of this embodiment can be performed in the same manner as Figure 2 Step 240 in the illustrated embodiment is performed in a similar manner and will not be described in detail here.

[0112] In this embodiment, the data to be settled that needs to be split into tasks is determined through the data to be settled, the data to be settled with a large amount of data is split, and the sub-aggregation tasks of the split data are used to perform settlement aggregation processing on each split data. After the task is split, the data range processed by the operator becomes smaller and the computing power is improved. For example, the computing power can become 64*N times, the overall capacity is improved, and the efficiency of bill aggregation is improved.

[0113] refer to Figure 5 , Figure 5 A flowchart 500 of an embodiment of sending a prompt message is shown. The bill generation method may further include the following steps:

[0114] Step 510: Call back the summary bill based on the callback task model to determine whether the summary bill is settled successfully.

[0115] In this step, the execution subject uses the callback task model to call back the summary bill, and can determine whether the summary bill is settled successfully by determining whether the summary bill is generated or whether the summary bill is correct.

[0116] If it is determined that the summary bill settlement is successful, step 520 is executed. In response to determining that the summary bill settlement is successful, a bill change task corresponding to the data to be settled is generated.

[0117] In this step, after determining that the summary bill settlement is successful, the execution subject may generate a bill change task corresponding to the data to be settled. The bill change task may be an asynchronous task for prompting the billing system that the settlement of the data to be settled is completed.

[0118] Step 530: Based on the bill change task, a prompt message indicating that the settlement of the data to be settled is completed is sent to the billing system corresponding to the data to be settled.

[0119] In this step, after the execution subject obtains the bill change task, it can determine the billing system corresponding to the data to be settled according to the bill change task, and send a prompt message indicating that the settlement of the data to be settled is completed to the billing system corresponding to the data to be settled.

[0120] The execution entity may also mark the pending settlement data as completed according to the prompt information.

[0121] In this implementation, by using the bill change task to process the data when the settlement is completed, the asynchronous task processing method can alleviate the processing pressure of the system without the need for real-time prompts.

[0122] Continue to refer Figure 5 The above bill generation method may further include the following steps:

[0123] If it is determined that the summary bill settlement fails, step 540 is executed. In response to determining that the summary bill settlement fails, a bill cancellation task corresponding to the to-be-settled data is generated.

[0124] In this step, after determining that the summary bill settlement has failed, the execution subject may generate a bill cancellation task corresponding to the pending settlement data. The bill cancellation task may be an asynchronous task for notifying the billing system that the pending settlement data has failed to settle.

[0125] Alternatively, the above-mentioned execution entity can receive a cancel summary instruction and generate a bill cancellation task corresponding to the pending settlement data according to the cancel summary instruction. The bill cancellation task can be an asynchronous task used to prompt the billing system that the settlement of the pending settlement data has failed and cancel the settlement summary.

[0126] Step 550: Based on the bill cancellation task, a prompt message indicating that the settlement of the data to be settled has failed is sent to the billing system corresponding to the data to be settled.

[0127] In this step, after the execution subject obtains the bill cancellation task, it can determine the billing system corresponding to the data to be settled according to the bill cancellation task, and send a prompt message indicating that the settlement of the data to be settled has failed to the billing system corresponding to the data to be settled.

[0128] The execution entity may also clear the pending settlement data according to the prompt information, so that the pending settlement data can be used for subsequent settlement summary processing.

[0129] In this implementation, by using the bill cancellation task to process the data when the settlement fails or the settlement is canceled, and using the asynchronous task processing method, the processing pressure of the system can be alleviated without the need for real-time prompts.

[0130] refer to Figure 6 , Figure 6 A flowchart 600 of an embodiment of sending an alarm message is shown. The bill generation method may include the following steps:

[0131] Step 610, in response to determining to perform settlement aggregation processing on the data to be settled, counting the number of failures of the aggregation task.

[0132] In this step, the execution subject performs a quantity statistics on each link in the chain processing and counts the number of failures of the summary task during the process of performing a settlement summary processing on the data to be settled based on the summary instruction and the summary task.

[0133] Step 620, determining whether the number of failures exceeds a preset threshold.

[0134] In this step, after the above-mentioned execution entity obtains the number of failures, it can compare the number of failures with the preset threshold to determine whether the number of failures exceeds the preset threshold. The preset threshold can be preset by the staff based on experience, for example 6 times, and this application does not make any specific limitations on this.

[0135] If the number of failures exceeds the preset threshold, step 630 is executed. In response to the number of failures exceeding the preset threshold, the aggregation task is terminated and an alarm message corresponding to the aggregation task is sent.

[0136] In this step, if the execution subject determines through comparison that the number of failures exceeds the preset threshold, the summary task can be terminated, and an alarm message corresponding to the summary task can be generated and sent to the staff.

[0137] And, if the number of failures does not exceed the preset threshold, step 640 is executed, and in response to the fact that the number of failures does not exceed the preset threshold, the summary task is continued to be executed.

[0138] In this step, the execution subject continues to execute the summary task after determining that the number of failures does not exceed the preset threshold.

[0139] In this embodiment, it is determined whether the number of failures in task execution reaches a preset threshold. If it reaches above the preset threshold, a fuse is blown, the summary task is terminated, and an alarm is notified to the R&D personnel for manual exception handling. If it does not reach the preset threshold, failures are accumulated and the next execution time is delayed, thereby ensuring that failures due to network jitter, interface instability, etc. during task execution are not summarized.

[0140] refer to Figure 7 , Figure 7 A flowchart 700 of an embodiment of hierarchical storage of multiple standard data is shown. The bill generation method may include the following steps:

[0141] Step 710 , in response to generating a summary bill corresponding to the data to be settled, obtaining access frequencies of a plurality of standard data.

[0142] In this step, after the execution entity generates the summary bill corresponding to the data to be settled, the data to be settled can be marked as settled, so that there will be standard data with settlement completion marks and unmarked standard data in the multiple standard data corresponding to the multiple billing systems. The execution entity can determine the access frequency of each standard data according to the mark of the standard data and the access call record of the standard data.

[0143] Among them, since the standard data with the settlement completion mark has completed the settlement aggregation and will not be accessed subsequently, the standard data with the settlement completion mark has a lower access frequency; since the unmarked standard data has not yet been settled and aggregated, it will be accessed subsequently, so the unmarked standard data has a higher access frequency.

[0144] Step 720 , determining data states of the plurality of standard data based on access frequencies of the plurality of standard data.

[0145] In this step, after the above-mentioned execution subject obtains the access frequency of multiple standard data, it can determine the data state of each standard data according to the access frequency of each standard data. The data state can correspond to the access frequency, and the data state is divided into three states: "hot", "warm" and "cold", so that the above-mentioned execution subject determines the data state of multiple standard data.

[0146] Step 730: hierarchically store the multiple standard data based on the data states of the multiple standard data.

[0147] In this step, after the above-mentioned execution entity determines the data status of multiple standard data, the standard data is stored in layers according to the data status of each standard data, and standard data with different data statuses are stored in different locations. For example, hot data uses MySQL as the storage engine; warm data is stored in TiDB; cold data is stored in object storage (OSS).

[0148] In this embodiment, by determining the data state of standard data and storing multiple standard data in layers, standard data with different data states can be stored in different locations. Hot data can be supported by MySQL for high-performance computing, warm data can be dynamically and infinitely expanded by TiDB, and cold data can be stored indefinitely using object storage at a basically constant cost.

[0149] As an optional implementation, the bill generation method may include the following steps: determining whether the current system information meets the expansion conditions; in response to the current system information meeting the expansion conditions, performing expansion processing on application containers corresponding to multiple standard data through an elastic platform.

[0150] Specifically, the above-mentioned execution subject can obtain the current system information, which may include current time information, current resource utilization and other information. Then the above-mentioned execution subject can judge the current system information obtained to determine whether the current system information meets the expansion condition. The expansion condition can represent the condition that the application container needs to be expanded and configured, and may include that the current time information is the preset time information, the current resource utilization is lower than the preset utilization, etc. Then the above-mentioned execution subject determines that the current system information meets the expansion condition through judgment, and expands the application containers corresponding to multiple standard data through the elastic platform. If it is determined that the current system information does not meet the expansion condition, the application container is not expanded, or the application containers corresponding to multiple standard data are reduced through the elastic platform.

[0151] As an example, when the current time information is the preset time information, the above-mentioned execution entity can expand the application containers corresponding to multiple standard data through the elastic platform. If the time exceeds the preset time, the application containers corresponding to multiple standard data need to be reduced through the elastic platform.

[0152] As an example, when the current resource utilization is lower than the preset utilization, the above-mentioned execution entity can expand the application containers corresponding to multiple standard data through the elastic platform. If the current resource utilization increases and exceeds the preset utilization, it is necessary to shrink the application containers corresponding to multiple standard data through the elastic platform.

[0153] In this implementation, the application container is expanded and reduced in capacity through expansion conditions, and the standard data is processed through elastically scalable server processing capabilities. When the data volume is large, the expansion process can support high-traffic business, ensuring resource-efficient and sustainable support system operation. When the data volume is low, the reduction process can save resources.

[0154] As an optional implementation, the above-mentioned bill generation method may include the following steps: in response to obtaining multiple summary bills corresponding to multiple billing data, performing wide table processing on the multiple billing data and the multiple summary bills respectively to generate multiple honeycomb processed wide tables.

[0155] Specifically, since the above-mentioned settlement summary processing only requires some fields in the billing data, the final summary bill also only includes some fields. Therefore, after the above-mentioned execution entity obtains multiple summary bills corresponding to multiple billing data, it can perform wide table processing on multiple billing data and multiple summary bills respectively, and process the billing data and the summary bills as a whole to generate a large wide table, and obtain the honeycomb processed wide table corresponding to each billing system. The honeycomb processed wide table can include all fields in the billing data, and the honeycomb processed wide table is stored in ElasticSearch for price personnel, accounting personnel, settlement personnel, etc. of each business system to jointly view the billing settlement data.

[0156] In this implementation, multiple billing data and multiple summary bills are processed into wide tables to generate multiple honeycomb processed wide tables, which can meet the different needs of different personnel for table information.

[0157] As an optional implementation, the above-mentioned bill generation method may include the following steps: in response to receiving a data processing operation from a user, determining target standard data corresponding to the data processing operation; based on the data processing operation, performing data processing on the target standard data to obtain new standard data.

[0158] Specifically, the execution subject has a standard interface service that can support merchants to check detailed data, support data repair of unsettled business data within the compliance scope, and support billing or other systems to make business logic judgments (unsettled data can be used for claims and recalculations). Thus, the execution subject can receive the user's data processing operation, determine the target standard data corresponding to the data processing operation from multiple standard data, and then the execution subject can perform data processing on the target standard data according to the data processing operation, such as performing data repair on the target standard, to obtain new standard data.

[0159] In this implementation, standard data can be processed through user-based data processing operations, providing an interface service for interaction with users and improving the flexibility of bill settlement.

[0160] Further references Figure 8 As an implementation of the methods shown in the above figures, the present disclosure provides an embodiment of a bill generation device. Figure 2 The method embodiments shown correspond.

[0161] like Figure 8 As shown, the bill generating device 800 of this embodiment may include: an acquisition module 810 , a selection module 820 and a generation module 830 .

[0162] The acquisition module 810 is configured to, in response to receiving multiple billing data sent by multiple billing systems, acquire multiple standard data corresponding to the multiple billing systems based on a pre-configured data conversion standard;

[0163] The selection module 820 is configured to select the to-be-settled data corresponding to the summary instruction from the plurality of standard data in response to receiving the summary instruction sent by the settlement system;

[0164] The generation module 830 is configured to generate a summary task corresponding to the data to be settled; based on the summary task, perform settlement summary processing on the data to be settled, and generate a summary bill corresponding to the data to be settled.

[0165] In some optional implementations of the present embodiment, the acquisition module 810 is further configured to: in response to receiving multiple billing data sent by multiple billing systems based on a standard interface, determine the multiple billing data as multiple standard data corresponding to the multiple billing systems; or, in response to receiving multiple billing data sent by multiple billing systems based on a message queue, perform standard conversion on the multiple billing data based on a pre-configured data conversion standard to obtain multiple standard data corresponding to the multiple billing data.

[0166] In some optional implementations of the present embodiment, the generation module 830 is further configured to: based on the summary task, use the review task model to perform data verification on the data to be settled; in response to determining that the data to be settled passes the data verification, use the special task model to perform special nature judgment on the data to be settled; in response to determining that the data to be settled is not special type data, perform settlement summary processing on the data to be settled based on the bill summary model, and generate a summary bill corresponding to the data to be settled.

[0167] In some optional implementations of the present embodiment, the generation module 830 is further configured to: in response to determining that the data to be settled is a special type of data, perform data processing on the data to be settled based on a special task model; perform settlement summary processing on the processed data to be settled based on a bill summary model, and generate a summary bill corresponding to the data to be settled.

[0168] In some optional implementations of the present embodiment, the summary task includes multiple sub-summary tasks; and the generation module 830 is further configured to: determine whether the data to be settled meets the task splitting conditions; in response to determining that the data to be settled meets the task splitting conditions, split the data to be settled; based on the multiple split data corresponding to the data to be settled, generate multiple sub-summary tasks; and, based on the multiple sub-summary tasks, respectively perform settlement summary processing on the multiple split data to generate multiple sub-bills for the multiple split data; based on the multiple sub-bills, generate a summary bill corresponding to the data to be settled.

[0169] In some optional implementations of the present embodiment, the device also includes: a judgment module, which is configured to call back the summary bill based on the callback task model to determine whether the summary bill is settled successfully; a generation module 830, which is further configured to generate a bill change task corresponding to the data to be settled in response to determining that the summary bill is settled successfully; a sending module, which is configured to send a prompt message indicating that the settlement of the data to be settled is completed to the billing system corresponding to the data to be settled based on the bill change task.

[0170] In some optional implementations of the present embodiment, the generation module 830 is further configured to generate a bill cancellation task corresponding to the data to be settled in response to determining that the summary bill settlement has failed; the sending module is further configured to send a prompt message indicating the failure of settlement of the data to be settled to the billing system corresponding to the data to be settled based on the bill cancellation task.

[0171] In some optional implementations of the present embodiment, the device also includes: a statistical module, configured to count the number of failures of the summary task in response to determining to perform settlement summary processing on the data to be settled; a judgment module, configured to judge whether the number of failures exceeds a preset threshold; a sending module, configured to terminate the summary task in response to the number of failures actually exceeding the preset threshold, and send an alarm message corresponding to the summary task.

[0172] In some optional implementations of the present embodiment, the device also includes: an acquisition module 810, configured to acquire access frequencies of multiple standard data in response to generating a summary bill corresponding to the data to be settled; a determination module, configured to determine data states of multiple standard data based on the access frequencies of multiple standard data; and a storage module, configured to perform hierarchical storage of multiple standard data based on the data states of multiple standard data.

[0173] In some optional implementations of the present embodiment, the device also includes: a judgment module, configured to judge whether the current system information meets the expansion conditions; an expansion module, configured to expand the application containers corresponding to multiple standard data through an elastic platform in response to the current system information indeed meeting the expansion conditions.

[0174] In some optional implementations of the present embodiment, the generation module 830 is further configured to: in response to obtaining multiple summary bills corresponding to multiple billing data, perform wide table processing on the multiple billing data and the multiple summary bills respectively to generate multiple honeycomb processed wide tables.

[0175] In some optional implementations of the present embodiment, the device also includes: a determination module, configured to determine the target standard data corresponding to the data processing operation in response to receiving the user's data processing operation; a processing module, configured to perform data processing on the target standard data based on the data processing operation to obtain new standard data.

[0176] The bill generation device provided by the above-mentioned embodiment of the present disclosure, the above-mentioned execution subject first responds to receiving multiple billing data sent by multiple billing systems, obtains multiple standard data corresponding to the multiple billing systems based on a pre-configured data conversion standard, and then responds to receiving a summary instruction sent by the settlement system, selects the data to be settled corresponding to the summary instruction from the multiple standard data, and then generates a summary task corresponding to the data to be settled. Finally, based on the summary task, the data to be settled is settled and summarized, and a summary bill corresponding to the data to be settled is generated. The billing data scattered in various billing systems can be connected using a simple standard process, and the billing data can be converted into standard data using a pre-configured data conversion standard, so as to realize the aggregation of massive billing data in different forms and complete the settlement and aggregation of massive data. There is no need to use an ORACLE database for support, and the storage cost and computing cost are controlled within a certain range, so that the settlement and aggregation for each billing system can be efficiently carried out in one system, thereby improving the efficiency and flexibility of bill generation.

[0177] Those skilled in the art will appreciate that the above device also includes some other well-known structures, such as a processor, a memory, etc. In order to unnecessarily obscure the embodiments of the present disclosure, these well-known structures are described in detail. Figure 8 Not shown in FIG.

[0178] Reference below Fig. 9 , which shows a schematic diagram of the structure of an electronic device 900 suitable for implementing the embodiments of the present disclosure. The terminal device in the embodiments of the present disclosure may include but is not limited to mobile terminals such as smart screens, notebook computers, PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig. 9 The terminal device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0179] like Fig. 9As shown, the electronic device 900 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 901, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 902 or a program loaded from a storage device 908 into a random access memory (RAM) 903. In the RAM 903, various programs and data required for the operation of the electronic device 900 are also stored. The processing device 901, the ROM 902, and the RAM 903 are connected to each other via a bus 904. An input / output (I / O) interface 905 is also connected to the bus 904.

[0180] Typically, the following devices may be connected to the I / O interface 905: an input device 906 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 907 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 908 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 909. The communication device 909 may allow the electronic device 900 to communicate with other devices wirelessly or by wire to exchange data. Although Fig. 9 The electronic device 900 is shown with various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead. Fig. 9 Each block shown in the figure may represent one device, or may represent multiple devices as required.

[0181] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through a communication device 909, or installed from a storage device 908, or installed from a ROM 902. When the computer program is executed by the processing device 901, the above functions defined in the method of the embodiment of the present disclosure are executed. It should be noted that the computer-readable medium of the embodiment of the present disclosure can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection with one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In an embodiment of the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, an apparatus, or a device. In an embodiment of the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which a computer-readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in combination with an instruction execution system, an apparatus, or a device. The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to: wire, optical cable, RF (radio frequency), etc., or any suitable combination of the foregoing.

[0182] Computer program code for performing the operations of the embodiments of the present disclosure may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" language or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., using an Internet service provider to connect via the Internet).

[0183] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0184] The units involved in the embodiments described in the present application may be implemented by software or hardware. The units described may also be set in a processor, for example, it may be described as: a processor includes an acquisition module, a selection module and a generation module, wherein the names of these modules do not constitute a limitation on the modules themselves in some cases.

[0185] As another aspect, the present application also provides a computer-readable medium, which may be included in the electronic device; or may exist independently without being assembled into the electronic device. The computer-readable medium carries one or more programs, and when the one or more programs are executed by the electronic device, the electronic device: in response to receiving multiple billing data sent by multiple billing systems, obtains multiple standard data corresponding to the multiple billing systems based on pre-configured data conversion standards; in response to receiving a summary instruction sent by a settlement system, selects the data to be settled corresponding to the summary instruction from the multiple standard data; generates a summary task corresponding to the data to be settled; based on the summary task, performs settlement summary processing on the data to be settled, and generates a summary bill corresponding to the data to be settled.

[0186] The above description is only a preferred embodiment of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above-mentioned technical features, but should also cover other technical solutions formed by any combination of the above-mentioned technical features or their equivalent features without departing from the above-mentioned inventive concept. For example, the above-mentioned features are replaced with the technical features with similar functions disclosed in the embodiments of the present disclosure (but not limited to) to form a technical solution.

Claims

1. A bill generation method, the method comprising: In response to receiving a plurality of billing data sent by a plurality of billing systems, acquiring a plurality of standard data corresponding to the plurality of billing systems based on a pre-configured data conversion standard; In response to receiving a summary instruction sent by a settlement system, selecting the to-be-settled data corresponding to the summary instruction from the plurality of standard data; Generate a summary task corresponding to the data to be settled; Based on the summary task, settlement summary processing is performed on the data to be settled to generate a summary bill corresponding to the data to be settled.

2. The method according to claim 1, wherein: The step of acquiring, in response to receiving a plurality of billing data sent by a plurality of billing systems, a plurality of standard data corresponding to the plurality of billing systems based on a pre-configured data conversion standard comprises: In response to receiving a plurality of billing data sent by a plurality of billing systems based on a standard interface, determining the plurality of billing data as a plurality of standard data corresponding to the plurality of billing systems; or, In response to receiving multiple billing data sent by multiple billing systems based on the message queue, the multiple billing data are subjected to standard conversion based on a pre-configured data conversion standard to obtain multiple standard data corresponding to the multiple billing data.

3. The method according to claim 1, wherein: The step of performing settlement summary processing on the data to be settled based on the summary task to generate a summary bill corresponding to the data to be settled includes: Based on the summary task, the data to be settled is verified by using the back-check task model; In response to determining that the data to be settled passes the data verification, using the special task model to perform a special determination on the data to be settled; In response to determining that the data to be settled is not special type data, settlement summary processing is performed on the data to be settled based on a bill summary model to generate a summary bill corresponding to the data to be settled.

4. The method according to claim 3, wherein: The step of performing settlement summary processing on the data to be settled based on the summary task to generate a summary bill corresponding to the data to be settled also includes: In response to determining that the data to be settled is special type data, performing data processing on the data to be settled based on the special task model; The processed data to be settled is subjected to settlement summary processing based on the bill summary model to generate a summary bill corresponding to the data to be settled.

5. The method according to claim 1, wherein: The summary task includes a plurality of sub-summary tasks; And, the generating of the summary task corresponding to the data to be settled includes: Determine whether the data to be settled meets the task splitting conditions; In response to determining that the data to be settled meets the task splitting condition, splitting the data to be settled; generating the plurality of sub-aggregation tasks based on the plurality of split data corresponding to the data to be settled; and The step of performing settlement summary processing on the data to be settled based on the summary task to generate a summary bill corresponding to the data to be settled includes: Based on the multiple sub-aggregation tasks, settlement aggregation processing is performed on the multiple split data respectively to generate multiple sub-bills for the multiple split data; Based on the multiple sub-bills, a summary bill corresponding to the data to be settled is generated.

6. The method according to any one of claims 1 to 5, further comprising: Calling back the summary bill based on the callback task model to determine whether the summary bill is settled successfully; In response to determining that the summary bill is settled successfully, generating a bill change task corresponding to the data to be settled; Based on the bill change task, a prompt message indicating that settlement of the data to be settled is completed is sent to a billing system corresponding to the data to be settled.

7. The method according to claim 6, further comprising: In response to determining that the summary bill settlement fails, generating a bill cancellation task corresponding to the to-be-settled data; Based on the bill cancellation task, a prompt message indicating that settlement of the data to be settled has failed is sent to a billing system corresponding to the data to be settled.

8. The method according to any one of claims 1 to 5, further comprising: In response to determining to perform settlement aggregation processing on the data to be settled, counting the number of failures of the aggregation task; Determining whether the number of failures exceeds a preset threshold; In response to the fact that the number of failures exceeds the preset threshold, the aggregation task is terminated, and an alarm message corresponding to the aggregation task is sent.

9. The method according to any one of claims 1 to 5, further comprising: In response to generating a summary bill corresponding to the data to be settled, obtaining access frequencies of the plurality of standard data; determining data states of the plurality of standard data based on access frequencies of the plurality of standard data; The plurality of standard data are stored in a hierarchical manner based on data states of the plurality of standard data.

10. The method according to any one of claims 1 to 5, further comprising: Determine whether the current system information meets the expansion conditions; In response to confirming that the current system information meets the expansion condition, expansion processing is performed on the application containers corresponding to the multiple standard data through the elastic platform.

11. The method according to any one of claims 1 to 5, further comprising: In response to obtaining a plurality of summary bills corresponding to the plurality of billing data, wide table processing is performed on the plurality of billing data and the plurality of summary bills respectively to generate a plurality of honeycomb processed wide tables.

12. The method according to any one of claims 1 to 5, further comprising: In response to receiving a data processing operation from a user, determining target standard data corresponding to the data processing operation; Based on the data processing operation, the target standard data is processed to obtain new standard data.

13. A bill generating device, comprising: an acquisition module, configured to, in response to receiving a plurality of billing data sent by a plurality of billing systems, acquire a plurality of standard data corresponding to the plurality of billing systems based on a pre-configured data conversion standard; A selection module, configured to select, in response to receiving a summary instruction sent by a settlement system, the to-be-settled data corresponding to the summary instruction from the plurality of standard data; A generating module, configured to generate a summary task corresponding to the data to be settled; Based on the summary task, settlement summary processing is performed on the data to be settled to generate a summary bill corresponding to the data to be settled.

14. An electronic device comprising: one or more processors; a storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors are enabled to implement the method according to any one of claims 1 to 12.

15. A computer readable medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 12 is implemented.

Images