User call billing method, device and medium, billing system, and accounting system

Abstract

The present application discloses a user call billing method, device and medium, billing system, and accounting system. The method includes: obtaining a call bill file from a billing system, the call bill file including a file header, billing rules, and an original call bill, the file header recording the storage location of the billing rules in the call bill file; obtaining the user's account data from a user profile database based on the user number in the original call bill; merging the account data and the call bill file to obtain a target call bill file, the file header in the target call bill file recording the storage location of the billing rules and the account data in the target call bill file; based on the storage location of the billing rules and the account data in the target call bill file, reading the user's account data, original call bill, and billing rules respectively to calculate the user's call bill charges. The system provided by the present application can solve the technical problem of excessive access pressure on operators' user profile databases in the prior art.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a user call billing method, equipment and medium, a billing system, and an accounting system. Background Art

[0002] With the rapid development of the national communications industry, the number of calls generated by mobile communications has increased rapidly.

[0003] In the existing technology, after the call bills are collected, they must go through the call bill sorting and call bill routing links and be distributed to various cities for processing. During the city processing process, they also need to go through call bill batch pricing, call bill consolidation, as well as signal control and reminder links. The entire call bill billing process is cumbersome and requires multiple accesses to the user information database, which brings great access pressure to the operator's database system. Summary of the Invention

[0004] The purpose of the embodiments of the present application is to provide a method, apparatus, device and storage medium that can at least solve the technical problem of excessive pressure on operator's user profile database access in the prior art.

[0005] The technical solution of this application is as follows:

[0006] In a first aspect, a user call billing method is provided, which is applied to an accounting system, and the method includes: obtaining a call bill file from a billing system, the call bill file including a file header, billing rules, and an original call bill, the file header recording the storage location of the billing rules in the call bill file; obtaining the user's account data in a user information database based on the user number in the original call bill; merging the account data and the call bill file to obtain a target call bill file, the file header in the target call bill file recording the storage location of the billing rules and the account data in the target call bill file; based on the storage location of the billing rules and the account data in the target call bill file, reading the user's account data, original call bill, and billing rules respectively to calculate the user's call bill charges.

[0007] In some embodiments, based on the billing rules and the storage location of the account data in the target bill file, the user's account data, the original bill, and the billing rules are read respectively to calculate the user's bill charges, including:

[0008] Based on the billing rules and the storage location of the account data in the target call record file, the user's account data, original call record and billing rules are read respectively, and the call record is batch-priced to obtain the batch-pricing result;

[0009] Based on the batch pricing results, the call bills are consolidated to determine the user's call bill charges.

[0010] In some embodiments, based on the billing rules and the storage location of the account data in the target call record file, the user's account data, the original call record, and the billing rules are read respectively, and the call record is batch-priced to obtain the batch-pricing result, including:

[0011] Based on the storage location of the accounting data in the target call record file, storing the accounting data into a first array of the local shared memory;

[0012] Based on the storage location of the billing rules in the target call record file, storing the billing rules in a second array of the local shared memory;

[0013] Based on the account data in the first array and the charging rules in the second array, the original call record is priced to obtain a pricing result.

[0014] In some embodiments, based on the batch pricing results, the billing process is performed to determine the user's bill charges, including:

[0015] Based on the batch pricing results of multiple target call record files, the cost of each billing item in the multiple billing items is calculated by a preset billing item calculation method, and the multiple target call record files are target call record files of the same user;

[0016] Based on the cost of each billing item in the multiple billing items, the cost of each account item in the multiple account items is calculated using a preset account item calculation method;

[0017] A bill charge for the user is determined based on the charge for each of the plurality of account items.

[0018] In some embodiments, after reading the user's account data, original call bill, and billing rules respectively based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill fee, the method further includes:

[0019] Based on the fees of each billing account in the multiple billing accounts, the balance of each billing account in the multiple billing accounts is calculated using a preset balance account calculation method;

[0020] Based on the balance of each billing item in multiple billing items, the user's credit control status is determined through preset credit control rules.

[0021] In some embodiments, after reading the user's account data, original call bill, and billing rules respectively based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill fee, the method further includes:

[0022] Based on multiple target call record files, the usage of each billing item in multiple billing items is calculated using a preset usage item calculation method;

[0023] Based on the usage of each billing item in the multiple billing items, the items to be reminded are determined in the multiple billing items by using a preset reminder item calculation method;

[0024] Determine the business to be reminded based on the subjects to be reminded and the preset business reminder rules.

[0025] In some embodiments, after reading the user's account data, original call bill, and billing rules respectively based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill fee, the method further includes:

[0026] The call bill charges are sent to the user information database so that the user information database updates the user's account data.

[0027] In a second aspect, a user call billing method is provided, which is applied to a billing system, and the method includes:

[0028] Obtain the original call records from the network element side;

[0029] Identify the original call record type;

[0030] Based on the call record type, determine the billing rule of the original call record from multiple billing rules;

[0031] Based on the billing rules and the original call record, a call record file is constructed. The file header of the call record file records the storage location of the billing rules in the call record file.

