Electrical computers and digital processing systems: multicomput – Computer-to-computer protocol implementing
Reexamination Certificate
1997-09-18
2001-05-29
Harrell, Robert B. (Department: 2152)
Electrical computers and digital processing systems: multicomput
Computer-to-computer protocol implementing
C709S225000, C709S230000, C709S250000, C340S870030, C370S475000, C710S003000, C710S009000
Reexamination Certificate
active
06240456
ABSTRACT:
FIELD OF THE INVENTION
This invention relates generally to computer networks and, more particularly, relates to an implementation of a computer network which allows a network client to perform various system administrative tasks and/or request a network server to perform a job.
BACKGROUND OF THE INVENTION
As defined in Helen Custer, INSIDE WINDOWS NT (Microsoft Press, 1993), pp. 285-326, which book is incorporated herein by reference in its entirety, a computer network is an interconnected collection of autonomous computers in which each computer is physically separate and runs its own operating system. The role of network software is to take a job request, usually an I/O request, from an application running on a network client, pass it to a network server, execute the request on the network server, and return the results to the network client. During these operations it will be appreciated that the network software is required to transform the request several times. For example, a high-level request such as “read x number of bytes from file y on an I/O device associated with network server z” requires the network software to determine how to get to network server z and what communication protocol network server z understands. Then the request must be altered for transmission across the network communications link and, when the request reaches network server z, it must be checked for completeness and compatibility, decoded, and sent to the correct operating system component to execute the request. Finally, the reply must be coded for sending back across the network communications link to the network client.
By way of example, the Windows NT brand operating system allows user-mode software running on a network client to request the performance of a job on a remote, compatible network server. Specifically, when the user-mode software, such as an I/O application programming interface (API), issues a remote I/O request by calling native I/O services, some initial processing is performed, the I/O manager creates an I/O request packet (IRP) and passes the request to one of its registered file system drivers, e.g. a redirector associated with a transport driver. The redirector and transport driver provide the facilities necessary for a client computer utilizing the Windows NT brand operating system to gain access via the network communications link to files, named pipes, printers, etc. associated with the compatible network server. Similarly, when a request arrives at a network server utilizing the Windows NT brand operating system from a remote, compatible network client, it is received by a server, similarly processed, and forwarded on to the appropriate job server which performs the requested job.
Unfortunately, in a distributed computer network where there are a variety of computers running a variety of operating systems each having a different set of APIs, protocols, device naming conventions, etc., incompatibilities abound. Accordingly, the various redirector, server, and transport drivers associated with the network client and server must be continually updated, i.e. loaded and unloaded, in order to establish a computer network model into which the various components may fit. Ensuring this required compatibility makes it difficult and costly to write network software especially when multiple different products from multiple different vendors are desired to work together.
In particular, with respect to network software for use in requesting printing jobs, when a network client wants to send a print job to a remote printer server, it has to use the printing APIs of a particular computer network protocol that the printer server supports. Since different operating systems often use different computer network protocols and different naming conventions, a print job request issued by a network client utilizing a first operating system cannot be forwarded to a printer server associated with a network server utilizing a different operating system unless the network client has installed thereon software which functions to overcome the noted incompatibilities. Likewise, printer administration tools will only work in connection with the one operating system they were designed for thereby requiring vendors to write specialized, standalone software applications which may be used to allow administrators to manage the printers/printer servers over the computer network. Furthermore, these specialized software applications have to be installed on every network client which the system administrator may desire to use to perform system administration.
From the foregoing, it is evident that a need exists for an improved computer network which generally allows network software to be easily written for network clients and network servers utilizing different operating systems. A related need also exists for such a computer network which eliminates the need to install any specialized administration tools on the client side of the computer network. For example, it would be desirous to provide a computer network which allows network software to be platform independent and, similarly, which allows vendors to write server side administration tools which can be managed from any network client without regard to operating system incompatibilities.
SUMMARY OF THE INVENTION
According to these needs, the invention is directed to an implementation of a computer network which generally provides the ability for a network client to submit data to a network server for performing a job at a logical endpoint associated with the network server. By way of example only, the data may pertain to a print job or a file, the job may be a printing operation or a file save operation, and the logical endpoint may be a printer or a disk drive, respectively. The logical endpoint is assigned a Uniform Resource Locator (URL) address which allows the data to be routed thereto.
Specifically, when the network client receives a request to perform a job, the network client performs a check on the address of the logical endpoint and, if the address is a URL address, the client will place the data necessary to perform the job into a Hypertext Transfer Protocol (HTTP) formatted message. The HTTP formatted message may then be submitted to the network server via a network communications link such as the Internet. Once the network server receives the HTTP formatted message, it uses the URL address to route the message to a server process associated with the logical endpoint. The server process parses the HTTP formatted message to extract the data and submits the data to the logical endpoint which then performs the requested job.
A further feature of the invention provides a means for allowing the network client to perform system administration utilizing an ordinary network browser application. In particular, the network server is provided with the ability to dynamically generate Hypertext Markup Language (HTML) pages in response to requests by the network client. These HTML pages will allow the user to view information about the network server and/or allow for the performance of various administrative tasks. The HTML pages may be customized by vendors to present unique information to the user or be associated with vendor supplied software components, such as a Dynamic-Link Library (DLL), which provides a means for communicating with a device having a proprietary protocol.
REFERENCES:
patent: 5537626 (1996-07-01), Kraslavsky et al.
patent: 5572643 (1996-11-01), Judson
patent: 5625781 (1997-04-01), Cline
patent: 5687320 (1997-11-01), Wiley et al.
patent: 5708780 (1998-01-01), Levergood et al.
patent: 5715453 (1998-02-01), Stewart
patent: 5721908 (1998-02-01), Largarde et al.
patent: 5732219 (1998-03-01), Blumer et al.
patent: 5734831 (1998-03-01), Sanders
patent: 5740263 (1998-04-01), Cohn et al.
patent: 5742768 (1998-04-01), Gennaro et al.
patent: 5742845 (1998-04-01), Wagner
patent: 5745360 (1998-04-01), Leone et al.
patent: 5752246 (1998-05-01), Rogers et al.
patent: 5754830 (1998-05-01), Butts et al.
patent: 5764908 (1998-06-01), Shoji et
Jahromi Babak
Teng Chia-Chi
Harrell Robert B.
Leydig , Voit & Mayer, Ltd.
Microsoft Corporation
Willett Stephan
LandOfFree
System and method for collecting printer administration... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with System and method for collecting printer administration..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and System and method for collecting printer administration... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-2565909