A method and device for accelerating payment

Abstract

The present invention provides a method and device for accelerating billing, the method comprising: synchronizing billing information in a first database to a second database, the billing information comprising user information and order information; generating first billing data according to the billing information based on an online transaction processing (OLTP) algorithm in the second database, the first billing data comprising the expense information of each business in the order information corresponding to each user in the user information, the first billing data being used for reconciliation of each user; performing report processing on the first billing data based on an online analytical processing (OLAP) algorithm in the second database to generate second billing data, the second billing data being used for reconciliation of a service provider, the service provider providing each business in the order information; transmitting the second billing data to the first database. The advantages of high concurrency and high efficiency of memory computing in the second database are fully utilized to improve the billing speed of the CRM system.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular to a method and device for accelerating payment. Background Art

[0002] In the communications industry, a Customer Relationship Management (CRM) system is usually used to perform a series of operations such as fee calculation, order start and rent change, fee tracing query, and bill generation. Billing refers to the monthly user fee calculation, order start and rent change, fee tracing query, and bill generation.

[0003] However, during the peak period of billing, the billing business competes with other businesses for server resources, resulting in slower processing speed.

[0004] It can be seen that the existing CRM system has a slow billing speed. Summary of the invention

[0005] The embodiment of the present invention provides a method and device for accelerating payment, so as to solve the problem that the payment speed of the existing CRM system is slow.

[0006] In a first aspect, an embodiment of the present invention provides a method for accelerating payment, the method comprising:

[0007] Synchronize the billing information in the first database to the second database, the billing information including user information and order information;

[0008] generating first billing data according to the billing information in the second database based on an online transaction processing (OLTP) algorithm, wherein the first billing data includes fee information of each business in the order information corresponding to each user in the user information, and the first billing data is used for reconciliation of each user;

[0009] In the second database, based on the online analytical processing (OLAP) algorithm, the first billing data is processed as a report to generate second billing data, wherein the second billing data is used for reconciliation by the service provider, and the service provider provides each business in the order information;

[0010] The second billing data is transmitted to the first database.

[0011] Optionally, generating the first billing data according to the billing information based on an OLTP algorithm in the second database includes:

[0012] Based on the coroutine model of the OLTP algorithm, generating the monthly expense data of each business in the order information corresponding to each user in the user information according to the user information and the order information;

[0013] Based on the thread pool model of the OLTP algorithm, the change order information of each user is traced back, and the first bill data is generated according to the change order information and the cost data of the current month, wherein the change order information includes new cost information and / or reduced cost information not included in the order information.

[0014] Optionally, after generating the first billing data according to the billing information based on an OLTP algorithm in the second database, the method further includes:

[0015] Performing data format conversion on the first bill data to generate a first bill, wherein the format of the first bill data is a format readable by the second database, and the format of the first bill is a format readable by the first database;

[0016] The first bill is transmitted to the first database.

[0017] Optionally, the transmitting the second bill data to the first database includes:

[0018] Performing data format conversion on the second bill data to generate a second bill, wherein the format of the second bill data is a format readable by the second database, and the format of the second bill is a format readable by the first database;

[0019] transmitting the second bill to the first database;

[0020] After transmitting the second bill data to the first database, the method further includes:

[0021] A detailed bill file is generated in the first database according to the first bill and the second bill, and the detailed bill file is used for data archiving.

[0022] Optionally, the performing report processing on the first billing data based on an OLAP algorithm in the second database to generate second billing data includes:

[0023] Based on the column storage model of the OLAP algorithm, each user in the user information in the first bill data and each business in the order information are respectively stored as columns in the column storage model as basic logical storage units;

[0024] According to the column storage model, the data in the logical storage unit is compressed in an encoded manner to obtain the encoded data corresponding to each user and each service respectively, and the encoded data is aggregated to generate the second billing data.

[0025] In a second aspect, an embodiment of the present invention provides a payment acceleration device, including:

[0026] A synchronization module, used to synchronize the billing information in the first database to the second database, wherein the billing information includes user information and order information;

[0027] a first calculation module, configured to generate first billing data according to the billing information based on an online transaction processing (OLTP) algorithm in the second database, wherein the first billing data includes fee information of each business in the order information corresponding to each user in the user information, and the first billing data is used for reconciliation of each user;

[0028] A second computing module is used to perform report processing on the first billing data based on an online analytical processing (OLAP) algorithm in the second database to generate second billing data, wherein the second billing data is used for reconciliation by a service provider, and the service provider provides each business in the order information;

