Image pickup apparatus, control method therefor, and program

Abstract

Provided is an image pickup apparatus capable of performing appropriate transfer management with limited resources even when the number of images undergoing transfer management increases. The image capturing apparatus includes: a recording unit for recording a captured image on a recording medium; and a transfer unit for transferring an image recorded in the recording medium to an external device, in which the recording unit records management data to the recording medium as data for each image folder recorded in the recording medium, the management data is used to manage an image transfer state related to transfer to the external device by the transfer unit.

Description

Technical Field

[0001] This invention relates to a technique for managing the transmission status when transmitting captured images to an external device. Background Technology

[0002] In recent years, with the improvement of network transmission speed, video recording equipment that automatically or manually transmits captured images to external devices via the network is being developed. Various devices such as FTP (File Transfer Protocol) servers and smartphones can be envisioned as external devices to which images are transmitted.

[0003] Such camera devices typically include functions for managing image transmission, enabling the device to determine if an image has been transmitted to an external device. For example, one known camera device provides a display indicating successful transmission when the transmitted image is played back on the camera device side, provided that the transmission was successful after successfully transmitting an image to a smartphone.

[0004] Various techniques have been proposed for controlling this image transmission management. For example, methods such as writing the transmission status to the header of the image file and using a separate file to manage information related to image transmission management are known.

[0005] Patent document (PTL) 1 discloses the following technique: When an image is transmitted from a server to a client, the transmission history is updated, and a list of transmission history data is transmitted from the server to the client. The client views the list of transmission history data transmitted from the server and requests the server to transmit files other than those already received.

[0006] PTL 2 discloses the following technology: In a mobile terminal, changes to stored image files and the directory where these files are stored are monitored, and when a change is detected, details of the detected change are reflected in a log file. The log file is then transferred to another device for use. Existing technical documents Patent documents

[0007] PTL 1: Japan Special Opening 2009-086800 PTL 2: Japanese special watch 2014-526103 Summary of the Invention The problem the invention aims to solve

[0008] However, the aforementioned patent documents do not mention the transmission management control of limited resources (e.g., RAM) when transmitting a large number of images, in the case where the transmission management data is managed as a separate file.

[0009] In view of the above problems, the present invention provides a camera device that can perform appropriate transmission management with limited resources even when the number of images under transmission management increases. Solution for solving the problem

[0010] The camera device according to the present invention includes: a recording component for recording captured images onto a recording medium; and a transmission component for transmitting the images recorded on the recording medium to an external device, wherein the recording component records management data as data for each image folder recorded on the recording medium, the management data being used to manage the image transmission status related to transmission to the external device via the transmission component. Advantages of the invention

[0011] According to the present invention, even when the number of images subject to transmission management increases, appropriate transmission management can be performed with limited resources.

[0012] Other features and advantages of the invention will become apparent from the following description taken in conjunction with the accompanying drawings. Note that throughout the drawings, the same reference numerals denote the same or similar components. Attached Figure Description

[0013] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and, together with the specification, serve to explain the principles of the invention. Figure 1 This is a block diagram illustrating the configuration of a camera device according to a first embodiment of the present invention. Figure 2 This is an example diagram showing a screen displayed during the process of selecting an image to be transmitted. Figure 3 This is a flowchart illustrating a control for managing the transmission of management data according to a first embodiment. Figure 4 This is a diagram illustrating the structure of the transmission management data according to the first embodiment. Figure 5 This is a flowchart illustrating a control for managing the transmission of management data according to a second embodiment. Figure 6A This is a diagram illustrating the structure of transmission management data according to the second embodiment. Figure 6B This is a diagram illustrating the structure of transmission management data according to the second embodiment. Figure 7 This is a flowchart illustrating a control for managing the transmission of management data according to a third embodiment. Figure 8A This is a diagram illustrating the structure of transmission management data according to the third embodiment. Figure 8B This is a diagram illustrating the structure of transmission management data according to the third embodiment. Figure 9A This is a flowchart illustrating a control for managing the transmission of management data according to a fourth embodiment. Figure 9B This is a flowchart illustrating a control for managing the transmission of management data according to a fourth embodiment. Figure 10 This is a diagram illustrating the structure of transmission management data according to the fourth embodiment. Detailed Implementation

