A multi-path gateway diagnostic data interaction method

Abstract

The application discloses a multi-path gateway diagnosis data interaction method, wherein a central gateway receives three kinds of data requests of local diagnosis, OTA upgrade diagnosis and remote diagnosis, arbitrates the local diagnosis data request, the OTA upgrade diagnosis data request and the remote diagnosis data request according to preset arbitration rules, and executes diagnosis data interaction according to an arbitration result. The application systematically solves the conflict problem when multiple diagnosis data are simultaneously interacted, and guarantees the completeness of diagnosis data and the functional safety of a vehicle.

Description

Technical Field

[0001] This invention relates to the field of automotive automation control technology, and in particular to a method for multi-channel gateway diagnostic data interaction. Background Technology

[0002] Intelligent connected vehicles have various diagnostic data interaction requirements, mainly including local diagnostics, remote diagnostics, and OTA data upgrade diagnostics. These diagnostic data use the same CAN data interaction. When multiple diagnostic data need to be used at the same time, there may be conflicts, which can lead to diagnostic data disorder and thus abnormal diagnostic functions.

[0003] The patent titled "A Platform-Based Gateway Routing Method for Automotive Flashing and Diagnostic Testing" (patent application number CN202110702520.7) discloses a technical solution: When two flashing and diagnostic methods exist simultaneously in a vehicle, local diagnostics, typically used by professional technicians, is crucial. By prioritizing local diagnostics, when conflicts arise, the communication module for remote diagnostics is promptly disconnected or shut down to disable remote diagnostics and prevent conflicts between local and remote diagnostics. However, this approach, where local diagnostics completely override remote diagnostics, can lead to abnormal interruptions in the vehicle upgrade process, resulting in ECU software loss, vehicle malfunctions, increased risk of abnormal vehicle operation, and unnecessary after-sales repair needs. Summary of the Invention

[0004] The purpose of this invention is to provide a method for multi-channel gateway diagnostic data interaction to solve the problem of prioritizing multi-channel diagnostic data.

[0005] The technical solution adopted in this invention is:

[0006] A multi-channel gateway diagnostic data interaction method, applied to the central gateway of a vehicle, the method comprising:

[0007] The central gateway receives local diagnostic data requests from the local diagnostic interface, OTA upgrade diagnostic data requests from the OTA host, and remote diagnostic data requests from the remote communication unit.

[0008] Arbitration is conducted for local diagnostic data requests, OTA upgrade diagnostic data requests, and remote diagnostic data requests in accordance with the preset arbitration rules;

[0009] Based on the arbitration result, diagnostic data exchange will be implemented.

[0010] Furthermore, based on the arbitration rules, other types of diagnostic data interaction are prohibited from being initiated during the execution of local diagnostic data interaction or OTA upgrade diagnostic data interaction; if a local diagnostic data request or OTA upgrade diagnostic data request is received during the execution of remote diagnostic data interaction, the remote diagnostic data interaction shall be interrupted.

[0011] Furthermore, the arbitration rules specifically include:

[0012] When a local diagnostic data request is received, if the process is not currently in the process of OTA upgrade diagnostic data interaction, the local diagnostic data request will be responded to and the local diagnostic data interaction will be executed, and other diagnostic data interactions will be prohibited from being started during the execution.

[0013] When an OTA upgrade diagnostic data request is received, if the local diagnostic data interaction is not currently in progress, the OTA upgrade diagnostic data request will be responded to and the OTA upgrade diagnostic data interaction will be executed. During the execution, other diagnostic data interactions will be prohibited from being started.

[0014] When a remote diagnostic data request is received, if the system is not currently in the process of local diagnostic data interaction or OTA upgrade diagnostic data interaction, it will respond to the remote diagnostic data request and perform remote diagnostic data interaction.

[0015] Furthermore, when diagnostic data interaction is not initiated, if the central gateway receives at least two of the following at the same time: local diagnostic data request, OTA upgrade diagnostic data request, and remote diagnostic data request, it will respond to only the request with the highest priority according to the preset priority order of local diagnostics > OTA upgrade diagnostics > remote diagnostics, and refuse to respond to the request with the lower priority.

[0016] Furthermore, the interaction method of the present invention also includes:

[0017] A status indication bit signal is sent to the remote communication unit and the OTA host. The status indication bit signal includes a local diagnostic status indication bit, an OTA upgrade status indication bit, and a remote diagnostic status indication bit, which are used to indicate whether the corresponding diagnostic data interaction is active.

