Control program and control method

JP2026146969APending Publication Date: 2026-09-17BUFFALO CORP LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2025034440
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-03-05
Publication Date
2026-09-17

AI Technical Summary

Benefits of technology

【0009】 本発明によれば、バックアップ対象のファイルを効率よく外部の記憶装置に保存させることが可能な制御プログラム、及び制御方法を提供することができる。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026146969000001_ABST
    Figure 2026146969000001_ABST
Patent Text Reader

Abstract

This invention provides a control program and a control method that enable efficient saving of backup target files to an external storage device. [Solution] The control program of the information terminal 10 instructs the processor 11 of the information terminal 10 to execute a first backup process, which saves the files to be backed up to an external storage device 20 that can communicate with the information terminal 10, and registers the identification information of the files that were successfully saved in the written list 60. A second backup process, which is executed after the first backup process, saves the files to be backed up to the external storage device 20, and is executed based on the written list 60.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a control program and a control method. [Background Art]

[0002] Photo and video data stored in information terminals such as smartphones and tablets may be stored in, for example, a USB storage for the purpose of sharing the data with other terminals or for backup purposes. However, if, for example, the USB storage is removed during data backup or restoration and the processing is interrupted, the data may be damaged or may not be backed up.

[0003] For example, the following Patent Document 1 describes a storage system in which when a user's mobile terminal accesses an information server via a communication network, the information server receives backup data from the user's mobile terminal by a communication unit after user authentication by an authentication unit, causes a data type determination unit to determine the data type of the backup data, and stores the backup data in an information storage unit in a classification based on a user ID and the data type. [Prior Art Documents] [Patent Documents]

[0004] [Patent Document 1] Japanese Unexamined Patent Application Publication No. 2006-013824 [Summary of the Invention] [Problems to be Solved by the Invention]

[0005] However, in the related art, there is room for improvement in efficiently backing up content data managed by an information terminal to an external storage.

[0006] This invention has been made in view of the above circumstances, and aims to provide a control program and a control method that can efficiently save files to be backed up to an external storage device. [Means for solving the problem]

[0007] The control program of the present invention is a control program for an information terminal, The processor of the aforementioned information terminal, The first backup process is executed, which saves the files to be backed up to an external storage device that can communicate with the information terminal, and registers the identification information of the successfully saved files in the first list. A second backup process, which is performed after the first backup process and saves the files to be backed up to the external storage device, is performed based on the first list. This is what causes the process to be executed.

[0008] The control method of the present invention is a control method for an information terminal, The processor of the aforementioned information terminal The first backup process is executed, which saves the files to be backed up to an external storage device that can communicate with the information terminal, and registers the identification information of the successfully saved files in the first list. A second backup process, which is performed after the first backup process and saves the files to be backed up to the external storage device, is performed based on the first list. [Effects of the Invention]

[0009] According to the present invention, it is possible to provide a control program and a control method that can efficiently save files to be backed up to an external storage device. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows an example of a communication system to which the information terminal of the present invention is applied. [Figure 2]It is a diagram showing an example of the hardware of the information terminal 10. [Figure 3] It is a diagram showing the software configuration of the information terminal 10. [Figure 4] It is a flowchart showing an example of processing by the backup application 18. [Figure 5] It is a flowchart showing the backup processing of step S14 and step S15 in FIG. 4. [Figure 6] It is a diagram showing an example of a written list. [Figure 7] It is a diagram showing the backup flow of first image data in the communication system 1. [Figure 8] It is a diagram showing the backup flow of second image data in the communication system 1. [Figure 9] It is a diagram showing a modified example of the communication system 1. [Figure 10] It is a flowchart showing an example of processing of the backup application 18 in the modified example. [Figure 11] It is a flowchart showing the backup processing of step S34 in FIG. 10. [Figure 12] It is a diagram showing the backup flow of image data in the communication system 1. [Figure 13] It is a diagram showing an example of a notification prompting deletion of a file. MODE FOR CARRYING OUT THE INVENTION

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0012] (Embodiment) <Communication system to which information terminal is applied> FIG. 1 is a diagram showing an example of a communication system to which the information terminal of the present invention is applied. The communication system 1 shown in FIG. 1 includes an information terminal 10, an external storage device 20, and a server 50.

[0013] The information terminal 10 is, for example, a portable information terminal. A portable information terminal generally refers to an information terminal with a small storage capacity, such as a smartphone, a tablet terminal, or the like. However, the information terminal 10 may also be, for example, a notebook personal computer, a desktop personal computer, or the like in addition to the above. The "control program" of the present invention causes the information terminal 10 to execute processing for performing control to back up files managed by the information terminal 10 to an external storage device 20. The control program is, for example, a backup application installed on the information terminal 10.

