A vehicle system application authority management method, device, equipment and storage medium

Abstract

A method, apparatus, device and storage medium for managing application permissions of a vehicle system in an embodiment of the present invention obtains the application package identifier and application running permissions of a system built-in application in the vehicle system, then generates a runtime permission whitelist, and then compares the runtime permission whitelist with the application permission declaration file to determine the permission declaration status of the application running permissions of the system built-in application. If the permission declaration status is completed, the runtime permissions of the system built-in application are controlled to be granted by default. The present invention updates the permissions of the built-in application in the vehicle system to the system running permission file, and grants the running permissions of the built-in application in the vehicle system by default when the system is started for the first time, avoiding a complicated authorization process. Moreover, when the permissions of the built-in application are updated to the system running permission file, the runtime permissions can be granted by default when the software is started again after an upgrade, ensuring iterative upgrades of the software and improving user experience.

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a method, apparatus, device, and storage medium for managing application permissions of a vehicle system. Background Art

[0002] With the continuous iteration and update of the Android system, especially after Android 6.0, the protection of user privacy has been continuously strengthened, and the access of application permissions has become increasingly restricted. With the introduction of the dynamic permission mechanism, each newly installed application needs to grant or deny permissions, which plays a significant role in protecting user privacy. However, since each newly installed application requires the user to actively decide whether to grant permissions, the relevant technical fields have also made many innovations in permission management.

[0003] In related technologies, permission management is mainly limited to some applications that are subsequently installed actively. It can manage the application permissions of the client in batches and perform relevant permission checks on each permission. However, permission management for some system built-in applications requires users to manually grant permissions in a tedious manner, and the use of traditional permission management solutions cannot enable the application version to be iterated and upgraded normally, reducing the user experience. Summary of the Invention

[0004] The purpose of the embodiments of the present invention is to provide a method, apparatus, device and storage medium for managing application permissions of a vehicle system to solve the problem that system built-in applications cannot be granted runtime permissions by default when the system is started for the first time.

[0005] The present invention provides a method for managing application permissions of a vehicle system, the method comprising: obtaining application information of a system built-in application in the vehicle system, the application information comprising an application package identifier and an application running permission, the application package identifier being used to represent the system built-in application, and the application running permission being the runtime permission required by the system built-in application when the system is first powered on and started and granted by default; generating a runtime permission whitelist based on the application package identifier and the application running permission; comparing the runtime permission whitelist with an application permission declaration file, the application permission declaration file comprising an application package identifier and declared running permissions; if the application running permissions of a system built-in application with the same application package identifier are the same as the declared running permissions, determining the permission declaration status of the application running permissions as completed declaration; and granting by default the target application permissions of the system built-in application, the target application permissions comprising the application running permissions with a permission declaration status of completed declaration.

[0006] In one embodiment of the present invention, after generating a runtime permission whitelist based on the application package identifier and the application execution permission, the method further includes: configuring a configuration file of the runtime permission whitelist to generate the runtime permission whitelist under a system preset path.

[0007] In one embodiment of the present invention, after configuring the configuration file of the runtime permission whitelist, it also includes: updating the application package identifier and the application running permission to the vehicle system runtime permission file, so as to read the application package identifier and the application running permission when the vehicle system is started.

[0008] In one embodiment of the present invention, the application package identifier and the application running permission are updated to the vehicle system runtime permission file, including: establishing an application file of the system built-in application based on the application package identifier; writing the application running permission and the application package identifier of the system built-in application into the application file; and adding the written application file to the vehicle system runtime permission file.

[0009] In one embodiment of the present invention, the runtime permission whitelist is compared with the application permission declaration file, and after the application permission declaration file includes the application package identifier and the declared runtime permissions, the method further includes: if the application runtime permissions and the declared runtime permissions of the system built-in application with the same application package identifier are different, determining the permission declaration status of the application runtime permissions as an incomplete declaration; when the system built-in application is running, and there is a permission requirement for the application runtime permissions with the permission declaration status as an incomplete declaration, requesting to grant the application runtime permissions of the system built-in application.

