Communication system

Abstract

Provided is a technique for reducing the communication time required for fault diagnosis communication without using a dedicated bus for fault diagnosis communication. A communication system (2) is provided with a plurality of communication nodes (30, 40, 50, 60, 70, 80, 90, 100, 110) for fault diagnosis communication that relays a diagnosis request and a diagnosis result between a request source and a request destination for fault diagnosis. A communication setting unit of a communication node encapsulates a first communication frame of a first communication protocol to a second communication frame of a second communication protocol, the first communication frame being specified to be used in a communication standard for fault diagnosis, if a communication determination unit determines that the communication is fault diagnosis communication when a diagnosis request is transmitted or a diagnosis result is transmitted. The communication speed of the second communication protocol is higher than the communication speed of the first communication protocol.

Description

Technical Field

[0001] The present disclosure relates to a technique for performing fault diagnosis communication. Background Art

[0002] There is known a technology for performing fault diagnosis communication via a communication node such as a central gateway.

[0003] For example, Patent Document 1 below proposes a technology for performing fault diagnosis communication between a diagnostic tool connected to a DLC or a center communicating wirelessly with a DCM, as a source of fault diagnosis request, and a destination of fault diagnosis request, via a communication node such as a central gateway.

[0004] In addition, DLC is the abbreviation of Diagnostics Link Connector, and DCM is the abbreviation of Data Communication Module.

[0005] Patent Document 1: Japanese Patent Application Laid-Open No. 2014-078800

[0006] However, the inventors have found a problem as a result of detailed studies: if the number of communication nodes relaying communication in the communication path between a fault diagnosis request source and a fault diagnosis request destination increases, the communication time required for fault diagnosis communication increases.

[0007] To reduce the communication time required for fault diagnosis communication, it is considered to use a dedicated bus for fault diagnosis communication instead of a shared bus with other communications. However, if a dedicated bus is set up for fault diagnosis communication, the problem of increasing the number of communication channels and buses will arise. Summary of the Invention

[0008] One aspect of the present disclosure provides a technique for reducing communication time required for fault diagnosis communication without using a dedicated bus for fault diagnosis communication.

[0009] A communication system according to one aspect of the present disclosure includes a plurality of communication nodes that relay fault diagnosis communications including a diagnosis request and a diagnosis result between a fault diagnosis request source and a fault diagnosis request destination.

[0010] Any one of the communication nodes includes a communication determination unit and a communication setting unit.

[0011] The communication determination unit determines whether the current communication is fault diagnosis communication. If the communication determination unit determines that the current communication is fault diagnosis communication, either when a diagnostic request is sent from a fault diagnosis request source to a request destination, or when a diagnostic result is sent from a fault diagnosis request destination to a request source, the communication setting unit encapsulates a first communication frame of a first communication protocol specified in a fault diagnosis communication standard into a second communication frame of a second communication protocol, wherein the second communication protocol has a faster communication speed than the first communication protocol.

[0012] According to this structure, since the first communication frame is encapsulated in the second communication frame, the time required to generate the second communication frame can be shortened compared to conventional protocol conversion in which data of the first communication frame is parsed to generate the second communication frame. Furthermore, the communication speed of the second communication protocol using the second communication frame is faster than the communication speed of the first communication protocol using the first communication frame.

[0013] In this way, since the first communication frame is encapsulated into the second communication frame of the second communication protocol, wherein the communication speed of the above-mentioned second communication protocol is faster than the communication speed of the first communication protocol, it is possible to reduce the communication time required for fault diagnosis communication without setting up a dedicated communication bus for fault diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 This is a block diagram showing the configuration of the communication system according to the first embodiment.

[0015] Figure 2 This is a block diagram showing the structure of the ECU.

[0016] Figure 3 is a block diagram showing a VM generated by a processor core.

[0017] Figure 4 This is a block diagram showing the functions of the ECU.

[0018] Figure 5 It is a schematic diagram showing the encapsulation and decapsulation of communication frames.

[0019] Figure 6 This is a flowchart showing the fault diagnosis communication process.

[0020] Figure 7 This is a flowchart showing the fault diagnosis communication process.

[0021] Figure 8 This is a block diagram showing the configuration of a communication system according to the second embodiment. DETAILED DESCRIPTION

[0022] Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0023] [1. First embodiment]

[0024] [1-1. Structure]

[0025] Figure 1 The communication system 2 shown is mounted on a vehicle and includes a DLC 10, a DCM 20, and ECUs 30, 70, and 90. ECU stands for Electronic Control Unit. The vehicle is equipped with either an internal combustion engine or an electric motor powered by a rechargeable battery as a driving source. The internal combustion engine can also be used to generate electricity to supply the rechargeable battery.

[0026] An external tool (not shown) is connected to the DLC 10. In this embodiment, the CAN protocol is used as a communication standard for fault diagnosis. Therefore, the DLC 10 and the ECU 30 communicate using the CAN protocol via the bus 300. CAN is an abbreviation for Controller Area Network and is a registered trademark.

