Virtual machine management method and system, electronic equipment, storage medium and vehicle

Abstract

The invention discloses a virtual machine management method and system, electronic equipment, a storage medium and a vehicle. The method comprises the following steps: receiving message information uploaded by a first processor; determining a virtual machine corresponding to the message information according to the message information and a preset message registry, so as to transmit the message information to the corresponding virtual machine; wherein the preset message registry comprises a mapping relation between the type of the message information and the virtual machine. Visibly, according to the application, the mapping relationship between the type of the message information registered by each virtual machine and the response target can be recorded according to the preset message registry maintained by the service operating system, so that the message can be transmitted to the specified response target according to different services, and more efficient communication is realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of intelligent vehicles, and in particular to a virtual machine management method and system, an electronic device, a storage medium, and a vehicle. BACKGROUND

[0002] Currently, the infotainment system of a modern vehicle plays a vital role, as it is responsible for managing and controlling various functions and subsystems of the vehicle. However, current infotainment systems typically use a single virtual machine architecture or a simple layered architecture. These architectures have some drawbacks, such as low flexibility and low message transmission efficiency.

[0003] SUMMARY

[0004] The present application provides a virtual machine management method and system, an electronic device, a storage medium, and a vehicle, which can maintain a preset message registration table according to a service operating system, record the mapping relationship between the type of message information registered by each virtual machine and the response target, and thus transmit messages to the specified response target according to different services, achieving more efficient communication.

[0005] To solve the above technical problems, the first aspect of the present application discloses a virtual machine management method, which comprises:

[0006] receiving message information uploaded by a first processor;

[0007] determining the virtual machine corresponding to the message information according to the message information and a preset message registration table, to deliver the message information to the corresponding virtual machine; wherein the preset message registration table comprises the mapping relationship between the type of message information and the virtual machine.

[0008] Optionally, the above method comprises:

[0009] determining the target virtual machine according to the message type of the message information and the preset message registration table, and delivering the message information to the target virtual machine.

[0010] Optionally, the above method further comprises:

[0011] receiving response message information of the target virtual machine, to send the response message information to a response target, wherein the response message information is generated by the target virtual machine in response to the message information.

[0012] Optionally, the above method comprises:

[0013] determining the response target of the response message information according to the message type of the response message information and the preset message registration table.

[0014] Optionally, the above method comprises:

[0015] When a corresponding virtual machine is found in the preset packet registration table according to the packet type of the response packet information, the response packet information is sent to the corresponding virtual machine and the first processor.

[0016] Optionally, the method comprises:

[0017] When a corresponding virtual machine is found in the preset packet registration table according to the packet type of the response packet information, the response packet information is copied and distributed to the corresponding virtual machine and the first processor.

[0018] Optionally, the method comprises:

[0019] When a corresponding virtual machine is not found in the preset packet registration table according to the packet type of the response packet information, the response packet information is sent to the first processor.

[0020] Optionally, the method comprises:

[0021] When each virtual machine is powered on, each virtual machine registers packet information, a corresponding virtual machine identifier, and a packet type corresponding processing function in the preset packet registration table.

[0022] Optionally, the preset packet registration table comprises a virtual machine registered packet type, a virtual machine identifier, and a packet type corresponding processing function, and the method of determining a virtual machine corresponding to the packet information according to the packet information and the preset packet registration table to deliver the packet information to the corresponding virtual machine comprises:

[0023] determining a virtual machine corresponding to the packet information according to the type of the packet information and the preset packet registration table;

[0024] delivering the packet information to a packet processing function of the target virtual machine to enable the packet processing function of the target virtual machine to process the packet information.

[0025] Optionally, the method comprises:

[0026] When the virtual machine corresponding to the packet information is determined, the packet information is put into a corresponding virtual machine message queue to enable the packet processing function of the target virtual machine to process the packet information.

[0027] Optionally, the corresponding virtual machine of the service operating system comprises at least a first virtual machine and a second virtual machine, and the first virtual machine and the second virtual machine deliver information through a shared memory technology and / or a message queue mechanism.

[0028] Optionally, the first virtual machine corresponds to a left rear cabin system or a right rear cabin system of the vehicle, and the second virtual machine corresponds to a center control system and / or a co-driver system of the vehicle.

[0029] Optionally, the first processor is connected with at least one electronic control unit, and the message information is message information generated by the electronic control unit and received by the first processor.

[0030] The second aspect of the application further discloses a management method of a virtual machine, the method comprising:

[0031] receiving message information of at least one virtual machine;

[0032] determining a response target corresponding to the message information according to the message information and a preset message registration table, so as to deliver the message information to the response target; wherein the preset message registration table comprises a mapping relationship between a type of response message information and a response target.

[0033] Optionally, the above method comprises:

[0034] determining the response target of the response message information according to the message type of the message information and the preset message registration table.

[0035] Optionally, the above method comprises:

[0036] when a corresponding virtual machine is found in the preset message registration table according to the message type of the response message information, sending the response message information to the virtual machine corresponding to the response message information and the first processor.

[0037] Optionally, the above method further comprises:

[0038] when a corresponding virtual machine cannot be found in the preset message registration table according to the message type of the response message information, directly sending the response message information to the first processor.

[0039] Optionally, the above message information is generated in response to message information uploaded by the first processor.

[0040] The third aspect of the application discloses a management system of a virtual machine, comprising: a service operating system, a plurality of virtual machines and a first processor, the service operating system receives message information uploaded by the first processor, and determines a virtual machine corresponding to the message information according to the message information and a preset message registration table, so as to deliver the message information to the corresponding virtual machine; wherein the preset message registration table comprises a mapping relationship between a type of message information and a virtual machine.

[0041] The fourth aspect of the present application further discloses a virtual machine management system, comprising a service operating system, a plurality of virtual machines and a first processor, the service operating system is configured to receive message information of at least one virtual machine, and determine a response target corresponding to the message information according to the message information and a preset message registration table, so as to deliver the message information to the response target; wherein the preset message registration table comprises a mapping relationship between a type of response message information and a response target.

[0042] The fifth aspect of the present application discloses an electronic device, comprising:

[0043] The processor, the memory and the program or instructions stored in the memory and executable on the processor, when the program or instructions are executed by the processor, implement part or all steps of any one of the virtual machine management methods disclosed in the first aspect or the second aspect of the present application.

[0044] The sixth aspect of the present application discloses a computer storage medium, the computer storage medium stores computer instructions, when the computer instructions are invoked, are used to execute part or all steps of any one of the virtual machine management methods disclosed in the first aspect or the second aspect of the present application.

