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) that relay fault diagnosis communication of a diagnosis request and a diagnosis result between a request source and a request destination for fault diagnosis. The communication setting unit of the communication node increases the priority of a priority parameter indicating the priority of the communication if the communication determination unit determines that the communication is a failure diagnosis communication when the diagnosis request is transmitted or the diagnosis result is transmitted.

Description

Technical Field

[0001] The present disclosure relates to techniques for performing fault diagnosis communications. 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 fault diagnosis request source and a fault diagnosis request destination via a communication node such as a central gateway, such as a diagnostic tool connected to a DLC or a center that performs wireless communication with a DCM.

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

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

[0006] However, as a result of detailed studies by the inventors, it was found that if the number of communication nodes that relay communication on a 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] In order to reduce the communication time required for fault diagnosis communication, it is considered to perform fault diagnosis communication through a dedicated bus instead of a bus shared 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 is to provide a technology for reducing the communication time required for fault diagnosis communication without using a dedicated bus for fault diagnosis communication.

[0009] A communication system according to one embodiment of the present disclosure includes a plurality of communication nodes (30, 40, 42, 44, 46, 50, 60, 70, 80, 90, 100, 110) for relaying fault diagnosis communications of diagnosis requests and diagnosis results between a fault diagnosis request source and a fault diagnosis request destination.

[0010] Any one of the communication nodes includes a communication determination unit (32, 72, 92, S402, S404, S422) and a communication setting unit (34, 74, 94, S406, S408, S424, S426).

[0011] The communication determination unit determines whether this communication is fault diagnosis communication. The communication setting unit increases the priority of the priority parameter indicating the priority of the communication when the communication determination unit determines that this communication is fault diagnosis communication, either when the diagnosis request is sent from the request source to the request destination, or when the diagnosis result is sent from the request destination to the request source.

[0012] According to this configuration, the priority parameter indicating the priority of communication is increased in any of the plurality of communication nodes, so that the fault diagnosis communication can be preferentially executed. Thus, it is possible to reduce the communication time required for the fault diagnosis communication without providing a dedicated communication bus for fault diagnosis. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0014] Figure 2 This is a block diagram showing the configuration of the ECU.

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

[0016] Figure 4 It is a block diagram showing the functions of the ECU.

[0017] Figure 5 This is a schematic diagram showing the setting of the priority of the communication frame.

[0018] Figure 6 Detailed description of the flowchart of the fault diagnosis communication process.

[0019] Figure 7 Detailed description of the flowchart of the fault diagnosis communication process.

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

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

[0022] [1. First embodiment]

[0023] [1-1. Composition]

[0024] 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 is an abbreviation for an electronic control unit. The vehicle includes an internal combustion engine or an electric motor supplied with power from a rechargeable battery as a driving source. The internal combustion engine may also be used for power generation to supply power to the rechargeable battery.

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

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

[0027] The ECUs 30, 70, and 90 are connected to each other via a bus 320 corresponding to a partial network. The bus 320 is used in normal vehicle control.

[0028] ECUs 30, 70, and 90 are connected via bus 330. Communication is performed using the CAN protocol in bus 330. Bus 330 is not used in normal vehicle control, but is used for data checking and fault diagnosis when ECUs 30, 70, and 90 communicate with each other.

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

[0030] 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 an external tool via the DLC 10 are performed via the ECU 30 .

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

[0032] For example, when ECU 70 receives a diagnostic request to ECU 90 from the server via DCM 20 , ECU 70 sends the diagnostic request to ECU 30 instead of to ECU 90 . Then, ECU 30 sends the diagnostic request to ECU 90 .

[0033] When the diagnosis result is transmitted from the ECU 90 to the server, the ECU 90 transmits the diagnosis result to the ECU 30 instead of to the ECU 70 . Then, the diagnosis result is transmitted from the ECU 30 to the ECU 70 .

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

[0035] In the present embodiment, the reason why the diagnosis request and the diagnosis result are transmitted via the DLC 10 and the DCM 20 is to provide only the ECU 30 with a function of checking whether the diagnosis request or the diagnosis result is appropriate.

[0036] ECU30, 70, 90 each includes one or more microcomputers having a processor core, RAM, ROM, etc. ECU30, 70, 90 is a domain ECU that manages groups classified by function or a zone ECU that manages groups classified by vehicle position, etc., which are ECUs with high information processing capabilities.

