Method and device for managing cloud data

Abstract

The invention provides a method and device for managing cloud data, and the method comprises the steps: recognizing to-be-managed data from the data, stored in a cloud storage application, of a target application in the cloud storage application in the cloud storage application; and intensively displaying the identified to-be-managed data in an intelligent identification management area in a cloud storage management interface corresponding to the target application in the cloud storage application. According to the scheme, the data needing to be managed in the cloud data of the target application is recognized, and the intelligent recognition management area is newly added in the management interface corresponding to the target application for centralized display, so that a user can conveniently manage the data of the target application in the intelligent recognition management area in a centralized manner subsequently.

Description

Technical Field

[0001] The present application relates to the technical field of electronic equipment, and in particular to a method and device for managing cloud data. Background Art

[0002] Cloud storage is an increasingly widely used function. When the cloud synchronization function is turned on, local resources on electronic devices will be automatically transferred to the cloud. However, due to this synchronization, a large number of files that users do not want to store and files that have no value (such as similar photos, useless screenshots, duplicate files) are easily uploaded to the cloud without distinction, occupying the user's cloud storage space, resulting in a waste of storage space resources, and making the files stored in the cloud storage space chaotic and complicated, making it difficult to find and manage.

[0003] Therefore, how to manage data in cloud storage space more efficiently is a technical problem that needs to be solved urgently. Summary of the invention

[0004] The present application provides a method and device for managing cloud data, which can manage data in a cloud storage space more efficiently.

[0005] In a first aspect, a method for managing cloud data is provided, the method comprising: in a cloud storage application, identifying data to be managed from data already stored in the cloud storage application by a target application; and centrally displaying the identified data to be managed in an intelligent identification management area in a cloud storage management interface corresponding to the target application in the cloud storage application.

[0006] In the technical solution of the present application, the data that needs to be managed in the cloud data of the target application is mainly identified, and a smart identification management area is added in the management interface corresponding to the target application for centralized display, so that users can centrally manage the data of the target application in the smart identification management area in the future.

[0007] In combination with the first aspect, in certain implementations of the first aspect, the target application includes at least one of the following: a gallery, an address book (contacts), notes (memos), and file management. The gallery is used to manage photos and / or recorded videos. The address book (contacts) is used to manage at least one of telephone numbers, mobile phone numbers, and email addresses. Notes (memos) are used to manage record files such as text, pictures, and videos stored by users. File management is used to manage various types of files. In this implementation, the target application is mainly locked in applications that are most likely to require data management. For example, the gallery is most likely to have unwanted, duplicate, blurred, and other types of photos, the address book is prone to invalid contact information, and notes are prone to blank and invalid notes. Other files will appear in the file management, and duplicate and redundant files are prone to appear.

[0008] In one example, when the target application includes a gallery, the data to be managed identified includes at least one of the following: screenshots, screen recordings, similar and duplicate images, and sensitive photos. Screenshots Figure 1 Generally have relatively strong timeliness and are used for communicating with others or for shopping searches, etc. Most of them are likely to be unwanted later, so they will be one of the identification objects (which can also be considered as the types of photos to be identified corresponding to the gallery application). Screen recordings also have similar properties to screenshots, so they will also be one of the identification objects. Moreover, screen recordings occupy a relatively large amount of storage space, and clearing useless screen recordings can also better release storage space. Similar and duplicate images refer to images with a relatively high similarity rate, which are generally likely to be generated in continuous shooting scenarios, or when continuously capturing, or in scenarios where multiple shots are taken to avoid unclear shots. Finally, the user may only need to keep the best one, but the synchronous and undifferentiated upload results in all of them being uploaded to the cloud, resulting in a waste of storage resources. In addition, if the photo name is changed or re-downloaded, it may result in two identical photos being saved, that is, an example of duplicate photos with different source data. Therefore, these similar and duplicate photos will be used as identification objects. The address book is prone to situations such as invalid contacts, duplicate contacts, blank contacts, etc., so it will also be used as an identification object. Sensitive photos mainly refer to photos that are likely to disclose user privacy, such as photos of various certificates like ID cards, passports, student IDs, bank cards, etc. Document photos are mainly photos taken and archived for documents such as contracts, agreements, and contracts. Privacy photos can be considered as the underlying category of all sensitive photos, and all sensitive photos other than the above can be classified as privacy photos. Therefore, for security reasons, sensitive photos will also be used as identification objects.

[0009] In one example, the similar and duplicate images include at least one of compositionally similar photos, burst snapshots, and duplicate photos with different source data. Compositionally similar photos are mainly used to screen out photos with a high similarity in the overall picture presentation. For example, taking many photos of the same object is one of the possibilities, but it should be understood that although burst photos may result in compositionally similar photos, compositionally similar photos do not necessarily have to be generated only by burst shooting.

[0010] In one example, the sensitive photos include at least one of ID photos, document photos, and privacy photos.

[0011] In one example, when the target application includes an address book, the data to be managed identified includes at least one of the following: duplicate contacts, blank contacts, duplicate address book groups, and blank address book groups.

[0012] In one example, when the target application includes notes, the data to be managed identified includes at least one of the following: blank notes and duplicate notes.

[0013] In one example, when the target application includes file management, the identified data to be managed includes at least one of files with similar or identical names and documents with similar or identical names.

[0014] In combination with the first aspect, in some implementations of the first aspect, when the identified data to be managed includes screenshots, the above-mentioned centralized display of the identified data to be managed in the intelligent recognition management area includes: displaying the number of identified screenshots and the first management control corresponding to the screenshots in the intelligent recognition management area;

[0015] The above method further includes:

[0016] In response to a user's click operation on the first management control, a screenshot management interface is displayed; in response to a management gesture operation by the user in the screenshot management interface, the identified screenshots are managed.

[0017] In this implementation, when screenshots need to be managed, management controls for the screenshots are set in the centrally displayed intelligent recognition management area, allowing users to trigger the management of screenshots through confirmation operations on the controls, and in the screenshot management interface, corresponding management is performed by recognizing the user's management gesture operations.

[0018] In one example, the management gesture operations in the screenshot management interface include at least one of a horizontal swipe operation and a drag-to-function identifier operation. The horizontal swipe operation is used to switch the screenshots displayed in the screenshot management interface, and the drag-to-function identifier operation is used to perform the operation corresponding to the function identifier on the screenshot currently displayed in the screenshot management interface. The function identifier includes at least one of archiving and deleting. The method of managing screenshots by dragging to the function identifier is a relatively intuitive and user-friendly interaction method, which can avoid misoperations to a certain extent because the dragging process allows the user to change their mind. Just lifting the hand midway will end the operation, and the user's management participation is higher.

[0019] In another example, the above method further includes: displaying small images of each screenshot in the small icon display area in the screenshot management interface; in response to a user's selection operation on any small image, the large image corresponding to the small image is displayed in the screenshot management interface. In this example, by setting two areas, namely the small icon display area and the large image display area, in the screenshot management interface, another way to switch the large image is added, and the user has more options.

[0020] In combination with the first aspect, in some implementations of the first aspect, when the identified data to be managed includes similar and duplicate images, when the identified data to be managed is centrally displayed in the intelligent recognition management area, it may include: displaying the number of groups of identified similar and duplicate images and the second management control corresponding to the similar and duplicate images in the intelligent recognition management area;

[0021] The above method further includes:

[0022] In response to a user's click operation on the second management control, a similar duplicate image management interface is displayed; in response to a user's management operation in the similar duplicate image management interface, each group of similar duplicate images is managed.

[0023] In this implementation, when it is necessary to manage similar duplicate images, a management control for similar duplicate images is set in the centrally displayed intelligent recognition management area, allowing the user to trigger the management of similar duplicate images through the confirmation operation of the control, and in the similar duplicate image management interface, corresponding management is performed by recognizing the user's management operation.

[0024] In one example, the management operations of the similar duplicate image management interface include at least one of the following: a one-key deletion operation, a selection operation, and a sliding switching operation; the one-key deletion operation is a click operation on the one-key deletion control, used to delete all selected photos in the current similar duplicate image group; the selection operation is used to select any one or more similar duplicate images; the sliding switching operation includes a group switching operation and a switching operation of photos within a group.

[0025] In one example, the management operations in the similar duplicate image management interface include a selection operation and a one-key deletion operation. The above-mentioned management of each group of similar duplicate images in response to the user's management operation in the similar duplicate image management interface includes:

[0026] In response to a user's click operation on the click control in at least one similar duplicate image in the current similar duplicate image group, at least one similar duplicate image is selected;

[0027] In response to a user's click operation on the one-key deletion control, all selected similar duplicate images in the current similar duplicate image group are deleted.

[0028] In this example, it is more efficient to select multiple and delete them with one key.

[0029] In another example, the management operation in the similar duplicate image management interface includes a sliding switching operation, and the sliding switching operation includes a group switching operation and a switching operation of photos within a group; the above-mentioned management of each group of similar duplicate images in response to the user's management operation in the similar duplicate image management interface includes:

[0030] In response to a user's group switching operation on the current similar duplicate image group, the current similar duplicate image group displayed in the similar duplicate image management interface is switched to the next group of similar duplicate image groups indicated by the sliding direction of the group switching operation; or,

[0031] In response to a user's operation of switching group photos on a similar duplicate photo being displayed in the similar duplicate photo management interface, switch the currently displayed similar duplicate photo to the next similar duplicate photo in the current similar duplicate photo group indicated by the sliding direction of the group photo switching operation.

[0032] In one example, the operation of switching photo groups is a vertical swipe, and the operation of switching group photos is a horizontal swipe.

[0033] In combination with the first aspect, in some implementations of the first aspect, when the identified data to be managed includes sensitive photos, the identified data to be managed is centrally displayed in the intelligent recognition management area, including: displaying the number of identified sensitive photos and the third management control corresponding to the sensitive photos in the intelligent recognition management area;

[0034] The above method further includes: in response to a user's click operation on the third management control, displaying a sensitive photo management interface; and in response to a management gesture operation of the user in the sensitive photo management interface, managing the identified sensitive photos.

[0035] In this implementation, when it is necessary to manage sensitive photos, management controls for sensitive photos are set in the centrally displayed intelligent recognition management area, allowing users to trigger the management of sensitive photos through confirmation operations on the controls, and in the sensitive photo management interface, corresponding management is performed by recognizing the user's management operations.

[0036] In one example, the management operations in the sensitive photo management interface include at least one of the following: encryption operation, decryption operation, deletion operation, selection operation, and one - key encryption operation; when any sensitive photo is encrypted, the sensitive photo is marked with an encryption mark on the electronic device side, and the image content of the sensitive photo is invisible on the cloud side; the decryption operation is used to cancel the encryption of the sensitive photo; the deletion operation is used to delete the selected photos in the sensitive photo interface; the selection operation is used to select one or more sensitive photos to be processed; the one - key encryption operation is used to encrypt all the selected sensitive photos.

[0037] The above management operations can cooperate with each other to achieve different management purposes. For example, at least one sensitive photo can be selected in response to the selection operation, and then the selected photo can be encrypted in response to the one - key encryption operation or the encryption operation; for another example, at least one sensitive photo can be selected in response to the selection operation, and then the selected photo can be deleted in response to the deletion operation; for another example, at least one encrypted sensitive photo can be selected in response to the selection operation, and then the selected encrypted photo can be decrypted in response to the decryption operation. Other situations are not listed one by one.

[0038] In combination with the first aspect, in some implementations of the first aspect, when the target application includes a gallery, the above method further includes: in response to a user's click operation on the data details display area in the cloud storage management interface corresponding to the gallery in the cloud storage application, displaying a photo aggregation management interface; in response to a user's aggregation operation on at least one selected target attribute in the photo aggregation management interface, aggregating the photos according to each target attribute in the at least one target attribute.

[0039] In this implementation, the photos can be saved by classifying (grouping) them according to specific one or more target attributes, which is convenient for the user to view later. For example, all the photos taken at a certain tourist attraction can be found, and even if the user has been there many times, the photos taken during multiple trips can be grouped together according to the location attribute. Another example is that when combining location and person, the photos of the same person at that location can be grouped together. For example, user A aggregates all the photos of friend B at a certain city on their electronic device. Other cases will not be listed one by one. There can be one or more target attributes, which can be flexibly and freely combined, making the aggregation and classification of photos by the user more flexible.

[0040] In one example, the at least one target attribute includes at least one of the following: location, time, person, and object.

[0041] In the second aspect, a device for managing cloud data is provided. The device includes a unit composed of software and / or hardware for executing any method of the first aspect.

[0042] In the third aspect, an electronic device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it can implement any method of the first aspect.

[0043] In the fourth aspect, a chip is provided, including a processor for reading and executing a computer program stored in a memory. When the computer program is executed by the processor, it can implement any method of the first aspect.

[0044] Optionally, the chip further includes a memory, and the memory is electrically connected to the processor.

[0045] Optionally, the chip can further include a communication interface.

[0046] In the fifth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it can implement any method of the first aspect.

[0047] In a sixth aspect, there is provided a computer program product, which includes a computer program that can implement any of the methods in the first aspect when executed by a processor. Description of the Drawings

[0048] Figure 1 is an example of an interface for managing cloud data.

[0049] Figure 2 is a schematic structural diagram of an interface of a cloud storage application according to an embodiment of the present application.

[0050] Figure 3 is a schematic flowchart of a method for managing cloud data according to an embodiment of the present application.

[0051] Figure 4 is a schematic diagram of a management interface of a picture gallery and notes in a cloud storage application according to an embodiment of the present application.

[0052] Figure 5 is a schematic diagram of a management interface of a contacts application in a cloud storage application according to an embodiment of the present application.

[0053] Figure 6 is a schematic diagram of an interaction process of screenshot management according to an embodiment of the present application.

[0054] Figure 7 is a schematic diagram of another interaction process of screenshot management according to an embodiment of the present application.

[0055] Figure 8 is a schematic diagram of an interaction process of managing similar and duplicate pictures according to an embodiment of the present application.

[0056] Figure 9 is a schematic diagram of another interaction process of managing similar and duplicate pictures according to an embodiment of the present application.

[0057] Figure 10 is a schematic diagram of an interaction process of managing cloud data of sensitive photos according to an embodiment of the present application.

[0058] Figure 11 and Figure 12 is a schematic diagram of an interaction process of aggregated photos according to an embodiment of the present application.

[0059] Figure 13 is a schematic diagram of a device for managing cloud data according to an embodiment of the present application.

[0060] Figure 14 is a schematic hardware structure diagram of an electronic device according to an embodiment of the present application. Detailed Embodiments

[0061] The solutions of the embodiments of the present application will be introduced below with reference to the accompanying drawings.

[0062] Figure 1 It is an example of an interface for managing cloud data. Figure 1 It is an example of interface interaction for managing cloud data in a traditional solution. Interface 101 and Interface 102 are examples of interfaces of a cloud storage application. Interface 101 is the home page of the cloud storage application. The cloud storage application can be understood as an application program (app) installed on an electronic device to manage the user's cloud data. In Interface 101, basic information about the storage status of cloud data is displayed, including basic information such as the user's avatar and number, as well as the capacity and used capacity of the cloud storage space, and the data information of each application that can perform cloud synchronization. For example, 120 items of the photo album application have been uploaded to the cloud storage space, that is, 120 items have been synchronously uploaded to the cloud for storage. 102 people's contact information has been uploaded by the contact application. 50 text messages have been synchronously uploaded to the cloud by the text message application, and 300 items have been synchronously uploaded by the cloud disk application. In Interface 102, different applications are displayed in the form of side-by-side large icons in the cloud storage application. Suppose the user clicks on the large icon (the large icon can also be regarded as a small card) of the photo album application in Interface 101, the content shown in Interface 102 can be displayed, and all the photos uploaded to the cloud by the photo album application are shown in Interface 102. Suppose the user needs to manage the photos, they have to search by swiping in Interface 102, or search for the target photo in the search bar by name. However, since the photos in the photo album application may also come from many sources, they may be downloaded from the chat application, taken by the camera application, copied from other electronic devices via Bluetooth, etc., or copied from other electronic devices such as a computer by file copying, and the types of photos will also be diverse. This may result in the same photos being stored in different folders, and the target photo cannot be found directly using the time axis. This makes it inconvenient to manage the photos.

[0063] Interface 103 and Interface 104 are examples of interfaces of another cloud storage application. Interface 103 is the home page of the cloud storage application. In Interface 103, the capacity of the cloud storage space is also displayed, and the stored capacity of different applications is displayed in a list form. Suppose the user clicks on the corresponding display bar of the photo application in Interface 103, the situation shown in Interface 104 can be seen. It can be seen that Interface 104 is similar to Interface 102. Therefore, there is also the problem that the photos are scattered, complicated and mixed together, which is not easy to manage.

[0064] In view of the above problems, the embodiments of the present application provide a new method for managing cloud data. By adding a new display area to the display interface of the cloud storage application, the data that is most likely to meet the user's management expectations identified by intelligent recognition is centrally displayed, which is convenient for users to manage data more quickly.

[0065] Figure 2 This is a schematic diagram of the interface structure of a cloud storage application according to an embodiment of the present application. As Figure 2 shown, in this interface, it includes the application name of the target application and information on the cloud storage data of the target application, that is, information on the data that the target application synchronously uploads to the cloud. This interface mainly includes a newly added intelligent recognition recommendation management content module (which can also be called the intelligent recognition management area). This interface also includes the content details of the cloud data of the target application. It can be seen that Figure 2 the interface shown Figure 1 compared with the traditional interfaces 102 and 104 in Figure 2 both include the content details of the cloud data of the target application, but

[0066] Figure 3 This is a schematic flowchart of a method for managing cloud data according to an embodiment of the present application. Next, Figure 3 each step will be introduced.

[0067] S301. In the cloud storage application, identify the data to be managed from the data already stored in the cloud storage application by the target application.

[0068] The target application can be any application that can synchronize data to the cloud. For example, it can be a gallery (album, camera, image, or other names equivalent thereto, as long as it is an application used to centrally manage photos and / or videos), notes (which can also be called a memo), music, player, text messages, contacts, file management, etc., and will not be listed one by one.

[0069] In one implementation, the target application includes at least one of the following: gallery, address book (contacts), notes (memo), and file management. The gallery is used to manage photos and / or recorded videos. The address book (contacts) is used to manage at least one of phone numbers, mobile phone numbers, and email addresses. Notes (memo) are used to manage recorded files such as text, pictures, and videos stored by users. File management is used to manage various types of files. In this implementation, the target application is mainly locked in the applications that are most likely to require data management. For example, the gallery is most likely to have various unwanted, duplicate, or blurred photos, the address book is likely to have invalid contact information, there are likely to be blank and invalid notes in the notes, and other files will appear concentrated in file management, and there are likely to be duplicate and redundant files.

[0070] In one example, when the target application includes a gallery, the data to be managed identified includes at least one of the following: screenshots, screen recordings, similar duplicate images, and sensitive photos. Figure 1 Generally, they have relatively strong timeliness and are used for communicating with others or for shopping searches, etc. Most of them are likely to be unwanted later, so they will be regarded as one of the identification objects (which can also be considered as the types of photos to be identified corresponding to the gallery application). Screen recordings also have similar properties to screenshots, so they will also be regarded as one of the identification objects. Moreover, screen recordings take up relatively large storage space, and clearing useless screen recordings can better free up storage space. Similar duplicate images refer to photos with a relatively high similarity rate, which are generally likely to be generated in continuous photo-taking scenarios, or when continuously capturing, or in scenarios where multiple photos are taken to avoid unclear shots, and finally the user may only need to keep the best one, but the synchronous and undifferentiated upload results in all of them being uploaded to the cloud, leading to a waste of storage resources. In addition, if the photo name is changed or redownloaded, it may result in two identical photos being saved, that is, an example of photos that are duplicate but have different source data. Therefore, these similar duplicate photos will be regarded as identification objects. The address book is likely to have invalid contacts, duplicate contacts, blank contacts, etc., so it will also be regarded as an identification object. Sensitive photos mainly refer to photos that are likely to disclose user privacy, such as photos of various certificates like ID cards, passports, student IDs, bank cards, etc. Document photos are mainly photos taken and archived for contracts, agreements, contracts, etc. Privacy photos can be considered as the underlying category of all sensitive photos, and all sensitive photos other than the above can be classified as privacy photos. Therefore, for security reasons, sensitive photos will also be regarded as identification objects.

[0071] In one example, the similar duplicate images include at least one of photos with similar compositions, burst snapshots, and duplicate photos with different source data. Photos with similar compositions are mainly used to screen out photos with high similarity in terms of the overall picture presentation. For example, taking many photos of the same object is one of the possibilities, but it should be understood that although burst photos may result in photos with similar compositions, photos with similar compositions do not necessarily have to be generated only by burst shooting.

[0072] In one example, the sensitive photos include at least one of ID photos, document photos, and privacy photos.

[0073] In one example, when the target application includes an address book, the data to be managed identified includes at least one of the following: duplicate contacts, blank contacts, duplicate address book groups, and blank address book groups.

[0074] In one example, when the target application includes notes, the data to be managed identified includes at least one of the following: blank notes and duplicate notes.

[0075] In one example, when the target application includes file management, the identified data to be managed includes at least one of files with similar or identical names and documents with similar or identical names.

[0076] The recognition method can be implemented by training a neural network model, that is, by labeling some training samples with tags to train the neural network model so that it has the ability to recognize the above-mentioned data to be managed.

[0077] Two neural network models can be set up. One is used to identify all the data to be managed, and the other is used to group and statistically analyze the identified data to be managed, so as to generate the information bars of each of the above-mentioned recognition objects. A neural network model can also be set up for each recognition object respectively to identify the same type of cloud data to be processed from all cloud data. For example, neural network models can be set up for screenshots, similar duplicate images, blank contacts, duplicate notes, etc. respectively, and other recognition objects will not be listed one by one. Neural network models can also be set up at the granularity of the target application, and each neural network model can identify all the cloud data to be processed that need to be recognized under the application and group them.

[0078] S302. Centralize and display the identified data to be managed in the intelligent recognition management area, which is a display area in the cloud storage management interface corresponding to the target application in the cloud storage application.

[0079] When centralizing and displaying, separate statistics and displays can be made according to different data categories. That is, each target application will correspond to at least one data category to be recognized.

[0080] In one implementation, when the identified data to be managed includes screenshots, the above-mentioned centralizing and displaying the identified data to be managed in the intelligent recognition management area includes: displaying the quantity of the identified screenshots and the first management control corresponding to the screenshots in the intelligent recognition management area;

[0081] The above method further includes:

[0082] In response to the user's click operation on the first management control, display the screenshot management interface; in response to the user's management gesture operation in the screenshot management interface, manage the identified screenshots.

[0083] In this implementation, when it is necessary to manage the screenshots, a management control for the screenshots will be set in the centralized intelligent recognition management area, allowing the user to trigger the management of the screenshots through the confirmation operation of the control, and in the screenshot management interface, corresponding management will be carried out by recognizing the user's management gesture operation.

[0084] In one example, the management gesture operations in the screenshot management interface include at least one of a horizontal swipe operation and a drag-to-function identifier operation. The horizontal swipe operation is used to switch the screenshots displayed in the screenshot management interface, and the drag-to-function identifier operation is used to perform the operation corresponding to the function identifier on the screenshot currently displayed in the screenshot management interface. The function identifier includes at least one of archiving and deleting.

[0085] In one example, the management gesture operations in the screenshot management interface include a horizontal swipe operation. In response to the user's management gesture operation in the screenshot management interface, managing the recognized screenshots includes: in response to the user's horizontal swipe operation in the screenshot management interface, displaying the screenshot displayed in the screenshot management interface as the next screenshot corresponding to the sliding direction of the horizontal swipe operation. Assuming the horizontal swipe is a left swipe, it can be understood as switching to the next screenshot. Assuming the horizontal swipe is a right swipe, it can be understood as switching to the previous screenshot.

[0086] In another example, the management gesture operations in the screenshot management interface include a drag-to-archive identifier operation. In response to the user's management gesture operation in the screenshot management interface, managing the recognized screenshots includes: in response to the user's operation of holding and dragging the screenshot to the archive identifier in the screenshot management interface, archiving the screenshot displayed in the screenshot management interface.

[0087] In another example, the management gesture operations in the screenshot management interface include a drag-to-delete identifier operation. In response to the user's management gesture operation in the screenshot management interface, managing the recognized screenshots includes: in response to the user's operation of holding and dragging the screenshot to the delete identifier in the screenshot management interface, deleting the screenshot displayed in the screenshot management interface and displaying the next screenshot.

[0088] Managing screenshots by dragging to a function identifier is a relatively intuitive and friendly interaction method, which can avoid misoperations to a certain extent because the dragging process allows the user to change their mind. Just lifting the hand midway will end this operation, and the user's management participation is higher.

[0089] In another example, the above method further includes: displaying a small picture of each screenshot in the small icon display area in the screenshot management interface; in response to the user's selection operation on any small picture, displaying the large picture of the screenshot corresponding to the small picture in the screenshot management interface. In this example, by setting two areas, namely the small icon display area and the large picture display area, in the screenshot management interface, another way to switch the large pictures is added, and the user has more options.

[0090] In another implementation, when the to-be-managed data identified includes similar duplicate images, when displaying the identified to-be-managed data set in the intelligent recognition management area, it may include: displaying the number of groups of similar duplicate images identified and the second management control corresponding to the similar duplicate images in the intelligent recognition management area;

[0091] The above method further includes:

[0092] In response to a user's click operation on the second management control, display a similar duplicate image management interface; in response to the user's management operation in the similar duplicate image management interface, manage each group of similar duplicate images.

[0093] In this implementation, when it is necessary to manage similar duplicate images, the management control of similar duplicate images will be set in the centrally displayed intelligent recognition management area so that users can trigger the management of similar duplicate images through the confirmation operation of the control, and in the similar duplicate image management interface, corresponding management will be performed by recognizing the user's management operation.

[0094] In one example, the management operations of the similar duplicate image management interface include at least one of the following: a one-key deletion operation, a selection operation, and a sliding switching operation; the one-key deletion operation is a click operation on the one-key deletion control, which is used to delete all selected photos in the current group of similar duplicate images; the selection operation is used to select any one or more similar duplicate images; the sliding switching operation includes a group switching operation and a switching operation of photos within the group.

[0095] In one example, the management operations in the similar duplicate image management interface include a selection operation and a one-key deletion operation. The above-mentioned management of each group of similar duplicate images in response to the user's management operation in the similar duplicate image management interface includes:

[0096] In response to the user's click operation on the selection control in at least one of the similar duplicate images in the current group of similar duplicate images, select at least one similar duplicate image;

[0097] In response to the user's click operation on the one-key deletion control, delete all selected similar duplicate images in the current group of similar duplicate images.

[0098] In this example, it is more convenient by selecting multiple and deleting them with one key.

[0099] In another example, the management operation in the similar duplicate image management interface includes a sliding switching operation, and the sliding switching operation includes a group switching operation and a switching operation of photos within the group; the above-mentioned management of each group of similar duplicate images in response to the user's management operation in the similar duplicate image management interface includes:

[0100] In response to a user's operation of switching the current similar and duplicate image group, switch the current similar and duplicate image group displayed in the similar and duplicate image management interface to the next similar and duplicate image group indicated by the sliding direction of the image group switching operation; or,

[0101] In response to a user's operation of switching photos within a group on a similar and duplicate image that is being displayed in the similar and duplicate image management interface, switch the currently displayed similar and duplicate image to the next similar and duplicate image in the current similar and duplicate image group indicated by the sliding direction of the photo switching operation within the group.

[0102] In one example, the image group switching operation is a vertical swipe, and the photo switching operation within the group is a horizontal swipe.

[0103] In one implementation, when the identified data to be managed includes sensitive photos, display the identified data set to be managed in the intelligent recognition management area, including: displaying the number of identified sensitive photos and the third management control corresponding to the sensitive photos in the intelligent recognition management area;

[0104] The above method further includes: in response to a user's click operation on the third management control, display a sensitive photo management interface; in response to a user's management gesture operation in the sensitive photo management interface, manage the identified sensitive photos.

[0105] In this implementation, when it is necessary to manage sensitive photos, a management control for sensitive photos is set in the centrally displayed intelligent recognition management area to allow the user to trigger the management of sensitive photos through a confirmation operation on the control, and corresponding management is performed by recognizing the user's management operation in the sensitive photo management interface.

[0106] In one example, the management operations in the sensitive photo management interface include at least one of the following: encryption operation, decryption operation, deletion operation, selection operation, and one - key encryption operation; when any sensitive photo is encrypted, the sensitive photo is marked with an encryption mark on the electronic device side, and the image content of the sensitive photo is invisible on the cloud side; the decryption operation is used to cancel the encryption of the sensitive photo; the deletion operation is used to delete the selected photos in the sensitive photo interface; the selection operation is used to select one or more sensitive photos to be processed; the one - key encryption operation is used to encrypt all the selected sensitive photos.

[0107] The above management operations can cooperate with each other to achieve different management purposes. For example, at least one sensitive photo can be selected in response to a selection operation, and then the selected photo can be encrypted in response to a one-key encryption operation or an encryption operation; for another example, at least one sensitive photo can be selected in response to a selection operation, and then the selected photo can be deleted in response to a deletion operation; for another example, at least one encrypted sensitive photo can be selected in response to a selection operation, and then the selected encrypted photo can be decrypted in response to a decryption operation. Other cases will not be listed one by one.

[0108] In another implementation manner, when the target application includes a gallery, the above method further includes: in response to a click operation of the user in the data details display area of the cloud storage management interface corresponding to the gallery in the cloud storage application, displaying a photo aggregation management interface; in response to an aggregation operation of the user on at least one selected target attribute in the photo aggregation management interface, aggregating the photos according to each target attribute in the at least one target attribute.

