JP6708134B2 - Driving data collection system and driving data collection center - Google Patents

Description

The present invention relates to a travel data collection system, and running data collection Centers for collecting running data from a plurality of vehicles.

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

JP, 2003-281674, A

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

The amount of travel data required for analysis needs to be a fixed amount for each road, but because the traffic volume of vehicles varies from road to road, the road data with low traffic volume will not have enough travel data, while the road with high traffic volume will have insufficient traffic data. It is conceivable that the collected driving data will be excessive. When the collected traveling data becomes excessive, the traveling data collection center side has a communication load for collecting traveling data, a cost for providing a memory for storing the collected traveling data, and the collected traveling data. The processing load and the like for analyzing the data unnecessarily increase. When an image is collected as driving data in order to generate a map and/or confirm changes in roads, the amount of information of the driving data becomes large, which causes a problem of unnecessary load and cost on the driving data collection center side. Becomes particularly large.

The present invention has been made in view of the above conventional problems, and an object thereof is to enable collecting a required amount of travel data while suppressing unnecessary load and cost on the travel data collection center side. to provide travel data acquisition system, and running data collection Centers.

The above objective is achieved by a combination of features described in independent claims, and the subclaims define further advantageous embodiments of the invention. The reference numerals in parentheses in the claims indicate the correspondence with the specific means described in the embodiments described below as one aspect, and do not limit the technical scope of the present invention. ..

To achieve the above object, engagement Ru inventions in running data acquisition system is mounted on a vehicle, the data acquisition unit for acquiring driving data is data obtained by the running of the vehicle (27), the data acquisition unit A travel data collection center including an in-vehicle terminal (2) including a travel data transmission unit (241) that transmits the acquired travel data, and a collection unit (312) that collects travel data transmitted from the in-vehicle terminals of a plurality of vehicles. The traveling data collection center includes a collection target determining unit (36) that determines, for each vehicle, a road section for collecting traveling data from the vehicle according to a traveling frequency of the plurality of vehicles for each road section. An acquisition information transmission unit (311) that transmits acquisition information for acquiring travel data at the vehicle-mounted terminal of each vehicle in the road section determined for each vehicle by the collection target determination unit to the vehicle-mounted terminal of each vehicle. The collection target determination unit collects the traveling data based on the importance of acquiring the traveling data for each road section of each vehicle, which is determined according to the traveling frequency of each vehicle for each road section. For each of the road sections to be set, it is determined that the vehicle with high importance is given priority to collect the travel data, and the importance increases as the number of other vehicles traveling on the target road section decreases. The collection target determining unit determines that, for each of the road sections for which the travel data is collected, when determining a vehicle for which the travel data is to be collected by giving priority to a vehicle having a high degree of importance, it is necessary for the target road section. Depending on the amount of collected travel data, the vehicle that collects the travel data is prioritized from the vehicles with higher importance, and the required collection amount of travel data differs depending on the target road section. in this case, the number of vehicles for collecting travel data, Ru varied in accordance with the collected amount of travel data required for each road segment.

In order to achieve the above object, the engaging Ru inventions in the running data collection center, are transmitted by acquiring the in-vehicle terminal mounted on a vehicle (2), the running data is data obtained by the running of the vehicle A collection unit (312) that collects data from on-vehicle terminals of a plurality of vehicles and a collection target determination that determines a road section from which the travel data is collected from the vehicle for each vehicle according to the travel frequency of the plurality of vehicles for each road section Part (36) and acquisition information transmission for transmitting acquisition information for acquiring traveling data by the in-vehicle terminal of each vehicle in the road section determined for each vehicle by the collection target determination unit to the in-vehicle terminal of each vehicle And a collection target determination unit based on the importance of acquisition of travel data of each vehicle for each road section, which is determined according to the travel frequency of each vehicle for each road section. For each road section for which travel data is to be collected, priority is given to vehicles with higher importance, and it is determined that the vehicles for which travel data is to be collected have priority. Therefore, the collection target determining unit targets the road sections for which the travel data is to be collected, when determining the vehicles for which the travel data is to be collected by prioritizing the vehicles with high importance. The number of vehicles that collect traveling data is determined according to the amount of traveling data that is required for the road section, and the vehicles that collect traveling data are prioritized from the vehicles with higher importance. If the amount of the collection are different, the number of vehicles for collecting travel data, Ru varied in accordance with the collected amount of travel data required for each road segment.

According to these, in the road section determined for each vehicle by the collection target determination unit, the acquisition information for acquiring the travel data by the in-vehicle terminal of each vehicle is transmitted from the acquisition information transmission unit to the in-vehicle terminal of each vehicle. Therefore, the vehicle-mounted terminal of each vehicle acquires the travel data according to the acquisition information. The collection target determination unit determines the road section for collecting the travel data from the vehicle for each vehicle according to the travel frequency of the plurality of vehicles for each road section, so that the vehicles for collecting the travel data are not biased for each road section. It will be possible to decide. Therefore, it is possible to prevent the driving data collected from the in-vehicle terminals of these vehicles from becoming excessive depending on the road section, and to collect the necessary amount of driving data while suppressing the unnecessary collection of driving data at the driving data collection center. To be able to do. As a result, it becomes possible to collect a required amount of travel data while suppressing unnecessary load and cost on the travel data collection center side.

It is a figure which shows an example of a schematic structure of the traveling data collection system 1. It is a figure which shows an example of a schematic structure of the vehicle-mounted terminal 2. It is a figure showing an example of a schematic structure of running data collection center 3. It is a figure for explaining an example of collection needs. It is a figure which shows an example of the acquisition target link with high traveling frequency for every vehicle AH. It is a figure for demonstrating an example of calculation of vehicle acquisition importance. It is a figure for explaining an example of calculation of a link acquisition importance. It is a figure for explaining an example of calculation of run acquisition importance. It is a figure for demonstrating an example of determination of an acquisition object link. It is a sequence diagram which shows an example of the flow of the traveling data acquisition related process in the traveling data collection system 1. 6 is a flowchart showing an example of the flow of a travel link identification transmission process in the vehicle-mounted terminal 2. It is a flow chart which shows an example of the flow of the run frequency specific processing in run data collection center 3. It is a flow chart which shows an example of a flow of table generation transmission processing in running data collection center 3. It is a flow chart which shows an example of the flow of traveling data acquisition transmission processing in in-vehicle terminal 2. It is a flow chart which shows an example of the flow of the travel data collection processing in the travel data collection center 3. It is a figure which shows an example of a schematic structure of the traveling data collection system 1a. It is a figure which shows an example of a schematic structure of the vehicle-mounted terminal 2a. It is a figure which shows an example of a schematic structure of the traveling data collection center 3a. It is a figure which shows an example of a schematic structure of the sub-collection apparatus 4.

A plurality of embodiments and modifications for disclosure will be described with reference to the drawings. Note that, for convenience of description, between a plurality of embodiments and modified examples, parts having the same functions as the parts shown in the drawings used in the above description are denoted by the same reference numerals, and description thereof will be omitted. There is a case. For the parts denoted by the same reference numerals, the description in other embodiments and/or modified examples can be referred to.