[0014] The "files managed by the information terminal 10" is an example of files to be backed up, and refers to, for example, images managed in a photo library (images viewable in a photo application). A "file" is content data such as image (still image or moving image) data or audio data, for example. Furthermore, a "file" may include, for example, a first file whose data body (object to be backed up) is stored in the information terminal 10, and a second file whose data body is stored in a server 50, for example. For the first file, there are cases where the data body is also stored in the server 50, and cases where it is not stored in the server 50. For the second file, only data obtained by simplifying the data body (such as a thumbnail) is stored in the information terminal 10. The first file and the second file are managed in a mixed state in the photo library. The files may be stored in one folder, or may be stored in a plurality of folders. The information terminal 10 is communicably connected to the external storage device 20 and the server 50.

[0015] The external storage device 20 is a storage device such as an SSD (Solid State Drive) or an HDD (Hard Disk Drive), and is an example of the "external storage device" of the present invention. The external storage device 20 is connected to the information terminal 10 by a wired connection, for example, via USB (Universal Serial Bus) or Lightning. The external storage device 20 may also be capable of communication via wireless. For example, the external storage device 20 may be capable of communicating directly with the information terminal 10 via Bluetooth®, or it may be a NAS (Network Attached Storage) that can be connected to a network (for example, a wireless LAN (Local Area Network)).

[0016] Server 50 is connected to the information terminal 10 via network 40, enabling communication. Network 40 is, for example, a wide area network (WAN). Server 50 is a device that allows the information terminal 10 to store data via network 40. Server 50 is, for example, a cloud server.

[0017] <Configuration of information terminal 10> Figure 2 shows an example of the hardware of the information terminal 10. As shown in Figure 2, the information terminal 10 includes a processor 11, main memory 12, internal storage 13, user interface 14, wireless communication interface 15, and wired communication interface 16.

[0018] The processor 11 is a circuit that performs signal processing, and is, for example, a CPU (Central Processing Unit) that controls the entire information terminal 10. The processor 11 may also be implemented using other digital circuits such as an FPGA (Field Programmable Gate Array) or a DSP (Digital Signal Processor). Furthermore, the processor 11 may be implemented by combining multiple digital circuits.

[0019] Main memory 12 is, for example, RAM (Random Access Memory). Main memory 12 is used as the work area of ​​the processor 11. Internal storage 13 is, for example, non-volatile memory such as magnetic disk, optical disk, or flash memory. Various programs for operating the information terminal 10 are stored in internal storage 13. Programs stored in internal storage 13 are loaded into main memory 12 and executed by the processor 11. The backup application, which is the control program of the present invention, is stored in internal storage 13.

[0020] The user interface 14 is a communication interface that communicates with the processor 11. The user interface 14 functions as an input device and display device for the processor 11. The user interface 14 is composed of, for example, a display screen (touch panel), a keyboard, etc., and is configured to allow input of various commands to the processor 11. The user interface 14 is also configured to display various screens related to the control content of the processor 11.

[0021] The wireless communication interface 15 is a communication interface capable of wireless communication with the information terminal 10. The wireless communication interface 15 may be capable of wireless communication using frequency bands such as 2.4GHz, 5GHz, and 6GHz. The information terminal 10 may be a wireless terminal that supports wireless LAN wireless communication such as Wi-Fi 7 (Wi-Fi is a registered trademark). The wireless communication interface 15 connects the information terminal 10 to the server 50 via the network 40.

[0022] The wired communication interface 16 is a communication interface that performs wired communication with the information terminal 10. In the example shown in Figure 2, the information terminal 10 is connected to the external storage device 20 by wire, but it may also be connected wirelessly.

[0023] Figure 3 shows the software configuration of the information terminal 10. As shown in Figure 3, the information terminal 10 is equipped with an operating system 17 for managing and controlling its overall operation. The information terminal 10 also has several applications installed, including a backup application 18 (hereinafter also referred to as the "application group"). The backup application 18 is one of the applications that run on the operating system 17.

[0024] The backup application 18 causes the processor 11 to execute a first backup process, which involves saving the files to be backed up to an external storage device 20 that can communicate with the information terminal 10, and registering the identification information of the successfully saved files in a first list. The second backup process, which is executed after the first backup process, saves the files to be backed up to the external storage device 20, and executes this process based on the first list.

[0025] "Identification information" refers to information that can identify a file, such as a file name or file ID. "First list" may be stored in the information terminal 10 or in the external storage device 20. Alternatively, "first list" may be stored as a list with the same content in both the information terminal 10 and the external storage device 20. If it is stored in both, a consistency check of both lists may be performed before the backup process. "Based on the first list" means based on the first list in which the identification information of the successfully saved files is registered.

[0026] "Backup processing" refers to requesting a file from the operating system 17, saving the file to a temporary folder assigned to the backup application 18, transmitting it from the temporary folder to the external storage device 20, and storing it on the external storage device 20. On the operating system 17 side, for example, for the first file stored in the information terminal 10, it reads it from within the information terminal 10 and sends it to the backup application 18. For the second file stored in the server 50, if the second file is in the cache of the information terminal 10, it reads it and sends it to the backup application 18; otherwise, it receives it from the server 50 and sends it to the backup application 18.

