Generally, laptops and other portable computers achieve portability at the expense of performance, connectivity, and ergonomics associated with desktop or workstation counterparts. Some users employ a two-computer solution, using a desktop in one location and a laptop elsewhere. However, this solution often involves synchronizing data between two computers, which can be inconvenient and sometimes results in accidental data loss.
Some laptops obviate the need for a desktop by providing sufficient connectivity for peripherals such as printers, monitors, networks, and external hard drives. However, connecting and disconnecting such peripherals one by one can be tedious and cause wear and tear on all the connectors involved.
Computer docks permit a laptop to connect to multiple peripherals using a single connection between the laptop and a dock, to which the peripherals remain connected while the laptop is on the road. Many docks have proprietary connectors for handling the data for the various connected peripherals. However, with the increased data handling capabilities of USB (Universal Serial Bus) 2.0 and the upcoming USB 3.0, docks that connect with computers over USB are increasingly prevalent.
The inventors recognized that docks and especially docks with USB or other non-proprietary docking connectors could provide unauthorized access to peripherals (including a network and networked peripherals) and data (e.g., on a hard drive attached to the dock). Likewise, an unauthorized person could steal the dock. To prevent the dock from being stolen, it can be physically secured to a fixture (such as a desk) via a lock such as a Kensington or Kensington-compatible lock. To this end, the dock can include a slot for the lock.
The dock described herein includes media for storing driver code that provides for installing a driver for the dock on a computer. However, this media is not accessible while the dock is physically secured by the lock. When the lock is inserted into the matching slot, the media is disconnected from a docking port so that a connected computer cannot access the driver code on the dock. Thus, computers that have had access to the dock while it was not physically secured can use the dock to access peripherals. Other computers can connect to the dock, but cannot install the driver. As a result, their access to peripherals through the dock will be restricted or prohibited.
As shown in
Dock 10 also includes a switch 33. Switch 33 is a normally closed switch so that USB flash drive 21 and hub 31 are normally connected, in which case USB flash drive is connected to docking port 30 and thus to a computer connected to docking port 30. When lock 18 or, more precisely, the functional shaft 35 thereof, is inserted into a compatible (Kensington) slot 37, it forces switch 33 into an open condition, disconnecting flash drive 21 from hub 31, docking port 30, and any connected computer. In the process, a spring 39 of switch 33 is compressed (as shown in the lower portion of
Note that while switch 33 is depicted as a mechanical switch, other switches use other technologies that can provide the same functionality. For example, the switch can be a relay or transistor-based switch. In the latter case, the lock shaft can serve as a conductor tying a contact to ground so as to turn off a transistor that otherwise would couple a flash drive to a docking port.
Laptop computer 11 includes a processor 43, communications devices 45, and computer-readable storage media 47. Communications devices 45 include a USB port 49. Media 47 has encoded thereon code including code constituting an operating system 51. When operating system 51 interacts with driver code 40, driver 30 can be installed on laptop 11 if it has not already been.
However, such installation cannot occur when lock 18 is inserted into slot 37, which is the normal situation when dock 10 is tethered to a fixture such as desk 53 (
Some embodiments permit user control to be circumvented by obtaining a driver from another source, e.g., downloading from a web site or installing a driver from a similar dock. The switch described below provides security code 41 so that access by computers with a similar driver but either lacking a security code or having a different security code can be restricted or prohibited. In an alternative embodiment, the security code is a hardware code, e.g., a MAC (Media Access Control) address, rather than a software security code.
System AP1 provides for implementation of a method ME1, flow charted in
At method segment M12, a computer can be connected to the dock; for example, laptop 11 can be connected to dock 10 via docking port 30. This allows the computer to recognize the dock media; for example, when laptop 11 is connected to dock 10 (while dock 10 is unlocked), flash drive 21 is mounted on laptop 11. Note method segment M12 can occur before or after method segment M11. In the former case, the computer cannot recognize the dock media until the dock is unlocked. The state resulting from method segment M12 is represented in the upper portion of
Method segment M13 involves installing a driver onto the docked computer. This involves the computer's operating system interacting with driver code 40 so that driver 20 is installed. Security code 41 is copied to driver 20 at this point as well. This installation is possible because laptop 11 is connected to flash drive 21 via USB port 49, docking port 30, and internal dock USB hub 31.
Method segment M14 involves locking the dock. This generally involves mechanically engaging the lock with the dock. Typically, the lock is mechanically attached to or tethered to a fixture, such as a desk. For example, lock 18 can be attached to desk 53 and dock 10 can be locked by inserting lock 18 into slot 35 and engaging the locking mechanism. The computer can be docked or, if it has been removed, undocked at this point. The resulting state is represented by the lower portion of
Method segment M15 involves attaching peripherals to the dock. This would typically involve using connectors other than the docking connector. The other connectors can be USB ports, video ports, printer ports, network ports, etc. Note that some “peripherals” can be built into the dock, such as an optical disk drive, flash memory slots, etc. The order in which method segment M15 falls in relation to method segments M11-M14 can vary from scenario to scenario. However, it would generally precede method segment M16, which provides for the computer interacting with peripherals via the dock.
In some scenarios, method ME can continue with method segment M21, shown in
At method segment M31, an unprepared computer is connected to the dock. For example, this method segment can refer to laptop 11 before driver 20 was installed. Alternatively, it can refer to some other computer that lacks driver 20. As a result, the unprepared computer fails to interact fully with the dock and the peripherals. This can be because some functionality requires a driver or because dock 20 actively restricts or prohibits some interactions when driver 20 is lacking. This is especially the case where a security code is used for access. Examples include a code used for network recognition or for decrypting encrypted data on a hard disk peripheral such as hard disk 14 (
For embodiments employing a USB dock, the USB standard involved can be USB 2.0 or later. USB 3.0 brings increased performance and therefore support for more dock connections. For other embodiments, other connection can be used for the docking port, including Firewire (IEEE 1394), E-SATA, and proprietary connections. Also, different physical locking systems can be used. For example, some docking stations provide locking engagement with a mating computer. These and other variations upon and modifications to the illustrated embodiment provided for by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5862349 | Cho et al. | Jan 1999 | A |
5933322 | Ruch et al. | Aug 1999 | A |
5941965 | Moroz et al. | Aug 1999 | A |
6567876 | Stufflebeam | May 2003 | B1 |
6594721 | Sakarda et al. | Jul 2003 | B1 |
6704808 | Kasamatsu et al. | Mar 2004 | B2 |
6804740 | Watts, Jr. | Oct 2004 | B1 |
6885552 | Mullen et al. | Apr 2005 | B2 |
6934151 | Nakano et al. | Aug 2005 | B2 |
7079385 | Cheng | Jul 2006 | B1 |
7142421 | Cheng | Nov 2006 | B2 |
7381079 | Chuang | Jun 2008 | B2 |
20020086703 | Dimenstein et al. | Jul 2002 | A1 |
20030149817 | Scott et al. | Aug 2003 | A1 |
20070016965 | Dan et al. | Jan 2007 | A1 |
20080002355 | Carnevali | Jan 2008 | A1 |
20080150684 | Gartner | Jun 2008 | A1 |
20090187678 | Itoh et al. | Jul 2009 | A1 |
20100138581 | Bird et al. | Jun 2010 | A1 |
Number | Date | Country |
---|---|---|
09006475 | Jan 1997 | JP |
2001167038 | Jun 2001 | JP |
2002073197 | Mar 2002 | JP |
2003022149 | Jan 2003 | JP |
2004272597 | Sep 2004 | JP |
WO 2007067195 | Jun 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20100287321 A1 | Nov 2010 | US |