Vehicle-mounted middleware and its control methods, control devices, media, products and vehicles

By using in-vehicle middleware to achieve precise communication connections and targeted data transmission, the problems of resource waste and latency in in-vehicle systems are solved, and the accuracy of message distribution and system stability are improved.

CN123123407APending Publication Date: 2026-11-17CHERY AUTOMOBILE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611547369.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-30
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing in-vehicle systems rely on a centralized node for full registry maintenance and cross-process communication in high-concurrency, low-latency scenarios, resulting in high computational resource consumption, system main thread blocking, and response delays.

Method used

It provides in-vehicle middleware that establishes precise communication connections in response to subscription requests from communication nodes, enabling targeted transmission of vehicle business messages, avoiding full broadcasts and blind connections, achieving a one-way data path, and ensuring real-time targeted transmission of messages.

Benefits of technology

It improves the effectiveness and accuracy of cross-process message relay and distribution, reduces resource waste and communication congestion, and enhances the robustness of the system and the accuracy of data processing.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123407A_ABST
    Figure CN123123407A_ABST
Patent Text Reader

Abstract

This disclosure provides in-vehicle middleware and its control methods, control devices, media, products, and vehicles, relating to the field of vehicle technology, particularly the field of smart cockpit technology, and capable of improving the accuracy and efficiency of message distribution between cross-processes within an in-vehicle system. The in-vehicle middleware is used to establish a communication connection with a second communication node indicated in a subscription request in response to a subscription request from a first communication node; wherein, the subscription request is used to request subscription to vehicle service messages corresponding to a target topic in the second communication node; the target topic is one of the established subscription topics in the second communication node, used to indicate the information type of the vehicle service message; the subscription request is forwarded to the second communication node so that the second communication node returns the vehicle service message; after receiving the vehicle service message, the vehicle service message is sent to the first communication node.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This disclosure relates to the field of vehicle technology, and more particularly to the field of intelligent cockpit technology, specifically to in-vehicle middleware and its control methods, control devices, media, products and vehicles. Background Technology

[0002] With the rapid development of smart cockpit technology, in-vehicle infotainment systems have become the core carrier of human-machine interaction in vehicles, undertaking the collaborative tasks of navigation, multimedia, vehicle settings, and other multi-functional modules. To ensure efficient data flow between these modules, in-vehicle systems rely on stable cross-process communication mechanisms to transmit control commands and status information, ensuring a smooth interactive experience for users while driving. In high-concurrency, low-latency in-vehicle applications, related technologies often rely on a centralized node for full registry maintenance and distribution through traversal matching.

[0003] However, this model requires a lot of computing resources to match receivers when distributing messages, which can easily cause the main thread of the system to be blocked, resulting in lag and response delays in the operation of the central control screen. Therefore, there is an urgent need for a more efficient cross-process data distribution method. Summary of the Invention

[0004] This disclosure provides vehicle-mounted middleware and its control method, control device, medium, product, and vehicle, which can improve the accuracy and efficiency of message distribution between processes within the vehicle system.

[0005] In a first aspect, this application provides an in-vehicle middleware deployed on a first communication node. The in-vehicle middleware is used to: establish a communication connection with a second communication node indicated in the subscription request in response to a subscription request from the first communication node; wherein the subscription request is used to request subscription to vehicle service messages corresponding to a target topic in the second communication node; the target topic is one of the subscription topics already established in the second communication node, used to indicate the information type of the vehicle service message; forward the subscription request to the second communication node so that the second communication node returns the vehicle service message; and after receiving the vehicle service message, send the vehicle service message to the first communication node.

[0006] The vehicle-mounted middleware provided in this application can establish a communication connection with the second communication node indicated in the subscription request in response to the subscription request of the first communication node. It also works with the vehicle service messages corresponding to the target topic in the second communication node subscribed to in the subscription request. This allows the vehicle-mounted middleware to more accurately locate and connect to the target communication node providing the service based on the specific type of service information, thereby avoiding resource waste and communication congestion caused by full broadcasting or blind connections. Based on this, by forwarding the subscription request to the second communication node to trigger its return of vehicle service messages, a one-way data path is established from the subscriber to the sender, ensuring that vehicle service messages under the target topic can be transmitted to the first communication node in real time and in a targeted manner, thereby improving the relay effectiveness and distribution accuracy of cross-process vehicle service messages.

[0007] In some possible implementations, establishing a communication connection with the second communication node indicated in the subscription request includes: determining a first process identifier of the service process distributing vehicle service messages on the second communication node; and establishing a communication connection with the second communication node based on the first process identifier.

[0008] According to the above implementation method, by defining the first process identifier of the service process that distributes vehicle service messages on the second communication node to establish a communication connection, the vehicle middleware can directly locate the specific service process, thereby avoiding invalid interaction with other non-target processes under the same node and improving the accuracy and efficiency of communication establishment.

[0009] In some possible implementations, a second process identifier is embedded in the subscription request forwarded to the second communication node, so that the second communication node can embed the second process identifier into the vehicle service message when returning the vehicle service message; the second process identifier is used to indicate the process identifier of the service process receiving the vehicle service message on the first communication node; receiving the vehicle service message includes: when receiving communication information returned by the second communication node, and the process identifier in the communication information is consistent with the second process identifier, the communication information is identified as a vehicle service message.

