Vehicle-mounted inter-domain communication method and device, equipment and storage medium

Abstract

The embodiment of the invention relates to the technical field of vehicle communication, and discloses a vehicle-mounted inter-domain communication method, device and equipment and a storage medium, and the method comprises the steps that when a vehicle-mounted domain controller receives a first service request sent by another vehicle-mounted domain controller, the first service request is sent to the other vehicle-mounted domain controller; controlling the main virtual machine to determine a virtual machine entity responsible for providing a service corresponding to the first service request; if the service corresponding to the first service request is provided by the main virtual machine, controlling the main virtual machine to process the first service request; and if the service corresponding to the first service request is provided by the sub-virtual machine, controlling the main virtual machine to forward the first service request to the corresponding sub-virtual machine for processing. According to the technical scheme, the problems that in the prior art, communication efficiency between vehicle-mounted electronic control units is low, resource utilization is insufficient, and service discovery and request processing delay is long can be solved.

Description

Technical Field

[0001] This invention relates to the field of vehicle communication technology, specifically to a vehicle-to-everything (V2X) communication method, apparatus, device, and storage medium. Background Technology

[0002] With the rapid development of intelligent vehicle technology, in-vehicle domain controllers are evolving from traditional distributed architectures to highly integrated, virtualized architectures. In traditional architectures, subsystems such as the TBox (Telematics Box, in-vehicle communication module), instrument cluster domain, and infotainment domain are typically deployed as independent hardware, each running its own operating system and communication protocol stack (such as SOME / IP protocol). While this architecture has clearly defined functions, it has significant limitations: on the one hand, each subsystem requires independent configuration of an Ethernet IP address, consuming network bandwidth and leading to network resource redundancy; on the other hand, the broadcast mechanism of Service Discovery (SD) messages is frequently triggered during inter-domain communication, significantly increasing network load and communication latency. Summary of the Invention

[0003] In view of the above problems, embodiments of the present invention provide a method, apparatus, device and storage medium for inter-vehicle domain communication, which solves the problems of low communication efficiency, insufficient resource utilization and long delay in service discovery and request processing in the prior art.

[0004] According to one aspect of the present invention, a method for inter-domain communication in a vehicle is provided, wherein the vehicle's in-vehicle domain controller includes a master virtual machine, the master virtual machine includes a plurality of sub-virtual machines, the master virtual machine and the plurality of sub-virtual machines respectively correspond to different functional domains, and the method includes:

[0005] When the vehicle domain controller receives a first service request sent by another vehicle domain controller, it controls the master virtual machine to determine the virtual machine entity responsible for providing the service corresponding to the first service request;

[0006] If the service corresponding to the first service request is provided by the main virtual machine itself, then control the main virtual machine to process the first service request;

[0007] If the service corresponding to the first service request is provided by a sub-virtual machine, then the master virtual machine is controlled to forward the first service request to the corresponding sub-virtual machine for processing.

[0008] According to another aspect of the present invention, an inter-domain communication device for vehicles is provided, wherein the vehicle's domain controller includes a master virtual machine, the master virtual machine includes a plurality of sub-virtual machines, the master virtual machine and the plurality of sub-virtual machines respectively correspond to different functional domains, including:

[0009] The first control module is used to control the master virtual machine to determine the virtual machine entity responsible for providing the service corresponding to the first service request when the vehicle domain controller receives a first service request sent by another vehicle domain controller.

[0010] The second control module is used to control the main virtual machine to process the first service request if the service corresponding to the first service request is provided by the main virtual machine itself.

[0011] The third control module is used to control the main virtual machine to forward the first service request to the corresponding sub-virtual machine for processing if the service corresponding to the first service request is provided by the sub-virtual machine.

[0012] According to another aspect of the present invention, a vehicle-mounted inter-domain communication device is provided, comprising:

[0013] The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus.

[0014] The memory is used to store at least one executable instruction that causes the processor to perform the operation of the vehicle-to-domain communication method as described above.

[0015] According to another aspect of the present invention, a computer-readable storage medium is provided, the storage medium storing at least one executable instruction that causes an inter-vehicle domain communication device / apparatus to perform the operation of the inter-vehicle domain communication method as described above.

[0016] This invention, through the inclusion of multiple sub-virtual machines corresponding to different functional domains within a main virtual machine, achieves centralized management and scheduling of different functional domains within the vehicle domain controller. When a service request is received, the main virtual machine can determine which virtual machine entity is responsible for providing the service, ensuring that the service request is effectively routed to the correct service provider. If the main virtual machine itself provides the required service, it can process it directly, reducing intermediate steps and improving response speed and processing efficiency. For services not directly provided by the main virtual machine, the request can be forwarded to the corresponding sub-virtual machine, realizing the transmission of service requests between different functional domains. Through virtualization technology, the computing and network resources of the vehicle domain controller can be utilized more effectively, reducing hardware requirements and lowering costs. Centralizing service discovery in the main virtual machine reduces the broadcasting of service discovery messages in the network, simplifies the network topology, and reduces network complexity.

[0017] The above description is merely an overview of the technical solutions of the embodiments of the present invention. In order to better understand the technical means of the embodiments of the present invention and to implement them in accordance with the contents of the specification, and to make the above and other objects, features and advantages of the embodiments of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0018] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0019] Figure 1 This diagram illustrates the communication architecture of a cockpit domain control system based on virtualization technology in related technologies.

[0020] Figure 2 A flowchart illustrating a first embodiment of the vehicle-to-domain communication method provided by the present invention is shown.

[0021] Figure 3 A flowchart illustrating a second embodiment of the vehicle-to-domain communication method provided by the present invention is shown.

[0022] Figure 4 A schematic diagram of the communication architecture of the cockpit domain control system based on virtualization technology of the present invention is shown;

[0023] Figure 5 A schematic diagram of an embodiment of the vehicle-mounted inter-domain communication device provided by the present invention is shown;

[0024] Figure 6 A schematic diagram of an embodiment of the vehicle-mounted inter-domain communication device provided by the present invention is shown;

[0025] Figure 7 A structural schematic diagram of an embodiment of the vehicle provided by the present invention is shown. Detailed Implementation

[0026] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. Although exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein.

[0027] As the computing power of System-on-Chips (SoCs) used in vehicle domain control systems continues to improve, and driven by virtualization technology, modern vehicle domain controllers are beginning to use a single virtual machine software platform to run multiple systems simultaneously, such as TBox, instrument cluster, and entertainment domains. Each domain operates independently, deploys its own SOME / IP services, and communication is required between these domains and with external domains. While this independent domain controller model achieves functional isolation, it also brings a series of problems, including excessive network resource consumption and decentralized service management.

[0028] Figure 1 This diagram illustrates the communication architecture of a cockpit domain control system based on virtualization technology. The system utilizes the SOME / IP protocol to achieve communication between different domains. The diagram mainly includes the following components:

[0029] Intelligent driving domain and vehicle body domain: These two domains communicate with various virtual machines in the cockpit domain control system via the SOME / IP protocol.

[0030] Cockpit Domain Control System: This system consists of multiple virtual machines, each corresponding to a different functional domain, such as the TBox domain, entertainment domain, and instrument domain.

[0031] The TBox domain virtual machine includes a Service Discovery (SD) module and a Connection Service (SOME / IP proxy) module. The Service Discovery module is responsible for registering and discovering SOME / IP services in the TBox domain. The Connection Service module is responsible for forwarding service requests and responses.

[0032] The entertainment domain virtual machine also includes a service discovery (SD) module and a connection service (SOME / IP proxy) module. The service discovery module is responsible for registering and discovering SOME / IP services in the entertainment domain. The connection service module is responsible for forwarding service requests and responses.

[0033] The instrumentation domain virtual machine also includes a service discovery (SD) module and a connection service (SOME / IP proxy) module. The service discovery module is responsible for registering and discovering SOME / IP services in the instrumentation domain. The connection service module is responsible for forwarding service requests and responses.

[0034] The intelligent driving domain and the vehicle domain send service requests to the cockpit domain control system via the SOME / IP protocol. Each virtual machine in the cockpit domain control system processes the service request through its respective service discovery and connection service module, based on the content of the request.

[0035] In cockpit domain control systems based on virtualization technology, each functional domain (such as TBox, instrument cluster, entertainment system, etc.) is deployed as an independent virtual machine, and each virtual machine requires an independent service discovery (SD) module and a connection service (SOME / IP proxy) module. While this architecture ensures the logical isolation of functional domains, it leads to problems such as excessive network resource consumption and fragmented service distribution. Each virtual machine consumes Ethernet address resources and network bandwidth, multiple independently deployed SD modules cause a surge in service registration / discovery traffic, and redundant SOME / IP proxy layers further exacerbate the consumption of network bandwidth and processing resources.

[0036] Therefore, this invention achieves centralized service management and optimized communication efficiency by separating the Service Discovery (SD) module and the Connection Service (SOME / IP proxy) module from the virtual machines of each functional domain and centrally deploying them in the main virtual machine. Furthermore, this invention employs the vsock communication mechanism to further optimize inter-domain communication paths. Through this design, this invention effectively solves the technical problems of service dispersion, network resource redundancy, and communication latency inherent in traditional architectures, significantly improving the communication performance of the vehicle domain controller and the overall reliability of the system.

[0037] Figure 2 A flowchart illustrating a first embodiment of the vehicle-to-domain communication method of the present invention is shown. The vehicle's on-board domain controller includes a master virtual machine, which contains several sub-virtual machines. The master virtual machine and the sub-virtual machines correspond to different functional domains. This method is executed by the on-board domain controller. Figure 2 As shown, the method includes the following steps:

[0038] Step 210: When the vehicle domain controller receives a first service request from another vehicle domain controller, the master virtual machine determines the virtual machine entity responsible for providing the service corresponding to the first service request.

[0039] The vehicle's onboard domain controller deploys a master virtual machine, which is configured to run several sub-virtual machines. In this step, when the onboard domain controller receives a service request from another onboard domain controller (referred to as the first service request for clarity), the service discovery (SD) module in the master virtual machine is triggered to determine which virtual machine entity (whether the master virtual machine itself or a sub-virtual machine) is responsible for providing the service corresponding to the first service request.

[0040] Step 220: If the service corresponding to the first service request is provided by the main virtual machine itself, then control the main virtual machine to process the first service request.

