JP6957623B2 - Express credential transaction system - Google Patents

Description

(Cross-reference of related applications)
This application claims the interests of US Provisional Patent Application No. 62 / 384,162, entitled "Express Credentialal Transition System," filed on September 6, 2016, in its entirety for all purposes. Incorporated herein by reference to.
The present specification generally relates to contactless transaction systems, including express transactions performed using stored credentials.

In mobile payment systems, payment applets provisioned on secure elements of electronic devices may support credential or card accounts, such as credit card accounts. The payment applet may be used by an electronic device after a legitimate user authenticates with a mobile device (eg, via a fingerprint and / or password) and may be linked to a wireless payment transaction with, for example, a wireless payment terminal. .. For example, after a legitimate user authenticates with an electronic device, the electronic device can use the card account corresponding to the payment applet to send a request for a wireless payment transaction to a wireless payment terminal. The wireless payment terminal can contact the service provider associated with the card account such as a financial institution, and can confirm that the payment can be made using the card account. For example, the service provider can ensure that sufficient funds and / or credits are available to complete the wireless payment transaction. If the service provider confirms that the wireless payment transaction can be completed, the wireless payment terminal completes the wireless payment transaction and returns the indication to the electronic device.

Some features of the subject technology are shown in the appended claims. However, for purposes of illustration, some embodiments of the technique of the present application are shown in the following figures.
FIG. 5 illustrates an exemplary network environment in which an express credential transaction system can be implemented, according to one or more implementations. FIG. 5 illustrates an exemplary network environment, including exemplary electronic devices capable of implementing an express credential transaction system, according to one or more implementations. FIG. 5 illustrates an exemplary electronic device, including exemplary secure elements that can be used in an express credential transaction system, according to one or more implementations. It is a flow diagram of an exemplary process for constructing a newly provisioned stored value payment applet in an express credential transaction system according to one or more implementations. FIG. 5 is a flow diagram of an exemplary process for using an Express Stored Value Payment applet in an Express Credential Transaction System, according to one or more implementations. FIG. 5 is a flow diagram of an exemplary process for designating an express stored value payment applet for a service provider in an express credential transaction system according to one or more implementations. A flow diagram of an exemplary process for locally protecting an electronic device that implements an express credential transaction system for one or more implementations is shown. FIG. 5 is a flow diagram of an exemplary process for remotely protecting an electronic device that implements an express credential transaction system according to one or more implementations. It is a figure which shows the exemplary electronic system which can be carried out with the aspect of the art of the subject which concerns on one or more implementations.

The detailed description described below is intended as an explanation of the various configurations of the subject technology and is not intended to represent the only configuration in which the subject technology can be practiced. The accompanying drawings are incorporated herein and form part of a detailed description. The detailed description includes specific details to provide a complete understanding of the art of the present application. However, the art of the subject is not limited to the particular details presented herein and can be practiced using one or more implementations. In one or more implementations, the structures and components are shown in block diagram format to avoid obscuring the concept of the subject technology.