[0010] According to the above implementation method, by embedding a second process identifier indicating the receiving service process on the first communication node in the subscription request forwarded to the second communication node, the second communication node can embed this identifier when returning vehicle service messages. The vehicle middleware then confirms the validity of the message by comparing whether the process identifier in the received communication information is consistent with the second process identifier. This achieves secondary verification and accurate delivery of messages at the receiving end, effectively preventing data confusion and error handling between different service processes under the same communication node, and further ensuring the security of message distribution.

[0011] In some possible implementations, after receiving a subscription request, the second communication node selects the subscription record corresponding to the target topic from the subscription relationship table; and synchronously returns the vehicle service message to the vehicle middleware and other vehicle middleware that have previously subscribed to vehicle service messages in the subscription record; the other vehicle middleware is deployed on other communication nodes besides the first and second communication nodes.

[0012] According to the above implementation method, after receiving the subscription request, the second communication node selects the subscription record corresponding to the target topic from the subscription relationship table and synchronously returns vehicle business messages to the vehicle middleware and other previously subscribed vehicle middleware. This enables a single subscription operation to trigger a one-to-many message broadcast mechanism when there is demand, realizing real-time sharing and synchronization of vehicle business messages among multiple communication nodes, thereby avoiding the waste of network resources caused by establishing a separate connection for each receiving node.

[0013] In some possible implementations, the vehicle-mounted middleware is further configured to: perform a target operation in response to a cancellation request from a first communication node; wherein the target operation includes: notifying a second communication node to terminate the subscription service corresponding to the subscription request, so that the second communication node stops returning vehicle service messages; disconnecting the communication connection; and clearing the second process identifier.

[0014] According to the above implementation method, when the vehicle middleware responds to the unsubscription request, it performs the target operations of terminating the subscription service, disconnecting the connection and clearing the second process identifier. This can release communication resources that are no longer needed in a timely manner and block invalid data streams, preventing memory leaks or invalid messages from continuously occupying bandwidth due to failure to clean up subscription relationships in a timely manner.

[0015] In some possible implementations, the vehicle-mounted middleware is also used to: perform a target operation in response to detecting an abnormal interruption of the communication link of the communication connection.

[0016] According to the above implementation method, when the vehicle middleware detects an abnormal interruption of the communication connection, it performs the target operations of terminating the subscription service, disconnecting the connection and clearing the identifier. This can quickly cut off the connection and clean up the residual state when the communication link is abnormal, avoiding deadlock or system hang-up caused by link failure, and improving the robustness of the vehicle system in complex network environments.

[0017] In some possible implementations, the information type includes at least one of vehicle operating status information, vehicle control command information, or vehicle fault warning information.

[0018] According to the above implementation method, by limiting the information type of vehicle business messages to include vehicle operating status information, vehicle control command information, or vehicle fault warning information, the system can adopt a unified routing and distribution method for vehicle business data with different real-time requirements and priority characteristics, thereby meeting the diverse needs for efficient interaction of multi-source heterogeneous data.

[0019] In some possible implementations, the subscription request includes a second process identifier; sending vehicle service messages to the first communication node includes: sending vehicle service messages to the first communication node based on the second process identifier.

[0020] According to the above implementation method, vehicle service messages are sent to the first communication node through the second process identifier, ensuring that the first communication node can accurately deliver the received messages to the specific service process for processing. This strengthens the isolation of cross-process communication, eliminates the possibility of messages being misprocessed by non-target processes at the receiving end, and improves the overall data processing accuracy of the system.

[0021] Secondly, this application provides a control method for an in-vehicle middleware, wherein the in-vehicle middleware is deployed on a first communication node. The method includes: the in-vehicle middleware responding to a subscription request from the first communication node to establish a communication connection with a second communication node indicated in the subscription request; wherein the subscription request is used to request subscription to vehicle service messages corresponding to a target topic in the second communication node; the target topic is one of the subscription topics already established in the second communication node, used to indicate the information type of the vehicle service message; the in-vehicle middleware forwards the subscription request to the second communication node so that the second communication node returns the vehicle service message; and after receiving the vehicle service message, the in-vehicle middleware sends the vehicle service message to the first communication node.

[0022] The control method for vehicle-mounted middleware provided in this application can establish a communication connection with the second communication node indicated in the subscription request in response to the subscription request of the first communication node. It also coordinates with the vehicle service messages corresponding to the target topic in the second communication node subscribed to in the subscription request. This allows the vehicle-mounted middleware to more accurately locate and connect to the target communication node providing the service based on the specific service information type, thereby avoiding resource waste and communication congestion caused by full broadcasting or blind connections. Based on this, by forwarding the subscription request to the second communication node to trigger its return of vehicle service messages, a one-way data path is established from the subscriber to the sender, ensuring that vehicle service messages under the target topic can be transmitted to the first communication node in real time and in a targeted manner, thereby improving the relay effectiveness and distribution accuracy of cross-process vehicle service messages.

[0023] In some possible implementations, establishing a communication connection with the second communication node indicated in the subscription request includes: determining a first process identifier of the service process distributing vehicle service messages on the second communication node; and establishing a communication connection with the second communication node based on the first process identifier.

[0024] In some possible implementations, a second process identifier is embedded in the subscription request forwarded to the second communication node, so that the second communication node can embed the second process identifier into the vehicle service message when returning the vehicle service message; the second process identifier is used to indicate the process identifier of the service process receiving the vehicle service message on the first communication node; receiving the vehicle service message includes: when receiving communication information returned by the second communication node, and the process identifier in the communication information is consistent with the second process identifier, the communication information is identified as a vehicle service message.

