File attribute management method and related apparatus
By identifying user needs in electronic devices and extracting the connotation, extension, and interactive attributes of files, the problem of limited attribute information in existing file systems is solved, enabling faster location of target files and exclusion of erroneous folders, thus improving the user experience.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- HUAWEI TECH CO LTD
- Filing Date
- 2026-01-20
- Publication Date
- 2026-07-30
AI Technical Summary
The existing file system attribute information is limited and cannot meet the multi-dimensional and personalized memory needs of users, making it difficult for users to quickly locate target files or eliminate erroneous folders.
Electronic devices receive user input, identify needs, extract intrinsic attributes, extrinsic attributes, and interactive attributes, filter out applicable documents, and display custom attribute values.
It improves the efficiency of users finding files, meets personalized needs, reduces the complexity of user operations, and enhances the user experience.
Smart Images

Figure CN2026073580_30072026_PF_FP_ABST
Abstract
Description
A method and related apparatus for managing file attributes
[0001] This application claims priority to Chinese Patent Application No. 202510116311.2, filed with the State Intellectual Property Office of China on January 23, 2025, entitled "A Method and Related Apparatus for Document Attribute Management", the entire contents of which are incorporated herein by reference. Technical Field
[0002] This application relates to the field of terminals, and more particularly to a method and related apparatus for managing file attributes. Background Technology
[0003] Users' memory of files is multi-dimensional and personalized, but current file system attributes only support limited and fixed attribute information, providing limited information. This makes it difficult for users to locate target files or exclude incorrect folders.
[0004] Therefore, how to extract attributes based on the user's memory of the file and related information, and present them in a list view to improve file extraction efficiency, is a problem worth considering. Summary of the Invention
[0005] This application provides a file attribute management method and related apparatus. Using this method, an electronic device can receive user input and identify the user's needs. The electronic device can extract key information from the user input, which may include the range of files the user needs, the file attributes the user requires, etc. The electronic device can filter files based on the file range, selecting suitable files according to the user's needs. Then, the electronic device can browse the relevant information of the filtered suitable files and extract the attribute values of the suitable files. Finally, the electronic device can display the extracted attribute values to the user. This improves the efficiency of file extraction, enabling users to more quickly locate target files or exclude incorrect folders.
[0006] In a first aspect, this application provides a file attribute management method, which is applied to a first electronic device. The method includes: displaying default attribute information of N files stored in the electronic device, where N is a positive integer; receiving input information from a user, where the input information is different from the default attribute information of the N files; and displaying custom attributes of M files, where the custom attributes correspond to the input information, and M is a positive integer less than or equal to N.
[0007] By implementing the method described in the first aspect above, electronic devices can identify the custom attributes of the files the user wants to extract based on user input, analyze files within a specified range, and intuitively present the custom attribute values of the applicable files. This allows users to quickly obtain more attribute information about files, locate target files more quickly, or exclude incorrect folders, thereby improving the efficiency of users finding and extracting files.
[0008] In conjunction with the first aspect, after receiving the user's input information, the method further includes: analyzing the custom attribute based on the input information. The custom attribute includes: connotation attribute, extension attribute, and interaction attribute. The connotation attribute is an attribute extracted based on the file content. The extension attribute is an attribute proposed based on file association information stored in the server. The file association information is not included in the file content. The interaction attribute is an attribute extracted based on the user's operation record on the file.
[0009] Electronic devices can extract file attributes based on multiple factors, including the file's content, related online databases or information sources, and user activity logs. This allows electronic devices to meet users' needs for personalized file attribute definition and usage, thus improving the user experience.
[0010] In conjunction with the first aspect, display the custom attributes of M files, specifically including: determining the target file category based on the input information; selecting the M files from the N files based on the target file category; and displaying the custom attributes of the M files.
[0011] Electronic devices can initially extract files in applicable formats and exclude files in inapplicable formats based on user needs, thereby improving the extraction efficiency of custom attributes.
[0012] For example, if an electronic device receives user input as custom attributes for extracting paper files, it can filter out M paper files from N files.
[0013] This can improve the speed and accuracy of subsequent custom attribute extraction, thereby enhancing the user experience.
[0014] In conjunction with the first aspect, displaying the custom attributes of the M files specifically includes: determining the custom attribute as an intrinsic attribute based on the input information; extracting the intrinsic attributes of the M files from their contents; and displaying the intrinsic attributes of the M files.
[0015] For example, when the user inputs "the year of publication of the paper," the electronic device can determine that the target file is a paper file based on the user's input information, and set the publication year as the custom attribute. Since the publication year is usually included in the content of the paper itself, it is an intrinsic attribute of the paper file. The electronic device can extract the publication year of each paper file based on its content.
[0016] In this way, electronic devices can extract the intrinsic information of a file, obtain and display its intrinsic attributes, so that users do not need to open the file one by one to view it, thereby improving the efficiency of users in obtaining file content and enhancing the user experience.
[0017] In conjunction with the first aspect, displaying the custom attributes of the M files specifically includes: determining the target files as the M files based on the input information, and the custom attribute as the extension attribute; obtaining the extension attributes of the M files from the server, wherein the access method of the server is pre-stored in the electronic device, or the access method of the server is specified by the user's second input information; and displaying the extension attributes of the M files.
[0018] For example, when the user inputs "citation count of the paper," the electronic device can determine that the target file is a paper file, and the custom attribute is citation count. Since the paper itself does not contain parameters such as citation count, but paper retrieval websites typically include data such as citation count, citation count is an extended attribute of the paper file. The electronic device can obtain the citation count attribute value of the paper file by accessing the server of the paper retrieval website. The access method to the paper retrieval website can be preset in the electronic device or specified by the user.
[0019] In this way, electronic devices can obtain the extended attributes of a file from external information sources related to file attributes, eliminating the need for users to perform searches and improving the user experience.
[0020] In conjunction with the first aspect, displaying the custom attributes of the M files specifically includes: determining that the custom attribute is an interactive attribute based on the input information; obtaining L interactive information corresponding to the M files in the file interactive information library, obtaining the interactive attributes of the M files from the L interactive information, wherein the L interactive information is used to record the operations performed by the user on the M files, and L is greater than or equal to M; and displaying the interactive attributes of the M files.
[0021] For example, if the user inputs information such as "files shared in the meeting," the electronic device can determine that the custom attribute is the file's interactive attribute. The electronic device can extract the file's interactive attributes by obtaining the user's operation records for the file based on a file interaction information database. For instance, the electronic device can extract and display the file's interactive application and interactive operation. If the user operation recorded in the file interaction information database is that the user enabled screen sharing through a meeting application and opened a file, then the corresponding interactive application for that file is the meeting application, and the interactive operation is screen sharing.
[0022] In this way, electronic devices can display the interactive attributes of files, allowing users to intuitively observe the operation records of files and making it easier for users to find files.
[0023] In conjunction with the first aspect, the M files include a first file, and the L interactive information includes first interactive information. Before displaying the interactive attributes of the M files, the method further includes: receiving a first operation by the user on the first file, generating first interactive information, the first interactive information being used to record the first operation, the first operation including one or more of screen sharing, sharing, downloading, editing, and referencing; and storing the first interactive information in the file interactive information library.
[0024] Electronic devices can record user operations on files, thereby building a file interaction information database to extract file interaction attributes.
[0025] In conjunction with the first aspect, after displaying the custom attributes of M files, the method further includes: extracting the custom attributes of K files from the first electronic device, wherein the storage paths of the K files are different from the storage paths of the N files; saving the custom attributes of the K files; receiving the first input information from the user; and displaying the custom attributes of the K files.
[0026] After an electronic device completes the extraction of custom attributes from a target file, it can also perform attribute pre-extraction on other files it stores and retain the extraction results. When the next user input indicates the same custom attribute, but the target file is a different file, the electronic device can directly use the extracted results, improving its response speed and enhancing the user experience.
[0027] In conjunction with the first aspect, after displaying the custom attributes of M files, the method further includes: performing attribute value operations on the custom attributes of the M files, which include one or more of filtering, sorting, and calculation.
[0028] In this way, electronic devices can perform further operations on the extracted custom attributes to meet users' deeper needs. For example, an electronic device can extract custom attributes such as sales volume and profit from annual report files, and perform sorting and filtering operations on these two custom attributes, allowing users to more intuitively observe the levels of sales volume and profit. The electronic device can also multiply the attribute values of sales volume and profit to obtain the total profit, providing users with even more detailed information.
[0029] In a second aspect, this application provides an electronic device including: a processor and a memory coupled to the processor, the memory being used to store computer program code including computer instructions, wherein when the processor reads the computer instructions from the memory, the electronic device causes the electronic device to perform the method described in the first aspect.
[0030] Thirdly, this application provides a chip system applied to an electronic device, the chip system including one or more processors, the processors being configured to invoke computer instructions to cause the execution of the method described in the first aspect.
[0031] Fourthly, this application provides a computer-readable storage medium including a computer program that, when run on an electronic device, causes the electronic device to perform the method described in the first aspect.
[0032] Fifthly, this application provides a computer program product that, when run on a computer, causes the electronic device to perform the method described in the first aspect.
[0033] Understandably, the electronic device provided in the second aspect, the chip system provided in the third aspect, the computer-readable storage medium provided in the fourth aspect, and the computer program product provided in the fifth aspect are all used to execute the method provided in this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here. Attached Figure Description
[0034] Figure 1 is a schematic diagram of the folder window displayed on an electronic device according to an embodiment of this application;
[0035] Figure 2 is a schematic diagram of the file attribute list of the electronic device provided in an embodiment of this application;
[0036] Figure 3 is a schematic diagram of the file attribute management window of the electronic device provided in an embodiment of this application;
[0037] Figure 4 is a schematic diagram of an electronic device receiving user input according to an embodiment of this application;
[0038] Figure 5 is a schematic diagram of the display of file attributes on an electronic device provided in an embodiment of this application;
[0039] Figure 6 is a schematic diagram of the electronic device displaying the extension attributes of a file according to an embodiment of this application;
[0040] Figure 7 is a schematic diagram of the electronic device displaying file interaction attributes provided in an embodiment of this application;
[0041] Figure 8 is a schematic diagram of the process of recording file interaction information by an electronic device according to an embodiment of this application;
[0042] Figure 9 is a schematic diagram of electronic device recording file interaction information provided in an embodiment of this application;
[0043] Figure 10 is a schematic diagram of the electronic device display prompt box provided in an embodiment of this application;
[0044] Figure 11 is a flowchart illustrating the file attribute management method provided in an embodiment of this application;
[0045] Figure 12 is a schematic diagram of an electronic device processing user input information provided in an embodiment of this application;
[0046] Figure 13 is a schematic diagram of the hardware structure of the electronic device provided in an embodiment of this application. Detailed Implementation
[0047] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0048] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. The terms “first” and “second” are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as “first” or “second” may explicitly or implicitly include one or more of that feature. “First” and “second,” etc., are used to distinguish different objects, not to describe a particular order of objects. For example, a first object and a second object are used to distinguish different objects, not to describe a particular order of objects.
[0049] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more. For example, multiple processing units refer to two or more processing units; multiple systems refer to two or more systems.
[0050] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or related scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0051] The term "and / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A existing alone, A and B existing simultaneously, and B existing alone.
[0052] To better understand the technical solutions provided in this application, before describing the technical solutions, we will first refer to the accompanying drawings to explain the electronic device 100 with a camera function to which this application applies. In the embodiments of this application, the electronic device 100 may include, but is not limited to, devices with camera functions such as mobile phones, tablets, and smartwatches. The embodiments of this application do not limit the specific form or type of the electronic device 100.
[0053] The term "user interface (UI)" used in the following embodiments of this application refers to the medium interface through which an application or operating system interacts and exchanges information with the user. It realizes the conversion between the internal form of information and the form that the user can accept. The user interface is source code written in a specific computer language such as Java or Extensible Markup Language (XML). The interface source code is parsed and rendered on the electronic device, ultimately presenting content that the user can recognize. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be visible interface elements such as text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets displayed on the screen of an electronic device.
[0054] To better understand the technical solutions provided in this application, before describing the technical solutions, we will first refer to the accompanying drawings to explain the electronic device 100 with file storage function to which this application applies. In the embodiments of this application, the electronic device 100 may include, but is not limited to, devices with file storage functions such as computers, mobile phones, tablets, and smartwatches. The embodiments of this application do not limit the specific form or type of the electronic device 100.
[0055] Electronic devices can use file systems to organize and manage data stored on them (such as hard drives, solid-state drives, flash drives, etc.). A file system provides a structured way for electronic devices to store and retrieve data. It defines how data is divided into files and directories, and how these files and directories are located on the storage device.
[0056] When storing files, electronic devices can extract and record file attributes, such as file name, file type, file size, and file modification date. These attributes can then be used to sort and categorize files.
[0057] When an electronic device displays a folder window, it can show some of the file's attributes at the corresponding file location. File attributes provide users with a variety of information to understand and manipulate files. For example, users can quickly identify a file's format through its filename, extension, and type, which helps them choose the correct application to open the file. Users can also view a file's activity level and historical operation records through attributes such as modification date, allowing for better file organization and management.
[0058] For example, refer to Figure 1. Figure 1 shows a folder window of an electronic device.
[0059] As shown in Figure 1, the electronic device can display a folder window 100A. This folder window 100A may include controls 101, 102, and 103. Control 101 can be used to select folder 1, control 102 can be used to select folder 2, and control 103 can be used to select folder 3. The electronic device can receive user clicks on control 101 and display the attribute values of the files in folder 1.
[0060] Folder 1 can contain five files: file a, file b, file c, file d, and file e. The electronic device can display partial attribute values of these five files in folder window 100A, such as file name, modification date, file type, and file size. For example, the electronic device can display the names of the five files in area 104, the modification dates in area 105, the file types in area 106, and the file sizes in area 107. The file attributes, including name, modification information, type, and size, can have a corresponding layout. As shown in Figure 1, the electronic device can display the attributes of the same file on the same line. Taking file a as an example, Figure 1 shows that file a is the file name, the modification date is 2024 / 12 / 2, the file type is PDF, and the file size is 645KB. In this way, the user can use the information provided by these file attributes to determine how and when file a was manipulated.
[0061] In current electronic devices, the set of file attributes that a file system can provide is fixed. The information that these file attributes can provide is limited.
[0062] Please refer to Figure 2, which exemplarily illustrates a list of file attributes provided by an electronic device.
[0063] As shown in Figure 2, the folder window 100A displayed on the electronic device may include a control 201, which can be used to trigger the electronic device to display a file attribute list 202. The file attribute list 202 may include one or more controls. The controls in the file attribute list 202 can be used to select or deselect file attributes. When a user selects a file attribute, the electronic device can display the corresponding file attribute in the folder window 100A. When the user deselects a file attribute, the electronic device no longer displays that file attribute in the folder window 100A. For example, the file attribute list 202 may include modification date, type, size, creation date, author, etc. If modification date, type, and size are selected, while creation date and author are not selected, then, referring to Figure 1, in the folder window 100A, the electronic device displays the file's modification date, type, and size, but not the file's creation date and author.
[0064] The file attribute list may also include a control 203, which can be used to open the attribute management window. As shown in Figure 3, in response to a click on the control 203, the electronic device can display an attribute management window 300, which may include an area 301. The electronic device can display multiple selectable file attribute options within the area 301, and can also receive user swipe gestures to display more file attribute options within the area 301.
[0065] However, the number of file attributes that electronic devices can offer is ultimately fixed, and the information they can provide is limited. Furthermore, these file attributes are preset within the electronic device and cannot be customized to individual user preferences, which may prevent them from meeting user needs in some situations.
[0066] Users' memories of files can be multi-dimensional and personalized. For example, a user's first impression of a work-related file might be: a file shared in a recent meeting with colleagues; their memory of a research paper might be: a recently published paper; and so on. It's not simply about file type or modification date. Therefore, the attributes (modification date, type, etc.) currently available on electronic devices cannot provide users with direct access to this information, making it difficult for them to quickly find the target file or eliminate incorrect folders. When there are many similar files, users may even need to browse through them one by one, increasing the complexity of the user operation and negatively impacting the user experience.
[0067] To address the mismatch between user memory methods and current file attributes, and to meet users' needs for personalized attribute definition and usage, this application proposes a file attribute management method. In this method, an electronic device can receive user input and identify the user's needs. The electronic device can extract key information from the user input, which may include the range of files the user needs, the required file attributes, etc. The electronic device can filter files based on the file range, selecting suitable files according to the user's needs. Then, the electronic device can browse the relevant information of the filtered suitable files and extract the attribute values of the suitable files. Finally, the electronic device can display the extracted attribute values to the user.
[0068] Optionally, the electronic device can also save the attribute values extracted each time, and can also extract other files stored in the electronic device based on each identified need, and store the extraction results in the electronic device. When the user enters the same need again, it can quickly respond to the user's operation and display the extraction results.
[0069] In one possible implementation, the electronic device 100 can receive user input to obtain the user's needs. For example, when displaying a folder window, the electronic device 100 can display an input box in the folder window. This input box can be used to receive user input. The user input methods can include text input, voice input, image input, etc.
[0070] Referring to Figure 4, which illustrates an electronic device 100 receiving user input, the electronic device 100 can display a folder window 100A, within which an input box 401 can be displayed. The input box 401 can be used to accept text, voice, images, and other content input by the user.
[0071] For example, electronic device 100 can receive text information input by a user through input box 401. Then, electronic device 100 can determine custom attributes and applicable files based on the text information input by the user. Afterwards, electronic device 100 can extract the custom attributes of the applicable files from the file's intrinsic information. The intrinsic information of the file may include content existing in the file itself, such as text content, image content, name, type, size, and date.
[0072] For example, as shown in Figure 5, the electronic device 100 receives text information input by the user through the input box 401, including "the year of publication of the paper". After receiving this text information, the electronic device 100 can determine that the applicable document is a paper and the custom attribute is the year of publication. Then, the electronic device 100 can display the attribute column 501. This attribute column 501 can be used to display the publication year of the document. For example, the user can observe through this attribute column 501 that the paper for document a was published in 2013, the paper for document b was published in 1994, the paper for document c was published in 2002, the paper for document d was published in 2006, and the paper for document e was published in 2010.
[0073] Optionally, the electronic device 100 can also extract custom attributes of the applicable file based on the file's extension information. Here, the file's extension information can be understood as content from online databases or information sources related to the file's attributes, such as content related to the file in the internet, academic paper databases, or large language models.
[0074] For example, as shown in Figure 6, electronic device 100 can receive the text information "citation count of the paper" input by the user through input box 401. Electronic device 100 can also additionally display input box 601, which can display a default website. Electronic device 100 can also receive website information input by the user through input box 601 and change the website in input box 601. Electronic device 100 can obtain the file's extension information by accessing the website in input box 601. Then, electronic device 100 can respond to the user's input by displaying attribute column 602, which can be used to display the citation count attribute of the file. The user can observe through attribute column 602 that file a has 13 citations, file b has 4 citations, file c has 9 citations, file d has 7 citations, and file e has 5 citations.
[0075] Optionally, the electronic device 100 can also extract custom attributes based on the file's interaction information. This interaction information can be understood as records of the user's actions on the file on the electronic device 100, such as the file's download source, the time of interaction during which the user managed, edited, shared, or referenced the file, and the application used to process the file.
[0076] As shown in Figure 7, the electronic device 100 can receive text input from the user: "Files shared in the last meeting". Then, the electronic device 100 can display attribute columns 701 and 702. Attribute column 701 displays the interactive application attributes of the files, and attribute column 702 displays the interactive operation attributes of the files. The user can observe through attribute columns 701 and 702 that file a was screen-shared through application a, file b was also screen-shared through application a, file c was downloaded through application b, file d was uploaded through application c, and file e was edited through application d. Optionally, the electronic device 100 can extract multiple attributes at once and add multiple attribute value columns simultaneously. Taking the description of Figure 7 above as an example, based on interactive information, the electronic device 100 can extract two attributes: interactive application and interactive behavior. Therefore, the electronic device 100 can add two columns of attribute values—interactive application and interactive behavior—to the file list at once.
[0077] Electronic device 100 can access information in the file interaction information database by accessing data in the file interaction information database. Referring to Figure 8, which exemplarily illustrates a method by which electronic device 100 records interaction information:
[0078] S801. Electronic device 100 records user, file, and application interaction information.
[0079] Electronic device 100 can record user interaction information with files. This interaction information can be used to record user interaction behaviors with files and associated applications. For example, when a user edits, uploads, or shares a file, electronic device 100 can record the user's editing, uploading, and sharing operations. Electronic device 100 can also record application information involved in the user's interaction with the file, such as the name of the application to which the user uploaded or shared the file.
[0080] For example, after a user activates the screen sharing function of a meeting application, they open file c and share it. During the file sharing process, the electronic device 100 can record this interaction information.
[0081] Optionally, the interaction information may also include associated files. The electronic device 100 can record other files involved in the interaction while the user is interacting with a file. For example, if a user is sharing file a in a meeting and also has file b open, the electronic device 100 can record the association information between file a and file b, which can be used to indicate that the user has opened both file a and file b simultaneously.
[0082] Optionally, the interaction information may also include information related to the user's interaction with the file, such as relevant contacts and interaction time. This application embodiment does not limit the specific content of the interaction information.
[0083] For example, reference can be made to Figure 9, which illustrates a schematic diagram of an electronic device 100 recording interactive information.
[0084] As shown in Figure 9, the electronic device 100 activates the screen sharing function of the meeting application, responding to the user's operation by opening file c and sharing it. During this process, the electronic device 100 can determine that the user may be sharing a file during a meeting based on the user's actions of opening the meeting application and opening a file. During the sharing process, the electronic device 100 can take screenshots to capture a screenshot of the meeting. The electronic device 100 can take screenshots intermittently or at regular time intervals; this embodiment does not limit this. After taking a screenshot, the electronic device 100 can save the screenshot. Then, the electronic device 100 can analyze the content of the screenshot. For example, the electronic device 100 can perform image recognition on the meeting screenshot. For example, the electronic device 100 can identify area 901 in Figure 9 to determine that the electronic device 100 has activated the screen sharing function of the meeting application in that screenshot. The electronic device 100 can also identify area 902 in Figure 9 to determine that the electronic device 100 opened file c when screen sharing was activated. Then, based on the identification results of areas 901 and 902, electronic device 100 can determine the interactive information that the user shares file c through the conference application.
[0085] Optionally, the electronic device 100 can further identify the screenshot. For example, when multiple conferencing applications are installed on the electronic device 100, the electronic device 100 can record the interface of each of the multiple conferencing applications separately. Then, when the electronic device 100 identifies the screenshot, it can determine which conferencing application is open in the screenshot.
[0086] Optionally, the electronic device 100 can also record the screenshot acquisition time to determine the time point when the user shares the image. Alternatively, the electronic device 100 can also acquire the time information that may exist in the screenshot when recognizing it, as shown in area 903 of Figure 9, to determine the time point when the user shares the file through the meeting application. Alternatively, the electronic device 100 can take screenshots at certain time intervals after starting the meeting application. Then, the electronic device 100 can recognize this batch of screenshots, acquire screenshots that include information about file c, and acquire the earliest and latest times of the screenshots containing file c, thereby determining the approximate duration of the user sharing file c.
[0087] Optionally, the electronic device 100 can also identify the names of people appearing in the meeting software through screenshots, and can use such information to determine the number of participants and specific members.
[0088] In some examples, electronic device 100 can also receive user permission settings, allowing the creation of blacklists or whitelists. When electronic device 100 opens an application or file on the blacklist, it will prevent screenshots; conversely, it can only take screenshots when an application or file on the whitelist is open. This protects user privacy and prevents the leakage of confidential information related to the meeting, thus avoiding any adverse impact on the user.
[0089] Optionally, the custom attributes related to the interaction information that the electronic device 100 can determine may also include: interaction time, number of interactions, related contacts, etc. This application embodiment does not limit the custom attributes related to the interaction information.
[0090] Optionally, the electronic device 100 can also record the user's interaction records when uploading and downloading files through an application. If a user uploads a file through a social application, the electronic device 100 can detect the user's action of opening the social application and record the user's action of uploading the file to the social application. Alternatively, the electronic device 100 can take a screenshot of the social application's interface and recognize the screenshot. The electronic device 100 can confirm that the user uploaded or downloaded a file through the social application by recognizing the file-related information present in the chat box within the screenshot. The electronic device 100 can also identify the user's relevant contacts in the social application and interaction information such as the upload time through the screenshot. The electronic device 100 can record the number of times the user performs various operations on the file to obtain information such as the number of file interactions.
[0091] S802. Electronic device 100 constructs a file interaction information database based on recorded interaction information.
[0092] After acquiring the file interaction information, the electronic device 100 can construct a file interaction information database and store the interaction information in the database. When the electronic device 100 responds to user operations and extracts file attributes, it can also query the file interaction information database to obtain file interaction information. When the user's request involves interaction information, the electronic device 100 can extract the corresponding attributes through the file interaction information. For example, if the user's input is "a PPT document shown during a video conference," the electronic device 100 can determine the file scope as a PPT file. Recognized custom attributes include interaction application and interaction behavior. Then, based on the file interaction information database, the electronic device 100 can extract attributes such as interaction application and interaction behavior information of PPT files in the current path.
[0093] Taking the interactive information contained in Figure 9 as an example, based on the interactive information provided in Figure 9, when extracting the attributes of file c, electronic device 100 can obtain that the attribute value of the interactive application of file c is conference application, and the attribute value of the interactive behavior is screen sharing.
[0094] In this way, the electronic device 100 can also extract file attributes related to user interaction by querying the file interaction information database.
[0095] In one possible implementation, after each attribute extraction, the electronic device 100 can recommend folders and file sets similar to the extracted file types or content based on analysis; alternatively, the user can specify a folder. Based on the user's actions, the electronic device 100 can pre-extract other files of the same type, reducing the user's waiting time for the next attribute result.
[0096] For example, after extracting file attributes, the electronic device 100 can display a prompt box asking the user whether to retain the attribute. Upon receiving confirmation from the user, the electronic device 100 can save the attribute and, based on this attribute, pre-extract files from other paths, storing the extracted results in the electronic device 100. When the electronic device 100 receives input containing the same attribute again, it can directly retrieve the pre-extracted results to respond promptly to user actions.
[0097] For example, refer to Figure 10, which illustrates a schematic diagram of an electronic device 100 displaying a prompt box. As shown in Figure 10, the electronic device 100 can display a prompt box 1001, which asks the user whether to save the extracted attributes and pre-extract other files.
[0098] The file attribute management method provided in this application embodiment will be described in detail below. Referring to Figure 11, which exemplarily shows a flowchart of the file attribute management method provided in this application embodiment. This application embodiment also provides an electronic device 100 for executing this file attribute management method. The flowchart of the file attribute management method is described below using the electronic device 100 as an example. As shown in Figure 11, the file attribute management method may include the following steps:
[0099] S1101. Electronic device 100 displays the default attributes of N files.
[0100] Electronic device 100 can respond to user operations, display a folder window, and show the files in the current path and their default attributes. The default file attributes are preset within electronic device 100; when storing files, electronic device 100 has already extracted the default file attributes. As shown in Figure 1 above, electronic device 100 can display attributes such as file name, modification date, file type, and file size. These attributes can be referred to as the file's default attributes.
[0101] Electronic device 100 can display or hide the default attributes of files based on user operations for managing file attributes. As shown in Figures 2 and 3, electronic device 100 can display a file attribute list 202 or an attribute management window 300 for users to manage file attributes.
[0102] S1102. The electronic device receives user input information.
[0103] The electronic device 100 can receive user input. As shown in Figure 4, the electronic device 100 can display an input box 401 and obtain user input information through the input box 401. The user input information may include text information, voice information, image information, etc. This application embodiment does not limit the specific form of the user input information.
[0104] S1103. Electronic device 100 determines the file range and custom attributes based on user input information.
[0105] After receiving user input, electronic device 100 can analyze the input to determine the user's needs. Then, based on these needs, it can filter files to obtain a smaller file range, thus reducing the number of files to be processed and improving subsequent processing efficiency. The file range can default to all files in the current path, but electronic device 100 can also specify the file range for which attributes are to be extracted using natural language input or path navigation.
[0106] After determining the user's requirements, the electronic device 100 can retrieve the custom attributes to be extracted from those requirements. These custom attributes can be defined by user input and are not limited to the default file attributes preset in the electronic device 100. If the electronic device 100 has already analyzed and stored the custom attribute, it can directly display the extraction results. If the electronic device 100 does not store the relevant data for the custom attribute determined this time, it can perform subsequent operations.
[0107] Optionally, the electronic device 100 may request the user to confirm whether the custom attribute has been correctly recognized. If the electronic device 100 cannot obtain a meaningful custom attribute, it may provide feedback and request the user to enter it again.
[0108] The electronic device 100 can achieve the determination of the file range and the determination of the custom attributes to be extracted as described in step S1103 through a pre-trained model. Alternatively, it can achieve this by comparing with an information database. This application embodiment does not limit the specific method by which the electronic device 100 determines the file range and the custom attributes to be extracted.
[0109] For example, electronic device 100 can analyze user input using a large language model (LLM). An LLM is an artificial intelligence model used to understand and generate human language. Developers can train the LLM with large amounts of text data, enabling it to perform a wide range of tasks, including text summarization, keyword extraction, and so on. In this embodiment, electronic device 100 may be pre-configured with an LLM to summarize and analyze user input, determine user needs, and filter files based on those needs.
[0110] Specifically, please refer to Figure 12. Figure 12 exemplarily illustrates a schematic diagram of an electronic device 100 processing user input information. As shown in Figure 12, the user can input through the input box displayed by the electronic device 100. The user input method may include text input, voice input, image input, etc. The specific method of user input is not limited in this embodiment.
[0111] After receiving user input, electronic device 100 can send the input to the LLM (Limited Management Library). The LLM analyzes the input and primarily outputs two types of parameters: the target file range and custom attributes. For example, as shown in Figure 12, electronic device 100 receives the text input by the user: "Please show the publication years of all papers." After inputting this text into the LLM, the LLM analyzes it and determines that the files the user wants to view are primarily papers, and that the user wants to view the custom attribute "publication year of the paper."
[0112] Electronic device 100 can initially extract files in applicable formats and exclude files in inapplicable formats by associating the requirement type with the file format. For example, when the user's requirement is a thesis file, electronic device 100 can initially extract files with text formats such as Word and PDF. Then, electronic device 100 can perform attribute analysis on the initially selected files, excluding files that cannot yield meaningful attribute values, and obtaining applicable files that meet the file range.
[0113] Based on the file range, the electronic device 100 can filter the files in the current path, select files that meet the file range, exclude files that do not meet the user's conditions, and reduce the amount of computation required for subsequent processing.
[0114] Taking the scope of files as academic papers as an example, electronic device 100 can filter files in the current path to select academic papers. The current path can be the folder selected by the user. For example, as shown in Figure 5, electronic device 100 is currently displaying files in folder 1, so the current path can be folder 1. After receiving the user's input of the "year of publication," since the text content does not include the specified path, electronic device 100 will by default filter the files in folder 1, selecting files belonging to academic papers from files a, b, c, d, and e. This filtering process can also be completed by an LLM (File Management Library). An LLM can browse the file content and determine whether the file is an applicable file based on the content; in this example, it determines whether the file belongs to an academic paper.
[0115] For example, files a, b, c, d, and e in folder 1 are all academic papers. Electronic device 100 retains these five files and extracts their custom attributes, namely the year of publication.
[0116] Alternatively, in one possible implementation, the electronic device 100 can filter files using default attributes such as file type. For example, when filtering thesis files, the electronic device 100 can determine the file range based on common text formats. The electronic device 100 can filter files of type ppt, word, pdf, or txt as applicable files.
[0117] Optionally, if the user input does not involve limiting the file range, the electronic device 100 may default to all files in the current path as applicable files.
[0118] Optionally, the electronic device 100 can also receive a specified path input by the user, filter applicable files under the specified path, and perform subsequent processing. For example, the electronic device 100 can receive user input through the input box 501. If the user input specifies that the files in folder 2 should be processed, the electronic device 100 will not process the files under the current path (folder 1), but will process the files in folder 2.
[0119] S1104. Filter out M files based on file range and extract custom attributes from the M files.
[0120] After determining the scope of documents and filtering out applicable documents, electronic device 100 can further read the relevant data of the applicable documents through LLM to obtain their custom attributes. As shown in Figure 6, this means extracting the publication years of applicable academic papers. Electronic device 100 can browse the content of applicable documents through LLM and extract their custom attributes based on that content. For example, if documents a, b, c, d, and e are all academic papers, electronic device 100 can read the content of these five papers through LLM and extract their publication years from the content.
[0121] In one possible implementation, the electronic device 100 can extract custom attributes of a file not only through its intrinsic information such as file content, but also through its extrinsic information and interactive information. The custom attributes that the electronic device 100 can extract include intrinsic attributes, extrinsic attributes, and interactive attributes. The content that the electronic device 100 can use to extract custom attributes includes, but is not limited to, the file's intrinsic information, extrinsic information, and interactive information. Specifically, the electronic device 100 can extract the file's intrinsic attributes through its intrinsic information, extract its extrinsic attributes through its extrinsic information, and extract its interactive attributes through its interactive information.
[0122] The following sections describe how electronic devices process the intrinsic, extrinsic, and interactive information of files.
[0123] I. Connotative Information
[0124] Electronic device 100 can understand and parse the intrinsic information of a document using a large model. For example, as shown in Figure 5, electronic device 100 can obtain the publication year of a paper based on its own content; the publication year can be considered an intrinsic attribute of the paper. When processing the intrinsic information of a paper to extract its publication year, electronic device 100 can call the LLM paper parsing plugin, using "publication year" as a prompt for large model question answering. If the LLM large model can intelligently understand the paper's content, it can attempt to extract the publication year and filter out other irrelevant information.
[0125] II. Extended Information
[0126] After parsing the intrinsic information of a file, electronic device 100 can also retrieve some keywords from the intrinsic information using an internet search engine. Electronic device 100 can use a default database as its information source, or it can use a database from an external information source specified by the user. Processing the extrinsic information of a file by electronic device 100 may include the following steps:
[0127] 1. For applicable files, electronic device 100 obtains the file name, file title or other specified information, uses this information to crawl and search external information websites, sends a Hypertext Transfer Protocol (HTTP) request, and obtains the Hypertext Markup Language (HTML) content of the webpage.
[0128] The external information website can be preset in the electronic device 100. When the electronic device 100 processes external information and the user does not specify an external database, the electronic device 100 can default to searching through the external information website preset in the electronic device 100.
[0129] In one possible implementation, the electronic device 100 can also accept external websites input by the user as the basis for retrieval. For example, as shown in FIG6, the electronic device 100 can display an input box 601 in a folder window. The electronic device 100 can accept information such as websites input by the user through the input box 601, obtain the web page information of the content received in the input box 601, and extract it based on the web page information.
[0130] Optionally, the electronic device 100 can perform online searches for keywords without specifying an external website. Then, the electronic device 100 can provide a search engine or database thumbnail interactive window in the file window, displaying websites related to the search content, and supporting users to quickly select external websites from the search results as external information sources after the search.
[0131] Optionally, the electronic device 100 may also display a default website preset within the electronic device 100 in the input box 601 for user confirmation. When the user does not make any modifications, the electronic device 100 can perform searches through the default website. When the user wishes to specify an external information source, the electronic device 100 can still receive the user's input through the input box 601 and replace the information source from the default website with the website entered by the user.
[0132] In one possible implementation, the electronic device 100 can first extract attributes based on the connotation information of the applicable document. When the user-specified custom attribute cannot be extracted from the connotation information of the applicable document, the electronic device 100 can also use the connotation information of the document to assist in obtaining the extension information. The above processing order is only an example, and the embodiments of this application do not limit the order and specific rules for the electronic device 100 to process various information.
[0133] For example, taking Figure 6 as an example, when the electronic device 100 obtains the citation count of a paper, it can first extract information such as the paper title and abstract from the paper as search keywords. Then, the electronic device 100 can use an Internet engine to search for these keywords on a paper search website and obtain the extended information of the paper, such as the citation count.
[0134] 2. Electronic device 100 uses an open-source web crawling tool to parse the obtained HTML content and extract web page data containing the relevant attributes of the file.
[0135] Taking a thesis as an example, electronic device 100 can search for the title of the thesis on the source website of the thesis, and then obtain the data related to the thesis from the search results.
[0136] 3. Clean the obtained web page data, remove useless information and convert the format.
[0137] Electronic device 100 can extract data obtained through retrieval, extracting content related to custom attributes. For example, when obtaining the "citation count" of a paper, electronic device 100 can extract data such as the citation count from the data obtained from the paper's source website and delete other irrelevant data. Then, electronic device 100 can convert the citation count data into user-readable data. For instance, if the citation count obtained by electronic device 100 from a webpage is a computer-understandable binary number, electronic device 100 can convert the binary number into a decimal number for later user viewing.
[0138] III. Interactive Information
[0139] In addition to the intrinsic and extrinsic information of a file, embodiments of this application can also manage the file's interactive information. When extracting the interactive attributes of a file, the electronic device 100 can access a file interactive information database in addition to browsing the file's content and external information sources. This file interactive information database can be created and updated by the electronic device 100 during user operation.
[0140] For details on the specific operation of the electronic device 100 in interacting with information, please refer to the descriptions of Figures 8 and 9 above, which will not be repeated here.
[0141] S1105. Electronic device 100 displays custom attributes of M files.
[0142] Electronic device 100 can clean the results returned from large models and display them on the front-end interface, and store the results in a structured database. Electronic device 100 can add attributes to the file list using a user interface rendering module integrated with a desktop operating system, and add columns for extracted attribute values to the file list in an adaptive-width text content list for user preview.
[0143] Optionally, the electronic device 100 may display attribute column 501 as shown in FIG. 5 to display the custom attribute of the publication year of the document; the electronic device 100 may also display attribute column 602 as shown in FIG. 6 to display the custom attribute of the number of citations of the document; the electronic device 100 may also display attribute columns 701 and 702 as shown in FIG. 7 to display the two custom attributes of interactive application and interactive operation of the document.
[0144] Optionally, the electronic device 100 can perform further processing based on the custom attribute values after extracting the custom attributes of the file. For example, the electronic device 100 can use one or more custom attribute values for filtering, sorting, calculation, etc.
[0145] For example, the electronic device 100 can also store a file of the type of company annual report. The electronic device 100 can extract custom attributes such as sales volume and profit per unit from the company annual report based on user input. After extracting the custom attributes, calculations can be performed on the two custom attributes of the file. For example, the sales volume and profit per unit of the company annual report file can be multiplied to obtain information such as total profit. The electronic device 100 can also save the calculated total profit as a custom attribute of the annual report file.
[0146] The electronic device 100 can perform calculations based on user needs. This application embodiment does not limit the specific calculation operations that the electronic device 100 can perform.
[0147] S1106. Electronic device 100 responds to user confirmation by saving custom attributes and pre-extracting other applicable local file sets.
[0148] After the electronic device 100 extracts a custom attribute from a file, it can also extract the same custom attribute from other local files based on user actions. The electronic device 100 can store these extraction results, and when it obtains the same custom attribute from user input the next time, it can directly display the extraction results.
[0149] For example, referring to Figure 10, after the electronic device 100 extracts the custom attribute of publication year from the files in folder 1, the electronic device 100 can also extract the publication year from the files in folder 2 and folder 3 in response to the user's confirmation operation, and save the extraction results.
[0150] Using the file attribute management method provided in this application, the electronic device 100 can identify the file attributes that the user wants to extract based on user input, analyze applicable files within a specified range, dynamically add the analyzed attribute values to the attribute table of the applicable files, or store them in the form of links to file paths, supporting the intuitive presentation and use of applicable file attribute values. The electronic device 100 can also discover file interaction events based on user interactions with files and build a file interaction information database. Based on this database, the electronic device 100 can extract attribute values related to file interaction events when extracting user attribute values, making the file attributes extracted by the electronic device 100 more closely aligned with the user's memory. This improves the efficiency of file extraction, enabling users to locate target files more quickly or eliminate incorrect folders.
[0151] The exemplary electronic device 100 provided in the embodiments of this application will be described next. Figure 13 is a schematic diagram of the hardware structure of the electronic device 100 provided in the embodiments of this application.
[0152] Electronic device 100 may include: processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.
[0153] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0154] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.
[0155] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.
[0156] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.
[0157] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.
[0158] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180K, charger, flash, camera 193, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180K through the I2C interface, enabling the processor 110 and the touch sensor 180K to communicate through the I2C bus interface, thereby realizing the touch function of the electronic device 100.
[0159] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to enable the function of answering phone calls through a Bluetooth headset.
[0160] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering phone calls through a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.
[0161] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to enable music playback through Bluetooth headphones.
[0162] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to enable the electronic device 100 to capture images. The processor 110 and the display screen 194 communicate via the DSI interface to enable the electronic device 100 to display images.
[0163] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to a camera 193, a display screen 194, a wireless communication module 160, an audio module 170, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.
[0164] The SIM interface can be used to communicate with the SIM card interface 195 to transmit data to or read data from the SIM card.
[0165] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, USB Type-C port, etc. USB port 130 can be used to connect a charger to charge electronic device 100, and can also be used for data transfer between electronic device 100 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.
[0166] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this application are merely illustrative and do not constitute a structural limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.
[0167] The charging management module 140 is used to receive charging input from the charger. The charger can be a wireless charger or a wired charger.
[0168] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.
[0169] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.
[0170] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antenna 1 can be multiplexed as a diversity antenna for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.
[0171] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 100. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.
[0172] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.
[0173] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.
[0174] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).
[0175] Electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.
[0176] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a Miniled LED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.
[0177] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.
[0178] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and color. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.
[0179] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.
[0180] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 100 selects a frequency, the DSP can perform Fourier transforms on the frequency energy.
[0181] Video codecs are used to compress or decompress digital video. Electronic device 100 may support one or more video codecs. Thus, electronic device 100 can play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.
[0182] An NPU (Neural Processing Unit) is a computational processor for neural networks (NNs). By borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it can rapidly process input information and continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.
[0183] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.
[0184] Internal memory 121 can be used to store computer executable program code, which includes instructions. Processor 110 executes various functional applications and data processing of electronic device 100 by running the instructions stored in internal memory 121. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as facial recognition, fingerprint recognition, mobile payment, etc.). The data storage area may store data created during the use of electronic device 100 (such as facial information template data, fingerprint information templates, etc.). Furthermore, internal memory 121 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc.
[0185] Electronic device 100 can implement audio functions, such as music playback and recording, through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.
[0186] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.
[0187] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or make hands-free calls through the speaker 170A.
[0188] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 100 answers a telephone call or voice message, the receiver 170B can be brought close to the ear to listen to the voice.
[0189] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic device 100 may have at least one microphone 170C. In some embodiments, electronic device 100 may have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 100 may also have three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.
[0190] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.
[0191] Pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, pressure sensor 180A can be disposed on display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, and capacitive pressure sensors. A capacitive pressure sensor may include at least two parallel plates with conductive material. When force is applied to pressure sensor 180A, the capacitance between the electrodes changes. Electronic device 100 determines the pressure intensity based on the change in capacitance. When a touch operation is applied to display screen 194, electronic device 100 detects the intensity of the touch operation based on pressure sensor 180A. Electronic device 100 can also calculate the touch position based on the detection signal from pressure sensor 180A. In some embodiments, touch operations applied to the same touch position but with different touch operation intensities can correspond to different operation commands. For example, when a touch operation with an intensity less than a first pressure threshold is applied to the SMS application icon, a command to view an SMS is executed. When a touch operation with an intensity greater than or equal to the first pressure threshold is applied to the SMS application icon, a command to create a new SMS is executed.
[0192] The gyroscope sensor 180B can be used to determine the motion attitude of the electronic device 100. In some embodiments, the gyroscope sensor 180B can determine the angular velocity of the electronic device 100 about three axes (i.e., the x, y, and z axes). The gyroscope sensor 180B can be used for image stabilization. For example, when the shutter is pressed, the gyroscope sensor 180B detects the angle of the shake of the electronic device 100, calculates the distance that the lens module needs to compensate based on the angle, and allows the lens to counteract the shake of the electronic device 100 by moving in the opposite direction, thus achieving image stabilization. The gyroscope sensor 180B can also be used in navigation and motion-sensing game scenarios.
[0193] The barometric pressure sensor 180C is used to measure air pressure. In some embodiments, the electronic device 100 calculates altitude using the air pressure value measured by the barometric pressure sensor 180C to assist in positioning and navigation.
[0194] The magnetic sensor 180D includes a Hall sensor. The electronic device 100 can use the magnetic sensor 180D to detect the opening and closing of the flip cover. In some embodiments, when the electronic device 100 is a flip phone, the electronic device 100 can detect the opening and closing of the flip cover using the magnetic sensor 180D. Then, based on the detected opening and closing state of the cover or the flip cover, features such as automatic flip unlocking can be set.
[0195] The 180E accelerometer can detect the magnitude of acceleration of electronic device 100 in various directions (typically three axes). When electronic device 100 is stationary, it can detect the magnitude and direction of gravity. It can also be used to identify the posture of electronic devices and applied to applications such as screen orientation switching and pedometers.
[0196] A distance sensor 180F is used to measure distance. Electronic device 100 can measure distance via infrared or laser. In some embodiments, during a shooting scene, electronic device 100 can utilize the distance sensor 180F to measure distance for rapid focusing.
[0197] The proximity sensor 180G may include, for example, a light-emitting diode (LED) and a light detector, such as a photodiode. The LED may be an infrared LED. The electronic device 100 emits infrared light outward through the LED. The electronic device 100 uses the photodiode to detect infrared reflected light from nearby objects. When sufficient reflected light is detected, it can be determined that there is an object near the electronic device 100. When insufficient reflected light is detected, the electronic device 100 can determine that there is no object near the electronic device 100. The electronic device 100 may use the proximity sensor 180G to detect when a user holds the electronic device 100 close to their ear for a call, so as to automatically turn off the screen to save power. The proximity sensor 180G can also be used in holster mode and pocket mode for automatic unlocking and locking of the screen.
[0198] The ambient light sensor 180L is used to sense the brightness of ambient light. The electronic device 100 can adaptively adjust the brightness of the display screen 194 based on the sensed ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also work with the proximity sensor 180G to detect whether the electronic device 100 is in a pocket to prevent accidental touches.
[0199] The fingerprint sensor 180H is used to collect fingerprints. The electronic device 100 can utilize the characteristics of the collected fingerprints to achieve fingerprint unlocking, accessing application locks, taking photos with fingerprints, answering calls with fingerprints, etc.
[0200] Temperature sensor 180J is used to detect temperature. In some embodiments, electronic device 100 uses the temperature detected by temperature sensor 180J to execute a temperature handling strategy. For example, when the temperature reported by temperature sensor 180J exceeds a threshold, electronic device 100 performs thermal protection by reducing the performance of a processor located near temperature sensor 180J to reduce power consumption. In other embodiments, when the temperature is below another threshold, electronic device 100 heats battery 142 to prevent abnormal shutdown of electronic device 100 due to low temperature. In still other embodiments, when the temperature is below yet another threshold, electronic device 100 boosts the output voltage of battery 142 to prevent abnormal shutdown due to low temperature.
[0201] Touch sensor 180K, also known as a "touch panel," can be located on display screen 194. The touch sensor 180K and display screen 194 together form a touchscreen, also known as a "touch screen." Touch sensor 180K detects touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through display screen 194. In other embodiments, touch sensor 180K may also be located on the surface of electronic device 100, in a different position than display screen 194.
[0202] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100.
[0203] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.
[0204] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.
[0205] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and detach from the electronic device 100. The electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, and other SIM cards. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 100 interacts with the network through the SIM card to realize functions such as calls and data communication.
[0206] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.
[0207] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if...", "after...", "in response to determining...", or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is interpreted as meaning "if determining...", "in response to determining...", "when (the stated condition or event) is detected", or "in response to detecting (the stated condition or event)".
[0208] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.
[0209] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.
Claims
1. A method for managing file attributes, characterized in that, The method is applied to a first electronic device, and the method includes: Display the default attribute information of N files stored in the electronic device, where N is a positive integer; The system receives user input information, which differs from the default attribute information of the N files. Display custom attributes of M files, the custom attributes corresponding to the input information, where M is a positive integer less than or equal to N.
2. The method according to claim 1, characterized in that, After receiving the user's input information, the method further includes: The custom attributes are analyzed based on the input information. The custom attributes include: connotation attributes, extension attributes, and interaction attributes. The connotation attributes are attributes extracted from the file content. The extension attributes are attributes derived from file association information stored in the server. The file association information is not included in the file content. The interaction attributes are attributes extracted from the user's operation records on the file.
3. The method according to claim 1 or 2, characterized in that, Display custom attributes for M files, including: Based on the input information, the target file category is determined; Based on the target file category, select the M files from the N files; Display the custom attributes of the M files.
4. The method according to claim 3, characterized in that, Display the custom attributes of the M files, specifically including: Based on the input information, the custom attribute is determined to be an intrinsic attribute; Extract the intrinsic attributes of each of the M files from their contents; Display the intrinsic attributes of the M files.
5. The method according to claim 3, characterized in that, Display the custom attributes of the M files, specifically including: Based on the input information, the custom attribute is determined to be the extended attribute; The extended attributes of the M files are obtained from the server, and the access method of the server is pre-stored in the electronic device, or the access method of the server is specified by the user's second input information; Display the extension attributes of the M files.
6. The method according to claim 3, characterized in that, Display the custom attributes of the M files, specifically including: Based on the input information, the custom attribute is determined to be an interactive attribute; Obtain L interaction information corresponding to the M files in the file interaction information database, and obtain the interaction attributes of the M files from the L interaction information. The L interaction information is used to record the operations performed by the user on the M files, and L is greater than or equal to M. Display the interactive properties of the M files.
7. The method according to claim 6, characterized in that, The M files include a first file, and the L interactive information pieces include the first interactive information. Before displaying the interactive attributes of the M files, the method further includes: Upon receiving a user's first operation on the first file, first interaction information is generated. The first interaction information is used to record the first operation and the application corresponding to the first operation. The first operation includes one or more of screen sharing, sharing, downloading, editing, and referencing. The first interaction information is stored in the file interaction information library.
8. The method according to any one of claims 1-7, characterized in that, After displaying the custom attributes of M files, the method further includes: Extract custom attributes from K files in the first electronic device, wherein the storage paths of the K files are different from the storage paths of the N files; Save the custom attributes of the K files; Receive the first input information from the user and display the custom attributes of the K files.
9. The method according to any one of claims 1-8, characterized in that, After displaying the custom attributes of M files, the method further includes: Perform attribute value operations on the custom attributes of the M files, including one or more of filtering, sorting, and calculation.
10. An electronic device, characterized in that, include: A processor and a memory, the memory being coupled to the processor, the memory being used to store computer program code, the computer program code including computer instructions, which, when the processor reads the computer instructions from the memory, cause the electronic device to perform the method as described in any one of claims 1-9.
11. A chip system applied to an electronic device, the chip system comprising one or more processors, characterized in that, The processor is used to invoke computer instructions to cause the execution of the method as described in any one of claims 1-9.
12. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program that, when run on an electronic device, causes the electronic device to perform the method as described in any one of claims 1-9.
13. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the electronic device to perform the method as described in any one of claims 1-9.