[0045] The seventh aspect of the present application discloses a computer program product, the computer program product comprises computer programs or instructions, when the computer programs or instructions are executed by the processor, implement part or all steps of any one of the virtual machine management methods disclosed in the first aspect or the second aspect of the present application.

[0046] The eighth aspect of the present application discloses a vehicle, the vehicle comprises the virtual machine management system disclosed in the third aspect or the second aspect of the present application, or the electronic device disclosed in the fifth aspect of the present application, or the computer readable storage medium disclosed in the sixth aspect of the present application, or the computer program product disclosed in the seventh aspect of the present application.

[0047] Compared with the prior art, the present application has the following beneficial effects:

[0048] In the present application, the message information uploaded by the first processor is received; according to the message information and a preset message registration table, a virtual machine corresponding to the message information is determined, so as to deliver the message information to the corresponding virtual machine; wherein the preset message registration table comprises a mapping relationship between a type of message information and a virtual machine. It can be seen that the present application can determine the mapping relationship between the type of message information registered by each virtual machine and the response target according to the preset message registration table maintained by the service operating system, so that the message can be delivered to the specified response target according to different services, and more efficient communication is realized. BRIEF DESCRIPTION OF DRAWINGS

[0049] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained without creative labor on the basis of these drawings.

[0050] Figure 1 is a schematic diagram of an architecture of a virtual machine management system disclosed by an embodiment of the present application;

[0051] Figure 2 is a schematic diagram of a flow of a virtual machine management method disclosed by an embodiment of the present application;

[0052] Figure 3 is a schematic diagram of a structure of another virtual machine management method disclosed by an embodiment of the present application;

[0053] Figure 4 is a schematic diagram of a structure of a virtual machine management system message upload disclosed by an embodiment of the present application;

[0054] Figure 5 is a schematic diagram of a structure of a virtual machine management system message delivery disclosed by an embodiment of the present application;

[0055] Figure 6 is a schematic diagram of a structure of an electronic device disclosed by an embodiment of the present application. DETAILED DESCRIPTION

[0056] In order to make the person skilled in the art better understand the present application, the technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of the present application.

[0057] The terms "first", "second", and the like in the specification and claims of the present application and the above-mentioned drawings are used to distinguish different objects, and are not used to describe a specific order. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, device, product, or end including a series of steps or units is not limited to the listed steps or units, but can optionally include steps or units not listed or can optionally include other steps or units inherent to the process, method, product, or end.

[0058] Reference to“an embodiment” herein means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase“in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are they necessarily all referring to a common set of embodiments, of the application. It is explicitly contemplated that embodiments described in one place can be combined with embodiments described in another place, even though such embodiments are not mentioned expressly in the same place.

[0059] The application discloses a virtual machine management method and system, an electronic device, a storage medium and a vehicle. The virtual machine management method and system, the electronic device, the storage medium and the vehicle can maintain a preset message registration table according to a service operating system, record the mapping relationship between the type of message information registered by each virtual machine and the response target, so that the message can be transmitted to the specified response target according to different services, and more efficient communication is realized. The following will be described in detail.

[0060] Please refer to Figure 1 , Figure 1 is a schematic diagram of the architecture of a virtual machine management system disclosed by the embodiments of the application. The virtual machine management system comprises a service operating system Service OS, a plurality of virtual machines and a first processor, that is Figure 1Service OS, multiple virtual machines and MCU hardware architecture. In the traditional cockpit solution, the central control, instrument and other systems are independent of each other, and are generally driven by a single chip to drive a single function / system. With the development of cockpit intelligence, the cockpit domain controller further integrates instruments, HUD, streaming rearview mirrors and other systems, from a single SoC driving a single system / single screen to a single SoC supporting multiple systems / multiple screens. A virtual machine-Hypervisor is used to run multiple operating systems on one hardware. The system using the multiple virtual machine architecture contains multiple virtual machines (Virtual Machine, VM), which can include left rear cockpit systems, right rear cockpit systems, central control and co-pilot systems in the vehicle cockpit, wherein the virtual machine VM1 corresponds to the left rear cockpit system, the virtual machine VM2 corresponds to the right rear cockpit system, and the virtual machine VM3 corresponds to the central control and co-pilot system. The Service OS manages the routing and delivery of messages and is responsible for service distribution and resource management. The microprocessor MCU is responsible for receiving requests and converting them into Can protocols to communicate with most electronic control units ECU in the vehicle control domain, including ECU in the intelligent access network, energy network and chassis network, etc. Each ECU device generates a message to the MCU, and the MCU uploads the message to the Service OS. In the system initialization stage, the Hypervisor starts and creates multiple virtual machine instances, VM1 corresponds to the left rear cockpit system, VM2 corresponds to the right rear cockpit system, and VM3 corresponds to the central control+co-pilot system. Each virtual machine loads its corresponding OS image, the Service OS starts and initializes the global resource manager, initializes the shared memory area, initializes the message queue management module, initializes the global message registry, each virtual machine starts its own message processing service, and calls the Service OS interface for registration. The registration process includes message type string, callback function reference and virtual machine identifier, etc. The Service OS writes this information into the message registry. The MCU also participates in the registration process, and the Service OS regards it as a target entity. The following embodiments will take the vehicle cockpit as an example for illustration, but the actual application range is not limited.

[0061] Embodiment one

[0062] Please refer to Figure 2 , Figure 2 is a flowchart of a virtual machine management method disclosed in an embodiment of the present application. Among them, Figure 2 The method described can be applied to an electronic device or a virtual machine management device or a virtual machine management system. The electronic device or virtual machine management device can be a separate device or integrated in a processing device, and the present application is not limited. As Figure 2 shown, the virtual machine management method can include the following operations:

[0063] 201、receive the message information uploaded by the first processor.

[0064] In the embodiment of the application, the message information is a data unit transmitted and processed in the network, and contains various information required by a specific device or system, such as data collected by a sensor, a control instruction, etc. The first processor is responsible for communication with an electronic control unit (ECU), and receives message information from the electronic control unit. The first processor can be a system on chip (SOC) or a microprocessor (MCU). Taking the example of a vehicle cabin system, a service operating system (Service OS) is used to manage the routing and delivery of message information. The MCU receives communication from most of the electronic control units (ECUs) in the vehicle control domain, including ECUs in the intelligent access network, the energy network and the chassis network, etc. Each ECU device generates a message to the MCU, and the MCU uploads the message to the service operating system (Service OS). The service operating system receives the message information uploaded by the first processor.

[0065] 202、determine a virtual machine corresponding to the message information according to the message information and a preset message registration table, so as to deliver the message information to the corresponding virtual machine; wherein the preset message registration table includes a mapping relationship between the type of the message information and the virtual machine.

