Authority management method and system and vehicle

Abstract

The invention provides an authority management method and system and a vehicle, and relates to the technical field of vehicles. Comprising the following steps that in response to authority management operation of a user in a first authority management interface, an authority configuration file is generated, and the authority configuration file at least comprises an authorization authority item and an authority validity period; key parameters in the permission configuration file are analyzed, and first permission updating information is generated. The first permission updating information is sent to all the application programs, so that each application program updates the permission access list of each application program based on the first permission updating information, and the application programs are configured to be capable of calling target equipment corresponding to the authorization permission item within the permission validity period. The use experience of the vehicle-mounted application is optimized, the user experience is improved, the uniformity and safety of authority management are enhanced, the user privacy is protected, and the data safety is improved.

Description

Technical Field

[0001] The present application relates to the technical field of vehicles, and in particular, to a permission management method, system and vehicle. Background Art

[0002] The rapid development of intelligent connected vehicles has led to a surge in in-vehicle applications such as cameras, maps, and voice assistants, all of which need to access key resources such as cameras and microphones. In this context, to ensure user privacy and driving safety, the permission management of in-vehicle applications is crucial for the vehicle-mounted system.

[0003] Currently, the permission management method for in-vehicle applications is similar to that for mobile devices. Users manage the permissions of each application through the system settings interface. Before an application attempts to access a resource, for unauthorised permissions, a request pop-up window will be used to ask the user whether they are willing to authorise. In the special environment inside the vehicle, frequent permission request pop-up windows interfere with operations and pose a threat to driving safety. At the same time, setting permissions without a time limit endangers privacy security and restricts users from adjusting according to their needs, affecting the experience. Therefore, how to achieve unified authorisation and management of in-vehicle application programs and improve the user experience has become an urgent problem to be solved in this field. Summary of the Invention

[0004] The purpose of the embodiments of the present invention is to provide a permission management method, system and vehicle to solve the problem of how to achieve unified authorisation and management of in-vehicle application programs and improve the user experience. The specific technical solutions are as follows:

[0005] In the first aspect of the present invention, a permission management method is first provided, including the following steps:

[0006] In response to a permission management operation by the user in the first permission management interface, a permission configuration file is generated, and the permission configuration file includes at least authorised permission items and a permission validity period;

[0007] Parse the key parameters in the permission configuration file to generate first permission update information;

[0008] Send the first permission update information to all application programs so that each application program updates the permission access list of each application program based on the first permission update information, where the application program is configured to be able to call the target device corresponding to the authorised permission item within the permission validity period.

[0009] Optionally, the permission validity period includes the number of authorisations;

[0010] After sending the first permission update information to all application programs, it further includes:

[0011] In response to the power-off and restart signal sent by the in-vehicle system, write off the authorized times;

[0012] In the case where the authorized times after write-off are less than or equal to 0, display the second permission management interface;

[0013] In response to the permission management operation of the user in the second permission management interface, update the permission configuration file;

[0014] Send second permission update information to all the application programs, where the second permission update information is used to update the permission access list of each application program again.

[0015] Optionally, the permission validity period includes the permission valid duration;

[0016] After sending the first permission update information to all the application programs, it further includes:

[0017] Obtain the response time and the current time, where the response time represents the specific time for responding to the permission management operation of the user in the first permission management interface;

[0018] Calculate the permission usage duration according to the response time and the current time, where the permission usage duration represents the usage duration of the authorized permission items;

[0019] In the case where the permission usage duration is less than the permission valid duration, load the authorized permission items;

[0020] In the case where the permission usage duration is greater than or equal to the permission valid duration, display the third permission management interface;

[0021] In response to the permission management operation of the user in the third permission management interface, update the permission configuration file;

[0022] Send the third permission update information to all the application programs, where the third permission update information is used to update the permission access list of each application program again.

[0023] Optionally, the permission management operation includes canceling the authorized permission items;

[0024] After generating the permission configuration file in response to the permission management operation of the user in the first permission management interface, it further includes:

[0025] In response to the permission management operation of the user canceling the authorized permission items, determine the target permission;

[0026] Identify the target permission information in the permission configuration file, where the target permission information represents the associated information of the target permission in the permission configuration file;

[0027] Update the permission configuration file using the target permission information;

[0028] Send a fourth permission update message to all the applications, where the fourth permission update message is used to instruct each application to stop using the target permission.

[0029] Optionally, after sending the fourth permission update message to all the applications, it further includes:

[0030] Each application identifies target data according to the target permission, where the target data represents the data obtained through the target permission;

[0031] Each application performs desensitization processing on the target data according to a preset security policy.

[0032] Optionally, after generating the permission configuration file in response to a user's permission management operation in the first permission management interface, it further includes:

[0033] Perform encryption processing on the permission configuration file to generate a first encrypted configuration file;

[0034] Upload the first encrypted configuration file to the cloud and generate a first digital fingerprint of the first encrypted configuration file;

[0035] Record the metadata information of the first encrypted configuration file, and associate the metadata information with the first digital fingerprint. The metadata information of the first encrypted configuration file at least includes the timestamp information and source device information for uploading the first encrypted configuration file to the cloud.

[0036] Optionally, after generating the permission configuration file in response to a user's permission management operation in the first permission management interface, it further includes:

[0037] Upload the permission configuration file to the cloud for backup to generate a configuration file copy;

[0038] Obtain a second encrypted configuration file currently stored in the cloud, and calculate a second digital fingerprint of the second encrypted configuration file;

[0039] In the case where the first digital fingerprint is inconsistent with the second digital fingerprint, obtain the configuration file copy from the cloud;

[0040] According to the configuration file copy, send a fifth permission update message to all the applications, where the fifth permission update message is used to update the permission access list of each application.

[0041] Optionally, after obtaining the second encrypted configuration file currently stored in the cloud and calculating the second digital fingerprint of the second encrypted configuration file, the following steps are further included:

[0042] When the first digital fingerprint is consistent with the second digital fingerprint, compare the metadata information of the second encrypted configuration file with the metadata information of the first encrypted configuration file;

[0043] When the metadata information of the second encrypted configuration file is consistent with the metadata information of the first encrypted configuration file, use a preset decryption strategy to decrypt the second encrypted configuration file to obtain the permission configuration file corresponding to the decrypted second encrypted configuration file;

[0044] According to the permission configuration file corresponding to the decrypted second encrypted configuration file, send a sixth permission update message to all application programs, where the sixth permission update message is used to update the permission access list of each application program.

[0045] In a second aspect of the implementation of the present application, a permission management system is further provided, including:

[0046] A first response module, configured to generate a permission configuration file in response to a permission management operation of a user in a first permission management interface, where the permission configuration file includes at least an authorized permission item and a permission validity period;

[0047] An analysis module, configured to analyze key parameters in the permission configuration file to generate a first permission update message;

