US7631810B2 - Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device - Google Patents

Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device Download PDF

Info

Publication number
US7631810B2
US7631810B2 US11/641,557 US64155706A US7631810B2 US 7631810 B2 US7631810 B2 US 7631810B2 US 64155706 A US64155706 A US 64155706A US 7631810 B2 US7631810 B2 US 7631810B2
Authority
US
United States
Prior art keywords
application
applications
request
wireless
effecting
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US11/641,557
Other versions
US20080147508A1 (en
Inventor
Ming-Li Liu
Pradeep Kumar
William S. Johnson, Jr.
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mastercard International Inc
Original Assignee
Vivotech Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivotech Inc filed Critical Vivotech Inc
Priority to US11/641,557 priority Critical patent/US7631810B2/en
Assigned to VIVOTECH, INC. reassignment VIVOTECH, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: JOHNSON, WILLIAM S., JR., KUMAR, PRADEEP, LIU, MING-LI
Publication of US20080147508A1 publication Critical patent/US20080147508A1/en
Application granted granted Critical
Publication of US7631810B2 publication Critical patent/US7631810B2/en
Assigned to SILICON VALLEY BANK reassignment SILICON VALLEY BANK SECURITY AGREEMENT Assignors: VIVOTECH, INC.
Assigned to VIVOTECH INC reassignment VIVOTECH INC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: SILICON VALLEY BANK
Assigned to VIVOTECH (ASSIGNMENT FOR THE BENEFIT OF CREDITORS), LLC reassignment VIVOTECH (ASSIGNMENT FOR THE BENEFIT OF CREDITORS), LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: VIVOTECH, INC.
Assigned to MASTERCARD INTERNATIONAL INCORPORATED reassignment MASTERCARD INTERNATIONAL INCORPORATED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: VIVOTECH (ASSIGNMENT FOR THE BENEFIT OF CREDITORS), LLC
Application status is Active legal-status Critical
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07FCOIN-FREED OR LIKE APPARATUS
    • G07F7/00Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
    • G07F7/08Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
    • G07F7/10Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
    • G07F7/1008Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/08Payment architectures
    • G06Q20/20Point-of-sale [POS] network systems
    • G06Q20/204Point-of-sale [POS] network systems comprising interface for record bearing medium or carrier for electronic funds transfer or payment credit
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/32Payment architectures, schemes or protocols characterised by the use of specific devices using wireless devices
    • G06Q20/322Aspects of commerce using mobile devices [M-devices]
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/341Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06QDATA PROCESSING SYSTEMS OR METHODS, SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL, SUPERVISORY OR FORECASTING PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00Payment architectures, schemes or protocols
    • G06Q20/30Payment architectures, schemes or protocols characterised by the use of specific devices
    • G06Q20/34Payment architectures, schemes or protocols characterised by the use of specific devices using cards, e.g. integrated circuit [IC] cards or magnetic cards
    • G06Q20/357Cards having a plurality of specified features
    • G06Q20/3574Multiple applications on card

Abstract

Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device are disclosed. According to one aspect, the subject matter described herein includes a system for supporting multiple instances of the same application. The system includes a wireless smart device for communicating with a wireless reader. The wireless smart device includes multiple instances of the same application for performing wireless transactions with an external device. The wireless smart device also includes an application manager for identifying one of the instances as active, for detecting a request from a wireless reader for performing a wireless transaction, and for communicating the request to the active instance.

Description

TECHNICAL FIELD

The subject matter described herein relates to effecting wireless payment and other transactions using wireless smart devices. More particularly, the subject matter described herein relates to systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device.

BACKGROUND

With the success and widespread prevalence of the use of credit and debit cards for banking transactions, card issuers, such as banks and financial institutions, have turned to wireless smart devices as a means to provide their customers with a richer, more powerful set of features than is possible using a traditional magnetic stripe (“magstripe”) credit card.

As used herein, the term “smart device” refers to a device with processing capabilities. A smart device may have on-board memory or other storage capacity, may be written to as well as read from, and may contain one or more applications that perform a particular function. Some smart devices may contain an operating system and/or user interface.

As used herein, the term “wireless smart device” refers to a smart device that can communicate via an electric and/or magnetic field between the device and some other entity, usually a wireless terminal or reader. One type of wireless communications that can be used between a wireless smart device and reader is near field communication (NFC). In one form of near field communication, a wireless smart device may communicate with a reader via inductive coupling of the reader antenna to the device antenna. The two loop antennas effectively form a transformer. The reader amplitude-modulates the RF field to send information to the device. The device communicates with the reader by modulating the loading on the device antenna, which also modulates the load on the reader antenna.

As used herein, the term “payment application” refers to an application that performs a payment or other financial transaction. An example payment application might respond to a request for credit card account information, for example, by providing credit card information, such as the credit card number, the name of the card holder, and the expiration date of the card—i.e., information that is typically coded onto the magnetic stripe of traditional credit cards.

Unlike magstripe cards, which are read-only devices that simply report account information to the magstripe card reader, wireless smart devices containing payment applications may have processing capability with which to perform functions, such as encryption/decryption of data, authentication, authorization, and verification of the user or of the user's transaction, storage and/or validation of the card-holder's identification, and so on. Wireless smart devices may interact with wireless readers to enable transactions involving the payment application. Examples of wireless smart devices containing payment applications include mobile phones, smart phones, key fobs, physical cards, personal digital assistants with interfaces to local card readers, and devices provisioned with a soft card.

As used herein, the term “soft card” refers to a software-implemented identity, security, authentication, membership, loyalty, electronic payment, or other card that is loadable onto a device with wireless communications capabilities.

An example of wireless communications commonly used by wireless smart devices is the ISO 14443 interface. The ISO/IEC 14443 specification (hereinafter referred to as the “14443 Specification”) defines a communication protocol for wireless smart devices operating at 13.56 MHz in close proximity with a reader antenna. Applications are uniquely identified by an application identifier (AID), defined by the ISO/IEC 7816 specification. An AID has two parts: a 5-byte registered application provider ID (RID), which is issued by a 14443 controlling authority, and a proprietary application identifier extension (PIX), which is assigned by the registered application provider as it sees fit and which may be from one to eleven bytes.

Some applications may limit the number of instances of that application that a wireless smart device may contain. For example, the protocol for the MasterCard Worldwide (formerly MasterCard International) MasterCard PayPass® product, which is a contactless device used for banking transactions, defines two AIDs, one for the MasterCard® brand and another for the Maestro® brand, and does not support multiple instances of the same PayPass® application (i.e., with the same AID) within one wireless smart device. Other payment applications that prohibit a wireless smart device from containing more than one application of the same type include American Express® ExpressPaySM and JCB® QUICPay™. Application types other than payment applications, such as identity, security, authentication, membership, loyalty, or other application type, may also similarly prohibit a wireless smart device from containing more than one instance of the same application.

There are advantages to allowing multiple instances of the same application on a wireless smart device. For example, it may be desirable to have multiple payment applications from a single financial institution or brand on a single wireless smart device, to allow the consumer to use a single wireless smart device as both a credit card and a debit card, as both a personal card and a corporate card, as both a card with a high credit limit and a card with a low credit limit, and so on. Another advantage is to allow the user multiple card issuer (such as MasterCard) accounts from different financial institutions. None of these advantages are available to the user of a payment or other type of application that does not support multiple instances of the same application on a single wireless smart device. It will be appreciated that the advantages associated with allowing a wireless smart device to support multiple instances of the same application are not limited to payment applications but extend to other types of applications as well.

Accordingly, there exists a need for a system, method, and computer product for providing multiple instances of the same application on a wireless smart device.

SUMMARY

According to one aspect, the subject matter described herein includes a system for supporting multiple instances of the same application. The system includes a wireless smart device for communicating with a wireless reader. The wireless smart device includes multiple instances of the same application for performing wireless transactions with an external device. The wireless smart device also includes an application manager for identifying one of the instances as active, for detecting a request from the wireless reader for performing a wireless transaction, and for communicating the request to the active instance.

According to another aspect, the subject matter described herein includes a system for supporting multiple applications. The system includes a wireless smart device that includes multiple applications for performing wireless transactions with an external device. The wireless smart device also includes an application manager for detecting a request from a wireless reader for performing a wireless transaction, for identifying one of the applications as the target of the request, for determining that the target application is active, and, responsive to that determination, communicating the request to the target application.

According to another aspect, the subject matter described herein includes a method for supporting multiple instances of the same application on a wireless smart device. The method includes receiving, using an application manager residing within a wireless smart device having multiple instances of the same application for effecting wireless transactions with an external device, a request from a wireless reader for effecting a transaction, and responsive to that request, identifying one of the instances as active and sending a request for effecting the transaction to the active instance. The method also includes receiving, using the active instance, the request from the application manager for effecting the transaction, and, responsive to that request, sending a response to the wireless reader.

According to another aspect, the subject matter described herein includes a method for supporting multiple applications on a wireless smart device. The method includes receiving, using an application manager residing within a wireless smart device having multiple applications for performing wireless transactions with an external device, a request from a wireless reader for effecting a transaction, and responsive to that request, identifying one of the applications as a target of that request, determining if the target application is active, and responsive to that determination, communicating the request to the target application. The method also includes receiving, using the target application, the request from the application manager for effecting the transaction, and, responsive to that request, sending a response to the wireless reader.

The subject matter described herein for providing multiple instances of the same application on a wireless smart device may be implemented in hardware, software, firmware, or any combination thereof. As such, the terms “function” or “module” as used herein refer to hardware, software, and/or firmware for implementing the feature being described. In one exemplary implementation, the subject matter described herein may be implemented using a computer program product comprising computer executable instructions embodied in a computer readable medium. Exemplary computer readable media suitable for implementing the subject matter described herein include disk memory devices, chip memory devices, programmable logic devices, application specific integrated circuits, and downloadable electrical signals. In addition, a computer program product that implements the subject matter described herein may be located on a single device or computing platform or may be distributed across multiple devices or computing platforms.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the subject matter described herein will now be explained with reference to the accompanying drawings of which:

FIG. 1 is a block diagram illustrating an exemplary wireless smart device according to an embodiment of the subject matter described herein; and

FIG. 2 is a message flow diagram illustrating the steps of an exemplary wireless payment transaction according to an embodiment of the subject matter therein; and

FIG. 3 is a message flow diagram illustrating the steps of an exemplary payment application selection according to an embodiment of the subject matter therein.

DETAILED DESCRIPTION OF THE INVENTION

In accordance with the subject matter disclosed herein, systems, methods, and computer program products are provided for providing multiple instances of the same application on a wireless smart device.

FIG. 1 is a block diagram illustrating an exemplary wireless smart device according to an embodiment of the subject matter therein. In FIG. 1, a wireless terminal or reader 100 communicates with wireless smart device 102. Device 102 may contain one or more application managers; two are shown in FIG. 1: application manager 1 104 and application manager 2 106. Each application manager may communicate with multiple applications, such as applications for performing wireless transactions with an external device. Such applications may include identity, security, authentication, membership, loyalty, electronic payment, or other application type. In some embodiments, an application manager may manage multiple instances of the same application. In some embodiments, an application may manage multiple different applications, which may include multiple applications of different types. Application manager 1 104 manages application 1 108, application 2 110, and application 3 112, while application manager 2 106 manages application 4114 and application 5 116. In the exemplary embodiment illustrated in FIG. 1, each application is a payment application and each payment application may represent an account at a bank or other financial entity. Each account may have an account number associated with it (e.g., “AAAA BBBB CCCC DDDD”). Application manager 1 104 may manage payment applications of a particular type, such as MasterCard PayPass®, which has an AID of “A0 00 00 00 04 10 10”. Application 1 108, application 2 110, and application 3 112 may represent multiple instances of the same type (i.e., MasterCard PayPass®), and each instance may represent a separate MasterCard account having a unique account number. Similarly, application manager 2 106 may manage payment applications of another type, such as Maestro PayPass®, which has an AID of “A0 00 00 00 04 30 60”. Application 4 114 and application 5 116 may represent multiple instances of another type (i.e., Maestro PayPass®), and each instance may represent a separate Maestro account having a unique account number. In some embodiments, an application selection function 118 may allow a user to select an active application and may communicate the selection to application manager 1 104 and application manager 2 106.

Application manager 1 104 and application manager 2 106 may each have several functions. One function of application manager 1 104 and application manager 2 106 may be to allow a wireless smart device to contain multiple instances of the same application, where the application specification prohibits multiple instances of the same application type on a single wireless smart device. In this case, compliance with the application specification requires that from the perspective of reader 100, device 102 appears to contain only one application of that type. In FIG. 1, application manager 1 104 and application manager 2 106 each may appear to reader 100 to be an application of a particular type. Application manager 1 104 may appear to reader 100 as a single MasterCard PayPass® application, for example, while application manager 2 106 may appear to reader 100 as a single Maestro PayPass® application. More specifically, if a PayPass® reader 100 requests from device 102 a list of payment applications available on device 102, the list may include application manager 1 104 (presented as a MasterCard PayPass® application) and application manager 2 106 (presented as a Maestro PayPass® application) rather than including the actual PayPass® applications application 1 108 through application 5 116. In other words, the actual PayPass® applications are, in one sense, hidden behind their respective account managers—at least from discovery through normal inquiry by reader 100. When reader 100 performs a MasterCard PayPass® transaction with device 102, it appears to reader 100 that device 102 contains only one MasterCard PayPass® application in compliance with the PayPass® specification, when in actuality there are three MasterCard PayPass® applications within device 102. FIG. 2, below, illustrates an example such transaction in detail.

Examples of other functions that may be performed by application manager 1 104 and application manager 2 106 include: managing multiple applications of the same type or of different types; notifying the user of completion of a transaction; disabling a wireless smart device's ability to do some (or all) types of transactions; and allowing a user to selectively activate or deactivate individual applications, regardless of type. A user may desire this feature as a means to avoid accidental or malicious transactions from occurring without the user's knowledge, or to avoid the use of a payment account which has reached its credit limit, for example.

FIG. 2 is a message flow diagram illustrating the steps of an exemplary wireless payment transaction according to an embodiment of the subject matter described herein. Although FIG. 2 is a simplified illustration of a wireless transaction in conformance with the 14443 Specification, the use of other communication specifications and protocols is within the scope of the subject matter described herein. Referring to FIG. 2, in step 200, wireless smart device 102 is placed within the detection field of reader 100, which detects the presence of device 102. In some embodiments, device 102 may power up. Device 102 may perform some initialization. Device 102 and reader 100 may perform a handshaking procedure. Reader 100 may request device 102 to provide to reader 100 information about the available applications residing on device 102. In some embodiments, information about available applications residing within device 102 is provided at the application level. In response to that request, device 102 may return a list or a pointer to a list, or may otherwise convey to reader 100 information about the applications available on device 102. That information may include the application type or AID for each application. For example, payment terminals may make a request to an application on device 102, such as the payment system environment (PSE) or the PayPass® payment system environment (PPSE), to return a list of payment applications available on device 102. Reader 100 may choose an appropriate application, if available, from the list. Further communication from reader 100 may be directed to the chosen application, identified by its AID. In embodiments of the subject matter described herein, in response to a request for information about applications, device 102 may return the AID of application manager 1 104 instead of the AIDs of application 1 108, application 2 110, or application 3 112. Application manager 1 104 presents itself to reader 100 as an application of the same type as the applications that it manages (i.e., a MasterCard PayPass® application.) Similarly, device 102 may return the AID of application manager 2 106 instead of the AIDs of application 4 114 or application 5 116. Application manager 2 106 presents itself to reader 100 as an application of the same type as the applications that it manages (i.e., a Maestro PayPass® application.)

In step 202, reader 100 may issue a command to select or otherwise initiate communication with the chosen application, such as the SELECT command. Reader 100 may select application manager 1 104, which appears to reader 100 as a payment application. Future communication from reader 100 will be directed toward application manager 1 104.

In step 204, application manager 1 104 may determine which of its managed applications is the active application. Referring to FIG. 1, application 1 108 is the active application, having been previously activated or selected by application selection function 118, which may be a user selection through a menu, for example, or prior configuration through an alternate means. Each application may have its own unique internal AID, which application manager 1 104 may use to identify and communicate with individual applications. For example, application 1 108 may have an AID of “A0 00 00 02 99 04 10 10 57 10”, application 2 110 may have an AID of “A0 00 00 02 99 04 10 10 57 01”, and application 3 112 may have an AID of “A0 00 00 02 99 04 10 10 57 10”. Returning to FIG. 2, application manager 1 104 may forward the SELECT command to active application 1 108, identifying the application by its internal AID. Alternatively, application manager 1 104 may issue its own internal command to application 1 108 rather than forwarding the SELECT command issued by reader 100. Although it is theoretically possible that reader 100 may attempt to bypass an application manager and contact the managed applications directly (by somehow discovering—or guessing—the AID of one of the managed applications and issuing a SELECT command to that AID) the managed applications may be programmed to reject requests received directly from a reader. For example, application 1 108 may be able to distinguish between a request from a reader 100 (an external request) and a request from an application manager 1 104 (an internal request) and respond only to internal requests. An external request may be distinguished from an internal request by, for example, using a different protocol for an internal request, using a different communications path for the internal request, using a different command, command argument, or command option for an internal request, setting a flag to enable a transaction command just prior to issuing the transaction, or by other mechanisms and methods that do not depart from the scope of the subject matter described herein.

In step 206, active application 1 108 may respond to the SELECT command (or internal command) by sending information about itself, such as the name of application 1 108 (e.g., “BankA Credit Card”) for example, to reader 100. The response may also include the AID of the application responding, in which case the identified application may respond, not with the application's internal AID, but with the AID of application manager 1 104; otherwise, reader 100 may reject the response, since from the point of view of reader 100, the application that responded (i.e., application 1 108) was not the application to which the request was sent (i.e., application manager 1 104).

The remainder of the communication between reader 100 and device 102 may follow the same basic process: reader 100 may send a request to application manager 1 104; application manager 1 104 may forward or reissue the request internally to application 1 108; application 1 108 may send a response back to reader 100. In an alternate embodiment, application 1 108 may send a response to another entity within device 102, such as application manager 1 104, which may forward or reissue the response to reader 100. Steps 208 through 218 illustrate an example payment transaction. In steps 208, 210, and 212, reader 100 may request and receive processing options in preparation for the execution of a financial transaction. In steps 214, 216, and 218, reader 100 may request and receive one or more data records. The data conveyed to reader 100 may include, for example, the equivalent of the data contained on tracks 1 and 2 of a magstripe device, such as the name of the account holder or card holder, the account number, the expiration date, etc. Steps 214 through 218 may be repeated as many times as necessary to complete the transaction. In some embodiments, the wireless smart device may prompt the user for a personal identification number (PIN) or other authorization code. If reader 100 determines that the transaction is valid, it may complete the process by executing the payment transaction with the bank, financial institution, or other issuing authority of the account represented by the active payment application.

FIG. 3 is a message flow diagram illustrating the steps of an exemplary application selection according to an embodiment of the subject matter described herein. Referring to FIG. 3, user 300, in step 302, invokes application selection function 118 in preparation for making a transaction. Alternatively, application selection function 118 may be invoked by device 102 as part of a wireless transaction, for example, to give user 300 an opportunity to verify that the desired application is currently activated. In step 304, application selection function 118 may present to user 300 a list of available applications from which user 300 may select an application to be activated. The list may be limited to include only those types of applications that are supported by reader 100 (not shown). In step 306, user 300 may select application 2 110. Alternatively, application selection function 118 may determine that there is only one application of the type supported by reader 100, and activate that application without user interaction, in which case step 302 through step 306 do not occur. In step 308, in response to selection, by user 300 or otherwise, of an application to be activated, application selection function 118 may deactivate any currently active instance of the same application, such as application 1 108. In step 310, application selection function 118 may notify application manager 1 104 that previously activated application 1 108, which it manages, has been deactivated. In step 312, application selection function 118 may activate the selected application, application 2 110. In step 314, application selection function 118 may notify application manager 1 104 that previously inactive application 2 110, which it manages, has been activated.

It should be noted that the activation and deactivation of instances of one application may not affect the status of instances of another application. Referring to FIG. 1, for example, activating application 2 110 may cause previously active application 1 108 to be deactivated, but the status of application 4 114 and application 5 116 may not be affected, since they are instances of one application while application 1 108, application 2 110, and application 3 112 are instances of another, different application. Alternatively, activation of one application may cause all other applications or instances of applications, regardless of application or type, to be deactivated. For example, activating application 4 114 may deactivate not only application 5 116, but also application 1 108, application 2 110, and application 3 112.

In an alternate embodiment, application selection function 118 may, in response to selection, by user 300 or otherwise, notify application manager 1 104 that one of its managed applications has been selected for activation. In response to receipt of that notification, application manager 1 104, rather than application selection function 118, may deactivate currently active instances of the selected application and activate the selected instance of the application. In embodiments where an application manager manages different applications, application manager 1 104, rather than application selection function 118, may activate selected applications either with or without deactivating applications that were active prior to operation of application selection function 118.

In embodiments where in response to a request from reader 100 for information about available applications residing with device 102, device 102 communicates a list containing a list of available applications within device 102, that list may be dynamically modified by application selection function 118 such that when an instance or application is selected to be active, the list is changed so that the list includes the selected application. Optionally, the list may be further modified to remove from the list instances or applications that were not selected. In this way, when reader 100 receives the list of available applications from device 102, that list may be reduced or constrained to contain only one instance or application, thus removing from reader 100 the need or ability to make its own selection process. This allows user 300, rather than reader 100, to control which application will be used by reader 100. For example, for embodiments in which device 102 uses a PSE to communicate the list of available applications to reader 100, the list returned may contain only the last instance or application activated by application selection function 118.

It will be understood that various details of the subject matter described herein may be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation.

Claims (78)

1. A system for supporting a plurality of instances of the same application, the system comprising:
a wireless smart device for communicating with a wireless reader, the wireless smart device including:
(a) a plurality of instances of a same application for performing wireless transactions with an external device, each of the plurality of instances of the application having a different first application identifier and each of the plurality of instances of the application being of a same type, which has a second application identifier that is different from any of the first application identifiers, wherein the application is an entity that performs a function and wherein the instances are entities that perform the function; and
(b) an application manager for identifying one of the instances associated with the second application identifier as active, for detecting a request from the wireless reader for performing a wireless transaction with an application, the request identifying the application by the second application identifier, and for communicating the request to the identified active instance and identifying the active instance using its respective first application identifier.
2. The system of claim 1 wherein the wireless smart device comprises one of a mobile telephone, a key fob, a physical card, a personal digital assistant, and a device provisioned with a soft card.
3. The system of claim 1 wherein the wireless smart device is adapted to communicate using a close-proximity wireless technology.
4. The system of claim 1 wherein the wireless smart device is adapted to communicate using a near field communications technology.
5. The system of claim 1 wherein the application comprises an application for effecting identity transactions.
6. The system of claim 1 wherein the application comprises an application for effecting security transactions.
7. The system of claim 1 wherein the application comprises an application for effecting authentication transactions.
8. The system of claim 1 wherein the application comprises an application for effecting membership transactions.
9. The system of claim 1 wherein the application comprises an application for effecting loyalty transactions.
10. The system of claim 1 wherein the application comprises an application for effecting electronic payment transactions.
11. The system of claim 1 wherein the application manager, by communicating with the active instance, makes the wireless smart device comply with a specification that limits the number of instances of the same application on the wireless smart device to one or that limits the number of instances of the same application that can respond to requests addressed to the second application identifier to one.
12. The system of claim 1 comprising an application selection function for selecting one of the plurality of instances to be active.
13. The system of claim 12 wherein the application selection function is adapted to present to a user a list of available instances, to receive an instance selection from the user, and in response to the selection to activate the selected instance.
14. The system of claim 12 wherein the application selection function, in response to selecting one of the plurality of instances to be active, deactivates any instance that is not the instance selected to be active.
15. The system of claim 12 comprising an application listing function for detecting the request from the wireless reader for a list of applications available within the wireless smart device, and responsive to detecting that request, communicating the list of available applications to the wireless reader, and wherein the application selection function is adapted to modify, in response to selecting one of the plurality of instances to be active, the list of available applications such that the selected instance is included in the list of available applications.
16. The system of claim 15 wherein the application selection function is adapted to modify, in response to selecting one of the plurality of instances to be active, the list of available applications such that instances that are not the selected instance are removed from the list of available applications.
17. The system of claim 15 wherein the application listing function is performed by a payment system environment (PSE) application.
18. A system for supporting a plurality of applications, the system comprising:
a wireless smart device including:
(a) a plurality of applications for performing wireless transactions with an external device, each application having a different first application identifier, wherein at least some of the applications are of a same type, which has a second application identifier that is different from any of the first application identifiers, wherein each application is an entity that performs a function; and
(b) an application manager for detecting a request from a wireless reader for performing a wireless transaction with an application the request identifying the application by the second application identifier, for identifying one of the applications associated with the second application identifier as the target of the request, for determining that the identified target application is active, and, responsive to the determination, communicating the request to the identified target application and identifying the target application using its respective first application identifier.
19. The system of claim 18 wherein the wireless smart device comprises one of a mobile telephone, a key fob, a physical card, a personal digital assistant, and a device provisioned with a soft card.
20. The system of claim 18 wherein the wireless smart device is adapted to communicate using a close-proximity wireless technology.
21. The system of claim 18 wherein the wireless smart device is adapted to communicate using a near field communications technology.
22. The system of claim 18 wherein the plurality of applications includes an application for effecting identity transactions.
23. The system of claim 18 wherein the plurality of applications includes an application for effecting security transactions.
24. The system of claim 18 wherein the plurality of applications includes an application for effecting authentication transactions.
25. The system of claim 18 wherein the plurality of applications includes an application for effecting membership transactions.
26. The system of claim 18 wherein the plurality of applications includes an application for effecting loyalty transactions.
27. The system of claim 18 wherein the plurality of applications includes an application for effecting electronic payment transactions.
28. The system of claim 18 wherein the plurality of applications includes a plurality of applications of the same type.
29. The system of claim 18 wherein the plurality of applications includes a plurality of instances of the same application.
30. The system of claim 18 wherein the application manager, by communicating with the active application, makes the wireless smart device comply with a specification that limits the number of applications of the same type on the wireless smart device to one or that limits the number of applications that can respond to requests addressed to the second application identifier to one.
31. The system of claim 18 comprising an application selection function for selecting one of the plurality of applications to be active.
32. The system of claim 31 wherein the application selection function is adapted to present to a user a list of available applications, to receive an application selection from the user, and in response to the selection to activate the selected application.
33. The system of claim 31 wherein the application selection function, in response to selecting one of the plurality of instances to be active, deactivates any instance that is not the instance selected to be active.
34. The system of claim 31 comprising an application listing function for detecting a request from the wireless reader for a list of applications available within the wireless smart device, and responsive to detecting that request, communicating a list of available applications to the wireless reader, and wherein the application selection function is adapted to modify, in response to selecting one of the plurality of instances to be active, the list of available applications such that the selected instance is included in the list of available applications.
35. The system of claim 34 wherein the application selection function is adapted to modify, in response to selecting one of the plurality of instances to be active, the list of available applications such that instances that are not the selected instance are removed from the list of available applications.
36. The system of claim 34 wherein the application listing function is performed by a payment system environment (PSE) application.
37. A method for supporting a plurality of instances of the same application on a wireless smart device, the method comprising:
(a) using an application manager residing within the wireless smart device having a plurality of instances of a same application for effecting wireless transactions with an external device, each of the plurality of instances of the application having a different first application identifier and each of the plurality of instances of the application being of a same type, which has a second application identifier that is different from any of the first application identifiers, wherein the application is an entity that performs a function and wherein the instances are entities that perform the function:
i) receiving a request from a wireless reader for effecting a transaction with an application, the request identifying the application by the second application identifier; and
ii) responsive to the request from the wireless reader, identifying one of the instances associated with the second application identifier and; residing within the wireless smart device as active, and sending the request for effecting the transaction to the identified active instance and identifying the active instance using its respective first application identifier; and
(b) using the active instance identified using its respective first application identifier and associated with the second application identifier:
i) receiving the request from the application manager for effecting the transaction; and
ii) responsive to the request from the application manager, effecting the transaction.
38. The method of claim 37 wherein using the wireless smart device comprises using one of a mobile telephone, a key fob, a physical card, a personal digital assistant, and a device provisioned as a soft card.
39. The method of claim 37 wherein receiving a request from and sending a response to the wireless reader includes communicating using a close-proximity wireless technology.
40. The method of claim 37 wherein receiving a request from and sending a response to the wireless reader includes communicating using a near field communications technology.
41. The method of claim 37 wherein the application comprises an application for effecting identity transactions.
42. The method of claim 37 wherein the application comprises an application for effecting security transactions.
43. The method of claim 37 wherein the application comprises an application for effecting authentication transactions.
44. The method of claim 37 wherein the application comprises an application for effecting membership transactions.
45. The method of claim 37 wherein the application comprises an application for effecting loyalty transactions.
46. The method of claim 37 wherein the application comprises an application for effecting electronic payment transactions.
47. The method of claim 37 wherein receiving the request from a wireless reader includes receiving a request for effecting a wireless payment transaction.
48. The method of claim 37 wherein effecting the transaction includes sending a response to the wireless reader using the active instance.
49. The method of claim 37 wherein effecting the transaction includes sending a response to the application manager using the active instance and, in response to receiving, by the application manager, a response from the active instance, sending a response to the wireless reader using the application manager.
50. The method of claim 37 wherein, by using the application manager for communicating with the active instance, the wireless smart device complies with a specification that limits the number of instances of the same application on the wireless smart device to one or that limits the number of instances of the same application that can respond to requests addressed to the second application identifier to one.
51. The method of claim 37 comprising selecting, using an application selection function, one of the plurality of instances and activating the selected instance.
52. The method of claim 51 wherein using the application selection function includes presenting to a user a list of available instances from which the user may select an instance to be activated, determining which instance is selected by the user, and responsive to the determination, activating the selected instance.
53. The method of claim 51 wherein using the application selection function includes deactivating any instance that is not the selected instance.
54. The method of claim 51 comprising detecting a request from the wireless reader for a list of applications available within the wireless smart device, and responsive to detecting that request, communicating a list of available applications to the wireless reader, and wherein using the application selection function includes modifying, in response to selecting one of the plurality of instances, the list of available applications to include in the list of available applications the selected instance.
55. The method of claim 54 comprising modifying, in response to selecting one of the plurality of instances, the list of available applications to remove from the list of available applications any instance that is not the selected instance.
56. The method of claim 54 including using a payment system environment (PSE) application for communicating the list of available applications to the wireless reader.
57. A method for supporting a plurality of applications on a wireless smart device, the method comprising:
(a) using an application manager residing within the wireless smart device having a plurality of applications for performing wireless transactions with an external device, each application having a different first application identifier wherein at least some of the applications are of a same type, which has a second application identifier that is different from any of the first application identifiers, wherein each application is an entity that performs a function:
i) receiving a request from a wireless reader for effecting a transaction with an application, the request identifying the application by the second application identifier; and
ii) responsive to the request from the wireless reader, identifying one of the applications associated with the second application identifier and residing within the wireless smart device as a target of the request, determining that the identified target application is active, and, responsive to that determination, communicating the request to the identified target application and identifying the target application using its respective first application identifier; and
(b) using the target application identified using its respective first application identifier and associated with the second application identifier:
i) receiving the request from the application manager for effecting the transaction; and
ii) responsive to the request from the application manager, effecting the transaction.
58. The method of claim 57 wherein using the wireless smart device comprises using one of a mobile telephone, a key fob, a physical card, a personal digital assistant, and a device provisioned as a soft card.
59. The method of claim 57 wherein receiving a request from and sending a response to the wireless reader includes communicating using a close-proximity wireless technology.
60. The method of claim 57 wherein receiving a request from and sending a response to the wireless reader includes communicating using a near field communications technology.
61. The method of claim 57 wherein the plurality of applications includes at least one application for effecting identity transactions.
62. The method of claim 57 wherein the plurality of applications includes at least one application for effecting security transactions.
63. The method of claim 57 wherein the plurality of applications includes at least one application for effecting authentication transactions.
64. The method of claim 57 wherein the plurality of applications includes at least one application for effecting membership transactions.
65. The method of claim 57 wherein the plurality of applications includes at least one application for effecting loyalty transactions.
66. The method of claim 57 wherein the plurality of applications includes at least one application for effecting electronic payment transactions.
67. The method of claim 57 wherein the plurality of applications includes a plurality of applications of the same type.
68. The method of claim 57 wherein effecting the transaction includes sending a response to the wireless reader using the target application.
69. The method of claim 57 wherein effecting the transaction includes sending a response to the application manager using the target application and, in response to receiving, by the application manager, a response from the target application, sending a response to the wireless reader using the application manager.
70. The method of claim 57 wherein, by using the application manager for communicating with the target application, the wireless smart device complies with a specification that limits the number of applications of the same type on the wireless smart device to one or that limits the number of applications that can respond to requests addressed to the second application identifier to one.
71. The method of claim 57 comprising selecting, using an application selection function, one of the plurality of applications and activating the selected application.
72. The method of claim 71 wherein using the application selection function includes presenting to a user a list of available applications from which the user may select an application to be activated, determining which application is selected by the user, and responsive to the determination, activating the selected application.
73. The method of claim 71 wherein using the application function includes deactivating any application that is not the selected application.
74. The method of claim 71 comprising detecting a request from the wireless reader for a list of applications available within the wireless smart device, and responsive to detecting that request, communicating a list of available applications to the wireless reader, and wherein using the application selection function includes modifying, in response to selecting one of the plurality of applications, the list of available applications to include in the list of available applications the selected application.
75. The method of claim 74 comprising modifying, in response to selecting one of the plurality of applications, the list of available applications to remove from the list of available applications any application that is not the selected application.
76. The method of claim 74 including using a payment system environment (PSE) application for communicating the list of available applications to the wireless reader.
77. A computer program product comprising computer-executable instructions embodied in a computer-readable medium for performing steps comprising:
(a) using an application manager residing within the wireless smart device having a plurality of instances of a same application for effecting wireless transactions with an external device, each application having a different first application identifier wherein at least some of the applications are of a same type, which has a second application identifier that is different from any of the first application identifiers, wherein the application is an entity that performs a function and wherein the instances are entities that perform the function:
i) receiving a request from a wireless reader for effecting a transaction with an application, the request identifying the application by the second application identifier; and
ii) responsive to the request from the wireless reader, identifying one of the instances associated with the second application identifier and residing within the wireless smart device as active, and sending the request for effecting the transaction to the identified active instance and identifying the active instance using its respective first application identifier; and
(b) using the active instance identified using its respective first application identifier and associated with the second application identifier:
i) receiving the request from the application manager for effecting the transaction; and
ii) responsive to the request from the application manager, effecting the transaction.
78. A computer program product comprising computer-executable instructions embodied in a computer-readable medium for performing steps comprising:
(a) using an application manager residing within the wireless smart device having a plurality of applications for performing wireless transactions with an external device, each application having a different first application identifier, wherein at least some of the applications are of a same type, which has a second application identifier that is different from any of the first application identifiers, wherein each application is an entity that performs a function:
i) receiving a request from a wireless reader for effecting a transaction with an application, the request identifying the application by the second application identifier; and
ii) responsive to the request from the wireless reader, identifying one of the applications associated with the second application identifier and residing within the wireless smart device as a target of the request, determining that the identified target application is active, and, responsive to that determination, communicating the request to the identified target application and identifying the target application using its respective first application identifier; and
(b) using the target application identified using its respective first application identifier and associated with the second application identifier:
i) receiving the request from the application manager for effecting the transaction; and
ii) responsive to the request from the application manager, effecting the transaction.
US11/641,557 2006-12-19 2006-12-19 Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device Active US7631810B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US11/641,557 US7631810B2 (en) 2006-12-19 2006-12-19 Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US11/641,557 US7631810B2 (en) 2006-12-19 2006-12-19 Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device
TW96147874A TWI437502B (en) 2006-12-19 2007-12-14 Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device
EP07150164A EP1939822A1 (en) 2006-12-19 2007-12-19 Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device
SG200718878-2A SG144103A1 (en) 2006-12-19 2007-12-19 Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device

