System and method for dynamic uploading and execution of applications and drivers between devices

• US 7,610,331 B1
• Filed: 09/13/2000
• Issued: 10/27/2009
• Est. Priority Date: 09/13/2000
• Status: Expired due to Fees

• Current Assignee: Syniverse ICX Corp. (Syniverse Corp.)
• Original Assignee: LightSurf Technologies, Inc. (VeriSign, Inc.)
• Inventors: Bodnar, Eric O., Vogel, David, Genske, Timothy W., Swinton, William G., Kahn, Philippe R.
• Primary Examiner(s): Srivastava; Vivek
• Assistant Examiner(s): CHOUDHURY, AZIZUL Q
• Application Number:
  US09/660,531
• Time in Patent Office: 3,331 Days
• Field of Search: 709/208, 709/220, 709/221, 709/223, 709/224, 709/330, 709/327, 709/321, 709/320, 709/201, 709/202, 709/219, 709/226
• US Class Current: 709/202
• CPC Class Codes: G06F 9/4411 Configuring for operating with peripheral devices; Loading of device drivers
• CPC Class Codes: H04N 1/2179 Interfaces allowing access to a plurality of users, e.g. connection to electronic image libraries

Abstract

A methodology for dynamic (i.e., run-time) uploading and execution of applications and drivers between devices (e.g., between “client” device and one or more (host) devices), in a fully automated manner, is described. The device which is to be hosted (e.g., the “client” device) initially probes its environment to determine which device or devices it is attached to (e.g., the “host” device(s)). Once it has correctly discerned the relevant host or target device(s), the client device includes the capability of immediately sending out (i.e., uploading) a particular driver or application (i.e., object or file of interest) for placement, and ultimately execution, at the host device. Once the particular object or file of interest has been “injected” into the host device and is executing, the client device may simply revert to a “listening mode” in which it waits to be told what to do (i.e., receive commands from the application or driver which is now executing at the host device). This approach is particularly well-suited for devices which serve as “add-on” devices (clients) to other devices (hosts) that are “smarter,” for instance, including more processing capability and/or memory. In this scenario, the client device enters into a dialog with a device with more resources for the purpose of harnessing the resources of the host device for operating the client or add-on device. The client device is, using this approach, able to start running (i.e., driver-directed operation) immediately upon attachment to a host device that can be identified.

Claims

1. A method of interaction between a client device and a host device to be performed when the client device is connected to the host device, the method comprising:

establishing a bidirectional communication channel between the client device and the host device using a handshake command/response;

negotiating a reliable stream protocol connection between the client device and the host device, data for the reliable stream protocol connection to flow over the bidirectional communication channel;

probing the host device by the client device with a probe message to identify the type of host device;

identifying the host device type by the client device with a handshake response, the handshake response transmitted by the host device in response to receiving the probe message;

transmitting executable information selected according to an identity of the host device from the client device to the host device over the reliable stream protocol connection and receiving a file handle for the executable information at the host device;

invoking execution by the client of the executable information at the host device using the file handle; and

entering a listening mode to receive a message sent by the executable information executing at the host device.

2. The method of claim 1 wherein the executable information comprises a device driver file.

3. The method of claim 2 wherein the device driver file, upon execution, controls interaction between the client device and the host device.

4. The method of claim 1 wherein the client device comprises a digital camera.

5. The method of claim 1 wherein the reliable stream protocol connection is a Transmission Control Protocol/Internet Protocol (“

TCP/IP”

) connection between the client device and the host device.

6. The method of claim 1 wherein invoking execution comprises:

instructing the host device to restart itself.

7. The method of claim 1, wherein the client device comprises a digital camera device and wherein said method further comprises:

upon execution of said executable information at said host device, transferring image information from said digital camera device to said host device.

8. The method of claim 7, further comprising:

after transferring said image information from the digital camera device to the host device, the host device wirelessly transmitting the image information to a third device.