JP6927088B2 - Driving data collection system, driving data collection center, and in-vehicle terminal - Google Patents

Description

The present disclosure relates to a driving data collection system for collecting driving data from a plurality of vehicles, a driving data collection center, and an in-vehicle terminal.

Conventionally, there is known a technique of collecting driving data from a plurality of vehicles and analyzing and using the collected driving data. For example, in Patent Document 1, the traffic congestion state is calculated by calculating the average value of the passing speeds of all the probe cars that the center has passed through each section based on the travel information acquired from a plurality of probe cars for each section. However, the technology used for travel guidance is disclosed.

Japanese Unexamined Patent Publication No. 2003-281674

However, in the conventional technique as disclosed in Patent Document 1, there is a problem that a wasteful load and a cost on the traveling data collection center side for collecting traveling data become large. The details are as follows.

The amount of driving data required for analysis may be a certain amount for each road, but since the traffic volume of vehicles differs depending on the road, the collected driving data will be insufficient on roads with low traffic volume, while roads with heavy traffic volume will be insufficient. Then, it is conceivable that the collected driving data will be excessive. When the collected driving data becomes excessive, the communication load for collecting the driving data on the driving data collection center side, the cost for making a margin in the memory for storing the collected driving data, and the collected driving The processing load for analyzing the data becomes unnecessarily large. When collecting images as driving data to generate a map and / or confirm changes in the road, the amount of information in the driving data becomes large, so there is a problem of unnecessary load and cost on the driving data collection center side. Will be particularly large.

One purpose of this disclosure is a driving data collection system, a driving data collection center, and an in-vehicle terminal that enable the driving data collection center to collect a required amount of driving data while suppressing unnecessary load and cost. Is to provide.

The above objectives are achieved by a combination of the features described in the independent claims, and the sub-claims provide for further advantageous embodiments of the disclosure. The reference numerals in parentheses described in the claims indicate, as one embodiment, the correspondence with the specific means described in the embodiments described later, and do not limit the technical scope of the present disclosure. ..

In order to achieve the above object, the driving data collection system of the present disclosure is mounted on a vehicle and has a data acquisition unit (27) for acquiring driving data which is information obtained by driving the vehicle and a vehicle side for transmitting the information. A vehicle-mounted terminal (2) including a transmitting unit (242) and a vehicle-side receiving unit (241) for receiving information, and the vehicle-side transmitting unit transmits driving data acquired by the data acquisition unit, and a vehicle-mounted terminal (2) of a plurality of vehicles. The travel data collection center includes a travel data collection center (3) including a collection unit (311) for collecting travel data transmitted from the vehicle-side transmission unit of the terminal, and the travel data collection center is based on the travel frequency of the vehicle for each road section. , The road section for collecting driving data from the vehicle is determined for each vehicle, and the collection instruction information for acquiring the driving data on the in-vehicle terminal of each vehicle in the determined road section is the driving data that needs to be acquired and the driving data thereof. A collection instruction information generation unit (39) that generates data based on collection needs, which is information indicating conditions for acquiring data, and a center-side transmission unit (312) that transmits information are provided, and the center-side transmission unit collects data. the collection instructing information generated by the instruction information generating unit, and transmits to the in-vehicle terminal of each vehicle, the vehicle-side transmitting unit of the car mounting device, before transmitting the driving data acquired by the data acquisition unit, summary of travel data When the driving data collection center receives the summary information from the in-vehicle terminal, the driving data collection center determines the collection status of the driving data in the collecting unit and the collection needs. Based on this, a necessity determination unit (37) for determining the necessity of driving data corresponding to this summary information is provided, and the center side transmission unit transmits the necessity determination result of the necessity determination unit to the in-vehicle terminal. , The vehicle-side transmitter of the in-vehicle terminal transmits the driving data when the necessity determination result received from the driving data collection center requires the driving data, but does not require the driving data. In some cases, driving data is not transmitted.

Further, in order to achieve the above object, the traveling data collection center of the present disclosure transmits information to a data acquisition unit (27) which is mounted on the vehicle and acquires driving data which is data obtained by the traveling of the vehicle. A vehicle-side transmitting unit (242) and a vehicle-side receiving unit (241) for receiving information are provided, and the vehicle-side transmitting unit collects driving data acquired by the data acquisition unit at a traveling data collection center (travel data collection center (241). send 3), the car sides transmission unit transmits before transmitting the driving data acquired by the data acquisition unit, an overview of the traveling data, a small outline information amount of information than the travel data, travel data received from the collection center, if the running data collection center, the collection form status of the travel data is determined on the basis of necessity determination result of the traveling data corresponding to the summary information, those requiring running data The driving data is transmitted to, but the driving data is not transmitted when the driving data is not required.

According to these, the collection needs a acquired showed the travel data and conditions for obtaining the traveling data required information, and transmits from the center side transmitting unit to the in-vehicle terminal of each vehicle, each vehicle The in-vehicle terminal will acquire driving data according to this collection need. Therefore, while suppressing the reception of driving data that exceeds the collection needs on the driving data collection center side and suppressing unnecessary load and cost on the driving data collection center side, the driving data that meets the collection needs is transmitted and the driving data is collected. It enables the center side to collect the required amount of driving data. Further, since the summary information received from the in-vehicle terminal has a smaller amount of information than the driving data, the amount of information received from the in-vehicle terminal on the driving data collection center side for determining the necessity of the driving data can be suppressed. It is possible to reduce unnecessary load and cost on the driving data collection center side. As a result, it becomes possible to collect a required amount of driving data while suppressing unnecessary load and cost on the driving data collection center side.

In addition, the driving data collection center is information indicating the collection status of driving data in the collecting unit, the driving data that needs to be collected, and the conditions for collecting the driving data when receiving the summary information from the in-vehicle terminal. Based on the collection needs, the necessity of driving data corresponding to this summary information is determined, and the necessity determination result is transmitted to the in-vehicle terminal. Therefore, while it is determined that driving data that meets the collection needs is necessary and transmitted from the in-vehicle terminal to the driving data collection center, it is determined that driving data that exceeds the collection needs is not necessary and is not transmitted from the in-vehicle terminal to the driving data collection center. It becomes possible to. Therefore, it is necessary to suppress the reception of driving data that exceeds the collection needs, suppress unnecessary load and cost on the driving data collection center side, receive the driving data that meets the collection needs, and collect the required amount of driving data. To enable. Further, since the summary information received from the in-vehicle terminal by the driving data collection center is smaller than the driving data, the amount of information received from the in-vehicle terminal for determining the necessity of the driving data is suppressed, and the driving is performed. It is possible to reduce unnecessary load and cost on the data collection center side. As a result, it becomes possible to collect a required amount of driving data while suppressing unnecessary load and cost on the driving data collection center side.

Further, in order to achieve the above object, the in-vehicle terminal of the present disclosure is mounted on a vehicle and has a data acquisition unit (27) for acquiring driving data which is data obtained by traveling of the vehicle and a vehicle side for transmitting information. The vehicle-side transmitting unit includes a transmitting unit (242) and a vehicle-side receiving unit (241) for receiving information, and the vehicle-side transmitting unit collects driving data acquired by the data acquisition unit and a traveling data collection center (3). Before transmitting the driving data acquired by the data acquisition unit, the vehicle-side transmitting unit transmits the summary information, which shows the outline of the driving data and has a smaller amount of information than the driving data, and the driving data collection center. Summary information determined based on the collection status of driving data, the driving data that needs to be acquired, and the collection needs that are the information indicating the conditions for acquiring the driving data at the driving data collection center received from. When the necessity determination result of the traveling data corresponding to the above indicates that the traveling data is required, the traveling data is transmitted, but when the driving data is not required, the traveling data is not transmitted.