Publications (2)

Publication Number Publication Date
US20080147508A1 US20080147508A1 (en) 2008-06-19
US7631810B2 true US7631810B2 (en) 2009-12-15

Family

ID=39301768

Family Applications (1)

Application Number Title Priority Date Filing Date
US11/641,557 Active US7631810B2 (en) 2006-12-19 2006-12-19 Systems, methods, and computer program products for supporting multiple applications and multiple instances of the same application on a wireless smart device

Country Status (4)

Country Link
US (1) US7631810B2 (en)
EP (1) EP1939822A1 (en)
SG (1) SG144103A1 (en)
TW (1) TWI437502B (en)

Cited By (37)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100051685A1 (en) * 2008-09-03 2010-03-04 First Data Corporation Enabling consumer choice on contactless transactions when using a dual-branded payment instrument
US8171525B1 (en) 2011-09-15 2012-05-01 Google Inc. Enabling users to select between secure service providers using a central trusted service manager
US8196131B1 (en) 2010-12-17 2012-06-05 Google Inc. Payment application lifecycle management in a contactless smart card
US8255687B1 (en) 2011-09-15 2012-08-28 Google Inc. Enabling users to select between secure service providers using a key escrow service
US8297520B1 (en) 2011-09-16 2012-10-30 Google Inc. Secure application directory
US8335921B2 (en) 2010-12-17 2012-12-18 Google, Inc. Writing application data to a secure element
US8335932B2 (en) 2010-12-17 2012-12-18 Google Inc. Local trusted services manager for a contactless smart card
US8385553B1 (en) 2012-02-28 2013-02-26 Google Inc. Portable secure element
FR2980867A1 (en) * 2011-10-04 2013-04-05 Inside Secure Method and system to execute a contactless transaction allowing multiple applications and multiple instances of the same application
US8429409B1 (en) 2012-04-06 2013-04-23 Google Inc. Secure reset of personal and service provider information on mobile devices
US8645222B1 (en) 2009-03-20 2014-02-04 Jpmorgan Chase Bank, N.A. System and methods for mobile ordering and payment
US8774721B2 (en) 2012-04-10 2014-07-08 Google Inc. Detecting a communication tap via signal monitoring
US8799163B1 (en) 2003-09-04 2014-08-05 Jpmorgan Chase Bank, N.A. System and method for financial instrument pre-qualification and offering
US8875228B2 (en) 2011-11-01 2014-10-28 Jvl Ventures, Llc Systems, methods, and computer program products for managing secure elements
US9008616B2 (en) 2011-08-19 2015-04-14 Google Inc. Point of sale processing initiated by a single tap
US9286049B2 (en) 2013-03-26 2016-03-15 Google Inc. Systems, methods, and computer program products for managing service installation
US9292345B2 (en) 2013-07-08 2016-03-22 Google Inc. Systems, methods, and computer program products for processing sets of instructions for mobile devices
US9311491B2 (en) 2013-09-30 2016-04-12 Google Inc. Systems, methods, and computer program products for securely managing data on a secure element
US9355391B2 (en) 2010-12-17 2016-05-31 Google Inc. Digital wallet
US9390414B2 (en) 2011-09-18 2016-07-12 Google Inc. One-click offline buying
US9408075B2 (en) 2013-06-17 2016-08-02 Google Inc. Systems, methods, and computer program products for processing a request relating to a mobile communication device
US9479571B2 (en) 2012-09-18 2016-10-25 Google Inc. Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements
US9495558B2 (en) 2013-03-26 2016-11-15 Google Inc. Systems, methods, and computer program products for managing access control
US9544759B2 (en) 2011-11-01 2017-01-10 Google Inc. Systems, methods, and computer program products for managing states
US9563891B2 (en) 2012-07-09 2017-02-07 Google Inc. Systems, methods, and computer program products for integrating third party services with a mobile wallet
US9572029B2 (en) 2012-04-10 2017-02-14 Imprivata, Inc. Quorum-based secure authentication
US9646302B2 (en) 2013-03-26 2017-05-09 Google Inc. Systems, methods, and computer program products for managing wallet activation
US9697516B2 (en) 2013-10-10 2017-07-04 Google Inc. System, methods, and computer program products for storing and managing program data
US9767287B2 (en) 2013-01-25 2017-09-19 Google Inc. Systems, methods, and computer program products for managing data re-installation
US9794353B2 (en) 2013-12-19 2017-10-17 Google Inc. Systems, methods, and computer program products for service processing
US9811825B2 (en) 2013-10-10 2017-11-07 Google Inc. Systems, methods, and computer program products for managing contactless transactions
US9898737B2 (en) 2012-01-30 2018-02-20 Honeywell International, Inc. Methods and systems employing time and/or location data for use in transactions
US10003969B2 (en) 2013-12-19 2018-06-19 Google Llc Communication between mobile devices and mobile wallet architectures
US10007906B2 (en) 2011-11-17 2018-06-26 Abdolreza Behjat Using a mobile device in a commercial transaction
US10127533B2 (en) 2012-07-31 2018-11-13 Google Llc Managing devices associated with a digital wallet account
US10311428B2 (en) 2012-05-24 2019-06-04 Google Llc Systems, methods, and computer program products for providing a contactless protocol
US10387873B2 (en) 2017-01-12 2019-08-20 Google Llc Systems, methods, and computer program products for integrating third party services with a mobile wallet

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110276420A1 (en) * 2008-09-17 2011-11-10 Robert White Cash card system
FR2945143B1 (en) * 2009-05-04 2012-07-06 Bnp Paribas Method and system activation of contactless payment applications
US8745250B2 (en) * 2009-06-30 2014-06-03 Intel Corporation Multimodal proximity detection
US8186602B2 (en) * 2009-08-18 2012-05-29 On Track Innovations, Ltd. Multi-application contactless smart card
WO2011127084A2 (en) 2010-04-05 2011-10-13 Vivotech, Inc. Systems, methods, and computer readable media for performing multiple transactions through a single near field communication (nfc) tap
US8799087B2 (en) * 2010-10-27 2014-08-05 Mastercard International Incorporated Systems, methods, and computer readable media for utilizing one or more preferred application lists in a wireless device reader
FR2968804B1 (en) * 2010-12-13 2013-01-04 St Microelectronics Rousset Process for dialogue management between equipment and at least one multi-application object such as a smart card and contactless corresponding object
US8862767B2 (en) * 2011-09-02 2014-10-14 Ebay Inc. Secure elements broker (SEB) for application communication channel selector optimization
FR2991082B1 (en) * 2012-05-24 2015-02-20 Morpho Application Management
US10121144B2 (en) * 2013-11-04 2018-11-06 Apple Inc. Using biometric authentication for NFC-based payments
CN105741106A (en) * 2016-01-29 2016-07-06 宇龙计算机通信科技(深圳)有限公司 Selection method and device of NFC (Near Field Communication) payment way
DE102017002151A1 (en) * 2017-03-06 2018-09-06 Giesecke+Devrient Mobile Security Gmbh Card Device with applets and transfer of APDUs to applets

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000008611A1 (en) 1998-08-06 2000-02-17 Visa International Service Association Terminal software architecture for use with smart cards
US6220510B1 (en) * 1997-05-15 2001-04-24 Mondex International Limited Multi-application IC card with delegation feature
US6317832B1 (en) * 1997-02-21 2001-11-13 Mondex International Limited Secure multiple application card system and process
US6564995B1 (en) * 1997-09-19 2003-05-20 Schlumberger Malco, Inc. Smart card application-selection
US6612486B2 (en) * 2001-12-19 2003-09-02 Hitachi, Ltd. Smart card managing system
US20040118930A1 (en) * 2001-07-10 2004-06-24 American Express Travel Related Services Company, Inc. Transparent transaction card
US6776332B2 (en) * 2002-12-26 2004-08-17 Micropin Technologies Inc. System and method for validating and operating an access card
US6824064B2 (en) * 2000-12-06 2004-11-30 Mobile-Mind, Inc. Concurrent communication with multiple applications on a smart card
US20080212558A1 (en) * 2005-01-19 2008-09-04 Gemplus Communication Set Up Between Wireless Devices

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6317832B1 (en) * 1997-02-21 2001-11-13 Mondex International Limited Secure multiple application card system and process
US6220510B1 (en) * 1997-05-15 2001-04-24 Mondex International Limited Multi-application IC card with delegation feature
US6564995B1 (en) * 1997-09-19 2003-05-20 Schlumberger Malco, Inc. Smart card application-selection
WO2000008611A1 (en) 1998-08-06 2000-02-17 Visa International Service Association Terminal software architecture for use with smart cards
US20020175207A1 (en) 1998-08-06 2002-11-28 Forough Kashef Terminal software architecture for use with smart cards
US6824064B2 (en) * 2000-12-06 2004-11-30 Mobile-Mind, Inc. Concurrent communication with multiple applications on a smart card
US20040118930A1 (en) * 2001-07-10 2004-06-24 American Express Travel Related Services Company, Inc. Transparent transaction card
US6612486B2 (en) * 2001-12-19 2003-09-02 Hitachi, Ltd. Smart card managing system
US6776332B2 (en) * 2002-12-26 2004-08-17 Micropin Technologies Inc. System and method for validating and operating an access card
US20080212558A1 (en) * 2005-01-19 2008-09-04 Gemplus Communication Set Up Between Wireless Devices