[0025] In some possible implementations, after receiving a subscription request, the second communication node selects the subscription record corresponding to the target topic from the subscription relationship table; and synchronously returns the vehicle service message to the vehicle middleware and other vehicle middleware that have previously subscribed to vehicle service messages in the subscription record; the other vehicle middleware is deployed on other communication nodes besides the first and second communication nodes.

[0026] In some possible implementations, the method further includes: in response to a first communication node’s unsubscription request, performing a target operation; wherein the target operation includes: notifying a second communication node to terminate the subscription service corresponding to the subscription request, so that the second communication node stops returning vehicle service messages; disconnecting the communication connection; and clearing the second process identifier.

[0027] In some possible implementations, the above method further includes: performing a target operation in response to detecting an abnormal interruption of the communication link of the communication connection.

[0028] In some possible implementations, the information type includes at least one of vehicle operating status information, vehicle control command information, or vehicle fault warning information.

[0029] In some possible implementations, the subscription request includes a second process identifier; sending vehicle service messages to the first communication node includes: sending vehicle service messages to the first communication node based on the second process identifier.

[0030] Thirdly, this application provides a control device, including: a memory and a processor; the memory and the processor are coupled; the memory is used to store a computer program; the processor executes the computer program to implement the control method of the vehicle middleware of any embodiment of the second aspect above.

[0031] Fourthly, this application provides a computer-readable storage medium storing computer program instructions that, when executed by a processor, implement the vehicle middleware control method of any embodiment of the second aspect described above.

[0032] Fifthly, this application provides a computer program product including computer program instructions that, when executed by a processor, implement the control method of the vehicle middleware described in any embodiment of the second aspect above.

[0033] Sixthly, this application provides a vehicle including the control device of any of the preceding embodiments; or the computer-readable storage medium of any of the preceding embodiments; or the computer program product of any of the preceding embodiments. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in this disclosure, the accompanying drawings used in some embodiments of this disclosure will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this disclosure. For those skilled in the art, other drawings can be obtained based on these drawings.

[0035] Figure 1 A schematic diagram of the architecture of a vehicle provided in an embodiment of this disclosure; Figure 2 This is a schematic diagram of the structure of an in-vehicle middleware provided in an embodiment of the present disclosure; Figure 3 A flowchart illustrating a control method for an in-vehicle middleware provided in this embodiment of the disclosure; Figure 4 A flowchart illustrating another control method for vehicle-mounted middleware provided in this embodiment of the disclosure; Figure 5 This is a schematic diagram of the structure of a control device provided in an embodiment of the present disclosure. Detailed Implementation

[0036] The technical solutions of this disclosure will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.

[0037] It should be noted that, in this disclosure, the terms "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in this disclosure should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0038] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0039] In the description of this disclosure, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Furthermore, "at least one" means one or more, and "more than one" means two or more.

[0040] As mentioned in the background technology, the distribution mode that relies on centralized nodes to maintain and traverse the entire registry requires a lot of computing resources to match receivers when distributing messages. This can easily cause the main thread of the system to be blocked, resulting in lag and response delays in the operation of the central control screen.

[0041] To address the aforementioned technical problems, this disclosure provides an in-vehicle middleware, the idea of ​​which is as follows: It can respond to the subscription request of the first communication node and establish a communication connection with the second communication node indicated in the subscription request. In conjunction with the vehicle business messages in the second communication node subscribed to in the subscription request that correspond to the target topic, the vehicle middleware can more accurately locate and connect to the target communication node that provides the service based on the specific business information type, thereby avoiding the waste of resources and communication congestion caused by full broadcast or blind connection.

[0042] Based on this, by forwarding the subscription request to the second communication node to trigger its return of vehicle service messages, a one-way data path from the subscriber to the sender is established, ensuring that vehicle service messages under the target topic can be transmitted to the first communication node in real time and in a targeted manner, thereby improving the relay effectiveness and distribution accuracy of cross-process vehicle service messages.

[0043] The vehicle provided in the embodiments of this disclosure will now be described in detail with reference to the accompanying drawings.

[0044] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of a vehicle provided as an embodiment of this disclosure. (For example...) Figure 1 As shown, the vehicle 100 includes: multiple communication nodes 110 and vehicle-mounted middleware 120 deployed on each communication node. The communication nodes are physically connected to each other through a vehicle-mounted communication network. For example, the multiple communication nodes 110 include a first communication node 1101 and a second communication node 1102.

[0045] The vehicle is used to execute the control method of the vehicle middleware provided in the embodiments of this application, so as to realize data interaction and message routing between different communication nodes and different service processes inside the vehicle.

[0046] The aforementioned vehicles can also be referred to as vehicles, mobile carriers, electric vehicles (EVs), hybrid electric vehicles (HEVs), plug-in hybrid electric vehicles (PHEVs), fuel cell vehicles (FCVs), autonomous vehicles, intelligent and connected vehicles (ICVs), driverless vehicles, etc.

[0047] In this application, the vehicle can be a sedan, a sport utility vehicle (SUV), a truck, a special vehicle (such as an ambulance, fire truck, police car, etc.), a driverless taxi, a smart connected bus, an autonomous logistics vehicle, an electric truck, etc. Furthermore, this method is also applicable to various special-purpose vehicles, such as agricultural vehicles, mining vehicles, forestry vehicles, airport vehicles, and port vehicles. This application does not impose specific limitations in this regard.