In mobile payment systems, in addition to the aforementioned payment applets that correspond to credit card accounts, stored value cards such as transit cards or other such prepaid cards (or "truth on the card" or "actual cash value" (or "real cash value" ( One or more stored value payment applets corresponding to ACV) cards) may be provisioned on the secure element of the electronic device. A stored value card can differ from, for example, a credit card in that, for example, the monetary value is stored in the card itself rather than being stored in an external account maintained by a financial institution. In this way, the representation of monetary value can be stored directly (or with) in the stored value payment applet, so that the electronic device requires confirmation or approval from the service provider associated with the stored value payment applet. You can use the stored value payment applet to work with a wireless payment terminal in a wireless payment transaction without having to do so. For example, a stored value payment applet with a wireless transit payment terminal, regardless of whether the wireless transit payment terminal (or device) can communicate with the transit provider to see the monetary value associated with the stored value payment applet. Can be used to perform wireless payment transactions.

Wireless transit payment terminals may be designed to perform high speed wireless payment transactions, such as express payment transactions, so that large numbers of passengers can pass through the terminal and access transit as soon as possible. Even the slightest delay in processing a wireless payment transaction, for example, creating a backup of the passenger, causing the passenger to miss the train, or mass transit such as a bus before the passenger completes his or her wireless payment transaction. It may prevent the vehicle from departing. Thus, when the user of the electronic device needs to provide an input such as authenticating (eg, via fingerprint and / or password entry) before using the stored value payment applet on the wireless transit payment terminal. For example, as in the case of payment applets for credit cards, the latency associated with authentication can cause delays during the processing of wireless payment transactions by wireless transit payment terminals. However, if the user of the electronic device does not need to authenticate to access one of the payment applets, the security of the mobile payment system can be compromised.

The subject system allows the user to specify one or more stored value payment applets provisioned on the secure elements of the electronic system (eg, per service provider) as express stored value payment applets. Provide solutions to these and other issues. Therefore, the express stored value payment applet can be used for any manual input from the user, for example, a wireless payment transaction with a wireless payment terminal such as a wireless transit payment terminal without requiring authentication. In this way, the user can use the user's electronic device near the wireless transit payment terminal without incurring any latency associated with having to authenticate (or provide other inputs) with the electronic device. Can be deployed to perform wireless payment transactions in the same way that users can do with physical transit cards. In addition, the subject system utilizes any non-stored value payment applet, such as one that accepts credit cards, as well as other stored value payment applets associated with service providers not designated as Express. Maintain the security of mobile payment systems by still requiring users to authenticate, as well as to utilize any non-stored value payment applets, such as those that support credit cards.

FIG. 1 shows an exemplary network environment 100 in which an express credential transaction system can be implemented, according to one or more implementations. However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. The arrangement and type of components can be modified without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided.

The network environment 100 includes one or more electronic devices 102A to B, one or more wireless payment terminals 104A to B, a network 106, one or more mobile payment system servers 110, and one or more service provider servers 120. ..

The network 106, for example, attaches one or more of the wireless payment terminals 104A to B to one or more service provider servers 120 and / or one or more mobile payment system servers 110 to the electronic devices 102A to B. One or more can communicate with one or more mobile payment system servers 110 and / or one or more service provider servers 120, and one or more mobile payment system servers 110 can communicate with one or more service provider servers 120. May be combined with. One or more of the electronic devices 102A-B may communicate with one or more of the wireless payment terminals 104A-B via direct communication such as Near Field Communication (NFC) that bypasses the network 106. .. In one or more implementations, one or more of the electronic devices 102A-B may communicate with one or more of the wireless payment terminals 104A-B via the network 106 and / or wireless payment. One or more of the terminals 104A to B may not be communicably coupled to the network 106. In one or more implementations, the network 106 may be a network of interconnected devices, including the Internet or communicatively coupled to the Internet.

The wireless payment terminals 104A to B include, for example, a wireless transit payment terminal, a wireless toll payment terminal, a wireless parking meter payment terminal, a wireless POS terminal, and / or NFC wireless communication, wireless local area network (WLAN) wireless communication, Bluetooth. Any device that includes one or more wireless interfaces that can be used to perform wireless transactions such as wireless communications, Zigbee wireless communications, cellular wireless communications, and / or other wireless communications. good. In FIG. 1, as an example, wireless payment terminals 104A to B are drawn as wireless transit payment terminals. One or more of the wireless payment terminals 104A-B may be the electronic systems described below with respect to FIG. 9 and / or may include all or part of them.

The one or more mobile payment system servers 110 may include one or more servers that facilitate providing the mobile payment system to the one or more electronic devices 102A-B. As will be further described below with respect to FIG. 2, one or more mobile payment system servers 110 are one or more trusted service manager (TSM) servers, one or more broker servers, one or more application servers, and /. Alternatively, it may include generally any server that can facilitate the provision of mobile payment systems. In one or more implementations, a legitimate user of electronic device 102A and / or electronic device 102B may have a user account in the mobile payment system. The user account can be used, for example, to manage various cards and / or credentials that the user has registered with the mobile payment system via one or more mobile payment system servers 110. The one or more mobile payment system servers 110 may be the electronic systems described below with respect to FIG. 9 and / or may include all or part of them. For purposes of illustration, one or more mobile payment system servers 110 are generally described herein with reference to a single mobile payment system. However, the one or more mobile payment system servers 110 may include servers corresponding to a plurality of different mobile payment systems.

One or more service provider servers 120 provide one or more server devices that can facilitate the provision of services such as transit services and / or facilitate the use of wireless payment transactions for the services provided. It may be included. In one or more implementations, one or more service provider servers 120 may include one or more servers that correspond to one or more financial institutions. One or more service provider servers 120 facilitate the provision of services and / or the use of wireless payment transactions for one or more TSM servers, one or more broker servers, or one or more application servers. Obtaining can generally include any server. In one or more implementations, a legitimate user of electronic device 102A and / or electronic device 102B may have a user account in one or more service providers associated with one or more service provider servers 120. The user account may be used by the user to access a wireless payment transaction (eg, a historical record) via electronic device 102A and / or electronic device 102B. The one or more service provider servers 120 may be the electronic systems described below with respect to FIG. 9 and / or may include all or part of them. For purposes of illustration, one or more service provider servers 120 are generally described herein with reference to a single transit system. However, one or more service provider servers 120 may include servers that support a plurality of different services, such as a plurality of different transit systems.

The electronic devices 102A to B are, for example, portable computing devices such as laptop computers, smartphones, peripheral devices (eg, digital cameras, headphones), tablet devices, wearable devices (eg, watches, bands, etc.), or one. In other suitable devices including one or more wireless interfaces such as NFC wireless communication, WLAN wireless communication, Bluetooth® wireless communication, Zigbee wireless communication, cellular wireless communication, and / or other wireless communication. There may be. In FIG. 1, as an example, the electronic devices 102A and 102B are depicted as mobile devices and smart watches, respectively. One or more of the electronic devices 102A-B may be the electronic devices described below with respect to FIG. 2 and / or the electronic devices described below with respect to FIG. 9 and / or all or part of them. May include.

In one or more implementations, one or more of the electronic devices 102A-B may include secure elements to which one or more payment applets can be provisioned, including a stored value payment applet. An exemplary electronic device containing a secure element is further discussed below with respect to FIG. 2, and an exemplary secure element is further discussed below with respect to FIG.

To provision a stored value payment applet for a given service provider on one or more secure elements of electronic devices 102A-B, such as electronic device 102A, the user of electronic device 102A may use one or more service provider servers. Accessing a website or application associated with a service provider, such as the website provided by 120, and / or its users interact with a physical device associated with the service provider, such as a stored value card provisioning device. You can then request the service provider to provision a stored value payment applet on the secure element of electronic device 102A. The user may provide financial payments to the service provider, such as cash payments to physical machines and / or electronic payments via websites or applications. The monetary payment may correspond to the monetary value that the user wants to associate with the stored value payment applet provisioned on the electronic device 102A.

After completing the transaction with the service provider, one or more of the service provider server 120 and / or one or more mobile payment system servers 110 such as the TSM server and / or the broker server are the secure elements of the electronic device 102A. A stored value payment applet for a service provider can be provisioned on a secure element of electronic device 102A, such as by sending a provisioning script executed by. The secure element may execute a provisioning script to provision the monetary value paid by the user to the stored value payment applet for the service provider on the secure element.

The stored value payment applet has an applet identifier (AID) and / or an attribute that indicates whether authentication is required to use the stored value payment applet, for example, an authentication required attribute locally without facilitation from the TSM server. On a secure element using one or more attributes, such as any / all of attributes that indicate whether it is configurable and / or that store the amount of monetary value associated with the stored value payment applet. May be provisioned to. The applet identifier may be a unique identifier for other payment applets provisioned on the secure element, and the applet identifier may be used to identify a stored value payment applet. In one or more implementations, if the stored value payment applet is the only stored value payment applet currently provisioned on the secure element of electronic device 102A to the service provider, the stored value payment applet will support it. It may be automatically designated as an express stored value payment applet for the service provider. An exemplary process for configuring a newly provisioned stored value payment applet is further discussed below with respect to FIG.

Once the Express Stored Value Payment applet is specified on the secure element of electronic device 102A for a given service provider and the Express Stored Value payment applet is activated on electronic device 102A, the user authenticates with electronic device 102A. The electronic device 102A is used for a wireless transaction such as a wireless payment transaction with a wireless payment terminal associated with a service provider such as the wireless payment terminal 104A without the need to provide other inputs to the electronic device 102A. Can be used. Thus, when utilizing NFC-based wireless payment transactions, users place their electronic device 102A on or close to the wireless payment terminal 104A (eg, within about 4-20 centimeters). Therefore, the express stored value payment applet can be used to execute a wireless payment transaction with the wireless payment terminal 104A without authentication. Thus, using an electronic device 102A configured with an express stored value payment applet, the electronic device 102A does not have to first receive an input such as an authentication input or an unlock command, such as a transit fee or other such. It is possible to complete a payment transaction (for example, contactless payment) with the wireless payment terminal 104A for such a transaction.

For example, when the electronic device 102A is in close proximity to the wireless payment terminal 104A, the electronic device 102A may detect one or more polling signals transmitted by the wireless payment terminal 104A. The electronic device 102A can use the polling signal to determine that the wireless payment terminal 104A is associated with a service provider corresponding to the express stored value payment applet, and then the electronic device 102A is an express stored value payment applet. You can use the Value Payments applet to execute wireless payment transactions. An exemplary process of using the Express Stored Value payment applet in a wireless payment transaction is further discussed below with respect to FIG.

In one or more implementations, only one stored value payment applet may be specified for each service provider as the express stored value payment applet on the secure element of the electronic device 102A. However, if for a given service provider there are multiple stored value payment applets provisioned on the secure element of electronic device 102A, the stored value payment applet designated as the express stored value payment applet for the service provider will Can be changed automatically and / or through user input. An exemplary process for modifying an express stored value payment applet for a given service provider and / or initially setting up an express stored value payment applet for a given service provider is further discussed below with respect to FIG.

After the stored value payment applet for a given service provider is provisioned on the secure element of electronic device 102A, the user is provided by one or more service provider servers 120 and / or the card provisioning device associated with the service provider. Interact with websites to add monetary value to stored value payment applets and / or add additional services to stored value payment applets such as certain types of commuter tickets, number of rides or passes for duration. After the user provides payment to the service provider for additional monetary value and / or service, additional monetary value and / or service, eg, one or more mobile payment system servers 110 and / or 1 It can be added to a stored value payment applet provisioned on a secure element through a script sent to electronic device 102A via the TSM server of one or more service provider servers 120. The script may be executed by the secure element of electronic device 102A, which allows additional monetary value and / or other services (s) to be added to the stored value payment applet.

In one or more implementations, the subject system implements one or more local and / or remote security mechanisms and is used by a rogue user with an express stored value payment applet provisioned on a secure element of electronic device 102A. It can be prevented from being provisioned. For example, if the user does not authenticate with the electronic device 102A within a given period of time, such as 24 hours, the express stored value payment mode on the electronic device 102A may be deactivated. After the user authenticates with the electronic device 102A, the subject system may reactivate the "express" operation of the express stored value payment mode. An exemplary process for locally protecting the electronic device 102A that implements the subject express credential transaction system is further discussed below with respect to FIG.

In addition to the local security mechanisms described above, the subject system may also implement one or more remote security mechanisms. For example, when a user indicates that he / she has lost the electronic device 102A by interacting with a cloud service provided by one or more mobile payment system servers 110, the one or more mobile payment system servers 110 may be, for example. An attempt may be made to remotely deactivate the express stored value payment mode on the electronic device 102A without affecting the authentication attributes of the express stored value payment applet provisioned on the secure element of the electronic device 102A. In one or more embodiments, the electronic device 102A attempts the user to remotely delete all data on the electronic device 102A, eg, via a cloud service provided by one or more mobile payment system servers 110. When initiating a remote wipe of, one or more mobile payment system servers 110 are provisioned on the secure element of electronic device 102A associated with the service provider by sending an indicator to one or more service provider servers 120. You may initiate a blacklisting process for each of your stored value payment applets (and other service providers will work similarly for payment applets that are provisioned associated with their respective systems. Will be done). An exemplary process for remotely protecting the electronic device 102A that implements the subject express credential transaction system is further discussed below with respect to FIG.

FIG. 2 shows a network environment 200 including an exemplary electronic device 102A capable of implementing an express credential transaction system according to one or more implementations. However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. The arrangement and type of components can be modified without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided. In one or more implementations, one or more components of the exemplary electronic device 102A may be implemented by the electronic device 102B.

An exemplary network environment 200 may include an electronic device 102A, a wireless payment terminal 104A, a network 106, and one or more mobile payment system servers 110. The one or more mobile payment system servers 110 may include a trusted service manager (TSM) server 222 and a broker server 224. The electronic device 102A can include a host processor 202, a memory 204, an NFC controller 206, and a secure element 208.

The secure element 208 can communicate (directly or indirectly) with the NFC controller 206 and / or the host processor 202 via one or more single wire protocol (SWP) connections and / or any other data connection. May include one or more interfaces for binding. The secure element 208 may be referred to as one or more set stored value payment applets 210A-N and / or payment applets 212A-N herein, one or more set non-stored value payment applets 212A-N. N, can be included. In one or more implementations, the secure element 208 operating system and / or execution environment may be a Java®-based operating system and / or a Java®-based execution environment, Applet 210A. ~ N, 212A ~ N may be Java®-based applets. In other implementations, other operating systems, languages, and / or environments can be implemented. In addition to the one or more applets 210A-N, 212A-N, the secure element 208 can also include one or more additional applets for performing other actions such as security applets, registry applets, and the like.

Applets 210A-N, 212A-N may be partially provisioned on secure element 208, for example by trusted service manager server 222 and / or broker server 224. For example, the trusted service manager server 222 and / or the broker server 224 may send a provisioning script to the electronic device 102A over the network 106. In some implementations, the host processor 202 of the electronic device 102A may receive the script and transfer the script to the secure element 208 via the NFC controller 206 and / or directly to the secure element 208. May be provided. The secure element 208 can execute one or more security mechanisms to validate the receive script, such as one or more security mechanisms specific to the GlobalPlatform framework, and then execute the receive script.

By executing the script by the secure element 208, one or more of applets 210A to N and 212A to N can be provisioned on the secure element 208. Each of applets 210A-N, 212A-N is provisioned with one or more of an applet identifier, a device primary account number (DPAN) identifier, an associated service provider identifier, and / or one or more attributes. May be good. The applet identifier associated with a given payment applet 212A is provisioned on secure element 208, for example by host processor 202 and / or trusted service manager server 222 to perform one or more actions on payment applet 212A. It may be used to uniquely identify the payment applet 212A with respect to the other applets 210A to N and 212B to N. In one or more implementations, the applet identifier may be used by the host processor 202 to store the association between applets 210A-N, 212A-N and the corresponding service provider.

The DPAN identifier may be associated with an account, such as a credit card account, associated with a given payment applet 212A. In one or more implementations, the stored value payment applets 210A-N store the monetary value locally, so that the stored value payment applets 210A-N do not have to be provisioned with a DPAN identifier and instead have another identifier. Can be used. When performing a wireless payment transaction using one of the payment applets 212A-N, the secure element 208 may provide the wireless payment terminal 104A with a DPAN identifier. The wireless payment terminal 104A then transfers the DPAN identifier associated with a service provider capable of determining the account associated with the DPAN identifier, and the account contains sufficient funds and / or credits to complete the wireless payment transaction. You can confirm that.

In particular, one or more attributes provisioned with one or more of the applets 210A-N, 212A-N are, for example, an authentication request attribute indicating whether authentication is required to use the applet for a wireless payment transaction. And may include an authentication configurable attribute indicating whether the authentication request attribute is locally configurable, such as via a command from the host processor 202 without involving the trusted service manager server 222. By allowing the authentication request attribute to be locally configurable, the user activates express credentials when the trusted service manager server 222 and / or the broker server 224 is inaccessible because the electronic device 102A is offline. Can be transformed into. One or more of the stored value payment applets 210A-N, such as the stored value payment applet 210A, also indicates the amount of monetary value stored locally (or in connection with) within the stored value payment applet 210A. It may be provisioned using attributes.

Express stored value payments to a given service provider for one or more of the stored value payment applets 210A-N, such as the stored value payment applet 210A, when one or more conditions are met, for example, without user authentication. The stored value payment applets 210A-N first set the authentication request attribute to "off" or "no" (or "0") and set the authentication configurable attribute to "0" so that they can be automatically specified as applets. It can be set to "Yes" or "On" (or "1") for provisioning. However, if one or more conditions are not met, only one of the stored value payment applets 210A-N per service provider is set to "off" or "no", as further discussed below with respect to FIG. The authentication request attributes of the stored value payment applets 210A-N can be changed to "on" or "yes" immediately after provisioning so that they have the authentication request attributes that have been set.

The payment applets 212A-N may be provisioned with the authentication request attribute set to "on" or "yes" and the authentication configurable attribute set to "no" or "off", respectively. Thus, the payment applets 212A-N are provisioned with an authentication configurable attribute set to "No" or "Off" so that the authentication request attribute can be, for example, without facilitation from the trusted service manager server 222. It cannot be changed locally by an instruction from the host processor 202.

In one or more implementations, applets 210A-N, 212A-N also specify the type of communication protocol used by applets 210A-N, 212A-N to communicate with payment terminals such as wireless payment terminal 104A. It can be set with the indicated attributes. The types of communication protocols include, for example, NFC-A protocol, NFC-B protocol, NFC-F protocol, Bluetooth® protocol, Bluetooth® low energy (BLE) protocol, Zigbee protocol, Wi-Fi protocol. , Or generally any communication protocol may be included.

In some implementations, two or more of the stored value payment applets 210A-N may correspond to the same service provider, such as the same transit system. In addition, in some implementations, two or more stored value payment applets 210A-N may be provisioned for different service providers, such as different transit systems. Similarly, one or more of the payment applets 212A-N may be associated with the same service provider, such as the same financial institution, and / or may be associated with different service providers. In one or more implementations, only one of the stored value payment applets 210A-N associated with a given service provider may be designated as the express stored value payment applet for the service provider. In one or more implementations, such as a host card emulation implementation, all or part of the secure element 208 may be implemented by the host processor 202, thus in one or more implementations the secure element 208 is an electronic device. It does not have to be included in 102A. The secure element 208 and the applets 210A-N, 212A-N provisioned on it are further discussed below with respect to FIG.

The NFC controller 206 can include one or more antennas and one or more transceivers for transmitting / receiving NFC communication. The NFC controller 206 may further include one or more interfaces, such as a single wire protocol interface, for coupling to the host processor 202 and / or the secure element 208. The NFC controller 206 communicates via one or more different NFC communication protocols such as NFC-A (or type A), NFC-B (or type B), and / or NFC-F (or type F or FeliCA). Can be. The NFC-A protocol may be based on the International Organization for Standardization (ISO) / International Electrotechnical Commission (IEC) 14443A, or mirror bit coding with 100% amplitude modulation may be used. The NFC-B protocol may be based on ISO / IEC 14443B and can use a variant of Manchester encoding with 10% modulation. The NFC-F protocol may be based on the FeliCA JIS X6319-4 and may use a slightly different Manchester coding variant than the NFC-B protocol.

The wireless payment terminal 104A may include a wireless communication function similar to that of the electronic device 102A. For example, the wireless payment terminal 104A includes NFC-A protocol, NFC-B protocol, NFC-F protocol, Bluetooth® protocol, Bluetooth® low energy protocol, Zigbee protocol, Wi-Fi protocol, or generally. It may include one or more antennas and / or transmitters / receivers for communicating with the electronic device 102A via one or more of any communication protocols. In one or more implementations, the wireless payment terminal 104A may include a wireless reader such as an NFC reader.

In one or more implementations, power may be supplied to the NFC controller 206 and the secure element 208 from a current induced by a wireless reader such as the NFC reader of the wireless payment terminal 104A. Thus, in one or more implementations, the NFC controller 206 and / or the secure element 208 may not be able to power the NFC controller 206 and / or the secure element 208, even if the electronic device 102A is unable to power the NFC controller 206 and / or the secure element 208. , Can provide a thematic system for express stored value payments. In one or more embodiments, the NFC controller 206 and the secure element 208 can power the NFC controller 206 and / or the secure element 208 even if the mains of the electronic device 102A are reduced or unavailable. , Solar power and / or auxiliary power such as solar charging power.

In one or more implementations, the wireless payment terminal 104A may transmit one or more polling signals, advertising signals, discovery signals, and / or broadcast signals. These signals, for example, initiate a wireless payment transaction with the electronic device 102A, identify the service provider associated with the wireless payment terminal 104A, and / or whether the wireless payment terminal 104A supports an express credential transaction. Can be used to determine. Thus, in one or more embodiments, the host processor 202 can identify the service provider associated with the wireless payment terminal 104A and is at least partially based on the polling signal and / or the geolocation information of the electronic device 102A. , It may be possible to determine that the wireless payment terminal 104A supports express credential transactions. In one or more implementations, one or more polling signals can carry information that identifies the service provider associated with the wireless payment terminal 104A.

For example, a polling signal (eg, based on transmission frequency, signal length, preamble length, etc.) can be associated with a given service provider within a given geographic area, such as a continent, country, state, city, etc. It may be associated with a particular pattern, code, and / or signature.
In one or more embodiments, the electronic device 102A has the presence or absence of one or more specific NFC technology types (A, B, F), as well as the presence or absence of polling signals and their data content (as many times as counted). May be detected. For example, in the electronic device 102A, type F is detected, type A / B is not detected, polling signal system code 0003 (in the case of type F FeliCA system) is detected at least twice, and polling signal FE00 or FFFF is not detected. If you can initiate an express credential transaction.

For purposes of explanation, FIG. 2 shows an electronic device 102A that uses the NFC controller 206 to communicate with the wireless payment terminal 104A. However, the electronic device 102A is an arbitrary wireless communication protocol such as Bluetooth®, Bluetooth® low energy, Wi-Fi, Zigbee, millimeter wave (mmWave), or generally any wireless communication protocol. Can be used to communicate with the wireless payment terminal 104A.

The broker server 224 manages user authentication with the service provider and communicates with one or more service provider servers 120 for the purpose of receiving updates from the service provider applied to the secure element 208 of the electronic device 102A. can do. The trusted service manager server 222 communicates with the secure element 208 of the electronic device 102A via the network 106 and the host processor 202 to facilitate the management of the stored value payment applets 210A-N, 212A-N on the secure element 208. be able to. For example, the trusted service manager server 222 attaches to secure element 208 to modify / update one or more of applets 210A-N, 212A-N and / or to provision a new applet on secure element 208. You can send a script.

Host processor 202 may include suitable logic, circuits, and / or codes that allow it to process data and / or control the operation of electronic device 102A. In this regard, the host processor 202 may allow the control signal to be supplied to various other components of the electronic device 102A. The host processor 202 may also control the data transfer of the electronic device 102A over various sections. In addition, the host processor 202 may allow the operating system to be implemented or execute code to manage the operation of the electronic device 102A. Memory 204 may include appropriate logic, circuits, and / or codes that allow storage of various types of information such as received data, generated data, codes, and / or configuration information. Memory 204 can include, for example, random access memory (RAM), read-only memory (ROM), flash, and / or magnetic storage.

In one or more embodiments, one or more of the host processor 202, memory 204, FPGA controller 206, secure element 208, and / or one or more portions thereof is software (eg, subroutines and code). , Hardware (eg, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (PLDs), controllers, state machines, gate logic, discrete hardware components, or any other suitable. Devices) and / or a combination of both.

FIG. 3 shows an exemplary electronic device 102A that includes an exemplary secure element 208 that can be used in an express credential transaction system for one or more implementations. However, not all of the depicted components may be used in all implementations, and one or more implementations may include additional or different components to those shown in the figure. The arrangement and type of components can be modified without departing from the spirit or scope of the claims set forth herein. Additional components, different components, or fewer components may be provided. For illustration purposes, the secure element 208 is shown as being mounted on the electronic device 102A, but the secure element 208 may be mounted on the electronic device 102B and / or any other electronic device.

The secure element 208 may include the secure processor 302, the RAM 304, the security engine 306, the interface 308, and the non-volatile memory 310 as other components. The RAM 304 can include one or more of a static RAM (SRAM) and / or a dynamic RAM (DRAM). Interface 308 can communicatively couple security element 208 to one or more other chips in the device, such as NFC controller 206 and / or host processor 202. The interface 308 may be, for example, a SWP interface, a universal serial bus (USB) interface, or generally any data interface. The secure processor 302 may be, for example, a reduced instruction set computing (RISC) processor, an advanced RISC machine (ARM) processor, or generally any processing circuit.

The security engine 306 can perform one or more security actions for the secure element 208. For example, the security engine 306 may perform cryptographic operations and / or manage cryptographic keys and / or certificates. In one or more implementations, communication between the secure element 208 and an external device such as wireless payment terminal 104A and / or trusted service manager server 222 may be encrypted. For example, in the case of NFC-F communication, an encryption key may be dynamically generated each time mutual authentication is executed. In one or more of these implementations, encryption / decryption and / or key generation / management may be performed entirely or partially by the security engine 306.

The non-volatile memory 310 may be, for example, a flash memory and / or may include a flash memory. The non-volatile memory 310 may store attributes and executable code associated with applets 210A-N, 212A-N.
In one or more embodiments, the non-volatile memory 310 is the firmware and / or the firmware executed by the secure processor 302 to provide an execution environment for applets 210A-N, 212A-N, such as a JAVA® execution environment. It can also store operating system executable code.

In one or more embodiments, one or more of the secure processor 302, RAM 304, security engine 306, interface 308, non-volatile memory 310, and / or one or more portions thereof is software (eg, a subroutine). And code), hardware (eg, ASICs, FPGAs, PLDs, controllers, state machines, gate logic, discrete hardware components, or any other suitable device), and / or a combination of both. May be good.