Non-Patent Citations (9)

* Cited by examiner, † Cited by third party
Title
"Frequently Asked Questions-MasterCard Paypass Specifications", MasterCard International Incorporated, 5-11257, pp. 1-4 (Jul. 2005).
"MasterCard Paypass-Terminal Implementation Guide", MasterCard International Incorporated, pp. 1-61 (2004).
Baentsch et al., "JavaCard-From Hype to Reality," IEEE Concurrency, pp. 36-43 (Oct. 1999).
Chen at al., "Understanding Java Card 2.0," http://www.javaworld.com, pp. 1-10 (Mar. 1998).
Communication pursuant to Article 94(3) for European Application No. 07150164.7 (Nov. 6, 200).
EMV, "Integrated Circuit Card-Specifications for Payment Systems-Book 1-Application Independent ICC to Terminal Interface Requirements", EMVCo, LLC, Version 4.1 (May 2004).
EMV, "Integrated Circuit Card-Specifications for Payment Systems-Book 3 -Application Specification", EMVCo, LLC, Version 4.1 (May 2004) .
European Search Report for European Application No. 07150164.7-2221 (May 8, 2008).
Hauke Meyn, "Identification cards-Contactless integrated circuit(s) cards-Proximity cards-Part 4: Transmission protocol", International Organisation for Standardisation, ISO/IEC JTC 1/SC 17/WG 8 (Mar. 10, 2000).

