Data management method and electronic device

Abstract

The application discloses a data management method and an electronic device; wherein the data management method comprises: determining application data corresponding to a plurality of applications from data stored in a plurality of storage locations; the plurality of storage locations represent different data storage locations in a target device; the plurality of applications represent applications installed in the target device; for a target application in the plurality of applications, generating target management information corresponding to the target application by using a target intelligent agent; the target management information represents management information of target application data corresponding to the target application.

Description

Technical Field

[0001] This application relates to, but is not limited to, the field of computer technology, and in particular to a data management method and an electronic device. Background Technology

[0002] Electronic devices generate a large amount of data during the installation and operation of applications. This data is scattered across multiple storage locations on the device, such as the application's private directory, external storage, and public directories, and includes various types of data such as cached data, database data, and configuration data. As a result, users need to examine each storage location containing application data individually to gain a comprehensive understanding of the application's actual data distribution and content, leading to inefficient data management.

[0003] Therefore, improving the efficiency of users' management of application data has become an urgent technical problem to be solved. Summary of the Invention

[0004] In view of this, this application provides at least one data management method and electronic device.

[0005] The technical solution of this application is implemented as follows: On the one hand, this application provides a data management method, which includes: From data stored in multiple storage locations, application data corresponding to multiple applications is determined; multiple storage locations represent different data storage locations in the target device; multiple applications represent applications installed on the target device; For a target application in multiple applications, target management information corresponding to the target application is generated using the target intelligent agent; the target management information represents the management information of the target application data corresponding to the target application.

[0006] On the other hand, this application provides a data management method, which includes: In response to a user's target-triggered operation on the target application installed on the target device, output the target management interface corresponding to the target. Among them, the target application represents the application among multiple applications installed in the target device; the target application data represents the application data determined from data stored in multiple storage locations; and the multiple storage locations represent different data storage locations in the target device. The target management interface represents the user interface determined based on the target management information corresponding to the target application; the target management information represents the management information of the target application data generated by the target agent for the target application.

[0007] In another aspect, this application provides an electronic device, comprising: a memory and at least one processor; wherein the memory is used to store a computer program; and when the processor executes the computer program, it is used to perform at least the following steps: From data stored in multiple storage locations, identify application data corresponding to multiple applications; for target applications among the multiple applications, use target agents to generate target management information corresponding to the target applications; target management information represents management information for target application data corresponding to the target applications; where multiple storage locations represent different data storage locations in the target device; multiple applications represent applications installed on the target device; And / or, In response to a user's target trigger operation on a target application installed on a target device, the target management interface corresponding to the target is output. Here, the target application represents the application among multiple applications installed on the target device; the target application data represents the application data determined from data stored in multiple storage locations; the multiple storage locations represent different data storage locations in the target device; the target management interface represents the user interface determined based on the target management information corresponding to the target application; and the target management information represents the management information generated by the target agent for the target application data corresponding to the target application.

[0008] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of this application. Attached Figure Description

[0009] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this application and, together with the specification, serve to explain the technical solutions of this application.

[0010] Figure 1 A schematic diagram illustrating the implementation process of a data management method provided in this application; Figure 2 A schematic diagram illustrating the implementation process of one embodiment provided in this application; Figure 3 A schematic diagram illustrating the implementation process of a data management method provided in this application; Figure 4 A schematic diagram of the context menu in one embodiment provided in this application; Figure 5 A schematic diagram of the target management interface in one embodiment provided in this application; Figure 6 A schematic diagram illustrating the implementation process of one embodiment provided in this application; Figure 7 This is a schematic diagram of the hardware entity of an electronic device provided in this application. Detailed Implementation

[0011] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application are further described in detail below with reference to the accompanying drawings and embodiments. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0012] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0013] The terms “first / second / third” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first / second / third” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0014] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used herein is for descriptive purposes only and is not intended to limit the scope of this application.

[0015] To address the issue of inefficient application data management, related technologies offer data cleanup functions, such as cleaning cache files by scanning them or accessing deep data using Android Debug Bridge (ADB) commands. However, these solutions are mostly limited to processing specific data types (e.g., only cleaning the cache), lacking an overall understanding of application data and failing to provide application-centric data management.

[0016] Based on this, this application provides a data management method. First, application data corresponding to multiple applications is determined from data stored in multiple storage locations. These multiple storage locations represent different data storage locations on a target device, and the multiple applications represent applications installed on the target device. Then, for a target application among the multiple applications, target management information corresponding to the target application is generated using a target intelligent agent. This target management information represents management information for the target application data corresponding to the target application. In this way, on the one hand, by scanning multiple storage locations to determine the application data corresponding to multiple applications, cross-storage location data aggregation centered on applications is achieved, solving the problem of scattered application data and difficulty in unified management. This provides a data foundation for generating a complete application-centric data view, thereby improving the convenience and accuracy of data management. On the other hand, using a target intelligent agent to generate target management information enables intelligent analysis and management scheme generation for target application data, thereby reducing the cognitive and decision-making burden on users and improving the security and accuracy of data management.

[0017] The technical solutions in the embodiments of this application will now be clearly and completely described with reference to the accompanying drawings.

[0018] Figure 1 This is a schematic diagram illustrating the implementation flow of a data management method provided in this application. In some embodiments, this data management method can be applied to a target device (i.e., a client device) and also to a server device. For example... Figure 1 As shown, the method includes the following steps S11 to S12: Step S11: Determine application data corresponding to multiple applications from data stored in multiple storage locations; the multiple storage locations represent different data storage locations in the target device; the multiple applications represent applications installed in the target device.

