Data collection device and data collection system

Abstract

A data collection device (100) that collects vehicle data and transmits the vehicle data to a server (4) is provided with arrangement conversion units (110, 120, 130), a data conversion unit (160), and a communication unit (190). The arrangement conversion units (110, 120, 130) convert vehicle data supplied from the data supply device (30) in a signal arrangement corresponding to the communication interface into a common signal arrangement. The data conversion unit (160) converts the vehicle data of the communication protocol corresponding to the communication interface, which has been converted to the general-purpose signal configuration by the configuration conversion units (110, 120, 130), to data in a general-purpose format. The communication unit (190) transmits, to a server (4), the vehicle data converted into the data in the general format by the data conversion unit (160).

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This international application claims the benefit of priority from Japanese Patent Application No. 2023-013170 filed with the Japan Patent Office on January 31, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to a technology for collecting vehicle data and sending the data to a server. Background Art

[0004] Patent Document 1 below discloses technology for collecting vehicle data from an in-vehicle network and transmitting it to a designated server. In the vehicle described in Patent Document 1, ECUs and other components are categorized into domains based on vehicle function, and appropriate communication interfaces are used within the in-vehicle network for each domain. ECU stands for Electronic Control Unit.

[0005] Patent Document 1: Japanese Patent Application Laid-Open No. 2018-060520

[0006] However, as a result of detailed research by the inventors, they discovered that when collecting vehicle data from a single vehicle equipped with a plurality of different communication interfaces, it is necessary to improve the device for collecting vehicle data according to the communication interface mounted on the vehicle.

[0007] Furthermore, a problem has been identified in that when collecting vehicle data from different vehicles using different communication interfaces, different devices for collecting vehicle data need to be used depending on the vehicles having different communication interfaces. Summary of the Invention

[0008] One aspect of the present disclosure is to provide a technology for collecting vehicle data having different communication interfaces in a universal manner.

[0009] One aspect of the present disclosure is a data collection device that collects vehicle data and transmits the data to a server. The device includes a configuration conversion unit, a data conversion unit, and a communication unit.

[0010] The configuration conversion unit converts vehicle data supplied from a data supply device in a signal configuration corresponding to the communication interface into a universal signal configuration. The data conversion unit converts vehicle data in a communication protocol corresponding to the communication interface, converted into the universal signal configuration by the configuration conversion unit, into data in a universal format. The communication unit transmits the vehicle data, converted into the universal format by the data conversion unit, to a server.

[0011] Another aspect of the present disclosure is a data collection system that collects vehicle data and transmits the collected data to a server. The system includes a data supply device and a data collection device.

[0012] The data supply device includes a gateway for supplying vehicle data from a vehicle network, and a connector for supplying vehicle data from the gateway using a signal configuration corresponding to a communication interface.

[0013] The data collection device includes a configuration conversion unit, a data conversion unit, a connector, and a communication unit.

[0014] The configuration converter converts the signal configuration of the vehicle data supplied by the data supply device into a universal signal configuration. The data converter converts the vehicle data of the communication protocol corresponding to the communication interface, which has been converted into the universal signal configuration by the configuration converter, into data in a universal format.

[0015] The data conversion unit acquires the vehicle data converted into a common signal configuration by the configuration conversion unit from the connector.

[0016] The communication unit transmits the vehicle data converted into data in a common format by the data conversion unit to the server.

[0017] Furthermore, the configuration conversion unit includes a universal connector connected to a connector for the data conversion unit to obtain vehicle data, a supply-side connector connected to a connector of the data supply device, and a cable that connects the universal connector to the supply-side connector and converts the signal configuration of the supply-side connector into a universal signal configuration of the universal connector.

[0018] With this configuration, even if vehicle data is supplied from a single vehicle data supply device, or from multiple vehicles with different communication interfaces, the vehicle data can be converted into a common format using a common data collection device. Therefore, there is no need to prepare separate data collection devices for each communication interface.

[0019] In the data collection system, the configuration conversion unit connects the connector of the data supply device to the connector for acquiring vehicle data by the data conversion unit of the data collection device, thereby easily converting vehicle data supplied through different communication interfaces into data in a common format.

