Apparatus and methods for mediating messages

• US 8,775,654 B2
• Filed: 12/19/2003
• Issued: 07/08/2014
• Est. Priority Date: 12/19/2003
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Shkvarchuk, Taras, Hinks, Paul
• Primary Examiner(s): TANG, KAREN C
• Application Number:
  US10/742,513
• Publication Number:
  US 20050138210A1
• Time in Patent Office: 3,854 Days
• Field of Search: 709/249, 709/238
• US Class Current: 709/231
• CPC Class Codes: H04L 51/063 Content adaptation, e.g. replacement of unsuitable content
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]

Abstract

Disclosed are methods and apparatus for effectively mediating communications between entities in a computer network. In general, a format preference for a first service is received into a message interchange network. The format preference specifies an expected format for messages received by such first service without specifying a format for any other services. The format preference for the first service is then stored in a repository associated with the message interchange network. Messages sent to the first service are then mediated using the format preference stored for the first service so that the first service receives messages in the expected format specified by the format preference stored for the first service.

Claims

1. A method for mediating messages within a message interchange network for facilitating communication among a plurality of entities, each entity having policy data corresponding thereto governing interaction with the entity via the message interchange network, the method comprising:

a) receiving a format preference for a first service in the message interchange network, wherein the format preference specifies an expected format for messages received by such first service, the expected format from a group including MIME (Multipurpose Internet Mail Extensions), DIME (Direct Internet Mail Extensions), AS2 (Applicability Statement

     2), and SOAP (Simple Object Access Protocol);

b) storing the format preference in a repository associated with the message interchange network; and

c) mediating messages sent to the first service using the format preference stored for the first service by receiving the messages,

determining a received format of the messages by inspecting at least one of the received messages,

translating the messages into the expected format specified by the format preference for the first service, and

sending the translated messages to the first service in the expected format, the translated messages having the specified message format.

2. The method of claim 1, wherein a second service sends messages to the first service via the message interchange network without specifying the format preference for the first service.

3. The method of claim 2, wherein a provider associated with the second service does not have information relating to the format preference of the first service.

4. The method of claim 1, wherein mediating messages further comprises:

comparing the format of the received message to the stored format preference associated with the first service;

translating the format of the received message into the format specified by the format preference if the format of the received message does not match the stored format preference associated with the first service.

5. The method of claim 4, further comprising repeating steps (a) through (c) for a plurality of services and a plurality of corresponding format preferences.

6. The method of claim 4, wherein the format of the received message is MIME (Multipurpose Internet Mail Extensions).

7. The method of claim 6, wherein the stored formatting preference associated with the first service is DIME (Direct Internet Mail Extensions).

8. The method of claim 7, wherein translating the received message from MIME to DIME further comprises setting a content type, parsing the received message and writing a new DIME record copying one or more MIME headers.

9. The method of claim 1, wherein messages are sent to the message interchange network via a public network.

10. The method of claim 9, wherein the public network is the Internet.

11. The method of claim 4, wherein the format of the received message is DIME.

12. The method of claim 11, wherein the stored formatting preference associated with the first service is MIME.

13. The method of claim 12, wherein translating the received message from DIME to MIME comprises setting a content type and writing MIME boundaries, headers, and payloads.

14. The method of claim 4, wherein the format of the received message is SOAP (Simple Object Access Protocol) and the stored format preference associated with the first service is AS2 (Applicability Statement 2).

15. The method of claim 14, wherein translating the received message from SOAP to AS2 comprises stripping a SOAP part from the received message.

16. The method of claim 15, wherein translating further comprises replacing SOAP message headers with AS2 message headers, setting content-type, and providing content between MIME boundaries.

17. The method of claim 4, wherein the format of the received message is AS2 and the stored format preference associated with the first service is SOAP.

18. The method of claim 4, wherein determining a received format associated with the message includes scanning the received message to determine the format.

19. The method of claim 4, wherein determining a received format associated with the received message is based on the format specified in a header of the encoded message.

20. The method of claim 4, wherein determining a received format associated with the received message is based on the second format preference associated with the second service.

21. The method of claim 1, wherein the repository is a database associated with a message interchange network.

22. The method of claim 1, wherein the first format preference is received over a network.

23. The method of claim 1, wherein the first format preference is input at the message interchange network.

24. The method of claim 23, wherein the format preference is input via a graphical user interface.

25. A computer system that mediates encoded messages within a message interchange network for facilitating communication among a plurality of entities, each entity having policy data corresponding thereto governing interaction with the entity via the message interchange network, the computer system comprising:

one or more processors;

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

a) receiving a format preference for a first service into the message interchange network, wherein the format preference specifies an expected format for messages received by such first service, the expected format from a group including MIME (Multipurpose Internet Mail Extensions), DIME (Direct Internet Mail Extensions), AS2 (Applicability Statement

     2), and SOAP (Simple Object Access Protocol);

b) storing the format preference in a repository associated with the message interchange network; and

