Imaging device, control method thereof, and program

Abstract

To provide an imaging apparatus that can perform appropriate transfer management even when the number of images is increased, which are managed in terms of transfer to a finite resource.SOLUTION: An imaging apparatus comprises: a recording unit that records picked-up images in a recording medium; and a transfer unit that transfers the images recorded in the recording medium to an external device. The recording unit records, in the recording medium, management data for managing the state of transfer of the images to the external device performed by the transfer unit, as data for every folder of the images recorded in the recording medium.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a technique for managing a transfer state when a captured image is transferred to an external device. [Background technology]

[0002] In recent years, with the increase in network transfer speed, imaging devices have been developed that transfer captured images to external devices via a network, either automatically or manually. The external devices to which images are to be transferred can be a variety of devices, such as FTP (File Transfer Protocol) servers and smartphones.

[0003] Such imaging devices often have a function for managing image transfer so that the user can know that an image has been transferred to an external device. For example, when an image is transferred to a smartphone and the transfer is successful, an imaging device is known that displays a message indicating that the transfer has been successful when the image that has been transferred is played back on the imaging device.

[0004] Various techniques have been proposed for controlling the above-mentioned image transfer management, including a method of writing the transfer status to the header of an image file and a method of managing information related to image transfer management in a separate file.

[0005] Patent Document 1 discloses the following technology. That is, when an image is sent from a server to a client, the transmission history is updated and the list of transmission histories is sent from the server to the client. The client looks at the list of transmission histories sent from the server and requests the sending of files other than files that have already been received.

[0006] Patent Document 2 discloses the following technology. That is, in a mobile terminal, changes to stored image files and directories in which image files are saved are monitored, and if any changes are detected, the detected changes are reflected in a log file. The log file is sent to other devices for use. [Prior art documents] [Patent documents]

[0007] [Patent Document 1] JP 2009-086800 A [Patent Document 2] Special Publication No. 2014-526103 Summary of the Invention [Problem to be solved by the invention]

[0008] However, the above-mentioned patent documents are silent about transfer management control of finite resources (eg, RAM) when a large amount of images are transferred in a case where transfer management data is managed as a separate file.

[0009] The present invention has been made in consideration of the above-mentioned problems, and its object is to provide an imaging device that is capable of performing appropriate transfer management even when the number of images to be transferred increases with finite resources. [Means for solving the problem]

[0010] The imaging device of the present invention comprises a recording means for recording an image captured on a recording medium, and a transfer means for transferring the images recorded on the recording medium to an external device, and the recording means records management data for managing the transfer status of images to the external device by the transfer means on the recording medium as data for each folder of images recorded on the recording medium. Effect of the Invention

[0011] According to the present invention, even when the number of images to be transferred is increased, it is possible to perform appropriate transfer management with limited resources. [Brief description of the drawings]

[0012] [Figure 1] 1 is a block diagram showing the configuration of an imaging apparatus according to a first embodiment of the present invention. [Diagram 2] FIG. 11 is a diagram showing an example of a screen display for performing a selection process of an image to be transferred; [Diagram 3] 5 is a flowchart showing control for managing transfer management data in the first embodiment. [Figure 4] FIG. 4 is a diagram showing a structure of transfer management data in the first embodiment. [Diagram 5] 10 is a flowchart showing control for managing transfer management data in the second embodiment. [Figure 6] FIG. 11 is a diagram showing the structure of transfer management data in the second embodiment. [Figure 7] 13 is a flowchart showing control for managing transfer management data in the third embodiment. [Figure 8] FIG. 13 is a diagram showing a structure of transfer management data in the third embodiment. [Figure 9] 13 is a flowchart showing control for managing transfer management data in the fourth embodiment. [Figure 10] FIG. 13 is a diagram showing the structure of transfer management data in the fourth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] Hereinafter, the embodiments will be described in detail with reference to the attached drawings. Note that the following embodiments do not limit the invention according to the claims. Although the embodiments describe a number of features, not all of these features are essential to the invention, and the features may be combined in any manner. Furthermore, in the attached drawings, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.

[0014] (First embodiment) FIG. 1 is a block diagram showing the configuration of an image capturing apparatus 100 according to a first embodiment of the present invention.

[0015] 1, the photographing lens 101 is composed of a fixed focal length lens, a zoom lens, etc., and forms an image of a subject. The image sensor 102 is composed of a CCD, a CMOS sensor, etc., and converts the subject image formed by the photographing lens 101 into an electrical signal. The A / D converter 103 converts the analog output signal of the image sensor 102 into a digital signal.

[0016] The microcomputer 104 controls each component, processes data, and controls the entire imaging device 100. For example, it controls each part based on an operation instruction from the operation member 110, generates an image to be displayed on the display member 109, and controls the network via the communication member 108. It also selects an image to be transferred, transfers the image to an external device, refers to and updates the transfer management data, controls the reading of the transfer management data from the recording medium 111 to the volatile memory 105, and controls the writing of the transfer management data from the volatile memory 105 to the recording medium 111.