[0048] For example, the above-mentioned communication nodes achieve data communication connection through vehicle buses such as vehicle Ethernet, controller area network bus or local connection network bus.

[0049] The aforementioned communication nodes 110, as physical devices, are distributed in different electronic control units or computing platforms of the vehicle to carry their respective service processes and exchange data with other nodes.

[0050] The vehicle-mounted middleware 120 is used to manage the service process identifiers within the corresponding communication nodes, process subscription requests, forward vehicle service messages, and maintain the connection status with external communication nodes.

[0051] The aforementioned communication node 110 serves as the signal interaction terminal of the system, used to send vehicle service messages to other communication nodes within the system, or to receive vehicle service messages sent from other communication nodes.

[0052] The aforementioned communication node 110 sends the generated vehicle service messages to the vehicle middleware 120 through its built-in communication interface, or receives the vehicle service messages after routing and forwarding from the vehicle middleware 120, thereby realizing data transmission and message interaction between the internal process of the node and the external node process.

[0053] The aforementioned communication nodes include a first communication node and a second communication node.

[0054] The vehicle-mounted middleware 120 is used to respond to the subscription request of the first communication node, establish a communication connection with the second communication node, and forward the subscription request to the second communication node. If a subscription request exists, it establishes a communication connection with the second communication node; after the connection is established, it sends a subscription request to cause the second communication node to return vehicle service messages.

[0055] It is understood that the application scenarios of the embodiments of this disclosure are not limited. The system architecture and business scenarios described in the embodiments of this disclosure are for the purpose of more clearly illustrating the technical solutions of the embodiments of this disclosure, and do not constitute a limitation on the technical solutions provided by the embodiments of this disclosure. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided by the embodiments of this disclosure are also applicable to similar technical problems.

[0056] The vehicle middleware provided in the embodiments of this disclosure will be described in detail below.

[0057] like Figure 2 As shown, Figure 2 This is a structural schematic diagram of an in-vehicle middleware provided in an embodiment of the present disclosure, combined with... Figure 1 and Figure 2 This disclosure provides an in-vehicle middleware 120, deployed in a first communication node 1101, including: a connection establishment module 201, a message receiving module 202, and a message forwarding module 203.

[0058] The connection establishment module 201 is used to establish a communication connection with the second communication node indicated in the subscription request in response to the subscription request of the first communication node.

[0059] The subscription request is used to request subscription to vehicle service messages in the second communication node that correspond to the target topic; the target topic is one of the subscription topics that have been established in the second communication node, and is used to indicate the information type of the vehicle service message.

[0060] The first communication node mentioned above refers to the message consumer or client application that initiates the subscription request.

[0061] The aforementioned second communication node refers to a message publisher or message gateway that receives subscription requests and provides business messages.

[0062] The aforementioned subscription request refers to control signaling that includes information such as the subject identifier, the subscriber's callback address / handle, and possible quality of service requirements.

[0063] The aforementioned target topics are used to characterize a specific type of vehicle business message. For example, target topics include vehicle speed topics, voltage topics, rearview mirror data topics, etc.

[0064] The aforementioned vehicle service messages refer to vehicle service data, including vehicle sensor data, control command status, fault codes, multimedia streams, and other related information.

[0065] The aforementioned information types include at least one of vehicle operating status information, vehicle control command information, or vehicle fault warning information.

[0066] The aforementioned vehicle operating status information refers to a real-time dynamic data set reflecting the vehicle's current physical motion parameters, system resource utilization, energy consumption status, and environmental perception data. Vehicle operating status information is typically collected and generated periodically by onboard sensors, controllers, or positioning modules. For example, vehicle operating status information includes dynamic parameter information, energy and power status information, system load status information, and environmental perception data. Specifically, dynamic parameter information includes vehicle speed, acceleration, and steering wheel angle; energy and power status information includes engine speed and accelerator pedal opening; system load status information includes memory usage and network bus load rate; and environmental perception data includes obstacle distance, lane line recognition status, and light intensity.

[0067] The aforementioned vehicle control command information refers to command-type data generated by in-vehicle applications, cloud servers, or remote terminals, used to change the current operating state of the vehicle, adjust hardware operating modes, or trigger specific actuator actions. For example, vehicle control command information includes body control commands, powertrain control commands, driver assistance commands, multimedia and connectivity commands, etc.

[0068] The aforementioned vehicle fault warning information refers to alarm data generated after logical judgment based on abnormal states monitored by the vehicle diagnostic system. For example, vehicle fault warning information includes real-time fault codes, warning and threshold alarm information, safety status indication information, maintenance information, etc.

[0069] In some embodiments, where the first communication node is an image compositing module, the second communication node can be a camera driver service.

[0070] In other embodiments, if the first communication node is a navigation application, the second communication node can be a location service.

[0071] In other embodiments, when the first communication node is a remote communication control module, the second communication node can be a message bus inside the vehicle.

[0072] In other embodiments, when the first communication node is a voice assistant, the second communication node is an event bus management center.

[0073] As one possible approach, if the first communication node is an image compositing module and the second communication node can be a camera driver service, a communication connection is established between the first communication node and the second communication node if the first communication node sends a subscription request containing the original stream topic of the forward-looking camera to the second communication node.

[0074] The message receiving module 202 is used to forward the subscription request to the second communication node so that the second communication node returns vehicle service messages.

[0075] The message forwarding module 203 is used to receive vehicle service messages and then send them to the first communication node.