[0066] In the embodiments of the present application, the service operating system Service OS maintains a preset message registry, which includes the type of message information and the mapping relationship of the virtual machine. The virtual machine needs to register the message type of the message information and the identifier of the virtual machine in the table. When the MCU uploads the message, after receiving the message information, the Service OS will deliver the message to the target virtual machine according to the mapping relationship of the message information and the virtual machine. It can also be through the processing function associated with the type of message information and the virtual machine in the preset message registry, to determine the corresponding virtual machine through the message type of the message information and send it to the processing function of the virtual machine for processing. The preset message registry can be a pre-set table or data structure, and the system can quickly find the corresponding virtual machine of the message information of a specific type through the preset message registry, and the system will deliver the message information to the corresponding virtual machine. In a multi-virtual machine architecture, the communication mechanism such as shared memory and message queue can be used to realize the delivery of message information. For example, through shared memory, the message information can be directly accessed by the target virtual machine; through the message queue, the message information can be sent to the message queue corresponding to the target virtual machine, waiting for the virtual machine to process. For example, in a vehicle cabin domain control system, the first processor receives a message from a temperature sensor, which contains temperature data in the current cabin. The first processor uploads the message containing the temperature data to the Service OS. The Service OS module analyzes the message information and determines that it belongs to the temperature sensor message. Then, by querying the preset message registry, the mapping relationship between the temperature sensor message type and the virtual machine VM1 is found in the registry. The virtual machine VM1 is responsible for processing information related to the cabin environment, and it can read the temperature data in the shared memory and perform corresponding processing according to the preset temperature control strategy, for example, if the temperature is too high, it sends a control instruction to the air conditioning system to reduce the temperature in the cabin. In this case, different types of messages can be assigned to different virtual machines for processing, so that the functions of each virtual machine are relatively independent, reducing the interference between different functions and improving the stability and reliability of the system.

[0067] It can be seen that the method described in the embodiments of the present application can quickly and accurately determine the virtual machine corresponding to the message information through the preset message registry, avoiding unnecessary search and judgment process, and improving the efficiency of message information processing.

[0068] In an optional embodiment, the method can include the following operations:

[0069] According to the message type of the message information and the preset message registry, the target virtual machine is determined, and the message information is delivered to the target virtual machine.

[0070] In the embodiment of the present application, in the cockpit domain control system of the multi-virtual machine architecture, when a message arrives, the message is parsed. The message generally includes a header and a payload part, and the message type information is generally stored in the message header. For example, it can be identified by a specific field that the message is a temperature message from a seat sensor, a state message from a window motor, or a play control message belonging to a multimedia device, etc. The preset message registry is a pre-constructed data structure, which records the target virtual machine corresponding to each message type with the message type as the index. This registry can be stored in the form of a database table, a hash table, etc. Taking the hash table as an example, the message type is taken as the key key and the target virtual machine identifier is taken as the value value. According to the message type, all registered targets in the preset registry are searched again to determine whether the message needs to be transferred to other virtual machines, and if so, the message is copied and distributed, and is also sent to the first processor, and if there is no target virtual machine, the message is directly sent to the first processor. Specifically, after the message type is obtained, the system uses the type as the key to search in the hash table. Through the searching operation in the preset message registry, the target virtual machine corresponding to the message type can be quickly located. Illustratively, when the window motor sensor detects that the window state changes, a window state message is generated, and the MCU sends the message to the service operating system. By parsing the message header, it is obtained that the message type is a “window state message”, and the preset message registry is queried to find the corresponding target virtual machine VM2 according to the message type. Then the window state message is transmitted to VM2. VM2 can take the message from the message queue, update the window state information after parsing, and send control instructions to the window motor as needed.

[0071] It can be seen that the method described in the embodiment of the present application can quickly and accurately route the message information to the target virtual machine through the preset message registry, avoid blindly transmitting the message between multiple virtual machines, reduce unnecessary communication overhead and processing time, and thus improve the operation efficiency of the entire cockpit domain control system.

[0072] In yet another optional embodiment, the method can further include the following operations: receiving response message information of the target virtual machine, and sending the response message information to the response target, wherein the response message information is generated by the target virtual machine in response to the message.

[0073] In the embodiments of the present application, when the response message is generated and delivered, the Service OS transfers the message to other virtual machines or directly delivers it to the MCU according to the message type. The target virtual machine receives the initial message information, processes the message information according to the message processing function, and generates corresponding response message information based on the processing result. For example, if the initial message is a request message for inquiring the status of a device, the target virtual machine will encapsulate the status information into a response message after obtaining the actual status of the device. The response message usually includes a message header and a message body, the message header can include response type, message length and other information, and the message body carries specific response content. The response target can be indicated in the initial message information or have a preset corresponding relationship in the Service OS. For example, the initial message can be a request sent by an external device, such as a vehicle-mounted sensor, to the virtual machine, and the response target can be the external device; or it can be other virtual machines or a functional module in the system. The Service OS will determine the response target according to the preset rules or the relevant information in the initial message. When the response target is determined, the response message information will be sent out according to the communication mode of the response target.

[0074] It can be seen that the method described in the embodiments of the present application can ensure that frequent information interaction is required between each electronic control unit and virtual machine. By receiving the response message of the target virtual machine and sending it to the response target, a complete information interaction closed loop is formed, which can timely grasp the processing status and result of each virtual machine.

[0075] In the optional embodiments, further optionally, the above method comprises:

[0076] According to the message type of the response message information and the preset message registration table, the response target of the response message information is determined.

[0077] In the embodiments of the present application, when the response message information is received, the message type of the response message information needs to be determined, and the determination can be performed by parsing the response message information to determine the message type. The response message usually has a specific format, and the message header part contains key information identifying the message type. For example, in a vehicle cabin domain control system, the message header can use specific bytes or fields to encode the message type, such as "0x01" representing a window status response message, "0x02" representing an air conditioning temperature adjustment response message, and the like. By reading these encoding information, the type of the response message can be accurately identified. By searching in the preset message registration table, the response target corresponding to the response message type can be obtained. According to the embodiments, when another response target is added to the cabin system, only the preset message registration table needs to be modified to bind the response message information and the response target, so that the information can be sent to the corresponding response target, without the need to make large-scale modifications to the core routing logic of the system, and the system flexibility and scalability can be improved.

[0078] It can be seen that the method described in the embodiments of the present application can manage the correspondence between the message type and the response target based on the preset message registration table, avoid the process of blindly trying and judging among multiple possible response targets, and enable the system maintenance personnel to clearly understand the processing path of each response message.

[0079] In the optional embodiments, further optionally, the method can further include the following operation: when the corresponding virtual machine is found in the preset message registration table according to the message type of the response message information, the response message information is sent to the virtual machine corresponding to the response message information and the first processor.

