Configuring applications on device using contactless card

Abstract

Systems, methods, apparatus, and computer-readable media for configuring applications on a device using a contactless card are disclosed. An application executing on a device may receive a password from a contactless card associated with an account. The application may communicate the password to the server. The application may receive configuration information for a plurality of applications associated with the account based on the password. The application may modify a respective configuration of each application on the device based on the configuration information.

Description

[0001] Related Applications

[0002] This application claims priority to U.S. Patent Application Serial No. 17 / 664,460, entitled “CONFIGURING APPLICATIONS ON A DEVICE USING A CONTACTLESS CARD,” filed on May 23, 2022. The contents of the above application are incorporated herein by reference in their entirety. Background Art

[0003] Configuring a new or additional device can be tedious, time-consuming, and error-prone. For example, a user may purchase a new device to replace another device. However, the new device does not include the applications and / or configurations from the other device. Traditional solutions for configuring devices are error-prone, present security risks, and are vulnerable to malicious attacks. Summary of the invention

[0004] Systems, methods, apparatus, and computer-readable media for configuring applications on a device using a contactless card. In one aspect, a method includes receiving, by an application executing on a device, a password from a contactless card associated with an account, transmitting, by the application, the password to a server, receiving, by the application, configuration information for a plurality of applications associated with the account based on the password, and modifying a corresponding configuration of each application on the device based on the configuration information. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To facilitate identification of the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which the element is first introduced.

[0006] Figure 1A An aspect of the subject matter according to one embodiment is shown.

[0007] Figure 1B An aspect of the subject matter according to one embodiment is shown.

[0008] Figure 1C An aspect of the subject matter according to one embodiment is shown.

[0009] Figure 1D An aspect of the subject matter according to one embodiment is shown.

[0010] Figure 2A An aspect of the subject matter according to one embodiment is shown.

[0011] Figure 2B An aspect of the subject matter according to one embodiment is shown.

[0012] Figure 2CAn aspect of the subject matter according to one embodiment is shown.

[0013] Figure 2D An aspect of the subject matter according to one embodiment is shown.

[0014] Figure 3 A routine 300 is shown according to one embodiment.

[0015] Figure 4 A routine 400 is shown according to one embodiment.

[0016] Figure 5 Routine 500 is shown according to one embodiment.

[0017] Fig. 6A A contactless card 104 is shown according to one embodiment.

[0018] Figure 6B A contactless card 104 is shown according to one embodiment.

[0019] Figure 7 A data structure 700 is shown according to one embodiment.

[0020] Figure 8 A computer architecture 800 is shown according to one embodiment. DETAILED DESCRIPTION

[0021] Embodiments disclosed herein provide security techniques for automatically configuring a device (such as a smartphone, tablet computer, or any other computing device) using a contactless card. Examples of configuring a device may include installing an application on the device, uninstalling an application from the device, and / or configuring an application on the device (e.g., modifying application settings, application parameters, etc.). Initially, a user may register one or more applications and / or configuration information for one or more applications. Doing so may include storing information for a given device and / or account in an account database. Registration may associate an application and / or configuration information with a contactless card.

[0022] The user may then tap the contactless card to any device, which may include a previously registered device, a new device, an existing device, etc. In some embodiments, tapping the card to the device may cause the card to generate a password. In some embodiments, the password is a parameter of a uniform resource locator (URL). When the device receives the URL and / or password, the device may launch an application that may transmit the password to a server for verification. The server may verify the password based at least in part on the decrypted password.

[0023] In other embodiments, tapping the card to the device may cause the device to launch a web browser based on the URL. In these embodiments, the web browser may access a page associated with the URL. The server may identify the password as a parameter of the URL accessed by the web browser. The server may verify the password based at least in part on the decrypted password.

[0024] Regardless of the application launched in response to tapping the card to the device, after verifying the password, the server can use the password (and / or parameters of the password) to identify the relevant application and / or configuration information of the application in the account database. The server can then transmit the configuration information to the requesting device. In some embodiments, the server sends the configuration information to the device via one or more push notifications. In some embodiments, such as when the size of the configuration information exceeds a threshold size, the server can send one or more tokens to the device. The device can then use the token to request the configuration information from the server.

[0025] Once received, the device may apply the received configuration information to each application. For example, the configuration information may include account login credentials, server information for establishing a connection with one or more servers, user preferences, settings, etc. In some embodiments, the configuration information may include information about one or more applications that are not installed on the device. In such an embodiment, these applications may be downloaded and installed on the device based on the receipt of the configuration information. Similarly, the configuration information may include information for disabling or uninstalling existing applications. In such an embodiment, the device may disable and / or uninstall these applications based on the configuration information. In addition, the device may prevent certain applications from being enabled and / or reinstalled on the device based on the configuration information.

[0026] Advantageously, embodiments disclosed herein provide a secure technique for automatically configuring a device using a contactless card. By requiring password authentication to initiate configuration, the security of user accounts, applications, devices, and data can be improved. In addition, this can ensure that automatic device configuration is performed only when the user has access to a contactless card, which facilitates password authentication with a server. Furthermore, by providing the disclosed automatic configuration functionality, many different applications, operating systems, and / or devices can be automatically configured without the need to be integrated into each application, operating system, and / or device.

[0027] The detailed description herein can be presented in terms of program processes executed on a computer or computer network with general reference to the symbols and terms used herein. These process descriptions and representations are used by those skilled in the art to effectively convey the substance of their work to others skilled in the art.

[0028] A process is here generally conceived to be a self-consistent sequence of operations leading to a desired result. These operations require physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical, magnetic, or optical signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It proves convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be noted, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.

[0029] In addition, the operations performed are often referred to in terms such as adding or comparing, which are often associated with mental operations performed by a human operator. In any of the operations described herein that form part of one or more embodiments, such capabilities of a human operator are not required or in most cases are not required. Instead, these operations are machine operations. Useful machines for performing the operations of the various embodiments include digital computers or similar devices.

[0030] Some embodiments may be described using the terms "coupled" and "connected" and their derivatives. These terms are not necessarily synonymous with each other. For example, some embodiments may be described using the terms "connected" and / or "coupled" to indicate that two or more elements are in direct physical or electrical contact with each other. However, the term "coupled" may also mean that two or more elements are not in direct contact with each other, but still cooperate or interact with each other.

[0031] Various embodiments also relate to apparatus or systems for performing these operations. The apparatus may be specially constructed for the desired purpose, or it may include a computer selectively activated or reconfigured by a computer program stored in the computer. The processes presented herein have no inherent relationship to a particular computer or other apparatus. Various machines may be used with programs written in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the desired method steps. The required structure of various such machines will be apparent from the description given.

[0032] Reference is now made to the accompanying drawings, in which the same reference numerals are used throughout to refer to the same elements. In the following description, for the purpose of explanation, many specific details are set forth in order to provide a thorough understanding thereof. However, novel embodiments may be practiced without these specific details. In other cases, structures and devices are shown in block diagram form to facilitate description thereof. The purpose is to cover all modifications, equivalents, and alternatives consistent with the claimed subject matter.

[0033] In the drawings and the accompanying description, the reference numerals "a", "b", and "c" (and similar reference numerals) are variables representing any positive integer. Thus, for example, if one embodiment sets a value for a=5, then a complete set of components 123, shown as components 123-1 to 123-a (or 123a), may include components 123-1, 123-2, 123-3, 123-4, and 123-5. In this context, the embodiments are not limited.

[0034] Figure 1A An exemplary computing architecture 100, also referred to as a system, consistent with the disclosed embodiments is depicted. Figure 1A-Figure 1C The computing architecture 100 shown in FIG. 1 has a limited number of elements in a particular topology, but it will be appreciated that the computing architecture 100 may include more or fewer elements in alternative topologies as desired for a given implementation.

[0035] The computing architecture 100 includes one or more computing devices 102, one or more servers 106, and one or more contactless cards 104. The contactless card 104 represents any type of card, such as a credit card, a debit card, an ATM card, a gift card, a payment card, a smart card, etc. The contactless card 104 may include one or more communication interfaces 124, such as a radio frequency identification (RFID) chip, which is configured to communicate with the communication interface 124 (also referred to herein as a "card reader", "wireless card reader" and / or "wireless communication interface") of the computing device 102 via NFC, the EMV standard, or other short-range protocols in wireless communication. Although NFC is used as an example communication protocol herein, the present disclosure is equally applicable to other types of wireless communications, such as the EMV standard, Bluetooth, and / or Wi-Fi.

[0036] The computing device 102 represents any number and type of computing devices, such as a smartphone, a tablet computer, a wearable device, a laptop computer, a portable gaming device, a virtualized computing system, a merchant terminal, a point of sale system, a server, a desktop computer, etc. A mobile device can be used as an example of the computing device 102, but should not be considered as a limitation of the present disclosure. The server 106 represents any type of computing device, such as a server, a workstation, a computing cluster, a cloud computing platform, a virtualized computing system, etc. Although not shown for clarity, the computing device 102, the contactless card 104, and the server 106 each include one or more processor circuits, for example, for executing programs, codes, and / or instructions.

