Permission management method, electronic device and server

Abstract

Provided in the present application are a permission management method, an electronic device and a server. The method comprises: in response to a first operation of a user, a first electronic device setting the permission of a first file in the first electronic device to a first permission; the first electronic device determining a second file on the basis of the first permission, to which the permission of the first file is set, wherein the second file is a file related to the first file; and the first electronic device triggering permission setting for the second file. By means of the design, after the user sets the permission of the first file, the first electronic device can determine the second file related to the first file and trigger permission setting for the second file, so that the permissions of a plurality of related files can be synchronously managed without the need for manually setting the permissions of the related files in sequence by the user, thereby strengthening file permission management and ensuring user data security.

Description

Rights management method, electronic device and server

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on December 18, 2023, with application number 202311754662.3 and application name "A Rights Management Method, Electronic Device and Server", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of Internet technology, and in particular to a rights management method, electronic device, and server. Background Art

[0004] With the advent of the information age, a large number of files will be generated in daily production and life scenarios, which puts higher demands on the file management capabilities of electronic devices. Users hope to have strict permission control over their files to avoid data resource leakage. However, in the current file management method, permissions can only be set for single-point files. For example, assuming that a copy of a file is stored in an electronic device, the user sets permissions for the original file but does not set permissions for the copy of the file, then the user cannot achieve the purpose of permission control over the content of the file. In summary, the current file management solution has the problem of insufficient permission control. Summary of the Invention

[0005] The present application provides a permission management method, electronic device and server, which are used to provide a convenient permission management method for related files to enhance the file permission management strength.

[0006] In a first aspect, the present application provides a permission management method that can be performed by a first electronic device. The method includes: in response to a first user operation, the first electronic device sets the permission of a first file in the first electronic device to the first permission; the first electronic device determines a second file based on setting the permission of the first file to the first permission, where the second file is a file related to the first file; and the first electronic device triggers the setting of permissions for the second file.

[0007] In the above method, after the user sets the first file permissions, the first electronic device can determine the second file related to the first file and trigger the setting of the second file permissions, thereby eliminating the need for the user to manually set the permissions of multiple related files in turn, and achieving synchronous management of the permissions of related files, thereby enhancing the file permission management and ensuring user data security.

[0008] In one possible design, determining the second file based on setting the permission of the first file to the first permission includes: after setting the permission of the first file to the first permission, determining the second file that is identical or similar to the first file according to a preset rule.

[0009] Through this design, after the first electronic device sets the first file permission to the first permission according to the user operation, it can search for a second file that is identical or similar to the first file according to preset rules to confirm whether there is a file related to the first file, thereby ensuring the comprehensiveness of permission management.

[0010] In one possible design, the triggering of setting permissions for the second file includes: triggering setting permissions for the second file to the first permissions; or triggering setting permissions for the second file to second permissions, where the second permissions are permissions set by the user or permissions configured by the system.

[0011] Optionally, the second permission may be the same as or different from the first permission. When the second permission is different from the first permission, the second permission may be a permission related to the first permission, such as the second permission may be a subset of the first permission.

[0012] Through this design, the first electronic device can directly set the permissions of the second file to the first permissions or system-configured permissions, or it can trigger a message to remind the user to set the permissions of the second file, and the user can set the permissions of the second file, thereby flexibly implementing permission management of related files.

[0013] In one possible design, determining the second file based on setting the permission of the first file to the first permission includes: in response to the user's second operation, determining the second file in at least one candidate file, the at least one candidate file being a file related to the first file.

[0014] Optionally, the second operation may be an operation of the user selecting the second file from at least one candidate file.

[0015] Through this design, the first electronic device can determine at least one candidate file related to the first file, and the user can select a second file from the at least one candidate file, so that the first electronic device can set permissions for the second file selected by the user, meeting the user's needs to simultaneously set permissions for multiple related files.

[0016] In one possible design, the at least one candidate file includes at least one of a file related to the first file in the first electronic device and a file related to the first file in the second electronic device.

[0017] Through this design, the files related to the first file determined by the first electronic device can be files in this device or files in other devices, so that files related to the first file can be searched more comprehensively and cross-device file permission management can be realized.

[0018] In one possible design, the method further includes: determining at least one candidate file from at least one file to be compared based on file features of the first file, wherein the similarity between the file features of the at least one candidate file and the file features of the first file satisfies a preset condition; and the at least one file to be compared comes from at least one of the first electronic device, the second electronic device, and the server.

[0019] With this design, the first electronic device can perform a file feature comparison on at least one file to be compared based on the file features of the first file to determine files related to the first file. In the rights management method provided by this application, the at least one file to be compared can come from at least one of the first electronic device, the second electronic device, and the server, thereby enabling cross-device retrieval of similar files and further ensuring user data security.

[0020] In one possible design, determining at least one candidate file from at least one file to be compared based on the file feature of the first file includes: determining at least one pending file from at least one file stored in the first electronic device based on the first file feature of the first file; and determining a ninth file from the at least one pending file based on the second file feature of the first file, the ninth file being one of the at least one candidate file.

[0021] With this design, when determining at least one candidate file related to the first file, the first electronic device can perform a two-step file feature comparison based on the first file feature and the second file feature of the first file to improve the accuracy of similar file retrieval.

[0022] Optionally, the first file feature may be a file feature that is easier to obtain than the second file feature.

[0023] Optionally, when determining at least one candidate file related to the first file, the first electronic device may also perform a one-step comparison based on the first file feature of the first file to obtain at least one candidate file, so that the first electronic device does not need to extract and store the second file feature of the first file and the second file feature of the file to be compared, thereby saving computing power and storage space of the first electronic device.

[0024] In a possible design, the file feature of the first file includes at least one of the following: a keyword, a key word, an optical character recognition (OCR) feature, a picture feature, a file paragraph feature, and a long text feature.

[0025] In one possible design, the method also includes: sending a first message to a server or a second electronic device, the first message being used to request determination of files related to the first file; and receiving information of a fourth file sent by the server or the second electronic device, the fourth file being one of the at least one candidate file.

[0026] Through this design, the first electronic device can also send a first message to the server or the second electronic device to request the server or the second electronic device to determine files related to the first file, thereby realizing cross-device related file retrieval, further enhancing the strength of file permission management, and ensuring user data security.

[0027] In a possible design, the information of the fourth file includes at least one of a file identifier of the fourth file, a file summary of the fourth file, and data of the fourth file.

[0028] Through this design, after determining the fourth file related to the first file, the server or the second electronic device can send information about the fourth file, such as the file identifier, file summary or data of the fourth file, to the first electronic device, so that the first electronic device can determine the file related to the first file in the second electronic device.

[0029] In one possible design, the method also includes: sending a first message to a server or a second electronic device, the first message being used to request determination of files related to the first file; receiving information of a fifth file sent by the server or the second electronic device; and determining that the fifth file is one of the at least one candidate file based on file features of the first file and information of the fifth file.

[0030] Through this design, after the first electronic device requests the server or the second electronic device to determine the files related to the first file, it receives the fifth file sent by the server or the second electronic device. The first electronic device can then compare the file features of the fifth file based on the file features of the first file to determine that the fifth file is a file related to the first file, thereby further improving the accuracy of file retrieval.

[0031] In one possible design, the triggering of setting permissions for the second file includes: setting permissions for the second file; or sending a second message to the server or the second electronic device, where the second message is used to request setting permissions for the second file.

[0032] Through this design, when the second file belongs to the first electronic device, the first electronic device can set permissions for the second file; when the second file belongs to the second electronic device, the first electronic device can send a second message to the server or the second electronic device to request to set permissions for the second file, thereby realizing file permission management of this device and file permission management across devices.

[0033] In one possible design, before the triggering of setting permissions for the second file, the method further includes: displaying a first reminder message, where the first reminder message is used to inquire whether to synchronously set permissions for the second file.

[0034] With this design, the first electronic device can display a reminder message to ask the user whether to set permissions for the second file before setting permissions for the second file, and can set permissions for the second file only after the user confirms the need to set permissions for the second file, thereby improving user experience.

[0035] In one possible design, the first reminder message includes information about the second file and information about the electronic device to which the second file belongs.

[0036] Through this design, the first electronic device can display the information of the second file and the information of the electronic device described in the second file in the reminder message, so that the user can intuitively see the file and its location, which makes it easier for the user to confirm which files to synchronize and set permissions, thereby improving the user experience.

[0037] In one possible design, the method further includes: determining that a third electronic device is online, and a sixth file in the third electronic device is a file related to the first file; and triggering setting permissions for the sixth file.

[0038] Through this design, the first electronic device can trigger the setting of permissions for the sixth file related to the first file in the third electronic device when determining that the third electronic device is online, further enhancing the strength of cross-device file permission management and ensuring user data security.

[0039] In one possible design, before the triggering of setting permissions for the sixth file, the method further includes: displaying a second reminder message, where the second reminder message is used to inquire whether to set permissions for the sixth file.

[0040] In one possible design, the method further includes: in response to a third operation of the user, setting the permission of the first file to a third permission; and triggering setting of permissions for the second file.

[0041] Optionally, the third operation may be an operation triggered by a user to modify permissions of the first file.

[0042] With this design, when a user modifies the permissions of a first file, the first electronic device can trigger permission settings for a second file, thereby achieving synchronous permission management of related files.

