JP2007148637A - Information storage device, information processing method and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To perform efficient management of storage data in a portable storage device for automatically receiving and storing push delivery data. <P>SOLUTION: The storage area of a storage part 16 of a digital still camera 1 is managed separately as a normal area and as a background area. Normal data in which storage necessity is declared by a user such as pick-up image data are stored in the normal area, and uncertain data in which declaration of storage necessity is uncertain are stored in the background area. When a normal file is recorded, a capacity necessary for recording normal data is ensured from the background area, the normal file is written thereto, and the written area is set as the normal area. Although uncertain files can be automatically deleted thereby, normal files can be stored as long as an empty capacity other than the normal area is present. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to an information processing apparatus for storing data acquired by some means such as imaging or via a network in a storage medium, and a method thereof. The present invention also relates to a program executed by such an information processing apparatus.

For example, as an aspect of data distribution, when the terminal side accesses a server or the like to request data and the server distributes data to the terminal in response to this, the terminal side extracts data from the server. Based on this, it is said to be a pull type distribution.
On the other hand, for example, a mode in which the server side transmits the data unilaterally and the received data is received and acquired on the terminal side is called push-type distribution. In recent years, this push-type distribution has been performed for mobile phones, for example.
In recent years, a service called a hot spot that provides an Internet connection service using a wireless LAN in, for example, a public space or place for a large number of unspecified users is becoming widespread. In addition, for example, portable devices such as digital cameras and video cameras are considered to be put into practical use with wireless data communication functions such as wireless LAN and Bluetooth.

  Against this backdrop, the provision of services that actively carry out push-type distribution using portable devices as described above as terminal devices has been envisaged and has been gradually realized. The situation is like that. For example, it is assumed that the user moves around the city while holding a portable device as a terminal, and happens to enter a place where push distribution is performed by wireless data communication. Then, the device possessed by the user is connected to the push delivery server side by wireless data communication, and the push delivered data is automatically received and stored. As such push distribution data, for example, information such as advertisements and guides according to the location can be considered. In other words, by receiving such push-type delivery data, it is possible to collect a lot of information regardless of whether or not the user is particularly conscious of himself / herself. The user confirms the content of the distribution data stored in the portable device in this way by reproducing it and determines whether it is necessary or unnecessary. For example, unnecessary items can be deleted from the portable device, and necessary items can be stored so that they can be reused.

JP 2005-38478 A

  By the way, in the management of storage data in the storage medium, for example, generally as shown in FIG. 9A, all user data storage areas in the storage medium are logically divided into used areas and unused areas. To be divided. An area where data is stored is a used area, and an area where no other data is stored is an unused area. Then, for example, assuming that this storage medium is to record an image captured by a digital still camera, and that an operation for taking a photograph is performed, the operations shown in FIGS. 9A to 9B are performed. As shown as the transition, the captured image data obtained in accordance with the photographing operation is added to the use area and stored. Accordingly, the capacity of the used area in all the storable areas increases, and the capacity of the unused area decreases accordingly.

In this way, the data distributed by the push type distribution is for the user who owns the terminal at the time of receiving and storing the data at the terminal because the push type distribution is one-way information distribution. Whether it is necessary or unnecessary is unknown.
In addition, if the terminal is set to accept the acquisition of push-type delivery data, the terminal accepts and receives the delivered data indiscriminately unless a filter setting is made. It will be remembered.
For this reason, it is conceivable that the terminal is in a situation where push distribution data is stored until the user runs out of space until there is no free space. In such a situation, even if the user operates the terminal again and tries to store data according to his / her clear intention (for example, if the terminal is a digital still camera, it becomes an imaging operation) Since there is no room for free space, for example, it is notified that there is no free space, and data cannot be additionally recorded as it is. At this time, for example, the user needs to delete the data judged unnecessary by listing the stored contents and perform an operation for storing the data again.
That is, a terminal device configured to be able to receive push distribution can enjoy the advantage of automatically acquiring a variety of information, but stores data that may be unnecessary for the user. Since the free space is under pressure, it is difficult to use the storage capacity efficiently, and when the free space is insufficient, the above-mentioned disadvantages such as the deletion operation are accompanied. Have.

In view of the above-described problems, the present invention is configured as an information processing apparatus as follows.
In other words, with respect to data stored in the storage medium, regular data that is data for which the user clearly indicates the necessity of storage, and unconfirmed data that is unconfirmed whether or not this regular data should be used. The classification means for classifying and managing the storage area in the storage medium at least divided into a regular data area formed by a regular data stored area and an unconfirmed data area capable of storing unconfirmed data When newly storing regular data in the storage medium, an area having a capacity capable of storing the newly stored regular data is secured from a storage area other than the regular data area in the storage medium. Write regular data that is newly stored in the area, and manage this area by including it in the regular data area. Was decided and a storage management control means is in so that.

According to the above configuration, the data stored in the storage medium is classified into regular data and unconfirmed data, and the storage area of the storage medium is also a regular data area composed of stored regular data and unconfirmed data. Are divided into unconfirmed data areas that can be stored.
Regular data is data that requires the user to save it in a storage medium (necessity to save), for example, according to some action such as an operation, and unconfirmed data should be regarded as regular data. This is data for which it is uncertain whether it is available, that is, data in a state where the necessity for saving is not clearly specified at the present time.
In addition, when new normal data is stored in the storage medium, the area corresponding to the capacity that can store new normal data is changed from the area other than the normal data area to the normal data area. The new regular data is stored here. In such storage control and management, when regular data is mainly used, areas other than the regular data area including the unconfirmed data area function as free space for regular data storage. Means that.

