JP2019101445A - Od traffic volume estimation device and od traffic volume estimation system - Google Patents

Abstract

To provide an OD traffic volume estimation device and an OD traffic volume estimation system for enabling a highly accurate prediction.SOLUTION: An OD (origin-destination) traffic volume estimation device 1 includes: an OD database 110 for storing a traffic volume between previously set origin and destination for each OD; a route distribution database 111 for storing a distribution value of a route-specific traffic volume between an origin and a destination for each OD; a route information database 112 for storing a link and a required time as route information for each route; a section traffic volume acquisition unit 103 for acquiring an observation traffic volume or a prediction traffic volume of the predetermined section; and an OD traffic volume estimation unit 105 for identifying an OD and an OD route being a generation source of an observation traffic volume or a prediction traffic volume of the predetermined section on the basis of route information including an observation traffic volume or a prediction traffic volume of the predetermined section and the predetermined section, distributing a distribution value of a traffic volume of a route identified based on the route distribution database to each OD route, and estimating a traffic volume of an OD being a generation source of a traffic volume of the predetermined section on the basis of a traffic volume between an origin and a destination to be stored in the OD database and a distribution value of a traffic volume.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an OD traffic volume estimation apparatus and system for estimating OD traffic volume including road traffic of vehicles moving from a traffic generation zone (O) to a concentration zone (D) and public traffic such as buses and railways.

  There are various types of urban traffic such as automobile road traffic and public transport such as buses and railways. In order to properly operate road traffic such as congestion control, road maintenance and toll setting, it is important to estimate OD which is the cause of congestion and its traffic demand. In addition, technology to estimate OD traffic volume is important in order to properly operate public transportation such as route planning in the future.

  As a method for predicting the OD traffic volume, the number of movements from a given outbreak zone (O) to a concentration zone (D) is determined based on survey information such as traffic census and person trips and survey information such as demographics The estimation method is used on a case-by-case basis. For example, in road traffic, in order to obtain basic information for road planning and maintenance, a survey of road traffic start and end points (hereinafter referred to as road OD survey) is carried out about every five years. In the road OD survey, an OD matrix (OD table) is created with a zone around the municipalities as a basic zone, and the movement traffic volume between ODs is estimated based on the OD survey data. The estimation data is used to estimate the future OD traffic volume by quantitatively evaluating the occurrence and concentration of road use, purpose and frequency of road use, loss due to traffic congestion, environmental load, etc.

  However, since the conventional OD traffic volume estimation method is based on survey data for a specific survey period, it is difficult to accurately grasp changes in traffic volume per unit time. Here, the unit time is appropriately set, for example, every hour, every day, or every month. In addition, since such surveys are conducted every few years, it is difficult to grasp current and hourly changes in traffic volume. Therefore, it is unsuitable for estimating the change of the present traffic demand which changes with time progress for the movement from the generation | occurrence | production zone (O) of the movement by the traffic user to the concentration zone (D).

By the way, from the information of OD traffic volume, the information of route network such as road network and railway network in road traffic, and the information of traffic environment attached to the route network such as information on speed restrictions of roads and information about installation places of traffic lights There is a method using traffic flow simulation to predict traffic flow based on a predetermined movement model.
Traffic flow simulation can be divided into two types: macro traffic flow simulation for relatively wide area route networks and micro traffic flow simulation for relatively narrow area route networks. In macro traffic flow simulation, the traffic volume of a section is predicted based on a traffic flow model in which the traffic flow is regarded as fluid. Also, in micro traffic flow simulation, the behavior of an autonomous agent and its interaction with each other, which are regarded as individual mobile objects such as vehicles or their aggregates, are represented by a model, and the behavior of the agent is used using that model Predict the impact of traffic on traffic in the route network.

  Macro traffic flow simulation has the disadvantage that it is not suitable for forecasting traffic flow reflecting the effects of detailed traffic environment such as road speed regulation and traffic signals. On the other hand, micro traffic flow simulation has a disadvantage that many parameters need to be set to execute the simulation. Therefore, there is a method of combining the two types of simulation to alleviate the disadvantages. For example, by extracting traffic problems such as sections with high traffic volume by macro traffic flow simulation, and analyzing traffic problems extracted by micro traffic flow simulation in detail, it is possible to predict traffic flows for which measures have been taken against traffic problems. There is a way.

In order to predict traffic flow using such traffic flow simulation, it is necessary to set huge and detailed OD traffic volume and traffic environment parameters. In addition, in order to obtain highly accurate prediction results, it is necessary to set parameters close to the actual values.
The technique disclosed in Patent Document 1 has been proposed for estimating OD traffic volume using such traffic flow simulation. In Patent Document 1, correction of simulation parameters such as OD traffic volume and route selection probability is repeated so that traffic volume in a predetermined section predicted by traffic flow simulation based on traffic volume between ODs approaches observed traffic volume. A method of estimating traffic is disclosed. By using this method, it is possible to correct the traffic volume between the ODs of the traffic simulation based on the observed traffic volume acquired in real time, and estimate the OD traffic volume in real time.

JP 2005-182383 A

In the configuration described in Patent Document 1, given OD traffic volume is given to the simulation unit to predict traffic flow, and the predicted traffic volume of the predetermined section is compared with the observed traffic volume, and the predicted traffic volume is the observed traffic volume It is effective in estimating the OD traffic volume which is close to the actual one, because the OD traffic volume is repeatedly corrected until it approaches OD traffic flow. However, in the configuration described in Patent Document 1, no consideration is given to the case where there are a plurality of combinations of OD, which is the generation source of observed traffic in the predetermined section, and the OD traffic, and such a case In the above, the OD which is the actual source is not necessarily obtained as a solution, and there may occur a problem that it is difficult to estimate the actual OD traffic volume.
Thus, the present invention provides an OD traffic volume estimation device and an OD traffic volume estimation system capable of highly accurate prediction with respect to traffic volume (traffic demand) of an OD section that changes with time.

