Vehicle data collection system, in-vehicle device, server, computer program and vehicle data collection method

Abstract

A vehicle data collection system equipped with an in-vehicle device installed in a vehicle and a server for collecting data from the in-vehicle device, wherein: the in-vehicle device is equipped with a data collection unit for collecting vehicle data, which is data pertaining to the vehicle, a data conversion unit for converting the collected vehicle data into formatted data of a version which corresponds to the vehicle data type, and writing said version onto the formatted data, and a data transmission unit for transmitting the formatted data onto which said version has been written to the server; and the server is equipped with a data-receiving unit for receiving the formatted data, and a data restoration unit for restoring the vehicle data from the formatted data on the basis of the version indicated by the formatted data.

Description

Vehicle data collection system, on-board device, server, computer program, and vehicle data collection method

[0001] This disclosure relates to a vehicle data collection system, an on-board device, a server, a computer program, and a vehicle data collection method. This application claims priority to Japanese Application No. 2022-175951 filed on November 2, 2022, and incorporates by reference all of the contents of said Japanese application.

[0002] 2. Description of the Related Art Conventionally, a movement management system has been developed that grasps and records the position information of a vehicle or a driver in real time (see, for example, Non-Patent Document 1).

[0003] “What is Vehicle Movement Management? Learn about the Benefits and Key Points of Vehicle Movement Management Systems,” [online], July 13, 2020, BIPROGY Group, Ltd., [Retrieved August 26, 2022], Internet <URL: https: / / dr.biprogy.com / column / 2020 / 0713.html>

[0004] A vehicle data collection system according to one aspect of the present disclosure includes an on-board device mounted on a vehicle and a server that collects data from the on-board device, wherein the on-board device includes a data collection unit that collects vehicle data related to the vehicle, a data conversion unit that converts the collected vehicle data into format data of a version corresponding to the type of vehicle data and writes the version into the format data, and a data transmission unit that transmits the format data with the version written to the server, and the server includes a data receiving unit that receives the format data and a data restoration unit that restores the vehicle data from the format data based on the version indicated in the format data.

[0005] The present invention can be realized not only as a vehicle data collection system including such a characteristic processing unit, but also as a vehicle data collection method including steps of such characteristic processing, as a computer program for causing a computer to execute such steps, or as a semiconductor integrated circuit that realizes part or all of the vehicle data collection system.

[0006] FIG. 1 is a diagram illustrating an example of the overall configuration of an operational management system according to an embodiment of the present disclosure. FIG. 2 is a block diagram illustrating an example of the configuration of an in-vehicle device. FIG. 3 is a diagram illustrating an example of the data structure of format data. FIG. 4 is a block diagram illustrating an example of the configuration of a server. FIG. 5 is a diagram illustrating an example of external data included in the format data. FIG. 6 is a diagram illustrating a conversion process of vehicle data. FIG. 7 is a diagram illustrating a conversion process of vehicle data. FIG. 8 is a diagram illustrating an example of vehicle data restored by converting the format data. FIG. 9 is a block diagram illustrating an example of the configuration of an administrator terminal. FIG. 10 is a diagram illustrating an example of screen information displayed on a display unit. FIG. 11 is a diagram illustrating an example of screen information displayed on the display unit. FIG. 12 is a diagram illustrating an example of screen information displayed on the display unit. FIG. 13 is a diagram illustrating an example of screen information displayed on the display unit. FIG. 14 is a diagram illustrating an example of screen information displayed on the display unit. FIG. 15 is a sequence diagram illustrating an example of a processing procedure of the operational management system. FIG. 16 is a sequence diagram illustrating an example of a processing procedure of the operational management system. FIG. 17 is a sequence diagram illustrating an example of a processing procedure of the operational management system. FIG. 18 is a sequence diagram illustrating an example of a processing procedure by the operational management system. FIG. 19 is a sequence diagram illustrating an example of a processing procedure by the operational management system.

[0007] [Problem to be Solved by the Present Disclosure] For example, the types of sensors installed in each vehicle of a parcel delivery company and a car sharing service provider differ. Furthermore, even in delivery vehicles managed by the same delivery company, the types of sensors installed may differ depending on the type of parcel. For example, delivery vehicles that deliver frozen and refrigerated goods may be equipped with temperature sensors, but delivery vehicles that deliver parcels that do not require temperature control may not be equipped with temperature sensors.

[0008] This poses a problem for the server that performs the dynamic state management in that the process of determining the vehicle data to be collected from each vehicle is complicated.

[0009] The present disclosure has been made in consideration of the above circumstances, and aims to provide a vehicle data collection system, an on-board device, a server, a computer program, and a vehicle data collection method that can efficiently collect vehicle data from multiple vehicles equipped with different numbers and types of sensors.

[0010] Effect of the Present Disclosure According to the present disclosure, vehicle data can be efficiently collected from a plurality of vehicles equipped with different numbers and types of sensors.

[0011] [Outline of Embodiments of the Present Disclosure] First, an outline of an embodiment of the present disclosure will be described. (1) A vehicle data collection system according to one embodiment of the present disclosure includes an on-board device mounted on a vehicle and a server that collects data from the on-board device, the on-board device including a data collection unit that collects vehicle data related to the vehicle, a data conversion unit that converts the collected vehicle data into format data of a version corresponding to a type of the vehicle data and writes the version into the format data, and a data transmission unit that transmits the format data with the version written therein to the server, the server including a data receiving unit that receives the format data and a data restoration unit that restores the vehicle data from the format data based on the version indicated in the format data.

[0012] According to this, a version is determined according to the type of vehicle data, and the vehicle data is converted into format data of a version corresponding to the type of vehicle data. In other words, the vehicle data is converted into format data in a data format corresponding to the version. The format data is then transmitted from the in-vehicle device to the server. Therefore, the server can restore the format data into vehicle data using a conversion method corresponding to each version, using the version as a clue. This allows the server to efficiently collect vehicle data from multiple vehicles equipped with different numbers and types of sensors.

[0013] (2) In the above (1), the server may further include a display control unit that displays the vehicle data restored by the data restoration unit.

[0014] This makes it possible to display on the screen vehicle data collected from multiple vehicles equipped with different numbers and types of sensors.

[0015] (3) In (2) above, the server may further include a display item information acquisition unit that acquires display item information indicating the type of vehicle data to be displayed, and a vehicle data selection unit that selects the vehicle data of the type indicated by the display item information from the restored vehicle data, and the display control unit may display the vehicle data selected by the vehicle data selection unit.

[0016] This allows the administrator to display the type of vehicle data he or she desires from among the vehicle data collected by the server.

[0017] (4) In (2) or (3) above, the data collection unit may collect the position of the vehicle as the vehicle data, the data receiving unit may further receive notification data notified by the vehicle's crew, and the display control unit may further display the notification data received by the data receiving unit in correspondence with the position of the vehicle on a map based on the vehicle data.

[0018] For example, if a crew member notifies a rest area, the rest area is displayed on the map. This allows other crew members who see the display to be notified of the rest area. In this way, notification data can be shared among multiple crew members or users.

[0019] (5) In any of (2) to (4) above, the data collection unit may collect, as the vehicle data, data regarding at least one of the amount of carbon dioxide inside the vehicle, the amount of odor inside the vehicle, and the breath alcohol concentration of the vehicle's crew, and the location of the vehicle, and the display control unit may display, based on the vehicle data, data regarding at least one of the amount of carbon dioxide inside the vehicle, the amount of odor inside the vehicle, and the breath alcohol concentration of the vehicle's crew restored by the data restoration unit, in correspondence with the location of the vehicle on a map.

