Method and device for displaying application permission, vehicle and storage medium

Abstract

The invention provides a method and device for displaying application permissions, a vehicle and a readable storage medium, the method is applied to the vehicle, and the method comprises the steps of obtaining N application permissions associated with a target application in response to an application permission management operation executed by a user on the target application; and according to the N application permissions and a preset permission configuration rule, displaying M application permissions on a permission management interface of the target application. According to the method, the application permission not supported by the configuration parameters of the current vehicle can be hidden for the user, and only the application permission supported by the configuration parameters of the current vehicle is displayed for the user, so that confusion or misoperation of the user is avoided; in addition, the cost of application development and maintenance is reduced, and the platformization process of the vehicle application is accelerated.

Description

Technical Field

[0001] The present application relates to the field of vehicles, and more specifically, to an application permission configuration method, device, vehicle, and computer-readable storage medium in the field of vehicles. Background Art

[0002] With the rapid development of intelligent driving technology, an increasing number of vehicle applications are being integrated into intelligent driving functions. To ensure that vehicle applications can safely and effectively access and use the vehicle's device resources and services, vehicle applications typically predefine the set of application permissions required for their operation. However, because different vehicle configurations may have different support capabilities for the same vehicle application, to ensure that the vehicle application can run compatibly on vehicles with multiple configurations, developers often need to customize and package a separate vehicle application version for each configuration, which increases the development and maintenance costs of vehicle applications. Summary of the Invention

[0003] The present application provides a method, device, vehicle and readable storage medium for displaying application permissions. The method can hide application permissions that are not supported by the current vehicle's configuration parameters from the user, and only display application permissions that are supported by the current vehicle's configuration parameters to the user, thereby avoiding user confusion or misoperation. In addition, the method can reduce the cost of developing and maintaining applications, and accelerate the process of platformization of vehicle applications.

[0004] In a first aspect, a method for displaying application permissions is provided, the method comprising: obtaining N application permissions associated with a target application in response to a user performing a management operation on the application permissions of the target application; and displaying M application permissions on a permission management interface of the target application based on the N application permissions and preset permission configuration rules, wherein M≤N, and the permission configuration rules include conditional parameters required for each application permission of one or more application-associated application permissions.

[0005] Through the method introduced above, the permission configuration rules are used to define information such as the application, one or more application permissions associated with the application, and the conditional parameters required for each application permission, and permission filtering conditions are set for each application permission. When the system settings of the vehicle equipment obtain the application identifier and one or more application permission information related to the target application, the conditional parameters required for each application permission associated with the application can be determined according to the permission configuration rules, and then it can be judged whether the relevant configuration parameters of the current vehicle meet the conditions. Finally, when displaying the application permissions, the useless permissions associated with the application are hidden from the user, that is, the application permissions that are not supported by the configuration parameters of the current vehicle are hidden, and only the application permissions supported by the configuration parameters of the current vehicle are displayed to the user, avoiding user confusion or misoperation.

[0006] In addition, the above display process does not require developers to configure manifest files differently according to the requirements of different vehicle models, or in other words, it does not require developers to package different APKs for different vehicle models. This process reduces the cost of developing and maintaining applications and accelerates the platformization process of vehicle applications.

[0007] In combination with the first aspect, in a possible implementation, the method also includes: obtaining configuration parameters of the vehicle, the configuration parameters including software and hardware parameters of the vehicle; and displaying M application permissions on the permission management interface of the target application based on the N application permissions and preset permission configuration rules, including: determining the M application permissions from the N application permissions based on the N application permissions, the permission configuration rules and the configuration parameters of the vehicle; and displaying the M application permissions on the permission management interface of the target application.

[0008] In an embodiment of the present application, the "permission configuration rule" may include the conditional parameters required for each application permission in the application permissions associated with one or more applications. In other words, the permission configuration rule can be understood as a database, which includes information on one or more applications introduced in S410, and includes information on functions or application permissions (privacy permissions) associated with each application in one or more applications. In addition, the permission configuration rule also records the conditional information required for each application permission. "Conditional parameters or conditional information" can be understood as the conditions that can support the function or application permission. Exemplarily, "conditional parameters" may include but are not limited to vehicle software and hardware parameters, etc.

[0009] Optionally, the vehicle configuration parameters may also include vehicle model parameters, which are associated with the vehicle's software and hardware parameters. In other words, if the vehicle model parameters are obtained, the software and hardware parameters corresponding to the vehicle model can be obtained. Exemplarily, the vehicle model parameters may be characters or codes of the vehicle model, and the specific model of the target vehicle may be obtained through the model identification. For example, the model may be a Sport Utility Vehicle (SUV), a Multi-Purpose Vehicle (MPV), a Sedan / Saloon (SED / SAL), a Sports Car (SPC), an Off-Road Vehicle (ORV), etc., and this embodiment of the present application does not limit this.

[0010] By obtaining the vehicle model parameters to determine the software and hardware parameters of the vehicle corresponding to the model, the amount of information obtained can be reduced and the processing process can be accelerated.

[0011] Optionally, the vehicle's hardware and software parameters may include hardware configuration information, software configuration information, and other information. The hardware configuration information describes the physical components or devices actually installed in the target vehicle, such as the engine type, motor power, number and model of cameras, the presence or absence of a lidar, audio playback device, microphone, and other hardware devices. The software configuration information describes information such as the software system version installed on the vehicle's onboard equipment, such as the current running software status and functional level, such as the version of the vehicle's operating system and the activation status of its functions. This embodiment of the application does not limit this.

[0012] In this application, each application permission can be filtered by the permission configuration rules. Only when the current vehicle configuration parameters meet the conditional parameters required for a certain application permission will the application permission be displayed in the permission management interface. If the current vehicle configuration parameters do not meet the conditional parameters required for a certain application permission, the application permission will not be displayed in the permission management interface. In other words, for the same application, when installed on the vehicle equipment of different vehicles, different numbers and contents of application permissions may be displayed.

