Multi-user vehicle-mounted operating system control method and device and vehicle machine

Abstract

The specification discloses a multi-user vehicle-mounted operating system control method, device and vehicle machine, and belongs to the field of intelligent vehicles. The method comprises the following steps: creating M first virtual machines one by one for M registered users in advance, and the virtualized hardware resources used by the M first virtual machines are isolated from each other; if the identity of a current driving user is identified, it is identified that the current driving user is a target registered user, a target virtual machine corresponding to the target registered user is determined from the M first virtual machines, and the target registered user belongs to the M registered users; and the target virtual machine is started so that the target virtual machine accesses the virtualized hardware resources allocated to the target virtual machine in an exclusive manner. The specification solves the technical problem of low privacy data security of a multi-user operating system in the prior art.

Description

TECHNICAL FIELD

[0001] The present specification relates to the field of intelligent vehicles, and in particular to a multi-user vehicle-mounted operating system control method and device and vehicle machine. BACKGROUND

[0002] With the development of intelligent vehicles, vehicles can collect more and more private information of driving users, including images, sounds, location information, motion trajectories, and the like. In a scenario in which multiple users use the same vehicle, such as a family sharing a vehicle, multiple employees sharing a vehicle, or lending a vehicle to others, the risk of mutual exposure of private data is caused.

[0003] As Figure 1 , the existing multi-user operating system technology is implemented under the same operating system. A user who obtains administrator permission can access all physical hardware, partitions, storage media, and the like. A user of the same operating system can easily obtain administrator permission and thus obtain access permission to all hardware resources, and can thus obtain private information of other users. It can be seen that the existing multi-user operating system technology has a risk of private data leakage and is not highly secure. SUMMARY

[0004] Embodiments of the present specification provide a multi-user vehicle-mounted operating system control method, device, and vehicle machine, which solve the technical problem of low private data security of the existing multi-user operating system.

[0005] In a first aspect, the embodiments of the present specification provide a multi-user vehicle-mounted operating system control method, including: performing identity recognition on a current driving user; if it is recognized that the current driving user is a target registered user, determining a target virtual machine corresponding to the target registered user from M first virtual machines, wherein the M first virtual machines are created in one-to-one correspondence for M registered users in advance, virtualized hardware resources used by the M first virtual machines are isolated from each other, and the target registered user belongs to one of the M registered users, and M is a positive integer; starting the target virtual machine to enable the target virtual machine to access virtualized hardware resources allocated to the target virtual machine in an exclusive manner.

[0006] Optionally, after the target virtual machine is started, the method further includes: during running of the target virtual machine, prohibiting starting of M-1 first virtual machines other than the target virtual machine in the M first virtual machines, and prohibiting access to a physical storage location of a client operating system of the M-1 first virtual machines.

[0007] Optionally, before the identity of the current driving user is identified, the method further comprises: triggering a virtual machine monitor to start based on a vehicle machine starting operation of the current driving user; starting a second virtual machine through the virtual machine monitor, the second virtual machine being different from the M first virtual machines; and identifying the current driving user through the second virtual machine.

[0008] Optionally, the identifying the current driving user through the second virtual machine comprises: obtaining user identity information of the current driving user through the second virtual machine; matching the user identity information of the current driving user with registered identity information of the M registered users respectively through the second virtual machine; if the user identity information matches the registered identity information of any one of the M registered users successfully, identifying the current driving user as a target registered user through the second virtual machine, and if the matching with the M registered users is all unsuccessful, identifying the current driving user as a non-registered user through the second virtual machine.

[0009] Optionally, the starting the target virtual machine comprises: if the current driving user is identified as a target registered user through the second virtual machine, sending a notification message carrying unique identification information of the current driving user to the virtual machine monitor through the second virtual machine; determining the unique identification information of the current driving user from the notification message through the virtual machine monitor; obtaining a physical storage address of a client operating system of the target virtual machine according to the unique identification information through the virtual machine monitor; and starting the client operating system of the target virtual machine and loading usage data of the target registered user into memory according to the physical storage address of the client operating system through the virtual machine monitor.