[0027] The DCM 20 communicates with a server (not shown) and the like via a network. DCM is an abbreviation for Data Communication Module. The DCM 20 and the ECUs 30 and 70 communicate via a bus 310 using the Ethernet protocol. Ethernet is a registered trademark.

[0028] The ECUs 30, 70, and 90 are connected to each other via a bus 320 supporting a local network. The bus 320 is used for normal vehicle control.

[0029] ECU 30 and ECU 70 are connected via bus 330, and ECU 30 and ECU 90 are connected via bus 332. Buses 330 and 332 communicate using the CAN FD protocol. CAN FD stands for CAN with Flexible Data Rate. Buses 330 and 332 are not used for normal vehicle control but are used, for example, for data checking and fault diagnosis during communication between ECUs 30, 70, and 90.

[0030] In the present embodiment, a diagnostic request from an external tool or server as a fault diagnosis request source is transmitted to a fault diagnosis request destination such as the ECU 30 , 70 , 90 or the device 200 connected to the ECU 30 , 70 , 90 .

[0031] Furthermore, in the present embodiment, since the DLC 10 is connected to the ECU 30 , transmission of a diagnostic request from an external tool via the DLC 10 and transmission of a diagnostic result to the external tool via the DLC 10 are performed via the ECU 30 .

[0032] Furthermore, transmission of a diagnostic request from the server via the DCM 20 and transmission of a diagnostic result to the server via the DCM 20 are performed via the ECU 30 .

[0033] For example, when ECU 70 receives a diagnostic request from the server to ECU 90 via DCM 20 , ECU 70 does not send the diagnostic request to ECU 90 but sends the diagnostic request to ECU 30 . ECU 30 then sends the diagnostic request to ECU 90 .

[0034] When the diagnosis result is transmitted from the ECU 90 to the server, the ECU 90 does not transmit the diagnosis result to the ECU 70 but transmits the diagnosis result to the ECU 30. Then, the diagnosis result is transmitted from the ECU 30 to the ECU 70.

[0035] Transmission of a diagnostic request from the server to the ECU 70 via the DCM 20 and transmission of a diagnostic result from the ECU 70 to the server via the DCM 20 are also performed from the ECU 70 via the ECU 30 .

[0036] In the present embodiment, the diagnosis request and the diagnosis result transmitted via the DLC 10 and the DCM 20 are transmitted via the ECU 30 because only the ECU 30 is provided with a function of checking whether the diagnosis request or the diagnosis result is appropriate.

[0037] Each of ECUs 30, 70, and 90 includes one or more microcomputers equipped with a processor core, RAM, ROM, etc. Furthermore, each of ECUs 30, 70, and 90 is a gateway ECU, such as a domain ECU that manages groups categorized by function or a regional ECU that manages groups categorized by vehicle location.

[0038] Various devices 200 such as a control ECU and actuators are connected to each of the ECUs 30, 70, and 90. Each of the ECUs 30, 70, and 90 communicates with the devices 200 using, for example, the CAN protocol.

[0039] ECU 30 includes three processor cores 40, 50, and 60, ECU 70 includes one processor core 80, and ECU 90 includes two processor cores 100 and 110. The number of processor cores included in ECUs 30, 70, and 90 is an example and is not limited to the number shown.

[0040] like Figure 2 As shown, ECU 30 includes a shared memory 62 and a communication unit 64 in addition to multiple processor cores 40, 50, and 60. Communication unit 64 includes a communication controller and a communication switch corresponding to a communication protocol for ECU 30 to communicate with DLC 10, ECUs 70, 90, and device 200 of the ECU itself.

[0041] Although the number of processor cores of ECU70 and 90 is different, they are also Figure 2 The ECU 30 shown has the same structure.

[0042] In addition, if Figure 3 As shown, the processor core 40 generates multiple VMs 42, 44, and 46. VM is an abbreviation for virtual machine. Other processor cores 50, 60 and processor cores of other ECUs 70, 90 can also generate multiple VMs.

[0043] The processor cores 40, 50, and 60 communicate with each other via the shared memory 62 or the communication unit 64. The VMs 42, 44, and 46 communicate with each other via a virtual CAN bus, a virtual CAN FD bus, a virtual Ethernet bus, and the like.

[0044] like Figure 4 As shown, ECUs 30, 70, and 90 respectively function as communication determination units 32, 72, and 92 and communication setting units 34, 74, and 94. The functions of communication determination units 32, 72, and 92 and communication setting units 34, 74, and 94 are described in [1-2. Fault diagnosis process] below.

[0045] [1-2. Fault diagnosis and treatment]

[0046] The fault diagnosis process described below is executed by ECUs 30, 70, and 90. The processor core of each ECU in which the fault diagnosis process is executed, and further, the VM in which the fault diagnosis process is executed when any of the processor cores generates a VM, is preset or appropriately determined according to processing conditions.

[0047] (1) Packaging

