Image backup method and device

Abstract

The embodiment of the invention provides an image backup method and device, and is applied to the technical field of terminals. The method comprises the steps that in response to a first user operation, a first device is connected with a second device, and the second device comprises a plurality of images. Then responding to the second user operation, a first interface is displayed in the first device, and the first interface comprises the first control and the multiple images. In response to a third user operation acting on the first control, the first device displays a second interface, and the second interface comprises a second control. And in response to a fourth user operation acting on the second control, the first equipment configures an image backup strategy. And in response to the fifth user operation, the first device backs up the plurality of images based on the image backup strategy. According to the technical scheme, the multiple images in the second equipment are backed up to the first equipment through the configured image backup strategy, so that automatic image classification backup based on the image backup strategy can be effectively realized, the time consumption of image backup is saved, and the efficiency is improved.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to an image backup method and device. Background Art

[0002] Data backup refers to copying data from one device to another, thereby providing backup protection for data security issues caused by data damage or data loss.

[0003] There is a specific scenario in data backup, which is image backup. The current technical solution for image backup, especially for classified image backup, is that the user usually manually creates multiple backup folders in the target device, and then manually classifies and identifies the images to be backed up. For each category of images, the user is required to manually copy and paste, so that the image is backed up in the corresponding category folder.

[0004] This image backup method has the problems of being time-consuming and inefficient. Summary of the invention

[0005] The embodiments of the present application provide an image backup method and device, which are applied in the field of terminal technology.

[0006] In a first aspect, an embodiment of the present application provides an image backup method. The method comprises:

[0007] In response to a first user operation, a first device is connected to a second device, wherein the second device includes a plurality of images. Then, in response to a second user operation, a first interface is displayed in the first device, wherein the first interface includes a first control and a plurality of images. In response to a third user operation acting on the first control, the first device displays a second interface, wherein the second interface includes a second control. In response to a fourth user operation acting on the second control, the first device configures an image backup policy. In response to a fifth user operation, the first device backs up the plurality of images based on the image backup policy.

[0008] In this implementation, by connecting the first device and the second device, and displaying the first control for multiple images and the second interface for triggering the backup configuration in the first device, on the one hand, the function of viewing images can be provided to the user, and on the other hand, the second interface for configuring the image backup strategy can be displayed based on the first control, and then the image backup strategy can be configured by operating the second control in the second interface, and finally the image can be backed up according to the image backup strategy, so that the image backup side can be flexibly configured according to actual needs to save time and improve efficiency of image backup.

[0009] In some implementations, the image backup strategy is: backing up a target image among the multiple images to a target directory of a target folder in the first device.

[0010] In some implementations, the second control is a first affirmative control, the target image is an image among the multiple images that has not been backed up in an incremental folder, and the target folder is an incremental folder in the first device for backing up incremental images.

[0011] In some implementations, the second control is a first negative control, the target image is at least a portion of the multiple images, and the target folder is a newly expanded folder created in response to the fourth user operation.

[0012] In this way, the target image can be stored in the target folder of the first device according to the corresponding image tag, so as to provide the optional functions of configuring only incremental images and backing up full images, thereby improving the flexibility of image backup.

[0013] In some implementations, the method further includes:

[0014] In response to a sixth user operation performed on the first interface, the first device determines a selected image from the multiple images.

[0015] In some implementations, when the second control is the first affirmative control, the target image is an image among the selected images that has not been backed up in the incremental folder;

[0016] When the second control is the first negative control, the target image is the selected image.

[0017] In this way, the target image can be determined based on the image selected by the user, so as to perform image backup, thereby improving the operability and flexible adjustment of the image backup.

[0018] In some implementations, the second control is a second affirmative control, and the target directory is a directory corresponding to the bottom-level tag with the highest priority of the target image.

[0019] In some implementations, the second control is a second negative control, and the target directory includes a directory corresponding to at least one bottom-level tag of the target image.

[0020] By providing the function of single backup for multi-label images, users can configure corresponding strategies according to actual image backup needs, thereby improving the flexibility and functional completeness of image backup, and effectively reducing the repeated backup of photos, further speeding up the backup speed.

[0021] In some implementations, the second interface further includes a third control;

[0022] The method further comprises:

[0023] In response to a seventh user operation on the third control, the first device updates the multiple images displayed in the first interface.

[0024] In some implementations, the third control is a first confirmation control or a first cancellation control;

[0025] In response to the seventh user operation on the third control, the first device updates the plurality of images displayed in the first interface, including:

[0026] In response to a seventh user operation on the first determination control, the first device updates the first interface to: display the plurality of images according to the image tags of the images; or,

[0027] In response to a seventh user operation on the first cancel control, the first device updates the first interface to display the multiple images according to the generation time periods to which the images belong.

[0028] By providing the first confirmation control and the first cancellation control, the user can adjust the image content displayed in the first interface according to actual needs, saving the user's picture selection operations and improving backup efficiency.

[0029] In some implementations, the third control is a second confirmation control or a second cancellation control;

[0030] In response to the seventh user operation on the third control, the first device updates the image displayed in the first interface, including:

[0031] In response to a seventh user operation on the second determination control, the first device updates the first interface to: display only the images among the plurality of images that are not backed up in the incremental folder; or,

[0032] In response to a seventh user operation on the second cancel control, the first device updates the first interface to display a full amount of the plurality of images.

[0033] By providing a second confirmation control and a second cancel control, the user can adjust the way the images are displayed in the first interface according to actual needs, so that the user can perform image selection operations more efficiently and improve backup efficiency.

[0034] In some implementations, the second interface further includes a fourth control;

[0035] The method further comprises:

[0036] In response to an eighth user operation acting on the fourth control, the first device displays a priority profile;

[0037] An edit operation acting on the priority configuration file is received, the edit operation being used to update a priority of an image tag.

[0038] By providing the user with a function of editing the priority of the second tag, the flexibility of image backup can be further improved, thereby improving the user experience of image backup.

[0039] In some implementations, the second interface further includes a fifth control;

[0040] The method further comprises:

[0041] In response to a ninth user operation on the fifth control, the first device displays a backup information record table, the permission of the backup information record table being read-only.

[0042] By displaying the backup information record table with read-only permission, users can view the specific image backup status.

[0043] In some implementations, the level of the label structure corresponding to the image label of the target image is N, where N is an integer greater than or equal to 1, wherein when N is greater than or equal to 2, any i-th level label is a lower layer label of its corresponding i-1-th level label, where i is an integer greater than or equal to 2 and less than or equal to N;

[0044] The directory structure of the target folder has at least N levels, any tag in the tag structure has a corresponding directory in the directory structure, and the hierarchical relationship between any two first tags and second tags in the tag structure is consistent with the hierarchical relationship between the first directory and the second directory in the directory structure, the first directory corresponds to the first tag, and the second directory corresponds to the second tag.

[0045] The image tag of the target image is stored in the first device, and the second device can obtain the image tag of the target image from the first device. Therefore, it should be understood that the image tag of the target image comes from the first device, and is not generated by the second device.

[0046] In this implementation, it can be ensured that the tag structure composed of the image tags of the target image is consistent with at least a part of the directory structure in the target folder, so that automatic classification and orderly storage can be achieved during the image backup process.

[0047] In a second aspect, an embodiment of the present application provides an image backup device. The device includes:

[0048] A processing module, configured to connect the first device with a second device in response to a first user operation, wherein the second device includes a plurality of images;

[0049] A display module, configured to cause the first device to display a first interface in response to a second user operation, where the first interface includes a first control and the plurality of images;

[0050] The display module is further configured to, in response to a third user operation acting on the first control, cause the first device to display a second interface, where the second interface includes a second control;

[0051] The processing module is further configured to, in response to a fourth user operation acting on the second control, configure the image backup strategy by the first device;

[0052] The processing module is further configured to, in response to a fifth user operation, enable the first device to back up the multiple images based on the image backup strategy.

[0053] In some implementations, the image backup strategy is: backing up a target image among the multiple images to a target directory of a target folder in the first device.

[0054] In some implementations, the second control is a first affirmative control, the target image is an image among the multiple images that has not been backed up in an incremental folder, and the target folder is an incremental folder in the first device for backing up incremental images.

[0055] In some implementations, the second control is a first negative control, the target image is at least a portion of the multiple images, and the target folder is a newly expanded folder created in response to the fourth user operation.

[0056] In some implementations, the method further includes:

[0057] In response to a sixth user operation performed on the first interface, the first device determines a selected image from the multiple images.

[0058] In some implementations, when the second control is the first affirmative control, the target image is an image among the selected images that has not been backed up in the incremental folder;

[0059] When the second control is the first negative control, the target image is the selected image.

[0060] In some implementations, the second control is a second affirmative control, and the target directory is a directory corresponding to the bottom-level tag with the highest priority of the target image.

[0061] In some implementations, the second control is a second negative control, and the target directory includes a directory corresponding to at least one bottom-level tag of the target image.

[0062] In some implementations, the second interface further includes a third control;

[0063] The display module is specifically used for:

[0064] In response to a seventh user operation on the third control, the first device updates the multiple images displayed in the first interface.

[0065] In some implementations, the third control is a first confirmation control or a first cancellation control;

[0066] The processing module is specifically used for:

[0067] In response to a seventh user operation on the first determination control, the first device updates the first interface to: display the plurality of images according to the image tags of the images; or,

[0068] In response to a seventh user operation on the first cancel control, the first device updates the first interface to display the multiple images according to the generation time periods to which the images belong.

[0069] In some implementations, the third control is a second confirmation control or a second cancellation control;

[0070] The processing module is specifically used for:

[0071] In response to a seventh user operation on the second determination control, the first device updates the first interface to: display only the images among the plurality of images that are not backed up in the incremental folder; or,

[0072] In response to a seventh user operation on the second cancel control, the first device updates the first interface to display a full amount of the plurality of images.

[0073] In some implementations, the second interface further includes a fourth control;

[0074] The display module is also used for:

[0075] In response to an eighth user operation acting on the fourth control, the first device displays a priority profile;

[0076] An edit operation acting on the priority configuration file is received, the edit operation being used to update a priority of an image tag.

[0077] In some implementations, the second interface further includes a fifth control;

[0078] The display module is also used for:

[0079] In response to a ninth user operation on the fifth control, the first device displays a backup information record table, the permission of the backup information record table being read-only.

[0080] In some implementations, the level of the label structure corresponding to the image label of the target image is N, where N is an integer greater than or equal to 1, wherein when N is greater than or equal to 2, any i-th level label is a lower layer label of its corresponding i-1-th level label, where i is an integer greater than or equal to 2 and less than or equal to N;

[0081] The directory structure of the target folder has at least N levels, any tag in the tag structure has a corresponding directory in the directory structure, and the hierarchical relationship between any two first tags and second tags in the tag structure is consistent with the hierarchical relationship between the first directory and the second directory in the directory structure, the first directory corresponds to the first tag, and the second directory corresponds to the second tag.

[0082] In a third aspect, an embodiment of the present application provides a terminal device, which may also be referred to as a terminal, user equipment (UE), mobile station (MS), mobile terminal (MT), etc. The terminal device may be a mobile phone, a smart TV, a wearable device, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc.

[0083] The terminal device comprises: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory, so that the terminal device executes the method of the first aspect.

[0084] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program. When the computer program is executed by a processor, the method of the first aspect is implemented.

[0085] In a fifth aspect, an embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed, the computer executes the method of the first aspect.

[0086] In a sixth aspect, an embodiment of the present application provides a chip, the chip including a processor, the processor being used to call a computer program in a memory to execute the method described in the first aspect.

[0087] It should be understood that the second to sixth aspects of the present application correspond to the technical solutions of the first aspect of the present application, and the beneficial effects achieved by each aspect and the corresponding feasible implementation methods are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0088] Figure 1 Implementation diagram of picture backup provided in the embodiment of the present application Figure 1 ;

[0089] Figure 2 Implementation diagram of picture backup provided in the embodiment of the present application Figure 2 ;

[0090] Figure 3 A flowchart of an image backup method provided in an embodiment of the present application;

[0091] Figure 4 A schematic diagram of the directory structure and tag structure provided in the embodiment of the present application;

[0092] Figure 5 A schematic diagram of the implementation of the backup configuration bar provided for this application;

[0093] Figure 6 Operation diagram of the backup configuration bar provided in the embodiment of the present application Figure 1 ;

[0094] Fig. 7A The image label provided in the embodiment of the present application is shown in FIG. Figure 1 ;

[0095] Figure 7B The image label provided in the embodiment of the present application is shown in FIG. Figure 2 ;

[0096] Figure 8 A schematic diagram of the implementation of the backup information record table provided in the embodiment of the present application;

[0097] Fig. 9 Operation diagram of the backup configuration bar provided in the embodiment of the present application Figure 2 ;

[0098] Fig.10 Operation diagram of the backup configuration bar provided in the embodiment of the present application Figure 3 ;

[0099] Fig.11 Operation diagram of the backup configuration bar provided in the embodiment of the present application Figure 4 ;

[0100] Fig.12 An interactive flow chart of image backup processing provided in an embodiment of the present application;

[0101] Fig.13 Schematic diagram of updating the first interface provided in the embodiment of the present application Figure 1 ;

[0102] Fig.14 Schematic diagram of updating the first interface provided in the embodiment of the present application Figure 2 ;

[0103] Fig.15 Schematic diagram of the priority configuration file provided in the embodiment of the present application Figure 1 ;

[0104] Fig.16 Schematic diagram of the implementation of the priority configuration file provided in the embodiment of the present application Figure 2 ;

[0105] Fig.17 A schematic diagram of the implementation of viewing the backup information record table provided in an embodiment of the present application;

[0106] Fig.18 A flowchart of an image backup method provided in an embodiment of the present application;

[0107] Fig.19 A schematic diagram of the structure of an image backup device provided in an embodiment of the present application;

[0108] Fig. 20 A schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0109] In order to facilitate the clear description of the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0110] In the embodiments of the present application, "at least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0111] It should be noted that the "at..." in the embodiment of the present application can be the instant when a certain situation occurs, or a period of time after a certain situation occurs, and the embodiment of the present application does not specifically limit this. In addition, the display interface provided in the embodiment of the present application is only an example, and the display interface can also include more or less content.

[0112] In order to better understand the technical solution of the present application, the relevant technologies involved in the present application are further introduced in detail below.

[0113] Data backup refers to copying data from one device to another, thereby providing backup protection for data security issues caused by data damage or data loss, and data backup can also save a certain amount of device storage space.

[0114] Among them, a common application scenario of data backup is picture backup, that is, users can back up pictures in the source device to the target device, for example, the source device is a mobile phone, and the target device is a personal computer (PC), that is, users can back up pictures in the mobile phone to the PC. Or, for example, the source device is a tablet computer, and the target device is a PC, that is, users can back up pictures in the tablet computer to the PC. This application does not impose any special restrictions on the specific implementation of the source device and the target device of the picture backup, which can be selected according to actual needs.

[0115] Especially for some users who do not want to use network storage and cloud storage, backing up pictures from the source device to the target device is a more preferred way to back up pictures. At the same time, this implementation method can avoid the information security issues caused by backing up pictures in the cloud and protect the user's personal privacy.

[0116] Currently, there are usually two ways for users to back up pictures from the source device to the target device. The following example takes the source device as a mobile phone and the target device as a PC as an example. Figure 1 and Figure 2 These two implementation methods are explained. Figure 1 Implementation diagram of picture backup provided in the embodiment of the present application Figure 1 , Figure 2 Implementation diagram of picture backup provided in the embodiment of the present application Figure 2 .

[0117] The first implementation method is to connect the mobile phone and the PC, where the connection can be a wired connection, for example, a wired connection between the mobile phone and the PC can be achieved through a universal serial bus USB; or the connection can also be a wireless connection, for example, a wireless connection between the mobile phone and the PC can be achieved through Bluetooth or access to the same local area network and other technologies. This embodiment does not limit the connection method between the mobile phone and the PC.

[0118] exist Figure 1 In the description, a wired connection is used as an example for explanation, and the implementation of a wireless connection is similar, so it will not be described in detail.

[0119] like Figure 1 As shown, after the mobile phone and the PC are connected, for example, an authorization operation can be performed in the mobile phone, and then the folder of the mobile phone can be accessed in the PC, thereby opening the folder storing pictures in the mobile phone to back up the pictures.

[0120] Reference Figure 1 In 101, it is assumed that the file path of the folder for storing pictures of the mobile phone opened in the PC is: mobile phone A / internal storage / DCIM / camera (where mobile phone A is the device name). Then, the user can manually select the pictures to be backed up in the folder opened as shown in 101, and store the pictures to be backed up in the designated folder in the PC through the copy command, where the designated folder for storing the backup pictures can be, for example, Figure 1 Get the "Backup" folder in the C drive as shown in 101.

