Communication device, imaging device, control method, storage medium, and program

Abstract

A communication device includes a storage section for storing a file obtained from a first external device, and for storing first information related to at least one of a creation date and time and an update date and time of the file; and a control section for, in a case where the file obtained from the first external device is a first file to which the first information is attached in the first external device, storing the first file into the storage section and storing the first information of the first file into the storage section, and in a case where the file obtained from the first external device is a second file to which the first information is not attached, obtaining second information related to a recording date and time at which the second file is recorded from the first external device, and overwriting the first information as the second information when storing the second file into the storage section.

Description

Technical Field

[0001] This invention relates to communication equipment, camera equipment, control methods, storage media and programs, and in particular to systems in which external devices and communication equipment are connected in a manner that enables them to communicate with each other. Background Technology

[0002] Patent Document 1 describes a technology for connecting a camera device, such as a digital camera, to an external device, such as a personal computer (PC), so that they can communicate with each other and send the content (including images and sounds) stored in the camera device to the external device.

[0003] In recent years, the mass media industry, including media and telecommunications companies, has faced a growing demand for the rapid delivery of content (including images and sound) captured on-site during news gathering. This has led to the development of content delivery solutions involving various types of network communication. For example, mobile applications for mobile devices offer the ability to send content (including still images, moving images, and sound) generated on camera equipment to mobile devices such as smartphones, and to transmit this content from the mobile device to an external server via a network using communication methods such as File Transfer Protocol (FTP).

[0004] The mobile app displays content stored on the mobile device (such as still images, moving images, and audio) along with file information including thumbnails, filenames, and the date and time of recording, allowing users to categorize them. Furthermore, the app displays files chronologically sorted by recording date and time, and filters to show only files with specific recording dates and times; this enables users to view and select files considering their recording date and time.

[0005] Existing technical documents

[0006] Patent documents

[0007] Patent Document 1: Japanese Patent Application Publication No. 2007-166577 Summary of the Invention

[0008] The problem the invention aims to solve

[0009] Meanwhile, image files, such as still images and moving images, which are a type of audio file, do not have a metadata area describing metadata such as the recording date and time, according to the RIFF waveform audio format (WAV). For this reason, when storing an externally acquired audio file to a mobile device, the recording date and time of that audio file cannot be stored. Therefore, in mobile applications that display, for example, a list of files stored on the mobile device, it is impossible to display files ordered chronologically by recording date and time, or to filter and display only files with specific recording dates and times.

[0010] The present invention was made in view of the above-mentioned problems and achieves the following technology: even if the file obtained from the outside does not include supplementary information such as creation date and time, it can be accurately displayed according to the record date and time of the file.

[0011] Solution for solving the problem

[0012] To address the aforementioned problems, the present invention provides a communication device for communicating with an external device. The communication device comprises: a storage component for storing a file obtained from a first external device, and for storing first information related to at least one of the file's creation date and time and its update date and time; and a control component for: storing the first file in the storage component and storing the first information of the first file in the storage component when the file obtained from the first external device is a first file on the first external device accompanied by the first information; and obtaining second information related to the recording date and time of the second file from the first external device when the file obtained from the first external device is a second file without the first information, and rewriting the first information to the second information when storing the second file in the storage component.

[0013] To address the aforementioned problems, the present invention provides a camera device for communicating with an external device, characterized in that it comprises: a generation component for generating a file; a management component for generating file information including the recording date and time of the file, and storing the file information in a storage component; and a control component for sending the file information including the recording date and time of the predetermined file stored in the management component when a request for obtaining file information of a predetermined file is received from the external device.

[0014] To address the aforementioned problems, the present invention provides a control method for a communication device used to communicate with an external device. The control method comprises the following steps: storing a file obtained from a first external device, and storing first information related to at least one of the file's creation date and time and its update date and time in a storage component; if the file obtained from the first external device is a first file on the first external device accompanied by the first information, storing the first file in the storage component, and storing the first information of the first file in the storage component; and if the file obtained from the first external device is a second file without the first information, obtaining second information related to the recording date and time of the second file from the first external device, and rewriting the first information to the second information when storing the second file in the storage component.

[0015] To address the aforementioned problems, the present invention provides a control method for a camera device used to communicate with an external device. The control method comprises the following steps: generating a file; generating file information including the recording date and time of the file, and storing the file information in a storage component; and, upon receiving a request from the external device to obtain file information for a predetermined file, sending the file information stored in the storage component, including the recording date and time of the predetermined file.

[0016] To address the aforementioned problems, the present invention provides a computer-readable storage medium storing a program for causing a computer to execute the control method described above.

[0017] To address the aforementioned problems, the present invention provides a program for enabling a computer to function as various components of the aforementioned camera device.

[0018] The effects of the invention

[0019] According to the present invention, even if the file obtained from the outside does not include supplementary information such as creation date and time, it can be accurately displayed based on the record date and time of the file.

[0020] 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

[0021] The accompanying drawings, which are included in and form part of this specification, illustrate embodiments and features of the invention and, together with the specification, serve to explain the principles of the invention.

[0022] Figure 1 This is a system structure diagram based on this embodiment.

[0023] Figure 2A This is a block diagram illustrating the structure of the camera device 100 according to this embodiment.

[0024] Figure 2B This is a front view showing the structure of the camera device 100 according to this embodiment.

[0025] Figure 2C This is a rear view showing the structure of the camera device 100 according to this embodiment.

[0026] Figure 3 This is an explanatory diagram of the directory of files stored in the camera device 100 according to this embodiment.

[0027] Figure 4 This is a block diagram illustrating the structure of the mobile device 200 according to this embodiment.

[0028] Figure 5 This is a software structure diagram of the mobile device 200 according to this embodiment.

[0029] Figure 6A This is an illustrative diagram showing the UI of the file transfer application 301 of the mobile device 200 according to this embodiment.

[0030] Figure 6B This is an illustrative diagram showing the UI of the file transfer application 301 of the mobile device 200 according to this embodiment.

[0031] Figure 6C This is an illustrative diagram showing the UI of the file transfer application 301 of the mobile device 200 according to this embodiment.

[0032] Figure 6D This is an illustrative diagram showing the UI of the file transfer application 301 of the mobile device 200 according to this embodiment.

[0033] Figure 6E This is an illustrative diagram showing the UI of the file transfer application 301 of the mobile device 200 according to this embodiment.

[0034] Figure 6F This is an illustrative diagram showing the UI of the file transfer application 301 of the mobile device 200 according to this embodiment.

[0035] Figure 6G This is an illustrative diagram showing the UI of the file transfer application 301 of the mobile device 200 according to this embodiment.

[0036] Figure 7 This is a diagram illustrating the processing sequence of the camera device 100 and the mobile device 200 according to this embodiment.

