Patent Application
20150161587
This disclosure relates to the provisioning and authentication of credentials on an electronic device and, more particularly, to the provisioning and authentication of virtual commerce credentials on an electronic device.
Portable electronic devices (e.g., cellular telephones) may be provided with near field communication (“NFC”) components for enabling contactless proximity-based communications with another entity. Often times, these communications are associated with financial transactions or other secure data transactions that require the electronic device to access and share a commerce credential, such as a credit card credential or a public transportation ticket credential. However, such contactless proximity-based communications often expose such commerce credentials to interception by rogue entities.
This document describes systems, methods, and computer-readable media for provisioning and authenticating credentials on an electronic device that is capable of near field communications and/or other wireless communications.
For example, a financial institution system may be in communication with an electronic device and a merchant subsystem. The financial institution system may include at least one processor component, at least one memory component, and at least one communications component, where the financial institution system may be configured to create a link between an actual commerce credential and a virtual commerce credential, provision the virtual commerce credential on the electronic device, after the virtual commerce credential is provisioned on the electronic device, receive a transaction request from the merchant subsystem, identify the virtual commerce credential from the received transaction request, and, in response to the identification of the virtual commerce credential, determine if the link between the actual commerce credential and the virtual commerce credential is authenticated for use in a financial transaction.
As another example, a method may include creating with a financial institution subsystem a link between an actual commerce credential and a virtual commerce credential. After the creating, the method may also include facilitating the provisioning of the virtual commerce credential on an electronic device using the financial institution subsystem. After the provisioning of the virtual commerce credential on the electronic device, the method may also include authenticating the link between the actual commerce credential and the virtual commerce credential using the financial institution subsystem.
As yet another example, a merchant system may be in communication with an electronic device and a financial institution subsystem. The merchant system may include a processor component, a memory component, and a communications component, where the merchant system may be configured to receive a contactless proximity-based communication from the electronic device, transmit information indicative of a device commerce credential of the received communication to the financial institution subsystem, receive an authorization request from the financial institution subsystem based on the transmitted information, and prompt a user of the electronic device to provide authentication information for an actual commerce credential based on the received authorization request.
As yet another example, a financial institution system may be in communication with a merchant subsystem. The financial institution system may include at least one processor component, at least one memory component, and at least one communications component, where the financial institution system may be configured to receive a virtual commerce credential from a merchant subsystem, detect a link between the received virtual commerce credential and an actual commerce credential, and determine if the detected link is authenticated.
As yet another example, a non-transitory computer-readable medium may include computer-readable instructions recorded thereon for detecting a link between a virtual commerce credential and an actual commerce credential, and determining if the detected link is authenticated.
As yet another example, a financial institution system may be in communication with at least one of an electronic device and a merchant subsystem. The financial institution system may include at least one processor component, at least one memory component, and at least one communications component, where the financial institution system may be configured to create a link between an actual commerce credential and a virtual commerce credential, facilitate the provisioning of the virtual commerce credential on the electronic device, and authenticate the link between the actual commerce credential and the virtual commerce credential after the provisioning of the virtual commerce credential on the electronic device.
This Summary is provided merely to summarize some example embodiments, so as to provide a basic understanding of some aspects of the subject matter described in this document. Accordingly, it will be appreciated that the features described in this Summary are merely examples and should not be construed to narrow the scope or spirit of the subject matter described herein in any way. Other features, aspects, and advantages of the subject matter described herein will become apparent from the following Detailed Description, Figures, and Claims.
The discussion below makes reference to the following drawings, in which like reference characters may refer to like parts throughout, and in which:
The provisioning of a commerce credential on an electronic device for later use in a secure data transaction may include a financial institution identifying an actual commerce credential, linking that actual commerce credential with a virtual commerce credential, and provisioning that virtual commerce credential rather than the actual commerce credential on the electronic device. Later, when a merchant receives a financial transaction request from the electronic device (e.g., as a contactless proximity-based communication) that includes the virtual commerce credential, the merchant may forward to the financial institution the financial transaction request with the virtual commerce credential, and then the financial institution may identify the actual commerce credential that was previously linked to that virtual commerce credential and may attempt to fund the financial transaction request using that actual commerce credential. The link between the virtual commerce credential and the actual commerce credential may be created but not authenticated when the virtual commerce credential is provisioned on the electronic device, such that the first time the electronic device uses the provisioned virtual commerce credential in a financial transaction request, the financial institution may detect the actual commerce credential linked to that virtual commerce credential but may determine that the link has not yet been authenticated. In such cases, before attempting to fund the financial transaction request using that linked but non-authenticated actual commerce credential, the financial institution may leverage the merchant to obtain the necessary information from the user of the electronic device for properly authenticating the link.
As shown in
Merchant subsystem 200 of
As shown in
Referring back to system 1 of
Payment network subsystem 360 and issuing bank subsystem 370 may be a single entity or separate entities. For example, American Express may be both a payment network subsystem 360 and an issuing bank subsystem 370. In contrast, Visa and MasterCard may be payment network subsystems 360, and may work in cooperation with issuing bank subsystems 370, such as Chase, Wells Fargo, Bank of America, and the like. Financial institution subsystem 350 may also include one or more acquiring banks, such as acquiring bank subsystem 300. For example, acquiring bank subsystem 300 may be the same entity as issuing bank subsystem 370. One, some, or all components of payment network subsystem 360 may be implemented using one or more processor components, which may be the same as or similar to processor component 102 of device 100, one or more memory components, which may be the same as or similar to memory component 104 of device 100, and/or one or more communications components, which may be the same as or similar to communications component 106 of device 100. One, some, or all components of issuing bank subsystem 370 may be implemented using one or more processor components, which may be the same as or similar to processor component 102 of device 100, one or more memory components, which may be the same as or similar to memory component 104 of device 100, and/or one or more communications components, which may be the same as or similar to communications component 106 of device 100.
To facilitate transactions within system 1, one or more commerce credentials may be provisioned on electronic device 100. However, before provisioning a credential on device 100, a user of device 100 may attempt to prove that he or she is an authorized user of the credential and that the credential is in good standing. As shown in
The commercial entity that may provide, manage, or at least partially control commercial entity subsystem 400 may also provide different users with their own personalized accounts for using the services offered by that commercial entity. Each user account with the commercial entity may be associated with a specific personalized user ID and password that a user may use to log-in to their account with the commercial entity. Each user account with the commercial entity may also be associated with or have access to at least one commerce credential that can then be used by the user for purchasing services or products offered by the commercial entity. For example, each Apple ID user account may be associated with at least one credit card of a user associated with that Apple ID, such that the credit card may then be used by the user of that Apple ID account for procuring services from Apple's iTunes™ Store, the Apple App Store™, the Apple iCloud™ Service, and the like. The commercial entity that may provide, manage, or at least partially control commercial entity subsystem 400 (e.g., Apple Inc.) may be distinct and independent from any financial entity of financial institution subsystem 350. For example, the commercial entity that may provide, manage, or at least partially control commercial entity subsystem 400 may be distinct and independent from any payment network subsystem 360 or issuing bank subsystem 370 that may furnish and manage any credit card or other commerce credential associated with a user account of the commercial entity. Similarly, the commercial entity that may provide, manage, or at least partially control commercial entity subsystem 400 may be distinct and independent from any payment network subsystem 360 or issuing bank subsystem 370 that may furnish and manage any commerce credential to be provisioned on user device 100. Such a commercial entity may leverage the known commerce credential information associated with each of its user accounts and/or any suitable information that commercial entity subsystem 400 may determine about device 100 (e.g., various communication mechanisms enabled by device 100) in order to more securely determine with commercial entity subsystem 400 whether a specific credential offered by financial institution subsystem 350 ought to be provisioned on a user device 100. Additionally or alternatively, such a commercial entity may leverage its ability to configure or control various components of device 100 (e.g., software and/or hardware components of device 100 when that commercial entity at least partially produces or manages device 100) in order to provide a more seamless user experience for a user of device 100 when he or she wants to provision a credential offered by financial institution subsystem 350 on user device 100. Details regarding an example of how commercial entity subsystem 400 may be implemented are provided below with reference to
As shown in
SMP broker component 410 of commercial entity subsystem 400 may be configured to manage user authentication with a commercial entity user account. SMP broker component 410 may also be configured to manage the lifecycle and provisioning of credentials on device 100. SMP broker component 410 may be a primary end point that may control the user interface elements (e.g., elements of GUI 180) on device 100. An operating system or other application of device 100 (e.g., application 103, application 113, and/or application 143) may be configured to call specific application programming interfaces (“APIs”) and SMP broker 410 may be configured to process requests of those APIs and respond with data that may derive the user interface of device 100 and/or respond with application protocol data units (“APDUs”) that may communicate with the secure element of NFC component 120 (e.g., via a communication path 65 between commercial entity subsystem 400 and electronic device 100). Such APDUs may be received by commercial entity subsystem 400 from financial institution subsystem 350 via a trusted services manager (“TSM”) of system 1 (e.g., a TSM of a communication path 55 between commercial entity subsystem 400 and financial institution subsystem 350). SMP TSM component 420 of commercial entity subsystem 400 may be configured to provide GlobalPlatform-based services that may be used to carry out credential provisioning operations on device 100 from financial institution subsystem 350. GlobalPlatform, or any other suitable secure channel protocol, may enable SMP TSM component 420 to properly communicate and/or provision sensitive account data between the secure element of device 100 and a TSM for secure data communication between commercial entity subsystem 400 and financial institution subsystem 350.
SMP TSM component 420 may be configured to use HSM component 460 to protect its keys and generate new keys. SMP crypto services component 430 of commercial entity subsystem 400 may be configured to provide key management and cryptography operations that may be required for user authentication and/or confidential data transmission between various components of system 1. SMP crypto services component 430 may utilize HSM component 460 for secure key storage and/or opaque cryptographic operations. A payment crypto service of SMP crypto services component 430 may be configured to interact with IDMS component 440 to retrieve on-file credit cards or other types of commerce credentials associated with user accounts of the commercial entity. Such a payment crypto service may be configured to be the only component of commercial entity subsystem 400 that may have clear text (i.e., non-hashed) information describing commerce credentials (e.g., credit card numbers) of its user accounts in memory. Commercial entity fraud system component 450 of commercial entity subsystem 400 may be configured to run a commercial entity fraud check on a commerce credential based on data known to the commercial entity about the commerce credential and/or the user (e.g., based on data (e.g., commerce credential information) associated with a user account with the commercial entity and/or any other suitable data that may be under the control of the commercial entity and/or any other suitable data that may not be under the control of financial institution subsystem 350). Commercial entity fraud system component 450 may be configured to determine a commercial entity fraud score for the credential based on various factors or thresholds. Additionally or alternatively, commercial entity subsystem 400 may include a store 470, which may be a provider of various services to users of device 100 (e.g., the iTunes™ Store for selling/renting media to be played by device 100, the Apple App Store™ for selling/renting applications for use on device 100, the Apple iCloud™ Service for storing data from device 100, the Apple Online Store for buying various Apple products online, etc.). As just one example, store 470 may be configured to manage and provide an application 113 to device 100 (e.g., via communications path 65), where application 113 may be any suitable application, such as a banking application, an e-mail application, a text messaging application, an internet application, or any other suitable application. Any suitable communication protocol or combination of communication protocols may be used by commercial entity subsystem 400 to communicate data amongst the various components of commercial entity subsystem 400 (e.g., via at least one communications path 495 of
As shown in
In response to receiving a user selected card request as at least a portion of credential provisioning request data 552 at step 502, an SSD may be created by commercial entity subsystem 400 (e.g., by SMP broker component 410) at step 504. For example, an identifier for an SSD of device 100 (e.g., an SSD 154 of NFC component 120) into which the credential is to be provisioned may be created at step 504, where the SSD may be at least partially determined based on the secure element information (e.g., an SSD identifier) that may be provided by request data 552 of step 502. Next, after step 504, commercial entity subsystem 400 (e.g., SMP broker component 410) may send a request to financial institution subsystem 350 for the provisioning of the selected credential on device 100 (e.g., using any suitable communications protocol over any suitable communications path 55 (e.g., via a TSM of path 55)). For example, at step 506 of process 500 of
In response to receiving such credential provisioning instruction data 556 from commercial entity subsystem 400, financial institution subsystem 350 (e.g., payment network subsystem 360) may be configured to generate a descriptor of the selected credential to be provisioned, as well as visual artwork and other metadata that may be provided on device 100 for aiding user interaction with the credential once provisioned. For example, at step 510 of process 500 of
In some embodiments, system 1 and/or process 500 may be configured to provision a virtual credential on device 100 rather than the actual credential that may be identified at step 502 and/or that may be used for the fraud risk analysis of step 503. For example, once it is determined that a credential is to be provisioned on device 100, it may be requested (e.g., by financial institution subsystem 350 at step 508, by commercial entity subsystem 400 at step 506, and/or by a user of device 100 at step 502) that a virtual credential be generated, linked to the actual credential, and provisioned on device 100 instead of the actual credential. That is, commercial entity subsystem 400 may generate and transmit credential provisioning instruction data 556 to financial institution subsystem 350 at step 506 that may also include a specific instruction for financial institution subsystem 350 to create a new virtual credential (e.g., a device primary account number (“D-PAN”)), link that virtual credential with the selected actual credential (i.e., a funding primary account number (“F-PAN”) originally issued by the issuing bank), and then provision that virtual credential onto device 100. Accordingly, in such embodiments, financial institution subsystem 350 may generate and transmit credential provisioning response data 560 back to commercial entity subsystem 400 at step 510 that may include a descriptor of the virtual credential (e.g., the D-PAN) to be provisioned and any suitable metadata that ought to be provided on device 100 for aiding user interaction with the virtual credential to be provisioned. Alternatively, in some embodiments, electronic device 100 may generate and transmit credential provisioning request data 552 at step 502 that may also include a specific instruction for financial institution subsystem 350 to create, link, and provision such a new virtual credential rather than the actual credential indicated by credential provisioning request data 552, where such a specific instruction may be passed on to financial institution subsystem 350 via credential provisioning instruction data 556 at step 506. Alternatively, in some embodiments, financial institution subsystem 350 may make a determination to create, link, and provision a new virtual credential rather than the actual credential indicated by data 552/556.
Such linking or other suitable association of a virtual credential with an actual credential may be performed by any suitable component of financial institution subsystem 350. For example, financial institution subsystem 350 (e.g., a particular payment network subsystem 360 that may be associated with the brand of the actual credential identified at step 502) may define and store an entry 702 in a virtual-linking table or data structure 352 (e.g., as shown in
Next, in response to receiving credential provisioning response data 560, commercial entity subsystem 400 (e.g., SMP broker component 410) may pass some or all of the information contained in that credential provisioning response data 560 to device 100 in order to at least partially prepare device 100 for having a credential provisioned thereon. For example, at step 512 of process 500 of
Next, in response to receiving such pass data 562 from commercial entity subsystem 400, device 100 may be configured to generate and add a disabled pass to an SSD 154 of NFC memory module 150 (e.g., automatically, without any required user interaction at device 100). For example, at step 514 of process 500 of
Moreover, before, after, or at least partially concurrently with step 510, financial institution subsystem 350 may initiate generation and transmission of put pending commands for commercial entity subsystem 400 and, thus, device 100. For example, at step 516 of process 500 of
Therefore, the state of the secure element on device 100 (e.g., whether the credential's PAN is enabled for use in NFC component 120) may be updated at step 520 asynchronously with (e.g., later than) an availability status of the credential that may be provided to a user of device 100 (e.g., provided visually in a Passbook or Wallet application on I/O interface 114a) at step 514. This may enable the credential to appear ready for use to a user of device 100 before it is actually ready for use, thereby providing a more desirable user experience (e.g., an apparently faster provisioning time). Once the selected credential is at least disabled on device 100 (e.g., as either the actual credential or a linked virtual credential) at step 514 and/or enabled at step 520, device 100 may automatically generate a user interface that may inform the user that the credential has been successfully provisioned. For example, GUI 180 may provide a screen on I/O interface 114a, where electronic device 100 may provide a message to the user indicative of the completed provisioning and enablement of the selected credential. Alternatively, financial institution subsystem 350 may be configured to generate and transmit the contents of credential provisioning response data 560 and pending command data 566 at the same time in a single step (e.g., step 510) rather than as distinct sets of data in different steps. Additionally or alternatively, commercial entity subsystem 400 may be configured to generate and transmit the contents of pass data 562 and notification data 568 at the same time in a single step (e.g., step 518) rather than as distinct sets of data in different steps. Alternatively or additionally, although not shown in
Once a credential has been provisioned and enabled on device 100 (e.g., at step 520), process 500 may also authenticate and use that credential in a financial transaction. Referring back to system 1 of
When financial institution subsystem 350 receives an authorization request (e.g., from acquiring bank subsystem 300 as acquiring bank attempted purchase data 576), the payment information may be analyzed by financial institution subsystem 350 at step 528 of process 500 of
As mentioned, in response to receiving virtual commerce credential data in an authorization request (e.g., from acquiring bank subsystem 300 as acquiring bank attempted purchase data 576), financial institution subsystem 350 may leverage virtual-linking data structure 352 or any other suitable data to determine whether or not the link between that virtual credential and its associated actual credential (i.e., its associated F-PAN) has been authenticated in one or more suitable ways such that the virtual credential may be used in a financial transaction. For example, as shown in
Therefore, in response to receiving virtual commerce credential data in an authorization request (e.g., from acquiring bank subsystem 300 as acquiring bank attempted purchase data 576), financial institution subsystem 350 may leverage virtual-linking data structure 352 at step 528 of process 500 to determine whether or not the link between that virtual credential (e.g., as indicated by a matching D-PAN 704 of a particular entry 702) and its associated actual credential (e.g., as indicated by the F-PAN 706 of that entry 702) has been authenticated (e.g., as indicated by the link authentication status 708 of that entry 702). If at step 528 it is determined that a link between the virtual credential identified in an attempted financial transaction and an associated actual credential is authenticated, process 500 may jump to step 538, whereby that associated actual credential may be used to fund the financial transaction, as described in more detail below. However, if at step 528 it is determined that a link between the virtual credential identified in an attempted financial transaction and an associated actual credential is not authenticated, process 500 may proceed to step 530, whereby system 1 may attempt to appropriately authenticate that link.
A link between a virtual credential provisioned on electronic device 100 and an associated actual credential may be authenticated in various suitable ways. For example, in some embodiments, financial institution subsystem 350 may leverage merchant subsystem 200 in order to attempt to acquire suitable information from a user of device 100 that may appropriate authentication of the user to the linked actual credential. As shown in
Next, in response to receiving such authentication request data 580 (e.g., at merchant communications component 206 of
Next, in response to receiving such user authentication information at step 532 (e.g., via merchant I/O interface 214), merchant subsystem 200 may be configured to generate and transmit data indicative of the user's response back to financial institution subsystem 350. For example, at step 534 of process 500, merchant subsystem 200 may be configured to generate and transmit authentication response data 584 (e.g., via merchant communications component 206) indicative of the user's authentication information back to financial institution subsystem 350, either directly (e.g., via communications path 85 of
Next, in response to receiving such authentication response data 584 from merchant subsystem 200, financial institution subsystem 350 may be configured to determine whether or not the user's answer(s) may appropriately authenticate the user to the actual credential or F-PAN 706 identified at step 528 and thus appropriately authenticate the non-authenticated link between the virtual credential and the actual credential identified at step 528. For example, at step 536 of process 500, financial institution subsystem 350 may be configured to receive authentication response data 584 from merchant subsystem 200 and to determine whether or not the user's answer(s) provided by that authentication response data 584 may be used to authenticate the user to the actual credential or F-PAN 706 identified at step 528 (e.g., by comparing the user's response of authentication response data 584 with verified user information already known to financial institution subsystem 350 in association with the actual credential identified at step 528 (e.g., particular verified user information that may already be known by and accessible to an issuing bank subsystem 370 that originally issued the actual credential to its rightful user)). If at step 536 it is determined by financial institution subsystem 350 that authentication response data 584 is not able to authenticate a user of device 100 with the actual credential identified at step 528, then the link between that actual credential and the particular virtual credential also identified at step 528 may remain non-authenticated (e.g., by maintaining the link authentication status 708 of the appropriate entry 702 of data structure 352 that links that actual credential and that virtual credential as “not authenticated”) and then process 500 may return to step 530 in order to once again attempt to authenticate the link or process 500 may proceed with any other suitable course of action. However, if at step 536 it is determined by financial institution subsystem 350 that authentication response data 584 is able to authenticate a user of device 100 with the actual credential identified at step 528, then the link between that actual credential and the particular virtual credential also identified at step 528 may be authenticated (e.g., by updating the link authentication status 708 of the appropriate entry 702 of data structure 352 that links that actual credential and that virtual credential from “not authenticated” to “authenticated”) and process 500 may proceed to step 538, whereby that associated and authenticated actual credential may be used to fund the financial transaction. Therefore, an actual credential may be identified as the basis for credential provisioning on device 100 (e.g., at step 502), then a virtual credential may be associated or linked with that actual credential (e.g., at step 508), and then that virtual credential may be provisioned on device 100 (e.g., at steps 510-520), where such provisioning may occur without device 100 or a user of device 100 providing any information for authenticating the link between that virtual credential and the actual credential and/or for authenticating the user's association to the actual credential. Then, after the actual credential has been identified, after the virtual credential has been associated or linked with that actual credential, and after that virtual credential has been provisioned on device 100, the link between that virtual credential and that actual credential may be authenticated (e.g., at steps 528-536). Such authentication may not require any interaction with device 100 (e.g., any user interaction and/or any communication between device 100 and any subsystem of system 1). Moreover, such authentication may not require any alteration of data on device 100, any removal of data from device 100, and/or any addition of data onto device 100.
Various other types of data may be generated and/or stored by financial institution subsystem 350 (e.g., in data structure 352) in response to analyzing received authentication response data 584 at step 536. For example, as shown in
When financial institution subsystem 350 identifies an authenticated link between a particular virtual credential (e.g., of acquiring bank attempted purchase data 576) and an associated actual credential (e.g., through leveraging data structure 352 at step 528 and/or step 536), process 500 may proceed to step 538, whereby that associated actual credential may be used by financial institution subsystem 350 to attempt to fund the requested financial transaction. For example, if financial institution subsystem 350 may leverage table 352 to determine that the commerce credential information of NFC communication 15 between device 100 and merchant terminal 220 is indicative of a virtual credential (e.g., a D-PAN 704 of data structure 352) that has an authenticated link to an actual credential (e.g., an associated F-PAN 706 of data structure 352), then financial institution subsystem 350 may determine at step 538 whether the account associated with that actual credential or F-PAN 706 has enough credit to cover the purchase amount of the attempted financial transaction (e.g., as may be identified by acquiring bank attempted purchase data 576). If sufficient funds are not present, financial institution subsystem 350 may decline the requested transaction by transmitting negative authorization response data 588 to acquiring bank subsystem 300 at step 538. However, if sufficient funds are present, financial institution subsystem 350 may approve the requested transaction by transmitting positive authorization response data 588 to acquiring bank subsystem 300 at step 538 and the financial transaction may be completed. Either type of authorization response may be provided by financial institution subsystem 350 to acquiring bank subsystem 300 as authorization response data 588 (e.g., via communications path 35 using any suitable communications protocol) at step 538 of process 500 of
It is understood that the steps shown in process 500 of
As mentioned, financial institution subsystem 350 may include a payment network subsystem 360 (e.g., a payment card association or a credit card association) and/or an issuing bank subsystem 370, where payment network subsystem 360 and issuing bank subsystem 370 may be a single entity or separate entities. For example, American Express may be both a payment network subsystem 360 and an issuing bank subsystem 370. In contrast, Visa and MasterCard may be payment network subsystems 360, and may work in cooperation with issuing bank subsystems 370, such as Chase, Wells Fargo, Bank of America, and the like. In instances where payment network subsystem 360 and issuing bank subsystem 370 may be separate entities, payment network subsystem 360 and issuing bank subsystem 370 may communicate with one another to ensure proper authentication of a link between a virtual credential and an actual credential and/or to complete the financial transaction. For example, as shown in
As shown in
As with process 500, rather than requiring a user of device 100 to authenticate that he or she is the rightful owner of an actual credential selected during the provisioning of an associated virtual credential on device 100 (e.g., by providing personal user-identifiable information from device 100 to financial institution subsystem 350 during the provisioning of an associated virtual credential on device 100, where such personal user-identifiable information may be authenticated by financial institution subsystem 350 based on verified user information already known to financial institution subsystem 350 in association with the actual credential), process 500A may be configured to enable a user of device 100 to authenticate that he or she is the rightful owner of an actual credential associated with a provisioned virtual credential during an attempted financial transaction. However, when payment network subsystem 360 may be provided in system 1 as an interface between issuing bank subsystem 370 and various acquiring bank subsystems 300 (e.g., to minimize direct integration points of financial institution subsystem 350 by acting as an aggregator for various issuing banks 370 and/or for various acquiring banks 300 (e.g., during financial transactions)) and/or as an interface between issuing bank subsystem 370 and various commercial entity subsystems 400/devices 100 (e.g., to minimize direct integration points of financial institution subsystem 350 by acting as an aggregator for various issuing banks 370 and/or for various commercial entity subsystems 400/devices 100 (e.g., during credential provisioning)), it may be burdensome for such a payment network subsystem 360 to authenticate a user with an actual credential, as verified personal user-identifiable information associated with the actual credential may not be accessible to payment network subsystem 360 (e.g., such verified personal user-identifiable information associated with the actual credential may only be accessible by a particular issuing bank subsystem 370 that originally issued that actual credential). Therefore, as shown by steps 536a-536e of process 500A, payment network subsystem 360 and particular issuing bank subsystem 370 may work together to ensure proper authentication of a link between a virtual credential and an actual credential and/or to complete the financial transaction.
At step 536a of process 500, payment network subsystem 360 may be configured to receive authentication response data 584 from merchant subsystem 200 and to associate such authentication response data 584 with the appropriate actual credential (e.g., the F-PAN 706 identified at step 528), for example, by storing such authentication response data 584 in the appropriate entry 702 of data structure 352 that may include the D-PAN 704 identified at step 528). Next, at step 536b, payment network subsystem 360 may be configured to transmit authentication/transaction request data 586b to a particular issuing bank subsystem 370 (e.g., via communications path 45 of
If it is determined by issuing bank subsystem 370 at step 536c that authentication response data 584 identified by authentication/transaction request data 586b is not able to authenticate the actual credential or F-PAN 706 identified by authentication/transaction request data 586b, then issuing bank subsystem 370 may generate and transmit a first type of authentication/transaction response data 586d to payment network subsystem 360 at step 536d (e.g., via communications path 45 of
However, if it is determined by issuing bank subsystem 370 at step 536c that authentication response data 584 identified by authentication/transaction request data 586b is able to authenticate the actual credential or F-PAN 706 identified by authentication/transaction request data 586b, then issuing bank subsystem 370 may also determine at step 536c whether the account associated with that actual credential or F-PAN 706 has enough credit to cover the purchase amount of the attempted financial transaction (e.g., as may be identified by authentication/transaction request data 586b). If issuing bank subsystem 370 determines at step 536c that sufficient funds are not present, financial institution subsystem 350 may decline the requested transaction by generating and transmitting a second type of authentication/transaction response data 586d to payment network subsystem 360 at step 536d (e.g., via communications path 45 of
However, if it is determined by issuing bank subsystem 370 at step 536c that authentication response data 584 identified by authentication/transaction request data 586b is able to authenticate the actual credential or F-PAN 706 identified by authentication/transaction request data 586b and that sufficient funds are present to cover the purchase amount of the attempted financial transaction, financial institution subsystem 350 may accept the requested transaction by generating and transmitting a third type of authentication/transaction response data 586d to payment network subsystem 360 at step 536d (e.g., via communications path 45 of
Moreover, in some embodiments, prior to generating authentication request 580 at step 530 in response to receiving authorization request 576 at step 526, payment network subsystem 360 may request certain authentication request data from issuing bank subsystem 370 that may be associated with the F-PAN linked to the D-PAN identified by authorization request 576. That is, prior to communicating authentication request 580 to merchant subsystem 200 in an attempt to get authentication data from a user for authenticating the link between an identified D-PAN and a linked F-PAN, payment network subsystem 360 may request from issuing bank subsystem 370 what type of information is known to issuing bank subsystem 370 about the F-PAN that may be used to authenticate the link, such as security data that may be used to authenticate the link (e.g., known maiden name of the owner of the F-PAN, etc.) and payment network subsystem 360 may then leverage that information from issuing bank subsystem 370 to generate an appropriate and effective authentication request 580 (e.g., by providing steps similar to steps 536a-536e between step 526 and step 530).
It is understood that the steps shown in process 500A of
It is understood that the steps shown in process 600 of
As mentioned,
Although each entry 702 of data structure 352 may be associated with a unique D-PAN of column 704, two or more entries 702 may be associated with the same actual credential or F-PAN of column 706. For example, as shown, a first actual credential “F-PAN1” of column 706 for entry 702a may have an identifier or F-PAN (e.g., 23456781) and a second actual credential “F-PAN2” of column 706 for entry 702b may have an identifier or F-PAN (e.g., 45678123), while a third actual credential “F-PAN3” of column 706 may have an identifier or F-PAN (e.g., 67812345) for each one of entries 702c and 702d. That is, a single actual credential (i.e., “F-PAN3”) may be linked with two different virtual credentials (i.e., “D-PAN3” and “D-PAN4”) of two different entries (i.e., entries 702c and 702d) of data structure 352, such that a user may provision a first virtual credential on a first device 100 and a second virtual credential on a second device 100 where both virtual credentials are linked to the same single actual credential.
Each row of link authentication status column 708 may include a value or an identifier associated with a value that may indicate that the link between the D-PAN of column 704 and the F-PAN of column 706 for that same row (e.g., for that particular entry 702) is “authenticated” or “not authenticated”. As shown in
As mentioned, and as shown in
As shown in
Memory 104 may include one or more storage mediums, including for example, a hard-drive, flash memory, permanent memory such as read-only memory (“ROM”), semi-permanent memory such as random access memory (“RAM”), any other suitable type of storage component, or any combination thereof. Memory 104 may include cache memory, which may be one or more different types of memory used for temporarily storing data for electronic device applications. Memory 104 may be fixedly embedded within electronic device 100 or may be incorporated on one or more suitable types of cards that may be repeatedly inserted into and removed from electronic device 100 (e.g., a subscriber identity module (“SIM”) card or secure digital (“SD”) memory card). Memory 104 may store media data (e.g., music and image files), software (e.g., for implementing functions on device 100), firmware, preference information (e.g., media playback preferences), lifestyle information (e.g., food preferences), exercise information (e.g., information obtained by exercise monitoring equipment), transaction information (e.g., information such as credit card information), wireless connection information (e.g., information that may enable device 100 to establish a wireless connection), subscription information (e.g., information that keeps track of podcasts or television shows or other media a user subscribes to), contact information (e.g., telephone numbers and e-mail addresses), calendar information, any other suitable data, or any combination thereof.
Communications component 106 may be provided to allow device 100 to communicate with one or more other electronic devices or servers or subsystems (e.g., one or more subsystems or other components of system 1) using any suitable communications protocol. For example, communications component 106 may support Wi-Fi (e.g., an 802.11 protocol), ZigBee (e.g., an 802.15.4 protocol), WiDi™, Ethernet, Bluetooth™, Bluetooth™ Low Energy (“BLE”), high frequency systems (e.g., 900 MHz, 2.4 GHz, and 5.6 GHz communication systems), infrared, transmission control protocol/internet protocol (“TCP/IP”) (e.g., any of the protocols used in each of the TCP/IP layers), Stream Control Transmission Protocol (“SCTP”), Dynamic Host Configuration Protocol (“DHCP”), hypertext transfer protocol (“HTTP”), BitTorrent™, file transfer protocol (“FTP”), real-time transport protocol (“RTP”), real-time streaming protocol (“RTSP”), real-time control protocol (“RTCP”), Remote Audio Output Protocol (“RAOP”), Real Data Transport Protocol™ (“RDTP”), User Datagram Protocol (“UDP”), secure shell protocol (“SSH”), wireless distribution system (“WDS”) bridging, any communications protocol that may be used by wireless and cellular telephones and personal e-mail devices (e.g., Global System for Mobile Communications (“GSM”), GSM plus Enhanced Data rates for GSM Evolution (“EDGE”), Code Division Multiple Access (“CDMA”), Orthogonal Frequency-Division Multiple Access (“OFDMA”), high speed packet access (“HSPA”), multi-band, etc.), any communications protocol that may be used by a low power Wireless Personal Area Network (“6LoWPAN”) module, any other communications protocol, or any combination thereof. Communications component 106 may also include or be electrically coupled to any suitable transceiver circuitry (e.g., transceiver circuitry or antenna 116 via bus 118) that can enable device 100 to be communicatively coupled to another device (e.g., a host computer or an accessory device) and communicate with that other device wirelessly, or via a wired connection (e.g., using a connector port). Communications component 106 may be configured to determine a geographical position of electronic device 100. For example, communications component 106 may utilize the global positioning system (“GPS”) or a regional or site-wide positioning system that may use cell tower positioning technology or Wi-Fi technology.
Power supply 108 can include any suitable circuitry for receiving and/or generating power, and for providing such power to one or more of the other components of electronic device 100. For example, power supply 108 can be coupled to a power grid (e.g., when device 100 is not acting as a portable device or when a battery of the device is being charged at an electrical outlet with power generated by an electrical power plant). As another example, power supply 108 can be configured to generate power from a natural source (e.g., solar power using solar cells). As another example, power supply 108 can include one or more batteries for providing power (e.g., when device 100 is acting as a portable device). For example, power supply 108 can include one or more of a battery (e.g., a gel, nickel metal hydride, nickel cadmium, nickel hydrogen, lead acid, or lithium-ion battery), an uninterruptible or continuous power supply (“UPS” or “CPS”), and circuitry for processing power received from a power generation source (e.g., power generated by an electrical power plant and delivered to the user via an electrical socket or otherwise). The power can be provided by power supply 108 as alternating current or direct current, and may be processed to transform power or limit received power to particular characteristics. For example, the power can be transformed to or from direct current, and constrained to one or more values of average power, effective power, peak power, energy per pulse, voltage, current (e.g., measured in amperes), or any other characteristic of received power. Power supply 108 can be operative to request or provide particular amounts of power at different times, for example, based on the needs or requirements of electronic device 100 or periphery devices that may be coupled to electronic device 100 (e.g., to request more power when charging a battery than when the battery is already charged).
One or more input components 110 may be provided to permit a user to interact or interface with device 100. For example, input component 110 can take a variety of forms, including, but not limited to, a touch pad, dial, click wheel, scroll wheel, touch screen, one or more buttons (e.g., a keyboard), mouse, joy stick, track ball, microphone, camera, scanner (e.g., a bar code scanner or any other suitable scanner that may obtain product identifying information from a code, such as a bar code, a QR code, or the like), proximity sensor, light detector, motion sensor, biometric sensor (e.g., a fingerprint reader or other feature recognition sensor, which may operate in conjunction with a feature-processing application that may be accessible to electronic device 100 for authenticating a user), and combinations thereof. Each input component 110 can be configured to provide one or more dedicated control functions for making selections or issuing commands associated with operating device 100.
Electronic device 100 may also include one or more output components 112 that may present information (e.g., graphical, audible, and/or tactile information) to a user of device 100. For example, output component 112 of electronic device 100 may take various forms, including, but not limited to, audio speakers, headphones, audio line-outs, visual displays, antennas, infrared ports, haptic output components (e.g., rumblers, vibrators, etc.), or combinations thereof.
As a specific example, electronic device 100 may include a display output component as output component 112. Such a display output component may include any suitable type of display or interface for presenting visual data to a user. A display output component may include a display embedded in device 100 or coupled to device 100 (e.g., a removable display). A display output component may include, for example, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light-emitting diode (“OLED”) display, a surface-conduction electron-emitter display (“SED”), a carbon nanotube display, a nanocrystal display, any other suitable type of display, or combination thereof. Alternatively, a display output component can include a movable display or a projecting system for providing a display of content on a surface remote from electronic device 100, such as, for example, a video projector, a head-up display, or a three-dimensional (e.g., holographic) display. As another example, a display output component may include a digital or mechanical viewfinder, such as a viewfinder of the type found in compact digital cameras, reflex cameras, or any other suitable still or video camera. A display output component may include display driver circuitry, circuitry for driving display drivers, or both, and such a display output component can be operative to display content (e.g., media playback information, application screens for applications implemented on electronic device 100, information regarding ongoing communications operations, information regarding incoming communications requests, device operation screens, etc.) that may be under the direction of processor 102.
It should be noted that one or more input components and one or more output components may sometimes be referred to collectively herein as an input/output (“I/O”) component or I/O interface (e.g., input component 110 and output component 112 as I/O component or I/O interface 114). For example, input component 110 and output component 112 may sometimes be a single I/O component 114, such as a touch screen, that may receive input information through a user's touch of a display screen and that may also provide visual information to a user via that same display screen.
Processor 102 of electronic device 100 may include any processing circuitry that may be operative to control the operations and performance of one or more components of electronic device 100. For example, processor 102 may receive input signals from input component 110 and/or drive output signals through output component 112. As shown in
Electronic device 100 may also include near field communication (“NFC”) component 120. NFC component 120 may be any suitable proximity-based communication mechanism that may enable contactless proximity-based transactions or communications 15 between electronic device 100 and merchant subsystem 200 (e.g., a merchant payment terminal). NFC component 120 may allow for close range communication at relatively low data rates (e.g., 424 kbps), and may comply with any suitable standards, such as ISO/IEC 7816, ISO/IEC 18092, ECMA-340, ISO/IEC 21481, ECMA-352, ISO 14443, and/or ISO 15693. Alternatively or additionally, NFC component 120 may allow for close range communication at relatively high data rates (e.g., 370 Mbps), and may comply with any suitable standards, such as the TransferJet™ protocol. Communication between NFC component 120 and merchant subsystem 200 may occur within any suitable close range distance between device 100 and merchant subsystem 200 (see, e.g., distance D of
NFC component 120 may include any suitable modules for enabling contactless proximity-based communication 15 between electronic device 100 and merchant subsystem 200. As shown in
NFC device module 130 may include an NFC data module 132, an NFC antenna 134, and an NFC booster 136. NFC data module 132 may be configured to contain, route, or otherwise provide any suitable data that may be transmitted by NFC component 120 to merchant subsystem 200 as part of a contactless proximity-based or NFC communication 15. Additionally or alternatively, NFC data module 132 may be configured to contain, route, or otherwise receive any suitable data that may be received by NFC component 120 from merchant subsystem 200 as part of a contactless proximity-based communication 15.
NFC transceiver or NFC antenna 134 may be any suitable antenna or other suitable transceiver circuitry that may generally enable communication of communication 15 from NFC data module 132 to merchant subsystem 200 and/or to NFC data module 132 from subsystem 200. Therefore, NFC antenna 134 (e.g., a loop antenna) may be provided specifically for enabling the contactless proximity-based communication capabilities of NFC component 120.
Alternatively or additionally, NFC component 120 may utilize the same transceiver circuitry or antenna (e.g., antenna 116) that another communication component of electronic device 100 (e.g., communication component 106) may utilize. For example, communication component 106 may leverage antenna 116 to enable Wi-Fi, Bluetooth™, cellular, or GPS communication between electronic device 100 and another remote entity, while NFC component 120 may leverage antenna 116 to enable contactless proximity-based or NFC communication 15 between NFC data module 132 of NFC device module 130 and another entity (e.g., merchant subsystem 200). In such embodiments, NFC device module 130 may include NFC booster 136, which may be configured to provide appropriate signal amplification for data of NFC component 120 (e.g., data within NFC data module 132) so that such data may be appropriately transmitted by shared antenna 116 as communication 15 to subsystem 200. For example, shared antenna 116 may require amplification from booster 136 before antenna 116 (e.g., a non-loop antenna) may be properly enabled for communicating contactless proximity-based or NFC communication 15 between electronic device 100 and merchant subsystem 200 (e.g., more power may be needed to transmit NFC data using antenna 116 than may be needed to transmit other types of data using antenna 116).
NFC controller module 140 may include at least one NFC processor module 142. NFC processor module 142 may operate in conjunction with NFC device module 130 to enable, activate, allow, and/or otherwise control NFC component 120 for communicating NFC communication 15 between electronic device 100 and merchant subsystem 200. NFC processor module 142 may exist as a separate component, may be integrated into another chipset, or may be integrated with processor 102, for example, as part of a system on a chip (“SoC”). As shown in
NFC controller module 140 may control the near field communication mode of NFC component 120. For example, NFC processor module 142 may be configured to switch NFC device module 130 between a reader/writer mode for reading information (e.g., communication 15) from NFC tags (e.g., from merchant subsystem 200) to NFC data module 132, a peer-to-peer mode for exchanging data (e.g., communication 15) with another NFC enabled device (e.g., merchant subsystem 200), and a card emulation mode for allowing another NFC enabled device (e.g., merchant subsystem 200) to read information (e.g., communication 15) from NFC data module 132. NFC controller module 140 also may be configured to switch NFC component 120 between active and passive modes. For example, NFC processor module 142 may be configured to switch NFC device module 130 (e.g., in conjunction with NFC antenna 134 or shared antenna 116) between an active mode where NFC device module 130 may generate its own RF field and a passive mode where NFC device module 130 may use load modulation to transfer data to another device generating an RF field (e.g., merchant subsystem 200). Operation in such a passive mode may prolong the battery life of electronic device 100 compared to operation in such an active mode. The modes of NFC device module 130 may be controlled based on preferences of a user and/or based on preferences of a manufacturer of device 100, which may be defined or otherwise dictated by an application running on device 100 (e.g., application 103 and/or application 143).
NFC memory module 150 may operate in conjunction with NFC device module 130 and/or NFC controller module 140 to allow for NFC communication 15 between electronic device 100 and merchant subsystem 200. NFC memory module 150 may be embedded within NFC device hardware or within an NFC integrated circuit (“IC”). NFC memory module 150 may be tamper resistant and may provide at least a portion of a secure element. For example, NFC memory module 150 may store one or more applications relating to NFC communications (e.g., application 143) that may be accessed by NFC controller module 140. For example, such applications may include financial payment applications, secure access system applications, loyalty card applications, and other applications, which may be encrypted. In some embodiments, NFC controller module 140 and NFC memory module 150 may independently or in combination provide a dedicated microprocessor system that may contain an operating system, memory, application environment, and security protocols intended to be used to store and execute sensitive applications on electronic device 100. NFC controller module 140 and NFC memory module 150 may independently or in combination provide at least a portion of a secure element, which may be tamper resistant. For example, such a secure element may be configured to provide a tamper-resistant platform (e.g., as a single or multiple chip secure microcontroller) that may be capable of securely hosting applications and their confidential and cryptographic data (e.g., applet 153 and key 155) in accordance with rules and security requirements that may be set forth by a set of well-identified trusted authorities (e.g., an authority of financial institution subsystem and/or an industry standard, such as GlobalPlatform). NFC memory module 150 may be a portion of memory 106 or at least one dedicated chip specific to NFC component 120. NFC memory module 150 may reside on a SIM, a dedicated chip on a motherboard of electronic device 100, or as an external plug in memory card. NFC memory module 150 may be completely independent from NFC controller module 140 and may be provided by different components of device 100 and/or provided to electronic device 100 by different removable subsystems.
NFC memory module 150 may include one or more of an issuer security domain (“ISD”) 152 and a supplemental security domain (“SSD”) 154 (e.g., a service provider security domain (“SPSD”), a trusted service manager security domain (“TSMSD”), etc.), which may be defined and managed by an NFC specification standard (e.g., GlobalPlatform). For example, ISD 152 may be a portion of NFC memory module 150 in which a trusted service manager (“TSM”) or issuing financial institution may store keys and/or other suitable information for creating or otherwise provisioning one or more credentials (e.g., credentials associated with various credit cards, bank cards, gift cards, access cards, transit passes, digital currency (e.g., bitcoin and associated payment networks), etc.) on electronic device 100 (e.g., via communications component 106), for credential content management, and/or security domain management. A specific supplemental security domain (“SSD”) 154 (e.g., one of SSDs 154-154b) may be associated with a specific credential (e.g., a specific credit card credential or a specific public transit card credential) that may provide specific privileges or payment rights to electronic device 100. Each SSD 154 may have its own manager key 155 for its own application or applet 153 that may need to be activated to enable a specific credential of that SSD 154 for use by NFC device module 130 as an NFC communication 15 between electronic device 100 and merchant subsystem 200. For example, a particular SSD 154 may be associated with a particular credit card credential. However, that particular credential may only be communicated as an NFC communication 15 to merchant subsystem 200 by NFC component 120 (e.g., that particular credential may only be accessible by NFC data module 132) when a particular applet 153 of that particular SSD 154 has been enabled or otherwise activated or unlocked for such use. Security features may be provided for enabling use of NFC component 120 that may be particularly useful when transmitting confidential payment information, such as credit card information or bank account information of a credential, from electronic device 100 to merchant subsystem 200 as NFC communication 15. Such security features also may include a secure storage area that may have restricted access. For example, user authentication via personal identification number (“PIN”) entry or via user interaction with a biometric sensor may need to be provided to access the secure storage area. In certain embodiments, some or all of the security features may be stored within NFC memory module 150. Further, security information, such as an authentication key, for communicating with subsystem 200 may be stored within NFC memory module 150. In certain embodiments, NFC memory module 150 may include a microcontroller embedded within electronic device 100.
While NFC component 120 has been described with respect to near field communication, it is to be understood that component 120 may be configured to provide any suitable contactless proximity-based mobile payment or any other suitable type of contactless proximity-based communication 15 between electronic device 100 and merchant subsystem 200. For example, NFC component 120 may be configured to provide any suitable short-range communication, such as those involving electromagnetic/electrostatic coupling technologies.
Electronic device 100 may also be provided with a housing 101 that may at least partially enclose one or more of the components of device 100 for protection from debris and other degrading forces external to device 100. In some embodiments, one or more of the components may be provided within its own housing (e.g., input component 110 may be an independent keyboard or mouse within its own housing that may wirelessly or through a wire communicate with processor 102, which may be provided within its own housing).
As mentioned, and as shown in
An output component 112a may be a display that can be used to display a visual or graphic user interface (“GUI”) 180, which may allow a user to interact with electronic device 100. GUI 180 may include various layers, windows, screens, templates, elements, menus, and/or other components of a currently running application (e.g., application 103 and/or application 143) that may be displayed in all or some of the areas of display output component 112a. For example, as shown in
Icons 182 may represent various layers, windows, screens, templates, elements, and/or other components that may be displayed in some or all of the areas of display component 112a upon selection by the user. Furthermore, selection of a specific icon 182 may lead to a hierarchical navigation process. For example, selection of a specific icon 182 may lead to a new screen of GUI 180 that may include one or more additional icons or other GUI elements of the same application or of a new application associated with that icon 182. Textual indicators 181 may be displayed on or near each icon 182 to facilitate user interpretation of each graphical element icon 182. It is to be appreciated that GUI 180 may include various components arranged in hierarchical and/or non-hierarchical structures. When a specific icon 182 is selected, device 100 may be configured to open a new application associated with that icon 182 and display a corresponding screen of GUI 180 associated with that application. For example, when the specific icon 182 labeled with a “Setup Assistant” textual indicator 181 (i.e., specific icon 183) is selected, device 100 may launch or otherwise access a specific setup application and may display screens of a specific user interface that may include one or more tools or features for interacting with device 100 in a specific manner. For each application, screens may be displayed on display output component 112a and may include various user interface elements. Additionally or alternatively, for each application, various other types of non-visual information may be provided to a user via various other output components 112 of device 100. The operations described with respect to various GUIs 180 may be achieved with a wide variety of graphical elements and visual schemes. Therefore, the described embodiments are not intended to be limited to the precise user interface conventions adopted herein. Rather, embodiments may include a wide variety of user interface styles.
Electronic device 100 also may include various other I/O components 114 that may allow for communication between device 100 and other devices. I/O component 114b may be a connection port that may be configured for transmitting and receiving data files, such as media files or customer order files, from a remote data source and/or power from an external power source. For example, I/O component 114b may be a proprietary port, such as a Lightning™ connector or a 30-pin dock connector from Apple Inc. of Cupertino, Calif. I/O component 114c may be a connection slot for receiving a SIM card or any other type of removable component. I/O component 114d may be a headphone jack for connecting audio headphones that may or may not include a microphone component. Electronic device 100 may also include at least one audio input component 110g, such as a microphone, and at least one audio output component 112b, such as an audio speaker.
Electronic device 100 may also include at least one haptic or tactile output component 112c (e.g., a rumbler), a camera and/or scanner input component 110h (e.g., a video or still camera, and/or a bar code scanner or any other suitable scanner that may obtain product identifying information from a code, such as a bar code, a QR code, or the like), and a biometric input component 110i (e.g., a fingerprint reader or other feature recognition sensor, which may operate in conjunction with a feature-processing application that may be accessible to electronic device 100 for authenticating a user). As shown in
Moreover, one, some, or all of the processes described with respect to
It is to be understood that any, each, or at least one module or component or subsystem of system 1 may be provided as a software construct, firmware construct, one or more hardware components, or a combination thereof. For example, any, each, or at least one module or component or subsystem of system 1 may be described in the general context of computer-executable instructions, such as program modules, that may be executed by one or more computers or other devices. Generally, a program module may include one or more routines, programs, objects, components, and/or data structures that may perform one or more particular tasks or that may implement one or more particular abstract data types. It is also to be understood that the number, configuration, functionality, and interconnection of the modules and components and subsystems of system 1 are merely illustrative, and that the number, configuration, functionality, and interconnection of existing modules, components, and/or subsystems may be modified or omitted, additional modules, components, and/or subsystems may be added, and the interconnection of certain modules, components, and/or subsystems may be altered.
At least a portion of one or more of the modules or components or subsystems of system 1 may be stored in or otherwise accessible to an entity of system 1 in any suitable manner (e.g., in memory 104 of device 100 (e.g., as at least a portion of application 103 and/or as at least a portion of application 113 and/or as at least a portion of application 143)). For example, any or each module of NFC component 120 may be implemented using any suitable technologies (e.g., as one or more integrated circuit devices), and different modules may or may not be identical in structure, capabilities, and operation. Any or all of the modules or other components of system 1 may be mounted on an expansion card, mounted directly on a system motherboard, or integrated into a system chipset component (e.g., into a “north bridge” chip).
Any or each module or component of system 1 (e.g., any or each module of NFC component 120) may be a dedicated system implemented using one or more expansion cards adapted for various bus standards. For example, all of the modules may be mounted on different interconnected expansion cards or all of the modules may be mounted on one expansion card. With respect to NFC component 120, by way of example only, the modules of NFC component 120 may interface with a motherboard or processor 102 of device 100 through an expansion slot (e.g., a peripheral component interconnect (′PCI″) slot or a PCI express slot). Alternatively, NFC component 120 need not be removable but may include one or more dedicated modules that may include memory (e.g., RAM) dedicated to the utilization of the module. In other embodiments, NFC component 120 may be integrated into device 100. For example, a module of NFC component 120 may utilize a portion of device memory 104 of device 100. Any or each module or component of system 1 (e.g., any or each module of NFC component 120) may include its own processing circuitry and/or memory. Alternatively, any or each module or component of system 1 (e.g., any or each module of NFC component 120) may share processing circuitry and/or memory with any other module of NFC component 120 and/or processor 102 and/or memory 104 of device 100.
As mentioned, an input component 110 of device 100 (e.g., input component 1100 may include a touch input component that can receive touch input for interacting with other components of device 100 via wired or wireless bus 118. Such a touch input component 110 may be used to provide user input to device 100 in lieu of or in combination with other input components, such as a keyboard, mouse, and the like.
A touch input component 110 may include a touch sensitive panel, which may be wholly or partially transparent, semitransparent, non-transparent, opaque, or any combination thereof. A touch input component 110 may be embodied as a touch screen, touch pad, a touch screen functioning as a touch pad (e.g., a touch screen replacing the touchpad of a laptop), a touch screen or touch pad combined or incorporated with any other input device (e.g., a touch screen or touch pad disposed on a keyboard), or any multi-dimensional object having a touch sensitive surface for receiving touch input. In some embodiments, the terms touch screen and touch pad may be used interchangeably.
In some embodiments, a touch input component 110 embodied as a touch screen may include a transparent and/or semitransparent touch sensitive panel partially or wholly positioned over, under, and/or within at least a portion of a display (e.g., display output component 112a). In other embodiments, a touch input component 110 may be embodied as an integrated touch screen where touch sensitive components/devices are integral with display components/devices. In still other embodiments, a touch input component 110 may be used as a supplemental or additional display screen for displaying supplemental or the same graphical data as a primary display and to receive touch input.
A touch input component 110 may be configured to detect the location of one or more touches or near touches based on capacitive, resistive, optical, acoustic, inductive, mechanical, chemical measurements, or any phenomena that can be measured with respect to the occurrences of the one or more touches or near touches in proximity to input component 110. Software, hardware, firmware, or any combination thereof may be used to process the measurements of the detected touches to identify and track one or more gestures. A gesture may correspond to stationary or non-stationary, single or multiple, touches or near touches on a touch input component 110. A gesture may be performed by moving one or more fingers or other objects in a particular manner on touch input component 110, such as by tapping, pressing, rocking, scrubbing, rotating, twisting, changing orientation, pressing with varying pressure, and the like at essentially the same time, contiguously, or consecutively. A gesture may be characterized by, but is not limited to, a pinching, pulling, sliding, swiping, rotating, flexing, dragging, or tapping motion between or with any other finger or fingers. A single gesture may be performed with one or more hands, by one or more users, or any combination thereof.
As mentioned, electronic device 100 may drive a display (e.g., display output component 112a) with graphical data to display a graphical user interface (“GUI”) 180. GUI 180 may be configured to receive touch input via a touch input component 110f. Embodied as a touch screen (e.g., with display output component 112a as I/O component 114a), touch I/O component 110f may display GUI 180. Alternatively, GUI 180 may be displayed on a display (e.g., display output component 112a) separate from touch input component 110f. GUI 180 may include graphical elements displayed at particular locations within the interface. Graphical elements may include, but are not limited to, a variety of displayed virtual input devices, including virtual scroll wheels, a virtual keyboard, virtual knobs, virtual buttons, any virtual user interface (“UI”), and the like. A user may perform gestures at one or more particular locations on touch input component 110f, which may be associated with the graphical elements of GUI 180. In other embodiments, the user may perform gestures at one or more locations that are independent of the locations of graphical elements of GUI 180. Gestures performed on a touch input component 110 may directly or indirectly manipulate, control, modify, move, actuate, initiate, or generally affect graphical elements, such as cursors, icons, media files, lists, text, all or portions of images, or the like within the GUI. For instance, in the case of a touch screen, a user may directly interact with a graphical element by performing a gesture over the graphical element on the touch screen. Alternatively, a touch pad may generally provide indirect interaction. Gestures may also affect non-displayed GUI elements (e.g., causing user interfaces to appear) or may affect other actions of device 100 (e.g., affect a state or mode of a GUI, application, or operating system). Gestures may or may not be performed on a touch input component 110 in conjunction with a displayed cursor. For instance, in the case in which gestures are performed on a touchpad, a cursor or pointer may be displayed on a display screen or touch screen and the cursor or pointer may be controlled via touch input on the touchpad to interact with graphical objects on the display screen. In other embodiments, in which gestures are performed directly on a touch screen, a user may interact directly with objects on the touch screen, with or without a cursor or pointer being displayed on the touch screen. Feedback may be provided to the user via bus 118 in response to or based on the touch or near touches on a touch input component 110. Feedback may be transmitted optically, mechanically, electrically, olfactory, acoustically, or the like or any combination thereof and in a variable or non-variable manner.
While there have been described systems, methods, and computer-readable media for securely provisioning and/or authenticating credentials on an electronic device, it is to be understood that many changes may be made therein without departing from the spirit and scope of the subject matter described herein in any way. Insubstantial changes from the claimed subject matter as viewed by a person with ordinary skill in the art, now known or later devised, are expressly contemplated as being equivalently within the scope of the claims. Therefore, obvious substitutions now or later known to one with ordinary skill in the art are defined to be within the scope of the defined elements.
Therefore, those skilled in the art will appreciate that the invention can be practiced by other than the described embodiments, which are presented for purposes of illustration rather than of limitation.
This application claims the benefit of prior filed U.S. Provisional Patent Application No. 61/912,727, filed Dec. 6, 2013, which is hereby incorporated by reference herein in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 61912727 | Dec 2013 | US |
