Network terminal server with full API implementation

• US 6,047,319 A
• Filed: 07/17/1996
• Issued: 04/04/2000
• Est. Priority Date: 03/15/1994
• Status: Expired due to Term

• Current Assignee: Digi International Inc.
• Original Assignee: Digi International Inc.
• Inventors: Olson, Gene H.
• Primary Examiner(s): Myers, Paul R.
• Application Number:
  US08/682,407
• Time in Patent Office: 1,357 Days
• Field of Search: 395/682, 395/681, 395/712, 395/800, 395/200.52-200.55, 395/651, 709/220-229, 713/1-100, 710/72
• US Class Current: 709/223
• CPC Class Codes: H04L 67/08 specially adapted for terminal emulation, e.g. Telnet
• 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
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A terminal server for providing communication between a host computer and a synchronous, asychronous or parallel communications port across a general purpose network is provided utilizing a unique device driver interface and multiplexing communication protocol. The server communicates data and control commands for multiple ports on a single connection, thereby reducing demands on the network. In addition, genuine TTY devices are made available across the general purpose network which have all the characteristics of local communication ports. The present invention also makes possible access to the ports on the server to multiple host computers located on the network, allowing fair access to shared resources such as modems and printers. Finally, the invention can also be implemented in hardware, further increasing compatibility with existing host computer software and further reducing host computer overhead.

Claims

1. A system comprising:

a server having a plurality of communication ports; and

a host computer having a driver communicatively coupling the host computer to the server via a network connection, wherein the driver emulates the communication ports of the server by defining a corresponding local communication port for each of the communication ports of the server, and further wherein the driver includes an application programming interface (API) by which an application program executing on the host computer is granted full control of one of the communication ports of the server, including hardware and software flow control, as if the communication ports of the server were local to the host computer.

2. The system as claimed in claim 1, wherein the driver maintains a single network connection from the host computer to the server as the application program requests additional local communication ports from the driver.

3. The system of claim 1, wherein the driver defines a TTY device as the local communication port.

4. The system of claim 1, wherein the driver receives input/output (I/O) settings from the application program via the application programming interface, and further wherein the driver communicates the I/O settings to the server for configuring hardware characteristics of the granted server communication port.

5. The system of claim 1 wherein the server communication ports are serial ports.

6. The system of claim 1, wherein the network connection is a TCP connection.

7. The system of claim 1, further comprising a UNIX daemon executing on the host computer for establishing the network connection as a reliable bi-directional bytestream connection over a network, opening a control device associated with the driver, and utilizing a STREAMS interface to link the reliable bytestream network connection to the driver.

8. A hardware device for a host computer, wherein the hardware device includes a driver that emulates a plurality of communication ports of a remote server that is communicatively coupled to the host computer via a network connection, wherein the driver defines a corresponding local communication port for each communication port of the server and includes an application programming interface (API) by which an application program executing on the host computer is granted full control of one of the communication ports of the server, including hardware and software flow control, as if the communication ports of the server were local to the host computer.

9. The hardware device of claim 8, wherein the driver receives requests to control one of the local communication ports from application programs executing on the host computer via a standard application programming interface (API).

10. The hardware device of claim 9, wherein the driver communicates the requests to the terminal server such that the terminal server grants to the host computer exclusive access to one of the communication ports of the terminal server.

11. The hardware device of claim 10, wherein the terminal server grants exclusive access to the server communication port that corresponds to the requested local communication port.

12. The hardware device as claimed in claim 8, wherein the driver maintains a single network connection from the host computer to the server as the application program requests additional local communication ports.

13. The hardware device of claim 8, wherein the driver defines a TTY device as the local communication port.

14. The hardware device of claim 9, wherein the driver receives input/output (I/O) settings from the application program via the application programming interface, and further wherein the driver communicates the I/O settings to the terminal server for configuring hardware characteristics of the terminal server communication port.

15. The hardware device of claim 8, wherein the terminal server communication ports are serial ports.

16. The hardware device of claim 8, wherein the network connection is a TCP connection.

17. The hardware device of claim 8, further comprising a UNIX daemon executing on the host computer for establishing the network connection as a reliable bi-directional bytestream connection over a network, opening a control device associated with the driver, and utilizing a STREAMS interface to link the reliable bytestream network connection to the driver.