[0080] In the embodiments of the present application, the service operating system parses the received response message and extracts message type information. The message type is usually contained in the message header and represented by a specific code or identifier. For example, a byte value is used to distinguish different types of messages, such as "0x01" representing a window status response message, "0x02" representing an air conditioner temperature response message, and so on. According to the parsed message type, a preset message registry including the mapping relationship between message types and virtual machines is queried. If the corresponding virtual machine is found in the preset message registry according to the message type, the response message information is sent to the virtual machine and the first processor. The sending method can be selected according to the architecture and communication protocol of the system, such as using shared memory, message queue, network socket, etc. The response message needs to be copied and sent to two different components. The response message information is copied and distributed to the virtual machine corresponding to the response message information and the first processor. When the virtual machine and the first processor process the response message at the same time, the problem of inconsistent data may occur. For example, the virtual machine updates the local state according to the message, while the first processor obtains the state inconsistent with the virtual machine due to processing delay or other reasons. In order to solve this problem, a synchronization mechanism such as lock, semaphore or distributed transaction can be used to ensure that the operations of the two components on related data are synchronized.

[0081] Sending the response message to the corresponding virtual machine and the first processor at the same time can ensure that the related functional modules obtain information in time and perform corresponding operations, and at the same time enable the core control unit to master the global state, thereby realizing efficient collaboration. If the response message is only sent to a single component, once the component fails, information loss or processing interruption may occur. By sending to two different components (virtual machine and first processor), even if one of the components has a problem, the other component can still normally process the information, thereby improving the reliability and fault tolerance of the system.

[0082] Optionally, the method can further include the following operation: when no corresponding virtual machine is found in the preset message registry according to the message type of the response message information, the response message information is directly sent to the first processor.

[0083] In the embodiment of the present application, the first processor can be an MCU or an SOC, which is responsible for receiving requests and converting into Can protocol to communicate with most electronic control units (ECUs) in the vehicle control domain. In the current technology, different regional systems of the vehicle cabin are carried by multiple virtual machines to achieve control of different regional systems, but the interaction between the multiple virtual machines and the electronic control units is severely dependent on the first processor for interaction. In the embodiment of the present application, when the corresponding virtual machine cannot be found in the preset message registration table according to the message type of the response message information, the response message information can be directly sent to the first processor, and the first processor executes the default processing logic. Alternatively, if the first processor supports dynamic configuration, the message header characteristics can be parsed, a temporary virtual machine configuration is automatically generated and registered in the preset message registration table for subsequent message matching. If the first processor is unavailable, the message can be discarded or a backup processor can be tried.

[0084] It can be seen that the method described in the embodiment of the present application can compensate for the incomplete preset message registration table in the message distribution process, and when the corresponding target virtual machine cannot be matched, the first processor is used as a bottom response target, which can balance the performance and security of message distribution.

[0085] Further optionally, the above method comprises:

[0086] When each virtual machine is started, the message information registered by each virtual machine in the preset message registration table, the corresponding virtual machine identifier, and the processing function corresponding to the message type are received.

[0087] In the embodiment of the present application, when each virtual machine is started, the message information registered by each virtual machine in the preset message registration table, the corresponding virtual machine identifier, and the processing function corresponding to the message type are received. Specifically, in the virtual machine startup phase, each virtual machine generates specific message information or the corresponding message information type of the business according to its business requirements and functional characteristics. These message information covers key content such as data format, communication protocol, and message type. At the same time, the virtual machine associates and registers its unique identifier, such as virtual machine ID, with the message information, so that the source of the message can be accurately identified subsequently. In addition, the virtual machine also needs to register the corresponding processing function for different types of messages. The processing function defines the specific processing logic for specific messages, such as data analysis, business processing, response generation, and other operations. Through the above message registration mechanism, the virtual machine and the message processing logic are decoupled. The virtual machine only needs to focus on message generation and registration when starting.

[0088] It can be seen that the embodiments of the present application can improve the scalability and flexibility of the system. When a new virtual machine is added or the message processing demand changes, only corresponding registration or modification operation needs to be performed in the preset message registry, without the need for large-scale adjustment of the entire system architecture. Meanwhile, this mechanism also helps to improve the performance and stability of the system. By centrally managing the message processing functions, the processing flow can be optimized, unnecessary resource consumption can be reduced, and the probability of system failure can be reduced.

[0089] In the optional embodiment, the preset message registry includes the message type registered by the virtual machine, the virtual machine identifier, and the processing function corresponding to the message type. According to the message information and the preset message registry, the virtual machine corresponding to the message information is determined, and the message information is transmitted to the corresponding virtual machine, including:

[0090] According to the type of the message information and the preset message registry, the virtual machine corresponding to the message information is determined.

[0091] The message information is transmitted to the message processing function of the target virtual machine, so that the message processing function of the target virtual machine processes the message information.

[0092] In the embodiments of the present application, the preset message registry covers key information such as the message type registered by the virtual machine, the virtual machine identifier, and the processing function corresponding to the message type. In the message processing flow, according to the message information and the preset message registry, the virtual machine corresponding to the message information is accurately determined, and then the message information is transmitted to the corresponding virtual machine. Specifically, according to the type of the message information, quick search and matching are performed in the preset message registry. Since the correspondence between each message type and the virtual machine identifier is recorded in detail in the registry, through this type matching method, the virtual machine corresponding to the message information can be quickly located. For example, if the message type is a data request message, the virtual machine identifier corresponding to the type is found in the registry, and it is clear that the message should be sent to which virtual machine. After the target virtual machine is determined, the message information is transmitted to the message processing function of the target virtual machine. Each virtual machine specifies a processing function for different message types when registering, and these processing functions encapsulate specific business logic and operation steps. When the message information is transmitted to the message processing function of the target virtual machine, the function will analyze, process and respond to the message information according to the preset logic, thereby completing the entire message processing flow. In the embodiments of the present application, through this message processing mechanism based on the preset message registry, efficient and accurate matching and processing of messages and virtual machines are realized.

[0093] It can be seen that the method described in the embodiments of the present application can significantly improve the packet processing efficiency and accuracy of the system. The preset packet registry provides a standardized reference basis for packet processing, avoiding the packet mis-matching and processing confusion problems that may occur in the traditional way, greatly shortening the time period of packet processing. At the same time, when a new virtual machine or packet type is added to the system, only the corresponding registration and updating operation needs to be performed in the preset packet registry, so that the new business requirements can be quickly adapted without the need for large-scale modification and optimization of the entire packet processing system, effectively reducing the development and maintenance cost of the system.