[0014] In the following, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments are not intended to limit the scope of the claimed invention. Multiple features are described in the embodiments, but this does not limit the invention to requiring all such features, and multiple such features can be appropriately combined. Furthermore, in the drawings, the same reference numerals are given the same or similar configuration, and redundant descriptions are omitted.

[0015] First Embodiment Figure 1 This is a block diagram showing the overall configuration of a camera device 100 according to a first embodiment of the present invention.

[0016] exist Figure 1 In this system, the capturing lens 101 consists of a fixed-focus lens and a zoom lens, etc., and forms an image of the subject. The image sensor 102 consists of a CCD or CMOS sensor, etc., and converts the image of the subject formed by the capturing lens 101 into an electrical signal. The A / D converter 103 converts the analog output signal from the image sensor 102 into a digital signal.

[0017] The microcomputer 104 controls the camera device 100 as a whole, including the control and data processing of various constituent components. This includes, for example, controlling various parts based on operation instructions from the operation component 110, generating images to be displayed on the display component 109, and network control via the communication component 108. It also includes selecting images to be transmitted, transmitting images to external devices, referencing and updating transmission management data, controlling the reading of transmission management data from the recording medium 111 to the volatile memory 105, and controlling the writing of data from the volatile memory 105 to the recording medium 111.

[0018] The volatile memory 105 temporarily holds image data converted into digital signals by the A / D converter 103. Data used for transmission management, as described in this embodiment, is also held here and referenced and updated by the microcomputer 104. The non-volatile memory 106 holds the control program for the camera device executed by the microcomputer 104. The non-volatile memory 106 also stores the camera device's settings.

[0019] The image processing unit 107 performs image processing on the captured images. The communication component 108 is, for example, a communication component for communication technologies such as wireless LAN. Wired or wireless connections can be used for the communication technology. Although technologies such as FTP (File Transfer Protocol) are assumed, other existing technologies can be used alternatively.

[0020] The display component 109 is controlled by the microcomputer 104 and displays menus and plays back images, etc. The operation component 110 is used to operate the menus, etc., displayed on the display component 109. It is assumed that the operation component is an operation component such as a key or a touch panel. For example, it is assumed that the recording medium 111 is a CF card or an SD card, etc. Using the microcomputer 104, data can be written from the volatile memory 105 to the recording medium 111, and data stored in the recording medium 111 can be read from the volatile memory 105, etc.

[0021] The following describes the transmission management according to this embodiment, as well as the processing for selecting images to be transmitted and the processing for indicating images that have failed to be transmitted, as examples of functions for responding to transmission management data.

[0022] Figure 2 This is an example diagram showing a screen displayed during processing for selecting an image to be transmitted. The description assumes that "IMG_0001.jpg" is stored in recording medium 111. Screen 200 indicates the display member 109 displaying the image stored in recording medium 111, which is being played back by the imaging device 100. In this state, "IMG_0001.jpg" is being played back. The user sets which image to transmit while viewing the displayed image. As an operation method, it is assumed that operation is performed using the touch panel or keys of the operation member 110. Area 201 is an area indicating the status of transmission management, including information such as whether the displayed image has been transmitted.

[0023] Image transmission management will be described here. "Transmission management" refers to managing the transmission status, such as whether an image is to be transmitted, whether an image has already been transmitted, and whether the transmission has failed, in association with the image. For example, when the user selects an image displayed on screen 200 as the image to be transmitted, transmission management is performed assuming a "selection" state. For example, a checkmark indicator 202 is displayed as an indication of "selection" transmission management. If a selected image exists as indicated by indicator 202, the image in the "selection" state can be transmitted to its destination by the user selecting "transmit".

[0024] A visible button, such as a transmission start button 203, can be prepared, and transmission can begin in response to the pressing of the transmission start button 203; alternatively, an indicator 202 placed in a selection state can be used as a trigger to start transmission. The timing and conditions for starting transmission are well-known techniques, so any method can be used.

[0025] When a transfer begins in response to the pressing of the transfer start button 203 and then completes, the image is managed as a "transferred" state for image management purposes. For example, the user can be notified that the image has been transferred by displaying a circular indicator 204.

[0026] The text also describes images that failed to be transmitted. When the transmit start button 203 is used to indicate a transmit and attempt to transmit an image to its destination, if a network error or other issue occurs and the image cannot be correctly transmitted to the destination, the image to be transmitted is managed as a failed transmission image. For example, the user can be notified that the image transmission has failed by displaying an "x" indicator 205.