[0017] The volatile memory 105 temporarily stores image data converted into a digital signal by the A / D converter 103. Data for transfer management described in this embodiment is also stored here, and is referenced, updated, and the like by the microcomputer 104. The non-volatile memory 106 stores a control program for the imaging device executed by the microcomputer 104. The non-volatile memory 106 also stores setting values ​​for the imaging device.

[0018] The image processing unit 107 performs image processing on the captured image. The communication member 108 is, for example, a communication member for a communication technology such as a wireless LAN. Regarding the communication technology, either a wired connection or a wireless connection may be used. Although a technology such as FTP (File Transfer Protocol) transfer is assumed, other existing technologies may also be used.

[0019] The display member 109 is controlled by the microcomputer 104, and displays a menu, plays images, and the like. The operation member 110 performs operations on the menus and the like displayed on the display member 109. The operation member is assumed to be an operation member such as a key or a touch panel. The recording medium 111 is assumed to be, for example, a CF card or an SD card. Using the microcomputer 104, data in the volatile memory 105 can be written to the recording medium 111, or data stored in the recording medium 111 can be read out to the volatile memory 105.

[0020] Hereinafter, the transfer management in this embodiment will be described while showing a process for selecting an image to be transferred and a process for displaying an image for which transfer has failed as an example of a function for handling transfer management data.

[0021] FIG. 2 is a diagram showing an example of a screen display for selecting an image to be transferred. The explanation will be given on the assumption that "IMG_0001.jpg" is stored in the recording medium 111. A screen 200 shows the screen of the display member 109 in which an image stored in the recording medium 111 is reproduced by the imaging device 100. "IMG_0001.jpg" is being reproduced. The user sets which image to transfer while looking at the displayed image. As an operation method, it is assumed that the touch panel, keys, etc. of the operation member 110 are used. An area 201 is an area showing the state of transfer management, including information such as whether the displayed image is a transferred image.

[0022] Image transfer management will now be described. Transfer management refers to a state in which transfer-related status, such as whether the image is to be sent, whether it is an image that has already been sent, or whether transfer has failed, is associated with the image and managed. For example, when a user selects an image displayed on screen 200 as an image to be transferred, the image is managed as being in a "selected" state in terms of transfer management. An indication of transfer management such as "selected" is, for example, a display such as a "R" indicator 202. When a selected image indicated by indicator 202 exists, the user can select transfer to send the image in the "selected" state to the transfer destination.

[0023] An explicit button such as the transfer start button 203 may be prepared and the transfer may be started by pressing the transfer start button 203, or the transfer may be started when the indicator 202 is placed in a selected state. The timing and conditions for starting this transfer are conventionally known techniques, and any method may be used.

[0024] Transfer is started by operating the transfer start button 203, and when the transfer is completed, the image is managed as being in a "transferred" state in the image management. For example, a "○" indicator 204 is displayed to notify the user that the image has been transferred.

[0025] An explanation will also be given of images with transfer failures. When a transfer is instructed by pressing the transfer start button 203 and an image is to be transferred to the transfer destination, if a network error or the like occurs and the image cannot be sent normally to the transfer destination, the image that was to be transferred is managed as an image with transfer failures. For example, the user can be notified of the transfer failure by displaying an "x" indicator 205.

[0026] So far, a method for selecting whether or not to transfer one image displayed on the display member 109 has been described, but a screen such as menu 206 may be displayed to provide the user with options for selecting multiple images at once. Image selection is assumed to be possible using known technology.

[0027] Next, the data structure and control for managing the above transfer status will be explained. An example of the transfer management data is shown in 207.

[0028] For each image file, the transfer status to each transfer destination is recorded. As shown in 207, assuming that the transfer destinations are an FTP server and a smartphone, the transfer status to each is recorded.

[0029] For example, in 207, image IMG_0001 means that the transfer to the FTP server has been completed, but the transfer to the smartphone has not been completed yet. Here, the transfer status to the transfer destination assumed for each image is stored, but in this embodiment, the structure of the transfer management data is assumed to be one that can be provided by known technology.

[0030] Next, the destination where the transfer management data is saved will be described. In this embodiment, a method is assumed in which the transfer management data is saved in a file format. An example of a folder structure when the captured image is stored in the recording medium 111 by the imaging device 100 is shown in 208.

[0031] The DCIM folder exists directly under the recording medium 111. The image IMG_0001.jpg shown at 209 is an image stored under the 100IMAGE folder.

[0032] For example, when the transfer management data as shown in 207 is managed on a per-photography folder basis, images stored in the 100IMAGE folder or below are handled as one transfer management file. Also, when a photo image exists in the 101IMAGE folder or below as shown in 210, it is handled as a separate transfer management file.