[0019] Here, the target device can be any type of device. For example, the target device can be a laptop, tablet, desktop computer, smart TV, set-top box, mobile device (e.g., mobile phone, portable video player, personal digital assistant, dedicated messaging device, portable gaming device), etc.

[0020] In some implementations, the operating system running on the target device can be any type of system. For example, the operating system can be Android, Apple's iPhone Operating System (iOS), iPadOS, HarmonyOS, Windows, etc.

[0021] An application can refer to any application installed and / or running on the target device. In some implementations, an application can be an office application, a network communication application, a multimedia application, a game application, a utility application, or a business-specific application, etc. In some implementations, an application can be a desktop application, a mobile application, or a web application, etc.

[0022] Application data can refer to any data generated during application installation and operation. In some implementations, application data may be the application's installation package, configuration data, business data generated during operation, identity and credential data, log data, or temporary data. In some implementations, application data may be text data, image data, audio data, video data, or multimodal data.

[0023] Application data can be stored in multiple different storage locations. Here, a storage location can be any physical or logical space on the target device that can be used for data storage.

[0024] In some implementations, when the target device is running a Windows operating system, the storage location for storing application data may include: a program installation directory for storing the application itself and static resources, a system public folder for storing global application configurations, public caches, and cross-user shared data, a folder for storing the current user's private application data, and a temporary directory for storing installation decoding files and temporary running files, etc.

[0025] In some implementations, when the target device is running Android, the storage location for storing application data may include: the application's internal private storage space (e.g., a path prefixed with " / data / data / ").<package_name> / "), apply external storage space (e.g., path prefixed with " / sdcard / Android / data / ").<package_name> / ”, and system public shared directories (e.g., paths prefixed with “ / sdcard / Pictures / ”, “ / sdcard / Download / ”, etc.).

[0026] Here, for storage locations with access restrictions, corresponding access permissions need to be requested. For example, for an application's private directory, the user needs to grant permission to "view all files"; another example is that the Scoped Storage API (Scoped Storage Application Programming Interface, Scoped Storage API) can be used to access application data.

[0027] In this way, for each of the above applications, multiple storage locations on the target device can be scanned to identify the application data corresponding to each application.

[0028] In some implementations, for a specific application, multiple storage locations can be scanned based on the application's application identifier to determine data containing that application identifier, and this determined data can be used as the application data for that application. The application identifier can be the application's package name, bundle identifier (Bundle ID), universally unique identifier (UUID), globally unique identifier (GUID), or download link, etc.

[0029] In some implementations, for a specific application, multiple storage locations can be scanned based on the application's name, developer information, version number, and other information to determine the corresponding application data.

[0030] In some implementations, file channels can be used to efficiently traverse multiple storage locations to determine application data for multiple applications.

[0031] In some implementations, after performing data traversal across multiple storage locations, a ContentObserver can be used to monitor data change information. This data change information can include data deletion, data modification, and / or data addition information.

[0032] In some implementations, a WorkManager can be used to periodically perform background scanning tasks.

[0033] Step S12: For the target application in the plurality of applications, use the target agent to generate target management information corresponding to the target application; the target management information represents the management information for the target application data corresponding to the target application.

[0034] A target intelligent agent refers to an intelligent entity capable of autonomously perceiving environmental information, making decisions, and taking actions. Here, target application data corresponding to the target application is input into the target intelligent agent as environmental information, enabling the agent to perform inference based on this data and output target management information. The target intelligent agent can invoke a target model to perform inference. In some implementations, the target intelligent agent and the target model may be programs deployed in the same location, such as both on the target device or both in the cloud. In other implementations, the target intelligent agent and the target model may be programs deployed in different locations, such as the target intelligent agent deployed on the target device and the target model deployed in the cloud.

[0035] Target management information can be any management information related to target application data.

[0036] In some implementations, target management information may be classification information for target application data, enabling users to quickly obtain data types related to the target application. In some implementations, the classification information may include data types and the corresponding data volume for each type. For example, data of type cached data corresponds to a data volume of 85MB; data of type media data corresponds to a storage capacity of 2.1GB; and so on.

[0037] In some implementations, target management information may be action recommendations for target application data. For example, target management information may be deletion or backup recommendations for specified application data.

[0038] The data management method provided in this application firstly identifies application data corresponding to multiple applications from data stored in multiple storage locations. These multiple storage locations represent different data storage locations on the target device, and the multiple applications represent applications installed on the target device. Then, for a target application among the multiple applications, a target intelligent agent is used to generate target management information corresponding to the target application. This target management information represents management information for the target application data corresponding to the target application. In this way, on the one hand, by scanning multiple storage locations to determine the application data corresponding to multiple applications, cross-storage location data aggregation centered on applications is achieved, solving the problem of scattered application data and difficulty in unified management. This provides a data foundation for generating a complete application-centric data view, thereby improving the convenience and accuracy of data management. On the other hand, using a target intelligent agent to generate target management information enables intelligent analysis and management scheme generation for target application data, thereby reducing the cognitive and decision-making burden on users and improving the security and accuracy of data management.

[0039] In some implementations, the method further includes the following step S13: Step S13: Generate a data index for the application data corresponding to each application.

[0040] Here, the data index for application data is structured information used to quickly locate or find the corresponding application data. It is evident that the process of generating a data index involves scanning and organizing application data scattered across different storage locations and establishing a unified data archive.