[0032] The call bill file is sent to the accounting system so that the accounting system executes any of the billing methods described in the first aspect to calculate the user's call bill charges.

[0033] In a third aspect, a billing system is provided, including:

[0034] A first acquisition module is used to obtain the original call record from the network element side;

[0035] A call record identification module is used to identify the call record type of the original call record;

[0036] A first information processing module, configured to determine a billing rule for an original call record from among multiple billing rules based on the call record type;

[0037] The second information processing module constructs a call record file based on the billing rules and the original call record, wherein the file header of the call record file records the storage location of the billing rules in the call record file;

[0038] The call bill sending module is used to send the call bill file to the accounting system so that the accounting system executes any billing method of claims 1-7 to calculate the user's call bill charges.

[0039] In a fourth aspect, an accounting system is provided, including:

[0040] The second acquisition module is used to obtain a call record file from the billing system. The call record file includes a file header, billing rules, and an original call record. The file header records the storage location of the billing rules in the call record file;

[0041] A third acquisition module is used to obtain the user's account data from the user information database based on the user number in the original call record;

[0042] The third information processing module is used to merge the accounting data and the call record file to obtain a target call record file, wherein the file header of the target call record file records the billing rules and the storage location of the accounting data in the target call record file;

[0043] The billing module is used to read the user's account data, original call bill and billing rules respectively based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill fee.

[0044] In the fifth aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or instruction stored on the memory and runnable on the processor. When the program or instruction is executed by the processor, the steps of the user call billing method described in the first aspect are implemented.

[0045] In a sixth aspect, an embodiment of the present application provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the user call billing method described in the first aspect are implemented.

[0046] The technical solutions provided by the embodiments of this application bring at least the following beneficial effects:

[0047] The user call billing method provided in the embodiment of the present application determines the first data node in the user profile database based on the user number in the original call bill, accesses the first data node in the user profile database, and obtains all the user's account data. Before processing the user's call bill charges, the entire call bill processing process only needs to read the user profile database once, which greatly reduces the pressure on the user profile database.

[0048] The accounting data and the call record file are merged to obtain the target call record file. The file header in the target call record file records the billing rules and the storage location of the accounting data in the target call record file. Based on the target call record file, the user's call record charges are calculated. Since the billing rules are stored in the target call record file, there is no need to rely on reading the billing rules in the shared memory of the local hardware device, which ensures the consistency of the upstream and downstream call record billing rules and improves the billing accuracy.

[0049] The user call billing method provided in the embodiment of the present application eliminates the concept of "city" in the downstream link of the original billing method. The downstream process is exactly the same. Even if the call bill volumes of various cities are inconsistent, there will be no "busy and idle" situation, and the system processing capacity is fully utilized.

[0050] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application, and do not constitute an improper limitation on the present application.

[0052] Figure 1 This is a flow chart of an existing user call billing method in an embodiment of the present application;

[0053] Figure 2 This is a flow chart of a user call billing method provided in an embodiment of the present application. Figure 1 ;

[0054] Figure 3 This is a flow chart of a method for performing user call billing based on a target call bill file provided in an embodiment of the present application;

[0055] Figure 4 This is a flow diagram of a user call billing method provided in an embodiment of the present application. Figure 2 ;

[0056] Figure 5 This is a schematic diagram of the structure of a billing system provided in an embodiment of the present application;

[0057] Figure 6 This is a schematic diagram of the structure of an accounting system provided in an embodiment of the present application;

[0058] Figure 7 This is a structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0059] In order to make those of ordinary skill in the art better understand the technical solutions of the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is merely to provide a better understanding of the present application by illustrating the examples of the present application.

[0060] It should be noted that the terms "first," "second," and the like in the specification and claims of this application and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments of the application described herein can be implemented in an order other than those illustrated or described herein. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples consistent with certain aspects of the present application as detailed in the appended claims.

[0061] Based on the background technology, it can be known that in the prior art, the user call billing process requires multiple accesses to the user profile database, which brings great access pressure to the operator's user profile database.

[0062] The following is a detailed description of the existing user call billing method with reference to the accompanying drawings.

[0063] Figure 1 A flow chart of an existing method for billing user calls is shown in FIG. Figure 1 As shown, the method may include call bill generation, call bill collection, call bill sorting, call bill routing, call bill batch pricing, call bill accounting, service reminders, call bill storage and other links. Each link is described in detail below.

[0064] Call record generation: The network element side records the user's mobile communication behavior and generates original call record files.

[0065] Call record collection: The original call record files generated by the network element side are collected and sent to the billing system through protocols such as FTP.

[0066] Call record sorting: The billing system reads the original call record file and splits the original call record file according to the identified call record type (GSM / GPRS / SMS / VPMN, etc.) (administrative city, business type, etc.).

[0067] Call bill routing: The accounting system reads the split call bill records, reads the user information for the first time based on the user number in the record, and determines which corresponding city directory the call bill record should be sent to for subsequent processing based on the user information.

[0068] Call bill batching: The corresponding process in the accounting system reads the call bill records sent by the upstream after routing judgment, reads the user information a second time, and fills in the user ID, account ID, account item code, subject code, and other information according to the rules in the local shared memory segment. Then, the corresponding information in the user information is updated for the first time.