[0076] As one feasible approach, the vehicle-mounted middleware receives the target topic and callback function handle registered by the first communication node as a subscription request, binds it, and forwards it to the second communication node. When the second communication node returns a vehicle business message, the vehicle-mounted middleware no longer performs data copying and forwarding, but directly calls the callback function pre-registered by the first communication node, asynchronously passing the vehicle business message as a parameter, thereby achieving efficient data transmission with zero copying.

[0077] As another possible approach, when the vehicle-mounted middleware forwards the subscription request to the second communication node, it simultaneously carries filtering rules based on data content or time windows; the second communication node only sends vehicle business messages to the middleware when the message meets the filtering conditions, and the middleware then forwards the filtered and accurate data to the first communication node according to the routing table.

[0078] The vehicle-mounted middleware provided in this application can establish a communication connection with the second communication node indicated in the subscription request in response to the subscription request of the first communication node. It also works with the vehicle service messages corresponding to the target topic in the second communication node subscribed to in the subscription request. This allows the vehicle-mounted middleware to more accurately locate and connect to the target communication node providing the service based on the specific type of service information, thereby avoiding resource waste and communication congestion caused by full broadcasting or blind connections. Based on this, by forwarding the subscription request to the second communication node to trigger its return of vehicle service messages, a one-way data path is established from the subscriber to the sender, ensuring that vehicle service messages under the target topic can be transmitted to the first communication node in real time and in a targeted manner, thereby improving the relay effectiveness and distribution accuracy of cross-process vehicle service messages.

[0079] To facilitate understanding, the following example illustrates the vehicle middleware.

[0080] In some embodiments, the establishment of communication connections in the prior art often lacks precise identification based on process granularity, resulting in a blind connection establishment process, making it difficult to distinguish different service processes within the same node, and thus causing resource mismatch or connection conflicts.

[0081] Based on this, as a feasible implementation, establishing a communication connection with the second communication node indicated in the subscription request includes: Determine the first process identifier of the service process that distributes vehicle service messages on the second communication node.

[0082] A communication connection is established with the second communication node based on the first process identifier.

[0083] The aforementioned service process refers to an independent execution unit running in the operating system of the second communication node, used for data acquisition, packaging, or distribution.

[0084] The aforementioned first process identifier refers to the number or handle used to identify the service process.

[0085] The aforementioned communication connection refers to the logical or physical data channel established between the service processes of the first and second communication nodes.

[0086] As one possible approach, if the service process of the second communication node is running in a container, the first communication node can parse the container identifier and then establish a service connection based on the container identifier.

[0087] As another feasible approach, if the first process identifier of the second communication node is determined, the first communication node can establish a connection by reading the first process identifier and constructing a domain socket.

[0088] As one possible approach, a second process identifier is embedded in the subscription request forwarded to the second communication node, so that the second communication node can embed the second process identifier into the vehicle service message when returning the vehicle service message.

[0089] The second process identifier is used to indicate the process identifier of the service process that receives vehicle service messages on the first communication node.

[0090] Receive vehicle service messages, including: If the communication information returned by the second communication node is received, and the process identifier in the communication information is consistent with the second process identifier, the communication information is identified as a vehicle service message.

[0091] The aforementioned second process identifier refers to the unique service process number on the first communication node responsible for receiving and processing messages.

[0092] The aforementioned embedding refers to encapsulating the process identifier in the header of the communication protocol's data packet, metadata fields, or custom messages.

[0093] The aforementioned communication information refers to the raw data stream returned by the second communication node, which contains data for various service types or multiple processes.

[0094] In some possible implementations, the second communication node, upon receiving a subscription request, selects the subscription record corresponding to the target topic from the subscription relationship table.

[0095] In addition, vehicle service messages are synchronously returned to the vehicle middleware and other vehicle middleware that have previously subscribed to vehicle service messages in the subscription records.

[0096] Other vehicle-mounted middleware is deployed on communication nodes other than the first and second communication nodes.

[0097] The subscription relationship table mentioned above is an index table maintained internally by the second communication node, which records the mapping relationship between "topic-middleware list".

[0098] The other vehicle-mounted middleware mentioned above are middleware instances deployed on other computing units within the vehicle network.

[0099] As one possible approach, the second node sends messages to a central message bus, which automatically fans the messages out to all registered in-vehicle middleware consumer endpoints based on a subscription relationship table.

[0100] According to the above implementation method, the distribution efficiency of vehicle business messages can be improved, so that vehicle business messages not only flow between two nodes, but also realize on-demand synchronous distribution across the entire network.

[0101] In some embodiments, if resources are not thoroughly released after a communication session ends due to business needs, the second communication node may continue to occupy computing resources to push useless data, and residual identification information may cause identity confusion in subsequent connections. Therefore, in this embodiment, the vehicle-mounted middleware is further used for: In response to the unsubscribe request from the first communication node, perform the target operation.

[0102] The target operation includes: notifying the second communication node to terminate the subscription service corresponding to the subscription request, so that the second communication node stops returning vehicle service messages.

[0103] Disconnect the communication connection.

[0104] And, clear the second process identifier.

[0105] The aforementioned unsubscribe request refers to an instruction initiated by the first communication node to terminate data reception.

[0106] The subscription service corresponding to the aforementioned termination subscription request refers to the logical actions of the second communication node to remove the subscription record, stop data encapsulation, or stop sending vehicle business messages of the target topic.