FIG. 4 shows a flow diagram of an exemplary process 400 for configuring a newly provisioned stored value payment applet in an express credential transaction system for one or more implementations. For purposes of explanation, process 400 will be described herein primarily with reference to the host processor 202 and the secure element 208 of the electronic devices 102A of FIGS. 1-2. However, process 400 is not limited to the secure element 208 of host processor 202 or electronic device 102A, and one or more blocks (or operations) of process 400 are by one or more other components of electronic device 102A. And / or may be executed without using the host processor 202. The electronic device 102A is also presented as an exemplary device, and the operations described herein may be performed by any suitable device. For example, process 400 may be performed by electronic device 102B or generally any electronic device. Further, for purposes of explanation, the blocks of process 400 are described herein as occurring sequentially or linearly. However, multiple blocks of process 400 may occur in parallel. In addition, the blocks of process 400 need not be executed in the order shown and / or one or more blocks of process 400 need not be executed and / or may be replaced by other actions. can.

In process 400 for configuring the newly provisioned stored value applet, the host processor 202 of the electronic device 102A is a stored value payment applet associated with a service provider such as the stored value payment applet 210A, which secures the electronic device 102A. Receive an applet that it is provisioned on element 208 (402). For example, the host processor 202 can receive a notification from the secure element 208 and / or the trusted service manager server 222 indicating that the stored value payment applet 210A is provisioned on the secure element 208. The notification can include an applet identifier for the newly provisioned stored value payment applet 210A. The stored value payment applet 210A has the authentication request attribute set to "off" or "no", the authentication configurable attribute set to "yes" or "on", and previously paid for the stored value payment applet 210A. A monetary value attribute set to monetary value, which can be first provisioned on secure element 208. Provision of the stored value payment applet 210A may occur through multiple separate actions and / or exchange of data.

