CN117793673A - Vehicle-mounted interconnection system based on event - Google Patents

Abstract

An event-based on-board interconnect system comprising: a plurality of ECUs communicatively connected via an on-board network, each ECU defining its associated vehicle event therein; and a remote communication terminal communicatively connected to each ECU via an in-vehicle network. After a certain vehicle event occurs, acquiring the vehicle event and issuing a synchronous uploading instruction to a vehicle-mounted network by an ECU (electronic control unit) associated with the vehicle event; other ECUs associated with the vehicle event receive the synchronous uploading instruction by the vehicle-mounted network; based on the synchronous uploading instruction, each ECU associated with the vehicle event synchronously collects event related data and uploads the synchronously collected event related data to the remote communication terminal; the remote communication terminal wirelessly transmits the event related data to a cloud platform associated with the vehicle.

Description

Vehicle-mounted interconnection system based on event

Technical Field

The present application relates to an on-board interconnect system in which comprehensive and practical data relating to certain events of a vehicle are collected and transmitted based on the events.

Background

The vehicle-mounted interconnection system can realize data transmission between the vehicle-mounted terminal and the cloud platform. The vehicle-mounted terminal can collect real-time information of the vehicle, such as operation behaviors of a driver, working parameters of various subsystems of the vehicle and the like, and wirelessly transmit the collected real-time information to the cloud platform, the cloud platform can perform preliminary processing on the received real-time information of the vehicle and then transmit the processed real-time information to the background so as to further process or analyze the data, and the background wirelessly transmits feedback or control signals generated after the processing or analysis to the vehicle-mounted terminal through the cloud platform.

Currently, for a certain vehicle event, each relevant ECU (electronic control unit) in the vehicle collects data in real time independently of each other and uploads the collected data to the cloud platform through the in-vehicle terminal. There is no inter-ECU data interconnection between each ECU for a vehicle event. For some vehicle event, each relevant ECU collects data based on its own logic independently of each other, resulting in incomplete or redundant data collection. In particular, for some ECUs that are not aware of the event, the event-related data may not be uploaded at all. Incomplete or redundant data can negatively impact subsequent data analysis and vehicle function optimization.

Disclosure of Invention

It is an object of the present application to provide an on-board interconnect system that is capable of synchronously collecting and transmitting, for a certain event of a vehicle, comprehensive and practical data related to the event based on data interconnection between ECUs.

To this end, according to one aspect of the present application, there is proposed an event-based on-board interconnection system comprising:

a plurality of ECUs communicatively connected via an on-board network, each ECU defining its associated vehicle event therein; and

a remote communication terminal in communication with each ECU through a vehicle-mounted network;

the in-vehicle interconnect system is configured to:

after a certain vehicle event occurs, acquiring the vehicle event and issuing a synchronous uploading instruction to a vehicle-mounted network by an ECU (electronic control unit) associated with the vehicle event;

other ECUs associated with the vehicle event receive the synchronous upload instruction by an on-board network;

based on the synchronous uploading instruction, each ECU associated with the vehicle event synchronously collects event related data and uploads the synchronously collected event related data to the remote communication terminal;

and the remote communication terminal wirelessly transmits the event related data to a cloud platform associated with the vehicle.

In one embodiment of the vehicle interconnection system, the vehicle interconnection system is a vehicle interconnection system for single-type vehicle events or a vehicle interconnection system for multiple-type vehicle events, in particular a whole vehicle interconnection system. For example, the vehicle-mounted interconnection system is a brake interconnection system.

In one embodiment of the in-vehicle interconnect system, a state machine is provided in each ECU, the state machine being configured to establish synchronization information between each ECU associated with the vehicle event based on the validity of the synchronization upload instruction, and to execute synchronization upload event related data based on the synchronization information.

In one embodiment of the vehicle interconnection system, an event authenticity detection mechanism, for example, an event authenticity detection mechanism based on an anti-shake function, is provided in each ECU, so as to evaluate the authenticity of the vehicle event, thereby judging the validity of the synchronous uploading instruction.