[0027] The method for selecting whether to transmit a single image displayed by display component 109 has been described above; however, a screen such as menu 206 can be displayed, and the user can be provided with the option to select multiple images at once. It is assumed that image selection can be provided using known techniques.

[0028] The data structures and controls used to manage the aforementioned transmission states will be described next. Example 207 indicates transmission management data.

[0029] For each image file, the transmission destination and transmission status are recorded. As indicated in 207, when assuming an FTP server and a smartphone are the transmission destinations, the transmission status is recorded for each of these transmission destinations.

[0030] For example, 207 indicates that image IMG_0001 has been successfully transmitted to the FTP server, but has not yet been transmitted to the smartphone. Although the transmission status to the assumed transmission destination is stored for each image, this embodiment assumes that the structure of the transmission management data can be provided by known techniques.

[0031] The location where the transmission management data is stored will be described next. This embodiment assumes a method for storing the transmission management data in a file format. 208 indicates an example of a folder structure in the camera device 100 when captured images are stored in the recording medium 111.

[0032] The DCIM folder exists directly under recording medium 111. 209 indicates that the image IMG_0001.jpg is an image saved in or under the 100IMAGE folder.

[0033] For example, when managing transfer management data, such as transfer management data indicated by 207, at the level of shooting folders, images stored in or under the 100 IMAGE folder are treated as a single transfer management file. Additionally, when captured images exist in or under the 101 IMAGE folder as indicated by 210, those images are treated as separate transfer management files.

[0034] The units and methods used to generate the transmission management file will be described in more detail later. Control is performed so that the transmission management file itself is stored in the recording medium 111 and read out to the volatile memory 105 at necessary time intervals; and the transmission management data in the volatile memory 105 is referenced and updated, and written back to the recording medium 111.

[0035] Regarding the location for storing the transfer management files on the recording medium 111, there are methods, for example, recording the data to the same folder as the captured images. As a specific example, transfer management data for images stored in or under the 100 IMAGE folder is stored in or under the 100 IMAGE folder. Alternatively, a control method for generating a dedicated folder for transfer management data is also conceivable. For example, as indicated in 211, a folder named "TRANS" for storing transfer management data can be generated in or under the DCIM folder, and the transfer management data can be stored therein. In this embodiment, there are no particular limitations on the location and method for recording transfer management data.

[0036] Figure 3This is a flowchart illustrating the controls for transferring management data to various folders where captured images are stored. Note that... Figure 3 The operation shown in the flowchart is achieved by the microcomputer 104 loading the control program stored in the non-volatile memory 106 into the volatile memory 105 and executing the program. This also applies to the flowcharts of the second embodiment and subsequent embodiments.

[0037] Note that the following description assumes that the images and transmission management data files stored in the recording medium 111 are in a location such as Figure 4 The status indicated by 400, etc. Specifically, IMG_0001.jpg, IMG_0002.jpg, and IMG_0003.jpg are stored in the 100 IMAGE folder and the 101 IMAGE folder, respectively. Transfer management files 100_Trans and 101_Trans exist in or under the TRANS folder, and these transfer management files manage the images stored in the 100 IMAGE folder and the 101 IMAGE folder according to folder level. 401 indicates details of the transfer management data of transfer management file 100_Trans. 402 indicates details of the transfer management data of transfer management file 101_Trans. Data of transfer management file 100_Trans has been read into volatile memory 105, while data of transfer management file 101_Trans has not yet been read into volatile memory 105.

[0038] First, in step S300, the microcomputer 104 determines whether the process requiring an update to the transmission management data has already been performed. "Process requiring an update to the transmission management data" refers to situations such as the previously described processes for selecting the image to be transmitted, the completion of image transmission, or the failure of image transmission. Figure 4 As indicated by 403 in the example, this embodiment will describe the process of completing the transfer of IMG_0002.jpg from the 101 IMAGE folder to the FTP server.

[0039] In step S300, if the processing that requires updating the transmission management data has already been performed, the microcomputer 104 moves the sequence to step S301; otherwise, the processing of step S300 is repeated.