[0048] (1-1) When a diagnostic request is received from DLC 10

[0049] When the ECU 30 receives communication from the DLC 10 via the bus 300, Figure 6 In S400 , the communication determination unit 32 determines whether the current communication has an ECU other than the own ECU as a destination.

[0050] When communication is performed from the DLC 10 via the bus 300 , the communication determination unit 32 determines whether the current communication is destined for an ECU other than the own ECU based on the ID of the received CAN frame.

[0051] If the determination in S400 is "NO", that is, if the current communication does not have an ECU other than the own ECU as a destination, the process proceeds to S412.

[0052] If the determination in S400 is "yes," in S402, the communication determination unit 32 determines whether the current communication is fault diagnosis communication based on the value of data at a predetermined position in the data field of the received CAN frame. In this case, the communication determination unit 32 functions as a first communication determination unit.

[0053] If the determination in S402 is "NO", that is, if the current communication is not fault diagnosis communication, the process proceeds to S412.

[0054] If the determination in S402 is "Yes," meaning that the current communication is fault diagnosis communication, in S404, the communication determination unit 32 determines whether a communication protocol conversion is necessary for the current communication. If the determination in S404 is "No," meaning that a communication protocol conversion is not necessary for the current communication, the process proceeds to S412.

[0055] When the ECU 30 receives a diagnostic request from the DLC 10 and the destination is an ECU 70 or 90 other than the ECU 30, the communication protocol is converted to transmit the CAN frame received from the DLC 10 to the buses 330 or 332. Therefore, the determination in S404 is "YES".

[0056] If the determination in S404 is "yes," that is, if the communication protocol needs to be converted in this communication, the communication determination unit 32 determines in S406 whether predetermined conditions for executing the encapsulation process are met.

[0057] (a) An external fault diagnosis tool is connected to the DLC 10.

[0058] (b) The vehicle is stopped by either the manual parking gear or the side brake or the electric parking brake.

[0059] (c) When the vehicle includes an electric motor as a driving source, the rechargeable battery that supplies power to the electric motor is being charged.

[0060] (d) The vehicle has an internal combustion engine and is being refueled.

[0061] (e) In the bus currently being used, the amount of communication other than the fault diagnosis communication is below a prescribed amount, and the fault diagnosis communication does not interfere with other communications.

[0062] If the determination in S406 is "No," that is, if none of the predetermined conditions (a) to (e) for executing the encapsulation process is satisfied, the process proceeds to S412.

[0063] If any one of the predetermined conditions (a) to (e) for executing the encapsulation process is satisfied, the determination in S404 is "Yes".

[0064] In this case, in S408, if Figure 5 As shown, the communication setting unit 34 encapsulates the received CAN frame into the data field of the CAN FD frame of the CAN FD protocol, which has a communication speed faster than the CAN protocol. In this case, the communication setting unit 34 functions as the first communication setting unit.

[0065] When the ECU 30 receives a diagnostic request from the DLC 10 in a CAN frame, the CAN frame ID is 0x7XX. The communication setup unit 34 retains the CAN frame ID received from the DLC 10 as 0x7XX and encapsulates it into a CAN FD frame. In this case, the communication setup unit 34 changes the CAN FD ID from 0x7XX, which was set as the CAN frame ID, to 0x0XX, thereby increasing the communication priority.

[0066] Then, in S410 , the communication setting unit 34 transmits the CAN FD frame encapsulating the CAN frame to the bus 330 or the bus 332 used this time.

[0067] In S412, if normal protocol conversion is required for the received communication frame, the communication setting unit 34 performs protocol conversion. If not, protocol conversion is not performed, normal communication is performed by sending communication frames of the corresponding communication protocol, and this processing ends.

[0068] In the process of S412, the so-called normal protocol conversion means analyzing the content of the received communication frame and reorganizing it into the structure of the communication frame corresponding to the transmitted communication protocol.

[0069] (1-2) When a diagnostic request is received from DCM20

[0070] When the ECU 70 receives data from the DCM 20 via the bus 310, Figure 6 In S400 , the communication determination unit 72 determines whether the current communication has an ECU other than the own ECU as a destination based on the destination MAC address of the Ethernet frame.

[0071] If the determination in S400 is “NO”, that is, if the current communication does not have an ECU other than the own ECU as a destination, the communication determination unit 72 moves the process to S412 .

[0072] If the determination in S400 is "yes," in S402, the communication determination unit 72 determines whether the current communication is fault diagnosis communication based on the value of data at a predetermined position in the data field of the received Ethernet frame. In this case, the communication determination unit 72 functions as a first communication determination unit.

[0073] If the determination in S402 is "NO", that is, if the current communication is not fault diagnosis communication, the process proceeds to S412.

[0074] If the determination in S402 is "Yes," meaning that the current communication is fault diagnosis communication, in S404, the communication determination unit 72 determines whether a communication protocol conversion is necessary for the current communication. If the determination in S404 is "No," meaning that a communication protocol conversion is not necessary for the current communication, the process proceeds to S412.