[0043] In one possible design, the second file belongs to the first electronic device, and the method further includes: in response to a fourth operation of the user, setting the permission of the second file to a fourth permission.

[0044] With this design, after the first electronic device triggers the setting of permissions for the second file, the user can modify the permissions for the second file again, thereby flexibly meeting the user's permission management needs.

[0045] In one possible design, the method further includes: triggering setting permissions for the first file.

[0046] Optionally, before triggering the setting of permissions for the first file, the method further includes: displaying a fourth reminder message, where the fourth reminder message is used to inquire whether to set permissions for the first file.

[0047] With this design, the first electronic device can also trigger setting permissions for the first file after the user modifies the permissions of the second file, thereby achieving synchronous permission management of related files.

[0048] In one possible design, the method also includes: receiving a third message sent by a third electronic device, the third message being used to request determination of files related to a seventh file in the third electronic device; determining files related to the seventh file from files stored in the first electronic device based on file characteristics of the seventh file; and sending information about files related to the seventh file to the third electronic device.

[0049] Through this design, the first electronic device can also receive a third message sent by other electronic devices, such as a third electronic device, to determine the files in the first electronic device that are related to the seventh file in the third electronic device, so as to assist the third electronic device in performing file permission management across devices.

[0050] In one possible design, the method also includes: receiving a fourth message sent by a third electronic device, the fourth message being used to request setting the permission of an eighth file in the first electronic device to a fifth permission; and setting the permission of the eighth file to the fifth permission.

[0051] Through this design, the first electronic device can receive other electronic devices, such as the fourth message sent by the third electronic device, to set permissions for the eighth file related to the seventh file in the first electronic device, assisting the third electronic device to complete cross-device file permission management and ensure user data security.

[0052] Optionally, the first electronic device, the second electronic device, and the third electronic device may be electronic devices associated with the same user account.

[0053] In a second aspect, the present application provides a rights management method that can be executed by a server. The method includes: the server receiving a first message sent by a first electronic device, the first message being used to request the determination of files related to a first file in the first electronic device; and the server sending information about a fourth file to the first electronic device, the fourth file being a file related to the first file.

[0054] In the above method, the server can receive a message sent by the first electronic device requesting to determine the files related to the first file, and send the information of the fourth file related to the first file determined to the first electronic device, assisting the first electronic device to complete the relevant file retrieval across devices, and then realize the synchronous management of relevant file permissions across devices to ensure user data security.

[0055] In a possible design, the information of the fourth file includes at least one of a file identifier of the fourth file, a file summary of the fourth file, and data of the fourth file.

[0056] In one possible design, the method also includes: receiving a second message sent by the first electronic device, the second message being used to request setting permissions for a second file; and sending a fifth message to a second electronic device, the fifth request message being used to request setting permissions for the second file, the second electronic device being the electronic device described in the second file.

[0057] Through this design, the server can receive a message sent by the first electronic device requesting to set permissions for the second file, and send a fifth message to the second electronic device to which the second file belongs to request the second electronic device to set permissions for the second file, thereby completing the relevant file permission management across devices.

[0058] In one possible design, before sending the information of the fourth file to the first electronic device, the method further includes: determining the fourth file based on file features of the first file and file features of at least one file stored on the server, wherein the similarity between the file features of the fourth file and the file features of the first file meets a preset condition.

[0059] In a possible design, the file feature of the first file includes at least one of the following: a keyword, a key word, an optical character recognition (OCR) feature, a picture feature, a file paragraph feature, and a long text feature.

[0060] In one possible design, determining the fourth file based on the file characteristics of the first file and the file characteristics of at least one file stored on the server includes: determining at least one pending file based on the first file characteristics of the first file and the file characteristics of at least one file stored on the server; sending the file identifier of the at least one pending file to a second electronic device corresponding to the at least one pending file, receiving the at least one pending file sent by the second electronic device, and determining the fourth file from the at least one pending file based on the second file characteristics of the first file, the fourth file being one of the at least one candidate file.

[0061] With this design, the server can store file features of multiple files. After receiving the file features of a first file sent by a first electronic device, the server compares the file features of the multiple files stored in the server with the file features of the first file to determine at least one pending file related to the first file. The server can then obtain at least one pending file from the second electronic device and further compare the at least one pending file with the first file to determine at least one candidate file related to the first file, thereby ensuring the accuracy of similar file retrieval.

[0062] In a third aspect, the present application provides a method for deleting related files, which can be executed by a first electronic device, and the method includes: the first electronic device deletes a first file in the first electronic device in response to a fifth operation of the user; the first electronic device determines a second file based on deleting the first file, and the second file is a file related to the first file; the first electronic device triggers the deletion of the second file.

[0063] In the above method, after the user deletes the first file, the first electronic device can simultaneously delete the second file related to the first file, thereby eliminating the need for the user to repeatedly search for and delete related files, thereby improving user experience.

[0064] In one possible design, before triggering deletion of the second file, the method further includes: displaying a third reminder message, where the third reminder message is used to inquire whether to synchronously delete the second file.

[0065] Through this design, the first electronic device can display a third reminder message to ask the user whether to delete the second file before triggering the deletion of the second file, and then delete the second file after the user confirms, so as to meet the user's file management needs and improve the user experience.

[0066] In a fourth aspect, the present application provides an electronic device comprising multiple functional modules; the multiple functional modules interact with each other to implement the method performed by the first electronic device or the second electronic device in any of the above aspects and their respective embodiments. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on the specific implementation.

[0067] In a fifth aspect, the present application provides an electronic device comprising at least one processor and at least one memory, wherein the at least one memory stores computer program instructions. When the electronic device is running, the at least one processor executes the method executed by the first electronic device or the second electronic device in any of the above aspects and each embodiment thereof.

[0068] In a sixth aspect, the present application provides a server comprising multiple functional modules; the multiple functional modules interact with each other to implement the method performed by the server in any of the above aspects and their respective embodiments. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on the specific implementation.

[0069] In the seventh aspect, the present application provides a server comprising at least one processor and at least one memory, wherein the at least one memory stores computer program instructions. When the server is running, the at least one processor executes the server execution method in any of the above aspects and its various embodiments.

[0070] In an eighth aspect, the present application provides a file management system, which includes an electronic device and a server. The electronic device can be used to execute the method executed by the first electronic device or the second electronic device in any of the above aspects and its various embodiments, and the server can be used to execute the method executed by the server in any of the above aspects and its various embodiments.

[0071] In a ninth aspect, the present application also provides a computer program product comprising instructions, which, when run on a computer, enables the computer to execute the method executed by the server or electronic device in any of the above aspects and its various embodiments.

[0072] In the tenth aspect, the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a computer, the computer executes the method executed by the server or electronic device in any of the above aspects and its various embodiments.

[0073] In the eleventh aspect, the present application also provides a chip, which is used to read the computer program stored in the memory and execute the method executed by the server or electronic device in any of the above aspects and its various embodiments.

[0074] In a twelfth aspect, the present application further provides a chip system, comprising a processor for supporting a computer device in implementing the method executed by a server or electronic device in any of the above aspects and their respective embodiments. In one possible design, the chip system further comprises a memory for storing programs and data necessary for the computer device. The chip system may be composed of a chip or may include a chip and other discrete devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0075] FIG1 is a schematic diagram of the architecture of a file management system provided in an embodiment of the present application;

[0076] FIG2 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

[0077] FIG3 is a software structure block diagram of an electronic device provided in an embodiment of the present application;

[0078] FIG4 is a schematic structural diagram of an electronic device provided in an embodiment of the present application;

[0079] FIG5 is a flowchart of a first rights management method provided in an embodiment of the present application;

[0080] FIG6 is a schematic diagram of setting file permissions according to an embodiment of the present application;

[0081] FIG7 is a schematic diagram of an interface for displaying a reminder message provided in an embodiment of the present application;

[0082] FIG8 is a schematic diagram of a display interface provided in an embodiment of the present application;

[0083] FIG9 is a flowchart of a first rights management method provided in an embodiment of the present application;

[0084] FIG10 is a schematic diagram of the structure of a file management system provided in an embodiment of the present application;

[0085] FIG11 is a flowchart of a second rights management method provided in an embodiment of the present application;

[0086] FIG12 is a schematic diagram of an interface for displaying a reminder message provided in an embodiment of the present application;

[0087] FIG13 is a schematic diagram of a display interface of an electronic device provided in an embodiment of the present application;

[0088] FIG14 is a flowchart of a second rights management method provided in an embodiment of the present application;

[0089] FIG15 is a schematic diagram of the structure of a file management system provided in an embodiment of the present application;

[0090] FIG16 is a flowchart of a third rights management method provided in an embodiment of the present application;

[0091] FIG17 is a flowchart of a third rights management method provided in an embodiment of the present application;

[0092] FIG18 is a flow chart of a method for synchronously deleting related files provided in an embodiment of the present application;

[0093] Figure 19 is a flowchart of an improved permission management method according to an embodiment of the present application. DETAILED DESCRIPTION

[0094] In order to make the purpose, technical solutions and advantages of the embodiments of the present application more clear, the embodiments of the present application will be further described in detail below with reference to the accompanying drawings. In the description of the embodiments of the present application, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features.

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