In order to solve the above problems, the OD traffic estimation apparatus according to the present invention is an OD traffic estimation apparatus that estimates traffic moving from a traffic generation zone (O) to a concentration zone (D), and is set in advance At least distinguishably, for each route, an OD database that stores the traffic volume between ODs identifiably for each OD, a route distribution database that stores distribution values of traffic volume for each route between ODs for each OD, and A route information database storing links and required times as route information, a section traffic volume acquisition unit for acquiring observed traffic volume or predicted traffic volume of a predetermined section, and observed traffic volume or predicted traffic volume of the predetermined section And an OD as a source of the observed traffic volume or the predicted traffic volume of the predetermined section based on the route information including the predetermined section and a route of the OD, and The distribution value of the traffic volume of the identified route is read out, and the observed traffic volume or predicted traffic volume of the predetermined section is distributed to each OD route, and the traffic volume between the ODs stored in the OD database and the traffic volume And an OD traffic volume estimation unit configured to estimate a traffic volume of an OD, which is a generation source of the traffic volume of the predetermined section, based on the distribution value of
In the OD traffic estimation system according to the present invention, an OD traffic estimation apparatus for estimating traffic moving from a traffic generation zone (O) to a concentration zone (D), an observed traffic volume of a predetermined section or the like A section traffic provision device for obtaining predicted traffic volume, an OD / route data provision device for obtaining route information of at least traffic volume between OD and route-specific traffic volume between OD, and these are mutually communicably connected The OD traffic volume estimation device stores the traffic volume between ODs acquired from the OD and route data providing device in a discriminable manner for each OD, and the OD and route data provision Route allocation database for storing the distribution value of traffic volume by route between ODs obtained from the device for each OD, and included in the route information obtained from the OD / route data providing device A route information database storing identifiably links and required times for each route, a section traffic volume acquisition unit for acquiring the observed traffic volume or predicted traffic volume of a predetermined section from the section traffic volume providing device; Identifying an OD as a generation source of the observed traffic volume or predicted traffic volume of the predetermined zone and a route of the OD based on the observed traffic volume or predicted traffic volume of the predetermined zone and route information including the predetermined zone, The traffic distribution value of the route specified from the route distribution database is read out and the observed traffic volume or predicted traffic volume of the predetermined section is distributed to the routes of each OD, and the traffic between the ODs stored in the OD database And an OD traffic volume estimation unit configured to estimate a traffic volume of OD which is a generation source of the traffic volume of the predetermined section based on the volume and the distribution value of the traffic volume.

According to the present invention, it is possible to provide an OD traffic volume estimation device and an OD traffic volume estimation system capable of highly accurate prediction with respect to traffic volume (traffic demand) of an OD section that changes with time. Become.
Problems, configurations, and effects other than those described above will be apparent from the description of the embodiments below.

BRIEF DESCRIPTION OF THE DRAWINGS It is a whole schematic block diagram of OD traffic volume estimation system which concerns on one Example of this invention. It is a figure which shows the example of hardware constitutions of OD traffic volume estimation apparatus which comprises OD traffic volume estimation system shown in FIG. It is a flowchart which shows the processing flow of OD * route data acquisition part which comprises OD traffic volume estimation apparatus shown in FIG. It is a figure which shows the example of a data structure of OD database which comprises OD traffic volume estimation apparatus shown in FIG. It is a figure which shows the example of a data structure of the route distribution database which comprises OD traffic volume estimation apparatus shown in FIG. It is a figure which shows the example of a data structure of the route information database which comprises OD traffic volume estimation apparatus shown in FIG. It is a flowchart which shows the processing flow of the traffic information acquisition part which comprises OD traffic volume estimation apparatus shown in FIG. It is a flowchart which shows the processing flow of OD traffic volume estimation part which comprises OD traffic volume estimation apparatus shown in FIG. It is a figure which shows an example of the estimation result of OD traffic volume output to the input / output part which comprises OD traffic volume estimation apparatus shown in FIG.

  An OD traffic volume estimation system according to an embodiment of the present invention is a traffic volume (traffic volume) that travels between a traffic generation zone (O zone) and a concentration zone (D zone) based on changes in traffic volume on a predetermined section. Estimate the demand) in real time. The OD traffic volume estimation apparatus constituting the OD traffic volume estimation system estimates, for example, an OD as a generation source of the zone traffic volume and the OD traffic volume from the zone traffic volume and traffic information acquired from the external system. In the embodiment shown below, the route between ODs and the traffic volume (route traffic volume), the actual required time of each section provided by the traffic information provision apparatus, etc., and the traffic volume of the predetermined section are used. A technique for estimating an OD which is a generation factor of traffic in a predetermined section and its OD traffic (traffic demand) and its generation time is described. At that time, in the estimation of the OD traffic volume, the transit time of each section (or via point) is traced back based on route information such as required time, speed and distance of the target route, and OD which is the generation factor of the above-mentioned predetermined section traffic volume Identify the time of occurrence of traffic.

Generally, the OD data (OD) is defined as data obtained by integrating from the origin to the end point. In this specification, the traffic generation zone is defined as O zone, and the concentration zone is defined as D zone.
For example, although the entrance and exit of a vehicle (car) which is a mobile object is specified by an ETC (Electronic Toll Collection System) on an expressway etc., for example, in a general road, each home (each residential facility) In the case of (origin), the OD data including the main road becomes enormous. On the other hand, with regard to the end point (destination), it is possible to narrow down to a certain extent such as "station" or "commercial facility" on a general road.
Therefore, in consideration of the general road, for example, the entrance to the main road is set as the "generation zone (O zone)", that is, the main road into which vehicles (cars) from multiple homes (residential facilities) enter It is possible to narrow down the OD data by making the entrance of the generation zone (O zone). In addition, the setting of "the generation | occurrence | production zone (O zone)" and the "concentration zone (D zone)" is not limited above, but is set suitably.
Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[OD traffic volume estimation system]
FIG. 1 is an overall schematic configuration diagram of an OD traffic estimation system according to an embodiment of the present invention. As shown in FIG. 1, the OD traffic estimation system 10 includes an OD traffic estimation device 1, a section traffic providing device 2, and an OD / route data providing device 3, which can communicate with each other by the communication network 5. Is configured. In addition to the above, the traffic information providing apparatus 4 for providing information on movement such as traffic information and operation information to the communication network 5, and a GPS carried by a mobile connected to the communication network 5 via the base station 6 A portable information terminal 7 on which (Global Positioning System) is mounted, and an on-board information system 8 mounted on a mobile object such as a car are connectable.

The OD traffic volume estimation device 1 has a function of estimating the OD which is the generation factor of the traffic volume and the traffic volume, and the time of its occurrence from the traffic volume of the section and the traffic information regarding the movement between them.
The section traffic providing device 2 has a function of providing section traffic such as observed traffic through the communication network 5. The section traffic volume provision device 2 includes the portable information terminal 7 on which the above-described GPS is mounted and the section traffic volume acquired from a measuring device such as a vehicle sensor (traffic counter) or a camera installed in a predetermined moving section. The section traffic volume may be calculated from movement data (person probe data and probe car data) of the in-vehicle information system 8, and the calculated section traffic volume may be transmitted to the communication network 5.

