Self-described stream in a communication services patterns environment

• US 6,477,580 B1
• Filed: 08/31/1999
• Issued: 11/05/2002
• Est. Priority Date: 08/31/1999
• Status: Expired due to Term

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture LLP (Accenture PLC)
• Inventors: Bowman-Amuah, Michel K.
• Primary Examiner(s): Dinh, Dung C.
• Assistant Examiner(s): Kupstas, Tod
• Application Number:
  US09/387,070
• Time in Patent Office: 1,162 Days
• Field of Search: 709/200, 709/236, 709/231, 709/219, 340/82, 237/230
• US Class Current: 709/231
• CPC Class Codes: G06F 9/54 Interprogram communication

Abstract

A system, method, and article of manufacture are described for providing a self-describing stream-based communication system. Messages are sent which include data between a sending system and a receiving system. Meta-data is attached to the messages being sent between the sending system and the receiving system. The data of the messages sent from the sending system to the receiving system is translated based on the meta-data. The meta-data includes first and second sections. The first section identifies a type of object associated with the data and a number of attribute descriptors in the data. The second section includes a series of the attribute descriptors defining elements of the data.

Claims

1. A method for providing a self-describing stream-based communication system comprising the steps of:

(a) loading messages including meta-data and representations of objects onto a data stream;

(b) sending messages between a sending system and a receiving system using a shared generic format;

(c) unloading the messages via the receiving system, wherein the messages are representative of object data;

(d) translating the messages into object data via the receiving system based on the meta-data;

(e) wherein the meta-data includes a first section identifying a type of object associated with the data and a number of attribute descriptors in the data and a second section including a series of the attribute descriptors defining elements of the data; and

(f) instantiating a new instance of the objects, and populating said objects with the object data that has been translated by the receiving system.

2. A method as recited in claim 1, wherein the sending system and receiving system are each equipped with logic for interpreting the meta-data of the messages.

3. A method as recited in claim 1, wherein one of the systems is an object-based system and one of the systems is a non-object-based system.

4. A method as recited in claim 1, wherein both of the systems are object-based systems.

5. A method as recited in claim 1, wherein both of the systems are non-object-based systems.

6. A method as recited in claim 1, wherein the elements are defined in terms of size, type, and name.

7. The method of claim 1 further comprising storing the meta-data in a relational database by the receiving system.

8. The method of claim 7 further comprising querying the relational database after receiving a message to determine if the meta-data has already been translated and stored, such that if the meta-data is stored in the database, the meta-data does not have to be re-translated from the message.

9. A computer program embodied on a computer readable medium for providing a self-describing stream-based communication system comprising:

(a) a code segment that loads messages including meta-data and representations of objects onto a data stream;

(b) a code segment that sends messages between a sending system and a receiving system using a shared generic format;

(c) a code segment that unloads the messages via the receiving system, wherein the messages are representative of object data;

(d) a code segment that translates the messages into object data via the receiving system based on the meta-data, wherein the meta-data includes a first section identifying a type of object associated with the data and a number of attribute descriptors in the data and a second section including a series of the attribute descriptors defining elements of the data; and

(e) a code segment that instantiates a new instance of the objects, and populates said objects with the object data that has been translated by the receiving system.

10. A computer program as recited in claim 9, wherein the sending system and receiving system are each equipped with logic for interpreting the meta-data of the messages.

11. A computer program as recited in claim 9, wherein one of the systems is an object-based system and one of the systems is a non-object-based system.

12. A computer program as recited in claim 9, wherein both of the systems are object-based systems.

13. A computer program as recited in claim 9, wherein both of the systems are non-object-based systems.

14. A computer program as recited in claim 9, wherein the elements are defined in terms of size, type, and name.

15. A system for providing a self-describing stream-based communication system comprising:

(a) logic that loads messages including meta-data and representations of objects onto a data stream;

(b) logic that sends messages between a sending system and a receiving system using a shared generic format;

(c) logic that unloads the messages via the receiving system, wherein the messages are representative of object data;

(d) logic that translates the messages into object data via the receiving system based on the meta-data, wherein the meta-data includes a first section identifying a type of object associated with the data and a number of attribute descriptors in the data and second including a series of the attribute descriptors defining elements of the data; and

(e) logic that instantiates a new instance of the objects, and populates said objects with the object data that has been translated by the receiving system.

16. A system as recited in claim 15, wherein the sending system and receiving system are each equipped with logic for interpreting the meta-data of the messages.

17. A system as recited in claim 15, wherein one of the systems is an object-based system and one of the systems is a non-object-based system.

18. A system as recited in claim 15, wherein both of the systems are object-based systems.

19. A system as recited in claim 15, wherein both of the systems are non-object-based systems.

20. A system as recited in claim 15, wherein the elements are defined in terms of size, type, and name.