Imaging device, method for controlling same, and program

Abstract

The present invention provides an imaging device capable of performing appropriate transfer management with respect to finite resources even when the number of images which are transfer management targets increases. The imaging device comprises: a recording unit that records a captured image on a recording medium; and a transfer unit that transfers, to an external device, the image recorded on the recording medium. The recording unit records, on the recording medium, management data for managing the transfer state of the image to the external device by the transfer unit as data for each folder of the image recorded on the recording medium.

Description

Imaging device, control method thereof, and program

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

[0002] In recent years, with the increase in network transfer speeds, 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 transferred can include various devices such as File Transfer Protocol (FTP) 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, some imaging devices display a message indicating that the transfer was successful when the image is played back on the imaging device.

[0004] Various techniques have been proposed for controlling the transfer of images as described above, 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] Japanese Patent Laid-Open No. 2006-124499 discloses the following technology: When an image is sent from a server to a client, the transmission history is updated and a list of the transmission history is sent from the server to the client. The client then checks the list of transmission history sent from the server and requests the transmission of files other than those already received.

[0006] Patent Document 2 discloses the following technology: 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 then sent to other devices for use.

[0007] JP 2009-086800 A JP 2014-526103 A

[0008] However, the above-mentioned patent documents do not mention transfer management control for finite resources (e.g., RAM) when a large number 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 view of the above-mentioned problems, and provides an imaging device that can perform appropriate transfer management even when the number of images to be transferred increases with limited resources.

[0010] The imaging device according to the present invention comprises a recording means for recording captured images 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.

[0011] According to the present invention, even when the number of images to be managed for transfer increases with limited resources, it is possible to perform appropriate transfer management.

[0012] Other features and advantages of the present invention will become apparent from the following description taken in conjunction with the accompanying drawings, in which the same or similar elements are designated by the same reference numerals.

[0013] The accompanying drawings are incorporated in and constitute a part of the specification, illustrate embodiments of the present invention, and are used, together with the description, to explain the principles of the present invention. A block diagram showing the configuration of an imaging device according to a first embodiment of the present invention. A diagram showing an example of a screen display for performing a process of selecting images to be transferred. A flowchart showing control for managing transfer management data in the first embodiment. A diagram showing the structure of transfer management data in the first embodiment. A flowchart showing control for managing transfer management data in the second embodiment. A diagram showing the structure of transfer management data in the second embodiment. A diagram showing the structure of transfer management data in the second embodiment. A flowchart showing control for managing transfer management data in the third embodiment. A diagram showing the structure of transfer management data in the third embodiment. A diagram showing the structure of transfer management data in the third embodiment. A flowchart showing control for managing transfer management data in the fourth embodiment. A flowchart showing control for managing transfer management data in the fourth embodiment. A diagram showing the structure of transfer management data in the fourth embodiment.

[0014] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention claimed. Although multiple features are described in the embodiments, not all of these multiple features are necessarily essential to the invention, and multiple features may be combined arbitrarily. Furthermore, in the accompanying drawings, the same reference numerals are used to designate the same or similar components, and redundant explanations will be omitted.

[0015] 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.

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

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

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

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

[0020] The display member 109 is controlled by the microcomputer 104 and displays menus, plays images, etc. The operation member 110 performs operations on the menus 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.

[0021] Hereinafter, transfer management in this embodiment will be described while showing a process for selecting images to be transferred and a process for displaying images for which transfer has failed as examples of functions for handling transfer management data.

[0022] FIG. 2 shows an example of a screen display for selecting an image to be transferred. The following description is based on the assumption that "IMG_0001.jpg" is stored in the recording medium 111. Screen 200 shows the screen of the display member 109 in which an image stored in the recording medium 111 is played back by the imaging device 100. In this state, "IMG_0001.jpg" is being played back. The user selects which image to transfer while viewing the displayed image. As an operation method, it is assumed that the operation is performed using the touch panel, keys, or the like of the operation member 110. Area 201 indicates the status of transfer management, including information such as whether the displayed image has been transferred.