When the traffic generation zone is O zone and the concentration zone is D zone, the OD / route data provision device 3 moves OD traffic volume generated for each OD section from O zone to D zone and the movement path between the OD zones It has a function to calculate each allocation value and its route information based on traffic data measured (observed) in the past.
The OD traffic estimation device 1 mutually exchanges necessary information with the section traffic providing device 2, the OD / route data providing device 3, and the traffic information providing device 4 via the communication network 5. The section traffic providing apparatus 2 transmits the acquired section traffic to the OD traffic estimating apparatus 1 via the communication network 5. The OD / route data provision device 3 sends the OD traffic volume generated for each OD section going from the O zone to the D zone, the distribution value for each movement route between the ODs, and the route information thereof to the OD traffic volume estimation device 1 It transmits via the communication network 5. In the present embodiment, the OD traffic volume estimation device 1 distributes the OD traffic volume between each OD and the traffic volume classified by route, which is calculated from traffic data measured (observed) in the past from the OD / route data provision device 3 The values and their route information are obtained via the communication network 5. Here, the route information is data in which road segments (road links and / or nodes) going from the departure point to the destination point with the arbitrary point in the O zone as the departure point and the arbitrary point in the D zone as the destination is there.

  The OD traffic volume estimated by the OD traffic volume estimation device 1 and the time of occurrence thereof are transmitted to an external system (not shown) via the communication network 5, and a predetermined movement is made based on the OD traffic volume estimated. It is used for traffic control and traffic control to distribute traffic volume to moving segments with less traffic volume and congestion elimination in the segment. Here, as the external system, for example, in the case of a bus that is a public traffic, an operation management system, a traffic flow control system that controls traffic flow by charging, etc. may be mentioned.

[OD traffic volume estimation device]
The OD traffic volume estimation device 1 is constituted by a so-called computer (information processing apparatus) including, for example, a CPU (processor), a storage device formed of a semiconductor, a hard disk drive, etc., and as shown in FIG. Route data acquisition unit 102, section traffic acquisition unit 103, traffic information acquisition unit 104, OD traffic estimation unit 105, input / output unit 106, OD database 110, route distribution database 111, route information database 112, section traffic database A traffic information database 114 and a map data database 115 are provided.

  For example, at least one of the OD / route data acquisition unit 102, the section traffic acquisition unit 103, the traffic information acquisition unit 104, and the OD traffic estimation unit 105, which constitutes the OD traffic estimation device 1, is a program (for example, It may be configured to be realized by a program stored in a program memory. Also, with regard to the OD database 110, the route distribution database 111, the route information database 112, the section traffic volume database 113, the traffic information database 114, and the map data database 115, a plurality of storage devices (respective storage devices such as semiconductor memory and hard disk) Type may be different), and each data may be stored in the corresponding storage device, divided into a plurality of storage areas in one or more storage devices, and stored in each storage area. Each data may be stored. In FIG. 1, the flow of data in the OD traffic estimation device 1 is indicated by a solid line, and the reference to information is indicated by a broken line.

  Hereinafter, in the present embodiment, the OD traffic estimation apparatus 1 acquires the section traffic of a car using a road from the section traffic providing apparatus 2 via the communication network 5 and targets the usage demand of the car. Although the form which estimates OD traffic volume of is demonstrated as an example, it is not restricted to this. For example, in public transportation such as railways or buses, the OD traffic volume of the public transportation service may be estimated based on the traffic volume of the section acquired from the collection system (not shown) of the traffic IC card. Similarly, even if indoors, section traffic volumes (number of movements) at predetermined two points of a mobile body such as a human being indoors are acquired, and OD traffic volumes (number of OD movements) indoors are estimated. good. Here, acquisition of the section traffic volume (number of movements) at predetermined two points of a mobile body such as a human being is executed based on the position information of the portable information terminal 7 on which the GPS carried by the human being is mounted. . Moreover, with an indoor, the apartment which is a residence facility, a commercial facility, or an office building etc. are mentioned, for example. The above-mentioned section traffic volume and movement information are acquired from the section traffic volume provision device 2, the OD / route data provision device 3 or the traffic information provision device 4.

The communication interface 101 performs communication control between the OD traffic estimation device 1 and the communication network 5 and, via the communication network 5, a section traffic providing device 2, an OD / route data providing device 3, and / or traffic. It exchanges data with the information providing device 4.
The OD / route data acquisition unit 102 receives an OD table including traffic volume information between ODs from the OD / route data provision device 3 via the communication network 5 and the communication interface 101, and the OD traffic volume of the OD table. The traffic distribution value of each route and the respective route information are acquired. The OD / route data acquisition unit 102 transmits the acquired OD table (OD data) to the OD database 110, the acquired traffic volume distribution value for each route to the route distribution database 111, and the acquired route information to the route information database 112. Store. The OD / route data acquisition unit 102 synchronizes with the timing at which the OD / route data is updated in the OD / route data provision device 3 and at a predetermined cycle or from the OD / route data acquisition unit 102 to the communication interface 101 and At the timing when the data transmission request is output to the OD / route data provision device 3 via the communication network 5, the OD / route data is acquired.

  The section traffic volume acquisition unit 103 acquires the observed traffic volume or the predicted traffic volume of a predetermined section from the section traffic volume provision device 2 connected to the communication network 5 through the communication interface 101, and transmits it to the section traffic volume database 113. Store. The time and section of the section traffic volume to be acquired is the section traffic volume updated in the section traffic volume provision device 2, or is scheduled in advance as periodic acquisition processing, or the user (via the input / output unit 106) In addition to being set by the administrator, it may be set from an external system (not shown) via the communication network 5. The section traffic volume stored in the section traffic volume database 113 is used by the OD traffic volume estimation unit 105 to estimate the OD traffic volume.

  The traffic information acquisition unit 104 acquires traffic information such as the required time and moving speed for each predetermined section of a predetermined area or route, the congestion section, and the degree thereof from the traffic information providing device 4 connected to the communication network 5 It is stored in the information database 114. The traffic information acquisition unit 104 synchronizes with the timing at which the traffic information is updated in the traffic information providing device 4 and at predetermined intervals or from the traffic information acquisition unit 104 to the traffic via the communication interface 101 and the communication network 5 At the timing when the traffic information transmission request is output to the information providing device 4, traffic information of a predetermined time and place is acquired.

  The OD traffic volume estimation unit 105 reads the traffic volume of the predetermined section from the section traffic volume database 113, reads the route information passing through the section (predetermined section) from the route information database 112, and reads the section traffic volume Identify the OD that is the cause of the section's traffic volume) and its route. Then, the OD traffic volume estimation unit 105 reads the distribution value of the traffic volume using the specified route from the route distribution database 111, and based on the distribution value and the section traffic volume, calculates the route traffic volume using the route. calculate. The OD traffic volume estimation unit 105 calculates the traffic volume of all routes traveling between the ODs based on the obtained route traffic volume and the traffic volume allocation value of other routes between the ODs, and estimates the OD traffic volume. Do. Here, since the time zone information of a predetermined interval is attached to the OD data stored in the OD database 110 and the route distribution value of each OD stored in the route distribution database 111, it corresponds to the observation time of the section traffic volume OD data of the time zone to be used and its path allocation value are read from the OD database 110 and the path allocation database 111. The occurrence time of the OD traffic volume passing through the section during the relevant time zone is based on the required time or travel speed of the route stored in the traffic information database 114, and the time required to pass the section along the route Time is estimated retroactively to the O zone. If traffic information of a road section or time zone corresponding to the traffic information database 114 does not exist (is not stored), the OD traffic volume estimation unit 105 transmits the OD to the traffic information providing device 4 via the traffic information acquisition unit 104. A transmission request for traffic information necessary for traffic volume estimation is output, and traffic information required for estimation of the above-mentioned OD traffic volume is acquired from the traffic information provision device 4 via the communication network 5. As for the failure of traffic information acquisition, or the required time of the road section where traffic information is not provided by the traffic information providing device 4, the OD traffic volume estimation unit 105 calculates the standard of the road section required from the map data database 115. The required time may be calculated based on the acquisition of the required time or the distance and speed (regulatory speed).

  The input / output unit 106 uses the communication network 5 to estimate OD traffic from the section traffic providing apparatus 2, the OD / route data providing apparatus 3, and the traffic information providing apparatus 4 (section traffic, OD Data, route allocation data, route information, traffic information) is acquired. Further, the input / output unit 106 displays the information for estimating the OD traffic and the execution result (OD traffic estimation information) on the display unit (not shown) of the OD traffic estimation device 1 and / or the external device 9. Output to the display unit (not shown) or transmitted to an external system (not shown) via the communication network 5. The execution result (OD traffic volume estimation information) is, on the map read from the map data database 115, the position of the section and its traffic volume (or traffic information), the OD corresponding to the section traffic volume, its estimated traffic volume, The time may be displayed. The input / output unit 106 also receives user input from the external device 9. Then, in response to the user input, each process of the OD / route data acquisition unit 102, the section traffic volume acquisition unit 103, the traffic information acquisition unit 104, and the OD traffic volume estimation unit 105 constituting the OD traffic volume estimation device 1 Or one of them is executed.