In one embodiment of the on-board interconnection system, the on-board interconnection system has three states: a normal running state, a ready to synchronize state, a synchronize upload state, and configured to switch between these three states based on the authenticity of the vehicle event and the validity of the synchronize upload instruction.

In one embodiment of the in-vehicle interconnect system, each ECU associated with the vehicle event synchronously uploads event related data collected synchronously to the remote communication terminal, respectively.

In one embodiment of the vehicle-mounted interconnection system, each ECU associated with the vehicle event uploads the event related data collected synchronously to a whole vehicle CPU, and the whole vehicle CPU integrates the event related data into a unified integration file and uploads the integration file to the remote communication terminal.

In one embodiment of the vehicle-mounted interconnection system, the plurality of ECUs includes a master ECU in which software for processing to be executed for the vehicle event is provided, and the synchronization upload instruction is issued to a vehicle-mounted network by the master ECU.

In one embodiment of the vehicle-mounted interconnection system, other ECUs associated with the vehicle event upload event related data collected synchronously to the master ECU, respectively, and the master ECU integrates the event related data into a unified integration file and uploads the integration file to the remote communication terminal.

In one embodiment of the in-vehicle interconnection system, the plurality of ECUs include therein a domain processor for a vehicle subsystem, the domain processor managing each ECU within the vehicle subsystem and configured to issue the synchronization upload instruction to an in-vehicle network.

In one embodiment of the vehicle-mounted interconnection system, each ECU associated with the vehicle event in the vehicle subsystem where the domain processor is located, and each ECU associated with the vehicle event in the other vehicle subsystem, upload event-related data collected synchronously to the domain processor, respectively, and the domain processor integrates the event-related data into a unified integration file and uploads the integration file to the remote communication terminal.

In one embodiment of the vehicle-mounted interconnection system, the format of the synchronous uploading instruction is a PDU newly added with a message ID representing that a message type transmitted between the ECUs is the synchronous uploading instruction, and the PDU further comprises a synchronization flag bit and synchronization information.

The present application provides, in another aspect thereof, a vehicle-mounted interconnection system control method, including:

detecting a vehicle event associated with the vehicle-mounted interconnection system;

confirming the authenticity of the vehicle event by a vehicle ECU (electronic control Unit) which is informed of the vehicle event and is associated with the vehicle event, and issuing a synchronous uploading instruction to a vehicle-mounted network;

other ECUs associated with the vehicle event receive the synchronous upload instruction by an on-board network;

based on the synchronous uploading instruction, each ECU associated with the vehicle event synchronously collects event related data and uploads the synchronously collected event related data to the remote communication terminal;

and the remote communication terminal wirelessly transmits the event related data to a cloud platform associated with the vehicle.

The control method may be implemented by means of the vehicle-mounted interconnection system of the present application, and may include various features related to the vehicle-mounted interconnection system of the present application, which will not be described herein.

According to the vehicle-mounted interconnection system and the related control method, based on data interconnection among ECUs, comprehensive data of ECUs related to a certain vehicle event is synchronously collected and uploaded to a cloud platform aiming at related control logic of the event. Compared with the scheme that each ECU independently collects data, the scheme of the application can collect and transmit comprehensive and practical data related to the event more rapidly and accurately synchronously, incomplete or redundant data is avoided, the cloud platform or the data analysis platform can process the related data of the vehicle event timely and accurately, and vehicle feedback is given when necessary.

Drawings

The foregoing and other aspects of the present application will be more fully understood and appreciated from the following detailed description taken with reference to the accompanying drawings, in which:

FIG. 1 is a schematic block diagram of control elements that may be involved in the on-board interconnection system of the present application;

FIG. 2 is a schematic block diagram of the in-vehicle interconnect system of the present application configured for a certain vehicle event;

FIG. 3 is a schematic block diagram of an on-board interconnection system of the present application configured for a variety of vehicle events;

