WO2010121513A1

WO2010121513A1 - System and method for billing short messages

Info

Publication number: WO2010121513A1
Application number: PCT/CN2010/071298
Authority: WO
Inventors: 李康; 沈松; 钱程
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-04-20
Filing date: 2010-03-25
Publication date: 2010-10-28
Also published as: CN101547414A; CN101547414B

Abstract

The present invention provides a system and a method for billing short messages. The system comprises a service control point, a short message billing center, and an interface machine connected with the service control point and the short message billing center, wherein: said short message billing center is configured to generate a billing request and send it to said interface machine; said interface machine is configured to receive the billing request and send the billing request to the service control point; and said service control point is configured to receive the billing request sent by the interface machine and perform a billing operation.

Description

SMS billing system and method

TECHNICAL FIELD The present invention relates to telecommunications value-added services, and in particular, to a short message charging system and method.

BACKGROUND With the rapid development of prepaid users, in order to better provide users with high quality value-added services, it is necessary to solve the real-time charging problem of prepaid users. The short message service is an important area for the development of value-added services. The problem of real-time charging for short messages can better expand the user base. SCP (Service Control Point, Service Control) is not required in the relevant specifications issued by the telecommunications industry.

Point ) is directly connected to the SMSC (Short Message Service Center) and SMG (Short Message Gateway, also known as China Unicom in the Short Message Gateway), but adds third-party equipment between the SCP and the SMS device ( The authentication device is operated by the authentication device and the SCP to complete the management of the prepaid service account pricing deduction. Therefore, the device that references the PDSCP (Prepaid Data Service Control Point) is used. PDSCP has the function of centralized pricing for short messages. For point-to-point messages, PDSCP can provide personalized services for users through the maintenance of the rate table. It can set rates for user characteristics. For Unicom's short messages, due to SGIP protocol. With the information fee, the PDSCP can price the user by calculating the sum of the information fee and the communication fee; as shown in Figure 1. However, PDSCP communicates with the SCP, SMC (Web Short Message Center), SMG, SMB (Short Message Bridge) and other nodes in the network through the TCP/IP protocol at the network layer. The network environment is relatively complex to build, and the database application is single. There is no corresponding caching mechanism, and the process of processing the deduction is relatively cumbersome, resulting in poor performance stability.

SUMMARY OF THE INVENTION The technical problem to be solved by the present invention is to provide a short message charging system and method for optimizing a network structure and improving the processing efficiency of short message charging. In order to solve the above technical problem, the present invention provides a short message charging system, including a service control point, a short message charging center, and an interface machine connected to the service control point and the short message charging center. The short message charging center is configured to generate a charging request, and is sent to the interface machine; the interface device is configured to receive an accounting request, and send the charging request to a service control point; The point is set to receive the charging request sent by the interface machine, and perform the charging operation. The above-mentioned short message charging system may also have the following features: the service control point is further configured to send an operation result of the charging operation to the interface machine; the interface machine is further configured to receive an operation result sent by the service control point And forwarding to the short message charging center; the short message charging center is further configured to receive an operation result forwarded by the interface machine. The above-mentioned short message charging system may also have the following features: when the charging request is a debiting request, the charging operation performed by the service control point is a rating and debit processing; when the charging request is a replenishment When requested, the charging operation performed by the service control point is a replenishment process. The above-mentioned short message charging system may also have the following features: The system further includes an operation record database connected to the interface machine, and the interface machine is further configured to: when the charging request is a debit request, receive the service control After the result of the operation sent by the point, if the operation result is a deduction success message, the operation record database is notified to insert the debit record; the interface machine is further configured to: when the charging request is a replenishment request, receive After the replenishment request, the operation record database is first queried, and if the debit record is queried and no replenishment is made, the replenishment request is forwarded to the service control point; and after receiving the operation result sent by the service control point And if the operation result is a replenishment success message, the interface machine notifies the operation record database to tamper with the debit record. The above SMS charging system can also have the following characteristics: The operation record database includes a cache database and a permanent database; the cache database is configured to insert a charge record according to the charge notice of the interface machine, and write the charge record to the permanent database. The foregoing short message charging system may further have the following features: The cache database is divided into a plurality of tables, and the cache database is further configured to determine a table for inserting the charge record by using a modulo result of the operation time. The foregoing SMS charging system may further have the following features: the operation record database includes a cache database and a permanent database; the interface machine is further configured to: query the cache database after receiving the replenishment request, if no corresponding Debit the record, and then query the permanent database. If there is a cache or permanent database corresponding to the debit record, the replenishment request is forwarded to the service control point; and after receiving the operation result sent by the service control point If the operation result is a replenishment success message, the interface machine notifies the cache or permanent database modification deduction record corresponding to the debit record. The short message charging system may also have the following features: The interface machine is implemented on a computer or a server; the short message charging center is a short message service center SMSC or a short message gateway SMG. In order to solve the above technical problem, the present invention provides a short message charging method, including: a short message charging center sends a charging request to an interface machine; the interface machine receives and forwards the charging request to a service control point; The control point receives the charging request and performs a charging operation. The foregoing SMS charging method may further have the following features: after the performing the charging operation at the service control point, the method further includes: the service control point sending an operation result of the charging operation to the interface machine; The operation result sent by the service control point is forwarded to the short message charging Center

The short message charging center receives an operation result forwarded by the interface machine. The foregoing SMS charging method may also have the following features: when the charging request is a debiting request, the charging operation performed by the service control point is a rating and debit processing; when the charging request is a replenishment When requested, the charging operation performed by the service control point is a replenishment process. The foregoing short message charging method may further have the following features: when the charging request is a debiting request, after the interface machine receives the operation result sent by the service control point, if the operation result is a deduction success message And the interface machine notifies the operation record database to insert the chargeback record; when the charging request is a replenishment request, in the step of the interface machine receiving and forwarding the charging request to the service control point, After receiving the replenishment request, the interface machine first queries the operation record database, and if the debit record is queried and no replenishment is made, the replenishment request is forwarded to the service control point; and the service is received at the interface machine. After the operation result sent by the control point, if the operation result is a replenishment success message, the interface machine notifies the operation record database to modify the debit record. The foregoing SMS charging method may further have the following features: the operation record database includes a cache database and a permanent database; when the charging request is a debit request, in the step of notifying the operation record database to insert the charge record, the The interface machine notifies the cache database to insert a charge record, the cache database inserts a charge record, and the charge record in the cache database is periodically written into the permanent database; when the charge request is a replenishment request, In the step of the interface machine receiving and forwarding the charging request to the service control point, the connecting After receiving the replenishment request, the machine first queries the cache database. If the corresponding debit record is not found, the permanent database is queried. If there is a cache or permanent database corresponding to the debit record, the replenishment will be made. The request is forwarded to the service control point; after the interface machine receives the operation result sent by the service control point, if the operation result is a replenishment success message, the interface machine notifies that there is a cache or permanent corresponding to the debit record The database tampers with the debit record. The foregoing short message charging method may further have the following features: The cache database is divided into a plurality of tables, and in the step of inserting the charge record into the cache database, determining the insertion charge record in the cache database by using the modulo result of the operation time table. The foregoing short message charging method may also have the following features: The interface machine is implemented on a computer or a server; the short message charging center is a short message service center SMSC or a short message gateway SMG.

Compared with the prior art, the short message charging system and method of the present invention reforms the PDSCP, switches to the interface mode, efficiently implements billing point migration, integrates resources, optimizes the network structure, and ensures the original PDSCP function. , can increase the number of SCP resources, improve the ability to handle SMS billing. And the original PDSCP needs to be arranged on the server. The modified interface machine can only be supported by an ordinary PC, which greatly reduces the cost of using the device, and the billing performance of the short message is obviously improved; Achieve the purpose of ensuring business performance.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a network structure diagram of a live network PDSCP device. 2 is a structural diagram of a short message charging system of the peer-to-peer short message method of the present invention. FIG. 3 is a structural diagram of a short message charging system in which the communication is in the short message mode according to the present invention. 4 is a schematic diagram of a point-to-point short message deduction process according to a first embodiment of the present invention. FIG. 5 is a schematic diagram of a point-to-point short message replenishment process according to a second embodiment of the present invention. FIG. 6 is a schematic diagram of a process of connecting a credit in a text message according to a third embodiment of the present invention. FIG. 7 is a schematic diagram of a flow of replenishing a text message in the fourth embodiment of the present invention.

BEST MODE FOR CARRYING OUT THE INVENTION The main idea of the present invention is to transform PDSCP into an interface machine, so that it can be loaded and used in any existing server or PC, and the SCP can complete the billing and the replenishment fee. Operation, resource integration, and improve the overall performance of the processing business. In addition, the cache database (Xbase) is added to further ensure that the prepaid subscribers are peer-to-peer and that Unicom's SMS deduction and replenishment are correct, thus achieving the purpose of ensuring business performance. The short message charging system of the present invention comprises a service control point, a short message charging center, an interface machine connected to the service control point and the short message charging center, and an operation record database connected to the interface machine, wherein

The short message charging center is configured to generate a charging request, and is sent to the interface machine; and is further configured to receive an operation result forwarded by the interface machine; where the short message charging center refers to a short message service center SMSC or The short message gateway SMG, the charging request is a debit request or a replenishment request. The interface machine is implemented on a computer or a server, configured to receive a charging request, and send the charging request to a service control point; and further configured to receive an operation result sent by the service control point and forward the result to the short message meter The service control point is configured to receive the charging request sent by the interface device and trigger the corresponding service to perform the charging operation, and is further configured to send the operation result to the interface device. The billing operations performed by the service control point include batch pricing and replenishment processing.

The operation record database is set to save the operation record, and the interface machine is further configured to query the operation record database after receiving the replenishment request, and if the operation record database records the deduction and fails to replenish the payment, the replenishment request is forwarded Give business control points.

The operational record database may further include a cache database and a permanent database. When the charging request is a replenishment request, the interface machine is configured to query the cache database first after receiving the replenishment request, and if the corresponding debit record is not found, query the permanent database, if there is a corresponding debit The cached or permanent database of the record shows that the replenishment request is not replenished, and then the replenishment request is forwarded to the service control point; if the operation result received by the interface machine is a replenishment success message, the interface machine is further configured to notify that there is a corresponding debit Recorded cache or permanent database modification charge record. If the operation result received by the interface machine is a deduction success message, the interface machine is further configured to notify the cache database to insert the debit record, and the debit record in the cache database is periodically written into the permanent database. The cache database is implemented by the Xbase database, divided into several tables by hour, and the corresponding table of the inserted charge records is determined according to the modulo result of the corresponding operation time, and the data in each table is periodically imported into the permanent database. The permanent database is implemented by Sybase database, and all the data is saved, divided into several tables by date, and each table holds the data of the corresponding date.

In the point-to-point SMS mode, as shown in Figure 2, the SMS charging center of the SMS charging system refers to

The SMSC server is implemented by the 360 interface thread. The 360 interface thread communicates with the SMSC server based on the SMPP+ protocol. The 360 interface thread interacts with the SCP through internal messages. In view of the frequent interaction of the charging messages in the point-to-point short message mode. Set up two databases, cache database (Xbase) and permanent database (Sybase). The 360 interface thread controls the update and maintenance of the two databases. The method for charging the SMS based on the above SMS charging system comprises the following steps: a) The SMSC sends the debit or replenishment request of the prepaid user to the corresponding interface machine; b) the interface machine sends the request according to the sent request The SCP triggers the related service and performs deduction or replenishment processing; c) the service returns the operation result to the interface machine after the deduction or replenishment is completed; d) after receiving the message, the interface machine returns the result to the SMSC (SMS center) At the same time, the interface machine inserts a record of the operation into the database. In China Unicom's SMS mode, as shown in Figure 3, the SMS charging center of the SMS charging system refers to the SMG server, the interface machine is implemented by the 359 interface thread, and the 359 interface thread communicates with the SMG server based on the SGIP+ protocol, 359 The interface thread interacts with the SCP through internal messages, and the database controlled by the 359 interface thread refers to the Sybase database. The method for charging the SMS based on the above-mentioned short message charging system includes the following steps: a) SMG (China Unicom in the letter gateway) sends the debit or replenishment message of the prepaid user to the corresponding interface machine;