[0010] Optionally, after the target virtual machine is started, the method further comprises: calling device usage permissions of the target registered user through the target virtual machine; and limiting usage ranges of various vehicle devices of the target registered user based on the device usage permissions.

[0011] Optionally, after the starting the client operating system of the target virtual machine and the loading the usage data of the target registered user into memory, the method further comprises: obtaining usage state information of the target registered user at the end of previous usage of the vehicle from the usage data of the target registered user through the target virtual machine; and restoring usage states of vehicle devices and vehicle-mounted applications according to the usage state information.

[0012] Optionally, after the second virtual machine identifies the current driving user as a non-registered user, the method further comprises: if the first virtual machine identifies the current driving user as a non-registered user, prohibiting the engine of the vehicle from starting.

[0013] In a second aspect, the embodiments of the present specification provide a multi-user vehicle-mounted operating system control device, comprising: an identity identification unit configured to identify a current driving user; a virtual machine determination unit configured to determine a target virtual machine corresponding to a target registered user from M first virtual machines if the current driving user is identified as the target registered user, wherein the M first virtual machines are created in one-to-one correspondence for M registered users in advance, virtualized hardware resources used by the M first virtual machines are isolated from each other, and the target registered user belongs to one of the M registered users, and M is a positive integer; and a first virtual machine starting unit configured to start the target virtual machine, so that the target virtual machine accesses virtualized hardware resources allocated to the target virtual machine in an exclusive manner.

[0014] In a third aspect, the embodiments of the present specification provide a car machine, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the method of any of the embodiments of the first aspect when executing the program.

[0015] In a fourth aspect, the embodiments of the present specification provide a computer readable storage medium having a computer program stored thereon, and the program is executed by a processor to implement the steps of the method of any of the embodiments of the first aspect.

[0016] The one or more technical solutions provided by the embodiments of the present specification have at least the following technical effects or advantages:

[0017] The multi-user operating system control method provided by the embodiments of the present specification creates M first virtual machines in one-to-one correspondence for M registered users in advance, and virtualized hardware resources used by the M first virtual machines are isolated from each other, so that the virtual machines cannot access virtualized hardware resources allocated to other virtual machines, and the virtualization technology is used to isolate information. On this basis, the current driving user is identified; if the current driving user is identified as a target registered user, a target virtual machine corresponding to the target registered user is determined from the M first virtual machines created in advance, and the target virtual machine is started, so that the target virtual machine accesses virtualized hardware resources allocated to the target virtual machine in an exclusive manner. Thus, the current driving user cannot access virtualized hardware resources of a virtual machine corresponding to another driving user, and further, the current driving user cannot obtain private data of another driving user, thereby improving the privacy data security of the multi-user operating system. BRIEF DESCRIPTION OF DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present specification, the following will briefly introduce the drawings needed to be used in the embodiments description. Obviously, the drawings in the following description are some embodiments of the present specification, and other drawings can also be obtained by those of ordinary skill in the art without any creative effort based on these drawings.

[0019] Figure 1 The system architecture of the multi-user operating system in the prior art is shown;

[0020] Figure 2 The flow chart of the multi-user vehicle-mounted operating system control method in the embodiments of the present specification is shown;

[0021] Figure 3 The system architecture of the multi-user vehicle-mounted operating system in the embodiments of the present specification is shown;

[0022] Figure 4 The execution logic of the multi-user vehicle-mounted operating system control method in the embodiments of the present specification is shown;

[0023] Figure 5 The structure of the multi-user vehicle-mounted operating system control device in the embodiments of the present specification is shown;

[0024] Figure 6 The structure of the vehicle machine in the embodiments of the present specification is shown. DETAILED DESCRIPTION

[0025] The embodiments of the present specification provide a multi-user vehicle-mounted operating system control method, which solves the technical problem of low privacy data security of the multi-user operating system in the prior art. The technical solution provided by the embodiments of the present specification is as follows to solve the above technical problem:

[0026] M first virtual machines are created one by one for M registered users in advance, and the virtualized hardware resources used by the M first virtual machines are configured to be isolated from each other, so that the virtualized hardware resources are inaccessible between the virtual machines, thereby realizing isolation of information by using virtualization technology. On this basis, the current driving user is identified; if it is identified that the current driving user is a target registered user, a target virtual machine corresponding to the target registered user is determined from the M first virtual machines created in advance, and the target virtual machine is started to enable the target virtual machine to access the virtualized hardware resources allocated to the target virtual machine in an exclusive manner. The current driving user cannot access the virtualized hardware resources allocated to other virtual machines, and thus cannot obtain the privacy data of other driving users, avoiding the risk of mutual exposure of the privacy data of different driving users, and improving the privacy data security of the multi-user operating system.

[0027] To better understand the above technical solutions, the following will provide a detailed explanation of the technical solutions in conjunction with the accompanying drawings and specific implementation methods.

[0028] First, it should be clarified that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0029] This specification provides an embodiment of a multi-user vehicle operating system control method, applied to a vehicle operating system that supports multi-user login. (See reference...) Figure 2 As shown, the multi-user vehicle operating system control method includes at least the following steps S101 to S103:

[0030] S101. Identify the current driver.

[0031] It should be understood that the current driver can be identified through a second virtual machine. The second virtual machine is a virtual machine that is different from the M first virtual machines that are created in advance to correspond one-to-one with the M registered users. The virtualization hardware resources used by the second virtual machine and the M first virtual machines are isolated from each other and cannot be accessed by each other. M is a positive integer.

[0032] To identify the current driver through a second virtual machine, a virtual machine monitor (VMM, also known as a hypervisor) is started based on the driver's vehicle infotainment system activation operation before the identification process. The hypervisor is virtual machine software based on armv8, armv9, or x86 architectures. It operates at the EL2 privilege level, and the operating system software (OS) of each virtual machine runs on top of the hypervisor. This allows the hypervisor to control the startup and shutdown of the guest operating systems of each virtual machine and the access permissions of each virtual machine to various hardware components.

[0033] It should be noted that after the virtual machine monitor is started, the second virtual machine is then started through the virtual machine monitor; the identity of the current driver is then identified through the second virtual machine.

[0034] In some embodiments, the identity recognition of the current driving user by the second virtual machine comprises: obtaining, by the second virtual machine, user identity information of the current driving user; matching, by the second virtual machine, the user identity information of the current driving user with the registered identity information of the M registered users respectively; if the user identity information of the current driving user matches the registered identity information of any one of the M registered users successfully, the second virtual machine identifies the current driving user as the target registered user, and if the user identity information of the current driving user does not match the registered identity information of the M registered users successfully, the second virtual machine identifies the current driving user as a non-registered user.

[0035] For example, if the user identity information of the current driving user matches the registered identity information of the registered user A successfully, the second virtual machine identifies the current driving user as the registered user A; if the user identity information of the current driving user matches the registered identity information of the registered user B successfully, the second virtual machine identifies the current driving user as the registered user B; if the user identity information of the current driving user matches the registered identity information of the registered user C successfully, the second virtual machine identifies the current driving user as the registered user C; and if the user identity information of the current driving user does not match the registered identity information of the registered users A, B and C successfully, the second virtual machine identifies the current driving user as a non-registered user.

[0036] Specifically, the second virtual machine can obtain the user identity information of the current driving user in various ways, and the obtained user identity information includes but is not limited to one or more of the following types of information of the current driving user: biological information, electronic information and physical information, wherein each type of information can include one or more specific information. The biological information can include one or more of the following: face, fingerprint, iris, voiceprint, etc., the electronic information can include one or more of the following: electronic key, various electronic tags (Active tag), personal password, etc., and the physical information can include one or more of the following: mechanical key, etc.