[0018] Furthermore, when the corresponding diagnostic data interaction is enabled, its corresponding status indicator signal is set to 1; when the corresponding diagnostic data interaction is disabled, its corresponding status indicator signal is set to 0; the status indicator signal is sent by the central gateway to the remote communication unit and the OTA host through periodic messages.

[0019] Furthermore, responding to local diagnostic data requests and performing local diagnostic data interactions includes:

[0020] Before responding to a local diagnostic data request, determine whether the vehicle is currently in the process of exchanging diagnostic data for an OTA update;

[0021] If not, a handshake success response is returned to the local diagnostic interface, and the local diagnostic data routing function is enabled to perform local diagnostic data interaction.

[0022] Furthermore, responding to OTA upgrade diagnostic data requests and performing OTA upgrade diagnostic data interaction includes:

[0023] Before responding to OTA upgrade diagnostic data requests, determine whether the vehicle is currently in the process of local diagnostic data exchange;

[0024] If not, then further determine whether the vehicle is currently in the process of remote diagnostic data exchange;

[0025] If so, first interrupt the remote diagnostic data interaction, then respond to the OTA upgrade diagnostic data request, and enable the OTA diagnostic data routing function to perform the OTA upgrade diagnostic data interaction.

[0026] Furthermore, before responding to OTA upgrade diagnostic data requests, it is necessary to determine whether the vehicle status meets the preset upgrade conditions; the vehicle status includes power mode, vehicle stationary status, battery level, and vehicle fault status, all of which must be met.

[0027] Furthermore, the process of performing local diagnostic data exchange, OTA upgrade diagnostic data exchange, or remote diagnostic data exchange also includes:

[0028] Monitor the corresponding diagnostic data channels;

[0029] If no valid diagnostic data is detected within the preset timeout period, the current diagnostic data interaction is considered to have ended, and the corresponding diagnostic data routing function is disabled.

[0030] The present invention adopts the above technical solution and has the following beneficial technical effects:

[0031] This invention standardizes the priority of multi-channel diagnostic data, avoids conflicts in multi-channel diagnostic data interaction, and can meet the data interaction requirements of local diagnostics, remote diagnostics, and OTA upgrade diagnostic functions. By adopting the gateway diagnostic data interaction technology of this patent, diagnostic function abnormalities caused by multi-channel diagnostic data conflicts can be avoided, ensuring the integrity of diagnostic data interaction and preventing vehicle function abnormalities caused by data priority issues. Attached Figure Description

[0032] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments;

[0033] Figure 1 This is a system architecture diagram on which the present invention is based;

[0034] Figure 2 A flowchart illustrating the process of interacting with local diagnostic data;

[0035] Figure 3 A flowchart illustrating the process of data interaction for OTA upgrade diagnostics;

[0036] Figure 4 A flowchart illustrating the process of remote diagnostic data interaction. Detailed Implementation

[0037] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings.

[0038] This invention provides a multi-channel gateway diagnostic data interaction method, applied to the central gateway of a vehicle. For example... Figure 1 As shown, the system architecture on which this method is based includes: a central gateway (CGW), a diagnostic tool connected via the vehicle's OBD interface, an in-vehicle entertainment host (as an OTA host), a remote communication unit (T-Box), and various functional domains within the vehicle (such as the power domain, chassis domain, body domain, and entertainment domain).

[0039] This system involves three types of diagnostic data streams:

[0040] (1) Local diagnostic data: The diagnostic instrument is connected to the vehicle's OBD diagnostic interface and sends diagnostic requests to the central gateway to realize functions such as vehicle fault reading and clearing, calibration matching learning, data reading, and software upgrade.

[0041] (2) OTA upgrade diagnostic data: The OTA host (usually the in-vehicle entertainment host) obtains the upgrade task and data package from the cloud OTA server, and then sends the upgrade diagnostic request to the central gateway to realize the identification of vehicle VIN and software and hardware version information and the upgrade of each ECU software.

[0042] (3) Remote diagnostic data: The diagnostic requirements of the TSP platform are obtained by the remote communication unit (TBOX) and sent to the central gateway to realize the acquisition of vehicle software and hardware version information, and the acquisition and clearing of fault DTC.

[0043] As the hub of the vehicle's network, the central gateway connects multiple networks within the vehicle, including the powertrain domain, chassis domain, body domain, and entertainment domain. One of its core functions is to accurately route diagnostic data from these different sources to the target ECUs located in different network domains. When multiple diagnostic data streams are generated simultaneously or nearly simultaneously and conflict with each other, the central gateway will prioritize and arbitrate them according to the multi-gateway diagnostic data interaction technology defined in this invention, thereby fundamentally avoiding data interaction conflicts.