[0027] For example, in the first backup process, if the backup application 18 successfully saves a file to the external storage device 20, it instructs the processor 11 to register the identification information of that file in the first list. This ensures that even if an application error occurs during the backup process, files that were successfully saved up to the time of the error are registered in the first list.

[0028] Furthermore, if the backup application 18 fails to save a file to the external storage device 20 during the first backup process, it determines whether the cause of the failure is persistent. If the cause is persistent, it instructs the processor 11 to perform a process that prevents the saving of the failed file to the external storage device 20. "Preventing saving" means that saving will not be performed, at least during that backup process. Persistent causes include, for example, the external storage device 20 being disconnected from the information terminal 10, the information terminal 10 having low battery power, the external storage device 20 having insufficient capacity, or the user canceling the backup process.

[0029] Furthermore, if the backup application 18 fails to save a file to the external storage device 20 during the first backup process, it determines whether the cause of the failure is persistent or not. If the cause is not persistent, it instructs the processor 11 to re-execute saving the failed file to the external storage device 20. "The cause is not persistent" means, for example, that the number of download failures from the cloud (server 50) is less than N. Therefore, for example, if the number of download failures is N or more, it is determined that the cause of the failure is persistent. Alternatively, "the cause is not persistent" could also mean, for example, that the number of write errors on the external storage device 20 is less than N. In that case, for example, if the number of write errors is N or more, it is determined that the cause of the failure is persistent. If the re-execution of saving is successful, the backup application 18 registers the file in the first list.

[0030] Furthermore, the backup application 18 instructs the processor 11 to register the identification information of files successfully saved in the second backup process into the first list. Instead of creating a new list in the second backup process, the backup application 18 registers the identification information of files successfully saved into the first list inherited from the first backup process, thereby updating the first list.

[0031] Furthermore, in the second backup process, the backup application 18 instructs the processor 11 to save the files managed by the information terminal 10, excluding those registered in the first list, to the external storage device 20. In other words, the backup application 18 does not repeatedly back up files that have already been saved.

[0032] Furthermore, the backup application 18 instructs the processor 11 to perform a process in the first backup process that does not register the identification information of files that failed to save in the first list.

[0033] <Processing by backup application 18> Figure 4 is a flowchart illustrating an example of processing by the backup application 18. The processing in this flowchart is started, for example, by tapping the backup application 18 icon displayed on the display screen of the information terminal 10. This example describes the case where image data (an example of a file) managed by the information terminal 10 is backed up to an external storage device 20 (external storage device). Image data includes still image data and moving image data. In this example, first the image data stored in the information terminal 10 (hereinafter referred to as the first image data) is backed up, and then the image data stored in the server 50 (hereinafter referred to as the second image data) is backed up.

[0034] First, the backup application 18 obtains a management list of image data managed by the information terminal 10 (for example, a list of PHAssets) from the operating system 17 (step S11). The operating system 17 obtains the management list using an API (Application Programming Interface).

[0035] The backup application 18 removes image data from the written list, which indicates files that have already been successfully saved, from the image data management list obtained in step S11, for example, to obtain a backup list (step S12). In the process of step S12, if the backup process is, for example, the first backup process, then no files that have been successfully saved will be registered in the written list.

[0036] Based on the backup list obtained in step S12, the backup application 18 classifies the image data into first image data stored in the information terminal 10 and second image data stored in the server 50 (step S13).

[0037] The backup application 18 first backs up the first image data from the classified first image data and second image data to the external storage device 20 (step S14).

[0038] Next, the backup application 18 backs up the second image data from the classified first image data to the external storage device 20 (step S15). The backup process in steps S14 and S15 is explained in Figure 5.

[0039] Figure 5 is a flowchart showing the backup process in steps S14 and S15 in Figure 4.

[0040] In the case of the backup process of the first image data stored in the information terminal 10 in step S14, first, the backup application 18 sets m=1 (step S21) and retrieves information of the first image data with m=1 in the backup list obtained in step S12 of Figure 4 from the internal storage 13 (step S22). The image data information includes, for example, the image data itself and information related to that data.

[0041] Next, the backup application 18 separates the image data acquired in step S22 into actual data and metadata (step S23), and writes the image data to the external storage device 20 (step S24).

[0042] The backup application 18 determines whether the saving of image data to the external storage device 20 in step S24 was successful (step S25).

[0043] If saving the image data fails in step S25 (step S25: No), the backup application 18 determines whether the failure is due to a persistent cause (step S26). A persistent failure is, for example, N or more failures as described above.

[0044] If it is determined in step S26 that it is not a continuous failure (step S26: No), the backup application 18 returns to step S22 and executes each process. If it is determined that it is not a continuous failure, it may return to step S22 after waiting for a predetermined time. Also, if the error does not require returning to step S22 to acquire image data information again, it may return to step S24 and execute each process.

[0045] If step S26 determines that the failure is persistent (step S26: Yes), the backup application 18 displays the results of the backup process on the display screen of the information terminal 10 (step S30). If the cause of the failure is persistent, the image data related to that failure is not saved, at least not in this backup process.

