A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever.
The subject matter discussed in the background section should not be assumed to be prior art merely as a result of its mention in the background section. Similarly, a problem mentioned in the background section or associated with the subject matter of the background section should not be assumed to have been previously recognized in the prior art. The subject matter in the background section merely represents different approaches, which in and of themselves may also be inventions.
A set of users U interacted with some of the objects o in a universe of objects O in a particular pre-defined way, with varying degrees of success. (u, o), uϵU, oϵO, denotes an interacting (user, object) pair, and an interaction strength wuo is associated with such a pair. A personalized recommendation model recommends, for any user u, objects in O that are similar to the objects o with which the user u has previously interacted. The higher the interaction strength, the more positive the influence the properties of o should have for recommending new objects to the user u. A personalized recommendation system may build a personalized recommendation model Mu, one for each user u, from the historical interaction data of the user u. This historical interaction data of the user u is Du={(o, wuo)|wuo>0}, where wuo>0 is an indicator that user u has interacted with object o. Mu uses the content of object o and the interaction strength of wuo of (u, o) to make recommendations. The personalized recommendation model Mu uses a score function Muscore(o) to assign a score to any object oϵO, reflecting on how similar object o is to user u's data DU on which the model Mu was trained. This score function is used for recommending new objects to user u.
A personalized recommendation system has challenges in evaluating when the personalized recommendation models {Mu} are “good enough” to be used in production and also in evaluating potential improvements to the personalized recommendation models {Mu}. Such evaluations seem to require human identification of objects that form good recommendations for a sufficiently large set of users, and require human identification of objects that form bad recommendations for a sufficiently large set of users. Such human identification, which might be very useful, tends to be very laborious and error-prone. Accordingly, it is desirable to provide techniques for evaluating personalized recommendation models that do not require such human identification.
In the following drawings like reference numbers are used to refer to like elements. Although the following figures depict various examples, the one or more implementations are not limited to the examples depicted in the figures.
General Overview
Systems and methods are provided for evaluating personalized recommendation models. As used herein, the term multi-tenant database system refers to those systems in which various elements of hardware and software of the database system may be shared by one or more customers. For example, a given application server may simultaneously process requests for a great number of customers, and a given database table may store rows for a potentially much greater number of customers. As used herein, the term query plan refers to a set of steps used to access information in a database system. Next, mechanisms and methods for evaluating personalized recommendation models will be described with reference to example embodiments. The following detailed description will first describe a method for evaluating personalized recommendation models. Next, example objects for evaluating personalized recommendation models are described.
In accordance with embodiments described herein, there are provided systems and methods for evaluating personalized recommendation models. A system uses a personalized recommendation model to score each object in test set of objects, which includes an interaction set of objects with which a user interacted and in a random set of objects with which the user lacks a known interaction. The system sorts each scored object based on a decreasing order of each corresponding score, and identifies a high scoring set of the sorted objects with a specified number (equal to the total number of objects in the interaction set of objects) of the highest corresponding scores. The system aggregates a corresponding order value for each object in the high scoring set that is also in the interaction set of objects. The corresponding order value for an object is based on a corresponding order for the object in the high scoring set. The system evaluates the personalized recommendation model for the user by dividing the aggregated order value by an aggregation of a corresponding order value for each object in the high scoring set.
In a simplified example, after training a personalized recommendation model on half of a sales representative's six accounts, the system uses the model to score a test set of accounts that includes the sales representative's three remaining accounts and a random sampling of three accounts from the universe of accounts which the model may score. The system sorts the six scored accounts in descending order based on their scores, and identifies the three accounts with the top three scores, which could be the sales representative's three remaining accounts if the model made perfect recommendations. In this example, the highest scoring account has an order value of 3, the second highest scoring account has an order value of 2, and the third highest scoring account has an order value of 1. The system aggregates the relevance-adjusted order values for each account in the top three scoring accounts that are also the sales representative's accounts, all of which are expected to be in the top three scoring accounts. Therefore, the system aggregates the order value of 3 with the order value of 2 to result in an actual aggregated order value of 5 because the top two scoring accounts are the sales representative's accounts, but does not aggregate the order value of 1 because the third highest scoring account was randomly selected from the universe of all accounts and is not one of the sales representative's accounts. The system aggregates the order value of 3 with the order value of 2 and the order value of 1 to result in a potential maximum aggregated order value of 6. The system divides the actual aggregated order value of 5 by the potential maximum aggregated order value of 6 to result in an evaluation of the model as the fraction ⅚, or 0.83 in decimal form. For this example, the highest evaluation would have produced the fraction 6/6, or 1.0 in decimal form. The system may repeat the process to evaluate all personalized recommendation models for all sales representatives, and then average all of the evaluations to produce a comprehensive evaluation of the recommendation model upon which all of the personalized recommendation models are based.
While one or more implementations and techniques are described with reference to an embodiment in which evaluating personalized recommendation models is implemented in a system having an application server providing a front end for an on-demand database service capable of supporting multiple tenants, the one or more implementations and techniques are not limited to multi-tenant databases nor deployment on application servers. Embodiments may be practiced using other database architectures, i.e., ORACLE®, DB2® by IBM and the like without departing from the scope of the embodiments claimed.
Any of the embodiments described herein may be used alone or together with one another in any combination. The one or more implementations encompassed within this specification may also include embodiments that are only partially mentioned or alluded to or are not mentioned or alluded to at all in this brief summary or in the abstract. Although various embodiments may have been motivated by various deficiencies with the prior art, which may be discussed or alluded to in one or more places in the specification, the embodiments do not necessarily address any of these deficiencies. In other words, different embodiments may address different deficiencies that may be discussed in the specification. Some embodiments may only partially address some deficiencies or just one deficiency that may be discussed in the specification, and some embodiments may not address any of these deficiencies.
The system optionally trains a personalized recommendation model on a training set of objects which include only some of the objects with which a user interacted, block 102. For example and without limitation, this can include the system training a personalized recommendation model on a randomly selected half of a sales representative's six accounts, which are account A, account C, and account E depicted in bold in
Although the sales representative's six accounts {A, B, C, D, E, F} are equally distributed between San Francisco {A, C, F} and San Jose {B, D, E}, and equally distributed among very small businesses {A, C, D} and small businesses {B, E, F}, the random sampling resulted in the training set {A, C, E,} which is weighted more to San Francisco and very small businesses. All of the accounts {A, B, C, D, E, F} are Northern California-based information technology businesses that are either very small or small.
Having optionally trained a personalized recommendation model on some of the objects with which a user interacted, the personalized recommendation model scores each object in the test set of objects, which includes an interaction set of objects, which is the remaining objects with which a user interacted, and a random set of objects with which the user lacks known interaction, block 104. By way of example and without limitation, this can include the system using the model to score a test set of accounts that includes the sales representative's three remaining accounts {B, D, F}, which may be referred to as positive objects, and a random sampling of three accounts {X. Y, Z} from the universe of accounts which the model may score, which may be referred to as negative objects. Although this example describes the system using exactly half of the objects which with a user interacted for testing a personalized recommendation model, the system may use any representative sampling of the objects which with a user interacted for testing the model. Similarly, although this example describes using a number of randomly sampled objects from the universe of objects that equals the number which is exactly half of the objects which with a user interacted, the system may use any representative random sampling of objects from the universe of objects. Since the random sampling is from the universe of accounts which the model may score, a small possibility exists that the user interacted with some of these randomly sampled accounts, but no known user interaction is used in the random sampling process. The accounts {X. Y, Z} are depicted in gray in
After the model scores the objects in a test set of objects, the system sorts each scored object based on a decreasing order of each corresponding score, block 106. In embodiments, this can include the system sorting the six scored accounts {B, D, F, X, Y, Z} in descending order based on their scores, which results in the order {B, Z, D, F, Y, X} depicted in
After sorting the scored objects, the system identifies a high scoring set of sorted objects with a number of highest corresponding scores, wherein the number equals the total number of objects in the interaction set of objects, block 108. For example and without limitation, this can include the system identifying the three accounts {B, Z, D} with the top scores {68. 67. 66}, which would be the sales representative's three remaining accounts if the model made perfect recommendations.
After identifying the highest scoring objects, the system aggregates a corresponding relevance-adjusted order value for each object in a high scoring set that is also in an interaction set of objects, wherein a corresponding order value for an object is based on a corresponding order for the object in the high scoring set, block 110. For this example, the system aggregates the order values for each account in the top three scoring accounts that are also the sales representative's accounts, all of which are expected to be in the top three scoring accounts.
After aggregating order values for high scoring objects that are in the user's set of objects, the system evaluates the personalized recommendation model for the user by dividing the aggregated order value by an aggregation of a corresponding order value for each object in the high scoring set, block 112.
In an optional version of block 110, aggregating the corresponding order value for each object in the high scoring set that is also in the interaction set of objects includes weighting an order value for an object by an interaction value that corresponds to an interaction of the user with the object. Therefore, rather than simply aggregating account B's order value of 3 and account D's order value of 2 depicted in
In an optional version of block 112, the aggregation of the corresponding order value for each object in the high scoring set is based on resorting each scored object based on a decreasing order of a corresponding interaction value, and weighting an order value for each object by a corresponding interaction value. Therefore, rather than simply aggregating the order value of 3 and the order value of 2 and the order value of 1 depicted in
In an example based on the objects depicted in
Having evaluated the model for a single user, the system optionally evaluates the personalized recommendation model for each of multiple users, including the user, block 114. For example and without limitation, this can include the system repeating the process described in blocks 102-112 to evaluate all personalized recommendation models for all sales representatives.
Having evaluated the models for multiple users, the system optionally comprehensively evaluates the recommendation model upon which the personalized recommendation models is based by averaging the evaluation of the personalized recommendation model for each of the multiple users, block 116. By way of example and without limitation, this can include the system averaging all of the evaluations of all personalized recommendation models to produce a comprehensive evaluation of the recommendation model upon which all of the personalized recommendation models are based.
The method 100 may be repeated as desired. Although this disclosure describes the blocks 102-116 executing in a particular order, the blocks 102-116 may be executed in a different order. In other implementations, each of the blocks 102-116 may also be executed in combination with other blocks and/or some blocks may be divided into a different set of blocks.
As described above,
As described above,
As described above,
As described above,
System Overview
The environment 310 is an environment in which an on-demand database service exists. A user system 312 may be any machine or system that is used by a user to access a database user system. For example, any of the user systems 312 may be a handheld computing device, a mobile phone, a laptop computer, a work station, and/or a network of computing devices. As illustrated in
An on-demand database service, such as the system 316, is a database system that is made available to outside users that do not need to necessarily be concerned with building and/or maintaining the database system, but instead may be available for their use when the users need the database system (e.g., on the demand of the users). Some on-demand database services may store information from one or more tenants stored into tables of a common database image to form a multi-tenant database system (MTS). Accordingly, the “on-demand database service 316” and the “system 316” will be used interchangeably herein. A database image may include one or more database objects. A relational database management system (RDMS) or the equivalent may execute storage and retrieval of information against the database object(s). The application platform 318 may be a framework that allows the applications of the system 316 to run, such as the hardware and/or software, e.g., the operating system. In an embodiment, the on-demand database service 316 may include the application platform 318 which enables creation, managing and executing one or more applications developed by the provider of the on-demand database service, users accessing the on-demand database service via user systems 312, or third party application developers accessing the on-demand database service via the user systems 312.
The users of the user systems 312 may differ in their respective capacities, and the capacity of a particular user system 312 might be entirely determined by permissions (permission levels) for the current user. For example, where a salesperson is using a particular user system 312 to interact with the system 316, that user system 312 has the capacities allotted to that salesperson. However, while an administrator is using that user system 312 to interact with the system 316, that user system 312 has the capacities allotted to that administrator. In systems with a hierarchical role model, users at one permission level may have access to applications, data, and database information accessible by a lower permission level user, but may not have access to certain applications, database information, and data accessible by a user at a higher permission level. Thus, different users will have different capabilities with regard to accessing and modifying application and database information, depending on a user's security or permission level.
The network 314 is any network or combination of networks of devices that communicate with one another. For example, the network 314 may be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration. As the most common type of computer network in current use is a TCP/IP (Transfer Control Protocol and Internet Protocol) network, such as the global internetwork of networks often referred to as the “Internet” with a capital “I,” that network will be used in many of the examples herein. However, it should be understood that the networks that the one or more implementations might use are not so limited, although TCP/IP is a frequently implemented protocol.
The user systems 312 might communicate with the system 316 using TCP/IP and, at a higher network level, use other common Internet protocols to communicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTP is used, the user systems 312 might include an HTTP client commonly referred to as a “browser” for sending and receiving HTTP messages to and from an HTTP server at the system 316. Such an HTTP server might be implemented as the sole network interface between the system 316 and the network 314, but other techniques might be used as well or instead. In some implementations, the interface between the system 316 and the network 314 includes load sharing functionality, such as round-robin HTTP request distributors to balance loads and distribute incoming HTTP requests evenly over a plurality of servers. At least as for the users that are accessing that server, each of the plurality of servers has access to the MTS' data; however, other alternative configurations may be used instead.
In one embodiment, the system 316, shown in
One arrangement for elements of the system 316 is shown in
Several elements in the system shown in
According to one embodiment, each of the user systems 312 and all of its components are operator configurable using applications, such as a browser, including computer code run using a central processing unit such as an Intel Pentium® processor or the like. Similarly, the system 316 (and additional instances of an MTS, where more than one is present) and all of their components might be operator configurable using application(s) including computer code to run using a central processing unit such as the processor system 317, which may include an Intel Pentium® processor or the like, and/or multiple processor units. A computer program product embodiment includes a machine-readable storage medium (media) having instructions stored thereon/in which can be used to program a computer to perform any of the processes of the embodiments described herein. Computer code for operating and configuring the system 316 to intercommunicate and to process webpages, applications and other data and media content as described herein are preferably downloaded and stored on a hard disk, but the entire program code, or portions thereof, may also be stored in any other volatile or non-volatile memory medium or device as is well known, such as a ROM or RAM, or provided on any media capable of storing program code, such as any type of rotating media including floppy disks, optical discs, digital versatile disk (DVD), compact disk (CD), microdrive, and magneto-optical disks, and magnetic or optical cards, nanosystems (including molecular memory ICs), or any type of media or device suitable for storing instructions and/or data. Additionally, the entire program code, or portions thereof, may be transmitted and downloaded from a software source over a transmission medium, e.g., over the Internet, or from another server, as is well known, or transmitted over any other conventional network connection as is well known (e.g., extranet, VPN, LAN, etc.) using any communication medium and protocols (e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.) as are well known. It will also be appreciated that computer code for implementing embodiments can be implemented in any programming language that can be executed on a client system and/or server or server system such as, for example, C, C++, HTML, any other markup language, Java™, JavaScript, ActiveX, any other scripting language, such as VBScript, and many other programming languages as are well known may be used. (Java™ is a trademark of Sun Microsystems, Inc.).
According to one embodiment, the system 316 is configured to provide webpages, forms, applications, data and media content to the user (client) systems 312 to support the access by the user systems 312 as tenants of the system 316. As such, the system 316 provides security mechanisms to keep each tenant's data separate unless the data is shared. If more than one MTS is used, they may be located in close proximity to one another (e.g., in a server farm located in a single building or campus), or they may be distributed at locations remote from one another (e.g., one or more servers located in city A and one or more servers located in city B). As used herein, each MTS could include one or more logically and/or physically connected servers distributed locally or across one or more geographic locations. Additionally, the term “server” is meant to include a computer system, including processing hardware and process space(s), and an associated storage system and database application (e.g., OODBMS or RDBMS) as is well known in the art. It should also be understood that “server system” and “server” are often used interchangeably herein. Similarly, the database object described herein can be implemented as single databases, a distributed database, a collection of distributed databases, a database with redundant online or offline backups or other redundancies, etc., and might include a distributed database or storage network and associated processing intelligence.
The user systems 312, the network 314, the system 316, the tenant data storage 322, and the system data storage 324 were discussed above in
The application platform 318 includes the application setup mechanism 438 that supports application developers' creation and management of applications, which may be saved as metadata into the tenant data storage 322 by the save routines 436 for execution by subscribers as one or more tenant process spaces 404 managed by the tenant management process 410 for example. Invocations to such applications may be coded using the PL/SOQL 434 that provides a programming language style interface extension to the API 432. A detailed description of some PL/SOQL language embodiments is discussed in commonly owned U.S. Pat. No. 7,730,478 entitled, METHOD AND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA A MULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, filed Sep. 21, 2007, which is incorporated in its entirety herein for all purposes. Invocations to applications may be detected by one or more system processes, which manages retrieving the application metadata 416 for the subscriber making the invocation and executing the metadata as an application in a virtual machine.
Each application server 400 may be communicably coupled to database systems, e.g., having access to the system data 325 and the tenant data 323, via a different network connection. For example, one application server 4001 might be coupled via the network 314 (e.g., the Internet), another application server 400N-1 might be coupled via a direct network link, and another application server 400N might be coupled by yet a different network connection. Transfer Control Protocol and Internet Protocol (TCP/IP) are typical protocols for communicating between application servers 400 and the database system. However, it will be apparent to one skilled in the art that other transport protocols may be used to optimize the system depending on the network interconnect used.
In certain embodiments, each application server 400 is configured to handle requests for any user associated with any organization that is a tenant. Because it is desirable to be able to add and remove application servers from the server pool at any time for any reason, there is preferably no server affinity for a user and/or organization to a specific application server 400. In one embodiment, therefore, an interface system implementing a load balancing function (e.g., an F5 Big-IP load balancer) is communicably coupled between the application servers 400 and the user systems 312 to distribute requests to the application servers 400. In one embodiment, the load balancer uses a least connections algorithm to route user requests to the application servers 400. Other examples of load balancing algorithms, such as round robin and observed response time, also can be used. For example, in certain embodiments, three consecutive requests from the same user could hit three different application servers 400, and three requests from different users could hit the same application server 400. In this manner, the system 316 is multi-tenant, wherein the system 316 handles storage of, and access to, different objects, data and applications across disparate users and organizations.
As an example of storage, one tenant might be a company that employs a sales force where each salesperson uses the system 316 to manage their sales process. Thus, a user might maintain contact data, leads data, customer follow-up data, performance data, goals and progress data, etc., all applicable to that user's personal sales process (e.g., in the tenant data storage 322). In an example of a MTS arrangement, since all of the data and the applications to access, view, modify, report, transmit, calculate, etc., can be maintained and accessed by a user system having nothing more than network access, the user can manage his or her sales efforts and cycles from any of many different user systems. For example, if a salesperson is visiting a customer and the customer has Internet access in their lobby, the salesperson can obtain critical updates as to that customer while waiting for the customer to arrive in the lobby.
While each user's data might be separate from other users' data regardless of the employers of each user, some data might be organization-wide data shared or accessible by a plurality of users or all of the users for a given organization that is a tenant. Thus, there might be some data structures managed by the system 316 that are allocated at the tenant level while other data structures might be managed at the user level. Because an MTS might support multiple tenants including possible competitors, the MTS should have security protocols that keep data, applications, and application use separate. Also, because many tenants may opt for access to an MTS rather than maintain their own system, redundancy, up-time, and backup are additional functions that may be implemented in the MTS. In addition to user-specific data and tenant specific data, the system 316 might also maintain system level data usable by multiple tenants or other data. Such system level data might include industry reports, news, postings, and the like that are sharable among tenants.
In certain embodiments, the user systems 312 (which may be client systems) communicate with the application servers 400 to request and update system-level and tenant-level data from the system 316 that may require sending one or more queries to the tenant data storage 322 and/or the system data storage 324. The system 316 (e.g., an application server 400 in the system 316) automatically generates one or more SQL statements (e.g., one or more SQL queries) that are designed to access the desired information. The system data storage 324 may generate query plans to access the requested data from the database.
Each database can generally be viewed as a collection of objects, such as a set of logical tables, containing data fitted into predefined categories. A “table” is one representation of a data object, and may be used herein to simplify the conceptual description of objects and custom objects. It should be understood that “table” and “object” may be used interchangeably herein. Each table generally contains one or more data categories logically arranged as columns or fields in a viewable schema. Each row or record of a table contains an instance of data for each category defined by the fields. For example, a CRM database may include a table that describes a customer with fields for basic contact information such as name, address, phone number, fax number, etc. Another table might describe a purchase order, including fields for information such as customer, product, sale price, date, etc. In some multi-tenant database systems, standard entity tables might be provided for use by all tenants. For CRM database applications, such standard entities might include tables for Account, Contact, Lead, and Opportunity data, each containing pre-defined fields. It should be understood that the word “entity” may also be used interchangeably herein with “object” and “table”.
In some multi-tenant database systems, tenants may be allowed to create and store custom objects, or they may be allowed to customize standard entities or objects, for example by creating custom fields for standard objects, including custom index fields. U.S. Pat. No. 7,779,039, filed Apr. 2, 2004, entitled “Custom Entities and Fields in a Multi-Tenant Database System”, which is hereby incorporated herein by reference, teaches systems and methods for creating custom objects as well as customizing standard objects in a multi-tenant database system. In certain embodiments, for example, all custom entity data rows are stored in a single multi-tenant physical table, which may contain multiple logical tables per organization. It is transparent to customers that their multiple “tables” are in fact stored in one large table or that their data may be stored in the same table as the data of other customers.
While one or more implementations have been described by way of example and in terms of the specific embodiments, it is to be understood that one or more implementations are not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements.
Number | Name | Date | Kind |
---|---|---|---|
5577188 | Zhu | Nov 1996 | A |
5583763 | Atcheson | Dec 1996 | A |
5608872 | Schwartz | Mar 1997 | A |
5649104 | Carleton | Jul 1997 | A |
5715450 | Ambrose et al. | Feb 1998 | A |
5761419 | Schwartz | Jun 1998 | A |
5819038 | Carleton | Oct 1998 | A |
5821937 | Tonelli et al. | Oct 1998 | A |
5831610 | Tonelli et al. | Nov 1998 | A |
5873096 | Lim et al. | Feb 1999 | A |
5918159 | Fomukong et al. | Jun 1999 | A |
5963953 | Cram et al. | Oct 1999 | A |
6092083 | Brodersen et al. | Jul 2000 | A |
6161149 | Achacoso et al. | Dec 2000 | A |
6169534 | Raffel et al. | Jan 2001 | B1 |
6178425 | Brodersen et al. | Jan 2001 | B1 |
6189011 | Lim et al. | Feb 2001 | B1 |
6216135 | Brodersen et al. | Apr 2001 | B1 |
6233617 | Rothwein et al. | May 2001 | B1 |
6266669 | Brodersen et al. | Jul 2001 | B1 |
6295530 | Ritchie et al. | Sep 2001 | B1 |
6324568 | Diec et al. | Nov 2001 | B1 |
6324693 | Brodersen et al. | Nov 2001 | B1 |
6336137 | Lee et al. | Jan 2002 | B1 |
D454139 | Feldcamp et al. | Mar 2002 | S |
6367077 | Brodersen et al. | Apr 2002 | B1 |
6393605 | Loomans | May 2002 | B1 |
6405220 | Brodersen et al. | Jun 2002 | B1 |
6434550 | Warner et al. | Aug 2002 | B1 |
6446089 | Brodersen et al. | Sep 2002 | B1 |
6535909 | Rust | Mar 2003 | B1 |
6549908 | Loomans | Apr 2003 | B1 |
6553563 | Ambrose et al. | Apr 2003 | B2 |
6560461 | Fomukong et al. | May 2003 | B1 |
6574635 | Stauber et al. | Jun 2003 | B2 |
6577726 | Huang et al. | Jun 2003 | B1 |
6601087 | Zhu | Jul 2003 | B1 |
6604117 | Lim et al. | Aug 2003 | B2 |
6604128 | Diec | Aug 2003 | B2 |
6609150 | Lee et al. | Aug 2003 | B2 |
6621834 | Scherpbier | Sep 2003 | B1 |
6654032 | Zhu | Nov 2003 | B1 |
6665648 | Brodersen et al. | Dec 2003 | B2 |
6665655 | Warner et al. | Dec 2003 | B1 |
6684438 | Brodersen et al. | Feb 2004 | B2 |
6711565 | Subramaniam et al. | Mar 2004 | B1 |
6724399 | Katchour et al. | Apr 2004 | B1 |
6728702 | Subramaniam et al. | Apr 2004 | B1 |
6728960 | Loomans et al. | Apr 2004 | B1 |
6732095 | Warshavsky et al. | May 2004 | B1 |
6732100 | Brodersen et al. | May 2004 | B1 |
6732111 | Brodersen et al. | May 2004 | B2 |
6754681 | Brodersen et al. | Jun 2004 | B2 |
6763351 | Subramaniam et al. | Jul 2004 | B1 |
6763501 | Zhu | Jul 2004 | B1 |
6768904 | Kim | Jul 2004 | B2 |
6772229 | Achacoso et al. | Aug 2004 | B1 |
6782383 | Subramaniam et al. | Aug 2004 | B2 |
6804330 | Jones et al. | Oct 2004 | B1 |
6826565 | Ritchie et al. | Nov 2004 | B2 |
6826582 | Chatterjee et al. | Nov 2004 | B1 |
6826745 | Coker | Nov 2004 | B2 |
6829655 | Huang et al. | Dec 2004 | B1 |
6842748 | Warner et al. | Jan 2005 | B1 |
6850895 | Brodersen et al. | Feb 2005 | B2 |
6850949 | Warner et al. | Feb 2005 | B2 |
7062502 | Kesler | Jun 2006 | B1 |
7340411 | Cook | Mar 2008 | B2 |
7356482 | Frankland et al. | Apr 2008 | B2 |
7401094 | Kesler | Jul 2008 | B1 |
7620655 | Larsson | Nov 2009 | B2 |
7698160 | Beaven et al. | Apr 2010 | B2 |
7779475 | Jakobson et al. | Aug 2010 | B2 |
7851004 | Hirao et al. | Dec 2010 | B2 |
8010663 | Firminger et al. | Aug 2011 | B2 |
8014943 | Jakobson | Sep 2011 | B2 |
8015495 | Achacoso et al. | Sep 2011 | B2 |
8032297 | Jakobson | Oct 2011 | B2 |
8082301 | Ahlgren et al. | Dec 2011 | B2 |
8095413 | Beaven et al. | Jan 2012 | B1 |
8095594 | Beaven et al. | Jan 2012 | B2 |
8209308 | Jakobson et al. | Jun 2012 | B2 |
8275836 | Beaven et al. | Sep 2012 | B2 |
8484111 | Frankland et al. | Jul 2013 | B2 |
8490025 | Jakobson et al. | Jul 2013 | B2 |
8504945 | Jakobson et al. | Aug 2013 | B2 |
8510664 | Rueben et al. | Aug 2013 | B2 |
8566274 | Koister | Oct 2013 | B2 |
8566301 | Rueben et al. | Oct 2013 | B2 |
8646103 | Jakobson et al. | Feb 2014 | B2 |
8924419 | Koister et al. | Dec 2014 | B2 |
20010044791 | Richter et al. | Nov 2001 | A1 |
20020072951 | Lee et al. | Jun 2002 | A1 |
20020082892 | Raffel | Jun 2002 | A1 |
20020129352 | Brodersen et al. | Sep 2002 | A1 |
20020140731 | Subramanian et al. | Oct 2002 | A1 |
20020143997 | Huang et al. | Oct 2002 | A1 |
20020162090 | Parnell et al. | Oct 2002 | A1 |
20020165742 | Robbins | Nov 2002 | A1 |
20030004971 | Gong | Jan 2003 | A1 |
20030018705 | Chen et al. | Jan 2003 | A1 |
20030018830 | Chen et al. | Jan 2003 | A1 |
20030066031 | Laane et al. | Apr 2003 | A1 |
20030066032 | Ramachandran et al. | Apr 2003 | A1 |
20030069936 | Warner et al. | Apr 2003 | A1 |
20030070000 | Coker et al. | Apr 2003 | A1 |
20030070004 | Mukundan et al. | Apr 2003 | A1 |
20030070005 | Mukundan et al. | Apr 2003 | A1 |
20030074418 | Coker et al. | Apr 2003 | A1 |
20030120675 | Stauber et al. | Jun 2003 | A1 |
20030151633 | George et al. | Aug 2003 | A1 |
20030159136 | Huang et al. | Aug 2003 | A1 |
20030187921 | Diec et al. | Oct 2003 | A1 |
20030189600 | Gune et al. | Oct 2003 | A1 |
20030204427 | Gune et al. | Oct 2003 | A1 |
20030206192 | Chen et al. | Nov 2003 | A1 |
20040001092 | Rothwein et al. | Jan 2004 | A1 |
20040015981 | Coker et al. | Jan 2004 | A1 |
20040027388 | Berg et al. | Feb 2004 | A1 |
20040128001 | Levin et al. | Jul 2004 | A1 |
20040186860 | Lee et al. | Sep 2004 | A1 |
20040193510 | Catahan et al. | Sep 2004 | A1 |
20040199489 | Barnes-Leon et al. | Oct 2004 | A1 |
20040199536 | Barnes-Leon et al. | Oct 2004 | A1 |
20040249854 | Barnes-Leon et al. | Dec 2004 | A1 |
20040260534 | Pak et al. | Dec 2004 | A1 |
20040260659 | Chan et al. | Dec 2004 | A1 |
20040268299 | Lei et al. | Dec 2004 | A1 |
20050050555 | Exley et al. | Mar 2005 | A1 |
20050091098 | Brodersen et al. | Apr 2005 | A1 |
20070089951 | Koister et al. | Aug 2007 | A1 |
20090063415 | Chatfield et al. | Mar 2009 | A1 |
20090100342 | Rueben et al. | Apr 2009 | A1 |
20090177744 | Marlow et al. | Jul 2009 | A1 |
20110246465 | Koister et al. | Oct 2011 | A1 |
20120233137 | Jakobson et al. | Sep 2012 | A1 |
20130085745 | Koister et al. | Apr 2013 | A1 |
20130218948 | Jakobson | Aug 2013 | A1 |
20130218949 | Jakobson | Aug 2013 | A1 |
20130218966 | Jakobson | Aug 2013 | A1 |
20140359537 | Jakobson et al. | Dec 2014 | A1 |
20150007050 | Jakobson et al. | Jan 2015 | A1 |
20150095162 | Jakobson et al. | Apr 2015 | A1 |
20150172563 | Jakobson et al. | Jun 2015 | A1 |
Entry |
---|
Batista, Gustavo EAPA, Ronaldo C. Prati, and Maria Carolina Monard. “A study of the behavior of several methods for balancing machine learning training data.” ACM SIGKDD explorations newsletter 6, No. 1 (2004): 20-29. 2004. |
Burke, Robin. “Hybrid recommender systems: Survey and experiments.” User modeling and user-adapted interaction12.4 (2002): 331-370. (Year: 2002). |
U.S. Appl. No. 13/986,251, filed Apr. 16, 2013. |
Number | Date | Country | |
---|---|---|---|
20170061325 A1 | Mar 2017 | US |