[0109] In this implementation manner, the photos can be saved by classifying (grouping) them according to a specific one or more target attributes, which is convenient for the user to view later. For example, all the photos taken at a certain tourist attraction can be found. Even if the user has been there many times, the photos taken during multiple trips can be grouped together according to the location attribute. For another example, combining the location and the person can group all the photos of the same person at that location. For example, user A aggregates all the photos of friend B at a certain city on his own electronic device. Other cases will not be listed one by one.

[0110] In one example, the at least one target attribute includes at least one of the following: location, time, person, and object. The location can be set by default in dimensions such as city, POI address (coordinate address), etc. Since there can be one or more persons and objects in the same photo, the user needs to further select which persons and objects. Since the photos on the electronic device are already segmented and displayed according to the time dimension, and the time unit is a day, in the embodiments of the present application, the case where there is only the time target attribute can be not considered.

[0111] In one example, in response to an aggregation operation of the user on at least one selected target attribute in the photo aggregation management interface, aggregating the photos according to each target attribute in the at least one target attribute includes:

[0112] When the target attribute is one, aggregating the photos that meet the target attribute; or,

[0113] When the target attribute is multiple, aggregating the photos that simultaneously meet all the target attributes.

[0114] There can be one or more target attributes, which can be flexibly and freely combined, making the aggregated classification of photos by users more flexible.

[0115] Figure 3 The solution shown mainly identifies the data that needs to be managed in the cloud data of the target application and adds an intelligent recognition management area in the management interface corresponding to the target application for centralized display, facilitating subsequent centralized management of this data of the target application by users in this intelligent recognition management area.

[0116] Figure 4 and Figure 5 are examples of the management interfaces of the cloud storage application in the embodiments of the present application. Figures 6 to 10 Then, examples of the management of screenshots, similar duplicate photos, and sensitive photos are respectively given. Figure 11 and Figure 12 Then, an example of the aggregated classification management of photos is given. The cloud data management in the embodiments of the present application will be introduced below in conjunction with the above respective drawings.

[0117] Figure 4 is a schematic diagram of the management interfaces of the photo gallery and notes in the cloud storage application in the embodiments of the present application. Interface 401 is the home page of the cloud storage application. It can be seen that some basic information of the cloud storage space is displayed therein, including the capacity of the cloud storage space and the used capacity, as well as a bar chart of the respective proportions of the target applications with relatively large proportions in the used capacity. This enables users to relatively intuitively feel the usage of the cloud storage space by different target applications. In the content details section, the home page also displays an information bar for each target application (an application that can synchronously upload data to the cloud). Each information bar includes the icon, name, and data capacity of the target application.

[0118] Assume that the user clicks on the information bar of the gallery application in interface 401, and the target application shown in interface 402, which is the management interface of the gallery, can be seen. In interface 402, that is, the cloud data management interface of the gallery, in addition to including a basic data details list (that is, the area in the lower half that centrally displays all photos by date, which can also be called the data details display area of the gallery in the cloud storage management interface), it also includes an intelligent recognition management area. In the intelligent recognition management area, there are recommendations for several types of photos such as screenshots, screen recordings, similar and duplicate images, and sensitive photos. It can be understood that in the intelligent recognition management area, the recognition results and management controls of these recognition objects, namely screenshots, screen recordings, similar and duplicate images, and sensitive photos, are centrally displayed. The recognition object can be understood as a data object that is recognized to filter out storage data that meets the user's processing expectations. The recognized data to be managed centrally displayed in the intelligent recognition management area here includes 323 screenshots, 57 screen recordings, 12 groups of similar and duplicate images, and 2 sensitive photos. When the user clicks on the management control of any kind of data to be managed in the intelligent recognition management area, the management interface of this kind of data to be managed can be entered. For example, when the user clicks on the management control "Go to clean up" for screenshots, the management interface of screenshots can be entered, and other situations will not be listed one by one.

[0119] It should also be understood that Figures 4 to 12 the specific values in all the interfaces are for illustration purposes to facilitate understanding of the solution and are not restrictive.

[0120] Assume that the user clicks on the information bar of the note application in interface 401, and the target application as shown in interface 403, i.e., the management interface of the note, can be seen. In interface 403, which is the cloud data management interface of the note, in addition to including a basic data details list (i.e., the area in the lower half that centrally displays all notes by date, which can also be referred to as the data details display area of the notes in the cloud storage management interface), it also includes an intelligent recognition management area. In the intelligent recognition management area, there are recommendations for two types of notes to be managed, namely duplicate notes and blank notes. It can be understood that in the intelligent recognition management area, the recognition results and management controls of these two types of notes to be managed, i.e., duplicate notes and blank notes, are centrally displayed. The recognized data to be managed (here are notes to be managed) centrally displayed in this intelligent recognition management area includes 3 duplicate notes and 6 blank notes. When the user clicks on the management control of any type of data to be managed in the intelligent recognition management area, the management interface of this type of data to be managed can be entered. For example, when the user clicks on the management control "Clean up" for the 6 blank notes, the management interface of the blank notes can be entered, and other situations will not be listed one by one. In interface 403, two duplicate notes, "Title 1 Content 1", are exemplified, created on February 12th and February 13th respectively, and these two will be included in the 3 duplicate notes. When the clean-up control of the duplicate notes is clicked, these two duplicate notes can be cleaned up in their management interface. In interface 403, the blank note "Meeting Minutes Blank Content" created on February 13th is also exemplified, and this blank note will be included in the 6 blank notes. When the clean-up control of the blank note is clicked, this blank note can be cleaned up in its management interface.

[0121] Figure 5 It is a schematic diagram of the management interface of the contact application in the cloud storage application in an embodiment of the present application. Interface 401 is the home page of the cloud storage application, and relevant content can be referred to Figure 4 , and will not be elaborated further.

[0122] Suppose the user clicks on the information bar of the Contacts (Address Book) app in interface 401, and the target app as shown in interface 404 can be seen, which is the management interface of the contacts. In interface 404, that is, the cloud data management interface of the contacts, in addition to including a basic data details list (that is, the display area for groups, business cards, and individual contact information in the lower half, which can also be called the data details display area of the contacts in the cloud storage management interface), it also includes an intelligent recognition management area. In the intelligent recognition management area, there are recommendations for photos of two types of items: duplicate items (that is, duplicate contacts) and blank contacts. It can be understood that in the intelligent recognition management area, the recognition results and management controls of these two types of contacts to be managed, namely duplicate contacts and blank contacts, are centrally displayed. The recognized data to be managed (here it is the contact data to be managed) centrally displayed in the intelligent recognition management area includes 5 duplicate items and 12 blank contacts. When the user clicks on the management control of any type of data to be managed in the intelligent recognition management area, the management interface of this type of data to be managed can be entered. For example, when the user clicks on the management control "Clean up" for blank contacts, the management interface for blank contacts can be entered. Other situations will not be listed one by one.

[0123] When users use electronic devices such as mobile phones and tablets in daily life, a large number of screenshots will be generated. Most of them are screenshots that users do not want to keep, but they will also be uploaded to the cloud with cloud synchronization, resulting in waste of storage resources and high cleaning costs. This application groups screenshots through intelligent screening to facilitate centralized processing by users. When users conduct screening and processing, they can quickly slide down to delete screenshots or quickly file the ones they want to keep, improving the management efficiency of users.

