Authority management method and device, vehicle and medium

Abstract

The invention relates to an authority management method and device, a vehicle and a medium. The method comprises the step of displaying a mode selection interface in a central control screen of the vehicle. And if the user performs selection operation on the privacy mode in the mode selection interface, switching the mode of the vehicle-mounted system to the privacy mode. Based on the privacy mode, basic permissions related to driving safety are authorized to applications installed in the vehicle, and permission information for each application is determined. And if the user selects the networking mode in the mode selection interface, switching the mode of the vehicle-mounted system to the networking mode. And then displaying a permission checking interface, and determining permission information of each application program based on an authorization operation of a user for the first permission of each application program in the permission checking interface. The permission checking interface is used for configuring the permission state of the authorizable permission corresponding to each application program. According to the technical scheme, the personalized demand of the user for privacy is ensured, and the authorization processing efficiency and the user experience are improved.

Description

Technical Field

[0001] The present invention relates to the technical field of authority management, and in particular to an authority management method, device, vehicle and medium. Background Art

[0002] With the continuous advancement of technology, the networking and intelligence of automobiles have become a general trend. People's demand for automobiles has changed from simply solving travel problems to expecting a younger and smarter entertainment system. Based on this, various local applications and third-party applications have been connected to the car system to meet the diverse needs of different users.

[0003] In the above implementation process, in order to ensure user privacy, the existing technology usually implements it by limiting the permissions of applications to access the vehicle system. However, under this implementation, an application usually calls multiple permissions in the vehicle system, and the user will be frequently asked to confirm whether to authorize these permissions to the application. The authorization process is complicated and inefficient, and the user experience is poor. Summary of the invention

[0004] One of the purposes of the present invention is to provide a permission management method to solve the problems of complex authorization processing, low efficiency and poor user experience; the second purpose is to provide a permission management device; the third purpose is to provide a car; and the fourth purpose is to provide a computer-readable storage medium.

[0005] In order to achieve the above object, the technical solution adopted by the present invention is as follows:

[0006] A method for managing permissions, applied to a vehicle-mounted system, comprising:

[0007] Displaying a mode selection interface on the vehicle's central control screen;

[0008] If the user selects the privacy mode in the mode selection interface, the mode of the vehicle system is switched to the privacy mode;

[0009] Based on the privacy mode, authorizing basic permissions related to driving safety to applications installed in the vehicle, and determining permission information for each application;

[0010] If the user selects the networking mode in the mode selection interface, the mode of the vehicle system is switched to the networking mode;

[0011] Display a permission check interface, which is used to configure the permission status of the authorized permissions corresponding to each application;

[0012] Based on the authorization operation of the user for the first permission of each application in the permission selection interface, the permission information of each application is determined.

[0013] According to the above technical means, by dividing the vehicle system into privacy mode and networking mode, in the networking mode, the user is shown a permission check interface, so that the user can authorize or not authorize multiple permissions of multiple applications at one time; in the privacy mode, the vehicle system only authorizes the application with basic permissions related to driving safety. In this way, while ensuring the user's personalized needs for privacy, the authorization process for the application is simplified, and the efficiency of authorization processing and the user's experience are improved.

[0014] Further, based on the privacy mode, authorizing basic permissions related to driving safety to applications installed in the vehicle, and determining permission information of each application, including:

[0015] Based on the privacy mode, authorizing the basic permissions to each application program, and determining initial permission information for each application program;

[0016] For each application, obtaining a permission authorization request for a second permission of the application;

[0017] Based on the permission authorization request, displaying authorization prompt information for the second permission on the central control screen;

[0018] In response to the user's authorization confirmation operation for the second permission, the initial permission information of the application is updated according to the second permission to determine the permission information of each application.

[0019] Based on the above technical means, the user's personalized needs for permission authorization are guaranteed while protecting the user's privacy to the greatest extent.

[0020] Further, based on the permission authorization request, displaying authorization prompt information for the second permission on the central control screen includes:

[0021] If the user has not denied authorization for the second permission at a previous moment, authorization prompt information for the second permission is displayed on the central control screen based on the permission authorization request.

[0022] According to the above technical means, considering that users have higher requirements for data privacy in privacy mode, when the user has denied authorization for the second permission, it means that the user does not want to authorize the second permission for the application, and there is no need to continue to confirm with the user. In other words, for a certain application, if the user previously disagrees to authorize a certain permission for the application, the subsequent in-vehicle system will not ask the user to confirm it again after obtaining the permission authorization request, further improving the user's experience.

[0023] Further, the displaying of the mode selection interface on the central control screen of the vehicle includes:

[0024] If the user account logged in to the in-vehicle system has not been logged in to the in-vehicle system at a previous time, the mode selection interface is displayed on the central control screen.

[0025] According to the above technical means, when the vehicle system detects that the user account is logging in to the vehicle system for the first time, in order to determine the user's demand for data privacy, it is necessary to display a mode selection interface for the user for selection, thereby meeting the user's personalized needs for data privacy.

[0026] Furthermore, the method further comprises:

[0027] If the user account logged in to the in-vehicle system has logged in to the in-vehicle system at a previous time, determining a target mode associated with the user account;

