CN115412868A - User ticket charging method, device and medium, charging system and accounting system - Google Patents
User ticket charging method, device and medium, charging system and accounting system Download PDFInfo
- Publication number
- CN115412868A CN115412868A CN202110585620.6A CN202110585620A CN115412868A CN 115412868 A CN115412868 A CN 115412868A CN 202110585620 A CN202110585620 A CN 202110585620A CN 115412868 A CN115412868 A CN 115412868A
- Authority
- CN
- China
- Prior art keywords
- ticket
- charging
- user
- file
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/24—Accounting or billing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/14—Charging, metering or billing arrangements for data wireline or wireless communications
- H04L12/1403—Architecture for metering, charging or billing
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The application discloses a user ticket charging method, device and medium, a charging system and an accounting system. The method comprises the following steps: acquiring a ticket file from a charging system, wherein the ticket file comprises a file header, a charging rule and an original ticket, and the file header records the storage position of the charging rule in the ticket file; acquiring the financial data of a user in a user data database based on the user number in the original call ticket; combining the accounting data and the bill file to obtain a target bill file, wherein a file header in the target bill file records a charging rule and a storage position of the accounting data in the target bill file; and respectively reading the accounting data, the original ticket and the charging rule of the user based on the charging rule and the storage position of the accounting data in the target ticket file so as to calculate the ticket expense of the user. By adopting the method and the device, the technical problem that the access pressure of the user data database of an operator is too large in the prior art can be solved.
Description
Technical Field
The application relates to the technical field of communication, in particular to a user bill charging method, device and medium, a charging system and an accounting system.
Background
With the rapid development of the national communication industry, the amount of call tickets generated by mobile communication is rapidly increasing.
In the prior art, after the call bills are collected, the call bills are distributed to various cities for processing through call bill sorting and call bill routing links, call bill pricing, call bill closing, signal control, reminding and other links are required in the city processing process, the whole call bill charging process is complicated, a user data database needs to be accessed for multiple times, and great access pressure is brought to a database system of an operator.
Disclosure of Invention
An object of the embodiments of the present application is to provide a method, an apparatus, a device, and a storage medium, which can at least solve the technical problem in the prior art that the access pressure of a user profile database of an operator is too large.
The technical scheme of the application is as follows:
in a first aspect, a method for charging a user ticket is provided, which is applied to an accounting system, and the method includes: acquiring a ticket file from a charging system, wherein the ticket file comprises a file header, a charging rule and an original ticket, and the file header records the storage position of the charging rule in the ticket file; acquiring the financial data of a user in a user data database based on the user number in the original call ticket; combining the accounting data and the bill file to obtain a target bill file, wherein a file header in the target bill file records a charging rule and a storage position of the accounting data in the target bill file; and respectively reading the accounting data, the original ticket and the charging rule of the user based on the charging rule and the storage position of the accounting data in the target ticket file so as to calculate the ticket expense of the user.
In some embodiments, based on the storage location of the billing rule and the accounting data in the target ticket file, reading the accounting data, the original ticket and the billing rule of the user respectively to calculate the ticket cost of the user, including:
respectively reading the accounting data, the original ticket and the charging rule of the user based on the charging rule and the storage position of the accounting data in the target ticket file, and rating the ticket to obtain a rating result;
and performing ticket combination based on the rating result, and determining the ticket cost of the user.
In some embodiments, based on the storage location of the billing rule and the accounting data in the target ticket file, reading the accounting data, the original ticket and the billing rule of the user, respectively, and performing ticket rating to obtain a rating result, including:
storing the accounting data into a first array of a local shared memory based on the storage position of the accounting data in the target ticket file;
storing the charging rule into a second array of the local shared memory based on the storage position of the charging rule in the target call ticket file;
and carrying out rating on the original ticket based on the accounting data in the first array and the charging rule in the second array to obtain a rating result.
In some embodiments, the performing the ticket reconciliation based on the rating result and determining the ticket cost of the user includes:
based on rating results of a plurality of target call bill files, calculating the cost of each charging subject in the plurality of charging subjects through a preset charging subject calculation method, wherein the plurality of target call bill files are target call bill files of the same user;
calculating the cost of each account item in the multiple account items by a preset account item calculation method based on the cost of each charging account item in the multiple charging account items;
determining the bill charge of the user based on the charge of each account item in the plurality of account items.
In some embodiments, after reading the billing data, the original ticket and the charging rule of the user respectively based on the storage location of the charging rule and the billing data in the target ticket file to calculate the ticket cost of the user, the method further includes:
calculating to obtain the balance of each charging subject in the plurality of charging subjects through a preset balance subject calculation method based on the cost of each charging subject in the plurality of charging subjects;
and determining the credit control state of the user through a preset credit control rule based on the balance of each charging subject in the plurality of charging subjects.
In some embodiments, after reading the billing data, the original ticket and the charging rule of the user respectively based on the storage location of the charging rule and the billing data in the target ticket file to calculate the ticket cost of the user, the method further includes:
calculating the usage amount of each charging subject in the plurality of charging subjects by a preset usage amount subject calculation method based on the plurality of target call bill files;
determining the subjects to be reminded in the plurality of charging subjects through a preset reminding subject calculation method based on the usage amount of each charging subject in the plurality of charging subjects;
and determining the business to be reminded based on the subject to be reminded and a preset business reminding rule.
In some embodiments, after reading the billing data, the original ticket and the charging rule of the user respectively based on the storage location of the charging rule and the billing data in the target ticket file to calculate the ticket cost of the user, the method further includes:
and sending the call ticket cost to a user data database so as to enable the user data database to update the financial data of the user.
In a second aspect, a method for charging a user ticket is provided, which is applied to a charging system, and includes:
acquiring an original ticket from a network element side;
identifying the bill type of an original bill;
determining a charging rule of an original call ticket in a plurality of charging rules based on the call ticket type;
constructing a ticket file based on the charging rule and the original ticket, wherein the file header of the ticket file records the storage position of the charging rule in the ticket file;
and sending the bill file to an accounting system so that the accounting system executes any one of the charging methods in the first aspect to calculate the bill cost of the user.
In a third aspect, a charging system is provided, including:
a first obtaining module, configured to obtain an original ticket from a network element side;
the call ticket identification module is used for identifying the call ticket type of the original call ticket;
the first information processing module is used for determining the charging rule of the original call ticket in a plurality of charging rules based on the call ticket type;
the second information processing module is used for constructing a ticket file based on the charging rule and the original ticket combination, and the file header of the ticket file records the storage position of the charging rule in the ticket file;
a ticket sending module, configured to send a ticket file to the accounting system, so that the accounting system executes the charging method according to any one of claims 1 to 7 to calculate the ticket cost of the user.
In a fourth aspect, there is provided an accounting system comprising:
the second acquisition module is used for acquiring a call ticket file from the charging system, wherein the call ticket file comprises a file header, a charging rule and an original call ticket, and the file header records the storage position of the charging rule in the call ticket file;
the third acquisition module is used for acquiring the financial data of the user from the user data database based on the user number in the original call ticket;
the third information processing module is used for combining the accounting data and the ticket file to obtain a target ticket file, and a file header in the target ticket file records a charging rule and a storage position of the accounting data in the target ticket file;
and the charging module is used for respectively reading the accounting data, the original ticket and the charging rule of the user based on the charging rule and the storage position of the accounting data in the target ticket file so as to calculate the ticket cost of the user.
In a fifth aspect, an embodiment of the present application provides an electronic device, which includes a processor, a memory, and a program or an instruction stored on the memory and executable on the processor, where the program or the instruction, when executed by the processor, implements the steps of the method for charging a user ticket according to the first aspect.
In a sixth aspect, an embodiment of the present application provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and the program or the instruction, when executed by a processor, implements the steps of the method for charging a user ticket according to the first aspect.
The technical scheme provided by the embodiment of the application at least has the following beneficial effects:
the user bill charging method provided by the embodiment of the application determines the first data node in the user data database based on the user number in the original bill, accesses the first data node in the user data database, obtains all financial data of a user, and only needs to read the user data database once in the whole bill processing process before processing the bill cost of the user, so that the pressure of the user data database is greatly reduced.
The billing rules are stored in the target ticket file, so that the billing rules in a shared memory of local hardware equipment do not need to be read any more, the consistency of the upstream and downstream rules of ticket billing is guaranteed, and the billing accuracy is improved.
The user ticket charging method provided by the embodiment of the application cancels the concept of 'local city' in the downstream link of the original charging method, the downstream processes are completely the same, the 'busy and free' condition can not occur even if the ticket amount of each local city is inconsistent, and the system processing capacity is fully utilized.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the application and are not to be construed as limiting the application.
Fig. 1 is a schematic flow chart of an existing user ticket charging method in an embodiment of the present application;
fig. 2 is a first flowchart of a method for charging a user ticket according to an embodiment of the present application;
fig. 3 is a schematic flow chart illustrating charging of a user ticket based on a target ticket file according to an embodiment of the present application;
fig. 4 is a flowchart illustrating a second method for charging a user ticket according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a charging system according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of an accounting system provided in an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to make the technical solutions of the present application better understood by those of ordinary skill in the art, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. It should be understood that the specific embodiments described herein are intended to be illustrative only and are not intended to be limiting. It will be apparent to one skilled in the art that the present application may be practiced without some of these specific details. The following description of the embodiments is merely intended to provide a better understanding of the present application by illustrating examples thereof.
It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples consistent with certain aspects of the present application, as detailed in the appended claims.
Based on the background technology, in the prior art, the user bill charging process needs to access the user data database for multiple times, which brings great access pressure to the user data database of an operator.
The following describes the existing user ticket charging method in detail with reference to the accompanying drawings.
Fig. 1 shows a schematic flow chart of a conventional user ticket charging method, and as shown in fig. 1, the method may include links such as ticket generation, ticket collection, ticket sorting, ticket routing, ticket pricing, ticket reconciliation, service reminding, and ticket warehousing, which are described in detail below.
Generating a call ticket: the network element side records the mobile communication behavior of the user and generates an original call ticket file.
And (3) ticket collection: and uniformly collecting the original call ticket files of the user generated by the network element side to a charging system through protocols such as FTP (file transfer protocol).
And (4) ticket sorting: the charging system reads the original ticket file and splits the original ticket file (administrative city, service type, etc.) according to the recognized ticket type (GSM/GPRS/SMS/VPMN, etc.).
Ticket routing: the accounting system reads the split call ticket record, reads the user data for the first time according to the user number in the record, and judges which directory of the corresponding city the call ticket record should be sent to for subsequent processing according to the user data.
Bill pricing: the accounting system reads the call bill record sent by the upstream after route judgment corresponding to the process of the local city, reads the user data for the second time, and fills in information such as the user ID, the account item code, the subject code and the like according to the rule in the local shared memory section. The corresponding information in the user profile is then updated for the first time.
And E, ticket reconciliation: the accounting system reads the call bill records after the upstream pricing corresponding to the process of the local city, reads the user data for the third time, combines the information of account items, user subjects, user usage and the like, completes the calculation tasks of user cost, user usage and the like according to the rules in the local shared memory segment, and simultaneously generates user signal control states and user reminding calculation events. The corresponding information in the user profile is then updated a second time.
And the process corresponding to the city calculates the balance of the user and the service prompt according to the ticket: the accounting system reads the user information control state and the user reminding calculation event generated at the upstream, and reads the user data for the fourth time and the fifth time. And calculating the user signal control judgment rule and the user reminding calculation rule according to the rule in the local shared memory segment, and generating a signal control starting and stopping instruction and a user service reminding short message for the users meeting the conditions. Then, the corresponding information state and content in the user profile are updated for the third time and the fourth time.
And (5) storing the call ticket in a warehouse: and storing the call ticket records which have completed all the processes into a database for the user to inquire.
In combination with the above-mentioned subscriber bill charging method in the prior art, the applicant finds that the above-mentioned scheme specifically has the following problems:
1) In the whole bill charging process, the database needs to be accessed 9 times to operate the user data (wherein the reading operation is performed for 5 times, and the writing operation is performed for 4 times), so that the access pressure of the database is increased, and the bill charging efficiency is reduced.
2) In the stages of sorting, pricing, account combination, signal control and reminding of call tickets, rules in a local shared memory of hardware equipment are read, the hardware equipment often has the scale of thousands of machines in the current cloud environment, the rules are independent from each other, the consistency cannot be guaranteed by 100%, the problem that the upstream and downstream rules of call ticket charging are inconsistent easily occurs, and the charging error of a user is caused.
3) The downstream processes of each local city in the accounting system are mutually independent, and when the bill quantity of each local city is inconsistent, the 'busy and free' condition occurs, so that the processing capacity of the system cannot be fully utilized.
Based on the above findings, the embodiments of the present application provide a method, device, medium, charging system, and accounting system for charging a user ticket. The technical scheme provided by the embodiment of the application matches and splices the charging rules of the call bills in the stage of the call bill sorting. In the stage of 'ticket routing', the user data required by charging is matched and spliced. And the spliced call ticket file respectively completes user charging, user reminding and user signal control calculation in the stages of call ticket pricing and call ticket reconciliation. The technical scheme provided by the embodiment of the application changes the reading and using modes of the user account data, the charging rule and the service reminding calculation rule, and realizes the balance and unification of the bill charging efficiency, the database load, the timeliness and the accuracy of the signal control and the reminding timeliness and the accuracy through the method of top layer reading and key information carrying.
The following describes the user ticket charging method provided by the embodiment of the present application in detail with reference to the accompanying drawings.
Fig. 2 shows a schematic flow chart of a user bill charging method provided in this embodiment of the present application, where the method may be applied to an accounting system, and as shown in fig. 2, the user bill charging method 100 may include steps S110 to S140.
Step S110, a call ticket file from a charging system is obtained, the call ticket file comprises a file header, a charging rule and an original call ticket, and the file header records the storage position of the charging rule in the call ticket file.
The charging system, as introduced in the foregoing description for the existing user ticket charging method, is used to collect an original ticket and split an original ticket file according to a ticket type, that is, the ticket collection and ticket sorting process in the foregoing description.
The method comprises the steps of obtaining a ticket file, wherein the ticket file is the ticket file after a charging system splits and processes on the basis of an original ticket file. It should be noted that the ticket file here is different from the ticket file processed by the charging system in the prior art, the ticket file here carries the charging rule corresponding to the original ticket in the ticket file, and the file header records the storage location of the charging rule in the ticket file.
The accounting system, as introduced in the foregoing description for the existing user bill charging method, is used for calculating the cost of the original bill according to the charging rules, that is, the links of bill routing, bill rating, bill reconciliation, bill warehousing and the like in the foregoing description.
The configuration of the accounting system here is different from the above-described conventional accounting system. The existing accounting system is a structure of a headquarter system and a city system, and the headquarter system divides the call ticket files into the corresponding city system for processing through a call ticket routing link. The accounting system is only one system and is not divided into a city system.
The accounting system acquires the processed call ticket file from the charging system, then identifies the user number in the original call ticket of the call ticket file, and carries out subsequent processing based on the user number.
Step S120, based on the user number in the original ticket, the financial data of the user is obtained in the user data database.
The user number can be a telephone number of the user or other identification codes capable of identifying the identity information of the user, and the financial data of the user can be found in the user data database according to the identification codes.
The user data database stores user data information, including the user's account data.
In an example, taking a GSM voice call ticket as an example, the specific accounting data may include the following contents: the user name is provided with the existing voice charging subject and the current record value; existing voice account items and current record values; current account balance subject and current record value; existing signal control state record values; the current voice usage subject and the current record value; the current voice prompts subjects and current recorded values; the existing voice service reminds the state record value.
The accounting system finds the data node where the user data is located in the user data database according to the routing rule and the user number in the original call ticket, accesses the data node, and reads all the accounting side data of the user, namely the accounting data.
Step S130, the accounting data and the bill file are combined to obtain a target bill file, and the file header in the target bill file records the charging rule and the storage position of the accounting data in the target bill file.
And combining the 'accounting data' and the 'ticket file' of the user, recording the storage position of the accounting data in the target ticket file in a file header to obtain the target ticket file, and transmitting the target ticket file to a downstream process.
Step S140, based on the charging rule and the storage position of the accounting data in the target call ticket file, respectively reading the accounting data, the original call ticket and the charging rule of the user to calculate the call ticket cost of the user.
The accounting system can perform bill pricing and bill reconciliation according to the accounting data of the account, the original bill and the charging rule, and the calculation method is similar to the existing scheme in the previous embodiment. The difference between the two is that the target call ticket contains all the data required by the calculation process, so that the user data database does not need to be accessed again in the calculation.
As an example, similar to the existing charging scheme in the foregoing, the method for charging a user ticket according to the embodiment of the present application may also access the user profile database again after the ticket fee of the user is calculated, so as to update the accounting data of the user. Based on this, the method 100 for charging a ticket of a user may further include step S150.
Step S150, the bill charge is sent to the user data database so that the user data database can update the financial data of the user.
After the bill charge of the user is calculated, the accounting system accesses the user data database again to update the accounting data of the user.
The user bill charging method provided by the embodiment of the application determines a first data node in a user data database based on a user number in an original bill, accesses the first data node in the user data database, acquires all financial data of a user, and only needs to read the user data database once in the whole bill processing process before processing to obtain the bill cost of the user, so that the pressure of the user data database is greatly reduced; after the bill charge of the user is calculated, only one write operation is needed, compared with 9 times of access to the user data database (wherein 5 times of read operation and 4 times of write operation) in the original scheme, the whole process is reduced to 2 times of access (wherein 1 time of read operation and 1 time of write operation) at most, through a method of top-level reading and key information carrying, the user data is only read once, and the related rules of charging calculation are also centrally controlled to be issued by 10 devices. Therefore, the expense of a database user data access system in a downstream link is reduced by 80%, the consistency of the dependence rules of a subsequent charging process can be ensured to be 100%, more importantly, the concept of 'city' in the charging downstream link can be cancelled, the processing capacity of the system is fully utilized, and the whole ticket charging efficiency is improved.
The following specifically describes a process of calculating a ticket fee of a user in the embodiment of the present application, that is, the step in the above embodiment is a specific implementation process of 140.
In some embodiments, step S140 may specifically include steps S141-S142.
Step S141, based on the charging rule and the storage position of the accounting data in the target call ticket file, respectively reading the accounting data, the original call ticket and the charging rule of the user, and performing call ticket pricing to obtain a pricing result.
Here, the accounting system does not need to access the user data database again to read user data, and can read the accounting data and the charging rule of the user from the corresponding storage positions according to records in the file header, namely the storage positions of the charging rule and the accounting data in the target ticket file, and then read the original ticket in the target ticket file to perform ticket pricing, so as to obtain a pricing result.
As an example, the accounting system needs to perform caching after reading the accounting data, the original ticket, and the charging rule of the user, and then perform the relevant processing. Based on this, step S141 may specifically include steps S1411-S1413.
Step S1411, storing the accounting data in the first array of the local shared memory based on the storage location of the accounting data in the target ticket file.
Step S1412, based on the storage location of the charging rule in the target ticket file, stores the charging rule into the second array of the local shared memory.
And step S1413, rating the original call bill based on the account data in the first array and the charging rule in the second array to obtain a rating result.
As an example, the ticket reconciliation may include a plurality of processing procedures, that is, step S142 may specifically include steps S1421 to S1423.
Step S1421, based on the rating results of the multiple target call ticket files, calculating the charge of each charging subject in the multiple charging subjects by a preset charging subject calculation method, where the multiple target call ticket files are target call ticket files of the same user.
Step S1422, based on the cost of each charging subject in the plurality of charging subjects, calculating the cost of each account item in the plurality of account items by using a preset account item calculation method.
Step S1423, based on the cost of each account item in the multiple account items, determining the call ticket cost of the user.
For ease of understanding, the above steps S141 to S142 will be described in detail below with a specific example.
Fig. 3 shows a flow of charging the user's call ticket based on the target call ticket file, including the call ticket rating and the call ticket reconciliation.
The bill pricing process reads a target bill file generated after routing processing at the upstream, and operates according to the following detailed flow:
1) Starting from the 33 th Byte of a ticket record (C1, cn, B1 and Bn are all 8 Bytes occupying 32 bytes), continuously reading the Cn Byte, storing the Cn Byte into a local shared memory variable X1, and putting data analyzed from the X1 into a local shared memory array T1, which corresponds to the steps 1, 2 and 3 in the flow of the attached figure 3;
2) Continuing to read Bn bytes, storing the Bn bytes into a local shared memory variable X2, and putting the data analyzed from the X2 into a local shared memory array T2, which corresponds to the step 4, the step 5 and the step 6 in the flow of the attached drawing 3;
3) Continuing to read An bytes and storing the read An bytes into a local shared memory variable X3, which corresponds to step 7 and step 8 in the flow of the attached figure 3;
4) Taking the array T1 as a sample, completing matching in the array T2, and updating the value of the corresponding data in the array T2. Reading the use amount information in the variable X3, and updating the value of the corresponding data in the array T2, which corresponds to step 9 in the flow of fig. 3;
the ticket reconciliation process directly reads the corresponding array T2 in the local shared memory, and performs the operations according to the following sequence corresponding to step 10, step 11 and step 12 in the flow of fig. 3:
1) Reading a charging subject calculation formula, calculating according to the existing voice charging subject codes and data corresponding to each subject, and updating calculation results in an array T2;
2) Reading an account item calculation formula, calculating according to the existing voice account item codes and data corresponding to each account item, and updating a calculation result in an array T2;
3) Reading a balance subject calculation formula, calculating according to the existing account balance subject codes and data corresponding to each subject, and updating calculation results in an array T2;
4) Reading a credit control calculation formula, finishing secondary calculation according to the account balance subject calculation result in the previous step, and updating the existing credit control state record in an array T2;
5) Reading a usage amount subject calculation formula, calculating according to the existing voice usage amount subject codes and data corresponding to each subject, and updating calculation results in an array T2;
6) Reading a reminding subject calculation formula, calculating according to the existing voice reminding subject codes and data corresponding to each subject, and updating calculation results in an array T2;
7) Reading a service reminding calculation formula, finishing secondary calculation according to the calculation result of the reminding subject in the previous step, and updating the existing service reminding state record in the group T2;
the user ticket charging method provided by the embodiment of the application cancels the concept of 'local city' in the downstream link of the original charging method, the downstream processes are completely the same, the 'busy and free' condition can not occur even if the ticket amount of each local city is inconsistent, and the system processing capacity is fully utilized.
In some embodiments, after the billing data, the original ticket and the charging rule of the user are respectively read based on the storage location of the charging rule and the billing data in the target ticket file to calculate the ticket cost of the user, the method 100 for charging a ticket of the user may further include steps S143 to S144.
Step S143, calculating to obtain the balance of each billing subject in the plurality of billing subjects through a preset balance subject calculation method based on the charge of each billing subject in the plurality of billing subjects;
and step S144, determining the credit control state of the user through a preset credit control rule based on the balance of each billing department in a plurality of billing departments.
In some embodiments, after the billing data, the original ticket, and the charging rule of the user are respectively read based on the storage location of the charging rule and the billing data in the target ticket file to calculate the ticket cost of the user, the method 100 for charging a ticket of the user may further include steps S145 to S147.
Step S145, calculating the usage amount of each charging subject in the plurality of charging subjects by a preset usage amount subject calculation method based on the plurality of target call bill files;
step S146, determining the subject to be reminded in the plurality of charging subjects through a preset reminding subject calculation method based on the usage amount of each charging subject in the plurality of charging subjects;
and step S147, determining the service to be reminded based on the subject to be reminded and the preset service reminding rule.
With continued reference to FIG. 3, the above steps S143-S147 will be described in detail.
How to perform user signaling control and service reminding calculation in the downstream process of the charging and accounting system corresponds to step 13 and step 14 in the flow of fig. 3.
In the process of processing the above-mentioned reconciliation process, reading the corresponding array T2 in the local shared memory, and completing the user information control calculation and the user service reminding calculation.
1) Reading a credit control calculation formula, finishing secondary calculation according to the account balance subject calculation result in the previous step, and updating the existing credit control state record in an array T2;
1) Reading a service reminding calculation formula, finishing secondary calculation according to the calculation result of the reminding subject in the previous step, and updating the existing service reminding state record in the group T2;
as an example, the foregoing step S150, the specific implementation process thereof may correspond to step 15 and step 16 in the flow of fig. 3.
And the ticket reconciliation process directly reads the corresponding array T2 in the local shared memory, finishes matching in the array T1 by taking the array T2 as a sample, and updates the value of the corresponding data in the array T1. And finally, reading the data in the array T1 line by line in a circular scanning mode, and writing spliced SQL statements into a database to finish the updating of the financial side data of the user.
According to the user ticket charging method provided by the embodiment of the application, after the ticket type is identified, a ticket file header is generated, the matched charging calculation rule, the user account side data and the user original communication ticket are sequentially spliced and integrated, the charging information carrying is completed, the charging rule and the user data are spliced in a rating link, a ticket file is obtained, the ticket charging, the signal control calculation and the reminding calculation are completed, and the access efficiency and the utilization efficiency of a user data database are improved.
Based on the same inventive concept, corresponding to the above embodiments, the embodiment of the present application further provides a user ticket charging method, which is applied to a charging system.
Fig. 4 shows a flowchart of a user ticket charging method provided in an embodiment of the present application, where the method may be applied to a charging system, and as shown in fig. 4, the user ticket charging method 200 may include steps S210-S250.
Step S210, obtaining an original call ticket from a network element side.
And (3) an original call bill, wherein the network element side records the mobile communication behavior of the user and generates an original call bill file.
The charging system collects the original phone bill files of the user generated by the network element side to the charging system step S220 through protocols such as FTP, and identifies the phone bill types of the original phone bills.
In a specific example, the charging system can identify the call ticket type, generate a "record file header", and splice the record file header at the head end of the user call ticket file. In the charging and sorting process, the user call records in the original call ticket file need to be read one by one, and the call records are split according to the recognized call ticket types (GSM/GPRS/SMS/VPMN, etc.).
Step S230, based on the type of the call ticket, determining the charging rule of the original call ticket in the plurality of charging rules.
In one example, the charging system may match the corresponding downstream calculation rule according to the split ticket type, and generate a corresponding "calculation rule file header". The sorting process reads a communication record of the user from the original call ticket, and the size of the record is (An-A1) Byte. For example, after identification, the communication record is a GSM voice call ticket, and a calculation rule for charging the call ticket is found according to the type of the call ticket.
Step S240, based on the charging rule and the original ticket, a ticket file is constructed, and the file header of the ticket file records the storage position of the charging rule in the ticket file.
The charging system splices the charging rule between the 'recording file header' and the 'user ticket file', and then records the storage position of the charging rule in the ticket file in the file header, specifically the Byte number occupied by the charging rule.
Step S250, the ticket file is sent to the accounting system, so that the accounting system executes the charging method provided in any of the above embodiments, and calculates the ticket cost of the user.
The billing system sends the ticket file to the accounting system, and the accounting system can calculate the ticket cost of the user by executing the user ticket billing method provided by any embodiment.
It should be noted that, the charging rule herein may include the following:
the existing voice charging subject codes and the data storage bits corresponding to each subject; existing voice account item codes and data storage bits corresponding to each account item; the existing account balance subject codes and the data storage positions corresponding to each subject; recording the existing signal control state; the existing voice usage subject codes and data storage bits corresponding to each subject; the existing voice reminding subject codes and data storage bits corresponding to each subject; recording the reminding state of the existing voice service; storing the voice usage data recorded in the current call ticket; a charging subject correlation calculation method; account item related calculation methods; a balance subject related calculation method; a usage amount subject related calculation method; a signal control calculation method; and reminding the subject related calculation method.
According to the user ticket charging method provided by the embodiment of the application, the charging rules are spliced in the ticket file, so that in the subsequent ticket pricing process, the charging rules in the shared memory of the local hardware equipment do not need to be read, the consistency of the upstream and downstream rules of ticket charging is guaranteed, and the charging accuracy is improved.
Based on the same inventive concept, the embodiment of the present application also provides a charging system corresponding to the embodiment of the user ticket charging method in fig. 4.
Fig. 5 shows a schematic structural diagram of a charging system provided in an embodiment of the present application, and as shown in fig. 5, the charging system 500 may include:
a first obtaining module 510, configured to obtain an original ticket from a network element side;
a ticket identification module 520, configured to identify a ticket type of an original ticket;
a first information processing module 530, configured to determine, based on the type of the ticket, a charging rule of an original ticket among the multiple charging rules;
the second information processing module 540, which constructs a ticket file based on the charging rule and the original ticket combination, wherein the file header of the ticket file records the storage position of the charging rule in the ticket file;
the ticket sending module 550 is configured to send the ticket file to the accounting system, so that the accounting system executes the user ticket charging method provided in any embodiment to calculate the ticket cost of the user.
The charging system provided in the embodiment of the present application may be configured to execute the steps executed by the charging system in the user ticket charging method provided in each method embodiment, and the implementation principle and the technical effect are similar, and for the sake of brevity, no further description is given here.
Based on the same inventive concept, the embodiment of the application also provides an accounting system.
Fig. 6 shows an accounting system provided in an embodiment of the present application, and as shown in fig. 6, the accounting system 600 may include:
the second obtaining module 610 may be configured to obtain a ticket file from the charging system, where the ticket file includes a file header, a charging rule, and an original ticket, and the file header records a storage location of the charging rule in the ticket file;
a third obtaining module 620, configured to obtain financial data of the user from a user profile database based on the user number in the original ticket;
the third information processing module 630 may be configured to combine the accounting data and the ticket file to obtain a target ticket file, where a file header in the target ticket file records a charging rule and a storage location of the accounting data in the target ticket file;
the charging module 640 may be configured to read the accounting data, the original ticket, and the charging rule of the user based on the storage location of the charging rule and the accounting data in the target ticket file, so as to calculate the ticket cost of the user.
In some embodiments, the charging module 640 may specifically include a rating unit and a reconciliation unit.
And the pricing unit can be used for respectively reading the financial data, the original call ticket and the charging rule of the user based on the charging rule and the storage position of the financial data in the target call ticket file, and carrying out call ticket pricing to obtain a pricing result.
And the reconciliation unit can be used for performing ticket reconciliation based on the rating result and determining the ticket cost of the user.
As an example, the rating unit may specifically include a first information processing component, a second information processing component, and a rating component.
The first information processing component can be used for storing the financial data into a first array of the local shared memory based on the storage position of the financial data in the target ticket file;
the second information processing component can be used for storing the charging rule into a second array of the local shared memory based on the storage position of the charging rule in the target ticket file;
and the pricing component can be used for pricing the original ticket based on the financial data in the first array and the charging rule in the second array to obtain a pricing result.
As an example, the billing unit may specifically include a first computing component, and a billing component.
The first calculation component can be used for calculating the cost of each charging subject in a plurality of charging subjects by a preset charging subject calculation method based on rating results of a plurality of target call bill files, wherein the plurality of target call bill files are target call bill files of the same user;
the second calculating component is used for calculating the cost of each account item in the multiple account items through a preset account item calculating method based on the cost of each charging account in the multiple charging accounts;
the reconciliation component can be used for determining the call ticket cost of the user based on the cost of each account item in the plurality of account items.
In some embodiments, the accounting system 600 may further include a first computing module and a signaling module.
The first calculation module may be configured to read the accounting data, the original ticket, and the charging rule of the user based on the charging rule and a storage location of the accounting data in the target ticket file, respectively, to calculate a ticket fee of the user, and then calculate, based on a fee of each charging subject in the plurality of charging subjects, a balance of each charging subject in the plurality of charging subjects by using a preset balance subject calculation method.
And the signal control module can be used for determining the signal control state of the user through a preset signal control rule based on the balance of each billing department in a plurality of billing departments.
In some embodiments, the accounting system 600 may further include a second computing module, a third computing module, and a service reminding module.
The second calculation module may be configured to read the billing data, the original ticket, and the charging rule of the user based on the charging rule and a storage location of the billing data in the target ticket file, respectively, to calculate a usage amount of each of the plurality of charging subjects based on the plurality of target ticket files and by a preset usage amount subject calculation method after calculating the ticket charges of the user.
The third calculation module may be configured to determine, based on the usage amount of each of the plurality of billing subjects, a subject to be reminded among the plurality of billing subjects by a preset reminding subject calculation method.
And the service reminding module can be used for determining the service to be reminded based on the subject to be reminded and a preset service reminding rule.
In some embodiments, the accounting system 600 may also include a database update module.
And the database updating module can be used for respectively reading the accounting data, the original ticket and the charging rule of the user based on the charging rule and the storage position of the accounting data in the target ticket file so as to calculate the ticket cost of the user and then send the ticket cost to the user data database, so that the user data database updates the accounting data of the user.
The accounting system provided in the embodiment of the present application may be configured to execute the steps executed by the accounting system in the user ticket charging method provided in the foregoing method embodiments, and the implementation principle and technical effects are similar, and for the sake of brevity, no further description is given here.
Based on the same inventive concept, the embodiment of the application also provides the electronic equipment.
Fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application. As shown in fig. 7, the electronic device may include a processor 701 and a memory 702 storing computer programs or instructions.
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.
The processor 701 reads and executes the computer program instructions stored in the memory 702 to implement any one of the above-described embodiments of the method for charging a subscriber's telephone bill.
In one example, the electronic device may also include a communication interface 703 and a bus 710. As shown in fig. 7, the processor 701, the memory 702, and the communication interface 703 are connected by a bus 710 to complete communication therebetween.
The communication interface 703 is mainly used for implementing communication between modules, devices, units, and/or devices in this embodiment of the application.
The electronic device can execute the user call ticket charging method in the embodiment of the application, thereby realizing the user call ticket charging method described in the embodiment of the user call ticket charging method.
In addition, by combining the user ticket charging method in the above embodiment, the embodiment of the present application can provide a readable storage medium to implement. The readable storage medium having stored thereon program instructions; when executed by the processor, the program instruction implements any one of the user ticket charging methods in the above embodiments.
It is to be understood that the present application is not limited to the particular arrangements and instrumentalities described above and shown in the attached drawings. A detailed description of known methods is omitted herein for the sake of brevity. In the above embodiments, several specific steps are described and shown as examples. However, the method processes of the present application are not limited to the specific steps described and illustrated, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps, after comprehending the spirit of the present application.
The functional blocks shown in the above-described structural block diagrams may be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, it may be, for example, an electronic circuit, an Application Specific Integrated Circuit (ASIC), suitable firmware, plug-in, function card, or the like. When implemented in software, the elements of the present application are the programs or code segments used to perform the required tasks. The program or code segments may be stored in a machine-readable medium or transmitted by a data signal carried in a carrier wave over a transmission medium or a communication link. A "machine-readable medium" may include any medium that can store or transfer information. Examples of a machine-readable medium include an electronic circuit, a semiconductor memory device, a ROM, a flash memory, an Erasable ROM (EROM), a floppy disk, a CD-ROM, an optical disk, a hard disk, an optical fiber medium, a Radio Frequency (RF) link, and so forth. The code segments may be downloaded via computer networks such as the internet, intranet, etc.
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, the present application is not limited to the order of the above-described steps, that is, the steps may be performed in the order mentioned in the embodiments, may be performed in an order different from the order in the embodiments, or may be performed simultaneously.
Aspects of the present application are described above with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions/acts specified in the flowchart and/or block diagram block or blocks. Such a processor may be, but is not limited to, a general purpose processor, a special purpose processor, an application specific processor, or a field programmable logic circuit. It will also be understood that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware for performing the specified functions or acts, or combinations of special purpose hardware and computer instructions.
As described above, only the specific embodiments of the present application are provided, and it can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the module and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again. It should be understood that the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive various equivalent modifications or substitutions within the technical scope of the present application, and these modifications or substitutions should be covered within the scope of the present application.
Claims (12)
1. A user ticket charging method is applied to an accounting system and comprises the following steps:
acquiring a ticket file from a charging system, wherein the ticket file comprises a file header, a charging rule and an original ticket, and the file header records the storage position of the charging rule in the ticket file;
acquiring financial data of the user from a user data database based on the user number in the original call ticket;
combining the accounting data and the bill file to obtain a target bill file, wherein a file header in the target bill file records the charging rule and the storage position of the accounting data in the target bill file;
and respectively reading the accounting data, the original ticket and the charging rule of the user based on the charging rule and the storage position of the accounting data in the target ticket file so as to calculate the ticket expense of the user.
2. The method of claim 1, wherein the reading the billing data, the original ticket, and the charging rule of the user based on the charging rule and the storage location of the billing data in the target ticket file, respectively, to calculate the ticket cost of the user comprises:
respectively reading the accounting data, the original ticket and the charging rule of the user based on the charging rule and the storage position of the accounting data in the target ticket file, and carrying out ticket pricing to obtain a pricing result;
and performing ticket combination based on the rating result, and determining the ticket cost of the user.
3. The method of claim 2, wherein the reading the billing data of the user, the original ticket and the charging rule based on the charging rule and the storage location of the billing data in the target ticket file, respectively, and performing ticket rating to obtain a rating result comprises:
storing the accounting data into a first array of a local shared memory based on the storage position of the accounting data in the target ticket file;
storing the charging rule into a second array of a local shared memory based on the storage position of the charging rule in the target call ticket file;
and performing rating on the original call ticket based on the accounting data in the first array and the charging rule in the second array to obtain a rating result.
4. The method of claim 3, wherein the performing a ticket reconciliation based on the rating result to determine the ticket cost of the user comprises:
calculating the cost of each charging subject in a plurality of charging subjects by a preset charging subject calculation method based on the rating results of a plurality of target call bill files, wherein the plurality of target call bill files are target call bill files of the same user;
calculating the cost of each account item in the multiple account items by a preset account item calculating method based on the cost of each charging subject in the multiple charging subjects;
and determining the bill charge of the user based on the charge of each account item in the plurality of account items.
5. The method of claim 4, wherein after reading the billing data, the original ticket and the charging rule of the user based on the charging rule and the storage location of the billing data in the target ticket file, respectively, to calculate the ticket cost of the user, the method further comprises:
calculating to obtain the balance of each charging subject in the plurality of charging subjects through a preset balance subject calculation method based on the cost of each charging subject in the plurality of charging subjects;
and determining the credit control state of the user through a preset credit control rule based on the balance of each charging subject in the plurality of charging subjects.
6. The method of claim 4, wherein after the reading the billing data, the original ticket, and the charging rule of the user based on the charging rule and the storage location of the billing data in the target ticket file to calculate the ticket cost of the user, the method further comprises:
calculating the usage amount of each charging subject in the plurality of charging subjects by a preset usage amount subject calculation method based on the plurality of target call bill files;
determining the subjects to be reminded in the plurality of charging subjects through a preset reminding subject calculation method based on the usage amount of each charging subject in the plurality of charging subjects;
and determining the business to be reminded based on the subject to be reminded and a preset business reminding rule.
7. The method of claim 1, wherein after reading the billing data, the original ticket and the charging rule of the user based on the charging rule and the storage location of the billing data in the target ticket file, respectively, to calculate the ticket cost of the user, the method further comprises:
and sending the call ticket cost to the user data database so as to enable the user data database to update the financial data of the user.
8. A user call ticket charging method is applied to a charging system and comprises the following steps:
acquiring an original ticket from a network element side;
identifying the bill list type of the original bill list;
determining a charging rule of the original call ticket in a plurality of charging rules based on the call ticket type;
constructing a ticket file based on the charging rule and the original ticket, wherein the file header of the ticket file records the storage position of the charging rule in the ticket file;
and sending the ticket file to an accounting system so that the accounting system executes the charging method of any one of claims 1 to 7 to calculate the ticket cost of the user.
9. A charging system, comprising:
a first obtaining module, configured to obtain an original ticket from a network element side;
the call ticket identification module is used for identifying the call ticket type of the original call ticket;
the first information processing module is used for determining the charging rule of the original call ticket in a plurality of charging rules based on the call ticket type;
the second information processing module is used for constructing a ticket file based on the charging rule and the original ticket combination, and the file header of the ticket file records the storage position of the charging rule in the ticket file;
a bill sending module, configured to send the bill file to an accounting system, so that the accounting system executes the charging method according to any one of claims 1 to 7, and calculates a bill cost of the user.
10. An accounting system, comprising:
the second acquisition module is used for acquiring a ticket file from a charging system, wherein the ticket file comprises a file header, a charging rule and an original ticket, and the file header records the storage position of the charging rule in the ticket file;
a third obtaining module, configured to obtain, based on the user number in the original ticket, account data of the user from a user profile database;
the third information processing module is used for combining the accounting data and the ticket file to obtain a target ticket file, wherein the file header in the target ticket file records the charging rule and the storage position of the accounting data in the target ticket file;
and the charging module is used for respectively reading the accounting data, the original call ticket and the charging rule of the user based on the charging rule and the storage position of the accounting data in the target call ticket file so as to calculate the call ticket cost of the user.
11. An electronic device comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method for billing a subscriber's telephone bill as claimed in any one of claims 1 to 8.
12. A readable storage medium, on which a program or instructions are stored, which when executed by a processor implement the steps of the method for charging a subscriber's telephone bill according to any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110585620.6A CN115412868A (en) | 2021-05-27 | 2021-05-27 | User ticket charging method, device and medium, charging system and accounting system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110585620.6A CN115412868A (en) | 2021-05-27 | 2021-05-27 | User ticket charging method, device and medium, charging system and accounting system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115412868A true CN115412868A (en) | 2022-11-29 |
Family
ID=84155262
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110585620.6A Pending CN115412868A (en) | 2021-05-27 | 2021-05-27 | User ticket charging method, device and medium, charging system and accounting system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115412868A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116684837A (en) * | 2023-07-19 | 2023-09-01 | 贵阳朗玛通信科技有限公司 | Billing preprocessing method and device for ticket |
-
2021
- 2021-05-27 CN CN202110585620.6A patent/CN115412868A/en active Pending
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN116684837A (en) * | 2023-07-19 | 2023-09-01 | 贵阳朗玛通信科技有限公司 | Billing preprocessing method and device for ticket |
| CN116684837B (en) * | 2023-07-19 | 2023-10-03 | 贵阳朗玛通信科技有限公司 | Billing preprocessing method and device for ticket |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112686746A (en) | Credit flow configuration method, device and equipment | |
| CN114064112A (en) | Business process configuration method, device, equipment and storage medium | |
| CN109582550A (en) | A kind of method, apparatus and server obtaining full dose business scenario failure collection | |
| CN107180343B (en) | Method and device for automatic payment | |
| CN115271697A (en) | Payment method, payment device, payment equipment, readable storage medium and computer program product | |
| CN115412868A (en) | User ticket charging method, device and medium, charging system and accounting system | |
| CN109951838B (en) | Method, device, equipment and medium for identifying double-card-slot and double-card user | |
| CN110972091B (en) | Communication charging method, device, equipment, medium and terminal | |
| CN111210345B (en) | Signature method and device based on block chain network transaction and terminal equipment | |
| CN108629699B (en) | Data uploading method, data uploading equipment, storage medium and device | |
| CN110677446A (en) | Method and device for identifying family group users | |
| CN115063132A (en) | Information processing method, apparatus, device, storage medium, and program product | |
| CN112801767A (en) | Accounting data processing method and device for newly added channels | |
| CN112449063B (en) | Call bill checking method, device, equipment and medium | |
| CN113496288B (en) | User stability determining method, device, equipment and storage medium | |
| CN110662169B (en) | Terminal equipment matching method and device | |
| CN114202301A (en) | Method and device for processing to-and-fro business data and terminal equipment | |
| CN114647672A (en) | General ledger index information pushing method, device, equipment, medium and program product | |
| CN115249163A (en) | User identification method, device, equipment and storage medium | |
| CN111353779A (en) | Method, device, equipment and storage medium for determining abnormal service provider | |
| CN114399302A (en) | Processing method and processing device for payment of parking lot group | |
| CN114266661A (en) | Data matching method and data matching device | |
| CN115473968A (en) | Call bill processing method and device | |
| CN115250421A (en) | Method and device for determining user permanent station, electronic equipment and storage medium | |
| CN115858531A (en) | Configuration method, device, equipment, medium and product of structured parameter table |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |