Vehicle-mounted application starting method and device, electronic equipment and storage medium

Abstract

The application discloses a kind of vehicle-mounted application program starting method, device, electronic equipment and storage medium.In whole vehicle power-on, the first operating system and the second operating system of virtualization in the target controller are started;The first vehicle-mounted application program to be quickly started in the target vehicle is started by the first operating system, and the second vehicle-mounted application program to be safely started in the target vehicle is started by the second operating system;In the case where the second operating system has started the same second vehicle-mounted application program as the first vehicle-mounted application program, the first operating system is closed;Wherein, the second operating system carries out safety check on preset target verification object during boot program starting process.Different vehicle-mounted application programs can be started by the first operating system and the second operating system, and the second operating system carries out safety check.The first operating system is closed after the same application program is started.Conflict is avoided, and user experience is improved.

Description

Technical Field

[0001] This invention relates to the field of intelligent vehicle technology, and in particular to a method, apparatus, electronic device, and storage medium for launching an in-vehicle application. Background Technology

[0002] In the current field of intelligent vehicles, intelligent vehicles generally need to be equipped with controllers with built-in high-computing-power SOC chips. The controllers run operating systems such as Linux, QNX, and AOS. As they are vehicle-mounted controllers, they need to meet extremely strict functional safety standards.

[0003] In the current technological field, security checks are performed on the system image file, file system, applications, and memory during system startup. Common operating systems typically take about 4-5 seconds for security checks during startup, about 1 second for kernel startup, about 6-7 seconds for hard disk initialization, file system startup, driver loading, and memory checks, and about 3 seconds for application startup. The entire system takes about 15 seconds from power-on to normal operation. However, functions such as holographic imaging and parking radar usually need to start within 6-7 seconds. Therefore, there is a conflict between the security checks of the vehicle controller and the need for fast application startup, resulting in a poor user experience. Summary of the Invention

[0004] This invention provides a method, apparatus, electronic device, and storage medium for launching in-vehicle applications, in order to resolve the conflict between the security verification of the in-vehicle controller and the application that needs to be launched quickly, resulting in a poor user experience.

[0005] According to one aspect of the present invention, a method for launching an in-vehicle application is provided, wherein the method includes:

[0006] After the vehicle is powered on, the virtualized first and second operating systems in the target controller are started;

[0007] The first in-vehicle application to be quickly launched in the target vehicle is launched through the first operating system, and the second in-vehicle application to be securely launched in the target vehicle is launched through the second operating system.

[0008] If the second operating system has already launched a second in-vehicle application that is the same as the first in-vehicle application, shut down the first operating system.

[0009] The second operating system performs security verification on the preset target verification object during the boot process.

[0010] According to another aspect of the present invention, a device for launching an in-vehicle application is provided, wherein the device comprises:

[0011] An operating system startup module is used to start the virtualized first and second operating systems in the target controller after the vehicle is powered on.

[0012] The vehicle application launch module is used to launch a first vehicle application to be launched quickly in the target vehicle through the first operating system, and to launch a second vehicle application to be launched securely in the target vehicle through the second operating system.

[0013] The first operating system shutdown module is used to shut down the first operating system when the second operating system has launched a second in-vehicle application that is the same as the first in-vehicle application.

[0014] The second operating system performs security verification on the preset target verification object during the boot process.

[0015] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0016] At least one processor; and

[0017] A memory communicatively connected to the at least one processor; wherein,

[0018] The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to execute the vehicle application launch method according to any embodiment of the present invention.

[0019] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the vehicle application startup method according to any embodiment of the present invention.

[0020] After the vehicle is powered on, the virtualized first and second operating systems in the target controller are started;

[0021] The first in-vehicle application to be quickly launched in the target vehicle is launched through the first operating system, and the second in-vehicle application to be securely launched in the target vehicle is launched through the second operating system.

[0022] If the second operating system has already launched a second in-vehicle application that is the same as the first in-vehicle application, shut down the first operating system.

[0023] The second operating system performs security verification on the preset target verification object during the boot process.

