CN103095946B - Charging method, charging system and charging device of rechargeable card - Google Patents

Abstract

The invention discloses a method, system and device for recharging a recharge card. Wherein the method includes: according to the received recharge request, initiate a recharge card status authentication request to the VC of the user to be recharged; initiate a recharge card validity authentication request to BOSS; receive the first authentication response signaling of VC and BOSS After the second authentication response signaling, initiate a recharge request to the BOSS. The present invention authenticates the validity of the recharge card at BOSS and VC respectively during the recharge process, and confirms that only normally sold recharge cards can be used, and unsold recharge cards are also unavailable on the VC side , to avoid financial loss and complaints caused by data out-of-sync between BOSS and VC, reduce the financial risk of operators, and improve user satisfaction.

Description

Method, system and device for recharging a recharge card

technical field

The invention relates to the technical field of telecommunications, in particular to a method, system and device for recharging a recharge card.

Background technique

As an expansion method of ordinary payment, recharge card recharge is playing an increasingly important role due to its fast and convenient advantages, and occupies a large part of the proportion of payment. Recharge card recharge is a voice value-added service that users do not need to go to the business hall, but pay for services such as fixed telephones and mobile phones by purchasing a recharge card, dialing a service access code or surfing the Internet.

The recharge card management system includes management node SMP (Sevice Management Point, business management node), management access node SMAP (Sevice Management Access Point, business management access node), business support system BOSS (Business&Operation Support System, telecom business operation support system ), the user to be recharged belongs to SCP (Sevice Control Point, service control node), and the recharge center VC (Voucher Center, recharge center).

SMP is a service exchange node, which realizes the management of recharge card data in VC, and at the same time, serves as the interface between BOSS and VC, and realizes the recharge of user BOSS account.

SMAP is a management access node, and realizes the management of recharge card information in VC through SMP.

BOSS is a business support system to realize recharge card resource management.

The SCP is the signaling access control part. After the user dials the access code, the message is triggered to the SCP, and the SCP controls the entire process of the recharge call.

VC is the recharge center, which maintains the recharge card information and authenticates the validity of the recharge card.

As shown in Figure 1, in the existing recharge card management technical scheme, both BOSS and VC have independent local databases. The BOSS system focuses on resource management, including recharge card sales and other information; VC focuses on recharge card availability information management, including Information such as whether the recharge card can be used, whether it has been recharged, etc.

The generation and management of recharge card data are shown in the two thick lines in Figure 1, and the data of the two systems are independent. The recharge card management personnel realize the management of recharge card resource information in VC through SMAP, and realize the management of recharge card sales information through the dedicated client of BOSS. There is an isolation between the two databases.

This isolation leads to the possibility of inconsistencies in the data in the two databases. On the one hand, the recharge card in VC may be available, but the recharge card in BOSS may not be available. At this time, if the recharge card is used, it will bring economic losses to the operator. ; On the other hand, the recharge card data in VC is unavailable, and the BOSS recharge card may be sold, which brings the risk that users cannot use it to make complaints.

At the same time, there are also some technical drawbacks in the real-time signaling process used by the recharge card. As shown in Figure 2, after the user dials the access code, the message is triggered to the SCP, and the SCP controls the entire process of the recharge call and sends a message to the recharge center VC sends recharge card status query and position setting signaling; VC, as a recharge center, stores all recharge card information, authenticates the validity of recharge cards during the recharge process, sets recharge card information after recharge is completed, and replies to the SCP for recharge Card status query results and setting responses; BOSS, as the recharge card management part and billing system, manages the resources of the recharge card and enters the recharge amount into the account.

During this process, if the SCP fails to receive the setting feedback message from the VC due to occasional signaling transmission loss or signaling discarding due to excessive delay, the system will default to The user recharges successfully, as shown in the thick line in the figure (the part of interacting with the BOSS is omitted).

