Method and system for exchanging messages between entities on a network comprising an actor attribute and a mandatory attribute in the header data structure

• US 7,069,335 B1
• Filed: 08/09/2000
• Issued: 06/27/2006
• Est. Priority Date: 08/10/1999
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Atkinson, Robert George, Layman, Andrew J., Thatte, Satish R., Kakivaya, Gopal Krishna R., Neilsen, Henrik F.
• Primary Examiner(s): Dharia, Rupal
• Assistant Examiner(s): Nguyen, Quang N.
• Application Number:
  US09/636,003
• Time in Patent Office: 2,148 Days
• Field of Search: 709204-207, 709/224, 709/230, 709/232, 709236-238, 709/242, 709/245, 709/248, 709/317, 379/88.14, 358/1.15
• US Class Current: 709/238
• CPC Class Codes: G06F 16/986 Document structures and storage, e.g. HTML extensions
• CPC Class Codes: G06F 9/547 Remote procedure calls [RPC]; Web services
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

Using a message exchanger (“message exchanger”), data messages are exchanged between entities in a decentralized, distributed, potentially heterogeneous, network environment. The message exchanger employs XML (extensible Markup Language). To accomplish this, the entities on both ends of the message exchange understand, identify, and parse the message format. The message exchanger defines such a mechanism. Data messages are broken down into two portions—one portion (the body) is intended from an ultimate destination and the other portion (the header) is intended for intermediate destination and/or the ultimate destination. The body may be defined so that it must be understood by the ultimate destination. The header may be defined so that it must be understood or changed. Regardless, the data in the body is delivered intact to the ultimate destination. The message exchanger defines a message envelope exchange format in XML over a transport protocol, such as HTTP (HyperText Transport Protocol). This format allows for the execution of RPC (Remote Procedure Call) over XML, but it can be used for any message exchange over a network.

Claims

1. A method of formatting a message for exchange between entities on a network, the method comprising:

generating a message envelope;

generating contents of the message envelope, the contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of that entity and a mandatory attribute indicating that an explicit request for that entity to perform a task in the data structure must be understood and processed by that entity.

2. A method as recited in claim 1, wherein each data structure specifies whether the entity that is intended to process the data structure must understand such data structure.

3. A method as recited in claim 1, wherein:

the message envelope has beginning and ending envelope tags;

the contents of the message envelope is between the envelope tags.

4. A method as recited in claim 1, wherein the contents include:

a header data structure;

a body data structure, the body data structure including message data.

5. A method as recited in claim 4, wherein:

the header data structure has beginning and ending header tags;

the body data structure has beginning and ending body tags.

6. A method as recited in claim 4, wherein:

the header data structure is intended for at least one intermediate entity;

the body data structure is intended for a destination entity.

7. A method as recited in claim 1 further comprising sending the message envelope to an entity on a network.

8. A method as recited in claim 1, wherein the data structures lack executable instructions for performing the task.

9. A method as recited in claim 1, wherein the data structures are expressed in a markup language.

10. A method as recited in claim 1, wherein the data structures are expressed in XML.

11. A method as recited in claim 1 further comprising:

formatting the message envelope for sending over a network using HTTP;

sending the message envelope to an entity on the network by using HTTP.

12. A method as recited in claim 1 further comprising:

binding the message envelope into a HTTP request;

sending the message envelope to an entity on the network by using HTTP.

13. A method as recited in claim 1 further comprising;

binding the message envelope into a HTTP response;

sending the message envelope to an entity on the network by using HTTP.

14. A method as recited in claim 3, wherein the envelope tags identify the message envelope.

15. A method as recited in claim 5, wherein the header tags identify the header data structure.

16. A method as recited in claim 5, wherein the body tags identify the body data structure.

17. A method as recited in claim 4, wherein the message envelope has the following format:

18. A method of delivering a message over a network, the method comprising:

transmitting a message envelope of a message from an origin entity to a destination entity via one or more intermediate entities on the network;

the message envelope having contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of the destination entity and a mandatory attribute indicating that an explicit request for the destination entity to perform a task in the data structure must be understood and processed by the destination entity.

19. A method as recited in claim 18, wherein each data structure specifies whether the entity that is intended to process the data structure must understand such data structure when that entity receives the message envelope over the network.

20. A method as recited in claim 18, wherein:

the message envelope has beginning and ending envelope tags;

the contents of the message envelope is between the envelope tags.

21. A method as recited in claim 18, wherein the contents include:

a header data structure;