b) The service interface machine first searches the database for duplicate records according to the sent request, and if it is not sent to the SCP to trigger the related service and performs deduction or replenishment processing; c) after the business is deducted or replenished Return the result to the interface machine; d) After receiving the message, the interface machine returns the result to SMG (China Unicom in the letter gateway), and the interface machine inserts the record of the operation into the database.

The service flow of the short message charging method of the present invention is specifically described below with reference to the accompanying drawings. The first embodiment is shown in FIG. 4, which is a schematic diagram of a point-to-point short message deduction process, which mainly includes the following steps: Step 41: SMSC (SMS center) is sent according to the user. The information determines that the user is a prepaid user, and sends a debit request to the corresponding service interface machine; Step 42: The service interface device sends a message to the SCP according to the sent request and triggers the related service to perform the user's rating and deduction processing. If the service fails to be processed due to the abnormality of the user account balance, the process proceeds to step 43. If the user account is normal and the SCP is successfully debited, step 45 is performed; Step 43: The SCP returns a failure message to the service interface machine; Step 44 : The service interface machine sends a deduction failure message to the SMSC (SMS center), and the process ends; Step 45: The SCP returns a success message to the service interface machine. Step 46: After receiving the success message, the service interface device sends the user's debit operation to the cache database (Xbase) for recording. If the insertion debit operation record is successful, then Step 47: If the insertion deduction operation record fails or times out, step 49 is performed; Step 47: The cache database (Xbase) returns a success message to the service interface machine; Step 48: The service interface machine returns a successful deduction message to the SMSC, and executes Step 411: Step 49: The cache database (Xbase) returns a failure message to the service interface machine; Step 410: The service interface machine still returns a successful debit message to the SMSC; Step 411: The cache database (Xbase) is placed in the table at regular intervals The operation record is imported into the Sybase database by task mode for reservation.