[0107] The above-mentioned clearing of the second process identifier refers to deleting or invalidating the second process identifier from the vehicle middleware or system configuration, thereby releasing the memory or table entries occupied by the second process identifier.

[0108] In some embodiments, when the first communication node sends an unsubscribe request, the second communication node immediately deletes the corresponding process identifier in the hash table and stops sending vehicle service messages to the first communication node.

[0109] In other embodiments, after the first communication node sends an unsubscribe request, the second communication node marks the corresponding subscription record as pending cleanup and sets a countdown. If there are no new subscription requests within the countdown period, the vehicle middleware terminates the service logic and cleans up the corresponding process identifier.

[0110] In other embodiments, after the first communication node sends an unsubscribe request, the second communication node clears the relevant vehicle service messages and returns a successful termination reply. After the vehicle middleware receives the reply, it disconnects the communication connection and clears the second process identifier.

[0111] As one possible approach, in-vehicle middleware can also be used to perform target operations in response to the detection of an abnormal interruption of the communication link of the communication connection.

[0112] The aforementioned abnormal interruption of the communication link refers to a failure of the data transmission channel caused by physical faults, network congestion, node crashes, or power fluctuations, which is not initiated by the user.

[0113] The aforementioned target operations refer to the emergency handling logic preset for link interruption, which is usually used to release resources, reset status, or report faults.

[0114] As one possible approach, the system watchdog monitors the operational status of the second communication node. If a process crash of the second communication node is detected, causing a link interruption, the vehicle-mounted middleware automatically performs the following actions: releases all resources associated with that node and attempts to initiate a reconnection process or switch to a backup node.

[0115] As another possible approach, the vehicle-mounted middleware sends a heartbeat detection packet to the second communication node after a preset time interval; if no corresponding heartbeat response packet is received within a preset number of times, the link is determined to be abnormally interrupted, triggering the target operation.

[0116] In some embodiments, when the vehicle-mounted middleware sends data to the first communication node, if it does not carry explicit process addressing information, the message may be broadcast to the wrong process or additional routing matching may be required, reducing the real-time performance and accuracy of data distribution. Therefore, in this embodiment, in some possible implementations, the subscription request includes a second process identifier.

[0117] Send vehicle service messages to the first communication node, including: Based on the second process identifier, vehicle service messages are sent to the first communication node.

[0118] The above message is only sent to the specified target process. Other processes on the network, even if they are listening on the same physical channel, cannot receive the logical message, thereby improving system security and the efficiency of message control or execution.

[0119] The foregoing primarily describes the solutions of the embodiments of this disclosure from the perspective of the device. It is understood that, in order to achieve the aforementioned functions, the control method of the vehicle-mounted middleware includes execution steps that can be executed in at least one of the aforementioned hardware structures and software modules. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a particular step is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different hardware structures or software modules to implement the described execution functions for each specific step, but such implementation should not be considered beyond the scope of the embodiments of this disclosure.

[0120] This disclosure embodiment can divide the control method of the vehicle middleware into steps according to the above-described device embodiment. For example, each function can be assigned a separate execution step, or two or more functional modules can be integrated into one execution step. The integrated steps can be implemented in hardware or software. It should be noted that the step division in this disclosure embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation. The following description uses the example of dividing each execution step according to each function.

[0121] Figure 3 This is a flowchart illustrating a control method for an in-vehicle middleware provided in an embodiment of this disclosure. The in-vehicle middleware is deployed on a first communication node and can be applied to the in-vehicle middleware provided in the above-described device embodiment. For example... Figure 3 As shown, the control method for the vehicle-mounted middleware includes: S301, the vehicle-mounted middleware responds to the subscription request of the first communication node and establishes a communication connection with the second communication node indicated in the subscription request.

[0122] The subscription request is used to request subscription to vehicle service messages in the second communication node that correspond to the target topic; the target topic is one of the subscription topics that have been established in the second communication node, and is used to indicate the information type of the vehicle service message.

[0123] S302. The vehicle-mounted middleware forwards the subscription request to the second communication node so that the second communication node returns vehicle service messages.

[0124] S303. After receiving the vehicle service message, send the vehicle service message to the first communication node.

[0125] The control method for vehicle-mounted middleware provided in this application can establish a communication connection between the middleware and the second communication node indicated in the subscription request in response to the subscription request of the first communication node. Combined with the mechanism of requesting subscription to vehicle business messages corresponding to the target topic in the second communication node, the middleware can accurately locate and connect to the target node providing the service based on the specific business information type, thus avoiding resource waste and communication congestion caused by full broadcasting or blind connections. By forwarding the subscription request to the second communication node to trigger its return of vehicle business messages, a one-way data path is established from the subscriber to the publisher, ensuring that vehicle business messages under the target topic can be transmitted to the requester in real time and in a targeted manner. By sending vehicle business messages to the first communication node after receiving them, cross-process message relay and distribution are achieved, enabling vehicle business modules deployed on different communication nodes to interact decoupled. This solves the technical problems of information transmission delays or failures caused by tight coupling, poor scalability, and lack of a unified message routing mechanism among functional modules in existing vehicle-mounted systems, effectively improving the accuracy, real-time performance, and overall operational stability of message distribution within the vehicle-mounted system.

[0126] In some possible implementations, establishing a communication connection with the second communication node indicated in the subscription request includes: Determine the first process identifier of the service process that distributes vehicle service messages on the second communication node.