(Embodiment 1)
<Schematic configuration of the traveling data collection system 1>
Embodiment 1 of the present invention will be described below with reference to the drawings. As shown in FIG. 1, the traveling data collection system 1 includes an in-vehicle terminal 2 and a traveling data collection center 3 mounted on each of a plurality of vehicles.

The in-vehicle terminal 2 is mounted on a vehicle and acquires traveling data obtained by traveling of the vehicle. Further, the vehicle-mounted terminal 2 communicates with the travel data collection center 3 and transmits the travel data acquired by the own vehicle to the travel 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 vehicle-mounted terminal 2 will be described later.

The travel data collection center 3 is, for example, a server device, receives a travel data collection need from a travel data utilization system that utilizes travel data, and collects travel data corresponding to the collection needs from the in-vehicle terminals 2 of a plurality of vehicles. , Present the collected driving data to the driving data utilization system. The traveling data collection center 3 transmits to the vehicle-mounted terminals 2 mounted on a plurality of vehicles a target road table indicating the road sections (that is, links) for which the vehicle-mounted terminals 2 should acquire the traveling data. 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 may be composed of a plurality of server devices. Details of the traveling data collection center 3 will be described later.

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

The locator 21 includes a GNSS (Global Navigation Satellite System) receiver that receives positioning signals from a plurality of positioning satellites, and an inertial sensor such as a 3D gyro. 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 coordinates of latitude/longitude, for example. Note that the vehicle position may be detected by using a traveling distance obtained from the vehicle speed detected by a vehicle speed sensor mounted in the vehicle.

The map DB 22 is a non-volatile memory and stores map data such as link data and node data. The link data is composed of a unique number that identifies the link, a link length that indicates the length of the link, a link direction, link shape information, node coordinates of the start and end of the link, and road attribute data. 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 given a unique number for each node on the map, a node coordinate, a node name, a node type, a connection link ID in which a link ID of a link connecting to the node is described, an intersection type, etc. It consists of each data.

The map matching unit 23 performs known map matching processing on the basis of the vehicle position sequentially detected by the locator 21 and the map data stored in the map DB 22, so that the link (hereinafter , Running links) are sequentially identified.

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 DCM (Data Communication Module).

The transmission unit 241 of the communication unit 24 transmits the travel links of the own vehicle, which are sequentially identified by the map matching unit 23, to the travel data collection center 3. The transmission unit 241 may be configured to transmit the history of the travel links of the vehicle that are 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 supply of the vehicle is turned on to when it is turned off is stored in a memory, and the stored travel link history is stored at the travel data collection center 3 at the end of the trip. You can send it to. The travel link and the history of the travel link correspond to the position-related information in the claims.

Further, when the target road table is transmitted from the traveling data collection center 3, the receiving unit 242 of the communication unit 24 receives the target road table and stores it in the reference information storage unit 25. The receiving unit 242 corresponds to the acquisition information receiving unit in the claims. The reference information storage unit 25 may be, for example, a non-volatile memory. The target road table is associated with the links for which the travel data should be acquired for each vehicle. As an example, a configuration may be used in which a link for obtaining travel data is associated with each identifier that can identify each vehicle. Further, the target road table is associated with acquisition conditions such as the type of travel data to be acquired and the acquisition period of travel data for a link from which travel data is to be acquired (hereinafter, acquisition target link).

It should be noted that the target road table may be configured such that the acquisition target links are associated with acquisition conditions such as a time zone for acquiring travel data and a lane for acquiring travel data. For the lanes from which the travel data is collected, it is only necessary to distinguish between the up and down lanes, the first lane and the second lane, and so on. From the viewpoint of reducing the memory capacity of the reference information storage unit 25, it is preferable that an expiration date is set in the target road table and the reference road information storage unit 25 be deleted when the expiration date has passed.

The acquisition determination unit 26 refers to the target road table stored in the reference 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 in the target road table. It is determined whether the link is an acquisition target link.

When the acquisition determination unit 26 determines that the current traveling link of the own vehicle is the acquisition target link, the traveling data acquisition unit 27 follows the acquisition conditions of the own vehicle according to the acquisition conditions associated with the acquisition target link in the target road table. The traveling data of the own vehicle is acquired from sensors and the like. The travel data acquisition unit 27 corresponds to the data acquisition unit in the claims. As an example, the type of travel data to be acquired is acquired according to the type of travel data to be acquired. Further, the travel data is acquired when the acquisition conditions such as the travel data acquisition period, the travel data acquisition time zone, and the lane from which the travel data is acquired are met.

As an example of the travel data acquired by the travel data acquisition unit 27, image data of the surroundings of the vehicle captured by the periphery monitoring camera, the vehicle position detected by the locator 21, accuracy information of the vehicle position, and a vehicle speed sensor are detected. Vehicle speed, acceleration detected by the G sensor, yaw rate detected by the gyro sensor, and the like. The vehicle position accuracy information may be, for example, DOP (Dilution of precision) which is a positioning accuracy deterioration coefficient affected by the geometrical arrangement of the positioning satellites G _n viewed from the reception point of the positioning signal. The travel data acquired by the travel data acquisition unit 27 includes a brake signal output from a brake switch in response to a brake operation, a winker signal output from a winker switch in response to a winker operation, and an ABS (Antilock) output from an ECU. Brake System) operation information, running energy consumption, and the like.

The travel data acquisition unit 27 outputs the acquired travel data to the communication unit 24. The transmission unit 241 of the communication unit 24 transmits the travel data output from the travel data acquisition unit 27 to the travel data collection center 3. Therefore, the transmission unit 241 corresponds to the travel data transmission unit in the claims. The transmission unit 241 may be configured to sequentially transmit the travel data output from the travel data acquisition unit 27 to the travel data collection center 3, or may store the travel data output from the travel data acquisition unit 27 in a memory. Alternatively, the accumulated traveling data may be collectively transmitted to the traveling data collection center 3. In addition, the transmission unit 241 includes the traveling link of the vehicle that is sequentially identified by the map matching unit 23 or the vehicle position of the vehicle that is sequentially detected by the locator 21 when transmitting the traveling data to the traveling data collection center 3. It may be configured so that it will not be sent.

<Schematic configuration of the driving data collection center 3>
Subsequently, a schematic configuration of the traveling data collection center 3 will be described with reference to FIG. The traveling data collection center 3 is, for example, a server device as described above, and as illustrated in FIG. 3, the communication unit 31, the traveling history storage unit 32, the traveling frequency specifying unit 33, the traveling frequency DB 34, the needs acquisition unit 35, the target. A road table generation unit 36, a target road table storage unit 37, a travel data storage unit 38, and a collection result output unit 39 are provided.

The communication unit 31 communicates with the vehicle-mounted terminal 2. The communication unit 31 communicates with the vehicle-mounted terminal 2 via, for example, a base station and a public communication network. When the history of the travel link of the vehicle equipped with the vehicle-mounted terminal 2 is transmitted from the vehicle-mounted terminal 2 to the receiver 312 of the communication unit 31, the history of the vehicle-driving link is received. The receiving unit 312 stores 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, a configuration in which an identifier capable of identifying a vehicle and a history of travel links are stored in association with each other may be used. As the travel history storage unit 32, for example, a non-volatile memory may be used. The reception unit 312 receives the history of the travel links from the vehicle-mounted terminals 2 of the plurality of vehicles, and stores the history of the travel links of the plurality of vehicles in the travel history storage unit 32.