[0023] Image transfer management will now be described. Transfer management refers to the state in which transfer status, such as whether the image is to be sent, whether it is an image that has already been sent, or whether transfer 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 indicator such as a check mark 202 is displayed as an indication of transfer management such as "selected." When a selected image indicated by the indicator 202 exists, the user can select transfer to send the image in the "selected" state to the transfer destination.

[0024] 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 the transfer are well known techniques, and any method may be used.

[0025] Transfer starts when the transfer start button 203 is pressed, and when the transfer is complete, the image is managed as "transferred" in the image management system. For example, a "○" indicator 204 can be displayed to notify the user that the transfer has been completed.

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

[0027] So far, we have explained a method for selecting whether or not to transfer a single image displayed on the display member 109, but it is also possible to display a screen such as the menu 206 and provide the user with options for selecting multiple images at once. Image selection is assumed to be possible using known technology.

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

[0029] 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 destination is recorded.

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

[0031] 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 images are stored in the recording medium 111 of the imaging device 100 is shown as 208.

[0032] The DCIM folder exists directly under the recording medium 111. The image IMG_0001.jpg indicated by 209 is an image stored under the 100IMAGE folder.

[0033] For example, when 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 a single transfer management file. Also, as shown in 210, if there are photographed images stored in the 101IMAGE folder or below, they are handled as separate transfer management files.

[0034] 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 then written back to the recording medium 111.

[0035] Regarding the location where the transfer management file is stored in the recording medium 111, one method is to record it in the same folder as the captured images. As a specific example, transfer management data for images stored in the 100IMAGE folder or below is stored in the 100IMAGE folder or below. Another possible method is to create a folder dedicated to transfer management data. For example, as shown in 211, a folder called TRANS may be created under the DCIM folder to store the transfer management data, and the data may be stored there. In this embodiment, there are no particular limitations on the location or method for recording the transfer management data.

[0036] 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 loading a control program stored in the nonvolatile memory 106 into the volatile memory 105 and executing it. This also applies to the flowcharts in the second and subsequent embodiments.

[0037] In the following explanation, it is assumed that the images and transfer management data files stored on the recording medium 111 are in the state shown by 400 in Figure 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 called 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 in the transfer management file 100_Trans are shown in 401. The contents of the transfer management data in the transfer management file 101_Trans are shown in 402. Also, it is assumed that the data in the transfer management file 100_Trans has been read into the volatile memory 105, and the data in the transfer management file 101_Trans has not been read into the volatile memory 105.

[0038] First, in step S300, the microcomputer 104 determines whether a process requiring an update of the transfer management data has been performed. Processes requiring an update of the transfer management data include the aforementioned processes of selecting an image as a transfer target, completing an image transfer, and failing to transfer an image. In this embodiment, the process of completing the transfer of IMG_0002.jpg in the 101IMAGE folder to the FTP server, as shown in 403 of FIG. 4, will be described as an example.

[0039] If a process that requires updating of the transfer management data has been performed in step S300, the microcomputer 104 proceeds to step S301; otherwise, it repeats the process of step S300.

[0040] In step S301, the microcomputer 104 identifies the folder in which the 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 for IMG_0002.jpg in the 101IMAGE folder, the 101IMAGE folder is the relevant folder.

[0041] In step S302, the microcomputer 104 checks whether the transfer management file 101_Trans in the relevant folder, i.e., the 101IMAGE folder, has been read into the nonvolatile memory 105. If the file has been read, the microcomputer 104 proceeds to step S304, and if not, the microcomputer 104 proceeds to step S303.

[0042] Here, as explained 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.

[0043] In step S303, the microcomputer 104 reads the transfer management file of the 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.

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

[0045] 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.

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

[0047] 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 to the TRANS folder of the recording medium 111 and below.

[0048] By recording the transfer management data as a file on the recording medium 111 in step S305, the transfer management data can be stored even if the power of the image capture device 100 is turned off.

[0049] In step S306, the microcomputer 104 checks whether or not the power supply to the image capture device 100 has been turned off. If the power supply has been turned off, the microcomputer 104 performs a shutdown process for the image capture 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.

[0050] 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 only necessary to prepare a volatile memory 105 according to the number of captured images that can be saved in the folder. Therefore, even 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.

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

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

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

[0054] 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 were managed as one transfer management file, but in the second embodiment, a transfer management file is created for each predetermined number of images.