[0028] The mode of the vehicle-mounted system is switched to the target mode, and authorization information of each application in the target mode is obtained from a server.

[0029] According to the above technical means, when the vehicle system detects that the user account is logging in to the vehicle system for the first time, in order to determine the user's demand for data privacy, it is necessary to display a mode selection interface for the user for selection, thereby meeting the user's personalized needs for data privacy.

[0030] Furthermore, the method further comprises:

[0031] When the vehicle is powered off, the user account logged in the vehicle system is bound to the current mode, and the mode identifier of the current mode and the permission information of each application are sent to the server.

[0032] According to the above technical means, by sending the mode identifier of the current mode and the permission information of each application to the server, the next time the user uses the vehicle, the vehicle system can determine the mode selected by the user last time and the permission information of each application under the mode from the server based on the user account logged in by the user, thereby avoiding the user from repeatedly setting permissions and improving processing efficiency and user experience.

[0033] Further, the method comprises:

[0034] An application management interface is displayed, where the application management interface is used to display authorization information for each application.

[0035] According to the above technical means, users can click on a specific application and individually check or uncheck its underlying permissions to change permissions. This allows targeted batch management of permissions for each application to ensure that privacy is fully protected.

[0036] Further, the method comprises:

[0037] A permission management interface is displayed, wherein the permission management interface is used to display an application list corresponding to each permission, wherein the application list stores application identifiers having the permission.

[0038] Based on the above technical means, users can easily manage a certain type of permissions in a unified manner, achieve more efficient permission management, and improve the efficiency of privacy protection.

[0039] A rights management device is applied to an on-board system of a vehicle, the device comprising:

[0040] A display module, used to display a mode selection interface on the vehicle's central control screen;

[0041] A switching module, configured to switch the mode of the vehicle-mounted system to the privacy mode if the user selects the privacy mode in the mode selection interface;

[0042] a determination module, configured to authorize basic permissions related to driving safety to applications installed in the vehicle based on the privacy mode, and determine permission information of each application;

[0043] The switching module is further configured to switch the mode of the vehicle system to the networking mode if the user selects the networking mode in the mode selection interface;

[0044] The display module is further used to display a permission check interface, where the permission check interface is used to configure the permission status of the authorizable permissions corresponding to each application;

[0045] The determination module is further configured to determine permission information of each application based on the authorization operation of the user for the first permission of each application in the permission selection interface.

[0046] Furthermore, the determination module is specifically used to:

[0047] Based on the privacy mode, authorizing the basic permissions to each application program, and determining initial permission information for each application program;

[0048] For each application, obtaining a permission authorization request for a second permission of the application;

[0049] Based on the permission authorization request, displaying authorization prompt information for the second permission on the central control screen;

[0050] In response to the user's authorization confirmation operation for the second permission, the initial permission information of the application is updated according to the second permission to determine the permission information of each application.

[0051] Furthermore, the determination module is specifically used to:

[0052] If the user has not denied authorization for the second permission at a previous moment, authorization prompt information for the second permission is displayed on the central control screen based on the permission authorization request.

[0053] Furthermore, the display module is specifically used for:

[0054] If the user account logged in to the in-vehicle system has not been logged in to the in-vehicle system at a previous time, the mode selection interface is displayed on the central control screen.

[0055] Furthermore, the rights management device further includes:

[0056] The determination module is further configured to determine a target mode associated with the user account if the user account logged into the in-vehicle system has logged into the in-vehicle system at a previous time;

[0057] The acquisition module is used to switch the mode of the vehicle-mounted system to the target mode and acquire the authorization information of each application in the target mode from the server.

[0058] Furthermore, the rights management device further includes:

[0059] The sending module is used to bind the user account logged in the vehicle system with the current mode when the vehicle is powered off, and send the mode identifier of the current mode and the permission information of each application to the server.

[0060] Furthermore, the display module is also used to display an application management interface, and the application management interface is used to display authorization information of each application.

[0061] Furthermore, the display module is also used to display a permission management interface, and the permission management interface is used to display an application list corresponding to each permission, and the application list stores the application identifiers having the permission.

[0062] A car comprises: a vehicle body, an on-board processor, a memory, and computer-executable instructions stored in the memory and executable on the on-board processor, wherein the on-board processor is used to implement the above-mentioned permission management method when executing the computer-executable instructions.

[0063] A computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to implement the above-mentioned permission management method when executed by an on-board processor.

[0064] Beneficial effects of the present invention:

[0065] (1) The vehicle system is divided into a privacy mode and a networking mode. In the networking mode, a permission check interface is displayed to the user, so that the user can authorize or not authorize multiple permissions of multiple applications at one time. In the privacy mode, the vehicle system only authorizes the application with basic permissions related to driving safety. In this way, while ensuring the user's personalized needs for privacy, the authorization process for the application is simplified, and the authorization processing efficiency and user experience are improved.

[0066] (2) Dynamic authorization: The main purpose is to allow users to adjust the permission settings of the application at any time during use while protecting user privacy, avoiding unnecessary permission exposure and achieving personalized privacy management with high flexibility.