[0037] As shown, the memory 108 of the contactless card 104 includes an applet 110, a counter 116, one or more master keys 114, one or more diversified keys 120, a unique ID 112, a primary account number (PAN) sequence number 144, and one or more unique derived keys (UDK) 118. The unique ID 112 can be any identifier that uniquely identifies the contactless card 104 relative to other contactless cards 104. The PAN sequence 144 can include a counter value stored by the contactless card 104. The applet 110 is an executable code configured to perform some or all of the operations described herein. The counter 116 is a value synchronized between the contactless card 104 and the server 106. The counter 116 can include a number that changes each time data is exchanged between the contactless card 104 and the server 106 (and / or the contactless card 104 and the computing device 102). The counter 116, the master key 114, the diversified key 120, the UDK 118, the PAN sequence 144, and / or the unique ID 112 are used to provide security in the system 100, as described in more detail below.

[0038] As shown, the memory 132 of the computing device 102 includes an instance of an operating system 134. Example operating systems include and Operating system. As shown, the operating system 134 includes an account application 136 and one or more other applications 146. The account application 136 allows a user to perform various operations, such as configuring the device 102 based on the configuration information 148 stored by the server 106. In some embodiments, the account application 136 can also perform other account-related operations, such as activating a payment card, viewing an account balance, purchasing items, processing payments, etc. In some embodiments, a user can authenticate using an authentication certificate to access certain features of the account application 136. For example, the authentication certificate can include a username (or login) and password, a biometric certificate (e.g., fingerprint, face ID, etc.), etc. The other applications 146 represent any type of application, such as a web browser, an email client, a messaging client, a social media application, etc.

[0039] As shown, the memory 126 of the server 106 includes an authentication application 138 and an account database 128. The account database 128 generally includes information related to an account holder (e.g., one or more users), one or more accounts of the account holder, and one or more contactless cards 104 of the account. For example, as shown, the account database 128 may include configuration information 148 for multiple accounts. The configuration information 148 may include any data for configuring the computing device 102, the operating system 134, the account application 136, other applications 146, and / or any component thereof. For example, the configuration information 148 may include information for connecting to one or more servers (e.g., Internet Protocol (IP) addresses, ports, etc.), account information (e.g., login / password), inbox contents (e.g., messages, emails, etc.), preferences, variable values, and / or settings. The configuration information 148 may also include executable files, scripts, etc., to install and / or configure one or more parts of the configuration information 148 on a given computing device 102. In this context, the embodiments are not limited as configuration information 148 may be used to modify any property and / or characteristic of computing device 102 and / or any software component thereof.

[0040] As described above, configuration information 148 may be used to automatically configure computing device 102. In other words, configuration information 148 may represent a "backup" of at least a portion of a given device and / or account (including any applications, operating systems, and / or parameters thereof) so that any device may be restored to a state similar to the backup. For example, when a user purchases a new smartphone, configuration information 148 from a previous smartphone may be used to automatically configure the new smartphone. For example, configuration information 148 may be used to install applications on the new smartphone (e.g., applications that were not included with the smartphone at the time of purchase, but were installed on the previous smartphone and registered as part of configuration information 148), remove applications from the new smartphone that were not installed on the previous smartphone (and / or remove restricted applications based on configuration information 148), apply settings and / or parameters of the old smartphone to the new smartphone, and the like.

[0041] In various embodiments, a user may initially register configuration information 148 with the server 106. For example, a user may access a function of the account application 136, access a web page, or any other resource to register configuration information 148 for any device and / or account. Configuration information 148 may be specific to all devices associated with an account and / or a subset of devices associated with an account. Additionally and / or alternatively, configuration information 148 may be specific to all applications associated with an account and / or a subset of applications associated with an account. In some embodiments, the account application 136 may collect information describing the computing device 102, such as installed applications, configuration files, etc., which may be stored as configuration information 148. In other embodiments, a user may provide input that specifies different applications, settings, functions, etc. for a given device. In some embodiments, the configuration information 148 includes a package name for each application to be registered, metadata describing the operating system 134 to be registered (e.g., device identifier, device version, preferences, settings, etc.), metadata describing each application to be registered, preferences, login information, application identification, or any other attributes of the device, application, operating system 134, and / or its components. Additionally, configuration information 148 may be associated with an account in account database 128, which allows server 106 to further associate configuration information 148 with one or more contactless cards 104 associated with the account.

[0042] For example, a user may register a social media application and an email client with the server 106. Thus, the user's configuration information 148 may include the respective package names of the social media application and the email client, connection information for the media application and the email client to connect to the respective servers, user identifications of the social media application and the email application, email inboxes (or folders) of the email client, social media profiles in the social media application, social media messages in the social media application, respective versions of the social media application and the email client, display settings (e.g., enabling dark mode in either application), enabling push notifications in either application, permissions for each application in the operating system 134, etc. In this context, the embodiments are not limited. Thus, an indication of this information may be stored as the configuration information 148 of the account.

[0043] Thereafter, the user may wish to configure computing device 102 using configuration information 148. For example, computing device 102 may be a new smartphone, and the user may wish to configure a social media application and an email client (e.g., to restore all emails in the email client, load their social media profile / settings in the social media application, etc.). In some embodiments, these applications may not be installed on the new smartphone, so configuration information 148 may also be used to download the social media application and / or email client to install on computing device 102. To initiate configuration of the device based on configuration information 148, the user may tap contactless card 104 onto computing device 102.

[0044] exist Figure 1A In the illustrated embodiment, a user may tap the contactless card 104 to the computing device 102 (or otherwise place the contactless card 104 within communication range of the communication interface 124 of the device 102). The applet 110 may then generate a password 122. The password 122 may be generated based on any suitable cryptographic technique. In some embodiments, the password 122 may be based on the unique ID 112 of the contactless card 104. In some embodiments, the applet 110 may include the password 122 and an unencrypted identifier (e.g., the counter 116, the PAN sequence 144, the unique ID 112, and / or any other unique identifier) ​​as part of a data packet that includes the password 122. In at least one embodiment, the data packet is an NDEF file.

[0045] As described above, the computing architecture 100 is configured to implement key diversification to protect data, which may be referred to herein as a key diversification technique. Typically, the server 106 (or another computing device) and the contactless card 104 may be equipped with the same master key 114 (also referred to as a master symmetric key). More specifically, each contactless card 104 is programmed with a different master key 114 that has a corresponding pair in a hardware security module (HSM) 130 of the server 106. For example, when the contactless card 104 is manufactured, a unique master key 114 may be programmed into the memory 108 of the contactless card 104. Similarly, the unique master key 114 may be stored in a record 142 in the HSM 130.

[0046] In addition, when a given card 104 is manufactured, the UDK 118 can be diversified from the master key 114 via an HSM function that takes as input a diversification factor and a reference to an index of the master key 114 in the HSM 130 (e.g., an index to the record 142). In some embodiments, the diversification factor can be the unique ID 112 and / or the PAN sequence 144 of the contactless card 104. The UDK 118 can be stored in the record 142 of the contactless card 104 and the HSM 130. The master key 114 and the UDK 118 can be kept secret from all parties other than the contactless card 104 and the server 106, thereby enhancing the security of the system 100. Although depicted as being stored in the record 142, in some embodiments, the counter 116 and / or the PAN sequence 144 are not stored in the HSM 130. For example, the unique ID 112, the counter 116, and the PAN sequence 144 can be stored in the account database 128.

[0047] In some embodiments, to generate the password 122, the applet 110 may provide the UDK 118, the unique ID 112, and the diversification factor as inputs to a cryptographic algorithm, thereby generating a diversified key 120. In some embodiments, the diversification factor is the counter 116. In other embodiments, the PAN sequence 144 is the diversification factor. The diversified key 120 may then be used to encrypt some data, such as the diversification factor (e.g., the counter 116 and / or the PAN sequence 144) or other sensitive data. The applet 110 and the server 106 may be configured to encrypt the same type of data to facilitate the decryption and / or verification process of the password.