[0024] The technical solution of this invention involves, after the vehicle is powered on, starting a virtualized first operating system and a second operating system in the target controller; then, starting a first in-vehicle application to be quickly launched in the target vehicle through the first operating system, and starting a second in-vehicle application to be securely launched in the target vehicle through the second operating system; finally, after the second operating system has launched the second in-vehicle application, which is the same as the first in-vehicle application, shutting down the first operating system; wherein, the second operating system performs security verification on a preset target verification object during the boot process. This solves the problem of conflict between the security verification of the in-vehicle controller and the application that needs to be quickly launched. By having the virtualized first and second operating systems in the target controller run in parallel, the first operating system enables the quick launch of the in-vehicle application, while the second operating system enables the secure launch of the in-vehicle application. The first operating system is then shut down only after the in-vehicle application has been securely launched by the second operating system, thus avoiding conflicts between the security verification of the in-vehicle controller and the application that needs to be quickly launched, thereby improving the user experience.

[0025] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0026] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0027] Figure 1 This is a flowchart of a method for launching an in-vehicle application according to Embodiment 1 of the present invention;

[0028] Figure 2 This is a flowchart of a method for launching an in-vehicle application according to Embodiment 2 of the present invention;

[0029] Figure 3 A schematic diagram of a scenario for executing a vehicle application according to an embodiment of the present invention;

[0030] Figure 4 This is a schematic diagram of the structure of a vehicle application launch device according to Embodiment 3 of the present invention;

[0031] Figure 5This is a schematic diagram of the structure of an electronic device that implements the vehicle application launch method provided in Embodiment 4 of the present invention. Detailed Implementation

[0032] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0033] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0034] Example 1

[0035] Figure 1 The flowchart of a method for launching an in-vehicle application is provided in Embodiment 1 of the present invention. This embodiment is applicable to the launching of in-vehicle applications in smart vehicles. The method can be executed by an in-vehicle application launching device, which can be implemented in hardware and / or software and can be configured in a smart vehicle.

[0036] like Figure 1 As shown, the method includes:

[0037] S110. After the vehicle is powered on, start the virtualized first operating system and second operating system in the target controller.

[0038] In this context, the controller refers to a device configured on the target vehicle that can run an operating system. The target controller can be understood as a controller containing a virtualized first operating system and a second operating system. Virtualization refers to the technology of running multiple operating systems on the same hardware device, which can improve development efficiency and reduce maintenance costs. For example, the target controller may contain a high-performance SoC (System on Chip). In this embodiment, two target operating systems, namely a first operating system and a second operating system, can be virtualized on the SoC of the target controller. Optionally, the first operating system and the second operating system can be implemented based on the same type of operating system or based on different types of operating systems. For example, the operating system can be Linux, QNX, AOS, or similar types of operating systems. In this embodiment of the invention, to save development costs, the first operating system and the second operating system can also be implemented based on the same type of operating system.

[0039] Specifically, after the vehicle is powered on, the target controller is started and its virtualization program is run. Two identical operating systems, a first operating system and a second operating system, are then started on the target controller's main chip. In this embodiment, the first operating system does not perform security checks during the boot process and starts as quickly as possible. The second operating system is a secure bootable operating system that performs image and application verification during the boot process. It should be noted that the objects requiring security verification can be set according to actual needs and are not specifically limited here.

[0040] S120. Start the first in-vehicle application to be quickly started in the target vehicle through the first operating system, and start the second in-vehicle application to be safely started in the target vehicle through the second operating system.

[0041] In this context, the first in-vehicle application to be quickly launched in the target vehicle refers to an in-vehicle application that needs to be quickly launched through the first operating system. The second in-vehicle application to be securely launched in the target vehicle refers to an in-vehicle application that needs to be securely launched through the second operating system. It is understood that an in-vehicle application can be both a program requiring quick launch and an in-vehicle application requiring secure launch. In other words, an in-vehicle application can be written to both the first operating system and the second operating system simultaneously. In this embodiment, a system for quick launch (i.e., the first operating system) and a system for secure launch (i.e., the second operating system) are started. The first operating system ensures the quick launch of functions such as holographic imaging and parking radar. The second operating system ensures that the image, application, memory, etc., are securely verified to meet relevant functional safety requirements.

[0042] Optionally, the first in-vehicle application includes, but is not limited to: applications associated with image acquisition and / or applications associated with radar detection.