[0067] (3) Maximizing privacy protection: The privacy mode provides users with strict privacy protection. All data processing is performed locally and does not involve uploading to the cloud.

[0068] (4) Personalized settings: The user's authorization selections and privacy preferences will be automatically synchronized to the cloud, ensuring that the last settings can be continued the next time they are used, simplifying operations.

[0069] (5) Intelligent Management: By combining permission management with application management, users can comprehensively manage the privacy and permission settings of the system on a centralized platform, with intuitive and easy operation. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] Figure 1A flowchart of a first embodiment of a rights management method provided by an embodiment of the present invention;

[0071] Figure 2 A schematic diagram of a scenario of a rights management method provided by an embodiment of the present invention;

[0072] Figure 3 A flowchart of a second embodiment of the rights management method provided by the embodiment of the present invention;

[0073] Figure 4 A flowchart of a third embodiment of the rights management method provided by the embodiment of the present invention;

[0074] Figure 5 A schematic diagram of the structure of a rights management device provided by an embodiment of the present invention;

[0075] Figure 6 A schematic structural diagram of a vehicle provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0076] The following will describe the embodiments of the present invention with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the contents disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and the details in this specification can also be modified or changed in various ways based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention, not for limiting the scope of protection of the present invention.

[0077] It should be noted that the illustrations provided in the following embodiments are only schematic illustrations of the basic concept of the present invention, and thus the drawings only show components related to the present invention rather than being drawn according to the number, shape and size of components in actual implementation. In actual implementation, the type, quantity and proportion of each component may be changed arbitrarily, and the component layout may also be more complicated.

[0078] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in the present invention are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and corresponding operation entrances shall be provided for users to choose to authorize or refuse.

[0079] Before introducing the embodiments of the present invention, the application background of the embodiments of the present invention is first explained:

[0080] With the continuous advancement of technology, the networking and intelligence of automobiles have become a general trend. People's demand for automobiles has changed from simply solving travel problems to expecting a younger and smarter entertainment system. Based on this, various local applications and third-party applications have been connected to the car system to meet the diverse needs of different users.

[0081] However, as the rate of third-party applications increases, it is impossible to solve the problem of third-party applications privately opening corresponding permissions to collect user information, which brings a series of privacy risks such as personal information leakage. With the popularization of personal information protection awareness, privacy protection has also become one of the concerns of users when buying a car. Therefore, terminal manufacturers also need to think about how to better protect user privacy.

[0082] In order to ensure user privacy, existing technologies usually implement this by limiting the permissions of applications. Specifically, when an application calls a certain permission of the vehicle system for the first time, the vehicle system usually pops up a permission prompt box. These permission prompt boxes will clearly inform users which permissions the application is requesting and require users to choose whether to grant them.

[0083] For example, when a music player app is started for the first time, it needs to request storage access permission in order to read local music files or store downloaded music files in local storage space. At this time, the car system will pop up a permission prompt box: "[Music app name] is requesting access to your storage to read local music files. Do you want to allow it?" The user can choose to allow or deny according to their needs.

[0084] However, in the prior art, an application usually calls multiple permissions in the vehicle system, and the user will be frequently asked to confirm whether to authorize these permissions to the application. The authorization process is complicated, inefficient, and the user experience is poor.

[0085] Based on the above technical issues, and taking into account the different needs of different users for data privacy, the car system can be divided into privacy mode and networking mode. Among them, if the user has a higher demand for data privacy, the mode of the car system can be switched to privacy mode. In privacy mode, the car system only authorizes the application with basic permissions related to driving safety. If the user has a lower demand for data privacy, the mode of the car system can be switched to networking mode. In networking mode, the car system will display a permission check interface for the user. The permission check interface is used to configure the permission status of the authorizable permissions corresponding to each application. Users can authorize or not authorize multiple permissions of multiple applications at one time. In this way, while ensuring the user's personalized needs for privacy, the authorization process for the application is simplified, and the efficiency of authorization processing and the user experience are improved.

[0086] The technical solution of the present invention is described in detail below through specific embodiments.

[0087] It should be noted that the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0088] Figure 1 The flowchart of the first embodiment of the rights management method provided by the embodiment of the present invention is as follows. Figure 1 As shown, the permission management method is applied to the vehicle-mounted system of the vehicle, and the permission management method may include the following steps:

[0089] S11. Displaying a mode selection interface on the central control screen of the vehicle.

[0090] Among them, the mode selection interface is used to provide users with privacy mode options and networking mode options to meet users' different data privacy needs and scenarios.

[0091] It should be understood that the specific explanations and descriptions of the privacy mode and the networking mode will be explained in subsequent steps and will not be repeated here.

[0092] In real-world scenarios, a family usually has one or more cars, which means that multiple family members may share a car. However, due to different privacy requirements of different family members, each family member needs to re-authorize the application based on their own needs every time they use the car, which is a complicated process and poor user experience.

[0093] Considering that users can log in to their accounts in the vehicle's corresponding on-board system when using a vehicle, the account can be associated with the user's own mode settings, thereby ensuring that the previous settings can be used next time the vehicle is used.