[0041] In some implementations, the data index can be generated in any manner. In some implementations, the data index of the application data can be determined based on the storage location of the application data (i.e., the data storage path). In some implementations, the data index of the application data can be determined based on information such as metadata, keywords, and / or content summaries of the application data.

[0042] In some implementations, a full scan is performed on the target device when it is first started or when the user actively triggers an application data scan to establish an initial data index. Subsequently, incremental scans are performed on the target device periodically to monitor changes in application data (e.g., using ContentObserver to monitor data changes) to dynamically update the initial data index and ensure the accuracy of the data index.

[0043] In some implementations, the method further includes generating application information for each application and using the application information as a data index for the application; wherein the application information includes the application package name, application name, and application icon.

[0044] In some implementations, the data index corresponding to the target application can be stored in any manner. For example, a lightweight relational database can be used to store the data index corresponding to the target application. For example, the lightweight relational database could be a lightweight Structured Query Language (SQLite) database.

[0045] Thus, the step of generating target management information corresponding to the target application using the target intelligent agent, i.e., step S12 above, can be implemented as the following step S121: Step S121: Based on the data index of the target application data corresponding to the target application, the target management information corresponding to the target application is generated using the target intelligent agent.

[0046] After creating a data index for the target application data, all target application data related to the target application in multiple storage locations can be centrally managed.

[0047] In this way, the data index of the target application data is used as the input information of the target intelligent agent, so as to use the target intelligent agent to analyze the target application data and generate application data management information centered on the target application, that is, target management information.

[0048] In some implementations, the target agent can generate target management information using any suitable method.

[0049] In some implementations, when the data index of the target application data is determined based on the storage location of the target application data, the target agent can generate an overview of the storage location of the target application data based on the data index and use this overview of the storage location as target management information.

[0050] In some implementations, when the data index of the target application data is determined based on the storage location of the target application data, the target agent can find the corresponding target application data based on the storage location in the data index, and then generate target management information based on the metadata, data content, etc. of the target application data.

[0051] In some implementations, when the data index of the target application data is determined based on information such as metadata, keywords, and / or content summaries of the target application data, the target agent can generate target management information corresponding to the target application based on information such as metadata, keywords, and / or content summaries.

[0052] As can be seen from the above, in the embodiments provided in this application, by generating a data index, a unified data view centered on the application can be constructed, thereby helping to improve the efficiency of the target intelligent agent in generating target management information.

[0053] In some implementations, the step of generating target management information corresponding to the target application based on the data index of the target application data corresponding to the target application, using the target agent, that is, step S121 above can be implemented as the following steps S1211 to S1212: Step S1211: Based on the data index of the target application data corresponding to the target application, the importance level of the target application data is determined using the target intelligent agent.

[0054] Importance rating is used to indicate the data value of target application data. In some implementations, importance rating can be used to indicate the degree of impact of target application data on the normal operation of the target application, user data security, and / or the user's experience with the target application. For example, in social applications, chat logs and profile pictures may be rated as high importance, while temporarily downloaded advertising images may be rated as low importance. It is understood that the higher the importance rating of target application data, the higher its data value.

[0055] In some implementations, when using a target agent to determine the importance level of target application data, the agent can look up the corresponding target application data based on a data index, and then determine the importance level of the target application data based on its semantics, data format, metadata, and other information. For example, if the target application data is in the format of an editable document, it is assigned a higher importance level; while if the target application data is a static image, it is assigned a lower importance level. As another example, if the target application data is accessed frequently, it is assigned a higher importance level; while if the target application data is accessed infrequently, it is assigned a lower importance level.

[0056] Step S1212: Based on the importance level, use the target intelligent agent to generate management suggestions for the target application data; the target management information includes management suggestions.

[0057] Management suggestions refer to action recommendations for target application data. In some implementations, management suggestions may include retention suggestions, deletion suggestions, suggestions to prohibit deletion, backup suggestions, and data update suggestions (e.g., document editing suggestions, image enhancement suggestions, etc.).

[0058] Here, after determining the importance level of the target application data, the target agent generates corresponding management recommendations based on that importance level. For example, for user photos or configuration files with a high importance level, the target agent generates recommendations to retain them, prohibit deletion, or back them up; for cached or temporary files with a low importance level, the target agent generates deletion recommendations; and for documents with a high importance level but incomplete content, the target agent can generate data update recommendations.

[0059] In some implementations, the target agent can invoke a target model to determine the importance level of the target application data and generate management recommendations. In some implementations, the target model can be a lightweight classification model.

[0060] As can be seen from the above, in the embodiments provided in this application, by determining the importance level of the target application data and generating corresponding management suggestions based on the importance level, differentiated management of different target application data can be achieved, thereby improving the accuracy of data management. At the same time, by using the target intelligent agent to generate management suggestions, the level of intelligence in data management can be improved, and the cognitive and decision-making burden on users can be reduced.

[0061] In some implementations, the data index includes metadata corresponding to the application data.

[0062] Here, metadata refers to descriptive data about application data. In some implementations, metadata may include the storage location, data volume, data format, access frequency, content summary, content abstract, semantic summary, keywords, and any other information related to the application data.

[0063] Thus, the data index based on the target application data corresponding to the target application, using the target intelligent agent, determines the importance level of the target application data. That is, the above step S1211 can be implemented as the following steps S12111 to S12112: Step S12111: Based on the metadata of the target application data, the target intelligent agent is used to determine the data type of the target application data; the data type is at least used to indicate the business attributes of the corresponding target application data.