The second embodiment is shown in FIG. 5, which is a schematic diagram of a point-to-point short message replenishment process, which mainly includes the following steps: Step 51: The SMSC (SMS Center) sends a replenishment request to the corresponding service interface machine because the user's short message transmission fails; 52: The service interface machine sends a message to the Xbase database to query the debit record of Table 0, Table 1, and Table 2 according to the sent request, if the user debit record is not queried, step 53 is performed; otherwise, step 57 is performed;

The Xbase database is divided into three tables of 0, 1, and 2. The modulo is taken for the corresponding operation time. The data is inserted into the three tables, and the data is imported from the 0 table to the Sybase database after three hours. , and so on. Because the amount of data stored in the cache database is small, querying the cache database first can improve processing efficiency. Step 53: The cache database (Xbase) does not query the user's chargeback record, and returns the result to the service interface machine; Step 54: The service interface machine sends a message to the Sybase database to query the user's debit record. If the user does not query the user's debit record, go to step 55. Otherwise, go to step 58. Step 55: The Sybase database does not query the user's deduction. Record, and return the result to the service interface machine; Step 56: The service interface machine returns a replenishment failure message to the SMSC (SMS center), and the process ends;

Step 57: The cache database (Xbase) queries the user's chargeback record, and returns the result to the service interface machine, and proceeds to step 59; Step 58: The Sybase database queries the user's chargeback record, and returns the result to the service interface machine; Step 59: The service interface device sends a message to the SCP, and triggers the related service to perform the replenishment process on the user account. If the SCP process user replenishment is successful, step 510 is performed; otherwise, step 514 is performed; Step 510: SCP processes the user replenishment Successfully, returning a success message to the service interface machine; Step 511: The service interface machine returns a successful replenishment message to the SMSC (SMS center); Step 512: If the user data is in the cache database (Xbase), the service interface machine sends a message to the cache database (Xbase) modify the user's operation record, modify it to have been replenished; Step 513: If the user data is on the Sybase database, the service interface machine sends a message to the Sybase database to modify the user's operation record, and the modification is that the payment has been made. End process; Step 514: The SCP fails to replenish the user, and returns a failure message to the service. Step 515: The service interface machine returns a failed replenishment message to the SMSC (SMS center). In the application examples shown in FIG. 4 and FIG. 5 above, for the feature that the traffic volume of the point-to-point short message is large, the cache database is added to provide the efficiency of the charging operation. The third embodiment is shown in FIG. 6 , which is a schematic diagram of the process of debiting the SMS in the communication, and mainly includes the following steps: Step 61: SMG (China Unicom in the gateway) determines that the user is a prepaid user according to the information sent by the user, and sends the buckle. Requests to the corresponding service interface machine; Step 62: The service interface machine sends a message to the Sybase database to query whether there is a chargeback record. If the query fails, step 63 is performed; otherwise, step 65 is performed; Step 63: The Sybase database has duplicate records or the query fails and returns the result to the service interface. Step 64: The service interface machine returns the deduction failure message to the SMG (China Unicom at the gateway), and the process ends;