[0069] Bill consolidation: The corresponding process in the accounting system reads the bill records after upstream pricing. It then reads the user profile a third time, combines account items, user accounts, and user usage information, and calculates user fees and usage based on the rules in the local shared memory segment. It also generates user credit control status and user reminder calculation events. Then, it updates the corresponding information in the user profile a second time.

[0070] The corresponding prefecture-level process calculates user balances and service reminders based on call records. The accounting system reads the user credit control status and reminder calculation events generated upstream, and then reads the user profile a fourth and fifth time. Based on the rules stored in the local shared memory segment, the credit control determination rules and reminder calculation rules are calculated. For users who meet the conditions, credit control shutdown and restart instructions and service reminder text messages are generated. Then, the corresponding information status and content in the user profile are updated a third and fourth time.

[0071] Call record storage: The call record that has completed all the above processes will be stored in the database for user query.

[0072] In combination with the above-mentioned prior art user call billing method, the applicant found that the above solution has the following specific problems:

[0073] 1) During the entire billing process, the database needs to be accessed nine times to perform operations on user information (including five read operations and four write operations). This not only increases the database access pressure but also reduces the efficiency of billing.

[0074] 2) The call bill sorting, batch pricing, account consolidation, signal control, and reminder stages all rely on reading rules from the local shared memory of the hardware devices. In the current cloud environment, there are often thousands of hardware devices, and these "rules" exist independently of each other, making it impossible to guarantee 100% consistency. This can easily lead to inconsistencies in upstream and downstream call billing rules, resulting in user billing errors.

[0075] 3) The downstream processes of various cities in the accounting system are independent of each other. When the call order volume of each city is inconsistent, there will be a "busy and idle" situation, and the system processing capacity cannot be fully utilized.

[0076] Based on the above findings, the embodiments of the present application provide a user call billing method, equipment and medium, billing system, and accounting system. The technical solution provided by the embodiments of the present application matches and splices the billing rules of the call bill in the "call bill sorting" stage. In the "call bill routing" stage, the user information required for billing is matched and spliced. The spliced ​​call bill files complete user billing, user reminders, and user credit control calculations in the "call bill batch pricing" and "call bill consolidation" stages respectively. The technical solution provided by the embodiments of the present application changes the reading and use methods of user account information, billing rules, and business reminder calculation rules. Through the "top-level reading, key information carrying" method, a balance is achieved among call bill billing efficiency, database load, credit control timeliness and accuracy, and reminder timeliness and accuracy.

[0077] The user call billing method provided in the embodiment of the present application is described in detail below with reference to the accompanying drawings.

[0078] Figure 2 The flowchart of a method for billing a user's call bill provided by an embodiment of the present application is shown. The method can be applied to an accounting system, such as Figure 2 As shown, the user call billing method 100 may include steps S110-S140.

[0079] Step S110: Acquire a call record file from the billing system. The call record file includes a file header, billing rules, and an original call record. The file header records the storage location of the billing rules in the call record file.

[0080] The billing system, as described in the previous article on the existing user call billing method, is used to collect original call bills and split the original call bill files according to the call bill type, which is the call bill collection and call bill sorting links mentioned above.

[0081] The bill file is the bill file generated by the billing system after it has been processed based on the original bill file. It should be noted that this bill file differs from the bill file processed by the billing system described above. This bill file contains the billing rules corresponding to the original bill file, and the file header records the storage location of these billing rules within the bill file.

[0082] The accounting system, as described in the previous article on the existing user call billing method, is used to calculate the cost of the original call bill according to the billing rules, namely the call bill routing, call bill batch pricing, call bill consolidation, call bill storage and other links mentioned in the previous article.

[0083] It's important to note that the accounting system structure here differs from the existing accounting system described above. The existing accounting system consists of a headquarters system + a prefecture-level city system. The headquarters system routes call bills to the corresponding prefecture-level city systems for processing. This accounting system is a single system, not divided into prefecture-level city systems.

[0084] The accounting system obtains the processed call record file from the billing system, then identifies the user number in the original call record file, and performs subsequent processing based on the user number.

[0085] Step S120: Based on the user number in the original call bill, the user's account data is obtained from the user information database.

[0086] User number, where the user number can be the user's phone number, or other identification code that can identify the user's identity information. Based on this identification code, the user's account data can be found in the user information database.

[0087] The user information database stores user information, including user account information, namely account data.

[0088] In an example, taking GSM voice call records as an example, specific account data may include the following: the existing voice billing items and current recorded values ​​under the user's name; the existing voice account items and current recorded values; the existing account balance items and current recorded values; the existing credit control status recorded values; the existing voice usage items and current recorded values; the existing voice reminder items and current recorded values; and the existing voice service reminder status recorded values.

[0089] The accounting system finds the data node where the user information is located in the user information database based on the routing rules and the user number in the original call record, accesses the data node, and reads all the accounting information of the user, that is, the accounting data.

[0090] Step S130: Merge the accounting data and the call record file to obtain a target call record file. The file header of the target call record file records the charging rules and the storage location of the accounting data in the target call record file.