The traveling frequency specifying unit 33 specifies the traveling frequency for each link for each of a plurality of vehicles from the history for the latest fixed period stored in the traveling history storage unit 32. As an example, the number of times that the link has traveled during the period in which the traveling frequency is specified can be calculated, and the calculated number of times of traveling can be specified as the traveling frequency. The traveling frequency specifying unit 33 stores the traveling frequency for each link for each of a plurality of vehicles in the traveling frequency DB 34. As the traveling frequency DB 34, for example, a non-volatile memory may be used. It is preferable that the traveling frequency specifying unit 33 re-specify the traveling frequency every time a predetermined period elapses, and update the traveling frequency for each link stored in the traveling frequency DB 34 for each vehicle. The predetermined period referred to here is a period that can be set arbitrarily. The updating of the traveling frequency may be irregular, triggered by an operator's operation or the like.

The needs acquisition unit 35 acquires the collection needs of the traveling data utilization system. The needs acquisition unit 35 may be configured to make a communication connection with the travel data utilization system and automatically acquire the collection needs. In addition, the needs acquisition unit 35 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 conditions for acquiring travel data that needs to be collected. As an example, as shown in FIG. 4, the collection needs include information such as roads, sections, lanes, time zones, periods, and vehicle types for which travel data is to be collected, and types and amount of travel data to be collected. is there. The amount of travel data to be collected (hereinafter, collected amount) may be represented by the required number of runs.

The target road table generation unit 36, based on the collection needs acquired by the needs acquisition unit 35 and the link-by-link travel frequency of each of the plurality of vehicles stored in the travel frequency DB 34, the target road for each of the plurality of vehicles. Generate a table. The target road table generating unit 36 corresponds to the collection target determining unit in the claims. The details of the method of generating the target road table will be described below.

First, the target road table generation unit 36 determines a link (that is, a collection target link) and a collection amount for collecting travel data based on the collection needs acquired by the needs acquisition unit 35. As an example, a link corresponding to a section of a road to be collected is determined as a collection target link. In the following, the case where the collection target links are the link I, the link J, the link K, the link L, and the link M between two certain points will be described as an example. The collection amount may be determined according to the collection amount of the collection needs. When the collection amount differs depending on the type of travel data, the collection amount may be set to a large value, or the collection amount may be determined for each different collection amount. When the collection amount is determined for each type of travel data having a different collection amount, for example, the subsequent generation of the target road table may be configured to generate separately for each type of travel data having a different collection amount.

The target road table generation unit 36 also determines acquisition conditions such as the type of travel data to be acquired, the lane from which the travel data is acquired, the time zone, the period, and the vehicle type, based on the collection needs acquired by the needs acquisition unit 35.

In addition, the target road table generation unit 36 extracts vehicles having a high traveling frequency of the collection target links from the traveling frequencies of the plurality of vehicles for each link stored in the traveling frequency DB 34. As an example, a vehicle in which the number of times of travel of the collection target link is equal to or greater than a prescribed number is extracted. The specified number referred to here is a value that can be set a plurality of times and can be set arbitrarily. When there are a plurality of collection target links, the target road table generation unit 36 may be configured to extract a vehicle having a high traveling frequency of at least one of the collection target links. In the following, the description will be continued by exemplifying the case where the vehicles with high traveling frequency of the collection target links are the vehicle A, the vehicle B, the vehicle C, the vehicle D, the vehicle E, the vehicle F, the vehicle F, and the vehicle H.

Further, the target road table generation unit 36 specifies the collection target link having a high traveling frequency for each of the plurality of vehicles having a high traveling frequency of the collection target link. Then, the number of travels of the collection target link for each vehicle (hereinafter, the number of travel links) and the number of vehicles having a high traveling frequency for each collection target link (hereinafter, the number of travel vehicles) are specified.

Here, an example of a collection target link that is frequently traveled for each of the vehicles A to H will be described with reference to FIG. Arrows in FIG. 5 indicate collection target links that are frequently traveled in each of the vehicles A to H. It is assumed that the collection target links of the vehicle A that frequently travel are links I and J. Further, the collection target links with high traveling frequency are links I to K in vehicle B, link I in vehicle C, links I to L in vehicle D, links I to M in vehicle E, links LM in vehicle F, and vehicles LM. It is assumed that the link is G in G and the links I to K are in vehicle H. In the example of FIG. 5, the number of traveling links is “2” for vehicle A, “3” for vehicle B, “1” for vehicle C, “4” for vehicle D, “5” for vehicle E, and “5” for vehicle F. 2", vehicle G has "1", and vehicle H has "3". The number of traveling vehicles is “6” for link I, “5” for link J, “5” for link K, “3” for link L, and “2” for link M. The subsequent description will be continued with reference to the example of FIG.

Subsequently, the target road table generation unit 36 determines the importance of acquisition of travel data for each collection target link for each vehicle, which is determined according to the travel frequency of each vehicle for each link (hereinafter, travel acquisition importance. ) Is determined. As an example, the travel acquisition importance for each collection target link for each vehicle is determined from the number of travel links for each vehicle and the number of travel vehicles for each collection target link described above. The details of the determination of the travel acquisition importance will be described below.

The target road table generation unit 36 calculates the importance of the responsibility for acquiring the traveling data of the vehicle for each collection target link (hereinafter, vehicle acquisition importance) from the number of traveling vehicles for each collection target link. As an example, the reciprocal of the number of running vehicles is calculated as the vehicle acquisition importance for each collection target link. As shown in FIG. 6, the reciprocal of the number of traveling vehicles for each collection target link has the same value for all the relevant vehicles with high traveling frequency of the collection target link. In the example of FIG. 6, the corresponding vehicles of the link I are vehicles A, B, C, D, E, and H, and the reciprocal of the number of running vehicles is “0.17”. The corresponding vehicles of the link J are vehicles A, B, D, E, H, and the reciprocal of the number of running vehicles is "0.2". The vehicles corresponding to the link K are vehicles B, D, E, G, and H, and the reciprocal of the number of running vehicles is “0.2”. The corresponding vehicles of the link L are vehicles D, E and F, and the reciprocal of the number of running vehicles is "0.33". The corresponding vehicles of the link M are vehicles E and F, and the reciprocal of the number of running vehicles is “0.5”.

The reciprocal of the number of traveling vehicles decreases as the number of vehicles traveling along a certain collection target link increases, and increases as the number of vehicles traveling along a certain collection target link decreases. For example, when the reciprocal of the number of traveling vehicles is 1, it indicates that there is no other vehicle traveling on the collection target link. In other words, the reciprocal of the number of running vehicles relatively represents the importance of the responsibility for acquiring the running data of that vehicle in the collection target link.