[0010] In one embodiment of the present invention, obtaining application running permissions includes: obtaining application initial permissions; dividing the application initial permissions into default-granted runtime permissions and running auxiliary permissions according to a preset application running permission requirement file; and determining the obtained default-granted runtime permissions as the application running permissions.

[0011] An embodiment of the present invention also provides an application permission management device, which includes: an information acquisition module for acquiring application information of a system-built-in application in a vehicle system, the application information including an application package identifier and application running permissions, the application package identifier being used to represent the system-built-in application, and the application running permissions being the runtime permissions required by the system-built-in application that are granted by default when the system is started for the first time; an information reading module for generating a runtime permission whitelist based on the application package identifier and the application running permissions; a permission granting module for comparing the runtime permission whitelist with an application permission declaration file, the application permission declaration file including an application package identifier and declared running permissions; if the application running permissions of a system-built-in application with the same application package identifier are the same as the declared running permissions, the permission declaration status of the application running permissions is determined to be completed declaration; the target application permissions of the system-built-in application are authorized by default, and the target application permissions include the application running permissions with a permission declaration status of completed declaration.

[0012] In one embodiment of the present invention, the permission granting module includes: a declaration status determination unit, used to compare the runtime permission whitelist with the application permission declaration file, the application permission declaration file includes an application package identifier and a declared runtime permission; if the application runtime permission of a system built-in application with the same application package identifier is the same as the declared runtime permission, the permission declaration status of the application runtime permission is determined to be a completed declaration; if the application runtime permission of a system built-in application with the same application package identifier is different from the declared runtime permission, the permission declaration status of the application runtime permission is determined to be an incomplete declaration; a runtime permission granting unit, used to perform default authorization on the target application permission of the system built-in application, the target application permission includes the application runtime permission with a completed declaration status; when the system built-in application is running and there is a permission requirement for the application runtime permission with an incomplete declaration status, a request is made to grant the application runtime permission of the system built-in application.

[0013] An embodiment of the present invention also provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the electronic device implements any of the above-mentioned vehicle system application authority management methods.

[0014] An embodiment of the present invention further provides a computer-readable storage medium having computer-readable instructions stored thereon. When the computer-readable instructions are executed by a processor of a computer, the computer is enabled to execute any of the above-mentioned vehicle system application authority management methods.

[0015] A method, apparatus, device and storage medium for managing application permissions of a vehicle system in an embodiment of the present invention obtains the application package identifier and application running permissions of a system built-in application in the vehicle system, then generates a runtime permission whitelist, and then compares the runtime permission whitelist with the application permission declaration file to determine the permission declaration status of the application running permissions of the system built-in application. If the permission declaration status is completed, the runtime permissions of the system built-in application are controlled to be granted by default. The present invention updates the permissions of the built-in application in the vehicle system to the system running permission file, and grants the running permissions of the built-in application in the vehicle system by default when the system is started for the first time, avoiding a complicated authorization process. Moreover, when the permissions of the built-in application are updated to the system running permission file, the runtime permissions can be granted by default when the software is started again after an upgrade, ensuring iterative upgrades of the software and improving user experience.

[0016] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings are incorporated into and constitute a part of the specification, illustrating embodiments consistent with the present application and, together with the specification, serving to explain the principles of the present application. It is obvious that the drawings described below are merely some embodiments of the present application, and a person of ordinary skill in the art can derive other drawings based on these drawings without inventive effort. In the drawings:

[0018] Figure 1 is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application;

[0019] Figure 2 This is a flowchart of a method for managing application permissions of a vehicle system according to an exemplary embodiment of the present application;

[0020] Figure 3 This is a flowchart of granting application execution permissions by default, as shown in an exemplary embodiment of the present application;

[0021] Figure 4 This is a flowchart of runtime permission whitelist parsing shown in an exemplary embodiment of the present application;

[0022] Figure 5 1 is a schematic diagram of a vehicle system application authority management method and apparatus according to an exemplary embodiment of the present application;

