Patent Grant
12079829
This disclosure relates in general to methods and systems for predicting the online behavior of one or more web users. More specifically, web users can be divided into groups based on a characteristic (e.g., observed online behavior, past interaction, demographic, etc.).
Observed behavior from each group can be used to generate a corresponding model for predicting user behavior (e.g., whether the user will make a purchase). When data is scares for one group, multiple models can then be used in combination to predict behavior of a user in the group.
Though a single commerce web page may be visited by many users, those users may have vastly different objectives and preferences. Some may be interested in engaging in a purchase, while others may be viewing the page for tangential reasons (e.g., landing on the page by mistake, analyzing a design of the webpage, studying market competition, etc.). Even among those interested in purchasing, users may differ with regard to whether they would appreciate assistance (e.g., a chat), a preferred type of content (e.g., text and images versus videos), etc. For a merchant and/or web-page designer, it would be useful to be able to reliably identify users' intentions and/or preferences in order to improve the experience and facilitate sales.
In one embodiment, the present disclosure provides a method and system for predicting a web user's intentions and/or preferences pertinent to a given web site. One approach includes using historical data to classify each user in a first set of users into a user group based on their webpage experience and observed actions. A user group can be defined based on an experience (or population) of the user during a website visit (e.g., whether an invitation to chat was offered, or whether the user chatted with a representative) and an action (or target) (e.g., whether the chat invitation was accepted, or whether the user purchased an item). For each user group, a model is generated to translate user characteristics (e.g., inter-click times, referring site, geographic location) into a prediction as to whether the user is likely to complete the action (e.g. the model corresponding to population: invited and to target: accepted predicts whether a given user will accept the chat if invited).
A model combination is then generated, which can include a weighted sum of the available group-specific models. The model combination is used to generate a real-time prediction for each user in a second set of users (e.g., the second set of users including users concurrently accessing a website) that predicts an action (or lack thereof) that will be taken by the user (e.g., whether a purchase will be made, a value of a purchase, a purchase quantity, and/or whether a chat will be accepted). In some instances, the prediction includes one or more probabilities. The predictions can be used to allocate resources. For example, chat invitations can be selectively extended to a subset of users with a purchasing probability above an absolute or relative threshold. Resources can be dynamically re-allocated as appropriate (e.g., extending chat invitations to a second subset of users upon one or more users declining the invitation.
Group-specific models and/or the model combination can be dynamically adjusted. For example, after observing actions of one or more users in the second set of users, the characteristics of those users and the observed actions can be used to assign the user(s) to one or more user groups and adjust the respective group-specific model(s).
In some instances, the model combination includes a weighted sum of two or more group-specific models. The weights can be defined, e.g., based on a size of data used to define respective group-specific models and/or accuracies of group-specific models. For example, higher weights may be associated with group-specific models generated based on a larger data pool, recently adjusted or verified using a larger data pool, and/or providing total or recent accurate predictions. Thus, the weights may change as more data is received to verify or adjust group-specific models.
In some embodiments, a computer-implemented method is provided. A first set of requests for a webpage is received. Each first request in the first set of requests includes an identifier. For each first request in the first set of requests, first information associated with the first identifier is collected and a webpage feature is identified. The webpage feature is indicative of an electronic opportunity offered in response to the first request. For each first request in the first set of requests, an action variable is identified that is indicative of an interaction with a version of the webpage provided in response to the first request. For each first request in the first set of requests, the first request is classified such that it is assigned to a group from amongst a plurality of groups. The classification is based on the webpage feature. For each group in the plurality of groups, first information and action variables associated with requests in the first set of requests that are assigned to the group are aggregated. For each group in the plurality of groups, a group-specific model is developed based on the aggregated first information and action variables. A model combination is developed that includes a combination of a plurality of the developed group-specific models. A second request for the webpage is received. The second request includes a second identifier. Second information associated with the second identifier is collected. A model result is determined using the model combination and the second information. The model result is used to provide a response to the second request for the webpage.
In some embodiments, a system is provided includes one or more data processors and a non-transitory computer readable storage medium containing instructions which when executed on the one or more data processors, cause the one or more data processors to perform all or part of a method disclosed herein. In some embodiments, a computer-program product tangibly embodied in a non-transitory machine-readable storage medium is provided that includes instructions configured to cause one or more data processors to perform all or part of a method disclosed herein.
The dynamic approach to defining group-specific models and model combinations allows for predictions to be reliably made (even if there is a small amount of data for a group) and prediction accuracy to remain high. Such techniques can allow web developers to understand what type of users are accessing their web pages and for users' experiences to be customized (e.g., to increase a purchasing probability).
Further areas of applicability of the present disclosure will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating various embodiments, are intended for purposes of illustration only and are not intended to necessarily limit the scope of the disclosure.
The present disclosure is described in conjunction with the appended figures:
In the appended figures, similar components and/or features can have the same reference label. Further, various components of the same type can be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If only the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.
The ensuing description provides preferred exemplary embodiment(s) only and is not intended to limit the scope, applicability or configuration of the disclosure. Rather, the ensuing description of the preferred exemplary embodiment(s) will provide those skilled in the art with an enabling description for implementing a preferred exemplary embodiment. It is understood that various changes can be made in the function and arrangement of elements without departing from the spirit and scope as set forth in the appended claims.
A set of user groups can be defined, with each group relating to a different webpage experience (e.g., whether a chat was offered), action (e.g., whether a chat invitation was accepted) and/or estimated user intention (e.g., whether a purchase is of interest or will be made) and/or preference with respect to visiting an e-commerce website. Requests can be empirically classified to be assigned to one of the groups based on actual webpage presentation features (e.g., whether a chat was offered) and/or user actions (e.g., whether a user accepted a chat invitation). A group-specific model can be generated for each group that translates user information (which can include user device characteristics and/or webpage interaction data) to a preliminary result (e.g., a purchasing probability). Because it may be difficult or impossible to classify the request initially, a model combination can include a weighted combination of a set of available group-specific models (e.g., the weights being based on a training data size or accuracy of the model or a probability of requests being assigned to the corresponding group). User information can be processed using the model combination to generate a model result (e.g., a weighted sum of results of group-specific models). The model result can be evaluated to determine whether a requested webpage is to be customized in a particular manner and/or an opportunity (e.g., chat invitation or discount) is to be offered.
Using this technique, a model need not rely on a single relationship between user information and a model result. Rather, different models can be developed. Thus, for example, a relationship between user information and purchasing probability can differ depending on whether a user accepted or declined a chat invitation. Results of individual models can be weighted and combined to produce a model result, which can then be evaluated to determine whether a particular opportunity or customization is to be presented. In this manner, resources can be effectively allocated.
As one illustrative example, user information associated with one request may indicate that the user was referred to a webpage using referral site abc.com, that the user is using a mobile device, that the user is located in Texas, and that the user is not recognized as having accessed the webpage before. A first model may have been developed for instances in which a user accepts a chat invitation, and a second model for instances in which a user declines a chat invitation. Each may evaluate the user information and produce a purchasing probability. The result of the first model may be 90%. The result of the second model may be 30%. A model combination can weight the two models based on a data size used to develop or verify each model, a past accuracy of each model, a probability that each model applies to the user (e.g., based on the user information), and so on. In this illustration, the use of the mobile device may indicate that there is only a 5% chance that the first model would apply (that the user would accept a chat invitation) and the first model may further have been built on a small data size. Thus, the model combination may produce a combined result biased towards the result of the second model (35%). A rule can indicate that a chat is to be offered in response to any request associated with a combined result above 60%. Thus, the offer would not be presented in response to this request. This example is illustrative. Groups may alternatively or additionally be defined based on different circumstances, and variables input to or output by models may differ from those included in the example.
Referring first to
Provider device 110, user device 120 and/or client device 130 can each be a single electronic device, such as a hand-held electronic device (e.g., a smartphone). It will be understood that content-provider device 110, structure-provider device 120 and/or user device 130 can also include a system that includes multiple devices and/or components. The device(s) 110, 120 and/or 130 can comprise a computer, such as the desktop computer, a laptop computer or a tablet. In some instances, a party 105, 115 and/or 125 uses different devices at different times to interact with the behavior prediction engine 150. For example, user 115 may use a mobile phone to set a target online course completion date and can use a laptop computer to access content for the course. As another example, content provider 105 may user multiple computers to upload image content objects and to define a design of a webpage.
A content provider 105 can provide one or more content objects to be made accessible to one or more users 115. In one instance, content provider 105 provides partial or full content (and/or layout and/or function) of a webpage. For example, content provider 105 may partially or fully define or provide a webpage file, (e.g., an HTML file), a script, a program and/or an image. The webpage may be hosted by behavior prediction engine 150 or it may be remotely hosted (e.g., in which case, content provider 105 may, or may not, be in communication with engine 150 and/or provide one or more webpage files). Webpages provided by one or more content providers may include commerce webpages (e.g., that include offers for sale), advertisement webpages, and/or informational webpages. The webpages or web sites including the webpages may be interactive (such that displayed content on a single page or which page is displayed depends on user input) and/or dynamic. The webpages may provide one or more users with an opportunity to buy a product or service or download additional content.
A user device 120 can be configured to request and/or retrieve webpages and to interact with at least some of the webpages (e.g., to click on links or options, to submit purchase requests, to navigate through one or more pages, etc.). User device 120 may run a browser application such as but not limited to: Openwave Systems Inc. or Opera Mobile Browser (a trademark of Opera Software ASA), Microsoft Internet Explorer (a trademark of Microsoft), Firefox Web Browser, Android browser, Google-Chrome, etc. The browser application can be used for rendering webpages and communicating with one or more web servers. A common browser application can use HTTP (Hyper Text Transport Protocol) while requesting a web page from a web site. The web site can respond with a markup language file such as but not limited to Hypertext Markup Language (HTML) files.
In some instances, behavior prediction engine 150 may be part of, in communication with or independent of a web server that receives web page requests from users. Thus, for example, behavior prediction engine 150 may itself receive and process a request (e.g., and data associated with a user submitting the request), and a result of the processing can be used to determine how to respond to the request (e.g., which content or interaction opportunities to provide). As another example, a separate web server may identify to behavior prediction engine 150 a request and/or an action (e.g., whether a purchase was made or webpages that were viewed).
Behavior prediction engine 150 may act as or include a transparent proxy and may use a redirector, for example. The transparent proxy can be adapted to collect packets traveling from/to one or more user devices and to/from one or more local or remote web servers. The packets can be analyzed and (in some instances) can be modified and/or transmitted to a local or remote destination (e.g., such that a web page request can be responded to or a web page can be posted).
For each of one or more users, behavior prediction engine 150 can collect information about the user and/or monitor the user's interaction with one or more web pages. For example, behavior prediction engine 150 can access a cookie and extract information from the cookie (e.g., identifying information about which web pages the user has visited, when they were visited, which online purchases were made, demographic information, time spent interacting with web pages, etc.). As another example, a web page can prompt a user to enter account information that includes information about the user (e.g., age, sex, interests, email address, income bracket, occupation, etc.). Thus, e.g., behavior prediction engine 150 can use data such as a cookie or login information to associate a user with a user account that includes information about the user. Requests received from the user during a particular session can also be tracked (e.g., and account data can be generated to reflect the request activity.)
Behavior prediction engine 150 can use this data for one or two purposes. Initially, some or all of the data can be individually processed by each of a set of available group-specific models, and the result of each group-specific model can be combined according to a model combination. The result of the combination can include an action prediction. The action prediction can include, for example, a prediction of one or more of the following:
As a specific illustration, six classes (or user groups) may be defined. Classes A and B can correspond to instances where no chat invitation is provided, and Classes C-F can correspond to instances where a chat invitation is made. Classes C and D can correspond to instances where users accepted the invitation, and Classes E and F can correspond to instances where users declined the invitation. Classes A, C and E can correspond to instances where the users completed a purchase during a session, and Classes B, D and F can correspond to instances where no purchase was completed during a session. As another illustration, three classes may be defined, which correspond to: no chat invitation, chat invitation accepted, and chat invitation declined. Thus, it will be appreciated that assigning a user to a class may be a retrospective analysis based on observed situations and/or user actions.
For each class, behavior prediction engine 150 can generate and/or update a model that processes one or more input variables to produce one or more output variables. An output variable can include a likelihood that a will complete an action, such as, a likelihood that a user will make a purchase, a likelihood that a user will accept a chat invitation, a likelihood that a user will click on or partly or fully watch a video, or a predicted type or value of a purchase.
An output of the model can be transmitted to a local or remote web server hosting a requested web page, such that a response to the request can optionally (e.g., in accordance with a policy) be customized for the user. Such customization can be performed with a goal to increase user satisfaction with a web site, increase a user's session duration, increase a quantity or total amount of purchases, and/or allocate resources (e.g., such that expensive resources such as chats are selectively offered to visitors with high purchasing prospects). In some instances, behavior prediction engine 150 can itself performs such modification. For example, engine 150 can modify a webpage identifier (e.g., a URL) in the request based on the classification in accordance with a policy (e.g., defined in part or in full by a client) and then transmit the modified request to a web server.
Each model can be generated or updated using data of previous user visits. In this instance, the user can accurately be assigned to a class (e.g., based on whether a chat was not offered; offered and accepted; or offered and declined). The class-specific model can then relate user characteristics to an outcome or action (e.g., whether a purchase was made) such that the model can be used to generate an outcome prediction. The structure, techniques or variable values used in the models can vary across models. For example, the variables predictive of a purchase for users who accept a chat invitation may differ from those predictive of a purchase for users who decline the invitation.
However, prospectively, it may be difficult or impossible to classify users. Thus, a model combination can draw on the prediction of multiple group-specific models to generate an overall prediction for a user. In some instances, the model combination combines results from all models, all available models or all models meeting a condition (e.g., corresponding to an above-threshold data size or accuracy). The combination can include weighting the results of group-specific models. The weights can be determined based on, e.g., the corresponding group-specific models' accuracy or size of data used to generate and/or update the model.
Behavior prediction engine 150 can further transmit prediction results to one or more clients 125. Clients 125 can include, e.g., web developers, web-analytic companies, marketers, e-commerce companies, etc. In some instances, a client 125 is also a content provider 105 or is otherwise associated with content provided by a content provider 105.
A client may provide policies or restrictions to influence how users are classified, predictions that are made and/or consequences of the prediction. For example, a client may identify multiple purchasing probability ranges and may provide a functionality (e.g., chat or high-bandwidth webpage) or discount that is only to be offered to a subset of the ranges. As another example, a client may identify a marketing technique to implement for a particular class of users (e.g., emailing promotions to users estimated to favor online chats).
Further, in some instances, clients 125 can provide information about particular users. For example, a client may transmit various users' purchasing history to engine 150, which may include online purchasing and/or in-store purchasing. This information can be used for defining user groups, making a prediction for the user and/or refining a model.
Referring next to
Behavior prediction engine 150 includes a user identifier 205, which generates, identifies and/or supplements a data collection for individual users. When behavior prediction engine 150 receives a webpage request or another communication corresponding to a user, user identifier 205 can determine whether a user associated with the request or communication is stored in a record data store 210. This determination can be made by using, e.g., information in a cookie (e.g., a user or device identifier), information in a webpage (e.g., an HTTP) request, login information (e.g., a login name) or user-provided input (e.g., a name of the user or an email address). The information can be compared to corresponding information in a set of user records to determine whether the information matches corresponding information in any record. When a record is identified, information from the record can be retrieved. Otherwise, a new record can be generated (e.g., using information in a request, in a cookie, received from a user, received from a client, etc.).
A record can include user demographic information, user device information, past online behavior (e.g., characterizing access history in general or for a particular webpage or domain or characterizing purchasing history in general or for a particular webpage or domain), user-identified or estimated user preferences, purchasing information (e.g., credit-card numbers), etc. It will be appreciated that a record may be or include a single file, a collection of files or a part of one or more files. It will further be appreciated that user records may vary in terms of a degree of completeness and/or what information is included in the record.
User identifier 205 can collect user characteristics using data from the identified record and/or other information (e.g., received from a client or webpage host, such as information in a cookie). These characteristics can characterize the user, a user device, a request and so on. User characteristics can include variables (i.e., input variables) processed by a model to generate a prediction. For example, user characteristics can include one or more of: a day and/or time of receiving a webpage request; part or all of an IP address from which a request was sent; and a type and/or version of a browser application used for requesting a webpage, part or all of a URL used to request a webpage. Input variables can further or alternatively include behavioral variables, such as one or more of: a time of or since a previous visit to a webpage or domain (e.g., the requested webpage or domain); a frequency or count of visits to a webpage or domain (e.g., the requested webpage or domain); a time of or since a previous session at a webpage or domain (e.g., the requested webpage or domain); a frequency or count of sessions at a webpage or domain (e.g., the requested webpage or domain); a time of or since a previous purchase made on any webpage, at a requested webpage or at any webpage on a domain of the requested webpage; a frequency or count of previous purchases made on any webpage, at a requested webpage or at any webpage on a domain of the requested webpage; a type or identity of a product or service previously purchased on any webpage, at a requested webpage or at any webpage on a domain of the requested webpage; and a situation of a user before or during an online purchase (e.g., whether the user engaged in a chat with a representative, viewed a particular content object or viewed a particular type of content object).
Input variables can be identified using, e.g., request counters, timers and/or parsers. Counters and/or timers can be set based on requests from all users, some users or a particular user. Counters can be incremented each time a request for an event that is related to the counter is identified (e.g., a request for a webpage on hosted at a particular domain, a request to submit a purchase). Incrementing the value of a counter can be dependent on time. The last value can be faded according to the time difference between the last event and the current event. Then the faded value can be incremented by one and the time of the current event is recorded. Fading the value of the counters can be done by using an exponential formula using a half-life-time constant, for example. The half-life-time constant can have a configurable value or an adaptive one. A timer can identify a time a request was made or received.
A parser can parse a request or a cookie. Parsed data can include, for example, an identifier of a user, a session identifier, a previous detection time (a time at which a current request was made or received or a time of a most recent webpage-access time or purchase time), a previous count (e.g., of purchases made or webpages accessed), a domain, a referrer, a user device identifier, a browser identifier, an operating system identifier, etc.
Retrospectively, a user classifier can assign users into a user group or class based on webpage experiences provided to the users and/or actions taken by the user. The classification can include, for example, evaluating one or more rules or flow charts. The user groups can be indicative of, for example, whether an opportunity (e.g., chat, discount, Flash website version, etc.) was offered, whether the user performed an action (e.g., accepted an opportunity) and/or what action was performed.
User groups can be defined automatically (e.g., such that users are automatically clustered based on user-information variables) and/or can be based on client input (e.g., which may define criteria for each group, specify a number of groups, etc.). User groups may, or may not, differ across clients, domains or web pages. For example, a first client may specify that she is interested in classifying users into two groups based on a chat experience. A second client may not enter any group-defining information. Group-defining information (e.g., and association with clients, webpages or web sites) can be stored in a user group data store 220.
In addition to using the information used for user classifying, the retrospective analysis can include collecting outcome data for each user. Thus, the input variables and outcome data for users in a particular user group can be used by a model engine 230 to generate or update a group-specific model for the group. The model can predict an action of the user, such as whether the user will make a purchase (e.g., during a same session or during a later one), what will be purchased, whether the user will click on an advertisement, whether the user will indicate that he/she is a current customer of a client, and so on. By developing separate models for separate groups, more accurate predictions may be able to be made. Thus, post-hoc classification of users based on actions and experiences can allow a set of models to be generated—each pertaining to a different group.
An output of a model can include one or more: numbers (e.g., a purchasing probability), binary responses (e.g., “Yes” or “No” as to whether a purchase will be made), selections (e.g., between multiple webpages or discounts to present or between multiple priority rankings), etc. This output can be used by a webpage customizer 230 to customize a webpage experience for the user.
Model engine 230 can further use collected data to generate a model combination. The model combination can include a function or other process to combine the model outputs of each of a plurality of group-specific models. In some instances, results from all group-specific models or all available group-specific models are combined. In some instances, results from all models meeting a condition (e.g., with an above-threshold accuracy or underlying data size) are combined. In some instances, model generation itself is conditioned, such using all available models nonetheless imparts a condition.
The model combination can include weighting results of particular group-specific models. The weights can be based on, for example, one or more of a data size used to generate or update the model, an accuracy of the model, a probability of users being within the associated group, a client-defined value of the associated group and so on.
In some instances, the model combination is generated using input variables and output data for users. The data used to generate and/or update the model combination may, or may not, overlap with the data used to generate one or more group-specific models. In some instances, the output of each of one, more or all group-specific models is the same type of output as the output for the model combination. For example, each group-specific model and a model combination may produce a purchasing probability (though the precise probability may differ).
After two or more group-specific models and a model combination is generated, the model(s) can be applied in real-time to make predictions of actions for users. Specifically, user identifier 205 can collect user characteristics or input variables, model engine 225 can initially generate a set of group-specific model results (irrespective of what group the user may belong to, as such data may not be known) and model engine 225 can then combine the results according to the model combination. This use of the models may be reliably performed or performed for select users. For example, some users may serve as training users, such that their webpage experience is less customized (e.g., responsive to user variables) than others. This can allow for the opportunity to ensure that a baseline level of diverse experiences are provided (e.g., to improve the performance of the various group-specific models).
An output of the model may influence, for example, webpage content (e.g., information, products or services to offer or feature, integrated content-object types, discount offerings, script inclusion, interaction options, design, etc.), functionality options (e.g., opportunities to chat or audio/videoconference with a representative, to participate in a forum or message board), and/or follow-up protocols (e.g., whether to send a follow-up email or call). Thus, a model output can influence which content objects webpage customizer 230 retrieves from a content data store 235 in response to a webpage request or online action. For a given webpage, multiple versions of the webpage may be stored in content data store 235 (e.g., some having a chat option, some including videos or animation, some having discount offerings, some feature select products or services, etc.). A version selection can then be made based on a user-specific model result.
To illustrate, model engine 225 may use a model combination (and the underlying group-specific models) to generate a probability that each user will actually complete a purchase within a session. The first and second users may be associated with high and low probabilities, respectively. Each probability may depend on the corresponding user's purchase history, referral site, time between clicks, geographic location, and so on. A webpage provider may have established a rule indicating that an opportunity to chat with in real-time with a representative is to be selectively provided to users associated with high probabilities or provided in a biased manner to users associated with high probabilities (e.g., but also depending on one or more factors such as available chat resources, user locations, product-type interest, and so on). Thus, even though it is first estimated that both users have a similar or same webpage intent, a chat option may be presented to the first user but not the second.
Webpage customizer 230 can send generated and/or retrieved webpage documents to an interface engine 240 such that an interface engine 240 an present a customized version of a webpage to a user. Presenting the webpage can include transmitting the webpage to a user device or to display the webpage (e.g., such that interface engine 240 is at least partly on a user device).For example, interface engine 215 can generate displays or screens that convey information or content and/or that receive input. The displays or screens can be dynamic, such that the content displayed changes, for example, in response to an automatic update or user input. The displays or screens can be ones that can be presented on a device, such as a user device, computer and/or mobile device. The displays or screens can be customized based on a particular presentation device (e.g., a resolution, screen size, operating system, web browser, etc.) and/or preferences (e.g. the preferences a user indicating how content is to be displayed and/or what types of content displayed).
Interface engine 240 can receive inputs from a user (e.g., directly or based on a communication received from a user device identifying the inputs), and the inputs can be transmitted to webpage customizer 230. Inputs can include, for example, inputs corresponding to an acceptance of an offer to communicate with a representative, communicating with a representative (e.g., entering chat text or speaking into a microphone), clicking on a link, scrolling up or down or sideways on a page, initiating a purchase, identifying user information, identifying purchase information, completing a purchase, selecting a product or service of interest or to purchase, scrolling through a page, etc. (It will be appreciated that interface engine 240 can further provide an interface by which a user can enter login information or by which a cookie can be detected to thereby identify a user or user device).
Based on an input, a new or modified webpage can be presented. In some instances, webpage customizer 230 can retrieve a new webpage from content data store 235, or execution of a script in an existing webpage can cause a webpage or portion of a webpage to change (or a new webpage to appear) based on the input. For example, clicking of a “chat now” button may cause a chat window to appear that allows a user to textually communicate with a representative in real time. As another example, clicking on a “Product A” link may cause a new webpage with information about Product A to be presented.
A usage monitor 245 can monitor user behaviors. The behaviors can include, e.g., user inputs or lack thereof. The behaviors can include an amount of time spent on a webpage, a speed of scrolling, which links were clicked and/or when, which offerings were accepted or rejected, etc. Usage monitor 245 can store data corresponding to users' behaviors in one or more usage records in usage record data store 250. Each record can identify one or more of a behavior, a webpage, a domain, a user identifier, a day, a time and so on. In some instances, a usage record further includes a classification of a user, an indication as to whether a webpage was customized for the user (e.g., or whether the user served as a control user), and/or a behavior prediction associated with the user. Identification of a user (or user device) can allow for a usage record to be associated with a user record. In some instances, a single record can include both user and usage information.
Model engine 225 can translate behaviors into output variables, such that paired input variables and output data can be used to update one or more models and/or model combination. Model engine 225 may perform updates at specific times (e.g., absolute times, time intervals or new-data quantities) or based on a functional analysis (e.g., by evaluating an updating condition based on a performance of one or more models or model combinations). In preparation for the update, model engine 225 can request that usage monitor 245 collect a set of usage records from usage record data store 250. Model engine 225 can include specifications such as one or more of a user classification, an indication as to whether the user was a control or training user (versus one having received a customized webpage experience), a time period, a product, a domain, and so on. In some instances, model engine 225 further requests user records from user identifier 205 for users corresponding to the usage records.
In one instance, model engine 225 uses the retrieved records to update each of one or more group-specific models or to update a model combination (e.g., which models are combined and/or how the models are combined). The updating can include updating one or more variables (e.g., weights) in a model, adjusting (e.g., adding or removing) input variables for the model, updating a technique or function employed by the model, and so on. The updating can be performed to preferentially model recent data (e.g., modeling only recent data or weighting training data based on a time variable) or can model data irrespective of time.
In one instance, the updating can be performance based. For example, model engine 225 can determine what a combination model would have predicted for each of a set of users and compare the prediction to an observed behavior (whether a purchase was made, what was purchased, whether a session for the user remained active for over a threshold period of time, whether the user engaged in a real-time communication with a representative, whether the user returned to the domain, whether the user clicked on an advertisement, etc.). Variables in one or more group-specific models or the model combination can be selectively performed when a comparison variable is below a threshold.
A condition evaluator 315 can periodically or routinely evaluate one or more conditions (stored in condition data store) to determine whether to update one or more models. The conditions may relate to a current time, a time since a last update, a model performance, a number of website visits, a number of purchases, a number of acceptances of opportunities, a system load, a resource availability, etc. In some instances, the conditions may be at least partly defined by a client. Conditions may apply across group-specific models and/or a model combination, or different conditions may be used for different models. When an updating condition is satisfied, a data collector 325 can retrieve input variables and corresponding output data from data stores. The retrieved data can include that corresponding to a defined time window, a defined data quantity, a web site, a client and so on.
Model developer 305 can then use the input variables and output data to update one or more group-specific models and/or model combinations. For example, model developer 305 can identify that each of a set of users is associated with an output variable indicating that a chat opportunity was presented and that the user declined the opportunity. Model developer 305 can then identify a group-specific model associated with that experience and train the model using the data.
Stored model variables and/or definitions can be stored in a model data store 310 and may be associated with corresponding identifiers of a user group, domain, webpage, client, etc. Model developer 305 may further generate and/or update a model combination. The model combination can include, e.g., a linear combination, linear interpolation, bi-linear interpolation, linear or geometric mean, use link function, etc. A model combination can be separately developed and/or updated for each user group, domain, webpage, client and/or other variables. Definitions of model combinations (e.g., and their associated user group, domain, webpage, client, etc.) can also be stored in model data store 310.
When a webpage request is received from a user, a condition evaluator 315 may also determine whether the request is to be evaluated using a model or model combination and/or is to initiate webpage customization or not. This decision may include determining whether the request is to serve as a basis for training data. The decision can be based on a condition, which can include a pseudo-random selection, a condition based on a time of the request, a condition based on a user group associated with the request, a condition based on a quantity of new training data available, a condition based on a performance of a model or model combination, etc.
When it is determined that a model is to be used, model evaluator 330 can evaluate each of a plurality of group-specific models and can combine results of the group-specific models according to a model combination.
Interface engine 240 receives a webpage request at block 410. In one instance, interface engine 240 is part of a user device and receives the request via input components, such as a touchscreen, a keyboard, an audio signal, etc. In one instance, interface engine 240 is not part of a user device and can receive the request (e.g., via a network) from a user device. In one instance, a request is first sent from a user device to a client device or web server, and the request is the rerouted to interface engine 240. The request can include one or more of a: webpage identifier (e.g., a full or partial URL), cookie, an IP address, a browser identifier, a user device identifier and a user identifier.
At block 415, user identifier 205 identifies user information associated with the request. In one instance, the user information is extracted from the request. For example, a cookie in the request may identify a number of purchases that a user made using a given website in the past. In one instance, a user identifier is determined based on the request, and part or all of the user information is then retrieved using the user identifier from another file (e.g., a user record). In some instances, the request may not be associated with a user record, in which case user information can indicate that a user is a new user. User information can include the variables that are to be received as input by the classification technique. In some instances, more or less information is identified. User information can include information characterizing the user, characterizing the request, characterizing a device, characterizing past behavior, etc. For example, user information can indicate that a requesting device is in Atlanta, Ga., that the user is estimated to be between 18-24 years old, that the request is being sent from a mobile-phone device, that the user has purchased one item from a website, that the user has visited the website ten times and that it has been 2 days since a most-recent visit to the website.
At block 420, usage monitor 245 tracks an experience of a user. The experience can relate to whether an opportunity (e.g., chat, discount, animation, etc.) was presented and/or whether it was accepted. In some instances, the experience corresponds to the types of user groups. That is, a result of the tracking may be used for determining which user group a user is to be assigned to.
At block 425, usage monitor 245 monitors whether a user action occurred and/or which action occurred. For example, usage monitor 245 may detect whether a user completed or initiated a purchase in a given session or within a defined time period. As another example, usage monitor 245 may detect a duration during which the user remained on a site or a number of pages on a site visited. As another example, usage monitor 245 may detect a total purchase amount for a session.
Process 400 can then return to block 410, such that more requests can be received and processed. Periodically, routinely or conditionally, process 400 can continue to block 430 where a set of the identified, tracked and monitored data can be used to generate or update models.
At block 430, user classifier 215 applies classifies the user into a user group. Classifying a user can include associating a pair of user-information and action data with a user group. The classification can be based on the experience provided to the user.
Model engine 225 can develop one or more group-specific models at block 435. For example, data correspond to a first user group can be aggregated. The aggregated data can be used to train or otherwise influence a group-specific model for the first user group to develop a relationship or technique to translate user information into action predictions.
Each model can receive as input one or more model-input variables and can translate the input variables into a result that includes, for example, a probability of a user action or an estimated action. For example, the result can include a probability that a user will make a purchase or click on an advertisement, an estimated purchase amount, an estimated type of product for which the user will view information for, an estimated type of product that the user will purchase, an estimated duration in a session that the user will spend on a website or webpage, an estimated number of pages that the user will view in a session, a number of times or frequency that the user will visit a webpage or web site, and so on. In some instances, each model in the set of models is structured to produce a value of a same type of variable. Input variables used may be the same or may differ across group-specific models. A technique used in the model (e.g., a formula or function structure, whether a learning algorithm is used, nodes on a flow diagram, etc.) may be the same or different across group-specific models. At least some variables in the model (e.g., weights) may differ across group-specific models.
At block 440, model engine develops a model combination based on the user information and monitored actions. The data used in block 435 and block 440 may be the same, overlapping, different or non-overlapping. The combination can include, for example, a weighted sum of the group-specific models.
The model can include an indication as to how results of one or more other models are to be manipulated and/or combined to produce a result for the model combination. The combination can include a summation and/or a weighting. The combinations of the models can be linear, log-odds, linear interpolation, bi linear interpolation, etc. and may include link function (and reveres link functions). The combination can be defined using data-fitting techniques, learning techniques, training data, etc.
Defining each model combination can include determining which group-specific models are to be represented in the combination and how a result of each selected group-specific model is to be combined and/or processed to produce a result of the model combination. These determinations can be made, for example, based on a quantity of data used to defined each group-specific model in a set (e.g., such that group-specific models associated with high quantities of training data are highly weighted), based on an accuracy of each group-specific model (e.g., generally, when applied to data for users in the group associated with the model, or when applied to data for users in the group associated with the model combination), and/or a probability of a user being assigned to various user groups.
In some instances, a same set of group-specific models and/or combinations apply to multiple clients, webpages, domains, etc. In some instances, a separate set of models and/or combinations is developed for each of two or more clients, webpages, and/or domains.
At block 510, user identifier 205 identifies user information associated with each request. Block 510 can parallel block 415 in process 400.
At block 515, model engine 225 can generate a model prediction for each request based on the corresponding user information and model combination. It will be appreciated that a set of group-specific models may first be used and the results can then be combined per the model combination The prediction may relate to an action prediction, such as a purchasing probability or predicted purchasing amount or time.
At block 520, webpage customizer 230 determines a webpage experience to be presented responsive to each request. The determination can include, for example, determining whether to present a chat opportunity, a discount, a high-bandwidth webpage version, select-quantity (or otherwise distinct) product offerings, etc. The determination can be based on evaluation of the predictions. For example, “expensive” offerings (in terms of potential revenue reduction or resource consumption) may be selectively offered to users most likely to complete a purchase, predicted to complete high-value purchases, or predicted to be substantially influenced by the offering. The determination can be based on an absolute or relative threshold. For example, an offering may be selectively offered to users with a prediction value in the top 10% for the set or for a prediction value exceeding a particular number. The determination can further be based on a current or predicted availability of a resource or a revenue constraint. The determination can be based on one or more customization policies, which may be partly or fully defined by a client or defined in order to effectively allocate client resources (e.g., to increase or maximize profits or sales). It will be appreciated that the determination may, or may not, be simultaneously made for all requests in the set. Sequential processing can allow for webpages to be timely provided responsive to a request.
At block 525, webpage customizer 230 causes a webpage experience to be customized based according to the determination. In one instance, the customization is performed by behavior prediction engine 150. In one instance, a communication is sent to a remote web server or client that causes the customization to occur. For example, the communication may include an identification of the user classification. The identification may be included as part of cookie and/or a modified request.
Each request in a set of requests can correspond to a same webpage, web site, web provider, client, and/or user classification. Further, each request may be received within a defined time period (e.g. corresponding to a training increment).
At block 610, model developer 305 designates a first subset of the requests as control requests and a second subset as customizable requests. The designation may be based on a training-data quota or allocation strategy. For example, a protocol may indicate that a defined percentage of requests are to be control requests or that all requests are to be control requests until a threshold number is met. Such a percentage or threshold number may be set by a client or otherwise defined. In some instances, measures are taken so that designations are distributed based on user characteristics. For example, designations may be performed so as to not cluster either designation to a particular geographic location. In some instances, the designations are made so as to bias control designations towards requests previously associated with poor model-result accuracy. A pseudo-random designation process may be used in the allocation process (e.g., to pseudo-randomly distribute the allocations to the requests while abiding by any restraints).
Webpage customizer 230 causes responds to the first subset of requests with reduced customization relative to the second subset at block 615. Webpage customizer 230 responds to the second subset of requests with enhanced customization relative to the first subset at block 620. The customization may be based on a user-group classification associated with the request and/or based on a result of a model or model combination made using variables associated with the request or a user associated with the request. In one instance, no customization is performed for the first subset of requests. In one instance, a discount, chat, video, purchasing opportunity or extra information is offered to in response to requests in the second subset of requests whereas no such offering (or a lesser such offering) is offered in response to requests in the first subset. The customization can be performed based on evaluating a result of a model (e.g., a model combination) using one or more customization rules. For example, a rule can indicate an offer (e.g., a chat opportunity) that is to be presented in response to those requests in the second subset associated with a model result value within a particular range.
It will be appreciated that, in some instances, a webpage and/or presence of offering presented in response to a request in the first subset may be similar to or the same as one presented in response to a request in the second subset. The two requests may differ, however, with regard to whether they were considered for a different presentation. To illustrate, a rule may indicate that a chat resource is to be offered in response to those requests in the second subset associated with a model result in the top 10% of the second subset. Thus, all requests in the second subset may be eligible to be considered for this customization, while (in one instance) no requests in the first subset are eligible to be considered for the particular customization.
It will be appreciated that blocks 610-620 can be performed incrementally. For example, as each request in the set of requests is received, it can be designated as a control request or a customizable request and then responded to accordingly.
At block 625, usage monitor 245 tracks behavior of users associated with the first subset of requests. The tracked behavior can correspond to an output variable of a group-specific model or a model combination. For example, the behavior can indicate whether the user made a purchase on a webpage or web site (e.g., during a same session or, in other instances, in general), what was purchased, an amount of a purchase, a session duration, a number of times that a user returned to a webpage or web site, a number of advertisements clicked on by a user, whether a user accepted an offer (e.g., to chat with a representative, to view or use a discount, to view more information, to view a video, etc.), and so on. The tracked behavior can be stored in a usage record along with details pertaining to the request and/or a user associated with the request.
Model developer 305 detects that an updating condition is satisfied at block 630. The updating condition can include, e.g., whether an absolute time has passed, whether a quantity of new control requests were received, whether a threshold number of particular behaviors (e.g., purchases) were detected, etc.
Upon detecting the condition satisfaction, at block 635, model developer 305 updates, for example, one or more group-specific models, a model combination and/or one or more rules for customizing a webpage based on a model result. In one instance, for each control request, one or more characteristics of the request and/or associated user are identified and associated with the corresponding tracked behavior. A group-specific model and/or model combination can then be updated using the pairs of data (e.g., using fitting techniques, learning techniques, etc.). In some instances, recent data is more highly weighted than older data.
In one instance, for each control request, the request is retrospectively assigned to a group based on which actions were taken by the user (e.g., whether a purchase was completed, whether a chat invitation accepted, a time spent on a web site, etc.). Such action(s) and input variables associated with the request can be used to modify one or more structures (e.g., formulas, techniques and so on) or variables of the group-specific model and/or model combination. For example, this data may be used to train one or more models or assess an accuracy of one or more models.
Such action(s) and input variables associated with the request can alternatively or addition be used to evaluate or adjust rules for customizing a webpage based on a model result. For example, a relationship can be established between model results and a degree to which a particular customization (e.g., chat invitation, discount offering, etc.) influences a user's actions (e.g., purchasing probability or purchasing amount). A rule can then be adjusted to selectively provide the particular customization to users associated with model results indicating that the customization would result in an overall desirable effect. To specifically illustrate, users associated with a high model result may complete an e-purchase regardless of a particular customization, and users associated with a low model result may forego the purchase regardless of the particular customization. Thus, the rule may be tailored to present the customization to users associated with an intermediate range of model results.
It will be appreciated that, in some instances, data associated with customizable requests is also used to update one or more group-specific models, one or more model combinations and/or one or more rules for customizing a webpage based on a model result. In one instance, control data is used to update one or more group-specific models and/or one or more model combinations and customizable data is used to update one or more rules for customizing a webpage based on a model result. In one instance, all requests are designated as being customizable requests, and some or all of the customizable requests are also used for training.
It will be appreciated that process 600 may be separately performed for each of one or more user groups, webpages, domains and/or clients.
Referring next to
A designer 704 can input commands into computer 702 using various input devices, such as a mouse, keyboard 722, track ball, touch screen, etc. If the computer system 700 comprises a mainframe, a designer 704 can access computer 702 using, for example, a terminal or terminal interface. Additionally, computer system 726 can be connected to a printer 708 and a server 710 using a network router 712, which can connect to the Internet 718 or a WAN.
Server 710 can, for example, be used to store additional software programs and data. In one embodiment, software implementing the systems and methods described herein can be stored on a storage medium in server 710. Thus, the software can be run from the storage medium in server 710. In another embodiment, software implementing the systems and methods described herein can be stored on a storage medium in computer 702. Thus, the software can be run from the storage medium in computer system 726. Therefore, in this embodiment, the software can be used whether or not computer 702 is connected to network router 712. Printer 708 can be connected directly to computer 702, in which case, computer system 726 can print whether or not it is connected to network router 712.
With reference to
Special-purpose computer system 800 comprises a computer 702, a monitor 706 coupled to computer 702, one or more additional user output devices 840 (optional) coupled to computer 702, one or more user input devices 835 (e.g., keyboard, mouse, track ball, touch screen) coupled to computer 702, an optional communications interface 855 coupled to computer 702, a computer-program product 805 stored in a tangible computer-readable memory in computer 702. Computer-program product 805 directs system 800 to perform the above-described methods. Computer 702 can include one or more processors 860 that communicate with a number of peripheral devices via a bus subsystem 890. These peripheral devices can include user output device(s) 840, user input device(s) 835, communications interface 855, and a storage subsystem, such as random access memory (RAM) 870 and non-volatile storage drive 880 (e.g., disk drive, optical drive, solid state drive), which are forms of tangible computer-readable memory.
Computer-program product 805 can be stored in non-volatile storage drive 890 or another computer-readable medium accessible to computer 702 and loaded into memory 870. Each processor 860 can comprise a microprocessor, such as a microprocessor from Intel® or Advanced Micro Devices, Inc®, or the like. To support computer-program product 805, the computer 702 runs an operating system that handles the communications of product 805 with the above-noted components, as well as the communications between the above-noted components in support of the computer-program product 805. Exemplary operating systems include Windows® or the like from Microsoft Corporation, Solaris® from Sun Microsystems, LINUX, UNIX, and the like.
User input devices 835 include all possible types of devices and mechanisms to input information to computer system 702. These can include a keyboard, a keypad, a mouse, a scanner, a digital drawing pad, a touch screen incorporated into the display, audio input devices such as voice recognition systems, microphones, and other types of input devices. In various embodiments, user input devices 835 are typically embodied as a computer mouse, a trackball, a track pad, a joystick, wireless remote, a drawing tablet, a voice command system. User input devices 835 typically allow a user to select objects, icons, text and the like that appear on the monitor 706 via a command such as a click of a button or the like. User output devices 840 include all possible types of devices and mechanisms to output information from computer 702. These can include a display (e.g., monitor 706), printers, non-visual displays such as audio output devices, etc.
Communications interface 855 provides an interface to other communication networks and devices and can serve as an interface to receive data from and transmit data to other systems, WANs and/or the Internet 718. Embodiments of communications interface 855 typically include an Ethernet card, a modem (telephone, satellite, cable, ISDN), a (asynchronous) digital subscriber line (DSL) unit, a FireWire® interface, a USB® interface, a wireless network adapter, and the like. For example, communications interface 855 can be coupled to a computer network, to a FireWire® bus, or the like. In other embodiments, communications interface 855 can be physically integrated on the motherboard of computer 702, and/or can be a software program, or the like.
RAM 870 and non-volatile storage drive 880 are examples of tangible computer-readable media configured to store data such as computer-program product embodiments of the present invention, including executable computer code, human-readable code, or the like. Other types of tangible computer-readable media include floppy disks, removable hard disks, optical storage media such as CD-ROMs, DVDs, bar codes, semiconductor memories such as flash memories, read-only-memories (ROMs), battery-backed volatile memories, networked storage devices, and the like. RAM 870 and non-volatile storage drive 880 can be configured to store the basic programming and data constructs that provide the functionality of various embodiments of the present invention, as described above.
Software instruction sets that provide the functionality of the present invention can be stored in RAM 870 and non-volatile storage drive 880. These instruction sets or code can be executed by processor(s) 860. RAM 870 and non-volatile storage drive 880 can also provide a repository to store data and data structures used in accordance with the present invention. RAM 870 and non-volatile storage drive 880 can include a number of memories including a main random access memory (RAM) to store of instructions and data during program execution and a read-only memory (ROM) in which fixed instructions are stored. RAM 870 and non-volatile storage drive 880 can include a file storage subsystem providing persistent (non-volatile) storage of program and/or data files. RAM 870 and non-volatile storage drive 880 can also include removable storage systems, such as removable flash memory.
Bus subsystem 890 provides a mechanism to allow the various components and subsystems of computer 702 communicate with each other as intended. Although bus subsystem 890 is shown schematically as a single bus, alternative embodiments of the bus subsystem can utilize multiple buses or communication paths within computer 702.
Specific details are given in the above description to provide a thorough understanding of the embodiments. However, it is understood that the embodiments can be practiced without these specific details. For example, circuits can be shown in block diagrams in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques can be shown without unnecessary detail in order to avoid obscuring the embodiments.
Implementation of the techniques, blocks, steps and means described above can be done in various ways. For example, these techniques, blocks, steps and means can be implemented in hardware, software, or a combination thereof. For a hardware implementation, the processing units can be implemented within one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors, controllers, micro-controllers, microprocessors, other electronic units designed to perform the functions described above, and/or a combination thereof.
Also, it is noted that the embodiments can be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart can describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations can be re-arranged. A process is terminated when its operations are completed, but could have additional steps not included in the figure. A process can correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination corresponds to a return of the function to the calling function or the main function.
Furthermore, embodiments can be implemented by hardware, software, scripting languages, firmware, middleware, microcode, hardware description languages, and/or any combination thereof. When implemented in software, firmware, middleware, scripting language, and/or microcode, the program code or code segments to perform the necessary tasks can be stored in a machine readable medium such as a storage medium. A code segment or machine-executable instruction can represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a script, a class, or any combination of instructions, data structures, and/or program statements. A code segment can be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, and/or memory contents. Information, arguments, parameters, data, etc. can be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, ticket passing, network transmission, etc.
For a firmware and/or software implementation, the methodologies can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. Any machine-readable medium tangibly embodying instructions can be used in implementing the methodologies described herein. For example, software codes can be stored in a memory. Memory can be implemented within the processor or external to the processor. As used herein the term “memory” refers to any type of long term, short term, volatile, nonvolatile, or other storage medium and is not to be limited to any particular type of memory or number of memories, or type of media upon which memory is stored.
Moreover, as disclosed herein, the term “storage medium” can represent one or more memories for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine readable mediums for storing information. The term “machine-readable medium” includes, but is not limited to portable or fixed storage devices, optical storage devices, wireless channels, and/or various other storage mediums capable of storing that contain or carry instruction(s) and/or data.
While the principles of the disclosure have been described above in connection with specific apparatuses and methods, it is to be clearly understood that this description is made only by way of example and not as limitation on the scope of the disclosure.
This application is a continuation of U.S. patent application Ser. No. 14/245,400 filed Apr. 4, 2014, which claims the benefit of and priority to U.S. Provisional Application No. 61/973,042, filed on Mar. 31, 2014, both of which are hereby incorporated by reference in their entireties for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5450537 | Hirai et al. | Sep 1995 | A |
| 5517405 | McAndrew et al. | May 1996 | A |
| 5563805 | Arbuckle et al. | Oct 1996 | A |
| 5572643 | Judson | Nov 1996 | A |
| 5581702 | McArdle et al. | Dec 1996 | A |
| 5583763 | Atcheson et al. | Dec 1996 | A |
| 5590038 | Pitroda | Dec 1996 | A |
| 5592378 | Cameron et al. | Jan 1997 | A |
| 5596493 | Tone | Jan 1997 | A |
| 5611052 | Dykstra et al. | Mar 1997 | A |
| 5636346 | Saxe | Jun 1997 | A |
| 5664115 | Fraser | Sep 1997 | A |
| 5668953 | Sloo | Sep 1997 | A |
| 5678002 | Fawcett et al. | Oct 1997 | A |
| 5694163 | Harrison | Dec 1997 | A |
| 5696907 | Tom | Dec 1997 | A |
| 5699526 | Siefert | Dec 1997 | A |
| 5704029 | Wright | Dec 1997 | A |
| 5710887 | Chelliah et al. | Jan 1998 | A |
| 5715402 | Popolo | Feb 1998 | A |
| 5724155 | Saito | Mar 1998 | A |
| 5724522 | Kagami et al. | Mar 1998 | A |
| 5727048 | Hiroshima et al. | Mar 1998 | A |
| 5727163 | Bezos | Mar 1998 | A |
| 5732400 | Mandler et al. | Mar 1998 | A |
| 5745654 | Titan | Apr 1998 | A |
| 5748755 | Johnson et al. | May 1998 | A |
| 5758328 | Giovannoli | May 1998 | A |
| 5760771 | Blonder et al. | Jun 1998 | A |
| 5761640 | Kalyanswamy et al. | Jun 1998 | A |
| 5761649 | Hill | Jun 1998 | A |
| 5764916 | Busey et al. | Jun 1998 | A |
| 5765142 | Allred et al. | Jun 1998 | A |
| 5774869 | Toader | Jun 1998 | A |
| 5774870 | Storey | Jun 1998 | A |
| 5774882 | Keen et al. | Jun 1998 | A |
| 5774883 | Andersen et al. | Jun 1998 | A |
| 5778164 | Watkins et al. | Jul 1998 | A |
| 5784568 | Needham | Jul 1998 | A |
| 5793365 | Tang et al. | Aug 1998 | A |
| 5794207 | Walker et al. | Aug 1998 | A |
| 5796393 | MacNaughton et al. | Aug 1998 | A |
| 5796952 | Davis | Aug 1998 | A |
| 5797133 | Jones et al. | Aug 1998 | A |
| 5799151 | Hoffer | Aug 1998 | A |
| 5805159 | Bertram et al. | Sep 1998 | A |
| 5806043 | Toader | Sep 1998 | A |
| 5812769 | Graber et al. | Sep 1998 | A |
| 5815663 | Uomini | Sep 1998 | A |
| 5818907 | Mahoney et al. | Oct 1998 | A |
| 5819029 | Edwards et al. | Oct 1998 | A |
| 5819235 | Tamai et al. | Oct 1998 | A |
| 5819236 | Josephson | Oct 1998 | A |
| 5819291 | Haimowitz et al. | Oct 1998 | A |
| 5825869 | Brooks et al. | Oct 1998 | A |
| 5826241 | Stein et al. | Oct 1998 | A |
| 5826244 | Huberman | Oct 1998 | A |
| 5828839 | Moncreiff | Oct 1998 | A |
| 5832465 | Tom | Nov 1998 | A |
| 5835087 | Herz et al. | Nov 1998 | A |
| 5838682 | Dekelbaum et al. | Nov 1998 | A |
| 5838910 | Domenikos et al. | Nov 1998 | A |
| 5839117 | Cameron et al. | Nov 1998 | A |
| 5850517 | Verkler et al. | Dec 1998 | A |
| 5852809 | Abel et al. | Dec 1998 | A |
| 5857079 | Claus et al. | Jan 1999 | A |
| 5859974 | McArdle et al. | Jan 1999 | A |
| 5862330 | Anupam et al. | Jan 1999 | A |
| 5866889 | Weiss et al. | Feb 1999 | A |
| 5870721 | Norris | Feb 1999 | A |
| 5878403 | DeFrancesco et al. | Mar 1999 | A |
| 5895454 | Harrington | Apr 1999 | A |
| 5903641 | Tonisson | May 1999 | A |
| 5907677 | Glenn et al. | May 1999 | A |
| 5911135 | Atkins | Jun 1999 | A |
| 5916302 | Dunn et al. | Jun 1999 | A |
| 5918014 | Robinson | Jun 1999 | A |
| 5924082 | Silverman et al. | Jul 1999 | A |
| 5930776 | Dykstra et al. | Jul 1999 | A |
| 5940811 | Norris | Aug 1999 | A |
| 5940812 | Tengel et al. | Aug 1999 | A |
| 5943416 | Gisby et al. | Aug 1999 | A |
| 5943478 | Aggarwal et al. | Aug 1999 | A |
| 5945989 | Freishtat et al. | Aug 1999 | A |
| 5948061 | Merriman et al. | Sep 1999 | A |
| 5950179 | Buchanan et al. | Sep 1999 | A |
| 5956693 | Geerlings | Sep 1999 | A |
| 5958014 | Cave | Sep 1999 | A |
| 5960411 | Hartman et al. | Sep 1999 | A |
| 5963625 | Kawecki et al. | Oct 1999 | A |
| 5963635 | Szlam | Oct 1999 | A |
| 5966699 | Zandi | Oct 1999 | A |
| 5970475 | Barnes et al. | Oct 1999 | A |
| 5970478 | Walker et al. | Oct 1999 | A |
| 5974396 | Anderson | Oct 1999 | A |
| 5974446 | Sonnenrich et al. | Oct 1999 | A |
| 5987434 | Libman | Nov 1999 | A |
| 5991740 | Messer | Nov 1999 | A |
| 5995947 | Fraser et al. | Nov 1999 | A |
| 6000832 | Franklin et al. | Dec 1999 | A |
| 6003013 | Boushy | Dec 1999 | A |
| 6009410 | LeMole et al. | Dec 1999 | A |
| 6014644 | Erickson | Jan 2000 | A |
| 6014645 | Cunningham | Jan 2000 | A |
| 6014647 | Nizzari | Jan 2000 | A |
| 6016504 | Arnold et al. | Jan 2000 | A |
| 6026370 | Jermyn | Feb 2000 | A |
| 6028601 | Machiraju et al. | Feb 2000 | A |
| 6029141 | Bezos et al. | Feb 2000 | A |
| 6029149 | Dykstra et al. | Feb 2000 | A |
| 6029890 | Austin et al. | Feb 2000 | A |
| 6044146 | Gisby et al. | Mar 2000 | A |
| 6044360 | Picciallo | Mar 2000 | A |
| 6049784 | Weatherly et al. | Apr 2000 | A |
| 6052447 | Golden | Apr 2000 | A |
| 6052730 | Felciano | Apr 2000 | A |
| 6055573 | Gardenswartz et al. | Apr 2000 | A |
| 6058375 | Park et al. | May 2000 | A |
| 6058428 | Wang et al. | May 2000 | A |
| 6061658 | Chou et al. | May 2000 | A |
| 6064987 | Walker et al. | May 2000 | A |
| 6067525 | Jonhson et al. | May 2000 | A |
| 6070149 | Tavor et al. | May 2000 | A |
| 6073112 | Geerlings | Jun 2000 | A |
| 6076100 | Cottrille et al. | Jun 2000 | A |
| 6078892 | Anderson et al. | Jun 2000 | A |
| 6084585 | Kraft et al. | Jul 2000 | A |
| 6085126 | Mellgren, III et al. | Jul 2000 | A |
| 6085195 | Hoyt et al. | Jul 2000 | A |
| 6088686 | Walker et al. | Jul 2000 | A |
| 6105007 | Norris | Aug 2000 | A |
| 6112190 | Fletcher et al. | Aug 2000 | A |
| 6119101 | Peckover | Sep 2000 | A |
| 6119103 | Basch et al. | Sep 2000 | A |
| 6131087 | Luke et al. | Oct 2000 | A |
| 6131095 | Low et al. | Oct 2000 | A |
| 6134318 | O′Neil | Oct 2000 | A |
| 6134530 | Bunting et al. | Oct 2000 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6134533 | Shell | Oct 2000 | A |
| 6134548 | Gottsman et al. | Oct 2000 | A |
| 6138139 | Beck et al. | Oct 2000 | A |
| 6141653 | Conklin et al. | Oct 2000 | A |
| 6144991 | England | Nov 2000 | A |
| 6163607 | Bogart et al. | Dec 2000 | A |
| 6167395 | Beck et al. | Dec 2000 | A |
| 6170011 | Macleod Beck et al. | Jan 2001 | B1 |
| 6173053 | Bogart et al. | Jan 2001 | B1 |
| 6182050 | Ballard | Jan 2001 | B1 |
| 6182124 | Lau et al. | Jan 2001 | B1 |
| 6185543 | Galperin et al. | Feb 2001 | B1 |
| 6189003 | Leal | Feb 2001 | B1 |
| 6192319 | Simonson | Feb 2001 | B1 |
| 6192380 | Light et al. | Feb 2001 | B1 |
| 6195426 | Bolduc et al. | Feb 2001 | B1 |
| 6199079 | Gupta et al. | Mar 2001 | B1 |
| 6202053 | Christiansen et al. | Mar 2001 | B1 |
| 6202155 | Tushie et al. | Mar 2001 | B1 |
| 6208979 | Sinclair | Mar 2001 | B1 |
| 6222919 | Hollatz et al. | Apr 2001 | B1 |
| 6230121 | Weber | May 2001 | B1 |
| 6236975 | Boe et al. | May 2001 | B1 |
| 6240396 | Walker et al. | May 2001 | B1 |
| 6249795 | Douglis | Jun 2001 | B1 |
| 6262730 | Horvitz | Jul 2001 | B1 |
| 6267292 | Walker et al. | Jul 2001 | B1 |
| 6272506 | Bell | Aug 2001 | B1 |
| 6282284 | Dezonno et al. | Aug 2001 | B1 |
| 6285983 | Jenkins | Sep 2001 | B1 |
| 6289319 | Lockwood | Sep 2001 | B1 |
| 6292786 | Deaton | Sep 2001 | B1 |
| 6295061 | Park et al. | Sep 2001 | B1 |
| 6298348 | Eldering | Oct 2001 | B1 |
| 6311169 | Duhon | Oct 2001 | B2 |
| 6311178 | Bi et al. | Oct 2001 | B1 |
| 6324524 | Lent et al. | Nov 2001 | B1 |
| 6327574 | Kramer et al. | Dec 2001 | B1 |
| 6330546 | Gopinathan et al. | Dec 2001 | B1 |
| 6334110 | Walter | Dec 2001 | B1 |
| 6338066 | Martin | Jan 2002 | B1 |
| 6346952 | Shtivelman | Feb 2002 | B1 |
| 6349290 | Horowitz et al. | Feb 2002 | B1 |
| 6356909 | Spencer | Mar 2002 | B1 |
| 6374230 | Walker et al. | Apr 2002 | B1 |
| 6377936 | Henrick et al. | Apr 2002 | B1 |
| 6381640 | Beck | Apr 2002 | B1 |
| 6385594 | Lebda et al. | May 2002 | B1 |
| 6393479 | Glommen et al. | May 2002 | B1 |
| 6405181 | Lent et al. | Jun 2002 | B2 |
| 6438526 | Dykes et al. | Aug 2002 | B1 |
| 6449358 | Anisimov | Sep 2002 | B1 |
| 6449646 | Sikora et al. | Sep 2002 | B1 |
| 6463149 | Jolissaint et al. | Oct 2002 | B1 |
| 6466970 | Lee | Oct 2002 | B1 |
| 6477533 | Schiff et al. | Nov 2002 | B2 |
| 6507851 | Fujiwara et al. | Jan 2003 | B1 |
| 6510418 | Case et al. | Jan 2003 | B1 |
| 6510427 | Bossemeyer, Jr. et al. | Jan 2003 | B1 |
| 6516421 | Peters | Feb 2003 | B1 |
| 6519628 | Locascio | Feb 2003 | B1 |
| 6526404 | Slater | Feb 2003 | B1 |
| 6535492 | Shtivelman | Mar 2003 | B2 |
| 6542936 | Mayle et al. | Apr 2003 | B1 |
| 6546372 | Lauffer | Apr 2003 | B2 |
| 6549919 | Lambert et al. | Apr 2003 | B2 |
| 6567791 | Lent et al. | May 2003 | B2 |
| 6571236 | Ruppelt | May 2003 | B1 |
| 6597377 | MacPhail | Jul 2003 | B1 |
| 6606744 | Mikurak | Aug 2003 | B1 |
| 6618746 | Desai et al. | Sep 2003 | B2 |
| 6622131 | Brown et al. | Sep 2003 | B1 |
| 6622138 | Bellamkonda | Sep 2003 | B1 |
| 6654815 | Goss | Nov 2003 | B1 |
| 6662215 | Moskowitz et al. | Dec 2003 | B1 |
| 6665395 | Busey et al. | Dec 2003 | B1 |
| 6671818 | Mikurak | Dec 2003 | B1 |
| 6691151 | Cheyer et al. | Feb 2004 | B1 |
| 6691159 | Grewal et al. | Feb 2004 | B1 |
| 6701441 | Balasubramaniam et al. | Mar 2004 | B1 |
| 6718313 | Lent et al. | Apr 2004 | B1 |
| 6721713 | Guheen et al. | Apr 2004 | B1 |
| 6725210 | Key | Apr 2004 | B1 |
| 6741995 | Chen | May 2004 | B1 |
| 6760429 | Hung et al. | Jul 2004 | B1 |
| 6766302 | Bach | Jul 2004 | B2 |
| 6771766 | Shaflee et al. | Aug 2004 | B1 |
| 6778982 | Knight | Aug 2004 | B1 |
| 6795812 | Lent et al. | Sep 2004 | B1 |
| 6804659 | Graham et al. | Oct 2004 | B1 |
| 6826594 | Pettersen | Nov 2004 | B1 |
| 6829585 | Grewal et al. | Dec 2004 | B1 |
| 6836768 | Hirsh | Dec 2004 | B1 |
| 6839680 | Liu | Jan 2005 | B1 |
| 6839682 | Blume | Jan 2005 | B1 |
| 6850896 | Kelman et al. | Feb 2005 | B1 |
| 6865267 | Dezono | Mar 2005 | B2 |
| 6892226 | Tso et al. | May 2005 | B1 |
| 6892347 | Williams | May 2005 | B1 |
| 6904408 | McCarthy et al. | Jun 2005 | B1 |
| 6920434 | Cossette | Jul 2005 | B1 |
| 6922705 | Northrup | Jul 2005 | B1 |
| 6925441 | Jones | Aug 2005 | B1 |
| 6925442 | Shapira et al. | Aug 2005 | B1 |
| 6950983 | Snavely | Sep 2005 | B1 |
| 6965868 | Bednarek | Nov 2005 | B1 |
| 6981028 | Rawat et al. | Dec 2005 | B1 |
| 6993557 | Yen | Jan 2006 | B1 |
| 7003476 | Samra et al. | Feb 2006 | B1 |
| 7013329 | Paul et al. | Mar 2006 | B1 |
| 7039599 | Merriman et al. | May 2006 | B2 |
| 7051273 | Holt et al. | May 2006 | B1 |
| 7076443 | Emens et al. | Jul 2006 | B1 |
| 7085682 | Heller et al. | Aug 2006 | B1 |
| 7092959 | Chen | Aug 2006 | B2 |
| 7106850 | Campbell et al. | Sep 2006 | B2 |
| 7123974 | Hamilton | Oct 2006 | B1 |
| 7143063 | Lent et al. | Nov 2006 | B2 |
| 7181492 | Wen et al. | Feb 2007 | B2 |
| 7200614 | Reid et al. | Apr 2007 | B2 |
| 7242760 | Shires | Jul 2007 | B2 |
| 7243109 | Omega et al. | Jul 2007 | B2 |
| 7251648 | Chaudhuri et al. | Jul 2007 | B2 |
| 7266510 | Cofino | Sep 2007 | B1 |
| 7287000 | Boyd et al. | Oct 2007 | B2 |
| 7313575 | Carr et al. | Dec 2007 | B2 |
| 7337127 | Smith et al. | Feb 2008 | B1 |
| 7346576 | Lent et al. | Mar 2008 | B2 |
| 7346604 | Bharat et al. | Mar 2008 | B1 |
| 7346606 | Bharat | Mar 2008 | B2 |
| 7370002 | Heckerman et al. | May 2008 | B2 |
| 7376603 | Mayr et al. | May 2008 | B1 |
| 7403973 | Wilsher et al. | Jul 2008 | B2 |
| 7424363 | Cheng | Sep 2008 | B2 |
| 7467349 | Bryar et al. | Dec 2008 | B1 |
| 7523191 | Thomas et al. | Apr 2009 | B1 |
| 7526439 | Freishtat et al. | Apr 2009 | B2 |
| 7536320 | McQueen et al. | May 2009 | B2 |
| 7552080 | Willard et al. | Jun 2009 | B1 |
| 7552365 | Marsh | Jun 2009 | B1 |
| 7562058 | Pinto | Jul 2009 | B2 |
| 7590550 | Schoenberg | Sep 2009 | B2 |
| 7630986 | Herz et al. | Dec 2009 | B1 |
| 7650381 | Peters | Jan 2010 | B2 |
| 7657465 | Freishtat et al. | Feb 2010 | B2 |
| 7660815 | Scofield | Feb 2010 | B1 |
| 7689924 | Schneider et al. | Mar 2010 | B1 |
| 7702635 | Horvitz et al. | Apr 2010 | B2 |
| 7716322 | Benedikt et al. | May 2010 | B2 |
| 7730010 | Kishore et al. | Jun 2010 | B2 |
| 7734503 | Agarwal et al. | Jun 2010 | B2 |
| 7734632 | Wang | Jun 2010 | B2 |
| 7739149 | Freishtat et al. | Jun 2010 | B2 |
| 7743044 | Kalogeraki | Jun 2010 | B1 |
| 7818340 | Warren | Oct 2010 | B1 |
| 7827128 | Karlsson et al. | Nov 2010 | B1 |
| 7865457 | Ravin et al. | Jan 2011 | B2 |
| 7877679 | Ozana | Jan 2011 | B2 |
| 7895193 | Cucerzan | Feb 2011 | B2 |
| 7958066 | Pinckney et al. | Jun 2011 | B2 |
| 7966564 | Catlin | Jun 2011 | B2 |
| 7975020 | Green et al. | Jul 2011 | B1 |
| 8010422 | Lascelles et al. | Aug 2011 | B1 |
| 8065666 | Schnabele | Nov 2011 | B2 |
| 8095408 | Schigel | Jan 2012 | B2 |
| 8166026 | Sadler | Apr 2012 | B1 |
| 8185544 | Oztekin et al. | May 2012 | B2 |
| 8260846 | Lahav | Sep 2012 | B2 |
| 8266127 | Mattox et al. | Sep 2012 | B2 |
| 8321906 | Agrusa | Nov 2012 | B2 |
| 8386340 | Feinstein | Feb 2013 | B1 |
| 8386509 | Scofield | Feb 2013 | B1 |
| 8392580 | Allen et al. | Mar 2013 | B2 |
| 8478816 | Parks et al. | Jul 2013 | B2 |
| 8738732 | Karidi | May 2014 | B2 |
| 8762313 | Lahav et al. | Jun 2014 | B2 |
| 8782200 | Hansen | Jul 2014 | B2 |
| 8799200 | Lahav | Aug 2014 | B2 |
| 8805844 | Schorzman et al. | Aug 2014 | B2 |
| 8805941 | Barak et al. | Aug 2014 | B2 |
| 8812601 | Hsueh et al. | Aug 2014 | B2 |
| 8839093 | Siroker | Sep 2014 | B1 |
| 8843481 | Xu | Sep 2014 | B1 |
| 8868448 | Freishtat et al. | Oct 2014 | B2 |
| 8918465 | Barak | Dec 2014 | B2 |
| 8943002 | Zelenko et al. | Jan 2015 | B2 |
| 8943145 | Peters et al. | Jan 2015 | B1 |
| 8954539 | Lahav | Feb 2015 | B2 |
| 8965998 | Dicker | Feb 2015 | B1 |
| 9104970 | Lahav et al. | Aug 2015 | B2 |
| 9247066 | Stec et al. | Jan 2016 | B1 |
| 9256761 | Sahu | Feb 2016 | B1 |
| 9274932 | Crossley | Mar 2016 | B2 |
| 9331969 | Barak et al. | May 2016 | B2 |
| 9336487 | Lahav | May 2016 | B2 |
| 9350598 | Barak et al. | May 2016 | B2 |
| 9396295 | Lahav et al. | Jul 2016 | B2 |
| 9396436 | Lahav | Jul 2016 | B2 |
| 9432468 | Karidi | Aug 2016 | B2 |
| 9525745 | Karidi | Dec 2016 | B2 |
| 9558276 | Barak et al. | Jan 2017 | B2 |
| 9563336 | Barak et al. | Feb 2017 | B2 |
| 9563707 | Barak et al. | Feb 2017 | B2 |
| 9569537 | Barak et al. | Feb 2017 | B2 |
| 9576292 | Freishtat et al. | Feb 2017 | B2 |
| 9582579 | Barak et al. | Feb 2017 | B2 |
| 9590930 | Karidi | Mar 2017 | B2 |
| 9672196 | Shachar et al. | Jun 2017 | B2 |
| 9767212 | Lavi et al. | Sep 2017 | B2 |
| 9819561 | Freishtat et al. | Nov 2017 | B2 |
| 9881318 | Krishnamoorthy | Jan 2018 | B1 |
| 9892417 | Shachar et al. | Feb 2018 | B2 |
| 9948582 | Karidi | Apr 2018 | B2 |
| 10038683 | Barak et al. | Jul 2018 | B2 |
| 10061860 | Daly, Jr. | Aug 2018 | B2 |
| 10142908 | Barak et al. | Nov 2018 | B2 |
| 10191622 | Karidi et al. | Jan 2019 | B2 |
| 10278065 | Stuber et al. | Apr 2019 | B2 |
| 10373177 | Vijayaraghavan | Aug 2019 | B2 |
| 11386442 | Lahav et al. | Jul 2022 | B2 |
| 11394670 | Karidi | Jul 2022 | B2 |
| 20010001150 | Miloslavsky | May 2001 | A1 |
| 20010011245 | Duhon | Aug 2001 | A1 |
| 20010011246 | Tammaro | Aug 2001 | A1 |
| 20010011262 | Hoyt et al. | Aug 2001 | A1 |
| 20010011282 | Katsumata et al. | Aug 2001 | A1 |
| 20010013009 | Greening et al. | Aug 2001 | A1 |
| 20010014877 | Defrancesco et al. | Aug 2001 | A1 |
| 20010025249 | Tokunaga | Sep 2001 | A1 |
| 20010027436 | Tenembaum | Oct 2001 | A1 |
| 20010032140 | Hoffman | Oct 2001 | A1 |
| 20010032244 | Neustel | Oct 2001 | A1 |
| 20010034689 | Heilman | Oct 2001 | A1 |
| 20010044751 | Pugliese | Nov 2001 | A1 |
| 20010054041 | Chang | Dec 2001 | A1 |
| 20010054064 | Kannan | Dec 2001 | A1 |
| 20010056405 | Muyres | Dec 2001 | A1 |
| 20020002491 | Whitfield | Jan 2002 | A1 |
| 20020004735 | Gross | Jan 2002 | A1 |
| 20020010625 | Smith et al. | Jan 2002 | A1 |
| 20020016731 | Kupersmit | Feb 2002 | A1 |
| 20020023051 | Kunzle et al. | Feb 2002 | A1 |
| 20020026351 | Coleman | Feb 2002 | A1 |
| 20020029188 | Schmid | Mar 2002 | A1 |
| 20020029267 | Sankuratripati et al. | Mar 2002 | A1 |
| 20020035486 | Huyn et al. | Mar 2002 | A1 |
| 20020038230 | Chen | Mar 2002 | A1 |
| 20020045154 | Wood | Apr 2002 | A1 |
| 20020046086 | Pletz | Apr 2002 | A1 |
| 20020046096 | Srinivasan | Apr 2002 | A1 |
| 20020047859 | Szlam et al. | Apr 2002 | A1 |
| 20020055878 | Burton et al. | May 2002 | A1 |
| 20020059095 | Cook | May 2002 | A1 |
| 20020067500 | Yokomizo et al. | Jun 2002 | A1 |
| 20020073162 | McErlean | Jun 2002 | A1 |
| 20020082923 | Merriman et al. | Jun 2002 | A1 |
| 20020083095 | Wu et al. | Jun 2002 | A1 |
| 20020083167 | Costigan et al. | Jun 2002 | A1 |
| 20020085705 | Shires | Jul 2002 | A1 |
| 20020091832 | Low et al. | Jul 2002 | A1 |
| 20020099694 | Diamond et al. | Jul 2002 | A1 |
| 20020107728 | Bailey et al. | Aug 2002 | A1 |
| 20020111847 | Smith | Aug 2002 | A1 |
| 20020111850 | Smrcka et al. | Aug 2002 | A1 |
| 20020123926 | Bushold | Sep 2002 | A1 |
| 20020161620 | Hatanaka | Oct 2002 | A1 |
| 20020161651 | Godsey | Oct 2002 | A1 |
| 20020161664 | Shaya et al. | Oct 2002 | A1 |
| 20020167539 | Brown et al. | Nov 2002 | A1 |
| 20030004781 | Mallon | Jan 2003 | A1 |
| 20030009768 | Moir | Jan 2003 | A1 |
| 20030011641 | Totman et al. | Jan 2003 | A1 |
| 20030014304 | Calvert et al. | Jan 2003 | A1 |
| 20030023754 | Eichstadt et al. | Jan 2003 | A1 |
| 20030028415 | Herschap et al. | Feb 2003 | A1 |
| 20030036949 | Kaddeche et al. | Feb 2003 | A1 |
| 20030041056 | Bossemeyer et al. | Feb 2003 | A1 |
| 20030055778 | Erlanger | Mar 2003 | A1 |
| 20030061091 | Amaratunga | Mar 2003 | A1 |
| 20030079176 | Kang et al. | Apr 2003 | A1 |
| 20030105826 | Mayraz | Jun 2003 | A1 |
| 20030110130 | Pelletier | Jun 2003 | A1 |
| 20030140037 | Deh-Lee | Jul 2003 | A1 |
| 20030149581 | Chaudhri et al. | Aug 2003 | A1 |
| 20030149937 | McElfresh et al. | Aug 2003 | A1 |
| 20030154196 | Goodwin et al. | Aug 2003 | A1 |
| 20030167195 | Fernandes et al. | Sep 2003 | A1 |
| 20030177096 | Trent et al. | Sep 2003 | A1 |
| 20030195848 | Felger | Oct 2003 | A1 |
| 20030217332 | Smith et al. | Nov 2003 | A1 |
| 20030221163 | Glover et al. | Nov 2003 | A1 |
| 20030233425 | Lyons et al. | Dec 2003 | A1 |
| 20040034567 | Gravett | Feb 2004 | A1 |
| 20040064412 | Phillips et al. | Apr 2004 | A1 |
| 20040073475 | Tupper | Apr 2004 | A1 |
| 20040075686 | Watler | Apr 2004 | A1 |
| 20040088323 | Elder et al. | May 2004 | A1 |
| 20040128390 | Blakley et al. | Jul 2004 | A1 |
| 20040141016 | Fukatsu et al. | Jul 2004 | A1 |
| 20040153368 | Freishtat et al. | Aug 2004 | A1 |
| 20040163101 | Swix et al. | Aug 2004 | A1 |
| 20040167928 | Anderson et al. | Aug 2004 | A1 |
| 20040193377 | Brown | Sep 2004 | A1 |
| 20040210820 | Tarr et al. | Oct 2004 | A1 |
| 20040243539 | Skurtovich et al. | Dec 2004 | A1 |
| 20040249650 | Freedman | Dec 2004 | A1 |
| 20040260574 | Gross | Dec 2004 | A1 |
| 20050004864 | Lent et al. | Jan 2005 | A1 |
| 20050014117 | Stillman | Jan 2005 | A1 |
| 20050033641 | Jha et al. | Feb 2005 | A1 |
| 20050033728 | James | Feb 2005 | A1 |
| 20050044149 | Regardie et al. | Feb 2005 | A1 |
| 20050091254 | Stabb | Apr 2005 | A1 |
| 20050096963 | Myr | May 2005 | A1 |
| 20050096997 | Jain et al. | May 2005 | A1 |
| 20050097089 | Nielsen et al. | May 2005 | A1 |
| 20050102177 | Takayama | May 2005 | A1 |
| 20050102257 | Onyon et al. | May 2005 | A1 |
| 20050114195 | Bernasconi | May 2005 | A1 |
| 20050131944 | Edward | Jun 2005 | A1 |
| 20050132205 | Palliyil et al. | Jun 2005 | A1 |
| 20050138115 | Llamas et al. | Jun 2005 | A1 |
| 20050171861 | Bezos et al. | Aug 2005 | A1 |
| 20050183003 | Peri | Aug 2005 | A1 |
| 20050198120 | Reshef et al. | Sep 2005 | A1 |
| 20050198212 | Zilberfayn et al. | Sep 2005 | A1 |
| 20050198220 | Wada et al. | Sep 2005 | A1 |
| 20050216342 | Ashbaugh | Sep 2005 | A1 |
| 20050234761 | Pinto | Oct 2005 | A1 |
| 20050256955 | Bodwell et al. | Nov 2005 | A1 |
| 20050262065 | Barth et al. | Nov 2005 | A1 |
| 20050273388 | Roetter | Dec 2005 | A1 |
| 20050288943 | Wei et al. | Dec 2005 | A1 |
| 20060015390 | Rijisinghani et al. | Jan 2006 | A1 |
| 20060021009 | Lunt | Jan 2006 | A1 |
| 20060026147 | Cone et al. | Feb 2006 | A1 |
| 20060026237 | Wang et al. | Feb 2006 | A1 |
| 20060041378 | Chen | Feb 2006 | A1 |
| 20060041476 | Zheng | Feb 2006 | A1 |
| 20060041562 | Paczkowski et al. | Feb 2006 | A1 |
| 20060047615 | Ravin et al. | Mar 2006 | A1 |
| 20060059124 | Krishna | Mar 2006 | A1 |
| 20060106788 | Forrest | May 2006 | A1 |
| 20060122850 | Ward et al. | Jun 2006 | A1 |
| 20060168509 | Boss et al. | Jul 2006 | A1 |
| 20060224750 | Davies | Oct 2006 | A1 |
| 20060253319 | Chayes et al. | Nov 2006 | A1 |
| 20060265495 | Butler et al. | Nov 2006 | A1 |
| 20060271545 | Youn et al. | Nov 2006 | A1 |
| 20060277477 | Christenson | Dec 2006 | A1 |
| 20060282327 | Neal et al. | Dec 2006 | A1 |
| 20060282328 | Gerace et al. | Dec 2006 | A1 |
| 20060284378 | Snow et al. | Dec 2006 | A1 |
| 20060284892 | Sheridan | Dec 2006 | A1 |
| 20060288087 | Sun | Dec 2006 | A1 |
| 20060293950 | Meek et al. | Dec 2006 | A1 |
| 20070027771 | Collins et al. | Feb 2007 | A1 |
| 20070027785 | Lent et al. | Feb 2007 | A1 |
| 20070053513 | Hoffberg | Mar 2007 | A1 |
| 20070061412 | Karidi | Mar 2007 | A1 |
| 20070061421 | Karidi | Mar 2007 | A1 |
| 20070073585 | Apple et al. | Mar 2007 | A1 |
| 20070094228 | Nevin et al. | Apr 2007 | A1 |
| 20070100653 | Ramer et al. | May 2007 | A1 |
| 20070100688 | Book | May 2007 | A1 |
| 20070112958 | Kim | May 2007 | A1 |
| 20070116238 | Jacobi | May 2007 | A1 |
| 20070116239 | Jacobi | May 2007 | A1 |
| 20070162501 | Agassi et al. | Jul 2007 | A1 |
| 20070162846 | Cave | Jul 2007 | A1 |
| 20070168465 | Toppenberg | Jul 2007 | A1 |
| 20070168874 | Kloeffer | Jul 2007 | A1 |
| 20070185751 | Dempers | Aug 2007 | A1 |
| 20070206086 | Baron et al. | Sep 2007 | A1 |
| 20070214048 | Chan | Sep 2007 | A1 |
| 20070220092 | Heitzeberg et al. | Sep 2007 | A1 |
| 20070239527 | Nazer et al. | Oct 2007 | A1 |
| 20070250585 | Ly et al. | Oct 2007 | A1 |
| 20070256003 | Wagoner | Nov 2007 | A1 |
| 20070260596 | Koran et al. | Nov 2007 | A1 |
| 20070260624 | Chung et al. | Nov 2007 | A1 |
| 20070265873 | Sheth et al. | Nov 2007 | A1 |
| 20080021816 | Lent et al. | Jan 2008 | A1 |
| 20080033794 | Ou et al. | Feb 2008 | A1 |
| 20080033941 | Parrish | Feb 2008 | A1 |
| 20080040225 | Roker | Feb 2008 | A1 |
| 20080072170 | Simons | Mar 2008 | A1 |
| 20080133650 | Saarimaki et al. | Jun 2008 | A1 |
| 20080147480 | Sarma et al. | Jun 2008 | A1 |
| 20080147486 | Wu et al. | Jun 2008 | A1 |
| 20080147741 | Gonen et al. | Jun 2008 | A1 |
| 20080183745 | Cancel et al. | Jul 2008 | A1 |
| 20080183806 | Cancel et al. | Jul 2008 | A1 |
| 20080201206 | Pokorney | Aug 2008 | A1 |
| 20080201436 | Gartner | Aug 2008 | A1 |
| 20080215541 | Li et al. | Sep 2008 | A1 |
| 20080222656 | Lyman | Sep 2008 | A1 |
| 20080244024 | Aaltonen et al. | Oct 2008 | A1 |
| 20080262897 | Howarter et al. | Oct 2008 | A1 |
| 20080270294 | Lent et al. | Oct 2008 | A1 |
| 20080270295 | Lent et al. | Oct 2008 | A1 |
| 20080275864 | Kim | Nov 2008 | A1 |
| 20080288658 | Banga | Nov 2008 | A1 |
| 20080319778 | Abhyanker | Dec 2008 | A1 |
| 20090006174 | Lauffer | Jan 2009 | A1 |
| 20090006179 | Billingsley et al. | Jan 2009 | A1 |
| 20090006622 | Doerr | Jan 2009 | A1 |
| 20090028047 | Schmidt | Jan 2009 | A1 |
| 20090030859 | Buchs et al. | Jan 2009 | A1 |
| 20090037355 | Brave | Feb 2009 | A1 |
| 20090055267 | Roker | Feb 2009 | A1 |
| 20090063645 | Casey et al. | Mar 2009 | A1 |
| 20090076887 | Spivack et al. | Mar 2009 | A1 |
| 20090099904 | Affeld et al. | Apr 2009 | A1 |
| 20090119173 | Parsons et al. | May 2009 | A1 |
| 20090132368 | Cotter et al. | May 2009 | A1 |
| 20090138563 | Zhu | May 2009 | A1 |
| 20090138606 | Moran et al. | May 2009 | A1 |
| 20090164171 | Wold et al. | Jun 2009 | A1 |
| 20090177771 | Britton et al. | Jul 2009 | A1 |
| 20090210405 | Ortega et al. | Aug 2009 | A1 |
| 20090222572 | Fujihara | Sep 2009 | A1 |
| 20090228914 | Wong | Sep 2009 | A1 |
| 20090240586 | Ramer et al. | Sep 2009 | A1 |
| 20090287534 | Guo et al. | Nov 2009 | A1 |
| 20090287633 | Nevin et al. | Nov 2009 | A1 |
| 20090293001 | Lu et al. | Nov 2009 | A1 |
| 20090298480 | Khambete | Dec 2009 | A1 |
| 20090307003 | Benjamin | Dec 2009 | A1 |
| 20090319296 | Schoenberg | Dec 2009 | A1 |
| 20090327863 | Holt et al. | Dec 2009 | A1 |
| 20100023475 | Lahav | Jan 2010 | A1 |
| 20100023581 | Lahav | Jan 2010 | A1 |
| 20100049602 | Softky | Feb 2010 | A1 |
| 20100057548 | Edwards | Mar 2010 | A1 |
| 20100063879 | Araradian et al. | Mar 2010 | A1 |
| 20100106552 | Barillaud | Apr 2010 | A1 |
| 20100125657 | Dowling et al. | May 2010 | A1 |
| 20100169176 | Turakhia | Jul 2010 | A1 |
| 20100169342 | Kenedy | Jul 2010 | A1 |
| 20100205024 | Shachar et al. | Aug 2010 | A1 |
| 20100211579 | Fujioka | Aug 2010 | A1 |
| 20100255812 | Nanjundaiah et al. | Oct 2010 | A1 |
| 20100262558 | Willcock | Oct 2010 | A1 |
| 20100281008 | Braunwarth | Nov 2010 | A1 |
| 20100306043 | Lindsay et al. | Dec 2010 | A1 |
| 20110004888 | Srinivasan et al. | Jan 2011 | A1 |
| 20110041168 | Murray et al. | Feb 2011 | A1 |
| 20110055207 | Schorzman et al. | Mar 2011 | A1 |
| 20110055309 | Gibor et al. | Mar 2011 | A1 |
| 20110055331 | Adelman et al. | Mar 2011 | A1 |
| 20110055338 | Loeb et al. | Mar 2011 | A1 |
| 20110112893 | Karlsson et al. | May 2011 | A1 |
| 20110113101 | Ye et al. | May 2011 | A1 |
| 20110119264 | Hu et al. | May 2011 | A1 |
| 20110131077 | Tan | Jun 2011 | A1 |
| 20110137733 | Baird et al. | Jun 2011 | A1 |
| 20110138298 | Alfred et al. | Jun 2011 | A1 |
| 20110161792 | Florence et al. | Jun 2011 | A1 |
| 20110208822 | Rathod | Aug 2011 | A1 |
| 20110246255 | Gilbert et al. | Oct 2011 | A1 |
| 20110246406 | Lahav et al. | Oct 2011 | A1 |
| 20110258039 | Patwa et al. | Oct 2011 | A1 |
| 20110270926 | Boyd | Nov 2011 | A1 |
| 20110270934 | Wong et al. | Nov 2011 | A1 |
| 20110271175 | Lavi et al. | Nov 2011 | A1 |
| 20110271183 | Bose et al. | Nov 2011 | A1 |
| 20110307331 | Richard et al. | Dec 2011 | A1 |
| 20110320715 | Ickman et al. | Dec 2011 | A1 |
| 20120012358 | Horan et al. | Jan 2012 | A1 |
| 20120036200 | Cole | Feb 2012 | A1 |
| 20120042389 | Bradley et al. | Feb 2012 | A1 |
| 20120059722 | Rao | Mar 2012 | A1 |
| 20120066345 | Rayan | Mar 2012 | A1 |
| 20120130918 | Gordon | May 2012 | A1 |
| 20120136939 | Stern et al. | May 2012 | A1 |
| 20120150973 | Barak | Jun 2012 | A1 |
| 20120173373 | Soroca | Jul 2012 | A1 |
| 20120195422 | Famous | Aug 2012 | A1 |
| 20120215664 | Dalal | Aug 2012 | A1 |
| 20120254301 | Fiero | Oct 2012 | A1 |
| 20120259891 | Edoja | Oct 2012 | A1 |
| 20120323346 | Ashby et al. | Dec 2012 | A1 |
| 20130013362 | Walker et al. | Jan 2013 | A1 |
| 20130013990 | Green | Jan 2013 | A1 |
| 20130036202 | Lahav | Feb 2013 | A1 |
| 20130050392 | Chiang | Feb 2013 | A1 |
| 20130054707 | Muszynski et al. | Feb 2013 | A1 |
| 20130080961 | Levien et al. | Mar 2013 | A1 |
| 20130117276 | Hedditch | May 2013 | A1 |
| 20130117380 | Pomazanov et al. | May 2013 | A1 |
| 20130117804 | Chawla | May 2013 | A1 |
| 20130125009 | DeLuca | May 2013 | A1 |
| 20130132194 | Rajaram | May 2013 | A1 |
| 20130136253 | Liberman | May 2013 | A1 |
| 20130138507 | Kumar | May 2013 | A1 |
| 20130165234 | Hall | Jun 2013 | A1 |
| 20130182834 | Lauffer | Jul 2013 | A1 |
| 20130204859 | Vijaywargi et al. | Aug 2013 | A1 |
| 20130212497 | Zelenko et al. | Aug 2013 | A1 |
| 20130238714 | Barak et al. | Sep 2013 | A1 |
| 20130250354 | Kato | Sep 2013 | A1 |
| 20130268468 | Vijayaraghavan et al. | Oct 2013 | A1 |
| 20130275862 | Adra | Oct 2013 | A1 |
| 20130290533 | Barak | Oct 2013 | A1 |
| 20130311874 | Schachar et al. | Nov 2013 | A1 |
| 20130326375 | Barak et al. | Dec 2013 | A1 |
| 20130336471 | Agarwal et al. | Dec 2013 | A1 |
| 20130339445 | Perincherry | Dec 2013 | A1 |
| 20140058721 | Becerra | Feb 2014 | A1 |
| 20140068011 | Zhang et al. | Mar 2014 | A1 |
| 20140094134 | Balthasar | Apr 2014 | A1 |
| 20140115466 | Barak et al. | Apr 2014 | A1 |
| 20140222888 | Karidi | Aug 2014 | A1 |
| 20140250051 | Lahav et al. | Sep 2014 | A1 |
| 20140278795 | Satyamoorthy | Sep 2014 | A1 |
| 20140289005 | Laing | Sep 2014 | A1 |
| 20140310229 | Lahav et al. | Oct 2014 | A1 |
| 20140331138 | Overton et al. | Nov 2014 | A1 |
| 20140372240 | Freishtat et al. | Dec 2014 | A1 |
| 20140379429 | Valimaki | Dec 2014 | A1 |
| 20150012602 | Barak et al. | Jan 2015 | A1 |
| 20150012848 | Barak et al. | Jan 2015 | A1 |
| 20150019525 | Barak et al. | Jan 2015 | A1 |
| 20150019527 | Barak et al. | Jan 2015 | A1 |
| 20150082345 | Archer | Mar 2015 | A1 |
| 20150101003 | Bull | Apr 2015 | A1 |
| 20150149571 | Barak et al. | May 2015 | A1 |
| 20150200822 | Zelenko et al. | Jul 2015 | A1 |
| 20150213363 | Lahav et al. | Jul 2015 | A1 |
| 20150248486 | Barak et al. | Sep 2015 | A1 |
| 20150269609 | Mehanian | Sep 2015 | A1 |
| 20150278837 | Lahav et al. | Oct 2015 | A1 |
| 20160055277 | Lahav et al. | Feb 2016 | A1 |
| 20160117736 | Barak et al. | Apr 2016 | A1 |
| 20160198509 | Hayes, Jr. | Jul 2016 | A1 |
| 20160248706 | Karidi | Aug 2016 | A1 |
| 20160380932 | Matan et al. | Dec 2016 | A1 |
| 20170011146 | Lahav et al. | Jan 2017 | A1 |
| 20170046021 | Karidi | Feb 2017 | A1 |
| 20170054701 | Barak et al. | Feb 2017 | A1 |
| 20170169081 | Barak et al. | Jun 2017 | A1 |
| 20170171047 | Freishtat et al. | Jun 2017 | A1 |
| 20170206568 | Schachar et al. | Jul 2017 | A1 |
| 20170230505 | McCarthy-Howe | Aug 2017 | A1 |
| Number | Date | Country |
|---|---|---|
| 840244 | May 1998 | EP |
| 1233361 | Aug 2002 | EP |
| 1276 064 | Jan 2003 | EP |
| 1549025 | Jun 2005 | EP |
| 1 840 803 | Oct 2007 | EP |
| 1845436 | Oct 2007 | EP |
| 1850284 | Oct 2007 | EP |
| 2 950 214 | Mar 2011 | FR |
| 9288453 | Nov 1997 | JP |
| 2004-054533 | Feb 2004 | JP |
| 2010128877 | Jun 2010 | JP |
| 20040110399 | Dec 2004 | KR |
| 20050010487 | Jan 2005 | KR |
| 20080046310 | May 2008 | KR |
| 20080097751 | Nov 2008 | KR |
| 9722073 | Jun 1997 | WO |
| 9845797 | Oct 1998 | WO |
| 9909470 | Feb 1999 | WO |
| 9922328 | May 1999 | WO |
| 9944152 | Sep 1999 | WO |
| 0057294 | Sep 2000 | WO |
| 0127825 | Apr 2001 | WO |
| 2001035272 | May 2001 | WO |
| 02065367 | Aug 2002 | WO |
| 03032146 | Apr 2003 | WO |
| 2004057473 | Jul 2004 | WO |
| 2005059777 | Jun 2005 | WO |
| 2007044757 | Apr 2007 | WO |
| 2007129625 | Nov 2007 | WO |
| 2008057181 | May 2008 | WO |
| 2008143382 | Nov 2008 | WO |
| 2009029940 | Mar 2009 | WO |
| 2010099632 | Sep 2010 | WO |
| 2010119379 | Oct 2010 | WO |
| 2010144207 | Dec 2010 | WO |
| 2011127049 | Oct 2011 | WO |
| 2013119808 | Aug 2013 | WO |
| 2013158830 | Oct 2013 | WO |
| 2013163426 | Oct 2013 | WO |
| 2015021068 | Feb 2015 | WO |
| Entry |
|---|
| “Building profitable online customer-brand relationships,” by Marco Vriens and Michael Grigsby, Marketing Management 10.4: 34-39, American Marketing Association, Nov./Dec. 2001 (Year: 2001). |
| “Navigation behavior models for link structure optimization,” by Vera Hollink, Maarten van Someren, and Bob J. Wielinga, User Modeling and User-Adapted Interaction 17.4: 339-377, Springer Nature B.V., Sep. 2007 (Year: 2007). |
| Chartrand Sabra, “A new system seeks to ease the bottleneck in the customer-service information highway,” The New York Times (Apr. 30, 2001), 2 pages. |
| Just Answer (2004 Faq) Archive.org cache of www.justanswer.com circa (Dec. 2004), 8 pages. |
| Pack Thomas, “Human Search Engines the next Killer app,” (Dec. 1, 2000) Econtent DBS vol. 23; Issue 6, 7 pages. |
| match.com “Match.com Launches Match.com Advisors,” PR Newswire (Oct. 14, 2003), 2 pages. |
| Sitel, “Sitel to Provide Live Agent Support Online for Expertcity.com,” PR Newswire (Feb. 28, 2000), 2 pages. |
| Webmaster World, “Link to my website is in a frame with banner ad at the top,” www.webmasterworld.com (Nov. 11, 2003), 2 pages. |
| Bry et al., “Realilzing Business Processes with ECA Rules: Benefits, Challenges, Limits,” Principles and Practice of Sematic Web Reasoning Lecture Notes in Computer Science, pp. 48-62, LNCS, Springer, Berlin, DE (Jan. 2006). |
| Fairisaac, “How SmartForms for Blaze Advisor Works,” www.fairisaac.com 12 pages (Jan. 2005). |
| Mesbah A et al., “A Component-and Push-Based Architectural Style for Ajax Applications,” The Journal of Systems & Software, 81 (12): pp. 2194-2209, Elsevier North Holland, New York, NY US (Dec. 2008). |
| Oracle Fusion Middleware Administrator's Guide for Oracle SOA (Oracle Guide) Suite 11g Release 1 (11.1.1) Part No. E10226-02 www.docs.oracle.com (Oct. 2009), 548 pages. |
| “OAuth core 1.0 Revision A [XP002570263],” OAuth Core Workgroups, pp. 1-27 www.ouath.net/core/1.0a/ (retrieved Jan. 31, 2013), 24 pages. |
| Anon., “AnswerSoft Announces Concerto; First to Combine Call Center Automation with Power of Web,” Business Wire, (Feb. 3, 1997) 3 pages. |
| Emigh, J., “AnswerSoft Unveils Concerto for Web-Based Call Centers Feb. 5, 1996,” Newsbytes, (Feb. 5, 1997) 2 pages. |
| Grigonis, R., “Webphony—It's not Just Callback Buttons Anymore,” Computer Telephony, (Dec. 1997) 4 pages. |
| Wagner, M., “Caring for Customers,” Internet World, (Sep. 1, 1999) 3 pages. |
| Sweat, J., “Human Touch—A New Wave of E-Service Offerings Blends the Web, E-Mail, and Voice Bringing People back into the Picture,” Information week, (Oct. 4, 1999) 2 pages. |
| Kirkpatrick, K., “Electronic Exchange 2000, the,” Computer Shopper, (Nov. 1999) 5 pages. |
| Anon., “InstantService.com Teams with Island Data to provide Integrated Solution for Online Customer Response,” Business Wire, (May 22, 2000) 3 pages. |
| Kersnar, S., “Countrywide Offers Proprietary Technology for Online Wholesale Lending,” National Mortgage News, vol. 24, No. 38, (Jun. 5, 2000) 2 pages. |
| Douglas Armstrong, Firstar Web site helps add up future, Milwaukee Journal Sentinel, (Mar. 28, 1996) 3 pages. |
| redhat .com downloaded on Jul. 23, 2006. |
| apache.org downloaded on Jul. 23, 2006. |
| mysql.com downloaded on Jul. 23, 2006. |
| developer.com downloaded on Jul. 23, 2006. |
| Canter, Ronald S., “Lender Beware-Federal Regulation of Consumer Credit”, Credit World, vol. 81, No. 5, pp. 16-20, (May 1993). |
| Staff, “On-Line System Approves Loans While Customer Waits,” Communication News, vol. 31, Issue 9, (Sep. 1994) 3 pages. |
| “Low-Rent Loan Officer in a Kiosk”, Bank Technology News vol. 8 No. 2, p (Feb. 1995) 2 pages. |
| Duclaux, Denise, “A Check for $5,000 in Ten Minutes”, ABA Banking Journal, vol. 87, No. 8, p. 45, AUQ. (1995) 2 pages. |
| “World Wide Web Enhances Customer's Choice”, Cards International, No. 143, p. 9, (Nov. 1995) 2 pages. |
| Wells Fargo Launches First Real-Time, Online Home Equity Credit Decision-Making Service, Business Wire, (Jun. 3, 1998), Dialog_ File 621: New Product Announcement, 3 pages. |
| Handley, John, “Credit Review Lets the Nos. Do the Talking in Home Mortgage Game”, Chicago Tribune (Jul. 1998) 3 pages. |
| Sherman, Lee, “Wells Fargo Writes a New Online Script”, Interactive Week, vol. 5, No. 31, p. 29, (Aug. 1998) 2 pages. |
| Calvey, Mark, “Internet Gives Bankers a Snappy Comeback”, San Francisco Business Times, vol. 13, No. 5, p. 3 (Sep. 1998) 2 pages. |
| McCormick, Linda, “Users of Credit Scoring Face Tough Rules on Notification”, American Banker, Dialog File 625: American Banker Publications, (Mar. 21, 1982) 2 pages. |
| What the Credit Bureau is Saying About You: If a Mistake Sneaks Into Your Record, You May Not Know About it Until You Get Turned Down for Credit, Changing Times, vol. 37, p. 56, (Jul. 1983) 2 pages. |
| McShane. Peter K., “Got Financing?”, Business Journal Serving Southern Tier, CNY, Mohawk Valley, Finger Lakes. North, vol. 11, Issue 19, p. 9, (Sep. 15, 1997) 3 pages. |
| Borowsky, Mark, “The Neural Net: Predictor of Fraud or Victim of Hype?”, Bank Technology News DialoQ File 16:PROMT, p. 7 (Sep. 1993) 2 pages. |
| FICO http://houseloans.idis.com/fico (2009) 1 page. |
| Altavista: search, FICO http://www.altavista.com (2001) 3 pages. |
| What Do FICO Scores Mean to Me?, http://www.sancap.com. (1999) 3 pages. |
| What is a FICO Score?, http://www.aspeenloan.com (2009) 1 page. |
| “Credit”, The New Encyclopedia Britannica vol. 3 p. 722. (1994) 3 pages. |
| “Creditnet.com—An Online Guide to Credit Cards”, http://www.creditnet/com. (1999) 1 page. |
| “Phillips 66 Introduces Mastercard with Rebate Feature”, PR Newswire, p914NY067, (Sep. 14, 1995) 1 page. |
| Anon, “VAR Agreement Expands Credit Bureau Access.”, (CCS America, Magnum Communications Ltd expand CardPac access, Computers in Banking, v6, n10, (1) (Oct. 1989) 2 pages. |
| Wortmann, Harry S., “Reengineering Update—Outsourcing: An Option Full of Benefits and Responsibilities”, American Banker, (Oct. 24, 1994), p. 7A vol. 159, No. 205 3 pages. |
| Anon. “To Boost Balances, AT&T Renews No-Fee Universal Credit Card Offer”, Gale Group Newsletter, V 10, N. 13, (Mar. 30, 1992) 2 pages. |
| Anon. “Citgo Puts a New Spin on the Cobranded Oil Card”, Credit Card News, p. 4, (Nov. 1, 1995) 2 pages. |
| Anon. “Microsoft Targets More than PIM Market with Outlook 2000,” Computer Reseller News, N. 805 p. 99, (Aug. 31, 1998) 2 pages. |
| Chesanow, Neil, “Pick the Right Credit Cards- and use them wisely”, Medical Economics, v. 75, n. 16, p. 94, (Aug. 24, 1998) 4 pages. |
| Friedland, Marc, “Credit Scoring Digs Deeper into Data”, Credit World, v. 84, n. 5 p. 19-23, (May 1996) 5 pages. |
| Hollander, Geoffrey, “Sibling Tool Personator 3 untangles File Formats”, InfoWorld, v20, n5, pp. 102 (Feb. 2, 1998) 2 pages. |
| Kantrow, Yvette D., “Banks Press Cardholders to Take Cash Advances”, American Banker, v. 157, n. 18 pp. 1-2. (Jan. 28, 1992) 2 pages. |
| Lotus News Release: “Lotus Delivers Pre-Release of Lotus Notes 4.6 Client Provides Compelling New Integration with Internet Explorer”, (May 20, 1997) 2 pages. |
| Stetenfeld, Beth, “Credit Scoring: Finding the Right Recipe”, Credit Union Management, v. 17, n 11, pp. 24-26 (Nov. 1994). |
| Block, Valerie, “Network Assembles Card Issuers at an Internet Site”, Am. Banker, V160, (1998) 1 page. |
| CreditNet Financial Network http://consumers.creditnet.com (1999) 1 page. |
| Anon., “Lending Tree: Lending Tree Provides Borrowers Fast and Easy Online Access to Multiple Loan Offers,” Business Wire, Jun. 23, 1998, 2 pages. |
| Anon, Regulation Z Commentary Amendments, Retail Banking Digest, vol. 15, No. 2, p. 17-18, (Mar.-Apr. 1995). |
| Anon, San Diego Savings Association Offers Customers No-Fee Visa Product, Card News, (Feb. 29, 1988) 1 page. |
| Bloom, J.K., “For This New Visa, Only Web Surfers Need Apply,” American Banker, vol. 1163, No. 34 12 (Feb. 20, 1998) 2 pages. |
| Harney, K.R., “Realty Brokers, Lenders Face Restrictions,” Arizona Republic, Final Chaser edition, Sun Living section, (Feb. 10, 1991) 2 pages. |
| Higgins, K.T., “Mr. Plastic Joins the Marketing Team,” Credit Card Management, vol. 6, No. 3, pp. 26-30, Jun. 1993. |
| Microsoft Press Computer Dictionary, Third Edition, Microsoft Press, Redmond, 1997, 4 pages. |
| Whiteside, D.E., “One Million and Counting,” Collections and Credit Risk, vol. 1, No. 11 (Nov. 1996) 5 pages. |
| Fickenscher, L., “Providian Undercuts rivals with 7.9% Rate Offer,” American banker, vol. 163, Oct. 8, 1998, 2 pages. |
| Fargo, J., “The Internet Specialists,” Credit Card Management, vol. 11, No. 10, pp. 38-45, Jan. 1999. |
| Lemay, T., “Browsing for a Mortgage a Click away,” Financial Post, (Jan. 15, 2000) 1 page. |
| Wijnen, R., “Banks Fortify Online Services,” Bank Technology News, vol. 13, No. 3, Mar., 2000, 3 pages. |
| Anon. “IAFC Launches NextCard, the First True Internet VISA,” Business Wire, New York: (Feb. 6, 1998), 3 pages. |
| Lazarony, Lucy, “Only Online Applicants Need Apply,” Bank Advertising News, North Palm Beach, Mar. 23, 1998, vol. 21, Issue 15, 3 pages. |
| FIData, Inc., News & Press Releases, “Instant Credit Union Loans via the Internet,” http://web.archive.org/web/19990221115203/www.fidata-inc.com/news-pr01.htm_(1999) 2 pages. |
| FIData, Inc., Press Releases, “Instant Loan Approvals via the Internet,” http://www.fidata- inc.com/news/pr_040198.htm, (Apr. 1, 1998) 2 pages. |
| Staff, “On-Line System Approves Loans While Customer Waits”—Abstract, Communication News, vol. 31, Issue 9, (Sep. 1994) 3 pages. |
| Anon. “Affordable Lending Systems Now Available for Smaller Financial Institutions,” Business Wire, (May 18, 1998), 2 pages. |
| Nexis—All News Sources—Examiner's NPL Search Results in U.S. Appl. No. 11/932,498, included with Office Action issued Oct. 8, 2008, 14 pages. |
| “Sample Experian Credit Report” by Consumer Information consumerinfo.com (Jul. 9, 1998) 4 pages. |
| Plaintiffs Original Complaint, Nextcard, LLC v. Liveperson, Inc.; Civil Action No. 2:08-cv-00184-TJW, In the U.S. District Court for the Eastern District of Texas, Marshall Division, filed Apr. 30, 2008 (7 pages). |
| Amended Complaint and Jury Demand; Liveperson, Inc. v. Nextcard, LLC , et al.; Civil Action No. 08-062 (GMS), in the U.S. District Court for the District of Delaware, filed Mar. 18, 2008 (5 pages). |
| Plaintiffs Second Amended Complaint; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); In the U.S. District Court for the Eastern District of Texas, Marshall Division, filed Apr. 9, 2008 (12 pages). |
| Defendants HSBC North America Holdings Inc.'s and HSBC USA Inc's Answer, Affirmative Defenses and Counterclaims to Plaintiffs Second Amended Complaint; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); In the U.S. District Court for the Eastern District of Texas, Marshall Division filed (Apr. 28, 2008), 13 pages. |
| Answer and Counterclaims of Defendant DFS Services LLC; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); In the U.S. District Court for the Eastern District of Texas, Marshall Division, filed Apr. 28, 2008 (13 pages). |
| Defendant the PNC Financial Services Group, Inc.'s Answer and Affirmative Defenses to Second Amended Complaint; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); In the U.S. District Court for the Eastern District of Texas, Marshall Division, filed Apr. 28, 2008, 10 pages. |
| Plaintiffs Second Amended Reply to Counterclaims of Defendants HSBC North America Holdings Inc. and HSBC USA Inc.; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); In the U.S. District Court for the Eastern District of Texas, Marshall Division, filed May 14, 2008, 5 pages. |
| Plaintiffs Second Amended Reply to Counterclaims of Defendant DFS Services LLC; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); In the U.S. District Court for the Eastern District of Texas, Marshall Division, filed May 14, 2008 (71 pages). |
| Plaintiffs Second Amended Reply to Counterclaims of Defendant American Express Company; Nextcard, LLC v. American Express Company, et al; Civil Action No. 2:07-cv-354 (TJW); In the U.S. District Court for the Eastern District of Texas, Marshall Division, filed (May 8, 2008), 8 pages. |
| Justin Hibbard, Gregory Dalton, Mary E Thyfault. (Jun. 1998). “Web-based customer care.” Information Week, (684) 18-20, 3 pages. |
| Kim S. Nash “Call all Customers.” Computerworld, 32 (1), 25-28 (Dec. 1997), 2 pages. |
| PRN: “First American Financial Acquires Tele-Track Inc.,” PR Newswire, (May 11, 1999), Proquest #41275773, 2 pages. |
| Young, Deborah, “The Information Store,” (Sep. 15, 2000), Wireless Review, pp. 42, 44, 46, 48, 50. |
| Whiting et al., “Profitable Customers,” (Mar. 29, 1999), Information Week, Issue 727, pp. 44, 45, 48, 52, 56. |
| Bayer, Judy, “A Framework for Developing and Using Retail Promotion Response Models,” Cares Integrated Solutions, retrieved from www.ceresion.com (2007) 5 pages. |
| Bayer, Judy, “Automated Response Modeling System for Targeted Marketing,” (Mar. 1998), Ceres Integrated Solutions, 5 pages. |
| Sweet et al., “Instant Marketing,” (Aug. 12, 1999), Information Week, pp. 18-20. |
| SmartKids.com “Chooses Quadstone—The Smartest Customer Data Mining Solution,” (Jul. 31, 2000), Business Wire, 2 pages. |
| “NCR's Next Generation Software Makes True Customer Relationship Management a Reality,” (Jul. 26, 1999) PR Newswire, 3 pages. |
| “Quadstone System 3.0 Meets New Market Demand for Fast, Easy-to-Use Predictive Analysis for CRM,” (May 22, 2000) Business Wire, 3 pages. |
| “Net Perceptions Alters Dynamics of Marketing Industry with Introduction of Net Perceptions for Call Centers,” (Oct. 12, 1998) PR Newswire, 3 pages. |
| “Ceres Targeted Marketing Application,” Ceres Integrated Solutions: retrieved from www.ceresios.com/Product/index.htm (2007) 3 pages. |
| Prince, C. J., E:business: A Look at the Future, Chief Executive, vol. 154, (Apr. 2000), pp. 10-11. |
| Oikarinen et al. “Internet Relay Chat Protocol” RFC-1459, pp. 1-65, (May 1993). |
| eDiet.com: Personalized Diets, Fitness, and Counseling, (May 3, 1998), pp. 1-15. |
| Fiszer, Max; “Customizing an inbound call-center with skills-based routing,” Telemarketing & Call Center Solutions, (Jan. 1997), v15i7 p. 24; Proquest #11267840, 5 pages. |
| “ESL Federal Credit Union Inaugurates Internet Target Marketing.” PR Newswire p. 4210 (Oct. 6, 1998), 3 pages. |
| “Welcome to eStara—The Industry Leader in Click to Call and Call Tracking Solutions,” e-Stara, Inc., retrieved from www.estara.com on Mar. 21, 2013, 1 page. |
| “Push to Talk Live Now! From your website” iTalkSystem, Inc., retrieved from www.italksystems.com on Mar. 21, 2013, 1 page. |
| Richardson et al., “Predicting Clicks: Estimating the Click-Through Rate for New Ads,” (May 2007) 9 pages. |
| “Welcome to Keen” retrieved from www.archive.org/web/20010302014355/http://www.keen.com/ on Jan. 25, 2013, 1 page. |
| Christophe Destruel, Herve Luga, Yves Duthen, Rene Caubet. “Classifiers based system for interface evolution.” Expersys Conference, 265-270 (1997), 6 pages. |
| Ulla de Stricker, Annie Joan Olesen. “Is Management Consulting for You?” Searcher, 48-53 (Mar. 2005), 6 pages. |
| Humberto T. Marques Neto, Leonardo C.D. Rocha, Pedro H.C. Guerra, Jussara M. Almeida, Wagner Meira Jr., Virgilio A. F. Almeida. “A Characterization of Broadband User Behavior and Their E-Business Activities.” ACM SIGMETRICS Performance Evaluation Review, 3-13 (2004), 11 pages. |
| Greg Bowman, Michael M. Danchak, Mary LaCombe, Don Porter. “Implementing the Rensselaer 80/20 Model in Professional Education.” 30th ASEE/IEEE Frontiers in Education Conference, Session T3G (Oct. 18-21, 2000), 1 page. |
| Elizabeth Sklar Rozier, Richard Alterman. “Participatory Adaptation.” CHI, 97, 261-262 (Mar. 22-27, 1997), 2 pages. |
| Frank White. “The User Interface of Expert Systems: What Recent Research Tells Us.” Library Software Review, vol. 13, No. 2, p. 91-98 (Summer 1994) 8 pages. |
| Frederick W. Rook, Michael L. Donnell. “Human Cognition and the Expert System Interface: Mental Models and Inference Explanations.” IEEE Transactions on Systems, Man, and Cybernetics, vol. 23, No. 6, p. 1649-1661 (Nov./Dec. 1993), 13 pages. |
| Francois Bry et al., “Realizing Business Processes with ECA Rules: Benefits Challenges, Limits” (2006) Principles and Practive of Semantic Web Reasoning Lecture Notes in Computer Science; LNCS Springer Belin DE pp. 48-62 XP019042871, ISBN: 978-3540-39586-7. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2013/041147, mailed Jul. 30, 2013, 9 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2013/037086, mailed Jul. 12, 2013, 9 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2013/29389, mailed Jul. 24, 2013, 8 pages. |
| International Search Report and Written Opinion for PCT Application No. PCT/US2013/038212, mailed Jul. 17, 2013, 11 pages. |
| International Search Report for PCT Application No. PCT/US03/41090, mailed on Sep. 1, 2004, 3 pages. |
| International Search Report for PCT Application No. PCT/US05/40012, mailed on Oct. 5, 2007, 2 pages. |
| International Preliminary Report on Patentability for PCT Application No. PCT/US2006/039630, dated Apr. 16, 2008, 4 pages. |
| International Search Report for PCT Application No. PCT/US2011/031239, mailed on Jul. 7, 2011, 3 pages. |
| International Search Report for PCT Application No. PCT/US2011/064946, mailed on Jun. 22, 2012, 3 pages. |
| International Preliminary Report on Patentability for PCT Application No. PCT/US2011/031239, dated Oct. 9, 2012, 8 pages. |
| Extended European Search Report dated Jul. 7, 2015 for European Patent Application No. 15161694.3; 8 pages. |
| Non-Final Office Action of Dec. 11, 2008 for U.S. Appl. No. 11/394,078, 15 pages. |
| Final Office Action of Jul. 9, 2009 for U.S. Appl. No. 11/394,078, 15 pages. |
| Non-Final Office Action of Jan. 28, 2010 for U.S. Appl. No. 11/394,078, 14 pages. |
| Final Office Action of Jul. 9, 2010 for U.S. Appl. No. 11/394,078, 16 pages. |
| Non-Final Office Action of Feb. 1, 2011 for U.S. Appl. No. 11/394,078, 20 pages. |
| Final Office Action of Aug. 2, 2011 for U.S. Appl. No. 11/394,078, 23 pages. |
| Non-Final Office Action of May 16, 2012 for U.S. Appl. No. 11/394,078, 23 pages. |
| Final Office Action of Jan. 25, 2013 for U.S. Appl. No. 11/394,078, 22 pages. |
| Non-Final Office Action of Jun. 22, 2012 for U.S. Appl. No. 13/080,324, 9 pages. |
| Non-Final Office Action of Aug. 15, 2012 for U.S. Appl. No. 12/967,782, 31 pages. |
| Non-Final Office Action of Jul. 29, 2011 for U.S. Appl. No. 12/608,117, 20 pages. |
| Final Office Action of Apr. 4, 2012 for U.S. Appl. No. 12/608,117, 25 pages. |
| Non-Final Office Action of Apr. 24, 2004 for U.S. Appl. No. 09/922,753, 16 pages. |
| Final Office Action of Oct. 14, 2004 for U.S. Appl. No. 09/922,753, 13 pages. |
| Non-Final Office Action of May 17, 2005 for U.S. Appl. No. 09/922,753, 13 pages. |
| Non-Final Office Action of Mar. 14, 2006 for U.S. Appl. No. 09/922,753, 13 pages. |
| Final Office Action of Jul. 26, 2006 for U.S. Appl. No. 09/922,753, 13 pages. |
| Non-Final Office Action of Aug. 13, 2008 for U.S. Appl. No. 09/922,753, 10 pages. |
| Final Office Action of Apr. 23, 2009 for U.S. Appl. No. 09/922,753, 11 pages. |
| Non-Final Office Action of Jul. 21, 2009 for U.S. Appl. No. 09/922,753, 10 pages. |
| Final Office Action of Feb. 18, 2010 for U.S. Appl. No. 09/922,753, 9 pages. |
| Non-Final Office Action of Apr. 25, 2011 for U.S. Appl. No. 09/922,753, 9 pages. |
| Final Office Action of Nov. 25, 2011 for U.S. Appl. No. 09/922,753, 10 pages. |
| Non-Final Office Action of Aug. 7, 2007 for U.S. Appl. No. 10/980,613, 16 pages. |
| Non-Final Office Action of May 15, 2008 for U.S. Appl. No. 10/980,613, 23 pages. |
| Non-Final Office Action of Apr. 30, 2012 for U.S. Appl. No. 12/504,265, 16 pages. |
| Final Office Action of Aug. 28, 2012 for U.S. Appl. No. 12/504,265, 28 pages. |
| Final Office Action of Feb. 14, 2013 for U.S. Appl. No. 13/080,324, 11 pages. |
| Non-Final Office Action of Mar. 30, 2013 for U.S. Appl. No. 11/360,530, 23 pages. |
| Final Office Action of Apr. 11, 2013 for U.S. Appl. No. 12/967,782, 18 pages. |
| Non-Final Office Action of May 10, 2013 for U.S. Appl. No. 13/563,708, 20 pages. |
| Non-Final Office Action of Jun. 12, 2013 for U.S. Appl. No. 12/608,117, 56 pages. |
| Non-Final Office Action of Jun. 20, 2013 for U.S. Appl. No. 13/157,936, 19 pages. |
| Non-Final Office Action of Jun. 27, 2013 for U.S. Appl. No. 12/504,265, 11 pages. |
| Non-Final Office Action of Jul. 8, 2013 for U.S. Appl. No. 13/413,197, 10 pages. |
| Final Office Action of Oct. 21, 2013 for U.S. Appl. No. 12/504,265 14 pages. |
| Non-Final Office Action of Oct. 30, 2013 for U.S. Appl. No. 13/961,072, 10 pages. |
| Non-Final Office Action of Dec. 5, 2013 for U.S. Appl. No. 12/967,782, 14 pages. |
| Non-Final Office Action of Dec. 4, 2014 for U.S. Appl. No. 14/275,698, 6 pages. |
| Notice of Allowance of Jan. 3, 2014 for U.S. Appl. No. 11/360,530, 29 pages. |
| Final Office Action of Jan. 22, 2014 for U.S. Appl. No. 12/608,117, 45 pages. |
| Final Office Action of Jan. 27, 2014 for U.S. Appl. No. 13/563,708, 35 pages. |
| Non-Final Office Action of Jan. 30, 2014 for U.S. Appl. No. 13/413,158, 19 pages. |
| Notice of Allowance of Feb. 12, 2014 for U.S. Appl. No. 13/157,936, 33 pages. |
| Final Office Action of Feb. 19, 2014 for U.S. Appl. No. 13/961,072, 35 pages. |
| Non-Final Office Action of Feb. 20, 2014 for U.S. Appl. No. 10/980,613, 43 pages. |
| Notice of Allowance of Feb. 28, 2014 for U.S. Appl. No. 09/922,753, 13 pages. |
| Notice of Allowance of Mar. 25, 2014 for U.S. Appl. No. 12/504,265 31 pages. |
| Notice of Allowance of Mar. 31, 2014 for U.S. Appl. No. 12/725,999, 41 pages. |
| Notice of Allowance of Mar. 30, 2015 for U.S. Appl. No. 14/275,698, 11 pages. |
| Notice of Allowance of Apr. 1, 2014 for U.S. Appl. No. 13/413,197, 32 pages. |
| Non-Final Office Action of Jul. 17, 2014 for U.S. Appl. No. 11/394,078, 41 pages. |
| Non-Final Office Action of Jul. 31, 2014 for U.S. Appl. No. 13/080,324, 38 pages. |
| Notice of Allowance of Aug. 18, 2014 for U.S. Appl. No. 12/967,782, 43 pages. |
| Non-Final Office Action of Aug. 21, 2014 for U.S. Appl. No. 10/980,613, 43 pages. |
| Final Office Action of Mar. 12, 2015 for U.S. Appl. No. 13/080,324, 13 pages. |
| Non-Final Office Action of Mar. 13, 2015 for U.S. Appl. No. 13/841,434, 26 pages. |
| Non-Final Office Action of Apr. 9, 2015 for U.S. Appl. No. 13/830,719, 24 pages. |
| Final Office Action of Apr. 7, 2015 for U.S. Appl. No. 11/394,078, 18 pages. |
| Non-Final Office Action of Apr. 6, 2015 for U.S. Appl. No. 14/322,736, 13 pages. |
| Non-Final Office Action of May 7, 2015 for U.S. Appl. No. 13/829,708, 16 pages. |
| Final Office Action of May 8, 2015 for U.S. Appl. No. 10/980,613, 18 pages. |
| Non-Final Office Action of May 13, 2015 for U.S. Appl. No. 14/317,346, 21 pages. |
| Non-Final Office Acton of Jun. 2, 2015 for U.S. Appl. No. 12/608,117, 26 pages. |
| First Action Pre-Interview Communication of Jun. 19, 2015 for U.S. Appl. No. 14/244,830, 7 pages. |
| Non-Final Office Action of Jul. 20, 2015 for U.S. Appl. No. 14/711,609; 12 pages. |
| Non-Final Office Action of Jul. 20, 2015 for U.S. Appl. No. 14/500,537; 12 pages. |
| Final Office Action of Jul. 31, 2015 for U.S. Appl. No. 14/317,346, 13 pages. |
| Final Office Action of Aug. 10, 2015 for U.S. Appl. No. 13/961,072, 12 pages. |
| Non-Final Office Action of Aug. 14, 2015 for U.S. Appl. No. 14/543,397, 12 pages. |
| Non-Final Office Action of Aug. 18, 2015 for U.S. Appl. No. 14/570,963, 23 pages. |
| Non-Final Office Action of Aug. 27, 2015 for U.S. Appl. No. 11/394,078, 21 pages. |
| Non-Final Office Action of Sep. 11, 2015 for U.S. Appl. No. 14/500,502; 12 pages. |
| Final Office Action of Sep. 18, 2015 for U.S. Appl. No. 14/288,258, 17 pages. |
| Notice of Allowance of Sep. 18, 2015 for U.S. Appl. No. 14/244,830, 11 pages. |
| First Action Interview Pilot Program Pre-Interview Communication of Oct. 21, 2015 for U.S. Appl. No. 14/313,511, 3 pages. |
| Final Office Action of Oct. 22, 2015 for U.S. Appl. No. 13/830,719, 29 pages. |
| Final Office Action of Nov. 10, 2015 for U.S. Appl. No. 13/841,434; 30 pages. |
| Final Office Acton of Nov. 17, 2015 for U.S. Appl. No. 12/608,117, 32 pages. |
| Non-Final Office Action of Dec. 4, 2015 for U.S. Appl. No. 10/980,613 21 pages. |
| Non-Final Office Action of Dec. 24, 2015 for U.S. Appl. No. 14/317,346, 15 pages. |
| Notice of Allowance of Dec. 30, 2015 for U.S. Appl. No. 14/322,736, 9 pages. |
| Non-Final Office Action of Jan. 5, 2016 for U.S. Appl. No. 14/245,400, 33 pages. |
| Notice of Allowance of Jan. 7, 2016 for U.S. Appl. No. 14/313,511, 5 pages. |
| First Action Pre-Interview Communication of Jan. 12, 2016 for U.S. Appl. No. 14/753,496, 3 pages. |
| Notice of Allowance of Jan. 20, 2016 for U.S. Appl. No. 13/829,708, 11 pages. |
| Final Office Action of Jan. 29, 2016 for U.S. Appl. No. 14/711,609; 15 pages. |
| Final Office Action of Jan. 29, 2016 for U.S. Appl. No. 14/500,537; 15 pages. |
| Non-Final Office Action of Feb. 12, 2016 for U.S. Appl. No. 13/080,324, 15 pages. |
| Notice of Allowance of Mar. 16, 2016 for U.S. Appl. No. 14/582,550; 9 pages. |
| Notice of Allowance of Mar. 21, 2016 for U.S. Appl. No. 14/753,496; 5 pages. |
| Final Office Action of Apr. 14, 2016 for U.S. Appl. No. 10/980,613, 21 pages. |
| Final Office Action of Apr. 21, 2016 for U.S. Appl. No. 14/317,346, 17 pages. |
| Non-Final Office Action of Apr. 22, 2016 for U.S. Appl. No. 14/288,258 11 pages. |
| Notice of Allowance of Apr. 22, 2016 for U.S. Appl. No. 11/394,078, 16 pages. |
| Non-Final Office Action of May 12, 2016 for U.S. Appl. No. 13/961,072, 12 pages. |
| Non-Final Office Acton of May 23, 2016 for U.S. Appl. No. 12/608,117, 35 pages. |
| Final Office Action of Jun. 9, 2016 for U.S. Appl. No. 14/543,397, 18 pages. |
| Final Office Action of Jun. 17, 2016 for U.S. Appl. No. 14/570,963, 18 pages. |
| Notice of Allowance of Jun. 23, 2016 for U.S. Appl. No. 13/830,719; 26 pages. |
| Final Office Action of Jun. 28, 2016 for U.S. Appl. No. 14/500,502, 10 pages. |
| Final Office Action of Jul. 12, 2016 for U.S. Appl. No. 14/245,400, 36 pages. |
| First Action Pre-Interview Communication of Jul. 14, 2016 for U.S. Appl. No. 14/970,225. |
| Final Office Action of Sep. 8, 2016 for U.S. Appl. No. 13/080,324, 15 pages. |
| Notice of Allowance of Sep. 21, 2016 for U.S. Appl. No. 14/711,609, 22 pages. |
| Notice of Allowance of Sep. 22, 2016 for U.S. Appl. No. 14/500,537, 19 pages. |
| Notice of Allowance of Sep. 23, 2016 for U.S. Appl. No. 13/841,434, 15 pages. |
| Notice of Allowance of Sep. 30, 2016 for U.S. Appl. No. 14/317,346, 19 pages. |
| Notice of Allowance of Oct. 7, 2016 for U.S. Appl. No. 14/288,258, 10 pages. |
| Non-Final Office Action of Jan. 13, 2017 for U.S. Appl. No. 14/543,397, 19 pages. |
| Non-Final Office Action of Jan. 9, 2017 for U.S. Appl. No. 14/570,963, 16 pages. |
| Notice of Allowance of Jan. 13, 2017 for U.S. Appl. No. 15/294,441, 10 pages. |
| Pre-Interview First Office Action of Apr. 3, 2017 for U.S. Appl. No. 15/384,895, 7 pages. |
| Non-Final Office Action of Mar. 27, 2017 for U.S. Appl. No. 14/245,400; 43 pages. |
| Notice of Allowance of May 22, 2017 for U.S. Appl. No. 13/080,324; 10 pages. |
| Non-Final Office Action of Jul. 17, 2017 for U.S. Appl. No. 15/131,777; 11 pages. |
| Non-Final Office Action of Sep. 7, 2017 for U.S. Appl. No. 15/273,863, 29 pages. |
| Pre-Interview First Office Action of Sep. 11, 2017 for U.S. Appl. No. 15/409,720, 6 pages. |
| Final Office Action of Sep. 22, 2017 for U.S. Appl. No. 14/543,397, 18 pages. |
| Non-Final Office Action of Sep. 25, 2017 for U.S. Appl. No. 15/632,069, 12 pages. |
| Final Office Action of Oct. 6, 2017 for U.S. Appl. No. 14/570,963, 17 pages. |
| Notice of Allowance of Oct. 2, 2017 for U.S. Appl. No. 15/595,590, 9 pages. |
| Notice of Allowance of Dec. 8, 2017 for U.S. Appl. No. 15/409,720, 9 pages. |
| Final Office Action of Jan. 4, 2018 for U.S. Appl. No. 14/245,400; 22 pages. |
| Final Office Action of Jan. 9, 2018 for U.S. Appl. No. 15/384,895, 10 pages. |
| Non-Final Office Action of Feb. 8, 2018 for U.S. Appl. No. 14/570,963; 25 pages. |
| Non-Final Office Action of Mar. 19, 2018 for U.S. Appl. No. 15/084,133; 16 pages. |
| Non-Final Office Action of Jun. 4, 2018 for U.S. Appl. No. 15/682,186; 13 pages. |
| Non-Final Office Action of Jul. 12, 2018 for U.S. Appl. No. 15/860,378; 7 pages. |
| Final Office Action of Jul. 11, 2018 for U.S. Appl. No. 15/273,863; 29 pages. |
| Notice of Allowance of Jul. 23, 2018 for U.S. Appl. No. 15/171,525; 14 pages. |
| Notice of Allowance of Sep. 12, 2018 for U.S. Appl. No. 15/213,776; 8 pages. |
| Non-Final Office Action of Oct. 4, 2018 for U.S. Appl. No. 15/389,598; 21 pages. |
| Final Office Action of Dec. 13, 2018 for U.S. Appl. No. 14/570,963; 32 pages. |
| Non-Final Office Action of Jan. 24, 2019 for U.S. Appl. No. 15/273,863; 29 pages. |
| Notice of Allowance of Feb. 1, 2019 for U.S. Appl. No. 15/084,133; 8 pages. |
| Notice of Allowance of Feb. 28, 2019 for U.S. Appl. No. 15/860,378; 7 pages. |
| Non-Final Office Action of Mar. 7, 2019 for U.S. Appl. No. 15/682,186; 12 pages. |
| Final Office Action of Apr. 25, 2019 for U.S. Appl. No. 14/245,400; 25 pages. |
| Final Office Action of May 14, 2019 for U.S. Appl. No. 15/389,598; 19 pages. |
| Non-Final Office Action of Jun. 25, 2019 for U.S. Appl. No. 16/218,052; 8 pages. |
| Non-Final Office Action of Aug. 7, 2019 for U.S. Appl. No. 16/353,321; 10 pages. |
| Final Office Action of Aug. 7, 2019 for U.S. Appl. No. 15/273,863; 33 pages. |
| Notice of Allowance of Aug. 14, 2019 for U.S. Appl. No. 15/384,895; 8 pages. |
| Non-Final Office Action of Sep. 20, 2019 for U.S. Appl. No. 15/682,186; 13 pages. |
| Non-Final Office Action of Dec. 4, 2019 for U.S. Appl. No. 15/182,310; 8 pages. |
| Non-Final Office Action of Dec. 31, 2019 for U.S. Appl. No. 16/026,603; 7 pages. |
| Final Office Action of Nov. 4, 2019 for U.S. Appl. No. 16/353,321; 14 pages. |
| Non-Final Office Action of Mar. 17, 2020 for U.S. Appl. No. 15/273,863; 25 pages. |
| Final Office Action of Apr. 9, 2020 for U.S. Appl. No. 16/218,052; 15 pages. |
| Non-Final Office Action of Oct. 2, 2020 for U.S. Appl. No. 15/912,761; 8 pages. |
| Final Office Action of Jun. 10, 2021 for U.S. Appl. No. 15/912,761; 11 pages. |
| Notice of Allowance of Mar. 21, 2022 for U.S. Appl. No. 15/912,761; 11 pages. |
| Non-Final Office Action of Jun. 14, 2021 for U.S. Appl. No. 14/245,400; 24 pages. |
| Notice of Allowance of Mar. 7, 2022 for U.S. Appl. No. 14/245,400; 18 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20230098620 A1 | Mar 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61973042 | Mar 2014 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14245400 | Apr 2014 | US |
| Child | 17832823 | US |