[0127] A communication connection is established with the second communication node based on the first process identifier.

[0128] In some possible implementations, a second process identifier is embedded in the subscription request forwarded to the second communication node, so that the second communication node can embed the second process identifier into the vehicle service message when returning the vehicle service message; the second process identifier is used to indicate the process identifier of the service process receiving the vehicle service message on the first communication node; receiving the vehicle service message includes: when receiving communication information returned by the second communication node, and the process identifier in the communication information is consistent with the second process identifier, the communication information is identified as a vehicle service message.

[0129] In some possible implementations, after receiving a subscription request, the second communication node selects the subscription record corresponding to the target topic from the subscription relationship table; and synchronously returns the vehicle service message to the vehicle middleware and other vehicle middleware that have previously subscribed to vehicle service messages in the subscription record; the other vehicle middleware is deployed on other communication nodes besides the first and second communication nodes.

[0130] Figure 4 A flowchart of another control method for vehicle-mounted middleware provided in this disclosure embodiment is shown below. Figure 4 As shown, the control method of the vehicle middleware includes: S301-S305, wherein the steps of S301-S303 are the same as those described above, and will not be repeated here.

[0131] S304. In response to the unsubscribe request from the first communication node, perform the target operation.

[0132] The target operations include: The second communication node is notified to terminate the subscription service corresponding to the subscription request, so that the second communication node stops returning vehicle service messages.

[0133] Disconnect the communication connection.

[0134] And, clear the second process identifier.

[0135] S305. In response to the detection of an abnormal interruption of the communication link of the communication connection, the target operation is executed.

[0136] In some possible implementations, the information type includes at least one of vehicle operating status information, vehicle control command information, or vehicle fault warning information.

[0137] In some possible implementations, the subscription request includes a second process identifier.

[0138] Send vehicle service messages to the first communication node, including: Based on the second process identifier, vehicle service messages are sent to the first communication node.

[0139] When implementing the functions of the integrated modules described above in hardware, this disclosure provides a possible structure for the control device involved in the above embodiments. For example... Figure 5 As shown, the control device 500 includes a processor 502 and a bus 504. Optionally, the control device may also include a memory 501; alternatively, the control device 500 may also include a communication interface 503.

[0140] Processor 502 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 502 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with embodiments of this disclosure. Processor 502 may also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a digital signal processor (DSP), and a microprocessor, etc.

[0141] Communication interface 503 is used to connect to other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0142] The memory 501 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0143] In one possible implementation, the memory 501 can exist independently of the processor 502. The memory 501 can be connected to the processor 502 via a bus 504 and is used to store instructions or program code. When the processor 502 calls and executes the instructions or program code stored in the memory 501, it can implement the control method of the vehicle middleware provided in this embodiment. In another possible implementation, the memory 501 can also be integrated with the processor 502.

[0144] Bus 504 can be an extended industry standard architecture (EISA) bus, etc. Bus 504 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 5 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0145] Some embodiments of this disclosure provide a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer program instructions that, when executed on a processor, cause the processor to perform a control method for an in-vehicle middleware as described in any of the above embodiments.

[0146] Exemplary examples of computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, various other media capable of storing, containing, and / or carrying instructions and / or data.

[0147] This disclosure provides a computer program product containing instructions that, when run on a processor, cause the processor to execute the vehicle middleware control method described in any of the above embodiments.

[0148] This disclosure provides a vehicle including the control device of any of the preceding embodiments; or the computer-readable storage medium of any of the preceding embodiments; or the computer program product of any of the preceding embodiments.

[0149] The vehicle provided in this application may be a passenger vehicle or a freight vehicle, and may also be an electric vehicle or a hybrid vehicle. This application does not limit the specific purpose or power type of the vehicle, and the choice can be made according to actual needs.

[0150] A vehicle consists of a body and wheels. The body is used for passengers and for carrying goods, while the wheels are mounted underneath the body to support it and allow it to roll on the road, thus enabling the vehicle to move.

[0151] In some possible examples, the vehicle is equipped with a control system, which typically adopts a layered distributed architecture. From the bottom layer to the top layer, it can be roughly divided into a perception layer, a control layer, a coordination layer, and an interaction layer. The layers communicate with each other through an in-vehicle network.

[0152] The perception layer mainly consists of various sensors distributed inside and outside the vehicle, including but not limited to external environment cameras, millimeter-wave radar, lidar, ultrasonic sensors, in-vehicle driver monitoring cameras, microphone arrays, and various vehicle status sensors (such as wheel speed sensors, inertial measurement units, temperature sensors, etc.). The perception layer is responsible for collecting multi-dimensional data such as the vehicle's own operating status, driver behavior, and external driving environment in real time.

[0153] The control layer consists of dozens to hundreds of electronic control units (ECUs), distributed across multiple functional domains including powertrain, chassis, body, intelligent driving, and infotainment. Each ECU embeds real-time control software that performs closed-loop control of the vehicle's actuators based on preset control strategies or upper-level commands, and generates corresponding alarm signals when abnormal conditions are detected. Typical ECUs include the engine control unit, transmission control unit, brake control unit, steering control unit, vehicle stability control unit, airbag control unit, intelligent driving domain controller, and in-vehicle infotainment unit.

[0154] The coordination layer typically exists in the form of a domain controller or a central computing platform, responsible for cross-domain data fusion, global state management, and collaborative decision-making. The coordination layer centrally processes and schedules the sensing data and control commands that were originally scattered across various functional domains, connecting downwards to various electronic control units and supporting human-machine interaction functions upwards.