[0020] Furthermore, if the communication interface of the vehicle data supplied from the data supply device is different and the signal configuration of the connector of the data supply device is different, a configuration conversion unit that matches the communication interface can be prepared. Alternatively, if the communication protocol is different, a data conversion unit that matches the communication interface can be prepared.

[0021] Furthermore, since the vehicle data supplied through different communication interfaces is converted into vehicle data in a common format, the server can easily process the vehicle data converted into the common format. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Figure 1This is a block diagram showing the structure of a data management system.

[0023] Figure 2 This is a block diagram showing the configuration of a data supply device.

[0024] Figure 3 This is a block diagram showing the configuration of a data collection device.

[0025] Figure 4 This is a correspondence diagram explaining the conversion of the signal configuration by the conversion adapter for OBD2.

[0026] Figure 5 This is a diagram illustrating the conversion of signal configuration using a conversion adapter for FMS.

[0027] Figure 6 This is a diagram illustrating the conversion of the signal configuration by the conversion adapter for CAN.

[0028] Figure 7 This diagram shows the signal arrangement of the universal connector.

[0029] Figure 8 This is a diagram showing the structure of a general format.

[0030] Figure 9 This is a diagram showing the conversion of vehicle data in OBD2.

[0031] Figure 10 This is a diagram showing the conversion of vehicle data on CAN.

[0032] Figure 11 This is a flowchart showing the data collection process. DETAILED DESCRIPTION

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

[0034] [1. Composition]

[0035] like Figure 1 As shown, the data management system 2 of this embodiment includes a server 4 , a wireless communication network 6 , and a plurality of data collection systems 20 .

[0036] The server 4 performs data communication with a plurality of data collection systems 20 via the wireless communication network 6 , and manages the travel of the vehicle 10 based on the vehicle data collected from the data collection systems 20 .

[0037] The data collection system 20 is mounted on the vehicle 10 and includes a data supply device 30 and a data collection device 100 .

[0038] like Figure 2As shown, the data supply device 30 includes multiple ECUs 40, a gateway 50, an FMS control unit 60, an OBD2 connector 70, an FMS connector 72, and a CAN connector 74, all mounted on the vehicle 10. OBD stands for On-Board Diagnostics, FMS stands for Fleet Management System, and CAN stands for Controller Area Network. CAN is a registered trademark.

[0039] Each ECU 40 communicates with each other using the CAN protocol, for example, for each control group, and controls the travel of the vehicle 10 .

[0040] The gateway 50 acquires control values for controlling the vehicle 10 and detection values of various sensors installed in the vehicle 10 as vehicle data from the ECU 40. The gateway 50 transmits the vehicle data acquired from the ECU 40 to the OBD2 connector 70 and the FMS connector 72 via their respective communication interfaces.

[0041] In this embodiment, the communication interface refers to at least one standard of hardware and software in communication, and the communication protocol refers to at least one of a procedure and a data format in communication.

[0042] The FMS control unit 60 provides a portion of the vehicle data collected from the CAN as data in the FMS standard format.

[0043] The OBD2 connector 70 and the FMS connector 72 are connectors mounted on the vehicle 10 as standard.

[0044] Normally, the CAN connector 74 is not mounted on the vehicle 10. For example, when vehicle data that cannot be acquired through the communication interfaces of the OBD2 connector 70 and the FMS connector 72 is required, the CAN connector 74 is provided to acquire the desired vehicle data by connecting to the vehicle network on the ECU 40 side rather than the gateway 50.

[0045] like Figure 3 As shown, the data collection device 100 includes conversion adapters 110 , 120 , and 130 and a data processing device 150 .

[0046] Conversion adapter 110 includes an OBD2 connector 112, a cable 114, and a universal connector 140. Conversion adapter 120 includes an FMS connector 122, a cable 124, and a universal connector 140. Conversion adapter 130 includes a CAN connector 132, a cable 134, and a universal connector 140. Universal connector 140 of conversion adapters 110, 120, and 130 has a common and identical signal configuration.

[0047] The OBD2 connector 112 is connected to the OBD2 connector 70 of the data supply device 30 . The FMS connector 122 is connected to the FMS connector 72 of the data supply device 30 . The CAN connector 132 is connected to the CAN connector 74 of the data supply device 30 .