[0029] A first transmission module is used to transmit the second bill data to the first database.

[0030] Optionally, the first calculation module includes:

[0031] A first calculation submodule is used to generate monthly expense data of each business in the order information corresponding to each user in the user information based on the coroutine model of the OLTP algorithm and according to the user information and the order information;

[0032] The second computing submodule is used to trace the change order information of each user based on the thread pool model of the OLTP algorithm, and generate the first billing data according to the change order information and the cost data of the current month, wherein the change order information includes new cost information and / or reduced cost information not included in the order information.

[0033] Optionally, the device further comprises:

[0034] a conversion module, configured to convert the data format of the first bill data to generate a first bill, wherein the format of the first bill data is a format readable by the second database, and the format of the first bill is a format readable by the first database;

[0035] The second transmission module is used to transmit the first bill to the first database.

[0036] Optionally, the first transmission module includes:

[0037] a conversion submodule, configured to convert the data format of the second bill data to generate a second bill, wherein the format of the second bill data is a format readable by the second database, and the format of the second bill is a format readable by the first database;

[0038] A transmission submodule, used for transmitting the second bill to the first database;

[0039] The device further comprises:

[0040] A generation module is used to generate a detailed bill file in the first database according to the first bill and the second bill, and the detailed bill file is used for data archiving.

[0041] Optionally, the second calculation module includes:

[0042] A storage submodule, for storing data based on a column storage model of the OLAP algorithm, using each user in the user information in the first billing data and each business in the order information as columns in the column storage model as basic logical storage units;

[0043] The third computing submodule is used to compress the data in the logical storage unit in an encoded manner according to the column storage model, obtain the encoded data corresponding to each user and each service respectively, and perform aggregation operation on the encoded data to generate the second billing data.

[0044] In the embodiment of the present invention, the billing information in the first database can be synchronized to the second database without upgrading the CRM system software and the server, so that the main storage and calculation of the billing data processing are completed in the second database, and the advantages of high concurrency and high I / O efficiency of memory computing in the second database are fully utilized, the parallelism of the billing program is improved, and the load on the first database in the CRM system is reduced, thereby improving the billing speed of the CRM system. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0046] Figure 1 This is one of the flowcharts of the method for accelerating payment provided by an embodiment of the present invention;

[0047] Figure 2 This is the second flow chart of the method for accelerating payment provided by an embodiment of the present invention;

[0048] Figure 3 This is the third flow chart of the method for accelerating payment provided by an embodiment of the present invention;

[0049] Figure 4 It is a structural diagram of a thread pool / coroutine model provided by an embodiment of the present invention;

[0050] Figure 5 is a schematic diagram of the structure of a row storage model provided by an embodiment of the present invention;

[0051] Figure 6 is a structural diagram of a column storage model provided by an embodiment of the present invention;

[0052] Figure 7 is a flow chart of a compression algorithm provided by an embodiment of the present invention;

[0053] Figure 8 is a schematic diagram of a multi-core parallel processing process provided by an embodiment of the present invention;

[0054] Fig. 9 It is a schematic diagram of the structure of the payment acceleration device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0055] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0056] The terms "first", "second", etc. in the embodiments of the present invention are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products, or devices.

[0057] See also Figure 1 , Figure 1 : is a flow chart of the method for accelerating payment provided by an embodiment of the present invention, such as Figure 1 As shown, the method comprises the following steps:

[0058] Step 101: Synchronize the billing information in the first database to the second database, wherein the billing information includes user information and order information;

[0059] In this step, the first database can be an Oracle database in the Customer Relationship Management (CRM) system. All business operations and account history data in the CRM system can be stored in the ORACLE database, of which order data can reach 5.12 million, user data can reach 6.22 million, and the total data file storage volume exceeds 20TB. By synchronizing the billing information in the ORACLE database to the second database, the pressure in areas such as disk access, internal and external memory data transfer, and buffer management when running the automated billing program can be reduced. The second database can be an independent memory database, which can accelerate the billing of the billing information synchronized and transmitted from the ORACLE database, shortening the billing time of the CRM system.

[0060] The billing information in the first database can be synchronized to the second database through a data synchronization module.

[0061] Step 102: Generate first billing data according to the billing information in the second database based on an online transaction processing (OLTP) algorithm, wherein the first billing data includes the cost information of each business in the order information corresponding to each user in the user information, and the first billing data is used for reconciliation of each user;