FIG. 4 is a schematic block diagram of a modified on-board interconnect system of the present application configured for vehicular events;

FIG. 5 is a logic diagram of one exemplary operation of the in-vehicle interconnect system of the present application;

FIG. 6 is a flow chart of one exemplary operation of the in-vehicle interconnection system of the present application.

Detailed Description

The present application relates generally to an on-board interconnect system that enables synchronous collection and transmission of comprehensive and practical data related to a vehicle event based on inter-ECU data interconnect for that event.

The control elements that may be involved in the in-vehicle interconnect system of the present application are schematically represented in fig. 1.

As shown in fig. 1, the whole CPU of the vehicle is communicatively connected to an electronic control unit ECU in each subsystem of the vehicle. The communication connection may be an in-vehicle network such as a controller area network bus CAN, flexray, ethernet. In fig. 1, the CAN represents a vehicle network, but it CAN be understood that the vehicle interconnection system of the present application may also implement communication connection by using other vehicle networks.

The various subsystems (or domains) of the vehicle may illustratively include: a power subsystem SY1, a chassis subsystem SY2, a body subsystem SY3, a driving assistance subsystem SY4, a multimedia subsystem SY5, etc. Various events of the vehicle are distributed to these subsystems. For example, engine and transmission control may be distributed into the power subsystem SY 1; antilock braking, electronic body stabilization, etc. may be distributed to the bottom subsystem SY 2; air conditioning, center control locks, seats, rearview mirror adjustments, etc. may be distributed to the vehicle body subsystem SY3 (or vehicle body comfort subsystem), and airbags, seat belts, etc. may also be distributed to the vehicle body subsystem SY3 (or vehicle body passive safety subsystem); various events that provide assistance to the driver during driving may be distributed to the driving assistance subsystem SY 4; entertainment, telephony, navigation etc. functions may be distributed to the multimedia subsystem SY 5. Of course, other ways of dividing the vehicle subsystems and assigning vehicle functions are possible.

It should be noted that for certain vehicle functions, execution within a certain subsystem may be required. For other functions, particularly the more recently developed complex or advanced vehicle functions, it may be desirable to perform jointly among multiple subsystems across the boundaries of each subsystem. For example, functions such as adaptive cruise, autopilot, and autopilot require the combined execution of the power subsystem SY1 and the drive assist subsystem SY 4.

Each vehicle subsystem contains several ECUs for implementing different vehicle functions, either independently or in combination. The ECUs in each subsystem are in communication connection with the CPU of the whole vehicle and the ECUs of each subsystem through a vehicle-mounted network. A gateway GT may be provided between the subsystems. A gateway can also be arranged between each subsystem and the whole vehicle CPU.

It should be noted that for some simple vehicle functions, only a certain ECU within a certain subsystem may be required to perform independently. For more complex vehicle functions, multiple ECUs within a subsystem may be required to perform in combination. Whereas for some newly developed complex or advanced vehicle functions, multiple ECUs in multiple subsystems may be required to be executed in combination.

In addition, a remote communication terminal (e.g., T-Box) TB is also connected to the in-vehicle network to achieve communication connection between the remote communication terminal TB and the whole vehicle CPU and ECU of each subsystem. The remote communication terminal TB can be in wireless connection with a cloud processing platform (cloud platform for short) CLD (compact disk) associated with the vehicle, so that bidirectional data transmission is realized. The cloud platform CLD may perform preliminary processing on the vehicle data from the remote communication terminal TB and transmit the processed data to a background (not shown), and the background further processes or analyzes the data and then wirelessly transmits the generated feedback or control signal to the remote communication terminal TB via the cloud platform CLD. The vehicle CPU and associated ECU may receive feedback or control signals from the rear-end station from the remote communication terminal TB.

The vehicle-mounted interconnection system is constructed for vehicle events. Specifically, the control scheme of the vehicle-mounted interconnection system is based on the interconnection capacity of the ECUs in the subsystems and the interconnection capacity of the ECUs among the subsystems, and realizes synchronous and complete collection, uploading and wireless transmission of the ECU data related to a certain vehicle event.