[0037] Various devices 200 such as a control ECU and an actuator are connected to the ECUs 30, 70, and 90. The ECUs 30, 70, and 90 communicate with the devices 200 using, for example, the CAN protocol.

[0038] ECU 30 includes a plurality of, namely, 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 ECU 30, 70, and 90 is an example and is not limited to the number described.

[0039] like Figure 2 As shown, ECU 30 includes a shared memory 62 and a communication unit 64 in addition to a plurality of processor cores 40, 50, 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, ECU 70, 90, and device 200 of the ECU.

[0040] ECU70, 90 are also Figure 2 The ECU 30 shown has the same configuration, although the number of processor cores is different.

[0041] In addition, if Figure 3 As shown, the processor core 40 generates a plurality of 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 may also generate a plurality of VMs.

[0042] The processor cores 40, 50, and 60 communicate with each other via the shared memory 62 or the communication unit 64. In addition, 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.

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

[0044] [1-2. Fault diagnosis and processing]

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

[0046] (1) Priority Rising Process

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

[0048] 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 is destined for an ECU other than the own ECU.

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

[0050] 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 S410 .

[0051] 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, for example. In this case, the communication determination unit 32 functions as a first communication determination unit.

[0052] If the determination in S402 is NO, that is, if the current communication is not a fault diagnosis communication, the process proceeds to S410 .

[0053] If the determination in S402 is YES, that is, if the current communication is fault diagnosis communication, the communication determination unit 32 determines in S404 whether a predetermined condition for executing a priority raising process for raising the priority of the communication is satisfied. The predetermined conditions (a) to (e) are shown below.

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

[0055] (b) The vehicle is stopped by any one of the manual parking gear, the side brake, or the electric parking brake.

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

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

[0058] (e) In the bus used this time, 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.

[0059] If the determination in S404 is negative, that is, if none of the predetermined conditions (a) to (e) for executing the priority raising process is satisfied, the process proceeds to S410 .

[0060] If any one of the predetermined conditions (a) to (e) for executing the priority raising process is satisfied, the determination in S404 is YES.

[0061] If the determination in S404 is yes, in S406 the communication setting unit 34 sets Figure 5 As shown, the ID of the CAN frame received from the DLC 10 is changed from 0x7XX to 0x0XX to increase the priority of communication. In this case, the communication setting unit 34 functions as a first communication setting unit.

[0062] Then, in S408 , the communication setting unit 34 transmits the CAN frame with the communication priority raised to the bus 330 used this time.

[0063] In S410, the communication setting unit 34 performs normal communication on the received communication frame, performs protocol conversion if normal protocol conversion is required, and does not perform protocol conversion if not required, and transmits the communication frame of the corresponding communication protocol, and ends this process.

[0064] In the process of S410 , normal protocol conversion means analyzing the contents of the received communication frame and reorganizing it into a communication frame structure corresponding to the transmitted communication protocol.

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

[0066] 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 is destined for an ECU other than the own ECU based on the destination MAC address of the Ethernet frame.

[0067] 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 communication determination unit 72 shifts the process to S410.

[0068] 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, for example. In this case, the communication determination unit 72 functions as a first communication determination unit.

[0069] If the determination in S402 is NO, that is, if the current communication is not a fault diagnosis communication, the process proceeds to S410 .

[0070] If the determination in S402 is yes, that is, the communication this time is the fault diagnosis communication, the communication determination unit 72 determines in S404 whether the above-mentioned prescribed condition for executing the priority raising process is satisfied. In addition, the communication determination unit 72 determines in the above-mentioned prescribed condition (e) whether the communication volume other than the fault diagnosis communication is below the prescribed volume on the bus 330 connecting the ECU 30 and the ECU 70.

[0071] If the determination in S404 is NO, that is, if the predetermined condition for executing the priority raising process is not satisfied, the process proceeds to S410.

[0072] If the determination in step S404 is yes, that is, if the predetermined condition for executing the priority raising process is satisfied, in step S406 the communication setting unit 74 performs the following steps: Figure 5 As shown, the ID of the CAN frame is changed from 0x7XX set in the fault diagnosis to 0x0XX to increase the priority of communication. In this case, the communication setting unit 74 functions as a first communication setting unit.