[0155] The interaction layer mainly includes in-cabin display devices (such as instrument panel, central control screen, head-up display), voice interaction system, haptic feedback device, etc., which are responsible for presenting vehicle status, warning information and driving suggestions to the driver in the form of visual, auditory or tactile, while receiving the driver's touch, voice and other input commands.

[0156] Data transmission and interaction between different layers are achieved through the vehicle bus network. Common vehicle bus protocols include CAN (Controller Area Network), CAN FD (CAN with Flexible Data-Rate), LIN (Local Interconnect Network), FlexRay, and vehicle Ethernet, which supports high-bandwidth data transmission. Among these, CAN and CAN FD buses are widely used for communication in real-time control domains such as powertrain and chassis, while vehicle Ethernet is gradually being applied to high-bandwidth sensor data transmission in the intelligent driving domain and multimedia interaction scenarios in the cockpit domain.

[0157] In some possible examples, the intelligent driving domain controller, as the core of the in-vehicle computing platform, is equipped with a processor and memory to execute the control method of the in-vehicle middleware provided in the embodiments of this application.

[0158] For example, the control device of this application is arranged in the intelligent driving domain controller.

[0159] For example, the intelligent driving domain controller has multiple functional modules deployed to perform the various method steps.

[0160] The above description is merely a specific embodiment of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any changes or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A vehicle-mounted middleware, deployed at a first communication node, characterized in that, The vehicle-mounted middleware is used for: In response to the subscription request of the first communication node, a communication connection is established with the second communication node indicated in the subscription request; wherein, the subscription request is used to request subscription to vehicle service messages corresponding to a target topic in the second communication node; the target topic is one of the subscription topics already established in the second communication node, used to indicate the information type of the vehicle service message; The subscription request is forwarded to the second communication node so that the second communication node returns the vehicle service message; After receiving the vehicle service message, the vehicle service message is sent to the first communication node.

2. The vehicle-mounted middleware according to claim 1, characterized in that, Establishing a communication connection with the second communication node indicated in the subscription request includes: Determine the first process identifier of the service process that distributes the vehicle service message on the second communication node; Based on the first process identifier, a communication connection is established with the second communication node.

3. The vehicle-mounted middleware according to claim 2, characterized in that, A second process identifier is embedded in the subscription request forwarded to the second communication node, so that when the second communication node returns the vehicle service message, the second process identifier is embedded in the vehicle service message; The second process identifier is used to indicate the process identifier of the service process on the first communication node that receives the vehicle service message; Receiving the vehicle service message includes: If the communication information returned by the second communication node is received, and the process identifier in the communication information is consistent with the second process identifier, the communication information is identified as the vehicle service message.

4. The vehicle-mounted middleware according to claim 2, characterized in that, After receiving the subscription request, the second communication node selects the subscription record corresponding to the target topic from the subscription relationship table; and synchronously returns the vehicle service message to the vehicle middleware and other vehicle middleware that have previously subscribed to the vehicle service message in the subscription record. The other vehicle-mounted middleware is deployed on communication nodes other than the first and second communication nodes.

5. The vehicle-mounted middleware according to claim 3, characterized in that, The vehicle-mounted middleware is also used for: In response to the unsubscribe request from the first communication node, perform the target operation; The target operation includes: The second communication node is notified to terminate the subscription service corresponding to the subscription request, so that the second communication node stops returning the vehicle service message; Disconnect the communication connection; And, clear the second process identifier.

6. The vehicle-mounted middleware according to claim 5, characterized in that, The vehicle-mounted middleware is also used for: In response to the detection of an abnormal interruption of the communication link of the communication connection, the target operation is performed.

7. The vehicle-mounted intermediate component according to any one of claims 1-6, characterized in that, The information type includes at least one of vehicle operating status information, vehicle control command information, or vehicle fault warning information.

8. The vehicle-mounted middleware according to any one of claims 3-6, characterized in that, The subscription request includes the second process identifier; Sending the vehicle service message to the first communication node includes: Based on the second process identifier, the vehicle service message is sent to the first communication node.

9. A control method for an in-vehicle middleware, wherein the in-vehicle middleware is deployed at a first communication node, characterized in that, The control method for the vehicle-mounted middleware includes: In response to the subscription request from the first communication node, the vehicle middleware establishes a communication connection with the second communication node indicated in the subscription request; wherein, the subscription request is used to request subscription to vehicle service messages corresponding to a target topic in the second communication node; the target topic is one of the subscription topics already established in the second communication node, used to indicate the information type of the vehicle service message; The vehicle middleware forwards the subscription request to the second communication node so that the second communication node returns the vehicle service message; After receiving the vehicle service message, the vehicle service message is sent to the first communication node.

10. A control device, characterized in that, The control device includes: a memory and a processor; the memory and the processor are coupled; the memory is used to store instructions executable by the processor; when the processor executes the instructions, it performs the control method of the vehicle middleware as described in claim 9.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that, when executed on a processor, cause the processor to perform the control method of the vehicle middleware as described in claim 9.

12. A computer program product, characterized in that, It includes a computer program; when the computer program is executed, it is able to implement the control method of the vehicle middleware as described in claim 9.

13. A vehicle, characterized in that, It includes the control device as claimed in claim 10; or the computer-readable storage medium as claimed in claim 11; or the computer program product as claimed in claim 12.