In order to avoid economic risks and enhance system security, in the existing technology, there are some solutions to solve this situation, such as Chinese patent CN101753745, which provides the following technical solutions. A record table is established in the SCP to record the default recharge successful recharge When the user recharges through the SCP again, the SCP will first check whether the recharge card used by the user has a default recharge success. If so, the recharge card is considered to have been used and cannot be used again.

Both BOSS and VC have independent local databases, and the BOSS and VC systems manage different information of recharge cards respectively. BOSS manages the sales information of recharge cards, and VC manages information such as the use of recharge cards. There should be a certain correspondence between these information. Recharge card management personnel need to use dedicated and independent terminals to manage recharge card data of BOSS and VC respectively.

Since the two databases are independent, there are dedicated terminals for data management of the two databases, so the data of the two databases is also isolated. There is no synchronization mechanism between the two, which makes it easy for unsold recharge cards to flow into the hands of users due to misselling recharge cards or poor channel management. When users dial the service access code for use, the system cannot accurately identify and cause financial losses and Complaints, possible situations are not limited to the following.

The recharge cards that are not sold in the BOSS system are already available on VC, and there is a risk of malicious use and loss of funds. The recharge cards that have been sold by BOSS have not been maintained in the normal usable state in the VC data, resulting in the risk that users cannot use them normally and affect user perception.

The above-mentioned current situation of management is decentralized management of recharge card resource management, which has not been unified, which provides opportunities for those who plan to do wrong, and brings great financial risks to operators.

Contents of the invention

The object of the present invention is to provide a method, system and device for recharging a recharge card, avoiding fund loss and complaints caused by data out-of-sync between BOSS and VC, reducing financial risks of operators, and improving user satisfaction.

In order to achieve the above object, according to one aspect of the present invention, a method for recharging a recharge card is provided, including:

Initiate a recharge card status authentication request to the VC of the user to be recharged according to the received recharge request;

Initiate a recharge card validity authentication request to BOSS;

After receiving the first authentication response signaling from the VC and the second authentication response signaling from the BOSS, initiate a recharge request to the BOSS.

In addition, the method further includes: receiving a recharge success message replied by the BOSS, and initiating a recharge card position setting signaling to the VC.

Preferably, the method further includes: if the VC's setting success message is not received within a predetermined time, then the default recharge is successful.

More preferably, the method also includes:

Send the recharge card position setting signaling again, but still do not receive the VC position setting success message within the predetermined time, and record the default recharge success message.

Further, the method also includes:

BOSS stores the recharge card storage file to be stored in the storage device;

The BOSS sends a storage command to the SMP;

The SMP downloads the recharge card storage file to be stored from the storage device according to the storage order;

SMP stores the downloaded recharge card storage file into VC.

Further, the method also includes:

When the BOSS maintains the recharge card information of the local database according to the management operation of the recharge card by the business front desk, it sends a negotiation command to the SMP;

The SMP modifies the recharge card information in the VC according to the negotiation command.

Further, the method further includes: the SMP queues the received batches of MML commands, and correspondingly modifies the recharge card information in the VC according to the queued order.

Further, the method also includes:

SMP uploads the recharge card information and summary verification file of VC changes to the storage device;

The storage device uploads the changed recharge card information and summarizes the verification files to BOSS;

The BOSS compares the recharge card information of the changed VC uploaded by the storage device with the locally changed recharge card information of the BOSS, generates a conflict file, and sends a conflict resolution request command to the SMP according to the conflict file;

The SMP updates the recharge card information of the VC according to the conflict resolution request command.

In order to achieve the above object, according to another aspect of the present invention, a kind of SCP is provided, comprising:

The first authentication module is used to initiate a recharge card status authentication request to the home VC of the user to be recharged according to the received recharge request;

The second authentication module is used to initiate a recharge card validity authentication request to BOSS;

The recharge request generation module is configured to initiate a recharge request to the BOSS after receiving the first authentication response signaling from the VC and the second authentication response signaling from the BOSS.

In addition, the SCP also includes: a position setting request module, which is used to initiate a recharge card position setting signaling to the VC after receiving the recharge success message replied by the BOSS.