[0096] With the advent of the information age, a large number of files will be generated in daily production and life scenarios, which puts higher demands on the file management capabilities of electronic devices. Users hope to have strict permission control over their files to avoid data resource leakage. Based on the current file management method, users can set permissions for single-point files. For example, users can set file permissions to read-only, encryption, restricted editing, etc. However, in the current file management method, permissions can only be set for single-point files. For example, assuming that a copy of a file is stored in an electronic device, the user sets permissions for the original file, but does not set permissions for the copy of the file, then the user cannot achieve the purpose of permission control over the content of the file. In summary, the current file management solution has the problem of insufficient permission control.

[0097] To address the above issues, an embodiment of the present application provides a file management system. FIG1 is a schematic diagram of the architecture of a file management system provided by an embodiment of the present application. Referring to FIG1 , the file management system may include at least one electronic device, such as electronic device 1 and electronic device 2, as shown in FIG1 . The file management system may also include a server.

[0098] Figure 1 shows the possible structure of the electronic device and the server in the embodiment of the present application. Referring to Figure 1, the electronic device may include a file management module, a permission setting module, a feature extraction module, an associated file identification module, a local file feature library, and a remote comparison module. Among them, the file management module can be used to perform user-triggered operations such as creating, editing, modifying, and saving files. The permission setting module can be used to provide users with an entry for setting file permissions. After the user sets the file permissions, the permission setting module can obtain the permissions set by the user and set the file permissions according to the permissions selected by the user. The feature extraction module can be used to extract file features. The associated file identification module can be used to find files associated with the file based on the file features. The local file feature library is used to store the file features of local files. The remote comparison module is used to extract the file features of the file sent by the remote device, and to identify whether the file sent by the remote device and the local file are associated files based on the file features.

[0099] Referring to Figure 1 , a server may include a file feature library, an associated file identification module, and a file scanning module. The file feature library is used to store file features. Optionally, the file features may be uploaded to the server by an electronic device. Alternatively, the server may also include a feature extraction module that extracts features from the files uploaded by the electronic device to obtain the file features. The associated file identification module is used to search for files associated with the file based on the file features. The file scanning module is used to search for files based on file identifiers.

[0100] It should be noted that the structure of each device in the file management system shown in Figure 1 is only an example and not a limitation. The scenario to which the rights management method provided in the embodiment of the present application is applicable may have more or fewer devices than the file management system shown in Figure 1. For example, the rights management method provided in the embodiment of the present application can be executed by an electronic device, or executed by an electronic device interacting with an electronic device, or executed by at least one electronic device interacting with a server. The embodiment of the present application does not limit this. The specific implementation method can be found in the following embodiment, which is not described in detail here. In addition, it is understandable that in different scenarios, the electronic device or server may also have more or fewer modules than the structure shown in Figure 1, or the module division may be performed according to other division methods in the specific implementation, and the embodiment of the present application does not limit this.

[0101] The following describes electronic devices and embodiments for using such electronic devices. The electronic devices of the embodiments of the present application may be tablet computers, mobile phones, in-vehicle devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), wearable devices, etc. The embodiments of the present application do not impose any restrictions on the specific types of electronic devices.

[0102] In some embodiments of the present application, the electronic device may also be a portable terminal device that also includes other functions such as a personal digital assistant and / or a music player. Or portable terminal devices with other operating systems.

[0103] Figure 2 is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of the present application. As shown in Figure 2, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195.

[0104] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors. The controller may serve as the nerve center and command center of the electronic device 100. The controller may generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution. The processor 110 may also include memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a high-speed cache memory. This memory may store instructions or data that have just been used or are being recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids duplicate accesses, reduces the processor 110's waiting time, and thus improves system efficiency.

[0105] The USB interface 130 is an interface that complies with USB standards and specifications, and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the electronic device 100, and can also be used to transfer data between the electronic device 100 and peripheral devices. The charging management module 140 is used to receive charging input from the charger. 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, and provides power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160.

[0106] The wireless communication functionality of electronic device 100 can be implemented using antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, a modem processor, and a baseband processor. 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 a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0107] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0108] The wireless communication module 160 can provide wireless communication solutions 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), infrared (IR), etc., which are applied to the electronic device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0109] In some embodiments, the antenna 1 of the electronic device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the electronic device 100 can communicate with a network and other devices through wireless communication technologies. The wireless communication technologies 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 technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

[0110] The display screen 194 is used to display the display interface of the application, such as displaying the display page of the application installed on the electronic device 100. 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 or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, 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 one.

[0111] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. 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, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0112] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, and the software code of at least one application, etc. The data storage area can store data generated during the use of the electronic device 100 (such as captured images, recorded videos, etc.). In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0113] The external memory 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. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as pictures and videos can be stored on the external memory card.

[0114] The electronic device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0115] Among them, the sensor module 180 may include a pressure sensor 180A, an acceleration sensor 180B, a touch sensor 180C, etc.

[0116] The pressure sensor 180A is used to sense the pressure signal and convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be disposed on the display screen 194 .

[0117] Touch sensor 180C, also known as a "touch panel," can be disposed on display screen 194. The touch sensor 180C and display screen 194 form a touch screen, also known as a "touch screen." Touch sensor 180C is used to detect touch operations applied thereto or in the vicinity thereof. The touch sensor can transmit the detected touch operations to an application processor to determine the type of touch event. Visual output related to the touch operations can be provided via display screen 194. In other embodiments, touch sensor 180C can also be disposed on the surface of electronic device 100, at a location different from that of display screen 194.

[0118] The buttons 190 include a power button, a volume button, etc. The button 190 can be a mechanical button. It can also be a touch button. The electronic device 100 can receive button input and generate key signal input related to the user settings and function control of the electronic device 100. The motor 191 can generate a vibration prompt. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization. The indicator 192 can be an indicator light, which can be used to indicate the charging status, power changes, and can also be used to indicate messages, missed calls, notifications, etc. The SIM card interface 195 is used to connect the SIM card. The SIM card can be inserted into the SIM card interface 195 or pulled out from the SIM card interface 195 to achieve contact and separation with the electronic device 100.

[0119] It is understood that the components shown in FIG2 do not constitute a specific limitation on the electronic device 100. The electronic device may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. In addition, the combination / connection relationship between the components in FIG2 may also be adjusted and modified.

[0120] Figure 3 is a block diagram of the software structure of an electronic device provided in an embodiment of the present application. As shown in Figure 3, the software structure of the electronic device can be a layered architecture. For example, the software can be divided into several layers, each with a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer (framework, FWK), the runtime (runtime) and system library, and the kernel layer.

[0121] The application layer may include a series of application packages. As shown in Figure 3, the application layer may include a camera, settings, skin module, user interface (UI), third-party applications, etc. Among them, third-party applications may include gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc. In an embodiment of the present application, the application layer may include a target installation package of a target application that the electronic device requests to download from a server, and the function files and layout files in the target installation package are adapted to the electronic device.

[0122] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer may include some predefined functions. As shown in Figure 3, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, and a file manager. The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, take screenshots, etc. The content provider is used to store and obtain data and make this data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

[0123] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0124] The phone manager is used to provide communication functions for electronic devices, such as call status management (including answering, hanging up, etc.).

[0125] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0126] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0127] The file manager is used to manage files stored in an electronic device. For example, the file manager can manage the permissions of files. In practice, the file manager can manage the permissions of files stored in the electronic device and their associated files based on the file permissions set by the user based on the permission management method provided in the embodiment of the present application. Optionally, the file manager in the embodiment of the present application can include multiple modules in the electronic device in the file management system shown in Figure 1, and implement the functions corresponding to the multiple modules.

[0128] The runtime includes the core library and the virtual machine. The runtime is responsible for the scheduling and management of the operating system.

[0129] The core library consists of two parts: one containing the Java language's callable functions and the other containing the operating system's core libraries. The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0130] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), a 2D graphics engine (e.g., SGL), and an image processing library.

[0131] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0132] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

[0133] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0134] A 2D graphics engine is a drawing engine for 2D drawings.

[0135] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0136] The hardware layer can include various sensors, such as accelerometers, gyroscopes, touch sensors, etc.

[0137] It should be noted that the structures shown in Figures 2 and 3 are merely examples of electronic devices provided in the embodiments of the present application and do not limit the electronic devices provided in the embodiments of the present application. In specific implementations, the electronic device may have more or fewer devices or modules than those in the structures shown in Figures 2 or 3.

[0138] The following is an introduction to the implementation of the permission management method provided by the embodiments of the present application in different application scenarios with reference to the accompanying drawings. Unless otherwise specified below, the steps represented by dotted lines in the accompanying drawings corresponding to the various embodiments of the present application are all optional steps.

[0139] Example 1

[0140] Optionally, when an electronic device executes the rights management method provided in an embodiment of the present application, the architecture of the electronic device may be as shown in FIG4 . Referring to FIG4 , the electronic device may include a file management module, a rights setting module, a feature extraction module, an associated file identification module, and a local file feature library. The functions of each module can be found in the relevant description of FIG1 above, and repeated parts will not be repeated here.

[0141] FIG5 is a flowchart of a first rights management method provided by an embodiment of the present application. The method can be executed by a first electronic device, such as any electronic device in the file management system shown in FIG1. ​​Referring to FIG5, the method may include the following steps:

[0142] S501: The first electronic device extracts file features of a first file.