[0073] In S408 , the communication setting unit 74 transmits the CAN frame with the communication priority raised to the bus 330 used this time.

[0074] In S410 , the communication setting unit 74 executes the above-mentioned normal communication and ends the present process.

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

[0076] 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 is destined for an ECU other than the own ECU.

[0077] When transmitting the diagnosis result of the own ECU, the communication determination unit 32 determines whether the destination is an ECU other than the own ECU.

[0078] On the other hand, in the case of communication from the device 200 connected to the own ECU, the communication determination unit 32 determines whether this communication is destined for another ECU other than the own ECU based on the ID of the CAN frame received from the device 200 .

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

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

[0081] In the case of ECU 70, 90, when the ECU or device 200 connected to the ECU sends a diagnosis result in response to a diagnosis request from DLC 10 or a diagnosis request from DCM 20, in this embodiment, the result is temporarily transmitted via ECU 30. Therefore, ECU 30 is the destination as another ECU, so the determination in S400 is YES.

[0082] 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 S410.

[0083] If the determination in S400 is yes, that is, the destination of this communication is another ECU other than the present ECU, in S402, the communication determination unit 32, 72, 92 determines whether this communication is fault diagnosis communication. In this case, the communication determination unit 32, 72, 92 functions as a second communication determination unit. If the determination in S402 is no, that is, the communication is not fault diagnosis communication, the process moves to S410.

[0084] If the determination in S402 is yes, that is, the communication is fault diagnosis communication, the communication determination unit 32, 72, 92 determines in S404 whether the above-mentioned predetermined conditions for executing the priority raising process are met. If the determination in S404 is no, that is, the predetermined conditions for executing the priority raising process are not met, the process moves to S410.

[0085] If the determination in S404 is YES, that is, if the predetermined condition for executing the priority raising process is satisfied, the communication setting unit 34, 74, 94 executes the priority raising process in S406. In this case, the communication setting unit 34, 74, 94 functions as a second communication setting unit.

[0086] When transmitting the diagnosis result of the own ECU, the communication setting unit 34, 74, 94 generates a CAN frame, and sets the ID of the generated CAN frame to 0x0XX instead of 0x7XX to increase the priority of communication.

[0087] When the device 200 connected to the present ECU transmits the diagnosis result, the communication setting unit 34 , 74 , 94 changes the ID of the CAN frame received from the device 200 from 0x7XX to 0x0XX to increase the priority of communication.

[0088] The following processes of S408 and S410 are substantially the same as the processes of S408 and S410 in the above-mentioned (1-1) when the diagnosis request is transmitted from the DLC 10 , and thus the description thereof is omitted.

[0089] (2) Priority reduction processing

[0090] 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.

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

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

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

[0094] For example, in any of the following cases (a) to (c), the determination in S422 is yes.

[0095] (a) The ECU 70 , 90 receives a CAN frame indicating a diagnosis 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 .

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

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

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

[0099] If the determination in S422 is YES, that is, if the CAN frame received from the other ECU is a CAN frame based on the fault diagnosis communication, the communication setting unit 34 in S424 Figure 5 As shown, the ID of the received CAN frame is set from 0x0XX to 0x7XX. As a result, the priority of communication is lowered. In this case, the communication setting unit 34 functions as a second communication setting unit.

[0100] In S426, the communication setting unit 34 performs a fault diagnosis on the own ECU based on the received CAN frame, sends the CAN frame to the device 20 connected to the own ECU, or sends the CAN frame to the DLC 10, and ends the present process.

[0101] In S428, the communication setting unit 34 executes the above-mentioned normal communication and ends the present process.

[0102] In the first embodiment described above, the portion 0x0 or 0x7 indicating the priority in the ID of the CAN frame corresponds to the priority parameter.

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

[0104] In addition, S402, S404, and S422 correspond to the processing of the communication determination unit, and the processing of S406, S408, S424, and S426 correspond to the processing of the communication setting unit.

[0105] [1-3. Effect]

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

[0107] (1a) Since the priority of communication based on CAN frames is increased by any communication node that relays fault diagnosis communication, delay in fault diagnosis communication can be suppressed. As a result, the communication time required for fault diagnosis can be further reduced.

