Input/output network for computer system

• US 4,941,089 A
• Filed: 12/12/1986
• Issued: 07/10/1990
• Est. Priority Date: 12/12/1986
• Status: Expired due to Fees

• Current Assignee: Datapoint Corp. (Dynacore Holdings Corporation)
• Original Assignee: Datapoint Corp. (Dynacore Holdings Corporation)
• Inventors: Fischer, Michael A.
• Primary Examiner(s): CLARK, DAVID
• Application Number:
  US06/941,084
• Time in Patent Office: 1,306 Days
• Field of Search: 371/32, 371/33, 340/825.06, 340/825.07, 340/825.08, 340/825.5, 340/825.54, 370/60, 370/13-17, 370/85, 370/94, 370/946, 370/85.1, 370/85.9, 370/85.13, 370/94.1, 370/94.2, 370/99, 370/85.4
• US Class Current: 709/231
• CPC Class Codes: G06F 13/128 for dedicated transfers to a network for protocol converters G06F13/387
• CPC Class Codes: H04L 69/00 Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass networks security protocols H04L9/40; wireless communication networks H04W

Abstract

An I/O network channel achieves relatively high rates of data communication between a plurality of widely physically dispersed devices interconnected by a LAN-type media. A processor connected to each node of the media controls the data and functions of a receiver and transmitter at each node to establish network level, transport level and session level data communication and control functions.

Claims

1. In a local area network (LAN) comprising a communication medium commonly connecting a plurality of Nodes, LAN interface means at each Node for controlling access to the medium and communicating LAN packets between predetermined selected source and destination Nodes, each LAN data packet including a LAN data field and a LAN header field containing characters which control the interface means to achieve Node to Node communications in accordance with a predetermined LAN communication protocol;

and in combination therewith,

a character I/O channel for communicating byte stream data and control administrative information in single IONET network level data packet messages from source to destination Devices connected at the Nodes, each Device including a device interface which connects to a device which is separate from the Device, the device being one of either an I/O device which conducts I/O data transfers or a computer device including a memory and a processor means and a program code for operating the computer device, said character I/O channel comprising;

point of use (POU) means included in the Device and connected to the LAN interface means at each Node, the POU means connected to each I/O device including a microcomputer means including a memory and a program code for operating the microcomputer means;

the program codes for the processor means and the microcomputer means defining a predetermined IONET communication protocol for communicating with Devices and their connected device interfaces and devices, the IONET communication protocol being separate from the LAN communication protocol;

the POU means inserting characters in the data field of LAN data packets to form the IONET network level data packet messages which have an IONET header field and an administrative field and byte stream data field, the IONET header characters including a function code specifying one of a plurality of control functions, the administrative field characters including an administrative information code for use in accomplishing the specified control function to be performed by one of the Device or its device interface, the byte stream data characters originating from a device at the source Node; and

the POU means of the destination Node directly interpreting the function code and the administrative information code characters (a) to establish a session between the source and destination Devices for communicating IONET data packet messages therebetween without acceptance of and interference from other IONET data packet messages for the duration of the session, and (b) to perform a corresponding control function on one of the destination Device or its device interface during the session, while (c) simultaneously transferring the byte stream data characters in unmodified form directly to the device connected to the device interface of the destination Device.

2. An invention as defined in claim 1 wherein one control function is a disconnect control function which terminates an established session.

3. An invention as defined in claim 1 wherein the IONET header characters include a length code specifying an arbitrary length for each of the administrative and byte stream data fields.

4. An invention as defined in claim 1 wherein the IONET header characters include an immediate code, and the POU means of the destination Device immediately performs the control function specified by the function code and the administrative information code upon receipt of the IONET message containing the immediate code.

5. An invention as defined in claim 1 wherein the LAN interface means inserts source Node identifying information in each LAN data packet, and wherein:

the microcomputer means of one POU means prohibits the responsive communication of IONET messages to a Device connected at a Node which has identifying information which does not correspond to the Node identifying information of the Devices with which the session is established.

