Systems and methods for authentication of access based on multi-data source information
First Claim
1. A method of authenticating account owners, the method comprising:
- receiving, at a database server, a plurality of participant files, wherein the plurality of participant files comprising at least one participant file from each of plurality of participant data sources, wherein, the plurality of participant files from the plurality of participant data sources containing current and accurate information of the account owners;
each participant file of the plurality of participant files comprises two or more participant data elements,each participant data element of the two or more participant data elements comprises participant data values including a participant account identifier that corresponds to one of a plurality of participant accounts maintained for one of the account owners and including participant account owner details that correspond to personally identifiable information about a corresponding account owner, andeach participant data element of the two or more participant data elements in a particular participant file from a particular participant data source corresponding to a participant account maintained by the particular participant data source;
extracting, at the database server, the participant data values from the two or more participant data elements from each of the plurality of participant files;
storing, by the database server, the participant data values extracted from the two or more participant data elements from each of the plurality of participant files in an account owner authentication database, wherein the account owner authentication database comprises a plurality of data element fields, and wherein each of the participant data values extracted corresponds to one of the plurality of data element fields;
periodically and automatically receiving, by the database server, a plurality of updated participant files, wherein the plurality of updated participants files comprising at least one updated participant file from each of the plurality of participant data sources, each updated participant file comprising at least one updated participant data element from a plurality of updated participant data elements;
in response to receiving the plurality of updated participant files, refreshing, by the database server, the account owner authentication database with the plurality of updated participant data elements;
wherein each updated participant file of the plurality of updated participant files is provided in a predetermined format to the database server on a predetermined schedule, the method further comprising;
receiving at the database server, a plurality of non-participant files, the plurality of non-participant files comprising at least one non-participant file from each of a plurality of non-participant data sources, wherein, the plurality of non-participant files from the plurality of non-participant data sources containing information that are not current and accurate about the account owners;
each non-participant file of the plurality of non-participant files comprises two or more non-participant data elements,each of the two or more non-participant data elements comprises non-participant data values including a non-participant account identifier that corresponds to one of a plurality of non-participant accounts maintained for one of the account owners and including non-participant account owner details that correspond to personally identifiable information about a corresponding account owner, andeach of the two or more non-participant data elements in a particular non-participant file from a particular non-participant data source corresponding to a particular non-participant account maintained by the particular non-participant data source;
extracting, at the database server, the non-participant data values from the two or more non-participant data elements from each of the plurality of non-participant files;
storing, by the database server, the non-participant data values extracted from the two or more non-participant data elements from each of the plurality of non-participant files in the account owner authentication database, wherein each of the non-participant data values extracted corresponds to one of the plurality of data element fields, wherein the plurality of data element fields comprises a non-participant flag field, and wherein each non-participant data element comprises a row in a table of the account owner authentication database having an indicator in the non-participant flag field,sporadically receiving, by the database server, at least one updated non-participant file from at least one non-participant data source, the at least one updated non-participant file comprising at least one updated non-participant data element, wherein the at least one updated non-participant data element is not provided in the predetermined format;
in response to receiving the at least one updated non-participant file, refreshing, by the database server, the account owner authentication database with the at least one updated non-participant data element;
receiving, at the database server a request for authentication of an account owner from an inquirer, the request comprising at least an account identifier and a data value;
in response to receiving the request, searching the account owner authentication database to determine whether a match is found for the account identifier and the data value received;
upon a match is found for both the account identifier and the data value, transmitting a response to the inquirer indicating a match is determined;
upon a match is not found for at least one of the account identifier and the data value, transmitting a response to the inquirer indicating a match is not determined; and
wherein the responses do not provide any account owner-specific data to the inquirer.
2 Assignments
0 Petitions
Accused Products
Abstract
An authentication method includes receiving a single electronic file of member data elements from multiple member data sources. The method can include extracting the member data elements from the single electronic file, populating an authentication database with the member data elements, and periodically receiving an update of the member data elements. The update can be used to refresh the authentication database. The method can include receiving non-member data elements from multiple non-member data sources, and updating the authentication database with the non-member data elements. The method can further include receiving a request for authentication for one or more queried data elements corresponding to a supplied identification data element. The method can include determining an authentication response for each of the queried data elements based on the authentication database. The method can further include transmitting the authentication response for each of the queried data elements to the requesting system.
-
Citations
13 Claims
-
1. A method of authenticating account owners, the method comprising:
-
receiving, at a database server, a plurality of participant files, wherein the plurality of participant files comprising at least one participant file from each of plurality of participant data sources, wherein, the plurality of participant files from the plurality of participant data sources containing current and accurate information of the account owners; each participant file of the plurality of participant files comprises two or more participant data elements, each participant data element of the two or more participant data elements comprises participant data values including a participant account identifier that corresponds to one of a plurality of participant accounts maintained for one of the account owners and including participant account owner details that correspond to personally identifiable information about a corresponding account owner, and each participant data element of the two or more participant data elements in a particular participant file from a particular participant data source corresponding to a participant account maintained by the particular participant data source; extracting, at the database server, the participant data values from the two or more participant data elements from each of the plurality of participant files; storing, by the database server, the participant data values extracted from the two or more participant data elements from each of the plurality of participant files in an account owner authentication database, wherein the account owner authentication database comprises a plurality of data element fields, and wherein each of the participant data values extracted corresponds to one of the plurality of data element fields; periodically and automatically receiving, by the database server, a plurality of updated participant files, wherein the plurality of updated participants files comprising at least one updated participant file from each of the plurality of participant data sources, each updated participant file comprising at least one updated participant data element from a plurality of updated participant data elements; in response to receiving the plurality of updated participant files, refreshing, by the database server, the account owner authentication database with the plurality of updated participant data elements; wherein each updated participant file of the plurality of updated participant files is provided in a predetermined format to the database server on a predetermined schedule, the method further comprising; receiving at the database server, a plurality of non-participant files, the plurality of non-participant files comprising at least one non-participant file from each of a plurality of non-participant data sources, wherein, the plurality of non-participant files from the plurality of non-participant data sources containing information that are not current and accurate about the account owners; each non-participant file of the plurality of non-participant files comprises two or more non-participant data elements, each of the two or more non-participant data elements comprises non-participant data values including a non-participant account identifier that corresponds to one of a plurality of non-participant accounts maintained for one of the account owners and including non-participant account owner details that correspond to personally identifiable information about a corresponding account owner, and each of the two or more non-participant data elements in a particular non-participant file from a particular non-participant data source corresponding to a particular non-participant account maintained by the particular non-participant data source; extracting, at the database server, the non-participant data values from the two or more non-participant data elements from each of the plurality of non-participant files; storing, by the database server, the non-participant data values extracted from the two or more non-participant data elements from each of the plurality of non-participant files in the account owner authentication database, wherein each of the non-participant data values extracted corresponds to one of the plurality of data element fields, wherein the plurality of data element fields comprises a non-participant flag field, and wherein each non-participant data element comprises a row in a table of the account owner authentication database having an indicator in the non-participant flag field, sporadically receiving, by the database server, at least one updated non-participant file from at least one non-participant data source, the at least one updated non-participant file comprising at least one updated non-participant data element, wherein the at least one updated non-participant data element is not provided in the predetermined format; in response to receiving the at least one updated non-participant file, refreshing, by the database server, the account owner authentication database with the at least one updated non-participant data element; receiving, at the database server a request for authentication of an account owner from an inquirer, the request comprising at least an account identifier and a data value; in response to receiving the request, searching the account owner authentication database to determine whether a match is found for the account identifier and the data value received; upon a match is found for both the account identifier and the data value, transmitting a response to the inquirer indicating a match is determined; upon a match is not found for at least one of the account identifier and the data value, transmitting a response to the inquirer indicating a match is not determined; and wherein the responses do not provide any account owner-specific data to the inquirer. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
9. A system for authenticating account owners, the system comprising:
-
one or more processors; and a memory communicatively coupled with and readable by the one or more processors and having stored therein processor-readable instructions which, when executed by the one or more processors, cause the one or more processors to; receive a plurality of participant files, wherein the plurality of participant files comprising at least one participant file from each of a plurality of participant data sources, wherein, the plurality of participant files from the plurality of participant data sources containing current and accurate information of the account owners; each participant file of the plurality of participant files comprises two or more participant data elements, each participant data element of the two or more participant data elements comprises participant data values including a participant account identifier that corresponds to one of a plurality of participant accounts maintained for one of the account owners and including participant account owner details that correspond to personally identifiable information about a corresponding account owner, and each participant data element of the two or more participant data elements in a particular participant file from a particular participant data source corresponding to a participant account maintained by the particular participant data source; extract the participant data values from the two or more participant data elements from each of the plurality of participant files; store the participant data values extracted from the two or more participant data elements from each of the plurality of participant files in an account owner authentication database, wherein the account owner authentication database comprises a plurality of data element fields, and wherein each of the participant data values extracted corresponds to one of the plurality of data element fields; periodically and automatically receive a plurality of updated participant files, wherein the plurality of updated participants files comprising at least one updated participant file from each of the plurality of participant data sources, each updated participant file comprising at least one updated participant data element from a plurality of updated participant data elements; in response to receiving the plurality of updated participant files, refresh the account owner authentication database with the plurality of updated participant data elements; wherein each updated participant file of the plurality of updated participant files is provided in a predetermined format to a database server on a predetermined schedule, and wherein the processor-readable instructions further cause the one or more processors to; receive a plurality of non-participant files, the plurality of non-participant files comprising at least one non-participant file from each of a plurality of non-participant data sources, wherein, the plurality of non-participant files from the plurality of non-participant data sources containing information that are not current and accurate about the account owners; each non-participant file of the plurality of non-participant files comprises two or more non-participant data elements, each of the two or more non-participant data elements comprises non-participant data values including a non-participant account identifier that corresponds to one of a plurality of non-participant accounts maintained for one of the account owners and including non-participant account owner details that correspond to personally identifiable information about a corresponding account owner, and each of the two or more non-participant data elements in a particular non-participant file from a particular non-participant data source corresponding to a particular non-participant account maintained by the particular non-participant data source; extract the non-participant data values from the two or more non-participant data elements from each of the plurality of non-participant files; store the non-participant data values extracted from the two or more non-participant data elements from each of the plurality of non-participant files in the account owner authentication database, wherein each of the non-participant data values extracted corresponds to one of the plurality of data element fields, wherein the plurality of data element fields comprises a non-participant flag field, and wherein each non-participant data element comprises a row in a table of the account owner authentication database having an indicator in the non-participant flag field, irregularly receive at least one updated non-participant file from at least one non-participant data source, the at least one updated non-participant file comprising at least one updated non-participant data element, wherein the at least one updated non-participant data element is not provided in the predetermined format; in response to receiving the at least one updated non-participant file, refreshing, by the database server, the account owner authentication database with the at least one updated non-participant data element; receive a request for authentication of an account owner from an inquirer, the request comprising at least an account identifier and a data value; in response to receiving the request, searching the account owner authentication database to determine whether a match is found for the account identifier and the data value received; upon a match is found for both the account identifier and the data value, transmitting a response to the inquirer indicating a match is determined; upon a match is not found for at least one of the account identifier and the data value, transmitting a response to the inquirer indicating a match is not determined; and wherein the responses do not provide any account owner-specific data to the inquirer. - View Dependent Claims (10, 11)
-
-
12. A computer-readable memory device having stored thereon processor-readable instructions which, when executed by one or more processors, cause the one or more processors to:
-
receive a plurality of participant files, wherein the plurality of participant files comprising at least one participant file from each of a plurality of participant data sources, wherein, the plurality of participant files from the plurality of participant data sources containing current and accurate information of account owners; each participant file of the plurality of participant files comprises two or more participant data elements, each participant data element of the two or more participant data elements comprises participant data values including a participant account identifier that corresponds to one of a plurality of participant accounts maintained for one of the account owners and including participant account owner details that correspond to personally identifiable information about a corresponding account owner, and each participant data element of the two or more participant data elements in a particular participant file from a particular participant data source corresponding to a participant account maintained by the particular participant data source; extract the participant data values from the two or more participant data elements from each of the plurality of participant files; store the participant data values extracted from the two or more participant data elements from each of the plurality of participant files in an account owner authentication database, wherein the account owner authentication database comprises a plurality of data element fields, and wherein each of the participant data values extracted corresponds to one of the plurality of data element fields; periodically and automatically receive a plurality of updated participant files, wherein the plurality of updated participants files comprising at least one updated participant file from each of the plurality of participant data sources, each updated participant file comprising at least one updated participant data element from a plurality of updated participant data elements; in response to receiving the plurality of updated participant files, refresh the account owner authentication database with the plurality of updated participant data elements; wherein each updated participant file of the plurality of updated participant files is provided in a predetermined format to a database server on a predetermined schedule, and wherein the processor-readable instructions further cause the one or more processors to; receive a plurality of non-participant files, the plurality of non-participant files comprising at least one non-participant file from each of a plurality of non-participant data sources, wherein, the plurality of non-participant files from the plurality of non-participant data sources containing information that are not current and accurate about the account owners; each non-participant file of the plurality of non-participant files comprises two or more non-participant data elements, each of the two or more non-participant data elements comprises non-participant data values including a non-participant account identifier that corresponds to one of a plurality of non-participant accounts maintained for one of the account owners and including non-participant account owner details that correspond to personally identifiable information about a corresponding account owner, and each of the two or more non-participant data elements in a particular non-participant file from a particular non-participant data source corresponding to a particular non-participant account maintained by the particular non-participant data source; extract the non-participant data values from the two or more non-participant data elements from each of the plurality of non-participant files; store the non-participant data values extracted from the two or more non-participant data elements from each of the plurality of non-participant files in the account owner authentication database, wherein each of the non-participant data values extracted corresponds to one of the plurality of data element fields, wherein the plurality of data element fields comprises a non-participant flag field, and wherein each non-participant data element comprises a row in a table of the account owner authentication database having an indicator in the non-participant flag field, irregularly receive at least one updated non-participant file from at least one non-participant data source, the at least one updated non-participant file comprising at least one updated non-participant data element, wherein the at least one updated non-participant data element is not provided in the predetermined format; in response to receiving the at least one updated non-participant file, refreshing, by the database server, the account owner authentication database with the at least one updated non-participant data element; receive a request for authentication of an account owner from an inquirer, the request comprising at least an account identifier and a data value; in response to receiving the request, searching the account owner authentication database to determine whether a match is found for the account identifier and the data value received; upon a match is found for both the account identifier and the data value, transmitting a response to the inquirer indicating a match is determined; upon a match is not found for at least one of the account identifier and the data value, transmitting a response to the inquirer indicating a match is not determined; and wherein the responses do not provide any account owner-specific data to the inquirer. - View Dependent Claims (13)
-
Specification