Step 65: There is no duplicate record in the Sybase database and the result is returned to the service interface machine. Step 66: The service interface machine sends a message to the SCP, and triggers the related service to perform the user's rating and debit processing, if the user account balance is insufficient, etc. If the abnormality reason fails to be processed by the service, go to step 67. If the user account is normal and the service debit is successful, go to step 69. Step 67: The SCP returns the failure message to the service interface machine. Step 68: The service interface machine fails to debit the service. The message is returned to SMG (China Unicom is at the gateway) and the process ends;

Step 69: The SCP returns a success message to the service interface machine. Step 610: The service interface machine sends a message to the Sybase database, and inserts a successful debit record of the user.

Step 611: The service interface machine returns a successful debit message to the SMG (China Unicom in the letter gateway).

The fourth embodiment is shown in FIG. 7 , which is a schematic diagram of the process of replenishing the SMS in the communication, mainly including the following steps: Step 71: SMG (China Unicom in the gateway) sends a replenishment request to the corresponding service because the user's short message transmission fails. Interface machine: Step 72: The service interface machine sends a message to the Sybase database to query the user's debit record in the corresponding date table according to the sent request; if the record is not queried, the query fails, or the record has been replenished, the execution is performed. step

73. Query the debit record to perform step 75. Step 73: The Sybase database does not query the record, the query fails, or the query to the record has been replenished, and the result is returned to the service interface machine; Step 74: The service interface machine sends a replenishment failure message to the SMG (Unicom in the letter gateway) , the process ends;