6. An invention as defined in claim 1 wherein the LAN interface means inserts source Node identifying information in each LAN data packet, and wherein:

the microcomputer means of one POU means includes password information identifying the source Node of each Device capable of initiating a session with the Device of the one POU means, and the microcomputer means of the one POU means prohibits the communication of IONET messages unless the source information associated with the received IONET message during one half session corresponds to the source Node identifying information of the Device which supplied the password information to initiate the session.

7. An invention as defined in claim 6 wherein the microcomputer means of the one POU means further includes lock means for preventing the password information from being changed by IONET messages received from other Devices.

8. An invention as defined in claim 1 wherein an IONET message specifying a command function is followed by the communication of a reply IONET message which contains function code and an administrative information code specifying whether the requested command function has been successfully performed.

9. An invention as defined in claim 8 wherein each session is established by the communication of a first IONET message which contains a function code and an administrative information code specifying a connect control function between two Devices and by the responsive communication of a reply IONET message which contains a function code and an administrative information code specifying whether the session has been successfully established.

10. An invention as defined in claim 9 wherein each session consists of two half sessions, the first IONET message establishing one half session, and the reply IONET message establishing the other half session.

11. An invention as defined in claim 10 wherein the function code and the administrative information code of the reply IONET message are directly interpreted by one of the microcomputer means or the computer device of one Device of the established session to prohibit the communication of further IONET messages to the other Device of the established session until further IONET messages can be received in memory of the POU means of the other Device.

12. An invention as defined in claim 10 wherein:

an IONET data packet message containing multiple data packets which is communicated in one half session includes IONET header characters which specify sequential ordering information of the multiple data packets; and

each other half session reply IONET message includes IONET header characters which specify acknowledgement information by which to determine those ones of data packets which were not successfully received.

13. An invention as defined in claim 12 wherein all data packets which were not successfully received are retransmitted in response to the reply IONET message containing the acknowledgement information.

14. An invention as defined in claim 12 wherein all data packets which were not successfully received are retransmitted in response to the expiration of a predetermined time period during which no reply IONET message was received.

15. An invention as defined in claim 13 wherein the reply IONET message contains characters in its IONET header which specify replies including:

successful completion of the control function;

non-support of the control function by the destination Device;

rejection by the destination Device of the control function due to the state of a receiver means at the destination Device;

rejection of the control function because the destination Device is not in session;

rejection of the control function because the destination Device is in session with another Device;

rejection of the control function because a configuration lock associated with the destination Device is set; and

rejection of the control function because there is an error in the control command character information in the control command IONET message.

16. An invention as defined in claim 8 herein the control commands specify control functions including:

report device parameters, which causes the generation of a control reply IONET message containing information relating to the type and predetermined attributes of the device connected to the Device;

report statistics, which causes the generation of a control reply IONET message containing statistics relating to medium communication;

report interface parameters, which causes the generation of a control reply IONET message relating to the interface control and related modal state of the Device;

set device parameters, which causes the one Device to store new parameter information regarding the other Device of the session; and

set interface parameters, which causes the destination Device to set new values for interface control and the related modal state.

17. An invention as defined in claim 8 wherein the control functions include:

flush buffers, which causes all previous information communicated in IONET messages to the memory of the recipient Device to be discarded;

run extended diagnostics, which causes the Device to perform diagnostic functions and report on the results of those functions; and

report status, which causes the Device to generate a control reply IONET message describing the status of an device interface of the device.

18. An invention as defined in claim 8 wherein the reply IONET messages include information specifying:

the state of the device interface input signals and an indication of generic power on/off and generic ready/not-ready status;

selection of those input status changes which result in communicating control reply IONET messages containing status information; and

specification of settings of device interface output control signals.

19. An invention as defined in claim 1 wherein the control commands for the device interface include:

a command to transfer the data packet message;

a command to stop receiving data packet messages; and

a command for communicating keep alive messages to maintain the session in the absence of communicated data packet messages.