[0048] The universal connectors 140 of the conversion adapters 110 , 120 , and 130 are respectively connected to the universal connector 152 of the data processing device 150 .

[0049] The cable 114 connects the OBD2 connector 112 with the universal connector 140 , the cable 124 connects the FMS connector 122 with the universal connector 140 , and the cable 134 connects the CAN connector 132 with the universal connector 140 .

[0050] like Figure 4 As shown, the OBD2 conversion adapter 110 converts the signal configuration corresponding to the OBD2 interface indicated by the pin number of the OBD2 connector 112 into a universal signal configuration of the universal connector 140 via the cable 114 .

[0051] like Figure 5 As shown, the conversion adapter 120 for FMS converts the signal configuration corresponding to the FMS interface indicated by the pin number of the FMS connector 122 into the universal signal configuration of the universal connector 140 via the cable 124 .

[0052] Figure 6 As shown, the CAN conversion adapter 130 converts the signal configuration corresponding to the CAN interface indicated by the pin number of the CAN connector 132 into a universal signal configuration of the universal connector 140 via a cable 134 .

[0053] Furthermore, the power (+) or 12V, GND or 12VGND, CAN1_H or CAN_H, and CAN1_L or CAN_L are all shared as the same signal in OBD2 connector 112, FMS connector 122, and CAN connector 132. These signals are converted into a single signal via cables 114, 124, and 134, with the signal configuration converted to power (+) on pin 5, GND on pin 6, CAN1_H on pin 7, and CAN1_L on pin 8 of universal connector 140.

[0054] The data processing device 150 of the data collection device 100 is supplied with power from the data supply device 30 via a power pin of the universal connector 152 .

[0055] In addition, in Figure 3When multiple universal connectors 152 are provided for multiple communication interfaces as shown, power is supplied from only one power pin of universal connector 152. This is to prevent power from being supplied to data processing device 150 from multiple power pins of universal connector 152.

[0056] Therefore, in order to supply power from the data supply device 30 to the data processing device 150 , it is necessary to connect any one of the conversion adapters 110 , 120 , and 130 to the universal connector 152 at the position where power is supplied.

[0057] like Figure 7 As shown, the signal values of pins 1 through 4 of universal connector 140, representing the interface ID, are set to the signal values of the corresponding communication interfaces for each conversion adapter 110, 120, or 130. ID stands for identifier. For example, an interface ID signal value of 0b0001 indicates a CAN signal, while a signal value of 0b0010 indicates an OBD2 signal.

[0058] The data processing device 150 includes a universal connector 152 , a data conversion unit 160 , a data storage unit 170 , a data access unit 180 , and a communication unit 190 .

[0059] The data processing device 150 is equipped with, for example, a microcomputer (not shown) having a CPU, ROM, RAM, flash memory, etc. The CPU of the data processing device 150 executes a program stored in the ROM or flash memory to perform data collection processing described below.

[0060] The universal connector 152 is connected to the universal connector 140 of the conversion adapters 110 , 120 , and 130 . The signal configuration of the universal connector 152 corresponds to the signal configuration of the universal connector 140 of the conversion adapters 110 , 120 , and 130 .

[0061] The data conversion unit 160 includes an interface identification unit 162 and a format conversion unit 164. The data conversion unit 160 is independently configured for each communication interface according to the number of corresponding communication interfaces in the data processing device 150. Each data conversion unit 160 receives a signal from any one of the universal connectors 152.

[0062] The interface identification unit 162 identifies the communication interface of the vehicle data acquired from the universal connector 152 based on the signal value of the interface ID of the universal connector 152 .

[0063] The format conversion unit 164 converts the vehicle data obtained from the universal connector 152 into a format according to the communication interface identified by the interface identification unit 162. Figure 8 Data in the general format shown.

[0064] The data ID in a general format indicates what the data represents. For example, the data ID indicates whether the data represents engine speed, vehicle speed, location, fuel level, battery level, diagnostic code, etc.

[0065] Common format data values are, for example, binary numeric values or, if they are characters, binary representations in UTF-8 format. If the data value is a numeric value, the unit is pre-set corresponding to the data ID. For example, if the data ID represents vehicle speed, the unit is km / h.