Step 75: The Sybase database queries the user's chargeback record and returns the result to the service interface. Step 76: The service interface machine returns a message to the Sybase database, and requests the update user's record to be replenished. If the update record fails, the step is performed. 77. If the update record is successful, go to step 79; Step 77: The Sybase database update user record fails, and return a message to the service interface machine; Step 78: The service interface machine sends a replenishment failure message to the SMG (Unicom in the letter gateway) Step 79: The Sybase database updates the user's record successfully, and returns a success message to the service interface machine. Step 710: The service interface machine sends a message to the SCP, and triggers related services to replenish the user, and the SCP replenishment succeeds. Step 711, the SCP replenishment fails to perform step 713; Step 711: The SCP returns a replenishment success message to the service interface machine; Step 712: The service interface machine sends a replenishment success message to the SMG (Unicom at the gateway), and the process ends; Step 713: The SCP returns a replenishment failure message to the service interface machine. Step 714: The service interface machine sends a message to the Sybase database, requesting that the user's record be modified as a chargeback record;

Step 715: The service interface machine sends a replenishment failure message to the SMG (Unicom is in the letter gateway).

Compared with the prior art, the present invention has the following advantages: PDSCP is a complete hardware server plus software-supported complete set of equipment; and the present invention only needs to be loaded and used in any existing server or PC, and the cost is greatly reduced. PDSCP originally had the function of rating. After the completion of the pricing, the SCP will be charged. The processing mechanism is slow and the network runs slowly. The present invention migrates the billing point and directly goes to the SCP for pricing and deduction. , Integrate resources, and optimize the network structure.

PDSCP must use a commercial database alone to ensure operation, and the cost is high. However, the present invention uses a database as a cache device in the interface machine, and the database does not necessarily use a commercial database, such as the Xbase database. This reduces costs and also guarantees the performance of the operation. While the invention has been described in connection with the specific embodiments, the modifications and variations may be Such modifications and variations are considered to be within the scope of the invention and the scope of the appended claims.

INDUSTRIAL APPLICABILITY The present invention provides a short message charging system and method. By modifying a PDSCP, switching to an interface machine mode, efficiently implementing billing point migration, integrating resources, and optimizing network structure, thereby ensuring the original PDSCP function. , can increase the number of SCP resources, improve the ability to handle SMS billing. And the original PDSCP needs to be arranged on the server. The modified interface machine only needs an ordinary PC to support, greatly reducing the cost of using the device, and obviously improving the billing performance of the short message; Achieve the purpose of ensuring business performance.

Claims

Claim

A short message charging system, comprising: a service control point, a short message charging center, and an interface machine connected to the service control point and the short message charging center, wherein the short message charging center is configured to generate a charging request And sending the interface to the interface device; the interface device is configured to receive the charging request, and send the charging request to the service control point; the service control point is configured to receive the charging request sent by the interface device, and execute the meter Fee operation.

2. The short message charging system according to claim 1, wherein: said service control point is further configured to send an operation result of the charging operation to said interface machine; said interface machine is further configured to receive said service control The operation result sent by the point is forwarded to the short message charging center; the short message charging center is further configured to receive the operation result forwarded by the interface machine.