[0094] The above-mentioned self-setting of the mode includes the mode set by the user (privacy mode or networking mode) and the permission information of each application in the mode.

[0095] The permission information of each application is used to indicate the permissions authorized to the application and the permissions not authorized to the application.

[0096] Furthermore, in a possible implementation, if the user account logged into the vehicle system has logged into the vehicle system at a previous time, the target mode associated with the user account is determined, the mode of the vehicle system is switched to the target mode, and the authorization information of each application in the target mode is obtained from the server.

[0097] The target mode is a privacy mode or a networking mode.

[0098] In this implementation, for user accounts that are not used for the first time in the vehicle-side system, the vehicle-mounted system will synchronize the user's previous mode settings from the server and use them. By memorizing and using the mode settings, redundant authorization processing is avoided and efficiency is improved.

[0099] In another possible implementation, if the user account logged in to the vehicle system has not been logged in to the vehicle system at a previous moment, the mode selection interface is displayed on the central control screen.

[0100] In actual applications, the vehicle system can obtain the latest privacy policy from the server. The latest privacy policy is used to explain to the user the permissions that can be opened to the application in the networking mode. After that, the mode selection interface is displayed through the central control screen, and the latest privacy policy is displayed in the form of a pop-up window in the mode selection interface, and the consent control and the disagree control are displayed in the pop-up window. Among them, if the user clicks the disagree control, it is determined that the user has selected the privacy mode in the mode selection interface; if the user clicks the consent control, it is determined that the user has selected the networking mode in the mode selection interface.

[0101] In this implementation, when the vehicle system detects that the user account is logging in to the vehicle system for the first time, in order to determine the user's demand for data privacy, it is necessary to display a mode selection interface for the user for selection, thereby meeting the user's personalized needs for data privacy.

[0102] In another possible implementation, since the user's demand for data privacy is variable, the user can switch the mode based on the current demand for data privacy. The in-vehicle system responds to the user's mode switching operation and displays a mode selection interface for the user.

[0103] It should be understood that the application can be a local application or a third-party application.

[0104] S12: If the user selects the privacy mode in the mode selection interface, the mode of the vehicle system is switched to the privacy mode.

[0105] Optionally, a privacy mode control and a networking mode control may be displayed in the mode selection interface. If the user clicks the privacy mode control, it is deemed that the user has selected the privacy mode in the mode selection interface, and the mode of the vehicle system is switched to the privacy mode.

[0106] Optionally, referring to the possible implementation in S11, the latest privacy policy can be displayed in the mode selection interface in the form of a pop-up window, and an agree control and a disagree control can be displayed. If the user clicks the disagree control, it is determined that the user has selected the privacy mode in the mode selection interface, and the mode of the vehicle system is switched to the privacy mode.

[0107] S13. Based on the privacy mode, authorize basic permissions related to driving safety to applications installed in the vehicle, and determine permission information for each application.

[0108] Among them, the privacy mode is designed to maximize the protection of user privacy. After the vehicle system mode is switched to privacy mode, the minimum vehicle-side permissions are opened to the application. The minimum vehicle-side permissions refer to the basic permissions related to driving safety in the vehicle system to ensure driving safety.

[0109] Furthermore, in privacy mode, the vehicle system will strictly limit the calling of permissions. When an application needs to call permissions other than basic permissions, user authorization is required.

[0110] In a possible implementation, based on the privacy mode, basic permissions are granted to each application, and the initial permission information of each application is determined. For each application, a permission authorization request for a second permission of the application is obtained. Based on the permission authorization request, authorization prompt information for the second permission is displayed on the central control screen. In response to the user's authorization confirmation operation for the second permission, the initial permission information of the application is updated according to the second permission, and the permission information of each application is determined.

[0111] In actual applications, the privacy mode only opens basic permissions by default, and the initial permission information is used to authorize basic permissions for each application. When an application tries to call a second permission (such as microphone, camera, location) other than basic permissions, it is necessary to check whether the second permission has been authorized. If the application does not obtain authorization for the second permission, the application will send a permission authorization request to the vehicle system. Based on the permission authorization request, the vehicle system triggers an authorization pop-up window, which displays authorization prompt information for the second permission to ask the user whether the user is allowed to call the second permission. The user can choose whether to allow the application to access the permission to ensure that the application cannot access the second permission without explicit permission, thereby realizing dynamic authorization of the application.

[0112] In the above implementation, the personalized needs of users for permission authorization are guaranteed while protecting user privacy to the greatest extent.

[0113] Furthermore, before the central control screen displays the authorization prompt information for the second permission, it is also necessary to determine whether the user has previously denied authorization for the second permission. If the user has not previously denied authorization for the second permission, the central control screen displays the authorization prompt information for the second permission based on the permission authorization request. If the user has previously denied authorization for the second permission, the central control screen does not display the authorization prompt information for the second permission.

[0114] Considering that users have higher requirements for data privacy in privacy mode, when the user denies the authorization of the second permission, it means that the user does not want to authorize the second permission for the application, and there is no need to continue to confirm with the user. In other words, for a certain application, if the user does not agree to authorize a certain permission for the application before, the subsequent in-vehicle system will not ask the user to confirm it again after obtaining the permission authorization request, further improving the user experience.