[0108] [2. Second Embodiment]

[0109] [2-1. Differences from the first embodiment]

[0110] The basic structure of the second embodiment is the same as that of the first embodiment, so the following describes the differences. In addition, the same reference numerals as those of the first embodiment represent the same structure, and the previous description is referred to.

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

[0112] In addition, 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.

[0113] [2-2. Fault diagnosis and processing]

[0114] (1) Priority Rising Process

[0115] (1-1) When a diagnostic request is sent via DLC 10

[0116] In the following processing, the same processing as described in <(1-1) When a diagnostic request is sent via the DLC 10 in the first embodiment> is actually performed. Figure 6 Since the processing of S400~S404 and S410 is the same, the description of the corresponding processing is omitted.

[0117] exist Figure 6 In S406, the communication setting unit 34 converts the CAN frame received from the DLC 10 into an Ethernet frame by converting the communication protocol. At this time, the communication setting unit 34 increases the communication priority set for the PCP of the tag field as the priority parameter in the Ethernet frame compared to the communication priority indicated by 0x7XX set for the ID of the CAN frame. In this case, the communication setting unit 34 functions as a first communication setting unit.

[0118] Then, in S408 , the communication setting unit 34 transmits the Ethernet frame with the communication priority raised to the buses 312 , 314 connected to the destination ECU.

[0119] (1-2) When a diagnostic request is sent via DCM20

[0120] 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 actually executed. Figure 6 Since the processing of S400~S404 and S410 is the same, the description of the corresponding processing is omitted.

[0121] exist Figure 6 In S406, the communication setting unit 74 converts the CAN frame for the diagnostic request into an Ethernet frame by converting the communication protocol. At this time, the communication setting unit 74 sets the PCP of the tag field of the Ethernet frame to a priority corresponding to the priority indicated by 0x0XX of the CAN frame set in the first embodiment to increase the priority of the Ethernet frame, thereby increasing the priority of the communication. In this case, the communication setting unit 74 functions as the first communication setting unit.

[0122] Then, in S408 , the communication setting unit 74 transmits the Ethernet frame with the communication priority raised to the bus 312 in either the case where the fault diagnosis request destination is the ECU 30 or the case where the fault diagnosis request destination is the ECU 70 , 90 .

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

[0124] (1-3) When the diagnostic result is sent from the ECU or the device 200 connected to the ECU

[0125] In the following processing, the same processing as described in <(1-3) When the diagnosis result is transmitted from the ECU or the device 200 connected to the ECU> of the first embodiment is actually executed. Figure 6 Since the processing of S400~S404 and S410 is the same, the description of the corresponding processing is omitted.

[0126] In S406, the communication setting unit 34, 74, 94 executes the priority raising process. In this case, the communication setting unit 34, 74, 94 functions as a second communication setting unit.

[0127] When the diagnosis result of the own ECU is to be transmitted, in S406 the communication setting unit 34 , 74 , 94 generates a CAN frame and converts the generated CAN frame into an Ethernet frame.

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

[0129] At this time, the communication setting unit 34, 74, 94 sets the priority corresponding to the priority indicated by 0x0XX in the ID of the CAN frame to the PCP of the tag field of the Ethernet frame, thereby raising the priority of communication.

[0130] Then, in S408 , the communication setting unit 34 , 74 , 94 transmits the Ethernet frame whose communication priority is raised to the bus 312 or the bus 314 connected to the destination ECU.

[0131] (2) Priority reduction processing

[0132] Since the actual process is the same as the process after replacing CAN with Ethernet in <(2) Priority reduction process> described in the first embodiment, the description is omitted.

[0133] In the second embodiment described above, the PCP in the tag field of the Ethernet frame corresponds to the priority parameter.

[0134] [2-3. Effect]

[0135] According to the second embodiment described above, substantially the same effect as that described in the effect (1a) of the first embodiment described above in which CAN is replaced by Ethernet can be obtained.

[0136] [3. Other embodiments]

[0137] 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.

[0138] (3a) In the above-mentioned embodiment, the priority of the priority parameter indicating the priority of communication is increased in both the fault diagnosis communication from the fault diagnosis request source to the request destination and the fault diagnosis communication from the fault diagnosis request destination to the request source, but the present invention is not limited thereto. The priority of the priority parameter indicating the priority of communication may also be increased 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.