[0121] like Figure 1 As shown, assuming that the pictures that need to be backed up are manually selected by the user Figure 1 If the images 1, 3, 6 and 11 are shown in 101, then after backing up the images by using the copy command, refer to Figure 1 By using 102 in the figure, the four images, image 1, image 3, image 6 and image 11, can be backed up in a designated folder in the PC.

[0122] Next, combine Figure 2 The second implementation method is introduced. The second implementation method is to connect the mobile phone and PC by wire and authorize them, then open the mobile assistant application in the PC, and then you can access the data in the mobile phone in the mobile assistant application.

[0123] like Figure 2 As shown in the figure, in the mobile assistant application, you can access the contacts, information, pictures, videos and other data in the mobile phone. For picture data, you can display them according to the albums to which the pictures belong. Figure 2 In the illustration, for example, there may be album categories such as camera pictures, screenshots, wallpapers, and other albums, and for pictures in each album category, the pictures may be displayed according to time periods.

[0124] Similarly, users can manually select the pictures to be backed up, refer to Figure 2 In 201, it is assumed that the user selects image 1, image 3, and image 6 for backup. After completing the selection, the user can, for example, click an "export" button in the interface to store the images to be backed up in a designated folder in the PC, where the designated folder for storing the backup images can be pre-configured. Figure 2 In the example, the specified folder can be Figure 2 Get the "Backup" folder in the C drive as shown in 201. Figure 2 According to 202, the three images, image 1, image 3 and image 6, can be backed up in a designated folder in the PC.

[0125] Currently, when users back up pictures from their mobile phones to their PCs, they usually have the following two requirements:

[0126] The first is the need for image classification. However, since there are usually a large number of images in a mobile phone, when backing up the images directly to a PC, the backed-up images are actually large and disorganized. Currently, users are required to manually classify the backed-up images. Specifically, users need to manually create folders of different categories on the PC to store different types of images and achieve a large number of image classifications.

[0127] The second is the need to manage picture backup information. Since picture backup is not a regular behavior, when the interval between two backups is long, users will forget which pictures have been backed up and which have not been backed up. At the same time, users will not necessarily delete the pictures backed up on the computer from the mobile phone, so it is necessary to manage picture backup information to avoid repeated backup of certain pictures.

[0128] However, the two image backup methods introduced above cannot meet the above requirements. Therefore, the current image backup methods have the problem of poor user experience. After further analysis, the problems existing in the image backup methods introduced above are specifically manifested in the following four aspects.

[0129] 1. Unable to automatically create a classification directory: The existing image backup methods require users to manually create folders of different categories, then determine the image categories one by one, and move or transfer the images to files of the corresponding categories, which greatly increases the workload of users in backing up images. In the implementation method of the mobile assistant application, it also reduces the actual experience of using the mobile assistant application.

[0130] 2. Unable to automatically identify unbacked up pictures: Usually, users want to back up only the unbacked up pictures in their phones, such as the pictures that were not backed up last time and the pictures that were newly added to their phones. However, as time goes by, a large number of pictures will be added to the user's phone. At the same time, users may forget which pictures have been backed up on the computer, when they were backed up, and where the backed up pictures are, because the user's backup behavior may be random. The picture backup method described above does not provide the function of managing picture backup information, and cannot automatically identify unbacked up pictures.

[0131] 3. Repeated backup of multi-label images: Currently, most of the gallery apps in mobile phones are equipped with image classification models, so it is possible to label images in the gallery apps. Creating a directory structure based on the labels corresponding to the images for image backup is one way to implement image classification. However, a picture in the gallery may correspond to multiple labels. For example, the same travel picture may have a geographic label "Province B", an object type label "Scenery", a time type label "A Certain Moment", etc. This means that if users directly classify and back up pictures according to their labels, they may unconsciously back up the same picture multiple times, which wastes the storage space of the target device to a certain extent and increases the backup time of the pictures (selection and time consumption caused by repeated backup).

[0132] 4. Uncustomizable image display / backup strategy: When processing images for backup purposes, users may need to display only unbacked images; and based on user preferences, users may need to display images by image tags, and need the image tags to be arranged in a certain priority order, for example, users want to prioritize backing up "portrait" images. Existing image backup methods cannot provide the above functions. In the implementation of mobile assistant applications, existing mobile assistants are also unable to set user preferences to display the order of images in the mobile phone in a specific order.

[0133] The root cause of the second and fourth problems is that users have many pictures on their phones. Without considering newly added pictures, the backup may not be completed all at once. In a single backup, users have different preferences for different types of picture backups. Users may prefer to back up specific categories (such as important documents or travel pictures with a strong sense of memory) first.

[0134] Furthermore, the root cause of the third problem is that users may use existing image classification algorithms / methods / tools (such as gallery tags) to classify images to reduce the workload of manual classification. However, the labels assigned to a single image by existing image classification methods may be multi-label, which may result in multiple backups of the same image.

[0135] Therefore, the image backup method introduced above does not take into account the diverse image backup needs of users, and requires users to manually create classification directories and manually manage backup images, which greatly increases the workload of users in backing up and managing backup images (high time and labor costs). The implementation method of using mobile assistant applications to perform image backup reduces the actual experience of users in performing image backup.

[0136] Exemplarily, the time consumption of the image backup method described above can be expressed by the following formula 1:

[0137] TC=T1*NumTag+(T2+T3)*NumImageFormula 1

[0138] Among them, TC represents the total time consumption; T1 represents the time for creating a folder, which can be data in seconds (1-30); T2 represents the time for selecting an image, which can be data in seconds (1-30); T3 represents the transmission time, which is usually less than seconds; NumTag represents the number of file categories, and NumImage represents the number of images.

[0139] Here, calculation formula 1 is explained with a specific example. Assuming that there are 1,000 pictures in the user's mobile phone that need to be backed up, and assuming that the user creates a total of 4 folders, and the creation time T1 of each folder is 10 seconds, and assuming that the time T2 for the user to select a picture is 5 seconds, and the transmission time T3 is 0.1 seconds, then the total backup time is 10s*4+(5s+0.1s)*1000=5140s. This high time cost is difficult for users to accept.

[0140] And refer to the above Figure 2 According to the introduction, although you can select all pictures with one click through "Select All" in the Mobile Assistant application, and then back them up on the computer with one click through "Export", although this implementation method can avoid the time consumption caused by users manually selecting each picture to be backed up, this implementation method still cannot meet the user's classification backup needs, nor can it meet the user's needs to back up only the unbacked pictures, and it cannot customize the display strategy of pictures in the Mobile Assistant, that is to say, it still cannot solve the various problems introduced above.

[0141] In response to the technical problems introduced above, this application proposes the following technical ideas: by improving the mobile phone assistant application, five sub-functions are added to the mobile phone assistant application, including display by picture type, display only unbacked pictures, incremental backup, multi-label single backup and customized configuration strategy (such as image tag priority). The mobile phone assistant application can automatically create a classification directory on the PC, automatically identify unbacked up pictures in the mobile phone, non-duplicate backup of multi-label pictures, and customize the display strategy of the required backup pictures, thereby meeting the diverse picture backup needs of users.

[0142] The image backup method provided by the present application is described in detail below in conjunction with specific embodiments. Figure 3 A flowchart of an image backup method provided in an embodiment of the present application.

[0143] like Figure 3 As shown, the method includes:

[0144] S301. In response to a first user operation, a first device is connected to a second device, and the second device includes a plurality of images.

[0145] The first user operation is an operation of connecting the first device and the second device. Exemplarily, the first device and the second device may be connected by wire, and the first user operation may be, for example, an operation of connecting the first device and the second device via a connecting wire; or the first device and the second device may be connected wirelessly, and the first user operation may be, for example, an operation of configuring Bluetooth, configuring a local area network, or other wireless connection methods in the first device and / or the second device.

[0146] Furthermore, the second device includes multiple images, and the current embodiment aims to back up the multiple images in the second device to the first device, wherein the number and specific content of the images in the second device depend on the actual implementation, and this embodiment does not impose any restrictions on this.

[0147] S302: In response to a second user operation, the first device displays a first interface, where the first interface includes a first control and multiple images.

[0148] The first interface may be an interface displayed in the first application. In this embodiment, the user can perform operations in the first application to complete the image backup. The first application is an application installed in the second device for backing up data in the second device (i.e., the source device) to the first device (i.e., the target device). For example, it may be the mobile assistant application described above, or it may be any application for achieving the purpose of data backup.

[0149] There are many possible implementations of displaying the first interface in response to the second user operation, which are described below:

[0150] In a possible implementation, after the first device is connected to the second device, the user can first open the first application and then click on the image control in the first application. In this case, the second user operation can be the above-mentioned operation of opening the first application and the operation of clicking the image control, and the first device displays the first interface in response to the second user operation. Figure 2 In the example, after opening the first application, the user needs to click "Picture" in the left function bar to display the first interface.

[0151] Alternatively, after the first device is connected to the second device, the first device may also start the first application in response to the establishment of the connection, so that the first application is automatically popped up in the first device, and then the user may click on the image control in the first application. In this case, the second user operation may be the operation of clicking on the image control described above, and the first device displays the first interface in response to the second user operation.

[0152] Alternatively, after the first device is connected to the second device, the first device may also automatically start the first application in response to the establishment of the connection, and automatically enter the first interface in the first application. In this case, the second user operation may be understood to be equivalent to the first user operation described above, that is, in response to the operation of connecting the first device and the second device, the first device is connected to the second device, and the first device displays the first interface.

[0153] In this embodiment, the first interface includes multiple images, and the multiple images here are the multiple images included in the second device. The multiple images included in the first interface may be a subset of the multiple images included in the second device, or may be equivalent to the multiple images included in the second device. The user may browse the images in the first interface or select an image.

[0154] Furthermore, the first interface also includes a first control, which is used to trigger the display of the second interface. The specific style of the first control and the position in the interface can be set according to actual needs.

[0155] S303: In response to a third user operation on the first control, display a second interface, where the second interface includes a second control.

[0156] Afterwards, the first application can detect the operation performed by the user in the first interface, and when the user performs the third user operation on the first control, the second interface can be displayed in response to the third user operation on the first control. For example, the second interface can be displayed in an independent small window on the upper layer of the first interface, or the interface can be directly replaced, that is, the second interface is displayed in a manner that replaces the first interface. The specific display method of the second interface can be selected and set according to actual needs.

[0157] In addition, the third user operation acting on the first control may be, for example, a click operation, a long press operation, etc. on the first control, and the operating medium for the operation on the first control may be a mouse, a keyboard, a part of the human body, etc. This embodiment does not impose any special restrictions on the specific operation method, as long as the operation can evoke the corresponding function of the first control.

[0158] In this embodiment, the second interface includes a second control. Exemplarily, the second interface may include multiple controls. In this embodiment, the controls for configuring the image backup strategy in the second interface are collectively referred to as second controls.

[0159] S304: In response to a fourth user operation on the second control, the first device configures an image backup strategy.

[0160] In this embodiment, the user operates the second control in the second interface to configure a corresponding image backup strategy.

[0161] Exemplarily, the second interface may include at least one backup configuration bar, each of which may include an operation control, and the operation control included in the backup configuration bar is the second control introduced in the current embodiment. The user may perform a fourth user operation on the second control in the backup configuration bar, wherein different second controls correspond to different image backup strategies, and the first device may configure a corresponding image backup strategy in response to the fourth user operation on the second control.

[0162] For example, the second interface may include a first backup configuration bar, and the second control in the first backup configuration bar is used to configure whether to back up only incremental images. For another example, the second interface may also include a second backup configuration bar, and the second control in the second backup configuration bar is used to configure whether to perform only a single backup for images with multiple tags.

[0163] Therefore, it can be understood that a backup configuration column in this embodiment can be used to configure an image backup strategy. In the actual implementation process, any image backup strategy that needs to be configured can be set with a corresponding backup configuration column. For example, a backup configuration column can be set to determine whether to back up only images with specified tags. That is, the specific settings of the backup configuration column can be selected and expanded according to actual needs, and the specific number of backup configuration columns can also be selected and set according to actual needs.

[0164] S305: In response to the fifth user operation, the first device backs up the multiple images based on the image backup policy.

[0165] After the user completes the operation on the second interface and configures the image backup strategy, the first device can back up multiple images based on the image backup strategy, wherein the image backup strategy can indicate which images are to be backed up and where the images are backed up in the first device.

[0166] In this embodiment, multiple images can be backed up based on the image backup strategy in response to the fifth user operation, wherein the fifth user operation can be a user operation on the confirmation control in the second interface, or can be a user operation on the confirmation control in the first interface after returning to the first interface.

[0167] The image backup method provided by the embodiment of the present application includes: in response to a first user operation, a first device and a second device are connected, wherein the second device includes a plurality of images. In response to a second user operation, the first device displays a first interface, wherein the first interface includes a first control and a plurality of images. In response to a third user operation acting on the first control, the first device displays a second interface, wherein the second interface includes a second control. In response to a fourth user operation acting on the second control, the first device configures an image backup strategy. In response to a fifth user operation, the first device backs up a plurality of images based on the image backup strategy. By connecting the first device and the second device, and displaying a first control for a plurality of images and a second interface for triggering backup configuration in the first device, on the one hand, the function of viewing images can be provided to the user, and on the other hand, a second interface for configuring an image backup strategy can be displayed based on the first control, and then the image backup strategy is configured by operating the second control in the second interface, and finally the image is backed up according to the image backup strategy, so that the image backup side can be flexibly configured according to actual needs to save time and improve efficiency of image backup.

[0168] Based on the above embodiments, it can be determined that the image backup strategy mainly involves two aspects of consideration: one is which images are backed up specifically, and the other is where the images are backed up in the first device. Therefore, in this application, the configured image backup strategy can be: backing up a target image among multiple images to a target directory of a target folder in the first device.

[0169] Because the directory of the target folder and the image tag of the target image in this application are associated with each other, before introducing the specific image backup strategy, a brief introduction to the image tag is first given.

[0170] Each target image in this embodiment corresponds to a respective image tag. When backing up the target images, each target image can be backed up to a target folder of the first device according to the image tag corresponding to each target image.

[0171] The image tags of the target images are stored in the second device, and the first device can obtain the image tags of each target image from the second device when backing up the images. Therefore, it should be understood that the image tags are obtained from the second device, not generated by the first device.

[0172] It is understandable that there is a directory structure in the target folder, which means which subfolders are further included in the target folder, and which subfolders are further included in each subfolder, and so on. Each target image corresponds to its own image tag, and different target images may have the same image tag. If the same image tag is understood to be merged together, then the image tags of multiple target images can constitute a tag structure. The tag structure is, for example, which primary tags currently exist, which secondary tags are included under each primary tag, and so on.

[0173] For example, there are currently target image 1 and target image 2, where target image 1 has a primary label A and a secondary label A1 under the primary label A. Target image 2 has label A and a secondary label A2 under the primary label A. Based on the image labels of target image 1 and target image 2, where the primary label A is the same, after merging, the label structure formed by the image labels of the two target images can be obtained, and the primary label A includes secondary labels A1 and A2.

[0174] In this embodiment, when the target image is backed up, the tag structure composed of the image tags of the target image is consistent with at least a portion of the directory structure in the target folder, thereby achieving automatic classification and orderly storage during the image backup process.

[0175] Here, the meaning of the tag structure and "at least part" of the directory structure being consistent is further explained. Specifically, any tag in the tag structure has a corresponding directory in the directory structure. Whether any directory in the directory structure has a corresponding tag in the tag structure depends on the actual situation. When the tag structure and the directory structure are completely consistent, any directory in the directory structure has a corresponding tag in the tag structure. However, when the tag structure is only partially consistent with the directory structure, only some of the directories in the directory structure have corresponding tags in the tag structure.

[0176] The reason for this "partial consistency" is that the target folder may be an incremental folder for storing incremental images, where the incremental folder can be understood as the main folder for backing up images in the first device. Whenever the user chooses to back up an incremental image, the image will be backed up in the incremental folder. Therefore, the directory structure in the incremental folder that has been backed up multiple times is obtained by continuously improving the image tags during the multiple backup processes. Based on the image tag of the target image in this backup process, the directory structure of the incremental folder will also be improved. Therefore, when the image backup is completed, the directory structure of the incremental folder must cover the tag structure corresponding to the image tag of the target image, and may include more directory information than the image tag of the target image.

[0177] At the same time, the target folder may also be an extended folder newly created for this backup process. Then the directory structure in the extended folder is generated based on the image tag of the target image during this backup process. Therefore, for the extended folder, when the image backup is completed, the directory structure of the extended folder and the tag structure corresponding to the image tag of the target image are completely consistent.