[0033] The units and methods for generating the transfer management file will be explained in more detail later. The transfer management file itself is also stored in the recording medium 111, and is controlled so that it is read out to the volatile memory 105 at the necessary timing, the transfer management data in the volatile memory 105 is referenced and updated, and written back to the recording medium 111.

[0034] As for the location where the transfer management file is saved in the recording medium 111, for example, one method is to record it in the same folder as the captured image. As a specific example, the transfer management data of images saved in the 100IMAGE folder or below is saved in the 100IMAGE folder or below. As another method, a control method may be considered in which a folder dedicated to transfer management data is generated. For example, as shown in 211, a folder called TRANS for saving the transfer management data may be generated in the DCIM folder and the data may be saved there. In this embodiment, there are no particular limitations on the location or method for recording the transfer management data.

[0035] Fig. 3 is a flowchart showing the control of managing transfer management data for each folder in which captured images are saved. The operation of the flowchart in Fig. 3 is realized by the microcomputer 104 expanding a control program stored in the non-volatile memory 106 into the volatile memory 105 and executing it. This also applies to the flowcharts in the second and subsequent embodiments.

[0036] In the following description, it is assumed that the images and transfer management data files stored in the recording medium 111 are in a state as shown in 400 in FIG. 4. Specifically, IMG_0001.jpg, IMG_0002.jpg, and IMG_0003.jpg are stored in the 100IMAGE folder and the 101IMAGE folder, respectively. Transfer management files 100_Trans and 101_Trans exist under the TRANS folder, and these transfer management files manage the images stored in the 100IMAGE folder and the 101IMAGE folder, respectively, on a folder-by-folder basis. The contents of the transfer management data of the transfer management file 100_Trans are shown in 401. The contents of the transfer management data of the transfer management file 101_Trans are shown in 402. It is assumed that the data of the transfer management file 100_Trans is read into the volatile memory 105, and the data of the transfer management file 101_Trans is not read into the volatile memory 105.

[0037] First, in step S300, the microcomputer 104 determines whether a process that requires updating of the transfer management data has been performed. Processes that require updating of the transfer management data include the above-mentioned cases where a process of selecting an image as a transfer target has been performed, where the transfer of an image has been completed, or where the transfer of an image has failed. In this embodiment, as shown in 403 in Fig. 4, a process in which the transfer of IMG_0002.jpg in the 101IMAGE folder to the FTP server has been completed will be described as an example.

[0038] In step S300, if a process that requires updating of the transfer management data has been performed, the microcomputer 104 advances the process to step S301, and if not, repeats the process of step S300.

[0039] In step S301, the microcomputer 104 identifies a folder in which an object for which transfer management data is to be updated is recorded. In this embodiment, since it is desired to update the transfer management data of IMG_0002.jpg in the 101IMAGE folder, the 101IMAGE folder is the relevant folder.

[0040] In step S302, the microcomputer 104 checks whether or not the transfer management file 101_Trans of the relevant folder, i.e., the 101IMAGE folder, has been read into the non-volatile memory 105. If it has been read, the microcomputer 104 advances the process to step S304, and if it has not been read, the microcomputer 104 advances the process to step S303.

[0041] Here, as described above, the data of the transfer management file 101_Trans has not been read out to the volatile memory 105, so the determination in step S302 is No, and the process proceeds to step S303.

[0042] In step S303, the microcomputer 104 reads the transfer management file of the corresponding folder from the recording medium 111 to the volatile memory 105. Specifically, the data of the transfer management file 101_Trans of 400 in FIG. 4 is read to the volatile memory 105. The transfer management file read to the volatile memory 105 is assumed to be in the state of 402.

[0043] In step S304, the microcomputer 104 updates the transfer management file of the corresponding folder.

[0044] In this example, since the transfer of IMG_0002.jpg in the 101IMAGE folder to the FTP server has been completed, the area managing the transfer status of IMG_0002.jpg to the FTP server is updated from "not transferred" to "transfer completed" as shown in 403 in FIG. 4.

[0045] In step S 305 , the microcomputer 104 writes the transfer management file of the corresponding folder to the recording medium 111 .

[0046] Specifically, the data of the transfer management file 101_Trans that was read into the volatile memory 105 in step S303 and updated in step S304 is written under the TRANS folder of the recording medium 111.

[0047] By recording the transfer management data as a file in the recording medium 111 in step S305, it becomes possible to store the transfer management data even if the power of the image capture device 100 is turned off.

[0048] In step S306, the microcomputer 104 checks whether or not the power supply to the imaging device 100 has been turned off. If the power supply has been turned off, the microcomputer 104 performs a process to terminate the imaging device 100. If the power supply has not been turned off, the process returns to step S300 and waits for the process to update the transfer management data.

