Data processing systems for fulfilling data subject access requests and related methods
Responding to a data subject access request includes receiving the request and identifying the requestor and source. In response to identifying the requestor and source, a computer processor determines whether the data subject access request is subject to fulfillment constraints, including whether the requestor or source is malicious. If so, then the computer processor denies the request or requests a processing fee prior to fulfillment. If not, then the computer processor fulfills the request.
Latest OneTrust, LLC Patents:
- Systems and methods for automatically blocking the use of tracking tools
- Data processing systems and methods for automatically blocking the use of tracking tools
- DATA PROCESSING CONSENT CAPTURE SYSTEMS AND RELATED METHODS
- Data processing systems and methods for automatically protecting sensitive data within privacy management systems
- SYSTEMS AND METHODS FOR MITIGATING RISKS OF THIRD-PARTY COMPUTING SYSTEM FUNCTIONALITY INTEGRATION INTO A FIRST-PARTY COMPUTING SYSTEM
This application is a continuation-in-part of U.S. patent application Ser. No. 17/201,040, filed Mar. 15, 2021, which is a continuation of U.S. patent application Ser. No. 17/019,771, filed Sep. 14, 2020, now U.S. Pat. No. 10,949,567, issued Mar. 16, 2021, which is a continuation of U.S. patent application Ser. No. 16/786,196, filed Feb. 10, 2020, now U.S. Pat. No. 10,776,515, issued Sep. 15, 2020, which is a continuation of U.S. patent application Ser. No. 16/512,011, filed Jul. 15, 2019, now U.S. Pat. No. 10,558,821, issued Feb. 11, 2020, which is a continuation of U.S. patent application Ser. No. 16/226,290, filed Dec. 19, 2018, now U.S. Pat. No. 10,354,089, issued Jul. 16, 2019, which is a continuation of U.S. patent application Ser. No. 16/054,672, filed Aug. 3, 2018, now U.S. Pat. No. 10,169,609, issued Jan. 1, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/547,530, filed Aug. 18, 2017, and which is also a continuation-in-part of U.S. patent application Ser. No. 15/996,208, filed Jun. 1, 2018, now U.S. Pat. No. 10,181,051, issued Jan. 15, 2019, which claims priority from U.S. Provisional Patent Application Ser. No. 62/537,839, filed Jul. 27, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/853,674, filed Dec. 22, 2017, now U.S. Pat. No. 10,019,597, issued Jul. 10, 2018, which claims priority from U.S. Provisional Patent Application Ser. No. 62/541,613, filed Aug. 4, 2017, and is also a continuation-in-part of U.S. patent application Ser. No. 15/619,455, filed Jun. 10, 2017, now U.S. Pat. No. 9,851,966, issued Dec. 26, 2017, which is a continuation-in-part of U.S. patent application Ser. No. 15/254,901, filed Sep. 1, 2016, now U.S. Pat. No. 9,729,583, issued Aug. 8, 2017, which claims priority from: (1) U.S. Provisional Patent Application Ser. No. 62/360,123, filed Jul. 8, 2016; (2) U.S. Provisional Patent Application Ser. No. 62/353,802, filed Jun. 23, 2016; and (3) U.S. Provisional Patent Application Ser. No. 62/348,695, filed Jun. 10, 2016. The disclosures of all of the above patent applications are hereby incorporated herein by reference in their entirety.
BACKGROUNDOver the past years, privacy and security policies, and related operations have become increasingly important with respect to the handling of personal data (which may include sensitive personal data). Such personal data may include, but is not limited to, personally identifiable information (PII), which may be information that directly (or indirectly) identifies an individual or entity. Examples of PII include names, addresses, dates of birth, social security numbers, and biometric identifiers such as a person's fingerprints or picture. Other personal data may include, for example, customers' Internet browsing habits, purchase history, or even their preferences (e.g., likes and dislikes, such as provided or obtained through social media).
To manage personal data, many organizations have implemented operational processes that comply with certain rights related to a data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example, a right to obtain confirmation of whether a particular organization is processing their personal data, a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected), and other such rights. Some regulations require organizations to comply with requests for such information (e.g., Data Subject Access Requests) within relatively short periods of time (e.g., 30 days). Accordingly, an organization's processing of such requests can require a significant amount of computing resources, especially when the organization is required to comply with such requests in a relatively short period of time. A significant challenge encountered by many organizations is that requests for personal data are not necessarily legitimate, but instead are submitted for malicious purposes such as to overexert the organizations' computing resources in processing the requests. For example, a malicious party may submit an excessive number of requests for personal data for the purpose of taxing an organization's computing resources in processing the requests. Therefore, a need exists in the arts for improved systems and methods for identifying and handling malicious requests associated with rights related to personal data.
SUMMARYIt should be appreciated that this Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to be used to limit the scope of the claimed subject matter.
In general, various embodiments of the present invention provide methods, apparatuses, systems, computing devices, computing entities, and/or the like for identifying a data subject access request is subject to fulfillment constraint data and processing the data subject access request accordingly. In accordance with various embodiments, a method is provided. According, the method comprises: providing, by computing hardware, a query interface that is accessible via a public data network and that is configured for querying a plurality of data storage systems included in a private data network; determining, with the computing hardware, that a plurality of queries comprising data subject access requests have been received via the query interface from an Internet Protocol (IP) address; responsive to determining that the plurality of queries have originated from the IP address, adding a processing constraint for the IP address to fulfillment constraint data in a data repository; receiving, via the query interface and the public data network, a query comprising a data subject access request from a computing device; determining, by the computing hardware, that the computing device is associated with the IP address; querying, by the computing hardware and using the IP address, the fulfillment constraint data from the data repository to identify the processing constraint; determining, by the computing hardware, that the data subject access request is subject to the processing constraint; and preventing, based on the determining that the data subject access request is subject to the processing constraint, the plurality of data storage systems from executing processing operations or performing network communication for retrieving data responsive to the data subject access request from a plurality of data sources included in the private data network.
According to particular embodiments, the method further comprises: providing, by the computing hardware, an authorization interface that is accessible via the public data network and that is configured for requesting authorization data from the computing device; receiving, by the computing hardware and via the authorization interface, the authorization data from the computing device; and overriding, by the computing hardware, the processing constraint based on receiving the authorization data, wherein overriding the processing constraint permits retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network. In some embodiments, the authorization data comprises at least one of a username, a password, an authorization code, or data confirming payment of a processing fee associated with fulfilling the data subject access request.
According to particular embodiments, adding the processing constraint for the IP address to the fulfillment constraint data in the data repository is based on a number of the plurality of queries originating from the IP address satisfying a threshold quantity within a threshold period of time. According to other embodiments, adding the processing constraint for the IP address to the fulfillment constraint data is based on the IP address being associated with at least one of a competitor of an entity associated with the plurality of data storage systems, a geographic region, a particular political group, or a particular protesting group.
According to particular embodiments, the method further comprises storing, by the computing hardware, documentation supporting preventing retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network. According to particular embodiments, the method further comprises providing, by the computing hardware, for display on the query interface, a reason for preventing retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network.
In accordance with various embodiments, a system is provided comprising a non-transitory computer-readable medium storing instructions and a processing device communicatively coupled to the non-transitory computer-readable medium. Accordingly, the processing device is configured to execute the instructions and thereby perform operations comprising: determining that a plurality of queries comprising data subject access requests have been received via a query interface from a domain, wherein the query interface is accessible via a public data network and is configured for querying a plurality of data storage systems included in a private data network; responsive to determining that the plurality of queries have originated from the domain, adding a processing constraint for the domain to fulfillment constraint data in a data repository; receiving, via the query interface and the public data network, a query comprising a data subject access request from a computing device; determining that the computing device is associated with the domain; querying, using the domain, the fulfillment constraint data from the data repository to identify the processing constraint; determining that the data subject access request is subject to the processing constraint; and preventing, based on the determining that the data subject access request is subject to the processing constraint, the plurality of data storage systems from executing processing operations or performing network communication for retrieving data responsive to the data subject access request from a plurality of data sources included in the private data network.
According to particular embodiments, the operations further comprise: providing an authorization interface that is accessible via the public data network and that is configured for requesting authorization data from the computing device; receiving, via the authorization interface, the authorization data from the computing device; and overriding the processing constraint based on receiving the authorization data, wherein overriding the processing constraint permits retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network. In some embodiments, the authorization data comprises at least one of a username, a password, an authorization code, or data confirming payment of a processing fee associated with fulfilling the data subject access request.
According to particular embodiments, adding the processing constraint for the domain to the fulfillment constraint data in the data repository is based on a number of the plurality of queries originating from the domain satisfying a threshold quantity within a threshold period of time. According to other embodiments, adding the processing constraint for the domain to the fulfillment constraint data is based on the domain being associated with at least one of a competitor of an entity associated with the plurality of data storage systems, a geographic region, a particular political group, or a particular protesting group.
According to particular embodiments, the operations further comprise storing documentation supporting preventing retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network. According to particular embodiments, the operations further comprise providing, for display on the query interface, a reason for preventing retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network.
In accordance with various aspects, a non-transitory computer-readable medium having program code that is stored thereon is provided. Accordingly, the program code is executable by one or more processing devices for performing operations comprising: determining that a first query has been received via a query interface from at least one of an Internet Protocol (IP) address, a domain, or a geographic location wherein the query interface is accessible via a public data network and is configured for querying a data storage system included in a private data network; responsive to determining the first query has originated from at least one of the IP address, the domain, or the geographic location, adding a processing constraint for at least one of the IP address, the domain, or the geographic location to fulfillment constraint data in a data repository; receiving, via the query interface and the public data network, a second query from a computing device; determining that the computing device is associated with at least one of the IP address, the domain, or the geographic location; querying, using at least one of the IP address, the domain, or the geographic location, the fulfillment constraint data from the data repository to identify the processing constraint; determining that the second query is subject to the processing constraint; and preventing, based on the determining that the second query is subject to the processing constraint, the data storage system from executing processing operations or performing network communication for retrieving data responsive to the second query from a data source included in the private data network.
According to particular embodiments, the operations further comprise: providing an authorization interface that is accessible via the public data network and that is configured for requesting authorization data from the computing device; receiving, via the authorization interface, the authorization data from the computing device; and overriding the processing constraint based on receiving the authorization data, wherein overriding the processing constraint permits retrieval of the data responsive to the second query from the data source included in the private data network. In some embodiments, the authorization data comprises at least one of a username, a password, an authorization code, or data confirming payment of a processing fee associated with fulfilling the data subject access request.
According to particular embodiments, adding the processing constraint for at least one of the IP address, the domain, or the geographic location to the fulfillment constraint data is based on at least one of the IP address or the domain being associated with at least one of a competitor of an entity associated with the data storage system, a geographic region, a particular political group, or a particular protesting group. According to particular embodiments, the operations further comprise storing documentation supporting preventing retrieval of the data responsive to the second query from the data source included in the private data network. According to particular embodiments, the operations further comprise providing a reason for display on the query interface for preventing retrieval of the data responsive to the second query from the data source included in the private data network.
The features, functions, and advantages that have been discussed can be achieved independently in various embodiments of the present disclosure or may be combined in yet other embodiments, further details of which can be seen with reference to the following description and drawings.
Various embodiments of a data subject access request fulfillment system are described below. In the course of this description, reference will be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:
Various embodiments now will be described more fully hereinafter with reference to the accompanying drawings. It should be understood that the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art. Like numbers refer to like elements throughout.
Overview and Technical Contributions of Various EmbodimentsAs previously noted, privacy and security policies, and related operations, have become increasingly important over the past years. As a result, many organizations have attempted to implement operational processes that comply with certain rights related to a data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example, a right to obtain confirmation of whether a particular organization is processing their personal data, a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected), and other such rights. Some regulations require organizations to comply with requests for such information (e.g., Data Subject Access Requests) within relatively short periods of time (e.g., 30 days).
However, a technical challenge often encountered by many organizations in their processing of personal data while complying with a data subject's rights related to their personal data that is collected, stored, or otherwise processed by an organization is facilitating (e.g., allowing) the data subject's exercise of such rights when the personal data involved may exist over multiple data sources (e.g., computing devices, data storage, and/or the like) found within multiple data storage systems. As a result, an organization's processing of requests received from data subjects (e.g., individuals) who are exercising their rights related to their personal data can require a significant amount of computing resources.
For instance, many organizations provide a publicly accessible query interface through which data subjects (or lawful representatives thereof) can submit requests (e.g., data subject access requests) related to their personal data being processed by the organizations. For example, many organizations provide a website that is accessible by data subjects over a public data network such as the Internet. Here, the website may include a web form that can be used by the data subjects to submit requests related to the data subjects' personal data being processed by the organizations. Therefore, a data subject wishing to exercise their rights can simply visit an organization's website and use the webform to submit a query that includes a request related to a personal data right that is then often required to be fulfilled by the organization in a timely manner. Since the query interface (e.g., website) is often publicly available, an organization can receive a considerable number of requests at any given time that then requires the organization to devote a significant number of computing resources to timely fulfill the requests. This can become even more of a substantial challenge as personal data collected, stored, or otherwise processed by an organization increases in volume and/or is collected, stored, or otherwise processed over an increasing number of data sources involving multiple data storage systems that are in communication over one or more private data networks.
Another technical challenge encountered by many organizations is the receiving and processing of requests by data subjects, or those who pretend to be data subjects, that are not submitted for valid/legitimate reasons (also referred to as malicious requests). Such actions can prove to be a technical challenge for many organizations in that the organizations can be subject to a wasteful devotion of computing resources in processing such requests when the resources could be used for more meaningful, valid, and/or legitimate purposes. For example, a malicious requestor or source may include a requestor (e.g., an individual) or source that submits an excessive or redundant number of data subject access requests for the purpose of tying up an organization's computing resources unnecessarily, expending the organization's computing resources, disrupting the organization's operations and/or computing resources, and/or the like. Since many organizations provide publicly accessible query interfaces for submitting requests, malicious requestors and/or sources can easily take advantage of such interfaces in submitting malicious requests. Therefore, many organizations are faced with the challenge of recognizing when malicious requests are being submitted, as opposed to valid/legitimate requests, and to eliminate and/or limit such malicious request to avoid wasteful use of computing resources.
Accordingly, various embodiments of the present disclosure overcome many of the technical challenges mentioned above by providing a fulfillment constraint determination system configured to maintain a “blacklist” of malicious requestors and/or sources. As described in further detail herein, this blacklist may include fulfillment constraint data that may be cross-referenced upon receipt of a data subject access request to determine if the data subject access request is subject to one or more response fulfillment (processing) constraints. If the data subject access request is subject to one or more response fulfillment constraints, then the system in particular embodiments initially prevents one or more data storage systems from executing processing operations or performing network communication for retrieving data responsive to the data subject access request from one or more data sources included in a private data network.
In addition, the system in various embodiments may take action on the data subject access request according to one or more limitations. Such actions may entail an action denying a data subject access request (a deny action) or an action fulfilling a data subject access request (a fulfillment action). For instance, a deny action may involve permanently preventing the one or more data storage systems from executing processing operations or performing network communication for retrieving data responsive to the data subject access request. In addition, the system may provide the requestor with information on the reason for denying the request. Such an action thus may entirely eliminate the need for using computing resources unnecessarily for processing a malicious data subject access request.
A fulfillment action may involve fulfilling the request, but only upon a condition and/or requirement being met. For instance, a fulfillment action may involve the system requiring the requestor and/or other system to provide some form of authorization data before allowing the one or more storage systems to execute processing operations or perform network communication for retrieving data responsive to the data subject access request. For example, the authorization data may involve the requestor providing a username, password, authorization code, and/or the like. In another example, the requestor may be required to pay a processing fee to have the request fulfilled. Here, the authorization data may involve data confirming payment of the processing fee. Accordingly, the system may provide the requestor with an authorization interface that requests the authorization data from the requestor and/or is used to acquire the authorization data.
Therefore, the requestor has the choice of meeting the condition and/or requirement or not. This can serve as a further stipulation in having the data subject access request processed. If the requestor refuses to meet the condition and/or requirement, then the system can permanently prevent the one or more data storage systems from executing processing operations or performing network communication for retrieving data responsive to the data subject access request. If the requestor meets the condition and/or requirement, then the system can override the one or more response fulfillment (processing) constraints and permit the one or more data storage systems to execute the processing operations or perform the network communication for retrieving data responsive to the data subject access request. Thus, such action may further help to ensure or verify that the data subject access request is not malicious (is valid/legitimate) before allowing the processing of the request, and again can avoid using computing resources unnecessarily for processing a malicious data subject access request.
Accordingly, in various embodiments, a data subject access request fulfillment system may be implemented in the context of any suitable privacy management system that is configured to ensure compliance with one or more legal or industry standards related to the collection and/or storage of private information (e.g., such as personal data). In various embodiments, a particular organization, sub-group, or other entity may initiate a privacy campaign or other activity (e.g., processing activity) as part of its business activities. In such embodiments, the privacy campaign may include any undertaking by a particular organization (e.g., such as a project or other activity) that includes the collection, entry, and/or storage (e.g., in computer memory) of any personal data associated with one or more individuals (e.g., data subjects). In particular embodiments, a privacy campaign may include any project undertaken by an organization that includes the use of personal data, or any other activity that could have an impact on the privacy of one or more individuals.
In any embodiment described herein, personal data may include, for example: (1) the name of a particular data subject (which may be a particular individual); (2) the data subject's address; (3) the data subject's telephone number; (4) the data subject's e-mail address; (5) the data subject's social security number; (6) information associated with one or more of the data subject's credit accounts (e.g., credit card numbers); (7) banking information for the data subject; (8) location data for the data subject (e.g., their present or past location); (9) internet search history for the data subject; and/or (10) any other suitable personal information, such as other personal information discussed herein. In particular embodiments, such personal data may include one or more cookies (e.g., where the individual is directly identifiable or may be identifiable based at least in part on information stored in the one or more cookies).
Various privacy and security policies (e.g., such as the European Union's General Data Protection Regulation, and other such policies) may provide data subjects (e.g., individuals, organizations, or other entities) with certain rights related to the data subject's personal data that is collected, stored, or otherwise processed by an organization. These rights may include, for example: (1) a right to obtain confirmation of whether a particular organization is processing their personal data; (2) a right to obtain information about the purpose of the processing (e.g., one or more reasons for which the personal data was collected); (3) a right to obtain information about one or more categories of data being processed (e.g., what type of personal data is being collected, stored, etc.); (4) a right to obtain information about one or more categories of recipients with whom their personal data may be shared (e.g., both internally within the organization or externally); (5) a right to obtain information about a time period for which their personal data will be stored (e.g., or one or more criteria used to determine that time period); (6) a right to obtain a copy of any personal data being processed (e.g., a right to receive a copy of their personal data in a commonly used, machine-readable format); (7) a right to request erasure (e.g., the right to be forgotten), rectification (e.g., correction or deletion of inaccurate data), or restriction of processing of their personal data; and (8) any other suitable rights related to the collection, storage, and/or processing of their personal data (e.g., which may be provided by law, policy, industry or organizational practice, etc.).
As may be understood in light of this disclosure, a particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of personal data. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same personal data for a particular individual more than once), and may store data and/or redundant data in one or more particular locations that serve as data sources (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store personal data in a plurality of different locations which may include one or more known and/or unknown locations. As such, complying with particular privacy and security policies related to personal data (e.g., such as responding to one or more requests by data subjects related to their personal data) may be particularly difficult (e.g., in terms of cost, time, etc.). In particular embodiments, the data subject access request fulfillment system may utilize one or more data model generation and population techniques to create a centralized data map with which the system can identify personal data stored, collected, or processed for a particular data subject, a reason for the processing, and any other information related to the processing.
In particular embodiments, the data subject access request fulfillment system is configured to: (1) receive a data subject access request from a data subject, the data subject access request comprising one or more requests related to the one or more rights described above (e.g., a request for a copy of the data subject's personal data, a request regarding how long personal data associated with the data subject is being stored by the system, etc.); (2) process the request; and (3) fulfill the request based at least in part on one or more request parameters.
Automatic Identity Validation Systems
In particular embodiments, when processing a data subject access request, the system may be configured to verify an identity of the data subject prior to processing the request (e.g., or as part of the processing step). In various embodiments, confirming the identity of the data subject may, for example, limit a risk that a third-party or other entity may gain unlawful or unconsented to access to the requestor's personal data. The system may, for example, limit processing and fulfillment of requests relating to a particular data subject to requests that are originated by (e.g., received from) the particular data subject. When processing a data subject access request, the system may be configured to use all reasonable measures to verify the identity of the data subject who requests access (e.g., in particular in the context of online services and online identifiers). In particular embodiments, the system is configured to substantially automatically validate an identity of a data subject when processing the data subject access request.
For example, in particular embodiments, the system may be configured to substantially automatically (e.g., automatically) authenticate and/or validate an identity of a data subject using any suitable technique. These techniques may include, for example: (1) one or more credit-based and/or public- or private-information-based verification techniques; (2) one or more company verification techniques (e.g., in the case of a business-to-business data subject access request); (3) one or more techniques involving integration with a company's employee authentication system; (4) one or more techniques involving a company's (e.g., organization's) consumer portal authentication process; (5) etc. Various exemplary techniques for authenticating a data subject are discussed more fully below.
In particular embodiments, when authenticating a data subject (e.g., validating the data subject's identity), the system may be configured to execute particular identity confirmation steps, for example, by interfacing with one or more external systems (e.g., one or more third-party data aggregation systems). For example, the system, when validating a data subject's identity, may begin by verifying that a person with the data subject's name, address, social security number, or other identifying characteristic (e.g., which may have been provided by the data subject as part of the data subject access request) actually exists. In various embodiments, the system is configured to interface with (e.g., transmit a search request to) one or more credit reporting agencies (e.g., Experian, Equifax, TransUnion, etc.) to confirm that a person with one or more characteristics provided by the data subject exists. The system may, for example, interface with such credit reporting agencies via a suitable plugin (e.g., software plugin). Additionally, there might be a verification on behalf of a trusted third-party system (e.g., the controller).
In still other embodiments, the system may be configured to utilize one or more other third-party systems (e.g., such as LexisNexis, IDology, RSA, etc.), which may, for example, compile utility and phone bill data, property deeds, rental agreement data, and other public records for various individuals. The system may be configured to interface with one or more such third-party systems to confirm that a person with one or more characteristics provided by the data subject exists.
After the step of confirming the existence of a person with the one or more characteristics provided by the data subject, the system may be configured to confirm that the person making the data subject access request is, in fact, the data subject. The system may, for example, verify that the requestor is the data subject by prompting the requestor to answer one or more knowledge-based authentication questions (e.g., out-of-wallet questions). In particular embodiments, the system is configured to utilize one or more third-party services as a source of such questions (e.g., any of the suitable third-party sources discussed immediately above). The system may use third-party data from the one or more third-party sources to generate one or more questions. These one or more questions may include questions that a data subject should know an answer to without knowing the question ahead of time (e.g., one or more previous addresses, a parent or spouse name and/or maiden name, etc.).
In still other embodiments, the system may be configured to prompt a requestor to provide one or more additional pieces of information in order to validate the requestor's identity. This information may include, for example: (1) at least a portion of the requestor's social security number (e.g., last four digits); (2) a name and/or place of birth of the requestor's father; (3) a name, maiden name, and/or place of birth of the requestor's mother; and/or (4) any other information which may be useful for confirming the requestor's identity (e.g., such as information available on the requestor's birth certificate). In other embodiments, the system may be configured to prompt the requestor to provide authorization for the company to check the requestor's social security or other private records (e.g., credit check authorization, etc.) to obtain information that the system may use to confirm the requestor's identity. In other embodiments, the system may prompt the user to provide one or more images (e.g., using a suitable mobile computing device) of an identifying document (e.g., a birth certificate, social security card, driver's license, etc.).
The system may, in response to a user providing one or more responses that matches information that the system receives from one or more third-party data aggregators or through any other suitable background, credit, or other search, substantially automatically authenticate the requestor as the data subject. The system may then continue processing the data subject's request, and ultimately fulfill their request.
In particular embodiments, such as embodiments in which the requestor includes a business (e.g., as in a business to business data subject access request), the system may be configured to authenticate the requesting business using one or more company verification techniques. These one or more company validation techniques may include, for example, validating a vendor contract (e.g., between the requesting business and the company receiving the data subject access request); receiving a matching token, code, or other unique identifier provided by the company receiving the data subject access request to the requesting business; receiving a matching file in possession of both the requesting business and the company receiving the data subject access request; receiving a signed contract, certificate (e.g., digital or physical), or other document memorializing an association between the requesting business and the company receiving the data subject access request; and/or any other suitable method of validating that a particular request is actually made on behalf of the requesting business (e.g., by requesting the requesting business to provide one or more pieces of information, one or more files, one or more documents, etc. that may only be accessible to the requesting business).
In other embodiments, the system may be configured to authenticate a request via integration with a company's employee or customer (e.g., consumer) authentication process. For example, in response to receiving a data subject access request that indicates that the data subject is an employee of the company receiving the data subject access request, the system may be configured to prompt the employee to login to the company's employee authentication system (e.g., Okta, Azure, AD, etc.) In this way, the system may be configured to authenticate the requestor based at least in part on the requestor successfully logging into the authentication system using the data subject's credentials. Similarly, in response to receiving a data subject access request that indicates that the data subject is a customer of the company receiving the data subject access request, the system may be configured to prompt the customer to login to an account associated with the company (e.g., via a consumer portal authentication process). In a particular example, this may include, for example, an Apple ID (for data subject access requests received by Apple). In this way, the system may be configured to authenticate the requestor based at least in part on the requestor successfully logging into the authentication system using the data subject's credentials. In some embodiments, the system may be configured to require the requestor to login using two-factor authentication or other suitable existing employee or consumer authentication process.
Data Subject Request Fulfillment Constraints
A particular organization (e.g., entity) may not be required to respond to a data subject access request that originates from (e.g., is received from) a malicious requestor or source. A malicious requestor or source may include, for example: a requestor (e.g., an individual) or source that submits excessive or redundant data subject access requests; a requestor who is a disgruntled employee that was previously and not currently employed by the organization receiving the data subject access request that is submitting such requests to tie up the organization's resources unnecessarily; a group of requestors such as researchers, professors, students, NGOs, etc. that submit a plurality of requests for reasons other than those reasons provided by policy, law, etc.; a competitor of the organization receiving the data subject access request that is submitting such requests to tie up the organization's resources unnecessarily; a group of requestors originating from a particular geographic region (e.g., a country) that may submit excessive data subject access requests to disrupt the organization's operations or tie up the organization's resources unnecessarily for economic or other reasons; a group of requestors associated with a particular political organization that may submit excessive data subject access requests to expend the organization's resources for economic or retaliatory reasons; a group of requestors associated with a particular protesting organization (e.g., a group protesting the organization, the organization's employees, or the any entities affiliated with the organization for any reason) that may submit excessive data subject access requests to expend the organization's resources; a terrorist or other organization that may spam requests to disrupt the organization's operation and response to valid/legitimate requests; and/or any other request that may fall outside the scope of valid/legitimate requests made for reasons proscribed by public policy, company policy, or law.
In particular embodiments, the system is configured to maintain a “blacklist” of such malicious requestors and/or sources. As will be described in detail below, this virtual blacklist may include fulfillment constraint data that may be cross-referenced upon receipt of a data subject access request to determine if the data subject access request is subject to one or more response fulfillment (processing) constraints. If the data subject access request is subject to one or more response fulfillment constraints, then the system may take action on the request according to one or more limitations.
Looking now at
According to various embodiments, a Data Subject Access Request (DSAR) 102 is submitted by a requestor and received at a DSAR Processing and Fulfillment Server 170. The DSAR 102 may be submitted and authenticated in the manner described above. The DSAR Processing and Fulfillment Server 170 may utilize one or more databases 140 and/or one or more third party servers 160 (discussed in greater detail below with respect to the example system architecture and
After verifying the existence of any Fulfillment Constraint Data 106, the DSAR Processing and Fulfillment Server 170 may initially prevent the DSAR 102 from being processed. For instance, the DSAR Processing and Fulfillment Server 170 may prevent one or more data storage systems from executing processing operations or performing network communication for retrieving data responsive to the DSAR 102 from one or more data sources included in a private data network. In addition, the DSAR Processing and Fulfillment Server 170 may take action, either by a Fulfillment Action 180 or a Deny Action 190. The action taken by the DSAR Processing and Fulfillment Server 170 may be subject to One or More Limitations 192 (indicated in
Looking at the system 5000 now in greater detail, the DSAR 102 may be submitted using the exemplary data subject access request form shown and described above with respect to
According to various embodiments, the system is configured to track a requestor and/or a source associated with each DSAR 102 and analyze each DSAR 102 to identify requestors and/or sources from which: (1) the organization receives a large volume of requests; (2) the organization receives a large number of repeat requests; (3) the organization receives a request from a requestor or source for which the organization does not legally have to respond, or does not have to respond at no cost. The sources may include, for example: (1) one or more particular IP addresses; (2) one or more particular domains; (3) one or more particular countries; (4) one or more particular institutions; (5) one or more particular geographic regions; (6) one or more political group; and/or (7) one or more protesting group. In response to analyzing the requestors and/or sources of the requests, the system may identify one or more requestors or sources that may be malicious (e.g., are submitting excessive requests).
As an example, the system may be configured to fulfill data subject access requests for the purpose of providing a data subject with information regarding what data the organization collects and for what purpose. A typical DSAR 102 may be made so that the data subject can ensure that the organization is collecting data for lawful reasons. As such, the system may be configured to identify requestors and other sources of data requests that are made for other reasons (e.g., a malicious reason or one or more reasons that would not obligate the organization to respond to the request). These reasons may include, for example, malicious or other reasons. One example includes requests made for research by an academic institution by one or more students or professors. While not malicious in the traditional sense, these requests may be categorized as malicious by the system since they tie up a large amount of company resources and do not require a free response by law. Anticompetitive requests by one or more competitors may be maliciously submitted with the intention to expend organizational time and resources. Requests by disgruntled former employees may be submitted for nefarious reasons. Requests from a particular country or geographic region may have malicious interests in tying up the resources of the organization by submitting excessive or frivolous DSARs 102. Requests from a particular political group may be made with malicious interests in tying up the resources of the organization. Similarly, one or more protesting groups or organizations may have the purpose of submitting one or more DSARs 102 to expend time and resources of the organization and its employees. It should be appreciated that the disclosure herein encompasses any response fulfillment constraints based on the submission of any DSAR 102 that is not submitted for lawful, valid, and/or legitimate reasons.
In various embodiments, the system is configured to maintain a database of the identified one or more requestors and sources (e.g., in computer memory). In particular embodiments, the database may store a listing of identities, data sources, etc. that have been found (e.g., by the system) to result in one or more response fulfillment (processing) constraints that lead to a denial of the request or a fulfillment subject to one or more conditions and/or requirements. This listing is stored in One or More Databases 140 or resides on One or More Third Party Servers 160 (
The Third Party Repository Server 104 can act as a central data-storage repository (e.g., one or more servers, databases, etc.), for the centralized storage of personally identifiable information (PII) and/or Personal Data 108 for one or more particular data subjects. In particular embodiments, the Third Party Repository Server 104 may enable the system to populate one or more data models (e.g., using one or more suitable techniques described herein) substantially on-the-fly (e.g., as the system collects, processes, stores, etc. Personal Data 108 regarding a particular data subject). In this way, in particular embodiments the system is configured to maintain a substantially up-to-date data model for a plurality of data subjects (e.g., each particular data subject for whom the system collects, processes, stores, etc. Personal Data 108). The system may then be configured to substantially automatically respond to one or more data access requests by a data subject (e.g., individual, entity, organization, etc.), for example, using the substantially up-to-date data model.
A particular organization may undertake a plurality of different privacy campaigns, processing activities, etc. that involve the collection and storage of Personal Data 108. In some embodiments, each of the plurality of different processing activities may collect redundant data (e.g., may collect the same Personal Data 108 for a particular individual more than once), and may store data and/or redundant data in one or more particular locations (e.g., on one or more different servers, in one or more different databases, etc.). In this way, a particular organization may store Personal Data 108 in a plurality of different locations which may include one or more known and/or unknown locations. As such, complying with particular privacy and security policies related to Personal Data 108 (e.g., such as responding to one or more requests by data subjects related to their Personal Data 108) may be particularly difficult (e.g., in terms of cost, time, etc.). Accordingly, utilizing and maintaining a Third Party Repository Server 104 for PII may enable the system to more quickly and accurately respond to DSARs 102 and other requests related to collected, stored, and processed Personal Data 108.
In various embodiments, a Third Party Repository Server 104 is configured to facilitate the receipt and centralized storage of Personal Data 108 for each of a plurality of respective data subjects. In particular embodiments, the system may be configured to: (1) receive Personal Data 108 associated with a particular data subject (e.g., a copy of the data, a link to a location of where the data is stored, etc.); and (2) store the Personal Data 108 in a suitable data format (e.g., a data model, a reference table, etc.) for later retrieval.
In particular embodiments, the Third Party Repository Server 104 is configured to: (1) receive an indication that a first party system (e.g., entity) has collected and/or processed a piece of Personal Data 108 for a data subject; (2) determine a location in which the first party system has stored the piece of Personal Data 108; (3) optionally digitally store (e.g., in computer memory) a copy of the piece of Personal Data 108 and associate, in memory, the piece of Personal Data 108 with the data subject; and (4) optionally digitally store an indication of the storage location utilized by the first party system for the piece of Personal Data 108. In particular embodiments, the system is configured to provide a centralized database, for each particular data subject, of any Personal Data 108 processed and/or collected by a particular entity.
Referring again to
In particular embodiments, the system may, for example, maintain a database (e.g., in computer memory) of former employees that are no longer employed by the company. When comparing the identity of the requesting party with the Requestor 112 identities and corresponding information stored as Fulfillment Constraint Data 106 in the Third Party Repository Server 104, DSAR Processing and Fulfillment Server 170 may determine that being a former employee alone is not enough to subject the DSAR 102 to one or more response fulfillment constraints, specifically imposing one or more limitations such as a fulfillment of the request subject to an authorization code, a processing fee, and/or the like or the denial of the request absent such limitations. Rather, the DSAR Processing and Fulfillment Server 170 may impose one or more limitations only if a former employee is further flagged or identified with a malicious history of requests (e.g., excessive requests or requests exceeding a threshold number) or potential for malicious requests. With respect to determining that a requestor possesses a potential for malicious requests, this potential may be stored as a rating or value assigned to the Requestor 112 in the Fulfillment Constraint Data 106 based on historical actions or special circumstances with respect to the requestor's departure from the company. It should be appreciated that any criteria may be used to determine that the Requestor 112 is subject to one or more response fulfillment constraints within the limits of guiding laws and regulations.
According to other embodiments, an example of Fulfillment Constraint Data 106 related to the identities of one or more Requestors 112 includes a customer history associated with the data subjects. The customer history may include one or more spending characteristics of the one or more Requestors 112, as well as any complaint history of the one or more Requestors 112. For example, the spending characteristics or other applicable relationship that a Requestor 112 has with the company may be a factor in determining whether the company fulfills the DSAR 102 at no cost even though not legally obligated to do so, fulfills the DSAR 102 for a processing fee, fulfills the DSAR 102 based upon some other condition being met, or denies the DSAR 102. In one embodiment, if a second or subsequent DSAR 102 is received from a Requestor 112 within a threshold period of time (e.g., within a year of the first DSAR 102), then the company may determine that it is worth expending the necessary resources to fulfill the DSAR 102, even though not legally required to do so, because the Requestor 112 is a good customer or holds a particular standing or status recognized by the company. For example, in making this determination, the DSAR Processing and Fulfillment Server 170 may determine if the one or more spending characteristics of the Requestor 112 includes an amount spent over a reference time period that exceeds a spending threshold. If so, then the DSAR Processing and Fulfillment Server 170 may fulfill the DSAR 102 without requesting one or more processing fees.
Similar to a purchase history, a complaint history may comprise valuable Fulfillment Constraint Data 106 utilized by the system to determine how or if to respond to the DSAR 102. For example, it may be beneficial to fulfill a second or subsequent DSAR 102 from a Requestor 112 that has never submitted a complaint or bad review of the organization during a substantial period of time even though that subsequent DSAR 102 does not legally require a response. Conversely, it may be determined that the benefits of fulfilling a subsequent DSAR 102 from a person with an extensive complaint history outweigh the costs of denying or charging a fee for the request. It should be appreciated that any quantity and type of weighting and prioritization of Fulfillment Constraint Data 106 may be utilized in a decision to fulfill, fulfill with limitations, or deny a DSAR 102. Regardless of the precise manner in which the Fulfillment Constraint Data 106 is used by the DSAR Processing and Fulfillment Server 170 in determining the action to take on the DSAR 102, the data used in the determination may be digitally attached to the identity of the Requestor 112 and stored in the Third Party Repository Server 104 (or One or More Databases 140 or One or More Third Party Servers 160) as Fulfillment Constraint Data 106.
An example of Fulfillment Constraint Data 106 related to one or more Sources 114 of malicious DSAR 102 submissions includes a particular domain and/or a particular IP address. If a requestor submits an excessive quantity of DSARs 102 using the same computer, then the DSAR Processing and Fulfillment Server 170 may store the domain or IP address associated with those electronic submission as Fulfillment Constraint Data 106 to identify that domain or IP address as a Source 114 of malicious DSAR 102 submissions. In doing so, future DSARs 102 originating from the domain or IP address stored as Fulfillment Constraint Data 106 will be identified by the DSAR Processing and Fulfillment Server 170 as being malicious or potentially malicious. According to one embodiment, one or more particular domains or IP addresses associated with a competitor of the organization are stored as Fulfillment Constraint Data 106 to identify that competitor's domain or IP address as a Source 114 of malicious DSAR 102 submissions. A subsequent search by the DSAR Processing and Fulfillment Server 170 for Fulfillment Constraint Data 106 associated with a DSAR 102 will result in a determination that the DSAR 102 originated from a competitor, which flags the submission as being potentially malicious.
Another example of Fulfillment Constraint Data 106 related to one or more Sources 114 of malicious DSAR 102 submissions includes a geographic location or region from which the DSAR 102 is submitted. For example, if the DSAR 102 originates from a country or specific geographic region commonly affiliated with terrorist or other organizations that may spam requests to disrupt the organization's operation and response to valid requests, then that country or geographic region may be stored as Fulfillment Constraint Data 106 that flags DSARs 102 originating from that country or geographic region as being malicious or potentially malicious.
Similarly, Fulfillment Constraint Data 106 may include identifications of political groups or organizations, protesting groups or organizations that commonly protest or object to the operations of the organization, religious groups or organizations, or any other group or organization that may have views, beliefs, or causes that are contrary to those of the organization. Any DSARs 102 submitted by a Requestor 112 or a Source 114 that may be affiliated with these groups or organizations may be flagged as being malicious or potentially malicious.
Handling of DSARs that are flagged or otherwise identified as being malicious or potentially malicious may be guided by company policy, applicable laws, and/or regulations. According to various embodiments, if the DSAR 102 is subject to one or more response fulfillment constraints, as determined from the presence of applicable Fulfillment Constraint Data 106 associated with the request, then the DSAR Processing and Fulfillment Server 170 acts on the DSAR 102 according to One or More Limitations 192. The One or More Limitations 192 may include a Fulfillment Action 180 or a Deny Action 190. The Fulfillment Action 180 includes fulfilling the DSAR 102 conditioned upon some requirement being met, such as payment of a processing fee. The Deny Action 190 includes denying or rejecting the DSAR 102. Accordingly, performing such actions can assist in the identification and/or handling of malicious DSARs and thus, assist in eliminating and/or limiting the wasteful use of computing resources in processing the malicious DSARs.
In particular embodiments, if the DSAR Processing and Fulfillment Server 170 acts on the DSAR 102 according to One or More Limitations 192, then a Notification 194 is provided to the requestor. According to these embodiments, the Notification 194 may include a reason for the One or More Limitations 192, such as the presence of one or more response fulfillment constraints. The Notification 194 may further provide the requestor of their right to communicate with a supervisory authority regarding the One or More Limitations 192, and inform the requestor of their right to a judicial remedy without delay. The Notification 194 may include any information mandated by applicable law or regulations, or desired according to company policy.
In addition to providing the Notification 194 to the requestor upon acting on the DSAR 102 according to One or More Limitations 192, the DSAR Processing and Fulfillment Server 170 according to particular embodiments may store or identify Supporting Documents 118 in the Third Party Repository Server 104. Judicial or other review actions taken by a supervisory authority after the denial of a DSAR 102, or fulfillment requiring a condition and/or requirement to be met (e.g., payment of a processing fee), may require documentation that identifies the applicable Fulfillment Constraint Data 106 and supports the associated response fulfillment constraints. In this situation, the Third Party Repository Server 104 provides a central storage location for the Supporting Documents 118. It should be appreciated that the Supporting Documents 118 may include links or locations to the electronic or physical documentation stored in locations outside of the Third Party Repository Server 104 (e.g., One or More Databases 140 or One or More Third Party Servers 160).
If the DSAR Processing and Fulfillment Server 170 does not find applicable Fulfillment Constraint Data 106, then the routine 5100 proceeds from operation 5106 to operation 5108, where the DSAR Processing and Fulfillment Server 170 takes a Fulfillment Action 180 and processes or fulfills the DSAR 102 and the routine 5100 ends. However, if at operation 5106, the DSAR Processing and Fulfillment Server 170 finds applicable Fulfillment Constraint Data 106, then the routine 5100 proceeds from operation 5106 to operation 5110, where the DSAR Processing and Fulfillment Server 170 provides a Notification 194 to the Requestor 112 and ensures Supporting Documents 118 are properly stored or indexed to support the One or More Limitations 192 imposed on the DSAR 102. In addition, in particular embodiments, the DSAR Processing and Fulfillment Server 170 prevents the DSAR 102 from being processed. For instance, the DSAR Processing and Fulfillment Server 170 prevents one or more data storage systems from executing processing operations or performing network communication for retrieving data responsive to the DSAR 102 from one or more data sources included in a private data network. At operation 5112, the DSAR Processing and Fulfillment Server 170 takes the appropriate action according to the One or More Limitations 192 and the routine 5100 ends. As discussed above, the One or More Limitations 192 may result in the DSAR 102 being fulfilled after one or more conditions and/or requirements have been met (e.g., such as payment of a processing fee), or a Deny Action 190.
Accordingly, in particular embodiments, the DSAR Processing and Fulfillment Server 170 may use authorization data in evaluating whether the one or more conditions and/or requirements have been met. Here, an authorization interface may be provided to the requestor that requests the authorization data from the requestor. For example, the authorization interface may ask the requestor to enter a username, password, an authorization code, and/or the like. In another example, the authorization interface may require the requestor to enter credit card information to pay a processing fee. The credit card information may then be processed to charge for the processing fee for processing the DSAR 102 and the authorization data may entail data confirming the payment of the fee. Upon the one or more conditions and/or requirements being met, the DSAR Processing and Fulfillment Server 170 may then override the One or More Limitations 192 (e.g., one or more processing constraints) to permit retrieval of the data responsive to the DSAR 102 from the one or more data sources included in the private data network.
Turning now to
Returning now to
Data Subject Access Request Fulfillment Cost Determination
In various embodiments, as may be understood in light of this disclosure, fulfilling a data subject access request may be particularly costly. In some embodiments, a company may store data regarding a particular data subject in multiple different locations for a plurality of different reasons as part of a plurality of different processing and other business activities. For example, a particular data subject may be both a customer and an employee of a particular company or organization. Accordingly, in some embodiments, fulfilling a data subject access request for a particular data subject may involve a plurality of different information technology (IT) professionals in a plurality of different departments of a particular company or organization. As such, it may be useful to determine a cost of a particular data subject access request (e.g., particularly because, in some cases, a data subject is entitled to a response to their data subject access request as a matter of right at no charge).
In particular embodiments, in response to receiving a data subject access request, the system may be configured to: (1) assign the request to at least one privacy team member; (2) identify one or more IT teams required to fulfill the request (e.g., one or more IT teams associated with one or more business units that may store Personal Data 108 related to the request); (3) delegate one or more subtasks of the request to each of the one or more IT teams; (4) receive one or more time logs from each individual involved in the processing and fulfillment of the data subject access request; (5) calculate an effective rate of each individual's time (e.g., based at least in part on the individual's salary, bonus, benefits, chair cost, etc.); (6) calculate an effective cost of fulfilling the data subject access request based at least in part on the one or more time logs and effective rate of each of the individual's time; and (7) apply an adjustment to the calculated effective cost that accounts for one or more external factors (e.g., overhead, etc.) in order to calculate a cost of fulfilling the data subject access request.
In particular embodiments, the system is configured to substantially automatically track an amount of time spent by each individual involved in the processing and fulfillment of the data subject access request. The system may, for example, automatically track an amount of time between each individual opening and closing a ticket assigned to them as part of their role in processing or fulfilling the data subject access request. In other embodiments, the system may determine the time spent based on an amount of time provided by each respective individual (e.g., the individual may track their own time and submit it to the system).
In various embodiments, the system is configured to measure a cost of each particular data subject access request received, and analyze one or more trends in costs of, for example: (1) data subject access requests over time; (2) related data subject access requests; (3) etc. For example, the system may be configured to track and analyze cost and time-to-process trends for one or more social groups, one or more political groups, one or more class action groups, etc. In particular, the system may be configured to identify a particular group from which the system receives particularly costly data subject access request (e.g., former and/or current employees, members of a particular social group, members of a particular political group, etc.).
In particular embodiments, the system may be configured to utilize data subject access request cost data when processing, assigning, and/or fulfilling future data subject access requests (e.g., from a particular identified group, individual, etc.). For example, the system may be configured to prioritize requests that are expected to be less costly and time-consuming (e.g., based on past cost data) over requests identified as being likely more expensive. Alternatively, the system may prioritize more costly and time-consuming requests over less costly ones in the interest of ensuring that the system is able to respond to each request in a reasonable amount of time (e.g., within a time required by law, such as a thirty-day period, or any other suitable time period). Moreover, the cost data associated with processing, assigning, and/or fulfilling data subject access requests may be a factor utilized by the DSAR Processing and Fulfillment Server 170 in determining whether to deny a DSAR 102 or request a processing fee prior to fulfilling a DSAR 102 after determining that the DSAR 102 is subject to one or more response fulfillment constraints, as discussed above.
Customer Satisfaction Integration with Data Subject Access Requests
In various embodiments, the system may be configured to collect customer satisfaction data, for example: (1) as part of a data subject access request submission form; (2) when providing one or more results of a data subject access request to the data subject; or (3) at any other suitable time. In various embodiments, the customer satisfaction data may be collected in the form of a suitable survey, free-form response questionnaire, or other suitable satisfaction data collection format (e.g., thumbs up vs. thumbs down, etc.).
In particular embodiments, the question depicted in
In various embodiments, the system may be configured to measure data related to any other suitable customer satisfaction method (e.g., in addition to NPS). By integrating a customer satisfaction survey with the data subject access request process, the system may increase a number of consumers that provide one or more responses to the customer satisfaction survey. In particular embodiments, the system is configured to require the requestor to respond to the customer satisfaction survey prior to submitting the data subject access request.
Exemplary Technical Platforms
As will be appreciated by one skilled in the relevant field, the present invention may be, for example, embodied as a computer system, a method, or a computer program product. Accordingly, various embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, particular embodiments may take the form of a computer program product stored on a computer-readable storage medium having computer-readable instructions (e.g., software) embodied in the storage medium. Various embodiments may take the form of web-implemented computer software. Any suitable computer-readable storage medium may be utilized including, for example, hard disks, compact disks, DVDs, optical storage devices, and/or magnetic storage devices.
Various embodiments are described below with reference to block diagrams and flowchart illustrations of methods, apparatuses (e.g., systems), and computer program products. It should be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, respectively, can be implemented by a computer executing computer program instructions. These computer program instructions may be loaded onto a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions which execute on the computer or other programmable data processing apparatus to create means for implementing the functions specified in the flowchart block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner such that the instructions stored in the computer-readable memory produce an article of manufacture that is configured for implementing the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions that execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Accordingly, blocks of the block diagrams and flowchart illustrations support combinations of mechanisms for performing the specified functions, combinations of steps for performing the specified functions, and program instructions for performing the specified functions. It should also be understood that each block of the block diagrams and flowchart illustrations, and combinations of blocks in the block diagrams and flowchart illustrations, can be implemented by special purpose hardware-based computer systems that perform the specified functions or steps, or combinations of special purpose hardware and other hardware executing appropriate computer instructions.
Example System Architecture
As may be understood from
The one or more computer networks 115 may include any of a variety of types of wired or wireless computer networks such as the Internet, a private intranet, a public switch telephone network (PSTN), or any other type of network. The communication link between The Intelligent Identity Scanning Server 130 and the One or More Third Party Servers 160 may be, for example, implemented via a Local Area Network (LAN) or via the Internet. In other embodiments, the One or More Databases 140 may be stored either fully or partially on any suitable server or combination of servers described herein.
In particular embodiments, the computer 200 may be connected (e.g., networked) to other computers in a LAN, an intranet, an extranet, and/or the Internet. As noted above, the computer 200 may operate in the capacity of a server or a client computer in a client-server network environment, or as a peer computer in a peer-to-peer (or distributed) network environment. The computer 200 may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a server, a network router, a switch or bridge, or any other computer capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that computer. Further, while only a single computer is illustrated, the term “computer” shall also be taken to include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
An exemplary computer 200 includes a processing device 202, a main memory 204 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), static memory 206 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage device 218, which communicate with each other via a bus 232.
The processing device 202 represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like. More particularly, the processing device 202 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLIW) microprocessor, or processor implementing other instruction sets, or processors implementing a combination of instruction sets. The processing device 202 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. The processing device 202 may be configured to execute processing logic 226 for performing various operations and steps discussed herein.
The computer 200 may further include a network interface device 208. The computer 200 also may include a video display unit 210 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)), an alphanumeric input device 212 (e.g., a keyboard), a cursor control device 214 (e.g., a mouse), and a signal generation device 216 (e.g., a speaker).
The data storage device 218 may include a non-transitory computer-accessible storage medium 230 (also known as a non-transitory computer-readable storage medium or a non-transitory computer-readable medium) on which is stored one or more sets of instructions (e.g., software instructions 222) embodying any one or more of the methodologies or functions described herein. The software instructions 222 may also reside, completely or at least partially, within main memory 204 and/or within processing device 202 during execution thereof by computer 200—main memory 204 and processing device 202 also constituting computer-accessible storage media. The software instructions 222 may further be transmitted or received over a network 115 via network interface device 208.
While the computer-accessible storage medium 230 is shown in an exemplary embodiment to be a single medium, the term “computer-accessible storage medium” should be understood to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term “computer-accessible storage medium” should also be understood to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the computer and that cause the computer to perform any one or more of the methodologies of the present invention. The term “computer-accessible storage medium” should accordingly be understood to include, but not be limited to, solid-state memories, optical and magnetic media, etc.
Systems for Managing Data Subject Access Requests
In various embodiments, the system may include a ticket management system and/or other systems for managing data subject access requests. Various embodiments of such systems are described below.
Overview
Ticket management systems, according to various embodiments, are adapted to receive data subject access requests (DSAR's) from particular data subjects, and to facilitate the timely processing of valid DSAR's by an appropriate respondent. In particular embodiments, the ticket management system receives DSAR's via one or more webforms that each may be accessed via an appropriate link on a respective web page. In other embodiments, the system may receive DSAR's through any other suitable mechanism, such as via a computer software application (e.g., a messaging application such as Slack, Twitter), or through entry by a representative who may receive the information, for example, via suitable paper forms or over the phone.
The ticket management system may include a webform creation tool that is adapted to allow a user to create customized webforms for receiving DSAR's from various different data subject types and for routing the requests to appropriate individuals for processing. The webform creation tool may, for example, allow the user to specify the language that the form will be displayed in, what particular information is to be requested for the data subject and/or provided by the data subject, who any DSAR's that are received via the webform will be routed to, etc. In particular embodiments, after the user completes their design of the webform, the webform creation tool generates code for the webform that may be cut and then pasted into a particular web page.
The system may be further adapted to facilitate processing of DSAR's that are received via the webforms, or any other suitable mechanism. For example, the ticket management system may be adapted to execute one or more of the following steps for each particular DSAR received via the webforms (or other suitable mechanism) described above: (1) before processing the DSAR, confirm that the DSAR request was actually submitted by the particular data subject of the DSAR (or, for example, by an individual authorized to make the DSAR request on the data subject's behalf, such as a parent, guardian, power-of-attorney holder, etc.)—any suitable method may be used to confirm the identity of the entity/individual submitting the DSAR—for example, if the system receives the DSAR via a third-party computer system, the system may validate authentication via API secret, or by requiring a copy of one or more particular legal documents (e.g., a particular contract between two particular entities)—the system may validate the identity of an individual by, for example, requiring the individual (e.g., data subject) to provide particular account credentials, by requiring the individual to provide particular out-of-wallet information, through biometric scanning of the individual (e.g., finger or retinal scan), or via any other suitable identity verification technique; (2) if the DSAR was not submitted by the particular data subject, deny the request; (3) if the DSAR was submitted by the particular data subject, advance the processing of the DSAR; (4) route the DSAR to the correct individual(s) or groups internally for handling; (5) facilitate the assignment of the DSAR to one or more other individuals for handling of one or more portions of the DSAR; and/or (6) facilitate the suspension of the data subject access request. In particular embodiments, the system may perform any one or more of the above steps automatically. The system then generates a receipt for the DSAR request that the user can use for a transactional record of their submitted request.
In particular embodiments, the ticket management system may be adapted to generate a graphical user interface (e.g., a DSAR request-processing dashboard) that is adapted to allow a user (e.g., a privacy officer of an organization that is receiving the DSAR) to monitor the progress of any the DSAR requests. The GUI interface may display, for each DSAR, for example, an indication of how much time is left (e.g., quantified in days and/or hours) before a legal and/or internal deadline to fulfill the request. The system may also display, for each DSAR, a respective user-selectable indicium that, when selected, may facilitate one or more of the following: (1) verification of the request; (2) assignment of the request to another individual; (3) requesting an extension to fulfill the request; (4) rejection of the request; or (5) suspension of the request.
As noted immediately above, and elsewhere in this application, in particular embodiments, any one or more of the above steps may be executed by the system automatically. As a particular example, the system may be adapted to automatically verify the identity of the DSAR requestor and then automatically fulfill the DSAR request by, for example, obtaining the requested information via a suitable data model and communicating the information to the requestor. As another particular example, the system may be configured to automatically route the DSAR to the correct individual for handling based at least in part on one or more pieces of information provided (e.g., in the webform).
Operation of Example Implementation
In other embodiments, the system is configured to enable a user to specify, when configuring a new webform, what individual at a particular organization (e.g., company) will be responsible for responding to requests made via the webform. The system may, for example, enable the user to define a specific default sub-organization (e.g., within the organization) responsible for responding to DSAR's submitted via the new webform. As such, the system may be configured to automatically route a new DSAR made via the new webform to the appropriate sub-organization for processing and fulfillment. In various embodiments, the system is configured to route one or more various aspects of the DSAR to one or more different sub-organizations within the organization.
In still other embodiments, the system is configured to enable a user generating webforms to assign multiple webforms to multiple different suborganizations within an organization. For example, an organization called ACME, Inc. may have a website for each of a plurality of different brands (e.g., sub-organizations) under which ACME sells products (e.g., UNICORN Brand T-shirts, GRIPP Brand Jeans, etc.). As may be understood in light of this disclosure, each website for each of the particular brands may include an associated webform for submitting DSAR's. Each respective webform may be configured to route a DSAR made via its associated brand website to a particular sub-organization within ACME for handling DSAR's related to the brand.
As noted above, after the user uses the webform construction tool to design a particular webform for use on a particular web page, the webform construction tool generates code (e.g., HTML code) that may be pasted into the particular web page to run the designed webform page.
As shown in
In various embodiments, the system includes a dashboard that may be used by various individuals within an organization (e.g., one or more privacy officers of an organization) to manage multiple DSAR requests. As discussed above, the dashboard may display DSAR's submitted, respectively, to a single organization, any of multiple different sub-organizations (divisions, departments, subsidiaries etc.) of a particular organization, and/or any of multiple independent organizations. For example, the dashboard may display DSAR's that were submitted from a parent organization and from the parent organization's U.S. and European subsidiaries. This may be advantageous, for example, because it may allow an organization to manage all DSAR requests of all of its sub-organizations centrally.
As shown in
In other embodiments, the input field may enable the respondent to provide one or more supporting reasons for a decision, by the respondent, to authenticate the request. The respondent may also upload one or more supporting documents (such as an attachment). The supporting documents or information may include, for example, one or more documents utilized in confirming the requestor's identity, etc.
In response to the respondent selecting the Submit button, the system changes the status of the request to “In Progress” and also changes the color of the request's status from orange to blue (or to any other suitable color)—see
As shown in
As shown in
As shown in
In particular embodiments, the system may include logic for automatically determining whether a requested extension complies with one or more applicable laws or internal policies and, in response, either automatically grant or reject the requested extension. For example, if the maximum allowable time for replying to a particular request is 90 days under the controlling laws and the respondent requests an extension that would result in the fulfillment of the request 91 or more days from the date that the request was submitted, the system may automatically reject the extension request. In various embodiments, the system may also communicate to the respondent (e.g., via a suitable electronic message or text display on a system user interface) an explanation as to why the extension request was denied, and/or a maximum amount of time (e.g., a maximum number of days) that the deadline may be extended under the applicable laws or policies. In various embodiments, if the system determines that the requested extension is permissible under the applicable laws and/or policies, the system may automatically grant the extension. In other embodiments, the system may be configured to automatically modify a length of the requested extension to conform with one or more applicable laws and/or policies.
As shown in
As shown in
As shown in
Additional Concepts
Automated Data Subject Verification
In various embodiments, before a data subject request can be processed, the data subject's identity needs to be verified. In various embodiments, the system provides a mechanism to automatically detect the type of authentication required for a particular data subject based on the type of Data Subject Access Request being made and automatically issues a request to the data subject to verify their identity against that form of identification. For example, a subject rights request might only require two types of authentication, but a deletion request may require four types of data to verify authentication. The system may automatically detect which is type of authentication is required based on the DSAR and send an appropriate request to the data subject to verify their identity.
Intelligent Prioritization of DSAR's
In various embodiments, the system may be adapted to prioritize the processing of DSAR's based on metadata about the data subject of the DSAR. For example, the system may be adapted for: (1) in response to receiving a DSAR, obtaining metadata regarding the data subject; (2) using the metadata to determine whether a priority of the DSAR should be adjusted based on the obtained metadata; and (3) in response to determining that the priority of the DSAR should be adjusted based on the obtained metadata, adjusting the priority of the DSAR.
Examples of metadata that may be used to determine whether to adjust the priority of a particular DSAR include: (1) the type of request, (2) the location from which the request is being made, (3) current sensitivities to world events, (4) a status of the requestor (e.g., especially loyal customer), or (5) any other suitable metadata.
In various embodiments, in response to the system determining that the priority of a particular DSAR should be elevated, the system may automatically adjust the deadline for responding to the DSAR. For example, the system may update the deadline in the system's memory and/or modify the “Days Left to Respond” field (See
In various embodiments, in response to the system determining that the priority of a particular DSAR should be lowered, the system may automatically adjust the deadline for responding to the DSAR by adding to the number of days left to respond to the request.
Automatic Deletion of Data Subject Records Based on Detected Systems
In particular embodiments, in response a data subject submitting a request to delete their Personal Data 108 from an organization's systems, the system may: (1) automatically determine where the data subject's Personal Data 108 is stored; and (2) in response to determining the location of the data (which may be on multiple computing systems), automatically facilitate the deletion of the data subject's Personal Data 108 from the various systems (e.g., by automatically assigning a plurality of tasks to delete data across multiple business systems to effectively delete the data subject's Personal Data 108 from the systems). In particular embodiments, the step of facilitating the deletion may comprise, for example: (1) overwriting the data in memory; (2) marking the data for overwrite; (2) marking the data as free (e.g., and deleting a directory entry associated with the data); and/or (3) any other suitable technique for deleting the Personal Data 108. In particular embodiments, as part of this process, the system uses an appropriate data model (see discussion above) to efficiently determine where all of the data subject's Personal Data 108 is stored.
Automatic Determination of Business Processes that Increase Chance of Deletion Requests
In various embodiments, the system is adapted to store, in memory, a log of DSAR actions. The system may also store, in memory, additional information regarding the data subjects of each of the requests. The system may use this information, for example, to determine which business processes are most commonly associated with a data subject submitting a request to have their personal information deleted from the organization's systems. The organization may then use this information to revise the identified business processes in an effort to reduce the number of deletion requests issued by data subjects associated with the business processes.
As a particular example, the system may analyze stored information to determine that a high number (e.g., 15%) of all participants in a company's loyalty program submit requests to have their personal information deleted from the company's systems. In response to making this determination, the system may issue an electronic alert to an appropriate individual (e.g., a privacy officer of the company), informing them of the high rate of members of the company's loyalty program issuing Personal Data 108 delete requests. This alert may prompt the individual to research the issue and try to resolve it.
CONCLUSIONAlthough embodiments above are described in reference to various privacy compliance monitoring systems, it should be understood that various aspects of the system described above may be applicable to other privacy-related systems, or to other types of systems, in general.
While this specification contains many specific embodiment details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments may also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment may also be implemented in multiple embodiments separately or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.
Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product or packaged into multiple software products.
Many modifications and other embodiments of the invention will come to mind to one skilled in the art to which this invention pertains having the benefit of the teachings presented in the foregoing descriptions and the associated drawings. Therefore, it is to be understood that the invention is not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for the purposes of limitation.
Claims
1. A method comprising:
- providing, by computing hardware, a query interface that is accessible via a public data network and that is configured for querying a plurality of data storage systems included in a private data network;
- determining, by the computing hardware, that a plurality of queries comprising data subject access requests have been received via the query interface from an Internet Protocol (IP) address;
- responsive to determining that the plurality of queries have originated from the IP address, adding a processing constraint for the IP address to fulfillment constraint data in a data repository;
- receiving, via the query interface and the public data network, a query comprising a data subject access request from a computing device;
- determining, by the computing hardware, that the computing device is associated with the IP address;
- querying, by the computing hardware and using the IP address, the fulfillment constraint data from the data repository to identify the processing constraint;
- determining, by the computing hardware, that the data subject access request is subject to the processing constraint; and
- preventing, based on the determining that the data subject access request is subject to the processing constraint, the plurality of data storage systems from executing processing operations or performing network communication for retrieving data responsive to the data subject access request from a plurality of data sources included in the private data network.
2. The method of claim 1 further comprising:
- providing, by the computing hardware, an authorization interface that is accessible via the public data network and that is configured for requesting authorization data from the computing device;
- receiving, by the computing hardware and via the authorization interface, the authorization data from the computing device; and
- overriding, by the computing hardware, the processing constraint based on receiving the authorization data, wherein overriding the processing constraint permits retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network.
3. The method of claim 2, wherein the authorization data comprises at least one of a username, a password, an authorization code, or data confirming payment of a processing fee associated with fulfilling the data subject access request.
4. The method of claim 1, wherein adding the processing constraint for the IP address to the fulfillment constraint data in the data repository is based on a number of the plurality of queries originating from the IP address satisfying a threshold quantity within a threshold period of time.
5. The method of claim 1, wherein adding the processing constraint for the IP address to the fulfillment constraint data is based on the IP address being associated with at least one of a competitor of an entity associated with the plurality of data storage systems, a geographic region, a particular political group, or a particular protesting group.
6. The method of claim 1 further comprising storing, by the computing hardware, documentation supporting preventing retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network.
7. The method of claim 1 further comprising providing, by the computing hardware, for display on the query interface, a reason for preventing retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network.
8. A system comprising:
- a non-transitory computer-readable medium storing instructions; and
- a processing device communicatively coupled to the non-transitory computer-readable medium,
- wherein, the processing device is configured to execute the instructions and thereby perform operations comprising:
- determining that a plurality of queries comprising data subject access requests have been received via a query interface from a domain, wherein the query interface is accessible via a public data network and is configured for querying a plurality of data storage systems included in a private data network;
- responsive to determining that the plurality of queries have originated from the domain, adding a processing constraint for the domain to fulfillment constraint data in a data repository;
- receiving, via the query interface and the public data network, a query comprising a data subject access request from a computing device;
- determining that the computing device is associated with the domain;
- querying, using the domain, the fulfillment constraint data from the data repository to identify the processing constraint;
- determining that the data subject access request is subject to the processing constraint; and
- preventing, based on the determining that the data subject access request is subject to the processing constraint, the plurality of data storage systems from executing processing operations or performing network communication for retrieving data responsive to the data subject access request from a plurality of data sources included in the private data network.
9. The system of claim 8, wherein the operations further comprise:
- providing an authorization interface that is accessible via the public data network and that is configured for requesting authorization data from the computing device;
- receiving, via the authorization interface, the authorization data from the computing device; and
- overriding the processing constraint based on receiving the authorization data, wherein overriding the processing constraint permits retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network.
10. The system of claim 9, wherein the authorization data comprises at least one of a username, a password, an authorization code, or data confirming payment of a processing fee associated with fulfilling the data subject access request.
11. The system of claim 8, wherein adding the processing constraint for the domain to the fulfillment constraint data in the data repository is based on a number of the plurality of queries originating from the domain satisfying a threshold quantity within a threshold period of time.
12. The system of claim 8, wherein adding the processing constraint for the domain to the fulfillment constraint data is based on the domain being associated with at least one of a competitor of an entity associated with the plurality of data storage systems, a geographic region, a particular political group, or a particular protesting group.
13. The system of claim 8, wherein the operations further comprise storing documentation supporting preventing retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network.
14. The system of claim 8, wherein the operations further comprise providing, for display on the query interface, a reason for preventing retrieval of the data responsive to the data subject access request from the plurality of data sources included in the private data network.
15. A non-transitory computer-readable medium having program code that is stored thereon, the program code executable by one or more processing devices for performing operations comprising:
- determining that a first query comprising a first data subject request has been received via a query interface from at least one of an Internet Protocol (IP) address, a domain, or a geographic location wherein the query interface is accessible via a public data network and is configured for querying a data storage system included in a private data network;
- responsive to determining the first query has originated from the at least one of the IP address, the domain, or the geographic location, adding a processing constraint for at least one of the IP address, the domain, or the geographic location to fulfillment constraint data in a data repository;
- receiving, via the query interface and the public data network, a second query comprising a second data subject access request from a computing device;
- determining that the computing device is associated with the at least one of the IP address, the domain, or the geographic location;
- querying, using at least one of the IP address, the domain, or the geographic location, the fulfillment constraint data from the data repository to identify the processing constraint;
- determining that the second query is subject to the processing constraint; and
- preventing, based on the determining that the second query is subject to the processing constraint, the data storage system from executing processing operations or performing network communication for retrieving data responsive to the second query from a data source included in the private data network.
16. The non-transitory computer-readable medium of claim 15, wherein the operations further comprise:
- providing an authorization interface that is accessible via the public data network and that is configured for requesting authorization data from the computing device;
- receiving, via the authorization interface, the authorization data from the computing device; and
- overriding the processing constraint based on receiving the authorization data, wherein overriding the processing constraint permits retrieval of the data responsive to the second query from the data source included in the private data network.
17. The non-transitory computer-readable medium of claim 16, wherein the authorization data comprises at least one of a username, a password, an authorization code, or data confirming payment of a processing fee associated with fulfilling the data subject access request.
18. The non-transitory computer-readable medium of claim 15, wherein adding the processing constraint for at least one of the IP address, the domain, or the geographic location to the fulfillment constraint data is based on at least one of the IP address or the domain being associated with at least one of a competitor of an entity associated with the data storage system, a geographic region, a particular political group, or a particular protesting group.
19. The non-transitory computer-readable medium of claim 15, wherein the operations further comprise storing documentation supporting preventing retrieval of the data responsive to the second query from the data source included in the private data network.
20. The non-transitory computer-readable medium of claim 15, wherein the operations further comprise providing a reason for display on the query interface for preventing retrieval of the data responsive to the second query from the data source included in the private data network.
4536866 | August 20, 1985 | Jerome et al. |
4574350 | March 4, 1986 | Starr |
5193162 | March 9, 1993 | Bordsen et al. |
5276735 | January 4, 1994 | Boebert et al. |
5329447 | July 12, 1994 | Leedom, Jr. |
5404299 | April 4, 1995 | Tsurubayashi et al. |
5535393 | July 9, 1996 | Reeve et al. |
5560005 | September 24, 1996 | Hoover et al. |
5668986 | September 16, 1997 | Nilsen et al. |
5710917 | January 20, 1998 | Musa et al. |
5761529 | June 2, 1998 | Raji |
5764906 | June 9, 1998 | Edelstein et al. |
5872973 | February 16, 1999 | Mitchell et al. |
5913041 | June 15, 1999 | Ramanathan et al. |
5913214 | June 15, 1999 | Madnick et al. |
6016394 | January 18, 2000 | Walker |
6122627 | September 19, 2000 | Carey et al. |
6148297 | November 14, 2000 | Swor et al. |
6148342 | November 14, 2000 | Ho |
6240416 | May 29, 2001 | Immon et al. |
6240422 | May 29, 2001 | Atkins et al. |
6243816 | June 5, 2001 | Fang et al. |
6253203 | June 26, 2001 | Oflaherty et al. |
6263335 | July 17, 2001 | Paik et al. |
6272631 | August 7, 2001 | Thomlinson et al. |
6275824 | August 14, 2001 | Oflaherty et al. |
6282548 | August 28, 2001 | Burner et al. |
6330562 | December 11, 2001 | Boden et al. |
6363488 | March 26, 2002 | Ginter et al. |
6374237 | April 16, 2002 | Reese |
6374252 | April 16, 2002 | Althoff et al. |
6408336 | June 18, 2002 | Schneider et al. |
6427230 | July 30, 2002 | Goiffon et al. |
6442688 | August 27, 2002 | Moses et al. |
6446120 | September 3, 2002 | Dantressangle |
6463488 | October 8, 2002 | San Juan |
6484149 | November 19, 2002 | Jammes et al. |
6484180 | November 19, 2002 | Lyons et al. |
6516314 | February 4, 2003 | Birkler et al. |
6516337 | February 4, 2003 | Tripp et al. |
6519571 | February 11, 2003 | Guheen et al. |
6574631 | June 3, 2003 | Subramanian et al. |
6591272 | July 8, 2003 | Williams |
6601233 | July 29, 2003 | Underwood |
6606744 | August 12, 2003 | Mikurak |
6611812 | August 26, 2003 | Hurtado et al. |
6625602 | September 23, 2003 | Meredith et al. |
6629081 | September 30, 2003 | Cornelius et al. |
6633878 | October 14, 2003 | Underwood |
6662192 | December 9, 2003 | Rebane |
6662357 | December 9, 2003 | Bowman-Amuah |
6697824 | February 24, 2004 | Bowman-Amuah |
6699042 | March 2, 2004 | Smith et al. |
6701314 | March 2, 2004 | Conover et al. |
6721713 | April 13, 2004 | Guheen et al. |
6725200 | April 20, 2004 | Rost |
6732109 | May 4, 2004 | Lindberg et al. |
6754665 | June 22, 2004 | Futagami et al. |
6755344 | June 29, 2004 | Mollett et al. |
6757685 | June 29, 2004 | Raffaele et al. |
6757888 | June 29, 2004 | Knutson et al. |
6816944 | November 9, 2004 | Peng |
6826693 | November 30, 2004 | Koshida et al. |
6850252 | February 1, 2005 | Hoffberg |
6886101 | April 26, 2005 | Glazer et al. |
6901346 | May 31, 2005 | Tracy et al. |
6904417 | June 7, 2005 | Clayton et al. |
6909897 | June 21, 2005 | Kikuchi |
6925443 | August 2, 2005 | Baggei, Jr. et al. |
6938041 | August 30, 2005 | Brandow et al. |
6956845 | October 18, 2005 | Baker et al. |
6978270 | December 20, 2005 | Carty et al. |
6980927 | December 27, 2005 | Tracy et al. |
6980987 | December 27, 2005 | Kaminer |
6983221 | January 3, 2006 | Tracy et al. |
6985887 | January 10, 2006 | Sunstein et al. |
6990454 | January 24, 2006 | McIntosh |
6993448 | January 31, 2006 | Tracy et al. |
6993495 | January 31, 2006 | Smith, Jr. et al. |
6996807 | February 7, 2006 | Vardi et al. |
7003560 | February 21, 2006 | Mullen et al. |
7003662 | February 21, 2006 | Genty et al. |
7013290 | March 14, 2006 | Ananian |
7017105 | March 21, 2006 | Flanagin et al. |
7023979 | April 4, 2006 | Wu et al. |
7039594 | May 2, 2006 | Gersting |
7039654 | May 2, 2006 | Eder |
7047517 | May 16, 2006 | Brown et al. |
7051036 | May 23, 2006 | Rosnow et al. |
7051038 | May 23, 2006 | Yeh et al. |
7058970 | June 6, 2006 | Shaw |
7069427 | June 27, 2006 | Adler et al. |
7076558 | July 11, 2006 | Dunn |
7093200 | August 15, 2006 | Schreiber et al. |
7095854 | August 22, 2006 | Ginter et al. |
7100195 | August 29, 2006 | Underwood |
7120800 | October 10, 2006 | Ginter et al. |
7124101 | October 17, 2006 | Mikurak |
7124107 | October 17, 2006 | Pishevar et al. |
7127705 | October 24, 2006 | Christfort et al. |
7127741 | October 24, 2006 | Bandini et al. |
7133845 | November 7, 2006 | Ginter et al. |
7139999 | November 21, 2006 | Bowman-Amuah |
7143091 | November 28, 2006 | Charnock et al. |
7149698 | December 12, 2006 | Guheen et al. |
7165041 | January 16, 2007 | Guheen et al. |
7167842 | January 23, 2007 | Josephson, II et al. |
7167844 | January 23, 2007 | Leong et al. |
7171379 | January 30, 2007 | Menninger et al. |
7181438 | February 20, 2007 | Szabo |
7203929 | April 10, 2007 | Vinodkrishnan et al. |
7213233 | May 1, 2007 | Vinodkrishnan et al. |
7216340 | May 8, 2007 | Vinodkrishnan et al. |
7219066 | May 15, 2007 | Parks et al. |
7223234 | May 29, 2007 | Stupp et al. |
7225460 | May 29, 2007 | Barzilai et al. |
7234065 | June 19, 2007 | Breslin |
7247625 | July 24, 2007 | Zhang et al. |
7251624 | July 31, 2007 | Lee et al. |
7260830 | August 21, 2007 | Sugimoto |
7266566 | September 4, 2007 | Kennaley et al. |
7272818 | September 18, 2007 | Ishimitsu et al. |
7275063 | September 25, 2007 | Horn |
7281020 | October 9, 2007 | Fine |
7284232 | October 16, 2007 | Bates et al. |
7284271 | October 16, 2007 | Lucovsky et al. |
7287280 | October 23, 2007 | Young |
7290275 | October 30, 2007 | Baudoin et al. |
7293119 | November 6, 2007 | Beale |
7299299 | November 20, 2007 | Hollenbeck et al. |
7302569 | November 27, 2007 | Betz et al. |
7313575 | December 25, 2007 | Carr et al. |
7313699 | December 25, 2007 | Koga |
7313825 | December 25, 2007 | Redlich et al. |
7315826 | January 1, 2008 | Guheen et al. |
7315849 | January 1, 2008 | Bakalash et al. |
7322047 | January 22, 2008 | Redlich et al. |
7330850 | February 12, 2008 | Seibel et al. |
7340447 | March 4, 2008 | Ghatare |
7340776 | March 4, 2008 | Zobel et al. |
7343434 | March 11, 2008 | Kapoor et al. |
7346518 | March 18, 2008 | Frank et al. |
7353204 | April 1, 2008 | Liu |
7356559 | April 8, 2008 | Jacobs et al. |
7367014 | April 29, 2008 | Griffin |
7370025 | May 6, 2008 | Pandit |
7376835 | May 20, 2008 | Olkin et al. |
7380120 | May 27, 2008 | Garcia |
7382903 | June 3, 2008 | Ray |
7383570 | June 3, 2008 | Pinkas et al. |
7391854 | June 24, 2008 | Salonen et al. |
7398393 | July 8, 2008 | Mont et al. |
7401235 | July 15, 2008 | Mowers et al. |
7403942 | July 22, 2008 | Bayliss |
7409354 | August 5, 2008 | Putnam et al. |
7412402 | August 12, 2008 | Cooper |
7424680 | September 9, 2008 | Carpenter |
7428546 | September 23, 2008 | Nori et al. |
7430585 | September 30, 2008 | Sibert |
7454457 | November 18, 2008 | Lowery et al. |
7454508 | November 18, 2008 | Mathew et al. |
7478157 | January 13, 2009 | Bohrer et al. |
7480755 | January 20, 2009 | Herrell et al. |
7487170 | February 3, 2009 | Stevens |
7493282 | February 17, 2009 | Manly et al. |
7512987 | March 31, 2009 | Williams |
7516882 | April 14, 2009 | Cucinotta |
7523053 | April 21, 2009 | Pudhukottai et al. |
7529836 | May 5, 2009 | Bolen |
7548968 | June 16, 2009 | Bura et al. |
7552480 | June 23, 2009 | Voss |
7562339 | July 14, 2009 | Racca et al. |
7565685 | July 21, 2009 | Ross et al. |
7567541 | July 28, 2009 | Karimi et al. |
7584505 | September 1, 2009 | Mondri et al. |
7584508 | September 1, 2009 | Kashchenko et al. |
7587749 | September 8, 2009 | Leser et al. |
7590705 | September 15, 2009 | Mathew et al. |
7590972 | September 15, 2009 | Axelrod et al. |
7603356 | October 13, 2009 | Schran et al. |
7606783 | October 20, 2009 | Carter |
7606790 | October 20, 2009 | Levy |
7607120 | October 20, 2009 | Sanyal et al. |
7613700 | November 3, 2009 | Lobo et al. |
7617136 | November 10, 2009 | Lessing et al. |
7617167 | November 10, 2009 | Griffis et al. |
7620644 | November 17, 2009 | Cote et al. |
7627666 | December 1, 2009 | Degiulio et al. |
7630874 | December 8, 2009 | Fables et al. |
7630998 | December 8, 2009 | Zhou et al. |
7636742 | December 22, 2009 | Olavarrieta et al. |
7640322 | December 29, 2009 | Wendkos et al. |
7650497 | January 19, 2010 | Thornton et al. |
7653592 | January 26, 2010 | Flaxman et al. |
7657476 | February 2, 2010 | Barney |
7657694 | February 2, 2010 | Mansell et al. |
7665073 | February 16, 2010 | Meijer et al. |
7665125 | February 16, 2010 | Heard et al. |
7668947 | February 23, 2010 | Hutchinson et al. |
7673282 | March 2, 2010 | Amaru et al. |
7676034 | March 9, 2010 | Wu et al. |
7681034 | March 16, 2010 | Lee et al. |
7681140 | March 16, 2010 | Ebert |
7685561 | March 23, 2010 | Deem et al. |
7685577 | March 23, 2010 | Pace et al. |
7693593 | April 6, 2010 | Ishibashi et al. |
7698398 | April 13, 2010 | Lai |
7702639 | April 20, 2010 | Stanley et al. |
7707224 | April 27, 2010 | Chastagnol et al. |
7712029 | May 4, 2010 | Ferreira et al. |
7716242 | May 11, 2010 | Pae et al. |
7725474 | May 25, 2010 | Tamai et al. |
7725875 | May 25, 2010 | Waldrep |
7729940 | June 1, 2010 | Harvey et al. |
7730142 | June 1, 2010 | Levasseur et al. |
7752124 | July 6, 2010 | Green et al. |
7756826 | July 13, 2010 | Bots et al. |
7756987 | July 13, 2010 | Wang et al. |
7761586 | July 20, 2010 | Olenick et al. |
7774745 | August 10, 2010 | Fildebrandt et al. |
7788212 | August 31, 2010 | Beckmann et al. |
7788222 | August 31, 2010 | Shah et al. |
7788632 | August 31, 2010 | Kuester et al. |
7788726 | August 31, 2010 | Teixeira |
7801758 | September 21, 2010 | Gracie et al. |
7801826 | September 21, 2010 | Labrou et al. |
7801912 | September 21, 2010 | Ransil et al. |
7802305 | September 21, 2010 | Leeds |
7805349 | September 28, 2010 | Yu et al. |
7805451 | September 28, 2010 | Hosokawa |
7813947 | October 12, 2010 | Deangelis et al. |
7822620 | October 26, 2010 | Dixon et al. |
7827523 | November 2, 2010 | Ahmed et al. |
7836078 | November 16, 2010 | Dettinger et al. |
7844640 | November 30, 2010 | Bender et al. |
7849143 | December 7, 2010 | Vuong |
7853468 | December 14, 2010 | Callahan et al. |
7853470 | December 14, 2010 | Sonnleithner et al. |
7853925 | December 14, 2010 | Kemmler |
7860816 | December 28, 2010 | Fokoue-Nkoutche et al. |
7870540 | January 11, 2011 | Zare et al. |
7870608 | January 11, 2011 | Shraim et al. |
7873541 | January 18, 2011 | Klar et al. |
7877327 | January 25, 2011 | Gwiazda et al. |
7877812 | January 25, 2011 | Koved et al. |
7885841 | February 8, 2011 | King |
7890461 | February 15, 2011 | Oeda et al. |
7895260 | February 22, 2011 | Archer et al. |
7904478 | March 8, 2011 | Yu et al. |
7904487 | March 8, 2011 | Ghatare |
7917888 | March 29, 2011 | Chong et al. |
7917963 | March 29, 2011 | Goyal et al. |
7921152 | April 5, 2011 | Ashley et al. |
7930197 | April 19, 2011 | Ozzie et al. |
7930753 | April 19, 2011 | Mellinger et al. |
7953725 | May 31, 2011 | Burris et al. |
7954150 | May 31, 2011 | Croft et al. |
7958087 | June 7, 2011 | Blumenau |
7958494 | June 7, 2011 | Chaar et al. |
7962900 | June 14, 2011 | Barraclough et al. |
7966310 | June 21, 2011 | Sullivan et al. |
7966599 | June 21, 2011 | Malasky et al. |
7966663 | June 21, 2011 | Strickland et al. |
7974992 | July 5, 2011 | Fastabend et al. |
7975000 | July 5, 2011 | Dixon et al. |
7991559 | August 2, 2011 | Dzekunov et al. |
7991747 | August 2, 2011 | Upadhyay et al. |
7996372 | August 9, 2011 | Rubel, Jr. |
8005891 | August 23, 2011 | Knowles et al. |
8010612 | August 30, 2011 | Costea et al. |
8010720 | August 30, 2011 | Iwaoka et al. |
8019881 | September 13, 2011 | Sandhu et al. |
8020206 | September 13, 2011 | Hubbard et al. |
8024384 | September 20, 2011 | Prabhakar et al. |
8032721 | October 4, 2011 | Murai |
8036374 | October 11, 2011 | Noble, Jr. |
8037409 | October 11, 2011 | Jacob et al. |
8041749 | October 18, 2011 | Beck |
8041913 | October 18, 2011 | Wang |
8069161 | November 29, 2011 | Bugir et al. |
8069471 | November 29, 2011 | Boren |
8082539 | December 20, 2011 | Schelkogonov |
8090754 | January 3, 2012 | Schmidt et al. |
8095923 | January 10, 2012 | Harvey et al. |
8099709 | January 17, 2012 | Baikov et al. |
8099765 | January 17, 2012 | Parkinson |
8103962 | January 24, 2012 | Embley et al. |
8117441 | February 14, 2012 | Kurien et al. |
8135815 | March 13, 2012 | Mayer |
8146054 | March 27, 2012 | Baker et al. |
8146074 | March 27, 2012 | Ito et al. |
8150717 | April 3, 2012 | Whitmore |
8156105 | April 10, 2012 | Altounian et al. |
8156158 | April 10, 2012 | Rolls et al. |
8156159 | April 10, 2012 | Ebrahimi et al. |
8166406 | April 24, 2012 | Goldfeder et al. |
8176061 | May 8, 2012 | Swanbeck et al. |
8176177 | May 8, 2012 | Sussman et al. |
8176334 | May 8, 2012 | Vainstein |
8176470 | May 8, 2012 | Klumpp et al. |
8180759 | May 15, 2012 | Hamzy |
8181151 | May 15, 2012 | Sedukhin et al. |
8185409 | May 22, 2012 | Putnam et al. |
8196176 | June 5, 2012 | Berteau et al. |
8205093 | June 19, 2012 | Argott |
8205140 | June 19, 2012 | Hafeez et al. |
8214362 | July 3, 2012 | Djabarov |
8214803 | July 3, 2012 | Horii et al. |
8234377 | July 31, 2012 | Cohn |
8239244 | August 7, 2012 | Ginsberg et al. |
8250051 | August 21, 2012 | Bugir et al. |
8255468 | August 28, 2012 | Vitaldevara et al. |
8260262 | September 4, 2012 | Ben Ayed |
8261362 | September 4, 2012 | Goodwin et al. |
8266231 | September 11, 2012 | Golovin et al. |
8275632 | September 25, 2012 | Awaraji et al. |
8275793 | September 25, 2012 | Ahmad et al. |
8286239 | October 9, 2012 | Sutton |
8312549 | November 13, 2012 | Goldberg et al. |
8316237 | November 20, 2012 | Felsher et al. |
8332908 | December 11, 2012 | Hatakeyama et al. |
8340999 | December 25, 2012 | Kumaran et al. |
8341405 | December 25, 2012 | Meijer et al. |
8346929 | January 1, 2013 | Lai |
8364713 | January 29, 2013 | Pollard |
8370224 | February 5, 2013 | Grewal |
8370794 | February 5, 2013 | Moosmann et al. |
8380630 | February 19, 2013 | Felsher |
8380743 | February 19, 2013 | Converting et al. |
8381180 | February 19, 2013 | Rostoker |
8381297 | February 19, 2013 | Touboul |
8386314 | February 26, 2013 | Kirkby et al. |
8392982 | March 5, 2013 | Harris et al. |
8418226 | April 9, 2013 | Gardner |
8423954 | April 16, 2013 | Ronen et al. |
8429179 | April 23, 2013 | Mirhaji |
8429597 | April 23, 2013 | Prigge |
8429630 | April 23, 2013 | Nickolov et al. |
8429758 | April 23, 2013 | Chen et al. |
8438644 | May 7, 2013 | Watters et al. |
8463247 | June 11, 2013 | Misiag |
8464311 | June 11, 2013 | Ashley et al. |
8468244 | June 18, 2013 | Redlich et al. |
8473324 | June 25, 2013 | Alvarez et al. |
8474012 | June 25, 2013 | Ahmed et al. |
8494894 | July 23, 2013 | Jaster et al. |
8504481 | August 6, 2013 | Motahari et al. |
8510199 | August 13, 2013 | Erlanger |
8515988 | August 20, 2013 | Jones et al. |
8516076 | August 20, 2013 | Thomas |
8527337 | September 3, 2013 | Lim et al. |
8533746 | September 10, 2013 | Nolan et al. |
8533844 | September 10, 2013 | Mahaffey et al. |
8538817 | September 17, 2013 | Wilson |
8539359 | September 17, 2013 | Rapaport et al. |
8539437 | September 17, 2013 | Finlayson et al. |
8560645 | October 15, 2013 | Linden et al. |
8560841 | October 15, 2013 | Chin et al. |
8560956 | October 15, 2013 | Curtis et al. |
8561100 | October 15, 2013 | Hu et al. |
8561153 | October 15, 2013 | Grason et al. |
8565729 | October 22, 2013 | Moseler et al. |
8566726 | October 22, 2013 | Dixon et al. |
8566938 | October 22, 2013 | Prakash et al. |
8571909 | October 29, 2013 | Miller et al. |
8572717 | October 29, 2013 | Narayanaswamy |
8578036 | November 5, 2013 | Holfelder et al. |
8578166 | November 5, 2013 | De Monseignat et al. |
8578481 | November 5, 2013 | Rowley |
8578501 | November 5, 2013 | Ogilvie |
8583694 | November 12, 2013 | Siegel et al. |
8583766 | November 12, 2013 | Dixon et al. |
8589183 | November 19, 2013 | Awaraji et al. |
8601467 | December 3, 2013 | Hofhansl et al. |
8601591 | December 3, 2013 | Krishnamurthy et al. |
8606746 | December 10, 2013 | Yeap et al. |
8612420 | December 17, 2013 | Sun et al. |
8612993 | December 17, 2013 | Grant et al. |
8615549 | December 24, 2013 | Knowles et al. |
8615731 | December 24, 2013 | Doshi |
8620952 | December 31, 2013 | Bennett et al. |
8621637 | December 31, 2013 | Al-Harbi et al. |
8626671 | January 7, 2014 | Federgreen |
8627114 | January 7, 2014 | Resch et al. |
8630961 | January 14, 2014 | Beilby et al. |
8631048 | January 14, 2014 | Davis et al. |
8640110 | January 28, 2014 | Kopp et al. |
8646072 | February 4, 2014 | Savant |
8650399 | February 11, 2014 | Le Bihan et al. |
8655939 | February 18, 2014 | Redlich et al. |
8656265 | February 18, 2014 | Paulin et al. |
8656456 | February 18, 2014 | Maxson et al. |
8661036 | February 25, 2014 | Turski et al. |
8667074 | March 4, 2014 | Farkas |
8667487 | March 4, 2014 | Boodman et al. |
8677472 | March 18, 2014 | Dotan et al. |
8681984 | March 25, 2014 | Lee et al. |
8682698 | March 25, 2014 | Cashman et al. |
8683502 | March 25, 2014 | Shkedi et al. |
8688601 | April 1, 2014 | Jaiswal |
8689292 | April 1, 2014 | Williams et al. |
8693689 | April 8, 2014 | Belenkiy et al. |
8700524 | April 15, 2014 | Williams et al. |
8700699 | April 15, 2014 | Shen et al. |
8706742 | April 22, 2014 | Ravid et al. |
8707451 | April 22, 2014 | Ture et al. |
8712813 | April 29, 2014 | King |
8713098 | April 29, 2014 | Adya et al. |
8713638 | April 29, 2014 | Hu et al. |
8719366 | May 6, 2014 | Mathew et al. |
8732839 | May 20, 2014 | Hohl |
8744894 | June 3, 2014 | Christiansen et al. |
8751285 | June 10, 2014 | Deb et al. |
8762406 | June 24, 2014 | Ho et al. |
8762413 | June 24, 2014 | Graham, Jr. et al. |
8763071 | June 24, 2014 | Sinha et al. |
8763082 | June 24, 2014 | Huber et al. |
8763131 | June 24, 2014 | Archer et al. |
8767947 | July 1, 2014 | Ristock et al. |
8769242 | July 1, 2014 | Tkac et al. |
8769412 | July 1, 2014 | Gill et al. |
8769671 | July 1, 2014 | Shraim et al. |
8776241 | July 8, 2014 | Zaitsev |
8788935 | July 22, 2014 | Hirsch et al. |
8793614 | July 29, 2014 | Wilson et al. |
8793650 | July 29, 2014 | Hilerio et al. |
8793781 | July 29, 2014 | Grossi et al. |
8793809 | July 29, 2014 | Falkenburg et al. |
8799984 | August 5, 2014 | Ahn |
8805707 | August 12, 2014 | Schumann, Jr. et al. |
8805806 | August 12, 2014 | Amarendran et al. |
8805925 | August 12, 2014 | Price et al. |
8812342 | August 19, 2014 | Barcelo et al. |
8812752 | August 19, 2014 | Shih et al. |
8812766 | August 19, 2014 | Kranendonk et al. |
8813028 | August 19, 2014 | Farooqi |
8813214 | August 19, 2014 | McNair et al. |
8819253 | August 26, 2014 | Simeloff et al. |
8819617 | August 26, 2014 | Koenig et al. |
8819800 | August 26, 2014 | Gao et al. |
8826446 | September 2, 2014 | Liu |
8832649 | September 9, 2014 | Bishop et al. |
8832854 | September 9, 2014 | Staddon et al. |
8839232 | September 16, 2014 | Taylor et al. |
8843487 | September 23, 2014 | McGraw et al. |
8843745 | September 23, 2014 | Roberts, Jr. |
8849757 | September 30, 2014 | Kruglick |
8856534 | October 7, 2014 | Khosravi et al. |
8856936 | October 7, 2014 | Datta Ray et al. |
8862507 | October 14, 2014 | Sandhu et al. |
8863261 | October 14, 2014 | Yang |
8875232 | October 28, 2014 | Blom et al. |
8893078 | November 18, 2014 | Schaude et al. |
8893286 | November 18, 2014 | Oliver |
8893297 | November 18, 2014 | Eversoll et al. |
8904494 | December 2, 2014 | Kindler et al. |
8914263 | December 16, 2014 | Shimada et al. |
8914299 | December 16, 2014 | Pesci-Anderson et al. |
8914342 | December 16, 2014 | Kalaboukis et al. |
8914902 | December 16, 2014 | Moritz et al. |
8918306 | December 23, 2014 | Cashman et al. |
8918392 | December 23, 2014 | Brooker et al. |
8918632 | December 23, 2014 | Sartor |
8930896 | January 6, 2015 | Wiggins |
8930897 | January 6, 2015 | Nassar |
8935198 | January 13, 2015 | Phillips et al. |
8935266 | January 13, 2015 | Wu |
8935342 | January 13, 2015 | Patel |
8935804 | January 13, 2015 | Clark et al. |
8938221 | January 20, 2015 | Brazier et al. |
8943076 | January 27, 2015 | Stewart et al. |
8943548 | January 27, 2015 | Drokov et al. |
8949137 | February 3, 2015 | Crapo et al. |
8955038 | February 10, 2015 | Nicodemus et al. |
8959568 | February 17, 2015 | Hudis et al. |
8959584 | February 17, 2015 | Piliouras |
8966575 | February 24, 2015 | McQuay et al. |
8966597 | February 24, 2015 | Saylor et al. |
8973108 | March 3, 2015 | Roth et al. |
8977234 | March 10, 2015 | Chava |
8977643 | March 10, 2015 | Schindlauer et al. |
8978158 | March 10, 2015 | Rajkumar et al. |
8983972 | March 17, 2015 | Kriebel et al. |
8984031 | March 17, 2015 | Todd |
8990933 | March 24, 2015 | Magdalin |
8996417 | March 31, 2015 | Channakeshava |
8996480 | March 31, 2015 | Agarwala et al. |
8997213 | March 31, 2015 | Papakipos et al. |
9003295 | April 7, 2015 | Baschy |
9003552 | April 7, 2015 | Goodwin et al. |
9009851 | April 14, 2015 | Droste et al. |
9014661 | April 21, 2015 | Decharms |
9015796 | April 21, 2015 | Fujioka |
9021469 | April 28, 2015 | Hilerio et al. |
9026526 | May 5, 2015 | Bau et al. |
9030987 | May 12, 2015 | Bianchetti et al. |
9032067 | May 12, 2015 | Prasad et al. |
9043217 | May 26, 2015 | Cashman et al. |
9043480 | May 26, 2015 | Barton et al. |
9047463 | June 2, 2015 | Porras |
9047582 | June 2, 2015 | Hutchinson et al. |
9047583 | June 2, 2015 | Patton et al. |
9047639 | June 2, 2015 | Ouintiliani et al. |
9049244 | June 2, 2015 | Prince et al. |
9049314 | June 2, 2015 | Pugh et al. |
9055071 | June 9, 2015 | Gates et al. |
9058590 | June 16, 2015 | Criddle et al. |
9064033 | June 23, 2015 | Jin et al. |
9069940 | June 30, 2015 | Hars |
9076231 | July 7, 2015 | Hill et al. |
9077736 | July 7, 2015 | Werth et al. |
9081952 | July 14, 2015 | Sagi et al. |
9087090 | July 21, 2015 | Cormier et al. |
9092478 | July 28, 2015 | Vaitheeswaran et al. |
9092796 | July 28, 2015 | Eversoll et al. |
9094434 | July 28, 2015 | Williams et al. |
9098515 | August 4, 2015 | Richter et al. |
9100778 | August 4, 2015 | Stogaitis et al. |
9106691 | August 11, 2015 | Burger et al. |
9106710 | August 11, 2015 | Feimster |
9110918 | August 18, 2015 | Rajaa et al. |
9111105 | August 18, 2015 | Barton et al. |
9111295 | August 18, 2015 | Tietzen et al. |
9123339 | September 1, 2015 | Shaw et al. |
9129311 | September 8, 2015 | Schoen et al. |
9135261 | September 15, 2015 | Maunder et al. |
9135444 | September 15, 2015 | Carter et al. |
9141823 | September 22, 2015 | Dawson |
9141911 | September 22, 2015 | Zhao et al. |
9152818 | October 6, 2015 | Hathaway et al. |
9152820 | October 6, 2015 | Pauley, Jr. et al. |
9154514 | October 6, 2015 | Prakash |
9154556 | October 6, 2015 | Dotan et al. |
9158655 | October 13, 2015 | Wadhwani et al. |
9165036 | October 20, 2015 | Mehra |
9170996 | October 27, 2015 | Lovric et al. |
9172706 | October 27, 2015 | Krishnamurthy et al. |
9177293 | November 3, 2015 | Gagnon et al. |
9178901 | November 3, 2015 | Xue et al. |
9183100 | November 10, 2015 | Gventer et al. |
9189642 | November 17, 2015 | Perlman |
9201572 | December 1, 2015 | Lyon et al. |
9201770 | December 1, 2015 | Duerk |
9202026 | December 1, 2015 | Reeves |
9202085 | December 1, 2015 | Mawdsley et al. |
9215076 | December 15, 2015 | Roth et al. |
9215252 | December 15, 2015 | Smith et al. |
9218596 | December 22, 2015 | Ronca et al. |
9224009 | December 29, 2015 | Liu et al. |
9230036 | January 5, 2016 | Davis |
9231935 | January 5, 2016 | Bridge et al. |
9232040 | January 5, 2016 | Barash et al. |
9235476 | January 12, 2016 | McHugh et al. |
9240987 | January 19, 2016 | Barrett-Bowen et al. |
9241259 | January 19, 2016 | Daniela et al. |
9245126 | January 26, 2016 | Christodorescu et al. |
9245266 | January 26, 2016 | Hardt |
9253609 | February 2, 2016 | Hosier, Jr. |
9264443 | February 16, 2016 | Weisman |
9274858 | March 1, 2016 | Milliron et al. |
9280581 | March 8, 2016 | Grimes et al. |
9286149 | March 15, 2016 | Sampson et al. |
9286282 | March 15, 2016 | Ling, III et al. |
9288118 | March 15, 2016 | Pattan |
9288556 | March 15, 2016 | Kim et al. |
9294498 | March 22, 2016 | Yampolskiy et al. |
9299050 | March 29, 2016 | Stiffler et al. |
9306939 | April 5, 2016 | Chan et al. |
9317697 | April 19, 2016 | Maier et al. |
9317715 | April 19, 2016 | Schuette et al. |
9325731 | April 26, 2016 | Mcgeehan |
9336184 | May 10, 2016 | Mital et al. |
9336220 | May 10, 2016 | Li et al. |
9336324 | May 10, 2016 | Lomme et al. |
9336332 | May 10, 2016 | Davis et al. |
9336400 | May 10, 2016 | Milman et al. |
9338188 | May 10, 2016 | Ahn |
9342706 | May 17, 2016 | Chawla et al. |
9344297 | May 17, 2016 | Shah et al. |
9344424 | May 17, 2016 | Tenenboym et al. |
9344484 | May 17, 2016 | Ferris |
9348802 | May 24, 2016 | Massand |
9348862 | May 24, 2016 | Kawecki, III |
9348929 | May 24, 2016 | Eberlein |
9349016 | May 24, 2016 | Brisebois et al. |
9350718 | May 24, 2016 | Sondhi et al. |
9355157 | May 31, 2016 | Mohammed et al. |
9356961 | May 31, 2016 | Todd et al. |
9361446 | June 7, 2016 | Demirjian et al. |
9369488 | June 14, 2016 | Woods et al. |
9374693 | June 21, 2016 | Olincy et al. |
9384199 | July 5, 2016 | Thereska et al. |
9384357 | July 5, 2016 | Patil |
9386078 | July 5, 2016 | Reno et al. |
9386104 | July 5, 2016 | Adams et al. |
9395959 | July 19, 2016 | Hatfield et al. |
9396332 | July 19, 2016 | Abrams et al. |
9401900 | July 26, 2016 | Levasseur et al. |
9411967 | August 9, 2016 | Parecki et al. |
9411982 | August 9, 2016 | Dippenaar et al. |
9417859 | August 16, 2016 | Gounares et al. |
9418221 | August 16, 2016 | Turgeman |
9424021 | August 23, 2016 | Zamir |
9424414 | August 23, 2016 | Demirjian et al. |
9426177 | August 23, 2016 | Wang et al. |
9450940 | September 20, 2016 | Belov et al. |
9460136 | October 4, 2016 | Todd et al. |
9460171 | October 4, 2016 | Marrelli et al. |
9460307 | October 4, 2016 | Breslau et al. |
9461876 | October 4, 2016 | Van Dusen et al. |
9462009 | October 4, 2016 | Kolman et al. |
9465702 | October 11, 2016 | Gventer et al. |
9465800 | October 11, 2016 | Lacey |
9473446 | October 18, 2016 | Vijay et al. |
9473505 | October 18, 2016 | Asano et al. |
9473535 | October 18, 2016 | Sartor |
9477523 | October 25, 2016 | Warman et al. |
9477660 | October 25, 2016 | Scott et al. |
9477685 | October 25, 2016 | Leung et al. |
9477942 | October 25, 2016 | Adachi et al. |
9483659 | November 1, 2016 | Bao et al. |
9489366 | November 8, 2016 | Scott et al. |
9495547 | November 15, 2016 | Schepis et al. |
9501523 | November 22, 2016 | Hyatt et al. |
9507960 | November 29, 2016 | Bell et al. |
9509674 | November 29, 2016 | Nasserbakht et al. |
9509702 | November 29, 2016 | Grigg et al. |
9514231 | December 6, 2016 | Eden |
9516012 | December 6, 2016 | Chochois et al. |
9521166 | December 13, 2016 | Wilson |
9524500 | December 20, 2016 | Dave et al. |
9529989 | December 27, 2016 | Kling et al. |
9536108 | January 3, 2017 | Powell et al. |
9537546 | January 3, 2017 | Cordeiro et al. |
9542568 | January 10, 2017 | Francis et al. |
9549047 | January 17, 2017 | Fredinburg et al. |
9552395 | January 24, 2017 | Bayer et al. |
9552470 | January 24, 2017 | Turgeman et al. |
9553918 | January 24, 2017 | Manion et al. |
9558497 | January 31, 2017 | Carvalho |
9569752 | February 14, 2017 | Deering et al. |
9571509 | February 14, 2017 | Satish et al. |
9571526 | February 14, 2017 | Sartor |
9571559 | February 14, 2017 | Raleigh et al. |
9571991 | February 14, 2017 | Brizendine et al. |
9576289 | February 21, 2017 | Henderson et al. |
9578060 | February 21, 2017 | Brisebois et al. |
9578173 | February 21, 2017 | Sanghavi et al. |
9582681 | February 28, 2017 | Mishra |
9584964 | February 28, 2017 | Pelkey |
9589110 | March 7, 2017 | Carey et al. |
9600181 | March 21, 2017 | Patel et al. |
9602529 | March 21, 2017 | Jones et al. |
9606971 | March 28, 2017 | Seolas et al. |
9607041 | March 28, 2017 | Himmelstein |
9619652 | April 11, 2017 | Slater |
9619661 | April 11, 2017 | Finkelstein |
9621357 | April 11, 2017 | Williams et al. |
9621566 | April 11, 2017 | Gupta et al. |
9626124 | April 18, 2017 | Lipinski |
9626680 | April 18, 2017 | Ryan et al. |
9629064 | April 18, 2017 | Graves et al. |
9642008 | May 2, 2017 | Wyatt et al. |
9646095 | May 9, 2017 | Gottlieb et al. |
9647949 | May 9, 2017 | Varki et al. |
9648036 | May 9, 2017 | Seiver et al. |
9652314 | May 16, 2017 | Mahiddini |
9654506 | May 16, 2017 | Barrett |
9654541 | May 16, 2017 | Kapczynski et al. |
9665722 | May 30, 2017 | Nagasundaram et al. |
9665733 | May 30, 2017 | Sills et al. |
9665883 | May 30, 2017 | Roullier et al. |
9672053 | June 6, 2017 | Tang et al. |
9672355 | June 6, 2017 | Titonis et al. |
9678794 | June 13, 2017 | Barrett et al. |
9691090 | June 27, 2017 | Barday |
9699209 | July 4, 2017 | Ng et al. |
9703549 | July 11, 2017 | Dufresne |
9704103 | July 11, 2017 | Suskind et al. |
9705840 | July 11, 2017 | Pujare et al. |
9705880 | July 11, 2017 | Siris |
9721078 | August 1, 2017 | Cornick et al. |
9721108 | August 1, 2017 | Krishnamurthy et al. |
9727751 | August 8, 2017 | Oliver et al. |
9729583 | August 8, 2017 | Barday |
9734148 | August 15, 2017 | Bendersky et al. |
9734255 | August 15, 2017 | Jiang |
9736004 | August 15, 2017 | Jung et al. |
9740985 | August 22, 2017 | Byron et al. |
9740987 | August 22, 2017 | Dolan |
9749408 | August 29, 2017 | Subramani et al. |
9753796 | September 5, 2017 | Mahaffey et al. |
9754091 | September 5, 2017 | Kode et al. |
9756059 | September 5, 2017 | Demirjian et al. |
9760620 | September 12, 2017 | Nachnani et al. |
9760635 | September 12, 2017 | Bliss et al. |
9760697 | September 12, 2017 | Walker |
9760849 | September 12, 2017 | Vinnakota et al. |
9762553 | September 12, 2017 | Ford et al. |
9767202 | September 19, 2017 | Darby et al. |
9767309 | September 19, 2017 | Patel et al. |
9769124 | September 19, 2017 | Yan |
9773269 | September 26, 2017 | Lazarus |
9785795 | October 10, 2017 | Grondin et al. |
9787671 | October 10, 2017 | Bogrett |
9798749 | October 24, 2017 | Saner |
9798826 | October 24, 2017 | Wilson et al. |
9798896 | October 24, 2017 | Jakobsson |
9800605 | October 24, 2017 | Baikalov et al. |
9800606 | October 24, 2017 | Yumer |
9804649 | October 31, 2017 | Cohen et al. |
9804928 | October 31, 2017 | Davis et al. |
9805381 | October 31, 2017 | Frank et al. |
9811532 | November 7, 2017 | Parkison et al. |
9817850 | November 14, 2017 | Dubbels et al. |
9817978 | November 14, 2017 | Marsh et al. |
9819684 | November 14, 2017 | Cernoch et al. |
9825928 | November 21, 2017 | Lelcuk et al. |
9830563 | November 28, 2017 | Paknad |
9832633 | November 28, 2017 | Gerber, Jr. et al. |
9836598 | December 5, 2017 | Iyer et al. |
9838407 | December 5, 2017 | Oprea et al. |
9838839 | December 5, 2017 | Vudali et al. |
9841969 | December 12, 2017 | Seibert, Jr. et al. |
9842042 | December 12, 2017 | Chhatwal et al. |
9842349 | December 12, 2017 | Sawczuk et al. |
9848005 | December 19, 2017 | Ardeli et al. |
9848061 | December 19, 2017 | Jain et al. |
9852150 | December 26, 2017 | Sharpe et al. |
9853959 | December 26, 2017 | Kapczynski et al. |
9860226 | January 2, 2018 | Thormaehlen |
9864735 | January 9, 2018 | Lamprecht |
9876825 | January 23, 2018 | Amar et al. |
9877138 | January 23, 2018 | Franklin |
9880157 | January 30, 2018 | Levak et al. |
9882935 | January 30, 2018 | Barday |
9887965 | February 6, 2018 | Kay et al. |
9888377 | February 6, 2018 | McCorkendale et al. |
9892441 | February 13, 2018 | Barday |
9892442 | February 13, 2018 | Barday |
9892443 | February 13, 2018 | Barday |
9892444 | February 13, 2018 | Barday |
9894076 | February 13, 2018 | Li et al. |
9898613 | February 20, 2018 | Swerdlow et al. |
9898739 | February 20, 2018 | Monastyrsky et al. |
9898769 | February 20, 2018 | Barday |
9912625 | March 6, 2018 | Muth et al. |
9912677 | March 6, 2018 | Chien |
9912810 | March 6, 2018 | Segre et al. |
9916703 | March 13, 2018 | Levinson et al. |
9922124 | March 20, 2018 | Rathod |
9923927 | March 20, 2018 | McClintock et al. |
9928379 | March 27, 2018 | Hoffer |
9934406 | April 3, 2018 | Khan et al. |
9934493 | April 3, 2018 | Castinado et al. |
9934544 | April 3, 2018 | Whitfield et al. |
9936127 | April 3, 2018 | Todasco |
9942214 | April 10, 2018 | Burciu et al. |
9942244 | April 10, 2018 | Lahoz et al. |
9942276 | April 10, 2018 | Sartor |
9946897 | April 17, 2018 | Lovin |
9948652 | April 17, 2018 | Yu et al. |
9948663 | April 17, 2018 | Wang et al. |
9953189 | April 24, 2018 | Cook et al. |
9954879 | April 24, 2018 | Sadaghiani et al. |
9954883 | April 24, 2018 | Ahuja et al. |
9959551 | May 1, 2018 | Schermerhorn et al. |
9959582 | May 1, 2018 | Sukman et al. |
9961070 | May 1, 2018 | Tang |
9973518 | May 15, 2018 | Lee et al. |
9973585 | May 15, 2018 | Ruback et al. |
9977904 | May 22, 2018 | Khan et al. |
9977920 | May 22, 2018 | Danielson et al. |
9983936 | May 29, 2018 | Dornemann et al. |
9984252 | May 29, 2018 | Pollard |
9990499 | June 5, 2018 | Chan et al. |
9992213 | June 5, 2018 | Sinnema |
10001975 | June 19, 2018 | Bharthulwar |
10002064 | June 19, 2018 | Muske |
10007895 | June 26, 2018 | Vanasco |
10013577 | July 3, 2018 | Beaumont et al. |
10015164 | July 3, 2018 | Hamburg et al. |
10019339 | July 10, 2018 | Von Hanxleden et al. |
10019588 | July 10, 2018 | Garcia et al. |
10019591 | July 10, 2018 | Beguin |
10019741 | July 10, 2018 | Hesselink |
10021143 | July 10, 2018 | Cabrera et al. |
10025804 | July 17, 2018 | Vranyes et al. |
10028226 | July 17, 2018 | Ayyagari et al. |
10032172 | July 24, 2018 | Barday |
10044761 | August 7, 2018 | Ducatel et al. |
10055426 | August 21, 2018 | Arasan et al. |
10055869 | August 21, 2018 | Borrelli et al. |
10061847 | August 28, 2018 | Mohammed et al. |
10069858 | September 4, 2018 | Robinson et al. |
10069914 | September 4, 2018 | Smith |
10073924 | September 11, 2018 | Karp et al. |
10075437 | September 11, 2018 | Costigan et al. |
10075451 | September 11, 2018 | Hall et al. |
10084817 | September 25, 2018 | Saher et al. |
10091214 | October 2, 2018 | Godlewski et al. |
10091312 | October 2, 2018 | Khanwalkar et al. |
10097551 | October 9, 2018 | Chan et al. |
10102533 | October 16, 2018 | Barday |
10108409 | October 23, 2018 | Pirzadeh et al. |
10122663 | November 6, 2018 | Hu et al. |
10122760 | November 6, 2018 | Terrill et al. |
10127403 | November 13, 2018 | Kong et al. |
10129211 | November 13, 2018 | Heath |
10140666 | November 27, 2018 | Wang et al. |
10142113 | November 27, 2018 | Zaidi et al. |
10152560 | December 11, 2018 | Potiagalov et al. |
10158676 | December 18, 2018 | Barday |
10165011 | December 25, 2018 | Barday |
10169762 | January 1, 2019 | Ogawa |
10176503 | January 8, 2019 | Barday et al. |
10181043 | January 15, 2019 | Pauley, Jr. et al. |
10181051 | January 15, 2019 | Barday et al. |
10187363 | January 22, 2019 | Smirnoff et al. |
10187394 | January 22, 2019 | Bar et al. |
10204154 | February 12, 2019 | Barday et al. |
10205994 | February 12, 2019 | Splaine et al. |
10212134 | February 19, 2019 | Rai |
10212175 | February 19, 2019 | Seul et al. |
10223533 | March 5, 2019 | Dawson |
10230571 | March 12, 2019 | Rangasamy et al. |
10230711 | March 12, 2019 | Kohli |
10250594 | April 2, 2019 | Chathoth et al. |
10255602 | April 9, 2019 | Wang |
10257127 | April 9, 2019 | Dotan-Cohen et al. |
10257181 | April 9, 2019 | Sherif et al. |
10268838 | April 23, 2019 | Yadgiri et al. |
10275221 | April 30, 2019 | Thattai et al. |
10275614 | April 30, 2019 | Barday et al. |
10282370 | May 7, 2019 | Barday et al. |
10282559 | May 7, 2019 | Barday et al. |
10284604 | May 7, 2019 | Barday et al. |
10289584 | May 14, 2019 | Chiba |
10289857 | May 14, 2019 | Brinskelle |
10289866 | May 14, 2019 | Barday et al. |
10289867 | May 14, 2019 | Barday et al. |
10289870 | May 14, 2019 | Barday et al. |
10296504 | May 21, 2019 | Hock et al. |
10304442 | May 28, 2019 | Rudden et al. |
10310723 | June 4, 2019 | Rathod |
10311042 | June 4, 2019 | Kumar |
10311475 | June 4, 2019 | Yuasa |
10311492 | June 4, 2019 | Gelfenbeyn et al. |
10318761 | June 11, 2019 | Barday et al. |
10320940 | June 11, 2019 | Brennan et al. |
10324960 | June 18, 2019 | Skvortsov et al. |
10326768 | June 18, 2019 | Verweyst et al. |
10326798 | June 18, 2019 | Lambert |
10326841 | June 18, 2019 | Bradley et al. |
10327100 | June 18, 2019 | Davis et al. |
10331689 | June 25, 2019 | Sorrentino et al. |
10331904 | June 25, 2019 | Sher-Jan et al. |
10333975 | June 25, 2019 | Soman et al. |
10339470 | July 2, 2019 | Dutta et al. |
10346186 | July 9, 2019 | Kalyanpur |
10346635 | July 9, 2019 | Kumar et al. |
10346637 | July 9, 2019 | Barday et al. |
10346638 | July 9, 2019 | Barday et al. |
10346849 | July 9, 2019 | Ionescu et al. |
10348726 | July 9, 2019 | Caluwaert |
10348775 | July 9, 2019 | Barday |
10353673 | July 16, 2019 | Barday et al. |
10361857 | July 23, 2019 | Woo |
10366241 | July 30, 2019 | Sartor |
10373119 | August 6, 2019 | Driscoll et al. |
10373409 | August 6, 2019 | White et al. |
10375115 | August 6, 2019 | Mallya |
10387559 | August 20, 2019 | Wendt et al. |
10387577 | August 20, 2019 | Hill et al. |
10387657 | August 20, 2019 | Belfiore, Jr. et al. |
10387952 | August 20, 2019 | Sandhu et al. |
10395201 | August 27, 2019 | Vescio |
10402545 | September 3, 2019 | Gorfein et al. |
10404729 | September 3, 2019 | Turgeman |
10417401 | September 17, 2019 | Votaw et al. |
10417621 | September 17, 2019 | Cassel et al. |
10419476 | September 17, 2019 | Parekh |
10423985 | September 24, 2019 | Dutta et al. |
10425492 | September 24, 2019 | Comstock et al. |
10430608 | October 1, 2019 | Peri et al. |
10435350 | October 8, 2019 | Ito et al. |
10437412 | October 8, 2019 | Barday et al. |
10437860 | October 8, 2019 | Barday et al. |
10438016 | October 8, 2019 | Barday et al. |
10438273 | October 8, 2019 | Burns et al. |
10440062 | October 8, 2019 | Barday et al. |
10445508 | October 15, 2019 | Sher-Jan et al. |
10445526 | October 15, 2019 | Barday et al. |
10452864 | October 22, 2019 | Barday et al. |
10452866 | October 22, 2019 | Barday et al. |
10453076 | October 22, 2019 | Parekh et al. |
10453092 | October 22, 2019 | Wang et al. |
10454934 | October 22, 2019 | Parimi et al. |
10460322 | October 29, 2019 | Williamson et al. |
10481763 | November 19, 2019 | Bartkiewicz et al. |
10489454 | November 26, 2019 | Chen |
10503926 | December 10, 2019 | Barday et al. |
10510031 | December 17, 2019 | Barday et al. |
10521623 | December 31, 2019 | Rodriguez et al. |
10534851 | January 14, 2020 | Chan et al. |
10535081 | January 14, 2020 | Ferreira et al. |
10536475 | January 14, 2020 | McCorkle, Jr. et al. |
10536478 | January 14, 2020 | Kirti et al. |
10541938 | January 21, 2020 | Timmerman et al. |
10546135 | January 28, 2020 | Kassoumeh et al. |
10552462 | February 4, 2020 | Hart |
10558809 | February 11, 2020 | Joyce et al. |
10558821 | February 11, 2020 | Barday et al. |
10564815 | February 18, 2020 | Soon-Shiong |
10564935 | February 18, 2020 | Barday et al. |
10564936 | February 18, 2020 | Barday et al. |
10565161 | February 18, 2020 | Barday et al. |
10565236 | February 18, 2020 | Barday et al. |
10567439 | February 18, 2020 | Barday |
10567517 | February 18, 2020 | Weinig et al. |
10572684 | February 25, 2020 | Lafever et al. |
10572686 | February 25, 2020 | Barday et al. |
10574705 | February 25, 2020 | Barday et al. |
10581825 | March 3, 2020 | Poschel et al. |
10592648 | March 17, 2020 | Barday et al. |
10592692 | March 17, 2020 | Brannon et al. |
10606916 | March 31, 2020 | Brannon et al. |
10613971 | April 7, 2020 | Vasikarla |
10614365 | April 7, 2020 | Sathish et al. |
10628553 | April 21, 2020 | Murrish et al. |
10645102 | May 5, 2020 | Hamdi |
10645548 | May 5, 2020 | Reynolds et al. |
10649630 | May 12, 2020 | Vora et al. |
10650408 | May 12, 2020 | Andersen et al. |
10657469 | May 19, 2020 | Bade et al. |
10657504 | May 19, 2020 | Zimmerman et al. |
10659566 | May 19, 2020 | Luah et al. |
10671749 | June 2, 2020 | Felice-Steele et al. |
10671760 | June 2, 2020 | Esmailzadeh et al. |
10678945 | June 9, 2020 | Barday et al. |
10685140 | June 16, 2020 | Barday et al. |
10706176 | July 7, 2020 | Brannon et al. |
10706226 | July 7, 2020 | Byun et al. |
10708305 | July 7, 2020 | Barday et al. |
10713387 | July 14, 2020 | Brannon et al. |
10726145 | July 28, 2020 | Duminy et al. |
10726153 | July 28, 2020 | Nerurkar et al. |
10726158 | July 28, 2020 | Brannon et al. |
10732865 | August 4, 2020 | Jain et al. |
10735388 | August 4, 2020 | Rose et al. |
10740487 | August 11, 2020 | Barday et al. |
10747893 | August 18, 2020 | Kiriyama et al. |
10747897 | August 18, 2020 | Cook |
10749870 | August 18, 2020 | Brouillette et al. |
10762213 | September 1, 2020 | Rudek et al. |
10762236 | September 1, 2020 | Brannon et al. |
10769302 | September 8, 2020 | Barday et al. |
10769303 | September 8, 2020 | Brannon et al. |
10776510 | September 15, 2020 | Antonelli et al. |
10776518 | September 15, 2020 | Barday et al. |
10778792 | September 15, 2020 | Handy Bosma et al. |
10783256 | September 22, 2020 | Brannon et al. |
10785173 | September 22, 2020 | Willett et al. |
10785299 | September 22, 2020 | Gupta et al. |
10791150 | September 29, 2020 | Barday et al. |
10795527 | October 6, 2020 | Legge et al. |
10796020 | October 6, 2020 | Barday et al. |
10796260 | October 6, 2020 | Brannon et al. |
10798133 | October 6, 2020 | Barday et al. |
10803196 | October 13, 2020 | Bodegas Martinez et al. |
10805331 | October 13, 2020 | Boyer et al. |
10831831 | November 10, 2020 | Greene |
10834590 | November 10, 2020 | Turgeman et al. |
10846433 | November 24, 2020 | Brannon et al. |
10853501 | December 1, 2020 | Brannon |
10860721 | December 8, 2020 | Gentile |
10860742 | December 8, 2020 | Joseph et al. |
10860979 | December 8, 2020 | Geffen et al. |
10878127 | December 29, 2020 | Brannon et al. |
10885485 | January 5, 2021 | Brannon et al. |
10891393 | January 12, 2021 | Currier et al. |
10893074 | January 12, 2021 | Sartor |
10896394 | January 19, 2021 | Brannon et al. |
10902490 | January 26, 2021 | He et al. |
10909488 | February 2, 2021 | Hecht et al. |
10924514 | February 16, 2021 | Altman et al. |
10929557 | February 23, 2021 | Chavez |
10949555 | March 16, 2021 | Rattan et al. |
10949565 | March 16, 2021 | Barday et al. |
10956213 | March 23, 2021 | Chambers et al. |
10957326 | March 23, 2021 | Bhaya et al. |
10963571 | March 30, 2021 | Bar Joseph et al. |
10963572 | March 30, 2021 | Belfiore, Jr. et al. |
10965547 | March 30, 2021 | Esposito et al. |
10970418 | April 6, 2021 | Durvasula et al. |
10972509 | April 6, 2021 | Barday et al. |
10976950 | April 13, 2021 | Trezzo et al. |
10983963 | April 20, 2021 | Venkatasubramanian et al. |
10984458 | April 20, 2021 | Gutierrez |
10997318 | May 4, 2021 | Barday et al. |
11003748 | May 11, 2021 | Oliker et al. |
11012475 | May 18, 2021 | Patnala et al. |
11023528 | June 1, 2021 | Lee et al. |
11037168 | June 15, 2021 | Lee et al. |
11057356 | July 6, 2021 | Malhotra et al. |
11057427 | July 6, 2021 | Wright et al. |
11062051 | July 13, 2021 | Barday et al. |
11068318 | July 20, 2021 | Kuesel et al. |
11068584 | July 20, 2021 | Burriesci et al. |
11068618 | July 20, 2021 | Brannon et al. |
11068797 | July 20, 2021 | Bhide et al. |
11068847 | July 20, 2021 | Boutros et al. |
11093950 | August 17, 2021 | Hersh et al. |
11138299 | October 5, 2021 | Brannon et al. |
11144622 | October 12, 2021 | Brannon |
11144678 | October 12, 2021 | Dondini et al. |
11144862 | October 12, 2021 | Jackson et al. |
11195134 | December 7, 2021 | Brannon et al. |
11201929 | December 14, 2021 | Dudmesh et al. |
11210420 | December 28, 2021 | Brannon et al. |
11238390 | February 1, 2022 | Brannon et al. |
11240273 | February 1, 2022 | Barday et al. |
11252159 | February 15, 2022 | Kannan et al. |
11256777 | February 22, 2022 | Brannon et al. |
11263262 | March 1, 2022 | Chen |
11327996 | May 10, 2022 | Reynolds et al. |
11443062 | September 13, 2022 | Latka et al. |
20020004736 | January 10, 2002 | Roundtree et al. |
20020049907 | April 25, 2002 | Woods et al. |
20020055932 | May 9, 2002 | Wheeler et al. |
20020077941 | June 20, 2002 | Halligan et al. |
20020103854 | August 1, 2002 | Okita |
20020129216 | September 12, 2002 | Collins |
20020161594 | October 31, 2002 | Bryan et al. |
20020161733 | October 31, 2002 | Grainger |
20030041250 | February 27, 2003 | Proudler |
20030065641 | April 3, 2003 | Chaloux |
20030093680 | May 15, 2003 | Astley et al. |
20030097451 | May 22, 2003 | Bjorksten et al. |
20030097661 | May 22, 2003 | Li et al. |
20030115142 | June 19, 2003 | Brickell et al. |
20030130893 | July 10, 2003 | Farmer |
20030131001 | July 10, 2003 | Matsuo |
20030131093 | July 10, 2003 | Aschen et al. |
20030140150 | July 24, 2003 | Kemp et al. |
20030167216 | September 4, 2003 | Brown et al. |
20030212604 | November 13, 2003 | Cullen |
20040002818 | January 1, 2004 | Kulp et al. |
20040025053 | February 5, 2004 | Hayward |
20040088235 | May 6, 2004 | Ziekle et al. |
20040098366 | May 20, 2004 | Sinclair et al. |
20040098493 | May 20, 2004 | Rees |
20040111359 | June 10, 2004 | Hudock |
20040128508 | July 1, 2004 | Wheeler et al. |
20040186912 | September 23, 2004 | Harlow et al. |
20040193907 | September 30, 2004 | Patanella |
20050022198 | January 27, 2005 | Olapurath et al. |
20050033616 | February 10, 2005 | Vavul et al. |
20050076294 | April 7, 2005 | Dehamer et al. |
20050114343 | May 26, 2005 | Wesinger et al. |
20050144066 | June 30, 2005 | Cope et al. |
20050197884 | September 8, 2005 | Mullen, Jr. |
20050198177 | September 8, 2005 | Black |
20050198646 | September 8, 2005 | Kortela |
20050246292 | November 3, 2005 | Sarcanin |
20050278538 | December 15, 2005 | Fowler |
20060015263 | January 19, 2006 | Stupp |
20060031078 | February 9, 2006 | Pizzinger et al. |
20060035204 | February 16, 2006 | Lamarche et al. |
20060041507 | February 23, 2006 | Novack et al. |
20060075122 | April 6, 2006 | Lindskog et al. |
20060149730 | July 6, 2006 | Curtis |
20060156052 | July 13, 2006 | Bodnar et al. |
20060190280 | August 24, 2006 | Hoebel et al. |
20060206375 | September 14, 2006 | Scott et al. |
20060224422 | October 5, 2006 | Cohen |
20060253597 | November 9, 2006 | Mujica |
20060259416 | November 16, 2006 | Johnson |
20070011058 | January 11, 2007 | Dev |
20070027715 | February 1, 2007 | Gropper et al. |
20070061125 | March 15, 2007 | Bhatt et al. |
20070061393 | March 15, 2007 | Moore |
20070130101 | June 7, 2007 | Anderson et al. |
20070130323 | June 7, 2007 | Landsman et al. |
20070157311 | July 5, 2007 | Meier et al. |
20070173355 | July 26, 2007 | Klein |
20070179793 | August 2, 2007 | Bagchi et al. |
20070180490 | August 2, 2007 | Renzi et al. |
20070192438 | August 16, 2007 | Goei |
20070266420 | November 15, 2007 | Hawkins |
20070283171 | December 6, 2007 | Breslin et al. |
20080015927 | January 17, 2008 | Ramirez |
20080028065 | January 31, 2008 | Caso et al. |
20080028435 | January 31, 2008 | Strickland |
20080047016 | February 21, 2008 | Spoonamore |
20080120699 | May 22, 2008 | Spear |
20080140696 | June 12, 2008 | Mathuria |
20080189306 | August 7, 2008 | Hewett et al. |
20080195436 | August 14, 2008 | Whyte |
20080222271 | September 11, 2008 | Spires |
20080235177 | September 25, 2008 | Kim et al. |
20080270203 | October 30, 2008 | Holmes et al. |
20080270351 | October 30, 2008 | Thomsen |
20080270381 | October 30, 2008 | Thomsen |
20080270382 | October 30, 2008 | Thomsen et al. |
20080270451 | October 30, 2008 | Thomsen et al. |
20080270462 | October 30, 2008 | Thomsen |
20080281649 | November 13, 2008 | Morris |
20080282320 | November 13, 2008 | Denovo et al. |
20080288271 | November 20, 2008 | Faust |
20080288299 | November 20, 2008 | Schultz |
20090012896 | January 8, 2009 | Arnold |
20090022301 | January 22, 2009 | Mudaliar |
20090037975 | February 5, 2009 | Ishikawa et al. |
20090119500 | May 7, 2009 | Roth et al. |
20090132419 | May 21, 2009 | Grammer et al. |
20090138276 | May 28, 2009 | Hayashida et al. |
20090140035 | June 4, 2009 | Miller |
20090144702 | June 4, 2009 | Atkin et al. |
20090158249 | June 18, 2009 | Tomkins et al. |
20090172705 | July 2, 2009 | Cheong |
20090182818 | July 16, 2009 | Krywaniuk |
20090187764 | July 23, 2009 | Astakhov et al. |
20090204452 | August 13, 2009 | Iskandar et al. |
20090204820 | August 13, 2009 | Brandenburg et al. |
20090210347 | August 20, 2009 | Sarcanin |
20090216610 | August 27, 2009 | Chorny |
20090249076 | October 1, 2009 | Reed et al. |
20090303237 | December 10, 2009 | Liu et al. |
20100010912 | January 14, 2010 | Jones et al. |
20100010968 | January 14, 2010 | Redlich et al. |
20100077484 | March 25, 2010 | Paretti et al. |
20100082533 | April 1, 2010 | Nakamura et al. |
20100094650 | April 15, 2010 | Tran et al. |
20100100398 | April 22, 2010 | Auker et al. |
20100121773 | May 13, 2010 | Currier et al. |
20100192201 | July 29, 2010 | Shimoni et al. |
20100205057 | August 12, 2010 | Hook et al. |
20100223349 | September 2, 2010 | Thorson |
20100228786 | September 9, 2010 | Török |
20100234987 | September 16, 2010 | Benschop et al. |
20100235297 | September 16, 2010 | Mamorsky |
20100235915 | September 16, 2010 | Memon et al. |
20100262624 | October 14, 2010 | Pullikottil |
20100268628 | October 21, 2010 | Pitkow et al. |
20100268932 | October 21, 2010 | Bhattacharjee |
20100281313 | November 4, 2010 | White et al. |
20100287114 | November 11, 2010 | Bartko et al. |
20100333012 | December 30, 2010 | Adachi et al. |
20110006996 | January 13, 2011 | Smith et al. |
20110010202 | January 13, 2011 | Neale |
20110082794 | April 7, 2011 | Blechman |
20110137696 | June 9, 2011 | Meyer et al. |
20110145154 | June 16, 2011 | Rivers et al. |
20110153396 | June 23, 2011 | Marcuvitz et al. |
20110191664 | August 4, 2011 | Sheleheda et al. |
20110208850 | August 25, 2011 | Sheleheda et al. |
20110209067 | August 25, 2011 | Bogess et al. |
20110231896 | September 22, 2011 | Tovar |
20110238573 | September 29, 2011 | Varadarajan |
20110252456 | October 13, 2011 | Hatakeyama |
20110302643 | December 8, 2011 | Pichna et al. |
20120041939 | February 16, 2012 | Amsterdamski |
20120084151 | April 5, 2012 | Kozak et al. |
20120084349 | April 5, 2012 | Lee et al. |
20120102411 | April 26, 2012 | Sathish |
20120102543 | April 26, 2012 | Kohli et al. |
20120110674 | May 3, 2012 | Belani et al. |
20120116923 | May 10, 2012 | Irving et al. |
20120131438 | May 24, 2012 | Li et al. |
20120143650 | June 7, 2012 | Crowley et al. |
20120144499 | June 7, 2012 | Tan et al. |
20120191596 | July 26, 2012 | Kremen et al. |
20120226621 | September 6, 2012 | Petran et al. |
20120239557 | September 20, 2012 | Weinflash et al. |
20120254320 | October 4, 2012 | Dove et al. |
20120259752 | October 11, 2012 | Agee |
20120323700 | December 20, 2012 | Aleksandrovich et al. |
20120330769 | December 27, 2012 | Arceo |
20120330869 | December 27, 2012 | Durham |
20130004933 | January 3, 2013 | Bhaskaran |
20130018954 | January 17, 2013 | Cheng |
20130085801 | April 4, 2013 | Sharpe et al. |
20130091156 | April 11, 2013 | Raiche et al. |
20130103485 | April 25, 2013 | Postrel |
20130111323 | May 2, 2013 | Taghaddos et al. |
20130124257 | May 16, 2013 | Schubert |
20130159351 | June 20, 2013 | Hamann et al. |
20130171968 | July 4, 2013 | Wang |
20130179982 | July 11, 2013 | Bridges et al. |
20130179988 | July 11, 2013 | Bekker et al. |
20130185806 | July 18, 2013 | Hatakeyama |
20130211872 | August 15, 2013 | Cherry et al. |
20130218829 | August 22, 2013 | Martinez |
20130219459 | August 22, 2013 | Bradley |
20130254649 | September 26, 2013 | O'Neill et al. |
20130254699 | September 26, 2013 | Bashir et al. |
20130262328 | October 3, 2013 | Federgreen |
20130282466 | October 24, 2013 | Hampton |
20130290169 | October 31, 2013 | Bathula et al. |
20130298071 | November 7, 2013 | Wine |
20130311224 | November 21, 2013 | Heroux et al. |
20130318207 | November 28, 2013 | Dotter |
20130326112 | December 5, 2013 | Park et al. |
20130332362 | December 12, 2013 | Ciurea |
20130340086 | December 19, 2013 | Blom |
20140006355 | January 2, 2014 | Kirihata |
20140006616 | January 2, 2014 | Aad et al. |
20140012833 | January 9, 2014 | Humprecht |
20140019561 | January 16, 2014 | Belity et al. |
20140032259 | January 30, 2014 | Lafever et al. |
20140032265 | January 30, 2014 | Paprocki |
20140040134 | February 6, 2014 | Ciurea |
20140040161 | February 6, 2014 | Jason |
20140040979 | February 6, 2014 | Barton et al. |
20140041048 | February 6, 2014 | Goodwin et al. |
20140047551 | February 13, 2014 | Nagasu et al. |
20140052463 | February 20, 2014 | Cashman et al. |
20140067973 | March 6, 2014 | Eden |
20140074550 | March 13, 2014 | Chourey |
20140074645 | March 13, 2014 | Ingram |
20140089027 | March 27, 2014 | Brown |
20140089039 | March 27, 2014 | McClellan |
20140108173 | April 17, 2014 | Cooper et al. |
20140108968 | April 17, 2014 | Vishria |
20140137257 | May 15, 2014 | Martinez et al. |
20140142988 | May 22, 2014 | Grosso et al. |
20140143011 | May 22, 2014 | Mudugu et al. |
20140143844 | May 22, 2014 | Goertzen |
20140164476 | June 12, 2014 | Thomson |
20140188956 | July 3, 2014 | Subba et al. |
20140196143 | July 10, 2014 | Fliderman et al. |
20140208418 | July 24, 2014 | Libin |
20140222468 | August 7, 2014 | Araya et al. |
20140244309 | August 28, 2014 | Francois |
20140244325 | August 28, 2014 | Cartwright |
20140244375 | August 28, 2014 | Kim |
20140244399 | August 28, 2014 | Orduna et al. |
20140257917 | September 11, 2014 | Spencer et al. |
20140258093 | September 11, 2014 | Gardiner et al. |
20140278539 | September 18, 2014 | Edwards |
20140278663 | September 18, 2014 | Samuel et al. |
20140278730 | September 18, 2014 | Muhart et al. |
20140283027 | September 18, 2014 | Orona et al. |
20140283106 | September 18, 2014 | Stahura et al. |
20140288971 | September 25, 2014 | Whibbs, III |
20140289681 | September 25, 2014 | Wielgosz |
20140289862 | September 25, 2014 | Gorfein et al. |
20140317171 | October 23, 2014 | Fox et al. |
20140324480 | October 30, 2014 | Dufel et al. |
20140337041 | November 13, 2014 | Madden et al. |
20140337466 | November 13, 2014 | Li et al. |
20140344015 | November 20, 2014 | Puértolas-Montañés et al. |
20150006514 | January 1, 2015 | Hung |
20150012363 | January 8, 2015 | Grant et al. |
20150019530 | January 15, 2015 | Felch |
20150026056 | January 22, 2015 | Calman et al. |
20150026260 | January 22, 2015 | Worthley |
20150033112 | January 29, 2015 | Norwood et al. |
20150066577 | March 5, 2015 | Christiansen et al. |
20150066865 | March 5, 2015 | Yara et al. |
20150088598 | March 26, 2015 | Acharyya et al. |
20150089585 | March 26, 2015 | Novack |
20150095352 | April 2, 2015 | Lacey |
20150106264 | April 16, 2015 | Johnson |
20150106867 | April 16, 2015 | Liang |
20150106948 | April 16, 2015 | Holman et al. |
20150106949 | April 16, 2015 | Holman et al. |
20150121462 | April 30, 2015 | Courage et al. |
20150143258 | May 21, 2015 | Carolan et al. |
20150149362 | May 28, 2015 | Baum et al. |
20150154520 | June 4, 2015 | Federgreen et al. |
20150169318 | June 18, 2015 | Nash |
20150172296 | June 18, 2015 | Fujioka |
20150178740 | June 25, 2015 | Borawski et al. |
20150199534 | July 16, 2015 | Francis et al. |
20150199541 | July 16, 2015 | Koch et al. |
20150199702 | July 16, 2015 | Singh |
20150229664 | August 13, 2015 | Hawthorn et al. |
20150235049 | August 20, 2015 | Cohen et al. |
20150235050 | August 20, 2015 | Wouhaybi et al. |
20150235283 | August 20, 2015 | Nishikawa |
20150242778 | August 27, 2015 | Wilcox et al. |
20150242858 | August 27, 2015 | Smith et al. |
20150248391 | September 3, 2015 | Watanabe |
20150254597 | September 10, 2015 | Jahagirdar |
20150261887 | September 17, 2015 | Joukov |
20150262189 | September 17, 2015 | Vergeer |
20150264417 | September 17, 2015 | Spitz et al. |
20150269384 | September 24, 2015 | Holman et al. |
20150271167 | September 24, 2015 | Kalai |
20150288715 | October 8, 2015 | Hotchkiss |
20150309813 | October 29, 2015 | Patel |
20150310227 | October 29, 2015 | Ishida et al. |
20150310575 | October 29, 2015 | Shelton |
20150348200 | December 3, 2015 | Fair et al. |
20150356362 | December 10, 2015 | Demos |
20150379430 | December 31, 2015 | Dirac et al. |
20160006760 | January 7, 2016 | Lala et al. |
20160012465 | January 14, 2016 | Sharp |
20160026394 | January 28, 2016 | Goto |
20160034918 | February 4, 2016 | Bjelajac et al. |
20160048700 | February 18, 2016 | Stransky-Heilkron |
20160050213 | February 18, 2016 | Storr |
20160063523 | March 3, 2016 | Nistor et al. |
20160063567 | March 3, 2016 | Srivastava |
20160071112 | March 10, 2016 | Unser |
20160080405 | March 17, 2016 | Schler et al. |
20160087957 | March 24, 2016 | Shah et al. |
20160099963 | April 7, 2016 | Mahaffey et al. |
20160103963 | April 14, 2016 | Mishra |
20160104259 | April 14, 2016 | Menrad |
20160125550 | May 5, 2016 | Joao et al. |
20160125749 | May 5, 2016 | Delacroix et al. |
20160125751 | May 5, 2016 | Barker et al. |
20160140466 | May 19, 2016 | Sidebottom et al. |
20160143570 | May 26, 2016 | Valacich et al. |
20160148143 | May 26, 2016 | Anderson et al. |
20160162269 | June 9, 2016 | Pogorelik et al. |
20160164915 | June 9, 2016 | Cook |
20160180386 | June 23, 2016 | Konig |
20160188450 | June 30, 2016 | Appusamy et al. |
20160189156 | June 30, 2016 | Kim et al. |
20160196189 | July 7, 2016 | Miyagi et al. |
20160225000 | August 4, 2016 | Glasgow |
20160232465 | August 11, 2016 | Kurtz et al. |
20160232534 | August 11, 2016 | Lacey et al. |
20160234319 | August 11, 2016 | Griffin |
20160253497 | September 1, 2016 | Christodorescu et al. |
20160255139 | September 1, 2016 | Rathod |
20160261631 | September 8, 2016 | Vissamsetty et al. |
20160262163 | September 8, 2016 | Gonzalez Garrido et al. |
20160292453 | October 6, 2016 | Patterson et al. |
20160292621 | October 6, 2016 | Ciccone et al. |
20160321582 | November 3, 2016 | Broudou et al. |
20160321748 | November 3, 2016 | Mahatma et al. |
20160330237 | November 10, 2016 | Edlabadkar |
20160335531 | November 17, 2016 | Mullen et al. |
20160342811 | November 24, 2016 | Whitcomb et al. |
20160359861 | December 8, 2016 | Manov et al. |
20160364736 | December 15, 2016 | Maugans, III |
20160370954 | December 22, 2016 | Burningham et al. |
20160378762 | December 29, 2016 | Rohter |
20160381064 | December 29, 2016 | Chan et al. |
20160381560 | December 29, 2016 | Margaliot |
20170004055 | January 5, 2017 | Horan et al. |
20170032395 | February 2, 2017 | Kaufman et al. |
20170032408 | February 2, 2017 | Kumar et al. |
20170034101 | February 2, 2017 | Kumar et al. |
20170041324 | February 9, 2017 | Ionutescu et al. |
20170046399 | February 16, 2017 | Sankaranarasimhan et al. |
20170046753 | February 16, 2017 | Deupree, IV |
20170061501 | March 2, 2017 | Horwich |
20170068785 | March 9, 2017 | Experton et al. |
20170070495 | March 9, 2017 | Cherry et al. |
20170093917 | March 30, 2017 | Chandra et al. |
20170115864 | April 27, 2017 | Thomas et al. |
20170124570 | May 4, 2017 | Nidamanuri et al. |
20170140174 | May 18, 2017 | Lacey et al. |
20170140467 | May 18, 2017 | Neag et al. |
20170142158 | May 18, 2017 | Laoutaris et al. |
20170142177 | May 18, 2017 | Hu |
20170154188 | June 1, 2017 | Meier et al. |
20170161520 | June 8, 2017 | Lockhart, III et al. |
20170171235 | June 15, 2017 | Mulchandani et al. |
20170171325 | June 15, 2017 | Perez |
20170177324 | June 22, 2017 | Frank et al. |
20170180378 | June 22, 2017 | Tyler et al. |
20170180505 | June 22, 2017 | Shaw |
20170193017 | July 6, 2017 | Migliori |
20170193624 | July 6, 2017 | Tsai |
20170201518 | July 13, 2017 | Holmqvist et al. |
20170206707 | July 20, 2017 | Guay et al. |
20170208084 | July 20, 2017 | Steelman et al. |
20170220685 | August 3, 2017 | Yan et al. |
20170220964 | August 3, 2017 | Datta Ray |
20170249710 | August 31, 2017 | Guillama et al. |
20170269791 | September 21, 2017 | Meyerzon et al. |
20170270318 | September 21, 2017 | Ritchie |
20170278004 | September 28, 2017 | Mcelhinney et al. |
20170278117 | September 28, 2017 | Wallace et al. |
20170286719 | October 5, 2017 | Krishnamurthy et al. |
20170287031 | October 5, 2017 | Barday |
20170289199 | October 5, 2017 | Barday |
20170308875 | October 26, 2017 | O'Regan et al. |
20170316400 | November 2, 2017 | Venkatakrishnan et al. |
20170330197 | November 16, 2017 | DiMaggio et al. |
20170353404 | December 7, 2017 | Hodge |
20180032757 | February 1, 2018 | Michael |
20180039975 | February 8, 2018 | Hefetz |
20180041498 | February 8, 2018 | Kikuchi |
20180046753 | February 15, 2018 | Shelton |
20180046939 | February 15, 2018 | Meron et al. |
20180063174 | March 1, 2018 | Grill et al. |
20180063190 | March 1, 2018 | Wright et al. |
20180082368 | March 22, 2018 | Weinflash et al. |
20180083843 | March 22, 2018 | Sambandam |
20180091476 | March 29, 2018 | Jakobsson et al. |
20180131574 | May 10, 2018 | Jacobs et al. |
20180131658 | May 10, 2018 | Bhagwan et al. |
20180165637 | June 14, 2018 | Romero et al. |
20180198614 | July 12, 2018 | Neumann |
20180204281 | July 19, 2018 | Painter et al. |
20180219917 | August 2, 2018 | Chiang |
20180239500 | August 23, 2018 | Allen et al. |
20180248914 | August 30, 2018 | Sartor |
20180285887 | October 4, 2018 | Crispen |
20180301222 | October 18, 2018 | Dew, Sr. et al. |
20180307859 | October 25, 2018 | Lafever et al. |
20180336509 | November 22, 2018 | Guttmann |
20180349583 | December 6, 2018 | Turgeman et al. |
20180351888 | December 6, 2018 | Howard |
20180352003 | December 6, 2018 | Winn et al. |
20180357243 | December 13, 2018 | Yoon |
20180365720 | December 20, 2018 | Goldman et al. |
20180374030 | December 27, 2018 | Barday et al. |
20180375814 | December 27, 2018 | Hart |
20190005210 | January 3, 2019 | Wiederspohn et al. |
20190012211 | January 10, 2019 | Selvaraj |
20190012672 | January 10, 2019 | Francesco |
20190019184 | January 17, 2019 | Lacey et al. |
20190050547 | February 14, 2019 | Welsh et al. |
20190087570 | March 21, 2019 | Sloane |
20190096020 | March 28, 2019 | Barday et al. |
20190108353 | April 11, 2019 | Sadeh et al. |
20190130132 | May 2, 2019 | Barbas et al. |
20190132350 | May 2, 2019 | Smith et al. |
20190138496 | May 9, 2019 | Yamaguchi |
20190139087 | May 9, 2019 | Dabbs et al. |
20190148003 | May 16, 2019 | Van Hoe |
20190156053 | May 23, 2019 | Vogel et al. |
20190156058 | May 23, 2019 | Van Dyne et al. |
20190171801 | June 6, 2019 | Barday et al. |
20190179652 | June 13, 2019 | Hesener et al. |
20190180051 | June 13, 2019 | Barday et al. |
20190182294 | June 13, 2019 | Rieke et al. |
20190188402 | June 20, 2019 | Wang et al. |
20190266200 | August 29, 2019 | Francolla |
20190266201 | August 29, 2019 | Barday et al. |
20190266350 | August 29, 2019 | Barday et al. |
20190268343 | August 29, 2019 | Barday et al. |
20190268344 | August 29, 2019 | Barday et al. |
20190272492 | September 5, 2019 | Elledge et al. |
20190294818 | September 26, 2019 | Barday et al. |
20190332802 | October 31, 2019 | Barday et al. |
20190332807 | October 31, 2019 | Lafever et al. |
20190333118 | October 31, 2019 | Crimmins et al. |
20190354709 | November 21, 2019 | Brinskelle |
20190356684 | November 21, 2019 | Sinha et al. |
20190362169 | November 28, 2019 | Lin et al. |
20190362268 | November 28, 2019 | Fogarty et al. |
20190377901 | December 12, 2019 | Balzer et al. |
20190378073 | December 12, 2019 | Lopez et al. |
20190384934 | December 19, 2019 | Kim |
20190392162 | December 26, 2019 | Stern et al. |
20190392170 | December 26, 2019 | Barday et al. |
20190392171 | December 26, 2019 | Barday et al. |
20200020454 | January 16, 2020 | McGarvey et al. |
20200050966 | February 13, 2020 | Enuka et al. |
20200051117 | February 13, 2020 | Mitchell |
20200057781 | February 20, 2020 | McCormick |
20200074471 | March 5, 2020 | Adjaoute |
20200081865 | March 12, 2020 | Farrar et al. |
20200082270 | March 12, 2020 | Gu et al. |
20200090197 | March 19, 2020 | Rodriguez et al. |
20200092179 | March 19, 2020 | Chieu et al. |
20200110589 | April 9, 2020 | Bequet et al. |
20200110904 | April 9, 2020 | Shinde et al. |
20200117737 | April 16, 2020 | Gopalakrishnan et al. |
20200137097 | April 30, 2020 | Zimmermann et al. |
20200143301 | May 7, 2020 | Bowers |
20200143797 | May 7, 2020 | Manoharan et al. |
20200159952 | May 21, 2020 | Dain et al. |
20200159955 | May 21, 2020 | Barlik et al. |
20200167653 | May 28, 2020 | Manjunath et al. |
20200175424 | June 4, 2020 | Kursun |
20200183655 | June 11, 2020 | Barday et al. |
20200186355 | June 11, 2020 | Davies |
20200193018 | June 18, 2020 | Van Dyke |
20200193022 | June 18, 2020 | Lunsford et al. |
20200210558 | July 2, 2020 | Barday et al. |
20200210620 | July 2, 2020 | Haletky |
20200211002 | July 2, 2020 | Steinberg |
20200220901 | July 9, 2020 | Barday et al. |
20200226156 | July 16, 2020 | Borra et al. |
20200226196 | July 16, 2020 | Brannon et al. |
20200242259 | July 30, 2020 | Chirravuri et al. |
20200242719 | July 30, 2020 | Lee |
20200250342 | August 6, 2020 | Miller et al. |
20200252413 | August 6, 2020 | Buzbee et al. |
20200252817 | August 6, 2020 | Brouillette et al. |
20200272764 | August 27, 2020 | Brannon et al. |
20200285755 | September 10, 2020 | Kassoumeh et al. |
20200293679 | September 17, 2020 | Handy Bosma et al. |
20200296171 | September 17, 2020 | Mocanu et al. |
20200302089 | September 24, 2020 | Barday et al. |
20200310917 | October 1, 2020 | Tkachev et al. |
20200311310 | October 1, 2020 | Barday et al. |
20200344243 | October 29, 2020 | Brannon et al. |
20200356695 | November 12, 2020 | Brannon et al. |
20200364369 | November 19, 2020 | Brannon et al. |
20200372178 | November 26, 2020 | Barday et al. |
20200394327 | December 17, 2020 | Childress et al. |
20200401380 | December 24, 2020 | Jacobs et al. |
20200401962 | December 24, 2020 | Gottemukkala et al. |
20200410117 | December 31, 2020 | Barday et al. |
20200410131 | December 31, 2020 | Barday et al. |
20200410132 | December 31, 2020 | Brannon et al. |
20210012341 | January 14, 2021 | Garg et al. |
20210056569 | February 25, 2021 | Silberman et al. |
20210081567 | March 18, 2021 | Park et al. |
20210099449 | April 1, 2021 | Frederick et al. |
20210110047 | April 15, 2021 | Victor |
20210125089 | April 29, 2021 | Nickl et al. |
20210136065 | May 6, 2021 | Liokumovich et al. |
20210152496 | May 20, 2021 | Kim et al. |
20210233157 | July 29, 2021 | Crutchfield, Jr. |
20210243595 | August 5, 2021 | Buck et al. |
20210248247 | August 12, 2021 | Poothokaran et al. |
20210256163 | August 19, 2021 | Fleming et al. |
20210279360 | September 9, 2021 | Gimenez Palop et al. |
20210297441 | September 23, 2021 | Olalere |
20210303828 | September 30, 2021 | Lafreniere et al. |
20210312061 | October 7, 2021 | Schroeder et al. |
20210326786 | October 21, 2021 | Sun et al. |
20210328969 | October 21, 2021 | Gaddam et al. |
20210382949 | December 9, 2021 | Yastrebenetsky et al. |
20210397735 | December 23, 2021 | Samatov et al. |
20210400018 | December 23, 2021 | Vettaikaran et al. |
20210406712 | December 30, 2021 | Bhide et al. |
20220217045 | July 7, 2022 | Blau et al. |
111496802 | August 2020 | CN |
112115859 | December 2020 | CN |
1394698 | March 2004 | EP |
2031540 | March 2009 | EP |
20130062500 | June 2013 | KR |
2001033430 | May 2001 | WO |
20020067158 | August 2002 | WO |
20030050773 | June 2003 | WO |
2005008411 | January 2005 | WO |
2007002412 | January 2007 | WO |
2008/134203 | November 2008 | WO |
2012174659 | December 2012 | WO |
2015116905 | August 2015 | WO |
2020/146028 | July 2020 | WO |
2022006421 | January 2022 | WO |
- Office Action, dated Nov. 1, 2017, from corresponding U.S. Appl. No. 15/169,658.
- Office Action, dated Nov. 10, 2021, from corresponding U.S. Appl. No. 17/380,485.
- Office Action, dated Nov. 10, 2021, from corresponding U.S. Appl. No. 17/409,999.
- Office Action, dated Nov. 12, 2020, from corresponding U.S. Appl. No. 17/034,355.
- Office Action, dated Nov. 12, 2020, from corresponding U.S. Appl. No. 17/034,772.
- Office Action, dated Nov. 12, 2021, from corresponding U.S. Appl. No. 17/346,586.
- Office Action, dated Nov. 12, 2021, from corresponding U.S. Appl. No. 17/373,444.
- Office Action, dated Nov. 15, 2018, from corresponding U.S. Appl. No. 16/059,911.
- Office Action, dated Nov. 15, 2019, from corresponding U.S. Appl. No. 16/552,758.
- Office Action, dated Nov. 16, 2021, from corresponding U.S. Appl. No. 17/370,650.
- Office Action, dated Nov. 16, 2021, from corresponding U.S. Appl. No. 17/486,350.
- Office Action, dated Nov. 18, 2019, from corresponding U.S. Appl. No. 16/560,885.
- Office Action, dated Nov. 18, 2019, from corresponding U.S. Appl. No. 16/560,889.
- Office Action, dated Nov. 18, 2019, from corresponding U.S. Appl. No. 16/572,347.
- Office Action, dated Nov. 19, 2019, from corresponding U.S. Appl. No. 16/595,342.
- Office Action, dated Nov. 20, 2019, from corresponding U.S. Appl. No. 16/595,327.
- Office Action, dated Nov. 23, 2018, from corresponding U.S. Appl. No. 16/042,673.
- Office Action, dated Nov. 23, 2021, from corresponding U.S. Appl. No. 17/013,756.
- Office Action, dated Nov. 24, 2020, from corresponding U.S. Appl. No. 16/925,628.
- Office Action, dated Nov. 26, 2021, from corresponding U.S. Appl. No. 16/925,550.
- Office Action, dated Nov. 4, 2021, from corresponding U.S. Appl. No. 17/491,906.
- Office Action, dated Nov. 8, 2021, from corresponding U.S. Appl. No. 16/872,130.
- Office Action, dated Oct. 10, 2018, from corresponding U.S. Appl. No. 16/041,563.
- Office Action, dated Oct. 10, 2018, from corresponding U.S. Appl. No. 16/055,083.
- Office Action, dated Oct. 10, 2018, from corresponding U.S. Appl. No. 16/055,944.
- Office Action, dated Oct. 12, 2021, from corresponding U.S. Appl. No. 17/346,509.
- Office Action, dated Oct. 14, 2020, from corresponding U.S. Appl. No. 16/927,658.
- Office Action, dated Oct. 15, 2018, from corresponding U.S. Appl. No. 16/054,780.
- Office Action, dated Oct. 15, 2021, from corresponding U.S. Appl. No. 16/908,081.
- Office Action, dated Oct. 16, 2019, from corresponding U.S. Appl. No. 16/557,392.
- Office Action, dated Oct. 16, 2020, from corresponding U.S. Appl. No. 16/808,489.
- Office Action, dated Oct. 23, 2018, from corresponding U.S. Appl. No. 16/055,961.
- Office Action, dated Oct. 26, 2018, from corresponding U.S. Appl. No. 16/041,468.
- Office Action, dated Oct. 8, 2019, from corresponding U.S. Appl. No. 16/552,765.
- Office Action, dated Sep. 1, 2017, from corresponding U.S. Appl. No. 15/619,459.
- Office Action, dated Sep. 11, 2017, from corresponding U.S. Appl. No. 15/619,375.
- Office Action, dated Sep. 11, 2017, from corresponding U.S. Appl. No. 15/619,478.
- Office Action, dated Sep. 15, 2021, from corresponding U.S. Appl. No. 16/623,157.
- Office Action, dated Sep. 16, 2019, from corresponding U.S. Appl. No. 16/277,715.
- Office Action, dated Sep. 19, 2017, from corresponding U.S. Appl. No. 15/671,073.
- Office Action, dated Sep. 22, 2017, from corresponding U.S. Appl. No. 15/619,278.
- Office Action, dated Sep. 24, 2021, from corresponding U.S. Appl. No. 17/342,153.
- Office Action, dated Sep. 4, 2020, from corresponding U.S. Appl. No. 16/989,086.
- Office Action, dated Sep. 5, 2017, from corresponding U.S. Appl. No. 15/619,469.
- Office Action, dated Sep. 6, 2017, from corresponding U.S. Appl. No. 15/619,479.
- Office Action, dated Sep. 7, 2017, from corresponding U.S. Appl. No. 15/633,703.
- Office Action, dated Sep. 8, 2017, from corresponding U.S. Appl. No. 15/619,251.
- Notice of Allowance, dated Apr. 12, 2017, from corresponding U.S. Appl. No. 15/256,419.
- Notice of Allowance, dated Apr. 17, 2020, from corresponding U.S. Appl. No. 16/593,639.
- Notice of Allowance, dated Apr. 19, 2021, from corresponding U.S. Appl. No. 17/164,029.
- Office Action, dated Aug. 13, 2019, from corresponding U.S. Appl. No. 16/505,430.
- Office Action, dated Aug. 13, 2019, from corresponding U.S. Appl. No. 16/512,033.
- Office Action, dated Aug. 15, 2019, from corresponding U.S. Appl. No. 16/505,461.
- Office Action, dated Aug. 18, 2021, from corresponding U.S. Appl. No. 17/222,725.
- Office Action, dated Aug. 19, 2019, from corresponding U.S. Appl. No. 16/278,122.
- Office Action, dated Aug. 20, 2020, from corresponding U.S. Appl. No. 16/817,136.
- Office Action, dated Aug. 23, 2017, from corresponding U.S. Appl. No. 15/626,052.
- Office Action, dated Aug. 24, 2017, from corresponding U.S. Appl. No. 15/169,643.
- Office Action, dated Aug. 24, 2017, from corresponding U.S. Appl. No. 15/619,451.
- Office Action, dated Aug. 24, 2020, from corresponding U.S. Appl. No. 16/595,327.
- Office Action, dated Aug. 27, 2019, from corresponding U.S. Appl. No. 16/410,296.
- Office Action, dated Aug. 27, 2021, from corresponding U.S. Appl. No. 17/187,329.
- Office Action, dated Aug. 27, 2021, from corresponding U.S. Appl. No. 17/334,948.
- Office Action, dated Aug. 29, 2017, from corresponding U.S. Appl. No. 15/619,237.
- Office Action, dated Aug. 30, 2017, from corresponding U.S. Appl. No. 15/619,212.
- Office Action, dated Aug. 30, 2017, from corresponding U.S. Appl. No. 15/619,382.
- Office Action, dated Aug. 30, 2021, from corresponding U.S. Appl. No. 16/938,520.
- Office Action, dated Aug. 6, 2019, from corresponding U.S. Appl. No. 16/404,491.
- Office Action, dated Aug. 6, 2020, from corresponding U.S. Appl. No. 16/862,956.
- Office Action, dated Dec. 11, 2019, from corresponding U.S. Appl. No. 16/578,712.
- Office Action, dated Dec. 14, 2018, from corresponding U.S. Appl. No. 16/104,393.
- Office Action, dated Dec. 15, 2016, from corresponding U.S. Appl. No. 15/256,419.
- Office Action, dated Dec. 16, 2019, from corresponding U.S. Appl. No. 16/563,754.
- Office Action, dated Dec. 16, 2019, from corresponding U.S. Appl. No. 16/565,265.
- Office Action, dated Dec. 16, 2020, from corresponding U.S. Appl. No. 17/020,275.
- Office Action, dated Dec. 18, 2020, from corresponding U.S. Appl. No. 17/030,714.
- Office Action, dated Dec. 19, 2019, from corresponding U.S. Appl. No. 16/410,866.
- Office Action, dated Dec. 2, 2019, from corresponding U.S. Appl. No. 16/560,963.
- Office Action, dated Dec. 23, 2019, from corresponding U.S. Appl. No. 16/593,639.
- Office Action, dated Dec. 24, 2020, from corresponding U.S. Appl. No. 17/068,454.
- Office Action, dated Dec. 3, 2018, from corresponding U.S. Appl. No. 16/055,998.
- Office Action, dated Dec. 31, 2018, from corresponding U.S. Appl. No. 16/160,577.
- Office Action, dated Dec. 8, 2020, from corresponding U.S. Appl. No. 17/013,758.
- Office Action, dated Dec. 8, 2020, from corresponding U.S. Appl. No. 17/068,198.
- Office Action, dated Feb. 10, 2021, from corresponding U.S. Appl. No. 16/862,944.
- Office Action, dated Feb. 10, 2021, from corresponding U.S. Appl. No. 17/106,469.
- Office Action, dated Feb. 15, 2019, from corresponding U.S. Appl. No. 16/220,899.
- Office Action, dated Feb. 17, 2021, from corresponding U.S. Appl. No. 16/862,948.
- Office Action, dated Feb. 18, 2021, from corresponding U.S. Appl. No. 16/862,952.
- Office Action, dated Feb. 2, 2021, from corresponding U.S. Appl. No. 17/101,915.
- Office Action, dated Feb. 26, 2019, from corresponding U.S. Appl. No. 16/228,250.
- Office Action, dated Feb. 3, 2021, from corresponding U.S. Appl. No. 17/013,757.
- Office Action, dated Feb. 5, 2020, from corresponding U.S. Appl. No. 16/586,202.
- Office Action, dated Feb. 6, 2020, from corresponding U.S. Appl. No. 16/707,762.
- Office Action, dated Feb. 8, 2021, from corresponding U.S. Appl. No. 17/139,650.
- Office Action, dated Feb. 9, 2021, from corresponding U.S. Appl. No. 16/808,493.
- Office Action, dated Jan. 18, 2019, from corresponding U.S. Appl. No. 16/055,984.
- Office Action, dated Jan. 22, 2021, from corresponding U.S. Appl. No. 17/099,270.
- Office Action, dated Jan. 24, 2020, from corresponding U.S. Appl. No. 16/505,426.
- Office Action, dated Jan. 24, 2020, from corresponding U.S. Appl. No. 16/700,049.
- Czeskis et al., “Lightweight Server Support for Browser-based CSRF Protection,” Proceedings of the 22nd International Conference on World Wide Web, 2013, pp. 273-284 (Year: 2013).
- Final Office Action, dated Feb. 25, 2022, from corresponding U.S. Appl. No. 17/346,586.
- Final Office Action, dated Mar. 21, 2022, from corresponding U.S. Appl. No. 17/373,444.
- Final Office Action, dated Mar. 22, 2022, from corresponding U.S. Appl. No. 17/380,485.
- Matte et al, “Do Cookie Banners Respect my Choice?: Measuring Legal Compliance of Banners from IAB Europe's Transparency and Consent Framework,” 2020 IEEE Symposium on Security and Privacy (SP), 2020, pp. 791-809 (Year: 2020).
- Notice of Allowance, dated Feb. 24, 2022, from corresponding U.S. Appl. No. 17/234,205.
- Notice of Allowance, dated Feb. 24, 2022, from corresponding U.S. Appl. No. 17/549,170.
- Notice of Allowance, dated Mar. 16, 2022, from corresponding U.S. Appl. No. 17/486,350.
- Notice of Allowance, dated Mar. 2, 2022, from corresponding U.S. Appl. No. 16/872,130.
- Notice of Allowance, dated Mar. 2, 2022, from corresponding U.S. Appl. No. 17/535,098.
- Notice of Allowance, dated Mar. 21, 2022, from corresponding U.S. Appl. No. 17/366,754.
- Notice of Allowance, dated Mar. 22, 2022, from corresponding U.S. Appl. No. 17/475,244.
- Notice of Allowance, dated Mar. 22, 2022, from corresponding U.S. Appl. No. 17/504,102.
- Notice of Allowance, dated Mar. 28, 2022, from corresponding U.S. Appl. No. 17/499,609.
- Notice of Allowance, dated Mar. 4, 2022, from corresponding U.S. Appl. No. 17/409,999.
- Office Action, dated Mar. 1, 2022, from corresponding U.S. Appl. No. 17/119,080.
- Office Action, dated Mar. 2, 2022, from corresponding U.S. Appl. No. 17/020,275.
- Office Action, dated Mar. 2, 2022, from corresponding U.S. Appl. No. 17/161,159.
- Office Action, dated Mar. 2, 2022, from corresponding U.S. Appl. No. 17/200,698.
- Office Action, dated Mar. 21, 2022, from corresponding U.S. Appl. No. 17/571,871.
- Office Action, dated Mar. 22, 2022, from corresponding U.S. Appl. No. 17/187,329.
- Sanchez-Rola et al., “Can I Opt Out Yet?: GDPR and the Global Illusion of Cookie Control,” Proceedings of the 2019 ACM Asia Conference on Computer and Communications Security, 2019, pp. 340-351 (Year: 2019).
- Office Action, dated Jan. 27, 2020, from corresponding U.S. Appl. No. 16/656,895.
- Office Action, dated Jan. 28, 2020, from corresponding U.S. Appl. No. 16/712,104.
- Office Action, dated Jan. 29, 2021, from corresponding U.S. Appl. No. 17/101,106.
- Office Action, dated Jan. 4, 2019, from corresponding U.S. Appl. No. 16/159,566.
- Office Action, dated Jan. 4, 2019, from corresponding U.S. Appl. No. 16/159,628.
- Office Action, dated Jan. 4, 2021, from corresponding U.S. Appl. No. 17/013,756.
- Office Action, dated Jan. 7, 2020, from corresponding U.S. Appl. No. 16/572,182.
- Office Action, dated Jul. 13, 2021, from corresponding U.S. Appl. No. 17/306,496.
- Office Action, dated Jul. 15, 2021, from corresponding U.S. Appl. No. 17/020,275.
- Office Action, dated Jul. 18, 2019, from corresponding U.S. Appl. No. 16/410,762.
- Office Action, dated Jul. 19, 2021, from corresponding U.S. Appl. No. 17/316,179.
- Office Action, dated Jul. 21, 2017, from corresponding U.S. Appl. No. 15/256,430.
- Office Action, dated Jul. 21, 2021, from corresponding U.S. Appl. No. 16/901,654.
- Office Action, dated Jul. 23, 2019, from corresponding U.S. Appl. No. 16/436,616.
- Office Action, dated Jul. 24, 2020, from corresponding U.S. Appl. No. 16/404,491.
- Office Action, dated Jul. 27, 2020, from corresponding U.S. Appl. No. 16/595,342.
- Office Action, dated Jun. 1, 2020, from corresponding U.S. Appl. No. 16/862,952.
- Office Action, dated Jun. 24, 2019, from corresponding U.S. Appl. No. 16/410,336.
- Office Action, dated Jun. 24, 2021, from corresponding U.S. Appl. No. 17/234,205.
- Office Action, dated Jun. 27, 2019, from corresponding U.S. Appl. No. 16/404,405.
- Office Action, dated Jun. 7, 2021, from corresponding U.S. Appl. No. 17/200,698.
- Office Action, dated Jun. 9, 2021, from corresponding U.S. Appl. No. 17/222,523.
- Office Action, dated Mar. 11, 2019, from corresponding U.S. Appl. No. 16/220,978.
- Office Action, dated Mar. 12, 2019, from corresponding U.S. Appl. No. 16/221,153.
- Office Action, dated Mar. 15, 2021, from corresponding U.S. Appl. No. 17/149,421.
- Office Action, dated Mar. 16, 2020, from corresponding U.S. Appl. No. 16/719,488.
- Office Action, dated Mar. 17, 2020, from corresponding U.S. Appl. No. 16/565,395.
- Office Action, dated Mar. 17, 2020, from corresponding U.S. Appl. No. 16/719,071.
- Office Action, dated Mar. 20, 2020, from corresponding U.S. Appl. No. 16/778,709.
- Office Action, dated Mar. 23, 2020, from corresponding U.S. Appl. No. 16/671,444.
- Office Action, dated Mar. 25, 2019, from corresponding U.S. Appl. No. 16/278,121.
- Office Action, dated Mar. 25, 2020, from corresponding U.S. Appl. No. 16/701,043.
- Office Action, dated Mar. 25, 2020, from corresponding U.S. Appl. No. 16/791,006.
- Office Action, dated Mar. 27, 2019, from corresponding U.S. Appl. No. 16/278,120.
- Office Action, dated Mar. 30, 2018, from corresponding U.S. Appl. No. 15/894,890.
- Office Action, dated Mar. 30, 2018, from corresponding U.S. Appl. No. 15/896,790.
- Office Action, dated Mar. 30, 2021, from corresponding U.S. Appl. No. 17/151,399.
- Office Action, dated Mar. 4, 2019, from corresponding U.S. Appl. No. 16/237,083.
- Office Action, dated May 14, 2020, from corresponding U.S. Appl. No. 16/808,497.
- Office Action, dated May 14, 2020, from corresponding U.S. Appl. No. 16/808,503.
- Office Action, dated May 15, 2020, from corresponding U.S. Appl. No. 16/808,493.
- Office Action, dated May 16, 2018, from corresponding U.S. Appl. No. 15/882,989.
- Office Action, dated May 17, 2019, from corresponding U.S. Appl. No. 16/277,539.
- Office Action, dated May 18, 2021, from corresponding U.S. Appl. No. 17/196,570.
- Office Action, dated May 2, 2018, from corresponding U.S. Appl. No. 15/894,809.
- Office Action, dated May 2, 2019, from corresponding U.S. Appl. No. 16/104,628.
- Office Action, dated May 29, 2020, from corresponding U.S. Appl. No. 16/862,944.
- Office Action, dated May 29, 2020, from corresponding U.S. Appl. No. 16/862,948.
- Office Action, dated May 29, 2020, from corresponding U.S. Appl. No. 16/863,226.
- Office Action, dated May 5, 2020, from corresponding U.S. Appl. No. 16/410,336.
- Imran et al, “Searching in Cloud Object Storage by Using a Metadata Model”, IEEE, 2014, retrieved online on Apr. 1, 2010, pp. 121 128. Retrieved from the Internet: URL: https://ieeeexplore.ieee.org/stamp/stampjsp? (Year: 2014).
- Iordanou et al, “Tracing Cross Border Web Tracking,” Oct. 31, 2018, pp. 329-342, ACM (Year: 2018).
- Islam, et al, “Mixture Model Based Label Association Techniques for Web Accessibility,” ACM, pp. 67-76 (Year: 2010).
- Jensen, et al, “Temporal Data Management,” IEEE Transactions on Knowledge and Data Engineering, vol. 11, No. 1, Jan./Feb. 1999, pp. 36-44 (Year: 1999).
- Joel Reardon et al., Secure Data Deletion from Persistent Media, ACM, Nov. 4, 2013, retrieved online on Jun. 13, 2019, pp. 271-283. Retrieved from the Internet: URL: http://delivery.acm.org/10.1145/2520000/2516699/p271-reardon.pdf? (Year: 2013).
- Joonbakhsh et al, “Mining and Extraction of Personal Software Process measures through IDE Interaction logs,” ACM/IEEE, 2018, retrieved online on Dec. 2, 2019, pp. 78-81. Retrieved from the Internet: URL: http://delivery.acm.org/10.1145/3200000/3196462/p78-joonbakhsh.pdf? (Year: 2018).
- Jun et al, “Scalable Multi-Access Flash Store for Big Data Analytics,” ACM, pp. 55-64 (Year: 2014).
- Kirkham, et al, “A Personal Data Store for an Internet of Subjects,” IEEE, pp. 92-97 (Year: 2011).
- Korba, Larry et al.; “Private Data Discovery for Privacy Compliance in Collaborative Environments”; Cooperative Design, Visualization, and Engineering; Springer Berlin Heidelberg; Sep. 21, 2008; pp. 142-150.
- Krol, Kat, et al, Control versus Effort in Privacy Warnings for Webforms, ACM, Oct. 24, 2016, pp. 13-23.
- Lamb et al, “Role-Based Access Control for Data Service Integration”, ACM, pp. 3-11 (Year: 2006).
- Leadbetter, et al, “Where Big Data Meets Linked Data: Applying Standard Data Models to Environmental Data Streams,” IEEE, pp. 2929-2937 (Year: 2016).
- Lebeau, Franck, et al, “Model-Based Vulnerability Testing for Web Applications,” 2013 IEEE Sixth International Conference on Software Testing, Verification and Validation Workshops, pp. 445-452, IEEE, 2013 (Year: 2013).
- Li, Ninghui, et al, t-Closeness: Privacy Beyond k-Anonymity and l-Diversity, IEEE, 2014, p. 106-115.
- Liu et al, “Cross-Geography Scientific Data Transferring Trends and Behavior,” ACM, pp. 267-278 (Year: 2018).
- Liu, Kun, et al, A Framework for Computing the Privacy Scores of Users in Online Social Networks, ACM Transactions an Knowledge Discovery from Data, vol. 5, No. 1, Article 6, Dec. 2010, 30 pages.
- Liu, Yandong, et al, “Finding the Right Consumer: Optimizing for Conversion in Display Advertising Campaigns,” Proceedings of the Fifth ACM International Conference on Web Search and Data Mining, Feb. 2, 2012, pp. 473-428 (Year: 2012).
- Lizar et al, “Usable Consents: Tracking and Managing Use of Personal Data with a Consent Transaction Receipt,” Proceedings of the 2014 ACM International Joint Conference on Pervasive and Ubiquitous Computing: Adjunct Publication, 2014, pp. 647-652 (Year: 2014).
- Luu, et al, “Combined Local and Holistic Facial Features for Age-Determination,” 2010 11th Int. Conf. Control, Automation, Robotics and Vision, Singapore, Dec. 7, 2010, IEEE, pp. 900-904 (Year: 2010).
- Ma Ziang, et al, “LibRadar: Fast and Accurate Detection of Third-Party Libraries in Android Apps,” 2016 IEEE/ACM 38th IEEE International Conference on Software Engineering Companion (ICSE-C), ACM, May 14, 2016, pp. 653-656, DOI: http://dx.doi.org/10.1145/2889160.2889178, p. 653, r.col, par. 1-3; figure 3 (Year: 2016).
- Mandal, et al, “Automated Age Prediction Using Wrinkles Features of Facial Images and Neural Network,” International Journal of Emerging Engineering Research and Technology, vol. 5, Issue 2, Feb. 2017, pp. 12-20 (Year: 2017).
- Maret et al, “Multimedia Information Interchange: Web Forms Meet Data Servers”, IEEE, pp. 499-505 (Year: 1999).
- Martin, et al, “Hidden Surveillance by Web Sites: Web Bugs in Contemporary Use,” Communications of the ACM, vol. 46, No. 12, Dec. 2003, pp. 258-264. Internet source https://doi.org/10.1145/953460.953509 (Year: 2003).
- McGarth et al, “Digital Library Technology for Locating and Accessing Scientific Data”, ACM, pp. 188-194 (Year: 1999).
- Mesbah et al, “Crawling Ajax-Based Web Applications Through Dynamic Analysis of User Interface State Changes,” ACM Transactions on the Web (TWEB) vol. 6, No. 1, Article 3, Mar. 2012, pp. 1-30 (Year: 2012).
- Moiso et al, “Towards a User-Centric Personal Data Ecosystem The Role of the Bank of Individual's Data,” 2012 16th International Conference on Intelligence in Next Generation Networks, Berlin, 2012, pp. 202-209 (Year: 2012).
- Moscoso-Zea et al, “Datawarehouse Design for Educational Data Mining,” IEEE, pp. 1-6 (Year: 2016).
- Mudepalli et al, “An efficient data retrieval approach using blowfish encryption on cloud CipherText Retrieval in Cloud Computing” IEEE, pp. 267-271 (Year: 2017).
- Mundada et al, “Half-Baked Cookies: Hardening Cookie-Based Authentication for the Modem Web,” Proceedings of the 11th ACM on Asia Conference on Computer and Communications Security, 2016, pp. 675-685 (Year: 2016).
- Newman et al, “High Speed Scientific Data Transfers using Software Defined Networking,” ACM, pp. 1-9 (Year: 2015).
- Newman, “Email Archive Overviews using Subject Indexes”, ACM, pp. 652-653, 2002 (Year: 2002).
- Nishikawa, Taiji, English Translation of JP 2019154505, Aug. 27, 2019 (Year: 2019).
- Notice of Filing Date for Petition for Post-Grant Review of related U.S. Pat. No. 9,691,090 dated Apr. 12, 2018.
- O'Keefe et al, “Privacy-Preserving Data Linkage Protocols,” Proceedings of the 2004 ACM Workshop on Privacy in the Electronic Society, 2004, pp. 94-102 (Year: 2004).
- Olenski, Steve, For Consumers, Data Is A Matter Of Trust, CMO Network, Apr. 18, 2016, https://www.forbes.com/sites/steveolenski/2016/04/18/for-consumers-data-is-a-matter-of-trust/#2e48496278b3.
- Pearson, et al, “A Model-Based Privacy Compliance Checker,” IJEBR, vol. 5, No. 2, pp. 63-83, 2009, Nov. 21, 2008. [Online]. Available: http://dx.doi.org/10.4018/jebr.2009040104 (Year: 2008).
- Pechenizkiy et al., “Process Mining Online Assessment Data,” Educational Data Mining, pp. 279-288 (Year: 2009).
- Petition for Post-Grant Review of related U.S. Pat. No. 9,691,090 dated Mar. 27, 2018.
- Petrie et al, “The Relationship between Accessibility and Usability of Websites”, ACM, pp. 397-406 (Year: 2007).
- Pfeifle, Sam, The Privacy Advisor, IAPP and AvePoint Launch New Free PIA Tool, International Association of Privacy Professionals, Mar. 5, 2014.
- Pfeifle, Sam, The Privacy Advisor, IAPP Heads to Singapore with APIA Template in Tow, International Association of Privacy Professionals, https://iapp.org/news/a/iapp-heads-to-singapore-with-apia-template_in_tow/, Mar. 28, 2014, p. 1-3.
- Ping et al, “Wide Area Placement of Data Replicas for Fast and Highly Available Data Access,” ACM, pp. 1-8 (Year: 2011).
- Popescu-Zeletin, “The Data Access and Transfer Support in a Local Heterogeneous Network (HMINET)”, IEEE, pp. 147-152 (Year: 1979).
- Porter, “De-ldentified Data and Third Party Data Mining: The Risk of Re-Identification of Personal Information,” Shidler JL Com. & Tech. 5, 2008, pp. 1-9 (Year: 2008).
- Pretorius, et al, “Attributing Users Based on Web Browser History,” 2017 IEEE Conference on Application, Information and Network Security (AINS), 2017, pp. 69-74 (Year: 2017).
- Qing-Jiang et al, “The (P, a, K) Anonymity Model for Privacy Protection of Personal Information in the Social Networks,” 2011 6th IEEE Joint International Information Technology and Artificial Intelligence Conference, vol. 2 IEEE, 2011, pp. 420-423 (Year: 2011).
- Qiu, et al, “Design and Application of Data Integration Platform Based on Web Services and XML,” IEEE, pp. 253-256 (Year: 2016).
- Radu, et al, “Analyzing Risk Evaluation Frameworks and Risk Assessment Methods,” IEEE, Dec. 12, 2020, pp. 1-6 (Year: 2020).
- Reardon et al., User-Level Secure Deletion on Log-Structured File Systems, ACM, 2012, retrieved online on Apr. 22, 2021, pp. 1-11. Retrieved from the Internet: URL: http://citeseerx.ist.psu.edu/viewdoc/download;isessionid=450713515DC7F19F8ED09AE961D4B60E. (Year: 2012).
- Carpineto et al, “Automatic Assessment of Website Compliance to the European Cookie Law with CooLCheck,” Proceedings of the 2016 ACM on Workshop on Privacy in the Electronic Society, 2016, pp. 135-138 (Year: 2016).
- Cerpzone, “How to Access Data on Data Archival Storage and Recovery System”, https://www.saj.usace.army.mil/Portals/44/docs/Environmental/Lake%20O%20Watershed/15February2017/How%20To%20Access%20Model%20Data%20on%20DASR.pdf?ver=2017-02-16-095535-633, Feb. 16, 2017.
- Cha et al, “A Data-Driven Security Risk Assessment Scheme for Personal Data Protection,” IEEE, pp. 50510-50517 (Year: 2018).
- Cha, et al, “Process-Oriented Approach for Validating Asset Value for Evaluating Information Security Risk,” IEEE, Aug. 31, 2009, pp. 379-385 (Year: 2009).
- Chapados et al, “Scoring Models for Insurance Risk Sharing Pool Optimization,” 2008, IEEE, pp. 97-105 (Year: 2008).
- Cheng, Raymond, et al, “Radiatus: A Shared-Nothing Server-Side Web Architecture,” Proceedings of the Seventh ACM Symposium on Cloud Computing, Oct. 5, 2016, pp. 237-250 (Year: 2016).
- Choi et al, “Retrieval Effectiveness of Table of Contents and Subject Headings,” ACM, pp. 103-104 (Year: 2007).
- Chowdhury et al, “A System Architecture for Subject-Centric Data Sharing”, ACM, pp. 1-10 (Year: 2018).
- Chowdhury et al, “Managing Data Transfers in Computer Clusters with Orchestra,” ACM, pp. 98-109 (Year: 2011).
- Decision Regarding Institution of Post-Grant Review in Case PGR2018-00056 for U.S. Pat. No. 9,691,090 B1, Oct. 11, 2018.
- Dimou et al, “Machine-Interpretable Dataset and Service Descriptions for Heterogeneous Data Access and Retrieval”, ACM, pp. 145-152 (Year: 2015).
- Dokholyan et al, “Regulatory and Ethical Considerations for Linking Clinical and Administrative Databases,” American Heart Journal 157.6 (2009), pp. 971-982 (Year: 2009).
- Dunkel et al, “Data Organization and Access for Efficient Data Mining”, IEEE, pp. 522-529 (Year: 1999).
- Emerson, et al, “A Data Mining Driven Risk Profiling Method for Road Asset Management,” ACM, pp. 1267-1275 (Year: 2013).
- Enck, William, et al, TaintDroid: An Information-Flow Tracking System for Realtime Privacy Monitoring on Smartphones, ACM Transactions on Computer Systems, vol. 32, No. 2, Article 5, Jun. 2014, p. 5:1-5:29.
- Everypixel Team, “A New Age Recognition API Detects the Age of People on Photos,” May 20, 2019, pp. 1-5 (Year: 2019).
- Falahrastegar, Marjan, et al, Tracking Personal Identifiers Across the Web, Medical Image Computing and Computer-Assisted Intervention—Miccai 2015, 18th International Conference, Oct. 5, 2015, Munich, Germany.
- Fan et al, “Intrusion Investigations with Data-hiding for Computer Log-file Forensics,” IEEE, pp. 1-6 (Year: 2010).
- Final Written Decision Regarding Post-Grant Review in Case PGR2018-00056 for U.S. Pat. No. 9,691,090 B1, dated Oct. 10, 2019.
- Francis, Andre, Business Mathematics and Statistics, South-Western Cengage Learning, 2008, Sixth Edition.
- Friedman et al., “Data Mining with Differential Privacy,” ACM, Jul. 2010, pp. 493-502 (Year: 2010).
- Friedman et al, “Informed Consent in the Mozilla Browser: Implementing Value-Sensitive Design,” Proceedings of the 35th Annual Hawaii International Conference on System Sciences, 2002, IEEE, pp. 1-10 (Year: 2002).
- Frikken, Keith B., et al, Yet Another Privacy Metric for Publishing Micro-data, Miami University, Oct. 27, 2008, p. 117-121.
- Fung et al, “Discover Information and Knowledge from Websites using an Integrated Summarization and Visualization Framework”, IEEE, pp. 232-235 (Year: 2010).
- Gajare et al, “Improved Automatic Feature Selection Approach for Health Risk Prediction,” Feb. 16, 2018, IEEE, pp. 816-819 (Year: 2018).
- Ghiglieri, Marco et al.; Personal DLP for Facebook, 2014 IEEE International Conference on Pervasive Computing and Communication Workshops (Percom Workshops); IEEE; Mar. 24, 2014; pp. 629-634.
- Gilda, et al, “Blockchain for Student Data Privacy and Consent,” 2018 International Conference on Computer Communication and Informatics, Jan. 4-6, 2018, IEEE, pp. 1-5 (Year: 2018).
- Golab, et al, “Issues in Data Stream Management,” ACM, SIGMOD Record, vol. 32, No. 2, Jun. 2003, pp. 5-14 (Year: 2003).
- Golfarelli et al, “Beyond Data Warehousing: What's Next in Business Intelligence?,” ACM, pp. 1-6 (Year: 2004).
- Gonçalves et al, “The XML Log Standard for Digital Libraries: Analysis, Evolution, and Deployment,” IEEE, pp. 312-314 (Year: 2003).
- Goni, Kyriaki, “Deletion Process_Only you can see my history: Investigating Digital Privacy, Digital Oblivion, and Control on Personal Data Through an Interactive Art Installation,” ACM, 2016, retrieved online on Oct. 3, 2019, pp. 324-333. Retrieved from the Internet URL: http://delivery.acm.org/10.1145/2920000/291.
- Gowadia et al, “RDF Metadata for XML Access Control,” ACM, pp. 31-48 (Year: 2003).
- Grolinger, et al, “Data Management in Cloud Environments: NoSQL and NewSQL Data Stores,” Journal of Cloud Computing: Advances, Systems and Applications, pp. 1-24 (Year: 2013).
- Guo, et al, “OPAL: A Passe-partout for Web Forms,” ACM, pp. 353-356 (Year: 2012).
- Gustarini, et al, “Evaluation of Challenges in Human Subject Studies “In-the-Wild” Using Subjects' Personal Smartphones,” ACM, pp. 1447-1456 (Year: 2013).
- Hacigümüs, Hakan, et al, Executing SQL over Encrypted Data in the Database-Service-Provider Model, ACM, Jun. 4, 2002, pp. 216-227.
- Halevy, et al, “Schema Mediation in Peer Data Management Systems,” IEEE, Proceedings of the 19th International Conference on Data Engineering, 2003, pp. 505-516 (Year: 2003).
- Hauch, et al, “Information Intelligence: Metadata for Information Discovery, Access, and Integration,” ACM, pp. 793-798 (Year: 2005).
- Hernandez, et al, “Data Exchange with Data-Metadata Translations,” ACM, pp. 260-273 (Year: 2008).
- Hinde, “A Model to Assess Organisational Information Privacy Maturity Against the Protection of Personal Information Act” Dissertation University of Cape Town 2014, pp. 1-121 (Year: 2014).
- Hodge, et al, “Managing Virtual Data Marts with Metapointer Tables,” pp. 1-7 (Year: 2002).
- Horrall et al, “Evaluating Risk: IBM's Country Financial Risk and Treasury Risk Scorecards,” Jul. 21, 2014, IBM, vol. 58, issue 4, pp. 2:1-2:9 (Year: 2014).
- Hu, et al, “Attribute Considerations for Access Control Systems,” NIST Special Publication 800-205, Jun. 2019, pp. 1-42 (Year: 2019).
- Hu, et al, “Guide to Attribute Based Access Control (ABAC) Definition and Considerations (Draft),” NIST Special Publication 800-162, pp. 1-54 (Year: 2013).
- Huang, et al, “A Study on Information Security Management with Personal Data Protection,” IEEE, Dec. 9, 2011, pp. 624-630 (Year: 2011).
- Huner et al, “Towards a Maturity Model for Corporate Data Quality Management”, ACM, pp. 231-238, 2009 (Year: 2009).
- Hunton & Williams LLP, The Role of Risk Management in Data Protection, Privacy Risk Framework and the Risk-based Approach to Privacy, Centre for Information Policy Leadership, Workshop II, Nov. 23, 2014.
- Huo et al, “A Cloud Storage Architecture Model for Data-lntensive Applications,” IEEE, pp. 1-4 (Year: 2011).
- IAPP, Daily Dashboard, PIA Tool Stocked With New Templates for DPI, Infosec, International Association of Privacy Professionals, Apr. 22, 2014.
- Regulation (EU) 2016/679, “On the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation),” Official Journal of the European Union, May 4, 2016, pp. L 119/1-L 119/88 (Year: 2016).
- Roesner et al, “Detecting and Defending Against Third-Party Tracking on the Web,” 9th USENIX Symposium on Networked Systems Design and Implementation, Apr. 11, 2013, pp. 1-14, ACM (Year: 2013).
- Rozepz, “What is Google Privacy Checkup? Everything You Need to Know,” Tom's Guide web post, Apr. 26, 2018, pp. 1-11 (Year: 2018).
- Salim et al, “Data Retrieval and Security using Lightweight Directory Access Protocol”, IEEE, pp. 685-688 (Year: 2009).
- Santhisree, et al, “Web Usage Data Clustering Using Dbscan Algorithm and Set Similarities,” IEEE, pp. 220-224 (Year: 2010).
- Sanzo et al, “Analytical Modeling of Lock-Based Concurrency Control with Arbitrary Transaction Data Access Patterns,” ACM, pp. 69-78 (Year: 2010).
- Schwartz, Edward J., et al, 2010 IEEE Symposium on Security and Privacy: All You Ever Wanted to Know About Dynamic Analysis and forward Symbolic Execution (but might have been afraid to ask), Carnegie Mellon University, IEEE Computer Society, 2010, p. 317-331.
- Sedinic et al., “Security Risk Management in Complex Organization,” May 29, 2015, IEEE, pp. 1331-1337 (Year: 2015).
- Singh, et al, “A Metadata Catalog Service for Data Intensive Applications,” ACM, pp. 1-17 (Year: 2003).
- Slezak, et al, “Brighthouse: An Analytic Data Warehouse for Ad-hoc Queries,” ACM, pp. 1337-1345 (Year: 2008).
- Soceanu, et al, “Managing the Privacy and Security of eHealth Data,” May 29, 2015, IEEE, pp. 1-8 (Year: 2015).
- Srinivasan et al, “Descriptive Data Analysis of File Transfer Data,” ACM, pp. 1-8 (Year: 2014).
- Srivastava, Agrima, et al, Measuring Privacy Leaks in Online Social Networks, International Conference on Advances in Computing, Communications and Informatics (ICACCI), 2013.
- Stack Overflow, “Is there a way to force a user to scroll to the bottom of a div?,” Stack Overflow, pp. 1-11, Nov. 2013. [Online], Available: https://stackoverflow.com/questions/2745935/is-there-a-way-to-force-a-user-to-scroll-to-the-bottom-of-a-div (Year: 2013).
- Stern, Joanna, “iPhone Privacy Is Broken . . . and Apps Are to Blame”, The Wall Street Journal, wsj.com, May 31, 2019.
- Strodl, et al, “Personal & SOHO Archiving,” Vienna University of Technology, Vienna, Austria, JCDL '08, Jun. 16-20, 2008, Pittsburgh, Pennsylvania, USA, pp. 115-123 (Year: 2008).
- Sukumar et al, “Review on Modern Data Preprocessing Techniques in Web Usage Mining (WUM),” IEEE, 2016, pp. 64-69 (Year: 2016).
- Symantec, Symantex Data Loss Prevention—Discover, monitor, and protect confidential data; 2008; Symantec Corporation; http://www.mssuk.com/images/Symantec%2014552315_IRC_BR_DLP_03.09_sngl.pdf.
- Tanasa et al, “Advanced Data Preprocessing for Intersites Web Usage Mining,” IEEE, Mar. 2004, pp. 59-65 (Year: 2004).
- Tanwar, et al, “Live Forensics Analysis: Violations of Business Security Policy,” 2014 International Conference on Contemporary Computing and Informatics (IC31), 2014, pp. 971-976 (Year: 2014).
- The Cookie Collective, Optanon Cookie Policy Generator, The Cookie Collective, Year 2016, http://web.archive.org/web/20160324062743/https:/optanon.com/.
- Thuraisingham, “Security Issues for the Semantic Web,” Proceedings 27th Annual International Computer Software and Applications Conference, COMPSAC 2003, Dallas, TX, USA, 2003, pp. 633-638 (Year: 2003).
- TRUSTe Announces General Availability of Assessment Manager for Enterprises to Streamline Data Privacy Management with Automation, PRNewswire, Mar. 4, 2015.
- Tsai et al, “Determinants of Intangible Assets Value: The Data Mining Approach,” Knowledge Based System, pp. 67-77 http://www.elsevier.com/locate/knosys (Year: 2012).
- Tuomas Aura et al., Scanning Electronic Documents for Personally Identifiable Information, ACM, Oct. 30, 2006, retrieved online on Jun. 13, 2019, pp. 41-49. Retrieved from the Internet: URL: http://delivery.acm.org/10.1145/1180000/1179608/p41-aura.pdf? (Year: 2006).
- Van Eijk et al, “The Impact of User Location on Cookie Notices (Inside and Outside of the European Union,” IEEE Security & Privacy Workshop on Technology and Consumer Protection (CONPRO '19), Jan. 1, 2019 (Year: 2019).
- Wang et al, “Revealing Key Non-Financial Factors for Online Credit-Scoring in E-Financing,” 2013, IEEE, pp. 1-6 (Year: 2013).
- Wang et al, “Secure and Efficient Access to Outsourced Data,” ACM, pp. 55-65 (Year: 2009).
- Weaver et al, “Understanding Information Preview in Mobile Email Processing”, ACM, pp. 303-312, 2011 (Year: 2011).
- Wu et al, “Data Mining with Big Data,” IEEE, Jan. 2014, pp. 97-107, vol. 26, No. 1, (Year: 2014).
- www.truste.com (1), 200150207, Internet Archive Wayback Machine, www.archive.org,2_7_2015.
- Xu, et al, “GatorShare: A File System Framework for High-Throughput Data Management,” ACM, pp. 776-786 (Year: 2010).
- Yang et al, “DAC-MACS: Effective Data Access Control for Multiauthority Cloud Storage Systems,” IEEE, pp. 1790-1801 (Year: 2013).
- Yang et al, “Mining Web Access Sequence with Improved Apriori Algorithm,” IEEE, 2017, pp. 780-784 (Year: 2017).
- Ye et al, “An Evolution-Based Cache Scheme for Scalable Mobile Data Access,” ACM, pp. 1-7 (Year: 2007).
- Yin et al, “Multibank Memory Optimization for Parallel Data Access in Multiple Data Arrays”, ACM, pp. 1-8 (Year: 2016).
- Yiu et al, “Outsourced Similarity Search on Metric Data Assets”, IEEE, pp. 338-352 (Year: 2012).
- Yu, “Using Data from Social Media Websites to Inspire the Design of Assistive Technology”, ACM, pp. 1-2 (Year: 2016).
- Yu, et al, “Performance and Fairness Issues in Big Data Transfers,” ACM, pp. 9-11 (Year: 2014).
- Zannone, et al, “Maintaining Privacy on Derived Objects,” ACM, pp. 10-19 (Year: 2005).
- Zhang et al, “Data Transfer Performance Issues for a Web Services Interface to Synchrotron Experiments”, ACM, pp. 59-65 (Year: 2007).
- Zhang et al, “Dynamic Topic Modeling for Monitoring Market Competition from Online Text and Image Data”, ACM, pp. 1425-1434 (Year: 2015).
- Zheng, et al, “Methodologies for Cross-Domain Data Fusion: An Overview,” IEEE, pp. 16-34 (Year: 2015).
- Zheng, et al, “Toward Assured Data Deletion in Cloud Storage,” IEEE, vol. 34, No. 3, pp. 101-107 May/Jun. 2020 (Year: 2020).
- Zhu, et al, “Dynamic Data Integration Using Web Services,” IEEE, pp. 1-8 (Year: 2004).
- Notice of Allowance, dated Jun. 11, 2021, from corresponding U.S. Appl. No. 16/862,948.
- Notice of Allowance, dated Jun. 11, 2021, from corresponding U.S. Appl. No. 16/862,952.
- Notice of Allowance, dated Jun. 11, 2021, from corresponding U.S. Appl. No. 17/216,436.
- Notice of Allowance, dated Jun. 12, 2019, from corresponding U.S. Appl. No. 16/278,123.
- Notice of Allowance, dated Jun. 12, 2019, from corresponding U.S. Appl. No. 16/363,454.
- Notice of Allowance, dated Jun. 16, 2020, from corresponding U.S. Appl. No. 16/798,818.
- Notice of Allowance, dated Jun. 17, 2020, from corresponding U.S. Appl. No. 16/656,895.
- Notice of Allowance, dated Jun. 18, 2019, from corresponding U.S. Appl. No. 16/410,566.
- Notice of Allowance, dated Jun. 19, 2018, from corresponding U.S. Appl. No. 15/894,890.
- Notice of Allowance, dated Jun. 19, 2019, from corresponding U.S. Appl. No. 16/042,673.
- Notice of Allowance, dated Jun. 19, 2019, from corresponding U.S. Appl. No. 16/055,984.
- Notice of Allowance, dated Jun. 2, 2021, from corresponding U.S. Appl. No. 17/198,581.
- Notice of Allowance, dated Jun. 21, 2019, from corresponding U.S. Appl. No. 16/404,439.
- Notice of Allowance, dated Jun. 22, 2020, from corresponding U.S. Appl. No. 16/791,337.
- Notice of Allowance, dated Jun. 27, 2018, from corresponding U.S. Appl. No. 15/882,989.
- Notice of Allowance, dated Jun. 4, 2019, from corresponding U.S. Appl. No. 16/159,566.
- Notice of Allowance, dated Jun. 5, 2019, from corresponding U.S. Appl. No. 16/220,899.
- Notice of Allowance, dated Jun. 5, 2019, from corresponding U.S. Appl. No. 16/357,260.
- Notice of Allowance, dated Jun. 6, 2018, from corresponding U.S. Appl. No. 15/875,570.
- Notice of Allowance, dated Jun. 6, 2019, from corresponding U.S. Appl. No. 16/159,628.
- Notice of Allowance, dated Jun. 7, 2021, from corresponding U.S. Appl. No. 17/099,270.
- Notice of Allowance, dated Jun. 8, 2020, from corresponding U.S. Appl. No. 16/712,104.
- Notice of Allowance, dated Mar. 1, 2018, from corresponding U.S. Appl. No. 15/853,674.
- Notice of Allowance, dated Mar. 1, 2019, from corresponding U.S. Appl. No. 16/059,911.
- Notice of Allowance, dated Mar. 10, 2021, from corresponding U.S. Appl. No. 16/925,628.
- Notice of Allowance, dated Mar. 10, 2021, from corresponding U.S. Appl. No. 17/128,666.
- Notice of Allowance, dated Mar. 13, 2019, from corresponding U.S. Appl. No. 16/055,083.
- Notice of Allowance, dated Mar. 14, 2019, from corresponding U.S. Appl. No. 16/055,944.
- Notice of Allowance, dated Mar. 16, 2020, from corresponding U.S. Appl. No. 16/778,704.
- Notice of Allowance, dated Mar. 16, 2021, from corresponding U.S. Appl. No. 17/149,380.
- Notice of Allowance, dated Mar. 17, 2020, from corresponding U.S. Appl. No. 16/560,885.
- Notice of Allowance, dated Mar. 18, 2020, from corresponding U.S. Appl. No. 16/560,963.
- Notice of Allowance, dated Mar. 19, 2021, from corresponding U.S. Appl. No. 17/013,757.
- Notice of Allowance, dated Mar. 2, 2018, from corresponding U.S. Appl. No. 15/858,802.
- Notice of Allowance, dated Mar. 24, 2020, from corresponding U.S. Appl. No. 16/552,758.
- Notice of Allowance, dated Mar. 25, 2019, from corresponding U.S. Appl. No. 16/054,780.
- Notice of Allowance, dated Mar. 26, 2020, from corresponding U.S. Appl. No. 16/560,889.
- Notice of Allowance, dated Mar. 26, 2020, from corresponding U.S. Appl. No. 16/578,712.
- Notice of Allowance, dated Mar. 27, 2019, from corresponding U.S. Appl. No. 16/226,280.
- Notice of Allowance, dated Mar. 29, 2019, from corresponding U.S. Appl. No. 16/055,998.
- Notice of Allowance, dated Mar. 31, 2020, from corresponding U.S. Appl. No. 16/563,744.
- Notice of Allowance, dated Mar. 31, 2021, from corresponding U.S. Appl. No. 17/013,758.
- Notice of Allowance, dated Mar. 31, 2021, from corresponding U.S. Appl. No. 17/162,205.
- Notice of Allowance, dated May 1, 2020, from corresponding U.S. Appl. No. 16/586,202.
- Notice of Allowance, dated May 11, 2020, from corresponding U.S. Appl. No. 16/786,196.
- Notice of Allowance, dated May 13, 2021, from corresponding U.S. Appl. No. 17/101,915.
- Notice of Allowance, dated May 19, 2020, from corresponding U.S. Appl. No. 16/505,430.
- Notice of Allowance, dated May 19, 2020, from corresponding U.S. Appl. No. 16/808,496.
- Notice of Allowance, dated May 20, 2020, from corresponding U.S. Appl. No. 16/707,762.
- Notice of Allowance, dated May 21, 2018, from corresponding U.S. Appl. No. 15/896,790.
- International Search Report, dated Feb. 11, 2022, from corresponding International Application No. PCT/US2021/053518.
- Jiahao Chen et al. “Fairness Under Unawareness: Assessing Disparity when Protected Class is Unobserved,” ARXIV.ORG, Cornell University Library, 201 Olin Library Cornell University, Ithaca, NY 14853, Nov. 27, 2018 (Nov. 27, 2018), Section 2, Figure 2. (Year 2018).
- Notice of Allowance, dated Feb. 1, 2022, from corresponding U.S. Appl. No. 17/346,509.
- Notice of Allowance, dated Feb. 14, 2022, from corresponding U.S. Appl. No. 16/623,157.
- Notice of Allowance, dated Feb. 22, 2022, from corresponding U.S. Appl. No. 17/535,065.
- Notice of Allowance, dated Feb. 4, 2022, from corresponding U.S. Appl. No. 17/520,272.
- Notice of Allowance, dated Feb. 8, 2022, from corresponding U.S. Appl. No. 17/342,153.
- Notice of Allowance, dated Jan. 31, 2022, from corresponding U.S. Appl. No. 17/472,948.
- Office Action, dated Feb. 16, 2022, from corresponding U.S. Appl. No. 16/872,031.
- Office Action, dated Feb. 9, 2022, from corresponding U.S. Appl. No. 17/543,546.
- Office Action, dated Jan. 31, 2022, from corresponding U.S. Appl. No. 17/493,290.
- Sarkar et al, “Towards Enforcement of the EU GDPR: Enabling Data Erasure,” 2018 IEEE Confs on Internet of Things, Green Computing and Communications, Cyber, Physical and Social Computing, Smart Data, Blockchain, Computer and Information Technology, Congress on Cybermatics, 2018, pp. 222-229, IEEE (Year: 2018).
- Written Opinion of the International Searching Authority, dated Feb. 11, 2022, from corresponding International Application No. PCT/US2021/053518.
- Notice of Allowance, dated May 26, 2021, from corresponding U.S. Appl. No. 16/808,493.
- Notice of Allowance, dated May 26, 2021, from corresponding U.S. Appl. No. 16/865,874.
- Notice of Allowance, dated May 26, 2021, from corresponding U.S. Appl. No. 17/199,514.
- Notice of Allowance, dated May 27, 2020, from corresponding U.S. Appl. No. 16/820,208.
- Notice of Allowance, dated May 27, 2021, from corresponding U.S. Appl. No. 16/927,658.
- Notice of Allowance, dated May 27, 2021, from corresponding U.S. Appl. No. 17/198,757.
- Notice of Allowance, dated May 28, 2019, from corresponding U.S. Appl. No. 16/277,568.
- Notice of Allowance, dated May 28, 2020, from corresponding U.S. Appl. No. 16/799,279.
- Notice of Allowance, dated May 28, 2021, from corresponding U.S. Appl. No. 16/862,944.
- Notice of Allowance, dated May 5, 2017, from corresponding U.S. Appl. No. 15/254,901.
- Notice of Allowance, dated May 5, 2020, from corresponding U.S. Appl. No. 16/563,754.
- Notice of Allowance, dated May 7, 2020, from corresponding U.S. Appl. No. 16/505,426.
- Notice of Allowance, dated May 7, 2021, from corresponding U.S. Appl. No. 17/194,662.
- Notice of Allowance, dated Nov. 14, 2019, from corresponding U.S. Appl. No. 16/436,616.
- Notice of Allowance, dated Nov. 16, 2021, from corresponding U.S. Appl. No. 17/491,871.
- Notice of Allowance, dated Nov. 2, 2018, from corresponding U.S. Appl. No. 16/054,762.
- Notice of Allowance, dated Nov. 22, 2021, from corresponding U.S. Appl. No. 17/383,889.
- Notice of Allowance, dated Nov. 23, 2020, from corresponding U.S. Appl. No. 16/791,589.
- Notice of Allowance, dated Nov. 24, 2020, from corresponding U.S. Appl. No. 17/027,019.
- Notice of Allowance, dated Nov. 25, 2020, from corresponding U.S. Appl. No. 17/019,771.
- Notice of Allowance, dated Nov. 26, 2019, from corresponding U.S. Appl. No. 16/563,735.
- Notice of Allowance, dated Nov. 27, 2019, from corresponding U.S. Appl. No. 16/570,712.
- Notice of Allowance, dated Nov. 27, 2019, from corresponding U.S. Appl. No. 16/577,634.
- Notice of Allowance, dated Nov. 3, 2020, from corresponding U.S. Appl. No. 16/719,071.
- Notice of Allowance, dated Nov. 5, 2019, from corresponding U.S. Appl. No. 16/560,965.
- Notice of Allowance, dated Nov. 7, 2017, from corresponding U.S. Appl. No. 15/671,073.
- Notice of Allowance, dated Nov. 8, 2018, from corresponding U.S. Appl. No. 16/042,642.
- Notice of Allowance, dated Nov. 9, 2020, from corresponding U.S. Appl. No. 16/595,342.
- Notice of Allowance, dated Oct. 1, 2021, from corresponding U.S. Appl. No. 17/340,395.
- Notice of Allowance, dated Oct. 10, 2019, from corresponding U.S. Appl. No. 16/277,539.
- Notice of Allowance, dated Oct. 17, 2018, from corresponding U.S. Appl. No. 15/896,790.
- Notice of Allowance, dated Oct. 17, 2018, from corresponding U.S. Appl. No. 16/054,672.
- Notice of Allowance, dated Oct. 17, 2019, from corresponding U.S. Appl. No. 16/563,741.
- Notice of Allowance, dated Oct. 21, 2019, from corresponding U.S. Appl. No. 16/404,405.
- Notice of Allowance, dated Oct. 21, 2020, from corresponding U.S. Appl. No. 16/834,812.
- Notice of Allowance, dated Oct. 22, 2021, from corresponding U.S. Appl. No. 17/346,847.
- Notice of Allowance, dated Oct. 3, 2019, from corresponding U.S. Appl. No. 16/511,700.
- Notice of Allowance, dated Sep. 1, 2021, from corresponding U.S. Appl. No. 17/196,570.
- Notice of Allowance, dated Sep. 1, 2021, from corresponding U.S. Appl. No. 17/222,556.
- Notice of Allowance, dated Sep. 12, 2019, from corresponding U.S. Appl. No. 16/512,011.
- Notice of Allowance, dated Sep. 13, 2018, from corresponding U.S. Appl. No. 15/894,809.
- Notice of Allowance, dated Sep. 13, 2018, from corresponding U.S. Appl. No. 15/894,890.
- Notice of Allowance, dated Sep. 14, 2021, from corresponding U.S. Appl. No. 16/808,497.
- Notice of Allowance, dated Sep. 16, 2020, from corresponding U.S. Appl. No. 16/915,097.
- Notice of Allowance, dated Sep. 17, 2020, from corresponding U.S. Appl. No. 16/863,226.
- Notice of Allowance, dated Sep. 18, 2018, from corresponding U.S. Appl. No. 15/894,819.
- Notice of Allowance, dated Sep. 18, 2018, from corresponding U.S. Appl. No. 16/041,545.
- Notice of Allowance, dated Sep. 18, 2020, from corresponding U.S. Appl. No. 16/812,795.
- Notice of Allowance, dated Sep. 23, 2020, from corresponding U.S. Appl. No. 16/811,793.
- Notice of Allowance, dated Sep. 23, 2021, from corresponding U.S. Appl. No. 17/068,454.
- Amar et al, “Privacy-Aware Infrastructure for Managing Personal Data,” ACM, pp. 571-572, Aug. 22-26, 2016 (Year: 2016).
- Banerjee et al, “Link Before You Share: Managing Privacy Policies through Blockchain,” IEEE, pp. 4438-4447 (Year: 2017).
- Civili et al, “Mastro Studio: Managing Ontology-Based Data Access Applications,” ACM, pp. 1314-1317, Aug. 26-30, 2013 (Year: 2013).
- Degeling et al, “We Value Your Privacy . . . Now Take Some Cookies: Measuring the GDPRs Impact on Web Privacy,” ARXIV.ORG, Cornell University Library, 201 Olin Library Cornell University, Ithaca, NY 14853, Aug. 15, 2018, pp. 1-15 (Year: 2019).
- Geko et al, “An Ontology Capturing the Interdependence of the General Data Protection Regulation (GDPR) and Information Security,” ACM, pp. 1-6, Nov. 15-16, 2018 (Year: 2018).
- International Search Report, dated Jan. 5, 2022, from corresponding International Application No. PCT/US2021/050497.
- Lu, “How Machine Learning Mitigates Racial Bias in the US Housing Market,” Available as SSRN 3489519, pp. 1-73, Nov. 2019 (Year: 2019).
- Notice of Allowance, dated Dec. 30, 2021, from corresponding U.S. Appl. No. 16/938,520.
- Notice of Allowance, dated Jan. 11, 2022, from corresponding U.S. Appl. No. 17/371,350.
- Notice of Allowance, dated Jan. 12, 2022, from corresponding U.S. Appl. No. 17/334,948.
- Notice of Allowance, dated Jan. 12, 2022, from corresponding U.S. Appl. No. 17/463,775.
- Notice of Allowance, dated Jan. 24, 2022, from corresponding U.S. Appl. No. 17/340,699.
- Notice of Allowance, dated Jan. 26, 2022, from corresponding U.S. Appl. No. 17/491,906.
- Notice of Allowance, dated Jan. 5, 2022, from corresponding U.S. Appl. No. 17/475,241.
- Notice of Allowance, dated Jan. 6, 2022, from corresponding U.S. Appl. No. 17/407,765.
- Notice of Allowance, dated Jan. 7, 2022, from corresponding U.S. Appl. No. 17/222,725.
- Office Action, dated Dec. 30, 2021, from corresponding U.S. Appl. No. 17/149,421.
- Office Action, dated Jan. 14, 2022, from corresponding U.S. Appl. No. 17/499,595.
- Office Action, dated Jan. 21, 2022, from corresponding U.S. Appl. No. 17/499,624.
- Office Action, dated Jan. 25, 2022, from corresponding U.S. Appl. No. 17/494,220.
- Office Action, dated Jan. 4, 2022, from corresponding U.S. Appl. No. 17/480,377.
- Office Action, dated Jan. 7, 2022, from corresponding U.S. Appl. No. 17/387,421.
- Rakers, “Managing Professional and Personal Sensitive Information,” ACM, pp. 9-13, Oct. 24-27, 2010 (Year: 2010).
- Sachinopoulou et al, “Ontology-Based Approach for Managing Personal Health and Wellness Information,” IEEE, pp. 1802-1805 (Year: 2007).
- Shankar et al., “Doppleganger: Better Browser Privacy Without the Bother,” Proceedings of the 13th ACM Conference on Computer and Communications Security; [ACM Conference on Computer and Communications Security], New York, NY: ACM, US, Oct. 30, 2006, pp. 154-167 (Year: 2006).
- Written Opinion of the International Searching Authority, dated Jan. 5, 2022, from corresponding International Application No. PCT/US2021/050497.
- Yue et al, “An Automatic HTTP Cookie Management System,” Computer Networks, Elsevier, Amsterdam, NL, vol. 54, No. 13, Sep. 15, 2010, pp. 2182-2198 (Year: 2010).
- Notice of Allowance, dated Apr. 2, 2019, from corresponding U.S. Appl. No. 16/160,577.
- Notice of Allowance, dated Apr. 2, 2021, from corresponding U.S. Appl. No. 17/162,006.
- Notice of Allowance, dated Apr. 22, 2021, from corresponding U.S. Appl. No. 17/163,701.
- Notice of Allowance, dated Apr. 25, 2018, from corresponding U.S. Appl. No. 15/883,041.
- Notice of Allowance, dated Apr. 28, 2021, from corresponding U.S. Appl. No. 17/135,445.
- Notice of Allowance, dated Apr. 28, 2021, from corresponding U.S. Appl. No. 17/181,828.
- Notice of Allowance, dated Apr. 29, 2020, from corresponding U.S. Appl. No. 16/700,049.
- Notice of Allowance, dated Apr. 30, 2020, from corresponding U.S. Appl. No. 16/565,265.
- Notice of Allowance, dated Apr. 30, 2020, from corresponding U.S. Appl. No. 16/820,346.
- Notice of Allowance, dated Apr. 30, 2021, from corresponding U.S. Appl. No. 16/410,762.
- Notice of Allowance, dated Apr. 8, 2019, from corresponding U.S. Appl. No. 16/228,250.
- Notice of Allowance, dated Apr. 8, 2020, from corresponding U.S. Appl. No. 16/791,348.
- Notice of Allowance, dated Apr. 9, 2020, from corresponding U.S. Appl. No. 16/791,075.
- Notice of Allowance, dated Aug. 10, 2020, from corresponding U.S. Appl. No. 16/671,444.
- Notice of Allowance, dated Aug. 10, 2020, from corresponding U.S. Appl. No. 16/788,633.
- Notice of Allowance, dated Aug. 12, 2020, from corresponding U.S. Appl. No. 16/719,488.
- Notice of Allowance, dated Aug. 12, 2021, from corresponding U.S. Appl. No. 16/881,832.
- Notice of Allowance, dated Aug. 14, 2018, from corresponding U.S. Appl. No. 15/989,416.
- Notice of Allowance, dated Aug. 18, 2017, from corresponding U.S. Appl. No. 15/619,455.
- Notice of Allowance, dated Aug. 20, 2019, from corresponding U.S. Appl. No. 16/241,710.
- Notice of Allowance, dated Aug. 24, 2018, from corresponding U.S. Appl. No. 15/619,479.
- Notice of Allowance, dated Aug. 26, 2019, from corresponding U.S. Appl. No. 16/443,374.
- Notice of Allowance, dated Aug. 26, 2020, from corresponding U.S. Appl. No. 16/808,503.
- Notice of Allowance, dated Aug. 28, 2019, from corresponding U.S. Appl. No. 16/278,120.
- Notice of Allowance, dated Aug. 30, 2018, from corresponding U.S. Appl. No. 15/996,208.
- Notice of Allowance, dated Aug. 31, 2021, from corresponding U.S. Appl. No. 17/326,901.
- Notice of Allowance, dated Aug. 4, 2021, from corresponding U.S. Appl. No. 16/895,278.
- Notice of Allowance, dated Aug. 7, 2020, from corresponding U.S. Appl. No. 16/901,973.
- Notice of Allowance, dated Aug. 9, 2018, from corresponding U.S. Appl. No. 15/882,989.
- Notice of Allowance, dated Aug. 9, 2021, from corresponding U.S. Appl. No. 16/881,699.
- Notice of Allowance, dated Dec. 10, 2018, from corresponding U.S. Appl. No. 16/105,602.
- Notice of Allowance, dated Dec. 11, 2019, from corresponding U.S. Appl. No. 16/278,122.
- Notice of Allowance, dated Dec. 11, 2019, from corresponding U.S. Appl. No. 16/593,634.
- Notice of Allowance, dated Dec. 12, 2017, from corresponding U.S. Appl. No. 15/169,643.
- Notice of Allowance, dated Dec. 12, 2017, from corresponding U.S. Appl. No. 15/619,212.
- Notice of Allowance, dated Dec. 12, 2017, from corresponding U.S. Appl. No. 15/619,382.
- Notice of Allowance, dated Dec. 13, 2019, from corresponding U.S. Appl. No. 16/512,033.
- Notice of Allowance, dated Dec. 15, 2020, from corresponding U.S. Appl. No. 16/989,086.
- Notice of Allowance, dated Dec. 16, 2019, from corresponding U.S. Appl. No. 16/505,461.
- Notice of Allowance, dated Dec. 17, 2020, from corresponding U.S. Appl. No. 17/034,772.
- Notice of Allowance, dated Dec. 18, 2019, from corresponding U.S. Appl. No. 16/659,437.
- Notice of Allowance, dated Dec. 23, 2019, from corresponding U.S. Appl. No. 16/656,835.
- Notice of Allowance, dated Dec. 23, 2020, from corresponding U.S. Appl. No. 17/068,557.
- Notice of Allowance, dated Dec. 3, 2019, from corresponding U.S. Appl. No. 16/563,749.
- Notice of Allowance, dated Dec. 31, 2018, from corresponding U.S. Appl. No. 16/159,634.
- Notice of Allowance, dated Dec. 31, 2019, from corresponding U.S. Appl. No. 16/404,399.
- Notice of Allowance, dated Dec. 4, 2019, from corresponding U.S. Appl. No. 16/594,670.
- Notice of Allowance, dated Dec. 5, 2017, from corresponding U.S. Appl. No. 15/633,703.
- Notice of Allowance, dated Dec. 6, 2017, from corresponding U.S. Appl. No. 15/619,451.
- Notice of Allowance, dated Dec. 6, 2017, from corresponding U.S. Appl. No. 15/619,459.
- Final Office Action, dated Apr. 1, 2022, from corresponding U.S. Appl. No. 17/370,650.
- Final Office Action, dated Apr. 5, 2022, from corresponding U.S. Appl. No. 17/013,756.
- International Search Report, dated Apr. 12, 2022, from corresponding International Application No. PCT/US2022/016735.
- International Search Report, dated Feb. 14, 2022, from corresponding International Application No. PCT/US2021/058274.
- International Search Report, dated Mar. 18, 2022, from corresponding International Application No. PCT/US2022/013733.
- Lewis, James et al., “Microservices,” Mar. 25, 2014 (Mar. 25, 2014),XP055907494, Retrieved from the Internet: https://martinfowler.com/articles/micr oservices.html [retrieved on Mar. 31, 2022].
- Notice of Allowance, dated Apr. 4, 2022, from corresponding U.S. Appl. No. 17/493,332.
- Notice of Allowance, dated Apr. 4, 2022, from corresponding U.S. Appl. No. 17/572,298.
- Notice of Allowance, dated Mar. 31, 2022, from corresponding U.S. Appl. No. 17/476,209.
- Office Action, dated Apr. 8, 2022, from corresponding U.S. Appl. No. 16/938,509.
- Restriction Requirement, dated Apr. 12, 2022, from corresponding U.S. Appl. No. 17/584,187.
- Written Opinion of the International Searching Authority, dated Apr. 12, 2022, from corresponding International Application No. PCT/US2022/016735.
- Written Opinion of the International Searching Authority, dated Feb. 14, 2022, from corresponding International Application No. PCT/US2021/058274.
- Written Opinion of the International Searching Authority, dated Mar. 18, 2022, from corresponding International Application No. PCT/US2022/013733.
- Ali et al, “Age Estimation from Facial Images Using Biometric Ratios and Wrinkle Analysis,” IEEE, 2015, pp. 1-5 (Year: 2015).
- Chang et al, “A Ranking Approach for Human Age Estimation Based on Face Images,” IEEE, 2010, pp. 3396-3399 (Year: 2010).
- Edinger et al, “Age and Gender Estimation of Unfiltered Faces,” IEEE, 2014, pp. 2170-2179 (Year: 2014).
- Final Office Action, dated Apr. 25, 2022, from corresponding U.S. Appl. No. 17/149,421.
- Han et al, “Demographic Estimation from Face Images: Human vs. Machine Performance,” IEEE, 2015, pp. 1148-1161 (Year: 2015).
- Huettner, “Digital Risk Management: Protecting Your Privacy, Improving Security, and Preparing for Emergencies,” IEEE, pp. 136-138 (Year: 2006).
- Jayasinghe et al, “Matching Facial Images Using Age Related Morphing Changes,” ISSRI, 2009, pp. 2901-2907 (Year: 2009).
- Khan et al, “Wrinkles Energy Based Age Estimation Using Discrete Cosine Transform,” IEEE, 2015, pp. 1-4 (Year 2015).
- Kristian et al, “Human Facial Age Classification Using Active Shape Module, Geometrical Feature, and Support Vendor Machine on Early Growth Stage,” ISICO, 2015, pp. 1-8 (Year: 2015).
- Liu et al, “Overview on Ontology Mapping and Approach,” IEEE, pp. 592-595 (Year: 2011).
- Milic et al, “Comparative Analysis of Metadata Models on e-Government Open Data Platforms,” IEEE, pp. 119-130 (Year: 2021).
- Notice of Allowance, dated Apr. 12, 2022, from corresponding U.S. Appl. No. 17/479,807.
- Notice of Allowance, dated Apr. 14, 2022, from corresponding U.S. Appl. No. 17/572,276.
- Notice of Allowance, dated Apr. 20, 2022, from corresponding U.S. Appl. No. 17/573,808.
- Notice of Allowance, dated Apr. 27, 2022, from corresponding U.S. Appl. No. 17/573,999.
- Notice of Allowance, dated Apr. 28, 2022, from corresponding U.S. Appl. No. 17/670,352.
- Office Action, dated Apr. 12, 2022, from corresponding U.S. Appl. No. 17/670,341.
- Office Action, dated Apr. 18, 2022, from corresponding U.S. Appl. No. 17/670,349.
- Office Action, dated Apr. 25, 2022, from corresponding U.S. Appl. No. 17/588,645.
- Office Action, dated Apr. 26, 2022, from corresponding U.S. Appl. No. 17/151,334.
- Qu et al., “Metadata Type System: Integrate Presentation, Data Models and Extraction to Enable Exploratory Browsing Interfaces,” ACM, pp. 107-116 (Year: 2014).
- Shulz et al., “Generative Data Models for Validation and Evaluation of Visualization Techniques,” ACM, pp. 1-13 (Year: 2016).
- Final Office Action, dated Apr. 28, 2022, from corresponding U.S. Appl. No. 16/925,550.
- Notice of Allowance, dated Apr. 28, 2022, from corresponding U.S. Appl. No. 17/592,922.
- Notice of Allowance, dated Apr. 29, 2022, from corresponding U.S. Appl. No. 17/387,421.
- Written Opinion of the International Searching Authority, dated Jan. 14, 2019, from corresponding International Application No. PCT/US2018/046949.
- Written Opinion of the International Searching Authority, dated Jan. 7, 2019, from corresponding International Application No. PCT/US2018/055772.
- Written Opinion of the International Searching Authority, dated Jun. 21, 2017, from corresponding International Application No. PCT/US2017/025600.
- Written Opinion of the International Searching Authority, dated Jun. 6, 2017, from corresponding International Application No. PCT/US2017/025605.
- Written Opinion of the International Searching Authority, dated Mar. 14, 2019, from corresponding International Application No. PCT/US2018/055736.
- Written Opinion of the International Searching Authority, dated Mar. 4, 2019, from corresponding International Application No. PCT/US2018/055773.
- Written Opinion of the International Searching Authority, dated Mar. 4, 2019, from corresponding International Application No. PCT/US2018/055774.
- Written Opinion of the International Searching Authority, dated Nov. 12, 2021, from corresponding International Application No. PCT/US2021/043481.
- Written Opinion of the International Searching Authority, dated Nov. 19, 2018, from corresponding International Application No. PCT/US2018/046939.
- Written Opinion of the International Searching Authority, dated Nov. 3, 2021, from corresponding International Application No. PCT/US2021/040893.
- Written Opinion of the International Searching Authority, dated Nov. 3, 2021, from corresponding International Application No. PCT/US2021/044910.
- Written Opinion of the International Searching Authority, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/043975.
- Written Opinion of the International Searching Authority, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/043976.
- Written Opinion of the International Searching Authority, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/043977.
- Written Opinion of the International Searching Authority, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/044026.
- Written Opinion of the International Searching Authority, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/045240.
- Written Opinion of the International Searching Authority, dated Oct. 12, 2017, from corresponding International Application No. PCT/US2017/036888.
- Written Opinion of the International Searching Authority, dated Oct. 12, 2018, from corresponding International Application No. PCT/US2018/044046.
- Written Opinion of the International Searching Authority, dated Oct. 16, 2018, from corresponding International Application No. PCT/US2018/045243.
- Written Opinion of the International Searching Authority, dated Oct. 18, 2018, from corresponding International Application No. PCT/US2018/045249.
- Written Opinion of the International Searching Authority, dated Oct. 20, 2017, from corresponding International Application No. PCT/US2017/036917.
- Written Opinion of the International Searching Authority, dated Oct. 3, 2017, from corresponding International Application No. PCT/US2017/036912.
- Written Opinion of the International Searching Authority, dated Sep. 1, 2017, from corresponding International Application No. PCT/US2017/036896.
- Written Opinion of the International Searching Authority, dated Sep. 12, 2018, from corresponding International Application No. PCT/US2018/037504.
- Written Opinion of the International Searching Authority, dated Sep. 15, 2021, from corresponding International Application No. PCT/US2021/033631.
- International Search Report, dated Aug. 15, 2017, from corresponding International Application No. PCT/US2017/036919.
- International Search Report, dated Aug. 21, 2017, from corresponding International Application No. PCT/US2017/036914.
- International Search Report, dated Aug. 29, 2017, from corresponding International Application No. PCT/US2017/036898.
- International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036889.
- International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036890.
- International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036893.
- International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036901.
- International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036913.
- International Search Report, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036920.
- International Search Report, dated Dec. 14, 2018, from corresponding International Application No. PCT/US2018/045296.
- International Search Report, dated Jan. 14, 2019, from corresponding International Application No. PCT/US2018/046949.
- International Search Report, dated Jan. 7, 2019, from corresponding International Application No. PCT/US2018/055772.
- International Search Report, dated Jun. 21, 2017, from corresponding International Application No. PCT/US2017/025600.
- International Search Report, dated Jun. 6, 2017, from corresponding International Application No. PCT/US2017/025605.
- International Search Report, dated Jun. 6, 2017, from corresponding International Application No. PCT/US2017/025611.
- International Search Report, dated Mar. 14, 2019, from corresponding International Application No. PCT/US2018/055736.
- International Search Report, dated Mar. 4, 2019, from corresponding International Application No. PCT/US2018/055773.
- International Search Report, dated Mar. 4, 2019, from corresponding International Application No. PCT/US2018/055774.
- International Search Report, dated Nov. 12, 2021, from corresponding International Application No. PCT/US2021/043481.
- International Search Report, dated Nov. 19, 2018, from corresponding International Application No. PCT/US2018/046939.
- International Search Report, dated Nov. 3, 2021, from corresponding International Application No. PCT/US2021/040893.
- International Search Report, dated Nov. 3, 2021, from corresponding International Application No. PCT/US2021/044910.
- International Search Report, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/043975.
- International Search Report, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/043976.
- International Search Report, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/043977.
- Final Office Action, dated Apr. 23, 2020, from corresponding U.S. Appl. No. 16/572,347.
- Final Office Action, dated Apr. 27, 2021, from corresponding U.S. Appl. No. 17/068,454.
- Final Office Action, dated Apr. 7, 2020, from corresponding U.S. Appl. No. 16/595,327.
- Final Office Action, dated Aug. 10, 2020, from corresponding U.S. Appl. No. 16/791,589.
- Final Office Action, dated Aug. 27, 2021, from corresponding U.S. Appl. No. 17/161,159.
- Final Office Action, dated Aug. 28, 2020, from corresponding U.S. Appl. No. 16/410,336.
- Final Office Action, dated Aug. 5, 2020, from corresponding U.S. Appl. No. 16/719,071.
- Final Office Action, dated Aug. 9, 2021, from corresponding U.S. Appl. No. 17/119,080.
- Final Office Action, dated Dec. 7, 2020, from corresponding U.S. Appl. No. 16/862,956.
- Final Office Action, dated Dec. 9, 2019, from corresponding U.S. Appl. No. 16/410,336.
- Final Office Action, dated Feb. 19, 2020, from corresponding U.S. Appl. No. 16/404,491.
- Final Office Action, dated Feb. 3, 2020, from corresponding U.S. Appl. No. 16/557,392.
- Final Office Action, dated Feb. 8, 2021, from corresponding U.S. Appl. No. 16/927,658.
- Final Office Action, dated Jan. 17, 2018, from corresponding U.S. Appl. No. 15/619,278.
- Final Office Action, dated Jan. 21, 2020, from corresponding U.S. Appl. No. 16/410,762.
- Final Office Action, dated Jan. 23, 2018, from corresponding U.S. Appl. No. 15/619,479.
- Final Office Action, dated Jan. 23, 2020, from corresponding U.S. Appl. No. 16/505,430.
- Final Office Action, dated Jul. 21, 2021, from corresponding U.S. Appl. No. 17/151,334.
- Final Office Action, dated Jul. 7, 2021, from corresponding U.S. Appl. No. 17/149,421.
- Final Office Action, dated Mar. 26, 2021, from corresponding U.S. Appl. No. 17/020,275.
- Final Office Action, dated Mar. 5, 2019, from corresponding U.S. Appl. No. 16/055,961.
- Final Office Action, dated Mar. 6, 2020, from corresponding U.S. Appl. No. 16/595,342.
- Final Office Action, dated May 14, 2021, from corresponding U.S. Appl. No. 17/013,756.
- Final Office Action, dated Nov. 29, 2017, from corresponding U.S. Appl. No. 15/619,237.
- Final Office Action, dated Oct. 26, 2021, from corresponding U.S. Appl. No. 17/306,496.
- Final Office Action, dated Oct. 28, 2021, from corresponding U.S. Appl. No. 17/234,205.
- Final Office Action, dated Oct. 29, 2021, from corresponding U.S. Appl. No. 17/020,275.
- Final Office Action, dated Sep. 17, 2021, from corresponding U.S. Appl. No. 17/200,698.
- Final Office Action, dated Sep. 21, 2020, from corresponding U.S. Appl. No. 16/808,493.
- Final Office Action, dated Sep. 21, 2020, from corresponding U.S. Appl. No. 16/862,944.
- Final Office Action, dated Sep. 22, 2020, from corresponding U.S. Appl. No. 16/808,497.
- Final Office Action, dated Sep. 23, 2020, from corresponding U.S. Appl. No. 16/862,948.
- Final Office Action, dated Sep. 24, 2020, from corresponding U.S. Appl. No. 16/862,952.
- Final Office Action, dated Sep. 25, 2019, from corresponding U.S. Appl. No. 16/278,119.
- Final Office Action, dated Sep. 28, 2020, from corresponding U.S. Appl. No. 16/565,395.
- Final Office Action, dated Sep. 8, 2020, from corresponding U.S. Appl. No. 16/410,866.
- Office Action, dated Apr. 1, 2021, from corresponding U.S. Appl. No. 17/119,080.
- Office Action, dated Apr. 15, 2021, from corresponding U.S. Appl. No. 17/161,159.
- Office Action, dated Apr. 18, 2018, from corresponding U.S. Appl. No. 15/894,819.
- Office Action, dated Apr. 2, 2021, from corresponding U.S. Appl. No. 17/151,334.
- Office Action, dated Apr. 20, 2020, from corresponding U.S. Appl. No. 16/812,795.
- Office Action, dated Apr. 22, 2019, from corresponding U.S. Appl. No. 16/241,710.
- Office Action, dated Apr. 22, 2020, from corresponding U.S. Appl. No. 16/811,793.
- Office Action, dated Apr. 28, 2020, from corresponding U.S. Appl. No. 16/798,818.
- Office Action, dated Apr. 28, 2020, from corresponding U.S. Appl. No. 16/808,500.
- Office Action, dated Apr. 28, 2021, from corresponding U.S. Appl. No. 16/808,497.
- Office Action, dated Apr. 29, 2020, from corresponding U.S. Appl. No. 16/791,337.
- Office Action, dated Apr. 5, 2019, from corresponding U.S. Appl. No. 16/278,119.
- Office Action, dated Apr. 7, 2020, from corresponding U.S. Appl. No. 16/788,633.
- Office Action, dated Apr. 7, 2020, from corresponding U.S. Appl. No. 16/791,589.
- Notice of Allowance, dated Dec. 7, 2020, from corresponding U.S. Appl. No. 16/817,136.
- Notice of Allowance, dated Dec. 9, 2019, from corresponding U.S. Appl. No. 16/565,261.
- Notice of Allowance, dated Dec. 9, 2020, from corresponding U.S. Appl. No. 16/404,491.
- Notice of Allowance, dated Feb. 10, 2020, from corresponding U.S. Appl. No. 16/552,765.
- Notice of Allowance, dated Feb. 11, 2021, from corresponding U.S. Appl. No. 17/086,732.
- Notice of Allowance, dated Feb. 12, 2020, from corresponding U.S. Appl. No. 16/572,182.
- Notice of Allowance, dated Feb. 13, 2019, from corresponding U.S. Appl. No. 16/041,563.
- Notice of Allowance, dated Feb. 14, 2019, from corresponding U.S. Appl. No. 16/226,272.
- Notice of Allowance, dated Feb. 19, 2019, from corresponding U.S. Appl. No. 16/159,632.
- Notice of Allowance, dated Feb. 19, 2021, from corresponding U.S. Appl. No. 16/832,451.
- Notice of Allowance, dated Feb. 24, 2021, from corresponding U.S. Appl. No. 17/034,355.
- Notice of Allowance, dated Feb. 24, 2021, from corresponding U.S. Appl. No. 17/068,198.
- Notice of Allowance, dated Feb. 24, 2021, from corresponding U.S. Appl. No. 17/101,106.
- Notice of Allowance, dated Feb. 24, 2021, from corresponding U.S. Appl. No. 17/101,253.
- Notice of Allowance, dated Feb. 25, 2020, from corresponding U.S. Appl. No. 16/714,355.
- Notice of Allowance, dated Feb. 25, 2021, from corresponding U.S. Appl. No. 17/106,469.
- Notice of Allowance, dated Feb. 26, 2021, from corresponding U.S. Appl. No. 17/139,650.
- Notice of Allowance, dated Feb. 27, 2019, from corresponding U.S. Appl. No. 16/041,468.
- Notice of Allowance, dated Feb. 27, 2019, from corresponding U.S. Appl. No. 16/226,290.
- Notice of Allowance, dated Feb. 3, 2021, from corresponding U.S. Appl. No. 16/827,039.
- Notice of Allowance, dated Feb. 3, 2021, from corresponding U.S. Appl. No. 17/068,558.
- Notice of Allowance, dated Jan. 1, 2021, from corresponding U.S. Appl. No. 17/026,727.
- Notice of Allowance, dated Jan. 14, 2020, from corresponding U.S. Appl. No. 16/277,715.
- Notice of Allowance, dated Jan. 15, 2021, from corresponding U.S. Appl. No. 17/030,714.
- Notice of Allowance, dated Jan. 18, 2018, from corresponding U.S. Appl. No. 15/619,478.
- Notice of Allowance, dated Jan. 18, 2019 from corresponding U.S. Appl. No. 16/159,635.
- Notice of Allowance, dated Jan. 2, 2020, from corresponding U.S. Appl. No. 16/410,296.
- Notice of Allowance, dated Jan. 23, 2018, from corresponding U.S. Appl. No. 15/619,251.
- Notice of Allowance, dated Jan. 25, 2021, from corresponding U.S. Appl. No. 16/410,336.
- Notice of Allowance, dated Jan. 26, 2018, from corresponding U.S. Appl. No. 15/619,469.
- Notice of Allowance, dated Jan. 29, 2020, from corresponding U.S. Appl. No. 16/278,119.
- Notice of Allowance, dated Jan. 6, 2021, from corresponding U.S. Appl. No. 16/595,327.
- Notice of Allowance, dated Jan. 8, 2020, from corresponding U.S. Appl. No. 16/600,879.
- Notice of Allowance, dated Jul. 10, 2019, from corresponding U.S. Appl. No. 16/237,083.
- Notice of Allowance, dated Jul. 10, 2019, from corresponding U.S. Appl. No. 16/403,358.
- Notice of Allowance, dated Jul. 12, 2019, from corresponding U.S. Appl. No. 16/278,121.
- Notice of Allowance, dated Jul. 14, 2020, from corresponding U.S. Appl. No. 16/701,043.
- Notice of Allowance, dated Jul. 15, 2020, from corresponding U.S. Appl. No. 16/791,006.
- Notice of Allowance, dated Jul. 16, 2020, from corresponding U.S. Appl. No. 16/901,979.
- Notice of Allowance, dated Jul. 17, 2019, from corresponding U.S. Appl. No. 16/055,961.
- Notice of Allowance, dated Jul. 17, 2020, from corresponding U.S. Appl. No. 16/778,709.
- Notice of Allowance, dated Jul. 19, 2021, from corresponding U.S. Appl. No. 17/306,252.
- Notice of Allowance, dated Jul. 21, 2020, from corresponding U.S. Appl. No. 16/557,392.
- Notice of Allowance, dated Jul. 23, 2019, from corresponding U.S. Appl. No. 16/220,978.
- Notice of Allowance, dated Jul. 26, 2019, from corresponding U.S. Appl. No. 16/409,673.
- Notice of Allowance, dated Jul. 26, 2021, from corresponding U.S. Appl. No. 17/151,399.
- Notice of Allowance, dated Jul. 26, 2021, from corresponding U.S. Appl. No. 17/207,316.
- Notice of Allowance, dated Jul. 31, 2019, from corresponding U.S. Appl. No. 16/221,153.
- Notice of Allowance, dated Jul. 8, 2021, from corresponding U.S. Appl. No. 17/201,040.
- Notice of Allowance, dated Jun. 1, 2020, from corresponding U.S. Appl. No. 16/813,321.
- Bansal et al, “Integrating Big Data: A Semantic Extract-Transform-Load Framework,” IEEE, pp. 42-50 (Year: 2015).
- Bao et al, “Performance Modeling and Workflow Scheduling of Microservice-Based Applications in Clouds,” IEEE Transactions on Parallel and Distributed Systems, vol. 30, No. 9, Sep. 2019, pp. 2101-2116 (Year: 2019).
- Bindschaedler et al, “Privacy Through Fake Yet Semantically Real Traces,” ARXIV.ORG, Cornell University Library, 201 Olin Library Cornell University Ithaca, NY 14853, May 27, 2015 (Year: 2015).
- Castro et al, “Creating Lightweight Ontologies for Dataset Description,” IEEE, pp. 1-4 (Year: 2014).
- Ex Parte Quayle Action, dated May 10, 2022, from corresponding U.S. Appl. No. 17/668,714.
- Final Office Action, dated May 12, 2022, from corresponding U.S. Appl. No. 17/499,624.
- Final Office Action, dated May 16, 2022, from corresponding U.S. Appl. No. 17/480,377.
- Final Office Action, dated May 2, 2022, from corresponding U.S. Appl. No. 17/499,595.
- Final Office Action, dated May 24, 2022, from corresponding U.S. Appl. No. 17/499,582.
- International Search Report, dated May 12, 2022, from corresponding International Application No. PCT/US2022/015929.
- International Search Report, dated May 17, 2022, from corresponding International Application No. PCT/US2022/015241.
- International Search Report, dated May 19, 2022, from corresponding International Application No. PCT/US2022/015637.
- Lasierra et al, “Data Management in Home Scenarios Using an Autonomic Ontology-Based Approach,” IEEE, pp. 94-99 (Year: 2012).
- Lenzerini et al, “Ontology-based Data Management,” ACM, pp. 5-6 (Year: 2011).
- Niu, et al, “Achieving Data Truthfulness and Privacy Preservation in Data Markets”, IEEE Transactions on Knowledge and Data Engineering, IEEE Service Centre, Los Alamitos, CA, US, vol. 31, No. 1, Jan. 1, 2019, pp. 105-119 (Year 2019).
- Notice of Allowance, dated May 11, 2022, from corresponding U.S. Appl. No. 17/395,759.
- Notice of Allowance, dated May 18, 2022, from corresponding U.S. Appl. No. 17/670,354.
- Notice of Allowance, dated May 25, 2022, from corresponding U.S. Appl. No. 16/872,031.
- Notice of Allowance, dated May 6, 2022, from corresponding U.S. Appl. No. 17/666,886.
- Office Action, dated May 12, 2022, from corresponding U.S. Appl. No. 17/509,974.
- Office Action, dated May 16, 2022, from corresponding U.S. Appl. No. 17/679,750.
- Office Action, dated May 24, 2022, from corresponding U.S. Appl. No. 17/674,187.
- Office Action, dated May 9, 2022, from corresponding U.S. Appl. No. 16/840,943.
- Preuveneers et al, “Access Control with Delegated Authorization Policy Evaluation for Data-Driven Microservice Workflows,” Future Internet 2017, MDPI, pp. 1-21 (Year: 2017).
- Thomas et al, “MooM—A Prototype Framework for Management of Ontology Mappings,” IEEE, pp. 548-555 (Year: 2011).
- Written Opinion of the International Searching Authority, dated May 12, 2022, from corresponding International Application No. PCT/US2022/015929.
- Written Opinion of the International Searching Authority, dated May 17, 2022, from corresponding International Application No. PCT/US2022/015241.
- Written Opinion of the International Searching Authority, dated May 19, 2022, from corresponding International Application No. PCT/US2022/015637.
- International Search Report, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/044026.
- International Search Report, dated Oct. 11, 2018, from corresponding International Application No. PCT/US2018/045240.
- International Search Report, dated Oct. 12, 2017, from corresponding International Application No. PCT/US2017/036888.
- International Search Report, dated Oct. 12, 2018, from corresponding International Application No. PCT/US2018/044046.
- International Search Report, dated Oct. 16, 2018, from corresponding International Application No. PCT/US2018/045243.
- International Search Report, dated Oct. 18, 2018, from corresponding International Application No. PCT/US2018/045249.
- International Search Report, dated Oct. 20, 2017, from corresponding International Application No. PCT/US2017/036917.
- International Search Report, dated Oct. 3, 2017, from corresponding International Application No. PCT/US2017/036912.
- International Search Report, dated Sep. 1, 2017, from corresponding International Application No. PCT/US2017/036896.
- International Search Report, dated Sep. 12, 2018, from corresponding International Application No. PCT/US2018/037504.
- International Search Report, dated Sep. 15, 2021, from corresponding International Application No. PCT/US2021/033631.
- Invitation to Pay Additional Search Fees, dated Aug. 10, 2017, from corresponding International Application No. PCT/US2017/036912.
- Invitation to Pay Additional Search Fees, dated Aug. 10, 2017, from corresponding International Application No. PCT/US2017/036917.
- Invitation to Pay Additional Search Fees, dated Aug. 24, 2017, from corresponding International Application No. PCT/US2017/036888.
- Invitation to Pay Additional Search Fees, dated Jan. 18, 2019, from corresponding International Application No. PCT/US2018/055736.
- Invitation to Pay Additional Search Fees, dated Jan. 7, 2019, from corresponding International Application No. PCT/US2018/055773.
- Invitation to Pay Additional Search Fees, dated Jan. 8, 2019, from corresponding International Application No. PCT/US2018/055774.
- Invitation to Pay Additional Search Fees, dated Oct. 23, 2018, from corresponding International Application No. PCT/US2018/045296.
- Abdullah et al, “The Mapping Process of Unstructured Data to the Structured Data”, ACM, pp. 151-155 (Yean 2013).
- Acar, Gunes, et al, The Web Never Forgets, Computerand Communications Security, ACM, Nov. 3, 2014, pp. 674-689.
- Aghasian, Erfan, et al, Scoring Users' Privacy Disclosure Across Multiple Online Social Networks,IEEE Access, Multidisciplinary Rapid Review Open Access Journal, Jul. 31, 2017, vol. 5, 2017.
- Agosti et al, “Access and Exchange of Hierarchically Structured Resources on the Web with the NESTOR Framework”, IEEE, pp. 659-662 (Year: 2009).
- Agrawal et al, “Securing Electronic Health Records Without Impeding the Flow of Information,” International Journal of Medical Informatics 76, 2007, pp. 471-479 (Year: 2007).
- Ahmad et al, “Task-Oriented Access Model for Secure Data Sharing Over Cloud,” ACM, pp. 1-7 (Year: 2015).
- Ahmad, et al, “Performance of Resource Management Algorithms for Processable Bulk Data Transfer Tasks in Grid Environments,” ACM, pp. 177-188 (Year: 2008).
- Alaa et al, “Personalized Risk Scoring for Critical Care Prognosis Using Mixtures of Gaussian Processes,” Apr. 27, 2017, IEEE, vol. 65, issue 1, pp. 207-217 (Year: 2017).
- Aman et al, “Detecting Data Tampering Attacks in Synchrophasor Networks using Time Hopping,” IEEE, pp. 1-6 (Year: 2016).
- Antunes et al, “Preserving Digital Data in Heterogeneous Environments”, ACM, pp. 345-348, 2009 (Year: 2009).
- Ardagna, et al, “A Privacy-Aware Access Control System,” Journal of Computer Security, 16:4, pp. 369-397 (Year: 2008).
- Avepoint, AvePoint Privacy Impact Assessemtn 1: User Guide, Cumulative Update 2, Revision E, Feb. 2014, AvePoint, Inc.
- Ball, et al, “Aspects of the Computer-Based Patient Record,” Computers in Healthcare, Springer-Verlag New York Inc., pp. 1-23 (Year: 1992).
- Bang et al, “Building an Effective and Efficient Continuous Web Application Security Program,” 2016 International Conference on Cyber Security Situational Awareness, Data Analytics and Assessment (CyberSA), London, 2016, pp. 1-4 (Year: 2016).
- Barker, “Personalizing Access Control by Generalizing Access Control,” ACM, pp. 149-158 (Year: 2010).
- Barr, “Amazon Rekognition Update—Estimated Age Range for Faces,” AWS News Blog, Feb. 10, 2017, pp. 1-5 (Year: 2017).
- Bayardo et al, “Technological Solutions for Protecting Privacy,” Computer 36.9 (2003), pp. 115-118, (Year: 2003).
- Berezovskiy et al, “A framework for dynamic data source identification and orchestration on the Web”, ACM, pp. 1-8 (Year: 2010).
- Bertino et al, “On Specifying Security Policies for Web Documents with an XML-based Language,” ACM, pp. 57-65 (Year: 2001).
- Bertino et al, “Towards Mechanisms for Detection and Prevention of Data Exfiltration by Insiders,” Mar. 22, 2011, ACM, pp. 10-19 (Year: 2011).
- Bhargav-Spantzel et al, Receipt Management—Transaction History based Trust Establishment, 2007, ACM, p. 82-91.
- Bhuvaneswaran et al, “Redundant Parallel Data Transfer Schemes for the Grid Environment”, ACM, pp. 18 (Year: 2006).
- Bieker, et al, “Privacy-Preserving Authentication Solutions—Best Practices for Implementation and EU Regulatory Perspectives,” Oct. 29, 2014, IEEE, pp. 1-10 (Year: 2014).
- Bin, et al, “Research on Data Mining Models for the Internet of Things,” IEEE, pp. 1-6 (Year: 2010).
- Binns, et al, “Data Havens, or Privacy Sans Frontiéres? A Study of International Personal Data Transfers,” ACM, pp. 273-274 (Year: 2002).
- Borgida, “Description Logics in Data Management,” IEEE Transactions on Knowledge and Data Engineering, vol. 7, No. 5, Oct. 1995, pp. 671-682 (Year: 1995).
- Brandt et al, “Efficient Metadata Management in Large Distributed Storage Systems,” IEEE, pp. 1-9 (Year: 2003).
- Bujlow et al, “Web Tracking: Mechanisms, Implications, and Defenses,” Proceedings of the IEEE, Aug. 1, 2017, vol. 5, No. 8, pp. 1476-1510 (Year: 2017).
- Byun, Ji-Won, Elisa Bertino, and Ninghui Li. “Purpose based access control of complex data for privacy protection.” Proceedings of the tenth ACM symposium on Access control models and technologies. ACM, 2005. (Year: 2005).
- Carminati et al, “Enforcing Access Control Over Data Streams,” ACM, pp. 21-30 (Year: 2007).
- Notice of Allowance, dated Oct. 18, 2022, from corresponding U.S. Appl. No. 16/840,943.
- Office Action, dated Sep. 16, 2022, from corresponding U.S. Appl. No. 17/306,438.
- Notice of Allowance, dated Sep. 24, 2021, from corresponding U.S. Appl. No. 17/334,939.
- Notice of Allowance, dated Sep. 25, 2020, from corresponding U.S. Appl. No. 16/983,536.
- Notice of Allowance, dated Sep. 27, 2017, from corresponding U.S. Appl. No. 15/626,052.
- Notice of Allowance, dated Sep. 27, 2021, from corresponding U.S. Appl. No. 17/222,523.
- Notice of Allowance, dated Sep. 28, 2018, from corresponding U.S. Appl. No. 16/041,520.
- Notice of Allowance, dated Sep. 29, 2021, from corresponding U.S. Appl. No. 17/316,179.
- Notice of Allowance, dated Sep. 4, 2018, from corresponding U.S. Appl. No. 15/883,041.
- Notice of Allowance, dated Sep. 4, 2020, from corresponding U.S. Appl. No. 16/808,500.
- Notice of Allowance, dated Sep. 4, 2020, from corresponding U.S. Appl. No. 16/901,662.
- Notice of Allowance, dated Sep. 9, 2021, from corresponding U.S. Appl. No. 17/334,909.
- Restriction Requirement, dated Apr. 10, 2019, from corresponding U.S. Appl. No. 16/277,715.
- Restriction Requirement, dated Apr. 13, 2020, from corresponding U.S. Appl. No. 16/817,136.
- Restriction Requirement, dated Apr. 24, 2019, from corresponding U.S. Appl. No. 16/278,122.
- Restriction Requirement, dated Aug. 7, 2019, from corresponding U.S. Appl. No. 16/410,866.
- Restriction Requirement, dated Aug. 9, 2019, from corresponding U.S. Appl. No. 16/404,399.
- Restriction Requirement, dated Dec. 31, 2018, from corresponding U.S. Appl. No. 15/169,668.
- Restriction Requirement, dated Dec. 9, 2019, from corresponding U.S. Appl. No. 16/565,395.
- Restriction Requirement, dated Jan. 18, 2017, from corresponding U.S. Appl. No. 15/256,430.
- Restriction Requirement, dated Jul. 28, 2017, from corresponding U.S. Appl. No. 15/169,658.
- Restriction Requirement, dated Jun. 15, 2021, from corresponding U.S. Appl. No. 17/187,329.
- Restriction Requirement, dated Jun. 15, 2021, from corresponding U.S. Appl. No. 17/222,556.
- Restriction Requirement, dated Jun. 9, 2021, from corresponding U.S. Appl. No. 17/222,725.
- Restriction Requirement, dated May 5, 2020, from corresponding U.S. Appl. No. 16/808,489.
- Restriction Requirement, dated Nov. 10, 2021, from corresponding U.S. Appl. No. 17/366,754.
- Restriction Requirement, dated Nov. 15, 2019, from corresponding U.S. Appl. No. 16/586,202.
- Restriction Requirement, dated Nov. 21, 2016, from corresponding U.S. Appl. No. 15/254,901.
- Restriction Requirement, dated Nov. 5, 2019, from corresponding U.S. Appl. No. 16/563,744.
- Restriction Requirement, dated Oct. 17, 2018, from corresponding U.S. Appl. No. 16/055,984.
- Restriction Requirement, dated Oct. 6, 2021, from corresponding U.S. Appl. No. 17/340,699.
- Restriction Requirement, dated Sep. 15, 2020, from corresponding U.S. Appl. No. 16/925,628.
- Restriction Requirement, dated Sep. 9, 2019, from corresponding U.S. Appl. No. 16/505,426.
- Advisory Action, dated Jan. 13, 2021, from corresponding U.S. Appl. No. 16/808,493.
- Advisory Action, dated Jan. 13, 2021, from corresponding U.S. Appl. No. 16/862,944.
- Advisory Action, dated Jan. 13, 2021, from corresponding U.S. Appl. No. 16/862,948.
- Advisory Action, dated Jan. 13, 2021, from corresponding U.S. Appl. No. 16/862,952.
- Advisory Action, dated Jan. 6, 2021, from corresponding U.S. Appl. No. 16/808,497.
- Advisory Action, dated Jun. 19, 2020, from corresponding U.S. Appl. No. 16/595,342.
- Advisory Action, dated Jun. 2, 2020, from corresponding U.S. Appl. No. 16/404,491.
- Advisory Action, dated May 21, 2020, from corresponding U.S. Appl. No. 16/557,392.
- Written Opinion of the International Searching Authority, dated Jun. 6, 2017, from corresponding International Application No. PCT/US2017/025611.
- Written Opinion of the International Searching Authority, dated Aug. 15, 2017, from corresponding International Application No. PCT/US2017/036919.
- Written Opinion of the International Searching Authority, dated Aug. 21, 2017, from corresponding International Application No. PCT/US2017/036914.
- Written Opinion of the International Searching Authority, dated Aug. 29, 2017, from corresponding International Application No. PCT/US2017/036898.
- Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036889.
- Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036890.
- Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036893.
- Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036901.
- Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036913.
- Written Opinion of the International Searching Authority, dated Aug. 8, 2017, from corresponding International Application No. PCT/US2017/036920.
- Written Opinion of the International Searching Authority, dated Dec. 14, 2018, from corresponding International Application No. PCT/US2018/045296.
- Choi et al, “A Survey on Ontology Mapping,” ACM, pp. 34-41 (Year: 2006).
- Cui et al, “Domain Ontology Management Environment,” IEEE, pp. 1-9 (Year: 2000).
- Falbo et al, “An Ontological Approach to Domain Engineering,” ACM, pp. 351-358 (Year: 2002).
- Final Office Action, dated Jun. 10, 2022, from corresponding U.S. Appl. No. 17/161,159.
- Final Office Action, dated Jun. 9, 2022, from corresponding U.S. Appl. No. 17/494,220.
- International Search Report, dated Jun. 1, 2022, from corresponding International Application No. PCT/US2022/016930.
- International Search Report, dated Jun. 22, 2022, from corresponding International Application No. PCT/US2022/019358.
- International Search Report, dated Jun. 24, 2022, from corresponding International Application No. PCT/US2022/019882.
- Nemec et al, “Assessment of Query Execution Performance Using Selected Business Intelligence Tools and Experimental Agile Oriented Data Modeling Approach,” Sep. 16, 2015, IEEE, pp. 1327-1333. (Year: 2015).
- Notice of Allowance, dated Jun. 14, 2022, from corresponding U.S. Appl. No. 17/679,734.
- Notice of Allowance, dated Jun. 16, 2022, from corresponding U.S. Appl. No. 17/119,080.
- Notice of Allowance, dated Jun. 2, 2022, from corresponding U.S. Appl. No. 17/493,290.
- Notice of Allowance, dated Jun. 23, 2022, from corresponding U.S. Appl. No. 17/588,645.
- Notice of Allowance, dated Jun. 8, 2022, from corresponding U.S. Appl. No. 17/722,551.
- Notice of Allowance, dated May 27, 2022, from corresponding U.S. Appl. No. 17/543,546.
- Notice of Allowance, dated May 31, 2022, from corresponding U.S. Appl. No. 17/679,715.
- Office Action, dated Jun. 1, 2022, from corresponding U.S. Appl. No. 17/306,496.
- Office Action, dated Jun. 14, 2022, from corresponding U.S. Appl. No. 17/346,586.
- Office Action, dated Jun. 16, 2022, from corresponding U.S. Appl. No. 17/689,683.
- Ozdikis et al, “Tool Support for Transformation from an OWL Ontology to an HLA Object Model,” ACM, pp. 1-6 (Year: 2010).
- Vukovic et al., “Managing Enterprise IT Systems Using Online Communities,” Jul. 9, 2011, IEEE, pp. 552-559. (Year: 2011).
- Wong et al, “Ontology Mapping for the Interoperability Problem in Network Management,” IEEE, pp. 2058-2068 (Year: 2005).
- Written Opinion of the International Searching Authority, dated Jun. 1, 2022, from corresponding International Application No. PCT/US2072/016930.
- Written Opinion of the International Searching Authority, dated Jun. 22, 2022, from corresponding International Application No. PCT/US2022/019358.
- Written Opinion of the International Searching Authority, dated Jun. 24, 2022, from corresponding International Application No. PCT/US2022/019882.
- Final Office Action, dated Sep. 19, 2022, from corresponding U.S. Appl. No. 17/306,496.
- Notice of Allowance, dated Aug. 22, 2022, from corresponding U.S. Appl. No. 17/499,595.
- Notice of Allowance, dated Sep. 12, 2022, from corresponding U.S. Appl. No. 17/674,187.
- Notice of Allowance, dated Sep. 2, 2022, from corresponding U.S. Appl. No. 17/380,485.
- Office Action, dated Jul. 28, 2022, from corresponding U.S. Appl. No. 16/925,550.
- Office Action, dated Jul. 7, 2022, from corresponding U.S. Appl. No. 17/370,650.
- Office Action, dated Sep. 2, 2022, from corresponding U.S. Appl. No. 17/499,624.
- Bjorn Greif, “Cookie Pop-up Blocker: Cliqz Automatically Denies Consent Requests,” Cliqz.com, pp. 1-9, Aug. 11, 2019 (Year: 2019).
- Final Office Action, dated Dec. 10, 2021, from corresponding U.S. Appl. No. 17/187,329.
- He et al, “A Crowdsourcing Framework for Detecting of Cross-Browser Issues in Web Application,” ACM, pp. 1-4, Nov. 6, 2015 (Year: 2015).
- International Search Report, dated Dec. 22, 2021, from corresponding International Application No. PCT/US2021/051217.
- Jones et al, “Al and the Ethics of Automating Consent,” IEEE, pp. 64-72, May 2018 (Year: 2018).
- Liu et al, “A Novel Approach for Detecting Browser-based Silent Miner,” IEEE, pp. 490-497 (Year: 2018).
- Lu et al, “An HTTP Flooding Detection Method Based on Browser Behavior,” IEEE, pp. 1151-1154 (Year: 2006).
- Notice of Allowance, dated Dec. 13, 2021, from corresponding U.S. Appl. No. 16/908,081.
- Notice of Allowance, dated Dec. 13, 2021, from corresponding U.S. Appl. No. 17/347,853.
- Notice of Allowance, dated Dec. 2, 2021, from corresponding U.S. Appl. No. 16/901,654.
- Notice of Allowance, dated Dec. 8, 2021, from corresponding U.S. Appl. No. 17/397,472.
- Nouwens et al, “Dark Patterns after the GDPR: Scraping Consent Pop-ups and Demonstrating their Influence,” ACM, pp. 1-13, Apr. 25, 2020 (Year: 2020).
- Office Action, dated Dec. 13, 2021, from corresponding U.S. Appl. No. 17/476,209.
- Office Action, dated Dec. 17, 2021, from corresponding U.S. Appl. No. 17/395,759.
- Office Action, dated Dec. 17, 2021, from corresponding U.S. Appl. No. 17/499,582.
- Office Action, dated Dec. 2, 2021, from corresponding U.S. Appl. No. 17/504,102.
- Office Action, dated Dec. 27, 2021, from corresponding U.S. Appl. No. 17/493,332.
- Office Action, dated Dec. 29, 2021, from corresponding U.S. Appl. No. 17/479,807.
- Office Action, dated December?, 2021, from corresponding U.S. Appl. No. 17/499,609.
- Paes, “Student Research Abstract: Automatic Detection of Cross-Browser Incompatibilities using Machine Learning and Screenshot Similarity,” ACM, pp. 697-698, Apr. 3, 2017 (Year: 2017).
- Restriction Requirement, dated Dec. 17, 2021, from corresponding U.S. Appl. No. 17/475,244.
- Shahriar et al, “A Model-Based Detection of Vulnerable and Malicious Browser Extensions,” IEEE, pp. 198-207 (Year: 2013).
- Sjosten et al, “Discovering Browser Extensions via Web Accessible Resources,” ACM, pp. 329-336, Mar. 22, 2017 (Year: 2017).
- Written Opinion of the International Searching Authority, dated Dec. 22, 2021, from corresponding International Application No. PCT/US2021/051217.
- Final Office Action, dated Feb. 23, 2023, from corresponding U.S. Appl. No. 17/370,650.
- Final Office Action, dated Mar. 3, 2023, from corresponding U.S. Appl. No. 17/306,438.
- Notice of Allowance, dated Feb. 8, 2023, from corresponding U.S. Appl. No. 17/831,700.
- Notice of Allowance, dated Jan. 31, 2023, from corresponding U.S. Appl. No. 17/499,624.
- Office Action, dated Feb. 15, 2023, from corresponding U.S. Appl. No. 17/499,582.
- Office Action, dated Mar. 9, 2023, from corresponding U.S. Appl. No. 17/306,496.
Type: Grant
Filed: Nov 18, 2021
Date of Patent: May 16, 2023
Patent Publication Number: 20220075896
Assignee: OneTrust, LLC (Atlanta, GA)
Inventors: Kabir A. Barday (Atlanta, GA), Jason L. Sabourin (Brookhaven, GA), Jonathan Blake Brannon (Smyrna, GA), Mihir S. Karanjkar (Marietta, GA), Kevin Jones (Atlanta, GA)
Primary Examiner: Anna C Deng
Application Number: 17/530,201
International Classification: G06F 9/44 (20180101); G06F 21/62 (20130101); H04L 9/40 (20220101); H04L 41/50 (20220101); H04L 41/5061 (20220101); G06F 15/76 (20060101); G06F 21/55 (20130101); G06F 21/31 (20130101); H04L 67/53 (20220101);