[0040] In step S301, the microcomputer 104 identifies the folder where the object whose transmission management data needs to be updated is recorded. In this embodiment, the transmission management data of IMG_0002.jpg in the 101 IMAGE folder will be updated, and therefore the 101 IMAGE folder is the corresponding folder.

[0041] In step S302, the microcomputer 104 confirms whether the transfer management file 101_Trans in the corresponding folder (i.e., the 101 IMAGE folder) has been read into the non-volatile memory 105. If the file has been read, the microcomputer 104 moves the sequence to step S304, and if the file has not been read, it moves the sequence to step S303.

[0042] Here, as described above, the data of the transfer management file 101_Trans has not yet been read out of the volatile memory 105, and therefore it is determined to be no in step S302, and the sequence moves to step S303.

[0043] In step S303, the microcomputer 104 reads the transfer management file of the corresponding folder from the recording medium 111 into the volatile memory 105. Specifically, by Figure 4 Data in the transfer management file 101_Trans, indicated by 400, is read into volatile memory 105. It is assumed that the transfer management file read into volatile memory 105 is in the state indicated by 402.

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

[0045] In this example, because the transfer of IMG_0002.jpg from the 101 IMAGE folder to the FTP server is complete, therefore... Figure 4 As indicated by 403, the area managing the transfer status of IMG_0002.jpg to the FTP server has been updated from "Not Transferred" to "Transfer Completed".

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

[0047] Specifically, the data read from the volatile memory 105 in step S303 and updated in step S304 in the transfer management file 101_Trans is written to the TRANS folder of the recording medium 111.

[0048] In step S305, the transmission management data is recorded as a file on the recording medium 111 so that the transmission management data can be stored even when the power of the camera device 100 is turned off.

[0049] In step S306, the microcomputer 104 checks whether the power supply to the camera device 100 has been turned off. If the power supply is off, the microcomputer 104 performs processing to shut down the camera device 100. If the power supply is not turned off, the sequence returns to step S300 and waits for processing to update the transmission management data.

[0050] According to this embodiment, transfer management data can be managed for each folder storing captured images. By managing data for each folder, when data is loaded into the volatile memory 105, space can be prepared in the volatile memory 105 according to the number of photos that can be saved in each folder. Therefore, even when the number of images undergoing transfer management increases, transfer management functionality can be provided with limited resources, which prevents a decrease in user availability.

[0051] Second Embodiment Figure 5 This is a flowchart illustrating the control for generating transmission management files for a predetermined number of images in each group, according to the second embodiment.

[0052] The following section describes an example of generating transmission management data as a file for a predetermined number of images in each group.

[0053] Here, it is assumed that images are captured and management files are transmitted in the form of, for example... Figure 6A The states indicated by 600 are stored in the recording medium 111.

[0054] Specifically, a total of 9,999 images, from IMG_0001.jpg to IMG_9999.jpg, are stored in the 100 IMAGE folder. While in the first embodiment, images existing in a single folder are managed as a single transfer management file, in the second embodiment, transfer management files are generated for each predetermined number of images in a group.

[0055] The predetermined quantity can be any desired quantity and can be determined in any way. This embodiment assumes that 9,999 images can be stored in a single folder, and therefore assumes that a single transfer management file is generated for half of that quantity (e.g., 5,000 images). 601 and 602 indicate examples of transfer management data for images in a 100 IMAGE folder.

[0056] 601 indicates the transfer status of images 0001 to 5000 recorded in the TRANS folder or the 100IMAGE folder under the TRANS folder, with filename 100_Trans_A. 602 indicates the transfer status of images 5001 to 9999 recorded in the TRANS folder or the 100IMAGE folder under the TRANS folder, with filename 100_Trans_B.

[0057] As an example, the second embodiment will describe the completion of the transfer of IMG_9999.jpg in the 100 IMAGE folder to the FTP server from the states indicated by 600, 601, and 602 above. These descriptions assume that the transfer management file 100_Trans_B has not yet been read out of the volatile memory 105.

[0058] In step S500, the microcomputer 104 determines whether the processing required to update the transmission management data has been performed. This embodiment will describe the completion of the transmission of IMG_9999.jpg from the 100 IMAGE folder to the FTP server.

[0059] In step S501, the microcomputer 104 confirms the number of images to be transmitted, which will be managed by a single transmission management file. In this embodiment, this is 5,000.