[0041] In this step, if the service discovery module determines that the service corresponding to the first service request can be provided by the main virtual machine itself, the main virtual machine will directly process the first service request.

[0042] Step 230: If the service corresponding to the first service request is provided by the sub-virtual machine, then control the main virtual machine to forward the first service request to the corresponding sub-virtual machine for processing.

[0043] If the service requested by the first service request needs to be provided by a certain sub-virtual machine, the master virtual machine will forward the first service request to the corresponding sub-virtual machine for processing.

[0044] These three steps enable efficient communication and collaboration between different virtual machines within the vehicle domain controller, optimize the service request processing flow, and improve the overall system response speed and reliability. Furthermore, by centrally managing service discovery and request forwarding, this method also helps reduce network resource consumption and lower system complexity.

[0045] This invention, through the inclusion of multiple sub-virtual machines corresponding to different functional domains within a main virtual machine, achieves centralized management and scheduling of different functional domains within the vehicle domain controller. When a service request is received, the main virtual machine can determine which virtual machine entity is responsible for providing the service, ensuring that the service request is effectively routed to the correct service provider. If the main virtual machine itself provides the required service, it can process it directly, reducing intermediate steps and improving response speed and processing efficiency. For services not directly provided by the main virtual machine, the request can be forwarded to the corresponding sub-virtual machine, realizing the transmission of service requests between different functional domains. Through virtualization technology, the computing and network resources of the vehicle domain controller can be utilized more effectively, reducing hardware requirements and lowering costs. Centralizing service discovery in the main virtual machine reduces the broadcasting of service discovery messages in the network, simplifies the network topology, and reduces network complexity.

[0046] Figure 3 A flowchart illustrating another embodiment of the vehicle-to-domain communication method of the present invention is shown. The vehicle's on-board domain controller includes a master virtual machine, which contains several sub-virtual machines. The master virtual machine and the sub-virtual machines correspond to different functional domains. This method is executed by the on-board domain controller. Figure 3 As shown, the method includes the following steps:

[0047] Step 310: When the service discovery module receives the first service request, it controls the service discovery module to query the internal database based on the first service request to determine the virtual machine entity responsible for providing the service corresponding to the first service request.

[0048] In this step, a service discovery module is deployed in the main virtual machine. When the service discovery module receives a first service request, it uses the information contained in the request (such as service identifier, service type, etc.) to query an internally maintained database. This internal database contains service information provided by each virtual machine entity, including service descriptions, the virtual machine entity where the service resides, and how to access the service. Service discovery is a crucial step in enabling inter-domain communication within the vehicle, ensuring that service requests are accurately delivered to the appropriate handler.

[0049] In traditional architectures, each functional domain (such as TBox, instrument cluster, entertainment system, etc.) has its own service interface. This fragmented service interface complicates service management and invocation, increasing system complexity and maintenance costs. By providing a unified service interface, service discovery and invocation can be performed regardless of which domain the service request originates from within the vehicle. This unified service interface simplifies service management and invocation processes, resolving the problem of service fragmentation.

[0050] By centrally deploying the Service Discovery (SD) module to the main virtual machine, the number of service discovery messages can be reduced. Because all service discovery is handled centrally in the main virtual machine, there is no need to perform service discovery in each functional domain, thus reducing the number of broadcast service discovery messages.

[0051] In an alternative approach, before the control service discovery module queries the internal database based on the first service request to determine the virtual machine entity responsible for providing the service corresponding to the first service request, the in-vehicle domain communication method of the present invention may further include the following steps:

[0052] When the service discovery module receives a service registration request from any sub-virtual machine through the inter-virtual machine communication mechanism, it triggers the service discovery module to parse the service registration request and stores the parsed service registration information in the internal database for subsequent querying to determine the virtual machine entity responsible for providing the service.

[0053] In this implementation, when any child virtual machine starts up or a new service needs to be provided, it can send a service registration request to the service discovery module. This request is sent through the inter-virtual machine communication mechanism, ensuring that the request can be securely and efficiently passed from the child virtual machine to the service discovery module in the main virtual machine.

[0054] After receiving a service registration request, the service discovery module triggers an internal parsing process. This process is responsible for analyzing the content of the service registration request and extracting key information, such as service type, service name, and service provider identifier (such as virtual machine ID or IP address).

[0055] The parsed service registration information is stored in the internal database of the service discovery module. This database serves as a central repository for service information, recording all registered services and their corresponding provider information. The stored information is used for subsequent service request processing. When other domains or virtual machines require a service, the service discovery module can quickly query this database to determine which virtual machine entity is responsible for providing that service. Centralized management of service registration information helps to allocate and utilize network resources more efficiently.

[0056] Step 320: If the service corresponding to the first service request is provided by the main virtual machine itself, then control the main virtual machine to process the first service request.

[0057] In one alternative approach, if the service corresponding to the first service request is provided by a sub-virtual machine, the controlling master virtual machine forwards the first service request to the corresponding sub-virtual machine for processing. This may specifically include the following steps:

[0058] If the service corresponding to the first service request is provided by a sub-virtual machine, the controlling master virtual machine forwards the first service request to the corresponding sub-virtual machine for processing through the inter-virtual machine communication mechanism.