According to this, the vehicle-side transmitter transmits the driving data when the necessity determination result received from the driving data collection center requires the driving data, but does not require the driving data. If there is, it does not send the run line data. Therefore, it is possible to transmit the driving data that meets the collection needs to the driving data collection center, but not to transmit the driving data that exceeds the collection needs to the driving data collection center. Therefore, while suppressing the reception of driving data that exceeds the collection needs on the driving data collection center side and suppressing unnecessary load and cost on the driving data collection center side, the driving data that meets the collection needs is transmitted and the driving data is collected. It enables the center side to collect the required amount of driving data. Further, since the summary information transmitted from the in-vehicle terminal to the driving data collection center has a smaller amount of information than the driving data, the information used for determining the necessity of the driving data is received from the in-vehicle terminal on the driving data collection center side. It is possible to reduce the amount of information and reduce unnecessary load and cost on the driving data collection center side. As a result, it becomes possible to collect a required amount of driving data while suppressing unnecessary load and cost on the driving data collection center side.

It is a figure which shows an example of the schematic structure of the driving data collection system 1. It is a figure which shows an example of the schematic structure of the in-vehicle terminal 2. It is a figure for demonstrating an example of collection instruction information. It is a figure which shows an example of the schematic structure of the driving data collection center 3. It is a figure for demonstrating an example of a traveling frequency map. It is a figure for demonstrating an example of collection needs. It is a figure for demonstrating an example of the generation of the collection required list. It is a figure for demonstrating an example of generation of collection instruction information. It is a sequence diagram which shows an example of the flow of the driving data acquisition-related processing in the driving data collection system 1. It is a flowchart which shows an example of the flow of the traveling link specific transmission processing in an in-vehicle terminal 2. It is a flowchart which shows an example of the flow of the traveling frequency specification processing in the traveling data collection center 3. It is a flowchart which shows an example of the flow of the collection instruction information generation processing in a driving data collection center 3. It is a flowchart which shows an example of the flow of the collection inquiry processing in an in-vehicle terminal 2. It is a flowchart which shows an example of the flow of the necessity determination-related processing in a driving data collection center 3. It is a flowchart which shows an example of the flow of the driving data transmission-related processing in an in-vehicle terminal 2. It is a flowchart which shows an example of the flow of the driving data collection processing in the driving data collection center 3.

A plurality of embodiments for disclosure will be described with reference to the drawings. For convenience of explanation, the parts having the same functions as the parts shown in the drawings used in the explanations up to that point may be designated by the same reference numerals and the description thereof may be omitted. be. For the parts with the same reference numerals, the description in other embodiments can be referred to.

(Embodiment 1)
<Outline configuration of driving data collection system 1>
Hereinafter, the first embodiment of the present disclosure will be described with reference to the drawings. As shown in FIG. 1, the travel data collection system 1 includes an in-vehicle terminal 2 mounted on each of a plurality of vehicles and a travel data collection center 3.

The in-vehicle terminal 2 is mounted on a vehicle and acquires driving data obtained by traveling the vehicle. Further, the in-vehicle terminal 2 communicates with the traveling data collection center 3 and transmits the traveling data acquired by the own vehicle to the traveling data collection center 3. The vehicle referred to here is, for example, an automobile, and may be a general vehicle or a commercial vehicle such as a taxi or a transportation vehicle. Details of the in-vehicle terminal 2 will be described later.

The driving data collection center 3 is, for example, a server device, receives driving data collection needs from a driving data utilization system that utilizes driving data, and collects driving data corresponding to the collection needs from in-vehicle terminals 2 of a plurality of vehicles. , Present the collected driving data to the driving data utilization system. The travel data collection center 3 sends the vehicle-mounted terminal 2 mounted on the vehicle to the road section (that is, the link) for which the vehicle-mounted terminal 2 should acquire the travel data, the travel data to be acquired, and the acquisition conditions for the travel data. The collection instruction information indicating the above is transmitted, and the traveling data transmitted from the in-vehicle terminal 2 is collected. The travel data collection center 3 may be composed of one server device or a plurality of server devices. The details of the driving data collection center 3 will be described later.

<Outline configuration of in-vehicle terminal 2>
First, a schematic configuration of the in-vehicle terminal 2 will be described with reference to FIG. The in-vehicle terminal 2 is mounted on the vehicle as described above, and as shown in FIG. 2, the locator 21, the map database (hereinafter, DB) 22, the map matching unit 23, the communication unit 24, and the collection instruction information storage. It includes a unit 25, an acquisition determination unit 26, a travel data acquisition unit 27, and a travel data storage unit 28.

The locator 21 includes a GNSS (Global Navigation Satellite System) receiver and an inertial sensor. The GNSS receiver receives positioning signals from a plurality of artificial satellites. The inertial sensor includes, for example, a gyro sensor and an acceleration sensor. The locator 21 detects the vehicle position of the own vehicle by combining the positioning signal received by the GNSS receiver and the measurement result of the inertial sensor. The vehicle position may be, for example, latitude / longitude coordinates. The vehicle position may be detected by using the mileage obtained from the vehicle speed detected by the vehicle speed sensor mounted on the own vehicle.

The map DB 22 is a non-volatile memory and stores map data such as link data and node data. The link data consists of link ID, which is a unique number that identifies the link, link length indicating the length of the link, link direction, link shape information, node coordinates between the start and end of the link, and road attribute data. Will be done. Road attributes include road name, road type, road width, number of lanes, speed regulation value, and the like. On the other hand, the node data includes a node ID with a unique number for each node on the map, node coordinates, a node name, a node type, a connection link ID in which a link ID of a link connecting to a node is described, an intersection type, and the like. It consists of each data.

The map matching unit 23 performs map matching processing based on the vehicle position sequentially detected by the locator 21 and the map data stored in the map DB 22, and thereby performs a link during travel of the own vehicle (hereinafter, traveling). Link) is specified sequentially.

The communication unit 24 communicates with the travel data collection center 3. The communication unit 24 communicates with the travel data collection center 3 via, for example, a base station and a public communication network. As an example, the communication unit 24 may be configured to communicate with the traveling data collection center 3 via a communication network used for telematics communication by an in-vehicle communication module used for telematics communication such as a DCM (Data Communication Module).

The receiving unit 241 of the communication units 24 receives the information transmitted from the travel data collection center 3. This receiving unit 241 corresponds to the vehicle side receiving unit. As an example, when the collection instruction information is transmitted from the travel data collection center 3, the reception unit 241 receives the collection instruction information and stores it in the collection instruction information storage unit 25. The collection instruction information storage unit 25 may be, for example, a non-volatile memory.

Here, an example of collection instruction information will be described with reference to FIG. FIG. 3 is an example of collection instruction information for a certain vehicle. The collection instruction information is associated with a link for acquiring driving data for each vehicle. As an example, as shown as "links 1 and 2" in FIG. 3, the link ID of the link for which the driving data should be acquired (hereinafter, the link to be acquired) may be associated with the link ID. In addition, the collection instruction information is associated with acquisition conditions such as the type, amount, and acquisition period of travel data to be acquired for the acquisition target link. In the example of FIG. 3, the types of driving data are the items "camera image", "speed", "front-back acceleration", "lateral acceleration", "winker signal", "brake signal", "ABS operation", and "fuel consumption". It corresponds to "amount" and so on. The amount of travel data corresponds to the content "40 travels" corresponding to the item "camera image" of the type of travel data. The travel data acquisition period corresponds to the content "2016/1/1 to 2016/12/31" corresponding to the item "period" of the acquisition condition.

Further, the collection instruction information may be configured so that the acquisition target link is associated with acquisition conditions such as a time zone for acquiring the travel data, a lane for acquiring the travel data, a target vehicle type, and a travel method. In the example of FIG. 3, the time zone for acquiring the traveling data corresponds to the content "10:00 to 19:00" corresponding to the item "time zone" of the acquisition condition. The lane for which the traveling data is collected may be, for example, distinguishing between the ascending and descending lanes, the first traveling lane and the second traveling lane, and the like. In the example of FIG. 3, the lane for collecting the traveling data corresponds to the content “up lane, first traveling lane” corresponding to the item “collecting lane” of the acquisition condition. The target vehicle type corresponds to the content "truck" corresponding to the acquisition condition item "target vehicle type". The traveling method corresponds to the content "average vehicle speed of 30 km / h or more" corresponding to the item "driving method" of the acquisition condition.