[0143] Optionally, in response to a user operation, the first electronic device may extract file features of the first file. For example, the user operation may be a user-triggered operation of saving and closing the first file. For example, after the user creates or edits the first file, the content of the first file changes. The user may click a save control to save the modified file content. After the user clicks a close control, the first electronic device may extract file features of the first file.

[0144] Optionally, in the embodiment of the present application, files may include documents, pictures, videos, audios, executable files, scripts, compressed packages, etc. The embodiment of the present application does not limit the type of files.

[0145] In an optional embodiment, the file features may include at least one of the following: keywords, key words, optical character recognition (OCR) features, image features, file paragraph features, long text features, etc. Among them, keywords and key words can be characters or words obtained from the file name or file content, OCR features can be features obtained after performing OCR detection on the file, and image features can be features obtained by extracting features based on the pictures in the file, wherein the pictures can be, for example, micro-logo (logo) pictures, etc. File paragraph features can be features extracted by analyzing the file paragraphs, for example, file paragraph features can include the number of paragraphs contained in the file, the number of words in each paragraph, etc. Long text features can include, for example, file length features, context features, etc. It should be noted that the content included in the file features in the embodiment of the present application is only used as an example and not as a limitation. In specific implementations, file features can also include other features.

[0146] In an embodiment of the present application, after the first electronic device obtains the file features of the first file, it can store the file features of the first file and the file identifier of the first file, where the file identifier of the first file can be, for example, a uniform resource identifier (URI) of the first file or a storage path of the first file. Optionally, the electronic device can store the file features and file identifier of the first file in a local file feature library shown in FIG4 .

[0147] S502: In response to a first operation by the user, the first electronic device sets the permission of the first file to the first permission.

[0148] Optionally, the first operation can be an operation in which the user selects the permission of the first file as the first permission. For example, Figure 6 is a schematic diagram of setting file permissions provided in an embodiment of the present application. Referring to Figure 6, the first electronic device can display a file permission setting interface, and the file permission setting interface includes optional file permissions, such as "read-only", "edit", "encrypt with password", "set permissions by personnel", etc. in Figure 6. The user can select the first permission in the file permission setting interface, and the electronic device sets the permission of the first file to the first permission. If the first permission selected by the user is "read-only", after opening the first file on the first electronic device, the user can only view the first file but cannot edit the first file.

[0149] After setting the permission for the first file to the first permission, the first electronic device may store the access control policy corresponding to the first file. The access control policy corresponding to the first file may include, but is not limited to, at least one of the following: a user account identifier, an expiration date of the first file, the first permission, an account identifier of the authorized user, etc. Optionally, the first electronic device may encrypt the access control policy corresponding to the first file and store the encrypted access control policy, thereby further improving the security of the permission setting.

[0150] It should be noted that, in implementation, the first electronic device may also extract the file features of the first file after setting the permissions of the first file to the first permissions. The embodiment of the present application does not limit the execution order of setting file permissions and extracting file features.

[0151] S503: The first electronic device determines at least one candidate file related to the first file according to the file feature of the first file.

[0152] In an embodiment of the present application, the first electronic device may determine a candidate file related to the first file from at least one file stored in the first electronic device based on the file characteristics of the first file. There may be one or more candidate files.

[0153] In an optional embodiment, the first electronic device may compare the first file and at least one file stored by the first electronic device according to a file comparison method, and determine at least one candidate file from the at least one file stored by the first electronic device. In implementation, the first electronic device may compare the file features of the first file with the file features of the file stored by the first electronic device, determine the similarity between the file features of the first file and the file features of the file stored by the first electronic device, and select files whose similarity meets a preset condition as candidate files. For example, the first electronic device may select files whose similarity is greater than or equal to a preset threshold as candidate files.

[0154] Optionally, the first electronic device may also perform a two-step file feature comparison to improve the accuracy of the determined candidate files. In implementation, the first electronic device may determine at least one pending file from the files stored by the first electronic device based on the first file feature of the first file, wherein the first file feature may include but is not limited to keywords, key words, OCR features, image features, etc. For example, the first electronic device may compare the first file feature of the first file with the file features of the files stored by the first electronic device to determine a first similarity, and use the file whose first similarity is greater than or equal to a first preset threshold as a pending file. The first electronic device may further determine at least one candidate file from at least one pending file based on the second file feature of the first file, wherein the second file feature may include but is not limited to pictures, file paragraph features, long text features, etc. For example, the first electronic device may perform at least one of the following file comparison methods to determine at least one candidate file from at least one pending file:

[0155] Mode 1: The first electronic device may determine a second similarity between the image in the first file and the image in the pending file, and select files whose second similarity is greater than or equal to a second preset threshold as candidate files.

[0156] Method 2: The first electronic device may determine the file paragraph features of the first file and the file paragraph features of the pending file, and determine the degree of match between the file paragraph features of the first file and the file paragraph features of the pending file. The first electronic device may use the file whose matching degree is greater than a third preset threshold as the second file.

[0157] Method 3: The first electronic device may determine a file whose similarity to the first file is greater than a fourth preset threshold based on image OCR and long text similarity detection, and use the determined file as a candidate file.

[0158] It should be noted that the above file comparison method is only an example provided in the embodiment of the present application and is not limiting. In specific implementation, one or a combination of them can be selected, or candidate files related to the first file can be determined based on other file comparison methods. The embodiment of the present application does not limit this.

[0159] In addition, it should be noted that the above-mentioned first file feature may be a file feature that is easier to obtain than the second file feature. In the embodiment of the present application, the second step of file feature comparison is an optional step. During implementation, the first electronic device may use at least one pending file determined by the first step of file feature comparison as at least one candidate file. Then, the first electronic device may not extract the second file feature when extracting the file feature, so as to save the computing power and storage space of the first electronic device.

[0160] It can be understood that the candidate file determined from the files stored in the first electronic device based on the above method is a file related to the first file, for example, the candidate file may be a copy file of the first file.

[0161] Optionally, before executing S503, the first electronic device may also display an inquiry message, which is used to ask the user whether to search for a second file related to the first file. After the user clicks OK, the first electronic device can execute S503, thereby searching for the second file when the user needs to set permissions for similar files, thereby preventing the electronic device from wasting computing power when the user does not set permission requirements.

[0162] S504: The first electronic device displays a reminder message.

[0163] In an optional embodiment, after the first electronic device determines at least one candidate file related to the first file, it can display a reminder message in the first electronic device, and the reminder message is used to ask the user whether to synchronously set permissions for at least one candidate file. The reminder message may include information about the candidate file, such as the reminder message may include the file name of the candidate file, and the user can select the candidate file for which permissions need to be synchronously set.

[0164] For example, Figure 7 is a schematic diagram of an interface for displaying a reminder message provided in an embodiment of the present application. Referring to Figure 7, the first electronic device can display relevant information of the first file for which permission setting has been completed in the reminder message. As shown in Figure 7, the first file is file 1, and the first electronic device displays that the "read-only" permission of the first file corresponds to user 1 and user 2, and the "edit" permission of the first file corresponds to user 3, and the access time is January 1, 2023. The first electronic device can also display the names of the candidate files found in the reminder message. As shown in Figure 7, the candidate files are file 2 and file 3. The user can select file 2 and / or file 3, thereby synchronously setting permissions for the candidate files selected by the user.

[0165] S505: In response to the second operation of the user, the first electronic device sets permissions for the second file.

[0166] Optionally, the second operation is an operation in which the user selects a second file from at least one candidate file, and the second file is part or all of the at least one candidate file.

[0167] In an optional implementation, after the user triggers the second operation and selects the second file, the first electronic device can set the permissions of the second file to the first permissions. After the setting is completed, the permissions of the second file are the same as the permissions of the first file, so that the user does not need to repeat the operation to quickly complete the permission settings of the relevant files, further enhancing the file permission management and control and ensuring the security of user information.

[0168] In another optional implementation, the first electronic device may set the permission of the second file to a second permission. The second permission may be a system-configured permission, or the second permission may be a user-configured permission. For example, the second permission may be a system-configured permission related to the first permission, such as a subset of the first permission.

[0169] That is to say, in the permission management method provided in the embodiment of the present application, after the user selects the second file from at least one candidate file, the first electronic device can directly set the permission of the second file to the first permission or the system configured permission, or it can trigger a message to remind the user to set the permission of the second file, and the user sets the permission of the second file, thereby flexibly realizing the permission management of related files.

[0170] Optionally, after completing the permission setting for the second file, the first electronic device may display a notification message, which is used to notify the user that the permission setting for the second file has been completed. As shown in Figure 8, a schematic diagram of a display interface provided in an embodiment of the present application is shown. Referring to Figure 8, when the user selects File 2 and File 3 in the interface shown in Figure 7, the first electronic device may set the permissions for File 2 and File 3 to the first permission, and the first electronic device may display a notification message that the permission setting for File 1, File 2, and File 3 has been completed.

[0171] In some embodiments, after the first electronic device completes the permission setting for the second file, when the user modifies the permission of the first file again, the first electronic device can trigger the modification of the permission of the second file. For example, if the user modifies the permission of the first file to the third permission, the first electronic device can synchronously modify the permission of the second file to the third permission, or the first electronic device can modify the permission of the second file to the fourth permission, where the fourth permission is a system-configured permission or a user-set permission. Similarly, when the user modifies the permission of the second file, the first electronic device can trigger the modification of the permission of the first file, and the repetitions will not be repeated.