[0048] A first sending module, configured to send the first permission update message to all application programs, so that each application program updates the permission access list of each application program based on the first permission update message, where the application program is configured to be able to call the target device corresponding to the authorized permission item within the permission validity period.

[0049] In a third aspect of the implementation of the present application, a vehicle is further provided, including: a permission management system, and / or, executing any one of the permission management methods.

[0050] In this application, the user performs permission management operations through the first permission management interface. After the permission management operations are completed, the permission management system generates a permission configuration file reflecting the authorized permission items and the permission validity period. By parsing the key parameters in the permission configuration file, the first permission update information is generated and sent to all application programs. After each application program receives the first permission update information, it updates the corresponding permission access list. The permission access list reflects the user's latest permission settings. After the permission access list is updated, all application programs can access the same authorized permission items within the same permission validity period. The embodiments of this application achieve unified authorization and unified management of application programs, avoiding the frequent appearance of permission request pop-up windows when the application programs are started for the first time, interrupting the normal operations of users, not only reducing the user experience, but also posing a potential threat to driving safety. Within the same permission validity period, all application programs access the same authorized permission items, which is more in line with the usage scenarios of this specific in-vehicle environment. By setting a unified permission validity period, it is also possible to avoid continuously obtaining relevant data of authorized permission items, increasing the risk of user privacy and data leakage, and improving data security. While achieving unified management of application programs, it protects user privacy and improves data security. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 FIG. shows a flowchart of the steps of a permission management method provided by an embodiment of this application;

[0052] Figure 2 FIG. shows an exemplary flowchart of the permission management method provided by the embodiments of this application;

[0053] Figure 3 FIG. shows a flowchart of the method for updating the permission access list provided by an embodiment of this application;

[0054] Figure 4 FIG. shows a flowchart of the method for updating the permission access list provided by another embodiment of this application;

[0055] Figure 5 FIG. shows a flowchart of the method for updating the permission configuration file provided by an embodiment of this application;

[0056] Figure 6 FIG. shows a flowchart of the method for desensitizing target data provided by an embodiment of this application;

[0057] Figure 7 FIG. shows a flowchart of the method for uploading the permission configuration file provided by an embodiment of this application;

[0058] Figure 8 FIG. shows a flowchart of the method for verifying the digital fingerprint provided by an embodiment of this application;

[0059] Figure 9Shows the flowchart of the method for decrypting the permission configuration file provided by an embodiment of the present application;

[0060] Figure 10 Shows the schematic structural diagram of the permission management system provided by an embodiment of the present application;

[0061] Figure 11 Shows the overall framework diagram of the permission management system provided by the embodiments of the present application. Detailed implementation manners

[0062] To make the above objects, features, and advantages of the present application more obvious and understandable, the present application will be further described in detail below with reference to the accompanying drawings and specific implementation manners.

[0063] With the rapid advancement of intelligent connected vehicles, more and more diverse application programs are integrated into the in-vehicle audio and video entertainment system, covering a series of convenient functions such as cameras, map navigation, and voice assistants. In order to provide more intelligent and personalized services, these application programs often need to deeply access various core resources and functions of the vehicle, including but not limited to cameras, microphones, and location information services. In this context, user privacy protection and device security protection have become problems that need to be solved urgently. In order to ensure that the privacy rights and interests of users are not violated and to ensure safety during driving, the permission management of in-vehicle applications is crucial for the vehicle-mounted system.

[0064] In the existing vehicle-mounted systems, the permission management method of in-vehicle applications is highly similar to the current mobile device management method. Users manage the permissions of each in-vehicle application in detail through an intuitive system settings interface.

[0065] Specifically, each application will pre-declare all the permissions required for running in the corresponding manifest file. For example, the declaration for applying for camera permission will appear in a standard format, such as: <uses-permission android:name="android.permission.CAMERA" / >. When an application attempts to access protected resources, the system will first perform a permission check step by calling ContextCompat.checkSelfPermission to confirm whether it has obtained the explicit authorization of the user. If the application has obtained the corresponding authorization, it can access the required resources seamlessly and directly. If the application has not obtained authorization, the system will immediately pop up a friendly prompt box asking the user whether they are willing to grant the application permission to access specific resources. The user's decision will be reflected through the timely feedback of the system pop-up window, thus directly determining whether the application has the right to continue accessing the relevant resources. If the user rejects the permission application, the application will stop accessing the relevant resources and explain to the user the reason and how to manually enable the permission path. In addition, users can also view and flexibly manage the permissions of each application in the system. Whether it is through entering the information page of each application for individual management or performing batch operations on the system's permission management page, it can ensure that user privacy and the device are properly handled.

[0066] In the process of implementing the inventive technical solution in the embodiments of the present application, the inventors of the present application found that the above technology has at least the following technical problems:

[0067] First, in the special environment inside the vehicle, since users do not operate the in-vehicle system as frequently as they use mobile phones, there is no need to grant different permissions to each application separately.

[0068] Second, some application programs do not follow the principle of requesting permissions on demand and the principle of minimum permissions when starting for the first time. Instead, they default to requesting all the required permissions, resulting in a large number of permission request pop-up windows for users when they first use the application. Frequent permission request pop-up windows not only interrupt the user's operation process but also distract the driver's attention, posing a potential threat to driving safety, reducing the user experience, and also causing the application to access more user data on the mobile phone. Applications with excessive permissions may become targets of malicious software attacks. Once the application is compromised, user data will face the risk of leakage.

[0069] Finally, due to reasons such as design intent, technical implementation difficulty, compatibility, and user habits, the existing system does not have a function to set the validity period of permissions during design. Once a user grants a certain permission, the permission remains valid until the user manually revokes it or the application is uninstalled. Since permissions are valid indefinitely once authorized, it is difficult for users to adjust permission settings according to their personal needs at any time, which may not only pose a threat to user privacy and data security but also limit the user's ability to adjust permission settings according to personal needs, thus affecting the user experience.

[0070] Referring to Figure 1 , a flowchart of the steps of a permission management method provided by an embodiment of the present application is shown, including the following steps:

[0071] S101. In response to a user's permission management operation in a first permission management interface, generate a permission configuration file, where the permission configuration file includes at least an authorized permission item and a permission validity period.

[0072] Specifically, as a user interface, the first permission management interface is usually located in the settings menu of the vehicle-mounted system and is used to display and manage the permissions of all applications. Through the first permission management interface, the user can perform permission management operations and thus manage the permissions of applications.