[0046] On the other hand, if the image data is successfully saved in step S25 (step S25: Yes), the backup application 18 registers the information of the first image data m=1 in the written list (step S27).

[0047] Next, the backup application 18 determines whether the number of first image data to be backed up (m-th) has reached the M-th (m=M?) (step S28). The M in the M-th is the number of first image data registered in the backup list.

[0048] If m=M in step S28 (step S28: No), the backup application 18 returns to step S22 and executes each process, setting m=m+1 (step S29). If m=M in step S28 (step S28: Yes), that is, if the backup process for the first image data registered in the backup list is completed, the backup application 18 displays the result of the backup process on the display screen of the information terminal 10 (step S30).

[0049] Furthermore, in the case of the backup process of the second image data stored on the server 50 in step S15 of Figure 4, the process will be as follows.

[0050] The backup application 18 obtains the information of the second image data with m=1 in the backup list obtained in step S12 of Figure 4 by downloading it from the server 50 (step S22), with m=1 set (step S21). The processing from step S23 onwards is the same as the backup processing of the first image data described above.

[0051] <List of entries> Figure 6 shows an example of a written list. As shown in Figure 5, the written list contains identification information of image data (files) that have been successfully saved to the external storage device 20. For example, the written list 60 includes "file name" and "writing date and time" as attribute information of the image data. The written list 60 is an example of the "first list" of the present invention.

[0052] <Backup of image data> Figure 7 shows the backup flow of the first image data in the communication system 1. The first image data is the image data whose data body (the data to be backed up) is stored in the information terminal 10. The first image data is backed up from the information terminal 10 to the external storage device 20.

[0053] As shown in Figure 7, the internal storage 13 of the information terminal 10 is provided with a photo / video folder 13a for saving the first image data and a dedicated folder 13b, which is a temporary folder assigned to the backup application 18. In addition, the storage 23 of the external storage device 20 is provided with an information terminal folder 23a for backing up the first image data.

[0054] The first image data is stored as image data 30 in the photo / video folder 13a under the management of the operating system 17. The backup application 18 requests one of the first image data files 30 stored in the photo / video folder 13a based on the image data management list obtained from the operating system 17. The operating system 17 sends one of the first image data files 30 to the backup application 18 in response to the request. The backup application 18 temporarily stores the received first image data file as image data 30 in a dedicated folder 13b.

[0055] Next, the backup application 18 backs up the first image data stored in the dedicated folder 13b as image data 30 to the information terminal folder 23a of the external storage device 20. When the backup application 18 backs up one first image data to the information terminal folder 23a, it registers the identification information (e.g., file name, write date and time) of the successfully backed-up first image data in the written list 60 (see Figure 6). Also, when the backup application 18 backs up one first image data to the information terminal folder 23a, it deletes the first image data that was stored in the dedicated folder 13b from the dedicated folder 13b. This series of backup processes of the first image data from the photo / video folder 13a of the information terminal 10 to the information terminal folder 23a of the external storage device 20 is repeated for the number of first image data in the management list.

[0056] However, when the first image data that was successfully backed up is registered in the written list 60 (for example, the second backup process), the process is repeated for the number of first image data entries in the backup list after the first image data entries in the written list 60 have been deleted from the first image data entries in the management list.

[0057] Figure 8 shows the backup flow of the second image data in communication system 1. The second image data is the image data whose main data (the data to be backed up) is stored on server 50. The second image data is stored on information terminal 10 as a simplified version of the main data, such as a thumbnail. The second image data is backed up from server 50 to external storage device 20.

[0058] As shown in Figure 8, the internal storage 13 of the information terminal 10 is provided with a cache folder 13c for storing the second image data and a dedicated folder 13b, which is a temporary folder assigned to the backup application 18. In addition, the storage 23 of the external storage device 20 is provided with an information terminal folder 23a for backing up the second image data.

[0059] The backup application 18 requests one of the second image data files 30 stored in the cache folder 13c based on the image data management list obtained from the operating system 17. In response to this request, if the second image data file is not in the cache folder 13c, the operating system 17 downloads the second image data file from the server 50, saves it as image data 30 in the cache folder 13c, and sends the second image data file to the backup application 18. If the second image data file is in the cache folder 13c, the operating system 17 reads the second image data file from the cache folder 13c and sends it to the backup application 18.

[0060] The backup application 18 temporarily saves the received second image data as image data 30 in a dedicated folder 13b. Furthermore, if the second image data cannot be downloaded due to insufficient capacity in the cache folder 13c when requested, the backup application 18 may request that more capacity be allocated to the cache folder 13c, and then request the second image data again.

