File management method, electronic equipment and readable storage medium

Abstract

The invention discloses a file management method, electronic equipment and a readable storage medium, and belongs to the technical field of electronic equipment. The method comprises the following steps: in response to first input of at least one file, compressing the at least one file to obtain a compressed file; generating first naming information of the compressed file based on the file content of the at least one file; and naming the compressed file according to the first naming information.

Description

Technical Field

[0001] This application belongs to the field of electronic equipment technology, specifically relating to a file management method, an electronic device, and a readable storage medium. Background Technology

[0002] In existing file management systems, users often need to compress multiple files into a single compressed file for storage or transfer. However, existing compression tools typically use default naming rules, such as generating compressed filenames based on the current date and time, which fails to accurately reflect the contents of the compressed file. This leads to difficulties for users in managing and finding compressed files later, while manually entering filenames is cumbersome. Clearly, the naming method for compressed files often struggles to balance accuracy and ease of use. Summary of the Invention

[0003] The purpose of this application is to provide a file management method, electronic device, and readable storage medium that can solve the problem of balancing the accuracy of compressed file naming and the portability of operation.

[0004] In a first aspect, embodiments of this application provide a file management method, the method comprising: In response to a first input of at least one file, the at least one file is compressed to obtain a compressed file; Generate the first naming information of the compressed file based on the file content of at least one file; Name the compressed file according to the first naming information.

[0005] Secondly, embodiments of this application provide a file management device, the device comprising: A compression module is used to compress at least one file in response to a first input of at least one file to obtain a compressed file; The generation module is used to generate the first naming information of the compressed file based on the file content of at least one file. The naming module is used to name the compressed file based on the first naming information.

[0006] Thirdly, embodiments of this application provide an electronic device including a processor and a memory, wherein the memory stores programs or instructions executable on the processor, and the programs or instructions, when executed by the processor, implement the steps of the method described in the first aspect.

[0007] Fourthly, embodiments of this application provide a readable storage medium on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect.

[0008] Fifthly, embodiments of this application provide a chip, the chip including a processor and a communication interface, the communication interface being coupled to the processor, the processor being used to run programs or instructions to implement the method as described in the first aspect.

[0009] In a sixth aspect, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the method described in the first aspect.

[0010] In this embodiment, in response to a first input of at least one file, at least one file is compressed to obtain a compressed file; based on the file content of at least one file, first naming information of the compressed file is generated; and the compressed file is named according to the first naming information. Thus, by automatically generating the first naming information of the compressed file based on the file content, the filename accurately reflects the file content, facilitating quick identification and management of compressed files by users, effectively reducing the burden of manual naming by users, balancing the accuracy of compressed file naming with operational portability, and improving the overall efficiency of file management. Attached Figure Description

[0011] Figure 1 This is a flowchart illustrating a file management method provided in some embodiments of this application; Figure 2 This is one of the interface diagrams of the file management method provided in some embodiments of this application; Figure 3 This is a second schematic diagram of the interface of the file management method provided in some embodiments of this application; Figure 4 This is the third schematic diagram of the interface of the file management method provided in some embodiments of this application; Figure 5 This is the fourth schematic diagram of the interface of the file management method provided in some embodiments of this application; Figure 6 These are schematic diagrams of the structure of a file management device provided in some embodiments of this application; Figure 7 These are schematic diagrams of the structure of electronic devices provided in some embodiments of this application; Figure 8 These are schematic diagrams of the hardware structure of electronic devices provided in some embodiments of this application. Detailed Implementation

[0012] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0013] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0014] The file management method provided in this application will be described in detail below with reference to the accompanying drawings, through specific embodiments and application scenarios.

[0015] Figure 1 This is a flowchart illustrating the file management method provided in an embodiment of this application. The file management method may include: Step 101: In response to the first input of at least one file, compress at least one file to obtain a compressed file.

[0016] In step 101, a user's first input on at least one file can be received. This first input can be a click on the file, a voice command, or a specific gesture. The specific gesture can be determined based on actual usage needs, and this embodiment does not limit this. The specific gesture in this embodiment can be any one of a single-click gesture, a swipe gesture, a drag gesture, a pressure-recognition gesture, a long-press gesture, an area-change gesture, a double-press gesture, or a double-tap gesture. The click input in this embodiment can be a single-click input, a double-tap input, or any number of clicks, and can also be a long-press input or a short-press input.

