Application permission configuration method and device, electronic equipment and computer readable storage medium

By obtaining and integrating permission management files in the Android system and configuring runtime permissions for system-level applications, the problems of low user experience and high code intrusion on Android cars are solved, and the default authorization and version adaptability of system-level applications are achieved.

CN118965394APending Publication Date: 2024-11-15CHONGQING SELIS PHOENIX INTELLIGENT INNOVATION TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411058854.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-02
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

On Android system cars, system-level applications require default authorization of runtime permissions, but the lack of setting interfaces in native Aosp code, resulting in a decline in user experience, and the hard-code modification method is highly invasive to native code and is not suitable for Android version iteration.

Method used

By obtaining permission management files, integrating them into the target directory of the Android system, reading permission management files to configure application permissions, including whitelists, path lists and application store lists, realizing default authorization for system-level applications, and running independently does not affect native code. Adapt to version iteration.

Benefits of technology

Improve user experience, avoid users confirming authorization after booting, decoupling native code, adapting to changes in Android versions, and implementing default authorization for system-level applications.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118965394A_ABST
    Figure CN118965394A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of computers, and discloses an application permission configuration method and device, electronic equipment and a computer readable storage medium, and the method comprises the following steps: obtaining a permission management file; wherein the authority management file comprises an authority configuration rule aiming at an application in the Android system; integrating the authority management file into a target directory in the Android system; wherein the target directory is a directory used for storing the configuration file in the Android system; and when the Android system is started, reading the permission management file under the target directory, and performing permission configuration on the application in the Android system based on the permission configuration rule in the permission management file. The embodiment of the invention is used for realizing default authorization of the application.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and specifically to an application permission configuration method, device, electronic device, and computer-readable storage medium. Background Art

[0002] When developing on an Android (a mobile operating system) car computer, the system-level application that needs to be customized and developed by the manufacturer is an application that ensures the normal operation of the system business. Therefore, the system-level application should be set to the default authorization runtime permission, rather than a pop-up box after startup asking the user to click a confirmation button to authorize, which reduces the user experience.

[0003] However, in the Android native Aosp (open source project of the Android operating system) code, there is no corresponding interface to set the default authorization runtime permission for the custom-developed system-level application. Some solutions will modify the native code and filter the application packages of system-level applications that require default authorization through hard-coding (defining a whitelist in the code). However, this method is highly invasive to the native code, and when the Android version is iterated, the modified code part cannot be transplanted and inserted into the new version due to changes in the native Aosp code structure, resulting in the inability of the iterated Android to grant default authorization to system-level applications. Summary of the invention

[0004] In view of the above problems, embodiments of the present application provide an application permission configuration method, device, electronic device and computer-readable storage medium for implementing default authorization of applications.

[0005] According to one aspect of an embodiment of the present application, there is provided an application permission configuration method, comprising: obtaining a permission management file; wherein the permission management file comprises permission configuration rules for applications in an Android system; integrating the permission management file into a target directory in the Android system; wherein the target directory is a directory for storing configuration files in the Android system; when the Android system is started, reading the permission management file in the target directory, and performing permission configuration for applications in the Android system based on the permission configuration rules in the permission management file.

[0006] In an optional manner, the permission management file also includes a whitelist list, the whitelist list includes a first application in the Android system, and the permission configuration rules include a first permission configuration rule for the first application; the permission configuration of the application in the Android system based on the permission configuration rules in the permission management file further includes: based on the first application in the whitelist list, obtaining the corresponding first permission configuration rule in the permission configuration rules; and configuring permissions for the first application based on the first permission configuration rule.

[0007] In an optional manner, there are multiple permission configuration rules, and there is a priority order between the multiple permission configuration rules. The applications in the Android system include a second application; the permission configuration of the applications in the Android system based on the permission configuration rules in the permission management file further includes: obtaining at least two second permission configuration rules that match the second application in the multiple permission configuration rules; determining a target second permission configuration rule with a high priority among the at least two second permission configuration rules based on the priority order; and performing permission configuration on the second application based on the target second permission configuration rule.