[0124] Figure 6It is a schematic diagram of an interaction process for screenshot management according to an embodiment of the present application. Assume that the user clicks on the management control "Go to Clean" for screenshots (which is an example of the first management control) on interface 402, and then can enter the screenshot management interface as shown in interface 405. For the relevant content of interface 402, refer to the above text and will not be elaborated here. Interface 405 includes a small icon display area for screenshots. The small icon of the currently displayed screenshot is framed with a border different from other small icons for distinction, and other distinguishing methods can also be used. Interface 405 also includes a large image display area for displaying a large image of a screenshot to facilitate the user to view more photo details. That is to say, when a large image screenshot is displayed, the small icon of this large image screenshot is marked synchronously in the small icon display area. Interface 405 also includes an editing bar, and there are two function identifiers in the editing bar, namely archiving and deleting. Assume that the user holds and drags the large image of the screenshot towards the delete identifier on interface 405, and then can see the situation shown in interface 406, where a screenshot image that gets smaller as the hand moves is displayed. When continuously holding and dragging, further see the situation shown in interface 407, where the screenshot image displayed following the hand movement is further reduced. Until after dragging to the delete identifier and then lifting the hand to end, the screenshot is deleted, and deleting the screenshot includes deleting both the small icon and the large image.

[0125] Figure 7 It is a schematic diagram of another interaction process for screenshot management according to an embodiment of the present application. Assume that the user clicks on the management control "Go to Clean" for screenshots (which is an example of the first management control) on interface 402, and then can enter the screenshot management interface as shown in interface 405. For the relevant content of interface 402 and interface 405, refer to the above text and will not be elaborated here. Assume that the user holds and drags the large image of the screenshot towards the archive identifier on interface 405, and then can see the situation shown in interface 408, where a screenshot image that gets smaller as the hand moves is displayed. When continuously holding and dragging, further see the situation shown in interface 409, where the screenshot image displayed following the hand movement is further reduced. Until after dragging to the archive identifier and then lifting the hand to end, the screenshot is archived.

[0126] Figure 6 and Figure 7 can be regarded as examples of functional interactions for the screenshot management interface.

[0127] When users find duplicate photos, they usually need to compare them multiple times to determine which photo data to retain. During the comparison process, they often switch directly between multiple pages to view the data, resulting in low operation efficiency. In this application, similar images are grouped together through intelligent screening, and factors such as composition, facial expressions of people, exposure, clarity, and photo size can be further comprehensively considered to select the optimal recommended solution, improving the user's selection efficiency. Visual comparison management is provided for duplicate photos. Users can quickly view the duplicate photos by swiping (for example, swiping horizontally to switch between images within a group and swiping up and down to switch between groups), visually and intuitively compare the duplicate photo data, or perform a one-click deletion operation on the duplicate photos based on the recommended retained data.

[0128] Figure 8 It is a schematic diagram of the management interaction process of similar duplicate images in an embodiment of this application. Assume that the user clicks on the management control "Go to Delete" (an example of the second management control) for similar duplicate images in interface 402, and then can enter the management interface for similar duplicate images, as shown in interface 410. In interface 410, a small icon and a selection result display area are set in the form of a floating window, and there is also a control for one-click deletion of duplicate images in this area. Assume that the user swipes left in the large image display area of interface 410, that is, swipes horizontally to the left, and the displayed image can be switched to the next one, as shown in interface 411. The sliding process follows the movement of the hand. As the distance of the leftward swipe increases, the currently displayed image and the next image to be displayed move leftward as a whole until the situation shown in interface 412 is presented. The image displayed in the large image display area is the next image, and the corresponding icon in the small image display area also switches to the small icon marked as the next image. Figure 8 An example of switching the displayed similar duplicate images by horizontal swiping is given. Through intelligent recognition, the optimal image can be further preferentially placed in the first display on the similar duplicate images, and the advantages of this photo can be marked.

[0129] Figure 9It is a schematic diagram of another management interaction process for similar and duplicate figures in an embodiment of the present application. Assume that the user clicks on the management control "Delete" (an example of the second management control) for similar and duplicate figures in interface 402, and then can enter the management interface for similar and duplicate figures, as shown in interface 413. It can be understood that interface 413 and interface 410 can be the same display interface, both being the management interfaces for similar and duplicate figures. Assume that the user clicks on the check control on the large figure in interface 413, then the currently displayed large figure can be selected, as shown in interface 414. The check control in the large figure display area is shown as selected, and the check control on the small icon corresponding to this large figure in the small icon display area is also shown as selected. Assume that the user clicks on the check controls of at least one small icon in the small icon display area in interface 413, then at least one figure can be selected, as shown in interface 415. Assume that the user clicks on the one-key delete duplicate figure control on interface 145, then all the selected figures can be deleted with one key. Figure 9 Examples of the selection operation and the one-key delete operation are given.

[0130] For the content automatically uploaded to the cloud, there will also be privacy content (such as contract files, ID photos, privacy photos). Without the user's knowledge, it will be automatically downloaded after logging in on other devices, resulting in privacy leakage. The present application provides management recommendations for privacy data, actively reminds the user of the content related to privacy, and can encrypt the privacy data in the cloud to prevent the privacy data in the cloud from being seen when the content is synchronized on other devices, thus protecting the user's data security.

[0131] Figure 10 It is a schematic diagram of the interaction process for managing cloud data of sensitive photos in an embodiment of the present application. Assume that the user clicks on the management control "Encrypt" (an example of the third management control) for sensitive photos in interface 402, and then can enter the management interface for sensitive photos, as shown in interface 416. The user can perform a selection operation in interface 416 to select the sensitive photos to be encrypted, and can also perform a one-key encryption operation to encrypt all the selected sensitive photos. As shown in interface 417, this is the result after encryption. A sensitive photo is marked with an encrypted mark, a small closed lock icon. It should be understood that although the user hopes to encrypt the sensitive photos in the cloud data, directly locking the photos (such as blurring them to be invisible) will cause the user to be unable to view these sensitive photos on the current electronic device. Therefore, using the method of adding an encrypted mark here is more conducive to ensuring that the user can continue to use the photos while also knowing that these photos have been encrypted in the cloud. Encrypting in the cloud means that the details of this photo cannot be seen when viewing the cloud data on any electronic device, and even if this photo is downloaded from the cloud, it cannot be seen.

[0132] Assume that the user is looking for encrypted photos in the local photo gallery application of the electronic device. These encrypted photos will have an encryption mark, as shown in interface 418, which makes them distinguishable from other photos.

[0133] It should also be understood that without the encryption mark for differentiation, the user will not be able to tell whether a photo is encrypted or not.

[0134] When the user needs to manage data with the same attributes scattered in different places in the cloud, and needs to select, edit, and manage the data across different pages, the efficiency is relatively low. Through long - press interaction, the present invention can obtain recommended management attributes of the data through intelligent analysis. The user can select one or more recommended data - attribute combinations, and through a downward - sliding operation (pull - down operation), efficient management of the data set can be carried out (including but not limited to deletion, archiving, etc.), improving the management efficiency of the user for scattered similar data. Moreover, the data attributes can be set as needed, with various attributes freely combined to enrich the management methods. For example, when the location and person attributes are combined, all the photos taken by a certain person or certain people at a certain place can be aggregated. Another example is when the task and object attributes are combined, all the photos taken by a certain person or certain people carrying the same object can be aggregated. For example, if one of the target attributes is a monument, all the photos taken in front of this monument can be aggregated. Other situations will not be listed one by one.