[0017] In response to the first input, at least one file can be compressed to obtain a compressed file.

[0018] For example, in one scenario, when a user opens a file management application on their electronic device, the application interface can display a file list. The user can then long-press to select one or more files that need to be compressed. These files can be text, images, spreadsheets, etc., without specific limitations. After selection, an operation menu will pop up on the application interface. The user can then click the "Compress" button in the operation menu to trigger the compressed file generation process.

[0019] Step 102: Generate the first naming information of the compressed file based on the file content of at least one file.

[0020] In step 102, after triggering the compressed file generation process, the file management application can automatically start the intelligent naming function in the background. That is, the intelligent naming function will automatically perform in-depth understanding and analysis of the file content of all files to be compressed, and automatically generate the first naming information of the compressed file based on the file content.

[0021] Understandably, the number of characters in the first naming information can be preset, for example, the number of characters in the first naming information can be limited to 8 to 10 characters to avoid the name being too long.

[0022] For example, if you select travel photos and guides for location A and compress them, the first name of the compressed file can be "Travel Data Package for Location A" or "Travel Collection of Location A in XX Year", etc.

[0023] The first naming information can be one or more (i.e., at least two), and no specific limitation is made here.

[0024] Step 103: Name the compressed file according to the first naming information.

[0025] In step 103, the compressed file can be named based on the automatically generated first naming information. For example, the first naming information can be directly entered in the naming input box of the compressed file. After compression, the resulting compressed file can be saved to the specified folder according to the first naming information.

[0026] In this embodiment, the file management method, in response to a first input of at least one file, compresses the at least one file to obtain a compressed file; generates first naming information for the compressed file based on the content of the at least one file; and names the compressed file according to the first naming information. Thus, by automatically generating the first naming information for the compressed file based on its content, the method ensures that the filename accurately reflects the file content, facilitating quick identification and management of compressed files by users. It also effectively reduces the burden of manual naming for users, balancing the accuracy of compressed file naming with ease of operation, thereby improving the overall efficiency of file management.

[0027] In some examples, because the naming information of compressed files generated by the intelligent naming function usually contains core content keywords, it can be deeply integrated with the search function of file management applications. When a user searches for "XX project" in a file management application, the system can not only find individual files with "XX project" in their name, but also accurately locate compressed files generated by the intelligent naming function with the naming information "XX project full process data", avoiding the problem of compressed files not being searchable due to vague naming.

[0028] In other examples, when users share compressed files through file management applications, the clear names generated by the intelligent naming feature can directly improve sharing efficiency. For instance, if a user shares "XX Year Q3 Marketing Department Activity Package" with a colleague, the colleague can immediately understand from the name that the compressed file contains information related to the marketing department's Q3 activities without needing to ask. If sharing "XX Year Location A Travel Collection" with family members, they can quickly identify it as travel-related files based on the name, avoiding communication costs caused by ambiguous names. This makes compressed files "self-explanatory" in sharing scenarios, improving the efficiency of cross-user file transfers.

[0029] In other examples, when users compress files containing duplicates, such as multiple versions of the same document or similar images, the intelligent naming function can first use the duplicate file identification function of the file management application to determine the proportion of duplicates in the file to be compressed, and then generate a name based on the non-duplicate content. For example, if the file to be compressed contains "Product Solution V1", "Product Solution V2", "Final Version of Product Solution" and 3 duplicate product illustrations, it can identify "Product Solution" as the core content and the presence of multiple versions and duplicate images. The generated compressed file name information is "Multiple Versions of Product Solution + Illustrations", helping users quickly understand the characteristics of the compressed file containing "multiple versions of documents + duplicate images" through the name. During subsequent organization, targeted deduplication operations can be performed to improve the clarity of the compressed file content.