The vehicle-mounted interconnection system can be configured to be applicable to interconnection systems of single vehicle events, interconnection systems of various vehicle events, and whole vehicle interconnection systems of most, even all vehicle events. Thus, the on-board interconnection system of the present application may relate to only some of the control elements schematically represented in fig. 1, and the overall interconnection system of the present application may relate to all of the control elements schematically represented in fig. 1.

The vehicle event described herein may include: triggering of vehicle functions (e.g., driver braking, autobraking, ABS, ESP), changes in vehicle operating conditions (e.g., engine, transmission conditions), changes in vehicle driving scenarios (e.g., driving environment), vehicle faults, vehicle traffic accidents, receiving control commands from the cloud platform CLD, and so forth.

Certain vehicle events may require only multiple ECUs within a certain subsystem to operate in combination or multiple ECUs within multiple subsystems to operate in combination. The in-vehicle interconnect system of the present application is configured for such vehicle events requiring multiple ECU co-operation.

According to one embodiment, in the block diagram shown in fig. 2, an in-vehicle interconnection system configured for single-type vehicle events of the present application is illustrated as an example. Assuming that a certain vehicle event A1 occurs, it is necessary to transmit comprehensive information of a plurality of ECUs, here represented by way of example by ECU1, ECU2, ECU3, to the cloud platform CLD. The present application relates to an in-vehicle interconnect system configured for a vehicle event A1, and to these ECUs, and to a remote communication terminal TB communicatively connected to these ECUs through an in-vehicle network.

Software of the process to be executed for the vehicle event A1 may be provided in one ECU, for example, the ECU 1. After the occurrence of the vehicle event A1, the ECU will learn of the vehicle event A1. For other relevant ECUs (e.g., ECU2, ECU 3), some of them may learn the vehicle event A1, and others may not learn the vehicle event A1.

When the vehicle event A1 occurs, each ECU that knows the vehicle event A1 issues a synchronization upload instruction to the vehicle-mounted network to upload data related to the vehicle event A1 to the remote communication terminal TB in synchronization, other ECUs related to the vehicle event A1 acquire the synchronization upload instruction from the vehicle-mounted network, and set synchronization information and perform a synchronization upload operation in a case where the vehicle event is determined to be related to itself, so that all ECUs related to the vehicle event A1 upload all data related to the vehicle event A1 to the remote communication terminal TB in synchronization. The remote communication terminal TB is wirelessly connected with the cloud platform CLD to transmit data related to the vehicle event A1 to the cloud platform CLD. The remote communication terminal TB may synchronously transmit all data related to the vehicle event A1 from different ECUs to the cloud platform CLD. In the cloud platform CLD, all data related to the vehicle event A1 from different ECUs are analyzed and processed, possibly integrated into a unified integration file to be sent to the background.

According to another embodiment, in the block diagram shown in fig. 3, an in-vehicle interconnection system configured for multiple types of vehicle events of the present application is illustrated as an example. Assuming that a certain vehicle event A1 occurs, it is necessary to transmit the integrated information of a plurality of ECUs (e.g., ECU1, ECU2, ECU 3) to the cloud platform CLD, and another vehicle event A2 occurs, it is necessary to transmit the integrated information of another plurality of ECUs (e.g., ECU3 to ECU n) to the cloud platform CLD. There may be one or more ECUs involved in different vehicle events. The present application relates to an ECU associated with various vehicle events, and a remote communication terminal TB communicatively connected to the ECU via an in-vehicle network.