[0115] Optionally, the vehicle system can memorize the permission information of each application to avoid repeated pop-up authorization pop-ups each time the application is restarted. To further protect the user's data privacy, the authorization information of the application can be restored to the initial authorization information after closing the application, so that the user will be prompted to authorize again the next time the application is started, ensuring that the corresponding permissions are allowed to be called only with the user's explicit consent.

[0116] Optionally, in privacy mode, user data will not be uploaded to the server. Furthermore, all networking functions in the vehicle system can be disabled to further ensure the privacy of the user.

[0117] S14: If the user selects the networking mode in the mode selection interface, the mode of the vehicle system is switched to the networking mode.

[0118] Optionally, a privacy mode control and a networking mode control may be displayed in the mode selection interface. If the user clicks the networking mode control, it is deemed that the user has selected the networking mode in the mode selection interface, and the mode of the vehicle system is switched to the networking mode.

[0119] Optionally, referring to the possible implementation in S11, the latest privacy policy can be displayed in the mode selection interface in the form of a pop-up window, and an agreement control and a disagreement control can be displayed. If the user clicks the agreement control, it is determined that the user has selected the networking mode in the mode selection interface, and the mode of the vehicle system is switched to the networking mode.

[0120] S15. Display the permission selection interface.

[0121] Among them, the permission check interface is used to configure the permission status of the authorizable permissions corresponding to each application.

[0122] In actual applications, the permission check interface can display multiple applications and the permission status of the authorized permissions corresponding to each application, which includes authorized and unauthorized. Furthermore, the specific function corresponding to each authorized permission can also be displayed. Users can adjust the permission status of the authorized permissions corresponding to each application according to their own needs.

[0123] S16: Determine permission information of each application based on the user's authorization operation for the first permission of each application in the permission selection interface.

[0124] Exemplarily, the permission status of the authorizable permission corresponding to each application in the permission check interface can be displayed in the form of a check box. If the check box of a certain authorizable permission of an application is not checked, it means that the authorizable permission is not authorized for the application. If the user wants to authorize the authorizable permission for the application, the user can click the check box of the authorizable permission to change the check box to a checked state.

[0125] In the above example, the authorization operation of the user for the first permission of each application in the permission checking interface is the user clicking the check box of the first permission of the application.

[0126] In actual application, in network mode, if the application calls unauthorized third-party permissions, the vehicle system will trigger an authorization pop-up window to remind the user to authorize permissions. The authorization pop-up window includes an agree control and a disagree control. If the user chooses to disagree with the control, the authorization pop-up window will continue to be triggered until the user clicks the agree control or the number of authorization pop-ups exceeds the preset number; if the user chooses to agree to the control, the third permission will be authorized for the application.

[0127] Optionally, the vehicle system can memorize the permission information of each application to avoid repeated pop-up authorization pop-ups each time the application is restarted.

[0128] In networking mode, user data will be uploaded to the server in real time, or uploaded to the server uniformly when the vehicle is powered off.

[0129] In an embodiment of the present invention, a mode selection interface is displayed in the central control screen of the vehicle. If the user selects the privacy mode in the mode selection interface, the mode of the vehicle system is switched to the privacy mode. Then, based on the privacy mode, the basic permissions related to driving safety are authorized to the application installed in the vehicle, and the permission information of each application is determined. If the user selects the networking mode in the mode selection interface, the mode of the vehicle system is switched to the networking mode. Then, a permission check interface is displayed, and the permission information of each application is determined based on the user's authorization operation for the first permission of each application in the permission check interface. The permission check interface is used to configure the permission status of the authorized permissions corresponding to each application. In this technical solution, by dividing the vehicle system into a privacy mode and a networking mode, the permission check interface is displayed to the user in the networking mode, so that the user can authorize or not authorize multiple permissions of multiple applications at one time; in the privacy mode, the vehicle system only authorizes the basic permissions related to driving safety to the application. In this way, while ensuring the user's personalized needs for privacy, the authorization process for the application is simplified, and the authorization processing efficiency and the user's experience are improved.

[0130] Optionally, in some embodiments, when the vehicle is powered off, the user account logged in to the vehicle system can be bound to the current mode, and the mode identifier of the current mode and the permission information of each application can be sent to the server.

[0131] In this embodiment, the mode identifier of the current mode and the permission information of each application are sent to the server, so that the next time the user uses the vehicle, the vehicle system can determine the mode selected by the user last time and the permission information of each application in the mode from the server based on the user account logged in by the user, thereby avoiding the user from repeatedly setting permissions, improving processing efficiency and user experience.

[0132] Next, under the premise that the user account logs in to the vehicle system for the first time, the application scenario of the permission management method is explained.

[0133] Figure 2 A schematic diagram of a scenario of a rights management method provided by an embodiment of the present invention. Figure 2 As shown, the scenario includes: vehicle side and cloud side. The vehicle side is the above-mentioned vehicle-mounted system, and the cloud side is the above-mentioned server.