Cited By (67)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8799163B1 (en) 2003-09-04 2014-08-05 Jpmorgan Chase Bank, N.A. System and method for financial instrument pre-qualification and offering
US20100051685A1 (en) * 2008-09-03 2010-03-04 First Data Corporation Enabling consumer choice on contactless transactions when using a dual-branded payment instrument
US8523053B2 (en) * 2008-09-03 2013-09-03 First Data Corporation Enabling consumer choice on contactless transactions when using a dual-branded payment instrument
US9886706B2 (en) 2009-03-20 2018-02-06 Jpmorgan Chase Bank, N.A. Systems and methods for mobile ordering and payment
US8645222B1 (en) 2009-03-20 2014-02-04 Jpmorgan Chase Bank, N.A. System and methods for mobile ordering and payment
US9230259B1 (en) 2009-03-20 2016-01-05 Jpmorgan Chase Bank, N.A. Systems and methods for mobile ordering and payment
US8352749B2 (en) 2010-12-17 2013-01-08 Google Inc. Local trusted services manager for a contactless smart card
US8335932B2 (en) 2010-12-17 2012-12-18 Google Inc. Local trusted services manager for a contactless smart card
US8806199B2 (en) 2010-12-17 2014-08-12 Google Inc. Writing application data to a secure element
US8793508B2 (en) 2010-12-17 2014-07-29 Google Inc. Local trusted services manager for a contactless smart card
US9355391B2 (en) 2010-12-17 2016-05-31 Google Inc. Digital wallet
US8196131B1 (en) 2010-12-17 2012-06-05 Google Inc. Payment application lifecycle management in a contactless smart card
US8646059B1 (en) 2010-12-17 2014-02-04 Google Inc. Wallet application for interacting with a secure element application without a trusted server for authentication
US8335921B2 (en) 2010-12-17 2012-12-18 Google, Inc. Writing application data to a secure element
US9691055B2 (en) 2010-12-17 2017-06-27 Google Inc. Digital wallet
US8621168B2 (en) 2010-12-17 2013-12-31 Google Inc. Partitioning the namespace of a contactless smart card
US8807440B1 (en) 2010-12-17 2014-08-19 Google Inc. Routing secure element payment requests to an alternate application
US9008616B2 (en) 2011-08-19 2015-04-14 Google Inc. Point of sale processing initiated by a single tap
US8171525B1 (en) 2011-09-15 2012-05-01 Google Inc. Enabling users to select between secure service providers using a central trusted service manager
US9450927B2 (en) 2011-09-15 2016-09-20 Google Inc. Enabling users to select between secure service providers using a key escrow service
US8255687B1 (en) 2011-09-15 2012-08-28 Google Inc. Enabling users to select between secure service providers using a key escrow service
US8412933B1 (en) 2011-09-15 2013-04-02 Google Inc. Enabling users to select between secure service providers using a key escrow service
US8379863B1 (en) 2011-09-15 2013-02-19 Google Inc. Enabling users to select between secure service providers using a central trusted service manager
US8737621B2 (en) 2011-09-15 2014-05-27 Google Inc. Enabling users to select between secure service providers using a central trusted service manager
US8297520B1 (en) 2011-09-16 2012-10-30 Google Inc. Secure application directory
US8511573B2 (en) 2011-09-16 2013-08-20 Google Inc. Secure application directory
US8313036B1 (en) 2011-09-16 2012-11-20 Google Inc. Secure application directory
US10134025B2 (en) 2011-09-18 2018-11-20 Google Llc One-click offline buying
US9390414B2 (en) 2011-09-18 2016-07-12 Google Inc. One-click offline buying
FR2980867A1 (en) * 2011-10-04 2013-04-05 Inside Secure Method and system to execute a contactless transaction allowing multiple applications and multiple instances of the same application
US9600816B2 (en) * 2011-10-04 2017-03-21 Inside Secure Method and system for executing a NFC transaction supporting multiple applications and multiples instances of a same application
WO2013050684A1 (en) 2011-10-04 2013-04-11 Inside Secure Method and system for executing a contactless transaction allowing multiple applications and multiple instances of the same application
US20140188713A1 (en) * 2011-10-04 2014-07-03 Inside Secure Method and system for executing a nfc transaction supporting multiple applications and multiples instances of a same application
US8875228B2 (en) 2011-11-01 2014-10-28 Jvl Ventures, Llc Systems, methods, and computer program products for managing secure elements
US9104887B2 (en) 2011-11-01 2015-08-11 Google Inc. Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements
US9652628B2 (en) 2011-11-01 2017-05-16 Google Inc. Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements
US10114976B2 (en) 2011-11-01 2018-10-30 Google Llc Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements
US9928382B2 (en) 2011-11-01 2018-03-27 Google Llc Systems, methods, and computer program products for managing secure elements
US9323945B2 (en) 2011-11-01 2016-04-26 Google Inc. Systems, methods, and computer program products for managing secure elements
US9544759B2 (en) 2011-11-01 2017-01-10 Google Inc. Systems, methods, and computer program products for managing states
US10007906B2 (en) 2011-11-17 2018-06-26 Abdolreza Behjat Using a mobile device in a commercial transaction
US9898737B2 (en) 2012-01-30 2018-02-20 Honeywell International, Inc. Methods and systems employing time and/or location data for use in transactions
US8385553B1 (en) 2012-02-28 2013-02-26 Google Inc. Portable secure element
US8625800B2 (en) 2012-02-28 2014-01-07 Google Inc. Portable secure element
US8429409B1 (en) 2012-04-06 2013-04-23 Google Inc. Secure reset of personal and service provider information on mobile devices
US8971533B2 (en) 2012-04-06 2015-03-03 Google Inc. Secure reset of personal and service provider information on mobile devices
US9572029B2 (en) 2012-04-10 2017-02-14 Imprivata, Inc. Quorum-based secure authentication
US9198214B2 (en) 2012-04-10 2015-11-24 Google Inc. Detecting a communication tap via signal monitoring
US8774721B2 (en) 2012-04-10 2014-07-08 Google Inc. Detecting a communication tap via signal monitoring
US10311428B2 (en) 2012-05-24 2019-06-04 Google Llc Systems, methods, and computer program products for providing a contactless protocol
US9563891B2 (en) 2012-07-09 2017-02-07 Google Inc. Systems, methods, and computer program products for integrating third party services with a mobile wallet
US10127533B2 (en) 2012-07-31 2018-11-13 Google Llc Managing devices associated with a digital wallet account
US10057773B2 (en) 2012-09-18 2018-08-21 Google Llc Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements
US9479571B2 (en) 2012-09-18 2016-10-25 Google Inc. Systems, methods, and computer program products for interfacing multiple service provider trusted service managers and secure elements
US9767287B2 (en) 2013-01-25 2017-09-19 Google Inc. Systems, methods, and computer program products for managing data re-installation
US9646302B2 (en) 2013-03-26 2017-05-09 Google Inc. Systems, methods, and computer program products for managing wallet activation
US9286049B2 (en) 2013-03-26 2016-03-15 Google Inc. Systems, methods, and computer program products for managing service installation
US9495558B2 (en) 2013-03-26 2016-11-15 Google Inc. Systems, methods, and computer program products for managing access control
US9408075B2 (en) 2013-06-17 2016-08-02 Google Inc. Systems, methods, and computer program products for processing a request relating to a mobile communication device
US9292345B2 (en) 2013-07-08 2016-03-22 Google Inc. Systems, methods, and computer program products for processing sets of instructions for mobile devices
US9608979B2 (en) 2013-09-30 2017-03-28 Google Inc. Systems, methods, and computer program products for securely managing data on a secure element
US9311491B2 (en) 2013-09-30 2016-04-12 Google Inc. Systems, methods, and computer program products for securely managing data on a secure element
US9697516B2 (en) 2013-10-10 2017-07-04 Google Inc. System, methods, and computer program products for storing and managing program data
US9811825B2 (en) 2013-10-10 2017-11-07 Google Inc. Systems, methods, and computer program products for managing contactless transactions
US9794353B2 (en) 2013-12-19 2017-10-17 Google Inc. Systems, methods, and computer program products for service processing
US10003969B2 (en) 2013-12-19 2018-06-19 Google Llc Communication between mobile devices and mobile wallet architectures
US10387873B2 (en) 2017-01-12 2019-08-20 Google Llc Systems, methods, and computer program products for integrating third party services with a mobile wallet