In the embodiment shown in fig. 3, for a certain vehicle event, there may be some relevant ECUs that will learn about the vehicle event, and others that may not learn about the vehicle event. When the vehicle event occurs, each ECU that is aware of the vehicle event issues a synchronization upload instruction to the in-vehicle network to upload data related to the vehicle event to the remote communication terminal TB in synchronization, other ECUs related to the vehicle event acquire the synchronization upload instruction from the in-vehicle network, and set synchronization information and perform a synchronization upload operation in a case where the vehicle event is determined to be related to itself, so that all ECUs related to the vehicle event upload all data related to the vehicle event to the remote communication terminal TB in synchronization. The remote communication terminal TB transmits data related to the occurred vehicle event to the cloud platform CLD in synchronization. The remote communication terminal TB may synchronously transmit all data related to the occurred vehicle event from the different ECUs to the cloud platform CLD. In the cloud platform CLD, all data related to the vehicle event from different ECUs are analyzed and processed, possibly integrated into a unified integration file to be sent to the background.

Alternatively, according to a modification shown in fig. 4, the vehicle-mounted interconnection system (for a single type of vehicle event or multiple types of vehicle events) of the present application may be configured, when a certain vehicle event occurs to trigger a certain ECU or certain ECUs to issue a synchronous upload instruction to the vehicle-mounted network, to cause all the ECUs involved in the vehicle event to synchronously upload all the data involved in the vehicle event to the vehicle CPU of the whole vehicle. The whole vehicle CPU may be configured to integrate the data to be synchronously uploaded and the data possibly provided by the whole vehicle CPU into a unified integration file, and upload the integration file to the remote communication terminal TB, where the remote communication terminal TB sends the integration file to the cloud platform CLD.

Alternatively, according to a modification not shown, the vehicle-mounted interconnection system for a single type vehicle event or multiple types of vehicle events of the present application may be configured, when a certain vehicle event occurs to trigger a certain ECU or certain ECUs to issue a synchronous upload instruction to the vehicle-mounted network, to cause all the ECUs involved in the vehicle event to synchronously upload all the data involved in the vehicle event to the ECU that issues the synchronous upload instruction. The ECU may be arranged to integrate all data to be uploaded synchronously into a unified integration file and upload the integration file to the remote communication terminal TB.

According to another modification, not shown, the software of the process to be performed for a certain vehicle event may be provided in one ECU, which may be referred to as a main ECU. At the time of occurrence of the vehicle event, the related processing software in the master ECU is executed to issue a synchronous upload instruction to the in-vehicle network so that each ECU related to the vehicle event synchronously uploads all data related to the vehicle event to the remote communication terminal TB. The modification that the main ECU sends the synchronous uploading instruction to other ECUs can reduce the data transmission quantity between ECUs and improve the control accuracy.

In a modification employing the master ECU, when a certain vehicle event occurs, a synchronous upload instruction may be issued to the in-vehicle network by the master ECU so that the other relevant ECUs transmit respective data related to the vehicle event to the master ECU. The main ECU integrates all data to be synchronously uploaded into a unified integration file and uploads the integration file to the remote communication terminal TB.

According to another modification, not shown, a domain processor (domain ECU) is provided for each subsystem (or domain) of the vehicle for managing the ECUs in that subsystem (or domain). When a certain ECU in the subsystem (or domain) knows a certain related vehicle event, the domain processor may issue a synchronization upload instruction to the on-board network, and all ECUs related to the vehicle event in the subsystem and possibly other related subsystems receive the synchronization upload instruction, so that each related ECU uploads respective data related to the vehicle event to the remote communication terminal TB. Alternatively, each relevant ECU may upload the respective data related to the vehicle event to the domain processor, where all the data are integrated into a unified integration file and then uploaded to the remote communication terminal TB.

The on-board interconnection system of the present application is a brake interconnection system of a vehicle, and the vehicle events involved include vehicle regular braking, ABS triggering, ESP triggering, braking system failure, and the like. Each ECU defines its associated various vehicle events therein.

The vehicle-mounted interconnection system (for single-type vehicle events or multi-type vehicle events) of the application can set an event authenticity detection mechanism, such as an anti-shake function-based detection mechanism, in each ECU capable of knowing the corresponding vehicle event. A vehicle event is considered a true event after the count value of a counter associated with the vehicle event reaches a set threshold.