[0020] This makes it possible to identify vehicles and their locations where there are abnormalities in the amount of carbon dioxide inside the vehicle, the amount of odor inside the vehicle, or the breath alcohol concentration of the driver.

[0021] (6) In any of (1) to (5) above, the vehicle data collection system may further include a conversion rule information registration unit that registers conversion rule information indicating the version and a conversion method corresponding to the version in the on-board device and the server, and the conversion method may include a method of conversion between the vehicle data and the format data.

[0022] This means that even if a new sensor is added to the vehicle and vehicle data collected by the on-board device is added, the on-board device and server can perform data conversion between vehicle data and format data in accordance with the new conversion rule information.

[0023] (7) An in-vehicle device according to another embodiment of the present disclosure includes a data collection unit that collects vehicle data, which is data related to a vehicle; a data conversion unit that converts the collected vehicle data into format data of a version corresponding to the type of the vehicle data and writes the version into the format data; and a data transmission unit that transmits the format data with the version written therein to a server.

[0024] This configuration is similar to the in-vehicle device provided in the above-described vehicle data collection system, and therefore can provide the same functions and effects as the above-described vehicle data collection system.

[0025] (8) A server according to another embodiment of the present disclosure includes a data receiving unit that receives format data in which vehicle data, which is data related to a vehicle, is converted according to a version corresponding to the type of the vehicle data, and the format data has the version written therein; and a data restoration unit that restores the vehicle data from the format data based on the version indicated in the format data.

[0026] This configuration is similar to the server provided in the vehicle data collection system described above, and therefore can provide the same functions and effects as the vehicle data collection system described above.

[0027] (9) A computer program according to another embodiment of the present disclosure causes a computer to function as a data collection unit that collects vehicle data, which is data related to a vehicle; a data conversion unit that converts the collected vehicle data into format data of a version corresponding to the type of vehicle data and writes the version into the format data; and a data transmission unit that transmits the format data with the version written to a server.

[0028] According to this configuration, the computer can function as an in-vehicle device provided in the vehicle data collection system described above, thereby achieving the same functions and effects as those of the vehicle data collection system described above.

[0029] (10) A computer program according to another embodiment of the present disclosure causes a computer to function as a data receiving unit that receives format data in which vehicle data, which is data related to a vehicle, is converted according to a version corresponding to the type of the vehicle data, and in which the version is written, and a data restoring unit that restores the vehicle data from the format data based on the version indicated in the format data.

[0030] According to this configuration, the computer can function as a server provided in the vehicle data collection system described above, thereby achieving the same functions and effects as those of the vehicle data collection system described above.

[0031] (11) A vehicle data collection method according to another embodiment of the present disclosure includes the steps of: an on-board device mounted on a vehicle collecting vehicle data, which is data related to the vehicle; the on-board device converting the collected vehicle data into format data of a version corresponding to the type of the vehicle data and writing the version to the format data; the on-board device transmitting the format data with the version written therein to a server; the server receiving the format data; and the server restoring the vehicle data from the format data based on the version indicated in the format data.

[0032] This configuration includes the characteristic processing steps of the above-described vehicle data collection system, and therefore, this configuration can provide the same functions and effects as the above-described vehicle data collection system.

[0033] [Details of the Embodiments of the Present Disclosure] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Note that each of the embodiments described below represents a specific example of the present disclosure. The numerical values, shapes, materials, components, component placement and connection configurations, steps, and step order shown in the following embodiments are examples and do not limit the present disclosure. Furthermore, among the components in the following embodiments, components not recited in independent claims are components that can be added arbitrarily. Furthermore, each figure is a schematic diagram and is not necessarily a precise illustration.

[0034] The same components are denoted by the same reference numerals, and their functions and names are also the same, so their explanations will be omitted where appropriate.

[0035] Overall Configuration of Traffic Management System FIG. 1 is a diagram illustrating an example of the overall configuration of a traffic management system according to an embodiment of the present disclosure.

[0036] The operation management system 1 includes an in-vehicle device 3A and an in-vehicle device 3B, a smartphone 4A and a smartphone 4B, a server 5, and an administrator terminal 7. The in-vehicle device 3A and the in-vehicle device 3B are mounted on the vehicle 2A and the vehicle 2B, respectively. The smartphones 4A and 4B are carried by crew members such as drivers of the vehicle 2A and the vehicle 2B, respectively. The smartphones 4A and 4B are examples of terminal devices carried by crew members. Therefore, a terminal device that can be carried by a crew member, such as a tablet terminal or a laptop computer, can also be used instead of the smartphones 4A and 4B.

[0037] The in-vehicle devices 3A and 3B and the smartphones 4A and 4B are connected wirelessly to the network 8. The server 5 and the administrator terminal 7 are connected to the network 8 wirelessly or by wire.

[0038] Vehicles 2A and 2B are collectively referred to as vehicles 2, in-vehicle devices 3A and 3B are collectively referred to as in-vehicle devices 3, and smartphones 4A and 4B are collectively referred to as smartphones 4. In FIG. 1 , the number of vehicles 2, in-vehicle devices 3, and smartphones 4 is two, but there may be three or more.

[0039] The in-vehicle device 3 collects vehicle data, which is data related to the vehicle 2, and transmits the collected vehicle data to the server 5 via the network 8. The vehicle data includes measurement results from various sensors installed in the vehicle 2. Details of the vehicle data will be described later.

[0040] The smartphone 4 accepts input of notification data notified by the driver of the vehicle 2 and transmits the notification data to the server 5 via the network 8. The notification data includes data useful for the operation of the vehicle 2. The notification data includes, for example, rest areas for the vehicle 2, locations of police traffic enforcement, locations of traffic accidents, and locations where any complaints have been made. For example, a number is associated in advance with each piece of notification data, and when the driver operates the smartphone 4 to input a number, the smartphone 4 transmits the notification data corresponding to the number to the server 5.

[0041] The server 5 receives the vehicle data and the notification data from the in-vehicle device 3 and the smartphone 4 via the network 8 , respectively, and displays the received vehicle data and notification data on the display of the administrator terminal 7 .

[0042] The administrator terminal 7 is a terminal device used by the administrator of the vehicle 2, and issues instructions for screen display to the server 5. The administrator terminal 7 receives screen information for display from the server 5 via the network 8 and displays it on the display of the administrator terminal 7.

[0043] [Configuration of the In-Vehicle Device 3] FIG. 2 is a block diagram showing an example of the configuration of the in-vehicle device 3. As shown in FIG.

[0044] The in-vehicle device 3 includes a communication unit 31, an interface unit 32, a storage device 33, and a processor 36. The communication unit 31, the interface unit 32, the storage device 33, and the processor 36 are connected to one another via a bus or the like.

[0045] The communication unit 31 includes a communication module for wirelessly connecting the in-vehicle device 3 to the network 8. The communication unit 31 transmits and receives data to and from other devices via the network 8. The communication unit 31 may be provided in a device separate from the in-vehicle device 3.

[0046] The interface unit 32 connects the in-vehicle device 3 to a sensor group 11 , an in-vehicle control device 12 , a GPS (Global Positioning System) receiver 13 , and a clock 14 that are mounted on the vehicle 2 .

[0047] The storage device 33 is composed of a volatile memory element such as an SRAM (Static Random Access Memory) or a DRAM (Dynamic Random Access Memory), a non-volatile memory element such as a flash memory or an EEPROM (Electrically Erasable Programmable Read Only Memory), or a magnetic storage device such as a hard disk.

[0048] The storage device 33 stores the computer program 34 executed by the processor 36. The storage device 33 also stores data used or generated during execution of the computer program 34. The data used or generated during execution of the computer program 34 includes, for example, conversion rule information 35, which will be described later.