[0060] In step S502, the microcomputer 104 determines that a transmission management file contains transmission management data of the object whose transmission management data needs to be updated.

[0061] Here, the transfer management data for IMG_9999.jpg in the 100 IMAGE folder will be updated, and the corresponding transfer management file will be confirmed. Since the number of images to be transferred is 5,000 and the total number of images is 9,999, it can be seen that the corresponding transfer management file is 100_Trans_B.

[0062] In step S503, the microcomputer 104 confirms whether the corresponding transfer management file has been read into the non-volatile memory 105. If the file has been read, the microcomputer 104 moves the sequence to step S505; if the file has not been read, it moves the sequence to step S504.

[0063] As mentioned above, here, the transfer management file 100_Trans_B has not yet been read out of the volatile memory 105, and therefore it is determined to be no in step S503, after which the sequence moves to step S504.

[0064] In step S504, the microcomputer 104 reads the transfer management file 100_Trans_B from the recording medium 111 into the volatile memory 105.

[0065] In step S505, the microcomputer 104 updates the transmission management data in the corresponding transmission management file. For example... Figure 6BAs indicated in section 603, the area for the transfer status of the file 100_Trans_B's IMG_9999.jpg to the FTP server has been updated from "Not Transferred" to "Transfer Completed".

[0066] In step S506, the microcomputer 104 writes the corresponding transmission management file into the recording medium 111.

[0067] In step S507, the microcomputer 104 checks whether the power supply to the camera device 100 has been turned off. If the power supply is off, the microcomputer 104 performs processing to shut down the camera device 100. If the power supply is not turned off, the sequence returns to step S500 and waits for processing to update the transmission management data.

[0068] According to this embodiment, a transmission management file can be generated for each group of a predetermined number of images. Generating a transmission management file for each group of images allows adjustment of the memory size when loading data into the volatile memory 105. As a result, even with an increased number of images undergoing transmission management, transmission management functionality can be provided using limited resources, thus preventing a decrease in user availability.

[0069] Third Embodiment Figure 7 The flowchart illustrates a control according to a third embodiment, in which transfer management data in a single file is segmented into folders, transfer management data is read from a recording medium for each folder-based segment, and transfer management data is further written to the recording medium.

[0070] Here, it is assumed that images are captured and management files are transmitted in the form of, for example... Figure 8A The states indicated by 800 are stored in the recording medium 111.

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

[0072] Although the transmission management data is managed as files, in this embodiment, the transmission management data of all images is managed as a single transmission management file.

[0073] 801 indicates an example of the data structure for the transfer management file. It can be seen that segments are provided for each folder. As an example, the transfer of IMG_5000.jpg in the 102 IMAGE folder to the FTP server will be described. Note that the description assumes that the transfer management data for the image in the 102 IMAGE folder has not yet been read out of the volatile memory 105.

[0074] In step S700, the microcomputer 104 determines whether the processing required to update the transmission management data has been performed. This embodiment will describe the completion of the transmission of IMG_5000.jpg in the IMAGE folder to the FTP server.

[0075] In step S701, the microcomputer 104 identifies the folder where the object whose transmission management data needs to be updated is recorded. Here, the transmission management data for IMG_5000.jpg in the 102 IMAGE folder will be updated, and therefore the 102 IMAGE folder is the corresponding folder.

[0076] In step S702, the microcomputer 104 confirms whether the transfer management data in the corresponding folder (i.e., the 102 IMAGE folder) has been read into the non-volatile memory 105. If the file has been read, the microcomputer 104 moves the sequence to step S704; if the file has not been read, it moves the sequence to step S703.

[0077] Here, as described above, the transfer management data in the 102 IMAGE folder has not yet been read out to the non-volatile memory 105, and therefore is determined to be no in step S702, and the sequence moves 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 indicated by 801, there is a single transfer management file, and therefore if the transfer management file is large, it may not be possible to read all the data to the volatile memory 105. Therefore, in the data 801 in the recording medium 111, only the data corresponding to the 102 IMAGE folder is read from the recording medium 111 to the volatile memory 105. Figure 8B The 802 in the code indicates this status.

[0079] In step S704, the microcomputer 104 updates the transfer management data for the corresponding object. In this embodiment, because the transfer of IMG_5000.jpg from the IMAGE folder in 102 to the FTP server is complete, therefore... Figure 8BAs indicated by error 803, the area managing the transfer status of IMG_5000.jpg to the FTP server has been updated from "Not Transferred" to "Transfer Completed".

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