A state machine may be provided in each ECU associated with a corresponding vehicle event for determining whether the vehicle event concerned is related to itself after receiving a synchronization upload instruction from the on-vehicle network, and establishing synchronization information only in the case of being related to itself, determining that the synchronization upload instruction is valid, and executing data associated with the synchronization upload vehicle event. On the other hand, the ECU, which is not related to the vehicle event, determines that the synchronization upload instruction is invalid for itself by the state machine after receiving the synchronization upload instruction from the in-vehicle network, and does not perform synchronization upload of data, which is not related to the vehicle event. Thereby, the uploading of redundant garbage is avoided.

One control scheme that may be implemented in the in-vehicle interconnect system of the present application is schematically illustrated in fig. 5. Wherein, on-vehicle interconnected system can have three states: a normal running state ST1, a ready synchronization state ST2, a synchronization uploading state ST3, and can be switched between these three states by operation.

Specifically, when no vehicle event occurs, the on-board interconnection system is in the normal operation state ST1 in which it is possible to transmit the required vehicle data to the cloud platform CLD in a continuous manner. After a certain vehicle event associated with the vehicle-mounted interconnection system occurs, the vehicle event triggers a synchronous uploading request in one or more ECUs (electronic control units) which acquire the event, and the vehicle-mounted interconnection system enters a state of preparation for synchronization ST2. In the state of preparing synchronization ST2, the ECU which knows the event evaluates the authenticity of the vehicle event after the time window is passed, if the vehicle event is evaluated to be true, the ECU which knows the event sends out a synchronization uploading instruction to other relevant ECUs, and the vehicle-mounted interconnection system enters a synchronization uploading state ST3. In the synchronous upload state ST3, each ECU involved in a vehicle event collects and uploads vehicle data related to the vehicle event, and then the on-vehicle interconnect system returns to the normal operation state ST1. In the ready to synchronize state ST2, if the ECU that has learned about the event denies the authenticity of the vehicle event after the lapse of the time window, the in-vehicle interconnect system returns to the normal operation state ST1 without performing the data synchronization upload. In the normal operation state ST1, each ECU can upload data to the remote communication terminal TB independently of each other.

In the vehicle-mounted interconnection system configured for multiple types of vehicle events, if the occurrence of a certain vehicle event only needs to upload related data of a single ECU, the single ECU judges that other ECUs are not needed to synchronously upload data through a state machine, and therefore the data is only uploaded to the remote communication terminal TB through the single ECU so as to be sent to the cloud platform CLD.

One control method that may be implemented in the in-vehicle interconnect system of the present application is schematically illustrated in fig. 6.

In this control flow, first, the in-vehicle interconnection system is started in step S1.

Next, at step S2, a vehicle event (possibly one event occurring or multiple events occurring simultaneously) associated with the on-board interconnection system is detected.

Next, in step S3, the authenticity of the vehicle event is evaluated by an event authenticity detection mechanism in the ECU that knows the vehicle event.

Next, in step S4, it is determined in the ECU that has learned the vehicle event whether the vehicle event requires other ECUs to collect and upload data synchronously. If the judgment result in the step S4 is negative, executing a step S5; if the determination in step S4 is yes, step S6 is performed.

In step S5, the ECU (possibly one or more ECUs) that learn of the vehicle event independently uploads data related to the vehicle event therein to the remote communication terminal. After step S5 is completed, step S8 is performed.

In step S6, the ECU that knows the vehicle event issues a synchronization upload instruction to the vehicle-mounted network, and the other ECUs related to the vehicle event receive the synchronization upload instruction and establish synchronization information.

Next, in step S7, all ECU related to the vehicle event synchronously collect all event related data and upload to the remote communication terminal. After step S7 is completed, step S8 is performed.

At step S8, all data related to the event is transmitted to the cloud platform via the remote communication terminal. The sending mode of the event related data may include: each ECU related to the vehicle event synchronously uploads the respective event related data to the remote communication terminal; and integrating the event related data into a unified integration file by the whole CPU or the event related domain processor or the event related main ECU of the whole vehicle, and uploading the integration file to the remote communication terminal.