For example, in the prior art, a storage area for regular data and unconfirmed data is used as a use area, and an area where no remaining data is stored is managed as a free area. In this case, as the amount of unconfirmed data stored increases, the free space also decreases. That is, there is a disadvantage that free space is consumed and compressed by unconfirmed data whose storage necessity is unclear.
In contrast, according to the present invention, regardless of the storage capacity of the unconfirmed file, as long as the user does not explicitly store the regular data, the free space for the regular data does not decrease in the storage medium. As a result, it is possible to efficiently use a storage medium that stores unconfirmed data in addition to regular data.

  Hereinafter, the best mode for carrying out the present invention (hereinafter referred to as an embodiment) will be described. In this embodiment, the configuration based on the present invention is applied to a digital still camera.

The block diagram of FIG. 1 shows a configuration example of a digital still camera 1 as the present embodiment.
In this figure, an imaging information input unit 11 is a part for inputting image information obtained by imaging. For example, a lens optical system for imaging, an imaging element such as a CCD or CMOS sensor, and a signal processing unit that generates captured image data based on an image light signal obtained by these imaging elements are provided. Become.

  The operation unit 12 includes, for example, various operators provided in the main body of the digital still camera 1 and an instruction signal generation unit that generates instruction signals corresponding to predetermined operations on these operators and outputs them to the control unit 15. It is supposed to be shown. The control unit 15 executes various required control processes so that the operation of the digital still camera 1 according to the instruction signal output from the operation unit 12 can be obtained.

  Various types of display are performed on the display unit 13 in accordance with the display control of the control unit 15. For example, in this case, since the display unit 13 is provided in a digital still camera, the display screen size is, for example, about 2 to 3 inches. At present, liquid crystal display devices are widely used as display devices as the display unit 13. In the imaging mode, an image captured by the imaging information input unit 11 is displayed as a monitor image. In the playback mode, captured image data as a photograph stored in the storage unit 16 is displayed and output. In addition, various operation screens are displayed, and operations on the displayed operation screen can be performed by a predetermined operation on the operation unit 12.

In this case, the network interface 14 is a part composed of hardware and software for enabling communication by connecting to a network such as a LAN (Local Area Network) according to a predetermined wireless communication standard. For example, in the present situation, it may be configured by a device and software corresponding to a wireless LAN standard such as IEEE802.11a / b / g.
By providing such a network interface 14, the digital still camera 1 can perform data communication with other devices via a network, and various functions can be realized depending on applications to be mounted. For example, data such as a captured image stored in the storage unit 16 can be transferred to and stored in another device via a network. In addition, it is possible to transfer the captured image data to a printer device connected to a network and print it out.
The digital still camera 1 according to the present embodiment is connected to the network in a public wireless LAN service use area called a so-called hot spot as a function of using the network interface 14, and is distributed via the network at this time. The received push distribution data can be received and acquired and stored in the storage unit 16.

  The control unit 15 adopts a hardware configuration as a microcomputer system including a CPU (Central Processing Unit), a ROM, a RAM, and the like, and executes various control processes in the digital still camera 1, so that the functions of the digital still camera 1 are performed. Realize operation. In the figure, functions of the control unit 15 related to the present embodiment are shown by blocks in the control unit 15. Each of these functions is realized by, for example, a CPU that constitutes a control unit executing a program stored in a ROM (or storage unit 16).

In this case, the function block of the control unit 15 includes a data signal processing unit 20, a time management unit 21, a display control unit 22, a data operation processing unit 23, a file system management unit 24, a storage area management unit 25, and an indeterminate file management. The unit 26 is provided.
The data signal processing unit 20 in this case receives the captured image data generated by the imaging information input unit 11 and performs signal processing such as file conversion and encoding for storing the data as a data file in the storage unit 16. Execute data processing. Further, signal processing necessary for causing the display unit 13 to display and output the contents of the image data input from the imaging information input unit 11 or the storage unit 17 as, for example, a monitor image is also executed.
In this case, the data signal processing unit 20 is also configured to process data such as images, sounds, and texts received and acquired by the network interface 14 at an application level, for example. For example, processing corresponding to the file format of the data is executed by the data signal processing unit 20.

  The time management unit 21 counts the current time and executes processing related to time such as outputting time information in response to a request from another task or the like.

  For example, the display control unit 22 uses display image data passed from the data signal processing unit 20 to perform display control for executing image display on the display unit 13. In addition, for example, the display control unit 22 may execute processing for generating display image data as a user interface image to be displayed on the display unit 13.

  The data operation processing unit 23 is a functional part for managing data file operations for writing and reading data (files) to and from the storage unit 16.

  The file system management unit 24 manages data stored in the storage unit 16 according to a predetermined file system standard.

As will be described later, the storage area of the storage unit 16 of the present embodiment is divided into two logical areas, a normal area and a background area. The storage area management unit 25 manages the storage area of the storage unit 16 by dividing it into a normal area and a background area as described above.
The unconfirmed file management unit 26 manages unconfirmed file data stored in the background storage area, and the management is performed by operating the unconfirmed file list as described later. The

  The storage unit 16 is a storage medium built in the digital still camera 1 or a storage medium that is removable and loaded in the digital still camera 1. The storage unit 16 is a photograph or a movie obtained by photographing with the digital still camera 1. The main purpose is to store and hold a file of the captured image. In addition, as a storage medium as the storage unit 16, currently, a wide removable flash memory is used, but is not limited to this, and for example, a hard disk or an optical disk medium is used. May be.