[0049] The processor 36 is composed of a CPU (Central Processing Unit) and the like, and includes a data collection unit 37, a data conversion unit 38, and a data transmission unit 39 as functional processing units realized by reading and executing the computer program 34 stored in the storage device 33.

[0050] The data collection unit 37 collects vehicle data from the sensor group 11 , the on-board control device 12 , the GPS receiver 13 and the clock 14 via the interface unit 32 .

[0051] The sensor group 11 includes sensors that output measurement values ​​related to the state of the vehicle 2, such as the running state of the vehicle 2 or the interior environment of the vehicle 2. The sensor group 11 includes, for example, a temperature sensor, an illuminance sensor, a carbon dioxide (hereinafter referred to as "CO2") sensor, an odor sensor, and a breath sensor.

[0052] The temperature sensor measures the temperature inside or outside the vehicle 2. The humidity sensor measures the humidity inside or outside the vehicle 2. The illuminance sensor measures the illuminance inside the vehicle 2.

[0053] The CO2 sensor measures the amount of CO2 inside the vehicle 2. The amount of CO2 increases when ventilation inside the vehicle 2 is insufficient. Maintaining the amount of CO2 below a certain level is effective in preventing crew members from falling asleep or from contracting infectious diseases. The CO2 sensor may measure the CO2 concentration instead of the amount of CO2.

[0054] The odor sensor measures the amount of odor inside the vehicle 2. The amount of odor is expressed, for example, by the concentration of volatile organic compounds, which are the source substances of the odor. Volatile organic compounds include, for example, formaldehyde, acetaldehyde, toluene, xylene, and ethylbenzene. The breath sensor measures the breath alcohol concentration of the driver of the vehicle 2.

[0055] The data collection unit 37 collects the measurement results of each sensor (temperature, humidity, illuminance, CO2 amount, odor amount, alcohol amount, etc.) as vehicle data. Note that the data collection unit 37 may collect CO2 concentration instead of CO2 amount.

[0056] The data collection unit 37 also collects data flowing over the in-vehicle network of the vehicle 2 as vehicle data. When the in-vehicle network is configured using a Controller Area Network (CAN), the data flowing over the in-vehicle network is called CAN information. The CAN information is information output by an in-vehicle control device 12 such as an Electronic Control Unit (ECU), and includes, for example, information such as the acceleration, angular velocity, engine speed, battery voltage, remaining fuel, and State of Charge (SOC) of the vehicle 2.

[0057] The data collection unit 37 also collects, as vehicle data, the position information of the vehicle 2 measured by the GPS receiver 13. The position information of the vehicle 2 is indicated by, for example, latitude, longitude, and altitude. The data collection unit 37 also collects current time information output by the clock 14.

[0058] The data conversion unit 38 converts the vehicle data sets collected by the data collection unit 37 into format data. Format data refers to data in a predetermined data format. In the following description, the "vehicle data sets" will also be referred to as "vehicle data."

[0059] 3 is a diagram showing an example of the data structure of the format data. The format data includes a timestamp indicated by the tag "datetime", an identifier of the in-vehicle device 3 (hereinafter referred to as "in-vehicle device ID") indicated by the tag "terminal_code", and a vehicle data structure indicated by the tag "parameters". The timestamp value "1600902266000" is calculated based on current time information collected from the clock 14. The in-vehicle device ID value "D1" is pre-stored in the storage device 33. The data conversion unit 38 reads the in-vehicle device ID "D1" from the storage device 33 and writes it into the format data.

[0060] The vehicle data structure indicated by the tag “parameters” includes vehicle data collected from the CAN information, vehicle data collected from the GPS receiver 13, and vehicle data collected from the sensor group 11.

[0061] Of the vehicle data structures indicated by the tag "parameters", vehicle data other than the vehicle data structure indicated by the tag "external" is vehicle data that is normally transmitted from the vehicle 2 (hereinafter referred to as "standard data"). The standard data is data that is commonly transmitted by all vehicles 2. The standard data includes, for example, vehicle data indicated by the tags "ac_l", "ac_x", "ac_y", "ac_z", "av_l", "av_x", "av_y", "av_z", "rssi_db", "co_lat", "co_log", "co_alt", "dir", "sat_no", and "speed". As an example, the vehicle data indicated by the tag "ac_l" represents an average acceleration (scalar). The vehicle data indicated by the tag "ac_x" represents a preset average acceleration in the x-axis direction. Vehicle data indicated by the tag "ac_y" represents the average acceleration in the y-axis direction, which is set in advance. Vehicle data indicated by the tag "ac_z" represents the acceleration in the z-axis direction, which is set in advance. Vehicle data indicated by the tags "co_lat", "co_log", and "co_alt" represent the latitude, longitude, and altitude of vehicle 2, respectively. Vehicle data indicated by the tag "dir" represents the direction of vehicle 2. Vehicle data indicated by the tag "spd" represents the speed of vehicle 2.

[0062] The type of vehicle data included in the data structure indicated by the tag "external" (hereinafter referred to as "external data") differs for each vehicle 2. The external data includes a version (data indicated by the tag "v") corresponding to the type of vehicle data included in the external data. In other words, the version defines the type of vehicle data included in the external data and the arrangement of the vehicle data. The type of vehicle data indicates the type of sensor measurement result. For example, temperature indicates the measurement result of a temperature sensor, and humidity indicates the measurement result of a humidity sensor, so the types of sensor measurement results differ. Therefore, the type of vehicle data indicating temperature differs from the type of vehicle data indicating humidity. Note that the type of vehicle data may also indicate the type of measurement result indicated by the vehicle data and the type of sensor that outputs the measurement result. In this case, for example, even if two pieces of vehicle data each indicate the temperature inside the vehicle 2, if the types of sensors that measure the temperature are different, the types of vehicle data are different. The conversion rule information 35 includes information indicating the type of vehicle data included in the external data and the arrangement of the vehicle data for each version. The conversion rule information 35 also includes a conversion rule for converting vehicle data into format data for each version.

[0063] The external data includes, for example, data indicated by the tags "cabintemp", "data1", "data2", "data3", "data4", "data5", "data6", and "carstatus", respectively, as vehicle data of version 1.0. The data indicated by the tag "cabintemp" is 8-bit data and indicates the temperature inside vehicle 2. The data indicated by the tags "data1", "data2", "data3", "data4", "data5", and "data6" is 16-bit data. Each of these data is data generated by combining one vehicle data item or two or more vehicle data items. For example, the data indicated by the tag "data1" indicates the humidity inside vehicle 2 and the voltage of the battery installed in vehicle 2. The data indicated by the tag "data2" indicates the illuminance inside vehicle 2. The data indicated by the tag "data3" represents the remaining fuel amount of vehicle 2 and the speed of vehicle 2. The data indicated by the tag "data4" represents the temperature outside vehicle 2 (outside air temperature) and the fuel type of vehicle 2. The data indicated by the tag "data5" represents the fuel consumption of vehicle 2. The data indicated by the tag "data6" represents the amount of intake air of vehicle 2 measured by the MAF (Mass flow sensor). The data indicated by the tag "carstatus" is 8-bit data and represents the engine status (engine speed) of vehicle 2.

[0064] The data conversion unit 38 converts the vehicle data collected by the data collection unit 37 into external data in accordance with a predetermined conversion rule. For example, the data conversion unit 38 converts the temperature inside the vehicle 2 collected by the data collection unit 37 in accordance with a predetermined calculation formula, thereby converting the data into data indicated by an 8-bit tag "cabintemp". The data conversion unit 38 also combines multiple converted data items in accordance with a predetermined combination rule to generate one piece of data. For example, the data conversion unit 38 combines the converted humidity inside the vehicle 2 with the converted battery voltage to generate data indicated by the tag "data1". The conversion rules and combination rules, including the calculation formula, are assumed to be stored in the conversion rule information 35.

