Reputation system for web services

• US 7,467,206 B2
• Filed: 12/23/2002
• Issued: 12/16/2008
• Est. Priority Date: 12/23/2002
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Moore, George, Meredith, Lucius Gregory
• Primary Examiner(s): Follansbee; John
• Assistant Examiner(s): Tran; Nghi V
• Application Number:
  US10/328,714
• Publication Number:
  US 20040122926A1
• Time in Patent Office: 2,185 Days
• Field of Search: 709/226, 709/228, 709/230, 709/225
• US Class Current: 709/225
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9538 Presentation of query results

Abstract

A system and method for automating the web service selection based on reputation information, to help negotiate a contractual web service binding between a client and a server. Reputation information may be schematized into behavioral attributes such as web service responsiveness, web service latency, web service uptime, cost data, business solvency and other trustworthiness and business-related data. Some of the reputation data may be empirically determined, and provided by an independent or other trusted auditor. In one implementation, a client queries a search engine, which returns a ranked list of web services, with the ranking based on reputation scores computed for each web service as collected by an auditor. Clients may provide computational data to weigh the attributes separately. A corporate internet can maintain reputation data for web services to act as an auditor, and a web service server can also execute trusted code to act as an auditor.

Claims

1. In a computing environment in which web services are used to provide computing services to clients via protocols and cross-platform standards, a system for finding and ranking web services in a manner that matches web services with a consumer'"'"'s computing service needs, and which is not significantly influenced by popularity data or other manipulable data of a web service, the system comprising:

a listing mechanism that identifies a plurality of web services, each of the web services operable to provide interoperative functionality to the system;

an auditor that collects reputation data that corresponds to schematized behavioral attributes for the plurality of web services, the behavioral attributes including technical attributes of the web service unrelated to web service popularity, including at least web service responsiveness, wherein web service responsiveness is a measure of how often a web service reads from a specific port; and

a selection mechanism for matching one or more web services to a consumer'"'"'s needs, the selection mechanism being adapted to narrow the plurality of web services identified by the listing mechanism, based on the reputation data, including at least the technical attributes, provided by the auditor, into a subset that identifies at least one web service, wherein the technical attributes used to narrow that plurality of web services include empirical data on at least web service responsiveness, and excludes attributes, including popularity data, that are susceptible to manipulation by provides of the plurality of web services, and instead includes technical attributes that are resistant to manipulation;

wherein the selection mechanism includes a server component that returns a list of at least two web services as the subset to a requesting client;

wherein the selection mechanism includes a client component that further narrows the list into a single selected web service.

2. The system of claim 1 wherein the listing mechanism comprises a UDDI web service search engine and wherein the plurality of web services comprises a plurality of UDDI defined web services.

3. The system of claim 1 wherein the subset identifies a single selected web service.

4. The system of claim 1 wherein the selection mechanism includes a ranking mechanism that ranks each web service in the subset into an order based on the reputation data.

5. The system of claim 1 wherein the selection mechanism determines a score for each web service in the subset based on the reputation data.

6. The system of claim 1 wherein the auditor collects reputation data from a plurality of web service providers.

7. The system of claim 1 wherein the auditor executes within an intranet and measures actual performance of web services.

8. The system of claim 1 wherein the auditor executes on a server that provides a web service.

9. The system of claim 1 wherein the auditor comprises an independent entity with respect to the listing mechanism and each provider of each web service in the subset, and wherein the auditor is accessible via a network connection.

10. The system of claim 1 wherein the auditor collects reputation data from a plurality of reviewers.

11. The system of claim 10 wherein the reviewers comprise clients that request the web services.

12. The system of claim 1 wherein the technical attributes used to narrow the plurality of web services further comprise web service latency information.

13. The system of claim 1 wherein the technical attributes used to narrow the plurality of web services further comprise web service uptime information.

14. The system of claim 1 wherein the reputation data used to narrow the plurality of web services comprises business-oriented attribute data.

15. The system of claim 1 wherein the reputation data used to narrow the plurality of web services comprises web service cost information.