[0139] (3b) As long as the priority of the priority parameter is increased, the priority of the priority parameter can be increased by any communication node on the communication path from the fault diagnosis request source to the request destination and from the fault diagnosis request destination to the request source.

[0140] (3c) In the second embodiment described above, the Ethernet protocol is used in the buses 312 and 314 , but the present invention is not limited to this. The buses 312 and 314 may also use the CAN FD protocol.

[0141] In this case, in the priority increase process, the ID of the CAN FD protocol is set to 0x0XX, and in the priority decrease process, the ID of the CAN FD protocol is set to 0x7XX.

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

[0143] By also providing the ECU 70 connected to the DCM 20 with a function of checking whether the diagnostic request or the diagnostic result is appropriate, it is possible to send a diagnostic request from the ECU 70 and send a diagnostic result to the ECU 70 without passing through the ECU 30. In this case, in the above-mentioned second embodiment, the ECU 70 needs to be connected to the ECU 30 and 90 respectively via a bus of the Ethernet protocol.

[0144] (3e) In the above-mentioned embodiment, fault diagnosis communication is performed not through bus 320 of the partial network for vehicle control, but through bus 330 for performing data check when ECUs 30, 70, 90 communicate with each other, or through buses 312, 314. On the other hand, it is also possible to perform fault diagnosis communication through bus 320 for vehicle control without providing buses 330, 312, 314.

[0145] (3f) In the above-mentioned embodiment, the communication system 2 and 4 having three ECUs 30, 70, and 90 is described. In this case, the number of ECUs that relay the fault diagnosis communication is a maximum of three as shown in the second embodiment. In contrast, the number of ECUs may be four or more. Furthermore, the fault diagnosis communication may be relayed by four or more ECUs.

[0146] (3g) The communication systems 2 and 4 and the methods described in the present disclosure may also be implemented by a dedicated computer provided with a processor and a memory programmed to execute one or more functions embodied by a computer program.

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

[0148] Alternatively, the communication systems 2 and 4 and the methods described in the present disclosure may be implemented by one or more special-purpose computers including a processor programmed to execute one or more functions and a memory and a processor including one or more hardware logic circuits.

[0149] The computer program may be stored in a computer-readable non-portable tangible recording medium as instructions executed by the computer. The method for implementing 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 implemented using one or more hardware.

[0150] (3h) It is also possible to implement multiple functions of one component in the above-mentioned embodiment by multiple components, or to implement one function of one component by multiple components. In addition, it is also possible to implement multiple functions of multiple components by one component, or to implement one function implemented by multiple components by one component. In addition, a part of the structure of the above-mentioned embodiment may be omitted. In addition, at least a part of the structure of the above-mentioned embodiment may be added to or replaced by the structure of other above-mentioned embodiments.

[0151] (3i) 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-migrating physical recording medium such as a semiconductor memory recording the program, and a communication method.

[0152] [Technical ideas disclosed in this specification]

[0153] [Project 1]

[0154] A communication system is a communication system including a plurality of communication nodes (30, 40, 42, 44, 46, 50, 60, 70, 80, 90, 100, 110) for relaying a fault diagnosis request and a fault diagnosis result between a fault diagnosis request source and a fault diagnosis request destination.

[0155] Any one of the above communication nodes has:

[0156] a communication determination unit (32, 72, 92, S402, S404, S422) configured to determine whether the current communication is the above-mentioned fault diagnosis communication; and

[0157] The communication setting unit (34, 74, 94, S406, S408, S424, S426) is configured to increase the priority of the priority parameter indicating the priority of the communication 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.

[0158] [Project 2]

[0159] According to the communication system described in item 1,

[0160] If the communication node is set as the first communication node, the communication determination unit is set as the first communication determination unit, and the communication setting unit is set as the first communication setting unit, then

[0161] The first communication setting unit is configured to increase the priority of the priority parameter if the first communication determination unit determines that the communication is the fault diagnosis communication when the diagnosis request is sent or when the diagnosis result is sent.

[0162] The other second communication nodes among the plurality of communication nodes that are not the first communication node include:

[0163] A second communication determination unit is configured to determine whether the communication is the fault diagnosis communication; and