[0044] In this invention, the central gateway receives local diagnostic data requests from the local diagnostic interface, OTA upgrade diagnostic data requests from the OTA host, and remote diagnostic data requests from the remote communication unit. Based on preset arbitration rules, the local diagnostic data requests, OTA upgrade diagnostic data requests, and remote diagnostic data requests are arbitrated; and based on the arbitration result, diagnostic data interaction is performed.

[0045] Based on the arbitration rules, other types of diagnostic data interaction are prohibited from being initiated during the execution of local diagnostic data interaction or OTA upgrade diagnostic data interaction; if a local diagnostic data request or OTA upgrade diagnostic data request is received during the execution of remote diagnostic data interaction, the remote diagnostic data interaction shall be interrupted.

[0046] The arbitration rules specifically include:

[0047] When a local diagnostic data request is received, if the process is not currently in the process of OTA upgrade diagnostic data interaction, the local diagnostic data request will be responded to and the local diagnostic data interaction will be executed. During the execution, other diagnostic data interactions will be prohibited (i.e., OTA upgrade diagnostic data interaction and remote diagnostic data interaction will be prohibited).

[0048] When an OTA upgrade diagnostic data request is received, if the local diagnostic data interaction is not currently in progress, the OTA upgrade diagnostic data request will be responded to and the OTA upgrade diagnostic data interaction will be executed. During the execution, other diagnostic data interactions will be prohibited from being started.

[0049] When a remote diagnostic data request is received, if the user is not currently in a local diagnostic data interaction process or an OTA upgrade diagnostic data interaction process, the user will respond to the remote diagnostic data request and execute the remote diagnostic data interaction. If a local diagnostic data request or an OTA upgrade diagnostic data request is received during the execution of the remote diagnostic data interaction, the remote diagnostic data interaction will be interrupted.

[0050] When diagnostic data interaction is not started, if the central gateway receives at least two of the following: local diagnostic data request, OTA upgrade diagnostic data request, and remote diagnostic data request, it will respond to only the request with the highest priority according to the preset priority order of local diagnostics > OTA upgrade diagnostics > remote diagnostics, and refuse to respond to the request with the lower priority.

[0051] To facilitate understanding of the current diagnostic status of the central gateway by various diagnostic sources, the central gateway sends status indicator signals to the remote communication unit and OTA host via periodic messages. These status indicator signals include local diagnostic status indicator bits, OTA upgrade status indicator bits, and remote diagnostic status indicator bits, which are used to indicate whether the corresponding diagnostic data interaction is active. For example, when local diagnostic data interaction is enabled, the local diagnostic status indicator bit is 1; otherwise, it is set to 0. The same applies to the OTA upgrade status indicator bit and the remote diagnostic status indicator bit.

[0052] During any diagnostic data interaction, the central gateway monitors the corresponding diagnostic data channel. If no valid diagnostic data is detected within a preset timeout period (preferably 5 seconds in this embodiment), the current diagnostic data interaction is considered to have ended, and the corresponding diagnostic data routing function is disabled.

[0053] The specific implementation process of the three diagnostic interactions in this invention is as follows:

[0054] I. Combination Figure 2 The flowchart and specific steps for local diagnostic data interaction are as follows:

[0055] (1) Local diagnostics begins. The diagnostic instrument sends a local diagnostic handshake request to the central gateway through the OBD diagnostic interface.

[0056] (2) After receiving the local diagnostic data request, the central gateway first determines whether the vehicle is currently in the process of OTA upgrade diagnostic data interaction (i.e., checks whether the OTA upgrade status indicator bit is 1). If so, the central gateway responds to the diagnostic tool with a handshake failure and prompts the user "The vehicle is currently undergoing OTA upgrade, please wait for the OTA upgrade to complete".

[0057] (3) If the central gateway determines that it is not currently in the process of OTA upgrade diagnostic data interaction, it will return a handshake success response to the diagnostic instrument, set the local diagnostic status indicator bit to 1, and enable the local diagnostic data routing function, that is, enable message routing between the diagnostic CAN and other CAN network segments.