[0055] The predetermined number may be any number and may be determined in any way. In this embodiment, the maximum number of images that can be saved in one folder is 9,999, so one transfer management file is created for half that number, or 5,000 images. Examples of transfer management data for images in the 100IMAGE folder are shown in 601 and 602.

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

[0057] 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 yet been read into the volatile memory 105.

[0058] 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.

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

[0060] 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.

[0061] Here, we want to update the transfer management data for IMG_9999.jpg in the 100IMAGE folder, so we check which transfer management file corresponds to that. The number of transfer management files 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.

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

[0063] As described above, since the transfer management file 100_Trans_B has not been read into the volatile memory 105 at this time, the determination in step S503 is No, and the process proceeds to step S504.

[0064] 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 .

[0065] In step S505, the microcomputer 104 updates the transfer management data of the corresponding transfer management file. As shown by 603 in Fig. 6B, 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."

[0066] In step S 506 , the microcomputer 104 writes the transfer management file in question to the recording medium 111 .

[0067] In step S507, the microcomputer 104 checks whether or not the power supply to the image capture device 100 has been turned off. If the power supply has been turned off, the microcomputer 104 performs a shutdown process for the image capture device 100. If the power supply 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.

[0068] 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 the files in the volatile memory 105. As a result, when using limited resources, it is possible to provide the transfer management function even if the number of images to be transferred increases, and it is possible to prevent a decrease in user operability.

[0069] (Third embodiment) Figure 7 is a flowchart that explains the control in the third embodiment in which transfer management data in one file is divided into folder units, the transfer management data is read from the recording medium in folder division units, and then written to the recording medium.

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

[0071] 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.

[0072] 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.

[0073] An example of the data structure of a transfer management file is shown in 801. The divisions between folders are clearly indicated. An example will be explained 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 for the images in the 102IMAGE folder has not yet been read into the volatile memory 105.

[0074] 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.

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

[0076] In step S702, the microcomputer 104 checks whether the transfer management data of the relevant folder, i.e., the 102IMAGE folder, has been read into the nonvolatile memory 105. If the data has been read, the microcomputer 104 proceeds to step S704, and if the data has not been read, the microcomputer 104 proceeds to step S703.

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

[0078] 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 by 801, because there is only 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 in FIG. 8B shows this state.

[0079] 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 has been completed, the area managing the transfer status of IMG_5000.jpg to the FTP server is updated from "not transferred" to "transfer completed," as shown in 803 in Fig. 8B.

[0080] 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 location where it was read from the recording medium 111 in step S703.

[0081] In step S706, the microcomputer 104 checks whether or not the power supply to the image capture device 100 has been turned off. If the power supply has been turned off, the microcomputer 104 performs a shutdown process for the image capture device 100. If the power supply has not been turned off, the process returns to step S700 and waits for the process of updating the transfer management data to be performed.

[0082] According to this embodiment, by dividing the transfer management data in a single file into folders, it becomes possible to read or write the transfer management data from or to the recording medium in folder division units. By handling the data in folder units, when expanding the data in the volatile memory 105, it is only necessary to prepare a volatile memory 105 according to the number of images that can be stored in a folder. Therefore, even 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.

[0083] In the present embodiment, an example has been described in which image transfer data is divided into folder units, 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 division may be made in units other than folder units. For example, as in the second embodiment, a certain number of images may be determined, and divisions may be made in units of that number. The method of dividing the data is not particularly limited.

[0084] (Fourth embodiment) Figures 9A and 9B are flowcharts illustrating control of transfer management data in a fourth embodiment, in which, when managing transfer management data for each folder, priority is given to folders that are expected to be more likely to be accessed.

[0085] 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.

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

[0087] The imaging device has a function for playing back images. When a playback command is received, the image to be played back is also a function for 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. Furthermore, when a new image is captured, it is saved as IMG_0004.jpg in the 104IMAGE folder. Furthermore, it is assumed that transfer management files 100_Trans to 104Trans exist in the recording medium 111 as transfer management files that store transfer management data for the captured images, and are used to manage the transfer status for each folder.

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

[0089] In step S900, the microcomputer 104 specifies a folder in which the newly captured image will be saved. 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.