[0037] S102, if the current driving user is identified as the target registered user, a target virtual machine corresponding to the target registered user is determined from the M first virtual machines, wherein the M first virtual machines are created one-to-one for the M registered users in advance, the virtualized hardware resources used by the M first virtual machines are isolated from each other, and the target registered user belongs to one of the M registered users, and M is a positive integer.

[0038] It should be understood that the technical solutions provided by the embodiments of the present specification do not require an additional MCU (Micro Control Unit) or a specially designated CPU, but only a CPU supporting virtualization.

[0039] Reference Figure 3 As shown, the M first virtual machines and the second virtual machine created by the virtualization technology are mutually isolated in the use of virtualized hardware resources, so that the M first virtual machines and the second virtual machine are not allowed to access the virtualized hardware resources allocated to other virtual machines, cutting off the channel for hackers or viruses to copy and modify the use data of other virtual machines from a virtual machine. In the specific implementation process, the various hardware resources isolated from each other include but are not limited to hard disks, floppy disks, U disks, optical disks, and some rare storage media (such as EEPROM, PLA), as long as the hardware resources accessed through the CPU data bus can be isolated.

[0040] It can be understood that in order to isolate the hardware resources used by the M first virtual machines and the second virtual machine from each other, it can be implemented based on a single-chip SOC (System-on-a-Chip, system-level chip), or based on two or more storage chips, including but not limited to UFS (Universal Flash Storage, universal flash storage) FLASH chip, EMMC (Embedded Multi Media Card, embedded multimedia card) FLASH chip, NVME (Nonvolatile memory express, non-volatile fast memory) FLASH chip.

[0041] It can be that different virtual machines in the second virtual machine and the M first virtual machines correspondingly use different storage chips to achieve the purpose of isolating the virtualized hardware resources used by each other. It can also be that different virtual machines in the second virtual machine and the M first virtual machines correspondingly use different partitions of the same storage chip to achieve the purpose of isolating the virtualized hardware resources.

[0042] In the specific implementation process, the partition information or hardware address information of each virtual machine can be configured to be invisible to other virtual machines by the virtual machine monitor, so as to isolate the hardware resources used by each virtual machine from each other. Reference Figure 3 As shown, taking the first virtual machines VM1, VM2, and VM3 corresponding to the registered users A, B, and C as examples, the virtual machine VM1 has a client operating system OS1, the virtual machine VM2 has a client operating system OS2, and the virtual machine VM3 has a client operating system OS3: The partition information or hardware address information of VM1 is configured by the Hypervisor to be invisible to VM0, VM2, and VM3; the partition information or hardware address information of VM2 is invisible to VM0, VM1, and VM3; and the partition information or hardware address information of VM3 is invisible to VM0, VM1, and VM2.

[0043] S103, start the target virtual machine, so that the target virtual machine accesses the virtualized hardware resources allocated to the target virtual machine in an exclusive manner.

[0044] A one-to-one correspondence between the unique identification information of each registered user and the physical storage address of the client operating system is established in advance in the virtual machine monitor. If the current driving user is identified as the target registered user by the second virtual machine, a notification message is sent by the second virtual machine to the virtual machine monitor, the notification message carrying the unique identification information of the target registered user. The unique identification information of the target registered user is determined by the virtual machine monitor according to the received notification message. The physical storage address of the client operating system of the target virtual machine is obtained by the virtual machine monitor according to the unique identification information of the target registered user. The virtual machine monitor guides the start of the client operating system of the target virtual machine and the use data of the target registered user to the memory according to the physical storage address of the client operating system of the target virtual machine.

[0045] It should be noted that the virtualized hardware resources are the hardware resources of the vehicle machine that are virtually allocated to the virtual machines. The second virtual machine and the M first virtual machines created in the embodiment of the application are all EL0 permission levels. The physical storage location of the client operating system of each virtual machine is accessed in an exclusive manner. That is, for any one of the second virtual machine and the M first virtual machines, vm i , the physical storage address of the client operating system of the virtual machine vm i can only be accessed by the virtual machine vm i itself, and other virtual machines except the virtual machine vm i are prohibited from accessing the physical storage address.

