Data collection devices and methods

Abstract

To provide a device enables useful information to be provided from the vehicle to the external device according to needs of the external device while reducing a communication load and a processing burden of the external device.SOLUTION: A data collection device of the present disclosure is mounted on a vehicle and collects data on a state of the vehicle. The device acquires an aggregation format of the data from an external device and aggregates the data collected from the vehicle to generate an aggregation result in the aggregation format specified by the external device. The device sends the aggregation result to the external device.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to a data collection device and method that is mounted on a vehicle and collects a plurality of data related to the vehicle. [Background technology]

[0002] Conventionally, a data collection device is known that receives a data collection request from a terminal (external device) of a user such as a service provider, developer, or driver, collects data from an in-vehicle device based on the received collection request, and provides the collected data to the user (see, for example, Patent Document 1). This data collection device includes a reception unit that receives a collection request including collection conditions of target data to be collected from a user, a selection unit that selects a vehicle that satisfies the collection conditions received by the reception unit, a selection request transmission unit that transmits a selection request of a specified data type based on the collection conditions to the in-vehicle device of the vehicle selected by the selection unit, and a transmission request transmission unit that transmits a transmission request of the data selected based on the selection request. The in-vehicle device selected by the data collection device selects a data type that satisfies the collection condition based on the selection request from the data collection device, or starts recording data of the data type specified by the selection request. Then, the in-vehicle device transmits the selected data to the data collection device in response to a transmission request from a data collection server. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2020-038407 A Summary of the Invention [Problem to be solved by the invention]

[0004] A user of the conventional data collection device can specify information on the data type, information on the vehicle to be collected, the collection period, the upper limit of the collection amount, the collection area, etc., as collection conditions in a collection request. However, the data transmitted from the in-vehicle device to the data collection device is actual data acquired by a sensor, a camera, etc. connected to the in-vehicle device and index data (tag information) of the corresponding actual data. This makes it difficult to secure the amount of information while suppressing an increase in the data volume, and the communication load between the data collection device and the in-vehicle device becomes excessive. In addition, when utilizing the actual data from the in-vehicle device, it is necessary to perform some processing on the data on the external device side, which causes an excessive processing load on the external device.

[0005] Therefore, a main object of the present disclosure is to provide an external device from a vehicle with useful information that meets the needs of the external device while reducing the communication load and the processing load of the external device. [Means for solving the problem]

[0006] The data collection device disclosed herein is a data collection device that is mounted on a vehicle and collects data regarding the condition of the vehicle, obtains a compilation format for the data from an external device, aggregates the data collected from the vehicle to generate compilation results in the compilation format specified by the external device, and transmits the compilation results to the external device.

[0007] In addition, the data collection method disclosed herein is a data collection method for collecting data regarding the condition of a vehicle, which involves transmitting a data aggregation format for the data from an external device to the vehicle, aggregating the data collected from the vehicle on the vehicle side to generate an aggregation result in the aggregation format specified by the external device, and transmitting the aggregation result from the vehicle to the external device.

[0008] According to the data collection device and method disclosed herein, it is possible to provide an external device with useful information from a vehicle in response to the needs of the external device while reducing the communication load and the processing load of the external device. [Brief description of the drawings]

[0009] [Figure 1] 1 is a schematic configuration diagram showing a vehicle including a data collection device according to the present disclosure. [Diagram 2] 1 is an explanatory diagram illustrating a communication frame used by a data collection device of the present disclosure. [Diagram 3] 1 is an explanatory diagram illustrating a plurality of counting conditions used by the data collection device of the present disclosure. [Figure 4] 5 is a flowchart illustrating an example of a data counting routine executed by the data collection device of the present disclosure. [Diagram 5] 10 is an explanatory diagram illustrating a new tally condition table acquired from an external device by the data collection device of the present disclosure; FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Next, an embodiment of the present disclosure will be described with reference to the drawings.

[0011] 1 is a schematic diagram showing a vehicle V including a data collection device of the present disclosure. The vehicle V shown in the figure is, for example, a hybrid vehicle including an engine (internal combustion engine), a motor generator, an inverter, a battery, etc., none of which are shown. As shown in the figure, the vehicle V includes a plurality of electronic control units (hereinafter referred to as "ECUs") 1, 2, 3, 4, ..., an in-vehicle communication device 20, and a compilation electronic control unit (hereinafter referred to as "compilation ECU") 30 that functions as the data collection device of the present disclosure.