c) mediating messages sent to the first service using the format preference stored for the first service by receiving the messages,

determining a received format of the messages by inspecting at least one of the received messages,

translating the messages into the expected format specified by the format preference for the first service, and

sending the translated messages to the first service in the expected format, the translated messages having the specified message format.

26. The computer system of claim 25, wherein a second service sends messages to the first service via the message interchange network without specifying the format preference for the first service.

27. The computer system of claim 26, wherein a provider associated with the second service does not have information relating to the format preference of the first service.

28. The computer system of claim 25, wherein mediating messages further comprises:

comparing the format of the received message to the stored format preference associated with the first service;

translating the format of the received message into the format specified by the format preference if the format of the received message does not match the stored format preference associated with the first service.

29. The computer system of claim 28, wherein the format of the received message is MIME, DIME, AS2 or SOAP.

30. The computer system of claim 28, wherein the stored formatting preference associated with the first service is MIME, DIME, AS2 or SOAP.

31. The computer system of claim 25, wherein messages are sent to the message interchange network via a public network.

32. The computer system of claim 31, wherein the public network is the Internet.

33. The computer system of claim 28, wherein determining a received format associated with the message includes scanning the received message to determine the format.

34. The computer system of claim 28, wherein determining a received format associated with the received message is based on the format specified in a header of the encoded message.

35. The computer system of claim 28, wherein determining a received format associated with the received message is based on the second format preference associated with the second service.

36. The computer system of claim 25, wherein the first format preference is received over a network.

37. The computer system of claim 25, wherein the first format preference is input at the message interchange network via a graphical user interface.

38. A computer program product for mediating encoded messages within a message interchange network for facilitating communication among a plurality of entities, each entity having policy data corresponding thereto governing interaction with the entity via the message interchange network, the computer program product comprising:

at least one tangible computer readable medium;

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

a) receiving a format preference for a first service into the message interchange network, wherein the format preference specifies an expected format for messages received by such first service, the expected format from a group including MIME (Multipurpose Internet Mail Extensions), DIME (Direct Internet Mail Extensions), AS2 (Applicability Statement

     2), and SOAP (Simple Object Access Protocol);

b) storing the format preference in a repository associated with the message interchange network; and

c) mediating messages sent to the first service using the format preference stored for the first service by receiving the messages,

determining a received format of the messages by inspecting at least one of the received messages,

translating the messages into the expected format specified by the format preference for the first service, and

sending the translated messages to the first service in the expected format, the translated messages having the specified message format.

39. The computer program product of claim 38, wherein a second service sends messages to the first service via the message interchange network without specifying the format preference for the first service.

40. The computer program product of claim 39, wherein a provider associated with the second service does not have information relating to the format preference of the first service.

41. The computer program product of claim 38, wherein mediating messages further comprises:

comparing the format of the received message to the stored format preference associated with the first service;

translating the format of the received message into the format specified by the format preference if the format of the received message does not match the stored format preference associated with the first service.

42. The computer program product of claim 41, further comprising repeating steps (a) through (c) for a plurality of services and a plurality of corresponding format preferences.

43. The computer program product of claim 41, wherein the format of the received message is MIME.

44. The computer program product of claim 43, wherein the stored formatting preference associated with the first service is DIME.

45. The computer program product of claim 44, wherein translating the received message from MIME to DIME further comprises setting a content type, parsing the received message and writing a new DIME record copying one or more MIME headers.

46. The computer program product of claim 38, wherein messages are sent to the message interchange network via a public network.

47. The computer program product of claim 46, wherein the public network is the Internet.

48. The computer program product of claim 41, wherein the format of the received message is DIME.

49. The computer program product of claim 48, wherein the stored formatting preference associated with the first service is MIME.

50. The computer program product of claim 49, wherein translating the received message from DIME to MIME comprises setting a content type and writing MIME boundaries, headers, and payloads.

51. The computer program product of claim 41, wherein the format of the received message is SOAP and the stored format preference associated with the first service is AS2.

52. The computer program product of claim 51, wherein translating the received message from SOAP to AS2 comprises stripping a SOAP part from the received message.

53. The computer program product of claim 52, wherein translating further comprises replacing SOAP message headers with AS2 message headers, setting content-type, and providing content between MIME boundaries.

54. The computer program product of claim 41, wherein the format of the received message is AS2 and the stored format preference associated with the first service is SOAP.

55. The computer program product of claim 41, wherein determining a received format associated with the message includes scanning the received message to determine the format.

56. The computer program product of claim 41, wherein determining a received format associated with the received message is based on the format specified in a header of the encoded message.

57. The computer program product of claim 41, wherein determining a received format associated with the received message is based on the second format preference associated with the second service.

58. The computer program product of claim 38, wherein the repository is a database associated with a message interchange network.

59. The computer program product of claim 38, wherein the first format preference is received over a network.

60. The computer program product of claim 38, wherein the first format preference is input at the message interchange network.

61. The computer program product of claim 60, wherein the format preference is input via a graphical user interface.