[0064] Data type refers to a category label determined after classifying the target application data according to its function or purpose, used to indicate the business attributes of the target application data. In some implementations, data type may include cached data, media data, document data, credential data, configuration data, log data, etc. Among them, cached data is temporary storage data that can be quickly accessed and reconstructed, such as preloaded web pages, to improve data access speed; media data is data that needs to be stored for a long time, such as media content such as images, audio, or video; document data is used to record document-type information created or received by users; configuration data is used to store application running parameters, such as user theme preferences; credential data is used for authentication, such as login tokens. It can be seen that data type not only reflects the physical format of the target application data (e.g., .doc, .pdf, etc.), but also emphasizes the role and function of the target application data in the application logic.

[0065] Here, the target agent determines the data type of the target application data by analyzing various metadata (e.g., storage location, data volume, data format, access frequency, content summary, content abstract, semantic summary, keywords, etc.). For example, for data with the extension ".jpg", although the extension indicates that the data is media data (i.e., image data within media data), because the data is stored in a cache directory, the target agent classifies the data as cached data rather than media data. It is evident that classifying the target application data based on various metadata can improve the accuracy of classification.

[0066] Step S12112: Based on the data type of the target application data, the target agent performs an importance assessment on the target application data to obtain the importance level of the target application data.

[0067] Since data types can be used to indicate the business attributes of the corresponding target application data, importance assessments of target application data can be performed based on data types to evaluate the importance of target application data from the perspective of business attributes (e.g., data usage or function).

[0068] For example, core business data (such as user account information, encryption keys, and application configuration data) should be assigned a higher importance level; partially replaceable data (such as historical chat logs and non-critical images) should be assigned a medium importance level; and temporary data (such as ad caches, webpage caches, and redundant files from automatic backups) should be assigned a lower importance level. As another example, since non-editable document data (such as documents with the ".pdf" extension) is typically fixed content sent to the current user by others, while editable document data (such as documents with the ".doc" extension) is typically updatable content edited by the current user, the importance level of non-editable document data is lower than that of editable document data.

[0069] In some implementations, there is a direct mapping between data types and importance levels. For example, credential data and configuration data typically have the highest security level.

[0070] In some implementations, the importance level of the target application data can be determined by combining its data type, semantic summary, access frequency, data volume, and recoverability. For example, for document data and media data, even if document data contains more semantic content than media data, if the access frequency of document data is extremely low and the access frequency of media data is relatively high, then a lower importance level can be assigned to document data and a higher importance level to media data. As another example, for cached data, even if the data volume is large, because cached data can be regenerated, the importance level assigned to cached data is still relatively low.

[0071] As can be seen from the above, in the embodiments provided by this application, the data type of the target application data is determined according to the metadata of the target application data, and then an importance assessment is performed based on the determined data type. This can achieve accurate classification and differentiated management of the target application data, thereby improving the precision of data management and reducing the risk of users accidentally deleting important data.

[0072] In some embodiments, when the target application data is shared data among multiple applications, the method further includes at least one of the following steps SS1213 and S1214: Step SS1213: The management recommendations corresponding to the target application data do not include deletion recommendations; Step SS1214: Set a shared data identifier for the target application data.

[0073] The target application data is shared data among multiple applications. It represents that the target application data is not only the application data of the target application, but also related to other applications. For example, the target application data may be media data, cache data, configuration data, or credential data of other applications.

[0074] When the target application data is shared across multiple applications, recommending its deletion in the management suggestions for that application could lead to malfunctions or data loss in other applications. For example, an image stored in a public photo album might be created by a camera app and accessed and used by multiple apps such as social media and photo galleries. In this case, recommending the deletion of the image only from the perspective of one app (e.g., a social media app) would cause cross-application data consistency issues. Therefore, when the target application data is shared across multiple applications, the management suggestions generated for that data should not include deletion recommendations.

[0075] Accordingly, if the target application data is shared data among multiple applications, and the user actively deletes the target application data, the system will provide the user with an analysis of the consequences of deleting the target application data.

[0076] When the target application data is shared data among multiple applications, a shared data identifier can be set for the target application data to indicate that it is shared by multiple applications. In some implementations, the shared data identifier can be presented in the user interface as an icon, text tooltip, or highlight mark.

[0077] As can be seen from the above, in the embodiments provided by this application, when the target application data is shared data among multiple applications, by prohibiting the generation of deletion suggestions, the consequences of other applications crashing or malfunctioning due to accidental deletion of target application data can be avoided, thereby improving the security and stability of application operation. In addition, by setting a shared data identifier for the target application data and displaying the shared data identifier in the user interface, clear visual feedback can be provided to the user, helping the user to make reasonable data management decisions. For example, when a user sees a video file with a shared data identifier, they will realize that the video file is shared by multiple applications, and then choose to keep or back up the video file instead of deleting it directly.

[0078] In some implementations, after generating the target management information corresponding to the target application using the target intelligent agent, that is, after step S12 above, the method further includes the following steps S14 to S15: Step S14: Obtain the management operations performed by the user on the target application data based on the target management information.

[0079] Here, after the target management information is determined, it can be output through a user interface or voice, so that users can perform management operations based on the output target management information.

[0080] In some implementations, the management operations performed by the user on the target application data can include any form of operation. In some implementations, the management operations can include deleting the target application data, backing up the data, changing the storage location, marking the target application data as important data, etc.