[0075] For example, when a diagnostic request from DCM 20 is transmitted from ECU 70 to ECU 90 via ECU 30 or when a diagnostic request is transmitted from ECU 70 to ECU 70 via ECU 30, the communication protocol remains unchanged to CAN FD in ECU 30. In this case, the determination in S404 is "NO".

[0076] If the determination in S404 is "Yes," that is, if communication protocol conversion is required for this communication, in S406, communication determination unit 72 determines whether the aforementioned predetermined conditions for executing the encapsulation process are met. Furthermore, communication determination unit 72 determines, under the aforementioned predetermined condition (e), whether the amount of communication other than fault diagnostic communication is below a predetermined amount on bus 330 connecting ECU 30 and ECU 70.

[0077] If the determination in S406 is "No," that is, if the predetermined condition for executing the encapsulation process is not satisfied, the process proceeds to S412.

[0078] If the determination in S406 is "yes", that is, if the prescribed conditions for executing the encapsulation process are met, then in S408, Figure 5 As shown, the communication setting unit 74 encapsulates the CAN frame used in the diagnostic request into the data field of the CAN FD frame. In this case, the communication setting unit 74 functions as a first communication setting unit.

[0079] Because the ECU 70 did not receive the CAN frame used in the diagnostic request from the DCM 20, the communication setup unit 74 generates a CAN frame with the ID set to 0x7XX and encapsulates it into the data field of the CAN FD frame. At this time, the communication setup unit 74 changes the CAN FD ID from 0x7XX, which was set as the CAN frame ID, to 0x0XX, thereby increasing the communication priority.

[0080] In S410 , the communication setting unit 74 transmits the CAN FD frame encapsulating the CAN frame to the bus 330 used this time.

[0081] In S412 , the communication setting unit 74 executes the above-described normal communication and ends the present process.

[0082] (1-3) When the diagnostic result from the ECU or the device 200 of the ECU is sent

[0083] When transmitting the diagnosis result received from the device 200 connected to the ECU 30 or the diagnosis result of the ECU itself, Figure 6 In S400 , the communication determination unit 32 determines whether the current communication has an ECU other than the own ECU as a destination.

[0084] When the diagnosis result of the own ECU is to be transmitted, the communication determination unit 32 determines whether an ECU other than the own ECU is to be transmitted as the destination.

[0085] In contrast, when communication is performed from the device 200 connected to the own ECU, the communication determination unit 32 determines whether the current communication is destined for an ECU other than the own ECU based on the ID of the CAN frame received from the device 200 .

[0086] In the case of the ECU 30, when the ECU itself or the device 200 connected to the ECU transmits the diagnostic result in response to the diagnostic request from the DLC 10, the DLC 10 is the destination, and therefore other ECUs are not the destinations. In this case, the determination in S400 is "NO".

[0087] On the other hand, in response to the diagnosis request from the DCM 20, the destination to which the ECU 30 or the device 200 connected to the ECU transmits the diagnosis result is the ECU 70, which is another ECU. In this case, the determination in S400 is "YES".

[0088] In the case of ECUs 70 and 90, when the diagnostic request from DLC 10 or the diagnostic request from DCM 20 is transmitted by the ECU itself or the device 200 connected to the ECU itself, in this embodiment, the diagnostic result is temporarily transmitted via ECU 30. Therefore, ECU 30 is the destination as the other ECU, and the determination in S400 is "YES".

[0089] If the determination in S400 is "NO", that is, if the destination of this communication is not an ECU other than the own ECU, the process proceeds to S412.

[0090] If the determination in S400 is "Yes," meaning the destination of this communication is an ECU other than the current ECU, the communication determination unit 32, 72, or 92 determines in S402 whether this communication is fault diagnostic communication. In this case, the communication determination unit 32, 72, or 92 functions as a second communication determination unit. If the determination in S402 is "No," meaning this communication is not fault diagnostic communication, the process proceeds to S412.

[0091] If the determination in S402 is "Yes," meaning that the current communication is fault diagnosis communication, in S404, the communication determination unit 32, 72, or 92 determines whether a communication protocol conversion is necessary for the current communication. If the determination in S404 is "No," meaning that a communication protocol conversion is not necessary for the current communication, the process proceeds to S412.

[0092] Furthermore, when the diagnostic results are transmitted from the ECU or the device 200 of the ECU to another ECU, the communication protocol is converted in order to transmit the CAN frame containing the diagnostic results to the buses 330 and 332 using the CAN FD protocol. In this case, the determination in S404 is "YES."

[0093] If the determination in S404 is "Yes," meaning that the communication protocol conversion is necessary for this communication, the communication determination unit 32, 72, or 92 determines in S406 whether the aforementioned predetermined conditions for executing the encapsulation process are met. If the determination in S406 is "No," meaning that the predetermined conditions for executing the encapsulation process are not met, the process proceeds to S412.