[0043] Optionally, the second in-vehicle application may include, but is not limited to, applications associated with software payment, applications associated with file storage, and applications associated with data access.

[0044] Optionally, launching the first in-vehicle application to be quickly launched in the target vehicle through the first operating system includes:

[0045] Using the first operating system, and following the preset startup process of the first operating system, the first in-vehicle application to be quickly launched in the target vehicle is started;

[0046] The preset startup process of the first operating system includes starting the boot program of the first operating system, loading the first image file and guiding the kernel of the first operating system to start, initializing the hard disk, mounting the first file system, loading the driver of the first vehicle application to be quickly started in the target vehicle, and starting the first vehicle application.

[0047] The bootloader of the first operating system refers to the program located on the target vehicle application that can boot the first operating system. The first image file refers to a file loaded into the first operating system that can compress a series of specific files into a single file according to a certain format for easy download and use by users. It can be recognized by specific software and directly burned onto a CD, and can contain a considerable amount of information. The kernel refers to the core of the first operating system, which can be expanded based on the first layer of hardware software, providing the most basic functions of the first operating system. It is the foundation for the operation of the first operating system and is responsible for managing system processes, memory, device drivers, files, and network systems. The hard disk refers to the primary storage device. The first file system refers to the file management system of the software structure responsible for managing and storing file information in the first operating system. The driver of the first in-vehicle application refers to the device driver, a special program that enables communication between the computer and the device.

[0048] Specifically, after the first operating system starts, the bootloader is started according to the preset boot process of the first operating system, the first image file is loaded, the kernel of the first operating system is booted, the hard disk is initialized, the first file system is mounted, the driver of the first in-vehicle application to be quickly launched in the target vehicle is loaded, and the first in-vehicle application is launched. Mounting the first file system refers to the process by which the first operating system makes the computer files and directories on the hard disk accessible to the user through the computer's first file system. Initializing the hard disk refers to importing or activating the hard disk.

[0049] For example, after virtualizing the first and second operating systems in the target controller, the first operating system performs a fast boot. The bootloader directly loads the system image and boots the kernel, initializes the hard disk, mounts the file system, loads drivers related to holographic imaging and radar functions, starts the first in-vehicle application to be quickly launched in the target vehicle, collects camera image data, and displays it on the display screen. Simultaneously with the first operating system's boot, the second operating system performs a secure boot. During the boot process, the bootloader performs security checks on the kernel image, applications, etc. After successful checks, it loads the image and starts the kernel, initializes the hard disk, mounts the file system, performs memory checks, and after successful checks, loads all system drivers, starts the second in-vehicle application to be securely launched in the target vehicle, and collects camera image data. The camera is used to collect graphic data around the vehicle, and both the first and second operating systems can drive the camera. The display screen is used to display the scene around the vehicle, and both the first and second in-vehicle applications can display the data collected by the camera on the display screen.

[0050] S130. If the second operating system has launched the same second vehicle application as the first vehicle application, shut down the first operating system.

[0051] Specifically, after the second operating system has launched the same second in-vehicle application as the first in-vehicle application, the second in-vehicle application sends an operating system switching command to the first in-vehicle application. The first in-vehicle application stops sending image data to the display screen, the second in-vehicle application displays the collected data on the display screen, and the first in-vehicle application controls the first operating system to shut down and release resources.

[0052] Optionally, shutting down the first operating system when the second operating system has launched the same second in-vehicle application as the first in-vehicle application includes: when the second operating system has launched the same second in-vehicle application as the first in-vehicle application, sending a system switching command from the second in-vehicle application to the first in-vehicle application to stop the first in-vehicle application from controlling the program response device, using the second in-vehicle application to control the program response device, and shutting down the first operating system through the second in-vehicle application.

[0053] The second operating system performs security verification on the preset target verification object during the boot process.