Further, the target road table generation unit 36 calculates the importance of the responsibility for acquiring travel data of the collection target links for each vehicle (hereinafter, link acquisition importance) from the number of travel links for each vehicle. As an example, the reciprocal of the number of running links is calculated as the link acquisition importance for each vehicle. As shown in FIG. 7, the reciprocal of the number of running links for each vehicle has the same value for all collection target links with high running frequency of the vehicle. In the example of FIG. 7, the collection target links of the vehicle A are the links I and J, and the reciprocal of the number of running links is “0.5”. The collection target links of the vehicle B are the links I to K, and the reciprocal of the number of running links is “0.33”. The collection target link of the vehicle C is the link I, and the reciprocal of the number of running links is “1”. The collection target links of the vehicle D are the links I to L, and the reciprocal of the number of running links is “0.25”. The collection target links of the vehicle E are the links I to M, and the reciprocal of the number of running links is “0.2”. The collection target links of the vehicle F are the links L and M, and the reciprocal of the number of running links is “0.5”. The collection target link of the vehicle G is the link K, and the reciprocal of the number of running links is “1”. The collection target links of the vehicle H are the links I to K, and the reciprocal of the number of running links is “0.33”.

The reciprocal of the number of running links decreases as the number of collection target links that a certain vehicle travels to increases, and increases as the number of collection target links that a vehicle travels to another decreases. For example, when the reciprocal of the number of running links is 1, it indicates that there is no collection target link running for a certain vehicle in addition to the collection target link. That is, the reciprocal of the number of running links represents the degree of importance of acquiring running data at the collection target link in a vehicle.

Then, the target road table generation unit 36 calculates the travel acquisition importance from the calculated vehicle acquisition importance and link acquisition importance. Specifically, the traveling acquisition importance is calculated by multiplying the vehicle acquisition importance and the link acquisition importance for each vehicle and the collection target link. In the example of the present embodiment, the calculation may be performed by rounding down the third decimal place. For example, regarding the travel acquisition importance degree of the vehicle A on the link I, the vehicle acquisition importance degree is “0.17” and the link acquisition importance degree is “0.5”, so 0.17×0.5= It becomes 0.085. Then, the third decimal place of 0.085 is rounded down, resulting in 0.08 (see FIG. 8). The same applies to other vehicle and collection target link combinations. This travel acquisition importance corresponds to the importance in the claims. The travel acquisition importance may be weighted by, for example, multiplying the travel frequency of each vehicle and collection target link.

Subsequently, the target road table generation unit 36 gives priority to the vehicle having the higher travel acquisition importance for each collection target link in order of priority, in accordance with the data amount of the travel data to be collected (that is, the collection amount). The number of vehicles is selected, and the collection target link (hereinafter, acquisition target link) from which the travel data is acquired for each vehicle is determined (see the white outline in FIG. 9 ). For example, when the collected amount, that is, the required number of times of travel is two, at least two vehicles may be selected and the acquisition target link may be determined. In consideration of the possibility that the vehicle does not travel the acquisition target link, a configuration may be adopted in which a larger number of vehicles are selected for the data amount of the travel data to be collected and the acquisition target link is determined.

Then, the target road table generation unit 36 generates the acquisition target link determined for each vehicle as a target road table. The target road table generation unit 36 also generates the target road table in association with the determined acquisition conditions. The target road table may be generated as a different table for each vehicle, or may be generated as one table in which each acquisition target link is associated with each vehicle. This target road table corresponds to the acquisition information in the claims.

In addition to the configuration described above, a configuration may be employed in which processing for further suppressing the variation in the amount of travel data acquired for each vehicle is performed. For example, the collection target links are ranked in advance according to the degree of importance of travel acquisition for each vehicle, and the number of collection target links in one vehicle is set as the acquisition target link by narrowing down the target rank or more as the collection target. It may be configured to avoid this.

The setting rank here may be set according to, for example, the collection amount, the number of collection target links, and the number of traveling vehicles. As an example, a rank corresponding to a number obtained by dividing the number obtained by multiplying the collection amount by the number of links to be collected by the number of traveling vehicles and raising the decimal point may be used as the setting rank. In this case, when the collection amount is two times the number of times of travel, the number of links to be collected is 5, and the number of traveling vehicles is 8, the decimal point of (2×5)/8=1.25 is rounded up. The second highest importance level corresponding to 2 is the set rank.

In addition, regarding the collection target links that do not reach the number of vehicles according to the collection amount due to the above-mentioned narrowing down, except the ones that could be narrowed down as collection targets, the process of lowering the setting rank and narrowing down again is performed. The configuration may be repeated until the number is reached. In addition, regarding the collection target links that do not reach the number of vehicles according to the collection amount, the vehicle with the smaller number of acquisition target links may be prioritized and selected until the number of vehicles according to the collection amount is reached.

In the case where the travel acquisition importance is the same and the above-mentioned selection and narrowing down cannot be performed, a priority order may be randomly given to perform the above-described selection and narrowing down. In addition, the configuration may be such that the amount of past travel data acquired is stored for each vehicle, and the above-described selection and narrowing down are performed by increasing the priority of the vehicle having the smaller amount of past acquisition.

The transmission unit 311 of the communication unit 31 transmits the target road table generated by the target road table generation unit 36 to the vehicle-mounted terminal 2. The transmission unit 311 corresponds to the acquisition information transmission unit in the claims. When the target road table is generated as a different table for each vehicle, the transmission unit 311 may be configured to specify the vehicle corresponding to each target road table and transmit the target road table. Further, when the target road table is one table in which each acquisition target link is associated with each vehicle, all the vehicles corresponding to this target road table are designated and the target road table is transmitted. And it is sufficient.

The receiving unit 312 of the communication unit 31 receives the travel data when the travel data acquired by the vehicle-mounted terminal 2 according to the target road table transmitted from the travel data collection center 3 is transmitted. Then, the reception unit 312 stores the received traveling data in the traveling data storage unit 38. As the traveling data storage unit 38, for example, a non-volatile memory may be used. The receiving unit 312 stores the traveling data received from the vehicle-mounted terminals 2 of the plurality of vehicles in the traveling data storage unit 38, and collects the traveling data transmitted from the vehicle-mounted terminals 2 of the plurality of vehicles. Therefore, the receiving unit 312 corresponds to the collecting unit in the claims.

The receiving unit 312 identifies the link from which the travel data is acquired, based on the travel link, vehicle position, etc. of the vehicle equipped with the on-vehicle terminal 2, which is included in the travel data transmitted from the on-vehicle terminal 2, and links the received travel data. It may be stored separately in the traveling data storage unit 38. Further, the receiving unit 312 diverts the traveling link, vehicle position, etc. of the vehicle equipped with the in-vehicle terminal 2 included in the traveling data transmitted from the in-vehicle terminal 2 to the history of the traveling link stored in the traveling history storage unit 32. It may be configured to.

The collection result output unit 39 outputs the travel data collected and stored in the travel data storage unit 38 to the travel data utilization system. The collection result output unit 39 establishes a communication connection with the traveling data utilization system, automatically reads out the traveling data collected and stored in the traveling data storage unit 38, and outputs the traveling data to the traveling data utilization system. do it. In addition, the collection result output unit 39 is operated by an operator to instruct the output of the travel data collected and stored in the travel data storage unit 38, and the travel data collected and stored in the travel data storage unit 38 is stored. The data may be read and output to, for example, an external storage medium.