[0073] Exemplarily, the user can enter the first permission management interface to view and edit permissions through "System Settings - Authorization Management". The first permission management interface displays a title, explanatory text, permission items, permission validity period, confirm authorization, and cancel authorization. The permission item refers to the type of item corresponding to the target device that is allowed to be called by the application in the permission management system. For example, the permission item can be a microphone, a camera, or a location sensor. The permission validity period refers to the time range for which the user authorizes the permission item. For example, the permission validity period can be once, 7 days, 30 days, or 1 year. During the permission validity period, the application can legally access and use the target device corresponding to the permission item. When the application obtains data or executes instructions based on the target device, the application first obtains the usage permission of the target device, that is, whether the permission item corresponding to the target device is authorized. If the permission item corresponding to the target device is authorized, the application can obtain data or execute instructions based on the target device within the permission validity period.

[0074] The user selects at least one permission item in the first permission management interface. After selecting the permission validity period, click the confirm authorization button to complete the permission management operation. When the user completes the permission management operation, the permission management system immediately responds. For example, the permission management system generates a permission configuration file according to the user's operation, and the permission configuration file details the permission validity period of the permission item selected by the user. In addition, the generated permission configuration file is stored in the secure storage area of the local device in an encrypted form to ensure the confidentiality and integrity of the information.

[0075] In this embodiment, by providing a first permission management interface, it is convenient for users to easily manage application permissions. The users are allowed to set permission items and permission validity periods, enabling them to adjust the permission settings at any time according to actual needs. By setting the permission validity period, the risk that the application holds unnecessary permissions for a long time is reduced, the risk of user privacy and data leakage is lowered, protecting user privacy and data security, and enhancing the user experience.

[0076] S102. Analyze the key parameters in the permission configuration file to generate the first permission update information.

[0077] Specifically, the key parameters are the basis for analyzing the permission configuration file and generating the first permission update information. The first permission update information is used to describe the user's latest permission settings for all applications, and at least includes the authorized permission items and the permission validity period. Exemplarily, the key parameters in the permission configuration file are obtained through real-time analysis after the permission configuration file is generated. The key parameters in the permission configuration file at least include the name of each authorized permission item, the identifier of each authorized permission item, and the permission validity period. The first permission update information is generated based on the key parameters, and the first permission update information at least includes the authorized permission item list and the permission validity period.

[0078] In this embodiment, by analyzing the parameters in the permission configuration file, the accuracy of the generated first permission update information is ensured. By restricting the generation method of the first permission update information, it is guaranteed that the first permission update information is directly related to the user's permission management operations, ensuring the accuracy of the first permission update information and avoiding permission management chaos caused by incorrect first permission update information.

[0079] S103. Send the first permission update information to all applications so that each application updates the permission access list of each application based on the first permission update information. Among them, the application is configured to be able to call the target device corresponding to the authorized permission item within the permission validity period.

[0080] Specifically, each application corresponds to a permission access list. The permission access list records the permission items authorized for the corresponding application to access. Each authorized permission item corresponds to a specific target device, such as a camera, a microphone, a location sensor, etc. When an application attempts to call a certain target device, it checks its own permission access list to ensure that it has the calling permission. By sending the first permission update information to all applications, each application updates its own permission access list based on the first permission update information, reflecting the user's latest permission settings in real time, and ensuring that the target device corresponding to the authorized permission item can be correctly called within the permission validity period.

[0081] Exemplarily, Figure 2The exemplary method flow chart of the permission management method provided by the embodiment of the present application is shown. Refer to Figure 2 , when the in-vehicle system is started for the first time, the permission validity period expires, the application requests to call the permission item, or the user calls the permission management interface in the system settings, by responding to the permission items and permission validity period selected by the user in the permission management interface, the permission configuration file is updated. On the one hand, the permission configuration file is uploaded to the cloud storage. On the other hand, based on the permission configuration file, all applications are instructed to update the internal permission access list to achieve unified management of application permissions.

[0082] Exemplarily, the permission management system sends the first permission update information to all running applications and subsequent started applications through inter-process communication. After receiving the first permission update information, the application updates its internal permission access list. All applications in the permission management system will be granted the authorized permission items, and the application does not need to initiate a permission request when accessing the authorized permission items within the permission validity period. Specifically, the inter-process communication methods include AIDL (Android Interface Definition Language), anonymous pipes, named pipes, signals, shared memory, semaphores, message queues, and sockets, etc.

[0083] Exemplarily, after each application updates the corresponding permission access list based on the first permission update information, for an application that depends on a specific permission item to run properly, the application will perform an initialization check to ensure that the target device corresponding to the authorized permission item can be correctly called under the updated permission access list. When an application uses a certain permission item, it first calls an AIDL interface for judging whether the permission item is authorized, communicates with the permission management system using the AIDL interface, and queries the status information of the permission item. If the permission item is authorized and within the permission validity period, the AIDL interface will return a signal with a boolean value of TRUE, enabling the application to normally call the target device corresponding to the permission item. If the permission item is not authorized or has expired, the AIDL interface will return a signal with a boolean value of FALSE to the application. At this time, the application cannot access the permission item and needs to call an AIDL interface for displaying the authorization management interface. The AIDL interface for displaying the authorization management interface will invoke the authorization management interface of the permission management system. This interface will only display the permission items applied for by this application, including the permission item, authorization, and rejection. After the user selects authorization or rejection, the permission management system will update the permission configuration file and notify the application of the result of this permission item request in the form of an AIDL callback. If the application receives an authorization result, it will normally access the target device corresponding to the permission item; if the application receives a rejection result, it will suspend the current operation process that requires this permission item and display corresponding prompt information to the user, informing the user of the situation where the permission acquisition fails. Once the user authorizes the permission item applied for by a certain application, all other applications in the in-vehicle system can also access this permission item.

[0084] In this embodiment, the user performs a permission management operation through the first permission management interface. After the permission management operation is completed, the permission management system generates a permission configuration file reflecting the authorized permission items and the permission validity period. By parsing the key parameters in the permission configuration file, a first permission update message is generated and sent to all application programs. After each application program receives the first permission update message, it updates the corresponding permission access list. The permission access list reflects the user's latest permission settings. After the permission access list is updated, all application programs can access the same authorized permission items within the same permission validity period. The embodiment of the present application realizes the unified authorization and unified management of application programs, avoiding the frequent appearance of permission request pop-up windows when the application programs are started for the first time, interrupting the normal operations of users, not only reducing the user experience, but also posing a potential threat to driving safety. Within the same permission validity period, all application programs access the same authorized permission items, which is more in line with the usage scenarios of this specific in-vehicle environment. By setting a unified permission validity period, it is also possible to avoid continuously obtaining the relevant data of the authorized permission items, increasing the risk of user privacy and data leakage, and improving data security. While realizing the unified management of application programs, it protects user privacy and improves data security.

[0085] Referring to Figure 3 , a flowchart of a method for updating a permission access list provided by an embodiment of the present application is shown. In this embodiment, the permission validity period includes the number of authorizations. After S103, sending the first permission update message to all application programs so that each application program updates the permission access list of each application program based on the first permission update message, the following steps are further included:

[0086] S201: In response to a power-off and restart signal sent by the in-vehicle system, write off the number of authorizations.

[0087] Specifically, the number of authorizations includes single and multiple times. The power-off and restart signal refers to a specific information generated internally by the in-vehicle system when the in-vehicle system is separated from the power system for a period of time and then reconnected. The power-off and restart information indicates that the in-vehicle system has experienced a restart process. After receiving the power-off and restart signal, the permission management system will write off the number of authorizations. Writing off the number of authorizations means subtracting the number of authorizations by one each time the power-off and restart information is received. By limiting the remaining number of times for the application program to call the corresponding target device in the subsequent authorized permission items, it is possible to prevent the application program from abusing or overcalling the target device and avoid excessive consumption of system resources.

[0088] S202: When the written-off number of authorizations is less than or equal to 0, display the second permission management interface.

[0089] Specifically, after the authorized times are written off, by checking the remaining authorized times, if it is found that the authorized times are less than or equal to 0, it means that the current application does not have the permission to call the target device. At this time, by displaying the second permission management interface, the user is guided to perform the permission management operation again. Exemplarily, the second permission management interface is the same as the first permission management interface, and the user can also be prompted to take additional steps to regain authorization. By displaying the second permission management interface, it is ensured that the application can smoothly call the target device during subsequent use, maintaining the normal operation of each application.

[0090] S203. In response to the user's permission management operation in the second permission management interface, update the permission configuration file.

[0091] Specifically, after the user performs the permission management operation in the second permission management interface, based on the permission management operation in the second permission management interface, re-determine the authorized permission items and the permission validity period. According to the authorized permission items and the permission validity period, update the permission configuration file. The updated permission configuration file contains the re-determined authorized permission items and the permission validity period. By updating the permission configuration file, it can be ensured that all subsequent applications call the target device based on the latest authorized permission items and the permission validity period, guaranteeing the accuracy of permission management.

[0092] S204. Send the second permission update information to all applications, where the second permission update information is used to update the permission access list of each application again.

[0093] Specifically, after the permission configuration file is updated, by parsing the key parameters in the permission configuration file, generate the second permission update information. The second permission update information is used to describe the user's latest permission settings for all applications, and at least includes the authorized permission items and the permission validity period. Exemplarily, the key parameters in the permission configuration file at least include the name of each authorized permission item, the identifier of each authorized permission item, and the permission validity period. The second permission update information is generated based on the key parameters, and the second permission update information at least includes the authorized permission item list and the permission validity period. The second permission update information at least includes the re-determined authorized permission items and the permission validity period. After all applications receive the second permission update information, update the corresponding permission access list according to the content of the second permission update information. The updated permission access list of each application has the same authorized permission items and the permission validity period. The updated permission access list ensures that the application calls the target device based on the latest set authorized permission items and the permission validity period during subsequent calls, guaranteeing the timeliness and effectiveness of the target device call.

[0094] Exemplarily, when the in-vehicle system is powered on for the first time or when the authorization has expired and it is powered on again, the permission management system actively pops up the first permission management interface, and the user performs permission management operations through the first permission management interface. The in-vehicle system has set up a circuit signal monitoring mechanism at the hardware level. In the case where the permission validity period is a single authorization, once the vehicle engine is turned off and the entire in-vehicle system is powered off and restarted, and the circuit signal monitoring mechanism detects that the power supply is cut off and then reconnected, it will send a power-off and restart signal to the permission management system. After receiving the power-off and restart signal, the permission validity period of the permission management system will immediately expire. By invoking the second permission management interface, the user is guided to perform permission management operations again. If the user needs to use the permission item again, the user needs to authorize the corresponding permission item, set the permission validity period in the second permission management interface, and send the second permission update information to all application programs, so that each application program updates the internal permission access list.

[0095] In this embodiment, by verifying the number of authorizations, after all the authorizations are written off, the second permission management interface is invoked to guide the user to perform permission management again, and all application programs are notified to update the internal permission access list according to the latest authorization management, ensuring that all application programs are based on the latest permission management operations when calling the target device subsequently, guaranteeing the accuracy of permission management and the effectiveness of target device calls.

[0096] Refer to Figure 4 , which shows a flowchart of a method for updating a permission access list provided by another embodiment of the present application. In this embodiment, the permission validity period includes the permission effective duration. After S103, sending the first permission update information to all application programs so that each application program updates the permission access list of each application program based on the first permission update information, the following steps are further included:

[0097] S301: Obtain the response time and the current time, where the response time represents the specific time when responding to the user's permission management operation in the first permission management interface.

[0098] S302: Calculate the permission usage duration according to the response time and the current time, where the permission usage duration represents the usage duration of the authorized permission item.

[0099] Specifically, the response time refers to the specific time point when the user performs a permission management operation in the first permission management interface, and the current time refers to the specific time at the current moment. By obtaining the response time and the current time, the permission usage duration can be determined. Among them, the permission usage duration represents the usage duration of the authorized permission item, that is, the time length from when the user authorizes the permission item to the current time point. By calculating the permission usage duration, it can be determined whether the authorized permission item is within the permission validity period, ensuring that the permission item will not be valid for a long time without the user's consent, not only avoiding unnecessary resource consumption, but also ensuring user privacy and data security.

[0100] S303. When the permission usage duration is less than the permission validity duration, load the authorized permission items.

[0101] Specifically, when the permission usage duration is less than the permission validity duration, it indicates that the authorized permission items are still within the permission validity period. The application can call the target device corresponding to the authorized permission items. Loading the authorized permission items when the permission usage duration is less than the permission validity duration not only ensures that the application can reasonably call the target device within the permission validity period, but also avoids frequent re-authorization by setting the permission validity duration, thus improving the user experience.

[0102] S304. When the permission usage duration is greater than or equal to the permission validity duration, display the third permission management interface.

[0103] S305. In response to the user's permission management operation in the third permission management interface, update the permission configuration file.

[0104] S306. Send the third permission update information to all applications, where the third permission update information is used to update the permission access list of each application again.

[0105] Specifically, when the permission usage duration is greater than or equal to the permission validity duration, it indicates that the permission items are not within the permission validity period. At this time, by displaying the third permission management interface, the user is reminded that the permission has expired and re-authorization is required. Through interface interaction, in response to the user's permission management operation in the third permission management interface, the permission configuration file is updated according to the user's permission management operation to maintain the real-time nature of the permission configuration file and ensure the accuracy of permission management. Exemplarily, the third permission management interface can be the same as the first permission management interface, or the user can be prompted to take additional steps to re-obtain authorization. By displaying the third permission management interface, it is ensured that the application can smoothly call the target device during subsequent use and maintain the normal operation of each application.