[0058] (4) During the diagnostic process, the central gateway continuously monitors the diagnostic data on the diagnostic CAN bus. If a 5-second diagnostic timeout occurs on the diagnostic CAN bus (i.e., no diagnostic message is received from the diagnostic instrument within 5 seconds), the central gateway determines that the local diagnostic process has ended, sets the local diagnostic status indicator bit to 0, and disables the diagnostic message routing function between the diagnostic CAN and other CAN network segments.

[0059] II. Combination Figure 3 The flowchart illustrates the specific steps for OTA upgrade diagnostic data interaction:

[0060] (1) The OTA host (vehicle entertainment host) obtains the corresponding OTA upgrade data from the OTA server. After the user selects the upgrade time, the OTA host starts the OTA upgrade process according to the time selected by the user.

[0061] (2) The OTA host starts the OTA upgrade diagnostic process according to the time selected by the user. The OTA host determines whether the local diagnostic status indicator bit of the central gateway is 1. If it is 1, it continues to wait for the local diagnostic to be completed.

[0062] (3) If the local diagnostic status indicator bit is 0, the OTA host will further determine whether the vehicle status meets the upgrade requirements (the vehicle status includes power mode, vehicle stationary status, battery level and vehicle fault status, all of which must meet the preset upgrade conditions). If the requirements are met, the OTA upgrade diagnostic service will be enabled.

[0063] (4) The OTA host sends an OTA upgrade diagnostic handshake request to the central gateway. Upon receiving the request, the central gateway first determines whether remote diagnostic data is in the process of interaction. If so, the central gateway immediately interrupts the remote diagnostic data interaction: sets the remote diagnostic status indicator bit to 0, stops the routing of remote diagnostic messages, and sends a remote diagnostic stop notification to the remote communication unit.

[0064] (5) After remote diagnostics is interrupted (or remote diagnostics was not activated in the first place), the central gateway responds to the handshake request of the OTA host, returns a handshake success response, sets the OTA upgrade status indicator bit to 1, and enables the OTA diagnostic data routing function.

[0065] (6) During the diagnostic process, the central gateway monitors the OTA upgrade diagnostic data channel. If a 5-second diagnostic timeout occurs on the diagnostic CAN bus, the central gateway determines that the OTA upgrade diagnostic is complete, sets the OTA upgrade status indicator bit to 0, and disables the diagnostic message routing function between the information CAN and other CAN network segments.

[0066] (7) After the OTA upgrade diagnosis is completed, the OTA host actively sends a disconnect handshake request to the central gateway. After receiving the request, the central gateway determines that the OTA data interaction is complete, sets the OTA upgrade status indicator bit to 0, and disables the corresponding diagnostic message routing function.

[0067] III. Combination Figure 4 The flowchart illustrates the specific steps for remote diagnostic data interaction:

[0068] (1) Before remote diagnostics begins, the remote communication unit (TBOX) first obtains the status indication signal sent by the central gateway (through periodic messages) to determine whether the vehicle is in local diagnostics or OTA upgrade diagnostics. If the local diagnostics status indication bit is 1 or the OTA upgrade status indication bit is 1, the TBOX reports to the TSP platform that "the vehicle is in the process of local diagnostics or OTA upgrade, and remote diagnostics cannot be started".

[0069] (2) If the vehicle is not currently in local diagnostic state and is not in OTA upgrade diagnostic state, then TBOX will enable remote diagnostic function and send a remote diagnostic request to the central gateway.

[0070] (3) After receiving the remote diagnostic request, the central gateway will determine whether the vehicle is in the process of local diagnostics or OTA upgrade diagnostics. If either process is in progress, the central gateway will not respond to the remote diagnostic request.

[0071] (4) If the vehicle is not in the local diagnostic or OTA upgrade diagnostic process, the central gateway will set the remote diagnostic status indicator to 1 and enable the TBOX diagnostic message routing function to start remote diagnostic data interaction.

[0072] (5) During remote diagnostic data interaction, as soon as the central gateway receives a local diagnostic data request or an OTA upgrade diagnostic data request, it will immediately set the remote diagnostic status indicator bit to 0, interrupt the remote diagnostic message routing, and stop the remote diagnostic service.

[0073] (6) During the remote diagnostic data exchange process, the central gateway also monitors whether the remote diagnostic message has a 5-second diagnostic timeout. If so, the central gateway determines that the remote diagnostic has ended, sets the remote diagnostic status indicator bit to 0, and stops the routing of the remote diagnostic message.

[0074] Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Without conflict, the embodiments and features described and illustrated herein can be combined with each other. The components of the embodiments of the present invention generally described and illustrated in the accompanying drawings can be arranged and designed in various different configurations. Therefore, the detailed description of the embodiments of the present invention is not intended to limit the scope of the claimed invention, but merely to illustrate selected embodiments of the invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without inventive effort are within the scope of protection of the present invention.