[0048] As described above, the UDK 118 of the contactless card 104 and the server 106 can be used in conjunction with the counter 116 to enhance security using key diversification. As described above, the counter 116 includes a value that is synchronized between the contactless card 104 and the server 106. The counter 116 can include a number that changes each time data is exchanged between the contactless card 104 and the server 106 (and / or the contactless card 104 and the computing device 102). When data is ready to be sent (e.g., to the server 106 and / or the device 102), the applet 110 of the contactless card 104 can increment the counter 116. The applet 110 of the contactless card 104 can then provide the UDK 118, the unique ID 112, and the counter 116 as inputs to a cryptographic algorithm that produces a diversified key 120 as output. The cryptographic algorithm can include an encryption algorithm, a hash-based message authentication code (HMAC) algorithm, a cipher-based message authentication code (CMAC) algorithm, and the like. Non-limiting examples of cryptographic algorithms may include symmetric encryption algorithms such as 3DES or AES107; symmetric HMAC algorithms such as HMAC-SHA-256; and symmetric CMAC algorithms such as AES-CMAC. Examples of key diversification techniques are described in more detail in U.S. patent application Ser. No. 16 / 205,119, filed Nov. 29, 2018. The entire contents of the above patent application are incorporated herein by reference. In some embodiments, the PAN sequence 144 is used as an input to the cryptographic algorithm instead of the counter 116 to generate the diversified key 120, for example, by encrypting the UDK 118, the unique ID 112, and the PAN sequence 144.

[0049] The applet 110 may then encrypt some data (e.g., unique ID 112, counter 116, PAN sequence 144, commands, and / or any other data) using the diversified key 120 and the data as input to a cryptographic algorithm. For example, encrypting the unique ID 112 using the diversified key 120 may result in an encrypted unique ID 112 (e.g., password 122). As described above, the applet 110 and the server 106 may be configured to encrypt the same data.

[0050] In some embodiments, two diversified keys 120 may be generated, for example, based on one or more portions of the input to a cryptographic function. In some embodiments, the two diversified keys 120 are generated based on two different master keys 114, two different UDKs 118, a unique ID 112, and a counter 116 (or a PAN sequence 144). In such an embodiment, a message authentication code (MAC) is generated using one of the diversified keys 120, and the MAC may be encrypted using another of the diversified keys 120. The MAC may be generated based on any suitable data input to the MAC algorithm, such as sensitive data, a unique ID 112, a counter 116, and / or a PAN sequence 144. More generally, the applet 110 and the server 106 may be configured to generate a MAC based on the same data. In some embodiments, the password 122 is included in a data packet such as an NDEF file. The account application 136 may then read the data packet including the password 122 via the communication interface 124 of the computing device 102.

[0051] In some embodiments, the applet includes the password 122 as a parameter of the URL. For example, the URL may be "http: / / www.example.com / appconfig?param=ABC123&custID=123". In such an example, the password 122 may correspond to the parameter "ABC123" and the unique ID 112 may correspond to the parameter "custID". Once received by the operating system 134, the operating system 134 may open the application to process the URL. In some embodiments, the URL may be registered with the account application 136, which causes the operating system 134 to launch the account application 136 and provide the URL 120 as input to the account application 136. However, in other examples, the operating system 134 may launch a web browser and provide the URL as input to the web browser. In other embodiments, the password 122 is not a parameter of the URL, but is transmitted in a data packet (such as an NDEF file) together with the URL. In such an embodiment, the operating system 134 may read the data packet including the URL and the password 122 via the communication interface 124 of the computing device 102.

[0052] exist Figure 1A In the example shown, the operating system 134 can launch the account application 136 based on reading the password 122. As described above, the password 122 can be a parameter of the URL. In such an example, the URL can be associated with the account application 136. Doing so causes the operating system 134 to launch the account application 136. The account application 136 can then extract the password 122 and transmit the password 122 to the server 106 for verification.

[0053] In embodiments where password 122 is not a parameter of the URL, operating system 134 can launch account application 136 based on reading password 122 and / or an NDEF file including password 122. Operating system 134 can provide password 122 to account application 136. Account application 136 can then extract password 122 and transmit password 122 to server 106 for verification.