FIG. 2 is a diagram showing an example of the hardware configuration of the OD traffic estimation device that constitutes the OD traffic estimation system shown in FIG. As shown in FIG. 2, the OD traffic estimation device 1 can be realized by the computer 20. The computer 20 includes a control unit 21, a display unit (display device) 22, an operation unit 24, a storage unit 25, a communication interface 101, and a bus 26 connecting these. The control unit 21 includes a CPU 21a, a ROM 21b, and a RAM 21c. The CPU 21a, the ROM 21b, and the RAM 21c are connected to the bus 26, respectively.
The CPU 21a reads out from the ROM 21b a program code of software for realizing the functions of the OD / route data acquisition unit 102, the section traffic acquisition unit 103, the traffic information acquisition unit 104, the OD traffic estimation unit 105, etc. . Variables, parameters, and the like generated during the arithmetic processing are temporarily written to the RAM 21 c. For example, a liquid crystal display monitor or an organic EL display is used as the display unit 22, and the result of processing executed by the computer 20 is visibly displayed to the user. For example, a keyboard, a mouse or the like is used as the operation unit 24, and the user can use the operation unit 24 to perform predetermined operation input and instruction input. In addition, the storage unit 25 implements the above-described OD database 110, route allocation database 111, route information database 112, section traffic volume database 113, traffic information database 114, and map data database 115.

Next, processing in the OD traffic estimation device 1 will be described.
[Process by OD traffic estimation device]
First, OD / path data acquisition processing in the OD / path data acquisition unit 102 will be described. FIG. 3 is a flow chart showing the processing flow of the OD / route data acquisition unit 102 that constitutes the OD traffic volume estimation device 1 shown in FIG.
As shown in FIG. 3, in step S101, the OD / route data acquisition unit 102 requests the OD / route data provision device 3 for OD / route data of a predetermined area or route. Specifically, the OD / route data acquisition unit 102 outputs a transmission request for OD / route data of a predetermined area or route to the OD / route data providing device 3 via the communication interface 101 and the communication network 5. Here, as described above, the OD and route data include an OD table including information on traffic between each OD, a traffic flow distribution value of each route of each OD traffic of the OD table, and each route information Including.

In step S102, the OD / path data acquisition unit 102 acquires OD / path data from the OD / path data provision device 3 via the communication network 5 and the communication interface 101.
In step S103, the OD / path data acquisition unit 102 stores OD data (OD table) in the OD database 110 among the acquired OD / path data.
In step S104, the OD / route data acquisition unit 102 stores route distribution data (traffic volume distribution value for each route) in the route distribution database 111 among the acquired OD and route data.
In step S105, the OD / path data acquisition unit 102 stores the path information in the acquired OD / path data in the path information database 112, and the process ends.

  FIG. 4 is a view showing an example of the data structure of the OD database 110 constituting the OD traffic estimation device 1 shown in FIG. As shown in FIG. 4, the traffic volume for each OD is registered in the OD data 40. "ODID" which is an identifier for identifying OD, "occurrence zone (O)" which is a traffic occurrence zone, "concentration zone (D)" which is a traffic concentration zone, and each time zone for each ODID. The “traffic volume”, which is the traffic volume, is linked and stored. "ODID" is assigned a unique value in all OD data, and in the example shown in FIG. 4, OD1, OD2, OD3 ... ODm are assigned as "ODID", and "occurrence zone (O And the "concentrated sone (D)" are stored in association with each other as O1, O2, O3, D1, D2,. Therefore, each OD can be specified by the identifier "ODID". In addition, the time zone Tn shown in the "traffic volume" column is a predetermined time interval obtained by summing up the OD traffic volume such as T1 from 0:00 to 0:10, T2 from 0:10 to 0:20, for example It is shown as a band. The OD data 40 may be created on a day type such as a day of the week or a flat holiday, and in that case, an identifier for identifying the type of day is added to each OD data 40.

  For example, if “ODID” is “OD2”, “O1” for “Occurrence Zone (O)”, “D2” for “Concentrated Thorn (D)”, “200” for “Traffic Volume” for time zone “Tn” It is stored in association with it. In addition, when "ODID" is "OD3", "O2" in "Occurrence Zone (O)", "D1" in "Concentrated Thorn (D)", and "300" in "Traffic Volume" of time zone "Tn" It is stored in association with it.