[0008] In an optional manner, the permission management file also includes a path list, the path list includes a target installation path in the Android system, and the permission configuration rules include a third permission configuration rule for the application under the target installation path; the permission configuration of the application in the Android system based on the permission configuration rules in the permission management file further includes: determining a corresponding third permission configuration rule in the permission configuration rules based on the target installation path; and configuring permissions for the application under the target installation path based on the third permission configuration rule.

[0009] In an optional manner, the permission management file also includes an application store list, the application store list includes a target application store in the Android system, and the permission configuration rules include a fourth permission configuration rule for applications downloaded from the target application store; the permission configuration of applications in the Android system based on the permission configuration rules in the permission management file further includes: determining a corresponding fourth permission configuration rule in the permission configuration rules based on the target application store; and performing permission configuration on applications downloaded from the target application store based on the fourth permission configuration rule.

[0010] In an optional manner, when the Android system is started, the permission management file under the target directory is read, and permission configuration is performed on the application in the Android system based on the permission configuration rules in the permission management file, further including: in response to the startup of the Android system, the permission management file under the target directory is read based on the execution logic preset in the permission management service, and permission configuration is performed on the application in the Android system based on the permission configuration rules in the permission management file; wherein the permission management service inherits the system service for permission management in the Android system, and the execution logic preset in the permission management service represents reading the permission management file under the target directory, and permission configuration is performed on the application in the Android system based on the permission configuration rules in the permission management file.

[0011] In an optional manner, after configuring the permissions of the application in the Android system based on the permission configuration rules in the permission management file, the method further includes: when the Android system is started, setting a prohibition update instruction, the prohibition update instruction indicates that the permission management file is not supported to be updated; before the Android system is started, the permission management file is updated to obtain an updated permission management file, so that after the Android system is started, the permission configuration of the application in the Android system is performed based on the permission configuration rules in the updated permission management file. Obtain the query index of the business request data; call the data access interface, and search the database for the data corresponding to the query index through the data access interface.

[0012] According to another aspect of an embodiment of the present application, an application permission configuration device is provided, including: a permission management file acquisition module, used to obtain a permission management file; wherein the permission management file includes permission configuration rules for applications in an Android system; a file processing module, used to integrate the permission management file into a target directory in the Android system; wherein the target directory is a directory for storing configuration files in the Android system; and a permission configuration module, used to read the permission management file in the target directory when the Android system is started, and perform permission configuration for the applications in the Android system based on the permission configuration rules in the permission management file.

[0013] According to one aspect of an embodiment of the present application, an electronic device is provided, including: a controller; and a memory for storing one or more programs, which, when the one or more programs are executed by the controller, execute the above-mentioned application permission configuration method.

[0014] According to one aspect of an embodiment of the present application, a computer-readable storage medium is further provided, on which computer-readable instructions are stored. When the computer-readable instructions are executed by a processor of a computer, the computer executes the above-mentioned application permission configuration method.

[0015] According to one aspect of the embodiments of the present application, a computer program product or a computer program is also provided, the computer program product or the computer program includes a computer instruction, and the computer instruction is stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the above-mentioned application permission configuration method.

[0016] In the embodiment of the present application, by writing a permission management file, and writing the permission management file into a target directory for storing configuration files in the Android system, when the Android system is started, the permission management file in the target directory can be directly read to configure permissions for the application. This process does not require the user to click a confirmation button in a pop-up box to authorize after booting up the system, thereby improving the user experience. The system runs independently in the target directory in the Android system, decoupling the native code and having no impact on each other, thereby being able to adapt to version iterations of the Android system.

[0017] The above description is only an overview of the technical solution of the embodiment of the present application. In order to more clearly understand the technical means of the embodiment of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the embodiment of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 It is an implementation environment diagram shown in an exemplary embodiment of the present application.

[0020] Figure 2 It is a flowchart of an application permission configuration method shown in an exemplary embodiment of the present application.

[0021] Figure 3 It is a flowchart of an application permission configuration method shown in another exemplary embodiment of the present application.