[0046] During the running process after the start of the target virtual machine, the M-1 first virtual machines except the target virtual machine among the M first virtual machines are prohibited from starting, and the physical storage location of the client operating system corresponding to each of the M-1 first virtual machines is prohibited from being accessed. Therefore, even if the current driving user obtains EL1 permission (i.e. root permission), the current driving user cannot obtain the data of other driving users through full memory scanning or hard disk scanning, thereby reducing the risk of exposure of private data between different driving users. The safety of private data such as driving time, geographic location information, driving record, camera video and photo, microphone recording of the driver is maximized.

[0047] It can be understood that after the target virtual machine is started, the device usage permission of the target registered user is invoked through the target virtual machine; and based on the device usage permission of the target registered user, the use range of various vehicle devices by the target registered user is limited.

[0048] It should be noted that the vehicle devices include various vehicle-mounted electrical equipment, seat functions, trunk, and the like, which serve as additional functions, wherein the electrical equipment specifically includes audio, cigarette lighter, air conditioner, lighting, camera, and the like.

[0049] For example, the device usage permission corresponding to a registered user A is that the camera is prohibited from being used, the trunk is prohibited from being opened, and the seat is prohibited from being heated. If it is identified that the current driving user is the registered user A, then based on the device usage permission of the registered user A, the use range of various vehicle devices by the current driving user is limited, so that the current driving user can use other vehicle devices and their functions except the camera, the trunk, and the heated seat.

[0050] It can be understood that according to the identity authentication of the current driving user, customized configuration services conforming to the current driving user can also be provided. Specifically, after the operating system of the target virtual machine is started and the usage data of the target registered user is introduced into the memory, the target virtual machine obtains the usage state information of the target registered user at the end of the last use of the vehicle from the usage data of the target registered user; and according to the obtained usage state information, the vehicle is restored to the state of the target registered user at the end of the last use of the vehicle.

[0051] The usage state information includes the state information of the vehicle devices and / or vehicle-mounted applications, the state information of the vehicle devices includes the state information of the seat position, the mirror position, and the like at the end of the last use of the vehicle, and the state information of the vehicle-mounted applications includes personal cabin configuration information (such as video playback progress, music playback progress, and the like) and login information of various third-party APPs, and the like. According to the usage state information, the seat position, the mirror position, the video playback progress, the music playback progress, and the like are adjusted, and according to the login information of the third-party APPs, the corresponding third-party APPs are automatically logged in. Thus, customized configuration services can be provided for the current driving user, and the driving user experience is improved.

[0052] It can be understood that if the first virtual machine identifies the current driving user as a non-registered user, the engine of the vehicle is prohibited from being started, so as to improve the safety of the vehicle.

[0053] In order to more clearly understand the multi-user vehicle-mounted operating system control method provided by the embodiments of the present application, the following is an example of a virtual machine VM0 for identity authentication, and a virtual machine VM1 (corresponding to registered user A), VM2 (corresponding to registered user B), and VM3 (corresponding to registered user C) that are created in one-to-one correspondence for registered users A, B, and C, respectively, with reference to Figure 4 An execution logic of the multi-user vehicle-mounted operating system control method in the embodiments of the present application is given as follows:

[0054] S1: The driving user X triggers the start, and triggers the Hypervisor to start.

[0055] S2: After the Hypervisor starts, the Hypervisor guides the VM0 for identity authentication to start.

[0056] S3: After the VM0 starts, the VM0 collects the biological information, electronic information, and physical information of the driving user X and submits them to the authentication center of the VM0, and the authentication center of the VM0 identifies the driving user X according to the biological information, electronic information, and physical information of the driving user X; if the driving user X is identified as a certain registered user (A or B or C), step S4 is executed; if the driving user X is identified as a non-registered user, step S4' is executed: the engine of the vehicle is prohibited from starting.

[0057] S4: The VM0 sends a notification message to the Hypervisor, and the notification message carries the unique identification information of the driving user X.

