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

• US 7,496,682 B2
• Filed: 06/26/2006
• Issued: 02/24/2009
• Est. Priority Date: 08/10/1999
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Atkinson, Robert George, Layman, Andrew J., Nielsen, Henrik F., Thatte, Satish R., Kakivaya, Gopal Krishna R.
• Primary Examiner(s): Nguyen; Quang N.
• Application Number:
  US11/426,581
• Publication Number:
  US 20060235983A1
• Time in Patent Office: 974 Days
• Field of Search: 709/238, 709/202, 709/206, 709/218, 709/224, 370/254, 370/395.31, 707/2
• 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 comprising:

exchanging a message having a data structure within a header element of the message between entities on a network, wherein the message also comprises a body data structure separate from the header element, and wherein a portion of the message is forwarded to a destination entity of the message;

the message'"'"'s data structure having;

an actor attribute specifying an identity of an intermediate entity between the entities on the network; and

a mandatory attribute indicating whether an entry in the message is mandatory or optional for the intermediate entity to process,

wherein if the entry in the message is mandatory and the intermediate entity is unable to understand and process the entry, then the intermediate entity generates and sends a fault message, and wherein the fault message indicates the Universal Resource Identifier (URI) of a fault source and whether the fault is related to processing the body data structure.

2. The method as recited in claim 1, wherein the body data structure separate from the header element is also forwarded to a destination entity of the entities on the network.

3. The method as recited in claim 1, further comprising generating the header element prior to exchanging the message.

4. The method as recited in claim 1, wherein the act of exchanging comprises transmitting the message'"'"'s data structure from an origin entity of the entities to the destination entity of the entities via the intermediate entity.

5. The method as recited in claim 1, further comprising performing a task in the data structure at the intermediate entity.

6. A method comprising:

receiving at an entity on a network a message having a data structure within a header element of the message with an actor attribute specifying the identity of the entity and a mandatory attribute indicating that an explicit request for the entity to perform a task in the message'"'"'s data structure must be performed by the entity, wherein a portion of the message is forwarded to a destination entity of the message; and

performing, at the entity, the task in the message'"'"'s data structure,

wherein if the entity does not understand the mandatory attribute of the message or if the entity encounters a problem in processing the message, then a fault message is generated by the entity to indicate the Universal Resource Identifier (URI) of a fault source and whether the fault is related to performing the task in the message'"'"'s data structure.

7. The method as recited in claim 6, further comprising transmitting the message to the destination entity responsive to performing the task.

8. The method as recited in claim 6, further comprising, responsive to performing the task, responding to an origin entity from which the message was received.

9. The method as recited in claim 8, further comprising, prior to responding to the origin entity, determining that the message'"'"'s data structure indicates that responding to the origin entity is required.

10. The method as recited in claim 6, further comprising, responsive to receiving and prior to performing:

parsing the message based on an indication of the message'"'"'s format in one or more tags of the message.

11. The method as recited in claim 6, further comprising determining that the entity is specified by the actor attribute.

12. The method as recited in claim 11, further comprising determining that the message'"'"'s data structure comprises the mandatory attribute and understanding the mandatory attribute prior to performing the task.

13. A computer-readable storage medium having computer-executable instructions that, when executed by a computer, performs a method comprising:

receiving at an entity on a network a message having a data structure within a header element of the message with an actor attribute specifying the identity of the entity and a mandatory attribute indicating whether an entry in the message is mandatory or optional for the entity to process, wherein a portion of the message is forwarded to a destination entity of the message; and

determining that the entity is specified by the actor attribute,

wherein if the entity does not understand the mandatory attribute of the message or if the entity encounters a problem in processing the message, then a fault message is generated by the entity, and wherein the fault message indicates a Universal Resource Identifier (URI) of a fault source and whether the fault is related to processing the message.

14. The computer-readable storage medium as recited in claim 13, further comprising transmitting the message to the destination entity.

15. The computer-readable storage medium as recited in claim 13, further comprising, responding to an origin entity from which the message was received.

16. The computer-readable storage medium as recited in claim 15, further comprising, prior to responding to the origin entity, determining that the message'"'"'s data structure indicates that responding to the origin entity is required.

17. The computer-readable storage medium as recited in claim 13, further comprising, responsive to receiving:

parsing the message based on an indication of the message'"'"'s format in one or more tags of the message.

18. The computer-readable storage medium as recited in claim 13, further comprising determining that the message'"'"'s data structure comprises the mandatory attribute and understanding the mandatory attribute.