[0013] In combination with the first aspect and the above-mentioned implementation method, in a possible implementation method, determining the M application permissions from the N application permissions based on the N application permissions, the permission configuration rules and the configuration parameters of the vehicle includes: determining the conditional parameters required for each of the N application permissions based on the N application permissions and the permission configuration rules; and determining, from the N application permissions, the M application permissions whose configuration parameters of the vehicle can meet the conditions based on the configuration parameters of the vehicle and the conditional parameters required for each application permission.

[0014] In combination with the first aspect and the above-mentioned implementation method, in a possible implementation method, the method further includes: in response to a user's modification operation on a first application permission among the M application permissions, not displaying the first application permission in the permission management interface of the target application, or adjusting the first application permission to be displayed in a gray non-working state or a disabled state in the permission management interface of the target application, and the first application permission is any one of the M application permissions.

[0015] In an embodiment of the present application, after the user performs operations such as modification and deletion, the "Find Charging Pile" option may no longer be displayed on the permission management interface, or the "Find Charging Pile" option may be displayed in a gray non-working state or a disabled state. The embodiment of the present application does not limit this.

[0016] Optionally, after the user performs a modification operation on the first application permission, the vehicle device may further update the permission configuration rule, and the updated permission configuration rule indicates that the first application permission is no longer displayed in the permission management interface of the target application.

[0017] In this implementation, the vehicle-mounted device can record user actions and update permission configuration rules. This process allows users to modify the display scheme of application permissions. While intelligently filtering and displaying application permissions, it also provides users with a modifiable scheme, allowing users to perform corresponding operations according to their needs, meeting the customized needs of different users.

[0018] In combination with the first aspect and the above-mentioned implementation method, in one possible implementation method, after the user performs a modification operation on the first application permission, the method further includes: updating the permission configuration rule, and the updated permission configuration rule indicates that the first application permission is no longer displayed in the permission management interface of the target application.

[0019] In combination with the first aspect and the above-mentioned implementation method, in a possible implementation method, the method further includes: determining other application permissions among the N application permissions other than the M application permissions, and displaying the other application permissions in a gray non-working state or a disabled state in the permission management interface of the target application.

[0020] Through the above process, for application permissions that are not supported by the current vehicle's software and hardware parameters, in addition to not being displayed in the permission management interface according to the method described above, they can also be displayed in a gray non-working state or a disabled state. This not only reminds users to distinguish between different types of application permissions, but also provides multiple possibilities for the display of application permissions; and supports users to adjust according to their own expectations and needs, meeting the needs of more users and improving the user experience.

[0021] In combination with the first aspect and the above-mentioned implementation method, in a possible implementation method, the method also includes: obtaining planning information of the vehicle, the planning information being used to indicate whether the software and hardware parameters of the vehicle can support being updated; when the planning information indicates that the software and hardware parameters of the vehicle can support being updated, determining the configuration parameters of the vehicle based on the updated software and hardware parameters.

[0022] It should be understood that the configuration parameters of the vehicle may be updated or iterated. The embodiment of the present application also provides a method. After obtaining the configuration information of the target vehicle, the method also needs to determine whether the target vehicle is associated with planning information, wherein the vehicle planning information includes that the hardware configuration of the target vehicle can support a new function, and the car company plans to add the new function to the target vehicle in the future.

[0023] If the planning information indicates that the vehicle's software and hardware parameters can be updated, the vehicle's configuration parameters can be determined based on the updated software and hardware parameters. In this case, if the first application permission does not meet the conditions for display on the permission management interface based on the configuration parameters before the update, and the updated configuration parameters may meet the conditions for the first application permission, then the first application permission can also be displayed on the permission management interface and displayed in a gray, non-working state or disabled state to remind the user to distinguish.

[0024] Through the above method, the application permissions displayed on the permission management interface of the vehicle device can be dynamically judged, and taking into account the possible subsequent updates and iterations of the vehicle's configuration parameters, the judgment process is more reasonable and accurate, avoiding the user's repeated operations after subsequent vehicle configuration parameters are updated.

[0025] In combination with the first aspect and the above-mentioned implementation method, in a possible implementation method, the permission configuration rule is encrypted, and the method further includes: obtaining the encrypted permission configuration rule and performing corresponding decryption processing to obtain the decrypted permission configuration rule.

[0026] Through the above process, the encryption and decryption processes of the permission configuration rules are added, which avoids the leakage of the permission configuration rules and ensures the security of the solution.

[0027] Optionally, when the target application is an energy management application, the N application permissions include at least positioning permission.

[0028] In a second aspect, a device for displaying application permissions is provided, the device comprising: an acquisition module for acquiring N application permissions associated with a target application in response to a user's management operation on the application permissions performed on the target application; a processing module for displaying M application permissions on a permission management interface of the target application based on the N application permissions and preset permission configuration rules, wherein M≤N, and the permission configuration rules include conditional parameters required for each application permission of one or more application-associated application permissions.

[0029] In combination with the second aspect, in one possible implementation, the acquisition module is also used to obtain the configuration parameters of the vehicle, wherein the configuration parameters include the software and hardware parameters of the vehicle; and the processing module is also used to determine the M application permissions from the N application permissions based on the N application permissions, the permission configuration rules and the configuration parameters of the vehicle; and display the M application permissions on the permission management interface of the target application.

[0030] In combination with the second aspect and the above-mentioned implementation method, in one possible implementation method, the processing module is also used to determine the conditional parameters required for each of the N application permissions based on the N application permissions and the permission configuration rules; and based on the configuration parameters of the vehicle and the conditional parameters required for each application permission, determine from the N application permissions the M application permissions for which the configuration parameters of the vehicle can meet the conditions.