Further, in the storage unit 16 of FIG. 1, the logical structure is simply shown.
First, in the system area, file system management information and an unconfirmed file list are stored. The file system management information here is, for example, FAT (File Allocation Table) if the file system format of FAT32 or FAT16 is taken as an example. In this embodiment, it is assumed that all files stored in the user data area are managed by this file system management information.
The unconfirmed file list is information in which unconfirmed files stored in the background area of the user data area are listed by a set of predetermined items and attributes as described later.

In the user data area in this case, an image file (referred to as a captured image file) such as a photograph obtained by shooting or a moving image is stored as user data. In addition, a data file (push delivery file) acquired by receiving the push delivery by the network interface 14 is stored. Other types of data and files may be stored as user data in the user data area. However, for convenience of explanation, user data will be stored in the captured image file and the push delivery file hereinafter. The explanation will be limited.
In the present embodiment, this user data area is managed so as to be divided into two logical areas, a normal area and a background area, as shown in the figure. The use of these areas will be described later.

  Next, storage management of user data stored in the storage unit 16 by the digital still camera 1 configured as described above will be described with reference to FIGS.

Here, in the present embodiment, data as a file to be stored in the user data area is classified into a regular file and an indeterminate file.
The regular file indicates, for example, a file that should be stored in a state stored in the user data area and should not be automatically deleted against the user's will. On the other hand, the unconfirmed file indicates a file that has not been confirmed as a regular file at the present time by the user's will. That is, the regular file is a file in which the user clearly indicates the need for saving, and the unconfirmed file is a file in which the user does not clearly indicate the need for saving.

If there are two types of user data that the digital still camera 1 of the present embodiment inputs, acquires, and stores in the storage unit 16, a captured image file and a push delivery file, the captured image file is a regular file. .
That is, in the digital still camera 1, the captured image file is obtained when the user performs an operation for shooting and recording by his / her own will. In other words, the operation for shooting and recording corresponds to the explicit need for storage, and accordingly, the captured image file should be classified into regular data.
On the other hand, the push distribution file obtained by receiving the data transmitted by the push type distribution is determined by the user himself / herself, for example, at the stage of reception and acquisition, after that, for example, by reproducing and outputting. Without it, it is impossible to decide whether or not there is a need for storage. Therefore, it is classified as an unconfirmed file.
It should be noted that when the push-type distribution is received and acquired by the digital still camera 1, one part of the digital still camera 1 receives the data being pushed and distributed by the background operation of the digital still camera 1. A method to make it go is considered. In addition, when the digital still camera 1 detects that push delivery is being performed, first, the user is prompted to set whether or not to accept push delivery, and accepts push delivery. If the setting operation has been performed, a method of acquiring the file by automatically receiving the push delivery is also conceivable.
In the present embodiment, not only the former method but also the push delivery file acquired by the latter method is classified as an indeterminate file. That is, for example, even in the latter case, at the stage of prompting the setting as to whether or not to accept push delivery, the contents of the file to be delivered are not understood. Although the user does not know the content of the push-delivered content, for example, the user can set whether or not to accept the push delivery in accordance with the prediction of whether or not the content is useful for the user. For this reason, even if the user performs an operation to accept push delivery, the content is unknown to the user, and after receiving and acquiring and storing it, the content must be confirmed and finally saved It cannot be determined whether or not there is. In this sense, the push delivery file in this case is also an undetermined file.

First, management of regular files (captured image files) stored in the storage unit 16 will be described with reference to FIG.
Here, in FIG. 2A, the user data area of the storage unit 16 is extracted and shown. As shown also in FIG. 1, the user data area of the present embodiment is divided and managed by a normal area and a background area.
The regular file is stored as being stored in the regular area. FIG. 2A shows a state in which the captured image files D (1) to D (n) are managed so as to be stored in the normal area.
Then, from this state, it is assumed that one captured image file is added and stored in the storage unit 16 according to the user's shooting operation. Then, as shown as a transition from FIG. 2A to FIG. 2B, the data of the captured image corresponding to this imaging operation is newly added in the normal region as the captured image file D (n + 1). Is stored in this way. In response to this, the normal area changes in accordance with the size of the captured image file D (n + 1) so that the capacity thereof increases in the user data area. Accordingly, the background area has a capacity reduced by the capacity of the captured image file D (n + 1). In other words, when a new regular file is stored, an area having a capacity corresponding to the new regular file is first secured from the background area. Then, data of a new regular file is written in the reserved area, and the area where the writing has been performed is newly included in the regular area and managed.
Here, it should be noted in the present embodiment that the size of the regular area is not particularly assigned a predetermined capacity in advance, but changes so as to correspond to the total capacity of the stored regular file. That is. Also, the background area is not particularly assigned a predetermined capacity in advance, but changes as a result of subtracting the capacity of the normal area from the total capacity of the user data area.
For this reason, as described above, as the regular file (captured image file) is additionally recorded, the capacity of the regular area increases by the amount of the additionally recorded file size, and the background area Capacity decreases. Conversely, when a regular file that has been stored is deleted, the capacity of the normal area decreases and the capacity of the background area increases according to the size of the deleted file.