[0134] In actual application, after the vehicle is powered on, the user logs in to the vehicle, and the vehicle obtains the permission information corresponding to the user account from the cloud. Since this is the first time the user account logs in to the vehicle system, the permission information of the corresponding application cannot be obtained from the cloud, so the latest privacy agreement is obtained from the cloud and displayed on the central control screen. Afterwards, in response to the user's selection of the mode, the network mode or privacy mode selected by the user is run in the cloud, and after the vehicle is powered off, the permission information of the application is uploaded to the cloud for storage.

[0135] Figure 3 Schematic diagram of the flow of the second embodiment of the rights management method provided by the embodiment of the present invention. Figure 3 As shown, the permission management method is applied to the vehicle-mounted system of the vehicle, and the permission management method may include the following steps:

[0136] S31. Log in with user account.

[0137] S32: Determine whether it is the first time to log into the user account in the vehicle system.

[0138] If yes, execute S33; if no, execute S36.

[0139] S33, privacy mode selection.

[0140] If the networking mode is selected, execute S34; if the privacy mode is selected, execute S37.

[0141] S34. Display the permission selection interface.

[0142] S35. Upload the account authorization memory to the cloud.

[0143] Among them, the account authorization memory includes the mode identifier selected by the user and the authorization information of each application in the privacy mode.

[0144] S36. Obtain account authorization memory from the cloud.

[0145] S37. Enable basic permissions.

[0146] S38. Dynamic authorization.

[0147] S39. Upload the account authorization memory to the cloud.

[0148] It should be understood that the implementation method and principle of each step in the embodiment of the present invention have been specifically explained in the above embodiment and will not be repeated here.

[0149] In actual applications, the in-vehicle system can also provide users with more detailed permission management functions. Users can manage the permissions of installed applications through the settings center. The authorization management of the settings center is divided into application management and permission management.

[0150] For example, Figure 4 Schematic diagram of the process of the third embodiment of the rights management method provided by the embodiment of the present invention. Figure 4 As shown, the permission management method is applied to the vehicle-mounted system of the vehicle, and the permission management method may include the following steps:

[0151] S41. Display setting center.

[0152] S42. Authorization management.

[0153] S43. Display the application management interface.

[0154] The application management interface is used to display the authorization information of each application.

[0155] S44. Change multiple permissions of a single application.

[0156] Through the application management interface, users can view all installed applications in the vehicle system and authorize or revoke the permissions of a single application. For example, the user selects an application in the application management interface and chooses to grant or revoke the application's access to certain permissions.

[0157] In actual applications, users can click on a specific application and individually check or uncheck its underlying permissions to change permissions. This allows targeted batch management of permissions for each application to ensure that privacy is fully protected.

[0158] S45. Display the permission management interface.

[0159] The permission management interface is used to display an application list corresponding to each permission, and the application list stores the identifiers of applications with permissions.

[0160] S46. Changes are made to multiple applications with a single permission.

[0161] In actual applications, the permission management interface displays a list of applications with all underlying permissions, and users can click on the corresponding permission to enable or disable its access rights. At the same time, the permission management interface will also display all applications involved in the permission, and users can batch manage the permission settings of multiple applications.

[0162] For example, users can view a list of applications related to these permissions according to specific permission types (such as camera, microphone, location), and manage these applications in batches. For example, users can check or uncheck the access of multiple applications to a certain permission with one click.

[0163] In this way, users can easily manage a certain type of permissions in a unified manner, achieve more efficient permission management, and improve the efficiency of privacy protection.

[0164] Based on the above embodiments, it can be seen that the present invention has the following technical effects:

[0165] Dynamic authorization: The main purpose is to allow users to adjust the application's permission settings at any time during use while protecting user privacy, avoiding unnecessary permission exposure and achieving personalized privacy management with high flexibility.

[0166] Maximize privacy protection: The privacy mode provides users with strict privacy protection. All data processing is performed locally without uploading to the cloud.

[0167] Personalized settings: The user's authorization selections and privacy preferences will be automatically synchronized to the cloud, ensuring that the last settings can be continued the next time they are used, simplifying operations.

[0168] Intelligent management: By combining permission management with application management, users can comprehensively manage the privacy and permission settings of the system on a centralized platform, with intuitive and easy operation.

[0169] In summary, the present invention simplifies the authorization process, greatly improves the user experience by memorizing user selections and centralized permission management, and ensures the privacy and security of users when using the vehicle-mounted system. Users can authorize permissions for multiple applications or turn off authorization with one click, providing a simple permission management experience so that users can easily control the permission settings of all applications. It effectively solves the problem of applications collecting personal information without user authorization, reduces the complexity of authorization operations, and can effectively balance the relationship between user privacy needs and application functions, providing users with a safe and convenient vehicle-mounted system experience, while avoiding the trouble caused by frequent authorization pop-ups.

[0170] The present invention can be used for vehicle-side privacy protection. More specifically, by controlling the underlying permissions of the operating system and the one-click authorization and multiple authorization methods, the user's one-click privacy protection and different authorizations for different users can be achieved. At the same time, it can also be applied to other systems and terminals involving privacy protection, such as mobile phones.