[0066] The format conversion unit 164 converts the vehicle data obtained from each universal connector 152 into a format corresponding to the communication protocol of the communication interface by taking OBD2 and CAN as examples. Figure 8 The process is described using data in a general format as shown.

[0067] (1)OBD2

[0068] The OBD2 format converter 164 of the data collection device 100 transmits a message requesting vehicle data to the data supply device 30 via the OBD2 conversion adapter 110. The OBD2 vehicle data request message is transmitted periodically or when a request is received from outside the vehicle 10 via the communication unit 190.

[0069] For example, when collecting vehicle speed data as vehicle data, the format conversion unit 164 transmits a vehicle speed data request message from the universal connector 152 to the data supply device 30 via the OBD2 conversion adapter 110. The signal configuration of the vehicle speed data request message is converted by the conversion adapter 110 from the universal signal configuration of the universal connector 152 to the signal configuration of the OBD2 connector 112 corresponding to the OBD2 interface.

[0070] For example, Figure 9 As shown, a vehicle data request message with CAN ID = 0x7E0, SID = 0x01, and Data ID = 0x0D is sent to the data supply device 30 via CAN1_H and CAN1_L of the conversion adapter 110. CAN ID = 0x7E0 specifies the engine ECU as the destination ECU for the vehicle data request, SID = 0x01 indicates that the current data request is for a diagnostic service, and Data ID = 0x0D indicates that the requested data is vehicle speed.

[0071] In response to the OBD2-based vehicle speed data request, the data provider 30 sends a response message with CAN ID = 0x7E8, SID = 0x41, and Data ID = 0x0D to the data collection device 100 via CAN1_H and CAN1_L of the conversion adapter 110. CAN ID = 0x7E8 indicates a response from the engine ECU, SID = 0x41 indicates a response to the current data request, and Data ID = 0x0D indicates the response data is vehicle speed.

[0072] The signal configuration of the response message of the vehicle speed data is converted by the conversion adapter 110 from the signal configuration of the OBD2 connector 112 corresponding to the OBD2 interface to the universal signal configuration of the universal connector 152 .

[0073] The format conversion unit 164 obtains the response message of the OBD2 communication protocol converted to the universal signal configuration in the universal connector 152. The format conversion unit 164 then refers to the conversion table based on the CAN ID = 0x7E8, SID = 0x41, and Data ID = 0x0D of the response message and obtains Resolution = 1 and Offset = 0.

[0074] Then, the format conversion unit 164 extracts the Data portion from the response message, multiplies it by the resolution=1, and adds the offset=0 to generate vehicle speed data.

[0075] For example, when the generated vehicle speed data is 30 km / h, the format conversion unit 164 sets the data ID to 0x01 and the data value to 30, and Figure 9 The vehicle data is converted into a common format as shown in the figure. Data ID = 0x01 indicates that the vehicle data is the vehicle speed.

[0076] (2)CAN

[0077] For example, the data collection device 100 obtains a message with CAN ID = 0x123 from the data supply device 30 via CAN1_H and CAN1_L of the conversion adapter 130. CAN ID = 0x123 indicates a message from the ECU that transmits the vehicle speed.

[0078] The signal configuration of the vehicle speed data is converted by the conversion adapter 130 from the signal configuration of the CAN connector 132 corresponding to the CAN interface to the universal signal configuration of the universal connector 152 .

[0079] The format converter 164 acquires the CAN communication protocol message converted into a universal signal configuration in the universal connector 152. Based on the CAN ID = 0x123 of the acquired message, the format converter 164 refers to the conversion table and acquires position = 1.0, DLC = 16 bits, resolution = 0.01, and offset = 0.

[0080] The format conversion unit 164 extracts DLC=16-bit data from position=1.0 of the Data portion of the message, multiplies it by resolution=0.01, and adds offset=0 to generate vehicle speed data.

[0081] For example, when the generated vehicle speed data is 30 km / h, the format conversion unit 164 sets the data ID to 0x01 and the data value to 30, and Figure 10 The vehicle data is converted into a common format as shown in the figure. Data ID = 0x01 indicates that the vehicle data is the vehicle speed.