20. For use with a local area network (LAN) comprising a communication medium commonly connecting a plurality of Nodes, LAN interface means at each Node for controlling access to the medium and communicating LAN packets between predetermined selected source and destination Nodes, each LAN data packet including a LAN data field and a LAN header field containing characters which control the interface means to achieve Node to Node communications in accordance with a predetermined LAN communication protocol;

a method for communicating byte stream data and control administrative information in single IONET network level data packet messages from source to destination Devices connected at the Nodes by communicating LAN data packets between source and destination odes in accordance with the LAN communication protocol, each Device including a device interface which connects to a device which is separate from the Device, the device being one of either an I/O device which conducts I/O data transfers or a computer device including a memory and a processor means and a program code for operating the computer device, said method being useful for communicating characters as an I/O channel and comprising;

including a point of use (POU) means in the Device and connecting the POU means to the LAN interface means at each Node;

including a microcomputer means including a memory and a program code for operating the microcomputer means in each POU means;

implementing an IONET communication protocol separately from the LAN communication protocol in the program codes of each computer device and microcomputer means, and thereby;

forming the IONET network level data packet messages in accordance with the IONET communication protocol by inserting characters in the LAN data field of each LAN data packet communicated between the Nodes;

forming an IONET header field and an administrative field and a byte stream data field in each IONET data packet message by the inserted characters, the IONET header characters including a function code specifying one of a plurality of control functions, the administrative field characters including an administrative information code for use in accomplishing the specified control function to be performed by the one of Device or its device interface, the byte stream data characters originating from a device at the source Node; and

directly interpreting the function code and administrative information code characters at the destination Node in accordance with the IONET communication protocol, and thereby (a) establishing a session between the source and destination Devices for communicating IONET data packet messages therebetween without acceptance of and interference from other IONET data packet messages for the duration of the session, and (b) performing a corresponding control function on one of the destination Device or its device interface during the session, while (c) simultaneously transferring the byte stream data characters in unmodified form directly to the device connected to the device interface of the destination Device.

21. A method as defined in claim 20 further comprising:

establishing a session to communicate byte stream data in IONET messages, each session consisting of two half sessions;

communicating a first IONET message from a first Device to a second Device in one half session; and

communicating a reply IONET message from the second Device to the first device in the other half session.

22. A method as defined in claim 21 further comprising:

communicating status information regarding the present and previous half sessions with each reply IONET message.

23. A method as defined in claim 21 further comprising:

communicating an IONET message to maintain the continuance of an established session when byte stream data is unavailable to communicate by IONET data packet messages.

24. A method as defined in claim 21 further comprising:

interpreting the function code and administrative information code and performing a corresponding control function on one of the Device or device interface while the session is established; and

communicating a reply IONET message to indicate whether the control function was successfully accomplished.

25. A method as defined in claim 21 further comprising:

including ordering information in an IONET data packet message of one half session which specifies the sequential order of multiple data packets; and

acknowledging in a replay IONET message in the other half session those ones of the data packets which have been unsuccessfully received.

26. A method as defined in claim 25 further comprising:

retransmitting those ones of the data packets which have been acknowledged as unsuccessfully received.

27. A method as defined in claim 21 further comprising:

retransmitting IONET data packet messages which have been previously transmitted after the expiration of a predetermined time period after which a reply IONET message acknowledging the successful receipt of those messages has not been received.

28. A method as defined in claim 20 further comprising:

establishing a session between only those Devices which are preselected to allow communication of IONET messages therebetween.

29. A method as defined in claim 20 further comprising:

dividing the administrative and byte stream data fields of each IONET message into arbitrary lengths, either of which may contain no information; and

specifying the length of each of the administrative and byte stream data fields by inserting characters in the IONET header field which form a length code.

30. A method as defined in claim 20 further comprising:

communicating multiple IONET data packet messages; and

limiting the number of IONET data packet messages communicated in a group to a number which is at least one less than the number of IONET data packet messages which can be received in the memory of a destination Device without inhibiting a receiver means of a destination Node.