[0022] Figure 4 It is a structural diagram of an application permission configuration device shown in an exemplary embodiment of the present application.

[0023] Figure 5 It is a structural diagram of a computer system of an electronic device shown in an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0024] Here, exemplary embodiments will be described in detail, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.

[0025] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0026] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0027] The term "multiple" as used in this application refers to two or more than two. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the related objects are in an "or" relationship.

[0028] Please refer to Figure 1 , Figure 1 This is an implementation scenario diagram proposed in this embodiment, which includes a terminal and a server, and the terminal and the server are in communication connection. It can be understood that Figure 1 The number of terminals and servers in the embodiment is exemplary. In other embodiments, other numbers of terminals and servers may be included.

[0029] In one embodiment, the terminal can accept a permission management file and send the permission management file to the server, which obtains the permission management file; the permission management file includes permission configuration rules for applications in the Android system; the permission management file is integrated into a target directory in the Android system; wherein the target directory is a directory for storing configuration files in the Android system; when the Android system is started, the permission management file in the target directory is read, and permissions are configured for applications in the Android system based on the permission configuration rules in the permission management file.

[0030] In some embodiments, the terminal can be a visual device such as a mobile phone, a car terminal, a television, a tablet, a computer, etc.; the server side can be a server cluster, a cloud server, or other device with data processing capabilities, and the Android system is partially or completely loaded on the terminal and / or the server side.

[0031] Understandably, Figure 1 Although an implementation scenario diagram is shown, it is for illustrative purposes only. In other embodiments, there may be other implementation scenarios, which are not specifically limited here.

[0032] One aspect of the present application provides a method for configuring application permissions. Figure 2 , Figure 2 is a flowchart of an application permission configuration method shown in an exemplary embodiment of the present application. The application permission configuration method can be applied to Figure 1 The server side in the embodiment includes at least S210 to S230, which are described in detail as follows:

[0033] S210: Acquire a permission management file; wherein the permission management file includes permission configuration rules for applications in the Android system.

[0034] The application permission configuration method proposed in this embodiment is used to configure the permissions of applications in the Android system. The permission management file includes permission configuration rules. It can be understood that the number of the permission configuration rules is one or more, which can be permission configuration rules for a specific application or permission configuration rules for a certain type of application.

[0035] It should be understood that the permission configuration rules may include permission configuration rules for all or part of the applications in the Android system. When the Android system is started, for some applications written in the permission management file, permission configuration is performed according to the permission configuration rules corresponding to the permission management file, while for some applications not written in the permission management file, permission configuration is performed according to the permission management method of the native code in the Android system.

[0036] S220: Integrate the permission management file into a target directory in the Android system; wherein the target directory is a directory for storing configuration files in the Android system.

[0037] In this embodiment, after configuring the permission management file, the permission management file is integrated into the target directory in the Android system. The target directory is a directory for storing configuration files in the Android system, so that other programs have no access to the files in the target directory.

[0038] In this embodiment, the target directory is used to store configuration files and data files provided by the vendor. In AOSP, the target directory is used to store some customized configuration information, so that the permission management file is integrated into the target directory of the Android system, so that the file is run when the subsequent Android system is started.

[0039] In one embodiment, the format of the permission management file is json (lightweight data exchange format). For example, if the permission management file is named config.json and the target directory in the Android system is vendor / etc / data / , config.json can be placed in the target directory through relevant instructions. Thus, the integration path of the permission management file is recorded as vendor / etc / data / config.json.

[0040] In one embodiment, the rights management file is stored in a certain path, and then the rights management file in the path is copied to the target directory through instructions.

[0041] For example, through the instruction "PRODUCT_COPY_FILES+=\" (an instruction in the Android.mk file, which is used to define the list of files that need to be copied to the compilation output. Android.mk is used to describe how to compile and build the relevant components and files of the device. Each project device can have one or more Android.mk files), the permission management file in a certain path is copied to the target directory.

[0042] If a path is set to device / qcom / msmnile_gvmq / xxx / , the copy instruction can be:

[0043] PRODUCT_COPY_FILES+=\

