Triggered charging method and system based on message queue and storage medium

Abstract

The invention discloses a triggering type charging method and system based on a message queue and a storage medium, a collector collects information of a triggering charging event from a collection object, and when the collection object triggers the charging event, the charging information is recorded and written into a collection file; and periodically sending the content of the collected file to a charging center through a message queue. According to the charging information received from the message queue in sequence, the charging center matches charging rules in sequence; after each piece of charging information is calculated by a charging rule, a calculation result is obtained; and after all the charging information is calculated, sending all charging results to the bookkeeping server through the message queue. And according to the charging result received from the message queue, the bookkeeping server performs bookkeeping operation. According to the invention, an information interaction hub taking the message queue as a core is established, the problems of high time delay and error proneness possibly occurring during high-concurrency charging are solved, a complete high-availability solution is finally formed, and the method has good practicability.

Description

Technical Field

[0001] The present invention belongs to the technical field of cloud computing, and in particular relates to a message queue-based triggered billing method, system and storage medium. Background Art

[0002] In the digital age, messaging has become an important tool for daily communication between enterprises and individuals. When the base station receives a request from the terminal, it will trigger the billing operation of the local computer room. Due to the large amount of data from terminal users, there are high requirements for timeliness and sequence, which reflects the higher requirements for the performance and availability of the billing system. However, in the traditional way, the client's request must wait for the business processing to be completed before the result is returned. Although this method ensures real-time performance, it will cause slow service or even downtime in high concurrency situations, resulting in unstable and low service availability.

[0003] AMQP, or Advanced Message Queuing Protocol, is a network protocol and an open standard for application layer protocols, designed for message-oriented middleware. Clients and message middleware based on this protocol can transmit messages without being restricted by different client / middleware products, different development languages, and other conditions. Message queue middleware includes Rabbitmq, Rocketmq, Kafka, etc., which are used to store and forward messages in distributed systems. Its core function is to decouple business processing. Figure 1 As shown in the figure, if the message queue is introduced, the call will first enter the message queue to queue, without waiting for the end of the business. The message queue middleware will automatically distribute the messages to the nodes with low pressure in order for business processing. This makes it almost real-time when the business volume is small, and slightly delayed when the business volume is large. This ensures the overall stability and high availability of the service. Summary of the invention

[0004] The object of the present invention is to provide a message queue-based triggered billing method, system and storage medium, aiming to solve the above-mentioned problems.

[0005] The present invention is mainly achieved through the following technical solutions: A trigger-type billing method based on a message queue comprises the following steps: Step S1: The collector collects information that triggers billing events from the collection object. Whenever the collection object triggers a billing event, the collector records the billing information and writes it into the collection file. The contents of the collection file are periodically sent to the billing center through the message queue. Step S2: According to the billing information received from the message queue, the billing center matches the billing rules in sequence; each billing information is calculated according to the billing rules to obtain the calculation result; when all the billing information is calculated, all the billing results are sent to the accounting service end through the message queue; Step S3: According to the billing result received from the message queue, the accounting service performs accounting operations, which include deducting an amount from the user's balance, accumulating the user's current bill amount, and recording the user's bill details; if the accounting operation triggers the user's balance alarm or the user's shutdown rule, the accounting service notifies the device management end to notify or disable the user's relevant permissions.

[0006] In order to better implement the present invention, further, step S1 includes the following steps: Step S11: When the collector is started, first check whether there is a collection file that has not been sent. If so, send the content of the collection file to the message queue; Step S12: After the collector is started, the collector monitors the collection object through the listener. When the billing content is listened, a billing information with a unique identifier is generated and the billing information is written into the collection file; Step S13: Scheduled sending task: first point the file to be monitored for writing to the new acquisition file, send the content of the old acquisition file to the message queue, and then delete the old acquisition file; Step S14: Continuously monitor the size of the file content in the message queue through capacity monitoring. If the size reaches a set threshold, a scheduled sending task is triggered and the time of the sending task is reset.