FIG. 5 is a view showing an example of the data structure of the route distribution database 111 that constitutes the OD traffic estimation device 1 shown in FIG. As shown in FIG. 5, in the route distribution data 50 and the route distribution data 51, traffic volume distribution values of the route moving between each OD are registered. That is, "ODID" which is an identifier for identifying OD, "route ID" which is a route identifier, and "allocation value" which is a route distribution value for OD traffic in each predetermined time zone are linked to each ODID. Are stored. In the path allocation data 50, there are three paths that move between ODs of “ODID” and “OD3”, and “path IDs” that are path identifiers of those are “R21_1”, “R21_2”, and “R21_3,” respectively. " The “allocation value”, which is the route distribution value for the OD traffic volume in the predetermined time zone Tn, is “30” when “route ID” is “R21_1”, “180” when “route ID” is “R21_2”, “route When the ID is "R21_3", "90" is stored in association with one another. When the traffic volumes of the above three routes are summed up, the traffic volume "300" of "OD3" in the time zone Tn in the OD data 40 (FIG. 4) is obtained.
Similarly, in the route allocation data 51, there are two routes which move between ODs of "ODID" and "OD2", and "route ID" which is their route identifier is "R12_1" and "R12_2" respectively. . The “allocation value”, which is the route distribution value for the OD traffic volume in the predetermined time zone Tn, is “40” when the “route ID” is “R12_1”, and “160” when the “route ID” is “R12_2” Is stored. When the traffic volumes of these two routes are added, the traffic volume of “OD2” in the time zone Tn in the OD data 40 (FIG. 4) becomes “200”. In the present embodiment, although the case of using the distributed traffic volume as the traffic volume distribution value is shown as an example, the present invention is not limited to this. For example, instead of the distribution traffic volume, the distribution ratio to each movement route in each OD may be used as the traffic volume distribution value.
As described above, the OD database 110 and the path distribution database 111 constitute a relational database having “ODID”, which is an identifier for identifying an OD, as a node.

  FIG. 6 is a view showing an example of the data structure of the route information database 112 constituting the OD traffic estimation apparatus 1 shown in FIG. As shown in FIG. 6, in the route information 60, identifiers (link IDs) of a series of road sections (links) from the departure point to the destination point are registered. The “link ID” is associated with the road data stored in the map data database 115, and the road segment (road position) is identified by the “link ID”. The required time of the link (road section) in each time zone is registered and read from the traffic information database 114 when the route information is acquired, when the traffic information acquisition unit 104 acquires traffic information, or in a predetermined cycle set in advance. Be done. The route information 60 identifies, as shown in FIG. 6, a series of road sections (links) from the departure point of the route identified by the route identifier “route ID” and “route ID” to the destination point. For each "link ID" and "link ID", a "required time" indicating a required time in each time zone is stored in association.

For example, the route with “route ID” “R21_2” is a road link (road section) with “link ID” “1111”, “1112”, “1115”, “1120”, “1125” sequentially from the departure point The required time of each link is “30 seconds”, “60 seconds”, “150 seconds”, “300 seconds”, “190 seconds”, “20 seconds when time zone Tn + 1”, “time” when time zone Tn. “60 seconds”, “150 seconds”, “300 seconds”, “190 seconds”. Similarly, the route with “route ID” “R12_2” is composed of road links (road sections) with “link ID” “1211”, “1213”, “1120” and “1311” in order from the departure point The link required time is "100 seconds", "140 seconds", "300 seconds", "120 seconds" when the time zone is Tn, and "100 seconds", "150 seconds" when the time zone is Tn + 1, It is "300 seconds" and "120 seconds".
As described above, the route distribution database 111 and the route information database 112 constitute a relational database having "route ID" which is a route identifier as a node. Therefore, the OD database 110, the route distribution database 111, and the route information database 112 constitute a relational database having "ODID" as an identifier for identifying an OD and "route ID" as a route identifier as nodes. .

Next, processing of generating the required time of each link based on the acquired traffic information in the traffic information acquisition unit 104 will be described. FIG. 7 is a flow chart showing the processing flow of the traffic information acquisition unit 104 that constitutes the OD traffic estimation device 1 shown in FIG.
As shown in FIG. 7, in the map area S201, the traffic information acquisition unit 104 acquires traffic information of a predetermined area or route from the traffic information provision device 4 via the communication interface 101 and the communication network 5. The traffic information acquired here is traffic information such as the required time for each link and the traveling speed. In this embodiment, traffic information in a plurality of time zones from a predetermined past to a future (predictive information) is acquired without being limited to the current state. For the time zone of traffic information to be acquired, a method such as a method of specifying to the traffic information providing device 4 by the traffic information acquisition unit 104, a method of setting in advance as a rule for acquiring traffic information from the traffic information providing device 4, or the like is applied. . In addition, the traffic information acquired here includes a time zone corresponding to the observation time zone of the section traffic information acquired by the section traffic volume acquisition unit 103.

In step S202, the traffic information acquisition unit 104 stores the acquired traffic information in the traffic information database 114.
In step S203, the traffic information acquisition unit 104 uses the latest traffic information acquired, and based on the "path ID" for each OD identified by the "ODID" shown in FIG. The route information is read from the route information database 112 in order to execute processing for updating the required time in each time zone of each link of the route information 60.

In step S204, the traffic information acquisition unit 104 initializes the time zone n (time zone n = 1). Here, n is counted up until the update processing of all the number of time zones registered in the route information 60 is completed.
In step S205, the traffic information acquisition unit 104 initializes the number of routes k (number of routes k = 1). Here, k is counted up until the updating process of all the routes registered in the route information 60 is finished.
In step S206, the traffic information acquisition unit 104 initializes the number of links i (number of links i = 1). Here, i is counted up until the update process of the required time of all links of each route is finished.

In step S207, the traffic information acquisition unit 104 reads from the traffic information database 114 the required time of the link l (i) in the time zone Tn. Here, when traffic information can not be obtained from the traffic information database 114, the traffic information acquisition unit 104 reads the standard required time of the link l (i) from the map data database 115. Alternatively, the distance and speed (regulatory speed) of link l (i) are read from the map data database 115, and the required time is calculated.
In step S208, the traffic information acquisition unit 104 updates the required time of the link l (i) of the route k.

In step S209, the traffic information acquisition unit 104 updates the number of links i (i = i + 1). That is, the number of links i is incremented by one. Then, the traffic information acquiring unit 104 repeatedly executes the processing from step S207 to step S209 until the setting of the required time of all the links constituting the route k is completed.
Next, in step S210, the traffic information acquisition unit 104 updates the number k of routes (k = k + 1). That is, the number of paths k is incremented by one. Then, the traffic information acquisition unit 104 repeatedly executes the processing from step S206 to step S210 until the setting of the link required time of all the routes read in step S203 is completed.
Next, in step S211, the traffic information acquisition unit 104 updates the time zone n (n = n + 1). That is, the time zone n is incremented by one. And traffic information acquisition part 104 repeatedly performs processing from Step S205 to Step S211 until setting of link required time of all routes of all time zones read at Step S203 is completed.