The collection instruction information stored in the collection instruction information storage unit 25 is updated with the new collection instruction information every time new collection instruction information is transmitted from the traveling data collection center 3. Further, the collection instruction information stored in the collection instruction information storage unit 25 may be deleted when the acquisition period of the acquisition conditions ends. The details of the transmission unit 242 of the communication unit 24 will be described later.

The acquisition determination unit 26 refers to the collection instruction information stored in the collection instruction information storage unit 25, and the current traveling link of the own vehicle specified by the map matching unit 23 is associated with the own vehicle by the collection instruction information. It is determined whether or not the link is to be acquired.

When the travel data acquisition unit 27 determines that the current travel link of the own vehicle is the acquisition target link by the acquisition determination unit 26, the travel data acquisition unit 27 of the own vehicle according to the acquisition condition associated with the acquisition target link in the collection instruction information. Acquire the driving data of the own vehicle from sensors and the like. The traveling data acquisition unit 27 corresponds to the data acquisition unit. As an example, the type of driving data to be acquired is acquired according to the type of driving data to be acquired. In addition, when the acquisition conditions such as the acquisition period of the driving data, the acquisition time zone of the driving data, the lane for acquiring the driving data, the target vehicle type, and the driving method are met, the driving data obtained by the driving of the acquisition target link is acquired. do.

As an example of the driving data acquired by the traveling data acquisition unit 27, the image data around the own vehicle captured by the peripheral monitoring camera, the vehicle position detected by the locator 21, the accuracy information of the vehicle position, and the vehicle speed sensor are detected. There are vehicle speed, acceleration detected by the G sensor, yaw rate detected by the gyro sensor, and so on. The accuracy information of the vehicle position may be, for example, DOP (Dilution of precision), which is a positioning accuracy deterioration coefficient affected by the geometrical arrangement of _{the positioning satellite Gn as seen from the receiving point of the positioning signal.} The travel data acquired by the travel data acquisition unit 27 includes a brake signal output from the brake switch in response to the brake operation, a winker signal output from the winker switch in response to the winker operation, and ABS (Antilock) output from the ECU. Brake System) operation information, running energy consumption, etc. may be used.

The travel data acquisition unit 27 stores the acquired travel data in the travel data storage unit 28. The travel data storage unit 28 may be a volatile memory or a non-volatile memory. The travel data storage unit 28 stores the acquired travel data in the travel data storage unit 28 in association with the outline information indicating the outline of the travel data. The summary information may be data having a smaller amount of information than the corresponding driving data. As the summary information, in addition to the link ID of the driving link from which the driving data has been acquired, information such as acquisition conditions when the driving data has been acquired and a flag indicating whether or not the driving data has been acquired for each type of driving data may be included. good. It is preferable that the flag indicating the presence / absence of acquisition of each type of travel data suppresses the amount of information by, for example, indicating the presence / absence of acquisition of each type of travel data as a 1-bit value.

The transmission unit 242 of the communication units 24 transmits information to the travel data collection center 3. This transmission unit 242 corresponds to the vehicle side transmission unit. As an example, the transmission unit 242 transmits the travel link of the own vehicle sequentially identified by the map matching unit 23 to the travel data collection center 3. The transmission unit 242 may be configured to transmit the history of the travel link of the own vehicle sequentially identified by the map matching unit 23 to the travel data collection center 3. As an example, the history of travel links between trips from when the ignition power of the own vehicle is turned on to when it is turned off is stored in a memory such as a travel data storage unit 28, and the accumulated history of travel links is tripped. At the end, it may be transmitted to the driving data collection center 3. The travel link and the history of the travel link correspond to the position-related information. The travel link referred to here is a link ID of the travel link, and the history of the travel link is a group of link IDs indicating the history of the travel link.

Further, when the travel data acquired by the travel data acquisition unit 27 is stored in the travel data storage unit 28, the transmission unit 242 corresponds to the travel data before transmitting the travel data to the travel data collection center 3. The summary information is transmitted to the driving data collection center 3. For example, the transmission unit 242 may be configured to transmit the summary information corresponding to the travel data to the travel data collection center 3 each time the travel data acquired by the travel data acquisition unit 27 is stored in the travel data storage unit 28. Although the details will be described later, the travel data collection center 3 determines the necessity of travel data corresponding to this summary information, and transmits the necessity determination result to the in-vehicle terminal 2 that transmits the summary information. Then, the reception unit 241 of the in-vehicle terminal 2 receives the necessity determination result.

When the necessity determination result received from the travel data collection center 3 requires the travel data, the transmission unit 242 transmits the travel data to the travel data collection center 3 while requiring the travel data. If not, the travel data is not transmitted to the travel data collection center 3. In other words, when the necessity determination result transmitted from the travel data collection center 3 in response to the transmission of the summary information requires the travel data, the transmission unit 242 travels corresponding to this summary state. The data is read from the driving data storage unit 28 and transmitted to the driving data collection center 3, but when the driving data is not required, the driving data corresponding to this summary state is read from the driving data storage unit 28. Do not send to the driving data collection center 3.

When the transmission unit 242 transmits the travel data to the travel data collection center 3, the transmission unit 242 also includes the travel link of the own vehicle sequentially identified by the map matching unit 23 or the vehicle position of the own vehicle sequentially detected by the locator 21. It may be configured to transmit. The travel data stored in the travel data storage unit 28 may be deleted when the travel data is transmitted or not transmitted according to the necessity determination result received from the travel data collection center 3. It may be configured to be erased after a certain period of time has passed since it was stored.

<Outline configuration of driving data collection center 3>
Subsequently, a schematic configuration of the traveling data collection center 3 will be described with reference to FIG. As described above, the travel data collection center 3 is, for example, a server device, and as shown in FIG. 4, the communication unit 31, the travel history storage unit 32, the travel data storage unit 33, the travel frequency specifying unit 34, and the travel frequency DB 35. It includes a needs acquisition unit 36, a needs control unit 37, a collection required list storage unit 38, a collection instruction information generation unit 39, a collection instruction information storage unit 40, and a collection result output unit 41.

The communication unit 31 communicates with the in-vehicle terminal 2. The communication unit 31 communicates with the in-vehicle terminal 2 via, for example, a base station and a public communication network. The receiving unit 311 of the communication units 31 receives the information transmitted from the in-vehicle terminal 2. As an example, when the history of the travel link and travel link of the vehicle on which the vehicle-mounted terminal 2 is mounted is transmitted from the vehicle-mounted terminal 2, the receiving unit 311 receives the history of the travel link and travel link.

The receiving unit 311 stores the travel link and the history of the travel link received from the vehicle-mounted terminal 2 of the vehicle in the travel history storage unit 32 in association with the vehicle. As an example, the configuration may be such that an identifier that can identify the vehicle, a traveling link, and a history of the traveling link are stored in association with each other. The identifier that can identify the vehicle may be the vehicle ID or the ID of the in-vehicle terminal 2, but the description will be continued by taking the vehicle ID as an example. When the receiving unit 311 receives the traveling link, the traveling link history is stored by storing the traveling link sequentially received for the same vehicle in chronological order in association with the vehicle ID of this vehicle. It may be configured to be used. The travel history storage unit 32 may be configured to use, for example, a non-volatile memory. The receiving unit 311 receives the history of the traveling link and the traveling link from the in-vehicle terminals 2 of the plurality of vehicles, and stores the history of the traveling link for the plurality of vehicles in the traveling history storage unit 32.

Further, the receiving unit 311 receives the summary information when the summary information is transmitted from the vehicle-mounted terminal 2 of the vehicle, and outputs the received summary information and the vehicle ID of the vehicle to the needs control unit 37.

