Patent Grant
11640605
The present disclosure relates to Internet communications and to a method, server and storage medium for verifying a transaction using a smart card.
This section provides background information related to the present disclosure which is not necessarily prior art.
With the rapid development of mobile Internet technologies, mobile terminals have become increasingly more useful. For example, as with most mobile terminals, a mobile terminal may include a function for resource processing. A user may process user resource information (e.g., account balance or payment account information) of two users by using the function of resource processing of the mobile terminal.
The two users include a first user and a second user, and a process in which the mobile terminal processes user resource information of the first user and user resource information of the second user is as follows. The first user turns on a first mobile phone and opens an application associated with the resource processing function (e.g., an online payment function), and the application then generates a two-dimensional code and displays the two-dimensional code on the first mobile phone, where the two-dimensional code includes an openID. A second terminal associated with a merchant scans the two-dimensional code, acquires the openID from the two-dimensional code, and sends the openID and amount transfer information to a server, where the amount transfer information includes user identifier information corresponding to the merchant and a resource amount. The server acquires user identifier information corresponding to the first user according to the openID, acquires user resource information of the first user according to the user identifier information, acquires the user resource information of the second user according to the user identifier information corresponding to the second user, subtracts the resource amount from a first amount included in the user resource information of the first user, and adds the resource amount to a second amount included in the user resource information of the second user. As such, processing of the user resource information of the first user and the user resource information of the second user is performed to complete a transaction.
This section provides a general summary of the disclosure, and is not a comprehensive disclosure of its full scope or all of its features.
In various embodiments, a method of verifying a transaction using a smart card includes receiving a transaction request from a first terminal to perform a transaction with a user of the smart card, where the transaction request includes card identification information and encrypted card data extracted by the first terminal from the smart card, and transaction information and determining a respective user account linked to the card identification information; performing a first verification process to authenticate the smart card, including: verifying that the smart card possesses a correct decryption key corresponding to the card identification information; performing a second verification process to authenticate the smart card, including: verifying that the encrypted card data extracted from the smart card encodes stored card data corresponding to the respective user account linked to the card identification information, and, in accordance with successful completion of the first and the second verification processes, processing the transaction in accordance with the transaction information.
In various embodiments, a server includes one or more processors and memory storing one or more programs for execution by the one or more processors, the one or more programs include instructions for performing the operations of any of the methods described herein. In various embodiments, a non-transitory computer readable storage medium storing one or more programs, the one or more programs comprising instructions, which, when executed by a server with one or more processors, cause the server to perform operations of any of the methods described herein.
Further areas of applicability will become apparent from the description provided herein. The description and various examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure.
The drawings described herein are for illustrative purposes only of selected embodiments and not all possible implementations, and are not intended to limit the scope of the present disclosure.
The aforementioned features and benefits of the disclosed technology as well as additional features and benefits thereof will be more clearly understood hereinafter as a result of a detailed description of various embodiments when taken in conjunction with the drawings.
To describe the embodiments of the present disclosed technology or in the prior art more clearly, the following briefly introduces the accompanying drawings necessary for describing the embodiments or the prior art. The accompanying drawings in the following description show various embodiments of the present disclosed technology, and persons of ordinary skill in the art may still derive other drawings from these accompanying drawings without creative efforts.
Corresponding reference numerals indicate corresponding parts throughout the several views of the drawings.
Example embodiments will now be described more fully with reference to the accompanying drawings.
At least the following challenges exist in the prior art. It takes a significant amount of time to start the application and generate the two-dimensional code, leading to a long lapse of time which may be tens of seconds or longer between when the first user turns on the first mobile phone to the scanning of the displayed two-dimensional code by the merchant. Therefore, the prior art is unsuitable in terms of processing efficiency. The techniques described in the present disclosure provides a streamlined transaction process using inexpensive, simple, and lightweight information carriers having some limited information processing capabilities, such as an information carrier in the form of a smart card or label, such that secure and convenient payment transactions can be accomplished without requiring cumbersome code scanning through using a mobile phone camera. The technique described herein can also be implemented using more sophisticated devices, such as a smart watch or other smart accessories worn by users.
Reference will now be made in detail to various embodiments, examples of which are illustrated in the accompanying drawings. In the following detailed description, numerous details are set forth in order to provide a thorough understanding of the subject matter presented herein. It will be apparent to one skilled in the art that the subject matter may be practiced without these details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
This disclosure describes the technical methods in the various embodiments with reference to the accompanying drawings in the embodiments of the present disclosure. The described various embodiments are merely a portion of the various embodiments of the present disclosure. All other embodiments obtained by persons of ordinary skill in the art based on the various embodiments of the present disclosure without creative efforts shall fall within the protection scope of the present disclosure.
As shown in
In various embodiments, server-side module 106 includes one or more processors 112, transactions database 114, profiles database 116, an I/O interface to one or more clients 118, and an I/O interface to one or more external services 120. I/O interface to one or more clients 118 facilitates the client-facing input and output processing for server-side module 106. In various embodiments, processor(s) 112 performs at least a first and second verification processes to authenticate a smart card 130 and process a transaction between a user of smart card 130 and a first terminal in accordance with a determination that the first and second authentication processes are successful. Transactions database 114 stores transaction information for processed and failed transactions, and profiles database 116 stores a plurality of user profiles for user accounts registered in the transaction processing application, where a respective user profile includes one or more of account credentials for a respective user account, payment information for the respective user account, and card information for a smart card linked to the respective user account (e.g., card identification information, a respective encryption key, a respective decryption key, and card data (in encrypted to decrypted form)). I/O interface to one or more external services 120 facilitates communications with one or more external services 122 (e.g., banking services, online shopping services, account settlement services, application hosting, web hosting, or cloud-based services such as video and/or image hosting and storage websites).
Examples of client device 104 include, but are not limited to, a handheld computer, a wearable computing device, a personal digital assistant (PDA), a tablet computer, a laptop computer, a desktop computer, a cellular telephone, a smart phone, an enhanced general packet radio service (EGPRS) mobile phone, a media player, a navigation device, a game console, a television, a remote control, a point-of-sale (POS) terminal, vehicle-mounted computer, an ebook reader, or a combination of any two or more of these data processing devices or other data processing devices.
Examples of one or more networks 110 include local area networks (LAN) and wide area networks (WAN) such as the Internet. One or more networks 110 are, optionally, implemented using any known network protocol, including various wired or wireless protocols, such as Ethernet, Universal Serial Bus (USB), FIREWIRE, Long Term Evolution (LTE), Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), code division multiple access (CDMA), time division multiple access (TDMA), Bluetooth, Wi-Fi, voice over Internet Protocol (VoIP), Wi-MAX, or any other suitable communication protocol.
Server system 108 is implemented on one or more standalone data processing apparatuses or a distributed network of computers. In various embodiments, server system 108 also employs various virtual devices and/or services of third party service providers (e.g., third-party cloud service providers) to provide the underlying computing resources and/or infrastructure resources of server system 108. In various embodiments, server system 108 includes, but is not limited to, a handheld computer, a tablet computer, a laptop computer, a desktop computer, or a combination of any two or more of these data processing devices or other data processing devices.
Server-client environment 100 shown in
operating system 210 including procedures for handling various basic system services and for performing hardware dependent tasks;
network communication module 212 for connecting server system 108 to other computing devices (e.g., client devices 104 and external service(s) 122) connected to one or more networks 110 via one or more network interfaces 204 (wired or wireless);
server-side module 106, which provides server-side data processing and functionalities for the transaction processing application, including but not limited to:
request handling module 222 for receiving a transaction request from a client device 104 (e.g., a point-of-sale (POS) terminal) to perform a transaction with a user of the smart card, where the transaction request includes card identification information and encrypted card data extracted from the smart card, and transaction information;
account determination module 224 for identifying a user account registered with the transaction processing application that is bound to the card identification information of the smart card;
first verification module 226 for performing a first verification process to authenticate the smart card by verifying that the smart card possesses a correct decryption key corresponding to the card identification information;
second verification module 228 for performing a second verification process to authenticate the smart card by verifying that the encrypted card data extracted from the smart card encodes stored card data corresponding to the respective user account linked to the card identification information;
third verification module 230 for performing a third verification process in accordance with a determination that the transaction information is associated with a security risk;
transaction processing module 232 for processing the transaction corresponding to the transaction request in accordance with a determination that the first verification process performed by first verification module 226 and the second verification process performed by second verification module 228 are successful;
transaction failure module 234 for locking-out the user account corresponding to the card identification information from performing subsequent transactions and sending a notification to an electronic device linked to the user account indicating failure in accordance with a determination that either the first verification process performed by first verification module 226 or the second verification process performed by second verification module 228 are unsuccessful;
notification providing module 236 for providing a notification to the client device corresponding to the transaction request indicating successful processing of the transaction or failure of the first verification process or the second verification process;
binding module 238 for performing a registration process whereby a user account in the transaction processing application is linked to card identification information corresponding to a smart card; and
updating module 240 for updating the encrypted card data stored by a smart card;
server data 250 storing data for the transaction processing application, including but not limited to:
transactions database 114 storing transaction information for processed and failed transactions; and
profiles database 116 storing a plurality of user profiles 252 for user accounts registered in the transaction processing application, where a respective user profile 252-A includes one or more of: account credentials 262 for a respective user account, payment information 264 for the respective user account, and card information for a smart card linked to the respective user account (e.g., card identification information 254, a respective encryption key 256, a respective decryption key 258, and card data 260).
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 206, optionally, stores a subset of the modules and data structures identified above. Furthermore, memory 206, optionally, stores additional modules and data structures not described above.
operating system 316 including procedures for handling various basic system services and for performing hardware dependent tasks;
network communication module 318 for connecting client device 104 to other computing devices (e.g., server system 108 and external service(s) 122) connected to one or more networks 110 via one or more network interfaces 304 (wired or wireless); presentation module 320 for enabling presentation of information (e.g., a user interface for application(s) 326 or the transaction processing application, widgets, websites and web pages thereof, and/or games, audio and/or video content, text, etc.) at client device 104 via one or more output devices 312 (e.g., displays, speakers, etc.) associated with user interface 310;
input processing module 322 for detecting one or more user inputs or interactions from one of the one or more input devices 314 and interpreting the detected input or interaction;
web browser module 324 for navigating, requesting (e.g., via HTTP), and displaying websites and web pages thereof;
one or more applications 326 for execution by client device 104 (e.g., games, application marketplaces, payment platforms, and/or other web or non-web based applications);
client-side module 102, which provides client-side data processing and functionalities for the transaction processing application, including but not limited to:
image capture module 332 for capturing images with one or more cameras, scanners, or photo sensor units 315, for example, an image of a graphic code 132 (e.g., a QR code) on a smart card 130 (as shown in
extracting module 334 for extracting card identification information and card data encoded in graphic code 132 of smart card 130 (as shown in
requesting module 336 for sending a transaction request to server system 108 including card identification information and encrypted card data extracted from smart card 130 (as shown in
relaying module 338 for relaying information from server system 108 to smart card 130 (as shown in
obtaining module 340 for obtaining a notification from server system 108 indicating successful processing of the transaction or failure of the first verification process or the second verification process;
verification module (optional) for performing at least the first verification process on behalf of the user to determine whether the smart card possesses a correct decryption key, including, for example, receiving the encryption key from the server, generating the random string, encrypting the random string, sending the smart string to the smart card, receiving decrypted string from the smart card, and verifying whether the received decrypted string matches the random string. If the smart passes the first verification process, the verification module lets the server proceed with the second verification process; and
client data 350 storing data associated with the transaction processing application, including, but is not limited to transaction data 352 storing information related with successful and failed transactions such as transaction amount, transaction time, goods and/or services associated with the transaction, card identification corresponding to the smart card that initiated the transaction, and/or the like.
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, modules or data structures, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 306, optionally, stores a subset of the modules and data structures identified above. Further, memory 306, optionally, stores additional modules and data structures not described above.
In various embodiments, at least some of the functions of server system 108 are performed by client device 104, and the corresponding sub-modules of these functions may be located within client device 104 rather than server system 108. In various embodiments, at least some of the functions of client device 104 are performed by server system 108, and the corresponding sub-modules of these functions may be located within server system 108 rather than client device 104. Client device 104 and server system 108 shown in
operating logic 416 including procedures for handling various basic system services and for performing hardware dependent tasks;
communication module 418 for obtaining data from or sending data to other computing devices such as client device 104;
(optionally) encoding module 420 for encoding card identification information and card data into a graphic code (e.g., a QR code such as graphic code 132 in
(optionally) presentation module 422 for displaying the graphic code (e.g., graphic code 132 in
data 430 storing data, including but not limited to:
card identification information 432 corresponding to a serial number for smart card 130;
decryption key 434 for responding to authentication challenges; and
encrypted card data 436 for verifying the authenticity of smart card 130.
Each of the above identified elements may be stored in one or more of the previously mentioned memory devices, and corresponds to a set of instructions for performing a function described above. The above identified modules or programs (i.e., sets of instructions) need not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or otherwise re-arranged in various implementations. In some implementations, memory 406, optionally, stores a subset of the modules and data structures identified above. Further, memory 406, optionally, stores additional modules and data structures not described above.
In various embodiments, the smart card 130 does not include a processor, and the processing functions may be accomplished through specially designed integrated circuits. The input and output interfaces of the smart card 130 may be designed to communicate with a card reading device (e.g., a client device 108 or a kiosk) through one or more wired and/or wireless transmission lines/ports. In various embodiments, when static graphic code are used to encode the card identification information, the graphic code may be printed on the surface of the smart card and scanned by a card reading device by a camera or barcode scanner. Other ways of implementing the various functions of the smart card are possible. Although a “smart card” is used in the present disclosure to describe the verification techniques, it would be apparent to a person skilled in the art that the “smart card” may adopt other suitable formats, shapes, and sizes, in actual use.
In various embodiments, data processing for a transaction processing application is implemented in client-server environment 100 (
The server receives (502) a transaction request including transaction information, card identifier information, and card data from a first terminal. For example, the transaction information includes a resource amount for the transaction, goods and/or services associated with the transaction, time/date and location of the transaction, and identifier information associated with the first terminal (e.g., a merchant's point-of-sale (POS) terminal).
The server authenticates (504) the identity of a first user according to the card identifier information and the card data.
If the authentication succeeds, the server acquires (506) user resource information of the first user according to the card identifier information, and acquires user resource information of a second user of the first terminal.
The server processes (508) the transaction against the user resource information of the first user and the user resource information of the second user according to a resource amount indicated by the transaction information. For example, a first payment account corresponding to the user resource information of the first user is debited according to the resource amount, and a second payment corresponding to the user resource information of the second user is credited according to the resource amount.
In method 500, the first terminal directly acquires card identifier information and card data from a smart card, and the server processes user resource information of a first user associated with the smart card and user resource information of a second user associated with the first terminal. It takes a short time for the first terminal to acquire the card identifier information and card data from the smart card, thereby improving efficiency of processing user resource information.
It should be understood that the particular order in which the operations in
In various embodiments, data processing for a transaction processing application is implemented in client-server environment 100 (
A second terminal scans (602) a graphic code of a smart card to acquire information from the graphic code. In various embodiments, a smart card includes a graphic code (e.g., a barcode, a two-dimensional QR code, or the like). In various embodiments, the graphic code is set by the manufacturer and is a unique graphic code. For example, a first user purchases the smart card and scans the graphic code on the smart card using a second terminal (e.g., the first user's mobile device) by capturing an image of the graphic code. In various embodiments, the smart card includes smart card includes card identifier information, card data, and a decryption key. In various embodiments, the card data is encrypted data and may be any data (e.g., unique data). In various embodiments, each smart card corresponds to a unique set of keys: an encryption key and a decryption key. In various embodiments, the card data is encrypted by using the encryption key corresponding to the smart card. In various embodiments, the graphic code is encoded with the card identifier information and the card data. In various embodiments, the server associates the card identifier information with a stored un-encrypted card data, the encryption key, and the decryption key.
The second terminal sends (604) a binding request message to the server. In various embodiments, the binding request message includes the card identifier information from the smart card and an indication of a user account for the first user of the second terminal.
The server receives (606) the binding request message and binds the user account corresponding to the first user of the second terminal to the card identifier information according to the binding request message. As such, the smart card is bound to the user account corresponding to the first user of the second terminal.
The first terminal reads (608) the smart card, and acquires card identifier information and card data from the smart card. For example, if the first user intends to perform a transaction with a merchant associated with the first terminal (e.g., a POS terminal), the first user provides the smart card to the first terminal for image capture of the graphic code. The first terminal reads the smart card, and extracts the card identifier information and card data from the smart card.
In various embodiments, the smart card is verified by sending a key acquisition request message to the server, where the key acquisition request message includes the card identifier information for the smart card. Thereafter, the server identifies a user account bound to the card identifier information and acquires an encryption key corresponding to the user account. The server sends the acquired encryption key to the first terminal. The first terminal verifies the smart card according to the encryption key, and if the verification succeeds, proceeds with the transaction. In various embodiments, the first terminal verifies the smart card in the following manner: The first terminal generates a random number, uses the encryption key to encrypt the random number to obtain an encrypted ciphertext, and sends the encrypted ciphertext to the smart card. The smart card decrypts the encrypted ciphertext by using a decryption key stored in the smart card to obtain decrypted data, and sends the decrypted data to the first terminal. The first terminal compares the decrypted data and the random number; if the two are the same, the verification of the smart card by the first terminal succeeds; if the two are different, the verification of the smart card by the first terminal fails. If the verification of the smart card by the first terminal fails, the first user and the second user are notified of the failure. The verification of the smart card by the first terminal can prevent loss to a user caused by a lawbreaker counterfeiting a smart card, thereby improving security. In various embodiments, the server may verify the smart card in the above manner using the first terminal to relay the ciphertext and decrypted data.
The first terminal sends (610) a transaction request to the server, and the transaction request includes a transaction amount and the acquired card information (i.e., the card identifier information and card data). In various embodiments, the first terminal packs transaction amount and the acquired card information into a data packet, and sends the data packet to an intermediate server corresponding to the second user (e.g., an inventory and transaction control server). In various embodiments, the intermediate server adds information, such as transaction description information and a processing time of the transaction, to the data packet, and then sends the data packet to the server.
The server receives (612) the transaction request with the transaction amount and the acquired card information (i.e., the card identifier information and card data). In various embodiments, the card data extracted by the first terminal from the graphic code of the smart card is encrypted.
The server determines (614) a user account associated with the card identifier information, and authenticates the identity of the first user according to the card identifier information and card data. If the authentication succeeds, the server performs operation 616. The server acquires stored un-encrypted card data and a decryption key corresponding to the determined user account. The server decrypts the card data included in the transaction request with the decryption key and compares the decrypted card data to the stored un-encrypted card data. If the two are the same, the authentication of the identity of the first user is successful, and if the two are different, the authentication of the identity of the first user fails. If the authentication fails, the server sends a notification message to the first terminal, and the first terminal receives the notification message and reminds the first user and the second user.
The server processes (616) the transaction according to the transaction request. In various embodiments, the server identifies first user resource information (e.g., a payment account or other payment information) of the first user based on the user account bound to the card identifier information. In various embodiments, the server identifies second user resource information (e.g., a payment account or other payment information) of the second user. Thereafter, the transaction amount indicated by the transaction request is debited from the first user resource information and credited to the second user resource information.
In various embodiments, after completing the execution of operation (616), the server sends a processing success message to the first terminal; and the first terminal receives the processing success message and reminds the first user and the second user.
In process 600, the first terminal directly acquires card identifier information and card data from a smart card, and the server processes user resource information of a first user associated with the smart card and user resource information of a second user associated with the first terminal. It takes a short time for the first terminal to acquire the card identifier information and card data from the smart card, thereby improving efficiency of processing user resource information. Moreover, the first terminal further authenticates the smart card, which may prevent a user from using a counterfeit smart card to process user resource information of the first user.
It should be understood that the particular order in which the operations in
In various embodiments, data processing for a transaction processing application is implemented in client-server environment 100 (
The server receives (702) a transaction request including card identifier information and card data corresponding to a smart card.
The server authenticates (704) the card identifier information. For example, the server identifies a user account bound to the card identifier information and acquires an encryption key corresponding to the user account. The server generates a random number, uses the encryption key to encrypt the random number to obtain an encrypted ciphertext, and sends the encrypted ciphertext to the smart card (relayed through the first terminal). The smart card decrypts the encrypted ciphertext by using a decryption key stored in the smart card to obtain decrypted data, and sends the decrypted data to the server (relayed through the first terminal). The server compares the decrypted data and the random number; if the two are the same, the first authentication succeeds; if the two are different, the verification of the smart card by the first authentication fails.
If the first authentication succeeds, the server authenticates (706) the card data. For example, the server acquires stored un-encrypted card data and a decryption key corresponding to the determined user account. The server decrypts the card data with the decryption key and compares the decrypted card data to the stored un-encrypted card data. If the two are the same, the second authentication of is successful, and if the two are different, the second authentication fails.
If the second authentication succeeds, the server processes (708) the transaction corresponding to the transaction request. For example, the server acquires first user resource information of a first user corresponding to the smart card and second user resource information of a second user corresponding to a first terminal that sent the transaction request. Continuing with this example, the transaction request includes a transaction amount, and the server processes the transaction by debiting the first user resource information according to the transaction amount and crediting the second user resource information according to the transaction amount.
In method 700, card identifier information and card data corresponding to a smart card are acquired by the server, so that the server may thereby authenticate the card identifier information and card data, which may prevent a user from using a counterfeit smart card to process user resource information of the first user.
The particular order in which the operations in
In various embodiments, data processing for a transaction processing application is implemented in client-server environment 100 (
In various embodiments, prior to receiving the transaction request, the server binds (802) the card identification information corresponding to the smart card to the respective user account. In various embodiments, server system 108 or a component thereof (e.g., binding module 238,
The server receives (804) a transaction request from a first terminal to perform a transaction with a user of the smart card, where the transaction request includes card identification information and encrypted card data extracted by the first terminal from the smart card, and transaction information. In various embodiments, server system 108 or a component thereof (e.g., request handling module 222,
In various embodiments, the first terminal is a merchant's POS terminal. In various embodiments, the first terminal (e.g., client device 104,
The server determines (806) a respective user account linked to the card identification information. In various embodiments, server system 108 or a component thereof (e.g., account determination module 224,
The server performs (808) a first verification process to authenticate the smart card by verifying that the smart card possesses a correct decryption key corresponding to the card identification information. In various embodiments, server system 108 or a component thereof (e.g., first verification module 226,
In various embodiments, the server verifies that the smart card possesses the correct decryption key corresponding to the card identification information by (810): generating a pseudo-random string, and storing the pseudo-random string in association with the transaction request; encrypting the pseudo-random string with a stored encryption key corresponding to the card identification information, where the stored encryption key and the correct decryption key corresponding to the card identification information form an encryption-decryption key pair; sending the encrypted pseudo-random string to the first terminal for processing by the smart card; in response to sending the encrypted pseudo-random string, receiving, from the first terminal, a decrypted string, where the decrypted string corresponds to a decryption process performed by the smart card on the encrypted pseudo-random string with a respective decryption key stored on the smart card; and comparing the decrypted string to the stored pseudo-random string to determine whether the decrypted string and the stored pseudo-random string are identical. For example, first verification module 226 generates the pseudo-random string, encrypts the pseudo-random string with the encryption key corresponding to the respective user account, and sends the encrypted string to the first terminal for relaying to the smart card. Continuing with this example, the smart card decrypts the encrypted string with its stored decryption key and sends the decrypted string to the first terminal for relaying to the server. Continuing with this example, the first verification module 226 compares the decrypted string to the generated pseudo-random string, and, if the two strings match, the first verification process is successful.
In various embodiments, the smart card stores a decryption key, and also the card identification information and encrypted card data. However, in various embodiments, the identification information and encrypted card data is encoded in the graphic code or image on the smart card. In various embodiments, a processor of the smart card generates the image based on a predefined pattern/encoding algorithm with the identification information and encrypted card data as inputs. In various embodiments, the first terminal acts as a communication bridge between the server and the smart card for the first verification process. In various embodiments, the first terminal is in communication with the server via CMDA, GSM, WiFi, or the like. In various embodiments, smart card receives the encrypted string from the first terminal by way of a series of encoded pulses, an encoded EM field, an encoded signal sent via BLE, NFC, or the like.
The server performs (812) a second verification process to authenticate the smart card by verifying that the encrypted card data extracted from the smart card encodes stored card data corresponding to the respective user account linked to the card identification information. In various embodiments, server system 108 or a component thereof (e.g., second verification module 228,
In various embodiments, the server starts (814) performance of the second verification process in accordance with a determination that the decrypted string is identical to the stored pseudo-random string. In various embodiments, second verification module 228 performs the second verification process if the first verification process performed by first verification module 226 in operations 808-810 is successful.
In various embodiments, the server verifies that the encrypted card data extracted from the smart card encodes stored card data corresponding to the respective user account linked to the card identification information by (816), including decrypting the encrypted card data included in the transaction request with a stored decryption key corresponding to the respective user account, determining whether the decrypted card data matches the stored card data corresponding to the respective user account, and, in accordance with a determination that the decrypted card data matches stored card data corresponding to the respective user account, authenticating the user of the smart card as an authorized user of the smart card. In various embodiments, second verification module 228 decrypts the encrypted card data with the decryption key corresponding to the respective user account. If the decrypted card data matches stored card data for the respective user account, the second verification process is successful.
In accordance with successful completion of the first and the second verification processes, the server processes (818) the transaction in accordance with the transaction information. In various embodiments, server system 108 or a component thereof (e.g., transaction processing module 232,
In various embodiments, the server processes (820) the transaction according to the transaction information and payment information linked to the respective user account. In various embodiments, server system 108 or a component thereof (e.g., transaction processing module 232,
In various embodiments, in accordance with a determination that the transaction information is associated with a security risk, the server performs (822) a third verification process including: sending a notification to an electronic device linked to the respective user account and, in response to receiving an authorization message from the electronic device, processing the transaction request corresponding to the transaction request. In various embodiments, server system 108 or a component thereof (e.g., third verification module 230,
In various embodiments, the security risk is detected when the transaction information indicates (824) at least one of: a transaction amount exceeding a single transaction limit, a transaction amount exceeding a daily transaction limit, a transaction location outside of a predetermined radius from a predefined home location, and one or more items corresponding to the transaction that do match a purchasing profile for the respective user account.
In various embodiments, the server provides (826) updated card data to the smart card, where the updated card data is encrypted with the stored encryption key corresponding to the respective user account. In various embodiments, server system 108 or a component thereof (e.g., updating module 240,
In various embodiments, in accordance with unsuccessful completion of at least one of the first and the second verification processes, the server (828) locks-out the respective user account from performing subsequent transactions and sends a notification to an electronic device linked to the respective user account indicating failure of the at least one of the first verification process and the second verification process. In various embodiments, server system 108 or a component thereof (e.g., transaction failure module 234,
It should be understood that the particular order in which the operations in
In various embodiments, receiving module 910 is configured to receive a transaction request from a first terminal including transaction information, card identifier information, and card data, where the card identifier information and the card data are acquired by the first terminal from a smart card of a first user.
In various embodiments, authentication module 920 is configured to authenticate the identity of the first user according to the card identifier information and the card data. In various embodiments, authentication module 920 includes a first acquisition unit 922, a second acquisition unit 924, a decryption unit 926, and a comparison unit 928. In various embodiments, first acquisition unit 922 is configured to acquire a stored card data from a stored correspondence between the card identifier information and a user account for the first user bound to the card identifier information. In various embodiments, second acquisition unit 924 is configured to acquire a stored decryption key from the stored correspondence between the card identifier information and a user account for the first user bound to the card identifier information. In various embodiments, decryption unit 926 is configured to decrypt the card data included in the transaction request with the decryption key acquired by second acquisition unit 924 to obtain un-encrypted data. In various embodiments, comparison unit 928 is configured to compare the un-encrypted data obtained by decryption unit 926 with the stored card data acquired by first acquisition unit 922. If the two are the same, the authentication of the identity of the first user succeeds, and if the two are different, the authentication of the identity of the first user fails.
In various embodiments, acquisition module 930 is configured to acquire first user resource information of the first user according to the card identifier information and second user resource information of the second user of the first terminal in accordance with a determination that the authentication by authentication module 920 is successful. In various embodiments, acquisition module 930 includes: a third acquisition unit 932, and a fourth acquisition unit 934. In various embodiments, third acquisition unit 932 is configured to acquire a user account corresponding to the card identifier information. In various embodiments, fourth acquisition unit 934 is configured to acquire acquiring first user resource information of the first user according to the user account acquired by third acquisition unit 932.
In various embodiments, processing module 940 is configured to process the transaction corresponding to the transaction request received by receiving module 910 according to the first user resource information, the second user resource information, and the transaction amount indicated by the transaction information.
In various embodiments, server 900 further includes a storage module 950 for storing an entry in a database to bind the card identifier information with a registered user account. In various embodiments, storage module 950 includes a binding request receiving unit 952 and a binding unit 954. In various embodiments, binding request receiving unit 952 is configured to receive a binding request from a second terminal to bind the card identifier information with a registered user account. In various embodiments, binding unit 954 is configured to bind the card identifier information included in the binding request with the user account identified by the binding request.
In various embodiments, first acquisition module 1010 is configured to acquire card identifier information from a smart card. In various embodiments, authentication module 1020 is configured to authenticate the smart card according to the card identifier information. In various embodiments, authentication module 1020 includes an acquisition unit 1022, a generation unit 1024, and an authentication unit 1026. In various embodiments, acquisition unit 1022 is configured to acquire an encryption key corresponding to the smart card from server 900 (
In various embodiments, authentication unit 1026 is configured to authenticate the smart card according to the random number generated by generation unit 1024 and the encryption key acquired by acquisition unit 1022. In various embodiments, authentication unit 1026 includes an encryption sub-unit 1028, a sending sub-unit 1030, a receiving sub-unit 1032, and a comparison sub-unit 1034. In various embodiments, encryption sub-unit 1028 is configured to encrypt the random number generated by generation unit 1024 using the encryption key acquired by acquisition unit 1022 to obtain encrypted ciphertext. In various embodiments, sending sub-unit 1030 is configured to send to the smart card the encrypted ciphertext obtained by encryption sub-unit 1028, so that the smart card decrypts the encrypted ciphertext to obtain decrypted data. In various embodiments, receiving sub-unit 1032 is configured to receive decrypted data sent by the smart car. In various embodiments, comparison sub-unit 1034 is configured to compare the decrypted data received by receiving sub-unit 1032 and the random number generated by generation unit 1024. If the two are the same, the authentication of the smart card succeeds, and if the two are different, the authentication of the smart card fails.
In various embodiments, second acquisition module 1040 is configured to acquire card data from the smart card if the authentication by authentication module 1020 succeeds. In various embodiments, sending module 1050 is configured to send a transaction request to server 900 (
While particular embodiments are described above, they are not intended to limit the application to these particular embodiments. On the contrary, the application includes alternatives, modifications and equivalents that are within the spirit and scope of the appended claims. Numerous details are set forth in order to provide a thorough understanding of the subject matter presented herein. It will be apparent to one of ordinary skill in the art that the subject matter may be practiced without these details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to unnecessarily obscure aspects of the embodiments.
The foregoing description of the embodiments has been provided for purposes of illustration and description. It is not intended to be exhaustive or to limit the disclosure. Individual elements or features of a particular embodiment are generally not limited to that particular embodiment, but, where applicable, are interchangeable and can be used in a selected embodiment, even if not specifically shown or described. The same may also be varied in many ways. Such variations are not to be regarded as a departure from the disclosure, and all such modifications are intended to be included within the scope of the disclosure.
The foregoing description is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. The broad teachings of the disclosure can be implemented in a variety of forms. Therefore, while this disclosure includes particular examples, the true scope of the disclosure should not be so limited since other modifications will become apparent upon a study of the drawings, the specification, and the following claims. It should be understood that one or more steps within a method may be executed in different order (or concurrently) without altering the principles of the present disclosure. Further, although each of the embodiments is described above as having certain features, any one or more of those features described with respect to any embodiment of the disclosure can be implemented in and/or combined with features of any of the other embodiments, even if that combination is not explicitly described. In other words, the described embodiments are not mutually exclusive, and permutations of one or more embodiments with one another remain within the scope of this disclosure.
Spatial and functional relationships between elements (for example, between modules, circuit elements, semiconductor layers, etc.) are described using various terms, including “connected,” “engaged,” “coupled,” “adjacent,” “next to,” “on top of,” “above,” “below,” and “disposed.” Unless explicitly described as being “direct,” when a relationship between first and second elements is described in the above disclosure, that relationship can be a direct relationship where no other intervening elements are present between the first and second elements, but can also be an indirect relationship where one or more intervening elements are present (either spatially or functionally) between the first and second elements. As used herein, the phrase at least one of A, B, and C should be construed to mean a logical (A OR B OR C), using a non-exclusive logical OR, and should not be construed to mean “at least one of A, at least one of B, and at least one of C.”
In the figures, the direction of an arrow, as indicated by the arrowhead, generally demonstrates the flow of information (such as data or instructions) that is of interest to the illustration. For example, when element A and element B exchange a variety of information but information transmitted from element A to element B is relevant to the illustration, the arrow may point from element A to element B. This unidirectional arrow does not imply that no other information is transmitted from element B to element A. Further, for information sent from element A to element B, element B may send requests for, or receipt acknowledgements of, the information to element A.
In this application, including the definitions below, the term “module” or the term “controller” may be replaced with the term “circuit.” The term “module” may refer to, be part of, or include: an Application Specific Integrated Circuit (ASIC); a digital, analog, or mixed analog/digital discrete circuit; a digital, analog, or mixed analog/digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor circuit (shared, dedicated, or group) that executes code; a memory circuit (shared, dedicated, or group) that stores code executed by the processor circuit; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system-on-chip.
The module may include one or more interface circuits. In some examples, the interface circuits may include wired or wireless interfaces that are connected to a local area network (LAN), the Internet, a wide area network (WAN), or combinations thereof. The functionality of any given module of the present disclosure may be distributed among multiple modules that are connected via interface circuits. For example, multiple modules may allow load balancing. In a further example, a server (also known as remote, or cloud) module may accomplish some functionality on behalf of a client module.
The term code, as used above, may include software, firmware, and/or microcode, and may refer to programs, routines, functions, classes, data structures, and/or objects. The term shared processor circuit encompasses a single processor circuit that executes some or all code from multiple modules. The term group processor circuit encompasses a processor circuit that, in combination with additional processor circuits, executes some or all code from one or more modules. References to multiple processor circuits encompass multiple processor circuits on discrete dies, multiple processor circuits on a single die, multiple cores of a single processor circuit, multiple threads of a single processor circuit, or a combination of the above. The term shared memory circuit encompasses a single memory circuit that stores some or all code from multiple modules. The term group memory circuit encompasses a memory circuit that, in combination with additional memories, stores some or all code from one or more modules.
The term memory circuit is a subset of the term computer-readable medium. The term computer-readable medium, as used herein, does not encompass transitory electrical or electromagnetic signals propagating through a medium (such as on a carrier wave); the term computer-readable medium may therefore be considered tangible and non-transitory. Non-limiting examples of a non-transitory, tangible computer-readable medium are nonvolatile memory circuits (such as a flash memory circuit, an erasable programmable read-only memory circuit, or a mask read-only memory circuit), volatile memory circuits (such as a static random access memory circuit or a dynamic random access memory circuit), magnetic storage media (such as an analog or digital magnetic tape or a hard disk drive), and optical storage media (such as a CD, a DVD, or a Blu-ray Disc).
The apparatuses and methods described in this application may be partially or fully implemented by a special purpose computer created by configuring a general purpose computer to execute one or more particular functions embodied in computer programs. The functional blocks and flowchart elements described above serve as software specifications, which can be translated into the computer programs by the routine work of a skilled technician or programmer.
The computer programs include processor-executable instructions that are stored on at least one non-transitory, tangible computer-readable medium. The computer programs may also include or rely on stored data. The computer programs may encompass a basic input/output system (BIOS) that interacts with hardware of the special purpose computer, device drivers that interact with particular devices of the special purpose computer, one or more operating systems, user applications, background services, background applications, etc.
The computer programs may include: (i) descriptive text to be parsed, such as HTML (hypertext markup language) or XML (extensible markup language), (ii) assembly code, (iii) object code generated from source code by a compiler, (iv) source code for execution by an interpreter, (v) source code for compilation and execution by a just-in-time compiler, etc. As examples only, source code may be written using syntax from languages including C, C++, C#, Objective-C, Swift, Haskell, Go, SQL, R, Lisp, Java®, Fortran, Perl, Pascal, Curl, OCaml, Javascript®, HTML5 (Hypertext Markup Language 5th revision), Ada, ASP (Active Server Pages), PHP (PHP: Hypertext Preprocessor), Scala, Eiffel, Smalltalk, Erlang, Ruby, Flash®, Visual Basic®, Lua, MATLAB, SIMULINK, and Python®.
None of the elements recited in the claims are intended to be a means-plus-function element within the meaning of 35 U.S.C. § 112(f) unless an element is expressly recited using the phrase “means for,” or in the case of a method claim using the phrases “operation for” or “step for.”
| Number | Date | Country | Kind |
|---|---|---|---|
| 201410006083.5 | Jan 2014 | CN | national |
This application is a continuation of U.S. application Ser. No. 15/177,413 filed on Jun. 9, 2016, which is a continuation of International Application No. PCT/CN2015/070230, filed on Jan. 6, 2015, which claims the benefit and priority of Chinese Application No. 201410006083.5, filed on Jan. 7, 2014. The entire disclosures of each of the above applications are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5036461 | Elliott | Jul 1991 | A |
| 5065429 | Lang | Nov 1991 | A |
| 5191611 | Lang | Mar 1993 | A |
| 5225664 | Iijima | Jul 1993 | A |
| 5282249 | Cohen | Jan 1994 | A |
| 5923759 | Lee | Jul 1999 | A |
| 5949044 | Walker | Sep 1999 | A |
| 6018717 | Lee | Jan 2000 | A |
| 6301660 | Benson | Oct 2001 | B1 |
| 6829711 | Kwok | Dec 2004 | B1 |
| 7028014 | Naclerio | Apr 2006 | B1 |
| 7103575 | Linehan | Sep 2006 | B1 |
| 7258267 | Choi | Aug 2007 | B2 |
| 7357309 | Ghosh | Apr 2008 | B2 |
| 7373517 | Riggins | May 2008 | B1 |
| 7395435 | Benhammou | Jul 2008 | B2 |
| 7426277 | Kimura | Sep 2008 | B2 |
| 7536722 | Saltz | May 2009 | B1 |
| 7599856 | Agrawal | Oct 2009 | B2 |
| 7627531 | Breck | Dec 2009 | B2 |
| 7681232 | Nordentoft | Mar 2010 | B2 |
| 7779455 | Abellan Sevilla | Aug 2010 | B2 |
| 7983419 | Fan | Jul 2011 | B2 |
| 8042155 | Chang | Oct 2011 | B1 |
| 8234504 | Cheung | Jul 2012 | B2 |
| 8239324 | Asai | Aug 2012 | B2 |
| 8355982 | Hazel | Jan 2013 | B2 |
| 8364808 | Shima | Jan 2013 | B2 |
| 8539233 | Dubhashi | Sep 2013 | B2 |
| 8606720 | Baker | Dec 2013 | B1 |
| 8787973 | Agami | Jul 2014 | B2 |
| 8966581 | Gross | Feb 2015 | B1 |
| 9060057 | Danis | Jun 2015 | B1 |
| 9547861 | Itwaru | Jan 2017 | B2 |
| 9560010 | Estes | Jan 2017 | B1 |
| 9628273 | Alshammari | Apr 2017 | B2 |
| 9760645 | Park | Sep 2017 | B1 |
| 9915943 | Wang | Mar 2018 | B2 |
| 10326797 | Murray | Jun 2019 | B1 |
| 10475024 | Behren | Nov 2019 | B1 |
| 10535044 | Feldman | Jan 2020 | B2 |
| 10614454 | Brooks, V | Apr 2020 | B1 |
| 10769624 | Gonzalez | Sep 2020 | B1 |
| 10878413 | Liu | Dec 2020 | B2 |
| 11037139 | Ho | Jun 2021 | B1 |
| 11257085 | Barkas | Feb 2022 | B1 |
| 11386424 | Dicker | Jul 2022 | B2 |
| 11423374 | Hardin | Aug 2022 | B2 |
| 20010045451 | Tan | Nov 2001 | A1 |
| 20020013898 | Sudia | Jan 2002 | A1 |
| 20020049729 | Umekawa | Apr 2002 | A1 |
| 20020076204 | Nakano | Jun 2002 | A1 |
| 20020077837 | Krueger | Jun 2002 | A1 |
| 20020107809 | Biddle | Aug 2002 | A1 |
| 20020128977 | Nambiar | Sep 2002 | A1 |
| 20020129250 | Kimura | Sep 2002 | A1 |
| 20020152178 | Lee | Oct 2002 | A1 |
| 20030009681 | Harada | Jan 2003 | A1 |
| 20030028481 | Flitcroft | Feb 2003 | A1 |
| 20030093680 | Astley | May 2003 | A1 |
| 20030111526 | Smith | Jun 2003 | A1 |
| 20030145205 | Sarcanin | Jul 2003 | A1 |
| 20030172273 | Hans | Sep 2003 | A1 |
| 20030187805 | Shen | Oct 2003 | A1 |
| 20030229795 | Kunigkeit | Dec 2003 | A1 |
| 20040033813 | Sakamura | Feb 2004 | A1 |
| 20040034784 | Fedronic | Feb 2004 | A1 |
| 20040059685 | Sakamura | Mar 2004 | A1 |
| 20040118914 | Smith | Jun 2004 | A1 |
| 20040127256 | Goldthwaite | Jul 2004 | A1 |
| 20040168063 | Revital | Aug 2004 | A1 |
| 20040218214 | Kihara | Nov 2004 | A1 |
| 20040236819 | Anati | Nov 2004 | A1 |
| 20040250066 | Di Luoffo | Dec 2004 | A1 |
| 20050044385 | Holdsworth | Feb 2005 | A1 |
| 20050050366 | Kwok | Mar 2005 | A1 |
| 20050138390 | Adams | Jun 2005 | A1 |
| 20050150945 | Choi | Jul 2005 | A1 |
| 20050165684 | Jensen | Jul 2005 | A1 |
| 20050188167 | Squibbs | Aug 2005 | A1 |
| 20050195975 | Kawakita | Sep 2005 | A1 |
| 20050240779 | Aull | Oct 2005 | A1 |
| 20060032905 | Bear | Feb 2006 | A1 |
| 20060049256 | von Mueller | Mar 2006 | A1 |
| 20060161490 | Chakiris | Jul 2006 | A1 |
| 20060271483 | Ernst | Nov 2006 | A1 |
| 20070011066 | Steeves | Jan 2007 | A1 |
| 20070192584 | Bajar | Aug 2007 | A1 |
| 20070198848 | Bjorn | Aug 2007 | A1 |
| 20080003977 | Chakiris | Jan 2008 | A1 |
| 20080052770 | Ali | Feb 2008 | A1 |
| 20080061150 | Phillips | Mar 2008 | A1 |
| 20080061151 | Phillips | Mar 2008 | A1 |
| 20080068181 | Phillips | Mar 2008 | A1 |
| 20080091944 | von Mueller | Apr 2008 | A1 |
| 20080104392 | Satoshi | May 2008 | A1 |
| 20080121707 | Phillips | May 2008 | A1 |
| 20080134346 | Cho | Jun 2008 | A1 |
| 20080165006 | Phillips | Jul 2008 | A1 |
| 20080165959 | Hong | Jul 2008 | A1 |
| 20080179401 | Hart | Jul 2008 | A1 |
| 20080201265 | Hewton | Aug 2008 | A1 |
| 20090076966 | Bishop | Mar 2009 | A1 |
| 20090121029 | Asnaashari | May 2009 | A1 |
| 20090125719 | Cochran | May 2009 | A1 |
| 20090144205 | Hurry | Jun 2009 | A1 |
| 20090235339 | Mennes | Sep 2009 | A1 |
| 20090254971 | Herz | Oct 2009 | A1 |
| 20090256676 | Piccirillo | Oct 2009 | A1 |
| 20090285397 | Iwamori | Nov 2009 | A1 |
| 20100057616 | Kapur | Mar 2010 | A1 |
| 20100057618 | Spicer | Mar 2010 | A1 |
| 20100088237 | Wankmueller | Apr 2010 | A1 |
| 20100100724 | Kaliski, Jr. | Apr 2010 | A1 |
| 20100153717 | Sandler | Jun 2010 | A1 |
| 20100185875 | Mayer | Jul 2010 | A1 |
| 20100199089 | Vysogorets | Aug 2010 | A1 |
| 20100239093 | Hotta | Sep 2010 | A1 |
| 20100241867 | Brown | Sep 2010 | A1 |
| 20100257101 | Fierro | Oct 2010 | A1 |
| 20110106710 | Reed | May 2011 | A1 |
| 20110173124 | Feldman | Jul 2011 | A1 |
| 20110246791 | Kambayashi | Oct 2011 | A1 |
| 20110258452 | Coulier | Oct 2011 | A1 |
| 20110270751 | Csinger | Nov 2011 | A1 |
| 20110307724 | Shaw | Dec 2011 | A1 |
| 20120130794 | Strieder | May 2012 | A1 |
| 20120159196 | Kuno | Jun 2012 | A1 |
| 20120233456 | Spitz | Sep 2012 | A1 |
| 20120239417 | Pourfallah | Sep 2012 | A1 |
| 20120317410 | Paulsen | Dec 2012 | A1 |
| 20120323717 | Kirsch | Dec 2012 | A1 |
| 20130080769 | Cha | Mar 2013 | A1 |
| 20130097419 | Lu | Apr 2013 | A1 |
| 20130185354 | Seligstein | Jul 2013 | A1 |
| 20130218769 | Pourfallah | Aug 2013 | A1 |
| 20130226609 | Pourfallah | Aug 2013 | A1 |
| 20130257590 | Kuenzi | Oct 2013 | A1 |
| 20130268443 | Petrov | Oct 2013 | A1 |
| 20130283040 | Tu | Oct 2013 | A1 |
| 20130283049 | Brown | Oct 2013 | A1 |
| 20130290714 | Hans | Oct 2013 | A1 |
| 20130311313 | Laracey | Nov 2013 | A1 |
| 20130339167 | Taylor | Dec 2013 | A1 |
| 20140032409 | Rosano | Jan 2014 | A1 |
| 20140046746 | Davis | Feb 2014 | A1 |
| 20140047703 | Forster | Feb 2014 | A1 |
| 20140054382 | Sugibuchi | Feb 2014 | A1 |
| 20140058855 | Hussein | Feb 2014 | A1 |
| 20140081874 | Lewis | Mar 2014 | A1 |
| 20140164774 | Nord | Jun 2014 | A1 |
| 20140189359 | Marien | Jul 2014 | A1 |
| 20140244494 | Davis | Aug 2014 | A1 |
| 20140258132 | Swamy | Sep 2014 | A1 |
| 20140263622 | Babatz | Sep 2014 | A1 |
| 20140317410 | Yamaguchi | Oct 2014 | A1 |
| 20140359144 | Kruse | Dec 2014 | A1 |
| 20150012430 | Chisholm | Jan 2015 | A1 |
| 20150032622 | Powell | Jan 2015 | A1 |
| 20150039506 | Groarke | Feb 2015 | A1 |
| 20150072653 | Fan | Mar 2015 | A1 |
| 20150088756 | Makhotin | Mar 2015 | A1 |
| 20150095219 | Hurley | Apr 2015 | A1 |
| 20150120419 | Byland | Apr 2015 | A1 |
| 20150140957 | Kiswani | May 2015 | A1 |
| 20150149776 | Chastain | May 2015 | A1 |
| 20150264091 | Lin | Sep 2015 | A1 |
| 20150301802 | Katoh | Oct 2015 | A1 |
| 20150302410 | Lacoss-Arnold | Oct 2015 | A1 |
| 20150332258 | Kurabi | Nov 2015 | A1 |
| 20160026997 | Tsui | Jan 2016 | A1 |
| 20160027010 | Babatz | Jan 2016 | A1 |
| 20160080364 | Karimzadeh | Mar 2016 | A1 |
| 20160112381 | Bhattacharyya | Apr 2016 | A1 |
| 20160132877 | Carrott | May 2016 | A1 |
| 20160174069 | Bruner | Jun 2016 | A1 |
| 20160219039 | Houthooft | Jul 2016 | A1 |
| 20160239835 | Marsyla | Aug 2016 | A1 |
| 20160241543 | Jung | Aug 2016 | A1 |
| 20160294783 | Piqueras Jover | Oct 2016 | A1 |
| 20160295404 | Gouget | Oct 2016 | A1 |
| 20160300224 | Liu | Oct 2016 | A1 |
| 20160307190 | Zarakas | Oct 2016 | A1 |
| 20160321660 | Liu | Nov 2016 | A1 |
| 20160330616 | Koriyama | Nov 2016 | A1 |
| 20170076277 | Zhou | Mar 2017 | A1 |
| 20170084116 | Anderson | Mar 2017 | A1 |
| 20170109738 | Brown | Apr 2017 | A1 |
| 20170124554 | Sloan | May 2017 | A1 |
| 20170223532 | Chen | Aug 2017 | A1 |
| 20170230345 | Piqueras Jover | Aug 2017 | A1 |
| 20170289185 | Mandyam | Oct 2017 | A1 |
| 20170310479 | Sato | Oct 2017 | A1 |
| 20180063874 | Wu | Mar 2018 | A1 |
| 20180096340 | Omojola | Apr 2018 | A1 |
| 20180108008 | Chumbley | Apr 2018 | A1 |
| 20180114226 | Desai | Apr 2018 | A1 |
| 20180121891 | Hosny | May 2018 | A1 |
| 20180121895 | Mohrlock | May 2018 | A1 |
| 20180124596 | Iannace | May 2018 | A1 |
| 20180174149 | Goldschmidt | Jun 2018 | A1 |
| 20180183608 | Koyun | Jun 2018 | A1 |
| 20180270340 | Ahmad | Sep 2018 | A1 |
| 20180300730 | Telford-Reed | Oct 2018 | A1 |
| 20190236599 | Jeong | Aug 2019 | A1 |
| 20190379667 | Touboul | Dec 2019 | A1 |
| 20200058023 | Travizano | Feb 2020 | A1 |
| 20200058068 | Gandhi | Feb 2020 | A1 |
| 20200104830 | Hart | Apr 2020 | A1 |
| 20200169550 | Xie | May 2020 | A1 |
| 20200294106 | Seshan | Sep 2020 | A1 |
| 20200349573 | Dong | Nov 2020 | A1 |
| 20210012339 | Rafferty | Jan 2021 | A1 |
| 20210012401 | Osborn | Jan 2021 | A1 |
| 20210073809 | Liu | Mar 2021 | A1 |
| 20210201296 | Rule | Jul 2021 | A1 |
| 20210279717 | Gupta | Sep 2021 | A1 |
| 20210326818 | Hogg | Oct 2021 | A1 |
| 20210344660 | Benkreira | Nov 2021 | A1 |
| Number | Date | Country |
|---|---|---|
| 02197407 | Sep 2011 | CN |
| 02842081 | Dec 2012 | CN |
| 02930435 | Feb 2013 | CN |
| 03067335 | Apr 2013 | CN |
| 04038924 | Sep 2014 | CN |
| 2006014043 | Feb 2006 | WO |
| Entry |
|---|
| Setyoko (Multipurpose Smart Card System) (Year: 2014). |
| Gupta et al (A New Framework for Credit Card Transactions involving Mutual Authentication between Cardholder and Merchant) (Year: 2011). |
| Matanovic et al (Enforcing access restrictions on terminal maintenance tasks using smart cards ) (Year: 2009). |
| Chinese Office Action for Application No. 2014100060835 dated Jan. 29, 2016, and an English concise explanation of relevance thereof. |
| International Preliminary Report for Application No. PCT/CN2015/070230 dated Jul. 12, 2016. |
| International Search Report for Application No. PCT/CN2015/070230 dated Apr. 9, 2015. |
| Number | Date | Country | |
|---|---|---|---|
| 20210073809 A1 | Mar 2021 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 15177413 | Jun 2016 | US |
| Child | 17101295 | US | |
| Parent | PCT/CN2015/070230 | Jan 2015 | US |
| Child | 15177413 | US |
