Patent Application
20230177528
Aspects of the disclosure generally relate to methods and computer systems, including one or more computers particularly configured and/or executing computer software. More specifically, aspects of this disclosure relate to methods and systems for data insights from consumer accessible data.
Currently, there are many digital identity and internet challenges today. First, too many passwords leads to authentication providers brokering authentication and learning behaviors of consumers. Second, digital trust is one-way with consumers authenticating with a website, but the website does not authenticate with the consumer. This can lead to phishing. Third, there are data quality concerns and high-trust transaction needs (e.g. opening a bank account requiring strong know-your-customer (KYC) information). These concerns and needs may be expensive for in-house experts to prevent fraud and may require external data verification services. Lastly, data centralization may create attractive targets for hackers and provide high risk and expense for enterprises and organizations to protect.
As consumers continue to utilize digital environments and use digital identities, there will be a need to improve the decentralized digital identity architecture.
In light of the foregoing background, the following presents a simplified summary of the present disclosure in order to provide a basic understanding of some aspects of the invention. This summary is not an extensive overview of the invention. It is not intended to identify key or critical elements of the invention or to delineate the scope of the invention. The following summary merely presents some concepts of the invention in a simplified form as a prelude to the more detailed description provided below.
Aspects of the disclosure address one or more of the issues mentioned above by disclosing methods, computer readable storage media, software, systems, and apparatuses to provide data insights information to a third-party organization from consumer accessible data.
In some aspects, the system may include at least one processor and a memory unit storing computer-executable instructions. The system may be configured to, in operation, receive, at a data insights server, a query from a processor at a third-party organization in communication with the data insights server. The data insights server may be linked and in communication with a plurality of consumer devices from a plurality of consumers. The system may also be configured to, in operation, send, by the data insights server, the query from the third-party organization to each of the plurality of consumer devices from the plurality of consumers. The system may also be configured to, in operation, request, by the data insights server, a response to the query from each of the plurality of consumers to be sent directly to the third-party organization that requested the insight. Each individual response from the plurality of consumers may include one or more elements of consumer data from the consumer. The consumer data may be derived from consumer accessible data of the individual consumer in the plurality of consumers. The consumer accessible data may include verifiable credentials found in digital wallets of consumer, or data stored in the consumer device, or data configured to be accessible to the device and permitted by the consumer to be used in the processing of a data insight request.
In other embodiments, the query may comprise a plurality of consumer identity information and a plurality of consumer commerce information. The system may be configured to, in operation, compose, by the data insights server, the query from the third-party organization. The query may include selected fields for building a plurality of questions for the query. Additionally, the query includes one or more fields filled in with the consumer data from the consumer accessible data. The system may be configured to, in operation, verify, by the data insights server, the query from the third-party organization. The consumer accessible data may include one or more of social media information or personal cloud drive storage that the plurality of consumers chose to use in processing or the insight request. The system may be configured to, in operation, provide, by the data insights server, a reward to the each of the plurality of consumers for providing the response to the insight request. Additionally, the reward may comprise one or more of the following: a monetary reward, a consumer goods discount, a services discount, or a digital dividend.
Of course, the methods and systems of the above-referenced embodiments may also include other additional elements, steps, computer-executable instructions, or computer-readable data structures. In this regard, other embodiments are disclosed and claimed herein as well. The details of these and other embodiments of the present invention are set forth in the accompanying drawings and the description below. Other features and advantages of the invention will be apparent from the description, drawings, and claims.
The present invention is illustrated by way of example and is not limited by the accompanying figures in which like reference numerals indicate similar elements and in which:
In accordance with various aspects of the disclosure, methods, computer-readable media, software, and apparatuses are disclosed for providing data insights information to a third-party organization from consumer accessible data. The consumer accessible data may include verifiable credentials found in digital wallets of consumers. The digital wallets of the consumers may be located in one or more consumer devices of consumers. The third-party organization may request and/or compose a query comprising questions that can be answered or filled in with consumer accessible data. A data insights server may request a response to the query from the consumers, wherein the response is derived from the consumer accessible data, including any verifiable credential issued to the consumer. The data insights server may request each of the plurality of consumer devices to search the consumer accessible data for the response to the query. The consumer device may be requested, in operation, to send and provide the data insights response to the third-party organization directly.
The data insights server does not receive the data from the consumer. In this way, no consumer identifiable information is disclosed. The data insights server knows which consumers provide a response, but not the response nor the data used, and the third-party organization sees the responses but does not know which consumer provided the response. This three-way ‘triangle’ of privacy enables third-party organizations to get insights from a wide, more holistic data set related to consumers, without leaking identity of the consumer, while enabling a reward to be provided.
In the following description of the various embodiments of the disclosure, reference is made to the accompanying drawings, which form a part hereof, and in which is shown by way of illustration, various embodiments in which the disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural and functional modifications may be made.
In one or more arrangements, aspects of the present disclosure may be implemented with a computing device.
The I/O module 109 may be configured to be connected to an input device 115, such as a microphone, keypad, keyboard, touchscreen, and/or stylus through which a user of the digital identity device 100 may provide input data. The I/O module 109 may also be configured to be connected to a display device 117, such as a monitor, television, touchscreen, etc., and may include a graphics card. The display device 117 and input device 115 are shown as separate elements from the digital identity device 100; however, they may be within the same structure. On some digital identity devices 100, the input device 115 may be operated by users to interact with the data collection module 101, including providing user information and/or preferences, device information, account information, warning/suggestion messages, etc., as described in further detail below. System administrators may use the input device 115 to make updates to the data collection module 101, such as software updates. Meanwhile, the display device 117 may assist the system administrators and users to confirm/appreciate their inputs.
The memory 113 may be any computer-readable medium for storing computer-executable instructions (e.g., software). The instructions stored within memory 113 may enable the digital identity device 100 to perform various functions. For example, memory 113 may store software used by the digital identity device 100, such as an operating system 119 and application programs 121, and may include an associated database 123.
The network interface 111 may allow the digital identity device 100 to connect to and communicate with a network 130. The network 130 may be any type of network, including a local area network (LAN) and/or a wide area network (WAN), such as the Internet, a cellular network, or a satellite network. Through the network 130, the digital identity device 100 may communicate with one or more other computing devices 140, such as laptops, notebooks, smartphones, tablets, personal computers, servers, vehicles, home management devices, home security devices, smart appliances, etc. The computing devices 140 may also be configured in a similar manner as digital identity device 100. In some embodiments the digital identity device 100 may be connected to the computing devices 140 to form a “cloud” computing environment.
The network interface 111 may connect to the network 130 via communication lines, such as coaxial cable, fiber optic cable, etc., or wirelessly using a cellular backhaul or a wireless standard, such as IEEE 802.11, IEEE 802.15, IEEE 802.16, etc. In some embodiments, the network interface 111 may include a modem. Further, the network interface 111 may use various protocols, including TCP/IP, Ethernet, File Transfer Protocol (FTP), Hypertext Transfer Protocol (HTTP), etc., to communicate with other computing devices 140.
The disclosure is operational with numerous other general purpose and/or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with the disclosure include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable user electronics, network PCs, minicomputers, mainframe computers, mobile telephones, smart phones, and distributed computing environments that include any of the above systems or devices, and the like.
Aspects of the disclosure may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The disclosure may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The following is a list of general definitions that may be known and used in the art for digital identity and/or verifiable credentials.
Verifiable Digital Credential or Verifiable Credential: A digitally signed tamperproof set of data (claims) containing information about a person, entity, or thing, as defined by the World Wide Web Consortium (W3C) Verifiable Credentials Data Model specification.
Decentralized Identifier (DID): A globally unique identifier developed specifically for decentralized systems as defined by the W3C DID specification. DIDs enable interoperable decentralized Digital Identity management. A DID is associated with exactly one DID Document.
DID Document: The machine-readable document to which a DID points as defined by the W3C DID specification. A DID document describes the Public Keys, Service Endpoints, and other metadata associated with a DID. A DID Document is associated with exactly one DID.
Claim: A single piece of information claimed about a person, entity, or thing.
Digital Identity Agent: A software application (agent) that can be used by its owner to issue, hold, or verify verifiable digital credentials and securely communicate with other digital identity agents according to well-defined protocols
Digital Wallet: Another name given a digital identity agent, implemented as a mobile app, that belongs to an individual consumer.
Connection: A secure, mutually-authenticated communication channel between two digital wallets
Credential Issuer: An entity (person, organisation, business etc.) that issues verifiable digital credentials from their wallet to the holder's wallet. Issuers would normally be an organisation that is trusted to some degree and therefore their issued credentials are deemed trustworthy to some degree
Credential Holder: The entity that receives an issued verifiable digital credential. The holder can later share elements of the stored credentials, or create a cryptographic proof that can be used in response to a request, without revealing the underlying data
Credential Verifier: An entity that receives cryptographic proofs or credential elements from a holder. They verify the presented data/proof by checking a public ledger to ensure the digital signatures of the issuer and holder are valid and that the credentials have not been revoked
Proof Request: A request originating from a verifier asking for credentials or a proof from a holder's wallet. In its simplest form it is a request for data, but could also be a request to prove that a person is at least 21 years of age
Cryptographic Proof: This is what the holder presents to the verifier in response to a proof request and is used by the ‘verifier’ to check that signatures are correct, and the credential has not been revoked.
As illustrated in
As illustrated at 250, a third-party business or organization 230 may request information regarding a plurality of consumers 220 through a data insights server 210. The requested information may be derived from consumer accessible data, such as physical appearance, job title, name, email address, physical home address, social security number, age, birth place, birth date, address history, employment information, employment history, college or school degree, graduation date, college or school history, utilities, financial information, home ownership, employment information, etc. The requested information may also include other consumer-specific commerce information, such as where the consumers shop, how often they shop, shopping habits, purchases, etc. The data insights server 210 may compose a query based on the information requested by the third-party organization 230. The third-party organization 230 may draft the query for the requested information through the data insights server 210. The query may contain a number of questions that may be answered by information available in verifiable credentials from the consumers. The insights server 210 may approve or deny the insight request proposed by the third-party organization 230. If approved, the data insights server will make available the insight request to a plurality of consumers.
As illustrated at 252, the data insights server 210 may make available the query and/or questions to the consumers 220. The data insights server 210 may make available the insight request from the third-party organization 230 to each of the plurality of consumer devices 226 and/or digital wallets 228 from the group of consumers 220. The data insights server 210 may then search each of the plurality of consumer devices. The consumer device 226 may determine whether the consumer data restrictions set by the consumer permit the consumer device 226 to create a response to the insight request. The individual response generated by a single device may include one or more elements of consumer data 222 from only the data accessible to the individual device. The consumer data 222 may be derived from consumer accessible data 224 found in and/or accessible to the consumer devices 226. The consumer data 222 may also be derived from a software agent operating on behalf of the consumer, within the rules and/or restrictions set by the consumer on any of the consumer devices, such as for example on a personal data cloud. The consumer data 222 may also be derived from the verifiable credentials in each of the digital wallets 228 of the individual consumer 220.
In an embodiment, the consumer 220 may provide automatic consent for one or more elements of consumer data 222. When the consumer 220 provides automatic consent, one or more of the elements of consumer data 222 from the consumers 220, through the consumer accessible data 224 and/or the verifiable credentials, is automatically included in the set of data available to the processing of the insight request on the consumer device. The consumer 220 may control all consumer data within the consumer accessible data 224 and/or the verifiable credentials and the consumer devices 226 and/or the digital wallets 228. The consumer 220 may also control whether to participate and/or what level of intervention regarding the responses to the queries for consumer data 222 and consumer information from the consumer accessible data 224 and/or the verifiable credentials and the consumer devices 226 and/or the digital wallets 228.
As illustrated at 254, the data insights processor on the consumer device 226 may send a data insight response directly to the third-party organization 230. The third-party organization 230 may see only the answers to the query in the form of a response provided by a consumer device 226. The third-party organization 230 may not see any consumer data sources or know the identity of who provided any of the answers to the query. The requestor or third-party organization 230 may never see any of the consumer data 222 other than what is provided in the response 254.
Further, at 254, only the data insight response is shared by the consumer with the third-party organization 230. A notification that a response was sent to the third-party organization 230 is registered with the data insights server 210. The requestor or third-party organization 230 may see the response and may not receive any identifier that can be traced to the consumer 220 directly.
Further, at 254, a system component on the consumer device 226 (e.g., a mobile phone application or an application deployed to a consumer personal online data store) may process the insight request by determining which data could be used and are authorized for use and then determining the insight result. The result may then only be sent to the insight requestor, the third-party organization 230, and would not be sent to the data insights server 210. The consumer device 226 may send a notification to the data insights server 210 to register that the consumer response was sent to the third-party organization 230. The data insights server 210 may then use this register of responses to compensate the consumer, and to bill the insight requestor or the third-party organization 230.
Further, the processing of data insight requests may be performed by any device that the consumer authorizes, i.e., it is not restricted to only mobile devices and may include software agents/programs running on behalf of a consumer in a cloud environment or other non-mobile device.
The data insights server 210 may reside either remotely or local to the user mobile computing device, or via the user computing device. If the data insights server 210 resides local to the user mobile computing device, or via the user computing device, the data insights server 210 may be integrated with the user mobile computing device, or via the user computing device via an application or other program.
The data insights server 210 may possess many of the same hardware/software components as the digital identity device 100 shown in
Additionally, the data insights server 210 may include a machine learning algorithm that may execute or operate on the data insights server 210. The data insights server 210 may utilize a machine learning algorithm for learning trends and improving queries, data collection, responses, consolidation, and any other facets of the data insights program from historical determinations. The machine learning algorithm may utilize one or more of a variety of machine learning architectures known and used in the art. These architectures can include, but are not limited to, neural networks (NN), recurrent neural networks (RNN), convolutional neural networks (CNN), transformers, and/or probabilistic neural networks (PNN), linear regression, random forest, decision trees, k-nearest neighbors, support vector machines (SVM), logistical regression, k-means clustering, association rules. RNNs can further include (but are not limited to) fully recurrent networks, Hopfield networks, Boltzmann machines, self-organizing maps, learning vector quantization, simple recurrent networks, echo state networks, long short-term memory networks, bi-directional RNNs, hierarchical RNNs, stochastic neural networks, and/or genetic scale RNNs. In a number of embodiments, a combination of machine learning architectures can be utilized, more specific machine learning architectures when available, and general machine learning architectures at other times can be used. Additionally, the machine learning algorithm may use semi-supervised learning and/or reinforcement learning. Additionally, the machine learning may be achieved using federated learning and/or on-device prediction techniques such that the consumer data is not disclosed to the data insights server 210. In this case, the machine learning algorithm is sent to the consumer device and the updates to the model are sent back to the insight server after the consumer device applies the consumer accessible data 222 to the model provided.
The steps that follow may be implemented by one or more of the components in
As illustrated in step 510, a data insights server may receive a query from a processor at a third-party organization. The third-party organization may be in communication with the data insights server. The data insights server may be linked and in communication with a plurality of consumer devices from a plurality of consumers. The data insights server may also be linked and in communication with a plurality of digital wallets from the plurality of consumers. Generally, the query comprises a request for specific consumer identity information and/or consumer commerce information that may be attainable through verifiable credentials. The query may include specific consumer identity information, such as physical appearance, job title, name, email address, physical home address, social security number, age, birth place, birth date, address history, employment information, employment history, college or school degree, graduation date, college or school history, utilities, financial information, home ownership, employment information, etc. The query may also include other consumer-specific commerce information, such as where the consumer shops, how often the consumer shops, shopping habits of the consumer, purchase history of the consumer, etc.
Additionally, the data insights server and/or third-party organization may compose the query. The data insights server may only allow selected fields for composing questions for the queries. The data insights server 210 will aim to preserve the anonymity of the consumer by checking the data fields required in current and past insight requests proposed by the third-party organization 230 such that correlation between responses to different queries would not permit the third-party organization 230 to identify any consumer providing a response to an insight request.
In step 520, the data insights server may verify the query from the third-party organization.
In step 530, the data insights server may send the query from the third-party organization to a plurality of consumer devices that are owned or held by a plurality of consumers. The consumer devices may include a mobile phone application that executes on the consumer device or may include any processor/system that the consumer has authorized and configured to participate in the data insights system. The consumer devices may include an application deployed to a consumer personal online data store or personal computer.
In step 540, the data insights server may make available the insight request to consumers.
Any response to the insight request may include one or more elements of consumer data from the plurality of consumers. The consumer data may include consumer accessible data. The consumer data may include consumer accessible data on a consumer device. The consumer accessible data may include any data that the consumer can access, including their social media, personal files, or personal cloud drive storage, etc. The consumer accessible data may only include the data that the consumer explicitly chooses to include in the set of data that could contribute to answer any of the data insight questions. The one or more elements of consumer data may include, but not be limited to specific consumer identity information, such as physical appearance, job title, name, email address, physical home address, social security number, age, birth place, birth date, address history, employment information, employment history, college or school degree, graduation date, college or school history, utilities, financial information, home ownership, employment information, etc. The one or more elements of consumer data may also include, but not be limited to consumer-specific commerce information, such as where the consumer shops, how often the consumer shops, shopping habits of the consumer, purchase history of the consumer, etc. The consumer data may be derived from one or more verifiable credentials in each of the digital wallets of the plurality of consumers. The one or more elements of the consumer data derived from the consumer accessible data from the consumers may be automatically provided to the data insights server when the consumer provides automatic consent.
In step 550, the consumer device may search for consumer accessible data in response to the query. The consumer device may use software deployed to that device, such that the privacy of the consumer's data is maintained. In step 560, the response may be sent directly to the third-party organization and is not shared with the data insights server. The data insights server may receive notification of each consumer that contributed a response to each insight request so as to determine billing to the third-party organization and compensation to the consumer.
In step 570, the data insights server may provide a query response to the third-party organization based on the consolidated responses from the consumers. In step 580, the data insights server may provide a reward to the plurality of those consumers for providing insight requests. The reward may include one or more of the following: a monetary reward, a consumer goods discount, a services discount, or a digital dividend. Other rewards to consumers may be utilized in accordance with this invention.
In an example of the data insights server, a third-party business or organization may want to know how many people between the ages of 18-24 shop at a specific Sporting Goods store. The third-party business or organization may compose the query and submit it to the data insights server. The data insights server may approve or deny the request and if approved may make the request available to a plurality of the consumers. An application on the mobile device may check for active insight requests and determine using consumer privacy preferences if the request could be processed using consumer data available. This may include looking through the verifiable credentials on the consumer's digital wallet(s) for answers—i.e., looks to see if the consumer has verifiable credentials from the Sporting Goods store. The information may also be derived from other verifiable credentials in the consumer's digital wallet. Consumers may determine to check what information is being sent to the third-party organization if the consumer chooses to select this protection. The consumer may also set defaults as to what information can be queried and sent. The consumer may receive rewards for sharing their information regarding the Sporting Goods store.
Aspects of the invention have been described in terms of illustrative embodiments thereof. Numerous other embodiments, modifications, and variations within the scope and spirit of the appended claims will occur to persons of ordinary skill in the art from a review of this disclosure. For example, one of ordinary skill in the art will appreciate that the steps illustrated in the illustrative figures may be performed in other than the recited order, and that one or more steps illustrated may be optional in accordance with aspects of the invention.