[0054] The technical solution of this invention involves, after the vehicle is powered on, starting a virtualized first operating system and a second operating system in the target controller; then, starting a first in-vehicle application to be quickly launched in the target vehicle through the first operating system, and starting a second in-vehicle application to be securely launched in the target vehicle through the second operating system; finally, after the second operating system has launched the second in-vehicle application, which is the same as the first in-vehicle application, shutting down the first operating system; wherein, the second operating system performs security verification on a preset target verification object during the boot process. This solves the problem of conflict between the security verification of the in-vehicle controller and the application that needs to be quickly launched. It enables the virtualized first and second operating systems in the target controller to run in parallel, achieving quick launch of the in-vehicle application through the first operating system and secure launch of the in-vehicle application through the second operating system, and shutting down the first operating system only after the in-vehicle application has been securely launched by the second operating system. This avoids the conflict between the security verification of the in-vehicle controller and the application that needs to be quickly launched, thus improving the user experience.

[0055] Example 2

[0056] Figure 2 This is a flowchart of a method for launching an in-vehicle application according to Embodiment 2 of the present invention. The difference between this embodiment and the previous embodiment lies in the detailed explanation of how to launch the second in-vehicle application to be securely launched in the target vehicle via the second operating system. For example... Figure 2 As shown, the method includes:

[0057] S210. After the vehicle is powered on, start the virtualized first operating system and second operating system in the target controller.

[0058] S220. Start the first in-vehicle application to be quickly launched in the target vehicle through the first operating system.

[0059] S230. Using the second operating system, the second in-vehicle application to be safely started in the target vehicle is launched according to the preset startup process of the second operating system.

[0060] The preset startup process of the second operating system includes starting the boot program, performing security verification on the preset target verification object during the boot program startup process, loading the second image file and booting the kernel of the second operating system, initializing the hard disk, mounting the second file system, loading the driver of the second vehicle application to be securely started in the target vehicle, and starting the second vehicle application.

[0061] The bootloader of the second operating system refers to the program located on the target vehicle application that can boot the second operating system. The second image file refers to a file loaded into the second operating system that can compress a series of specific files into a single file according to a certain format for easy download and use by users. It can be recognized by specific software and directly burned to a CD, and can contain a considerable amount of information. The kernel refers to the core of the second operating system, which can be expanded based on the first layer of hardware software, providing the most basic functions of the second operating system. It is the foundation for the operation of the second operating system and is responsible for managing system processes, memory, device drivers, files, and network systems. The hard disk refers to the primary storage device. The second file system refers to the file management system of the software organization responsible for managing and storing file information in the second operating system. The driver of the second in-vehicle application refers to the device driver, a special program that enables communication between the computer and the device.

[0062] The preset target verification object can be understood as a pre-defined application that needs to be verified in the second operating system. It should be noted that the applications requiring verification can be pre-set in the second operating system according to actual needs, and are not specifically limited here. Optionally, the preset target verification object includes, but is not limited to, the second image file to be loaded and the second in-vehicle application to be securely started.

[0063] Specifically, after the second operating system starts, the bootloader is started through the boot process preset by the second operating system. During the boot process, the preset target verification object is security verified. If the security verification passes, the second image file is loaded, the kernel of the second operating system is booted, the hard disk is initialized, the second file system is mounted, the driver of the second vehicle application to be quickly started in the target vehicle is loaded, and the second vehicle application is started.

[0064] Mounting the second file system refers to the process by which the second operating system makes computer files and directories on the hard disk accessible to users through the computer's second file system. Initializing the hard disk refers to importing or activating the hard disk. The bootloader starts simultaneously with the security verification of the preset target verification object.

[0065] If the security verification fails, a first message is generated to indicate the failure. Specifically, the first message may display a preset target verification object that failed the security verification, allowing the user to troubleshoot the problem and promptly fix the preset target verification object.

[0066] Optionally, after initializing the hard disk and mounting the second file system, and before loading the driver for the second in-vehicle application to be securely booted in the target vehicle, the method further includes:

[0067] A memory test is performed on the second operating system. If the test passes, the driver for loading the second in-vehicle application to be safely started in the target vehicle is executed.