<Traveling data acquisition related processing>
Here, with reference to the sequence diagram of FIG. 10 and the flowcharts of FIGS. 11 to 15, regarding an example of the flow of processing related to acquisition of travel data in the travel data collection system 1 (hereinafter, travel data acquisition-related processing) I will explain. The sequence diagram of FIG. 10 is a sequence diagram showing the overall flow of the traveling data collection system 1, and the flowcharts of FIGS. 11 to 15 are flowcharts showing the flow of each routine of FIG. 10.

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

In step S3, the traveling data collection center 3 generates a target road table for each of the plurality of vehicles from the collection needs acquired by the needs acquisition unit 35 and the traveling frequency for each of the plurality of vehicles specified in S2. , A process of transmitting to the in-vehicle terminal 2 (hereinafter, table generation/transmission process). In step S4, the vehicle-mounted terminal 2 performs a process of acquiring traveling data according to the target road table transmitted from the traveling data collection center 3 in S3 and transmitting the traveling data to the traveling data collection center 3 (hereinafter, traveling data acquisition transmission process). .. In step S5, the travel data collection center 3 performs a process of collecting travel data transmitted from the plurality of vehicle-mounted terminals 2 in S4 (travel data collection process). The processing of S1 and S2 may be configured to be performed in parallel with the timing of performing the processing of S3 to S5.

Subsequently, the flow of each routine of S1 to S5 of FIG. 10 will be described below with reference to the flowcharts of FIGS. 11 to 15.

[Run link specific transmission process]
First, an example of the flow of the traveling link identification transmission process in the vehicle-mounted terminal 2 will be described with reference to the flowchart of FIG. The process of the flowchart of FIG. 11 may be configured to be performed, for example, for each trip described above of the vehicle in which the vehicle-mounted terminal 2 is mounted.

In step S101, the locator 21 sequentially detects the vehicle position of the own vehicle. In step S102, the map matching unit 23 performs map matching processing based on the vehicle position sequentially detected in S101 and the map data stored in the map DB 22, thereby sequentially identifying the running links of the own vehicle. .. In step S103, the transmission unit 241 transmits to the traveling data collection center 3 the history of the traveling links of the vehicle that are sequentially identified in S102.

[Trend frequency identification processing]
Next, an example of the flow of the traveling frequency identification processing in the traveling data collection center 3 will be described using the flowchart of FIG. The process of the flowchart of FIG. 12 may be configured to be performed, for example, every time the above-described predetermined period has elapsed.

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

In step S203, the traveling frequency identifying unit 33 identifies the traveling frequency for each link for each of a plurality of vehicles from the history for the latest fixed period stored in the traveling history storage unit 32. In step S204, the traveling frequency identification unit 33 stores the traveling frequency for each link for each of the plurality of vehicles identified in S203 in the traveling frequency DB 34.

[Table generation and transmission process]
Next, an example of the flow of table generation and transmission processing in the travel data collection center 3 will be described using the flowchart of FIG. The process of the flowchart of FIG. 13 may be configured to be performed, for example, when the needs acquisition unit 35 acquires the collection needs of the travel data utilization system.

In step S301, the target road table generation unit 36 determines a collection target link, a collection amount, and an acquisition condition based on the collection needs acquired by the needs acquisition unit 35. In step S302, the target road table generation unit 36 uses the collection target links, the collection amount, and the acquisition conditions determined in step S301, and the driving frequency for each link for each of a plurality of vehicles stored in the driving frequency DB 34. Then, a target road table for each of a plurality of vehicles is generated. In step S303, the transmission unit 311 transmits the target road table generated by the target road table generation unit 36 to the vehicle-mounted terminal 2. The transmission unit 311 transmits the target road table to the vehicle-mounted terminal 2 of the vehicle for which the acquisition target link has been determined.

[Traveling data acquisition and transmission processing]
Next, an example of the flow of travel data acquisition and transmission processing in the vehicle-mounted terminal 2 will be described using the flowchart of FIG. The process of the flowchart of FIG. 14 may be configured to start when the receiving unit 242 of the vehicle-mounted terminal 2 receives the target road table transmitted from the traveling data collection center 3, for example.

In step S401, the reception unit 242 stores the target road table received from the traveling data collection center 3 in the reference information storage unit 25. In step S402, locator 21 detects the vehicle position of the own vehicle. In step S403, the map matching unit 23 performs map matching processing based on the vehicle position detected in S402 and the map data stored in the map DB 22, thereby identifying the traveling link of the own vehicle.

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

In step S405, the traveling data acquisition unit 27 acquires traveling data of the own vehicle from the sensor of the own vehicle or the like according to the acquisition condition associated with the acquisition target link in the target road table. If the acquisition condition is not met, the travel data may not be acquired.

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

For example, the traveling data transmission timing may be when the traveling data acquisition period ends or when new traveling data is acquired in S405. When the time when the acquisition period of the travel data ends is adopted as the transmission timing, the travel data accumulated during the acquisition period is collectively transmitted. On the other hand, when the time when new travel data is acquired in S405 is adopted as the transmission timing, this travel data is transmitted every time new travel data is acquired in S405.

[Traveling data collection processing]
Next, an example of the flow of the travel data collection process in the travel data collection center 3 will be described using the flowchart of FIG. The process of the flowchart of FIG. 15 may be configured to start when the target road table is transmitted to the vehicle-mounted terminal 2, for example.

In step S501, the reception unit 312 receives the travel data transmitted from each of the plurality of vehicle-mounted terminals 2. In step S502, the reception unit 312 stores the travel data received in S501 in the travel data storage unit 38, and collects the travel data transmitted from the vehicle-mounted terminals 2 of a plurality of vehicles. The travel data collected and stored in the travel data storage unit 38 is output to the travel data utilization system by the collection result output unit 39.

<Summary of Embodiment 1>
According to the configuration of the first embodiment, the vehicle-mounted terminal 2 of each vehicle acquires traveling data according to the target road table transmitted from the traveling-data collection center 3. In the target road table, the acquisition target links for which travel data should be acquired are prioritized in order from the vehicle with the highest travel acquisition importance, which is determined according to the travel frequency of each link of multiple vehicles, and the collection amount is determined according to the collection amount. The number of vehicles is associated. Since the travel acquisition importance increases as the number of vehicles traveling on a certain collection target link decreases, the configuration of the first embodiment allows the vehicle to collect travel data for each collection target link. It is possible to more reliably acquire the travel data by limiting the acquisition target links to vehicles with high travel frequency while preventing the deviation. Therefore, it is possible to prevent the travel data collected from the in-vehicle terminals 2 of these vehicles from becoming excessive due to the link, and to suppress the wasteful collection of the travel data at the travel data collection center 3 while at the same time providing the necessary amount of travel data. Allows to collect. As a result, it becomes possible to collect a required amount of travel data while suppressing unnecessary load and cost on the travel data collection center side 3.