[0031] In combination with the second aspect and the above-mentioned implementation method, in one possible implementation method, the processing module is also used to respond to the user's modification operation of the first application permission among the M application permissions, and not display the first application permission in the permission management interface of the target application, where the first application permission is any one of the M application permissions.

[0032] In combination with the second aspect and the above-mentioned implementation method, in one possible implementation method, after the user performs a modification operation on the first application permission, the processing module is also used to update the permission configuration rule, and the updated permission configuration rule indicates that the first application permission is no longer displayed in the permission management interface of the target application.

[0033] Optionally, the first application permission is displayed in a gray non-working state or a disabled state.

[0034] In combination with the second aspect and the above-mentioned implementation method, in a possible implementation method, the acquisition module is also used to obtain planning information of the vehicle, and the planning information is used to indicate whether the software and hardware parameters of the vehicle can support being updated; the processing module is also used to determine the configuration parameters of the vehicle based on the updated software and hardware parameters when the planning information indicates that the software and hardware parameters of the vehicle can support being updated.

[0035] Optionally, the permission configuration rule is encrypted, and the processing module is further configured to obtain the encrypted permission configuration rule and perform corresponding decryption processing to obtain the decrypted permission configuration rule.

[0036] Optionally, when the target application is an energy management application, the N application permissions include at least positioning permission.

[0037] In a third aspect, a vehicle is provided, comprising a memory for storing executable program code; and a processor for calling and running the executable program code from the memory, so that the vehicle executes the method in the above-mentioned first aspect or any possible implementation of the first aspect.

[0038] In a fourth aspect, a computer program product is provided, comprising: a computer program code, which, when executed on a computer, enables the computer to execute the method in the first aspect or any possible implementation of the first aspect.

[0039] In a fifth aspect, a computer-readable storage medium is provided, which stores a computer program code. When the computer program code runs on a computer, the computer executes the method in the above-mentioned first aspect or any possible implementation of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0040] Figure 1 This is a schematic diagram of a driving scenario provided in an embodiment of the present application.

[0041] Figure 2 This is a schematic diagram of the interface of a vehicle-mounted device provided in an embodiment of the present application.

[0042] Figure 3 This is a schematic diagram of an application permission authorization example provided in an embodiment of the present application.

[0043] Figure 4 This is a flowchart of a method for displaying application permissions provided by an embodiment of the present application.

[0044] Figure 5 This is a schematic diagram of an example provided in an embodiment of the present application that displays application permissions on different vehicle models.

[0045] Figure 6 This is a structural diagram of an application permission configuration device provided in an embodiment of the present application.

[0046] Figure 7 It is a structural schematic diagram of a vehicle provided in an embodiment of the present application. DETAILED DESCRIPTION

[0047] The following will clearly and thoroughly describe the technical solutions in this application in conjunction with the accompanying drawings. In the description of the embodiments of this application, unless otherwise specified, " / " means or, for example, A / B can mean A or B: "and / or" in the text is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of this application, "multiple" means two or more than two.

[0048] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features.

[0049] Figure 1 This is a driving scenario diagram provided in an embodiment of the present application. During the use of the vehicle, the user will frequently use the vehicle-mounted device 100, which can also be called a central control screen device, a vehicle-mounted device, etc.

[0050] Optionally, the vehicle-mounted device 100 has the functions of an intelligent electronic device, such as installing and running multiple applications (APPs), such as a navigation application, a settings application, a music application, etc. In addition, the vehicle-mounted device 100 can also be connected to a user's mobile phone, watch, or other portable electronic device, so that the user can make and receive calls, video calls, etc. through the vehicle-mounted device 100, which is not limited in this embodiment of the present application.

[0051] Figure 2 This is a schematic diagram of the interface of an in-vehicle device 100 provided in an embodiment of the present application.

[0052] For example, Figure 2 As shown, the user can install different applications on the vehicle device 100, for example, Figure 2 On the interface 101 shown in FIG, the navigation bar on the left displays multiple application icons such as home page, navigation, system settings, vehicle settings, etc. The user can quickly run the application by clicking the application icon in the navigation bar.

[0053] Optionally, the interface 101 may include a thumbnail window display area. For example, the upper half of the display area of ​​the interface 101 may display thumbnail windows of one or more applications frequently used by the user, such as a thumbnail window 101-1 of a system settings application and a thumbnail window 101-12 of a settings application. The user may click on any thumbnail window to trigger the display of the running interface of the application corresponding to the thumbnail window on the interface 101. This embodiment of the present application is not limited to this.

[0054] In addition, the interface 101 may also include an application display area. For example, the display area in the lower half of the interface 101 may display one or more application icons, such as one or more application icons such as system settings, communications, vehicle settings, personal center, etc. Users can also slide to view more applications. The embodiments of the present application are not limited to this.

[0055] Figure 3 This is a schematic diagram of an application permission authorization example provided in an embodiment of the present application.

[0056] For example, after the user clicks in sequence according to the path of "system setting application icon - application options - permission management options", the vehicle device 100 may display the following: Figure 3 The permission management interface 102 shown in Figure (a) of the figure is shown. On the permission management interface 102, one or more application permissions (or "privacy permissions") are displayed, such as location information, camera / camera, microphone, address book, photos and videos, documents and files, and finding charging stations. This embodiment of the application does not limit the number and type of application permissions.

[0057] like Figure 3 As shown in Figure (a), the user clicks the location information option. In response to the user's operation, the vehicle equipment can display the following Figure 3 The interface 103 shown in FIG. 1 (b) shows one or more applications associated with the location information, such as Energy management, XX music, In other words, the applications listed here can all be associated with the privacy permissions of location information, and users can choose whether to authorize the acquisition of the current vehicle's location information when using any application.

