System and method for data access control of personal user data using short-range transceivers

Abstract

Systems and methods are presented for controlling data access through interaction between a short-range transceiver, such as a contactless card, and a client device. Exemplary systems and methods may include establishing a database that stores user and service provider identifiers and keys, receiving a request for a service provider token and a data access key from the service provider's client device over a network, the request generated in response to a tap action between a contactless card associated with the user and the client device, verifying that the service provider is authorized to receive access to personal user data encrypted and stored on the contactless card, generating the data access key based on the user key, and transmitting the data access key over the network to the service provider client device so that the client device may decrypt the personal user data retrieved from the contactless card.

Description

[Technical Field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority to U.S. Patent Application No. 16 / 863,750, filed April 30, 2020, the disclosure of which is incorporated herein by reference in its entirety.

[0002] Field of Disclosure The present disclosure relates generally to user data control, and more particularly to an exemplary system and method for active control of access to personal user data through interaction of short-range transceivers and client devices. [Background technology]

[0003] A typical user has confidential or sensitive personal user information or data, including, for example, information such as personal health data, social security numbers, and family contact information. When a user creates an account, the user typically provides a certain amount of personal identifying information about the user and account access information such as a username and password. Entities other than the user may be added to the personal user data. Different entities may have, for example, different user data retention policies, different usage policies, and different user data sharing policies. Policies regarding the use of user information may further change without notice to the user. Additionally, the owner of user information may change without notice to the user, often through a merger or acquisition of one entity by another.

[0004] Access to an account often relies on login credentials (e.g., username and password) to verify the cardholder's identity. However, if the login credentials are compromised, others may be able to access the user's account and, in some cases, the user's confidential or sensitive information or data. Furthermore, the more entities or individuals with whom a user shares personal information, the greater the risk that a breach at any one entity will result in the theft of the user's information. Furthermore, a user may only wish to share certain personal information with entities or individuals for limited purposes or for a limited time.

[0005] Therefore, it would be beneficial to provide exemplary systems and methods that allow users to control the use of their information to overcome at least some of the deficiencies described herein. Summary of the Invention

[0006] Aspects of the disclosed technology include systems and methods for controlling data access through interaction of a short-range transceiver, such as a contactless card, with a client device. Data access control may be provided in the context of personal user data and may include processing requests to obtain access to personal user data through interaction of a short-range transceiver, such as a contactless card, with a client device such that the personal user data is provided only to service providers authorized to verify the data and disclosure of specific account identifier information or account login information is not disclosed to service providers requesting access to the personal user data.

[0007] An embodiment of the present disclosure provides a data access control system, the system comprising: a database storing information comprising a user identifier and a user key associated with a user and a service provider identifier and a service provider key associated with a service provider; a server configured to communicate data with a client device associated with the service provider over a network; a contactless card associated with the user, the contactless card comprising a communications interface, a processor, and a memory, the memory storing an applet, a user token, and personal user data associated with the user, the personal user data being encrypted using the user key; and a client application comprising instructions for execution on the client device, the client application receiving the user token from the contactless card in response to a tapping action between the contactless card and the client device, and and transmitting a request for a service provider token, a user token, and a data access key to the server, wherein the service provider token is associated with the service provider and is configured to receive the data access key from the server, receive encrypted personal user data from the contactless card, and decrypt the encrypted personal user data using the data access key; and the data access control system comprises: a processor in data communication with the server and the database, the processor configured to receive from the client device the request for the service provider token, the user token, and the data access key, identify the service provider based on the service provider token, identify the user based on the user token, verify that the service provider is authorized to receive access to the personal user data, and transmit the data access key to the client device.

[0008] An embodiment of the present disclosure provides a method for controlling data access, the method including: establishing a database storing information comprising a user identifier and a user key associated with a user, and a service provider identifier and a first service provider key associated with a service provider; receiving, via a network, from a first client device associated with the service provider, a service provider token and a request for a data access key to access personal user data stored on a contactless card associated with the user, the personal user data being encrypted using the user key, the request being generated in response to a tapping action between the contactless card and the first client device, the request involving the user token stored on the contactless card; identifying the service provider based on the service provider token; identifying the user based on the user token; verifying that the service provider is authorized to receive access to the personal user data stored on the contactless card; generating a data access key based on the user key; and transmitting the data access key to the first client device.

[0009] An embodiment of the present disclosure provides a method for controlling data access, the method including: establishing a database storing information comprising a user identifier and a user key associated with a user and a service provider identifier and a service provider key associated with a service provider; providing a contactless card comprising a communication interface, a processor, and a memory, the memory storing an applet and a user token, the communication interface configured to support at least one of near field communication, Bluetooth, or Wi-Fi, the contactless card being associated with the user; and providing a client application comprising instructions for execution on a client device associated with the service provider, the client application receiving the user token from the contactless card in response to a tapping action between the contactless card and the client device, and sending a request to a server for the service provider token, the user token, and a data access key, the service provider token being associated with the service provider. receiving from the server a data access key and a link to a data repository storing encrypted personal user data associated with the user, the data access key being generated based on the user key; transmitting a request for the encrypted personal user data to the data repository via the link; receiving the encrypted personal user data from the data repository; and decrypting the encrypted personal user data using the data access key; the method is configured to receive from the client device over a network a service provider token and a request for the data access key to access the personal user data associated with the user, the request being accompanied by the user token; identifying a service provider based on the service provider token; identifying the user based on the user token; verifying that the service provider is authorized to receive access to the personal user data associated with the user; and generating a link to the data repository storing the encrypted personal user data.retrieving a user key from the database; generating a data access key based on the user key; and transmitting the data access key and a link to a data repository storing encrypted personal user data to the client device.

[0010] Further features of the disclosed design and advantages offered thereby are described in more detail below with reference to specific exemplary embodiments that are described below and illustrated in the accompanying drawings. [Brief explanation of the drawings]

[0011] [Figure 1A] FIG. 1 is an illustration of a data access control system in accordance with one or more exemplary embodiments. [Figure 1B] FIG. 1 illustrates a sequence for providing data access control in accordance with one or more exemplary embodiments. [Figure 1C] FIG. 1 illustrates a sequence for providing data access control in accordance with one or more exemplary embodiments. [Figure 2] 1 illustrates components of a client device for use in a data access control system according to one or more exemplary embodiments. [Figure 3] 1 illustrates components of a short-range transceiver for use in a data access control system according to one or more exemplary embodiments. [Figure 4] FIG. 1 illustrates an interaction between a client device and a short-range transceiver used in a data access control system according to one or more exemplary embodiments. [Figure 5] FIG. 1 illustrates an interaction between a client device and a short-range transceiver used in a data access control system according to one or more exemplary embodiments. [Figure 6A] 1 provides a flowchart illustrating a method of data access control according to one or more exemplary embodiments. [Figure 6B]1 provides a flowchart illustrating a method of data access control according to one or more exemplary embodiments. [Figure 7A] 1 provides a flowchart illustrating one or more methods of data access control according to one or more exemplary embodiments. [Figure 7B] 1 provides a flowchart illustrating one or more methods of data access control according to one or more exemplary embodiments. [Figure 7C] 1 provides a flowchart illustrating one or more methods of data access control according to one or more exemplary embodiments. [Figure 8] FIG. 1 is an illustration of a data access control system in accordance with one or more exemplary embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0012] The following description of the embodiments provides non-limiting representative examples that refer to numerals to particularly explain the features and teachings of different aspects of the present invention. It should be recognized that the described embodiments can be implemented separately or in combination with other embodiments from the description of the embodiments. Those skilled in the art who review the description of the embodiments should be able to learn and understand the different described aspects of the present invention. The description of the embodiments should facilitate understanding of the present invention so that other embodiments not specifically covered but within the knowledge of those skilled in the art who read the description of the embodiments will be understood to be consistent with the application of the present invention.