[0094] Optionally, the method further includes:

[0095] When the virtual machine corresponding to the packet information is determined, the packet information is put into the corresponding virtual machine message queue, so that the packet processing function of the target virtual machine processes the packet information.

[0096] In the embodiments of the present application, the packet processing flow is perfected by introducing the virtual machine message queue, and the packet information is buffered and temporarily stored. When the virtual machine corresponding to the packet information is determined, the packet information is not directly delivered to the packet processing function of the target virtual machine, but is first put into the corresponding virtual machine message queue. Each virtual machine has an independent and exclusive message queue, which is like an ordered "task warehouse" that stores the packet information waiting for processing according to certain rules, such as first-in first-out.

[0097] It can be seen that the method described in the embodiments of the present application can greatly enhance the robustness and reliability of the system by introducing the virtual machine information queue. In the face of complex and variable business scenarios and high-concurrency packet transmission, the message queue can effectively balance the system load and ensure that each virtual machine can process the packet information in an orderly manner.

[0098] Optionally, the virtual machines corresponding to the service operating system include at least a first virtual machine and a second virtual machine, and the first virtual machine and the second virtual machine deliver information through a shared memory technology and / or a message queue mechanism.

[0099] In the embodiments of the present application, the information transmission between the first virtual machine and the second virtual machine is realized by using the shared memory technology and / or the message queue mechanism. The virtual machines corresponding to the service operating system at least include the first virtual machine and the second virtual machine. The first virtual machine and the second virtual machine do not work in isolation, but realize efficient information transmission through the shared memory technology and / or the message queue mechanism. The shared memory technology provides a common memory area for the first virtual machine and the second virtual machine, and both parties can directly read and write the area to quickly exchange data. The advantage of this way is that the data transmission speed is fast, and there is no need to go through a complex data encapsulation and decapsulation process, which is especially suitable for information transmission scenarios with high real-time requirements and large data volume. For example, in a real-time data processing system, the first virtual machine can write the collected data into the shared memory in real time, and the second virtual machine can immediately read the data from the shared memory for further processing, greatly shortening the data transmission delay. The message queue mechanism provides an asynchronous and decoupled way for information transmission between the first virtual machine and the second virtual machine. Each virtual machine can encapsulate the information to be sent into a message and put it into the message queue, and the receiving virtual machine can obtain the message from the message queue according to its processing capacity and rhythm. This way can effectively avoid the system blocking problem caused by the mismatch between the sending side and the receiving side processing speed, and improve the overall stability and reliability of the system. For example, in a distributed task scheduling system, the first virtual machine as a task publisher sends task information in the form of a message to the message queue, and the second virtual machine as a task executor obtains the task from the message queue and executes it, realizing flexible allocation and efficient processing of tasks.

[0100] It can be seen that the method described in the embodiments of the present application can improve the communication efficiency and cooperative working ability between virtual machines in the service operating system.

[0101] In optional embodiments, the above method is applied to a vehicle, the first virtual machine corresponds to a left rear compartment system or a right rear compartment system of the vehicle, and the second virtual machine corresponds to a central control and / or co-pilot system of the vehicle.

[0102] In the embodiments of the present application, the above method is applied to a vehicle, wherein the first virtual machine corresponds to a left rear cabin system or a right rear cabin system of the vehicle, and the two rear cabin systems are generally responsible for the control of related functions in the rear area of the vehicle, such as rear seat adjustment, rear cabin environment control (such as temperature, humidity, air purification, etc.), rear entertainment device control, etc. The second virtual machine corresponds to a central control system and / or a co-pilot system of the vehicle. The central control system is a core control hub of the vehicle, integrating multimedia entertainment, navigation, vehicle state monitoring and setting, and many other key functions. The co-pilot system focuses on providing exclusive entertainment and service functions for the co-pilot passenger, such as independent control of the co-pilot display screen, personalized adjustment of the co-pilot seat, etc. In actual application, the first virtual machine and the second virtual machine communicate information through shared memory technology and / or message queue mechanism. Taking the shared memory technology as an example, when the first virtual machine of the left rear cabin system detects the adjustment demand of the rear passengers on the temperature, it will directly write the related temperature setting data into the shared memory area. The central control system corresponding to the second virtual machine can read these data from the shared memory in real time, and synchronously display them on the central control display screen, while adjusting the air conditioning system of the vehicle according to the new temperature setting, to realize the cooperative control of the front and rear cabin temperatures. The above method is applied to a vehicle, and the virtual machines are reasonably allocated according to the functional characteristics of different areas of the vehicle, so as to realize the information transmission and cooperative work between the virtual machines through an efficient communication mechanism.

[0103] Optionally, the first processor is connected with at least one electronic control unit, and the message information is message information generated by the electronic control unit and received by the first processor.

[0104] In the embodiments of the present application, the first processor plays a key role in core data processing and coordination in the vehicle system, and is connected with at least one electronic control unit (ECU). The first processor can be a SOC, MCU or other processor. As the intelligent control core of various subsystems in the vehicle, the electronic control unit is widely distributed in many fields such as engine control, vehicle body electronics, chassis control, etc., and is responsible for real-time collection of various state information in the vehicle running process, such as engine speed, vehicle speed, temperature, pressure, etc., and generates corresponding control instructions and message information according to the preset control strategy. The message information is a key data carrier received by the first processor from the electronic control unit. These message information contains rich vehicle state and control instruction content, and its format usually follows a specific communication protocol to ensure accurate data transmission and analysis. For example, in the engine control system, the electronic control unit will generate message information containing key parameters such as fuel injection amount and ignition timing according to the real-time working condition of the engine, and send it to the first processor. In actual application, the communication between the first processor and the electronic control unit usually uses high-speed and reliable communication buses such as CAN (Controller Area Network) bus, LIN (Local Interconnect Network) bus or FlexRay bus, etc.

[0105] Embodiment two

[0106] Please refer to Figure 3 , Figure 3 is another flowchart of a method for managing a virtual machine according to an embodiment of the present application. In this method, Figure 3 The method described can be applied in an electronic device or a virtual machine management device or a virtual machine management system. The electronic device or the virtual machine management device can be a separate device or integrated in a processing device, which is not limited in the embodiments of the present application. As shown in Figure 3 The method for managing a virtual machine can include the following operations:

[0107] 301, receiving message information of at least one virtual machine.