[0059] In this embodiment, a connection service module is deployed in the main virtual machine. After the service discovery module determines that the service corresponding to the first service request is provided by the sub-virtual machine, it sends the first service request to the connection service module. The connection service module then forwards the first service request to the corresponding sub-virtual machine for processing through the inter-virtual machine communication mechanism. By centrally deploying the connection service (SOME / IP proxy) module in the main virtual machine, the repetitive communication logic in each sub-virtual machine can be reduced, thereby simplifying the entire network architecture.

[0060] In one alternative approach, the inter-virtual machine communication mechanism includes: using virtual socket technology to enable communication between the main virtual machine and several sub-virtual machines.

[0061] Inter-virtual machine communication mechanisms utilize virtual sockets (VSock) technology to enable communication between the main virtual machine and several child virtual machines. Virtual sockets are a highly efficient virtualization communication technology that allows virtual machines to communicate directly without going through the host machine's network stack. Because VSock does not require allocating a separate network interface and IP address for each virtual machine, it simplifies network configuration and management. VSock also reduces the demand on host machine network resources, thereby improving overall resource utilization.

[0062] Step 330: If the service corresponding to the first service request is provided by the sub-virtual machine, then control the main virtual machine to forward the first service request to the corresponding sub-virtual machine for processing.

[0063] In an optional embodiment, the vehicle-to-domain communication method of the present invention may further include the following steps:

[0064] When the main virtual machine receives a second service request from any child virtual machine, it controls the main virtual machine to determine the target entity responsible for providing the service corresponding to the second service request.

[0065] If the service corresponding to the second service request is provided by the main virtual machine itself, then control the main virtual machine to process the second service request;

[0066] If the service corresponding to the second service request is provided by another sub-virtual machine, then the main virtual machine will forward the second service request to the other sub-virtual machine for processing.

[0067] If the service corresponding to the second service request is provided by another vehicle domain controller, the master virtual machine will forward the second service request to the other vehicle domain controller for processing.

[0068] In this implementation, when the master virtual machine receives a second service request from any of the child virtual machines, it first determines which entity (the master virtual machine itself, another child virtual machine, or another vehicle domain controller) is responsible for providing the service corresponding to the request. If it is determined that the service corresponding to the second service request can be provided by the master virtual machine itself, then the master virtual machine will directly process the service request. If the service corresponding to the second service request needs to be provided by another child virtual machine, the master virtual machine will forward the service request to the corresponding child virtual machine for processing through an inter-virtual machine communication mechanism (such as vsock). If the service corresponding to the second service request needs to be provided by another vehicle domain controller, the master virtual machine will forward the service request to the other vehicle domain controller for processing through the vehicle network. By centrally managing the routing and forwarding of service requests, it helps to reduce network resource consumption and lower system complexity.

[0069] In one alternative approach, the vehicle domain controller is a cockpit domain controller, the main virtual machine is an instrument domain main virtual machine corresponding to the instrument domain, and the sub-virtual machines include TBox domain sub-virtual machines corresponding to the TBox domain and entertainment domain sub-virtual machines corresponding to the entertainment domain.

[0070] Figure 4This diagram illustrates the communication architecture of the cockpit domain control system based on virtualization technology according to the present invention. As shown, the service discovery module resides in the main virtual machine of the instrument cluster domain and communicates with the sub-virtual machines of the TBox and entertainment domains via the vsock communication mechanism. When a sub-virtual machine of the TBox or entertainment domain needs to register a service, it sends a service registration request to the service discovery module. Upon receiving the request, the service discovery module parses the service registration information in the request and stores it in its internal database. When the intelligent driving domain or the vehicle body domain needs to use these services, it sends a service request. The service discovery module searches for the corresponding service provider information in its internal database based on the requested service type and forwards the request to the corresponding sub-virtual machine for processing. After processing the request, the sub-virtual machine forwards the response to the requester. Specifically, the TBox domain SOME / IP service module is responsible for providing the services required for vehicle communication with external networks. The entertainment domain SOME / IP service module is responsible for providing services related to the in-vehicle entertainment system, such as audio and video playback. The instrument cluster domain SOME / IP service module is responsible for providing services related to the vehicle's instrument display. The SD vsock channel is used by sub-virtual machines (such as TBox domain sub-virtual machines and entertainment domain sub-virtual machines) to register the services they provide with the Service Discovery (SD) module in the main virtual machine. Connecting to the vsock channel is used to forward service requests and responses. Once the service discovery module determines which sub-virtual machine should handle a service request, it forwards the request to the appropriate sub-virtual machine through this channel. Similarly, after processing the request, the sub-virtual machine returns the response to the requester through this channel. The Unix vsock channel is used for direct communication between the connection service (SOME / IP proxy) module and the instrumentation domain SOME / IP service module. Unix vsock provides an inter-process communication mechanism, allowing communication between different processes or services within the main virtual machine.

[0071] This invention achieves unified backend integration of SOME / IP services for TBox, metering, and entertainment domains by employing the vsock communication mechanism in virtualization technology. In this architecture, the metering domain, as the primary SOME / IP service, is responsible for distributing requests from outside the domain to the TBox and entertainment domain SOME / IP services within the virtual machine via the vsock channel. This eliminates the need for TBox and entertainment domains to handle Service Discovery (SD) messages, thus simplifying their responsibilities. By using vsock communication, this invention optimizes the number of connections in the Ethernet network, reducing the consumption of Ethernet IP addresses and network bandwidth.