[0172] The first permission management method provided in the embodiment of the present application can be executed by various modules in the first electronic device. When the various modules in the first electronic device shown in FIG4 execute the first permission management method provided in the embodiment of the present application, FIG9 is a flowchart of the first permission management method provided in the embodiment of the present application. Referring to FIG9, the method includes the following steps:

[0173] S901: In response to a user operation, the file management module modifies a first file and saves the modified first file.

[0174] In this embodiment, the user operation may be an operation of modifying and saving the first file by the user.

[0175] S902: The feature extraction module extracts file features of the first file.

[0176] Optionally, the file feature of the first file may include but is not limited to at least one of the following: keywords, key words, OCR features, image features, file paragraph features, long text features, etc.

[0177] S903: The feature extraction module sends the file features of the first file to the local file feature library.

[0178] S904: The local file feature database registers the file feature of the first file or updates the file feature of the first file.

[0179] Optionally, when the local file feature library does not store the file features of the first file, upon receiving the file features of the first file, the local file feature library may register the file features of the first file, thereby storing the file features of the first file and the file identifier of the first file. When the local file feature library already stores the file features of the first file, upon receiving the file features of the first file, the local file feature library may update the file features of the first file in the local file feature library.

[0180] S905: In response to the user's first operation, the file management module sends a first permission setting request message to the permission setting module.

[0181] Optionally, the first operation may be an operation in which the user selects the permission of the first file as the first permission, and the first permission setting request message may be used to request the permission setting module to set the permission of the first file to the first permission.

[0182] S906: The permission setting module sets the permission of the first file as the first permission, and generates an access control policy corresponding to the first file.

[0183] S907: The permission setting module sends a notification message to the file management module.

[0184] The notification message is used to indicate that the permission setting of the first file has been completed, and the notification message may include the access control policy corresponding to the first file.

[0185] S908: The file management module displays an inquiry message.

[0186] Optionally, the inquiry message is used to inquire the user whether to search for files related to the first file.

[0187] S909: In response to the user's operation, the file management module sends an identification request message to the associated file identification module.

[0188] Optionally, the identification request message is used to request the associated file identification module to determine files related to the first file.

[0189] It should be noted that S908-S909 are optional steps. During implementation, the first electronic device may not ask the user whether to search for files related to the first file and automatically execute S910.

[0190] S910: The associated file identification module obtains file features of files stored in the first electronic device from a local file feature library.

[0191] S911: The associated file identification module determines at least one pending file from the files stored in the first electronic device according to the first file feature of the first file and the file features of the files stored in the first electronic device.

[0192] S912: The associated file identification module determines at least one candidate file from at least one pending file according to the second file feature of the first file.

[0193] The specific implementation of S911-S912 can refer to S503, and the repeated parts will not be repeated.

[0194] It should be noted that S912 is an optional step, that is, S912 may not be executed during implementation, and the associated file identification module may use the pending file determined in S911 as a candidate file.

[0195] S913: The associated file identification module sends the file identification of at least one candidate file to the file management module.

[0196] S914: The file management module displays a reminder message.

[0197] The reminder message is used to ask the user whether to synchronously set permissions for the candidate file.

[0198] S915: In response to the user's second operation, the file management module sends a second permission setting request message to the permission setting module.

[0199] Among them, the second operation is an operation in which the user selects a second file from at least one candidate file, and the second permission setting request message is used to request setting permissions for the second file. The second permission setting request message may include a file identifier of the second file. For example, the second permission setting request message can be used to request setting permissions for the second file to the first permission.

[0200] S916: The permission setting module sets permissions for the second file.

[0201] For example, when the permission of the second file is set to the first permission, the permission setting module can obtain the access control policy corresponding to the first file, and generate and store the access control policy corresponding to the second file based on the access control policy corresponding to the first file.

[0202] The following introduces the implementation method of applying the permission management method provided in the embodiments of the present application to multiple electronic devices, among which Example 2 can be applied to a file management system including a server and multiple electronic devices, and in Example 2, the server can be used to search for associated files on different electronic devices under the same user account; Example 3 can be applied to a file management system including multiple electronic devices, and in Example 3, interaction can be performed through the connection established between electronic devices to search for associated files on different electronic devices under the same user account.

[0203] Example 2

[0204] Optionally, when the first electronic device, the second electronic device, and the server execute the rights management method provided in the embodiment of the present application, the architecture of each device can be as shown in Figure 10. Referring to Figure 10, the first electronic device can include a first file management module, a first rights setting module, a feature extraction module, and a first associated file identification module; the second electronic device can include a second file management module, a second rights setting module, and a second associated file identification module; the server can include a file feature library, a third associated file identification module, and a file scanning module. The functions of each module can be found in the relevant introduction of Figure 1 above, and the repeated parts will not be repeated.

[0205] FIG11 is a flowchart of a second rights management method provided by an embodiment of the present application. The method can be performed by a first electronic device, a second electronic device, and a server. For example, the method can be performed by the electronic device and the server in the file management system shown in FIG1 . Referring to FIG11 , the method may include the following steps:

[0206] S1101: In response to a first operation of a user, the first electronic device sets the permission of the first file as a first permission.

[0207] Optionally, the first operation may be an operation in which the user selects the permission of the first file as the first permission.

[0208] S1102: The first electronic device extracts file features of the first file.

[0209] Optionally, the file feature of the first file may include but is not limited to at least one of the following: keywords, key words, OCR features, image features, file paragraph features, long text features, etc.

[0210] S1103: The first electronic device sends a first message to the server.

[0211] Optionally, the first message may be used to request determination of files related to the first file. The first request message may include file characteristics of the first file.

[0212] In an embodiment of the present application, the server can store file features of files uploaded by different electronic devices under the same user account. For example, if the first user account is logged into the first electronic device and the second electronic device, when the first electronic device and the second electronic device upload files and file features of the files to the server, the server can store the file features of the files uploaded by the first electronic device and the second electronic device in the file feature library of the server. For example, after the first electronic device sends the file features of the first file to the server, the server can store the device identification of the first electronic device, the account identification of the first user account, the file identification of the first file, and the file features of the first file. Optionally, the first electronic device can also upload the first file to the server, and the server extracts the file features of the first file.

[0213] S1104: The server determines at least one pending file according to the first file feature of the first file.

[0214] In an optional embodiment, the server may compare the first file feature of the first file with file features in a first file feature library stored on the server to determine a first similarity between the first file feature and the file features in the first file feature library, wherein the first file feature library includes file features uploaded by an electronic device corresponding to a first account, where the first account is a user account logged into the first electronic device. The server may designate as pending files files in the first file feature library those whose first similarity with the first file feature of the first file satisfies a preset condition. For example, the server may designate as pending files files whose first similarity is greater than or equal to a first preset threshold.

[0215] It can be understood that the first file feature library stored in the server includes the file features uploaded by the electronic device corresponding to the first account, so the candidate file determined by the server may be a file stored in the first electronic device or a file stored in other electronic devices logged in to the first account.

[0216] S1105: The server sends the file identifier of the pending file to the second electronic device.

[0217] Optionally, after determining at least one pending file, the server can determine a second electronic device based on the device identifier corresponding to the at least one pending file, where the second electronic device stores the pending file, and the server can send the file identifier of the at least one pending file to the second electronic device.

[0218] S1106: The second electronic device uploads the pending file to the server.

[0219] In an embodiment of the present application, after receiving the file identifier of the pending file sent by the server, the second electronic device can search for the pending file from the file system of the second electronic device according to the file identifier of the pending file and upload the pending file to the server.

[0220] In some embodiments, when the server has stored the pending file, S1105-S1106 are optional steps. The server can search for the pending file according to the file identifier of the pending file from the files stored on the server and then execute S1107. This embodiment of the present application does not limit this.

[0221] S1107: The server determines at least one candidate file related to the first file from at least one pending file according to the second file feature of the first file.

[0222] Optionally, the server may obtain file features of the pending file and determine at least one candidate file from the at least one pending file based on the second file feature of the first file and the file features of the pending file. For example, the server may determine the at least one candidate file based on at least one of image similarity, file paragraph matching, or image OCR and long text similarity. The above file comparison method can be found in the description of S503, and repeated parts are not repeated here.

[0223] In some embodiments, S1105-S1107 are optional steps, and the server may also directly use the at least one pending file as the at least one candidate file without performing a file comparison between the at least one pending file and the first file.

[0224] S1108: The server sends information about at least one candidate file and information about the second electronic device to the first electronic device.

[0225] The candidate file information may include at least one of the candidate file's file identifier, the candidate file's file summary, and the candidate file's data. The second electronic device information may include at least one of the second electronic device's device identifier, device name, device model, and other information.

[0226] S1109: The first electronic device displays a reminder message.

[0227] Optionally, the reminder message is used to ask the user whether to synchronously set permissions for the candidate files. For example, the reminder message may include information about the candidate files and information about the second electronic device, and the user can select the files for which permissions need to be synchronously set.

