Electrical architecture for service-oriented vehicle diagnostics
Through the service-oriented diagnostic electrical architecture, the problems of static configuration and security risks in the existing vehicle diagnostic architecture are solved, dynamic diagnostic service updates and multi-tester access are realized, and the scalability and security of the diagnostic architecture are improved.
Patent Information
- Application Number
- CN202080061635.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-09-02
- Filing Date
- 2020-08-27
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2040-08-27
AI Technical Summary
The existing vehicle diagnostic architecture has static configuration, lack of diagnostic redundancy, limited to component-based diagnostics, limited to diagnostic access to one tester at a time, and security risks between the external tester and the vehicle module.
Adopting a service-oriented diagnostic electrical architecture, by deploying diagnostic server modules, service interface modules and diagnostic service registration modules in vehicles, it allows diagnostic communication between the electronic control unit and the network service bus, and provides unified diagnostic service agreement communication and service-oriented communication. The conversion between diagnostic communications supports dynamic service registration and subscription of non-vehicle modules, and uses the Ethernet backbone network to transmit diagnostic service notifications.
Realize dynamic diagnostic service updates, improve the scalability and flexibility of the diagnostic architecture, provide logical and physical separation, enhance security, allows multiple diagnostic testers to access and dynamically discover diagnostic services simultaneously, reducing external configuration complexity sex.
Smart Images