[0058] S5: The Hypervisor guides the client operating system OS of the virtual machine created for the driving user X in the VM1, VM2, and VM3 to start according to the unique identification information, and guides the usage data of the driving user X to the memory. For example, if the driving user X is the registered user A, the client operating system OS1 of the virtual machine VM1 is guided to start, and the usage data of the registered user A is guided to the memory.

[0059] S6: The client operating system OS of the virtual machine created for the driving user X automatically acquires the device usage permission of the driving user X to the vehicle, and limits the usage range of the driving user X to the devices of the vehicle according to the device usage permission.

[0060] S7: The client operating system OS of the virtual machine created for the driving user X retains the usage state information of the driving user X when the driving user X uses the vehicle last time, and the client operating system OS restores the vehicle to the state of the driving user X when the driving user X ends the last use of the vehicle according to the usage state information.

[0061] Based on the same inventive concept, the embodiments of the present application provide a multi-user vehicle-mounted operating system control device, with reference to Figure 5As shown, the multi-user vehicle-mounted operating system control apparatus comprises: an identity recognition unit 501 configured to recognize the current driving user; a virtual machine determination unit 502 configured to determine a target virtual machine corresponding to a target registered user from M first virtual machines if the current driving user is identified as the target registered user, wherein the M first virtual machines are created in one-to-one correspondence with M registered users in advance, virtualized hardware resources used by the M first virtual machines are isolated from each other, and the target registered user belongs to one of the M registered users; and a first virtual machine starting unit 503 configured to start the target virtual machine to enable the target virtual machine to access virtualized hardware resources allocated to the target virtual machine in an exclusive manner.

[0062] It can be understood that, in some embodiments, the multi-user vehicle-mounted operating system control apparatus further comprises a disabling unit configured to disable M-1 first virtual machines other than the target virtual machine among the M first virtual machines from starting and to disable access to physical storage locations of client operating systems of the M-1 first virtual machines during running of the target virtual machine.

[0063] It can be understood that, in some embodiments, the multi-user vehicle-mounted operating system control apparatus further comprises: a monitor starting unit configured to trigger starting of a virtual machine monitor based on a vehicle-machine starting operation of the current driving user; a second virtual machine starting unit configured to start a second virtual machine through the virtual machine monitor, the second virtual machine being different from the M first virtual machines; and the identity recognition unit 501, in particular, configured to recognize the current driving user through the second virtual machine.

[0064] It can be understood that, in some embodiments, the identity recognition unit 501 is in particular configured to: acquire user identity information of the current driving user through the second virtual machine; match the user identity information of the current driving user with registered identity information of the M registered users through the second virtual machine; if the user identity information matches the registered identity information of any one of the M registered users successfully, the second virtual machine identifies the current driving user as the target registered user, and if the matching with the M registered users is all unsuccessful, the second virtual machine identifies the current driving user as a non-registered user.

[0065] Understandably, in some implementations, the first virtual machine startup unit 503 includes: a notification subunit, configured to send a notification message to the virtual machine monitor if the second virtual machine identifies the current driving user as the target registered user, the notification message carrying the unique identification information of the current driving user; an identification determination subunit, configured to determine the unique identification information of the current driving user from the notification message through the virtual machine monitor; an address acquisition subunit, configured to obtain the physical storage address of the guest operating system of the target virtual machine by the virtual machine monitor based on the unique identification information; and a boot subunit, configured to boot the guest operating system of the target virtual machine and load the usage data of the target registered user into memory by the virtual machine monitor based on the physical storage address of the guest operating system.

[0066] It is understood that, in some implementations, a restriction unit is also included, used to: after the target virtual machine is started, retrieve the device usage permissions of the target registered user through the target virtual machine; and based on the device usage permissions, restrict the scope of use of various vehicle devices by the target registered user.