Next, storage management of unconfirmed files will be described with reference to FIG.
FIG. 3A shows a state where the captured image files D (1) to D (n) are stored in the regular area and nothing is stored in the background area. Has been.
Assume that the digital still camera 1 receives push-distributed data and acquires three push-distributed files in this storage state. The push delivery file acquired in this way is stored in the storage unit 16, but the push delivery file is an undetermined file as described above. Therefore, these push delivery files are managed as being in the background area as shown as push delivery files Db (1), Db (2), and Db (3) in FIG. Will be remembered.

As described above, the capacity of the background area is obtained by subtracting the capacity of the normal area from the total capacity of the user data area. Therefore, when the total capacity of unconfirmed files stored in the background area is smaller than the capacity of the background area, there is a free capacity in the background area.
Then, for example, in a state where the unconfirmed file stored in the background area is full and there is no free space in the background area, it is assumed that a new unconfirmed file should be written.
Since the background area is formed by subtracting the capacity of the regular area from the total capacity of the user data area, even if the situation described above is reached, the capacity of the background area is further increased. The capacity of the regular area is reduced and a new unconfirmed file is not recorded. In such a situation, either no more unconfirmed files are recorded, or a specific file is deleted from the stored unconfirmed files according to a predetermined rule to ensure a recordable capacity. The new unconfirmed file is stored in the background area.

The situation where there is no free space in the background area corresponds to the fact that there is no substantial free capacity in the user data area when the regular files and unconfirmed files are combined. In this state, when a new regular file is recorded, in this embodiment, the new regular file recording procedure described with reference to FIG. 1 is applied. That is, even in this case, an area having a capacity corresponding to the regular file to be newly recorded is secured from the background area. However, in this case, since there is no actual free area in the background area, the unconfirmed files stored in the background area are deleted in descending order of necessity according to a predetermined priority. Thus, a capacity capable of writing a new regular file is secured. Thereafter, in the same manner, data of a new regular file is written in the reserved area so that it can be newly included in the regular area and managed.
In this case, as described above, the unconfirmed file is automatically deleted according to the size of the regular file. However, in the present embodiment, the regular file in which the user explicitly indicates the necessity of saving is given higher priority than the unconfirmed file, and the regular file is given priority. This is because, due to the nature of the file, if the regular file is automatically deleted, the loss for the user is greater than if the unconfirmed file is automatically deleted.

The push delivery file stored in the background area as shown in FIG. 3B is an unconfirmed file. In other words, the unconfirmed file indicates that the necessity for saving is clearly indicated by the user. If so, it will be changed to the handling of regular data.
For example, the push delivery files Db (1), Db (2), and Db (3) stored in the background area by the user performing a predetermined operation under the file saving state shown in FIG. After confirming the contents, the user wants to save the push delivery file Db (1) so that the file is not automatically deleted because the push delivery file Db (1) has necessary information contents. Suppose. Therefore, the user designates this push delivery file Db (1) and performs a predetermined operation for re-storing it as a regular file.
In response to this operation, as shown as a transition from FIG. 3B to FIG. 3C, the push delivery file Db (1) is managed as being stored in the regular area. Accordingly, the capacity of the normal area increases by the capacity of the push delivery file Db (1), and the capacity of the background area decreases by the capacity of the push delivery file Db (1). In the push delivery file, push delivery files Db (2) and Db (3) remain. As a result, the push delivery file Db (1) is handled as the same regular file as the captured image file in the following.

  In the present embodiment, for example, as shown in the figure, the unconfirmed file is stored in the background area for the free capacity of the storage unit 16 that is presented and notified to the user by display output on the display unit 13 or the like. It is not the actual free space that is not, but the total capacity of this background area.

The digital still camera 1 according to this embodiment configured to perform file management and present free space in this way is used by the user as follows, for example.
First, the user can store a still image and a captured image of a moving image as a file in the storage unit 16 using an imaging function which is an original function as a digital still camera.
At the same time, since the digital still camera 1 has a push-type distribution receiving function, for example, the user is in the area where the push-type distribution service is provided while the digital still camera 1 is moving. In this case, the push delivery file is automatically received and acquired and stored in the storage unit 16 as it is accumulated. As can be seen from the above description, the push delivery file is stored as being in the background area, and if the push delivery file fills the background area, it is assumed that it has been stored in the past. A new push delivery file can be stored by overwriting and erasing the push delivery file. In this way, the digital still camera 1 according to the present embodiment can accept, acquire, and hold information that is distributed by push. The user can know various information later by reproducing and outputting these push delivery files. In addition, as described with reference to FIGS. 3B and 3C, if the push delivery file is to be saved, an operation corresponding to saving confirmation is performed so that the push delivery file is treated as a regular file. can do.

In the situation where it is used as described above, the capacity of the background area at that time is presented to the user as the free capacity of the storage unit 16. This means that the free space presented to the user (hereinafter also referred to as user-presented free space) indicates the free space that can store the regular file. As can be understood from the description with reference to FIG. 2 and FIG. 3, the captured image file can be stored in practice as long as the user-presented free space has a margin, for example.
For example, if the list of files stored in the storage unit 16 is output to the display unit 13 or the like, in addition to the captured image file as a regular file (and a push delivery file that clearly indicates the necessity to save), Actually, a push delivery file managed as being stored in the background area is also presented. That is, the user is notified of the remaining capacity in which the regular file can be stored as the free space while indicating that not only the regular file but also the unconfirmed file is stored as the stored content. However, in practice, the free space can be stored with respect to the regular file in which the user clearly indicates the necessity for saving, and in this respect, the user-presented free space in the present embodiment. This is suitable for the free space that is sensibly grasped while the user is using it.

