US 8,296,757 B2Grant
Copy protection of software and/or data
Issue Date:2012-10-23
•20 Claims
•6 Drawing Sheets
Abstract
Autorun functionality is incorporated into a portable device such as a flash drive, a wireless adapter, a communication adapter, or any USB peripheral device. The portable device is connectable to a computing device (e.g. USB). The portable device may act as a security key to protect software or data running on the computing device from unauthorized use. At least part of the protected software or data may be stored in a protected memory component of the portable device which is not accessible by the user. Upon connecting the integrated circuit memory device to the computing device, the at least part of the protected software or data may run automatically on the computing device to enable the function of the protected software or data; whereby the user may run the protected software or data on the computing device while the portable integrated circuit memory device remains connected to the computing device.
Metadata
Assignee
- Flexiworld Technologies, Inc.
Inventors
- William Ho Chang
- Vinaynathan Viswanathan
Application Information
Application Number:US 12/890,487
Filing Date:2010-09-24
Priority Date:2002-12-12
Art Unit:2191
Classifications
IPC:
G06F9/44
Patent Drawings (6 sheets)
Description
Cross-References to Related Applications
[0001] This application is a continuation of U.S. patent application Ser. No. 10/823,513, filed Apr. 12, 2004 now U.S. Pat. No. 7,805,720, which claims priority to U.S. Provisional Patent Application Ser. No. 60/462,080, filed Apr. 11, 2003, and a continuation-in-part of U.S. patent application Ser. No. 10/734,481, filed Dec. 12, 2003, which claims priority to U.S. Provisional Patent Application Ser. No. 60/433,196, filed Dec. 12, 2002, which are incorporated herein by reference in their entirety for all purposes.
Technical Field
[0002] This invention relates to a system and method for utilizing storage media such as flash memory for achieving autorun of an application executable or installer stored on the storage media.
Background and Summary of the Invention
[0003] As is known in the art, some applications such as software installers may be run automatically upon insertion of a CD-ROM disc into a CD-ROM drive, which may sometimes be called a dock or reader. In operation, this automatic running of an application is provided by an autorun feature that is stored on or incorporated into CD-ROM drive dock/reader. Executables or installers stored on the CD-ROM disc are executed by the host personal computer based upon activation by the autorun feature in the CD-ROM drive dock/reader. In this implementation, the autorun feature is incorporated into the hardware drive/dock/reader, which is separate from the storage media.
[0004] Universal Serial Bus (USB) technology is rapidly gaining preference as the interfacing technology of choice for peripherals on computing devices such as personal or laptop computers. Flash memories coupled with a USB interface has become a convenient and portable storage device that can replaces floppy disks and compact disks (CDs).
[0005] However, the popular and widely-adopted Universal Serial Bus technology does not include distinct autorun features in the docks/readers. As a consequence, conventional integrated circuit memory devices such as USB memory devices do not have autorun functionality.
[0006] Accordingly, the present invention provides autorun functionality to any IC memory device, such as any USB peripheral, that has a memory component interfaced to a computing device interface microcontroller. The present invention provides autorun of one or more executables or application installers from a memory component with an interface to a computing device without an intermediate hardware-based autorun feature. As an example, such interface could be a USB interface and such computing device could be a personal computer.
[0007] For example, each USB peripheral device internally contains a USB microcontroller that performs the functionality associated with identifying the device to a host computing device, such as a personal computer. In accordance with the present invention, autorun firmware is embedded into the USB microcontroller. The autorun firmware enables autorun of an installable or executable application stored on the memory component of the USB device. The firmware acts as bridge component translating all commands and interactions between a host PC and the memory component.
[0008] Additional description and implementations of the present invention will be apparent from the detailed description of the preferred embodiment thereof, which proceeds with reference to the accompanying drawings.
Brief Descriptions of the Drawings
[0009] FIG. 1 illustrates an exemplary implementation of an autorun integrated circuit (IC) memory device according to the present invention.
[0010] FIG. 2 is a block diagram of a prior art arrangement in which a host personal computer includes an intermediate hardware dock that provides an autorun feature.
[0011] FIG. 3 is a flow diagram of an IC memory device autorun method.
[0012] FIGS. 4A and 4B illustrate autorun firmware according to the present invention be embedded into alternative USB device configurations
[0013] FIG. 5 is a block diagram of a USB peripheral having multiple functionalities.
[0014] FIG. 6 is a block diagram of a USB hub with autorun firmware and access to multiple distinct functionalities.
[0015] FIG. 7 is a schematic diagram of a person-operable physical slide switch.
[0016] FIG. 8 is a flow diagram of a software-implemented copy protection method.
Detailed Description of Preferred Embodiment
[0017] FIG. 1 illustrates an exemplary implementation of an autorun integrated circuit (IC) memory device 100 according to the present invention. Autorun IC memory device may be in the form of a USB memory device, a compact flash card, a smart card, etc. For purposes of illustration, autorun IC memory device 100 will be described with reference to a universal serial bus (USB) memory device implementation.
[0018] Autorun IC memory device 100 includes a memory component 110 that communicates with a USB microcontroller 120 having autorun firmware 130 incorporated or embedded into microcontroller 120. Autorun IC memory device 100 includes an upstream port 140 for connecting to a host computing device 150 (e.g., personal or laptop computer, handheld computer, PDA, smart phone, etc., not shown). In the illustrated implementation, upstream port 140 is a USB port.
[0019] Autorun firmware 130 causes an application or executable stored in memory component 110 to be installed or run automatically upon activation of the IC memory device 100 vis-à-vis the host computing device 150. This activation may be achieved in a variety of ways including connecting or inserting the autorun IC memory device 100 into a docking system or port present on or interfaced to the host computing device 150. For example, IC memory device 100 with autorun firmware 130 incorporated into USB microcontroller 120 allows a “USB Flash Drive” storing one or more application executables or installables to be run automatically (i.e., autorun) upon activation, such as being plugged into the USB port of a host PC 150.
[0020] FIG. 2 is a block diagram of a prior art arrangement in which a host personal computer 200 includes an intermediate hardware dock 220 that provides an autorun feature for a storage medium like a CD-ROM 230. Intermediate hardware dock 220 functions as a storage media reader that may be internally integrated with or externally connected to the host personal computer 200 and the storage medium 230.
[0021] In this prior art implementation, insertion of a CD-ROM disc 230 into a CD-ROM dock/reader 220 may cause activation of an autorun feature that is stored on or incorporated into CD-ROM dock/reader 220. Executables or installers stored on the CD-ROM disc 230 may then be executed by the host personal computer 200 based upon activation by the autorun feature CD-ROM dock/reader 220.
[0022] As another example of such a prior art implementation, a flash memory card reader connected to a host computing device, such as a personal computer, may also include an autorun feature that can activate an executable or installer to run on the host computing device.
[0023] A disadvantage of such prior art implementations is that autorun features are incorporated into hardware docks or readers that are separate from the storage media. However, the popular and widely-adopted Universal Serial Bus technology does not include such distinct autorun features. As a consequence, conventional integrated circuit memory devices such as USB memory devices do not have autorun functionality. In contrast, the present invention provides autorun functionality to any IC memory device, such as any USB peripheral that has a memory component interfaced to a USB microcontroller.
[0024] FIG. 3 is a flow diagram of an IC memory device autorun method 300 that may be implemented from firmware 130 incorporated into a USB controller 120.
[0025] In step 305, a USB peripheral is inserted into or connected to a USB port of a host computing device (e.g., a personal computer).
[0026] In step 310, the host computing device performs an enumeration to identify the newly attached USB peripheral.
[0027] Step 320 is a query as to whether the USB peripheral includes autorun firmware that is enabled. If so, step 320 proceeds to step 330. If not, step 320 proceeds to step 370.
[0028] In step 330, the autorun firmware in the USB peripheral announces itself with a device interface description. For example, the device interface description may include Mass Storage Class, SCSI transparent command set, Bulk Only Transport corresponding to a CD-ROM, for example.
[0029] In step 340, the host and the USB peripheral communicate with each other using, for example a standard MMC-2 specification set. The communication includes a response to host commands from the autorun firmware according to the MMC-2 specification. As a part of the MMC-2 specification, the host requests enumeration of files in root directory and the autorun firmware responds to the request.
[0030] In step 350, the autorun firmware informs the host of the presence of an autorun executable file to be executed and provides the file to the host. For example, the file may be named “Autorun.inf,” which may be stored on the memory component of the USB peripheral. The host executes the autorun executable file to provide the autorun functionality.
[0031] Step 360 is a query whether the autorun firmware is to be enumerated again or “re-enumerated.” If so, step 360 proceeds to step 370. If not, step 360 proceeds to step 390. Re-enumeration allows the autorun firmware to announce itself to the host as one or more other USB peripherals (e.g. data storage device, communication adapter, etc.) or, if there is no re-enumeration, the autorun firmware can continue to function as per MMC-2 specifications.
[0032] In step 370, the autorun firmware re-enumerates or identifies itself as another USB device, such as a USB flash drive or a USB wireless (e.g., Bluetooth, WiFi, IrDA) device or “dongle.” With such a re-enumeration, the autorun firmware identifies itself with device interface descriptors for the other USB devices (e.g., USB flash drive or USB Bluetooth dongle).
[0033] In step 380, the autorun firmware loads the firmware associated with the enumerated USB peripheral (e.g., USB flash drive or USB Bluetooth dongle).
[0034] In step 390, the autorun firmware is configured to not re-enumerate itself and continues to act as a virtual CD-ROM type device implementing the MMC-2 specifications.
[0035] Process steps 320, 330, 340, 350 and 360 correspond to the autorun firmware implementation. Step 390 provides for the implementation of a virtual mass storage device from a memory component that implements SCSI command set and MMC-2 specifications.
[0036] Autorun firmware according to the present invention can be embedded into multiple USB device configurations to provide a variety of unique USB peripherals with autorun functionality and into other peripheral devices with similar functionality. For example, FIG. 4A shows a USB hub 400 in which a USB microcontroller 410 with auto run firmware 415 communicates with an internal memory component 420. In FIG. 4B , a USB microcontroller 450 is connected to an external memory component 460 through a USB downstream port 470.
[0037] With reference to FIG. 4A , the USB microcontroller 410 that forms a part of the USB hub 400 typically is a repeater type entity allowing for cascaded multiple USB peripherals to connect through a single upstream port to a host system. The USB microcontroller 410 includes support for programming capability, which includes the autorun firmware 415. The Autorun firmware can then be ported to work on the USB microcontroller 410. The firmware may be stored on the internal memory component 420. Alternatively, the Autorun firmware may be stored on external memory that is in an attached USB memory component 430.
[0038] As another configuration, FIG. 5 is a block diagram of a USB peripheral 500 having multiple functionalities. In this implementation, USB peripheral 500 includes an internal microprocessor with USB interfacing 510, or alternatively a USB microcontroller, that communicates with a memory component 520 and wireless (e.g., Bluetooth) networking hardware 530. As a result, USB peripheral 500 is capable of operating as a wireless (e.g., Bluetooth) networking device or “dongle” and as USB flash drive, both of which are accessible with autorun functionality
[0039] In one configuration, the microprocessor 510 has USB interfacing ability. It is coupled with a memory component 520 and Bluetooth radio component 530. Microprocessor 510 implements client layers of the Bluetooth stack. The firmware that the microprocessor 510 executes is stored in memory component 520. The autorun firmware can also be additionally stored as a part of the functionality of existing firmware or separately in the memory component 520. In another configuration, the microprocessor 510 may not directly have USB interfacing capability and could use a separate USB microcontroller (not shown).
[0040] A feature of including autorun firmware in USB peripherals is that software applications can be bundled with the USB peripherals. The bundled software application may or may not utilize the USB peripheral.
[0041] As an example, FIG. 6 is a block diagram of a USB hub 600 that includes a USB microcontroller 610 with autorun firmware 615 and access to one or multiple distinct functionalities or USB peripherals, such as an external memory component 630, a Bluetooth networking component 640, or a WLAN component 650. Such USB peripherals 630-650 could be formed in combination with USB hub 600. USB hub 600 may be externally connected with one or more of these components 630-650, as illustrated, or alternatively one or more of the components 630-650 can be internally integrated to form a USB peripheral or device with multiple distinct functionalities.
[0042] There could be multiple executions of autorun firmware from each or some of these peripherals. Thus the autorun firmware allows for distribution of software (e.g. device drivers, synchronization software, etc.) that can be autorun along with any USB peripheral.
[0043] The implementation options also include mechanisms for allowing the autorun feature to be enabled or disabled by an external mechanism (e.g., switch) that is included on the device or peripheral. The switch could be manually operable by a person. The switch could be a simple two-mode (e.g., autorun on/off) switch or could be a switch that selects from among more than two modes.
[0044] FIG. 7 is a schematic diagram of a person-operable physical slide switch 700 that allows a person to select from among multiple modes, functionalities, or peripherals available on a USB device or “dongle.” As an example, switch 700 relates to features or peripherals available from USB hub 600 of FIG. 6 , including external memory component 630, and wireless dongle or module (640 or 650) for adding wireless (e.g. Bluetooth, WiFi, IrDA) interface to its host PC.
[0045] In this exemplary illustration, switch 700 has 4 user-selectable positions. In position 710, autorun functionality is enabled, the wireless component is disabled. In position 720, autorun functionality is disabled, wireless component is disabled. In position 730, autorun functionality is enabled, wireless component is enabled. In position 740, autorun functionality is disabled, wireless component is enabled.
[0046] The autorun firmware enables the distribution of software that can be autorun from a memory component. There is also a unique security mechanism that can be incorporated to protect the software that is installable or executable from the memory component by the autorun firmware.
[0047] A section of the internal memory component (e.g., memory component 620, FIG. 6 ) may be protected from public access by password protecting it or by physical security means such as a lock, among other means. The flash memory component can also be segmented into public and private sections. Private sections can be used to store installable or executables that cannot be viewed or accessed by the user, and public sections can be viewed or accessed by users in a conventional manner. The installable or executable software being distributed through the memory component can be stored in the protected region of the memory component. Security by way of copy protection of this installable software can be achieved by allowing only an application launcher executable, which is autorun from the memory component, to access the installable software.
[0048] In one implementation, the application launcher executable has the following characteristics: it is autorun from memory component, and it has access to the protected or private region of memory component. This access is gained by authenticating itself to the memory controller (e.g. USB microcontroller) and/or to the installable software in the protected region of the memory component. The authentication mechanism may be a password-based mechanism or a more involved cryptographic algorithm. Among the various techniques used for authentication are digital signatures and unique identifiers like the Bluetooth Device Address, MAC address, etc. The application launcher executable may authenticate itself directly to the memory controller software and/or installable software or to a separate authentication software that resides in the protected region of the memory component.
[0049] The application launcher executable may be built generically to execute any or all executables and installables that exist within the protected region of the memory component. Alternatively, the application launcher executable may be programmed to launch a particular executable or installable from the protected region. Considering the possibility of the memory component being segmented into “n” protected sections where n is greater than 1, the application launcher executable may access one or more of these sections in the mechanism described herein. The protected memory region may contain, for example, executable software (also called an application executable), or installable software (also called an application installable), or protected data.
[0050] FIG. 8 is a flow diagram of a software-implemented copy protection method for protecting of software that is executable or installable on using autorun firmware.
[0051] In step 810, an application launcher executable that is stored in a memory component of an IC memory device is run automatically on a host computer by an autorun firmware stored on the IC memory device. The autorun firmware is operates automatically upon activation of the IC memory device, such as occurs when the memory device is plugged into a port or socket of the host computer.
[0052] In step 820, the application launcher authenticates itself to authentication agent software that resides in the protected region of the memory component. The authentication agent software may be incorporated within the software executable or installable that is being protected or may be a separate application. The authentication algorithm may be password based or may involve cryptographic techniques.
[0053] Step 830 is a query whether the authentication is successful. If not, access to the protected executable or installable is denied. If authentication is successful, step 830 proceeds to step 840 and the application launcher executable gains access to the protected memory region.
[0054] In step 840, the application launcher executable executes the application executable or installable that is stored in the protected region of the memory component. The application launcher executable may also be programmed to execute any or all executables and installables that exist within the protected region of the memory component.
[0055] In step 850, the executables and installables thus launched are executed on the host computer.
[0056] In view of the many possible embodiments to which the principles of our invention may be applied, it should be recognized that the detailed embodiments are illustrative only and should not be taken as limiting the scope of our invention. Rather, we claim as our invention all such embodiments as may come within the scope and spirit of the following claims and equivalents thereto.
Claims
The invention claimed is:
1. A portable memory device connectable by a user to a host computing device for enabling said user to run or execute at the host computing device a protected software or data and not enabling said user to copy the protected software or data, the portable memory device comprising:
a controller for controlling interaction between the portable memory device and the host computing device;
a memory component that includes a protected memory component storing at least part of the protected software or data that is installable or executable on the host computing device by said user and at least part of the protected software or data stored in the protected memory component cannot be accessed and copied by said user from the protected memory component; and
an autorun software stored on the memory device and executable on the host computing device upon connection and activation of the portable memory device to the host computing device, the autorun software stored on the portable memory device including:
software for running automatically on the host computing device upon connection and activation of the portable memory device with the host computing device;
software for accessing, by the autorun software, at least part of the protected software or data from the protected memory component of the portable memory device in dependence of a successful authentication of the autorun software; and
software for installing, executing, or running, on the host computing device at least part of the protected software or data accessed from the protected memory component of the portable memory device;
whereby the portable memory device enables said user to operate, to run or to execute the protected software or data on the host computing device upon connection and activation of the portable memory device with the host computing device and not enabling said user access to the protected memory component for copying at least part of the protected software or data from the protected memory component of the portable memory device.
2. The portable memory device of claim 1 further comprising a Universal Serial Bus hub for enabling interface with one or more functional components or devices.
3. The portable memory device of claim 1 further including a public memory component that can be viewed or accessed by the user.
4. The portable memory device of claim 1, further comprising a wireless component for adding a wireless interface to the host computing with the wireless component.
5. The portable memory device of claim 1 further comprising a user operable external manual switch on the portable memory device that is accessible and operable by said user to select from among plural operating states.
6. The portable memory device of claim 1 further comprising one upstream port for interfacing or connecting with the host computing device and two or more downstream ports.
7. The portable memory device of claim 1 further comprising a connection that is connectable to a host computing device over a Universal Serial Bus connection port.
8. A method of distributing protected data or software with a portable memory device for copy protection of the protected data or software, the portable memory device including,
a controller for controlling interaction between the portable memory device and a host computing device;
a memory component that includes a protected memory component storing at least part of the protected software or data that is installable or executable on the host computing device by a user and the at least part of the protected data or software stored in the protected memory component cannot be accessed and copied by said user from the protected memory component; and
an autorun software stored on the memory device and executable on the host computing device upon connection and activation of the portable memory device to the host computing device, the method comprising:
running automatically at least part of the autorun software on the host computing device upon connection and activation of the portable memory device with the host computing device;
accessing, by the autorun software, the at least part of the protected software or data from the protected memory component of the portable memory device in dependence of a successful authentication of the autorun software; and
installing, executing or running, on the host computing device, by the autorun software, the at least part of the protected data or software accessed from the protected memory component of the portable memory device;
whereby, the portable memory device enables said user to operate, to run or to execute the protected software or data on the host computing device stored in the protected memory component of the portable memory device and not enabling said user access to the protected memory component for copying the at least part of the protected software or data from the protected memory component of the portable memory device.
9. The method of claim 8 in which the portable memory device further includes a public memory component that can be viewed or accessed by the said user.
10. The method of claim 8 in which the portable memory device further comprises a wireless component for adding a wireless interface to the host computing device with the wireless component.
11. The method of claim 8 in which the portable memory device further comprises a user operable external manual switch on the portable memory device that is accessible and operable by said user to select from among plural operating states.
12. The method of claim 8 in which the portable memory device further comprises one upstream port for interfacing or connecting with the host computing device and two or more downstream ports.
13. The method of claim 8 in which the protected data or software is associated with a wireless software running or executing at the host computing device.
14. An integrated circuit memory device connectable by a user to a host computing device for running or executing a protected data or software on the host computing device without providing said user means to copy at least part of the protected data or software from the integrated circuit memory device, the integrated circuit memory device comprising:
a controller for controlling interaction between the integrated circuit memory device and the host computing device;
a protected memory component storing at least part of a protected data or software that is installable or executable on the host computing device by said user and the protected memory component is not viewable or accessible by said user;
a public memory component that is viewable or accessible by said user for storing data or software components that are viewable or accessible by said user;
the integrated circuit memory device being further configurable to include:
means to install, execute, or run automatically one or more autorun software on the host computing device upon connecting the integrated circuit memory device to the host computing device by said user;
means to access at least part of the protected data or software, by the one or more autorun software, from the protected memory component of the integrated circuit memory device for installing, executing, or running the protected software or data on the host computing device employing the at least part of the protected data or software accessed from the protected memory component of the integrated circuit memory device;
whereby the integrated memory device enables said user to run or to execute on the host computing device the protected data or software stored in the protected memory component of the integrated circuit memory device and the integrated memory device does not enable said user means to access the protected memory component and to copy the at least part of the protected data or software from the protected memory component.
15. The integrated circuit memory device of claim 14 in which accessing the protected memory component by the autorun software includes an authenticated step by the autorun software.
16. The integrated circuit memory device of claim 14 in which the controller and the public memory component operate together as a flash drive storage device to the host computing device.
17. The integrated circuit memory device of claim 14 further comprising a user operable external manual switch that allows a user to select from among plural operating states of the integrated circuit memory device.
18. The integrated circuit memory device of claim 14 further comprising a wireless component for adding a wireless interface to the host computing device.
19. The integrated circuit memory device of claim 14 further comprising a connection that is connectable to a Universal Serial Bus port of the host computing device.
20. The integrated circuit memory device of claim 14 in which the memory component includes an external memory added to the integrated circuit memory device.
Patent Citations (171)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5166809(A) | 1992-11-01 | Surbrook | Applicant |
| US5220674(A) | 1993-06-01 | Morgan et al. | Applicant |
| US5404433(A) | 1995-04-01 | Hosogai | Applicant |
| US5412798(A) | 1995-05-01 | Garney | Applicant |
| US5519641(A) | 1996-05-01 | Beers et al. | Applicant |
| US5564109(A) | 1996-10-01 | Snyder et al. | Applicant |
| US5580177(A) | 1996-12-01 | Gase et al. | Applicant |
| US5596697(A) | 1997-01-01 | Foster et al. | Applicant |
| US5613123(A) | 1997-03-01 | Tsang et al. | Applicant |
| US5619649(A) | 1997-04-01 | Kovnat et al. | Applicant |
| US5699495(A) | 1997-12-01 | Snipp | Applicant |
| US5832191(A) | 1998-11-01 | Thorne | Applicant |
| US5867633(A) | 1999-02-01 | Taylor et al. | Applicant |
| US5911044(A) | 1999-06-01 | Lo et al. | Applicant |
| US5940843(A) | 1999-08-01 | Zucknovich et al. | Applicant |
| US5982520(A) | 1999-11-01 | Weiser et al. | Applicant |
| US5987454(A) | 1999-11-01 | Hobbs | Applicant |
| US6009464(A) | 1999-12-01 | Hamilton et al. | Applicant |
| US6020973(A) | 2000-02-01 | Levine et al. | Applicant |
| US6043898(A) | 2000-03-01 | Jacobs | Applicant |
| US6044428(A) | 2000-03-01 | Rayabhari | Applicant |
| US6046820(A) | 2000-04-01 | Konishi | Applicant |
| US6070185(A) | 2000-05-01 | Anupam et al. | Applicant |
| US6119153(A) | 2000-09-01 | Dujari et al. | Applicant |
| US6138178(A) | 2000-10-01 | Watanabe | Applicant |
| US6141659(A) | 2000-10-01 | Barker et al. | Applicant |
| US6148346(A) | 2000-11-01 | Hanson | Applicant |
| US6167514(A) | 2000-12-01 | Matsui et al. | Applicant |
| US6202023(B1) | 2001-03-01 | Hancock et al. | Applicant |
| US6216183(B1) | 2001-04-01 | Rawlins | Applicant |
| US6225993(B1) | 2001-05-01 | Lindblad et al. | Applicant |
| US6233611(B1) | 2001-05-01 | Ludtke et al. | Applicant |
| US6246486(B1) | 2001-06-01 | Takahashi | Applicant |
| US6256666(B1) | 2001-07-01 | Singhal | Applicant |
| US6263387(B1) | 2001-07-01 | Chrabaszcz | Applicant |
| US6279153(B1) | 2001-08-01 | Bi et al. | Examiner |
| US6282710(B1) | 2001-08-01 | Boehler | Examiner |
| US6285889(B1) | 2001-09-01 | Nykanen et al. | Applicant |
| US6288790(B1) | 2001-09-01 | Yellepeddy et al. | Applicant |
| US6324521(B1) | 2001-11-01 | Shiota et al. | Applicant |
| US6330611(B1) | 2001-12-01 | Itoh et al. | Applicant |
| US6363452(B1) | 2002-03-01 | Lach | Applicant |
| US6366912(B1) | 2002-04-01 | Wallent et al. | Applicant |
| US6366965(B1) | 2002-04-01 | Binford et al. | Applicant |
| US6366966(B1) | 2002-04-01 | Laney et al. | Applicant |
| US6379058(B1) | 2002-04-01 | Petteruti et al. | Applicant |
| US6389010(B1) | 2002-05-01 | Kubler et al. | Applicant |
| US6389159(B2) | 2002-05-01 | Gilman et al. | Applicant |
| US6405362(B1) | 2002-06-01 | Shih et al. | Applicant |
| US6418439(B1) | 2002-07-01 | Papierniak et al. | Applicant |
| US6421748(B1) | 2002-07-01 | Lin et al. | Applicant |
| US6434535(B1) | 2002-08-01 | Kupka et al. | Applicant |
| US6449052(B1) | 2002-09-01 | Sherer et al. | Applicant |
| US6452692(B1) | 2002-09-01 | Yacoub | Applicant |
| US6453127(B2) | 2002-09-01 | Wood et al. | Applicant |
| US6473800(B1) | 2002-10-01 | Jerger et al. | Applicant |
| US6477575(B1) | 2002-11-01 | Koeppel et al. | Applicant |
| US6480292(B1) | 2002-11-01 | Sugiyama | Applicant |
| US6487587(B1) | 2002-11-01 | Dubey | Applicant |
| US6487599(B1) | 2002-11-01 | Smith et al. | Applicant |
| US6493104(B1) | 2002-12-01 | Cromer et al. | Applicant |
| US6529522(B1) | 2003-03-01 | Ito et al. | Applicant |
| US6546387(B1) | 2003-04-01 | Triggs | Applicant |
| US6546419(B1) | 2003-04-01 | Humpleman et al. | Applicant |
| US6553431(B1) | 2003-04-01 | Yamamoto et al. | Applicant |
| US6584903(B2) | 2003-07-01 | Jacobs | Applicant |
| US6594723(B1) | 2003-07-01 | Chapman et al. | Applicant |
| US6600569(B1) | 2003-07-01 | Osada et al. | Applicant |
| US6603744(B2) | 2003-08-01 | Mizutani et al. | Applicant |
| US6604135(B1) | 2003-08-01 | Rogers et al. | Applicant |
| US6607314(B1) | 2003-08-01 | McCannon et al. | Applicant |
| US6608928(B1) | 2003-08-01 | Queiroz | Applicant |
| US6611812(B2) | 2003-08-01 | Hurtado et al. | Applicant |
| US6623527(B1) | 2003-09-01 | Hamzy | Applicant |
| US6625472(B1) | 2003-09-01 | Farazmandnia et al. | Applicant |
| US6628417(B1) | 2003-09-01 | Naito et al. | Applicant |
| US6633395(B1) | 2003-10-01 | Tuchitoi et al. | Applicant |
| US6654135(B2) | 2003-11-01 | Mitan | Applicant |
| US6658625(B1) | 2003-12-01 | Allen | Applicant |
| US6678751(B1) | 2004-01-01 | Hays et al. | Applicant |
| US6694371(B1) | 2004-02-01 | Sanai | Applicant |
| US6697848(B2) | 2004-02-01 | Hamilton et al. | Applicant |
| US6705781(B2) | 2004-03-01 | Iwazaki | Applicant |
| US6735768(B1) | 2004-05-01 | Tanaka | Applicant |
| US6745229(B1) | 2004-06-01 | Gobin et al. | Applicant |
| US6745255(B2) | 2004-06-01 | Yen et al. | Applicant |
| US6751732(B2) | 2004-06-01 | Strobel et al. | Applicant |
| US6757783(B2) | 2004-06-01 | Koh | Examiner |
| US6760745(B1) | 2004-07-01 | Tan et al. | Applicant |
| US6772233(B2) | 2004-08-01 | Iida et al. | Applicant |
| US6785727(B1) | 2004-08-01 | Yamazaki | Applicant |
| US6788428(B1) | 2004-09-01 | Shimokawa | Applicant |
| US6798530(B1) | 2004-09-01 | Buckley et al. | Applicant |
| US6826632(B1) | 2004-11-01 | Wugofski | Applicant |
| US6829672(B1) | 2004-12-01 | Deng et al. | Applicant |
| US6840441(B2) | 2005-01-01 | Monaghan et al. | Applicant |
| US6857716(B1) | 2005-02-01 | Nagahashi | Applicant |
| US6885362(B2) | 2005-04-01 | Suomela | Applicant |
| US6889058(B2) | 2005-05-01 | Tordera | Applicant |
| US6898652(B2) | 2005-05-01 | Peters et al. | Applicant |
| US6941014(B2) | 2005-09-01 | Lin et al. | Applicant |
| US6944687(B2) | 2005-09-01 | Doragh et al. | Applicant |
| US6948165(B1) | 2005-09-01 | Luu et al. | Applicant |
| US6975644(B2) | 2005-12-01 | Tordera et al. | Applicant |
| US7050840(B2) | 2006-05-01 | Lin et al. | Applicant |
| US7055956(B2) | 2006-06-01 | Olson et al. | Applicant |
| US7102691(B2) | 2006-09-01 | Dischert et al. | Applicant |
| US7136914(B2) | 2006-11-01 | Motoyama | Applicant |
| US7149834(B2) | 2006-12-01 | Peters et al. | Applicant |
| US7174535(B2) | 2007-02-01 | Wragge | Applicant |
| US7237046(B2) | 2007-06-01 | Paley et al. | Applicant |
| US7243153(B2) | 2007-07-01 | McIntyre et al. | Applicant |
| US7353416(B2) | 2008-04-01 | Jeansonne et al. | Applicant |
| US7370090(B2) | 2008-05-01 | Nakaoka et al. | Applicant |
| US7908401(B2) | 2011-03-01 | Chang | Applicant |
| US2001/0029531(A1) | 2001-10-01 | Ohta | Applicant |
| US2001/0032254(A1) | 2001-10-01 | Hawkins | Applicant |
| US2002/0012329(A1) | 2002-01-01 | Atkinson | Applicant |
| US2002/0026492(A1) | 2002-02-01 | Fujita | Applicant |
| US2002/0032855(A1) | 2002-03-01 | Neves et al. | Applicant |
| US2002/0065098(A1) | 2002-05-01 | Hosogaya | Applicant |
| US2002/0065872(A1) | 2002-05-01 | Genske | Applicant |
| US2002/0078367(A1) | 2002-06-01 | Lang | Applicant |
| US2002/0081993(A1) | 2002-06-01 | Toyoshima | Applicant |
| US2002/0083151(A1) | 2002-06-01 | Adams | Applicant |
| US2002/0083430(A1) | 2002-06-01 | Kusuda | Applicant |
| US2002/0097408(A1) | 2002-07-01 | Chang | Applicant |
| US2002/0097415(A1) | 2002-07-01 | Chang | Applicant |
| US2002/0097416(A1) | 2002-07-01 | Chang | Applicant |
| US2002/0097417(A1) | 2002-07-01 | Chang | Applicant |
| US2002/0097418(A1) | 2002-07-01 | Chang | Applicant |
| US2002/0097419(A1) | 2002-07-01 | Chang | Applicant |
| US2002/0097433(A1) | 2002-07-01 | Chang | Applicant |
| US2002/0101515(A1) | 2002-08-01 | Yoshida | Applicant |
| US2002/0108054(A1) | 2002-08-01 | Moore et al. | Applicant |
| US2002/0145632(A1) | 2002-10-01 | Shmueli | Applicant |
| US2003/0028797(A1) | 2003-02-01 | Long et al. | Examiner |
| US2003/0046447(A1) | 2003-03-01 | Kouperchliak | Applicant |
| US2003/0084256(A1) | 2003-05-01 | McKee | Applicant |
| US2003/0087601(A1) | 2003-05-01 | Agam | Applicant |
| US2003/0110371(A1) | 2003-06-01 | Yang | Applicant |
| US2003/0112975(A1) | 2003-06-01 | Taiwanese | Applicant |
| US2003/0120754(A1) | 2003-06-01 | Muto | Applicant |
| US2003/0122934(A1) | 2003-07-01 | Shiohara | Applicant |
| US2003/0160993(A1) | 2003-08-01 | Kang | Applicant |
| US2003/0200372(A1) | 2003-10-01 | Doragh et al. | Applicant |
| US2003/0225971(A1) | 2003-12-01 | Oishi | Applicant |
| US2004/0006648(A9) | 2004-01-01 | Kita et al. | Applicant |
| US2004/0015709(A1) | 2004-01-01 | Chen | Applicant |
| US2004/0057075(A1) | 2004-03-01 | Stewart | Applicant |
| US2004/0070379(A1) | 2004-04-01 | Koretsky | Applicant |
| US2004/0095382(A1) | 2004-05-01 | Fisher et al. | Applicant |
| US2004/0177355(A1) | 2004-09-01 | Wragge | Applicant |
| US2004/0203694(A1) | 2004-10-01 | Wong | Applicant |
| US2005/0005149(A1) | 2005-01-01 | Hirota et al. | Applicant |
| US2005/0005263(A1) | 2005-01-01 | Miyazaki | Applicant |
| US2005/0246436(A1) | 2005-11-01 | Day et al. | Applicant |
| US2006/0080517(A1) | 2006-04-01 | Brown | Examiner |
| US2006/0173980(A1) | 2006-08-01 | Kobayashi | Applicant |
| US2007/0081486(A1) | 2007-04-01 | Koide | Applicant |
| US2008/0003947(A1) | 2008-01-01 | Morris | Applicant |
| US2008/0071935(A1) | 2008-03-01 | Ohta | Applicant |
| US2008/0126628(A1) | 2008-05-01 | Mullis | Applicant |
| US2009/0198839(A1) | 2009-08-01 | Banerjee | Applicant |
| US2011/0138378(A1) | 2011-06-01 | Chang et al. | Applicant |
| US2011/0167166(A1) | 2011-07-01 | Chang | Applicant |
| US2011/0167175(A1) | 2011-07-01 | Chang | Applicant |
| EP473987 | 1992-03-01 | Applicant | |
| WO9526703 | 1995-10-01 | Applicant | |
| WO6904 | 2000-02-01 | Applicant | |
| WO3015641 | 2003-02-01 | Applicant |
Non-Patent Literature (19)
- Attiaoui et al., Conception of Data Base Management System in USB Smart Card Flash Memory: Application for the Cancer Pathology of Medical Information Systems; 3rd International Conference: Sciences of Electronic, Technologies of Information and Telecommunications Mar. 27-31, 2005—Tunisia, pp. 1-7.Examiner
- European Examination Report of European Application No. 04759486.6 dated Dec. 23, 2011, 11 pages total.Applicant
- David, J., “Security in a Flash”, Computers & Security, vol. 22, No. 1, Jan. 1, 2003, pp. 29-33, Elsevier Science Publishers, Amsterdam, Netherlands.Applicant
- Wiener et al. “Meeting USB and IEEE1394 overcurrent protection requirements using PolySwitch devices”, IEEE Wescon/97 Conference Proceedings, Nov. 1997 pp. 442-475.Applicant
- Remple, “USB on-the-go interface for portable devices”, IEEE, Jun. 2003 pp. 8-9.Applicant
- Jankovec et al., “Analog circuit development system”, IEEE, Sep. 2003 pp. 125-129 vol. 1.Applicant
- WIPO, “International Search Report” for PCT/US2003/039547; mailed Jul. 15, 2005; 4 pages.Applicant
- WIPO, “International Search Report” for PCT/US2004/011372; mailed Jun. 20, 2007; 3 pages.Applicant
- WIPO, “International Preliminary Examination Report and Written Opinion” for PCT/US2004/011372; mailed Aug. 14, 2007; 3 pages.Applicant
- USPTO “Office Action” for U.S. Appl. No. 10/823,513; mailing date Feb. 8, 2007; 60 pages.Applicant
- USPTO “Office Action” for U.S. Appl. No. 10/823,513; mailing date Oct. 31, 2007; 26 pages.Applicant
- USPTO “Office Action” for U.S. Appl. No. 10/734,481; mailing date Mar. 24, 2008; 33 pages.Applicant
- USPTO “Office Action” for U.S. Appl. No. 10/734,484; mailing date Sep. 2, 2008; 44 pages.Applicant
- USPTO “Office Action” for U.S. Appl. No. 10/823,513; mailing date Dec. 29, 2008; 28 pages.Applicant
- USPTO “Office Action” for U.S. Appl. No. 10/734,481; mailing date Jan. 6, 2009; 43 pages.Applicant
- USPTO “Office Action” for U.S. Appl. No. 10/823,513; mailing date Dec. 17, 2009; 32 pages.Applicant
- USPTO; “Notice of Allowance” for U.S. Appl. No. 10/823,513; mailing date Jun. 1, 2010; 43 pages.Applicant
- USPTO; “Notice of Allowance” for U.S. Appl. No. 10/734,484; mailing date Oct. 28, 2011; 57 pages.Applicant
- USPTO; “Office Action” for U.S. Appl. No. 10/734,481; mailing date Aug. 2, 2011; 68 pages.Applicant