[0049] According to this embodiment, it is possible to manage transfer management data for each folder in which captured images are saved. By managing the data for each folder, when expanding the data in the volatile memory 105, it is sufficient to prepare a volatile memory 105 according to the number of captured images that can be saved in the folder. Therefore, when using limited resources, it is possible to provide a transfer management function even if the number of images to be transferred is increased, and it is possible to prevent a decrease in user operability.

[0050] Second embodiment FIG. 5 is a flowchart showing the control for generating a transfer management file for each predetermined number of images in the second embodiment.

[0051] An example in which transfer management data is generated as a file for each predetermined number of images will be described below.

[0052] Here, it is assumed that the captured image and the transfer management file are stored in the recording medium 111 in a state as shown in 600 in FIG.

[0053] Specifically, a total of 9999 images, IMG_0001.jpg to IMG_9999.jpg, are stored in the 100IMAGE folder. In the first embodiment, images in one folder are managed as one transfer management file, but in the second embodiment, a transfer management file is generated for each predetermined number of images.

[0054] The predetermined number may be any number and may be determined in any way. In this embodiment, the number of images that can be saved in one folder is set to 9999, so one transfer management file is generated for half that number, or 5000 images. Examples of transfer management data for images in the 100IMAGE folder are shown in 601 and 602.

[0055] Numeral 601 indicates the transfer status of images 0001 to 5000 in the 100IMAGE folder, which are recorded in the TRANS folder with the file name 100_Trans_A. Numeral 602 indicates the transfer status of images 5001 to 9999 in the 100IMAGE folder, which are recorded in the TRANS folder with the file name 100_Trans_B.

[0056] The second embodiment will be described by taking as an example a case where the transfer of IMG_9999.jpg in the 100IMAGE folder to the FTP server is completed from the above states 600, 601, and 602. Note that the description will be given on the assumption that the transfer management file 100_Trans_B has not been read out to the volatile memory 105.

[0057] In step S500, the microcomputer 104 determines whether or not a process that requires updating of the transfer management data has been performed. In this embodiment, the case where the transfer of IMG_9999.jpg in the 100IMAGE folder to the FTP server has been completed is taken as an example.

[0058] In step S501, the microcomputer 104 checks the number of transfer management items managed by one transfer management file. In this embodiment, the number is set to 5,000.

[0059] In step S502, the microcomputer 104 determines the transfer management file in which the transfer management data of the object for which the transfer management data is to be updated is stored.

[0060] Here, we want to update the transfer management data for IMG_9999.jpg in the 100IMAGE folder, so we check which transfer management file that corresponds. The number of transfers managed by one transfer management file is 5000, and the image number is 9999, so we can see that the corresponding transfer management file is 100_Trans_B.

[0061] In step S503, the microcomputer 104 checks whether or not the transfer management file has been read into the volatile memory 105. If the file has been read, the microcomputer 104 advances the process to step S505, and if the file has not been read, the microcomputer 104 advances the process to step S504.

[0062] As described above, since the transfer management file 100_Trans_B has not been read out to the volatile memory 105 here, the result of step S503 is determined as No, and the process proceeds to step S504.

[0063] In step S 504 , the microcomputer 104 reads the transfer management file 100 _Trans_B from the recording medium 111 to the volatile memory 105 .

[0064] In step S505, the microcomputer 104 updates the transfer management data of the corresponding transfer management file. As shown in 603 in Fig. 6, the area in the transfer management file 100_Trans_B that manages the transfer status of IMG_9999.jpg to the FTP server is updated from "not transferred" to "transfer completed".

[0065] In step S 506 , the microcomputer 104 writes the corresponding transfer management file to the recording medium 111 .

[0066] In step S507, the microcomputer 104 checks whether or not the power of the imaging device 100 has been turned off. If the power has been turned off, the microcomputer 104 performs a process to terminate the imaging device 100. If the power has not been turned off, the process returns to step S500 and waits for the process of updating the transfer management data to be performed.

[0067] According to this embodiment, it is possible to generate a transfer management file for each predetermined number of images. By generating a transfer management file for each predetermined number of images, it is possible to adjust the memory size when expanding in the volatile memory 105. As a result, when using limited resources, it is possible to provide a transfer management function even if the number of images to be transferred is increased, and it is possible to prevent a decrease in user operability.

[0068] (Third embodiment) FIG. 7 is a flowchart for explaining the control of dividing the transfer management data in one file into folder units, reading the transfer management data from the recording medium for each folder division, and further writing the data to the recording medium in the third embodiment.

[0069] Here, it is assumed that the captured image and the transfer management file are stored in the recording medium 111 in a state as shown in 800 in FIG.

[0070] Specifically, a total of 9999 images, IMG_0001.jpg to IMG_9999.jpg, are stored in the 100IMAGE folder. Similarly, a total of 9999 images, IMG_0001.jpg to IMG_9999.jpg, are stored in the 101 to 104IMAGE folders, respectively.