[0065] The data transmission unit 39 transmits the format data generated by the data conversion unit 38 through the communication unit 31 to the server 5 .

[0066] 4 is a block diagram showing an example of the configuration of the server 5. The server 5 includes a communication unit 51, a storage device 52, and a processor 58. The communication unit 51, the storage device 52, and the processor 58 are connected to each other via a bus or the like.

[0067] The communication unit 51 includes a communication module for connecting the server 5 to the network 8 wirelessly or via a wired connection. The communication unit 51 transmits and receives data to and from other devices via the network 8.

[0068] The storage device 52 is configured by a volatile memory element such as an SRAM or a DRAM, a non-volatile memory element such as a flash memory or an EEPROM, or a magnetic storage device such as a hard disk.

[0069] The storage device 52 stores a computer program 53 executed by the processor 58. The storage device 52 also stores data used or generated during execution of the computer program 53. The data used or generated during execution of the computer program 53 includes, for example, conversion rule information 54, vehicle data 55, notification data 56, and display item information 57.

[0070] The conversion rule information 54 includes conversion rules for converting format data and restoring vehicle data from the format data. The conversion rule information 54 includes conversion rules for each version of format data. The vehicle data 55 is a set of vehicle data restored from the format data. The notification data 56 is notification data transmitted from the smartphone 4. The display item information 57 is information indicating the type of vehicle data to be displayed.

[0071] The processor 58 is configured with a CPU etc. The processor 58 reads and executes the computer program 53 stored in the storage device 52. The processor 58 includes, as functional processing units, a data receiving unit 59, a data restoring unit 60, a display control unit 61, a display item information acquiring unit 62, a vehicle data selecting unit 63, and a conversion rule information registering unit 64.

[0072] The data receiving unit 59 receives data transmitted by the in-vehicle device 3, the smartphone 4, and the administrator terminal 7 via the communication unit 51. Specifically, the data receiving unit 59 receives format data transmitted by the in-vehicle device 3. The data receiving unit 59 may write the received format data directly to the storage device 52. The data receiving unit 59 receives notification data transmitted by the smartphone 4. The data receiving unit 59 receives various information such as screen display instruction information transmitted by the administrator terminal 7.

[0073] The data restoration unit 60 restores the vehicle data from the format data based on the version indicated in the format data received by the data receiving unit 59. More specifically, the data restoration unit 60 reads the version from the external data in the format data, and reads the conversion rule information 54 corresponding to the read version from the storage device 52. The data restoration unit 60 restores the vehicle data by converting the vehicle data included in the external data of the format data based on the read conversion rule information 54.

[0074] An example of a method for restoring vehicle data will be described below. FIG. 5 is a diagram showing an example of external data included in format data. The external data includes vehicle data of version 1.0 indicated by the tag "v". That is, the external data includes data indicated by the tags "cabintemp", "data1", "data2", "data3", "data4", "data5", "data6", and "carstatus", respectively.

[0075] The value of the data indicated by the tag "cabintemp" is 108 in decimal notation. The value of the data indicated by the tag "data1" is 29439 in decimal notation. The value of the data indicated by the tag "data2" is 418 in decimal notation. The value of the data indicated by the tag "data3" is 12323 in decimal notation. The value of the data indicated by the tag "data4" is 17665 in decimal notation. The value of the data indicated by the tag "data5" is 356 in decimal notation. The value of the data indicated by the tag "data6" is 52719 in decimal notation. The value of the data indicated by the tag "carstatus" is 0 in decimal notation. The type, arrangement, and size of each vehicle data are specified in the conversion rule information 54 for each version.

[0076] FIG. 6 is a diagram illustrating the conversion process of vehicle data. The table shown in FIG. 6 includes five columns (tag name, decimal number, hexadecimal number, decomposition, and decomposition decimal number). "Tag name" indicates the item (tag name) of data included in the external data. "Decimal number" indicates the value of the data expressed in decimal. The data restoration unit 60 extracts from the external data the value expressed in decimal number indicated in "Decimal number" for each data item indicated in "Item".

[0077] "Hexadecimal" indicates the hexadecimal value of the data. Here, data items that are subject to hexadecimal representation are stored for each version in the conversion rule information 54. The data restoration unit 60 expresses the subject data (here, the decimal values ​​indicated by the tags "data1," "data3," "data4," "data5," and "data6") in hexadecimal based on the conversion rule information 54 and the version of the external data.

[0078] The data restoration unit 60 breaks down the hexadecimal value into the most significant two digits and the least significant two digits, and expresses each in decimal.

[0079] "Decomposition" indicates the upper two digits and the lower two digits of a hexadecimal value. "Decomposed Decimal" indicates the decimal representation of the decomposed hexadecimal data. Furthermore, "Decomposed Decimal" indicates the decimal representation of data that is not subject to hexadecimal representation. For example, the decimal representation of the data indicated by the tag "data1" is 29439, and the hexadecimal representation of that data is 72FF. Furthermore, the decimal representation of the decomposed hexadecimal data is 114 and 255.

[0080] FIG. 7 is a diagram illustrating the vehicle data conversion process. The table shown in FIG. 7 includes six columns (tag name, data size, item, calculation formula, resolved decimal number, and converted value). "Tag name" is the same as that shown in FIG. 6 and indicates the item (tag name) of data included in the external data. "Data size" indicates the size of the data indicated by the tag name. In the case of data that is the target of hexadecimal representation, "data size" indicates the size of the data in the most significant two digits and the least significant two digits. "Item" indicates the item of the vehicle data after conversion. "Calculation formula" indicates the calculation formula for converting the data indicated in "Resolved decimal number." "Resolved decimal number" indicates the value in decimal representation before conversion. The value of "Resolved decimal number" is the same as "Resolved decimal number" shown in FIG. 6. "Converted" indicates the value obtained after the value indicated in "Resolved decimal number" is converted according to the calculation formula indicated in "Calculation formula."

[0081] The calculation formula shown in "Calculation formula" is stored in the conversion rule information 54 for each version. For example, the data restoration unit 60 derives a temperature of 24.6°C by substituting the value 108 of the "Decomposed Decimal Number" of the tag "cabintemp" for the variable "cabintemp" of the calculation formula "((cabintemp / 256)*165)-45". In addition, the data restoration unit 60 derives a humidity of 59.5% by substituting the value 114 of the higher-order "Decomposed Decimal Number" of the tag "data1" for the variable A of the calculation formula "(A / 256)*100+15". In addition, the data restoration unit 60 derives a fuel consumption of 17.8 km / L by substituting the value 1 of the upper "decomposed decimal number" of the tag "data5" and the value 100 of the lower "decomposed decimal number" of the tag "data5" into the variables A and B of the calculation formula "(256*A+B) / 20", respectively.

[0082] FIG. 8 is a diagram showing an example of vehicle data 55 restored by converting the format data. The vehicle data 55 includes an in-vehicle device ID, standard data, and external data. The in-vehicle device ID includes data indicated by the tag "terminal_code" in the format data shown in FIG. 3. The standard data includes data other than the data indicated by the tag "external" in the vehicle data structure indicated by the tag "parameters" in the format data. The external data includes the version of the external data and the value of the external data after conversion shown in FIG. 7.

[0083] The data restoration unit 60 stores the restored vehicle data 55 in the storage device 52 for each in-vehicle device ID.