[0091] The user's "account data" and "call bill file" are merged, and the storage location of the account data in the target call bill file is recorded in the file header to obtain the target call bill file, which is then transmitted to the downstream process.

[0092] Step S140 , based on the billing rules and the storage location of the account data in the target bill file, the user's account data, the original bill and the billing rules are read respectively to calculate the user's bill charges.

[0093] The accounting system can perform bill batch pricing and bill consolidation based on the user's account data, original call records, and billing rules. The calculation method is similar to the existing solution in the previous embodiment. The difference is that the target call record contains all the information required for the calculation process, so the calculation does not require re-accessing the user information database.

[0094] As an example, similar to the existing billing schemes described above, the user billing method provided in the embodiment of the present application can also access the user profile database again to update the user's account data after calculating the user's bill charges. Based on this, the user billing method 100 can also include step S150.

[0095] Step S150: Send the call bill charges to the user information database so that the user information database updates the user's account data.

[0096] After calculating the user's call charges, the accounting system accesses the user information database again to update the user's accounting data.

[0097] The user billing method provided in the embodiment of the present application determines the first data node in the user profile database based on the user number in the original bill, accesses the first data node in the user profile database, and obtains the user's entire account data. Before processing the user's bill charges, the entire bill processing process only requires reading the user profile database once, greatly reducing the pressure on the user profile database. After calculating the user's bill charges, only one write operation is required. Compared with the original scheme's nine accesses to the user profile database (including five read operations and four write operations), the entire process is reduced to a maximum of two accesses (including one read operation and one write operation). Through the "top-level read, key information carrying" method, only one user profile is read, and billing calculation rules are centrally controlled and issued on 10 devices. This not only reduces the database user profile access system overhead by 80% in the downstream link, but also ensures 100% consistency of the dependent rules in the subsequent billing process. More importantly, it eliminates the concept of "city" in the downstream billing link, fully utilizes the system processing capacity, and improves the overall billing efficiency.

[0098] The following specifically introduces the process of calculating the user's call bill charges in an embodiment of the present application, that is, the specific implementation process of step 140 in the above embodiment.

[0099] In some embodiments, step S140 may specifically include steps S141-S142.

[0100] Step S141 , based on the billing rules and the storage location of the account data in the target bill file, the user's account data, the original bill and the billing rules are read respectively, and the bill is batch-priced to obtain the batch-pricing result.

[0101] Here, the accounting system does not need to access the user information database again to read the user information. It can read the user's accounting data and billing rules from their corresponding storage locations according to the records in the file header, that is, the storage location of the billing rules and accounting data in the target call record file, and then read the original call record in the target call record file to perform call record batch pricing and obtain the batch pricing results.

[0102] As an example, the accounting system needs to cache the user's accounting data, original call bills, and charging rules after reading them separately, and then perform relevant processing. Based on this, step S141 can specifically include steps S1411-S1413.

[0103] Step S1411: based on the storage location of the account data in the target call record file, store the account data into a first array of the local shared memory.

[0104] Step S1412: based on the storage location of the charging rules in the target call record file, the charging rules are stored in the second array of the local shared memory.

[0105] Step S1413: Based on the account data in the first array and the charging rules in the second array, the original call record is priced to obtain a pricing result.

[0106] As an example, the call bill consolidation may include multiple processing procedures, that is, step S142 may specifically include steps S1421-S1423.

[0107] Step S1421, based on the batch pricing results of multiple target call bill files, the cost of each billing item in the multiple billing items is calculated by a preset billing item calculation method, and the multiple target call bill files are target call bill files of the same user.

[0108] Step S1422 : Based on the fee of each billing item in the multiple billing items, the fee of each account item in the multiple account items is calculated using a preset account item calculation method.

[0109] Step S1423: Determine the user's call bill charge based on the charge of each account item in the multiple account items.

[0110] For ease of understanding, the above steps S141-S142 are described in detail below using a specific example.

[0111] Figure 3 The process of user call billing based on the target call bill file is shown, including call bill batch pricing and call bill consolidation.

[0112] The bill batch pricing process reads the target bill file generated after upstream routing processing and operates according to the following detailed process:

[0113] 1) Start from the 33rd byte of the call record (C1, Cn, B1, Bn are all 8 bytes, occupying a total of 32 bytes), read Cn bytes continuously, store them in the local shared memory variable X1, and put the data parsed from X1 into the local shared memory array T1, corresponding to the attached Figure 3 Step 1, Step 2, Step 3 in the process;

[0114] 2) Continue to read Bn bytes and store them in the local shared memory variable X2. Put the data parsed from X2 into the local shared memory array T2. Figure 3 Steps 4, 5, and 6 in the process;

[0115] 3) Continue to read An bytes and store them in the local shared memory variable X3, corresponding to the attached Figure 3 Steps 7 and 8 in the process;

[0116] 4) Using array T1 as a sample, complete the matching in array T2 and update the value of the corresponding data in array T2. Read the usage information in variable X3, update the value of the corresponding data in array T2, and Figure 3 Step 9 in the process;

[0117] The call bill consolidation process directly reads the corresponding array T2 in the local shared memory, corresponding to the attached Figure 3 In the process, follow the steps 10, 11, and 12 in the following order:

[0118] 1) Read the billing account calculation formula, calculate according to the existing voice billing account code and the data corresponding to each account, and update the calculation result in array T2;

[0119] 2) Read the account item calculation formula, perform calculations based on the existing voice account item code and the data corresponding to each account item, and update the calculation results in array T2;

[0120] 3) Read the balance account calculation formula, perform calculations based on the existing account balance account code and the data corresponding to each account, and update the calculation results in array T2;

[0121] 4) Read the credit control calculation formula, complete the secondary calculation according to the account balance calculation result in the previous step, and update the existing credit control status record in array T2;

[0122] 5) Read the usage account calculation formula, perform calculations based on the existing voice usage account codes and the data corresponding to each account, and update the calculation results in array T2;

[0123] 6) Read the reminder subject calculation formula, calculate according to the existing voice reminder subject code and the data corresponding to each subject, and update the calculation result in array T2;

[0124] 7) Read the business reminder calculation formula, complete the secondary calculation according to the reminder subject calculation result in the previous step, and update the existing business reminder status record in array T2;

[0125] The user call billing method provided in the embodiment of the present application eliminates the concept of "city" in the downstream link of the original billing method. The downstream process is exactly the same. Even if the call bill volumes of various cities are inconsistent, there will be no "busy and idle" situation, and the system processing capacity is fully utilized.

[0126] In some embodiments, based on the billing rules and the storage location of the account data in the target call bill file, the user's account data, original call bill and billing rules are read respectively to calculate the user's call bill charges. The user call bill billing method 100 may also include steps S143-S144.

[0127] Step S143, based on the fees of each of the multiple billing items, calculate the balance of each of the multiple billing items using a preset balance item calculation method;

[0128] Step S144: Based on the balance of each billing item in the multiple billing items, the credit control status of the user is determined by using a preset credit control rule.

[0129] In some embodiments, based on the billing rules and the storage location of the account data in the target call bill file, the user's account data, original call bill and billing rules are read respectively to calculate the user's call bill charges. The user call bill billing method 100 may also include steps S145-S147.

[0130] Step S145, based on the multiple target call record files, calculate the usage of each of the multiple billing items using a preset usage item calculation method;

[0131] Step S146, based on the usage of each billing item in the multiple billing items, determine the items to be reminded in the multiple billing items using a preset reminder item calculation method;

[0132] Step S147: Determine the business to be reminded based on the subject to be reminded and the preset business reminder rule.

[0133] Please continue to refer to the attached Figure 3 , describe the above steps S143-S147 in detail.

[0134] How does the downstream process of the billing system perform user credit control and business reminder calculations? Figure 3 Step 13 and Step 14 in the process.

[0135] During the account consolidation process described above, the corresponding array T2 in the local shared memory is read, and the user credit control calculation and user service reminder calculation are completed at the same time.

[0136] 1) Read the credit control calculation formula, complete the secondary calculation according to the account balance calculation result in the previous step, and update the existing credit control status record in array T2;

[0137] 1) Read the business reminder calculation formula, complete the secondary calculation according to the reminder subject calculation result in the previous step, and update the existing business reminder status record in array T2;

[0138] As an example, the specific implementation process of step S150 in the above text can correspond to the following Figure 3 Step 15 and Step 16 in the process.

[0139] The bill consolidation process directly reads the corresponding array T2 from local shared memory, uses array T2 as a sample, matches it in array T1, and updates the corresponding data value in array T1. Finally, through a loop scan, it reads the data from array T1 row by row, concatenates SQL statements, and writes them to the database, completing the update of the user's account information.

[0140] The user call billing method provided in the embodiment of the present application generates a call bill file header after identifying the call bill type, and sequentially splices and integrates the matching billing calculation rules, user account side information and user original communication call bill to complete the carrying of billing information. In the batch pricing link, the billing rules and user information are spliced ​​to obtain the call bill file, complete the call bill billing, signal control calculation, and reminder calculation, thereby improving the access efficiency and utilization efficiency of the user information database.

[0141] Based on the same inventive concept, corresponding to the above embodiments, the embodiment of the present application also provides a user call billing method, which is applied to a billing system.

[0142] Figure 4 The flow chart of a method for billing a user call bill provided by an embodiment of the present application is shown. The method can be applied to a billing system, such as Figure 4 As shown, the user call billing method 200 may include steps S210-S250.

[0143] Step S210: Obtain the original call record from the network element side.

[0144] Original call record: The network element side records the user's mobile communication behavior and generates an original call record file.

[0145] The billing system collects the user original call bill files generated by the network element side to the billing system in a unified manner through protocols such as FTP, and identifies the call bill type of the original call bill.

[0146] In a specific example, the billing system can identify the call record type, generate a "record file header," and append it to the front of the user's call record file. During the billing sorting process, the user's call records in the original call record file must be read one by one and split based on the identified call record type (GSM / GPRS / SMS / VPMN, etc.).

[0147] Step S230: Determine the billing rule of the original bill from among multiple billing rules based on the bill type.