[0071] Furthermore, although the transfer management data is managed as a file, in this embodiment the transfer management data for all images is managed as one transfer management file.

[0072] An example of the data structure of a transfer management file is shown in 801. The delimiters are made clear for each folder. An example will be described in which the transfer of IMG_5000.jpg in the 102IMAGE folder to the FTP server has been completed from this state. Note that the transfer management data relating to the images in the 102IMAGE folder is assumed not to have been read out to the volatile memory 105.

[0073] In step S700, the microcomputer 104 determines whether or not a process that requires updating of the transfer management data has been performed. In this embodiment, the case where the transfer of IMG_5000.jpg in the 102IMAGE folder to the FTP server has been completed is taken as an example.

[0074] In step S701, the microcomputer 104 identifies the folder in which the object for which the transfer management data is to be updated is recorded. In this example, since the transfer management data of IMG_5000.jpg in the 102IMAGE folder is to be updated, the 102IMAGE folder is the relevant folder.

[0075] In step S702, the microcomputer 104 checks whether or not the transfer management data of the relevant folder, i.e., the 102IMAGE folder, has been read into the non-volatile memory 105. If the data has been read, the microcomputer 104 advances the process to step S704, and if the data has not been read, the microcomputer 104 advances the process to step S703.

[0076] As described above, the transfer management data in the 102IMAGE folder has not yet been read out to the non-volatile memory 105, so the determination in step S702 is No, and the process proceeds to step S703.

[0077] In step S703, the microcomputer 104 reads the transfer management data of the corresponding folder from the recording medium 111 to the volatile memory 105. At this time, as shown in 801, since there is one transfer management file, if the size of the transfer management file is large, it may not be possible to read all of the data into the volatile memory 105. Therefore, only the data corresponding to the 102IMAGE folder of the data 801 in the recording medium 111 is read from the recording medium 111 and placed in the volatile memory 105. 802 shows this state.

[0078] In step S704, the microcomputer 104 updates the transfer management data for the object. In this embodiment, since the transfer of IMG_5000.jpg in the 102IMAGE folder to the FTP server is complete, the area that manages the transfer status of IMG_5000.jpg to the FTP server is updated from "not transferred" to "transfer completed" as shown in 803.

[0079] In step S705, the microcomputer 104 writes the transfer management data of the folder in question to the recording medium 111. At this time, the transfer management data 803 is written back to the position where it was read from the recording medium 111 in step S703.

[0080] In step S706, the microcomputer 104 checks whether or not the power of the imaging device 100 has been turned off. If the power has been turned off, the microcomputer 104 performs a process to terminate the imaging device 100. If the power has not been turned off, the process returns to step S700 and waits for the process to update the transfer management data.

[0081] According to this embodiment, by dividing the transfer management data in one file into folders, it becomes possible to read the transfer management data from the recording medium or write the data to the recording medium in folder division units. By handling the data in folder units, when expanding the data in the volatile memory 105, the volatile memory 105 may be prepared according to the number of shots that can be saved in the folder. Therefore, when using limited resources, it is possible to provide the transfer management function even if the number of images to be transferred is increased, and it is possible to prevent a decrease in user operability.

[0082] In the present embodiment, an example has been described in which image transfer data is divided by folder, read from the recording medium 111 to the volatile memory 105, and written from the volatile memory 105 to the recording medium 111. However, the unit for dividing the data may be other than the folder. For example, as in the second embodiment, a certain number of images may be determined, and the data may be divided by that number of images. The method for dividing the data is not particularly limited.

[0083] (Fourth embodiment) FIG. 9 is a flowchart for explaining control of transfer management data in which a folder that is assumed to be more likely to be accessed has priority when managing transfer management data for each folder in the fourth embodiment.

[0084] Here, it is assumed that the captured image and the transfer management file are stored in the recording medium 111 in the state shown in 1000 of FIG.

[0085] Specifically, a total of 9999 images, IMG_0001.jpg to IMG_9999.jpg, are stored in the 100 to 103IMAGE folders, respectively. IMG_0001.jpg to IMG_0003.jpg are stored in the 104IMAGE folder.

[0086] The imaging device has a function of playing back images. When a playback instruction is received, the image to be played back also has a function of displaying the most recent captured image. In this embodiment, the playback image will be described on the assumption that the most recent captured image is played back. When a new image is captured, it is saved as IMG_0004.jpg in the 104IMAGE folder. It is also assumed that transfer management files 100_Trans to 104Trans for managing the transfer status for each folder are present in the recording medium 111 as transfer management files that store the transfer management data of the captured images.