[0081] In step S706, the microcomputer 104 checks whether the power supply to the camera device 100 has been turned off. If the power supply is off, the microcomputer 104 performs processing to shut down the camera device 100. If the power supply is not turned off, the sequence returns to step S700 and waits for processing to update the transmission management data.

[0082] According to this embodiment, the transfer management data in a single file is segmented into folders. This allows transfer management data to be read from or written to the recording medium for each folder-based segment. By managing data at the folder level, when data is loaded into the volatile memory 105, space can be prepared in the volatile memory 105 according to the number of photos that can be saved in each folder. Therefore, even when the number of images undergoing transfer management increases, transfer management functionality can be provided with limited resources, preventing a decrease in user availability.

[0083] This embodiment has described an example of segmenting image transfer data into folders, reading it from the recording medium 111 to the volatile memory 105, and then writing it from the volatile memory 105 back to the recording medium 111. However, the unit for segmenting the data is not limited to folders. For example, a certain number of images can be set as in the second embodiment, and this number can be used as the unit to determine the segmentation. There are no particular limitations on the segmentation method.

[0084] Fourth embodiment Figure 9A and Figure 9B This is a flowchart illustrating the transmission management data control performed when managing transmission management data in units of folders according to the fourth embodiment, in which folders that are estimated to be highly likely to be accessed are given priority.

[0085] Here, it is assumed that images are captured and management files are transmitted in the form of, for example... Figure 10 The states indicated by 1000 are stored in the recording medium 111.

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

[0087] The function for playing back images is a feature of the camera device. There is also a function for displaying the latest captured image as the image to be played back when a playback command is received. The description in this embodiment assumes that the latest captured image is the image to be played back. It is also assumed that when a new image is captured, it is saved as IMG_0004.jpg in the 104 IMAGE folder. Furthermore, it is assumed that transmission management files 100_Trans to 104Trans, used to manage transmission status in folder units, exist in the recording medium 111 as transmission management files storing transmission management data for the captured images.

[0088] This embodiment also assumes that when transfer management data is read from recording medium 111 to volatile memory 105, multiple areas in volatile memory 105 (volatile memory 105 has multiple storage areas) are prepared. 1001 indicates an example of this. 1001 indicates that areas are prepared in volatile memory 105 to hold the three transfer management data items read from recording medium 111. The process described below when IMG_0001.jpg from folder 100 IMAGE, IMG_0002.jpg from folder 101 IMAGE, and IMG_0003.jpg from folder 102 IMAGE are transferred to an FTP server from this state will be described as an example.

[0089] In step S900, the microcomputer 104 identifies the folder where the newly captured image is to be saved. As described above, in this embodiment, the newly captured image is saved as IMG_0004.jpg in the 104 IMAGE folder, and therefore the folder identified in step S900 is the 104 IMAGE folder.

[0090] In step S901, the microcomputer 104 reads the transfer management data of the folder (here, the 104IMAGE folder) where the newly captured images are to be saved into the volatile memory 105.

[0091] In step S902, the microcomputer 104 reads the transfer management file 104_Trans from the recording medium 111 into the volatile memory 105. 1002 indicates the current state of the volatile memory 105. Of the three regions in the volatile memory 105, one region is being used by data from a single transfer management file 104_Trans.

[0092] In step S902, the microcomputer 104 determines whether the process requiring updating transmission management data has already been performed. If the process requiring updating transmission management data has already been performed, the microcomputer 104 moves the sequence to step S903; otherwise, the process of step S902 is repeated.

[0093] This embodiment assumes that IMG_0001.jpg in the 100 IMAGE folder has been transferred to the FTP server in step S902.

[0094] In step S903, the microcomputer 104 identifies the folder containing the object whose management data needs to be updated. Here, this is 100 IMAGE.

[0095] In step S904, the microcomputer 104 confirms whether the transfer management data in the corresponding folder has been read into the volatile memory 105. If the data has been read, the microcomputer 104 moves the sequence to step S905; otherwise, it moves the sequence to step S908.

[0096] In the state of the volatile memory 105 indicated by 1002, the transfer management file 100_Trans, which manages the transfer management data of 100 IMAGE as a file, has not yet been read out of the volatile memory 105. Therefore, it is determined that no in step S904, and then the sequence moves to step S908.