[0178] If the tag structure of the image recorded in the first application of the second device is analogous to set S1, and the directory structure of the target folder maintained in the first device is analogous to set S2, then it can be understood that backing up the target image is actually to merge the subset A (corresponding to the image tag of the target image) in set S1 into set S2. Assuming that the set S2 after merging set A is recorded as S2`, it can be guaranteed that at the current moment when the image backup is completed, set S2` must contain set A. In other words, at the current moment when the target image backup is completed, it can be guaranteed that the directory structure of the target folder must cover the tag structure corresponding to the image tag of the target image, that is, the tag structure composed of the image tag of the target image is consistent with at least part of the directory structure in the target folder.

[0179] It should also be noted that, at the moment when the image backup is completed, it is possible to ensure that the tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the target folder. However, after the backup is completed, the user may delete, move, rename, etc. the target image in the second device, and the user may also move the image or delete, move, rename, etc. the folder in the first device. Therefore, after the image backup is completed, if the user adjusts the image or folder, it will affect the result that the tag structure composed of the image tags of the target image introduced here is consistent with at least part of the directory structure in the target folder. At that time, the relationship between the tag structure and the directory structure depends on the actual tag and image situation, which is not limited in this embodiment.

[0180] The same can be explained in conjunction with the example of the above set. After the target image backup is completed, the user's operation may cause the set S2` to change. For example, the changed set is recorded as S2``. Because there are any possible situations for the folder operations performed by the user, it is impossible to guarantee that the changed set S2`` contains the set A. The relationship between the set S2`` and the set A depends on the actual situation after the adjustment.

[0181] Based on the above introduction, it can be determined that any image tag in this embodiment has a corresponding directory in the directory structure of the target folder, and for the hierarchical relationship between the various tags in the tag structure, the same hierarchical relationship also exists between the corresponding directories in the directory structure. It can also be understood that the directory structure in the target folder covers the tag structure composed of the image tags of the target image, so that each target image can be backed up according to its corresponding image tag to the subfolder corresponding to the image tag in the target folder. This effectively reduces the work of users manually creating folders during the image backup process, and quickly and efficiently realizes the automatic classification of images.

[0182] The target folder may be a fixed folder preset in the first device for storing the backup image of the second device, or the target folder may be a new folder created for storing the target image, which is not limited in this embodiment.

[0183] After the backup is completed, the target folder can display each target image according to the directory structure introduced above, thereby effectively realizing the automatic classification backup of the target images.

[0184] Furthermore, the user can open the target folder at any time, whether during or after the image backup is completed. If the user opens the target folder after the image backup is completed, the target folder will store the target images according to the directory structure described above, and the user can view the corresponding images when opening the subfolders in the target folder.

[0185] Alternatively, if the user opens the target folder during the image backup process, the target folder will, on the one hand, store the target images that have been backed up up to the current moment in accordance with the directory structure described above; on the other hand, because the image backup process is still ongoing, the target images that have been backed up after the target folder is opened will also be promptly stored in the corresponding directory in the target folder. When the user opens certain subfolders in the target folder, the images that have just been backed up will also be displayed in the subfolders in sequence as the backup of the corresponding images is completed.

[0186] Based on the above introduction, the following Figure 4 The directory structure in the target folder and the tag structure of the target image are further described in detail. Figure 4 A schematic diagram of the implementation of the directory structure and tag structure provided in the embodiment of the present application.

[0187] In this embodiment, the number of levels of the tag structure is N, where N is an integer greater than or equal to 1.

[0188] When N is 1, there is only one level of the tag structure, that is, there is only one level of tags in the tag structure. When N is greater than or equal to 2, there are multiple levels of the tag structure, and there will be a hierarchical relationship between the multiple levels of tags. Specifically, when N is greater than or equal to 2, any i-th level tag is the lower level tag of its corresponding i-1th level tag, and i is an integer greater than or equal to 2 and less than or equal to N.

[0189] For example, when i is 2, any second-level label has a corresponding first-level label, and the second-level label introduced here is the lower-level label of its corresponding first-level label, that is, there is a hierarchical correspondence between the i-th level label and the i-1-th level label.

[0190] In this embodiment, the tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the target folder, so the hierarchy of the directory structure is at least N levels, and any tag in the tag structure has a corresponding directory in the directory structure, and the hierarchical relationship between any two first tags and second tags in the tag structure is consistent with the hierarchical relationship between the first directory and the second directory in the directory structure, the first directory corresponds to the first tag, and the second directory corresponds to the second tag.

[0191] In order to better understand the label structure and directory structure introduced above, the following is an example of N=2. Then, for example, the label structure composed of the image labels of the target image has 2 levels, and any second-level label (also called a second-level label) is a lower-level label of its corresponding first-level label (also called a first-level label).

[0192] For example, refer to Figure 4 In (a), it is assumed that the label structure composed of the target image's image labels includes four first-level labels: "person", "thing", "place", and "date". And under the first-level label "person", it is assumed that there are three second-level labels: "family", "friends", and "colleagues", then these three second-level labels are used as the lower-level labels of the first-level label "person"; under the first-level label "thing", there are two second-level labels: "food" and "scenery"; under the first-level label "place", it is assumed that there are three second-level labels: "Province A", "Province B", and "Province C"; under the first-level label "date", it is assumed that there are two second-level labels: "May Day holiday" and "Tomb-Sweeping Day".

[0193] Exemplarily, when N is currently equal to 2, the first-level tag is usually pre-set by the gallery application in the second device, for example, the created first-level tag is pre-stored in the database, and the second-level tags included under the first-level tag are often not fixed, which depends on which images are specifically stored in the second device. Among them, the second-level tag can be generated by the gallery application in the second device through the corresponding algorithm by the background process without the user's perception. For example, for an image taken on May 1, 2023, the background process in the gallery application can run the corresponding algorithm, read the timestamp of the image, and determine through algorithm analysis that May 1, 2023 is during the May Day holiday, thereby generating a second-level tag "May Day Holiday" under the first-level tag "Time" for the image.

[0194] For another example, assuming that the second device stores images taken by the user in Province A, Province B, and Province C, then the corresponding first-level tag of Location includes three second-level tags of Province A, Province B, and Province C. For another example, assuming that the second device stores images taken by the user in Province B, Province C, and Province D, then the corresponding first-level tag of Location includes three second-level tags of Province B, Province C, and Province D. Therefore, the specific tag content of the second-level tag is generated by the gallery application in the second device according to the specific image situation, and is not pre-set.

[0195] In the actual implementation process, which levels of labels are pre-set and which levels of labels are determined according to the actual image situation depends on the specific implementation of the gallery application in the second device, and this embodiment does not limit this.

[0196] In this embodiment, the tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the target folder. Correspondingly, any tag in the tag structure has a corresponding directory in the directory structure, and the hierarchical relationship between any two tags has a corresponding directory structure.

[0197] We can take N=2 as an example and combine Figure 4 To understand, such as Figure 4 As shown, the target folder first includes the first-level directories (also called first-level directories) corresponding to the four first-level tags in the tag structure, that is, Figure 4 There are four first-level directories, “People”, “Things”, “Places” and “Dates”, as shown in (b). These four first-level directories correspond to four first-level folders respectively.

[0198] And, under any first-level directory, there are second-level directories (also called second-level directories) corresponding to each second-level tag under the corresponding first-level tag. For example, for the first-level directory "People", its corresponding first-level tag is "People", and the second-level tags under the first-level tag "People" include "Family", "Friends", and "Colleagues". Therefore, the first-level directory includes three second-level directories "Family", "Friends", and "Colleagues" corresponding to these three second-level tags. These three second-level directories also correspond to three second-level folders respectively, which exist in the first-level folder "People".

[0199] Figure 4 The remaining second-level directories under the first-level directories in (b) are similar to those described above. The second-level directories correspond to the second-level tags one by one, and the first-level directories to which the second-level directories belong correspond to the first-level tags to which the corresponding second-level tags belong.

[0200] In the current Figure 4 In the example, for example, the first-level label "People" is used as the first label, and the second-level label "Family" is used as the second label. Then it can be determined that the hierarchical relationship between the first label and the second label currently introduced is that the second label "Family" is the lower label of the first label "People". Among them, the second label "Family" corresponds to the second directory "Family" in the target folder, and the first label "People" corresponds to the first directory "People" in the target folder. Figure 4What can be determined is that the second directory "Family" is also a lower-level directory of the first directory "People", which corresponds to the hierarchical relationship between any two first tags and the second tags in the tag structure introduced above, and is consistent with the hierarchical relationship between the first directory and the second directory in the directory structure.

[0201] In this embodiment, each tag in the tag structure has a corresponding directory in the directory structure, and the hierarchical relationship of the tags in the tag structure is consistent with the hierarchical relationship of at least part of the directories in the directory structure.

[0202] The above combination Figure 4 The specific situation that the tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the target folder is introduced. Figure 4 In the example, the description is made by taking the tag structure containing two levels as an example. In the actual implementation process, the number of levels N contained in the tag structure depends on the specific implementation of the gallery application in the second device. The first device is only responsible for reading the image tags from the second device and then processing the directory structure of the target folder accordingly. This embodiment does not limit the number of levels of the tag structure. No matter how many layers it contains, its implementation method is similar to that described above, as long as the tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the target folder.

[0203] Based on the image tag introduced above, the second control in the second interface and the specific implementation of configuring the image backup strategy according to the second control are further elaborated in detail below. Figure 5 This is a schematic diagram of the implementation of the backup configuration bar provided for this application.

[0204] Figure 5 The first interface is shown in (a) in the figure. As shown in the figure, the first interface includes a first control, that is, Figure 5 Assume that the user clicks on the first control of "Classification Backup", thereby triggering the display of Figure 5 The second interface 50 shown in (b) .

[0205] exist Figure 5 In the illustration, the second interface 50 is displayed above the first interface in the form of a new window, wherein the second interface is a separate window and can be moved to any position independently. Alternatively, in other implementations, the second interface can also be displayed in a window content update manner, that is, there is always only one window, and when the second interface is triggered to be displayed, the second interface is used in the window to replace the first interface. The specific display method of the second interface can be selected and set according to actual needs, and this embodiment does not impose any special restrictions on this.

[0206] The specific contents included in the second interface can be referred to Figure 5 As can be understood from (b) in the figure, at least one backup configuration bar may be included in the second interface.

[0207] Exemplarily, at least one backup configuration bar may include a first backup configuration bar 503, and the first backup configuration bar 503 is used to configure whether to back up only incremental images, wherein incremental images refer to images that are not backed up in the incremental folder. Referring to the diagram, it can be determined that the first backup configuration bar 503 includes a text description of "enable incremental backup" to indicate the specific function of the configuration bar. The first backup configuration bar 503 includes an affirmative control (that is, a "yes" button in 503) and a negative control (that is, a "no" button in 503). In this embodiment, the affirmative control in the first backup configuration bar 503 is referred to as a first affirmative control, and the negative control in the first backup configuration bar 503 is referred to as a first negative control.

[0208] Furthermore, at least one backup configuration bar may further include a second backup configuration bar 504, which is used to configure whether to perform only a single backup of an image containing multiple tags. Referring to the diagram, it can be determined that the second backup configuration bar 504 includes a text description of "starting multiple backups of a single tag" to indicate the specific function of the configuration bar. The second backup configuration bar 504 also includes an affirmative control (i.e., a "yes" button in 504) and a negative control (i.e., a "no" button in 504). In this embodiment, the affirmative control in the second backup configuration bar 504 is referred to as a second affirmative control, and the negative control in the second backup configuration bar 504 is referred to as a second negative control.

[0209] Among them, the first affirmative control, the first negative control, the second affirmative control and the second negative control can be collectively referred to as the second control introduced above.

[0210] In addition, the second interface may also include at least one display configuration bar, which is used to configure the display order of images in the first interface and / or which specific images are displayed. In this embodiment, the controls in the second interface used to configure the image display method in the first interface are collectively referred to as third controls.

[0211] like Figure 5As shown in (b), illustratively, at least one backup configuration bar may include a first display configuration bar 501, and the first display configuration bar 501 is used to configure whether the image in the first interface is displayed according to the image label. Referring to the diagram, it can be determined that the first display configuration bar 501 includes a text description of "display by image type" to indicate the specific function of the configuration bar. The first display configuration bar 501 includes a confirmation control and a cancel control. In this embodiment, the confirmation control in the first display configuration bar 501 is referred to as a first confirmation control, and the cancel control in the first display configuration bar 501 is referred to as a first cancel control.

[0212] At least one backup configuration bar may also include a second display configuration bar 502, which is used to configure whether to display only images that have not been backed up in the incremental folder among the multiple images in the first interface. Referring to the diagram, it can be determined that the second display configuration bar 502 includes a text description of "only displaying images that have not been backed up" to indicate the specific function of the configuration bar, where "not backed up" means not backed up in the incremental folder. The second display configuration bar 502 includes a confirmation control and a cancel control. In this embodiment, the confirmation control in the second display configuration bar 502 is referred to as a second confirmation control, and the cancel control in the second display configuration bar 502 is referred to as a second cancel control.

[0213] Among them, the first confirmation control, the first cancel control, the second confirmation control and the second cancel control can be collectively referred to as the third control introduced above.

[0214] And reference Figure 5 It can also be understood that the second interface can also include a fourth control 505, and the text content "custom configuration policy" is also displayed in front of the fourth control to indicate that the function of the fourth control is that the user can define some configuration policies by himself, such as configuring the tag priority. Then, if an operation on the fourth control is detected, the first application can open the corresponding configuration file (such as the priority configuration file), and then the user enters data in the configuration file to implement the custom configuration policy.

[0215] Furthermore, the second interface may also include a fifth control 506, and the text content "View image backup information" is also displayed in front of the fifth control 506 to indicate that the function of the fifth control is to open the backup information record table for the user to view the backup information. Among them, because the backup information record table is an important basis for image backup, in order to prevent the user from modifying the backup information record table, the file permission of the backup information record table opened in response to the operation acting on the fifth control 506 can be set to read-only. Furthermore, in order to further improve the data security of the backup information record table, a copy of the backup information record table can also be generated, and then the copy of the backup information record table is opened in response to the operation acting on the fifth control 506, and the read-only permission can be set to ensure that the user has no opportunity to modify the backup information record table.

[0216] And, refer to Figure 5 In (b), the second interface may also include annotations to indicate the specific functions, operation methods, or functions of related files of each configuration column in the current second interface. For example, the annotations may include Figure 5 As shown in (b), "File 1 is used to configure the priority of the image tag, and File 2 is used to view the backup information of the image", wherein File 1 may be, for example, a priority configuration file, and File 2 may be, for example, a backup information record table. The specific text content in the annotation may be selected and set according to actual needs, and this embodiment does not impose any particular limitation on this.

[0217] Then refer to the above Figure 5 It can be understood from the introduction that in this embodiment, a first control is provided on the first interface to trigger the display of the second interface. The second interface includes multiple configuration bars for configuring specific image backup strategies and image display strategies during the image backup process, thereby meeting the user's diverse configuration requirements for image backup.

[0218] Specifically, the backup configuration bar is used to configure the image backup strategy, the display configuration bar is used to configure the image display strategy, and the custom configuration bar is used to obtain some custom content entered by the user. Therefore, the following is a further detailed introduction to the specific implementation of the backup configuration bar, the display configuration bar and the custom configuration bar in combination with the specific embodiments.

[0219] First combine Figures 6 to 11 Describes how to configure image backup strategies through the backup configuration bar. Figure 6 Operation diagram of the backup configuration bar provided in the embodiment of the present application Figure 1 , Fig. 7A The image label provided in the embodiment of the present application is shown in FIG. Figure 1 , Figure 7B The image label provided in the embodiment of the present application is shown in FIG. Figure 2 , Figure 8 A schematic diagram of the implementation of the backup information record table provided in the embodiment of the present application, Fig. 9 Operation diagram of the backup configuration bar provided in the embodiment of the present application Figure 2 , Fig.10 Operation diagram of the backup configuration bar provided in the embodiment of the present application Figure 3 , Fig.11 Operation diagram of the backup configuration bar provided in the embodiment of the present application Figure 4 .

[0220] Here we first analyze and explain the practical problems that need to be solved in the process of image backup. When performing image backup, there are three practical problems that need to be solved:

[0221] Question 1: Which target images need to be backed up? Question 2: To which folder should the target images be backed up (that is, which target folder is it?) Question 3: To what location in the target folder should the target images be backed up?