Host processor 202 then determines if any other stored value payment applets 210B-N provisioned on secure element 208 are associated with the service provider (404). If the host processor 202 determines that none of the other stored value payment applet applets 210B-N provisioned on the secure element 208 associated with the service provider are present (404), the host processor 202 receives the stored stored. The value payment applet 210A is designated as the express stored value payment applet 210A for the service provider (406). Specifying the stored value payment applet 210A received as the express stored value payment applet 210A may include leaving the authentication request attribute for the stored value payment applet 210A set to "off" or "no". Therefore, the Express Stored Value Payment Applet 210A can be used, for example, in a transit transaction with a corresponding service provider, without manual input such as authentication.

In one or more implementations, the host processor 202 is newly provisioned regardless of whether any other stored value payment applets 210B-N associated with the service provider are provisioned on secure element 208. The stored value applet 210A can be designated as an express stored value payment applet for a service provider, and any other stored value payment applet 210B associated with the service provider provisioned on secure element 208. For N, set the authentication request attribute to "Yes" or "On".

If the host processor 202 determines that there is one or more other stored value payment applets 210B-N provisioned on the secure element 208 associated with the service provider (404), the host processor 202 is newly provisioned. For the stored value settlement applet 210A, the authentication request attribute is set to "on" or "yes" (408). Thus, if there is one or more other stored value payment applets 210B-N already provisioned on the secure element 208, the host processor 202 allows the user to provide at least one express stored value payment applet to the service provider. The newly provisioned stored value payment applet 210A is not designated as an express stored value payment applet for the service provider because it determines that it has already been deactivated. For example, in order to change the authentication request attribute of the stored value payment applet 210A, the host processor 202 includes the applet identifier of the newly provisioned stored value payment applet 210A and sets the authentication request attribute for the stored value payment applet 210A to "Yes." An instruction, command, and / or script indicating that it should be set to "on" may be sent to the secure element 208.

The host processor 202 then determines whether another of the stored value payment applets 210B-N provisioned on the secure element 208 is designated as an express stored value payment applet for the service provider (410). .. The host processor 202 determines that another of the stored value payment applets 210B-N provisioned on the secure element 208, such as the stored value payment applet 210B, is designated as the express stored value payment applet for the service provider. If (410), the host processor 202 sets the authentication request attribute on for all other stored value payment applets associated with the service provider provisioned on secure element 208 as a security precaution. (412). For example, the host processor 202 attaches an authentication request attribute to the secure element 208 for all stored value payment applets 210A-N provisioned on the secure element 208 associated with the service provider, except for the express stored value payment applet 210B. A command can be sent to the secure element 208 instructing it to be set to "on" or "yes".

