CN-122027386-A - Communication system for vehicle

Abstract

In certain embodiments, a control system for an electric vehicle includes an Electronic Control Unit (ECU) bus and a plurality of ECUs. The first ECU executes a proxy service that communicates with a web server over a network, receives status information from an application executing on the ECU, generates subscription information based on the status information, and transmits the subscription information to the application subscribed to the subscription information. The first ECU also executes a translation service in communication with the proxy service and the ECU bus, and an application that generates status information, sends the status information to the proxy service, and receives subscription information from the proxy service. The second ECU executes an application that transmits status information to the first ECU over the ECU bus and receives subscription information from the first ECU over the ECU bus.

Inventors

• J. SCHULTZ
• J. Donne
• J. Haynes
• B. N. Drobiz
• M. Powers
• M. T. Vanderfried
• S. Bentley

Assignees

• 瑞维安知识产权控股有限责任公司

Dates

Publication Date

20260512

Application Date

20251112

Priority Date

20251103

Claims (20)

1. 1. A control system for an electric vehicle, the control system comprising: an Electronic Control Unit (ECU) bus, and A plurality of ECUs coupled to the ECU bus, the ECU comprising: The first ECU has a first control unit configured to control, the first ECU is configured to: executing a proxy service configured to communicate with a web server over a network; Generating subscription information based on status information received from an application executing on the ECU; Transmitting the subscription information to one or more of the applications executing on the ECU that subscribe to the subscription information, and Executing a translation service configured to communicate with the proxy service and the ECU bus, and A second ECU which is provided with a second control unit, the second ECU is configured to: executing an application configured to transmit status information to the first ECU over the ECU bus, and Subscription information is received from the first ECU over the ECU bus.
2. 2. The control system of claim 1, wherein the conversion service is configured to: receiving the status information in a first format from the second ECU via the ECU bus; Converting said state information in said first format into state information in a second format, and Providing the status information in the second format to the proxy service.
3. 3. The control system of claim 2, wherein the conversion service is further configured to: Receiving additional state information in the first format from the second ECU via the ECU bus; Determining whether the additional state information is different from the state information, and When the additional state information is different from the state information, converting the state information of the first format into state information of the second format, and providing the state information of the second format to the proxy service.
4. 4. The control system of claim 1, wherein: the first ECU is further configured to execute an application configured to: generating state information; transmitting the status information to the proxy service, and Receiving subscription information from the proxy service; An application executing on the web server subscribes to the subscription information, and The proxy service is further configured to transmit the subscription information over the network to the application executing on the web server.
5. 5. The control system of claim 4, wherein the proxy service is further configured to: Receiving additional state information from the application executing on the web server; generating additional subscription information based on the additional status information received from the web server, and Transmitting the additional subscription information to the application executing on the ECU that subscribes to the additional subscription information.
6. 6. The control system of claim 4, wherein: the first ECU is further configured to execute a diagnostic client, and The diagnostic client is configured to: receiving a status command from the application executing on the web server, wherein the status command is associated with an application transmitting status information and the status command includes updated status information; determining which ECU is executing the application transmitting the status information, and The status command is sent to the determined ECU over the ECU bus.
7. 7. The control system of claim 6, wherein the application associated with the status command is configured to: determining whether the status command is authorized; Changing the status information to the updated status information when the status command is authorized, and And transmitting the updated state information to the first ECU through the ECU bus.
8. 8. An Electronic Control Unit (ECU) for an electric vehicle, the ECU comprising: Memory, and A processor coupled to the memory and ECU bus, the processor configured to: executing a proxy service configured to: Is in communication with a network server via a network, Generating subscription information based on status information received from an application executing on an ECU coupled to the ECU bus, and Transmitting the subscription information to one or more of the applications executing on the ECU that subscribe to the subscription information; executing a translation service configured to communicate with the proxy service and the ECU bus, and Executing a first application configured to: The status information is generated and the status information is stored, Transmitting the status information to the proxy service, and Subscription information is received from the proxy service.
9. 9. The ECU according to claim 8, wherein the conversion service is configured to: Receiving the status information in a first format from an application executing on an ECU over the ECU bus; Converting said state information in said first format into state information in a second format, and Providing the status information in the second format to the proxy service.
10. 10. The ECU according to claim 9, wherein the conversion service is further configured to: Receiving additional state information in the first format from the application executing on the ECU over the ECU bus; Determining whether the additional state information is different from the state information, and When the additional state information is different from the state information, converting the state information of the first format into state information of the second format, and providing the state information of the second format to the proxy service.
11. 11. The ECU according to claim 8, wherein: An application executing on the web server subscribes to the subscription information, and The proxy service is further configured to transmit the subscription information to the application executing on the web server.
12. 12. The ECU of claim 11, wherein the proxy service is further configured to: Receiving additional state information from the application executing on the web server; generating additional subscription information based on the additional status information received from the web server, and Transmitting the additional subscription information to the application executing on the ECU that subscribes to the additional subscription information.
13. 13. The ECU according to claim 11, wherein: the processor is further configured to execute a diagnostic client, and The diagnostic client is configured to: receiving a status command from the application executing on the web server, wherein the status command is associated with an application transmitting status information and the status command includes updated status information; determining which ECU is executing the application transmitting the status information, and The status command is sent to the determined ECU over the ECU bus.
14. 14. The ECU of claim 13, wherein the diagnostic client is further configured to: updated state information is received from the application executing on the determined ECU via the ECU bus.
15. 15. A method for managing status information of an electric vehicle, the method comprising: a proxy service executing on an Electronic Control Unit (ECU) coupled to an ECU bus communicates with a web server over a network, Generating, by the proxy service, subscription information based on status information received from an application executing on an ECU coupled to the ECU bus, and Transmitting, by the proxy service, the subscription information to one or more of the applications executing on the ECU that have subscribed to the subscription information; status information is generated by a first application executing on the ECU, Transmitting, by the application, the status information to the proxy service, and Subscription information is received by the application from the proxy service.
16. 16. The method of claim 15, the method further comprising: receiving, by a conversion service executing on the ECU, the status information in a first format from an application executing on the ECU over the ECU bus; converting said state information in said first format into state information in a second format by said conversion service, and The state information in the second format is provided by the translation service to the proxy service.
17. 17. The method of claim 16, the method further comprising: Receiving, by the conversion service, additional state information in the first format from the application executing on the ECU over the ECU bus; determining by the conversion service whether the additional state information is different from the state information by the conversion service, and When the additional state information is different from the state information, the state information of the first format is converted into state information of the second format by the conversion service, and the state information of the second format is provided to the proxy service.
18. 18. The method according to claim 15, wherein: An application executing on the web server subscribes to the subscription information, and The method also includes transmitting, by the proxy service, the subscription information to the application executing on the web server.
19. 19. The method of claim 18, the method further comprising: Receiving, by the proxy service, additional state information from the application executing on the web server; Generating, by the proxy service, additional subscription information based on the additional status information received from the web server, and The additional subscription information is transmitted by the proxy service to the application executing on the ECU that is subscribed to the additional subscription information.
20. 20. The method of claim 18, the method further comprising: Receiving, by a diagnostic client, a status command from the application executing on the web server, wherein the status command is associated with an application transmitting status information and the status command includes updated status information; determining, by the diagnostic client, which ECU is executing the application that transmitted the status information; Transmitting the status command by the diagnostic client to the determined ECU via the ECU bus, and Updated state information is received by the diagnostic client over the ECU bus from the application executing on the determined ECU.