Various adaptations of the various steps shown in fig. 6 and described above may be performed by those skilled in the art.

Regarding the synchronization upload instruction, the entire vehicle CPU or the event-related domain processor or the event-related main ECU may issue the synchronization upload instruction to the vehicle-mounted network, and the other event-related ECUs receive the synchronization upload instruction from the vehicle-mounted network, and establish synchronization information and perform the synchronization upload operation in the case that the vehicle event is related to itself. The ECU, which is not related to the vehicle event, determines by the state machine that the synchronous upload instruction is invalid for itself, and does not perform the operation of synchronously uploading data.

In addition, the ECUs involved in some vehicle events are not clearly distinguished from each other in the vehicle event, but are located in substantially equal positions. For example, in a vehicle crash event, multiple ECUs in multiple subsystems may be required to take action simultaneously and upload data synchronously. For such an event, a master ECU requiring priority of taking measures may be selected from among a plurality of ECUs, and this ECU issues a synchronization upload instruction to the in-vehicle network, and other relevant ECUs receive the synchronization upload instruction from the in-vehicle network. For different vehicle events, it may be desirable to choose different ECUs as the master ECU. For this purpose, a synchronization upload instruction is defined herein as an instruction that can be issued by an ECU to the in-vehicle network and that can be received by other ECUs by the in-vehicle network.

Under the condition that the vehicle-mounted interconnection system adopts a CAN bus transmission mode, the synchronous uploading instruction is in the form of a message transmitted on the CAN. The specific format may employ PDUs (protocol data units). A PDU is a specific data frame format that is suitable for transmission over CAN for use in a vehicle. In view of reducing CAN communication load, multiplexing PDU mode transmission is adopted here, wherein different PDUs adopt the same CAN ID. Thus, in order to clearly distinguish the synchronous upload instruction from various data transmitted between ECUs, the PDU of the synchronous upload instruction may be given a new message ID, for example, (0×11), to characterize the transmitted data as the synchronous upload instruction. And each frame of PDU contains a synchronization flag bit and synchronization information. Thereby, it is ensured that dedicated synchronous upload instructions are accurately transmitted and recognized between different ECUs.

In the case of the vehicle interconnection system of the present application that uses other vehicle networks to implement data uploading, for example, CANFD, flexray, ethernet, the synchronous uploading command format may also be set similarly.

According to the vehicle-mounted interconnection system and the related control method, after a certain vehicle event occurs, based on data interconnection among ECUs, the issuing and receiving of the synchronous uploading instruction among the ECUs are realized through the vehicle-mounted network, so that the comprehensive data of all ECUs related to the event are synchronously collected and uploaded to the cloud platform through the remote communication terminal. Compared with the scheme that each ECU independently collects data, the scheme of the application can collect and transmit comprehensive and practical data related to the event more quickly and accurately, avoids incomplete data caused by that some ECUs are not informed of the vehicle event, and also can avoid redundant uploading of data of ECUs unrelated to the vehicle event, so that a cloud platform or a data analysis platform can process related data of the vehicle event timely and accurately and give vehicle feedback (feedback information, control signals and the like) when necessary.

Although the present application is described herein with reference to specific embodiments, the scope of the application is not intended to be limited to the details shown. Various modifications may be made to these details without departing from the underlying principles of the present application.

Claims (11)

1. An event-based on-board interconnect system, comprising:

a plurality of ECUs communicatively connected via an on-board network, each ECU defining its associated vehicle event therein; and

a remote communication terminal in communication with each ECU through a vehicle-mounted network;

the in-vehicle interconnect system is configured to:

after a certain vehicle event occurs, acquiring the vehicle event and issuing a synchronous uploading instruction to a vehicle-mounted network by an ECU (electronic control unit) associated with the vehicle event;

other ECUs associated with the vehicle event receive the synchronous upload instruction by an on-board network;

