Communication device, control method for communication device, and program

Abstract

To improve efficiency of transmission of metadata files related to video files.SOLUTION: When a notification from an imaging device is a notification indicating that recording of a video is continued from reception of a recording instruction from a user by the imaging device until the imaging device receives a recording terminating instruction, and split video files generated by a first recording method for generating split video files for every predetermined time or predetermined size have been generated, control is performed to request the split video files. When the notification is a notification indicating that metadata files corresponding to the split video files have been generated, control is performed not to request the metadata files. When the notification is a notification indicating that metadata files corresponding to the split video files have been updated, control is performed to request the metadata files.SELECTED DRAWING: Figure 7

Description

[Technical field]

[0001] The present invention relates to a communication device that can be connected to an external device via wireless communication. [Background technology]

[0002] There is a known technology in which an imaging device such as a digital video camera is equipped with a wireless communication function, and a video input from the imaging device is divided into predetermined time segments, recorded, and then a video file is generated and transmitted to an external device (Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2003-134435 A Summary of the Invention [Problem to be solved by the invention]

[0004] In the above-mentioned Patent Document 1, when a video file that is recorded in segments is generated, an associated metadata file is also generated. However, in the case of a video file that is recorded in segments as in Patent Document 1, some information can be grasped only when the entire video is generated. In addition, the file is divided to realize smooth communication, and it is not necessary to handle the divided files in the device that has finished receiving them. In other words, it is inefficient to send and receive metadata files associated with a video file every time they are generated. [Means for solving the problem]

[0005] In order to solve the above problem, the communication device of the present invention has a receiving means for receiving a notification from an imaging device and a control means, and when the notification is a notification indicating that the imaging device continues video recording from the time it receives a recording instruction from a user until it receives an instruction to end recording, and that split video files have been generated using a first recording method in which split video files are generated every predetermined time or predetermined size, the control means controls the imaging device to request the split video files in response to receiving the notification, when the notification is a notification indicating that metadata files corresponding to the split video files have been generated, the control means controls the imaging device not to request the metadata file in response to receiving the notification, and when the notification is a notification indicating that the metadata files corresponding to the split video files have been updated, the control means controls the imaging device to request the metadata file in response to receiving the notification. Effect of the Invention

[0006] According to the present invention, the transmission of metadata files related to video files can be made more efficient. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a conceptual diagram showing a system configuration according to a first embodiment. [Diagram 2] 1 is a block diagram showing the configuration of an imaging apparatus 100 according to a first embodiment. [Diagram 3] 1 is a block diagram showing a configuration of a communication device 200 according to a first embodiment. [Figure 4] FIG. 4 is a diagram for explaining features of chunk recording in the first embodiment. [Diagram 5] 5 is an example of a screen of a transfer application controlled by the communication device 200 in the first embodiment. [Figure 6] 5 shows a process sequence for transferring a chunk recording file between the imaging device 100, the communication device 200, and the server 300 in the first embodiment. [Figure 7] 6 shows a processing flow of the communication device 200 in transferring a chunk recording file and a metadata file in the communication device 200 according to the first embodiment. [Figure 8] 6A to 6C show examples of a list of chunk recording files and metadata files transferred by the communication device 200 in the first embodiment, and a screen example of a transfer application after the transfer. [Figure 9] 13A to 13C are examples of screens of a list of chunk recording files and metadata files and a transfer application displayed on the communication device 200 according to the second embodiment. [Figure 10] 10 shows a processing sequence for determining whether or not a metadata file can be edited between the imaging device 100 and the communication device 200 in the second embodiment. [Figure 11] 10 is a processing flow of the communication device 200 regarding whether or not a metadata file of the communication device 200 in the second embodiment can be edited. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

[0009] The embodiment described below is an example of a means for realizing the present invention, and may be appropriately modified or changed depending on the configuration of the device to which the present invention is applied and various conditions. Also, each embodiment may be appropriately combined.

[0010] [First embodiment] <System configuration> FIG. 1 is a schematic diagram for explaining the system configuration of the present invention.

[0011] In Fig. 1, 100 is an imaging device such as a digital video camera. 200 is a communication device as a mobile terminal, which is an information processing device with a communication function such as a smartphone or a computer. 300 is a server, which is an image storage device installed at the connection destination via a communication network such as the Internet.

[0012] 1, the imaging device 100 and the communication device 200 are connected by wired communication or wireless communication via a connection means such as a wired cable or Wi-Fi, and a video file and a metadata file generated by the imaging device 100 can be transferred to the communication device 200. The communication device 200 and the server 300 are connected via a communication means such as mobile data communication, and information stored in the communication device 200 can be transferred to the server 300 by communication such as FTP.

[0013] Note that the system configuration is not limited to this. For example, the imaging device 100, the communication device 200, and the server 300 may be connected to the same network via an access point without using mobile data communication, and file transfer processing between each device may be realized.

[0014] <Configuration of imaging device> 2A is a block diagram showing an example of the hardware configuration of an imaging device 100 according to the present embodiment. Note that, although a digital video camera is described here as an example of an imaging device, the imaging device is not limited to this. For example, the imaging device may be an information processing device such as a portable media player, a so-called tablet device, or a personal computer.

[0015] The control unit 101 is one or more processors that control each unit of the imaging device 100 in accordance with input signals and programs described below. Note that instead of the control unit 101 controlling the entire device, the entire device may be controlled by multiple hardware devices sharing the processing.

[0016] The imaging unit 102 is composed of, for example, an optical system that controls an optical lens unit, an aperture, zoom, focus, etc., and an imaging element for converting light (image) introduced through the optical lens unit into an electrical image signal. As the imaging element, a complementary metal oxide semiconductor (CMOS) or a charge coupled device (CCD) is generally used. Under the control of the control unit 101, the imaging unit 102 converts the subject light imaged by the lens included in the imaging unit 102 into an electrical signal using the imaging element, performs noise reduction processing, etc., and outputs the digital data as video data. In the imaging device 100 of this embodiment, the video data is recorded on a recording medium 110.

[0017] The non-volatile memory 103 is an electrically erasable and recordable non-volatile memory, and stores programs executed by the control unit 101, which will be described later, meta template information, and the like.

[0018] The working memory 104 is used as a buffer memory for temporarily storing moving image data captured by the imaging unit 102, a memory for displaying moving images on the display unit 106, a working area for the control unit 101, and the like.

[0019] The operation unit 105 is used to receive instructions from the user to the imaging device 100. The operation unit 105 includes, for example, a power button for the user to instruct ON / OFF of the power supply of the imaging device 100, a release switch for instructing start / stop of shooting, and a playback button for instructing playback of video data. It also includes operation members such as a dedicated connection button for starting communication with an external device via a communication unit 111 described later. The operation unit 105 also includes a touch panel formed on a display unit 106 described later.

[0020] The display unit 106 displays a viewfinder image during shooting, displays shot video data, displays characters for interactive operations, etc. The display unit 106 does not necessarily have to be built into the imaging device 100. The imaging device 100 can be connected to an internal or external display unit 106, and it is sufficient that the imaging device 100 has at least a display control function for controlling the display of the display unit 106.

[0021] The voice input unit 107 is a device for inputting voice information, and the voice data converted from the voice information by the voice input unit 107 is recorded on the recording medium 110 in a voice file format.

[0022] The recording medium 110 can record the video data output from the imaging unit 102 and the audio data output from the audio input unit 107. The recording medium 110 of this embodiment has two slots. When the control unit 201 performs calculations on the video data obtained from the imaging unit 202, the control unit 201 records a high-resolution video file (hereinafter referred to as a main video file) designated by the user, such as the resolution of an image sensor (not shown) of the imaging unit 202, in the first slot of the recording medium 110. Furthermore, a low-resolution or low-bitrate video file (hereinafter referred to as a proxy video file) for transmission from the communication unit 111 described later to the communication device 200 via a network can be generated and recorded in the second slot of the recording medium 110. Furthermore, the recording medium 110 records a template of a metadata file. When video data is recorded on the recording medium 110, the control unit 101 can generate a new metadata file by adding information such as the recording time of the video file to the template of the metadata file and record the file on the recording medium 110. At this time, it is preferable that the file name of the video file and the file name of the new metadata file are the same so that they can be linked. The recording medium 110 may be configured to be detachable from the imaging device 100, or may be built into the imaging device 100. In other words, it is sufficient for the imaging device 100 to have at least a means for accessing the recording medium 110.

[0023] The communication unit 111 is an interface for connecting to an external device. The imaging device 100 of this embodiment can exchange data with the external device via the communication unit 111. For example, moving image data generated by the imaging unit 102 and audio data generated by the audio input unit 107 can be transmitted to the external device via the communication unit 111. In this embodiment, the communication unit 111 includes an interface for communicating with the external device via a so-called wireless LAN in accordance with the IEEE802.11 standard. The communication unit 111 also includes a USB interface using a USB (Universal Serial Bus) cable with the external device. The control unit 101 realizes wireless communication and wired communication with the external device by controlling the communication unit 311.

[0024] The communication unit 111 of the imaging device 100 in this embodiment has an access point mode (hereinafter, AP mode) in which the imaging device 100 operates as an access point in infrastructure mode. Furthermore, the communication unit 111 has a client mode (hereinafter, CL mode) in which the imaging device 100 operates as a client in infrastructure mode. By operating the communication unit 111 in the CL mode, the imaging device 100 in this embodiment can operate as a CL device in infrastructure mode. When the imaging device 100 operates as a CL device, it can connect to a surrounding AP device and participate in a network formed by the AP device. Furthermore, by operating the communication unit 111 in the AP mode, the imaging device 100 in this embodiment can also operate as a simple AP (hereinafter, simple AP), which is a type of AP but has more limited functions. When the imaging device 100 operates as a simple AP, the imaging device 100 forms a network by itself. Devices surrounding the imaging device 100 recognize the imaging device 100 as an AP device and can participate in the network formed by the imaging device 100. It is assumed that the program for operating the image capturing apparatus 100 as described above is stored in the non-volatile memory 103 .

[0025] Note that, although the imaging device 100 in this embodiment is a type of AP, it is a simple AP that does not have a gateway function for transferring data received from a CL device to an Internet provider, etc. Therefore, even if data is received from another device participating in a network formed by the imaging device, the data cannot be transferred to a network such as the Internet.

[0026] Next, the external appearance of the imaging device 100 will be described. Fig. 2(b) is a diagram showing an example of the external appearance of the imaging device 100. The release switch 105a, zoom lever 105b, playback button 105c, and touch panel 105d are operation members included in the above-mentioned operation unit 105. In addition, a moving image obtained as a result of imaging by the imaging unit 102 is displayed on the display unit 106.

[0027] The imaging device 100 has been described above.

[0028] <Hardware Configuration of Communication Device 200> 3 is a block diagram showing an example of a hardware configuration of the communication device 200 of the present embodiment. Note that, although a portable mobile terminal is described here as an example of the communication device 200, the communication device 200 is not limited to this. For example, the communication device 200 may be a digital video camera with a wireless function, a tablet device, a personal computer, or the like.

[0029] The control unit 201 controls each unit of the communication device 200 in accordance with input signals and a program described below. Note that instead of the control unit 201 controlling the entire device, the entire device may be controlled by multiple hardware devices sharing the processing.

[0030] The imaging unit 202 converts the subject light imaged by the lens included in the imaging unit 202 into an electric signal, performs noise reduction processing, etc., and outputs the digital data as video data. The captured video data is stored in a buffer memory, and then the control unit 201 performs a predetermined calculation on the captured video data and records it on the recording medium 210.

[0031] The non-volatile memory 203 is an electrically erasable and recordable non-volatile memory. In the non-volatile memory 203, an OS (operating system) which is basic software executed by the control unit 201 and applications which cooperate with the OS to realize applied functions are recorded.

[0032] In this embodiment, the non-volatile memory 203 stores a transfer application (hereinafter, a transfer app) for communicating with the imaging device 100 and the server 300.

[0033] Also stored are a file management application (hereinafter referred to as a file management app) and an image management application (hereinafter referred to as an image management app) for managing moving image files and audio files output from the imaging device 100.

[0034] The working memory 204 is used as an image display memory for the display unit 206, a working area for the control unit 201, etc. In this embodiment, when a video file or a metadata file received from the imaging device 100 is transferred to the server 300, the working memory 204 is temporarily stored therein.

[0035] The operation unit 205 is used to receive instructions from a user for the communication device 200. The operation unit 205 includes, for example, an operation member such as a power button for a user to instruct to turn on / off the power of the communication device 200, and a touch panel formed on the display unit 206.

[0036] The display unit 206 displays video data, characters for interactive operations, etc. The display unit 206 does not necessarily have to be included in the communication device 200. The communication device 200 only needs to be able to connect to the display unit 206 and have at least a display control function for controlling the display of the display unit 206.

[0037] The recording medium 210 can record image data output from the imaging unit 202. The recording medium 210 may be configured to be detachable from the communication device 200, or may be built into the communication device 200. In other words, the communication device 200 only needs to have at least a means for accessing the recording medium 210.

[0038] The communication unit 211 is an interface for communicating with an external device. The communication device 200 of this embodiment can exchange data with the imaging device 100 and the server 300 via the communication unit 211. In this embodiment, the communication unit 211 is an antenna, and the control unit 101 can connect to the imaging device 100 via the antenna. Note that the imaging device 100 and the server 300 may be connected directly or via an access point. As a protocol for communicating data, for example, PTP / IP (Picture Transfer Protocol over Internet Protocol) via a wireless LAN can be used.

[0039] The communication unit 211 also includes a Universal Serial Bus (USB) interface via a USB cable to connect to an external device. Note that communication with an external device is not limited to this. For example, the communication unit 211 may include a wireless communication module such as an infrared communication module, a Bluetooth (registered trademark) communication module, or a Wireless USB.

[0040] The public network connection unit 213 is an interface used when performing public wireless communication. The communication device 200 can make a call with another device via the public network connection unit 213. At this time, the control unit 201 inputs and outputs an audio signal via the microphone 214 and the speaker 215 to realize the call.

[0041] The communication device 200 of this embodiment can also exchange data with the server 300 via the public network connection unit 213. The public network connection unit 213 is an antenna, and the control unit 101 can connect to the public network via the antenna. It is also possible to use one antenna as both the communication unit 211 and the public network connection unit 213. Generally, the communication speed is faster in communication via the communication unit 211 than in communication via the public network. Therefore, in the communication device 200 of this embodiment, communication via the communication unit 211 is prioritized when no call is being made.

[0042] The above is the description of the communication device 200.

[0043] <Chunk record file description> Next, two methods will be described with reference to Fig. 4, in which the imaging device 100 of this embodiment records a low-resolution and low-bit-rate moving image file in the MP4 file format onto the recording medium 110. Both of these methods are executed in parallel with the recording of the main moving image file.

[0044] When the user presses the release switch 105a of the image capturing device 100, recording starts, and when the user presses the release switch 105a again, recording ends.

[0045] The first method is proxy recording, which records a proxy video file with the same recording time as the main video file. 401 is a proxy video file whose recording time is from the start of recording to the end of recording. In other words, proxy recording is a recording method that generates one proxy video file from the start of recording to the end of recording. In this case, the metadata file 402 is generated in parallel with the generation of the proxy video file 401 at the end of recording.

[0046] In this embodiment, for example, the file name of the proxy video file 401 has the fourth character following "MVI" as "P", followed by a file number and an extension. For example, it is written as "MVIP0001.MP4". In this way, it is possible to know that it is a proxy video file recorded by proxy recording by the last character of the character string excluding the file number and extension of the file name, in other words, the character immediately before the file number. Also, the file name of the metadata file 402 is the same as that of the proxy video file 401 except for the extension, and is written as "MVIP0001.XML". This MVI character string is just an example, and is not limited to three characters.

[0047] Next, as a second method, there is chunk recording, in which proxy movie files divided into small parts are generated and recorded at the timing when a predetermined time has elapsed during movie recording. In this embodiment, each of the divided proxy movie files in the case of chunk recording is a divided movie file or a chunk movie file. For example, a chunk movie file is generated when 30 seconds have elapsed from the timing of starting recording or generating a previous chunk movie file. When 30 seconds have elapsed from the start of recording, the control unit 201 generates a chunk movie file 403a and also generates a metadata file 404. In proxy recording, when a movie file is generated, the recording time of the movie file is added to the metadata file, but in chunk recording, if a movie is being recorded, it is not necessary to add the recording time to the metadata file. Even if the chunk movie file 403a is generated, the movie recording continues, and when 30 seconds have elapsed from generating the chunk movie file 403a, a chunk movie file 403b is generated. In the example of FIG. 4, chunk movie files are recorded at 30-second intervals up to 403b. When the user presses the release switch 105a to instruct the end of recording, a chunk moving image file 403c is generated from the timing when the previous chunk moving image file 403b was generated to the time when the end of recording was instructed. At this time, the control unit 201 updates the metadata file 404 so as to add the recording time from the start of recording to the end of recording to the metadata file 404. In this way, in this embodiment, even in the case of chunk recording, one metadata file is provided for a group of chunk moving image files from the start of recording to the end of recording.

[0048] In this embodiment, for example, the file names in the case of chunk recording are as follows. The chunk movie file 403a generated first has the fourth character following "MVI" as "B" so that it is identified as the starting point (when recording starts) movie file, and is named "MVIB0001.MP4". The chunk movie file 403b generated next has the fourth character following "MVI" as "D" so that it is identified as the middle movie file, and is named "MVID0002.MP4". The chunk movie file 403c generated last has the fourth character following "MVI" as "E" so that it is identified as the ending point (when recording ends) movie file, and is named "MVIE0003.MP4".

[0049] Furthermore, the file name of the metadata file 404 is the same as that of the proxy video file 403a except for the file extension, and is written as "MVIB0001.XML".

[0050] In this embodiment, the naming rule for allocating the fourth character of the file name in this way is used to determine whether it is proxy recording or chunk recording, which will be described later. Also, the fourth character of the chunk movie file generated at the end of recording in chunk recording is set to "E", which is used to determine whether it is the last movie file. In this way, the last character of the file name, in other words the character immediately before the file number, makes it possible to know that it is a chunk movie file recorded by chunk recording, and also to know whether it is the starting movie, middle movie, or ending movie of a series of divided movies.

[0051] Next, the effect of performing chunk recording, which is the second method, in the case of transferring data from the imaging device 100 to the server 300 via the communication device 200 will be described with reference to FIG.

[0052] In the case of proxy recording, since a video file cannot be transmitted while being recorded, it takes time to transmit the proxy video file 401 in addition to the recording time of the proxy video file 401. 405 in Fig. 4(b) is the time required from the start of proxy recording to the completion of transfer of the proxy video file 401.

[0053] In the case of chunk recording, chunk movie files that have already been generated can be transmitted one after another during recording. For example, once chunk movie file 403a is generated, it can be transferred even if the imaging device 100 is recording. In FIG. 4(b), transfer can start earlier than the recording time of proxy movie file 401 by differential time 406. Reference numeral 407 denotes the time from the start of recording to the completion of transmission of the movie file in chunk recording. In this way, there is an advantage that transfer time 407 of chunk recording can be completed earlier by differential time 408 than transfer time 405 of proxy recording.

[0054] In the above description, the time is 30 seconds as an example, but the time is not limited to this. If the communication speed is sufficiently fast, a longer time may be used. Also, the user may be allowed to set any time by operating a menu so that the time can be changed according to the performance of the communication line used.

[0055] Also, the division of a video file may occur when recording a main video. For example, when the file system is FAT32, the upper limit of the file size that the system can recognize is stipulated as 4GByte. Therefore, even if the main video file is being recorded, it is divided before the file size exceeds 4GByte, and a new video file is generated to continue recording. That is, the division of a video by chunk recording may be installed in one device as a function separate from the division based on the upper limit of the file size that the file system can recognize. Note that, in the case of division based on the file size that the file system can recognize, the file name is generated according to the same generation rule as when a new video file is generated, unlike the file name generation rule in the division of a video by chunk recording. That is, the file name is the same up to "MVI", which indicates that it is a video file, and the number following it is incremented to distinguish it.

[0056] <Screen Description> Next, the mode of the transfer application of this embodiment will be described with reference to Fig. 5. Fig. 5 is a schematic diagram showing the display state and functions of the operation screen of the transfer application.

[0057] 5(a), 501 denotes a function selection screen, which is displayed after the transfer application is started and in a state in which the imaging device 100 is connected. The function selection screen 501 includes an in-camera content list display button 502 for selecting a function for displaying files recorded in the imaging device 100. Furthermore, the function selection screen 501 includes an automatic transfer button 503 for selecting a function for automatically transferring a file to the server 300 via the communication device 200 after the file is generated when the imaging device 100 starts recording. Pressing the in-camera content list display button 502 transitions to a transfer selection screen, and pressing the automatic transfer button 503 transitions to an automatic transfer screen.

[0058] In FIG. 5B, reference numeral 504 denotes an automatic transfer screen for displaying a file transferred from the imaging device 100 to the server 300, and transition to this screen occurs when a button 503 is tapped on the screen 501.

[0059] Numeral 505 denotes a button for returning to the previous screen. Numeral 506 denotes the initial screen of the automatic transfer screen 504, which is displayed while no transfer has been performed.

[0060] As described above, the main purpose of the transfer application in this embodiment is to automatically transfer the video file and metadata file recorded by the imaging device 100 to the server 300 via the communication device 200 using the above-mentioned functions. In particular, with regard to the automatic transfer when the recording format of the imaging device 100 is chunk recording, the automatic transfer sequence is optimized to prevent communication of unnecessary metadata files. The automatic transfer function in the imaging device and transfer application in this embodiment handles transmission and reception of proxy video files, and does not transmit or receive the main video file. This is because the main video file has a large data size and takes time to complete communication. However, this is not limited to this. When a line with a sufficiently fast communication speed is used, the main video file may be transmitted and received using the automatic transfer function.

[0061] <Processing sequence between the imaging device 100, the communication device 200, and the server 300> Next, the process of the automatic transfer function of the transfer application of the communication device 200 will be described with reference to FIGS.

[0062] 6 is a diagram showing a procedure for transferring a video file and a metadata file between the imaging device 100, the communication device 200, and the server 300. This procedure is started when a screen 504 is displayed in response to detection of a user tapping an automatic transfer button 503 on the function selection screen 501 in FIG.

[0063] 6, the communications device 200 instructs the imaging device 100 to send a notification when the imaging device 100 generates a video file, generates a metadata file, or updates a metadata file. Although the generation of a metadata file and the update of a metadata file may not be performed depending on the recording process to be executed, since it is unknown at this point what kind of recording process will be executed later by the imaging device 100, the communications device 200 instructs the imaging device 100 to send a notification for both.

[0064] 6, when the user presses the release switch 105a of the imaging device 100, the imaging device 100 starts recording a moving image file. At this time, the process performed by the control unit 101 of the imaging device 100 is branched depending on whether the user operates the operation unit 105 of the imaging device 100 to set the recording format of the imaging device 100 to proxy recording or chunk recording.

[0065] First, a case where chunk recording has been set will be described. In this case, the imaging device 100 continues recording for a predetermined time at T603 in Fig. 6. After the predetermined time has elapsed, the imaging device 100 generates a chunk video file at T604 in Fig. 6.

[0066] When the chunked moving image file is generated in T604, a notification of generation of the chunked moving image file is transmitted from the imaging device 100 to the communication device 200 via the communication unit 111 in T605 of FIG.

[0067] Upon receiving the chunked moving image file generation notification of T605, the communication device 200 transmits a chunked moving image file transmission request to the imaging device 100 via the communication unit 211 in T606 of FIG.

[0068] When the imaging device 100 receives the chunked moving image file transmission request from the communication device 200 at T606, the imaging device 100 transmits the chunked moving image file to the communication device 200 via the communication unit 111 at 607 in FIG. When the communication device 200 completes receiving the chunked moving image file from the imaging device 100 at T607, at T608 in Fig. 6, the communication device 200 records a reception status in the working memory 204. The reception status is, for example, the file name of the received chunked moving image file. The reception status will be described in detail later.

[0069] 6, the communication device 200 starts transferring the chunked video file received in T607 to the server 300 via the communication unit 211. The subsequent processes, except for the process of further transferring the chunked video file to the server, are executed in parallel with the transfer of the chunked video file to the server 300 in T609. For example, the transfer of the chunked video file to the server 300 in T609 is executed in parallel with the processes of T612 to T617.

[0070] After generating the chunk moving image file in T604, the imaging device 100 generates a metadata file for the moving image being recorded by referring to a template of a metadata file recorded on the recording medium 110 in T606 of FIG.

[0071] 6, when the imaging device 100 completes the generation of metadata at T610, the imaging device 100 transmits a notification of the generation of a metadata file to the communication device 200 via the communication unit 111. If the recording format of the imaging device 100 is chunk recording, the communication device 200 does not request the generated metadata file even if it receives a notification of the generation of a metadata file. Note that although the communication device 200 does not request a metadata file, this notification enables the communication device 200 to know that the chunk movie file received at T607 is a chunk movie file accompanied by metadata.

[0072] In addition, for the sake of explanation, the case where the metadata is generated at the timing of T610 has been described as an example here, but the timing of metadata generation is not limited to this. The metadata can be generated at any timing at least after the chunk movie file is generated at T604.

[0073] Next, in T612, moving image recording is continued until a predetermined time has elapsed since the chunk moving image file generation in T604. That is, the processes from T605 to T611 are executed in parallel with the moving image recording that is continued after T604.

[0074] T613 to T618 in FIG. 6 are the same processes as T604 to T609, and therefore description thereof will be omitted. T612 to T618 are loop processes until the user presses the release switch 105a of the imaging device 100. As a result, recording of the moving image itself continues until the loop is terminated, and what would normally be a single moving image file is divided into chunk moving images and sequentially transmitted from the imaging device 100 to the communication device 200. Note that in this embodiment, a metadata file is not generated during this process as in T610. Also, the metadata file is not updated. Also, depending on the status of the line used when transferring to the server 300, it is assumed that the transmission of T609 has not been completed at the time of T617. Also, it is assumed that the transmission of T618 of the previous loop has not been completed at the time of T617, which is repeatedly executed in a loop. In such a case, the chunk moving image file is in a state where transmission is reserved, and is transmitted sequentially.

[0075] When the user presses the release switch 105a of the image capturing apparatus 100, the loop process ends and recording stop process of T619 in FIG. 6 is performed.

[0076] When the recording stop process of T619 is performed, the final chunk video file is generated at T620 in Fig. 6. The processes from T621 to T625 are the same as those from T605 to T609, so the explanation will be omitted.

[0077] After generating the chunk video file at T620, at T626 in FIG. 6, the control unit 101 of the imaging device 100 updates the metadata file generated at T610 by adding the recording time from T602 to T619 and the like.

[0078] After updating the metadata file at T626, the control unit 101 of the imaging apparatus 100 transmits a notification of the update of the metadata file to the communication apparatus 200 via the communication unit 111 at T627 in FIG.

[0079] When the control unit 201 of the communication device 200 receives the update notification of the metadata file from the imaging device 100 at T627, the control unit 201 transmits a transmission request of the metadata file to the imaging device 100 via the communication unit 211 at T628 in FIG.

[0080] When the control unit 101 of the imaging apparatus 100 receives a request to transmit the metadata file from the communication apparatus 200 at T628, the control unit 101 transmits the metadata file to the communication apparatus 200 via the communication unit 111 at T629 in FIG.

[0081] When the control unit 201 of the communication device 200 receives the metadata file from the imaging device 100 at T629, the control unit 201 transmits the received metadata file to the server 300 via the communication unit 211 at T630 in FIG.

[0082] Next, a sequence when the recording format of the image capture device 100 is proxy recording will be described.

[0083] In this case, the moving image recording started at T602 continues until the release switch 105a is pressed. When the user presses the release switch 105a of the image capture device 100, the image capture device 100 performs a process of stopping recording at T631 in FIG.

[0084] When the recording stop process of T631 is performed, one proxy video file is generated at T632 in FIG.

[0085] When the proxy video file is generated at T632, a notification of generation of the proxy video file is transmitted from the imaging device 100 to the communication device 200 via the communication unit 111 at T633 in FIG.

[0086] Upon receiving the notification of generation of the proxy moving image file at T633, the communication device 200 transmits a proxy moving image file transmission request to the imaging device 100 via the communication unit 211 at T634 in FIG.

[0087] When the image capture apparatus 100 receives the proxy moving image file transmission request from the communication apparatus 200 at T634, the image capture apparatus 100 transmits the proxy moving image file to the image capture apparatus 200 via the communication unit 111 at 635 in FIG.

[0088] When the communication device 200 completes receiving the proxy video file from the imaging device 100 at T635, at T636 in FIG. 6, the communication device 200 transfers the proxy video file received at T635 to the server 300 via the communication unit 211.

[0089] After generating the proxy video file at T632, the imaging device 100 generates a metadata file for the video being recorded at T637 in Fig. 6 by referring to a template of the metadata file recorded on the recording medium 110. At this time, the metadata file is generated by adding the recording time from T602 to T631 and the like.

[0090] When the control unit 101 of the imaging apparatus 100 generates the metadata file at T637, the control unit 101 transmits a notification of the generation of the metadata file to the communication apparatus 200 via the communication unit 111 at T638 in FIG.

[0091] When the control unit 201 of the communication device 200 receives a notification of the generation of the metadata file from the imaging device 100 at T638, the control unit 201 transmits a request to transmit the metadata file to the imaging device 100 via the communication unit 211 at T639 in FIG.

[0092] When the control unit 101 of the imaging apparatus 100 receives a request to transmit the metadata file from the communication apparatus 200 at T639, the control unit 101 transmits the metadata file to the communication apparatus 200 via the communication unit 111 at T640 in FIG.

[0093] When the control unit 201 of the communication device 200 receives the metadata file from the imaging device 100 at T640, the control unit 201 transmits the received metadata file to the server 300 via the communication unit 211 at T641 in FIG.

[0094] The above describes the procedure from when the transfer application of the communication device 200 transitions to the automatic transfer screen 504 and starts waiting for automatic transfer, until when the video file and metadata file recorded by the imaging device 100 are transferred to the server 300.

[0095] <Processing flow of communication device 200> Next, a processing flow of the communication device 200 for transferring a moving image file and a metadata file recorded by the imaging device 100 to the server 300 will be described with reference to FIG.

[0096] The process flow shown in FIG. 7 is a process that is executed in the transfer application when a tap on the button 503 is detected on the operation unit 205 while the screen 501 in FIG. 6(a) is being displayed.

[0097] 7, the control unit 201 of the communication device 200 transitions the screen display of the transfer application to the automatic transfer standby screen 504. Also, the control unit 201 of the communication device 200 transmits a recording time notification request of T601 to the imaging device 100 via the communication unit 211 so that the imaging device 100 transmits a video file generation notification and a metadata file generation notification and an update notification after the imaging device 100 starts recording. At this time, the control unit 211 of the communication device 200 waits for a notification transmitted from the imaging device 100 via the communication unit 211.

[0098] In S702, the control unit 201 of the communication device 200 determines whether a notification has been received from the imaging device 100 via the communication unit 211. If a notification has not been received, the control unit 201 waits until a notification is received. If a notification has been received, the process branches depending on the type of notification received. In this embodiment, there are three types of notifications received: a video file generation notification of the imaging device 100, a metadata file generation notification, and a metadata file update notification.

[0099] In this embodiment, these notifications are received using the PTP / IP protocol. In S702, the command type of the PTP / IP protocol is analyzed to determine which notification has been received. A video file generation notification and a metadata file generation notification are notified by an object addition notification event. By storing the file name as a parameter in the event data set of this notification, it can be determined that if the file extension is MP4, it is a video file, and if it is XML, it is a metadata file. A metadata file update notification is notified by the event name of an object update notification event. Similarly, the file name is stored in the event data set, and if it is an XML file, it can be determined that it is a metadata file update notification.

[0100] In this embodiment, the file name is stored in the event data set, but the file name may be obtained by obtaining information about the file recorded on the recording medium 110 from the imaging device 100 based on a notification.

[0101] When the control unit 201 receives a video file generation notification, the process proceeds to S703. When the control unit 201 receives a metadata file generation notification, the process proceeds to S708. When the control unit 201 receives a metadata file update notification, the process proceeds to S712.

[0102] First, a case where the control unit 201 of the communication device 200 receives a notification of generation of a moving image file in S702 will be described.

[0103] In S703 of FIG. 7, the control unit 201 of the communication device 200 acquires information from the event data set included in the received notification of generation of the video file.

[0104] In S704 of FIG. 7, the recording format of the imaging device 100 is determined from the information acquired in S703. For example, in this embodiment, the control unit 201 determines whether the recording format is chunk recording or proxy recording from the file name included in the event data set. As described in FIG. 4(a), if the fourth character following "MVI" in the file name is "B", "D", or "E", it can be determined as chunk recording, and if it is "P", it can be determined as proxy recording. However, if the user presses the release switch 105a to end recording within a predetermined time from the start of recording to the generation of the first chunk moving image file, the fourth character of the file name may be "E" indicating the end, rather than "B". Also, if recording is stopped immediately after the generation of the starting moving image file, the fourth character of the file name may be "E" indicating the end, rather than "D" indicating the middle moving image file.

[0105] The method of determining the recording format of the imaging device 100 is not limited to the method of referring to the file name included in the parameters of the event data set included in the notification. For example, the control unit 201 of the communication device 200 may determine the recording format by acquiring the setting value of the recording format of the imaging device 100 via the communication unit 211. The timing of acquiring the setting value of the recording format of the imaging device 100 may be the timing when the communication device 200 connects to the imaging device 100, the timing when the screen transitions to the automatic transfer standby screen 504 in S701, etc.

[0106] Also, if the previous and next chunk movie file names are recorded in the header or footer of each chunk movie file, the determination becomes possible since no similar file names are recorded in the header or footer of the proxy movie file.

[0107] Also, the determination may be made by adding a metadata file to each chunked moving image file indicating that the chunked moving image file constitutes a chunked moving image file.

[0108] Any method may be used as long as the recording format of the image capture device 100 can be obtained within the scope of the gist of the invention.

[0109] In S704, if the control unit 201 of the communication device 200 determines that a chunk moving image is to be generated based on the moving image file generation notification received from the imaging device 100, the process proceeds to S705. If the control unit 201 determines that a proxy moving image is to be generated, the process proceeds to S708.

[0110] In S705, the control unit 201 of the communication device 200 stores the classification of the chunk movie file name included in the event data set of the movie file generation notification received in S704 in the working memory 204. The classification of the chunk movie file name indicates that the character string following "MVI" is either "B" at the beginning, "D" in the middle, or "E" at the end.

[0111] In S706 of FIG. 7, the control unit 201 of the communication device 200 receives and transfers the chunked video file from the imaging device 100. Specifically, first, the control unit 201 of the communication device 200 shown in T606 / T615 / T622 transmits a request to transmit the chunked video file to the imaging device 100 via the communication unit 211. For example, the control unit 201 transmits an object acquisition operation of the PTP / IP protocol. When the control unit 101 of the imaging device 100 receives the request to transmit the chunked video file from the communication device 200, the control unit 201 transmits the chunked video file shown in T607 / T616 / T623 to the communication device 200. The control unit 201 of the communication device 200 receives the chunked video file from the imaging device 100 and temporarily stores it in the working memory 204. When the reception is completed, the control unit 201 of the communication device 200 transmits the chunked video file stored in the working memory 204 to the server 300 via the communication unit 211.

[0112] The display contents of the automatic transfer screen 504 at this time will be described with reference to FIG.

[0113] Reference numeral 801 denotes a status area showing the chunked video files received and being transferred in S706 and their statuses. The lower part of the status area 801 shows chunked video files that have already been transferred and those being transferred.

[0114] 802 is a character string indicating the file name of the chunk video file.

[0115] Reference numeral 803 denotes a component that displays a thumbnail image of a file, and displays a thumbnail image recorded in a moving image file corresponding to the file name 803 .

[0116] 804 is a character string indicating the recording date and time of the file.

[0117] An icon 805 indicates whether a metadata file for the chunk video file exists or not, and is displayed when a notification of the generation of a metadata file (to be described later) is received.

[0118] An icon 806 indicates that the data has been recorded by chunk recording, and is displayed based on the recording format determined by the control unit 201 of the communication device 200 in S704.

[0119] Reference numeral 807 denotes a transfer completion icon that is displayed when the reception and transfer process of S705 is completed.

[0120] Reference numeral 808 denotes a transfer-in-progress icon which indicates that the reception and transfer process of S705 is in progress.

[0121] Returning to the explanation of Figure 7.

[0122] When the reception of the chunked moving image file in S706 is completed, in S707, the control unit 201 of the communication device 200 stores the reception status of the moving image file. For example, if the classification acquired in S705 is the end, a flag indicating that the final chunked moving image file has been received and the file name are stored in the working memory 204.

[0123] When the control unit 201 of the imaging device 200 completes the transmission of the chunked video file to the server 300, the process proceeds to S715.

[0124] When it is determined in S704 that the recording format of the imaging device 100 is proxy recording, in S708, the control unit 201 of the communication device 200 receives a proxy video file from the imaging device 100 via the communication unit 211. Specifically, first, the control unit 201 of the communication device 200 shown in T634 transmits a request to transmit the proxy video file to the imaging device 100 via the communication unit 211. For example, the control unit 201 transmits an object acquisition operation of the PTP / IP protocol. When the control unit 101 of the imaging device 100 receives a request to transmit the proxy video file from the communication device 200, the control unit 201 transmits the proxy video file shown in T635 to the communication device 200. The control unit 201 of the communication device 200 receives the proxy video file from the imaging device 100 and temporarily stores it in the working memory 204. When the reception is completed, the control unit 201 of the communication device 200 transmits the proxy video file stored in the working memory 204 to the server 300 via the communication unit 211.

[0125] When the control unit 201 of the communication device 200 completes the transmission of the proxy video file to the server 300, the process proceeds to S715.

[0126] Next, a case where the notification received by the control unit 201 of the communication device 200 in S702 is a notification of the generation of a metadata file will be described.

[0127] In S709, the control unit 201 of the communication device 200 acquires information from the event data set included in the received notification of the generation of the video file.

[0128] In S710, the recording format of the imaging device 100 is determined from the information acquired in S709. The method of determining whether to perform chunk recording or proxy recording is the same as in S704, and therefore a description thereof will be omitted. If it is determined in S710 that the imaging device 100 is in a state for proxy recording, the process proceeds to S711, and metadata is acquired. On the other hand, if it is determined that the imaging device 100 is in a state for chunk recording, the process proceeds to S715 without going through S711. In other words, the process proceeds to S715 without acquiring metadata.

[0129] In S711, the control unit 201 of the communication device 200 receives and transfers a metadata file from the imaging device 100. Specifically, first, the control unit 201 of the communication device 200 shown in T639 transmits a request to transmit a metadata file to the imaging device 100 via the communication unit 211. For example, an operation of acquiring an object of the PTP / IP protocol is transmitted. When the control unit 101 of the imaging device 100 receives a request to transmit a metadata file from the communication device 200, the control unit 201 transmits a metadata file shown in T640 to the communication device 200. The control unit 201 of the communication device 200 receives the metadata file from the imaging device 100 and temporarily stores it in the working memory 204. When the reception is completed, the control unit 201 of the communication device 200 transmits the metadata file stored in the working memory 204 to the server 300 via the communication unit 211 as shown in T641.

[0130] The display contents of the automatic transfer screen 504 at this time will be described with reference to FIG.

[0131] A status area 801 displays an indication that the metadata file of the proxy movie file is currently being transferred. A file name 809 displays the proxy movie file name corresponding to the metadata file received and being transferred in S711. Since the proxy movie file and the metadata file form a pair, a transfer in progress icon 808 is displayed next to the file name 809 of the proxy movie file.

[0132] When the control unit 201 of the communication device 200 completes the transmission of the metadata file to the server 300, the process proceeds to S715.

[0133] Next, a case will be described where the notification received by the control unit 201 of the communication device 200 in S702 is a metadata file update notification. Note that, when the imaging device 100 is performing chunk recording and the control unit 101 of the imaging device 100 updates the metadata file in T626, the metadata file update notification is transmitted to the communication device 200 via the communication unit 111 in T627.

[0134] In S712 of FIG. 7, the control unit 201 of the communication device 200 reads out from the working memory 204 the reception status stored in S707.

[0135] 7, if the reception status read out in S712 indicates that the last chunked video file has been received, the process proceeds to S714. If the last chunked video file has not been received, the process proceeds to S715.

[0136] In S714 of FIG. 7, the control unit 201 of the communication device 200 receives and transfers a metadata file from the imaging device 100. Specifically, first, the control unit 201 of the communication device 200 shown in T628 transmits a request to transmit a metadata file to the imaging device 100 via the communication unit 211. For example, an operation of acquiring an object of the PTP / IP protocol is transmitted. When the control unit 101 of the imaging device 100 receives a request to transmit a metadata file from the communication device 200, the control unit 201 transmits a metadata file shown in T629 to the communication device 200. The control unit 201 of the communication device 200 receives the metadata file from the imaging device 100 and temporarily stores it in the working memory 204. When the reception is completed, the control unit 201 of the communication device 200 transmits the metadata file stored in the working memory 204 to the server 300 via the communication unit 211 as shown in T630.

[0137] The display contents of the automatic transfer screen 504 after the reception and transfer of the metadata file is completed in S714 will be described with reference to FIG.

[0138] The status area 801 indicates that the transfer of the updated metadata file has been completed, and the transferred chunk movie file and metadata file are displayed at the bottom of the status area 801. In the case of a metadata file transfer, the thumbnail image displayed in the status area 801 indicates that the metadata file was previously stored in the non-volatile memory 203.

[0139] In this embodiment, as a result of executing the processes shown in FIGS. 6 and 7, the chunked moving image file and metadata file recorded by the imaging device 100 on the recording medium 110 will be as shown in the directory entry in FIG. 8(d).

[0140] The directory entry shown in FIG. 8( d ) is made up of a file name 811 , an extension 812 , a creation date and time 813 , and an update date and time 814 .

[0141] A file with the file name 811 being "MVIB0001" and the extension 1102 being "MP4" is a chunked movie file generated in T604. A file with the file name 811 being "MVID0002" and the extension 812 being "MP4" is a chunked movie file generated in T613. A file with the file name 811 being "MVIE0003" and the extension 812 being "MP4" is a chunked movie file generated in T620. A file with the file name 811 being "MVIB0001" and the extension 812 being "XML" is a metadata file generated in T610 and updated in T626. The metadata file is updated by the control unit 101 of the imaging device 100 in T626 when the last chunked movie file is generated in T620, and therefore the update date and time 814 is recorded in the metadata file.

[0142] 7, when the processing of each notification received in S702 is completed, the control unit 201 of the communication device 200 determines whether the user has instructed the end of standby on the automatic transfer screen 504 through the operation unit 205 of the communication device 200. For example, when the user presses the button 505 to return to the previous screen, the automatic transfer screen 504 returns to the function selection screen 501 in FIG. 5(a), and the automatic transfer function is terminated.

[0143] If the user has instructed the automatic transfer screen 504 to end standby, the processing of the flowchart in FIG. 7 is terminated; if the user has not instructed the automatic transfer screen 504 to end standby, the processing proceeds to S702, and the control unit 201 of the communication device 200 waits for a notification from the imaging device 100.

[0144] The above describes a method in which the control unit 201 of the communication device 200 does not request or receive a metadata file when a notification of the creation of a metadata file is received, but does request or receive a metadata file when a notification of the update of the metadata file is received.

[0145] When a chunked video file with a metadata file is transferred to the server 300, efficient communication can be achieved by performing the operation of this embodiment.

[0146] In this embodiment, the metadata file update notification is sent from the imaging device 100 to the communication device 200 only when the first chunk video file is generated, but the recording time, etc. may also be updated and an update notification may be sent when intermediate chunk video files are generated.

[0147] Even if a metadata file update notification is sent when an intermediate chunk video file is generated, no unnecessary communication is performed because S713 in Figure 7 does not request or receive the metadata file if it is not the final chunk video file.

[0148] In this embodiment, the recording format of the imaging device 100 is determined in S704 and S710 to separate the operations, but the present invention is not limited to this. For example, when the function selection screen 501 is displayed, the fact that the recording format of the imaging device 100 has been changed may be acquired, and when the recording format is changed, the function of the automatic transfer button 503 may be switched. For example, when the recording format of the imaging device 100 is proxy recording, the function name of the button 503 may be set to "automatic transfer of proxy video file," and when the recording format is chunk recording, the function name of the button 503 may be set to "automatic transfer of chunk video file." Alternatively, two buttons, "automatic transfer of proxy video file" and "automatic transfer of chunk video file," may be prepared. In this case, in the flowchart of FIG. 7, S704 and S710 may execute only one of the processes, proxy recording or chunk recording, according to the function name of the automatic transfer button 503.

[0149] [Second embodiment] In this embodiment, a method for determining whether or not a metadata file can be edited will be described.

[0150] In the transfer application, the files recorded on the recording medium 110 of the imaging device 100 are displayed in a list on a transfer selection screen described later, and various files to be transferred to the server 300 can be selected, and a metadata file attached to a video file can be edited. However, even if the metadata file is edited to "already generated" while the imaging device 100 is performing chunk recording, the metadata file is updated when recording is completed, and therefore data communication related to editing becomes a wasteful communication.

[0151] Therefore, the main purpose of the transfer app in this embodiment is to provide a function that prevents the metadata file from being edited while the imaging device 100 is performing chunk recording, even if the chunk video file and metadata file are displayed on the transfer selection screen.

[0152] The function of disabling editing of a metadata file while the imaging device 100 in this embodiment is performing chunk recording will be described in detail with reference to Figs.

[0153] The configurations of the image capture device 100 and the communication device 200 are similar to those in the first embodiment, and therefore a description thereof will be omitted.

[0154] The processing of Figures 10 and 11 begins after the control unit 201 of the communication device 200 detects a tap on the in-camera content list display button 502 on the function selection screen 501 of Figure 5(a) via the operation unit 205 and displays the transfer selection screen of Figure 9(a) described below.

[0155] <Explanation about the list display of contents in the camera (transfer selection screen)> First, the transfer selection screen will be described with reference to FIG.

[0156] FIG. 9A is a diagram illustrating a transfer selection screen 901 for a transfer application that is displayed on the display unit 206 of the communication device 200 when the camera internal content list display button 502 in FIG. 5 is pressed.

[0157] Fig. 9(a) is an example in which each file shown in Fig. 8(d) is displayed on a transfer selection screen 905. In this embodiment, it is assumed that the file of the directory entry shown in Fig. 8(d) has already been stored in the recording medium 110 of the imaging device 100.

[0158] Buttons 902 and 903 are for changing the recording medium 110 to be referred to when there are multiple recording media 110 in the imaging device 100. In the example of Fig. 9(a), the recording medium 110 of the button 902 with the underlined text is selected, and a list of files recorded on the recording medium 110 indicated by the button 902, as shown in Fig. 8(d), is displayed.

[0159] Components 904 to 910 in FIG. 9(a) are generated based on list information of files recorded in the connected imaging device 100 and file information of each file.

[0160] Reference numeral 904 denotes a component that displays a thumbnail image of the file. In the case of a moving image file, a thumbnail image recorded in the moving image file is displayed.

[0161] An icon image 905 indicates that the video file is a proxy video file. A proxy video file is a file that has been made lighter by lowering the bit rate and resolution compared to a normal recording file, and in this embodiment, if the fourth character of the file name is "P", "B", "D", or "E", it is determined to be a proxy video file.

[0162] 906 is a character string indicating a file name.

[0163] 907 is a character string indicating the recording date and time of the file.

[0164] The file name 906 is the file name of a chunk moving image file captured in chunk recording by the imaging device 100. The file name 906 shown in Fig. 9(a) displays the file name with "B" as the fourth character, which is the file name at the beginning.

[0165] Reference numeral 908 denotes a metadata file icon indicating whether a metadata file indicating metadata information of a video file exists on the same recording medium 110. When the user taps the metadata file icon 908 via the operation unit 205 of the communication device 200, the control unit 201 detects the tap and opens a metadata file editing screen (not shown), allowing the user to edit the metadata file.

[0166] Reference numeral 909 denotes a file selection status icon indicating whether a file is selected or not, and is displayed superimposed on the thumbnail image 904. When the file selection status icon 909 displays a check mark, it is an icon indicating a selected state. When the file selection status icon 909 does not display a check mark, it is an icon indicating a non-selected state. When the thumbnail image 908 of each file is tapped, the file is switched between selected and non-selected, and the displayed icon is also switched.

[0167] An icon 910 indicates that the chunk video files are recorded by chunk recording. In the directory entry shown in Fig. 8(d), the icon indicates that "MVIB0001.MP4", "MVID0002.MP4", "MVIE0003.MP4", and "MVIB0001.XML" are grouped together.

[0168] Reference numeral 911 denotes a button for starting saving of a file from the imaging device 100 to the communication device 200, and the file to be saved is the previously described selected file.

[0169] Hereinafter, the processing described with reference to FIGS. 10 and 11 will be described assuming that the processing starts from the screen display state of FIG. 9(a).

[0170] <Processing sequence between the imaging device 100 and the communication device 200> FIG. 10 is a diagram showing a processing sequence for displaying a list of moving image files and metadata files between the imaging device 100 and the communication device 200 from when the imaging device 100 starts recording to when it ends the recording.

[0171] First, a sequence in which the imaging device 100 performs chunk recording will be described.

[0172] In FIG. 10, the same sequences as those in FIG. 6 are assigned the same numbers, and the description of these sequences is omitted, and in this embodiment, the differences will be described.

[0173] When the transfer application of the communication device 200 opens the transfer selection screen shown in FIG. 11, the sequence of FIG. 10 starts.

[0174] When the communications device 200 receives the chunked moving image file generation notification of T605, it transmits a chunked moving image file information acquisition request to the imaging device 100 via the communications unit 211 in T1001 of FIG. 10 to request that information about the chunked moving image file be transmitted.

[0175] When the imaging device 100 receives the chunked movie file information acquisition request, in T1002, the imaging device 100 transmits a thumbnail image of the file obtained by analyzing the meta information storage area of ​​the chunked movie file to the imaging device 200 via the communication unit 111. Furthermore, the imaging device 100 transmits chunked movie file information including the recording date and time to the imaging device 200 via the communication unit 111.

[0176] When the communication device 200 completes receiving the chunked moving image file information from the imaging device 100 in T1002, in T1003 of Fig. 10, the communication device 200 updates the display of the transfer selection screen 1105 on the display unit 206. For example, the recording date and time 1110 is updated based on the chunked moving image file information acquired in T1002.

[0177] 10, the communication device 200 updates the display of the transfer selection screen 1105 displayed on the display unit 206. An icon 1117 indicating a non-editable state is displayed in a display area 1108 for video file information that is the target of the metadata file generation notification received in T611. The icon 1117 indicating a non-editable state is displayed because, in the case of chunk recording, the metadata file is updated in T626 (described later), and updating the metadata file in the intermediate state would result in unnecessary communication.

[0178] Since T1005 to T1007 are the same processes as T1001 to T1003, the explanation will be omitted. T612 to T1007 perform loop processing until the user presses the release switch 105a of the imaging device 100. In this embodiment, no metadata file is generated during this processing, unlike T610.

[0179] When the user presses the release switch 105a of the image capturing apparatus 100, the loop process ends and recording stop process of T619 in FIG. 6 is performed.

[0180] Since T1008 to T1010 in FIG. 10 are the same processes as T1001 to T1003, the explanation thereof will be omitted.

[0181] 10, the control unit 201 of the imaging device 200 stores the metadata file received by the imaging device 200 at T629 in the working memory 204, and updates the display of the transfer selection screen 1105 displayed on the display unit 206 of the communication device 200. Here, the icon 1117 indicating an uneditable state in the display area 1108 of the video file information that is the target of the update notification of the metadata file received at T627 is updated to the icon 1115 indicating an editable state. This is because the metadata file is in the final state due to the update of the metadata file in T626 and will not be updated thereafter. At this time, when the icon 1115 in the display area 1108 of the video file information that is the target of the update notification of the metadata file received at T627 is tapped, it is possible to transition to an edit screen for the metadata file (not shown).

[0182] At T1013 in FIG. 10, the user switches to an editing screen for the metadata file using the operation unit 205 of the communication device 200, and editing of the metadata file is accepted.

[0183] At T1014 in FIG. 10, the control unit 201 of the communication device 200 transmits the metadata file edited by the user to the imaging device 100 via the communication unit 211.

[0184] In T1015 of FIG. 10, the imaging device 100 overwrites the metadata file having the matching file name with the metadata file received in T1014.

[0185] Next, a sequence when the recording format of the image capture device 100 is proxy recording will be described.

[0186] When the user presses the release switch 105a of the image capturing apparatus 100, the image capturing apparatus 100 performs a process of stopping recording at T631 in FIG.

[0187] When the imaging device 100 receives a proxy video file information acquisition request from the communication device 200 at T1016, at T1017, the imaging device 100 transmits a thumbnail image of the file obtained by analyzing the meta information storage area of ​​the proxy video file to the imaging device 200 via the communication unit 111. Furthermore, the imaging device 100 transmits proxy video file information including the recording date and time to the imaging device 200 via the communication unit 111.

[0188] When the communication device 200 completes receiving the proxy video file information from the imaging device 100 at T10917, at T1018 in Fig. 10, the communication device 200 updates the display of the transfer selection screen 1105 on the display unit 206. For example, a new video file display area 1108 for transfer selection is generated based on the proxy video file information acquired at T1002.

[0189] Since T1019 to T1022 in FIG. 10 are the same processes as T1012 to T1015, the explanation thereof will be omitted.

[0190] The difference between the sequence in the case of proxy recording and the sequence in the case of chunk recording is that in the case of proxy recording, editing of the metadata file is possible from the notification of the generation of the metadata file, but in the case of chunk recording, this is not possible at the time of notification of the generation of the metadata file.

[0191] In the case of proxy recording, the recording of the moving image file has already been completed at the time of notification of the generation of the metadata file, and the recording time and other information are not overwritten in the final state, so editing may be possible.

[0192] The sequence in which the transfer application of the communication device 200 transitions to the transfer selection screen 1105, permits editing of the metadata file, and updates the metadata file in the imaging device 100 has been described above.

[0193] <Processing flow of communication device 200> Next, a processing flow of the communication device 200 of the present embodiment will be described with reference to FIG.

[0194] The processing flow shown in FIG. 11 is processing that is executed in response to detection of a tap on the camera content list display button 502 on the operation unit 205 while the screen 501 in FIG. 6(a) is being displayed in the transfer application.

[0195] In FIG. 11, the same processes as those in FIG. 7 are assigned the same numbers, and the description of these processes is omitted. In this embodiment, the differences will be described.

[0196] In S1101 of FIG. 11, the control unit 201 of the communication device 200 transitions the screen display of the transfer application to a transfer selection screen 901 shown in FIG. 9(a).

[0197] 9 to transmit various notifications to the imaging device 100 after the imaging device 100 starts recording. At this time, the control unit 211 of the communication device 200 goes into a standby state for notifications to be received from the imaging device 100 via the communication unit 211.

[0198] <When receiving a video file creation notification and recording chunks at S704> A case will be described where the control unit 201 of the communication device 200 receives a notification of generation of a moving image file in S702 and the imaging device 100 performs chunk recording in S704.

[0199] 11, the classification of the chunked video file is acquired and recorded in the working memory 204, and then in S1103, the transfer selection screen 901 is updated. For example, as shown in FIG. 9(b), when the chunked video file "MVID0006.MP4" is generated, the transfer selection screen 901 is as shown in FIG. 9(c).

[0200] An item display area 912 indicates the chunk moving image file being recorded. In the item display area 912, the file name of the start point of the chunk moving image file is displayed.

[0201] An icon 913 indicates that the chunk moving image file displayed in the item display area 912 is being chunk-recorded by the imaging device 100 and that the chunk moving image file is being added. When the imaging device 100 stops recording, the icon is changed to a file selection status icon 909.

[0202] An icon 914 indicates that a metadata file exists in the chunk video file displayed in the item display area 912. This icon is not displayed until the control unit 201 of the communication device 200 receives a notification of the generation of the metadata file and executes S1105 described later.

[0203] <When receiving a video file creation notification and recording proxy in S704> Next, a case will be described in which the control unit 201 of the communication device 200 receives a moving image file generation notification in S702 and the imaging device 100 is performing proxy recording in S704.

[0204] S1102 in Fig. 11 is a process of updating the transfer selection screen when a video file generation notification is received in S702 and the recording format of the imaging device 100 is proxy recording. Specifically, the communication device 200 updates the display of the transfer selection screen 901 on the display unit 206 based on the proxy video file information described in T1017. In the case of proxy recording, for example, as shown in Fig. 9(d), the file name "MVIP0005.MP4" is displayed in the item display area 912, indicating proxy recording. An icon 905 indicating proxy recording and a file selection status icon 909 are displayed on the thumbnail image. The metadata file icon is not displayed until S1104 described later is executed.

[0205] <Metadata file generation notification received> Next, a case will be described where the control unit 201 of the communication device 200 receives a notification of the generation of a metadata file in S702.

[0206] In S710 of FIG. 11, if the recording format is proxy recording, the process proceeds to S1104, and if it is chunk recording, the process proceeds to S1105.

[0207] When the recording format is proxy recording, in S1104 of Fig. 11, a metadata file is received and a metadata file icon 908 is displayed in the item display area 912 shown in Fig. 9(d). The reception of the metadata file has been explained in T638 to T640, and so will not be explained here. When the control unit 201 of the communication device 200 detects a tap on the metadata file icon 908, the control unit 201 opens a metadata file editing screen (not shown) so that the user can edit the metadata file.

[0208] When the recording format is chunk recording, in S1105 of FIG. 11, a metadata file is received and a metadata file icon 914 is displayed in the item display area 912 shown in FIG. 9(c). However, the metadata file icon 914 is indicated as a shaded icon to indicate that editing is not possible because the imaging device 100 is in the middle of chunk recording. The reason why the metadata file is made uneditable is to prevent unnecessary communication because the imaging device 100 performs update processing of the metadata file at the end of recording of the chunk recording, and therefore editing of the intermediate state file will be overwritten. Therefore, even if the control unit 201 detects a tap on the metadata file icon 914, it does not perform any processing, and therefore the metadata file editing screen does not open.

[0209] <Metadata file update notification received> Next, a case will be described where the control unit 201 of the communication device 200 receives a notification of the generation of a metadata file in S702.

[0210] 11, the display of the metadata file icon 914 in the item display area 912 shown in FIG. 9(c) is changed to a metadata file icon 908 indicating that the metadata file can be edited upon reception of the metadata file. The reception of the metadata file has been described in T627 to T629 and will not be described here. Furthermore, when the control unit 201 of the communication device 200 detects a tap on the metadata file icon 908, the control unit 201 opens a metadata file editing screen (not shown) so that the user can edit the metadata file.

[0211] In the above, a method for preventing overwriting of the metadata file of the imaging device 100 from the communication device 200 has been described by not accepting editing of the metadata file by the user from the transfer selection screen 901 before the update process of the metadata file of the imaging device 100. Furthermore, when the imaging device 100 completes chunk recording and updates the metadata file, the user is permitted to overwrite the metadata file from the communication device 200.

[0212] Therefore, even if the metadata file of the imaging device 100 is overwritten from the communication device 200 by user operation, updating of the metadata file due to completion of chunk recording by the imaging device 100 can be prevented, and unnecessary communication can be reduced.

[0213] In this embodiment, editing of the metadata file is permitted when chunk recording of the imaging device 100 is completed, and the communication device 200 completes reception of the metadata file after receiving an update notification of the metadata file. However, when the chunk video file and the metadata file are being transferred, editing of the metadata file may be permitted after the transfer is completed.

[0214] As described above, when a metadata file is attached to a video file recorded in chunks and transmitted to an external device, the automatic file transfer and editing sequence can be optimized, and unnecessary data communication can be prevented.

[0215] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

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

Claims

1. A receiving means for receiving a notification from the imaging device; and a control means, when the notification is a notification indicating that moving image recording is continued from when the imaging device receives a recording instruction from a user until when the imaging device receives an instruction to end recording, and that divided moving image files have been generated using a first recording method in which divided moving image files are generated every predetermined time or every predetermined size, the control means controls the imaging device to request the divided moving image files in response to receiving the notification; When the notification is a notification indicating that a metadata file corresponding to the divided video file has been generated, the control means performs control so as not to request the metadata file from the imaging device in response to receiving the notification; A communication device characterized in that, when the notification is a notification indicating that a metadata file corresponding to the divided video file has been updated, the control means controls the imaging device to request the metadata file in response to receiving the notification.

2. When the notification is a notification indicating that the imaging device continues recording a moving image from when the imaging device receives a recording instruction from a user until when the imaging device receives an instruction to end recording, and that a moving image file has been generated using a second recording method that generates a moving image file based on the moving image data that has been continuously recorded up until that point in response to receiving the instruction to end recording, the control means controls the imaging device to request the moving image file in response to receiving the notification; When the notification is a notification indicating that a metadata file corresponding to the video file has been generated, the control means performs control so as to request the imaging device to generate the metadata file corresponding to the video file in response to receiving the notification.

2. The communication device according to claim 1 .

3. The communication device according to claim 1 , wherein the notification is determined to be a notification indicating that the divided moving image file has been generated, based on the file names of the divided moving image files included in the notification.

4. The communication device according to claim 1 , further comprising: a communication unit configured to receive a notification from the communication unit and transmit the notification to the communication unit; a communication unit configured to receive a notification from the communication unit and transmit the notification to the communication unit;

5. The communication device according to claim 1 , characterized in that, based on the file names of the divided video files included in the notification, it is determined that the notification is a notification indicating that a metadata file corresponding to the divided video file has been updated.

6. The communication device according to claim 1 , wherein the notification is determined to be a notification indicating that the divided video files have been generated based on the file name of the video file included in the notification.

7. The communication device according to claim 1 , characterized in that, based on the file name of the video file included in the notification, it is determined that the notification is a notification indicating that a metadata file corresponding to the divided video file has been generated.

8. 2. The communication device according to claim 1, wherein the divided moving image files and the moving image file are proxy moving image files.

9. The communication device according to claim 8 , wherein a main moving image file corresponding to the proxy moving image file and having a data size larger than that of the proxy moving image file is not received from the imaging device.

10. The received divided video files are sequentially transmitted to a server; The communication device according to claim 1 , wherein the metadata corresponding to the received divided moving images is transmitted to a server after all the divided moving images have been transmitted.

11. The communication device according to claim 1 , wherein the transmission of the received divided video files to a server and the reception of the divided video files are executed in parallel.

12. A receiving step of receiving a notification from the imaging device; a step of controlling the imaging device to request the divided video files in response to receiving the notification, when the notification indicates that the imaging device will continue to record video during the period from when the imaging device receives a recording instruction from a user until when the imaging device receives an instruction to end recording, and that divided video files have been generated using a first recording method that generates divided video files every predetermined time or every predetermined size; when the notification is a notification indicating that a metadata file corresponding to the divided video file has been generated, controlling the imaging device not to request the metadata file in response to receiving the notification; and if the notification is a notification indicating that a metadata file corresponding to the divided video file has been updated, controlling the communication device to request the metadata file from the imaging device in response to receiving the notification.

13. A computer readable program for causing a computer to function as each of the means of the communication device according to claim 1.

Images