[0081] In some implementations, when target management information is output through a user interface, the management operations performed by the user can be obtained by listening to the user's interaction with the user interface. For example, when a user clicks on a control used to delete cached data, the click is identified as a management operation; or, when a user manually selects specific media data and backs it up to the cloud, both the selection and the cloud backup operations are identified as management operations.

[0082] In some implementations, when outputting target management information via voice (e.g., using a speaker), the management operation performed by the user can be obtained by listening to the user's voice commands. For example, when a user's voice command to delete cached data is heard, the deletion command is identified as a management operation.

[0083] Step S15: Based on the management operation, update the target model corresponding to the target agent; the target model is used to generate target management information corresponding to the target application.

[0084] The target model refers to the artificial intelligence (AI) analysis engine corresponding to the target intelligent agent. Here, target application data can be used as input information, and the target model can be used to perform data inference to generate target management information corresponding to the target application.

[0085] In some implementations, the target model can determine the data type, importance level, and management recommendations of the target application's data based on the data index corresponding to the target application. In some implementations, the target model can be implemented using a lightweight neural network.

[0086] Here, after obtaining the management operations performed by the user on the target application data, the target model can be updated using the data related to those operations (i.e., the target model can be fine-tuned) to make the updated target model more suitable for the user's personalized needs. For example, if the user frequently cleans up frequently accessed media data, updating the target model based on those management operations can make the target model more inclined to mark frequently accessed media data as deletable data in future data inference; conversely, if the user frequently chooses to retain document data, updating the target model based on those management operations can make the target model assign a higher importance level to document data.

[0087] In some implementations, after a user performs a management operation, information such as the data type and importance level involved in the operation can be extracted, and this extracted information can be added as new samples to the training set of the target model. In some implementations, the target model can be updated through online learning or incremental training.

[0088] As can be seen from the above, in the embodiments provided by this application, updating the target model based on the user's management operations can realize the continuous learning and personalized adaptation of the target model, thereby improving the personalized management effect of application data and enhancing user stickiness.

[0089] Below, in conjunction with Figure 2 An embodiment provided in this application will be described below. Figure 2 As shown, this embodiment includes the following steps S21 to S23: Step S21: Perform a data scan on multiple storage locations in the target device to determine the application data corresponding to each application; then, proceed to step S22. For example, you can scan " / data / data / <package_name> Data in the " / " directory, " / sdcard / Android / data / <package_name> Data in the " / " directory, data in the public storage directory, data in the application database, and application configuration data are used to identify application data belonging to the same application.

[0090] Step S22: For each application, construct the corresponding data index; then, execute step S23. In some implementations, the data index corresponding to the application may include the application information (e.g., application package name, application name, application icon), a list of application data paths, and metadata of the application data (e.g., for data size, modification time, file format, semantic digest, access frequency, etc.).

[0091] Step S23: Analyze the data index corresponding to the target application in multiple applications using the target agent to generate target management information corresponding to the target application.

[0092] In some implementations, when the target agent generates target management information, it may perform the following steps: First, the target application data is identified by data type to distinguish between cached data, media data, document data, configuration data, credential data, etc.; based on the semantic summary of the target application data, content analysis is performed on the target application data to determine the data characteristics (e.g., text semantics, image features, etc.) and identify the data purpose of the target application data; access timestamps of the target application data are obtained, and the access frequency of the target application data is calculated. Then, based on information such as the data type, content analysis results, and access frequency of the target application data, an importance assessment is performed on the target application data to determine its importance level. Then, based on the data type, content analysis results, access frequency, and importance level of the target application data, management suggestions are generated for the target application data. For example, deletion suggestions are generated for cached data; retention suggestions are generated for user photos with high importance levels; and suggestions to prohibit deletion are generated for core data (e.g., login credentials); and so on.

[0093] As can be seen from the above, the data management method provided in this application, on the one hand, determines the application data corresponding to multiple applications by scanning multiple storage locations, realizing cross-storage location data aggregation centered on applications, solving the problem of scattered application data and difficulty in unified management, providing a data foundation for generating a complete data view centered on applications, thereby improving the convenience and accuracy of user data management; on the other hand, it supports unified management of private directories, external storage, and public target data, thereby realizing deep data perception; furthermore, by generating data indexes corresponding to applications, a unified data view centered on applications is constructed, thereby improving the efficiency of target intelligent agents in generating target management information; finally, by using target intelligent agents to automatically identify the importance level of application data, intelligent analysis of application data can be achieved, reducing the cognitive and decision-making burden on users.

[0094] This application also provides a data management method. In some embodiments, this data management method can be applied to a target device (i.e., a client device). For example... Figure 3 As shown, the data management method includes the following steps S31: Step S31: In response to the user's target trigger operation on the target application installed on the target device, output the target management interface corresponding to the target. Wherein, the target application represents an application among multiple applications installed on the target device; the target application data represents application data determined from data stored in multiple storage locations; and the multiple storage locations represent different data storage locations in the target device; The target management interface represents a user interface determined based on the target management information corresponding to the target application; the target management information represents management information generated using the target agent for the target application data corresponding to the target application.

[0095] Here, the target management interface refers to the user interface determined by the target device based on the target management information corresponding to the target application after obtaining the user's target trigger operation. The specific implementation method for generating target management information using the target intelligent agent can be found in the detailed description of any embodiment described above in conjunction with steps S11 to S12, S13, S121, S1211 to S1212, S12111 to S12112, S1213, or S1214, and steps S14 to S15; it will not be repeated here.