a body data structure, the body data structure including message data.

22. A method as recited in claim 21, wherein:

the header data structure has beginning and ending header tags;

the body data structure has beginning and ending body tags.

23. A method as recited in claim 21, wherein:

the header data structure is intended for at least one intermediate entity;

the body data structure is intended for a destination entity.

24. A method as recited in claim 18, wherein the data structures lack executable instructions for performing the task.

25. A method as recited in claim 18, wherein at least one of the data structures includes a request for an intermediate entity to perform a task.

26. A method as recited in claim 18, wherein the data structures are expressed in a markup language.

27. A method as recited in claim 18, wherein the data structures are expressed in XML.

28. A method as recited in claim 18 further comprising:

formatting the message envelope for sending over a network using HTTP;

sending the message envelope to an entity on the network by using HTTP.

29. A method as recited in claim 18 further comprising:

binding the message envelope into a HTTP request;

sending the message envelope to an entity on the network by using HTTP.

30. A method as recited in claim 18 further comprising:

binding the message envelope into a HTTP response;

sending the message envelope to an entity on the network by using HTTP.

31. A method as recited in claim 20, wherein the envelope tags identify the message envelope.

32. A method as recited in claim 22, wherein the header tags identify the header data structure.

33. A method as recited in claim 22, wherein the body tags identify the body data structure.

34. A method as recited in claim 21, wherein the message envelope has the following format:

35. A method of parsing a message received by a receiving entity over a network from a sending entity, the method comprising:

parsing a message envelope;

parsing contents of the message envelope, the contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of the receiving entity and a mandatory attribute indicating that an explicit request for the receiving entity to perform a task in the data structure must be understood and processed by the receiving entity.

36. A method as recited in claim 35, wherein each data structure specifies whether the entity that is intended to process the data structure must understand such data structure when that entity receives the message envelope over the network.

37. A method as recited in claim 36 further comprising if the entity that is intended to process the data structure does not understand such data structure, sending a response message to the sending entity that indicates that the entity did not understand such data structure.

38. A method as recited in claim 35 further comprising sending a response message to the sending entity on the network.

39. A method as recited in claim 35, wherein:

the message envelope has beginning and ending envelope tags;

the contents of the message envelope is between the envelope tags.

40. A method as recited in claim 35, wherein the contents include:

a header data structure;

a body data structure, the body data structure including message data.

41. A method as recited in claim 40, wherein:

the header data structure has beginning and ending header tags;

the body data structure has beginning and ending body tags.

42. A method as recited in claim 40, wherein:

the header data structure is intended for at least one intermediate entity;

the body data structure is intended for a destination entity.

43. A method as recited in claim 35, wherein the data structures lack executable instructions for performing the task.

44. A method as recited in claim 35, wherein the data structures are expressed in a markup language.

45. A method as recited in claim 35, wherein the data structures are expressed in XML.

46. A computer-readable storage medium having computer-executable instructions that, when executed by a computer, performs a method of formatting a message for exchange between entities on a network, the method comprising:

generating a message envelope;

generating contents of the message envelope, the contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of that entity and a mandatory attribute indicating that an explicit request for that entity to perform a task in the data structure must be understood and processed by that entity.

47. A computer-readable storage medium having computer-executable instructions that, when executed by a computer, performs a method of delivering a message between entities on a network, the method comprising:

transmitting a message envelope of a message from an origin entity to a destination entity via one or more intermediate entities on the network;

the message envelope having contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of the destination entity and a mandatory attribute indicating that an explicit request for the destination entity to perform a task in the data structure must be understood and processed by the destination entity.

48. A computer-readable storage medium having computer-executable instructions that, when executed by a computer, performs a method of parsing a message received by a receiving entity over a network from a sending entity, the method comprising:

parsing a message envelope of a message;

parsing contents of the message envelope, the contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of the receiving entity and a mandatory attribute indicating that an explicit request for the receiving entity to perform a task in the data structure must be understood and processed by the receiving entity.

49. A message exchange apparatus comprising:

a processor;

a message formatter executable on the processor to;

generate a message envelope;

generate contents of the message envelope, the contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of that entity and a mandatory attribute indicating that an explicit request for that entity to perform a task in the data structure must be understood and processed by that entity.

50. A message exchange apparatus comprising:

a processor;

a message deliverer executable on the processor to;

transmit a message envelope of a message from an origin entity to a destination entity via one or more intermediate entities on the network;

