Dual communication services interface for distributed transaction processing

• US 5,878,225 A
• Filed: 06/03/1996
• Issued: 03/02/1999
• Est. Priority Date: 06/03/1996
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Bilansky, Mark Alan, Stavana, Edward James, Huang, Kevin Chuang-Chi, Ryder, James William
• Primary Examiner(s): Asta, Frank J.
• Assistant Examiner(s): RINEHART, MARK H
• Application Number:
  US08/650,121
• Time in Patent Office: 1,002 Days
• Field of Search: 395/200.57, 395/200.58, 395/200.6, 395/200.79, 370/465, 370/469
• US Class Current: 709/227
• CPC Class Codes: H04L 67/00 Network arrangements or protocols for supporting network services or applications user-to-user messaging H04L51/00; network arrangements, protocols or services for supporting real-time applications in data packet communications networks H04L65/00
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/14 Multichannel or multilink protocols
• CPC Class Codes: H04L 69/26 Special purpose or proprietary protocols or architectures network applications for proprietary or special purpose networking environments H04L67/12
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/322 Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A system and method is provided for communicating data and control information between two systems, each system including a communication protocol stack, such as an advanced program to program communication (APPC) protocol stack which includes an I/O interface layer with modules for OPEN, GET, PUT, UPDATE, RELEASE, DELETE, CLOSE, and an OPC interface to a serial optical bus. Dual control and data paths are established from, for example, a client system to a single agent on a target system, the control path including a protocol stack and a data path avoiding at least one layer of the protocol stack. Packets of control information for a given process are transferred on the control path, and packets of data information are transferred on the data path. Communications are sychronized so that the client and target systems send and receive communications packets on the same one of the two paths.

Claims

1. In a client/server communications system in which each system includes a strictly layered protocol stack comprising a plurality of layers for establishing communications and transferring data with respect to the other for a given process, a protected conversation method comprising the steps of:

establishing dual control and data paths from the client system to a single agent on the server system, the control path including said protocol stack and a data path including a subset of the layers of said protocol stack, said subset bypassing at least one layer of said protocol stack;

transferring packets of control information for a given process on said control path;

transferring packets of data information on said data path; and

synchronizing communications so that said client and server systems send and receive communications packets on the same one of the two paths.

2. A method for communicating data and control between a plurality of systems, each system including a communication protocol stack having at least three architected protocol layers, including an application layer above a machine interface and an interface layer to a physical layer below said machine interface,

responsive to a request from an application program in a client system to establish a protected conversation with a server system,

determining if a communication path already exists between said client and server systems for said conversation;

and if not

establishing a dual communication path and bus path to a single agent on said server system, said communication path traversing said communication protocol stack and said bus path traversing a subset excluding at least one of the layers of said protocol stack;

transferring packets of control information for this conversation on said communication path;

transferring packets of data information for this conversation on said bus path; and

synchronizing the communications on said paths so that said systems send and receive communications packets on the same one of the two paths.

3. A method for executing a protected conversation between a client system and a server system, each system including an architected protocol stack for managing communications between said systems, comprising the steps of

establishing a communications path traversing all layers of said protocol stack from said client system to an agent on said server system;

attaching a bus path to said communications path to said agent, said bus path traversing a subset of the layers of said protocol stack, said subset bypassing at least one layer of said protocol stack;

putting said agent to sleep on said bus path;

receiving at said server system on said bus path a data message including a data command, or a check other path command;

responsive to said data command, operating said server system to execute said data command;

responsive to said check other path command, putting said agent to sleep on said communication path;

responsive to a control command on said communication path, operating said server system to execute said control command and wait on receipt of a first crossing flag on said communication path; and

responsive to said first crossing flag, operating said server system to return control to said bus path.

4. The method of claim 3 wherein said communications path traverses a plurality of architected protocol layers in each of said client and said target systems, and wherein said data path traverses at least one less architected protocol layer.

5. The method of claim 4 wherein said communications path and said data path both traverse the same physical link between said client and server systems.

6. The method of claim 5 wherein said physical link is a serial optical channel.

7. A memory device for storing electrical signals operable to control a digital computer to execute a protected conversation between a client system and a target system, each system including an architected protocol stack for managing communications between said systems, said protected conversation comprising the steps of

establishing a communications path traversing all layers of said protocol stack from said client system to an agent on said server system;

attaching a bus path to said communications path to said agent, said bus path traversing a subset of the layers of said protocol stack, said subset bypassing at least one layer of said protocol stack;

putting said agent to sleep on said bus path;

receiving at said target system on said bus path a data message including a data command, or a check other path command;

responsive to said data command, operating said target system to execute said data command;

responsive to said check other path command, putting said agent to sleep on said communication path;

responsive to a control command on said communication path, operating said target system to execute said control command and wait on receipt of a first crossing flag on said communication path; and

responsive to said first crossing flag, operating said target system to return control to said bus path.

8. Apparatus for executing a protected conversation between a client system and a target system, each system including an architected protocol stack for managing communications between said systems, comprising:

means for establishing a communications path traversing all layers of said protocol stack from said client system to an agent on said server system;

means for attaching a bus path to said communications path to said agent, said bus path traversing a subset of the layers of said protocol stack, said subset bypassing at least one layer of said protocol stack;

means for putting said agent to sleep on said bus path;

means at said target system for receiving on said bus path a data message including a data command, or a check other path command;

means responsive to said data command, for operating said target system to execute said data command;

means responsive to said check other path command, for putting said agent to sleep on said communication path;

means responsive to a control command on said communication path, for operating said target system to execute said control command and wait on receipt of a first crossing flag on said communication path; and

means responsive to said first crossing flag, for operating said target system to return control to said bus path.

9. A client system for executing a protected conversation between said client system and a target system, said client system including a protocol stack having a plurality of layers including an application layer, a physical layer, and at least one intermediate layer for managing communications between said systems, comprising:

a communications path traversing said protocol stack from said application layer to said physical layer;

a bus path attached to said communications path, said bus path bypassing at least one intermediate layer; and

a device driver for transferring data packets with respect to said bus path and control packets with respect to said communications path selectively to and from said physical layer for communication with said target system.

10. The client system of claim 9, further comprising:

an initialization module responsive to a request for a protected conversation with said target system for coordinating the initialization of said communications path and said bus path.

11. The client system of claim 10, further comprising:

a first crossing after commit flag set on to assure transmission over the communications path of a first packet of data following a commit flow;

a check other path flag for controlling synchronization of said target system to the same path as said client system.

12. A target system for executing a protected conversation between said target system and a client system, said target system including a protocol stack having a plurality of layers including an application layer, a physical layer, and at least one intermediate layer for managing communications between said systems, comprising:

a communications path traversing said protocol stack from said application layer to said physical layer;

a bus path attached to said communications path, said bus path bypassing at least one intermediate layer; and

a device driver for transferring data packets with respect to said bus path and control packets with respect to said communications path selectively to and from said physical layer for communication with said client system.

13. The target system of claim 12, further comprising:

an agent responsive to a check other path flag and a first crossing after commit flag received from said client system for synchronizing communications with said client system to one of said communications path or said bus path.

14. The target system of claim 13, further comprising:

means for putting said agent to sleep on said bus path;

means at said target system for receiving on said bus path a data message including a data command, or a check other path command;

means responsive to said data command, for operating said target system to execute said data command;

means responsive to said check other path command, for putting said agent to sleep on said communication path;

means responsive to a control command on said communication path, for operating said target system to execute said control command and wait on receipt of a first crossing flag on said communication path; and

means responsive to said first crossing flag, for operating said target system to return control to said bus path.