[0023] Figure 6 is a schematic diagram of a permission granting module shown in an exemplary embodiment of the present application;

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

[0025] The following will describe embodiments of the present invention with reference to the accompanying drawings and specific embodiments. Those skilled in the art will readily appreciate the other advantages and benefits of the present invention from the disclosure herein. The present invention may also be implemented or applied through various other specific embodiments, and the details in this specification may be modified or altered based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are intended only to illustrate the present invention and are not intended to limit the scope of protection of the present invention.

[0026] It should be noted that the illustrations provided in the following embodiments are merely schematic illustrations of the basic concept of the present invention. Therefore, the illustrations only show components related to the present invention and are not drawn according to the number, shape, and size of components in actual implementation. In actual implementation, the type, quantity, and proportion of each component may be changed arbitrarily, and the component layout may also be more complex.

[0027] In the following description, numerous details are discussed to provide a more thorough explanation of the embodiments of the present invention. However, it will be apparent to those skilled in the art that the embodiments of the present invention may be practiced without these specific details. In other embodiments, well-known structures and devices are shown in block diagram form rather than in detail to avoid obscuring the embodiments of the present invention.

[0028] The term "and / or" used in this application describes a relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0029] Figure 1 It is a schematic diagram of an exemplary system architecture shown in an exemplary embodiment of the present application.

[0030] Reference Figure 1As shown, the system architecture may include an in-vehicle system 101 and a computer device 102. Specifically, the in-vehicle system 101 is configured to obtain application information of system-built-in applications in the in-vehicle system. The application information includes an application package identifier and application execution permissions. The application package identifier represents the system-built-in application, and the application execution permissions are the default runtime permissions granted to the system-built-in application upon initial startup. The information is then provided to the computer device 102 for processing. The computer device 102 may be at least one of a microcomputer, an embedded computer, a network computer, or the like. Relevant technicians may implement, on the computer device 101, generation of a runtime permission whitelist based on the application package identifier and the application execution permissions, and then compare the runtime permission whitelist with an application permission declaration file, which includes the application package identifier and declared execution permissions. If the application execution permissions and the declared execution permissions of a system-built-in application with the same application package identifier are identical, the permission declaration status of the application execution permissions is determined to be "completed"; and target application permissions of the system-built-in application are granted by default, with the target application permissions including the application execution permissions with the "completed" permission declaration status.

[0031] Schematically, after obtaining the application package identifier and application running permission of the system built-in application in the vehicle system 101, the computer device 102 generates a runtime permission whitelist, and then compares the runtime permission whitelist with the application permission declaration file to determine the permission declaration status of the application running permission of the system built-in application. If the permission declaration status is completed, the control grants the runtime permission of the system built-in application by default. The present invention updates the permissions of the built-in application in the vehicle system to the system running permission file, and grants the running permission of the built-in application in the vehicle system by default when the system is started for the first time, avoiding a complicated authorization process. Moreover, when the permissions of the built-in application are updated to the system running permission file, the runtime permission can be granted by default when the software is started again after the software is upgraded, ensuring the iterative upgrade of the software and improving the user experience.

[0032] Figure 2 This is a flowchart of a vehicle system application permission management method shown in an exemplary embodiment of the present application. The vehicle system application permission management method can be executed by a computing processing device, which can be Figure 1 The computer device 102 shown in FIG. Figure 2 As shown, the flowchart of the vehicle system application authority management method includes at least steps S210 to S250, which are described in detail as follows:

[0033] In step S210, application information of the system built-in application in the vehicle system is obtained. The application information includes the application package identifier and the application running permission. The application package identifier is used to represent the system built-in application. The application running permission is the runtime permission required by the system built-in application that is granted by default when the system is started for the first time.