[0062] In this step, the billing program calls the OLTP algorithm to calculate and process the cost information of each user and each business in the in-memory database. It can match the billing element data line by line according to the city, user, and order dimensions, and frequently accumulate the costs of each business to generate the first bill data, which is a typical OLTP scenario. Each user can grasp the details of each business cost of the order of the month based on the first bill data.

[0063] Step 103: Based on the OLAP algorithm, the first billing data is processed into a report in the second database to generate second billing data, wherein the second billing data is used for reconciliation by the service provider, and the service provider provides each business in the order information;

[0064] In this step, the billing program calls the OLAP algorithm to audit and verify the first bill data in the in-memory database, and then performs report processing on each expense item according to the user and order dimensions to generate the second bill data. The report processing algorithm may be required to classify and aggregate the statistical data of the expense item amounts each time the first bill data is polled, which is a typical OLAP scenario.

[0065] Step 104: Transmit the second bill data to the first database.

[0066] In this step, after all the billing data in the billing information in the current bill period are processed in the memory database through the OLTP algorithm and the OLAP algorithm, the completion status is returned to the billing program. The billing program determines that the calculation processing in the memory database has been completed based on the billing status, and then writes the second billing data in the memory database back to the ORACLE database by calling the data synchronization module.

[0067] In the embodiment of the present invention, the billing information in the first database can be synchronized to the second database without upgrading the CRM system software and the server, so that the main storage and calculation of the billing data processing are completed in the second database, and the advantages of high concurrency and high I / O efficiency of memory computing in the second database are fully utilized, the parallelism of the billing program is improved, and the load on the first database in the CRM system is reduced, thereby improving the billing speed of the CRM system.

[0068] Among them, in-memory computing technology can be combined with different data storage modes, and optimization solutions can be customized according to the characteristics of OLTP and OLAP scenarios. Existing technologies can be fully utilized to improve the timeliness and stability of bill processing without upgrading the CRM system software and servers. This can save more time and facilitate local employees to carry out bill auditing work.

[0069] Optionally, generating the first billing data according to the billing information based on an OLTP algorithm in the second database includes:

[0070] Based on the coroutine model of the OLTP algorithm, generating the monthly expense data of each business in the order information corresponding to each user in the user information according to the user information and the order information;

[0071] Based on the thread pool model of the OLTP algorithm, the change order information of each user is traced back, and the first bill data is generated according to the change order information and the cost data of the current month, wherein the change order information includes new cost information and / or reduced cost information not included in the order information.

[0072] In this embodiment, if Figures 1 to 5 As shown, when the CRM system starts renting, changes and / or terminates each user's business, it will write incremental log information to the incremental business log table in the ORACLE database to load data for user information and order information; then, by configuring the incremental data log daemon in the data synchronization module, the incremental business log table is scanned regularly, and the incremental data extraction process is called according to the incremental log information to retrieve the relevant user information and order information in the ORACLE database; the billing information is formatted for easy reading by the in-memory database, and is synchronously loaded into the in-memory database.

[0073] Among them, the data synchronization module improves the speed of heterogeneous data increment and full data synchronization between the ORACLE database and the in-memory database of the CRM system. It can achieve real-time synchronization through uninterrupted polling, and support flexible scheduling of microservice interfaces, thereby speeding up the billing speed of the CRM system.

[0074] Based on the coroutine model of the OLTP algorithm, the billing details can be processed, and the monthly expense data of each user can be generated according to the user information and order information. The monthly expense data may include the monthly expenses of each service ordered by the user in the order information; then, based on the thread pool model of the OLTP algorithm, the account consolidation processing is performed. The account consolidation processing process needs to trace the changed order information of each user. The changed order information includes the new expense information and / or reduced expense information not included in the order information, and the first billing data is generated according to the changed order information and the monthly expense data.

[0075] Among them, the calculation process of outgoing account details and combined account processing is optimized in a targeted manner, and user information and order information can also adopt a row storage model. The data structure in the row storage model can be organized in rows, and the data of the previous row is stored in a continuous space, which is suitable for transactional operations that require frequent insertion or update, so as to adapt to the CRM system to load and / or update user information and order information when starting, changing and / or terminating each user's business. At the same time, the writing of row storage is completed in one go, the writing consumes less time, and the integrity of the data can be guaranteed.