For example, if the storage unit 16 is managed by a conventional method, the area where the captured image file (regular file) and the unconfirmed file (push delivery file) are stored is collectively treated as a use area according to FIG. Then, after managing so that an area where no other data is recorded is handled as an unused area, the capacity of the unused area is presented as it is to the user as it is.
In this case, for example, if a large number of push delivery files are accumulated and there is no free space, no more regular files can be written. If a regular file is to be written, it becomes necessary to secure a free space by erasing a selected one of the stored captured image file and the push delivery file. The push delivery file is unilaterally transmitted, and the necessity for storage for the user is unknown at the time of acquisition. It is not efficient and the user feels that the storage capacity is compressed by such data and the above-described troublesome operations are not efficient.
On the other hand, if the storage unit 16 is managed as in the present embodiment, in reality, even when a large number of push delivery files are accumulated and there is no actual free space, it corresponds to the background area. As long as there is room in the user-provided free space, it is possible to record the captured image file (regular file) without being aware of the fact that there is no actual free space. In this way, the conventional disadvantages as described above are eliminated.

  Next, a technical configuration example related to the management mode of the storage unit 16 according to the present embodiment described with reference to FIGS. 2 and 3 will be described. First, the free capacity for the user according to the present embodiment is described. The presentation will be explained. Note that the configuration for presenting the free space to the user described here is merely an example to show the feasibility, and various other file management and capacity calculation methods can be considered.

First, in the digital still camera 1 according to the present embodiment, basic management of files stored in the user data area of the storage unit 16 is performed by a file system. Depending on the file system, regular files and unconfirmed files are handled as “files” without any particular distinction and managed. The file management information managed by this file system is the file system management information shown in FIG.
In order to manage unconfirmed files, an unconfirmed file list shown in FIG. 1 as being stored in the system area together with the file system management information is used. This unconfirmed file list has a structure shown in FIG. 4, for example.

As shown in FIG. 4, the unconfirmed file list has a structure in which items such as a file name, a size, a recording date / time, a last access date / time, and an access count are associated with each unconfirmed file list. An unconfirmed file managed by the file system and an unconfirmed file registered in the unconfirmed file list can be associated with each other by, for example, a file name.
Note that the structure of the unconfirmed file list shown in this figure is merely an example, and other combinations of types of items (attributes) per taste-determined file are conceivable.
Information such as the recording date and time and the last access date and time in the unconfirmed file list can be described using time information timed by the time management unit 21 in the control unit 15.

A specific example of file management based on the file system management information and the unconfirmed file list will be described with reference to FIG.
In this figure, the regular files D (1) and D (2) to D (n) are stored in the regular area and the unconfirmed files Db (1) and Db are stored in the remaining background area in the entire capacity of the user data area. A state in which (2) is stored is shown.
In the file system, as described above, these regular files D (2), D (2) to D (n) and undefined files Db (1), Db (2) are handled and managed as the same file. The stored capacity managed by this file system is indicated by section B. The free capacity managed by the file system is the capacity of section C obtained by subtracting the capacity of section B from the capacity of section A indicating the total capacity of the user data area. In this embodiment, the capacity of the section C is the same as the free capacity in the background area, that is, the actual free capacity.

  On the other hand, the capacity of the stored unconfirmed file managed by the unconfirmed file list corresponds to the sum of the sizes of the unconfirmed files Db (1) and Db (2). It becomes capacity.

In this case, the free capacity presented to the user is the capacity of the section E corresponding to the entire background area. Then, the capacity | capacitance of the area E can be represented by E = C + D, for example.
As described above, the capacity of the section C refers to, for example, the file system management information, for example, from the total capacity of the user data area (section A), the total of stored files (regular file and unconfirmed file list). It is obtained by subtracting the capacity (section B). The capacity of the section D is obtained by adding up the sizes of unconfirmed files registered in the unconfirmed file list. In this way, the information on the user-presented free space can be appropriately acquired using the file system management information and the unconfirmed file list. And the value of the user presentation free space acquired in this way is displayed on the display unit 13 in a predetermined display mode, for example. As a result, the user-presented free space is notified so as to be visible to the user.

  Next, file storage management according to the present embodiment will be described with reference to the flowcharts of FIGS. The procedure shown as a flowchart in this figure is, for example, a program that is stored in the ROM or the storage unit 16 in which the CPU that is the hardware component of the control unit 15 in FIG. It can be seen as being realized by loading and executing. As described above, such a program is written and stored in a ROM at the time of manufacture, for example, and is stored in a removable storage medium, for example, and then installed using this storage medium. Can be stored in the digital still camera 1. It is also conceivable that the data is stored in a storage device in a server on the network, acquired by downloading via the network, and installed in the digital still camera 1.

First, in FIG. 6, the process waits for an event to occur, and when an event occurs, the process proceeds to step S102 and subsequent steps.
In step S102, first, a determination is made as to whether or not the content of the event that has occurred in response to step S101 is automatic reception of push-type distribution. If a positive determination result is obtained, step S103 is skipped and the process proceeds to step S104. However, if a negative determination result is obtained, the process proceeds to step S103.

In step S103, it is determined whether or not the event content that has occurred in response to step S101 is an operation for accepting and receiving push-type delivery.
As described above, in the case of receiving push distribution, in this embodiment, the case of receiving completely automatically, and the case of receiving again after the operation of permission of acceptance by the user is once performed. There is. The event content that is the determination target in step S102 corresponds to the former, and the event content that is the determination target in step S103 corresponds to the latter.
If an affirmative result is obtained in step S103, the process proceeds to step S104 and subsequent steps. If a negative determination result is obtained, the process proceeds to step S110 in FIG.