[0061] Next, the backup application 18 backs up the second image data stored in the dedicated folder 13b as image data 30 to the information terminal folder 23a of the external storage device 20. When the backup application 18 backs up one second image data to the information terminal folder 23a, it registers the identification information (e.g., file name, write date and time) of the successfully backed-up second image data in the written list 60 (see Figure 6). Also, when the backup application 18 backs up one second image data to the information terminal folder 23a, it deletes the second image data that was stored in the dedicated folder 13b from the dedicated folder 13b. This series of backup processes of the second image data from the cache folder 13c of the information terminal 10 to the information terminal folder 23a of the external storage device 20 is repeated for the number of second image data in the management list.

[0062] However, when the second image data that was successfully backed up is registered in the written list 60 (for example, the second backup process), the process is repeated for the number of second image data entries in the backup list after the second image data entries in the written list 60 have been deleted from the second image data entries in the management list.

[0063] In the above embodiment, the first image data stored in the information terminal 10 and the second image data stored in the server 50 are classified, and then the first image data is backed up first, followed by the second image data. However, the system is not limited to this. For example, after classifying the data into first and second image data, the user may be allowed to select which files to back up. Specifically, the user may be allowed to select whether to back up only the first image data, only the second image data, or both the first and second image data. Furthermore, after classifying the data into first and second image data, the user may be allowed to select the extraction conditions for the files to be backed up. Specifically, the user may be allowed to select whether to back up image data for a predetermined imaging period, or to back up media types (video only), etc.

[0064] Furthermore, after classifying the data into first and second image data, if the information terminal 10 is not connected to the wireless LAN, only the first image data may be backed up, and the second image data may not be backed up. Alternatively, after classifying the data into first and second image data, the second image data may be backed up first, and then the first image data may be backed up. This makes it possible for users, for example, when they are about to go out, to prioritize backing up the second image data (cloud data) before they leave (while they can still use the wireless LAN).

[0065] As explained above, the backup application 18 of the information terminal 10 performs a first backup process that saves files managed by the information terminal 10 to the external storage device 20 and registers the identification information of the successfully saved files in a written list. In the second backup process, which is executed after the first backup process, when saving files managed by the information terminal 10 to the external storage device 20, it saves files excluding those registered in the written list. With this configuration, files that were successfully saved in the previous backup process are not backed up in the next backup process, so the files to be backed up can be efficiently saved to the external storage device 20.

[0066] Furthermore, in the first backup process, if saving a file to the external storage device 20 fails, the backup application 18 of the information terminal 10 will not attempt to save the file involved in the failure to the external storage device 20 if the cause of the failure is persistent, and will attempt to re-save the file involved in the failure to the external storage device 20 if the cause of the failure is not persistent. With this configuration, for example, files that fail to save due to an accidental write error can be saved by re-executing the backup process, thus enabling efficient saving of files to be backed up to the external storage device 20.

[0067] Furthermore, the backup application 18 on the information terminal 10 registers the identification information of files successfully saved in the second backup process into the written list. With this configuration, instead of creating a new written list in the second backup process, the files successfully saved in the second backup process are registered in the written list inherited from the first backup process, thus reducing the data size of the written list.

[0068] Furthermore, the backup application 18 on the information terminal 10 does not register the identification information of files that failed to save in the written list during the first backup process. This configuration reduces the data size of the written list compared to a configuration that simply logs backups. Also, for example, if a backup process is interrupted and a file fails to save, the backup process will be executed again in the next backup process, so that all files to be backed up can be saved to the external storage device 20 without any omissions.

[0069] <Variation> Figure 9 shows a modified example of the communication system 1. As shown in Figure 9, in the communication system 1, the information terminal 10 may be configured to be communicatively connected to a plurality of external storage devices (in this example, a first external storage device 20A and a second external storage device 20B). For example, if the connection between the information terminal 10 and the external storage devices is wired, the first external storage device 20A and the second external storage device 20B are connected to the information terminal 10 via a hub. The first external storage device 20A is an example of the "second external storage device" of the present invention. The second external storage device 20B is an example of the "first external storage device" of the present invention.

[0070] In this configuration, the files to be backed up include files stored on the first external storage device 20A.

[0071] The backup application 18 of the information terminal 10 instructs the processor 11 to perform a process in the second backup process to save to the second external storage device 20B all files stored in the first external storage device 20A except for those registered in the first list. Files stored in the first external storage device 20A are, for example, files saved from the information terminal 10 to the first external storage device 20A. Files registered in the first list are files that were successfully saved from the first external storage device 20A to the second external storage device 20B in the first backup process. Saving the excluded files to the second external storage device 20B means saving files that have not yet been saved from the first external storage device 20A to the second external storage device 20B.

[0072] Furthermore, in the second backup process, the backup application 18 instructs the processor 11 to save to the second external storage device 20B the files stored in the first external storage device 20A, excluding the files registered in the first list and the files stored in the second external storage device 20B. In other words, the backup application 18 excludes not only the files registered in the first list, but also files already stored in the second external storage device 20B from the files to be saved to the second external storage device 20B. For example, files that have already been backed up and saved to the second external storage device 20B directly from the information terminal 10 are also excluded from the files to be saved.