[0222] First, question one is explained. Based on the introduction of the above embodiment, it can be determined that the first interface includes multiple images, and the user can select the image to be backed up in the first interface. After that, when the first application performs image backing up, it actually further screens the images selected by the user according to the image backup strategy to determine the final target image.

[0223] When the user selects images in the first interface, the user may click on each image that he wants to back up individually, or may click on a "select all" control in the first interface to select all images in the first interface.

[0224] Alternatively, the user has neither clicked on any image individually nor selected an image through the select all control, that is, there is no image selected by the user, but the first application has detected a trigger operation for the image backup process. In this embodiment, it can be considered that the user has selected all images, and then all images are screened according to the image backup strategy to determine the target image, thereby effectively saving the user's screening operation. The trigger operation can be a click operation on the confirmation control in the second interface, or a click operation on the export control in the first interface, in short, an operation that indicates the start of the image backup process.

[0225] Secondly, for the second problem, a fixed incremental folder may exist in the first device for storing incremental images, wherein the incremental images are images that are not backed up in the incremental folder, that is, as long as an image has not been backed up in the incremental folder, even if it is backed up in other extended folders, it is still an incremental image. If the user indicates to back up only incremental images through the first backup configuration bar, the target image is always backed up in the incremental folder. In this case, the target folder is actually the incremental folder here.

[0226] However, if the user indicates to back up all selected images (not just incremental) through the first backup configuration bar, then in order to avoid the problem of image duplication in the incremental folder, you can choose to create a new extended folder for this backup process, and then back up the target images to the newly created extended folder. In this case, the target folder is actually the extended folder here.

[0227] Exemplarily, the name of the extended folder can be the preset field plus the backup date. For example, if the preset field is "New Backup" and the date of the current image backup is August 15, 2023, then the name of the newly created extended folder can be "New Backup-20230815" to effectively distinguish the newly created extended folders in the backup operations performed on different dates. By adding the backup date to the name of the extended folder, the speed and efficiency of users finding backup images can also be improved.

[0228] Furthermore, the user may perform multiple backup operations on the same day. Assuming that in these multiple backup operations, the user selects "Backup all selected images" multiple times through the first backup configuration bar, then there will be multiple backup requirements for backing up the target image to the extended folder on the same day.

[0229] In a possible implementation, an extended folder may be created separately for each backup process of backing up the target image to an extended folder. In order to distinguish the extended folders created in different backup processes, the name of the extended folder may be added with the hour, minute, and second information of the newly created extended folder on that day. For example, the user performed two image backup operations on August 15, 2023. If the user indicated "backup all selected images" multiple times through the first backup configuration bar in both image backup operations, the first image backup operation may be performed at 14:23:35 on August 15, 2023. For the first backup operation, a new extended folder "New Backup-20230815-142335" may be created. And assuming that the first image backup operation was performed at 15:05:46 on August 15, 2023, a new extended folder "New Backup-20230815-150546" may be created for the second backup operation.

[0230] Alternatively, the number of times the new extended folder was created on that day can be added to the name of the extended folder. For example, if the user performs three image backup operations on August 15, 2023, and if the user indicates "backup all selected images" multiple times through the first backup configuration bar in these three image backup operations, then a new extended folder "New Backup-20230815-1" can be created for the first backup operation, a new extended folder "New Backup-20230815-2" can be created for the second backup operation, and a new extended folder "New Backup-20230815-3" can be created for the third backup operation.

[0231] By adding the hour, minute, second information or the number of times the newly created extended folder is currently created to the name of the extended folder, on the one hand, the names of the newly created extended folders for multiple backups on the same day can be distinguished; on the other hand, the user can also use the hour, minute, second information or the number of times to quickly obtain the folder creation order among the multiple newly created extended folders on the same day, so that the user can efficiently identify the folders they need.

[0232] In the actual implementation process, the specific usage strategy of the extended folder can be selected and set according to actual needs. In addition, the specific expression of the preset fields, backup date, hour, minute, second information, creation times and other data included in the file name of the extended folder can also be set according to actual needs, as long as it can express the corresponding meaning.

[0233] Finally, let's explain question three. Regardless of whether the target folder is the incremental folder introduced above or the newly created extended folder during this backup process, the tag structure composed of the image tags of the target image is always consistent with at least part of the directory structure in the target folder (when processing the target folder, it will be processed according to the tag structure). So when storing the target image in the target folder, you need to consider in which specific directory in the target folder to store the target image.

[0234] When storing the target image, the target image will be preferentially stored in the directory corresponding to the lowest-level label it has, where the lowest-level label can be expressed as the t-th level label, and t is the maximum value of the label level in the image label of the target image.

[0235] For example, if the target image has an N-th level label, then the bottom-level label of the target image is also the N-th level label, so the target image can be stored in the directory corresponding to its N-th level label. When the N-th level label of the target image is empty, then the bottom-level label of the target image is also the N-1-th level label, so the target image can be stored in the directory corresponding to its N-1-th level label, and so on.

[0236] For the example of N=2 introduced above, assume that there are four first-level tags, namely "person", "thing", "place", and "date", and then depending on the actual situation of the current image, there are corresponding second-level tags under these four first-level tags. However, it is understandable that when the image is generated, the graphics APP that processes the image will definitely record the timestamp of the generated image, where the timestamp can also be regarded as an image identifier. Therefore, for any target image, there must be a second-level tag under the first-level tag of "time", so it can be guaranteed that the bottom-level tag of the target image must be a second-level tag, that is, the target image will be stored under the directory corresponding to its second-level tag.

[0237] Based on this, for a target image containing only a single bottom-level tag, the target image can be directly stored in the directory corresponding to the bottom-level tag. However, for a target image containing multiple bottom-level tags, it is necessary to determine how to back up according to the instructions in the second backup configuration column.

[0238] Exemplarily, if the operation instructions of the second backup configuration bar indicate that only a single backup is to be performed for a multi-label image, then the target image is only backed up to a directory corresponding to a certain bottom-level label (i.e., a single backup). If the operation instructions of the second backup configuration bar indicate that not only a single backup is to be performed for a multi-label image, then the target image needs to be backed up to a secondary directory corresponding to each bottom-level label contained therein (i.e., multiple backups are required). For the example of N=2 introduced above, the bottom-level label introduced here is the secondary label.

[0239] Based on the analysis here, it can be determined that in the process of backing up the target image, it is necessary to determine the specific image backup strategy according to the operation acting on the backup configuration bar, so as to realize backing up the target image to the corresponding directory in the target folder. Therefore, the example of N=2 introduced above is still used below to introduce in detail the various backup strategies generated by different operations acting on each backup configuration bar. The implementation method of N equal to other values ​​is similar, so it will not be repeated.

[0240] Exemplarily, the second interface may include the first backup configuration bar and the second backup configuration bar introduced above. There are two possible options in each of the two backup configuration bars. Then, the two possible options of the two backup configuration bars are combined to include 4 image backup strategies. These 4 image backup strategies are explained separately below with reference to specific diagrams.

[0241] Strategy 1: Back up only incremental images and perform only a single backup for images with multiple tags.

[0242] Can be combined Figure 6It is understood that the first backup configuration column 503 is used to configure whether to back up only the incremental image, which includes a first positive control and a first negative control, such as Figure 6 As shown, if the first affirmative control in the first backup configuration column 503 is selected, then in response to a fourth user operation acting on the first affirmative control, it can be determined that the image backup strategy includes only backing up images that are not backed up in the incremental folder (ie, incremental images).

[0243] And, the second backup configuration column 504 is used to configure whether to perform only a single backup for the multi-label image, which includes a second positive control and a second negative control, such as Figure 6 As shown, if the second affirmative control in the second backup configuration field 504 is selected, then in response to a fourth user operation on the second affirmative control, it can be determined that the image backup strategy includes only performing a single backup for images with multiple tags.

[0244] In this embodiment, the first application receives the user operation in the first backup configuration column and the second backup configuration column, which actually corresponds to the configuration process of the image backup policy performed by the user. After confirming that the policy configuration is completed, further triggering or confirmation can be performed. Exemplarily, the second interface includes a policy confirmation control, that is, Figure 6 The "Confirm" control shown in (a) in the figure.

[0245] Therefore, in response to the operation on the policy confirmation control, the image backup policy can be determined according to the control selection state of the backup configuration bar, so that the target image can be backed up according to the corresponding image tag to the target directory of the target folder of the first device according to the image backup policy.

[0246] Among them, the first affirmative control is selected to indicate that only the incremental image needs to be backed up. Therefore, in this embodiment, based on the user operation acting on the first affirmative control, the incremental image in the selected image that has not been backed up to the incremental folder can be determined as the target image, and the incremental folder introduced above can be used as the target folder to back up the target image to the target folder.

[0247] At the same time, the second affirmative control is selected, indicating that only a single backup is required for the multi-label image. Therefore, in this embodiment, the target image can be backed up to the target directory in the target folder (or the folder corresponding to the target directory) according to the user operation acting on the second affirmative control. The target directory in this embodiment can be the directory corresponding to the lowest-level label with the highest priority of the target image, where the lowest-level label can also be understood as the Wth-level label, where W is the level of the image label of the target image, and W is greater than or equal to 1.

[0248] For example, taking W=2 as an example, the target directory may be the secondary directory corresponding to the secondary tag with the highest priority among at least one secondary tag corresponding to the target image, or the target directory may be the secondary directory corresponding to any secondary tag corresponding to the target image.

[0249] Combined here Figure 6 The implementation of image backup under current strategy 1 is described with a specific example. Figure 6 As shown in (a), the first interface includes 8 images, namely, image 1 to image 8. Assuming that image 1, image 2, image 4 and image 8 are selected images, when determining the target image to be backed up, in fact, further screening is performed among the 4 selected images according to the image backup strategy.

[0250] Based on the above description, it can be determined that the backup location of the target image needs to be determined based on the label of the image, so the image labels of images 1 to 8 are first described below in conjunction with FIG. 7 .

[0251] For example, N=2 is still used as an example for explanation, that is, the levels of the label structure and the directory structure are both two-level, the label structure includes a first-level label and a second-level label, and the directory structure includes a first-level directory and a second-level directory. For the case where N is equal to other values, the implementation method is similar to the content described below, so it will not be repeated.

[0252] like Fig. 7A As shown, each image includes four first-level labels, namely "person", "thing", "place", and "date", while the second-level labels contained in the image under a specific first-level label are not fixed.

[0253] For example, the second-level label corresponding to image 1 under the first-level label "person" is "family", and the second-level label corresponding to the first-level label "date" is "Qingming Festival". There is no corresponding second-level label under the first-level labels "things" and "places". Therefore, it can be understood that image 1 is an image containing family generated during the Qingming Festival.

[0254] For another example, the secondary tag corresponding to image 2 under the primary tag "people" is "family", the secondary tag corresponding to the primary tag "place" is "province A", and the secondary tag corresponding to the primary tag "date" is "Qingming Festival", and there is no corresponding secondary tag under the primary tag "things", so it can be understood that image 2 is an image containing family members generated in province A during the Qingming Festival. The rest of the image tags are similar to those described above and will not be repeated here.

[0255] Reference Fig. 7AIt can be understood that the data structure of the label data can be represented by the data form of a table. In the table, the first-level label can be a column name, and the second-level label can be indicated by the value of the data row under the first-level label (that is, the column name). Specifically, when N=2, the value of the data row under the first-level label is directly the content of the second-level label. Fig. 7A The implementation of the table shown can achieve accurate and effective representation for a tag structure with 2 levels, but cannot achieve effective representation for a tag structure with more than 2 levels.

[0256] Next, combine Figure 7B When the number of levels of the tag structure is greater than 2 (i.e., N is greater than 2), the implementation method of the data structure representing the tag data is further introduced. It should also be noted that the implementation method currently introduced is also applicable to the case where N=2, but it can further implement the storage of tag data when N is greater than 2.

[0257] When N is greater than 2, it means that there are at least three levels of tags. In this case, a general table can be stored in the first application of the second device, and the image information of each image is stored in the general table. The image information at least includes basic information such as image identification and image date. On this basis, the content contained in the image information can also be expanded according to actual needs. Figure 7B In the example, the image information in the general table includes image ID, date and size. One type of image information is a column in the general table. The column name is the name of the image information. The specific value under the column name is the content of the specific image information of each image. In the actual implementation process, the specific content of the image information can be selected and expanded according to actual needs.

[0258] And optionally, the general table may also include a tag column corresponding to each first-level label. For example, the current first-level labels include "person", "thing", "place", and "time", then these four first-level labels correspond to a total of four tag columns in the general table, where the column name is the label content of the first-level label, and the value under the column name is used to indicate whether each image has the first-level label and its lower-level labels, where "true" indicates that the image has the first-level label and its lower-level labels, and "false" indicates that the image does not have the first-level label and its lower-level labels.

[0259] In one possible implementation, the column names of the table in the database are in English format, such as the image identification, date, size, and each first-level label introduced above, namely "person", "thing", "place", "time" and other column names, which can be their corresponding English words or English abbreviations in the general table.

[0260] In the general table, the tag column corresponding to the first-level label is optional, that is, the tag column corresponding to the first-level label may or may not exist in the general table. When it exists, by reading the tag column in the general table, it is possible to quickly determine whether the image has the corresponding first-level label and its lower-level label.

[0261] Based on the above introduction, it can be determined that the general table only provides some basic information of the image, and does not actually reflect the specific label information of the image. In the current implementation, a separate sub-table can be set for each first-level label to reflect the specific label status of each lower-level label under the first-level label of each image.

[0262] like Figure 7B As shown, assuming that there are currently four first-level tags of "person", "thing", "place" and "time", then correspondingly, there are four sub-tables, namely the person table, thing table, place table and date table, which respectively represent the specific label status of the lower-level tags of the image under these four first-level tags.

[0263] Each subtable includes a column for image identification, which is used to indicate which image each row in the table corresponds to. For any row in the table (i.e., for any image), the first column in the subtable other than the column corresponding to the image identification is used to indicate the second-level label under the first-level label corresponding to the current subtable, and the column name of the column is used to indicate the type of the second-level label, and the content under the column name is the specific second-level label of the current image; and, the second column in the subtable other than the column corresponding to the image identification is used to indicate the third-level label under the second-level label indicated by the previous column, and similarly, the column name of the column is used to indicate the type of the third-level label, and the content under the column name is the specific third-level label of the current image.

[0264] If you need to expand to level 4, level 5 or even more levels, you only need to add corresponding columns in the subtable. For any column, the column name is used to indicate the type of the current level label, and the value under the column name is the specific label content of the image corresponding to the current level label. Therefore, this implementation method can simply and efficiently realize the expansion and management of multi-level label structures while controlling the number of tables.

[0265] Combine the following Figure 7B Take the character table as an example to further explain the above content. Figure 7BAs shown, the character table includes columns corresponding to image identifications. The first column other than the image identifications is a "relationship" column, in which the "relationship" column is used to indicate the secondary labels corresponding to each image. The column name "relationship" is used to indicate that the secondary label indicated by the current column is used to indicate character relationships. The specific value under the column name "relationship" is the secondary label corresponding to each image.

[0266] For example, if the specific value of image 1 under the column name "Relationship" is "Family", then it can be determined that the second-level label of image 1 under the first-level label "People" is "Family".

[0267] In addition to the image identification, the second column is the "Specific Person" column, where the "Specific Person" column is used to indicate the third-level label corresponding to each image. The column name "Specific Person" is used to indicate which specific person the third-level label indicated by the current column is used to indicate. The specific value under the "Specific Person" column name is the third-level label corresponding to each image.

[0268] For example, if the specific value of image 1 under the column name "Specific Person" is "A", then it can be determined that the second-level label of image 1 under the first-level label "Person" is "Family Member", and the third-level label under the second-level label "Family Member" is "A".

[0269] The same is true for the other images in the character table. For example, for image 2, it can be determined that the second-level label of image 2 under the first-level label of "character" is "friend", and the third-level label under the second-level label of "friend" is "B". The other images are similar and will not be described here.

[0270] And reference Figure 7B It can also be understood that, because image 3 and image 4 do not have the first-level label "person" and its lower-level labels, the rows corresponding to image 3 and image 4 are not included in the person table, and by referring to the general table, it can be determined that the column value under the first-level label "person" corresponding to image 3 and image 4 is false, which is also used to indicate that image 3 and image 4 do not have the first-level label "person" and its lower-level labels.

[0271] Next, combine Figure 7B Taking the object table as an example for further explanation, referring to the object table, it can be analyzed and determined that the second-level label of image 3 under the first-level label of "object" is "scenery", and the third-level label under the second-level label of "scenery" is "sunset". The second-level label of image 4 under the first-level label of "object" is "food", and the third-level label under the second-level label of "food" is "white porridge". The remaining image situations are similar to the above-mentioned character table, and will not be further explained here.