[0044] device / qcom / msmnile_gvmq / xxx / permission / permission_config.json:$(TARGET_COPY_OUT_VENDOR) / etc / data / permission_config.json

[0045] Among them, $(TARGET_COPY_OUT_VENDOR) is a variable that represents the vendor directory of the target output.

[0046] In this way, the configured permission management file can be compiled into the Android system image as device content, with excellent stability.

[0047] S230: When the Android system is started, the permission management file in the target directory is read, and permission configuration is performed on the application in the Android system based on the permission configuration rules in the permission management file.

[0048] In this embodiment, when the Android system is started, the permission management file in the target directory can be read to configure permissions for applications in the Android system. Through this permission management file, some system-level applications can be authorized by default when the Android system is started, without the need for a pop-up window to ask the user to click a confirmation button to authorize after booting up.

[0049] And the permission management files are placed in the target directory, so there is no need to modify the native code and it can adapt to Android version iterations.

[0050] In this embodiment, the permission management file also includes a whitelist list, the whitelist list includes the first application in the Android system, and the permission configuration rules include a first permission configuration rule for the first application; in this way, based on the first application in the whitelist list, the corresponding first permission configuration rule can be obtained in the permission configuration rules; and the first application is given permission configuration based on the first permission configuration rule.

[0051] The whitelist list is written with applications that need to be individually configured with permissions. For each first application in the whitelist list, there is a corresponding first permission configuration rule, that is, the first application and the first permission configuration rule correspond one to one, so that the corresponding first application is configured with permissions through the first permission configuration rule.

[0052] It should be understood that the first permission configuration rules corresponding to the first applications in the whitelist may be the same, partially the same, or completely different.

[0053] In other embodiments, the permission management file also includes a path list, the path list includes a target installation path in the Android system, and the permission configuration rules include a third permission configuration rule for the application under the target installation path; thereby, the corresponding third permission configuration rule can be determined in the permission configuration rules based on the target installation path; and permission configuration can be performed on the application under the target installation path based on the third permission configuration rule.

[0054] In this embodiment, the path list includes at least one target installation path in the Android system. For each target installation path, there may be a corresponding third permission configuration rule, which performs permission configuration on the application under the corresponding target installation path.

[0055] It can be understood that the third permission configuration rules corresponding to each target installation path in the path list may be different, partially the same, or completely the same, and no specific limitation is made here.

[0056] In other embodiments, the permission management file also includes an application store list, the application store list includes a target application store in the Android system, and the permission configuration rules include a fourth permission configuration rule for applications downloaded from the target application store; thereby, the corresponding fourth permission configuration rule can be determined based on the permission configuration rules of the target application store; and permission configuration is performed on applications downloaded from the target application store based on the fourth permission configuration rule.

[0057] In this embodiment, the permission management file also includes an application store list, which includes at least one target application store in the Android system, and in the permission management file, there is a corresponding fourth permission configuration rule for the target application store, and the fourth permission configuration rule performs permission configuration on the downloaded application stored in the corresponding target application store.

[0058] It can be understood that the fourth permission configuration rules corresponding to each target application store in the application store list may be different, partially the same, or completely the same, and no specific limitation is made here.

[0059] In other embodiments, there are multiple permission configuration rules, and there is a priority order between the multiple permission configuration rules. The application in the Android system includes a second application. In this way, after the Android system is started, at least two second permission configuration rules that match the second application in the multiple permission configuration rules can be obtained; based on the priority order, a target second permission configuration rule with a high priority is determined among the at least two second permission configuration rules; and permission is configured for the second application based on the target second permission configuration rule.

[0060] In this embodiment, there are multiple permission configuration rules. If an application can match at least two second permission configuration rules in the permission management file, the application will be regarded as a second application. According to the priority order between the permission configuration rules set in the permission management file, the permission configuration rule with the highest priority among the multiple second permission configuration rules of the second application can be determined and used as the target second permission configuration rule. Permission configuration of the second application is performed based on the target second permission configuration rule.

