This invention relates to a portable device with a user interface and relates more particularly, though not exclusively, to a portable memory device with a user interface.
When using a portable device with a host such as, for example, a personal computer, laptop computer, notebook computer, personal digital assistant, and so forth, it is normally necessary to use a relatively complex procedure to be able to safely remove the portable device. The portable device is removable from the host and may be, for example, a memory device, a USB flash drive, MP3 player, and so forth. The safely remove procedure will normally involve:
This takes five separate steps, with several clicks of the mouse. This is slow, inconvenient, and prone to errors. As a result, some users do not use this procedure. The not using of the procedure may cause the data transfer to be not complete, the file allocation table to be incomplete, the data in the drive might be corrupted, the data copied into the drive might not be there, and the data copied into the drive may be incomplete.
Similar comments can be made about other functions performed by instructions or commands given to the host, for the firmware of the device, and that are effected on the portable device. For example the erasing of files stored on a portable memory device, saving files to a portable memory device, and so forth.
According to a first preferred aspect there is provided a portable device comprising:
According to a second preferred aspect there is provided a method for using a user interface on a portable device for enabling functions within a host to which the portable device is attachable, the method comprising:
The method may further comprise a preliminary step of determining if the host has the auto-run application and, if not, uploading the auto-run application to the host for residing in the host. Upon the user interface being activated, all necessary functions may be performed automatically and without user involvement and without display of graphic user interfaces.
For both aspects the user interface may be a physical user interface; and may be a push button, a jog button, a rotary wheel, a scroll wheel, and touch button. The at least one function may be safely remove hardware, fast erase of data, slow erase of data, download data, upload data, save data, and the running of a software application. The central processing unit may be for uploading to the host the auto-run application to reside in the host for enabling the user interface in the host. The portable device may be a portable memory device. The portable memory device may be a USB flash memory device.
In order that the invention may be fully understood and readily put into practical effect, there shall now be described by way of non-limitative example only a preferred embodiment of the present invention, the description being with reference to the accompanying illustrative drawings.
In the drawings:
To first refer to
The device 10 has a main body 12 and a connector 14, in this case a USB connector. However, it may be any other suitable form of connector such as, for example, a Firewire connector. Mounted to the body 12 is a physical user interface 16. The user interface 16 may be a push button (as shown) or any other suitable user-activated device including, but not limited to: a jog button, a touch button, a rotary wheel, and a scroll wheel.
The device 10 is adapted to be releasably attached to a host 18 in the normal manner. The device 10 also has a USB interface 20; central processing unit 22 operatively connected to the interface 20; at least one non-volatile memory 24 that may be a single unit or may be several units and that is operatively connected to the central processing unit 20; and a power management module 26 operatively connected to the interface 20, central processing unit 22 and the memory 24. The user interface 16 is operatively connected to the central processing unit 22.
To now refer to
The auto-run application will only be invoked if the device 10 is operatively connected to the host and the user interface 16 is operated. So the auto-run application in the host 18 checks to determine of the user interface 16 has been activated (307). If not (308) the process reverts to after (306). Rather than continuous polling for the user interface 16, the auto-run application in the host 18 may wait for an interrupt from the activation of the user interface 16.
When the user interface 16 is activated (309), the host performs the function commanded by the user interface 16. For example, and as shown in box 312 of
Therefore, once the auto-run application resides in the host 18, it will remain there unless specifically deleted by user action. Whenever a device 10 with user interface 16 is operatively connected to the host 18, the auto-run application will await the activation of the user interface.
Whilst there has been described in the foregoing description a preferred embodiment of the present invention, it will b e understood by those skilled in the technology concerned that many variations or modifications in details of design, construction or operation may be made without departing from the present invention.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/SG2006/000196 | 7/13/2006 | WO | 00 | 12/19/2008 |