[0012] Each of the multiple ECUs 1, 2, 3, 4, ... includes a microcomputer (not shown) having a CPU, ROM, RAM, an input / output interface, etc., all of which are not shown, and storage devices 1M, 2M, 3M, 4M, ... such as a non-volatile memory (NVRAM). In this embodiment, the ECU 1 comprehensively controls the entire vehicle. The ECU 2 controls the engine of the vehicle V. The ECU 3 controls an inverter that drives the motor generator of the vehicle V, etc. The ECU 4 manages the battery of the vehicle V.

[0013] The in-vehicle communication device 20 exchanges various information with external devices such as the management server 100 shown in Fig. 1 and terminals 150 (including mobile terminals) at vehicle dealerships and vehicle maintenance shops through high-speed data communication (packet communication) via wires or wirelessly. The aggregation ECU 30 includes a microcomputer (not shown) having a CPU, ROM, RAM, an input / output interface, etc., not shown, and a storage device 30M such as a non-volatile memory (NVRAM). The aggregation ECU 30 aggregates time-series data based on data acquired by each of the ECUs 1, 2, 3, 4, ..., to generate a plurality of aggregation results.

[0014] These ECUs 1, 2, 3, 4, ..., the in-vehicle communication device 20, and the compilation ECU 30 are connected to a shared communication line of the vehicle V, which is a CAN bus including two communication lines (wire harnesses) Lo and Hi. The multiple ECUs 1, 2, 3, 4, ..., the in-vehicle communication device 20, and the compilation ECU 30 exchange information (communication frames) with each other by CAN communication via the shared communication line. In this embodiment, the frame F of the CAN communication includes, as shown in Fig. 2, a data collection frame Ft in which data is stored by the ECUs 1, 2, 3, 4, ..., a diagnosis record frame Fd in which data for vehicle diagnosis and the like is mainly stored by the ECUs 1, 2, 3, 4, ..., and a general-purpose frame Ff in which any data is stored.

[0015] As shown in Fig. 1, the ECUs 1, 2, 3, 4, ... include data processing modules 1P, 2P, 3P, 4P, ... constructed by cooperation between the installed programs (software) and hardware such as a CPU, a ROM, and a RAM. The data processing modules 1P, 2P, 3P, 4P, ... acquire (detect or calculate) a plurality of data (physical quantities such as vehicle speed, engine speed, motor speed, and setting state, etc.) related to the state of the vehicle V assigned to each of them at a predetermined sampling period (e.g., several msec to several tens of msec). Furthermore, the data processing modules 1P, 2P, 3P, 4P, ... store the acquired data in a data collection frame Ft, a diagnosis record frame Fd, or a general-purpose frame Ff of a frame F of CAN communication at a predetermined timing. In addition, the data processing modules 1P, 2P, 3P, 4P, ... acquire multiple pieces of data regarding the condition of the vehicle V assigned to each of them at a reference recording period (e.g., 500 msec) longer than the sampling period, and store the acquired data in the diagnosis recording frame Fd of the CAN communication frame F as data for vehicle diagnosis.

[0016] 1, the compilation ECU 30 includes a compilation processing module 30P and a plurality of arithmetic modules 31, 32, ..., 3n constructed by cooperation between an installed program (software) and hardware such as a CPU, a ROM, and a RAM. The compilation processing module 30P of the compilation ECU 30 receives (acquires) data stored by the ECUs 1, 2, 3, 4, ... from a data collection frame Ft of a frame F of CAN communication, and stores the data in the storage device 30M as time-series data (history information). The compilation processing module 30P also receives (acquires) data stored by the ECUs 1, 2, 3, 4, ... from a diagnosis record frame Fd of a frame F of CAN communication, and stores the data in the storage device 30M as time-series data for vehicle diagnosis. The compilation processing module 30P cooperates with the plurality of arithmetic modules 31, 32, ... to perform compilation processing of time-series data based on data acquired from the ECUs 1, 2, 3, 4, ....