[0072] This invention, through the inclusion of multiple sub-virtual machines corresponding to different functional domains within a main virtual machine, achieves centralized management and scheduling of different functional domains within the vehicle domain controller. When a service request is received, the main virtual machine can determine which virtual machine entity is responsible for providing the service, ensuring that the service request is effectively routed to the correct service provider. If the main virtual machine itself provides the required service, it can process it directly, reducing intermediate steps and improving response speed and processing efficiency. For services not directly provided by the main virtual machine, the request can be forwarded to the corresponding sub-virtual machine, realizing the transmission of service requests between different functional domains. Through virtualization technology, the computing and network resources of the vehicle domain controller can be utilized more effectively, reducing hardware requirements and lowering costs. Centralizing service discovery in the main virtual machine reduces the broadcasting of service discovery messages in the network, simplifies the network topology, and reduces network complexity.

[0073] Figure 5 A schematic diagram of an embodiment of the vehicle-to-domain communication device of the present invention is shown. The vehicle's on-board domain controller includes a main virtual machine, which contains several sub-virtual machines. The main virtual machine and the sub-virtual machines correspond to different functional domains. For example... Figure 5 As shown, the device 500 includes: a first control module 510, a second control module 520 and a third control module 530.

[0074] The first control module is used to control the main virtual machine to determine the virtual machine entity responsible for providing the service corresponding to the first service request when the vehicle domain controller receives a first service request sent by another vehicle domain controller.

[0075] The second control module is used to control the main virtual machine to process the first service request if the service corresponding to the first service request is provided by the main virtual machine itself.

[0076] The third control module is used to control the main virtual machine to forward the first service request to the corresponding sub-virtual machine for processing if the service corresponding to the first service request is provided by the sub-virtual machine.

[0077] In one alternative approach, a service discovery module is deployed in the main virtual machine, and the first control module is specifically used for:

[0078] When the service discovery module receives the first service request, it controls the service discovery module to query the internal database based on the first service request to determine the virtual machine entity responsible for providing the service corresponding to the first service request.

[0079] In one alternative embodiment, the in-vehicle inter-domain communication device of the present invention is further used for:

[0080] When the service discovery module receives a service registration request from any sub-virtual machine through the inter-virtual machine communication mechanism, it triggers the service discovery module to parse the service registration request and stores the parsed service registration information in the internal database for subsequent querying to determine the virtual machine entity responsible for providing the service.

[0081] In one alternative approach, the third control module is specifically used for:

[0082] If the service corresponding to the first service request is provided by a sub-virtual machine, the controlling master virtual machine forwards the first service request to the corresponding sub-virtual machine for processing through the inter-virtual machine communication mechanism.

[0083] In one alternative embodiment, the in-vehicle inter-domain communication device of the present invention is further used for:

[0084] When the main virtual machine receives a second service request from any child virtual machine, it controls the main virtual machine to determine the target entity responsible for providing the service corresponding to the second service request.

[0085] If the service corresponding to the second service request is provided by the main virtual machine itself, then control the main virtual machine to process the second service request;

[0086] If the service corresponding to the second service request is provided by another sub-virtual machine, then the main virtual machine will forward the second service request to the other sub-virtual machine for processing.

[0087] If the service corresponding to the second service request is provided by another vehicle domain controller, the master virtual machine will forward the second service request to the other vehicle domain controller for processing.

[0088] In one alternative approach, the inter-virtual machine communication mechanism includes: using virtual socket technology to enable communication between the main virtual machine and several sub-virtual machines.

[0089] In one alternative approach, the vehicle domain controller is a cockpit domain controller, the main virtual machine is an instrument domain main virtual machine corresponding to the instrument domain, and the sub-virtual machines include TBox domain sub-virtual machines corresponding to the TBox domain and entertainment domain sub-virtual machines corresponding to the entertainment domain.

[0090] This invention, through the inclusion of multiple sub-virtual machines corresponding to different functional domains within a main virtual machine, achieves centralized management and scheduling of different functional domains within the vehicle domain controller. When a service request is received, the main virtual machine can determine which virtual machine entity is responsible for providing the service, ensuring that the service request is effectively routed to the correct service provider. If the main virtual machine itself provides the required service, it can process it directly, reducing intermediate steps and improving response speed and processing efficiency. For services not directly provided by the main virtual machine, the request can be forwarded to the corresponding sub-virtual machine, realizing the transmission of service requests between different functional domains. Through virtualization technology, the computing and network resources of the vehicle domain controller can be utilized more effectively, reducing hardware requirements and lowering costs. Centralizing service discovery in the main virtual machine reduces the broadcasting of service discovery messages in the network, simplifies the network topology, and reduces network complexity.

[0091] Figure 6 The diagram shows a structural schematic of an embodiment of the vehicle-to-domain communication device provided by the present invention. The specific embodiments of the present invention do not limit the specific implementation of the vehicle-to-domain communication device.

[0092] like Figure 6 As shown, the vehicle-mounted inter-domain communication device may include: a processor 602, a communication interface 604, a memory 606, and a communication bus 608.