[0034] In one embodiment of the present application, the applications to be installed and their associated files are packaged, the installation path is set, the applications are installed in the system's built-in application partition, and the application package identifier and application execution permissions are extracted from the application information to form a new permissions file, which is named the runtime permissions whitelist. This step constructs a new permissions file with the application package representation and runtime permissions of the applications to be granted permissions as content, thereby performing permissions management on the applications to be granted permissions in batches.

[0035] In one embodiment of the present application, the vehicle system application storage area is mainly divided into the following three partitions: an application data storage area for storing third-party applications, a privileged application storage area for privileged applications, and a system application storage area for other system applications. In the actual application of the present application, the above-mentioned applications to be granted permissions can be stored in the system application storage partition.

[0036] In one embodiment of the present application, obtaining application running permissions requires first obtaining the application initial permissions, then dividing the application initial permissions into default-granted runtime permissions and running auxiliary permissions according to the preset application running permission requirement file, and finally obtaining the default-granted runtime permissions as application running permissions.

[0037] The default runtime permissions are those required for app launch, including but not limited to storage permissions, location permissions, and background permissions. The auxiliary permissions are those required for app extensibility, including but not limited to floating window permissions, microphone permissions, device search permissions, and Bluetooth permissions. The above permission examples are merely illustrative of the default runtime permissions and auxiliary permissions, and do not specifically limit them.

[0038] In step S220, a runtime permission whitelist is generated based on the application package identifier and the application execution permission.

[0039] In one embodiment of the present application, after generating a runtime permission whitelist based on the application package identifier and the initial runtime permissions, it is also necessary to configure the configuration file of the runtime permission whitelist to generate a runtime permission whitelist under the system preset path, where the system preset path can be the system's built-in application storage area, or other storage areas that can implement this embodiment, which is not specifically limited here.

[0040] In one embodiment of the present application, after configuring the configuration file of the runtime permission whitelist, it is also necessary to update the application package identifier and application running permissions to the vehicle system runtime permission file so that the application package identifier and application running permissions can be read when the vehicle system is started.

[0041] In one embodiment of the present application, the application package identifier and application running permissions are updated to the vehicle system runtime permission file, including establishing an application file for the system built-in application based on the application package identifier, then writing the application running permissions and application package identifier of the system built-in application into the application file, and finally adding the written application file to the vehicle system runtime permission file.

[0042] In step S230 , the runtime permission whitelist is compared with the application permission declaration file, where the application permission declaration file includes the application package identifier and the declared runtime permissions.

[0043] In one embodiment of the present application, if an application needs to use certain permissions, it must declare these permissions in its manifest file. The file used to declare these permissions is an application permission declaration file.

[0044] In step S240 , if the application execution permission of the system built-in application with the same application package identifier is the same as the declared execution permission, the permission declaration status of the application execution permission is determined to be completed declaration.

[0045] In one embodiment of the present application, if the application running permission and the declared running permission of a system built-in application with the same application package identifier are different, the permission declaration status of the application running permission is determined to be an incomplete declaration. When the system built-in application is running and there is a permission requirement for the application running permission with the permission declaration status being an incomplete declaration, a request is made to grant the application running permission to the system built-in application.

[0046] In step S250 , the target application permissions of the system built-in application are authorized by default, and the target application permissions include application execution permissions whose permission declaration status is completed.

[0047] See also Figure 3 , Figure 3 This is a flowchart of granting runtime permissions by default as shown in an exemplary embodiment of the present application. Figure 3 The implementation environment shown is specifically implemented by the vehicle system 101 and / or the computer device 102 in the implementation environment. It should be understood that the method can also be applied to other exemplary implementation environments and specifically implemented by devices in other implementation environments. This embodiment does not limit the implementation environment to which the method is applicable.

[0048] like Figure 3As shown, in an exemplary embodiment, the package name and runtime permissions corresponding to the vehicle system application are first extracted based on the system's built-in application information to form a runtime permission whitelist, and then the runtime permission whitelist is parsed, and the list of permissions required at runtime in the runtime permission whitelist is used as the content of the permission application, and the runtime permissions in this part of the whitelist are granted, and other runtime permissions are dynamically applied for and authorized when the application is running.