[0082] The vehicle data converted into a universal format by the data conversion unit 160 is stored in the data storage unit 170 composed of a memory such as RAM or flash memory. The data stored in the data storage unit 170 is rewritten each time it is saved, or is rewritten in order from the oldest data in a ring buffer format.

[0083] Since the vehicle data stored in the data storage unit 170 is in a universal format, it is not accessed for each communication interface when supplied from the data supply device 30 but is accessed from the data access unit 180 using a universal access method.

[0084] The communication unit 190 transmits the vehicle data accessed by the data access unit 180 in a general access method to the server 4 .

[0085] [2. Processing]

[0086] based on Figure 11 The flowchart shown in FIG. 1 illustrates the data collection process performed by the data collection device 100. Figure 11 The program of the flowchart is stored in each data conversion unit 160 independently configured for each communication interface.

[0087] When the data processing device 150 is connected to the data supply device 30 via at least one of the conversion adapters 110, 120, and 130 and is supplied with power from the data supply device 30, the data processing device 150 executes Figure 11 Thereafter, the data processing device 150 executes the Figure 11 The flowchart shown.

[0088] In S400 , the interface identification unit 162 identifies the communication interface of the vehicle data acquired from the universal connector 152 based on the interface ID indicated by the signal values of the pins 1 to 4 of the universal connector 152 .

[0089] If the determination in S402 is NO, that is, if the communication interface is not OBD2, the process proceeds to S410.

[0090] If the determination in S402 is yes, that is, if the communication interface is OBD2, then in S402 the format conversion unit 164 acquires a data signal representing vehicle data from the universal connector 152 based on the communication protocol corresponding to the identified communication interface.

[0091] In S406, the format conversion unit 164 converts the vehicle data received from the universal connector 152 into data in a universal format. In S408, the format conversion unit 408 updates the old vehicle data with the current vehicle data to store the latest data.

[0092] If the determination in S410 is NO, that is, if the communication interface is not FMS, the process proceeds to S418.

[0093] If the determination in S410 is yes, that is, if the communication interface is FMS2, then in S412 to S416, the format conversion unit 164 executes the process of replacing OBD2 with FMS in the above-mentioned S404 to S408.

[0094] If the determination in S418 is NO, that is, if the communication interface is not any of OBD2, FMS, and CAN, the process proceeds to S426.

[0095] If the determination in S418 is yes, that is, if the communication interface is CAN, then in S420 to S414 , the format conversion unit 164 executes the process of replacing OBD2 with CAN in the above-mentioned S404 to S408 .

[0096] In S426 , the format converter 164 executes appropriate processing corresponding to the interface ID indicated by the signal values of the pins 1 to 4 of the universal connector 152 .

[0097] For example, when the interface ID indicates a value of the universal connector 142 that is not connected to any of the conversion adapters 110 , 120 , and 130 , the present process is terminated without performing any processing.

[0098] Alternatively, when the interface ID indicated by the signal values of the pin numbers 1 to 4 of the universal connector 152 is different from the values assumed in a normal situation, the format conversion unit 164 notifies the vehicle 10 of the abnormality.

[0099] [3. Effect]

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

[0101] (1) Vehicle data with different communication interfaces supplied from the data supply device 30 is converted into data in a common format by the conversion adapters 110 , 120 , 130 and the data conversion unit 160 as shown in the following (a) and (b).

[0102] (a) The conversion adapters 110 , 120 , and 130 convert the signal configuration of each communication interface on the data supply device 30 side into a common signal configuration based on the communication interface.

[0103] (b) The data conversion unit 160 converts the vehicle data converted into a common signal configuration into data in a common format based on a communication protocol corresponding to the communication interface.

[0104] Thus, the conversion adapters 110 , 120 , and 130 can easily convert vehicle data having different communication interfaces into data in a common format simply by connecting the data supply device 30 to the data processing device 150 including the data conversion unit 160 .

[0105] Furthermore, even if vehicle data is supplied from a single vehicle 10 data supply device 30 or from multiple vehicles 10 data supply devices 30 with different communication interfaces, the vehicle data is converted into data in a common format by the universal data collection device 100. Therefore, there is no need to prepare a separate data collection device for each communication interface.