[0037] Figure 8 This is a flowchart illustrating the processing of the mobile device 200 according to this embodiment.

[0038] Figure 9 This is a flowchart illustrating the processing of the camera device 100 according to this embodiment.

[0039] Figure 10 This is a flowchart illustrating the processing of the mobile device 200 according to this embodiment.

[0040] Figure 11A This is an explanatory diagram of the catalog entries of the mobile device 200 according to this embodiment.

[0041] Figure 11B This is an explanatory diagram of the catalog entries of the mobile device 200 according to this embodiment.

[0042] Figure 12 This is a flowchart illustrating the processing of the mobile device 200 according to this embodiment. Detailed Implementation

[0043] The embodiments will be described in detail below 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 the invention is not limited to requiring all of these features, and multiple features can be appropriately combined. Furthermore, in the drawings, the same reference numerals are assigned to the same or similar configurations, and redundant descriptions are omitted.

[0044] Referring to the accompanying drawings, the following provides a detailed description of the following embodiments: applying the imaging device of the present invention to a camera device such as a digital camera, applying the communication device of the present invention to a mobile device such as a smart device of the type of mobile phone and a tablet device, and applying the information processing device of the present invention to a server that provides various services to a mobile device acting as a client.

[0045] <System Structure>

[0046] First, refer to Figure 1 The system structure according to this embodiment will be explained.

[0047] The system according to this embodiment includes a camera device 100, a mobile device 200, and a server 300. The camera device 100 and the mobile device 200 are connected to each other via a wireless antenna or a wired cable. The camera device 100 can transmit motion image files and sound files generated by the camera device 100 to the mobile device 200. The mobile device 200 and the server 300 are connected to each other via mobile data communication using lines based on 4G / LTE and 5G, etc. The mobile device 200 can use communication methods such as File Transfer Protocol (FTP) to transmit various types of information stored in the mobile device 200 to the server 300.

[0048] Note that the system architecture according to this embodiment is not limited to the example above; for example, the camera device 100, the mobile device 200 and the server 300 can be connected to the same network via an access point without using mobile data communication to realize the processing used for file transfer between discrete devices.

[0049] <Structure of Camera Device 100>

[0050] First, refer to Figure 2A The structure and function of the camera device 100 according to this embodiment will be explained.

[0051] Note that although this embodiment describes a camera device such as a digital camera, it is not intended to be limiting, and the camera device may be an information processing device such as a tablet device and a personal computer equipped with camera functions, a media player, a surveillance camera, and a medical camera.

[0052] The control unit 101 is a central processing unit (CPU) that performs comprehensive control of the entire camera device 100, and implements the communication and control processing described later by executing the program stored in the non-volatile memory 103. Note that instead of the control unit 101, the entire device can be controlled by multiple hardware components handling the processing separately.

[0053] The imaging unit 102 includes a lens assembly comprising a zoom lens and a focusing lens, and a shutter with an aperture function. Furthermore, the imaging unit 102 includes an image sensor, which is configured, for example, with a CCD or CMOS element for converting the image of the subject into an electrical signal; and an A / D converter for converting the analog image signal output from the image sensor into a digital signal. Under the control of the control unit 101, the imaging unit 102 uses the image sensor to convert the light of the subject image formed by the lenses included in the imaging unit 102 into an electrical signal, performs noise reduction processing, and outputs image data composed of digital signals.

[0054] The control unit 101 performs pixel interpolation, resizing (such as reduction), and color conversion processing on the image data captured by the imaging unit 102. Furthermore, the control unit 101 compresses and encodes still image data with applied image processing using JPEG format and encodes moving image data using motion image compression methods such as MP4 format to generate image files, and records these image files onto the recording medium 110. In the camera device 100 according to this embodiment, image data is recorded onto the recording medium 110 according to the Camera File System Design Rules (DCF) standard. Furthermore, the control unit 101 performs predetermined calculation processing using the captured image data, and controls the focusing lens, aperture, and shutter speed of the imaging unit 102 based on the obtained calculation results; as a result, autofocus (AF) processing and auto exposure (AE) processing are performed.

[0055] The non-volatile memory 103 is an electrically erasable and recordable memory; for example, an EEPROM is used here. Constants used in the operation of the control unit 101, as well as programs, are recorded in the non-volatile memory 103. The programs mentioned here refer to programs used to perform the communication and control processes described later in this embodiment.

[0056] The working memory 104 serves as a working area, in which constants and variables used in the operation of the control unit 101, as well as programs read from the non-volatile memory 103, are expanded. Furthermore, the working memory 104 serves as a buffer memory for temporarily storing image data captured by the camera unit 102, and as an image display memory for the display unit 106.

[0057] The operation unit 105 is composed of operating components (such as various types of switches, buttons, and touch panels) for accepting various types of operations from the user. For example, such as Figure 2B and Figure 2C As shown, the operation unit 105 includes a shutter button 105a for capturing images, a playback button 105b for reproducing captured images, and a four-way directional pad 105c consisting of up, down, left, and right buttons for configuring various types of camera settings. Furthermore, a touch panel 105d integrally formed with the display unit 106 described later is also included in the operation unit 105. Additionally, the operation unit 105 includes operation components such as a dedicated connection button for initiating communication with external devices via the communication unit 111 described later.

[0058] Display unit 106 displays viewfinder images during recording, captured images, and characters used for interactive operations. Display unit 106 is, for example, a display device such as a liquid crystal display (LCD) or an organic EL display. Display unit 106 can be configured to be integrated with camera device 100, or it can be an external device connected to camera device 100. It is sufficient for camera device 100 to be able to connect to display unit 106 and have the function of controlling the display displayed by display unit 106.

[0059] The sound input unit 107 uses one or more microphones, either built into the camera device 100 or connected via a sound terminal, to collect sound around the camera device 100 and convert this sound into electrical signals. The sound input unit 107 converts the analog sound signals generated by collecting sound from around the camera device 100 into digital signals and outputs these digital signals to the control unit 101. The control unit 101 generates sound data by performing various types of sound processing on the digital signals generated by the sound input unit 107. The microphone can be a directional microphone or an omnidirectional microphone. The control unit 101 compresses and encodes the sound data generated by the sound input unit 107 using formats such as WAV to generate a sound file, and records the sound file onto the recording medium 110.

[0060] Recording medium 110 records image data output from imaging unit 102 and sound data output from sound input unit 107. Furthermore, control unit 101 reads the image and sound files stored in recording medium 110 in playback mode. Recording medium 110 may be, for example, a memory card or hard disk attached to camera device 100, or a flash memory or hard disk built into camera device 100. It is sufficient for camera device 100 to include at least a means for accessing recording medium 110.