[0093] The processor 602, communication interface 604, and memory 606 communicate with each other via communication bus 608. Communication interface 604 is used to communicate with other network elements, such as clients or other servers. Processor 602 executes program 610, specifically performing the relevant steps described in the embodiment of the method for inter-domain communication in vehicles.

[0094] Specifically, program 610 may include program code, which includes computer-executable instructions.

[0095] Processor 602 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present invention. The one or more processors included in the vehicle-to-domain communication device may be processors of the same type, such as one or more CPUs; or they may be processors of different types, such as one or more CPUs and one or more ASICs.

[0096] Memory 606 is used to store program 610. Memory 606 may include high-speed RAM memory, and may also include non-volatile memory, such as at least one disk storage device.

[0097] The vehicle's onboard domain controller contains a master virtual machine, which contains several sub-virtual machines. The master virtual machine and the sub-virtual machines correspond to different functional domains. Specifically, program 610 can be called by processor 602 to enable the onboard domain communication device to perform the following operations:

[0098] When the vehicle domain controller receives a first service request from another vehicle domain controller, the master virtual machine determines the virtual machine entity responsible for providing the service corresponding to the first service request.

[0099] If the service corresponding to the first service request is provided by the main virtual machine itself, then control the main virtual machine to process the first service request;

[0100] If the service corresponding to the first service request is provided by a sub-virtual machine, then the master virtual machine will forward the first service request to the corresponding sub-virtual machine for processing.

[0101] In an alternative approach, a service discovery module is deployed in the main virtual machine, and program 610 is invoked by processor 602 to cause the on-board inter-domain communication device to perform the following operations:

[0102] When the service discovery module receives the first service request, it controls the service discovery module to query the internal database based on the first service request to determine the virtual machine entity responsible for providing the service corresponding to the first service request.

[0103] In an alternative manner, program 610 is invoked by processor 602 to cause the on-board inter-domain communication device to perform the following operations:

[0104] When the service discovery module receives a service registration request from any sub-virtual machine through the inter-virtual machine communication mechanism, it triggers the service discovery module to parse the service registration request and stores the parsed service registration information in the internal database for subsequent querying to determine the virtual machine entity responsible for providing the service.

[0105] In an alternative manner, program 610 is invoked by processor 602 to cause the on-board inter-domain communication device to perform the following operations:

[0106] If the service corresponding to the first service request is provided by a sub-virtual machine, the controlling master virtual machine forwards the first service request to the corresponding sub-virtual machine for processing through the inter-virtual machine communication mechanism.

[0107] In an alternative manner, program 610 is invoked by processor 602 to cause the on-board inter-domain communication device to perform the following operations:

[0108] If the service corresponding to the first service request is provided by a sub-virtual machine, the controlling master virtual machine forwards the first service request to the corresponding sub-virtual machine for processing through the inter-virtual machine communication mechanism.

[0109] When the main virtual machine receives a second service request from any child virtual machine, it controls the main virtual machine to determine the target entity responsible for providing the service corresponding to the second service request.

[0110] If the service corresponding to the second service request is provided by the main virtual machine itself, then control the main virtual machine to process the second service request;

[0111] If the service corresponding to the second service request is provided by another sub-virtual machine, then the main virtual machine will forward the second service request to the other sub-virtual machine for processing.

[0112] If the service corresponding to the second service request is provided by another vehicle domain controller, the master virtual machine will forward the second service request to the other vehicle domain controller for processing.

[0113] In one alternative approach, the inter-virtual machine communication mechanism includes: using virtual socket technology to enable communication between the main virtual machine and several sub-virtual machines.

[0114] In one alternative approach, the vehicle domain controller is a cockpit domain controller, the main virtual machine is an instrument domain main virtual machine corresponding to the instrument domain, and the sub-virtual machines include TBox domain sub-virtual machines corresponding to the TBox domain and entertainment domain sub-virtual machines corresponding to the entertainment domain.

[0115] This invention, through the inclusion of multiple sub-virtual machines corresponding to different functional domains within a main virtual machine, achieves centralized management and scheduling of different functional domains within the vehicle domain controller. When a service request is received, the main virtual machine can determine which virtual machine entity is responsible for providing the service, ensuring that the service request is effectively routed to the correct service provider. If the main virtual machine itself provides the required service, it can process it directly, reducing intermediate steps and improving response speed and processing efficiency. For services not directly provided by the main virtual machine, the request can be forwarded to the corresponding sub-virtual machine, realizing the transmission of service requests between different functional domains. Through virtualization technology, the computing and network resources of the vehicle domain controller can be utilized more effectively, reducing hardware requirements and lowering costs. Centralizing service discovery in the main virtual machine reduces the broadcasting of service discovery messages in the network, simplifies the network topology, and reduces network complexity.

[0116] Figure 7 A structural schematic diagram of an embodiment of the vehicle provided by the present invention is shown. For example... Figure 7As shown, the vehicle 700 includes: one or more processors and communication interfaces;

[0117] The processor is used to execute the steps in the above embodiments of the vehicle-to-domain communication method.