[0106] Furthermore, since the vehicle data supplied through the different communication interfaces is converted into vehicle data in a common format, the server 4 can easily process the vehicle data converted into the common format.

[0107] (2) When converting the signal configuration of vehicle data supplied from the communication interface to a common signal configuration, the data supply device 30 configures the signals common to each communication interface as a single signal in the common signal configuration. This minimizes the number of signals in the common signal configuration. Consequently, the number of pins of the common connectors 140 and 152 can be reduced, allowing for miniaturization of the common connectors 140 and 152.

[0108] (3) Since power is supplied from the data supply device 30 to the data processing device 150 of the data collection device 100 via any one of the conversion adapters 110 , 120 , and 130 , it is not necessary to provide a power supply in the data collection device 100 .

[0109] (4) It is not predetermined which communication interface conversion adapter 110, 120, 130 is connected to the universal connector 152 of the data processing device 150. Therefore, an interface ID indicating the communication interface is set for the signal converted into a universal signal configuration by the conversion adapters 110, 120, 130 in the universal connector 152.

[0110] Thus, the data conversion unit 160 of the data processing device 150 can identify the communication interface of the connected conversion adapter based on the interface ID, regardless of which conversion adapter 110 , 120 , or 130 of the communication interface is connected to the universal connector 152 .

[0111] (5) The OBD2 connector 70 and the FMS connector 72 are usually provided in the vehicle 10. Therefore, when OBD2 and FMS are used as the communication interface for the data supply device 30 to supply vehicle data, there is no need to newly provide the OBD2 connector 70 and the FMS connector 72 in the vehicle 10.

[0112] (6) By using CAN as a communication interface, the data collection device 100 directly obtains vehicle data from the network of the vehicle 10 rather than from the gateway 50 , thereby being able to obtain vehicle data that cannot be obtained through OBD2 or FMS.

[0113] In the embodiment described above, the conversion adapters 110 , 120 , and 130 correspond to the configuration conversion unit, and the OBD2 connector 112 , the FMS connector 122 , and the CAN connector 132 correspond to the supply-side connector.

[0114] The processes of S402 to S406 , S410 to S414 , and S418 to S422 correspond to the processes of the data conversion unit.

[0115] [5. Other embodiments]

[0116] As mentioned above, although embodiment of this disclosure was described, this disclosure is not limited to the said embodiment, Various deformation|transformation and implementation are possible.

[0117] (1) In the above embodiment, an example is described in which the data collection device 100 converts vehicle data of different communication interfaces supplied from the data supply device 30 of a single vehicle 10 into data in a common format. Alternatively, for example, the data collection device 100 may convert vehicle data of a single type of communication interface supplied from the data supply device 30 of a single vehicle 10 into data in a common format.

[0118] (2) In the above embodiment, CAN is used as an example of the network of the vehicle 10, but the network is not limited to this. For example, the network of the vehicle 10 may be Ethernet, a mixture of CAN and Ethernet, or other networks. Ethernet is a registered trademark.

[0119] (3) In the above embodiment, OBD2, FMS, and CAN are exemplified as communication interfaces, but the communication interface is not limited to these interfaces. If a communication interface different from OBD2, FMS, or CAN is used, and the signal configuration of the connector of the data supply device 30 is different, a conversion adapter with a signal configuration that matches the communication interface can be prepared. Furthermore, if the communication protocol is different, a data conversion unit 160 that matches the communication interface can be prepared.

[0120] (4) The data collection device 100 and the method 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.

[0121] Alternatively, the data collection system 20, the data collection device 100, and the method 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.

[0122] Alternatively, the data collection system 20, data collection device 100, and method described in the present disclosure may be implemented by one or more dedicated computers consisting of a processor programmed to perform one or more functions, a memory, and a processor consisting of one or more hardware logic circuits.

[0123] The computer program may also be stored in a computer-readable non-transferable tangible recording medium as instructions executed by a computer. The method for implementing the functions of each component included in the data collection device 100 does not necessarily need to include software, and all its functions may be implemented using one or more hardware components.