[0058] When the user executes Figure 3 As shown in Figure (b), click In response to the user's click operation, a window 103-1 may pop up on the interface 103, wherein the window 103-1 displays one or more operation options, such as an option to always allow, an option to allow only during each use, and an option to prohibit. The user can click any one of the options (such as the option to always allow) according to his or her usage needs, and click the "Confirm" control to authorize the user. The app always allows access to the vehicle's location.

[0059] It should be understood that when a user installs multiple apps in a vehicle, each app may have a different number and type of permissions, and the user can grant or deny each permission. The Android system in the car has very strict requirements for app permissions, emphasizing user control and transparency. Developers must adhere to relevant specifications during the design and development process to ensure that when users use an app, the requests for and use of permissions comply with privacy protection requirements.

[0060] According to the Android system application development specifications, when using privacy permissions (camera, location information, microphone, etc.), applications need to declare the use of the corresponding application permission names in the application manifest file. The system settings module scans and displays the permission configurations declared in each application manifest file, providing users with permission management capabilities. The number and types of permissions associated with the manifest file declaration may vary for different applications. For the same application installed on different car models, if the number and types of permissions associated with the manifest file declaration are the same, it may cause trouble for users because different models support different functions.

[0061] For example, consider the energy management app installed on a vehicle. Some models have a feature called "Find a Charging Station." This feature requires location permissions (or location information permissions). When the energy management app is installed on a vehicle without charging capabilities, the "Find a Charging Station" feature can be confusing for users. For example, even vehicles without charging support will display the aforementioned permission management item in the system settings. Furthermore, if the user disables the "Disable" option, the app may be forcibly terminated by the system, impacting the user experience.

[0062] To address the current situation, developers configure different permissions for the energy management app on different vehicle models, packaging it into different Android Package Kits (APKs) and integrating them into the system. This allows the app to be installed on different models with different permissions. However, this process increases development and maintenance costs and hinders the platform's progress.

[0063] The embodiment of the present application provides a method for displaying application permissions. The method can be applied to vehicles, specifically to Figure 1 The vehicle-mounted device 100 shown, or the method can be applied to any electronic device that can install application programs, such as mobile phones, tablets, etc., and the embodiments of the present application do not limit this.

[0064] Figure 4 This is a flowchart of a method for displaying application permissions provided by an embodiment of the present application, the method comprising the following steps:

[0065] S410 : In response to a user performing a management operation on application permissions on a target application, obtaining N application permissions associated with the target application.

[0066] Optionally, the target application may be any application installed on the vehicle device 100, such as Figures 1 to 3 Energy management applications introduced in Energy management, XX music, The embodiments of the present application do not limit this.

[0067] It should be understood that for each application, the application may be associated with one or more application permissions (privacy permissions). Table 1 is a possible example that lists multiple applications and associated application permissions. For example, as shown in Table 1, for an energy management application, assuming that the energy management application has multiple functions such as finding charging piles, power / fuel level monitoring, and background operation, each function may be associated with one or more application permissions (privacy permissions). If the user wants to normally use the charging pile search function of the energy management application, it is necessary to authorize the energy management application to have the permission to obtain the current location information of the vehicle device. If the user wants to normally use the background operation function of the energy management application, it is necessary to authorize the energy management application to have the permission to display the floating window. I will not go into details here.

[0068] It should also be understood that Table 1 is only a possible example. In actual applications, more other applications may be installed on the vehicle device, and each application may be associated with more or fewer functional options, or each application may be associated with more or fewer privacy permissions. The embodiments of this application do not limit this.

[0069] Table 1

[0070]

[0071] Optionally, the management operation on the application permissions performed by the user on the target application may be one operation or multiple consecutive operations.

[0072] For example, the user can follow the path of "System Settings Application Icon - Application Options - Permission Management Options" and perform multiple click operations in sequence, and then the following will be displayed: Figure 3 The permission management interface 102 is shown in FIG. (a) in FIG. Alternatively, as technology evolves, there may be shortcut operations, where a user clicks a shortcut function control to display the permission management interface 102. The embodiment of the present application does not limit the steps of the user's management operations for application permissions.

[0073] In one possible scenario, the timing for obtaining the N application permissions associated with the target application may be actively triggered by the user. For example, the user described above performs one or more operations, triggering the vehicle device 100 to display the permission management interface 102, thereby obtaining the N application permissions associated with the target application; or, after the target application is installed on the vehicle device 100, the vehicle device 100 can obtain the N application permissions associated with the target application, which can be directly used as known information in the process of user authorization of application permissions. The embodiment of the present application does not limit the timing for obtaining the N application permissions associated with each application.

[0074] Specifically, when installing a target application on the vehicle device 100 , a manifest file related to the target application may be obtained. The manifest file may include the application name of the target application and one or more application permission names associated with the target application.

[0075] S420: Display M application permissions on the permission management interface of the target application according to the N application permissions and a preset permission configuration rule, where M≤N, and M and N are positive integers.

[0076] It should be understood that in an embodiment of the present application, the "permission configuration rule" may include the conditional parameters required for each application permission in the application permissions associated with one or more applications. In other words, the permission configuration rule can be understood as a database, which includes information on one or more applications introduced in S410, and includes information on functions or application permissions (privacy permissions) associated with each application in one or more applications. In addition, the permission configuration rule also records relevant information on the conditional parameters required for each application permission. "Conditional parameters or conditional information" can be understood as conditions that can support the function or application permission. Exemplarily, "conditional parameters" may include vehicle hardware and software parameters, etc. For details, please refer to the subsequent introduction to vehicle parameters.

[0077] Table 2 shows an example of information in a permission configuration rule provided by an embodiment of the present application. For example, as shown in Table 2, the permission configuration rule may include information such as the application name, one or more application permissions, and conditional parameters of the application permissions.