[0118] This invention, through the inclusion of multiple sub-virtual machines corresponding to different functional domains within a main virtual machine, achieves centralized management and scheduling of different functional domains within the vehicle domain controller. When a service request is received, the main virtual machine can determine which virtual machine entity is responsible for providing the service, ensuring that the service request is effectively routed to the correct service provider. If the main virtual machine itself provides the required service, it can process it directly, reducing intermediate steps and improving response speed and processing efficiency. For services not directly provided by the main virtual machine, the request can be forwarded to the corresponding sub-virtual machine, realizing the transmission of service requests between different functional domains. Through virtualization technology, the computing and network resources of the vehicle domain controller can be utilized more effectively, reducing hardware requirements and lowering costs. Centralizing service discovery in the main virtual machine reduces the broadcasting of service discovery messages in the network, simplifies the network topology, and reduces network complexity.

[0119] This invention provides a computer-readable storage medium storing at least one executable instruction that, when executed on a vehicle-to-domain communication device / app, causes the device / app to perform the vehicle-to-domain communication method in any of the above-described method embodiments.

[0120] The vehicle's onboard domain controller contains a master virtual machine, which in turn contains several sub-virtual machines. The master virtual machine and the sub-virtual machines correspond to different functional domains, and the executable instructions can be used to cause the onboard domain communication devices / devices to perform the following operations:

[0121] When the vehicle domain controller receives a first service request from another vehicle domain controller, the master virtual machine determines the virtual machine entity responsible for providing the service corresponding to the first service request.

[0122] If the service corresponding to the first service request is provided by the main virtual machine itself, then control the main virtual machine to process the first service request;

[0123] If the service corresponding to the first service request is provided by a sub-virtual machine, then the master virtual machine will forward the first service request to the corresponding sub-virtual machine for processing.

[0124] In one alternative approach, a service discovery module is deployed in the main virtual machine, which can execute instructions to cause the in-vehicle inter-domain communication devices / devices to perform the following operations:

[0125] When the service discovery module receives the first service request, it controls the service discovery module to query the internal database based on the first service request to determine the virtual machine entity responsible for providing the service corresponding to the first service request.

[0126] In one alternative approach, the executable instructions cause the on-board inter-domain communication device / app to perform the following operations:

[0127] When the service discovery module receives a service registration request from any sub-virtual machine through the inter-virtual machine communication mechanism, it triggers the service discovery module to parse the service registration request and stores the parsed service registration information in the internal database for subsequent querying to determine the virtual machine entity responsible for providing the service.

[0128] In one alternative approach, the executable instructions cause the on-board inter-domain communication device / app to perform the following operations:

[0129] If the service corresponding to the first service request is provided by a sub-virtual machine, the controlling master virtual machine forwards the first service request to the corresponding sub-virtual machine for processing through the inter-virtual machine communication mechanism.

[0130] In one alternative approach, the executable instructions cause the on-board inter-domain communication device / app to perform the following operations:

[0131] When the main virtual machine receives a second service request from any child virtual machine, it controls the main virtual machine to determine the target entity responsible for providing the service corresponding to the second service request.

[0132] If the service corresponding to the second service request is provided by the main virtual machine itself, then control the main virtual machine to process the second service request;

[0133] If the service corresponding to the second service request is provided by another sub-virtual machine, then the main virtual machine will forward the second service request to the other sub-virtual machine for processing.

[0134] If the service corresponding to the second service request is provided by another vehicle domain controller, the master virtual machine will forward the second service request to the other vehicle domain controller for processing.

[0135] In one alternative approach, the inter-virtual machine communication mechanism includes: using virtual socket technology to enable communication between the main virtual machine and several sub-virtual machines.

[0136] In one alternative approach, the vehicle domain controller is a cockpit domain controller, the main virtual machine is an instrument domain main virtual machine corresponding to the instrument domain, and the sub-virtual machines include TBox domain sub-virtual machines corresponding to the TBox domain and entertainment domain sub-virtual machines corresponding to the entertainment domain.

[0137] This invention, through the inclusion of multiple sub-virtual machines corresponding to different functional domains within a main virtual machine, achieves centralized management and scheduling of different functional domains within the vehicle domain controller. When a service request is received, the main virtual machine can determine which virtual machine entity is responsible for providing the service, ensuring that the service request is effectively routed to the correct service provider. If the main virtual machine itself provides the required service, it can process it directly, reducing intermediate steps and improving response speed and processing efficiency. For services not directly provided by the main virtual machine, the request can be forwarded to the corresponding sub-virtual machine, realizing the transmission of service requests between different functional domains. Through virtualization technology, the computing and network resources of the vehicle domain controller can be utilized more effectively, reducing hardware requirements and lowering costs. Centralizing service discovery in the main virtual machine reduces the broadcasting of service discovery messages in the network, simplifies the network topology, and reduces network complexity.

[0138] The algorithms or displays provided herein are not inherently related to any particular computer, virtual system, or other device. Furthermore, the embodiments of this invention are not directed to any particular programming language.

[0139] Numerous specific details are set forth in the specification provided herein. However, it will be understood that embodiments of the invention may be practiced without these specific details. Similarly, for the sake of brevity and to aid in understanding one or more aspects of the invention, in the description of exemplary embodiments of the invention above, various features of the embodiments are sometimes grouped together in a single embodiment, figure, or description thereof. The claims, which follow the detailed description, are hereby expressly incorporated into that detailed description, wherein each claim itself is a separate embodiment of the invention.