[0135] Figure 11 and Figure 12 FIG. is a schematic diagram of an interaction process for aggregating photos according to an embodiment of the present application. Assume that the user clicks on the data - detail display area of the photo gallery in the cloud - storage management interface in interface 402, and then can enter the function interface for aggregating photos, as shown in interface 419. Interface 419 includes a small - icon display area, a large - photo display area, and an editing bar, and the editing bar includes function identifiers. Assume that the user long - presses on the large photo, and then interface 420 will be shown. In interface 420, the management attributes intelligently recognized from the photo are displayed. Here, the example of recognizing three attributes of location, person, and object is used. Assume that the user clicks and selects at least one management attribute in interface 420, and then the result shown in interface 421 will be presented. Interface 421 shows an example where the selected target attributes are location and person 1.

[0136] Assume that the user performs a pull-down operation in the blank area of the large image in Interface 421 (i.e., the area without management property bubbles), which can trigger an aggregation operation. As shown in Interface 422, small icons and the number of images in the image set under the target property combination will be displayed in the form of a pop-up window. Assume that the user holds and drags this image set to a certain function identifier in Interface 422, and the management operation corresponding to the function identifier can be performed on this image set. Here, taking the example of dragging this image set to the delete identifier, a delete prompt pop-up window shown in Interface 423 will be displayed, instructing the user to further confirm whether to delete the entire image set.

[0137] As can be seen from the above, the solution of the embodiment of the present application realizes the intelligent prediction and centralized display of the data to be managed in the cloud data, facilitating the user's quick management. On this basis, through rich management strategies, a flexible management method is realized. The entire interaction process is friendly and rich and changeable, improving the user's experience.

[0138] In short, the present application provides an efficient management solution for cloud data content, including: intelligently identifying and screening the data to be managed in cloud storage data that users may want to process, such as similar images, useless screenshots, duplicate items, etc., performing quick grouping processing, and editing and managing cloud content through convenient and efficient interactive operations. It helps users efficiently manage cloud data, efficiently clean up useless data, and can protect data privacy and security.

[0139] In the traditional solution, when the user manages cloud data, generally, operations such as searching - selecting / batch selecting - deleting / merging management need to be performed. Usually, searching for the target data will consume a large amount of the user's energy and time cost to find the data scattered in different corners of the cloud. While the present application intelligently identifies cloud data and makes intelligent recommendations for the content that the user wants to process (similar images, useless screenshots, duplicate items), helping the user efficiently and targeted search for and manage the target cloud data, improving the efficiency of the user's management of cloud data. Moreover, the application data that can perform intelligent identification and recommendation management includes but is not limited to: photos (gallery), contacts (address book), memos / notes, files / documents in the network disk (file management).

[0140] The above mainly introduced the method of the embodiments of the present application in combination with the accompanying drawings. It should be understood that although the steps in the flowcharts involved in the above-described embodiments are shown in sequence, these steps are not necessarily executed in the order shown in the figures. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least some of the steps in the flowcharts involved in the above-described embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of the steps or stages in other steps or other steps. The device of the embodiments of the present application will be introduced below in combination with the accompanying drawings.

[0141] Figure 13 It is a schematic diagram of a device for managing cloud data according to an embodiment of the present application. As Figure 13 shown, the device 2000 includes an identification unit 2001 and a processing unit 2002. The device 2000 can be integrated in electronic devices such as mobile phones, tablet computers, and touch-screen laptop computers.

[0142] The device 2000 can be used to execute any of the above methods for managing cloud data. For example, the identification unit 2001 can be used to execute step S301, and the processing unit 2002 is used to execute step S302. The device 2000 can also be used to execute Figures 4 to 12 the interaction process shown.

[0143] In one implementation, the device 2000 may further include a storage unit for storing relevant data. The storage unit can be integrated in any of the above units, or can be a unit independent of all the above units.

[0144] Figure 14 It is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present application. As Figure 14As shown, the electronic device 900 may include a processor 910, an external memory interface 920, an internal memory 921, a universal serial bus (USB) interface 930, a charging management module 940, a power management module 941, a battery 942, an antenna 1, an antenna 2, a mobile communication module 950, a wireless communication module 960, an audio module 970, a speaker 970A, a receiver 970B, a microphone 970C, a headphone interface 970D, a sensor module 980, a key 990, a motor 991, an indicator 992, a camera 993, a display screen 994, and a subscriber identification module (SIM) card interface 995, etc. Among them, the sensor module 980 may include a pressure sensor 980A, a gyroscope sensor 980B, a barometric pressure sensor 980C, a magnetic sensor 980D, an acceleration sensor 980E, a distance sensor 980F, a proximity light sensor 980G, a fingerprint sensor 980H, a temperature sensor 980J, a touch sensor 980K, an ambient light sensor 980L, a bone conduction sensor 980M, etc.

[0145] It can be understood that the structure schematically shown in the embodiments of the present application does not constitute a specific limitation on the electronic device 900. In other embodiments of the present application, the electronic device 900 may include more or fewer components than shown, or combine certain components, or split certain components, or have different component arrangements. The components shown may be implemented in hardware, software, or a combination of software and hardware.

[0146] Exemplarily, Figure 14 The shown processor 910 may include one or more processing units. For example, the processor 910 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0147] Among them, the controller may be the nerve center and command center of the electronic device 900. The controller may generate operation control signals according to the instruction operation code and timing signals to complete the control of fetching instructions and executing instructions.

[0148] A memory may also be provided in the processor 910 for storing instructions and data. In some embodiments, the memory in the processor 910 is a cache memory. This memory can hold the instructions or data that the processor 910 has just used or recycled. If the processor 910 needs to use the instruction or data again, it can be directly called from the said memory. This avoids repeated accesses, reduces the waiting time of the processor 910, and thus improves the efficiency of the system.

[0149] The electronic device 900 implements the display function through the GPU, the display screen 994, and the application processor, etc. The GPU is a microprocessor for image processing, which is connected to the display screen 994 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 910 may include one or more GPUs, which execute program instructions to generate or change the display information.

[0150] The display screen 994 is used to display images, videos, etc. The display screen 994 includes a display panel. In some embodiments, the electronic device 900 may include 1 or N display screens 994, where N is a positive integer greater than 1.

[0151] The electronic device 900 can implement the shooting function through the ISP, the camera 993, the video codec, the GPU, the display screen 994, and the application processor, etc.

[0152] The NPU is a neural-network (NN) computing processor. By drawing on the structure of the biological neural network, such as the transmission pattern between human brain neurons, it can quickly process the input information and can also continuously self-learn. Through the NPU, applications such as intelligent cognition of the electronic device 900 can be realized, such as: image recognition, face recognition, voice recognition, text understanding, etc.

[0153] The pressure sensor 980A is used to sense pressure signals and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 980A may be disposed on the display screen 994. There are many types of pressure sensors 980A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. The capacitive pressure sensor may include at least two parallel plates having conductive materials. When a force acts on the pressure sensor 980A, the capacitance between the electrodes changes. The electronic device 900 determines the intensity of the pressure according to the change in capacitance. When a touch operation acts on the display screen 994, the electronic device 900 detects the intensity of the touch operation according to the pressure sensor 980A. The electronic device 900 can also calculate the position of the touch according to the detection signal of the pressure sensor 980A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities may correspond to different operation instructions. For example, when a touch operation with a touch operation intensity less than the first pressure threshold acts on the short message application icon, the instruction to view the short message is executed. When a touch operation with a touch operation intensity greater than or equal to the first pressure threshold acts on the short message application icon, the instruction to create a new short message is executed.

[0154] It should be noted that, regarding the information interaction, execution process, etc. between the above-mentioned devices / units, since they are based on the same concept as the method embodiments of the present application, for their specific functions and the technical effects brought, reference can be specifically made to the method embodiment part, and details are not described herein again.

