WO2017166060A1

WO2017166060A1 - Refill method

Info

Publication number: WO2017166060A1
Application number: PCT/CN2016/077693
Authority: WO
Inventors: 李昕光
Original assignee: 李昕光
Priority date: 2016-03-29
Filing date: 2016-03-29
Publication date: 2017-10-05

Abstract

A refill method, related to the field of data processing, comprising: a terminal receives a third party refill operation of a user and transmits a refill request to a background server on the basis of the third party refill operation (501); the background server verifies the refill request (502), forwards same to a third party system when the verification is successful (503), and, when a refill successful response is received from the third party system, transmits a key acquisition request to a key server (504); the key server receives the key acquisition request and generates a key (505); the key server feeds the key back to the background server (506); the background server generates a request successful response carrying the key and transmits the request successful response to the terminal (507); the terminal extracts the key from the request successful response, performs a card writing operation with respect to a smart card on the basis of the key (508), and transmits to the background server a confirmation request packet carrying a verification code when the card writing operation is successful (509); the background server verifies the verification code in the confirmation request packet and transmits a confirmation successful packet to the terminal when the verification is successful (510); and the terminal receives the confirmation successful packet and records refill successful information (511). The method employs online processing irrespective of refill mode, the refill request and the confirmation request packet are verified by the background server and the card writing is performed by the terminal on the basis of the key issued by the key server, thus solving the problem of poor security with a current refill system, and achieving the effect of ensuring refill security by means of multistep verification in each refill process.

Description

Recharge method

Technical field

The present invention relates to the field of data processing, and in particular, to a charging method.

Background technique

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. The current recharge system can recharge smart cards through offline recharge, online recharge, and self-service cash terminals.

In the process of implementing the present invention, 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.

Summary of the invention

In order to solve the problem that the current recharge system has poor security, the embodiment of the present invention provides a recharge method. The technical solution is as follows:

According to a first aspect of the embodiments of the present invention, a refill system is provided, the 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 confirmation success message and record the refill success information.

In a first possible implementation manner of the first aspect, 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.

In a second possible implementation manner of the first aspect, 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.

In a third possible implementation manner of the first aspect, the terminal is configured to receive a third-party recharge operation of the user, and send the refill 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. .

In a fourth possible implementation manner of the first aspect, the terminal is a terminal that supports a short-range communication technology (NFC);

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.

According to a second aspect of the embodiments of the present invention, a charging method is provided, the 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;

Receiving, by the key server, the key acquisition request, generating a key according to the key acquisition request, and feeding back the key to the background server;

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;

Receiving, by the terminal, the acknowledged success message, and recording the refill success information;

The terminal sends a refill request to the background server, including:

Receiving, by the terminal, a third-party recharge operation of the user, and sending the refill request to the background server according to the third-party recharge operation;

In a first possible implementation manner of the second aspect, 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.

In a second possible implementation manner of the second aspect, 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.

In a third possible implementation manner of the second aspect, the terminal sends a recharge request to the background server, including:

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 beneficial effects brought by the technical solutions provided by the embodiments of the present invention are:

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.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. Other drawings may also be obtained from those of ordinary skill in the art in light of the inventive work.

1 is a schematic structural view of an implementation environment involved in various embodiments of the present invention;

2 is a flowchart of a method for charging a method according to an embodiment of the present invention;

3 is a flowchart of a method for charging a method according to another embodiment of the present invention;

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.

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.

detailed description

The embodiments of the present invention will be further described in detail below with reference to the accompanying drawings.

Please refer to FIG. 1, which 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. The terminal 120 can be a mobile phone or a laptop Portable computers and desktop computers, etc. For example, the terminal 120 may be a mobile terminal supporting NFC (Near Field Communication) technology, and has the capability of reading and writing an external smart card 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.

Please refer to FIG. 2, which 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 terminal sends a refill request to the background server, including:

In summary, 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.

Since 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:

1. Offline recharge method;

2. On-line recharge method;

3. The method of recharging through a third-party system;

4. Recharge through NFC-enabled mobile phones.

These methods are described in detail below using different embodiments.

Please refer to FIG. 3, which 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;

When the terminal is a self-service cash refill terminal, the offline recharge operation may be an operation in which the user puts the recharged cash into the self-service cash refill terminal;

When the terminal is a transfer 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.

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.

Correspondingly, 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.

After receiving the refill request, the background server extracts the user data carried in the refill request. The user profile is then verified.

If the user profile includes the underlying data, the background server verifies the underlying data to verify that the underlying data is correct.

If the user profile includes the user's identity, 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.

If the user profile includes smart card data, 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.

After the above various verifications are passed, 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. Specifically, 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.

Correspondingly, 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.

If the key is a key corresponding to the smart card, the smart card allows the card to be operated by the terminal;

If the key is a key that does not correspond to the smart card, 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;

After the terminal successfully writes the card, the terminal sends a confirmation request message to the background server. 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.

Then, 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.

After receiving the confirmation message of the system, the terminal records the transaction success information.

Preferably, 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.