[0007] In order to better implement the present invention, further, step S2 includes the following steps: Step S21: deduplication and batch processing: deduplication is performed on the received billing information to ensure the global uniqueness of each piece of data; the billing information is then grouped, each group has similar matching rules, and each group uses a separate thread; Step S22: Billing: The billing information of the current group is matched with the billing rules; each billing information of the current group is calculated according to the matched billing rules to obtain a calculation result; when the data of all groups are calculated, all calculation results are summarized and sent to the message queue.

[0008] In order to better implement the present invention, further, in the step S21, when deduplicating the billing information, first self-check and deduplication are performed, and then the messages are diverted according to the time when they are generated. For data generated within 1 minute, deduplication is performed in redis; for data that is more than 1 minute away from generation time, deduplication is performed in es; all non-duplicate billing information is written into the es deduplication database.

[0009] In order to better implement the present invention, further, in the step S22, the billing information of the current group is first matched for the first time: the corresponding rules are matched according to the collected billing information; then a second match is performed: based on the rules of the first match, calculation formulas of different priorities are matched according to the validity period and number of uses of the billing information; if the calculation formula is matched, the calculation is performed, otherwise the billing record is recorded in the exception record table; if multiple rules are matched for the first time, and multiple calculation formulas are matched for the second time, the final calculation result is the sum of the calculation results of multiple formulas.

[0010] In order to better implement the present invention, further, step S3 includes the following steps: Step S31: After receiving the message from the message queue, the batch of information is grouped according to the account, the deduction information of each account is counted, and a deduction operation is performed on each account; if the warning value of the account balance is triggered, the device management end performs the corresponding permission restriction operation; Step S32: Bill accumulation: further group the accounts in a single bill and find the bill that needs to be recorded for each consumption; Step S33: Detailed record: Supplement each consumption record with account information, bill information, and reconciliation information, and then enter it into the warehouse.

[0011] In order to better implement the present invention, further, the detailed record includes a main thread and a deletion thread operating in parallel: Main thread: Each batch of detail data is written into a detail file with a globally unique file name. The detail file path is written into a detail temporary table. When a detail temporary table is being written, the table-level lock is released and deletion and update cannot be performed. When the number of written tables reaches the threshold, the writing table will be switched to a table that the deletion thread is not reading. Deletion thread: Get the detail file by reading the detail temporary table, and then write the detail data in the detail file into the non-relational database line by line; when the data in a file is completely written, delete the temporary table data corresponding to the file and execute the commit.

[0012] The present invention is mainly achieved through the following technical solutions: A triggered billing system based on a message queue is based on the above-mentioned triggered billing method, and includes a collector, a billing center and a billing service end arranged in sequence from front to back, wherein the collector is used to collect information triggering billing events from the collection object, and periodically sends the collected information to the billing center through the message queue; The billing center is used to match the billing rules in sequence according to the information that needs to be billed sent by the message queue, and after the batch calculation is completed, the billing result of the batch is sent to the accounting service end through the message queue; The accounting service end is used to perform accounting operations according to the billing results sent from the message queue.

[0013] In order to better implement the present invention, it further includes a device management end, which is connected to the accounting service end and several collection objects respectively; the device management end is used to manipulate the services of the terminal device and disable or enable the specified terminal device or function based on the received request.

[0014] A computer-readable storage medium stores a computer program, which implements the above-mentioned trigger-type billing method when executed by a processor.

[0015] The beneficial effects of the present invention are as follows: (1) The present invention establishes an information exchange hub with a message queue as the core. Through the close cooperation of the collector, the billing center, and the accounting service, it solves the high latency and error-prone problems that may occur during high-concurrency billing, and finally forms a complete high-availability solution. The billing method of the present invention can be applied to all prepaid scenarios with clear trigger conditions, such as the usage fee for renting shared items, the usage fee for IoT products, etc.

[0016] (2) Reliability: In every link of the entire billing process, a multi-node approach can be used to ensure the stable operation of the entire system. Each link has its own exception handling method to ensure that each billing event can be executed to the final result.

[0017] (3) Stability: The entire system uses message queues for traffic diversion. When encountering high concurrency, messages will be temporarily stored in the message queue and queued for processing without causing server instability. The entire billing process uses a buffer-batch method for billing, rather than a single operation. The high-frequency billing of each device still has stable and good processing performance.