[0124] (5) 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, it is also possible to omit part of the components of the above-mentioned embodiment. In addition, it is also possible to add or replace at least part of the components of the above-mentioned embodiment with the components of other above-mentioned embodiments.

[0125] (6) In addition to the above-mentioned data collection device 100, the present disclosure can also be implemented in various ways, such as a data collection system 20 that uses the data collection device 100 as a component, a program for causing a computer to function as the data collection device 100, a non-migrating physical recording medium such as a semiconductor memory that records the program, and a data collection method.

[0126] [Technical Ideas Disclosed in This Specification]

[0127] [Project 1]

[0128] A data collection device (100) for collecting vehicle data and sending the data to a server (4) comprises:

[0129] A configuration conversion unit (110, 120, 130) is configured to convert the vehicle data supplied from the data supply device (30) in a signal configuration corresponding to the communication interface into a universal signal configuration;

[0130] a data conversion unit (160, S402 to S406, S410 to S414, S418 to S422) configured to convert the vehicle data of the communication protocol corresponding to the communication interface, which has been converted into the common signal configuration by the configuration conversion unit, into data in a common format; and

[0131] The communication unit (190) is configured to transmit the vehicle data converted into the common format by the data conversion unit to the server.

[0132] [Project 2]

[0133] According to the data collection device described in item 1,

[0134] The connector (152) is configured such that the data conversion unit obtains the vehicle data converted into the universal signal configuration by the configuration conversion unit.

[0135] The configuration conversion unit includes a universal connector (140) connected to the connector for the data conversion unit to obtain the vehicle data, a supply-side connector (112, 122, 132) connected to the connector (70-74) of the data supply device that supplies the vehicle data in the signal configuration corresponding to the communication interface, and a cable (114, 124, 134) that connects the universal connector to the supply-side connector and converts the signal configuration of the supply-side connector into the universal signal configuration of the universal connector.

[0136] [Item 3]

[0137] According to the data collection device described in item 2,

[0138] The data conversion unit and the communication unit are configured to be supplied with power from the data supply device via the cable.

[0139] [Item 4]

[0140] According to the data collection device described in item 3,

[0141] When the plurality of configuration conversion units connect the connector of the data supply device to the connector from which the data conversion unit obtains the vehicle data according to the communication interface, the data conversion unit and the communication unit are configured to be supplied with power from the data supply device via one of the plurality of cables.

[0142] [Item 5]

[0143] The data collection device according to any one of items 1 to 4,

[0144] The signal in the common signal configuration is set with an interface identifier indicating the communication interface of the data supply device.

[0145] The data conversion unit is configured to convert the vehicle data converted into the common signal configuration into data in the common format based on the interface identifier.

[0146] [Item 6]

[0147] The data collection device according to any one of items 1 to 5,

[0148] The common signal configuration is configured to configure the same signal into one signal when different communication interfaces have the same signal.

[0149] [Item 7]

[0150] A data collection system is a data collection system (20) that collects vehicle data and sends it to a server (4).

[0151] A data supply device (30) and a data collection device (100) are provided.

[0152] The data supply device comprises a gateway (50) for supplying the vehicle data from a vehicle network, and connectors (70 to 74) for supplying the vehicle data from the gateway in a signal configuration corresponding to a communication interface.

[0153] The data collection device includes:

[0154] a configuration conversion unit (110, 120, 130) configured to convert the signal configuration of the vehicle data supplied by the data supply device into a universal signal configuration;

[0155] a data conversion unit (160, S402 to S406, S410 to S414, S418 to S422) configured to convert the vehicle data of the communication protocol corresponding to the communication interface, which has been converted into the common signal configuration by the configuration conversion unit, into data in a common format;

[0156] The connector (152), the data conversion unit acquires the vehicle data converted into the universal signal configuration by the configuration conversion unit; and

[0157] The communication unit (190) is configured to transmit the vehicle data converted into the universal format by the data conversion unit to the server.

[0158] The configuration conversion unit includes a universal connector (140) connected to the connector for the data conversion unit to obtain the vehicle data, a supply-side connector (112, 122, 132) connected to the connector of the data supply device, and a cable (114, 124, 134) for connecting the universal connector to the supply-side connector and converting the signal configuration of the supply-side connector into the universal signal configuration of the universal connector.