[0068] Specifically, after starting the bootloader, performing security verification on the preset target verification object, loading the second image file and booting the kernel of the second operating system, initializing the hard disk, and mounting the second file system, some resources of the second operating system are already occupied. Loading the driver for the second in-vehicle application to be securely started in the target vehicle also requires resources from the second operating system. Therefore, memory testing of the second operating system is necessary. Optionally, memory testing of the second operating system can be performed multiple times during the production process, detecting the resource usage rate of loading the driver for the second in-vehicle application and the maximum memory required to start the second in-vehicle application, preventing resource usage from exceeding the limits of the second operating system. It is also necessary to test the second operating system resources under extreme conditions, such as when memory resources are consumed by other applications and the program runs for a long time. If the memory test passes, it means that the resources used do not exceed the limits of the second operating system, and the operation of loading the driver for the second in-vehicle application to be securely started in the target vehicle is executed. If the memory test fails, it means that the resources used exceed the limits of the second operating system, and the operation of loading the driver for the second in-vehicle application to be securely started in the target vehicle cannot be executed. In this case, a second message indicating memory verification failure can be generated. This allows users to optimize memory resource configuration based on the second prompt information.

[0069] S240. If the second operating system has launched the same second vehicle application as the first vehicle application, shut down the first operating system.

[0070] The technical solution of this invention involves, after the vehicle is powered on, starting a virtualized first operating system and a second operating system in the target controller; then, starting a first in-vehicle application to be quickly launched in the target vehicle through the first operating system; then, starting a second in-vehicle application to be quickly launched in the target vehicle through the second operating system according to its preset startup process; finally, shutting down the first operating system when the second in-vehicle application, which is the same as the first in-vehicle application, has already been launched. This avoids conflicts between the security verification of the in-vehicle controller and applications requiring quick launch. It enables the first in-vehicle application to launch according to the preset startup process of the first operating system, and the second in-vehicle application to launch according to the preset startup process of the second operating system. When two applications are already launched, the first operating system is shut down. This achieves both security verification for applications with security requirements and quick launch for applications with quick launch needs, avoiding conflicts between security and user experience.

[0071] Figure 3 This is a schematic diagram illustrating a scenario for launching an in-vehicle application according to an embodiment of the present invention. Taking the launch of a holographic image and parking radar function of a target vehicle as an example, the launching method of the in-vehicle application in this embodiment of the present invention will be described. Wherein, the first operating system is represented by operating system B, the second system by operating system A, the first in-vehicle application by application 2, and the second in-vehicle application, which is the same as the first in-vehicle application, by application 1.

[0072] like Figure 3As shown, after the vehicle is powered on, the target controller is initialized. Further, the target controller virtualization program runs, booting two identical operating systems (such as Linux), Operating System B and Operating System A, on the controller's main chip. The target controller includes intelligent driving-related software, such as image acquisition and radar. Virtualization is a technology that runs multiple operating systems on the same hardware device. The target controller contains a high-computing-power SOC chip, providing hardware support for virtualization. For example, two target operating systems can be virtualized on the SOC chip of the intelligent driving controller. Operating System A is a secure bootable operating system, typically performing image and application verification during the boot process, which is the most time-consuming part. Operating System B is the same type of operating system as Operating System A, but unlike Operating System A, Operating System B does not perform security verification during its boot process, booting at the fastest speed.

[0073] Specifically, operating system B performs an insecure boot and, according to the preset fast boot process of operating system B, launches application 2, which is related to the holographic imaging and radar functions in the target vehicle. The fast boot process includes the bootloader directly loading the system image and booting the kernel, initializing the hard disk, mounting the file system, loading the drivers that application 2 depends on, launching application 2, collecting camera image data, and displaying it on the display screen. At this time, the holographic imaging and parking radar functions are activated.

[0074] While operating system B starts booting, operating system A performs a secure boot, following its preset secure boot process. Application 1, related to holographic imaging and radar functions, is launched. During the boot process, the kernel image and applications undergo security verification. If verification passes, the image is loaded and the kernel is started. The hard drive is initialized, the file system is mounted, and memory is checked. If the check is successful, all system drivers are loaded, application 1 is launched, and camera image data is acquired. In this embodiment, application 1 and application 2 are the same program, burned to operating systems A and B respectively. The camera is used to acquire image data around the target vehicle; both operating systems A and B can drive the camera. The display screen is used to display the acquired image data; both application 1 and application 2 can display the data acquired by the camera. Finally, with application 1 (the same as application 2) already running on operating system A, the camera data is acquired, and the system takes over the functions of the vehicle's holographic imaging and parking radar. Application 1 sends an operating system switching command (e.g., a shutdown command) to application 2. Application 2 stops sending image data to the display screen, application 1 displays the acquired data, and application 2 controls operating system B to shut down and release resources.