[0076] The link mode between the payment program and the memory database can adopt the thread pool mode. Compared with threads, coroutines do not require kernel participation when switching contexts, and the application layer code can control the timing of switching. Used in conjunction with the thread pool, it can further solve the problems of thread number jitter and deadlock caused by the thread pool mode. In addition, through high-concurrency interval indexing technology, the B-Link-tree algorithm is adopted, and read and write concurrency is used. When modifying the multi-way search tree B-tree, it is not necessary to lock the entire tree, and it is not necessary to lock the complete path from the root node to the leaf node. It greatly improves the concurrent performance of interval index access. At the same time, the node merging and recycling function can minimize the memory usage and speed up the payment of the CRM system.

[0077] Optionally, the performing report processing on the first billing data based on an OLAP algorithm in the second database to generate second billing data includes:

[0078] Based on the column storage model of the OLAP algorithm, each user in the user information in the first bill data and each business in the order information are respectively stored as columns in the column storage model as basic logical storage units;

[0079] According to the column storage model, the data in the logical storage unit is compressed in an encoded manner to obtain the encoded data corresponding to each user and each service respectively, and the encoded data is aggregated to generate the second billing data.

[0080] In this embodiment, if Figures 1 to 3 ,as well as Figures 6 to 8 As shown, after the billing program calls the OLAP algorithm to audit and verify the first bill data in the in-memory database, it performs report processing on each expense item according to the user and order dimensions to generate the second bill data. The report processing algorithm may be such that each time the first bill data is polled, it is necessary to classify and aggregate the statistical data of the expense item amounts.

[0081] Among them, the calculation process of report processing is optimized in a targeted manner, and user information and order information can also adopt a column storage model. The structure of data in the column storage model can be stored according to columns as the basic logical storage unit. For example, each user and each business in the first bill data is stored as the column-based logical storage unit in the column storage model, and the data in a column is stored in a continuous storage space. Column storage does not require indexing on the database table, which can remove a large amount of index space. When querying data records of a certain attribute, the column database only needs to return the value related to the column attribute. In large data volume query scenarios, column storage can efficiently assemble the values ​​of each column in memory, and finally form a relational record set, so it can significantly reduce IO consumption and reduce query response time.

[0082] Based on the column storage model, the data in the logical storage unit can be compressed in an encoded manner. After the data content is compressed twice, the actual storage and memory usage space will be greatly saved. After the data content is compressed for the first time through the data dictionary, the character strings corresponding to each user, each business and / or each city are converted into numbers for storage, so the purpose of space compression is achieved. The second run length compression is performed to replace the original records of repeated characters with frequency records, because each character string only appears once in the dictionary table, further eliminating redundant data space occupation.

[0083] The in-memory database can be based on a share-nothing architecture. On the basis of column storage optimization, it can further make full use of server multi-core and distributed cluster processing to improve the parallelism of OLAP processing scenarios. Each CPU thread is assigned to aggregate operations on an independent column of data to perform aggregation operations on encoded data, avoiding IO resource queue contention between threads, reducing the number of context switches, and reducing delays in processing large amounts of data.

[0084] Optionally, after generating the first billing data according to the billing information based on an OLTP algorithm in the second database, the method further includes:

[0085] Performing data format conversion on the first bill data to generate a first bill, wherein the format of the first bill data is a format readable by the second database, and the format of the first bill is a format readable by the first database;

[0086] The first bill is transmitted to the first database.

[0087] In this embodiment, the memory database generates the first bill data after processing the bill information for billing details and account consolidation. The first bill data can provide data support for each user to query the details of each business expense of the order of the current month. After the first bill data is generated, the completion status is returned to the billing program. The billing program determines that the account consolidation processing in the memory database has been completed based on the billing status, and then starts the full data synchronization job by calling the microservice call interface of the data synchronization module. After the first bill data in the memory database is converted into a data format, the first bill in the format readable by the ORACLE database is generated and written back to the ORACLE database, so that the CRM system can provide the first bill to the user for viewing.

[0088] Optionally, the transmitting the second bill data to the first database includes:

[0089] Performing data format conversion on the second bill data to generate a second bill, wherein the format of the second bill data is a format readable by the second database, and the format of the second bill is a format readable by the first database;

[0090] transmitting the second bill to the first database;

[0091] After transmitting the second bill data to the first database, the method further includes:

[0092] A detailed bill file is generated in the first database according to the first bill and the second bill, and the detailed bill file is used for data archiving.