[0067] It is understood that, in some implementations, a configuration recovery unit is also included, used to: after the guest operating system that boots the target virtual machine starts and the usage data of the target registered user is loaded into memory, the target virtual machine obtains the usage status information of the target registered user at the end of the last use of the vehicle from the usage data of the target registered user; and restore the usage status of the vehicle device and the in-vehicle application according to the usage status information.

[0068] It is understood that, in some implementations, the system further includes a start-prevention unit, which is used to prevent the vehicle's engine from starting if the first virtual machine identifies the current driver as an unregistered user after the second virtual machine identifies the current driver as an unregistered user.

[0069] Regarding the above-mentioned device, the specific functions of each unit have been described in detail in the multi-user vehicle operating system control method provided in the embodiments of this specification, and will not be elaborated here.

[0070] Based on the same inventive concept, this specification also provides an in-vehicle infotainment system, such as... Figure 6 As shown, it includes a memory 604, a processor 602, and a computer program stored in the memory 604 and executable on the processor 602. When the processor 602 executes the program, it implements the steps described in any of the embodiments of the multi-user vehicle operating system control method described above.

[0071] wherein, in Figure 6 The bus architecture, represented by the bus 600, can include any number of interconnected buses and bridges, the bus 600 interconnects various circuits including the one or more processors represented by the processor 602 and the memory represented by the memory 604. The bus 600 can also interconnect various other circuits, such as peripheral devices, voltage stabilizers and power management circuits, which are well known in the art and thus, not further described herein. The bus interface 606 provides an interface between the bus 600 and the receiver 601 and the transmitter 603. The receiver 601 and the transmitter 603 can be the same element, i.e. a transceiver, providing a means for communicating with various other apparatuses over a transmission medium. The processor 602 is responsible for managing the bus 600 and general processing, while the memory 604 can be used for storing data used by the processor 602 in executing operations.

[0072] In a fourth aspect, based on the same inventive concept, the specification further provides a computer readable storage medium, having stored thereon a computer program, which when executed by a processor implements the method steps of any of the method embodiments of the end-side task scheduling method as described above.

[0073] The specification is described with reference to flow diagrams and / or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the specification. It will be understood that each block of the flow diagrams and / or block diagrams, and combinations of blocks in the flow diagrams and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flow diagrams and / or block diagrams block or blocks. Figure 1 The flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams illustrate the functions specified in the flow diagrams and / or block diagrams by one or more flows and / or blocks. Figure 1 The flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams illustrate the functions specified in the flow diagrams and / or block diagrams by one or more flows and / or blocks.

[0074] These computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including an instruction apparatus that implements the flow diagrams and / or block diagrams flow or flows and / or block or blocks specified in the flow diagrams and / or block diagrams. Figure 1 The flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams illustrate the functions specified in the flow diagrams and / or block diagrams by one or more flows and / or blocks. Figure 1 The flow diagrams and / or block diagrams in the flow diagrams and / or block diagrams illustrate the functions specified in the flow diagrams and / or block diagrams by one or more flows and / or blocks.

[0075] These computer program instructions can also be loaded into a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 These computer program instructions can also be loaded into a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 These computer program instructions can also be loaded into a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.

[0076] Although preferred embodiments of the present specification have been described, those skilled in the art who have the benefit of the present specification can make additional changes and modifications to these embodiments once the basic inventive concept is appreciated. Therefore, it is intended that the appended claims be construed to include all alternatives falling within the scope of the present specification.

[0077] Obviously, various modifications and changes are possible in the present specification without departing from the scope and spirit of the present specification. Accordingly, the present specification is also intended to include within its scope all such modifications and changes as fall within the scope of the claims and their equivalents.

Claims