In addition, since the travel acquisition importance increases as the number of collection target links that a certain vehicle travels to decreases, the travel acquisition importance degree is high according to the configuration of the first embodiment. Nevertheless, it is possible to prevent a vehicle that does not acquire the travel data from occurring, and it is possible to suppress the deviation in the number of collection target links that acquire the travel data for each vehicle. Therefore, it is possible to suppress the unfairness in which the communication time and the communication cost of the traveling data are biased between the vehicles.

(Modification 1)
Although the vehicle-mounted terminal 2 specifies the traveling link of the vehicle and transmits the specified traveling link to the traveling data collection center 3 in the first embodiment, the present invention is not limited to this. For example, a configuration may be adopted in which the vehicle-mounted link is not specified by the vehicle-mounted terminal 2 but the vehicle-driving link is specified by the travel-data collection center 3 (hereinafter, modified example 1).

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

Further, when the first modification is adopted, the target road table is associated with the vehicle position (hereinafter, acquisition target position) from which the travel data is to be acquired, instead of the link from which the travel data is to be acquired, for each vehicle. And it is sufficient. In this case, the acquisition determination unit 26 of the vehicle-mounted terminal 2 may determine whether the current vehicle position of the own vehicle is the acquisition target position associated with the own vehicle in the target road table. In addition, 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 traveling data acquisition unit 27 follows the acquisition conditions associated with the acquisition target position in the target road table according to the acquisition condition. The configuration may be such that the traveling data of the own vehicle is acquired from the sensor or the like.

When the first modification is adopted, the vehicle-mounted terminal 2 may not have the locator 21 and may be configured to acquire and use the vehicle position detected by another device.

(Embodiment 2)
In the first embodiment and the first modified example, the configuration in which the vehicle-mounted terminal 2 determines whether to acquire the travel data has been described, but the present invention is not limited to this. For example, the configuration may be as in the following second embodiment. Embodiment 2 of the present invention will be described below with reference to the drawings.

<Schematic configuration of the traveling data collection system 1a>
As shown in FIG. 16, the traveling data collection system 1a includes an in-vehicle terminal 2a mounted on each of a plurality of vehicles, a traveling data collection center 3a, and a sub-collection device 4. The travel data collection system 1a is different from the travel data of the first embodiment except that the on-vehicle terminal 2a and the travel data collection center 3a are included instead of the on-vehicle terminal 2 and the travel data collection center 3 and that the sub-collection device 4 is included. It is similar to the collection system 1.

In the travel data collection system 1a, the vehicle-mounted terminal 2a and the travel data collection center 3a do not communicate with each other. The traveling data collection center 3a can communicate with a plurality of sub-collection devices 4 via a communication network, and the sub-collection device 4 can communicate with vehicle-mounted terminals 2a of a plurality of vehicles via a communication network. I shall.

<Schematic configuration of in-vehicle terminal 2a>
First, the schematic configuration of the vehicle-mounted terminal 2a will be described with reference to FIG. As shown in FIG. 17, the vehicle-mounted terminal 2a includes a locator 21, a map DB 22, a map matching unit 23, a travel data acquisition unit 27a, and a communication unit 28. The vehicle-mounted terminal 2 a does not include the travel data acquisition unit 27 a instead of the travel data acquisition unit 27, the communication unit 28 instead of the communication unit 24, and the reference information storage unit 25 and the acquisition determination unit 26. Except for the points, it is the same as the in-vehicle terminal 2 of the first embodiment.

The traveling data acquisition unit 27a sequentially acquires traveling data of a preset type as the vehicle travels. Then, the acquired travel data is output to the communication unit 28. The travel data acquisition unit 27a corresponds to the data acquisition unit in the claims. An example of the travel data acquired by the travel data acquisition unit 27a is the same as the example of the travel data acquired by the travel data acquisition unit 27 described in the first embodiment. The travel data acquisition unit 27a may have a configuration in which the range in which travel data is sequentially acquired is limited to a specific area and set in advance.

The communication unit 28 communicates with the sub collection device 4. It is preferable that the communication unit 28 communicates with the sub-collection device 4 via a high-speed wireless LAN or the like with low or low communication cost. Further, the transmission unit 281 of the communication unit 28 transmits the travel data output from the travel data acquisition unit 27a to the sub collection device 4. Therefore, the transmission unit 281 corresponds to the travel data transmission unit in the claims.

The transmission unit 281 may be configured to sequentially transmit the traveling data output from the traveling data acquisition unit 27a to the sub-collection device 4, or may store the traveling data output from the traveling data acquisition unit 27a in a large-capacity memory. A configuration may be adopted in which the traveling data that has been accumulated is collectively transmitted to the sub-collection device 4. When transmitting the travel data to the sub-collection device 4, the transmission unit 281 also includes the travel link of the vehicle that is sequentially identified by the map matching unit 23 and transmits the travel data.

<Schematic configuration of the traveling data collection center 3a>
Subsequently, a schematic configuration of the traveling data collection center 3a will be described with reference to FIG. As shown in FIG. 18, the travel data collection center 3a includes a travel history storage unit 32, a travel frequency identification unit 33, a travel frequency DB 34, a needs acquisition unit 35, a target road table generation unit 36, a target road table storage unit 37, and a travel. The data storage unit 38, the collection result output unit 39, and the communication unit 40 are provided. The traveling data collection center 3a is the same as the traveling data collection center 3 of the first embodiment except that the communication unit 40 is provided instead of the communication unit 31.

The communication unit 40 communicates with the sub collection device 4. The communication unit 40 communicates with the sub collection device 4 via, for example, a base station and a public communication network. When the history of the travel link of the vehicle equipped with the vehicle-mounted terminal 2a is transmitted from the sub-collection device 4, the reception unit 402 of the communication unit 40 receives the history of the travel link. Similarly to the receiving unit 312, the receiving unit 402 stores the history of the traveling link of the vehicle received from the sub-collection device 4 in the traveling history storage unit 32 in association with the vehicle.

The transmission unit 401 of the communication unit 40 transmits the target road table generated by the target road table generation unit 36 to the sub collection device 4. This target road table corresponds to the extraction information of the claims, and the transmission unit 401 corresponds to the extraction information transmission unit of the claims. In addition, when the traveling data extracted by the sub-collection device 4 according to the target road table transmitted from the traveling data collection center 3 is transmitted, the reception unit 402 receives this traveling data. Then, the receiving unit 402 collects the traveling data transmitted from the sub-collecting device 4 by storing the received traveling data in the traveling data storage unit 38 in the same manner as the receiving unit 312. Therefore, the receiving unit 402 corresponds to the collecting unit in the claims.

<Schematic configuration of the sub-collection device 4>
Subsequently, a schematic configuration of the sub-collection device 4 will be described with reference to FIG. As shown in FIG. 19, the sub-collection device 4 includes a first communication unit 41, a travel history storage unit 42, a travel data storage unit 43, a second communication unit 44, a reference information storage unit 45, an extraction determination unit 46, and an extraction. A part 47 is provided. As an example, when a commercial vehicle such as a taxi or a transportation vehicle is used as the vehicle, the sub-collection device 4 may be a PC or the like of each business office.