Next, estimation processing of each OD traffic volume in the OD traffic volume estimation unit 105 will be described.
FIG. 8 is a flow chart showing the processing flow of the OD traffic volume estimation unit 105 that constitutes the OD traffic volume estimation device 1 shown in FIG.
As shown in FIG. 8, in step S301, the OD traffic estimation unit 105 acquires the predetermined time and interval obtained by the interval traffic acquisition unit 103 from the interval traffic providing device 2 via the communication network 5 and the communication interface 101. Section traffic volume is read from the section traffic volume database 113.

In step S302, the OD traffic estimation unit 105 initializes the number of sections j (number of sections j = 1). Here, j is counted up until the processing of the number of sections of all section traffic volumes read in step S301 is finished.
In step S303, the OD traffic volume estimation unit 105 acquires, from the route information database 112, route information passing through the section j and its OD.
In step S304, the OD traffic volume estimation unit 105 initializes the OD number n (OD number n = 1). Here, n is counted up until processing of the number of ODs passing through the section j acquired in step S303 is finished.

Next, in step S305, the OD traffic volume estimation unit 105 sets the route information of the OD (n) that passes through the section j acquired in step S303 as the route k (route k = k (OD (n)) ).
Next, in step S306, the OD traffic volume estimation unit 105 searches for a link corresponding to the section j from among the link strings constituting the route k, acquires the link number m in the route, and the number of links i Set m to and initialize i (link number i = m). For example, a route having “R21_2” as the “route ID” of the route information 60 stored in the route information database 112 shown in FIG. 6 is set as the route k. The "link ID" constituting the route of "R21_2" is a road link (road section) of "1111", "1112", "1115", "1120" and "1125" in order from the departure point. When the “link ID” corresponding to the section j is “1120”, the link number is the fourth from the departure link, so 4 is set to m.