[0171] The following are embodiments of the device of the present invention, which can be used to implement the method embodiments of the present invention. For details not disclosed in the device embodiments of the present invention, please refer to the method embodiments of the present invention.

[0172] Figure 5 Schematic diagram of the structure of the rights management device provided by the embodiment of the present invention. Figure 5 As shown, the authority management device 50 is applied to the vehicle-mounted system of the vehicle, and the authority management device 50 includes:

[0173] The display module 51 is used to display the mode selection interface on the central control screen of the vehicle.

[0174] The switching module 52 is used to switch the mode of the vehicle system to the privacy mode if the user selects the privacy mode in the mode selection interface.

[0175] The determination module 53 is used to authorize basic permissions related to driving safety to applications installed in the vehicle based on the privacy mode and determine permission information of each application.

[0176] The switching module 52 is further configured to switch the mode of the vehicle-mounted system to the networking mode if the user selects the networking mode in the mode selection interface.

[0177] The display module 51 is also used to display a permission selection interface, which is used to configure the permission status of the authorizable permissions corresponding to each application.

[0178] The determination module 53 is further configured to determine the permission information of each application based on the authorization operation of the user for the first permission of each application in the permission selection interface.

[0179] Furthermore, the determination module 53 is specifically used for:

[0180] Based on the privacy model, basic permissions are granted to each application, and the initial permission information of each application is determined.

[0181] For each application, a permission authorization request for a second permission of the application is obtained.

[0182] Based on the permission authorization request, authorization prompt information for the second permission is displayed on the central control screen.

[0183] In response to the user's authorization confirmation operation for the second permission, the initial permission information of the application is updated according to the second permission, and the permission information of each application is determined.

[0184] Furthermore, the determination module 53 is specifically used for:

[0185] If the user has not denied authorization for the second permission at the previous moment, authorization prompt information for the second permission is displayed on the central control screen based on the permission authorization request.

[0186] Furthermore, the display module 51 is specifically used for:

[0187] If the user account logged in to the vehicle system has not been logged in to the vehicle system before, the mode selection interface will be displayed on the central control screen.

[0188] Furthermore, the rights management device 50 further includes:

[0189] The determination module 53 is further configured to determine a target mode associated with the user account if the user account logged into the vehicle-mounted system has logged into the vehicle-mounted system at a previous time.

[0190] The acquisition module is used to switch the mode of the vehicle system to the target mode and obtain the authorization information of each application in the target mode from the server.

[0191] Furthermore, the rights management device 50 further includes:

[0192] The sending module is used to bind the user account logged in to the vehicle system with the current mode when the vehicle is powered off, and send the mode identifier of the current mode and the permission information of each application to the server.

[0193] Furthermore, the display module 51 is also used to display an application management interface, and the application management interface is used to display the authorization information of each application.

[0194] Furthermore, the display module 51 is also used to display a permission management interface, which is used to display a list of applications corresponding to each permission, and the application list stores identifiers of applications with permissions.

[0195] The rights management device provided in the embodiment of the present invention can be used to execute the rights management method in any of the above embodiments. Its implementation principle and technical effects are similar and will not be repeated here.

[0196] It should be noted that it should be understood that the division of the various modules of the above device is only a division of logical functions. In actual implementation, all or part of them can be integrated into one physical entity, or they can be physically separated. And these modules can all be implemented in the form of software called by processing elements. They can also be implemented in the form of hardware. Some modules can also be implemented in the form of software called by processing elements, and some modules can be implemented in the form of hardware. In addition, all or part of these modules can be integrated together or implemented independently. The processing element here can be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each module above can be completed by an integrated logic circuit of hardware in the processor element or instructions in the form of software.

[0197] Figure 6 The schematic diagram of the structure of the vehicle provided by the embodiment of the present invention is shown in FIG. Figure 6As shown, the vehicle 60 may include: a vehicle body 61, an on-board processor 62, a memory 63, and computer execution instructions stored in the memory 63 and executable on the on-board processor 62. When the on-board processor 62 executes the computer execution instructions, it is used to implement the permission management method provided in any of the aforementioned embodiments.

[0198] Optionally, the above-mentioned components of the vehicle 60 may be connected via a system bus.

[0199] The memory 63 may be a separate storage unit or a storage unit integrated in the vehicle-mounted processor 62. The number of the vehicle-mounted processor 62 is one or more.

[0200] Optionally, the vehicle 60 may also include an interface for interacting with other devices.

[0201] The transceiver is used to communicate with the server, and the transceiver constitutes a communication interface.

[0202] It should be understood that the vehicle-mounted processor 62 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in the present invention may be directly embodied as being executed by a hardware processor, or may be executed by a combination of hardware and software modules in the vehicle-mounted processor 62.

[0203] The system bus may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus, etc. The system bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. The memory 63 may include a random access memory 63 (RAM), and may also include a non-volatile memory 63 (NVM), such as at least one disk memory 63.

[0204] All or part of the steps of the above-mentioned method embodiments can be completed by hardware related to program instructions. The above-mentioned program can be stored in a readable memory 63. When the program is executed, the steps of the above-mentioned method embodiments are executed. The above-mentioned memory 63 (storage medium) includes: read-only memory 63 (ROM), RAM, flash memory 63, hard disk, solid state drive, magnetic tape, floppy disk, optical disc and any combination thereof.