[0061] The communication unit 111 is an interface for connecting to an external device, such as the mobile device 200. The camera device 100 according to this embodiment can exchange data with the external device via the communication unit 111. For example, image data generated by the imaging unit 102 and sound data generated by the sound input unit 107 can be sent to the external device via the communication unit 111. Note that in this embodiment, the communication unit 111 includes an interface for communicating with the external device via a wireless LAN according to the IEEE 802.11 standard. The control unit 101 realizes wireless communication with the external device by controlling the communication unit 111. Note that the communication method is not limited to a wireless LAN, and may include, for example, wireless communication interfaces (such as infrared communication interfaces and wireless USB) and wired communication interfaces (such as USB cables, HDMI (registered trademark), and IEEE 1394).

[0062] Note that the communication unit 111 of the camera device 100 according to this embodiment has an AP mode and a CL mode. In AP mode, the communication unit 111 operates as an access point in the infrastructure mode, and in CL mode, the communication unit 111 operates as a client in the infrastructure mode. Then, by operating the communication unit 111 in CL mode, the camera device 100 according to this embodiment can operate as a CL device in the infrastructure mode. When operating as a CL device, the camera device 100 can join the network formed by surrounding AP devices by connecting to them. Furthermore, by operating the communication unit 111 in AP mode, the camera device 100 according to this embodiment can also operate as a simplified AP (which is a type of AP but more functionally limited) (hereinafter referred to as a simple AP). When the camera device 100 operates as a simple AP, the camera device 100 forms a network independently. Devices around the camera device 100 can recognize the camera device 100 as an AP device and join the network formed by the camera device 100. It is assumed that the program used to make the camera device 100 operate in the manner described above is stored in the non-volatile memory 103.

[0063] Note that the camera device 100 according to this embodiment is a simple AP, but it does not have the gateway function to transmit data received from the CL device to an Internet provider or the like. Therefore, even if the camera device receives data from other devices joining a network formed by the camera device itself, the camera device cannot transmit that data to a network such as the Internet.

[0064] <Directory structure of files stored in recording medium 110>

[0065] Next, refer to Figure 3 To illustrate the directory structure of the files stored in the recording medium 110.

[0066] Recording medium 110 has been formatted using a file system (such as Extended File Allocation Table (exFAT)) that allows reference from the operating system (OS).

[0067] The control unit 101 records the motion image data generated by the camera unit 102 as an MP4 format motion image file in the directory "100_0420" (assuming the last four digits represent the current date) under the "DCIM" directory. Furthermore, based on the metadata template information read from the non-volatile memory 103, the control unit 101 generates metadata files (supplementary information files) that describe the metadata of the motion image files in Extensible Markup Language (XML) format. The metadata is supplementary information for data management at the destination of the motion image data transmission, and information such as category, title, and annotations of the motion image data is entered into the relevant tags of the XML file.

[0068] The control unit 101 records the sound data generated by the sound input unit 107 as a WAV format sound file in the "AUDIO" directory under the "PRIVATE" directory.

[0069] Furthermore, when the camera unit 102 and the audio input unit 107 generate motion image data and audio data, the control unit 101 generates or updates a catalog file for file management in the "GANONMSC" directory under the "DCIM" directory. The catalog file records the filenames of the files stored on the recording medium 110 and file information related to the recording date and time.

[0070] Recording media 110 stores motion picture files recorded in MP4 format, metadata files recorded in XML format, sound files recorded in WAV format, and catalog files used to manage file information for each file.

[0071] <Structure of Mobile Device 200>

[0072] Next, refer to Figure 4 The structure and function of the mobile device 200 according to this embodiment will be explained.

[0073] Although this embodiment describes mobile devices such as smartphones, which are a type of mobile phone, it is not intended to be limiting, and mobile devices may be digital cameras equipped with communication functions, tablet devices, personal computers, wristwatch-type smartwatches, and wearable computers such as glasses-type smart glasses.

[0074] The mobile device 200 according to this embodiment includes a control unit 201, a camera unit 202, a non-volatile memory 203, a working memory 204, an operation unit 205, a display unit 206, a recording medium 210, and a communication unit 211. The basic functions of these components are similar to those of the camera device 100, and their detailed descriptions are omitted.

[0075] The non-volatile memory 203 stores the operating system (OS), which is the basic software executed by the control unit 201, and applications that coordinate with the OS to implement application functions. Furthermore, the non-volatile memory 203 stores applications for communicating with the camera device 100 and the server 300. Additionally, the non-volatile memory 203 stores file transfer applications for communicating with the camera device 100 and the server 300. Furthermore, the non-volatile memory 203 stores a file management application that stores and manages image files such as still image data and moving image data obtained from the camera device 100, as well as metadata files and sound files associated with these image files. Additionally, the non-volatile memory 203 stores an image management application that specifically stores and manages image files such as still image data and moving image data obtained from the camera device 100, as well as metadata files and sound files associated with these image files.

[0076] The processing of the mobile device 200 according to this embodiment is implemented by reading software provided by an application. Note that it is assumed that the application includes software for using the basic functions of the OS installed on the mobile device 200. Note that the OS of the mobile device 200 may include software for implementing the processing in this embodiment.

[0077] Communication unit 211 includes a wireless communication interface for wireless communication with external devices such as camera device 100 and server 300. Control unit 201 realizes wireless communication with external devices by controlling communication unit 211. Note that communication unit 211 can be directly connected to camera device 100 and server 300, or it can be configured to connect to camera device 100 and server 300 via an access point. For example, Picture Transfer Protocol over Internet Protocol (PTP / IP) via wireless LAN can be used as the protocol for data communication. Note that communication with camera device 100 and server 300 is not limited to the foregoing. For example, communication unit 211 may include wireless communication modules such as infrared communication modules, Bluetooth (registered trademark) communication modules, and wireless USB. In addition, wired connection interfaces such as USB cables, HDMI (registered trademark), and IEEE 1394 can be used.

[0078] The public network connection unit 213 is an interface used for wireless communication via a wide area network (WAN) such as 4G / LTE and 5G. The mobile device 200 can communicate with other devices via the public network connection unit 213 for calls or data communication. During a call, the control unit 201 processes the input and output of audio signals via a microphone 214 and a speaker 215. In this embodiment, the public network connection unit 213 is not limited to using 4G / LTE or 5G, and can use other communication methods including local 5G, WiMAX, ADSL, and FTTH. In this embodiment, the public network connection unit 213 is an antenna, and the control unit 201 can connect to the public network via the antenna. Note that the communication unit 211 and the public network connection unit 213 do not necessarily need to be composed of separate hardware, and for example, one antenna can serve as both.