[0054] In some embodiments, account application 136 (or another application that configures computing device 102 based on configuration information 148) may not be installed on the device. In some such embodiments, operating system 134 may cause account application 136 to be downloaded and installed on computing device 102 based on URL and / or password 122. In other such embodiments, an application clip (e.g., In one embodiment, the app clip, instant app, and / or progressive web app may be automatically removed from computing device 102 after configuration information 148 is used to configure computing device 102.

[0055] Figure 1BAn embodiment is depicted in which the account application 136 transmits the password 122 to the server 106. The server 106 may provide the password 122 to the authentication application 138 and / or the HSM 130 for verification based at least in part on instances of the master key 114 and / or the UDK 118 stored by the server 106. In some embodiments, the authentication application 138 and / or the HSM 130 may identify the UDK 118 (or the master key 114) and the counter 116 using the unencrypted unique ID 112 provided to the server 106. In examples where the PAN sequence 144 is used to generate the password 122, the server 106 may identify the PAN sequence 144 in the account database 128 and / or the HSM 130 using the unencrypted unique ID 112. In some examples, the authentication application 138 may provide the UDK 118, the unique ID 112, and the counter 116 as inputs to a cryptographic function of the HSM 130 that produces one or more diversified keys 120 as outputs. In other embodiments, the server encrypts the UDK 118, the unique ID 112, and the PAN sequence 144 to generate a diversified key 120. The resulting diversified key 120 may correspond to the diversified key 120 of the contactless card 104, which may be used to decrypt the password 122 and / or verify the MAC after decryption. For example, the server 106 may generate a MAC based on the same data as the applet 110, such as the sensitive data, the unique ID 112, the counter 116, and / or the PAN sequence 144. If the MAC generated by the server 106 matches the decrypted MAC in the password 122, the server 106 may verify or otherwise authenticate the password 122.

[0056] Regardless of the decryption used, the authentication application 138 and / or HSM 130 may successfully decrypt the password 122 and verify the MAC, thereby verifying and / or authenticating the password 122. If the decryption and / or MAC verification is successful, the authentication application 138 may reference the account database 128 to identify the configuration information 148 for the account. In some embodiments, the authentication application 138 may access the configuration information 148 based on the unencrypted unique ID 112 provided to the server 106. In this context, the embodiments are not limited as any suitable identifier may be used to access the configuration information 148 for the account. The server 106 may also transmit a response to the computing device 102 (e.g., to the account application 136 and / or the operating system 134) indicating that the server 106 verified the password 122 and that the configuration information 148 may be used to configure the computing device 102.

[0057] The authentication application 138 may then parse the configuration information 148 to identify each application, operating system, and / or setting registered therein. Continuing with the previous example, the configuration information 148 may include an indication of a social media application and an email client. As described in more detail below, the server 106 may then transmit the configuration information 148 (and / or portions thereof) to the computing device 102.

[0058] Returning to decryption, if authentication application 138 is unable to decrypt password 122 (and / or is unable to verify the MAC), authentication application 138 does not verify password 122. In such an example, authentication application 138 determines not to access configuration information 148 to automatically configure computing device 102. Authentication application 138 may transmit a response to computing device 102 that includes an indication of the decryption and / or verification failure and an indication that configuration information 148 cannot be used to configure computing device 102.

[0059] Figure 1C An embodiment is depicted in which the authentication application 138 transmits a push notification 150 including the configuration information 148 to the account application 136 of each identified application or other software component in the configuration information 148 in the account database 128. In some embodiments, the push notification 150 includes an indication that the server 106 has verified the password 122 and that the configuration information 148 can be used to configure the computing device 102. Although depicted as being transmitted in a single push notification, in some embodiments, the server 106 may transmit multiple push notifications to the computing device 102, where each push notification includes at least a portion of the configuration information 148. In some embodiments, a given push notification may be received in the background of the operating system 134 (e.g., a background push notification that may not be output for display on the computing device 102 but is instead sent directly to the corresponding application and / or operating system 134). In some embodiments, the push notification is a foreground push notification (e.g., a notification displayed on the computing device 102). In some embodiments, the configuration information 148 includes one or more configuration files.

[0060] Additionally, in some embodiments, the size of configuration information 148 (and / or a portion thereof) may exceed a size threshold (e.g., 1 megabyte, 10 megabytes, etc.). In such embodiments, server 106 may generate one or more tokens, associate each token with one or more portions of configuration information 148, and transmit the one or more tokens to computing device 102. Computing device 102 may then transmit the tokens to server 106 to retrieve the relevant configuration information 148 (and / or a portion thereof) from server 106. For example, by associating a token with configuration information 148, server 106 may provide the associated configuration information 148 based on receiving the token from account application 136, operating system 134, and / or other applications 146.

[0061] In some embodiments, computing device 102 may transmit configuration information 148 and / or the token to contactless card 104. Contactless card 104 may then store configuration information 148 and / or the token in memory 108. Computing device 102 may subsequently receive configuration information 148 from contactless card 104 (e.g., via NFC in response to a tap of contactless card 104 to computing device 102) to configure computing device 102 and any of its components as described herein.

[0062] In addition, as shown in the figure, Figure 1C An embodiment is depicted in which computing device 102 includes three different applications, such as other applications 146 - 1 , other applications 146 - 2 , and other applications 146 -N, in addition to account application 136 . Advantageously, account application 136 can configure these applications on computing device 102 using configuration information 148 .

[0063] Figure 1D An embodiment is depicted in which the account application 136 uses one or more portions of the configuration information 148 received from the server 106 to configure the computing device 102. As described above, the account application 136 can adjust the use of the configuration information 148 based on a response from the server 106 indicating that the server 106 verified the password 122 and that the configuration information 148 can be used to configure the computing device 102. As shown, the account application 136 uses the configuration information 148-1 to configure other applications 146-1, and uses the configuration information 148-N to configure other applications 146-N. In some embodiments, the account application 136 can parse the configuration information 148 to generate the configuration information 148-1 to 148-N. In other embodiments, the server 106 generates the configuration information 148 to include multiple files, one file for each application or other entity configured on the computing device 102. Therefore, in such embodiments, the configuration information 148-1 to 148-N is generated by the server 106. In some embodiments, at least a portion of the configuration information 148 is associated with the account application 136 and is thus used to configure the account application 136 (eg, load a user profile, settings, etc.).

[0064] In some embodiments, account application 136 saves (or writes) configuration information 148 as a corresponding configuration file in a location associated with each application and / or operating system 134. For example, account application 136 may store configuration information 148-1 as a configuration file for another application 146-1 (e.g., with a file name and / or stored in a file location associated with a file storing configuration information for application 146-1). As another example, account application 136 may use a portion of configuration information 148 to store and / or modify one or more files, registry settings, or other parameters of operating system 134. In some such examples, account application 136 may provide configuration information 148 to operating system 134, where operating system 134 may use configuration information 148 to modify operating system 134. In some embodiments, use of configuration information 148 may result in new configuration information being written to computing device 102, may result in some existing configuration information of computing device 102 being modified (e.g., by changing a value, setting, etc.), and / or may result in other existing configuration information of computing device 102 remaining unchanged.

[0065] In addition, the account application 136 uses the configuration information 148-3 to determine that the application 146-3 is not installed on the computing device 102. In such an embodiment, the account application 136 uses the configuration information 148-3 (e.g., the package name of the application 146-3) to download the application 146-3 from the Internet. The account application 136 can then use the configuration information 148-3 to configure the application 146-3 as described herein.

[0066] Similarly, the account application 136 uses the configuration information 148 to determine that the other application 146-2 is not registered in the configuration information 148. In some embodiments, the account application 136 determines that the other application 146-2 is a restricted application based on the configuration information 148. For example, an enterprise may restrict the use of social media applications on enterprise devices. Therefore, based on the configuration information 148, the account application 136 causes the computing device 102 to uninstall or otherwise disable the other application 146-2. In some embodiments, the account application 136 can permanently restrict the user from reinstalling or otherwise enabling the other application 146-2 (e.g., by configuring the operating system 134 to restrict the installation and / or enabling of the other application 146-2 on the computing device 102).

[0067] In some embodiments, the account application 136 may require additional permissions to configure the computing device 102. For example, the account application 136 may need access to the storage media (e.g., non-volatile and / or volatile memory, not shown for clarity) of the computing device 102, for example, to read, write, or otherwise access the storage. In such embodiments, the account application 136 and / or the operating system 134 may request that the account application 136 be granted access to the storage, which may be authorized by the user and, in turn, by the operating system 134.

[0068] Thus, by configuring computing device 102 using configuration information 148, computing device 102 may be automatically configured to include all associated applications, settings, and / or functions. For example, by configuring an email client with configuration information 148, a user may be able to view emails, receive new emails, connect to an email server, and send new emails. In this context, the embodiments are not limited. Furthermore, before configuring computing device 102 using configuration information 148, the user may not be able to view emails, receive emails, connect to an email server, or send emails using an email client (if the email client is not manually configured).

[0069] Figure 2A 2 is a schematic diagram 200 illustrating an embodiment of performing at least a portion of automatic configuration of a computing device 102 using a web browser 206. Figure 2A In the example shown, the contactless card 104 generates a URL 204 with a password in response to the contactless card 104 being tapped on the computing device 102. The URL 204 with a password may include a password generated as described above with reference to the password 122, as well as other related information (e.g., an unencrypted identifier, etc.). More generally, the URL 204 may be generated as described above with reference to the computing device 102. Figure 1A-Figure 1D The URL with the password is generated 204.

[0070] Once read by the operating system 134 (not shown for clarity), the operating system 134 may launch a web browser 206 (e.g., one of the other applications 146) and provide the URL 204 with the password to the web browser 206. Doing so may cause the web browser 206 to access the URL 204 with the password (or a portion thereof). In some embodiments, the URL 204 with the password is directed to a configuration page for automatically configuring the computing device 102. The embodiments are not limited in this context.

[0071] Figure 2BAn embodiment is depicted in which a web browser 206 accesses a URL 204 with a password, for example, based on a hypertext transfer protocol (HTTP) request that includes the URL 204 with the password. As shown, the authentication application 138 can receive the URL 204 with the password based on the HTTP request. The authentication application 138 can then extract the password from the URL 204 with the password for verification. For example, the server 106 can decrypt the password and / or verify the MAC contained therein as described above to verify the password.

[0072] Based on the server 106 verifying the password (e.g., decrypting the password in the URL with the password 204 and / or verifying the MAC), the server 106 can refer to the account database 128 to identify the associated configuration information 148. The server 106 can also transmit a response to the computing device 102 (e.g., to the web browser 206 and / or the operating system 134) based on the verification, indicating that the server 106 verified the password 122 and that the configuration information 148 can be used to configure the computing device 102. In some embodiments, the authentication application 138 can access the configuration information 148 based on the unencrypted unique ID 112 provided to the server 106 in the URL with the password 204. In this context, the embodiments are not limited as any suitable identifier can be used to access the configuration information 148 of the account.

[0073] On the other hand, if server 106 cannot decrypt the password and / or verify the MAC, server 106 does not verify the password. In such an example, authentication application 138 determines not to access configuration information 148 to automatically configure computing device 102. Authentication application 138 can transmit an indication of the decryption and / or verification failure to computing device 102.

[0074] Figure 2C An embodiment is depicted in which the server 106 verifies the password portion of the URL 204 with the password. As described above, when the server 106 verifies the password, the server 106 accesses the configuration information 148 of the account associated with the contactless card 104. The server 106 can then identify a plurality of different applications represented in the configuration information 148. For each identified application, the server 106 can generate a corresponding push notification that includes the relevant configuration information 148 and / or a portion thereof.

[0075] As shown, server 106 sends push notification 208, push notification 210, and push notification 212 to computing device 102. As shown, push notification 208 includes configuration information 148-1, push notification 210 includes configuration information 148-2, and push notification 212 includes configuration information 148-N. In such an example, each corresponding push notification and each configuration information instance therein can be associated with a corresponding application executed on the device. In some embodiments, the push notification can also include a push notification transmitted to operating system 134, which can include configuration information 148 applicable to operating system 134 (e.g., enabling blue light filter, do not disturb function, etc.). In some embodiments, push notification 208, 210 and / or 212 include server 106 verifying password 122 and corresponding indication that configuration information 148 can be used to configure computing device 102.

[0076] In some embodiments, push notifications 208, 210, and / or 212 may be received in the background of operating system 134 (e.g., background push notifications that may not be output for display on computing device 102 but are instead sent directly to the corresponding application and / or operating system 134). In some embodiments, push notifications 208, 210, and / or 212 are foreground push notifications (e.g., notifications displayed on computing device 102). In some embodiments, configuration information 148 includes one or more configuration files. In addition, in some embodiments, the size of configuration information 148-1 to 148-N may exceed a size threshold. In such embodiments, server 106 may generate one or more tokens and include a corresponding token in each of push notifications 208, 210, and 212. Once received, each application may then provide the received token to server 106 to extract the relevant configuration information 148 (and / or a portion thereof) from server 106.

[0077] Figure 2D An embodiment is depicted in which push notifications 208, 210, and 212 are received by other applications 146-1, 146-2, and 146-N, respectively. Generally, once received, other applications 146-1, 146-2, and 146-N can be configured using configuration information 148-1, 148-2, and 148-N, respectively. For example, other application 146-1 can be configured based on configuration information 148-1, other application 146-2 can be configured based on configuration information 148-2, and other application 146-N can be configured based on configuration information 148-N. In some embodiments, other applications 146-1, 146-2, and 146-N and / or operating system 134 adjust use of configuration information 148 based on receiving an indication from server 106 that server 106 has verified password 122 and that configuration information 148 can be used to configure computing device 102.

[0078] In some embodiments, the configuration information 148 is stored as a corresponding configuration file in a location associated with each application and / or the operating system 134. For example, the other application 146-1 may store the configuration information 148-1 as a configuration file for the other application 146-1 (e.g., with a file name and / or stored in a file location associated with a file storing the configuration information for the application 146-1). As another example, the other application 146-1 may use a portion of the configuration information 148-1 to store and / or modify one or more files, registry settings, or other parameters of the operating system 134 to configure the other application 146-1. In some such examples, the other application 146-1 may provide the configuration information 148-1 to the operating system 134, where the operating system 134 may use the configuration information 148 to modify the operating system 134. Similarly, the application 146-2 may store the configuration information 148-2 as a configuration file for the other application 146-2, and the application 146-N may store the configuration information 148-N as a configuration file for the other application 146-N.

[0079] In some embodiments, use of configuration information 148-1 through 148-N may result in new configuration information being written to computing device 102, may result in some existing configuration information of computing device 102 being modified (e.g., by changing values, settings, etc.), and / or may result in other existing configuration information of computing device 102 remaining unchanged.

[0080] and Figure 1A-Figure 1D Similar to the illustrated embodiment, configuration information 148 may be used to install and / or uninstall applications from computing device 102. For example, operating system 134 may receive push notification 210 and determine that application 146-2 is not installed on computing device 102. In such an example, operating system 134 may download application 146-2, e.g., from an application store, the Internet, etc., and install it on computing device 102. Similarly, if configuration information 148-N specifies that application 146-N is not allowed to be installed on the device and / or is not registered in configuration information 148, configuration information 148-N may cause application 146-N to initiate removal (and / or disable) of application 146-N from computing device 102.

[0081] Advantageously, configuration information 148 is used to automatically configure and / or restore computing device 102. By requiring a verification password, configuration of computing device 102 is accomplished in a secure manner. More generally, a user can quickly restore a backup, configure a new device, and / or apply configuration information 148 from one device to another. Embodiments are not limited in these contexts.

[0082] The operation of the disclosed embodiments may be further described with reference to the following figures. Some of the figures may include logic flows. Although the figures presented herein may include specific logic flows, it is understood that the logic flows only provide examples of how the general functions described herein can be implemented. In addition, unless otherwise stated, a given logic flow does not necessarily have to be executed in the order presented. In addition, in some embodiments, not all behaviors shown in the logic flow are required. In addition, a given logic flow may be implemented by hardware elements, software elements executed by a processor, or any combination thereof. In this context, the embodiments are not limited.

[0083] Figure 3 One embodiment of a logic flow or routine 300 is shown. The logic flow 300 may represent some or all of the operations performed by one or more embodiments described herein. For example, the logic flow 300 may include some or all of the operations of automatically configuring a device using configuration information and a contactless card. In this context, the embodiments are not limited.

[0084] In box 302, the routine 300 receives a password (e.g., password 122 and / or password of URL 204 with password) from a contactless card 104 associated with an account by an account application 136 executed on a computing device 102. In box 304, the routine 300 transmits the password to a server 106 by the account application 136. In box 306, the routine 300 receives configuration information 148 of a plurality of applications associated with the account by the account application 136 based on the server verifying the password. The server 106 may include, along with the configuration information 148, an indication that the server 106 verified the password 122 and that the configuration information 148 may be used to configure the computing device 102. The applications may include other applications 146, an operating system 134, and / or an account application 136. In box 308, the routine 300 modifies the corresponding configuration of each application on the computing device 102 based on the configuration information 148.

[0085] Figure 4 One embodiment of a logic flow or routine 400 is shown. The logic flow 400 may represent some or all of the operations performed by one or more embodiments described herein. For example, the logic flow 400 may include some or all of the operations of automatically configuring a device using configuration information and a contactless card. In this context, the embodiments are not limited.

[0086] In box 402, the routine 400 registers a plurality of applications and configuration information for each application associated with an account and / or computing device 102 with a server 106. Doing so may result in the configuration information 148 being stored in at least one entry associated with the account in the account database 128. In box 404, the routine 400 receives, by the computing device 102, a password (e.g., a password 122 and / or a password for a URL 204 with a password) from a contactless card 104 associated with the account. In box 406, the routine 400 transmits, by the computing device 102, the password to the server 106. In box 408, the routine 400 determines, by the computing device 102, based on a response received from the server 106, that the server 106 has verified the password, and that the configuration information 148 may be used to configure the computing device 102. In box 410, the routine 400 receives, by the computing device 102, configuration information 148 for a plurality of applications associated with the account based on the server 106's verification of the password. The applications may include other applications 146 , operating system 134 , and / or account applications 136 .

[0087] In block 412, the routine 400 downloads, by the computing device 102, the first application (e.g., one of the other applications 146) to the device based on a determination that the first application is not installed on the computing device 102. In block 414, the routine 400 installs, by the computing device 102, the first application on the device. In block 416, the routine 400 uninstalls, by the computing device 102, the second application (e.g., another of the other applications 146) from the computing device 102 based on the configuration information 148. For example, the configuration information 148 may specify uninstalling or disabling the second application. In block 418, the routine 400 modifies, by the computing device 102, the respective configuration of each application based on the configuration information 148.

[0088] Figure 5 One embodiment of a logic flow or routine 500 is shown. The logic flow 500 may represent some or all of the operations performed by one or more embodiments described herein. For example, the logic flow 500 may include some or all of the operations of automatically configuring a device using configuration information and a contactless card. In this context, the embodiments are not limited.

[0089] In box 502, the routine 500 registers multiple applications and configuration information for each application with an account with a server. Doing so may cause the configuration information 148 to be stored in an entry associated with the account in the account database 128. In box 504, the routine 500 receives a URL 204 with a password from a contactless card 104 associated with the account by the computing device 102. In box 506, the routine 500 launches a web browser based on the URL 204 with the password by the computing device 102. In box 508, the routine 500 transmits at least the password to the server 106 by the web browser 206, for example, by accessing a web page associated with the URL 204 with the password. In box 510, the routine 500 determines by the web browser 206 based on the response received from the server that the server has verified the password from the URL 204 with the password, and the configuration information 148 can be used to configure the computing device 102.

[0090] In box 512, the routine 500 receives, by the computing device 102, configuration information 148 for a plurality of applications associated with the account based on the server's verification of the password. The applications may include other applications 146, the operating system 134, and / or the account application 136. In box 514, the routine 500 downloads, by the device, the first application to the computing device 102 based on a determination that the first application is not installed on the computing device 102. In box 516, the routine 500 installs, by the computing device 102, the first application on the computing device 102. In box 518, the routine 500 uninstalls, by the computing device 102, a second application (e.g., another one of the other applications 146) based on the configuration information 148. For example, the configuration information 148 may specify uninstalling or disabling the second application. In box 520, the routine 500 modifies, by the computing device 102, the corresponding configuration of each application based on the configuration information 148.

[0091] Fig. 6A600 is a schematic diagram showing an example configuration of a contactless card 104, which may include a payment card issued by a service provider, such as a credit card, debit card, or gift card, as shown by a service provider mark 602 on the front or back of the contactless card 104. In some examples, the contactless card 104 is not related to a payment card and may include, but is not limited to, an identification card. In some examples, a transaction card may include a dual-interface contactless payment card, a reward card, etc. The contactless card 104 may include a substrate 604, which may include a single layer or one or more laminated layers composed of plastic, metal, and other materials. Exemplary substrates include polyvinyl chloride, polyvinyl chloride acetate, acrylonitrile butadiene styrene, polycarbonate, polyester, anodized titanium, palladium, gold, carbon, paper, and biodegradable materials. In some examples, the contactless card 104 may have physical characteristics of an ID-1 format that conforms to the ISO / IEC 7816 standard, and the transaction card may otherwise conform to the ISO / IEC 14443 standard. However, it should be understood that a contactless card 104 according to the present disclosure may have different characteristics and the present disclosure does not require that a transaction card be implemented in a payment card.

[0092] The contactless card 104 may also include identification information 606 displayed on the front and / or back of the card and a contact pad 608. The contact pad 608 may include one or more pads and is configured to establish communication with another client device, such as an ATM, a user device, a smartphone, a laptop, a desktop, or a tablet, via a transaction card. The contact pad may be designed according to one or more standards (such as the ISO / IEC 7816 standard) and may be capable of communicating according to the EMV protocol. The contactless card 104 may also include processing circuitry, an antenna, and other components, such as will be described in detail in the accompanying drawings. Figure 6B These components may be located behind the contact pads 608 or elsewhere on the substrate 604, such as within a different layer of the substrate 604, and may be electrically and physically coupled to the contact pads 608. The contactless card 104 may also include a magnetic stripe or tape, which may be located on the back of the card ( Fig. 6A ). The contactless card 104 may also include a near field communication (NFC) device coupled to an antenna capable of communicating via the NFC protocol. The embodiments are not limited in this manner.

[0093] like Figure 6B As shown, the contact pad 608 of the contactless card 104 may include a processing circuit 610 for storing, processing, and communicating information, including a processor 612, memory 108, and one or more communication interfaces 124. It should be understood that the processing circuit 610 may include additional components necessary to perform the functions described herein, including a processor, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tampering hardware.

[0094] The memory 108 may be a read-only memory, a write-once read-many memory, or a read / write memory, such as a RAM, a ROM, and an EEPROM, and the contactless card 104 may include one or more of these memories. The read-only memory may be a factory-programmable read-only memory or a one-time programmable memory. One-time programmability provides an opportunity to write once and then read multiple times. The write-once / read-many memory may be programmed at a certain point in time after the memory chip leaves the factory. Once the memory is programmed, it may not be rewritten, but it may be read multiple times. The read / write memory may be programmed and reprogrammed multiple times after leaving the factory. The read / write memory may also be read multiple times after leaving the factory. In some cases, the memory 108 may be an encrypted memory that encrypts data using an encryption algorithm executed by the processor 612.

[0095] The memory 108 may be configured to store one or more applets 110, one or more counters 116, a unique ID 112, a master key 114, a UDK 118, a diversification key 120, a PAN sequence 144, and configuration information 148. The configuration information 148 may include one or more tokens generated by the server 106. The one or more applets 110 may include one or more software applications configured to execute on one or more contactless cards 104, such as a Card applet. However, it should be understood that applet 110 is not limited to a Java Card applet, but can be any software application that can operate on a contactless card or other device with limited memory. One or more counters 116 can include a digital counter sufficient to store an integer. Unique ID 112 can include a unique alphanumeric identifier assigned to contactless card 104, and the identifier can distinguish contactless card 104 from other contactless cards 104. In some examples, unique ID 112 can identify a customer and an account assigned to the customer.

[0096] The processor 612 and storage elements of the above exemplary embodiments are described with reference to the contact pad 608, but the present disclosure is not limited thereto. It should be understood that these elements can be implemented outside the contact pad 608, can be completely separated from the contact pad, or can be implemented as other elements other than the processor 612 and the memory 108 elements located within the contact pad 608.

[0097] In some examples, the contactless card 104 can include one or more antennas 614. The one or more antennas 614 can be placed inside the contactless card 104 and around the processing circuit 610 of the contact pad 608. For example, the one or more antennas 614 can be integrated with the processing circuit 610, and the one or more antennas 614 can be used with an external booster coil. As another example, the one or more antennas 614 can be external to the contact pad 608 and the processing circuit 610.

[0098] In one embodiment, the coil of the contactless card 104 can act as the secondary of an air-core transformer. The terminal can communicate with the contactless card 104 by cutting off power or amplitude modulation. The contactless card 104 can use the gap in its power connection to infer the data transmitted from the terminal, which can be functionally maintained by one or more capacitors. The contactless card 104 can communicate by switching the load on its coil or performing load modulation. The load modulation may be detected in the terminal coil by interference. More generally, using one or more antennas 614, processors 612 and / or memory 108, the contactless card 104 provides a communication interface to communicate via NFC, Bluetooth and / or Wi-Fi communications.

[0099] As described above, the contactless card 104 can be built on a software platform that can operate on a smart card or other device with limited memory (such as a JavaCard), and can securely execute one or more applications or applets. The applet 110 can be added to the contactless card to provide a one-time password (OTP) for multi-factor authentication (MFA) in various mobile application-based use cases. The applet 110 can be configured to respond to one or more requests from a reader (such as a mobile NFC reader (e.g., a mobile computing device 102 or a point-of-sale terminal)), such as a near-field data exchange request, and generate an NDEF message including a cryptographically secure OTP encoded as an NDEF text tag. The NDEF message can include a password, such as a password 122 or a URL 204 with a password, as well as any other data.

[0100] One example of an NDEF OTP is an NDEF short record layout (SR=1). In such an example, one or more applets 110 may be configured to encode the OTP as a well-known type text tag of NDEF Type 4. In some examples, an NDEF message may include one or more records. Applet 110 may be configured to add one or more static tag records in addition to the OTP record.

[0101] In some examples, one or more applet applications 110 can be configured to simulate an RFID tag. The RFID tag can include one or more polymorphic tags. In some examples, each time the tag is read, a different password is presented, which data may indicate the authenticity of the contactless card. Based on one or more applet applications 110, the NFC reading of the tag can be processed, the data can be transmitted to a server, such as a server of a banking system, and the data can be verified at the server.

[0102] In some examples, the contactless card 104 and the server may include certain data so that the card can be properly identified. The contactless card 104 may include one or more unique identifiers (not shown). The counter 116 may be configured to increment each time a read operation occurs. In some examples, each time data is read from the contactless card 104 (e.g., by a mobile device), the counter 116 is transmitted to the server for verification and a determination is made as to whether the counter 116 is equal to the server's counter (as part of the verification of the server's counter).

