Fixed format stream in a communication services patterns environment

• US 6,549,949 B1
• Filed: 08/31/1999
• Issued: 04/15/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): Dinh, Dung C.
• Application Number:
  US09/386,430
• Time in Patent Office: 1,323 Days
• Field of Search: 709/230, 709/246, 709/314, 709/231, 709/236
• US Class Current: 709/236
• CPC Class Codes: H04L 69/06 Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
• 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 provide a fixed format stream-based communication system. A sending fixed format contract on interface code is defined for a sending system. A receiving fixed format contract on interface code is also defined for a receiving system. A message to be sent from the sending system to the receiving system is translated based on the sending fixed format contract. The message is then sent from the sending system and subsequently received by the receiving system. The message received by the receiving system is then translated based on the receiving fixed format contract.

Claims

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

(a) defining a sending fixed format contract on interface code for a sending system and a receiving fixed format contract on interface code for a receiving system;

(b) translating a message to be sent from the sending system to the receiving system based on the sending fixed format contract;

(c) sending the message from the sending system;

(d) receiving the message by the receiving system; and

(e) translating the message received by the receiving system based on the receiving fixed format contract.

2. A method as recited in claim 1, wherein the fixed format contracts are included in meta-data of the message.

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, and further comprising the step of storing information in the translated message received by the receiving system in a relational database.

7. A method as recited in claim 1, wherein the message includes an indication of a version thereof.

8. A computer program embodied on a computer readable medium for providing a fixed format stream-based communication system comprising:

(a) a code segment that defines a sending fixed format contract on interface code for a sending system and a receiving fixed format contract on interface code for a receiving system;

(b) a code segment that translates a message to be sent from the sending system to the receiving system based on the sending fixed format contract;

(c) a code segment that sends the message from the sending system;

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

(e) a code segment that translates the message received by the receiving system based on the receiving fixed format contract.

9. A computer program as recited in claim 8, wherein the fixed format contracts are included in meta-data of the message.

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

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

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

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

14. A computer program as recited in claim 8, wherein the message includes an indication of a version thereof.

15. A system for providing a fixed format stream-based communication system comprising:

(a) logic that defines a sending fixed format contract on interface code for a sending system and a receiving fixed format contract on interface code for a receiving system;

(b) logic that translates a message to be sent from the sending system to the receiving system based on the sending fixed format contract;

(c) logic that sends the message from the sending system;

(d) logic that receives the message by the receiving system; and

(e) logic that translates the message received by the receiving system based on the receiving fixed format contract.

16. A system as recited in claim 15, wherein the fixed format contracts are included in meta-data of the message.

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, and further comprising logic that stores information in the translated message received by the receiving system in a relational database.