[0090] In step S901, the microcomputer 104 reads into 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).

[0091] 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 this time is shown in 1002. Of the three sides of the volatile memory 105, one side is in use by the data of the transfer management file 104_Trans.

[0092] 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; if not, step S902 is repeated.

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

[0094] 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 100IMAGE.

[0095] In step S904, the microcomputer 104 checks whether 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 proceeds to step S905; if not, the microcomputer 104 proceeds to step S908.

[0096] In the state 1002 of 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 determined as No, and the process proceeds to step S908.

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

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

[0099] In step S909, the microcomputer 104 reads the transfer management data of the folder into the volatile memory 105. In this case, the transfer management file 100_Trans, which is the transfer management data of the 100IMAGE folder, is read.

[0100] The state of the volatile memory 105 after reading is shown in 1003. Two of the three sides are in use.

[0101] 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.

[0102] 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 determination in step S906 is No, and the microcomputer 104 returns the process to step S902.

[0103] 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 answer in step S902 is Yes, and the microcomputer 104 advances the process to step S903.

[0104] 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.

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

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

[0107] In step S908, the microcomputer 104 checks whether there is free space in the volatile memory 105 from which the transfer management file 101_Trans can be read. As shown in 1003, there is free space on one side remaining, so step S908 is determined 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.

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

[0109] 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.

[0110] 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.

[0111] 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.

[0112] 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.

[0113] In step S908, the microcomputer 104 checks whether 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 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 proceeds to step S910.

[0114] 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 transfer to the recording medium 111.

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

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

[0117] 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. The process from this point on is the same as that described above, so a description thereof will be omitted.

[0118] 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.

[0119] Some imaging devices are capable of separately storing the folder in which newly captured images are saved and the location of the most recently played back image. In such cases, the folder in which the played back images are saved may be targeted as the folder with a high probability of being accessed. There are also functions for saving still images and videos in separate folders. In such cases, folders with a high probability of being accessed may be defined for still images and videos. In this embodiment, how the folder with a high probability of being accessed is determined is based on the specifications of the individual product.

[0120] In step S910, the oldest management data other than the management data corresponding to the folders that are likely to be accessed is selected as the data to be released from the volatile memory 105, but the oldest data that has been read or the oldest data that has been accessed after being read may also be selected. There are no particular limitations on the method for deleting transfer data from the volatile memory 105 other than the folders that are likely to be accessed.

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

[0122] The present invention can also be realized by supplying a program that realizes one or more of the functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., an ASIC) that realizes one or more of the functions.

[0123] The invention is not limited to the above-described embodiments, and various changes and modifications can be made 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.

[0124] This application claims priority based on Japanese Patent Application No. 2023-145573, filed September 7, 2023, the entire contents of which are incorporated herein by reference.

Claims

1. An imaging device comprising: a recording means for recording captured images onto a recording medium; and a transfer means for transferring the images recorded onto the recording medium to an external device, wherein the recording means records, onto the recording medium, management data for managing the transfer status of images to the external device by the transfer means as data for each folder of images recorded on the recording medium.

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

3. The imaging device according to claim 2, wherein said recording means records said management data on said recording medium as a management file for each folder of said images.

4. The imaging device according to claim 3, characterized in that the storage means reads out 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.

5. The imaging device according to claim 2, wherein said recording means records said management data on said recording medium as management files for each predetermined number of images.

6. The imaging device according to claim 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.

7. The imaging device according to claim 2, wherein said recording means records said management data on said recording medium as a management file having delimiters for each folder of said images.

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

9. The imaging device according to claim 7, wherein the management file is a single file.

10. The imaging device according to claim 2, wherein said storage means has a plurality of storage areas.

11. The imaging device of claim 10, wherein when the management data is stored in all of the plurality of 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 plurality of 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. The imaging device according to claim 11, wherein the folder for images to be given priority is a folder for recording newly captured images.

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

14. A method for controlling an imaging device, comprising: a recording step of recording a captured image on a recording medium; and a transfer step of transferring the image recorded on the recording medium to an external device, wherein in the recording step, management data for managing the transfer status of images to the external device in the transfer step 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 device according to any one of claims 1 to 13.

Images