Further, the receiving unit 311 receives the traveling data when the traveling data acquired by the in-vehicle terminal 2 is transmitted according to the collection instruction information transmitted from the traveling data collection center 3. Then, the receiving unit 311 stores the received traveling data in the traveling data storage unit 33. The traveling data storage unit 33 may be configured to use, for example, a non-volatile memory. The receiving unit 311 stores the traveling data received from the vehicle-mounted terminals 2 of the plurality of vehicles in the traveling data storage unit 33, and collects the traveling data transmitted from the vehicle-mounted terminals 2 of the plurality of vehicles. Therefore, the receiving unit 311 corresponds to the collecting unit.

The receiving unit 311 identifies the link from which the traveling data has been acquired according to the traveling link, the vehicle position, etc. of the vehicle on which the in-vehicle terminal 2 is mounted, which is included in the traveling data transmitted from the in-vehicle terminal 2, and receives the received traveling data. It may be stored in the traveling data storage unit 33 for each link. Further, the receiving unit 311 stores the traveling link, the vehicle position, etc. of the vehicle on which the in-vehicle terminal 2 is mounted in the traveling data transmitted from the in-vehicle terminal 2 in the history of the traveling link stored in the traveling history storage unit 32. It may be diverted. The details of the transmission unit 312 of the communication units 31 will be described later.

The traveling frequency specifying unit 34 specifies the traveling frequency for each link for each of a plurality of vehicles from the history for the latest fixed period (for example, one month) stored in the traveling history storage unit 32. As an example, the number of times the link has traveled during the period for which the frequency of travel is specified may be calculated, and the calculated number of times of travel may be specified as the frequency of travel. The traveling frequency specifying unit 34 stores a traveling frequency map for each link for each of a plurality of vehicles (hereinafter referred to as a traveling frequency map) in the traveling frequency DB 35. The traveling frequency DB 35 may be configured to use, for example, a non-volatile memory.

Here, an example of a traveling frequency map will be described with reference to FIG. In the example of FIG. 5, the traveling frequency of each link of the link IDs "link 1" to "link 5" is associated with each vehicle of the vehicle IDs "vehicle A" to "vehicle D" traveling on the target link. The driving frequency map is shown. In the example of FIG. 5, for "vehicle A", the traveling frequency "10" is associated with "link 1" and "link 2", and there is no traveling frequency data for "link 3" to "link 5". It has become. Regarding "Vehicle B", "Link 1" has no travel frequency data, "Link 2" to "Link 4" have a travel frequency of "5", and "Link 5" has a travel frequency of "2". It is associated. Regarding "vehicle C", "link 1" and "link 2" have no travel frequency data, and "link 3" to "link 5" are associated with a travel frequency "10". Regarding the "vehicle D", the traveling frequency "10" is associated with the "link 1" to the "link 5".

It is preferable that the traveling frequency specifying unit 34 respecifies the traveling frequency every time a predetermined period elapses, and updates the traveling frequency map stored in the traveling frequency DB 35. The predetermined period referred to here is a period that can be arbitrarily set. The travel frequency map may be updated irregularly triggered by an operator's operation or the like.

The needs acquisition unit 36 acquires the collection needs of the driving data utilization system. The needs acquisition unit 36 may be configured to automatically acquire collection needs by making a communication connection with the travel data utilization system. In addition, the needs acquisition unit 36 may be configured to acquire the collection needs of the travel data utilization system input to the travel data collection center 3 by the operation of the operator. The collection needs are information indicating the driving data that needs to be collected and the acquisition conditions for acquiring the driving data. As an example, as shown in FIG. 6, the collection needs include information such as roads, sections, lanes, time zones, periods, vehicle types, and driving methods for which driving data is to be collected, and types of driving data to be collected. There is a lot of data. The amount of travel data to be collected (hereinafter referred to as the amount of collection) may be represented by the required number of travels.

The needs control unit 37 determines the section in which the travel data should be collected, the type of the travel data to be collected, and the travel data to be collected, based on the collection needs acquired by the needs acquisition unit 36 and the collection status of the travel data in the reception unit 311. The amount to be collected is determined, and a collection required list showing the section in which driving data should be collected, the type of driving data to be collected, and the amount to be collected is generated. As the collection status of the travel data in the receiving unit 311 may be used, the collected travel data stored in the travel data storage unit 33 may be used. The needs control unit 37 stores the generated collection-required list in the collection-required list storage unit 38. The collection-required list storage unit 38 may be configured to use, for example, a non-volatile memory.

Here, an example of generating a collection required list by the needs control unit 37 will be described with reference to FIG. 7. The needs control unit 37 extracts insufficient data in the collected driving data for the collection needs based on the collection needs acquired by the needs acquisition unit 36 and the collection status of the driving data in the receiving unit 311. do.

In the example of FIG. 7, for the running data under the predetermined acquisition conditions, the “camera image” and “speed” require “50 running minutes” in the collection needs, whereas the collected running data is “camera”. The "image" is "for 10 runs" and the "speed" is "for 100 runs". Therefore, the running data of "speed" satisfies the required collection amount and there is no shortage. On the other hand, the travel data of the "camera image" is insufficient for "40 travels" with respect to the required collection amount. Therefore, the needs control unit 37 extracts the travel data of the “camera image” of “40 travels” as insufficient data. Subsequently, the needs control unit 37 generates a collection-required list indicating the section in which the travel data should be collected, the type of the travel data to be collected, and the collection amount based on the extracted insufficient data. In the example of FIG. 7, a collection-required list showing the above-mentioned predetermined acquisition conditions including the section for which the driving data should be collected, the type of driving data to be collected "camera image", and the collection amount "40 driving minutes" is displayed. Generate.

The predetermined acquisition conditions shown in the example of FIG. 7 are that the "road name" is "X highway", the "section" is "links 1 to 5", the "collection lane" is "up lane, first driving lane", and " "Time zone" is "10:00 to 19:00", "Period" is "2016/1/1 to 2016/12/31", "Target vehicle type" is "Truck", "Driving method" is "Average vehicle speed 30km" / H or more ".

It is preferable that the needs control unit 37 sequentially generates the collection-required list, so that the collection-required list stored in the collection-required list storage unit 38 is sequentially updated even if the collection needs are not changed. As an example, the collection-required list may be generated and updated on a regular basis, such as every hour. When the collection needs include the collection period as an acquisition condition, the frequency of generation and update of the collection required list is preferably set to the frequency of being generated and updated at least a plurality of times within this collection period. According to this, according to the change in the collection status of the travel data at the receiving unit 311 during the collection period, the travel data that does not need to be collected as the collection status progresses is removed from the collection required list, and the travel data is useless. It becomes possible to suppress the collection of. In addition, if another collection need is newly added within the collection period, the additional required driving data can be quickly added to the collection required list, and the additional required driving data can be quickly collected. It will be possible.

Further, the needs control unit 37 includes the summary information output from the reception unit 311 and the vehicle ID of the vehicle when the reception unit 311 receives the summary information transmitted from the vehicle-mounted terminal 2 of the vehicle by the reception unit 311. To get. Then, based on the collection needs acquired by the needs acquisition unit 36 and the collection status of the travel data by the reception unit 311, the necessity of the travel data corresponding to this summary information is determined. Therefore, the needs control unit 37 corresponds to the necessity determination unit.

As an example, the needs control unit 37 uses the collection required list and the summary information to be updated sequentially, and if the driving data corresponding to the summary information corresponds to the driving data to be collected in the collection required list, the needs control unit 37 obtains the driving data. On the other hand, if it does not correspond to the driving data to be collected in the collection required list, it is determined that this driving data is not required. When there are a plurality of types of travel data corresponding to the summary information, the necessity of the travel data may be determined for each type of travel data.

The collection instruction information generation unit 39 determines a link for collecting driving data from the vehicle for each vehicle according to the traveling frequency and collection needs for each link of the vehicle, and the traveling data on the in-vehicle terminal 2 of each vehicle at the determined link. Generate collection instruction information to acquire. Hereinafter, the details of the method of generating the collection instruction information will be described by taking as an example the case where the travel frequency map of FIG. 5 and the collection required list of FIG. 7 are used.