[0093] In this embodiment, after the in-memory database processes the first bill data as a report, it generates the second bill data, which can provide data support for the service provider to verify the details of each business expense of the current month's income. After the second bill data is generated, the completion status is returned to the billing program. The billing program determines that the report processing in the in-memory database has been completed based on the billing status, and then starts the full data synchronization job by calling the microservice call interface of the data synchronization module. After the second bill data in the in-memory database is converted into a data format, a second bill in an ORACLE database readable format is generated and written back to the ORACLE database, so that the CRM system can provide the second bill to the service provider for viewing.

[0094] In the ORACLE database, a detailed bill file can be generated based on the first bill and the second bill. The detailed bill file can be used by the CRM system to archive the data of the first bill and the second bill to facilitate downloading and viewing of historical bill period data.

[0095] In the process of billing processing, memory computing technology is fully utilized through data synchronization. The main storage and calculation of billing data processing are completed in the memory database. At the same time, the most suitable data storage mode is adopted, row storage is used in OLTP scenarios, and column storage is used in OLAP scenarios. Compared with the CRM system database, it has significant performance advantages. By utilizing the high concurrency and high I / O efficiency of the memory database, the parallelism of the billing program is improved, thereby improving the processing speed and stability of the billing work, which can shorten the system billing time by more than half and reduce the database server operating load by more than 50%. It can save more time for local and municipal employees to carry out billing and billing auditing work without upgrading the CRM system software and server, and without affecting the closing time, laying a good foundation for improving the timeliness, accuracy and completeness of the company's centralized billing work.

[0096] See also Fig. 9 , Fig. 9 is a schematic diagram of the structure of the payment acceleration device provided by an embodiment of the present invention. Fig. 9 As shown, the payment acceleration device 900 includes:

[0097] Synchronization module 901, used to synchronize billing information in the first database to the second database, the billing information including user information and order information;

[0098] A first calculation module 902 is used to generate first billing data according to the billing information based on an online transaction processing (OLTP) algorithm in the second database, wherein the first billing data includes the cost information of each business in the order information corresponding to each user in the user information, and the first billing data is used for reconciliation of each user;

[0099] A second calculation module 903 is used to perform report processing on the first bill data based on an online analytical processing (OLAP) algorithm in the second database to generate second bill data, wherein the second bill data is used for reconciliation by the service provider, and the service provider provides each business in the order information;

[0100] The first transmission module 904 is configured to transmit the second bill data to the first database.

[0101] Optionally, the first calculation module 902 includes:

[0102] A first calculation submodule is used to generate monthly expense data of each business in the order information corresponding to each user in the user information based on the coroutine model of the OLTP algorithm and according to the user information and the order information;

[0103] The second computing submodule is used to trace the change order information of each user based on the thread pool model of the OLTP algorithm, and generate the first billing data according to the change order information and the cost data of the current month, wherein the change order information includes new cost information and / or reduced cost information not included in the order information.

[0104] Optionally, the device further comprises:

[0105] a conversion module, configured to convert the data format of the first bill data to generate a first bill, wherein the format of the first bill data is a format readable by the second database, and the format of the first bill is a format readable by the first database;

[0106] The second transmission module is used to transmit the first bill to the first database.

[0107] Optionally, the first transmission module 904 includes:

[0108] a conversion submodule, configured to convert the data format of the second bill data to generate a second bill, wherein the format of the second bill data is a format readable by the second database, and the format of the second bill is a format readable by the first database;

[0109] A transmission submodule, used for transmitting the second bill to the first database;

[0110] The device further comprises:

[0111] A generation module is used to generate a detailed bill file in the first database according to the first bill and the second bill, and the detailed bill file is used for data archiving.

[0112] Optionally, the second calculation module 903 includes:

[0113] A storage submodule, for storing data based on a column storage model of the OLAP algorithm, using each user in the user information in the first billing data and each business in the order information as columns in the column storage model as basic logical storage units;

[0114] The third computing submodule is used to compress the data in the logical storage unit in an encoded manner according to the column storage model, obtain the encoded data corresponding to each user and each service respectively, and perform aggregation operation on the encoded data to generate the second billing data.

[0115] The payment acceleration device provided by the embodiment of the present invention can achieve Figure 1 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again to avoid repetition.

[0116] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present invention is not limited to performing functions in the order discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0117] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0118] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

Claims