The first communication unit 41 communicates with the vehicle-mounted terminal 2a. The communication unit 31 communicates with the vehicle-mounted terminal 2a via, for example, a high-speed wireless LAN. The receiving unit 411 of the first communication unit 41 receives the travel data when the travel data acquired by each of the plurality of vehicle-mounted terminals 2a is transmitted. Then, the reception unit 411 stores the travel link of the vehicle included in the received travel data in the travel history storage unit 42 in association with this vehicle. As an example, a configuration in which an identifier capable of identifying a vehicle and a travel link are stored in association with each other may be used. As the travel history storage unit 42, for example, a non-volatile memory may be used.

Further, the reception unit 411 stores the travel data received from the plurality of vehicle-mounted terminals 2 in the travel data storage unit 43. As the travel data storage unit 43, for example, a non-volatile memory may be used. The receiving unit 411 stores the traveling data received from the vehicle-mounted terminals 2 of the plurality of vehicles in the traveling data storage unit 43, and collects the traveling data transmitted from the vehicle-mounted terminals 2 of the plurality of vehicles. Therefore, the receiving unit 411 corresponds to the intermediate collecting unit in the claims. The receiving unit 411 identifies the link from which the travel data is acquired by the travel link of the vehicle equipped with the in-vehicle terminal 2a included in the travel data transmitted from the in-vehicle terminal 2a, and stores the received travel data for each link in the travel data. It may be stored in the unit 43.

The second communication unit 44 communicates with the traveling data collection center 3a. The second communication unit 44 communicates with the traveling data collection center 3a via, for example, a base station and a public communication network. The transmission unit 441 of the second communication unit 44 transmits the history of the traveling link for each vehicle stored in the traveling history storage unit 32 to the traveling data collection center 3a. Further, when the target road table is transmitted from the traveling data collection center 3 a, the receiving unit 442 of the second communication unit 44 receives the target road table and stores it in the reference information storage unit 45. The receiving unit 442 corresponds to the extraction information receiving unit in the claims. The reference information storage unit 45 may be, for example, a non-volatile memory. The target road table is the same as that described in the first embodiment.

The extraction determination unit 46 refers to the target road table stored in the reference information storage unit 45, and corresponds to the acquisition target link of the acquisition target vehicle among the travel links stored in the travel history storage unit 42. Determine the link. The extraction unit 47 sets the travel data of the acquisition target vehicle associated with the link determined to be the acquisition target link by the extraction determination unit 46, according to the acquisition conditions associated with the target road table, the travel data storage unit 43. Extract from. As an example, the number of types of travel data that should be acquired that match the acquisition conditions such as the acquisition period of travel data, the time period of travel data acquisition, the lane from which the travel data is acquired, etc. is acquired for each target link. To extract. Then, the extraction unit 47 outputs the extracted travel data to the second communication unit 44. The transmission unit 441 of the second communication unit 44 transmits the travel data extracted by the extraction unit 47 to the travel data collection center 3a. Therefore, the transmission unit 441 corresponds to the extracted data transmission unit in the claims.

<Summary of Embodiment 2>
According to the configuration of the second embodiment, instead of the configuration in which the vehicle-mounted terminal 2 narrows down the traveling data collected by the traveling data collection center 3 of the first embodiment, the traveling data collection center 3a narrows down the traveling data. The configuration performed by the collecting device 4 is adopted. Even when such a configuration is adopted, the same effect as that of the first embodiment can be obtained.

Further, in the travel data collection system 1a of the second embodiment, when the sub-collection device 4 cannot extract the target amount of travel data for the acquisition target link only by extracting the travel data according to the target road table, it is sufficient. It may be configured to replenish the unused portion. As an example, the sub-collection device 4 stores another vehicle that has traveled through the acquisition target link (hereinafter, supplement target link) that needs supplementation of travel data, and the travel link for each vehicle stored in the travel history storage unit 32. Identify from the history of. Then, the extraction unit 47 may be configured to supplement the missing data by additionally extracting the travel data for the specified supplement target link of the vehicle from the travel data storage unit 43. According to this, even when the vehicle for which the travel data is acquired does not actually travel on the acquisition target link and the target amount of travel data cannot be extracted, the sub-collection device 4 supplements the insufficient amount. Will be possible. As a result, it is possible to stably collect the required amount of travel data at the travel data collection center 3a while suppressing unnecessary collection of travel data at the travel data collection center 3a.

(Modification 2)
In the second embodiment, the sub-collection device 4 includes the traveling history storage unit 42 and the traveling data storage unit 43 that collectively store data, but the configuration is not necessarily limited to this. For example, the sub-collection device 4 may not include the travel history storage unit 42 and the travel data storage unit 43 that collectively store data. In this case, the extraction determination unit 46 may be configured to sequentially determine whether the travel link included in the travel data received by the reception unit 411 corresponds to the acquisition target link of the acquisition target vehicle. .. When the extraction determination unit 46 determines that the acquisition target vehicle is the acquisition target link, the extraction unit 47 may output the received travel data to the second communication unit 44.

(Modifications 3 and 4)
Although the vehicle-mounted terminal 2a specifies the traveling link of the vehicle and transmits the specified traveling link to the sub-collection device 4 in the second embodiment, the present invention is not limited to this. For example, the in-vehicle terminal 2a does not specify the traveling link of the vehicle, but the sub-collecting device 4 identifies the traveling link of the vehicle (hereinafter, modified example 3), or the traveling data collection center 3a identifies the traveling link of the vehicle. A configuration (hereinafter, modified example 4) may be adopted.

When the modifications 3 and 4 are adopted, the vehicle position detected by the locator 21 may be transmitted from the vehicle-mounted terminal 2a to the sub-collection device 4 instead of the traveling link. In this case, this vehicle position corresponds to the position-related information in the claims.

Further, in the case of adopting the modified example 3, if the vehicle-mounted terminal 2a is provided with the map DB 22 and the map matching unit 23, the sub-collection device 4 is provided with the same configuration as the map DB 22 and the map matching unit 23. Good. Then, the sub-collection device 4 performs map matching processing based on the vehicle position transmitted from the vehicle-mounted terminal 2a, identifies a traveling link of the vehicle, and transmits the traveling link of the vehicle to the traveling data collection center 3a. It may be configured.

On the other hand, in the case of adopting the modified example 4, instead of providing the in-vehicle terminal 2a with the map DB 22 and the map matching unit 23, the travel data collection center 3a may have the same configuration as the map DB 22 and the map matching unit 23. Good. Further, the sub-collection device 4 may be configured to transmit the vehicle position transmitted from the vehicle-mounted terminal 2a to the traveling data collection center 3a. Then, the travel data collection center 3a may perform the map matching process based on the vehicle position transmitted from the sub-collection device 4 to specify the travel link of the vehicle.