16. The system of claim 1 wherein the reputation data used to narrow the plurality of web services comprises information representing a solvency level of a provider of a web service.

17. The system of claim 1 wherein the reputation data used to narrow the plurality of web services comprises information representing an external business auditor of a provider of a web service.

18. The system of claim 1 wherein the reputation data used to narrow the plurality of web services comprises information representing a privacy policy of a provider of a web service.

19. The system of claim 1 wherein the reputation data used to narrow the plurality of web services comprises information representing certificate data of a provider of a web service.

20. The system of claim 1 wherein the reputation data used to narrow the plurality of web services comprises technically-oriented attribute data and business-oriented attribute data.

21. The system of claim 1 wherein the reputation data used to narrow the plurality of web services is categorized into a set of scores, and wherein the selection mechanism determines a ranking score for each web service in the subset based on the set of scores and at least one weight value corresponding to at least one of the scores.

22. The system of claim 21 wherein a client provides each weight value in a query to a server.

23. The system of claim 1 wherein the reputation data used to narrow the plurality of web services is categorized into a set of scores, and wherein a requesting client indicates reputation requirements for at least one of the scores in a query to a server.

24. In a computing environment for providing web services which provide computing services to clients via protocols and cross-platform standards, a method for finding and ranking web services in a manner that matches web services with a consumer'"'"'s computing service needs, and which is not significantly influenced by popularity data or other manipulable data of a web service, the method comprising:

receiving a query for web service data, the query including request data comprising at least one basic operating requirement and at least one reputation requirement that corresponds to at least one schematized behavioral attribute for a web service, the at least one schematized behavioral attribute of the reputation data including at least one technical attribute unrelated to web service popularity and which are resistant to manipulation and which relates to empirical data on a web service'"'"'s responsiveness, wherein web service responsiveness is a measure of how often a web service reads from a specific port;

using the request data, including the technical attribute including the web service'"'"'s responsiveness data, and excluding attributes, including popularity data, that are susceptible to manipulation by a provider of a web services, to locate a set of web services that meet each basic operating requirement and a subset of at least one web service that meets each reputation requirement, wherein each of the web services are operable to provide interoperative functionality to the systems; and

wherein the query is received at a search engine from a client, and wherein returning the subset in response to the query comprises returning a list to the client;

wherein the list includes at least two web services, and further comprising, at the client, receiving the list and selecting a web service from the list;

returning the subset in response to the query.

25. The method of claim 24 wherein the query is received at a search engine, and further comprising, at the search engine, crawling cached contract data to locate the set of web services that meet each basic operating requirement.

26. The method of claim 25 further comprising, at the search engine, crawling cached reputation data to locate the subset of web services that meet each reputation requirement.

27. The method of claim 24 further comprising, communicating with a provider of a web service identified in the subset to verify that the provider meets each basic operating requirement and each reputation requirement.

28. The method of claim 24 further comprising, communicating with an auditor to verify that a provider of a web service identified in the subset meets each basic operating requirement and each reputation requirement.

29. The method of claim 24 wherein the subset identifies at least two web services, and further comprising, ranking each web service in the subset into an order based on collected reputation data.

30. The method of claim 24 further comprising determining a score for each web service in the subset based on collected reputation data.

31. The method of claim 24 further comprising, collecting reputation data from a plurality of reviewers.

32. The method of claim 24 further comprising, collecting reputation data from a web service provider.

33. The method of claim 32 wherein collecting reputation data from the web service provider comprises measuring actual performance of a web service corresponding to the provider.

34. The method of claim 33 wherein measuring the actual performance comprises measuring web service responsiveness.

35. The method of claim 34 wherein measuring web service responsiveness comprises determining how often a web service reads from a specific port.

36. The method of claim 33 wherein measuring the actual performance comprises measuring web service latency.

37. The method of claim 36 wherein the at least one technical attribute further includes web service latency, and wherein measuring web service latency comprises determining a guaranteed not-to-exceed latency for the results of a specific operation.

38. The method of claim 33 wherein the at least one technical attribute further includes web service uptime measuring the actual performance comprises measuring web service uptime.