[0164] The second communication setting unit is configured to lower the priority of the priority parameter increased by the first communication setting unit when the second communication determination unit determines that the communication is the fault diagnosis communication, either when the diagnosis request is sent or when the diagnosis result is sent.

[0165] [Item 3]

[0166] According to the communication system described in item 2,

[0167] The second communication setting unit is configured to increase the priority of the priority parameter when the second communication determination unit determines that the communication is the fault diagnosis communication when the diagnosis request is sent or when the diagnosis result is sent.

[0168] The first communication setting unit is configured to reduce the priority of the priority parameter increased by the second communication setting unit if the first communication determination unit determines that the communication is the fault diagnosis communication when the diagnosis request is sent or when the diagnosis result is sent.

[0169] [Item 4]

[0170] A communication system according to any one of items 1 to 3,

[0171] The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and at least one of the manual parking device, the side brake and the electric parking brake is in a state of stopping the vehicle.

[0172] [Item 5]

[0173] A communication system according to any one of items 1 to 4,

[0174] The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and an external tool for the fault diagnosis is connected to the communication system as the request source for the fault diagnosis.

[0175] [Item 6]

[0176] A communication system according to any one of items 1 to 5,

[0177] The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and the vehicle includes an electric motor as a driving source and a rechargeable battery that supplies power to the electric motor is being charged.

[0178] [Item 7]

[0179] A communication system according to any one of items 1 to 6,

[0180] The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and the vehicle includes an internal combustion engine and is being refueled.

[0181] [Item 8]

[0182] A communication system according to any one of items 1 to 7,

[0183] The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and that an amount of communication other than the fault diagnosis communication is less than a predetermined amount.

[0184] [Item 9]

[0185] A communication system according to any one of items 1 to 8,

[0186] At least one of the communication nodes is an electronic control device.

[0187] [Item 10]

[0188] A communication system according to any one of items 1 to 9,

[0189] At least one of the communication nodes is a processor core.

[0190] [Item 11]

[0191] The communication system according to any one of items 1 to 10,

[0192] At least one of the above communication nodes is a virtual machine.

Claims

1. A communication system comprising a plurality of communication nodes, wherein the plurality of communication nodes relay fault diagnosis communication of a diagnosis request and a diagnosis result between a fault diagnosis request source and a fault diagnosis request destination, wherein: 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 increase the priority of the priority parameter indicating the priority of the communication 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.

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, then The first communication setting unit is configured to increase the priority of the priority parameter if the first communication determination unit determines that the communication is the fault diagnosis communication when the diagnosis request is sent or when the diagnosis result is sent. The other second communication nodes among the plurality of communication nodes that are not the first communication node include: A second communication determination unit is configured to determine whether the communication is the fault diagnosis communication; and The second communication setting unit is configured to lower the priority of the priority parameter increased by the first communication setting unit when the second communication determination unit determines that the communication is the fault diagnosis communication, either when the diagnosis request is sent or when the diagnosis result is sent.

3. The communication system according to claim 2, wherein: The second communication setting unit is configured to increase the priority of the priority parameter when the second communication determination unit determines that the communication is the fault diagnosis communication when the diagnosis request is sent or when the diagnosis result is sent. The first communication setting unit is configured to reduce the priority of the priority parameter increased by the second communication setting unit if the first communication determination unit determines that the communication is the fault diagnosis communication when the diagnosis request is sent or when the diagnosis result is sent.

4. The communication system according to claim 1, wherein: The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and at least one of the manual parking device, the side brake and the electric parking brake is in a state to stop the vehicle.

5. The communication system according to claim 1, wherein: The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and an external tool for the fault diagnosis is connected to the communication system as the request source for the fault diagnosis.

6. The communication system according to claim 1, wherein: The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and the vehicle includes an electric motor as a driving source and a rechargeable battery that supplies power to the electric motor is being charged.

7. The communication system according to claim 1, wherein: The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and the vehicle includes an internal combustion engine and is being refueled.

8. The communication system according to claim 1, wherein: The communication setting unit is configured to increase the priority of the priority parameter if the communication determination unit determines that the communication is the fault diagnosis communication and that an amount of communication other than the fault diagnosis communication is less than a predetermined amount.

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

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

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

Images