[0084] The display control unit 61 transmits screen information including at least one of the vehicle data 55 and the notification data 56 stored in the storage device 52 to the administrator terminal 7 via the communication unit 51. This causes the administrator terminal 7 to display the screen information including at least one of the vehicle data 55 and the notification data 56.

[0085] The display item information acquisition unit 62 receives display item information indicating the types of vehicle data that the manager of the vehicle 2 wishes to display from the manager terminal 7 via the communication unit 51. The display item information acquisition unit 62 stores the received display item information 57 in the storage device 52.

[0086] The vehicle data selection unit 63 selects vehicle data of the type indicated by the display item information 57 from the vehicle data 55 stored in the storage device 52. The vehicle data selection unit 63 outputs the selected vehicle data to the display control unit 61. The display control unit 61 generates screen information including the vehicle data selected by the vehicle data selection unit 63 and transmits it to the administrator terminal 7 via the communication unit 51. This allows the administrator terminal 7 to display screen information including the vehicle data selected based on the display item information 57.

[0087] Furthermore, when the data receiving unit 59 receives various kinds of screen display instruction information, the vehicle data selecting unit 63 selects vehicle data based on the instruction information from the vehicle data 55. For example, when screen display instruction information for vehicle data of a vehicle 2 for which an alcohol check has not been completed is received, the vehicle data selecting unit 63 selects vehicle data of the vehicle 2 for which an alcohol check has not been completed from the vehicle data 55. The selected vehicle data is displayed on the administrator terminal 7 in the same manner as described above.

[0088] The conversion rule information registration unit 64 registers the conversion rule information 54 by writing it to the storage device 52. The conversion rule information registration unit 64 also registers the conversion rule information in the on-board device 3 by transmitting the conversion rule information for generating format data from vehicle data to the on-board device 3 via the communication unit 51. For example, the conversion rule information registration unit 64 registers the conversion rule information when a new type of sensor is additionally installed in the vehicle 2. When a new type of sensor is additionally installed, the measurement results of the additional sensor cannot be converted into format data using existing conversion rule information. For this reason, the conversion rule information registration unit 64 creates mutual conversion rule information between the new vehicle data and the format data, including the conversion rule for the measurement results of the additional sensor. The conversion rule information registration unit 64 also assigns a new version to the new conversion rule information.

[0089] The conversion rule information registration unit 64 may be provided in a device external to the server 5. For example, the conversion rule information registration unit 64 may be provided in the administrator terminal 7, and the administrator terminal 7 may register the conversion rule information of the in-vehicle device 3 and the server 5.

[0090] 9 is a block diagram showing an example of the configuration of the administrator terminal 7. The administrator terminal 7 includes a communication unit 71, an input unit 72, a display unit 73, a processor 74, and a storage device 75. The communication unit 71, the input unit 72, the display unit 73, the processor 74, and the storage device 75 are connected to each other via a bus, a communication line, or the like.

[0091] The communication unit 71 includes a communication module for connecting the administrator terminal 7 to the network 8 wirelessly or via a wired connection. The communication unit 71 transmits and receives data to and from other devices via the network 8.

[0092] The input unit 72 is an input device used by the administrator who uses the administrator terminal 7 to input data, and includes, for example, a keyboard or a mouse.

[0093] The display unit 73 is an output device for displaying data, and includes, for example, a display using a liquid crystal or an organic electroluminescence (EL) display. The processor 74 is configured with a CPU and the like, and performs processing such as calculations according to a computer program.

[0094] The storage device 75 is configured by a volatile memory element such as an SRAM or a DRAM, a non-volatile memory element such as a flash memory or an EEPROM, or a magnetic storage device such as a hard disk. The storage device 75 stores a computer program 76 executed by the processor 74. The storage device 75 also stores data used or generated when the computer program 76 is executed.

[0095] The processor 74 receives screen information for display from the server 5 via the communication unit 71 and causes the display unit 73 to display the received screen information.

[0096] Fig. 10 is a diagram showing an example of screen information displayed on the display unit 73. A vehicle data screen 100 shown in Fig. 10 is an example of screen information, and shows the location of a vehicle 2 in which a driver is riding who has not completed a breath alcohol concentration test (alcohol check).

[0097] Vehicle data screen 100 shows, for example, vehicle icons 111A, 111B, and 111C and mug icons 112A, 112B, and 112C on a map. In the following, when there is no need to distinguish between vehicle icons 111A, 111B, and 111C, they will be referred to as vehicle icons 111, and when there is no need to distinguish between mug icons 112A, 112B, and 112C, they will be referred to as mug icons 112.

[0098] A vehicle icon 111 is displayed at the location on the map of a vehicle 2 for which an alcohol test has not been completed. The direction of the tip of the vehicle icon 111 indicates the traveling direction of the vehicle 2. For example, the vehicle 2 indicated by the vehicle icon 111A can be seen to be traveling from left to right on the page. A mug icon 112 is displayed near the vehicle icon 111. The mug icon 112 is an icon indicating that the alcohol test of the driver has not been completed. Note that a vehicle 2 that similarly exhibits abnormal values ​​for the CO2 amount and odor amount inside the vehicle 2 (for example, exhibits a CO2 amount or odor amount above a predetermined threshold) may be displayed on the map using the vehicle icon 111. An icon indicating the type of vehicle data that exhibits an abnormal value may also be displayed near the vehicle icon 111. Note that the CO2 concentration inside the vehicle 2 may be used instead of the CO2 amount inside the vehicle 2.

[0099] Fig. 11 is a diagram showing an example of screen information displayed on the display unit 73. The vehicle data screen 110 shown in Fig. 11 is an example of screen information, and shows a list of vehicle data for the vehicles 2 managed by the administrator. For example, the vehicle data screen 110 includes multiple records for each vehicle 2, each consisting of 11 items (display, vehicle name, status, driver name, alcohol check, SOC, remaining fuel, remaining battery, outside temperature, odor, and notification data).

[0100] The item "Display" indicates whether or not the location of the vehicle 2 is shown by a vehicle icon 111 superimposed on a map on the vehicle data screen 100 as shown in Fig. 10. The locations of the vehicles 2 (here, vehicles with the vehicle names Vehicle B, Vehicle F, and Vehicle H) for which the item "Display" is checked are shown on the vehicle data screen 100.

[0101] The item "Vehicle Name" indicates a list of the names of the vehicles 2 managed by the administrator. The names of the vehicles 2 managed by the administrator are managed by the server 5 in association with, for example, the in-vehicle device IDs.

[0102] The item "Status" is an icon that indicates the status of vehicle 2 or the crew of vehicle 2. The icon shown in the item "Status" is superimposed on the map on the vehicle data screen 100. For example, a vehicle icon 111 indicating that some kind of abnormality has occurred in vehicle 2 or the crew of vehicle 2 is displayed on the map, and an icon indicating the nature of the abnormality is displayed near the vehicle icon 111.

[0103] The icons indicating the abnormality include, for example, a mug icon 112, a gas station icon 114, and a battery icon 115. When the mug icon 112 is displayed, it indicates that the alcohol check of the driver of the vehicle 2 has not been completed, as described above. When the gas station icon 114 is displayed, it indicates that the remaining fuel of the vehicle 2 is low (for example, the remaining fuel is below a predetermined fuel threshold). When the battery icon 115 is displayed, it indicates that the SOC of the battery of the vehicle 2 is abnormal (for example, the SOC is below a predetermined SOC threshold).

[0104] Also, a vehicle icon 113 is displayed on the map, indicating that no abnormalities have been detected by vehicle 2 or the crew of vehicle 2.