As a security precaution, if the host processor 202 determines that none of the stored value payment applets 210A-N provisioned on secure element 208 is currently designated as an express stored value payment applet for the service provider. , The host processor 202 sets the authentication request attribute to "yes" or "on" for all of the stored value payment applets 210A-N provisioned on the secure element 208 associated with the service provider (414). For example, host processor 202 sets the authentication request attribute to secure element 208 to "on" or "yes" for all stored value payment instructions 210A-N provisioned on secure element 208 associated with the service provider. A command to instruct the configuration can be sent to the secure element 208.

FIG. 5 shows a flow diagram of an exemplary process 500 for using the Express Stored Value Payment Applet 210A in an Express Credential Transaction System according to one or more implementations. For purposes of explanation, process 500 will be described herein primarily with reference to the host processor 202, the NFC controller 206, and the secure element 208 of the electronic device 102A of FIGS. 1-2. However, process 500 is not limited to the host processor 202, NFC controller 206, or secure element 208 of electronic device 102A, and one or more blocks (or operations) of process 500 are one or more other of electronic device 102A. It may be executed by the components of and / or without using the host processor 202. The electronic device 102A is also presented as an exemplary device, and the operations described herein may be performed by any suitable device. For example, process 500 may be performed by electronic device 102B or generally any electronic device. Further, for purposes of explanation, the blocks of process 500 are described herein as occurring sequentially or linearly. However, multiple blocks of process 500 may occur in parallel. In addition, the blocks of process 500 need not be executed in the order shown and / or one or more blocks of process 500 need not be executed and / or may be replaced by other actions. can.

In process 500 for using the express stored value payment applet 210A, the electronic device 102A detects one or more signals associated with the wireless payment terminal 104A, such as through the NFC controller 206 (502). The one or more signals may include, for example, a polling signal, a pilot signal, an advertising signal, a discovery signal, a broadcast signal, a signal type, or a generally arbitrary signal that can be transmitted by the wireless payment terminal 104A. In one or more implementations, the NFC controller 206 provides one or more signals to the host processor 202 of the electronic device 102A.

The host processor 202 identifies the service provider associated with the wireless payment terminal 104A based at least in part on one or more signals (504). Further, as described above, the host processor 202 identifies the service provider associated with the wireless payment terminal 104A, at least in part, based on information that can be determined and / or derived from one or more signals. May be good. Further, in some implementations, information about the electronic device 102A as determinable by the host processor 202, such as the location of the electronic device 102A, can also be used to identify the service provider associated with the wireless payment terminal 104A. .. Host processor 202 determines if any stored value payment applets 210A-N associated with the identified service provider are provisioned on secure element 208 (506). For example, the host processor 202 can query the secure element 208 to determine if any of the stored value payment applets 210A-N are provisioned for use with a service provider.

If the host processor 202 determines that none of the stored value payment applets 210A-N provisioned on the secure element 208 is associated with a service provider (506), the host processor 202 has one or more signals. Ignores one or more signals, such as not responding to (508). If the host processor 202 determines that the stored value payment applet 210A associated with the service provider is provisioned on the secure element 208 (506), the host processor 202 determines that the stored value payment applet 210A is the stored value payment applet. It is determined whether or not the attribute indicating that the user authentication is not required to use the 210A is included (510). For example, the host processor 202 queries the secure element 208 using the applet identifier associated with the stored value payment applet 210A, and sets the authentication attribute for the stored value payment applet 210A to "No" or "Off". It can be determined whether or not the applet is used.

When the host processor 202 determines that the stored value payment applet 210A contains an attribute indicating that user authentication is not required to use the stored value payment applet 210A (510), the host processor 202 determines that the stored value payment applet 210A contains a stored value. The payment applet 210A can be used by the NFC controller 206 or the like for a wireless payment transaction with the wireless payment terminal 104A without requiring user authentication (516). Next, the NFC controller 206 can perform a wireless payment transaction with the wireless payment terminal 104A by using the stored value payment applet 210A. In this way, the host processor 202 automatically makes the stored value payment applet 210A available to the NFC controller 206 in response to detecting the polling signal from the wireless payment terminal 104A that triggers the express credential transaction. In addition, it is possible to verify that the stored value payment applet 210A includes an attribute indicating that user authentication is not required to use the stored value payment applet 210A.

After protecting the connection with the wireless payment terminal 104A, for example by establishing one or more encryption keys, the wireless payment terminal 104A is deducted from the monetary value associated with the stored value payment applet 210A. The forehead may be transmitted to the NFC controller 206. The NFC controller 206, alone and / or with the host processor 202, may instruct the secure element 208 to deduct the indicated amount. The secure element 208 can respond with an indication of whether the deduction of the amount was successful, and the NFC controller 206 transfers the indication to the wireless payment terminal 104A. If the indicated amount is successfully deducted, the wireless payment terminal 104A can allow the user of the electronic device 102A to access services such as access transit provided by trains, buses, ships and the like.

In one or more implementations, the host processor 202 takes any active step to enable the stored value payment applet 210A to be used by the NFC controller 206 to perform a wireless payment transaction with the wireless payment terminal 104A. It may not be taken. Instead, if the authentication request attribute for the stored value payment applet 210A is set to "no" or "off", the NFC controller 206 can use the stored value payment applet 210A without facilitating the host processor 202. Can be done. However, the stored value payment applet 210A does not include an attribute indicating that the user does not need to authenticate, eg, the host processor 202 and / or NFC if the authentication request attribute is set to "yes" or "on". If the controller 206 determines (510), the host processor 202 requests user authentication (512) before making the stored value payment applet 210A available. User authentication can include, for example, biometric authentication such as fingerprint authentication, iris authentication, voice authentication, password authentication, manual user input, or generally arbitrary user authentication.

If the polling signal from the wireless payment terminal 104A that triggers the express credential transaction is not detected and / or if there is no corresponding stored value payment applet that contains an attribute indicating that user authentication is not required, the host processor 202 wirelessly It is possible to determine whether or not the default stored value payment applet is configured for the service provider corresponding to the payment terminal 104A. For example, the user can set up an express stored value payment applet for a service provider that can be used without authentication (if the corresponding wireless payment terminal 104A supports express credential transactions), and / or the user. You can set a default stored value payment applet for the service provider that can be used with authentication, such as when the wireless payment terminal 104A does not support express credential transactions. In one or more implementations, the express stored value payment applet may be set as the default stored value payment applet.

For example, when the host processor 202 determines that the user has succeeded in authentication within the time limit (514), the host processor 202 uses the NFC controller 206 or the like to perform a stored value payment applet for the wireless payment transaction with the wireless payment terminal 104A. Make 210A available (518). If the host processor 202 determines that the user has not succeeded in authentication (514), the host processor 202 does not make the stored value payment applet 210A available for the wireless payment transaction with the wireless payment terminal 104A (the stored value payment applet 210A). 520).

FIG. 6 shows a flow diagram of an exemplary process 600 for designating an express stored value payment applet 210A for a service provider in an express credential transaction system according to one or more implementations. For purposes of explanation, process 600 will be described herein primarily with reference to the host processor 202 and the secure element 208 of the electronic device 102A of FIGS. 1-2. However, process 600 is not limited to the secure element 208 of host processor 202 or electronic device 102A, and one or more blocks (or operations) of process 600 are by one or more other components of electronic device 102A. And / or may be executed without using the host processor 202. The electronic device 102A is also presented as an exemplary device, and the operations described herein may be performed by any suitable device. For example, process 600 may be performed by electronic device 102B or generally any electronic device. Further, for purposes of explanation, the blocks of process 600 are described herein as occurring sequentially or linearly. However, multiple blocks of process 600 may occur in parallel. In addition, the blocks of process 600 need not be executed in the order shown and / or one or more blocks of process 600 need not be executed and / or may be replaced by other actions. can.

In process 600 for designating the Express Stored Value Settlement Applet 210A for the Service Provider, the host processor 202 receives a request to designate the Stored Value Settlement Applet 210A as the Express Stored Value Settlement Applet for the Service Provider (602). For example, the host processor 202 may provide the user with a user interface on the display for selecting / deselecting and / or modifying an express stored value payment applet for one or more service providers. The user interface may display a graphic representation of the stored value payment applets 210A-N provisioned on secure element 208, eg, associated with or corresponding to a given service provider. The user selects one of the graphical representations that requires the corresponding stored value payment applet 210A to be configured as an express stored value payment applet, eg, for use in a transaction with an associated service provider. Can be done.

Upon receiving the request (602), the host processor 202 determines if another stored value payment applet 210B has already been designated as an express stored value payment applet for the service provider (604). For example, the host processor 202 can query the secure element 208 to determine if the express stored value payment applet has already been designated as "express" to the service provider. In one or more implementations, the host processor 202 accesses the data stored in memory 204, such as the data associated with the generation of the user interface, and the express stored value payment applet has already specified to the service provider. Whether or not it is done can be determined without querying the secure element 208.