Preferably, the SCP also includes: a timing module, which is used to start timing after the position request module initiates the recharge card position signaling to the VC; the recharge state recording module, if it does not receive the setting from the VC within a predetermined time Bit success message, then record the recharge status as the default recharge successful.

Wherein, more preferably, the setting request module sends the recharge card setting signaling again; the recharging state recording module has not received the VC's setting success message within the predetermined time, and records the default recharging success message.

In order to achieve the above purpose, according to another aspect of the present invention, a BOSS is provided, which is characterized in that it includes:

An authentication module, configured to perform authentication according to the received recharge card validity authentication request, and generate a second authentication response message; a sending module, configured to send the generated second authentication response message to the SCP.

Preferably, the BOSS also includes:

A storage order generation module is used to generate a storage order;

The first interface module is configured to transmit the storage command to the SMP.

Preferably, the BOSS also includes: a negotiation command generating module, configured to maintain the recharge card information in the local database according to the management operation of the recharge card by the business front desk, and generate a negotiation command; the first interface module is used to convert the negotiated Commands are transferred to the SMP.

More preferably, the BOSS also includes: a comparison module, which is used to compare the recharge card information of the changed VC uploaded by the storage device with the changed recharge card information of the BOSS itself, and generate a conflict file; the conflict resolution request module uses Generate a conflict resolution request command according to the conflict file and send it to the SMP.

In order to achieve the above object, according to another aspect of the present invention, a kind of SMP is provided, which is characterized in that it includes: a download module, which is used to download the recharge card storage file to be stored from the storage device according to the received storage order; The modification module is configured to modify the recharge card information in the VC according to the received negotiation command.

Preferably, the SMP also includes:

The upload module is used to upload the recharge card information changed by the VC and the summary verification file to the storage device; the modification module is used to modify the recharge card information in the VC according to the conflict file sent by the BOSS.

Preferably, the SMP further includes: a queuing module for queuing the received batches of MML commands; the modifying module for correspondingly modifying the recharge card information in the VC according to the queuing order.

In order to achieve the above purpose, according to another aspect of the present invention, a recharge card recharging system is provided, including:

The SCP, according to the received recharge request, initiates a recharge card status authentication request to the VC of the user to be recharged; initiates a recharge card validity authentication request to the BOSS; receives the first authentication response signaling from the VC and the second authentication response from the BOSS After the authentication response signaling, initiate a recharge request to the BOSS.

The VC is configured to perform authentication according to the received recharge card status authentication request, and generate a first authentication response message and send it to the SCP;

The BOSS is configured to perform authentication according to the received recharge card validity authentication request, and generate a second authentication response message and send it to the SCP.

In the method, system and device for recharging a recharge card of the present invention, during the recharge process, the BOSS and the VC respectively authenticate the validity of the recharge card, and confirm that only normally sold recharge cards can be used, and unsold The recharge card is also unavailable on the VC side, avoiding financial loss and complaints caused by data out-of-sync between BOSS and VC, reducing the operator's financial risk and improving user satisfaction.

Description of drawings

Fig. 1 is a schematic diagram of the management mode of the recharge card in the prior art of the present invention;

Fig. 2 is another schematic diagram of the charging management method in the prior art of the present invention;

Fig. 3 is a flow chart of Embodiment 1 of the method for recharging a recharge card of the present invention;

Fig. 4 is a flow chart of Embodiment 2 of the method for recharging a recharge card of the present invention;

Fig. 5 is a flow chart of Embodiment 3 of the method for recharging a recharge card of the present invention;

Fig. 6 is a structural diagram of an SCP embodiment of the present invention;

Fig. 7 is a structural diagram of a BOSS embodiment of the present invention;

Fig. 8 is a structural diagram of an SMP embodiment of the present invention;

Fig. 9 is a structural diagram of an embodiment of the recharge card recharging system of the present invention.

Detailed ways