[0097] In step S908, the microcomputer 104 checks whether the volatile memory 105 has space for reading and transmitting management data. If such space exists, the microcomputer 104 moves the sequence to step S909, and if such space does not exist, the microcomputer 104 moves the sequence to step S910.

[0098] In the current state of the volatile memory 105 indicated by 1002, two of the three regions are empty, and thus it is determined to be empty in step S908, after which the sequence moves to step S909.

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

[0100] 1003 indicates the state of volatile memory 105 after being read. Two of the three regions are in use.

[0101] In step S905, the microcomputer 104 updates the transmission management data for the corresponding object. The update of the transmission management data is performed in the same manner as in the previous embodiments, and therefore will not be described again here.

[0102] In step S906, the microcomputer 104 checks whether the power is off. If the power is off, in step S907, the microcomputer 104 writes the transfer management data of the corresponding folder to the recording medium 111 and ends the operation. In this embodiment, the power is not off in step S906, so the determination is negative in step S906, and then the microcomputer 104 returns to step S902.

[0103] Assuming this state, IMG_0002.jpg in the 101 IMAGE folder is transferred to the FTP server. When the transfer of IMG_0002.jpg is complete, it is determined in step S902 that yes, and then the microcomputer 104 moves the sequence to step S903.

[0104] In step S903, the microcomputer 104 identifies the folder containing the object whose management data needs to be updated. Here, this is IMAGE 101.

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

[0106] Since the transfer management file 101_Trans has not yet been read into the volatile memory 105, it is determined to be no in step S904, and then the microcomputer 104 moves the sequence to step S908.

[0107] In step S908, the microcomputer 104 checks whether the volatile memory 105 has sufficient space to read the transfer management file 101_Trans. As indicated by 1003, one remaining area is empty, therefore it is determined to be yes in step S908; then, in step S909, the microcomputer 104 reads the transfer management file 101_Trans into the volatile memory 105. The state of the volatile memory 105 at this time is the state indicated by 1004. All three areas are in use.

[0108] In step S905, the microcomputer 104 updates the transmission management data of IMG_0002.jpg in the IMAGE folder of 101, moves the sequence to step S906, and returns the sequence to step S902 because the power is not turned off.

[0109] Assuming this state, IMG_0003.jpg in the 102 IMAGE folder is transferred to the FTP server. When the transfer of IMG_0003.jpg is complete, it is determined in step S902 that yes, and then the microcomputer 104 moves the sequence to step S903.

[0110] In step S903, the microcomputer 104 identifies the folder containing the object whose management data needs to be updated. Here, this is IMAGE 102.

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

[0112] Since the transfer management file 102_Trans has not yet been read into the volatile memory 105, it is determined to be no in step S904, and then the microcomputer 104 moves the sequence to step S908.

[0113] In step S908, the microcomputer 104 checks whether the volatile memory 105 has space for reading the transfer management file 102_Trans. The current state of the volatile memory 105 is indicated by 1004. In this case, as indicated by 1004, all three areas of the volatile memory 105 are in use, therefore it is determined that there is no space. Therefore, the determination is negative in step S908, and the microcomputer 104 then moves the sequence to step S910.

[0114] In step S910, the microcomputer 104 writes the oldest transfer management data from the folders other than the folder containing the newly captured images to the recording medium 111, thereby freeing up the volatile memory 105. The folder containing the newly captured images is 104 IMAGE. Therefore, the transfer management file 104_Trans is not moved to the recording medium 111.

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

[0116] In this embodiment, the earlier read transfer management file 100_Trans from volatile memory 105 is determined to be older, and therefore the data of transfer management file 100_Trans is written back to recording medium 111, thereby releasing volatile memory 105. The state of volatile memory 105 after this process is indicated by 1005. The portion that has stored transfer management file 100_Trans is released, so two of the three regions are in use.

[0117] In step S909, the microcomputer 104 reads the transfer management data of the corresponding folder onto the recording medium 111. In other words, the transfer management file 102_Trans is read into the volatile memory 105. The state of the volatile memory 105 at this time is indicated by 1006. The transfer management file 102_Trans is read, and therefore all three areas of the volatile memory 105 are in use. The subsequent processing is the same as the process described above, and therefore will not be described again here.