[0205] The vehicle provided in the embodiment of the present invention can be used to execute the permission management method provided in any of the above method embodiments. The implementation principles and technical effects are similar and will not be repeated here.

[0206] An embodiment of the present invention provides a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed on a computer, the computer executes the above-mentioned permission management method.

[0207] The computer-readable storage medium mentioned above can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory, electrically erasable programmable read-only memory, erasable programmable read-only memory, programmable read-only memory, read-only memory, magnetic memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0208] Optionally, the readable storage medium is coupled to the onboard processor so that the onboard processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the onboard processor. The onboard processor and the readable storage medium can be located in an ASIC. Of course, the onboard processor and the readable storage medium can also exist in the device as discrete components.

[0209] An embodiment of the present invention also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one vehicle-mounted processor can read the computer program from the computer-readable storage medium. When at least one vehicle-mounted processor executes the computer program, the above-mentioned permission management method can be implemented.

[0210] It should be understood that the present invention is not limited to the exact construction that has been described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

[0211] The above embodiments are only preferred embodiments for fully illustrating the present invention, and the protection scope of the present invention is not limited thereto. Any equivalent substitution or change made by a person skilled in the art based on the present invention is within the protection scope of the present invention.

Claims

1. A rights management method, characterized in that: The method is applied to an on-board system of a vehicle, and comprises: Displaying a mode selection interface on the vehicle's central control screen; If the user selects the privacy mode in the mode selection interface, the mode of the vehicle system is switched to the privacy mode; Based on the privacy mode, authorizing basic permissions related to driving safety to applications installed in the vehicle, and determining permission information for each application; If the user selects the networking mode in the mode selection interface, the mode of the vehicle system is switched to the networking mode; Display a permission check interface, which is used to configure the permission status of the authorized permissions corresponding to each application; Based on the authorization operation of the user for the first permission of each application in the permission selection interface, the permission information of each application is determined.

2. The method according to claim 1, characterized in that: The step of authorizing basic permissions related to driving safety to the application programs installed in the vehicle based on the privacy mode and determining permission information of each application program includes: Based on the privacy mode, authorizing the basic permissions to each application program, and determining initial permission information for each application program; For each application, obtaining a permission authorization request for a second permission of the application; Based on the permission authorization request, displaying authorization prompt information for the second permission on the central control screen; In response to the user's authorization confirmation operation for the second permission, the initial permission information of the application is updated according to the second permission to determine the permission information of each application.

3. The method according to claim 2, characterized in that The displaying authorization prompt information for the second permission on the central control screen based on the permission authorization request includes: If the user has not denied authorization for the second permission at a previous moment, authorization prompt information for the second permission is displayed on the central control screen based on the permission authorization request.

4. The method according to any one of claims 1 to 3, characterized in that: The displaying of the mode selection interface on the central control screen of the vehicle includes: If the user account logged in to the in-vehicle system has not been logged in to the in-vehicle system at a previous time, the mode selection interface is displayed on the central control screen.

5. The method according to claim 4, characterized in that The method further comprises: If the user account logged in to the vehicle-mounted system has logged in to the vehicle-mounted system at a previous time, determining a target mode associated with the user account; The mode of the vehicle-mounted system is switched to the target mode, and authorization information of each application in the target mode is obtained from a server.

6. The method according to claim 5, characterized in that The method further comprises: When the vehicle is powered off, the user account logged in the vehicle system is bound to the current mode, and the mode identifier of the current mode and the permission information of each application are sent to the server.

7. The method according to any one of claims 1 to 3, characterized in that: The method comprises: An application management interface is displayed, where the application management interface is used to display authorization information for each application.

8. The method according to any one of claims 1 to 3, characterized in that: The method comprises: A permission management interface is displayed, wherein the permission management interface is used to display an application list corresponding to each permission, wherein the application list stores application identifiers having the permission.

9. A rights management device, characterized in that: The vehicle-mounted system is applied to a vehicle, and the device comprises: A display module, used to display a mode selection interface on the vehicle's central control screen; A switching module, configured to switch the mode of the vehicle-mounted system to the privacy mode if the user selects the privacy mode in the mode selection interface; a determination module, configured to authorize basic permissions related to driving safety to applications installed in the vehicle based on the privacy mode, and determine permission information of each application; The switching module is further configured to switch the mode of the vehicle system to the networking mode if the user selects the networking mode in the mode selection interface; The display module is further used to display a permission check interface, where the permission check interface is used to configure the permission status of the authorizable permissions corresponding to each application; The determination module is further configured to determine permission information of each application based on the authorization operation of the user for the first permission of each application in the permission selection interface.

10. A vehicle comprising: A vehicle body, an on-board processor, a memory, and computer execution instructions stored in the memory and executable on the on-board processor, wherein the on-board processor executes the computer execution instructions to implement the permission management method as described in any one of claims 1 to 8.

11. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which, when executed by an on-board processor, are used to implement the permission management method as described in any one of claims 1 to 8.

Images