the message envelope having contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of the destination entity and a mandatory attribute indicating that an explicit request for the destination entity to perform a task in the data structure must be understood and processed by the destination entity.

51. A message exchange apparatus comprising:

a processor;

a message parser executable on the processor to;

parse a message envelope of a message;

parse contents of the message envelope, the contents comprising data structures, each data structure identifies which entity is intended to process the data structure when that entity receives the message envelope over the network, wherein at least one of the data structures includes an actor attribute specifying the identity of that entity and a mandatory attribute indicating that an explicit request for that entity to perform a task in the data structure must be understood and processed by that entity.

52. A message envelope generated in accordance with the following acts:

providing a sending entity in communication with a network of entities;

generating contents of the message envelope of a message, the contents comprising;

a header data structure having an actor attribute specifying the identity of an intermediate entity and a mandatory attribute indicating that an explicit request for the intermediate entity to perform a task in the header data structure must be understood and processed by the intermediate entity; and

a body data structure which identifies a destination entity as that which is intended to process the body data structure.

53. A message envelope as recited in claim 52, wherein the data structures are expressed in a markup language.

54. A message envelope as recited in claim 52, wherein the data structures are expressed in XML.

55. A modulated data signal having computer-executable instructions embodied thereon comprising:

a header data structure having an actor attribute specifying the identity of an intermediate entity, over a network of entities, and a mandatory attribute indicating that an explicit request for the intermediate entity to perform a task in the header data structure must be understood and processed by the intermediate entity; and

a body data structure which identifies a destination entity as that which is intended to process the body data structure.

56. A modulated data signal as recited in claim 55, wherein the data structures are expressed in a markup language.

57. A modulated data signal as recited in claim 55, wherein the data structures are expressed in XML.

58. A computer-readable medium having a data structure embodied thereon comprising:

a header data-structure section having an actor attribute specifying the identity of an intermediate entity, over a network of entities, and a mandatory attribute indicating that an explicit request for the intermediate entity to perform a task in the header data-structure section must be understood and processed by the intermediate entity; and

a body data-structure section which identifies a destination entity as that which is intended to process the body data-structure section.

59. A computer-readable medium as recited in claim 58, wherein the data-structure sections are expressed in a markup language.

60. A computer-readable medium as recited in claim 58, wherein the data-structure sections are expressed in XML.

61. A method of formatting a message for exchange between entities on a network, the method comprising:

generating a message envelope of a message, the message comprising at least one explicit request by one entity on a network of another entity on the network to perform a task;

generating contents of the message envelope, the contents comprising data structures, at least one data structure having an actor attribute specifying the identity of that entity indicated in the at least one explicit request and a mandatory attribute indicating that the at least one explicit request for that entity to perform a task in the data structure must be understood and processed by that entity.

62. A method as recited in claim 61, wherein each data structure specifies whether the entity that is intended to process the data structure must understand such data structure.

63. A method as recited in claim 61, wherein each data structure specifies whether the entity that is intended to process the data structure must respond if it does not understand such data structure.

64. A method as recited in claim 61, wherein:

the message envelope has beginning and ending envelope tags;

the contents of the message envelope is between the envelope tags.

65. A method as recited in claim 61, wherein the contents include:

a header data structure;

a body data structure, the body data structure including message data.

66. A method as recited in claim 65, wherein:

the header data structure has beginning and ending header tags;

the body data structure has beginning and ending body tags.

67. A method as recited in claim 65, wherein:

the header data structure is intended for at least one intermediate entity;

the body data structure is intended for a destination entity.

68. A method as recited in claim 61 further comprising sending the message envelope to an entity on a network.

69. A method as recited in claim 61, wherein at least one of the data structures includes a request for an entity to perform a task, wherein the data structures lack executable instructions for performing the task.

70. A method as recited in claim 61, wherein the data structures are expressed in a markup language.

71. A method as recited in claim 61, wherein the data structures are expressed in XML.

72. A method as recited in claim 61 further comprising:

formatting the message envelope for sending over a network using HTTP;

sending the message envelope to an entity on the network by using HTTP.

73. A method as recited in claim 61 further comprising:

binding the message envelope into a HTTP request;

sending the message envelope to an entity on the network by using HTTP.

74. A method as recited in claim 61 further comprising:

binding the message envelope into a HTTP response;

sending the message envelope to an entity on the network by using HTTP.

75. A method as recited in claim 66, wherein the header tags identify the header data structure.

76. A method as recited in claim 66, wherein the body tags identify the body data structure.