[0079] Note that since the communication speed implemented by the communication unit 211 is higher than the communication speed implemented by the public network connection unit 213, the mobile device 200 according to this embodiment prioritizes communication via the communication unit 211 when it is not calling other devices via the public network connection unit 213.

[0080] <Software Structure of Mobile Device 200>

[0081] Next, refer to Figure 5 The software structure of the mobile device 200 according to this embodiment will be explained.

[0082] In the mobile device 200 according to this embodiment, the non-volatile memory 203 stores fixed data such as parameters and software such as firmware.

[0083] Recording medium 210 stores OS 310 as basic software executed by control unit 201, and file management application 306 and image management application 308 as application software executed by control unit 201. Recording medium 210 also stores file transfer application 301 as application software, which has the functions of connecting to camera device 100 to acquire and store files, and connecting to server 300 to transfer files.

[0084] When the user turns on the power switch included in the operation unit 205 of the mobile device 200, the mobile device 200 starts up, and the control unit 201 reads the OS 310 from the recording medium 210, expands the OS 310 into the working memory 204, and executes the OS 310. Furthermore, various components of the mobile device 200 are controlled according to the OS 310 and the applications installed on the OS 310.

[0085] OS 310 not only has the function of controlling various components of mobile device 200, but also provides various services to applications. As a function according to this embodiment, OS 310 includes communication service 311.

[0086] Communication service 311 controls the on / off state of communication functions, connection to external devices, and data communication with connected external devices. Communication service 311 also controls the provision of data obtained through the communication functions to the application, and the sending / receiving of data to / from external devices in response to requests from the application.

[0087] File management application 306 includes a file management service 307 that manages files stored in recording medium 210. Furthermore, file management application 306 controls the reading of managed files from recording medium 210 and the writing of files to recording medium 210 in response to requests from the application.

[0088] Image management application 308 includes image management service 309 for managing image files of still images and moving images stored in recording medium 210. Unlike file management application 306, image management application 308 has functions focused on image file management, such as displaying a list of thumbnails of image files and frame-by-frame playback of moving image files. Furthermore, image management application 308 controls reading managed files from recording medium 210 and writing files to recording medium 210 in response to requests from the application.

[0089] Note that it is assumed that the file managed by the file management application 306 and the file managed by the image management application 308 are stored in different areas of the recording medium 210, and these files cannot reference each other.

[0090] Next, the file transfer application 301 according to this embodiment will be described.

[0091] Through display control 302, file transfer application 301 generates a UI screen to be displayed on display unit 206. This will be used later. Figures 6A to 6G To illustrate the structure of the UI screen.

[0092] Through communication service control 303, file transfer application 301 communicates with camera device 100 using communication service 311 and obtains master data of each file stored in camera device 100, information about the file list, and file information of each file. File transfer application 301 also reads files stored in recording medium 210 and sends these files to server 300 using communication service 311.

[0093] Under control of file management service 304, the file transfer application 301 uses the file management service 307 to write and store the main data file held in the working memory 204 into the recording medium 210.

[0094] Under control of image management service 305, the file transfer application 301 uses the image management service 309 to write and store the main data file held in the working memory 204 into the recording medium 210.

[0095] <Structure of UI Screen>

[0096] Next, reference is made to Figures 6A to 6G describe the structure and functions of the UI screen provided by the file transfer application 301.

[0097] Figure 6A The UI screen 501 shown is a function selection screen displayed in a state of being connected to the camera apparatus 100 after the file transfer application 301 is started. The function selection screen 501 includes a button 502 for selecting a function of displaying files stored in the camera apparatus 100, and a button 503 for selecting a function of displaying files stored in the recording medium 210 of the mobile apparatus 200.

[0098] Figure 6B The UI screen 504 shown is a screen of a list of files stored in the camera apparatus 100 connected to the mobile apparatus 200. When the button 502 is tapped on the function selection screen 501, the list screen 504 is displayed.

[0099] The list screen 504 includes a button 505 for returning to the previous screen, and buttons 506 and 507 for selecting the recording medium 110 that serves as a file reference destination when the camera apparatus 100 includes a plurality of recording media 110. Figure 6B The list screen 504 shown is in a state where the recording medium 110 corresponding to the button 506 with underlined characters is selected, and displays a list of files stored in the recording medium 110 indicated below the button 506.

[0100] Figure 6B The components 508 to 514 on the list screen 504 shown are generated based on information of the list of files stored in the camera apparatus 100 connected to the mobile apparatus 200 and based on information related to the list. Note that the content displayed by the components 508 to 512 will be described below; in the following, Figure 7 A and Figure 7 B and Figure 8 A and Figure 8 B describe a method of obtaining information related to the files used for displaying the discrete components 508 to 512.

[0101] Component 508 is a component for displaying thumbnails of files; in the case of motion picture files, component 508 displays a thumbnail attached to the motion picture file, and in the case of sound files, displays an image representing the sound file stored in non-volatile memory 203.

[0102] Component 509 is an icon indicating that a moving image or sound file is a proxy file. A proxy file is a file with data that is smaller in size compared to a normal file by reducing the bitrate or resolution, and users can identify it as a proxy file when the fourth letter of the filename is "P". Figure 6B On the list screen 504, each file is a proxy file, so an icon 509 is overlaid and displayed on each thumbnail.

[0103] Component 510 is a string representing the filename, and component 511 is a string representing the record date and time of the file.

[0104] Component 512 is an icon indicating whether the metadata file representing the metadata of the motion picture file is stored on the same recording medium.

[0105] Components 513 and 514 are icons representing the selected / unselected state of a file, and are overlaid and displayed on thumbnail 508. Icon 513 indicates the selected state, while icon 514 indicates the unselected state. Each time the thumbnail 508 of any file is tapped, the selected / unselected state of that file is toggled, switching between icon 513 and icon 514 depending on the selected / unselected state of the file.

[0106] Button 515 is used to begin saving a file from the camera device 100 to the mobile device 200. The file to be saved is the file in the selected state.

[0107] Figure 6C On list screen 504, components 516 to 518 are buttons for selecting the following applications, and upon tapping... Figure 6B When the button 515 on the list screen 504 is superimposed and displayed on the list screen 504, files imported from the camera device 100 to the mobile device 200 will be stored in the application while the camera device 100 is connected to the mobile device 200.

[0108] Component 516 is a button for selecting the file management application 306 as the application to which files will be stored. Tapping button 516 will initiate the process of transferring files stored in the camera device 100 to the mobile device 200 and storing these files in the file management application 306. Here, the files to be stored in the file management application 306 are the files in the selected state and the metadata files associated with the files in the selected state.