[0061] For example, in one embodiment, there is a second application, which is both an application in the whitelist and an application under a target installation path in the path list. In this case, the second application corresponds to a third permission configuration rule and a first permission configuration rule. The third permission configuration rule and the first permission configuration rule can be regarded as the second permission configuration rule of the first application. At this time, the configuration rule with a higher priority is determined in the third permission configuration rule and the first permission configuration rule through the priority order as the target second permission configuration rule of the second application, and the second application is configured with permissions through the target second permission configuration rule.

[0062] It can be understood that the permission configuration rules in this embodiment can be written into the authorization type of the corresponding application, and the authorization types include full authorization, partial authorization and full rejection. Full authorization means that all permissions of the corresponding application are automatically authorized, partial authorization means that the relevant permissions written in the permission configuration rules in the corresponding application are authorized, and the permissions not written in the permission configuration rules are processed according to the permissions in the native code. Full rejection means that all permissions of the corresponding application are rejected.

[0063] In some embodiments, when the Android system is started, in response to the startup of the Android system, the permission management file in the target directory is read based on the execution logic preset in the permission management service, and the permission configuration of the application in the Android system is performed based on the permission configuration rules in the permission management file; wherein, the permission management service inherits the system service for permission management in the Android system, and the execution logic preset in the permission management service represents reading the permission management file in the target directory, and the permission configuration of the application in the Android system is performed based on the permission configuration rules in the permission management file.

[0064] In this embodiment, a permission management service is created under the vendor (manufacturer development directory) by means of overlay (used to allow additional resources, configurations or functions to be superimposed (covered) in the system). The permission management services all inherit the system services for permission management in the Android system, such as the system service PackageManagerService in the native code, such as creating permission management services ExtPermissionManagerService and ExtPackageManagerService, which are used for permission management and installation package management, respectively.

[0065] In this way, by inheriting the system service through the permission management service, you can retain the original code and do expansion development without changing the original code. No matter how the original code is changed or upgraded, the permission management service of the expansion development will not be affected.

[0066] In the permission management service, overload the life cycle function of the parent class during the service startup process. In this way, when the Android system starts, this life cycle function can be used to indicate that the permission management service has been started, the operating environment is ready, and the task can be started.

[0067] At the same time, a preset execution logic is written into the lifecycle function, and the preset execution logic represents reading the permission management file under the target directory, and configuring the permission of the application in the Android system based on the permission configuration rules in the permission management file.

[0068] Specifically, the preset execution logic may be to read vendor / etc / data / config.json and parse it, and execute the permission configuration task for the relevant application according to the parsed permission configuration rules.

[0069] In this embodiment, the preset execution logic in the rights management service is written in an overlay native service manner, which has no intrusion on the native code and has strong extensibility.

[0070] In other embodiments, when the Android system is started, a prohibit update instruction is set, and the prohibit update instruction indicates that updating of the permission management file is not supported; before the Android system is started, the permission management file is updated to obtain an updated permission management file, so that after the Android system is started, permissions of applications in the Android system are configured based on the permission configuration rules in the updated permission management file.

[0071] In this embodiment, the permission management file has the highest priority processing right. Even if the system security is compromised and the application permissions are modified, as long as the permission configuration rules of the relevant applications in the permission management file remain unchanged, the permissions of the corresponding applications will still be configured according to the permission management file when the Android system is started.

[0072] The permission management file does not support updating during the Android system startup process, but can be updated before the Android system starts.

[0073] In one embodiment, the Android system runs in the vehicle computer, which can be referred to as Figure 3 , when the car computer is turned on, the Android system is started, the permission management service is started, the preset execution logic is executed, the permission management file in the target directory is read, and the permission configuration rules in the permission management file are used to configure the permissions of the application in the Android system.

[0074] In this embodiment, a method for configuring application permissions is proposed. By writing a permission management file, and writing the permission management file into a target directory for storing configuration files in the Android system, when the Android system is started, the permission management file in the target directory can be directly read to configure permissions for the application and implement default authorization. This process does not require the user to click a confirmation button in a pop-up box to authorize after booting up the system, thereby improving the user experience. In addition, the system runs independently in the target directory in the Android system, decoupling the native code and having no impact on each other, thereby being able to adapt to version iterations of the Android system.