[0030] It is understood that this application's embodiments fill the gap in the field of intelligent naming of compressed files in existing applications by adding intelligent naming functionality to file management applications, upgrading the application from a "basic file management tool" to a "highly efficient management platform with AI-assisted capabilities." Through the intelligent naming function, when a user triggers a compression operation in the file management application, the system automatically collects, analyzes, and generates naming suggestions for the file to be compressed. Users are not required to return to view the file content, manually organize information, or think about naming; the system directly provides users with a precise summary title within a limited character limit as naming information, effectively reducing operation steps and saving operation time.

[0031] The intelligent naming feature not only covers various file types such as text, images, and tables, but also generates differentiated naming information based on file content. Compared to traditional single compression functions, it better meets users' needs for refined file management. When searching for compressed files later, users can quickly locate the target file by using a name that closely matches the content, avoiding difficulties in finding files due to ambiguous naming, thereby increasing user engagement with the file management application.

[0032] Furthermore, the analysis and generation of naming information is performed locally on the electronic device, without uploading the content data of the files to be compressed to the cloud, thus avoiding the risk of data leakage at the source. The collected file content can also be processed using encryption algorithms, and the dataset is deleted immediately after processing to ensure file privacy and security.

[0033] In some embodiments, generating first naming information for a compressed file based on the file content of at least one file may include: Based on the file content of at least one file, and at least one of the metadata of the at least one file and the naming convention information of historical compressed files, generate the first naming information of the compressed file; In some embodiments, metadata includes at least one of file type, file storage path, and file modification time.

[0034] In this embodiment, the first naming information may consider not only the file content, but also metadata such as file type, file storage path, and file modification time.

[0035] Taking file type metadata as an example, when a user selects multiple file types in a file management application, such as text + images + tables, for compression, the intelligent naming function can further identify the proportion and relationship between file types, generating more accurate and differentiated names. For example, if 80% of the file to be compressed is images and 20% is text guides, the system will prioritize image attributes, generating "XX Scene Images + Guide Package," such as "A Location Travel Images + Guide Package." If the files are "Product Manual.pdf," "Product Design Drawing.png," and "Product Parameter Table.xlsx," the system will identify the core theme of "product" and the type combination of "document + image + table," generating "XX Product Full-Dimensional Data." In this way, the naming information of compressed files can both reflect the core content and clearly define the file type composition, allowing users to quickly determine whether the compressed file contains the file types they need.

[0036] Taking metadata, including file storage paths, as an example, the intelligent naming function can link the file storage path information of the file management application and combine it with the folder names in the path to assist in generating names. For example, if a user selects multiple files to compress in the "Work / Marketing Department / 2024Q3 Activities" folder in the file management application, the system will read the "Marketing Department" and "2024Q3 Activities" information in the path. If the file content is event planning or promotional materials, the first name generated will be "2024Q3 Marketing Department Activity Package". As another example, if a user compresses photos and growth records in the "Life / Baby Growth / 2024" folder, the system will combine the path "Baby Growth" to generate the first name "2024 Baby Growth Records". In this way, the compressed file name corresponds to the storage path. Even if the user moves the compressed file location later, the name can still be associated with the original storage context, avoiding the compressed file becoming disconnected from the original context due to path changes.

[0037] Taking metadata including file modification time as an example, for scenarios where users compress "recently updated files," the intelligent naming function can extract the latest modification time of the file to be compressed and generate time-sensitive naming suggestions based on the content. For example, if a user selects five files related to "product optimization plans" that were modified last week, the system will recognize the time-sensitive information "modified last week" and generate the first naming information as "Product Optimization Plan (Last Week)". If the files are "Latest Financial Statements (Date)" or "Financial Adjustment Explanation (Date)," the first naming information will be "Latest Financial Data (Date)." In this way, users can quickly determine the timeliness of files by their compressed file names, which is especially suitable for scenarios that require frequent file version updates, such as iterative solutions at work or updated notes during study.

[0038] In some examples, the initial naming information of the compressed file can also be generated by combining the naming convention information of historical compressed files. For example, if the file selected by the user is a design draft returned in cooperation with "B Technology Company", containing "XX Product Design Draft V3.psd" and "Draft Revision Instructions.docx", the initial naming information can be generated as "B Technology Company-Draft-Date" by combining the naming convention information of historical compressed files.