[0109] Component 517 is a button for selecting the image management application 308 as the application to which files will be stored. Tapping button 517 initiates the process of transferring files stored in the camera device 100 to the mobile device 200 and storing these files in the image management application 308. Here, since the image management application 308 is an application capable of managing image files, only motion picture files that are currently selected are to be stored in the image management application 308.

[0110] Button 518 is used to cancel saving the file. Clicking button 518 will return you to... Figure 6B The list screen returned a 504 error.

[0111] Figure 6D The components 519 to 521 on the function selection screen 501 are buttons for selecting the application used as the read source when reading a file from the recording medium 210, and are activated by tapping... Figure 6A When the button 503 on the function selection screen 501 is superimposed and displayed... Figure 6A On the function selection screen 501.

[0112] Component 519 is a button for selecting the file management application 306 as the application to be used as the file reading source. Clicking button 519 will initiate the process of reading files from the file management application 306. This will be used later. Figure 6E This describes the screen used to select a file managed by the file management application 306.

[0113] Component 520 is a button for selecting the image management application 308 as the application to be used as the file reading source. Clicking button 520 will initiate the process of reading files from the image management application 308. This will be used later. Figure 6F This describes the screen used to select a file managed by the image management application 308.

[0114] Button 521 is used to cancel reading the file; clicking button 521 will return to... Figure 6A Function selection screen 501.

[0115] Figure 6EThe UI screen 522 shown is provided by OS 310 and is a selection screen for selecting files to be read from files managed by file management application 306. After tapping... Figure 6D When button 519 is pressed on function selection screen 501, selection screen 522 is overlaid and displayed. Figure 6A The function selection screen 501 is used. In this embodiment, it is assumed that the files selectable on the selection screen 522 are only MP4 format motion picture files and WAV format audio files.

[0116] Figure 6E The selection screen 522 includes components 523 to 529.

[0117] Component 523 is a button for returning to the previous screen; when the return button 523 is tapped, the following is displayed: Figure 6A Function selection screen 501.

[0118] Component 524 is a button for completing file selection; when button 524 is clicked, the following will be displayed. Figure 6G The description list is shown in screen 535.

[0119] Component 525 is a component for displaying thumbnails of files; in the case of motion picture files, component 525 displays a thumbnail attached to the motion picture file, and in the case of sound files, displays an image representing the sound file stored in non-volatile memory 203.

[0120] Component 526 is a string representing the filename, and component 527 is a string representing the record date and time of the file.

[0121] Components 528 and 529 are icons representing the selected / unselected state of a file, and are overlaid and displayed on thumbnail 525. Icon 528 indicates the selected state, while icon 529 indicates the unselected state. Whenever any file's thumbnail 525 is tapped, the selected / unselected state of that file is toggled, switching to icon 528 or icon 529 depending on the selected / unselected state of the file.

[0122] Figure 6F The UI screen 530 shown is provided by OS 310 and is a selection screen for selecting files to be read from files managed by the image management application 308. After tapping... Figure 6D When button 520 is on the function selection screen 501, the selection screen 530 is overlaid and displayed. Figure 6A The function selection screen 501 is used. In this embodiment, it is assumed that the only file that can be selected on the selection screen 530 is a motion image file.

[0123] Button 531 is used to cancel file selection and return to the previous screen; tapping the back button 531 will return to the previous screen. Figure 6D Function selection screen 501.

[0124] Button 532 is used to complete file selection; when button 532 is clicked, the following will be displayed. Figure 6G The explanation list is shown in screen 535.

[0125] Component 533 is a component for displaying thumbnails of files, and displays thumbnails attached to moving image files.

[0126] Component 534 is an icon indicating the selection status of a file, and it is overlaid and displayed on thumbnail 533. Icon 534 is only displayed when the file is selected. Tapping the file thumbnail 533 toggles the selected / unselected state of the file, and the display / display of icon 534 toggles according to the selected / unselected state of the file.

[0127] Figure 6G The UI screen shown is 535. Figure 6E Selection screen 522 or Figure 6F The selection screen 530 shows the list of selected files, and after tapping... Figure 6E Select button 524 on screen 522 or Figure 6F The button 532 on the selection screen 530 is displayed.

[0128] Figure 6G The list screen 535 shows parts 508 to 512 and Figure 6B The list screen 504 shows components 508 to 512 similarly, and is generated based on the following information: Figure 6E Selection screen 522 or Figure 6F The selection screen 530 displays information about the file list selected and read from the recording medium 210, as well as information related to that list. This will be used later. Figures 10 to 12 This describes a method for obtaining information related to the documents used to display components 508 to 512.

[0129] Button 505 is used to return to the previous screen; tapping button 505 will return to the previous screen. Figure 6A Function selection screen 501.

[0130] Button 536 is used to initiate the process of sending files from mobile device 200 to server 300. The files to be sent are all the files displayed on list screen 535.

[0131] Note that the license provides the following functionality: Figure 6BFiles selected from files stored in the camera device 100 on the list screen 504 are sent to the server 300 even if they are not stored in the mobile device 200.

[0132] <Functions of File Transfer Application 301>

[0133] Next, the function of the file transfer application 301 according to this embodiment will be explained.

[0134] The file transfer application 301 according to this embodiment has the following two functions.

[0135] The primary function is to communicate with the camera device 100 and store the file selected by the user from the motion image file and sound file stored in the camera device 100 into the mobile device 200.

[0136] The second function is to communicate with the server 300 and send (upload) the files selected by the user from the motion image files and sound files stored in the mobile device 200 to the server 300.

[0137] The first and second functions described above allow the file transfer application 301 to send motion image files and sound files stored in the camera device 100 to the server 300 via the mobile device 200.

[0138] <Processing sequence of camera device 100 and moving device 200>

[0139] Next, refer to Figures 7 to 9 The file transfer application 301 of the mobile device 200 is displayed. Figure 6B The following is an explanation of the processing of the file list screen 504 shown as an example.

[0140] Figure 7 Showing from in Figure 6A The processing sequence of the camera device 100 and the mobile device 200 from the moment a tap of button 502 is detected on the function selection screen 501 until the list screen 504 is displayed.

[0141] In T701, after detection Figure 6A When the button 502 on the function selection screen 501 is tapped, the mobile device 200 sends a request to the camera device 100 to obtain file list information.

[0142] In T702, when a request for file list information is received from the mobile device 200, the camera device 100 generates the file list information using information about the files stored in the recording medium 110. Here, it is assumed that the file list information includes the file name, format information, and file ID. The file ID is a unique identifier generated for each file and is used, for example, when a request is sent to the camera device 100 to obtain file information and master data files.

[0143] In T703, once the camera device 100 generates the file list information, it sends the file list information to the mobile device 200 as a response to the request in T701. Upon receiving the file list information from the camera device 100, the mobile device 200 refers to the format of all files included in the file list and performs processing corresponding to those formats.