[0105] Both the vehicle icon 111 and the vehicle icon 113 indicate the position of the vehicle 2, and the direction of the tip indicates the traveling direction of the vehicle 2. As an example, the display mode of the vehicle icon 111 and the vehicle icon 113 differs depending on whether or not they are hatched. This allows the administrator to easily identify whether or not an abnormality has been detected in the vehicle 2.

[0106] The item "crew name" indicates the name of the crew of the vehicle 2. The names of the crew of the vehicle 2 managed by the administrator are managed by the server 5 in association with, for example, the in-vehicle device ID.

[0107] The item "alcohol check" indicates the time elapsed since the driver last measured the breath alcohol concentration using the breath sensor installed in the vehicle 2 and the measurement result was determined to be below the reference value (hereinafter referred to as "alcohol check elapsed time"). If the alcohol check elapsed time is equal to or greater than a predetermined time threshold, a warning icon 116 is displayed near the alcohol check elapsed time.

[0108] The item "SOC" indicates the SOC of the battery mounted on the vehicle 2. If the SOC is less than a predetermined SOC threshold, a warning icon 116 is displayed near the SOC.

[0109] The item "remaining fuel" indicates the remaining fuel amount of the vehicle 2. Here, the remaining fuel amount is a percentage of the remaining fuel amount relative to the tank capacity of the fuel, such as gasoline. If the remaining fuel amount is less than a predetermined remaining fuel amount threshold, a warning icon 116 is displayed near the remaining fuel amount.

[0110] The item "Battery voltage" indicates the voltage of the battery installed in the vehicle 2. If the battery voltage is below a predetermined battery voltage threshold, a warning icon 116 is displayed near the battery voltage threshold. The item "Outside temperature" indicates the temperature outside the vehicle 2 (outside temperature).

[0111] The item "Odor" indicates the odor determination result based on the amount of odor inside the vehicle 2. If the amount of odor is less than a predetermined odor amount threshold, "OK" is displayed, and if the amount of odor is equal to or greater than the odor amount threshold, "NG" is displayed.

[0112] The item "notification data" indicates whether or not there is notification data notified by the crew of vehicle 2. When the notification icon 117 is displayed, it indicates that there is notification data. When the notification icon 117 is not displayed, it indicates that there is no notification data.

[0113] Each item is provided with a sort button 118 shaped, for example, like an inverted triangle. When the administrator presses the sort button 118 for any item, the processor 74 sorts and displays the records in ascending or descending order of the values ​​of the item to which the pressed sort button 118 belongs.

[0114] It should be noted that the vehicle data 55 of version 1.0 shown in FIG. 8 does not include breath alcohol concentration, SOC, and odor amount, but these data are included in the vehicle data 55 of other versions.

[0115] Fig. 12 is a diagram showing an example of screen information displayed on the display unit 73. A vehicle data screen 120 shown in Fig. 12 is an example of screen information, and shows the notification position of notification data from the vehicle 2 and the content of the notification data.

[0116] The vehicle data screen 120, for example, displays a notification icon 131 at the notification position of the notification data on a map, and displays notification data content 132 near the notification icon 131. By looking at the vehicle data screen 120, the administrator can know that there is a rest area at the position of the notification icon 131.

[0117] Fig. 13 is a diagram showing an example of screen information displayed on the display unit 73. A setting screen 130 shown in Fig. 13 is an example of screen information, and is a screen for selecting display items indicating the types of vehicle data to be displayed on the vehicle data screen 110 shown in Fig. 11.

[0118] The vehicle data screen 110 displays a list of display item candidates with a check box to the left of each candidate. The administrator operates the input unit 72 to check the check box and presses the OK button 101. This selects the checked candidate as a display item. For example, the administrator selects alcohol check, battery voltage, SOC, remaining fuel, outside temperature, and odor as display items. The processor 74 transmits display item information indicating the selected display items to the server 5 via the communication unit 71.

[0119] Fig. 14 is a diagram showing an example of screen information displayed on the display unit 73. A management screen 140 shown in Fig. 14 displays a list of information related to the vehicles 2 managed by the manager.

[0120] The management screen 140 includes multiple records each consisting of an on-board device ID, on-board device name, vehicle name, crew name, last operating date and time, version, acceleration, angular velocity, battery voltage, SOC, remaining fuel, etc. "On-board device ID" is an identifier for the on-board device 3 installed in the vehicle 2. "On-board device name" is the name of the on-board device 3. "Vehicle name" is the name of the vehicle 2. "Crew name" is the name of the crew of the vehicle 2. "Last operating date and time" indicates the last operating date and time of the vehicle 2. The last operating date and time indicates, for example, the date and time when the vehicle 2 stopped, which is identified by the server 5 based on the speed or position of the vehicle 2.

[0121] "Version" indicates the version of the external data. "Acceleration," "Angular velocity," "Battery voltage," "SOC," "Remaining fuel amount," and the like indicate each vehicle data of the vehicle 2.

[0122] Each item is provided with a sort button 118 shaped, for example, like an inverted triangle. When the administrator presses the sort button 118 for any item, the processor 74 sorts and displays the records in ascending or descending order of the values ​​of the item to which the pressed sort button 118 belongs.

[0123] [Processing Procedure of Traffic Management System 1] Fig. 15 is a sequence diagram showing an example of the processing procedure of the traffic management system 1. Fig. 15 shows the processing procedure for collecting vehicle data from the in-vehicle device 3. The data collection unit 37 of the in-vehicle device 3 collects current time information from the clock 14 (step S1).

[0124] The data collection unit 37 of the in-vehicle device 3 collects the position information of the vehicle 2 from the GPS receiver 13 (step S2).

[0125] The data collection unit 37 of the in-vehicle device 3 collects CAN information flowing on the in-vehicle network of the vehicle 2 (step S3).

[0126] The data collection unit 37 of the in-vehicle device 3 collects the measurement results from the group of sensors 11 installed in the vehicle 2 (step S4).

[0127] The data conversion unit 38 of the in-vehicle device 3 converts the data collected by the processes of steps S1 to S4 into format data (step S5). An example of the format data is as shown in FIG.

[0128] The data transmitting unit 39 of the in-vehicle device 3 transmits the format data generated by the process of step S4 to the server 5, and the data receiving unit 59 of the server 5 receives the format data (step S6).

[0129] The data restoration unit 60 of the server 5 restores the vehicle data from the format data received in step S6 (step S7). An example of the restored vehicle data is shown in FIG.

[0130] The data restoration unit 60 of the server 5 stores the restored vehicle data for each in-vehicle device ID in the storage device 52 (step S8). The process shown in Fig. 15 is repeatedly executed at a predetermined cycle.

[0131] 16 is a sequence diagram showing an example of a processing procedure of the traffic management system 1. FIG. 16 shows a processing procedure of a process for collecting notification data from the smartphone 4.

[0132] The driver of vehicle 2 operates smartphone 4 at a location where information useful for the operation of vehicle 2 has been obtained, and inputs the notification data (step S11). For example, the driver launches an app for collecting notification data and inputs a number corresponding to the type of notification data. For example, numbers 1, 2, 3, and 4 are associated with vehicle 2's rest area, police traffic enforcement locations, traffic accident locations, and locations where some kind of complaint has occurred, respectively.

[0133] The smartphone 4 adds the location information of the vehicle 2 and the in-vehicle device ID of the in-vehicle device 3 to the notification data input in step S11 and transmits the result to the server 5, and the server 5 receives the notification data with the location information and the in-vehicle device ID added (step S12). For example, if the driver operates the smartphone 4 to input number 1 corresponding to the rest area, the number "1" as notification data, the location information, and the in-vehicle device ID are transmitted to the server 5.