[0228] For example, Figure 12 is a schematic diagram of an interface for displaying a reminder message provided in an embodiment of the present application. Referring to Figure 12, the first electronic device can display relevant information of the first file for which permission setting has been completed in the reminder message. As shown in Figure 12, the first file is file 1, the first electronic device is electronic device 1, and the first electronic device displays that the "read-only" permission of the first file corresponds to user 1 and user 2, and the "edit" permission of the first file corresponds to user 3, and the access time is January 1, 2023. The first electronic device can also display the file name of the candidate file and the identifier of the electronic device to which the candidate file belongs in the reminder message. As shown in Figure 12, the candidate files include file 2, file 3, file 4 and file 5, wherein file 2 and file 3 are located in electronic device 1, file 4 is located in electronic device 2, and file 3 is located in electronic device 3. The user can select at least one of file 2, file 3, file 4 or file 5, thereby triggering the electronic device to synchronize and set permissions for the second file selected by the user.

[0229] S1110: In response to a second operation of the user, the first electronic device sends a second message to the server.

[0230] Optionally, the second operation is an operation in which the user selects a second file from at least one candidate file, and the second file is part or all of the candidate file. The second message may be used to request permission to set the second file, and the second request may include a file identifier of the second file.

[0231] S1111: The server sends a fifth message to the second electronic device corresponding to the second file.

[0232] Optionally, the fifth message is used to request the second electronic device to set permissions for the second file.

[0233] In an optional implementation, the fifth message can be used to request the second electronic device to set the permission of the second file to the first permission. Optionally, the first electronic device can send the access control policy corresponding to the first file to the server. When the server sends the fifth message to the second electronic device, the fifth message can include the access control policy corresponding to the first file, or the fifth message can include the identifier corresponding to the first permission.

[0234] S1112: The second electronic device sets permissions for the second file.

[0235] Optionally, the second electronic device can set the permission of the second file to the first permission, or the second electronic device can set the permission of the second file to the second permission. The second permission can be a permission set by the user or a permission configured by the system. For example, the second permission can be a permission configured by the system and related to the first permission, such as the second permission can be a subset of the first permission.

[0236] The second electronic device can set the permissions for the second file and store the access control policy corresponding to the second file. Taking the example of the second electronic device setting the second file to the first permission, if the sixth message received by the second electronic device includes the access control policy corresponding to the first file, the second electronic device can generate and store the access control policy corresponding to the second file based on the access control policy corresponding to the first file; or the second electronic device can store a preset access control policy, and when the request message received by the second electronic device includes an identifier corresponding to the first permission, the second electronic device can search for the access control policy corresponding to the first permission from the preset access control policy based on the identifier of the first permission, and use the access control policy corresponding to the first permission found as the access control policy corresponding to the second file.

[0237] In some embodiments, when the first permission is to encrypt a file with a password, the first electronic device can encrypt the password set by the user for encrypting the first file, and send the encrypted password to the second electronic device. After the second electronic device decodes the password to obtain the password, it can encrypt the second file based on the password without the user entering the password again; or, the second electronic device can display a reminder message, which is used to remind the user to enter the password used to encrypt the second file.

[0238] It should be noted that the permission management method provided in Example 2 of the present application can be combined with the permission management method provided in Example 1. That is, when the second file selected by the user from the candidate files includes a file stored in the first electronic device, the first electronic device sets the permissions of the file. When the second file includes a file stored in the second electronic device, the first electronic device sends the file identifier of the second file to the server, and the server notifies the second electronic device to set the permissions of the second file. For specific implementation, please refer to the above-mentioned Examples 1 and 2, and the repeated parts will not be repeated.

[0239] Optionally, after the second electronic device sets the permissions for the second file, it can send a notification message to the server to notify the server that the permission setting is completed. The server can send a notification message to the first electronic device, and the first electronic device can display a reminder message. The reminder message is used to notify the user that the permission setting for the second file has been completed.

[0240] In some scenarios, the electronic device can interact with the server after accessing the network. After the server sends a message to the second electronic device corresponding to the second file, if the second electronic device is not connected to the network, the second electronic device cannot receive the message and will not respond. When the server does not receive the notification message sent by the second electronic device within a preset time period, it can send a message to the second electronic device again, or the server can send a message to the second electronic device after determining that the second electronic device is online.

[0241] For example, FIG13 is a schematic diagram of a display interface of an electronic device provided in an embodiment of the present application. Referring to (a) in FIG13 , a first electronic device can receive a notification message sent by a server, so that the first electronic device can determine the second file for which file permission setting has been completed. For example, in FIG13 , electronic device 2 has set file 4 to the first permission, and electronic device 3 has not responded to the request message sent by the server. The first electronic device can display that file 5 has not completed permission setting. Optionally, referring to (b) in FIG13 , when electronic device 1 or electronic device 2 determines that electronic device 3 is online, a reminder message can be displayed. The reminder message can be used to notify the user that electronic device 3 is online and ask the user whether to try again to set the file permission of file 5 to the first permission.

[0242] The second rights management method provided in the embodiment of the present application can be executed by the first electronic device, the second electronic device, and the server having the structure shown in FIG10 . FIG14 is a flowchart of the second rights management method provided in the embodiment of the present application. Referring to FIG14 , the method includes the following steps:

[0243] S1401: In response to a first operation of a user, the first file management module sends a first permission setting request message to the first permission setting module.

[0244] Optionally, the first operation may be an operation in which the user selects the permission of the first file as the first permission, and the first permission setting request message may be used to request the first permission setting module to set the permission of the first file to the first permission.

[0245] S1402: The first permission setting module sets the permission of the first file to the first permission, and generates an access control policy corresponding to the first file.

[0246] S1403: The first permission setting module sends a notification message to the first file management module.

[0247] The notification message is used to indicate that the permission setting of the first file has been completed, and the notification message may include the access control policy corresponding to the first file.

[0248] S1404: The first file management module sends a first identification request message to the first associated file identification module.

[0249] Optionally, the first identification request message is used to request determination of files related to the first file.

[0250] S1405: The feature extraction module extracts file features of the first file.

[0251] S1406: The feature extraction module sends the file features of the first file to the first associated file identification module.

[0252] S1407: The first associated file identification module sends a second identification request message to the third associated file identification module.

[0253] Optionally, the second identification request message is used to request determination of files related to the first file, and the second identification request message may include file characteristics of the first file, the first file, and an access control policy corresponding to the first file.

[0254] S1408: The third associated file identification module obtains a first file feature set corresponding to the first account from the file feature library.

[0255] S1409: The third associated file identification module determines at least one pending file according to the first file feature of the first file and the file features in the first file feature set.

[0256] S1410: The third associated file identification module sends the file identifier of at least one pending file and the device identifier of the second electronic device to the file scanning module.

[0257] S1411: The file scanning module sends a file identifier of at least one pending file to the second associated file identification module.

[0258] S1412: The second associated file identification module obtains at least one pending file according to the file identifier of the at least one pending file.

[0259] S1413: The second associated file identification module sends at least one pending file to the file scanning module.

[0260] S1414: The file scanning module sends at least one pending file to the third associated file identification module.

[0261] S1415: The third associated file identification module determines at least one candidate file related to the first file from the at least one pending file according to the second file feature of the first file.

[0262] The specific implementation of S1409 and S1415 can be found in S503, and the repeated parts will not be repeated.

[0263] It should be noted that S1410 to S1415 are optional steps, that is, S1410 to S1415 may not be performed during implementation, and the third associated file identification module may use the pending file determined in S1409 as a candidate file.

[0264] S1416: The third associated file identification module sends the file identifier of at least one candidate file and the device identifier of the second electronic device to the first associated file identification module.

[0265] S1417: The first associated file identification module sends the file identifier of at least one candidate file and the device identifier of the second electronic device to the first file management module.

[0266] S1418: The first file management module displays a reminder message.

[0267] The reminder message is used to inquire the user whether to synchronously set the permissions of the candidate file. The reminder message may include information about at least one candidate file and information about the second electronic device.

[0268] S1419: In response to the user's second operation, the first file management module sends a second permission setting request message to the first associated file identification module.

[0269] Optionally, the second operation may be an operation of the user selecting a second file from at least one candidate file, and the second permission setting request message is used to request setting permissions for the second file.

[0270] S1420: The first associated file identification module sends a third permission setting request message to the third associated file identification module.

[0271] The third permission setting request message is used to request setting permissions for the second file.

[0272] S1421: The third associated file identification module sends a fourth permission setting request message to the second associated file identification module.

[0273] The fourth permission setting request message is used to request setting permissions for the second file.

[0274] S1422: The second associated file identification module sends a fifth permission setting request message to the second permission setting module.

[0275] The fifth permission setting request message is used to request setting permissions for the second file.

[0276] S1423: The second permission setting module sets permissions for the second file.

[0277] Example 3

[0278] Optionally, when the first electronic device and the second electronic device execute the permission management method provided in the embodiment of the present application, the architecture of each device can be as shown in Figure 15. Referring to Figure 15, the first electronic device may include a first file management module, a first permission setting module, a feature extraction module, and a first remote comparison module, and the second electronic device may include a second file management module, a second permission setting module, a second local file feature library, and a second remote comparison module. The functions of each module can be found in the relevant introduction of Figure 1 above, and the repeated parts will not be repeated.

[0279] FIG16 is a flowchart of a third rights management method provided by an embodiment of the present application. The method can be executed by a first electronic device and a second electronic device, such as the method can be executed by multiple electronic devices in the file management system shown in FIG1. ​​Referring to FIG16, the method may include the following steps:

[0280] S1601: In response to a first operation of the user, the first electronic device sets the permission of the first file to the first permission.