[0018] (4) Maintainability: Users can monitor the flow and progress of the entire billing process through the message queue console. Users can freely add formulas to adapt to the changing business.

[0019] (5) Scalability: The processing nodes in each link can be expanded horizontally, and the number of collection nodes, billing nodes, and accounting nodes can be flexibly adjusted as the business scale changes.

[0020] (6) High performance: Through intelligent batch processing and multi-threaded distribution, high performance of the entire processing process is guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 Schematic diagram of sending messages to a message queue; Figure 2 It is a structural diagram of a triggered billing system based on a message queue; Figure 3 This is a schematic diagram of the collector's working principle; Figure 4 This is a schematic diagram of the working principle of the billing center; Figure 5 Schematic diagram of deduplication processing for the billing center; Figure 6 Flowchart for calculating fees for the billing center; Figure 7 Schematic diagram for bookkeeping services; Figure 8 This is a schematic diagram of a batch of deductions; Fig. 9 A schematic diagram of the main thread and the deletion thread for detailed recording; Fig.10 This is a schematic diagram of the execution principle of deleting a thread; Fig.11 Schematic diagram of the principle of switching from writing a table to deleting a table that the thread is not reading. DETAILED DESCRIPTION

[0022] Embodiment 1: A trigger-type billing method based on a message queue comprises the following steps: Step S1: The collector collects information that triggers billing events from the collection object. Whenever the collection object triggers a billing event, the collector records the billing information and writes it into the collection file. The contents of the collection file are periodically sent to the billing center through the message queue. Step S2: According to the billing information received from the message queue, the billing center matches the billing rules in sequence; each billing information is calculated according to the billing rules to obtain the calculation result; when all the billing information of the batch is calculated, all the billing results of the batch are sent to the accounting service end through the message queue; Step S3: According to the billing result received from the message queue, the accounting service performs accounting operations, which include deducting an amount from the user's balance, accumulating the user's current bill amount, and recording the user's bill details; if the accounting operation triggers the user's balance alarm or the user's shutdown rule, the accounting service notifies the device management end to notify or disable the user's relevant permissions.

[0023] Preferably, if Figure 3 As shown, the specific implementation steps of step S1 are as follows: 1. When the collector is started, first check whether there are any collected files that have not been sent. If found, send the files to the message queue first.

[0024] 2. After the collector is started, the listener part monitors the collection object that needs to be monitored. The monitoring object can be another message queue, or a certain interface, a certain indicator, etc. When the content that needs to be billed is monitored, a billing information is generated, and this information must have a unique identifier. Then the generated billing information is written into the collection file.

[0025] 3. Scheduled sending tasks will be executed at a specified time (configurable). First, the file written by the monitored part will be pointed to the new file, and the old file will be sent to the message queue. After this operation, delete this file.

[0026] 4. Capacity monitoring will continuously monitor the size of the collected files. If a limit is reached (configurable), a scheduled sending task will be triggered immediately and the sending task time will be reset.

[0027] Further, precautions and exception handling: If you use the container method to start the collector, you need to pay attention to the mounting of the listening file directory, otherwise the files being written will be lost due to the restart of the container.

[0028] You can use multiple collectors, but multiple collectors should not directly collect the same collection object, otherwise it will cause duplicate billing. If you want to use multiple collectors, you can also use the message queue diversion method or the master-slave method to improve the reliability of the system.

[0029] When the collector is collecting data, please remember to save the current location. When the collector is restarted, it should continue from the last interruption point.

[0030] When the collector is restarted during file sending, the current file may be sent again at the next startup, so deduplication processing is required in the next step.

[0031] Preferably, if Figure 4 As shown, the specific implementation steps of step S2 are as follows: 1. Deduplication and batching: The incoming billing files need to be deduplicated to ensure that each piece of data is globally unique. Then the files are grouped. Each group should have similar matching rules so that they can be merged and processed later. Each group uses a separate thread for the next step of processing.

