JP7735902B2 - Data Distribution System - Google Patents

Description

This disclosure relates to a data distribution system.

One example of a data distribution system is the remote diagnostic system disclosed in Patent Document 1. The remote diagnostic system includes a fault response center and an on-board LAN configured on a mobile object. The on-board LAN is equipped with sensors that acquire data indicating the status of devices that make up the mobile object, and an on-board server. The fault response center accesses the on-board server via the mobile communications network and acquires data indicating the status of the devices that make up the mobile object.

Japanese Patent Application Laid-Open No. 2003-163747

A possible data distribution system is one that includes a control device and a mobile diagnostic device installed in a mobile object, and a data center configured to be able to communicate wirelessly with the mobile diagnostic device. The mobile diagnostic device can collect data by receiving data correlated to mobile object failures from the control device. The mobile diagnostic device then distributes the collected data to the data center.

However, the control device may change its communication target to another client while sending data to the mobile diagnostic device. In this case, the mobile diagnostic device will no longer be able to collect data. This creates a problem for the data distribution system, as it can prevent data from being distributed from the mobile diagnostic device to the data center.

One disclosed objective is to provide a data distribution system that can prevent data distribution from being interrupted.

The data distribution system disclosed herein comprises:
a control device (10) mounted on a moving object and transmitting at least one data item related to a fault in the moving object;
a mobile diagnostic device (20) mounted on the mobile body, receiving data from a control device and distributing the data to a data center (300) provided outside the mobile body by wireless communication;
a diagnostic tool (200) that is provided outside the mobile body, performs fault diagnosis on the mobile body, and is configured to be capable of wireless communication with the data center;
The control device
a communication determination step (S140) of determining whether or not there is a communication request from the diagnostic tool while communicating with the mobile diagnostic device;
a first transmission step (S144) of transmitting data to the mobile diagnostic device when it is determined that there is no communication request;
a switching step (S22, S24) of switching the communication target of the control device from the mobile object diagnostic device to the diagnostic tool when it is determined that there is a communication request;
a second transmission step (S282) of transmitting data to the diagnostic tool instead of to the mobile diagnostic device when the communication target is switched to the diagnostic tool;
the mobile diagnostic device includes a first distribution step (S324) of distributing the received data to the data center by wireless communication when the communication target cannot be switched;
The diagnostic tool is characterized by comprising a second distribution step (S446) of distributing the received data to the data center by wireless communication when the communication target is switched.

In this way, when a communication request is received from the diagnostic tool, the data distribution system switches the control device's communication target from the mobile diagnostic device to the diagnostic tool. As a result, the mobile diagnostic device is unable to receive data from the control device and is unable to distribute data to the data center. However, when the data distribution system switches the communication target to the diagnostic tool, it transmits the data to the diagnostic tool. Then, when the communication target is switched, the data distribution system distributes the data received by the diagnostic tool to the data center via wireless communication. As a result, the data distribution system can prevent data distribution from being interrupted.

The various aspects disclosed in this specification employ different technical means to achieve their respective objectives. The reference symbols in parentheses in the claims and this section are intended to illustratively indicate the correspondence with the embodiments described below and are not intended to limit the technical scope. The objectives, features, and advantages disclosed in this specification will become clearer with reference to the detailed description that follows and the accompanying drawings.

1 is a block diagram showing a schematic configuration of a data distribution system according to an embodiment. 4 is a flowchart showing a transmission process of an ECU in the embodiment. 4 is a flowchart showing a process of changing an ECU in the embodiment. 10 is a flowchart illustrating a distribution process of OBC in an embodiment. 10 is a flowchart illustrating a diagnostic tool distribution process according to an embodiment. 10 is a flowchart illustrating a diagnostic tool distribution process according to the first modification. 10 is a flowchart illustrating a diagnostic tool distribution process according to Modification 2. 13 is a flowchart showing a diagnostic tool distribution process according to Modification 3.

Below, several embodiments for implementing the present disclosure will be described with reference to the drawings. In each embodiment, parts corresponding to matters described in the preceding embodiment may be assigned the same reference numerals, and duplicate explanations may be omitted. In each embodiment, when only a portion of the configuration is described, the other portions of the configuration can be applied by referring to the other previously described embodiments.

<Overall structure>
The overall configuration of the data distribution system will be described using Figure 1. The data distribution system distributes data correlated with a fault in a mobile object 100 to a data center 300. The data distribution system includes an ECU 10 and an OBC 20 mounted on the mobile object 100, and a diagnostic tool 200 provided outside the mobile object 100.

The mobile object 100 may be an automobile, train, aircraft, or the like. The automobile may be an automobile equipped with an internal combustion engine, an electric automobile or fuel cell vehicle without an internal combustion engine, or a so-called hybrid vehicle. The aircraft may be an airplane, helicopter, VTOL (vertical take-off and landing aircraft), eVTOL (electric vertical take-off and landing aircraft), or the like.

ECU is an abbreviation for Electronic Control Unit. OBC is an abbreviation for On Board Client. In Figure 1, the mobile unit is referred to as AUTM, the diagnostic tool as DIGT, and the data center as DATC. Also in Figure 1, the communication interface (communication IF) is referred to as CIF, the display as DIS, and the flash memory as FM. CPU is an abbreviation for Central Processing Unit. RAM is an abbreviation for Random Access Memory. ROM is an abbreviation for Read Only Memory.

<ECU>
As shown in FIG. 1 , the ECU 10 includes a CPU 11, a RAM 12, a ROM 13, a flash memory 14, a communication IF 15, and the like. The ECU 10 is configured to be able to communicate with clients such as the OBC 20 and other ECUs via a communication line, such as a two-wire differential system, and the communication IF 15. The ECU 10 is also configured to be able to communicate with a diagnostic tool 200. Therefore, the diagnostic tool 200 can be considered one of the clients. Furthermore, the ECU 10 is electrically connected to sensors provided in the vehicle 100 via, for example, a wire harness or a connector. The sensors output electrical signals indicating physical quantities correlated with the operation and control of the vehicle 100. The ECU 10 corresponds to a control device.

ECU 10 is configured to be able to acquire sensor data output by sensors. ECU 10 may be configured to be able to acquire sensor data from multiple sensors. ECU 10 may also be configured to be able to acquire sensor data from other ECUs.

The ECU 10 generates control data when the CPU 11 executes a program. The ECU 10 performs various controls on the mobile object 100 by outputting the control data to the controlled object. The ECU 10 also stores failure information in the flash memory 14 or the like that indicates the location and state of the failure when the mobile object 100 fails.

RAM 12 temporarily stores the calculation results of CPU 11, sensor data, etc. ROM 13 and flash memory 14 store programs executed by CPU 11, etc.

Sensor data and control data indicate information that correlates with the operation and control of the mobile object 100. By analyzing sensor data and control data, it is possible to predict malfunctions of the mobile object 100. Therefore, control data and sensor data can be said to be data that correlates with malfunctions of the mobile object 100. Hereinafter, when there is no need to distinguish between control data and sensor data, they will be simply referred to as data. Data can also be referred to as mobile object information, vehicle information, etc.

The ECU 10 distributes data to the data center 300 using the OBC 20 and the diagnostic tool 200. Therefore, it can be said that the ECU 10 distributes data via the OBC 20 and the diagnostic tool 200.

For this purpose, the ECU 10 transmits at least one piece of data via the communication IF 15. In other words, the ECU 10 may transmit multiple pieces of data. In this case, the ECU 10 transmits data to the OBC 20 and the diagnostic tool 200.

More specifically, when ECU 10 requests OBC 20 to distribute data, it transmits the data to OBC 20. In this case, OBC 20 can be said to be responsible for collecting data. It can also be said that OBC 20 is responsible for distributing data.

Furthermore, the ECU 10 can switch responsibility for data collection from the OBC 20 to the diagnostic tool 200. When the ECU 10 has the diagnostic tool 200 distribute data, it transmits data to the diagnostic tool 200. In this case, it can be said that the diagnostic tool 200 is responsible for data collection. It can also be said that the diagnostic tool 200 is responsible for data distribution. The transmission process of the ECU 10 will be explained later.

<OBC>
1 , the OBC 20 includes a CPU 21, a RAM 22, a ROM 23, a flash memory 24, a communication IF 25, etc. The OBC 20 receives data transmitted from the ECU 10 via the communication IF 25, etc. In other words, the OBC 20 collects data transmitted from the ECU 10. The data collected by the OBC 20 is sensor data and control data transmitted from the ECU 10. For this reason, it can be said that the OBC 20 can collect data that cannot be collected by a repair shop or a dealer of the mobile object 100.

In addition, when the CPU 21 executes a program, the OBC 20 distributes the received data to the data center 300 via wireless communication. The OBC 20 can be considered an electronic control device with diagnostic tool functionality. The communication IF 25 of the OBC 20 may include a wireless communication device, or the OBC 20 may include a wireless communication device separate from the communication IF 25. The OBC 20 corresponds to a mobile object diagnostic device.

The RAM 22 temporarily stores the calculation results and data of the CPU 21. The ROM 23 and flash memory 24 store programs executed by the CPU 21.

<Diagnostic tool>
As shown in FIG. 1 , the diagnostic tool 200 includes a CPU 210, a RAM 220, a ROM 230, a flash memory 240, a communication IF 250, a display 260, and the like. The diagnostic tool 200 is a device that performs fault diagnosis on a mobile object. The diagnostic tool 200 is provided outside the mobile object 100. The diagnostic tool 200 is configured to be detachable from the mobile object 100 via a communication line, a connector, and the like. The diagnostic tool 200 is a tool operated by an operator at a repair shop, a dealer, or the like. The diagnostic tool 200 is also a tool for reading out fault information held by the ECU 10.

The diagnostic tool 200 performs various controls by having the CPU 210 execute programs. The CPU 210, for example, receives fault information from the ECU 10 via the communication IF 250 and displays the fault information on the display 260. The fault information read by the diagnostic tool 200 is used to repair faults and improve the efficiency of maintenance of the vehicle 100. The diagnostic tool 200 receives fault information from the ECU 10 as part of normal processing. Receiving fault information from the ECU 10 is also referred to as diagnostic communication.

Furthermore, the diagnostic tool 200 is configured to be capable of wireless communication with the data center 300. The diagnostic tool 200 can also receive data transmitted from the ECU 10 via the communication IF 250 or the like. The diagnostic tool 200 distributes the received data to the data center 300 via wireless communication when the CPU 210 executes a program. The diagnostic tool 200 may include a wireless communication device in the communication IF 250, or may include a wireless communication device separate from the communication IF 250.

<Data Center>
The data center 300 is located outside the mobile object 100 and in a remote location. The data center 300 includes a computer equipped with a CPU, RAM, ROM, flash memory, a communication IF, etc., and a display capable of displaying various information. The data center 300 is configured to be capable of wireless communication with the OBC 20 and the diagnostic tool 200. The computer in the data center 300 can collect data from multiple mobile objects 100. The computer in the data center 300 can also collect data from multiple mobile objects 100 simultaneously, or can collect data from multiple mobile objects 100 at different times. The collected data is used to predict vehicle failures and to build new services.

<Processing Operation>
First, the processing operation of the ECU 10 will be described with reference to Figures 2 and 3. Figures 2 and 3 show processing mainly executed by the CPU 11. The ECU 10 executes the flowchart of Figure 2 at predetermined time intervals. Note that, in this embodiment, as an example, an ECU 10 that transmits a plurality of data is employed.

In step S10, a data transmission setting request is received from the OBC. The ECU 10 receives a setting request to set data transmission conditions. The data transmission conditions are the conditions for transmitting data to the OBC 20. As will be explained later, the ECU 10 transmits only data that meets the set data transmission conditions.

In step S12, the data transmission conditions are set in accordance with the setting request. The ECU 10 sets the data transmission conditions in accordance with the setting request. Examples of data transmission conditions include when the vehicle speed reaches a certain value or when unauthorized access from outside the vehicle is detected. Note that the data transmission conditions may be determined in advance, or the data transmission conditions may not be set. In this case, the ECU 10 can omit steps S10 and S12. The ECU 10 can also omit steps S142 and S146, which will be described later.

In step S14, data transmission conditions are monitored. The ECU 10 performs a loop process to monitor whether the data transmission conditions are met. In other words, the ECU 10 repeatedly performs steps S140 to S146.

In step S140, it is determined whether a request has been received from the diagnostic tool 200 (communication determination step). The ECU 10 determines whether a communication request (communication request) has been received from the diagnostic tool 200. In other words, the ECU 10 determines whether to interrupt data transmission to the OBC 20 and switch the communication partner from the OBC 20 to the diagnostic tool 200. It can also be said that the ECU 10 determines whether or not there is a communication request from the diagnostic tool 200 while communicating with the OBC 20.

If the ECU 10 determines that it has not received a communication request, it does not interrupt data transmission to the OBC 20 and does not assume that the communication partner will be switched from the OBC 20 to the diagnostic tool 200, and proceeds to step S142. On the other hand, if the ECU 10 determines that it has received a communication request, it interrupts data transmission to the OBC 20 and assumes that the communication partner will be switched from the OBC 20 to the diagnostic tool 200, and proceeds to step S20.

The ECU 10 communicates with one client with a high priority. In other words, the ECU 10 does not transmit data to both the OBC 20 and the diagnostic tool 200 simultaneously, so data transmission to the OBC 20 may be interrupted.

A situation in which the diagnostic tool 200 and the OBC 20 attempt to communicate with the ECU 10 at the same time can occur when the timing at which the ECU 10 sends data to the OBC 20 coincides with the timing at which the diagnostic tool 200 sends fault information to the data center 300. Also, a case in which the diagnostic tool 200 and the OBC 20 communicate with the same ECU 10 at the same time can occur when some operation is performed on an individual vehicle using the diagnostic tool 200 and the results are collected in the data center 300 via the OBC 20. Note that this assumes that the diagnostic tool 200 has a higher priority than the OBC 20.

While ECU 10 is transmitting data to OBC 20, it may receive a request (communication request) from diagnostic tool 200 to transmit fault information. In this case, ECU 10 compares the priority of BC 20 with the priority of diagnostic tool 200. Then, ECU 10 interrupts data transmission to OBC 20 and switches its communication partner from OBC 20 to diagnostic tool 200.

In step S142, it is determined whether the data transmission conditions are met (first transmission step). If the ECU 10 determines that the data transmission conditions are met, it proceeds to step S144; if it does not determine that the data transmission conditions are met, it proceeds to step S146. In other words, if the ECU 10 does not determine that the data transmission conditions are met, it proceeds to step S146 without performing step S144. The data transmission conditions are not particularly limited. Note that the data transmission conditions do not have to be set. In other words, if the ECU 10 determines NO in step S140, it may execute step S144.

In step S144, data is transmitted to the OBC (first transmission step). The ECU 10 transmits data to the OBC 20 to have the OBC 20 distribute the data to the data center 300. In other words, the ECU 10 transmits data to the OBC 20 to be distributed to the data center 300. At this time, the responsibility for collecting the data lies with the OBC 20.

In step S146, it is determined whether the transmission termination condition is met. If the ECU 10 determines that the termination condition is met, it terminates the flowchart in Figure 2, but if it determines that the termination condition is not met, it returns to step S14. The termination condition may be, for example, that transmission of predetermined data has been completed.

Here, the process of changing the data transmission destination in step S20 will be explained using Figure 3. If the ECU 10 determines YES in step S140, it proceeds to step S20. In step S20, the data transmission destination is changed from the OBC 20 to the diagnostic tool 200.

In step S22, the OBC is notified of the suspension of data transmission (switching step). When switching the communication target from the OBC 20 to the diagnostic tool 200, the ECU 10 notifies the OBC 20 of the suspension of data transmission. Note that the communication target can also be referred to as the data transmission target. The communication target is also the client responsible for data distribution.

In step S24, the diagnostic tool is notified of the transfer of data distribution responsibility (switching step). When the ECU 10 determines that there is a communication request from the diagnostic tool 200, it switches the communication target from the OBC 20 to the diagnostic tool 200. At this time, the ECU 10 notifies the diagnostic tool 200 that it will begin transmitting data. In this way, the ECU 10 notifies the diagnostic tool 200 of the start of data transmission, thereby notifying the transfer of data distribution.

In step S26, data transmission to the diagnostic tool begins (second transmission step). The ECU 10 transmits data to the diagnostic tool 200 so that the diagnostic tool 200 can distribute the data to the data center 30.

In step S28, data transmission conditions are monitored (second transmission step). The ECU 10 performs a loop process to monitor whether the data transmission conditions are met. In other words, the ECU 10 repeatedly performs steps S280 to S284. Step S280 is the same as S142.

In step S282, data is transmitted to the diagnostic tool (second transmission step). The ECU 10 transmits data to the diagnostic tool 200 to have the diagnostic tool 200 distribute the data to the data center 30. In other words, the ECU 10 transmits data to the diagnostic tool 200 to be distributed to the data center 300. At this time, the diagnostic tool 200 is responsible for collecting the data. Note that data transmission conditions do not need to be set. In other words, the ECU 10 may execute step S282 after step S26. In this way, when the ECU 10 switches the communication target to the diagnostic tool 200, it transmits data to the diagnostic tool 200 instead of to the OBC 20. Note that step S284 is the same as S146.

Next, the distribution process of the OBC 20 will be described using Figure 4. The OBC 20 executes the process shown in the flowchart in Figure 3 in response to a data distribution request from the ECU 10. Furthermore, when the OBC 20 receives data from the ECU 10, it may execute the process from step S32 onwards.

In step S30, data is received from the ECU. The OBC 20 receives data from the ECU 10 to be distributed to the data center 300.

In step S32, the OBC 20 monitors for a data transmission stop notification from the ECU. The OBC 20 performs a loop process to monitor for a notification from the ECU 10 indicating that data transmission has been stopped.

In step S320, it is determined whether a data transmission stop notification has been received from the ECU. If OBC20 receives a notification indicating that data transmission is to be stopped, it proceeds to step S326; if not, it proceeds to step S322.

In step S322, the data is converted for distribution to the data center. OBC20 converts the received data for distribution to the data center.

In step S324, data is distributed to the data center (first distribution step). If the communication target cannot be switched, OBC20 distributes the received data to the data center 300 via wireless communication. In this embodiment, as an example, OBC20 is employed in which, unless a notification to stop transmission is received, it is assumed that the communication target cannot be switched and the data is distributed.

In step S326, data distribution is stopped. When OBC 20 receives a notification of the stop from ECU 10, it stops data distribution. Then, in step S328, it notifies the data center that data distribution has been stopped. OBC 20 notifies the data center 300 that data distribution from itself will be stopped.

Next, the distribution process of the diagnostic tool 200 will be described using Figure 5. The diagnostic tool 200 executes the process shown in the flowchart in Figure 5 in response to a communication request to the ECU 10.

In step S40, a request is sent to the ECU. The diagnostic tool 200 sends a communication request to the ECU 10.

In step S42, it is determined whether a data transmission delegation notification has been received from the ECU. If the diagnostic tool 200 determines that a data distribution delegation notification has been received from the ECU 10, it assumes that data distribution to the data center 300 will be performed and proceeds to step S44. On the other hand, if the diagnostic tool 200 does not determine that a data distribution delegation notification has been received from the ECU 10, it assumes that data distribution to the data center 300 will not be performed and proceeds to step S46.

In step S44, the diagnostic tool 200 monitors whether the data distribution conditions are met. The diagnostic tool 200 performs a loop process to monitor whether the data distribution conditions are met.

In step S440, data is received from the ECU. The diagnostic tool 200 receives data from the ECU 10 to be distributed to the data center 300.

In step S442, it is determined whether the data distribution conditions are met. The diagnostic tool 200 determines whether the data distribution conditions are met for the received data. If the diagnostic tool 200 determines that the data distribution conditions are met, it proceeds to step S444; if it does not determine that the conditions are met, it returns to step S44.

In this way, the diagnostic tool 200 does not distribute all data to the data center 300, but distributes data that meets specified data distribution conditions to the data center 300. In other words, the diagnostic tool 200 distributes filtered data that takes into account metadata such as whether the data should be distributed or the data priority. The metadata must be defined in advance. The data distribution conditions correspond to distribution conditions. There are no particular limitations on the data distribution conditions. An example of a data distribution condition will be explained later.

Note that data distribution conditions do not necessarily have to be set. In this case, the diagnostic tool 200 performs step S440 and then proceeds to step S444. Also, with regard to the OBC 20, only data for which the data distribution conditions are met may be distributed to the data center 300.

Step S444 is the same as step S322. In step S446, data is distributed to the data center (second distribution step). When the communication target is switched, the diagnostic tool 200 distributes the received data to the data center 300 via wireless communication. In other words, when the diagnostic tool 200 is notified of the start of data transmission, it assumes that the communication target has been switched and distributes the data. As an example, this embodiment employs a diagnostic tool 200 that distributes to the data center 300 only data for which the data distribution conditions are met from among the multiple pieces of data received.

In step S46, normal diagnostic communication processing with the ECU is performed. The diagnostic tool 200 performs diagnostic communication processing to receive fault information from the ECU 10. In this way, if the diagnostic tool 200 does not receive a delegation notification, it receives fault information for fault diagnosis rather than data to be distributed to the data center 300.

<Effects>
In this way, when a communication request is received from the diagnostic tool 200, the data distribution system switches the communication target of the ECU 10 from the OBC 20 to the diagnostic tool 200. As a result, the OBC 20 becomes unable to receive data from the ECU 10 and is unable to distribute data to the data center 300. However, when the communication target is switched to the diagnostic tool 200, the data distribution system transmits the data to the diagnostic tool 200. Then, when the communication target is switched, the data distribution system distributes the data received by the diagnostic tool 200 to the data center 300 via wireless communication. As a result, the data distribution system can prevent data distribution from being interrupted.

Incidentally, it is possible for the data distribution system to prevent data distribution from being interrupted by providing a redundant system for ECU 10 and constantly transmitting data to OBC 20. However, in this case, a redundant ECU is required, which increases the complexity of the software and the hardware costs. In contrast, in this embodiment, there is no need to provide a redundant ECU, so data distribution can be prevented from being interrupted while preventing the complexity of the software and the hardware costs from increasing.

The data distribution system may also queue data to be distributed to the data center 300 when the diagnostic tool 200 requests ECU 10 to communicate. In this case, when communication with the diagnostic tool 200 ends, ECU 10 distributes the queued data to the data center 300 via OBC 20. However, in this case, if the amount of data held in queue reaches an upper limit, the data may be discarded. In contrast, in this embodiment, there is no need to queue data to be sent to OBC 20, so data discarding can be prevented while preventing data distribution from being interrupted.

The above describes preferred embodiments of the present disclosure. However, the present disclosure is not limited to the above embodiments, and various modifications are possible without departing from the spirit of the present disclosure. Below, Modifications 1 to 3 are described as other aspects of the present disclosure. The above embodiments and Modifications 1 to 3 can be implemented independently, or in appropriate combinations. The present disclosure is not limited to the combinations shown in the embodiments, and can be implemented in various combinations.

(Variation 1)
The diagnostic tool 200 in Modification 1 will be described using FIG. 6. Modification 1 will be described mainly in terms of the differences from the above embodiment. Modification 1 differs from the above embodiment in the data distribution process to the data center 300. In particular, Modification 1 differs in the content of the loop process in step S44. Modification 1 employs batch processing. FIG. 6 mainly illustrates the differences from FIG. 5. For example, steps S40, S42, and S46 are omitted in FIG. 6.

In step S442a, it is determined whether the amount of received data is greater than the threshold. If the diagnostic tool 200 determines that the amount of received data is greater than the threshold, it considers that the data distribution conditions are met and proceeds to step S446. Note that in this modified example, step S444 may also be executed before step S466.

Furthermore, if the diagnostic tool 200 does not determine that the amount of received data is greater than the threshold, it considers that the data distribution conditions are not met and proceeds to step S448. In this way, the diagnostic tool 200 queues the data received from the ECU 10 and accumulates it to a certain extent before transferring it to the data center 300. For example, the diagnostic tool 200 is equipped with a transmission buffer, and temporarily stores the data in that transmission buffer.

In this way, the diagnostic tool 200 sets in advance the amount of data to be distributed at one time, and distributes the data when the amount of data received from the ECU 10 reaches the set amount. In other words, in this variant example 1, the data distribution condition is that the amount of received data exceeds a threshold.

In step S448, it is determined whether the distribution termination condition is met. If the diagnostic tool 200 determines that the distribution termination condition is met, it ends the flowchart in FIG. 6; if it determines that the condition is not met, it returns to step S44. The distribution termination condition may be, for example, that the transmission of predetermined data has been completed. Step S448 may also be omitted. Step S448 may also be added to the above embodiment.

The data distribution system of variant 1 can achieve the same effects as the above-described embodiment. Furthermore, the data distribution system of variant 1 can reduce the number of communications between the diagnostic tool 200 and the data center 300. Note that variant 1 can also be applied to the OBC 20. In this case, the data distribution system of variant 1 can reduce the number of communications between the OBC 20 and the data center 300.

(Variation 2)
The diagnostic tool 200 in Modification 2 will be described using FIG. 7. Modification 2 will be described mainly in terms of differences from the above embodiment. Modification 2 differs from the above embodiment in the data distribution process to the data center 300. Modification 2 employs online processing. For example, steps S40, S42, and S46 are omitted in FIG. 7.

The diagnostic tool 200 receives data from the ECU 10 (S440). The diagnostic tool 200 then distributes the received data to the data center 300 (S446). At this time, the diagnostic tool 200 transmits the received data to the data center 300 in the background while receiving data from the ECU 10. The diagnostic tool 20 repeatedly executes S440 and S446 until the distribution termination condition is met (S448).

In this modified example, step S444 may also be executed before step S466. In this way, the diagnostic tool 200 distributes data to the data center 300 each time it receives data from the ECU 10. In other words, this modified example adopts the reception of a certain amount of data as a data distribution condition.

The data distribution system of Variation 2 can achieve the same effects as the above embodiment. Furthermore, the data distribution system of Variation 2 can reduce the transmission buffer in the diagnostic tool 200 more than Variation 1. Note that Variation 1 can also be applied to OBC 20. In this case, the data distribution system of Variation 1 can reduce the transmission buffer in OBC 20 more than Variation 1.

(Variation 3)
The diagnostic tool 200 in Modification 3 will be described using FIG. 8. Modification 3 will be described mainly in terms of the differences from the above embodiment. Modification 3 differs from the above embodiment in the data distribution process to the data center 300. In particular, Modification 3 differs in the content of the loop process in step S44. FIG. 8 mainly illustrates the differences from FIG. 5. For example, steps S40, S42, and S46 are omitted in FIG. 8.

The ECU 10 distributes multiple pieces of data with different priorities to the data center 300. Therefore, the diagnostic tool 200 receives multiple pieces of data with different priorities. Each piece of data includes priority information, such as information indicating the priority and information linked to the priority. The diagnostic tool 200 can determine the priority of the received data based on the priority information. Note that if the priority information is linked to a priority, the diagnostic tool 200 associates a priority with each piece of priority information and stores it in advance in the ROM 230 or flash memory 240. Therefore, the diagnostic tool 200 can determine the priority of the received data by checking the contents stored in the ROM 230 or flash memory 240. Furthermore, each piece of data may include information indicating high or low priority as priority information.

In step S442b, it is determined whether high priority data has been received. The diagnostic tool 200 determines whether the priority of the received data is high priority. If the diagnostic tool 200 determines that the data is high priority, it proceeds to step S444; if it does not determine that the data is high priority, it proceeds to step S442c.

If the priority information indicates a priority or is linked to a priority, the diagnostic tool 200 checks the priority information of the received data and the contents stored in the ROM 230 and flash memory 240. By checking, the diagnostic tool 200 determines the priority of the received data. The diagnostic tool 200 compares the determined priority with a priority threshold (predetermined value), and if the priority exceeds the priority threshold, determines the data to be high priority, and if it does not, determines the data to be low priority. Furthermore, if the priority information indicates high priority or low priority, the diagnostic tool 200 determines whether the received data is high priority or low priority based on the priority information of the data. In other words, if the priority information of the received data is high priority, the diagnostic tool 200 considers the data to have a priority exceeding the predetermined value.

In step S442c, low-priority data is discarded. The diagnostic tool 200 discards low-priority data received from the ECU 10 that is not to be distributed to the data center 300.

The data distribution system of Variation 3 can achieve the same effects as the above-described embodiments. Furthermore, the data distribution system of Variation 3 can reduce the amount of data transmitted by the diagnostic tool 200 compared to when all received data is transmitted. Variation 3 can also be applied to the OBC 20. In this case, the data distribution system of Variation 3 can reduce the amount of data transmitted by the OBC 20 compared to the above-described embodiments and other variations.

While the present disclosure has been described with reference to embodiments, it is understood that the present disclosure is not limited to those embodiments or structures. The present disclosure also encompasses various modifications and variations within the scope of equivalents. In addition, while various combinations and forms are shown in the present disclosure, other combinations and forms including only one element, more, or less are also within the scope and spirit of the present disclosure.

10...ECU, 11...CPU, 12...RAM, 13...ROM, 14...Flash memory, 15...Communication IF, 20...OBC, 21...CPU, 22...RAM, 23...ROM, 24...Flash memory, 25...Communication IF, 100...Mobile object, 200...Diagnostic tool, 210...CPU, 220...RAM, 230...ROM, 240...Flash memory, 250...Communication IF, 260...Display, 300...Data center

Claims (8)

a control device (10) mounted on a moving object and transmitting at least one data item related to a fault in the moving object;
a mobile body diagnostic device (20) mounted on the mobile body, receiving the data from the control device and distributing the data to a data center (300) provided outside the mobile body by wireless communication;
a diagnostic tool (200) that is provided outside the mobile body, performs fault diagnosis on the mobile body, and is configured to be capable of wireless communication with the data center;
The control device
a communication determination step (S140) of determining whether or not there is a communication request from the diagnostic tool while communicating with the mobile diagnostic device;
a first transmission step (S144) of transmitting the data to the mobile object diagnostic device when it is determined that there is no communication request;
a switching step (S22, S24) of switching a communication target of the control device from the mobile object diagnostic device to the diagnostic tool when it is determined that there is a communication request;
a second transmission step (S282) of transmitting the data to the diagnostic tool instead of to the mobile diagnostic device when the communication target is switched to the diagnostic tool;
a first distribution step (S324) of the mobile diagnostic device distributing the received data to the data center by wireless communication when the communication target cannot be switched;
A data distribution system comprising a second distribution step (S446) in which the diagnostic tool distributes the received data to the data center by wireless communication when the communication target is switched. In the switching step, when the communication target is switched from the mobile diagnostic device to the diagnostic tool, the mobile diagnostic device is notified of the suspension of transmission of the data;
2. The data distribution system according to claim 1, wherein the mobile diagnostic device stops distributing the data when the notification of the stop is received. The data distribution system described in claim 2, wherein the mobile diagnostic device assumes that the communication target cannot be switched unless the notification of cancellation is received, and distributes the data in the first distribution step. In the switching step, when the communication target is switched from the mobile diagnostic device to the diagnostic tool, the diagnostic tool is notified of the start of transmission of the data;
A data distribution system according to any one of claims 1 to 3, wherein when the notification of the start is given, the diagnostic tool assumes that the communication target has been switched and distributes the data in the second distribution step. A data distribution system according to any one of claims 1 to 4, wherein in at least one of the first distribution step and the second distribution step, the received data is distributed when the amount of data received exceeds a threshold. A data distribution system according to any one of claims 1 to 4, wherein in at least one of the first distribution step and the second distribution step, the received data is distributed each time the data is received. the control device transmits a plurality of the data;
A data distribution system according to any one of claims 1 to 6, wherein in at least one of the first distribution step and the second distribution step, only the data for which the distribution conditions are met among the received multiple data are distributed to the data center. The plurality of data are associated with priorities;
8. The data distribution system according to claim 7, wherein in at least one of the first distribution step and the second distribution step, the distribution condition is deemed to be met if the priority exceeds a predetermined value.