[0140] Those skilled in the art will understand that the modules in the device of the embodiment can be adaptively changed and placed in one or more devices different from that embodiment. Modules, units, or components in the embodiment can be combined into a single module, unit, or component, and further, they can be divided into multiple sub-modules, sub-units, or sub-components, except that at least some of such features and / or processes or units are mutually exclusive.

[0141] It should be noted that the above embodiments are illustrative of the invention and not restrictive, and that those skilled in the art can devise alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses should not be construed as limiting the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by the same item of hardware. The use of the words first, second, and third, etc., does not indicate any order. These words can be interpreted as names. The steps in the above embodiments, unless otherwise specified, should not be construed as limiting the order of execution.

Claims

1. A method for inter-domain communication between vehicles, characterized in that, The vehicle's onboard domain controller includes a master virtual machine, which contains several sub-virtual machines. The master virtual machine and the sub-virtual machines each correspond to a different functional domain. The method includes: When the vehicle domain controller receives a first service request sent by another vehicle domain controller, it controls the master virtual machine to determine the virtual machine entity responsible for providing the service corresponding to the first service request; If the service corresponding to the first service request is provided by the main virtual machine itself, then control the main virtual machine to process the first service request; If the service corresponding to the first service request is provided by a sub-virtual machine, then the master virtual machine is controlled to forward the first service request to the corresponding sub-virtual machine for processing.

2. The method according to claim 1, characterized in that, The primary virtual machine is equipped with a service discovery module. When the vehicle domain controller receives a first service request from another vehicle domain controller, it controls the primary virtual machine to determine the virtual machine entity responsible for providing the service corresponding to the first service request, including: When the service discovery module receives the first service request, it controls the service discovery module to query the internal database based on the first service request to determine the virtual machine entity responsible for providing the service corresponding to the first service request.

3. The method according to claim 2, characterized in that, Before the method controls the service discovery module to query the internal database based on the first service request to determine the virtual machine entity responsible for providing the service corresponding to the first service request, the method further includes: When the service discovery module receives a service registration request from any sub-virtual machine through the inter-virtual machine communication mechanism, it triggers the parsing process of the service registration request and stores the parsed service registration information in the internal database for subsequent querying to determine the virtual machine entity responsible for providing the service.

4. The method according to claim 1, characterized in that, If the service corresponding to the first service request is provided by a sub-virtual machine, then controlling the main virtual machine to forward the first service request to the corresponding sub-virtual machine for processing includes: If the service corresponding to the first service request is provided by a sub-virtual machine, then the main virtual machine is controlled to forward the first service request to the corresponding sub-virtual machine for processing through the inter-virtual machine communication mechanism.

5. The method according to any one of claims 1-4, characterized in that, The method further includes: When the main virtual machine receives a second service request sent by any child virtual machine, it controls the main virtual machine to determine the target entity responsible for providing the service corresponding to the second service request; If the service corresponding to the second service request is provided by the main virtual machine itself, then control the main virtual machine to process the second service request; If the service corresponding to the second service request is provided by another sub-virtual machine, then the main virtual machine is controlled to forward the second service request to the other sub-virtual machine for processing; If the service corresponding to the second service request is provided by the other vehicle domain controller, then control the master virtual machine to forward the second service request to the other vehicle domain controller for processing.

6. The method according to any one of claims 1-4, characterized in that, The inter-virtual machine communication mechanism includes: using virtual socket technology to realize communication between the main virtual machine and the several sub-virtual machines.

7. The method according to any one of claims 1-4, characterized in that, The vehicle domain controller is a cockpit domain controller, the main virtual machine is an instrument domain main virtual machine corresponding to the instrument domain, and the plurality of sub-virtual machines include a TBox domain sub-virtual machine corresponding to the TBox domain and an entertainment domain sub-virtual machine corresponding to the entertainment domain.

8. A vehicle-mounted inter-domain communication device, characterized in that, The vehicle's onboard domain controller includes a master virtual machine, which contains several sub-virtual machines. The master virtual machine and the sub-virtual machines each correspond to a different functional domain. The device includes: The first control module is used to control the master virtual machine to determine the virtual machine entity responsible for providing the service corresponding to the first service request when the vehicle domain controller receives a first service request sent by another vehicle domain controller. The second control module is used to control the main virtual machine to process the first service request if the service corresponding to the first service request is provided by the main virtual machine itself. The third control module is used to control the main virtual machine to forward the first service request to the corresponding sub-virtual machine for processing if the service corresponding to the first service request is provided by the sub-virtual machine.

9. A vehicle-mounted inter-domain communication device, characterized in that, include: The processor, memory, communication interface, and communication bus are provided, wherein the processor, memory, and communication interface communicate with each other via the communication bus. The memory is used to store at least one executable instruction that causes the processor to perform the operation of the vehicle-to-domain communication method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The storage medium stores at least one executable instruction, which, when executed on the vehicle-to-domain communication device / apparatus, causes the vehicle-to-domain communication device / apparatus to perform the operation of the vehicle-to-domain communication method as described in any one of claims 1-7.

Images