[0272] as well as Figure 7B The analysis method of the location table and date table in is similar to the above description. It should also be noted that in the location table, because image 2 has the fourth-level label "α District", the location table contains the "District" column; however, images 3, 5, 6, and 7 do not have the fourth-level label under the first-level label "Location", so the values ​​corresponding to these rows under the "District" column are empty. Figure 7B The rest of the implementation of the location table and date table will not be repeated here.

[0273] It should also be emphasized that the sub-tables such as the person table, thing table, location table and date table also contain at least a column for image identification. In addition to the column for image identification, which columns are specifically included in each sub-table depends on the label generation of the graphic application in the second device.

[0274] exist Figure 7B The label structure of the comprehensive table and each sub-table can be referred to Figure 7B From the diagram on the right, we can see that under the first-level label "People", there are three second-level labels: "Family", "Friends", and "Colleagues". And under the second-level label "Family", there is a third-level label "A", and under the second-level label "Friends", there are two third-level labels "B" and "C", and under the second-level label "Colleagues", there is a third-level label "D".

[0275] Also, under the first-level label "things", there are two second-level labels "food" and "scenery". Also, under the second-level label "food", there are two third-level labels "porridge" and "steak", and under the second-level label "scenery", there is a third-level label "sunset".

[0276] And, under the first-level label "place", there are three second-level labels "Province A", "Province B", and "Province C". And under the second-level label "Province A", there are three third-level labels "City A1", "City A2", and "City A3", and under the second-level label "Province B", there is a third-level label "City B1", and under the second-level label "Province C", there is a third-level label "City C1". And under the third-level label "City A1", there is a fourth-level label "District α".

[0277] Also, under the first-level label "Date", there are two second-level labels "Tomb-Sweeping Day" and "Labor Day Holiday". Also, under the second-level label "Tomb-Sweeping Day", there is a third-level label "20230405", and under the second-level label "Labor Day Holiday", there are three third-level labels "20230501", "20230502" and "20230503".

[0278] The above combination Figure 7B The embodiment introduces a method for implementing the first application in the second device to store the label data of the image when N is greater than 2. Based on the above introduction, it can be determined that the image identifier is included in both the general table and the sub-tables. Then, the first application in the first device can connect the general table and the sub-tables introduced above based on the image identifier through multi-table query to obtain a complete table. Then, the label data of each target image can be determined based on this complete table.

[0279] Next, let's explain the tag column in the general table. For example, if the value of the tag column corresponding to the first-level label "person" for a certain image is "false", it means that the image does not have the first-level label "person" and its lower-level labels. In this case, there is no need to query the sub-table corresponding to the first-level label "person" for this image, thereby saving data processing.

[0280] It needs to be emphasized again that Figure 7B The specific labeling conditions of the labels at each level of the image shown in the example (whether there is a certain level of label and what the specific label content is) depend on the specific labeling conditions of the graphics application in the second device in actual implementation. The first device in this embodiment is only responsible for reading from the second device and is not responsible for generating labels.

[0281] Furthermore, when screening target images, it is necessary to determine whether the images are backed up in the incremental folder. In a possible implementation, the first application can maintain a backup information record table based on the backup results of the images to record the specific backup status of each image.

[0282] like Figure 8 As shown, the backup information record table includes the image name of each backed up image, the last backup result, the number of global backup successes, the number of backups corresponding to the incremental folder, the storage path in the second device, the backup path in the first device, and the backup date.

[0283] The image name is used to identify the image. When determining whether the image has been backed up, the backup information record table can be queried according to the image name to determine whether the corresponding image has been backed up. Alternatively, the image name can also be replaced with an image identifier, which can be, for example, a hash value of the image, a personalized identifier generated for the image, etc. This embodiment does not impose any special restrictions on the specific identifier content used to indicate the image in the backup information record table.

[0284] The last backup result is used to indicate whether the last backup of the image is successful, and the backup information record table also includes the last backup folder. The backup folder can be a "backup" folder as an incremental folder, or a "new backup-xx" folder as an extended folder, where xx is the backup date, hour, minute, second, etc. If the last backup result indicates that the last image backup is unsuccessful, the user can check the backup information record table to determine the folder location of the last backup of the image, thereby checking the specific backup situation.

[0285] And, the backup count is used to indicate how many times the image has been backed up. The backup count can be the total number of image backups, that is, whether a backup of an image is successful or not, the backup count will be increased by one. For example, if an image is backed up 4 times in total, even if only 3 of them are successful, the backup count is still recorded as 4. Alternatively, only the number of successful backups can be recorded. For example, if an image is backed up 4 times in total, only 3 of them are successful, then the backup count can be recorded as 3.

[0286] In the backup information record table of this embodiment, two types of backup times can be maintained. One is the global backup success times, which is used to indicate the total backup times of the image. Whether the image is backed up to the incremental folder or the extended folder, it will be recorded in the global backup success times. The other is the backup times corresponding to the incremental folder, which is used to indicate the backup times of the image in the incremental folder. That is to say, only when the image is backed up to the incremental folder, the backup times corresponding to the incremental folder will be increased by 1.

[0287] Because the incremental folder actually exists as the main folder for image backup, it is necessary to ensure that the images backed up in the incremental folder are as complete as possible. For example, for an image A, if the user chooses to back up image A to the extended folder through policy configuration during a backup process, and image A has not been backed up to the incremental folder, then image A is actually still an incremental image that has not been backed up to the incremental folder.

[0288] If the user backs up the image again later and selects "incremental backup" through policy configuration, in this case, because image A has not been backed up to the incremental folder, image A can be backed up to the incremental folder as an incremental image. Therefore, by maintaining the backup times corresponding to the incremental folder in the backup information record table, it is possible to quickly determine whether the image has been backed up to the incremental folder.

[0289] Furthermore, the storage path in the second device is used to indicate the storage location of the image in the second device, and the backup path in the first device is used to indicate the backup location of the image in the first device, so that the user can quickly search for the image in the second device and the first device. The backup date is the date when the image was last backed up.

[0290] This embodiment does not limit the actual meaning of each data in the backup information record table, which can be expanded according to actual needs, and the specific content included in the backup information record table can also be expanded according to actual needs.

[0291] The backup information record table in the first device is used to store the backup information of each image, but it is understandable that after the image backup is completed, the user may delete the backed-up images in the first device, or directly delete certain folders, and then the data in the corresponding backup information record table needs to be updated. In a possible implementation, when the first application in the first device is started, the first application can obtain the backup status of each image in the backup information record table, and then update the backup information record table to ensure that the detailed information recorded in the backup information record table is consistent with the actual backup status of the image.

[0292] Back to Figure 6 In the example, image 1, image 2, image 4 and image 8 are selected images. Since the current backup strategy is to only back up incremental images that are not backed up to the incremental folder, it is necessary to determine the images that are not backed up to the incremental folder among the selected images as target images. Figure 8 It can be determined that among the selected images, image 1, image 2 and image 4 are all images that have been backed up to the incremental folder, so among the selected images, only image 8 remains that has not been backed up to the incremental folder, so image 8 is determined as the target image that needs to be backed up.

[0293] And, because the current image backup strategy is to back up only incremental images, the incremental folder can be determined as the target folder, for example, the "backup" folder (that is, the incremental folder) located in the C drive of the first device is the target folder. Figure 6 It can be determined from (b) that image 8 is stored in the "backup" folder.

[0294] At the same time, combined Fig. 7AIt can be determined that image 8 contains two secondary tags (also the bottom-level tags) of "colleagues" and "Labor Day holiday", so image 8 is a multi-tagged image. The image backup strategy in the current embodiment is to perform only a single backup for multi-tagged images. Assuming that the priority of the secondary tag "colleagues" is higher than the priority of the secondary tag "Labor Day holiday", the secondary tag "colleagues" can be corresponding to the secondary directory in the "backup" folder, determined as the target directory, and then image 8 can be backed up to the target directory.

[0295] like Figure 6 As shown in (b), the tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the incremental folder (the figure shows a completely consistent situation, and in fact the directory structure of the incremental folder can contain more content). Under the first-level directory "People" in the "Backup" folder, there is a second-level directory "Colleagues", which is the directory corresponding to the second-level tag "Colleagues". Therefore, image 8 is backed up in the file path "C Drive / Backup / People / Colleagues".

[0296] It should also be noted that, because the image backup strategy in the current embodiment is to perform only a single backup of multi-label images, then for another secondary label "Labor Day Holiday" of image 8, its corresponding secondary directory is the secondary directory "Labor Day Holiday" under the first-level directory "Date" in the "Backup" folder, and there is no backup of image 8 therein, thereby achieving a single backup of multi-label images.

[0297] For example, Figure 8 For the image 5 shown in the example, the number of global successful backups is 2, and the number of backups corresponding to the incremental folder is 0, which means that image 5 has been backed up twice, but has never been backed up in the incremental folder. Therefore, image 5 is actually an incremental image that has not been backed up to the incremental folder. If the user selects image 5, then image backup is also required for image 5.

[0298] In a possible implementation, the operation on the policy confirmation control may directly trigger the execution of the image backup process. Alternatively, the operation on the policy confirmation control is only used to trigger the generation of the backup policy, and then the user needs to further click the "Export" control in the first interface before the application can respond to the operation on the export control and back up the target image to the target folder according to the image backup policy indicated by the selected state of the backup configuration bar. In the actual implementation process, the specific method used to trigger the execution of the image backup process can be selected and set according to actual needs.

[0299] The following is an introduction to Strategy 2:

[0300] Strategy 2: Back up only incremental images and perform multiple backups for images with multiple tags.

[0301] Can be combined Fig. 9 It is understood that the first backup configuration column 503 is used to configure whether to back up only the incremental image, which includes a first positive control and a first negative control, such as Fig. 9 As shown, if the first affirmative control in the first backup configuration column 503 is selected, then in response to a fourth user operation acting on the first affirmative control, it can be determined that the image backup strategy includes only backing up images that are not backed up in the incremental folder (ie, incremental images).

[0302] And, the second backup configuration column 504 is used to configure whether to perform only a single backup for the multi-label image, which includes a second positive control and a second negative control, such as Fig. 9 As shown, if the second negative control in the second backup configuration field 504 is selected, then in response to a fourth user operation acting on the second negative control, it can be determined that the image backup strategy includes multiple backups for images with multiple tags.