[0078] Table 2

[0079]

[0080]

[0081] The above describes the content included in the permission configuration rules. The following describes a possible configuration method for the permission configuration rules. For example, the possible configuration content of the permission configuration rules is as follows, which at least includes the following information:

[0082] (1) Application package name (application name)

[0083] The application configures the meta-data tag in the project's AndroidMainifest.xml file, where the application name can also be called the application package name. For example, taking the energy management application as an example, the application package name can be recorded as "com.gwm.app.energy".

[0084] (2) Application permission name (permission name)

[0085] The application package name is associated with one or more permission names, denoted as "values." Each "value" is associated with one or more conditional parameters, denoted as "GwmFeature." For example, taking the location information permission of an energy management application as an example, the conditional parameter corresponding to the location information permission (value) can be denoted as "android.permission.ACCESS_COARSE_LOCATION," i.e., android.permission.ACCESS_COARSE_LOCATION = GwmFeature.

[0086] The GwmFeature and value values ​​can be separated by ":", and multiple value values ​​can be separated by ",". For example: GWM_FEATURE_NOTSUPPORT_LOCATION1 means that positioning condition 1 is not supported; GWM_FEATURE_NOTSUPPORT_LOCATION2 means that positioning condition 2 is not supported; GWM_FEATURE_NOTSUPPORT_ENERGY means that the energy management display application permission is not supported.

[0087] It's important to note that when an application permission involves multiple GwmFeatures, logical relationships can be used to represent them. For example, "&" represents "and" and "||" represents "or." For multiple application permissions, separate each one with "#." This allows you to determine whether the current vehicle supports a specific application permission based on the general configuration rules.

[0088] For example, taking the energy management application ("com.gwm.app.energy") as an example, when configuring on a vehicle without charging requirements, the relevant configuration content in the permission configuration rule can be as follows:

[0089]

[0090] The above configuration content means "not supporting positioning condition 1 and not supporting positioning condition 2 or not supporting energy management display permission management", which will not be repeated here.

[0091] In one possible implementation, the vehicle device 100 can obtain the configuration parameters of the vehicle, which include the software and hardware parameters of the vehicle; and, based on N application permissions, the permission configuration rules and the configuration parameters of the vehicle, determine the M application permissions from the N application permissions, and display the M application permissions in the permission management interface of the target application.

[0092] Specifically, the vehicle device 100 can determine the conditional parameters required for each of the N application permissions based on the N application permissions and the permission configuration rules; based on the configuration parameters of the vehicle and the conditional parameters required for each application permission, determine the M application permissions whose configuration parameters of the vehicle can meet the conditions from the N application permissions, and display the M application permissions in the permission management interface of the target application.

[0093] Optionally, the vehicle configuration parameters may also include vehicle model parameters, which are associated with the vehicle's software and hardware parameters. In other words, if the vehicle model parameters are obtained, the software and hardware parameters corresponding to the vehicle model can be obtained. Exemplarily, the vehicle model parameters may be characters or codes of the vehicle model, and the specific model of the target vehicle may be obtained through the model identification. For example, the model may be a Sport Utility Vehicle (SUV), a Multi-Purpose Vehicle (MPV), a Sedan / Saloon (SED / SAL), a Sports Car (SPC), an Off-Road Vehicle (ORV), etc., and this embodiment of the present application does not limit this.

[0094] Optionally, the vehicle's hardware and software parameters may include hardware configuration information, software configuration information, and other information. The hardware configuration information describes the physical components or devices actually installed in the target vehicle, such as the engine type, motor power, number and model of cameras, the presence or absence of a lidar, audio playback device, microphone, and other hardware devices. The software configuration information describes information such as the software system version installed on the vehicle's onboard equipment, such as the current running software status and functional level, such as the version of the vehicle's operating system and the activation status of its functions. This embodiment of the application does not limit this.

[0095] By obtaining the vehicle model parameters to determine the software and hardware parameters of the vehicle corresponding to the model, the amount of information obtained can be reduced and the processing process can be accelerated.

[0096] In S420, each application permission can be filtered according to the permission configuration rules. Only when the current vehicle configuration parameters meet the conditional parameters required for a certain application permission will the application permission be displayed in the permission management interface. If the current vehicle configuration parameters do not meet the conditional parameters required for a certain application permission, the application permission will not be displayed in the permission management interface. In other words, for the same application, when installed on the vehicle equipment of different vehicles, different numbers and contents of application permissions may be displayed.

[0097] Figure 5This is a schematic diagram of an example of displaying application permissions on different car models provided by an embodiment of the present application. Figure 5 Figures (a) and (b) illustrate different types of vehicle-mounted devices. Assume that Figure (a) corresponds to the permission management interface for the energy management application on the vehicle-mounted device of electric vehicle A, and Figure (b) corresponds to the permission management interface for the energy management application on the vehicle-mounted device of gasoline vehicle B. For the same energy management application, when installed on the vehicle-mounted device of electric vehicle A, window 104-1 of the energy management application permission interface can display the user's authorized permissions for location information, microphone, charging station search, and battery monitoring in a list format. It can also display the user's unauthorized permissions for installing other applications within the application and for floating windows.

[0098] When the energy management app is installed on the vehicle's head unit (Vehicle B) and the user hasn't set authorized app permissions, window 105-1 of the Energy Management App Permissions interface displays a list of permissions for location information, microphone, finding a charging station, battery monitoring, installing other apps within the app, and a floating window. The user can click on any permission to configure the authorization time limit for each permission, which is not detailed here.

[0099] contrast Figure 5 In Figures (a) and (b), for electric car A, the energy management application can display the application permission for finding charging piles for the user, and supports the user to click on the application permission to authorize or prohibit it; for gasoline car B, based on the vehicle configuration parameters and the conditional parameters required for each application permission in the permission configuration rules, the application permission for finding charging piles is filtered, that is, the application permission for finding charging piles can be filtered on the application permission interface of the energy management application, that is, the application permission for finding charging piles is not displayed, avoiding confusion for users.