[0106] After the permission configuration file is updated, by parsing the key parameters in the permission configuration file, third permission update information is generated. The third permission update information is used to describe the user's latest permission settings for all application programs, and at least includes the authorized permission items and the permission validity period. Exemplarily, the key parameters in the permission configuration file at least include the name of each authorized permission item, the identifier of each authorized permission item, and the permission validity period. The third permission update information is generated according to the key parameters, and the third permission update information at least includes the authorized permission item list and the permission validity period. By sending the third permission update information to all application programs, the internal permission access lists of each application program are updated, ensuring that all application programs can timely obtain the latest authorized permission items and the permission validity period, preventing data security problems and abnormal calls of the target device caused by inaccurate authorized permission items and permission validity periods, and improving the accuracy of permission management.

[0107] Exemplarily, when the permission validity period is the permission effective duration, the in-vehicle system will start a built-in high-precision timer to record the remaining authorization time. The high-precision timer is closely synchronized with the real-time clock of the in-vehicle system to ensure the accuracy of timing. The remaining authorization time is determined according to the response time and the current time. First, the permission usage duration is calculated based on the response time and the current time. Then, according to the permission effective duration and the permission usage duration, the remaining authorization time is determined. Within the permission effective duration, the authorized permission items are valid for all application programs. When the in-vehicle system is powered on again each time, the permission management system will first check the remaining authorization time of the high-precision timer. When the remaining authorization time is greater than 0, the authorized permission items are normally loaded. When the remaining authorization time is less than or equal to 0, the third permission management interface is called to prompt the user that the permission items have expired and display the guidance information for re-authorization, guiding the user to re-perform the permission management operation. The user can re-select the permission validity period according to actual needs, or re-select the authorized permission items and the permission validity period. In addition, the user can also click the cancel button to skip the permission management and directly enter the in-vehicle system.

[0108] In this embodiment, by comparing the magnitude relationship between the permission effective duration and the permission usage duration, it is determined whether the authorized permission items are within the permission validity period. When the authorized permission items are within the permission validity period, the authorized permission items are normally loaded to ensure that the application programs can normally call and access the device. When the authorized permission items are not within the permission validity period, the third permission management interface is displayed to guide the user to re-authorize, and the permission configuration file and the permission access lists of all application programs are updated, ensuring the accuracy and timeliness of permission management and avoiding resource consumption and potential data problems.

[0109] Refer to Figure 5, which shows a flowchart of a method for updating a permission configuration file provided by an embodiment of the present application. In this embodiment, the permission management operation includes canceling an authorized permission item.

[0110] After generating a permission configuration file in S101 in response to a permission management operation of a user in a first permission management interface, the following steps are further included:

[0111] S401: In response to a permission management operation of the user canceling an authorized permission item, determine the target permission.

[0112] Specifically, after the user performs a permission management operation in the first permission management interface, when canceling an authorized permission item, by calling the first permission management interface, cancel the target permission. The target permission represents the authorized permission item that the user needs to cancel. After the user cancels the authorized permission item, by determining the target permission, update the permission configuration file to ensure the accuracy of permission management.

[0113] S402: Identify the target permission information in the permission configuration file. The target permission information represents the associated information of the target permission in the permission configuration file.

[0114] S403: Use the target permission information to update the permission configuration file.

[0115] Specifically, after determining the target permission, by searching for and identifying all information related to the target permission in the permission configuration file, update the permission configuration file. Exemplarily, the target permission information at least includes the permission name, permission description, or associated target device. Updating the permission configuration file includes deleting the entry of the target permission, modifying the target permission status, etc.

[0116] By identifying the associated information of the target permission in the permission configuration file, determining the target permission information, and updating the permission configuration file according to the target permission information, the operation result of the user canceling the authorized permission item is reflected, ensuring the latest state of the permission configuration file, preventing the target permission from being continuously used by the application program, and improving the accuracy of permission management.

[0117] S404: Send a fourth permission update message to all application programs. The fourth permission update message is used to instruct each application program to stop using the target permission.

[0118] Exemplarily, when the user decides to cancel a certain permission item within the validity period of the permission, by entering the first authorization management interface again to cancel the target permission. After determining to cancel the target permission, the permission management system will update the permission configuration file in real time. After the permission configuration file is updated, according to the updated permission configuration file, a fourth permission update message is generated. The fourth permission update message is used to describe the latest permission settings after the user cancels the target permission, and at least includes the authorized permission items and the permission validity period. Exemplarily, the key parameters in the permission configuration file at least include the name of each authorized permission item, the identifier of each authorized permission item, and the permission validity period. The fourth permission update message is generated based on the key parameters, and the fourth permission update message at least includes the list of authorized permission items and the permission validity period. By sending the fourth permission update message to all application programs, all application programs are notified to stop using the target permission. Each application program, after receiving the fourth permission update message, deletes the target permission from the internal permission access list to ensure that the permission item is correctly called and prevent the security risks caused by the abuse of the permission item.

[0119] In this embodiment, after the user cancels the target permission, the target permission information in the permission configuration file is identified, the permission configuration file is updated, and a fourth permission update message is generated to instruct all application programs to update the permission access list and stop using the target permission, ensuring the real-time and accuracy of permission management and preventing the data leakage risk caused by permission abuse.

[0120] Refer to Figure 6 , which shows the flowchart of the method for desensitizing target data provided by an embodiment of the present application. After S404, sending the fourth permission update message to all application programs, where the fourth permission update message is used to instruct the application programs to stop using the target permission, the following steps are further included:

[0121] S501: Each application program identifies the target data according to the target permission, and the target data represents the data obtained through the target permission.

[0122] S502: Each application program performs desensitization processing on the target data according to the preset security policy.

[0123] Specifically, the preset security policy refers to the rules and methods of the device in advance for protecting data privacy and data security, and is used to guide how the application performs data desensitization processing. After receiving the fourth permission update information, each application checks the data that is currently being used or stored, determines which data is obtained through the target permission, and determines this data as the target data. After identifying the target data, according to the preset security policy, the target data is desensitized. Exemplarily, the application quickly identifies the target data according to the mapping relationship between the target permission and the target data. The preset security policy includes at least one of statistical techniques, cryptographic techniques, suppression techniques, pseudonymization techniques, generalization techniques, and randomization techniques. The desensitization processing includes data obfuscation, anonymization, data encryption, or data deletion, etc.

[0124] Exemplarily, after the target data is desensitized, the permission management system records the operation information for canceling the target permission, including the operation time, the name of the target permission, etc. Recording the operation information for canceling the target permission provides a basis for subsequent security audits and user behavior analysis.

[0125] In this embodiment, by accurately identifying the target data, unnecessary processing of irrelevant data is avoided, the resource consumption of the system is reduced, the preset security policy is used to desensitize the target data, preventing the data related to the target permission from being misused or leaked, reducing the potential risk brought by data leakage, improving the overall security, and protecting user privacy and data security.