based on the synchronous uploading instruction, each ECU associated with the vehicle event synchronously collects event related data and uploads the synchronously collected event related data to the remote communication terminal;

and the remote communication terminal wirelessly transmits the event related data to a cloud platform associated with the vehicle.

2. The on-board interconnection system of claim 1, wherein the on-board interconnection system is an on-board interconnection system for single type vehicle events or an on-board interconnection system, in particular a whole vehicle interconnection system, for multiple types of vehicle events;

for example, the vehicle-mounted interconnection system is a brake interconnection system.

3. The in-vehicle interconnect system according to claim 1 or 2, wherein a state machine is provided in each ECU, the state machine being configured to establish synchronization information between each ECU associated with the vehicle event based on validity of the synchronization upload instruction, and to execute synchronization upload event related data based on the synchronization information.

4. The vehicle-mounted interconnection system according to claim 3, wherein an event authenticity detection mechanism, such as an anti-shake function-based event authenticity detection mechanism, is provided in each ECU for evaluating the authenticity of the vehicle event, thereby judging the validity of the synchronous upload instruction.

5. The in-vehicle interconnection system of any of claims 1-4, wherein the in-vehicle interconnection system has three states: a normal running state, a ready to synchronize state, a synchronize upload state, and configured to switch between these three states based on the authenticity of the vehicle event and the validity of the synchronize upload instruction.

6. The in-vehicle interconnect system according to any one of claims 1 to 5, wherein each ECU associated with the vehicle event synchronously uploads event related data collected synchronously to the remote communication terminal, respectively.

7. The vehicle-mounted interconnection system according to any one of claims 1 to 5, wherein each ECU associated with the vehicle event uploads event related data collected synchronously to a whole vehicle CPU, respectively, the whole vehicle CPU integrates the event related data into a unified integration file, and uploads the integration file to the remote communication terminal.

8. The in-vehicle interconnection system according to any one of claims 1 to 5, wherein a main ECU is included in the plurality of ECUs, software of a process to be executed for the vehicle event is provided in the main ECU, and the synchronization upload instruction is issued to an in-vehicle network by the main ECU;

alternatively, other ECUs associated with the vehicle event upload event related data collected synchronously to the master ECU, respectively, which integrates the event related data into a unified integration file and uploads the integration file to the remote communication terminal.

9. The on-board interconnection system of any of claims 1-5, wherein the plurality of ECUs include a domain processor therein for a vehicle subsystem, the domain processor managing each ECU within the vehicle subsystem and configured to issue the synchronous upload instructions to an on-board network;

optionally, each ECU associated with the vehicle event in the vehicle subsystem where the domain processor is located, and each ECU associated with the vehicle event in the other vehicle subsystems upload event related data collected synchronously to the domain processor, respectively, and the domain processor integrates the event related data into a unified integration file and uploads the integration file to the remote communication terminal.

10. The vehicle-mounted interconnection system according to any one of claims 1-9, wherein the format of the synchronization uploading instruction is a PDU to which a message ID representing that a message type transmitted between ECUs is the synchronization uploading instruction is added, and the PDU further includes a synchronization flag bit and synchronization information.

11. A vehicle-mounted interconnection system control method comprises the following steps:

detecting a vehicle event associated with the vehicle-mounted interconnection system;

confirming the authenticity of the vehicle event by a vehicle ECU (electronic control Unit) which is informed of the vehicle event and is associated with the vehicle event, and issuing a synchronous uploading instruction to a vehicle-mounted network;

other ECUs associated with the vehicle event receive the synchronous upload instruction by an on-board network;

based on the synchronous uploading instruction, each ECU associated with the vehicle event synchronously collects event related data and uploads the synchronously collected event related data to the remote communication terminal;

the remote communication terminal wirelessly transmits the event related data to a cloud platform associated with a vehicle;

optionally, the vehicle-mounted interconnection system is a vehicle-mounted interconnection system according to any one of claims 1-10.