Patent Grant
12153666
Many methods and systems have been developed over the years to prevent or detect Internet fraud. Today, to gain consumer confidence and prevent revenue loss, online communities, such as financial institutions, a website operator, merchant, or other online communities that desire ring enrollment may desire an accurate and trustworthy way of detecting possible Internet fraud and providing Internet security. Many sites require entry of a password or other credentials for authentication, but this does not suffice because credentials may be stolen.
Traditionally, entities have used manual processes to review a suspected fraudulent transaction and individuals who may have been involved, which is often cumbersome and time consuming. Conventional fraud detection systems often focus on a user's account and behavior of the user to find anomalous behavior. However, if too much time has passed between a fraudulent transaction and/or early-stage fraud staging activities (e.g., including the theft of credentials, changing the victim's contact information to disrupt communication between the bank and the victim, adding payees for future money movement), and/or identifying fraudsters, fraudulent attacks may have occurred undetected in the mean-time.
Accordingly, a need exists for improved methods and systems for fraud containment. A further need exists for mandating the integrity of online communities and services.
An aspect of the invention may be directed to an enterprise security and fraud detection and prevention system. Systems and methods may be provided for detecting physical devices that interact with a group of potential victims over an electronic network in support of fraudulent activities. A fraud containment system may include (i) systems and methods for identifying circles of at-risk customers targeted by a common physical device; (ii) systems and methods for profiling the interaction between the device and individual victims and between the device and the circle of victims as a whole; (iii) systems and methods for identifying accomplice devices that acted in support of confirmed fraud even when the fraud transaction did not occur over an electronic network or the device was not directly involved in the fraudulent transaction; (iv) systems and methods for identifying devices that may have assisted in the compromise of an account whose credentials have been stolen; (v) systems and methods for using at-risk victim circles to assist in prioritizing and directing rapid-response and attack-containment activities; (vi) systems and methods for assessing the threat/vulnerability of individual victim circles and the network as a whole; and/or (vii) systems and methods for expanding the scope of monitoring coverage to cover the combined networks of multiple organizations.
An aspect of the invention is directed to a method for fraud containment comprising: determining a proximity of a device to a fraud event; based on said proximity, determining that the device is high risk for fraud involvement; identifying one or more user accounts associated with the device; and identifying one or more potential victim accounts from the one or more user accounts associated with the device.
Another aspect of the invention is directed to a method for fraud containment. The method may comprise: identifying one or more fraud perpetrator devices; determining a behavioral profile of the fraud perpetrator device based on interactions between the fraud perpetrator device and one or more known victim accounts; and comparing the behavioral profile with the fraud perpetrator device with interactions between the fraud perpetrator devices and other accounts, thereby identifying additional potential victim accounts.
A method and system for fraud containment may be provided in accordance with an additional aspect of the invention. These implementations may comprise steps and modules for: determining a proximity of a virtual representation of an individual to a fraud event; based on said proximity, determining that the virtual representation is high risk for fraud involvement; identifying one or more user accounts associated with the virtual representation; and identifying one or more potential victim accounts from the one or more user accounts associated with the virtual representation. A virtual representation, which may be also referred to as digital identities anywhere else herein, corresponds to an individual and may take into consideration any devices, accounts and/or other characteristics described elsewhere herein which are associated with the individual. The invention provides methods and systems for the assessment and determination of a level of risk or trust (or confidence) for such virtual representations in the same ways described herein for one or more devices, individuals or accounts.
Other goals and advantages of the invention will be further appreciated and understood when considered in conjunction with the following description and accompanying drawings. While the following description may contain specific details describing particular embodiments of the invention, this should not be construed as limitations to the scope of the invention but rather as an exemplification of preferable embodiments. For each aspect of the invention, many variations are possible as suggested herein that are known to those of ordinary skill in the art. A variety of changes and modifications can be made within the scope of the invention without departing from the spirit thereof.
All publications, patents, and patent applications mentioned in this specification are herein incorporated by reference to the same extent as if each individual publication, patent, or patent application was specifically and individually indicated to be incorporated by reference.
The novel features of the invention are set forth with particularity in the appended claims. A better understanding of the features and advantages of the present invention will be obtained by reference to the following detailed description that sets forth illustrative embodiments, in which the principles of the invention are utilized, and the accompanying drawings of which:
While preferred embodiments of the invention have been shown and described herein, it will be obvious to those skilled in the art that such embodiments are provided by way of example only. Numerous variations, changes, and substitutions will now occur to those skilled in the art without departing from the invention. It should be understood that various alternatives to the embodiments of the invention described herein may be employed in practicing the invention.
The invention provides systems and methods for fraud containment. Systems and methods described herein may maintain the integrity and security of online communities. Various aspects of the invention described herein may be applied to any of the particular applications set forth below or for any other types of data handling or fraud detection system. The invention may be applied as a standalone system or method, or as part of an integrated electronic transaction system. It shall be understood that different aspects of the invention can be appreciated individually, collectively, or in combination with each other.
Systems and methods for detecting physical devices that interact with a group of potential victims over an electronic network in support of fraudulent activities may be provided in accordance with an aspect of the invention. Such systems and methods may perform one or more of the following: (i) identify circles of at-risk customers targeted by a common physical device; (ii) profile the behavioral interaction between the device and individual victims and between the device and the circle of victims as a whole; (iii) identify devices that acted as an accomplice in support of confirmed fraud even when the fraud transaction did not occur over an electronic network or the device was not directly involved in the fraudulent transaction; (iv) identify devices that may have participated in the compromise of an account whose credentials have been determined to have been stolen; (v) use at-risk victim circles to assist in prioritizing and directing rapid-response and attack-containment activities; (vi) use the size and risk of at-risk victim circles to assess and quantify the threat/vulnerability level of the network as a whole; and (vii) expand the scope of monitoring coverage to cover the combined networks of multiple organizations.
One or more of the steps described herein may occur automatically without requiring human intervention. Systems may include a processor that may execute a program capable of performing one or more of the steps. In some instances, one or more of the steps may be performed manually and/or may involve human interaction.
The system 10 for fraud containment may include one or more subsystems that may perform one or more steps for fraud containment. The system may be capable of performing one or more computer-implemented methods or steps. The system may be provided on and/or implemented by one or more devices. A device may be a computer, such as a personal computer, client-side computer, server computer, laptop computer, tablet, mobile device (e.g., smartphone, cellular phone, personal digital assistant). A device (such as those used for fraud containment) may include a processor and a memory. The memory may include storage for data, which may include non-transitory computer readable media such as code, logic, or instructions for performing one or more step. Algorithms may be stored in memory. The processor may be capable of carrying out one or more steps described herein.
In some embodiments, a device may be a virtual representation of an individual or entity. In some instances, the individual or identity may be a fraudster. A device may provide a virtual representation of a fraudster. A device may be a proxy or representation of an individual or entity. Any descriptions herein may apply to other proxies of individuals, and vice versa. For example, an email address may be used in person-to-person payments, which may be used as representations of individuals involved. Any identifier, such as email addresses, names, credit cards, phone numbers, addresses, usernames, passwords may be used as a proxy. One or more proxies may be identified and/or associated with a fraudulent transaction or potential fraud.
In some embodiments, the system 10 may be implemented using a single device. Alternatively, the system may be distributed over a plurality of devices. The subsystems may be implemented together on a single device, or may be distributed over a plurality of devices. In some instances, each subsystem may be implemented on its own device. Alternatively, some subsystems may share devices. One or more programs may be provided in memory that may assist with carrying out the functions of the one or more subsystems.
A group tracking system 100 may be a subsystem of the fraud containment system 10. The group tracking system may create and maintain groups of accounts (and/or records of such accounts) accessed by the same device. The group tracking system may store and/or track account information. The account information may be grouped by devices that have accessed the accounts. In some instances, device information may be stored. Account information for accounts that have been accessed by the device may be associated with the device. Such accounts may be grouped together.
Information about account and/or device activity may be stored in the group tracking system 100. Such information may include online logins 102 and online account maintenance events 104. Online logins may include times that a user logged in, characteristics of a device the user used to log in, identifying information that a user used to login, or characteristics associated with the login or authentication procedure (e.g., number of times a password was entered/login attempts made, timing of password, etc.). Online account maintenance events may include activities performed by a user in the account, how the user used the account, settings of the account, any activity associated with the account, checks performed on the account. Such user login and account information may be stored through the group tracking system, along with device information.
Device information may include one or more characteristics of the device, such as network address (e.g., IP address), browser ID, device clock information, or settings associated with the device. Device information may be associated with related account information. In some instances, a device may be associated with a single account of a plurality of accounts. In some instances, an account may have been accessed by a single device or a plurality of devices. A plurality of accounts may have been accessed by a single device or a plurality of devices. Such information may be stored in a memory of the system.
A confirmed fraudulent transaction system 110 may be another subsystem of the fraud containment system 10. The confirmed fraudulent transaction system may discover devices which may have acted as accomplices in support of confirmed fraudulent transactions. In some instances, a fraudulent transaction may be detected and/or confirmed. One or more account involved in the fraudulent transaction may be identified. Devices associated with the transaction and/or the account may be identified. Such associated devices may be assessed to determine likelihood of involvement with the fraud. A risk assessment may determine the likelihood that one or more of the associated devices acted as accomplices in support of the fraudulent transaction.
Information about transaction and/or device activity may be stored in the confirmed fraudulent transaction system 110. Such information may include notification of confirmed fraud 112. The notification of the confirmed fraud may include information about the fraudulent transaction. Information such as time of the fraudulent transaction, accounts involved with the fraudulent transaction, devices associated with the accounts, devices active at or around the time of the fraudulent transaction, or behavioral profiles associated with the fraudulent transaction may be included. Such information may be stored in a memory of the system. In other embodiments of the invention, such information may include notification of untrusted or risky devices. It may be beneficial to store in the same system, or in a separate at-risk or “possible” fraudulent transaction system, similar types of information related to transactions, accounts etc. involving untrusted devices that are assessed with a level of risk above a predetermined threshold or below a selected confidence level.
Additionally, a confirmed credential theft system 120 may be a subsystem of the fraud containment system 10. The confirmed credential theft system may discover devices which may have acted as accomplices in support of observations of confirmed credential theft system. In some instances, a theft of credentials may be detected and/or confirmed. One or more account involved in the credentials theft may be identified. Devices associated with the theft and/or the account may be identified. Such associated devices may be assessed to determine likelihood of involvement with the theft. A risk assessment may determine the likelihood that one or more of the associated devices acted as accomplices in support of the credential theft.
Information about theft and/or device activity may be stored in the confirmed credential theft system 120. Such information may include notification of confirmed stolen credentials 122. The notification of the confirmed stolen transaction may include information about the credentials that were stolen. Information such as accounts associated with the credentials, accounts active at the time credentials were stolen or used, devices associated with the accounts, devices active at or around the time credentials were stolen or used, or behavioral profiles associated with the theft may be included. Such information may be stored in a memory of the system.
A profiling system 130 may be provided as a subsystem of the fraud containment system 10. The profiling system may profile devices and accounts. The profiling system may receive information from one or more of the group tracking system 100, confirmed fraudulent transaction system 110, or the confirmed credential theft system 120. Such information may be aggregated and/or combined in order to analyze behavior related to the devices and/or accounts. Such information may also be used to analyze behavior related to suspected or confirmed fraudulent transactions and/or thefts of credentials. Such analysis may assist with the determination of the likelihood that a device was associated with a particular fraudulent transaction and/or theft of credentials.
A circles system 140 may be an additional subsystem of the fraud containment system 10, which may be useful for the profiling of devices across circles of accounts which they access. The circles system may receive information from the profiling system 130. The circles system may analyze which accounts they have accessed. The accounts may be grouped into circles. In some instances, circles of accounts may share one or more common characteristic. Examples of such characteristics may include but are not limited to demographics of account users (e.g., age, location, socioeconomic status, race, gender, credit card company), habits of the users, uses of the accounts, types of account, entities associated with the account (e.g., financial institutions, commerce sites), frequency of account use, other accounts or sites accessed by users of such accounts, or any other common characteristics of account users or accounts.
Thus, devices may be profiled, not only in relation to single accounts, but in relation to circles or groups of accounts. Some devices may be found to act in a particular manner with respect to certain circles of accounts. For example, some devices may be found to have a particular behavior for bank accounts of wealthy individuals at a particular location, which may be notes and used in the assessment of risk.
Information from the circles system 140 may be used in one or more of the following systems: request risk assessment system 150, response prioritization system 160, or risk aggregation system 170. Such systems may be subsystems of a fraud containment system 10.
A request risk assessment system 150 may use account and/or device risk factors to assess the risk of customer requests. For example, in previous subsystems, risks of fraud (e.g., transaction, stolen credentials), may be provided for an account and/or device. The likelihood of fraud may go up or down depending on the combination of a device with a particular account or particular type of account, or vice versa. The risk associated with a particular request may be assessed. For the particular request, the device involved in the request or associated with an account making the request and/or information about the account associated with the request, or a device involved in making the request may be considered in assessing risk.
Any number of degrees of separation between an account and/or device involved in the particular request and additional accounts and/or devices that may have been involved or not involved in fraud may be considered. For example, zero degrees of separation (e.g., only looking at the particular account and/or device involved in the request), a single degree of separation (e.g., looking at other accounts or devices directly associated with accounts and/or devices involved in the request), two degrees of separation (e.g., looking at accounts or devices directly associated with other accounts or devices directly associated with accounts and/or devices involved in the request), three degrees of separation, four degrees of separation, or more may be considered.
Behaviors associated with the account and/or device in making the request, and/or in combination with any degrees of separation may be considered. For example, particular behaviors may raise a red flag and elevate the risk of fraud.
A risk score 152 may be generated for a customer request. In some instances, the risk score may have a numerical value. For example, the risk score may be a number between two other numbers along a scale, such as a number between 1 and 100 or between 1 and 10, or between any other numbers. The risk score may have a qualitative value. The risk score may or may not have a label associated with the risk (e.g., high, medium, low risk). One or more visual indicator may be associated with a risk score (e.g., the number, label, a color (e.g., red high risk, green low risk), size, graphs, charts, lines, percents). The risk score for a request may be calculated based on the devices, accounts, and/or behaviors associated with the particular request. Indicators of fraud associated with the devices, accounts, and/or behaviors associated with the request may raise the risk score. For example, if the device involved in making the request was involved in or suspected of being involved in fraud, the risk score may be raised higher. If the behavior in the particular request mirrors behavior involved in a known fraud transaction, the risk score may be even higher.
A response prioritization system 160 may be used for prioritizing and directing rapid response activities. In some instances, the response prioritization may or may not depend on a risk score 152 for a particular request. In some instances, a response prioritization may consider the likelihood of fraud, and/or the number of potential victims associated with the fraud. For example, a higher likelihood of fraud may increase the priority for a response. A larger number of potential victims associated may also increase the priority for a response. A larger likelihood magnitude of fraud effects (e.g., large amounts of money involved in the fraud) may further increase priority for a response. Such factors, such as likelihood of fraud, number of potential victims of fraud, magnitude of fraud results may be weighted in order to determine the priority of a response.
A recommendation for groups of accounts for blocking 162 may be made based on information from the response prioritization system. For example, a response prioritization system may prioritize actions that may be taken and accounts or groups of accounts on which the actions are to be taken. The highest priority actions may be recommended to be taken first. For example, if taking action on a particular individual account or a group of accounts will alleviate a high likelihood of fraud, large number of victims, and/or large magnitude of fraud results, action may first be taken on that group of accounts over another group of accounts which may have lower risk, smaller number of victims, and/or lesser magnitude of fraud effects.
A group of accounts in such a situation may be an account circle. An account circle may be associated with potential victim accounts. For example, if a high threat is detected for a particular victim circle, extra safeguards may be put into play for the victim circle, or the victim circle accounts may be frozen until further assessment and/or actions can be taken. Moreover, blocking of corresponding devices or untrusted devices to such account(s) can be implemented as described elsewhere herein. An account circle may be associated with potential fraud perpetrator accounts. For example, if a perpetrator circle is determined to present a high threat, such accounts may be frozen to prevent the perpetrator accounts from being used in further fraudulent actions.
For example, a bank or financial institution may be under attack and instruct the response prioritization system 160 for prioritizing and directing rapid response activities. A recommendation for groups of bank accounts for blocking 162 may be made based on information from the response prioritization system. A limited or targeted block of selected accounts within an accounts (victim) circle may be implemented while simultaneously allowing transactions associated with all other accounts to continue uninterrupted. This type of surgical blocking against a subgroup of accounts deemed a threat may avoid having to place a total hold on all accounts thereby allowing banking to continue as usual for other accounts that may represent a vast majority of its customers. By establishing a targeted or surgical block, the bank would not be required to shut its door completely or decline access to all accounts. For some implementations, the bank could designate a third party to issue instructions for such surgical locks on behalf of the bank.
A risk aggregation system 170 may be useful for aggregating risk factors from account circles to determine channel vulnerability and risk. Risk factors, such as those previously described, may be used to determine risk for a particular channel. The particular channel may be at risk as a victim channel, or may be a fraud perpetrator channel.
Threat-level metrics for an online channel 172 may be provided based on information from the risk aggregation system. Threat-level metrics may include a value or a series of values that may determine risk associated with an online channel.
A fraud containment system 10 may be capable of receiving information about user accounts (e.g., logins, maintenance events), devices, and/or confirmed fraud (e.g., fraudulent transactions and/or stolen credentials). The fraud containment system may analyze and/or aggregate the data and may provide information relating to a risk score for a particular customer request, recommended groups of accounts for blocking, and/or threat-level metrics for an online channel. It shall be understood that the aforementioned generation and analysis of risk score values and scales can be equally applicable to and interchangeable with other aspects of the invention herein in calculating and assessing degrees of separation, risk and proximity.
A fraud event may be detected 200. In some embodiments, a suspicion of a fraud event may be formulated. The fraudulent event may be confirmed. In some instances, the fraudulent event may be confirmed with a threshold certainty. In some instances, a fraudulent event may be confirmed when there is 100% certainty of fraud. Alternatively, a fraudulent event may be confirmed for any other threshold value, such as about 99% or higher, 95% or higher, 90% or higher, 85% or higher, 80% or higher, 75% or higher, or 70% or higher. In some instances, detecting a fraud event may include suspecting fraud with a certain degree of certainty.
A fraud event may be detected when one or more conditions are fulfilled. A fraud may be detected when one or more indicators of fraud are met. For example, if a sudden burst of financial activity occurs in a user's account in a geographic location far from the user to purchase many of the same items, fraud may be suspected. A user or other entity may confirm that a fraud event has occurred. For example, a user may confirm that the user's account was used to purchase an item that the user did not order.
Examples of fraud events may include a fraudulent transaction, or stolen credentials. Fraud may be based on information obtained through “scams” or deceptive practices developed to gain personal, confidential and/or financial information.
For example, a common technique today known as “phishing” involves gaining personal information from an individual to commit identify theft by typically using fraudulent e-mail messages that appear to come from legitimate businesses. “Phishing” can be defined as the act of sending an e-mail to a user falsely claiming to be an established legitimate enterprise in an attempt to scam the user into surrendering private information that will be used for identity theft. The e-mail often directs the user to visit a website where they are asked to provide or update personal information, such as passwords and credit card, social security, and bank account numbers, that the legitimate organization already has. But the website to which the user is directed is phony and established to steal the user information during a fake session. For example, a widely recognized website, e.g., eBay, can be targeted in a phishing scam whereby users received e mails supposedly claiming that the user account is about to be suspended unless they clicked-on a provided link and updated the credit card information that the genuine website already had. Because it is relatively simple to make a website look like a legitimate organizations site by mimicking the HTML code, people can be tricked into thinking they were actually being contacted by the website and will subsequently go to the fraudulent site to update or provide their account information. Moreover, by spamming large groups of people (or spIMming them which spam sent over Instant Messaging (IM) applications that can include links to fake sites), the “phisher” could rely on a response from at least some percentage of people who actually had listed credit card numbers with the website legitimately. The concept of phishing in general can also referred to as brand spoofing or carding, a variation on the idea whereby bait is set with the hope that some will bite despite most individuals knowing better. By way of these seemingly legitimate e-mails, criminals “go fishing” for information which is in turn later used to gain access to a real account. Such information includes commonly stolen items in identify theft including a personal identification number (PIN), user account name, a credit card number, and an account number.
The criminal act that is often committed after information is “phished” can be ultimately referred to as “account takeover.” These scams are commonly committed by e-mail to users at least partially because millions can be rapidly and efficiently sent to random or selected individuals, but other techniques can involve transmission of a virus through attachments to c-mails. In particular, some viruses can be created to replace the universal resource locator (URL) of a merchant, financial institution or other party commonly stored in a web browser “Favorites” folder. Instead of being routed to an intended legitimate website, the user is sent to a fake or spoofed site where user information is shared unknowingly with a fraudster. Similar in nature to e-mail phishing, another Internet scam referred to as “pharming” seeks to obtain personal or private (usually financial related) information through domain spoofing. Rather than being spammed with malicious and mischievous e-mail requests for you to visit spoof websites which appear legitimate, pharming can “poison” a DNS server by infusing into it false information resulting in a user request being redirected elsewhere. A browser however will indicate the correct website location, which can make pharming a bit more serious and more difficult to detect. A distinction however is that generally phishing attempts to scam people one at a time with an e-mail while pharming allows the scammers to target large groups of people at one time through domain spoofing. Meanwhile, “spoofing” basically includes a variety of ways in which hardware and software can be fooled into operating as if there was a legitimate transaction or exchange taking place. “IP spoofing” more particularly involves trickery that makes a message appear as if it came from an authorized IP address, e.g., e-mails spoofing. As a result, access can be gained to computers through IP spoofing when an intruder sends messages to a computer with an IP address indicating that the message is coming from a trusted host. To engage in IP spoofing, a hacker must first use a variety of techniques to find an IP address of a trusted host and then modify the packet headers so that it appears that the packets are coming from that host.
Malicious software (aka malware) can be also involuntarily downloaded to a computer and designed specifically to damage or disrupt a system by means of a virus or a Trojan horse. A “Trojan horse” is a program that masquerades as a benign application and unlike many viruses, they do not replicate themselves but can be just as destructive. One of the most insidious types of Trojan horse is a program that claims to rid a computer or other device of viruses but instead introduces viruses onto a computer. The concepts relating to fraud detection and prevention can be applied also to other traditional methods of stealing personal information also include e-mail or other means that involve a fake premise or story such as seeking help fleeing from a third world country (e.g., Nigerian scam) or conducting some type of customer service call or transaction (e.g., “Hello, I am from your bank . . . ”).
It shall be understood that the description of fraudulent schemes provided herein is not exhaustive and that additional techniques will be developed in the future to improperly gain access to user information. Additionally it shall be understood that accounts and/or devices may be used in various fraudulent events. Fraudulent events may occur online (e.g., may be performed over a network, may be performed using a device and/or may be performed with aid of a processor). Alternatively, a confirmed fraudulent event need not occur online. For instance, a detected fraud event itself may not involve the use of a device and/or may be performed without the aid of a processor.
After a fraud event has been detected, potential devices associated with the fraud event 210 may be detected. Such devices may have zero, one, two, three or more degrees of separation from the fraud event. Such devices may be used with some sort of representative proximity to the fraud event (e.g., temporal proximity, degree of separation proximity).
In one example, devices somehow associated with the event may be identified. The likelihood of their involvement with the fraud event may be assessed based on one or more factors. A device meeting a larger number of factors may have a greater likelihood of being involved with the fraudulent event. The degree to which the device meets one or more of the factors may affect the likelihood the device was involved with the event. A pattern of behavior of the device and associated accounts may be assessed. A behavioral profile of a device and/or an account may be stored and/or compared to other stored profiles. One or more factors may be weighted in calculating the likelihood of involvement of the device. If a factor is expected to play a greater role in the likelihood that the device was involved in the fraud event, the factor may be given a greater weight.
In some embodiments, a device may meet a predetermined threshold in order to be identified as likely involved in the fraud event. The predetermined threshold may be a score or value depending on how many factors are met by the device and/or the degree to which the device meets the factors. In some instances, a plurality of thresholds may be provided to determine a grade or level of likelihood that a device is likely involved in the fraud event. For example, there may be a high likelihood, a medium likelihood, or low likelihood that a device was involved in a fraud event.
A device may be identified as being a prime instigator of the fraud event. Alternatively, a device may be an accomplice device which may not have been the prime instigator, but that may have somehow enabled a prime instigator to cause the fraud event. Both prime instigators and accomplices may be perpetrators of fraud.
Potential victims may be identified 220. In some instances, potential victims may be identified after identifying potential perpetrator devices. In some instances, if a device is identified as being involved in a fraud event, the accounts associated with or touched by the device may be identified. For example, if the device was used to access an account, the account and/or user of the account may be potential victims.
In some embodiments, the likelihood of an account or associated user being a potential victim may be evaluated based on one or more factors. For example, if the device exhibited behavior with the account that matches other behavior for known fraud events, the likelihood of the account/user becoming a potential victim is increased. The types of activities that may have occurred involving the account that may deviate from normal activities for the account may also be indicative of likelihood of being a fraud victim, even if no verified fraud event has occurred. Additional factors such as frequency of contact between the device and account, type of contact, type of transactions or actions, demographics of a user of the account, or other information may be considered.
In some instances, one, two, three or more potential victims may be identified. The potential victims may be part of one or more victim circle. Potential victims within a victim circle may share one or more characteristics. In some examples, potential victims of a single perpetrator device, or devices associated with a single fraud event may be grouped in to a victim circle. For instance, a victim circle may include accounts that were accessed by the same device. A victim circle may also be organized by user demographics, behavioral characteristics, account activity, related devices or accounts, or any other information.
Victim circles may have any number of potential victims within them. Any level of threat may be associated with individual victims or the victim circles. In some instances, each potential victim may have a calculated risk level. Similarly, in some instances, victim circles may have calculated risk levels.
A fraud containment method may include recommending action based on a threat risk 230. For example, if a risk of threat is considered to be high for a victim circle, it may be recommended that action be taken to protect the victim circle. In another example, if the victim circle has a large number of potential victims, then it may be recommended that action be taken to protect the victim circle.
In some instances, recommending action may include prioritizing which potential individual victims or victim circles receive action first. Furthermore, the suggested course of action may depend on the likelihood of fraud or the type of fraud, weighed against potential inconvenience to users of accounts.
In some embodiments, as previously described, a fraud event may be detected. Suspicious activity may be detected. In some embodiments, the suspicious activity may be confirmed as a fraud event. The suspicious activity may be confirmed as a fraud event by an entity. The entity may be an entity associated with an account. For example, the account may be a bank account, and the entity may be the bank to which the account belongs. Examples of entities may include various individuals, companies, corporations, partnerships, groups, or associations, such as financial institutions, credit card companies, commercial institutions, online communities, online service providers, web site operators, or any other groups. In some instances, the suspicious activity may be confirmed as fraud by an individual. The individual may be a user associated with an account that was involved in the fraudulent transaction. For example, the user may have a bank account, where the user confirms that the user did not make certain transactions. A suspicious event may be confirmed to be a fraud event by a third party. The third party need not be associated with an account. In some instances, a fraud containment system may receive notification of a confirmed fraud event.
In some instances, an event may be suspected to be a fraud event with a certain degree of certainty. One or more factors may be considered when determining the likelihood of a fraud event. In some instances, the likelihood of fraud may have a value along a continuous scale. Alternatively, the likelihood of fraud may fall into one or more predetermined categories or levels. In some instances, when the likelihood of fraud exceeds a predetermined threshold, the event may be considered confirmed as a fraud event.
The fraud event may be any kind of fraud event, such as those described elsewhere herein. The fraud event may include fraudulent transactions, and/or stolen credentials. The fraud event may have occurred online or offline. The fraud event may have been detected online or offline.
After a fraud event has been detected, devices that may have been associated with the fraud event may be identified.
In some instances, a fraud event may be detected. The detected fraud event may be associated with an account 310c. The fraud event may be a confirmed fraud event. In some embodiments, a plurality of devices, e.g., D1, D2, and D3, may have been associated with the account that experienced the fraud event. In some instances, the plurality of devices may have been used to access the account. A user may have used the devices to log into the account.
In some instances, information about other accounts that have been accessed by the devices may be available. In some instances, data about the devices and accounts may be stored and aggregated. Associations between devices and accounts may be stored in memory. In some embodiments, when a fraud event is detected 310c, records of the associated devices 300a, 300b, 300c may be examined. In some instances, records of accounts 310a, 310b, 310d that are associated with the associated devices may be examined as well.
The account records may include records of devices that accessed the accounts, when the devices accessed the accounts, information about the account user(s), how the accounts were used, activity on the accounts, or any other information associated with the accounts. In some instances, the records of the accounts may include one or more indicators that are similar to a characteristic of the fraud event. For example, an account 310b may include one or more indicators that may parallel a record relating to an account 310c associated with a confirmed fraud event. For example, a behavior pattern that was involved with account 310c may also have been exhibited for account 310b. Thus, although no fraud has occurred or been confirmed for account 310b, there may be some similarities that may suggest that fraud has or may occur in the future, or that the device 300a that there may be suspicious activity associated with the device associated in both transactions.
In the example provided in
A fraud event 400 may be provided. In some instances a fraud event may be associated with an account. One or more devices 410a, 410b, 410c may have been associated with the account. The device's proximity or relation to the fraud event may be determined. Based on the device's proximity or relation to the fraud event, the device may be identified as a potential fraud perpetrator.
The fraud event may be a confirmed fraud event. The fraud event may have occurred online. For example, the fraud event may be a transaction that occurred using one or more device. The fraud event may be a transaction that may have occurred over a network, such as the Internet. The fraud may include the transfer or exchange of information. In some instances, the fraud event may include the transfer or exchange of money. In some instances, the fraud event may have occurred offline. For example, the fraud event may include a forged check or bank note. The fraud may incorporate the use of tangible items, such as documents, financial instruments, identification papers, health-related papers, insurance documents, or any other type of tangible item. The fraud may include falsification of information, items, or documents.
The fraud event may be associated with account. The fraud event may be associated with an identity or item that may be associated with an account. For example, the fraud event may include a falsified document, such as a check, which may be associated with an individual (e.g., allegedly the individual's check), that may be associated with an account (e.g., the individual's bank account). The fraud event may be directly or indirectly associated with an account. An account may be provided for services for a user of the account. A user of an account may or may not have a verified or verifiable identity.
One or more devices may be associated with the account. For example, a device may be used to access the account. For instance, a user may log into an account using a computer, mobile device, or other device. The device may be listed as a device that is authorized to access the account. One or more device may be associated with an individual. For example, the device may be used by an individual who may be a user of the account, or who may have accessed the account.
Additionally, one or more devices may be associated with the fraud event. The device may have been detected to have been in use during the fraud event. For example, a device may be used during a fraudulent transaction. The device may be a perpetrator of the fraudulent transaction or may be the recipient of a benefit of the fraudulent transaction. The device may be associated with the fraud event through the account, individual, or any other factor that may tie the device to the fraud event.
A device may have a “proximity” to the fraud event 400. In some embodiments, a plurality of devices may be somehow associated with the fraud event. One or more devices 410a may be in closer proximity to the fraud event than other devices 410b, 410c. In some instances, one or more factors may be evaluated to assess a device's proximity to the fraud event. For example, if the device was used during the fraud event and/or somehow initiated the fraud event, the device may have a closer proximity to the fraud event, than another device that may have been used to access the account at an earlier or subsequent time. Another example of a factor that may be used to determine proximity may be behavior. For example, if the device is in use when unusual account activity occurs, this may be considered a red flag that may increase the proximity of the device to an event, especially if the unusual account activity is tied to the fraudulent account activity. Even if the unusual account activity is not directly tied to the fraudulent account activity, its proximity to the fraudulent account activity may still contribute to bringing a device closer to a fraud event. If the unusual account activity is similar to or mirrors any other account activity that occurred in a similar matter to other fraud events, the proximity of the device to the fraud event may be increased. In another example, even if the event is not unusual, if it fits a behavioral profile that is similar to or mirrors other behavior profiles in other fraud events, the proximity of the device to the fraud may be increased.
Behavioral profiles may be created and/or tracked. For example, a behavior profile may be created for an account. The account activity may be stored and/or tracked. For example, it may be known when the account was accessed. The device information for the account accesses may be tracked. For example, the IP addresses, clock information, geographic location, or settings of the devices used to access an account may be stored and/or tracked. Account setting changes may be stored and/or tracked. For example, changing user identification information, contact information (e.g., addresses, email addresses, phone numbers), privacy settings, passwords, credit card information, bank account information, payment schedules, or authorized devices (e.g., adding new devices, removing existing devices) may be tracked. Account transactions or other activity may be stored and/or tracked. Frequency of account activity, types of account activity, or other information associated with the account activity may be stored/tracked.
In some instances, particular account activity may automatically increase the proximity of a device to a fraud event. For example, suddenly increasing the number of transactions, and changing the address of the beneficiary may be a red flag that may increase the likelihood of a fraud event. In some instances, the account activity in itself may not be overtly suspicious, but when coupled with other factors may increase the proximity of a device to a fraud event. In some instances, aggregated data may be considered to determine which account activities fit a behavior profile that may cause the device to have a closer proximity to a fraud event. Suspicious behavior profiles may be generated based on the aggregated data. When particular behaviors are associated with an increased likelihood of a fraud event, the behavior profiles may be marked as suspicious.
A device that may show up repeatedly at the wrong place at the wrong time may be considered to be a suspicious device, and its proximity to a particular fraud event may be increased. For example, even if it is not understood what role a device may play in a fraud event, the repeated association of a device with potential fraud events, or accounts or individuals linked to fraud events may increase the likelihood the device was somehow involved. For example, a device may repeatedly show up inline in accounts. A day later someone may call a call center and change the contact address or password for such accounts. Even though the device itself was not directly involved in changing the password (e.g., it was done through the call center), there may be a strong correlation between the online appearance of the device and the call to the call center. The aggregation of data may create an opportunity to see such habitual repeating behavior.
A predetermined threshold may be provided, where a device 410a that is closer to a fraud event 400 than the predetermined threshold 420 may have an increased likelihood of being associated with the fraud event. In some instances, if the device has a greater proximity to the fraud event, the device may be identified as a fraud perpetrator. In some instances, a single predetermined threshold may be provided, which may determine whether a device is a fraud perpetrator or not. In some instances, a plurality of predetermined thresholds may be provided which may be used to indicate a likelihood that a device is a fraud perpetrator. For example, devices that cross a closest predetermined threshold may be considered to have a high likelihood of being a fraud perpetrator. Devices that cross a further away threshold may be considered to have a moderate likelihood of being a fraud perpetrator. Devices that cross an even further away threshold may be considered to have a low likelihood of being a fraud perpetrator. Devices that are even further away may be considered to have an extremely low likelihood of being a fraud perpetrator.
A device may be identified as a fraud perpetrator or having a certain likelihood of being a fraud perpetrator. In some instances, the role that a device may have played in the fraud may be identified. For example, the device may be considered a master perpetrator, or may be considered as an accomplice. In some instances, a master perpetrator may be involved in the fraudulent event itself. For example, a master perpetrator may be a device used to access an account and that was used to make a fraudulent transaction. In another example, an accomplice device may be a device that was used for an activity that wasn't the fraud event itself, but that appears to have some relation to the fraud activity (e.g., device used to access accounts, where later a call is placed to a call center to change passwords or contact information for those accounts). An accomplice device may be a device that is at the “wrong place at the wrong time.” An accomplice device may have some sort of conceptual proximity to the fraud event without being directly linked to the fraud event, or the link being unknown.
Activities and/or interactions between the device and the accounts may be tracked. In some embodiments, a first part of the interaction 520a, 520aa, 520b, 520bb, 520c, 520cc, 520d, 520e, 520ee may relate to the type of interaction. For example personally identifiable information (PII) such as a change in customer contact information may be tracked, check fraud (CFRAUD), unfamiliar foreign (UNFML_FORGN), unfamiliar local (UNFML_LOCAL), may be examples of types of interactions. Additional types of interactions may be provided. Any number or types of interactions may be tracked. In some instances, a single type of interaction may be recorded between a device and an account. Alternatively, a plurality of types of interactions may be recorded between a device and an account. In some instances, all applicable types of interactions between a device and an account may be recorded.
A second part of the interaction 530a, 530b, 530c, 530d, 530e, 530ee may represent the role that a device plays. For example, a device 530a may be a direct perpetrator (PERP), which may be a device having a direct involvement with an activity. In one example, the device may have a direct involvement with fraudulent activity. In another example, a device 530e may be a potential accomplice (ACOMP). The device may not directly be involved, but may show up with a close time proximity to the event.
Additional parts of the interaction may be tracked. In some instances, a device may function as a direct perpetrator for a first type of an interaction and as an accomplice for a second type of interaction with the same account. For example, a device 500 may be a direct perpetrator 530ee, for personally identifiable information 520ee, and an accomplice 530e for check fraud 520e for the same device 510e. In other instances, the device may function as a direct perpetrator for multiple types of interactions, or as an accomplice for multiple types of interactions.
Systems and methods may be provided for identifying devices that may have assisted in the compromise of accounts whose credentials have been stolen. Such systems and methods may comprise (i) a system for receiving notifications of confirmed compromised credentials; (ii) a system for identifying devices that logged into the compromised accounts; and (iii) a system for retrieving the device risk profiles and scores calculated by systems and methods described herein. Such systems and methods may be useful for determining potential fraud perpetrator devices. The likelihood of a device being a fraud perpetrator may be assessed based on the device risk profiles.
In some embodiments, methods and systems may be provided for assessing the confidence level or level of trust for one or more devices. These can be used to identify a physical device and determine its suitability for linking together accounts accessed by a common device. In some instances, the confidence level or level of trust may be used in determining whether the device was involved in fraud. An increased confidence level for identifying a device may increase the confidence level of whether an assessment of whether the device is involved in fraud is accurate. Moreover, a method and system may be provided for determining the likelihood that a device logging into an account was an accomplice in confirmed fraud reported against an account. An increased confidence level or level of trust for identifying a physical device may also increase the likelihood that an assessment whether a device was an accomplice is accurate.
As relationships between devices and accounts are identified, potential victims may be identified. Once devices who have potentially been involved in fraud have been identified, potential victims may be identified based on the interactions between such devices with various accounts. The types of interactions and behavior profiles between the devices and accounts may be stored and/or tracked. Such stored information may be useful for identifying potential victims, based on the relationship between the devices and accounts.
In some instances, single victims may be identified based on a relation between a device and the account. For example, if the device is known to be involved in fraudulent activity, any account associated with the device may be automatically considered a potential victim. In another example, additional factors may be considered in determining whether the account is a potential victim. For example, even if no fraud event has yet been detected at the account, if the device-account interactions fall within a set of suspect interactions, the likelihood that an account is a potential victim may increase. For example, certain interactions may be flagged as being potentially suspicious. For example, sudden password changes coupled with other account activity may indicate an increased likelihood that the account is a victim account.
In another example, behavior between the device and account may be compared to other behavior profiles to determine whether there is an increased likelihood that the account is a victim account. The compared behavior profiles may be between the same device and other accounts. The other accounts may include accounts for whom known fraud events have occurred, or for whom there is a high likelihood that fraud has occurred. The compared behavior profiles may also be between other devices and other accounts. The other accounts may include accounts for whom known fraud events have occurred, or for whom there is a high likelihood that fraud has occurred. The other devices may include devices who have been identified as fraud perpetrator devices, or who have passed a predetermined threshold to have a particular likelihood of being a fraud perpetrator device.
In some instances, victim circles may be identified. Victim circles may include one or more victims who may have one or more shared characteristic. In some instances, a victim circle may include potential victims of the same device. For example, the common characteristic may be that each of the victims within the victim circle may have interacted with the same device, or that fraud may have been perpetrated by the same device. The same device may have perpetrated the fraud as a direct perpetrator or as an accomplice. The same device may have been used to log into the accounts.
Other examples of potential common characteristics may include demographics of a user of the account, relationships between users of accounts, account access location, account access time zone, frequency of account access, behavioral trait of account, type of account, entity with whom the account is affiliated, financial transactions associated with accounts, or any other characteristics.
In some instances, a degree of risk for a victim may be assessed. In some instances, there may be only two degrees of risk (e.g., is a victim, is not a victim). In some instances, three or more degrees of risk may be provided (e.g., high likelihood of being a victim (+), moderate likelihood of being a victim (·), or low likelihood of being a victim (−)). In some instances, the degree of risk of being a victim may be a numerical value (e.g., between 1 and 10, between 0 and 100). The degree of risk may be continuous along a scale, or may have discrete values. In some instances, each potential victim within a victim circle may have an assessed level risk. The level of risk for various victims within a circle may be the same or may vary.
In some embodiments, the overall threat level for a particular victim circle may take the risk level of the member victims into account. For example, a victim circle having more potential victims with a higher risk level may have an increased threat level compared to a victim circle where the member victims have a lower threat level. In one illustration, Victim Circle 2600b has members with a higher risk level (+) than members of Victim Circle 3600c (−), which may suggest that Victim Circle 2 has a higher threat level than Victim Circle 3.
When assessing the threat level for victim circles, additional factors may be considered. For example, the potential impact of the threat (i.e. in addition to the number of victims in the circle) may be considered. The potential impact may include a financial amount. For example, if larger value financial transactions or more frequent financial transactions are occurring, the threat level may be elevated. Additional potential ramifications that may be considered are whether there is any threat to safety or security. Various types of fraud threats may be prioritized.
Factors in assessing the threat levels of individual victims and/or victim circles may be weighted and/or prioritized. For example, the size of the victim circle may be given greater weight than the risk level for the member victims. In such an example, Victim Circle 1600a having a larger number of potential victims may have a higher threat level than Victim Circle 2600b. In another example, the risk level for the member victims may be given greater weight than the number of potential victims. In such an example, Victim Circle 2 having higher risk levels for its member victims may have a higher threat level than Victim Circle 1. Any number of factors may be considered and/or weighted to determine threat levels for the various victim circles.
Systems and methods for identifying circles of at-risk customers targeted by a common physical device may comprise (i) a system for identifying physical devices accessing victims over an electronic network; (ii) a system for assessing the confidence level in the identifying the device and the validity of a victims circle associated with it; and/or (iii) a system for maintaining counts of interactions between the device and each potential victim.
In some instances, the system may keep a running count of each interaction between a device and an account. The counts may be kept for all transactions, regardless of whether a device has been identified as a potential fraud perpetrator or whether an account has been identified as a potential victim. The interactions between various devices and accounts may be tracked and/or counted. In another example, the running count may be kept for only selected devices and/or accounts. For example, running counts of interactions may be kept after a device has been identified as a potential fraud perpetrator device, or as a confirmed fraud perpetrator device. The counts may be kept between the device and all accounts that the device interacts with (e.g., regardless of whether the account is a potential victim). In another example, the counts may be kept for interactions between the device and accounts that have been identified as potential victims (e.g., that have reached a threshold or likelihood of being a victim).
Systems and methods for profiling the interaction between a device and individual potential victims and the device and the circle of victims may be provided. Such systems and methods may further comprise (i) a system for keeping counts and other statistics of the device interactions with individual accounts; (ii) a system for maintaining counts and other statistics of the device interactions with the victim group as a whole; and (iii) a system for executing rules that associate risk levels with specific combinations of statistics.
In some instances, the counts and/or statistics between a device and individual accounts that form a victim group may be added and/or aggregated to determine counts and/or statistics between the device and the victim group. For example, a running count may be kept of the number of interactions between a device and a first account, and a device and a second account. The number of interactions may be tracked separately for each account. The first and second account may belong to the same victim group. The counts for the first and second accounts may be added to determine counts for the victim group. Alternatively, separately, counts may be kept for a group, so when a count is added for a member of the group, the count is automatically added to the group as well. Examples of statistics may include the number of interactions, the interactions over time, average interaction rate, types of interactions, or additional statistics.
A method may be provided for aggregating risk scores from a circle of victims associated with the same device. For example, the member victims of a circle may be associated with the same device. The interactions between the device and the member victims may be counted and added for the victim circle. In another example, a risk score may be assessed between the device and each member victim. The individual risk scores may be added to form an aggregated risk score between the device and the victim circle.
In some embodiments, a method for aggregating risk scores from multiple circles of victims to assess the threat level associated with the entire network may be provided. For example, a risk score for individual victim circles may be calculated. The individual victim circles may be associated with the same device or with different devices. The various victim circles may or may not be associated with the same device. A risk score may be assessed between a device and each victim circle. The individual victim circle scores may be added to form an aggregated risk score for the entire network.
After threat levels for individual victims and/or victim groups have been assessed, a response to the threat may be determined. In some instances, depending on the threat level, a priority of response may be determined. For example, higher threat levels may be addressed first. In some instances, limited resources may be available that may result in certain threats being addressed first, before additional threats are addressed. Once resources are freed up after addressing the first prioritized threats, the resources may move on to address subsequent prioritized threats. In some instances, the threat priority may be adjusted in real-time. In some instances, threats may be addressed manually with human intervention, or automatically without human intervention. For example, an assessment may be made by an individual whether to freeze particular accounts in response to suspicious activity. Alternatively, a processor may determine based on analytics to automatically freeze one or more account.
In some instances, responses may be prioritized or timed based on the status of the threat. For example, in some instances, further observation may be warranted before any response is instituted. Such victims or victim circles may be monitored under it is determined that the time is ripe for a response.
The type of response to a potential fraud threat may also be determined. For example, account activity may be monitored, or frozen. Access to accounts may be cut off for one or more particular devices. Access for accounts may be granted only to particular approved devices. Certain types of account activity may be permitted while others are not. Additional responses that may not involve online actions may be provided. For example, if bad checks are detected, notifications may be provided one or more entities warning of the bad checks.
In some instances, a recommendation may be made for the response to the assessed threat(s). The recommendation may or may not be followed. The recommendation may be made automatically without requiring human interaction (e.g., with aid of a processor). Alternatively, human involvement may be provided in making the recommendation, or in determining whether to follow the recommendation. In some instances, a recommendation may automatically be followed after it is formulated.
Systems and methods described herein may use at-risk victim circles to assist in prioritizing and directing rapid-response and attack-containment activities. Such systems and methods may further comprise (i) a system for retrieving the victim circles identified as high risk; and/or (ii) a system for serving the list of accounts included within the victim circles identified as high risk.
In some embodiments, systems and methods may be provided for assessing the threat/vulnerability of individual victims, individual victim circles and the network as a whole. The systems and methods may also include (i) a system for weighting the risk scores of individual victim circles and aggregating the number of accounts included in them; and (ii) a system for reporting the aggregated results.
Additionally, there may be expanded monitoring coverage for combined networks of multiple organizations. Such systems and methods may further comprise (i) a system for translating reported events to a common standard enabling uniform description of contributing organizations and event types; and (ii) a system for enforcing data-sharing policies and preventing inadvertent disclosure of unpermitted information.
The online organizations connected to the one or more user devices may be any sort of host, such as an electronic commerce business, an online merchant, a financial institution, or any other type of website service provider that may provide a service to a user or may interact with a user device. An online organization and a user device may perform an electronic transaction, such as a purchase of a product or service, such as online banking. In accordance with one aspect of the invention, each electronic transaction may be susceptible to fraud and each user device or user can be identified to reduce the risk of fraud. In some instances, online organizations may have their own networks or be fraud-detecting entities.
The connection between a user device and an online organization may be, for example, a connection between a client computer and a website server over a network (see
When a user device is communicating with the consortium, the device memory may store an operating system (OS) and a browser application. For example, the operating system may operate to display a graphical user interface to the user and permit the user to execute other computer programs, such as the browser application. The browser application, such as Microsoft Internet Explorer, when executed by the processor, permits the user to access the World Wide Web as is well known. The user device may interact with an online organization that is part of the consortium, which may perform some fraud prevention and detection functions and may generate a device identifier derived from information gathered about the user and/or user device in accordance with the invention. The user device may or may not be involved in fraudulent transactions. The confidence with which the system may track the identity of a user device may assist with determining whether the device is a fraud perpetrator.
In some embodiments, an online organization may have one or more web-based server computers, such as a web server, an application server, a database server, etc., that are capable of communicating with a user device over a network, such as the Internet or a wireless network, and are capable of downloading web pages to the user device. In some implementations, the online organization may comprise one or more processors, one or more persistent storage devices and a memory. For the online organization to interact with the user devices, the memory may store (and the processor(s) may execute) a server operating system and a transaction processing software system to facilitate an electronic transaction between the online organization and one or more user devices. Each online organization may further comprise a database, such as a database server or a data structure stored in the memory of the online organization, that stores the electronic transaction data for the online organization. In some embodiments, a server for an online organization may have greater computing or processing power than a user device. Similarly, the server may have more memory than a user device.
The online organization may control each device and/or each user's access to the resources of the online organization by, for example, denying access to a user or device in particular circumstances. For example, if a user device has been implicated in fraud, an online organization may prevent a transaction with the user device from occurring. In another example, if a user has a ‘bad’ or ‘low’ rating, an online organization may prevent the user from participating in an electronic sales forum. If a user device has been implicated in fraud, the device interactions with various accounts of the online organization may be monitored. Past interactions may be reviewed and current interactions may be stored as they occur. Further potential victims of fraud may be identified.
In a preferable embodiment of the invention, the online organizations may be connected to a fraud repository. The fraud repository or fraud detection monitor that is part of a fraud detection consortium may be connected to the online organizations over a network. If the central repository is connected to the network, then the data between the online organizations and the fraud repository may be encrypted or may travel over a virtual private network to ensure privacy and security.
Thus, the fraud repository may receive user and/or user device information from each online organization, which may collect user or user device information from each user device during an online transaction. The fraud repository may also receive information about user accounts and interactions between devices and accounts. Behavioral profiles relating to device and/or account activity may be received as well. In some instances, interaction counts between devices and individual accounts or account circles may be received at the fraud repository. Interaction counts or profiles between potential fraud perpetrator devices and individual victims and/or victim circles may be received at the fraud repository. For example, a banking consortium of any number of members may be established for sharing fraud-related data, shared-monitoring of behavior, including counting the number of accounts accessed by the same device across multiple banks. Although in some instances a fraudster may not have accessed enough accounts in any single bank, shared insight may result from the ability to detect the behavior across banks in the aggregate. In some embodiments of the invention, one or some members of the consortium could be delegated the responsibility of identifying risky or untrusted devices, while others could handle other steps and processes described herein such as counting or tracking the number of accounts accessed by a device across banks. It shall be understood that any of the described methods or functions of the fraud repository or consortia members are not necessarily carried out by a single entity but rather such functions may be separated and divided up among its members, their customers or designated third parties.
The repository may store some or all of the information received. In some implementations, the fraud repository may generate a device identifier that identifies each user device. In some cases, the device identifiers may be unique identifiers for each user device. In other cases, the device identifiers may not be unique for each user device, but may be derived from information gathered about a user and/or user device which may or may not be duplicative in another user device. In some cases, a device identifier may function as a “fingerprint” of a user device, and include various parameters derived from gathered information about a user and/or user device to be discussed in greater detail below.
The fraud repository may use a device identifier to determine whether a device described through a first online organization is the same as a device described in a second online organization. This may assist with identifying whether a device is involved in fraudulent transactions. The behavior of a device may be tracked across multiple organizations. If a device is identified as a fraud perpetrator potential victim circles may be determined. In some instances, a victim circle may have been identified for a particular device through a first online organization. An additional victim circle may have been identified for the same device through a second online organization. Information about the victim circles may be shared and/or combined. Similarly, identifying a potentially fraudulent device in a first organization may assist with determining a victim circle associated with the device at a second organization. The sharing of information may assist with identifying potential fraud perpetrators and/or victims. As with other embodiments and aspects of the invention, the concepts herein not only apply to confirmed fraudulent devices, but also to untrusted, risky devices or those devices assessed with a high level of risk or threat.
Using the identification information in accordance with the invention, the fraud repository may be able to detect fraudulent activities across the consortium. In particular, the fraud repository may provide a centralized service utilizing this invention to identify user devices, store user and device information, track end-user logins, associate an end-user account with one or more specific devices, associate a device with one or more end-user accounts, associate a device or end-user with fraudulent activity, and share this information with each online organization of the consortium. The fraud repository may include a centralized database.
Any action taken within a fraud detection consortium may be directed by computer readable media, code, instructions, or logic thereof. These may be stored in a memory, such as the memory of a fraud repository or the memory for an online organization.
In one example, a user computer, such as A1, may request access to the fraud detection consortium and a particular online business, such as A. To gain access to A, complete a transaction, or access a particular part of the network, a user may connect through a user device, which in this case may be user computer A1. The online business A may receive user and/or user information from the user computer and may then pass the information to the fraud repository. The online business may or may not store the information gathered through the user device that is passed onto the fraud repository.
In some implementations, the fraud repository may generate a computer identifier which may be derived from the information gathered. In other implementations, a computer identifier may be generated at different stages. For example, an online business A may gather information from A1 and may generate a computer identifier for A1, and may pass the computer identifier to the fraud repository. The online business A may only pass the computer identifier, may only pass gathered information, or may pass a combination of both to the fraud repository.
Information or data, such as a computer identifier, raw data, data used to make up the computer identifier, or any combination thereof may be stored in “pairs.” Any type of data may be coupled with the same or different type of data when stored in memory. The paired data may be linked within memory where they are stored, or may have some other mechanism that associates them with one another. In one example, an email address and a computer identifier may be stored as a pair. The email address and computer identifier may be stored in memory together, as a unit of data. Alternatively, they need not be stored together but may include pointers that associate them with one another. Although the term “pair” may be used, any number of data items may be linked in memory. For example, two, three, four, five, six, seven, eight, ten, twelve, fifteen, twenty, thirty, forty, fifty, eighty, one hundred, two hundred, or more items may be linked in memory. As discussed in greater detail below, any of these linked sets of data may be shared together.
In one embodiment, the fraud repository may store some or all of the information. For example, the fraud repository may store all of the information gathered by online business A, B, C, D, and any other businesses in the consortium. Online businesses A, B, C, and D may or may not also store the information that is stored by the fraud repository. The fraud repository may share some or all of the information gathered or generated, such as computer identifiers, detected fraud information, or potential victim information with the online businesses of the consortium.
In an alternate embodiment, the fraud detection monitor or repository may facilitate transfer of information between one or more online business without actually storing the gathered information. For example, information gathered by online business A may be stored on A's server, and information gathered by online business B may be stored on B's server. The fraud detection monitor may enable transfer of information from A to B, C, D, and any other businesses and so forth for the other online businesses. The fraud detection monitor may also process information, with or without storing it on a fraud detection monitor server, such as generating computer identifiers or detecting fraud from information gathered from one or more online business, and may share this information with the online businesses of the consortium. The fraud detection monitor may detect fraud by cross referencing the gathered information and tracking user and device behavior over time. In some cases, the fraud detection monitor may only store processed information, such as computer identifiers or fraud indicators.
In some embodiments, each online business may represent different private network environments operated by independent organizations that do not share end-user identities. The data storage system, such as a set of databases, used by each online business may be remotely located at the fraud repository and can be a service provided by a third party. Alternatively, online businesses may communicate via a network, such as the Internet, such that end-user identifiers, fraud information, device, and/or account information may be shared.
Another example provides fraud detection and information processing applications distributed across a plurality of computing devices (with no central fraud repository and database). The computing devices may be the online businesses' devices, the user devices, or a combination of the user devices and online businesses, such that each may perform part of the functions of the fraud detection and prevention system in accordance with the invention. For instance, the various online businesses may share information with one another in a peer to peer manner, and may collectively detect fraud and/or identify devices or victims of fraud. In one case, online business A may detect an at-risk user device and share this information with online businesses B, C, D, and so forth. In another case, online business A may detect suspicious user devices and share such information with the other online businesses. Online businesses A, B, C, and D may share information in a peer to peer manner such that they all have access to certain information. Similarly, multiple networks may share information in a peer to peer manner.
Those skilled in the art will appreciate that the fraud detection/containment consortium may be implemented in various different manners that are within the scope of this invention, such that previous discussions are provided by way of example only and are not limiting.
One aspect of the invention provides for multiple consortia that may interact with one another and share information. For example, a fraud repository may communicate with another fraud repository. In some embodiments, information gathered from an online business may be shared between one or more fraud repositories, which may subsequently share the information with the other online businesses that they are connected to. In some implementations, the information shared between a first repository and second repository may be stored by both the first and second repositories before being distributed to connected online businesses. Alternatively, a repository may merely pass on information it receives from another repository. The information may be stored or shared in various ways that are known in the art.
For instance, any information stored by a fraud repository may be stored in one or more database of the fraud repository. In one example, the database may have a database table containing pertinent information. However, the data may be stored in different databases and may include different database data structures that are within the scope of this invention. In this example, a database table may include a host column, a unique user-account name, and a user device identifier column that may permit the fraud detection system to associate a particular host (or online business) with a particular user and a particular user device. As described above, the user-account name may represent end-user accounts that are unique to each host. The user device identifiers may represent user devices that have connected to at least one host. The individual rows in the database table may represent unique combinations of host, user-account names and user device identifiers. In some embodiments, each interaction between a device and an account may be tracked. Each interaction may have its own row in the database. Alternatively, interactions between a device and account may be aggregated into a single row. A count and/or statistics of interactions between the device and account may be recorded in the database.
The database table may enable the same user connecting to a different online business with the same user device to be tracked and registered in the consortium. A great deal of additional information may be maintained such as last successful login date and time, last unsuccessful login date and time, total successful logins, total unsuccessful logins, which accounts were accessed, what activity was performed using the accounts, what account setting were modified, etc. as well as any relevant personal and non-personal information, to be discussed in greater detail below.
As previously discussed, information may be stored in “pairs,” which may refer to any number of data items that may be somehow linked or connected together. A database table, as mentioned previously, may be an implementation of storing data in pairs. In a consortium or multiple consortia, such information may also be shared in “pairs.” For example, a particular host may always link together a credit card number and email address. Such information may be stored and shared as a pair. In some embodiments, each host may have uniform pairs of data that may be shared. For instance, all of the hosts within an online consortium may store together a credit card number and an email address. Similarly, any time a credit card number is shared or tracked across a consortium, an email address may also be shared and tracked with the corresponding credit card number. In another example, a device identifier may be paired with account access and/or activity. In another embodiment of the invention, different hosts may have different pairs of data that are shared (e.g., one host may always pair an email address with a username, and another host may always pair an email address with a credit card number). Any of the data items or types, including device identifiers, or other items discussed herein, may be paired.
When data is stored and tracked as a pair, fraud detection and validation may be improved. For example, if a pair of identifying data is stored, and then the same pair appears again, the device or individual can be identified with greater certainty as the same device or individual. Thus, consortia members may be able to share pairs of information to track a device or user, and/or interactions between a device and an account or other activity.
Based on gathered information, and any information generated by processing the gathered information, such as a device identifier, to be described in more detail, the likelihood of fraud being committed by a particular user with the user computer A1 may be determined and an appropriate action can be taken. Assuming the user computer A1 is granted access to the network, the user computer performs its electronic transaction. If a fraudulent activity occurs during that electronic transaction, that information may also be conveyed to the fraud repository and may be stored by the fraud repository. Alternatively, if fraudulent activity occurs, the information may be conveyed to the other online businesses. In this manner, the one or more online businesses may share fraud information between each other selectively so that a fraud committed against one online business, i.e. online business A, can be logged into and tracked by the fraud repository in accordance with the invention. Alternatively, information about fraudulent activity can be tracked by the consortium of online businesses without analysis by a fraud repository. Thus, a user or user computer that has committed fraudulent activities can be tracked even when the user or user device logs into a different online business, i.e. online business B. Therefore, the fraudulent activities of a user or user computer can be tracked across the consortium.
In some instances, the fraud event may occur and/or be detected while a device is accessing an account and/or a network. In some instances, a fraud event may occur or be detected after the devices accesses the account and/or network. The fraud event may occur online or offline. The device may be identified as having been associated with the fraud event. The behavioral profile of the device may be analyzed to determine the likelihood that the device was involved in the fraud event. Behavioral profiles may be provided to the fraud repository. The fraud repository may make a determination of the likelihood of the device's involvement in the fraud activity based on the collected information. Alternatively, online businesses and/or networks may share the behavioral profile information with one another. Each online business and/or network may optionally make its own determination of whether a device was involved in fraud.
If the device was determined to have been involved in fraud, such information may be shared with all the online businesses of the consortium. The fraud repository may share the information with the various online businesses/networks. Alternatively, the online businesses/networks may share information of fraud perpetrator devices directly with one another.
Similarly, once a fraud perpetrator device has been identified, potential victims may be identified. Information about potential victims may be collected and/or analyzed at a fraud repository. The fraud repository may prioritize and/or determine a response for the potential individual victims and/or victim circles. The fraud repository may suggest courses of actions for the containment and/or prevention of fraud. The online businesses may choose whether to follow such suggestions or not. Alternatively, the online businesses may be required to follow the suggestions. In other embodiments, the online businesses may share potential victim information without requiring a centralized priority and/or response. Each online business may determine its own prioritization and/or course of action in dealing with the fraud threat. The online businesses may or may not share such prioritization and/or courses of action with one another.
Some implementations of using a fraud repository in a consortium may involve repositories capable of handling various tasks. A fraud repository may be one or more stand-alone computing resource, such as a server computer, with a database or storage system, although the functions of the fraud repository and the information storage may be distributed in any number of ways, such as in examples described previously. The fraud repository may include one or more processors, one or more persistent storage devices and a memory. The fraud repository may further include a database server/manager that may store the data in accordance with the invention. The structure and operation of the processor, persistent storage device and memory may be any computing device structure as known in the art. The memory may store a server operating system, and one or more administrator module that are executed by the processor to implement the fraud detection and prevention.
An administrator module may permit an administrator to interact with an online business. For example, an administrator may determine the threshold for enabling a user to interact with the online business if the user may be at risk for fraud. An administrator may also determining a response plan if fraud is detected. In some instances, the response plan may include the prioritization of victims and/or devices that will be addressed. The response plan may include monitoring access and/or activity, or cutting off access and/or certain activity. An administrator may also configure items of the system, adjust query items and update items. An administrator module may also process the data stored or received by the repository, such as to generate a device identifier. An administrator module may enable an administrator to generate a query of, given a particular user device, what users have used that network device or a query that asks, given a particular user, what network devices have been used by the particular user. The administrator may also configure a query that asks, given a particular user device, what other online businesses set this network device to associate users/computers a predetermined number of levels deep or given a particular user, what is that user's current status in the system. An administrator module may perform additional administrative functions such as generating reports from the fraud detection and prevention system and its database.
In some embodiments, hosts, such as online organizations or networks, may be able to individually control their interactions with selected user devices. For example, hosts may set up any number of device and user status levels, and establish any number of behavior patterns/profiles, each of which might require a different action, such as notify a particular email address, page a particular number, deny access to the network, monitor certain actions on or using the account, deny certain actions on or using the account, allow access but change the status of the device, etc. The hosts may also carry out different actions to only certain groups of user devices or on a per device basis. In some cases, each host can establish its own customized rules for every aspect of the present validation method. Because of this, the same circumstances that result in denied access for an end-user for one host may not result in denied access for another host. Such actions may be provided to monitor fraud potential and/or provide fraud containment. Some actions may be provided to help identify fraud perpetrator devices and/or potential fraud victims. One or more device may be tracked to find additional associated fraud perpetrator devices, such as accomplices. Access to one or more high-risk victim account may be cut off to provide fraud containment.
Alternatively, a fraud repository may control a host's interaction with a user device. For example, a fraud repository may determine whether a user device is at risk for fraud and may deny the user device access to the consortium. In some cases, the fraud repository's determination for fraud risk may be uniform for all hosts. Denial of access of the device may prevent the device from being used for future fraudulent activities and may assist with fraud containment. Other preferable embodiments of the invention may allow hosts, or third parties designated by the host(s), to deny access to only certain devices such as risky or untrusted devices (which may be considered herein to be devices associated with confirmed or suspected fraudulent activity that exceeds desired or predetermined levels of risk). For example, a bank or financial institution may be under attack and implement a limited or targeted block of untrusted devices while simultaneously allowing transactions associated with trusted devices to continue uninterrupted. This type of surgical blocking against untrusted devices (or all devices other than trusted devices) would avoid having to place a total hold on all devices thereby allowing banking to continue as usual for vast majority of its customers using trusted devices. By establishing a targeted or surgical block of only some devices, the bank would not be required to shut its door completely or decline access to all devices trying to enter accounts. For some implementations, the bank could designate a third party to issue instructions for such surgical locks on behalf of the bank. Accordingly, fraud containment can be achieved without entirely disrupting all interactions between a host and all user devices.
Identifying information may be used for other applications in addition to fraud detection and prevention or network security. For example, gathered information may relate to a user rating, which may or may not relate to fraud. Such information can be shared across one or more online businesses in a consortium, to track the user or user computer across the consortium. In another example, gathered identity information may have applications in national security and law enforcement.
The information gathered in accordance with the invention may be customized for different user device types. For example, with a personal computer that connects to an online business, the information gathered may include an IP address or browser ID and additional personal or non-personal information to identify the user device. With a cellular phone, it is typically possible to extract data from the cellular phone, such as its serial number, so that only non-personal information may be used to identify the cellular phone network device. For a PDA user device, it may be typically possible to put data/information onto the PDA only so that the certain parameters only may be used to identify the PDA. Thus, depending on the user device, different information may be gathered. In accordance with the invention, information may also be gathered from a hardware device, such as a smart card or PCMCIA card, which may have its own unique identifier that may be used to uniquely identify the card. Thus, information gathering in accordance with the invention may be implemented in a variety of different manners.
A user device's information, which may include risk for fraudulent activity, may be shared with various hosts at various times or manners. Similarly, account information, which may also include risk of fraudulent activity being perpetrated on or though the account, may be shared with various hosts at various times or manners. For example, transaction information (which may include device information and/or account information) may be shared with all hosts whenever a transaction occurs. In another example, transaction information may be shared with all the hosts at particular times, i.e. updating each host every ten minutes, or whatever time an individual host may wish to be updated. Alternatively, transaction information may be provided to a host upon request by the host. For instance, if the information is stored with a fraud repository, a host may choose to automatically update and access repository information whenever a transaction occurs between the host and a user device. In some cases, individual hosts may be able to determine when or how they receive or send shared information. In other cases, information sharing may be uniform across a consortium.
For any of the systems and methods described herein, a consortium may operate taglessly. One or more consortia may be tagless and/or may not require a program to be downloaded to a user device. In some examples, an online host and/or fraud repository may collect information about a user or user device without the use of cookies, text parcels, or programs sent from a server to a client computer. A fraud detection consortium may be able to detect fraud without downloading a fraud detection program to a user device. Rather, a consortium may operate taglessly by collecting information from a user device without requiring a user device to receive any cookies, text parcels, or programs, or download additional applications from any of the hosts or repositories of the consortium. For example, instead of “pushing” an application or tag onto a user device, a consortium may enable data to be “pulled” or extracted from the user device.
In some embodiments, a method for uniformly describing event types and reporting sources so that intelligence from multiple areas and organizations can be interpreted and processed consistently. This may be beneficial for providing information across single networks or combined networks. This may incorporate one or more consortium that may share information useful for the detection and/or containment of fraud.
The devices 800a, 800b, 800c as shown may be network devices used in accordance with any of the concepts of the invention illustrated herein for fraud containment. Network devices may include computers whether they be a personal computer, server computer, or laptop computer; mobile devices, such as a tablet, personal digital assistants (PDAs) such as a Palm-based device or Windows CE device; smartphones (e.g., iPhone, BlackBerry, Android, Treo); a wireless email device or other device capable of communicating over landlines or wirelessly with a computer network or other communication network; or any other type of network device that may communicate over a network and handle electronic transactions. The devices may be the same type of device and/or may include different types of devices. For example, the devices may be a computer 800a, a smartphone 800b, and/or a tablet 800c. Alternatively, the devices may all of the same kind or a heterogeneous system with different types of devices.
The devices as shown may belong to customers or individuals interacting with any kind of entity described herein including banks, online businesses merchants, etc. For example, the devices may belong to one or more senders or recipients. Devices may belong to one or more customers of an entity. An entity may be an organization, association, company, partnership, employer, or any other entity. In some embodiments, the entity may be a bank, financial institution, merchant, health care provider, or any other entity that may benefit from providing communications to customers.
The devices 800a, 800b, 800c may communicate with a web server 804. The communication between a network device and a web server may be, for example, a connection between a client computer and a website server over a network 802. It shall be understood that the web server 804 shown may conceptually represent one or more servers that may communicate with one or more computers or other network devices across a network. For example, a plurality of devices may communicate with a single server, or with a plurality of servers as part of a fraud containment system 804. Any description herein of a server may apply to a single server or a plurality of servers. Any description herein of a server may apply to a cloud computing type infrastructure. Cloud computing may include provisioning of dynamically scalable and/or virtualized resources. One or more resources (e.g., memory, processors) may be distributed over one or a plurality of machines.
The network 802, for example, can include a private network, such as a LAN, or interconnections to the online organizations over a communications network, such as the Internet or World Wide Web or any other network that is capable of communicating digital data, such as a wireless, cellular, data transfer, or telecommunications network. Each computer or other network device may connect to one or more web server over the network using data protocols, such as HTTP, HTTPS and the like. In one example, a workflow engine may reside on a computer separate from a web/application server that is on the same LAN as the web/application server.
A customer may interact with a mobile device (e.g., tablet, smartphone) or other network device that may be part of or connected to the fraud containment system. When a computer or other network device is communicating with the web server, the device may have a processor 806 and a memory 808 that may store an operating system (OS) and a browser application or other application to facilitate communications with the web server to carry out any aspect of the invention described herein. For example, the operating system may operate to display a graphical user interface to the user and permit the user to execute other computer programs, such as the browser application. The browser application, such as Microsoft Internet Explorer, Mozilla Firefox, Safari, when executed by the processor, permits the user to access the World Wide Web as is well known. Similarly, other applications or “apps” on mobile devices may be used.
In some embodiments, the server may be owned and/or run by a bank or designated entity. In some instances, the server may be owned and/or run by a third party that may communicate with the bank and/or any other entities described elsewhere herein.
The devices and/or server may include one or more processor and/or memory. The processor may be capable of executing one or more steps to detect and/or contain fraud with recipient devices in accordance with the invention herein.
It should be understood from the foregoing that, while particular implementations have been illustrated and described, various modifications can be made thereto and are contemplated herein. It is also not intended that the invention be limited by the specific examples provided within the specification. While the invention has been described with reference to the aforementioned specification, the descriptions and illustrations of the preferable embodiments herein are not meant to be construed in a limiting sense. Furthermore, it shall be understood that all aspects of the invention are not limited to the specific depictions, configurations or relative proportions set forth herein which depend upon a variety of conditions and variables. Various modifications in form and detail of the embodiments of the invention will be apparent to a person skilled in the art. It is therefore contemplated that the invention shall also cover any such modifications, variations and equivalents.
This patent application is a continuation of U.S. patent application Ser. No. 17/230,272, filed Apr. 14, 2021, entitled METHODS AND SYSTEMS FOR FRAUD CONTAINMENT, which is a continuation of U.S. patent application Ser. No. 16/435,092, filed Jun. 7, 2019, entitled METHODS AND SYSTEMS FOR FRAUD CONTAINMENT, which is a continuation of U.S. patent application Ser. No. 15/471,990, filed Mar. 28, 2017, entitled METHODS AND SYSTEMS FOR FRAUD CONTAINMENT, which is a continuation of U.S. patent application Ser. No. 13/782,745, filed Mar. 1, 2013, now U.S. Pat. No. 9,633,201, issued Apr. 25, 2017, entitled METHODS AND SYSTEMS FOR FRAUD CONTAINMENT, which claims benefit of priority to U.S. Provisional Application Ser. No. 61/605,677, filed on Mar. 1, 2012, entitled METHODS AND SYSTEMS FOR FRAUD CONTAINMENT, where all above-cited applications are hereby incorporated herein by reference in their entireties.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4801924 | Burgmann et al. | Jan 1989 | A |
| 4805222 | Young et al. | Feb 1989 | A |
| 4912761 | Tan et al. | Mar 1990 | A |
| 4924387 | Jeppesen | May 1990 | A |
| 5184849 | Taylor | Feb 1993 | A |
| 5491735 | Hsieh | Feb 1996 | A |
| 5519827 | Mizushima | May 1996 | A |
| 5521907 | Ennis, Jr. | May 1996 | A |
| 5557686 | Brown et al. | Sep 1996 | A |
| 5583380 | Larsen et al. | Dec 1996 | A |
| 5627886 | Bowman | May 1997 | A |
| 5679940 | Templeton et al. | Oct 1997 | A |
| 5721765 | Smith | Feb 1998 | A |
| 5724424 | Giffor | Mar 1998 | A |
| 5748740 | Curry et al. | May 1998 | A |
| 5748780 | Stolfo et al. | May 1998 | A |
| 5764275 | Lappington et al. | Jun 1998 | A |
| 5802156 | Felger | Sep 1998 | A |
| 5819226 | Gopinathan et al. | Oct 1998 | A |
| 5864620 | Pettitt | Jan 1999 | A |
| 5884289 | Anderson et al. | Mar 1999 | A |
| 5886334 | D'Entremont | Mar 1999 | A |
| 5892900 | Ginter et al. | Apr 1999 | A |
| 5894510 | Felger | Apr 1999 | A |
| 5899980 | Wilf et al. | May 1999 | A |
| 5903646 | Rackman | May 1999 | A |
| 5903721 | Sixtus | May 1999 | A |
| 5933480 | Felger | Aug 1999 | A |
| 5960069 | Felger | Sep 1999 | A |
| 6009523 | Owaki et al. | Dec 1999 | A |
| 6029154 | Pettitt | Feb 2000 | A |
| 6029159 | Zorba et al. | Feb 2000 | A |
| 6062474 | Kroll | May 2000 | A |
| 6078907 | Lamm | Jun 2000 | A |
| 6092053 | Boesch et al. | Jul 2000 | A |
| 6094643 | Anderson et al. | Jul 2000 | A |
| 6105012 | Chang et al. | Aug 2000 | A |
| 6112240 | Pogue et al. | Aug 2000 | A |
| 6148407 | Aucsmith | Nov 2000 | A |
| 6151593 | Cho et al. | Nov 2000 | A |
| 6163604 | Baulier et al. | Dec 2000 | A |
| 6163771 | Walker et al. | Dec 2000 | A |
| 6164528 | Hills et al. | Dec 2000 | A |
| 6205436 | Rosen et al. | Mar 2001 | B1 |
| 6209104 | Jalili | Mar 2001 | B1 |
| 6216153 | Vortriede | Apr 2001 | B1 |
| 6223289 | Wall et al. | Apr 2001 | B1 |
| 6282276 | Felger | Aug 2001 | B1 |
| 6295605 | Dockter et al. | Sep 2001 | B1 |
| 6327384 | Hirao et al. | Dec 2001 | B1 |
| 6330546 | Gopinathan et al. | Dec 2001 | B1 |
| 6370648 | Diep | Apr 2002 | B1 |
| 6405922 | Kroll | Jun 2002 | B1 |
| 6442529 | Krishan et al. | Aug 2002 | B1 |
| 6442692 | Zilberman | Aug 2002 | B1 |
| 6457021 | Berkowitz et al. | Sep 2002 | B1 |
| 6480710 | Laybourn et al. | Nov 2002 | B1 |
| 6509847 | Anderson | Jan 2003 | B1 |
| 6523019 | Borthwick | Feb 2003 | B1 |
| 6546493 | Magdych et al. | Apr 2003 | B1 |
| 6553108 | Felger | Apr 2003 | B1 |
| 6560455 | Amin et al. | May 2003 | B2 |
| 6567099 | Dawson | May 2003 | B1 |
| 6597775 | Lawyer et al. | Jul 2003 | B2 |
| 6646765 | Barker et al. | Nov 2003 | B1 |
| 6678666 | Boulware | Jan 2004 | B1 |
| 6687390 | Avni et al. | Feb 2004 | B2 |
| 6687696 | Hofmann et al. | Feb 2004 | B2 |
| 6689055 | Mullen et al. | Feb 2004 | B1 |
| 6718363 | Ponte | Apr 2004 | B1 |
| 6745333 | Thomsen | Jun 2004 | B1 |
| 6803920 | Gossett et al. | Oct 2004 | B2 |
| 6804624 | Silverman | Oct 2004 | B2 |
| 6850606 | Lawyer et al. | Feb 2005 | B2 |
| 6892307 | Wood et al. | May 2005 | B1 |
| 6895507 | Tepler | May 2005 | B1 |
| 6895514 | Kermani | May 2005 | B1 |
| 6898709 | Teppler | May 2005 | B1 |
| 6908030 | Rajasekaran et al. | Jun 2005 | B2 |
| 6937569 | Sarkar et al. | Aug 2005 | B1 |
| 6947978 | Huffman | Sep 2005 | B2 |
| 6954532 | Handley et al. | Oct 2005 | B1 |
| 6957185 | Labaton | Oct 2005 | B1 |
| 6957339 | Shinzaki | Oct 2005 | B2 |
| 7002712 | Barker et al. | Feb 2006 | B2 |
| 7003670 | Heaven et al. | Feb 2006 | B2 |
| 7007174 | Wheeler et al. | Feb 2006 | B2 |
| 7013001 | Felger | Mar 2006 | B1 |
| 7027800 | Haumont et al. | Apr 2006 | B2 |
| 7039505 | Southard et al. | May 2006 | B1 |
| 7039699 | Narin et al. | May 2006 | B1 |
| 7043640 | Pritchard et al. | May 2006 | B2 |
| 7089310 | Ellerman et al. | Aug 2006 | B1 |
| 7089585 | Dharmarajan | Aug 2006 | B1 |
| 7096192 | Pettitt | Aug 2006 | B1 |
| 7100049 | Gasparini et al. | Aug 2006 | B2 |
| 7103570 | Morea et al. | Sep 2006 | B1 |
| 7103668 | Corley et al. | Sep 2006 | B1 |
| 7120590 | Eisen et al. | Oct 2006 | B1 |
| 7130858 | Ciaramitaro et al. | Oct 2006 | B2 |
| 7143095 | Barrett et al. | Nov 2006 | B2 |
| 7158622 | Lawyer et al. | Jan 2007 | B2 |
| 7165051 | Ronning et al. | Jan 2007 | B2 |
| 7174454 | Roskind | Feb 2007 | B2 |
| 7191467 | Dujari et al. | Mar 2007 | B1 |
| 7197646 | Fritz et al. | Mar 2007 | B2 |
| 7206938 | Bender et al. | Apr 2007 | B2 |
| 7221949 | Clough | May 2007 | B2 |
| 7225974 | Yamauchi | Jun 2007 | B2 |
| 7237717 | Rao et al. | Jul 2007 | B1 |
| 7249093 | King | Jul 2007 | B1 |
| 7251624 | Lee et al. | Jul 2007 | B1 |
| 7260837 | Abraham et al. | Aug 2007 | B2 |
| 7263492 | Suresh et al. | Aug 2007 | B1 |
| 7263506 | Lee et al. | Aug 2007 | B2 |
| 7272610 | Torres | Sep 2007 | B2 |
| 7272728 | Pierson et al. | Sep 2007 | B2 |
| 7292723 | Tedesco et al. | Nov 2007 | B2 |
| 7293096 | Foltak et al. | Nov 2007 | B1 |
| 7296088 | Padmanabhan et al. | Nov 2007 | B1 |
| 7328216 | Hofmann et al. | Feb 2008 | B2 |
| 7330824 | Kanojia et al. | Feb 2008 | B1 |
| 7330871 | Barber | Feb 2008 | B2 |
| 7340045 | Felger | Mar 2008 | B2 |
| 7346551 | Pe Jimenez et al. | Mar 2008 | B2 |
| 7346775 | Gasparinl et al. | Mar 2008 | B2 |
| 7349955 | Korb et al. | Mar 2008 | B1 |
| 7352280 | Rockwood | Apr 2008 | B1 |
| 7359962 | Willebeek-Lemair | Apr 2008 | B2 |
| 7363170 | Seul et al. | Apr 2008 | B2 |
| 7373669 | Eisen | May 2008 | B2 |
| 7376618 | Anderson et al. | May 2008 | B1 |
| 7379891 | Donner et al. | May 2008 | B1 |
| 7386892 | Gilfix et al. | Jun 2008 | B2 |
| 7404087 | Teunen | Jun 2008 | B2 |
| 7401082 | Keene et al. | Jul 2008 | B2 |
| 7403922 | Lewis et al. | Jul 2008 | B1 |
| 7406441 | Kimura et al. | Jul 2008 | B2 |
| 7428587 | Rowland et al. | Sep 2008 | B2 |
| 7436780 | Stephens | Oct 2008 | B2 |
| 7438226 | Helsper et al. | Oct 2008 | B2 |
| 7447494 | Law et al. | Nov 2008 | B2 |
| 7451487 | Oliver et al. | Nov 2008 | B2 |
| 7457401 | Lawyer et al. | Nov 2008 | B2 |
| 7457823 | Shraim et al. | Nov 2008 | B2 |
| 7475242 | Baird et al. | Jan 2009 | B2 |
| 7478182 | Schweig | Jan 2009 | B2 |
| 7487350 | Utin | Feb 2009 | B2 |
| 7496752 | Yamaguchi et al. | Feb 2009 | B2 |
| 7497374 | Helsper et al. | Mar 2009 | B2 |
| 7502610 | Maher | Mar 2009 | B2 |
| 7502933 | Jakobsson et al. | Mar 2009 | B2 |
| 7526796 | Lulich et al. | Apr 2009 | B2 |
| 7543740 | Greene et al. | Jun 2009 | B2 |
| 7552090 | Barber | Jun 2009 | B1 |
| 7555458 | Felger | Jun 2009 | B1 |
| 7562221 | Nyström et al. | Jul 2009 | B2 |
| 7577620 | Donner | Aug 2009 | B1 |
| 7581112 | Brown et al. | Aug 2009 | B2 |
| 7606560 | Labrou et al. | Oct 2009 | B2 |
| 7630924 | Collins et al. | Dec 2009 | B1 |
| 7631808 | Kundu et al. | Dec 2009 | B2 |
| 7657626 | Zwicky | Feb 2010 | B1 |
| 7660902 | Graham et al. | Feb 2010 | B2 |
| 7665140 | Oliver et al. | Feb 2010 | B2 |
| 7665658 | Fields | Feb 2010 | B2 |
| 7673793 | Greene et al. | Mar 2010 | B2 |
| 7685629 | White et al. | Mar 2010 | B1 |
| 7698743 | Ohmori et al. | Apr 2010 | B2 |
| 7708200 | Helsper et al. | May 2010 | B2 |
| 7711846 | Padmanabhan et al. | May 2010 | B2 |
| 7735141 | Noel | Jun 2010 | B1 |
| 7739402 | Roese et al. | Jun 2010 | B2 |
| 7739512 | Hawkes | Jun 2010 | B2 |
| 7743409 | Gonzalez et al. | Jun 2010 | B2 |
| 7752084 | Pettitt | Jul 2010 | B2 |
| 7756783 | Crooks | Jul 2010 | B2 |
| 7761379 | Zoldi et al. | Jul 2010 | B2 |
| 7769032 | Ou | Aug 2010 | B1 |
| 7778846 | Suresh et al. | Aug 2010 | B2 |
| 7788195 | Subramanian et al. | Aug 2010 | B1 |
| 7813937 | Pathria et al. | Oct 2010 | B1 |
| 7813944 | Luk et al. | Oct 2010 | B1 |
| 7814029 | Siegel | Oct 2010 | B1 |
| 7849029 | Crooks et al. | Dec 2010 | B2 |
| 7849307 | Roskind | Dec 2010 | B2 |
| 7853526 | Milana | Dec 2010 | B2 |
| 7853533 | Eisen | Dec 2010 | B2 |
| 7856372 | Ullah | Dec 2010 | B2 |
| 7860783 | Yang et al. | Dec 2010 | B2 |
| 7861260 | Shkedi | Dec 2010 | B2 |
| 7865427 | Wright et al. | Jan 2011 | B2 |
| 7882217 | Katzir | Feb 2011 | B2 |
| 7908223 | Klein et al. | Mar 2011 | B2 |
| 7908645 | Varghese et al. | Mar 2011 | B2 |
| 7930285 | Abraham et al. | Apr 2011 | B2 |
| 7933984 | Smith et al. | Apr 2011 | B1 |
| 7937467 | Barber | May 2011 | B2 |
| 7940929 | Sengupta | May 2011 | B1 |
| 7945494 | Williams | May 2011 | B2 |
| 7945515 | Zoldi et al. | May 2011 | B2 |
| 7949564 | Hughes et al. | May 2011 | B1 |
| 7958029 | Bobich et al. | Jun 2011 | B1 |
| 7958246 | Barber | Jun 2011 | B2 |
| 7961857 | Zoldi et al. | Jun 2011 | B2 |
| 7970701 | Lewis et al. | Jun 2011 | B2 |
| 7983490 | Minter | Jul 2011 | B1 |
| 7983691 | Wong et al. | Jul 2011 | B1 |
| 7991716 | Crooks et al. | Aug 2011 | B2 |
| 7995996 | Link, II et al. | Aug 2011 | B2 |
| 8001376 | Utin | Aug 2011 | B2 |
| 8001597 | Crooks | Aug 2011 | B2 |
| 8015614 | Matsuzaki et al. | Sep 2011 | B2 |
| 8015921 | Leppanen et al. | Sep 2011 | B2 |
| 8019678 | Wright et al. | Sep 2011 | B2 |
| 8020763 | Kowalchyk et al. | Sep 2011 | B1 |
| 8024266 | Barber | Sep 2011 | B1 |
| 8025220 | Zoldi et al. | Sep 2011 | B2 |
| 8027439 | Zoldi et al. | Sep 2011 | B2 |
| 8032448 | Anderson et al. | Oct 2011 | B2 |
| 8037097 | Guo et al. | Oct 2011 | B2 |
| 8037511 | Lundy et al. | Oct 2011 | B1 |
| 8041597 | Li et al. | Oct 2011 | B2 |
| 8042164 | Sheynblat et al. | Oct 2011 | B2 |
| 8046271 | Jimenez et al. | Oct 2011 | B2 |
| 8060922 | Crichton et al. | Nov 2011 | B2 |
| 8065233 | Lee et al. | Nov 2011 | B2 |
| 8090648 | Zoldi et al. | Jan 2012 | B2 |
| 8108378 | Ott, IV et al. | Jan 2012 | B2 |
| 8121962 | Vaiciulis et al. | Feb 2012 | B2 |
| 8122082 | Klein | Feb 2012 | B2 |
| 8126816 | Mu et al. | Feb 2012 | B2 |
| 8131615 | Diev et al. | Mar 2012 | B2 |
| 8140689 | Barber | Mar 2012 | B2 |
| 8141148 | Thomas et al. | Mar 2012 | B2 |
| 8145560 | Kulkarni et al. | Mar 2012 | B2 |
| 8145762 | Barber | Mar 2012 | B2 |
| 8150968 | Barber | Apr 2012 | B2 |
| 8151327 | Eisen | Apr 2012 | B2 |
| 8166068 | Stevens | Apr 2012 | B2 |
| 8175897 | Lee et al. | May 2012 | B2 |
| 8176178 | Thomas et al. | May 2012 | B2 |
| 8180686 | Ryu et al. | May 2012 | B2 |
| 8181015 | Roskind | May 2012 | B2 |
| 8185953 | Rothstein et al. | May 2012 | B2 |
| 8190513 | Felger | May 2012 | B2 |
| 8190529 | Abe et al. | May 2012 | B2 |
| 8191148 | Oliver et al. | May 2012 | B2 |
| 8200527 | Thompson | Jun 2012 | B1 |
| 8201099 | Osbourn et al. | Jun 2012 | B1 |
| 8204833 | Mu et al. | Jun 2012 | B2 |
| 8209744 | Zhu et al. | Jun 2012 | B2 |
| 8209760 | Hardman | Jun 2012 | B1 |
| 8213898 | Choti et al. | Jul 2012 | B2 |
| 8214232 | Tyler et al. | Jul 2012 | B2 |
| 8214285 | Hu et al. | Jul 2012 | B2 |
| 8219415 | Tyler et al. | Jul 2012 | B2 |
| 8224308 | Gavrylyako et al. | Jul 2012 | B1 |
| 8224348 | Bolon et al. | Jul 2012 | B2 |
| 8229844 | Felger | Jul 2012 | B2 |
| 8250631 | Iyengar et al. | Aug 2012 | B2 |
| 8266295 | Klein et al. | Sep 2012 | B2 |
| 8271891 | Osbourn et al. | Sep 2012 | B1 |
| 8272061 | Lotem | Sep 2012 | B1 |
| 8280833 | Miltonberger | Oct 2012 | B2 |
| 8290838 | Thakur et al. | Oct 2012 | B1 |
| 8295898 | Ashfield et al. | Oct 2012 | B2 |
| 8296228 | Kloor | Oct 2012 | B1 |
| 8296229 | Yellin et al. | Oct 2012 | B1 |
| 8296245 | Barber et al. | Oct 2012 | B2 |
| 8296250 | Crooks et al. | Oct 2012 | B2 |
| 8306933 | Kawai et al. | Nov 2012 | B2 |
| 8307430 | Chen | Nov 2012 | B1 |
| 8311907 | Klein et al. | Nov 2012 | B2 |
| 8321269 | Linden et al. | Nov 2012 | B2 |
| 8326759 | Hammad | Dec 2012 | B2 |
| 8326760 | Ma et al. | Dec 2012 | B2 |
| 8326763 | Zuili | Dec 2012 | B2 |
| 8332338 | Vaiciulis et al. | Dec 2012 | B2 |
| 8332522 | Barber | Dec 2012 | B2 |
| 8370253 | Grossman et al. | Feb 2013 | B1 |
| 8370638 | Duane et al. | Feb 2013 | B2 |
| 8380831 | Barber | Feb 2013 | B2 |
| 8392987 | Sasamura et al. | Mar 2013 | B2 |
| 8407112 | Walter | Mar 2013 | B2 |
| 8407798 | Lotem | Mar 2013 | B1 |
| 8417587 | Jimenez et al. | Apr 2013 | B2 |
| 8423458 | Barber | Apr 2013 | B2 |
| 8424061 | Rosenor | Apr 2013 | B2 |
| 8429070 | Hu et al. | Apr 2013 | B2 |
| 8438134 | Wang et al. | May 2013 | B2 |
| 8438184 | Wang | May 2013 | B1 |
| 8443202 | White et al. | May 2013 | B2 |
| 8452715 | Barber | May 2013 | B2 |
| 8453226 | Hammad | May 2013 | B2 |
| 8462161 | Barber | Jun 2013 | B1 |
| 8464290 | Beyda et al. | Jun 2013 | B2 |
| 8468582 | Kuang et al. | Jun 2013 | B2 |
| 8484470 | Sakakihara et al. | Jul 2013 | B2 |
| 8495714 | Jones et al. | Jul 2013 | B2 |
| 8516439 | Brass et al. | Aug 2013 | B2 |
| 8539070 | Barber | Sep 2013 | B2 |
| 8543522 | Ryman-Tubb et al. | Sep 2013 | B2 |
| 8548137 | Zoldi et al. | Oct 2013 | B2 |
| 8559607 | Zoldi et al. | Oct 2013 | B2 |
| 8567669 | Griegel et al. | Oct 2013 | B2 |
| 8588816 | Collins | Nov 2013 | B2 |
| 8601109 | Johannsen | Dec 2013 | B2 |
| 8611856 | Yan et al. | Dec 2013 | B2 |
| 8612854 | Eisen et al. | Dec 2013 | B2 |
| 8620942 | Hoffman et al. | Dec 2013 | B1 |
| 8631006 | Haveliwala et al. | Jan 2014 | B1 |
| 8660539 | Khambete et al. | Feb 2014 | B2 |
| 8661119 | Jindal et al. | Feb 2014 | B1 |
| 8676684 | Newman | Mar 2014 | B2 |
| 8677398 | Shkedi | Mar 2014 | B2 |
| 8683561 | Utin | Mar 2014 | B2 |
| 8688543 | Dominquez | Apr 2014 | B2 |
| 8701168 | Sastry et al. | Apr 2014 | B2 |
| 8701170 | Barber | Apr 2014 | B1 |
| 8725570 | Doughty et al. | May 2014 | B2 |
| 8751815 | Lunde et al. | Jun 2014 | B2 |
| 8762283 | Gerber et al. | Jun 2014 | B2 |
| 8762574 | Barber | Jun 2014 | B2 |
| 8763113 | Thomas et al. | Jun 2014 | B2 |
| 8776225 | Pierson et al. | Jul 2014 | B2 |
| 8779981 | Eisen et al. | Jul 2014 | B2 |
| 8781975 | Bennett et al. | Jul 2014 | B2 |
| 8782783 | Thomas et al. | Jul 2014 | B2 |
| 8799458 | Barber | Aug 2014 | B2 |
| 8817984 | Miller et al. | Aug 2014 | B2 |
| 8826393 | Eisen | Sep 2014 | B2 |
| 8838478 | Kretz et al. | Sep 2014 | B2 |
| 8838967 | Mills et al. | Sep 2014 | B1 |
| 8862514 | Eisen | Oct 2014 | B2 |
| 8862526 | Miltonberger | Oct 2014 | B2 |
| 8874735 | Barber | Oct 2014 | B2 |
| 8880097 | Xu et al. | Nov 2014 | B1 |
| 8881288 | Levy | Nov 2014 | B1 |
| 8938671 | Eisen et al. | Jan 2015 | B2 |
| 8954560 | Johannsen | Feb 2015 | B2 |
| 8966276 | Nanopoulos et al. | Feb 2015 | B2 |
| 9037483 | Curcio et al. | May 2015 | B1 |
| 9038153 | Barber | May 2015 | B2 |
| 9060012 | Eisen | Jun 2015 | B2 |
| 9075896 | Barber | Jul 2015 | B2 |
| 9083735 | Reumann et al. | Jul 2015 | B2 |
| 9098617 | Pauley, Jr. et al. | Aug 2015 | B1 |
| 9112850 | Eisen | Aug 2015 | B1 |
| 9118646 | Pierson et al. | Aug 2015 | B2 |
| 9172691 | Barber | Oct 2015 | B2 |
| 9177293 | Gagnon | Nov 2015 | B1 |
| 9183567 | Barber | Nov 2015 | B2 |
| 9191370 | Barber et al. | Nov 2015 | B2 |
| 9196004 | Eisen | Nov 2015 | B2 |
| 9202039 | Dandu et al. | Dec 2015 | B2 |
| 9203837 | Pierson et al. | Dec 2015 | B2 |
| 9294448 | Miller et al. | Mar 2016 | B2 |
| 9298677 | Tollinger et al. | Mar 2016 | B2 |
| 9332020 | Thomas et al. | May 2016 | B2 |
| 9361597 | Britton et al. | Jun 2016 | B2 |
| 9378500 | Jimenez et al. | Jun 2016 | B2 |
| 9390384 | Eisen | Jul 2016 | B2 |
| 9396331 | Eisen et al. | Jul 2016 | B2 |
| 9412123 | Eisen | Aug 2016 | B2 |
| 9477968 | Barber | Oct 2016 | B2 |
| 9514248 | Guan et al. | Dec 2016 | B1 |
| 9514446 | Rajkumar et al. | Dec 2016 | B1 |
| 9521161 | Reumann et al. | Dec 2016 | B2 |
| 9521551 | Eisen et al. | Dec 2016 | B2 |
| 9559852 | Miller et al. | Jan 2017 | B2 |
| 9603016 | Mills et al. | Mar 2017 | B1 |
| 9633201 | Katz | Apr 2017 | B1 |
| 9699164 | Barber | Jul 2017 | B2 |
| 9702961 | Shields | Jul 2017 | B2 |
| 9703983 | Eisen et al. | Jul 2017 | B2 |
| 9712497 | Barber et al. | Jul 2017 | B2 |
| 9722968 | Barber | Aug 2017 | B2 |
| 9754256 | Britton et al. | Sep 2017 | B2 |
| 9754311 | Eisen | Sep 2017 | B2 |
| 9781151 | McCorkendale | Oct 2017 | B1 |
| 9785973 | Tollinger et al. | Oct 2017 | B2 |
| 9916393 | Barber | Mar 2018 | B2 |
| 9948629 | Eisen | Apr 2018 | B2 |
| 9990631 | Eisen | Jun 2018 | B2 |
| 10007895 | Vanasco | Jun 2018 | B2 |
| 10021099 | Eisen et al. | Jul 2018 | B2 |
| 10037529 | Barber | Jul 2018 | B2 |
| 10089679 | Eisen | Oct 2018 | B2 |
| 10091312 | Khanwalkar et al. | Oct 2018 | B1 |
| 10123368 | Gundavelli et al. | Nov 2018 | B2 |
| 10231120 | Nethi et al. | Mar 2019 | B2 |
| 10248968 | Sivaramakrishnan et al. | Apr 2019 | B2 |
| 10290017 | Traasdahl et al. | May 2019 | B2 |
| 10305880 | Barber | May 2019 | B2 |
| 10321309 | Lee et al. | Jun 2019 | B2 |
| 10339306 | Katz | Jul 2019 | B1 |
| 10341344 | Eisen et al. | Jul 2019 | B2 |
| 10395252 | Eisen | Aug 2019 | B2 |
| 10402854 | Barber | Sep 2019 | B2 |
| 10417637 | Eisen | Sep 2019 | B2 |
| 10425379 | Barber | Sep 2019 | B2 |
| 10453066 | Eisen | Oct 2019 | B2 |
| 10510094 | Sivaramakrishnan et al. | Dec 2019 | B2 |
| 10535093 | Eisen | Jan 2020 | B2 |
| 10616201 | Eisen | Apr 2020 | B2 |
| 10642899 | Barber | May 2020 | B2 |
| 10679216 | Barber | Jun 2020 | B2 |
| 10691751 | Atlas et al. | Jun 2020 | B2 |
| 10726151 | Eisen et al. | Jul 2020 | B2 |
| 10728350 | Khanwalkar | Jul 2020 | B1 |
| 10754913 | Liodden et al. | Aug 2020 | B2 |
| 10853813 | Eisen | Dec 2020 | B2 |
| 10862889 | Eisen et al. | Dec 2020 | B2 |
| 10902327 | Yalov et al. | Jan 2021 | B1 |
| 10956732 | Henaff | Mar 2021 | B2 |
| 10984128 | Hoffer | Apr 2021 | B1 |
| 10999298 | Eisen | May 2021 | B2 |
| 11010468 | Katz | May 2021 | B1 |
| 11095643 | Huffman et al. | Aug 2021 | B2 |
| 11176200 | Barber | Nov 2021 | B2 |
| 11176573 | Barber | Nov 2021 | B2 |
| 11177967 | Pala | Nov 2021 | B2 |
| 11195225 | Eisen | Dec 2021 | B2 |
| 11223621 | Cano et al. | Jan 2022 | B2 |
| 11238456 | Eisen | Feb 2022 | B2 |
| 11240326 | Khanwalkar et al. | Feb 2022 | B1 |
| 11301585 | Eisen et al. | Apr 2022 | B2 |
| 11301860 | Eisen | Apr 2022 | B2 |
| 11314838 | Liodden et al. | Apr 2022 | B2 |
| 11410179 | Eisen | Aug 2022 | B2 |
| 11657299 | Yalov et al. | May 2023 | B1 |
| 11675868 | Putnam | Jun 2023 | B2 |
| 11683306 | Eisen et al. | Jun 2023 | B2 |
| 11683326 | Eisen | Jun 2023 | B2 |
| 11727471 | Eisen | Aug 2023 | B2 |
| 11750584 | Eisen | Sep 2023 | B2 |
| 11886575 | Katz | Jan 2024 | B1 |
| 11895204 | Khanwalkar et al. | Feb 2024 | B1 |
| 11922423 | Eisen | Mar 2024 | B2 |
| 20010011243 | Dembo et al. | Aug 2001 | A1 |
| 20010011304 | Wesigner et al. | Aug 2001 | A1 |
| 20010016840 | Hijikata et al. | Aug 2001 | A1 |
| 20010016876 | Kurth et al. | Aug 2001 | A1 |
| 20010018739 | Anderson et al. | Aug 2001 | A1 |
| 20010034712 | Colvin | Oct 2001 | A1 |
| 20010046096 | Worden | Nov 2001 | A1 |
| 20020035622 | Barber | Mar 2002 | A1 |
| 20020041328 | LeCompte et al. | Apr 2002 | A1 |
| 20020046157 | Solomon | Apr 2002 | A1 |
| 20020052852 | Bozeman | May 2002 | A1 |
| 20020056042 | van der Kaay et al. | May 2002 | A1 |
| 20020073046 | David | Jun 2002 | A1 |
| 20020073099 | Gilbert et al. | Jun 2002 | A1 |
| 20020073327 | Vellandi | Jun 2002 | A1 |
| 20020083079 | Meier et al. | Jun 2002 | A1 |
| 20020112171 | Ginter et al. | Aug 2002 | A1 |
| 20020128917 | Grounds | Sep 2002 | A1 |
| 20020133721 | Adjaoute | Sep 2002 | A1 |
| 20020138335 | Palmer et al. | Sep 2002 | A1 |
| 20020138577 | Teng et al. | Sep 2002 | A1 |
| 20020153424 | Li | Oct 2002 | A1 |
| 20020156724 | Levchin et al. | Oct 2002 | A1 |
| 20020156836 | Janosik, Jr. et al. | Oct 2002 | A1 |
| 20020166063 | Lachman et al. | Nov 2002 | A1 |
| 20020167965 | Beasley et al. | Nov 2002 | A1 |
| 20020194119 | Wright et al. | Dec 2002 | A1 |
| 20030002732 | Gossett et al. | Jan 2003 | A1 |
| 20030002740 | Melikian et al. | Jan 2003 | A1 |
| 20030014327 | Skantze | Jan 2003 | A1 |
| 20030033161 | Walker et al. | Feb 2003 | A1 |
| 20030033356 | Tran et al. | Feb 2003 | A1 |
| 20030058277 | Bowman-Amuah | Mar 2003 | A1 |
| 20030070080 | Rosen | Apr 2003 | A1 |
| 20030074301 | Solomon | Apr 2003 | A1 |
| 20030076242 | Burns et al. | Apr 2003 | A1 |
| 20030105707 | Audebert et al. | Jun 2003 | A1 |
| 20030105854 | Thorsteinsson et al. | Jun 2003 | A1 |
| 20030113033 | Huang | Jun 2003 | A1 |
| 20030115334 | Bhat et al. | Jun 2003 | A1 |
| 20030115481 | Baird et al. | Jun 2003 | A1 |
| 20030120543 | Carey | Jun 2003 | A1 |
| 20030120586 | Litty | Jun 2003 | A1 |
| 20030140258 | Nelson et al. | Jul 2003 | A1 |
| 20030140283 | Nishio | Jul 2003 | A1 |
| 20030154214 | Tu et al. | Aug 2003 | A1 |
| 20030158751 | Suresh et al. | Aug 2003 | A1 |
| 20030163359 | Kanesaka | Aug 2003 | A1 |
| 20030163398 | Yoshioka et al. | Aug 2003 | A1 |
| 20030163413 | Wiczkowski | Aug 2003 | A1 |
| 20030172036 | Feigenbaum | Sep 2003 | A1 |
| 20030182551 | Frantz et al. | Sep 2003 | A1 |
| 20030208684 | Camacho et al. | Nov 2003 | A1 |
| 20030212618 | Keyes et al. | Nov 2003 | A1 |
| 20030233553 | Parks et al. | Dec 2003 | A1 |
| 20030237000 | Denton et al. | Dec 2003 | A1 |
| 20040001044 | Luciani et al. | Jan 2004 | A1 |
| 20040004733 | Barker et al. | Jan 2004 | A1 |
| 20040006553 | de Vries et al. | Jan 2004 | A1 |
| 20040010682 | Foster et al. | Jan 2004 | A1 |
| 20040027385 | Rekimoto et al. | Feb 2004 | A1 |
| 20040030912 | Merkle, Jr. et al. | Feb 2004 | A1 |
| 20040034794 | Mayer et al. | Feb 2004 | A1 |
| 20040066023 | Joseph | Apr 2004 | A1 |
| 20040073809 | Wing Keong | Apr 2004 | A1 |
| 20040088313 | Torres | May 2004 | A1 |
| 20040098618 | Kim | May 2004 | A1 |
| 20040105431 | Monjas-Llorente et al. | Jun 2004 | A1 |
| 20040111621 | Himberger et al. | Jun 2004 | A1 |
| 20040111632 | Halperin | Jun 2004 | A1 |
| 20040117321 | Sancho | Jun 2004 | A1 |
| 20040139008 | Mascavaage, III | Jul 2004 | A1 |
| 20040153644 | McCorkendale et al. | Aug 2004 | A1 |
| 20040159699 | Nelson et al. | Aug 2004 | A1 |
| 20040166857 | Shim et al. | Aug 2004 | A1 |
| 20040171381 | Inselberg | Sep 2004 | A1 |
| 20040181598 | Paya et al. | Sep 2004 | A1 |
| 20040187023 | Alagna et al. | Sep 2004 | A1 |
| 20040203750 | Cowdrey et al. | Oct 2004 | A1 |
| 20040230820 | Hui Hsu et al. | Nov 2004 | A1 |
| 20040236696 | Aoki et al. | Nov 2004 | A1 |
| 20040236702 | Fink et al. | Nov 2004 | A1 |
| 20040254890 | Sancho et al. | Dec 2004 | A1 |
| 20040260876 | Singh et al. | Dec 2004 | A1 |
| 20040260922 | Goodman et al. | Dec 2004 | A1 |
| 20050008148 | Jacobson | Jan 2005 | A1 |
| 20050015601 | Tabi | Jan 2005 | A1 |
| 20050021360 | Miller et al. | Jan 2005 | A1 |
| 20050022020 | Fremberg et al. | Jan 2005 | A1 |
| 20050033653 | Eisenberg et al. | Feb 2005 | A1 |
| 20050033703 | Holdsworth | Feb 2005 | A1 |
| 20050039034 | Doyle et al. | Feb 2005 | A1 |
| 20050039219 | Cooper et al. | Feb 2005 | A1 |
| 20050074015 | Chari et al. | Apr 2005 | A1 |
| 20050076230 | Redenbaugh et al. | Apr 2005 | A1 |
| 20050085931 | Willeby | Apr 2005 | A1 |
| 20050097320 | Golan et al. | May 2005 | A1 |
| 20050108177 | Sancho | May 2005 | A1 |
| 20050111054 | Umeda | May 2005 | A1 |
| 20050113092 | Coppinger et al. | May 2005 | A1 |
| 20050131826 | Cook | Jun 2005 | A1 |
| 20050138110 | Redlich et al. | Jun 2005 | A1 |
| 20050165643 | Wilson et al. | Jul 2005 | A1 |
| 20050185225 | Brawn et al. | Aug 2005 | A1 |
| 20050187883 | Bishop et al. | Aug 2005 | A1 |
| 20050188423 | Motsinger et al. | Aug 2005 | A1 |
| 20050204159 | Davis et al. | Sep 2005 | A1 |
| 20050210533 | Copeland | Sep 2005 | A1 |
| 20050216278 | Eisen | Sep 2005 | A1 |
| 20050246551 | Dondl et al. | Nov 2005 | A1 |
| 20050278542 | Pierson et al. | Dec 2005 | A1 |
| 20060008779 | Shand et al. | Jan 2006 | A1 |
| 20060010072 | Eisen | Jan 2006 | A1 |
| 20060026669 | Zakas | Feb 2006 | A1 |
| 20060031938 | Choi | Feb 2006 | A1 |
| 20060048211 | Pierson et al. | Mar 2006 | A1 |
| 20060059253 | Goodman | Mar 2006 | A1 |
| 20060059568 | Smith-Mickelson | Mar 2006 | A1 |
| 20060064346 | Steenstra et al. | Mar 2006 | A1 |
| 20060069619 | Walker et al. | Mar 2006 | A1 |
| 20060075492 | Golan | Apr 2006 | A1 |
| 20060080263 | Willis et al. | Apr 2006 | A1 |
| 20060126829 | Lai | Jun 2006 | A1 |
| 20060130132 | Dharmarajan | Jun 2006 | A1 |
| 20060136294 | Linden et al. | Jun 2006 | A1 |
| 20060155985 | Canard et al. | Jul 2006 | A1 |
| 20060161501 | Waserstein et al. | Jul 2006 | A1 |
| 20060176984 | Lee et al. | Aug 2006 | A1 |
| 20060190331 | Tollinger et al. | Aug 2006 | A1 |
| 20060190489 | Vohariwatt et al. | Aug 2006 | A1 |
| 20060200855 | Willis | Sep 2006 | A1 |
| 20060200856 | Salowey et al. | Sep 2006 | A1 |
| 20060224898 | Ahmed | Oct 2006 | A1 |
| 20060237531 | Heffez et al. | Oct 2006 | A1 |
| 20060253327 | Morris et al. | Nov 2006 | A1 |
| 20060253328 | Kohli et al. | Nov 2006 | A1 |
| 20060264202 | Hagmeier et al. | Nov 2006 | A1 |
| 20060281541 | Nguyen et al. | Dec 2006 | A1 |
| 20060282660 | Varghese et al. | Dec 2006 | A1 |
| 20060284838 | Tsatalos et al. | Dec 2006 | A1 |
| 20060287902 | Helsper et al. | Dec 2006 | A1 |
| 20070011078 | Jain et al. | Jan 2007 | A1 |
| 20070026942 | Kinsley et al. | Feb 2007 | A1 |
| 20070030528 | Quaeler et al. | Feb 2007 | A1 |
| 20070038568 | Greene et al. | Feb 2007 | A1 |
| 20070043837 | Kruse et al. | Feb 2007 | A1 |
| 20070061211 | Ramer et al. | Mar 2007 | A1 |
| 20070061273 | Greene et al. | Mar 2007 | A1 |
| 20070073630 | Greene et al. | Mar 2007 | A1 |
| 20070094594 | Matichuk et al. | Apr 2007 | A1 |
| 20070097076 | Gross | May 2007 | A1 |
| 20070097976 | Wood et al. | May 2007 | A1 |
| 20070101405 | Engle et al. | May 2007 | A1 |
| 20070107059 | Chasin et al. | May 2007 | A1 |
| 20070118892 | Sastry et al. | May 2007 | A1 |
| 20070124246 | Lawyer et al. | May 2007 | A1 |
| 20070162763 | Bender et al. | Jul 2007 | A1 |
| 20070192240 | Crooks | Aug 2007 | A1 |
| 20070198410 | Labgold et al. | Aug 2007 | A1 |
| 20070199054 | Florencio et al. | Aug 2007 | A1 |
| 20070204044 | Rice et al. | Aug 2007 | A1 |
| 20070208619 | Branam et al. | Sep 2007 | A1 |
| 20070214151 | Scott et al. | Sep 2007 | A1 |
| 20070220594 | Tulsyan | Sep 2007 | A1 |
| 20070233599 | Ganesan et al. | Oct 2007 | A1 |
| 20070233759 | Tomlinson et al. | Oct 2007 | A1 |
| 20070234070 | Horning et al. | Oct 2007 | A1 |
| 20070234409 | Eisen | Oct 2007 | A1 |
| 20070239604 | O'Connell et al. | Oct 2007 | A1 |
| 20070239606 | Eisen | Oct 2007 | A1 |
| 20070255821 | Ge et al. | Nov 2007 | A1 |
| 20070266257 | Camaisa et al. | Nov 2007 | A1 |
| 20070271466 | Mak | Nov 2007 | A1 |
| 20070294401 | Shkedi | Dec 2007 | A1 |
| 20070297459 | Cucos et al. | Dec 2007 | A1 |
| 20080002725 | Alicherry | Jan 2008 | A1 |
| 20080005394 | Crooks | Jan 2008 | A1 |
| 20080010367 | Chen et al. | Jan 2008 | A1 |
| 20080010678 | Burdette et al. | Jan 2008 | A1 |
| 20080015988 | Brown et al. | Jan 2008 | A1 |
| 20080021801 | Song et al. | Jan 2008 | A1 |
| 20080040653 | Levine | Feb 2008 | A1 |
| 20080040802 | Pierson et al. | Feb 2008 | A1 |
| 20080043634 | Wang et al. | Feb 2008 | A1 |
| 20080045201 | Kies | Feb 2008 | A1 |
| 20080046562 | Butler | Feb 2008 | A1 |
| 20080049779 | Hopmann et al. | Feb 2008 | A1 |
| 20080052629 | Phillips et al. | Feb 2008 | A1 |
| 20080098222 | Zilberman | Apr 2008 | A1 |
| 20080101277 | Taylor | May 2008 | A1 |
| 20080104070 | Lonchar | May 2008 | A1 |
| 20080104672 | Lunde et al. | May 2008 | A1 |
| 20080104684 | Lunde et al. | May 2008 | A1 |
| 20080109307 | Ullah | May 2008 | A1 |
| 20080120195 | Shakkarwar | May 2008 | A1 |
| 20080120214 | Steele et al. | May 2008 | A1 |
| 20080121690 | Carani et al. | May 2008 | A1 |
| 20080126180 | Ullah | May 2008 | A1 |
| 20080133420 | Barber | Jun 2008 | A1 |
| 20080162200 | O'Sullivan et al. | Jul 2008 | A1 |
| 20080162202 | Khanna et al. | Jul 2008 | A1 |
| 20080162475 | Meggs | Jul 2008 | A1 |
| 20080163128 | Callanan et al. | Jul 2008 | A1 |
| 20080184355 | Walrath et al. | Jul 2008 | A1 |
| 20080184372 | Hoshina | Jul 2008 | A1 |
| 20080189790 | Park | Aug 2008 | A1 |
| 20080191007 | Keay | Aug 2008 | A1 |
| 20080201214 | Aaron | Aug 2008 | A1 |
| 20080204788 | Kelly et al. | Aug 2008 | A1 |
| 20080222706 | Renaud et al. | Sep 2008 | A1 |
| 20080235623 | Li | Sep 2008 | A1 |
| 20080239365 | Salgado et al. | Oct 2008 | A1 |
| 20080249820 | Pathria et al. | Oct 2008 | A1 |
| 20080255944 | Shah et al. | Oct 2008 | A1 |
| 20080281606 | Kitts | Nov 2008 | A1 |
| 20080281941 | Park et al. | Nov 2008 | A1 |
| 20080288299 | Schultz | Nov 2008 | A1 |
| 20080301281 | Wang et al. | Dec 2008 | A1 |
| 20080306830 | Lasa et al. | Dec 2008 | A1 |
| 20080313079 | Van Bosch et al. | Dec 2008 | A1 |
| 20080319774 | O'Sullivan et al. | Dec 2008 | A1 |
| 20080319841 | Oliver et al. | Dec 2008 | A1 |
| 20090017805 | Sarukkai et al. | Jan 2009 | A1 |
| 20090018940 | Wang et al. | Jan 2009 | A1 |
| 20090024971 | Willner et al. | Jan 2009 | A1 |
| 20090037213 | Eisen | Feb 2009 | A1 |
| 20090037602 | Patel et al. | Feb 2009 | A1 |
| 20090044279 | Crawford et al. | Feb 2009 | A1 |
| 20090044282 | Govindaraju | Feb 2009 | A1 |
| 20090055398 | Zhu et al. | Feb 2009 | A1 |
| 20090055929 | Lee et al. | Feb 2009 | A1 |
| 20090070664 | Gavin et al. | Mar 2009 | A1 |
| 20090083184 | Eisen | Mar 2009 | A1 |
| 20090089869 | Varghese | Apr 2009 | A1 |
| 20090106413 | Salo | Apr 2009 | A1 |
| 20090138590 | Lee | May 2009 | A1 |
| 20090138593 | Kalavade | May 2009 | A1 |
| 20090157417 | Bradley et al. | Jun 2009 | A1 |
| 20090164269 | Gupta et al. | Jun 2009 | A1 |
| 20090171760 | Aarnio et al. | Jul 2009 | A1 |
| 20090177692 | Chagoly et al. | Jul 2009 | A1 |
| 20090183010 | Schnell et al. | Jul 2009 | A1 |
| 20090187625 | Blackstock et al. | Jul 2009 | A1 |
| 20090198629 | De Prisco et al. | Aug 2009 | A1 |
| 20090203390 | Bradbury et al. | Aug 2009 | A1 |
| 20090205031 | Sato et al. | Aug 2009 | A1 |
| 20090210305 | Lyons | Aug 2009 | A1 |
| 20090222308 | Zoldi et al. | Sep 2009 | A1 |
| 20090228340 | Bohannon | Sep 2009 | A1 |
| 20090228585 | Kosbab et al. | Sep 2009 | A1 |
| 20090234738 | Britton et al. | Sep 2009 | A1 |
| 20090241174 | Rajan et al. | Sep 2009 | A1 |
| 20090254430 | Cherenson | Oct 2009 | A1 |
| 20090260064 | Mcdowell et al. | Oct 2009 | A1 |
| 20090265773 | Schultz | Oct 2009 | A1 |
| 20090271306 | Pierson | Oct 2009 | A1 |
| 20090307141 | Kongalath et al. | Oct 2009 | A1 |
| 20090280777 | Doherty | Nov 2009 | A1 |
| 20090292568 | Khosravani et al. | Nov 2009 | A1 |
| 20090293128 | Lippmann | Nov 2009 | A1 |
| 20090296907 | Vendrow et al. | Dec 2009 | A1 |
| 20090298480 | Khambete et al. | Dec 2009 | A1 |
| 20090307119 | Ahles | Dec 2009 | A1 |
| 20090313134 | Faith et al. | Dec 2009 | A1 |
| 20090327333 | Diener et al. | Dec 2009 | A1 |
| 20100004965 | Eisen | Jan 2010 | A1 |
| 20100005013 | Uriarte | Jan 2010 | A1 |
| 20100023382 | Fushimi et al. | Jan 2010 | A1 |
| 20100030641 | Ibenforth | Feb 2010 | A1 |
| 20100030777 | Panwar et al. | Feb 2010 | A1 |
| 20100057623 | Kapur et al. | Mar 2010 | A1 |
| 20100057843 | Landsman et al. | Mar 2010 | A1 |
| 20100070606 | Shenfield et al. | Mar 2010 | A1 |
| 20100082136 | Rosenblatt et al. | Apr 2010 | A1 |
| 20100082972 | Benco et al. | Apr 2010 | A1 |
| 20100094767 | Miltonberger | Apr 2010 | A1 |
| 20100094768 | Miltonberger | Apr 2010 | A1 |
| 20100106611 | Paulsen et al. | Apr 2010 | A1 |
| 20100107225 | Spencer et al. | Apr 2010 | A1 |
| 20100115115 | Terrill | May 2010 | A1 |
| 20100121716 | Golan | May 2010 | A1 |
| 20100138299 | Preston et al. | Jun 2010 | A1 |
| 20100145960 | Casteel et al. | Jun 2010 | A1 |
| 20100147945 | Bando et al. | Jun 2010 | A1 |
| 20100153540 | Li et al. | Jun 2010 | A1 |
| 20100157848 | Das et al. | Jun 2010 | A1 |
| 20100161424 | Sylvain | Jun 2010 | A1 |
| 20100161566 | Adair et al. | Jun 2010 | A1 |
| 20100161728 | Drozt et al. | Jun 2010 | A1 |
| 20100169157 | Muhonen et al. | Jul 2010 | A1 |
| 20100169192 | Zoldi | Jul 2010 | A1 |
| 20100192082 | Sodah | Jul 2010 | A1 |
| 20100199332 | Bachmann et al. | Aug 2010 | A1 |
| 20100199338 | Craddock et al. | Aug 2010 | A1 |
| 20100211464 | Zhu et al. | Aug 2010 | A1 |
| 20100223105 | Gassewitz et al. | Sep 2010 | A1 |
| 20100223145 | Dragt | Sep 2010 | A1 |
| 20100228624 | Morris et al. | Sep 2010 | A1 |
| 20100228625 | Priyadarshan et al. | Sep 2010 | A1 |
| 20100228638 | Mikan et al. | Sep 2010 | A1 |
| 20100235220 | Guha et al. | Sep 2010 | A1 |
| 20100257065 | Gupta et al. | Oct 2010 | A1 |
| 20100262467 | Barnhill, Jr. et al. | Oct 2010 | A1 |
| 20100269175 | Stolfo | Oct 2010 | A1 |
| 20100274678 | Rolf et al. | Oct 2010 | A1 |
| 20100293094 | Kolkowitz et al. | Nov 2010 | A1 |
| 20100306827 | Esteve Balducci et al. | Dec 2010 | A1 |
| 20100313009 | Combet et al. | Dec 2010 | A1 |
| 20100321296 | Gross | Dec 2010 | A1 |
| 20100333170 | Cox et al. | Dec 2010 | A1 |
| 20110015497 | Eggenberger et al. | Jan 2011 | A1 |
| 20110022483 | Hammad | Jan 2011 | A1 |
| 20110022517 | Hammad | Jan 2011 | A1 |
| 20110023115 | Wright | Jan 2011 | A1 |
| 20110029339 | Callahan | Feb 2011 | A1 |
| 20110035302 | Martell et al. | Feb 2011 | A1 |
| 20110047072 | Ciurea | Feb 2011 | A1 |
| 20110055627 | Zawacki et al. | Mar 2011 | A1 |
| 20110065490 | Lutnick | Mar 2011 | A1 |
| 20110082768 | Eisen | Apr 2011 | A1 |
| 20110082858 | Yu et al. | Apr 2011 | A1 |
| 20110106610 | Landis et al. | May 2011 | A1 |
| 20110112901 | Fried et al. | May 2011 | A1 |
| 20110113388 | Eisen et al. | May 2011 | A1 |
| 20110119267 | Forman et al. | May 2011 | A1 |
| 20110153426 | Reddy et al. | Jun 2011 | A1 |
| 20110161228 | Suzuki et al. | Jun 2011 | A1 |
| 20110173281 | Smith | Jul 2011 | A1 |
| 20110184778 | Graepel et al. | Jul 2011 | A1 |
| 20110194679 | Patisaul et al. | Aug 2011 | A1 |
| 20110225091 | Plastina et al. | Sep 2011 | A1 |
| 20110238575 | Nightengale et al. | Sep 2011 | A1 |
| 20110251951 | Kolkowitz et al. | Oct 2011 | A1 |
| 20110258118 | Ciurea | Oct 2011 | A1 |
| 20110271225 | Van Roy et al. | Nov 2011 | A1 |
| 20110282778 | Wright et al. | Nov 2011 | A1 |
| 20110288932 | Marks et al. | Nov 2011 | A1 |
| 20110302087 | Crooks | Dec 2011 | A1 |
| 20110302096 | Lowry | Dec 2011 | A1 |
| 20110307341 | Zohar et al. | Dec 2011 | A1 |
| 20110313847 | Cao et al. | Dec 2011 | A1 |
| 20110314557 | Marshall | Dec 2011 | A1 |
| 20120022883 | Morrison | Jan 2012 | A1 |
| 20120030083 | Newman et al. | Feb 2012 | A1 |
| 20120030757 | Baikalov et al. | Feb 2012 | A1 |
| 20120030771 | Pierson et al. | Feb 2012 | A1 |
| 20120036042 | Graylin et al. | Feb 2012 | A1 |
| 20120036051 | Sachson | Feb 2012 | A1 |
| 20120036261 | Salazar et al. | Feb 2012 | A1 |
| 20120041841 | Hu et al. | Feb 2012 | A1 |
| 20120042361 | Wong | Feb 2012 | A1 |
| 20120054136 | Maulik | Mar 2012 | A1 |
| 20120054847 | Schultz et al. | Mar 2012 | A1 |
| 20120059711 | Ramer et al. | Mar 2012 | A1 |
| 20120060863 | Speckmaier et al. | Mar 2012 | A1 |
| 20120078708 | Taylor et al. | Mar 2012 | A1 |
| 20120084203 | Mehew et al. | Apr 2012 | A1 |
| 20120084860 | Cao | Apr 2012 | A1 |
| 20120094639 | Carlson et al. | Apr 2012 | A1 |
| 20120096076 | Chan | Apr 2012 | A1 |
| 20120096557 | Britton et al. | Apr 2012 | A1 |
| 20120101939 | Kasower | Apr 2012 | A1 |
| 20120150742 | Poon et al. | Jun 2012 | A1 |
| 20120150750 | Law et al. | Jun 2012 | A1 |
| 20120157062 | Kim et al. | Jun 2012 | A1 |
| 20120158586 | Ganti et al. | Jun 2012 | A1 |
| 20120166533 | Rubinstein et al. | Jun 2012 | A1 |
| 20120173465 | Hore et al. | Jul 2012 | A1 |
| 20120174223 | Eisen | Jul 2012 | A1 |
| 20120179558 | Fischer | Jul 2012 | A1 |
| 20120197981 | Chan | Aug 2012 | A1 |
| 20120204262 | Thomas et al. | Aug 2012 | A1 |
| 20120215777 | Malik et al. | Aug 2012 | A1 |
| 20120215896 | Johannsen | Aug 2012 | A1 |
| 20120216282 | Pappu | Aug 2012 | A1 |
| 20120221404 | Ahmed et al. | Aug 2012 | A1 |
| 20120221470 | Lyon | Aug 2012 | A1 |
| 20120222111 | Oliver et al. | Aug 2012 | A1 |
| 20120233640 | Odryna et al. | Sep 2012 | A1 |
| 20120233665 | Ranganathan et al. | Sep 2012 | A1 |
| 20120239553 | Gonen et al. | Sep 2012 | A1 |
| 20120239574 | Smith et al. | Sep 2012 | A1 |
| 20120239774 | Tola et al. | Sep 2012 | A1 |
| 20120254320 | Dove et al. | Oct 2012 | A1 |
| 20120271860 | Graham, Jr. et al. | Oct 2012 | A1 |
| 20120278127 | Kirakosyan et al. | Nov 2012 | A1 |
| 20120278321 | Traub et al. | Nov 2012 | A1 |
| 20120295580 | Corner | Nov 2012 | A1 |
| 20120297380 | Colbert et al. | Nov 2012 | A1 |
| 20120299925 | Najork et al. | Nov 2012 | A1 |
| 20120311162 | Paulsen et al. | Dec 2012 | A1 |
| 20120323788 | Keresman et al. | Dec 2012 | A1 |
| 20120323836 | Wright et al. | Dec 2012 | A1 |
| 20120324027 | Vaynblat et al. | Dec 2012 | A1 |
| 20120324060 | Afergan et al. | Dec 2012 | A1 |
| 20120330787 | Hanson et al. | Dec 2012 | A1 |
| 20130005299 | Raleigh | Jan 2013 | A1 |
| 20130006743 | Moore et al. | Jan 2013 | A1 |
| 20130018789 | Kaufmann | Jan 2013 | A1 |
| 20130018791 | Mendicino et al. | Jan 2013 | A1 |
| 20130024300 | Choudhuri et al. | Jan 2013 | A1 |
| 20130036304 | Lin et al. | Feb 2013 | A1 |
| 20130040603 | Stahlberg et al. | Feb 2013 | A1 |
| 20130042298 | Plaza Fonseca et al. | Feb 2013 | A1 |
| 20130054433 | Giard et al. | Feb 2013 | A1 |
| 20130055388 | Thomas et al. | Feb 2013 | A1 |
| 20130073463 | Dimmick et al. | Mar 2013 | A1 |
| 20130073473 | Heath | Mar 2013 | A1 |
| 20130080327 | Baldrick et al. | Mar 2013 | A1 |
| 20130085841 | Singleton et al. | Apr 2013 | A1 |
| 20130097673 | Meehan et al. | Apr 2013 | A1 |
| 20130097701 | Moyle et al. | Apr 2013 | A1 |
| 20130097706 | Titonis et al. | Apr 2013 | A1 |
| 20130103482 | Song et al. | Apr 2013 | A1 |
| 20130103629 | Vaiciulis et al. | Apr 2013 | A1 |
| 20130110623 | Kilroy et al. | May 2013 | A1 |
| 20130110637 | Bott | May 2013 | A1 |
| 20130111592 | Zhu et al. | May 2013 | A1 |
| 20130117832 | Gandhi | May 2013 | A1 |
| 20130124329 | Tengler | May 2013 | A1 |
| 20130124332 | Doughty et al. | May 2013 | A1 |
| 20130124333 | Doughty et al. | May 2013 | A1 |
| 20130129071 | Teitelman et al. | May 2013 | A1 |
| 20130144539 | Allen et al. | Jun 2013 | A1 |
| 20130148525 | Sanchez et al. | Jun 2013 | A1 |
| 20130159192 | Partridge et al. | Jun 2013 | A1 |
| 20130159195 | Kirillin et al. | Jun 2013 | A1 |
| 20130179878 | Dain | Jul 2013 | A1 |
| 20130185764 | Krstić et al. | Jul 2013 | A1 |
| 20130197998 | Buhrmann et al. | Aug 2013 | A1 |
| 20130198066 | Wall et al. | Aug 2013 | A1 |
| 20130204793 | Kerridge et al. | Aug 2013 | A1 |
| 20130217330 | Gardenfors et al. | Aug 2013 | A1 |
| 20130218947 | Zur et al. | Aug 2013 | A1 |
| 20130226692 | Kouladjie et al. | Aug 2013 | A1 |
| 20130226717 | Ahluwalia et al. | Aug 2013 | A1 |
| 20130229693 | Harada | Sep 2013 | A1 |
| 20130253965 | Joseph | Sep 2013 | A1 |
| 20130273879 | Eisen et al. | Oct 2013 | A1 |
| 20130290119 | Howe et al. | Oct 2013 | A1 |
| 20130325601 | Shekhawat et al. | Dec 2013 | A1 |
| 20130326007 | Turner et al. | Dec 2013 | A1 |
| 20130339186 | French | Dec 2013 | A1 |
| 20130339848 | Patil et al. | Dec 2013 | A1 |
| 20140019542 | Rao et al. | Jan 2014 | A1 |
| 20140032902 | Agrawal et al. | Jan 2014 | A1 |
| 20140095320 | Sivaramakrishnan et al. | Apr 2014 | A1 |
| 20140114821 | Yoshioka et al. | Apr 2014 | A1 |
| 20140120864 | Manolarakis et al. | May 2014 | A1 |
| 20140122343 | Einav | May 2014 | A1 |
| 20140122697 | Liu et al. | May 2014 | A1 |
| 20140129322 | George et al. | May 2014 | A1 |
| 20140148197 | Shields | May 2014 | A1 |
| 20140180802 | Boal | Jun 2014 | A1 |
| 20140197950 | Shupp et al. | Jul 2014 | A1 |
| 20140258125 | Gerber et al. | Sep 2014 | A1 |
| 20140289867 | Bukai | Sep 2014 | A1 |
| 20140361926 | Eisen et al. | Dec 2014 | A1 |
| 20150026027 | Priess et al. | Jan 2015 | A1 |
| 20150039596 | Stewart | Feb 2015 | A1 |
| 20150046989 | Oberheide et al. | Feb 2015 | A1 |
| 20150066979 | Zhang et al. | Mar 2015 | A1 |
| 20150088980 | Lakes et al. | Mar 2015 | A1 |
| 20150106198 | Miller et al. | Apr 2015 | A1 |
| 20150106270 | Burrell et al. | Apr 2015 | A1 |
| 20150120717 | Kim et al. | Apr 2015 | A1 |
| 20150127825 | Johannsen | May 2015 | A1 |
| 20150142767 | Wu et al. | May 2015 | A1 |
| 20150161207 | Li et al. | Jun 2015 | A1 |
| 20150186901 | Miltonberger | Jul 2015 | A1 |
| 20150188897 | Grigorovici et al. | Jul 2015 | A1 |
| 20150193769 | Barber | Jul 2015 | A1 |
| 20150193821 | Izumori et al. | Jul 2015 | A1 |
| 20150205978 | Eisen et al. | Jul 2015 | A1 |
| 20150221019 | Eisen | Aug 2015 | A1 |
| 20150235258 | Shah et al. | Aug 2015 | A1 |
| 20150235275 | Shah et al. | Aug 2015 | A1 |
| 20150242861 | Baldassano | Aug 2015 | A9 |
| 20150254658 | Bondesen et al. | Sep 2015 | A1 |
| 20150294316 | Eisen | Oct 2015 | A1 |
| 20150326517 | Block et al. | Nov 2015 | A1 |
| 20150350856 | Circosta et al. | Dec 2015 | A1 |
| 20160019546 | Eisen | Jan 2016 | A1 |
| 20160021084 | Eisen | Jan 2016 | A1 |
| 20160034954 | Tollinger et al. | Feb 2016 | A1 |
| 20160036782 | Jeffrey et al. | Feb 2016 | A1 |
| 20160125461 | Sivaramakrishnan et al. | May 2016 | A1 |
| 20160182657 | Mukherjee et al. | Jun 2016 | A1 |
| 20160188893 | Ghafourifar | Jun 2016 | A1 |
| 20160203487 | Eisen | Jul 2016 | A1 |
| 20160246581 | Jimenez et al. | Aug 2016 | A1 |
| 20160275545 | Dasdan et al. | Sep 2016 | A1 |
| 20160321701 | Tollinger et al. | Nov 2016 | A1 |
| 20160328710 | Britton et al. | Nov 2016 | A1 |
| 20170039571 | Eisen | Feb 2017 | A1 |
| 20170053208 | Krishnamurthy et al. | Feb 2017 | A1 |
| 20170142106 | Eisen et al. | May 2017 | A1 |
| 20170364918 | Malhotra et al. | Dec 2017 | A1 |
| 20180089459 | Eisen et al. | Mar 2018 | A1 |
| 20180108029 | Sinha et al. | Apr 2018 | A1 |
| 20180121915 | Britton et al. | May 2018 | A1 |
| 20180227299 | Varon et al. | Aug 2018 | A1 |
| 20180262478 | Eisen | Sep 2018 | A1 |
| 20180322500 | Eisen | Nov 2018 | A1 |
| 20190028472 | Eisen | Jan 2019 | A1 |
| 20190066192 | Eisen | Feb 2019 | A1 |
| 20190340642 | Barber | Nov 2019 | A1 |
| 20190356659 | Eisen et al. | Nov 2019 | A1 |
| 20190370859 | Traasdahl et al. | Dec 2019 | A1 |
| 20200005315 | Eisen | Jan 2020 | A1 |
| 20200013064 | Eisen | Jan 2020 | A1 |
| 20200034845 | Eisen | Jan 2020 | A1 |
| 20200064444 | Regani et al. | Feb 2020 | A1 |
| 20200092287 | Cano et al. | Mar 2020 | A1 |
| 20200218763 | Barber | Jul 2020 | A1 |
| 20200219173 | Eisen | Jul 2020 | A1 |
| 20200226186 | Liodden et al. | Jul 2020 | A1 |
| 20200294086 | Traasdahl et al. | Sep 2020 | A1 |
| 20200380162 | Eisen et al. | Dec 2020 | A1 |
| 20210224811 | Eisen | Jul 2021 | A1 |
| 20210226950 | Eisen | Jul 2021 | A1 |
| 20210281580 | Eisen | Sep 2021 | A1 |
| 20210336955 | Huffman et al. | Oct 2021 | A1 |
| 20220043881 | Putnam et al. | Feb 2022 | A1 |
| 20220129969 | Eisen | Apr 2022 | A1 |
| 20220269818 | Eisen | Aug 2022 | A1 |
| 20220270100 | Eisen | Aug 2022 | A1 |
| 20230046734 | Eisen | Feb 2023 | A1 |
| 20230254311 | Huffman et al. | Aug 2023 | A1 |
| 20240015173 | Putnam et al. | Jan 2024 | A1 |
| 20240073209 | Eisen | Feb 2024 | A1 |
| 20240078546 | Britton et al. | Mar 2024 | A1 |
| 20240089267 | Eisen | Mar 2024 | A1 |
| 20240127314 | Eisen | Apr 2024 | A1 |
| 20240137351 | Eisen | Apr 2024 | A1 |
| Number | Date | Country |
|---|---|---|
| 2022206815 | Aug 2022 | AU |
| 0 418 144 | Mar 1991 | EP |
| 0 645 692 | Mar 1995 | EP |
| 0 923 039 | Jun 1999 | EP |
| 1 067 792 | Jan 2001 | EP |
| 1 209 935 | May 2002 | EP |
| 1 256 911 | Nov 2002 | EP |
| 1 201 070 | Jun 2006 | EP |
| 1 703 382 | Sep 2006 | EP |
| 1 197 032 | Aug 2007 | EP |
| 2 009 569 | Dec 2008 | EP |
| 2 154 891 | Feb 2010 | EP |
| 2 323 091 | May 2011 | EP |
| 3 583 758 | Apr 2021 | EP |
| 3 937 456 | Jan 2022 | EP |
| 2 491 101 | Nov 2012 | GB |
| 2 492 604 | Jan 2013 | GB |
| 05-257602 | Oct 1993 | JP |
| 2000-020467 | Jan 2000 | JP |
| 2000-099250 | Apr 2000 | JP |
| 2000-137755 | May 2000 | JP |
| 2000-242582 | Sep 2000 | JP |
| 2000-276281 | Oct 2000 | JP |
| 2002-007697 | Jan 2002 | JP |
| 2002-297869 | Oct 2002 | JP |
| 2002-304568 | Oct 2002 | JP |
| 2003-050910 | Feb 2003 | JP |
| 2005-063216 | Mar 2005 | JP |
| 2005-115644 | Apr 2005 | JP |
| 2005-135431 | May 2005 | JP |
| 2006-004333 | Jan 2006 | JP |
| 2007-018446 | Jan 2007 | JP |
| 2007-041642 | Feb 2007 | JP |
| 2007-272520 | Oct 2007 | JP |
| 2007-282249 | Oct 2007 | JP |
| 2008-022298 | Jan 2008 | JP |
| 2008-065363 | Mar 2008 | JP |
| 2008-171315 | Jul 2008 | JP |
| 2008-535062 | Aug 2008 | JP |
| 2008-535124 | Aug 2008 | JP |
| 2008-242805 | Oct 2008 | JP |
| 2008-243008 | Oct 2008 | JP |
| 2008-257434 | Oct 2008 | JP |
| 2008-269229 | Nov 2008 | JP |
| 4202314 | Dec 2008 | JP |
| 2009-017298 | Jan 2009 | JP |
| 2009-048538 | Mar 2009 | JP |
| 2009-512940 | Mar 2009 | JP |
| 2009-122880 | Jun 2009 | JP |
| 2009-175984 | Aug 2009 | JP |
| 2009-271661 | Nov 2009 | JP |
| 2010-020728 | Jan 2010 | JP |
| 2010-061254 | Mar 2010 | JP |
| 2010-122955 | Jun 2010 | JP |
| 2010-122956 | Jun 2010 | JP |
| 2010-146153 | Jul 2010 | JP |
| 2010-225040 | Oct 2010 | JP |
| 2010-250664 | Nov 2010 | JP |
| 2011-065531 | Mar 2011 | JP |
| 2011-134252 | Jul 2011 | JP |
| 2011-159264 | Aug 2011 | JP |
| 2011-159307 | Aug 2011 | JP |
| 2011-524560 | Sep 2011 | JP |
| 2011-210263 | Oct 2011 | JP |
| 2012-234503 | Nov 2012 | JP |
| 5191376 | May 2013 | JP |
| 5216932 | Jun 2013 | JP |
| 2015-503148 | Jan 2015 | JP |
| 10-1999-0015738 | Mar 1999 | KR |
| 10-0645983 | Nov 2006 | KR |
| 10-2008-0044558 | May 2008 | KR |
| 10-2009-0051977 | Sep 2009 | KR |
| 10-2009-0012013 | May 2010 | KR |
| 10-2010-0085888 | Jul 2010 | KR |
| WO 96041488 | Dec 1996 | WO |
| WO 97003410 | Jan 1997 | WO |
| WO 97023816 | Jul 1997 | WO |
| WO 99050775 | Oct 1999 | WO |
| WO 01011450 | Feb 2001 | WO |
| WO 01033520 | May 2001 | WO |
| WO 01086877 | Nov 2001 | WO |
| WO 01095550 | Dec 2001 | WO |
| WO 01097134 | Dec 2001 | WO |
| WO 02001462 | Jan 2002 | WO |
| WO 02071176 | Sep 2002 | WO |
| WO 02091226 | Nov 2002 | WO |
| WO 03017155 | Feb 2003 | WO |
| WO 03025868 | Mar 2003 | WO |
| WO 03075197 | Sep 2003 | WO |
| WO 03075197 | Dec 2003 | WO |
| WO 02037219 | May 2004 | WO |
| WO 2004038997 | May 2004 | WO |
| WO 2005038818 | Apr 2005 | WO |
| WO 2005099166 | Oct 2005 | WO |
| WO 2006135367 | Dec 2006 | WO |
| WO 2007001394 | Jan 2007 | WO |
| WO 2007045818 | Apr 2007 | WO |
| WO 2007072238 | Jun 2007 | WO |
| WO 2007075573 | Jul 2007 | WO |
| WO 2008029828 | Mar 2008 | WO |
| WO 2008054849 | May 2008 | WO |
| WO 2009132148 | Oct 2009 | WO |
| WO 2011081818 | Jul 2011 | WO |
| WO 2011104864 | Sep 2011 | WO |
| WO 2012054646 | Apr 2012 | WO |
| WO 2012061801 | May 2012 | WO |
| WO 2012142121 | Oct 2012 | WO |
| WO 2012142584 | Oct 2012 | WO |
| WO 2013006538 | Jan 2013 | WO |
| WO 2013070687 | May 2013 | WO |
| WO 2013074750 | May 2013 | WO |
| WO 2013142722 | Sep 2013 | WO |
| WO 2014022813 | Feb 2014 | WO |
| WO 2014078569 | May 2014 | WO |
| WO 2017040799 | Mar 2017 | WO |
| WO 2018129373 | Jul 2018 | WO |
| WO 2018151822 | Aug 2018 | WO |
| WO 2022104341 | May 2022 | WO |
| Entry |
|---|
| Banking Services Newsletter, “Keeping You Up-to-Date on Banking Developments Throughout the UC System”, University of California, Office of the President, Banking Services Group, Newsletter 1, Dec. 2005, p. 1. |
| Bharosa, “Bharosa Authenticator”, http://www.bharosa.com/authenticator.html, Jan. 18, 2007, pp. 3. |
| Bharosa, “Bharosa Announces Online Authentication Solution to Counter Check 21-Based Fraud”, http://www.bharosa.com/news/PR-110705.html, Jan. 18, 2007, pp. 2. |
| Bourobou et al., “User Activity Recognition in Smart Homes Using Pattern Clustering Applied to Temporal ANN Algorithm”, Sensors, May 21, 2015, vol. 15, pp. 11953-11971. |
| Broenink, Ralph, “Using Browser Properties for Fingerprinting Purposes”, 16th Biennial Twente Student Conference on IT, Enschede, Holanda, Jan. 2012, pp. 8. |
| Darlin, Damon, “Opening the Door on the Credit Report and Throwing Away the Lock”, http://www.nytimes.com/2006/03/18/business/yourmoney/18money.html, The New York Times, Saturday Mar. 18, 2006, pp. 2. |
| Derfler, Jr. et al., “How Networks Work”, Millennium Edition, Que Corporation, Indianapolis, IN, Sep. 2000, p. 230. |
| Eckersley, Peter, “How Unique Is Your Web Browser?”, Electronic Frontier Foundation, 2010, pp. 19. |
| Elkhodr et al., “A Review of Mobile Location Privacy in the Internet of Things”, 2012 Tenth International Conference on ICT and Knowledge Engineering, 2012, pp. 266-272. |
| Faulkner, Alisdair, “Fraud Network Whitepaper”, ThreatMetrix, Whitepaper, 2010, pp. 16. |
| Gralla, Preston, “How The Internet Works”, Millennium Edition, Que Corporation, Indianapolis, IN, Aug. 1999, pp. 329. |
| Gueye et al., “Constraint-Based Geolocation of Internet Hosts”, ACM Internet Measurement Conference 2004, Oct. 25-27, 2004, Taormina, Sicily, Italy, vol. 14, No. 6, pp. 288-293. |
| “ISO 8583”, Wikipedia, http://en.wikipedia.org/wiki/ISO_8583, dated Apr. 13, 2015 in 14 pages. |
| Kisel et al., “Utilizing a Personalization-Enabled Access Node in Support of Converged Cross-Domain Scoring and Advertising”, Bell Labs Technical Journal, 2010, vol. 15, No. 1, pp. 77-94. |
| Kohno et al., “Remote Physical Device Fingerprinting”, Proceedings of 2005 IEEE Symposium on Security and Privacy, May 8-11, 2005, Oakland, CA, pp. 211-225. |
| Manavoglu et al., “Probabilistic User Behavior Models”, ICDM, Third IEEE International Conference on Data Mining, Nov. 19-22, 2003, pp. 203-210. |
| Marshall, Jack, “Device Fingerprinting Could Be Cookie Killer”, ClickZ. Mar. 2, 2011, pp. 7. http://www.clickz.com/clickz/news/2030243/device-fingerprinting-cookie-killer. |
| Quora, [No Author Listed], How does a tracking pixel work? by Quora, 2011. |
| Schmücker, Niklas, “Web Tracking”, SNET2 Seminar Paper—Summer Term 2011, Berlin University of Technology, pp. 12. |
| Shabtai et al., “Andromaly': A Behavioral Malware Detection Framework for Android Devices”, Journal of Intelligent Information Systems, 2012, vol. 38, pp. 161-190. |
| TechWeb, “Wells Fargo Intros Anti-Theft Alerts”, http://www.techweb.com/wire/166404177, Aug. 1, 2005, pp. 1. |
| The Knightmare, “Secrets of a Super Hacker”, Loompanics Unlimited, Port Townsend, Washington, 1994, pp. 233. |
| “UPIC Marketing Guide—The Clearing House”. http://www.upic.com/infofiles/UPIC_Marketing_Guide.pdf, as printed Dec. 19, 2006. pp. 1-16. |
| White, Ron, “How Computers Work”, Millennium Edition, Que Corporation, Indianapolis, IN, Sep. 1999, pp. 284. |
| Official Communication in European Patent Application No. 05818903.6, dated Dec. 23, 2011. |
| Official Communication in European Patent Application No. 05818903.6, dated Mar. 18, 2014. |
| Official Communication in European Patent Application No. 05818903.6, dated Jul. 18, 2017. |
| Official Communication in European Patent Application No. 19189189.4, dated Jan. 21, 2020. |
| Official Communication in European Patent Application No. 19189189.4, dated Nov. 19, 2020. |
| International Search Report and Written Opinion for Application No. PCT/US2005/035532, dated Oct. 29, 2007. |
| International Preliminary Report on Patentability and Written Opinion for Application No. PCT/US2005/035532, dated Jan. 9, 2008. |
| Official Communication in European Patent Application No. 6845722.5, dated Mar. 13, 2009. |
| Official Communication in European Patent Application No. 19181057.1, dated Sep. 17, 2019. |
| Official Communication in European Patent Application No. 19181057.1, dated Oct. 25, 2021. |
| Official Communication in European Patent Application No. 8159110.9, dated Oct. 27, 2008. |
| Official Communication in European Patent Application No. 8159110.9, dated Mar. 22, 2010. |
| Summons to Attend Oral Proceedings received in European Application No. EP08159110, dated Jul. 23, 2020. |
| International Search Report and Written Opinion for Application No. PCT/US2006/048251, dated Feb. 26, 2008. |
| International Preliminary Report on Patentability and Written Opinion for Application No. PCT/US2006/048251, dated Jun. 18, 2008. |
| International Search Report and Written Opinion for Application No. PCT/US2007/065776, dated Jul. 3, 2008. |
| International Preliminary Report on Patentability and Written Opinion for Application No. PCT/US2007/065776, dated Sep. 30, 2008. |
| International Search Report and Written Opinion received in PCT Application No. PCT/US2005/020750, dated Jun. 13, 2008. |
| International Preliminary Report on Patentability and Written Opinion received in PCT Application No. PCT/US2005/020750, dated Jul. 1, 2008. |
| Official Communication in European Patent Application No. 08165224.0, dated Nov. 15, 2010. |
| Supplementary European Search Report for Application No. EP09735653, dated Dec. 28, 2011. |
| Official Communication for Application No. EP09735653, dated Jan. 4, 2013. |
| Summons to Attend Oral Proceedings received in European Application No. EP09735653, dated Oct. 7, 2016. |
| International Search Report and Written Opinion for Application No. PCT/US2009/041462, dated Dec. 1, 2009. |
| International Preliminary Report on Patentability and Written Opinion for Application No. PCT/US2009/041462, dated Nov. 4, 2010. |
| International Search Report and Written Opinion for Application No. PCT/US2011/056948, dated Apr. 18, 2012. |
| International Preliminary Report on Patentability in Application No. PCT/US2011/056948, dated May 2, 2013. |
| International Search Report and Written Opinion for Application No. PCT/US2013/033357, dated Jul. 10, 2013. |
| International Preliminary Report on Patentability in Application No. PCT/US2013/033357, dated Sep. 23, 2014. |
| International Search Report and Written Opinion for Application No. PCT/US2013/053495, dated Nov. 22, 2013. |
| International Preliminary Report on Patentability in Application No. PCT/US2013/053495, dated Feb. 3, 2015. |
| International Search Report and Written Opinion for Application No. PCT/US2013/070146, dated Mar. 3, 2014. |
| International Preliminary Report on Patentability in Application No. PCT/US2013/070146, dated May 28, 2015. |
| Official Communication received in European Patent Application No. 16766741.9, dated Aug. 20, 2019. |
| Summons to Attend received in European Patent Application No. 16766741.9, dated Mar. 25, 2020. |
| Official Communication received in European Patent Application No. 21154719.5, dated Jun. 15, 2021. |
| International Search Report and Written Opinion for Application No. PCT/US2012/065220, dated Mar. 21, 2013. |
| International Preliminary Report on Patentability in Application No. PCT/US2012/065220, dated May 30, 2014. |
| International Search Report and Written Opinion for Application No. PCT/US2016/049930, dated Nov. 9, 2016. |
| Provisional Application as filed in U.S. Appl. No. 61/324,312, dated Apr. 15, 2010 in 15 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 61605677 | Mar 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17230272 | Apr 2021 | US |
| Child | 18540108 | US | |
| Parent | 16435092 | Jun 2019 | US |
| Child | 17230272 | US | |
| Parent | 15471990 | Mar 2017 | US |
| Child | 16435092 | US | |
| Parent | 13782745 | Mar 2013 | US |
| Child | 15471990 | US |