39. The method of claim 38 wherein measuring web service uptime comprises observing how often a site or device is available.

40. The method of claim 38 wherein measuring web service uptime comprises observing what time of day a web service is unavailable.

41. The method of claim 24 wherein the request data comprises categorized weight data corresponding to at least some categories of scores corresponding to reputation data for each web service, and wherein using the request data comprises applying the weight data to the scores to determine a resultant score for each web service.

42. A computer-readable storage medium having computer-executable instructions for performing the method of claim 24.

43. In a computing environment in which web services are used to provide computing services to clients via protocols and cross-platform standards, a method for finding and ranking web services in a manner that matches web services with a consumer'"'"'s computing service needs, and which is not significantly influenced by popularity data or other manipulable data of a web service, the method comprising:

maintaining information that identifies a plurality of web services, each web service operable to provide interoperative functionality to a computer system;

obtaining reputation data that corresponds to schematized behavioral attributes for the plurality of web services, the at least one schematized behavioral attribute of the reputation data including at least one technical attribute unrelated to web service popularity, which is resistant to manipulation, and which relates to empirical data on at least a web service'"'"'s responsiveness, wherein web service responsiveness is a measure of how often a web service reads from a specific port; and

selecting a subset from the plurality of web services based on the reputation data, and excluding attributes, including popularity data, that are susceptible to manipulation by providers of the plurality of web services, and instead including the empirical data on responsiveness, the subset comprising at least one web service;

wherein the selecting includes a server component that returns a list of at least two web services as the subset to a requesting client;

wherein the selecting includes a client component that further narrows the list into a single selected web service.

44. The method of claim 43 further comprising, receiving a request for the subset from a client, and returning the subset in response to the request.

45. The method of claim 43 further comprising, ranking each web service in the subset into an order based on the reputation data.

46. The method of claim 43 wherein selecting a subset comprises determining a reputation score for each web service in the subset.

47. The method of claim 43 wherein obtaining reputation data comprises communicating with an auditor.

48. The method of claim 43 wherein obtaining reputation data comprises communicating with each provider of each web service.

49. The method of claim 43 further comprising collecting the reputation data.

50. The method of claim 43 wherein collecting the reputation data comprises measuring actual performance of a web service.

51. The method of claim 43 further comprising, verifying the reputation data.

52. A computer-readable storage medium having computer-executable instructions for performing the method of claim 43.

53. In a computing environment in which web services are used to provide computing services to clients via protocols and cross-platform standards, a system for finding and ranking web services in a manner that matches web services with a consumer s computing service needs, and which is not significantly influenced by popularity data or other manipulable data of a web service, the system comprising,

a client that requests a web service;

a server that provides a web service corresponding to the requested web service, the web service operable to provide interoperative functionality to the client;

an auditor that collects reputation data that corresponds to at least one schematized behavioral attribute for the requested web service, the behavioral attributes including technical attributes of the web service, and the technical attributes being resistant to manipulation and including empirical data on at least web service responsiveness, wherein web service responsiveness is a measure of how often a web service reads from a specific ports; and

a UDDI search engine that receives the web service request from the client, identifies the server as corresponding to the requested web service, uses the reputation data, including the technical attributes relating to web service responsiveness, and excluding attributes, including popularity data, which are susceptible to manipulation by a provider of a web service, to select the web service from among other servers that provide web services that correspond to the requested web service, and returns an identifier of the server to the client in response to the request;

wherein the search engine returns the identifier in a list of identifiers to the client, each identifier corresponding to a server that provides a web service that corresponds to the requested web service;

wherein the list of identifiers corresponds to a narrowed subset of the other servers that provide web services that correspond to the requested web service.

54. The system of claim 53 wherein the list of identifiers is ranked according to the reputation data.

55. The system of claim 53 wherein the client reports reputation data to the auditor.

56. The system of claim 53 wherein the server provides reputation data to the auditor.

57. The system of claim 53 wherein the search engine caches the reputation data.

58. The system of claim 53 wherein the search engine communicates with the auditor to receive the reputation data.

59. The system of claim 53 wherein the search engine communicates with the auditor to verify the reputation.