Apparatus and methods for correlating messages sent between services

• US 7,249,195 B2
• Filed: 12/03/2003
• Issued: 07/24/2007
• Est. Priority Date: 03/30/2001
• Status: Expired due to Term

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Octavian Udrea
• Inventors: Douglas, Jason, Panec, Peter A.
• Primary Examiner(s): Jaroenchonwanit; Bunjob
• Assistant Examiner(s): Refai; Ramsey
• Application Number:
  US10/728,356
• Publication Number:
  US 20040186891A1
• Time in Patent Office: 1,329 Days
• Field of Search: 345/765, 371/19, 709/249, 709204-206, 709223-225, 709/227, 709/238, 705/1, 707/10
• US Class Current: 709/238
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 45/44 Distributed routing
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04M 2203/5063 Centrally initiated conference, i.e. Conference server dials participants computer conference organisation arrangements H04L12/1818
• CPC Class Codes: H04Q 11/0407 using a stored programme control

Abstract

Disclosed are methods and apparatus for effectively correlating messages sent between services. In general, a message interchange network is configured to manage the use of services by remote entities or services within a computer network. In general terms, correlation information is stored for each message. The correlation information includes information for correlating each message with a specific call between two services and a specific session between two or more services.

Claims

1. A method for correlating services within a computer network, the method comprising:

providing a message interchange network for exchanging application-level messages between services that are located outside the message interchange network;

registering, at the message interchange network, each of the plurality of services so that each service is specified as being accessible by one or more of the plurality of services according to one or more properties and permissions associated with each of the plurality of services;

receiving, at the message interchange network, a plurality of application-level messages that each specify one or more of the plurality of services that are to receive the each application-level message and forwarding each received application-level message towards its specified service according to the one or more properties and permissions associated with the specified service;

retaining correlation information regarding each application-level message received into message interchange network, wherein the application-level messages are being sent between pairs of the services, wherein the retained correlation information for each application-level message pertains to each application-level message and any other application-level messages related to the each application-level message, the retained correlation information including one or more of;

a Hop Identifier (ID) uniquely identifying a hop between a sender and receiver of the each application-level message, call information regarding a call to which the each application-level message and any other related application-level message belongs, or session information regarding a session to which the each application-level message and any other related application-level message belongs, wherein the correlation information is retained in a searchable format that is accessible by the message interchange network;

receiving, at the message interchange network, a query from a first service to search the retained correlation information for a specific one or more portions of the retained correlation information; and

sending, to the first service, a response to the query that includes the specific one or more portions of the retained correlation information.

2. The method as recited in claim 1, wherein the retained correlation information for each application-level message further includes an identification of the each application-level message'"'"'s sending service and receiving service.

3. The method as recited in claim 1, wherein the retained correlation information for each application-level message further includes an indication as to whether the each application-level message has completed transmission.

4. The method as recited in claim 3, wherein the retained correlation information for each application-level message further includes a reason or error log regarding why the each application-level message has failed to complete its transmission if the each application-level message has failed.

5. The method as recited in claim 1, wherein the retained correlation information for each application-level message further includes a portion of the each message content.

6. The method as recited in claim 1, wherein the retained correlation information for each application-level message further includes two or more of the following:

an identification of the each application-level message'"'"'s sending and receiving service, an indication as to whether the each application-level message has completed transmission, a reason or error log regarding why the each application-level message has failed to complete its transmission if the each application-level message has failed, and a portion of the each application-level message content, a size of the each application-level message, a topic of the each application-level message, a status on processing steps taken on the each application-level message, or specification of any protocols used in receiving and sending the each application-level message.

7. The method as recited in claim 1, wherein the call information for each call includes a Call Identifier (ID) uniquely identifying the each call.

8. The method as recited in claim 7, wherein the call information for each call further includes two or more of the following:

an indication as to whether the each call is complete and a reason for the call not being complete if the each call fails to complete, a type of each call, a receiving and sending time for the each call, a sender and recipient service of each call, a status of policy evaluation for each call, or a set of hops in each call.

9. The method as recited in claim 1, wherein the session information for each session includes a Session Identifier (ID) uniquely identifying the each session.

10. The method as recited in claim 9, wherein the session information for each session further includes an indication as to whether the each session is complete and a reason for the session not being complete if the each session fails to complete.

11. The method as recited in claim 9, wherein the session information for each session further includes a calculated or executed route for application-level messages sent within the each session.