[0126] Referring to Figure 7 , a flowchart of a method for configuring an upload permission profile provided by an embodiment of the present application is shown. After S101, in response to the permission management operation of the user in the first permission management interface, after generating the permission profile, the following steps are further included:

[0127] S601. Encrypt the permission profile to generate a first encrypted profile.

[0128] Specifically, after generating the permission profile, according to the preset encryption algorithm, the permission profile is encrypted. The encryption process involves converting the permission profile into ciphertext to protect the sensitive information in the permission profile from being easily read or tampered with by unauthorized third parties. The encrypted permission profile is called the first encrypted profile.

[0129] Exemplarily, when encrypting the permission configuration file, a combination of symmetric encryption and asymmetric encryption is adopted. First, the content of the permission configuration file is encrypted using a symmetric encryption algorithm. The symmetric encryption key is generated by encrypting it with the public key of the asymmetric encryption associated with the vehicle owner's digital certificate. The symmetric encryption key is stored in an independent key library. Using the symmetric encryption key, the first encrypted configuration file can be decrypted to obtain the permission configuration file.

[0130] S602. Upload the first encrypted configuration file to the cloud and generate a first digital fingerprint of the first encrypted configuration file.

[0131] Specifically, the encrypted permission configuration file is uploaded to the cloud for storage for remote access and backup.

[0132] The first digital fingerprint is calculated based on the first encrypted configuration file and a hashing algorithm. The first digital fingerprint serves as the unique identifier of the first encrypted configuration file and is used to verify whether the encrypted configuration file uploaded to the cloud has been tampered with during transmission. Even if there are minor changes in the file content, the digital fingerprint will be completely different.

[0133] Exemplarily, the permission configuration file is uploaded to the cloud through the HyperText Transfer Protocol Secure (HTTPS) and stored in the vehicle owner's information database. After the permission configuration file is uploaded to the cloud and saved in the vehicle owner's information database, the permission management system will generate a first digital fingerprint for the first encrypted configuration file in the cloud. The first digital fingerprint is generated based on the hashing algorithm and serves as the unique identifier of the first encrypted configuration file. As the permission items change during the vehicle owner's use of the vehicle, the permission management system will timely update the permission configuration file and generate an updated encrypted configuration file. The updated encrypted configuration file will overwrite the original first encrypted configuration file. At the same time, the permission management system will record the historical versions of each encrypted configuration file to facilitate traceability and auditing, ensuring the traceability and security of permission management throughout the entire process.

[0134] S603. Record the metadata information of the first encrypted configuration file and associate the metadata information with the first digital fingerprint. The metadata information of the first encrypted configuration file at least includes the timestamp information and source device information for uploading the first encrypted configuration file to the cloud.

[0135] Specifically, by recording the metadata information of the first encryption configuration file, associating the metadata information with the first digital fingerprint and then storing it, and by verifying the first digital fingerprint and the metadata information, it is ensured that the file stored in the cloud is the same as the content of the first encryption configuration file, solving the problems of secure storage and secure management of the permission configuration file, and ensuring the efficiency and accuracy of permission configuration file management.

[0136] Refer to Figure 8 , which shows the flowchart of the method for verifying digital fingerprints provided by an embodiment of the present application. After generating a permission configuration file in S101 in response to a permission management operation of a user in the first permission management interface, the following steps are further included:

[0137] S701. Upload the permission configuration file to the cloud for backup to generate a configuration file copy.

[0138] Specifically, uploading the permission configuration file to the cloud for backup to generate a configuration file copy ensures that when a local device fails or data is lost, the permission configuration information can be quickly restored using the permission configuration file, ensuring the continuous availability of the permission configuration. Exemplarily, in the case where the first encryption configuration file is tampered with during the upload to the cloud, the configuration file copy uploaded to the cloud can ensure that the content of the in-vehicle system is consistent with the file stored in the cloud.

[0139] S702. Obtain a second encryption configuration file currently stored in the cloud and calculate the second digital fingerprint of the second encryption configuration file.

[0140] Specifically, during integrity verification, the system obtains the currently stored second encryption configuration file from the cloud and uses the same hashing algorithm to calculate the second digital fingerprint of the second encryption configuration file. By comparing the consistency between the first digital fingerprint and the second digital fingerprint, the permission management system can verify whether the encrypted configuration file stored in the cloud has been tampered with during the upload, ensuring the consistency of file storage. Exemplarily, in the case where the first digital fingerprint is inconsistent with the second digital fingerprint, it indicates that the encrypted configuration file stored in the cloud has been tampered with during the upload; in the case where the first digital fingerprint is consistent with the second digital fingerprint, it indicates that the encrypted configuration file stored in the cloud has not been tampered with during the upload.

[0141] S703. In the case where the first digital fingerprint is inconsistent with the second digital fingerprint, obtain the configuration file copy from the cloud.

[0142] Specifically, after comparing the first digital fingerprint with the second digital fingerprint of the second encrypted configuration file already existing in the cloud, if it is found that the two are inconsistent, it means that the encrypted configuration file stored in the cloud has been damaged or tampered with. At this time, the permission management system triggers a security alarm, starts the data recovery process, obtains a copy of the previously backed-up configuration file from the cloud, and after encrypting the copy of the configuration file, updates the encrypted configuration file stored in the cloud.

[0143] S704. According to the copy of the configuration file, send the fifth permission update information to all application programs, and the fifth permission update information is used to update the permission access list of each application program.

[0144] Specifically, in the case where the configuration file stored in the cloud has been damaged or tampered with, the copy of the configuration file is used to generate the fifth permission update information so that each application program updates the permission access list. Exemplarily, in the case where the user logs in to the permission management system on other vehicles or needs to re-obtain the permission configuration file, download the copy of the configuration file from the cloud, and generate the fifth permission update information by parsing the key parameters in the copy of the configuration file. The fifth permission update information is used to describe the latest permission access list of each application program, and the fifth permission update information at least includes the authorized permission items and the permission validity period. Exemplarily, the key parameters in the copy of the configuration file at least include the name of each authorized permission item, the identifier of each authorized permission item, and the permission validity period. The fifth permission update information is generated according to the key parameters, and the fifth permission update information at least includes the authorized permission item list and the permission validity period. By sending the fifth permission update information to each application program, each application program updates the permission access list according to the fifth permission update information. The copy of the configuration file ensures the accuracy of permission management and prevents access problems caused by mismatched permission items. By updating the permission access list through the copy of the configuration file, the system can more effectively control the authorized permission items of the application program, reduce security risks, and improve the overall reliability and security of the permission management system.

[0145] Refer to Figure 9 , which shows the flowchart of the method for decrypting the permission configuration file provided by an embodiment of the present application. After S702, obtaining the second encrypted configuration file currently stored in the cloud and calculating the second digital fingerprint of the second encrypted configuration file, the following steps are further included:

[0146] S801. In the case where the first digital fingerprint is consistent with the second digital fingerprint, compare the metadata information of the second encrypted configuration file with the metadata information of the first encrypted configuration file.

[0147] Specifically, when the vehicle owner logs in to the permission management system of other vehicles or needs to re-obtain the permission configuration file, first compare the first digital fingerprint with the second digital fingerprint. When the first digital fingerprint is consistent with the second digital fingerprint, compare the metadata information of the second encrypted configuration file with the metadata information of the first encrypted configuration file to ensure the integrity and source legality of the permission configuration file.

[0148] S802. When the metadata information of the second encrypted configuration file is consistent with the metadata information of the first encrypted configuration file, use a preset decryption strategy to decrypt the second encrypted configuration file to obtain the permission configuration file corresponding to the decrypted second encrypted configuration file.

[0149] S803. According to the permission configuration file corresponding to the decrypted second encrypted configuration file, send a sixth permission update message to all application programs. The sixth permission update message is used to update the permission access list of each application program.

[0150] Specifically, when the metadata information of the second encrypted configuration file is consistent with the metadata information of the first encrypted configuration file, use a preset decryption strategy to decrypt the second encrypted configuration file to obtain the permission configuration file corresponding to the decrypted second encrypted configuration file. By parsing the key parameters in the permission configuration file corresponding to the decrypted second encrypted configuration file, generate a sixth permission update message. The sixth permission update message is used to update the permission access list of each application program in the permission management system of other vehicles, or to update the permission access list of the application programs that need to be synchronously updated due to re-login or permission change in the current vehicle permission management system.

[0151] Exemplarily, the key parameters in the permission configuration file corresponding to the decrypted second encrypted configuration file at least include the name of each authorized permission item, the identifier of each authorized permission item, and the permission validity period. The sixth permission update message is generated according to the key parameters, and the sixth permission update message at least includes the authorized permission item list and the permission validity period. By sending the sixth permission update message to each application program, each application program updates the permission access list of each application program according to the sixth permission update message to ensure that the authorized permission items are correctly called.

[0152] Exemplarily, when obtaining the permission configuration file from the cloud, each download operation is detailedly recorded in the operation log. The operation log includes the device information and download time of the download, etc., which is convenient for subsequent review and analysis to timely discover possible security problems.

[0153] In this embodiment, by verifying the consistency of the digital fingerprint and the metadata information, when the vehicle owner logs in to the permission management system on other vehicles or needs to re-obtain the permission configuration file, the secure acquisition of the permission configuration file and the timely update of the application permission access list are realized, ensuring the accuracy and security of permission management.

[0154] Referring to Figure 10 , a schematic structural diagram of a permission management system provided by an embodiment of the present application is shown, including:

[0155] A first response module 101, configured to generate a permission configuration file in response to a permission management operation of a user in a first permission management interface, where the permission configuration file includes at least an authorized permission item and a permission validity period.

[0156] An analysis module 102, configured to analyze key parameters in the permission configuration file and generate first permission update information.

[0157] A first sending module 103, configured to send the first permission update information to all applications, so that each application updates the permission access list of each application based on the first permission update information, where the application is configured to call a target device corresponding to an authorized permission item within the permission validity period.

[0158] Exemplarily, Figure 11 A schematic diagram of the overall framework of the permission management system provided by an embodiment of the present application is shown. Referring to Figure 11 , the in-vehicle system includes an application and an authorization management system. The authorization management system is used to provide an authorization management interface, judge the permission validity period, generate a permission configuration file, and provide a callback list. The application includes an authorization management SDK, and the authorization management SDK is used to bind services, judge permission items, apply for permission items, and register callbacks. Communication between the authorization management SDK and the authorization management system is implemented through AIDL. After generating the permission configuration file, the authorization management system uploads the permission configuration file to cloud storage through HTTPS. When the metadata information and the digital fingerprint are consistent, the authorization management system can obtain the permission configuration file from the cloud database to implement the permission configuration of the application.

[0159] In some embodiments, the permission validity period includes the number of authorizations, and the permission management system further includes:

[0160] A cancellation module, configured to cancel the number of authorizations in response to a power-off restart signal sent by the in-vehicle system.

[0161] A first display module, configured to display a second permission management interface when the cancelled number of authorizations is less than or equal to 0.

[0162] A first update module, configured to update a permission configuration file in response to a user's permission management operation in a second permission management interface.

[0163] A second sending module, configured to send second permission update information to all application programs, where the second permission update information is used to update the permission access list of each application program again.

[0164] In some embodiments, the permission validity period includes a permission valid duration, and the permission management system further includes:

[0165] A time acquisition module, configured to acquire a response time and a current time, where the response time represents the specific time of responding to the user's permission management operation in a first permission management interface.

[0166] A duration calculation module, configured to calculate a permission usage duration according to the response time and the current time, where the permission usage duration represents the usage duration of an authorized permission item.

[0167] An item loading module, configured to load an authorized permission item when the permission usage duration is less than the permission valid duration.

[0168] A second display module, configured to display a third permission management interface when the permission usage duration is greater than or equal to the permission valid duration.

[0169] A second update module, configured to update a permission configuration file in response to a user's permission management operation in a third permission management interface.

[0170] A third sending module, configured to send third permission update information to all application programs, where the third permission update information is used to update the permission access list of each application program again.

[0171] In some embodiments, the permission management operation includes canceling an authorized permission item, and the permission management system further includes:

[0172] A second response module, configured to determine a target permission in response to the user's permission management operation of canceling an authorized permission item.

[0173] A first identification module, configured to identify target permission information in a permission configuration file, where the target permission information represents the associated information of the target permission in the permission configuration file.

[0174] A third update module, configured to update the permission configuration file using the target permission information.

[0175] A fourth sending module, configured to send fourth permission update information to all application programs, where the fourth permission update information is used to instruct each application program to stop using the target permission.

[0176] In some embodiments, the permission management system further includes:

[0177] A second recognition module, configured to enable each application to recognize target data according to the target permission, where the target data represents the data obtained through the target permission.

[0178] A data processing module, configured to enable each application to perform desensitization processing on the target data according to a preset security policy.

[0179] In some embodiments, the permission management system further includes:

[0180] An encryption module, configured to perform encryption processing on the permission configuration file to generate a first encrypted configuration file.

[0181] An upload module, configured to upload the first encrypted configuration file to the cloud and generate a first digital fingerprint of the first encrypted configuration file.

[0182] An association module, configured to record the metadata information of the first encrypted configuration file, associate the metadata information with the first digital fingerprint, where the metadata information of the first encrypted configuration file at least includes the timestamp information and source device information for uploading the first encrypted configuration file to the cloud.

[0183] In some embodiments, the permission management system further includes:

[0184] A file backup module, configured to upload the permission configuration file to the cloud for backup and generate a configuration file copy.