[0103] One or more counters 116 can be configured to prevent replay attacks. For example, if a password has been obtained and replayed, if counter 116 has been read or used or otherwise passed, the password will be immediately rejected. If counter 116 is not used, it can be replayed. In some examples, the counter incremented on contactless card 104 is different from the counter incremented for the transaction. Since there is no communication between the small applications 110 on contactless card 104, contactless card 104 cannot determine the application transaction counter 116. In some examples, contactless card 104 can include a first small application 440-1 (which can be a transaction small application) and a second small application 440-2. Each small application 440-1 and 440-2 can include respective counters 116.

[0104] In some examples, counter 116 may not be synchronized. In some examples, to account for unexpected reads that initiate transactions, such as reading at an angle, counter 116 may be incremented, but the application does not process counter 116. In some examples, when mobile device 10 is awake, NFC may be enabled, and computing device 102 may be configured to read available tags, but not take any action in response to the read.

[0105] To keep the counter 116 synchronized, an application, such as a background application, can be executed that will be configured to detect when the computing device 102 wakes up and synchronizes with the server of the banking system, indicate the read that occurred due to the detection, and then move the counter 116 forward. In other examples, a hashed one-time password can be used so that a window of false synchronization can be accepted. For example, if within a threshold of 10, the counter 116 can be configured to move forward. However, if within a different threshold, such as within 10 or 1000, a request to perform a resynchronization can be processed, which requests the user to tap, gesture, or otherwise indicate one or more times via the user's device via one or more applications. If the counter 116 increases in the appropriate order, it can be known that the user has done so.