In order to solve the risk of operator fund loss caused by the malicious use of recharge cards that have not been sold in the prior art, as well as the complaints caused by the inability of the system to accurately identify users when recharging, the present invention controls the recharge card during the recharge process. Validity is double-authenticated to confirm that only normally sold recharge cards can be used, and unsold recharge cards are also unavailable on the VC side. The present invention will be described in detail below in conjunction with the accompanying drawings.

Method embodiment one

As shown in Figure 3, the recharge card recharge method embodiment of the present invention comprises the following steps:

Step 101, user A dials a voice access code to initiate a recharge process for user B; the service switching point (Service Switching Point, referred to as SSP) triggers the recharge service, and sends the mobile phone number to be recharged and the recharge card password to the call access SCP;

Step 102, call access to the SCP for business processing, collect relevant information including recharge card password, calling number and mobile phone number to be recharged, and submit a recharge request, including recharge card password, calling number, recharged number, etc. to the user to be recharged Belonging to SCP;

Step 103, according to the received recharge request, the SCP of the user to be recharged initiates a recharge card status authentication request to the recharge VC, and the recharge card status authentication request includes information such as the recharge card password, calling number, and mobile phone number to be recharged ;

Step 104, the recharged attributable VC completes the authentication and replies to the first authentication response signaling, the first authentication response signaling includes information such as the recharge card amount, validity period, and valid identification;

Step 105, the SCP of the user to be recharged receives the first authentication response signaling, and the authentication passes, and initiates a recharge card validity authentication request to the BOSS. The recharge card validity authentication request includes: recharge card serial number, recharge Card password and mobile phone number to be recharged;

Step 106, the home SCP of the user to be recharged receives the second authentication response signaling from the BOSS, and the authentication passes;

Step 107, the SCP of the user to be recharged initiates a recharge request to the BOSS;

Step 108, BOSS receives the recharge request, confirms that the customer can recharge, completes the recharge operation, credits the funds, and replies with a successful recharge message;

Step 109, the SCP of the user to be recharged receives a message of successful recharge from the BOSS, and initiates a recharge card position signaling to the VC;

Step 110, the VC receives the position setting signaling, and the user to be recharged returns a position setting success message to the SCP;

Step 111, the SCP of the user to be recharged sends the recharge operation result to the call access SCP,

In this embodiment, both VC and BOSS authenticate the validity of the recharge card to confirm that only recharge cards that are normally sold can be used, and unsold recharge cards are also in an unavailable state on the VC side, reducing the operator's financial risk and improve user satisfaction.

In addition, in order to avoid the problem of multiple charging of one card when the signaling response times out, this embodiment further includes the following steps:

Step 112, if the SCP does not receive the VC's successful setting message within the predetermined time, the recharge is successful by default;

Step 113, the SCP sends the recharge card position signaling again, the number of times of sending can be configured, for example, less than or equal to 3 times, if the number of repeated sending is too many, it will affect the system performance;

In step 114, the SCP has not received the VC's location success message within the predetermined time, and records the default recharge success information, including the recharge card serial number, recharge time, recharged number, originating recharge number, recharge method, etc.

SMP maintains the default recharge success script, starts the script task regularly, exports the recharge card information in the current time period in the SCP default recharge success record table, backs it up to a file and updates the corresponding recharge card information in the VC database.

Through the multiple sending of setting signaling and the timing update task mechanism, the used recharge card is prevented from being used again. In addition, multiple sending is placed after the default recharge occurs successfully, so as to improve user perception and reduce system resource occupation.

Method embodiment two

Preferably, in order to realize the unified management of the recharge card information of the BOSS database and the VC database, an interface is added between the BOSS and the SMP, and the synchronization of the two databases is maintained from the generation, sale, activation, and return of the recharge card to ensure that only normal The recharge card sold is only available in VC and can be used. As shown in Figure 4, the specific operation process is as follows:

Step 201, BOSS processes the storage file, stores the recharge card information in its own database, and stores the recharge card storage file to be stored in the storage device;

Step 202, the BOSS submits the MML command of "start storing" to the SMP;

Step 203, the SMP downloads new files to be stored from the storage device via FTP;