[0087] Furthermore, in this embodiment, it is assumed that when the transfer management data is read from the recording medium 111 to the volatile memory 105, a plurality of volatile memories 105 are prepared (the volatile memory 105 has a plurality of storage areas). An example is shown in 1001. 1001 shows a state in which an area is prepared in the volatile memory 105 so as to hold three pieces of transfer management data to be read from the recording medium 111. The following describes an example of the process when IMG_0001.jpg in the 100IMAGE folder, IMG_0002.jpg in the 101IMAGE folder, and IMG_0003.jpg in the 102IMAGE folder are transferred to the FTP server from this state.

[0088] In step S900, the microcomputer 104 specifies a folder in which to save the newly captured image. In this embodiment, as described above, the newly captured image is saved in the 104IMAGE folder as IMG_0004.jpg, so in step S900, the folder is the 104IMAGE folder.

[0089] In step S901, the microcomputer 104 reads out to the volatile memory 105 the transfer management data of the folder in which the newly captured image is to be saved (here, the 104IMAGE folder).

[0090] In step S902, the microcomputer 104 reads the transfer management file 104_Trans from the recording medium 111 to the volatile memory 105. The state of the volatile memory 105 at that time is shown in 1002. Of the three surfaces of the volatile memory 105, one surface is in use by the data of the transfer management file 104_Trans.

[0091] In step S902, the microcomputer 104 determines whether or not a process that requires updating the transfer management data has been performed. If a process that requires updating the transfer management data has been performed, the microcomputer 104 proceeds to step S903, and if not, repeats step S902.

[0092] In this embodiment, it is assumed that IMG_0001.jpg in the 100IMAGE folder is transferred to the FTP server in step S902.

[0093] In step S903, the microcomputer 104 identifies the folder containing the object for which the transfer management data is to be updated. In this example, this is 100IMAGE.

[0094] In step S904, the microcomputer 104 checks whether or not the transfer management data of the folder has been read out to the volatile memory 105. If the data has been read out, the microcomputer 104 advances the process to step S905, and if not, the microcomputer 104 advances the process to step S908.

[0095] In the state of 1002 for the volatile memory 105, the transfer management file 100_Trans in which the transfer management data of 100IMAGE is managed as a file has not been read out to the volatile memory 105. Therefore, step S904 is judged as No, and the process proceeds to step S908.

[0096] In step S908, the microcomputer 104 checks whether or not there is free space for reading out the transfer management data in the volatile memory 105. If there is free space, the microcomputer 104 advances the process to step S909, and if there is no free space, the microcomputer 104 advances the process to step S910.

[0097] In the current state 1002 of the volatile memory 105, two of the three sides are free, so step S908 is judged as Yes, and the process proceeds to step S909.

[0098] In step S909, the microcomputer 104 reads out the transfer management data of the folder in question into the volatile memory 105. Here, the transfer management file 100_Trans, which is the transfer management data of the 100IMAGE folder, is read out.

[0099] The state of the volatile memory 105 after reading is shown in 1003. Of the three sides, two are in use.

[0100] In step S905, the microcomputer 104 updates the transfer management data of the object. The update of the transfer management data is the same as in the previous embodiments, and therefore a description thereof will be omitted.

[0101] In step S906, the microcomputer 104 checks whether the power has been turned off. If the power has been turned off, the microcomputer 104 writes the transfer management data of the folder in question to the recording medium 111 in step S907, and ends the operation of this flow. In this embodiment, since the power has not been turned off in step S906, the result in step S906 is No, and the microcomputer 104 returns the process to step S902.

[0102] From this state, it is assumed that IMG_0002.jpg in the 101IMAGE folder is transferred to the FTP server. When the transfer of IMG_0002.jpg is completed, the determination in step S902 is Yes, and the microcomputer 104 advances the process to step S903.

[0103] In step S903, the microcomputer 104 identifies the folder containing the object for which the transfer management data is to be updated, which in this case is 101IMAGE.

[0104] In step S904, the microcomputer 104 checks whether the transfer management file 101_Trans in the 101IMAGE folder has been read out to the volatile memory 105. The current state of the volatile memory is the state indicated by 1003.

[0105] Since the transfer management file 101_Trans has not been read out to the volatile memory 105, the result of step S904 is No, and the microcomputer 104 advances the process to step S908.

[0106] In step S908, the microcomputer 104 checks whether or not there is free space in the volatile memory 105 from which the transfer management file 101_Trans can be read. As shown in 1003, since there is free space on one side remaining, step S908 is judged as Yes, and the microcomputer 104 reads the transfer management file 101_Trans into the volatile memory 105 in step S909. The state of the volatile memory 105 at this time is as shown in 1004. This shows that all three sides are in use.

[0107] In step S905, the microcomputer 104 updates the transfer management data for IMG_0002.jpg in the 101IMAGE folder, advances the process to step S906, and returns the process to step S902 since the power has not been turned off.

