Automatic server-side plug-and-play without user intervention

• US 6,813,670 B1
• Filed: 01/22/2001
• Issued: 11/02/2004
• Est. Priority Date: 09/26/2000
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Yao, Baogang, Gulabani, Raju, Watson, Brandon L.
• Primary Examiner(s): Auve, Glenn A.
• Assistant Examiner(s): Lee, Christopher E.
• Application Number:
  US09/681,139
• Publication Number:
  US 20040221081A1
• Time in Patent Office: 1,380 Days
• Field of Search: 710/260, 710/302, 710/315, 710/316, 710/104, 710/8, 709/229, 709/223, 709/250, 709/218, 709/220, 713/1, 713/200, 707/1, 358/474, 717/178
• US Class Current: 710/302
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers

Abstract

Automatic server-side plug-and-play without user intervention is disclosed. An automatic plug-and-play component residing on the server is designed to detect connection and disconnection of a device to a port. Without user intervention, the component automatically installs an appropriate driver for the device upon connection of the device to the port. The device is then accessible by clients served by the server. Also without user intervention, the component automatically uninstalls the driver upon disconnection of the device from the port. The device is then inaccessible by the clients.

Claims

1. A machine-readable medium having stored thereon as a computer program for execution by a processor and a monitoring logic for automatic device plug-and-play without user intervention that is implemented as a state transition system comprising:

a first state in which a device driver is not installed and a plug-and-play identifier has been detected from a device connected to a port;

a second state in which the device driver is installed and the plug-and-play identifier has been detected from the device connected to the port;

a third state in which the device driver is not installed and the plug-and-play identifier has not been detected from the device connected to the port; and

,

a fourth state in which the device driver is installed and the plug-and-play identifier has not been detected from the device connected to the port, wherein the states are transitioned among one another based on a set of transitions comprising;

a first state-to-second state transition based on a device driver installation event;

a first state-to-third state transition based on an event of no detection of the plug-and-play identifier,

a second state-to-first state transition based on a device driver uninstallation event;

a second state-to-second state transition based on an event of detection of a new plug-and-play identifier;

a second state-to-fourth state transition based on the event of no detection of the plug-and-play identifier;

a third state-to-second state transition based on an event of detection of the plug-and-play identifier;

a third state-to-fourth state transition based on the device driver installation event;

a fourth state-to-third state transition based on the device driver uninstallation event; and

,

a fourth state-to-second state transition based on the event of detection of the plug-and-play identifier.

2. The medium of claim 1, wherein the device is a printer, a scanner, a fax machine, a multi-function device (MFD), or a digital camera.

3. The medium of claim 1, wherein the port is a parallel port or a serial port.

4. The medium of claim 3, wherein the serial port has a Universal Serial Bus (USB) form factor or an IEEE1394 form factor.

5. The medium of claim 1, wherein upon connection of the port device to the port, the device driver installation event retrieves a plug-and-play identifier from the device, and selects an appropriate device driver based on the plug-and-play identifier.

6. The medium of claim 5, wherein the device driver installation event includes downloading the appropriate driver from the Internet.