[0106] The key diversification technique described herein with reference to counter 116, master key 114, UDK 118, and diversification key 120 is one example of an encryption and / or decryption key diversification technique. This example key diversification technique should not be considered limiting of the present disclosure, as the present disclosure is equally applicable to other types of key diversification techniques.

[0107] During the creation of the contactless card 104, two cryptographic keys may be uniquely assigned to each card. The cryptographic keys may include symmetric keys, which may be used for encryption and decryption of data. The Triple DES (3DES) algorithm may be used by EMV, and it is implemented by hardware in the contactless card 104. By using a key diversification process, one or more keys may be derived from a master key based on uniquely identifiable information for each entity that requires a key.

[0108] In some examples, to overcome the shortcomings of the 3DES algorithm, which may be susceptible to vulnerabilities, session keys (such as unique keys for each session) can be derived, but a unique card derived key (e.g., UDK 118) and a counter can be used as diversified data instead of using a master key. For example, each time a contactless card 104 is used in an operation, a different key can be used to create a message authentication code (MAC) and perform encryption. This results in three layers of cryptography. The session key can be generated by one or more applets and derived using an application transaction counter and one or more algorithms (as defined in EMV4.3 Book 2 A1.3.1 Universal Session Key Derivation).

[0109] Additionally, the increment may be unique to each card and may be assigned either through personalization or through some identifying information algorithm. For example, odd numbered cards may increment by 2 and even numbered cards may increment by 5. In some examples, the increment may also vary across sequential reads such that a card may be sequentially incremented by 1, 3, 5, 2, 2, ... repeatedly. The specific sequence or algorithmic sequence may be defined at personalization or from one or more processes derived from the unique identifier. This may make it more difficult for a replay attacker to generalize from a small number of card instances.

[0110] The authentication message may be delivered as the content of a text NDEF record in hexadecimal ASCII format. In another example, the NDEF record may be encoded in hexadecimal format.

[0111] Figure 7 An NDEF short record layout (SR=1) data structure 700 is shown according to an example embodiment. One or more applets 110 may be configured to encode the OTP as a well-known type text tag of NDEF type 4. In some examples, the NDEF message may include one or more records. The applet may be configured to add one or more static tag records in addition to the OTP record. Exemplary tags include, but are not limited to, tag type: well-known type, text, encoded English (en); applet ID: D2760000850101; capabilities: read-only access; encoding: the authentication message may be encoded as ASCII hexadecimal; type-length-value (TLV) data may be provided as personalized parameters that may be used to generate the NDEF message. In one embodiment, the authentication template may include a first record having a well-known index for providing the actual dynamic authentication data. The data structure 700 may include a password, such as a password 122 or a URL 204 with a password, and any other data provided by the applet 110.