[0075] The technical solution of this invention virtualizes two identical operating systems, a first operating system and a second operating system, running the same applications, a second vehicle application and a second vehicle application, thereby improving development efficiency and reducing maintenance costs. It initiates a fast-start system and a secure-start system. The fast-start system ensures the rapid startup of functions such as holographic imaging and parking radar. The secure-start system ensures that the image, applications, memory, etc., have undergone security verification to meet relevant functional safety requirements.

[0076] Example 3

[0077] Figure 4 This is a schematic diagram of a vehicle application launch device provided in Embodiment 3 of the present invention. Figure 4 As shown, the device includes: an operating system startup module 310, an in-vehicle application startup module 320, and a first operating system shutdown module 330.

[0078] The system includes an operating system startup module 310, which starts the virtualized first and second operating systems in the target controller after the vehicle is powered on; an in-vehicle application startup module 320, which starts the first in-vehicle application to be quickly started in the target vehicle through the first operating system, and starts the second in-vehicle application to be securely started in the target vehicle through the second operating system; and a first operating system shutdown module 330, which shuts down the first operating system when the second in-vehicle application, which is the same as the first in-vehicle application, has been started in the second operating system; wherein the second operating system performs security verification on a preset target verification object during the boot process.

[0079] The technical solution of this invention involves, after the vehicle is powered on, starting a virtualized first operating system and a second operating system in the target controller; then, starting a first in-vehicle application to be quickly launched in the target vehicle through the first operating system, and starting a second in-vehicle application to be securely launched in the target vehicle through the second operating system; finally, after the second operating system has launched the second in-vehicle application, which is the same as the first in-vehicle application, shutting down the first operating system; wherein, the second operating system performs security verification on a preset target verification object during the boot process. This solves the problem of conflict between the security verification of the in-vehicle controller and the application that needs to be quickly launched. It enables the virtualized first and second operating systems in the target controller to run in parallel, achieving quick launch of the in-vehicle application through the first operating system and secure launch of the in-vehicle application through the second operating system, and shutting down the first operating system only after the in-vehicle application has been securely launched by the second operating system. This avoids the conflict between the security verification of the in-vehicle controller and the application that needs to be quickly launched, thus improving the user experience.

[0080] Optionally, the in-vehicle application launch module 320 includes: a first in-vehicle application launch unit, used for...

[0081] Using the first operating system, and following the preset startup process of the first operating system, the first in-vehicle application to be quickly launched in the target vehicle is started;

[0082] The preset startup process of the first operating system includes starting the boot program of the first operating system, loading the first image file and guiding the kernel of the first operating system to start, initializing the hard disk, mounting the first file system, loading the driver of the first vehicle application to be quickly started in the target vehicle, and starting the first vehicle application.

[0083] Optionally, the vehicle application startup module 320 includes: a second vehicle application startup unit, used to start the second vehicle application to be safely started in the target vehicle through the second operating system according to the preset startup process of the second operating system;

[0084] The preset startup process of the second operating system includes starting the boot program, performing security verification on the preset target verification object during the boot program startup process, loading the second image file and booting the kernel of the second operating system, initializing the hard disk, mounting the second file system, loading the driver of the second vehicle application to be securely started in the target vehicle, and starting the second vehicle application.

[0085] Optionally, the vehicle application startup module 320 further includes: a second operating system memory detection unit, used to perform memory detection on the second operating system, and if the detection passes, to execute the operation of loading the driver of the second vehicle application to be safely started in the target vehicle.

[0086] Optionally, the preset target verification object includes:

[0087] The second image file to be loaded and the second in-vehicle application to be securely started.

[0088] Optionally, the first operating system shutdown module 330 includes: a first vehicle application stopping unit and a first operating system shutdown unit.

[0089] The first vehicle application stopping unit is used to stop the first vehicle application from controlling the program response device by sending a system switching command from the second vehicle application to the first vehicle application when the second operating system has launched a second vehicle application that is the same as the first vehicle application; the first operating system shutting down unit is used to control the program response device using the second vehicle application and shut down the first operating system through the second vehicle application.