[0039] For example, if the user selects a draft of an internal "marketing campaign plan" for review, containing "Marketing Campaign Plan Review Draft 1.pdf" and "Review Comments Form.xlsx", the intelligent naming function will generate naming suggestions from multiple dimensions. It can combine the naming convention information of historical compressed files to generate the first naming information as "Internal - Review Draft 1 - Marketing Plan".

[0040] For example, if the user selects a file such as "Baby's Growth Photos in August 2024" or "Growth Record Document", the first naming information can be generated as "202408 Baby Growth Package" by combining the naming convention information of historical compressed files.

[0041] In this way, by generating first naming information based on metadata and / or naming convention information such as file type, storage path, and modification time, the first naming information becomes more comprehensive and detailed, further improving the accuracy of filenames.

[0042] In some embodiments, generating first naming information for a compressed file based on the file content of at least one file may include: If at least one file is an encrypted file, generate the first naming information of the compressed file based on the de-identification information in the file content of at least one file; The first naming information includes a first prompt information, which is used to indicate that at least one file is an encrypted file.

[0043] In this embodiment, if a user selects an encrypted file for compression in a file management application, such as an encrypted work contract or privacy bill, the intelligent naming function, unable to read the encrypted content, can combine the file's de-identification information, such as non-privacy keywords in the file name and public scenarios in the storage path, to generate first naming information for the compressed file. The first naming information may also include first prompt information, which indicates that at least one file is an encrypted file.

[0044] For example, if the encrypted file is named "Company B - XX Year Confidentiality Contract (Encrypted)" and the storage path is "Work / Contract Files", the system will generate the first naming information as "Company B Contract File (Encrypted)". This retains the core identification information such as "Company B" and "Contract" while also marking the first prompt information as "Encrypted" to indicate the file attribute. This avoids the naming being completely ambiguous due to the inability to read the content, and at the same time protects the file privacy.

[0045] In this way, for encrypted files, naming information is generated based on the de-identified information, and a prompt message is included in the name to indicate that the file is encrypted, which enhances the security of file management. Users can directly identify the encryption status from the file name and avoid accidental operation or unauthorized access.

[0046] In some embodiments, naming the compressed file according to the first naming information may include: Display the first naming information; In response to the second input of the first naming information, the first naming information is entered into the naming input box of the compressed file.

[0047] In this embodiment, as Figure 2 , Figure 3 As shown, after the compressed file generation process is triggered, the file management application can pop up the compressed file settings interface 200. The compressed file settings interface 200 can include a compressed file naming input box 201 and a compressed file save path input box 202.

[0048] The first naming information 203 can be displayed in the compressed file settings interface 200. For example, the first naming information 203 can be displayed in the area near the naming input box 201.

[0049] The system can receive a second input from the user regarding the first naming information 203. In response to the second input, the first naming information 203 can be entered into the naming input box 201 of the compressed file. For example, the compressed file settings interface 200 can also display a function control corresponding to the first naming information 203, such as a "Use" control. The user can click the "Use" control, and in response to the user's operation, the naming input box 201 of the compressed file can be automatically filled with the first naming information 203.

[0050] In this way, by displaying the generated first naming information and allowing users to fill it into the naming input box through a second input, the system provides flexibility in user interaction. Users can confirm the naming information before applying it, ensuring that the naming meets expectations.

[0051] In some embodiments, in response to a second input of the first naming information, after the first naming information is entered into the naming input box of the compressed file, the method may further include: Receive edit input for the first naming information in the naming input box; In response to edit input, replace the first naming information in the naming input box with the second naming information.

[0052] In this embodiment, if the first naming information is close to the user's naming requirements but needs minor adjustments, it can be modified directly after being entered into the naming input box. That is, the system receives the user's edit input for the first naming information in the naming input box, and in response to the edit input, replaces the first naming information in the naming input box with the modified second naming information.

[0053] For example, the first name entered in the naming input box could be "Internal - Draft for Review 1 - Marketing Plan". Users can change it to the second name in the naming input box: "Internal - Draft for Review 1 - Marketing Activity Plan (North Region)", which adds the geographical information of "North Region". Similarly, the first name entered in the naming input box could be "B Technology Company - Return Draft". Users can change it to the second name in the naming input box: "B Technology Company - Return Draft - V3", adding the version number.