[0134] The server 5 stores the notification data to which the location information and the in-vehicle device ID received in step S12 have been added in the storage device 52 (step S13).

[0135] 17 is a sequence diagram showing an example of the processing procedure of the traffic control system 1. FIG. 17 shows the processing procedure of the manager terminal 7 for selecting display items to be displayed.

[0136] The administrator inputs, from the input unit 72 of the administrator terminal 7, an instruction to display a setting screen, which is a screen for selecting display items (step S21).

[0137] In response to the input of the display instruction in step S21, the processor 74 of the administrator terminal 7 transmits setting screen display instruction information to the server 5, and the data receiving unit 59 of the server 5 receives the information (step S22).

[0138] The display control unit 61 of the server 5 generates setting screen information for allowing the administrator terminal 7 to select display items to be displayed based on the received setting screen display instruction information (step S23).

[0139] The display control unit 61 of the server 5 transmits the generated setting screen information to the administrator terminal 7, and the processor 74 of the administrator terminal 7 receives the information (step S24).

[0140] The processor 74 of the administrator terminal 7 causes the display unit 73 to display a setting screen based on the received setting screen information (step S25). An example of the setting screen is as shown in FIG. 13.

[0141] The administrator operates the input unit 72 to select display items from the setting screen (step S26).

[0142] The processor 74 of the administrator terminal 7 transmits display item information indicating the selected display items to the server 5, and the display item information acquisition unit 62 of the server 5 receives the display item information (step S27).

[0143] The processor 74 of the administrator terminal 7 writes the received display item information 57 into the storage device 52 (step S28).

[0144] Fig. 18 is a sequence diagram showing an example of a processing procedure by the traffic management system 1. Fig. 18 shows a processing procedure for displaying a vehicle data screen.

[0145] The administrator inputs an instruction to display the vehicle data screen from the input unit of the administrator terminal 7 (step S31). Here, it is assumed that an instruction to display the location of vehicles 2 that have not yet completed alcohol checks has been input.

[0146] In response to the input of the display instruction in step S31, the processor 74 of the administrator terminal 7 transmits vehicle data screen display instruction information to the server 5, and the data receiving unit 59 of the server 5 receives the information (step S32).

[0147] Based on the instruction information, the vehicle data selection unit 63 of the server 5 selects vehicle data of vehicles 2 for which the alcohol check has not been completed from the vehicle data 55 (step S33). Specifically, the vehicle data selection unit 63 calculates the alcohol check elapsed time for each in-vehicle device ID by referring to the vehicle data 55. The vehicle data selection unit 63 selects the latest vehicle data 55 for an in-vehicle device ID for which the alcohol check elapsed time is equal to or greater than a predetermined time threshold.

[0148] The display control unit 61 of the server 5 generates vehicle data screen information based on the vehicle data 55 selected in step S33 (step S34). For example, the display control unit 61 generates vehicle data screen information for displaying a vehicle data screen in which the location of a vehicle 2 for which an alcohol check has not been completed is indicated on a map by a vehicle icon 111 and a mug icon 112, as shown in FIG.

[0149] The display control unit 61 of the server 5 transmits the generated vehicle data screen information to the administrator terminal 7, and the processor 74 of the administrator terminal 7 receives the information (step S35).

[0150] The display control unit 61 of the server 5 causes the display unit 73 to display a vehicle data screen 100 as shown in FIG. 10 based on the received vehicle data screen information (step S36).

[0151] The display process of the vehicle data screen 110 as shown in Fig. 11 is also performed according to the processing procedure shown in Fig. 18. Specifically, in step S31, the administrator inputs an instruction to display a list of vehicle data of the vehicles 2 managed by the administrator.

[0152] In step S33, the vehicle data selection unit 63 of the server 5 reads the latest vehicle data 55 for each in-vehicle device ID from the storage device 52. The vehicle data selection unit 63 refers to the display item information 57 and selects, from the read vehicle data 55, vehicle data of the type indicated by the display item information 57.

[0153] In step S34, the display control unit 61 of the server 5 generates vehicle data screen information for displaying the vehicle data screen 110 as shown in Fig. 11 based on the selected vehicle data and the notification data 56 stored in the storage device 52. As a result, the vehicle data screen 110 is displayed on the administrator terminal 7 in step S35.

[0154] The display process of the vehicle data screen 120 as shown in Fig. 12 is also performed according to the processing procedure shown in Fig. 18. Specifically, in step S31, the administrator inputs an instruction to display the notification position and content of the notification data from the vehicle 2. In this case, the process of step S33 is not executed.

[0155] In step S34, the display control unit 61 generates notification data display screen information for displaying the vehicle data screen 120 as shown in FIG. 12 based on the notification data 56 stored in the storage device 52, instead of the vehicle data screen information.

[0156] In step S35, the display control unit 61 of the server 5 transmits the notification data display screen information to the administrator terminal 7 instead of the vehicle data screen information, and the processor 74 of the administrator terminal 7 receives the information. In step S36, the processor 74 causes the display unit 73 to display a vehicle data screen 120 as shown in FIG. 12 .

[0157] 19 is a sequence diagram showing an example of a processing procedure by the traffic control system 1. Fig. 19 shows the processing procedure for displaying the management screen. The manager inputs a display instruction for the management screen from the input unit of the manager terminal 7 (step S41).

[0158] In response to the input of the display instruction in step S41, the processor 74 of the administrator terminal 7 transmits management screen display instruction information to the server 5, and the data receiving unit 59 of the server 5 receives the information (step S42).

[0159] Based on the instruction information, the display control unit 61 of the server 5 reads the latest vehicle data 55 from the storage device 52 for each in-vehicle device ID (step S43).

[0160] The display control unit 61 of the server 5 generates management screen information for displaying the management screen 140 as shown in FIG. 14 based on the read vehicle data 55 (step S44). It is assumed that correspondence information between the on-board device ID and the on-board device name, vehicle name, and crew name is stored in advance in the storage device 52. The display control unit 61 references this correspondence information to generate the information on the on-board device name, vehicle name, and crew name for the management screen 140. The last operation date and time of the management screen 140 is derived from the timestamp of the vehicle data 55.

[0161] The display control unit 61 of the server 5 transmits the generated management screen information to the administrator terminal 7, and the processor 74 of the administrator terminal 7 receives the information (step S45).

[0162] The display control unit 61 of the server 5 causes the display unit 73 to display a management screen 140 as shown in FIG. 14 based on the received management screen information (step S46).

[0163] According to an embodiment of the present disclosure, a version is determined according to the type of vehicle data collected by the in-vehicle device 3, and the vehicle data is converted into format data of a version corresponding to the type of vehicle data, and then transmitted from the in-vehicle device 3 to the server 5. Therefore, the server 5 can restore the format data to vehicle data using a conversion method appropriate for each version, using the version as a clue. Therefore, the server 5 can efficiently collect vehicle data from multiple vehicles 2 equipped with different numbers and types of sensors.

[0164] In addition, the server 5 can display vehicle data collected from multiple vehicles 2 equipped with different numbers and types of sensors on the administrator terminal 7.

[0165] Furthermore, the server 5 can display on the administrator terminal 7 the vehicle data of the type desired by the administrator from among the vehicle data collected by the server 5 .

[0166] Furthermore, the server 5 can display the notification data collected from multiple vehicles 2 on the manager terminal 7 in association with the positions of the vehicles 2 on a map. For example, when a crew member notifies a rest area, the rest area is displayed on the map. This allows other managers or crew members who see the display to be notified of the rest area. In this way, the notification data can be shared between managers or multiple crew members.