[0108] In the embodiments of the present application, the service operating system undertakes the key responsibility of overall management and efficient coordination in the running process of a complex system such as a vehicle, and receives message information from at least one virtual machine. The virtual machines correspond to different functional modules of the vehicle respectively, such as a power system virtual machine responsible for engine and related control, a vehicle body control virtual machine managing vehicle windows, lights and other components, and the vehicle cabin can also be partitioned, with different virtual machines corresponding to different areas of the cabin, such as left and right rear cabin systems, a central control and / or co-pilot system. The virtual machines will continuously generate various types of message information in the running process, which covers rich content such as system state, control instructions and data requests. The service operating system receives the message information through specific communication interfaces and protocols.

[0109] 302. Determine, according to the message information and a preset message registration table, a response target corresponding to the message information, so as to deliver the message information to the response target; wherein the preset message registration table comprises a mapping relationship between a type of the message information and the response target.

[0110] In the embodiments of the present application, after receiving the message information, the service operating system accurately determines the response target corresponding to the message information according to the message information and the preset message registration table, and accurately delivers the message information to the response target. The mapping relationship between the type of the message information and the response target is recorded in detail in the preset message registration table. For example, when a message information about adjusting the engine speed is received, the service operating system can quickly determine that the response target corresponding to the message information is a virtual machine or an electronic control unit (ECU) related to engine control by querying the preset message registration table, so as to accurately deliver the message information and ensure that the engine can respond in time and make corresponding adjustments.

[0111] It can be seen that the method described in the embodiments of the present application can greatly improve the efficiency and accuracy of message processing based on the matching and delivery mechanism of the preset message registration table, and avoid system failure caused by information delivery error or delay.

[0112] In optional embodiments, the above method comprises:

[0113] Determine, according to the message type of the message information and a preset message registration table, a response target of the message information.

[0114] In the embodiments of the present application, the response target of the message information is determined according to the message type of the message information and the preset message registration table. The message type is a classification identifier of the essential characteristics of the message information. The preset message registration table records the mapping relationship between each message type and the corresponding response target. In actual application, when the system receives a message information, it will analyze and identify the message type of the message information. This process is usually realized through a specific protocol analysis algorithm and message header information analysis to determine the type of the message. Once the message type is determined, the system will immediately query the preset message registration table to quickly locate the response target to which the message information should be delivered according to the mapping relationship between the message type and the response target. This matching and positioning method based on the preset rules improves the efficiency and accuracy of message processing.

[0115] Optionally, the above method comprises:

[0116] When the corresponding virtual machine is found in the preset message registration table according to the message type of the message information, the message information is sent to the virtual machine corresponding to the message information and the first processor.

[0117] In the embodiments of the present application, when the corresponding virtual machine is found in the preset message registration table according to the message type of the message information, the message information is sent to the virtual machine corresponding to the message information and the first processor. The preset message registration table is a key rule base for system message processing, which records in detail the mapping relationship between each message type and the corresponding virtual machine. Once the corresponding virtual machine is matched, the message information is sent to the virtual machine alone, and it is also delivered to the first processor at the same time. The first processor is the core control center of the system, and the message information is sent to the first processor synchronously. It can analyze and judge the received message information in depth, realize real-time monitoring of the running state of each virtual machine, and also can determine whether the vehicle faces potential safety risks according to the system state change reflected by the message information, combined with the preset global strategy and business rules, and comprehensively judge the message information, and timely trigger the corresponding safety warning or automatic control measures. The comprehensive control can also be controlled through the double-channel mode. Only when both the response target matching mode through the preset registration table and the response target determination mode after being processed by the first processor are satisfied, the response target executes the corresponding function.

[0118] It can be seen that the method described in the embodiments of the present application can improve the intelligent level and collaborative work ability of the system. Through this double-channel information delivery mechanism, the system core realizes real-time control and accurate decision-making of the overall running state, effectively avoiding system collapse or function failure caused by information island or local fault.

[0119] Optionally, the above method further comprises:

[0120] When no corresponding virtual machine is found in the preset message registry according to the message type of the message information, the message information is directly sent to the first processor.

[0121] In the embodiments of the present application, although the preset message registry is carefully designed and covers the mapping relationship between most common message types and virtual machines during normal operation of the system, due to continuous expansion of system functions, continuous introduction of new services, or some unexpected or abnormal message conditions, there will inevitably be some message types that are not pre-registered in the registry. That is, in the process of querying the preset message registry according to the message type of the message information to determine the response target, it may occur that no corresponding virtual machine is found in the preset message registry according to the message type of the message information. When this situation of not finding a corresponding virtual machine in the preset message registry occurs, the message information is directly sent to the first processor. For example, if the message information is data about a certain intelligent sensor newly added to the vehicle, although the preset message registry does not record the virtual machine corresponding to the sensor message, the first processor can recognize that it is sensor data and forward it to the data storage module for storage, while triggering a system alarm to remind the developer to update the preset message registry and configure the corresponding virtual machine in time.

[0122] As can be seen, the method described in the embodiments of the present application can enhance the fault tolerance and adaptability of the system by directly sending the response message information to the first processor when no corresponding virtual machine is found in the preset message registry.

[0123] Optionally, the message information is generated in response to the message information uploaded by the first processor.

[0124] In the embodiments of the present application, the message information is generated in response to the message information uploaded by the first processor. After the first processor generates and uploads the message information, the system will have virtual machine processing according to a specific trigger mechanism and business process, and the virtual machine generates new message information in response to these uploaded message information. Alternatively, the system can also directly generate new message information in response to the message information uploaded by the first processor.

[0125] Embodiment Three