Step 204, SMP feeds back the warehousing task number to BOSS;

In step 205, the SMP checks the files in storage. If the check fails, the entire batch fails to respond and is not processed; after the check is passed, the storage operation is performed, that is, step 206 is executed;

Step 206, SMP stores the obtained recharge card storage files into VC piece by piece; for operations such as batch issuance, adding and unlocking, if the number of recharge cards to be operated is large, or the operation is intensive, it will have an impact on VC, and even Affects calling tasks, so for bulk operations, SMP queues all tasks and processes them sequentially;

Step 207, the SMP is put into storage segment by segment until the storage is completed;

Step 208, during the process of SMP storage step by step, BOSS can send a task query command to SMP to query the progress of storage;

Step 209, the SMP responds to the task progress to the BOSS;

Step 210, after the SMP warehousing is completed, send the recharge card warehousing result file to the storage device for query and acquisition by BOSS;

Step 211, after the SMP storage is completed, the BOSS sends a task query command to the SMP;

Step 212, SMP responds to task processing results and possible error messages;

Step 213, when the business front desk involves management operations on the recharge card, including sales, adding and unlocking, and returning cards, the BOSS sends a negotiation command to the SMP while maintaining the recharge card information in the local database;

In step 214, the SMP performs operations such as issuing, unlocking, and de-issuing the recharge card of the VC according to the received negotiation command.

In this embodiment, on the basis of the method embodiment 1, the interface between BOSS and SMP is further increased to realize the unified management of recharge card information in the BOSS database and VC database, from the generation, sale, activation and refund of recharge cards The link maintains the synchronization of the two databases to ensure that only normally sold recharge cards are available in VC and can be used to avoid unsold recharge cards flowing into users due to misselling of recharge cards or poor channel management. In the hands, when the user dials the service access code for use, the system cannot accurately identify the financial loss and complaints caused. Reduce user loss and improve user satisfaction.

Method embodiment three

More preferably, a synchronization mechanism between BOSS and VC is further added to ensure a one-to-one correspondence between sales information and usage information of the two databases. As shown in Figure 5, this embodiment includes the following steps:

Step 301, the SMP screens the changed recharge card information in the VC every morning at leisure, generates the recharge card data files changed the previous day, and summarizes the verification files;

Steps 302 and 303, storing the information of the recharge card with changed VC and summarizing verification files to the storage device;

Step 304, BOSS initiates a consistency management request file;

Step 305, the storage device checks the request data;

Step 306, the storage device returns the consistency management answer file;

Steps 307 and 308, the storage device uploads the recharge card information and the summary verification file of the changed VC to the BOSS;

Step 309, BOSS compares the recharge card information changed by VC with the recharge card information changed by BOSS locally, and obtains the conflict file;

Step 310, BOSS uploads the conflict file to the storage device;

Step 311, the BOSS generates a conflict resolution request command and sends it to the SMP;

Step 312, the storage device sends the conflicting file to the SMP;

Step 313, the SMP returns a conflict resolution response command to the BOSS;

Step 314, SMP synchronizes the recharge card information in the VC segment by segment according to the received conflict file;

Step 315, the synchronization is completed;

Step 316, the SMP generates a conflict resolution result file and sends it to the storage device;

Step 317, the storage device uploads the conflict resolution result file to the BOSS.

In this embodiment, the unified management of recharge card information between the BOSS database and the VC database is further realized through the conflict file checking mechanism, and the synchronization of the two databases is maintained from the generation, sale, activation, and return of the recharge card to ensure that only normal sales The prepaid recharge card can be used only when it is available in the VC, so as to avoid unsold recharge cards flowing into the hands of users due to misselling of recharge cards or poor channel management. When users dial the service access code for use, the system It is impossible to accurately identify the cause of financial loss and complaints. Reduce user loss and improve user satisfaction.

Based on the same inventive concept, the embodiment of the present invention also provides SCP, SMP, BOSS, VC and recharge card recharge system, which will be described one by one below.

