Identity verification is critical for various transactions or activities, such as transactions of age-restricted merchandise or access control activities for certain restricted areas. In a traditional fashion, a sales clerk or gate keeper can manually check an identification document of an individual who is involved in a transaction or wants to have access to a restricted area. Unfortunately, manual verification can be a time-consuming process and can be subject to inaccuracies due to human errors.
One way to overcome the problems with manual identification checks is to utilize an automatic scanning system that can quickly scan and accurately verify an identification document. However, various jurisdictions have different rules and regulations regarding the scanning of identification documents and the retention of information gained from the scans. For example, some jurisdictions may prohibit retention or dissemination of information retrieved from identification documents by electronic scans, while other jurisdictions may allow the same. For entities having activities in multiple jurisdictions, it is cumbersome and difficult to comply with all applicable rules and regulations in all jurisdictions where they operate. In addition, not every individual or business entity is capable of keeping track of related rules (not to mention corresponding updates) in various jurisdictions. As a result, many companies err on the side of caution and do not use or store much of the information that can be obtained from an identification document. Alternatively, some companies may manually enter information that is read from a document, which is prone to errors, rather than rely on a scan. Both solutions are sub-optimal from the standpoint of the business operator.
Identity verification plays an important role in transactions, activities, or interactions among parties who are not familiar with one another. To make sure that an individual standing in front of you is “authentic” or “the right person” to deal with, identification documents (e.g., a driver license, an identification card, a passport, or other suitable documents containing sufficient information to help verify the identity of an individual) are frequently used to verify the holders' identifies. Systems that can automatically read identification documents are increasingly used by businesses, governments, or individuals because they provide a fast, convenient and accurate solution for identity verification. Due to the increasing use of identity document scans and privacy concerns over the use of information obtained from those scans, however, more and more jurisdictions (e.g., countries, states, provinces, counties, cities, or other suitable administrative districts) have specific rules to regulate conduct involving collecting identification information via electronic scans of identification documents. Therefore, simply using an automatic identity verification system runs the risk of violating such rules in various jurisdictions.
The present system and method provide a convenient way to automatically verify identity of an identification document holder while maintaining compliance with applicable electronic scanning rules of various jurisdictions. More particularly, the present system and method enable scanning, processing, and utilizing (by, for example, presenting and/or storing) identification information derived from identification documents in a rule-compliant fashion. The scanning process includes a manual or automatic process of capturing any suitable information (including but not limited to images, embedded information, coded information, layout information, etc.) by a suitable scanning device. The system utilizes a database that contains relevant rules and regulations from various jurisdictions. The database can be centralized (e.g., a network-accessible database having all relevant rules) or decentralized (e.g., databases having relevant rules stored in various devices). In some embodiments, the system can retrieve (e.g., by a scanning device) identification information from an identification document and then receive applicable rules (of various jurisdictions) from the database. In other embodiments, the system can first receive applicable rules from the database and then retrieve identification information from an identification document.
Applicable rules can be determined or identified based on various factors. The factors include, for example, an issuer of the identification document, a current location where the identification document is being read, and a proposed use of the information contained in the identification document by an operator of a document scanner. The issuer of an identification document can be a state government, a federal government, a national or local agency (e.g., a military service, a government agency), a corporation, or other suitable entity. The issuer can have its own rules or regulations associated with how the information may be used from the identification documents issued by it. For example, Jurisdiction A may prohibit transmission of identification information retrieved from any Jurisdiction A driver licenses to a third party. The current location of the identification document when it is being scanned can be another factor. Various jurisdictions have rules on electronic scans of identification documents that happen within their territories. For example, Jurisdiction B can prohibit a seller from recording or maintaining certain sensitive information (e.g., name and address) derived from electronic scans of identification documents. Proposed uses of the scanned information by the operator of the document scanner can be another factor to consider. For example, Jurisdiction C may expressly prohibit the storage and use of identification information derived from electronic scans of identification documents for mailing list purposes.
After identifying applicable rules, the present technology can process the retrieved identification information based on the applicable rules. The “processing” of scanned identification information includes applying use restrictions specified by the applicable rules to the identification information, such as redacting, masking, removing, not storing, not transmitting, using only for limited purposes, etc. some of the retrieved identification information. For example, the system can delete, hide, mask, obscure, or edit the retrieved identification information, so as to make sure that an operator of the system (e.g., a sales clerk scanning a customer's identification document for a loyalty program) is in compliance with the applicable rules. The system can further present the processed identification information to a user via a user interface (e.g., on a display). In some embodiments, the system can present an indication showing that the identification information has been processed and is being presented in compliance with the applicable rules. In some embodiments, the system can maintain a record of how the identification information has been processed and utilized for purposes of a subsequent audit to show that the system has been compliant with the applicable rules. The system disclosed herein can be implemented by a suitable software product or various types of applications.
The system includes an input device (e.g., an identification scanner) configured to receive identification information. The system includes a processing module configured to process the received identification information based on multiple rules. As noted previously, the rules can be determined or identified at least based on an issuer of the identification document (e.g., a driver license issued by Jurisdiction A), a current location of the identification document (e.g., a used-car dealer's office in Jurisdiction B), and a proposed use of information from the identification document (e.g., to verify the identity of a potential used-car buyer for an application for a loan). In some embodiments, the rules can be predetermined and stored in the system before the system retrieves the identification information. In other embodiments, the rules can be determined after the system retrieves the identification information. For example, the system can identify the issuer of the identification document after retrieving the identification information, and the system can communicate with a database that stores relevant rules in various jurisdictions via a network. The system disclosed herein can be implemented in a dedicated scanning device, in a multi-purposes portable device (e.g., a smartphone, a notebook, a tablet, a phablet), or in other suitable devices, either fixed or mobile.
Various embodiments of the invention will now be described. The following description provides specific details for a thorough understanding and an enabling description of these embodiments. One skilled in the art will understand, however, that the invention may be practiced without many of these details. Additionally, some well-known structures or functions may not be shown or described in detail, so as to avoid unnecessarily obscuring the relevant description of the various embodiments. The terminology used in the description presented below is intended to be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific embodiments of the invention.
At decision block 105, the system determines whether there exist any applicable rules based on the issuer. For example, Jurisdiction A may have specific rules regarding retention and use of data derived from any identification cards issued by it. In some embodiments, relevant rules are maintained and stored in a centralized database, and the system can access the centralized database system via a wired or wireless network. In some embodiments, the relevant rules can be stored in a local scanning device or at a local computing system at a point of sale.
In an event that one or more applicable issuer rules are identified, the system continues at block 107 to apply the identified rules to the retrieved identification information. For example, Jurisdiction A may prohibit use of gender and age information derived from Jurisdiction-A-issued identification cards by electronic scans. In this example, the system can apply Jurisdiction A's rule by processing the retrieved identification information to delete the gender and age information retrieved from a Jurisdiction-A-issued identification card. In an event that no applicable rule has been identified, processing proceeds to block 109 directly.
At block 109, the system receives a current location of the identification document. The current location can be generated, determined, or identified from various sources. The current location of the identification document being scanned can be determined using one or more methods, including: (1) accessing a database that contains the location where the system implementing the method 100 is installed (e.g., a record shows that a relevant software product was installed in a computing device located in a city such as Moab, Utah); (2) accessing a database containing a location of a physical building containing the point of sale (e.g., the current scanning operation occurs at a store located in Jurisdiction B); (3) using a service that converts a (network) virtual address to a physical location (e.g., a service shows that an Internet Protocol (IP) address of a computing device utilized in the scanning operation has a physical location in Jurisdiction B); or (4) using a global positioning system (GPS) or other similar location-determining technology to determine the current location of the scanning device (e.g., a GPS shows that a computing device utilized in the scanning operation is located in Jurisdiction B). In some embodiments, the current location can be determined using one method and then can be further verified by another method.
After the location information is received, the system proceeds to decision block 111 to determine whether there exist any applicable rules based on the location. For example, Jurisdiction B may have specific rules regarding electronic scans of identification documents within its jurisdiction. Examples of specific rules include: (1) a prohibition of retention of any scanned data after use, (2) a prohibition of dissemination of scanned data to third parties, (3) a prohibition of using the scanned data for more than one purpose (e.g., using the scanned customer information for the purpose of age-restricted purchase and adding to a mailing list, (4) restrictions on the types of information that can be collected (e.g., a date of birth, an identification number, an expiration date, a name, or an address), and (5) a prohibition of storing certain types of information (e.g., a photograph, a social security number, a height, a weight, a race, or a signature).
In an event that one or more applicable rules based on location are identified at block 111, the system continues at block 113 to apply the identified rules to the retrieved identification information. For example, if Jurisdiction B prohibits retention of age information from electronic scans of any identification documents, the system can apply this rule by processing the retrieved identification information to delete the age information retrieved from an identification card issued by any jurisdiction. In an event that no applicable rule has been identified at block 111, processing proceeds to block 115 directly.
At block 115, the system receives a proposed use of the identification document. The proposed use can be based on a predetermined system setting. For example, a system installed at a point of sale may be configured so that the proposed use of scanned information is for purposes of consummating a sale. As another example, a system at a car dealership may be configured so that the proposed use of the scanned information is to prevent fraud in loan applications. In some embodiments, the proposed use is received from a user input. For example, a cashier may indicate that the scanned information is to be used for purposes of signing up for a loyalty program. After the proposed use is determined, processing proceeds to decision block 117 where the system determines whether there exist any applicable rules based on the proposed use. For example, Jurisdiction C may only allow information electronically scanned from identification documents to be stored or shared for specific purposes (e.g., product returns, account collection activities, establishing contractual relationships, credit card applications, credit verification, identity verification, fraud prevention, criminal conduct prevention, advancing law enforcement, etc.) but prohibited for other activities (e.g., activities relating to general marketing or customer loyalty programs). In an event that no applicable rule has been identified at block 117, processing proceeds to block 121 directly.
In an event that one or more applicable rules are identified, at block 119 the system applies the identified rules to the retrieved identification information. For example, if Jurisdiction C only allows use of electronically-scanned gender and age information for law enforcement purposes, the system can apply this rule by processing the retrieved identification information to delete the gender and age information retrieved from an identification card if the proposed use is not for law enforcement.
At block 121, the system displays the processed identification information based on the applied rules. In some embodiments, the system presents the processed identification information to an operator or a user of the system (e.g., a sales clerk, a gate keeper, a used-car dealer, a loan officer, a police officer, or other suitable individual). The information may be presented on a computing device display or in a printout of a form or other document, stored for subsequent reference, and/or transmitted to other computing systems for additional processing. In some embodiments, the processed identification information is a redacted version of the identification information. In other words, some identification information is stripped out and not presented to the user. The system ensures that the electronic scans of identification documents are in compliance with the identified applicable rules. In some embodiments, the system can present the processed identification information along with an indication showing the reasons why the identification information has been redacted or restricted in some fashion (e.g., a description of “State Law Prohibits Electronic Scan of Age for Marketing”).
In some embodiments, the system generates and maintains a record regarding the scanned identification documents and resulting use of the scanned information for purposes of future review and audit. By providing an audit trail associated with a scanned document, the system enables system users to provide evidence to appropriate authorities that demonstrate compliance with applicable rules. It will be appreciated that in the illustrated embodiment of
After receiving the information regarding the issuer, the current location, and the proposed use of the identification document, the system determines whether there are any applicable rules based on the received information in parallel at decision blocks 209, 211, and 213. In an event that no applicable rule has been identified, processing proceeds to block 223 directly. In an event that one or more applicable rules are identified at decision blocks 209, 211, and 213, the system continues at block 215 to retrieve the identified applicable rules (e.g., from a local database or a centralized database, as discussed above). After retrieving the applicable rules, processing proceeds to decision block 217 to determine whether there is any conflict among the identified applicable rules. For example, conflicts may arise between a federal rule and a state rule. If there is a conflict, the system continues to block 219 to prioritize the identified applicable rules in conflict. For example, a federal rule may prevail when it conflicts with a state rule, and therefore a high priority is assigned to the federal rule while a low priority is assigned to the state rule. As another example, if two rules conflict, the system may selectively apply the most restrictive aspects of each of the rules to ensure that the system abides by the minimum requirements of both rules. For example, if one rule indicates that information can be used for marketing purposes but not for loyalty purposes, and another rule indicates that the information can be used for loyalty purposes but not marketing purposes, the system may bar the use of scanned information for either marketing purposes or for loyalty purposes. By applying the most conservative interpretation, the system helps ensure that all applicable rules are being met. If there is no conflict among the identified rules, processing proceeds to block 221 directly.
Processing continues to block 221 to apply identified rules to the identification information. If there is a conflict of rules, then the rules are applied based on the priorities thereof. For example, when a rule with high priority conflicts with a rule with low priority, the rule with high priority is applied and the rule with low priority is ignored. As discussed above, applying the applicable rules can include processing (e.g., delete, hide, mask, obscure, or edit) the identification information. In some embodiments, an operator of the system can modify the rules manually (e.g., override an identified rule). In such case, the system can provide a warning to the operator so as to inform the operator that a manual modification may result in a violation of the identified rule.
At block 223, the system presents the processed identification information based on the applied rules (e.g., it is presented to an operator of the system or stored for a future use such as a royalty program). In some embodiments, the presented identification information can be a stripped version of the identification information. The system can make sure that the whole process (e.g., including electronic scans of identification documents and further uses of the retrieved information) involving identification documents from various jurisdictions is in compliance with identified applicable rules. In some embodiments, the system can present the processed identification information along with an indication showing the reasons why the identification information needs to be processed. In some embodiments, the system can generate and maintain a record regarding the whole process involving electronic scans of identification documents for purposes of a subsequent audit to show that the system has been compliant with the applicable rules.
At block 307, the system receives information regarding a current location of the identification document. The current location can be generated from various sources, as discussed above. After the current location is received, processing proceeds to decision block 309 to determine whether there exist any applicable rules based on the second set of information. In an event that one or more applicable rules are identified at decision block 309, the rules are “remembered” or stored. The system continues at block 313.
At block 313, the system receives information regarding a proposed use of the identification document. The proposed use can be received from a predetermined setting or a user input. After the proposed use is received, processing proceeds to decision block 315 to determine whether there exist any applicable rules on the proposed use based on the issuer and/or location. In an event that one or more applicable rules are identified, the rules are “remembered.” The system then continues at block 319.
At decision block 319, the system determines whether there is any conflict among identified “remembered” applicable rules (e.g., a federal rule may conflict with a state rule for certain types of conduct). If there is no conflict among the identified rules, processing proceeds to block 323 directly. If there is a conflict among identified rules, processing proceeds to block 321 to prioritize the identified rules in conflict. The system continues to block 323 to retrieve identification information from the identification document in accordance with the “remembered” applicable rules. For example, Jurisdiction A may prohibit retrieving address information by electronic scanning an identification document for any purposes. In this case, the system would not retrieve the address information from the identification document (e.g., the system can identify the field of “Address” and skip it in the process of information retrieval).
At block 325, the system displays the processed identification information to an operator. In some embodiments, the processed identification information can be presented as a stripped or “sanitized” version of the identification information. The system can make sure that the whole process involving identification documents from various jurisdictions is in compliance with applicable rules. In some embodiments, the system can present the processed identification information along with an indication showing the reasons why the identification information needs to be processed. In some embodiments, the system can generate and maintain a record regarding the whole process involving electronic scans of identification documents for purposes of future review and audit (e.g., as evidence for compliance of applicable rules). In some embodiments, the system can generate a statement stating that the use of the information scanned by the system has remained compliant with the applicable rules. The statement can be used to let an identification document holder (e.g., a customer at a store) know that the identification scan performed by the system is compliant with the applicable rules.
In the illustrated embodiment, the input device 403 can receive a user input (e.g., the issuer, the current location, and the proposed use for identifying applicable rules as discussed above). In some embodiments, the input device 403 can be a scanning device for retrieving identification information from an identification document associated with an individual. In some embodiments, the input device 403 can be configured to have embedded information regarding a location or a proposed use. For example, the input device 403 can be designed or programed to use only in a certain jurisdiction (e.g., a store located in Jurisdiction A). As another example, the input device 403 can be designed or programed for a specific purpose, such as a customer royalty program. The embedded information can be used to determine one of the factors (e.g., the “location” factor and the “proposed use” factor discussed above) that are used to identify applicable rules in various jurisdictions. The processing module 405 is configured to process the retrieved identification information based on identified applicable rules (e.g., these rules can be identified at and received from the database 415 based on predetermined criteria such as the issuer, the current location, and the proposed use). In some embodiments, the processing module 405 can delete, hide, mask, obscure, or edit the retrieved identification information based on multiple identified applicable rules. The display module 407 is configured to present the processed identification information to an operator or a user of the system 400 (e.g., a sales clerk uses the system 400 to scan a customer's identification document for identity verification). In some embodiments, the identified applicable rules can be stored in the data storage unit 411, such that the system 400 can have access to the identified applicable rules without accessing the network 413. This arrangement enables the system 400 to function normally without network connection. In some embodiments, the data storage unit 411 can be used to store the redacted or processed identification information for a future process. For example, the stored redacted identification information can be used for an analysis of consumer behavior, a consumer royalty program, a marketing activity, or other suitable processes.
It will be appreciated by those skilled in the art that the components or modules that are part of the system or interact with the system may be implemented by computer-executable instructions, such as program modules, executed by one or more computers or other devices. Those skilled in the art will further appreciate that the system or aspects of the system disclosed herein may be implemented on any computing system or device. Suitable computing systems or devices include server computers, multiprocessor systems, microprocessor-based systems, network devices, minicomputers, mainframe computers, distributed computing environments that include any of the foregoing, and the like. Such computing systems or devices may include one or more processors that execute software instructions to perform the functions described herein. Processors include programmable general-purpose or special-purpose microprocessors, programmable controllers, application specific integrated circuits (ASICs), programmable logic devices (PLDs), or a combination of such devices. Software may be stored in a memory, such as a random access memory (RAM), a read-only memory (ROM), a flash memory, or a combination of such devices. Software may also be stored in one or more storage devices, such as magnetic or optical based disks, flash memory devices, or any other type of non-volatile storage medium for storing data. Software may include one or more program modules which include routines, programs, objects, components, data structures, and so on that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or distributed as desired in various embodiments.
From the foregoing, it will be appreciated that specific embodiments of the invention have been described herein for purposes of illustration, but that various modifications may be made without deviating from the spirit and scope of the present disclosure. Accordingly, the present technology is not limited except as by the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
3569619 | Simjian et al. | Mar 1971 | A |
3636318 | Lindstrom et al. | Jan 1972 | A |
3702392 | St. Jean | Nov 1972 | A |
3868057 | Chavez | Feb 1975 | A |
3906201 | Housman et al. | Sep 1975 | A |
3956615 | Anderson et al. | May 1976 | A |
3988570 | Murphy et al. | Oct 1976 | A |
4138057 | Atalla | Feb 1979 | A |
4180207 | Lee | Dec 1979 | A |
4186871 | Anderson et al. | Feb 1980 | A |
4193131 | Lennon et al. | Mar 1980 | A |
RE30579 | Goldman et al. | Apr 1981 | E |
4304961 | Campbell, Jr. | Dec 1981 | A |
4357529 | Atalla | Nov 1982 | A |
4369361 | Swartz et al. | Jan 1983 | A |
4450348 | Stockburger et al. | May 1984 | A |
4453074 | Weinstein | Jun 1984 | A |
4471216 | Herve | Sep 1984 | A |
4506148 | Berthold et al. | Mar 1985 | A |
4575816 | Hendrickson et al. | Mar 1986 | A |
4629872 | Hallberg | Dec 1986 | A |
4634846 | Harvey et al. | Jan 1987 | A |
4639889 | Matsumoto et al. | Jan 1987 | A |
4656473 | Goldman et al. | Apr 1987 | A |
4659914 | Kondo et al. | Apr 1987 | A |
4689477 | Goldman | Aug 1987 | A |
4752676 | Leonard et al. | Jun 1988 | A |
4807287 | Tucker et al. | Feb 1989 | A |
4811393 | Hazard | Mar 1989 | A |
4811408 | Goldman | Mar 1989 | A |
4812628 | Boston et al. | Mar 1989 | A |
4816655 | Musyck et al. | Mar 1989 | A |
4816657 | Stockburger et al. | Mar 1989 | A |
4879747 | Leighton | Nov 1989 | A |
4906988 | Copella | Mar 1990 | A |
4972476 | Nathans | Nov 1990 | A |
4981370 | Dziewit et al. | Jan 1991 | A |
4982072 | Takigami | Jan 1991 | A |
4993068 | Piosenka et al. | Feb 1991 | A |
4995081 | Leighton et al. | Feb 1991 | A |
5001752 | Fischer | Mar 1991 | A |
5007089 | Matyas et al. | Apr 1991 | A |
5012077 | Takano | Apr 1991 | A |
5016192 | Ishido et al. | May 1991 | A |
5030117 | Delorme | Jul 1991 | A |
5054077 | Suzuki | Oct 1991 | A |
5055658 | Cockburn | Oct 1991 | A |
5136643 | Fischer | Aug 1992 | A |
5140634 | Guillon et al. | Aug 1992 | A |
5163098 | Dabhura | Nov 1992 | A |
5172785 | Takahashi | Dec 1992 | A |
5199074 | Thor | Mar 1993 | A |
5214699 | Monroe et al. | May 1993 | A |
5222152 | Fishbine et al. | Jun 1993 | A |
5237611 | Rasmussen et al. | Aug 1993 | A |
5241600 | Hillis | Aug 1993 | A |
5249227 | Bergum et al. | Sep 1993 | A |
5259025 | Monroe et al. | Nov 1993 | A |
5267315 | Narita et al. | Nov 1993 | A |
5280527 | Gullman et al. | Jan 1994 | A |
5284364 | Jain | Feb 1994 | A |
5287181 | Holman | Feb 1994 | A |
5321751 | Ray et al. | Jun 1994 | A |
5336871 | Colgate, Jr. | Aug 1994 | A |
5337358 | Axelrod | Aug 1994 | A |
5337361 | Wang et al. | Aug 1994 | A |
5341428 | Schatz | Aug 1994 | A |
5347589 | Meeks et al. | Sep 1994 | A |
5367148 | Storch et al. | Nov 1994 | A |
5367581 | Abel | Nov 1994 | A |
5420924 | Berson et al. | May 1995 | A |
5422468 | Abecassis | Jun 1995 | A |
5429361 | Raven et al. | Jul 1995 | A |
5432864 | Lu et al. | Jul 1995 | A |
5446273 | Leslie | Aug 1995 | A |
5446885 | Moore et al. | Aug 1995 | A |
5453600 | Swartz | Sep 1995 | A |
5461217 | Claus | Oct 1995 | A |
5469506 | Berson et al. | Nov 1995 | A |
5471533 | Wang et al. | Nov 1995 | A |
5475585 | Bush | Dec 1995 | A |
5490217 | Wang et al. | Feb 1996 | A |
5500518 | Olzak et al. | Mar 1996 | A |
5506395 | Eppley | Apr 1996 | A |
5513019 | Cueli | Apr 1996 | A |
5513261 | Maher | Apr 1996 | A |
5513272 | Bogosian, Jr. | Apr 1996 | A |
5514860 | Berson | May 1996 | A |
5546278 | Bethurum | Aug 1996 | A |
5553143 | Ross | Sep 1996 | A |
5559885 | Drexler et al. | Sep 1996 | A |
5590193 | Le Roux | Dec 1996 | A |
5594226 | Steger | Jan 1997 | A |
5594806 | Colbert | Jan 1997 | A |
5598474 | Johnson | Jan 1997 | A |
5610993 | Yamamoto | Mar 1997 | A |
5621200 | Irwin, Jr. et al. | Apr 1997 | A |
5630127 | Moore et al. | May 1997 | A |
5635981 | Ribacoff | Jun 1997 | A |
5642485 | Deaton | Jun 1997 | A |
5651066 | Moriyasu et al. | Jul 1997 | A |
5661805 | Miyauchi | Aug 1997 | A |
5663553 | Aucsmith | Sep 1997 | A |
5668874 | Kristol et al. | Sep 1997 | A |
5679940 | Templeton et al. | Oct 1997 | A |
5694471 | Chen et al. | Dec 1997 | A |
5695835 | Weber et al. | Dec 1997 | A |
5706507 | Schloss | Jan 1998 | A |
5712472 | Lee | Jan 1998 | A |
5717776 | Watanabe | Feb 1998 | A |
5719939 | Tel | Feb 1998 | A |
5721777 | Blaze | Feb 1998 | A |
5722526 | Sharrard | Mar 1998 | A |
5742685 | Berson et al. | Apr 1998 | A |
D393950 | Lockhart | May 1998 | S |
5748908 | Yu | May 1998 | A |
5754939 | Herz et al. | May 1998 | A |
5770084 | Novis et al. | Jun 1998 | A |
5770849 | Novis et al. | Jun 1998 | A |
5781650 | Lobo et al. | Jul 1998 | A |
5786587 | Colgate, Jr. | Jul 1998 | A |
5805849 | Jordan et al. | Sep 1998 | A |
5812664 | Bernobich et al. | Sep 1998 | A |
5838812 | Pare et al. | Nov 1998 | A |
5848426 | Wang et al. | Dec 1998 | A |
5862247 | Fisun et al. | Jan 1999 | A |
5864622 | Marcus | Jan 1999 | A |
5864623 | Messina | Jan 1999 | A |
5870723 | Pare, Jr. et al. | Feb 1999 | A |
5966654 | Croughwell et al. | Oct 1999 | A |
5988497 | Wallace | Nov 1999 | A |
5991429 | Coffin et al. | Nov 1999 | A |
5995014 | DiMaria | Nov 1999 | A |
6038666 | Hsu et al. | Mar 2000 | A |
6070147 | Harms et al. | May 2000 | A |
6075455 | DiMaria et al. | Jun 2000 | A |
6089452 | Rhode, III | Jul 2000 | A |
6104809 | Berson et al. | Aug 2000 | A |
6119932 | Maloney et al. | Sep 2000 | A |
6119933 | Wong et al. | Sep 2000 | A |
6135355 | Han et al. | Oct 2000 | A |
6138914 | Campo et al. | Oct 2000 | A |
6148091 | DiMaria | Nov 2000 | A |
6169542 | Hooks et al. | Jan 2001 | B1 |
6171138 | Lefebvre et al. | Jan 2001 | B1 |
6182221 | Hsu et al. | Jan 2001 | B1 |
6196460 | Shin | Mar 2001 | B1 |
6199079 | Gupta et al. | Mar 2001 | B1 |
6202055 | Houvener et al. | Mar 2001 | B1 |
6222463 | Rai | Apr 2001 | B1 |
6224109 | Yang | May 2001 | B1 |
6234389 | Valliani et al. | May 2001 | B1 |
6263447 | French et al. | Jul 2001 | B1 |
6279013 | LaMarca | Aug 2001 | B1 |
6289113 | McHugh et al. | Sep 2001 | B1 |
6317544 | Diehl et al. | Nov 2001 | B1 |
6354506 | Plan et al. | Mar 2002 | B1 |
6363387 | Ponnekanti et al. | Mar 2002 | B1 |
6386451 | Sehr | May 2002 | B1 |
6442532 | Kawan | Aug 2002 | B1 |
6460185 | Hardy | Oct 2002 | B1 |
6463416 | Messina | Oct 2002 | B1 |
6475146 | Frelburger et al. | Nov 2002 | B1 |
6484260 | Scott et al. | Nov 2002 | B1 |
6499141 | Egnew | Dec 2002 | B1 |
6523741 | DiMaria et al. | Feb 2003 | B1 |
6542635 | Hu et al. | Apr 2003 | B1 |
6557752 | Yacoob | May 2003 | B1 |
6564997 | Juds | May 2003 | B1 |
6565000 | Sehr | May 2003 | B2 |
6587032 | Armingaud | Jul 2003 | B2 |
6592029 | Brikho | Jul 2003 | B2 |
6609659 | Sehr | Aug 2003 | B2 |
6612958 | Imai et al. | Sep 2003 | B2 |
6615263 | Dulai et al. | Sep 2003 | B2 |
6624739 | Stobbe | Sep 2003 | B1 |
6651217 | Kennedy et al. | Nov 2003 | B1 |
6679425 | Sheppard et al. | Jan 2004 | B1 |
6736317 | McDonald et al. | May 2004 | B1 |
6736322 | Gobburu et al. | May 2004 | B2 |
6745937 | Walsh et al. | Jun 2004 | B2 |
6754910 | Shultz et al. | Jun 2004 | B2 |
6758394 | Maskatiya et al. | Jul 2004 | B2 |
6760463 | Rhoads | Jul 2004 | B2 |
6779721 | Larson et al. | Aug 2004 | B2 |
6785405 | Tuttle et al. | Aug 2004 | B2 |
6808109 | Page | Oct 2004 | B2 |
6820984 | Furuhata | Nov 2004 | B2 |
6854642 | Metcalf et al. | Feb 2005 | B2 |
6910223 | Egnew | Jun 2005 | B2 |
6914517 | Kinsella | Jul 2005 | B2 |
6920437 | Messina | Jul 2005 | B2 |
6928546 | Nanavati et al. | Aug 2005 | B1 |
6934861 | Haala | Aug 2005 | B2 |
6944782 | von Mueller et al. | Sep 2005 | B2 |
6956615 | Nakagishi et al. | Oct 2005 | B2 |
6970088 | Kovach | Nov 2005 | B2 |
6991159 | Zenou | Jan 2006 | B2 |
7003669 | Monk | Feb 2006 | B2 |
7027931 | Jones et al. | Apr 2006 | B1 |
7035626 | Luciano, Jr. | Apr 2006 | B1 |
7059516 | Matsuyama et al. | Jun 2006 | B2 |
7072081 | Johnson et al. | Jul 2006 | B2 |
7110573 | Monk et al. | Sep 2006 | B2 |
7117228 | Tomita et al. | Oct 2006 | B2 |
7118033 | Merkert | Oct 2006 | B2 |
7119553 | Yang et al. | Oct 2006 | B2 |
7119674 | Sefton | Oct 2006 | B2 |
7147155 | Weekes | Dec 2006 | B2 |
7161465 | Wood et al. | Jan 2007 | B2 |
7185808 | Mitsumoto | Mar 2007 | B2 |
7212113 | Zanovitch | May 2007 | B2 |
7212279 | Feng | May 2007 | B1 |
7244043 | Monk et al. | Jul 2007 | B2 |
7277891 | Howard et al. | Oct 2007 | B2 |
7280030 | Monaco | Oct 2007 | B1 |
7284698 | Sogo | Oct 2007 | B2 |
7299408 | Daconta | Nov 2007 | B1 |
7309010 | Stopperan et al. | Dec 2007 | B2 |
7309012 | von Mueller et al. | Dec 2007 | B2 |
7313825 | Redlich et al. | Dec 2007 | B2 |
7349987 | Redlich et al. | Mar 2008 | B2 |
7362210 | Bazakos et al. | Apr 2008 | B2 |
7382261 | Lin et al. | Jun 2008 | B2 |
7382911 | Meier et al. | Jun 2008 | B1 |
7392944 | Shieh | Jul 2008 | B2 |
7466223 | Sefton | Dec 2008 | B2 |
7478067 | Messina | Jan 2009 | B2 |
7484088 | Campbell et al. | Jan 2009 | B2 |
7492256 | Eren et al. | Feb 2009 | B2 |
7494060 | Zagami | Feb 2009 | B2 |
7500178 | O'Donnell | Mar 2009 | B1 |
7526645 | Miyazaki | Apr 2009 | B2 |
7554446 | Ciarcia et al. | Jun 2009 | B2 |
7568108 | Monaco et al. | Jul 2009 | B2 |
7587368 | Felsher | Sep 2009 | B2 |
7599847 | Block et al. | Oct 2009 | B2 |
7631805 | Larson et al. | Dec 2009 | B2 |
7639846 | Yoda | Dec 2009 | B2 |
7685629 | White et al. | Mar 2010 | B1 |
7708189 | Cipriano | May 2010 | B1 |
7716240 | Lim | May 2010 | B2 |
7739744 | Burch et al. | Jun 2010 | B2 |
7802305 | Leeds | Sep 2010 | B1 |
7817013 | Bazakos et al. | Oct 2010 | B2 |
7821391 | Gupta et al. | Oct 2010 | B2 |
7844545 | Michelsen | Nov 2010 | B2 |
7860318 | Mandelbaum et al. | Dec 2010 | B2 |
7895611 | Grabarnik et al. | Feb 2011 | B2 |
7898385 | Kocher | Mar 2011 | B2 |
7899751 | Messina | Mar 2011 | B2 |
7925887 | Burton | Apr 2011 | B2 |
8009013 | Hirschfeld et al. | Aug 2011 | B1 |
8019691 | Dominguez et al. | Sep 2011 | B2 |
8023140 | Lapstun et al. | Sep 2011 | B2 |
8036431 | Fisher et al. | Oct 2011 | B1 |
8083130 | Cipriano | Dec 2011 | B1 |
8086525 | Atwood et al. | Dec 2011 | B2 |
8090388 | Opitz | Jan 2012 | B1 |
8139869 | Mandelbaum et al. | Mar 2012 | B2 |
8220047 | Soghoian | Jul 2012 | B1 |
8235287 | McKelvey | Aug 2012 | B2 |
8286875 | Tang et al. | Oct 2012 | B2 |
8294554 | Shoarinejad et al. | Oct 2012 | B2 |
8322605 | Ludlow et al. | Dec 2012 | B2 |
8517254 | Cipriano | Aug 2013 | B1 |
8520957 | Mandelbaum et al. | Aug 2013 | B2 |
8616446 | Ludlow et al. | Dec 2013 | B2 |
8771085 | Clyde et al. | Jul 2014 | B1 |
8960541 | Ludlow | Feb 2015 | B2 |
8964211 | Koga | Feb 2015 | B2 |
9069982 | Coles | Jun 2015 | B2 |
9245157 | Cipriano | Jan 2016 | B1 |
9697667 | Cipriano | Jul 2017 | B1 |
9864482 | Dube | Jan 2018 | B2 |
20010027439 | Holtzman et al. | Oct 2001 | A1 |
20010034222 | Roustaei et al. | Oct 2001 | A1 |
20010041581 | Hansson | Nov 2001 | A1 |
20020001393 | Jones | Jan 2002 | A1 |
20020002507 | Hatakeyama | Jan 2002 | A1 |
20020010679 | Felsher | Jan 2002 | A1 |
20020025796 | Taylor et al. | Feb 2002 | A1 |
20020046185 | Villart et al. | Apr 2002 | A1 |
20020052193 | Chetty | May 2002 | A1 |
20020056747 | Matsuyama et al. | May 2002 | A1 |
20020087478 | Hudd et al. | Jul 2002 | A1 |
20020089410 | Janiak et al. | Jul 2002 | A1 |
20020095389 | Gaines | Jul 2002 | A1 |
20020100802 | Sehr | Aug 2002 | A1 |
20020100803 | Sehr | Aug 2002 | A1 |
20020134837 | Kishon | Sep 2002 | A1 |
20020143571 | Messina | Oct 2002 | A1 |
20020156676 | Ahrens et al. | Oct 2002 | A1 |
20030048904 | Wang et al. | Mar 2003 | A1 |
20030055689 | Block et al. | Mar 2003 | A1 |
20030057276 | Appalucci et al. | Mar 2003 | A1 |
20030070077 | Redlich et al. | Apr 2003 | A1 |
20030071730 | Valbh | Apr 2003 | A1 |
20030078069 | Lindeman | Apr 2003 | A1 |
20030099379 | Monk et al. | May 2003 | A1 |
20030115459 | Monk | Jun 2003 | A1 |
20030126092 | Chihara | Jul 2003 | A1 |
20030143990 | Minear et al. | Jul 2003 | A1 |
20030154138 | Phillips | Aug 2003 | A1 |
20030177102 | Robinson | Sep 2003 | A1 |
20030182435 | Redlich et al. | Sep 2003 | A1 |
20030218066 | Fernandes et al. | Nov 2003 | A1 |
20030225687 | Lawrence | Dec 2003 | A1 |
20040002894 | Kocher | Jan 2004 | A1 |
20040010472 | Hilby et al. | Jan 2004 | A1 |
20040034666 | Chen | Feb 2004 | A1 |
20040049401 | Carr et al. | Mar 2004 | A1 |
20040059688 | Dominguez et al. | Mar 2004 | A1 |
20040068693 | Rawat | Apr 2004 | A1 |
20040078335 | Calvesio et al. | Apr 2004 | A1 |
20040080504 | Salesky | Apr 2004 | A1 |
20040081332 | Tuttle et al. | Apr 2004 | A1 |
20040083091 | Ie et al. | Apr 2004 | A1 |
20040104268 | Bailey | Jun 2004 | A1 |
20040107356 | Shamoon | Jun 2004 | A1 |
20040117060 | Stopperan et al. | Jun 2004 | A1 |
20040117624 | Brandt et al. | Jun 2004 | A1 |
20040124982 | Kovach | Jul 2004 | A1 |
20040153408 | Jones | Aug 2004 | A1 |
20040205466 | Kuppinger et al. | Oct 2004 | A1 |
20040215557 | Michelsen | Oct 2004 | A1 |
20040223197 | Ohta | Nov 2004 | A1 |
20040233036 | Sefton | Nov 2004 | A1 |
20040250142 | Feyler | Dec 2004 | A1 |
20040254895 | Kumagaya et al. | Dec 2004 | A1 |
20050039014 | Sajkowsky | Feb 2005 | A1 |
20050076013 | Hilbert | Apr 2005 | A1 |
20050080649 | Alvarez et al. | Apr 2005 | A1 |
20050082365 | Merkert | Apr 2005 | A1 |
20050093675 | Wood et al. | May 2005 | A1 |
20050131829 | Messina | Jun 2005 | A1 |
20050137987 | May | Jun 2005 | A1 |
20050140679 | Kaneda | Jun 2005 | A1 |
20050171787 | Zagami | Aug 2005 | A1 |
20050187677 | Walker | Aug 2005 | A1 |
20050205668 | Sogo | Sep 2005 | A1 |
20050209955 | Underwood et al. | Sep 2005 | A1 |
20050212654 | Yoda | Sep 2005 | A1 |
20050216953 | Ellingson | Sep 2005 | A1 |
20050241003 | Sweeney et al. | Oct 2005 | A1 |
20050242172 | Murata | Nov 2005 | A1 |
20050247787 | Von Mueller et al. | Nov 2005 | A1 |
20050248450 | Zanovitch | Nov 2005 | A1 |
20050258234 | Silverbrook | Nov 2005 | A1 |
20050273453 | Holloran | Dec 2005 | A1 |
20050284931 | Adams et al. | Dec 2005 | A1 |
20060004812 | Blackwell et al. | Jan 2006 | A1 |
20060047731 | Matsui | Mar 2006 | A1 |
20060049255 | Mueller et al. | Mar 2006 | A1 |
20060075228 | Black et al. | Apr 2006 | A1 |
20060080541 | Monaco et al. | Apr 2006 | A1 |
20060102717 | Wood et al. | May 2006 | A1 |
20060151607 | Horikiri | Jul 2006 | A1 |
20060157559 | Levy | Jul 2006 | A1 |
20060176062 | Yang et al. | Aug 2006 | A1 |
20060184575 | Singleton | Aug 2006 | A1 |
20060186994 | Lin et al. | Aug 2006 | A1 |
20060231610 | Cheng | Oct 2006 | A1 |
20060237529 | Kelley et al. | Oct 2006 | A1 |
20060243799 | Kelly et al. | Nov 2006 | A1 |
20060259983 | Sperry | Nov 2006 | A1 |
20070046424 | Davis et al. | Mar 2007 | A1 |
20070069921 | Sefton | Mar 2007 | A1 |
20070085684 | Ciarcia et al. | Apr 2007 | A1 |
20070094594 | Matichuk et al. | Apr 2007 | A1 |
20070118479 | Halsema | May 2007 | A1 |
20070121937 | Kochevar et al. | May 2007 | A1 |
20070152841 | Eren et al. | Jul 2007 | A1 |
20070156659 | Lim | Jul 2007 | A1 |
20070183000 | Eisen | Aug 2007 | A1 |
20070226014 | Alemayehu et al. | Sep 2007 | A1 |
20070254676 | Pedigo et al. | Nov 2007 | A1 |
20070275735 | Estevez | Nov 2007 | A1 |
20080002911 | Eisen | Jan 2008 | A1 |
20080011850 | Henry | Jan 2008 | A1 |
20080027949 | Kawada | Jan 2008 | A1 |
20080041942 | Aissa | Feb 2008 | A1 |
20080109099 | Moshier | May 2008 | A1 |
20080143482 | Shoarinejad et al. | Jun 2008 | A1 |
20080148059 | Shapiro | Jun 2008 | A1 |
20080168062 | Reeves | Jul 2008 | A1 |
20080239365 | Salgado et al. | Oct 2008 | A1 |
20080272881 | Goel | Nov 2008 | A1 |
20080307503 | Waters | Dec 2008 | A1 |
20090085745 | Gupta et al. | Apr 2009 | A1 |
20090089206 | Lukac | Apr 2009 | A1 |
20090121897 | Muhlethaler et al. | May 2009 | A1 |
20090144619 | Best | Jun 2009 | A1 |
20090150442 | Barnard et al. | Jun 2009 | A1 |
20090167492 | Madafferi | Jul 2009 | A1 |
20090282492 | Takahashi | Nov 2009 | A1 |
20090289443 | Okezie | Nov 2009 | A1 |
20090296166 | Schrichte | Dec 2009 | A1 |
20090321517 | Deane et al. | Dec 2009 | A1 |
20100033753 | Stephenson | Feb 2010 | A1 |
20100046015 | Whittle et al. | Feb 2010 | A1 |
20100070396 | Schrichte | Mar 2010 | A1 |
20100123003 | Olson et al. | May 2010 | A1 |
20100241844 | Hussain et al. | Sep 2010 | A1 |
20110001604 | Ludlow et al. | Jan 2011 | A1 |
20110142295 | Mandelbaum et al. | Jun 2011 | A1 |
20110145053 | Hashim-Waris | Jun 2011 | A1 |
20110221565 | Ludlow et al. | Sep 2011 | A1 |
20110238668 | Matsumoto | Sep 2011 | A1 |
20120024948 | Messina | Feb 2012 | A1 |
20120117045 | Carlock | May 2012 | A1 |
20120330838 | Hoffman et al. | Dec 2012 | A1 |
20130024239 | Baker et al. | Jan 2013 | A1 |
20130040657 | Jackson | Feb 2013 | A1 |
20130159021 | Felsher | Jun 2013 | A1 |
20130185240 | Ward et al. | Jul 2013 | A1 |
20130214044 | Sperduti et al. | Aug 2013 | A1 |
20130291126 | Thomson | Oct 2013 | A1 |
20140056486 | Mandelbaum et al. | Feb 2014 | A1 |
20140059188 | Linden et al. | Feb 2014 | A1 |
20140115710 | Hughes et al. | Apr 2014 | A1 |
20150012305 | Truskovsky | Jan 2015 | A1 |
20150200922 | Eschbach | Jul 2015 | A1 |
20160125680 | White | May 2016 | A1 |
20160358171 | Gannon | Dec 2016 | A1 |
20170126784 | Mattern | May 2017 | A1 |
20180096201 | Bermundo | Apr 2018 | A1 |
20180117945 | Talwerdi | May 2018 | A1 |
Number | Date | Country |
---|---|---|
2802430 | Jul 1978 | DE |
3050473 | Sep 1986 | DE |
4410459 | Feb 1995 | DE |
19527737 | Jun 2006 | DE |
0187448 | Jul 1986 | EP |
0407207 | Jul 1991 | EP |
0683471 | Nov 1995 | EP |
0991027 | Apr 2000 | EP |
2571873 | Apr 1986 | FR |
1546053 | Jan 1978 | GB |
2067322 | Oct 1984 | GB |
2136180 | Feb 1985 | GB |
2270586 | Mar 1994 | GB |
2332973 | Jul 1999 | GB |
2359172 | Feb 2004 | GB |
0050075879 | Jun 1975 | JP |
63138462 | Jun 1988 | JP |
64055695 | Mar 1989 | JP |
7093648 | Apr 1995 | JP |
0080101868 | Apr 1996 | JP |
09245231 | Sep 1997 | JP |
11316818 | Nov 1999 | JP |
3100972 | Oct 2000 | JP |
2003157615 | May 2003 | JP |
WO8702491 | Apr 1987 | WO |
WO9412372 | Jun 1994 | WO |
WO9422371 | Oct 1994 | WO |
0213049 | Feb 2002 | WO |
WO02095589 | Nov 2002 | WO |
Entry |
---|
“Natural Language Understanding Through Fuzzy Logic Interference and Its Application to Speech Recognition” (2002) Jiping Sun, Fakhri Karray, Otman Basir & Mohamed Kamel. |
Honeywell International Inc. v. Intellicheck Mobilisa, Inc, PTAB-CBM2017-00062, CBM review of patent owned by common assignee, initiated Jul. 28, 2017, documents filed Jul. 28, 2017. |
Honeywell International Inc. v. Intellicheck Mobilisa, Inc, PTAB-CBM2017-00062, CBM review of patent owned by common assignee, initiated Jul. 28, 2017, documents filed Aug. 14, 2017 through Aug. 31, 2017. |
Honeywell International Inc. v. Intellicheck Mobilisa, Inc, PTAB-CBM2017-00062, CBM review of patent owned by common assignee, initiated Jul. 28, 2017, documents filed Oct. 18, 2018. |
Honeywell International Inc. v. Intellicheck Mobilisa, Inc, PTAB-CBM2017-00062, CBM review of patent owned by common assignee, initiated Jul. 28, 2017, documents filed Oct. 27, 2017. |
Honeywell International Inc. v. Intellicheck Mobilisa, Inc, PTAB-CBM2017-00062, CBM review of patent owned by aommon assignee, initiated Jul. 28, 2017, documents filed Oct. 30, 2017. |
Kim et al. ‘Experiences with Tripwire: Using Integrity Checkers for Intrusion Detection’, In Systems Administration. Networking and Security Conference III (Usenix, 1994 [online]). Published Feb. 21, 1994. [retrieved on Dec. 18, 2008]. Retrieved from the Internet. |
Honeywell International Inc. v. Intellicheck Mobilisa, Inc, PTAB-CBM2017-00062, CBM review of patent owned by common assignee, initiated Jul. 28, 2017, documents filed Oct. 30, 2017. |
Number | Date | Country | |
---|---|---|---|
20160125680 A1 | May 2016 | US |