[0054] This allows users to edit the automatically generated naming information, replacing the first naming information with the second naming information, providing customization flexibility. Users can adjust the file names as needed, balancing the convenience of automatic naming with the precision of manual adjustment.

[0055] In some examples, if the initial naming information does not meet the user's needs at all, the user can directly enter a custom name in the naming input box.

[0056] In this way, the naming information generated by the intelligent naming function closely matches the core content of the file. Users do not need to struggle with multiple vague names and can quickly choose to adopt or make minor modifications. At the same time, the functional interaction layer retains the manual naming option, taking into account different user habits. This avoids the lack of practicality of the system's default naming and solves the tedious problem of purely manual naming, greatly reducing the user's operational burden.

[0057] In some embodiments, the method may further include: If the estimated generation time of the first naming information is less than the time threshold, a second prompt message is displayed; wherein, the second prompt message is used to indicate that the first naming information is being generated. If the estimated generation time of the first naming information is greater than or equal to the duration threshold, the default naming information is displayed.

[0058] In this embodiment, the intelligent naming function may take a long time to generate the first naming information due to reasons such as the file being too large or network latency. In this case, a time threshold can be set, which can be set according to actual needs, for example, 3 to 5 seconds.

[0059] Taking a duration threshold of 3 seconds as an example, during the generation of the first naming information, if the generation time of the first naming information does not exceed 3 seconds, a second prompt message can be displayed, such as "Generating naming suggestions...", to indicate that the first naming information is being generated, and to prevent users from mistakenly thinking that the intelligent naming function is not responding.

[0060] If the file is not generated within 3 seconds, the system's default naming information, such as "compressed file + date", will be automatically displayed. Once generated, the second prompt or default naming information will be automatically replaced with the first naming information.

[0061] In this way, prompts or default names are displayed during the naming process to provide feedback, keep users informed of the system status, avoid confusion due to generation delays, and update the display after generation to ensure that users receive the final naming information.

[0062] In some embodiments, the number of first naming information is at least two.

[0063] In this embodiment, the first naming information may include multiple naming information with different expressions, as naming suggestions that can be selected for the compressed file.

[0064] For example, in a workplace collaboration scenario, if the user selects a design draft submitted in collaboration with "Company B," containing "XX Product Design Draft V3.psd" and "Draft Revision Notes.docx," the intelligent naming function will generate naming suggestions across multiple dimensions. These could include: content dimension: "XX Product Design Draft Package"; naming convention dimension: "Company B - Draft - Date"; and comprehensive dimension: "Company B - XX Product Draft Design Package - Date," etc.

[0065] For example, in an internal review scenario, if the user selects a draft of the company's internal "Marketing Activity Plan" for review, including "Marketing Activity Plan Review Draft 1.pdf" and "Review Comments Form.xlsx", the intelligent naming function will generate naming suggestions across multiple dimensions. These could include: content dimension: "Marketing Plan Review Draft 1 Package"; naming convention dimension: "Internal - Review Draft 1 - Market Plan"; and other dimensions: "Marketing Plan Review Material Package," etc. These naming suggestions can be displayed side-by-side in card format, allowing users to choose according to their specific collaboration needs.

[0066] For example, in everyday scenarios, if a user selects a file such as "Baby's August 2024 Growth Photos" or "Growth Record Document", the intelligent naming function will generate naming suggestions from multiple dimensions, such as "Baby's August Growth Album", "202408 Baby Growth Package", or "Baby Growth Record Collection", to meet the diverse needs of daily naming.

[0067] Multiple naming suggestions can be displayed side-by-side in card format, allowing users to choose based on their specific collaboration needs. For example... Figure 4 and Figure 5 As shown, multiple naming information 2031 can be displayed in the compressed file settings interface 200. In response to a second input of any of the multiple naming information, the naming information is entered in the compressed file naming input box 201.

[0068] In this way, the first naming information includes multiple naming options. Users can select one of the naming options to fill in the naming input box, providing a variety of naming options. Users can choose the most suitable name to adapt to different needs and scenarios.

[0069] In some embodiments, the method may further include: Based on the content of at least one file, identify the classification attribute information of compressed files; Save the compressed file to the folder corresponding to the category attribute information.