In summary, 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.

Please refer to FIG. 4, which 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. 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.

Step 402: The background server verifies the user data carried in the refill request.

In this step, 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;

Step 404: The key server receives the key acquisition request, and generates a key according to the key acquisition request.

Step 405: The key server feeds back the key 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.

Correspondingly, 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;

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.

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;

Step 410: The terminal receives the confirmation success message and records the refill success information.

In summary, 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.

Please refer to FIG. 5, which 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.

Step 502: The background server verifies the user data carried in the refill request.

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. When 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.

Step 505: The key server receives the key acquisition request, and generates a key according to the key acquisition request.

Step 506, the key server feeds back the key 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.

Correspondingly, 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;

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;

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;

In step 511, the terminal receives the confirmation success message and records the refill success information.

In summary, the recharging method provided in this embodiment is performed by the background server to verify the refill request and the acknowledgment request message and the terminal is 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.

Please refer to FIG. 6, which 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 (APP) 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. 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.

Step 602: The background server verifies the user data carried in the refill request.

Step 603: The background server sends a key acquisition request to the key server when the verification is successful.

Step 604: The key server receives a key acquisition request, and generates a key according to the key acquisition request.

Step 605: The key server feeds back the key 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.

Correspondingly, 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.

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;

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;

In step 610, the terminal receives the confirmation success message and records the refill success information.

In summary, 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.

Please refer to FIG. 7, which 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 according to the key Performing a card writing operation on the smart card, and sending 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.

In summary, 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.

In a more preferred embodiment provided by the embodiment shown in FIG. 7, 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.

In a more preferred embodiment provided by the embodiment shown in FIG. 7, 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.

In a more preferred embodiment provided by the embodiment shown in FIG. 7, the terminal 720 is configured to receive a third-party recharge operation of the user, and send the recharge to the background server 740 according to the third-party recharge operation. request;

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.

In a more preferred embodiment provided based on the embodiment shown in FIG. 7, 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.

It should be noted that the recharge system provided by the foregoing embodiment only recharges the smart card. The division of each functional module is illustrated by an example. In an actual application, the function allocation may be completed by different functional modules according to requirements, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. . In addition, 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.

The serial numbers of the embodiments of the present invention are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Please refer to FIG. 8 , which 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. It will be understood by those skilled in the art that the terminal structure shown in 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. . Generally, 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. In addition, 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.

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.); The stored data area can store data (such as audio data, phone book, etc.) created according to the use of the terminal 800, and the like. Moreover, 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. In particular, input unit 830 can include touch-sensitive surface 831 as well as other input devices 832. Touch-sensitive surface 831, also referred to as a touch display or trackpad, can collect touch operations on or near the user (eg, the user uses a finger, stylus, etc., on any suitable object or accessory on touch-sensitive surface 831 or The operation near the touch-sensitive surface 831) and driving the corresponding connecting device according to a preset program. Alternatively, the touch-sensitive surface 831 can include two portions of a touch detection device and a touch controller. Wherein, 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. In addition, the touch sensitive surface 831 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch-sensitive surface 831, the input unit 830 can also include other input devices 832. In particular, 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. Alternatively, 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. Further, 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. Although in FIG. 8, 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. Specifically, 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. As a kind of motion sensor, 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. It can be used to identify the gesture of the mobile phone (such as horizontal and vertical screen switching, related Game, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for the terminal 800 can also be configured with gyroscopes, barometers, hygrometers, thermometers, infrared sensors and other sensors, here Let me repeat.

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. Optionally, 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 source 890 (such as a battery) that supplies power to the various components, preferably, a power source. It can be logically connected to the processor 880 through a power management system to manage functions such as charging, discharging, and power management through a 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.

Although not shown, the terminal 800 may further include a camera, a Bluetooth module, and the like, and details are not described herein again. Specifically, in this embodiment, 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 of the programs included to perform the refill method as described above.

Please refer to FIG. 9, which is a schematic structural diagram of a server according to an embodiment of the present invention. One or more of the servers may constitute a background server or a key server in the 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. Device 907.

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.

Without loss of generality, 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. Of course, those skilled in the art will appreciate that the computer storage medium is not limited to the above. The system memory 904 and mass storage device 907 described above may be collectively referred to as a memory.

According to various embodiments of the present invention, the server 900 may also be operated by a remote computer connected to the network through a network such as the Internet. 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.

The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are within the spirit and scope of the present invention, should be included in the protection of the present invention. Within the scope.

Claims

A method for recharging, characterized in that the method comprises:

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;

Receiving, by the key server, the key acquisition request, generating a key according to the key acquisition request, and feeding back the key to the background server;

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;

Receiving, by the terminal, the acknowledged success message, and recording the refill success information;

The terminal sends a refill request to the background server, including:

Receiving, by the terminal, a third-party recharge operation of the user, and sending the refill 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 method according to claim 1, wherein the terminal sends a refill 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 method according to claim 1, wherein the terminal sends a refill 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 method according to claim 1, wherein the terminal sends a refill request to the background server, including:

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.