When step S104 in FIG. 6 is reached, the digital still camera 1 has received and acquired data transmitted by push distribution via the network interface 14. For confirmation, the data received and acquired by push-type distribution is a push distribution file, and therefore should be handled as an unconfirmed file in the reception and acquisition stage.
In step S104, the free space in the background (BG) area (actual free capacity) is compared with the size of the push delivery file acquired by receiving the push delivery, and the free space in the background (BG) area. It is determined whether or not the capacity (indicated by section C in FIG. 5) is larger than the size of the push delivery file received and acquired.

First, in step S104, a negative determination result is obtained. In this case, there is not enough free space in the background area to record the newly received and received data (received push delivery file). It will be that.
In this case, whether or not a free space in which the received push delivery file can be written can be secured in the background area by deleting the undetermined file that has been stored in the background area at the current time in step S105. Determine whether or not.
For example, if the capacity of the background area at this time is larger than the size of the push delivery file, the free space for the received push delivery file can be secured by deleting the stored unconfirmed file. Therefore, a positive determination result is obtained as step S105. On the other hand, if the capacity of the background area at this time is smaller than the size of the push delivery file, the received push delivery file is completely stored even if all the unconfirmed stored files are deleted. Therefore, a negative determination result is obtained as step S105.

If a negative determination result is obtained in step S105, the process proceeds to step S108 to execute a process of canceling the storage of the data of the push delivery file received and acquired this time. That is, for example, the push delivery file data held in the RAM or the like provided in the control unit 15 is discarded, and the process returns to step S101.
On the other hand, if an affirmative determination result is obtained in step S105, the minimum number of unconfirmed files that can secure a free space are deleted in step S106. At this time, an unconfirmed file to be deleted is selected in accordance with a predetermined deletion order. There are several possible rules for determining the deletion order. For example, the oldest recording date can be associated with the oldest recording date and deleted from the oldest recording date. Or, it can be deleted in ascending order of access times, deleted from the oldest access date and time, or deleted in descending order of file size. Further, in order to delete an unconfirmed file in these examples, an unconfirmed file list as shown in FIG. 4 may be referred to.
In addition to the undetermined file deletion process in step S106, the process in the next step S107 is performed to update the file system management information and the undetermined file list according to the deletion process result. .
When the process of step S107 is completed, the process proceeds to step S109.

When the process of step S107 is completed or when a positive determination result is obtained in step S104, the process proceeds to step S109.
In step S109, a processing procedure for storing the data of the received push delivery file in the background area is executed. That is, the control unit 15 (CPU) transfers the data of the received push delivery file to the storage unit 16 and executes writing to the unused area. Then, the file system management information is updated so that the written data is managed as if one file was stored. The stored file is registered in the unconfirmed file list. Thereby, the push delivery file newly recorded this time is managed as being stored in the background area as an unconfirmed file.
When the process of step S109 is completed, the process returns to step S101.

Next, the flowchart of FIG. 7 will be described.
As described in FIG. 6, when a negative determination result is obtained in step S103, the process proceeds to step S110 in FIG.
In step S110, it is determined whether or not the event content generated in accordance with step S101 is a shooting operation for recording a captured image as a still image or a moving image, and a positive determination result is obtained. In step S111, the process skips step S111 and proceeds to step S112. However, if a negative determination result is obtained, the process proceeds to step S111.

In step S111, it is determined whether or not the event content generated in accordance with step S101 is acquisition of pull type data other than the captured image data. The pull-type data here refers to, for example, data acquired by the digital still camera 1 by performing an operation meaningful to be taken into the digital still camera 1 from the user himself / herself. Therefore, the data file of the captured image acquired by the shooting operation is also one of the pull type data. In the description so far, for convenience, only the captured image file has been cited as the pull-type data acquired by the digital still camera 1. However, in the configuration of the digital still camera 1 according to the present embodiment, it is possible to access a pull-type distribution service via the network interface 14 or the like and download data or the like. In such a case, the user will actively perform an operation for downloading the distribution data, and such data is included in the pull type. Alternatively, even if it is not a distribution service, data that is received and acquired by transfer from another terminal or the like connected via the network interface 14 also becomes a pull type.
In the present embodiment, such pull-type data is assumed to be data acquired by the digital still camera 1 by performing a meaningful operation that clearly indicates the necessity of storage from the beginning. It is handled as file data.

  If a positive determination result is obtained in step S111, the process proceeds to step S112. If a negative determination result is obtained, the process proceeds to step S118.

  Step S112 is executed when a positive determination result is obtained in step S110 or step S111. That is, step S112 is a process that is executed when an event that acquires data handled as a regular file occurs.

At the stage of reaching step S112, captured image file data (in the case of a moving image, a certain amount of data is sequentially held) or pull-type data is acquired as the regular file data. It is in a state held in RAM or the like. Therefore, in step S112, it is determined whether or not the data size held in this way is less than or equal to the actual free space in the user data area of the storage unit 16. The actual free space is the same as the free space in the background area as shown as section C in FIG.
If an affirmative determination result is obtained in step S112, the data of the regular file can be recorded with respect to the actual free space at that time. Therefore, steps S113 to S115 are skipped and the process proceeds to step S117.
On the other hand, if a negative determination result is obtained in step S112, the processing after step S113 is executed to secure free space.

  When writing regular file data, the automatic deletion of data stored as an indeterminate file is executed when free space is secured in accordance with the state where the actual free space is insufficient. The stored regular files are not automatically deleted. This is because, as described above, due to the nature of the regular file, if it is automatically deleted unnecessarily, the loss of the user is large. A regular file is a file that is not suitable for automatic deletion unless there is an operation for clearly indicating the intention of deletion by the user.

