WO2017166068A1 - 充值系统 - Google Patents

充值系统 Download PDF

Info

Publication number
WO2017166068A1
WO2017166068A1 PCT/CN2016/077705 CN2016077705W WO2017166068A1 WO 2017166068 A1 WO2017166068 A1 WO 2017166068A1 CN 2016077705 W CN2016077705 W CN 2016077705W WO 2017166068 A1 WO2017166068 A1 WO 2017166068A1
Authority
WO
WIPO (PCT)
Prior art keywords
key
terminal
request
background server
recharge
Prior art date
Application number
PCT/CN2016/077705
Other languages
English (en)
French (fr)
Inventor
李昕光
Original Assignee
李昕光
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 李昕光 filed Critical 李昕光
Priority to PCT/CN2016/077705 priority Critical patent/WO2017166068A1/zh
Publication of WO2017166068A1 publication Critical patent/WO2017166068A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07F—COIN-FREED OR LIKE APPARATUS
    • G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means

Definitions

  • the present invention relates to the field of data processing, and in particular, to a recharge system.
  • the recharge system is an important part of the card trading system.
  • the recharge system is the first step in the normal operation of the card trading system.
  • the card transaction system refers to an IC (Integrated Circuit Card) card, PBOC (The People's Bank of China) card, PSAM (Purchase Secure Access Module) card or electronic A system in which a smart card such as a wallet is used for trading.
  • IC Integrated Circuit Card
  • PBOC People's Bank of China
  • PSAM Purchase Secure Access Module
  • the current recharge system can recharge smart cards through offline recharge, online recharge, and self-service cash terminals.
  • the inventors have found that at least the following problems exist in the prior art: the current recharge system usually only performs one-step key verification, and the security is poor.
  • the embodiment of the present invention provides a recharge system.
  • the technical solution is as follows:
  • a refill system comprising: a terminal, a background server, and a key server;
  • the terminal is configured to send a refill request to the background server, where the refill request carries user data;
  • the background server is configured to verify user data carried in the refill request, and send a key acquisition request to the key server when the verification is successful;
  • the key server is configured to receive the key acquisition request, generate a key according to the key acquisition request, and feed back the key to the background server;
  • the background server is configured to generate a request success response carrying the key, and send the request success response to the terminal;
  • the terminal is configured to extract the key from the request success response, perform a card write operation on the smart card according to the key, and send a confirmation request message to the background server after the card is successfully written, Confirm that the request message carries a verification verification code;
  • the background server is configured to verify the verification verification code carried in the confirmation request message, and send a confirmation success message to the terminal when the verification is successful;
  • the terminal is configured to receive the acknowledged success message and record the refill success information
  • the terminal is configured to receive a third-party recharge operation of the user, and send the recharge request to the background server according to the third-party recharge operation;
  • the background server is further configured to forward the refill request to a third-party system when the verification succeeds, and send the key acquisition request to the key server after receiving the successful recharge response of the third-party system.
  • the terminal is configured to receive an offline refill operation of the user, and send the refill request to the background server according to the offline recharge operation.
  • the terminal is configured to receive a user recharge operation, and send the refill request to the background server according to the recharge refill operation.
  • the terminal is a terminal that supports a short-range communication technology (NFC);
  • NFC short-range communication technology
  • the terminal is configured to pay a refill amount through a built-in application, and send the refill request to the background server after successfully repaying the recharge amount;
  • the terminal is further configured to perform a card writing operation on the smart card by using the NFC technology according to the key.
  • a charging method comprising:
  • the terminal sends a refill request to the background server, where the refill request carries user data;
  • the background server verifies the user data carried in the refill request, and sends a key acquisition request to the key server when the verification is successful;
  • the background server generates a request success response carrying the key, and sends the request success response to the terminal;
  • the terminal extracts the key from the request success response, performs a card write operation on the smart card according to the key, and sends an acknowledgement request message to the background server after the card is successfully written, the confirmation request report
  • the document carries a verification verification code
  • the background server verifies the verification verification code carried in the confirmation request message, and sends a confirmation success message to the terminal when the verification succeeds;
  • the terminal receives the confirmation success message and records the refill success information.
  • the terminal sends a recharge request to the background server, including:
  • the terminal receives an offline recharge operation of the user, and sends the refill request to the background server according to the offline recharge operation.
  • the terminal sends a recharge request to the background server, including:
  • the terminal receives a user's recharge and refill operation, and sends the refill request to the background server according to the recharge refill operation.
  • the terminal sends a recharge request to the background server, including:
  • the background server is further configured to forward the refill request to a third-party system when the verification succeeds, and send the key acquisition request to the key server after receiving the successful recharge response of the third-party system.
  • the terminal sends a recharge request to the background server, including:
  • the terminal When the terminal is a terminal that supports the NFC of the short-range communication technology, the terminal pays the recharge amount through the built-in application, and sends the refill request to the background server after successfully repaying the recharge amount;
  • the terminal performs a card writing operation on the card according to the key, including:
  • the terminal performs a card writing operation on the smart card by using the NFC technology according to the key.
  • the online processing is performed by any recharge method, and the replenishment request and the confirmation request message are verified by the background server, and the terminal writes the card according to the key issued by the key server; the current recharge system security is solved. Poor problem; every time the recharge process is reached, a multi-step verification is performed to ensure the safety of the recharge process.
  • FIG. 1 is a schematic structural view of an implementation environment involved in various embodiments of the present invention.
  • FIG. 2 is a flowchart of a method for charging a method according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for charging a method according to another embodiment of the present invention.
  • FIG. 4 is a flowchart of a method for charging a method according to still another embodiment of the present invention.
  • FIG. 5 is a flowchart of a method for charging a method according to still another embodiment of the present invention.
  • FIG. 6 is a flowchart of a method for charging a method according to still another embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a recharge system according to another embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of a server according to another embodiment of the present invention.
  • FIG. 1 is a schematic structural diagram of an implementation environment involved in various embodiments of the present invention.
  • the implementation environment includes a terminal 120, a backend server 140, and a key server 160.
  • the terminal 120 and the background server 140 are connected by a wired network or a wireless network; the background server 140 and the key server 160 are connected by a wired network or a wireless network.
  • the terminal 120 is an electronic device having smart card reading and writing capabilities.
  • Terminal 120 can be a cell phone, a laptop portable computer, a desktop computer, and the like.
  • the terminal 120 can be supporting NFC (Near Field) Communication, short-range wireless communication technology) mobile terminal has the ability to read and write external smart cards in a non-contact reading manner.
  • the smart card includes an IC card, a PBOC card, a PSAM card, an electronic wallet, an NFC card, and an iBeacon produced by Apple Inc. of the United States.
  • the backend server 140 can be a server, or a server cluster consisting of several servers, or a cloud computing service center.
  • the key server 160 can be a server, or a server cluster consisting of several servers, or a cloud computing service center.
  • FIG. 2 shows a flowchart of a method for recharging according to an embodiment of the present invention.
  • This embodiment is exemplified by applying the recharging method to the implementation environment shown in FIG. 1.
  • the recharging method may include:
  • Step 201 The terminal sends a refill request to the background server, where the refill request carries user data.
  • Step 202 The background server verifies the user data carried in the refill request.
  • Step 203 The background server sends a key acquisition request to the key server when the verification is successful.
  • Step 204 The key server receives a key acquisition request, and generates a key according to the key acquisition request.
  • Step 205 The key server feeds back the key to the background server.
  • Step 206 The background server generates a request success response carrying the key, and sends a request success response to the terminal.
  • Step 207 The terminal extracts a key from the request success response, and performs a card write operation on the smart card according to the key;
  • Step 208 After the card is successfully written, the terminal sends a confirmation request message to the background server, where the confirmation request message carries a verification verification code.
  • Step 209 The background server verifies the verification verification code carried in the confirmation request message, and sends a confirmation success message to the terminal when the verification succeeds;
  • Step 210 The terminal receives the confirmation success message and records the refill success information.
  • the recharging method provided in this embodiment adopts online processing by any recharge method, and the background server verifies the refill request and the confirmation request message, and the key issued by the terminal according to the key server.
  • Write the card solve the problem of poor safety of the current recharge system; achieve a multi-step verification for each recharge process to ensure the safety of the recharge process.
  • the terminal sends a recharge request to the background server during the process of recharging the smart card, it can be divided into the following different ways:
  • FIG. 3 shows a flowchart of a method for recharging according to an embodiment of the present invention.
  • This embodiment is exemplified by applying the recharging method to the implementation environment shown in FIG. 1.
  • the method can include:
  • Step 301 The terminal receives an offline recharge operation of the user, and sends a refill request to the background server according to the offline recharge operation;
  • the offline recharge operation may be an operation in which the user puts the recharged cash into the self-service cash refill terminal;
  • the offline recharge operation may be an operation in which the user transfers the funds of the bank card account to the account corresponding to the recharge system.
  • the terminal After the user performs the offline recharge operation successfully, that is, after the funds are transferred to the recharge system, the terminal sends a refill request to the background server.
  • the refill request usually carries user data and recharge data, and the user data includes but is not limited to basic data, user identity data, smart card data, and the like.
  • the recharge data usually includes the recharge amount and may also include recharge rules.
  • the background server receives the refill request sent by the terminal.
  • Step 302 The background server verifies the user data carried in the refill request.
  • the background server After receiving the refill request, the background server extracts the user data carried in the refill request. The user profile is then verified.
  • the background server verifies the underlying data to verify that the underlying data is correct.
  • the background server authenticates the user identity and verifies the User identity is correct.
  • the user identity can be the identity of the cardholder or the identity of the user of the terminal.
  • the background server verifies the smart card data.
  • the smart card data may include a card type parameter of the smart card, a smart card identifier, and the like.
  • This step can ensure that the terminal and the smart card are terminals and smart cards recognized by the recharge system, not illegally accessed terminals, or forged cards or blacklist cards.
  • Step 303 The background server sends a key acquisition request to the key server when the verification is successful.
  • the background server sends a key acquisition request to the key server. Because the keys corresponding to different smart cards are different, the background server sends a key acquisition request for acquiring a key corresponding to the smart card currently to be recharged to the key server. This key is a recharge key.
  • Step 304 The key server receives a key acquisition request, and generates a key according to the key acquisition request.
  • the key server receives the key acquisition request, and generates a key corresponding to the smart card according to the key acquisition request.
  • the encryption machine in the key server may calculate a recharge key corresponding to the smart card by using a decentralized algorithm.
  • Step 305 The key server feeds back the key to the background server.
  • the key server feeds back the key corresponding to the smart card to the background server.
  • Step 306 The background server generates a request success response carrying the key, and sends a request success response to the terminal.
  • the terminal receives the request and successfully responds.
  • Step 307 The terminal extracts a key from the request success response, and performs a card write operation on the smart card according to the key;
  • the terminal extracts the corresponding key from the request success response, and performs a card writing operation on the smart card according to the key.
  • the smart card allows the card to be operated by the terminal;
  • the smart card does not allow the card to be written by the terminal.
  • Step 308 After the card is successfully written, the terminal sends a confirmation request message to the background server, where the confirmation request message carries a verification verification code;
  • the confirmation request message carries a verification verification code, and the verification verification code can be generated according to the data of the current card writing operation process.
  • Step 309 The background server verifies the verification verification code carried in the confirmation request message, and sends a confirmation success message to the terminal when the verification is successful.
  • the background server verifies the sensitive information such as the verification verification code carried in the confirmation request message. Because the verification verification code is generated according to the data of the current card writing operation process of the terminal, the background server compares the current card writing operation indicated in the recharging request with the actual card writing operation of the terminal, and if they are the same, The verification is considered successful, and if it is not the same, the verification is considered unsuccessful. This step can ensure that the recharge data of the recharge process is not tampered with.
  • the background server sends a confirmation success message to the terminal.
  • Step 310 The terminal receives the confirmation success message and records the refill success information.
  • the terminal After receiving the confirmation message of the system, the terminal records the transaction success information.
  • the terminal may also perform statistics on the transaction success information in the batch every predetermined batch, obtain statistical information and upload the information to the background server.
  • the recharging method provided in this embodiment is to use the online processing method to verify the refill request and the acknowledgment request message by the background server and the secret issued by the terminal according to the key server.
  • the key is written to the card; the problem of poor security of the current recharge system is solved; and each time the recharge process is performed, multi-step verification is performed to ensure the safety of the recharge process.
  • FIG. 4 is a flowchart of a method for charging a method according to another embodiment of the present invention. This embodiment is exemplified by applying the recharging method to the implementation environment shown in FIG. 1.
  • the method can include:
  • Step 401 The terminal receives the user's recharge and recharge operation, and sends a refill request to the background server according to the recharge and recharge operation;
  • the terminal receives the user's recharge operation, and sends a refill request to the background server according to the recharge operation.
  • the recharge operation refers to an operation in which the user deposits the funds in the A account into the B account corresponding to the smart card.
  • the B account corresponding to the smart card is usually bound to the A account.
  • the terminal After receiving the user's recharge operation, the terminal sends a refill request to the background server according to the amount of the recharge. This refill request usually carries user data.
  • the background server receives the refill request sent by the terminal.
  • Step 402 The background server verifies the user data carried in the refill request.
  • the background server After receiving the refill request, the background server extracts the user data carried in the refill request. The user profile is then verified.
  • the background server verifies the underlying data to verify that the underlying data is correct.
  • the background server authenticates the user's identity and verifies that the user's identity is correct.
  • the user identity can be the identity of the cardholder or the identity of the user of the terminal.
  • the background server verifies the smart card data.
  • the smart card data may include a card type parameter of the smart card, a smart card identifier, and the like.
  • the terminal and the smart card are both terminals and smart cards recognized by the background server, not illegally accessed terminals, or forged cards or blacklist cards.
  • Step 403 The background server sends a key acquisition request to the key server when the verification succeeds;
  • the background server sends a key acquisition request to the key server. Because the keys corresponding to different smart cards are different, the background server sends a key acquisition request for acquiring a key corresponding to the smart card currently to be recharged to the key server. This key is a recharge key.
  • Step 404 The key server receives the key acquisition request, and generates a key according to the key acquisition request.
  • the key server receives the key acquisition request, and generates a key corresponding to the smart card according to the key acquisition request.
  • the encryption machine in the key server may calculate a recharge key corresponding to the smart card by using a decentralized algorithm.
  • Step 405 The key server feeds back the key to the background server.
  • the key server feeds back the key corresponding to the smart card to the background server.
  • Step 406 The background server generates a request success response carrying the key, and sends a request success response to the terminal.
  • the terminal receives the request and successfully responds.
  • Step 407 The terminal extracts a key from the request success response, and performs a card write operation on the smart card according to the key;
  • the terminal extracts the corresponding key from the request success response, and performs a card writing operation on the smart card according to the key.
  • the smart card allows the card to be operated by the terminal;
  • the smart card does not allow the card to be written by the terminal. Work.
  • Step 408 After the card is successfully written, the terminal sends a confirmation request message to the background server, where the confirmation request message carries a verification verification code.
  • the confirmation request message carries a verification verification code, and the verification verification code can be generated according to the data of the current card writing operation process.
  • Step 409 The background server verifies the verification verification code carried in the confirmation request message, and sends a confirmation success message to the terminal when the verification succeeds;
  • the background server verifies the sensitive information such as the verification verification code carried in the confirmation request message. Because the verification verification code is generated according to the data of the current card writing operation process of the terminal, the background server compares the current card writing operation indicated in the recharging request with the actual card writing operation of the terminal, and if they are the same, The verification is considered successful, and if it is not the same, the verification is considered unsuccessful. This step can ensure that the recharge data of the recharge process is not tampered with.
  • the background server sends a confirmation success message to the terminal.
  • Step 410 The terminal receives the confirmation success message and records the refill success information.
  • the terminal After receiving the confirmation message of the system, the terminal records the transaction success information.
  • the terminal may also perform statistics on the transaction success information in the batch every predetermined batch, obtain statistical information and upload the information to the background server.
  • the recharging method provided in this embodiment is used to verify the refill request and the acknowledgment request message by the background server and to be issued by the terminal according to the key server.
  • the key is used to write the card; the problem of poor security of the current recharge system is solved; and each time the recharge process is performed, multi-step verification is performed to ensure the safety of the recharge process.
  • FIG. 5 is a flowchart of a method for charging a method according to another embodiment of the present invention. This embodiment is exemplified by applying the recharging method to the implementation environment shown in FIG. 1.
  • the method can include:
  • Step 501 The terminal receives a third-party recharge operation of the user, and sends a refill request to the background server according to the third-party recharge operation;
  • Third-party systems usually refer to trading systems other than the smart card system such as electricity, gas, water conservancy, social security, provident fund, and payment platform.
  • the third party system is pre-accessed to the backend server shown in FIG.
  • the terminal receives the third-party recharge operation of the user, and sends a recharge request to the background server according to the third-party recharge operation.
  • the refill request may carry a third party system identification, recharge amount, user data, and the like.
  • the background server receives the refill request sent by the terminal.
  • Step 502 The background server verifies the user data carried in the refill request.
  • the background server After receiving the refill request, the background server extracts the user data carried in the refill request. The user profile is then verified.
  • the background server verifies the underlying data to verify that the underlying data is correct.
  • the background server authenticates the user's identity and verifies that the user's identity is correct.
  • the user identity can be the identity of the cardholder or the identity of the user of the terminal.
  • the background server verifies the smart card data.
  • the smart card data may include a card type parameter of the smart card, a smart card identifier, and the like.
  • the terminal and the smart card are both terminals and smart cards recognized by the background server, not illegally accessed terminals, or forged cards or blacklist cards.
  • Step 503 The background server forwards the refill request to the third-party system when the verification succeeds;
  • the background server forwards the refill request to the third-party system when the verification is successful.
  • the replenishment request carries the third-party system identifier and the recharge amount
  • the background server sends the recharge request carrying the recharge amount to the third-party system according to the third-party system identifier, so that the third-party system performs recharge, and after the recharge is successful, , feedback the successful recharge response to the background server.
  • Step 504 After receiving the successful recharge response of the third-party system, the background server sends a key acquisition request to the key server.
  • the background server sends a key acquisition request to the key server. Because the keys corresponding to different smart cards are different, the background server sends a key acquisition request for acquiring a key corresponding to the smart card currently to be recharged to the key server. This key is a recharge key.
  • Step 505 The key server receives the key acquisition request, and generates a key according to the key acquisition request.
  • the key server receives the key acquisition request, and generates a key corresponding to the smart card according to the key acquisition request.
  • the encryption machine in the key server may calculate a recharge key corresponding to the smart card by using a decentralized algorithm.
  • Step 506 the key server feeds back the key to the background server
  • the key server feeds back the key corresponding to the smart card to the background server.
  • Step 507 The background server generates a request success response carrying the key, and sends a request success response to the terminal.
  • the terminal receives the request and successfully responds.
  • Step 508 The terminal extracts a key from the request success response, and performs a card write operation on the smart card according to the key;
  • the terminal extracts the corresponding key from the request success response, and performs a card writing operation on the smart card according to the key.
  • the smart card allows the card to be operated by the terminal;
  • the smart card does not allow the card to be written by the terminal.
  • Step 509 After the card is successfully written, the terminal sends a confirmation request message to the background server, where the confirmation request message carries a verification verification code;
  • the confirmation request message carries a verification verification code, and the verification verification code can be generated according to the data of the current card writing operation process.
  • Step 510 The background server verifies the verification verification code carried in the confirmation request packet, and sends a confirmation success message to the terminal when the verification succeeds;
  • the background server verifies the sensitive information such as the verification verification code carried in the confirmation request message. Because the verification verification code is generated according to the data of the current card writing operation process of the terminal, the background server compares the current card writing operation indicated in the recharging request with the actual card writing operation of the terminal, and if they are the same, The verification is considered successful, and if it is not the same, the verification is considered unsuccessful. This step can ensure that the recharge data of the recharge process is not tampered with.
  • the background server sends a confirmation success message to the terminal.
  • step 511 the terminal receives the confirmation success message and records the refill success information.
  • the terminal After receiving the confirmation message of the system, the terminal records the transaction success information.
  • the terminal may also perform statistics on the transaction success information in the batch every predetermined batch, obtain statistical information and upload the information to the background server.
  • the recharging method provided in this embodiment is to verify the refill request and the confirmation request message by the background server by using the online processing method when the third party recharges, and the terminal root is verified by the terminal root.
  • the key issued by the key server the card is written; the problem of poor security of the current recharge system is solved; and each recharge process is performed, and multi-step verification is performed to ensure the security effect of the recharge process.
  • FIG. 6 shows a flow chart of a method for recharging according to still another embodiment of the present invention.
  • This embodiment is exemplified by applying the recharging method to the implementation environment shown in FIG. 1.
  • the recharge method includes:
  • Step 601 The terminal pays the recharge amount through the built-in application, and sends a refill request to the background server after successfully paying the recharge amount;
  • the terminal in this embodiment may be a mobile terminal supporting NFC technology, such as a mobile phone. That is, in this embodiment, the user can directly recharge the smart card through the mobile phone supporting the NFC technology.
  • An application may be pre-built in the terminal, and then the terminal pays the recharge amount through the built-in application according to the operation triggered by the user, and the payment form may include, but is not limited to, bank transfer, deposit or third party payment.
  • the terminal After successfully paying the replenishment amount to the background server, the terminal sends a refill request to the background server.
  • the refill request carries the user profile.
  • the background server receives the refill request sent by the terminal.
  • Step 602 The background server verifies the user data carried in the refill request.
  • the background server After receiving the refill request, the background server extracts the user data carried in the refill request. The user profile is then verified.
  • the background server verifies the underlying data to verify that the underlying data is correct.
  • the background server authenticates the user's identity and verifies that the user's identity is correct.
  • the user identity can be the identity of the cardholder or the identity of the user of the terminal.
  • the background server verifies the smart card data.
  • the smart card data may include a card type parameter of the smart card, a smart card identifier, and the like.
  • the terminal and the smart card are both terminals and smart cards recognized by the background server, not illegally accessed terminals, or forged cards or blacklist cards.
  • Step 603 The background server sends a key acquisition request to the key server when the verification is successful.
  • the background server sends a key acquisition request to the key server. Because the keys corresponding to different smart cards are different, the background server sends the key server to obtain the current A key acquisition request of a key corresponding to the smart card to be recharged. This key is a recharge key.
  • Step 604 The key server receives a key acquisition request, and generates a key according to the key acquisition request.
  • the key server receives the key acquisition request, and generates a key corresponding to the smart card according to the key acquisition request.
  • the encryption machine in the key server may calculate a recharge key corresponding to the smart card by using a decentralized algorithm.
  • Step 605 The key server feeds back the key to the background server.
  • the key server feeds back the key corresponding to the smart card to the background server.
  • Step 606 The background server generates a request success response carrying the key, and sends a request success response to the terminal.
  • the terminal receives the request and successfully responds.
  • Step 607 The terminal extracts a key from the request success response, and performs a card write operation on the smart card according to the key;
  • the terminal extracts the corresponding key from the request success response, and performs a card writing operation on the smart card according to the key. Since the terminal is a terminal that supports the NFC technology, the terminal performs a card writing operation on the smart card according to the key through the NFC technology.
  • the smart card allows the card to be operated by the terminal;
  • the smart card does not allow the card to be written by the terminal.
  • Step 608 After the card is successfully written, the terminal sends a confirmation request message to the background server, where the confirmation request message carries a verification verification code;
  • the confirmation request message carries a verification verification code, and the verification verification code can be generated according to the data of the current card writing operation process.
  • Step 609 The background server verifies the verification verification code carried in the confirmation request message, and sends a confirmation success message to the terminal when the verification succeeds;
  • the background server verifies the sensitive information such as the verification verification code carried in the confirmation request message. Because the verification verification code is generated according to the data of the current card writing operation process of the terminal, the background server compares the current card writing operation indicated in the recharging request with the actual card writing operation of the terminal, and if they are the same, The verification is considered successful, and if it is not the same, the verification is considered unsuccessful. This step can ensure that the recharge data of the recharge process is not tampered with.
  • the background server sends a confirmation success message to the terminal.
  • step 610 the terminal receives the confirmation success message and records the refill success information.
  • the terminal After receiving the confirmation message of the system, the terminal records the transaction success information.
  • the terminal may also perform statistics on the transaction success information in the batch every predetermined batch, obtain statistical information and upload the information to the background server.
  • the recharging method provided by the embodiment is used to verify the refill request and the confirmation request message by the background server and the key according to the key by using the online processing method when recharging the mobile phone supporting the NFC technology.
  • the key issued by the server is used to write the card; the problem of poor security of the current recharge system is solved; and each recharge process is performed, and multi-step verification is performed to ensure the security effect of the recharge process.
  • FIG. 7 is a structural block diagram of a recharge system according to an embodiment of the present invention.
  • the system includes: a terminal 720, a background server 740, and a key server 760;
  • the terminal 720 is configured to send a refill request to the background server 740, where the refill request carries user data.
  • the background server 740 is configured to verify user data carried in the refill request, and send a key acquisition request to the key server 760 when the verification is successful.
  • the key server 760 is configured to receive the key acquisition request, generate a key according to the key acquisition request, and feed back the key to the background server 740.
  • the background server 740 is configured to generate a request success response carrying the key, and send the request success response to the terminal 720.
  • the terminal 720 is configured to extract the key from the request success response, perform a card write operation on the smart card according to the key, and send a confirmation request message to the background server 740 after the card is successfully written.
  • the confirmation request message carries a verification verification code.
  • the background server 740 is configured to verify the verification verification code carried in the confirmation request message, and send a confirmation success message to the terminal 720 when the verification is successful.
  • the terminal 720 is configured to receive the acknowledged success message and record the refill success information.
  • the terminal 720 is configured to receive a third-party recharge operation of the user, and send the refill request to the background server 740 according to the third-party recharge operation;
  • the background server 740 is further configured to forward the refill request to a third-party system when the verification succeeds, and send the key to the key server 760 after receiving the successful recharge response of the third-party system. Get the request.
  • the refill system provided in this embodiment adopts online processing by any recharge method, and the background server verifies the refill request and the confirmation request message, and the key issued by the terminal according to the key server.
  • Write the card solve the problem of poor safety of the current recharge system; achieve a multi-step verification for each recharge process to ensure the safety of the recharge process.
  • the terminal 720 is configured to receive an offline recharge operation of the user, and send the recharge to the background server 740 according to the offline recharge operation. request.
  • the terminal 720 is configured to receive a user recharge operation, and send the recharge to the background server 740 according to the recharge refill operation. request.
  • the terminal 720 is a terminal supporting a short-range communication technology NFC;
  • the terminal 720 is configured to use a built-in application to pay a recharge amount, and send the refill request to the background server 720 after successfully repaying the recharge amount;
  • the terminal 720 is further configured to perform a card writing operation on the smart card by using the NFC technology according to the key.
  • the refill system provided by the above embodiment is only illustrated by the division of the above functional modules. In actual applications, the function distribution may be completed by different functional modules as needed.
  • the internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the refilling system and the charging method embodiment are provided in the same concept. For details, refer to the method embodiment, and details are not described herein again.
  • FIG. 8 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
  • the electronic device can be used to implement the refilling method provided in the above embodiments. Specifically:
  • the terminal 800 may include an RF (Radio Frequency) circuit 810, a memory 820 including one or more computer readable storage media, an input unit 830, a display unit 840, a sensor 850, an audio circuit 860, a short-range communication module 870, A processor 880 having one or more processing cores, and a power supply 890 and the like are included.
  • RF Radio Frequency
  • FIG. 8 does not constitute a limitation to the terminal, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements. among them:
  • the RF circuit 810 can be used for transmitting and receiving information or during a call, and receiving and transmitting the signal. Specifically, after receiving the downlink information of the base station, the downlink information is processed by one or more processors 880; in addition, the data related to the uplink is sent to the base station. .
  • the RF circuit 810 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, an LNA (Low Noise Amplifier). , duplexer, etc.
  • RF circuitry 810 can also communicate with the network and other devices via wireless communication.
  • Wireless communication can use any communication standard or protocol, including but not limited to GSM (Global System of Mobile communication), GPRS (General Packet Radio Service), CDMA (Code Division Multiple Access) Divisional Multiple Access), WCDMA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), e-mail, SMS (Short Messaging Service), and the like.
  • GSM Global System of Mobile communication
  • GPRS General Packet Radio Service
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • LTE Long Term Evolution
  • e-mail Short Messaging Service
  • the memory 820 can be used to store software programs and modules, and the processor 880 executes various functional applications and data processing by running software programs and modules stored in the memory 820.
  • the memory 820 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required for at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may be stored according to The data created by the use of the terminal 800 (such as audio data, phone book, etc.) and the like.
  • memory 820 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 820 can also include a memory controller to provide access to memory 820 by processor 880 and input unit 830.
  • Input unit 830 can be used to receive input numeric or character information, as well as to generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function controls.
  • input unit 830 can include touch-sensitive surface 831 as well as other input devices 832.
  • Touch sensitive surface 831 also Known as a touch display or trackpad, it can collect touch operations on or near the user (such as the user using a finger, stylus, etc., on any touchable surface 831 or near the touch-sensitive surface 831. Operation), and drive the corresponding connecting device according to a preset program.
  • the touch-sensitive surface 831 can include two portions of a touch detection device and a touch controller.
  • the touch detection device detects the touch orientation of the user, and detects a signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts the touch information into contact coordinates, and sends the touch information.
  • the processor 880 is provided and can receive commands from the processor 880 and execute them.
  • the touch sensitive surface 831 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves.
  • the input unit 830 can also include other input devices 832.
  • other input devices 832 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackballs, mice, joysticks, and the like.
  • Display unit 840 can be used to display information entered by the user or information provided to the user and various graphical user interfaces of terminal 800, which can be constructed from graphics, text, icons, video, and any combination thereof.
  • the display unit 840 can include a display panel 841.
  • the display panel 841 can be configured in the form of an LCD (Liquid Crystal Display), an OLED (Organic Light-Emitting Diode), or the like.
  • the touch-sensitive surface 831 can cover the display panel 841, and when the touch-sensitive surface 831 detects a touch operation thereon or nearby, it is transmitted to the processor 880 to determine the type of the touch event, and then the processor 880 according to the touch event The type provides a corresponding visual output on display panel 841.
  • touch-sensitive surface 831 and display panel 841 are implemented as two separate components to implement input and input functions, in some embodiments, touch-sensitive surface 831 can be integrated with display panel 841 for input. And output function.
  • Terminal 800 can also include at least one type of sensor 850, such as a light sensor, motion sensor, and other sensors.
  • the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 841 according to the brightness of the ambient light, and the proximity sensor may close the display panel 841 when the terminal 800 moves to the ear. / or backlight.
  • the gravity acceleration sensor can detect the magnitude of acceleration in all directions (usually three axes). When it is stationary, it can detect the magnitude and direction of gravity.
  • terminal 800 can also be configured with gyroscope, barometer, hygrometer, thermometer, infrared sensor Other sensors, such as the device, will not be described here.
  • Audio circuit 860, speaker 861, and microphone 862 can provide an audio interface between the user and terminal 800.
  • the audio circuit 860 can transmit the converted electrical data of the received audio data to the speaker 861 for conversion to the sound signal output by the speaker 861; on the other hand, the microphone 862 converts the collected sound signal into an electrical signal by the audio circuit 860. After receiving, it is converted into audio data, and then processed by the audio data output processor 180, sent to the terminal, for example, via the RF circuit 18, or outputted to the memory 120 for further processing.
  • the audio circuit 160 may also include an earbud jack to provide communication of the peripheral earphones with the terminal 800.
  • the short-range communication module 170 may include WiFi (wireless fidelity) technology and/or NFC technology and/or Bluetooth technology and/or infrared technology, and the terminal 800 may help the user to send and receive emails and browse the webpage through the short-range communication module 170. And accessing streaming media, etc., it provides users with wireless broadband Internet access and close-range communication, such as reading and writing of electronic cards in the embodiment of the present invention.
  • Processor 880 is the control center of terminal 800, which connects various portions of the entire handset using various interfaces and lines, by running or executing software programs and/or modules stored in memory 820, and recalling data stored in memory 820, The various functions and processing data of the terminal 800 are performed to perform overall monitoring of the mobile phone.
  • the processor 880 may include one or more processing cores; preferably, the processor 880 may integrate an application processor and a modem processor, where the application processor mainly processes an operating system, a user interface, an application, and the like.
  • the modem processor primarily handles wireless communications. It will be appreciated that the above described modem processor may also not be integrated into the processor 880.
  • the terminal 800 also includes a power supply 890 (such as a battery) for powering various components.
  • the power supply can be logically coupled to the processor 880 through a power management system to manage functions such as charging, discharging, and power management through the power management system.
  • the power supply 890 may also include any one or more of a DC or AC power source, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and the like.
  • the terminal 800 may further include a camera, a Bluetooth module, and the like, and details are not described herein again.
  • the display unit of the electronic device is a touch screen display
  • the electronic device further includes a memory, and one or more programs, wherein one or more programs are stored in the memory and configured to be one or one
  • the above processor executes one or more programs A method for performing the recharging as described above is included.
  • FIG. 9 is a schematic structural diagram of a server according to an embodiment of the present invention.
  • the server 900 includes a central processing unit (CPU) 901, a system memory 904 including a random access memory (RAM) 902 and a read only memory (ROM) 903, and a system bus 905 that connects the system memory 904 and the central processing unit 901.
  • the server 900 also includes a basic input/output system (I/O system) 906 that facilitates transfer of information between various devices within the computer, and mass storage for storing the operating system 913, applications 914, and other program modules 915.
  • I/O system basic input/output system
  • the basic input/output system 906 includes a display 908 for displaying information and an input device 909 such as a mouse or keyboard for user input of information. Both the display 908 and the input device 909 are connected to the central processing unit 901 via an input and output controller 910 that is coupled to the system bus 905.
  • the basic input/output system 906 can also include an input output controller 910 for receiving and processing input from a plurality of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input and output controller 910 also provides output to a display screen, printer, or other type of output device.
  • the mass storage device 907 is connected to the central processing unit 901 by a mass storage controller (not shown) connected to the system bus 905.
  • the mass storage device 907 and its associated computer readable medium provide non-volatile storage for the server 900. That is, the mass storage device 907 can include a computer readable medium (not shown) such as a hard disk or a CD-ROM drive.
  • the computer readable medium can include computer storage media and communication media.
  • Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data.
  • Computer storage media include RAM, ROM, EPROM, EEPROM, flash memory or other solid state storage technologies, CD-ROM, DVD or other optical storage, tape cartridges, magnetic tape, magnetic disk storage or other magnetic storage devices.
  • RAM random access memory
  • ROM read only memory
  • EPROM Erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • the server 900 may also pass through a network such as the Internet. Connect to a remote computer running on the network. That is, the server 900 can be connected to the network 912 through a network interface unit 911 connected to the system bus 905, or can be connected to other types of networks or remote computer systems (not shown) using the network interface unit 99. .
  • the memory further includes one or more programs, the one or more programs being stored in a memory, the one or more programs including instructions for performing a refill method provided by an embodiment of the present invention.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