Also Published As

Publication number Publication date
US20080147508A1 (en) 2008-06-19
EP1939822A1 (en) 2008-07-02
SG144103A1 (en) 2008-07-29
TW200839637A (en) 2008-10-01
TWI437502B (en) 2014-05-11

Similar Documents

Publication Publication Date Title
KR101802862B1 (en) The electronic payment application system and payment authorization method
AU2007261035B2 (en) Portable consumer device configured to generate dynamic authentication data
US9456027B2 (en) Methods, secure element, server, computer programs and computer program products for improved application management
KR101789113B1 (en) A payment terminal using a mobile communication device, such as a mobile phone;a method of direct debit payment transaction
US8811895B2 (en) System and method for presentation of multiple NFC credentials during a single NFC transaction
KR101632465B1 (en) Amplifying radio frequency signals
AU2007249461B2 (en) System and method for activating telephone-based payment instrument
US6776339B2 (en) Wireless communication device providing a contactless interface for a smart card reader
CN101809633B (en) Wirelessly executing transactions with different enterprises
US8060012B2 (en) Method and apparatus for automatic near field communication application selection in an electronic device
KR101194509B1 (en) Method and apparatus for automatic application selection in an electronic device using multiple discovery managers
JP4987125B2 (en) Method for managing access to a trusted application, system, Trusted Service Manager, a service provider and a memory device
KR101802303B1 (en) Systems, methods, and computer readable media for payment and non-payment virtual card transfer between mobile devices
EP2332092B1 (en) Apparatus and method for preventing unauthorized access to payment application installed in contactless payment device
EP3038034A1 (en) Secure mobile payment system
US8977195B2 (en) Multiple NFC card applications in multiple execution environments
US20080027815A1 (en) Methods, systems and computer program products for wireless payment transactions
US20090271315A1 (en) Portable device including alterable indicator
US9224140B2 (en) Near field communication activation and authorization
US20100330958A1 (en) Mobile communication device and method for disabling applications
US20050006461A1 (en) System and method for managing electronic data transfer applications
US20150186864A1 (en) Processing a transaction using multiple application identifiers
JP6419925B2 (en) Systems, methods, and computer program products for providing contactless protocols
US20020174336A1 (en) Information protection system and information protection method
EP3487155A1 (en) Method, device and computer program product for network-based remote control over contactless secure storages

Legal Events

Date Code Title Description
AS Assignment

Owner name: VIVOTECH, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:LIU, MING-LI;KUMAR, PRADEEP;JOHNSON, WILLIAM S., JR.;REEL/FRAME:018941/0701

Effective date: 20070206

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: SILICON VALLEY BANK, CALIFORNIA

Free format text: SECURITY AGREEMENT;ASSIGNOR:VIVOTECH, INC.;REEL/FRAME:024864/0849

Effective date: 20100526

AS Assignment

Owner name: VIVOTECH INC, CALIFORNIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SILICON VALLEY BANK;REEL/FRAME:028849/0225

Effective date: 20120820

AS Assignment

Owner name: VIVOTECH (ASSIGNMENT FOR THE BENEFIT OF CREDITORS)

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VIVOTECH, INC.;REEL/FRAME:029036/0100

Effective date: 20120806

Owner name: MASTERCARD INTERNATIONAL INCORPORATED, NEW YORK

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VIVOTECH (ASSIGNMENT FOR THE BENEFIT OF CREDITORS), LLC;REEL/FRAME:029036/0242

Effective date: 20120813

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8