[0281] Optionally, the first operation may be an operation in which the user selects the permission of the first file as the first permission.

[0282] After setting the permission for the first file to the first permission, the first electronic device may store an access control policy corresponding to the first file. The access control policy corresponding to the first file may include at least one of the following: a user account identifier, an expiration date of the first file, the first permission, an account identifier of an authorized user, etc. Optionally, the first electronic device may encrypt the access control policy corresponding to the first file and store the encrypted access control policy, thereby further improving the security of the permission setting.

[0283] S1602: The first electronic device extracts file features of the first file.

[0284] Optionally, the file feature of the first file may include at least one of the following: a keyword, a key word, an OCR feature, a picture feature, a file paragraph feature, a long text feature, etc.

[0285] S1603: The first electronic device sends a first message to the second electronic device.

[0286] Optionally, the first message may be used to request the second electronic device to determine files related to the first file. The first message may include a first file feature of the first file. The first file feature of the first file may include, for example, at least one of a keyword, a key word, an OCR feature, and an image feature.

[0287] S1604: The second electronic device determines at least one pending file according to the first file feature of the first file.

[0288] In an optional embodiment, the second electronic device can compare the first file feature of the first file with the file feature of the file stored in the second electronic device to determine the first similarity between the first file feature and the file feature of the file stored in the second electronic device. The second electronic device can regard the file whose first similarity with the first file feature meets the preset conditions among the stored files as a pending file. For example, the second electronic device can regard the file whose first similarity is greater than or equal to the first preset threshold as a pending file.

[0289] S1605: The second electronic device sends at least one pending file to the first electronic device.

[0290] S1606: The first electronic device determines at least one candidate file related to the first file from at least one pending file according to the second file feature of the first file.

[0291] Optionally, the first electronic device may obtain file features of the pending file and determine at least one candidate file from the at least one pending file based on the second file features of the first file and the file features of the pending file. For example, the second file features of the first file may include at least one of an image, a file paragraph feature, and a long text feature. The first electronic device may determine the at least one candidate file based on at least one of image similarity, file paragraph matching, or image OCR and long text similarity. The above file comparison method can be found in the introduction to S503, and repeated parts will not be repeated here.

[0292] In some embodiments, S1605-S1606 are optional steps. The second electronic device may also directly use the pending file as a candidate file and send the file identifier of at least one candidate file to the first electronic device without comparing the pending file with the first file.

[0293] S1607: The first electronic device displays a reminder message.

[0294] Optionally, the reminder message is used to ask the user whether to synchronously set permissions for the candidate file. For example, the reminder message may include information about at least one candidate file and information about the second electronic device, and the user can select the second file for which permissions need to be synchronously set.

[0295] S1608: In response to the user's second operation, the first electronic device sends a second message to the second electronic device.

[0296] Optionally, the second operation is an operation in which the user selects a second file from at least one candidate file, and the second file is part or all of the candidate file. The second message is used to request permission to set the second file, and the second message may include a file identifier of the second file.

[0297] The first electronic device may determine the second electronic device according to the device identifier corresponding to the second file, and send the file identifier of the second file to the second electronic device.

[0298] S1609: The second electronic device sets permissions for the second file.

[0299] In the implementation, S1609 can refer to S1112, and the repeated parts will be omitted.

[0300] It should be noted that the permission management method provided in Example 3 of the present application can be combined with the permission management method provided in Example 1. That is, when the second file selected by the user from the second file includes a file stored in the first electronic device, the first electronic device sets the permissions of the file. When the second file includes a file stored in the second electronic device, the first electronic device sends the file identifier of the second file to the second electronic device, and the second electronic device sets the permissions of the second file. For specific implementation, please refer to the above-mentioned Examples 1 and 2, and the repeated parts will not be repeated.

[0301] Optionally, after the second electronic device sets permissions for the second file, it may send a notification message to the first electronic device to notify the first electronic device that permission setting is complete. The first electronic device may display a reminder message to notify the user that permission setting for the second file has been completed.

[0302] The third rights management method provided in the embodiment of the present application can be performed by the first electronic device and the second electronic device having the structure shown in FIG15 . FIG17 is a flowchart of the third rights management method provided in the embodiment of the present application. Referring to FIG17 , the method includes the following steps:

[0303] S1701: In response to a first operation of a user, the first file management module sends a first permission setting request message to the first permission setting module.

[0304] Optionally, the first operation may be an operation in which the user selects the permission of the first file as the first permission, and the first permission setting request message may be used to request the first permission setting module to set the permission of the first file to the first permission.

[0305] S1702: The first permission setting module sets the permission of the first file to the first permission, and generates an access control policy corresponding to the first file.

[0306] S1703: The first permission setting module sends a notification message to the first file management module.

[0307] The notification message is used to indicate that the permission setting of the first file has been completed, and the notification message may include the access control policy corresponding to the first file.

[0308] S1704: The first file management module sends a first identification request message to the first remote comparison module.

[0309] Optionally, the first identification request message is used to request determination of files related to the first file.

[0310] S1705: The feature extraction module extracts file features of the first file.

[0311] S1706: The feature extraction module sends the first file feature of the first file to the first remote comparison module.

[0312] S1707: The first remote comparison module sends a second identification request message to the second remote comparison module.

[0313] Optionally, the second identification request message is used to request determination of files related to the first file, and the second identification request message may include file features of the first file, the first file, and an access control policy corresponding to the first file.

[0314] S1708: The second remote comparison module obtains the file feature of the file stored in the second electronic device from the second local file feature library.

[0315] S1709: The second remote comparison module determines at least one pending file from the files stored in the second electronic device according to the first file feature of the first file and the file features of the files stored in the second electronic device.

[0316] S1710: The second remote comparison module sends at least one pending file to the first remote comparison module.

[0317] S1711: The first remote comparison module determines at least one candidate file from at least one pending file according to the second file feature of the first file.

[0318] The specific implementation of S1709 and S1711 can refer to S503, and the repeated parts are not repeated. In addition, the description of the file feature of the first file, the first file feature of the first file and the second file feature of the first file in this embodiment can refer to the above embodiment.

[0319] It should be noted that S1710-S1711 are optional steps, that is, S1710-S1711 may not be performed during implementation, and the second remote comparison module may use the pending file determined in S1709 as a candidate file.

[0320] S1712: The first remote comparison module sends the file identifier of at least one candidate file and the device identifier of the second electronic device to the first file management module.

[0321] S1713: The first file management module displays a reminder message.

[0322] The reminder message is used to inquire the user whether to synchronously set the permissions of the candidate file. The reminder message may include information about at least one candidate file and information about the second electronic device.

[0323] S1714: In response to the user's second operation, the first file management module sends a second permission setting request message to the first remote comparison module.

[0324] Optionally, the second operation may be an operation of the user selecting a second file from at least one candidate file, and the second permission setting request message is used to request setting permissions for the second file.

[0325] S1715: The first remote comparison module sends a third permission setting request message to the second remote comparison module.

[0326] The third permission setting request message is used to request setting permissions for the second file.

[0327] S1716: The second remote comparison module sends a fourth permission setting request message to the second permission setting module.

[0328] The fourth permission setting request message is used to request setting permissions for the second file.

[0329] S1717: The second permission setting module sets permissions for the second file.

[0330] Through the permission management method provided in Example 2 or Example 3 of the present application, cross-device related file retrieval and cross-device file permission management can be realized, further enhancing the strength of file permission management and ensuring user data security.

[0331] Example 4

[0332] Based on similar inventive concepts, the present embodiment also provides a method for synchronously deleting related files. FIG18 is a flow chart of a method for synchronously deleting related files provided by the present embodiment. Referring to FIG18 , the method includes the following steps:

[0333] S1801: In response to a fifth operation of the user, the first electronic device deletes the first file.

[0334] The fifth operation may be an operation triggered by the user to delete the first file.

[0335] S1802: The first electronic device determines at least one candidate file related to the first file according to a file feature of the first file.

[0336] It should be noted that S1802 can be implemented with reference to S503, and the repeated parts are not repeated here.

[0337] S1803: The first electronic device triggers deletion of the second file.

[0338] In an optional embodiment, after the first electronic device determines at least one candidate file related to the first file, it can display a reminder message in the first electronic device, and the reminder message is used to ask the user whether to synchronously delete the candidate file. If the reminder message can include information about at least one candidate file, the user can select the second file that needs to be deleted synchronously.

[0339] Optionally, the first electronic device may trigger deletion of the second file in response to a sixth operation of the user, where the sixth operation is an operation in which the user selects the second file from at least one candidate file, and the second file is part or all of the candidate files.

[0340] Optionally, when the second file belongs to the first electronic device, the first electronic device may delete the second file; when the second file belongs to the second electronic device, the first electronic device may send a request message to the second electronic device, and the second electronic device may delete the second file.

[0341] Through the above method, after the user deletes the first file, the first electronic device can simultaneously delete the second file related to the first file, thereby eliminating the need for the user to repeatedly search for and delete related files, thereby improving user experience.

[0342] It can be understood that the method for synchronously deleting related files provided in Example 4 of the present application can also be executed by a file management system including a server and / or other electronic devices. For specific implementation, please refer to the above-mentioned Examples 2 and 3, which will not be repeated here.