[0075] Another aspect of the present application also provides an application permission configuration device, such as Figure 4 As shown, Figure 4 FIG. 4 is a schematic diagram of a structure of an application permission configuration device shown in an exemplary embodiment of the present application. The application permission configuration device 400 includes:

[0076] The permission management file acquisition module 410 is used to acquire a permission management file; wherein the permission management file includes permission configuration rules for applications in the Android system.

[0077] The file processing module 430 is used to integrate the permission management file into the target directory in the Android system; wherein the target directory is a directory for storing configuration files in the Android system.

[0078] The permission configuration module 450 is used to read the permission management file in the target directory when the Android system is started, and perform permission configuration on the application in the Android system based on the permission configuration rules in the permission management file.

[0079] In an optional manner, the permission management file further includes a whitelist list, the whitelist list includes a first application in the Android system, and the permission configuration rule includes a first permission configuration rule for the first application; the permission configuration module 450 further includes:

[0080] The first permission configuration rule acquisition unit is configured to acquire a corresponding first permission configuration rule from the permission configuration rules based on the first application in the whitelist.

[0081] The first permission configuration unit performs permission configuration on the first application based on a first permission configuration rule.

[0082] In an optional manner, there are multiple permission configuration rules, and the multiple permission configuration rules have a priority order. The application in the Android system includes the second application; the permission configuration module 450 further includes:

[0083] The second permission configuration rule acquisition unit acquires at least two second permission configuration rules matched by the second application from among the plurality of permission configuration rules.

[0084] The target second permission configuration rule acquisition unit determines a target second permission configuration rule with a higher priority among the at least two second permission configuration rules based on the priority order.

[0085] The second permission configuration unit performs permission configuration on the second application based on the target second permission configuration rule.

[0086] In an optional manner, the permission management file further includes a path list, the path list includes a target installation path in the Android system, and the permission configuration rule includes a third permission configuration rule for an application under the target installation path; the permission configuration module 450 further includes:

[0087] The third permission configuration rule acquisition unit determines a corresponding third permission configuration rule in the permission configuration rule based on the target installation path.

[0088] The third permission configuration unit performs permission configuration on the application under the target installation path based on the third permission configuration rule.

[0089] In an optional manner, the permission management file further includes an application store list, the application store list includes a target application store in the Android system, and the permission configuration rule includes a fourth permission configuration rule for applications downloaded from the target application store; the permission configuration module 450 further includes:

[0090] The fourth permission configuration rule acquisition unit determines a corresponding fourth permission configuration rule based on the permission configuration rule of the target application store.

[0091] The fourth permission configuration unit performs permission configuration on the application downloaded from the target application store based on the fourth permission configuration rule.

[0092] In an optional manner, the permission configuration module 450 further includes:

[0093] The permission configuration unit responds to the startup of the Android system, reads the permission management file under the target directory based on the execution logic preset in the permission management service, and performs permission configuration on the application in the Android system based on the permission configuration rules in the permission management file; wherein the permission management service inherits the system service for permission management in the Android system, the execution logic preset in the permission management service represents reading the permission management file under the target directory, and performs permission configuration on the application in the Android system based on the permission configuration rules in the permission management file.

[0094] In an optional manner, the application permission configuration device 400 further includes:

[0095] The first instruction module is used to set a prohibition update instruction when the Android system is started, and the prohibition update instruction indicates that the update of the permission management file is not supported.

[0096] The second instruction module is used to update the permission management file before the Android system is started to obtain the updated permission management file, so as to configure permissions for applications in the Android system based on the permission configuration rules in the updated permission management file after the Android system is started.

[0097] The application permission configuration device of the present application writes a permission management file, and writes the permission management file into a target directory for storing configuration files in the Android system. Thus, when the Android system is started, the permission management file in the target directory can be directly read to configure permissions for the application and implement default authorization. This process does not require the user to click a confirmation button in a pop-up window to authorize after booting up the device, thereby improving the user experience. The device runs independently in a target directory in the Android system, decoupling the native code and having no influence on each other, thus being adaptable to version iterations of the Android system.