[0049] In this exemplary embodiment, after parsing the runtime permission whitelist, the runtime permission whitelist is compared with the application permission declaration file to determine the declaration status of the runtime permissions in the whitelist. If the runtime permissions in the whitelist have been declared in the application permission declaration file, the runtime permissions are granted by default, while other runtime permissions can only be dynamically applied for by the user when the application is running.

[0050] See also Figure 4 , Figure 4 This is a flowchart of the runtime permission whitelist parsing shown in an exemplary embodiment of the present application. This method can be applied to Figure 4 The implementation environment shown is specifically implemented by the vehicle system 101 and / or the computer device 102 in the implementation environment. It should be understood that the method can also be applied to other exemplary implementation environments and specifically implemented by devices in other implementation environments. This embodiment does not limit the implementation environment to which the method is applicable.

[0051] like Figure 4 As shown in the figure, after the package management service is initialized and started in the system service, it enters the system preparation phase of the permission management service. During the system preparation phase, the grantDefaultPermissions method in the default permission handling policy management class is called. This method pre-grants certain specific runtime permissions to each application that has modified runtime permissions. The permissions are mainly divided into three categories: granting any runtime permissions to system components and privileged applications, granting specific runtime permissions to applications with important intents, and granting specified runtime permissions to specific applications.

[0052] In this exemplary embodiment, the default runtime permission granting method calls a method for granting specific runtime permissions to a specific application. In this method, the generated runtime permission whitelist is first read, the read whitelist is parsed, and then the grantRuntimePermissions method is called to update the parsed package name and runtime permissions to the overall runtime permission file of the vehicle system. This achieves the purpose of reading the system's runtime permission file when the system is first powered on, thereby granting runtime permissions by default.

[0053] The following describes an embodiment of the device of the present application, which can be used to implement the vehicle system application permission management method in the above embodiment of the present application. For details not disclosed in the system embodiment of the present application, please refer to the embodiment of the vehicle system application permission management method in the above embodiment of the present application.

[0054] Figure 5 This is a schematic diagram of a vehicle system application authority management method and device shown in an exemplary embodiment of the present application. The device can be applied to Figure 2 The implementation environment shown in FIG. 1 is specifically configured in the computer device 102. The apparatus may also be applicable to other exemplary implementation environments and specifically configured in other devices. This embodiment does not limit the implementation environment to which the apparatus is applicable.

[0055] like Figure 5 As shown, the exemplary vehicle system application authority management method and device includes: an information acquisition module 501, an information reading module 502, and a authority granting module 503.

[0056] Among them, the information acquisition module 501 is used to obtain application information of system built-in applications in the vehicle system, and the application information includes application package identification and application running permissions. The application package identification is used to represent the system built-in application, and the application running permissions are the runtime permissions required by the system built-in application when it is started for the first time; the information reading module 502 is used to generate a runtime permission whitelist based on the application package identification and application running permissions; the permission granting module 503 is used to compare the runtime permission whitelist with the application permission declaration file, and the application permission declaration file includes the application package identification and the declared running permissions; if the application running permissions and the declared running permissions of the system built-in application with the same application package identification are the same, the permission declaration status of the application running permissions is determined to be completed declaration; the target application permissions of the system built-in application are authorized by default, and the target application permissions include application running permissions with a permission declaration status of completed declaration.

[0057] In one embodiment of the present application, Figure 6 This is a schematic diagram of a permission granting module shown in an exemplary embodiment of the present application. Figure 6 As shown, the permission granting module includes a declaration status determination unit 601 and an execution permission granting unit 602.

[0058] Among them, the declaration status determination unit 601 is used to compare the runtime permission whitelist with the application permission declaration file, and the application permission declaration file includes the application package identifier and the declared runtime permission; if the application running permission and the declared running permission of the system built-in application with the same application package identifier are the same, the permission declaration status of the application running permission is determined to be completed declaration; if the application running permission and the declared running permission of the system built-in application with the same application package identifier are different, the permission declaration status of the application running permission is determined to be incomplete declaration; the running permission granting unit 602 is used to perform default authorization on the target application permissions of the system built-in application, and the target application permissions include the application running permissions with the permission declaration status of completed declaration; when the system built-in application is running, and there is a permission requirement for the application running permission with the permission declaration status of incomplete declaration, a request is made to grant the application running permission of the system built-in application.