[0096] The target trigger operation can be any operation used to trigger data management.

[0097] In some implementations, the target triggering operation can be a specified action performed by the user on the application icon of the target application through a cursor or the touchscreen of the target device. For example, the user may perform a click, swipe, or other specified gesture on the application icon through a cursor or the touchscreen of the target device.

[0098] In some implementations, the target triggering action can be a voice command issued by the user. For example, the user's target triggering action is determined when the user's voice is detected as "manage application data for the video application".

[0099] In this way, after obtaining the user's trigger operation, the target management information corresponding to the target application is determined, and then the target management interface is generated based on the target management information and the preset data management interface template.

[0100] As can be seen from the above, in the embodiments provided by this application, in response to a user's target trigger operation on a target application installed on a target device, a target management interface corresponding to the target is output. In this way, on the one hand, the target management interface provides users with a unified data management view, realizing application-centric data management and solving the problem of scattered and difficult-to-manage application data, thereby improving the convenience and accuracy of data management; on the other hand, since the target management information is generated using the target intelligent agent, intelligent analysis and management scheme generation of application data are realized, thereby reducing the user's cognitive and decision-making burden, while improving the security and accuracy of data management.

[0101] In some embodiments, the method further includes steps S32 to S33: Step S32: In response to the user's first trigger operation on the application icon and / or application name of the target application, display the context menu of the target application; the context menu includes a data management item.

[0102] Here, an application icon refers to a user interface component that is bound to interactive logic. As you can see, users can interact with the corresponding application through the application icon. In some implementations, the application icon of the target application can be displayed on the target device's system desktop, application launch menu or start menu, taskbar or status bar, folder, lock screen, negative one screen, widget area, file manager, resource manager, communication center, pop-up window, or any other location on the target device.

[0103] An application name is a text element that is associated with an application and has interactive logic. As can be seen, similar to an application icon, users can interact with the corresponding application through its name. In some implementations, the application name of the target application can be displayed on the target device's system desktop, application list, taskbar, desktop widget, application entry within a folder, or any other arbitrary location.

[0104] The first triggering action can be any action used to trigger the display of the context menu. In some implementations, the first triggering action can be any action such as a long press, double tap, swipe, or hover. The specific form of the first triggering action depends on the device type and operating system of the target device. For example, on an Android phone, the first triggering action can be a long press; on a tablet or desktop, the first triggering action can be a right-click or touch gesture.

[0105] In this way, in response to the first trigger operation, the context menu of the target application is displayed to quickly expose the function entry point.

[0106] The target application's context menu includes data management items. Here, data management items refer to the function options in the context menu, used to guide users to the target application's data management interface.

[0107] In some implementations, data management items may be presented as text labels, such as "Data Management," for quick user access. In some implementations, data management items may be presented as data management icons. In some implementations, the data management items in the context menu may also display the total data volume of the target application, such as 1.2GB, to give users a clear understanding of the target application's data size.

[0108] like Figure 4 As shown, in one embodiment provided in this application, the context menu 400 of the target application may include: Application name area 410 is used to display the application name of the target application; in some embodiments, application name area 410 may also display the application icon of the target application. Item 420, "Open", is used to launch the target application; The “Application Information” item 430 is used to display the application information of the target application; The “Data Management” item 440 is used to launch the data management interface and display the total data volume of the target application (i.e., 1.2GB).

[0109] Step S33: In response to the user's second trigger operation for the data management item, determine the user's target trigger operation for the target application.

[0110] The second trigger action refers to the interactive action performed by the user on a data management item to confirm entry into the data management interface. In some implementations, the second trigger action can be a click action, a long press action, a swipe action, or any other action method that conforms to the user's interaction habits.

[0111] Here, after obtaining the second triggering operation performed by the user, the target triggering operation for the target application is determined, that is, the first and second triggering operations performed by the user are taken as the target triggering operations.

[0112] As can be seen from the above, in the embodiments provided by this application, by setting a data management item in the context menu, users can enter the target management interface of the target application through two operations (i.e., the first trigger operation and the second trigger operation), which significantly reduces the complexity of operation and improves the efficiency of data management and the user experience.

[0113] In some implementations, the target management interface includes at least one of the following: The quantity and / or volume of the target application data; The data index of the target application data; The amount of target application data corresponding to each data type; wherein, the data type is determined using the target agent and based on the data index of the target application data, and the data type is at least used to indicate the business attributes of the corresponding target application data; the data index includes the metadata of the corresponding target application data.

[0114] Here, the number of target application data refers to the total number of target application data items identified after scanning multiple storage locations on the target device. For example, the number of target application data items is 1000.

[0115] The data volume of the target application data refers to the amount of storage space occupied by the target application data. In some implementations, the data volume of the target application data may refer to the total data volume corresponding to the target application, or it may refer to the data volume of a specific target application.

[0116] In some implementations, the total data volume of the target application data corresponding to each data type can be displayed using the target management interface. For example, the total data volume corresponding to cached data, the total data volume corresponding to media data, and the total data volume corresponding to configuration data. The specific implementation method for determining the data type corresponding to the target application data can be found in the detailed explanation above in conjunction with step S12111, and will not be repeated here.

[0117] The data index for the target application data, as described above, is structured data established for the target application data, at least for quickly locating the target application data. In some implementations, the target management interface can display arbitrary information such as the storage location (i.e., file path), data format, access frequency, semantic summary, keywords, and modification time of the target application data.