[0073] Furthermore, if the backup application 18 detects a file stored on the information terminal 10 that is also stored on multiple external storage devices 20, it causes the processor 11 to execute a process that notifies the user to delete the detected file from the information terminal 10. "Files stored on the information terminal 10" refers to files stored on the information terminal 10, not files stored in the cloud (e.g., server 50). "Detecting files also stored on multiple external storage devices 20" means, for example, detecting files based on a list of files backed up from the information terminal 10 to the first external storage device 20A and a list of files backed up from the first external storage device 20A to the second external storage device 20B. "Notification prompting the user to delete" is a notification that accepts a response, such as "Do you want to delete? Yes / No". In this case, if Yes is selected, the file is deleted. Alternatively, "notification prompting the user to delete" may simply be a notification that suggests deleting the file using normal operation.

[0074] <Processing of backup application 18 in the modified example> Figure 10 is a flowchart illustrating an example of the processing of the backup application 18 in a modified example. The processing in this flowchart is started by tapping, for example, the "Save Between Storages" icon displayed on the display screen of the information terminal 10. This example describes the case where image data (an example of a file) backed up from the information terminal 10 to the first external storage device 20A is backed up from the first external storage device 20A to the second external storage device 20B.

[0075] First, the backup application 18 obtains a first written list of image data backed up from the information terminal 10 to the first external storage device 20A (step S31). The first written list may be stored, for example, on the information terminal 10 or on the first external storage device 20A.

[0076] Next, the backup application 18 obtains a second written list of files that have already been successfully backed up from the first external storage device 20A to the second external storage device 20B (step S32). The second written list is an example of the "first list" of the present invention. The second written list may be stored, for example, in the information terminal 10, or in the first external storage device 20A or the second external storage device 20B.

[0077] The backup application 18 removes the image data in the second written list from the first written list obtained in step S31, for example, to obtain a backup list (step S33).

[0078] The backup application 18 backs up the image data of the first written list from the first external storage device 20A to the second external storage device 20B based on the backup list obtained in step S33 (step S34). The backup process in step S34 is explained in Figure 11.

[0079] Figure 11 is a flowchart showing the backup process in step S34 in Figure 10.

[0080] First, the backup application 18, with m=1 (step S41), obtains information about the image data with m=1 in the backup list obtained in step S33 of Figure 10 from the first external storage device 20A (step S42). The image data information includes, for example, the image data itself and information related to that data.

[0081] The backup application 18 reads the image data acquired in step S42 from the first external storage device 20A and writes it to the second external storage device 20B (step S43).

[0082] The backup application 18 determines whether the saving of image data to the second external storage device 20B in step S43 was successful (step S44).

[0083] If saving the image data fails in step S44 (step S44: No), the backup application 18 determines whether the failure is due to a persistent cause (step S45). A persistent failure is, as mentioned above, for example, N or more failures.

[0084] If it is determined in step S45 that it is not a continuous failure (step S45: No), the backup application 18 returns to step S42 and executes each process. If it is determined that it is not a continuous failure, it may return to step S42 after waiting for a predetermined time. Also, if the error does not require obtaining image data information from the first external storage device 20A again after returning to step S42, it may return to step S44 and execute each process.

[0085] If step S45 determines that the failure is persistent (step S45: Yes), the backup application 18 displays the results of the backup process on the display screen of the information terminal 10 (step S49). If the cause of the failure is persistent, the image data related to that failure is not saved, at least not in this backup process.

[0086] On the other hand, if the image data is successfully saved in step S44 (step S44: Yes), the backup application 18 registers the information of the first image data (m=1) in the second written list (step S46).

[0087] Next, the backup application 18 determines whether the number of image data to be backed up (m-th) has reached the Mth (m=M?) (step S47). The Mth is the number of image data registered in the backup list.

[0088] If m=M in step S47 (step S47: No), the backup application 18 returns to step S42 and executes each process, setting m=m+1 (step S48). If m=M in step S47 (step S47: Yes), that is, if the backup process for the image data registered in the backup list is completed, the backup application 18 displays the result of the backup process on the display screen of the information terminal 10 (step S49).

[0089] <Backup of image data in the modified image> Figure 12 is a diagram illustrating the image data backup process in communication system 1. In this modified example, the image data to be backed up is the image data stored in the first external storage device 20A. The image data to be backed up is backed up from the first external storage device 20A to the second external storage device 20B.

[0090] As shown in Figure 12, the internal storage 13 of the information terminal 10 is provided with a dedicated folder 13b, which is a temporary folder assigned to the backup application 18. In addition, the storage 23A of the first external storage device 20A is provided with an information terminal folder 23Aa for backing up image data. The storage 23B of the second external storage device 20B is provided with an information terminal folder 23Ba for backing up image data.

[0091] The image data to be backed up is stored as image data 30 in the information terminal folder 23Aa of the first external storage device 20A. Based on the first written list of image data backed up from the information terminal 10 to the first external storage device 20A, the backup application 18 reads one of the image data 30 stored in the information terminal folder 23Aa. The backup application 18 temporarily saves the read image data as image data 30 in the dedicated folder 13b.