[0112] Figure 8 An embodiment of an exemplary computer architecture 800 suitable for implementing various embodiments as described above is shown. In one embodiment, the computer architecture 800 may include or be implemented as a portion of the computing architecture 100 and / or 200. In some embodiments, the computing system 800 may represent, for example, a contactless card 104, a computing device 102, and / or a server 106. In this context, the embodiments are not limited. More generally, the computing architecture 800 is configured to implement the embodiments described herein. Figure 1A-Figure 7 All logics, applications, systems, methods, devices and functions described herein.

[0113] The terms "system" and "component" used in this application are intended to refer to computer-related entities, whether hardware, a combination of hardware and software, software, or software in execution, examples of which are provided by the exemplary computing computer architecture 800. For example, a component can be, but is not limited to, a process running on a processor, a processor, a hard drive, multiple storage drives (of optical and / or magnetic storage media), an object, an executable file, an execution thread, a program, and / or a computer. As an example, both an application running on a server and a server can be a component. One or more components can reside in a process and / or an execution thread, and a component can be localized on a computer and / or distributed between two or more computers. In addition, components can be communicatively coupled to each other through various types of communication media to coordinate operations. Coordination may involve a unidirectional or bidirectional exchange of information. For example, a component can communicate information in the form of a signal communicated through a communication medium. The information can be implemented as a signal assigned to various signal lines. In this assignment, each message is a signal. However, other embodiments may alternatively employ data messages. Such data messages can be sent through various connections. Exemplary connections include parallel interfaces, serial interfaces, and bus interfaces.

[0114] The computer architecture 800 includes various common computing elements, such as one or more processors, multi-core processors, coprocessors, memory units, chipsets, controllers, peripherals, interfaces, oscillators, timing devices, video cards, audio cards, multimedia input / output (I / O) components, power supplies, etc. However, embodiments are not limited to implementation by the computing computer architecture 800.

[0115] like Figure 8 As shown, computer architecture 800 includes computer 812, which includes processor 802, system memory 804 and system bus 806. Processor 802 can be any of a variety of commercially available processors. Computer 812 can represent computing device 102 and / or server 106.

[0116] The system bus 806 provides an interface to the processor 802 for system components including, but not limited to, the system memory 804. The system bus 806 may be any of several types of bus structures, which may also interconnect a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercial bus architectures. Interface adapters may be connected to the system bus 806 via a slot architecture. Example slot architectures may include, but are not limited to, Accelerated Graphics Port (AGP), Cardbus, (Extended) Industry Standard Architecture ((E)ISA), Micro Channel Architecture (MCA), NuBus, Peripheral Component Interconnect (Extended) (PCI(X)), PCI Express, Personal Computer Memory Card International Association (PCMCIA), and the like.

[0117] The computer architecture 800 may include or implement various articles of manufacture. Articles of manufacture may include a computer-readable storage medium for storing logic. Examples of computer-readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, etc. Examples of logic may include executable computer program instructions implemented using any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, visual code, etc. Embodiments may also be implemented at least in part as instructions contained in or on a non-transitory computer-readable medium, which may be read and executed by one or more processors to perform the operations described herein.