[0144] When the file format is MP4, in T704, the mobile device 200 sends a request to the camera device 100 to obtain moving image file information. In this case, the file for which the moving image file information is to be obtained is specified by assigning a file ID.

[0145] In T705, upon receiving a request for motion image file information from mobile device 200, camera device 100 generates motion image file information based on information stored in the file's metadata storage area. The metadata storage area for MP4 format files includes the recording date and time as detailed file information; in this embodiment, it is assumed that camera device 100 stores thumbnails in the metadata storage area when generating the motion image file. As a result of the above, it is assumed that the motion image file information generated in T705, referring to the file's metadata storage area, includes at least thumbnails and the recording date and time. It is also assumed that the motion image file information further includes information indicating whether a related metadata file exists.

[0146] In T706, once the camera device 100 generates motion image file information for the file specified by the request for obtaining motion image file information from the mobile device 200, the camera device 100 sends the motion image file information as a response to the request in T704 to the mobile device 200.

[0147] In the case of a WAV file format, in T707, the mobile device 200 sends a request to the camera device 100 to obtain audio file information. In this case, the file for which audio file information is to be obtained is specified by assigning a file ID.

[0148] In T708, upon receiving a request for obtaining audio file information from the mobile device 200, the camera device 100 generates the audio file information based on file information in a catalog file stored in the recording medium 110. It is assumed that the file information in the catalog file includes the recording date and time, and that the audio file information includes at least the recording date and time.

[0149] In T709, once the camera device 100 generates sound file information of the file specified by the mobile device 200, the camera device 100 sends the sound file information as a response to the request for obtaining the sound file information in T707 to the mobile device 200.

[0150] If the file format is neither MP4 nor WAV, the file will not be displayed. Figure 6B On the list screen 504, and the mobile device 200 does not perform processing.

[0151] Once the mobile device 200 has processed each file according to the format, in T710, the mobile device 200 generates a file based on the file list information, motion image file information, and sound file information obtained from the camera device 100. Figure 6B The list screen returned a 504 error. Note that this assumes... Figure 6B The files on the list screen with 504 error are sorted in descending order by date and time by default.

[0152] <Processing of mobile device 200>

[0153] Next, refer to Figure 8 The following describes the processing of the mobile device 200 for generating a list screen 504 for files stored in the camera device 100.