[0032] 2. In the billing process, the data in the current group needs to be matched with rules, and the matched rules need to be calculated with formulas to obtain results. When all calculations for a batch of data are completed, all results are summarized and sent to the message queue s.

[0033] Furthermore, if Figure 5 As shown, the steps for deduplication are as follows: 1. Perform self-check and deduplication on the incoming batch of data to remove the duplicate data in this batch of data.

[0034] 2. Divide the messages according to their generation time. For data generated within 1 minute, remove duplicates in redis. Non-duplicates are stored in the redis cache for 1 minute. 3. For data that is more than 1 minute old, deduplicate it in es.

[0035] 4. All non-duplicate data are written into the es deduplication database.

[0036] The reason for the separation by generation time is that ES is not suitable for deduplication and filtering of short-term data because the newly stored data is still in the indexing stage and cannot be queried immediately. Most of the data is generated in a short period of time, so using redis can reduce the excessive pressure on ES and improve the response speed.

[0037] Possible reasons for duplicate data: ① The data generated by the collection object itself may be repeated in some extreme or abnormal circumstances.

[0038] ② When multiple collectors collect the same object without coordination, duplication may occur.

[0039] ③ The collector itself has an abnormality, which may cause duplication.

[0040] ④ If the collector is restarted during the collection process, duplication may occur.

[0041] In short, the reason for duplication is usually due to some abnormal factors. In order to avoid the impact of abnormal factors on the entire system and enhance the stability of the entire system, it is necessary to add a deduplication link at the beginning of the entire process.

[0042] Furthermore, if Figure 6 As shown, the steps of the billing process are as follows: 1. The first match: used to match the collected billing information to the corresponding rule data. For example, if a billing message is received, the content is: device 123, performed operation A, then it is necessary to match the corresponding rule according to the device number and operation code.

[0043] 2. Second match: The first matched rule is used to determine whether its validity period and number of times of use meet the conditions. For example, in tiered billing, the first 3 times are free, 4-10 times are charged 0.1 yuan each time, and 10 times and above are charged 0.2 yuan each time. Then there are 3 different formulas. The formula needs to have a priority. The calculation starts according to the priority to determine the number of times this rule is used in the cycle. When the number of times exceeds the limit, the formula of the next priority is used.

[0044] 3. Multiple matching situations: For example, a taxi-hailing app will charge a time fee in addition to the mileage fee, and multiple rules will be matched. In this case, the result will be the sum of the calculation results of multiple formulas.

[0045] 4. If the calculation formula cannot be matched, it is considered a logical anomaly or an account anomaly. At this time, the billing record is recorded in the abnormal record table for manual analysis and processing later.

[0046] 5. Restoration of the formula's available times: When the formula's available times exceed the limit, it needs to be restored in the next cycle. Therefore, the formula needs to have a recovery time. If the formula is called again after the recovery time has passed, the available times need to be restored, and the recovery time will be pushed to the next cycle.

[0047] 6. Formula: You can use mathematical formulas, and you can use common mathematical formula plug-ins to calculate the results. For example, the starting price of a taxi is 11 yuan, 2.5 yuan per kilometer, and the time charge is 0.25 yuan per minute from 10 to 11 o'clock. Then formula 1 is: 11 + 2.5 * (kilometers - 3), and formula 2 is: 0.25 * minutes.

[0048] Preferably, if Figure 7 As shown, the specific implementation steps of step S3 are as follows: (1) After receiving the message from the message queue s, group the batch of information by account, count how much money needs to be deducted from each account, how much money is for each item, and make a total. Finally, after getting the result, deduct the amount from each account.

[0049] (2) If the account balance warning value is triggered, corresponding actions need to be performed, such as sending a text message to notify the user of insufficient balance, or suspending relevant permissions of the user account.

[0050] (3) Bill accumulation: further group the accounts within a single bill and find the bills that need to be recorded for each consumption, such as consumption bills, activity bills, etc.

[0051] (4) Detailed records: Supplement each consumption record with account information, bill information, reconciliation information, etc., and then enter it into the database.

[0052] (5) All the above operations must be performed within one transaction to ensure atomicity.