[0185] A fingerprint calculation module, configured to obtain a second encrypted configuration file currently stored in the cloud and calculate a second digital fingerprint of the second encrypted configuration file.

[0186] A file copy acquisition module, configured to obtain the configuration file copy from the cloud in the case where the first digital fingerprint is inconsistent with the second digital fingerprint.

[0187] A fifth sending module, configured to send a fifth permission update message to all applications according to the configuration file copy, where the fifth permission update message is used to update the permission access list of each application.

[0188] In some embodiments, the permission management system further includes:

[0189] A comparison module, configured to compare the metadata information of the second encrypted configuration file with the metadata information of the first encrypted configuration file in the case where the first digital fingerprint is consistent with the second digital fingerprint.

[0190] A decryption module, configured to, when the metadata information of the second encryption configuration file is consistent with the metadata information of the first encryption configuration file, use a preset decryption strategy to decrypt the second encryption configuration file and obtain the permission configuration file corresponding to the decrypted second encryption configuration file.

[0191] A sixth sending module, configured to send sixth permission update information to all application programs according to the permission configuration file corresponding to the decrypted second encryption configuration file, where the sixth permission update information is used to update the permission access list of each application program again.

[0192] For the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For the relevant parts, refer to the partial description of the method embodiment.

[0193] Each embodiment in this specification is described in a progressive manner. Each embodiment focuses on the differences from other embodiments. For the same and similar parts among the embodiments, reference can be made to each other.

[0194] The embodiment of the present application further provides a vehicle, including a permission management system, and / or, executing any one of the permission management methods.

[0195] The above provides a detailed introduction to a permission management method, system, and vehicle provided by the present application. Specific examples are used in this article to elaborate on the principle and implementation manner of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific implementation manner and application scope. In summary, the content of this specification should not be construed as a limitation to the present application.

Claims

1. A rights management method, characterized in that: The steps include: In response to a user's permission management operation in the first permission management interface, generating a permission configuration file, the permission configuration file at least including an authorized permission item and a permission validity period; Parsing key parameters in the authority configuration file to generate first authority update information; The first permission update information is sent to all applications, so that each application updates its permission access list based on the first permission update information, wherein the application is configured to call a target device corresponding to the authorization permission item within the validity period of the permission.

2. The rights management method according to claim 1, characterized in that: The validity period of the permission includes the number of authorizations; After sending the first permission update information to all applications, the method further includes: In response to a power-off restart signal sent by the vehicle computer system, canceling the number of authorizations; If the number of authorizations after cancellation is less than or equal to 0, the second permission management interface is displayed; In response to a permission management operation performed by a user in the second permission management interface, updating the permission configuration file; Second permission update information is sent to all the application programs, where the second permission update information is used to update the permission access list of each application program again.

3. The rights management method according to claim 1, characterized in that: The validity period of the permission includes the validity period of the permission; After sending the first permission update information to all applications, the method further includes: Acquire the response time and the current time, wherein the response time represents the specific time of responding to the user's permission management operation in the first permission management interface; Calculate the permission usage duration according to the response time and the current time, where the permission usage duration represents the usage duration of the authorized permission item; When the permission usage duration is less than the permission validity duration, loading the authorization permission item; When the permission usage duration is greater than or equal to the permission validity duration, displaying a third permission management interface; In response to a permission management operation performed by a user in the third permission management interface, updating the permission configuration file; The third permission update information is sent to all the application programs, where the third permission update information is used to update the permission access list of each application program again.

4. The rights management method according to claim 1, characterized in that: The permission management operation includes canceling the authorization permission item; After generating a rights configuration file in response to the rights management operation of the user in the first rights management interface, the method further includes: In response to a user canceling a permission management operation of the authorization permission item, determining a target permission; Identifying target permission information in the permission configuration file, wherein the target permission information represents associated information of the target permission in the permission configuration file; Using the target permission information, updating the permission configuration file; Sending fourth permission update information to all the application programs, where the fourth permission update information is used to instruct each application program to stop using the target permission.

5. The rights management method according to claim 4, characterized in that: After sending the fourth permission update information to all the applications, the method further includes: Each of the applications identifies target data according to the target permission, where the target data represents data obtained through the target permission; Each application program desensitizes the target data according to a preset security policy.

6. The rights management method according to any one of claims 1 to 5, characterized in that: After generating a rights configuration file in response to the rights management operation of the user in the first rights management interface, the method further includes: Encrypting the authority configuration file to generate a first encrypted configuration file; Uploading the first encrypted configuration file to the cloud and generating a first digital fingerprint of the first encrypted configuration file; The metadata information of the first encrypted configuration file is recorded, and the metadata information is associated with the first digital fingerprint, wherein the metadata information of the first encrypted configuration file at least includes timestamp information and source device information of uploading the first encrypted configuration file to the cloud.

7. The rights management method according to claim 6, characterized in that: After generating a rights configuration file in response to the rights management operation of the user in the first rights management interface, the method further includes: Uploading the permission configuration file to the cloud for backup and generating a copy of the configuration file; Obtaining a second encrypted configuration file currently stored in the cloud, and calculating a second digital fingerprint of the second encrypted configuration file; When the first digital fingerprint is inconsistent with the second digital fingerprint, obtaining the copy of the configuration file from the cloud; According to the configuration file copy, fifth permission update information is sent to all the application programs, where the fifth permission update information is used to update the permission access list of each application program.

8. The rights management method according to claim 7, characterized in that: After obtaining the second encrypted configuration file currently stored in the cloud and calculating the second digital fingerprint of the second encrypted configuration file, the following steps are also included: When the first digital fingerprint is consistent with the second digital fingerprint, comparing the metadata information of the second encrypted configuration file with the metadata information of the first encrypted configuration file; When the metadata information of the second encrypted configuration file is consistent with the metadata information of the first encrypted configuration file, decrypt the second encrypted configuration file using a preset decryption strategy to obtain a rights configuration file corresponding to the decrypted second encrypted configuration file; According to the permission configuration file corresponding to the decrypted second encrypted configuration file, sixth permission update information is sent to all application programs, wherein the sixth permission update information is used to update the permission access list of each application program again.

9. A rights management system, characterized in that: include: A first response module, configured to generate a rights configuration file in response to a user's rights management operation in the first rights management interface, wherein the rights configuration file at least includes an authorized rights item and a rights validity period; A parsing module, used for parsing key parameters in the rights configuration file to generate first rights update information; The first sending module is used to send the first permission update information to all applications, so that each application updates the permission access list of each application based on the first permission update information, wherein the application is configured to call the target device corresponding to the authorization permission item within the validity period of the permission.

10. A vehicle, characterized in that: The method comprises the rights management system as claimed in claim 9, and / or executes the rights management method as claimed in any one of claims 1 to 8.

Images