Integrated circuit device that includes a secure element and a wireless component for transmitting protected data over short range wireless point-to-point communications

Information

  • Patent Grant
  • 10359957
  • Patent Number
    10,359,957
  • Date Filed
    Thursday, February 11, 2016
    9 years ago
  • Date Issued
    Tuesday, July 23, 2019
    5 years ago
Abstract
An integrated circuit device that includes a wireless component and a secure element is herein disclosed and enabled. The integrated circuit device includes a protected memory area for storing protected data that is implemented to be not accessible by a user, but is accessible by a memory controller included in the integrated circuit device. The memory controller accesses the protected data with a combination of security operations that may include cryptography, decryption, or encryption. The integrated circuit device further includes a wireless interface for establishing a short range wireless point-to-point communication with wireless computing devices or readers for transmitting the protected data that is encrypted. The integrated circuit device functions as a security key requiring the presence of the integrated circuit device when accessing and using the protected data. The wireless integrated circuit device can be included in, or embodied as, any wireless communication device, such as a smart phone.
Description
TECHNICAL FIELD

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

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.


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).


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.


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.


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.


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


FIG. 1 illustrates an exemplary implementation of an autorun integrated circuit (IC) memory device according to the present invention.



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.



FIG. 3 is a flow diagram of an IC memory device autorun method.



FIGS. 4A and 4B illustrate autorun firmware according to the present invention be embedded into alternative USB device configurations.



FIG. 5 is a block diagram of a USB peripheral having multiple functionalities.



FIG. 6 is a block diagram of a USB hub with autorun firmware and access to multiple distinct functionalities.



FIG. 7 is a schematic diagram of a person-operable physical slide switch.



FIG. 8 is a flow diagram of a software-implemented copy protection method.





DETAILED DESCRIPTION OF PREFERRED EMBODIMENT


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.


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.


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.



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.


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.


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.


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.



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.


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).


In step 310, the host computing device performs an enumeration to identify the newly attached USB peripheral.


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.


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.


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.


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.


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.


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).


In step 380, the autorun firmware loads the firmware associated with the enumerated USB peripheral (e.g., USB flash drive or USB Bluetooth dongle).


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.


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.


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.


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.


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.


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).


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.


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.


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.


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.



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.


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.


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.


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.


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.


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.



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.


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.


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.


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.


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.