[0059] An embodiment of the present application also provides an electronic device, comprising: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by one or more processors, the electronic device implements the vehicle system application permission management method provided in the above-mentioned embodiments.

[0060] Figure 7 The following is a schematic diagram showing the structure of a computer system suitable for implementing an electronic device according to an embodiment of the present application. Figure 7 The computer system 700 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.

[0061] like Figure 7 As shown, computer system 700 includes a central processing unit (CPU) 701, which can perform various appropriate actions and processes according to the program stored in read-only memory (ROM) 702 or the program loaded from the storage portion into random access memory (RAM) 703, such as the method for executing the above embodiment. Various programs and data required for system operation are also stored in RAM 703. CPU 701, ROM 702 and RAM 703 are connected to each other via a bus. Input / output (I / O) interface 705 is also connected to bus 704.

[0062] The following components are connected to the I / O interface 705: an input section 706 including a keyboard, a mouse, etc.; an output section 707 including devices such as a cathode ray tube (CRT), a liquid crystal display (LCD), and a speaker; a storage section 708 including a hard disk; and a communication section 709 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section performs communication processing via a network such as the Internet. A drive is also connected to the I / O interface 705 as needed. Removable media 711, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed in the drive 710 as needed so that computer programs read therefrom can be installed into the storage section 708 as needed.

[0063] 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 via the communication section 709, and / or installed from a removable medium 711. When the computer program is executed by the central processing unit (CPU) 701, the various functions defined in the system of the present application are executed.

[0064] It should be noted that the computer-readable medium shown in the embodiments 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 signal medium can include a data signal propagated in baseband or as part of a carrier wave, which carries a computer-readable computer program. This propagated data signal can take a variety of forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. A computer program embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0065] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. Among them, each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that 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 the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0066] In the corresponding drawings of the above embodiments, connecting lines can represent the connection relationship between various components to represent more constituent signal paths and / or one or more ends of some lines have arrows to indicate the main information flow direction. The connecting lines serve as an identifier and are not a limitation to the scheme itself. Instead, the use of these lines in combination with one or more exemplary embodiments helps to connect circuits or logic units more easily. Any represented signal (determined by design requirements or preferences) can actually include one or more signals that can be transmitted in any direction and can be implemented with any appropriate type of signal scheme.

[0067] 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. In some cases, the names of these units do not constitute limitations on the units themselves.

[0068] Another aspect of the present application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the aforementioned vehicle system application permission management method. The computer-readable storage medium may be included in the electronic device described in the above embodiments, or may exist independently and not be incorporated into the electronic device.

[0069] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiment of the application, the features and functions of two or more modules or units described above can be concretized in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0070] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a touch terminal, or a network device, etc.) to execute the method according to the embodiments of the present application.

[0071] It should be noted that the present application can be used in a wide variety of general-purpose or special-purpose computing system environments or configurations, such as personal computers, server computers, handheld or portable devices, tablet devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above, and the like.

[0072] Those skilled in the art will readily conceive of other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present application that follow the general principles of this application and include common knowledge or customary techniques in the art that are not disclosed herein.

[0073] It should be understood that 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. Ordinary technicians in this field 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 should be the scope of protection required by the claims.

Claims