[0167] Furthermore, the server 5 causes the manager terminal 7 to display data relating to at least one of the amount of carbon dioxide inside the vehicle 2, the amount of odor inside the vehicle 2, and the breath alcohol concentration of the driver of the vehicle 2, in association with the position of the vehicle 2 on a map. This allows the manager to identify the vehicle 2 and the position of the vehicle 2 where an abnormality has occurred in the amount of carbon dioxide inside the vehicle 2, the amount of odor inside the vehicle 2, or the breath alcohol concentration of the driver.

[0168] Furthermore, the server 5 registers conversion rule information 54 for restoring vehicle data from format data in the server 5, and also registers conversion rule information for generating format data from vehicle data in the in-vehicle device 3. As a result, even when a new sensor is added to the vehicle 2 and vehicle data collected by the in-vehicle device 3 is added, the in-vehicle device 3 and the server 5 can perform data conversion between vehicle data and format data in accordance with the new conversion rule information.

[0169] [Modification 1] In the above-described embodiment, the smartphone 4 is configured to transmit the notification data to the server 5. However, the in-car device 3 may be configured to transmit the notification data to the server 5.

[0170] For example, a physical switch corresponding to the notification data is provided in a position that can be operated by the occupant, such as on the dashboard of the vehicle 2. The physical switch is connected to the interface unit 32 of the in-vehicle device 3. When the occupant presses any of the physical switches, the data collection unit 37 of the in-vehicle device 3 collects the notification data corresponding to the physical switch, and the data transmission unit 39 transmits the collected notification data to the server 5.

[0171] [Modification 2] In the above-described embodiment, the server 5 transmits the screen information to the administrator terminal 7 and causes the administrator terminal 7 to display the screen information. However, the server 5 may transmit the screen information to the smartphone 4 and cause the smartphone 4 to display the screen information. For example, the vehicle data screen 120 shown in Fig. 12 may be displayed on the smartphone 4. This allows the passengers of the vehicle 2 to be informed of the contents of the notification data.

[0172] [Additional Notes] Some or all of the components constituting each of the above devices may be configured from one or more semiconductor devices such as system LSIs.

[0173] The computer program described above may be recorded on a computer-readable non-transitory recording medium, such as a HDD, a CD-ROM, or a semiconductor memory, and distributed. The computer program may also be transmitted and distributed via a telecommunications line, a wireless or wired communication line, a network such as the Internet, or data broadcasting. Each of the above devices may be realized by multiple computers or multiple processors.

[0174] Furthermore, some or all of the functions of each of the above-described devices may be provided by cloud computing, that is, some or all of the functions of each device may be realized by a cloud server.

[0175] Furthermore, at least some of the above-described embodiments and modifications may be combined in any manner.

[0176] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the meaning and scope of the claims.

[0177] REFERENCE SIGNS LIST 1 Operation management system (vehicle data collection system) 2, 2A, 2B Vehicle 3, 3A, 3B In-vehicle device 4, 4A, 4B Smartphone 5 Server 7 Administrator terminal 8 Network 11 Sensor group 12 In-vehicle control device 13 GPS receiver 14 Clock 31, 51, 71 Communication unit 32 Interface unit 33, 52, 75 Storage device 34, 53, 76 Computer program 35 Conversion rule information 36, 58, 74 Processor 37 Data collection unit 38 Data conversion unit 39 Data transmission unit 54 Conversion rule information 55 Vehicle data 56 Notification data 57 Display item information 59 Data receiving unit 60 Data restoration unit 61 Display control unit 62 Display item information acquisition unit 63 Vehicle data selection unit 64 Conversion rule information registration unit 72 Input unit 73 Display unit 100, 110, 120 Vehicle data screen 101 OK button 111, 111A, 111B, 111C, 113 Vehicle icon 112, 112A, 112B, 112C Mug icon 114 Gas station icon 115 Battery icon 116 Warning icon 117, 131 Notification icon 130 Settings screen 132 Notification data content 140 Management screen

Claims

1. An in-vehicle device mounted on a vehicle, and a server that collects data from the in-vehicle device, wherein the in-vehicle device includes a data collection unit that collects vehicle data, which is data related to the vehicle, a data conversion unit that converts the collected vehicle data into format data of a version corresponding to the type of the vehicle data and writes the version into the format data, and a data transmission unit that transmits the format data with the version written therein to the server, and the server includes a data reception unit that receives the format data, and a data restoration unit that restores the vehicle data from the format data based on the version indicated in the format data. A vehicle data collection system.

2. The server further includes a display control unit that causes the vehicle data restored by the data restoration unit to be displayed. The vehicle data collection system according to claim 1.

3. The server further includes a display item information acquisition unit that acquires display item information indicating the type of the vehicle data to be displayed, and a vehicle data selection unit that selects the vehicle data of the type indicated by the display item information from among the restored vehicle data, wherein the display control unit causes the vehicle data selected by the vehicle data selection unit to be displayed. The vehicle data collection system according to claim 2.

4. The data collection unit collects the position of the vehicle as the vehicle data, the data reception unit further receives notification data notified by a crew member of the vehicle, and the display control unit further causes the notification data received by the data reception unit to be displayed in association with the position of the vehicle on a map based on the vehicle data. The vehicle data collection system according to claim 2 or claim 3.

5. The data collection unit collects, as the vehicle data, data related to at least one of the amount of carbon dioxide in the vehicle, the amount of odor in the vehicle, and the breath alcohol concentration of a crew member of the vehicle, and the position of the vehicle, and the display control unit causes, based on the vehicle data, data related to at least one of the amount of carbon dioxide in the vehicle, the amount of odor in the vehicle, and the breath alcohol amount of a crew member of the vehicle restored by the data restoration unit to be displayed in association with the position of the vehicle on a map. The vehicle data collection system according to claim 2 or claim 3.

6. A conversion rule information registration unit that registers conversion rule information indicating the version and the conversion method corresponding to the version in the in-vehicle device and the server; The conversion method includes a method of converting between the vehicle data and the format data, and the vehicle data collection system according to any one of claims 1 to 3.

7. A data collection unit that collects vehicle data, which is data related to a vehicle; A data conversion unit that converts the collected vehicle data into format data of a version corresponding to the type of the vehicle data, and writes the version into the format data; An in-vehicle device including a data transmission unit that transmits the format data with the version written therein to a server.

8. A data reception unit that receives format data obtained by converting vehicle data, which is data related to a vehicle, according to a version corresponding to the type of the vehicle data, and in which the version is written; A server including a data restoration unit that restores the vehicle data from the format data based on the version indicated in the format data.

9. A computer program for causing a computer to function as: A data collection unit that collects vehicle data, which is data related to a vehicle; A data conversion unit that converts the collected vehicle data into format data of a version corresponding to the type of the vehicle data, and writes the version into the format data; and A data transmission unit that transmits the format data with the version written therein to a server.

10. A computer program for causing a computer to function as: A data reception unit that receives format data obtained by converting vehicle data, which is data related to a vehicle, according to a version corresponding to the type of the vehicle data, and in which the version is written; and A data restoration unit that restores the vehicle data from the format data based on the version indicated in the format data.

11. A step in which an in-vehicle device mounted on a vehicle collects vehicle data, which is data related to the vehicle; The step in which the in-vehicle device converts the collected vehicle data into format data of a version corresponding to the type of the vehicle data and writes the version into the format data; The step in which the in-vehicle device transmits the format data with the version written therein to a server; The step in which the server receives the format data; A vehicle data collection method, including: the step in which the server restores the vehicle data from the format data based on the version indicated in the format data.