[0094] If the determination in S406 is "Yes," that is, if the predetermined condition for executing the encapsulation process is satisfied, the communication setting unit 34, 74, or 94 executes the encapsulation process in S408. In this case, the communication setting unit 34, 74, or 94 functions as a second communication setting unit.

[0095] When transmitting the diagnosis result of the own ECU, the communication setting unit 34 , 74 , 94 generates a CAN frame and encapsulates the generated CAN frame into a CAN FD frame.

[0096] When the device 200 connected to the ECU transmits the diagnosis result, the communication setting unit 34, 74, 94 encapsulates the CAN frame received from the device 200 into a CAN FD frame. In this case, the communication setting unit 34, 74, 94 functions as a second communication setting unit.

[0097] In either case of encapsulating a CAN frame into a CAN FD frame, the CAN frame ID is 0x7XX. To increase the priority of communication, the CAN FD ID is set to 0x0XX.

[0098] Since the following processes of S410 and S412 are substantially the same as the processes of S410 and S412 in the case of transmitting the diagnostic request from the DLC 10 in (1-1) above, the description thereof will be omitted.

[0099] (2) Decapsulation processing

[0100] The following processing is executed in any of the ECUs 30 , 70 , and 90 , and is basically the same processing, so the description will be made using the ECU 30 as an example.

[0101] exist Figure 7 In S420 , the communication determination unit 32 determines whether the current communication is from another ECU.

[0102] If the determination in S420 is "NO", that is, if the current communication is not from another ECU, the process proceeds to S430.

[0103] If the determination in S420 is "YES", that is, if the current communication is from another ECU, in S422, the communication determination unit 32 determines whether the current communication is fault diagnosis communication. In this case, the communication determination unit 32 functions as a second communication determination unit.

[0104] The determination in S422 is "Yes" in any of the following cases (a) to (c), for example.

[0105] (a) The ECU 70 , 90 receives a CAN FD frame indicating a diagnostic request for the ECU itself or the device 200 connected to the ECU from the DLC 10 or the DCM 20 via the ECU 30 .

[0106] (b) The ECU 30 receives, from the ECU 70 , a CAN FD frame indicating a diagnostic request from the DCM 20 to the ECU itself or the device 200 connected to the ECU itself.

[0107] (c) The ECU 30 receives a CAN FD frame indicating a diagnosis result in response to a diagnosis request from the DLC 10 from the ECUs 70 and 90 .

[0108] If the determination in S422 is “NO”, that is, if the CAN FD frame received from the other ECU is not a frame based on fault diagnosis communication, the communication determination unit 32 shifts the process to S430 .

[0109] If the determination in S422 is "Yes," meaning that the CAN FD frame received from the other ECU is a frame for fault diagnosis communication, then in S424, the communication determination unit 32 determines whether communication protocol conversion is necessary for this communication. If the determination in S424 is "No," meaning that communication protocol conversion is not necessary for this communication, the process proceeds to S430.

[0110] For example, when the diagnosis result is transmitted from the ECU 70 or the ECU 90 to the ECU 70 via the ECU 30 , the communication protocol in the ECU 30 remains CAN FD and is not converted, so the determination in S424 is “NO”.

[0111] If the determination in S424 is "yes", that is, if the communication protocol needs to be converted in this communication, then in S426, Figure 5 As shown, the communication setting unit 34 decapsulates the CAN frame from the received CAN FD frame. In this case, the communication setting unit 34 functions as a second communication setting unit. The ID of the decapsulated CAN frame is set to 0x7XX, which is the ID of the CAN frame encapsulated in the CAN FD frame.

[0112] In S428 , the communication setting unit 34 performs one of fault diagnosis in the own ECU based on the decapsulated CAN frame, transmitting the CAN frame to the device 200 connected to the own ECU, and transmitting the CAN frame to the DLC 10 , and ends this process.

[0113] In S430 , the communication setting unit 34 executes the above-described normal communication and ends this process.

[0114] In the first embodiment described above, the CAN protocol corresponds to the first communication protocol, the CAN frame corresponds to the first communication frame, the CAN FD protocol corresponds to the second communication protocol, and the CAN FD frame corresponds to the second communication frame.

[0115] In addition, the 0x7 portion indicating the priority in the ID of the CAN frame and the 0x0 portion indicating the priority in the ID of the CAN FD frame correspond to the priority parameter.

[0116] In addition, ECUs 30 , 70 , 90 , processor cores 40 , 50 , 60 , 80 , 100 , 1106 , and VMs 42 , 44 , 46 correspond to a communication node, a first communication node, and a second communication node.

[0117] In addition, S402, S406, and S422 correspond to the processing of the communication determination unit, and the processing of S408, S410, S426, and S428 corresponds to the processing of the communication setting unit.

[0118] [1-3. Effect]

[0119] According to the first embodiment described above, the following effects can be obtained.