[0013] Exemplary embodiments of the disclosed system and method provide for controlling data access through the interaction of a short-range transceiver, such as a contactless card, with a client device. Data access control may be provided in the context of controlling access to personal user data. Requests for access to personal user data are handled through the interaction of a short-range transceiver, such as a contactless card, with a client device such that the personal user data is provided only to service providers authorized to view the data, and disclosure of specific account identifier information or account login information is not required to service providers requesting access to the personal user data. Advantages of the disclosed technology may include improved data security for personal user data, improved access to personal user data when access is required without user response or intervention (e.g., in an emergency), and an improved user experience.

[0014] 1A shows a diagram illustrating a data access control system 100 according to one or more exemplary embodiments. As described further below, system 100 may include client device 101, client device 103, short-range transceiver 105, server 110, processor 120, and database 130. Client device 101 and client device 103 may communicate with server 110 via network 115. Although FIG. 1 shows certain components connected in a particular manner, system 100 may include additional or multiple components connected in various ways.

[0015] System 100 may include one or more client devices, such as client device 101 and / or client device 103, each of which may be a network-enabled computer. As referred to herein, a network-enabled computer may include a computing device or a communication device, including, for example, but not limited to, a server, a network appliance, a personal computer, a workstation, a telephone, a handheld PC, a personal digital assistant, a thin client, a fat client, an Internet browser, or other device. Each of client devices 101 and 103 may also be a mobile device. For example, mobile devices may include an Apple® iPhone®, iPod®, iPad®, or other mobile device running Apple's iOS® operating system, a device running Microsoft's Windows® Mobile operating system, a device running Google's Android® operating system, and / or other smartphones, tablets, or similar wearable mobile devices. Additional functionality that may be included in a client device, such as client device 101 and / or client device 103, is further described below with reference to FIG. 2.

[0016] System 100 may include one or more short-range transceivers, such as short-range transceiver 105. Short-range transceiver 105 may wirelessly communicate with client devices, such as client device 101 and / or client device 103, within a short-range communication range, such as, for example, near field communication (NFC). Short-range transceiver 105 may include, for example, a contactless card, a smart card, or may include devices having various form factors, such as a fob, pendant, or other device configured to communicate within a short-range communication range. In other embodiments, short-range transceiver 105 may be the same as or similar to client devices 101, 103. Additional functionality that may be included in a short-range transceiver, such as short-range transceiver 105, is further described below with reference to FIG. 3.

[0017] System 100 may include one or more servers 110. In some exemplary embodiments, server 110 may include one or more processors (e.g., microprocessors, etc.) coupled to memory. Server 110 may be configured as a central system, server, or platform for controlling and calling various data at different times to perform multiple workflow actions. Server 110 may be a dedicated server computer, such as a blade server, or may be a personal computer, laptop computer, notebook computer, palmtop computer, network computer, mobile device, or any processor-controlled device capable of supporting system 100.

[0018] Server 110 may be configured for data communication (e.g., via a connection, etc.) with one or more processors, such as processor 120. In some exemplary embodiments, server 110 may incorporate processor 120. In some exemplary embodiments, server 110 may be physically separate and / or remote from processor 120. Processor 120 may be configured to function as a back-end processor. Processor 120 may be configured for data communication (e.g., via a connection, etc.) with database 130 and / or server 110. Processor 120 may include one or more processing devices such as a microprocessor, a RISC processor, an ASIC, etc., along with associated processing circuitry. Processor 120 may include or be connected to memory that stores executable instructions and / or data. Processor 120 may communicate, send, or receive messages, requests, notifications, data, etc., from other devices, such as client devices 101 and / or 103, via server 110.

[0019] Server 110 may be configured for data communication (e.g., via a connection) with one or more databases, such as database 130. Database 130 may be a relational database or a non-relational database, or a combination of multiple databases. In some exemplary embodiments, server 110 may incorporate database 130. In some exemplary embodiments, database 130 may be physically separate and / or remote from server 110, located on another server, a cloud-based platform, or any storage device in data communication with server 110.

[0020] The connections between server 110, processor 120, and database 130 may be via any wired and / or wireless communication line, link, or network, or combination thereof, suitable for communication between these components. Such networks may include network 115 and / or one or more networks of the same or similar type as those described herein with reference to network 115. In some exemplary embodiments, the connections between server 110, processor 120, and database 130 may include a corporate LAN.