[0090] Optionally, the first in-vehicle application includes: an application associated with image acquisition and / or an application associated with radar detection.

[0091] The vehicle application launch device provided in this embodiment of the invention can execute the vehicle application launch method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0092] Example 4

[0093] Figure 5 A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0094] like Figure 5As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0095] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0096] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the startup method of an in-vehicle application.

[0097] In some embodiments, the method for launching an in-vehicle application can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the method for launching an in-vehicle application described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to execute the method for launching an in-vehicle application by any other suitable means (e.g., by means of firmware).

[0098] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0099] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0100] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0101] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0102] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0103] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0104] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and no limitation is imposed herein.

[0105] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for launching an in-vehicle application, characterized in that, include: After the vehicle is powered on, the virtualized first and second operating systems in the target controller are started. The first operating system launches a first in-vehicle application in the target vehicle that needs to be launched quickly, and the second operating system launches a second in-vehicle application in the target vehicle that needs to be launched securely; wherein the first operating system and the second operating system are based on the same type of operating system; the first in-vehicle application and the second in-vehicle application are the same program, which is burned into the first operating system and the second operating system respectively; If the second operating system has already launched the same vehicle application as the first vehicle application, shut down the first operating system. The second operating system performs security verification on the preset target verification object during the boot process.

2. The method according to claim 1, characterized in that, The step of launching the first in-vehicle application to be quickly launched in the target vehicle through the first operating system includes: Using the first operating system, and following the preset startup process of the first operating system, the first in-vehicle application to be quickly launched in the target vehicle is started; The preset startup process of the first operating system includes starting the boot program of the first operating system, loading the first image file and guiding the kernel of the first operating system to start, initializing the hard disk, mounting the first file system, loading the driver of the first vehicle application to be quickly started in the target vehicle, and starting the first vehicle application.

3. The method according to claim 1, characterized in that, The step of launching the second in-vehicle application to be securely launched in the target vehicle through the second operating system includes: Using the second operating system, and following the preset startup process of the second operating system, the second in-vehicle application to be safely started in the target vehicle is launched; The preset startup process of the second operating system includes starting the boot program, performing security verification on the preset target verification object during the boot program startup process, loading the second image file and booting the kernel of the second operating system, initializing the hard disk, mounting the second file system, loading the driver of the second vehicle application to be securely started in the target vehicle, and starting the second vehicle application.

4. The method according to claim 3, characterized in that, After initializing the hard drive and mounting the second file system, and before loading the driver for the second in-vehicle application to be securely booted in the target vehicle, the process also includes: A memory test is performed on the second operating system. If the test passes, the driver for loading the second in-vehicle application to be safely started in the target vehicle is executed.

5. The method according to claim 3, characterized in that, The preset target verification object includes: The second image file to be loaded and the second in-vehicle application to be securely started.

6. The method according to claim 1, characterized in that, The step of shutting down the first operating system when the second operating system has already launched a second in-vehicle application that is the same as the first in-vehicle application includes: If the second operating system has launched the same second in-vehicle application as the first in-vehicle application, a system switching command is sent from the second in-vehicle application to the first in-vehicle application to stop the first in-vehicle application from controlling the program response device. The second in-vehicle application then controls the program response device and shuts down the first operating system.

7. The method according to claim 1, characterized in that, The first in-vehicle application includes: Applications associated with image acquisition and / or applications associated with radar detection.

8. A device for launching an in-vehicle application, characterized in that, include: The operating system startup module is used to start the virtualized first and second operating systems in the target controller after the vehicle is powered on. The vehicle application startup module is used to launch a first vehicle application to be quickly launched in the target vehicle through the first operating system, and to launch a second vehicle application to be safely launched in the target vehicle through the second operating system; wherein, the first operating system and the second operating system are based on the same type of operating system; the first vehicle application and the second vehicle application are the same program, respectively burned into the first operating system and the second operating system; the first operating system shutdown module is used to shut down the first operating system when the second operating system has launched the second vehicle application which is the same as the first vehicle application; The second operating system performs security verification on the preset target verification object during the boot process.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the method for launching the vehicle application according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed by a processor, implement the method for launching the vehicle application according to any one of claims 1-7.

Images