Therefore, depending on Steps S113 to S115 and Step S116, a process of deleting the stored unconfirmed file is executed as a process for securing a free space enough to write data of the regular file.
The processes in steps S113 to S115 and step S116 are the same as steps S105 to S107 and step S108 in FIG.

  In step S117, control processing for storing the acquired captured image file data or other pull-type data in the storage unit 16 so as to be managed as a regular file is executed. That is, for example, the recording data held in the RAM is transferred to the storage unit 16 to be written and stored, and the file system management information is appropriately updated according to the data writing result. When the data writing as the regular file in step S117 is completed, the process returns to step S101.

  When a negative determination result is obtained in step S111, the process proceeds to a different event content determination. First, in step S118, it is determined whether or not the event content generated in accordance with step S101 is an operation for changing a stored unconfirmed file to a regular file, and a positive determination result is obtained. If so, the process proceeds to step S119. In step S119, the undetermined file designated as the change target by the operation is deleted from the undetermined file list. By such file operation processing, the present embodiment is changed so that the unconfirmed file is managed as a regular file. In other words, by canceling the registration from the unconfirmed file list, the file is no longer managed as an unconfirmed file, and normal file management is performed using only file system management information. For example, as can be understood from the above description with reference to FIG. 5 and the like, such a file is handled as a regular file.

If a negative determination result is obtained in step S118, the process proceeds to step S120.
In step S120, it is determined whether or not the event content generated in accordance with step S101 is an operation for deleting an indeterminate file. If a positive determination result is obtained, the process proceeds to step S121. move on.
In step S121, the file system management information is updated so that the unconfirmed file designated as the deletion target is managed as deleted. At the same time, the unconfirmed file designated as the deletion target is deleted from the unconfirmed file list.

  If a negative result is obtained in step S120, the process proceeds to step S122, and a required process corresponding to the content of the event that has actually occurred is executed.

FIG. 8 shows a modification of the present embodiment.
As described in the above embodiment, an unconfirmed file stored in the background area can be managed as being stored in the normal area after being changed to a normal file, for example, according to a user operation. it can. For this purpose, it is possible, for example, by rewriting the unconfirmed file list. On the basis of this, on the contrary, it is possible to change a regular file to an unconfirmed file. Become. For this purpose, for example, the regular file to be changed is registered in the unconfirmed file list. That is, in the present embodiment, the information stored in the storage unit 16 can be changed from an unconfirmed file to a regular file and from a regular file to an unconfirmed file.

Utilizing this fact, as a modification, a form of use of the storage unit 16 as shown in FIG. 8 can be considered.
In this modified example, the definition of the indeterminate file is not particularly different from the previous examples, but the specific meaning of the definition is provisionally deleted from the user data area instead of the push delivery file or the like. File. For example, in a personal computer that employs the current GUI, even if a file deletion operation is performed, the file entity is not deleted from the HDD, and is temporarily saved in an area called “trash can”. Be made. As long as the file that is supposed to be in the trash box remains without being deleted from the trash box, it can be restored again from the trash box to a predetermined directory in the normal use area.

  As a modification of the present embodiment shown in FIG. 8, the regular area is treated as a normal use area and the background area is treated as a trash can area. For example, in FIG. 8A, files D (1)... D (n-1) and D (n) are managed as being stored for the regular area (normally used area). From this state, for example, if an operation of specifying the file D (n-1) and moving to the trash box is performed, the file D (n-1) changes from FIG. 8 (a) to FIG. 8 (b). As shown in FIG. 6, the data is managed as being stored in the background area, which is a storage area as a trash can, from the state stored in the normal area, which is the normal use area. On the other hand, if an operation for returning the file D (n−1), which is assumed to be in the trash box, to the normal use area is performed, the transition from FIG. 8B to FIG. 8A is shown. Thus, the state managed as being in the background area, which is a trash box, is changed to the normal management area, which is stored in the normal area. As can be understood from the above description, such a change can be realized by changing the contents of the unconfirmed file list on the assumption that file management is performed by the file system.

  Even when the background area is handled as a trash can in this way, the user-present free space is the size of the background area. In this case, the user-present free space indicates the capacity of an area other than the normal use area in the user data area, and is suitable for the actual user's sense of use.

In the embodiment described so far, a storage area other than the normal area in the user data area is assumed to be the background area. That is, the background area increases or decreases according to the capacity of the normal area. However, as another area management mode, it may be possible to determine the upper limit of the capacity of the background area. The background area in this case has a used capacity corresponding to the total capacity of the unconfirmed files to be stored in the same manner as the regular area. Therefore, in this case, the user data area is not managed so that the actual free space is included, but is divided into three areas: a normal area, a background area, and an actual free area. Will be managed. For example, in the user data area, when a regular area, a background area, and an actual empty area are formed, a new regular file is added. Storage is performed using the free area. In this way, the actual free space is used for storing the new regular file, and when it is assumed that the capacity of the actual free space for storing the new regular file is insufficient at a certain stage, From time to time, a capacity for storing new regular files is secured from the background area.
When the upper limit capacity of the background area is set in this way, for example, when an unconfirmed file is stored and the capacity of the background area reaches the upper limit, no more indeterminate files are stored. It is possible to consider a file management configuration in which new storage is not performed. For example, depending on the user's way of thinking and circumstances, it may be considered that it is not preferable to overwrite an indeterminate file indefinitely. It is useful not to execute new storage of the definite file.