[0108] From this state, it is further assumed that IMG_0003.jpg in the 102IMAGE folder is transferred to the FTP server. When the transfer of IMG_0003.jpg is completed, the determination in step S902 is Yes, and the microcomputer 104 advances the process to step S903.

[0109] In step S903, the microcomputer 104 identifies the folder containing the object for which the transfer management data is to be updated, which in this case is 102IMAGE.

[0110] In step S904, the microcomputer 104 checks whether the transfer management data 102_Trans in the 102IMAGE folder has been read out to the volatile memory 105. The current state of the volatile memory is the state indicated by 1004.

[0111] Since the transfer management file 102_Trans has not been read out to the volatile memory 105, step S904 is determined as No, and the microcomputer 104 advances the process to step S908.

[0112] In step S908, the microcomputer 104 checks whether or not there is free space in the volatile memory 105 to read out the transfer management file 102_Trans. The current state of the volatile memory 105 is the state shown in 1004. In this case, as shown in 1004, all three sides of the volatile memory 105 are in use, so it is determined that there is no free space. Therefore, step S908 is determined as No, and the microcomputer 104 advances the process to step S910.

[0113] In step S910, the microcomputer 104 writes the oldest transfer management data other than the folder in which the new captured image is to be saved to the recording medium 111, and releases the volatile memory 105. The folder in which the new captured image is to be saved is 104IMAGE. Therefore, the transfer management file 104_Trans is not subject to being moved to the recording medium 111.

[0114] The state of the volatile memory 105 is shown by 1004, and in addition to the transfer management file 104_Trans, there exist transfer management files 100_Trans and 101_Trans.

[0115] In this embodiment, since it is determined that the transfer management file 100_Trans that was read out earlier to the volatile memory 105 is older, the data of the transfer management file 100_Trans is written back to the recording medium 111, and the volatile memory 105 is released. The state of the volatile memory 105 after this process becomes the state shown in 1005. Since the portion of the transfer management file 100_Trans that was saved has been released, two of the three sides become in use.

[0116] In step S909, the microcomputer 104 reads the transfer management data of the folder into the recording medium 111. That is, the transfer management file 102_Trans is read into the volatile memory 105. At this time, the state of the volatile memory 105 becomes the state shown in 1006. The transfer management file 102_Trans is read, and all three sides of the volatile memory 105 become in use. From this point on, the process is the same as that described above, so the description will be omitted.

[0117] In this embodiment, the sequence has been described using a folder in which newly captured images are saved as an example of a folder that is likely to be accessed, but folders that are likely to be accessed are not limited to this.

[0118] Some imaging devices are capable of separately storing the folder for saving a newly captured image and the location of the last played image. In such a case, the folder in which the played image is saved may be targeted as the folder that is likely to be accessed. There is also a function for saving still images and videos in separate folders. In such a case, folders that are likely to be accessed may be defined for still images and videos, respectively. In this embodiment, how to determine the folder that is likely to be accessed is determined based on the individual product specifications.

[0119] In step S910, the oldest management data other than the management data corresponding to the folders likely to be accessed is selected as the data to be released from the volatile memory 105, but the oldest data read out or the oldest data accessed after being read out may be selected. There is no particular limitation on the method for deleting which transfer data other than the folders likely to be accessed from the volatile memory 105.

[0120] In this embodiment, when managing transfer management data for each folder, the control has been described in which the transfer management file of a folder that is assumed to be highly likely to be accessed is kept in a read state in the volatile memory 105, and the other transfer management data is released. This control makes it possible to reduce the frequency of writing the transfer management data to the recording medium 111 and reading it to the volatile memory 105. As a result, it becomes possible to reduce the processing load.

[0121] The disclosure of this specification includes the following imaging device, its control method, and program.

[0122] (Item 1) A recording means for recording the captured image on a recording medium; a transfer means for transferring the images recorded on the recording medium to an external device; Equipped with The imaging device is characterized in that the recording means records management data for managing the transfer status of images to the external device by the transfer means on the recording medium as data for each folder of images recorded on the recording medium.

[0123] (Item 2) The imaging device described in item 1 further comprises a storage means for storing the management data, the storage means reads the management data from the recording medium, updates it according to the transfer status of the image, and then writes it back to the recording medium.

[0124] (Item 3) 3. The imaging device according to item 2, wherein the recording means records the management data on the recording medium as a management file for each folder of the images.

[0125] (Item 4) 4. The imaging device according to item 3, wherein the storage means reads the management file for each folder of images from the recording medium, updates it according to the transfer status of the images, and then writes it back to the recording medium.

[0126] (Item 5) 3. The imaging device according to item 2, wherein the recording means records the management data in the recording medium as a management file for each predetermined number of images.

[0127] (Item 6) The imaging device described in item 5, characterized in that the storage means reads out the management file for each of the specified number of images from the recording medium, updates it according to the transfer status of the images, and then writes it back to the recording medium.