一种充值系统，属于数据处理领域。所述充值系统包括：终端（720）、后台服务器（740）和密钥服务器（760）。其中，终端向后台服务器发送充值请求；后台服务器对充值请求进行验证，并在验证成功时向密钥服务器获取密钥并发送给终端；终端根据密钥对智能卡进行写卡操作，并在写卡成功后向后台服务器发送确认请求报文；后台服务器对确认请求报文进行验证，并在验证成功时向终端发送确认成功报文。该系统不论任何充值方式，均采用联机处理，并由后台服务器对充值请求和确认请求报文进行验证以及由终端根据密钥服务器下发的密钥进行写卡；解决了目前的充值系统安全性较差的问题；达到了每次充值过程，都进行了多步验证，确保充值安全的效果。

Description

充值系统 技术领域
本发明涉及数据处理领域，特别涉及一种充值系统。
背景技术
充值系统是一卡通交易系统的重要组成部分。充值系统是一卡通交易系统正常运作的第一步。
一卡通交易系统是指通过IC(Integrated Circuit Card，集成电路卡)卡、PBOC(The People's Bank of China，中国人民银行)卡、PSAM(Purchase Secure Access Module，销售点终端安全存取模块)卡或电子钱包等智能卡进行交易的系统。目前的充值系统可以通过线下充值、线上充值、自助现金终端等方式为智能卡进行充值。
在实现本发明的过程中，发明人发现现有技术至少存在以下问题：目前的充值系统通常只做一步密钥验证，安全性较差。
发明内容
为了解决目前的充值系统安全性较差的问题，本发明实施例提供了一种充值系统。所述技术方案如下：
根据本发明实施例的第一方面，提供了一种充值系统，所述系统包括：终端、后台服务器和密钥服务器；
所述终端，用于向所述后台服务器发送充值请求，所述充值请求携带有用户资料；
所述后台服务器，用于对所述充值请求中携带的用户资料进行验证，并在验证成功时向所述密钥服务器发送密钥获取请求；
所述密钥服务器，用于接收所述密钥获取请求，根据所述密钥获取请求生成密钥，并向所述后台服务器反馈所述密钥；
所述后台服务器，用于生成携带有所述密钥的请求成功响应，并将所述请求成功响应发送给所述终端；
所述终端，用于从所述请求成功响应中提取所述密钥，根据所述密钥对智能卡进行写卡操作，并在写卡成功后向所述后台服务器发送确认请求报文，所述确认请求报文携带有校验验证码；
所述后台服务器，用于对所述确认请求报文中携带的所述校验验证码进行验证，并在验证成功时向所述终端发送确认成功报文；
所述终端，用于接收所述确认成功报文，记录充值成功信息；
其中，所述终端，用于接收用户的第三方充值操作，根据所述第三方充值操作向所述后台服务器发送所述充值请求；
所述后台服务器，还用于在验证成功时将所述充值请求转发给第三方系统，在接收到所述第三方系统的成功充值响应后，向所述密钥服务器发送所述密钥获取请求。
在第一方面的第一种可能的实现方式中，所述终端，用于接收用户的线下充值操作，根据所述线下充值操作向所述后台服务器发送所述充值请求。
在第一方面的第二种可能的实现方式中，所述终端，用于接收用户的圈存充值操作，根据所述圈存充值操作向所述后台服务器发送所述充值请求。
在第一方面的第三种可能的实现方式中，所述终端为支持近距离通信技术NFC的终端；
所述终端，用于通过内置应用程序支付充值金额，在成功支付所述充值金额后向所述后台服务器发送所述充值请求；
所述终端，还用于根据所述密钥通过所述NFC技术对所述智能卡进行写卡操作。
根据本发明实施例的第二方面，提供了一种充值方法，所述方法包括：
终端向后台服务器发送充值请求，所述充值请求携带有用户资料；
所述后台服务器对所述充值请求中携带的用户资料进行验证，并在验证成功时向密钥服务器发送密钥获取请求；
所述密钥服务器接收所述密钥获取请求，根据所述密钥获取请求生成密钥，并向所述后台服务器反馈所述密钥；
所述后台服务器生成携带有所述密钥的请求成功响应，并将所述请求成功响应发送给所述终端；
所述终端从所述请求成功响应中提取所述密钥，根据所述密钥对智能卡进行写卡操作，并在写卡成功后向所述后台服务器发送确认请求报文，所述确认请求报文携带有校验验证码；
所述后台服务器对所述确认请求报文中携带的所述校验验证码进行验证，并在验证成功时向所述终端发送确认成功报文；
所述终端接收所述确认成功报文，记录充值成功信息。
在第二方面的第一种可能的实现方式中，所述终端向后台服务器发送充值请求，包括：
所述终端接收用户的线下充值操作，根据所述线下充值操作向所述后台服务器发送所述充值请求。
在第二方面的第二种可能的实现方式中，所述终端向后台服务器发送充值请求，包括：
所述终端接收用户的圈存充值操作，根据所述圈存充值操作向所述后台服务器发送所述充值请求。
在第二方面的第三种可能的实现方式中，所述终端向后台服务器发送充值请求，包括：
所述终端接收用户的第三方充值操作，根据所述第三方充值操作向所述后台服务器发送所述充值请求；
所述后台服务器，还用于在验证成功时将所述充值请求转发给第三方系统，在接收到所述第三方系统的成功充值响应后，向所述密钥服务器发送所述密钥获取请求。
在第二方面的第四种可能的实现方式中，所述终端向后台服务器发送充值请求，包括：
在所述终端为支持近距离通信技术NFC的终端时，所述终端通过内置应用程序支付充值金额，在成功支付所述充值金额后向所述后台服务器发送所述充值请求；
所述终端根据所述密钥对卡片进行写卡操作，包括：
所述终端根据所述密钥通过所述NFC技术对所述智能卡进行写卡操作。
本发明实施例提供的技术方案带来的有益效果是：
通过不论任何充值方式，均采用联机处理，并由后台服务器对充值请求和确认请求报文进行验证以及由终端根据密钥服务器下发的密钥进行写卡；解决了目前的充值系统安全性较差的问题；达到了每次充值过程，都进行了多步验证，确保充值过程的安全性的效果。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1是本发明各个实施例所涉及的实施环境的结构示意图；
图2是本发明一个实施例提供的充值方法的方法流程图；
图3是本发明另一个实施例提供的充值方法的方法流程图；
图4是本发明再一个实施例提供的充值方法的方法流程图；
图5是本发明又一个实施例提供的充值方法的方法流程图；
图6是本发明又一个实施例提供的充值方法的方法流程图；
图7是本发明另一个实施例提供的充值系统的结构示意图；
图8是本发明一个实施例提供的终端的结构示意图；
图9是本发明另一实施例提供的服务器的结构示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明实施方式作进一步地详细描述。
请参考图1，其示出了本发明各个实施例所涉及的实施环境的结构示意图。该实施环境包括终端120、后台服务器140和密钥服务器160。其中，终端120和后台服务器140之间通过有线网络或者无线网络相连；后台服务器140和密钥服务器160通过有线网络或者无线网络相连。
终端120是具有智能卡读写能力的电子设备。终端120可以是手机、膝上型便携计算机和台式计算机等等。比如，终端120可以是支持NFC(Near Field  Communication，近距离无线通信技术)技术的移动终端，具有以非接触读取方式读写取外部的智能卡的能力。智能卡包括IC卡、PBOC卡、PSAM卡、电子钱包、NFC卡以及美国苹果公司出品的iBeacon。
后台服务器140可以是一台服务器，或者由若干台服务器组成的服务器集群，或者是一个云计算服务中心。
密钥服务器160可以是一台服务器，或者由若干台服务器组成的服务器集群，或者是一个云计算服务中心。
请参考图2，其示出了本发明一个实施例提供的充值方法的方法流程图。本实施例以该充值方法应用于图1所示实施环境来举例说明。该充值方法，可以包括：
步骤201，终端向后台服务器发送充值请求，充值请求携带有用户资料；
步骤202，后台服务器对充值请求中携带的用户资料进行验证；
步骤203，后台服务器在验证成功时向密钥服务器发送密钥获取请求；
步骤204，密钥服务器接收密钥获取请求，根据密钥获取请求生成密钥；
步骤205，密钥服务器向后台服务器反馈密钥；
步骤206，后台服务器生成携带有密钥的请求成功响应，并将请求成功响应发送给终端；
步骤207，终端从请求成功响应中提取密钥，根据密钥对智能卡进行写卡操作；
步骤208，终端在写卡成功后向后台服务器发送确认请求报文，该确认请求报文携带有校验验证码；
步骤209，后台服务器对确认请求报文中携带的校验验证码进行验证，并在验证成功时向终端发送确认成功报文；
步骤210，终端接收确认成功报文，记录充值成功信息。
综上所述，本实施例提供的充值方法，通过不论任何充值方式，均采用联机处理，并由后台服务器对充值请求和确认请求报文进行验证以及由终端根据密钥服务器下发的密钥进行写卡；解决了目前的充值系统安全性较差的问题；达到了每次充值过程，都进行了多步验证，确保充值过程的安全性的效果。
由于为智能卡充值的过程中，终端向后台服务器发送充值请求，可以分为如下几种不同的方式：
1、线下充值方式；
2、线上的圈存充值方式；
3、通过第三方系统充值的方式；
4、通过支持NFC的手机进行充值的方式。
下面分别采用不同的实施例对这几种方式分别进行详细描述。
请参考图3，其示出了本发明一个实施例提供的充值方法的方法流程图。，本实施例以该充值方法应用于图1所示实施环境来举例说明。该方法可以包括：
步骤301，终端接收用户的线下充值操作，根据线下充值操作向后台服务器发送充值请求；
当终端是自助现金充值终端时，线下充值操作可以是用户将充值现金放入自助现金充值终端的操作；
当终端是转账终端时，线下充值操作可以是用户将银行卡账户的资金转入充值系统对应的账户的操作。
当用户执行线下充值操作成功后，也即资金转入充值系统方后，终端向后台服务器发送充值请求。该充值请求通常携带有用户资料以及充值数据，用户资料包括但不限于基础资料、用户身份资料、智能卡资料等。充值数据通常包括充值金额，还可能包括充值规则。
对应地，后台服务器接收终端发送的充值请求。
步骤302，后台服务器对充值请求中携带的用户资料进行验证；
后台服务器在接收到充值请求后，提取充值请求中携带的用户资料。然后对该用户资料进行验证。
如果用户资料包括基础资料，则后台服务器对基础资料进行验证，验证该基础资料是否正确。
如果用户资料包括用户身份，则后台服务器对用户身份进行验证，验证该 用户身份是否正确。用户身份可以是持卡人的用户身份，或者终端的用户身份。
如果用户资料包括智能卡资料，则后台服务器对智能卡资料进行验证。智能卡资料可以包括智能卡的卡类型参数，智能卡标识等。
本步骤可以保证终端和智能卡均为充值系统所认可的终端和智能卡，而不是非法接入的终端，或者伪造卡或黑名单卡。
步骤303，后台服务器在验证成功时向密钥服务器发送密钥获取请求；
在上述各种验证均通过后，后台服务器向密钥服务器发送密钥获取请求。由于不同智能卡对应的密钥不同，后台服务器向密钥服务器发送用于获取当前待充值的智能卡对应的密钥的密钥获取请求。该密钥为充值密钥。
步骤304，密钥服务器接收密钥获取请求，根据密钥获取请求生成密钥；
密钥服务器接收密钥获取请求，根据密钥获取请求生成与该智能卡对应密钥。具体来讲，密钥服务器中的加密机可以采用分散算法计算得到与该智能卡对应的充值密钥。
步骤305，密钥服务器向后台服务器反馈密钥；
密钥服务器向后台服务器反馈与该智能卡对应的密钥。
步骤306，后台服务器生成携带有密钥的请求成功响应，并将请求成功响应发送给终端；
对应地，终端接收该请求成功响应。
步骤307，终端从请求成功响应中提取密钥，根据密钥对智能卡进行写卡操作；
终端从请求成功响应中提取对应的密钥，根据该密钥对智能卡进行写卡操作。
如果该密钥为与该智能卡对应的密钥，则智能卡允许该终端的写卡操作；
如果该密钥为与该智能卡不对应的密钥，则智能卡不允许该终端的写卡操作。
步骤308，终端在写卡成功后向后台服务器发送确认请求报文，该确认请求报文携带有校验验证码；
终端在写卡成功后，向后台服务器发送确认请求报文。该确认请求报文中携带有校验验证码，该校验验证码可以根据本次写卡操作过程的数据生成。
步骤309，后台服务器对确认请求报文中携带的校验验证码进行验证，并在验证成功时向终端发送确认成功报文；
后台服务器对确认请求报文中携带的校验验证码等敏感信息进行验证。由于该校验验证码根据终端本次写卡操作过程的数据生成，所以后台服务器根据充值请求中所指示的本次写卡操作和终端本次实际的写卡操作进行比对，如果相同，则认为验证成功，如果不相同，则认为验证不成功。本步骤可以保证充值过程的充值数据不被篡改。
然后，后台服务器向终端发送确认成功报文。
步骤310，终端接收确认成功报文，记录充值成功信息。
终端在接收到系统的确认成功报文之后，记录交易成功信息。
优选地，终端还可以每隔预定批次，将该批次内的交易成功信息进行统计，得到统计信息并上传至后台服务器。
综上所述，本实施例提供的充值方法，通过在线下充值时，也使用联机处理的方式，由后台服务器对充值请求和确认请求报文进行验证以及由终端根据密钥服务器下发的密钥进行写卡；解决了目前的充值系统安全性较差的问题；达到了每次充值过程，都进行了多步验证，确保充值过程的安全性的效果。
请参考图4，其示出了本发明另一实施例提供的充值方法的方法流程图。本实施例以该充值方法应用于图1所示实施环境来举例说明。该方法可以包括：
步骤401，终端接收用户的圈存充值操作，根据圈存充值操作向后台服务器发送充值请求；
终端接收用户的圈存充值操作，根据圈存充值操作向后台服务器发送充值请求。圈存充值操作是指用户将A账户中的资金存入智能卡所对应的B账户中的一种操作。该智能卡所对应的B账户通常与A账户进行绑定。终端在接收到用户的圈存充值操作后，根据圈存充值的金额向后台服务器发送充值请求。该充值请求通常携带有用户资料。
对应地，后台服务器接收终端发送的充值请求。
步骤402，后台服务器对充值请求中携带的用户资料进行验证；
后台服务器在接收到充值请求后，提取充值请求中携带的用户资料。然后对该用户资料进行验证。
如果用户资料包括基础资料，则后台服务器对基础资料进行验证，验证该基础资料是否正确。
如果用户资料包括用户身份，则后台服务器对用户身份进行验证，验证该用户身份是否正确。用户身份可以是持卡人的用户身份，或者终端的用户身份。
如果用户资料包括智能卡资料，则后台服务器对智能卡资料进行验证。智能卡资料可以包括智能卡的卡类型参数，智能卡标识等。
本步骤可以保证终端和智能卡均为后台服务器所认可的终端和智能卡，而不是非法接入的终端，或者伪造卡或黑名单卡。
步骤403，后台服务器在验证成功时向密钥服务器发送密钥获取请求；
在上述各种验证均通过后，后台服务器向密钥服务器发送密钥获取请求。由于不同智能卡对应的密钥不同，后台服务器向密钥服务器发送用于获取当前待充值的智能卡对应的密钥的密钥获取请求。该密钥为充值密钥。
步骤404，密钥服务器接收密钥获取请求，根据密钥获取请求生成密钥；
密钥服务器接收密钥获取请求，根据密钥获取请求生成与该智能卡对应密钥。具体来讲，密钥服务器中的加密机可以采用分散算法计算得到与该智能卡对应的充值密钥。
步骤405，密钥服务器向后台服务器反馈密钥；
密钥服务器向后台服务器反馈与该智能卡对应的密钥。
步骤406，后台服务器生成携带有密钥的请求成功响应，并将请求成功响应发送给终端；
对应地，终端接收该请求成功响应。
步骤407，终端从请求成功响应中提取密钥，根据密钥对智能卡进行写卡操作；
终端从请求成功响应中提取对应的密钥，根据该密钥对智能卡进行写卡操作。
如果该密钥为与该智能卡对应的密钥，则智能卡允许该终端的写卡操作；
如果该密钥为与该智能卡不对应的密钥，则智能卡不允许该终端的写卡操 作。
步骤408，终端在写卡成功后向后台服务器发送确认请求报文，该确认请求报文携带有校验验证码；
终端在写卡成功后，向后台服务器发送确认请求报文。该确认请求报文中携带有校验验证码，该校验验证码可以根据本次写卡操作过程的数据生成。
步骤409，后台服务器对确认请求报文中携带的校验验证码进行验证，并在验证成功时向终端发送确认成功报文；
后台服务器对确认请求报文中携带的校验验证码等敏感信息进行验证。由于该校验验证码根据终端本次写卡操作过程的数据生成，所以后台服务器根据充值请求中所指示的本次写卡操作和终端本次实际的写卡操作进行比对，如果相同，则认为验证成功，如果不相同，则认为验证不成功。本步骤可以保证充值过程的充值数据不被篡改。
然后，后台服务器向终端发送确认成功报文。
步骤410，终端接收确认成功报文，记录充值成功信息。
终端在接收到系统的确认成功报文之后，记录交易成功信息。
优选地，终端还可以每隔预定批次，将该批次内的交易成功信息进行统计，得到统计信息并上传至后台服务器。
综上所述，本实施例提供的充值方法，通过在线上圈存充值时，也使用联机处理的方式，由后台服务器对充值请求和确认请求报文进行验证以及由终端根据密钥服务器下发的密钥进行写卡；解决了目前的充值系统安全性较差的问题；达到了每次充值过程，都进行了多步验证，确保充值过程的安全性的效果。
请参考图5，其示出了本发明另一实施例提供的充值方法的方法流程图。本实施例以该充值方法应用于图1所示实施环境来举例说明。该方法可以包括：
步骤501，终端接收用户的第三方充值操作，根据第三方充值操作向后台服务器发送充值请求；
第三方系统通常是指电力、燃气、水利、社保、公积金、支付平台等非本智能卡系统的交易系统。第三方系统预先接入图1所示的后台服务器中。
终端接收用户的第三方充值操作，根据第三方充值操作向后台服务器发送充值请求。该充值请求可以携带有第三方系统标识、充值金额和用户资料等。
对应地，后台服务器接收终端发送的充值请求。
步骤502，后台服务器对充值请求中携带的用户资料进行验证；
后台服务器在接收到充值请求后，提取充值请求中携带的用户资料。然后对该用户资料进行验证。
如果用户资料包括基础资料，则后台服务器对基础资料进行验证，验证该基础资料是否正确。
如果用户资料包括用户身份，则后台服务器对用户身份进行验证，验证该用户身份是否正确。用户身份可以是持卡人的用户身份，或者终端的用户身份。
如果用户资料包括智能卡资料，则后台服务器对智能卡资料进行验证。智能卡资料可以包括智能卡的卡类型参数，智能卡标识等。
本步骤可以保证终端和智能卡均为后台服务器所认可的终端和智能卡，而不是非法接入的终端，或者伪造卡或黑名单卡。
步骤503，后台服务器在验证成功时将充值请求转发给第三方系统；
后台服务器在验证成功时将充值请求转发给第三方系统。在充值请求中携带有第三方系统标识和充值金额时，后台服务器根据第三方系统标识将携带有该充值金额的充值请求发送给第三方系统，以便该第三方系统进行充值，并在充值成功后，向后台服务器反馈成功充值响应。
步骤504，后台服务器在接收到第三方系统的成功充值响应后，向密钥服务器发送密钥获取请求；
在上述各种验证均通过后，后台服务器向密钥服务器发送密钥获取请求。由于不同智能卡对应的密钥不同，后台服务器向密钥服务器发送用于获取当前待充值的智能卡对应的密钥的密钥获取请求。该密钥为充值密钥。
步骤505，密钥服务器接收密钥获取请求，根据密钥获取请求生成密钥；
密钥服务器接收密钥获取请求，根据密钥获取请求生成与该智能卡对应密钥。具体来讲，密钥服务器中的加密机可以采用分散算法计算得到与该智能卡对应的充值密钥。
步骤506，密钥服务器向后台服务器反馈密钥；
密钥服务器向后台服务器反馈与该智能卡对应的密钥。
步骤507，后台服务器生成携带有密钥的请求成功响应，并将请求成功响应发送给终端；
对应地，终端接收该请求成功响应。
步骤508，终端从请求成功响应中提取密钥，根据密钥对智能卡进行写卡操作；
终端从请求成功响应中提取对应的密钥，根据该密钥对智能卡进行写卡操作。
如果该密钥为与该智能卡对应的密钥，则智能卡允许该终端的写卡操作；
如果该密钥为与该智能卡不对应的密钥，则智能卡不允许该终端的写卡操作。
步骤509，终端在写卡成功后向后台服务器发送确认请求报文，该确认请求报文携带有校验验证码；
终端在写卡成功后，向后台服务器发送确认请求报文。该确认请求报文中携带有校验验证码，该校验验证码可以根据本次写卡操作过程的数据生成。
步骤510，后台服务器对确认请求报文中携带的校验验证码进行验证，并在验证成功时向终端发送确认成功报文；
后台服务器对确认请求报文中携带的校验验证码等敏感信息进行验证。由于该校验验证码根据终端本次写卡操作过程的数据生成，所以后台服务器根据充值请求中所指示的本次写卡操作和终端本次实际的写卡操作进行比对，如果相同，则认为验证成功，如果不相同，则认为验证不成功。本步骤可以保证充值过程的充值数据不被篡改。
然后，后台服务器向终端发送确认成功报文。
步骤511，终端接收确认成功报文，记录充值成功信息。
终端在接收到系统的确认成功报文之后，记录交易成功信息。
优选地，终端还可以每隔预定批次，将该批次内的交易成功信息进行统计，得到统计信息并上传至后台服务器。
综上所述，本实施例提供的充值方法，通过在第三方充值时，也使用联机处理的方式，由后台服务器对充值请求和确认请求报文进行验证以及由终端根 据密钥服务器下发的密钥进行写卡；解决了目前的充值系统安全性较差的问题；达到了每次充值过程，都进行了多步验证，确保充值过程的安全性的效果。
请参考图6，其示出了本发明又一个实施例提供的充值方法的方法流程图。本实施例以该充值方法应用于图1所示的实施环境中来举例说明。该充值方法包括：
步骤601，终端通过内置应用程序支付充值金额，在成功支付充值金额后向后台服务器发送充值请求；
本实施例中的终端，可以是支持NFC技术的移动终端，比如手机。也即，本实施例中用户可以直接通过支持NFC技术的手机对智能卡进行充值。
终端中可以预先内置应用程序(APP)，然后终端根据用户触发的操作来通过该内置应用程序支付充值金额，支付形式可以包括但不限于银行转账、圈存或第三方支付。当成功向后台服务器支付充值金额后，终端向后台服务器发送充值请求。该充值请求携带有用户资料。
对应地，后台服务器接收终端发送的充值请求。
步骤602，后台服务器对充值请求中携带的用户资料进行验证；
后台服务器在接收到充值请求后，提取充值请求中携带的用户资料。然后对该用户资料进行验证。
如果用户资料包括基础资料，则后台服务器对基础资料进行验证，验证该基础资料是否正确。
如果用户资料包括用户身份，则后台服务器对用户身份进行验证，验证该用户身份是否正确。用户身份可以是持卡人的用户身份，或者终端的用户身份。
如果用户资料包括智能卡资料，则后台服务器对智能卡资料进行验证。智能卡资料可以包括智能卡的卡类型参数，智能卡标识等。
本步骤可以保证终端和智能卡均为后台服务器所认可的终端和智能卡，而不是非法接入的终端，或者伪造卡或黑名单卡。
步骤603，后台服务器在验证成功时向密钥服务器发送密钥获取请求；
在上述各种验证均通过后，后台服务器向密钥服务器发送密钥获取请求。由于不同智能卡对应的密钥不同，后台服务器向密钥服务器发送用于获取当前 待充值的智能卡对应的密钥的密钥获取请求。该密钥为充值密钥。
步骤604，密钥服务器接收密钥获取请求，根据密钥获取请求生成密钥；
密钥服务器接收密钥获取请求，根据密钥获取请求生成与该智能卡对应密钥。具体来讲，密钥服务器中的加密机可以采用分散算法计算得到与该智能卡对应的充值密钥。
步骤605，密钥服务器向后台服务器反馈密钥；
密钥服务器向后台服务器反馈与该智能卡对应的密钥。
步骤606，后台服务器生成携带有密钥的请求成功响应，并将请求成功响应发送给终端；
对应地，终端接收该请求成功响应。
步骤607，终端从请求成功响应中提取密钥，根据密钥对智能卡进行写卡操作；
终端从请求成功响应中提取对应的密钥，根据该密钥对智能卡进行写卡操作。由于终端是支持NFC技术的终端，所以终端根据密钥通过NFC技术对智能卡进行写卡操作。
如果该密钥为与该智能卡对应的密钥，则智能卡允许该终端的写卡操作；
如果该密钥为与该智能卡不对应的密钥，则智能卡不允许该终端的写卡操作。
步骤608，终端在写卡成功后向后台服务器发送确认请求报文，该确认请求报文携带有校验验证码；
终端在写卡成功后，向后台服务器发送确认请求报文。该确认请求报文中携带有校验验证码，该校验验证码可以根据本次写卡操作过程的数据生成。
步骤609，后台服务器对确认请求报文中携带的校验验证码进行验证，并在验证成功时向终端发送确认成功报文；
后台服务器对确认请求报文中携带的校验验证码等敏感信息进行验证。由于该校验验证码根据终端本次写卡操作过程的数据生成，所以后台服务器根据充值请求中所指示的本次写卡操作和终端本次实际的写卡操作进行比对，如果相同，则认为验证成功，如果不相同，则认为验证不成功。本步骤可以保证充值过程的充值数据不被篡改。
然后，后台服务器向终端发送确认成功报文。
步骤610，终端接收确认成功报文，记录充值成功信息。
终端在接收到系统的确认成功报文之后，记录交易成功信息。
优选地，终端还可以每隔预定批次，将该批次内的交易成功信息进行统计，得到统计信息并上传至后台服务器。
综上所述，本实施例提供的充值方法，通过在支持NFC技术的手机进行充值时，也使用联机处理的方式，由后台服务器对充值请求和确认请求报文进行验证以及由终端根据密钥服务器下发的密钥进行写卡；解决了目前的充值系统安全性较差的问题；达到了每次充值过程，都进行了多步验证，确保充值过程的安全性的效果。
请参考图7，其示出了本发明一个实施例提供的充值系统的结构方框图，所述系统包括：终端720、后台服务器740和密钥服务器760；
所述终端720，用于向所述后台服务器740发送充值请求，所述充值请求携带有用户资料。
所述后台服务器740，用于对所述充值请求中携带的用户资料进行验证，并在验证成功时向所述密钥服务器760发送密钥获取请求。
所述密钥服务器760，用于接收所述密钥获取请求，根据所述密钥获取请求生成密钥，并向所述后台服务器740反馈所述密钥.
所述后台服务器740，用于生成携带有所述密钥的请求成功响应，并将所述请求成功响应发送给所述终端720。
所述终端720，用于从所述请求成功响应中提取所述密钥，根据所述密钥对智能卡进行写卡操作，并在写卡成功后向所述后台服务器740发送确认请求报文，所述确认请求报文携带有校验验证码。
所述后台服务器740，用于对所述确认请求报文中携带的所述校验验证码进行验证，并在验证成功时向所述终端720发送确认成功报文。
所述终端720，用于接收所述确认成功报文，记录充值成功信息。
所述终端720，用于接收用户的第三方充值操作，根据所述第三方充值操作向所述后台服务器740发送所述充值请求；
所述后台服务器740，还用于在验证成功时将所述充值请求转发给第三方系统，在接收到所述第三方系统的成功充值响应后，向所述密钥服务器760发送所述密钥获取请求。
综上所述，本实施例提供的充值系统，通过不论任何充值方式，均采用联机处理，并由后台服务器对充值请求和确认请求报文进行验证以及由终端根据密钥服务器下发的密钥进行写卡；解决了目前的充值系统安全性较差的问题；达到了每次充值过程，都进行了多步验证，确保充值过程的安全性的效果。
在基于图7所示实施例提供的更为优选的实施例中，所述终端720，用于接收用户的线下充值操作，根据所述线下充值操作向所述后台服务器740发送所述充值请求。
在基于图7所示实施例提供的更为优选的实施例中，所述终端720，用于接收用户的圈存充值操作，根据所述圈存充值操作向所述后台服务器740发送所述充值请求。
在基于图7所示实施例提供的更为优选的实施例中，所述终端720为支持近距离通信技术NFC的终端；
所述终端720，用于通过内置应用程序支付充值金额，在成功支付所述充值金额后向所述后台服务器720发送所述充值请求；
所述终端720，还用于根据所述密钥通过所述NFC技术对所述智能卡进行写卡操作。
需要说明的是：上述实施例提供的充值系统在对智能卡进行充值时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的充值系统与充值方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
上述本发明实施例序号仅仅为了描述，不代表实施例的优劣。
请参考图8，其示出了本发明一个实施例提供的终端的结构示意图。该电子设备可以用于实施上述实施例中提供的充值方法。具体来讲：
终端800可以包括RF(Radio Frequency，射频)电路810、包括有一个或一个以上计算机可读存储介质的存储器820、输入单元830、显示单元840、传感器850、音频电路860、短距离通信模块870、包括有一个或者一个以上处理核心的处理器880、以及电源890等部件。本领域技术人员可以理解，图8中示出的终端结构并不构成对终端的限定，可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置。其中：
RF电路810可用于收发信息或通话过程中，信号的接收和发送，特别地，将基站的下行信息接收后，交由一个或者一个以上处理器880处理；另外，将涉及上行的数据发送给基站。通常，RF电路810包括但不限于天线、至少一个放大器、调谐器、一个或多个振荡器、用户身份模块(SIM)卡、收发信机、耦合器、LNA(Low Noise Amplifier，低噪声放大器)、双工器等。此外，RF电路810还可以通过无线通信与网络和其他设备通信。无线通信可以使用任一通信标准或协议，包括但不限于GSM(Global System of Mobile communication，全球移动通讯系统)、GPRS(General Packet Radio Service，通用分组无线服务)、CDMA(Code Division Multiple Access，码分多址)、WCDMA(Wideband Code Division Multiple Access,宽带码分多址)、LTE(Long Term Evolution,长期演进)、电子邮件、SMS(Short Messaging Service，短消息服务)等。
存储器820可用于存储软件程序以及模块，处理器880通过运行存储在存储器820的软件程序以及模块，从而执行各种功能应用以及数据处理。存储器820可主要包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序(比如声音播放功能、图像播放功能等)等；存储数据区可存储根据终端800的使用所创建的数据(比如音频数据、电话本等)等。此外，存储器820可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他易失性固态存储器件。相应地，存储器820还可以包括存储器控制器，以提供处理器880和输入单元830对存储器820的访问。
输入单元830可用于接收输入的数字或字符信息，以及产生与用户设置以及功能控制有关的键盘、鼠标、操作杆、光学或者轨迹球信号输入。具体地，输入单元830可包括触敏表面831以及其他输入设备832。触敏表面831，也 称为触摸显示屏或者触控板，可收集用户在其上或附近的触摸操作(比如用户使用手指、触笔等任何适合的物体或附件在触敏表面831上或在触敏表面831附近的操作)，并根据预先设定的程式驱动相应的连接装置。可选的，触敏表面831可包括触摸检测装置和触摸控制器两个部分。其中，触摸检测装置检测用户的触摸方位，并检测触摸操作带来的信号，将信号传送给触摸控制器；触摸控制器从触摸检测装置上接收触摸信息，并将它转换成触点坐标，再送给处理器880，并能接收处理器880发来的命令并加以执行。此外，可以采用电阻式、电容式、红外线以及表面声波等多种类型实现触敏表面831。除了触敏表面831，输入单元830还可以包括其他输入设备832。具体地，其他输入设备832可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆等中的一种或多种。
显示单元840可用于显示由用户输入的信息或提供给用户的信息以及终端800的各种图形用户接口，这些图形用户接口可以由图形、文本、图标、视频和其任意组合来构成。显示单元840可包括显示面板841，可选的，可以采用LCD(Liquid Crystal Display，液晶显示器)、OLED(Organic Light-Emitting Diode,有机发光二极管)等形式来配置显示面板841。进一步的，触敏表面831可覆盖显示面板841，当触敏表面831检测到在其上或附近的触摸操作后，传送给处理器880以确定触摸事件的类型，随后处理器880根据触摸事件的类型在显示面板841上提供相应的视觉输出。虽然在图8中，触敏表面831与显示面板841是作为两个独立的部件来实现输入和输入功能，但是在某些实施例中，可以将触敏表面831与显示面板841集成而实现输入和输出功能。
终端800还可包括至少一种传感器850，比如光传感器、运动传感器以及其他传感器。具体地，光传感器可包括环境光传感器及接近传感器，其中，环境光传感器可根据环境光线的明暗来调节显示面板841的亮度，接近传感器可在终端800移动到耳边时，关闭显示面板841和/或背光。作为运动传感器的一种，重力加速度传感器可检测各个方向上(一般为三轴)加速度的大小，静止时可检测出重力的大小及方向，可用于识别手机姿态的应用(比如横竖屏切换、相关游戏、磁力计姿态校准)、振动识别相关功能(比如计步器、敲击)等；至于终端800还可配置的陀螺仪、气压计、湿度计、温度计、红外线传感 器等其他传感器，在此不再赘述。
音频电路860、扬声器861、传声器862可提供用户与终端800之间的音频接口。音频电路860可将接收到的音频数据转换后的电信号，传输到扬声器861，由扬声器861转换为声音信号输出；另一方面，传声器862将收集的声音信号转换为电信号，由音频电路860接收后转换为音频数据，再将音频数据输出处理器180处理后，经RF电路18以发送给比如另一终端，或者将音频数据输出至存储器120以便进一步处理。音频电路160还可能包括耳塞插孔，以提供外设耳机与终端800的通信。
短距离通信模块170可以包括WiFi(wireless fidelity，无线保真)技术和/或NFC技术和/或蓝牙技术和/或红外技术，终端800通过短距离通信模块170可以帮助用户收发电子邮件、浏览网页和访问流式媒体等，它为用户提供了无线的宽带互联网访问及近距离通信，比如在本发明实施例中用于电子卡片的读写。
处理器880是终端800的控制中心，利用各种接口和线路连接整个手机的各个部分，通过运行或执行存储在存储器820内的软件程序和/或模块，以及调用存储在存储器820内的数据，执行终端800的各种功能和处理数据，从而对手机进行整体监控。可选的，处理器880可包括一个或多个处理核心；优选的，处理器880可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序等，调制解调处理器主要处理无线通信。可以理解的是，上述调制解调处理器也可以不集成到处理器880中。
终端800还包括给各个部件供电的电源890(比如电池)，优选的，电源可以通过电源管理系统与处理器880逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。电源890还可以包括一个或一个以上的直流或交流电源、再充电系统、电源故障检测电路、电源转换器或者逆变器、电源状态指示器等任意组件。
尽管未示出，终端800还可以包括摄像头、蓝牙模块等，在此不再赘述。具体在本实施例中，电子设备的显示单元是触摸屏显示器，电子设备还包括有存储器，以及一个或者一个以上的程序，其中一个或者一个以上程序存储于存储器中，且经配置以由一个或者一个以上处理器执行述一个或者一个以上程序 包含用于执行如上所述的充值方法。
请参考图9，其示出了本发明一个实施例提供的服务器的结构示意图。一个或者多个该服务器可以组成本发明实施例中的后台服务器或者密钥服务器。所述服务器900包括中央处理单元(CPU)901、包括随机存取存储器(RAM)902和只读存储器(ROM)903的系统存储器904，以及连接系统存储器904和中央处理单元901的系统总线905。所述服务器900还包括帮助计算机内的各个器件之间传输信息的基本输入/输出系统(I/O系统)906，和用于存储操作系统913、应用程序914和其他程序模块915的大容量存储设备907。
所述基本输入/输出系统906包括有用于显示信息的显示器908和用于用户输入信息的诸如鼠标、键盘之类的输入设备909。其中所述显示器908和输入设备909都通过连接到系统总线905的输入输出控制器910连接到中央处理单元901。所述基本输入/输出系统906还可以包括输入输出控制器910以用于接收和处理来自键盘、鼠标、或电子触控笔等多个其他设备的输入。类似地，输入输出控制器910还提供输出到显示屏、打印机或其他类型的输出设备。
所述大容量存储设备907通过连接到系统总线905的大容量存储控制器(未示出)连接到中央处理单元901。所述大容量存储设备907及其相关联的计算机可读介质为服务器900提供非易失性存储。也就是说，所述大容量存储设备907可以包括诸如硬盘或者CD-ROM驱动器之类的计算机可读介质(未示出)。
不失一般性，所述计算机可读介质可以包括计算机存储介质和通信介质。计算机存储介质包括以用于存储诸如计算机可读指令、数据结构、程序模块或其他数据等信息的任何方法或技术实现的易失性和非易失性、可移动和不可移动介质。计算机存储介质包括RAM、ROM、EPROM、EEPROM、闪存或其他固态存储其技术，CD-ROM、DVD或其他光学存储、磁带盒、磁带、磁盘存储或其他磁性存储设备。当然，本领域技术人员可知所述计算机存储介质不局限于上述几种。上述的系统存储器904和大容量存储设备907可以统称为存储器。
根据本发明的各种实施例，所述服务器900还可以通过诸如因特网等网络 连接到网络上的远程计算机运行。也即服务器900可以通过连接在所述系统总线905上的网络接口单元911连接到网络912，或者说，也可以使用网络接口单元99来连接到其他类型的网络或远程计算机系统(未示出)。
所述存储器还包括一个或者一个以上的程序，所述一个或者一个以上程序存储于存储器中，所述一个或者一个以上程序包含用于进行本发明实施例提供的充值方法的指令。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (4)

  1. 一种充值系统，其特征在于，所述系统包括：终端、后台服务器和密钥服务器；
    所述终端，用于向所述后台服务器发送充值请求，所述充值请求携带有用户资料；
    所述后台服务器，用于对所述充值请求中携带的用户资料进行验证，并在验证成功时向所述密钥服务器发送密钥获取请求；
    所述密钥服务器，用于接收所述密钥获取请求，根据所述密钥获取请求生成密钥，并向所述后台服务器反馈所述密钥；
    所述后台服务器，用于生成携带有所述密钥的请求成功响应，并将所述请求成功响应发送给所述终端；
    所述终端，用于从所述请求成功响应中提取所述密钥，根据所述密钥对智能卡进行写卡操作，并在写卡成功后向所述后台服务器发送确认请求报文，所述确认请求报文携带有校验验证码；
    所述后台服务器，用于对所述确认请求报文中携带的所述校验验证码进行验证，并在验证成功时向所述终端发送确认成功报文；
    所述终端，用于接收所述确认成功报文，记录充值成功信息；
    其中，所述终端，用于接收用户的第三方充值操作，根据所述第三方充值操作向所述后台服务器发送所述充值请求；
    所述后台服务器，还用于在验证成功时将所述充值请求转发给第三方系统，在接收到所述第三方系统的成功充值响应后，向所述密钥服务器发送所述密钥获取请求。
  2. 根据权利要求1所述的系统，其特征在于，
    所述终端，用于接收用户的线下充值操作，根据所述线下充值操作向所述后台服务器发送所述充值请求。
  3. 根据权利要求1所述的系统，其特征在于，
    所述终端，用于接收用户的圈存充值操作，根据所述圈存充值操作向所述 后台服务器发送所述充值请求。
  4. 根据权利要求1所述的系统，其特征在于，所述终端为支持近距离通信技术NFC的终端；
    所述终端，用于通过内置应用程序支付充值金额，在成功支付所述充值金额后向所述后台服务器发送所述充值请求；
    所述终端，还用于根据所述密钥通过所述NFC技术对所述智能卡进行写卡操作。
PCT/CN2016/077705 2016-03-29 2016-03-29 充值系统 WO2017166068A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/077705 WO2017166068A1 (zh) 2016-03-29 2016-03-29 充值系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/077705 WO2017166068A1 (zh) 2016-03-29 2016-03-29 充值系统

Publications (1)

Publication Number Publication Date
WO2017166068A1 true WO2017166068A1 (zh) 2017-10-05

Family

ID=59963307

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/077705 WO2017166068A1 (zh) 2016-03-29 2016-03-29 充值系统

Country Status (1)

Country Link
WO (1) WO2017166068A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159074A (zh) * 2007-11-16 2008-04-09 北京飞天诚信科技有限公司 一种自助充值的系统和方法
CN103714625A (zh) * 2013-12-20 2014-04-09 北京握奇数据系统有限公司 一种智能卡充值方法及系统
CN104574652A (zh) * 2013-10-14 2015-04-29 国家电网公司 Ic卡排污数据增加、扣减的方法和ic卡
CN105373919A (zh) * 2015-10-27 2016-03-02 熊文俊 基于远近场数据交互的用户身份安全认证设备及认证方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101159074A (zh) * 2007-11-16 2008-04-09 北京飞天诚信科技有限公司 一种自助充值的系统和方法
CN104574652A (zh) * 2013-10-14 2015-04-29 国家电网公司 Ic卡排污数据增加、扣减的方法和ic卡
CN103714625A (zh) * 2013-12-20 2014-04-09 北京握奇数据系统有限公司 一种智能卡充值方法及系统
CN105373919A (zh) * 2015-10-27 2016-03-02 熊文俊 基于远近场数据交互的用户身份安全认证设备及认证方法

Similar Documents

Publication Publication Date Title
US11488234B2 (en) Method, apparatus, and system for processing order information
CN104572325B (zh) 一种递进式响应表单处理方法和终端
TWI529560B (zh) 安全平台系統、用於電子裝置上之憑證之安全佈建之方法、及相關之電子裝置及非暫時性電腦可讀媒體
KR101971329B1 (ko) 전자 디바이스 상의 크리덴셜의 프로비저닝 및 인증
TWI554048B (zh) 使用一電子裝置之低功率模式之近場通信管理
CN105706131B (zh) 使用通过已验证的信道传送的密码在电子设备上提供凭据
US10762542B2 (en) Item transfer apparatus, system and method
WO2018019261A1 (zh) 资源转移方法及装置
EP2866188A1 (en) Method, terminal apparatus and server for transmitting NFC data
US20160301530A1 (en) Sensitive operation verification method, apparatus, and system
CN104392350A (zh) 一种虚拟资源数据的处理方法、装置和系统
CN106603389B (zh) 虚拟票据转移方法及装置
WO2017166170A1 (zh) 中央清分结算方法
CN104899488A (zh) 数值转移方法及装置
WO2017166060A1 (zh) 充值方法
WO2015101254A1 (zh) 一种信息交互的方法、装置及系统
WO2017166174A1 (zh) 中央清分结算方法
WO2017166067A1 (zh) 充值系统
WO2017166056A1 (zh) 充值方法
WO2017166051A1 (zh) 充值方法
CN108122151B (zh) 图形码显示方法、图形码处理方法、装置及系统
WO2017166061A1 (zh) 充值系统
WO2017166068A1 (zh) 充值系统
WO2017166069A1 (zh) 充值系统
WO2017166059A1 (zh) 充值方法

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16895849

Country of ref document: EP

Kind code of ref document: A1

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20.03.2019)

122 Ep: pct application non-entry in european phase

Ref document number: 16895849

Country of ref document: EP

Kind code of ref document: A1