[0118] In some implementations, the target management interface also includes an intelligent suggestion area. This intelligent suggestion area is used to output deletable data recommended by the target agent.

[0119] Meanwhile, the target management interface includes at least one operation control to support user management operations on target application data. For example, the target management interface may include a control for implementing a deletion selection function, allowing the user to select the application data to be deleted based on the control; another example is that for the deletable data recommended by the target agent, a control for implementing a one-click cleanup function may be displayed; yet another example is that for application data with a high level of importance, a control for implementing data backup may be displayed.

[0120] As can be seen from the above, in the embodiments provided in this application, by outputting the quantity and / or volume of target application data in the target management interface, the overall data scale of the target application can be clearly presented, thereby assisting users in determining whether data cleaning or optimization needs to be performed, and thus improving data management efficiency; by outputting the volume of target application data corresponding to each data type in the target management interface, the target application data classified by business attributes can be visualized, thereby guiding users to perform targeted application data management; by outputting the data index of target application data in the target management interface, a structured and searchable view of target application data can be provided to users, thereby supporting refined target application data filtering and management, and enhancing users' control over target application data.

[0121] like Figure 5 As shown, in one embodiment provided in this application, the target management interface 500 includes the following information: Application information area 510 is used to display the application information of the target application, including the application icon, application name, total data volume, and total number of data items of the target application; The intelligent analysis area 520 is used to display management suggestions generated by the target intelligent agent, such as the amount of data that can be cleaned up to 856MB, and provides a "one-click cleanup" control; Data type area 530 is used to display the various data types corresponding to the target application, and the total data volume corresponding to each data type; among them, the data volume corresponding to cached data is 892MB, the data volume corresponding to media data is 234MB, the data volume corresponding to document data is 56MB, and the data volume corresponding to temporary data is 18MB.

[0122] Below, in conjunction with Figure 6 An example of user-managed data will be described. Figure 6 As shown, this embodiment includes the following steps S61 to S63: Step S61: In response to the user's long press operation on the target application's icon, display the target application's context menu; then, execute step S62. Here, the context menu of the target application can be as follows: Figure 4 As shown.

[0123] Step S62: In response to the user's click operation on the data management item in the context menu, the target management interface corresponding to the target application is displayed; then, step S63 is executed. Here, the target management interface corresponding to the target application can be viewed as follows: Figure 5 As shown.

[0124] Step S63: Obtain the user's operation actions on the target management interface, and perform corresponding data management based on the user's operation actions.

[0125] For example, when the user clicks Figure 5 When using the "One-Click Cleanup" control shown, first, a data deletion operation is performed; then, the data index of the target application is updated, and the target management interface is updated.

[0126] In some implementations, when a user performs a deletion operation on target application data, a preview of the corresponding target application data is output so that the user can confirm whether to delete the data, reducing accidental deletion. For example, a semantic summary of document data, a preview image of image data, or key video clips of video data can be output.

[0127] In some implementations, after a user performs a deletion operation on the target application data, the deleted target application data can be backed up to the cloud so that the accidentally deleted data can be recovered.

[0128] For example, users' views on Figure 5 When performing a backup operation on the document data shown, firstly, the document data selected by the user is packaged; then, the packaged document data is copied to the backup data storage location specified by the user; finally, the backup operation is recorded in the log file corresponding to the target application.

[0129] In some implementations, users can be proactively reminded to perform data management based on a user-defined or default time period. In other implementations, users can be proactively reminded to perform data management based on the frequency with which they manage application data.

[0130] As can be seen from the above, the data management method provided by this application, on the one hand, provides users with a convenient data management entry through the application's context menu, which can reduce the complexity of user operations; on the other hand, it provides users with a unified data view centered on the application through the target management interface, which allows users to quickly view and manage application data, thereby improving data management efficiency.

[0131] Based on the foregoing embodiments, this application provides an electronic device. For example... Figure 7 As shown, an electronic device 700 includes: a memory 710 and at least one processor 720; wherein, the memory 710 is used to store a computer program; when the processor 720 executes the computer program, it is used to perform at least the following steps: From data stored in multiple storage locations, application data corresponding to multiple applications is determined; for a target application among the multiple applications, target management information corresponding to the target application is generated using a target agent; the target management information represents management information for the target application data corresponding to the target application; wherein, the multiple storage locations represent different data storage locations in the target device; the multiple applications represent applications installed in the target device; And / or, In response to a user's target trigger operation on a target application installed on a target device, a target management interface corresponding to the target is output; wherein, the target application represents an application among multiple applications installed on the target device; the target application data represents application data determined from data stored in multiple storage locations; the multiple storage locations represent different data storage locations in the target device; the target management interface represents a user interface determined based on the target management information corresponding to the target application; the target management information represents management information generated using the target agent for the target application data corresponding to the target application.

[0132] In some embodiments, the processor 720 is configured to: For each application, a data index is generated for the application data. Based on the data index of the target application data corresponding to the target application, the target intelligent agent is used to generate target management information corresponding to the target application.

[0133] In some embodiments, the processor 720 is configured to: Based on the data index of the target application data corresponding to the target application, the importance level of the target application data is determined using the target intelligent agent; Based on the importance level, the target intelligent agent generates management recommendations for the target application data; the target management information includes the management recommendations.