In step 850, the executables and installables thus launched are executed on the host computer.


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
  • 1. An integrated circuit memory device that is a wireless device for transmitting protected data stored in the integrated circuit memory device, the integrated circuit memory device comprising: a wireless interface, that includes a radio component, for establishing a short range wireless communication connection with a wireless computing device, the short range wireless communication connection being a radio communication connection, the wireless computing device being a distinct device from the integrated circuit memory device;a memory controller;a memory component;a protected memory section, in the memory component, storing the protected data that is implemented to be not accessible by a user of the integrated circuit memory device at the protected memory section, but is implemented to be accessible by the memory controller, the protected data includes data or software, individually or in any combination;wherein the integrated circuit memory device is configured for:establishing, via the wireless interface of the integrated circuit memory device, a short range wireless communication connection between the integrated circuit memory device and the wireless computing device, the short range wireless communication connection being a radio communication connection; providing, by the integrated circuit memory device to the wireless computing device, information for identifying itself to the wireless computing device via the established short range wireless communication connection;accessing, by the memory controller, the protected data stored in the protected memory section, the access of the protected data by the memory controller includes an authentication mechanism having a cryptographic algorithm implemented by the memory controller for accessing the protected data stored in the protected memory section; andwirelessly transmitting, via the wireless interface, at least part of the protected data accessed by the memory controller, from the integrated circuit memory device and over the short range wireless communication connection, to the wireless computing device.
  • 2. The device of claim 1, wherein the integrated circuit memory device is further configured for: operating, by the memory controller, at least part of an encryption operation on the protected data for wireless transmission; andwirelessly transmitting, via the wireless interface, at least part of the encrypted protected data by the memory controller, from the integrated circuit memory device and over the short range wireless communication connection, to the wireless computing device;wherein the integrated circuit memory device functions as a security key by requiring presence of the integrated circuit memory device for the wireless transmitting of the at least part of the encrypted protected data.
  • 3. The device of claim 1, wherein the integrated circuit memory device is included in, or embodied as, a smart card, or a dongle, or a USB memory device, or a wireless communication device, individually or in any combination.
  • 4. The device of claim 2, wherein the integrated circuit memory device is further configured for wirelessly discovering the wireless computing device for establishing the short range wireless communication connection.
  • 5. The device of claim 1 in which the integrated circuit memory device is included in a smart phone.
  • 6. The device of claim 5, further comprising a structural interface for connecting the integrated circuit memory device to a reader, or a docket, or a socket, or a port of a computing device, and the integrated circuit memory device is further configured for transmitting the protected data from the integrated circuit memory device, over the structural interface and via a structural connection, to the wireless computing device.
  • 7. A security method for transmitting protected data stored in an integrated circuit memory device, the integrated circuit memory device having: a wireless interface that includes a radio component for establishing a short range wireless communication connection with a wireless computing device, the short range wireless communication connection being a radio communication connection,a memory controller,a memory component,a protected memory area, in the memory component, storing the protected data that is implemented to be accessible by the memory controller by operating an authentication mechanism, the protected data includes data or software executable, individually or in any combination, andan internal memory area, in the memory component, storing a program that is implemented to be not accessible by a user of the integrated circuit memory device, but is implemented to be accessible and executable by the memory controller to support, at least part of, functionalities of the memory controller, the security method comprising: establishing, via the wireless interface of the integrated circuit memory device, a short range wireless communication connection between the integrated circuit memory device and the wireless computing device, the short range wireless communication connection being a radio communication connection;providing, by the integrated circuit memory device to the wireless computing device, at least identification information associated with the integrated circuit memory device;accessing, by the memory controller, the protected data stored in the protected memory area, the accessing of the protected data includes the memory controller operating the authentication mechanism that includes, at least in part, one or more cryptography algorithms;operating, by the memory controller, at least part of an encryption operation on the protected data, accessed by the memory controller, for wireless transmission; andwirelessly transmitting, via the wireless interface, the encrypted protected data, from the integrated circuit memory device and over the short range wireless communication connection, to the wireless computing device,wherein the integrated circuit memory device functions as a security key by requiring presence of the integrated circuit memory device for the wireless transmitting of the encrypted protected data, and security of the protected data is safeguarded at least by the storing of the protected data in the protected memory area of the integrated circuit memory device, by the encryption operation, and by the wireless transmission over the short range wireless communication connection.
  • 8. The method of claim 7, further comprising operating, by the memory controller, at least part of an authentication algorithm that includes cryptography techniques for accessing the protected data stored in the protected memory area.
  • 9. The method of claim 7, wherein the security of the protected data includes preventing cloning or piracy of the protected data, and the security is safeguarded at least by the storing of the protected data in the protected memory area of the integrated circuit memory device, by the one or more cryptography algorithms, by a decryption operation, by the encryption operation, and by the wireless transmission over the short range wireless communication connection.
  • 10. The method of claim 7, wherein the integrated circuit memory device is included in a smart phone.
  • 11. The method of claim 7 in which the integrated circuit memory device is embodied as a smart card, and the wireless computing device is at least a reader.
  • 12. The method of claim 7 in which the integrated circuit memory device functions as a security key by storing a program in the internal memory area that is implemented to be not accessible by the user, but is implemented to be accessible and executable by the memory controller, the program providing at least part of the operations of the memory controller that includes accessing the protected data stored in the protected memory area of the integrated circuit memory device.
  • 13. The method of claim 7 in which the integrated circuit memory device further includes a structural interface for connecting the integrated circuit memory device to a reader, or a docket, or a socket, or a port of a computing device.
  • 14. The method of claim 13, further comprising transmitting the protected data, from the integrated circuit memory device, over the structural interface and via a structural connection, to the wireless computing device.
  • 15. A wireless communication device that includes an integrated circuit memory device for storing protected data and a wireless component for wireless transmission, the wireless communication device comprising: a wireless interface that includes a radio component for establishing a short range wireless communication connection with a wireless computing device, the short range wireless communication connection being a radio communication connection;a memory controller;a memory component included in the integrated circuit memory device;a protected memory area, in the memory component, storing the protected data that is implemented to be not accessible by a user of the wireless communication device, but is implemented to be accessible by the memory controller, the protected data includes data or software executable, individually or in any combination; andan internal memory area, in the memory component, storing a program that is implemented to be not accessible by the user, but is implemented to be accessible and executable by the memory controller to support at least part of functionalities of the memory controller;wherein the wireless communication device is operable for: establishing, by the wireless communication device and via the wireless interface, a short range wireless communication connection between the wireless communication device and the wireless computing device, the short range wireless communication connection being a radio communication connection;activating, by the wireless communication device, at least part of operations of the wireless communication device subsequent to establishing the short range wireless communication connection that is a radio communication connection; andexecuting, by the memory controller, the program stored store in the internal memory area, and the execution of the program, by the memory controller, manages to: access, by the memory controller, the protected data stored in the protected memory area, the accessing of the protected data stored in the protected memory area includes an authentication mechanism that further includes at least one cryptographic algorithm;encrypt, at least part of, the protected data, accessed by the memory controller, for wireless transmission; andwirelessly transmit, via the wireless interface, the encrypted protected data from the wireless communication device and over the short range wireless communication connection, to the wireless computing device; and wherein the wireless communication device-functions as a security key by requiring presence of the wireless communication device for short range wireless transmission of the encrypted protected data to the wireless computing device.
  • 16. The device of claim 15, wherein the wireless communication device is a smart phone.
  • 17. The device of claim 16, wherein security of the protected data includes preventing cloning or piracy of the protected data, and wherein the security of the protected data is safeguarded, at least partly, by the storing of the protected data in the protected memory area of the wireless communication device, by at least one cryptographic algorithm, by the encryption operation, and by the wireless transmission of the encrypted protected data, using the wireless interface and over the short range wireless communication connection to the wireless computing device.
  • 18. The device of claim 15, wherein the integrated circuit memory device is included in, or embodied as, a smart card, or a dongle, or a USB memory device, or a wireless communication device, individually or in any combination.
  • 19. The device of claim 15, further comprising a structural interface for connecting the wireless communication device to a reader, or a docket, or a socket, or a port of a computing device.
  • 20. The device of claim 19, wherein operations of the wireless communication device is further operable for transmitting the protected data, from the wireless communication device, over the structural interface and via a structural connection, to the wireless computing device.
CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 14/835,585, filed on Aug. 25, 2015, which is a continuation of U.S. patent application Ser. No. 14/833,961, filed on Aug. 24, 2015, which is a continuation of U.S. patent application Ser. No. 14/089,622, filed on Nov. 25, 2013, now U.S. Pat. No. 9,116,723, which is a continuation of U.S. patent application Ser. No. 12/891,594, filed on Sep. 27, 2010, now U.S. Pat. No. 8,595,717, which is (1) a continuation of U.S. patent application Ser. No. 10/823,513, filed on Apr. 12, 2004, now U.S. Pat. No. 7,805,720, which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/462,080, filed on Apr. 11, 2003; and (2) a continuation-in-part of U.S. patent application Ser. No. 10/734,481, filed on Dec. 12, 2003, which claims the benefit of U.S. Provisional Patent Application Ser. No. 60/433,196, filed on Dec. 12, 2002. Additionally, this application is a continuation-in-part of U.S. patent application Ser. No. 14/828,349 filed Aug. 17, 2015, which is a continuation of U.S. patent application Ser. No. 13/710,306 filed Dec. 10, 2012, now U.S. Pat. No. 9,110,622, which is a continuation of U.S. patent application Ser. No. 12/903,048 filed Oct. 12, 2010, now U.S. Pat. No. 8,332,521, which is a continuation of U.S. patent application Ser. No. 10/016,223 filed Nov. 1, 2001, now U.S. Pat. No. 7,941,541, which claims benefit of U.S. Provisional Patent Application Ser. No. 60/245,101 filed on Nov. 1, 2000. The complete disclosures of the above patents and patent applications are hereby incorporated by reference for all purposes.