[0120] (1a) CAN frames, which are specified by the fault diagnosis communication standard, are encapsulated and transmitted within CAN FD frames, which are faster than the CAN protocol. This eliminates the need for a dedicated fault diagnosis communication bus and reduces the communication time required for fault diagnosis.

[0121] (1b) Since the CAN frame is encapsulated into the CAN FD frame instead of the usual protocol conversion, the time to generate the CAN FD frame from the CAN frame can be shortened.

[0122] (1c) When encapsulating CAN frames into CAN FD frames, the priority of communication based on CAN FD frames is given higher priority than that of communication based on CAN frames. This can suppress delays in fault diagnosis communication, thereby further reducing the communication time required for fault diagnosis.

[0123] [2. Second embodiment]

[0124] [2-1. Differences from the First Embodiment]

[0125] Since the basic structure of the second embodiment is the same as that of the first embodiment, the following describes the differences. In addition, the same reference numerals as those of the first embodiment represent the same structures, and reference is made to the previous description.

[0126] In the first embodiment described above, the ECUs 30, 70, and 90 include buses 330 and 332 that communicate using the CAN FD protocol. Figure 8 The second embodiment shown is different from the first embodiment in that the ECUs 30 , 70 , and 90 are connected via buses 312 and 314 that communicate using the Ethernet protocol, instead of the buses 330 and 332 .

[0127] Furthermore, the buses 312 and 314 may be used for a part of normal vehicle control in addition to data checking when the ECUs 30 , 70 , and 90 communicate with each other.

[0128] [2-2. Fault diagnosis and treatment]

[0129] (1) Packaging

[0130] (1-1) When a diagnostic request is sent from DLC10

[0131] In the following processing, the same process as described in <(1-1) When a diagnostic request is sent from the DLC 10 in the first embodiment> is executed. Figure 6 S400 to S406 and S412 are substantially the same processes, so the description of the corresponding processes is omitted.

[0132] exist Figure 6 In S408, Figure 5 As shown, the communication setting unit 34 encapsulates the received CAN frame into the data field of the Ethernet frame of the Ethernet protocol having a communication speed faster than the CAN protocol. In this case, the communication setting unit 34 functions as the first communication setting unit.

[0133] Then, in S410 , the communication setting unit 34 transmits the Ethernet frame encapsulating the CAN frame to the buses 312 and 314 connected to the destination ECU.

[0134] At this time, the communication setting unit 34 sets the priority corresponding to the priority indicated by 0x0XX set in the first embodiment to increase the priority of CAN FD in the PCP of the tag field of the Ethernet frame to increase the priority of communication.

[0135] (1-2) When sending a diagnostic request from DCM20

[0136] In the following processing, the same process as described in <(1-2) When a diagnostic request is sent from the DCM 20> of the first embodiment is executed. Figure 6 S400 to S406 and S412 are substantially the same processes, so the description of the corresponding processes is omitted.

[0137] exist Figure 6 In S408, Figure 5As shown in FIG. 1 , the communication setup unit 74 encapsulates the CAN frame used for the diagnostic request into the data field of the Ethernet frame. In this case, the communication setup unit 74 functions as the first communication setup unit. At this time, the communication setup unit 74 sets the priority corresponding to the priority indicated by 0x0XX, which is set to increase the priority of CAN FD in the first embodiment, in the PCP of the tag field of the Ethernet frame, thereby increasing the communication priority.

[0138] Then, in S410 , communication setting unit 74 transmits the Ethernet frame encapsulating the CAN frame to bus 312 , whether the fault diagnosis request destination is ECU 30 or the fault diagnosis request destination is ECU 70 or 90 .

[0139] This is because, as described above, since the ECU 30 is provided with only the function of checking whether the diagnosis request or the diagnosis result is appropriate, the appropriateness check of the fault diagnosis is performed in the ECU 30 .

[0140] (1-3) When the diagnostic results from this ECU or the device 200 connected to this ECU are sent

[0141] In the following processing, the same process as described in <(1-3) When the diagnosis result from the ECU or the device 200 connected to the ECU is transmitted> in the first embodiment is executed. Figure 6 S400 to S406 and S412 are substantially the same processes, so the description of the corresponding processes is omitted.

[0142] In S408, the communication setting unit 34, 74, 94 executes encapsulation processing. In this case, the communication setting unit 34, 74, 94 functions as a second communication setting unit.

[0143] When transmitting the diagnosis result of the own ECU, in S408 , the communication setting unit 34 , 74 , 94 generates a CAN frame and encapsulates the generated CAN frame into an Ethernet frame.

[0144] When the device 200 connected to the present ECU transmits the diagnosis result, in S408 , the communication setting unit 34 , 74 , 94 encapsulates the CAN frame received from the device 200 into an Ethernet frame.

[0145] As described above, the ID of the CAN frame used for fault diagnosis is 0x7XX. The communication setting unit 34 keeps the ID of the CAN frame at 0x7XX without changing it, and encapsulates it into an Ethernet frame.