[0134] In some implementations, the data index includes metadata corresponding to the application data; The processor 720 is used for: Based on the metadata of the target application data, the data type of the target application data is determined using the target intelligent agent; the data type is at least used to indicate the business attributes of the corresponding target application data. Based on the data type of the target application data, the target agent performs an importance assessment on the target application data to obtain the importance level of the target application data.

[0135] In some implementations, when the target application data is shared data among multiple applications, the processor 720 is configured to perform one of the following: The management recommendations for the target application data do not include deletion recommendations; Set a shared data identifier for the target application data.

[0136] In some embodiments, the processor 720 is configured to: Obtain the management operations performed by the user on the target application data based on the target management information; Based on the management operation, the target model corresponding to the target agent is updated; the target model is used to generate target management information corresponding to the target application.

[0137] In some embodiments, the processor 720 is configured to: In response to a user's first trigger action on the application icon and / or application name of the target application, a context menu of the target application is displayed; the context menu includes a data management item. In response to a second triggering action by the user for the data management item, a target triggering action by the user for the target application is determined.

[0138] In some implementations, the target management interface includes at least one of the following: The quantity and / or volume of the target application data; The data index of the target application data; The amount of target application data corresponding to each data type; wherein, the data type is determined using the target agent and based on the data index of the target application data, and the data type is at least used to indicate the business attributes of the corresponding target application data; the data index includes the metadata of the corresponding target application data.

[0139] The descriptions of the above device embodiments are similar to those of the above method embodiments, and have similar beneficial effects. In some embodiments, the functions or modules included in the device provided in this application can be used to perform the methods described in the above method embodiments. For technical details not disclosed in the device embodiments of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0140] The above description is merely an embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A data processing method, comprising: Determine application data corresponding to multiple applications from data stored in multiple storage locations; The multiple storage locations represent different data storage locations in the target device; The multiple applications represent the applications installed in the target device; For the target application in the multiple applications, target management information corresponding to the target application is generated using the target intelligent agent; The target management information represents the management information for the target application data corresponding to the target application.

2. The method according to claim 1, further comprising: For each application, a data index is generated for the application data. The step of generating target management information corresponding to the target application using the target intelligent agent includes: generating target management information corresponding to the target application using the target intelligent agent based on the data index of the target application data corresponding to the target application.

3. The method according to claim 2, wherein generating target management information corresponding to the target application based on the data index of the target application data corresponding to the target application, using the target agent, includes: Based on the data index of the target application data corresponding to the target application, the importance level of the target application data is determined using the target intelligent agent; Based on the importance level, the target intelligent agent is used to generate management recommendations for the target application data; The target management information includes management recommendations.

4. The method according to claim 3, wherein the data index includes metadata corresponding to the application data; The data index based on the target application data corresponding to the target application, using the target intelligent agent, determines the importance level of the target application data, including: Based on the metadata of the target application data, the data type of the target application data is determined using the target intelligent agent; The data type is at least used to indicate the business attributes of the corresponding target application data; Based on the data type of the target application data, the target agent performs an importance assessment on the target application data to obtain the importance level of the target application data.

5. The method according to claim 3, wherein when the target application data is shared data among multiple applications, the method further comprises at least one of the following: The management recommendations for the target application data do not include deletion recommendations; Set a shared data identifier for the target application data.

6. The method according to any one of claims 1 to 5, after generating the target management information corresponding to the target application using the target intelligent agent, it further includes: Obtain the management operations performed by the user on the target application data based on the target management information; Based on the management operation, update the target model corresponding to the target agent; The target model is used to generate target management information corresponding to the target application.

7. A data management method, comprising: In response to a user's target trigger operation on a target application installed on a target device, the target management interface corresponding to the target is output; Wherein, the target application represents an application among multiple applications installed on the target device; the target application data represents application data determined from data stored in multiple storage locations; and the multiple storage locations represent different data storage locations in the target device; The target management interface represents a user interface determined based on the target management information corresponding to the target application; the target management information represents management information generated using the target agent for the target application data corresponding to the target application.

8. The method according to claim 7, further comprising: In response to a user's first trigger action on the application icon and / or application name of the target application, display and output the context menu of the target application; The context menu includes data management items; In response to a second triggering action by the user for the data management item, a target triggering action by the user for the target application is determined.

9. The method according to claim 7, wherein the target management interface includes at least one of the following: The quantity and / or volume of the target application data; The data index of the target application data; The amount of target application data corresponding to each data type; where, The data type is determined using the target intelligent agent and a data index based on the target application data, and the data type is at least used to indicate the business attributes of the corresponding target application data; the data index includes the metadata of the corresponding target application data.

10. An electronic device, comprising: A memory and at least one processor; wherein the memory is used to store a computer program; and the processor, when executing the computer program, is used to perform at least the following steps: From data stored in multiple storage locations, application data corresponding to multiple applications is determined; for a target application among the multiple applications, target management information corresponding to the target application is generated using a target agent; the target management information represents management information for the target application data corresponding to the target application; wherein, the multiple storage locations represent different data storage locations in the target device; the multiple applications represent applications installed in the target device; And / or, In response to a user's target trigger operation on a target application installed on a target device, a target management interface corresponding to the target is output; wherein, the target application represents an application among multiple applications installed on the target device; the target application data represents application data determined from data stored in multiple storage locations; the multiple storage locations represent different data storage locations in the target device; the target management interface represents a user interface determined based on the target management information corresponding to the target application; the target management information represents management information generated using the target agent for the target application data corresponding to the target application.

Images