As shown in Figure 6, the SCP embodiment of the present invention may include:

The first authentication module 41 is used to initiate a recharge card status authentication request to the home VC of the user to be recharged according to the received recharge request;

The second authentication module 42 is used to initiate a recharge card validity authentication request to BOSS;

The recharge request generation module 43 is configured to initiate a recharge request to the BOSS after receiving the first authentication response signaling from the VC and the second authentication response signaling from the BOSS.

The SCP in this embodiment, by initiating authentication and authentication of the validity of the recharge card to both VC and BOSS, confirms that only normally sold recharge cards can be used, and unsold recharge cards are also unavailable on the VC side , reduce the operator's financial risk and improve user satisfaction.

In addition, the SCP also includes: a position setting request module 44, configured to initiate a recharge card position setting signaling to the VC after receiving the recharge success message replied by the BOSS.

Preferably, the SCP also includes: a timing module 45, which is used to start timing after the setting request module initiates the recharge card setting signaling to the VC; the recharge state recording module 46, if the VC does not receive a message within a predetermined time If the success message is set, the recharge status is recorded as the default recharge success.

More preferably, the SCP also includes: a set request module 44, which sends the recharge card set signaling again; a recharge status recording module 46, which has not received the VC's set success message within the predetermined time, and records the default recharge success message.

The SCP of this embodiment prevents the used recharge card from being used again by setting the multiple sending mechanism of the signaling. In addition, multiple sending is placed after the default recharge occurs successfully, so as to improve user perception and reduce system resource occupation.

As shown in Figure 7, the BOSS embodiment of the present invention may include:

An authentication module 51, an authentication module, configured to perform authentication according to the received recharge card validity authentication request, and generate a second authentication response message;

The sending module 52 is configured to send the generated second authentication response message to the SCP.

In the BOSS of this embodiment, by increasing the interface between the BOSS and the SCP, the BOSS also authenticates the validity of the recharge card, confirming that only normally sold recharge cards can be used, and the unsold recharge cards are on the VC side It is also in an unavailable state, which reduces the operator's financial risk and improves user satisfaction.

In addition, the BOSS embodiment further includes: a storage order generating module 53, configured to generate a storage order; a first interface module 54, configured to transmit the storage order to the SMP.

Preferably, the BOSS embodiment also includes: a negotiation command generation module 55, which is used to maintain the recharge card information of the local database according to the management operation of the recharge card by the business front desk, and generates a negotiation command; the first interface module 54 is used to convert the Negotiation commands are transmitted to the SMP.

The BOSS of this embodiment, by further increasing the interface between BOSS and SMP, realizes the unified management of the recharge card information of the BOSS database and the VC database, and maintains the synchronization of the two databases from the generation, sales, activation, and return of the recharge card. , to ensure that only normally sold recharge cards are available in VC and can be used to avoid unsold recharge cards flowing into the hands of users due to misselling of recharge cards or poor channel management, and users dial service access When the code is used, the system cannot accurately identify the problem of fund loss and complaints. Reduce user loss and improve user satisfaction.

More preferably, the BOSS of this embodiment also includes: a comparison module 56, which is used to compare the recharge card information of the VC uploaded by the storage device with the recharge card information of the BOSS local change, and generate a conflict file; conflict resolution request Module 57, configured to generate a conflict resolution request command according to the conflict file and send it to the SMP. Through the BOSS conflict file inspection mechanism, the unified management of the recharge card information between the BOSS database and the VC database is further realized, and the synchronization of the two databases is maintained from the generation, sales, activation, and return of the recharge card to ensure that only normally sold recharges Only when the card is available in VC can it be used, so as to avoid unsold recharge cards flowing into the hands of users due to misselling of recharge cards or poor channel management, and the system cannot accurately identify when users dial the service access code for use Cause financial loss and complaints. Reduce user loss and improve user satisfaction.

As shown in Figure 8, the SMP embodiment of the present invention may include:

The download module 61 is used to download the recharge card storage file to be stored from the storage device according to the received storage order; the modification module 62 is used to respond to the recharge card information in the VC according to the received negotiation command. Modifications.

The SMP of this embodiment, by further increasing the interface between BOSS and SMP, realizes the unified management of the recharge card information of the BOSS database and the VC database, and keeps the synchronization of the two databases from the generation, sales, activation, and return of the recharge card. , to ensure that only normally sold recharge cards are available in VC and can be used to avoid unsold recharge cards flowing into the hands of users due to misselling of recharge cards or poor channel management, and users dial service access When the code is used, the system cannot accurately identify the problem of fund loss and complaints. Reduce user loss and improve user satisfaction.

The SMP embodiment also includes: an upload module 63 for uploading the recharge card information changed by the VC and summarizing verification files to the storage device; a modification module 62 for modifying the recharge card information in the VC based on the conflict file sent by the BOSS. Through the interface between SMP and BOSS, data consistency comparison can be carried out, which strengthens the data synchronization between BOSS and VC, and ensures that the recharge card information is consistent.

The SMP embodiment also includes: a queuing module 64 for queuing the received batches of MML commands; a modification module 62 for modifying the recharge card information in the VC according to the queuing sequence.

For operations such as batch issuance, adding and unlocking, if the number of recharge cards to be operated is large, or the operation is intensive, it will have an impact on VC and even affect call tasks. Therefore, for batch operations, SMP will adopt the mode of queuing and sequential processing.

As shown in Figure 9, the recharge card recharge system of the present invention may include:

SCP, according to the received recharge request, initiates a recharge card status authentication request to the VC of the user to be recharged; initiates a recharge card validity authentication request to the BOSS; receives the first authentication response signaling from the VC and the second authentication response from the BOSS After the authentication response signaling, initiate a recharge request to the BOSS.

The VC is configured to perform authentication according to the received recharge card status authentication request, and generate a first authentication response message and send it to the SCP;

The BOSS is configured to perform authentication according to the received recharge card validity authentication request, and generate a second authentication response message and send it to the SCP.

In this embodiment, both VC and BOSS authenticate the validity of the recharge card to confirm that only recharge cards that are normally sold can be used, and unsold recharge cards are also in an unavailable state on the VC side, reducing the operator's financial risk and improve user satisfaction.

Preferably, the system also includes: a storage device and an SMP, the storage device is used to store the recharge card storage file to be stored; BOSS is used to generate a storage order and send it to the SMP; The library command downloads the recharge card storage file to be stored from the storage device, and stores the downloaded recharge card storage file into the VC.

In this embodiment, by further increasing the interface between BOSS and SMP, the unified management of the recharge card information between the BOSS database and the VC database is realized, and the synchronization of the two databases is maintained from the generation, sale, activation, and return of the recharge card to ensure that only Normally sold recharge cards are only available in VC and can be used to avoid unsold recharge cards flowing into the hands of users due to misselling of recharge cards or poor channel management, and users dial the service access code to use Sometimes the system cannot accurately identify the cause of financial loss and complaints. Reduce user loss and improve user satisfaction.

More preferably, in this embodiment, a conflict detection mechanism is added on the BOSS side, that is, the BOSS compares the recharge card information of the VC stored in the storage device with the recharge card information of the BOSS local change, generates a conflict file, and then A conflict resolution request command is generated according to the conflict file and sent to the SMP, and the SMP updates the recharge card information in the VC according to the conflict resolution request.

Further realize the unified management of the recharge card information of the BOSS database and the VC database, and keep the synchronization of the two databases. Avoid unsold recharge cards flowing into the hands of users due to misselling of recharge cards or poor channel management. When users dial the service access code for use, the system cannot accurately identify fund losses and complaints. Reduce user loss and improve user satisfaction.

It should be noted that: the above embodiments are only used to illustrate the present invention without limitation, and the present invention is not limited to the above-mentioned examples, and all technical solutions and improvements thereof that do not depart from the spirit and scope of the present invention should be included in the present invention. within the scope of the claims.

