WO2007120393A1 - Configuration de catégorie de client - Google Patents

Configuration de catégorie de client Download PDF

Info

Publication number
WO2007120393A1
WO2007120393A1 PCT/US2007/004719 US2007004719W WO2007120393A1 WO 2007120393 A1 WO2007120393 A1 WO 2007120393A1 US 2007004719 W US2007004719 W US 2007004719W WO 2007120393 A1 WO2007120393 A1 WO 2007120393A1
Authority
WO
WIPO (PCT)
Prior art keywords
clients
categories
configuration
client
computer
Prior art date
Application number
PCT/US2007/004719
Other languages
English (en)
Inventor
Gowri S. Paranthaman
Karthik Lakshminarayanan
Trevor Foucher
Original Assignee
Microsoft Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Microsoft Corporation filed Critical Microsoft Corporation
Priority to EP07751478A priority Critical patent/EP2005337A1/fr
Priority to JP2009502793A priority patent/JP2009531772A/ja
Publication of WO2007120393A1 publication Critical patent/WO2007120393A1/fr

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising

Definitions

  • PCs desktop personal computers
  • PDAs personal digital assistants
  • game consoles and so on.
  • communication applications e.g.. browsers, instant messaging and email
  • productivity applications e.g., word processing, spreadsheets, presentations, note taking, graphical design
  • games and so on.
  • the maintenance service may make recommendations to the users regarding configurations of the computing devices. Because of the variations in functionality available to the users, however, a wide variety of configurations may be employed by the users to gain access to and select from this functionality. For example, the users may choose from the different varieties of computing devices and also choose from the different varieties of software that are available as previously described. Therefore, configurations of software and hardware employed by the computing devices may vary greatly from user to user.
  • Traditional maintenance service techniques did not make distinctions between the computing devices, but rather made general recommendations to be employed by each device. Variations in the configurations, however, may make recommendations inapplicable to one or more of the clients. Further, the recommendations may even result in a decrease in functionality of the "inapplicable" computing devices and resultant frustration on the part of the users.
  • Client category configuration is described.
  • a computer-implemented method is employed to find categories of clients based on configuration data obtained from the. clients.
  • a configuration recommendation is then created for a particular one of the categories based on configuration of one or more ' of the clients included in the particular category.
  • FIG. 1 is an illustration of an environment in an exemplary implementation that is operable to employ client category configuration techniques.
  • FIG. 2 is an illustration of a system in an exemplary implementation showing a client maintenance service and a plurality of clients of FIG. 1 in greater detail.
  • FIG. 3 is a flow diagram depicting a procedure in an exemplary implementation in which configuration data is used to find categories of clients and create a configuration recommendation for a particular one of the categories.
  • FIG. 4 is a flow diagram depicting a procedure in an exemplary implementation in which configuration data is processed that contains clients and modules that were not previously detected.
  • FIG. 5 is a flow diagram depicting a procedure in an exemplary implementation in which an automatic determination is made in relation to a module not previously encountered by a client and recommendations are provided based on whether the module is included in the client's category.
  • the maintenance service may obtain data from the computing devices regarding configuration of the computing devices, such as decisions made by the users pertaining to applications being executed on the computing devices, files that are selected for backup, and so on. This data may be analyzed for purposes of providing better service back to the users of the service, such as by providing recommendations regarding configuration.
  • FIG. 1 is an illustration of an environment 100 in an exemplary implementation that is operable to employ client category configuration techniques.
  • the illustrated environment 100 includes a plurality of clients 102(1), ..., 102 ⁇ N) that are communicatively coupled to a client maintenance service 104 over a network 106.
  • the clients 102(l)-102(N) may be configured in a variety of ways for accessing the network 106.
  • one or more of the clients 102(1)- 102(N) may be configured as a computing device, such as a desktop computer, a mobile station, an entertainment appliance, a set-top box communicatively coupled to a display device, a wireless phone, a game console, and so forth.
  • the clients 102(1)- 102(N) may range from full resource devices with substantial memory and processor resources (e.g., personal computers, game consoles) to low-resource devices with limited memory and/or processing resources (e.g., traditional set-top boxes, hand-held game consoles).
  • the clients 102(1)- 102(N) may also relate to a person and/or entity that operate the clients. In other words, one or more of the clients 102(I)-102(N) may describe logical clients that include users, software, and/or devices.
  • the network 106 is illustrated as the Internet, the network may assume a wide variety of configurations.
  • the network 106 may include a wide area network (WAN), a local area network (LAN), a wireless network, a public telephone network, an intranet, and so on.
  • WAN wide area network
  • LAN local area network
  • wireless network a public telephone network
  • intranet an intranet
  • the network 106 may be configured to include multiple networks.
  • the clients 102(l)-102(N) are each illustrated as having a respective monitoring module 108(l)-108(N)-
  • the monitoring modules 108(l)-108(N) are representative of logic to monitor configuration of the respective clients 102(1)- 102(N).
  • configuration data 110(d) and data 112(e) Data generated from this monitoring is illustrated as configuration data 110(d) and data 112(e) (where “d” and “e” can be any integer from one to “D” and “E”, respectively) in respective storage 114(I)-114(N).
  • This configuration data may then be uploaded at period intervals over the network 106 to the client maintenance service 104 and stored in storage 116 as configuration data 110(c).
  • the client maintenance service 104 includes a configuration manager module 118 that is representative of functionality to process the configuration data 110(c).
  • the configuration manager module 118 when executed, may examine the configuration data 110(c) to arrive at a plurality of client categories 120(k) (where "k” can be any integer from two to "K") that are illustrated as being stored in storage 122.
  • the client categories 120(k) reference commonalities of clients within the group. For instance, one such client category 120(k) may be "gamers" which are defined by a particular group of the clients 102(1)- 102(N) that permit Internet access to a variety of games.
  • the configuration manager module 118 may then make recommendations to this group as a whole based on actions taken by others in the group.
  • a new game module may be provided to the clients 102(1)- 102(N) which provides for an "online" experience through access to the network 106.
  • a first few gamers when setting up the new game module, may permit the game module to access the network 106 through use of a configuration setting.
  • Information regarding this decision may be populated to other clients in that same client category 120(k) (e.g., "gamers") such that the other clients are not forced to manually set the configuration as was done by those first few gamers.
  • knowledge absorbed from known client categories may be leveraged to take similar actions on behalf of other clients who have been categorized into the categories.
  • the client maintenance service 104 may also employ the configuration manager module 118 to categorize new clients. For example, a "new" client may join the client maintenance service 104.
  • the configuration manager module 118 may examine the client and based on the examination, place the client into one or more of the client categories 120(k).
  • the client for instance, may include a variety of games and be placed in a "gamers” category and a variety of accounting software and therefore also be placed in a "finance" category. Recommendations to the client may then be provided based on membership of the client in the respective categories, further discussion of which may be found in relation to FIG. 4.
  • any of the functions described herein can be implemented using software, firmware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations.
  • the terms "module,” “functionality,” and “logic” as used herein generally represent software, firmware, or a combination of software and firmware.
  • the module, functionality, or logic represents program code that performs specified tasks when executed on a processor (e.g., CPU or CPUs).
  • the program code can be stored in one or more computer readable memory devices, further description of which may be found in relation to FIG. 2.
  • the features of the client category configuration techniques described below are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors. [0022] FIG.
  • FIG. 2 is an illustration of a system 200 in an exemplary implementation showing the client maintenance service 104 and the plurality of clients of FIG. 1 in greater detail.
  • the client maintenance service 104 is illustrated as being implemented by a server 202, which although a single server 202 is illustrated, server 202 may be representative of multiple servers, e.g., a server cluster.
  • the client 102(n), which in FIG. 2 is illustrated as a client device, may be representative of any one of the clients 102(1)- 102 (N). Accordingly, the server 202 and the client 102(n) are illustrated as having respective processor 204, 206(n) and memory 208, 210(n).
  • processors are not limited by the materials from which they are formed or the processing mechanisms employed therein.
  • processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)).
  • processor-executable instructions may be electronically- executable instructions.
  • the mechanisms of or for processors, and thus of or for a computing device may include, but are not limited to, .quantum computing, optical computing, mechanical computing (e.g., using nanotechnology), and so forth.
  • RAM random access memory
  • the client category 120(k) may be maintained in RAM while the configuration data 110(c) may be maintained in a hard disk drive.
  • the client 102(n) is illustrated as executing the monitoring module 108(n) on the processor 206(n) 5 which is also storable in memory 210(n).
  • the monitoring module 108(n), as previously described, is executable to generate configuration data 110(n) that describes the configuration of the client 102(n).
  • the configuration data 110(n) may described modules 212 (e.g., applications, third-party plug-in modules, and so on), files 214 (e.g., types of files, such as a particular file name extension), settings 216 (e.g., settings of the modules 212, hardware settings and network settings) and "other" 218 configuration data 110(n) that describes the configuration of the client 102(n), such as responses to actions performed during execution of a module, particular behavior in relation to files 214 (e.g., backup storage), and so on.
  • modules 212 e.g., applications, third-party plug-in modules, and so on
  • files 214 e.g., types of files, such as a particular file name extension
  • settings 216 e.g., settings of the modules 212, hardware settings and network settings
  • the configuration data 110(n) of the clients 102(n) may be uploaded to the client maintenance service 104 over the network 106 (such as at periodic intervals, when a threshold amount of data has been generated, and so on) and stored as configuration data 110(c) in memory 208.
  • the configuration data 110(c) may then be processed by the configuration manager module 118 in a variety of ways.
  • the configuration data 110(c) may be used to generate the plurality of client categories 120(k).
  • the client categories 120(k) may be generated automatically based on similarities detected in configurations of the clients 102(n) through analysis of the configuration data 110(c) by the configuration manager module 118.
  • the similarities of the client categories 120(k) may reflect a wide variety of groupings, such as a hobby 220, occupation 222, a common interest 224 and other 226 commonalities. These commonalities, for instance, may be reflected by the modules 212, files 214, settings 216 included by each of the clients 102(n).
  • the client categories 120(k) may then be utilized to find configuration recommendations that are particular to that category. Therefore, these recommendations are more likely to be pertinent to each of the clients 102(n) in the category. Additionally, as new clients are encountered, the clients may be categorized into one or more of the client categories 120(k) based on modules 212, files 214 and settings 216 of the new client. Further, new modules (e.g., a new game, productivity application, third-party plugin .modules, and so on) may also be categorized based on which clients 102(n) have obtained and/or used the module. Yet further, the client categorization process may be repeated at periodic intervals to realign the client categories 120(k). Further discussion of client category configuration techniques may be found in relation to the following figures. [0028] Exemplary Procedures
  • FIG. 3 depicts a procedure 300 in an exemplary implementation in which configuration data is used to find categories _of clients and create a configuration recommendation for a particular one of the categories. Configuration of a client is monitored (block 302).
  • the client 102(n) may execute the monitoring module 108(n) to monitor usage of the client 102(n), such as which applications are included on the client, setting relating to the applications, file types included on the client 102(n), which files are backed up on the client 102(n) (e.g., a finance file configured for storage on two different memory devices), and so on.
  • the monitoring may be performed to include a description of performance realized as a result of the change by the clients, such as changes to reliability, performance, and so on after a configuration has changed.
  • the monitoring module 108(n) may be configured to publish the configuration data 110(n) at periodic intervals, when a configuration has been changed, when a threshold amount of configuration data 110(n) is created, and so on.
  • a category may be formed specifying clients that have a particular combination of modules (e.g., games, finance applications, graphical design applications, third-party plugin modules, and so on), settings for the modules, files (e.g., purchased and downloaded music files), and so on.
  • modules e.g., games, finance applications, graphical design applications, third-party plugin modules, and so on
  • settings for the modules e.g., settings for the modules
  • files e.g., purchased and downloaded music files
  • An indication is formed to be communicated to one or more of the clients that identifies one or more of the categories, to which, the client belongs (block 308).
  • the indication may describe that the client is a member of the "gamers" category and a "finance" category. This indication may or may not be exposed to a user.
  • the indication may be communicated for use by the monitoring module 108(n) without notifying a user as to the categories.
  • the indication is output for viewing by a user such that the user may accept, decline or change one or more of the categories. A variety of other examples are also contemplated.
  • a configuration recommendation is created for a particular one of the categories based on configuration of one or more of the clients that are included in the particular category (block 310). For example, a subset of clients in the finance category may enable a financial application to access financial accounts over a network every half hour. This access, however, may cause a significant decrease in the performance of the client. On the other hand, another subset of the clients in the finance category may permit access by the financial application to financial accounts every hour and experience a minor reduction in functionality. Therefore, a recommendation may be formed which indicates that the network access setting for the financial application should be set to access every hour.
  • the configuration manager module 118 may determine that clients in the finance category typically backup files with a particular extension. Therefore, a recommendation may be formed for the finance category that suggests backup of files having that extension. A variety of other examples are also contemplated.
  • the recommendation is communicated to at least one of the clients in the particular category (block 312). For instance, recommendations for each of the groups may be packaged and communicated to each one of the plurality of clients
  • the clients may then determine which of the recommendations are pertinent to the client.
  • this packaging may serve to protect the privacy of the client regarding category membership by having the client 102(n) determine which recommendations are pertinent.
  • this packaging may serve to protect the privacy of the client regarding category membership by having the client 102(n) determine which recommendations are pertinent.
  • a variety of other instances are also contemplated.
  • FIG. 4 depicts a procedure 400 in an exemplary implementation in which configuration data is processed that contains clients and modules that were not previously detected.
  • Configuration data is obtained (block 402), such as configuration data published from the plurality of clients 102(l)l-2(N), configuration data obtained from a data extraction service, and so on.
  • Clients (block 404) and modules (block 406) are extracted from the configuration data, such as through the use of globally unique identifiers (GUIDs), hashes of represented data (e.g., a hash value generated from data of a particular file), and so on. A variety of other extraction techniques are also contemplated.
  • GUIDs globally unique identifiers
  • hashes of represented data e.g., a hash value generated from data of a particular file
  • a variety of other extraction techniques are also contemplated.
  • a configuration of the client is determined (block 408). For example, the configuration manager module 118 may determine which modules are included on the client, settings for the modules, file types, which files were backed up by the client, and so on.
  • the client is categorized based on the comparison (block 412), such as by comparing configurations specified by the categories with the configuration of the client.
  • the client is permitted membership to multiple categories.
  • conflicting recommendations may be resolved by prioritizing the categories, such as by determining that the client is more suited to membership in one particular category over another category and therefore recommendations for the particular category "win”.
  • membership is restricted to one category and therefore conflicting recommendations are not encountered.
  • the category is communicated to the client (block 414). Therefore, in this example the processing is performed by the client maintenance service 104 through execution of the configuration manager module 118. In another example, the client 102(n) may perform all or part of the processing, such as by determining by a client 102(n) which of a plurality of categories defined by the client maintenance service 104 correspond to the client 102(n). A variety of other examples are also contemplated.
  • Similar techniques may be employed to find one or more categories for a previously undetected module. For example, when a previously undetected module is detected, a determination is made as to which clients include the module (block 416). The clients that include the module are then compared with the categories (block 418). One or more of the categories may then be updated to include the module (block 420). For example, it may be determined that a significant percentage of the clients that include the module are also members of a "gamers" category. Therefore, a definition of the "gamers" category may be updated to include the module. The updated one or more categories may then be communicated to the clients in the respective categories (block 422). Therefore, in this instance, the client is able to determine category membership based on the definitions of the categories. A wide variety of other examples are also contemplated as previously described.
  • FIG. 5 depicts a procedure 500 in an exemplary implementation in which automatic determination is made in relation to a module not previously encountered by a client and recommendations are provided based on whether the module is included in the client's category.
  • a client encounters a module (block 502).
  • the client 102(n) may download a module via the network 106 from a. content provider.
  • the monitoring module 108(n) may include a listing of previously identified modules obtained from the client maintenance service 104 and consult this list whenever a new module is encountered by the client 102(n).
  • the client 102(n) prompts for input regarding configuration of a particular feature (block 506).
  • the prompt for instance, may be whether to permit the module to access the network 106.
  • the client 102(n) may then receive the input in response to the prompt on whether to permit access.
  • This input may also be communicated to the client maintenance service (block 508).
  • the client maintenance service 104 may collect inputs regarding configuration of the module and make ⁇ recommendations to other clients based on the collected inputs.
  • a determination is made as to whether the module is included in the client's category (decision block 510).
  • an appropriate recommendation is made (block 512).
  • the monitoring module 108(n) may automatically give a negative recommendation (e.g., a warning) to caution a user when the module lies "outside" the client's category. !0047)
  • a recommendation is made based on the client's category (block 514). Continuing with the previous example, a "positive" recommendation may be made to permit network access based on inclusion of the module within the client's category. A variety of other examples are also contemplated.
  • Changes in previously set configurations may also be monitored and given special consideration. For example, by monitoring client interaction (block 516) a change in a configuration may be detected. A determination is then made as to whether the client has changed this configuration again (decision block 518). If not ("no" from decision block 518), the service (e.g., the client maintenance service) is notified of the new configuration (block 520). If so ("yes" from decision block 518), however, the service is notified that configuration that was previously set by the client has been changed again (block 522). In this way, the monitoring module 108(n) "flags" the configuration data 110(n) such that the client maintenance service 104 may give special consideration to the configuration data.
  • the service e.g., the client maintenance service
  • the configuration maintenance service 104 itself, may perform the processing to determine when the configuration was changed. Therefore, because a change to a previous setting may indicate a previous undesirable result, that change may be given special consideration when making future recommendations. A variety of other examples are also contemplated. [0049J Conclusions

Landscapes

  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Information Transfer Between Computers (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne une configuration de catégorie de client dans laquelle un procédé mis en œuvre sur ordinateur peut être employé pour trouver des catégories de clients basées sur des données de configuration obtenues auprès des clients. Une recommandation de configuration est alors créée pour une catégorie particulière sur la base de la configuration d'un ou plusieurs des client(s) inclus dans la catégorie particulière.
PCT/US2007/004719 2006-03-29 2007-02-23 Configuration de catégorie de client WO2007120393A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07751478A EP2005337A1 (fr) 2006-03-29 2007-02-23 Configuration de catégorie de client
JP2009502793A JP2009531772A (ja) 2006-03-29 2007-02-23 クライアントカテゴリ構成

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/277,884 2006-03-29
US11/277,884 US20070239672A1 (en) 2006-03-29 2006-03-29 Client Category Configuration

Publications (1)

Publication Number Publication Date
WO2007120393A1 true WO2007120393A1 (fr) 2007-10-25

Family

ID=38576705

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/004719 WO2007120393A1 (fr) 2006-03-29 2007-02-23 Configuration de catégorie de client

Country Status (5)

Country Link
US (1) US20070239672A1 (fr)
EP (1) EP2005337A1 (fr)
JP (1) JP2009531772A (fr)
CN (1) CN101410835A (fr)
WO (1) WO2007120393A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20080003884A (ko) * 2005-04-15 2008-01-08 에스프리다 코포레이션 지능 장치의 네트워크 관리 장치 및 방법

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6029196A (en) * 1997-06-18 2000-02-22 Netscape Communications Corporation Automatic client configuration system
US6539375B2 (en) * 1998-08-04 2003-03-25 Microsoft Corporation Method and system for generating and using a computer user's personal interest profile
US20030066067A1 (en) * 2001-09-28 2003-04-03 Koninklijke Philips Electronics N.V. Individual recommender profile modification using profiles of others
WO2004030360A1 (fr) * 2002-09-26 2004-04-08 Koninklijke Philips Electronics N.V. Dispositif de recommandation publicitaire
WO2004107758A1 (fr) * 2003-06-02 2004-12-09 Koninklijke Philips Electronics N.V. Recommandation par creation dynamique de categories

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5941947A (en) * 1995-08-18 1999-08-24 Microsoft Corporation System and method for controlling access to data entities in a computer network
US6493702B1 (en) * 1999-05-05 2002-12-10 Xerox Corporation System and method for searching and recommending documents in a collection using share bookmarks
US20040236843A1 (en) * 2001-11-15 2004-11-25 Robert Wing Online diagnosing of computer hardware and software
US7840652B2 (en) * 2001-03-21 2010-11-23 Ascentive Llc System and method for determining network configuration settings that provide optimal network performance
US6836750B2 (en) * 2001-04-23 2004-12-28 Hewlett-Packard Development Company, L.P. Systems and methods for providing an automated diagnostic audit for cluster computer systems
US7340770B2 (en) * 2002-05-15 2008-03-04 Check Point Software Technologies, Inc. System and methodology for providing community-based security policies
US7293272B1 (en) * 2004-02-26 2007-11-06 Veritas Operating Corporation Device driver processing for automated system restores

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6029196A (en) * 1997-06-18 2000-02-22 Netscape Communications Corporation Automatic client configuration system
US6539375B2 (en) * 1998-08-04 2003-03-25 Microsoft Corporation Method and system for generating and using a computer user's personal interest profile
US20030066067A1 (en) * 2001-09-28 2003-04-03 Koninklijke Philips Electronics N.V. Individual recommender profile modification using profiles of others
WO2004030360A1 (fr) * 2002-09-26 2004-04-08 Koninklijke Philips Electronics N.V. Dispositif de recommandation publicitaire
WO2004107758A1 (fr) * 2003-06-02 2004-12-09 Koninklijke Philips Electronics N.V. Recommandation par creation dynamique de categories

Also Published As

Publication number Publication date
JP2009531772A (ja) 2009-09-03
CN101410835A (zh) 2009-04-15
US20070239672A1 (en) 2007-10-11
EP2005337A1 (fr) 2008-12-24

Similar Documents

Publication Publication Date Title
US10162891B2 (en) Determining demographics based on user interaction
US11847480B2 (en) System for detecting impairment issues of distributed hosts
US20160012479A1 (en) System and method for preference determination
US20230014418A1 (en) Recommending contents using a base profile
US10262265B2 (en) Systems and methods for generating and communicating application recommendations at uninstall time
US8868439B2 (en) Content activity feedback into a reputation system
US20160210646A1 (en) System, method, and computer program product for model-based data analysis
US10657559B2 (en) Generating and utilizing a conversational index for marketing campaigns
CN111539756B (zh) 基于搜索要求识别用户并将用户选为目标的系统和方法
US20130179418A1 (en) Search ranking features
US10248527B1 (en) Automated device-specific dynamic operation modifications
WO2013162593A1 (fr) Mesures de conservation d'application
Saleem et al. Personalized decision-strategy based web service selection using a learning-to-rank algorithm
US20150242887A1 (en) Method and system for generating a targeted churn reduction campaign
CN106156123B (zh) 活跃值计算方法及装置
US7487181B2 (en) Targeted rules and action based client support
US20180129664A1 (en) System and method to recommend a bundle of items based on item/user tagging and co-install graph
US11294917B2 (en) Data attribution using frequent pattern analysis
US11061937B2 (en) Method and system for classifying user identifiers into similar segments
US20070239672A1 (en) Client Category Configuration
US11605042B1 (en) Artificial intelligence system for content presentation impact estimation
CN114827157A (zh) 集群任务处理方法、装置、系统、电子设备及可读介质
Khalid On the link between mobile app quality and user reviews
US20150294332A1 (en) Sales process review platform
JP2020042607A (ja) 情報処理装置、サーバ、情報処理方法及び情報処理プログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07751478

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 4561/CHENP/2008

Country of ref document: IN

WWE Wipo information: entry into national phase

Ref document number: 200780010939.4

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 2009502793

Country of ref document: JP

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2007751478

Country of ref document: EP