Method, system, and computer program product for managing interchange of enterprise data messages

• US 9,083,601 B2
• Filed: 05/04/2010
• Issued: 07/14/2015
• Est. Priority Date: 03/26/2001
• Status: Expired due to Term

• Current Assignee: Grand Central Networks, Inc., Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Brouk, Lev, Norton, Kenneth, Douglas, Jason, Panec, Peter
• Primary Examiner(s): Choudhury, Azizul
• Assistant Examiner(s): NAJEE-ULLAH, TARIQ S
• Application Number:
  US12/773,776
• Publication Number:
  US 20100218245A1
• Time in Patent Office: 1,897 Days
• Field of Search: 709/203, 709/206, 709/227, 709/238
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 45/00 Routing or path finding of packets in data switching networks routing or path finding in wireless networks H04W40/00
• CPC Class Codes: H04L 45/70 Routing based on monitoring results
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• 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/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

A system and method for enabling the interchange of enterprise data through an open platform is disclosed. This open platform can be based on a standardized interface that enables parties to easily connect to and use the network. Services operating as senders, recipients, and in-transit parties can therefore leverage a framework that overlays a public network.

Claims

1. A method for managing interchange of enterprise data messages, comprising:

authenticating a sending service to a message interchange network using information stored by the message interchange network;

receiving a message at the message interchange network from the sending service, wherein the message is generated to include a header that conforms to an XML schema and a body portion and is routed from the sending service to the message interchange network;

storing the message by the message interchange network;

authenticating a receiving service to the message interchange network using other information stored by the message interchange network; and

providing the message to the receiving service when the receiving service polls the message interchange network for stored messages;

wherein the receiving service periodically polls the message interchange network for messages routed to the message interchange network;

wherein messages received by the receiving service from the message interchange network have been filtered by one or more predetermined values and, as a result, include a subset of the messages routed to the message interchange network associated with the one or more predetermined values;

wherein the header of the message defines a time-to-live specifying an expiration time for the message on the message interchange network such that a lifetime of the message on the message interchange network is controlled by;

determining that the specified expiration time has passed before a retrieving of the message from the message interchange network by the receiving service, and in response to determining that the specified expiration time has passed before the retrieving of the message from the message interchange network by the receiving service, aborting further routing of the message.

2. The method of claim 1, wherein header information in the header affects routing of the message.

3. The method of claim 1, further comprising receiving an authentication token provided by the message interchange network.

4. The method of claim 1, wherein the receiving service uses a secure HTTPS protocol.

13. The method of claim 1, wherein the information for the sending service that is used by the message interchange network to authenticate the sending service includes a sending token issued for the sending service by the message interchange network.

14. The method of claim 13, wherein the sending token is issued by the message interchange network in response to authentication of a username and password for the sending service.

15. The method of claim 1, wherein the information for the sending service that is used for the authentication of the sending service by the message interchange network includes authentication information.

16. The method of claim 15, wherein the authentication information is generated in response to registration of the sending service with the message interchange network.

17. The method of claim 1, wherein the other information for the receiving service that is used by the message interchange network to authenticate the receiving service includes a receiving token issued for the receiving service by the message interchange network.

18. The method of claim 17, wherein the receiving token is issued by the message interchange network in response to authentication of a username and password for the receiving service.

19. The method of claim 1, wherein the sending service and the receiving service are each an application of a different organization, wherein each application of each organization is a different service connected to the message interchange network.

20. The method of claim 1, wherein the sending service and the receiving service each register with the message interchange network.

21. The method of claim 1, wherein the message interchange network includes a policy.

22. The method of claim 21, wherein the policy is specified by the receiving service.

23. The method of claim 1, wherein the message interchange network handles the message based on a type of the message.

24. The method of claim 1, wherein the message interchange network determines whether the message is a duplicate of a previous message routed to the message interchange network.

25. The method of claim 1, wherein the lifetime of the message on the message interchange network is controlled by:

determining that a specified expiration time has passed before a retrieving of the message from the message interchange network by the receiving service,

in response to determining that the specified expiration time has passed before the retrieving of the message from the message interchange network by the receiving service, aborting further routing of the message.

26. The method of claim 1, wherein a set of arguments that define actions the receiving service will perform are included in the message by the sending service such that the receiving service receives the set of arguments with the message.

27. The method of claim 1, wherein the sending service and the receiving service are each registered with the message interchange network in order to communicate using the message interchange network, wherein the registration of the sending service with the message interchange network results in an association of at least one of a property and a permission with the sending service.

28. The method of claim 27, wherein the at least one of the property and the permission associated with the sending service includes at least one of a unique service identifier and authentication information, and wherein the at least one of the property and the permission affects routing of the message from the sending service.

5. A system for managing interchange of enterprise data messages, comprising:

a hardware processor for;

authenticating a sending service to a message interchange network using information stored by the message interchange network;

receiving a message at the message interchange network from the sending service, wherein the message is generated to include a header that conforms to an XML schema and a body portion and is routed from the sending service to the message interchange network;

storing the message by the message interchange network;

authenticating a receiving service to the message interchange network using other information stored by the message interchange network; and

providing the message to the receiving service when the receiving service polls the message interchange network for stored messages;

wherein the receiving service periodically polls the message interchange network for messages routed to the message interchange network;

wherein the system is operable such that messages received by the receiving service from the message interchange network have been filtered by one or more predetermined values and, as a result, include a subset of the messages routed to the message interchange network associated with the one or more predetermined values;

wherein the header of the message defines a time-to-live specifying an expiration time for the message on the message interchange network such that a lifetime of the message on the message interchange network is controlled by;

determining that the specified expiration time has passed before a retrieving of the message from the message interchange network by the receiving service, and in response to determining that the specified expiration time has passed before the retrieving of the message from the message interchange network by the receiving service, aborting further routing of the message.

6. The system of claim 5, wherein that header information in the header affects routing of the message.

7. The system of claim 5, wherein the hardware processor is further for receiving an authentication token provided by the message interchange network.

8. The system of claim 5, wherein the receiving service uses a secure HTTPS protocol.

9. A computer program product, comprising a non-transitory computer usable medium having a computer readable program code embodied therein, the computer readable program code adapted to be executed to cause a computer to implement a method comprising:

authenticating a sending service to a message interchange network using information stored by the message interchange network;

receiving a message at the message interchange network from the sending service, wherein the message is generated to include a header that conforms to an XML schema and a body portion and is routed from the sending service to the message interchange network;

storing the message by the message interchange network;

authenticating a receiving service to the message interchange network using other information stored by the message interchange network; and

providing the message to the receiving service when the receiving service polls the message interchange network for stored messages;

wherein the receiving service periodically polls the message interchange network for messages routed to the message interchange network;

wherein the computer program product is operable such that messages received by the receiving service from the message interchange network have been filtered by one or more predetermined values and, as a result, include a subset of the messages routed to the message interchange network associated with the one or more predetermined values;

wherein the header of the message defines a time-to-live specifying an expiration time for the message on the message interchange network such that a lifetime of the message on the message interchange network is controlled by;

determining that the specified expiration time has passed before a retrieving of the message from the message interchange network by the receiving service, and in response to determining that the specified expiration time has passed before the retrieving of the message from the message interchange network by the receiving service, aborting further routing of the message.

10. The computer program product of claim 9, wherein header information in the header affects routing of the message.

11. The computer program product of claim 9, further comprising receiving an authentication token provided by the message interchange network.

12. The computer program product of claim 9, wherein the receiving service uses a secure HTTPS protocol.