1. A method for accelerating payment, characterized in that: The method comprises: Synchronize the billing information in the first database to the second database, the billing information including user information and order information; generating first billing data according to the billing information in the second database based on an online transaction processing (OLTP) algorithm, wherein the first billing data includes fee information of each business in the order information corresponding to each user in the user information, and the first billing data is used for reconciliation of each user; In the second database, based on the online analytical processing (OLAP) algorithm, the first billing data is processed as a report to generate second billing data, wherein the second billing data is used for reconciliation by the service provider, and the service provider provides each business in the order information; transmitting the second billing data to the first database; The step of performing report processing on the first billing data based on the OLAP algorithm in the second database to generate second billing data includes: Based on the column storage model of the OLAP algorithm, each user in the user information in the first bill data and each business in the order information are respectively stored as columns in the column storage model as basic logical storage units, and the second database adopts a shared-nothing architecture; According to the column storage model, the data in the logical storage unit is compressed in an encoded manner, wherein the content of the data undergoes two compression processes, namely, data dictionary compression and length compression, to obtain the encoded data corresponding to each user and each service respectively, and the encoded data is aggregated to generate the second billing data.

2. The method according to claim 1, characterized in that: The generating the first billing data according to the billing information based on the OLTP algorithm in the second database includes: Based on the coroutine model of the OLTP algorithm, generating the monthly expense data of each business in the order information corresponding to each user in the user information according to the user information and the order information; Based on the thread pool model of the OLTP algorithm, the change order information of each user is traced back, and the first bill data is generated according to the change order information and the cost data of the current month, wherein the change order information includes new cost information and / or reduced cost information not included in the order information.

3. The method according to claim 1, characterized in that After generating the first billing data according to the billing information in the second database based on the OLTP algorithm, the method further includes: Performing data format conversion on the first bill data to generate a first bill, wherein the format of the first bill data is a format readable by the second database, and the format of the first bill is a format readable by the first database; The first bill is transmitted to the first database.

4. The method according to claim 3, characterized in that The transmitting the second bill data to the first database comprises: Performing data format conversion on the second bill data to generate a second bill, wherein the format of the second bill data is a format readable by the second database, and the format of the second bill is a format readable by the first database; transmitting the second bill to the first database; After transmitting the second bill data to the first database, the method further includes: A detailed bill file is generated in the first database according to the first bill and the second bill, and the detailed bill file is used for data archiving.

5. A payment acceleration device, characterized in that: include: A synchronization module, used to synchronize the billing information in the first database to the second database, wherein the billing information includes user information and order information; a first calculation module, configured to generate first billing data according to the billing information based on an online transaction processing (OLTP) algorithm in the second database, wherein the first billing data includes fee information of each business in the order information corresponding to each user in the user information, and the first billing data is used for reconciliation of each user; A second computing module is used to perform report processing on the first billing data based on an online analytical processing (OLAP) algorithm in the second database to generate second billing data, wherein the second billing data is used for reconciliation by a service provider, and the service provider provides each business in the order information; A first transmission module, configured to transmit the second bill data to the first database; The second calculation module includes: A storage submodule, which is used for storing in a column storage model based on the OLAP algorithm, taking each user in the user information in the first billing data and each business in the order information as a column in the column storage model as a basic logical storage unit, and the second database adopts a shared-nothing architecture; The third computing submodule is used to compress the data in the logical storage unit in an encoded manner according to the column storage model, wherein the content of the data undergoes two compression processes of data dictionary compression and length compression to obtain the encoded data corresponding to each user and each service respectively, and perform aggregation operation on the encoded data to generate the second billing data.

6. The device according to claim 5, characterized in that The first calculation module includes: A first calculation submodule is used to generate monthly expense data of each business in the order information corresponding to each user in the user information based on the coroutine model of the OLTP algorithm and according to the user information and the order information; The second computing submodule is used to trace the change order information of each user based on the thread pool model of the OLTP algorithm, and generate the first billing data according to the change order information and the cost data of the current month, wherein the change order information includes new cost information and / or reduced cost information not included in the order information.

7. The device according to claim 5, characterized in that Also includes: a conversion module, configured to convert the data format of the first bill data to generate a first bill, wherein the format of the first bill data is a format readable by the second database, and the format of the first bill is a format readable by the first database; The second transmission module is used to transmit the first bill to the first database.

8. The device according to claim 7, characterized in that The first transmission module includes: a conversion submodule, configured to convert the data format of the second bill data to generate a second bill, wherein the format of the second bill data is a format readable by the second database, and the format of the second bill is a format readable by the first database; A transmission submodule, used for transmitting the second bill to the first database; The device further comprises: A generation module is used to generate a detailed bill file in the first database according to the first bill and the second bill, and the detailed bill file is used for data archiving.

Images