For example, if an express stored value payment applet has already been specified for the service provider, the graphic representation of the express stored value payment applets 210A-N associated with the service provider is that the stored value payment applet 210B express stored for the service provider. It may include a graphic indication that it is designated as a value payment applet. Graphical attributes may include, for example, shading, highlighting, color changes, contours, and the like. Thus, the host processor 202 does not query the secure element 208 based on the information used to generate the user interface, and another stored value payment applet 210B can make an express stored value payment applet to the service provider. It can be determined whether or not it has already been designated as 210B (604).

If the host processor 202 determines that the stored value payment applet 210A has already been designated as an express stored value payment applet for the service provider (604), as a security precaution, the host processor 202 is secured associated with the service provider. Set the authentication request attribute to "yes" or "on" for all of the stored value payment applets 210A-N provisioned on element 208 (606). For example, the host processor 202 commands all of the stored value payment applets 210A-N provisioned on the secure element 208 to set the authentication request attribute to "yes" or "on" on the secure element 208. The command can be sent to secure element 208 (606).

Whether or not the host processor 202 determines that the stored value payment applet 210B has already been designated as an express stored value payment applet for the service provider (604), the requested stored value payment applet 210A is currently "yes". Alternatively, because it has an authentication request attribute set to "on", the host processor 202 requests authentication from the user to initiate the change (608). If the user is not authenticated (610), the host processor 202 rejects the request to set the stored value payment applet 210A as an express stored value payment applet (612). Thus, in one or more implementations, if user authentication fails (610), any of the stored value payment applets 210A-N associated with the service provider is designated as an express store value payment applet for the service provider. It is not possible.

When the user is authenticated (610), the host processor 202 sets the authentication request attribute to "off" or "no" for the stored value payment applet 210A (614). For example, the host processor 202 may send a command to the secure element 208 to indicate to the requested stored value payment applet 210A that the authentication request attribute should be set to "off" or "no". Can be done (614). The host processor 202 then identifies the stored value payment applet 210A as an express stored value payment applet to the service provider, such as by providing a graphic indication indicating that on the user interface displayed to the user. Can be done (616).

FIG. 7 shows a flow diagram of an exemplary process 700 for locally protecting an electronic device 102A that implements an express credential transaction system for one or more implementations. For purposes of explanation, the process 700 will be described herein primarily with reference to the host processor 202 and the secure element 208 of the electronic device 102A of FIGS. 1-2. However, process 700 is not limited to the secure element 208 of host processor 202 or electronic device 102A, and one or more blocks (or operations) of process 700 are by one or more other components of electronic device 102A. And / or may be executed without using the host processor 202. The electronic device 102A is also presented as an exemplary device, and the operations described herein may be performed by any suitable device. For example, process 700 may be performed by electronic device 102B or generally any electronic device. Further, for purposes of explanation, the blocks of process 700 are described herein as occurring sequentially or linearly. However, multiple blocks of process 700 may occur in parallel. In addition, the blocks of process 700 need not be executed in the order shown and / or one or more blocks of process 700 need not be executed and / or may be replaced by other actions. can.

In the process 700 for locally protecting the electronic device 102A, the host processor 202 determines if the electronic device 102A has not received user authentication for a given period of time, such as 24 hours (702). If the host processor 202 determines that the electronic device 102A has not received user authentication during a predetermined period (702), the host processor 202 deactivates the express stored value payment mode on the electronic device 102A (s). 704). The express stored value payment mode may be associated with, for example, a setting configurable by the host processor 202. When the express stored value payment mode is deactivated on the electronic device 102A, the host processor 202 causes the NFC controller 206 to use any of the stored value payment applets 210A to N in a wireless transaction without user authentication. To prevent. However, deactivating the express stored value payment mode will result in the authentication request attributes of the stored value payment applets 210A-N so that the authentication request attributes will be maintained when the express stored value payment mode is reactivated. Does not affect.

The host processor 202 waits for user authentication to be received (706), and when a valid user authentication is received (706), the host processor 202 reactivates the express stored value payment mode on the electronic device 102A ( 708). Once the express stored value payment mode is activated, the NFC controller 206 has a stored value with an authentication request attribute set to "no" or "off", for example for an "express" transaction, without user authentication. Make any of the payment applets 210A to N available.

In one or more implementations, the host processor 202 if one or more of the stored value payment applets 210A-N, such as the stored value payment applet 210A, is designated as an express stored value payment applet for a given service provider. And / or the secure element 208 may implement additional security measures. For example, the host processor 202 and / or the secure element 208 may limit the number of times the Express Stored Value Payment Applet 210A can be used without user authentication within a given time, such as 5 minutes. The host processor 202 and / or the secure element 208 may impose other security restrictions that may prevent unauthorized use of the Express Stored Value Payment Applet, eg, based on location or amount.

FIG. 8 shows a flow diagram of an exemplary process 800 for remotely protecting an electronic device 102A that implements an express credential transaction system according to one or more implementations. For purposes of explanation, process 800 will be described herein primarily with reference to the electronic devices 102A of FIGS. 1 and 2 and one or more mobile payment system servers 110. However, process 800 is not limited to electronic device 102A or one or more mobile payment system servers 110, and one or more blocks (or operations) of process 800 are one or more components of electronic device 102A, or It may be executed by one or more mobile payment system servers 110. The electronic device 102A is also presented as an exemplary device, and the operations described herein may be performed by any suitable device. For example, process 800 may be performed by electronic device 102B and / or one or more service provider servers 120, or generally any electronic device and / or server. Further, for purposes of explanation, the blocks of process 800 are described herein as occurring sequentially or linearly. However, multiple blocks of process 800 may occur in parallel. In addition, the blocks of process 800 need not be executed in the order shown and / or one or more blocks of process 800 need not be executed and / or may be replaced by other actions. can.

In the process 800 for remotely protecting the electronic device 102A, one or more mobile payment system servers 110 can receive an applet that the electronic device 102A has been lost, where the electronic device 102A is said to have lost its electronic device 102A. Includes a secure element 208 with one or more stored value payment applets 210A-N provisioned above (802). For example, the user may interact with, for example, a website or application associated with one or more mobile payment system servers 110 to indicate that the electronic device has been lost. Since the stored value settlement applets 210A-N locally store the representation of the actual monetary value, if the electronic device 102A is lost, the represented monetary value may also be lost.

Upon receiving the indication that the electronic device 102A has been lost (802), the one or more mobile payment system servers 110 will, for example, the electronic device 102A without affecting the authentication attributes of the stored value payment applets 210A-N. An attempt is made to send a command to the electronic device 102A to deactivate the express stored value payment mode in the host processor 202 (804).
In one or more implementations, if one or more mobile payment system servers 110 later receive an indication that the electronic device 102A has been found, the one or more mobile payment system servers 110 will host the electronic device 102A. A command to reactivate the express stored value payment mode in the processor 202 can be sent to the electronic device 102A. For example, express mode can be reactivated after local and / or cloud-based authentication has been performed.

One or more mobile payment system servers 110 also include, for example, one or more stored value payment applets 210A-N provisioned on secure element 208 upon receiving an indication of a request from a user, electronic device 102A. All of the above data may be deleted remotely (806). Upon receiving an applet request to delete all data from electronic device 102A (806), one or more mobile payment system servers 110 have one or more stored values provisioned on secure element 208 of electronic device 102A. One or more service providers associated with applets 210A-N can be notified that one or more stored value payment applets 210A-N should no longer be accepted in a wireless payment transaction (808). For example, one or more mobile payment system servers 110 may list one or more stored value applets 210A-N, such as a serial number or other such unique credential identifier, from one or more service providers. It can be sent to the server 120.

The one or more service provider servers 120 can add the identifiers of one or more stored value applets 210A to N to the blacklist that can be periodically delivered to the wireless transaction terminals 104A to B.
Wireless transaction terminals 104A-B may not accept wireless payment transactions that utilize stored value applets with blacklisted identifiers. When one or more service provider servers 120 propagate the identifier to the wireless payment terminals 104A-B, the one or more service provider servers 120 remain for each of the one or more stored value payment applets 210A-N. Determine recoverable and / or unused monetary value.

The one or more mobile payment system servers 110 then inject the amount of monetary value remaining from the one or more service provider servers 120 to each of the one or more stored value payment applets 210A-N. Is received (810). One or more mobile payment system servers 110 may then allow one or more stored value payment applets 210A-N to be reprovisioned with the remaining monetary value on another electronic device of the user. Can be done (812). The user interacts with one or more mobile payment system servers 110, such as through a website or application, and another one or more stored value payment applets 210A-N, such as by the method described above with respect to FIG. It may be reprovisioned on an electronic device.