[0098] It should be noted that the application permission configuration device provided in the above embodiment and the application permission configuration method provided in the above embodiment belong to the same concept, wherein the specific manner in which each module and unit performs operations has been described in detail in the method embodiment and will not be repeated here.

[0099] Another aspect of the present application provides an electronic device, including: a controller; a memory for storing one or more programs, and when the one or more programs are executed by the controller, the above-mentioned application permission configuration method is executed.

[0100] See also Figure 5 , Figure 5 1 is a schematic diagram of the structure of a computer system of an electronic device shown in an exemplary embodiment of the present application, which shows a schematic diagram of the structure of a computer system of an electronic device suitable for implementing an embodiment of the present application.

[0101] It should be noted that Figure 5 The computer system 500 of the electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.

[0102] like Figure 5 As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes according to the program stored in the read-only memory (ROM) 502 or the program loaded from the storage part 508 to the random access memory (RAM) 503, such as executing the method in the above embodiment. In the RAM 503, various programs and data required for system operation are also stored. The CPU 501, ROM 502 and RAM 503 are connected to each other through a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

[0103] The following components are connected to the I / O interface 505: an input section 506 including a keyboard, a mouse, etc.; an output section 507 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 508 including a hard disk, etc.; and a communication section 509 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 509 performs communication processing via a network such as the Internet. A drive 510 is also connected to the I / O interface 505 as needed. A removable medium 511, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 510 as needed so that a computer program read therefrom is installed into the storage section 508 as needed.

[0104] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a computer program for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication section 609, and / or installed from a removable medium 611. When the computer program is executed by a central processing unit (CPU) 601, various functions defined in the system of the present application are executed.

[0105] It should be noted that the computer-readable medium shown in the embodiment of the present application can be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium can be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media can include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it. In the present application, a computer-readable signal medium can include a data signal propagated in a baseband or as a part of a carrier wave, wherein a computer-readable computer program is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which may send, propagate, or transmit programs for use by or in conjunction with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wired, etc., or any suitable combination of the above.

[0106] The flowchart and block diagram in the accompanying drawings illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present application. Wherein, each box in the flowchart or block diagram can represent a module, a program segment, or a part of the code, and the above-mentioned module, program segment, or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order than the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of boxes in the block diagram or flowchart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0107] The units involved in the embodiments described in this application may be implemented by software or hardware, and the units described may also be set in a processor. The names of these units do not, in some cases, constitute limitations on the units themselves.

[0108] Another aspect of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the vehicle light control method as described above is implemented. The computer-readable storage medium may be included in the electronic device described in the above embodiment, or may exist independently without being assembled into the electronic device.

[0109] Another aspect of the present application also provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the vehicle light control method provided in each of the above embodiments.

[0110] According to one aspect of an embodiment of the present application, a computer system is also provided, including a central processing unit (CPU), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) or a program loaded from a storage portion into a random access memory (RAM), such as executing the method in the above embodiment. In RAM, various programs and data required for system operation are also stored. CPU, ROM and RAM are connected to each other via a bus. An input / output (I / O) interface is also connected to the bus.

[0111] The following components are connected to the I / O interface: an input part including a keyboard, a mouse, etc.; an output part including a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker; a storage part including a hard disk, etc.; and a communication part including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication part performs communication processing via a network such as the Internet. A drive is also connected to the I / O interface as needed. Removable media, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., are installed on the drive as needed so that the computer program read therefrom is installed into the storage part as needed.

[0112] The above content is only a preferred exemplary embodiment of the present application and is not intended to limit the implementation scheme of the present application. A person skilled in the art can easily make corresponding changes or modifications based on the main concept and spirit of the present application. Therefore, the scope of protection of the present application shall be based on the scope of protection required by the claims.

Claims