Claims

1. A multi-channel gateway diagnostic data interaction method, applied to the central gateway of a vehicle, characterized in that: The method includes: The central gateway receives local diagnostic data requests from the local diagnostic interface, OTA upgrade diagnostic data requests from the OTA host, and remote diagnostic data requests from the remote communication unit. Arbitration is conducted for local diagnostic data requests, OTA upgrade diagnostic data requests, and remote diagnostic data requests in accordance with the preset arbitration rules; Based on the arbitration result, diagnostic data exchange will be implemented.

2. The multi-channel gateway diagnostic data interaction method according to claim 1, characterized in that: Based on the arbitration rules, other types of diagnostic data interaction are prohibited from being initiated during the execution of local diagnostic data interaction or OTA upgrade diagnostic data interaction; if a local diagnostic data request or OTA upgrade diagnostic data request is received during the execution of remote diagnostic data interaction, the remote diagnostic data interaction shall be interrupted.

3. The method of claim 2, wherein: The arbitration rules specifically include: When a local diagnostic data request is received, if the process is not currently in the process of OTA upgrade diagnostic data interaction, the local diagnostic data request will be responded to and the local diagnostic data interaction will be executed, and other diagnostic data interactions will be prohibited from being started during the execution. When an OTA upgrade diagnostic data request is received, if the local diagnostic data interaction is not currently in progress, the OTA upgrade diagnostic data request will be responded to and the OTA upgrade diagnostic data interaction will be executed. During the execution, other diagnostic data interactions will be prohibited from being started. When a remote diagnostic data request is received, if the system is not currently in the process of local diagnostic data interaction or OTA upgrade diagnostic data interaction, it will respond to the remote diagnostic data request and perform remote diagnostic data interaction.

4. The method of claim 1, wherein: When diagnostic data interaction is not started, if the central gateway receives at least two of the following: local diagnostic data request, OTA upgrade diagnostic data request, and remote diagnostic data request, it will respond to only the request with the highest priority according to the preset priority order of local diagnostics > OTA upgrade diagnostics > remote diagnostics, and refuse to respond to the request with the lower priority.

5. The method of claim 1 to 3, wherein: Also includes: A status indication bit signal is sent to the remote communication unit and the OTA host. The status indication bit signal includes a local diagnostic status indication bit, an OTA upgrade status indication bit, and a remote diagnostic status indication bit, which are used to indicate whether the corresponding diagnostic data interaction is active.

6. The method of claim 5, wherein: When the corresponding diagnostic data interaction is enabled, its corresponding status indicator bit signal is set to 1; when the corresponding diagnostic data interaction is disabled, its corresponding status indicator bit signal is set to 0; the status indicator bit signal is sent by the central gateway to the remote communication unit and the OTA host through periodic messages.

7. The method of claim 3, wherein: Responding to local diagnostic data requests and performing local diagnostic data interactions, including: Before responding to a local diagnostic data request, determine whether the vehicle is currently in the process of exchanging diagnostic data for an OTA update; If not, a handshake success response is returned to the local diagnostic interface, and the local diagnostic data routing function is enabled to perform local diagnostic data interaction.

8. The method of claim 3, wherein: Responding to OTA upgrade diagnostic data requests and performing OTA upgrade diagnostic data interaction, including: Before responding to OTA upgrade diagnostic data requests, determine whether the vehicle is currently in the process of local diagnostic data exchange; If not, then further determine whether the vehicle is currently in the process of remote diagnostic data exchange; If so, first interrupt the remote diagnostic data interaction, then respond to the OTA upgrade diagnostic data request, and enable the OTA diagnostic data routing function to perform the OTA upgrade diagnostic data interaction.

9. The method of claim 8, wherein: Before responding to OTA upgrade diagnostic data requests, it is necessary to determine whether the vehicle status meets the preset upgrade conditions; the vehicle status includes power mode, vehicle stationary status, battery level, and vehicle fault status, all of which must be met.

10. The method of claim 1, wherein: The process of performing local diagnostic data exchange, OTA upgrade diagnostic data exchange, or remote diagnostic data exchange also includes: Monitor the corresponding diagnostic data channels; If no valid diagnostic data is detected within the preset timeout period, the current diagnostic data interaction is considered to have ended, and the corresponding diagnostic data routing function is disabled.

Images