FIG. 9 shows an electronic system 900 capable of implementing one or more implementations of the subject technology. The electronic system 900 is one or more of the electronic devices 102A to B shown in FIG. 1, one or more of the wireless payment terminals 104A to B, and / or one or more of the servers 110 and 120. Can and / or be part of them. The electronic system 900 may include interfaces for various types of computer-readable media, as well as various other types of computer-readable media. The electronic system 900 includes bus 908, one or more processing units (s) 912, system memory 904 (and / or buffer), ROM 910, permanent storage device 902, input device interface 914, output device interface 906, and 1 Includes one or more network interfaces 916, or subsets or variants thereof.

The bus 908 collectively represents all systems, peripherals, and chipset buses that communicatively connect a number of internal devices of the electronic system 900. In one or more implementations, the bus 908 connects one or more processing units (s) 912 communicably with the ROM 910, system memory 904, and permanent storage device 902. From these various memory units, one or more processing units (s) 912 retrieve instructions to be executed and data to be processed in order to perform the subject disclosure process. The one or more processing units (s) 912 can be single or multi-core processors in different implementations.

The ROM 910 stores static data and instructions required by one or more processing units (s) 912 and other modules of the electronic system 900. On the other hand, the permanent storage device 902 may be a read / write memory device. Permanent storage device 902 may be a non-volatile memory unit that stores instructions and data, even if the electronic system 900 is off. In one or more implementations, a large capacity storage device (magnetic or optical disk, and corresponding disk drive, etc.) may be used as the permanent storage device 902.

In one or more implementations, a removable storage device (such as a floppy disk, a flash drive, and a corresponding disk drive) may be used as the permanent storage device 902. Similar to the permanent storage device 902, the system memory 904 may be a read and write memory device. However, unlike the permanent storage device 902, the system memory 904 may be a volatile read and write memory, such as a random access memory. The system memory 904 may store any of the instructions and data that may be required by one or more processing units (s) 912 at run time. In one or more implementations, the subject disclosure process is stored in system memory 904, permanent storage device 902, and / or ROM 910. From these various memory units, one or more processing units (s) 912 retrieve instructions to be executed and data to be processed in order to execute a process of one or more implementations.

Bus 908 also connects to input and output device interfaces 914 and 906. The input device interface 914 allows the user to communicate information and select commands to the electronic system 900. Input devices that can be used with the input device interface 914 can include, for example, an alphanumeric keyboard and a pointing device (also referred to as a "cursor control device"). The output device interface 906 can, for example, enable the display of images generated by the electronic system 900. An output device that can be used with the output device interface 906 is, for example, a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, a flexible display, a flat panel display, a solid state display, a projector, or information. Can include printers and display devices, such as any other device for outputting. One or more implementations can include devices that act as both input and output devices, such as touch screens. In these embodiments, the feedback provided to the user can be any form of sensory feedback such as visual feedback, auditory feedback, tactile feedback, etc., and the user input can be acoustic input, audio input, or It can be received in any form, including tactile input.