1. A method for configuring application permissions, characterized in that: include: Obtaining a permission management file; wherein the permission management file includes permission configuration rules for applications in the Android system; Integrate the permission management file into the target directory in the Android system; wherein the target directory is a directory in the Android system for storing configuration files; When the Android system is started, the permission management file in the target directory is read, and permission configuration is performed on the application in the Android system based on the permission configuration rules in the permission management file.

2. The method according to claim 1, characterized in that The permission management file further includes a whitelist list, the whitelist list includes a first application in the Android system, and the permission configuration rule includes a first permission configuration rule for the first application; The step of configuring permissions for the application in the Android system based on the permission configuration rules in the permission management file further includes: Based on the first application in the whitelist, obtaining a corresponding first permission configuration rule in the permission configuration rule; Perform permission configuration on the first application based on the first permission configuration rule.

3. The method according to claim 1, characterized in that: The number of the permission configuration rules is multiple, and there is a priority order between the multiple permission configuration rules, and the application in the Android system includes a second application; The step of configuring permissions for the application in the Android system based on the permission configuration rules in the permission management file further includes: Obtaining at least two second permission configuration rules matched by the second application from among the plurality of permission configuration rules; Determine a target second permission configuration rule with a high priority among the at least two second permission configuration rules based on the priority order; The second application is given permission configuration based on the target second permission configuration rule.

4. The method according to claim 1, characterized in that The permission management file further includes a path list, the path list includes a target installation path in the Android system, and the permission configuration rule includes a third permission configuration rule for an application under the target installation path; The step of configuring permissions for the application in the Android system based on the permission configuration rules in the permission management file further includes: Determining a corresponding third permission configuration rule in the permission configuration rule based on the target installation path; Based on the third permission configuration rule, permission configuration is performed on the application under the target installation path.

5. The method according to claim 1, characterized in that The permission management file also includes an application store list, the application store list includes a target application store in the Android system, and the permission configuration rule includes a fourth permission configuration rule for applications downloaded from the target application store; The step of configuring permissions for the application in the Android system based on the permission configuration rules in the permission management file further includes: Determining a fourth permission configuration rule corresponding to the target application store in the permission configuration rule; Permissions are configured for the application downloaded from the target application store based on the fourth permission configuration rule.

6. The method according to claim 1, characterized in that When the Android system is started, the permission management file in the target directory is read, and permission configuration is performed on the application in the Android system based on the permission configuration rules in the permission management file, further comprising: In response to the startup of the Android system, the permission management file under the target directory is read based on the execution logic preset in the permission management service, and the permission configuration is performed on the application in the Android system based on the permission configuration rules in the permission management file; wherein, the permission management service inherits the system service for permission management in the Android system, and the execution logic preset in the permission management service represents reading the permission management file under the target directory, and the permission configuration is performed on the application in the Android system based on the permission configuration rules in the permission management file.

7. The method according to any one of claims 1 to 6, characterized in that: After configuring permissions for the application in the Android system based on the permission configuration rules in the permission management file, the method further includes: When the Android system is started, a prohibition update instruction is set, wherein the prohibition update instruction indicates that updating of the permission management file is not supported; Before the Android system is started, the permission management file is updated to obtain an updated permission management file, so that after the Android system is started, permission configuration is performed on applications in the Android system based on permission configuration rules in the updated permission management file. Obtaining query indicators of the business request data; A data access interface is called, and data corresponding to the query index is searched in the database through the data access interface.

8. An application permission configuration device, characterized in that: include: A rights management file acquisition module, used to acquire a rights management file; wherein the rights management file includes rights configuration rules for applications in the Android system; A file processing module, used to integrate the permission management file into a target directory in the Android system; wherein the target directory is a directory in the Android system for storing configuration files; The permission configuration module is used to read the permission management file in the target directory when the Android system is started, and perform permission configuration on the application in the Android system based on the permission configuration rules in the permission management file.

9. An electronic device, characterized in that: include: Controller; A memory for storing one or more programs, which, when executed by a controller, enables the controller to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and when the computer-readable instructions are executed by a processor of a computer, the computer is caused to execute the method according to any one of claims 1 to 7.