1. A multi-user vehicle operating system control method, characterized in that, The method is applied to a multi-user in-vehicle operating system, which includes M first virtual machines, second virtual machines, a virtual machine monitor, and virtualized hardware resources corresponding one-to-one with the M first virtual machines. The current driver triggers the power-on process, starting the virtual machine monitor; The virtual machine monitor guides the second virtual machine to start, and the second virtual machine identifies the current driver based on the unique identifier information of the current driver. If the second virtual machine identifies the current driving user as the target registered user, it determines the target virtual machine corresponding to the target registered user from the M first virtual machines. The M first virtual machines are pre-created one-to-one for the M registered users. The second virtual machine and the M+1 virtualization hardware resources corresponding to the M first virtual machines are isolated from each other. The target registered user belongs to one of the M registered users, and M is a positive integer. Start the target virtual machine so that the target virtual machine can exclusively access the virtualization hardware resources allocated to the target virtual machine. During the operation of the target virtual machine, start the M-1 first virtual machines other than the target virtual machine among the M first virtual machines. If the second virtual machine identifies the current driving user as an unregistered user, it will prevent the vehicle's engine from starting.

2. The method as described in claim 1, characterized in that, After starting the target virtual machine, the following is also included: During the operation of the target virtual machine, access to the physical storage location of the guest operating system of the M-1 first virtual machines is prohibited.

3. The method as described in claim 1, characterized in that, The step of identifying the current driving user through the second virtual machine includes: The second virtual machine obtains the user identity information of the current driving user; The second virtual machine matches the current driver's identity information with the registration identity information of the M registered users respectively; If the user's identity information matches the registration identity information of any one of the M registered users, the second virtual machine identifies the current driver as the target registered user. If the user fails to match any of the M registered users, the second virtual machine identifies the current driver as a non-registered user.

4. The method as described in claim 3, characterized in that, Starting the target virtual machine includes: If the second virtual machine identifies the current driving user as the target registered user, the second virtual machine sends a notification message to the virtual machine monitor, the notification message carrying the unique identification information of the current driving user; The virtual machine monitor determines the unique identification information of the current driving user from the notification message; The virtual machine monitor obtains the physical storage address of the guest operating system of the target virtual machine based on the unique identifier information; The virtual machine monitor, based on the physical storage address of the guest operating system, guides the startup of the guest operating system of the target virtual machine and loads the usage data of the target registered user into memory.

5. The method as described in claim 4, characterized in that, After starting the target virtual machine, the following is also included: The target virtual machine accesses the device usage permissions of the target registered user. The target virtual machine restricts the scope of use of various vehicle devices by the target registered user based on the device usage permissions.

6. The method as described in claim 4, characterized in that, After the guest operating system of the target virtual machine is booted and the usage data of the target registered user is loaded into memory, the process further includes: The target virtual machine obtains the usage status information of the target registered user at the end of the last time the vehicle was used from the usage data of the target registered user; Based on the usage status information, restore the usage status of the vehicle devices and in-vehicle applications.

7. A multi-user vehicle operating system control device, characterized in that, A device for use in a multi-user vehicle operating system, the multi-user vehicle operating system comprising M first virtual machines, second virtual machines, a virtual machine monitor, and virtualization hardware resources corresponding one-to-one with the M first virtual machines, the device comprising: An identity recognition unit is used to trigger the power-on process by the current driver and start the virtual machine monitor; the virtual machine monitor guides the second virtual machine to start, and the second virtual machine performs identity recognition on the current driver based on the unique identification information of the current driver; The virtual machine determination unit is used to determine the target virtual machine corresponding to the target registered user from M first virtual machines if the second virtual machine identifies the current driving user as the target registered user. The M first virtual machines are pre-created one-to-one with the M registered users. The second virtual machine and the M+1 virtualization hardware resources corresponding to the M first virtual machines are isolated from each other. The target registered user belongs to one of the M registered users, and M is a positive integer. The first virtual machine startup unit is used to start the target virtual machine so that the target virtual machine can exclusively access the virtualization hardware resources allocated to the target virtual machine. The start-disable unit is used to prevent the vehicle's engine from starting if the second virtual machine identifies the current driving user as an unregistered user.

8. A vehicle infotainment system, characterized in that, It includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the steps of the method according to any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon that, when executed by a processor, implements the steps of the method as claimed in any one of claims 1-6.

Images