[0155] Those skilled in the art can clearly understand that, for the convenience and simplicity of description, only the above-mentioned division of each functional unit and module is used for illustration. In actual applications, the above-mentioned functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device is divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit and module are only for the convenience of mutual distinction and do not limit the protection scope of the present application. The specific working process of the units and modules in the above system can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

[0156] The embodiment of the present application also provides an electronic device, which includes: at least one processor, a memory, and a computer program stored in the memory and executable on the at least one processor. When the processor executes the computer program, the steps in any of the above methods can be implemented.

[0157] An embodiment of the present application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0158] An embodiment of the present application provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0159] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, to implement all or part of the processes in the above-mentioned method embodiments of the present application, a computer program can be used to instruct relevant hardware to complete. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or some intermediate form, etc. The computer-readable medium can at least include: any entity or device that can carry the computer program code to the photographing device / electronic device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium. For example, a USB flash drive, a mobile hard disk, a magnetic disk or an optical disc, etc. In some jurisdictions, according to legislation and patent practice, the computer-readable medium cannot be an electrical carrier signal and a telecommunication signal.

[0160] In the above embodiments, the descriptions of the respective embodiments have their own emphases. For parts not detailed or recorded in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0161] Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be implemented by electronic hardware, or by a combination of computer software and electronic hardware. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. A professional technician can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present application.

[0162] In the embodiments provided in the present application, it should be understood that the disclosed apparatus / devices and methods can be implemented in other ways. For example, the apparatus / device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed coupling or direct coupling or communication connection between each other can be through some interfaces. The indirect coupling or communication connection of the devices or units can be in electrical, mechanical or other forms.

[0163] The units described as separate components may or may not be physically separated. The components displayed as units may or may not be physical units, that is, they can be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0164] It should be understood that when used in the specification of the present application and the appended claims, the term "comprising" indicates the presence of the described features, wholes, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or their combinations.

[0165] It should also be understood that the term "and / or" used in the specification of the present application and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0166] As used in the specification of the present application and the appended claims, the term "if" can be interpreted as "when...", "once", "in response to determining" or "in response to detecting" according to the context.

[0167] In addition, in the description of the specification of the present application and the appended claims, the terms "first", "second", "third", etc. are only used for distinguishing descriptions and cannot be understood as indicating or implying relative importance.

[0168] Reference to "an embodiment" or "some embodiments" etc. described in the specification of this application means that a specific feature, structure or characteristic described in connection with that embodiment is included in one or more embodiments of this application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments" etc. that appear in different places in this specification do not necessarily all refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "comprise", "include", "have" and their variants all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0169] The above-described embodiments are only used to illustrate the technical solutions of this application, rather than to limit them; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A method for managing cloud data, characterized in that, Including: In a cloud storage application, identify data to be managed from the data that the target application has already stored in the cloud storage application; Centrally display the identified data to be managed in an intelligent recognition management area, where the intelligent recognition management area is a display area in the cloud storage management interface corresponding to the target application in the cloud storage application.

2. The method according to claim 1, characterized in that, The target application includes at least one of the following: photo gallery, address book, notes, and file management.

3. The method according to claim 2, characterized in that, When the target application includes a photo gallery, the identified data to be managed includes at least one of the following: screenshots, screen recordings, similar and duplicate pictures, and sensitive photos.

4. The method according to claim 3, characterized in that, The similar and duplicate pictures include at least one of photos with similar compositions, burst shots, and photos that are duplicates but have different source data.

5. The method according to claim 3, characterized in that, The sensitive photos include at least one of ID photos, document photos, and privacy photos.

6. The method according to claim 2, characterized in that, When the target application includes an address book, the identified data to be managed includes at least one of the following: duplicate contacts, blank contacts, duplicate address book groups, and blank address book groups.

7. The method according to claim 2, characterized in that, When the target application includes notes, the identified data to be managed includes at least one of the following: blank notes and duplicate notes.

8. The method according to claim 2, characterized in that, When the target application includes file management, the identified data to be managed includes at least one of files with similar or identical names and documents with similar or identical names.

9. The method according to claim 3, characterized in that, When the identified data to be managed includes screenshots, the central display of the identified data to be managed in the intelligent recognition management area includes: Display the number of identified screenshots and the first management control corresponding to the screenshots in the intelligent recognition management area; The method further includes: In response to a user's click operation on the first management control, display a screenshot management interface; In response to a user's management gesture operation in the screenshot management interface, manage the identified screenshots.

10. The method according to claim 9, characterized in that, The management gesture operations in the screenshot management interface include at least one of a horizontal swipe operation and a drag-to-function identifier operation. The horizontal swipe operation is used to switch the screenshots displayed in the screenshot management interface, and the drag-to-function identifier operation is used to perform the operation corresponding to the function identifier on the screenshot currently displayed in the screenshot management interface. The function identifier includes at least one of archiving and deleting.

11. The method according to claim 9 or 10, characterized in that, The method further includes: Display small pictures of each screenshot in the small picture display area in the screenshot management interface; In response to a user's selection operation on any small picture, display the large screenshot corresponding to the small picture in the screenshot management interface.

12. The method according to claim 3, characterized in that, When the identified data to be managed includes similar and duplicate pictures, the central display of the identified data to be managed in the intelligent recognition management area includes: Display the number of groups of identified similar and duplicate pictures and the second management control corresponding to the similar and duplicate pictures in the intelligent recognition management area; The method further includes: In response to a user's click operation on the second management control, display a similar and duplicate picture management interface; In response to a user's management operation in the similar and duplicate picture management interface, manage each group of similar and duplicate pictures.

13. The method according to claim 12, characterized in that, The management gesture operations of the similar duplicate image management interface include at least one of the following: one-key deletion operation, selection operation, and sliding switching operation; the one-key deletion operation is a click operation on the one-key deletion control, which is used to delete all selected photos in the current similar duplicate image group; the selection operation is used to select any one or more similar duplicate images; the sliding switching operation includes a group switching operation and a switching operation of photos within the group.

14. The method according to claim 3, characterized in that, When the identified data to be managed includes sensitive photos, the centralized display of the identified data to be managed in the intelligent recognition management area includes: Displaying the quantity of the identified sensitive photos and the third management control corresponding to the sensitive photos in the intelligent recognition management area; The method further includes: Responding to the click operation of the user on the third management control to display the sensitive photo management interface; Responding to the management gesture operation of the user in the sensitive photo management interface to manage the identified sensitive photos.

15. According to the method described in claim 14, wherein, The management operations in the sensitive photo management interface include at least one of the following: encryption operation, decryption operation, deletion operation, selection operation, and one-key encryption operation; when any sensitive photo is encrypted, the sensitive photo is marked with an encryption mark on the electronic device side, and the image content of the sensitive photo is invisible on the cloud side; the decryption operation is used to cancel the encryption of the sensitive photo; the deletion operation is used to delete the selected photos in the sensitive photo interface; the selection operation is used to select one or more sensitive photos to be processed; The one-key encryption operation is used to encrypt all selected sensitive photos.

16. According to the method described in any one of claims 1 to 15, wherein, When the target application includes a gallery, the method further includes: Responding to the click operation of the user in the data details display area of the cloud storage management interface corresponding to the gallery in the cloud storage application to display the photo aggregation management interface; Responding to the aggregation operation of the user on at least one selected target attribute in the photo aggregation management interface to aggregate the photos according to each target attribute in the at least one target attribute.

17. According to the method described in claim 16, wherein, The at least one target attribute includes at least one of the following: location, time, person, and object.

18. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein, The processor implements the method according to any one of claims 1 to 17 when executing the computer program.

19. A computer-readable storage medium storing a computer program, wherein, The computer program implements the method according to any one of claims 1 to 17 when executed by the processor.

Images