DIAGNOSTIC SYSTEM AND PROCEDURES FOR A CENTRAL ENGINE CONTROL UNIT
Patent Information
- Application Number
- DE602022043116
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2021-06-23
- Filing Date
- 2022-06-22
- Publication Date
- 2026-09-16
- Estimated Expiration
- 2042-06-22
AI Technical Summary
The existing vehicle controller diagnosis methods are inefficient and cannot perform real-time diagnosis of multiple application programs simultaneously, leading to low diagnosis efficiency and inability to diagnose integrated application programs independently.
A diagnosis system and method for a vehicle central controller that utilizes a parallel diagnosis component in the main process to synchronize and diagnose multiple application components in sub-processes through Inter-Process Communication (IPC), enabling real-time and efficient diagnosis without altering the original design of the diagnosis device.
The system enables real-time and synchronous diagnosis of multiple application programs, improving diagnosis efficiency and maintaining independence of each program's diagnosis, while maintaining compatibility with existing diagnosis devices.
Description
Cross-Reference to Related Application
[0001] The disclosure claims priority to Chinese Patent Application No. 202110697531.0 filed to the China National Intellectual Property Administration on June 23, 2021.Technical Field
[0002] Embodiments of the disclosure relate to technical field of vehicle controllers, for example, to a diagnosis system and method for a vehicle central controller.Background
[0003] At present, with the development of the intelligent connected vehicle industry and technology, the electronic and electrical architecture of the entire vehicle is also changed from a distributed architecture to a centralized architecture. A bus architecture of a distributed architecture controller unit is gradually evolved into an architectural form that combines a central control unit with a regional communication.
[0004] As the electronic and electrical architecture of the entire vehicle develops, a vehicle controller tends to be integrated, the number of the vehicle controllers is also lower than before, and a plurality of application programs with different functions are integrated onto the same hardware controller. In a vehicle controller diagnosis method in the related art, an application program on a controller may be diagnosed, but the plurality of application programs in the controller cannot be diagnosed independently.
[0005] Therefore, the following technical problems exist in the related art. The diagnosis efficiency of a vehicle controller is relatively low; and when there are troubles in the plurality of application programs on the controller at the same time, real-time diagnosis of the plurality of application programs cannot be realized in the related art.
[0006] WO 2021 / 043660 A1 discloses an electrical architecture or service-oriented vehicle diagnostics.
[0007] US 2021 / 0157902 A1 discloses a vehicle information communication system.
[0008] CN 103348230 A discloses a system and method for recognizing, diagnosing, maintaining and repairing vehicle.Summary
[0009] The present invention is defined in the appended independent claims.
[0010] Further embodiments are set out in the appended dependent claims.
[0011] Embodiments of the disclosure provide a diagnosis system and method for a vehicle central controller, to realize synchronization and real-time diagnosis of a plurality of application programs on a vehicle, so as to improve the diagnosis efficiency of a vehicle controller.
[0012] According to a first aspect, an embodiment of the disclosure provides a diagnosis system for a vehicle central controller. The diagnosis system includes the vehicle central controller and at least one diagnosis device. The vehicle central controller includes a parallel diagnosis component deployed in a main process, and at least one application component deployed in at least one sub-process.
[0013] The at least one diagnosis device is connected to the parallel diagnosis component; the at least one diagnosis device is configured to send, to the parallel diagnosis component, a diagnosis request for diagnosing the application component, wherein the diagnosis request carries a diagnosis identifier.
[0014] The parallel diagnosis component is configured to determine, on the basis of the diagnosis identifier, the application component corresponding to the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device, and transmit, in a Inter-Process Communication manner, the diagnosis request to the application component corresponding to the diagnosis request.
[0015] Each application component is configured to process the received diagnosis request, and transmit a processing result of the diagnosis request to the parallel diagnosis component in an IPC manner.
[0016] The parallel diagnosis component is further configured to send the processing result to the diagnosis device corresponding to the diagnosis request.
[0017] According to a second aspect, an embodiment of the disclosure further provides a diagnosis method for a vehicle central controller. The diagnosis method includes the following operations.
[0018] A diagnosis request for diagnosing the application component sent by at least one diagnosis device is received on the basis of a parallel diagnosis component deployed in a main process of the vehicle central controller, wherein the diagnosis request carries a diagnosis identifier.
[0019] The parallel diagnosis component determines the application component corresponding to the diagnosis request on the basis of the diagnosis identifier, and transmits, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request.
[0020] The parallel diagnosis component acquires a processing result of the diagnosis request from the application component in an IPC manner, wherein the processing result of the diagnosis request is obtained by processing the received diagnosis request through the application component.
[0021] The parallel diagnosis component sends the processing result to the diagnosis device corresponding to the diagnosis request.Brief Description of the Drawings
[0022] Fig. 1 is a schematic structural diagram of a diagnosis system for a vehicle central controller according to the invention. Fig. 2 is a schematic structural diagram of a diagnosis system for a vehicle central controller according to Embodiment II of the disclosure. Fig. 3 is a schematic structural diagram of a diagnosis system for a vehicle central controller according to Embodiment III of the disclosure. Fig. 4A is a schematic flowchart of a diagnosis method for a vehicle central controller according to Embodiment IV of the disclosure. Fig. 4B is a schematic flowchart of another diagnosis method for a vehicle central controller according to Embodiment IV of the disclosure. Detailed Description of the Embodiments
[0023] The disclosure is described in detail below with reference to the accompanying drawings and embodiments.Embodiment I
[0024] Fig. 1 is a schematic structural diagram of a diagnosis system for a vehicle central controller according to Embodiment I of the disclosure. As shown in Fig. 1, the diagnosis system for a vehicle central controller includes the vehicle central controller 11 and at least one diagnosis device 12. Software involved in the disclosure is implemented in the vehicle central controller 11. The vehicle central controller 11 includes a parallel diagnosis component 111 deployed in a main process, and at least one application component 112 deployed in at least one sub-process. The at least one diagnosis device 12 is connected to the parallel diagnosis component 111. The at least one diagnosis device 12 is configured to send, to the parallel diagnosis component 111, a diagnosis request for diagnosing the application component 112, and the diagnosis request carries a diagnosis identifier. The parallel diagnosis component 111 is configured to determine, on the basis of the diagnosis identifier, the application component 112 corresponding to the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device 12, and transmit, in an IPC manner, the diagnosis request to the application component 112 corresponding to the diagnosis request. Each application component 112 is configured to process the received diagnosis request, and transmit a processing result of the diagnosis request to the parallel diagnosis component 111 in an IPC manner. The parallel diagnosis component 111 is further configured to send the processing result to the diagnosis device 12 corresponding to the diagnosis request.
[0025] In this embodiment, the vehicle central controller 11 may be a controller that is integrated by all Electronic Control Unit (ECU) of a vehicle. Exemplarily, a main control chip of the vehicle central controller is a System on Chip (SOC). The ECUs integrating the vehicle central controller 11 include, but are not limited to, an engine controller unit, an automatic transmission controller unit, a vehicle body controller unit, a vehicle body electronic stability controller unit, a battery management controller unit, and a vehicle controller unit.
[0026] The vehicle central controller 11 includes a plurality of ECUs, and each ECU includes at least one application program implementing a corresponding function, such that the vehicle central controller 11 includes a plurality of application programs.
[0027] The application component 112 may be an independent diagnosis component of the application program. The application component 112 may monitor the application program, and record trouble information (for example, communication loss trouble information) of the application program. For each application program included in the vehicle central controller 11, the application component 112 for performing independent diagnosis on the application program is provided. The parallel diagnosis component 111 may be a component that is configured to establish interlinkage between the at least one application component 112 and the at least one diagnosis device 12. Exemplarily, in this embodiment, the parallel diagnosis component 111 is deployed in the main process of the vehicle central controller 11, and the application component 112 of the application program is deployed in the at least one sub-process of the vehicle central controller 11, such that the parallel diagnosis component 111 and the at least one application component 112 may transmit data in an IPC manner.
[0028] Exemplarily, the diagnosis device 12 in this embodiment is connected to the parallel diagnosis component 111. Optionally, the vehicle central controller 11 is deployed with a Controller Area Network (CAN) interface and / or an Ethernet communication interface. The diagnosis device 12 may be connected to the parallel diagnosis component 111 through a CAN bus, or is connected to the parallel diagnosis component 111 through Ethernet. Exemplarily, there is a transmission layer protocol stack of Diagnostic communication over Internet Protocol (DoIP) and Unified Diagnostics Services on CAN (UDS-on-CAN) in the parallel diagnosis component 111, supporting the external diagnosis device 12 to perform Unified Diagnostic Services (UDS) on the plurality of ECUs of the vehicle central controller 11 through different buses.
[0029] Optionally, the vehicle central controller 11 further includes a communication driving component; and the at least one diagnosis device 12 is connected to the parallel diagnosis component 111 through the communication driving component. The communication driving component may be a component that connects the diagnosis device 12 and the parallel diagnosis component 111. In an implementation, the communication driving component may belong to a Board Support Package (BSP) portion.
[0030] In an implementation, the communication driving component includes a CAN bus communication driving component; and the at least one diagnosis device 12 is connected to the parallel diagnosis component 111 through the CAN bus communication driving component. In another implementation, the communication driving component includes an Ethernet communication driving component; and the diagnosis device 12 is connected to the parallel diagnosis component 111 through the Ethernet communication driving component.
[0031] The diagnosis device 12 may initiate, to the parallel diagnosis component 111, the diagnosis request for diagnosing the application component 112. In an implementation, the plurality of diagnosis devices 12 is connected to the parallel diagnosis component 111, and the diagnosis requests for different application components 112 are sent to the parallel diagnosis component 111 at the same time; and the parallel diagnosis component 111 simultaneously establish interlinkage with the plurality of application components according to the plurality of diagnosis requests.
[0032] Exemplarily, the diagnosis device A, the diagnosis device B and the diagnosis device C simultaneously initiate the diagnosis requests for the application component a, the application component b and the application component c to the parallel diagnosis component 111, and in this case, the parallel diagnosis component 111 may respectively establish the interlinkage with the application component a, the application component b and the application component c according to the diagnosis requests.
[0033] In another implementation, the diagnosis request initiated by the diagnosis device 12 may aim at the plurality of application components. If the diagnosis device 12 initiates the diagnosis request for the plurality of application components, the parallel diagnosis component 111 may also simultaneously establish the interlinkage with the plurality of application components according to the diagnosis request.
[0034] In other words, the parallel diagnosis component 111 in this embodiment may synchronously establish, according to the received diagnosis request, the interlinkage with the plurality of application components corresponding to the diagnosis request. That is, the external diagnosis device 12 may establish a diagnosis communication connection with the application component 112 through the parallel diagnosis component 111.
[0035] The diagnosis request initiated by the external diagnosis device 12 needs to follow a certain diagnosis communication protocol requirement, for example, the diagnosis request follows a UDS protocol.
[0036] In this embodiment, the diagnosis request includes the diagnosis identifier. The diagnosis identifier may be identifier information that describes a sending party and a receiving party of the diagnosis request. Exemplarily, after receiving at least one diagnosis request, the parallel diagnosis component 111 may determine, according to the diagnosis identifier carried by each diagnosis request, the application component 112 corresponding to each diagnosis request, establish the interlinkage with the application component 112 in an IPC manner, and send each diagnosis request to the application component 112 corresponding to each diagnosis request.
[0037] After receiving the diagnosis request transmitted by the parallel diagnosis component 111 on the basis of IPC, each application component 112 processes the diagnosis request, and transmits a processing result to the parallel diagnosis component 111 in an IPC manner. The parallel diagnosis component 111 sends the processing result transmitted by each application component 112 to the diagnosis device 12 corresponding to the diagnosis request, that is, to the diagnosis device 12 of the diagnosis request for the application component 112.
[0038] The application component 112 processes the diagnosis request, may read trouble code information (0x19 service), or may also enter diagnosis session control (0x10 service), clear diagnostic information (0x14 service), reset ECU (0x11 service), control the setting of Diagnostic Trouble Codes (DTC) (0x85 service), read data through an Identity (ID) (0x22 service) or write the data through the ID (0x2E service), where ID includes a CAN ID or an Ethernet message ID.
[0039] To sum up, the parallel diagnosis component 111 in this embodiment has the following functions: 1, performing data interaction with the external diagnosis device 12, for example, receiving the diagnosis request sent by the external diagnosis device 12, and sending the processing result of the diagnosis request to the external diagnosis device 12; 2, extracting the diagnosis identifier of the received diagnosis request; and 3, performing data interaction with the application component 112, for example, searching the corresponding application component 112 according to the diagnosis identifier carried by the received diagnosis request, sending the diagnosis request to the application component 112, and receiving the processing result of the diagnosis request sent by the application component 112.
[0040] Definitely, if the external diagnosis device 12 issues the diagnosis request for a plurality of times to the application component 112 within a set time period, when the diagnosis request is issued for the first time, the diagnosis device 12 establishes a communication connection with the application component 112 through the parallel diagnosis component 111, such that the application component 112 may establish a session with the diagnosis device 12, and maintain the session when a communication is established for the first time; and when the diagnosis request is not issued for the first time, the application component 112 may record, on the basis of the session, a process of performing data interaction with the diagnosis device 12.
[0041] The diagnosis system for a vehicle central controller provided in this embodiment includes the vehicle central controller and the at least one diagnosis device. The vehicle central controller includes the parallel diagnosis component deployed in the main process, and the at least one application component deployed in at least one sub-process. The parallel diagnosis component in the main process is configured to establish the interlinkage between each application component on the vehicle central controller and the external diagnosis device; and the application component in the sub-process is configured to diagnose the application program on the sub-process. In the disclosure, the parallel diagnosis component is deployed in the main process; and the independent diagnosis component of each application program is deployed in the sub-process. The parallel diagnosis component is configured to establish a communication between the at least one application component and the at least one external diagnosis device, so as to realize the real-time and synchronous diagnosis of the plurality of application programs on the vehicle central controller, thereby improving the diagnosis efficiency of a controller. In addition, the diagnosis system for a vehicle central controller provided in this embodiment does not need to change the original design of the diagnosis device. After the plurality of ECUs are deployed in the vehicle central controller, the plurality of ECUs may still be independently and synchronously diagnosed according to the original diagnosis device, without depending on the model of a controller chip, such that the diagnosis system has good portability.
[0042] In an implementation, the parallel diagnosis component 111 includes a message processing component 1112 and a routing management component 1113. The message processing component 1112 is connected to the at least one diagnosis device 12. The message processing component 1112 is configured to determine the diagnosis identifier of the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device 12, and send the diagnosis identifier to the routing management component 1113. The routing management component 1113 is configured to determine, on the basis of the diagnosis identifier, the application component 112 corresponding to the diagnosis request, and transmit, in an IPC manner, the diagnosis request to the application component 112 corresponding to the diagnosis request.
[0043] In an implementation, the parallel diagnosis component 111 consists of the message processing component 1112 and the routing management component 1113. The message processing component 1112 is configured to extract the diagnosis identifier of the received diagnosis request. The routing management component 1113 is configured to determine the corresponding application component 112 according to the diagnosis identifier, establish, on the basis of an IPC, communication connection with the application component 112 corresponding to the diagnosis request, and transmit the diagnosis request to the application component 112.
[0044] The advantage of arranging the message processing component 1112 and the routing management component 1113 in the parallel diagnosis component 111, so as to respectively extract the diagnosis identifier and determine the application component corresponding to the diagnosis identifier lies in that, the communication connection may be established with the plurality of application components at the same time when the plurality of diagnosis requests are received, so as to improve the diagnosis efficiency of the plurality of application components.
[0045] Optionally, the application component 112 is further configured to execute at least one of the following operations.
[0046] Security access verification is performed on the received diagnosis request, and a verification result of the diagnosis request is transmitted to the parallel diagnosis component 111 in an IPC manner.
[0047] A DTC of the application program running in each application component 112 is recorded, and a diagnostic trouble state of the application program running in each application component 112 is maintained.
[0048] A session state between the application component 112 and the parallel diagnosis component 111 is recorded.
[0049] In an optional implementation, the application component 112 may not only perform diagnosis service request processing, but also perform security access verification, session state management, DTC recording, and diagnostic trouble state maintenance. Due to the constantly changing of the trouble state, including the current trouble and a historical trouble, maintaining the diagnostic trouble state can update the trouble state in real time.
[0050] In an implementation, the application component 112 includes a diagnosis processing component and a diagnosis storage component. The diagnosis processing component is configured to execute at least one of the following operations: recording a session state between the application component 112 and the parallel diagnosis component 111; performing security access verification on the received diagnosis request, and transmitting the verification result of the diagnosis request to the parallel diagnosis component 111 in an IPC manner; and processing the received diagnosis request, and transmitting the processing result of the diagnosis request to the parallel diagnosis component 111 in an IPC manner. The diagnosis storage component is configured to record the DTC of the application program running in the application component 112, and maintain the diagnostic trouble state of the application program running in the application component 112. Optionally, the diagnosis processing component is further configured to provide a diagnosis service interface to the application program deployed in the application component. The diagnosis storage component is further configured to provide a diagnosis storage interface to the application program deployed in the application component.
[0051] It is to be noted that, in an optional implementation, the diagnosis processing component and the diagnosis storage component of the at least one application component may be implemented by using the same code, but each application component needs to be integrated with the diagnosis processing component and the diagnosis storage component. Diagnosis data (for example, the DTC) of each application component 112 in the entire vehicle central controller 11 may be separately stored. That is to say, diagnostic information of each application component 112 may be respectively stored to a data storage space corresponding to each application component. However, the parallel diagnosis component 111 of the main process may acquire the diagnosis data of each application component 112 through a mechanism of IPC.
[0052] In an optional implementation, the application component 112 may also perform session state management, security access verification, DTC recording, and diagnostic trouble state maintenance. Therefore, trouble diagnosis of the plurality of application programs of the vehicle central controller is realized.Embodiment II
[0053] Fig. 2 is a schematic structural diagram of a diagnosis system for a vehicle central controller according to Embodiment II of the disclosure. In this embodiment, on the basis of each embodiment, optionally, the vehicle central controller further includes a communication driving component; and the at least one diagnosis device is connected to the parallel diagnosis component through the communication driving component. Optionally, the communication driving component includes a CAN bus communication driving component; and the at least one diagnosis device is connected to the parallel diagnosis component through the CAN bus communication driving component. Optionally, the diagnosis identifier includes a request message identifier. The parallel diagnosis component includes a CAN bus transmission analysis component. The CAN bus transmission analysis component is configured to analyze the diagnosis request, to acquire the request message identifier of the diagnosis request. The parallel diagnosis component is configured to call the CAN bus transmission analysis component to analyze the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device on the basis of the CAN bus communication driving component, so as to obtain the request message identifier of the diagnosis request, determine, on the basis of the request message identifier, the application component corresponding to the diagnosis request, and transmit, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request.
[0054] Exemplarily, as shown in Fig. 2, the diagnosis system for a vehicle central controller provided in this embodiment includes a vehicle central controller 11 and at least one diagnosis device 12. The vehicle central controller 11 includes a parallel diagnosis component 111 deployed in a main process, at least one application component 112 deployed in at least one sub-process, and a communication driving component 213. The communication driving component 213 includes a CAN bus communication driving component 2131. The parallel diagnosis component 111 includes the CAN bus transmission analysis component 2111. The diagnosis device 12 is connected to the parallel diagnosis component 111 through the CAN bus communication driving component 2131. The diagnosis device 12 is configured to send, to the parallel diagnosis component 111, a diagnosis request for diagnosing the application component 112, wherein the diagnosis request carries a diagnosis identifier, and the diagnosis identifier includes the request message identifier. The parallel diagnosis component 111 is configured to call the CAN bus transmission analysis component 2111 to analyze the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device 12 on the basis of the CAN bus communication driving component 2131, so as to obtain the request message identifier of the diagnosis request, determine, on the basis of the request message identifier, the application component 112 corresponding to the diagnosis request, and transmit, in an IPC manner, the diagnosis request to the application component 112 corresponding to the diagnosis request. Each application component 112 is configured to process the received diagnosis request, and transmit a processing result of the diagnosis request to the parallel diagnosis component 111 in an IPC manner. The parallel diagnosis component 111 is further configured to send the processing result to the diagnosis device 12 corresponding to the diagnosis request.
[0055] The request message identifier may be a Controller Area Network Identity Document (CANID). Exemplarily, if the diagnosis device 12 sends the diagnosis request through the CAN bus communication driving component 2131, and the diagnosis identifier of the diagnosis request sent by the diagnosis device 12 is the CANID.
[0056] Exemplarily, the parallel diagnosis component 111 in this embodiment may analyze the diagnosis request by calling the CAN bus transmission analysis component 2111, to acquire the request message identifier of the diagnosis request.
[0057] According to the technical solution of this embodiment, the diagnosis request sent by the external diagnosis device is received through the CAN bus communication driving component of the communication driving component; the diagnosis request is analyzed by the CAN bus transmission analysis component of the parallel diagnosis component, a diagnosis message data packet portion of the diagnosis request is acquired, and the request message identifier is extracted from the diagnosis message data packet portion, so as to determine the corresponding application component on the basis of the request message identifier; and interlinkage with the application component is established. In this way, the real-time diagnosis of the plurality of application programs on the vehicle central controller at the same time is realized, a communication mechanism of a diagnosis device in the related art does not need to be changed, and a plurality of ECUs may still be independently and synchronously diagnosed according to the diagnosis device in the related art, such that the applicability of the diagnosis system for a vehicle central controller is improved.Embodiment III
[0058] Fig. 3 is a schematic structural diagram of a diagnosis system for a vehicle central controller according to Embodiment III of the disclosure. In this embodiment, on the basis of each embodiment, optionally, the vehicle central controller further includes a communication driving component; and the diagnosis device is connected to the parallel diagnosis component through the communication driving component. Optionally, the communication driving component includes an Ethernet communication driving component; and the at least one diagnosis device is connected to the parallel diagnosis component through the Ethernet communication driving component. Optionally, the diagnosis identifier includes a diagnosis node identifier. The parallel diagnosis component includes an Ethernet transmission analysis component. The Ethernet transmission analysis component is configured to analyze a diagnosis request, and acquire the diagnosis node identifier of the diagnosis request. The parallel diagnosis component is configured to call the Ethernet transmission analysis component to analyze the diagnosis request, in response to is receiving the diagnosis request sent by the at least one diagnosis device on the basis of the Ethernet communication driving component, so as to obtain the diagnosis node identifier of the diagnosis request, determine, on the basis of the diagnosis node identifier, the application component corresponding to the diagnosis request, and transmit, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request.
[0059] Exemplarily, as shown in Fig. 3, the diagnosis system for a vehicle central controller provided in this embodiment includes a vehicle central controller 11 and at least one diagnosis device 12. The vehicle central controller 11 includes a parallel diagnosis component 111 deployed in a main process, at least one application component 112 deployed in at least one sub-process, and a communication driving component 213. The communication driving component 213 includes the Ethernet communication driving component 3132. The parallel diagnosis component includes the Ethernet transmission analysis component 3112. The diagnosis device 12 is connected to the parallel diagnosis component 111 through the Ethernet communication driving component 3132. The diagnosis device 12 is configured to send, to the parallel diagnosis component 111, the diagnosis request for diagnosing the application component 112, wherein the diagnosis request carries a diagnosis identifier, and the diagnosis identifier includes the diagnosis node identifier. The parallel diagnosis component 111 is configured to call the Ethernet transmission analysis component 3112 to analyze the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device 12 on the basis of the Ethernet communication driving component 3132, so as to obtain the diagnosis node identifier of the diagnosis request, determine, on the basis of the diagnosis node identifier, the application component 112 corresponding to the diagnosis request, and transmit, in an IPC manner, the diagnosis request to the application component 112 corresponding to the diagnosis request. The application component 112 is configured to process the received diagnosis request, and transmit a processing result of the diagnosis request to the parallel diagnosis component 111 in an IPC manner. The parallel diagnosis component 111 is further configured to send the processing result to the diagnosis device 12 corresponding to the diagnosis request.
[0060] The diagnosis node identifier may be an Internet Protocol (IP) address or a port number (IP / PORT). Exemplarily, if the diagnosis device 12 sends the diagnosis request through the Ethernet communication driving component, and the diagnosis identifier of the diagnosis request sent by the diagnosis device 12 is the diagnosis node identifier.
[0061] Exemplarily, the parallel diagnosis component 111 in this embodiment may analyze the diagnosis request by calling the Ethernet transmission analysis component 3112, and acquire the diagnosis node identifier of the diagnosis request.
[0062] According to the technical solution of this embodiment, the diagnosis request sent by the external diagnosis device is received through the Ethernet communication driving component of the communication driving component; the diagnosis request is analyzed by the Ethernet transmission analysis component of the parallel diagnosis component, a diagnosis message data packet portion of the diagnosis request is acquired, and the diagnosis node identifier is extracted from the diagnosis message data packet portion, so as to determine the corresponding application component on the basis of the diagnosis node identifier; and interlinkage with the application component is established. In this way, the real-time diagnosis of the plurality of application programs on the vehicle central controller at the same time is realized, a communication mechanism of a diagnosis device in the related art does not need to be changed, and a plurality of ECUs may still be independently and synchronously diagnosed according to the diagnosis device in the related art, such that the applicability of the diagnosis system for a vehicle central controller is improved.
[0063] Definitely, the communication driving component provided in this embodiment may further include the Ethernet communication driving component and a CAN bus communication driving component; and the parallel diagnosis component also includes the Ethernet transmission analysis component and a CAN bus transmission analysis component.
[0064] In an implementation, a diagnosis message determination component may further be deployed in the communication driving component. On the basis of the diagnosis message determination component, before the parallel diagnosis component acquires the diagnosis identifier of the diagnosis request, the diagnosis message determination component determines whether the diagnosis request is a request of a diagnosis message type. That is, optionally, the communication driving component includes the diagnosis message determination component. The diagnosis message determination component is configured to determine whether the diagnosis request of the application component sent by the at least one diagnosis device is the request of the diagnosis message type, and transmit the diagnosis request to the parallel diagnosis component when the diagnosis request of the application component sent by the at least one diagnosis device is the request of the diagnosis message type.
[0065] The diagnosis message type may be a preset message type. In an implementation, the diagnosis message type may be set through a preset diagnosis identifier.
[0066] Exemplarily, whether the diagnosis request is the request of the diagnosis message type may be determined on the basis of the diagnosis identifier of the diagnosis request. For example, if the diagnosis identifier carried by the diagnosis request is 101, 301 or 401, the diagnosis request is the request of the diagnosis message type.
[0067] Exemplarily, the communication driving component may call the CAN bus communication driving component or the Ethernet communication driving component, acquire the diagnosis identifier of the diagnosis request, and determine, on the basis of the diagnosis message determination component, whether the diagnosis request is the request of the diagnosis message type. If the diagnosis request is the request of the diagnosis message type, the diagnosis request is transmitted to the parallel diagnosis component through the communication driving component, so as to cause the parallel diagnosis component to establish interlinkage with the application component corresponding to the diagnosis request, thereby diagnosing the application component.
[0068] Optionally, if the diagnosis request is not the request of the diagnosis message type, the diagnosis request is processed on the basis of a non-diagnosis message processing component in the vehicle central controller.
[0069] In an optional implementation, whether the diagnosis request is the request of a preset diagnosis message type is determined through the diagnosis message determination component of the communication driving component; and when the diagnosis request is the request of the preset diagnosis message type, the diagnosis request is transmitted to the parallel diagnosis component. Therefore, the filtration of a diagnosis message is realized, a non-preset diagnosis request is prevented from being processed, and the safety of the diagnosis system for a vehicle central controller is improved.
[0070] It is to be noted that, components included in the system are only divided according to the functional logic, but are not limited to the above divisions, as long as the corresponding functions can be realized. In addition, the specific names of the functional components are only for the convenience of distinguishing from each other, and are not used to limit the scope of protection of the embodiments of the disclosure.Embodiment IV
[0071] Fig. 4A is a schematic flowchart of a diagnosis method for a vehicle central controller according to Embodiment IV of the disclosure. This embodiment may be suitable for a situation of diagnosing a plurality of application programs in a vehicle central controller, for example, suitable for a situation of diagnosing the plurality of application programs in the vehicle central controller at the same time. The method is suitable for a diagnosis system for a vehicle central controller. The system may be implemented by hardware and / or software. The method includes the following steps.
[0072] At S410, a diagnosis request for diagnosing the application component sent by at least one diagnosis device is received on the basis of a parallel diagnosis component deployed in a main process of a vehicle central controller, wherein the diagnosis request carries a diagnosis identifier.
[0073] Optionally, the step of receiving, on the basis of a parallel diagnosis component deployed in a main process of a vehicle central controller, a diagnosis request for diagnosing the application component sent by at least one diagnosis device includes: receiving, by the parallel diagnosis component deployed in the main process of the vehicle central controller through a communication driving component of the vehicle central controller, the diagnosis request for diagnosing the application component that is sent by the at least one diagnosis device. Exemplarily, the vehicle central controller further includes the communication driving component; and the diagnosis device is connected to the parallel diagnosis component through the communication driving component.
[0074] Optionally, the communication driving component includes a CAN bus communication driving component. Correspondingly, the parallel diagnosis component deployed in the main process of the vehicle central controller receives, through the CAN bus communication driving component, the diagnosis request for diagnosing the application component sent by at least one diagnosis device. Exemplarily, the diagnosis device is connected to the parallel diagnosis component through the CAN bus communication driving component.
[0075] Optionally, the communication driving component includes an Ethernet communication driving component. Correspondingly, the parallel diagnosis component deployed in the main process of the vehicle central controller receives, through the Ethernet communication driving component, the diagnosis request for diagnosing the application component sent by at least one diagnosis device. Exemplarily, the diagnosis device is connected to the parallel diagnosis component through the Ethernet communication driving component.
[0076] At S420, the parallel diagnosis component determines the application component corresponding to the diagnosis request on the basis of the diagnosis identifier, and transmits, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request.
[0077] Optionally, the step of determining, by the parallel diagnosis component, the application component corresponding to the diagnosis request on the basis of the diagnosis identifier, and transmitting, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request includes: receiving, by a message processing component of the parallel diagnosis component, the diagnosis request sent by the at least one diagnosis device, determining a diagnosis identifier of the diagnosis request, and sending the diagnosis identifier to a routing management component of the parallel diagnosis component; and through the routing management component; of the parallel diagnosis component, determining, on the basis of the diagnosis identifier, the application component corresponding to the diagnosis request, and transmitting, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request.
[0078] Optionally, the diagnosis identifier includes a request message identifier. The parallel diagnosis component includes a CAN bus transmission analysis component. The step of determining, by the parallel diagnosis component, the application component corresponding to the diagnosis request on the basis of the diagnosis identifier, and transmitting, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request includes the following operation.
[0079] The parallel diagnosis component calls the CAN bus transmission analysis component to analyze the diagnosis request , in response to receiving the diagnosis request sent by the at least one diagnosis device on the basis of the CAN bus communication driving component, so as to obtain the request message identifier of the diagnosis request, determines, on the basis of the request message identifier, the application component corresponding to the diagnosis request, and transmits, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request.
[0080] Optionally, the diagnosis identifier includes a diagnosis node identifier. The parallel diagnosis component includes an Ethernet transmission analysis component. The step of determining, by the parallel diagnosis component, the application component corresponding to the diagnosis request on the basis of the diagnosis identifier, and transmitting, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request includes the following operation.
[0081] The parallel diagnosis component calls the Ethernet transmission analysis component to analyze the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device on the basis of the Ethernet communication driving component, so as to obtain the diagnosis node identifier of the diagnosis request, determine, on the basis of the diagnosis node identifier, the application component corresponding to the diagnosis request, and transmit, in an IPC manner, the diagnosis request to the application component corresponding to the diagnosis request.
[0082] At S430, the parallel diagnosis component acquires a processing result of the diagnosis request from the application component in an IPC manner, wherein the processing result of the diagnosis request is obtained by processing the received diagnosis request through the application component.
[0083] Optionally, the method further includes at least one of the followings.
[0084] The parallel diagnosis component acquires a verification result of the diagnosis request from the application component in an IPC manner, and the verification result of the diagnosis request is obtained by performing security access verification on the received diagnosis request by the application component.
[0085] A DTC of the application program running in the application component is recorded on the basis of the application component, and a diagnostic trouble state of the application program running in the application component is maintained.
[0086] A session state between the application component and the parallel diagnosis component is recorded on the basis of the application component.
[0087] At S440, the parallel diagnosis component sends the processing result to the diagnosis device corresponding to the diagnosis request.
[0088] Optionally, the parallel diagnosis component may send the processing result to the diagnosis device corresponding to the diagnosis request on the basis of the communication driving component. Optionally, the parallel diagnosis component may send the processing result to the diagnosis device corresponding to the diagnosis request on the basis of the CAN bus communication driving component of the communication driving component. Optionally, the parallel diagnosis component may send the processing result to the diagnosis device corresponding to the diagnosis request on the basis of the Ethernet communication driving component of the communication driving component.
[0089] Optionally, the method further includes: determining whether the diagnosis request of the application component sent by the at least one diagnosis device is a request of a diagnosis message type, and transmitting the diagnosis request to the parallel diagnosis component when the diagnosis request of the application component sent by the at least one diagnosis device is the request of the diagnosis message type.
[0090] According to the technical solution of this embodiment, by performing data interaction between the parallel diagnosis component established in the main process and the external diagnosis device and the application component in the at least one sub-process, the real-time diagnosis of the plurality of application programs on the vehicle central controller at the same time is realized, such that the diagnosis efficiency of the controller is improved. In addition, the original design of the diagnosis device does not need to be changed. After the plurality of ECUs are deployed in the vehicle central controller, the plurality of ECUs may still be independently and synchronously diagnosed according to the original diagnosis device, without depending on the model of a controller chip, such that the diagnosis system has good portability.
[0091] It is to be noted that, this embodiment further provides another diagnosis method for a vehicle central controller, as shown in Fig. 4B. Referring to Fig. 4B, the method includes the following steps.
[0092] At S1, the main process is started.
[0093] At S2, the diagnosis request is received, and a message communication ID ETH PORT or CANID is acquired.
[0094] At S3, whether the diagnosis request is the request of the diagnosis message type is determined; when the diagnosis request is not the request of the diagnosis message type, S4 is executed; and when the diagnosis request is the request of the diagnosis message type, S5 is executed.
[0095] At S4, the non-diagnosis message processing component processes the diagnosis request.
[0096] At S5, the diagnosis request is analyzed through a UDS-On-Can / DolP transmission layer.
[0097] At S6, the ID ETH PORT or CANID of the diagnosis request is extracted, and the application component corresponding to the diagnosis request is matched.
[0098] At S7, whether to establish interlinkage with the application component is determined; if so, S10 is executed; and if no, S8 is executed.
[0099] At S8, an IPC communication connection is established with the sub-process of the application component.
[0100] At S9, diagnosis session interlinkage and security access verification are established.
[0101] At S10, the diagnosis request is processed (for example, 0X22, 0X2E, 0X31, ect.)
[0102] At S11, diagnosis service are implemented and data storage are performed.
[0103] In this implementation, by performing data interaction between the main process and the external diagnosis device and the application component in the at least one sub-process, the real-time diagnosis of the plurality of application programs on the vehicle central controller at the same time is realized, such that the diagnosis efficiency of the controller is improved.
Claims
1. A diagnosis system for a vehicle central controller comprising the vehicle central controller (11) and at least one diagnosis device (12), wherein the vehicle central controller (11) comprises a parallel diagnosis component (111) deployed in a main process, and at least one application component (112) deployed in at least one sub-process; the at least one diagnosis device (12) is connected with the parallel diagnosis component (111), and the at least one diagnosis device (12) is configured to send, to the parallel diagnosis component (111), a diagnosis request for diagnosing the application component (112), wherein the diagnosis request carries a diagnosis identifier; the parallel diagnosis component (111) is configured to determine, on the basis of the diagnosis identifier, the application component (112) corresponding to the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device (12), and transmit, in an Inter-Process Communication, IPC, manner, the diagnosis request to the application component (112) corresponding to the diagnosis request; each application component (112) is configured to process the received diagnosis request, and transmit a processing result of the diagnosis request to the parallel diagnosis component (111) in the IPC manner; and the parallel diagnosis component (111) is further configured to send the processing result to the diagnosis device (12) corresponding to the diagnosis request, wherein the parallel diagnosis component (111) comprises a message processing component (1112) and a routing management component(1113); the message processing component (1112) is connected with the at least one diagnosis device (12); the message processing component (1112) is configured to determine the diagnosis identifier of the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device, and send the diagnosis identifier to the routing management component (1113); and the routing management component (1113) is configured to determine, on the basis of the diagnosis identifier, the application component (112) corresponding to the diagnosis request, and transmit, in the IPC manner, the diagnosis request to the application component (112) corresponding to the diagnosis request.
2. The system as claimed in claim 1, wherein the vehicle central controller (11) further comprises a communication driving component (213), and the at least one diagnosis device (12) is connected with the parallel diagnosis component (111) through the communication driving component (213).
3. The system as claimed in claim 2, wherein the communication driving component (213) comprises a Controller Area Network (CAN) bus communication driving component(2131), and the at least one diagnosis device (12) is connected with the parallel diagnosis component (111) through the CAN bus communication driving component (2131).
4. The system as claimed in claim 3, wherein the diagnosis identifier comprises a request message identifier, and the parallel diagnosis component (111) comprises a CAN bus transmission analysis component (2111); the CAN bus transmission analysis component (2111) is configured to analyze the diagnosis request, to acquire the request message identifier of the diagnosis request; and the parallel diagnosis component (111) is configured to call the CAN bus transmission analysis component (2111) to analyze the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device (12) on the basis of the CAN bus communication driving component (2131), to obtain the request message identifier of the diagnosis request, and determine, on the basis of the request message identifier, the application component (112) corresponding to the diagnosis request, and transmit, in the IPC manner, the diagnosis request to the application component (112) corresponding to the diagnosis request.
5. The system as claimed in claim 2, wherein the communication driving component (213) comprises an Ethernet communication driving component (3132); and the at least one diagnosis device (12) is connected with the parallel diagnosis component (111) through the Ethernet communication driving component (3132).
6. The system as claimed in claim 5, wherein the diagnosis identifier comprises a diagnosis node identifier, and the parallel diagnosis component (111) comprises an Ethernet transmission analysis component (3112); the Ethernet transmission analysis component (3112) is configured to analyze the diagnosis request, to acquire the diagnosis node identifier of the diagnosis request; and the parallel diagnosis component (111) is configured to call the Ethernet transmission analysis component (3112) to analyze the diagnosis request ,in response to receiving the diagnosis request sent by the at least one diagnosis device (12) on the basis of the Ethernet communication driving component (3132), so as to obtain the diagnosis node identifier of the diagnosis request, determine, on the basis of the diagnosis node identifier, the application component (112) corresponding to the diagnosis request, and transmit, in an IPC manner, the diagnosis request to the application component (112) corresponding to the diagnosis request.
7. The system as claimed in claim 1, wherein each application component (112) is further configured to execute at least one of the following steps: performing security access verification on the received diagnosis request, and transmitting a verification result of the diagnosis request to the parallel diagnosis component (111) in the IPC manner; recording a Diagnostic Trouble Code (DTC) of the application program running in each application component (112), and maintaining a diagnostic trouble state of the application program running in each application component (112); and recording a session state between each application component (112) and the parallel diagnosis component (111).
8. The system as claimed in claim 2, wherein the communication driving component (213) comprises a diagnosis message determination component; and the diagnosis message determination component is configured to determine whether the diagnosis request of the application component (112) sent by the at least one diagnosis device (12) is a request of a diagnosis message type, and transmit the diagnosis request to the parallel diagnosis component (111), in response to the diagnosis request of the application component (112) sent by the at least one diagnosis device (12) being the request of the diagnosis message type.
9. A diagnosis method for a vehicle central controller, comprising: receiving, on the basis of a parallel diagnosis component (111) deployed in a main process of the vehicle central controller (11), a diagnosis request for diagnosing an application component (112) sent by at least one diagnosis device (12), wherein the diagnosis request carries a diagnosis identifier; determining, by the parallel diagnosis component (111), the application component (112) corresponding to the diagnosis request on the basis of the diagnosis identifier, and transmitting, in an Inter-Process Communication, IPC, manner, the diagnosis request to the application component (112) corresponding to the diagnosis request; acquiring a processing result of the diagnosis request by the parallel diagnosis component (111) from the application component (112) in an IPC manner, wherein the processing result of the diagnosis request is obtained by processing the received diagnosis request through the application component (112); and sending, by the parallel diagnosis component (111), the processing result to the diagnosis device (12) corresponding to the diagnosis request; wherein the parallel diagnosis component (111) comprises a message processing component (1112) and a routing management component (1113); the message processing component (1112) is connected with the at least one diagnosis device (12); the message processing component (1112) is configured to determine the diagnosis identifier of the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device, and send the diagnosis identifier to the routing management component (1113); and the routing management component (1113) is configured to determine, on the basis of the diagnosis identifier, the application component (112) corresponding to the diagnosis request, and transmit, in the IPC manner, the diagnosis request to the application component (112) corresponding to the diagnosis request.
10. The method as claimed in claim 9, wherein the vehicle central controller (11) further comprises a communication driving component (213), and the at least one diagnosis device (12) is connected with the parallel diagnosis component (111) through the communication driving component (213).
11. The method as claimed in claim 10, wherein the communication driving component (213) comprises a Controller Area Network (CAN) bus communication driving component (2131), and the at least one diagnosis device (12) is connected with the parallel diagnosis component (111) through the CAN bus communication driving component (2131).
12. The method as claimed in claim 11, wherein the diagnosis identifier comprises a request message identifier, and the parallel diagnosis component (111) comprises a CAN bus transmission analysis component (2111); analyzing, by the CAN bus transmission analysis component (2111), the diagnosis request, to acquire the request message identifier of the diagnosis request; calling, by the parallel diagnosis component (111), the CAN bus transmission analysis component (2111) to analyze the diagnosis request, in response to receiving the diagnosis request sent by the at least one diagnosis device (12) on the basis of the CAN bus communication driving component(2131); determining, on the basis of the request message identifier, the application component (112) corresponding to the diagnosis request; and transmitting, in an IPC manner, the diagnosis request to the application component (112) corresponding to the diagnosis request.
13. The method as claimed in claim 10, wherein the communication driving component (213) comprises an Ethernet communication driving component (3132); and the at least one diagnosis device (12) is connected with the parallel diagnosis component (111) through the Ethernet communication driving component (3132).