12. The method as recited in claim 11, wherein the session information for each session further includes an identity and status of each service of the each session.

13. The method as recited in claim 9, wherein the session information for each session further includes two or more of the following:

an indication as to whether the each session is complete and a reason for the session not being complete if the each session fails to complete, a calculated or executed route for messages sent within the each session, and an identity and status of each service of the each session, an initiating time and completion time for each session, or an indication of a set of calls in each session.

14. The method as recited in claim 1, wherein each application-level message belongs to a particular call between two of the services.

15. The method as recited in claim 1, wherein each call includes a request message and a response message or a notification message.

16. The method as recited in claim 1, wherein a call is defined as a set of predefined application-level message types.

17. The method as recited in claim 1, wherein a session is determined by the services which send application-level messages for the set of calls as a set of calls.

18. The method as recited in claim 1, wherein at least some of services are implemented on different computer systems and at least some of these computer systems differ from a computer system which implements the message interchange network.

19. The method as recited in claim 1, wherein the retaining of correlating information comprises:

receiving a current application-level message at the message interchange network, wherein the current application-level message belongs to a current session and a current call;

when the received current application-level message is received for the current session, assigning a session identifier for the current message and embedding the session identifier in the current application-level message prior to forwarding the application-level message to the one or more services specified by the current application-level message;

when the received current application-level message is received first for the current call, assigning a call identifier for the current application-level message and embedding the call identifier in the current application-level message prior to forwarding the application-level message to the one or more services specified by the current application-level message;

assigning a hop identifier for the current application-level message which uniquely identifies the current application-level message; and

associating and storing the session identifier, the call identifier, and the hop identifier, along with message information, call information, and session information for the received application-level message.

20. The method as recited in claim 1,

wherein the query for the retained correlation information is regarding a particular session or call;

and

wherein the specific portions of the retained correlation information that are sent to the first service are related to the particular session or call of the query.

21. The method as recited in claim 20, wherein the specific one or more portions of the retained correlation information, that are sent to the first service, include information regarding application-level messages sent between more than two services.

22. The method as recited in claim 20, further comprising determining whether the first service is authorized to make the query and only sending the specific one or more portions of the retained correlation information that are sent to the first service when it is determined that the first service is authorized.

23. The method as recited in claim 1, wherein at least one of the services is a routing script.

24. The method as recited in claim 1, wherein the retained correlation information includes at least one message identifier specified in at least one of the application-level messages which is sent by a sending service, the method further comprising:

receiving a query for the retained correlation information regarding a particular message identifier, wherein the query is sent by a second one of the services; and

sending correlation information to the second service related to the particular message identifier of the query.

25. A computer system operable to correlate services within a computer network the computer system comprising:

one or more processors;

one or more memory, wherein at least one of the processors and memory are adapted for;

providing a message interchange network for exchanging application-level messages between services that are located outside the message interchange network;

registering, at the message interchange network, each of the plurality of services so that each service is specified as being accessible by one or more of the plurality of services according to one or more properties and permissions associated with each of the plurality of services;

receiving, at the message interchange network, a plurality of application-level messages that each specify one or more of the plurality of services that are to receive the each application-level message and forwarding each received application-level message towards its specified service according to the one or more properties and permissions associated with the specified service;

retaining correlation information regarding each application-level message received into message interchange network, wherein the application-level messages are being sent between pairs of the services, wherein the retained correlation information for each application-level message pertains to each application-level message and any other application-level messages related to the each application-level message, the retained correlation information including one or more of;

a Hop Identifier (ID) uniquely identifying a hop between a sender and receiver of the each application-level message, call information regarding a call to which the each application-level message and any other related application-level message belongs, or session information regarding a session to which the each application-level message and any other related application-level message belongs, wherein the correlation information is retained in a searchable format that is accessible by the message interchange network;

receiving, at the message interchange network, a query from a first service to search the retained correlation information for a specific one or more portions of the retained correlation information; and

sending, to the first service, a response to the query that includes the specific one or more portions of the retained correlation information.

26. The computer system as recited in claim 25, wherein the retained correlation information for each application-level message further includes two or more of the following:

an identification of the each application-level message'"'"'s sending and receiving service, an indication as to whether the each application-level message has completed transmission, a reason or error log regarding why the each application-level message has failed to complete its transmission if the each application-level message has failed, and a portion of the each application-level message content, a size of the each application-level message, a topic of the each application-level message, a status on processing steps taken on the each application-level message, or specification of any protocols used in receiving and sending the each application-level message.

27. The computer system as recited in claim 25, wherein the call information for each call includes a Call Identifier (ID) uniquely identifying the each call.

28. The computer system as recited in claim 27, wherein the call information for each call further includes two or more of the following:

an indication as to whether the each call is complete and a reason for the call not being complete if the each call fails to complete, a type of each call, a receiving and sending time for the each call, a sender and recipient service of each call, a status of policy evaluation for each call, or a set of hops in each call.

29. The computer system as recited in claim 25, wherein the session information for each session includes a Session Identifier (ID) uniquely identifying the each session.

30. The computer system as recited in claim 29, wherein the session information for each session further includes two or more of the following:

an indication as to

whether the each session is complete and a reason for the session not being complete if the each session fails to complete, a calculated or executed route for messages sent within the each session, and an identity and status of each service of the each session, an initiating time and completion time for each session, or an indication of a set of calls in each session.

31. The computer system as recited in claim 27, wherein each call includes a request message and a response message or a notification message.

32. The computer system as recited in claim 25, wherein a call is defined as a set of predefined application-level message types.

33. The computer system as recited in claim 32, wherein a session is determined by the services which send application-level messages for the set of calls as a set of calls.

34. The computer system as recited in claim 25, wherein at least some of services are implemented on difference computer systems and at least some of these computer systems differ from a computer system which implements the message interchange network.

35. The computer system as recited in claim 25, wherein the retaining of correlating information comprises:

receiving a current application-level message at the message interchange network, wherein the current application-level message belongs to a current session and a current call;

when the received current application-level message is a first message received for the current session, assigning a session identifier for the current message and embedding the session identifier in the current application-level message prior to forwarding the application-level message to the one or more services specified by the current application-level message;

when the received current application-level message is received first for the current call, assigning a call identifier for the current application-level message and embedding the call identifier in the current application-level message prior to forwarding the application-level message to the one or more services specified by the current application-level message;

assigning a hop identifier for the current application-level message which uniquely identifies the current application-level message; and

associating and storing the session identifier, the call identifier, and the hop identifier, along with message information, call information, and session information for the received application-level message.

36. The computer system as recited in claim 25,

wherein the query for the retained correlation information is regarding a particular session or call;

and

wherein the specific portions of the retained correlation information that are sent to the first service are related to the particular session or call of the query.

37. The computer system as recited in claim 25, wherein at least one of the services is a routing script.

38. A computer program product for correlating services within a computer network, the computer program product comprising:

at least one computer readable medium;

computer program instructions stored within the at least one computer readable medium configured for;

providing a message interchange network for exchanging application-level messages between services that are located outside the message interchange network;

registering, at the message interchange network, each of the plurality of services so that each service is specified as being accessible by one or more of the plurality of services according to one or more properties and permissions associated with each of the plurality of services;

receiving, at the message interchange network, a plurality of application-level messages that each specify one or more of the plurality of services that are to receive the each application-level message and forwarding each received application-level message towards its specified service according to the one or more properties and permissions associated with the specified service;

retaining correlation information regarding each application-level message received into message interchange network, wherein the application-level messages are being sent between pairs of the services, wherein the retained correlation information for each application-level message pertains to each application-level message and any other application-level messages related to the each application-level message, the retained correlation information including one or more of;

a Hop Identifier (ID) uniquely identifying a hop between a sender and receiver of the each application-level message, call information regarding a call to which the each application-level message and any other related application-level message belongs, or session information regarding a session to which the each application-level message and any other related application-level message belongs, wherein the correlation information is retained in a searchable format that is accessible by the message interchange network;

receiving, at the message interchange network, a query from a first service to search the retained correlation information for a specific one or more portions of the retained correlation information; and

sending, to the first service, a response to the query that includes the specific one or more portions of the retained correlation information.

39. The computer program product as recited in claim 38, wherein the retained correlation information for each application-level message further includes an identification of the each application-level message'"'"'s sending service and receiving service.

40. The computer program product as recited in claim 38, wherein the retained correlation information for each application-level message further includes an indication as to whether the each application-level message has completed transmission.