[0021] The server 110 and / or database 130 may contain user login credentials used to control access to user accounts, including, but not limited to, usernames, passwords, access codes, security questions, swipe patterns, image recognition, identification scans (e.g., driver's license scans or passport scans), device registrations, phone numbers, email addresses, social media account access information, and biometrics (e.g., voice recognition, fingerprint scans, retinal scans, facial scans).

[0022] Database 130 may include data regarding one or more users, one or more service providers, and one or more accounts. Data regarding users may include a user identifier and a user key and may be maintained or organized in one or more accounts. Data regarding service providers may include a service provider identifier and a service provider key and may be maintained or organized in one or more accounts. Accounts may be maintained by (or on behalf of) and / or associated with any one or more of a variety of entities, such as, for example, a bank, a merchant, an online retailer, a service provider, a merchandiser, a manufacturer, a social media provider, a provider or promoter of a sporting or entertainment event, or a hotel chain. For example, database 130 may include, but is not limited to, account identification information (e.g., account number, account holder identification number, account holder name and contact information—any one or more of which may comprise an account identifier), account characteristics (e.g., account type, funding and transaction limits, access and other activity limits), and may include information and data related to the account, such as financial information (balance information, payment history, transaction history, etc.), social information, personal information, etc. The data stored in database 130 may be stored in any suitable format, and may be stored in an encrypted and secure format to prevent unauthorized access. Any suitable algorithms / procedures may be used for the encryption and authorized decryption of data.

[0023] Server 110 may be configured to communicate with one or more client devices, such as client device 101 and / or client device 103, over one or more networks, such as network 115. Network 115 may include one or more of a wireless network, a wired network, or any combination of wireless and wired networks, and may be configured to connect client device 101 and / or 103 to server 110. For example, network 115 may include an optical fiber network, a passive optical network, a cable network, an Internet network, a satellite network, a wireless local area network (LAN), a global system for mobile communications, a personal communication service, a personal area network, a wireless application protocol, a multimedia messaging service, an enhanced messaging service, a short message service, a time division multiplex-based system, a code division multiple access-based system, D-AMPS, Wi-Fi, fixed wireless data, IEEE 802.11b, 802.15.1, 802.11n and 802.11g, Bluetooth, NFC, radio frequency identification (RFID), Wi-Fi, etc.

[0024] Additionally, network 115 may include, but is not limited to, telephone lines, optical fiber, IEEE Ethernet 902.3, wide area networks, wireless personal area networks, LANs, or global networks such as the Internet. Furthermore, network 115 may support an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network 115 may further include one network or any number of the exemplary types of networks listed above, operating as a standalone network or in cooperation with one another. Network 115 may utilize one or more protocols of one or more network elements to which they are communicatively coupled. Network 115 may translate one or more protocols of network devices to and from other protocols. While network 115 is shown as a single network, it should be understood that, according to one or more exemplary embodiments, network 115 may comprise multiple interconnected networks, such as the Internet, a service provider network, a cable television network, an enterprise network such as a credit card association network, a LAN, and / or a home network.

[0025] In some demonstrative embodiments, server 110 may access records, including records, in database 130 to determine one or more methods for communicating with client device 101 and / or client device 103. Communication methods may include executable push notifications to and from applications stored on client device 101 and / or client device 103. Other communication methods may include text messages, email, or other messaging techniques suitable for a network-based client / server configuration. Messages or requests by client device 101 and / or 103 may be communicated to server 110 via applications on the client device, or may be sent by text message, email, or other messaging techniques suitable for a network-based client / server configuration. Communications originating from client device 101 or client device 103 may be sent to server 110 using the same communication method as communications originating from server 110, or via a different communication method.

[0026] FIG. 1B shows a diagram illustrating a sequence for providing data access control according to one or more exemplary embodiments, which may include a request by a service provider for a data access key to access or decrypt personal user data stored on a short-range transceiver. FIG. 1B references similar components of exemplary embodiment system 100 as shown in FIG. 1A. Client device 101 may be associated with a service provider. The service provider may have an associated service provider token. Client device 101 may include an application 102 that may include instructions for execution by client device 101. Client device 101 may include functionality further described below with reference to FIG. 2. Application 102 may be configured to provide a user interface to the service provider when using client device 101. Application 102 may be configured to communicate with other client devices, short-range transceiver 105, and server 110 via client device 101. Application 102 may be configured to receive requests and send messages as described herein with reference to client device 101. Service provider information and user information, including identifiers and / or keys, may be stored in database 130.

[0027] The short-range transceiver 105 may be associated with a user. The short-range transceiver 105 may include, for example, a contactless card and may include features further described below with reference to FIG. 3. The short-range transceiver 105 may have memory for storing the applet 106 and / or the token 107 and for storing personal user data. The token 107 and personal user data 108 may be associated with a user.

[0028] Tokens may be used to enhance security through token validation. The server 110 may send a verification request to a client device, such as the client device 101, receive response information from the client device, and, if verified, send a verification token back to the client device. The verification token may be based on a predetermined token or may be a dynamic token based on an algorithm that may be secret and known only to the server 110 and the client device. The algorithm may include live parameters that participants can independently verify, such as the temperature or time of day at a specific location. The token may be used to verify the identity of a first service provider or user. The verification request and / or verification token may be based on a token 107 stored in the short-range transceiver 105.

[0029] Personal user data 108 may include, for example, personal user information or data that may be confidential or sensitive, such as personal health data, social security numbers, family contact information, etc. (including the types of data identified herein with reference to FIG. 3). Personal user data 108 may be encrypted and stored in a secure format to prevent unauthorized access.

[0030] In some exemplary embodiments, personal user data may include personal health data, such as height, weight, blood type, prescription medications, allergies, emergency contacts, medical treatments or DNR orders, etc. Personal user data may also include personal identification data, such as name, gender, date of birth, etc. The service provider using client device 101 may be, for example, a first responder, emergency team member, or emergency medical provider or technician, and may be associated with a service entity, such as a fire or ambulance department, a police station, a hospital, etc.

[0031] In some demonstrative embodiments, the application 102 may display instructions on the client device 101 to prompt the service provider to initiate a tapping operation between the short-range transceiver 105 and the client device 101. As used herein, a tapping operation may include tapping the short-range transceiver 105 against the client device 101 (or vice versa). For example, if the short-range transceiver 105 is a contactless card and the client device 101 is a mobile device, the tapping operation may include tapping the contactless card on a screen or other portion of the client device 101. However, the tapping operation is not limited to a physical tap by the short-range transceiver 105 against the client device 101, but may include other gestures such as, for example, a wave or other movement of the short-range transceiver 105 near the client device 101 (or vice versa).

[0032] There may be a tapping action at label 150 between short-range transceiver 105 and client device 101. The tapping action may be in response to a prompt displayed on client device 101.

[0033] At label 152, application 102 may communicate with short-range transceiver 105 (via client device 101) (e.g., after short-range transceiver 105 is brought close to client device 101). Communication between application 102 and short-range transceiver 105 may involve short-range transceiver 105 (e.g., a contactless card, etc.) being sufficiently close to a card reader (not shown) of client device 101 to enable NFC data transfer between application 102 and short-range transceiver 105, and may occur in conjunction with (or in response to) a tapping action between short-range transceiver 105 and client device 101 (e.g., a tapping action on label 150, etc.). The communication may include an exchange of data or commands to establish a communication session between application 102 and short-range transceiver 105. The exchange of data may include the transfer or exchange of one or more keys. These may be pre-existing keys or generated as session keys. In some demonstrative embodiments, communication may occur when the short-range transceiver 105 enters the short-range communication range of the client device 101 prior to a tap operation between the short-range transceiver 105 and the client device 101 .

[0034] At label 154, short-range transceiver 105 may transmit a user token 107 associated with the user to application 102. Token 107 may include a user identifier. In some exemplary embodiments, user token 107 may include a key associated with the user. In some exemplary embodiments, transmission of token 107 to application 102 may occur in conjunction with (or in response to) a tapping operation between short-range transceiver 105 and client device 101 (e.g., a tapping operation at label 150). In some exemplary embodiments, transmission of token 107 to application 102 may occur when short-range transceiver 105 enters short-range communication range of client device 101, prior to the tapping operation between short-range transceiver 105 and client device 101.

[0035] At label 156, application 102 may send user token 107 to server 110 along with a request for a service provider token and a data access key associated with the service provider. This may be performed in response to a tap action between short-range transceiver 105 and client device 101 (e.g., a tap action at label 150). The data access key allows the service provider to decrypt encrypted personal user data 108.

[0036] At label 158, processor 120 may receive (e.g., via server 110) a user token, a service provider token, and a data access key request. Processor 120 may use the user token to identify the user. Processor 120 may use the service provider token to identify the service provider as the sender of the data access key request. In some exemplary embodiments, identifying the service provider may be performed by searching information in database 130 using the service provider identifier in the token. In some exemplary embodiments, at label 159, if the service provider token includes a key associated with the service provider, processor 120 may use the service provider key to authenticate the service provider. Similarly, if the user token includes a key associated with the user, processor 120 may use the user key to authenticate the user. Based on the identity of the service provider (and because such identity may be authenticated), processor 120 may verify whether the service provider is authorized to receive the data access key to decrypt and thereby gain access to personal user data 108. In an exemplary embodiment, the service provider key is available to the service provider and may be valid for a limited period of time, such as daily, weekly, monthly, or other basis. The client device 101 may send a request for the service provider key to the server 110 at intervals (e.g., daily, weekly, monthly, or other basis) when a new key becomes available. Receipt of the service provider key by the client device 101 does not require the service provider to be in proximity of the short-range transceiver 105, and the service provider key may be requested or received by the client device 101 independent of any tapping action on the short-range transceiver 105.

[0037] At label 160, processor 120 may send a data access key to client device 101. As described above, processor 120 may verify that the service provider is authorized to receive the data access key. The data access key may be stored in database 130 or may be generated based on a user key, a service provider key, or a combination of both a user key and a service provider key. The user key may be stored in database 130 or may be included in user token 107. The service provider key may be stored in database 130 or may be included in a service provider token received from client device 101.

[0038] In an exemplary embodiment, processor 120 may instead send a denial notice (not shown) to client device 101 indicating that the service provider is not authorized to receive the data access key.

[0039] At label 162, the short-range transceiver 105 may transmit the encrypted personal user data 108 to the application 102 via the client device 101. Note that, relative to the other events described with respect to FIG. 1B , the timing of the transmission of the encrypted personal user data 108 by the short-range transceiver 105 to the client device 101 is not important. The encrypted personal user data 108 may be transmitted at any time, including upon the first tap action or after receipt of the data access key by the client device 101.

[0040] The application 102 may be configured to use the received data access key to receive, decrypt, and access the encrypted personal user data 108. In some embodiments, the application 102 may cause the personal user data to be displayed on the client device 101. In some embodiments, the application 102 may be permitted to store the personal user data on the client device 101 for retrieval based on a time limit or a limited number of uses.

[0041] In one or more exemplary embodiments, access to personal user data by service providers may be restricted according to data control parameters. In an exemplary embodiment, the data control parameters may be stored in database 130. In an exemplary embodiment, the data control parameters may be stored in memory of short-range transceiver 105. The data control parameters stored in memory of short-range transceiver 105 may be transmitted to and used by application 102 to restrict access to personal user data by service providers. Applet 106 may be configured to receive the data control parameters and store the data control parameters in memory of short-range transceiver 105.

[0042] In one or more exemplary embodiments, the data control parameters may be used to restrict a service provider's access to personal user data in one or more ways. For example, the data control parameters may allow access only for a specific or limited period of time. As another example, the data control parameters may allow access by a service provider for a single use. As another example, the data control parameters may allow access only if the short-range transceiver 105 is detected within the short-range communication range of the client device 101. In one or more embodiments, the user may be prompted to confirm that the service provider may access the personal user data. In one or more embodiments, the user may pre-approve the service provider's access to the personal data so that the user does not have to grant permission when the service provider attempts to obtain data access. The user may confirm or pre-approve access to the personal user data in various ways, such as by tapping the user's short-range transceiver to the client device in response to a prompt.

[0043] In an exemplary embodiment, personal user data may be stored and updated in database 130. Updated personal user data may be stored in database 130 and transmitted to client device 101 in response to a request for personal user data.

[0044] In an exemplary embodiment, the application 102 may be launched in response to a tapping action between the short-range transceiver 105 and the client device 101 .

[0045] FIG. 1C illustrates a diagram illustrating a sequence for providing data access control according to one or more exemplary embodiments, which may include a request by a service provider for a data access key to access or decrypt personal user data stored in a short-range transceiver. FIG. 1C references similar components of the exemplary embodiment system 100 illustrated in FIG. 1A and similar features of the exemplary embodiment system 100 illustrated in FIG. 1B, including features described above with reference to labels 150-159 (not repeated here). The service provider referenced in the above description with reference to FIG. 1B is referred to as the first service provider in the description of FIG. 1C. Referring to FIG. 1C, once the first service provider has been identified as the sender of the data access key request to access the user's personal user data according to the procedure described above with reference to labels 150-159, it may be determined that two authorizations are required.

[0046] The response to the two authorization requirements may include a client device 103 associated with a second service provider. The second service provider may be associated with the same service entity as the first service provider (see above), an entity related to that service entity, or a different entity. The client device 103 may include an application 104 that may include instructions for execution by the client device 103. The client device 103 may include functionality further described below with reference to FIG. 2. The application 104 may be configured to provide a user interface to the second service provider when using the client device 103. The application 104 may be configured to communicate with other client devices, with the short-range transceiver 105, and with the server 110 via the client device 103. The application 104 may be configured to receive requests and send messages as described herein with reference to the client device 103.

[0047] At label 164, processor 120 may send a two-party approval notification to client device 101 (e.g., via server 110) notifying the first service provider that a second service provider is needed to approve the data access key request. Application 102 may cause a message to be displayed on client device 101 indicating that the system is awaiting approval of the request by the second service provider. In some exemplary embodiments, the notification may be sent to client device 103, or to both client device 101 and client device 103. Processor 120 may open a data access session with application 102 to provide tracking of the data access key request (associated with the user, via the user token) while it is awaiting approval.

[0048] There may be a tapping action between the short-range transceiver 105 and the client device 103 at label 166. The tapping action may be responsive to a notification of approval from the two. The application 104 may receive a user token 107 from the short-range transceiver 105.

[0049] At label 168, application 104 may send the user token to server 110 along with a second service provider token associated with the second service provider and a data access key request. This may be in response to the tapping action described above with reference to label 166. The second service provider token may include a second service provider key. Processor 120 may open a data access session with application 104 to provide separate tracking of data access key requests (associated with the user via the user token) from the second service provider. Processor 120 may use the second service provider token to identify the second service provider as the sender of the data access key request. Based on the user token, processor 120 may determine that the data access key request made by the second service provider corresponds to the open data access key request made by the first service provider and, therefore, may attempt to authorize access to personal user data by the first service provider.

[0050] At label 170, processor 120 may send an approval notification to application 104 requesting approval by a second service provider of a data access key request submitted by a first service provider.

[0051] The application 104 may display instructions on the client device 103 for the second service provider to approve the data access key request made by the first service provider. In some exemplary embodiments, the display may instruct the second service provider to tap the short-range transceiver 105 on or against the client device 103 to indicate approval (e.g., as shown in FIG. 5 ). In some exemplary embodiments, the display may instruct the second service provider to press a button (not shown in FIG. 5 ) to indicate approval. In one or more exemplary embodiments, the display on the client device 103 of the instructions to approve the data access key request may be in response to an approval notification on the label 170. In one or more exemplary embodiments, the display on the client device 103 of the instructions to approve the data access key request may be in response to two approval notifications on the label 164.

[0052] When the second service provider acts to indicate approval (e.g., by tapping or pressing a button) at label 172, application 104 may send an approval message to server 110. Based on the approval message, processor 120 may determine that the second service provider has approved the data access key request by the first service provider.

[0053] In an exemplary embodiment, in response to the two approval notifications, application 102 may display a code (such as a QR code or a numeric code) on client device 101 to be scanned or otherwise entered into client device 103. Application 104 may transmit the code (scanned or entered into client device 103) to server 110 to indicate approval of the data access key request. Based on the transmitted code, processor 120 may determine that the second service provider has approved the data access key request by the first service provider.

[0054] At label 174, processor 120 may send a data access key to client device 101. The data access key may be stored in database 130 or generated based on a user key, a first service provider key, or a combination of the user key and the first service provider key, or a combination of the user key, the first service provider key, and the second service provider key. The user key may be stored in database 130 or included in user token 107. The first service provider key may be stored in database 130 or included in a first service provider token received from client device 101. The second service provider key may be stored in database 130 or included in a second service provider token received from client device 103.

[0055] At label 176, the short-range transceiver 105 may transmit the encrypted personal user data 108 to the application 102 via the client device 101. Note that, relative to the other events described with respect to Figures 1B or 1C, the timing of the transmission of the encrypted personal user data 108 by the short-range transceiver 105 to the client device 101 is not important. The encrypted personal user data 108 may be transmitted at any time, including upon the first tap action or after receipt of the data access key by the client device 101.

[0056] 1B , the application 102 may be configured to receive, decrypt, and access the encrypted personal user data 108 using the received data access key, including, for example, displaying the personal user data on the client device 101 and / or storing the personal user data on the client device 101 for retrieval on a time-limited or limited-use basis. In an exemplary embodiment, the received data access key may be stored on the client device 101, and the application 102 may display the personal user data on the client device only if the data access key remains stored on the client device.

[0057] In an exemplary embodiment, the application 104 may be launched in response to a tapping action between the short-range transceiver 105 and the client device 103 .

[0058] FIG. 2 illustrates components of a client device 200 used in a data access control system, according to one or more exemplary embodiments. In one or more exemplary embodiments, client device 200 may be one or more of client devices 101 and / or 103, described above with reference to FIGS. 1A and 1B-1C. Client device 200 may include one or more applications 201, one or more processors 202, a short-range communications interface 203, and a network interface 204. Application 201 may include a software application or executable program code configured to execute on processor 202 and perform any of the functions described herein for any of the client devices, such as client devices 101 and / or 103, and / or any of the functions described herein with reference to application 102. Application 201 may be configured to send and / or receive data with other devices via client device 101, e.g., via short-range communications interface 203 and / or network interface 204. For example, application 201 may be configured to initiate one or more requests, such as a short-range data exchange request to a short-range transceiver (e.g., a contactless card). The application 201 may also be configured to provide a user interface to a user of the client device via a display (not shown). The application 201 may be stored in memory of the client device 200. The memory may include read-only memory, write-once-read-multiple memory, and / or read / write memory, such as RAM, ROM, and EEPROM.

[0059] Processor 202 may include one or more processing devices, such as a microprocessor, a RISC processor, an ASIC, etc., and may include associated processing circuitry. Processor 202 may include or be connected to memory that stores executable instructions and / or data as may be necessary or appropriate to control, operate, or interface with other functions of client device 200, including application 201. Processor 202 (including associated processing circuitry) may include additional components, including processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware, as needed to perform the functions described herein.

[0060] The short-range communication interface 203 may support communication over a short-range wireless communication range, such as NFC, RFID, or Bluetooth. The short-range communication interface 203 may include a reader, such as a mobile device NFC reader. The short-range communication interface 203 may be incorporated into the network interface 204 or may be provided as a separate interface.

[0061] The network interface 204 may include wired or wireless data communication capabilities that support data communication with wired or wireless communication networks, including the Internet, a cellular network, a wide area network, a local area network, a wireless personal area network, a wide body area network, other wired or wireless networks for transmitting and receiving data signals, or any combination thereof. Such networks may include, but are not limited to, telephone lines, optical fiber, IEEE Ethernet 902.3, a wide area network, a local area network, a wireless personal area network, a wide body area network, or a global network such as the Internet.

[0062] Client device 200 may also include a display (not shown). Such a display may be any type of device for presenting visual information, such as a computer monitor, a flat panel display, or a mobile device screen, including liquid crystal displays, light emitting diode displays, plasma panels, and cathode ray tube displays.

[0063] Client device 200 may also include one or more device inputs (not shown). Such inputs may include any device for inputting information into client device 300 that is available and supported by client device 200, such as a touchscreen, keyboard, mouse, cursor control device, touchscreen, microphone, digital camera, video recorder, or camcorder. The device inputs may be used to input information and interact with client device 200 and, in turn, the system described herein.

[0064] FIG. 3 illustrates components of a short-range transceiver 300 for use in a data access control system according to one or more exemplary embodiments. In one or more exemplary embodiments, the short-range transceiver 300 may be one or more of the short-range transceivers 105 described above with reference to FIGS. 1A and 1B-1C. The short-range transceiver 300 may include, for example, a contactless card or devices having various form factors, such as a fob, pendant, or other device configured to communicate within a short-range communication range. The short-range transceiver 300 may include a processor 302, a memory 302, and a short-range communication interface 306.

[0065] Processor 301 may include one or more processing devices, such as a microprocessor, a RISC processor, an ASIC, etc., and may include associated processing circuitry. Processor 301 may include or be connected to memory that stores executable instructions and / or data as may be necessary or appropriate to control, operate, or interface with other functions of short-range transceiver 300, including applet 303. Processor 301 (including associated processing circuitry) may include additional components, including processors, memory, error and parity / CRC checkers, data encoders, anti-collision algorithms, controllers, command decoders, security primitives, and anti-tamper hardware, as needed to perform the functions described herein.

[0066] Memory 302 may be read-only memory, write-once-read-multiple memory, or read / write memory, such as RAM, ROM, and EEPROM. Memory 302 may be configured to store one or more applets 303, one or more tokens 304, and personal user data 305. Applet 303 may comprise one or more software applications configured to execute on processor 301, such as a Java Card applet that may be executable on a contactless card. However, it is understood that applet 303 is not limited to a Java Card applet and may instead be any software application operable on a contactless card or other memory-limited device. Applet 303 may be configured to respond to one or more requests, such as a near-field data exchange request, from a client device, including a request from a device with a reader, such as a mobile device NFC reader. Applet 303 may be configured to read (or write) data, including token 304 and / or personal user data 305, from (or to) memory 302 and provide such data in response to a request.

[0067] The token 304 may include a unique alphanumeric identifier assigned to the user of the short-range transceiver 300, which may distinguish the user of the short-range transceiver 300 from other users of other short-range transceivers (e.g., other contactless card users). In some exemplary embodiments, the token 304 may identify both a customer and an account assigned to that customer, and may further identify the short-range transceiver (e.g., a contactless card) associated with the customer's account. In some exemplary embodiments, the token 304 may include a key unique to the user or customer with whom the short-range transceiver is associated.

[0068] Personal user data 305 may be stored in memory 302 and located in a data file identified, for example, by a specific memory location or file name. Personal user data 305 may include personal user information or data that may be confidential or sensitive, such as personal health data, social security numbers, family contact information, etc. Personal user data 305 may be encrypted and stored in a secure format to prevent unauthorized access. Any suitable algorithms / procedures (including, for example, public / private key encryption) may be used to encrypt and authorize decrypt the data.

[0069] Personal user data 305 (and personal user data 108 described above with reference to Figures 1B-1C) may include any one or more of the following data categories: name, date of birth, email address, home address, ethnicity / race, gender, place of birth, mother's maiden name, social security number, national ID number, passport number, visa permit number, driver's license number, vehicle registration number, genetic information, medical information, disability information, insurance details, location information, what you are doing and when, status, events attended, sexual orientation, education history, grades, employment history, salary, job title / position, financial, social, public, service account information or other accounts, photographs, political and religious leanings and affiliations, views on controversial issues, history / background, credit score / record, sites registered, criminal history, and / or commercially sensitive information.

[0070] The short-range communication interface 306 may support communication over a short-range wireless communication range, such as NFC, RFID, or Bluetooth. The short-range transceiver 300 may also include one or more antennas (not shown) connected to the short-range communication interface 306 to provide connection with the short-range wireless communication range.

[0071] FIG. 4 illustrates an interaction 400 between a client device 401 and a short-range transceiver 420 used in a data access control system according to one or more exemplary embodiments, including those described above with reference to FIGS. 1A-1C. The client device 401 may be the client device 101 described above with reference to FIGS. 1A and 1B-1C. The client device 401 may be associated with a (first) service provider as described above with reference to FIGS. 1B-1C. The user interface 402 may be generated by the application 102 described above with reference to FIGS. 1B-1C. The short-range transceiver 420 may be the short-range transceiver 105 described above with reference to FIGS. 1A and 1B-1C. When the short-range transceiver 420 comes within short-range communication range of the client device 401 (e.g., via a tapping action), the client device 401 may communicate with the short-range transceiver 420. Client device 401 may transmit data or commands to short-range transceiver 420 via transmit signal 431 and receive data from short-range transceiver 420, including token 422, via receive signal 432. Short-range transceiver 420 may also transmit encrypted personal user data (not shown) to client device 401. Communication between client device 401 and short-range transceiver 420 may proceed as described above with reference to Figures 1B-1C (e.g., client device 101 or 103 and short-range transceiver 105).

[0072] The user interface 402 may present on the client device 401 a screen display for a user data access request 410, which may include a field 411 and a field 412. If necessary, the first service provider may enter a username in field 411 and a password in field 412. The screen display may include instructions 414 prompting the first service provider to tap a short-range transceiver 420 (in the illustrated example, the short-range transceiver 420 may be a contactless card) to initiate a data access key request and obtain the data access key necessary to decrypt the encrypted personal user data. The instructions 414 may be a push notification from the server 110 (shown in FIGS. 1A and 1B-1C). In response to the tapping action, the client device 401 may send a data access key request to the server 110 (shown in FIGS. 1A and 1B-1C) along with the user token 422 (from the short-range transceiver 420) and the first service provider token.

[0073] FIG. 5 illustrates an interaction 500 between a client device 501 and a short-range transceiver 520 used in a data access control system according to one or more exemplary embodiments, including those described above with reference to FIGS. 1A-1C. The client device 501 may be the client device 103 described above with reference to FIGS. 1A-1C. The client device 501 may be associated with a second service provider, as described above with reference to FIG. 1C. The user interface 502 may be generated by the application 104 described above with reference to FIG. 1C. The short-range transceiver 520 may be the short-range transceiver 105 described above with reference to FIGS. 1A and 1B-1C. When the short-range transceiver 520 enters the short-range communication range of the client device 501 (e.g., via a tapping action), the client device 501 may communicate with the short-range transceiver 520. Client device 501 may transmit data or commands to short-range transceiver 520 via transmit signal 531 and may receive data, including token 522, from short-range transceiver 520 via receive signal 532. Communication between client device 501 and short-range transceiver 520 may proceed as described above with reference to Figures 1B-1C (e.g., client device 101 or 103 and short-range transceiver 105).

[0074] User interface 502 may present on client device 501 a screen display of user data access request 510, which may include field 511 and field 512. If necessary, second service provider may enter a username in field 511 and a password in field 512. The screen display may include instructions 514 notifying the second service provider that two service providers are required to approve the user data access request and prompting the second service provider to tap short-range transceiver 520 (in the illustrated example, short-range transceiver 520 may be a contactless card) to complete the approval process. Instructions 514 may be a push notification from server 110 (shown in FIGS. 1A and 1B-1C). In response to the tapping action, client device 501 may transmit user token 522 (from short-range transceiver 520) and the second service provider token to server 110.

[0075] 6A is a flowchart illustrating a method of data access control 600 according to one or more exemplary embodiments, with reference to the components and features described above, including but not limited to the figures and associated descriptions. The data access control method 600 may be performed by an application 102 running on a client device 101 associated with a (first) service provider. A short-range transceiver 105 is associated with a user.

[0076] At block 610, application 102 may cause client device 101 to display a user data access request screen (as shown in and described above with reference to FIG. 4). The user data access request screen may include instructions to tap short-range transceiver 105 on / against client device 101 to initiate a data access key request. As described above with reference to FIG. 4, short-range transceiver 420 (and thus short-range transceiver 105) may be a contactless card.

[0077] At block 620 , a tapping action may be detected between the short-range transceiver 105 and the client device 101 .

[0078] At block 630, a user token 107 may be received from the short-range transceiver 105. Receipt of the user token 107 may be in response to the tapping action of block 620. The user token 107 may include a user identifier. In some exemplary embodiments, the user token 107 may include a user key associated with the user.

[0079] In block 640, the user token 107 and the service provider token (associated with the service provider) may be transmitted to the server 110 along with a data access key request to obtain a key for decrypting encrypted personal user data received (or to be received) from the short-range transceiver 105. The transmission of the user token 107, the service provider token, and the data access key request to the server 110 may be in response to the tapping action of block 620.

[0080] At block 650 , a data access key may be received from the server 110 .

[0081] At block 660, the encrypted private user data may be received from the short-range transceiver 105. As mentioned above, the encrypted private user data may be received at any time during the process.

[0082] At block 670, the data access key may be used to decrypt the encrypted personal user data. As discussed above, in some embodiments, the application 102 may cause the personal user data to be displayed on the client device 101. In some embodiments, the application 102 may be permitted to store the personal user data on the client device 101 for retrieval based on a time limit or a limited number of uses.

[0083] 6B is a flowchart illustrating a method of data access control 600 according to one or more exemplary embodiments, with reference to the components and features described above, including but not limited to the drawings and related descriptions. The features described in FIG. 6B may be in addition to the features referenced in FIG. 6A. The description of the blocks referenced in FIG. 6A will not be repeated here. As described above with reference to FIG. 6A, the data access control method 600 may be performed by an application 102 executing on a client device 101 associated with a (first) service provider. A short-range transceiver 105 is associated with the user.

[0084] A memory located in the short-range transceiver 105 (such as memory 302 shown in FIG. 4) may include basic user data, such as name, gender, date of birth, etc. This basic user data may be a subset of the types of data included in the personal user data, may be additional data, and / or may be data that is less likely to change (or less likely to change over time than other types of personal user data). In some exemplary embodiments, such as when the personal user data includes health data, the basic user data may include certain aspects of the health data, such as, for example, height, weight, allergies, prescriptions, DNR orders, etc. The types of information that may be included in the basic user data may be selectable by the user.

[0085] Basic user data is stored in short-range transceiver memory 302 and may be located, for example, in a data file identified by a particular memory location or file name.

[0086] Basic user data may be encrypted with a key such that it can be decrypted with a basic service provider key available to the service provider. The basic service key may be different from the data access key required to describe personal user data 305. In one or more embodiments, the basic service provider key may be available to the service provider and may be valid for a limited period of time, such as daily, weekly, monthly, or other basis. The basic service provider key may be common to all personnel associated with a particular service provider entity. The basic service provider key may be stored in database 130 or generated by the system based on the identity of the service provider. Storing the basic service provider key (or generating a key) by the system and pushing the key to client devices allows for access control and for access to be logged and tracked for audit purposes.

[0087] At block 690, the basic service provider key is received from the server. The basic service provider key may be requested and / or obtained at any time according to any agreement or protocol the service provider (or service provider entity) may have with system 100. For example, client device 101 may send a request for the basic service provider key to server 110 at intervals when a new key becomes available (e.g., daily, weekly, monthly, or on some other basis). Receiving the basic service provider key does not require the service provider to be in proximity of short-range transceiver 105, and the basic service provider key may be requested or received independently of any tapping action by short-range transceiver 105.

[0088] At block 692, the basic service provider key is stored in memory located on the client device 101 so that the service provider may later recall and use the basic service provider key.

[0089] At block 694, the encrypted basic user information may be received from the short-range transceiver 105 in response to a tap action between the short-range transceiver 105 and the client device 101, or may otherwise be received whenever the short-range transceiver 105 is within short-range wireless communication range of the client device 101.

[0090] At block 696, the encrypted basic user data may be decrypted using the basic service provider key. The application 102 may cause the basic user data to be displayed on the client device 101. In some embodiments, the application 102 may be permitted to store the basic user data on the client device 101 for retrieval on a time-limited or limited-use basis. In an exemplary embodiment, the basic user data may be stored on the transceiver 105 in unencrypted format. In an exemplary embodiment, the basic user data may be received by the client device 101 in unencrypted form and accessed without the need for the basic service provider key. Whether the basic user data is stored or provided in unencrypted format may be determined by the user.

[0091] 7A is a flowchart illustrating a method of data access control 700 according to one or more exemplary embodiments, with reference to the components and features described above, including but not limited to the figures and associated descriptions. The data access control method 700 may be performed by a processor 120 communicating with a client device 101 associated with a first service provider and / or a client device 103 associated with a second service provider via a server 110.

[0092] At block 710, a data access key request may be received from a client device 101 associated with a first service provider, requesting a data access key that enables decryption of encrypted personal user data along with a user token 107 and a service provider token (associated with the first service provider). The token 107 may include a user identifier. In some exemplary embodiments, the token 107 may include a user key associated with the user. In some exemplary embodiments, the service provider token may include a first service provider key.

[0093] At block 720, the sender of the data access key request may be identified as the first service provider based on the service provider token. In some example embodiments, if the service provider token includes a first service provider key associated with the first service provider, the first service provider key may be used to authenticate the first service provider.

[0094] At block 730, the user may be identified based on the received user token 107. In some example embodiments, if the token 107 includes a user key associated with the user, the user key may be used to authenticate the user.

[0095] At block 740, the processor may verify that the first service provider is authorized to receive access to the personal user data (and therefore authorized to obtain the data access key). Authorization may be based on the identity of the service provider, or the identity of the user, or both, and may include retrieval of information from database 130.

[0096] At block 750, a data access key may be sent to the client device 101 associated with the service provider. As described above, the data access key may be stored in the database 130 or may be generated based on the user key, the first service provider key, or a combination of the user key and the first service provider key.

[0097] 7B is a flowchart illustrating a method of data access control 701 according to one or more exemplary embodiments, with reference to the components and features described above, including but not limited to the drawings and associated description. The features described in FIG. 7B may be in addition to the features referenced in FIG. 7A. The description of the blocks referenced in FIG. 7A will not be repeated here. As described above with reference to FIG. 7A, the data access control method 700 may be performed by a processor 120 in communication with a client device 101 associated with a first service provider and / or a client device 103 associated with a second service provider via a server 110.

[0098] According to the method of Figure 7B, block 750 (referenced in Figure 7A) is not executed in the sequence shown in Figure 7A. Instead, referring to Figure 7B, at block 750', it is determined that service provider access to personal user data requires two-person approval.

[0099] At block 760, a notification is sent to the client 101 associated with the first service provider that dual approval requires that the second service provider must approve the data access key request.

[0100] At block 765, a data access key request may be received from a client device 103 associated with a second service provider, along with the user token and the second service provider token. The second service provider token may include a second service provider key.

[0101] At block 770, it may be determined that the data access key request from the second service provider client device 103 corresponds to a data access key request previously received from the first service provider client device 101.

[0102] At block 775, an approval notice may be sent to the client device 103 of the second service provider requesting approval of the data access key request made by the first service provider.

[0103] At block 780, an approval message may be received from the client device 103 of the second service provider indicating approval by the second service provider of the data access key request made by the first service provider.

[0104] At block 785, the data access key may be sent to the client device 101 associated with the first service provider. As described above, the data access key may be stored in the database 130 or may be generated based on the user key, the first service provider key, or a combination of the user key and the first service provider key, or a combination of the user key, the first service provider key, and the second service provider key.

[0105] 7A and 7B.

[0042] FIG. 7C is a flowchart illustrating a method of data access control 702 according to one or more exemplary embodiments, with reference to the components and features described above, including but not limited to the figures and associated descriptions. The features described in FIG. 7C may be in addition to the features referenced in FIG. 7A or 7B. The descriptions of the blocks referenced in FIG. 7A and 7B will not be repeated here. As described above with reference to FIG. 7A and 7B, the data access control method 700 may be performed by a processor 120 in communication with a client device 101 associated with a first service provider and / or a client device 103 associated with a second service provider via a server 110.

[0106] At block 790, a request for a basic service provider key is received from the client device 101. As discussed above, the basic service provider key may be requested at any time according to any agreement or protocol the service provider (or service provider entity) may have with the system 100. Requesting the basic service provider key does not require the service provider to be in proximity of the short-range transceiver 105, and the basic service provider key may be transmitted to the client device 101 independent of a tapping operation on the short-range transceiver 105.

[0107] At block 792, the processor may verify that the service is authorized to receive access to the basic user data (and therefore authorized to obtain the basic service provider key). Authorization may be based on the identity of the service provider and may include retrieving information from database 130.

[0108] At block 794, a basic service provider key may be sent to the client device 101 associated with the service provider. The service provider key may be stored in the database 130 or may be generated by the system based on the identity of the service provider.

[0109] FIG. 8 shows a diagram illustrating a data access control system 800 according to one or more exemplary embodiments. FIG. 8 references similar components of system 100 of the exemplary embodiment shown in FIG. 1A, and descriptions of those components will not be repeated here. In addition to the components associated with system 100 shown in FIG. 1A and described above, system 800 may include a data repository 801. Data repository 801 may include a database having some or all of the same or similar structure, functionality, or features as described above for database 130. The data repository may include or incorporate a server having some or all of the same or similar structure, functionality, or features as described above for server 110. The data repository may also include or incorporate a processor having some or all of the same or similar structure, functionality, or features as described above for processor 120. The data repository is configured to store personal user data, such as the type of personal user data described above with respect to personal user data 305 of FIG. 3. The data repository may store the personal user data in an encrypted format or encrypt the personal user data before transmitting it to authorized service providers. The data repository 801 may be operated by the same or related entity as the operating system 100, or may be operated by a third party.

[0110] In operation, system 800 may perform all or many of the same functions performed by components of system 100, as described above, to process requests for data access keys to access personal user data. Once system 800 verifies that the service provider is authorized to receive access to the personal user data, processor 120 may generate a link to a data repository where the personal user data is stored. In an exemplary embodiment, processor 120 may provide information (e.g., an electronic address of data repository 801) in addition to or instead of a link to data repository 801.

[0111] The processor 120 may retrieve the data access key or generate the data access key as described above (including, for example, generating it based on the user key or based on the user key and the service provider key). The processor 120 may send the client device 101 the data access key and a link to the data repository 801 where the personal user data may be located. Upon receiving the data access key and the link to the data repository 801, the client device 101 may retrieve the encrypted personal user data from the data repository 801 based on the link. For example, the client device 101 may send a request for the encrypted personal user data to the data repository 801 via the link and receive the encrypted personal user data from the data repository 801. Once the client device 101 obtains the encrypted personal user data, the client device 101 may use the data access key to decrypt the encrypted personal user data. Once the personal user data is decrypted, the client device 101 may access and use the personal user data as described above.

[0112] In some exemplary embodiments, data repository 801 may store the same personal user data that is stored on transceiver 105. In some exemplary embodiments, personal user data is stored in data repository 801 instead of being stored on transceiver 105. In some exemplary embodiments, personal user data may be stored in data repository 801 and only a limited set of user data (e.g., basic user data, etc.) may be stored on transceiver 105. In some exemplary embodiments, personal user data stored in data repository 801 may be updated. The updated personal user data may be stored in data repository 801 and transmitted to client device 101 in response to a request for personal user data.

[0113] The description of the embodiments in this disclosure provides non-limiting representative examples that refer to figures and numbers to particularly explain the features and teachings of different aspects of the present disclosure. It should be recognized that the described embodiments can be implemented separately or in combination with other embodiments from the description of the embodiments. Those skilled in the art who review the description of the embodiments should be able to learn and understand the different described aspects of the present disclosure. The description of the embodiments is intended to facilitate understanding of the present disclosure to the extent that other implementations not specifically described but within the knowledge of those skilled in the art who read the description of the embodiments are understood to be consistent with the application of the present disclosure.

[0114] Throughout the specification and claims, the following terms shall have at least the meaning expressly associated therewith, unless the context clearly dictates otherwise. The term "or" is intended to mean an inclusive "or." Furthermore, the terms "a," "an," and "the" are intended to mean one or more unless otherwise specified or clearly directed to the singular from the context.

[0115] In this description, many specific details have been set forth. However, it should be understood that implementations of the disclosed technology may be practiced without these specific details. In other instances, well-known methods, structures, and techniques have not been shown in detail so as not to obscure an understanding of this description. References to "some examples," "other examples," "one example," "examples," "various examples," "one embodiment," "embodiments," "some embodiments," "exemplary embodiments," "various embodiments," "one implementation," "implementation," "exemplary implementation," "various implementations," "some implementations," etc., indicate that implementations of the disclosed technology so described may include particular features, structures, or characteristics, but not all implementations necessarily include the particular feature, structure, or characteristic. Furthermore, repeated use of the phrase "in one example," "in one embodiment," or "in one implementation" does not necessarily refer to the same example, embodiment, or implementation, although it may.

[0116] As used herein, unless otherwise specified, the use of ordinal adjectives "first," "second," "third," etc. to describe a common object merely indicates that different instances of a similar object are being referred to, and does not imply that the objects so described need be in any particular order, whether temporally, spatially, ranked, or otherwise.

[0117] While particular implementations of the disclosed technology have been described in connection with what are presently considered to be the most practical various implementations, it is to be understood that the disclosed technology is not to be limited to the disclosed implementations, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

[0118] This written description uses examples to disclose particular implementations of the disclosed technology, including the best mode, and also enables any person skilled in the art to practice particular implementations of the disclosed technology, including making and using any device or system, and performing any incorporated methods. The patentable scope of particular implementations of the disclosed technology is defined in the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have structural elements that do not differ from the literal language of the claims, or if they include equivalent structural elements that are substantially different from the literal language of the claims.

Claims

1. 1. A data access control system, comprising: The data access control system includes: a contactless card associated with a user, the contactless card comprising a processor, a memory, and a communications interface, the memory of the contactless card storing a user token, encrypted personal user data associated with the user, and basic user data associated with the user, the basic user data being encrypted with a basic service provider key; The data access control system further comprises: a server having a processor and a memory, the server being in data communication with a database and a client device; The server receiving a request from the client device for the user token, a service provider token, and a data access key for decrypting encrypted personal user data; Identifying a user based on the user token; identifying a service provider based on the service provider token; verifying that the service provider is authorized to access personal user data; Retrieving a user key from the database; generating a data access key based on the user key; transmitting the data access key to the client device; A data access control system configured to:

2. the request for the data access key is generated in response to a tapping action between the contactless card and the client device. The data access control system according to claim 1 .

3. the server is further configured to generate the base service provider key based on the identity of the service provider. The data access control system according to claim 1 .

4. The server further comprises: receiving a request for the basic service provider key; verifying that the service provider is authorized to receive the base service provider key; sending the basic service provider key to the client device; It is configured as follows: The data access control system according to claim 3 .

5. The basic service provider key is valid for only a predetermined period of time. The data access control system according to claim 4.

6. the server receives a request for the basic service provider key after the predetermined period has expired; The data access control system according to claim 5 .

7. the request for the basic service provider key is independent of the tapping action between the contactless card on the client device; The data access control system according to claim 5 .

8. After verifying that the service provider is not authorized to receive the basic service provider key, the server is further configured to send a rejection notice to the client device. The data access control system according to claim 4.

9. 1. A method for controlling data access, comprising: The method for controlling data access includes: receiving a request from a first client device for a data access key for decrypting encrypted personal user data stored on a user token, a service provider token, and a contactless card associated with the user; identifying a user based on the user token; identifying a service provider based on the service provider token; verifying that the service provider is authorized to access personal user data stored on the contactless card; retrieving a first service provider key associated with the service provider from a database; retrieving a user key associated with a user from the database; generating a data access key based on the user key and the first service provider key; transmitting the data access key to the first client device; Including, How to control data access.

10. The method for controlling data access further includes authenticating the user based on the user key. The method for controlling data access according to claim 9.

11. the request for the data access key is generated in response to a tapping action between the contactless card and the first client device. The method for controlling data access according to claim 9.

12. The method for controlling data access further comprises: receiving a second service provider key from the second client device; the data access key is generated based on the user key, the first service provider key, and the second service provider key; The method for controlling data access according to claim 9.

13. the second service provider key is transmitted by the second client device in response to a tapping action between the contactless card and the second client device. The method for controlling data access according to claim 12.

14. the service provider token includes a first service provider key; The method for controlling data access further includes authenticating the service provider based on the first service provider key. The method for controlling data access according to claim 9.

15. a server, The server includes a processor and a memory. the server is in data communication with a database and a client device; The server receiving a request from the client device for a user token, a service provider token, and a data access key for decrypting encrypted personal user data; Identifying a user based on the user token; identifying a service provider based on the service provider token; verifying that the service provider is authorized to access personal user data; Retrieving a user key from the database; generating a data access key based on the user key; transmitting the data access key to a client device; generating a base service provider key based on the identity of the service provider; receiving a request for the basic service provider key; verifying that the service provider is authorized to receive the base service provider key; sending the basic service provider key to the client device; It is configured as follows: server.

16. the server is further configured to record each transmission of the base service provider key; The server of claim 15.

17. The service provider's access to the personal user data is restricted by one or more data control parameters. The method for controlling data access according to claim 9.

18. The one or more data control parameters limit access by the service provider to the personal user data for a limited period of time.

20. The method for controlling data access according to claim 17.

19. The one or more data control parameters limit access by the service provider to the personal user data for a single use.

20. The method for controlling data access according to claim 17.

20. The one or more data control parameters permit the service provider to access the personal user data when the contactless card is within communication range of the client device.

20. The method for controlling data access according to claim 17.

Images