Claims (9)

1. a rechargeable card method, is characterized in that, comprising:

Business control nodes initiates rechargeable card state authentication request according to the charging request received to the voucher center of user to be supplemented with money;

Business control nodes initiates rechargeable card validity authentication request to business support system;

After business control nodes receives the first Authentication Response signaling of described voucher center and the second Authentication Response signaling of described business support system, initiate charging request to described business support system;

Be there is the rechargeable card information that changes and gathers verification file to upload to storage device by service management node in described voucher center;

Storage device upload described voucher center occur change rechargeable card information, gather verification file to described business support system;

Storage device is uploaded the local rechargeable card information occurring to change of rechargeable card information and described business support system that described voucher center occurs to change and is compared by described business support system, generate conflict file, and send Conflict solving request command according to described conflict file to service management node;

Described service management node upgrades the rechargeable card information of described voucher center according to described Conflict solving request command.

2. rechargeable card method according to claim 1, is characterized in that, also comprise:

Business control nodes receives the successful recharging message that described business support system is replied, and initiates setting rechargeable card signaling to described voucher center.

3. rechargeable card method according to claim 2, is characterized in that, also comprise:

Business control nodes does not receive the set success message of described voucher center within the predetermined time, then give tacit consent to successful recharging.

4. rechargeable card method according to claim 3, is characterized in that, also comprise:

Business control nodes sends setting rechargeable card signaling again, receives the set success message of described voucher center not yet within the predetermined time, records this acquiescence successful recharging information.

5., according to the arbitrary described rechargeable card method of claim 1-4, it is characterized in that, also comprise:

Rechargeable card to be put in storage is entered library file and is stored into storage device by described business support system;

Described business support system transmits into library command to described service management node;

Described service management node according to described in enter library command and download rechargeable card to be put in storage from described storage device and enter library file;

Described service management node puts the rechargeable card downloaded in storage file warehousing to described voucher center.

6. rechargeable card method according to claim 1, is characterized in that, also comprise:

Described business support system to carry out the rechargeable card maintenance of information of local data base according to business foreground during to the bookkeeping of rechargeable card, send to described service management node and consult order;

Described service management node is revised the rechargeable card information in described voucher center accordingly according to described negotiation order.

7. rechargeable card method according to claim 5, it is characterized in that, also comprise: described service management node is ranked for the MML order of the batch received, according to Queue sequence, the rechargeable card information in described voucher center is revised accordingly.

8. a rechargeable card system, is characterized in that, comprising: business control nodes, voucher center, business support system, service management node and storage device;

Described business control nodes, initiates rechargeable card state authentication request according to the charging request received to the ownership voucher center of user to be supplemented with money; Rechargeable card validity authentication request is initiated to business support system; After receiving the first Authentication Response signaling of described voucher center and the second Authentication Response signaling of described business support system, initiate charging request to described business support system;

Described voucher center, for carrying out authentication according to the rechargeable card state authentication request that receives, and generates the first authentication response message and sends to business control nodes;

Described business support system, for carrying out authentication according to the described rechargeable card validity authentication request that receives, and generates the second authentication response message and sends to described business control nodes;

Described service management node, for the rechargeable card information that described voucher center occurred to change and gather verification file and upload to described storage device, and upgrades the rechargeable card information of described voucher center according to Conflict solving request command;

, there is the rechargeable card information of change for uploading described voucher center, gathering verification file to described business support system in described storage device;

Described business support system, the rechargeable card information that the rechargeable card information changed for the described voucher center generation of being uploaded by storage device and described business support system this locality occur to change is compared, generate conflict file, and send Conflict solving request command according to described conflict file to described service management node.

9. rechargeable card system according to claim 8, is characterized in that,

Described business support system, is stored into storage device for rechargeable card to be put in storage is entered library file, and transmits into library command to described service management node;

Described service management node, downloads rechargeable card to be put in storage from described storage device enter library file for entering library command described in basis, and by the rechargeable card warehouse-in file warehousing downloaded to described voucher center.