[0070] In this embodiment, when generating the first naming information of the compressed file, the intelligent naming function can simultaneously identify the category attribute information corresponding to the compressed file, such as "work", "study", "life", etc., based on the file content of at least one file, and link with the automatic classification function of the file management application to automatically save the compressed file to the folder corresponding to the category attribute information.

[0071] For example, after generating the initial naming information for "XX Project Full Process Data", it is identified as a working file and the compressed file is automatically moved to the working files folder in the file management application. After generating the initial naming information for "Advanced Mathematics Differential Equations Data Package", the compressed file is automatically placed into the learning materials folder.

[0072] In this way, the classification attributes of compressed files are identified based on their content, and they are automatically saved to the corresponding folders, realizing automatic file classification and storage, and further improving the efficiency of file management.

[0073] The file management method provided in this application can be executed by a file management device. This application uses an example of a file management device executing a file management method to illustrate the file management device provided in this application.

[0074] like Figure 6 As shown, the file management device 600 provided in this application embodiment may include: Compression module 601 is configured to compress at least one file in response to a first input to at least one file to obtain a compressed file; The generation module 602 is used to generate first naming information of the compressed file based on the file content of at least one file; The naming module 603 is used to name the compressed file according to the first naming information.

[0075] In this way, by automatically generating the first naming information of the compressed file based on the file content, the file name can accurately reflect the file content, making it easy for users to quickly identify and manage compressed files. It also effectively reduces the burden of manual naming for users, balances the accuracy of compressed file naming with the portability of operation, and improves the overall efficiency of file management.

[0076] In some embodiments, the generation module 602 may be specifically used for: Generate first naming information for the compressed file based on the file content of at least one file, and at least one of the metadata of at least one file and the naming convention information of historical compressed files.

[0077] In some embodiments, metadata includes at least one of file type, file storage path, and file modification time.

[0078] In this way, by further generating first naming information based on file metadata such as file type, storage path, modification time, and / or naming convention information of historical compressed files, the first naming information becomes more comprehensive and detailed, further improving the accuracy of filenames.

[0079] In some embodiments, the generation module 602 may be specifically used for: If at least one file is an encrypted file, generate the first naming information of the compressed file based on the de-identification information in the file content of at least one file; The first naming information includes a first prompt information, which is used to indicate that at least one file is an encrypted file.

[0080] In this way, for encrypted files, naming information is generated based on the de-identified information, and a prompt message is included in the name to indicate that the file is encrypted, which enhances the security of file management. Users can directly identify the encryption status from the file name and avoid accidental operation or unauthorized access.

[0081] In some embodiments, the naming module 603 may be specifically used for: Display the first naming information; In response to the second input of the first naming information, the first naming information is entered into the naming input box of the compressed file.

[0082] In this way, by displaying the generated first naming information and allowing users to fill it into the naming input box through a second input, the system provides flexibility in user interaction. Users can confirm the naming information before applying it, ensuring that the naming meets expectations.

[0083] In some embodiments, the file management device 600 may further include: The receiving module is used to receive edit input of the first naming information in the naming input box; Naming module 603 can also be used for: In response to edit input, replace the first naming information in the naming input box with the second naming information.

[0084] This allows users to edit the automatically generated naming information, replacing the first naming information with the second naming information, providing customization flexibility. Users can adjust the file names as needed, balancing the convenience of automatic naming with the precision of manual adjustment.

[0085] In some embodiments, the number of first naming information is at least two.

[0086] In this way, the first naming information includes multiple naming options. Users can select one of the naming options to fill in the naming input box, providing a variety of naming options. Users can choose the most suitable name to adapt to different needs and scenarios.

[0087] In some embodiments, the file management device 600 may further include: The identification module is used to identify the classification attribute information of compressed files based on the file content of at least one file. The save module is used to save compressed files to the folder corresponding to the category attribute information.

[0088] In this way, the classification attributes of compressed files are identified based on their content, and they are automatically saved to the corresponding folders, realizing automatic file classification and storage, and further improving the efficiency of file management.