[0053] Furthermore, if Figure 8 As shown in the figure, in the deduction phase, a batch of billing results are grouped according to the account ID and bill to be deducted. For example, if 26.2 yuan is deducted from account A, 16.1 yuan will be added to the call bill of account A, and 10.1 yuan will be added to the SMS bill of account A. According to the grouping results, the account balance and bill total are updated in batches.

[0054] Furthermore, if Fig. 9 As shown, the detailed recording process includes the following steps: 1. Each batch of detailed data is written into a detailed file, and the file name is globally unique.

[0055] 2. The detailed file path is written into a temporary detailed table. At this time, the transaction with the previous deduction link is committed, the lock is released, and the continued execution of other threads is guaranteed.

[0056] 3. Since this operation is performed by multiple threads, each thread can occupy a queue, and each queue occupies multiple queue tables to reduce the occurrence of lock conflicts. Fig.10 As shown in the figure, when a detail temporary table is being written, the table-level lock is released and deletion and update cannot be performed. The deletion thread needs to read and delete data from other tables.

[0057] 4. If Fig.11 As shown, when the write table reaches a certain number (the number is a configuration value), the write table will switch to the table that the delete thread is not reading.

[0058] 5. The deletion thread obtains the detail file by reading the temporary table, and then writes the detail data in the detail file into the non-relational database line by line.

[0059] 6. When the data in a file is completely written, the temporary table data corresponding to the file is deleted and the commit is executed.

[0060] 7. The main thread and the deletion thread are parallel operations. The deletion thread is independent and is not affected by the main thread. Since the process of writing all details into a non-relational database is slower than operations such as account deductions, the number of tables can be adjusted according to the situation to avoid excessive pressure on the database due to too fast writing.

[0061] Embodiment 2: A triggered billing system based on message queue, such as Figure 2 As shown, it includes a collector, a billing center, an accounting server and a device management terminal.

[0062] Collector: Collect information that triggers billing events from the collection objects that need to trigger billing events. Whenever a billing event is triggered, the relevant information is recorded. The recording method can be a local file, database, etc. When the record volume reaches a certain size or reaches a certain time period, the collected file content is sent out through the message queue.

[0063] Billing center: When receiving billing information sent from the message queue, it matches the billing rules in sequence. After each billing information is calculated by the billing rules, the calculation result is obtained. When all the billing information of this batch is calculated, this batch of billing results is sent out again through the message queue.

[0064] Accounting service: When receiving the billing result sent from the message queue, the accounting service needs to perform accounting operations based on the result. Accounting operations include: deducting the amount from the user's balance, accumulating the user's current bill amount, and recording the user's bill details. If the user's balance alarm or the user's shutdown rule is triggered, the device management service needs to be notified to notify and disable the user's relevant permissions.

[0065] Device management terminal: a service used to manipulate terminal devices. Upon receiving a request, the specified terminal device is disabled or enabled, or certain functions are disabled or enabled. There is no restriction on the implementation method, and the terminal device can be notified directly, or only the status field can be recorded in the central database.

[0066] The above description is only a preferred embodiment of the present invention and does not limit the present invention in any form. Any simple modification or equivalent change made to the above embodiment based on the technical essence of the present invention shall fall within the protection scope of the present invention.

Claims

1. A triggered billing method based on a message queue, characterized in that: The following steps are involved: Step S1: The collector collects information that triggers billing events from the collection object. Whenever the collection object triggers a billing event, the collector records the billing information and writes it into the collection file. The contents of the collection file are periodically sent to the billing center through the message queue. Step S2: According to the billing information received from the message queue, the billing center matches the billing rules in sequence; each billing information is calculated according to the billing rules to obtain the calculation result; when all the billing information is calculated, all the billing results are sent to the accounting service end through the message queue; Step S3: According to the billing result received from the message queue, the accounting service performs accounting operations, which include deducting an amount from the user's balance, accumulating the user's current bill amount, and recording the user's bill details; if the accounting operation triggers the user's balance alarm or the user's shutdown rule, the accounting service notifies the device management end to notify or disable the user's relevant permissions.