[0126] Please refer to Figure 4 , Figure 4 is a structural schematic diagram of message uploading of a virtual machine management system disclosed in the embodiments of the present application. The virtual machine management system comprises a service operating system, a plurality of virtual machines and a first processor, the service operating system receives the message information uploaded by the first processor, and determines the virtual machine corresponding to the message information according to the message information and a preset message registry, so as to deliver the message information to the corresponding virtual machine; wherein the preset message registry comprises the mapping relationship between the type of the message information and the virtual machine.Figure 4In the example shown in the middle, the first processor is an MCU, the service operating system is Service OS, there are three virtual machines, VM1, VM2 and VM3, VM1 corresponds to the left rear cabin system (RSE L), VM2 corresponds to the right rear cabin system (RSE R), and VM3 corresponds to the central control + co-pilot system (IVI + FSE). Different virtual machines also require different messages, such as turn signal messages. The upper-layer APP of the central control virtual machine, my car module, needs to receive and render the car lights, while other rear cabin systems do not need to receive such messages. Exemplarily, when the MCU uploads a message, the Service OS first searches the message registry to quickly and accurately determine which virtual machines are interested in the currently uploaded message. Once the corresponding target virtual machine is determined, the corresponding target virtual machine is determined according to the mapping relationship between the target virtual machine message processing function and the message type. After the target virtual machine responds to the message information, the response message information can be sent to the service operating system, or the response message information can be sent to the first processor, such as the MCU. Optionally, the uploaded message is placed in a message queue. The message queue is implemented using structures such as linked lists and arrays, and is managed using the FIFO first-in-first-out method, ensuring that messages are passed to the message processing function of the target virtual machine in the order of upload. The message processing function is called in an event-driven manner, that is, when a new message arrives in the message queue, the system automatically calls the corresponding message processing function to parse, process and respond to the specific type of message. The message is placed in the message queue of the corresponding virtual machine after matching to the corresponding VM. The event loop listens to the message queue, and once a new message is found, the callback function is called to execute the message processing function handleMessage() to process the received message and generate a response message. The message is received and routed again by the Service OS. In summary, through the cooperative action of the message registry, the message queue and the virtual machine message processing function, the system can implement an efficient and reliable message transmission mechanism, providing a reliable processing flow and guarantee for the MCU uploaded message. At the same time, after each virtual machine is started, it registers the required message types and the corresponding message processing function handleMessage() in the message registry messageRegistry maintained by the Service OS. The message processing function is constructed in the application service layer inside the virtual machine and is a class method. The types of message types include, for example, "ControlCommand" (control command), "SensorData" (sensor data), "StatusUpdate" (status update), etc. During the registration process, the message type and the corresponding message processing function are mapped, that is, the mapping registration is completed through the registration interface provided by the Service OS during the registration stage, the reference or identifier is passed to the Service OS and stored in the messageRegistry, which is used for subsequent message routing and callback calling.This registration process is a very key link in the system, it ensures the accurate delivery and processing of messages. The information is delivered between the various virtual machines VM through the shared memory technology and message queue mechanism of Hypervisor, Hypervisor is a method to achieve data sharing and communication between virtual machines, Hypervisor will create a shared memory area in the physical memory of the host, and then map this memory area to the address space of each virtual machine. In this way, the virtual machine can directly access and operate this shared memory, realize the data sharing and communication between virtual machines. The communication mode of the message queue is that one party sends the message to the queue, and the other party receives the message from the queue. The message queue provides an asynchronous communication mechanism, ensuring the ordered delivery and processing of messages. In this embodiment, the service operating system can also be used to implement the steps in the virtual machine management method disclosed in embodiment one or embodiment two of the application.

[0127] Embodiment four

[0128] Please refer to Figure 5 , Figure 5is another structure diagram of message delivery of a virtual machine management system disclosed by the embodiment of the present application. The virtual machine management system comprises a service operating system, a plurality of virtual machines and a first processor, the service operating system is configured to receive message information of at least one virtual machine, and determine a response target corresponding to the message information according to the message information and a preset message registration table, so as to deliver the message information to the response target; wherein the preset message registration table comprises a mapping relationship between a type of response message information and a response target. When a message uploaded by an MCU is received by a message processing function of a virtual machine, a process of generating a response message for delivery is generated through analysis and processing. The key of the process is a message transfer mechanism of the Service OS, which quickly locates a target virtual machine or MCU according to the type of the message, and effectively delivers the message. The specific process is as follows: when a virtual machine delivers a message, the Service OS will first look up the corresponding target virtual machine in the registration table according to the type of the message. If one or more virtual machines have previously registered the type of the message and there is a corresponding mapping of the message processing function, the Service OS will copy multiple copies of the message and directly deliver them to the target virtual machine through the message queue for processing, without the need for message response and upload by the MCU, thereby realizing quick transfer of the message, reducing transmission delay and improving the message delivery efficiency and response speed of the system. For example, if the rear cabin adjusts the temperature of the air conditioner, the control instruction type message will be directly delivered to the central control cabin and the co-driver cabin, so that the adjusted temperature can be quickly responded and displayed. This mechanism enables the system to more flexibly process different types of messages and realize quick response and scheduling of tasks. On the other hand, if the processing function or the target virtual machine corresponding to the type of the message is the MCU, the Service OS will deliver the message to the MCU for processing. Compared with the single path delivery mode of the traditional cabin domain control system, the message transfer mechanism of the cabin domain control scheme with the multi-virtual machine architecture is more flexible and scalable, thereby improving the real-time performance of the system and the efficiency of processing tasks. The shared memory technology and the message queue mechanism of the Hypervisor are used to deliver information between the virtual machines VM. The Hypervisor is a method for realizing data sharing and communication between virtual machines. The Hypervisor creates a shared memory area in the physical memory of the host, and then maps the memory area to the address space of each virtual machine. In this way, the virtual machines can directly access and operate the shared memory, thereby realizing data sharing and communication between the virtual machines. The communication mode of the message queue is that one party sends a message to the queue, and the other party receives the message from the queue. The message queue provides an asynchronous communication mechanism to ensure the ordered delivery and processing of the message. In the embodiment, the service operating system can also be used to realize the steps in the virtual machine management method disclosed in the first embodiment or the second embodiment of the present application.

[0129] Embodiment five

[0130] Please refer to Figure 6 , Figure 6 is a structural schematic diagram of an electronic device disclosed in an embodiment of the present application. In the figure, Figure 6 The apparatus described can be a stand-alone apparatus or can be integrated in a display control processing device, and the embodiments of the present application are not limited in this regard. As Figure 6 indicated, the electronic device can include:

[0131] The processor 601, the memory 602, and the program or instruction stored in the memory and executable on the processor 601, when executed by the processor 601, implement some or all steps of the virtual machine management method disclosed in Embodiment One or Embodiment Two of the present application.

[0132] Embodiment Six

[0133] The embodiments of the present application disclose a computer storage medium, which stores computer instructions, and when the computer instructions are invoked, are used to execute the steps of the virtual machine management method disclosed in Embodiment One or Embodiment Two of the present application.

[0134] Embodiment Seven

[0135] The embodiments of the present application disclose a computer program product, which includes computer programs or instructions, and when the computer programs or instructions are executed by a processor, implement the steps of the virtual machine management method disclosed in Embodiment One or Embodiment Two of the present application.

[0136] Embodiment Eight

[0137] The embodiments of the present application disclose a vehicle, which includes the steps of the virtual machine management method disclosed in Embodiment One or Embodiment Two of the present application, or the virtual machine management system disclosed in Embodiment Three or Embodiment Four of the present application, or the electronic device disclosed in Embodiment Five of the present application, or the computer readable storage medium disclosed in Embodiment Six of the present application, or the computer program product disclosed in Embodiment Seven of the present application.

[0138] The apparatus or component embodiments described above are only schematic, and the modules described as separate components can or can not be physically separate, that is, can be located in one place or distributed on multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the present embodiment. Those skilled in the art can understand and implement without creative labor.

