Telecom Billing Service: Sub-statement

the problem of arrears has always been a problem for telecom enterprises. In the beginning, the telecom enterprises adopt the model of after-pay, that is, calculate the cost once a month, if the cost is not paid within a certain period of time to stop. Mobile business development, because the user may be due to the cost of the month to stop using this card, so the use of each business to calculate the cost of the model, if the balance is insufficient, the start of downtime. Later found that a single use of the business may also incur a large cost, (especially in the data business), there is online billing (real-time billing), each time the use of the business will judge the balance, only set aside the time (or traffic) can be used, after the balance is exhausted, the use of business will be interrupted.

In the quasi-real-time billing and real-time billing, there is a compromise between the solution, that is, the sub-billing, the so-called single billing, is the switch to produce the telephone, the high cost can be generated by single segmentation, such as the user in the use of voice services, after 30 minutes of phone calls, Switch first out a single statement out to the billing, after the completion of the bill to determine whether the balance is sufficient, if insufficient to issue a shutdown, the network side in the receipt of the outage, the end of user communication (this point has doubts, asked some familiar people, some said can be suspended, some say cannot stop, look forward to answer), avoid causing high arrears

For billing, however, a billing error can result if the split order is not processed separately. For example, a 2-minute statement, cut into 61 seconds and 59 seconds, will be calculated as 3 minutes (less than a minute by one minute calculation, the front count 2 points, followed by 1 points), so users will certainly complain. Therefore, the sub-statement business needs to be charged with separate processing steps. As a general practice, in the case of billing, if it is a sub-statement, after the completion of the billing, to make a record, the next message of the same communication came over, then the record is merged, and according to the combined words of the cost, minus the calculation of the last call, the cost of the bill to get this statement.

The biggest problem in this is the problem of querying the user. User query, you need to query a single word, and then to the management analysis and statistical data, also need to be a statement. The final output of the billing should be a single statement. Therefore, this statement will not be completed before the full billing, not to the warehousing and accounting processing. If not to the account processing, the reference is not the cost of the preceding sub-statement to do the letter-control processing. Lost the meaning of the sub-statement. Therefore, either the query module to make changes, the query to consider the logic of the statement, or the information control module to make changes, the trust when the reference to the sub-statement "reservation" fee. To say that fundamentally solve the problem, it is natural that the Trust module modified better.

There is an ultimate solution, and the process of the sub-statement is very similar to the online billing process. The first order of the statement, the update order, the end order can be mapped to the online billing of the initial package, update package and end package. You can solve all of the above problems by turning the business of the statement into message processing. How is it solved? With the OCS process, the balance will be reserved, which naturally solves the problem.

Billing or message billing, from the surface is a file interface or message interface problems, in fact, the file interface or message interface, only the protocol level, the definition of the relevant file format or message format, the process will not be different. The real difference is the current document billing (OFCS) and message billing (OCS) differences in the balance process. For a long time, due to the inertia of the system, we have divided the system into two pieces of billing and accounting, billing and calculation of the cost, the balance of the deduction costs. So Ofcs in the billing, and did not put the balance of the real deduction, but just do the accumulation, the time of the Trust to refer to the "Available Balance" and the cumulative cost of the size, while OCS billing, the balance will be deducted, when the trust, only refer to the balance. File billing, the most important process is that the balance is not deducted (or withholding), the trust process is to refer to the cumulative cost + balance or only reference balance. File messages go to the message billing, the issue of efficiency aside, is actually only the unification of the two processes.

Of course, there is a big killing device, voice services by the second billing, data services by byte billing, we think it is not?

Telecom Billing Service: Sub-statement