[0154] Note that the file transfer application 301 will be described below as the entity performing this process; however, in reality, this process is implemented by the control unit 201 of the mobile device 200 expanding the program of the file transfer application 301 (or the application's functions, OS, OS services, etc.) stored in the non-volatile memory 203 to the working memory 204 and executing the program. This also applies to what will be described later. Figure 10 and Figure 12 .also, Figure 8 The processing occurs when a file transfer application displays error 301. Figure 6A The function selection screen 501 is triggered when the button 502 is tapped by the operation unit 205.

[0155] In S801, the file transfer application 301 obtains file list information from the camera device 100 through the communication service control 303, so as to display a list screen 504 of the files stored in the camera device 100.

[0156] Once the file transfer application 301 obtains the file list information from the camera device 100, the file transfer application 301 performs the processing steps S802 to S805 for each file included in the file list information.

[0157] In S802, the file transfer application 301 determines whether the file format is MP4. If the file transfer application 301 determines that the file format is MP4, the file transfer application 301 causes the processing to proceed to S803; if the file format is not MP4, the file transfer application 301 causes the processing to proceed to S804.

[0158] In S803, the file transfer application 301 obtains motion image file information from the camera device 100.

[0159] In S804, the file transfer application 301 refers to the file list information and determines whether the file format is WAV. If the file transfer application 301 determines that the file format is WAV, the file transfer application 301 causes the processing to proceed to S805; if the file format is not WAV, the file transfer application 301 ends the processing and executes S802 and subsequent processing for the next file.

[0160] By performing S802 to S804 processing for each file, the file transfer application 301 obtains the information required for generating the file list screen 504 from the camera device 100.

[0161] In S806, the file transfer application 301 generates a file transfer function based on the file list information, motion image file information, and sound file information obtained from the camera device 100. Figure 6B Components 508 to 512 on the list screen 504.

[0162] Through the above processing, the file transfer application 301 generates a screen displaying a list of files stored in the camera device 100.

[0163] <Processing of Camera Device 100>

[0164] Next, refer to Figure 9 The following describes the processing of the camera device 100 when it receives a communication command from the mobile device 200.

[0165] Figure 9The processing is achieved by the control unit 101 expanding the program stored in the non-volatile memory 103 to the working memory 104 and executing the program. Furthermore, Figure 9 The processing is triggered when the communication unit 111 receives a PTP / IP communication command from the mobile device 200.

[0166] In S901, the control unit 101 analyzes the type of PTP / IP communication commands received by the communication unit 111.

[0167] In S902, the control unit 101 determines whether the command type is a request to obtain file list information. If the control unit 101 determines that the command type is a request to obtain file list information, the control unit 101 causes the process to proceed to S903; if the control unit 101 determines that the command type is not a request to obtain file list information, the control unit 101 causes the process to proceed to S905.

[0168] In S903, the control unit 101 analyzes the directory entries in the recording medium 110 and obtains information about all the files stored in the recording medium 110.

[0169] In S904, the control unit 101 generates a file ID for each file based on the file information obtained in S903, and generates a file list information including the file name, format and file ID as a response command.

[0170] In S905, the control unit 101 determines whether the command type is a request to obtain motion image file information. If the control unit 101 determines that the command type is a request to obtain motion image file information, the control unit 101 causes the process to proceed to S906; if the control unit 101 determines that the command type is not a request to obtain motion image file information, the control unit 101 causes the process to proceed to S908.

[0171] In S906, the control unit 101 references the metadata storage area in the motion picture file specified by the file ID and obtains detailed information about the file, including thumbnails and the recording date and time.

[0172] In S907, the control unit 101 generates motion image file information, including thumbnails and recording date and time, as a response command based on the detailed information of the motion image file obtained in S906.

[0173] In S908, the control unit 101 determines whether the command type is a request to obtain sound file information. If the control unit 101 determines that the command type is a request to obtain sound file information, the control unit 101 causes the process to proceed to S909; if the control unit 101 determines that the command type is not a request to obtain sound file information, the control unit 101 causes the process to proceed to S911.

[0174] In S909, the control unit 101 refers to the information in the catalog file stored in the recording medium 110 and obtains detailed information of the sound file, including the recording date and time, as specified by the file ID.

[0175] In S910, the control unit 101 generates sound file information, including the recording date and time, as a response command based on the detailed information of the sound file obtained in S909.

[0176] In S911, the control unit 101 determines whether the command type is a request to obtain the master data file. If the control unit 101 determines that the command type is a request to obtain the master data file, the control unit 101 causes the process to proceed to S912; if the control unit 101 determines that the command type is not a request to obtain the master data file, the control unit 101 causes the process to proceed to S914.

[0177] In S912, the control unit 101 obtains the master data file specified by the file ID.

[0178] In S913, the control unit 101 generates the master data file obtained in S912 as a response command.

[0179] In S914, the control unit 101 performs processing corresponding to command types other than those described above, and generates a response command. Since the processing in S914 is not particularly relevant to this embodiment, its detailed description is omitted.

[0180] In S915, the control unit 101 sends the response command generated in one of S904, S907, S910 and S913 to the mobile device 200, which is the source of the communication command, via the communication unit 111.

[0181] Through the above processing, the camera device 100 exchanges file information and master data files with external devices such as mobile devices 200 via the communication unit 111.

[0182] <File storage processing of mobile device 200>

[0183] Next, refer to Figure 10 as well as Figure 11A and Figure 11B The description provides an explanation of the process for storing files stored in the camera device 100 into the recording medium 210 of the mobile device 200.

[0184] exist Figure 6B On the list screen 504, the user selects files from those stored in the camera device 100 to transfer and store on the mobile device 200. After the file selection is complete, the user taps button 515 and then taps... Figure 6C The mobile device 200 selects either the file management application 306 or the image management application 308 as the file storage destination by pressing button 516 or button 517. Once an application is selected as the storage destination, the mobile device 200 obtains the selected master data file from the camera device 100 and writes these master data files to the management area of ​​the storage destination application in the recording medium 210.

[0185] Figure 10 This is a flowchart illustrating the file storage process of a mobile device 200 when a file management application 306 is selected as the storage destination application.

[0186] exist Figure 10 During the processing, the file transfer application 301 detects that the file is transferred via the operation unit 205. Figure 6C When button 516 is tapped on the list screen 504, file transfer application 301 executes a command for all selected files. Figure 10 The processing of S1001 to S1004.

[0187] In S1001, via communication service control 303, file transfer application 301 sends a request to obtain a master data file to camera device 100 and obtains the selected master data file. Camera device 100 performs processing based on the request to obtain the master data file, such as using... Figure 9 As stated above.

[0188] In S1002, through the file management service control 304, the file transfer application 301 writes the master data file obtained from the camera device 100 to the management area of ​​the file management application 306 in the recording medium 210.

[0189] In S1003, the file transfer application 301 determines whether the file format is an audio file format. If the file transfer application 301 determines that the file format is an audio file format, the file transfer application 301 causes the processing to proceed to S1004. Furthermore, if the transfer application 301 determines that the file format is not an audio file format, the transfer application 301 ends the processing and executes S1001 and subsequent processing for the next file.

[0190] In S1004, through the file management service control 304, the file transfer application 301 uses the recording date and time of the sound file obtained from the camera device 100 to overwrite the creation date and time and update date and time of the directory entry in the management area of ​​the file management application 306.

[0191] Figure 11A and Figure 11B Example shown Figure 10 The data structure of directory entries in the management area of ​​file management application 306 in S1004.

[0192] The directory entries describe information about the files managed by the file management application 306, and include the file name 1101, extension 1102, creation date and time 1103, update date and time 1104, and file size 1105.

[0193] Figure 11A Example shows targeting Figure 10 The directory entry in which the judgment in S1003 is "no" and the overwrite process is not performed in S1004 (that is, in the case where the file obtained from the camera device 100 is stored in the file management application 306).

[0194] When a file obtained from an external source is stored in the file management application 306, the date and time of the stored file are written to the creation date and time and the update date and time of the directory entry. Note that although this embodiment illustrates an example of writing the date and time of the stored file to the creation date and time and the update date and time of the directory entry, there are cases where, according to the OS specifications and writing method, only the creation date and time, or the update date and time, or both, are updated.

[0195] Figure 11B Example shows targeting Figure 10 The directory entry for the case where the judgment in S1003 is "yes" and the overwrite process is performed in S1004. Figure 11B In cases where the file obtained and stored from an external source is an audio file, the recording date and time of the audio file obtained from the external source are used to overwrite the creation date and time, as well as the update date and time, of the directory entry.

[0196] As described above, even if the file obtained from the outside is a sound file whose creation date and time, as well as its update date and time, are not recorded in the file's directory entry, the recording date and time of the sound file are recorded in the file's directory entry by rewriting the creation date and time, as well as the update date and time, of the directory entry managed by the storage destination application to the recording date and time of the file obtained from the sending source. In this way, the mobile device 200 can accurately display a list of files obtained from the outside based on the recording date and time.

[0197] Note that although this embodiment illustrates an example of rewriting both the creation date and time and the update date and time of a file as a record date and time, it is possible to rewrite either the creation date and time or the update date and time of a file.

[0198] <Processing for displaying a list of files stored in the mobile device 200>

[0199] Next, refer to Figure 12 Provides a method for retrieving files from file management application 306 and generating... Figure 6G Explanation of the processing of file list screen 535.

[0200] Figure 12 The processing is in Figure 6E The file management application 306 is triggered when it detects a tap of button 524 on the file selection screen 522, when one or more files are selected (that is, when the file selection is complete).

[0201] File transfer application 301 performs the processing shown in S1201 to S1203 for all selected files.

[0202] In S1201, the file transfer application 301 determines whether the file is in MP4 format. If the file transfer application 301 determines that the file is in MP4 format, the file transfer application 301 causes the processing to proceed to S1202; if the file transfer application 301 determines that the file is not in MP4 format, the file transfer application 301 causes the processing to proceed to S1203.

[0203] In S1202, the file transfer application 301 analyzes the file's metadata storage area and obtains the file's information, including thumbnails and motion image file information such as the recording date and time.

[0204] In S1203, the file transfer application 301 determines whether the file is in WAV format. If the file transfer application 301 determines that the file is in WAV format, the file transfer application 301 causes the processing to proceed to S1204; if the file transfer application 301 determines that the file is not in WAV format, the file transfer application 301 ends the processing and executes S1201 and subsequent processing for the next file.

[0205] In S1204, the file transfer application 301 refers to the directory entry in the file management application 306 and obtains the sound file information by interpreting the file's creation date and time as the recording date and time.

[0206] By pre-writing or overwriting the creation date and time of files in directory entries with the recorded date and time, the accurate recorded date and time can be obtained when retrieving sound files.

[0207] As a result of performing the above S1201 to S1204 processes for each file, the file transfer application 301 obtains the information required for generating the file list screen 535 from the file management application 306.

[0208] In S1205, the file transfer application 301 generates a file based on the motion image file information and sound file information obtained from the file management application 306. Figure 6G The file list screen is 535.

[0209] Note, assuming Figure 6G The files on the list screen 535 are sorted in descending order by date and time by default.

[0210] Through the above processing, when displaying a screen showing a list of files stored in the file management application 306, the file transfer application 301 can display the accurate recording date and time even for sound files that cannot have their recording date and time stored internally.

[0211] <Variation Example>

[0212] Although the above embodiments illustrate an example of processing audio files in the WAV file format, audio files can be in other formats that do not allow storing the recording date and time.

[0213] Furthermore, although the above embodiments illustrate the use of audio files as an example of a file type that does not allow the storage of recording dates and times, files that cannot store recording dates and times can be used instead of audio files. For example, in the case of processing metadata files such as XML format generated when capturing moving images, similar processing to that for audio files can be performed.

[0214] Furthermore, although the above embodiments determine the existence of a record date and time for a file based on its file format, the existence of a record date and time for each file can be managed using management methods such as cataloging files, to prepare for situations such as processing files in their original formats. In this case, a management method can be provided that manages whether the creation date and time and update date and time of a file have been updated when the file is stored in the mobile device 200, and that references the creation date and time and update date and time of the file when reading file information from the mobile device 200.

[0215] [Other Embodiments]

[0216] This invention can be implemented by supplying a program for implementing one or more functions of the above embodiments to a system or device via a network or storage medium, and causing one or more processors in the computer of the system or device to read and execute the program. This invention can also be implemented by a circuit (e.g., an ASIC) for implementing one or more functions.

[0217] 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, the appended claims have been added to inform the public of the scope of this invention.

[0218] This application claims the benefit of Japanese Patent Application 2021-113138, filed on July 7, 2021, the entire contents of which are incorporated herein by reference.

[0219] Explanation of reference numerals in the attached figures

[0220] 100…Camera device, 101…Control unit, 102…Image capture unit, 106…Display unit, 107…Sound input unit, 111…Communication unit, 200…Mobile device, 201…Control unit, 205…Operation unit, 206…Display unit, 210…Recording medium, 211…Communication unit, 300…Server

Claims

1. A communication device for communicating with external devices, characterized in that, The communication device includes: A storage component for storing a file obtained from a first external device, and for storing first information related to at least one of the file's creation date and time and its update date and time; and Control components, used for: If the file obtained from the first external device is a first file on the first external device that includes second information related to the recording date and time of the file, then the first file is stored in the storage component, and the first information of the first file is stored in the storage component. If the file obtained from the first external device is a second file without the second information, the second information related to the recording date and time of the second file is obtained from the first external device, and the first information is overwritten with the second information when the second file is stored in the storage component. In the case where the file obtained from the first external device is the second file, the control unit obtains the second information from management information, which is obtained from the first external device, is managed separately in the first external device as information different from the second file, and associates the identification information of the second file with the recording date and time of the second file.

2. The communication device according to claim 1, characterized in that, When the second file stored in the storage component is sent to the second external device, the control component reads the second file from the storage component and obtains the second information by referring to the first information of the second file stored in the storage component.

3. The communication device according to claim 2, characterized in that, Also includes: A display component is used to display a list of files stored in the storage component. In the case where the file stored in the storage component is the second file, the control component obtains the second information by referring to the first information of the second file stored in the storage component, and displays the second information on the list of files.

4. The communication device according to any one of claims 1 to 3, characterized in that, Also includes: The determination component is used to determine whether the file obtained from the first external device is the first file or the second file.

5. The communication device according to claim 4, characterized in that, The determining component determines whether the file obtained from the first external device is the first file or the second file based on the format of the file obtained from the first external device.

6. The communication device according to claim 4, characterized in that, If the obtained file is in the format of an audio file, the determination component determines that the obtained file is the second file.

7. The communication device according to claim 5, characterized in that, If the obtained file is in the format of a still image or a moving image file, the determination component determines that the obtained file is the first file.

8. The communication device according to any one of claims 1 to 3, 5 to 7, characterized in that, If the control unit rewrites the first information into the second information when storing the second file into the storage unit, the control unit stores the second file in association with information indicating whether the first information has been rewritten.

9. A camera device for communicating with external devices, characterized in that, include: Generate components, used to generate files; A management component is used to generate file information including the record date and time of the file, and to store the file information in a storage component; as well as Control components, used for: Upon receiving a request from the external device to obtain file information of the first file, which includes second information related to the recording date and time of the first file, the management component sends the file information stored therein, including the recording date and time of the first file. Upon receiving a request from the external device to obtain file information for a second file that does not include second information related to the recording date and time of the second file, file information including the second information, which is managed separately as information different from the second file and whose identification information is associated with the recording date and time of the second file, is generated, and the file information including the second information of the second file stored in the management component is sent.

10. The camera device according to claim 9, characterized in that, When the management component stores the files generated by the generation component into the storage component, it generates and stores files whose record dates and times are associated with the file names.

11. The camera device according to claim 9 or 10, characterized in that, Upon receiving the request from the external device, the control unit sends information about the list of files stored in the storage unit to the external device.

12. A control method for a communication device used to communicate with an external device, characterized in that, The control method includes the following steps: The file obtained from the first external device is stored, and first information related to at least one of the file's creation date and time and update date and time is stored in the storage component; If the file obtained from the first external device is a first file on the first external device that includes second information related to the recording date and time of the file, then the first file is stored in the storage component, and the first information of the first file is also stored in the storage component; and If the file obtained from the first external device is a second file without the second information, the second information related to the recording date and time of the second file is obtained from the first external device, and the first information is overwritten with the second information when the second file is stored in the storage component. In the case where the file obtained from the first external device is the second file, the second information is obtained from management information, which is obtained from the first external device, is managed separately in the first external device as information different from the second file, and associates the identification information of the second file with the recording date and time of the second file.

13. A control method for a camera device used to communicate with an external device, characterized in that, The control method includes the following steps: Generate files; Generate file information including the recording date and time of the file, and store the file information in a storage component; and Upon receiving a request from the external device to obtain file information of the first file, which includes second information related to the recording date and time of the first file, the storage component sends the file information stored therein, including the recording date and time of the first file. Upon receiving a request from the external device to obtain file information for a second file that does not include second information related to the recording date and time of the second file, file information including the second information, which is managed separately as information different from the second file and whose identification information is associated with the recording date and time of the second file, is generated, and the stored file information including the second information is sent.

14. A computer-readable storage medium storing a program for causing a computer to perform the control method according to claim 12 or 13.

15. A computer program product comprising a program for causing a computer to perform the control method according to claim 12 or 13.

Images