[0092] Next, the backup application 18 backs up the image data stored in the dedicated folder 13b to the information terminal folder 23Ba of the second external storage device 20B as image data 30. When the backup application 18 backs up one image data to the information terminal folder 23Ba, it registers the identification information (e.g., file name, date and time of writing) of that successfully backed-up image data in the second written list (see, for example, Figure 6). Also, when the backup application 18 backs up one image data to the information terminal folder 23Ba, it deletes the image data that was stored in the dedicated folder 13b from the dedicated folder 13b. This series of image data backup processes from the information terminal folder 23Aa of the first external storage device 20A to the information terminal folder 23Ba of the second external storage device 20B is repeated for the number of image data in the first written list.

[0093] However, if the image data that was successfully backed up is registered in the second written list (for example, the second backup process), the process is repeated for the number of image data files in the backup list after deleting the image data files from the second written list from the image data files in the first written list.

[0094] Figure 13 shows an example of a notification prompting the user to delete a file. As described above, when the backup application 18 detects a file stored on the information terminal 10 that is also stored on the first external storage device 20A and the second external storage device 20B, it issues a notification prompting the user to delete the detected file from the information terminal 10.

[0095] The detection of, for example, "duplicate files" stored in both the first external storage device 20A and the second external storage device 20B is performed based on a first written list showing image data backed up from the information terminal 10 to the first external storage device 20A, and a second written list showing image data backed up from the first external storage device 20A to the second external storage device 20B.

[0096] If duplicate files are detected, as shown in Figure 13, the touch panel 14a of the information terminal 10 will display a message 71 such as "The following files have been backed up on both SSD#1 and SSD#2. Do you want to delete these files from the terminal?", a file name 72 such as "·AAAA.JPG ·BBBB.mpeg ·CCCC.jpg", an erase button 73 to tap to delete, and a do not erase button 74 to tap to not delete.

[0097] When the delete button 73 is tapped, the duplicate file with the displayed file name 72 is deleted from the information terminal 10. Although the duplicate file is deleted from the information terminal 10, it remains saved on the first external storage device 20A and the second external storage device 20B, so it can be restored to the information terminal 10. This notification prompting the user to delete the duplicate file is executed, for example, after the backup process shown in Figure 11.

[0098] In this modified example, the backup application 18 of the information terminal 10, in a backup process that saves files managed by the information terminal 10 to the first external storage device 20A, obtains a first written list indicating files that have been successfully saved, saves the files stored in the first external storage device 20A to the second external storage device 20B, and executes a first backup process that registers the identification information of the successfully saved files in the second written list. In the second backup process, which is executed after the first backup process, when saving files stored in the first external storage device 20A to the second external storage device 20B, the application saves the files based on a backup list obtained by excluding the files registered in the second written list from the files in the first written list. With this configuration, files that have been successfully saved in the previous backup process are not backed up in the next backup process, so files to be backed up can be efficiently saved from the first external storage device 20A to the second external storage device 20B.

[0099] Furthermore, if the backup application 18 of the information terminal 10 detects that a file stored on the information terminal 10 is also stored on multiple external storage devices 20, it will issue a notification prompting the user to delete the detected file from the information terminal 10. This configuration makes it possible to free up space on the internal storage 13 of the information terminal 10.

[0100] (Regarding the control program) The control method for the information terminal described in the above-mentioned embodiment can be realized by executing a pre-prepared control program on a computer. This control program is recorded on a computer-readable storage medium and executed when read from the storage medium. This control program may also be provided in the form of a non-transient storage medium such as flash memory, or it may be provided via a network such as the Internet. The computer that executes this control program may be included in the information terminal, included in an electronic device capable of communicating with the information terminal, or included in a server device capable of communicating with these information terminals and electronic devices.

[0101] As described above, the following matters are disclosed in this specification.

[0102] The disclosed control program is a control program for an information terminal, which causes the processor of the information terminal to execute a first backup process that saves the files to be backed up to an external storage device that can communicate with the information terminal and registers the identification information of the successfully saved files in a first list, and executes a second backup process that is executed after the first backup process, which saves the files to be backed up to the external storage device, based on the first list.

[0103] The disclosed control program causes the processor to execute a process in which, in the first backup process, if it succeeds in saving one file to the external storage device, it registers the identification information of the one file in the first list.

[0104] The disclosed control program causes the processor to perform a process in which, if saving a file to the external storage device fails in the first backup process, it determines whether the cause of the failure is persistent, and if the cause is persistent, it does not perform the saving of the file related to the failure to the external storage device.

[0105] The disclosed control program causes the processor to perform a process in which, if the saving of a file to the external storage device fails in the first backup process, it determines whether the cause of the failure is continuous, and if the cause is not continuous, it re-executes the saving of the file related to the failure to the external storage device.

[0106] The disclosed control program registers the identification information of the files successfully saved in the second backup process in the first list to the processor.

[0107] The disclosed control program includes files managed by the information terminal as files to be backed up.