[0146] At this time, the communication setting units 34 , 74 , and 94 set the priority corresponding to the priority indicated by 0x0XX set in the first embodiment to increase the priority of CAN FD in the PCP of the tag field of the Ethernet frame to increase the priority of communication.

[0147] Then, in S410 , the communication setting unit 34 , 74 , 94 transmits the Ethernet frame encapsulating the CAN frame to the bus 312 or the bus 314 to which the destination ECU is connected.

[0148] (2) Decapsulation processing

[0149] Since the process is substantially the same as the process of replacing CAN FD with Ethernet in <(2) Decapsulation Process> described in the first embodiment, the description thereof will be omitted.

[0150] In the second embodiment described above, CAN corresponds to the first communication protocol, the CAN frame corresponds to the first communication frame, the Ethernet protocol corresponds to the second communication protocol, and the Ethernet frame corresponds to the second communication frame.

[0151] In addition, the PCP of the tag field of the Ethernet frame corresponds to a priority parameter.

[0152] [2-3. Effect]

[0153] According to the second embodiment described above, substantially the same effects as those described in the effects (1a) to (1c) of the first embodiment described above where CAN FD is replaced by Ethernet can be obtained.

[0154] [3. Other Implementation Methods]

[0155] As mentioned above, although embodiment of this disclosure was described, this disclosure is not limited to the said embodiment, Various deformation|transformation can be made and it can be implemented.

[0156] (3a) In the above embodiment, the CAN FD protocol or the Ethernet protocol is used as a communication protocol having a communication speed faster than the CAN protocol, but the present invention is not limited thereto. For example, the CAN XL protocol may also be used.

[0157] (3b) In the above embodiment, when a CAN frame is encapsulated into a communication frame of a communication protocol having a communication speed faster than the CAN protocol, the priority of the priority parameter indicating the priority of the communication is increased. Conversely, the priority of the priority parameter indicating the priority of the communication may remain the same.

[0158] (3c) In the above-described embodiment, the process of encapsulating the first communication frame into the second communication frame is performed in both the fault diagnosis communication from the fault diagnosis request source to the request destination and from the fault diagnosis request destination to the request source, but the present invention is not limited to this. The process of encapsulating the first communication frame into the second communication frame may be performed only in one or the other of the communication paths from the fault diagnosis request source to the request destination or from the fault diagnosis request destination to the request source.

[0159] (3d) As long as the first communication frame can be encapsulated into the second communication frame, any communication node in the communication path from the fault diagnosis request source to the request destination and from the fault diagnosis request destination to the request source may perform the encapsulation process.

[0160] (3e) In the above-described embodiment, only the ECU 30 connected to the DLC 10 has the function of checking whether a diagnosis request or a diagnosis result is appropriate, but the present invention is not limited to this.

[0161] By also providing the ECU 70 connected to the DCM 20 with a function for checking whether a diagnostic request or a diagnostic result is appropriate, it is possible to transmit a diagnostic request from the ECU 70 and transmit a diagnostic result to the ECU 70 without going through the ECU 30. In this case, in the above-described embodiment, the ECU 70 needs to be connected to each of the ECUs 30 and 90 via a bus using the CAN FD protocol or the Ethernet protocol.

[0162] (3f) In the above embodiment, the CAN protocol is used as an example of the first communication protocol specified in the communication standard for fault diagnosis, but the present invention is not limited to this. If the communication standard for fault diagnosis is changed, the first communication protocol may be, for example, CAN FD or Ethernet. In this case, a second communication protocol having a faster communication speed than the CAN FD protocol or the Ethernet protocol is used.

[0163] (3g) In the above embodiment, fault diagnostic communication is performed not via bus 320 of the local network used for vehicle control, but via buses 330, 332 or buses 312, 314 for performing data checks when ECUs 30, 70, and 90 communicate with each other. Alternatively, buses 330, 332, 312, and 314 may be omitted and fault diagnostic communication may be performed via bus 320 used for vehicle control. In this case, the communication protocol used in bus 320 is a communication protocol having a communication speed at least faster than the CAN protocol.

[0164] (3h) In the above embodiment, the communication systems 2 and 4 are described as including three ECUs 30, 70, and 90. In this case, the number of ECUs relaying fault diagnostic communications is a maximum of three, as described in the second embodiment. However, the number of ECUs may be four or more. Furthermore, fault diagnostic communications may be relayed by four or more ECUs.

[0165] (3i) The communication systems 2 and 4 and the methods thereof described in the present disclosure may also be implemented by a special-purpose computer provided by a processor and a memory programmed to execute one or more functions embodied by a computer program.

[0166] Alternatively, the communication systems 2 and 4 and the methods thereof described in the present disclosure may be implemented by a dedicated computer provided with a processor constituted by one or more dedicated hardware logic circuits.

[0167] Alternatively, the communication systems 2, 4 and methods described in the present disclosure may be implemented by one or more special-purpose computers, each of which is composed of a combination of a processor and a memory programmed to perform one or more functions and a processor composed of one or more hardware logic circuits.