[0139] Those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary universal hardware platform, and of course can also be implemented by hardware, through the specific description of the above embodiments. Based on such understanding, the above technical solutions can be embodied in the form of a software product in essence or in the form of a part of the prior art. The computer software product can be stored in a computer readable storage medium, and the storage medium includes a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, a magnetic disk storage, a magnetic tape storage, or any other computer readable medium that can be used to carry or store data.

[0140] It should be noted that the computer program code required for the operation of the various parts of the specification can be written in any one or more programming languages, including object-oriented programming languages such as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB.NET, Python, etc., conventional programmatic programming languages such as C language, Visual Basic, Fortran2003, Perl, COBOL 2002, PHP, ABAP, dynamic programming languages such as Python, Ruby and Groovy, or other programming languages. The program code can be completely run on a computer (PC, embedded intelligent device, etc.), or run as a separate software package on a user computer, or partially run on a user computer and partially run on a remote computer, or completely run on a remote computer or server. In the latter case, the remote computer can be connected to the user computer through any network form, such as a local area network (LAN) or a wide area network (WAN), or connected to an external computer (for example, through the Internet), or in a cloud computing environment, or as a service such as software as a service (SaaS).

[0141] It should be pointed out finally that: the management method and system of the virtual machine disclosed by the embodiments of the present application are only the preferred embodiments of the present application, and are used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that; the technical solutions recorded in the foregoing embodiments can still be modified, or some technical features therein can be replaced equivalently; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for managing virtual machines, characterized in that, The method includes: Receive message information uploaded by the first processor; Based on the message information and the preset message registry, the virtual machine corresponding to the message information is determined, so as to pass the message information to the corresponding virtual machine; wherein, the preset message registry includes the mapping relationship between the message information type and the virtual machine.

2. The virtual machine management method according to claim 1, characterized in that, The method includes: Based on the message type of the message information and the preset message registry, the target virtual machine is determined, and the message information is transmitted to the target virtual machine.

3. The virtual machine management method according to claim 1, characterized in that, The method further includes: The system receives the response message information from the target virtual machine and sends the response message information to the target, wherein the response message information is generated by the target virtual machine in response to the message information.

4. The virtual machine management method according to claim 3, characterized in that, The method includes: The response target of the response message is determined based on the message type of the response message and the preset message registry.

5. The virtual machine management method according to claim 4, characterized in that, The method includes: When a corresponding virtual machine is found in the preset message registry based on the message type of the response message information, the response message information is sent to the virtual machine corresponding to the response message information and the first processor.

6. The virtual machine management method according to claim 5, characterized in that, The method includes: When a corresponding virtual machine is found in the preset message registry based on the message type of the response message information, the response message information is copied and distributed to the virtual machine corresponding to the response message information and the first processor.

7. The virtual machine management method according to claim 5, characterized in that, The method further includes: When a virtual machine cannot be found in the preset message registry according to the message type of the response message information, the response message information is sent to the first processor.

8. The virtual machine management method according to claim 1, characterized in that, The method includes: When each virtual machine is powered on, it receives the message information registered by each virtual machine in the preset message registry, as well as the corresponding virtual machine identifier and the processing function corresponding to the message type.

9. The virtual machine management method according to claim 1, characterized in that, The preset message registry includes the message type registered by the virtual machine, the virtual machine identifier, and the processing function corresponding to the message type. The step of determining the virtual machine corresponding to the message information based on the message information and the preset message registry, and then passing the message information to the corresponding virtual machine, includes: The virtual machine corresponding to the message information is determined based on the message information type and the preset message registry. The message information is passed to the message processing function of the target virtual machine so that the message processing function of the target virtual machine can process the message information.

10. The virtual machine management method according to any one of claims 1-9, characterized in that, The method further includes: Once the virtual machine corresponding to the message information is determined, the message information is placed in the corresponding virtual machine message queue so that the message processing function of the target virtual machine can process the message information.

11. The virtual machine management method according to claim 1, characterized in that, The virtual machine corresponding to the service operating system includes at least a first virtual machine and a second virtual machine, and the first virtual machine and the second virtual machine transmit information through shared memory technology and / or message queue mechanism.

12. The virtual machine management method according to claim 11, characterized in that, The first virtual machine corresponds to the vehicle's left rear cabin system or right rear cabin system, and the second virtual machine corresponds to the vehicle's central control and / or passenger system.

13. The virtual machine management method according to claim 1, characterized in that, The first processor is connected to at least one electronic control unit, and the message information is the message information that the first processor receives from the electronic control unit.

14. A method for managing virtual machines, characterized in that, The method includes: Receive message information from at least one virtual machine; Based on the message information and the preset message registry, the response target corresponding to the message information is determined, so as to transmit the message information to the response target; wherein, the preset message registry includes a mapping relationship between the message information type and the response target.

15. The virtual machine management method according to claim 14, characterized in that, The method includes: The response target of the message information is determined based on the message type of the message information and the preset message registration form.

16. The virtual machine management method according to claim 14, characterized in that, The method includes: When a corresponding virtual machine is found in the preset message registry based on the message type of the message information, the message information is sent to the virtual machine corresponding to the message information and the first processor.

17. The virtual machine management method according to claim 16, characterized in that, The method further includes: When a virtual machine corresponding to the message type of the message information cannot be found in the preset message registry, the message information is directly sent to the first processor.

18. The virtual machine management method according to claim 14, characterized in that, The message information is generated in response to the message information uploaded by the first processor.

19. A virtual machine management system, characterized in that, include: The system includes a service operating system, multiple virtual machines, and a first processor. The service operating system user receives message information uploaded by the first processor and determines the virtual machine corresponding to the message information based on the message information and a preset message registry, so as to pass the message information to the corresponding virtual machine. The preset message registry includes a mapping relationship between the message information type and the virtual machine.

20. A virtual machine management system, characterized in that, include: The system includes a service operating system, multiple virtual machines, and a first processor. The service operating system is configured to receive message information from at least one virtual machine and determine the response target corresponding to the message information based on the message information and a preset message registry, so as to transmit the message information to the response target. The preset message registry includes a mapping relationship between the type of response message information and the response target.

21. An electronic device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the virtual machine management method as described in any one of claims 1-18.

22. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed, implements the steps of the virtual machine management method as described in any one of claims 1-18.

23. A computer program product, characterized in that, It includes a computer program or instructions that are executed by a processor to implement the steps of the virtual machine management method according to any one of claims 1-18.

24. A vehicle, characterized in that, This includes a virtual machine management system as described in claim 19 or 20, an electronic device as described in claim 21, a computer-readable storage medium as described in claim 22, or a computer program product as described in claim 23.

Images