[0100] Optionally, for oil truck B, in addition to Figure 5 The display method shown in Figure (b) does not display the application permissions for finding charging piles, and can also be Figure 5 The display method is the same as that shown in Figure (a) above, and the app permission for finding charging stations is grayed out or disabled. In other words, app permissions that are not supported by the current vehicle model and the vehicle's software and hardware parameters can also be displayed to the user in a grayed-out or disabled state, distinguishing them from the normal working state of other supported app permissions to avoid user confusion. Even if the user accidentally clicks on the app permission for finding charging stations, the interface will not change.

[0101] Through the method introduced above, the permission configuration rules are used to define information such as the application, one or more application permissions associated with the application, and the conditional parameters required for each application permission, and permission filtering conditions are set for each application permission. When the system settings of the vehicle equipment obtain the application identifier and one or more application permission information related to the target application, the conditional parameters required for each application permission associated with the application can be determined according to the permission configuration rules, and then it can be judged whether the relevant configuration parameters of the current vehicle meet the conditions. Finally, when displaying the application permissions, the useless permissions associated with the application are hidden from the user, that is, the application permissions that are not supported by the configuration parameters of the current vehicle are hidden, and only the application permissions supported by the configuration parameters of the current vehicle are displayed to the user, avoiding user confusion or misoperation.

[0102] In addition, the above display process does not require developers to configure manifest files differently according to the requirements of different vehicle models, or in other words, it does not require developers to package different APKs for different vehicle models. This process reduces the cost of developing and maintaining applications and accelerates the platformization process of vehicle applications.

[0103] In another possible implementation, the permission configuration rule is encrypted, and the vehicle-mounted device can obtain the encrypted permission configuration rule and perform corresponding decryption processing to obtain the decrypted permission configuration rule.

[0104] It should be understood that in order to avoid the leakage of permission configuration rules, the value in the configured meta-data can be encrypted and applied to the system settings, and the encrypted result can be configured to the value.

[0105] Optionally, the encryption algorithm may be a BlowFish algorithm, which is not limited in the present embodiment. For example, taking energy management application as an example, the encryption result of the above-described example is:

[0106]

[0107] When the system settings obtain the meta-data android:value configured in the energy management application, it can perform the corresponding decryption processing and then, according to the aforementioned process and the permission configuration rules, determine the application permissions that the energy management application of the current vehicle model needs to display to the user.

[0108] Through the above process, the encryption and decryption processes of the permission configuration rules are added, which avoids the leakage of the permission configuration rules and ensures the security of the solution.

[0109] In another possible implementation, the vehicle-mounted device may respond to a user's modification operation on the first application permission among the M application permissions by not displaying the first application permission in the permission management interface of the target application, or by adjusting the first application permission to be displayed in a gray non-working state or a disabled state in the permission management interface of the target application, where the first application permission is any one of the M application permissions.

[0110] For example, in Figure 5 In the interface 104 shown in Figure (a), the application permission for electric vehicle A to support the search for charging stations in the energy management application is displayed in window 104-1. The user may not need the search for charging stations function, for example, if the user has a fixed charging location and rarely needs to charge elsewhere. In this scenario, the user is supported to modify the display interface of the current energy management application. For example, the user can click or long press the "Search for Charging Station" option. In response to the user's operation, one or more operation controls such as modification and deletion may pop up, thereby supporting the user to perform corresponding operations according to personal needs.

[0111] After the user performs operations such as modification and deletion, the "Find Charging Pile" option may no longer be displayed on the permission management interface, or the "Find Charging Pile" option may be displayed in a gray non-working state or disabled state. This embodiment of the present application does not limit this.

[0112] Optionally, after the user performs a modification operation on the first application permission, the vehicle device may further update the permission configuration rule, and the updated permission configuration rule indicates that the first application permission is no longer displayed in the permission management interface of the target application.

[0113] In this implementation, the vehicle-mounted device can record user actions and update permission configuration rules. This process allows users to modify the display scheme of application permissions. While intelligently filtering and displaying application permissions, it also provides users with a modifiable scheme, allowing users to perform corresponding operations according to their needs, meeting the customized needs of different users.

[0114] In another possible implementation, after determining that the current vehicle's hardware and software parameters can support the display of M application permissions according to the process described above, the vehicle-mounted device can also determine other application permissions among the N application permissions in addition to the M application permissions, and display the other application permissions in a gray, non-working state or disabled state in the permission management interface of the target application.

[0115] For example, in Figure 5In the interface 105 shown in Figure (b), although gasoline vehicle B does not support the function of finding charging piles in the energy management application, it can also display the application permission of finding charging piles in window 105-1. The application permission of finding charging piles can be displayed in a grayed-out or disabled state, which is not limited in this embodiment of the application.

[0116] Through the above process, for application permissions that are not supported by the current vehicle's software and hardware parameters, in addition to not being displayed in the permission management interface according to the method described above, they can also be displayed in a gray non-working state or a disabled state. This not only reminds users to distinguish between different types of application permissions, but also provides multiple possibilities for the display of application permissions; and supports users to adjust according to their own expectations and needs, meeting the needs of more users and improving the user experience.

[0117] In another possible implementation, the vehicle-mounted device can also obtain planning information of the vehicle, where the planning information is used to indicate whether the software and hardware parameters of the vehicle can support being updated; when the planning information indicates that the software and hardware parameters of the vehicle can support being updated, the configuration parameters of the vehicle are determined based on the updated software and hardware parameters.

