Stream-based communication in a communication services patterns environment

• US 6,606,660 B1
• Filed: 08/31/1999
• Issued: 08/12/2003
• 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): Burgess, Glenton B.
• Assistant Examiner(s): KUPSTAS, TOD A
• Application Number:
  US09/386,717
• Time in Patent Office: 1,442 Days
• Field of Search: 709/227, 709/228, 709/230, 709/231, 709/232
• US Class Current: 709/227
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/762 at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 65/764 at the destination reformatting of additional data in video clients H04N21/4355
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

A system, method, and article of manufacture are disclosed for providing a stream-based communication system. A shared format is defined on interface code for a sending system and a receiving system. A message to be sent from the sending system to the receiving system is translated based on the shared format. Once translated, the message is then sent from the sending system and received by the receiving system. Once the message is received by the receiving system, the message is then translated based on the shared format.

Claims

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

defining on a central system a shared fixed format on interface code for a sending system and a receiving system;

downloading the shared fixed format from the central system to the sending system and the receiving system;

translating a message to be sent from the sending system to the receiving system based on the shared fixed format;

sending the message from the sending system using a stream-based protocol;

receiving the message by the receiving system; and

translating the message received by the receiving system based on the shared fixed format;

wherein where the shared fixed format maps the fixed location and fixed size of each attribute in the message; and

wherein the shared fixed format is stored on both the sending system and receiving system subsequent to being downloaded from the central system.

2. 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.

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

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

5. A method as recited in claim 1, and further comprising the step of storing information in the translated message received by the receiving system in a relational database.

6. A method as recited in claim 1, wherein the shared format is based on an order of attributes in the message.

7. A computer program embodied on a computer readable medium for providing a stream-based communication system comprising the steps of:

a code segment that defines on a central system a shared fixed format on interface code for a sending system and a receiving system;

a code segment that downloads the shared fixed format from the central system to the sending system and the receiving system;

a code segment that translates a message to be sent from the sending system to the receiving system based on the shared fixed format;

a code segment that sends the message from the sending system using a stream-based protocol;

a code segment that receives the message by the receiving system; and

a code segment that translates the message received by the receiving system based on the shared fixed format;

wherein where the shared fixed format maps the fixed location and fixed size of each attribute in the message; and

wherein the shared fixed format is stored on both the sending system and receiving system subsequent to being downloaded from the central system.

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

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

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

11. A computer program as recited in claim 7, and further comprising a code segment that stores information in the translated message received by the receiving system in a relational database.

12. A computer program as recited in claim 7, wherein the shared format is based on an order of attributes in the message.

13. A system for providing a stream-based communication system comprising the steps of:

logic that defines on a central system a shared fixed format on interface code for a sending system and a receiving system;

logic that downloads the shared fixed format from the central system to the sending system and the receiving system;

logic that translates a message to be sent from the sending system to the receiving system based on the shared fixed format;

logic that sends the message from the sending system using a stream-based protocol;

logic that receives the message by the receiving system; and

logic that translates the message received by the receiving system based on the shared fixed format;

wherein where the shared fixed format maps the fixed location and fixed size of each attribute in the message; and

wherein the shared fixed format is stored on both the sending system and receiving system subsequent to being downloaded from the central system.

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

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

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

17. A system as recited in claim 13, and further comprising logic that stores information in the translated message received by the receiving system in a relational database.

18. A system as recited in claim 13, wherein the shared format is based on an order of attributes in the message.