[0089] The file management device in this application embodiment can be an electronic device or a component within an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or other devices besides a terminal. For example, the electronic device can be a mobile phone, tablet computer, laptop computer, PDA, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc. It can also be a server, network attached storage (NAS), personal computer (PC), television (TV), ATM, or self-service machine, etc. This application embodiment does not specifically limit the device.

[0090] The file management device in this application embodiment can be a device with an operating system. This operating system can be Android, iOS, or other possible operating systems; this application embodiment does not specifically limit the specific operating system used.

[0091] The file management device provided in this application embodiment can implement the various processes implemented in the method embodiment, and will not be described again here to avoid repetition.

[0092] Optionally, such as Figure 7As shown, this application embodiment also provides an electronic device 700, including a processor 701 and a memory 702. The memory 702 stores a program or instructions that can run on the processor 701. When the program or instructions are executed by the processor 701, they implement the various steps of the above-described file management method embodiment and can achieve the same technical effect. To avoid repetition, they will not be described again here.

[0093] It should be noted that the electronic devices in the embodiments of this application include the mobile electronic devices and non-mobile electronic devices described above.

[0094] Figure 8 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application.

[0095] The electronic device 800 includes, but is not limited to, components such as: radio frequency unit 801, network module 802, audio output unit 803, input unit 804, sensor 805, display unit 806, user input unit 807, interface unit 808, memory 809, and processor 810.

[0096] Those skilled in the art will understand that the electronic device 800 may also include a power supply (such as a battery) for supplying power to various components. The power supply may be logically connected to the processor 810 through a power management system, thereby enabling functions such as managing charging, discharging, and power consumption through the power management system. Figure 8 The electronic device structure shown does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown, or combine certain components, or have different component arrangements, which will not be elaborated here.

[0097] The processor 810 can be used for: In response to a first input of at least one file, the at least one file is compressed to obtain a compressed file; Generate the first naming information of the compressed file based on the file content of at least one file; Name the compressed file according to the first naming information.

[0098] In this way, by automatically generating the first naming information of the compressed file based on the file content, the file name can accurately reflect the file content, making it easy for users to quickly identify and manage compressed files. It also effectively reduces the burden of manual naming for users, balances the accuracy of compressed file naming with the portability of operation, and improves the overall efficiency of file management.

[0099] In some embodiments, the processor 810 can also be used for: Generate first naming information for the compressed file based on the file content of at least one file, and at least one of the metadata of at least one file and the naming convention information of historical compressed files.

[0100] In some embodiments, metadata includes at least one of file type, file storage path, and file modification time.

[0101] In this way, by further generating first naming information based on file metadata such as file type, storage path, modification time, and / or naming convention information of historical compressed files, the first naming information becomes more comprehensive and detailed, further improving the accuracy of filenames.

[0102] In some embodiments, the processor 810 can also be used for: If at least one file is an encrypted file, generate the first naming information of the compressed file based on the de-identification information in the file content of at least one file; The first naming information includes a first prompt information, which is used to indicate that at least one file is an encrypted file.

[0103] In this way, for encrypted files, naming information is generated based on the de-identified information, and a prompt message is included in the name to indicate that the file is encrypted, which enhances the security of file management. Users can directly identify the encryption status from the file name and avoid accidental operation or unauthorized access.

[0104] In some embodiments, the display unit 806 may be used for: Display the first naming information; The 810 processor can also be used for: In response to the second input of the first naming information, the first naming information is entered into the naming input box of the compressed file.

[0105] In this way, by displaying the generated first naming information and allowing users to fill it into the naming input box through a second input, the system provides flexibility in user interaction. Users can confirm the naming information before applying it, ensuring that the naming meets expectations.

[0106] In some embodiments, the user input unit 807 may be used for: Receive edit input for the first naming information in the naming input box; The 810 processor can also be used for: In response to edit input, replace the first naming information in the naming input box with the second naming information.

[0107] This allows users to edit the automatically generated naming information, replacing the first naming information with the second naming information, providing customization flexibility. Users can adjust the file names as needed, balancing the convenience of automatic naming with the precision of manual adjustment.

[0108] In some embodiments, the number of first naming information is at least two.

[0109] In this way, the first naming information includes multiple naming options. Users can select one of the naming options to fill in the naming input box, providing a variety of naming options. Users can choose the most suitable name to adapt to different needs and scenarios.