[0148] In one example, the billing system can match the corresponding downstream calculation rules based on the split call record type and generate the corresponding "calculation rule file header." The sorting process reads a communication record for the user from the original call record. The record size is (An-A1) bytes. For example, after identification, the communication record is a GSM voice call record. Based on the call record type, the calculation rule for call billing is found.

[0149] Step S240: construct a call record file based on the charging rules and the original call record. The file header of the call record file records the storage location of the charging rules in the call record file.

[0150] The billing system splices the billing rules between the "record file header" and the "user call record file", and then records the storage location of the billing rules in the call record file in the file header, which can be the number of bytes occupied by the billing rules.

[0151] Step S250: Send the call bill file to the accounting system so that the accounting system executes the billing method provided in any of the above embodiments to calculate the user's call bill charges.

[0152] The billing system sends the call bill file to the accounting system, and the accounting system can calculate the user's call bill fee by executing the user call bill billing method provided in any of the above embodiments.

[0153] It should be noted that the billing rules here can include the following:

[0154] Existing voice billing subject codes and the data storage locations corresponding to each subject; existing voice account item codes and the data storage locations corresponding to each account item; existing account balance subject codes and the data storage locations corresponding to each subject; existing signal control status records; existing voice usage subject codes and the data storage locations corresponding to each subject; existing voice reminder subject codes and the data storage locations corresponding to each subject; existing voice service reminder status records; voice usage data storage locations recorded in the current call log; billing subject-related calculation methods; account item-related calculation methods; balance subject-related calculation methods; usage subject-related calculation methods; signal control calculation methods; reminder subject-related calculation methods.

[0155] The user call billing method provided in the embodiment of the present application, by splicing the billing rules into the call bill file, makes it unnecessary to rely on reading the billing rules in the shared memory of the local hardware device during the subsequent call bill batch pricing process, thereby ensuring the consistency of the upstream and downstream call bill billing rules and thereby improving the billing accuracy.

[0156] Based on the same inventive concept, Figure 4 Corresponding to the embodiment of the user call billing method, the embodiment of the present application also provides a billing system.

[0157] Figure 5 A schematic diagram of the structure of a billing system provided in an embodiment of the present application is shown in FIG. Figure 5 As shown, the billing system 500 may include:

[0158] A first acquisition module 510 is configured to acquire an original call record from a network element side;

[0159] A call record identification module 520 is used to identify the call record type of the original call record;

[0160] A first information processing module 530 is configured to determine a billing rule for an original call record from among multiple billing rules based on the call record type;

[0161] The second information processing module 540 constructs a call record file based on the billing rules and the original call record. The file header of the call record file records the storage location of the billing rules in the call record file.

[0162] The call bill sending module 550 is used to send the call bill file to the accounting system so that the accounting system executes the user call bill billing method provided in any embodiment to calculate the user's call bill fee.

[0163] The billing system provided in the embodiment of the present application can be used to execute the steps performed by the billing system in the user call billing method provided in the above-mentioned method embodiments. Its implementation principles and technical effects are similar, and for the sake of simplicity, they will not be repeated here.

[0164] Based on the same inventive concept, an embodiment of the present application also provides an accounting system.

[0165] Figure 6 An accounting system provided by an embodiment of the present application is shown. Figure 6 As shown, the accounting system 600 may include:

[0166] The second acquisition module 610 can be used to obtain a call record file from the billing system. The call record file includes a file header, billing rules, and an original call record. The file header records the storage location of the billing rules in the call record file.

[0167] The third acquisition module 620 may be used to obtain the user's account data from the user profile database based on the user number in the original call record;

[0168] The third information processing module 630 can be used to merge the accounting data and the call record file to obtain a target call record file. The file header of the target call record file records the billing rules and the storage location of the accounting data in the target call record file;

[0169] The billing module 640 can be used to read the user's account data, original call bill and billing rules respectively based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill fee.

[0170] In some embodiments, the billing module 640 may specifically include a batch pricing unit and a combined accounting unit.

[0171] The pricing unit can be used to read the user's account data, original call record and billing rules respectively based on the billing rules and the storage location of the account data in the target call record file, perform call record pricing, and obtain the pricing result.

[0172] The bill consolidation unit can be used to consolidate call bills based on the batch pricing results and determine the user's call bill charges.

[0173] As an example, the pricing unit may specifically include a first information processing component, a second information processing component, and a pricing component.

[0174] The first information processing component can be used to store the accounting data into a first array of the local shared memory based on the storage location of the accounting data in the target call record file;

[0175] The second information processing component can be used to store the charging rules into a second array of the local shared memory based on the storage location of the charging rules in the target call record file;

[0176] The pricing component can be used to price the original call record based on the account data in the first array and the charging rules in the second array to obtain a pricing result.

[0177] As an example, the account combining unit may specifically include a first computing component, a first computing component, and an account combining component.

[0178] The first calculation component can be used to calculate the cost of each billing item in the multiple billing items based on the batch pricing results of the multiple target call record files by using a preset billing item calculation method, and the multiple target call record files are target call record files of the same user;

[0179] The second calculation component may be configured to calculate the cost of each of the plurality of billing items based on the cost of each of the plurality of billing items by using a preset account item calculation method;