[0108] The disclosed control program is such that the second backup process is a process of saving files managed by the information terminal, excluding the files registered in the first list, to the external storage device.

[0109] The disclosed control program is such that the information terminal can communicate with a second external storage device which is different from the first external storage device which is the external storage device, and the files to be backed up include files stored on the second external storage device.

[0110] The disclosed control program is such that the second backup process is a process of saving files stored in the second external storage device, excluding the files registered in the first list, to the first external storage device.

[0111] The disclosed control program is a process in which the second backup process saves files stored in the second external storage device to the first external storage device, excluding the files registered in the first list and the files stored in the first external storage device.

[0112] The disclosed control program is such that the first list is stored in the information terminal.

[0113] The disclosed control program is such that the first list is stored in the external storage device.

[0114] The disclosed control program, when it detects a file stored in the information terminal that is also stored in multiple external storage devices, notifies the user to delete the detected file from the information terminal.

[0115] The disclosed control program instructs the processor not to register the identification information of files that failed to be saved in the first backup process in the first list.

[0116] The disclosed control method is a control method for an information terminal, wherein the processor of the information terminal executes a first backup process in which it saves the files to be backed up to an external storage device that can communicate with the information terminal and registers the identification information of the files that were successfully saved to a first list, and executes a second backup process, which is performed after the first backup process, in which it saves the files to be backed up to the external storage device, based on the first list. [Explanation of Symbols]

[0117] 1. Communication System 10 Information terminals 11 processors 12 Main Memory 13 Internal Storage 13a Photo / Video Folder 13b Dedicated folder 13c Cache Folder 14 User Interface 14a Touch Panel 15 Wireless Communication Interface 16 Wired Communication Interface 17 Operating Systems 18 Backup Applications 20 External storage devices 20A First External Storage Device 20B Second External Storage Device 23, 23A, 23B Storage 23Aa Folder for information terminal 23Ba Folder for Information Terminal 23a Folder for information terminal 30 Image Data 40 Networks 50 servers 60 Written List 71 Message 72 filenames 73. Erase button 74. Do not erase button

Claims

1. A control program for an information terminal, The processor of the aforementioned information terminal, The first backup process is executed, which saves the files to be backed up to an external storage device that can communicate with the information terminal, and registers the identification information of the files that were successfully saved in the first list. A second backup process, which is performed after the first backup process and saves the files to be backed up to the external storage device, is performed based on the first list. A control program that executes a process.

2. A control program according to claim 1, The aforementioned processor, In the first backup process, if saving a file to the external storage device is successful, the identification information of the file is registered in the first list. A control program that executes a process.

3. A control program according to claim 1, The aforementioned processor, In the first backup process, If saving the file to the external storage device fails, determine whether the cause of the failure is continuous. If the aforementioned cause is persistent, saving the file related to the failure to the external storage device will not be performed. A control program that executes a process.

4. A control program according to claim 1, The aforementioned processor, In the first backup process, If saving the file to the external storage device fails, determine whether the cause of the failure is continuous. If the aforementioned cause is not continuous, the saving of the file related to the failure to the external storage device will be re-executed. A control program that executes a process.

5. A control program according to claim 1, The aforementioned processor, The identification information of the files successfully saved in the second backup process is registered in the first list. Control program.

6. A control program according to claim 1, The files to be backed up include files managed by the information terminal, Control program.

7. A control program according to claim 6, The second backup process is a process of saving files managed by the information terminal, excluding the files registered in the first list, to the external storage device. Control program.

8. A control program according to claim 1, The information terminal is capable of communicating with a second external storage device, which is different from the first external storage device, which is the external storage device. The files to be backed up include files stored on the second external storage device, Control program.

9. A control program according to claim 8, The second backup process is a process of saving files stored in the second external storage device, excluding the files registered in the first list, to the first external storage device. Control program.

10. A control program according to claim 9, The second backup process is a process of saving files stored in the second external storage device to the first external storage device, excluding the files registered in the first list and the files stored in the first external storage device. Control program.

11. A control program according to claim 1, The first list is stored in the information terminal. Control program.

12. A control program according to claim 1, The first list is stored in the external storage device. Control program.

13. A control program according to claim 1, The aforementioned processor, If a file stored on the information terminal is detected to also be stored on multiple external storage devices, the system will notify the user to delete the detected file from the information terminal. Control program.

14. A control program according to any one of claims 1 to 13, The aforementioned processor, In the first backup process, the identification information of files that failed to save is not registered in the first list. Control program.

15. A method for controlling an information terminal, The processor of the aforementioned information terminal The first backup process is executed, which saves the files to be backed up to an external storage device that can communicate with the information terminal, and registers the identification information of the files that were successfully saved in the first list. A second backup process, which is performed after the first backup process and saves the files to be backed up to the external storage device, is performed based on the first list. Control method.

Citation Information

Patent Citations

  • Storage system and method for backup data, information server used by the same, mobile terminal, and program

    JP2006013824A