[0110] In some embodiments, the processor 810 can also be used for: Based on the content of at least one file, identify the classification attribute information of compressed files; Save the compressed file to the folder corresponding to the category attribute information.

[0111] In this way, the classification attributes of compressed files are identified based on their content, and they are automatically saved to the corresponding folders, realizing automatic file classification and storage, and further improving the efficiency of file management.

[0112] It should be understood that, in this embodiment, the input unit 804 may include a graphics processing unit (GPU) 8041 and a microphone 8042. The GPU 8041 processes image data of still images or videos obtained by an image capture device (such as a camera) in video capture mode or image capture mode. The display unit 806 may include a display panel 8061, which may be configured in the form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 807 includes at least one of a touch panel 8071 and other input devices 8072. The touch panel 8071 is also called a touch screen. The touch panel 8071 may include a touch detection device and a touch controller. Other input devices 8072 may include, but are not limited to, physical keyboards, function keys (such as volume control buttons, power buttons, etc.), trackballs, mice, and joysticks, which will not be described in detail here.

[0113] The memory 809 can be used to store software programs and various data. The memory 809 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store the operating system, application programs or instructions required for at least one function (such as sound playback, image playback, etc.). Furthermore, the memory 809 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DRRAM). The memory 809 in the embodiments of this application includes, but is not limited to, these and any other suitable types of memory.

[0114] Processor 810 may include one or more processing units; optionally, processor 810 integrates an application processor and a modem processor, wherein the application processor mainly handles operations involving the operating system, user interface, and applications, and the modem processor mainly handles wireless communication signals, such as a baseband processor. It is understood that the aforementioned modem processor may also not be integrated into processor 810.

[0115] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they implement the various processes of the above-described file management method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0116] The processor is the processor in the electronic device described in the above embodiments. The readable storage medium includes computer-readable storage media, such as computer read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0117] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described file management method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0118] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0119] This application provides a computer program product that is stored in a storage medium and executed by at least one processor to implement the various processes of the file management method embodiment described above, and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0120] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0121] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0122] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A file management method, characterized in that, The method includes: In response to a first input of at least one file, the at least one file is compressed to obtain a compressed file; Based on the file content of the at least one file, generate the first naming information of the compressed file; The compressed file is named according to the first naming information.

2. The method according to claim 1, characterized in that, The step of generating the first naming information of the compressed file based on the file content of the at least one file includes: The first naming information of the compressed file is generated based on the file content of the at least one file, and at least one of the metadata of the at least one file and the naming convention information of historical compressed files.

3. The method according to claim 2, characterized in that, The metadata includes at least one of the following: file type, file storage path, and file modification time.

4. The method according to claim 1, characterized in that, The step of generating the first naming information of the compressed file based on the file content of the at least one file includes: In the case that at least one file is an encrypted file, the first naming information of the compressed file is generated based on the de-identification information in the file content of the at least one file; The first naming information includes a first prompt information, which is used to indicate that the at least one file is an encrypted file.

5. The method according to claim 1, characterized in that, The step of naming the compressed file according to the first naming information includes: Display the first naming information; In response to a second input of the first naming information, the first naming information is entered into the naming input box of the compressed file.

6. The method according to claim 5, characterized in that, In response to a second input of the first naming information, after the first naming information is entered into the naming input box of the compressed file, the method further includes: Receive edit input for the first naming information in the naming input box; In response to the edit input, the first naming information in the naming input box is replaced with the second naming information.

7. The method according to claim 1, characterized in that, The number of the first naming information is at least two.

8. The method according to claim 1, characterized in that, The method further includes: Based on the file content of the at least one file, identify the classification attribute information of the compressed file; Save the compressed file to the folder corresponding to the classification attribute information.

9. An electronic device, characterized in that, It includes a processor and a memory, the memory storing a program or instructions that can run on the processor, the program or instructions being executed by the processor to implement the steps of the method as described in any one of claims 1-8.

10. A readable storage medium, characterized in that, A program or instructions are stored on the readable storage medium, which, when executed by a processor, implement the steps of the method as described in any one of claims 1-8.

Images