US Referenced Citations (331)
Number Name Date Kind
5166809 Surbrook Nov 1992 A
5220674 Morgan et al. Jun 1993 A
5287194 Lobiondo Feb 1994 A
5337258 Dennis Aug 1994 A
5404433 Hosogai Apr 1995 A
5412798 Gamey May 1995 A
5519641 Beers et al. May 1996 A
5564109 Snyder et al. Oct 1996 A
5580177 Gase et al. Dec 1996 A
5596697 Foster et al. Jan 1997 A
5604843 Shaw et al. Feb 1997 A
5613123 Tsang et al. Mar 1997 A
5619649 Kovnat et al. Apr 1997 A
5699495 Snipp Dec 1997 A
5705781 Habedank et al. Jan 1998 A
5761480 Fukada et al. Jun 1998 A
5832191 Thorne Nov 1998 A
5867633 Taylor, III et al. Feb 1999 A
5911044 Lo et al. Jun 1999 A
5933498 Schneck et al. Aug 1999 A
5940843 Zucknovich et al. Aug 1999 A
5982520 Weiser et al. Nov 1999 A
5987454 Hobbs Nov 1999 A
6009464 Hamilton Dec 1999 A
6020973 Levine et al. Feb 2000 A
6043898 Jacobs Mar 2000 A
6044428 Rayabhari Mar 2000 A
6046820 Konishi Apr 2000 A
6070185 Anupam et al. May 2000 A
6091956 Hollenberg Jul 2000 A
6119153 Dujari et al. Sep 2000 A
6138178 Watanabe Oct 2000 A
6141659 Barker et al. Oct 2000 A
6148346 Hanson Nov 2000 A
6167514 Matsui et al. Dec 2000 A
6202023 Hancock et al. Mar 2001 B1
6216183 Rawlins Apr 2001 B1
6225993 Lindblad et al. May 2001 B1
6233611 Ludtke et al. May 2001 B1
6246486 Takahashi Jun 2001 B1
6251014 Stockdale et al. Jun 2001 B1
6256666 Singhal Jul 2001 B1
6263387 Chrabaszcz Jul 2001 B1
6263392 McCauley Jul 2001 B1
6279153 Bi et al. Aug 2001 B1
6282710 Boehler Aug 2001 B1
6285889 Nykanen et al. Sep 2001 B1
6288790 Yellepeddy et al. Sep 2001 B1
6324521 Shiota et al. Nov 2001 B1
6330611 Itoh et al. Dec 2001 B1
6353928 Altberg et al. Mar 2002 B1
6360364 Chen et al. Mar 2002 B1
6363452 Lach Mar 2002 B1
6366912 Wallent et al. Apr 2002 B1
6366965 Binford et al. Apr 2002 B1
6366966 Laney et al. Apr 2002 B1
6370686 Delo et al. Apr 2002 B1
6379058 Petteruti et al. Apr 2002 B1
6389010 Kubler et al. May 2002 B1
6389159 Gilman et al. May 2002 B2
6405362 Shih et al. Jun 2002 B1
6418439 Papiemiak et al. Jul 2002 B1
6418554 Delo et al. Jul 2002 B1
6421748 Lin et al. Jul 2002 B1
6434535 Kupka et al. Aug 2002 B1
6449052 Sherer et al. Sep 2002 B1
6452692 Yacoub Sep 2002 B1
6453127 Wood et al. Sep 2002 B2
6473800 Jerger et al. Oct 2002 B1
6477575 Koeppel et al. Nov 2002 B1
6480292 Sugiyama Nov 2002 B1
6484219 Dunn et al. Nov 2002 B1
6487587 Dubey Nov 2002 B1
6487599 Smith et al. Nov 2002 B1
6493104 Cromer et al. Dec 2002 B1
6546387 Triggs Apr 2003 B1
6546419 Humpleman et al. Apr 2003 B1
6550008 Zhang Apr 2003 B1
6553431 Yamamoto et al. Apr 2003 B1
6556313 Chang et al. Apr 2003 B1
6529522 Ito et al. May 2003 B1
6584903 Jacobs Jul 2003 B2
6590588 Lincke et al. Jul 2003 B2
6594723 Chapman et al. Jul 2003 B1
6600569 Osada et al. Jul 2003 B1
6603744 Mizutani et al. Aug 2003 B2
6604135 Rogers et al. Aug 2003 B1
6607314 McCannon et al. Aug 2003 B1
6608928 Queiroz Aug 2003 B1
6611812 Hurtado et al. Aug 2003 B2
6623527 Hamzy Sep 2003 B1
6625472 Farazmandnia et al. Sep 2003 B1
6625761 Sartore et al. Sep 2003 B1
6628417 Naito et al. Sep 2003 B1
6633395 Tuchitoi et al. Oct 2003 B1
6636929 Frantz et al. Oct 2003 B1
6654135 Mitani Nov 2003 B2
6658625 Allen Dec 2003 B1
6671068 Chang et al. Dec 2003 B1
6678751 Hays et al. Jan 2004 B1
6694371 Sanai Feb 2004 B1
6697848 Hamilton et al. Feb 2004 B2
6701009 Makoto et al. Mar 2004 B1
6705781 Iwazaki Mar 2004 B2
6735766 Chamberlain et al. May 2004 B1
6735768 Tanaka May 2004 B1
6745229 Gobin et al. Jun 2004 B1
6745255 Yen et al. Jun 2004 B2
6751732 Strobel et al. Jun 2004 B2
6753978 Chang Jun 2004 B1
6757070 Lin et al. Jun 2004 B1
6757783 Koh Jun 2004 B2
6760745 Tan et al. Jul 2004 B1
6772233 Iida et al. Aug 2004 B2
6785727 Yamazaki Aug 2004 B1
6788428 Shimokawa Sep 2004 B1
6798530 Buckley et al. Sep 2004 B1
6826632 Wugofski Nov 2004 B1
6829672 Deng et al. Dec 2004 B1
6839771 Bouchier et al. Jan 2005 B1
6840441 Monaghan et al. Jan 2005 B2
6857716 Nagahashi Feb 2005 B1
6859228 Chang et al. Feb 2005 B1
6885362 Suomela Apr 2005 B2
6889058 Tordera May 2005 B2
6898652 Peters et al. May 2005 B2
6941014 Lin et al. Sep 2005 B2
6944687 Doragh et al. Sep 2005 B2
6947995 Chang et al. Sep 2005 B2
6948165 Luu et al. Sep 2005 B1
6975644 Tordera et al. Dec 2005 B2
7050840 Lin et al. May 2006 B2
7055956 Olson et al. Jun 2006 B2
7055965 Koba Jun 2006 B2
7099304 Liu et al. Aug 2006 B2
7102691 Dischert et al. Sep 2006 B2
7127541 Govindarajulu et al. Oct 2006 B2
7136914 Motoyama Nov 2006 B2
7143408 Anderson et al. Nov 2006 B2
7149834 Peters et al. Dec 2006 B2
7174535 Wragge Feb 2007 B2
7230939 Toyoshima Jun 2007 B2
7237046 Paley et al. Jun 2007 B2
7243153 McIntyre et al. Jul 2007 B2
7260390 Skinner et al. Aug 2007 B1
7269668 Redford et al. Sep 2007 B2
7318086 Chang et al. Jan 2008 B2
7353416 Jeansonne et al. Apr 2008 B2
7370090 Nakaoka et al. May 2008 B2
7484245 Friedman et al. Jan 2009 B1
7609402 Chang et al. Oct 2009 B2
7704147 Quraishi et al. Apr 2010 B2
RE41416 Liu et al. Jul 2010 E
RE41487 Liu et al. Aug 2010 E
RE41532 Liu et al. Aug 2010 E
RE41689 Liu et al. Sep 2010 E
7805720 Chang et al. Sep 2010 B2
RE41882 Liu et al. Oct 2010 E
7908401 Chang Mar 2011 B2
7941541 Chang et al. May 2011 B2
7944577 Chang et al. May 2011 B2
7953818 Chang et al. May 2011 B2
RE42725 Chang et al. Sep 2011 E
RE42828 Liu et al. Oct 2011 E
RE43181 Liu et al. Feb 2012 E
8169649 Chang et al. May 2012 B2
8184324 Chang et al. May 2012 B2
8285802 Chang et al. Oct 2012 B2
8296757 Chang et al. Oct 2012 B2
8332521 Chang et al. Dec 2012 B2
8533352 Chang Sep 2013 B2
8595717 Chang et al. Nov 2013 B2
8630000 Chang et al. Jan 2014 B2
8705097 Chang et al. Apr 2014 B2
8711408 Chang et al. Apr 2014 B2
8812398 Kuhn et al. Aug 2014 B2
8964220 Chang et al. Feb 2015 B2
8972610 Chang Mar 2015 B2
8989064 Chang et al. Mar 2015 B2
9036181 Chang et al. May 2015 B2
9037088 Chang et al. May 2015 B2
9042811 Chang et al. May 2015 B2
9043482 Chang May 2015 B2
9069510 Chang et al. Jun 2015 B2
9092177 Chang et al. Jul 2015 B2
9110622 Chang et al. Aug 2015 B2
9116723 Chang et al. Aug 2015 B2
9164718 Chang et al. Oct 2015 B2
9298407 Chang et al. Mar 2016 B2
9383956 Chang et al. Jul 2016 B2
9389822 Chang et al. Jul 2016 B2
9798516 Chang et al. Oct 2017 B2
RE46637 Liu et al. Dec 2017 E
9836257 Chang et al. Dec 2017 B2
9836259 Chang et al. Dec 2017 B2
9841935 Chang et al. Dec 2017 B2
9965233 Chang et al. May 2018 B2
9971555 Chang et al. May 2018 B2
10037178 Chang et al. Jul 2018 B2
10126991 Chang et al. Nov 2018 B2
10133527 Chang et al. Nov 2018 B2
10140071 Chang et al. Nov 2018 B2
10140072 Chang et al. Nov 2018 B2
10140073 Chang et al. Nov 2018 B2
10152285 Chang et al. Dec 2018 B2
20010029531 Ohta Oct 2001 A1
20010032254 Hawkins Oct 2001 A1
20020012329 Atkinson et al. Jan 2002 A1
20020026492 Fujita Feb 2002 A1
20020032855 Neves et al. Mar 2002 A1
20020051200 Chang May 2002 A1
20020065098 Hosogaya May 2002 A1
20020065872 Genske et al. May 2002 A1
20020078367 Lang et al. Jun 2002 A1
20020081993 Toyoshima Jun 2002 A1
20020083151 Adams et al. Jun 2002 A1
20020083430 Kusuda et al. Jun 2002 A1
20020091843 Vaid Jul 2002 A1
20020097408 Chang et al. Jul 2002 A1
20020097415 Chang et al. Jul 2002 A1
20020097416 Chang et al. Jul 2002 A1
20020097417 Chang et al. Jul 2002 A1
20020097418 Chang et al. Jul 2002 A1
20020097419 Chang et al. Jul 2002 A1
20020097433 Chang et al. Jul 2002 A1
20020101515 Yoshida et al. Aug 2002 A1
20020108054 Moore et al. Aug 2002 A1
20020145632 Shmueli et al. Oct 2002 A1
20020147912 Shmueli et al. Oct 2002 A1
20020174254 Kita et al. Nov 2002 A1
20020178295 Buczek et al. Nov 2002 A1
20030028481 Flitcroft et al. Feb 2003 A1
20030028797 Long et al. Feb 2003 A1
20030046447 Kouperchliak et al. Mar 2003 A1
20030084256 McKee May 2003 A1
20030087601 Agam et al. May 2003 A1
20030110371 Yang et al. Jun 2003 A1
20030110372 Proudler Jun 2003 A1
20030112975 Taiwanese Jun 2003 A1
20030120754 Muto et al. Jun 2003 A1
20030122934 Shiohara Jul 2003 A1
20030126298 Redford et al. Jul 2003 A1
20030160993 Kang Aug 2003 A1
20030161193 Moran et al. Aug 2003 A1
20030182456 Lin et al. Sep 2003 A1
20030196007 Baron Oct 2003 A1
20030200372 Doragh et al. Oct 2003 A1
20030208629 Parkman Nov 2003 A1
20030225971 Oishi et al. Dec 2003 A1
20040006648 Kita et al. Jan 2004 A9
20040015709 Chen et al. Jan 2004 A1
20040057075 Stewart et al. Mar 2004 A1
20040070379 Koretsky et al. Apr 2004 A1
20040078708 Li et al. Apr 2004 A1
20040095382 Fisher et al. May 2004 A1
20040127254 Chang Jul 2004 A1
20040177355 Wragge Sep 2004 A1
20040199909 Goodman Oct 2004 A1
20040203694 Wong et al. Oct 2004 A1
20050005149 Hirota et al. Jan 2005 A1
20050005263 Miyazaki Jan 2005 A1
20050055690 Cornillon et al. Mar 2005 A1
20050059380 Tomita Mar 2005 A1
20050246436 Day et al. Nov 2005 A1
20060080517 Brown Apr 2006 A1
20060173980 Kobayashi et al. Aug 2006 A1
20070038724 Toyoshima Feb 2007 A1
20070081486 Koide Apr 2007 A1
20070240154 Gerzymisch et al. Oct 2007 A1
20070288611 Serceki et al. Dec 2007 A1
20080003947 Morris Jan 2008 A1
20080049740 Serceki et al. Feb 2008 A1
20080071935 Ohta Mar 2008 A1
20080126628 Mullis et al. May 2008 A1
20090048978 Ginter et al. Feb 2009 A1
20090182903 Tordera Jul 2009 A1
20090198839 Banerjee et al. Aug 2009 A1
20090210868 Parthasarathy Aug 2009 A1
20100174631 Tian et al. Jul 2010 A1
20100201996 Chang et al. Aug 2010 A1
20100203824 Chang et al. Aug 2010 A1
20100227550 Chang et al. Sep 2010 A1
20110016280 Chang et al. Jan 2011 A1
20110034150 Chang et al. Feb 2011 A1
20110035682 Chang et al. Feb 2011 A1
20110138378 Chang et al. Jun 2011 A1
20110167166 Chang Jul 2011 A1
20110167175 Chang Jul 2011 A1
20110211226 Chang et al. Sep 2011 A1
20110279829 Chang et al. Nov 2011 A1
20110279863 Chang et al. Nov 2011 A1
20120096451 Tenbarge et al. Apr 2012 A1
20120230315 Chang et al. Sep 2012 A1
20120258700 Chang et al. Oct 2012 A1
20130095887 Chang et al. Apr 2013 A1
20130103775 Chang et al. Apr 2013 A1
20130104052 Chang Apr 2013 A1
20130109353 Chang et al. May 2013 A1
20130111459 Nakamoto May 2013 A1
20140018130 Chang Jan 2014 A1
20140082604 Chang et al. Mar 2014 A1
20150356561 Chang et al. Dec 2015 A1
20150356564 Chang et al. Dec 2015 A1
20150356565 Chang et al. Dec 2015 A1
20150363763 Chang et al. Dec 2015 A1
20150381612 Chang et al. Dec 2015 A1
20160011836 Chang et al. Jan 2016 A1
20160174068 Chang et al. Jun 2016 A1
20160239243 Chang et al. Aug 2016 A1
20160313974 Chang et al. Oct 2016 A1
20170039009 Chang et al. Feb 2017 A1
20170064746 Chang et al. Mar 2017 A1
20170075636 Chang et al. Mar 2017 A1
20170078521 Chang et al. Mar 2017 A1
20170185376 Chang et al. Jun 2017 A1
20170228202 Chang et al. Aug 2017 A1
20170249116 Chang et al. Aug 2017 A1
20170277487 Chang et al. Sep 2017 A1
20170286027 Chang et al. Oct 2017 A1
20170364326 Chang et al. Dec 2017 A1
20180011667 Chang et al. Jan 2018 A1
20180024790 Chang et al. Jan 2018 A1
20180024791 Chang et al. Jan 2018 A1
20180039456 Chang et al. Feb 2018 A1
20180039459 Chang et al. Feb 2018 A1
20180041482 Chang et al. Feb 2018 A1
20180046418 Chang et al. Feb 2018 A1
20180203647 Chang et al. Jul 2018 A1
20180203648 Chang et al. Jul 2018 A1
20180253264 Chang et al. Sep 2018 A1
20180335989 Chang et al. Nov 2018 A1
Foreign Referenced Citations (9)
Number Date Country
1345497 Apr 2002 CN
0473987 Mar 1992 EP
1072976 Jan 2001 EP
9526703 Oct 1995 WO
006904 Feb 2000 WO
0125870 Apr 2001 WO
0241118 May 2002 WO
03015641 Feb 2003 WO
2004093149 Oct 2004 WO
Non-Patent Literature Citations (76)
Entry
Dave Haynie, “The Zorro III Bus Specification: A General Purpose Expansion Bus for High Performance Amiga Computers,” Vernal Equinox Release, Mar. 20, 1991, 60 pages.
Herman D'Hooge, “The Communicating PC,” IEEE Communications Magazine, Apr. 1996, pp. 36-42.
Wiener et al. “Meeting USB and IEEE1394 overcurrent protection requirements using PolySwitch devices,” IEEE Wescon/97 Conference Proceedings, Nov. 1997, pp. 442-475.
Tony K.P. Wong, “An Embedded Chip for USB Application: from the Architecture to the Implementation,” International IC ′99 Conference Proceedings, 1999, pp. 1-10.
E.V. Vetvitskii et al., “Use of the USB Universal Serial Bus in Computer Medical Systems,” Biomedical Engineering, 2000, pp. 167-172, vol. 34, No. 4.
M-Systems, “Mobile DiskOnChip Plus 32/64MByte, Flash Disk with Protection and Security-Enabling Features,” 2002, 50 pages.
Ray Geroski, “Take your data anywhere with these four USB miniature storage devices,” Sep. 23, 2002, 6 pages.
Ed Roth, “Storage in a Flash,” Dec. 15, 2002, 4 pages.
Jon David, “Security in a Flash,” 2003, 6 pages.
Jankovec et al., “Analog circuit development system,” IEEE, 2003, pp. 125-129.
Terrence B. Remple, “USB On-The-Go Interface for Portable Devices,” IEEE, 2003, pp. 8-9.
Attiaoui et al. “Conception of Data Base Management System in USB Smart Card Flash Memory: Application for the cancer Pathology of Medical Information Systems,” SETIT 2005: 3rd International Conference: Sciences of Electronic Technologies of Information and Telecommunications, Mar. 27-31, 2005, pp. 1-7.
Tahir et al., “Analysis of AutoPlay Feature via the USB Flash Drives,” Proceedings of the World Conference on Engineering WCE 2008, London, U.K., Jul. 2-4, 2008, pp. 1-4, vol. 1.
Jebarajan et al., “A Method for Designing an Operating System for Plug and Play Bootstrap Loader USB Drive,” IJCSI International Journal of Computer Science Issues, Jan. 2001, pp. 295-301, vol. 8, Issue 1.
International Searching Authority, International Search Report in International application No. PCT/US01/48057, dated Jan. 6, 2003, 1 page.
International Preliminary Examination Authority, International Preliminary Examination Report in International application No. PCT/US01/48057, dated Aug. 24, 2004, 11 pages.
International Searching Authority, International Search Report in International application No. PCT/US03/39547, dated Jul. 15, 2005, 4 pages.
International Searching Authority, International Search Report in International application No. PCT/US04/11372, dated Jun. 20, 2007, 3 pages.
The International Bureau of WIPO, International Preliminary Report on Patentability in International application No. PCT/US2004/011372, dated Aug. 14, 2007, 8 pages.
State Intellectual Property Office of the P.R.C., Office action in Chinese Patent Application No. 2004800163094.4, dated May 8, 2009, 10 pages.
European Patent Office, Office action in European Patent Application No. 01985549.3, dated Oct. 26, 2010, 4 pages.
State Intellectual Property Office of the P.R.C., Office action in Chinese Patent Application No. 200480016309.4, dated May 24, 2011, 11 pages.
State Intellectual Property Office of the P.R.C., Office action in Chinese Patent Application No. 200480016309.4, dated Oct. 28, 2011, 6 pages.
European Patent Office, Office action in European Patent Application No. 04759486.6, dated Dec. 23, 2011, 11 pages.
State Intellectual Property Office of the P.R.C., Office action in Chinese Patent Application No. 200480016309.4, dated Aug. 5, 2013, 18 pages.
European Patent Office, Office action in European Patent Application No. 04759486.6, dated Jan. 8, 2014, 14 pages.
European Patent Office, Office action in European Patent Application No. 04759486.6, dated Mar. 19, 2014, 3 pages.
State Intellectual Property Office of the P.R.C., Office action in Chinese Patent Application No. 200480016309.4, dated Apr. 3, 2014, 14 pages.
European Patent Office, Office action in European Patent Application No. 04759486.6, dated May 22, 2014, 43 pages.
State Intellectual Property Office of the P.R.C., Decision of Rejection in Chinese Patent Application No. 200480016309A, dated Sep. 29, 2014, 17 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/823,513, dated Feb. 8, 2007, 60 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/823,513, dated Oct. 31, 2007, 26 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Mar. 24, 2008, 33 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,484, dated Sep. 2, 2008, 44 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/823,513, dated Dec. 29, 2008, 28 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Jan. 6, 2009, 43 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Dec. 8, 2009, 40 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/823,513, dated Dec. 17, 2009, 32 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 10/823,513, dated Jun. 1, 2010, 43 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 10/734,484, dated Oct. 28, 2010, 57 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Aug. 2, 2011, 68 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 13/047,672, dated Jan. 20, 2012, 58 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 13/047,674, dated Mar. 14, 2012, 38 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Apr. 4, 2012, 83 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 12/890,487, dated Jun. 20, 2012, 10 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 12/891,594, dated Jul. 5, 2012, 50 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 13/047,674, dated Nov. 6, 2012, 21 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 13/047,672, dated Nov. 6, 2012, 33 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Nov. 7, 2012, 86 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 12/891,594, dated Jan. 18, 2013, 11 pages.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 10/734,481, dated Sep. 28, 2016, 20 pages.
United States Patent and Trademark Office, Office Action for U.S. Appl. No. 10/734,481, dated May 15, 2017, 98 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 13/047,674, dated Apr. 29, 2013, 15 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 12/891,594, dated Jul. 22, 2013, 26 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 13/047,672, dated Aug. 1, 2013, 25 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Sep. 10, 2013, 28 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 14/021,974, dated Nov. 22, 2013, 21 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 13/047,672, dated Dec. 24, 2013, 21 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Apr. 3, 2014, 22 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 14/021,974, dated May 16, 2014, 47 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 13/047,672, dated Jun. 25, 2014, 30 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 10/734,481, dated Aug. 27, 2014, 23 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 14/021,974, dated Sep. 9, 2014, 17 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 14/089,622, dated Oct. 6, 2014, 101 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 13/047,672, dated Oct. 17, 2014, 33 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 14/021,974, dated Dec. 19, 2014, 24 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 10/734,481, dated Dec. 23, 2014, 15 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 14/089,622, dated Mar. 24, 2015, 44 pages.
U.S. Patent and Trademark Office, Notice of Allowance in U.S. Appl. No. 10/734,481, dated Apr. 14, 2015, 18 pages.
U.S. Patent and Trademark Office, Supplemental Notice of Allowability in U.S. Appl. No. 14/089,622, dated Apr. 29, 2015, 16 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Aug. 17, 2015, 19 pages.
U.S. Patent and Trademark Office, Office action in U.S. Appl. No. 10/734,481, dated Jan. 28, 2016, 33 pages.
Office Action issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 15/042,044, dated Jan. 11, 2018, 65 pages.
Office Action issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/835,585, dated Mar. 20, 2018, 96 pages.
Final Office Action issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 14/835,585, dated Oct. 4, 2018, 33 pages.
Office Action issued by the U.S. Patent and Trademark Office for U.S. Appl. No. 10/734,481, dated Feb. 14, 2018, 41 pages.
Related Publications (2)
Number Date Country
20160239232 A1 Aug 2016 US
20180364929 A9 Dec 2018 US
Provisional Applications (2)
Number Date Country
60462080 Apr 2003 US
60433196 Dec 2002 US
Continuations (5)
Number Date Country
Parent 14835585 Aug 2015 US
Child 15042051 US
Parent 14833961 Aug 2015 US
Child 14835585 US
Parent 14089622 Nov 2013 US
Child 14833961 US
Parent 12891594 Sep 2010 US
Child 14089622 US
Parent 10823513 Apr 2004 US
Child 12891594 US
Continuation in Parts (1)
Number Date Country
Parent 10734481 Dec 2003 US
Child 12891594 US