WO2001046862A1 - Data linking system and method using tokens - Google Patents
Data linking system and method using tokens Download PDFInfo
- Publication number
- WO2001046862A1 WO2001046862A1 PCT/US2000/034545 US0034545W WO0146862A1 WO 2001046862 A1 WO2001046862 A1 WO 2001046862A1 US 0034545 W US0034545 W US 0034545W WO 0146862 A1 WO0146862 A1 WO 0146862A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- data
- tokens
- token
- customer
- repository
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/02—Marketing; Price estimation or determination; Fundraising
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/242—Query formulation
- G06F16/2433—Query languages
- G06F16/2445—Data retrieval commands; View definitions
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99941—Database schema or data structure
- Y10S707/99943—Generating database or data structure, e.g. via user interface
Definitions
- the invention is directed to a system and method for linking data that pertains to like entities.
- the invention is directed to a system and method for linking data pertaining to consumers, businesses, addresses, occupancies, and households using permanent, universally unique tokens.
- This information is typically stored electronically as a series of records in a computer database, each record pertaining to a particular customer. Records are logical constructs that may be implemented in a computer database in any number of ways well known in the art. The database used may be flat, relational, or may take any one of several other known forms. Each record in the database may contain various fields, such as the customer's first name, last name, street address, city, state, and zip code. The records may also include more complex demographic data, such as the customer's marital status, estimated income, hobbies, or purchasing history.
- Businesses generally gather customer data from a multitude of sources. These sources may be internal, such as customer purchases, or external, such as data provided by information service providers.
- sources may be internal, such as customer purchases, or external, such as data provided by information service providers.
- a number of information service providers maintain large databases with broad-based consumer information that can be sold or leased to businesses ; for example, a catalog-based retail business may purchase a list of potential customers in a specific geographic area.
- Businesses with multiple, independent databases may find it particularly valuable to know who among their customers come to them for multiple services. For example, a bank may wish to offer an enhanced suite of banking services to a customer that maintains only $100 in his or her savings account, if the bank could also determine that this same individual maintains a $100,000 brokerage account. This information could also be valuable, for example, to take advantage of cross- selling opportunities and to assist the business in optimizing the mix of services to best serve its existing customer base.
- Linking all available data concerning each customer would also allow each of the business's divisions to have access to the most up-to-date information concerning each customer. For example, a customer may get married and relocate, then notify only one of the business's divisions concerning the change.
- Sue Smith residing in Memphis
- Sue Thompson residing in Minneapolis.
- the other systems would be unable to determine that "new" customer Sue Thompson in Minneapolis is the same person as existing customer Sue Smith in Memphis.
- One of the oldest methods used to combat this problem is simply to assign a number to every customer, and then perform matching, searching, and data manipulation operations using that number. Many companies that maintain large, internal customer databases have implemented this type of system.
- each customer number always stays the same for each customer, even when that customer changes his or her name or address.
- These numbers may be used internally, for example, for billing and for tracking packages shipped to that customer.
- the use of a customer identification number eliminates the potential ambiguities if, for example, the customer's name and address were instead used as identifiers.
- Financial institutions in particular have used personal identification numbers (PINs) to unambiguously identify the proper customer to which each transaction pertains.
- Customer number systems are inherently limited to certain applications. Customer identification numbers are not intended to manage a constantly changing, nationwide, comprehensive list of names and addresses. Companies maintaining these numbers are generally only interested in keeping up with their own customers.
- the assignment process for such numbers is quite simple-when a customer approaches the company seeking to do business, a new number is assigned to that customer.
- the customer numbers are not the result of a broad-based process capable of managing the address and name history for a given customer.
- the customer numbers are assigned based only on information presented to the business creating the numbers.
- the numbers are noi assigned from a multi-sourced data repository that functions independently of the company's day-to-day transactions.
- the purpose of such numbers is simply transaction management, not universal data linkage.
- Such numbers are also not truly permanent, since they are typically retired by the company after a period of inactivity. Again, since the focus of the customer number assignment scheme is merely internal business transactions, there is no reason to permanently maintain a number for which no transactions are ongoing. These numbers cannot be used externally to link data because every company maintains a different set of customer numbers.
- UPC universal product code
- bar codes The universal product code
- UPC Uniform Code Council, Inc.
- a database of these codes is made publicly available so that the codes can be used by everyone. Using this database, every retailer can track price and other information about each product sitting on its shelves.
- Today's product distribution chains also rely heavily on the UPC system to track products and make determinations concerning logistics and distribution channels.
- UPC system While the UPC system has been enormously successful, the system's usefulness is limited. To obtain a UPC number for a new product, a manufacturer first applies for a UPC number, the product and number are added to the UCC database, and then the manufacturer applies the proper bar coding to its products before they are distributed. There is no scheme for assigning UPC numbers to pre- existing products, and no scheme for matching UPC numbers to the products they represent. Also, since each UPC number represents a single, distinct item packaged for retail sale, there is no scheme for identifying the various elements of a particular product to which a single UPC number is assigned. The UPC system thus could not be used to link various pre-existing data pertaining to consumers and addresses.
- a final but vitally important issue raised by the use of any identification number system with respect to individuals is privacy.
- a company's internal-only use of a customer identification number raises few privacy concerns.
- the external use of a customer number or PIN with respect to an individual increases the risk that the individual's private data may be easily shared in an unauthorized or illegal manner. The potential for misuse thus makes customer number systems unacceptable solutions for an information service provider seeking to develop an externally-distributed linking system for data pertaining to the entire United States consumer population.
- the only comprehensive method to eliminate duplicates and link (or "integrate") customer data maintained on separate databases has historically been to rebuild the relevant databases from scratch. Since many such databases contain tens of millions of records, the cost of completely rebuilding the databases is often prohibitively expensive.
- these databases are constantly in flux as old customers leave, new customers take their place, and customer information changes; thus the rebuild procedure must be periodically repeated to keep all information reasonably current.
- deduping routines are necessarily complex, they must also be performed with great speed. These routines are used to dedupe databases having tens of millions of records. With such large databases, the software subroutine that performs the deduping function may be called millions of times during a single deduping session. Thus these subroutines must be executed on very fast, expensive computer equipment that has the necessary power to complete the deduping routine in a reasonable amount of time. Because duplicate elimination is so resource-intensive, such tasks are today performed only by information service providers or data owners that have access to the massive computing power necessary to efficiently perform these routines.
- deduping routines necessarily involve some guesswork.
- duplicate elimination is based on the available data, which may be incomplete.
- the results of duplicate elimination routines are thus only as good as the available information.
- no system can eliminate 100% of the duplicates in a customer database; inevitably, the resulting database will contain instances of multiple records for the same customer, and multiple customers merged into one record as if they were a single customer.
- the procedure by which an information service provider integrates a business's databases has been time consuming and labor intensive. Since a wide variety of database formats are in use, the information service provider must first convert the database source files to a standard format for processing. The information service provider then runs one of the complex deduping programs as explained above.
- the data in the business's databases may be augmented with external sources of information to improve the accuracy of the deduping routines.
- the resulting database file is then reformatted into the business's database file format to complete the process. This entire procedure requires significant direct involvement by the information service provider's technical personnel, which is an important factor in the cost of the service.
- a significant limitation of this data integration method is that each time the service is requested, the entire process must be repeated. Data integration cannot be performed for a single record at a time, or for only those records that have been updated. This is because the data integration process depends upon the comparison of all of the data records against each other to establish groupings of similar records. Although matching links are usually created during the comparison process, those links are temporary and are lost once the process is complete. The links must be recreated from scratch each time the se rvice is performed. It would be impossible to reuse these links since they are not unique across the universe of all possible customers, and are not maintained by the information services provider.
- One of the most significant limitations of the current data integration method is that it cannot be performed in real time; the process is only performed in batch mode.
- Real-time data integration would be highly desirable since it would allow a retailer or other data owner to provide an immediate, customized response to input for a particular customer. For example, when a particular customer visits a retailer's web site, it would be desirable to link all available information concerning that customer, and then display a web page that is particularly tailored to that customer's interests and needs. Another application would be to provide customized coupons or sales information in response to the "swiping" of a particular customer's credit card when a retail purchase is in progress.
- Prior-art systems to provide a customized response to customer input are based on the matching of internal customer numbers. For example, some grocery stores distribute "member" cards containing bar codes to identify a particular customer. When the customer presents his or her member card at the check-out line, the card's bar code is scanned to determine the customer's identification number. The grocer's data processing system then automatically consults its buying history database in order to print coupons that are tailored to that customer's particular buying habits.
- Record-at-a-time processing based on internal customer numbers has several important limitations. First, this system only works for established customers for whom a number has already been assigned. If a new customer enters the store, that customer must be issued a member card (and corresponding customer identification number) before the system will recognize the customer. Initially, the grocer would know nothing about this customer. In addition, this system's use of customer identification numbers would make it unacceptable for use externally, due to the individual privacy concerns discussed above.
- Still another limitation of traditional data integration methods is that they provide no means by which a business can remotely and automatically update or "enhance" the data it maintains for each customer when the data concerning that customer changes.
- the traditional, batch-mode method of providing update or enhancement data is laborious, and may require several weeks from start to finish.
- the company requesting data enhancement is required to build an "extract file" containing an entry for each record in its customer database.
- This extract file is stored on a computer-readable medium, such as magnetic tape, which is then shipped to the information service provider for enhancement. Since a wide variety of database formats are in use, the information service provider must first convert the extract file to the information service provider's internal format for processing.
- the information service provider then executes a software application that compares the information in the company's database against all of the information that the information service provider maintains.
- the update or enhancement data is then overlaid onto the company's standardized extract file.
- the present invention is directed to a system and method for using permanent
- tokens to create an unambiguous linking scheme to match related data. Tokens may be implemented as unique numbers that are used to tag all data pertaining to a particular entity. These tokens are created by an information services provider, and may be distributed externally for the use of its customers. Unlike the customer identification numbers discussed above, the creation of tokens is not dependent upon a customer approaching the data owner.
- the information services provider that creates the tokens may maintain databases with information pertaining to the entire United States population, and constantly monitors the population for changes of address, name, status, and other demographic data in order to keep the list of tokens current. New tokens are assigned as new entities are identified.
- the tokens are created only by a single central repository operated by the information services provider.
- Temporary tokens may be created initially when a new entity is encountered, so that the information services provider may collect additional data to confirm that the supposed new entity is not already in the database. Once the information services provider confirms that the entity is actually new, however, a permanent token will be assigned that will be used to link data pertaining to that entity for all time. Because even the information service provider's information will not be complete, it may be necessary to periodically perform token maintenance in the form of combining two or more tokens into a single token, or splitting a single token into two different tokens. This process may be performed simply by publishing a list of consolidated and split tokens that is transmitted to all token users. This maintenance method makes unnecessary the complete reprocessing of a database to keep tokens current.
- the central repository may create an identification class that contains all available data pertaining to each entity for which information is maintained.
- the purpose of the identification class is to link all available data concerning a particular entity using the appropriate token. Even though much of this information may never be distributed, it may still be used in the matching process to assure that the correct token is assigned to a customer's data in response to a data integration, update, or enhancement request.
- the identification class may include name aliases, common name misspellings, last name change history, address history, street aliases, and other relevant information useful for matching purposes.
- the identification-class structure enables far more accurate matching and "deduping" than previously possible; for example, by using known name aliases, the central repository may recognize that a customer's separate database records for "Sue C. Smith,” “Carol Smith,” and “Sue Thompson” each actually refer to the same person, and would accurately assign a single token to link all relevant information about this person.
- the tokens are permanent and are universally unique, they are not limited to use by a particular data provider, or to a particular matching session; instead, the tokens are specifically intended for external distribution to any owner of relevant data, and will never expire.
- the tokens can be used to rapidly compare, match, search, and integrate data from multiple internal databases, either in batch mode or real time, using as few as one record at a time.
- Different types of tokens may be used to link data relevant to, for example, customers, businesses, addresses, households, and occupancies.
- An occupancy token links information about a customer or business and the address at which that particular customer resides at a particular time.
- a household token links information about all persons who are determined to share a household.
- a series of linked address tokens can further be used to maintain an individual's address history. Using an address history, ambiguities caused by name similarity between individuals may be more easily resolved, and the correct token will be tagged to that individual's data despite a change in address.
- the present invention also uses tokens to greatly simplify the process of data integration where multiple databases are maintained.
- the data owner need only search each database for information that is linked by the token associated with the entity of interest. There is no need to perform complex matching algorithms designed to determine whether, for example, two customers about whom information is maintained on separate databases are in fact the same individual.
- the tokens thus enable the data owner to treat each of its physically remote databases as if they were a single "virtual" database in which ail information about a particular entity is readily accessible.
- the use of tokens for linking data also significantly reduces the privacy concerns related to data enhancement, data integration, and related data processing.
- update and enhancement requests may be transmitted to an information services provider as simply a list of tokens.
- the tokens themselves contain no information concerning the data to which they pertain. Thus anyone who clandestinely intercepts such a transmission would be unable to extract any private data from the transmission.
- the tokens are merely data links, and not PINs or customer identification numbers, there is no increased individual-privacy risk associated with the external use of the tokens.
- the tokens further allow real-time, record-at-a-time linking for the immediate collection of ail relevant data in response to customer input.
- the data owner is able to construct a "total customer view" that may be used, for example, to customize the interaction between the data owner and its customer. If multiple databases must be consulted to retrieve all relevant customer data, then each database need only be searched for data linked to the relevant token.
- the data owner can use the tokens to link all of its own data, or can link with data maintained by an information services provider to immediately enhance its data pertaining to a particular customer. Because the linking process is performed just at the moment when the customer input is received, the data retrieved will be the most recently updated customer information available.
- the linkage between the data owner's database and information provider's database may be by OLTP (on-line transactional processing) using the linking tokens.
- This linkage may also be used to perform "trigger notification.”
- Trigger notification is the automatic triggering of update messages to every linked database when new information is received about a particular entity. Using tokens, trigger notification may taken place almost instantaneously, allowing, for example, every division of a large retailer to take advantage of the latest information received from a customer.
- Another advantage of the record-at-a-time processing is that data may be "pushed" from the information services provider to its customers. For example, the information services provider may learn that a particular individual's name has changed.
- This change can be "pushed" to a customer's database automatically through the use of a message that contains the new information and the token used to link all data pertaining to this individual. Because the update process requires only the matching of tokens, the process may be performed automatically without direct intervention by either the information services provider or its customer.
- FIG. 1 is a diagram showing the structure of the data-linking tokens according to a preferred embodiment of the present invention.
- Fig. 2 is a table illustrating the relationship between customer, address, and occupancy tokens according to a preferred embodiment of the present invention.
- Fig. 3 is a diagram illustrating the results of applying the linking tokens to a retailer's customer database according to a preferred embodiment of the present invention.
- Fig. 4 is a diagram illustrating the procedure for applying linking tokens to a customer database according to a preferred embodiment of the present invention.
- Fig. 5 is a diagram showing the structure of the identification class object resident on the information service provider data repository according to a preferred embodiment of the present invention.
- Fig. 6 is a diagram illustrating the procedure for linking customer data despite an error in the address information according to a preferred embodiment of the present invention.
- Fig. 7 is a diagram illustrating the procedure for performing token maintenance by consolidating tokens according to a preferred embodiment of the present invention.
- Fig. 8 is a diagram illustrating the procedure for performing token maintenance by splitting tokens according to a preferred embodiment of the present invention.
- Fig. 9 is a diagram illustrating the difference between processing an initial assignment of tokens to a customer database and a subsequent update of token information to the same database according to a preferred embodiment of the present invention.
- Fig. 10 is a table of typical data for a retailer with several business divisions prior to tagging with tokens according to a preferred embodiment of the present invention.
- Fig. 11 is a table of typical data for a retailer with several business divisions after tagging with tokens according to a preferred embodiment of the present invention.
- Fig. 12 is a diagram illustrating a method of building a total customer view using tokens according to a preferred embodiment of the present invention.
- Fig. 13 is a diagram illustrating a method of responding to consumer input to build a customized web page using tokens according to a preferred embodiment of the present invention.
- Fig. 14 is a diagram illustrating a method of improving call center response using tokens according to a preferred embodiment of the present invention.
- Fig. 15 is a diagram illustrating "trigger notification" customer relationship management using tokens according to a preferred embodiment of the present invention.
- Fig. 16 is a diagram illustrating the use of "push" technology using tokens according to a preferred embodiment of the present invention.
- Each token 10 may be stored electronically as a number or code.
- Token 10 is made up of prefix 12 and unique number 14.
- Prefix 12 preferably has a decimal value between 0 and 255, and thus may be represented by a single byte on a computer storage medium.
- the value of prefix 12 represents the type of entity for which token 10 links all relevant information. For example, a prefix 12 value of "254" may indicate that token 10 is used to link information about a consumer, while a prefix value of "253" may indicate that token 10 is used to link information about an address.
- Unique number 14 preferably may be represented by four bytes on a computer storage medium, and thus may have a decimal value between 0 and 4,294,967,294. Unique number 14 must be unique for each token 10 that has the same prefix 12, such that no token 10 will be identical to any other token 10.
- unique number 14 is generated using counters, and is sequentially assigned to new tokens 10 as they are generated. Any alternative method may be used to generate unique number 14 so long as the uniqueness of each token 10 is maintained.
- prefix 12 and unique number 14 may be of any size, and may be combined in any order to form token 10.
- the invention is not limited to a token 10 in which prefix 12 necessarily precedes unique number 14; the term "prefix" should not be read in such a narrow fashion.
- Token 10 may also include additional fields.
- Fig. 2 illustrates the relationship between consumer, address, and occupancy tokens using a specific example.
- Table 16 shows data relative to a husband and wife, the first two rows showing their name and address data when they live in
- Input file 20 is generated which contains each record from the relevant database files maintained b) the data owner.
- Input file 20 may be drawn from a single database, or from multiple independently maintained databases.
- Input file 20 in the illustrated example shows information about the same customer that is drawn from three separately maintained databases.
- the first step in the token association process is to form input file 20 as described above.
- Input file 20 is then fed into matching software 22, which may be executed on computer equipment maintained by the information services provider, but may also be executed on the data owner's own equipment.
- Matching software 22 then compares data from input file 20 with data from repository 24 to find matches.
- Repository 24 which is maintained by the information services provider, contains broad-based information concerning consumers and addresses on a nationwide scale.
- Repository may be a single physical database, or may consist of a number of physically independent databases linked by a communications network.
- repository 24 will contain information pertaining to virtually all consumers living in the United States or other area of interest.
- information is stored in repository 24 in the form of identification class 30.
- Each identification class 30 contains all information available concerning a particular individual, which is linked using consumer token 26.
- identification class 30 may contain name history 32, which is a list of the current and former names used by the individual; address history 34, which is a list of addresses at which the individual has resided; and occupancy history 36, which includes the occupancy tokens 21 associated with each name/address correlation for a particular period of time.
- Address history 34 may be used to build occupancy history 36, since, as noted above, an occupancy is the combination of an individual's name at a particular time and the address at which that individual resided at that time.
- Address history 34 may also include an address token 28 for each address in address history 34.
- Name history 32 and address history 34 allow matching software 22 to perform correct matching of data with tokens 10 even when an individual has changed both his or her name and address.
- Identification class 30 may also contain various sorts of demographic information concerning the particular individual to which it pertains. This additional information may also be used by matching software 22 for comparison. Identification class 30 may also contain common name and address misspellings as part of or separate from name history 32 and address history 34. Referring again to Fig. 4, the process of attaching tokens to the corresponding data in input file 20 after matching software 22 has completed the matching process is described. As explained above, each identification class 30 includes a consumer token 26 and at least one address token 28. (Where identification class 30 contains past addresses in address history 34, additional address tokens 28 may be linked to those past addresses.) As a result of the execution of matching software 22, input file 20 is rewritten to include the correct consumer token 26 and address token 28 as part of each record.
- Result file 29 which consists of input file 20 augmented with consumer tokens 26 and address tokens 28, is then returned to the data owner. Duplicate elimination is automatically performed in this process, since the result file 29 will have identical consumer tokens 26 for each record that contains information referring to the same individual. For example, result file 29 contains records for "James L. Smith" and "Jimmy L. Smith," but since each record is matched to the same consumer token 26, the data owner may now easily determine that both records refer to the same customer. Input file 20 and result file 29 may be transmitted in any manner suitable for the transmission of electronic files.
- the files may be transmitted between the data owner and information service provider using FTP (file transfer protocol) techniques through a telecommunications network, or may be physically transferred on electronic storage media such as magnetic tape or disks.
- FTP file transfer protocol
- the matching software 22 relies upon the comprehensive data in repository 24 for matching, rather than on similarities contained within the input file 20 itself, there is no limit on the minimum size of input file 20.
- Input file 20 may be as small as a single record with no loss in the accuracy of the matching process.
- Erroneous input data 40 contains name and address information for a husband and wife.
- Erroneous input data 40 contains a typographical error pertaining to the husband; the street address of "210" has been transposed to "120.”
- street address "120" does in fact exist. Because the address is valid but is incorrect for this particular consumer, this error would ordinarily be difficult to resolve; for example, simply matching this data against a master address list would not reveal an error.
- repository data 42 contains the correct data, it would be difficult to match the data without tokens since the "120" street address would not be a part of the husband's address history stored in identification class 30.
- resulting data 49 may be delivered containing the corrected address information as found in repository 24, based on token linking.
- resulting data 49 may be delivered with additional address information missing from input data 40, such as, for example, an apartment number that was not included with erroneous input data 40.
- the present invention may be used to perform householding.
- a desired objective of many data processing systems is to determine how many customers share the same household. Definitions of a household may vary from business to business. One business may define a household as natural families residing at a single address. Another may consider two unrelated roommates to be; a single household. Still another business may treat legally separated couples who reside at separate addresses as a single household in some instances, and as separate households in others.
- identification class 30 to assign a common address token 28 to different customers as illustrated in Figs. 5 and 6, despite street name aliases and other problems, significantly increases the accuracy of householding data.
- Using the most common definition of household that is, persons who live at the same address, householding may be performed simply by accessing all data with a common address token 28.
- the concept of householding can be extended to other definitions by linking identification classes 30 on repository 24 based on other objective data contained in identification classes 30 which is pertinent to separated families, roommates/relative distinctions, name changes which result in common surnames, and similar issues.
- Tokens 10 with different prefixes 12 may be used to link data according to each household definition.
- a prefix 12 of "250” may be used for tokens 10 that are used to link all data according to the traditional definition of household, and a prefix 12 of "249" may be used to link all data according to the roommate/relative definition of household.
- Such tokens 10 may be returned as an additional linked token for each record in resulting data 49, as shown in Fig. 4.
- repository 24 contains comprehensive information on the entire population of interest (for example, consumers in the United States), it cannot possibly contain all desired information with respect to all such persons, since such information is constantly in flux. As repository 24 is presented with new consumers and addresses, it must assign a token to link information relevant to those entities. It may occur, however, that as more information is later gathered about that entity, that the entity is in fact an old entity that was already known but, based on the available information in repository 24, could not be resolved into a single entity. The solution to this problem is to consolidate the two tokens into a single token.
- token consolidation and splitting does not require the data owners who have already been supplied with tokens to rebuild or "retokenize" their database. Instead, these data owners are merely provided with an electronic file containing a table of token updates.
- repository 24 maintains an identification class 30 for a first consumer 50 and a second consumer 52. These two consumers have different consumer tokens "100" and "150" assigned to link data relevant to them.
- a new associative data item 54 is entered into repository 24, which indicates that first consumer 50 and second consumer 52 are in fact the same consumer.
- the result is to merge the identification classes 30 for these two consumers into a single identification class 30 that contains all information relevant to consumer 56.
- a single consumer token "100” is now used to link all of this information.
- the other token "150” is now permanently retired from the set of all tokens.
- consolidation message 58 informs the data owner that the retired token "150" must now be replaced wherever it occurs with token "100" that had been used with respect to this consumer.
- the data owner now need simply run a software routine that searches for all occurrences of the retired token and replace it with the new token.
- the information service provider can send consolidation messages 58 as soon as associative data item 54 is received, or it may send periodic consolidation messages 58 that reflect all token consolidations that have occurred since the last consolidation message 58 was sent.
- Repository 24 initially contains information that consumer 56 is a single individual, for which all relevant information is contained in an identification class 30, including the single consumer token 26 used to link data relevant to this consumer.
- Associative data item 54 is then received by repository 24, but in this case associative data item 54 indicates that consumer 56 is in fact two different consumers.
- a software routine is then performed to split the identification class 30 for consumer 56 into two identification classes, one for first consumer 50 and the other for second consumer 52. While existing consumer token 26 may be used to link data relevant to one of these entities, a new consumer token 26 must be assigned to link data relevant to the other consumer.
- split message 68 is published in a manner similar to that described above for consolidation message 58.
- Split message 68 and consolidation message 58 may be merged to form a single message that is periodically sent out to data owners. Additional information is required in the case of a split, however, since the data owner must know which data retains the old consumer token, and which data will be tagged with the new consumer token. Reprocessing will be necessary to determine if a specific occupancy is to be tagged with the new token.
- Fig. 9 the advantages of performing data updates using a preferred embodiment of the invention are described.
- the first step to apply the present invention to a data owner's data processing system is to overlay the tokens 10 onto the data owner's data, as explained above.
- customer data 70 contains records from four physically independent databases, totaling 23 million records.
- Customer data 70 is input into consolidation process 72 and token assignment 74 (these processes are performed by matching software 22, as discussed above, based on data from repository 24).
- consolidation process 72 may be skipped and data may be fed from each source in customer data 70 directly to token assignment 74.
- Update data 78 represents that new data that the data owner has acquired in the preceding month. This data may be, for example, new customers the data owner has acquired during the preceding month. In the example of Fig. 9, update data 78 contains only 1.5 million records from two different databases. Update data 78 is input to consolidation process 72 and token assignment 74 (or directly into token assignment 74) as described above with respect to the initial build, and then integrated with customer file 76. Since consolidation process 72 and token assignment 74 are based on information in repository 24, and not on name and address comparisons across all of customer data 70, it is not necessary to reprocess the entire file to perform the update procedure.
- update data 78 could be a file as small as a single record.
- update data 78 just as a new record is received, it is sent as update data 78 to the information service provider, which immediately runs matching software 22 to perform consolidation process 72 and token assignment 74, thereby allowing real-time update of customer file 76.
- More frequent updates will reduce the volume of each update, and thereby relieve computational resource bottlenecks caused by less frequent processing of large updates.
- more frequent or even real-time updates will allow the data owner to maintain the most accurate information concerning all of its customers.
- one application according to a preferred embodiment of the present invention is data integration. Many businesses today are finding it advantageous to implement
- CRM Customer Relationship Management
- the goal of a CRM plan is for the business to completely understand its relationship with any particular customer.
- CRM requires that a business integrate all information known about each customer, whether such information is derived from inside or outside sources. This integrated information would ideally be available in real time so that the business may respond immediately to interactions initiated by any given customer.
- CRM may include, for example, knowing all products and product lines of interest to the customer, knowing the customer's purchasing history with all of the business's various divisions, and knowing the customer's relevant demographic (or, in the case of a business, firmographic) information.
- businesses find that they are better able to serve their customers through sales and marketing efforts that are specifically tailored to the interests of a particular customer. Customers find this process desirable as well, since they are alerted to products and offers in which they are interested, but are not solicited to purchase those products or services in which they have not expressed an interest.
- the key element of any successful CRM plan is the creation of a "Total Customer View" regarding any particular customer.
- the total customer view consists of an assimilation of all relevant information for a customer, from any number of disparate information stores, arranged in a manner to facilitate CRM.
- the principal obstacle facing a business attempting to build a total customer view system is that the business's information stores usually contain overlapping information about the same customer that is not equally consistent, accurate, and current. As a result, information concerning the same individual may reside in multiple databases or information stores with various inconsistencies. Because each of these data stores may use a different customer numbering scheme, or may rely merely on name and address matching, successfully linking this data together using only internal information is difficult, and cannot be performed with a high level of accuracy.
- Fig. 10 provides an illustrative example of this problem.
- Each row of company data table 80 represents a record pulled from a different database maintained by one of a retailer's various divisions.
- Each column of company data table 80 represents a particular field in these records, such as name, address, and customer account number.
- the information in this case is pulled from four different databases maintained by the retailer — automotive services, home services, retail sales, and the sporting goods "special mailing list.”
- the records from each database actually represent the same individual, the variations in name spelling, the individual's change of address, and the different account numbers used by each division would make it impossible to match this data together using internally- generated matching routines. The retailer would thus be unable to determine that this is a single individual, rather than four different individuals, and would therefore be unable to build an accurate total customer view.
- linked data table 90 each record on the company's various databases has been augmented with the appropriate tokens.
- Repository 24 which contains all of the variant name spellings and address history for customer William F. Smith, will be able to resolve that each of these records contains information referring to the same individual.
- the retailer may quickly and easily link all of its data concerning this individual through a simple token matching process. The retailer can also quickly and easily link to information about this customer that is maintained by an external information services provider, thereby allowing update or enhancement of the retailer's data.
- FIG. 12 the method for constructing a total customer view for customer William F. Smith is illustrated.
- the information accumulated by each of the retailer's divisions has been tagged with the consumer token 26 for William F. Smith — this information is contained in home services database 100, retail sales database 102, and automotive services database 104.
- the retailer may search for all data relevant to customer William F. Smith merely by searching for the consumer token 26 used to link that data, and retrieving all records tagged with that token.
- the retailer can also connect to repository 24 maintained by the information service provider to pull additional information concerning customer William F. Smith as desired. Because this token- matching process is computationally simple, it may be performed in real time.
- the result is total customer view 101 , through which the retailer may immediately determine its total relationship with this customer.
- the total customer view 101 may, for example, enable the retailer to direct its marketing efforts toward this particular customer in a more efficient manner by concentrating on products and services that this customer is known to favor.
- FIG. 13 illustrates the example of a customer 103 contacting a large retailer through the retailer's Internet web site.
- customer 103 decides to order rain gutters for his home. He then accesses the Internet web site the retailer maintains to facilitate e-commerce, which is hosted on web server 108.
- the customer is prompted to enter his name and address by the software maintained on web server 108.
- Web server 108 determines the consumer token 26 used to link information concerning customer 103.
- interactive data access 109 may search all of the retailer's various databases for matches to this token, including home services database 100, retail sales database 102, and automotive services database 104. This data is then returned to web server 108. Again, since matching is performed using tokens, this process will return all relevant data concerning customer 103 regardless of whether there is a match between a particular record containing relevant information and the name and address entered by the customer in response to the query of web server 108.
- the token may be used to retrieve additiona information from an information services provider's repository 24 in real time through a connection with repository 24. Linkage with the repository 24 may preferably be by OLTP techniques.
- the combined data of the retailer and information services provider may then be used by web server 108 to immediately build a customized Internet web page for viewing by customer 103.
- This customized web page may, for example, display special promotions particularly of interest to that customer.
- This entire process may, in a preferred embodiment of the invention, be performed in real time and will thus not result in noticeable delay for customer 103.
- a data owner may provide a customized web page for viewing by customer 103 by sending customer 103's response to the query by web server 108 directly to an information service provider's repository 24.
- the information service provider uses this information, in conjunction with the data in repository 24, to find the appropriate consumer token 26 to match all relevant information about customer 103. If additional information from the information service provider is requested, that data can be returned along with the appropriate consumer token 26 to web server 108.
- This consumer token 26 may then be used to match all information the retailer maintains about customer 103 using interactive data access 109 as explained above.
- This aggregate of data may then be used by web server 108 to construct a customized web site for customer 103.
- This aggregate of data may also, in an alternative embodiment, be transmitted to an analytical modeling engine (not shown) to perform data mining and other analytical functions, the results of which may be returned to web server 108 to assist in constructing a customized web site for customer 103.
- the present invention may allow a retailer to use a customer transaction or input as an opportunity to update its data concerning that customer.
- customer 103 has recently moved from Jacksonville to Phoenix.
- Customer 103 decides that his new home needs rain gutters, and he attempts to order them over the Internet through the retailer's e-commerce web site.
- web server 108 prompts customer 103 for name and address information. None of the retailer's internal databases will contain customer 103's new address, and thus it may be difficult to accurately link all information about customer 103 without tokens.
- the name and address is sent to the information services provider, however, it may use repository 24 to return to web server 108 the correct consumer token 26 and address token 28 for customer 103, provided that the repository 24 has previously received data indicating the move.
- the retailer can then use token matching to retrieve all of its data that is relevant to this customer using data access routine 109, and can then use web server 108 to build a customized web page for customer 103 based on this information.
- the updated address information provided by customer 103 can be used by the retailer to later mail coupons and special offers directed to customer 103 at his correct address.
- Still another example will illustrate how tokens 10 facilitate another important aspect of customer relationship management. Referring now to Fig. 14, suppose that customer 103 calls service representative 105 to complain that the rain gutters he ordered were not delivered on time.
- Service representative 105 may then immediately call up all available information concerning customer 103 using interactive data access routine 109.
- service representative 105 will be able to determine that customer 103 has done substantial business with the retailer in the recent past, and usually purchases sporting goods.
- service representative 105 may determine that the best course of action is to offer customer 103 a coupon for a significant discount on his next sporting goods purchase.
- the etailer is thus able to determine the best method of retaining customer 103 in spite of a poor service event in one particular transaction.
- the present invention also may be used to perform trigger notification throughout the various databases maintained by a data owner. For example, this process is illustrated in Fig. 15 for a large financial institution.
- the financial institution maintains physically separate databases for its various operations, including legal services database 140, insurance database 141 , retail banking database 142, investment banking database 143, and corporate data warehouse 144.
- Broker 148 learns from customer 103 that he is planning to purchase a new home. This information may be valuable to other divisions of the financial institution, such as retail banking and legal, who may wish to offer their services to customer 103 in connection with this transaction.
- Broker 148 may enter this information into messaging system 146, which then uses matching tokens to immediately provide this information to legal services database 140, insurance database 141, retail banking database 142, investment banking database 143, and corporate data warehouse 144. Persons operating in the legal and retail banking divisions will now have access to this information, and may retrieve any additional information maintained about customer 103 through data integration using tokens as illustrated above.
- Still another application of the present invention is to update or enhance data on a customer file 76 not in response to input from the entity about which information is maintained, but instead as new information is added to the data service provider's repository 24.
- the new information may be automatically "pushed" to those data owners who maintain records concerning the entity to which the information pertains and who wish to receive this service.
- FIG. 16 an example of push technology using tokens is illustrated.
- repository 24 is updated with additional information about a particular customer in the form of update data 156.
- Retailer A also maintains information about the customer to which this data pertains on its customer file 76, which may be, for example, a database maintained at retailer A's home office data center.
- the information service provider Since retailer A has previously subscribed to the push service, the information service provider maintains retailer A tokens list 152, containing a list of all tokens 10 corresponding to entities for which retailer A desires push updates.
- the information service provider's monitor routine 150 checks retailer A token list 152 to determine if update data 156 should be pushed to customer file 76. Assuming that other data owners subscribe to the push service, monitor routine 150 would check the token list associated with each of these subscribers as well. This process may be performed quickly because monitor routine 150 need only compare the token in update data 156 with the tokens in each token list. Once monitor routine 150 finds a match in retailer A token list 152, it will then pass update data 156 to publish routine 154, which will then communicate update data 156 to retailer A's customer file 76.
- This communication may be by telephone line or any other means of transmitting data electronically.
- customer file 76 is updated customer list 158.
- retailer A may take advantage of the information service provider's vast resources and access to a nationwide database of information, while at the same time paying only for updates to data that is relevant to its business as reflected by that information maintained in customer file 76 and retailer A token list 152.
Abstract
Description
Claims
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
MXPA02006267A MXPA02006267A (en) | 1999-12-21 | 2000-12-19 | Data linking system and method using tokens. |
BRPI0016904A BRPI0016904B1 (en) | 1999-12-21 | 2000-12-19 | data binding system, method of integrating a plurality of data elements residing in a data storage system |
JP2001547309A JP4634685B2 (en) | 1999-12-21 | 2000-12-19 | Data linking system and method using tokens |
CA2395241A CA2395241C (en) | 1999-12-21 | 2000-12-19 | Data linking system and method using tokens |
AU24408/01A AU782174B2 (en) | 1999-12-21 | 2000-12-19 | Data linking system and method using tokens |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/469,096 | 1999-12-21 | ||
US09/469,096 US6523041B1 (en) | 1997-07-29 | 1999-12-21 | Data linking system and method using tokens |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2001046862A1 true WO2001046862A1 (en) | 2001-06-28 |
Family
ID=23862399
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US2000/034545 WO2001046862A1 (en) | 1999-12-21 | 2000-12-19 | Data linking system and method using tokens |
Country Status (8)
Country | Link |
---|---|
US (1) | US6523041B1 (en) |
EP (1) | EP1118948A3 (en) |
JP (1) | JP4634685B2 (en) |
AU (1) | AU782174B2 (en) |
BR (1) | BRPI0016904B1 (en) |
CA (1) | CA2395241C (en) |
MX (1) | MXPA02006267A (en) |
WO (1) | WO2001046862A1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6523041B1 (en) | 1997-07-29 | 2003-02-18 | Acxiom Corporation | Data linking system and method using tokens |
EP1661372A2 (en) * | 2003-09-06 | 2006-05-31 | Intrado, Inc. | Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores |
JP2009301577A (en) * | 2002-08-12 | 2009-12-24 | Acxiom Corp | Data linking system and method using encoded link |
Families Citing this family (181)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6732111B2 (en) | 1998-03-03 | 2004-05-04 | Siebel Systems, Inc. | Method, apparatus, system, and program product for attaching files and other objects to a partially replicated database |
EP1247221A4 (en) | 1999-09-20 | 2005-01-19 | Quintiles Transnat Corp | System and method for analyzing de-identified health care data |
US7428554B1 (en) | 2000-05-23 | 2008-09-23 | Ocimum Biosolutions, Inc. | System and method for determining matching patterns within gene expression data |
WO2002003219A1 (en) | 2000-06-30 | 2002-01-10 | Plurimus Corporation | Method and system for monitoring online computer network behavior and creating online behavior profiles |
JP2002056237A (en) * | 2000-08-14 | 2002-02-20 | Tsubasa System Co Ltd | Charge information processor and franchise system provided with the same |
US7363308B2 (en) * | 2000-12-28 | 2008-04-22 | Fair Isaac Corporation | System and method for obtaining keyword descriptions of records from a large database |
US7091882B2 (en) * | 2001-05-29 | 2006-08-15 | Terion, Incorporated | Automated exchange for determining availability of assets shareable among entities |
US20040044664A1 (en) * | 2001-07-10 | 2004-03-04 | Sabre Inc. | Systems and methods for applying customer DNA to airline service and customer relationship management environments |
US7533179B2 (en) | 2001-09-20 | 2009-05-12 | Hitwise Pty, Ltd. | Method and system for characterization of online behavior |
EA200400873A1 (en) * | 2001-12-28 | 2005-12-29 | Джеффри Джэймс Джонас | REAL-TIME DATA STORAGE |
WO2004107094A2 (en) * | 2002-01-25 | 2004-12-09 | Seurat Company | Data integration system and method for presenting 360° customer views |
US7716165B2 (en) * | 2002-02-12 | 2010-05-11 | Mantas, Inc. | Analysis of third party networks |
US7672945B1 (en) * | 2002-04-08 | 2010-03-02 | Oracle International Corporation | Mechanism for creating member private data in a global namespace |
US7096213B2 (en) * | 2002-04-08 | 2006-08-22 | Oracle International Corporation | Persistent key-value repository with a pluggable architecture to abstract physical storage |
US9400589B1 (en) | 2002-05-30 | 2016-07-26 | Consumerinfo.Com, Inc. | Circular rotational interface for display of consumer credit information |
US9710852B1 (en) | 2002-05-30 | 2017-07-18 | Consumerinfo.Com, Inc. | Credit report timeline user interface |
US8200622B2 (en) | 2002-05-31 | 2012-06-12 | Informatica Corporation | System and method for integrating, managing and coordinating customer activities |
US7039650B2 (en) * | 2002-05-31 | 2006-05-02 | Sypherlink, Inc. | System and method for making multiple databases appear as a single database |
EP1537475A2 (en) * | 2002-09-03 | 2005-06-08 | Sap Ag | Collaborative master data management |
US7792715B1 (en) | 2002-09-21 | 2010-09-07 | Mighty Net, Incorporated | Method of on-line credit information monitoring and control |
EP1563628A4 (en) * | 2002-11-06 | 2010-03-10 | Ibm | Confidential data sharing and anonymous entity resolution |
US7020804B2 (en) * | 2002-12-03 | 2006-03-28 | Lockheed Martin Corporation | Test data generation system for evaluating data cleansing applications |
US8620937B2 (en) * | 2002-12-27 | 2013-12-31 | International Business Machines Corporation | Real time data warehousing |
CN100541443C (en) * | 2002-12-31 | 2009-09-16 | 国际商业机器公司 | The method and system that is used for deal with data |
US7657540B1 (en) | 2003-02-04 | 2010-02-02 | Seisint, Inc. | Method and system for linking and delinking data records |
US7451113B1 (en) * | 2003-03-21 | 2008-11-11 | Mighty Net, Inc. | Card management system and method |
EP1631908A4 (en) * | 2003-03-24 | 2012-01-25 | Ibm | Secure coordinate identification method, system and program |
US7571172B2 (en) | 2003-05-06 | 2009-08-04 | Novell, Inc. | Methods, data stores, data structures, and systems for electronic identity aggregation |
US7647344B2 (en) * | 2003-05-29 | 2010-01-12 | Experian Marketing Solutions, Inc. | System, method and software for providing persistent entity identification and linking entity information in an integrated data repository |
US7756822B2 (en) | 2003-12-01 | 2010-07-13 | Sap Ag | Operational reporting architecture |
US20050144066A1 (en) * | 2003-12-19 | 2005-06-30 | Icood, Llc | Individually controlled and protected targeted incentive distribution system |
US8036907B2 (en) * | 2003-12-23 | 2011-10-11 | The Dun & Bradstreet Corporation | Method and system for linking business entities using unique identifiers |
US8095567B2 (en) | 2003-12-29 | 2012-01-10 | Myfamily.Com, Inc. | Providing alternatives within a family tree systems and methods |
GB0411198D0 (en) * | 2004-05-20 | 2004-06-23 | Gentronix Ltd | Genotoxic testing |
US8969008B2 (en) | 2004-05-20 | 2015-03-03 | Gentronix Limited | Genotoxic testing |
JP4348236B2 (en) * | 2004-06-04 | 2009-10-21 | 株式会社日立製作所 | Community inheritance method |
US8370437B2 (en) * | 2004-12-23 | 2013-02-05 | Microsoft Corporation | Method and apparatus to associate a modifiable CRM related token to an email |
US20060184584A1 (en) * | 2005-02-11 | 2006-08-17 | Microsoft Corporation | Contact merge auto-suggest |
US8175889B1 (en) | 2005-04-06 | 2012-05-08 | Experian Information Solutions, Inc. | Systems and methods for tracking changes of address based on service disconnect/connect data |
US7908242B1 (en) | 2005-04-11 | 2011-03-15 | Experian Information Solutions, Inc. | Systems and methods for optimizing database queries |
US20060238919A1 (en) * | 2005-04-20 | 2006-10-26 | The Boeing Company | Adaptive data cleaning |
US20060241983A1 (en) * | 2005-04-21 | 2006-10-26 | Valerie Viale | Customer centric travel system |
US7496588B2 (en) * | 2005-06-27 | 2009-02-24 | Siperian, Inc. | Method and apparatus for data integration and management |
WO2007081666A2 (en) | 2006-01-03 | 2007-07-19 | Siperian, Inc. | Relationship data management |
US7523121B2 (en) * | 2006-01-03 | 2009-04-21 | Siperian, Inc. | Relationship data management |
US20070214179A1 (en) * | 2006-03-10 | 2007-09-13 | Khanh Hoang | Searching, filtering, creating, displaying, and managing entity relationships across multiple data hierarchies through a user interface |
US8150803B2 (en) * | 2006-01-03 | 2012-04-03 | Informatica Corporation | Relationship data management |
US7580917B2 (en) | 2006-03-22 | 2009-08-25 | Prolific Publishing, Inc. | System and method for brokering information between a plurality of commercially distinct clients |
US7464101B2 (en) * | 2006-04-11 | 2008-12-09 | Alcatel-Lucent Usa Inc. | Fuzzy alphanumeric search apparatus and method |
US7542973B2 (en) * | 2006-05-01 | 2009-06-02 | Sap, Aktiengesellschaft | System and method for performing configurable matching of similar data in a data repository |
US7792864B1 (en) * | 2006-06-14 | 2010-09-07 | TransUnion Teledata, L.L.C. | Entity identification and/or association using multiple data elements |
US7747745B2 (en) | 2006-06-16 | 2010-06-29 | Almondnet, Inc. | Media properties selection method and system based on expected profit from profile-based ad delivery |
US8005759B2 (en) | 2006-08-17 | 2011-08-23 | Experian Information Solutions, Inc. | System and method for providing a score for a used vehicle |
US7912865B2 (en) * | 2006-09-26 | 2011-03-22 | Experian Marketing Solutions, Inc. | System and method for linking multiple entities in a business database |
CN101536024B (en) * | 2006-10-02 | 2016-10-26 | 塞戈米特公司 | Personalized consumer advertising is arranged |
US8874465B2 (en) | 2006-10-02 | 2014-10-28 | Russel Robert Heiser, III | Method and system for targeted content placement |
US8036979B1 (en) | 2006-10-05 | 2011-10-11 | Experian Information Solutions, Inc. | System and method for generating a finance attribute from tradeline data |
US8204831B2 (en) * | 2006-11-13 | 2012-06-19 | International Business Machines Corporation | Post-anonymous fuzzy comparisons without the use of pre-anonymization variants |
US20080120318A1 (en) * | 2006-11-21 | 2008-05-22 | Shmuel Zailer | Device, Method and Computer Program Product for Information Retrieval |
US9355273B2 (en) | 2006-12-18 | 2016-05-31 | Bank Of America, N.A., As Collateral Agent | System and method for the protection and de-identification of health care data |
US8606666B1 (en) | 2007-01-31 | 2013-12-10 | Experian Information Solutions, Inc. | System and method for providing an aggregation tool |
US20080208788A1 (en) * | 2007-02-27 | 2008-08-28 | International Business Machines Corporation | Method and system for predicting customer wallets |
US8285656B1 (en) | 2007-03-30 | 2012-10-09 | Consumerinfo.Com, Inc. | Systems and methods for data verification |
US7975299B1 (en) | 2007-04-05 | 2011-07-05 | Consumerinfo.Com, Inc. | Child identity monitor |
US7742982B2 (en) | 2007-04-12 | 2010-06-22 | Experian Marketing Solutions, Inc. | Systems and methods for determining thin-file records and determining thin-file risk levels |
US8204866B2 (en) * | 2007-05-18 | 2012-06-19 | Microsoft Corporation | Leveraging constraints for deduplication |
US20080294540A1 (en) * | 2007-05-25 | 2008-11-27 | Celka Christopher J | System and method for automated detection of never-pay data sets |
US8271477B2 (en) * | 2007-07-20 | 2012-09-18 | Informatica Corporation | Methods and systems for accessing data |
US8301574B2 (en) * | 2007-09-17 | 2012-10-30 | Experian Marketing Solutions, Inc. | Multimedia engagement study |
US9690820B1 (en) | 2007-09-27 | 2017-06-27 | Experian Information Solutions, Inc. | Database system for triggering event notifications based on updates to database records |
US20090089190A1 (en) * | 2007-09-27 | 2009-04-02 | Girulat Jr Rollin M | Systems and methods for monitoring financial activities of consumers |
US8055497B2 (en) * | 2007-11-02 | 2011-11-08 | International Business Machines Corporation | Method and system to parse addresses using a processing system |
US8127986B1 (en) | 2007-12-14 | 2012-03-06 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US9990674B1 (en) | 2007-12-14 | 2018-06-05 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US11669866B2 (en) | 2008-03-17 | 2023-06-06 | Segmint Inc. | System and method for delivering a financial application to a prospective customer |
US10885552B2 (en) | 2008-03-17 | 2021-01-05 | Segmint, Inc. | Method and system for targeted content placement |
US8825520B2 (en) | 2008-03-17 | 2014-09-02 | Segmint Inc. | Targeted marketing to on-hold customer |
US11663631B2 (en) | 2008-03-17 | 2023-05-30 | Segmint Inc. | System and method for pulling a credit offer on bank's pre-approved property |
US11120471B2 (en) | 2013-10-18 | 2021-09-14 | Segmint Inc. | Method and system for targeted content placement |
US11138632B2 (en) | 2008-03-17 | 2021-10-05 | Segmint Inc. | System and method for authenticating a customer for a pre-approved offer of credit |
US8234159B2 (en) | 2008-03-17 | 2012-07-31 | Segmint Inc. | Method and system for targeted content placement |
WO2009117322A2 (en) | 2008-03-17 | 2009-09-24 | Segmint Inc. | Method and system for targeted content placement |
US8266168B2 (en) | 2008-04-24 | 2012-09-11 | Lexisnexis Risk & Information Analytics Group Inc. | Database systems and methods for linking records and entity representations with sufficiently high confidence |
US8166071B1 (en) | 2008-05-22 | 2012-04-24 | Informatica Corporation | System and method for efficiently securing enterprise data resources |
US8224873B1 (en) | 2008-05-22 | 2012-07-17 | Informatica Corporation | System and method for flexible security access management in an enterprise |
US7853493B2 (en) * | 2008-06-18 | 2010-12-14 | Consumerinfo.Com, Inc. | Personal finance integration system and method |
US8312033B1 (en) | 2008-06-26 | 2012-11-13 | Experian Marketing Solutions, Inc. | Systems and methods for providing an integrated identifier |
US8285725B2 (en) | 2008-07-02 | 2012-10-09 | Lexisnexis Risk & Information Analytics Group Inc. | System and method for identifying entity representations based on a search query using field match templates |
US7991689B1 (en) | 2008-07-23 | 2011-08-02 | Experian Information Solutions, Inc. | Systems and methods for detecting bust out fraud using credit data |
US9256904B1 (en) | 2008-08-14 | 2016-02-09 | Experian Information Solutions, Inc. | Multi-bureau credit file freeze and unfreeze |
US8060424B2 (en) | 2008-11-05 | 2011-11-15 | Consumerinfo.Com, Inc. | On-line method and system for monitoring and reporting unused available credit |
US20100174638A1 (en) * | 2009-01-06 | 2010-07-08 | ConsumerInfo.com | Report existence monitoring |
US8639920B2 (en) | 2009-05-11 | 2014-01-28 | Experian Marketing Solutions, Inc. | Systems and methods for providing anonymized user profile data |
US20100332292A1 (en) | 2009-06-30 | 2010-12-30 | Experian Information Solutions, Inc. | System and method for evaluating vehicle purchase loyalty |
US8364518B1 (en) | 2009-07-08 | 2013-01-29 | Experian Ltd. | Systems and methods for forecasting household economics |
US20110137760A1 (en) * | 2009-12-03 | 2011-06-09 | Rudie Todd C | Method, system, and computer program product for customer linking and identification capability for institutions |
US9411859B2 (en) | 2009-12-14 | 2016-08-09 | Lexisnexis Risk Solutions Fl Inc | External linking based on hierarchical level weightings |
US8725613B1 (en) | 2010-04-27 | 2014-05-13 | Experian Information Solutions, Inc. | Systems and methods for early account score and notification |
RU2012152642A (en) * | 2010-05-07 | 2014-06-20 | Дзе Дан Энд Брадстрит Корпорейшн | IMPROVING A DATABASE REQUEST |
EP2569747A4 (en) | 2010-05-10 | 2015-11-04 | Segmint Inc | Consumer-specific advertisement presentation and offer library |
WO2011143166A1 (en) | 2010-05-10 | 2011-11-17 | Segmint Inc. | Targeted marketing with cpe buydown |
US9189505B2 (en) | 2010-08-09 | 2015-11-17 | Lexisnexis Risk Data Management, Inc. | System of and method for entity representation splitting without the need for human interaction |
US9152727B1 (en) | 2010-08-23 | 2015-10-06 | Experian Marketing Solutions, Inc. | Systems and methods for processing consumer information for targeted marketing applications |
US8639616B1 (en) | 2010-10-01 | 2014-01-28 | Experian Information Solutions, Inc. | Business to contact linkage system |
US20120089614A1 (en) * | 2010-10-08 | 2012-04-12 | Jocelyn Siu Luan Hamilton | Computer-Implemented Systems And Methods For Matching Records Using Matchcodes With Scores |
US8782217B1 (en) | 2010-11-10 | 2014-07-15 | Safetyweb, Inc. | Online identity management |
US8484186B1 (en) | 2010-11-12 | 2013-07-09 | Consumerinfo.Com, Inc. | Personalized people finder |
US9147042B1 (en) | 2010-11-22 | 2015-09-29 | Experian Information Solutions, Inc. | Systems and methods for data verification |
US8996548B2 (en) | 2011-01-19 | 2015-03-31 | Inmar Analytics, Inc. | Identifying consuming entity behavior across domains |
US8839390B2 (en) * | 2011-03-08 | 2014-09-16 | Microsoft Corporation | Grouping personal accounts to tailor a web service |
US8688589B2 (en) | 2011-04-15 | 2014-04-01 | Shift4 Corporation | Method and system for utilizing authorization factor pools |
US9256874B2 (en) | 2011-04-15 | 2016-02-09 | Shift4 Corporation | Method and system for enabling merchants to share tokens |
US9818111B2 (en) | 2011-04-15 | 2017-11-14 | Shift4 Corporation | Merchant-based token sharing |
US9607336B1 (en) | 2011-06-16 | 2017-03-28 | Consumerinfo.Com, Inc. | Providing credit inquiry alerts |
US9483606B1 (en) | 2011-07-08 | 2016-11-01 | Consumerinfo.Com, Inc. | Lifescore |
US8775299B2 (en) | 2011-07-12 | 2014-07-08 | Experian Information Solutions, Inc. | Systems and methods for large-scale credit data processing |
US10599620B2 (en) * | 2011-09-01 | 2020-03-24 | Full Circle Insights, Inc. | Method and system for object synchronization in CRM systems |
US10621206B2 (en) | 2012-04-19 | 2020-04-14 | Full Circle Insights, Inc. | Method and system for recording responses in a CRM system |
US9106691B1 (en) | 2011-09-16 | 2015-08-11 | Consumerinfo.Com, Inc. | Systems and methods of identity protection and management |
US8738516B1 (en) | 2011-10-13 | 2014-05-27 | Consumerinfo.Com, Inc. | Debt services candidate locator |
US11030562B1 (en) | 2011-10-31 | 2021-06-08 | Consumerinfo.Com, Inc. | Pre-data breach monitoring |
US9286578B2 (en) | 2011-12-23 | 2016-03-15 | Sap Se | Determination of a most suitable address for a master data object instance |
US8930363B2 (en) * | 2011-12-23 | 2015-01-06 | Sap Se | Efficient handling of address data in business transaction documents |
US9853959B1 (en) | 2012-05-07 | 2017-12-26 | Consumerinfo.Com, Inc. | Storage and maintenance of personal data |
US9779220B1 (en) * | 2012-09-28 | 2017-10-03 | EMC IP Holding Company LLC | Obscuring data using on-the-fly retokenizable tokens |
US8621244B1 (en) | 2012-10-04 | 2013-12-31 | Datalogix Inc. | Method and apparatus for matching consumers |
US9654541B1 (en) | 2012-11-12 | 2017-05-16 | Consumerinfo.Com, Inc. | Aggregating user web browsing data |
US8856894B1 (en) | 2012-11-28 | 2014-10-07 | Consumerinfo.Com, Inc. | Always on authentication |
US9916621B1 (en) | 2012-11-30 | 2018-03-13 | Consumerinfo.Com, Inc. | Presentation of credit score factors |
US10255598B1 (en) | 2012-12-06 | 2019-04-09 | Consumerinfo.Com, Inc. | Credit card account data extraction |
US10373194B2 (en) | 2013-02-20 | 2019-08-06 | Datalogix Holdings, Inc. | System and method for measuring advertising effectiveness |
US9697263B1 (en) | 2013-03-04 | 2017-07-04 | Experian Information Solutions, Inc. | Consumer data request fulfillment system |
US8972400B1 (en) | 2013-03-11 | 2015-03-03 | Consumerinfo.Com, Inc. | Profile data management |
US9870589B1 (en) | 2013-03-14 | 2018-01-16 | Consumerinfo.Com, Inc. | Credit utilization tracking and reporting |
US10102570B1 (en) | 2013-03-14 | 2018-10-16 | Consumerinfo.Com, Inc. | Account vulnerability alerts |
US9406085B1 (en) | 2013-03-14 | 2016-08-02 | Consumerinfo.Com, Inc. | System and methods for credit dispute processing, resolution, and reporting |
US10664936B2 (en) | 2013-03-15 | 2020-05-26 | Csidentity Corporation | Authentication systems and methods for on-demand products |
US9633322B1 (en) | 2013-03-15 | 2017-04-25 | Consumerinfo.Com, Inc. | Adjustment of knowledge-based authentication |
US10685398B1 (en) | 2013-04-23 | 2020-06-16 | Consumerinfo.Com, Inc. | Presenting credit score information |
US9767127B2 (en) | 2013-05-02 | 2017-09-19 | Outseeker Corp. | Method for record linkage from multiple sources |
US9721147B1 (en) | 2013-05-23 | 2017-08-01 | Consumerinfo.Com, Inc. | Digital identity |
US9443268B1 (en) | 2013-08-16 | 2016-09-13 | Consumerinfo.Com, Inc. | Bill payment and reporting |
US11157944B2 (en) | 2013-09-13 | 2021-10-26 | Liveramp, Inc. | Partner encoding of anonymous links to protect consumer privacy |
US9665883B2 (en) | 2013-09-13 | 2017-05-30 | Acxiom Corporation | Apparatus and method for bringing offline data online while protecting consumer privacy |
US10990686B2 (en) | 2013-09-13 | 2021-04-27 | Liveramp, Inc. | Anonymous links to protect consumer privacy |
US10592920B2 (en) | 2013-09-19 | 2020-03-17 | Liveramp, Inc. | Method and system for tracking user engagement on multiple third-party sites |
US10621600B2 (en) | 2013-09-23 | 2020-04-14 | Liveramp, Inc. | Method for analyzing website visitors using anonymized behavioral prediction models |
US10102536B1 (en) | 2013-11-15 | 2018-10-16 | Experian Information Solutions, Inc. | Micro-geographic aggregation system |
US10325314B1 (en) | 2013-11-15 | 2019-06-18 | Consumerinfo.Com, Inc. | Payment reporting systems |
US9477737B1 (en) | 2013-11-20 | 2016-10-25 | Consumerinfo.Com, Inc. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
US9529851B1 (en) | 2013-12-02 | 2016-12-27 | Experian Information Solutions, Inc. | Server architecture for electronic data quality processing |
US10262362B1 (en) | 2014-02-14 | 2019-04-16 | Experian Information Solutions, Inc. | Automatic generation of code for attributes |
USD760256S1 (en) | 2014-03-25 | 2016-06-28 | Consumerinfo.Com, Inc. | Display screen or portion thereof with graphical user interface |
USD759689S1 (en) | 2014-03-25 | 2016-06-21 | Consumerinfo.Com, Inc. | Display screen or portion thereof with graphical user interface |
USD759690S1 (en) | 2014-03-25 | 2016-06-21 | Consumerinfo.Com, Inc. | Display screen or portion thereof with graphical user interface |
US9892457B1 (en) | 2014-04-16 | 2018-02-13 | Consumerinfo.Com, Inc. | Providing credit data in search results |
US10373240B1 (en) | 2014-04-25 | 2019-08-06 | Csidentity Corporation | Systems, methods and computer-program products for eligibility verification |
US9576030B1 (en) | 2014-05-07 | 2017-02-21 | Consumerinfo.Com, Inc. | Keeping up with the joneses |
US20160110713A1 (en) * | 2014-10-21 | 2016-04-21 | Mastercard International Incorporated | Method and system for secure global tokenization |
US9613072B2 (en) * | 2014-10-29 | 2017-04-04 | Bank Of America Corporation | Cross platform data validation utility |
US10445152B1 (en) | 2014-12-19 | 2019-10-15 | Experian Information Solutions, Inc. | Systems and methods for dynamic report generation based on automatic modeling of complex data structures |
US10430423B1 (en) * | 2015-07-31 | 2019-10-01 | Priceline.Com Llc | Attribute translation and matching from a plurality of data records to create consolidated data records |
US11316844B2 (en) * | 2015-08-24 | 2022-04-26 | Paypal, Inc. | Optimizing tokens for identity platforms |
US10757154B1 (en) | 2015-11-24 | 2020-08-25 | Experian Information Solutions, Inc. | Real-time event-based notification system |
US10699255B1 (en) | 2016-04-04 | 2020-06-30 | United Services Automobile Association (Usaa) | Efficient propagation of user data across disparate systems |
US10678894B2 (en) | 2016-08-24 | 2020-06-09 | Experian Information Solutions, Inc. | Disambiguation and authentication of device users |
US10552523B2 (en) * | 2016-10-14 | 2020-02-04 | Sap Se | Automatically identifying synonyms within a token-based database management system |
US10191942B2 (en) | 2016-10-14 | 2019-01-29 | Sap Se | Reducing comparisons for token-based entity resolution |
CA3050139A1 (en) | 2017-01-31 | 2018-08-09 | Experian Information Solutions, Inc. | Massive scale heterogeneous data ingestion and user resolution |
US10735183B1 (en) | 2017-06-30 | 2020-08-04 | Experian Information Solutions, Inc. | Symmetric encryption for private smart contracts among multiple parties in a private peer-to-peer network |
US11503015B2 (en) * | 2017-10-12 | 2022-11-15 | Mx Technologies, Inc. | Aggregation platform portal for displaying and updating data for third-party service providers |
US10911234B2 (en) | 2018-06-22 | 2021-02-02 | Experian Information Solutions, Inc. | System and method for a token gateway environment |
US10880313B2 (en) | 2018-09-05 | 2020-12-29 | Consumerinfo.Com, Inc. | Database platform for realtime updating of user data from third party sources |
US10963434B1 (en) | 2018-09-07 | 2021-03-30 | Experian Information Solutions, Inc. | Data architecture for supporting multiple search models |
US10380380B1 (en) * | 2018-10-08 | 2019-08-13 | Capital One Services, Llc | Protecting client personal data from customer service agents |
US11315179B1 (en) | 2018-11-16 | 2022-04-26 | Consumerinfo.Com, Inc. | Methods and apparatuses for customized card recommendations |
US11238656B1 (en) | 2019-02-22 | 2022-02-01 | Consumerinfo.Com, Inc. | System and method for an augmented reality experience via an artificial intelligence bot |
US11113258B2 (en) | 2019-05-08 | 2021-09-07 | Bank Of America Corporation | Artificially-intelligent, continuously-updating, centralized-database-identifier repository system |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
US11675754B2 (en) | 2020-11-24 | 2023-06-13 | Collibra Belgium Bv | Systems and methods for universal reference source creation and accurate secure matching |
US11880377B1 (en) | 2021-03-26 | 2024-01-23 | Experian Information Solutions, Inc. | Systems and methods for entity resolution |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5613012A (en) * | 1994-11-28 | 1997-03-18 | Smarttouch, Llc. | Tokenless identification system for authorization of electronic transactions and electronic transmissions |
US5966695A (en) * | 1995-10-17 | 1999-10-12 | Citibank, N.A. | Sales and marketing support system using a graphical query prospect database |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4528643A (en) | 1983-01-10 | 1985-07-09 | Fpdc, Inc. | System for reproducing information in material objects at a point of sale location |
US4933848A (en) | 1988-07-15 | 1990-06-12 | International Business Machines Corporation | Method for enforcing referential constraints in a database management system |
US5291583A (en) | 1990-12-14 | 1994-03-01 | Racal-Datacom, Inc. | Automatic storage of persistent ASN.1 objects in a relational schema |
GB9204450D0 (en) | 1992-03-02 | 1992-04-15 | Ibm | Concurrent access to indexed data files |
US5530854A (en) | 1992-09-25 | 1996-06-25 | At&T Corp | Shared tuple method and system for generating keys to access a database |
US5794229A (en) | 1993-04-16 | 1998-08-11 | Sybase, Inc. | Database system with methodology for storing a database table by vertically partitioning all columns of the table |
US5603025A (en) | 1994-07-29 | 1997-02-11 | Borland International, Inc. | Methods for hypertext reporting in a relational database management system |
US5890140A (en) * | 1995-02-22 | 1999-03-30 | Citibank, N.A. | System for communicating with an electronic delivery system that integrates global financial services |
US5692132A (en) | 1995-06-07 | 1997-11-25 | Mastercard International, Inc. | System and method for conducting cashless transactions on a computer network |
JPH11513826A (en) * | 1995-10-17 | 1999-11-24 | シティバンク、エヌ.エイ. | Sales processing support system and method |
US5809478A (en) | 1995-12-08 | 1998-09-15 | Allstate Insurance Company | Method for accessing and evaluating information for processing an application for insurance |
US5870753A (en) | 1996-03-20 | 1999-02-09 | International Business Machines Corporation | Method and apparatus for enabling a persistent metastate for objects in an object oriented environment |
US5754772A (en) * | 1996-03-26 | 1998-05-19 | Unisys Corporation | Transaction service independent HTTP server-to-transaction gateway |
US5706495A (en) | 1996-05-07 | 1998-01-06 | International Business Machines Corporation | Encoded-vector indices for decision support and warehousing |
US5765028A (en) | 1996-05-07 | 1998-06-09 | Ncr Corporation | Method and apparatus for providing neural intelligence to a mail query agent in an online analytical processing system |
US5767854A (en) | 1996-09-27 | 1998-06-16 | Anwar; Mohammed S. | Multidimensional data display and manipulation system and methods for using same |
US5799300A (en) | 1996-12-12 | 1998-08-25 | International Business Machines Corporations | Method and system for performing range-sum queries on a data cube |
US5890154A (en) * | 1997-06-06 | 1999-03-30 | International Business Machines Corp. | Merging database log files through log transformations |
US6523041B1 (en) | 1997-07-29 | 2003-02-18 | Acxiom Corporation | Data linking system and method using tokens |
US6073140A (en) * | 1997-07-29 | 2000-06-06 | Acxiom Corporation | Method and system for the creation, enhancement and update of remote data using persistent keys |
-
1999
- 1999-12-21 US US09/469,096 patent/US6523041B1/en not_active Expired - Lifetime
-
2000
- 2000-12-15 EP EP00311258A patent/EP1118948A3/en not_active Ceased
- 2000-12-19 AU AU24408/01A patent/AU782174B2/en not_active Expired
- 2000-12-19 MX MXPA02006267A patent/MXPA02006267A/en active IP Right Grant
- 2000-12-19 JP JP2001547309A patent/JP4634685B2/en not_active Expired - Lifetime
- 2000-12-19 BR BRPI0016904A patent/BRPI0016904B1/en not_active IP Right Cessation
- 2000-12-19 WO PCT/US2000/034545 patent/WO2001046862A1/en active IP Right Grant
- 2000-12-19 CA CA2395241A patent/CA2395241C/en not_active Expired - Lifetime
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5613012A (en) * | 1994-11-28 | 1997-03-18 | Smarttouch, Llc. | Tokenless identification system for authorization of electronic transactions and electronic transmissions |
US5966695A (en) * | 1995-10-17 | 1999-10-12 | Citibank, N.A. | Sales and marketing support system using a graphical query prospect database |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6523041B1 (en) | 1997-07-29 | 2003-02-18 | Acxiom Corporation | Data linking system and method using tokens |
JP2009301577A (en) * | 2002-08-12 | 2009-12-24 | Acxiom Corp | Data linking system and method using encoded link |
EP1661372A2 (en) * | 2003-09-06 | 2006-05-31 | Intrado, Inc. | Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores |
EP1661372A4 (en) * | 2003-09-06 | 2009-04-01 | Intrado Inc | Method and system for availing participants in a special number call event and others of information contained in a plurality of data stores |
Also Published As
Publication number | Publication date |
---|---|
AU782174B2 (en) | 2005-07-07 |
CA2395241A1 (en) | 2001-06-28 |
US6523041B1 (en) | 2003-02-18 |
BR0016904A (en) | 2002-10-22 |
JP2003518296A (en) | 2003-06-03 |
JP4634685B2 (en) | 2011-02-16 |
MXPA02006267A (en) | 2004-02-26 |
EP1118948A3 (en) | 2003-02-05 |
EP1118948A2 (en) | 2001-07-25 |
BRPI0016904B1 (en) | 2015-12-29 |
AU2440801A (en) | 2001-07-03 |
CA2395241C (en) | 2010-12-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CA2395241C (en) | Data linking system and method using tokens | |
CA2435468C (en) | Data linking system and method using encoded links | |
US9613373B2 (en) | System and method for retrieving and normalizing product information | |
US6246997B1 (en) | Electronic commerce site with query interface | |
US6073140A (en) | Method and system for the creation, enhancement and update of remote data using persistent keys | |
US7200806B2 (en) | System and method for generating pre-populated forms | |
US7698281B2 (en) | Use of extensible markup language in a system and method for influencing a position on a search result list generated by a computer network search engine | |
US6438544B1 (en) | Method and apparatus for dynamic discovery of data model allowing customization of consumer applications accessing privacy data | |
US7644070B2 (en) | System and method for improving resolution of channel data | |
US20020062241A1 (en) | Apparatus and method for coding electronic direct marketing lists to common searchable format | |
US20020138375A1 (en) | System and method for synchronizing ledger accounts by company group | |
US20020184222A1 (en) | Chaining database records that represent a single customer or multiple customers living in a household | |
EP0979477A1 (en) | Client profile management within a marketing system | |
US20060212416A1 (en) | Method for processing data to optimize and categorize matches | |
US7406471B1 (en) | Scalable multi-database event processing system using universal subscriber-specific data and universal global data | |
CN1411581A (en) | On-line advertisement mechanism | |
US7970782B1 (en) | Systems and methods for set filtering of data |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY CA CH CN CR CU CZ DE DK DM DZ EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
WWE | Wipo information: entry into national phase |
Ref document number: 2395241 Country of ref document: CA |
|
ENP | Entry into the national phase |
Ref country code: JP Ref document number: 2001 547309 Kind code of ref document: A Format of ref document f/p: F |
|
WWE | Wipo information: entry into national phase |
Ref document number: PA/a/2002/006267 Country of ref document: MX |
|
WWE | Wipo information: entry into national phase |
Ref document number: 24408/01 Country of ref document: AU |
|
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
122 | Ep: pct application non-entry in european phase | ||
WWG | Wipo information: grant in national office |
Ref document number: 24408/01 Country of ref document: AU |