The present invention relates to a data carrier for storing files.
The invention also relates to an apparatus for managing the files stored in a data carrier comprising a light source for illumination, an optical data carrier, and a motor for driving said data carrier, as well as a method of processing data in such a carrier.
The patent document WO 00/58958 discloses such an apparatus.
The invention finds its application notably in optical data carriers, known as SFFO (Small Form-Factor Optical), having the ability to be rewritable. These data carriers are used with apparatus supplied by batteries, so it is important that the battery life is as long as possible.
The SFFO carriers are driven at constant angular velocity. The measures that the invention proposes turn to account the properties of the constant angular velocity.
A data carrier in accordance with the invention comprises files, the transfer rates of which are dependent on their locations on the data carrier, the files often required by the user being in a location that provides a high file transfer rate.
The basic idea of the invention is that the supply power is consumed when the carrier is driven and the light source is on. For example if the user often wants to play a MP3 file having 4.5 MB, it takes 1 s for being transfered into a process unit for being listened to by the user if the file is on the outer part and 2 s if the file is on the inner part of the disc. Supply power is thus economized in that the motor and the source light are used less.
The invention relates to a method of economizing the supply energy of an apparatus managing a data carrier having power-consuming elements which consume supply energy during a transfer of data from the data carrier, which method comprises the steps of:
determining the more frequently used files,
allocating the more frequently used files to locations on the carrier which are faster for transferring,
supplying said power-consuming elements when the transfer has been completed.
These and other aspects of the invention are apparent from and will be elucidated, by way of non-limitative example, with reference to the embodiment(s) described hereinafter.
In the drawings:
When a file placed on the disc I is required, the disc I is driven at a constant speed or angular velocity (CAV). The data rate is thus higher at the outer radius of the disc than at the inner. For example, the bit rate is about 18 Mbps at the inner and 36 Mbps at the outer radius. Then reading of the same file from the inner radius instead of the outer radius requires one second longer. During this second the laser diode 25 is switched on and the disc 1 is spinning. The difference in supply power is significant. The switch 56 can be off after the transfer and an economy of energy is obtained when the transfer time is shorter.
The invention proposes to allocate the most frequently used files close to the outer radius, so that the battery life can be significantly increased.
Analyzing the use of the files renders it possible to determine how often they are read. The processor set 50 as shown in the
The reallocation will typically be done when the disc is in an apparatus connected to a power supply, e.g. when it is recharging its batteries or when the disc is placed in a fixed device such as a PC. The system may want to record when re-allocation was last performed so that the files are not reallocated too often (this may result in degradation of the disc as the same fast locations are overwritten too often).
Another embodiment of the invention proposes to use the UDF File system well known in the state of the art.
There are two ways to implement this feature in the UDF File System. In both cases an UDF implementation that is not aware of this feature will still be able to read the files without problem.
UDF allows applications to define an extension to the File Entry table for their own use. This is called “Application Use Extended Attribute” (see
Controlling the file counting from the application has an advantage because the application knows whether the file was actually used by the user. For example, the user may have skipped an audio track after a few seconds. In this case the application may choose not to count this as a file usage. Similarly, files may be accessed on disc and cached by the application but then not used by the user.
The re-allocation may also be performed under the application control. For example, when the disc is placed in a drive connected to a power supply (e.g. a PC), an application may analyse the file usage and then decide how to optimally re-allocate the file data. Then the application may choose to re-allocate the files so that the most frequently used files are recorded on the outside of the disc. One way to do this is for the application to treat the disc as a block device and bypass the normal file system implementation. The application will create a disc image with the files in the correct locations and then copy the complete disc image including File System tables to disc.
It is also possible to let the file system perform the reallocation, but then the file system implementation must implement the specific reallocation strategy.
Number | Date | Country | Kind |
---|---|---|---|
03290853.5 | Apr 2003 | EP | regional |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/IB04/00991 | 3/24/2004 | WO | 9/29/2005 |