1. A method for managing application permissions of a vehicle system, characterized in that: The method comprises: Obtain application information of a system-built-in application in the vehicle system, the application information including an application package identifier and application execution permissions, the application package identifier being used to identify the system-built-in application, and the application execution permissions being the default permissions granted to the system-built-in application when it is first started; Generate a runtime permission whitelist based on the application package identifier and the application execution permission; Comparing the runtime permission whitelist with an application permission declaration file, wherein the application permission declaration file includes an application package identifier and declared runtime permissions; If the application running permission of the system built-in application with the same application package identifier is the same as the declared running permission, determining the permission declaration status of the application running permission as completed declaration; The target application permissions of the system's built-in applications are authorized by default, and the target application permissions include the application running permissions whose permission declaration status is completed. The configuration file of the runtime permission whitelist is configured to generate the runtime permission whitelist under the system preset path, and the application package identifier and the application running permissions are updated to the vehicle system runtime permission file to read the application package identifier and the application running permissions when the vehicle system is started.

2. The vehicle system application authority management method according to claim 1, characterized in that: Updating the application package identifier and the application running permission to the vehicle system runtime permission file includes: Creating an application file for a system built-in application according to the application package identifier; Writing the application execution permission of the system built-in application and the application package identifier into the application file; The written application file is added to the vehicle system runtime permission file.

3. The vehicle system application authority management method according to any one of claims 1-2, characterized in that: After comparing the runtime permission whitelist with an application permission declaration file, wherein the application permission declaration file includes an application package identifier and declared runtime permissions, the method further includes: If the application running permission of the system built-in application with the same application package identifier is different from the declared running permission, determining the permission declaration status of the application running permission as incomplete declaration; When the system built-in application is running and there is a permission requirement for the application running permission whose permission declaration status is incomplete declaration, a request is made to grant the application running permission to the system built-in application.

4. The vehicle system application authority management method according to any one of claims 1-2, characterized in that: Obtain application running permissions, including: Obtain initial permissions for the application; Dividing the initial permissions of the application into default runtime permissions and auxiliary permissions granted by default according to the preset application running permission requirement file; The obtained default granted runtime permission is determined as the application execution permission.

5. A vehicle system application authority management device, characterized in that: The device comprises: An information acquisition module is used to obtain application information of a system-built-in application in the vehicle system, wherein the application information includes an application package identifier and application execution permissions, wherein the application package identifier is used to represent the system-built-in application, and the application execution permissions are the permissions required for the system-built-in application to be run by default when the vehicle is first powered on; An information reading module, configured to generate a runtime permission whitelist based on the application package identifier and the application execution permission; A permission granting module is used to compare the runtime permission whitelist with the application permission declaration file, where the application permission declaration file includes an application package identifier and declared runtime permissions; if the application runtime permissions of a system built-in application with the same application package identifier are the same as the declared runtime permissions, the permission declaration status of the application runtime permissions is determined to be completed declaration; the target application permissions of the system built-in application are authorized by default, and the target application permissions include the application runtime permissions with a permission declaration status of completed declaration; the configuration file of the runtime permission whitelist is configured to generate the runtime permission whitelist under the system preset path, and the application package identifier and the application runtime permissions are updated to the vehicle system runtime permission file, so that the application package identifier and the application runtime permissions can be read when the vehicle system is started.

6. The vehicle system application authority management device according to claim 5, characterized in that: The permission granting module includes: a declaration status determination unit, configured to compare the runtime permission whitelist with an application permission declaration file, the application permission declaration file including an application package identifier and declared runtime permissions; if the application runtime permissions of a system built-in application with the same application package identifier are the same as the declared runtime permissions, determining the permission declaration status of the application runtime permissions as completed declaration; if the application runtime permissions of a system built-in application with the same application package identifier are different from the declared runtime permissions, determining the permission declaration status of the application runtime permissions as incomplete declaration; The running permission granting unit is used to perform default authorization on the target application permissions of the system built-in application, and the target application permissions include the application running permissions whose permission declaration status is completed; when the system built-in application is running and there is a permission requirement for the application running permissions whose permission declaration status is incomplete, request to grant the application running permissions of the system built-in application.

7. An electronic device, characterized in that: include: one or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, enables the electronic device to implement the vehicle system application authority management method as described in any one of claims 1 to 4.

8. 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 vehicle system application authority management method according to any one of claims 1 to 4.

Images