[0118] It should be understood that the configuration parameters of the vehicle may be updated or iterated. The embodiment of the present application also provides a method. After obtaining the configuration information of the target vehicle, the method also needs to determine whether the target vehicle is associated with planning information, wherein the vehicle planning information includes that the hardware configuration of the target vehicle can support a new function, and the car company plans to add the new function to the target vehicle in the future.

[0119] For example, if the vehicle's planning information includes the function of recording videos and uploading them to social media or cloud backup, the existing 360-degree panoramic imaging system can record the environment during the vehicle's driving. If the application permission of the recording and uploading videos to social media or cloud is turned on, the 360-degree panoramic imaging system can record the environment video during the vehicle's driving and transmit the recorded environment video to social media or cloud for backup; the vehicle's planning information includes an air purification function, and the existing vehicle air-conditioning system has a built-in PM2.5 filter that supports air purification. If the application permission of the air purification function is turned on, the air in the vehicle can be purified through the built-in PM2.5 filter of the vehicle air-conditioning system.

[0120] Table 3 shows an example of a possible mapping relationship between preset vehicle models and preset planning information provided in an embodiment of the present application. Vehicle model A and vehicle model B can be associated with different or the same planning information.

[0121] Table 3

[0122] Preset car models Preset planning information Model A Planning Information 1 Model B Planning Information 2 Model C none …… ……

[0123] Optionally, if the planning information indicates that the vehicle's software and hardware parameters can be updated, the vehicle's configuration parameters can be determined based on the updated software and hardware parameters. In this case, if the first application permission does not meet the conditions for display on the permission management interface based on the pre-update configuration parameters, and the updated configuration parameters may meet the conditions for the first application permission, then the first application permission can also be displayed on the permission management interface and displayed in a gray, non-working state or disabled state to remind the user to distinguish.

[0124] The above method can dynamically determine the application permissions displayed on the permission management interface of the vehicle equipment, and take into account the possible subsequent updates and iterations of the vehicle's configuration parameters. The judgment process is more reasonable and accurate, avoiding the user's repeated operations after the subsequent vehicle configuration parameters are updated.

[0125] In summary, through the permission configuration rules, the application, one or more application permissions associated with the application, the conditional parameters required for each application permission and other information are defined, and permission filtering conditions are set for each application permission. When the system settings of the vehicle equipment obtain the application identification and one or more application permission information related to the target application, the conditional parameters required for each application permission associated with the application can be determined according to the permission configuration rules, and then it can be judged whether the relevant configuration parameters of the current vehicle meet the conditions. Finally, when displaying the application permissions, the useless permissions associated with the application are hidden from the user, that is, the application permissions that are not supported by the configuration parameters of the current vehicle are hidden, and only the application permissions supported by the configuration parameters of the current vehicle are displayed to the user, so as to avoid user confusion or misoperation.

[0126] In addition, the above display process does not require developers to configure manifest files differently according to the requirements of different vehicle models, or in other words, it does not require developers to package different APKs for different vehicle models. This process reduces the cost of developing and maintaining applications and accelerates the platformization process of vehicle applications.

[0127] The aforementioned combined Figures 1 to 5 This paper introduces the method for displaying application permissions provided by the embodiment of the present application. Figure 6 and Figure 7 The present invention provides a method and apparatus for enabling a user to execute and display application permissions, as provided in an embodiment of the present application.

[0128] Figure 6 This is a schematic diagram of the structure of an application permission configuration device provided by an embodiment of the present application. Figure 6 As shown, the apparatus 600 includes:

[0129] An acquisition module 610 is configured to acquire N application permissions associated with a target application in response to a user performing a management operation on application permissions on the target application;

[0130] Processing module 620 is used to display M application permissions on the permission management interface of the target application based on the N application permissions and preset permission configuration rules, where M≤N, and the permission configuration rules include conditional parameters required for each application permission in the application permissions associated with one or more applications.

[0131] In a possible implementation, the acquisition module 610 is further configured to acquire configuration parameters of the vehicle, where the configuration parameters include software and hardware parameters of the vehicle;

[0132] Furthermore, the processing module 620 is further configured to determine the M application permissions from the N application permissions based on the N application permissions, the permission configuration rules, and the configuration parameters of the vehicle; and display the M application permissions on the permission management interface of the target application.

[0133] In another possible implementation, the processing module 620 is further used to determine the conditional parameters required for each of the N application permissions based on the N application permissions and the permission configuration rules; and to determine, from the N application permissions, the M application permissions for which the vehicle configuration parameters can meet the conditions based on the vehicle configuration parameters and the conditional parameters required for each application permission.

[0134] In another possible implementation, the processing module 620 is further used to, in response to a user's modification operation on a first application permission among the M application permissions, not display the first application permission in the permission management interface of the target application, or to adjust the first application permission to be displayed in a gray non-working state or a disabled state in the permission management interface of the target application, where the first application permission is any one of the M application permissions.

[0135] In another possible implementation, after the user performs a modification operation on the first application permission, the processing module 620 is also used to update the permission configuration rule, and the updated permission configuration rule indicates that the first application permission is no longer displayed in the permission management interface of the target application.

[0136] Optionally, the first application permission is displayed in a gray non-working state or a disabled state.

[0137] In another possible implementation, the acquisition module 610 is further configured to acquire planning information of the vehicle, where the planning information is used to indicate whether software and hardware parameters of the vehicle can be updated.

[0138] The processing module 620 is further configured to determine the configuration parameters of the vehicle based on the updated software and hardware parameters when the planning information indicates that the software and hardware parameters of the vehicle can be updated.

[0139] Optionally, the permission configuration rule is encrypted, and the processing module 620 is further configured to obtain the encrypted permission configuration rule and perform corresponding decryption processing to obtain the decrypted permission configuration rule.

[0140] In another possible implementation, the processing module 620 is further used to determine other application permissions among the N application permissions except the M application permissions, and display the other application permissions in a gray non-working state or disabled state in the permission management interface of the target application.