[0168] In addition, the computer program may be stored as a computer-executable instruction in a non-transitory tangible recording medium. The method of realizing the functions of each unit included in the communication systems 2 and 4 does not necessarily need to include software, and all functions may be realized using one or more hardware.

[0169] (3j) Multiple functions of one component in the above-mentioned embodiment may be realized by multiple components, or one function of one component may be realized by multiple components. In addition, multiple functions of multiple components may be realized by one component, or one function realized by multiple components may be realized by one component. In addition, part of the structure of the above-mentioned embodiment may be omitted. In addition, at least part of the structure of the above-mentioned embodiment may be added to or replaced with the structure of another above-mentioned embodiment.

[0170] (3k) In addition to the above-mentioned communication systems 2 and 4, the present disclosure can also be implemented in various forms such as a program for causing a computer to function as the communication system 2 and 4, a non-transitional physical recording medium such as a semiconductor memory recording the program, and a communication method.

Claims

1. A communication system comprising a plurality of communication nodes, wherein the plurality of communication nodes relay fault diagnosis communications of a diagnosis request and a diagnosis result between a fault diagnosis request source and a fault diagnosis request destination, Any one of the above communication nodes has: a communication determination unit configured to determine whether the current communication is the fault diagnosis communication; and The communication setting unit is configured to encapsulate the first communication frame of the first communication protocol specified in the communication standard for the fault diagnosis into the second communication frame of the second communication protocol if the communication determination unit determines that the communication is the fault diagnosis communication when a diagnostic request is sent from the request source to the request destination or when a diagnostic result is sent from the request destination to the request source, wherein: The communication speed of the second communication protocol is faster than the communication speed of the first communication protocol.

2. The communication system according to claim 1, wherein: If the communication node is a first communication node, the communication determination unit is a first communication determination unit, and the communication setting unit is a first communication setting unit, The first communication setting unit is configured to encapsulate the first communication frame into the second communication frame if the first communication determination unit determines that the communication is the fault diagnosis communication when sending the diagnosis request or when sending the diagnosis result. The other second communication nodes among the plurality of communication nodes that are not the first communication node include: a second communication determination unit configured to determine whether the current communication is the fault diagnosis communication; as well as The second communication setting unit is configured to decapsulate the first communication frame from the second communication frame if the second communication determination unit determines that the current communication is the fault diagnosis communication when sending the diagnosis request or when sending the diagnosis result.

3. The communication system according to claim 2, wherein: The second communication setting unit is configured to encapsulate the first communication frame into the second communication frame if the second communication determination unit determines that the communication is the fault diagnosis communication when sending the diagnosis request or when sending the diagnosis result. The first communication setting unit is configured to decapsulate the first communication frame from the second communication frame if the first communication determination unit determines that the current communication is the fault diagnosis communication when sending the diagnosis request or when sending the diagnosis result.

4. The communication system according to any one of claims 1 to 3, wherein: The communication setting unit is configured to increase the priority of the priority parameter indicating the priority of communication in the second communication frame when encapsulating the first communication frame in the second communication frame.

5. The communication system according to any one of claims 1 to 3, wherein: The communication setting unit is configured as follows: if the communication determination unit determines that the communication is the fault diagnosis communication, and at least one of the manual parking gear, the side gate and the electric parking brake is in a state to stop the vehicle, the first communication frame is encapsulated into the second communication frame.

6. The communication system according to any one of claims 1 to 3, wherein: The communication setting unit is configured to encapsulate the first communication frame into the second communication frame if the communication determination unit determines that the current communication is the fault diagnosis communication and an external tool for fault diagnosis is connected to the communication system as the request source for the fault diagnosis.

7. The communication system according to any one of claims 1 to 3, wherein: The communication setting unit is configured to encapsulate the first communication frame into the second communication frame if the communication determination unit determines that the current communication is the fault diagnosis communication and the vehicle has an electric motor as a driving source and a rechargeable battery supplying power to the electric motor is being charged.

8. The communication system according to any one of claims 1 to 3, wherein: The communication setting unit is configured to encapsulate the first communication frame into the second communication frame if the communication determination unit determines that the current communication is the fault diagnosis communication and the vehicle includes an internal combustion engine and is being refueled.

9. The communication system according to any one of claims 1 to 3, wherein: The communication setting unit is configured to encapsulate the first communication frame into the second communication frame if the communication determination unit determines that the current communication is the fault diagnosis communication and the amount of communication other than the fault diagnosis communication is less than a predetermined amount.

10. The communication system according to any one of claims 1 to 3, wherein: The above-mentioned first communication protocol is the CAN protocol.

11. The communication system according to any one of claims 1 to 3, wherein: At least one of the communication nodes is an electronic control device.

12. The communication system according to any one of claims 1 to 3, wherein: At least one of the communication nodes is a processor core.

13. The communication system according to any one of claims 1 to 3, wherein: At least one of the above communication nodes is a virtual machine.

Images