Integrated circuit device that includes a protected memory component for transmitting protected data over a communication interface

Abstract

An integrated circuit device that includes a secure or protected memory component is herein disclosed and enabled. The integrated circuit may be a wireless communication device or a smart card or an USB device. Additionally, the integrated circuit may be part of or in a computing device or mobile device. The integrated circuit device includes a private memory section for storing protected data that is not accessible by a user at the private memory section, 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. The integrated circuit device may further include a wireless component for establishing a wireless connection with wireless computing devices or readers for wirelessly transmitting the protected data accessed by the memory controller to the wireless computing devices.

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

SUMMARY OF THE INVENTION

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 have become convenient and portable storage devices that can replace 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 components 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 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.

FIGS. 9-13 are block diagrams of embodiments of a communication device of the present invention.

FIG. 14 is a block diagram 1400 that illustrates the exemplary features of an application of the present invention after the application is launched in the computing device.

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 (Small Computer System Interface) 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 (Mobile Module Connector 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 a 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, USB peripheral device responds to native USB driver commands, and 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 sets and MMC-2specifications.

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 460 that is in an attached USB memory component.

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, and the wireless components are disabled. In position 720, autorun functionality is disabled, and the wireless is components are disabled. In position 730, autorun functionality is enabled, and the wireless components are enabled. In position 740, autorun functionality is disabled, and the wireless components are 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 data or executable software 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 data 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 data or executable software can be achieved by allowing only an application launcher executable, which is autorun from the memory component, to access the installable data or executable software.

In one implementation, the application launcher executable has the following characteristics: it is autorun from the memory component, and it has access to the protected or private region of the 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 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.

FIG. 9 is a block diagram of one embodiment of a communication device 900 of the present invention. The communication device 900 includes a structural interface 910, such as a USB (universal serial bus) interface, and a wireless component interface 920. Interface 910 can be any structural interface including, but not limited, to USB, FireWire (IEEE 1394), CF (compact flash), SD (secure digital), parallel, serial, among others, that enables device 900 to plug into a computing device 170. The wireless interface 920 may be implemented using any wireless medium such as infrared or radio communication according to any protocol including but not limited to Bluetooth®, IEEE 802.11a, IEEE 802.11b (WiFi), IEEE 802.11ab, IEEE 802.11g, IEEE 802.11f, IEEE 802.15, IEEE 802.17, ZigBee® among others.

The communication device 900 includes a memory component 930 that may include volatile memory (e.g., ROM, RAM) and/or non-volatile memory (e.g., flash memory, hard disk). One or more software components or applications (not shown) may be stored in the memory component 930. The software components or applications stored in the memory component 930 may include programs or functionalities that enable device 900 to “auto run” or “auto play” so that, when the communication device 900 is connected with interface 910 to a computing device 170, the program or software application will be automatically installed, launched and executed in the computing device 170, as will be described in detail below. The memory component 930 may include a program memory segment 940 and an optional separate file memory segment 950. Programs or software applications can be stored or embedded in the program memory 940. The software programs or applications may or may not be viewed or edited (e.g., added, deleted or changed) by a user. Hence program memory segment 940 can be implemented as a private or secure section of the memory component 930.

As an optional feature, file memory segment 950 may provide for additional file or data storage, run time buffering of data, or caching of data and files for faster access. The file storage component 950 is an example of an implementation of such memory segmentation. This component 950 may be optional and may or may not exist depending on implementation. Files and data stored in the file storage memory component 950 typically can be saved, retrieved, viewed or edited by a user through a computing device. As an example, the communication device 900 can be used as an external disk drive (e.g., “Flash drive”) that a user can access and use as separate data storage drive when device 900 is plugged into the computing device 170.

The communication device 900 may include an optional external control switch 165, which can be used to activate, deactivate, control or adjust one or more functions provided by the device. The communication device 900 may also include an interface or status indicator (not shown) such as an LCD displaying text or image, lights or sound for status indication.

As is known in the art, wireless interface 920 may include a radio, a baseband controller and separate internal memory (not shown). The separate internal memory, implemented with Flash, RAM and or ROM circuitry, can store instructions and data required for proper functioning of the wireless component 920, such as a wireless protocol stack. Wireless component interface 920 may include an internal processor (not shown) that implements the instructions and logic for complying with wireless protocols (e.g. Bluetooth or IEEE 80211, a,b,g,f, among others), in addition to managing the radio and the baseband of the wireless component interface 920.

Computing device 170 (e.g. PC, laptop, server) includes at least one structural interface 172 to which interface 910 of communication device 900 is connectable. In a typical implementation, structural interface 172 is a USB interface, however other interfaces such as parallel, serial, Firewire (IEEE 1394 a, 1394 b), CF (compact flash), SD (secure digital), Ethernet or wireless interfaces can also be implemented. To simplify the following description of the invention, interfaces 910 and 172 will be referred to a USB interfaces. It will be appreciated, however, that interfaces 910 and 172 could alternatively be implemented with any other interface format.

A computing device 180 (e.g., PC, laptop, server, PDAs such as pocket PC, Palm, Symbian, Java or Linux cell phones, digital cameras, etc.) includes a wireless interface 182. The communication device 900 can communicate with the computing device 180 via wireless interface 920. Examples of wireless interface 920 that can be implemented include Bluetooth, IrDa, ZigBee, IEEE802.11 A, B, F and G, among others.

FIG. 10 is a block diagram of another embodiment of a communication device 1000 of the present invention. Elements of the communication device 1000 that are common to or the same as elements of communication device 900 are indicated by the same reference numerals. In addition, the communication device 1000 includes a controller 260, which may comprise a microprocessor. Other implementations of the controller 260 are and may include a digital signal processor (DSP), a system-on-a-chip (SOC), Field Programmable Gate Arrays FPGL, Application-Specific Integrated Circuit etc. In this implementation, the memory component 930 may also store programs to be executed by the controller 260. Examples of functionality and components operable by controller 160 may include any combination below and are not limited to:

• • A communication protocol stack component (e.g., USB interface or Bluetooth stack, data or format conversion).
  • Communication and or security management software (e.g., protocol encoding/decoding, encryption/decryption, and authentication).
  • Control modules and components for managing the radio and baseband component of wireless interface 920.
  • AutoRun components that provide and control automatic installation and launching on the computing device 170 of one or more programs stored in 940 when the device 900 is plugged into computing device 170.
  • Control and management of the structural interface 910 (e.g. USB, FireWire etc)

The controller 260 may or may not include an operating system. An advantage of the implementation of communication device 1000 in FIG. 10 is that it may have a reduced chip count or hardware component cost compared to some implementations. For example, the functionalities of multiple components of a communication device of this invention may be implemented and managed with a single processor in the controller 260, rather than employing multiple controller/processor implementations.

FIG. 11 is a block diagram of another embodiment of a communication device 1100 of the present invention. Elements of the communication device 1100 that are common to or the same as elements of communication device 900 are indicated by the same reference numerals. In FIG. 11, the memory component 930 acts and may include a hub for the wireless interface 920. Memory component 930 may include a controller or processor (not shown). In FIG. 9, the wireless interface 920 and memory component 930 are connected to the USB interface 910.

As discussed, memory component 940 can be implemented depending on the application. All above features and requirements can be implemented in a single memory component 930, segmented into two components 940 and 950, or segmented into three components 144, 146, and 950 as illustrated in FIGS. 12 and 13.

FIGS. 9-11 show memory component 930 segmented into two sections, private section or program section 940 and public section or file storage section 950. The public file storage component 950 corresponds to memory that can be accessed by the end-user. This optional component 950 allows a user to save and retrieve data when device 900 is plugged into the USB interface of computing device 170. This public memory section 950 (e.g., flash) can also be exposed for public wireless access. Program memory section 940 is private and an end user cannot access it.

FIGS. 12 and 13 illustrate as additional implementations respective communication devices 1200 and 1300 of the present invention. Elements of the communication devices 1200 and 1300 that are common to or the same as elements of communication device 900 are indicated by the same reference numerals. A data output process (e.g. output or printing of digital document or display or presentation of digital content) may be executed using the system configuration as shown in FIGS. 12 and 13.

In communication devices 1200 and 1300 private memory component 940 is segmented into two sections: internal section 144 and embedded section 146. Internal memory section 144 can store data and programs required for proper functioning of the communication device 900. These programs and data can be accessed by a memory controller 1215 [or 515 in FIG. 13] and support its functionalities. Embedded memory section 146 can store programs, applications, and data that will be installed or launched on computing device 170 when communication device 900 is plugged into computing device 170. The software program or applications typically may not be viewed or edited (e.g., added, deleted or changed) by a user and are embedded during the manufacture of devices 1200 and 1300.

Memory controller 1215 [or 515 in FIG. 13] manages communication with the structural external interface 910 [or 525 in FIG. 13] (e.g., USB, FireWire, etc.) and memory component 930. Memory controller 1215 [or 515 in FIG. 13] can be implemented with a microprocessor, DSP, ASIC, etc and may include internal memory for running its program. Additional memory such as those provided by internal memory section 144 can also be implemented if needed. Examples of the functionality and software components that may be implemented with the memory controller 1215 [or 515 in FIG. 13] include “auto run” or “auto play” functionalities, segmentation of memory 930, data security, and USB interfacing functionalities, among others.

Communication device 1200 includes a hub component 425 (e.g., a chip), which combines the components of wireless interface block 920 with the memory component block 930 and its memory controller 1215 [or 515 in FIG. 13]. The hub 425 enables sharing of the same external structural interface 910 [or 525 in FIG. 13] (e.g., USB, FireWire) between wireless component 920, memory controller 1215 [or 515 in FIG. 13] and memory component 930.

Each of FIGS. 9-13 illustrates an optional battery 167 being included in the respective communication devices 900-1300. Optional battery 167 enables each of communication devices 900-1300 to receive or send data wirelessly without being plugged into a computing device 170. Typically, each communication device 900-1300 draws its operating power computing device 170 when plugged into its interface 172 (e.g., USB).

Communication devices 900-1300 of the present invention provide users of mobile devices 180 (e.g., wireless enabled digital camera, mobile phone, etc.) data storage that is integral with the wireless communication and may be independent of computing device 170. In accordance with the present invention, each of communication devices 900-1300 can be configured to communicate in a point-to-point manner with a wireless-enabled mobile device 180 (e.g., a Bluetooth digital camera, phone etc). An embedded application (not shown) stored on each wireless device 900-1300 can manage the communication with an embedded application in the mobile device 180.

An application 1310 is stored or embedded in the memory component 930 of the communication device 900-1300. The application 1310 may be launched and executed in the computing device 170 once the device 900-1300 is connected to or plugged into computing device 170. In this particular example and as shown at 1400 in FIG. 14, the application 1310, after being launched in the computing device 170, may include but is not limited to any combination of the features below:

• • 1. Install necessary one or more drivers, one or more applications, and/or one or more wireless communication stacks in the computing device;
  • 2. Discover existence of other computing devices;
  • 3. Receive information relating to the one or more discovered devices (e.g. name, id, availability, type of service, service or communication options, quality of service, price etc.);
  • 4. Transmit data content to the computing device;
  • 5. Encrypt and/or compress the digital document prior to the transmission;
  • 6. Receive information on an output process (e.g. status, payment requirement, time left to complete, error messages, etc.) from the application; and
  • 7. Provide a GUI in the computing device. The GUI allows the user to select one or more computing devices for communication from a list of discovered computing devices available. Further, the user may select one or more output devices, from a list of available output devices, that are connected to the selected computing device. The GUI may further include means for user to obtain information on the output process and/or give instruction to the output process. For example, this may include providing payment information, status information. The GUI may further allow for controlling the functionality of the application such as initiating, pausing, or canceling the process.

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 for transmitting protected data stored in the integrated circuit memory device to a wireless computing device, the integrated circuit memory device comprising: a graphical user interface;a wireless interface, which includes a radio component, for establishing a local point-to-point wireless communication connection with the wireless computing device, the local point-to-point 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, wherein the protected data stored in the protected memory area is implemented to be inaccessible, at the protected memory area, by a user of the integrated circuit memory device, but is implemented to be accessible by the memory controller, wherein the protected data includes data or software;an internal memory area in the memory component storing a program, wherein the program stored in the internal memory area is implemented to be inaccessible at the internal memory area 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 integrated circuit memory device is configured for: establishing, by the wireless interface of the integrated circuit memory device, the local point-to-point wireless communication connection between the integrated circuit memory device and the wireless computing device, the local point-to-point wireless communication connection being a radio communication connection;accessing, by the memory controller, the protected data stored in the protected memory area;operating, by the memory controller, at least part of an authentication algorithm for accessing the protected data stored in the protected memory area;operating, by the memory controller, at least part of an encryption operation on the protected data for wireless transmission;wirelessly transmitting the encrypted protected data from the integrated circuit memory device over the local point-to-point wireless communication connection to the wireless computing device;wirelessly receiving information, via the wireless interface of the integrated circuit memory device, over the local point-to-point wireless communication connection, from the wireless computing device, in response to the integrated circuit memory device having wirelessly transmitted the encrypted protected data to the wireless computing device over the local point-to-point wireless communication; anddisplaying, on the graphical user interface, at the integrated circuit memory device, and to the user of the integrated circuit memory device, the information that is wirelessly received from the wireless computing device;wherein the integrated circuit memory device provides protection of the protected data by storing the protected data in the protected memory area and requiring use of the integrated circuit memory device for wirelessly transmitting the encrypted protected data stored in the protected memory area.

2. The integrated circuit memory device of claim 1, wherein the protecting of the protected data includes storing the protected data in the protected memory area of the integrated circuit memory device, using a decryption operation, using the encryption operation, and using the wireless transmission over the local point-to-point wireless communication connection.

3. The integrated circuit memory device of claim 1, wherein the integrated circuit memory device is included in at least one of a smart card, a dongle, a USB memory device, or a wireless communication device.

4. The integrated circuit memory device of claim 3, wherein the integrated circuit memory device is a wireless communication device, and wherein the wireless communication device further includes the graphical user interface, and wherein the integrated circuit memory device is further configured for, prior to establishing the local point-to-point wireless communication connection between the integrated circuit memory device and the wireless computing device, obtaining, via the graphical user interface, authentication information for establishing the local point-to-point wireless communication connection between the integrated circuit memory device and the wireless computing device, wherein the authentication information includes a password, a personal identification number (PIN), or biometric information, individually or in combination.

5. The integrated circuit memory device of claim 1, wherein the integrated circuit memory device is further configured for discovering the wireless computing device for establishing the local point-to-point wireless communication connection.

6. The integrated circuit memory device of claim 1, further comprising a structural interface for connecting the integrated circuit memory device to a reader or a computing device, wherein the integrated circuit memory device is further configured for transmitting the encrypted protected data from the integrated circuit memory device, over the structural interface and via a structural connection, to the reader or the computing device.

7. A method for wirelessly transmitting protected data stored in an integrated circuit memory device to a wireless computing device, the integrated circuit memory device having: a graphical user interface;a wireless interface, which includes a radio component, for establishing a local point-to-point wireless communication connection with the wireless computing device, the local point-to-point wireless communication connection being a radio communication connection;a controller;a memory component;a protected memory area in the memory component storing protected data, wherein the protected data stored in the protected memory area is implemented to be inaccessible at the protected memory area by a user of the integrated circuit memory device, but is implemented to be accessible by the controller, wherein the protected data includes data or software; andan internal memory area in the memory component storing a program, wherein the program stored in the internal memory area is implemented to be inaccessible, at the internal memory area, by the user, but is implemented to be accessible and executable by the controller to support at least part of functionalities of the controller;the method comprising: establishing, using the wireless interface of the integrated circuit memory device, the local point-to-point wireless communication connection between the integrated circuit memory device and the wireless computing device, the local point-to-point wireless communication connection being a radio communication connection;enabling, by the integrated circuit memory device, at least part of operations of the integrated circuit memory device subsequent to establishing the local point-to-point wireless communication connection;accessing, by the controller, the protected data stored in the protected memory area;operating, by the controller, at least part of an encryption operation on the protected data for encrypting the protected data for wireless transmission;wirelessly transmitting the encrypted protected data from the integrated circuit memory device, over the local point-to-point wireless communication connection, to the wireless computing device;wirelessly receiving, via the wireless interface, at the integrated circuit memory device, and over the local point-to-point wireless communication connection, information from the wireless computing device, in response to the integrated circuit memory device having wirelessly transmitted the encrypted protected data, over the local point-to-point wireless communication connection, to the wireless computing device; anddisplaying, on the graphical user interface, at the integrated circuit memory device, and to the user of the integrated circuit memory device, the information that is wirelessly received from the wireless computing device,wherein the integrated circuit memory device provides protection of the protected data by storing 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 local point-to-point wireless communication connection.

8. The method of claim 7, further comprising operating, by the controller, at least part of an authentication algorithm for the controller to access the protected data stored in the protected memory area.

9. The method of claim 7, wherein security of the protected data includes storing the protected data in the protected memory area of the integrated circuit memory device, and wherein the security is safeguarded, at least in part, by the storing of the protected data in the protected memory area of the integrated circuit memory device, by a decryption operation, by the encryption operation, and by the wireless transmission over the local point-to-point wireless communication connection.

10. The method of claim 7, wherein the integrated circuit memory device is included in, or embodied as, a smart card, a dongle, a USB memory device, or a wireless communication device.

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 the program in the internal memory area, wherein the program in the internal memory area is implemented to be inaccessible at the internal memory area by the user, but is implemented to be accessible and executable by the controller, wherein the program provides at least part of the operations of the controller, wherein the at least part of the operations 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 is a wireless communication device that includes the graphical user interface, and wherein the method further comprises, prior to establishing the local point-to-point wireless communication connection between the integrated circuit memory device and the wireless computing device, obtaining, via the graphical user interface, authentication information for establishing the local point-to-point wireless communication connection between the integrated circuit memory device and the wireless computing device, wherein the authentication information includes a password, a personal identification number (PIN), or biometric information, individually or in combination.

14. The method of claim 7, wherein the integrated circuit memory device further includes a structural interface for connecting the integrated circuit memory device to a reader, a socket, or a port of a computing device, and wherein the method further comprises transmitting the encrypted 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 transmitting the protected data to a wireless computing device, the wireless communication device comprising: a graphical user interface;a wireless interface, which includes a radio component, for establishing a local point-to-point wireless communication connection with the wireless computing device, the local point-to-point 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, wherein the protected data stored in the protected memory area is implemented to be inaccessible, at the protected memory area, by a user of the wireless communication device at the protected memory area, but is implemented to be accessible by the memory controller, wherein the protected data includes data or software; andan internal memory area in the memory component storing a program, wherein the program is implemented to be inaccessible, at the internal memory area, 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 operations of the wireless communication device include: establishing, by the wireless communication device, the local point-to-point wireless communication connection between the wireless communication device and the wireless computing device, the establishing of the local point-to-point wireless communication connection using the wireless interface of the wireless communication device, the local point-to-point wireless communication connection being a radio communication connection;enabling, by the wireless communication device, at least part of the operations of the wireless communication device, subsequent to establishing the local point-to-point wireless communication connection;executing, by the memory controller, the program stored in the internal memory area, and wherein the execution of the program, by the memory controller, causes the memory controller: to access the protected data stored in the protected memory area, the accessing of the protected data stored in the protected memory area includes an authentication algorithm, andto encrypt the accessed protected data for wireless transmission; wirelessly transmitting the encrypted protected data from the wireless communication device, over the local point-to-point wireless communication connection, to the wireless computing device;wirelessly receiving information, at the wireless communication device, over the local point-to-point wireless communication connection, from the wireless computing device, in response to the wireless communication device having wirelessly transmitted the encrypted protected data to the wireless computing device; anddisplaying, on the graphical user interface, at the wireless communication device, and to the user of the wireless communication device, the information that is wirelessly received from the wireless computing device,wherein the wireless communication device provides protection of the protected data by storing the protected data in the protected memory area and requiring use of the wireless communication device for the wireless transmission of the encrypted protected data.

16. The wireless communication device of claim 15, wherein the operations of the wireless communication device further comprise providing, by the wireless communication device to the wireless computing device, identification information associated with a device interface description.

17. The wireless communication device of claim 15, wherein security of the protected data includes storing the protected data in the protected memory area of the integrated circuit memory device, and wherein the security of the protected data is safeguarded, at least partly, (i) by the storing of the protected data in the protected memory area of the wireless communication device, (ii) by the encryption of the accessed protected data for the wireless transmission, and (iii) by the wireless transmission over the local point-to-point wireless communication connection.

18. The wireless communication device of claim 15, wherein the integrated circuit memory device is included in at least one of a smart card, a dongle, or a USB memory device.

19. The wireless communication device of claim 15, further comprising a structural interface for connecting the integrated circuit memory device to a reader or a computing system.

20. The wireless communication device of claim 19, wherein the operations of the wireless communication device further comprise: transmitting the protected data, from the integrated circuit memory device over the structural interface and via a structural connection, to the reader or the computing system.