[0118] Although this embodiment has used the example of considering the folder containing newly captured images as a folder with a high probability of being accessed to describe the sequence, the folder with a high probability of being accessed is not limited to this.

[0119] There are also camera devices that store newly captured images and last played-back images separately. In this case, the folder containing the played-back images can be considered a folder with a high probability of being accessed. There are also functions that store still images and moving images in separate folders. In this case, folders with a high probability of being accessed can be defined for both still images and moving images. In this embodiment, the method for determining folders with a high probability of being accessed is defined based on various product specifications.

[0120] Additionally, in step S910, the oldest item in the management data, excluding the management data corresponding to folders with a high probability of being accessed, is selected as the object to be released from the volatile memory 105. However, this item can be the oldest read item, or an item accessed after being read can be the oldest item. There are no particular limitations on the method used to determine which transfer data to delete from the volatile memory 105, excluding folders with a high probability of being accessed.

[0121] This embodiment describes a control system in which, when managing transfer management data in folders, transfer management files in folders with a high probability of being accessed are kept read into volatile memory 105, while other transfer management data is released. This control reduces the frequency of reading data into volatile memory 105 when writing transfer management data to recording medium 111. This reduces the processing load.

[0122] Other embodiments The present invention can also be implemented by supplying a program that implements one or more functions of the above embodiments to a system or device via a network or via a storage medium, and then causing one or more processors of the computer of the system or device to read and execute the program. The present invention can also be implemented by circuitry (e.g., an ASIC) for implementing one or more functions.

[0123] This invention is not limited to the embodiments described above, and various changes and modifications can be made within the spirit and scope of this invention. Therefore, in order to inform the public of the scope of this invention, the following claims are made.

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

Claims

1. An image pickup apparatus characterized by comprising: including: a recording section for recording a captured image to a recording medium; and a transmitting section for transmitting an image recorded in the recording medium to an external device, wherein the recording section records management data as data for each image folder recorded in the recording medium to the recording medium, the management data being used to manage an image transmission state relating to transmission to the external device by the transmitting section.

2. The apparatus according to claim 1, wherein further including a storage section for storing the management data, wherein the storage section reads out the management data from the recording medium, and writes the management data back to the recording medium after updating the management data in accordance with the image transmission state.

3. The apparatus according to claim 2, wherein The recording section records the management data as a management file for each image folder to the recording medium.

4. The apparatus according to claim 3, wherein The storage section reads out the management file from the recording medium for each image folder, and writes the management file back to the recording medium after updating the management file in accordance with the image transmission state.

5. The apparatus according to claim 2, wherein The recording section records the management data as a management file for each group of a predetermined number of images to the recording medium.

6. The apparatus according to claim 5, wherein The storage section reads out the management file from the recording medium for each group of the predetermined number of images, and writes the management file back to the recording medium after updating the management file in accordance with the image transmission state.

7. The apparatus according to claim 2, wherein The recording section records the management data as a management file having segments for each image folder to the recording medium.

8. The apparatus according to claim 7, wherein The storage section reads out the management data from the recording medium for each segment, and writes the management data back to the recording medium after updating the management data in accordance with the image transmission state.

9. The apparatus according to claim 7, wherein The management file is a single file.

10. The apparatus according to claim 2, wherein The storage section has a plurality of storage areas.

11. The apparatus according to claim 10, wherein In a case where the management data is stored in all of the plurality of storage areas and management data corresponding to another image folder needs to be updated, the storage section clears an area for storing management data other than management data corresponding to a priority image folder from the plurality of storage areas, and stores the management data that needs to be updated.

12. The apparatus according to claim 11, wherein The priority image folder is a folder in which a newly captured image is recorded.

13. The apparatus according to claim 11, wherein The priority image folder is a folder in which a playback image is saved.

14. A control method for an image pickup apparatus, the control method characterized by comprising: a recording step for recording a captured image to a recording medium; and a transmitting step for transmitting an image recorded in the recording medium to an external device, wherein in the recording step, management data is recorded as data for each image folder recorded in the recording medium to the recording medium, the management data being used to manage an image transmission state relating to transmission to the external device by the transmitting step.

15. A program which causes a computer to function as each section of the image pickup apparatus according to any one of claims 1 to 13.

Images