[0303] Similar to the above, you can respond to the policy confirmation control ( Fig. 9 The image backup strategy is determined according to the control selection state of the backup configuration bar, so that the target image is backed up according to the corresponding image tag to the target directory of the target folder of the first device according to the image backup strategy.

[0304] Among them, the first affirmative control is selected to indicate that only the incremental image needs to be backed up. Therefore, in this embodiment, based on the user operation acting on the first affirmative control, the incremental image in the selected image that has not been backed up to the incremental folder can be determined as the target image, and the incremental folder introduced above can be used as the target folder to back up the target image to the target folder.

[0305] At the same time, the selection of the second negative control indicates that the multi-label image needs to be backed up multiple times. Therefore, in this embodiment, the multi-label target image can be repeatedly backed up to the target directory in the target folder (or the folder corresponding to the target directory) according to the user operation acting on the second negative control. The target directory in this embodiment can be the directory corresponding to at least one bottom-level label of the target image. Here, "at least one bottom-level label" refers to all the bottom-level labels possessed by the target image. The reason why it is said is at least one because the target image may only include one bottom-level label. Therefore, in the current case, the target directory can also be directly understood as the directory corresponding to all the bottom-level labels of the target image.

[0306] Exemplarily, taking W=2 as an example, the target directory may be a secondary directory corresponding to the secondary tag of the target image. There are several target directories corresponding to the several secondary tags corresponding to the target image.

[0307] Combined here Fig. 9 The implementation of image backup under current strategy 2 is described with a specific example. Fig. 9 As shown in (a), the first interface includes 8 images, namely image 1 to image 8. The labeling and backup status of images 1 to image 8 follow the above examples and will not be repeated here.

[0308] Assume that images 1, 2, 4, and 8 are selected images, and because the current backup strategy is to back up only incremental images, similar to the above situation, only image 8 is left among the selected images, which is an incremental image that has not been backed up to the incremental folder, so image 8 is determined as the target image to be backed up. And the incremental folder is determined as the target folder, for example, the "Backup" folder in the C drive of the first device is the target folder. Then refer to Fig. 9 It can be determined from (b) that image 8 is stored in the "backup" folder.

[0309] At the same time, image 8 contains two secondary tags (also the bottom-level tags) of "colleagues" and "May Day holiday", so image 8 is a multi-tag image. The image backup strategy in the current embodiment is to perform multiple backups for multi-tag images. Then, image 8 needs to be backed up in the secondary directories corresponding to the two secondary tags of image 8.

[0310] like Fig. 9 As shown in (b), the tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the target folder (the figure shows a completely consistent situation, and in fact the directory structure of the incremental folder can contain more content). Under the first-level directory "People" in the "Backup" folder, there is a second-level directory "Colleagues", which is the directory corresponding to the second-level tag "Colleagues". Therefore, image 8 is backed up in the file path "C Drive / Backup / People / Colleagues".

[0311] In addition, under the first-level directory "Date" in the "Backup" folder, there is a second-level directory "Labor Day Holiday". The second-level directory "Labor Day Holiday" is the directory corresponding to the second-level label "Labor Day Holiday". Therefore, image 8 is backed up under the file path "C Drive / Backup / Date / Labor Day Holiday", thereby realizing multiple backups for multi-label images.

[0312] The following is an introduction to Strategy 3:

[0313] Strategy 3: Back up all selected images and perform a single backup for multi-tagged images.

[0314] Can be combined Fig.10 It is understood that the first backup configuration column 503 is used to configure whether to back up only the incremental image, which includes a first positive control and a first negative control, such as Fig.10 As shown, if the first negative control in the first backup configuration column 503 is selected, then in response to a fourth user operation acting on the first negative control, it can be determined that the image backup strategy includes backing up all selected images (ie, full images).

[0315] And, the second backup configuration column 504 is used to configure whether to perform only a single backup for the multi-label image, which includes a second positive control and a second negative control, such as Fig.10 As shown, if the second affirmative control in the second backup configuration field 504 is selected, then in response to a fourth user operation on the second affirmative control, it can be determined that the image backup strategy includes only performing a single backup for images with multiple tags.

[0316] Similar to the above, you can respond to the policy confirmation control ( Fig.10 The operation of the confirmation control in (a) in the backup configuration bar is performed to determine the image backup strategy according to the control selection state in the backup configuration bar, so as to back up the target image according to the corresponding image tag to the target directory in the target folder of the first device according to the image backup strategy.

[0317] Among them, the first negative control is selected, indicating that all selected images are to be backed up, so the selected image in the image is directly determined as the target image. Also, in order to avoid the problem of duplicate backup of images in the incremental folder, a new extended folder needs to be created when backing up the target image, because the extended folder is newly created according to the tag structure of the target image, so the tag structure composed of the image tags of the target image is completely consistent with the directory structure in the extended folder, and then the extended folder is used as the target folder to realize the backup of the target image. Therefore, in this embodiment, a new extended folder can be created according to the user operation acting on the first negative control, and then the target image can be backed up to the target folder (i.e., the extended folder) according to the corresponding image tag.

[0318] And, the second affirmative control is selected, indicating that only a single backup is required for the multi-label image, so in this embodiment, the target image can be backed up to the target directory in the target folder according to the user operation acting on the second affirmative control. The implementation method is similar to that in the above strategy 1, and will not be repeated here.

[0319] Combined here Fig.10The implementation of image backup under the current strategy 3 is described with a specific example. Fig.10 As shown in (a), the first interface includes 8 images, namely image 1 to image 8. The labeling and backup status of images 1 to image 8 follow the above examples and will not be repeated here.

[0320] Assume that image 1 and image 8 are selected images, because the current backup strategy is to back up all selected images, so image 1 and image 8 will be determined as target images. Fig.10 , assuming that a new Fig.10 The expanded folder "New Backup-20230815-150546" shown in (b) in the figure can be used as the target folder to store the image 8 in the folder "New Backup-20230815-150546". The file name of the expanded folder includes the preset field "New Backup", the backup date "20230815", and the hour, minute, and second information "150546", so that the user can easily check the backup image.

[0321] At the same time, image 8 contains two secondary tags, "colleagues" and "Labor Day holiday", so image 8 is a multi-label image. The image backup strategy in the current embodiment is to perform only a single backup for multi-label images. Assuming that the priority of the tag "colleagues" is higher than the priority of the tag "Labor Day holiday", the tag "colleagues" can be corresponding to the secondary directory in the "backup" folder, determined as the target directory, and then image 8 is backed up to the target directory.

[0322] Similar to the one introduced in Strategy 1, Fig.10 As shown in (b), image 8 is backed up in the file path "C Drive / New Backup-20230815-150546 / People / Colleagues", but there is no backup image 8 in "C Drive / New Backup-20230815-150546 / Date / Labor Day Holiday".

[0323] Furthermore, image 1 contains two secondary tags, "family" and "Qingming Festival", so image 1 is also a multi-tagged image. The image backup strategy in the current embodiment is to perform only a single backup for multi-tagged images. Assuming that the priority of the tag "family" is higher than the priority of the tag "Qingming Festival", the tag "family" can be corresponding to the secondary directory in the "backup" folder, determined as the target directory, and then image 1 can be backed up to the target directory.

[0324] Similar, such as Fig.10As shown in (b), image 1 is backed up in the file path "C drive / New backup-20230815-150546 / People / Family", while image 1 is not backed up in "C drive / New backup-20230815-150546 / Date / Qingming", thereby achieving a single backup for multi-label images.

[0325] The following is an introduction to Strategy 4:

[0326] Strategy 4: Back up all selected images and perform multiple backups for multi-label images.

[0327] Can be combined Fig.11 It is understood that the first backup configuration column 503 is used to configure whether to back up only the incremental image, which includes a first positive control and a first negative control, such as Fig.11 As shown, if the first negative control in the first backup configuration column 503 is selected, then in response to a fourth user operation acting on the first negative control, it can be determined that the image backup strategy includes backing up all selected images (ie, full images).

[0328] And, the second backup configuration column 504 is used to configure whether to perform only a single backup for the multi-label image, which includes a second positive control and a second negative control, such as Fig.11 As shown, if the second negative control in the second backup configuration field 504 is selected, then in response to a fourth user operation acting on the second negative control, it can be determined that the image backup strategy includes multiple backups for images with multiple tags.

[0329] Similar to the above, you can respond to the policy confirmation control ( Fig.11 The image backup strategy is determined according to the control selection state of the backup configuration bar, so that the target image is backed up according to the corresponding image tag to the target directory of the target folder of the first device according to the image backup strategy.

[0330] The first negative control is selected, indicating that all selected images are to be backed up, so the selected images in the image are directly determined as the target image. The implementation method is similar to that in the above strategy 3, and will not be repeated here.

[0331] And, the second negative control is selected to indicate that the multi-label image needs to be backed up multiple times, so in this embodiment, the multi-label target image needs to be repeatedly backed up to the target directory in the target folder. The implementation method is similar to that in the above strategy 2, and will not be repeated here.

[0332] Combined here Fig.11 The implementation of image backup under current strategy 4 is described with a specific example. Fig.11 As shown in (a), the first interface includes 8 images, namely image 1 to image 8. The labeling and backup status of images 1 to image 8 follow the above examples and will not be repeated here.

[0333] Assume that image 1 and image 8 are selected images, because the current backup strategy is to back up all selected images, so image 1 and image 8 will be determined as target images. Fig.11 , assuming that a new Fig.11 The expanded folder of “New Backup-20230815-150546” shown in (b) in the figure, so the folder of “New Backup-20230815-150546” can be used as the target folder to store image 8 in the folder of “New Backup-20230815-150546”.

[0334] At the same time, image 8 contains two secondary tags, "colleagues" and "May Day holiday", so image 8 is a multi-label image. The image backup strategy in the current embodiment is to perform multiple backups for multi-label images. Then, image 8 needs to be backed up in the secondary directories corresponding to the two secondary tags of image 8.

[0335] like Fig.11 As shown in (b), image 8 is backed up in the file path "C drive / new backup-20230815-150546 / characters / colleagues", and image 8 is also backed up in the file path "C drive / new backup-20230815-150546 / date / Labor Day holiday".

[0336] Furthermore, image 1 contains two secondary tags, "family" and "Qingming Festival", so image 1 is a multi-tagged image. The image backup strategy in the current embodiment is to perform multiple backups for multi-tagged images. Then, image 1 needs to be backed up in the secondary directories corresponding to the two secondary tags of image 1.

[0337] like Fig.11 As shown in (b), image 1 is backed up in the file path "C drive / new backup-20230815-150546 / people / family", and image 1 is also backed up in the file path "C drive / new backup-20230815-150546 / date / Qingming", thereby realizing multiple backups for multi-label images.

[0338] In this embodiment, by selecting the corresponding control in the first backup configuration bar to indicate whether only incremental images are to be backed up, and selecting the corresponding control in the second backup configuration bar to indicate whether only a single backup is to be performed for multi-label images, and then responding to the operation on the policy confirmation control, the image backup policy is determined according to the control selection state of the backup configuration bar, so that the target image is stored in the target folder of the first device according to the corresponding image tag, thereby effectively providing the function of configuring only incremental images and the function of performing a single backup for multi-label images. Users can configure the corresponding functions according to actual image backup requirements, thereby improving the flexibility and functional completeness of image backup, and effectively reducing repeated backup of photos, further speeding up the backup speed.

[0339] The above introduction introduces the operation in the backup configuration bar in the second interface, so as to implement image backup according to the corresponding image backup strategy. However, the above introduction focuses on interface operation. Fig.12 Further details on the internal implementation of image backup devices are provided. Fig.12 An interactive flowchart of image backup processing provided in an embodiment of the present application.

[0340] like Fig.12 As shown, the method comprises the following steps:

[0341] 1. A first application in a first device receives an operation on a second interface.

[0342] A first application is installed in the first device. In the second interface of the first application, the user can perform the above-described operations on the backup configuration bar and the policy confirmation control.

[0343] 2. The first application in the first device sends a data query command to the first application in the second device.

[0344] The first application is also installed in the second device, and the second device and the first application in the first device can perform data interaction to achieve image backup.

[0345] Exemplarily, if the first application detects an operation on the policy confirmation control, it can be confirmed that the user has completed and confirmed the image backup policy. At this time, in response to the operation on the policy confirmation control, a data query command can be sent to the first application in the second device.

[0346] The data query command is used to instruct to query the image information of each target image in the second device. The image information may include the image tag of the target image and the image storage path in the second device. The specific content contained in the image information may also be selected according to actual needs.

[0347] 3. The first application in the second device queries the image information of each target image according to the data query command.

[0348] 4. The first application in the second device sends the image information of the queried target image to the first application in the first device.

[0349] 5. The first application in the first device creates an extended folder or updates an incremental folder according to the image tag of the target image, and backs up the target image to the target folder according to the image information.

[0350] After acquiring the image information of the target image, the first application in the first device may create an extended folder or update an incremental folder according to the image tag in the image information.

[0351] If an extended folder is created, then at the moment the image backup is completed, the tag structure composed of the image tags of the target image is completely consistent with the directory structure in the extended folder. If an incremental folder is updated, then at the moment the image backup is completed, the tag structure composed of the image tags of the target image is either consistent with part of the directory structure in the incremental folder, or completely consistent with the directory structure in the incremental folder, depending on the specific directory situation in the incremental folder, which can be understood by referring to the analogy between set S2` and set A introduced above.

[0352] When processing the target folder according to the image tag, whether to create an extended folder or update an incremental folder depends on the operation on the first backup configuration bar in the second interface.

[0353] Based on the above introduction, it can be determined that if the first affirmative control in the first backup configuration bar is selected in the second interface, it means that only the unbacked up images need to be backed up currently, so the incremental folder can be determined as the target folder and the incremental folder can be updated.

[0354] In this embodiment, the label structure composed of the image labels of the target image needs to be consistent with at least part of the directory structure in the incremental folder, where there is an existing directory structure in the incremental folder itself (which is continuously generated during the previous image backup process). Therefore, in this embodiment, it is necessary to update the directory structure in the incremental folder according to the label structure of the current target image so that the label structure of the current target image corresponds to the directory structure of the incremental folder.

[0355] When updating the incremental folder, multiple target images can be processed in sequence. For any image label in any target image, if there is a corresponding directory in the incremental folder, there is no need to create it again; if there is no corresponding directory in the incremental folder, it is necessary to create a corresponding directory according to the hierarchical position of the label (specifically, which level of label it is and under which label it belongs).

[0356] After completing the above-mentioned processing for each image tag of the target image, the backup processing of the target image can be directly performed. That is to say, when processing each target image, on the one hand, the directory corresponding to the image tag of the target image will be updated, and on the other hand, the backup processing of the target image will be directly performed.

[0357] The target image can be backed up to the target folder according to the image information, wherein the image information may include an image tag and a storage path of the image in the second device. Based on the image tag, it can be determined in which directories in the target folder the target image is specifically stored, and based on the storage path, the storage location of the target image can be accessed, thereby copying the image from the corresponding storage location to achieve image backup.

[0358] And if a certain image tag is deleted in the second device, but the corresponding directory still exists in the target folder of the first device, no processing is required. That is to say, the directory structure of the incremental folder may contain the corresponding part of the tag that is not in the tag structure of the target image.

[0359] The above introduces the implementation of updating the incremental folder. Alternatively, if in the second interface, the first negative control in the first backup configuration bar is selected, it means that the selected full image needs to be backed up at present. Therefore, a new extended folder can be created and the extended folder can be determined as the target folder. The tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the extended folder.

[0360] Among them, the extended folder is empty initially, so the directory structure in the extended folder is completely generated according to the label structure of the target image, so the label structure composed of the image labels of the target image is completely consistent with the directory structure in the extended folder.

[0361] When creating a new extended folder at one time, multiple target images can also be processed in sequence. Among them, the image labels of multiple target images may be repeated. For a label 1 of the target image that is backed up first, assuming that the corresponding directory has been generated, then if the target image that is backed up later also contains the label 1, there is no need to repeatedly generate the directory corresponding to the label 1.

[0362] Therefore, similar to the above description, for any image tag in any target image, first determine whether the image tag has a corresponding directory in the extended folder. If the directory corresponding to the image tag already exists in the extended folder, there is no need to generate the directory corresponding to the image tag. If the directory corresponding to the image tag does not exist in the extended folder, the corresponding directory is generated according to the hierarchical position of the current image tag.

[0363] After the above-described processing is completed for each image tag of the target image, the backup processing of the target image can be directly performed. The implementation method of image backup is also similar to the above-described method and will not be repeated here. Based on this process, after the processing of each target image is completed, an expanded folder with a directory structure consistent with the tag structure composed of the image tags of the target image can be obtained.

[0364] Based on the introduction of the current embodiment, it can be determined that in this embodiment, when backing up the target image, the target image is read, the target folder is processed, and the target image is backed up at the same time. That is to say, for each target image read, the image backup of this target image will be completed as soon as possible, rather than starting the backup process after all target images are read. This processing method in this embodiment can ensure that the image backup is completed as soon as possible for the read images, avoiding the feeling that the image backup takes too long at the user experience level. At the same time, this implementation method can ensure that when an exception occurs, at least the images that have been read before the exception occurs can be backed up to improve the stability of the image backup.

[0365] 6. Maintain the backup information record table.

[0366] After the target images are backed up, the backup information record table may be maintained according to the specific backup conditions of the backed up target images, so that the backup information record table may reflect the latest image backup conditions.

[0367] The above describes the implementation of the image backup strategy. The second interface also includes at least one display configuration bar. In this application, the image displayed in the first interface can be updated in response to the operation on the display configuration bar. Figure 13 to Figure 14 The implementation of the image display strategy is explained. Fig.13 Schematic diagram of updating the first interface provided in the embodiment of the present application Figure 1 , Fig.14 Schematic diagram of updating the first interface provided in the embodiment of the present application Figure 2 .

[0368] like Fig.13As shown in (a) of FIG. 1 , it is assumed that the first interface includes eight images, image 1 to image 8, and the image labels of each image follow the above Fig. 7A In the initial first interface, images with creation dates belonging to the time period can be displayed under each time period according to the divided time periods. For example, under the time period of April 1 to April 5, 2023, images 4, 5, 6, and 9 are displayed.

[0369] In this embodiment, the first display configuration bar 501 is used to configure whether the images in the first interface are displayed according to the image tags. If the user operates the first determination control in the first display configuration bar 501, the first application can respond to the seventh user operation on the first determination control and update the first interface. The updated first interface displays each image according to the image tag of the image.

[0370] Here is a further introduction to images. When images need to be displayed in the first interface for the user to view, the first application in the first device will first obtain part of the images from the second device and cache the obtained part of the images. Initially, part of these cached images will be displayed in the first interface. Then, in response to the user's browsing operation on the first interface (such as swiping up or down in the interface), more images will be further obtained from the cached images to update the first interface. As the user continues to browse, the first device will continue to obtain more images from the second device to expand the cached images.

[0371] Therefore, the image will be cached in the first device, so that when displaying the image, data can be directly obtained from the cache in the first device for display, avoiding frequent interactions between the second device and the first device, and at the same time improving the processing speed of image display.

[0372] The image is cached in the first device only for the convenience of displaying the first interface, but in addition to being cached in the first device, the image is still stored in the second device. When backing up the image, the image is still obtained from the specific file path in the second device and backed up to the first device. Or it can be understood that what is cached in the first device is only a copy or thumbnail of the image, and the real image is still stored in the second device.

[0373] When images are displayed according to their image tags, for example, a tag structure may be constructed according to the image tags of the respective images, and then the images are displayed according to the constructed tag structure.

[0374] Specifically, multiple i-level labels can be displayed in sequence in the first interface according to the constructed label structure, and the corresponding i+1-th level labels can be displayed under each i-th level label, and the images contained in the current interface can be displayed under the corresponding bottom-level labels, where the value range of i is 1 to N.

[0375] Take the case of N=2 as an example. Fig.13 As shown in (b), in the updated first interface, at least one first-level label of the image label of the image is displayed in sequence, and the corresponding second-level labels are displayed under each first-level label. Furthermore, the image is specifically displayed under the second-level label, and the image displayed under the second-level label is the image with the second-level label.

[0376] Recombination Fig.13 The detailed contents in (b) are explained. In the first interface, the first-level label "Person" and the first-level label "Place" are displayed. Due to the size of the interface, the remaining first-level labels are not displayed. The implementation method is similar.

[0377] For the first-level label "People", the corresponding second-level labels "Family" and "Colleagues" are displayed below. Due to the size of the interface, the remaining second-level labels under the first-level label "People" are not shown. Taking the second-level label "Family" as an example, the images 1 and 7 containing the second-level label "Family" are displayed below it. Taking the second-level label "Colleagues" as an example, the images 6 and 8 containing the second-level label "Colleagues" are displayed below it.

[0378] The display method of the secondary labels under the primary label "Place" and the images under them is similar and will not be repeated here.

[0379] And reference Fig.13 It can also be understood that in (b), in the first interface, a selection control (rectangular box in the figure) is displayed in front of each first-level label and second-level label, so the first application can respond to the user's operation on the selection control in front of a certain label, thereby selecting all images under the label.

[0380] At the same time, the image may contain multiple secondary tags (that is, the bottom-level tags). For images with multiple tags, the image can be displayed only below a certain secondary tag to avoid the problem of repeated display of images with multiple tags. The secondary tag of the image displayed below can be the secondary tag with the highest priority among the multiple secondary tags of the image, or the secondary tag that is ranked the highest according to the target sorting method. The target sorting method is, for example, sorting according to the first letter of the first word of the secondary tag, or any possible sorting method, which is not limited in this embodiment.

[0381] For example, you can combine Fig.13 (b) in the figure is used for explanation, where image 7 includes three secondary tags, namely "Family", "Province A" and "May Day Holiday". Assuming that the priority of the secondary tag "Family" is higher than that of the secondary tag "Province A" and higher than that of the secondary tag "May Day Holiday", image 7 is only displayed below the secondary tag "Family", and image 7 will not be repeatedly displayed below the secondary tag "Province A" and below the secondary tag "May Day Holiday" to avoid the problem of user selection confusion caused by repeated display of images.

[0382] In some special cases, if the secondary labels of some images are all empty, that is, these images have no corresponding secondary labels, for these images, you can follow Fig.13 As shown in (a), the image is displayed in a divided time period manner, and the image displayed in a divided time period manner can be displayed at the bottom of the first interface, that is, below the image displayed according to the image label, the image displayed in a divided time period manner is displayed.

[0383] And in the present embodiment, the second display configuration bar 502 is used to configure whether only incremental images in the image are displayed in the first interface. If the user operates the second determination control in the second display configuration bar 502, the first application can update the first interface in response to the seventh user operation acting on the second determination control. The updated first interface only displays the incremental images in the image, where the incremental images refer to images that have not been backed up to the incremental folder. Therefore, "only displaying incremental images in the image" means that only displaying images that have not been backed up to the incremental folder.

[0384] exist Fig.13 In (b), the images displayed in the first interface actually still include images 1 to 8 (not all of which are shown), which are displayed according to the image tags of the images, and refer to Figure 8It can be determined that images 1 to 4 are all images that have been backed up to the incremental folder, so in response to the operation acting on the second determination control, the first interface is updated, and the updated first interface is as follows Fig.13 As shown in (c), only the images that have not been backed up to the incremental folder are displayed, namely, images 5 to 8 (due to the size of the interface, image 5 displayed under the secondary label "Friends" is not shown), and the display is still maintained according to the label structure.

[0385] The above combination Fig.13 The following describes the operations on the first confirmation control and the second confirmation control. The user can also operate the first cancellation control and the second cancellation control to trigger the graphical user interface to be updated accordingly. Fig.14 Provide explanation.

[0386] like Fig.14 As shown in (a) of FIG. 1 , it is assumed that the first interface includes eight images, image 1 to image 8, and the image labels of each image follow the above Fig. 7A .

[0387] Reference Fig.14 It can be determined from (a) that images are currently displayed according to their image tags, and only images that have not been backed up are displayed.

[0388] In this embodiment, the first display configuration bar 501 is used to configure whether the images in the first interface are displayed according to the image tags of the images. If the user operates the first cancel control in the first display configuration bar 501, the first application can respond to the seventh user operation on the first cancel control and update the first interface. The updated first interface cancels the display of each image according to the image tags of the images and instead restores the display of each image in a divided time period manner, that is, multiple images are displayed according to the generation time period to which each image belongs.

[0389] like Fig.14 As shown in (b), in the updated first interface, according to the multiple generation time periods, the images with the creation date belonging to the generation time period are displayed under each generation time period. At the same time, the incremental images in the displayed images are still kept, for example, under the period of April 1 to April 5, 2023, images 5, 6, and 8 that have not been backed up to the incremental folder are displayed, and under the period of May 1 to May 5, 2023, image 7 that has not been backed up to the incremental folder is displayed.

[0390] And in the present embodiment, the second display configuration bar 502 is used to configure whether only the incremental image in the image is displayed in the first interface. If the user operates the second cancel control in the second display configuration bar 502, the first application can respond to the seventh user operation on the second cancel control and update the first interface, and all images are displayed in the updated first interface.

[0391] The first interface after the update is as follows Fig.14 As shown in (c) in FIG. 1 , all images 1 to 8 are displayed, and the display is still maintained in the manner of dividing the time periods.

[0392] In this embodiment, by selecting the corresponding control in the first display configuration bar to indicate whether to display the image according to the image tag of the image, and selecting the corresponding control in the second display configuration bar to indicate whether to display only the incremental images in the image, the user can be provided with the function of configuring the display method of the image to enhance the flexibility and diversity of the displayed images. At the same time, by displaying the images according to the tag structure and only displaying the images that have not been backed up to the incremental folder, the workload of the user in selecting the images to be backed up can be reduced and optimized, thereby effectively improving the efficiency of image screening.

[0393] Based on the above introduction, it can be understood that the priority of the image tag is actually used when displaying images according to the tag type and in the function of single backup of multiple tags. In this embodiment, the priority of the image tag can be pre-set in the priority configuration file. At the same time, in order to improve the completeness of the function and the flexibility of image backup, a fourth control can be provided in the second interface. Then, according to the user's operation on the fourth control, the interface for configuring the priority is displayed, so that the user can customize the priority of the image tag.

[0394] Combine the following Fig.15 This chapter introduces how to implement custom image label priority. Fig.15 Schematic diagram of the priority configuration file provided in the embodiment of the present application Figure 1 .

[0395] like Fig.15 As shown in (a) of FIG. 1 , the second interface further includes a fourth control 505, and the first application program displays the priority configuration file in response to an operation on the fourth control 505. Fig.15 As shown in (b) in the figure, the opening interface of the priority configuration file is directly displayed.

[0396] The priority configuration file may include the preset priority of each primary tag. The priority of a tag may be represented by a value greater than or equal to 0. The larger the value, the higher the priority. Fig.15In the example (b), the priority of the first-level tag "People" is 5, the priority of the first-level tag "Things" is 4, the priority of the first-level tag "Places" is 3, and the priority of the first-level tag "Date" is 2. Then the default preset priority is: "People" > "Things" > "Places" > "Date".

[0397] Afterwards, the user may edit the priority configuration file. The editing operation may, for example, be to change the priority value of the image tag, thereby updating the priority of the image tag.

[0398] For example, Fig.15 In the example (b) in FIG, if the editing operation changes the priority of the first-level label "person" to 1, then the priority of the image label becomes "thing" > "place" > "date" > "person".

[0399] The priority of image tags actually affects the functions of "multi-tag single backup" and "display images according to tag structure". The impact of these two functions is explained in detail below.

[0400] First of all, in the "Multi-label Single Backup" function, pictures with multiple labels can be backed up in a specified directory in the target folder. The specified directory is the secondary label with the highest priority among the multiple secondary labels of the image.

[0401] It should be noted here that the priority of the first-level tag will first determine the priority of the first-level tag itself, and secondly, the priority of the first-level tag will also affect the priority of each second-level tag under it. For example, the priority of the first-level tag "People" is higher than the priority of the first-level tag "Time", so the priority of each second-level tag under the first-level tag "People" is higher than the priority of each second-level tag under the second-level tag "Time". For example, the priority of the second-level tag "Family" is higher than the priority of the second-level tag "Qingming". Then for a multi-label image that contains both the second-level tags "Family" and "Qingming", the image will be backed up in the second-level directory corresponding to the second-level tag "Family" with a higher priority.

[0402] Secondly, in the "display images according to tag structure" function, the first application determines the order of image tags according to the priority of each image tag. In the above example, the priority configuration file only contains the priority of the first-level tag, so each first-level tag will be displayed in sequence according to the priority. For the second-level tags in the first-level tags, if there is no priority, they can be displayed in sequence according to the default sorting method. The default sorting method can be, for example, sorting according to the first letter of the second-level tag, and this embodiment does not limit this.

[0403] It should be noted here that the reason why only the priority of the first-level tag is preset is that the first-level tag is actually generated by the device gallery application when creating the media table, that is, the first-level tag is preset, but according to the different image contents stored in the device, the second-level tags specifically included under each first-level tag, and the third-level tags specifically included under each second-level tag, etc., are actually not fixed. In other words, it is not certain what tag content is included in each tag level under the first-level tag, so it is impossible to preset the priority for the second-level tag, the third-level tag, etc.

[0404] In a possible implementation, in addition to presetting the priority of each first-level tag in the priority configuration file, the user can also be provided with a function of editing the priority of each level of tags under the first-level tag. Fig.16 To explain, Fig.16 Schematic diagram of the implementation of the priority configuration file provided in the embodiment of the present application Figure 2 .

[0405] like Fig.16 As shown, in the priority configuration file, the three second-level tags "Family", "Friends" and "Colleagues" under the first-level tag "People" can be captured according to the tag structure, and each second-level tag can be displayed in the priority configuration file of the second-level tag. After that, the user can enter a priority value after each second-level tag to configure the priority for the second-level tag.

[0406] For example, refer to Fig.16 , the user enters a priority value of 2 for the secondary tag "family", a priority value of 1 for the secondary tag "friends", and a priority value of 0 for the secondary tag "colleagues", then the priorities of these three secondary tags can be determined as "family" > "friends" > "colleagues". Among them, the priority of the secondary tags is locally effective under the primary tags, that is, the priorities of the secondary tags under each primary tag are independent of each other.

[0407] Alternatively, the user may also input the secondary tag in a certain format in the priority configuration file of the second-level tag and configure the priority of the secondary tag, which is not limited in this embodiment.

[0408] Among them, if the secondary tag entered by the user is an image tag that does not exist in the tag structure, for example, there is no secondary tag "G City" in the image tag, but the user enters the secondary tag "G City" and configures the priority for the secondary tag, then the priority for the secondary tag "G City" is temporarily ineffective because the secondary tag does not exist at present. However, when the secondary tag "G City" is included in the tag structure later, the priority of the secondary tag "G City" can take effect.

[0409] Also, when the user edits the priority configuration file, the data format of the file may be modified incorrectly. In order to ensure the availability of the priority configuration file, the application can detect the correctness of the data format in the file after the user completes the editing. Only when the data format is correct will the priority configuration file edited by the user be saved. When the data format is incorrect, the program prompts that the priority configuration file failed to be saved due to the format error, and the user's editing operation is not saved, and the priority configuration file before editing is used to take effect.

[0410] When the user configures the priority for the secondary tag, in the "Multi-tag Single Backup" function, if an image contains multiple secondary tags under the same primary tag, the backup image directory can be determined according to the priority of the secondary tags. For example, if an image contains both family members and friends, then the secondary tags corresponding to the primary tag "People" include "Family" and "Friends". In the example described above, the priority of the secondary tag "Family" is higher than the secondary tag "Friends", so the image can be backed up to the secondary directory corresponding to the secondary tag "Family". In the current situation, if the priority of the secondary tag is not configured, you can choose to back up the secondary tag with a higher sorting according to the default sorting method of the secondary tags, or select any secondary tag from multiple secondary tags that meet the current situation for backup.

[0411] Also, in the "Display images according to tag structure" function, first sort according to the priority of the first-level tags, and then sort the second-level tags under each first-level tag according to the priority of the second-level tags, so as to clarify the tag arrangement in the graphical backup interface.

[0412] In this embodiment, by providing the user with a function of editing the priority of the second tag, the flexibility of the image backup can be further improved, thereby improving the user experience of the image backup.

[0413] When performing image backup, there may be multiple image applications (APPs) in the first device, where the images in different graphic APPs may be independent of each other. For example, the first device may have a default device gallery APP installed, and may also have other third-party graphic APP1, third-party graphic APP2, etc. In the actual backup process, the user may have image backup requirements for both the device gallery application and other third-party graphic APPs, so the priority configuration file may also include the backup priority set for each application.

[0414] For example, refer to Fig.16 , the priority set for the device gallery application is 30, the priority set for the third-party graphics APP1 is 20, and the priority set for the third-party graphics APP2 is 10. In one possible implementation, the backup priority setting has the following rules: only back up images for the application with the highest priority, so in the current case, the first application will only back up images in the device gallery application. If the user needs to back up the images of other third-party graphics APPs, the backup priority of the other third-party graphics APPs needs to be changed. For example, edit the priority configuration file and change the priority of the third-party graphics APP1 to 30, then the first application will back up the images of both the device gallery application and the third-party graphics APP1.

[0415] It should also be noted that when performing image backup for different applications, a general folder can be created for each graphic application. After that, various possible image backup processes for each graphic application will be completed in its corresponding general folder. The general folders corresponding to different graphic applications can be parallel in directory relationship, thereby ensuring that the image backups of each image application do not affect each other, avoiding errors and confusion in image backup.

[0416] For example, a first folder is set for the device gallery APP. When backing up images for the device gallery APP, the incremental folders and supplementary folders introduced above are maintained for the images in the device gallery APP in the first folder, so as to realize the image backup for the device gallery APP. For another example, a second folder is set for the third-party gallery APP1. When backing up images for the third-party gallery APP1, the incremental folders and supplementary folders introduced above are maintained for the images in the third-party gallery APP1 in the second folder, so as to realize the image backup for the third-party gallery APP1. Regardless of which image application is used, the image backup processing method is similar, and the contents introduced in the above embodiments can be referred to, which will not be repeated here.

[0417] Regardless of which graphic APP, the first application needs to obtain the image tags in the corresponding graphic APP to implement image backup. Therefore, an application support file can also be maintained in the first application, and the application support file includes a database to be queried and a corresponding query structure set for each graphic APP.

[0418] The application support file may be, for example, an ApplicationSupportProfile.json file, which is described below as an example:

[0419] Graphics application support list SupportedApps

[0420]

[0421]

[0422] Referring to the above introduction, it can be determined that for each graphic APP, its corresponding query database, query interface and parameter list to be queried can be configured in the application support file, and multiple tables to be queried can be configured in the parameter list. The application support file can be maintained by the developer, and then the first application can query the corresponding database based on the application support file, and obtain the required parameters through the corresponding query interface to obtain the label structure of the graphic APP.

[0423] Therefore, in this embodiment, the various image backup functions introduced above can be effectively implemented for various possible graphic apps to effectively ensure the coverage integrity of the functions.

[0424] Regarding the contents introduced in the above embodiments, it should also be noted that the default image tags used in this application are those provided in graphic applications, such as people, things, places, dates, etc. However, this application is not limited to the use of only the image tags provided in graphic applications. Users can also use existing image classification methods or classification tools to classify images, thereby obtaining image classification results. The image classification tool or application can be deployed in the second device, and the image classification results obtained based on this are also stored in the second device, and the image classification results are queryable data. Then, the first application can obtain the corresponding label structure based on the image classification results, and then implement the various functions introduced above based on the label structure. That is to say, in the actual implementation process, the image labels can be provided by users in addition to the default ones of graphic APPs, and they can all implement the technical solutions of this application.

[0425] Regardless of which of the above-described methods is used to determine the image label, there is no need to deploy the image classification model in the first application. Therefore, the technical solution of the present application can ensure the lightweight of the first application.

[0426] Furthermore, in the present application, a fifth control may be provided in the second interface, and then according to the user's operation on the fifth control, a backup information record table with read-only permission is displayed so that the user can view the specific image backup status.

[0427] Combine the following Fig.17 This section introduces how to view the backup information record table. Fig.17 A schematic diagram of an implementation of viewing a backup information record table provided in an embodiment of the present application.

[0428] like Fig.17 As shown in (a) of FIG. 1 , the second interface further includes a fifth control 507, and the first application program displays a backup information record table in response to an operation on the fifth control 507. Fig.17 As shown in (b) in the figure, the opening interface of the backup information record table is directly displayed, and the file permission of the backup information record table is read-only, preventing the user from modifying the backup information record table.

[0429] Based on the above embodiments, Fig.18 Taking the second device being a mobile phone and the first device being a PC as an example, a flowchart is used to further introduce the specific execution process of the image backup method in this application. Fig.18 A flowchart of the image backup method provided in an embodiment of the present application.

[0430] like Fig.18 As shown, the method includes:

[0431] 1. A first interface in a first application on a PC receives an operation on a first control.

[0432] Among them, in response to the operation acting on the first control, the second interface can be opened. The specific implementation method of the second interface can refer to the introduction of the above embodiment, which will not be repeated here.

[0433] 2. In the second interface, receive an operation on the first display configuration bar.

[0434] The first display configuration bar is used to configure whether to display the image according to the label structure. The operation on the first display configuration bar can be an operation on the first confirmation control or an operation on the first cancellation control. Regardless of which control is operated, the second interface can send the operation content in the first display configuration bar to the display processing unit in the first application on the PC, and the operation content also indicates which control the user has clicked.

[0435] 3. The display processing unit generates a data query command according to the operation content.

[0436] If the operation content indicates that the user has operated the first determined control, it can be confirmed that the image is currently to be displayed according to the tag structure, so a data query command can be generated. Exemplarily, the display processing unit can also determine whether the operation on the first determined control is the first operation in this backup process, and only generate a data query command if it is determined to be the first operation.

[0437] If it is not the first time to operate the first determination control, it means that the image data has been queried before, and there are some cached images in the first device, so the first interface can be updated according to the cached images in the first device without generating a data query command. When it is determined that the cached images in the first device need to be supplemented, a data query command is generated to obtain the image data.

[0438] Alternatively, if the operation content indicates that the user has operated the first negative control, it can be confirmed that the image is currently displayed in a time period division manner. In this case, there is no need to determine the tag structure, and therefore no need to generate a data query command.

[0439] 4. The display processing unit sends a data query command to the first application on the mobile phone.

[0440] 5. The first application on the mobile phone responds to the data query command and queries the image data of the image.

[0441] The data query command here is used to query the image data of at least part of the multiple images in the second device, wherein the image data may include an image tag and a storage path, wherein the image data may also include, for example, the image itself or a thumbnail of the image, etc., so that the first device can cache at least part of the image locally so as to display it in the first interface. As for which part of the image is specifically, it can be determined according to actual needs.

[0442] Exemplarily, the first application on the mobile phone may query the image database of the gallery APP that currently needs to be backed up, access the media table therein, and thereby query and obtain image data of at least part of the images.

[0443] 6. The first application on the mobile phone sends the image data of the image to the display processing unit.

[0444] 7. The display processing unit updates the first interface according to the image data of the image.

[0445] For example, a label structure may be constructed based on image labels of at least part of the image, and then the images in the first interface may be displayed in sequence according to the order of their respective labels and the constructed label structure. The specific implementation method may refer to the contents of the above embodiments and will not be described in detail here.

[0446] 8. In the second interface, receive an operation acting on the second display configuration bar.

[0447] The second display configuration bar is used to configure whether to display only the incremental image in the image, and the operation on the second display configuration bar can be an operation on the second confirmation control or an operation on the second cancellation control. Regardless of which control is operated, the second interface can send the operation content in the second display configuration bar to the display processing unit, and the operation content also indicates which control the user has clicked.

[0448] 9. The display processing unit sends a first information query instruction to the backup information recording unit.

[0449] If the user operates the second determination control, it is necessary to determine which of the multiple images in the current first interface are not backed up. The backup information recording unit may include a backup information recording table, so the display processing unit may send a first information query instruction to the backup information recording unit to query the image backup status of each of the multiple images in the current first interface.

[0450] If the user performs an operation on the second cancel control, there is no need to send the first information query instruction.

[0451] 10. The backup information recording unit sends the first image backup information to the display processing unit.

[0452] The first image backup information includes the image backup information of each image included in the current first interface. The image backup information may include whether the image has been backed up, the backup location, the backup time, etc.

[0453] 11. The display processing unit updates the first interface according to the first image backup information.

[0454] Specifically, the display processing unit displays only the incremental image in the image in the first interface according to the first image backup information.

[0455] 12. In the second interface, receive an operation on the fourth control.

[0456] 13. The second interface sends an opening instruction to the priority configuration unit.

[0457] 14. Priority Configuration Unit Open the priority configuration file.

[0458] 15. The priority configuration unit receives an edit operation for the priority configuration file.

[0459] The implementation of the priority configuration file may refer to the contents described in the above embodiment, which will not be described in detail here.

[0460] It should also be noted that steps 2 to 7 in this embodiment introduce operations and processing for the first display configuration bar, and steps 8 to 11 introduce operations and processing for the second display configuration bar, and steps 12 to 15 introduce operations and processing for the fourth control. In the actual implementation process, the operation order of these three parts can be determined according to the actual needs of the user, and this embodiment does not limit this.

[0461] 16. In the second interface, receive operations on the first backup configuration bar, the second backup configuration bar, and the confirmation control.

[0462] The specific operation method can refer to the introduction of the above embodiment and will not be repeated here.

[0463] 17. The backup processing unit determines an image backup strategy according to the operation contents on the first backup configuration bar, the second backup configuration bar, and the confirmation control.

[0464] Among them, the operation methods of the first backup configuration bar, the second backup configuration bar and the confirmation control, and the implementation methods of the image backup strategy composed of various possible operation methods can refer to the introduction of the above embodiments, which will not be repeated here.

[0465] 18. The backup processing unit sends a second information query instruction to the priority configuration unit.

[0466] 20. The priority configuration unit sends the second image backup information to the backup processing unit.

[0467] The second information query instruction is used to query the priority of the image tag of each target image, and accordingly, the second image backup information includes the priority of the image tag of each target image.

[0468] 20. The backup processing unit sends a data query command to the first application on the mobile phone.

[0469] 21. The first application on the mobile phone responds to the data query command and queries the image data of the target image.

[0470] The image data may include image tags and storage locations, etc.

[0471] 22. The first application on the mobile phone sends the image data of the target image to the backup processing unit.

[0472] Although it is described above that the display processing unit also queries image data through the data query command, the image data triggered by the two data query commands are different.

[0473] 23. The backup processing unit processes the target folder according to the image data of the target image, and backs up the target image to the target folder according to the image data.

[0474] The processing target folder may be the newly created supplementary folder described above, or may be the updated incremental folder described above, so that the tag structure composed of the image tags of the target image is consistent with at least part of the directory structure in the target folder.

[0475] Furthermore, the backup processing unit will back up the target image to the target folder according to the image data according to the image backup strategy. Specifically, the target image will be backed up accordingly according to the image tag, and when backing up, the target image will be accessed according to the file path in the image data, thereby realizing the backup.

[0476] 24. The backup processing unit maintains the backup information recording table in the backup information recording unit.

[0477] In summary, in the technical solution of the present application, in order to solve the multiple problems that reduce the user experience when backing up images in the second device to the first device (inability to automatically create a classification directory, inability to automatically identify unbacked up pictures, duplicate backup of multi-label photos, and non-customizable picture display / backup strategy), a method for automatically classifying and backing up pictures based on classified labels of pictures and priority configuration strategy is proposed. By providing the five functions of "display by picture type", "only display pictures that have not been backed up to incremental folders", "incremental backup", "multi-label single backup" and "custom configuration strategy" in the first application, the first application can automatically create a classification directory in the first device, automatically identify unbacked up pictures in the mobile phone, non-duplicate backup of multi-label photos, and allow users to customize picture display / backup strategies according to personal preferences, so as to avoid duplicate backup of pictures and allow users to customize picture display / backup strategies, thereby greatly improving the user experience when backing up pictures.

[0478] In addition, the present application can significantly reduce the time consumption required for backing up images. For the calculation formula 1 introduced above for expressing the time consumption of image backup, the technical solution of the present application can optimize it into the following formula 2:

[0479] TC=T3*NumImage formula 2

[0480] Formula 2 is also explained using a specific example. Assuming that there are 1,000 pictures in the user's mobile phone that need to be backed up, and assuming that the transmission time T3 is 0.1 seconds, the total backup time is 0.1s*1000=100s. It can be understood that this effectively shortens the backup time.

[0481] The method of the image backup method of the embodiment of the present application has been described above, and the device for executing the above-mentioned image backup method provided by the embodiment of the present application is described below. Those skilled in the art can understand that the method and the device can be combined and referenced with each other, and the relevant device provided by the embodiment of the present application can execute the steps in the above-mentioned image backup method.

[0482] Fig.19 This is a schematic diagram of the structure of the image backup device provided in the embodiment of the present application. Fig.19 As shown, the device 190 includes: a display module 1901, a processing module 1902;

[0483] Processing module 1902, configured to connect the first device to a second device in response to a first user operation, wherein the second device includes a plurality of images;

[0484] Display module 1901, configured to cause the first device to display a first interface in response to a second user operation, where the first interface includes a first control and the plurality of images;

[0485] The display module 1901 is further configured to, in response to a third user operation acting on the first control, cause the first device to display a second interface, where the second interface includes a second control;

[0486] The processing module 1902 is further configured to, in response to a fourth user operation acting on the second control, configure the image backup strategy by the first device;

[0487] The processing module 1902 is further configured to, in response to a fifth user operation, enable the first device to back up the multiple images based on the image backup policy.

[0488] In some implementations, the image backup strategy is: backing up a target image among the multiple images to a target directory of a target folder in the first device.

[0489] In some implementations, the second control is a first affirmative control, the target image is an image among the multiple images that has not been backed up in an incremental folder, and the target folder is an incremental folder in the first device for backing up incremental images.

[0490] In some implementations, the second control is a first negative control, the target image is at least a portion of the multiple images, and the target folder is a newly expanded folder created in response to the fourth user operation.

[0491] In some implementations, the method further includes:

[0492] In response to a sixth user operation performed on the first interface, the first device determines a selected image from the multiple images.

[0493] In some implementations, when the second control is the first affirmative control, the target image is an image among the selected images that has not been backed up in the incremental folder;

[0494] When the second control is the first negative control, the target image is the selected image.

[0495] In some implementations, the second control is a second affirmative control, and the target directory is a directory corresponding to the bottom-level tag with the highest priority of the target image.

[0496] In some implementations, the second control is a second negative control, and the target directory includes a directory corresponding to at least one bottom-level tag of the target image.

[0497] In some implementations, the second interface further includes a third control;

[0498] The display module 1901 is specifically used for:

[0499] In response to a seventh user operation on the third control, the first device updates the multiple images displayed in the first interface.

[0500] In some implementations, the third control is a first confirmation control or a first cancellation control;

[0501] The processing module 1902 is specifically used for:

[0502] In response to a seventh user operation on the first determination control, the first device updates the first interface to: display the plurality of images according to the image tags of the images; or,

[0503] In response to a seventh user operation on the first cancel control, the first device updates the first interface to display the multiple images according to the generation time periods to which the images belong.

[0504] In some implementations, the third control is a second confirmation control or a second cancellation control;

[0505] The processing module 1902 is specifically used for:

[0506] In response to a seventh user operation on the second determination control, the first device updates the first interface to: display only the images among the plurality of images that are not backed up in the incremental folder; or,

[0507] In response to a seventh user operation on the second cancel control, the first device updates the first interface to display a full amount of the plurality of images.

[0508] In some implementations, the second interface further includes a fourth control;

[0509] The display module 1901 is also used for:

[0510] In response to an eighth user operation acting on the fourth control, the first device displays a priority profile;

[0511] An edit operation acting on the priority configuration file is received, the edit operation being used to update a priority of an image tag.

[0512] In some implementations, the second interface further includes a fifth control;

[0513] The display module 1901 is also used for:

[0514] In response to a ninth user operation on the fifth control, the first device displays a backup information record table, the permission of the backup information record table being read-only.

[0515] In some implementations, the level of the label structure corresponding to the image label of the target image is N, where N is an integer greater than or equal to 1, wherein when N is greater than or equal to 2, any i-th level label is a lower layer label of its corresponding i-1-th level label, where i is an integer greater than or equal to 2 and less than or equal to N;

[0516] The directory structure of the target folder has at least N levels, any tag in the tag structure has a corresponding directory in the directory structure, and the hierarchical relationship between any two first tags and second tags in the tag structure is consistent with the hierarchical relationship between the first directory and the second directory in the directory structure, the first directory corresponds to the first tag, and the second directory corresponds to the second tag.

[0517] The device provided in this embodiment can be used to execute the technical solution of the above method embodiment. Its implementation principle and technical effect are similar and will not be described in detail in this embodiment.

[0518] The image backup method provided in the embodiment of the present application can be applied to electronic devices with communication functions. The electronic devices include terminal devices, and the specific device form of the terminal devices can refer to the above related descriptions.

[0519] The present application embodiment provides a terminal device, Fig. 20 A schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present application.

[0520] like Fig. 20 As shown, the terminal device 200 includes: a processor 2001 and a memory 2002; the memory 2002 stores computer execution instructions; the processor 2001 executes the computer execution instructions stored in the memory 2002, so that the terminal device 200 executes the above method.

[0521] When the memory 2002 is independently provided, the terminal device further includes a bus 2003 for connecting the memory 2002 and the processor 2001 .

[0522] Furthermore, the software system of the terminal device may adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture, etc. The embodiment of the present application takes the Android system of the layered architecture as an example to exemplify the software structure of the terminal device.

[0523] The layered architecture divides the software into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the several layers are, from top to bottom, the application layer, the application framework layer, the system library (native layer) and the Android runtime (Android runtime), the HAL (Hardware Abstraction Layer, hardware abstraction) layer, the kernel layer, and the hardware layer. The technical solution of the present application can be implemented, for example, at the application layer.

[0524] The embodiment of the present application provides a chip. The chip includes a processor, and the processor is used to call a computer program in a memory to execute the technical solution in the above embodiment. Its implementation principle and technical effect are similar to those of the above related embodiments, and will not be repeated here.

[0525] The embodiments of the present application also provide a computer-readable storage medium. The computer-readable storage medium stores a computer program. The above method is implemented when the computer program is executed by the processor. The method described in the above embodiment can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium or transmitted on a computer-readable medium. Computer-readable media can include computer storage media and communication media, and can also include any medium that can transfer a computer program from one place to another. The storage medium can be any target medium that can be accessed by a computer.

[0526] In one possible implementation, a computer-readable medium may include RAM, ROM, compact disc read-only memory (CD-ROM) or other optical disk storage, disk storage or other magnetic storage devices, or any other medium that is intended to carry or store the required program code in the form of instructions or data structures and can be accessed by a computer. Moreover, any connection is appropriately referred to as a computer-readable medium. For example, if a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) is used to transmit software from a website, server or other remote source, the coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology such as infrared, radio and microwave are included in the definition of medium. Disks and optical disks as used herein include optical disks, laser disks, optical disks, digital versatile disks (DVD), floppy disks and Blu-ray disks, where disks usually reproduce data magnetically, while optical disks reproduce data optically using lasers. Combinations of the above should also be included in the scope of computer-readable media.

[0527] An embodiment of the present application provides a computer program product, which includes a computer program. When the computer program is executed, the computer executes the above method.

[0528] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable device to generate a machine, so that the instructions executed by the processing unit of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0529] The above specific implementation methods further illustrate the purpose, technical solutions and beneficial effects of the present invention in detail. It should be understood that the above are only specific implementation methods of the present invention and are not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the present invention should be included in the scope of protection of the present invention.

Claims

1. An image backup method, characterized in that: The method is applied to a first device, and the method includes: In response to a first user operation, the first device is connected to a second device, wherein the second device includes a plurality of images; In response to a second user operation, the first device displays a first interface, where the first interface includes a first control and the plurality of images; In response to a third user operation acting on the first control, the first device displays a second interface, where the second interface includes a second control; In response to a fourth user operation acting on the second control, the first device configures an image backup policy; In response to a fifth user operation, the first device backs up the multiple images based on the image backup policy.

2. The method according to claim 1, characterized in that The image backup strategy is: backing up a target image among the multiple images to a target directory of a target folder in the first device.

3. The method according to claim 2, characterized in that The second control is a first affirmative control, the target image is an image among the multiple images that has not been backed up in the incremental folder, and the target folder is an incremental folder in the first device for backing up incremental images.

4. The method according to claim 2, characterized in that The second control is a first negative control, the target image is at least a portion of the multiple images, and the target folder is an expanded folder newly created in response to the fourth user operation.

5. The method according to any one of claims 2 to 4, characterized in that: The method further comprises: In response to a sixth user operation performed on the first interface, the first device determines a selected image from the multiple images.

6. The method according to claim 5, characterized in that When the second control is a first affirmative control, the target image is an image among the selected images that has not been backed up in the incremental folder; When the second control is a first negative control, the target image is the selected image.

7. The method according to any one of claims 2 to 6, characterized in that: The second control is a second affirmative control, and the target directory is a directory corresponding to the bottom-level tag with the highest priority of the target image.

8. The method according to any one of claims 2 to 6, characterized in that: The second control is a second negative control, and the target directory includes a directory corresponding to at least one bottom-level label of the target image.

9. The method according to any one of claims 2 to 8, characterized in that: The second interface also includes a third control; The method further comprises: In response to a seventh user operation on the third control, the first device updates the multiple images displayed in the first interface.

10. The method according to claim 9, characterized in that The third control is a first confirmation control or a first cancellation control; In response to the seventh user operation on the third control, the first device updates the plurality of images displayed in the first interface, including: In response to a seventh user operation on the first determination control, the first device updates the first interface to: display the plurality of images according to the image tags of the images; or, In response to a seventh user operation on the first cancel control, the first device updates the first interface to display the multiple images according to the generation time periods to which the images belong.

11. The method according to claim 9, characterized in that The third control is a second confirmation control or a second cancellation control; In response to the seventh user operation on the third control, the first device updates the image displayed in the first interface, including: In response to a seventh user operation on the second determination control, the first device updates the first interface to: display only the images among the plurality of images that are not backed up in the incremental folder; or, In response to a seventh user operation on the second cancel control, the first device updates the first interface to display a full amount of the plurality of images.

12. The method according to any one of claims 2 to 11, characterized in that: The second interface also includes a fourth control; The method further comprises: In response to an eighth user operation acting on the fourth control, the first device displays a priority profile; An edit operation acting on the priority configuration file is received, the edit operation being used to update a priority of an image tag.

13. The method according to any one of claims 2 to 12, characterized in that: The second interface also includes a fifth control; The method further comprises: In response to a ninth user operation on the fifth control, the first device displays a backup information record table, the permission of the backup information record table being read-only.

14. The method according to any one of claims 2 to 13, characterized in that: The level of the label structure corresponding to the image label of the target image is N, where N is an integer greater than or equal to 1, wherein when N is greater than or equal to 2, any i-th level label is a lower-layer label of its corresponding i-1-th level label, where i is an integer greater than or equal to 2 and less than or equal to N; The directory structure of the target folder has at least N levels, any tag in the tag structure has a corresponding directory in the directory structure, and the hierarchical relationship between any two first tags and second tags in the tag structure is consistent with the hierarchical relationship between the first directory and the second directory in the directory structure, the first directory corresponds to the first tag, and the second directory corresponds to the second tag.

15. A terminal device, characterized in that: include: Processor and memory; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the terminal device executes the method according to any one of claims 1 to 14.

16. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the method according to any one of claims 1 to 14 is implemented.

Images