[0128] (Item 7) 3. The imaging device according to item 2, wherein the recording means records the management data on the recording medium as a management file having delimiters for each folder of the images.

[0129] (Item 8) 8. The imaging device according to item 7, wherein the storage means reads the management data from the recording medium for each division, updates the management data according to a transfer status of the image, and then writes the management data back to the recording medium.

[0130] (Item 9) 9. The imaging device according to item 7 or 8, wherein the management file is a single file.

[0131] (Item 10) 3. The imaging device according to item 2, wherein the storage means has a plurality of storage areas.

[0132] (Item 11) The imaging device described in item 10 is characterized in that, when the management data is stored in all of the multiple storage areas and it becomes necessary to update the management data corresponding to a folder of another image, the storage means frees up areas in the multiple storage areas for management data other than the management data corresponding to the folder of a prioritized image, and stores the management data that needs to be updated.

[0133] (Item 12) 12. The imaging device according to item 11, wherein the folder of images to be prioritized is a folder for recording newly captured images.

[0134] (Item 13) 12. The imaging device according to item 11, wherein the folder of images to be prioritized is a folder in which playback images are saved.

[0135] (Item 14) a recording step of recording the captured image on a recording medium; a transfer step of transferring the images recorded on the recording medium to an external device; having A method for controlling an imaging device, characterized in that, in the recording process, management data for managing the transfer status of images to the external device in the transfer process is recorded on the recording medium as data for each folder of images recorded on the recording medium.

[0136] (Item 15) A program for causing a computer to function as each of the means of the imaging device according to any one of items 1 to 13.

[0137] (Other embodiments) The present invention can also be realized by a process in which a program for realizing one or more functions of the above-mentioned embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) for realizing one or more functions.

[0138] The invention is not limited to the above-described embodiments, and various modifications and variations are possible without departing from the spirit and scope of the invention. Accordingly, the following claims are appended to apprise the public of the scope of the invention. [Explanation of symbols]

[0139] 100: imaging device, 101: lens, 102: imaging element, 103: A / D converter, 104: microcomputer, 105: volatile memory, 106: non-volatile memory, 111: recording medium

Claims

1. A recording means for recording the captured image on a recording medium; a transfer means for transferring the images recorded on the recording medium to an external device; Equipped with The imaging device is characterized in that the recording means records management data for managing the transfer status of images to the external device by the transfer means on the recording medium as data for each folder of images recorded on the recording medium.

2. 2. The imaging device according to claim 1, further comprising a storage means for storing the management data, the storage means reading the management data from the recording medium, updating the management data according to a transfer status of the image, and then writing the management data back to the recording medium.

3. 3. The image pickup apparatus according to claim 2, wherein the recording means records the management data on the recording medium as a management file for each folder of the images.

4. 4. The imaging device according to claim 3, wherein the storage means reads out the management file for each folder of images from the recording medium, updates the management file in accordance with a transfer status of the images, and then writes the management file back to the recording medium.

5. 3. The image pickup apparatus according to claim 2, wherein said recording means records said management data on said recording medium as a management file for each predetermined number of images.

6. 6. The imaging device according to claim 5, wherein the storage means reads out the management file for each of the predetermined number of images from the recording medium, updates the management file in accordance with a transfer status of the images, and then writes the management file back to the recording medium.

7. 3. The image pickup apparatus according to claim 2, wherein the recording means records the management data on the recording medium as a management file having delimiters for each folder of the images.

8. 8. The imaging apparatus according to claim 7, wherein said storage means reads out said management data for each segment from said recording medium, updates said management data in accordance with a transfer status of the images, and then writes said management data back to said recording medium.

9. 8. The image pickup apparatus according to claim 7, wherein the management file is a single file.

10. 3. The image pickup apparatus according to claim 2, wherein the storage means has a plurality of storage areas.

11. The imaging device of claim 10, characterized in that, when the management data is stored in all of the multiple memory areas and it becomes necessary to update the management data corresponding to a folder of other images, the storage means frees up areas in the multiple memory areas for management data other than the management data corresponding to the folder of prioritized images, and stores the management data that needs to be updated.

12. 12. The imaging apparatus according to claim 11, wherein the folder for images to be prioritized is a folder for recording newly captured images.

13. 12. The imaging apparatus according to claim 11, wherein the folder of images to be prioritized is a folder in which reproduced images are saved.

14. a recording step of recording the captured image on a recording medium; a transfer step of transferring the images recorded on the recording medium to an external device; having A method for controlling an imaging device, characterized in that, in the recording process, management data for managing the transfer status of images to the external device in the transfer process is recorded on the recording medium as data for each folder of images recorded on the recording medium.

15. A program for causing a computer to function as each of the means of the imaging apparatus according to any one of claims 1 to 13.

Images