41. The computer program product as recited in claim 40, wherein the retained correlation information for each application-level message further includes a reason or error log regarding why the each application-level message has failed to complete its transmission if the each application-level message has failed.

42. The computer program product as recited in claim 38, wherein the retained correlation information for each application-level message further includes a portion of the each message content.

43. The computer program product as recited in claim 38, wherein the retained correlation information for each application-level message further includes two or more of the following:

an identification of the each application-level message'"'"'s sending and receiving service, an indication as to whether the each application-level message has completed transmission, a reason or error log regarding why the each application-level message has failed to complete its transmission if the each application-level message has failed, and a portion of the each application-level message content, a size of the each application-level message, a topic of the each application-level message, a status on processing steps taken on the each application-level message, or specification of any protocols used in receiving and sending the each application-level message.

44. The computer program product as recited in claim 38, wherein the call information for each call includes a Call Identifier (ID) uniquely identifying the each call.

45. The computer program product as recited in claim 44, wherein the call information for each call further includes two or more of the following:

an indication as to whether the each call is complete and a reason for the call not being complete if the each call fails to complete, a type of each call, a receiving and sending time for the each call, a sender and recipient service of each call, a status of policy evaluation for each call, and a set of hops in each call.

46. The computer program product as recited in claim 38, wherein the session information for each session includes a Session Identifier (ID) uniquely identifying the each session.

47. The computer program product as recited in claim 46, wherein the session information for each session further includes an indication as to whether the each session is complete and a reason for the session not being complete if the each session fails to complete.

48. The computer program product as recited in claim 46, wherein the session information for each session further includes a calculated or executed route for application-level messages sent within the each session.

49. The computer program product as recited in claim 46, wherein the session information for each session further includes an identity and status of each service of the each session.

50. The computer program product as recited in claim 46, wherein the session information for each session further includes two or more of the following:

an indication as to whether the each session is complete and a reason for the session not being complete if the each session fails to complete, a calculated or executed route for messages sent within the each session, and an identity and status of each service of the each session, a initiating time and completion time for each session, or an indication of a set of calls in each session.

51. The computer program product as recited in claim 38, wherein each application-level message belongs to a particular call between two of the services.

52. The computer program product as recited in claim 38, wherein each call includes a request message and a response message or a notification message.

53. The computer program product as recited in claim 38, wherein a call is defined as a set of predefined application-level message types.

54. The computer program product as recited in claim 38, wherein a session is determined by the services which send application-level messages for the set of calls as a set of calls.

55. The computer program product as recited in claim 38, wherein at least some of services are implemented on difference computer systems and at least some of these computer systems differ from a computer system which implements the message interchange network.

56. The computer program product as recited in claim 38, wherein the retaining of correlating information comprises:

receiving a current application-level message at the message interchange network, wherein the current application-level message belongs to a current session and a current call;

when the received current application-level message is a first message received for the current session, assigning a session identifier for the current message and embedding the session identifier in the current application-level message prior to forwarding the application-level message to the one or more services specified by the current application-level message;

when the received current application-level message is received first for the current call, assigning a call identifier for the current application-level message and embedding the call identifier in the current application-level message prior to forwarding the application-level message to the one or more services specified by the current application-level message;

assigning a hop identifier for the current application-level message which uniquely identifies the current application-level message; and

associating and storing the session identifier, the call identifier, and the hop identifier, along with message information, call information, and session information for the received application-level message.

57. The computer program product as recited in claim 38,

wherein the query for the retained correlation information is regarding a particular session or call;

and

wherein the specific portions of the retained correlation information that are sent to the first service are related to the particular session or call of the query.

58. The computer program product as recited in claim 57, wherein the specific one or more portions of the retained correlation information, that are sent to the first service, include information regarding application-level messages sent between more than two services.

59. The computer program product as recited in claim 57, wherein the computer program product is further configured for determining whether the first service is authorized to make the query and only sending the specific one or more portions of the retained correlation information that are sent to the first service when it is determined that the first service is authorized.

60. The computer program product as recited in claim 38, wherein at least one of the services is a routing script.

61. The computer program product as recited in claim 38, wherein the retained correlation information includes at least one message identifier specified in at least one of the application-level messages which is sent by a sending service, and wherein the computer program product is further configured for:

receiving a query for the retained correlation information regarding a particular message identifier, wherein the query is sent by a second one of the services; and

sending a portion of the retained correlation information to the second service related to the particular message identifier of the query.