Further, in the case where the fourth modification is adopted, the target road table is associated with the vehicle position (hereinafter, acquisition target position) from which the travel data is to be acquired, instead of the link from which the travel data is to be acquired, for each vehicle. And it is sufficient. In this case, the extraction determination unit 46 of the sub-collection device 4 determines the vehicle position corresponding to the acquisition target position of the acquisition target vehicle among the vehicle positions stored in the travel history storage unit 42. The vehicle position may be determined to correspond to the acquisition target position when the vehicle position and the acquisition target position substantially match. Then, the extraction unit 47 sets the travel data of the vehicle to be acquired, which is associated with the vehicle position determined to be the acquisition target position by the extraction determination unit 46, according to the acquisition conditions associated with the target road table. The configuration may be extracted from the traveling data storage unit 43.

When the modified examples 3 and 4 are adopted, the vehicle-mounted terminal 2a may be configured not to include the locator 21 and to acquire and use the vehicle position detected by another device.

(Modification 5)
In the above-described embodiment, the target road table generation unit 36 shows a configuration in which the vehicle having the high travel acquisition importance calculated from the vehicle acquisition importance and the link acquisition importance is determined as the vehicle for collecting the travel data. However, this is not necessarily the case. For example, the target road table generation unit 36 may handle the vehicle acquisition importance as the travel acquisition importance, and prioritize the vehicle having the high vehicle acquisition importance as the vehicle for collecting the travel data.

(Modification 6)
In the above-described embodiment and modified examples, a configuration has been shown in which the traveling data collection centers 3 and 3a specify the traveling frequency for each link for each of a plurality of vehicles from the traveling link or the vehicle position transmitted from the vehicle-mounted terminal 2. It is not necessarily limited to this. For example, the travel data collection centers 3 and 3a may be configured to be usable by the travel data collection centers 3 and 3a acquiring the travel frequency specified by a server device other than the travel data collection centers 3 and 3a. In addition, the traveling data collection centers 3 and 3a may be configured to specify the traveling frequency for each link for each of a plurality of vehicles from the operation record for each vehicle input by the operator of the traveling data collection centers 3 and 3a. ..

It should be noted that the present invention is not limited to the above-described embodiments and modifications, and various modifications can be made within the scope of the claims, and the technical means disclosed in the different embodiments and modifications, respectively. Embodiments obtained by appropriately combining the above are also included in the technical scope of the present invention.

1,1a traveling data collection system, 2,2a vehicle-mounted terminal, 3,3a traveling data collection center, 4 sub collection device, 27,27a traveling data acquisition unit (data acquisition unit), 33 traveling frequency identification unit, 36 target road table Generation unit (collection target determination unit), 47 extraction unit, 241 transmission unit (travel data transmission unit), 242 reception unit (acquisition information reception unit), 281 transmission unit (travel data transmission unit), 311 transmission unit (for acquisition) Information transmitting unit), 312 receiving unit (collecting unit), 401 transmitting unit (extracting information transmitting unit), 402 receiving unit (collecting unit), 411 receiving unit (intermediate collecting unit), 441 transmitting unit (extracted data transmitting unit) , 442 receiver (extraction information receiver)

Claims (5)

A data acquisition unit (27) that is mounted on a vehicle and acquires traveling data that is data obtained by traveling of the vehicle, and a traveling data transmission unit (241) that transmits the traveling data acquired by the data acquisition unit. An in-vehicle terminal (2) provided,
A travel data collection center (3) including a collection unit (312) for collecting the travel data transmitted from the vehicle-mounted terminals of a plurality of the vehicles;
The traveling data collection center is
A collection target determination unit (36) that determines, for each vehicle, a road section for collecting the travel data from the vehicle according to a traveling frequency of the plurality of vehicles for each road section,
Transmission of acquisition information for transmitting acquisition information for acquiring the travel data at the vehicle-mounted terminal of each vehicle in the road section determined for each vehicle by the collection target determination unit to the vehicle-mounted terminal of each vehicle And a part (311) ,
The collection target determining unit determines the traveling data based on the importance of acquiring the traveling data for each road section for each vehicle, which is determined according to the traveling frequency for each road section of the plurality of vehicles. For each of the road sections to be collected, the vehicle with high importance is prioritized and determined as the vehicle for collecting the travel data,
The degree of importance is higher as the number of vehicles running elsewhere in the target road section decreases,
For each of the road sections where the traveling data is collected, the collection target determining unit determines that the vehicle having the higher importance is required for the target road section when determining the vehicle for collecting the traveling data. The number of traveling data to be collected depends on the number of traveling data to be collected and the vehicle for which the traveling data is to be collected is prioritized from the vehicles having the higher importance. if different, the traveling data acquisition system Ru varied by road segment combined number of vehicles to collect the driving data, the collection of travel data required. In claim 1,
The in-vehicle terminal also transmits position-related information regarding the position of the vehicle,
The traveling data collection center is
A travel frequency specifying unit (33) for specifying the travel frequency of each of the plurality of vehicles for each road section from the position-related information transmitted from the vehicle-mounted terminals of the plurality of vehicles,
The collection target determining unit determines a road section for collecting the traveling data from the vehicle for each vehicle, according to the traveling frequency of the plurality of vehicles for each road section identified by the traveling frequency identifying unit. Data collection system. In claim 1 or 2 ,
The traveling data collection system in which the degree of importance increases according to the number of vehicles that are traveling on a target road section being reduced and the number of road sections that are traveling on a target vehicle being reduced. In any one of claims 1 to 3
The in-vehicle terminal,
An acquisition information receiving unit (242) for receiving the acquisition information transmitted from the acquisition information transmitting unit,
The data acquisition unit, when the acquisition information receiving unit receives the acquisition information, acquires the travel data according to the received acquisition information,
The traveling data collection system transmits the traveling data acquired by the data acquisition unit to the traveling data collection center according to the acquisition information received by the acquisition information reception unit. A collection unit (312) for collecting, from the in-vehicle terminals of the plurality of vehicles, traveling data that is data obtained by traveling of the vehicle, which is acquired and transmitted by the in-vehicle terminal (2) mounted in the vehicle;
A collection target determination unit (36) that determines, for each vehicle, a road section for collecting the travel data from the vehicle according to a traveling frequency of the plurality of vehicles for each road section,
Transmission of acquisition information for transmitting acquisition information for acquiring the travel data at the vehicle-mounted terminal of each vehicle in the road section determined for each vehicle by the collection target determination unit to the vehicle-mounted terminal of each vehicle And a part (311) ,
The collection target determining unit determines the traveling data based on the importance of acquiring the traveling data for each road section for each vehicle, which is determined according to the traveling frequency for each road section of the plurality of vehicles. For each of the road sections to be collected, the vehicle with high importance is prioritized and determined as the vehicle for collecting the travel data,
The degree of importance is higher as the number of vehicles running elsewhere in the target road section decreases,
For each of the road sections where the traveling data is collected, the collection target determining unit determines that the vehicle having the higher importance is required for the target road section when determining the vehicle for collecting the traveling data. The number of traveling data to be collected depends on the number of traveling data to be collected and the vehicle for which the traveling data is to be collected is prioritized from the vehicles having the higher importance. if different, the travel data collection center where Ru varied by road segment combined number of vehicles to collect the driving data, the collection of travel data required.

Images