[0343] The embodiment of the present application also provides a rights management method, which can be executed by the first electronic device. Figure 19 is a flowchart of a rights management method provided by the embodiment of the present application. Referring to Figure 19, the method includes the following steps:

[0344] S1901: In response to a first operation of a user, the first electronic device sets the permission of a first file in the first electronic device as a first permission.

[0345] S1902: The first electronic device determines a second file according to setting the permission of the first file to the first permission, where the second file is a file related to the first file.

[0346] S1903: The first electronic device triggers setting of permissions for the second file.

[0347] It should be noted that the rights management method shown in FIG19 of the present application can be specifically implemented by referring to the above embodiments of the present application, and the repeated parts will not be repeated. In addition, the steps and operations performed by the above-described embodiments can be cross-linked or combined with each other on a reasonable basis according to the specific design to form a combined implementation scheme.

[0348] Based on the above embodiments, the present application also provides an electronic device, which includes multiple functional modules; the multiple functional modules interact with each other to implement the functions performed by the first electronic device or the second electronic device in each method described in the embodiments of the present application. For example, execute the steps performed by the first electronic device or the second electronic device in the embodiments shown in Figure 5, Figure 9 or Figure 11. The multiple functional modules can be implemented based on software, hardware or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on the specific implementation. For example, the electronic device may include some or all of the functional modules in the electronic device 1 or the electronic device 2 shown in Figure 1.

[0349] Based on the above embodiments, the present application further provides an electronic device, which includes at least one processor and at least one memory, wherein the at least one memory stores computer program instructions, and when the electronic device is running, the at least one processor performs the functions performed by the first electronic device or the second electronic device in each method described in the embodiments of the present application. For example, the steps performed by the first electronic device or the second electronic device in the embodiments shown in Figures 5, 9, or 11 are performed.

[0350] Based on the above embodiments, the present application also provides a server, which includes multiple functional modules; the multiple functional modules interact with each other to implement the functions performed by the server in each method described in the embodiments of the present application. For example, the steps performed by the server in the embodiment shown in Figure 9 are executed. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on the specific implementation. For example, the server can include some or all of the functional modules in the server shown in Figure 1.

[0351] Based on the above embodiments, the present application further provides a server comprising at least one processor and at least one memory, wherein the at least one memory stores computer program instructions. When the server is running, the at least one processor executes the functions performed by the server in each method described in the embodiments of the present application. For example, the server executes the steps in the embodiment shown in FIG9 .

[0352] Based on the above embodiments, the present application also provides a file management system, which may include a first electronic device, a second electronic device and a server. The first electronic device, the second electronic device and the server may be used to execute the permission management method described in the embodiments of the present application.

[0353] Based on the above embodiments, the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the methods described in the embodiments of the present application.

[0354] Based on the above embodiments, the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a computer, the computer executes the methods described in the embodiments of the present application.

[0355] Based on the above embodiments, the present application further provides a chip, which is used to read a computer program stored in a memory to implement the various methods described in the embodiments of the present application.

[0356] Based on the above embodiments, the present application provides a chip system, which includes a processor for supporting a computer device to implement the various methods described in the embodiments of the present application. In one possible design, the chip system also includes a memory for storing the necessary programs and data for the computer device. The chip system can be composed of a chip or can include a chip and other discrete devices.

[0357] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0358] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0359] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0360] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0361] Obviously, those skilled in the art may make various modifications and variations to this application without departing from the scope of protection of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A rights management method, characterized in that: Applied to a first electronic device, the method includes: In response to a first operation of the user, setting the permission of the first file in the first electronic device to a first permission; Determine a second file according to setting the permission of the first file to the first permission, where the second file is a file related to the first file; Trigger setting permissions for the second file.

2. The method according to claim 1, characterized in that The determining the second file according to setting the permission of the first file to the first permission includes: After the permission of the first file is set to the first permission, the second file which is identical or similar to the first file is determined according to a preset rule.

3. The method according to claim 1 or 2, characterized in that The triggering sets permissions for the second file, including: triggering setting the permission of the second file to the first permission; or Triggering setting the permission of the second file to a second permission, where the second permission is the permission set by the user or the permission configured by the system.

4. The method according to any one of claims 1 to 3, characterized in that: The determining the second file according to setting the permission of the first file to the first permission includes: In response to a second operation of the user, the second file is determined in at least one candidate file, where the at least one candidate file is a file related to the first file.

5. The method according to claim 4, characterized in that The at least one candidate file includes at least one of a file in the first electronic device related to the first file and a file in the second electronic device related to the first file.

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: At least one candidate file is determined from at least one file to be compared according to the file features of the first file, and the similarity between the file features of the at least one candidate file and the file features of the first file meets a preset condition; the at least one file to be compared comes from at least one of the first electronic device, the second electronic device and the server.

7. The method according to claim 6, characterized in that The file feature of the first file includes at least one of the following: a keyword, a key word, an optical character recognition (OCR) feature, a picture feature, a file paragraph feature, and a long text feature.

8. The method according to any one of claims 4 to 7, characterized in that: The method further comprises: Sending a first message to a server or a second electronic device, wherein the first message is used to request to determine a file related to the first file; Receive information of a fourth file sent by the server or the second electronic device, where the fourth file is one of the at least one candidate file.

9. The method according to claim 8, characterized in that The information of the fourth file includes at least one of a file identification of the fourth file, a file summary of the fourth file, and data of the fourth file.

10. The method according to any one of claims 4 to 7, characterized in that: The method further comprises: Sending a first message to a server or a second electronic device, wherein the first message is used to request to determine a file related to the first file; receiving information of a fifth file sent by the server or the second electronic device; The fifth file is determined to be one of the at least one candidate file according to the file feature of the first file and the information of the fifth file.

11. The method according to any one of claims 1 to 10, characterized in that: The triggering sets permissions for the second file, including: Set permissions for the second file; or A second message is sent to the server or the second electronic device, where the second message is used to request setting permissions for the second file.

12. The method according to any one of claims 1 to 11, characterized in that: Before the triggering sets permissions for the second file, the method further includes: A first reminder message is displayed, where the first reminder message is used to inquire whether to synchronously set permissions for the second file.

13. The method according to claim 12, characterized in that The first reminder message includes information about the second file and information about the electronic device to which the second file belongs.

14. The method according to any one of claims 1 to 13, characterized in that: The method further comprises: Determining that a third electronic device is online, and a sixth file in the third electronic device is a file related to the first file; Triggering setting of permissions for the sixth file.

15. The method according to claim 14, characterized in that Before the triggering sets permissions for the sixth file, the method further includes: A second reminder message is displayed, where the second reminder message is used to inquire whether to set permissions for the sixth file.

16. The method according to any one of claims 1 to 15, characterized in that: The method further comprises: In response to a third operation of the user, setting the permission of the first file to a third permission; Trigger setting permissions for the second file.

17. The method according to any one of claims 1 to 16, characterized in that: The second file belongs to the first electronic device, and the method further includes: In response to a fourth operation of the user, the permission of the second file is set to a fourth permission.

18. The method according to claim 17, characterized in that The method further comprises: Trigger setting permissions for the first file.

19. The method according to any one of claims 1 to 18, characterized in that: The method further comprises: receiving a third message sent by a third electronic device, wherein the third message is used to request to determine a file related to a seventh file in the third electronic device; determining, according to a file feature of the seventh file, a file related to the seventh file from files stored in the first electronic device; The information of the file related to the seventh file is sent to the third electronic device.

20. The method according to any one of claims 1 to 19, characterized in that The method further comprises: receiving a fourth message sent by a third electronic device, where the fourth message is used to request that the permission of an eighth file in the first electronic device be set to a fifth permission; The permission of the eighth file is set to the fifth permission.

21. A method for rights management, characterized in that: Applied to a server, the method comprises: Receiving a first message sent by a first electronic device, wherein the first message is used to request to determine a file related to a first file in the first electronic device; Information of a fourth file is sent to the first electronic device, where the fourth file is a file related to the first file.

22. The method according to claim 21, characterized in that The information of the fourth file includes at least one of a file identification of the fourth file, a file summary of the fourth file, and data of the fourth file.

23. The method according to claim 21 or 22, characterized in that The method further comprises: receiving a second message sent by the first electronic device, where the second message is used to request permission to set a second file; A fifth message is sent to a second electronic device, where the fifth request message is used to request setting permissions for the second file, and the second electronic device is the electronic device described in the second file.

24. The method according to any one of claims 21 to 23, characterized in that Before sending the information of the fourth file to the first electronic device, the method further includes: The fourth file is determined according to the file feature of the first file and the file feature of at least one file stored in the server, and the similarity between the file feature of the fourth file and the file feature of the first file meets a preset condition.

25. The method of claim 24, wherein: The file feature of the first file includes at least one of the following: a keyword, a key word, an optical character recognition (OCR) feature, a picture feature, a file paragraph feature, and a long text feature.

26. An electronic device, characterized in that: The system comprises at least one processor, wherein the at least one processor is coupled to at least one memory, and the at least one processor is configured to read a computer program stored in the at least one memory to execute the method according to any one of claims 1 to 20.

27. A server, characterized in that: The system comprises at least one processor coupled to at least one memory, wherein the at least one processor is configured to read a computer program stored in the at least one memory to execute the method according to any one of claims 21 to 25.

28. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the method according to any one of claims 1 to 20, or to execute the method according to any one of claims 21 to 25.

Images