Device handling system and method

• US 6,418,486 B1
• Filed: 07/28/1999
• Issued: 07/09/2002
• Est. Priority Date: 07/28/1999
• Status: Expired due to Term

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Ritchie, Jonathan G., Lortz, Victor B.
• Primary Examiner(s): Shin, Christopher B.
• Application Number:
  US09/362,196
• Time in Patent Office: 1,077 Days
• Field of Search: 710/8-14, 710/15-19, 710/104, 709/217-219, 709/220-222, 709/321, 709/327
• US Class Current: 710/10
• CPC Class Codes: G06F 9/4415 Self describing peripheral devices

Abstract

A system and method for distributing software needed to enable a device coupled to a computer to provide a desired functionality. Static information called a moniker is embedded in the device, and a generic device handler software is installed on the computer. When the device is coupled to the computer, the generic device handler software is executed by the computer to interpret the moniker to identify the software needed to enable the device, determine the enabling software'"'"'s location, and install it, if necessary. The generic handler software and/or the enabling software performs any further action needed by the device or computer to provide or utilize, respectively, the functionality of the device.

Claims

1. A method for enabling the functionality of a device coupled to a computer, including:

a. extracting moniker information stored in the device;

b. interpreting at least part of the moniker information to determine if a custom handler is installed at the computer;

c. if a custom handler is not installed at the computer, then;

i. interpreting at least part of the moniker information to identify the location of a custom handler;

ii. installing the custom handler; and

iii. performing a custom handler action.

2. The method of claim 1, wherein if a custom handler is already installed, then performing a custom handler action.

3. The method of claim 1, wherein the string is stored in the memory of the device.

4. The method of claim 1, wherein the moniker string is adapted to identify a custom handler.

5. The method of claim 1, wherein the moniker string is adapted to identify a property of the device in which the moniker string is stored.

6. The method of claim 1, wherein the moniker string is adapted to provide a device identifier.

7. The method of claim 6, wherein the device identifier is a serial number.

8. The method of claim 6, wherein the device identifier is a model number.

9. The method of claim 1, wherein the moniker string is adapted to identify a protocol for communicating with the device.

10. The method of claim 1, wherein the moniker string includes a cryptographic key.

11. The method of claim 1, wherein the step of interpreting at least part of the moniker string includes the steps of:

i. parsing the moniker string to distinguish a first discrete subpart of the moniker string that specifies a first location for a custom handler;

ii. determining if a custom handler is available at the specified first location;

iii. if a custom handler is not available at the specified first location, then

a. further parsing the moniker string to distinguish a second discrete subpart of the moniker string that specifies a second location for a custom handler;

b. determining if the custom handler is available at the second location.

12. The method of claim 1, wherein the step of installing the custom handler comprises the step of configuring the computer to which the device is coupled to execute at least part of the instructions included in the custom handler.

13. The method of claim 1, wherein performing a custom handler action includes the step of installing on the computer a driver for the device to which the computer is coupled.

14. The method of claim 1, wherein performing a custom handler action includes the step of configuring the computer to which the device is coupled to interoperate with the device.

15. The method of claim 1, wherein performing a custom handler action includes the step of copying instructions adapted to be executed by a processor stored at a first memory to a second memory.

16. The method of claim 1, wherein the step of performing a custom handler action includes the steps of sending status information pertaining to the device from the computer to a remote site.

17. The method of claim 1, wherein the step of performing a custom handler action includes the step of storing at the computer status information pertaining to the device.

18. The method of claim 1, wherein the step of performing a custom handler action includes the steps of:

a. requesting new device software from a remote site;

b. receiving new device software from the remote site; and

c. installing at the computer the new device software.

19. The method of claim 18, wherein the new device software includes a driver that enables an application to communicate with the device.

20. The method of claim 18, wherein the new device software includes device monitoring software that detects and reports a failure of the device.

21. The method of claim 18, wherein the new device software is device monitoring software that diagnoses maintenance requirements of the device.

22. The method of claim 1, wherein the step of performing a custom handler action includes the steps of:

a. requesting a family of drivers from a remote site;

b. receiving a family of drivers from the remote site;

c. installing at the computer a driver from the family of drivers.

23. An apparatus for handling a device coupled to a computer, comprising the steps of:

a. a processor;

b. a memory that stores device handling instructions adapted to be executed by said processor to extract a moniker string stored in a device, interpreting at least part of the moniker string, determine if there is a custom handler installed based at least partly on the interpretation of the moniker string, and if there is not a custom handler installed, then to interpret at least part of the moniker string to identify the location of a custom handler, install the custom handler and perform a custom handler action, said memory coupled to said processor, said processor coupled to the device.

24. The apparatus of claim 23, further comprising a port adapted to be coupled to a network, said port coupled to said processor.

25. A medium that stores instructions adapted to be executed by a processor to perform steps including:

a. extracting a moniker string stored in the device;

b. interpreting at least part of the moniker string to determine if there is a custom handler installed;

i. if there is not a custom handler installed, then

a. interpreting at least part of the moniker string to identify the location of a custom handler;

b. installing the custom handler;

c. performing a custom handler action.

26. The medium of claim 25, wherein if there is a custom handler installed, then the instructions are adapted to be executed by a processor to perform a custom handler action.