[0141] Optionally, when the target application is an energy management application, the N application permissions include at least positioning permission.

[0142] It should be noted that the application permission configuration device provided in the above embodiment only uses the division of the above-mentioned functional modules as an example when executing the application permission configuration method. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0143] In addition, the device 600 provided in the above embodiment and the embodiment of the application permission configuration method belong to the same concept. Therefore, for details not disclosed in the device embodiment of this specification, please refer to the embodiment of the application permission configuration method above in this specification, and no further details will be given here.

[0144] Figure 7 It is a structural schematic diagram of a vehicle provided in an embodiment of the present application.

[0145] For example, Figure 7 As shown, the vehicle 700 includes: a memory 701 and a processor 702, wherein the memory 701 stores an executable program code 7011, and the processor 702 is used to call and execute the executable program code 7011 to perform an application permission configuration method.

[0146] In addition, an embodiment of the present application also protects a device, which may include a memory and a processor, wherein the memory stores executable program code, and the processor is used to call and execute the executable program code to perform an application permission configuration method provided by an embodiment of the present application.

[0147] In this embodiment, the device can be divided into functional modules based on the above-described method examples. For example, each functional module can be mapped to a specific functional module, or two or more functions can be integrated into a single processing module. The integrated module can be implemented in hardware. It should be noted that the module division in this embodiment is illustrative and represents only a logical functional division. In actual implementation, other division methods may be used.

[0148] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0149] It should be understood that the apparatus provided in this embodiment is used to execute the above-mentioned method for displaying application permissions, and thus can achieve the same effect as the above-mentioned implementation method.

[0150] In the case of an integrated unit, the device may include a processing module and a storage module. When the device is used in a vehicle, the processing module may be used to control and manage the vehicle's movements, while the storage module may be used to support the vehicle's execution of relevant program codes.

[0151] The processing module may be a processor or controller that implements or executes the various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a digital signal processing system (DSP) and a microprocessor, and the storage module may be a memory.

[0152] In addition, the device provided in the embodiments of the present application can specifically be a chip, component or module, and the chip may include a connected processor and memory; wherein the memory is used to store instructions, and when the processor calls and executes the instructions, the chip can execute an application permission configuration method provided in the above embodiment.

[0153] This embodiment also provides a computer-readable storage medium, which stores computer program code. When the computer program code runs on a computer, the computer executes the above-mentioned related method steps to implement a method for displaying application permissions provided by the above embodiment.

[0154] This embodiment further provides a computer program product. When the computer program product is run on a computer, it enables the computer to execute the above-mentioned related steps to implement a method for displaying application permissions provided by the above embodiment.

[0155] Among them, the device, computer-readable storage medium, computer program product or chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0156] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0157] In the embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0158] The above content is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection of the claims.

Claims

1. A method for displaying application permissions, characterized in that: Applied to a vehicle, the method comprises: In response to an application management operation performed by a user on a target application, obtaining N application permissions associated with the target application; According to the N application permissions and preset permission configuration rules, M application permissions are displayed on the permission management interface of the target application, where M≤N, and the permission configuration rules include conditional parameters required for each application permission in the application permissions associated with one or more applications.

2. The method according to claim 1, characterized in that The method further comprises: Acquiring configuration parameters of the vehicle, wherein the configuration parameters include software and hardware parameters of the vehicle; Furthermore, displaying M application permissions on the permission management interface of the target application according to the N application permissions and the preset permission configuration rules includes: Determining the M application permissions from the N application permissions according to the N application permissions, the permission configuration rule, and the configuration parameters of the vehicle; M application permissions are displayed on the permission management interface of the target application.

3. The method according to claim 2, characterized in that The determining the M application permissions from the N application permissions based on the N application permissions, the permission configuration rule, and the configuration parameters of the vehicle includes: Determining, based on the N application permissions and the permission configuration rule, conditional parameters required for each of the N application permissions; According to the configuration parameters of the vehicle and the conditional parameters required by each application permission, the M application permissions for which the configuration parameters of the vehicle can satisfy the conditions are determined from the N application permissions.

4. The method according to claim 3, characterized in that The method further comprises: In response to a user's modification operation on a first application permission among the M application permissions, the first application permission is not displayed in the permission management interface of the target application, or the first application permission is adjusted to be displayed in a gray non-working state or a disabled state in the permission management interface of the target application, and the first application permission is any one of the M application permissions.

5. The method according to claim 4, characterized in that After the user performs a modification operation on the first application permission, the method further includes: The permission configuration rule is updated, where the updated permission configuration rule indicates that the first application permission is no longer displayed on the permission management interface of the target application.

6. The method according to any one of claims 2 to 5, characterized in that The method further comprises: Acquiring planning information of the vehicle, where the planning information is used to indicate whether software and hardware parameters of the vehicle can support being updated; When the planning information indicates that the software and hardware parameters of the vehicle can be updated, the configuration parameters of the vehicle are determined based on the updated software and hardware parameters.

7. The method according to any one of claims 1 to 5, characterized in that The method further comprises: Determine other application permissions other than the M application permissions among the N application permissions, and display the other application permissions in a gray, non-working state or a disabled state in a permission management interface of the target application.

8. The method according to any one of claims 1 to 5, characterized in that The permission configuration rule is encrypted, and the method further includes: The encrypted permission configuration rule is obtained, and corresponding decryption processing is performed to obtain the decrypted permission configuration rule.

9. A vehicle, characterized in that: The vehicle comprises: a memory for storing executable program code; A processor is configured to call and run the executable program code from the memory, so that the vehicle executes the method for displaying application permissions as described in any one of claims 1 to 8.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed, the method for displaying application permissions according to any one of claims 1 to 8 is implemented.

Images