[0118] The system memory 804 may include various types of computer-readable storage media in the form of one or more high-speed memory units such as read-only memory (ROM), random access memory (RAM), dynamic RAM (DRAM), double data rate DRAM (DDRAM), synchronous DRAM (SDRAM), static RAM (SRAM), programmable ROM (PROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory, polymer memory (such as ferroelectric polymer memory, bidirectional memory, phase change or ferroelectric memory, silicon oxide nitride oxide silicon (SONOS) memory), magnetic or optical cards, device arrays (such as redundant array of independent disks (RAID) drives), solid-state storage devices (e.g., USB memory, solid-state drive (SSD)), and any other type of storage medium suitable for storing information. Figure 8 In the illustrated embodiment, system memory 804 may include non-volatile memory 808 and / or volatile memory 810. A basic input / output system (BIOS) may be stored in non-volatile memory 808.

[0119] The computer 812 may include various types of computer-readable storage media in the form of one or more low-speed memory units, including an internal (or external) hard disk drive 814, a magnetic disk drive 816 for reading from or writing to a removable magnetic disk 818, and an optical disk drive 820 for reading from or writing to a removable optical disk 822 (e.g., a CD-ROM or DVD). The hard disk drive 814, magnetic disk drive 816, and optical disk drive 820 may be connected to the system bus 806 via a HDD interface 824, an FDD interface 826, and an optical drive interface 828, respectively. The HDD interface 824 for external drive implementations may include at least one or both of a universal serial bus (USB) and IEEE 1394 interface technologies.

[0120] The drives and associated computer-readable media provide volatile and / or nonvolatile storage of data, data structures, computer-executable instructions, etc. For example, a number of program modules can be stored in the drives and nonvolatile memory 808 and volatile memory 810, including an operating system 830, one or more applications 832, other program modules 834, and program data 836. In one embodiment, one or more applications 832, other program modules 834, and program data 836 may include, for example, various applications and / or components of system 100.

[0121] A user may enter commands and information into the computer 812 through one or more wired / wireless input devices, such as a keyboard 838 and a pointing device such as a mouse 840. Other input devices may include a microphone, an infrared (IR) remote control, a radio frequency (RF) remote control, a game controller, a stylus, a card reader, a dongle, a fingerprint reader, a glove, a graphic tablet, a joystick, a keyboard, a retina reader, a touch screen (e.g., capacitive, resistive, etc.), a trackball, a trackpad, a sensor, a stylus, etc. These and other input devices are typically connected to the processor 802 through an input device interface 842, which is coupled to the system bus 806, but may also be connected through other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a USB port, an IR port, etc.

[0122] A monitor 844 or other type of display device is also connected to the system bus 806 via an interface, such as a video adapter 846. The monitor 844 may be internal or external to the computer 812. In addition to the monitor 844, computers typically include other peripheral output devices, such as speakers, printers, etc.

[0123] The computer 812 can operate in a networked environment using logical connections to one or more remote computers, such as one or more remote computers 848, via wired and / or wireless communications. The one or more remote computers 848 can be workstations, server computers, routers, personal computers, portable computers, microprocessor-based entertainment devices, peer devices, or other common network nodes, and typically include many or all of the elements described relative to the computer 812, but for simplicity, only a memory and / or storage device 850 is shown. The depicted logical connections include wired / wireless connections to a local area network 852 and / or a larger network (e.g., a wide area network 854). Such LAN and WAN network environments are common in offices and companies and facilitate enterprise-wide computer networks, such as intranets, all of which can be connected to a global communication network, such as the Internet.

[0124] When used in a LAN 852 networking environment, the computer 812 is connected to the LAN 852 through a wired and / or wireless communication network interface or network adapter 856. The network adapter 856 can facilitate wired and / or wireless communications with the LAN 852, which can also include a wireless access point disposed thereon for communicating with the wireless functionality of the network adapter 856.

[0125] When used in a wide area network 854 networking environment, the computer 812 may include a modem 858, or be connected to a communications server on the wide area network 854, or have other means for establishing communications through the wide area network 854, such as through the Internet. The modem 858 may be an internal or external wired and / or wireless device connected to the system bus 806 via the input device interface 842. In a networked environment, program modules described relative to the computer 812 or portions thereof may be stored in the remote memory and / or storage device 850. It should be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.

[0126] The computer 812 is operable to communicate with wired and wireless devices or entities using the IEEE 802 family of standards, such as wireless devices operatively configured for wireless communications (e.g., IEEE 802.11 over-the-air modulation techniques). This includes at least Wi-Fi (or Wireless Fidelity), WiMax, and Bluetooth. TMWireless technology, etc. Therefore, communication can be a predefined structure like traditional networks, or it can be an ad hoc communication between at least two devices. Wi-Fi networks use radio technologies known as IEEE802.11 (a, b, g, n, ac, ax, etc.) to provide secure, reliable, and fast wireless connections. Wi-Fi networks can be used to connect computers to each other, the Internet, and wired networks (using media and functions related to IEEE 802.3).

[0127] As previously referenced Figure 1A -The various elements of the device described in Figure 12 may include various hardware elements, software elements, or a combination of the two. Examples of hardware elements may include devices, logic devices, components, processors, microprocessors, circuits, processors, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field programmable gate arrays (FPGAs), memory cells, logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. Examples of software elements may include software components, programs, applications, computer programs, applications, system programs, software development programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, processes, software interfaces, application program interfaces (APIs), instruction sets, computing codes, computer codes, code segments, computer code segments, words, values, symbols, or any combination thereof. However, as desired for a given implementation, the determination of whether to use hardware elements and / or software elements to implement an embodiment may vary depending on any number of factors, such as desired computing rates, power levels, thermal tolerances, processing cycle budgets, input data rates, output data rates, memory resources, data bus speeds, and other design or performance constraints.

[0128] One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium, which represents various logic within the processor, and when read by a machine, causes the machine to manufacture logic to perform the techniques described herein. Such representations, referred to as "IP cores", may be stored on tangible machine-readable media and provided to various customers or manufacturing facilities to be loaded into manufacturing machines that manufacture logic or processors. For example, some embodiments may be implemented using a machine-readable medium or article, which may store an instruction or a set of instructions that, if executed by a machine, may cause the machine to perform methods and / or operations according to the embodiments. Such a machine may include, for example, any suitable processing platform, computing platform, computing device, processing device, computing system, processing system, computer, processor, etc., and may be implemented using any suitable combination of hardware and / or software. The machine-readable medium or article may include, for example, any suitable type of memory unit, memory device, memory article, memory medium, storage device, storage article, storage medium and / or storage unit, such as memory, removable or non-removable media, erasable or non-erasable media, writable or rewritable media, digital or analog media, hard disk, floppy disk, compact disk read only memory (CD-ROM), compact disk recordable (CD-R), compact disk rewritable (CD-RW), optical disk, magnetic media, magneto-optical media, removable memory cards or diskettes, various types of digital versatile disks (DVDs), magnetic tapes, cassettes, etc. The instructions may include any suitable type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, encrypted code, etc., implemented using any suitable high-level, low-level, object-oriented, visual, compiled and / or interpreted programming language.

[0129] The components and features of the above-described devices may be implemented using any combination of discrete circuits, application specific integrated circuits (ASICs), logic gates, and / or single chip architectures. In addition, where appropriate, features of the devices may be implemented using microcontrollers, programmable logic arrays, and / or microprocessors, or any combination of the above. It should be noted that hardware, firmware, and / or software elements may be collectively or individually referred to herein as "logic" or "circuitry."

[0130] It should be understood that the exemplary devices shown in the above block diagrams can represent one functional description example of many potential implementations. Therefore, the division, omission or inclusion of block functions shown in the drawings does not mean that the hardware components, circuits, software and / or elements used to implement these functions will necessarily be divided, omitted, or included in the embodiments.

[0131] At least one computer-readable storage medium may include instructions that, when executed, cause a system to perform any of the computer-implemented methods described herein.

[0132] Some embodiments may be described using the expression "one embodiment" or "an embodiment" and their derivatives. These terms mean that a particular feature, structure, or characteristic described in conjunction with the embodiment is included in at least one embodiment. The phrase "in one embodiment" appearing in various places in the specification does not necessarily refer to the same embodiment. In addition, unless otherwise stated, the above-mentioned features are considered to be usable together in any combination. Therefore, any features discussed separately can be used in combination with each other, unless it is noted that these features are incompatible with each other.

[0133] It is emphasized that the Abstract of the present disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the above detailed description, it can be seen that various features are grouped together in a single embodiment in order to simplify the present disclosure. This disclosure method should not be interpreted as reflecting an intention that the claimed embodiments require more features than those explicitly cited in each claim. On the contrary, as reflected in the following claims, the inventive subject matter lies in less than all features of a single disclosed embodiment. Therefore, the following claims are hereby incorporated into the detailed description, and each claim stands on its own as a separate embodiment. In the appended claims, the terms "including" and "in which" are used as the plain English equivalents of the corresponding terms "comprising" and "wherein", respectively. In addition, the terms "first", "second", "third", etc. are used only as labels and are not intended to impose numerical requirements on their objects.

[0134] The foregoing includes examples of the disclosed architecture. It is, of course, not possible to describe every conceivable combination of components and / or methodologies, but one of ordinary skill in the art will recognize that many other combinations and permutations are possible. Accordingly, the novel architecture is intended to embrace all such changes, modifications, and variations that fall within the spirit and scope of the appended claims.

[0135] The above description of example embodiments has been given for the purpose of illustration and description. It is not intended to be exhaustive or to limit the disclosure to the precise form disclosed. Many modifications and variations are possible in light of the disclosure. The scope of the disclosure is not limited by this detailed description, but by the appended claims. Future applications claiming priority to the present application may claim the disclosed subject matter in different ways, and may generally include any set of one or more limitations variously disclosed or otherwise demonstrated herein.

Claims

1. A method comprising: receiving, by an application executing on the device, a password from a contactless card associated with the account; The application transmits the password to a server; receiving, by the application, configuration information of a plurality of applications associated with the account based on the password; as well as The corresponding configuration of each application on the device is modified based on the configuration information.

2. The method according to claim 1, further comprising, before modifying the configuration of each application: determining, by the application, that a first application of the plurality of applications is not installed on the device; and downloading, by the application, the first application to the device; and The first application is installed on the device by an operating system (OS) of the device.

3. The method according to claim 2, further comprising, after installing the first application on the device: The configuration of the first application is modified based on the configuration information of the first application.

4. The method according to claim 1, wherein: Receiving the configuration information includes receiving a plurality of configuration files from the server.

5. The method according to claim 1, wherein: Receiving the configuration information includes: Each application receives a corresponding push notification from the server, where the corresponding push notification includes corresponding configuration information of the corresponding application, wherein the push notification includes a background notification.

6. The method according to claim 1, wherein: Receiving the configuration information includes: Receiving, by each application, a corresponding push notification from the server, wherein the corresponding push notification includes a corresponding token, wherein the push notification includes a background notification; transmitting, by the corresponding application, the corresponding token to the server; and The corresponding configuration information is received by the corresponding application based on the corresponding token.

7. The method according to claim 1, wherein: The configuration information includes: (i) information for connecting to one or more servers, (ii) account information, (iii) messages, (iv) preferences, and (v) settings.

8. A non-transitory computer-readable storage medium comprising instructions that, when executed by a processor of a device, cause the processor to: receiving, by the application, a code from a contactless card associated with the account; The application transmits the password to a server; receiving, by the application, configuration information of a plurality of applications associated with the account based on the password; as well as The corresponding configuration of each application on the device is modified based on the configuration information.

9. The computer-readable storage medium of claim 8, wherein: The instructions further configure the processor to, prior to modifying the configuration of each application: determining, by the application, that a first application of the plurality of applications is not installed on the device; and downloading, by the application, the first application to the device; and The first application is installed on the device by an operating system (OS) of the device.

10. The computer-readable storage medium of claim 9, wherein: The instructions further configure the processor to, after installing the first application on the device: The configuration of the first application is modified based on the configuration information of the first application.

11. The computer-readable storage medium according to claim 8, wherein: Receiving the configuration information includes receiving a plurality of configuration files from the server.

12. The computer-readable storage medium of claim 8, wherein: Receiving the configuration information includes: Each application receives a corresponding push notification from the server, where the corresponding push notification includes corresponding configuration information of the corresponding application, wherein the push notification includes a background notification.

13. The computer-readable storage medium of claim 8, wherein: Receiving the configuration information includes: Receiving, by each application, a corresponding push notification from the server, wherein the corresponding push notification includes a corresponding token, wherein the push notification includes a background notification; transmitting, by the corresponding application, the corresponding token to the server; and The corresponding configuration information is received by the corresponding application based on the corresponding token.

14. The computer-readable storage medium of claim 8, wherein: The configuration information includes: (i) information for connecting to one or more servers, (ii) account information, (iii) messages, (iv) preferences, and (v) settings.

15. A computing device comprising: processor; and a memory storing instructions that, when executed by the processor, cause the processor to: receiving, by the application, a code from a contactless card associated with the account; The application transmits the password to a server; receiving, by the application, configuration information of a plurality of applications associated with the account based on the password; as well as The corresponding configuration of each application on the device is modified based on the configuration information.

16. The computing device of claim 15, wherein: The instructions further cause the processor, before modifying the configuration of each application: determining, by the application, that a first application of the plurality of applications is not installed on the device; and downloading, by the application, the first application to the device; as well as The first application is installed on the device by an operating system (OS) of the device.

17. The computing device of claim 16, wherein: The instructions further configure the device to, after installing the first application: The configuration of the first application is modified based on the configuration information of the first application.

18. The computing device of claim 15, wherein: Receiving the configuration information includes receiving a plurality of configuration files from the server.

19. The computing device of claim 15, wherein: Receiving the configuration information includes: Each application receives a corresponding push notification from the server, where the corresponding push notification includes corresponding configuration information of the corresponding application, wherein the push notification includes a background notification.

20. The computing device of claim 15, wherein: Receiving the configuration information includes: Receiving, by each application, a corresponding push notification from the server, wherein the corresponding push notification includes a corresponding token, wherein the push notification includes a background notification; transmitting, by the corresponding application, the corresponding token to the server; and The corresponding configuration information is received by the corresponding application based on the corresponding token.

Images