Figure CN114341758B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a diagnostic electrical architecture for a vehicle, and in particular, to a diagnostic electrical architecture hosted on a plurality of vehicle onboard computing devices. Aspects of the present invention relate to a vehicle diagnostic electrical architecture, a method, a computer readable medium, and a vehicle. Background Art
[0002] Modern vehicles - for example, road vehicles such as automobiles - include multiple embedded electronic control units, components or modules (ECUs) for controlling and executing multiple functions of the vehicle. Examples of such ECUs may include anti-lock braking systems (ABS), powertrain control modules (PCMs), transmission control modules (TCMs), instrument panel clusters (IPCs), ADAS domain controllers (ADCs), engine management systems (EMSs), air conditioning modules (ACMs), etc. Typically, each vehicle ECU is connected to multiple sensors of the vehicle and receives sensor data from the sensors along with signals from other components of the vehicle as input.
[0003] Electronic components or software of the ECU, or sensors connected to the ECU may fail or malfunction. Many ECUs will include a local diagnostic server with self-diagnostic capabilities, including the ability to identify and report faults, and possibly perform self-repair of the faults.
[0004] Currently, diagnostic testing of vehicles involves a diagnostic tester - which may be on-board or off-board - establishing a point-to-point (p2p) diagnostic communication between the diagnostic tester and a local diagnostic server of any ECU of the vehicle. In particular, such diagnostic communication is carried out via a single central gateway, which acts as a router of diagnostic messages to a specific local diagnostic server, in particular for routing diagnostic messages between different transport protocols.
[0005] There are many potential disadvantages or drawbacks associated with the above-described prior art vehicle diagnostic architectures. These disadvantages or drawbacks include, but are not limited to: static diagnostic configuration, lack of diagnostic redundancy, limitation to component-based diagnostics, diagnostic access limited to one tester at a time, and no logical and physical separation between external testers and vehicle modules resulting in safety risks. It is an object of the present invention to address one or more of the disadvantages associated with the prior art. Summary of the invention
[0006] According to one aspect of the present invention, a diagnostic electrical architecture for a vehicle is provided, the vehicle being, for example, a car or other road-going vehicle. The vehicle includes a plurality of onboard computing devices for hosting the diagnostic electrical architecture. The diagnostic electrical architecture includes one or more electronic control units, each of which includes a diagnostic server module, the diagnostic server module being arranged to perform diagnostic tasks to generate diagnostic object data. The architecture includes a service interface module, the service interface module being arranged to allow diagnostic communication between the one or more electronic control units and a network service bus of the vehicle, the service interface module being arranged to receive the generated diagnostic object data. The architecture includes a diagnostic service registration module, the diagnostic service registration module being arranged to store diagnostic service data indicating diagnostic services provided by the service interface module, the diagnostic service data including a diagnostic capability description of the generated diagnostic object data. The service interface module is arranged to transmit diagnostic service notifications via the network service bus, wherein the diagnostic service notifications are based on the generated diagnostic object data and the diagnostic service data retrieved from the diagnostic service registration table.
[0007] The diagnostic service notification may be generated in response to a change in the diagnostic capabilities provided by the service interface module.
[0008] Changes in diagnostic capabilities may result from the addition or removal of diagnostic tasks performed by the one or more control units.
[0009] Changes in diagnostic capabilities may be caused by the addition or removal of electronic control units associated with the service interface module.
[0010] The diagnostic service notification may be generated in response to a request for diagnostic capabilities received by the service interface module.
[0011] The request for diagnostic capabilities may be received from an off-board diagnostic tester.
[0012] The generated service notification may be transmitted outside the vehicle.
[0013] The generated diagnostic capability notification may be used to update the diagnostic registration module.
[0014] The service interface module may be deployed on a communication middleware on one or more of the onboard computing devices.
[0015] The communication middleware may be one of: SOME / IP (Scalable Service-Oriented Middleware over IP); REST (Representational State Transfer); and DDS (Data Distribution Service).
[0016] The vehicle service bus may include an Ethernet backbone network.
[0017] The service interface module can be connected directly to the Ethernet backbone network.
[0018] The stored diagnostic service data may include an Open Diagnostic Exchange (ODX) file for interpreting diagnostic object data.
[0019] The diagnostic service registration module may be arranged to allow on-board modules and off-board modules to subscribe to the diagnostic service registration module, so that the on-board modules and off-board modules dynamically learn the diagnostic services provided by the service interface module.
[0020] The diagnostic electrical architecture may be arranged to provide translation between unified diagnostic services (UDS) protocol communications and service-oriented diagnostic communications.
[0021] The diagnostic electrical architecture may be a hierarchical architecture having a component diagnostic layer and at least one supervisory diagnostic layer, the component diagnostic layer including the one or more electronic units.
[0022] The at least one supervisory diagnostic layer may include a service interface module.
[0023] The at least one supervisory diagnostic layer may include a diagnostic service registration module.
[0024] The at least one supervisory diagnostic layer may include a system diagnostic layer and a vehicle diagnostic layer, the vehicle diagnostic layer being at a higher level of the architecture than the system diagnostic layer. The vehicle diagnostic layer may include a service interface module, and the system diagnostic layer may include an application service module, the application service module including a local diagnostic agent, the local diagnostic agent being arranged to aggregate the generated diagnostic service notifications received from the electronic control unit to generate a supervisory level diagnostic service notification.
[0025] Supervisor-level diagnostic service notifications can be used to update the diagnostic service registration module.
[0026] The service interface module may be hosted on a local input / output computing device of the vehicle or on a central computing platform of the vehicle.
[0027] According to another aspect of the present invention, a vehicle, such as an automobile or other road-going vehicle, is provided, the vehicle comprising a network architecture having a plurality of computing devices and hosting the above-mentioned diagnostic electrical architecture.
[0028] According to another aspect of the present invention, a method for providing diagnostic communications in a diagnostic electrical architecture of a vehicle is provided, the vehicle being, for example, an automobile or other road-going vehicle. The vehicle includes a plurality of onboard computing devices for hosting the diagnostic electrical architecture. The diagnostic electrical architecture includes: one or more electronic control units, each electronic control unit including a diagnostic server module; a service interface module, the service interface module being arranged to allow diagnostic communications between the one or more electronic control units and a network service bus of the vehicle; and a diagnostic service registration module. The method includes performing a diagnostic task by the diagnostic server module to generate diagnostic object data, and receiving the generated diagnostic object data into the service interface module. The method includes retrieving diagnostic service data from the diagnostic service registration module, the diagnostic service data including a diagnostic capability description of the generated diagnostic object data. The method includes transmitting a diagnostic service notification via a network service bus, the diagnostic service notification being based on the generated diagnostic object data and the diagnostic service data.
[0029] According to another aspect of the present invention, a non-transitory computer-readable storage medium is provided, on which instructions are stored, and when the instructions are executed by one or more processors, the one or more processors execute the above method.
[0030] It is expressly intended that within the scope of the present application, the various aspects, embodiments, examples and alternatives set forth in the preceding paragraphs, in the claims and / or in the following description and drawings, and in particular individual features thereof, may be taken independently or in any combination. That is, all embodiments and / or features of any embodiment may be combined in any manner and / or combination, unless such features are incompatible. Applicants reserve the right to change any originally filed claim or to file any new claim accordingly, including the right to amend any originally filed claim to be subordinate to any other claim and / or to incorporate any features of any other claim, even though protection was not originally claimed in that manner. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] One or more embodiments of the present invention will now be described, by way of example only, with reference to the accompanying drawings, in which:
[0032] Figure 1 A vehicle diagnostic electrical architecture having a flat, non-hierarchical structure utilizing signal-oriented diagnostic communications is shown;
[0033] Figure 2 A vehicle diagnostic electrical architecture according to another example of the present invention is shown, the vehicle diagnostic electrical architecture having a hierarchical structure utilizing service-oriented diagnostic communication;
[0034] Figure 3Shows Figure 2 Application service module for diagnostic electrical architecture;
[0035] Figure 4 A vehicle network architecture is shown, the vehicle network architecture includes multiple computing devices, the vehicle network architecture indicates Figure 2 The locations where the various layers of the diagnostic electrical architecture are hosted;
[0036] Figure 5 Shown is a vehicle direction indicator feature Figure 2 The vehicle diagnostic electrical architecture;
[0037] Figure 6 Shows the use of Figure 2 The vehicle diagnostic electrical architecture performs the steps of the method of vehicle diagnostic communication;
[0038] Figure 7 A vehicle according to an example of an aspect of the present invention is shown, the vehicle comprising a hosting Figure 2 Diagnosis of electrical architecture Figure 4 network architecture; and
[0039] Figure 8 A simplified example of an onboard computing device is shown. DETAILED DESCRIPTION
[0040] Figure 1 A point-to-point (p2p) diagnostic electrical architecture 10 of a vehicle is shown. The vehicle diagnostic architecture 10 has multiple electronic control units, components or modules (ECUs) 101, which are logically arranged in a flat non-hierarchical structure 10 or a component-level diagnostic architecture 10. The ECUs 101 each perform a separate function and may include an anti-lock braking system module (ABS), a powertrain control module (PCM), a transmission control module (TCM), an instrument panel cluster (IPC), an ADAS domain controller (ADC), an engine management system (EMS) and / or an air conditioning module (ACM). It should be understood that the vehicle diagnostic architecture 10 may include any number of suitable ECUs. Typically, a vehicle may include 40 to 60 ECUs.
[0041] Each ECU 101 in the diagnostic architecture 10 can communicate with an on-board or off-board diagnostic tester 11. In fact, the diagnostic tester 11 is able to directly establish a diagnostic communication path with any on-board ECU 101. Therefore, the diagnostic tester 11 is able to initiate diagnostic communications and perform various diagnostic tasks such as initiating an on-demand self-test (ODST) of any of the ECUs 101 so that faults associated with the ECU are reported back to the tester 11. In particular, a gateway module (GWM) 12 is used to implement diagnostic communications between each ECU 101 and the diagnostic tester 11. The diagnostic tester 11 can be any suitable vehicle diagnostic tester, such as an engineering, manufacturing or service tester, a connected diagnostic tester, or an on-board diagnostic or software over the air (SOTA) tester. In fact, a vehicle typically has a plurality of different diagnostic testers that communicate with the on-board ECUs.
[0042] Each ECU 101 in the diagnostic electrical architecture 10 has a local diagnostic server or module 102. Each diagnostic server 102 is arranged to perform self-diagnostic operations associated with its respective ECU 101, including identifying, reporting and / or repairing faults or failures of components or software of the ECU 101 or sensors associated with the ECU 101. The diagnostic server 102 then reports any identified faults or errors back to the diagnostic tester 11, and notifies the diagnostic tester 11 of any self-repair operations that have been performed.
[0043] The ECU 101 in the diagnostic architecture 10 is part of different networks present in the vehicle, such as CAN (Controller Area Network), LIN (Local Interconnect Network), FlexRay, and Ethernet. Each of these networks has different protocols and data transmission rates. For example, LIN is used for low-speed networks such as sensors and actuators with a data rate of about 20kbps, CAN can be used for communication between different ECUs with a data rate of about 1Mbps to 5Mbps, FlexRay can be used for safety-critical applications with a data rate of about 10Mbps, and Ethernet can be used for infotainment systems, advanced driver assistance systems (ADAS), and wireless interfaces such as 4G, Wi-Fi, etc., with data rates ranging from megabits per second to gigabits per second.
[0044] From a logical point of view, the GWM 12 provides a single entry point for communication between the diagnostic tester 11 and the component-level diagnostic architecture 10 with the ECU 101. The GWM 12 acts as a router for diagnostic messages from one network to another (e.g., from Ethernet frames to CAN bus frames, and vice versa, e.g., from CAN bus frames to Ethernet frames). In particular, the GWM 12 bridges between the external or off-board network of the diagnostic tester 11 and the internal or on-board network of the vehicle ECU 101.
[0045] The diagnostic protocol used between the diagnostic tester 11 and the ECU 101 is the Unified Diagnostic Service (UDS) protocol defined in ISO Standard 14229-1. In particular, the UDS protocol for diagnostic communications for a variety of different underlying network technologies has been addressed and specified in various ISO standards: ISO 14229-3 specifies UDS over CAN; ISO 14229-4 specifies UDS over FlexRay; and ISO 14229-5 specifies UDS over Internet Protocol. The UDS protocol continues to be used for the purpose of diagnostic communications regardless of the underlying network technology used in the vehicle electrical architecture. This may limit the diagnostic capabilities that can be delivered, while also limiting the scalability and / or flexibility of the overall diagnostic electrical architecture.
[0046] The standardized diagnostic transmission protocol DoIP (Diagnostic Communication over Internet Protocol) is used in conjunction with the UDS protocol to encapsulate diagnostic messages in Ethernet frames for communication between the diagnostic tester 11 and the vehicle ECU 101. Therefore, the GWM 12 routes the DoIP Ethernet frame from the diagnostic tester 11 to the relevant transmission protocol for the specific ECU 101 to which the diagnostic message is to be sent, such as CAN, LIN, FlexRay frames, etc. That is, the diagnostic tester 11 establishes p2p diagnostic communication with each ECU 101 in the vehicle architecture (i.e., component-level diagnostic architecture) 10 via the DoIP gateway module 12, and UDS is used as the protocol for diagnostic communication in the entire diagnostic electrical architecture 10.
[0047] A single fault or failure in a vehicle may cause multiple ECU 101 faults. Each of these ECUs 101 will detect and report faults related or associated with that particular ECU 101 and report these faults back to the diagnostic tester 11. This means that the diagnostic tester 11 may receive multiple fault codes, also known as diagnostic trouble codes (DTCs), from multiple different ECUs 101. The diagnostic tester 11 or an engineer or service technician must then analyze and interpret the received DTCs to determine the root cause of the multiple DTCs and therefore determine the correct diagnostic fix that needs to be performed.
[0048] Although many different diagnostic testers may access the ECU 101, only a single diagnostic tester may establish diagnostic communication with the component-level diagnostic architecture 10 at any one time. Therefore, relative priorities between different diagnostic testers may be set in the GWM 12. For example, a third-party off-board tester such as an OBD scan tool or an insurance dongle may be assigned the highest priority, a manufacturer off-board tester may be assigned the next highest priority, and an on-board SOTA may be assigned the lowest priority.
[0049] The present invention provides a vehicle diagnostic electrical architecture in which the diagnostic capabilities of the vehicle, in particular the vehicle's ECU, are provided as diagnostic services via the vehicle's network service bus to, for example, an off-board diagnostic tester and / or other on-board modules. Figure 1 This is in contrast to the signal-oriented p2p diagnostic communication of the diagnostic electrical architecture 10 in FIG. Figure 1 Each ECU in the electrical architecture of the present invention may respond to the diagnostic tester with a signal having raw diagnostic object data related to the diagnostic test performed (where the raw data must then be interpreted outside the vehicle), but in the present invention, the ECU may respond to the diagnostic tester with interpreted or evaluated data or values related to the diagnostic test performed. This will be described in detail below.
[0050] Figure 2 Another diagnostic electrical architecture 20 for a vehicle is shown. Figure 1 Different, in Figure 2 In FIG. 2 , the architecture 20 is a hierarchical diagnostic architecture 20 of the vehicle. This may also be referred to as a layered diagnostic architecture 20. Figure 1 Unlike the non-hierarchical architecture 10, the hierarchical architecture 20 includes multiple diagnostic layers 21, 22, and 23. Figure 1 Similar to the non-hierarchical architecture 10, the hierarchical architecture 20 has a component diagnostic layer 21 including a plurality of ECUs 211 each for performing a different function on the vehicle.
[0051] Each ECU 211 in the hierarchical diagnostic architecture 20 has a local diagnostic server or module 212. Each diagnostic server 212 provides the ability to read fault log data associated with the associated ECU 211 and initiate ECU self-tests to determine whether all inputs and outputs to the ECU are connected, configured and functioning as designed, and whether the components or software of the ECU and sensors connected to the ECU are functioning correctly. In addition to these "pull" mechanisms for retrieving fault data from the ECU 211, the ECU 211 is also able to "push" or transmit fault data to higher levels or layers 22, 23 of the hierarchical diagnostic architecture 20, such as when a fault is detected or when a predefined event or trigger occurs.
[0052] and Figure 1Unlike the non-hierarchical architecture 10 of the present invention, the hierarchical architecture 20 also includes two supervisory diagnostic layers 22, 23 above the component diagnostic layer 21 or between the component diagnostic layer 21 and an on-board or off-board diagnostic tester 24, which is arranged to be in diagnostic communication with the hierarchical diagnostic architecture 20. The provision of such supervisory layers 22, 23 enables diagnostic monitoring and reporting at a level higher than the component-level diagnostics provided by the ECU 211 in the component diagnostic layer 21. Although the diagnostics performed in the component diagnostic layer 21 are limited to determining and reporting faults associated with a specific ECU independently of other ECUs, the supervisory layer has an overview of multiple different ECUs 211 in the lower layer 21, and thus the diagnostics performed in the supervisory layer can aggregate fault data from multiple different ECUs 211 - or more generally, fault data from the lower layers - to provide a clearer diagnostic overview of the vehicle system.
[0053] In the described example, the hierarchical diagnostic architecture 20 includes a system diagnostic layer 22 on the component diagnostic layer 21 and a vehicle diagnostic layer 23 on the system diagnostic layer 22 and arranged to be in diagnostic communication with a diagnostic tester 24. In the system diagnostic layer 22, fault data from multiple ECUs 211 are analyzed and interpreted for each of a plurality of application services. Each application service requires certain functions provided by certain individual components or ECUs 211. As an example, vehicle speed can be supplied or provided as an application service for the vehicle. In order to determine the vehicle speed, each of the four wheel speed sensors of the vehicle is required to provide a wheel speed sensor signal.
[0054] Diagnostics can then be performed at a "service level" for each of the different application services provided based on the fault data from the associated ECU. In particular, the system diagnostic layer 22 includes a plurality of application service interface modules 221 that are each respectively connected to a plurality of ECUs 211 in the component diagnostic layer 21. Note that a given ECU 211 can provide fault data to a plurality of different application service modules 221 via a hierarchical structure. Diagnostic notifications can then be sent from the application service modules 221 to a higher layer of the architecture 20, in this case the vehicle diagnostic layer 23. The system diagnostic layer 22 also includes a local database or register 222 that can be used to store fault data or other notifications from the ECUs 211 in the component diagnostic layer 21.
[0055] In the vehicle diagnostic layer 23, the fault data from the plurality of application service modules 221 is analyzed and interpreted for each of a plurality of customer-oriented vehicle features. These user features may be considered vehicle features that may be used to assist the user in driving the vehicle, or other vehicle features that provide entertainment, comfort, etc. to the vehicle user. Such vehicle features may include, for example, a direction indicator feature or a lane change assist feature.
[0056] Diagnostics may then be performed at a "vehicle level" or "vehicle feature level" for each of the different vehicle user features provided based on the fault data from the associated application service module 221. In particular, the vehicle diagnostic layer 23 includes a platform diagnostic service module 231 connected to the application service module 221 in the system diagnostic layer 22. Diagnostic notifications may then be sent from the platform diagnostic service module 231 to an on-board or off-board diagnostic tester 24. The vehicle diagnostic layer 23 also includes a central database or register 232 that may be used to store fault data or other notifications from the application service module 221 in the system diagnostic layer 22. The central database 232 also includes a list of current application services provided by the vehicle, which list may be added to or modified over time.
[0057] Figure 3 Shown in more detail Figure 2 In particular, each application service module 221 includes a local diagnostic agent 2211, which is similar to the diagnostic server 212 of the ECU in some aspects. In particular, the local diagnostic agent 2211 is integrated with the associated application service module 221 and has direct access to all inputs to and outputs from the module 221, as well as to the internal state of the application service module 221. That is, the local diagnostic agent 2211 is connected to the corresponding interfaces of the input 2212, output 2213 and internal state 2214 of the module 221. Figure 2 In the example of , the local diagnostic agent 2211 can perform diagnostics at the “service level” of the hierarchical network architecture 20 based on the accessed data (which may include, for example, fault data received from multiple ECUs 211).
[0058] Figure 4 A vehicle network architecture 40 is shown that includes multiple connected computing devices disposed in a vehicle. The network architecture 40 includes a central computing platform (CCP) 41. The CCP 41 is connected to multiple other computing platforms in the form of domain controllers or partitioned computing platforms (CPs) or remote input / output (RIO) modules 43 via an Ethernet data backbone 42. These CPs and RIOs 43 are each also connected to multiple ECUs 211 via a conventional network 44 (e.g., CAN, FlexRay, or LIN).
[0059] The computing device may be provided by running suitable software on any suitable computing substrate using conventional or custom processors and memory. Some of the computing devices may use a common computing substrate (e.g., they may run on the same server) or separate substrates, or one or some of the computing devices may themselves be distributed among multiple computing devices.
[0060] In the example described illustratively, the CCP 41 is connected to four CPs and RIOs 43 along an Ethernet backbone network, in particular, to three RIO modules 431, 432, 434 and an ADC (ADAS domain controller) 433. In the case of the architecture 20, the first RIO 431 is connected to three ECUs 211 along a conventional network 44, in particular, to an ABS module 2111, a PCM 2112, and a TCM 2113. The ABS module 2111 is also connected to four wheel speed sensors 45 for respective wheels of the four wheels of the vehicle. The second RIO 432 is connected to an IPC 2114 and a plurality of other peripheral modules or ECUs 2115 along a conventional network 44. The nth RIO 434 is also connected to a plurality of peripheral modules 2116, 2117, 2118 along a conventional network 44.
[0061] Figure 2 Different diagnostic layers 21, 22, 23 in the hierarchical diagnostic architecture 20 are hosted on different computer devices or modules of the vehicle network architecture 40. In particular, Figure 4 As indicated in , the vehicle diagnostic layer 23 is hosted on the CCP 41 , the system diagnostic layer 22 is hosted on the CP / RIO 43 and / or the CCP 41 , and the component diagnostic layer 21 is hosted on the ECU 211 and / or the CP / RIO 43 .
[0062] and Figure 1 Unlike the "signal-oriented" diagnostics of Architecture 10, Figure 2 The "service-oriented" diagnostics of the architecture 20 do not use UDS as the protocol for diagnostic communications throughout the diagnostic architecture 20. Either the diagnostic tester 24 that establishes diagnostic communications with the vehicle directly supports a service-oriented diagnostic interface, or the platform diagnostic service module 231 performs the conversion from UDS (between the tester 24 and the platform diagnostic service module 231) to service-oriented diagnostic communications (between the platform diagnostic service module 231 and the rest of the vehicle architecture 20), and vice versa, performs the conversion from service-oriented diagnostic communications to UDS.
[0063] Each RIO 43 connected via the Ethernet data backbone 42 provides application services via the application service module 221. These application services can be subscribed to and unsubscribed from by the tester 24 or other components / modules of the vehicle via the network service bus 42. Note that modules that are not directly connected to the Ethernet backbone network 42 cannot provide diagnostic services. Figure 2 In the example of FIG. 4 , the application service module 221 is part of the service layer 22, and the service layer 22 is hosted on the CCP 41 and / or the RIO 42. Figure 4 As can be seen, since the CCP 41 and / or RIO 42 are directly connected to the Ethernet backbone 42, in this case the application service module 221 is always directly connected to the Ethernet backbone 42. In the case where the (peripheral) modules / ECUs are not directly connected to the Ethernet backbone and therefore cannot provide diagnostic services, they can publish an equivalent network signal interface for diagnostic services through one of the conventional subnets (e.g. CAN, LIN, FlexRay). The diagnostic signal manager module hosted on the RIO 43 then manages the mapping between the diagnostic signals from the ECU and the diagnostic services provided to, for example, the tester. That is, the diagnostic signal manager acts as a local gateway between the Ethernet data backbone and the various subnets of the CAN / LIN / FlexRay network.
[0064] Reference Figure 4 , describes an example for highlighting the benefits of a service-oriented diagnostic architecture with a local diagnostic agent. In particular, in this example, vehicle speed is provided as a service, where wheel speed signals are from each of four wheel speed sensors, i.e., one wheel speed sensor for each wheel of the vehicle.
[0065] The ABS module 2111 receives wheel speeds from four wheel speed sensors 45 connected to the ABS 2111 via a conventional network 44. The RIO #1 module 431, which is directly connected to the Ethernet backbone 42, calculates the vehicle speed based on the wheel speed signals received from the ABS module 2111 via the conventional network 44. The RIO #1 module 431 then provides the vehicle speed as a service to the modules participating in the service-oriented architecture, where the quality of service is added to the service interface. The RIO #1 module 431 then routes the calculated vehicle speed signal back through the conventional network 44 connected to the RIO #1 module 431.
[0066] Other modules directly connected to the Ethernet backbone network 42 can then subscribe to the vehicle speed service provided in the RIO #1 module 431. For example, the RIO #2 module 432 subscribes to the vehicle speed service and uses it as input for the application / service hosted on the module 432. In addition, the RIO #2 module 432 provides a reverse conversion from service-oriented communication to signal-oriented communication, and transmits the obtained vehicle speed signal through the conventional network 44 connected to the RIO #2 module 432. In addition, the ADC module 433 subscribes to the vehicle speed service from the Ethernet service bus 42 and uses the vehicle speed service for its own application / service.
[0067] The PCM 2112 and the TCM 2113 are connected to the RIO #1 module 431 through the conventional network 44, and thus these modules 2112, 2113 receive the vehicle speed signal transmitted by the RIO #1 module 431 to deliver their own functions. Similarly, the IPC module 2114 is connected to the RIO #2 module 432 through the conventional network 44, and thus the IPC module 2114 receives the vehicle speed signal transmitted by the RIO #2 module 432 to deliver its own functions.
[0068] In terms of diagnostics, faults or failures related to wheel speed sensors or signals can be reported at the service level, which advantageously can provide an explanatory view of the failure rather than the original diagnostic trouble code (DTC), which then needs to be analyzed off-vehicle to find the root cause of the failure.
[0069] For example, if the first of the wheel speed sensors 45 fails, this will be detected by the diagnostic server in the ABS module 2111 which will generate a DTC, such as a short circuit or an open circuit, for the wheel speed sensors 45. Figure 4 , the failure of the wheel speed sensor 45 will also be detected by the RIO module #1 431, which will also generate a DTC, such as invalid serial data has been received from the wheel speed sensor 45. In a signal-oriented diagnostic architecture, two of these individual DTCs may be reported, and analysis of the potential fault or root fault would then be required. In contrast, in a service-oriented diagnostic architecture, classification of the DTCs can be performed in the system diagnostic layer 22 - specifically in the local diagnostic agent 2211 of the application service module - to determine the root fault that caused multiple DTCs. In this case, the classification determines that the wheel speed sensor 45 is faulty, and therefore only the DTC code generated by the ABS module 2111 is reported.
[0070] As another example, and with continued reference to Figure 4, consider a situation where three of the wheel sensors 45 fail. In this case, the ABS module 2111 will generate three DTCs, namely, there is a short circuit or an open circuit in each of the three wheel speed sensors 45. The RIO module #1 431 will also generate three DTCs, namely, invalid serial data has been received from each of the three failed wheel speed sensors 45. However, unlike the previous example, if three wheel speed sensors fail, calculation of vehicle speed cannot be performed, making it impossible for the vehicle speed to be provided as a service by the RIO module #1 431. As outlined above, there are many modules in the vehicle that utilize a calculated vehicle speed signal. When the vehicle speed service is not received as a service along the Ethernet network 42, the RIO module #2 432 generates a DTC, such as an invalid vehicle speed signal, and the IPC module 2114 also generates a DTC, such as a signal authenticity failure because the steering column cannot be unlocked, or the engine cannot be started due to an incorrect vehicle speed. In addition, the ADC module 433 also utilizes a vehicle speed service, such as as part of a cruise control function, and therefore when the vehicle speed is not received as a service along the Ethernet network 42, the ADC module 433 generates a DTC, such as an invalid vehicle speed signal. In addition, the PCM 2112 and TCM 2113 can use the vehicle speed signal transmitted by the RIO module #1 431 along the conventional network 44, and therefore these modules will generate DTCs when the vehicle speed signal is not received. In a signal-oriented diagnostic structure, each of these nine separate DTCs (two for the TCM 2113) may be reported, and then an analysis of the potential fault or root fault would be required. In contrast, in a service-oriented diagnostic architecture, service-level analysis of the DTCs can be performed in the system diagnostic layer 22 (in this case hosted by the domain controllers 431, 432, 433) and the vehicle diagnostic layer 23 (in this case hosted in the CCP 41) to determine the root fault that caused multiple DTCs. In this case, the service level diagnostics identified three faults in the wheel speed sensor 45 and therefore only reports the three DTC codes associated with the wheel speed sensor faults generated by the ABS module 2111.
[0071] As yet another example, consider that the conventional network communication bus 44 connected to the RIO module #1 431 is down / faulty. In this case, the RIO module #1 431 will generate a DTC for this. The ABS 2111, PCM 2112, and TCM 2113 are all on this communication bus 44, and therefore each of these modules also generates a DTC for this. The RIO module #2 432 and ADC 433 need to communicate with the ABS module 2111, and therefore each generates a DTC that communication with the ABS module 2111 has been lost. Similarly, the IPC module 2114 needs to communicate with the ABS module 2111, and therefore generates a DTC that communication with the ABS module 2111 has been lost. In a signal-oriented diagnostic structure, a "communication bus down" DTC and a "communication lost with ABS" DTC will be reported, and analysis of the underlying fault or root fault will then be required. In contrast, in a service-oriented diagnostic architecture, service-level analysis of DTCs may be performed in the system diagnostic layer 22 and the vehicle diagnostic layer 23 to determine that a communication bus down or fault is the root cause, and therefore only report a “communication bus down” DTC.
[0072] Figure 5 Shows Figure 2 4. An example of how the hierarchical diagnostic electrical architecture 20 of FIG. 4 can provide an application service for a vehicle user feature in the form of a direction indicator feature. The direction indicator feature has been decomposed into one application service 51 in the system diagnostic layer (or second diagnostic layer) 22, and four functions 521, 522, 523, 524 in the component diagnostic layer (or first diagnostic layer) 21. In the depicted example, both the vehicle diagnostic layer 23 and the system diagnostic layer 22 are hosted on the CCP 41, and the component diagnostic layer 21 is hosted on the RIO 43. The four functional components or modules 521, 522, 523, 524 are each hosted on a different one of the RIOs 43. The four functional components 521, 522, 523, 524 each have an associated diagnostic server 5211, 5221, 5231, 5241.
[0073] In the described example, the four functions 521, 522, 523, 524 include three light functions 521, 522, 524 and one stalk function 523. Each of the functions 521, 522, 523, 524 receives sensor data from a corresponding sensor 531, 532, 533, 534 connected to it via a conventional network 44, in particular in this case a LIN. In particular, the sensors include sensors associated with different indicator lights on the vehicle, for example at the front or rear of the vehicle or on the rearview mirror. The data from each of the function modules 521, 522, 523, 524 is transmitted to the indicator service module 51 via the Ethernet backbone network 42.
[0074] With regard to diagnostic capabilities, each of the diagnostic servers 5211, 5221, 5231, 5241 can perform diagnostic operations on the received sensor output data together with the input / output connections of the functional modules 521, 522, 523, 524. Diagnostic notifications (e.g., in the form of fault codes) are transmitted to the indicator application service 51, and in particular, the local diagnostic agent 511 of the service 51 performs service-level diagnostics on the diagnostic notifications received from the functional modules 521, 522, 523, 524 and the internal state of the indicator module 51.
[0075] like Figure 5 As shown, the off-board engineering diagnostic tester 54 is connected to the platform diagnostic service module 231 in the vehicle diagnostic layer 23. Since there is only one application service in this example, namely the indicator service 51, there is no vehicle or feature level classification of diagnostic notifications in the vehicle diagnostic layer 23. The availability of the indicator service 51 is stored in the central database 232. The engineering tester 54 can be made aware of the indicator service 51, or the availability of the indicator service 51 can be sent to the engineering tester 54, so that diagnostic messages related to the indicator service 51 can be sent to the engineering tester 54. In particular, the local diagnostic agent 511 can generate group diagnostic notifications based on its diagnostic operations. In the described example, the diagnostic communication between the engineering tester 54 outside the vehicle and the platform service module 231 on the vehicle is sent using the UDS transmission protocol. A separate gateway module in the vehicle architecture is not required. This is because such a gateway function can be provided as part of the platform diagnostic service module 231. That is, the diagnostic communication is converted between service-oriented diagnostic communication and UDS on Do IP so that successful diagnostic communication between the tester 54 and the vehicle architecture 20 is possible.
[0076] The engineering tester 54 can dynamically discover the indicator service 51 by subscribing to the latest list of diagnostic capabilities of the provided services stored in the on-board diagnostic registry or the central database 232. In particular, the central database 232 stores a list of faults, sensor readings, etc. supported by the diagnostic service. If one of the functions 521, 522, 523, 524 of the indicator service 51 is added / removed / modified, the diagnostic capabilities of the indicator service 51 are updated in the central registry 232. For example, the engineering tester 54 can send a request to read the fault information associated with the indicator service 51. The ECU 5211, 5221, 5231, 5241 responds with raw data in the form of relevant diagnostic objects such as fault codes / DTCs. The diagnostic registry of the on-board central database 232 can then be used to interpret the DTCs and send the interpreted diagnostic objects back to the diagnostic tester 54, so that the diagnostic data sent outside the vehicle does not need to be interpreted by the testee.
[0077] Component-based diagnostics allow for the detection of physical faults of sensors and actuators. However, it does not allow for the determination of whether the received sensor data is suitable for the purpose of the application that uses it. That is, even if the sensor itself is not faulty, the received data may be outside the range that is useful for a specific application. Therefore, the quality of service can be improved by introducing functional operating range monitoring of the received sensor data.
[0078] Physical faults of sensors and actuators can be monitored at the component level, i.e., the ECU level. This includes physical I / O faults, such as short circuit faults or open circuit faults. When such a fault is detected, a DTC log is created. At the service level, the local diagnostic agent 2211 can perform functional operating range monitoring of sensor data. Specifically, the local diagnostic agent 2211 can evaluate the functional validity of the sensor data received under a given operating state of a specific system, and fuse the received data from other sources in a given context. If it is determined that the received data is not suitable for the purpose, the local diagnostic agent 2211 will create a DTC log and generate an event notification even if no physical fault is detected at the component level.
[0079] Once the local diagnostic agent 2211 generates such a notification, it is evaluated at the vehicle level for vehicle status and power mode by the vehicle level supervision service. As a result of this evaluation, if necessary, a predicted event notification can be generated, i.e., an event notification predicting a possible sensor or actuator failure. Therefore, the diagnostic architecture 20 is not limited to reactive event notifications.
[0080] although Figure 2 The example of shows a service-oriented diagnostic electrical architecture that is hierarchical in nature with multiple diagnostic layers, but in different examples, a service-oriented diagnostic electrical architecture that is non-hierarchical in nature is also possible. In such an example, various ECUs can broadcast or publish the services provided. For example, other components such as external diagnostic testers can subscribe to specific ECUs to receive event notifications.
[0081] Now describe Figure 1 The non-hierarchical, signal-oriented (i.e., UDS protocol) architecture 10 is compared to non-hierarchical and hierarchical variants of service-oriented architectures (e.g., Figure 2 In particular, the steps involved in the design, deployment, runtime, and update phases of the diagnostic use case for each architecture are now described.
[0082] First, the diagnostic design phase is described. For UDS communication, UDS protocol adaptation is required. This involves identifying all diagnostic use cases for a specific system. Manufacturer-specific rules and restrictions are then defined on top of the UDS protocol specification for diagnostic communication, i.e. ISO 14229-1 as mentioned above. Note that not all manufacturer-specific customizations or extensions may be feasible within the UDS framework.
[0083] For service-oriented diagnostics (SoD), a SoD design needs to be performed. For both flat and layered architectures, this involves identifying all diagnostic use cases for a specific system, such as for UDS communications. However, unlike UDS, SoD services that meet all diagnostic use cases are designed, specifying the service provider and consumer relationships. Then suitable communication middleware that meets all identified diagnostic use cases is selected. In particular, suitable industry standard middleware can be selected, such as SOME / IP (Scalable Service-Oriented Middleware over IP), REST (Representational State Transfer), DDS (Data Distribution Service), etc. Then the SoD service interface needs to be designed. In particular, properties, methods, events and fields are specified on top of the selected middleware. For a layered SoD architecture, the SoD service interface is then instantiated on the various diagnostic layers of the architecture, such as the above-mentioned system and vehicle layers.
[0084] For both UDS and SoD communications, diagnostic objects are designed. In both cases, the failure modes and causes of the system are identified. This can be achieved using Failure Mode Effects Analysis (FMEA) or similar methods. In particular, diagnostic objects are designed - in the form of diagnostic trouble codes (DTCs) - for monitoring the identified failure modes and causes of failures. They are also designed to capture snapshot information of environmental conditions when a failure occurs. A diagnostic extraction file (DEXT) is created for configuring the ECU software. A diagnostic description file (ODX) is also created for configuring the diagnostic tester.
[0085] Secondly, the diagnostic deployment phase is described. For UDS communication, the ECU software platform is configured using DEXT files, and the diagnostic tester is configured using ODX files. An external process ensures that the revisions of the DEXT files and ODX files are compatible between the on-board ECU and the diagnostic tester.
[0086] For SoD communication, the SoD service interface is deployed on a chosen communication middleware such as SOME / IP. The ECU software platform is configured using DEXT files and ODX files. Note that this is in contrast to UDS communication, where ODX files are used to configure the diagnostic tester. For flat (non-hierarchical) SoD, the ECU ODX files are embedded in the ECU software, while for hierarchical (layered) SoD, the vehicle ODX files are embedded in the vehicle diagnostic layer of the architecture. This means that there is no need to use ODX files to configure external off-board diagnostic testers for SoD communication (both flat and layered), which significantly simplifies the complexity of external processes that need to be managed, for example, by the manufacturer. In addition, the centralized management of ODX files for hierarchical SoD in the vehicle diagnostic layer further simplifies the process and communication.
[0087] Third, consider the diagnostic runtime phase. For UDS communication, the off-vehicle diagnostic tester establishes diagnostic communication with the target ECU or module in the vehicle by using the UDS protocol. This diagnostic communication is successful if the ODX file used to configure the tester is compatible with the DEXT file used to configure the ECU software stack in the vehicle. In the example, the off-vehicle diagnostic tester sends a request message, such as a request to read DTC information. The on-vehicle target ECU responds with a UDS response message, which includes the requested diagnostic object with the DTC appropriately statically configured using "raw" values. The diagnostic tester then interprets the raw values of the received diagnostic object by using the ODX file configured with the diagnostic tester. If the ODX file used for the tester is the same / compatible with the DEXT file used to configure the ECU software, the diagnostic can correctly interpret the response from the ECU.
[0088] For SoD communication, the off-board diagnostic tester establishes diagnostic communication with the target ECU or module in the vehicle by using the SoD interface. If the diagnostic tester directly supports the SoD interface, this diagnostic communication is successful. Alternatively, the diagnostic tester communicates with the vehicle architecture using UDS, and the platform diagnostic service module in the vehicle architecture performs conversion between SoD and UDS on DoIP so that the diagnostic tester can successfully communicate with the target ECU through the SoD interface. The diagnostic tester is then able to dynamically discover or learn diagnostic services supplied or provided through the network service bus via the SoD service interface. In particular, the central database maintains a diagnostic service registry including a list of supplied services, and the diagnostic tester subscribes to the diagnostic service registry to dynamically learn the available services. Note that the target ECU also subscribes to the diagnostic service registry. Since the ODX file is embedded in the on-board architecture—particularly in the ECU software for flat architectures and in the vehicle diagnostic layer for layered architectures—then the target ECU can respond to the diagnostic tester with interpreted values of diagnostic objects (DTCs, events, snapshot dates, etc.) instead of the original values of the diagnostic objects that need to be interpreted outside the vehicle.
[0089] Finally, consider the diagnostic update phase. The update can be in the form of a new application or diagnostic capability, for example. For both UDS communication and SoD communication, the DEXT file and the ODX file are updated to reflect the changes in the diagnostic capabilities. A new version of the DEXT file is released for the ECU software configuration, and a new version of the ODX file is released for the tester configuration. For both the UDS configuration and the SoD configuration, the ECU software is reconfigured using the new DEXT file. However, unlike UDS communication, for SoD communication, a new ODX is also used to reconfigure the ECU software. For UDS communication, the diagnostic tester needs to be reconfigured using the new ODX file by using an external process. In contrast, for SoD communication, such reconfiguration of the external diagnostic tester is not required. For UDS communication, if both the tester and the target ECU have been statically updated to recognize the changes, the target ECU will support the new diagnostic capabilities when requested by the diagnostic tester. In contrast, for SoD communication, the diagnostic tester dynamically discovers new diagnostic capabilities by discovering new diagnostic services supplied in the updated diagnostic service registry and subscribing to them. As described above, the diagnostic communication between the diagnostic tester and the target ECU can be successfully established if the diagnostic tester supports the SoD interface or by performing the conversion between UDS and SoD in the platform diagnostic service module of the vehicle architecture.
[0090] Figure 6The steps of a method 60 for providing diagnostic communications in a diagnostic electrical architecture of a vehicle are summarized. The vehicle has a network including a plurality of onboard computing devices for hosting the diagnostic electrical architecture. The onboard computing devices include a CCP 41, a plurality of RIO modules 43 or other regional computing devices or domain controllers, and a plurality of ECUs or other peripheral modules 211. For example, the diagnostic electrical architecture may be Figure 2 hierarchical architecture 20. Alternatively, the diagnostic electrical architecture may be a non-hierarchical architecture. The architecture 20 includes electronic control units 211, each of which has a diagnostic server module 212. The architecture 20 also includes service interface modules 221, 231, which are arranged to allow diagnostic communication between the electronic control units 211 of the vehicle and the network service bus 42. In the described example, the architecture 20 includes a plurality of application service interface modules 221 in the system layer, and a platform service interface module 231 in the vehicle layer. The architecture 20 also includes diagnostic service registration modules 222, 232, which store a list of diagnostic services supplied via the service interface modules 221, 231.
[0091] At step 601, the diagnostic server module 212 performs a diagnostic task to generate diagnostic object data. Specifically, each diagnostic server 212 has a plurality of associated diagnostic objects, which may include DTCs, events, data IDs (DIDs) and / or diagnostic control routines, for diagnosing and monitoring various possible fault modes, input / output / internal state controls and / or module identification associated with the corresponding ECU 211. Specific diagnostic object data may be generated in response to a request or other event. The diagnostic object data includes raw data or codes that need to be interpreted to identify associated faults. For example, a DEXT file may specify configuration parameters for configuring ECU diagnostic software and diagnostic objects supported by the ECU software.
[0092] At step 602 , the service interface module receives the generated diagnostic object data from the ECU 211 . Specifically, in the depicted example, the platform diagnostic service module 231 may receive the diagnostic object data from each of the plurality of ECUs 211 .
[0093] At step 603, diagnostic service data is retrieved from the diagnostic service registration module 232. In particular, the retrieved diagnostic service data includes the diagnostic capability description of the generated diagnostic object data. For example, the diagnostic service data may include a diagnostic description file, such as an ODX file.
[0094] At step 604, the diagnostic service notification is transmitted via a network service bus, such as via the Ethernet backbone 42. In particular, the diagnostic service notification is based on the generated diagnostic object data and the diagnostic service data. That is, the transmitted diagnostic service notification includes the interpreted values or data of the original (non-interpreted) diagnostic object data. For example, the diagnostic service notification can be transmitted outside the vehicle to the diagnostic tester 24, so there is no need to interpret the message received from the vehicle architecture 20.
[0095] The diagnostic service notification may be an autonomous diagnostic service notification, ie, automatically generated when an event / fault occurs. The diagnostic service notification may also be a response to a diagnostic request received from an on-board or off-board diagnostic tester.
[0096] Figure 7 A vehicle 70 is shown, which in the illustrated embodiment includes a vehicle having a network architecture 40 ( Figure 8 ) and hosts a vehicle with a diagnostic electrical architecture 20 .
[0097] Embodiments of the present invention are advantageous in that they provide service-oriented diagnostic communications in a vehicle electrical network architecture. This is in contrast to known systems that use signal-oriented diagnostic communications, for example, using the UDS protocol. The service-oriented diagnostic communications of the present invention allow diagnostic tasks to be supplied as services across a vehicle service bus, for example, to a diagnostic tester outside the vehicle or to other modules that are part of the vehicle network architecture. In particular, service-oriented diagnostic communications allow interpreted diagnostic messages to be transmitted to, for example, an external diagnostic tester, rather than raw diagnostic data, such as one or more DTCs, which then need to be interpreted outside the vehicle.
[0098] Embodiments of the present invention are particularly advantageous in that they use a service-oriented architecture middleware to independently perform diagnostic communications. This allows for a scalable and flexible on-board service diagnostic interface to be provided. In particular, updates to ECU diagnostic capabilities do not require reflashing of the ECU. Furthermore, this allows for dynamic discovery of diagnostic services by other components (e.g., external diagnostic testers) so that these components do not need to be specifically configured to be compatible with any ECU diagnostic updates.
[0099] Known systems do not provide such capabilities, at least not to the greatest extent. Some known systems provide middleware support for service-oriented architectures; however, these systems only provide support for UDS diagnostics within the basic software components of the ECU. Therefore, the known systems inherit the limitations of the UDS protocol. For example, in some known systems, the diagnostic capabilities of the ECU need to be statically configured during the design and development phase of the ECU. That is, each time the diagnostic capabilities of the ECU change, the basic software layer of the ECU needs to be statically reconfigured and refreshed. Some known systems can provide a certain degree of dynamic configuration of the basic software layer of the ECU, such as providing functions for updating certain software packages without having to refresh the entire ECU. In such cases, the individual software packages are clustered together and have their own diagnostic addresses, which are used to access diagnostic functions or software updates via a diagnostic manager component, where the component can configure each software package using another file. However, none of these known systems provide capabilities / flexibility beyond the services provided by UDS.
[0100] Embodiments of the present invention advantageously allow components such as external diagnostic testers to subscribe to a particular service so that diagnostic updates to the service can be learned dynamically. In particular, the present invention advantageously allows a service to generate an event notification or publish an event notification to all subscribers of a service based on an event trigger such as an update to the diagnostic capabilities of the service. Furthermore, event notifications can advantageously be provided with delivery guarantees to service subscribers.
[0101] Embodiments of the present invention are advantageous in that, from a diagnostic access perspective, they provide a logical and physical separation between external connection modules, i.e., diagnostic testers, and vehicle core modules, i.e., ECUs, by introducing an abstraction layer via a service interface module. This improves security and makes the diagnostic architecture less vulnerable to cyberattacks. This is in contrast to a p2p diagnostic architecture, where an external diagnostic tester can establish a direct communication path with the onboard ECU.
[0102] Embodiments of the present invention are advantageous in that they provide dynamic diagnostic resource conflict management. Specifically, embodiments of the present invention advantageously allow simultaneous access to multiple different diagnostic testers, such as, for example, legislative scan tools, SOTA events, OBD scan tools, insurance dongles, etc. This is in contrast to some known systems that are limited to allowing access to one diagnostic tester at a time through a gateway module, even if different testers require access to different system domains.
[0103] Reference Figure 8, showing a simplified example of the above-mentioned on-board computing device 800. The on-board computing device 800 may include a control unit or computing device having one or more electronic processors (e.g., microprocessors, microcontrollers, application-specific integrated circuits (ASICs), etc.), and may include a single control unit or computing device, or alternatively, different functions of the on-board computing device 800 or each on-board computing device 800 may be implemented or hosted in different control units or computing devices. As used herein, the terms "controller", "control unit" or "computing device" will be understood to include a single controller, control unit or computing device, as well as multiple controllers, control units or computing devices that operate together to provide the required control functions. A set of instructions may be provided that, when executed, enables the on-board computing device 800 to implement the control techniques described herein (including some or all of the functions required by the methods described herein). The set of instructions may be embedded in the one or more electronic processors of the on-board computing device 800; or alternatively, the set of instructions may be provided as software to be executed in the on-board computing device 800. The first controller or control unit may be implemented in software running on one or more processors. The one or more further controllers or control units may be implemented in software running on one or more processors, optionally the same one or more processors as the first controller or control unit.Other arrangements are also available.
[0104] exist Figure 8 In the example shown, the onboard computing device 800 includes at least one electronic processor 820 having one or more electrical inputs 822 for receiving one or more (input signals), and one or more electrical outputs 824 for outputting one or more (output signals). The onboard computing device 800 also includes at least one memory device 830 electrically coupled to the at least one electronic processor 820 and having stored therein instructions 840. The at least one electronic processor 820 is configured to access the at least one memory device 830 and execute the instructions 840 thereon.
[0105] The electronic processor 820 or each electronic processor 820 may include any suitable electronic processor (e.g., a microprocessor, a microcontroller, an ASIC, etc.) configured to execute electronic instructions. The electronic memory device 830 or each electronic memory device 830 may include any suitable memory device and may store various data, information, thresholds, lookup tables or other data structures, and / or instructions therein or thereon. In an embodiment, the memory device 830 has information and instructions for software, firmware, programs, algorithms, scripts, applications, etc. stored therein or thereon, which may control all or part of the methods described herein. The processor or each electronic processor 820 may access the memory device 830 and execute and / or use the instructions and information or those instructions and information to implement or perform part or all of the functions and methods described herein.
[0106] The at least one memory device 830 may include a computer-readable storage medium (e.g., a non-transitory or non-volatile storage medium), which may include any mechanism for storing information in a form readable by a machine or electronic processor / computing device, including but not limited to: magnetic storage media (e.g., floppy disks); optical storage media (e.g., CD-ROMs); magneto-optical storage media; read-only memory (ROM); random access memory (RAM); erasable programmable memory (e.g., EPROM and EEPROM); flash memory; or an electrical or other type of medium for storing such information / instructions.
[0107] An example vehicle-mounted computing device 800 has been described that includes at least one electronic processor 820 configured to execute electronic instructions stored in at least one memory device 830, which, when executed, causes the electronic processor 820 to perform the methods as described above. However, it should be understood that embodiments of the present invention may be implemented in any suitable form of hardware, software, or a combination of hardware and software. For example, it is contemplated that the present invention is not limited to being implemented by way of a programmable processing device, and that at least some of the functions and / or method steps of the present invention, and in some embodiments all of the functions and / or method steps, may also be implemented by way of non-programmable hardware, such as by way of a non-programmable ASIC, Boolean logic circuits, etc.
[0108] It should be understood that various changes and modifications may be made to the present invention without departing from the scope of the present application. For example, all features disclosed in this specification (including any attached claims, abstracts and drawings), and / or all steps of any method or process disclosed in this specification may be combined in any combination, except for combinations where at least some of such features and / or steps are mutually exclusive.
[0109] Unless expressly stated otherwise, each feature disclosed in this specification (including any attached claims, abstracts and drawings) may be replaced by alternative features having the same, equivalent or similar purpose. Therefore, unless expressly stated otherwise, each feature disclosed is only an example of a general series of equivalent or similar features.
[0110] The invention is not limited to the details of any foregoing embodiments. The invention extends to any novel one or any novel combination of the features disclosed in this specification (including any accompanying claims, abstract and drawings), or to any novel one or any novel combination of the steps of any method or process so disclosed. The claims should not be construed as covering only the foregoing embodiments, but also any embodiments falling within the scope of the claims.
Claims
1. A diagnostic electrical architecture for a vehicle, the vehicle comprising a plurality of onboard computing devices for hosting the diagnostic electrical architecture, and the diagnostic electrical architecture include: one or more electronic control units, each of the electronic control units comprising a diagnostic server module arranged to perform diagnostic tasks to generate diagnostic object data; a service interface module arranged to allow diagnostic communications between the one or more electronic control units and a network service bus of the vehicle, the service interface module being arranged to receive the generated diagnostic object data; as well as a diagnostic service registration module arranged to store diagnostic service data indicative of diagnostic services provided by the service interface module, the diagnostic service data comprising a diagnostic capability description of the generated diagnostic object data, wherein the service interface module is arranged to transmit a diagnostic service notification via the network service bus, the diagnostic service notification being based on the generated diagnostic object data and the diagnostic service data retrieved from the diagnostic service registration module; and The diagnostic service registration module is arranged to allow both the onboard module and the off-board module to subscribe to the diagnostic service registration module, so that the onboard module and the off-board module can dynamically learn the diagnostic service provided by the service interface module.
2. The diagnostic electrical architecture according to claim 1, in, The diagnostic service notification is generated in response to a change in diagnostic capabilities provided by the service interface module.
3. The diagnostic electrical architecture according to claim 2, in, The change in diagnostic capabilities is caused by the addition or removal of diagnostic tasks performed by the one or more electronic control units.
4. The diagnostic electrical architecture according to claim 2, in, The change in diagnostic capability is caused by the addition or removal of an electronic control unit associated with the service interface module.
5. The diagnostic electrical architecture according to any one of claims 1 to 4, in, The diagnostic service notification is generated in response to a request for diagnostic capabilities received by the service interface module.
6. The diagnostic electrical architecture according to claim 5, in, The request for diagnostic capabilities is received from a diagnostic tester external to the vehicle.
7. The diagnostic electrical architecture according to any one of claims 1 to 4, in, The generated service notification is transmitted outside the vehicle.
8. The diagnostic electrical architecture according to any one of claims 1 to 4, in, The generated diagnostic capability notification is used to update the diagnostic service registration module.
9. The diagnostic electrical architecture according to any one of claims 1 to 4, in, The service interface module is deployed on a communication intermediate device on one or more of the onboard computing devices.
10. The diagnostic electrical architecture according to claim 9, in, The communication intermediate device is one of the following: SOME / IP, an extensible service-oriented middleware based on IP; Representational State Transfer (REST); and Data Distribution Service DDS.
11. The diagnostic electrical architecture according to any one of claims 1 to 4, in, The vehicle's network service bus includes an Ethernet backbone network.
12. The diagnostic electrical architecture according to claim 11, in, The service interface module is directly connected to the Ethernet backbone network.
13. The diagnostic electrical architecture according to any one of claims 1 to 4, arranged to provide conversion between Unified Diagnostic Services (UDS) protocol communications and service-oriented diagnostic communications.
14. The diagnostic electrical architecture according to any one of claims 1 to 4, in, The diagnostic electrical architecture is a hierarchical architecture having a component diagnostic layer and at least one supervisory diagnostic layer, the component diagnostic layer including the one or more electronic units.
15. The diagnostic electrical architecture of claim 14, in, The at least one supervisory diagnostic layer includes the service interface module.
16. The diagnostic electrical architecture of claim 14, in, The at least one supervisory diagnostic layer includes the diagnostic service registration module.
17. The diagnostic electrical architecture of claim 14, in, The at least one supervisory diagnostic layer comprises a system diagnostic layer and a vehicle diagnostic layer, the vehicle diagnostic layer being at a higher level of the architecture than the system diagnostic layer, the vehicle diagnostic layer comprising the service interface module, and the system diagnostic layer comprising an application service module comprising a local diagnostic agent arranged to aggregate the generated diagnostic service notifications received from the electronic control unit to generate a supervisory level diagnostic service notification.
18. The diagnostic electrical architecture of claim 17, in, The supervisory-level diagnostic service notification is used to update the diagnostic service registration module.
19. A vehicle comprising a network architecture having a plurality of computing devices and hosting a diagnostic electrical architecture according to any one of claims 1 to 18.
20. A method of providing diagnostic communications in a diagnostic electrical architecture of a vehicle, the vehicle comprising a plurality of onboard computing devices for hosting the diagnostic electrical architecture, the diagnostic electrical architecture include: one or more electronic control units, each of said electronic control units comprising a diagnostic server module; a service interface module arranged to allow diagnostic communications between the one or more electronic control units and a network service bus of the vehicle; as well as Diagnostic service registration module, The method comprises: The diagnostic server module executes the diagnostic task to generate diagnostic object data; receiving the generated diagnostic object data into the service interface module; retrieving diagnostic service data from the diagnostic service registration module, the diagnostic service data including a diagnostic capability description of the generated diagnostic object data; transmitting, via the network service bus, a diagnostic service notification based on the generated diagnostic object data and the diagnostic service data; and Allowing both the on-board module and the off-board module to subscribe to the diagnostic service registration module enables the on-board module and the off-board module to dynamically learn the diagnostic service provided by the service interface module.
21. A non-transitory computer-readable storage medium having stored thereon instructions that, when executed by one or more processors, cause the one or more processors to perform the method of claim 20.
Citation Information
Patent Citations
Integrated fault diagnosis and prognosis for in-vehicle communications
CN103139011A
Diagnostic method and integrated ECU
CN103607327A
Vehicle fault remote diagnosis system and method
CN107272649A
Method and system for diagnosis or configuration of vehicle
CN108227674A
Integrated hierarchical process for fault detection and isolation
US20090295559A1