Next, in step S307, the OD traffic estimation unit 105 uses the time zone in which the section traffic volume q (j) acquired in step S301 was observed as the entry time zone tin (l (i (i) of the link l (i)). Set to)).
In step S308, the OD traffic estimation unit 105 determines whether the link l (i) is a departure link of the route k. If it is determined that the link l (i) is a departure link of the route k (i = 1), the process proceeds to step S313. On the other hand, as a result of the determination, if the link l (i) is other than the departure link (if i ≠ 1), the process proceeds to step S309.

  In step S309, the OD traffic volume estimation unit 105 adds l (i) to the entry time slot tin (l (i-1)) of the link l (i-1) entering the link l (i) on the route k. The entry time zone tin (l (i)) is set (tin (l (i-1)) = tin (l (i)) For example, as described above, it is stored in the route information database 112 shown in FIG. Assuming that the route with the “route ID” of “R21_2” set as the route k of the route information 60 to be selected is the entry time zone of the “link ID” of “1120” be Tn, the “link ID” is “1120”. Tn is set in the entry time zone of the road link (road segment) whose “link ID” is “1115” which is the entry side of the road link (road segment).

  Next, in step S310, when the OD traffic estimation unit 105 enters the link l (i-1) in the time zone tin (l (i-1) set in step S309, the link l (i -1) Read the required time t (tin (l (i-1))). In the example of the route information 60 stored in the route information database 112 shown in FIG. 6, the road where the “link ID” is the entry side of the road link (road section) “1120” and the “link ID” is the road “1115” In the link (road section), the required time t (Tn) = 150 seconds is set for the “link ID” of “1115” when entering the time zone Tn.

In step S311, the OD traffic volume estimation unit 105 uses the required time t (tin (l (i-1)) of the link l (i-1) set in step S310 to link l (i-1). The entry time zone tin (l (i-1)) of is corrected by the following equation (1).
tin (l (i-1)) = tin (l (i))-t (tin (l (i-1))) (1)
In the example of the route information 60 stored in the route information database 112 shown in FIG. 6, the entry time zone tin (1120) of the road link (road section) where the “link ID” which is l (i) is “1120” = Tn, the required time t (Tn) = 150 seconds of the road link (road section) having the “link ID” of “1115” is stored. Therefore, the entrance time zone of the road link (road section) having the “link ID” of “1115” is corrected to tin (1115) = Tn−150 seconds.
Next, in step S312, the OD traffic volume estimation unit 105 updates the number of links i (i = i-1). That is, the number of links i is decremented by one. Then, the OD traffic volume estimation unit 105 repeatedly executes the processing from step S308 to step S312 until the entry time zone up to the departure link (departure road link) of the route k is obtained.

  On the other hand, if l (i) is determined to be the departure link (departure road link) in step S308, then in step S313, the OD traffic volume estimation unit 105 determines that l (i) 's approach time slot tin (l (i (i)). )) Is set to the generation time zone ts (k (OD (n))) of the OD (n) traffic volume passing through the section j. For example, in the case of the route information 60 stored in the route information database 112 shown in FIG. 6, the “route ID” passes through the road link with “link ID” “1120” (= section j) in the time zone Tn. Is the departure link (departure road link) of the route (= k) of “R21_2” The entry time tin (l (i)) of the road link (road section) with “link ID” of “1111” is OD3 It is the time of occurrence ts (k (OD3)) of the traffic volume. That is, since the “route ID” of the road link (road section) whose “link ID” is “1111” stored in the route information database 112 is “R21_2”, the OD traffic volume estimation unit 105 Specify that “ODID” corresponding to “R21_2” in the route allocation data 50 is “OD3” by referring to “111”, and the OD3 traffic volume occurrence time zone ts (k (OD3)) Set

  In step S314, the OD traffic volume estimation unit 105 reads the distribution value of the route k of the OD (n) traffic volume generated in the time zone ts (k (OD (n))) from the route distribution database 111, and the section j The traffic volume Q '(n) of OD (n) passing through is set. For example, in the route distribution data 50 stored in the route distribution database 111 shown in FIG. 5, the distribution value of the route k (= route R21_2) of the OD3 traffic volume in the occurrence time zone ts (k (OD3)) is the occurrence time zone It is assumed that it is the same value as the distribution value at Tn. In that case, since the distribution value of the “route ID” “R21_2” is 180, Q ′ (OD3) = 180 is set.

  Next, in step S315, the OD traffic volume estimation unit 105 updates the OD number n (n = n + 1). That is, the OD number n is incremented by one. Then, n is counted up until the processing is finished in all ODs related to the route passing through the section j. In the example of the route information 60 stored in the route information database 112 shown in FIG. 6, OD3 and “route ID” are other than “R21_2” as a route that passes through the section j (= link ID 1120) and its route. , OD2 and "route ID" are "R12_2". Therefore, based on the route distribution data 50 and the route distribution data 51 stored in the route distribution database 111 shown in FIG. 5 as the OD related to the route passing through the section j and the traffic volume when step S315 is finished, Two of Q '(OD3) = 180 and Q' (OD2) = 160 are set. Here, Q ′ (OD2) = 160 is the same value as the distribution value when the “route ID” of the OD2 traffic volume at the occurrence time ts (k (OD2)) is “R12_2” is the occurrence value at the occurrence time Tn. It is supposed to have been.

  In step S316, the OD traffic volume estimation unit 105 calculates q (j) as the OD traffic volume from the traffic volume Q ′ (n) of each OD and the traffic volume q (j) related to the route passing through the zone j. Allocate to For example, when q (j) = 170, q (j) is each OD traffic, q (j, OD3) = 90, q from the traffic volume ratio of Q ′ (OD3) and Q ′ (OD2). It is distributed to (j, OD2) = 80. Here, the ratio of traffic volume of Q '(OD3) and Q' (OD2) refers to the ratio of Q '(OD3) = 180: Q' (OD2) = 160.

  Next, in step S317, the OD traffic volume estimation unit 105 distributes the traffic volume of q (j) obtained in step S316 to each OD, and the route distribution data 50 and route distribution data stored in the route distribution database 111. Each OD traffic volume Q (n) is calculated from the route allocation value registered in 51. For example, when the time zone of the distribution values of the route distribution data 50 and the route distribution data 51 corresponding to the traffic volume distributed in step S316 is Tn, the generated traffic volume Q (OD3) of OD3 is the distribution of each route of OD3. From the ratio of values (30: 180: 90) and q (j, OD3) = 90 (= “Distributed traffic volume with“ route ID ”of“ R21_2 ””), the traffic volume of the route with “route ID” of “R21_1” is 15. The traffic volume of the route having “route ID” “R21_2” is 90, and the traffic volume of the route having “route ID” “R21_3” is 45. Therefore, Q (OD3) = 15 + 90 + 45 = 150. Similarly, the generated traffic volume Q (OD2) of OD2 is obtained from the ratio (40: 160) and q (j, OD2) = 80 of the distribution value of each route of OD2, and the route ID is "R12_1" The traffic volume is 20, and the traffic volume for the route with “route ID” “R12_2” is 80. Therefore, Q (OD2) = 20 + 80 = 100.

In step S318, the OD traffic volume estimation unit 105 updates the number of sections j (j = j + 1). That is, the section number j is incremented by one. Then, the OD traffic estimation unit 105 repeatedly executes the processing from step S305 to step S318 until OD traffic is obtained for all ODs related to the section traffic read in step S301.
Finally, in step S319, the OD traffic volume estimation unit 105 outputs all the OD traffic volumes calculated in the process up to step S318, and the process ends.

  In addition, in step S301 in the above-mentioned FIG. 8, since the case where all the section traffic volumes are read is taken as an example, the case where “the number of sections j” repeats the processing until the corresponding section number of all the section traffic volumes read is reached Although explained, it is not limited to this. For example, among the acquired section traffic volumes, only one section indicating the highest section traffic volume may be targeted, or only some sections, for example, a predetermined number of sections in descending order of section traffic volume The above-described process for estimating the OD traffic volume may be performed. Furthermore, the above-described OD traffic volume estimation process may be performed on a section where the change in section traffic volume per unit time is large. In addition, the above-described estimation process of the OD traffic volume may be performed on a desired number of sections selected by the user via the input / output unit 106 among the acquired section traffic volumes. Further, it is predicted that congestion will occur in the section indicating the section traffic volume increased from the average traffic volume of the section. Therefore, the above-described OD traffic volume estimation process may be performed on the section. In this way, it is possible to identify the generation zone of the section in which the congestion should be alleviated or the congestion should be eliminated, and it is also possible to reduce the processing load.

  Also, the section traffic volume is not limited to the observed section traffic volume, that is, the current section traffic volume, and may be a predicted section traffic volume. In this case, for example, the predicted section traffic volume may be obtained based on the statistical value using the past section traffic volume.

FIG. 9 is a diagram showing an example of the estimation result of the OD traffic volume output to the input / output unit 106 of the OD traffic volume estimation device 1 shown in FIG.
As shown in FIG. 9, lc is a section (link) of the section traffic volume whose OD traffic volume was estimated, and route R21_2 is a moving route from traffic occurrence zone O2 passing through lc to concentration zone D1. The route R12_2 is a moving route from the generation zone O1 of the traffic passing through lc to the concentration zone D2. The generated traffic volumes Q1 and Q2 and the time zones T1 and T2 of each OD are the OD traffic volume estimated by the OD traffic volume estimation unit 105 based on the observed traffic volume Qo in the time zone To in the section lc and the generation time thereof.

  By estimating the OD which is the generation source and the traffic volume from the observed traffic volume of the predetermined section lc, for example, the OD which is a factor of the congested section is identified, and the traffic demand generated from the identified OD It is possible to take measures such as toll regulation or display guidance prompting to change the route. Moreover, it becomes possible to take measures for traffic distribution in advance by handling the predicted traffic volume of a predetermined section instead of the observation traffic volume.

  In the present embodiment, a configuration for estimating the OD traffic volume was mainly described for a car moving on a road as an example, but other moving bodies moving on a predetermined network such as a railway or a bus are described. Can also be targeted.

  In addition, although each process has been described with each processing unit (for example, an OD traffic volume estimation unit or the like) as a "program" as an operation subject, the program determines the process defined by being executed by a processor, memory and communication port In order to carry out using (communication control apparatus), a processor may be an operation subject. Further, the processing having the program as an operation subject may be processing performed by various computers and the like. Some or all of the programs may be realized by dedicated hardware or may be modularized. Various programs may be installed on each computer by a program distribution server or storage medium. Also, it may be implemented in software that runs on a general-purpose computer, or may be implemented as dedicated hardware or a combination of software and hardware.

  Also, the above-described embodiment can be realized only by the program code of software. A storage medium storing the program code is mounted in a system or apparatus, and a computer (CPU or MPU) of the system or apparatus reads the program code stored in the storage medium. In this case, the program code itself read out from the storage medium implements the above-described embodiment, and the program code itself and the storage medium storing the same constitute the present invention. As a storage medium for supplying such a program code, for example, a flexible disk, a CD-ROM, a DVD-ROM, a hard disk, an optical disk, an optical magnetic disk, a CD-R, a magnetic tape, a non-volatile memory card, a ROM Etc. are used.

  In addition, even if an operating system (OS) operating on a computer performs part or all of the actual processing based on the instructions of the program code, and the above-described embodiment is realized by the processing. good. Furthermore, after the program code read from the storage medium is written into the memory on the computer, the CPU of the computer or the like executes a part or all of the actual processing based on the instruction of the program code, The above-described embodiment may be configured to be realized by the process.

  Furthermore, by distributing the program code of the software for realizing the above-mentioned embodiment through the network, it is stored in a storage device such as a hard disk or a memory of a system or device or a storage medium such as CD-RW or CD-R. The computer (or CPU or MPU) of the system or apparatus may read out and execute the program code stored in the storage device or the storage medium at the time of use.

  The present invention is not limited to the embodiments described above, but includes various modifications. For example, the embodiments described above are described in detail in order to explain the present invention in an easy-to-understand manner, and are not necessarily limited to those having all the configurations described.

DESCRIPTION OF SYMBOLS 1 ... OD traffic volume estimation apparatus 2 ... Section traffic volume provision apparatus 3 ... OD and route data provision apparatus 4 ... Traffic information provision apparatus 5 ... Communication network 6 ... Base station 7 ... Portable information terminal 8 ... In-vehicle information system 9 ... External device 10 ... OD traffic estimation system 20 ... computer 21 a ... CPU
21b ... ROM
21c ... RAM
Reference Signs List 22 Display 24 Operation unit 25 Storage 26 Memory bus 101 Communication interface 102 OD / route data acquisition unit 103 Section traffic acquisition unit 104 Traffic information acquisition unit 105 OD traffic estimation unit 106 Enter / Output unit 110 ... OD database 111 ... Route allocation database 112 ... Route information database 113 ... Section traffic volume database 114 ... Traffic information database 115 ... Map data database

Claims (10)

An OD traffic volume estimation apparatus for estimating traffic volume moving from a traffic generation zone (O) to a concentration zone (D),
An OD database that stores traffic between preset ODs in a discriminable manner for each OD;
A route allocation database that stores distribution values of traffic volume by route between ODs for each OD;
A route information database that stores at least identifiable links and required times as route information for each route;
A section traffic volume acquisition unit that acquires the observed traffic volume or predicted traffic volume of the predetermined section;
Identify the OD which is the source of the observed traffic volume or predicted traffic volume of the predetermined section and the route of the OD based on the observed traffic volume or predicted traffic volume of the predetermined section and route information including the predetermined section The distribution value of the traffic volume of the route specified from the route distribution database is read, and the observed traffic volume or predicted traffic volume of the predetermined section is distributed to the route of each OD, and between the ODs stored in the OD database An OD traffic volume estimation device comprising: an OD traffic volume estimation unit configured to estimate a traffic volume of an OD which is a generation source of the traffic volume of the predetermined section based on the traffic volume and the distribution value of the traffic volume. In the OD traffic estimation device according to claim 1,
The OD traffic volume estimation unit reads the required time of each link constituting the route of the OD and the OD as the generation source from the route information database, and based on the read required time of each link, the traffic of the predetermined section An OD traffic volume estimation device for estimating the traffic volume of each OD that is the generation source in a generation time zone of a volume. In the OD traffic estimation device according to claim 2,
A traffic information acquisition unit for acquiring traffic information including at least movement speed for each predetermined section;
The OD traffic volume estimation unit generates traffic volume of the predetermined section based on the required time of each link read from the route information database and the traveling speed for each predetermined section acquired by the traffic information acquisition section. An OD traffic volume estimation apparatus characterized by specifying an outbreak zone of each OD. In the OD traffic estimation device according to claim 3,
Equipped with input / output unit,
The input / output unit associates the traffic volume of each OD that is the generation source of the traffic volume of the predetermined section estimated by the OD traffic volume estimation unit with the position of each OD and the generation time zone to the section traffic volume OD traffic volume estimation device characterized by outputting. In the OD traffic estimation device according to claim 4,
It has a map data database that stores map data,
The input / output unit sets each OD on map data stored in the map data database as the traffic volume of each OD that is a generation source of the traffic volume of the predetermined section estimated by the OD traffic volume estimation unit. An OD traffic estimation device for displaying the position and the generation time zone of the and the section traffic volume. An OD traffic estimation device for estimating traffic moving from a traffic generation zone (O) to a concentration zone (D), a section traffic provision device for obtaining observed traffic or predicted traffic of a predetermined section, and at least The OD / route data provision device for obtaining traffic volume between ODs and distribution value of traffic volume by route between ODs and route information, and a communication network communicably connecting these to each other,
The OD traffic estimation device is
An OD database that stores the traffic between ODs obtained from the OD and route data providing device in a discriminable manner for each OD;
A route allocation database for storing, for each OD, an allocation value of traffic volume by route between ODs acquired from the OD / route data provision device;
A route information database that stores links and required times included in route information acquired from the OD and route data providing apparatus in a distinguishable manner for each route;
A section traffic volume acquisition unit for acquiring the observed traffic volume or the predicted traffic volume of a predetermined section from the section traffic volume provision device;
Identify the OD which is the source of the observed traffic volume or predicted traffic volume of the predetermined section and the route of the OD based on the observed traffic volume or predicted traffic volume of the predetermined section and route information including the predetermined section The distribution value of the traffic volume of the route specified from the route distribution database is read, and the observed traffic volume or predicted traffic volume of the predetermined section is distributed to the route of each OD, and between the ODs stored in the OD database An OD traffic volume estimation system comprising: an OD traffic volume estimation unit configured to estimate a traffic volume of an OD which is a generation source of the traffic volume of the predetermined section based on the traffic volume and the distribution value of the traffic volume. In the OD traffic estimation system according to claim 6,
The OD traffic volume estimation unit reads the required time of each link constituting the route of the OD and the OD as the generation source from the route information database, and based on the read required time of each link, the traffic of the predetermined section An OD traffic volume estimation system for estimating the traffic volume of each OD that is the generation source in a generation time zone of a volume. In the OD traffic estimation system according to claim 7,
The OD traffic estimation device includes a traffic information acquisition unit that acquires traffic information including at least a moving speed for each predetermined section,
The OD traffic volume estimation unit generates traffic volume of the predetermined section based on the required time of each link read from the route information database and the traveling speed for each predetermined section acquired by the traffic information acquisition section. An OD traffic volume estimation system characterized by specifying an outbreak zone of each OD. In the OD traffic estimation system according to claim 8,
The OD traffic estimation device comprises an input / output unit,
The input / output unit associates the traffic volume of each OD that is the generation source of the traffic volume of the predetermined section estimated by the OD traffic volume estimation unit with the position of each OD and the generation time zone to the section traffic volume OD traffic volume estimation system characterized by outputting. In the OD traffic estimation system according to claim 9,
The OD traffic estimation device comprises a map data database for storing map data,
The input / output unit sets each OD on map data stored in the map data database as the traffic volume of each OD that is a generation source of the traffic volume of the predetermined section estimated by the OD traffic volume estimation unit. An OD traffic estimation system characterized by displaying the position and the generation time zone of the and the section traffic volume.

Images