2. A message queue-based trigger billing method according to claim 1, characterized in that: The step S1 comprises the following steps: Step S11: When the collector is started, first check whether there is a collection file that has not been sent. If so, send the content of the collection file to the message queue; Step S12: After the collector is started, the collector monitors the collection object through the listener. When the billing content is listened, a billing information with a unique identifier is generated and the billing information is written into the collection file; Step S13: Scheduled sending task: first point the file to be monitored for writing to the new acquisition file, send the content of the old acquisition file to the message queue, and then delete the old acquisition file; Step S14: Continuously monitor the size of the file content in the message queue through capacity monitoring. If the size reaches a set threshold, a scheduled sending task is triggered and the time of the sending task is reset.

3. A message queue-based trigger billing method according to claim 1, characterized in that: The step S2 comprises the following steps: Step S21: deduplication and batch processing: deduplication is performed on the received billing information to ensure the global uniqueness of each piece of data; the billing information is then grouped, each group has similar matching rules, and each group uses a separate thread; Step S22: Billing: The billing information of the current group is matched with the billing rules; each billing information of the current group is calculated according to the matched billing rules to obtain a calculation result; when the data of all groups are calculated, all calculation results are summarized and sent to the message queue.

4. A message queue-based trigger billing method according to claim 3, characterized in that: In step S21, when deduplicating the billing information, first self-check and deduplication are performed, and then the messages are diverted according to the time when they are generated. For data generated within 1 minute, deduplication is performed in redis; for data that is more than 1 minute away from generation, deduplication is performed in es; all non-duplicate billing information is written into the es deduplication database.

5. A message queue-based trigger billing method according to claim 3, characterized in that: In step S22, the billing information of the current group is first matched: the corresponding rules are matched according to the collected billing information; then the second match is performed: based on the rules of the first match, the calculation formulas of different priorities are matched according to the validity period and the number of times of use of the billing information; If the calculation formula is matched, the calculation is performed, otherwise the billing record is recorded in the exception record table; If multiple rules are matched in the first time, and multiple calculation formulas are matched in the second time, the final calculation result is the sum of the calculation results of the multiple formulas.

6. A message queue-based trigger billing method according to claim 1, characterized in that: The step S3 comprises the following steps: Step S31: After receiving the message from the message queue, the batch of information is grouped according to the account, the deduction information of each account is counted, and a deduction operation is performed on each account; if the warning value of the account balance is triggered, the device management end performs the corresponding permission restriction operation; Step S32: Bill accumulation: further group the accounts in a single bill and find the bill that needs to be recorded for each consumption; Step S33: Detailed record: Supplement each consumption record with account information, bill information, and reconciliation information, and then enter it into the warehouse.

7. A message queue-based trigger billing method according to claim 6, characterized in that: The detailed record includes the main thread and the deletion thread of the parallel operation: Main thread: Each batch of detailed data is written into a detailed file, and the file name is globally unique; The detailed file path is written into a detailed temporary table; When a detailed temporary table is being written, the table-level lock is released and deletion and update cannot be performed. When the number of written tables reaches the threshold, the writing table will be switched to a table that the deletion thread is not reading. Deletion thread: Get the detail file by reading the detail temporary table, and then write the detail data in the detail file into the non-relational database line by line; when the data in a file is completely written, delete the temporary table data corresponding to the file and execute the commit.

8. A triggered billing system based on a message queue, based on the triggered billing method according to any one of claims 1 to 7, characterized in that: It includes a collector, a billing center and an accounting server which are arranged in sequence from front to back, wherein the collector is used to collect information triggering billing events from the collection object, and periodically send the collected information to the billing center through a message queue; The billing center is used to match the billing rules in sequence according to the information that needs to be billed sent by the message queue, and after the batch calculation is completed, the billing result of the batch is sent to the accounting service end through the message queue; The accounting service end is used to perform accounting operations according to the billing results sent from the message queue.

9. A message queue-based trigger billing system according to claim 8, characterized in that: It also includes a device management end, which is connected to the accounting service end and several collection objects respectively; the device management end is used to manipulate the services of the terminal device and disable or enable the specified terminal device or function based on the received request.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the triggered billing method described in any one of claims 1 to 7 is implemented.

Images