First, the collection instruction information generation unit 39 sets a link (that is, a collection target link) for which driving data should be collected based on a collection required list generated by the needs control unit 37 using the collection needs acquired by the needs acquisition unit 36. decide. As an example, the link corresponding to the section of the road to be collected is determined as the link to be collected. In the collection required list of FIG. 7, since the “section” used as the acquisition condition is “links 1 to 5”, the collection target link is determined to be “links 1 to 5”.

Further, the collection instruction information generation unit 39 also determines the travel data to be collected, the collection amount of the travel data, and the acquisition conditions of the travel data based on the collection required list generated by the needs control unit 37. In the collection required list of FIG. 7, since the collection amount "40 travels" is associated with the type "camera image" of the travel data to be collected, the travel data to be collected is determined to be "camera image". , The collection amount is determined to be "40 runs". When the collection amount differs depending on the type of travel data, the collection amount may be adjusted to a large value, or the collection amount may be determined for each of the different collection amounts.

As the acquisition condition, the collection instruction information generation unit 39 may determine the acquisition condition included in the collection required list as the acquisition condition. Therefore, according to the acquisition conditions included in the collection required list in FIG. 7, the acquisition conditions are "road name" as "X expressway", "collection lane" as "up lane, first driving lane", and "time zone" as "time zone". "10:00 to 19:00", "Period" is "2016/1/1 to 2016/12/31", "Target vehicle type" is "Truck", "Driving method" is "Average vehicle speed 30km / h or more" It is determined.

In addition, the collection instruction information generation unit 39 extracts the collection target links having a high traveling frequency for each vehicle from the traveling frequency map stored in the traveling frequency DB 35. As an example, a collection target link whose number of trips is equal to or greater than a threshold value is extracted. The threshold value referred to here is a value that can be arbitrarily set multiple times. Hereinafter, the description will be continued by taking the case where the threshold value is 5 times as an example. Since the collection target links are "links 1 to 5" and the threshold value is 5, from the travel frequency map of FIG. 5, "link 1" and "link" are used as the collection target links having a high travel frequency for the vehicle A. 2 ”is extracted. For vehicle B, "link 2" to "link 4" are extracted. For vehicle C, "link 3" to "link 5" are extracted. For vehicle D, "link 1" to "link 5" are extracted.

Then, the collection instruction information generation unit 39 collects instruction information for each vehicle from the acquisition target link extracted for each vehicle, the determined travel data to be collected, the amount of the travel data collected, and the acquisition conditions for the travel data. To generate. The collection instruction information may be generated as a table different for each vehicle. The collection instruction information generation unit 39 selects the link for acquiring the driving data included in the collection instruction information, the driving data to be acquired, and the link for acquiring the driving data among the conditions for acquiring the driving data for each vehicle. The collection instruction information may be generated by applying the extracted acquisition target links for each vehicle. Regarding the driving data to be acquired, based on the determined driving data to be collected and the collected amount of the driving data, the collected amount is associated with the type of driving data to be acquired in common for each vehicle. The collection instruction information may be generated. Regarding the acquisition conditions of the travel data to be acquired, the collection instruction information may be generated by applying the determined acquisition conditions of the travel data to be collected in common for each vehicle.

Here, an example of the collection instruction information generated for each of the vehicles A to D will be described with reference to FIG. The collection instruction information for vehicles A to D is determined according to the acquisition conditions included in the collection required list in FIG. 7, where the "road name" is "X highway" and the "collection lane" is "up lane, first run". "Lane", "Time zone" is "10:00 to 19:00", "Period" is "2016/1/1 to 2016/12/31", "Target vehicle type" is "Truck", "Driving method" It is generated so as to include acquisition conditions such as "average vehicle speed of 30 km / h or more" in common. Further, the travel data to be acquired is generated so as to commonly include the collection amount "40 travels" for the type "camera image" of the travel data, which is determined based on the collection required list of FIG.

As for the links for which driving data should be acquired, the acquisition target links extracted for each vehicle are generated so as to be included in the collection instruction information for each vehicle. As an example, the collection instruction information of the vehicle A is generated so as to include "link 1" and "link 2" for the "section" in the acquisition conditions as the links for which the traveling data should be acquired. The vehicle B is generated so that the "link 2" to the "link 4" are included in the "section". The vehicle C is generated so that the "link 3" to the "link 5" are included in the "section". The vehicle D is generated so that "link 1" to "link 5" are included in the "section".

The collection instruction information generation unit 39 stores the generated collection instruction information for each vehicle in the collection instruction information storage unit 40. The collection instruction information storage unit 40 may be configured to use, for example, a non-volatile memory. When the collection instruction information generation unit 39 determines the collection amount for each type of travel data having a different collection amount, as an example, the collection instruction information is also generated for each type of travel data with a different collection amount. The configuration may be generated.

In addition, the collection instruction information generation unit 39 sequentially generates collection instruction information and updates the collection instruction information stored in the collection instruction information storage unit 40 with the newly generated collection instruction information to meet the collection needs. It is preferable to update the collection instruction information sequentially even if there is no change. According to this, even if there is no change in collection needs, driving data that no longer needs to be collected is quickly removed from the collection instruction information in response to changes in the collection status of driving data, and unnecessary collection of driving data is suppressed. Will be possible.

The collection instruction information generation unit 39 is a collection instruction for acquiring the travel data required in the collection status based on the collection needs acquired by the needs acquisition unit 36 and the travel data collection status of the reception unit 311. The information may be updated sequentially. As an example, the collection instruction information generation unit 39 updates the collection instruction information by newly updating the collection instruction information according to the updated collection required list each time the needs control unit 37 updates the collection required list. do it.

As an example, the collection instruction information may be updated periodically, such as every hour. When the collection instruction information is updated at least a plurality of times within the collection period when the collection needs include the collection period as an acquisition condition, it is preferable. According to this, according to the change in the collection status of the travel data at the receiving unit 311 during the collection period, the travel data that does not need to be collected as the collection status progresses is excluded from the collection instruction information, and the travel data is useless. It becomes possible to suppress the collection of. In addition, when another collection need is newly added within the collection period, the additional required driving data can be quickly added to the collection instruction information, and the additional required driving data can be quickly collected. It will be possible.

The transmission unit 312 of the communication units 31 transmits information to the in-vehicle terminal 2. This transmission unit 312 corresponds to the center side transmission unit. As an example, the transmission unit 312 reads the collection instruction information for each vehicle generated by the collection instruction information generation unit 39 from the collection instruction information storage unit 40 and transmits it to the in-vehicle terminal 2 of each vehicle. In other words, the transmission unit 312 reads the collection instruction information for each vehicle, which is sequentially updated by the collection instruction information generation unit 39, from the collection instruction information storage unit 40, and transmits the collection instruction information to the in-vehicle terminal 2 of each vehicle. The frequency with which the transmission unit 312 transmits the collection instruction information may be lower than the frequency with which the collection instruction information is updated in order to reduce the communication load. For example, every time the ignition power of the vehicle is turned on and the in-vehicle terminal 2 is activated, the in-vehicle terminal 2 requests the collection instruction information, and the transmission unit 312 transmits the collection instruction information to the in-vehicle terminal 2 in response to this request. It may be configured.

Further, the transmission unit 312 transmits the necessity determination result, which is the necessity determination result of the travel data corresponding to the outline information transmitted from the vehicle-mounted terminal 2 of the vehicle by the needs control unit 37, to the transmission source of the outline information. It is transmitted to the in-vehicle terminal 2 of. In addition, when there are a plurality of types of driving data corresponding to the summary information and the necessity determination result can be obtained for each type of driving data, the transmission unit 312 determines the necessity determination result for each type of driving data. It may be configured to transmit. The transmission unit 242 of the in-vehicle terminal 2 that has received the necessity judgment result for each type of driving data narrows down the driving data to the type of driving data required for the necessity judgment result for each type of driving data, and collects the driving data. The configuration may be such that the data is transmitted to the collection center 3.