The short message charging system according to claim 1 or 2, wherein: when the charging request is a debiting request, the charging operation performed by the service control point is a lottery and debit processing; When the charging request is a replenishment request, the charging operation performed by the service control point is a replenishment process.

The short message charging system according to claim 1 or 2, wherein: the system further comprises an operation record database connected to the interface machine, wherein the interface machine is further configured to: when the charging request is a debit request And after receiving the operation result sent by the service control point, if the operation result is a deduction success message, notifying the operation record database to insert the debit record; the interface machine is further configured to: when the charging request is When the replenishment request is received, after receiving the replenishment request, the operation record database is first queried, and if the debit record is queried and no replenishment is made, the replenishment request is forwarded to the service control point; and the service is received. The result of the operation sent by the control point Thereafter, if the operation result is a replenishment success message, the interface machine notifies the operation record database to tamper with the debit record.

5. The short message charging system according to claim 4, wherein: the operation record database comprises a cache database and a permanent database; the cache database is configured to insert a charge record according to a charge notice of the interface machine, and The record is written to the permanent database at regular intervals.

6. The short message charging system according to claim 5, wherein: the cache database is divided into a plurality of tables, and the cache database is further configured to determine a table for inserting the charge record by modulating the result of the operation time.

7. The short message charging system according to claim 4, wherein: the operation record database comprises a cache database and a permanent database; and the interface machine is further configured to: query the cache database after receiving the replenishment request, if The corresponding debit record is not found, and the permanent database is queried. If there is a cache or permanent database corresponding to the debit record, the replenishment request is forwarded to the service control point; and, at the service control point, After the sent operation result, if the operation result is a replenishment success message, the interface machine notifies the cache or permanent database modification deduction record corresponding to the debit record.

The short message charging system according to claim 1 or 2, wherein: the interface machine is implemented on a computer or a server; and the short message charging center is a short message service center SMSC or a short message gateway SMG.

A short message charging method, comprising: the short message charging center sends an accounting request to the interface machine; the interface machine receives and forwards the charging request to the service control point; and the service control point receives the charging Request, perform a billing operation.

The method of claim 9, wherein: after the service control point performs the charging operation, the method further includes: the service control point transmitting an operation result of the charging operation to the interface machine; The machine receives the operation result sent by the service control point, and forwards the result to the short message charging center; the short message charging center receives the operation result forwarded by the interface machine.

11. The method according to claim 9 or 10, wherein: when the charging request is a debiting request, the charging operation performed by the service control point is a rating and debit processing; When the request is a replenishment request, the charging operation performed by the service control point is a replenishment process.

12. The method according to claim 10, wherein: when the charging request is a debit request, after the interface machine receives the operation result sent by the service control point, if the operation result is a deduction a success message, the interface machine notifying the operation record database to insert the chargeback record; when the charging request is a replenishment request, in the step of receiving and forwarding the charging request to the service control point by the interface machine, After receiving the replenishment request, the interface machine first queries the operation record database, and if the debit record is queried and no replenishment is made, the replenishment request is forwarded to the service control point; After the operation result sent by the service control point, if the operation result is a replenishment success message, the interface machine notifies the operation record database to modify the debit record.

13. The method of claim 12, wherein: the operation record database comprises a cache database and a permanent database; when the charge request is a chargeback request, In the step of notifying the operation record database to insert the charge record, the interface machine notifies the cache database to insert a charge record, the cache database inserts a charge record, and the charge record in the cache database is periodically written into the Permanent database; when the charging request is a replenishment request,

In the step of the interface machine receiving and forwarding the charging request to the service control point, the interface machine first queries the cache database after receiving the replenishment request, and if the corresponding debit record is not found, the query is further performed. The permanent database, if there is a cache or permanent database corresponding to the debit record, the replenishment request is forwarded to the service control point; after the interface machine receives the operation result sent by the service control point, if If the operation result is a replenishment success message, the interface machine notifies the cache or permanent database tampering with the debit record.

14. The method according to claim 13, wherein: the cache database is divided into a plurality of tables, and in the step of inserting the charge record into the cache database, determining the insertion charge in the cache database by using the modulo result of the operation time Recorded table.

The method according to claim 9 or 10, wherein: the interface machine is implemented on a computer or a server; and the short message charging center is a short message service center SMSC or a short message gateway SMG.