[0017] The calculation modules 31, 32, ... of the aggregation ECU 30 execute the corresponding calculation programs (general-purpose logic) to aggregate time-series data based on data from the ECUs 1, 2, 3, 4, ... to generate aggregation results in different aggregation formats. In this embodiment, the aggregation formats of the time-series data in the multiple calculation modules 31, 32, ... include maximum values, minimum values, average values, integrated values, one-dimensional frequency distributions, two-dimensional frequency distributions, etc. That is, the calculation modules 31, 32, ... extract or calculate maximum values, minimum values, average values, or integrated values ​​of specified data (e.g., physical quantities such as engine speed) under specified conditions and output them as aggregation results, or create one-dimensional frequency distributions or two-dimensional frequency distributions of one or two specified data under specified conditions as aggregation results.

[0018] Further, the storage device 30M of the tallying ECU 30 stores (contains) a plurality of tallying conditions (data sets) as exemplified in Fig. 3, linked to a tallying format. The plurality of tallying conditions shown in Fig. 3 are each determined in advance to obtain a desired tallying result, and are stored in the storage device 30M, for example, during the manufacturing stage of the vehicle V. As shown in the figure, the plurality of tallying conditions each include a data ID and attribute determined for the vehicle V of a variable (tallying item) in the tally, tallying axis information, a calculation cycle (tallying cycle), a prerequisite for tallying, associated information, and the like.

[0019] The variables (aggregation items) in the aggregation are selected from a number of physical quantities such as vehicle speed, engine RPM, and motor RPM, and a number of setting states, and the attributes of the variables are selected from raw values, extreme values, average values, etc. The aggregation axis information includes the upper and lower limits of the vertical axis (X-axis) and horizontal axis (Y-axis), the intervals of the scale, etc. The calculation cycle indicates, for example, the cycle at which values ​​are plotted on the XY coordinates. The preconditions specify, for example, the vehicle speed range and temperature range in the aggregation, and include at least one condition variable, equality and inequality signs indicating the magnitude relationship between the condition variables, and the relationship between multiple preconditions (such as "AND" and "OR"). The associated information is any information related to the aggregation process, including, for example, the time to start / end the aggregation, vehicle speed, and mileage.

[0020] Furthermore, each of the multiple tally conditions is assigned an tally ID as an identifier. In this embodiment, the tally ID is a number assigned to each tally condition, and is divided into multiple groups, each of which includes an empty number, in numerical order. Each group of tally IDs is assigned (linked) to one tally format. For example, a "two-dimensional frequency distribution" is assigned to the group of tally IDs from n to n+α. This links each of the multiple tally conditions to a corresponding tally format. Note that the tally conditions are not limited to those illustrated in FIG. 3, and can be arbitrarily determined depending on the tally format, etc.

[0021] Next, a data collection procedure performed by the collection ECU 30 will be described with reference to Fig. 4. Fig. 4 is a flowchart showing a data collection routine executed by the collection ECU 30, i.e., the collection processing module 30P and the multiple arithmetic modules 31, 32, ... at a predetermined timing.

[0022] When the timing for executing the data counting routine arrives, the counting processing module 30P of the counting ECU 30 sets the repeat variable i to "1" (step S100), reads out the first counting condition, i.e., the counting condition having the smallest counting ID, from the storage device 30M and expands it in the RAM (step S110). The counting processing module 30P also selects one of the calculation modules 31, 32, ... that corresponds to the counting format linked to the counting ID (number) of the counting condition read out in step S110 (step S120), and instructs one of the selected calculation modules 31, 32, ... to execute data counting.

[0023] Any one of the calculation modules 31, 32, ... reads out data (variables) specified by the tallying conditions read out in step S110 from the storage device 30M, and generates tallying results in a tallying format linked to the tallying ID according to the tallying conditions (step S130). When any one of the calculation modules 31, 32, ... generates tallying results, the tallying processing module 30P stores the generated tallying results in the storage device 30M (step S140). Furthermore, the tallying processing module 30P determines whether tallying for all tallying conditions stored in the storage device 30M has been completed (step S150).

[0024] If the tallying has not been completed for all tallying conditions (step S150: NO), the tallying module 30P increments the repeat variable i (step S160) and then executes the processes of steps S110-S150. If the tallying has been completed for all tallying conditions (step S150: YES), the tallying module 30P ends the data tallying routine of Fig. 4. The routine of Fig. 4 may be modified so that the processes of steps S110, S120, S130, and S140 are each executed in order for all tallying IDs.

[0025] 4 is transmitted from the aggregation ECU 30 to the in-vehicle communication device 20 in response to a transmission request from the management server 100 or at a predetermined cycle, similar to the time-series data for vehicle diagnosis, and is then transmitted from the in-vehicle communication device 20 to the management server 100. This makes it possible to significantly reduce the data volume of information transmitted from the vehicle V (in-vehicle communication device 20) to the management server 100, compared to the case where time-series data for obtaining a plurality of aggregation results is transmitted from the vehicle V (aggregation ECU 30) to the management server 100. Furthermore, the management server 100 does not need to aggregate data from the vehicle V (aggregation ECU 30), and can basically utilize the aggregation results as they are.

[0026] On the other hand, the management server 100 is installed and managed by, for example, a vehicle manufacturer that manufactures the vehicle V, and includes a computer having a CPU, ROM, RAM, input / output devices, etc., a communication module for communicating with the in-vehicle communication device 20 of the vehicle V, etc., and a storage device 100M that stores various information. The management server 100 links the time series data for vehicle diagnosis transmitted from a large number of vehicles including the vehicle V and the aggregation results of the time series data to vehicle information such as the chassis number and vehicle number of the vehicle V, etc., and stores them in the storage device 100M. In addition, developers of the vehicle manufacturer, personnel of a vehicle dealer or a maintenance shop, etc. can access the management server 100 via their own terminals, etc., and view or download the time series data for vehicle diagnosis and the aggregation results managed by the management server 100. This makes it possible to use the information managed by the management server 100 for the development of new vehicles, market research, analysis of the cause of abnormalities occurring in vehicles, etc.

[0027] Here, for the development of a new vehicle, market research, analysis of the cause of an abnormality occurring in a vehicle, and the like, it is required to secure as much actual measurement data as possible. However, if the tallying conditions stored in the storage device 30M of the tallying ECU 30 are only those prepared at the manufacturing stage of the vehicle V, there is a risk that the developer or the like will not be able to obtain the tallying results that the developer or the like desires from the vehicle V side. In light of this, the management server 100 is configured to accept a request for acquiring new tallying results from the developer or the like, and to notify the vehicle V side of new tallying conditions and tallying formats according to the developer or the like's request. Furthermore, the vehicle V is configured so that the tallying ECU 30 can tally up time-series data according to the new tallying conditions and tallying formats notified from the management server 100.

[0028] In this embodiment, information regarding data processing by multiple ECUs and in-vehicle data communication for each vehicle model is pre-stored in the storage device 100M of the management server 100. When the management server 100 receives a request from a developer or the like to acquire new tally results for the vehicle V, the management server 100 creates a new tally condition table as shown in Fig. 5 while referring to the information stored in the storage device 100M, and transmits the created new tally condition table to the in-vehicle communication device 20 of the vehicle V. The new tally condition table associates tally conditions for obtaining new tally results requested by the developer or the like with the tally format of the new tally results.

[0029] 5, the new tally condition table created by the management server 100 also includes variables (tally items) in tally, attributes of the variables (tally items), tally axis information, calculation cycle (tally cycle), tally preconditions, associated information, etc. In addition, in the new tally condition table, the management server 100 specifies data IDs of variables (variables 1 and 2 in FIG. 5) that are tally items and preconditions (condition variables 1 and 2 in FIG. 5), as well as the ID of the data collection frame Ft, diagnostic record frame Fd, or general frame Ff in which data corresponding to the data ID should be stored, the address (starting address) in the data collection frame Ft, diagnostic record frame Fd, or general frame Ff in which the data should be stored, and the data length.

[0030] However, in the specification fields of the variables that are the aggregation items of the new aggregation condition table and the condition variables that define the prerequisites, the addresses of the storage devices 1M, 2M, 3M, 4M, ... in which the data corresponding to the data ID is stored may be written instead of the data ID. Furthermore, the new aggregation condition table is not limited to the example shown in Fig. 5, and can be arbitrarily determined within the range that can be handled on the vehicle V side.

[0031] Furthermore, when the in-vehicle communication device 20 of the vehicle V receives a new tally condition table from the management server 100, it transmits the received new tally condition table to the tally ECU 30. Furthermore, the in-vehicle communication device 20 executes a process for storing data corresponding to the variables and condition variables specified by the new tally condition table in the general-purpose frame Ff of CAN communication as necessary. This enables data that has not been provided (transmitted) to the tally ECU 30 until then to be stored in the frame F of CAN communication by the ECUs 1, 2, 3, 4, ....

[0032] Further, the tally processing module 30P of the tally ECU 30 assigns a tally ID (for example, the smallest vacant number in the range of numbers of the specified tally format) to the new tally conditions defined by the new tally condition table received from the in-vehicle communication device 20, links the new tally conditions to the tally format, and stores them in the storage device 30M. Furthermore, the tally processing module 30P acquires (receives) data stored by the ECUs 1, 2, 3, 4, ... from the data collection frame Ft, the diagnosis record frame Fd, and the general-purpose frame Ff of the frame F of the CAN communication, and stores them as time-series data (history information) in the storage device 30M. As a result, when the tally ECU 30 executes the data tally routine of FIG. 4 after the in-vehicle communication device 20 receives the new tally condition table from the management server 100, in addition to the tally results corresponding to the existing tally conditions, the tally ECU 30 generates tally results corresponding to the new tally conditions defined by the new tally condition table, i.e., tally results in the tally format specified by the management server 100.

[0033] As described above, when a new tally condition table is transmitted from the management server 100, which is an external device, to the in-vehicle communication device 20, the tally ECU 30 as a data collection device tallys the time-series data collected from the vehicle V to generate tally results in a tally format designated by the management server 100, and transmits the tally results to the management server 100 via the in-vehicle communication device 20. This makes it possible to significantly reduce the data volume of information transmitted from the vehicle V (in-vehicle communication device 20) to the management server 100, compared to the case where data for obtaining tally results corresponding to the new tally condition table is transmitted from the vehicle V to the management server 100. Furthermore, the management server 100 does not need to tally data from the vehicle V (the tally ECU 30), and can basically utilize the tally results corresponding to the new tally condition table as they are. As a result, by mounting the tally ECU 30 on the vehicle V, it becomes possible to provide the management server 100 with useful information according to the needs of the management server 100 (developers, etc.) from the vehicle V to the management server 100, while reducing the communication load and the processing load of the management server 100.

[0034] In the above embodiment, the aggregation ECU 30 includes a plurality of calculation modules 31, 32, ..., 3n that aggregate time-series data and generate aggregation results in different aggregation formats. This makes it possible to provide the management server 100 (developer, etc.) with useful aggregation results that meet various needs of the management server 100 from the vehicle V.

[0035] Furthermore, the tally processing module 30P of the tally ECU 30 acquires from the management server 100 a new tally condition table (see FIG. 5) including at least variables to be tally items, attributes of tally items (variables), tally axis information, calculation cycle (tally cycle), and tally preconditions, and linked to a tally format requested by a developer or the like. The tally processing module 30P links the new tally conditions defined by the new tally condition table to the tally format and stores them in the storage device 30M. Furthermore, the tally processing module 30P causes one of the arithmetic modules 31, 32, ... corresponding to the tally format from the management server 100 to tally the time series data according to the new tally conditions linked to the tally format (FIG. 4). This allows one of the corresponding arithmetic modules 31, 32, ... to execute an appropriate tally process, thereby making it possible to obtain useful tally results according to the needs of the management server 100 (developer or the like).

[0036] In the above embodiment, the tallying ECU 30 collects data by CAN communication from the ECUs 1, 2, 3, 4, ... of the vehicle V that acquire the assigned data. The frame F of the CAN communication includes a data collection frame Ft in which the data received by the tallying ECU 30 is stored, a diagnosis record frame Fd in which data for vehicle diagnosis and the like is stored, and a general frame Ff in which any data is stored. The new tallying conditions defined by the new tallying condition table include a data ID of the data to be stored in the frame F of the CAN communication, an ID of the data collection frame Ft, the diagnosis record frame Fd, or the general frame Ff in which the data is to be stored, and an address in the data collection frame Ft, the diagnosis record frame Fd, or the general frame Ff in which the data is to be stored. The ECUs 1, 2, 3, 4, ... store the data acquired by each of them in the frame F of the CAN communication according to the new tallying conditions from the management server 100. This makes it possible to flexibly change the data collected by the tallying ECU 30 and the tallying results according to the ever-changing needs of the management server 100 side (developers, etc.).

[0037] 3 does not necessarily need to be stored in the storage device 30M at the manufacturing stage of the vehicle V, and may be sequentially stored in the storage device 30M when the vehicle V is delivered to a user. The external device is not limited to the management server 100 or the terminal 150 at the vehicle dealer or vehicle maintenance shop, but may be a dedicated terminal (not shown) connected to the in-vehicle communication device 20 by wire or wireless communication for fault diagnosis of the vehicle V. The aggregation ECU 30 may be configured as a data logger mounted on the vehicle V and constantly recording a plurality of data at a predetermined cycle. The function of the aggregation ECU 30 may be incorporated in any of the ECUs 1, 2, 3, 4, . . . The vehicle V is not limited to a hybrid vehicle, but may be a vehicle using only an engine as a power source, or may be an electric vehicle (including a fuel cell vehicle).

[0038] As described above, the data collection device disclosed herein is a data collection device (30) that is mounted on a vehicle (V) and collects data regarding the condition of the vehicle (V), obtains the data aggregation format from an off-vehicle device (100, 150), aggregates the data collected from the vehicle (V) to generate aggregation results in the aggregation format specified by the off-vehicle device (100, 150), and transmits the aggregation results to the off-vehicle device (100, 150).

[0039] The data collection device disclosed herein aggregates data collected from the vehicle, generates an aggregated result in an aggregate format specified by the external device, and transmits the generated aggregated result to the external device. This makes it possible to significantly reduce the data volume of information transmitted from the vehicle to the external device, compared to a case in which data for obtaining the aggregated result is transmitted from the vehicle to the external device. Furthermore, the external device does not need to aggregate data from the vehicle (data collection device), and can basically use the aggregated result as it is. As a result, the data collection device disclosed herein makes it possible to provide the external device with useful information according to the needs of the external device from the vehicle, while reducing the communication load and the processing load of the external device.

[0040] The data collection device (30) may also include a plurality of calculation modules (31, 32, . . . , 3n) each of which aggregates the data and generates the aggregation results in the aggregation formats different from each other.

[0041] This makes it possible to provide useful tabulation results that meet various needs of external devices from the vehicle to the external devices.

[0042] Furthermore, the data collection device (30) may acquire, in addition to the aggregation format, aggregation conditions including at least aggregation items, attributes of the aggregation items, aggregation axis information, aggregation period, and aggregation prerequisites from the off-vehicle device (100, 150), link the acquired aggregation format and the aggregation conditions, store them in a storage device (30M), and cause the calculation module (31, 32, ..., 3n) corresponding to the aggregation format from the off-vehicle device (100, 150) to aggregate the data in accordance with the aggregation conditions linked to the aggregation format.

[0043] This allows the relevant calculation module to execute an appropriate tallying process, making it possible to obtain useful tallying results that meet the needs of the external device.

[0044] The data collection device (30) may collect the data by CAN communication from a plurality of devices (1, 2, 3, 4, ...) of the vehicle that acquire the assigned data, and a frame (F) of the CAN communication may include a data collection frame (Ft) in which the data received by the data collection device is stored, a diagnosis record frame (Fd) in which the data for vehicle diagnosis is stored, and a general-purpose frame (Ff) in which any of the data is stored, and the aggregation conditions are stored in the frame (F) of the CAN communication. The frame (F) may include an ID of the data to be stored in the data collection frame (Ft), the diagnostic record frame (Fd) or the general frame (Ff) in which the data is to be stored, and an address in the data collection frame (Ft), the diagnostic record frame (Fd) or the general frame (Ff) in which the data is to be stored, and the multiple devices (1, 2, 3, 4, ...) may store the data they have acquired in the frame (F) of the CAN communication in accordance with the aggregation conditions from the external device (100, 150).

[0045] This makes it possible to flexibly change the data collected by the data collection device and the collected results in response to the ever-changing needs of the external device.

[0046] In addition, the external device may be at least one of a management server (100) that acquires and manages information from the data collection device (30) via a communication device (20) mounted on the vehicle (V) and a terminal (150) that is connected to the data collection device (30) via the communication device (20) for fault diagnosis of the vehicle (V).

[0047] The data collection method disclosed herein is a data collection method for collecting data regarding the condition of a vehicle (V), in which an external device (100, 150) transmits a data aggregation format for the data to the vehicle (V), the data collected from the vehicle (V) is aggregated on the vehicle (V) side to generate an aggregate result in the aggregation format specified by the external device (100, 150), and the aggregate result is transmitted from the vehicle (V) to the external device (100, 150).

[0048] According to this method, it is possible to provide useful information that meets the needs of the external device from the vehicle, while reducing the communication load and the processing load of the external device.

[0049] However, the invention of the present disclosure is not limited to the above embodiment, and various modifications can be made within the scope of the present disclosure. Furthermore, the above embodiment is merely a specific form of the invention described in the Summary of the Invention, and does not limit the elements of the invention described in the Summary of the Invention. [Industrial Applicability]

[0050] The present disclosure is applicable to the vehicle manufacturing industry and the like. [Explanation of symbols]

[0051] 1, 2, 3, 4 electronic control unit (ECU), 1M, 2M, 3M, 4M, 30M, 100M storage device, 1P, 2P, 3P, 4P data processing module, 20 on-board communication device, 30 aggregation electronic control device (data collection device), 30P aggregation processing module, 31, 32, 3n calculation module, 100 management server (external device), 150 terminal, F frame, Fd diagnosis record frame, Ff general-purpose frame, Ft data collection frame, V vehicle.

Claims

1. A data collection device that is mounted on a vehicle and collects data regarding a state of the vehicle, a plurality of calculation modules each for aggregating the data and generating aggregating results in a different format; a data collection device that acquires from an external device the aggregation format of the data and aggregation conditions including at least aggregation items, attributes of the aggregation items, aggregation axis information, aggregation cycles, and aggregation prerequisites, links the acquired aggregation format and the aggregation conditions and stores them in a storage device, causes the calculation module corresponding to the aggregation format from the external device to aggregate the data in accordance with the aggregation conditions linked to the aggregation format, and transmits to the external device the aggregation results in the aggregation format specified by the external device and generated by the calculation module.

2. 2. The data collection device according to claim 1, the data collection device collects the data from a plurality of devices of the vehicle that acquire the assigned data through CAN communication; the frames of the CAN communication include a data collection frame in which the data received by the data collection device is stored, a diagnosis record frame in which the data for vehicle diagnosis is stored, and a general-purpose frame in which any data is stored; the counting conditions include an ID of the data to be stored in the frame of the CAN communication, an ID of the data collection frame, the diagnostic record frame, or the general frame in which the data is to be stored, and an address in the data collection frame, the diagnostic record frame, or the general frame in which the data is to be stored, The plurality of devices are configured to store the acquired data in the frame of the CAN communication in accordance with the collection conditions from the external device.

3. 3. The data collection device according to claim 1, The external device is a data collection device which is at least one of a management server which acquires and manages information from the data collection device via a communication device mounted on the vehicle, and a terminal which is connected to the data collection device via the communication device for fault diagnosis of the vehicle.

4. 1. A data collection method for collecting data regarding a state of a vehicle, comprising: transmitting, from an external device to the vehicle, a data collection format of the data and collection conditions including at least collection items, attributes of the collection items, collection axis information, a collection period, and a collection prerequisite; The tallying format and the tallying conditions from the external device are associated with each other and stored in a storage device of the vehicle; causing a computing module of the vehicle corresponding to the tallying format from the external device to tally the data in accordance with the tallying conditions associated with the tallying format; a data collection method for transmitting, from the vehicle to the external device, a compilation result in the compilation format specified by the external device and generated by the computing module.

Images