The collection result output unit 41 outputs the travel data collected and stored in the travel data storage unit 33 to the travel data utilization system. The collection result output unit 41 establishes a communication connection with the travel data utilization system, automatically reads the travel data collected and stored in the travel data storage unit 33, and outputs the travel data to the travel data utilization system. do it. In addition, the collection result output unit 41 collects and stores the travel data in the travel data storage unit 33 by the operator's operation to instruct the output of the travel data collected and stored in the travel data storage unit 33. The data may be read out and output to, for example, an external storage medium.

<Traveling data acquisition related processing>
Here, using the sequence diagram of FIG. 9 and the flowchart of FIGS. 10 to 16, an example of a flow of processing related to acquisition of driving data in the traveling data collection system 1 (hereinafter, driving data acquisition related processing) will be described. Give an explanation. The sequence diagram of FIG. 9 is a sequence diagram showing the flow of the entire traveling data collection system 1, and the flowcharts of FIGS. 10 to 16 are flowcharts showing the flow of each routine of FIG.

First, in step S1, the in-vehicle terminal 2 sequentially identifies the traveling link of the own vehicle and sequentially transmits it to the traveling data collection center 3 (hereinafter, traveling link specifying transmission processing). It is assumed that the traveling link specific transmission process is performed by the in-vehicle terminals 2 of a plurality of vehicles. In step S2, the travel data collection center 3 specifies the travel frequency for each link for each of the plurality of vehicles based on the travel links transmitted from the in-vehicle terminals 2 of the plurality of vehicles in S1 (hereinafter, travel frequency identification). Processing).

In step S3, the travel data collection center 3 generates collection instruction information for each of a plurality of vehicles from the collection needs acquired by the needs acquisition unit 36 and the travel frequency for each link for each of the plurality of vehicles specified in S2. Performs processing (hereinafter, collection instruction information generation processing). In step S4, the travel data collection center 3 transmits the collection instruction information for each vehicle generated in S3 to the in-vehicle terminal 2 of each vehicle.

In step S5, the in-vehicle terminal 2 acquires the driving data according to the collection instruction information transmitted from the driving data collection center 3 in S4, and inquires the driving data collection center 3 whether or not the driving data needs to be transmitted. Is performed (hereinafter referred to as acquisition inquiry processing).

In step S6, the travel data collection center 3 obtains the summary information transmitted from the in-vehicle terminal 2 in S5 based on the collection needs acquired by the needs acquisition unit 36 and the collection status of the travel data by the reception unit 311. A process of determining the necessity of the corresponding traveling data and transmitting the necessity determination result to the in-vehicle terminal 2 (hereinafter referred to as a necessity determination related process) is performed.

In step S7, the in-vehicle terminal 2 transmits or does not transmit the travel data acquired in S5 to the travel data collection center 3 according to the necessity determination result received from the travel data collection center 3 (hereinafter, , Driving data transmission related processing).

In step S8, the travel data collection center 3 performs a process of collecting travel data transmitted from the vehicle-mounted terminal 2 of the vehicle in S7 (hereinafter, travel data collection process). The processes of S1 and S2 may be performed in parallel with the timing of the processes of S3 to S8. Further, the processing of S3 may be performed in parallel with the timing at which the processing of S4 to S8 is performed.

Subsequently, in the following, the flow charts of FIGS. 10 to 16 will be used to explain the flow of each routine of S1 to S3 and S5 to S8 of FIG.

[Traveling link specific transmission processing]
First, an example of the flow of the traveling link specific transmission process in the in-vehicle terminal 2 will be described with reference to the flowchart of FIG. The processing of the flowchart of FIG. 10 may be configured to be performed for each of the above-mentioned trips of the vehicle equipped with the in-vehicle terminal 2, for example.

In step S101, the locator 21 sequentially detects the vehicle position of the own vehicle. In step S102, the map matching unit 23 sequentially identifies the traveling link of the own vehicle by performing map matching processing based on the vehicle position sequentially detected in S101 and the map data stored in the map DB 22. .. In step S103, the transmission unit 242 transmits the history of the travel link of the own vehicle sequentially identified in S102 to the travel data collection center 3.

[Driving frequency identification process]
Subsequently, an example of the flow of the traveling frequency specifying process in the traveling data collection center 3 will be described with reference to the flowchart of FIG. The processing of the flowchart of FIG. 11 may be configured to be performed every time the predetermined period described above elapses, for example.

In step S201, the receiving unit 311 receives the history of the traveling link transmitted from the in-vehicle terminals 2 of the plurality of vehicles. In step S202, the history of the travel link received in S201 is stored in the travel history storage unit 32, and the history of the travel link for each vehicle is accumulated.

In step S203, the travel frequency specifying unit 34 specifies the travel frequency for each link for each of a plurality of vehicles from the history for the most recent fixed period stored in the travel history storage unit 32. In step S204, the traveling frequency specifying unit 34 stores the traveling frequency map showing the traveling frequency for each link for each of the plurality of vehicles specified in S203 in the traveling frequency DB 35.

[Collection instruction information generation process]
Subsequently, an example of the flow of collection instruction information processing in the traveling data collection center 3 will be described with reference to the flowchart of FIG. The processing of the flowchart of FIG. 12 may be performed at a fixed cycle such as an hour cycle when the needs acquisition unit 36 acquires the collection needs of the traveling data utilization system.

In step S301, the section in which the travel data should be collected and the travel data to be collected based on the collection needs acquired by the needs acquisition unit 36 and the travel data collection status in the reception unit 311 by the needs control unit 37. Determine the type and amount of collection. Then, a collection-required list showing the section for collecting the driving data, the type of the traveling data to be collected, and the collection amount is generated.

In step S302, the collection instruction information generation unit 39 collects collection instruction information for each vehicle as described above based on the collection required list generated in S301 and the travel frequency map stored in the travel frequency DB 35. Generate.

[Collection inquiry processing]
Subsequently, an example of the flow of the collection inquiry process in the in-vehicle terminal 2 will be described with reference to the flowchart of FIG. The processing of the flowchart of FIG. 13 may be configured to start when, for example, the collection instruction information transmitted from the travel data collection center 3 is received by the reception unit 241 of the vehicle-mounted terminal 2.

In step S401, the receiving unit 241 stores the collection instruction information received from the travel data collection center 3 in the collection instruction information storage unit 25. In step S402, the locator 21 detects the vehicle position of the own vehicle. In step S403, the map matching unit 23 identifies the traveling link of the own vehicle by performing map matching processing based on the vehicle position detected in S402 and the map data stored in the map DB 22.

In step S404, the acquisition determination unit 26 refers to the collection instruction information stored in the collection instruction information storage unit 25, and determines whether or not the traveling link of the own vehicle specified in S403 is the acquisition target link. Then, when it is determined that the link is to be acquired (YES in S404), the process proceeds to step S405. On the other hand, if it is determined that the link is not the acquisition target link (NO in S404), the process proceeds to step S406.

In step S405, the travel data acquisition unit 27 acquires the travel data of the own vehicle from the sensor or the like of the own vehicle according to the acquisition condition associated with the acquisition target link in the collection instruction information. If the acquisition conditions are not met, the driving data may not be acquired. As for the acquisition conditions, for the driving data including the acquisition conditions such as "driving method" is "average vehicle speed of 30km / h or more" that cannot be determined unless the driving of the link is completed, about the link until the driving of the link is completed. If the travel data of the above is temporarily saved in the travel data storage unit 28 and the storage is continued if the acquisition conditions are met, the temporarily saved travel data is deleted if the acquisition conditions are not met. good.

In step S406, if it is the timing of transmitting travel data (YES in S406), the process proceeds to step S407. In step S407, the transmission unit 242 transmits the summary information of the travel data acquired so far to the travel data collection center 3. On the other hand, if it is not the travel data transmission timing (NO in S406), the process returns to S402 and the process is repeated.

For example, the transmission timing of the travel data may be the end of the trip described above, or may be the time when new travel data is acquired in S405. When the end of the trip is adopted as the transmission timing, the summary information of the travel data for the plurality of travel links accumulated during the trip may be collectively transmitted. On the other hand, when the time when new travel data is acquired in S405 is adopted as the transmission timing, the summary information of the travel data may be transmitted every time the new travel data is acquired in S405. The collection inquiry process may be configured to be sequentially repeated until the collection period of the acquisition conditions included in the collection instruction information ends.