Further, the present invention is not limited to the configuration as the embodiment described so far. For example, regarding the configuration of the digital still camera 1 shown in FIG. 1, for example, some of the various functions realized by the control unit 15 executing a program are configured based on hardware other than the control unit 15. It is possible to do. Various examples of management of regular files and unconfirmed files can be considered other than the combination of the file system and the unconfirmed file list described in the above embodiment. Furthermore, other algorithm procedures relating to file recording shown in FIGS. 6 and 7 can be considered.
Furthermore, as a device to which the present invention is applied, various devices such as a mobile phone, a video camera, a portable audio player, and a DVD player can be considered in addition to a digital still camera. In the embodiment, the regular data and unconfirmed data in the present invention are respectively taken as a captured image file and data distributed by push-type distribution. For example, the definition of regular data and unconfirmed data is defined as follows. There is no particular limitation as long as the data and files have characteristics that satisfy each of them.

It is a block diagram which shows the structural example of the digital still camera as embodiment of this invention. It is a figure for demonstrating the example of a basic management aspect of the regular file in embodiment. It is a figure for demonstrating the example of a management aspect of a regular file and an undetermined file in embodiment. It is a figure which shows the example of a structure of an undetermined file list. It is a figure which shows the capacity | capacitance relationship between area | regions in a user data area. It is a flowchart which shows the process sequence for the file recording of embodiment, file management setting, etc. It is a flowchart which shows the process sequence for the file recording of embodiment, file management setting, etc. It is a figure for demonstrating the modification of embodiment. It is a figure which shows the example of management of the storage area in the past.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 Digital still camera, 11 Imaging information input part, 12 Operation part, 13 Display part, 14 Network interface, 15 Control part, 16 Storage part, 20 Data signal processing part, 21 Time management part, 22 Display control part, 23 Data operation Processing unit, 24 File system management unit, 25 Storage area management unit, 26 Unconfirmed file management unit

Claims (8)

The data stored in the storage medium is classified into regular data, which is data for which the user clearly indicates the necessity for storage, and unconfirmed data, which is unconfirmed data as to whether or not this regular data should be used. Classification means;
The storage area in the storage medium is managed by dividing at least a normal data area formed by a normal data stored area and an indeterminate data area capable of storing indeterminate data, and the normal data When newly storing in the storage medium, an area having a capacity capable of storing the newly stored regular data is secured from the storage area other than the regular data area in the storage medium, and the secured area is stored in the secured area. A storage management control means for performing writing of regular data to be newly stored and managing the written area to be included in the regular data area;
An information processing apparatus comprising: Further comprising presentation means for presenting the capacity of the unconfirmed data area in the storage medium, including the free capacity of the storage medium.
The information processing apparatus according to claim 1. Push type distribution data acquisition means for receiving and acquiring push type distribution data, which is data sent by push type distribution,
The classification means classifies the push-type distribution data acquired by the push-type distribution data acquisition means as the unconfirmed data.
The information processing apparatus according to claim 1. A captured image acquisition unit that captures captured image data obtained by imaging and performs imaging,
The classification unit classifies the captured image data acquired by the captured image acquisition unit as the regular data.
The information processing apparatus according to claim 1. The storage management control means includes
Changing the unconfirmed data stored in the unconfirmed data area of the storage medium to normal data stored in the normal data area;
Alternatively, the data stored in the storage medium in such a manner that the normal data stored in the normal data area of the storage medium is changed to unconfirmed data stored in the unconfirmed data area. Can be managed,
The information processing apparatus according to claim 1. The storage management control means includes
In response to an operation for deleting regular data, the regular data stored in the regular data area of the storage medium is changed to unconfirmed data stored in the undefined data area. Perform management,
In accordance with an operation for restoring the deleted regular data to the non-deleted regular data, the unconfirmed data stored in the unconfirmed data area of the storage medium is Execute management of data to be changed to regular data stored in the regular data area,
The information processing apparatus according to claim 5. The data stored in the storage medium is classified into regular data, which is data for which the user clearly indicates the necessity for storage, and unconfirmed data, which is unconfirmed data as to whether or not this regular data should be used. Classification procedure;
The storage area in the storage medium is divided and managed by a normal data area formed by a stored area of normal data and an indeterminate data area capable of storing indeterminate data, and the normal data is When newly storing data in a storage medium, an area having a capacity capable of storing the newly stored normal data is secured from a storage area other than the normal data area in the storage medium, and a new area is stored in the reserved area. A storage management control procedure, in which regular data stored in is written, and the area in which this writing is performed is managed to be included in the regular data area;
The information processing method characterized by performing. The data stored in the storage medium is classified into regular data, which is data for which the user clearly indicates the necessity for storage, and unconfirmed data, which is unconfirmed data as to whether or not this regular data should be used. Classification procedure;
The storage area in the storage medium is divided and managed by a normal data area formed by a stored area of normal data and an indeterminate data area capable of storing indeterminate data, and the normal data is When newly storing data in a storage medium, an area having a capacity capable of storing the newly stored normal data is secured from a storage area other than the normal data area in the storage medium, and a new area is stored in the reserved area. A program for causing the information processing apparatus to execute a storage management control procedure for writing regular data stored in the storage area and managing the written area to be included in the regular data area. .

Images