[0180] The account consolidation component can be used to determine the user's call bill charges based on the charges of each account item in multiple account items.

[0181] In some embodiments, the accounting system 600 may further include a first calculation module and a signal control module.

[0182] The first calculation module can be used to read the user's account data, original call bill and billing rules respectively based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill charges. Then, based on the charges of each billing account in multiple billing accounts, the balance of each billing account in multiple billing accounts is calculated through a preset balance account calculation method.

[0183] The credit control module can be used to determine the user's credit control status based on the balance of each billing item in multiple billing items through preset credit control rules.

[0184] In some embodiments, the accounting system 600 may further include a second calculation module, a third calculation module, and a business reminder module.

[0185] The second calculation module can be used to read the user's account data, original call bill and billing rules respectively based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill charges. Then, based on multiple target call bill files, the usage of each billing account in multiple billing accounts is calculated through a preset usage account calculation method.

[0186] The third calculation module can be used to determine the subject to be reminded among the multiple billing subjects based on the usage of each billing subject among the multiple billing subjects through a preset reminder subject calculation method.

[0187] The business reminder module can be used to determine the business to be reminded based on the subjects to be reminded and the preset business reminder rules.

[0188] In some embodiments, the accounting system 600 may further include a database update module.

[0189] The database update module can be used to read the user's account data, original call bill and billing rules respectively based on the billing rules and the storage location of the account data in the target call bill file, calculate the user's call bill charges, and then send the call bill charges to the user information database so that the user information database can update the user's account data.

[0190] The accounting system provided in the embodiment of the present application can be used to execute the steps performed by the accounting system in the user call billing method provided in the above-mentioned method embodiments. Its implementation principles and technical effects are similar, and for the sake of simplicity, they will not be repeated here.

[0191] Based on the same inventive concept, an embodiment of the present application also provides an electronic device.

[0192] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 7 As shown, the electronic device may include a processor 701 and a memory 702 storing computer programs or instructions.

[0193] Specifically, the processor 701 may include a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0194] The memory 702 may include a large-capacity memory for data or instructions. By way of example and not limitation, the memory 702 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, the memory 502 may include a removable or non-removable (or fixed) medium. Where appropriate, the memory 502 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 702 is a non-volatile solid-state memory. In a specific embodiment, the memory 702 includes a read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or a flash memory, or a combination of two or more of these.

[0195] The processor 701 reads and executes the computer program instructions stored in the memory 702 to implement any one of the user call billing methods in the above embodiments.

[0196] In one example, the electronic device may further include a communication interface 703 and a bus 710. Figure 7 As shown, the processor 701, the memory 702, and the communication interface 703 are connected via a bus 710 and communicate with each other.

[0197] The communication interface 703 is mainly used to implement communication between various modules, devices, units and / or devices in the embodiments of the present application.

[0198] Bus 710 comprises hardware, software or both, couples the parts of electronic equipment to each other.For example, and not limitation, bus can comprise accelerated graphics port (AGP) or other graphics bus, enhanced industry standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industry standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations.In suitable cases, bus 710 can comprise one or more buses.Although the present application embodiment describes and shows specific bus, the application considers any suitable bus or interconnection.

[0199] The electronic device can execute the user call billing method in the embodiment of the present application, thereby realizing the user call billing method described in the above user call billing method embodiment.

[0200] In addition, in conjunction with the user call billing method in the above embodiment, the present application embodiment can provide a readable storage medium for implementation. The readable storage medium stores program instructions; when the program instructions are executed by a processor, any one of the user call billing methods in the above embodiment is implemented.

[0201] It should be understood that the present application is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and illustrated as examples. However, the method process of the present application is not limited to the specific steps described and illustrated. Those skilled in the art can make various changes, modifications, and additions, or change the order of the steps after understanding the spirit of the present application.

[0202] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memories, erasable ROMs (EROMs), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0203] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps. In other words, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0204] The flowchart and / or block diagram of the method, device (system) and computer program product according to the embodiment of the present application are described above in various aspects of the present application.It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, to produce a kind of machine, so that these instructions executed via the processor of a computer or other programmable data processing device enable the realization of the function / action specified in one or more boxes of the flowchart and / or block diagram.Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit.It is also understood that each box in the block diagram and / or the flowchart and the combination of the boxes in the block diagram and / or the flowchart can also be realized by the dedicated hardware that performs the specified function or action, or can be realized by the combination of dedicated hardware and computer instructions.

[0205] The above description is only a specific embodiment of the present application. Those skilled in the art will clearly understand that for the convenience and brevity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the scope of protection of the present application.

Claims