[Necessity judgment related processing]
Subsequently, an example of the flow of the necessity determination-related processing in the traveling data collection center 3 will be described with reference to the flowchart of FIG. The processing of the flowchart of FIG. 14 may be configured to start when the receiving unit 311 receives the summary information from the in-vehicle terminal 2.

In step S501, the needs control unit 37 acquires the summary information output from the reception unit 311 and the vehicle ID of this vehicle. Then, based on the collection needs acquired by the needs acquisition unit 36 and the collection status of the travel data by the reception unit 311, the necessity of the travel data corresponding to this summary information is determined.

In step S502, the transmission unit 312 transmits the necessity determination result determined in S501 to the in-vehicle terminal 2 that transmits the summary information. When the summary information of the driving data for a plurality of driving links is collectively received from the in-vehicle terminal 2, the necessity of the driving data corresponding to the summary information is determined for each summary information, and the necessity for each summary information is determined. The rejection determination result may be transmitted to the in-vehicle terminal 2. In this case, for example, in the distinction of the necessity determination result for each summary information on the in-vehicle terminal 2, since the summary information is the summary information of the driving data for each driving link, the link ID in the summary information is used as the necessity judgment result. It may be possible by linking and sending.

[Traveling data transmission related processing]
Subsequently, an example of the flow of the traveling data transmission-related processing in the in-vehicle terminal 2 will be described with reference to the flowchart of FIG. The processing of the flowchart of FIG. 15 may be configured to start when, for example, the necessity determination result transmitted from the traveling data collection center 3 is received by the receiving unit 241 of the vehicle-mounted terminal 2.

In step S601, if the necessity determination result received from the travel data collection center 3 requires travel data (YES in S601), the process proceeds to step S602. On the other hand, when the traveling data is not required (NO in S601), the process proceeds to step S603.

In step S602, the transmission unit 242 transmits the travel data acquired in S5 to the travel data collection center 3. On the other hand, in step S603, the transmission unit 242 does not transmit the travel data acquired in S5 to the travel data collection center 3. The travel data acquired in S5 may be deleted from the stored travel data storage unit 28 when the processes of S602 and S603 are performed.

When the necessity judgment result for each driving data summary information for a plurality of driving links is received, the driving data is transmitted or transmitted to the driving data collection center 3 according to the necessity judgment result for each of these driving data. The configuration may or may not be used. Further, when the necessity determination result for each type of travel data is received, the travel data is collected by the travel data collection center 3 by narrowing down the travel data to the types required for the necessity determination result for each type of travel data. It may be configured to send to.

[Driving data collection process]
Subsequently, an example of the flow of the travel data collection process at the travel data collection center 3 will be described with reference to the flowchart of FIG. The processing of the flowchart of FIG. 16 may be configured to start when, for example, the necessity determination result requiring the traveling data is transmitted to the in-vehicle terminal 2 in S6.

In step S701, the receiving unit 311 receives the traveling data transmitted from the in-vehicle terminal 2. In step S702, the receiving unit 311 stores the traveling data received in S701 in the traveling data storage unit 33, and collects the traveling data transmitted from the in-vehicle terminal 2. The travel data collected and stored in the travel data storage unit 33 is output to the travel data utilization system by the collection result output unit 41.

<Summary of Embodiment 1>
According to the configuration of the first embodiment, the collection instruction information generation unit 39 generates the collection instruction information based on the collection needs, which is the information indicating the travel data that needs to be acquired and the conditions for acquiring the travel data. It is possible to generate collection instruction information for acquiring driving data at the in-vehicle terminal 2 of each vehicle at the link determined for each vehicle. Further, since the collection instruction information is transmitted to the vehicle-mounted terminal 2 of the vehicle, the vehicle-mounted terminal 2 of each vehicle acquires the traveling data according to the collection instruction information. The collection instruction information generation unit 39 determines a link for collecting driving data from the vehicle for each vehicle according to the traveling frequency for each link of the vehicle. It will be possible to determine the vehicle for which data can be easily acquired. Therefore, compared to the case where the vehicles for which the driving data is collected for each link are narrowed down to the vehicles for which the driving data can be easily acquired at the link and the collection instruction information is indiscriminately transmitted to a plurality of vehicles, the driving data collection center 3 is used. It is possible to reduce unnecessary communication volume.

Further, when the travel data collection center 3 receives the outline information from the in-vehicle terminal 2, the travel data collection center 3 has this outline based on the collection status of the travel data in the receiving unit 311 and the collection needs acquired by the needs acquisition unit 36. The necessity of driving data corresponding to the information is determined, and the necessity determination result is transmitted to the in-vehicle terminal 2. On the other hand, the in-vehicle terminal 2 determines that driving data that meets the collection needs is necessary and transmits the driving data to the driving data collection center 3, while the vehicle-mounted terminal 2 determines that driving data that exceeds the collection needs is not necessary and transmits the driving data collection center 3. Do not send to. Therefore, it is possible to suppress the reception of driving data that exceeds the collection needs, and to suppress unnecessary load and cost on the driving data collection center 3 side. Further, since the traveling data that meets the collection needs is received, it is possible to collect the required amount of traveling data at the traveling data collection center 3. Further, since the summary information received by the driving data collection center 3 from the in-vehicle terminal 2 has a smaller amount of information than the traveling data, the amount of information received from the in-vehicle terminal 2 for determining the necessity of the traveling data can be obtained. It is possible to suppress unnecessary load and cost on the driving data collection center 3 side. As a result, it becomes possible to collect a necessary amount of driving data while suppressing unnecessary load and cost on the driving data collection center 3 side.

(Embodiment 2)
In the first embodiment, the vehicle-mounted terminal 2 specifies the traveling link of the vehicle, and the identified traveling link is transmitted to the traveling data collection center 3, but the present invention is not necessarily limited to this. For example, the vehicle-mounted terminal 2 may not specify the vehicle travel link, and the travel data collection center 3 may specify the vehicle travel link (hereinafter, the second embodiment).

When the second embodiment is adopted, the vehicle-mounted terminal 2 may transmit the vehicle position detected by the locator 21 to the traveling data collection center 3 instead of the traveling link. In this case, this vehicle position corresponds to the position-related information. Further, instead of providing the in-vehicle terminal 2 with the map DB 22 and the map matching unit 23, the traveling data collection center 3 may have the same configuration as the map DB 22 and the map matching unit 23. Then, the travel data collection center 3 may perform map matching processing based on the vehicle position transmitted from the in-vehicle terminal 2 to specify the travel link of the vehicle.

Further, when the second embodiment is adopted, the collection instruction information is associated with the vehicle position (hereinafter referred to as the acquisition target position) for which the driving data should be acquired instead of the link for acquiring the traveling data for each vehicle. And it is sufficient. In this case, the acquisition determination unit 26 of the in-vehicle terminal 2 may determine whether or not the current vehicle position of the own vehicle is the acquisition target position associated with the own vehicle in the collection instruction information. When the current vehicle position of the own vehicle and the acquisition target position substantially match, the current vehicle position of the own vehicle may be determined to be the acquisition target position. Then, when the acquisition determination unit 26 determines that the current vehicle position of the own vehicle is the acquisition target position, the travel data acquisition unit 27 follows the acquisition condition associated with the acquisition target position in the collection instruction information, and the own vehicle The driving data of the own vehicle may be acquired from the sensor or the like of the vehicle.

When the second embodiment is adopted, the in-vehicle terminal 2 may be configured to acquire and use the vehicle position detected by another device without providing the locator 21.