Finally, as shown in FIG. 9, the bus 908 also connects the electronic system 900 through one or more network interfaces (s) 916 to one or more networks and / or the electronic device 102A shown in FIG. Combine to one or more network nodes such as ~ F. In this way, the electronic system 900 can be part of a network of computers (LAN, wide area network (such as "WAN"), or a network of multiple networks such as an intranet or the Internet. Any or all components may be used with the subject disclosure.

Implementations within the scope of this disclosure partially use a tangible computer-readable storage medium (or one or more types of tangible computer-readable storage media) that encodes one or more instructions. It can be realized completely or completely. The tangible computer-readable storage medium may also be virtually non-temporary.

A computer-readable storage medium is any storage that can be read, written, or otherwise accessed by a general purpose or dedicated computing device, including any processing electronics and / or processing circuits capable of executing instructions. It can be a medium. For example, but not limited to, computer readable media can include any volatile semiconductor memory such as RAM, DRAM, SRAM, T-RAM, Z-RAM, and TTRAM. Computer-readable media are also ROM, PROM, EPROM, EEPROM, NVRAM, flash, nvSRAM, FeRAM, FeTRAM, MRAM, PRAM, CBRAM, SONOS, RRAM®, NRAM, racetrack memory, FJG, and millipede memory. Any non-volatile semiconductor memory such as can be included.

Further, the computer-readable storage medium includes any non-semiconductor memory, such as an optical disk storage device, a magnetic disk storage device, a magnetic tape, another magnetic storage device, or any other medium capable of storing one or more instructions. be able to. In one or more implementations, the tangible computer-readable storage medium can be directly coupled to the computing device, and in other implementations, the tangible computer-readable storage medium is, for example, one or more wired connections. It can be indirectly coupled to a computing device via one or more wireless connections, or any combination thereof.

The instruction can be directly executable or can be used to develop an executable instruction. For example, an instruction can be implemented as executable or non-executable machine code, or as a high-level language instruction that can be compiled to generate executable or non-executable machine code. In addition, the instructions can also be implemented as data or include data. Computer-executable instructions can also be structured in any format, including routines, subroutines, programs, data structures, objects, modules, applications, applets, functions, and so on.
As will be appreciated by those skilled in the art, details including, but not limited to, the number, structure, order, and structure of instructions can be significantly changed without changing the basic logic, functionality, processing, and output. Can be done.

The above discussion primarily refers to microprocessors or multi-core processors that run software, but one or more implementations are run by one or more integrated circuits, such as ASICs or FPGAs (s). Will be done. In one or more implementations, such an integrated circuit executes instructions stored in the circuit itself.

Those skilled in the art may implement the various exemplary blocks, modules, elements, components, methods, and algorithms described herein as electronic hardware, computer software, or a combination thereof. Will understand. To demonstrate this compatibility of hardware and software, various exemplary blocks, modules, elements, components, methods, and algorithms have been generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the design constraints imposed on the particular application and system as a whole. Those skilled in the art will be able to implement the functionality described in various ways for each particular application. The various components and blocks may be arranged differently (eg, arranged in different orders or divided in different ways) without departing from the scope of the subject matter at all.

It will be appreciated that any particular order or hierarchy of blocks in the disclosed process is an example of an exemplary approach. Based on the design choices, it is understood that the particular order or hierarchy of blocks in the process may be rearranged, or all the illustrated blocks may be executed. Both blocks may be executed at the same time. In one or more implementations, multitasking and parallel processing can be advantageous. Moreover, the separation of the various system components in the embodiments described above should not be understood as requiring such separation in any embodiment, and the described program components and systems are generally united together. It should be understood that it may be integrated into a single software product or packaged into multiple software products.

As used herein and in any of the claims of this application, the terms "base station", "receiver", "computer", "server", "processor", and "memory" are all used. Refers to electronic or other technical devices. These terms exclude a person or a group of people. For the purposes of this specification, the terms "display" or "displaying" mean displaying on an electronic device.

As used herein, the phrase "at least one" preceding a series of items, along with the terms "and" or "or" that separate any of the items, is an element of the list (ie, each item). Instead, qualify the list as a whole. The phrase "at least one" does not require at least one selection of each listed item, but rather the phrase is at least one of any one of the items and / or of the item. Allows meaning to include at least one of any combination and / or at least one of each of the items. As an example, the phrases "at least one of A, B, and C" or "at least one of A, B, or C" are A only, B only, or C only, A, respectively. , B, and C, and / or at least one of each of A, B, and C.

The predicates "configured to", "operable to", and "programmed to" are tangible or peculiar to the object. It does not mean an intangible modification, but rather is intended to be used interchangeably. In one or more embodiments, a processor configured to monitor and control an operation or component means that the processor is programmed to monitor and control the operation, or the processor monitors the operation. And it can also mean that it can operate to control. Similarly, a processor configured to execute code can be interpreted as a processor programmed to execute code or capable of operating to execute code.

One aspect, its aspect, another aspect, some aspects, one or more aspects, one mounting form, its mounting form, another mounting form, some mounting forms, one or more mounting forms, 1 One embodiment, its embodiment, another embodiment, some embodiments, one or more embodiments, one configuration, its configuration, another configuration, some configurations, one or more configurations, the subject matter. The technology, disclosures, present disclosures, other variants thereof, and similar phrases are for convenience only, and disclosures relating to such phrases (s) are essential to the subject technology, or such. It does not imply that the disclosure applies to all configurations of the subject technology. Disclosures relating to such phrases (s) may apply to all configurations, or to one or more constructs. Disclosure of such phrases (s) can provide one or more examples. A phrase such as an aspect or some aspects can refer to one or more aspects and vice versa, which applies like any other aforementioned phrase.

The word "exemplary" is used herein to mean "to act as an example, case, or example." Any embodiment described herein as "exemplary" or "example" should not necessarily be construed as preferred or advantageous over other embodiments. Further, as long as terms such as "include" and "have" are used in the specification or claims, such terms are used when "provide" is used as a transitional term in the claims. As interpreted, it is intended to be inclusive in a manner similar to the term "prepare".

All structural and functional equivalents to the elements of the various aspects described throughout this disclosure, which will be known to those of skill in the art or will become known later, are expressly incorporated herein by reference. And it is intended to be included in the scope of claims. Moreover, none of the disclosures herein are intended to be made public, whether or not such disclosures are explicitly listed in the claims. Elements of any claim are either explicitly enumerated using the phrase "means for" or, in the case of a method claim, the element is the phrase "step for". Unless listed using, it should not be construed under the provisions of Article 35, paragraph 112, paragraph 6 of the US Patent Act.

The above description is provided to allow one of ordinary skill in the art to implement the various aspects described herein. Various changes to these embodiments will be readily apparent to those of skill in the art, and the general principles defined herein can be applied to other embodiments as well. Therefore, the claims are not intended to be limited to the embodiments set forth herein, and the full scope of the claims in accordance with the wording should be accepted, and references to elements in the singular form should be accepted. Unless otherwise noted, it is not intended to mean "one and only one", but rather "one or more". Unless otherwise stated, the term "some" refers to one or more. Male pronouns (eg, he) include female and neutral genders (eg, she and her), and vice versa. Headings and subheadings, if any, are used for convenience only and do not limit the disclosure of the present application.

Claims (21)

It ’s a device
A payment applet associated with a service provider, the payment applet comprising a first attribute indicating whether the payment applet can be used for a wireless transaction associated with the service provider without user authentication. Received an applet that it was provisioned on the secure element of the device
Another payment applet associated with the service provider is provisioned on the secure element of the device, and the first attribute of the other payment applet is for the wireless transaction associated with the service provider. When indicating that it can be used without the user authentication, the user authentication is required to use the payment applet in the wireless transaction associated with the service provider by setting the first attribute of the payment applet. Indicates that, otherwise, leave the first attribute of the payment applet unchanged.
The payment applet or the other for the wireless transaction associated with the service provider, at least in part based on the first attribute of the payment applet and the first attribute of the other payment applet. A device comprising at least one processor configured to control whether or not to request the user authentication when using the payment applet of. The at least one processor
When the first attribute of the other payment applet indicates that the other payment applet can be used for the wireless transaction associated with the service provider without the user authentication, on the secure element of the device. Requires the user authentication to execute the wireless transaction with each additional payment applet by setting the first attribute of each additional payment applet associated with the service provider provisioned in The device of claim 1, further configured to indicate that. The device of claim 1, wherein the service provider includes a transit provider. The device of claim 1, wherein the payment applet is associated with a stored monetary value and the result of the wireless transaction is a reduction in the stored monetary value associated with the payment applet. The payment applet further includes a second attribute indicating that the first attribute can be locally configured by the device without interacting with the server, and additional payment applets associated with other service providers include the device. Provisioned on said secure element of, said additional payment applet indicates that the additional payment applet cannot be used without said user authentication for another wireless transaction associated with said other service provider. The first aspect of claim 1 comprises an additional first attribute and an additional second attribute indicating that the additional first attribute is not locally configurable by the device without contacting the server. Device. The first attribute of the payment applet indicates that the payment applet can be used for the wireless transaction associated with the service provider without user authentication, and the additional payment applet associated with the additional service provider , The additional payment applet, provisioned on the secure element of the device, indicates that the additional payment applet can be used for additional wireless transactions with the additional service provider without the user authentication. The device of claim 1, comprising the first attribute. The at least one processor
Detects one or more signals from a wireless payment terminal and
Determining if the wireless payment terminal is associated with the service provider or the additional service provider, based at least in part on the one or more signals.
When the wireless payment terminal is associated with the service provider, the wireless payment terminal using the payment applet can be used to execute the wireless transaction without the user authentication.
When the wireless payment terminal is associated with the additional service provider, the wireless payment terminal utilizing the additional payment applet can be used to execute the additional wireless transaction without the user authentication. The device of claim 6, further configured as such. The at least one processor
If the user authentication is not received for a certain period of time,
Whether or not the first attribute of the payment applet is set to indicate that the payment applet can be used for the wireless transaction associated with the service provider without the user authentication. The device of claim 7, further configured to require the user authentication before enabling the wireless transaction to be performed using the wireless payment terminal that utilizes an applet. The device according to claim 7, wherein the one or more signals include a short-range communication signal. The at least one processor
The first attribute of the payment applet is set to indicate that the user authentication is required to use the payment applet in the wireless transaction without contacting the server. The device according to claim 1. The first attribute of the payment applet indicates that the payment applet can be used for the wireless transaction associated with the service provider without the user authentication, the at least one processor.
Receives a request to make the other payment applet available to the wireless transaction associated with the service provider without the user authentication.
The first attribute of the payment applet is set to indicate that the payment applet cannot be used for the wireless transaction associated with the service provider without the user authentication.
Request the user authentication
Upon receiving the user authentication, the first attribute of the other payment applet is set so that the other payment applet can be used for the wireless transaction associated with the service provider without the user authentication. The device of claim 1, further configured as shown. It's a method
The device detects one or more polling signals transmitted by a wireless payment terminal, and
Identifying the service provider associated with the wireless payment terminal, at least in part, based on the one or more polling signals.
Determining if the payment applet associated with the service provider is provisioned on the secure element of the device, the payment applet does not authenticate the user for the wireless transaction associated with the service provider. Includes an attribute indicating that the payment applet can be used in
When the payment applet includes the attribute indicating that the payment applet can be used for the wireless transaction associated with the service provider without the user authentication, the wireless payment terminal associated with the service provider Making the payment applet available to the wireless transaction without the user authentication, and otherwise, the payment applet for the wireless transaction with the wireless payment terminal associated with the service provider. A method, including requesting said user authentication before making available. Identifying the service provider associated with the wireless payment terminal based at least in part on the one or more signals
12. The method of claim 12, further comprising identifying the service provider associated with the wireless payment terminal based at least in part on the one or more signals and the determined location of the device. Identifying the service provider associated with the wireless payment terminal based at least in part on the one or more signals can be said.
At least partially in at least one of the information carried by the one or more signals, the pattern associated with the one or more signals, or at least one length of the one or more signals. 12. The method of claim 12, further comprising identifying the service provider associated with the wireless payment terminal. The secure element includes said other payment applet that includes an attribute indicating that no other payment applet can be used without said user authentication for the wireless transaction associated with the service provider.
When the service provider associated with the wireless payment terminal is identified, the user with respect to the wireless transaction with the wireless payment terminal associated with the service provider and with respect to the wireless transaction associated with the service provider. 12. The method of claim 12, further comprising selecting the payment applet that includes the attribute indicating that the payment applet can be used without authentication. It ’s a system,
A wireless communication controller configured to detect one or more polling signals transmitted by a wireless payment terminal and participate in a wireless transaction with the wireless payment terminal.
A secure element configured to store a plurality of payment applets, each of the plurality of payment applets being associated with one of the plurality of service providers, among the plurality of payment applets. The first payment applet includes an attribute indicating whether or not the first payment applet can be used without user authentication, and the first payment applet is the first service of the plurality of service providers. With the secure element associated with the provider,
It ’s a processor,
Upon receiving the one or more polling signals transmitted by the wireless payment terminal from the wireless communication controller,
Based on at least partly based on the one or more polling signals, it is determined that the wireless payment terminal is associated with the first service provider.
When the attribute of the first payment applet indicates that the first payment applet can be used without the user authentication, the wireless communication controller uses the first payment applet to and the wireless payment terminal. Allows the wireless communication controller to participate in the wireless transaction without the user authentication, and in other cases, allows the wireless communication controller to interlock with the wireless transaction with the wireless payment terminal using the first payment applet. A system comprising a processor, previously configured to require said user authentication. The system according to claim 16, wherein the wireless communication controller includes a short-range communication controller. 16. The system of claim 16, wherein the processor comprises the secure element. 16. The system of claim 16, wherein the processor is further configured to modify the attributes of the first payment applet without assistance from the server. The processor
The wireless communication controller receives a request to allow the wireless communication controller to participate in the wireless transaction with the wireless payment terminal using the second payment applet without the user authentication.
The attribute of the first payment applet is set to a first value indicating that the first payment applet cannot be used without the user authentication.
16. The system of claim 16, further configured to set the attributes of the second payment applet to a second value indicating that the second payment applet can be used without the user authentication. The second payment applet of the plurality of payment applets is associated with a second service provider different from the first service provider of the service providers.
16. The 16. system.

Images