1. A user call billing method, characterized in that: Applied to accounting systems, including: Obtain a call record file from a billing system, wherein the call record file includes a file header, billing rules, and an original call record, wherein the file header records a storage location of the billing rules in the call record file; Based on the user number in the original call record, obtaining the user's account data in the user information database; Merging the accounting data and the call record file to obtain a target call record file, wherein a file header of the target call record file records the charging rules and the storage location of the accounting data in the target call record file; Based on the billing rules and the storage location of the account data in the target bill file, respectively reading the account data of the user, the original bill and the billing rules to calculate the bill fee of the user; The step of reading the user's account data, the original call bill, and the billing rule based on the billing rule and the storage location of the account data in the target call bill file to calculate the user's call bill fee includes: Based on the billing rules and the storage location of the account data in the target call record file, respectively read the user's account data, the original call record and the billing rules, perform call record batch pricing, and obtain a batch pricing result; Based on the pricing result, the call bill is consolidated to determine the call bill fee of the user; The step of performing call bill consolidation based on the batch pricing result to determine the call bill fee of the user includes: Based on the batch pricing results of multiple target call record files, the fee of each billing item in the multiple billing items is calculated by a preset billing item calculation method, and the multiple target call record files are target call record files of the same user; Based on the fee of each billing item in the plurality of billing items, the fee of each account item in the plurality of account items is calculated by a preset account item calculation method; The user's call bill charge is determined based on the charge of each account item in the plurality of account items.

2. The method according to claim 1, characterized in that The method of reading the user's account data, the original call record, and the billing rules based on the billing rules and the storage location of the account data in the target call record file, performing call record batch pricing, and obtaining a batch pricing result includes: Based on the storage location of the accounting data in the target call record file, storing the accounting data in a first array of a local shared memory; Based on the storage location of the charging rule in the target call record file, storing the charging rule in a second array of the local shared memory; Based on the account data in the first array and the billing rules in the second array, the original call record is priced to obtain a pricing result.

3. The method according to claim 1, characterized in that After respectively reading the user's account data, the original call bill, and the billing rules based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill fee, the method further includes: Based on the fee of each billing account in the plurality of billing accounts, the balance of each billing account in the plurality of billing accounts is calculated by a preset balance account calculation method; Based on the balance of each billing account in the multiple billing accounts, the credit control status of the user is determined through a preset credit control rule.

4. The method according to claim 1, wherein After respectively reading the user's account data, the original call bill, and the billing rules based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill fee, the method further includes: Based on multiple target call record files, the usage of each billing item in multiple billing items is calculated using a preset usage item calculation method; Based on the usage of each billing item in the multiple billing items, the items to be reminded are determined in the multiple billing items by using a preset reminder item calculation method; Based on the subject to be reminded and preset business reminder rules, the business to be reminded is determined.

5. The method according to claim 1, wherein After respectively reading the user's account data, the original call bill, and the billing rules based on the billing rules and the storage location of the account data in the target call bill file to calculate the user's call bill fee, the method further includes: The call bill charges are sent to the user profile database so that the user profile database updates the account data of the user.

6. A user call billing method, characterized in that: Applied to billing systems, including: Obtain the original call records from the network element side; Identifying the call record type of the original call record; Determining a charging rule for the original call record from a plurality of charging rules based on the call record type; Based on the billing rules and the original bill, a bill file is constructed, wherein the file header of the bill file records the storage location of the billing rules in the bill file; The call bill file is sent to the accounting system so that the accounting system executes the billing method described in any one of claims 1 to 5 to calculate the call bill fee of the user.

7. A billing system, characterized in that: include: A first acquisition module is used to obtain the original call record from the network element side; A call record identification module, configured to identify the call record type of the original call record; A first information processing module, configured to determine a billing rule for the original call record from a plurality of billing rules based on the call record type; A second information processing module constructs a call record file based on the billing rule and the original call record, wherein the file header of the call record file records the storage location of the billing rule in the call record file; A call bill sending module is used to send the call bill file to the accounting system, so that the accounting system executes the billing method described in any one of claims 1 to 5 to calculate the user's call bill fee.

8. An accounting system, characterized in that: include: A second acquisition module is used to obtain a call record file from a billing system, wherein the call record file includes a file header, billing rules, and an original call record, wherein the file header records a storage location of the billing rules in the call record file; A third acquisition module is used to obtain the user's account data from the user information database based on the user number in the original call record; a third information processing module, configured to merge the accounting data and the call record file to obtain a target call record file, wherein a file header of the target call record file records the billing rules and a storage location of the accounting data in the target call record file; A billing module, configured to read the user's account data, the original call bill, and the billing rule based on the billing rule and the storage location of the account data in the target call bill file, so as to calculate the user's call bill fee; It is also used to read the user's account data, the original call record and the billing rules based on the billing rules and the storage location of the account data in the target call record file, perform call record batch pricing, and obtain a batch pricing result; Based on the pricing result, the call bill is consolidated to determine the call bill fee of the user; It is also used to calculate the cost of each billing item in multiple billing items based on the batch pricing results of multiple target call record files using a preset billing item calculation method, and the multiple target call record files are target call record files of the same user; Based on the fee of each billing item in the plurality of billing items, the fee of each account item in the plurality of account items is calculated by a preset account item calculation method; The user's call bill charge is determined based on the charge of each account item in the plurality of account items.

9. An electronic device, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and capable of running on the processor. When the program or instruction is executed by the processor, the steps of the user call billing method as described in any one of claims 1 to 6 are implemented.

10. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, the steps of the user call billing method as described in any one of claims 1-6 are implemented.

Images