(Embodiment 3)
In the above-described embodiment, a configuration is shown in which the travel data collection center 3 specifies the travel frequency for each link for each of a plurality of vehicles from the travel link or the vehicle position transmitted from the in-vehicle terminal 2, but the present invention is not necessarily limited to this. .. For example, the configuration may be such that the travel data collection center 3 can be used by acquiring the travel frequency specified by the server device other than the travel data collection center 3. Alternatively, the travel data collection center 3 may specify the travel frequency for each link for each of a plurality of vehicles from the operation record for each vehicle input by the operator or the like of the travel data collection center 3.

(Embodiment 4)
In the above-described embodiment, the collection instruction information generation unit 39 shows a configuration in which the collection instruction information generation unit 39 is sequentially updated even if the collection needs are not changed, but the present invention is not necessarily limited to this. For example, the collection instruction information generation unit 39 may not be updated unless the collection needs are changed. Even when this configuration is adopted, the travel data collection center 3 determines the necessity of travel data corresponding to the summary information, transmits the necessity determination result to the vehicle-mounted terminal 2, and the vehicle-mounted terminal 2 collects the data. It is determined that the traveling data that meets the needs is necessary and is transmitted to the traveling data collection center 3, while the traveling data that exceeds the collection needs is determined not to be necessary and is not transmitted to the traveling data collection center 3. Therefore, it is possible to collect a necessary amount of driving data while suppressing unnecessary load and cost on the driving data collection center 3 side.

The present disclosure is not limited to the above-described embodiment, and various modifications can be made within the scope of the claims, and can be obtained by appropriately combining the technical means disclosed in the different embodiments. Embodiments are also included in the technical scope of the present disclosure.

1 Driving data collection system, 2 In-vehicle terminal, 3 Driving data collection center, 24 Communication unit, 27 Driving data acquisition unit (data acquisition unit), 34 Driving frequency identification unit, 37 Needs control unit (necessity judgment unit), 39 Collection Instruction information generation unit, 241 receiving unit (vehicle side receiving unit), 242 transmitting unit (vehicle side transmitting unit), 311 receiving unit (collecting unit), 312 transmitting unit (center side transmitting unit)

Claims (8)

A data acquisition unit (27) that is mounted on a vehicle and acquires travel data, which is information obtained by traveling the vehicle, a vehicle-side transmission unit (242) that transmits information, and a vehicle-side reception unit (242) that receives information. 241), and the vehicle-side transmission unit includes an in-vehicle terminal (2) that transmits the travel data acquired by the data acquisition unit.
A travel data collection center (3) including a collection unit (311) for collecting the travel data transmitted from the vehicle side transmission unit of the vehicle-mounted terminal of the plurality of vehicles.
The driving data collection center
The road section for collecting the traveling data from the vehicle is determined for each vehicle according to the traveling frequency of the vehicle for each road section, and the traveling data is acquired by the in-vehicle terminal of each vehicle in the determined road section. The collection instruction information generation unit (39) that generates the collection instruction information to be obtained based on the collection needs, which is the information indicating the driving data that needs to be acquired and the conditions for acquiring the driving data.
It is equipped with a center-side transmitter (312) that transmits information.
The center-side transmission unit transmits the collection instruction information generated by the collection instruction information generation unit to the in-vehicle terminal of each vehicle .
The vehicle-side transmission unit of the previous SL-vehicle terminal, before transmitting the driving data acquired by the data acquisition unit, an overview of the travel data, send a small summary information amount of information than the traveling data ,
The driving data collection center
When the summary information is received from the in-vehicle terminal, the necessity of the travel data corresponding to the summary information is determined based on the collection status of the travel data in the collection unit and the collection needs. Equipped with a necessity judgment unit (37)
The center-side transmission unit transmits the necessity determination result of the necessity determination unit to the vehicle-mounted terminal, and the center side transmission unit transmits the necessity determination result.
The vehicle-side transmission unit of the in-vehicle terminal transmits the travel data when the necessity determination result received from the travel data collection center requires the travel data, while the travel data is transmitted. A driving data collection system that does not transmit the driving data when it does not require. The collection instruction information generation unit of the travel data collection center does not change the collection instruction information based on the collection status of the travel data at the collection unit and the collection needs. Also updates the collection instruction information to acquire the driving data required in the collection situation.
The center-side transmission unit of the travel data collection center transmits the sequentially updated collection instruction information to the in-vehicle terminal of each vehicle.
When the data acquisition unit of the vehicle-mounted terminal receives the newly updated collection instruction information from the travel data collection center in the collection instruction information generation unit, the data acquisition unit follows the newly updated collection instruction information. The driving data collection system according to claim 1, wherein the driving data is changed so as to acquire the driving data. The collection needs include the collection period of the travel data as a condition for acquiring the travel data.
The traveling data collection system according to claim 2, wherein the collection instruction information generation unit sequentially updates the collection instruction information at a frequency of being updated at least a plurality of times within the collection period. The in-vehicle terminal also transmits position-related information regarding the position of the vehicle.
The driving data collection center
A traveling frequency specifying unit (34) for specifying the traveling frequency of each of the plurality of vehicles for each road section from the position-related information transmitted from the in-vehicle terminals of the plurality of vehicles is provided.
The collection instruction information generation unit determines a road section for collecting the traveling data from the vehicle according to the traveling frequency of each of the plurality of vehicles specified by the traveling frequency specifying unit for each road section. The driving data collection system according to any one of claims 1 to 3. The collection instruction information generation unit determines, according to the traveling frequency of the vehicle for each road section, a road section having a traveling frequency equal to or higher than a threshold value as a road section for collecting the traveling data from the vehicle for each vehicle. The driving data collection system according to any one of claims 1 to 4. A collection unit (311) that collects travel data, which is data obtained by traveling of the vehicle, which is acquired and transmitted by the vehicle-mounted terminal (2) mounted on the vehicle, from the vehicle-mounted terminals of a plurality of the vehicles.
The road section for collecting the traveling data from the vehicle is determined for each vehicle according to the traveling frequency of the plurality of vehicles for each road section, and the traveling data is determined by the in-vehicle terminal of each vehicle in the determined road section. The collection instruction information generation unit (39) that generates the collection instruction information for acquiring the vehicle based on the collection needs, which is the information indicating the driving data that needs to be acquired and the conditions for acquiring the driving data.
It is equipped with a center-side transmitter (312) that transmits information.
The center-side transmission unit transmits the collection instruction information generated by the collection instruction information generation unit to the in-vehicle terminal of each vehicle.
When receiving summary information having a smaller amount of information than the running data, which is transmitted before the running data is transmitted from the vehicle-mounted terminal that has acquired the running data according to the collected instruction information, and shows the outline of the running data. A necessity determination unit (37) for determining the necessity of the travel data corresponding to this summary information based on the collection status of the travel data by the collection unit and the collection needs is provided.
The center-side transmission unit is a traveling data collection center that transmits the necessity determination result of the necessity determination unit to the vehicle-mounted terminal. Mounted on the vehicle
A data acquisition unit (27) that acquires driving data, which is data obtained by traveling the vehicle, and
Vehicle-side transmitter (242) that transmits information,
It is equipped with a vehicle-side receiver (241) that receives information.
The vehicle-side transmission unit transmits the travel data acquired by the data acquisition unit to the travel data collection center (3) that collects the travel data.
The vehicle-side transmitter is
Before transmitting the travel data acquired by the data acquisition unit, outline information showing an outline of the travel data and having a smaller amount of information than the travel data is transmitted.
Based on the travel data collection status , the travel data that needs to be acquired, and the collection needs that are information indicating the conditions for acquiring the travel data, which are received from the travel data collection center. When the necessity determination result of the travel data corresponding to the summary information determined in the above is that the travel data is required, the travel data is transmitted, but the travel data is not required. An in-vehicle terminal that does not transmit the driving data in some cases. The vehicle-side receiver receives the travel data in the road section of the own vehicle, which is transmitted from the travel data collection center and is determined for each vehicle according to the travel frequency of the plurality of vehicles for each road section. Receive the collection instruction information to get
The vehicle-mounted terminal according to claim 7, wherein when the vehicle-side receiving unit receives the collection instruction information, the data acquisition unit acquires the traveling data according to the received collection instruction information.

Images