[0159] [Item 8]

[0160] According to the data collection system described in item 7,

[0161] The data supply device is configured to use at least one of OBD2 and FMS as the communication interface for the vehicle data supplied from the gateway.

[0162] [Item 9]

[0163] According to the data collection system described in item 7 or 8,

[0164] The data supply device includes a connector (74) for supplying the vehicle data not from the gateway but from the network of the vehicle.

Claims

1. A data collection device, comprising: a data collection device (100) for collecting vehicle data and transmitting the data to a server (4); have: A configuration conversion unit (110, 120, 130) is configured to convert the vehicle data supplied from the data supply device (30) in a signal configuration corresponding to the communication interface into a universal signal configuration; a data conversion unit (160, S402 to S406, S410 to S414, S418 to S422) configured to convert the vehicle data of the communication protocol corresponding to the communication interface, which has been converted into the common signal configuration by the configuration conversion unit, into data in a common format; and The communication unit (190) is configured to transmit the vehicle data converted into the common format by the data conversion unit to the server.

2. The data collection device according to claim 1, wherein: have: The connector (152) is configured such that the data conversion unit obtains the vehicle data converted into the universal signal configuration by the configuration conversion unit. The configuration conversion unit includes a universal connector (140) connected to the connector for the data conversion unit to obtain the vehicle data, a supply-side connector (112, 122, 132) connected to the connector (70-74) of the data supply device that supplies the vehicle data in the signal configuration corresponding to the communication interface, and a cable (114, 124, 134) that connects the universal connector to the supply-side connector and converts the signal configuration of the supply-side connector into the universal signal configuration of the universal connector.

3. The data collection device according to claim 2, wherein: The data conversion unit and the communication unit are configured to be supplied with power from the data supply device via the cable.

4. The data collection device according to claim 3, wherein: When the plurality of configuration conversion units connect the connector of the data supply device to the connector from which the data conversion unit obtains the vehicle data according to the communication interface, the data conversion unit and the communication unit are configured to be supplied with power from the data supply device via one of the plurality of cables.

5. The data collection device according to claim 1, wherein: The signal in the common signal configuration is set with an interface identifier indicating the communication interface of the data supply device. The data conversion unit is configured to convert the vehicle data converted into the common signal configuration into data in the common format based on the interface identifier.

6. The data collection device according to claim 1, wherein: The common signal configuration is configured to configure the same signal into one signal when different communication interfaces have the same signal.

7. A data collection system, comprising: a data collection system (20) for collecting vehicle data and transmitting the data to a server (4); A data supply device (30) and a data collection device (100) are provided. The data supply device comprises a gateway (50) for supplying the vehicle data from a vehicle network, and connectors (70 to 74) for supplying the vehicle data from the gateway in a signal configuration corresponding to a communication interface. The data collection device includes: a configuration conversion unit (110, 120, 130) configured to convert the signal configuration of the vehicle data supplied by the data supply device into a universal signal configuration; a data conversion unit (160, S402 to S406, S410 to S414, S418 to S422) configured to convert the vehicle data of the communication protocol corresponding to the communication interface, which has been converted into the common signal configuration by the configuration conversion unit, into data in a common format; The connector (152), the data conversion unit acquires the vehicle data converted into the universal signal configuration by the configuration conversion unit; and The communication unit (190) is configured to transmit the vehicle data converted into the universal format by the data conversion unit to the server. The configuration conversion unit includes a universal connector (140) connected to the connector for the data conversion unit to obtain the vehicle data, a supply-side connector (112, 122, 132) connected to the connector of the data supply device, and a cable (114, 124, 134) for connecting the universal connector to the supply-side connector and converting the signal configuration of the supply-side connector into the universal signal configuration of the universal connector.

8. The data collection system according to claim 7, wherein: The data supply device is configured to use at least one of OBD2 and FMS as the communication interface for the vehicle data supplied from the gateway.

9. The data collection system according to claim 7 or 8, wherein: The data supply device includes a connector (74) for supplying the vehicle data not from the gateway but from the network of the vehicle.

Images