Description

Communication system for vehicle Cross Reference to Related Applications The present application claims the benefit of U.S. provisional application serial No. 63/719,643 (filed 11/12 at 2024), the contents of which are incorporated herein by reference in their entirety. Background The present disclosure relates to communication systems. More specifically, the present disclosure relates to a communication system for an electric vehicle. Vehicles use various ad hoc communication technologies to share data between applications running on network devices and applications running on vehicle Electronic Control Units (ECUs). After the data is generated, the data is transmitted over a plurality of communication channels and transitions before being received for further processing. Drawings Fig. 1 depicts a diagram of an example electric vehicle, according to an embodiment of the present disclosure. Fig. 2 depicts a block diagram of example components of an electric vehicle, according to an embodiment of the present disclosure. Fig. 3 depicts a block diagram of an example communication system, according to an embodiment of the present disclosure. Fig. 4 depicts a flowchart describing functionality for managing status information of an electric vehicle, according to an embodiment of the present disclosure. Fig. 5 depicts a flow chart describing the functionality of event-driven or state-driven self-tuning for an electric vehicle, according to an embodiment of the present disclosure. Fig. 6 depicts a flowchart describing functionality for managing status information of an electric vehicle, according to certain embodiments of the present disclosure. Detailed Description In existing communication systems, there is no unified presentation method for data states and services available across network devices and vehicle ECUs. In addition, applications running on network devices and vehicle ECUs must constantly modify the underlying code to accommodate changes in data structures and service Application Programming Interfaces (APIs). Managing these platform and architecture changes becomes complex and cumbersome. Therefore, it is difficult to share data and services across the network devices and the vehicle ECU. Embodiments of the present disclosure advantageously provide a communication system for a vehicle that includes a simple, convenient, efficient, and error-free unified communication structure (also referred to as a secure data structure). The secure data structure encompasses data transmitted between a network application running on a network device and a vehicle application running on an ECU, data transmitted between vehicle applications running on different ECUs, and data transmitted between vehicle applications running on the same ECU. The network devices may include network servers, cloud-based network servers that provide cloud computing services, smart phones, personal computers, and the like. The vehicle has a control system that includes a plurality of ECUs coupled to an ECU bus. Each ECU includes one or more processors configured to execute one or more software modules stored in memory. At least one ECU includes a wireless transceiver that is coupleable to a wireless network (such as a cellular network, wiFi network, etc.) that is coupled to a wide area network (WAN, such as the internet, etc.). The web application and the vehicle application work together to provide a set of services within the communication system, such as backend services, user services, vehicle services, and the like. More specifically, the network device and the vehicle ECU are nodes forming a distributed cluster of secure data structures. The data is generated by a "producer" application running on the network device or vehicle ECU, transmitted through a secure data structure, and received by a "consumer" application running on the vehicle ECU or network device. Advantageously, an application connected to a secure data structure on one node may generate data that may be consumed by other applications connected to secure data structures on any node. The secure data structure includes a messaging protocol and supporting infrastructure that publishes data to the producer application and provides a service providing framework to the consumer application, and subscribes to published data for the consumer application and requests the service providing framework from the producer application. In certain embodiments, the communication messaging protocol implements the Neural Autonomous Transport System (NATS) protocol. In other embodiments, the communication messaging protocol may implement APACHE KAFKA, rabbitMQ, apache Pulsar, gRPC, and the like. The communication system provides a number of technical advantages over existing ad hoc communication techniques. The secure data network structure provides final data consistency (also referred to as "at least once" semantics) by providing the latest state of the relevant data to the consumer appl