JP7365521B1 - Programs, methods and systems - Google Patents

Abstract

An object of the present invention is to provide a system that can acquire expressway usage history with a sufficient number of samples that can be used as significant information regarding traffic volume. [Solution] The program of the present invention includes a step of acquiring movement data indicating a movement route of a user carrying a mobile terminal to a processor of a computer, and shows the usage record of the expressway, and the point and passing time of the IC used. By comparing the usage details and movement data with the step of obtaining the ETC usage details, including the information about the vehicle and the model of the vehicle, the user's movement data corresponding to the travel log indicated by the usage details is obtained. and associating the vehicle identification information of the travel log with the user ID of the travel data, and the corresponding travel data is identified by referring to the combination of the travel log and the travel data for which the correspondence relationship has already been identified. A step of supplementing the corresponding user information with respect to the driving log that has not been recorded is executed. [Selection diagram] Figure 1

Description

TECHNICAL FIELD This disclosure relates to programs, methods, and systems.

Conventionally, in expressway management, it has been common practice to understand current traffic conditions, predict future traffic conditions, and consider maintenance plans that will be necessary for the future. At this time, web surveys of expressway users are regularly conducted to sample the usage status of expressways.
Further, Patent Document 1 listed below discloses a system that conducts a road traffic survey by photographing a traveling vehicle.

Japanese Patent Application Publication No. 2017-138861

However, in conventional traffic situation surveys, it is difficult to obtain a sufficient number of samples that can provide meaningful information on traffic volume.

SUMMARY OF THE INVENTION An object of the present invention is to provide a system that can acquire a sufficient number of samples of expressway usage history to provide significant information regarding traffic volume.

The program of the present invention is created by arranging location information of mobile terminals in a processor according to communication time, and includes a step of acquiring movement data indicating a travel route of a user carrying a mobile terminal, and a step of acquiring movement data indicating a movement route of a user carrying a mobile terminal; The usage details are obtained by comparing the usage details and movement data with the step of obtaining ETC usage details, including information about the IC location and passing time used, and information about the vehicle model. a step of identifying the user's movement data corresponding to the shown driving log, linking the vehicle identification information of the driving log and the user ID of the movement data, and combining the driving log and movement data for which the correspondence relationship has already been identified. A step of referencing and supplementing the corresponding user information with respect to a travel log for which corresponding movement data is not specified is executed.

According to the present invention, it is possible to obtain a sufficient number of samples of expressway usage history that can provide significant information regarding traffic volume.

FIG. 1 is a diagram showing an overview of a human flow analysis system according to the present embodiment. FIG. 2 is a block diagram showing the hardware configuration of the user terminal shown in FIG. 1. FIG. FIG. 2 is a block diagram showing the hardware configuration of the administrator terminal shown in FIG. 1. FIG. FIG. 2 is a block diagram showing the hardware configuration of the server shown in FIG. 1. FIG. 5 is a block diagram showing the functional configuration of the server shown in FIG. 4. FIG. FIG. 2 is a diagram showing a database managed when using a user terminal. FIG. 2 is a diagram showing a database managed as a user's movement history. It is a figure showing the structure of trip data in this embodiment. FIG. 2 is a diagram showing a database managed in the use of expressways. FIG. 3 is a diagram showing a database managed as a result of matching processing. FIG. 2 is a diagram illustrating an overview of the present embodiment. It is a flow showing the entire process of this embodiment. This is a flowchart showing details of a process for specifying movement information corresponding to a travel log. This is a flowchart showing details of user information complementation processing. It is a figure explaining other functions of a people flow analysis system. It is a figure showing an example of an OD table.

Hereinafter, one embodiment of the present invention will be described in detail based on the drawings. In addition, in the drawings for explaining the embodiments, the same components are generally designated by the same reference numerals, and repeated explanations thereof will be omitted.

(1) Overview of System 1 An overview of a people flow analysis system 1 (hereinafter simply referred to as system 1) according to an embodiment of the present invention will be described. FIG. 1 is a conceptual diagram showing an overview of a system 1 of this embodiment.
As shown in Figure 1, the system 1 responds to operational instructions from the administrator by providing ETC usage details (hereinafter referred to simply as usage details in this paper) indicating expressway usage records and the user's mobile phone information. This is a system that provides information that contributes to analysis of expressway usage records by comparing and matching movement data obtained from communication logs of mobile phones (user terminals 10). Here, the movement data is information indicating a user's movement route (transition of positional information), which is specified by changes in the positional information of a mobile phone over time, and is subdivided as follows depending on the means of movement.
・Expressway movement data ・General road movement data ・Air movement data ・Walking movement data

Specifically, the system 1 matches travel logs that indicate the history of expressway travel routes included in the usage details with travel data that shows the history of the user's travel route. The vehicle identification information is linked to the user ID of the user who is the moving subject identified from the movement data.
Here, in this embodiment, the vehicle identification information is an onboard device ID of an ETC onboard device mounted on a traveling vehicle. Further, the user ID refers to user identification information set when using a mobile phone.

By identifying the user ID and the vehicle used by the user, the system 1 aggregates expressway usage records and collects movement data when using general roads through processing described later. By linking vehicle identification information to general road movement data, a wide variety of traffic conditions can be analyzed. The configuration of such system 1 will be explained.

(2) Overall configuration of system 1 As shown in FIG. 1, system 1 includes a user terminal 10, an administrator terminal 20, and an information processing server 30 (hereinafter simply referred to as server 30).
The user terminal 10, the administrator terminal 20, and the server 30 are connected via a network (eg, the Internet or an intranet) 80.
The user terminal 10, the administrator terminal 20, and the server 30 are connected to a base station database 40 and a transportation network database 50 via a network 80.

The user terminal 10 is an information processing device such as a mobile phone carried by a user. The user terminal 10 is configured to perform mobile communication with a base station (fixed positioning device 81). The user terminal 10 is a communication device that is carried by a user and moves, and can also be referred to as a mobile terminal. In addition to mobile phones, such mobile terminals include WiFi beacons carried and used by users, mobile antennas used for radar positioning, in-vehicle car navigation terminals compatible with ITS spot (DSRC), and Bluetooth (registered) This includes communication terminals, etc. that use trademarks. Note that the mobile terminal may be any other device that communicates while moving.

The fixed positioning device 81 refers to a device that is fixed at a fixed location and communicates with a communication device, and includes, for example, a positioning device that communicates with a mobile phone base station, a wifi beacon, in addition to a mobile phone base station, This includes positioning equipment that performs radar positioning, positioning equipment for ITSspot, etc. Note that the fixed positioning device 81 may be any other device as long as it is fixed at a fixed position and communicates with a communication device.

The user terminal 10 may include various computers, such as a smartphone, a tablet terminal, a wearable device (for example, a smart watch or smart glasses), as a device that performs mobile communication with the fixed positioning device 81. In this embodiment, the user terminal 10 will be described using as an example a smartphone that performs mobile communication with a fixed positioning device 81 that is provided with an antenna used for mobile communication of a mobile phone.

The administrator terminal 20 is an information processing device used by the administrator of the system 1. The administrator terminal 20 is a terminal on which an administrator who analyzes movement data accumulated in the base station database 40 and ETC usage details indicating expressway usage records issues instructions necessary for matching processing. . Administrator terminal 20 may include various computers such as a personal computer, a server computer (eg, a web server, an application server, a database server, or a combination thereof). In this embodiment, the administrator terminal 20 will be explained using a personal computer used by an administrator as an example.

The server 30 is an information processing device that performs various processes to be described later on input information. The server 30 mainly executes a process of matching the location information of the user terminal 10 with expressway usage details.
Server 30 may include a variety of computers, such as a personal computer, a server computer (eg, a web server, an application server, a database server, or a combination thereof). In this embodiment, the server 30 will be explained using a server computer as an example.

The base station database 40 is a database in which a plurality of user terminals 10 accumulate a huge amount of position information obtained through mobile communication with the fixed positioning device 81. The base station database 40 stores user terminal information and location information at communication times as communication logs.

When the user terminal 10 is located in a communication area where the fixed positioning device 81 can communicate, the fixed positioning device 81 stores position information estimated from radio waves received from the user terminal 10 in the base station database 40 along with time information. The base station database 40 is a database operated by a mobile phone carrier, and stores location information acquired by the fixed positioning device 81 together with time information as a communication log for each terminal in use.

The transportation network database 50 is a database that stores information on transportation means such as railways, expressways, and air routes. The transportation network database 50 stores the following information as transportation means information.
・Facility name, facility number, location, and applicable means of transportation for each transportation hub ・Route name, road name, and air route name connecting each transportation hub ・Location information of transportation links connecting each transportation hub (including the location of roads and railroads) )
Here, transportation hubs include various transportation facilities such as airports, stations, express buses, and expressway interchanges (hereinafter referred to as ICs) that serve as transit points (transit nodes) when using each means of transportation. .

(1-1) Configuration of user terminal 10 The configuration of the user terminal 10 will be explained. FIG. 2 is a block diagram showing the configuration of the user terminal 10 of this embodiment.

As shown in FIG. 2, the user terminal 10 includes a storage device 11, a processor 12, an input/output interface 13, and a communication interface 14. User terminal 10 is connectable to at least one of input device 15 and output device 16 .

Storage device 11 is configured to store programs and data. The storage device 11 is, for example, a combination of ROM (Read Only Memory), RAM (Random Access Memory), and storage (for example, flash memory or hard disk).

The programs include, for example, the following programs.
・OS (Operating System) program ・Application program that executes information processing (e.g. web browser)

The data includes, for example, the following data.
・Databases referenced in information processing ・Data obtained by executing information processing (that is, execution results of information processing)

The processor 12 is configured to implement the functions of the user terminal 10 by activating a program stored in the storage device 11. Processor 12 is an example of a computer.

The input/output interface 13 obtains a signal (e.g., a user's instruction, a sensing signal, or a combination thereof) from the input device 15 and sends a signal (e.g., an image signal, an audio signal, or a combination thereof) to the output device 16. ) is configured to output.

The input device 15 is, for example, a keyboard, a pointing device, a touch panel, a physical button, a sensor (eg, a camera, a vital sensor, or a combination thereof), or a combination thereof.

Output device 16 is, for example, a display, a speaker, a printing device, or a combination thereof.

Communication interface 14 is configured to control communication between user terminal 10 and external devices.

(1-2) Configuration of administrator terminal 20 The configuration of administrator terminal 20 will be explained. FIG. 3 is a block diagram showing the configuration of the administrator terminal 20 of this embodiment.

As shown in FIG. 3, the administrator terminal 20 includes a storage device 21, a processor 22, an input/output interface 23, and a communication interface 24. The administrator terminal 20 is connectable to at least one of an input device 25 and an output device 26.

Storage device 21 is configured to store programs and data. The storage device 21 is, for example, a combination of ROM (Read Only Memory), RAM (Random Access Memory), and storage (for example, flash memory or hard disk).

The programs include, for example, the following programs.
・OS (Operating System) program ・Application program that executes information processing (e.g. web browser)

The data includes, for example, the following data.
・Databases referenced in information processing ・Data obtained by executing information processing (that is, execution results of information processing)

The processor 22 is configured to implement the functions of the administrator terminal 20 by activating a program stored in the storage device 21. Processor 22 is an example of a computer.

The input/output interface 23 obtains a signal (e.g., a user's instruction, a sensing signal, or a combination thereof) from the input device 25 and sends a signal (e.g., an image signal, an audio signal, or a combination thereof) to the output device 26. ) is configured to output.

The input device 25 is, for example, a keyboard, a pointing device, a touch panel, a physical button, a sensor (eg, a camera, a vital sensor, or a combination thereof), or a combination thereof.

Output device 26 is, for example, a display, a speaker, a printing device, or a combination thereof.

Communication interface 24 is configured to control communication between administrator terminal 20 and external devices.

(1-3) Hardware configuration of server 30 The configuration of server 30 will be explained. FIG. 4 is a block diagram showing the configuration of the server 30 of this embodiment.
As shown in FIG. 4, the server 30 includes a storage device 31, a processor 32, and a communication interface 34.

Storage device 31 is configured to store programs and data. The storage device 31 is, for example, a combination of ROM, RAM, and storage (eg, flash memory or hard disk).

The programs include, for example, the following programs.
・OS program ・Application program that executes information processing

The data includes, for example, the following data.
・Databases referenced in information processing ・Execution results of information processing

The processor 32 is configured to implement the functions of the server 30 by activating a program stored in the storage device 31. Processor 32 is an example of a computer.

Communication interface 34 is configured to control communication between server 30 and external devices.

(1-4) Functional configuration of server 30 Next, the functional configuration of server 30 will be described. FIG. 5 is a block diagram showing the functional configuration of the server 30.
As shown in FIG. 5, the server 30 functions as a communication section 301, a storage section 302, and a control section 303.

(1-4-1) Functions of communication unit 301 and storage unit 302 The communication unit 301 performs processing for the server 30 to communicate with external devices.

Storage unit 302 stores data and programs used by server 30. The storage unit 302 stores, for example, the following data.
・User database (user DB)
・Terminal database (terminal DB)
・Communication log database (communication log DB)
・People flow node database (people flow node DB)
・People flow link database (people flow link DB)
・Trip group database (trip group DB)
・Trip database (Trip DB)
・Usage details database (Usage details DB)
・Onboard equipment database (onboard equipment DB)
・Tollgate database (tollgate DB)
・Driving log database (driving log DB)
・Movement candidate database (movement candidate DB)
・Judgment result database (judgment result DB)
・Completion result database (completion result DB)

The user DB is a database that stores information regarding users who use the user terminal 10. Details of the user DB will be described later.

The terminal DB is a database that stores information regarding the user terminal 10. Details of the terminal DB will be described later.

The people flow node DB is a database that stores information on nodes corresponding to the location information specified by the communication log, out of the movement data obtained from the location information of the user terminal 10. Details of the people flow node DB will be described later.

The human flow link DB is a database that stores information regarding routes (links) between nodes among movement data obtained from the position information of the user terminal 10. Details of the people flow link DB will be described later.

The trip group DB is a database that stores information about a grouping of nodes and links (trip groups) for each trip mode, which is information indicating the means of transportation, among movement data obtained from the location information of the user terminal 10. be. Details of the trip group DB will be described later.

The trip DB is a database that stores information related to trip data indicating a travel route for each series of travel actions from a starting point to an ending point of a specific user, out of travel data obtained from the location information of the user terminal 10. Details of the trip DB will be described later. Note that trip data is a collection of travel data for each series of travel actions from the start point to the end point, so a plurality of trip data may exist in one day.

The usage details DB is a database that stores information related to ETC usage details indicating expressway usage records. Details of the user DB will be described later.

The onboard device DB is a database that stores information regarding onboard devices installed in vehicles that use expressways. Details of the onboard equipment DB will be described later.

The tollgate DB is a database that stores information regarding tollgates on expressways. Details of the toll gate DB will be described later.

The travel log DB is a database that stores information regarding travel logs of vehicles using expressways. Details of the driving section DB will be described later.

The movement candidate DB is a database that stores information regarding movement candidate data. Movement candidate data is data that is a candidate for movement data corresponding to a vehicle travel log, among a plurality of movement data that constitute trip data. Details of the migration candidate DB will be described later.

The determination result DB is a database that stores the determination results of matching between expressway travel logs and movement data. Details of the determination result DB will be described later.

The complementation result DB is a database that stores the complementation results of user information corresponding to expressway travel logs. Details of the complementary result DB will be described later.

(1-4-2) Functions of the control unit 303 The control unit 303 shown in FIG. It functions as a module 3034, a specific module 3035, an estimation module 3036, a creation module 3037, and an output module 3038.

<Functions of transmission/reception control module 3031>
The transmission/reception control module 3031 controls processing in which the server 30 transmits and receives signals from an external device according to a communication protocol.

<Functions of acquisition module 3032>
The acquisition module 3032 acquires a communication log from the external base station database 40 and records a new record in the communication log DB of the storage unit 302.
The acquisition module 3032 also acquires the ETC usage details and records them as a new record in the usage details DB in the storage unit 302. The usage details include information regarding the entrance and exit points and passing time of the IC used, and information regarding the model of the vehicle.

<Functions of generation module 3033>
The generation module 3033 processes communication logs included in the communication log DB to generate data to be stored in each of the following DBs.
・People flow node DB
・People flow link DB
・Trip group DB
・Trip DB
Details of these will be described later together with the structure of each DB.

<Functions of sorting module 3034>
The sorting module 3034 selects a plurality of movement candidate data, which are movement data candidates corresponding to the vehicle travel log, from among the plurality of movement data, based on the degree of coincidence of the passage times of passing nodes in each of the usage details and movement data. . Details of this processing will be described later.

<Functions of specific module 3035>
The identification module 3035 identifies the user's movement data corresponding to the travel log by comparing the usage details and the movement data. At this time, the identification module 3035 compares the group of movement candidate data selected by the selection module with the travel logs indicated by the multiple usage details of one or more vehicles, so that the travel logs indicated by the specific usage details are The corresponding movement data is identified and the vehicle identification information in the travel log and the user ID of the movement data are linked. Details of this processing will be described later.
In addition, the identification module 3035 refers to the combinations of travel logs and travel data for which the correspondence relationship has already been identified, and supplements the travel logs for which corresponding travel data has not been identified with the corresponding user information. Connect. Details of this processing will be described later.

<Functions of estimation module 3036>
The estimation module 3036 estimates the vehicle used in the trip data when the user traveled on a general road, based on the correspondence between the onboard device ID, which is the vehicle identification information obtained through the matching process, and the user information. . Details of this processing will be described later.

<Functions of creation module 3037>
The creation module 3037 creates and outputs an OD table (Origin-Destination Table Matrix) for each vehicle type using vehicle identification information and user information that are associated with each other. An OD table is a statistical method for investigating road usage, and in order to investigate the flow of vehicles, it is used to calculate the amount of vehicles moving from an origin to a destination. This is data that shows in tabular form whether the Details of the OD table and its creation method will be described later.

<Functions of output module 3038>
The output module 3038 outputs the results of processing performed by other modules to the administrator terminal 20.

(2) Database Structure Next, an example of the structure of each database stored in the storage unit 302 will be described.

(2-1) DB managed when using user terminal 10
First, the following DBs that are managed when using the user terminal 10 shown in FIG. 6 will be explained.
・User DB
・Terminal DB
・Communication log DB

(2-1-1) User DB
FIG. 6A is a diagram showing a specific example of a user DB.
As shown in FIG. 6A, the user DB includes the item "user ID", the item "name", the item "age", the item "gender", the item "place of residence", the item "occupation", and the item It has "contract contents".

The item "user ID" stores identification information that can identify the user who uses the user terminal 10.

The item "Name" stores information regarding the name of the user corresponding to the user ID.

The item "age" stores information regarding the age of the user corresponding to the user ID.

The item “gender” stores information regarding the gender of the user corresponding to the user ID.

The item "place of residence" stores information regarding the place of residence of the user corresponding to the user ID.

The item "occupation" stores information regarding the occupation of the user corresponding to the user ID.

The item "contract details" stores information regarding the details of a usage contract concluded regarding the use of the user terminal 10 by the user corresponding to the user ID. For example, the contract contents may include a contract ID that can identify the contract.
Note that these configurations are just examples, and the user DB may include other columns.

(2-1-2) Terminal DB
FIG. 6B is a diagram showing a specific example of the terminal DB.
As shown in FIG. 6B, the terminal DB includes the item "terminal ID", the item "user ID", and the item "contract ID".

The item “terminal ID” stores identification information of a terminal that can identify the user terminal 10.

The item "user ID" stores identification information of a user who uses the travel log corresponding to the travel log ID.

The item "contract ID" stores the identification number of the usage contract concluded regarding the use of the travel log corresponding to the travel log ID.
Note that these configurations are just examples, and the terminal DB may include other columns.

(2-1-3) Communication log DB
FIG. 6C is a diagram showing a specific example of the communication log DB.
As shown in FIG. 6C, the communication log DB includes an item "communication log ID", an item "terminal ID", an item "position coordinates", and an item "communication time".

The item “communication log ID” stores identification information of a communication log that can identify communication of the user terminal 10.

The item "terminal ID" stores the terminal ID of the user terminal 10 that performed the communication corresponding to the communication log ID.

The item "location coordinates" stores the location coordinates of the user terminal 10 acquired in the communication corresponding to the communication log ID.

The item "communication time" stores time information when the communication corresponding to the communication log ID was performed.
Note that these configurations are just examples, and the communication log DB may include other columns.

(2-2) DB managed as user movement history
Next, the following DB that is managed as the user's movement history (movement data) shown in FIG. 7 will be explained.
・Trip DB
・Trip group DB
・People flow node DB
・People flow link DB

(2-2-1) Trip DB
FIG. 7A is a diagram showing a specific example of the trip DB.
As shown in FIG. 7A, the trip DB includes an item "trip ID", an item "terminal ID", and an item "action date".

The item "Trip ID" stores identification information of trip data that can identify the user terminal 10 of the trip data that can identify the trip data.

The item "terminal ID" stores the terminal ID of the user terminal 10 from which the trip data corresponding to the trip ID was acquired.

The item "activity date" stores information indicating the date on which the user moved, which is indicated by the trip data corresponding to the trip ID.
Note that these configurations are just examples, and the trip DB may include other columns.

(2-2-2) Trip group DB
FIG. 7B is a diagram showing a specific example of the trip group DB.
As shown in FIG. 7B, the trip group DB includes an item "trip group ID" and an item "trip ID."

The item "trip group ID" stores identification information of a trip group that can identify the trip group.

The item "Trip ID" stores identification information of trip data to which the trip group corresponding to the trip group ID belongs.
Note that these configurations are just examples, and the trip group DB may include other columns.

(2-2-3) People flow node DB
FIG. 7C is a diagram showing a specific example of the people flow node DB.
As shown in FIG. 7C, the people flow node DB includes an item "people flow node ID", an item "communication log ID", an item "trip group ID", and an item "reference time".

The item "people flow node ID" stores identification information of a people flow node that can identify the people flow node.

The item "communication log ID" stores identification information of the communication log to which the people flow node corresponding to the people flow node ID corresponds. The communication log to which the human flow node corresponds refers to the communication log in which the human flow node is recorded as position information.

The item "trip group ID" stores identification information of the trip group to which the people flow node corresponding to the people flow node ID belongs.

The item “reference time” stores time information that serves as a time-series reference for the people flow node corresponding to the people flow node ID. The reference time of the people flow node corresponds to the communication time of the communication log from which the person flow node was acquired as location information.
Note that these configurations are just examples, and the people flow node DB may include other columns.

(2-2-4) People flow link DB
FIG. 7D is a diagram showing a specific example of the people flow link DB.
As shown in FIG. 7D, the terminal DB includes the item "people flow link ID", the item "start point node ID", the item "end point node ID", the item "trip mode ID", the item "trip group ID", The item "Reference time ID" is provided.

The item "people flow link ID" stores identification information of a people flow link that can identify the people flow link.

The item “starting point node ID” stores the people flow node ID of the people flow node (starting point node) that is the start point of the people flow link corresponding to the people flow link ID.

The item "end point node ID" stores the people flow node ID of the people flow node (end point node) that is the end point of the people flow link corresponding to the people flow link ID.

The item "trip mode" stores information indicating the means of transportation in the people flow link corresponding to the people flow link ID.

The item “trip group ID” stores identification information of a trip group that includes the people flow link corresponding to the people flow link ID.

The item “reference time” stores time information that serves as a time-series reference for the people flow link corresponding to the people flow link ID. The reference time of the people flow link corresponds to the communication time of the communication log from which the position information of at least one of the start point node and the end point node of the person flow link is acquired. For example, the communication times corresponding to the position information of both the start point node and the end point node may be managed as the first reference time and the second reference time, respectively, or only the communication times corresponding to the position information of the start point node may be managed as the reference time. It may be managed as
Note that these configurations are just examples, and the people flow node DB may include other columns.

Next, the structure of trip data (<people flow data) defined using four DBs that are managed as such user movement history will be explained. FIG. 8 is a diagram showing the structure of trip data.
As shown in FIG. 8, in the movement data including the starting point node n1 to the ending point node n21, a people flow link is defined between each node. The human flow link is linked by determining the trip mode (transportation means) based on the travel distance and travel time. In the illustrated example, the plurality of people flow links arranged in chronological order are classified into five trip groups depending on the trip mode. In this case, the trip data includes five trip groups, and the trip mode in each trip group is determined. In this embodiment, this trip group is treated as a unit of movement data corresponding to a travel log. Specifically, Group B and Group D are the expressway travel data to be compared with the travel log.

(2-3) DB managed for expressway use
Next, the following DB that is managed as expressway usage records shown in FIG. 9 will be explained.
・Usage details DB
・Onboard equipment DB
・Tollgate DB
・Driving log DB

(2-3-1) Usage details DB
FIG. 9A is a diagram showing a specific example of the usage details DB.
As shown in FIG. 9A, the usage details DB includes the item "Usage details ID", the item "Used onboard device ID", the item "Used interface/toll plaza ID", and the item "Usage date and time". There is.

The item “usage details ID” stores identification information of usage details that can identify the usage details.

The item "Used onboard device ID" stores identification information of the ETC onboard device installed in the vehicle that used the expressway corresponding to the usage details ID.

The item "Used Inter/Toll Gate ID" stores the identification number of the IC or toll gate where the expressway corresponding to the usage details ID was used.

The item "date and time of use" stores information regarding the date and time when the expressway corresponding to the usage details ID was used.
Note that these configurations are just examples, and the usage details DB may include other columns.

(2-3-2) Onboard equipment DB
FIG. 9B is a diagram showing a specific example of the onboard equipment DB.
As shown in FIG. 9B, the onboard device DB includes an item "onboard device ID" and an item "vehicle type."

The item "onboard device ID" stores identification information of the onboard device that can identify the ETC onboard device installed in the vehicle.

The item “vehicle type” stores information indicating the type of vehicle in which the on-vehicle device corresponding to the on-vehicle device ID is mounted.
Note that these configurations are merely examples, and the onboard device DB may include other columns.

(2-3-3) Tollgate DB
FIG. 9C is a diagram showing a specific example of the tollgate DB.
As shown in FIG. 9C, the toll plaza DB includes the item "IC/toll plaza ID", the item "facility name", the item "location", and the item "location coordinates".

The item "IC/tollgate ID" stores identification information that can identify an expressway IC or tollgate.

The item "facility name" stores the facility name of the IC or tollgate corresponding to the IC/tollgate ID.

The item "location" stores information regarding the location of the IC or toll gate corresponding to the IC/toll gate ID, for example, in the form of a lot number.

The item "location coordinates" stores latitude and longitude information indicating the location coordinates of the IC or tollgate corresponding to the IC/tollgate ID.
Note that these configurations are just examples, and the IC/toll gate DB may include other columns.

(2-3-4) Travel log DB
FIG. 9D is a diagram showing a specific example of the travel log DB.
As shown in FIG. 9D, the driving log DB includes the item "driving log ID", the item "onboard device ID", the item "approach facility ID", the item "approach date and time", and the item "passing facility ID". , the item "passing date and time", the item "leaving facility ID", and the item "leaving date and time".

The item "driving log ID" stores identification information of a driving log that can identify a driving log on an expressway.

The item "onboard device ID" stores identification information of the onboard device installed in the vehicle that used the expressway corresponding to the travel log ID.

The item "Enter facility ID" stores identification information of the IC or toll gate where the vehicle entered the expressway when using the expressway corresponding to the travel log ID.

The item "date and time of entry" stores information indicating the date and time when the vehicle entered the expressway when using the expressway corresponding to the travel log ID.

The item "Passed Facility ID" stores identification information of an IC or toll gate passed during the travel section when using the expressway corresponding to the travel log ID. Note that the passing facility ID is recorded only when the vehicle passes through a facility (transfer point) such as a toll gate that is the boundary of the expressway's governing company. This information is used to change the fare system for the sections before and after the transfer point.

The item "passing date and time" stores information indicating the date and time when the vehicle passed through the IC or tollgate corresponding to the passing facility ID while using the expressway corresponding to the travel log ID.

The item "exit facility ID" stores identification information of the IC or toll gate from which the vehicle exited the expressway when using the expressway corresponding to the travel log ID.

The item "exit date and time" stores information indicating the date and time when the vehicle exited the IC or tollgate when using the expressway corresponding to the travel log ID.
Note that these configurations are just examples, and the travel log DB may include other columns.

(2-4) DB managed as a result of matching processing
Next, the following DBs that are managed as a result of the matching process shown in FIG. 10 will be explained.
・Movement candidate DB
・Judgment result DB
・Completion result DB

(2-4-1) Movement candidate DB
FIG. 10A is a diagram illustrating a specific example of a movement candidate DB.
As shown in FIG. 10A, the movement candidate DB includes an item "movement candidate ID", an item "driving log ID", and an item "trip group ID".

The item “movement candidate ID” stores identification information of movement candidate data that can identify movement candidate data.

The item "driving log ID" stores identification information of the traveling log to be evaluated in the movement candidate data corresponding to the movement candidate ID.

The item "trip group ID" stores identification information of a trip group estimated as a candidate for travel data corresponding to the corresponding travel log, as travel candidate data corresponding to the travel candidate ID.
Note that these configurations are just examples, and the migration candidate DB may include other columns.

(2-4-2) Judgment result DB
FIG. 10B is a diagram showing a specific example of the determination result DB.
As shown in FIG. 10B, the determination result DB includes an item "determination result ID", an item "onboard device ID", and an item "user ID".

The item "determination result ID" stores identification information of the determination result that can specify the determination result of the matching process between the driving log and the movement data.

The item "onboard device ID" stores identification information of the onboard device that recorded the driving log that was evaluated in the determination corresponding to the determination result ID.

The item "user ID" stores identification information of the user terminal 10 that is linked to the onboard device ID in the determination corresponding to the determination result ID.
Note that these configurations are just examples, and the determination result ID may include other columns.

(2-4-3) Completion result DB
FIG. 10C is a diagram showing a specific example of the complementation result DB.
As shown in FIG. 10C, the complementation result DB includes an item "complementation result ID", an item "driving log ID", and an item "user ID".

The item "complementation result ID" stores identification information of the completion result that can identify the result of the user information complementation process for the driving log.

The item “driving log” stores identification information of a driving log that is an evaluation target in the complementation process corresponding to the complementation result ID.

The item "user ID" stores the user ID that is linked to the corresponding travel log in the complementation process corresponding to the complementation result ID.
Note that these configurations are just examples, and the complementary result ID may include other columns.

(3) Overview of the embodiment An overview of the present embodiment will be explained.
In response to an operation instruction from the administrator, the system 1 compares the user movement data generated from the communication log of the user terminal 10 and the vehicle travel log obtained from the expressway usage details. By specifying the movement data corresponding to the driving log, matching processing between the movement data and the driving log is performed. This process will be explained using a specific example.

FIG. 11 is a diagram illustrating an overview of this embodiment.
As shown in FIG. 11, the people flow data generated from the communication log of the user terminal 10 shows a series of movement routes starting from the people flow node 1 and ending at the people flow node 18. This series of travel routes is called user trip data. The trip data includes a plurality of people flow links, which are represented by broken lines in the illustrated example.

This trip data includes the following trip groups.
・Group X corresponding to people flow node 1 to people flow node 3 (general road movement data)
・Group Y corresponding to people flow node 3 to people flow node 15 (expressway movement data)
・Group Z corresponding to people flow node 15 to people flow node 18 (general road movement data)
Details regarding each of these movement data are managed by four DBs shown in FIG. 8.

On the other hand, the system 1 generates a travel log indicating passing nodes indicated by white rectangles on the map of FIG. 11 based on the usage details of the expressway.
Specifically, the travel log includes information on usage details 1 recorded when passing through an IC that served as an entrance, and information on usage details 2 recorded when passing through an IC that served as an exit. generated using Furthermore, if there is a transit point, the information in the usage details 3 recorded when passing through the transit facility is also used. By specifying a plurality of passing nodes from the usage details, the route shown by the dashed line in FIG. 11 can be estimated as the travel route of the vehicle.

Next, the system 1 performs a process of matching the travel log R with corresponding movement data in response to an operation instruction from the administrator. Although not shown in the diagram, in reality, from a huge amount of movement data detected on the evaluation date and a huge amount of usage details recorded on the same day, the position and time of each passing node are matched. Based on the degree, the system 1 estimates movement data corresponding to the travel log.

In the illustrated example, it is estimated that there is a high probability that the trip group Y and the travel log match from the following viewpoints.
・The position of the people flow node 3 and the position of the IC where the usage details 1 are recorded are close.・The reference time of the people flow node 3 and the passing time of the IC where the usage details 1 are recorded are close.・The people flow The position of the node 15 and the position of the IC where the usage details 2 are recorded are close.The reference time of the people flow node 3 and the passing time of the IC where the usage details 1 are recorded are close.

System 1 selects a movement with a high probability corresponding to the travel log to be evaluated based on the degree of coincidence between the passing nodes and the passing time included in each from a huge amount of travel data and travel logs. A plurality of pieces of data are selected as movement candidate data.

The system 1 selects the movement data with the highest probability from the selected movement candidate data, and specifies it as movement data corresponding to the travel log to be evaluated. Then, the system 1 associates the onboard device corresponding to the travel log with the user ID of the user terminal 10 corresponding to the movement data. Thereby, the vehicle type linked to the on-vehicle device ID and the user ID are associated with each other. The processing of the system 1 will be described in detail below.

(4) Processing of System 1 Next, processing of System 1 will be explained.

(4-1) Overall processing of system 1 FIG. 12 is a flowchart showing the overall processing of system 1.
As shown in FIG. 12, the system 1 first obtains a communication log (step S30). Specifically, the acquisition module 3032 of the server 30 acquires communication logs stored in the base station database 40. The acquisition module 3032 stores the acquired communication log in the communication log DB.

After step S30, the system 1 acquires trip data by processing the acquired communication log (step S31).
Specifically, the generation module 3033 of the server 30 first sets a new trip data identification number for each user terminal and travel date, and records it as a new record in the trip DB.

Next, the generation module 3033 defines people flow nodes in the movement route of the user terminal 10 by arranging the position information of the user terminal 10 read from the communication log database in chronological order using communication times. At this time, the generation module 3033 may perform a process (cleansing process) to remove part of the acquired position information. When the cleansing process is performed, the generation module 3033 creates a new people flow node in the people flow node DB with the position information that remains unremoved from among a group of position information corresponding to a series of communication logs arranged in chronological order. be stored as a record.

Next, the generation module 3033 refers to the people flow node DB and defines people flow links that connect the people flow nodes. The generation module 3033 stores the defined human flow link as a new record in the human flow link DB.

Next, in generating trip data, the generation module 3033 uses the position information and time information to calculate the movement speed for each human flow link. The generation module 3033 uses the calculated travel speed to determine the means of transportation used in the travel route. In determining the means of transportation, various types of information regarding transportation hubs stored in the transportation network database 50 are used to determine the means of transportation that has a high probability of being applicable.
The generation module 3033 determines the means of transportation for each human flow link, and inputs the determination result into the trip mode in the human flow link DB.

Next, the generation module 3033 refers to the people flow link DB and defines a trip group. The generation module 3033 defines a group of human flow links that are in the same trip mode and are arranged in chronological order as one trip group. The generation module 3033 updates the trip group ID column in the people flow node DB and the people flow link DB, and records a new record in the trip group DB. This completes the trip data generation process.

After step S31, the system 1 obtains the expressway ETC usage details (step S32).
Specifically, the acquisition module 3032 of the server 30 acquires information regarding ETC usage details from, for example, an external server managed by an expressway company. The acquisition server stores information regarding the acquired usage details in the usage details DB. The generation module 3033 of the server 30 generates travel log data by referring to the usage details DB, as well as the pre-stored onboard equipment DB and toll booth DB. The generation module 3033 stores the generated travel log data as a new record in the travel log DB.

After step S32, the system 1 identifies (matches) movement data corresponding to the travel log obtained from the usage details (step S33). Details of the movement data identification process will be described later.

After step S33, the system 1 supplements the corresponding user information with respect to the travel log for which corresponding movement data is not specified (step S34). Details of the user ID complementing process will be described later.
With the above, the entire processing of the system 1 is completed.

(4-1) Processing for specifying movement data corresponding to a travel log Next, details of the process for specifying movement data corresponding to a travel log shown in step S33 in FIG. 12 will be described. FIG. 13 is a flowchart showing details of the matching process.
As shown in FIG. 13, in the matching process, the server 30 first selects a plurality of movement candidate data (step S331).
Specifically, the selection module 3034 of the server 30 selects movement data candidates corresponding to the vehicle travel log from among the plurality of movement data based on the degree of coincidence of the passage times of passing nodes in each of the usage details and movement data. A plurality of movement candidate data are selected.

At this time, the sorting module 3034 determines whether the movement data passes through a transit node adjacent to each of the approach IC and exit IC of the expressway in the travel log indicated by the usage details. The sorting module 3034 determines whether the passage time of each of the entry IC and exit IC indicated by the usage details and the passage time of each transit node indicated by the movement data are within a predetermined time difference when the movement data includes the corresponding passing node. Determine whether or not. The selection module 3034 selects the movement data as movement candidate data when both passing times are within a predetermined time difference.

Note that the time difference between passing times, which serves as a reference for this determination, is set to different values depending on the difference in roadside conditions between the entrance IC and the exit IC. That is, when the approach IC and the exit IC are located in a mountainous area, the time difference serving as a criterion for determination is set longer than when the approach IC and exit IC are located in an urban area. This is because location information is sampled less frequently in mountainous areas than in urban areas, so in order to be less susceptible to this influence, a longer time difference is allowed in mountainous areas than in urban areas.
The selection module 3034 stores the selected movement data as a new record in the movement candidate DB.

After step S331, the server 30 specifies movement data corresponding to the travel log (step S332).
Specifically, the identification module 3035 of the server 30 compares the selected group of travel candidate data with travel logs indicated by multiple usage details for one or more vehicles, thereby identifying the travel indicated by the specific usage details. Identify the movement data corresponding to the log. Here, a method for specifying movement data by the specifying module 3035 will be explained.

First, when the travel log indicated by multiple usage details regarding one vehicle matches multiple movement candidate data for the same user, the identification module 3035 corresponds to the travel log indicated by the multiple usage details. The plurality of movement candidate data are identified as movement candidate data.

Next, when the driving logs indicated by the plurality of usage details regarding the plurality of vehicles match the plurality of movement candidate data for the plurality of users, the identification module 3035 determines whether the plurality of use For each travel log indicated by the details, each of the plurality of movement candidate data is identified as the corresponding movement candidate data.

Next, if the travel log indicated by one usage detail for the same section on the same day matches movement candidate data for one or more users, the identification module 3035 corresponds to the travel log indicated by the usage detail. The movement candidate data for one or more users is specified as the movement candidate data.

Next, if the travel log indicated by one or more usage details in the same section matches the movement candidate data for one or more users, the specific module 3035 determines the usage of the area based on the time difference of the passing time. Movement candidate data for one or more users is specified as movement candidate data corresponding to the travel log indicated by the details.

The identification module 3035 stores the vehicle-mounted device ID of the travel log to be evaluated, the user ID of the identified movement data, and a new record in the determination result DB. This completes the movement information identification process for the travel log.

(4-3) About the user information complementation process Next, details of the user information complementation process shown in step S34 in FIG. 12 will be described. FIG. 14 is a flowchart showing details of the user information complementing process.
As shown in FIG. 14, in the user information supplementation process, user information is supplemented for travel logs for which corresponding travel data is not specified. A specific complementation method will be explained below.

First, as a first complement process, the specific module 3035 detects when the first user information is already linked to the on-vehicle device ID of the driving log related to two usage details arranged in chronological order regarding one vehicle. performs a process of supplementing the first user information with respect to the on-vehicle device ID related to the usage details located between the two usage details in chronological order. On the other hand, if a plurality of pieces of user information are already linked to the on-vehicle device IDs related to two usage details arranged in chronological order regarding one vehicle, the complementation process is not executed.

Next, as a second complement process, the specific module 3035 determines that the second user information has already been added to the on-vehicle device ID of the driving log related to more than half of the usage details on the same day among the multiple usage details for one vehicle. If they are linked, processing is performed to complement the second user information with respect to the on-vehicle device IDs related to other usage details on the same day. On the other hand, if the number does not exceed half, the complementation process is not executed.

Next, as a third complementary process, the specific module 3035 adds a third value to the onboard device ID of the travel log related to two usage details arranged in chronological order among the multiple usage details on the same day regarding one passenger vehicle. If the user information has already been linked, the third user information is supplemented to the on-vehicle device ID related to the usage details located between the two usage details in chronological order.

The specific module 3035 does not complement the user information for a travel log for which no user information is stored even after the first to third complement processes described above. The identification module 3035 records the trip group ID targeted for the complementation process and the user ID complemented for the trip group as a new record in the determination result DB. This completes the user information supplementation process.

(5) Summary As explained above, according to the system 1, the server 30 identifies the user's movement data corresponding to the travel log indicated by the usage details by comparing the usage details and the movement data, Processing is performed to link the on-vehicle device ID and user ID.

Further, the server 30 refers to the combination of the travel log and movement data for which the correspondence relationship has already been identified, and supplements the corresponding user information with respect to the travel log for which the corresponding movement data has not been specified. , link trip groups and user IDs.

Through these processes, it becomes possible to link the onboard device ID managed as the expressway usage history to the user ID registered as the user of the user terminal 10, and the onboard device ID that is managed as the expressway usage history can be linked to the user ID registered as the user of the user terminal 10. Vehicle information can be estimated. Therefore, it is possible to obtain a sufficient number of samples of expressway usage history that can provide significant information regarding traffic volume.

Further, the server 30 selects a plurality of movement candidate data that are movement data candidates corresponding to the travel log of a vehicle, and then selects a group of selected movement candidate data that has multiple usage details for one or more vehicles. By comparing with the travel log shown, processing is performed to identify movement data corresponding to the travel log indicated by the specific usage details. Therefore, it is possible to ensure the accuracy of the process of specifying the movement data corresponding to the travel log.

In addition, when the movement data passes through passing nodes adjacent to each of the approach IC and exit IC of the expressway in the travel log indicated by the usage details, the server 30 stores information about each of the approach ICs and exit ICs indicated by the usage details. If the passing time and the passing time of each passing node indicated by the movement data are within a predetermined time difference, the movement data is selected as movement candidate data. For this reason, we evaluate whether the positions of passing nodes and transit times match each other in travel logs obtained from usage details and travel data obtained from communication logs, and select travel data that has a high probability of corresponding to the travel logs. be able to.

Furthermore, the server 30 sets the range of time difference between passing times used for sorting determination to different values depending on the roadside conditions of the entrance IC and the exit IC. Therefore, it is possible to set a time difference that serves as an appropriate determination criterion, taking into consideration the sampling frequency of position information due to differences in roadside conditions.

Furthermore, when specifying travel data corresponding to a travel log, if the travel log indicated by multiple usage details regarding one vehicle matches multiple travel candidate data regarding the same user, the server 30 identifies the travel data corresponding to the travel log. The plurality of movement candidate data are identified as movement candidate data corresponding to the travel logs indicated by the plurality of usage details. Therefore, it is possible to specify the correspondence between a vehicle and a user, assuming that the user always uses the same vehicle.

In addition, when specifying movement data corresponding to a driving log, the server 30 determines whether the driving log indicated by the plurality of usage details regarding the plurality of vehicles matches the plurality of movement candidate data regarding the plurality of users. According to the time difference, each of the plurality of movement candidate data is specified as the corresponding movement candidate data for each of the travel logs indicated by the plurality of usage details. Therefore, for a group traveling in a plurality of vehicles, the user ID corresponding to each vehicle can be identified with high accuracy, taking into consideration the passing time at the passing node.

Furthermore, when specifying travel data corresponding to a travel log, the server 30 determines if the travel log indicated by one usage detail for the same section on the same day matches travel candidate data for one or more users. specifies movement candidate data for one or more users as movement candidate data corresponding to the travel log indicated by the usage details. Therefore, it is possible to ensure the accuracy of the process of specifying the movement data corresponding to the travel log.

Furthermore, when specifying travel candidate data corresponding to travel logs, if the travel logs indicated by one or more usage details for the same section match the travel candidate data for one or more users, According to the time difference between passing times, movement candidate data for one or more users is specified as movement candidate data corresponding to the travel log indicated by the usage details. Therefore, it is possible to ensure the accuracy of the process of specifying the movement data corresponding to the travel log.

In addition, by performing the various types of complementation processing described above, the server 30 refers to combinations of travel logs and travel data for which a correspondence relationship has already been identified, and for travel logs for which corresponding travel data has not been identified. and supplement the corresponding user information. Therefore, even if a group of selected travel candidate data is compared with multiple travel logs of one or more vehicles, corresponding user information is supplemented for travel logs in which the corresponding travel data cannot be identified. be able to.

(6) Other Processes Next, other processes of the system 1 will be explained. FIG. 15 is a diagram illustrating other processing. As shown in FIG. 15, as process 1, the system 1 specifies or complements the correspondence between the aforementioned vehicle travel log and the movement data of the user terminal 10. As a result, the determination result DB shown in FIG. 10C is obtained, and the on-vehicle device ID that can identify the vehicle and the user ID of the user of the user terminal 10 are linked.

Then, the system 1 executes the following process 2 and process 3 based on the process 1.
・Processing 2: Processing of estimating vehicle identification information for general road movement data using the correspondence between user ID and vehicle identification information (on-vehicle device ID) ・Processing 3: Processing of tabulating OD tables by vehicle type These processes will be explained in detail below in order.

(6-1) Process of estimating vehicle specific information from general road movement data In this process, the server 30 estimates the user based on the user information linked to the onboard device ID, which is vehicle specific information. Estimate the vehicle used in the trip data when traveling on general roads.

Specifically, the estimation module 3036 of the server 30 refers to the trip group DB and the people flow link DB, and selects a trip group whose trip mode is general road/vehicle as an evaluation target. The estimation module 3036 refers to the trip DB to specify the terminal ID of the selected trip group, and then refers to the terminal DB to specify the user ID.
Next, the estimation module 3036 refers to the determination result DB to identify the on-vehicle device ID associated with the specified user ID, thereby estimating the on-vehicle device ID corresponding to the user ID.

Next, in the determination result DB, a plurality of vehicle-mounted device IDs may be linked to one user ID. The estimation process in such a case will be described in detail.
When estimating the vehicle used in the general road movement data, the estimation module 3036 determines whether the general road movement data to be evaluated constitutes one trip data together with the expressway movement data.
In this primary determination, if general road movement data and expressway movement data coexist in one day and constitute one trip data, the estimation module 3036 calculates whether the same user's expressway movement data on the same day It is determined whether there is one vehicle or multiple vehicles associated with the movement data.

In this secondary determination, if only one vehicle is linked to one or more expressway movement data on the same day, that vehicle is considered as the vehicle used in the general road movement data that is the subject of evaluation. presume.
On the other hand, in the secondary judgment, if multiple vehicles are linked to one or more expressway movement data on the same day, the most frequently used vehicle is selected as the one used in the general road movement data that is the subject of evaluation. It is estimated that the vehicle is

In addition, in the above-described primary determination, if general road movement data and expressway movement data do not coexist and do not constitute one trip data in a day, the estimation module 3036 determines whether the same user's It is determined whether there is one vehicle or a plurality of vehicles associated with expressway movement data within a predetermined period, for example, the same month.

In this secondary determination, if only one vehicle is linked to one or more expressway movement data for the same month, that vehicle will be considered as the vehicle used in the general road movement data that is the subject of evaluation. presume.
On the other hand, in the secondary judgment, if multiple vehicles are linked to one or more expressway movement data for the same month, the vehicles that are frequently used within the same month are It is estimated that the vehicle was used in At this time, the type of day of the week within the same month may be considered. For example, if the general road movement data to be evaluated indicates movement on weekdays, identify frequently used vehicles using the expressway movement data on weekdays in the same month, and When indicating movement, vehicles that are frequently used may be identified using expressway movement data on holidays within the same month. Note that the predetermined period is not limited to the same month, but the evaluation period can be within several weeks or months, and whether the same user has one or more vehicles associated with the expressway movement data. It may be determined whether
This completes the process of estimating vehicle specific information for the general road movement data.

(6-2) OD table creation process In this process, the server 30 uses the data obtained through the previous processes to create an OD table that shows the amount of travel for each starting point and ending point for each vehicle type in a tabular format. create.
Specifically, the creation module 3037 of the server 30 uses the trip DB to extract a plurality of trip data included in the evaluation target period.

Next, the creation module 3037 refers to the four DBs managed as the user's movement history and the communication log DB to identify the positions of the start point and end point in the extracted trip data.

Next, the creation module 3037 mainly refers to the determination result DB and the complementation result DB for the extracted trip data, and identifies the onboard equipment ID used for the trip. The creation module 3037 refers to the onboard equipment DB and identifies the vehicle type corresponding to the specified onboard equipment ID.
Then, the creation module 3037 creates an OD table by totaling the identified starting point and ending point positions and the corresponding vehicle type for the entire plurality of trip data included in the evaluation target period.

FIG. 16 is a diagram showing a specific example of an OD table by prefecture.
As shown in FIG. 16, in the OD table, the number of moving vehicles is aggregated for each starting point and ending point as the actual use of general road movement data and expressway movement data during the evaluation period. In the illustrated example, starting points and ending points are aggregated for each prefecture, but starting points and ending points may be aggregated for each city, ward, town, or village.
In addition, we have adopted a regional mesh statistics method that divides regions into mesh areas without gaps based on latitude and longitude and organizes statistical data for each area, and uses the mesh area allocated for each area as a starting point. You can also tally up the end points.

In this way, in System 1, by performing processing to estimate vehicle identification information on general road movement data, the vehicle identification information and user ID obtained by comparing expressway usage records and expressway movement data are processed. It is possible to estimate the vehicle used for movement with respect to the general road movement data indicating the user's movement route on the general road by utilizing the correspondence relationship between the user and the user.
This makes it possible to estimate the region of the start and end points as well as the type of vehicle used for trip data that shows the travel route in a series of travel actions from the user's start point to the end point. The included road usage status can be efficiently aggregated.

In addition, System 1 creates an OD table in which the number of moving vehicles at each starting point and ending point is aggregated for each vehicle type as a usage record of general road movement data and expressway movement data during the evaluation period. It is now possible to aggregate movement trends by vehicle type, making it possible to obtain useful information not only for maintenance and operation of general roads and expressways, but also for a wide range of fields such as urban planning.

(7) Other modified examples Other modified examples of the system 1 are shown below.
In the embodiment described above, the process of matching the expressway usage record and the travel route of the user terminal 10 has been described, but the present invention is not limited to this. For example, the system 1 may match the usage history of an IC card ticket indicating the usage history of a railway with the travel route of the user terminal 10.
Note that in the following description, descriptions of configurations similar to those of the embodiment described above will be omitted.

In the system 1 according to the first modification, the structure of the database is different from the above-described actual configuration.
The server 30 of the system 1 according to the modified example stores the following four databases instead of the four databases stored as databases managed in the use of expressways in the above-described embodiment. An example of the structure of each database will be explained along with columns included in each database.

1) Ticket gate details DB: A database that manages details of ticket gate history at ticket gates ・Ticket gate details ID: Identification information that can identify ticket gate details ・Used IC card ID: IC card boarding where the ticket gate corresponding to the ticket gate ID was performed Ticket identification information/Ticket gate ID: Identification information of the ticket gate where the ticket gate corresponding to the ticket gate ID was operated.Ticket gate date and time: Date and time when the ticket gate corresponding to the ticket gate ID was operated.

2) IC card DB: A database that manages information related to IC card tickets ・IC card ID: Identification information that can identify an IC card ticket ・User name: Name of the user of the IC card ticket corresponding to the IC card ID・Balance held: Balance deposited in the IC card corresponding to the IC card ID ・Commuter pass information: Information regarding the commuter pass set on the IC card ticket corresponding to the IC card ID (regular section and validity period)

3) Ticket gate DB: A database that manages information about station ticket gates ・Ticket gate ID: Identification information that can identify the ticket gate ・Location station name: Station name and location where the ticket gate corresponding to the ticket gate ID is installed: Location information/location coordinates of the station where the ticket gate corresponding to the ticket gate ID is installed: Representative latitude and longitude information of the station name where the ticket gate corresponding to the ticket gate ID is installed

4) Riding log DB: A database that manages riding history. - Riding log ID: Identification information that can identify the riding history. - IC card ID: Identification information of the IC card ticket used in the riding history corresponding to the riding log ID. Boarding ticket gate ID: Identification information of the ticket gate where the ticket gate was opened at the boarding station in the boarding history corresponding to the boarding log ID ・ Boarding ticket gate date and time: In the boarding history corresponding to the boarding log ID, the date and time at which the ticket gate was checked at the boarding station Information/Transit ticket gate ID: Identification information of the ticket gate where the ticket gate was used when transferring between lines or transferring in the ride history corresponding to the boarding log ID (if not applicable, it will be NuLL)
・Pass ticket gate date and time: In the ride history corresponding to the ride log ID, the date and time information of the ticket gate at the time of transfer between routes or transfers (if not applicable, it will be NuLL)
・Disembarking ticket gate ID: In the boarding history corresponding to the boarding log ID, identification information of the ticket gate at which the ticket gate was used at the exiting station. -Disembarking ticket gate date and time: In the boarding history corresponding to the boarding log ID, the ticket gate was used at the disembarking station. date and time information

In the movement candidate DB stored in the storage unit 302 of the server 30, ride log IDs are stored instead of travel log IDs.
In the determination result DB stored in the storage unit 302 of the server 30, an IC card ID is stored instead of the onboard device ID.
In the complementation result DB stored in the storage unit 302 of the server 30, an IC card ID is stored instead of the onboard device ID.

The server 30 sequentially executes processes from acquiring communication logs to supplementing user information, similar to the process shown in FIG. 12 in the above-described embodiment. At this time, the server 30 acquires the ride details instead of "obtaining the usage details" in step S32.
Furthermore, the server 30 specifies the movement information corresponding to the riding log instead of "specifying the movement information corresponding to the travel log" in step S33.
Through this series of processing, the IC card ID of the IC card ticket and the user ID of the user terminal 10 become linked information in the determination result DB. Further, in the complementation result DB, the trip group ID and the IC card ID are linked.

As described above, the server 30 according to the modified example can link the IC card ID of the IC card ticket of the railway transportation facility to the user ID registered as the user of the user terminal 10. , it is possible to estimate the railway facilities that users use on a daily basis. Therefore, it is possible to obtain a sufficient number of samples of the usage history of railway transportation that can provide significant information regarding the usage of railway transportation.

Furthermore, in the embodiment described above, the on-vehicle device ID is used as the vehicle identification information, but the invention is not limited to this. For example, identification information that can identify a vehicle body may be used as vehicle identification information.

Further, in the embodiment described above, the generation module 3033 of the server 30 has explained the process of generating trip data from the acquired communication log, but the present invention is not limited to this. The server 30 may acquire trip data by accepting trip data generated by an external server.

Further, the trip data may be generated using a data structure different from that of the embodiment described above. For example, in the people flow node DB shown in FIG. 7C, the results of transportation point determination, which is position matching with transportation points, may be associated with each person flow node. The transportation point determination in this case is performed, for example, by the following process.

The generation module 3033 of the server 30 performs matching processing with transportation hubs or transportation links for each of the people flow nodes defined in step S31 shown in FIG. 12. Specifically, the generation module 3033 determines whether the positional relationship between the location of the people flow node and the locations of transportation hubs and transportation links stored in the transportation network database 50 is within a predetermined threshold. , the transportation base or transportation link to which the people flow node corresponds is estimated.

For example, if there is a road link within 200 meters from the human flow node to be evaluated, the generation module 3033 matches the human flow node to the road link with the shortest distance.
Further, the generation module 3033 matches the people flow node with the airport if the people flow node is located within the area of the airport. The threshold value used for determination can be set arbitrarily.
The generation module 3033 records the information regarding the transportation base estimated by such matching processing in the people flow node DB in association with the people flow node ID.

Then, in the system 1, the information regarding the traffic hubs obtained for the people flow nodes may be used in comparison with the travel log obtained from the expressway usage details. In this case, by determining whether each of the approach and exit interchanges of the expressway in the travel log match the traffic base (corresponding interchange) estimated by traffic base determination for the human flow node, movement candidates can be determined. Processing to select a plurality of pieces of data may also be performed.

In addition, in the system 1, when the travel log data includes information regarding the passing facility ID indicating the transfer point and the passing date and time, the position and time of the transfer point, the passing node and the passing time in the movement data, The degree of agreement may be evaluated. This increases the number of matching positions, thereby improving the determination accuracy.

Although the preferred embodiments of the present disclosure have been described above, the present disclosure is not limited to such specific embodiments, and the present disclosure includes the inventions described in the claims and their equivalents. It will be done. Further, the configurations of the devices described in the above embodiments and modified examples can be combined as appropriate as long as no technical contradiction occurs.
Moreover, the program of the present invention may be expressed by a plurality of source codes, and the system 1 of the present invention may be realized by a plurality of hardware resources.

(Additional note)
Additional notes regarding the embodiments of the present invention are shown below.

(Additional note 1)
A program executed by a system having a computer equipped with a processor,
The program is sent to the processor
a step of acquiring movement data that is created by arranging the position information of the mobile terminal according to the communication time and indicates the movement route of the user carrying the mobile terminal (step S31);
a step of obtaining ETC usage details indicating the expressway usage record and including information on the point and passing time of the interchange used, and information on the vehicle type of the vehicle (step S32);
a step of identifying travel data corresponding to the travel log indicated by the usage details by comparing the usage details and the travel data (step S33);
a step (step S34) of referencing combinations of travel logs and travel data for which correspondence has already been identified, and supplementing corresponding user information for travel logs for which no corresponding travel data has been identified; A program to be executed.

(Additional note 2)
In the step of specifying movement data (step S33),
A step of selecting a plurality of movement candidate data, which are movement data candidates corresponding to the vehicle travel log, from among the plurality of movement data, based on the degree of coincidence of the passage times of passing nodes in each of the usage details and movement data (step S331). and,
A step of identifying the user's movement data corresponding to the travel log indicated by the specific usage details by comparing the selected group of movement candidate data with the travel logs indicated by the plurality of usage details of one or more vehicles. (Step S332). The program according to supplementary note 1.

(Additional note 3)
In the step of selecting a plurality of movement candidate data (step S331),
If the movement data passes through passing nodes adjacent to each of the approach and exit interchanges of the expressway in the travel log indicated by the usage details, the time of passing each of the approach and exit interchanges indicated by the usage details, and the movement data 3. The program according to claim 2, which selects the movement data as movement candidate data when the passing time of each passing node indicated by is within a predetermined time difference.

(Additional note 4)
4. The program according to claim 3, wherein the time difference is set to different values depending on the roadside conditions of the approach interchange and the exit interchange.

(Appendix 5)
In the step of identifying the user's movement data (step S33),
If the travel logs indicated by multiple usage details for one vehicle match multiple movement candidate data for the same user, the travel logs shown by the multiple usage details are used as the travel data corresponding to the travel logs shown by the multiple usage details. The program according to claim 2, which specifies movement candidate data.

(Appendix 6)
In the step of identifying the user's movement data (step S33),
When travel logs indicated by multiple usage details regarding multiple vehicles match multiple movement candidate data regarding multiple users, the travel logs indicated by the multiple usage details are updated according to the time difference between passing times. The program according to claim 2, which identifies each of the plurality of movement candidate data as the corresponding movement data.

(Appendix 7)
In the step of identifying the user's movement data (step S33),
If the travel log indicated by one usage detail for the same section on the same day matches the travel candidate data for one or more users, one or more travel logs corresponding to the travel log indicated by the usage detail are 3. The program according to claim 2, wherein the program identifies movement candidate data for a user.

(Appendix 8)
In the step of identifying the user's movement data (step S33),
If the travel log indicated by one or more usage details in the same section matches the movement candidate data for one or more users, the travel log indicated by the usage details is matched according to the time difference between the passing times. The program according to claim 2, which specifies movement candidate data for one or more users as movement data.

(Appendix 9)
In the step of supplementing the user information (step S33), the processor further includes:
If the first user information is already linked to vehicle specific information related to two usage details arranged in chronological order regarding one vehicle, the first user information is located between the two usage details in chronological order. The program according to claim 1, which complements the first user information with vehicle specific information related to usage details.

(Appendix 10)
In the step of supplementing the user information (step S33), the processor further includes:
If the second user information is already linked to the vehicle identification information for more than half of the usage details on the same day among multiple usage details for one vehicle, the vehicle information related to other usage details on the same day The program according to claim 1, which complements the specific information with second user information.

(Appendix 11)
In the step of supplementing the user information (step S33), the processor further includes:
If the third user information is already linked to the vehicle specific information related to two usage details arranged in chronological order among multiple usage details on the same day regarding one passenger vehicle, the third user information is linked in chronological order. 2. The program according to claim 1, wherein the third user information is supplemented to the vehicle specific information related to the usage details located between the two usage details.

(Appendix 12)
In addition, the processor
Using information about the vehicle type and information about the start and end points in trip data, which is a collection of user movement data linked to the vehicle, the amount of travel for each start point and end point for each vehicle type is displayed in a tabular format. The program according to claim 1, causing the program to execute the step of creating an OD table shown in .

(Appendix 13)
In addition, the processor
The program according to claim 1, which executes the step of estimating a vehicle used in movement data when the user moves on a general road, using vehicle identification information linked to user information.

(Appendix 14)
In the step of estimating the vehicle used,
In the case where the general road movement data that is the subject of evaluation constitutes one trip data together with the expressway movement data, and there is only one vehicle linked to the expressway movement data of the same user on the same day. estimates the vehicle as the vehicle used in the general road movement data that is the subject of evaluation, and if there are multiple vehicles, selects the frequently used vehicle as the vehicle that was used in the general road movement data that is the subject of evaluation. The program according to claim 13, which estimates.

(Appendix 15)
In the step of estimating the vehicle used,
In the case where the general road movement data to be evaluated does not constitute one trip data together with the expressway movement data, and there is only one vehicle linked to the same month's expressway movement data for the same user. The vehicle is estimated as the vehicle used in the trip data that is the subject of evaluation, and if there are multiple vehicles, the vehicle that is used frequently within the same month is estimated as the vehicle that was used in the trip data that is the subject of evaluation. , the program according to claim 13.

(Appendix 16)
A method performed by a system having a computer with a processor, the method comprising:
The program allows the processor to
obtaining movement data that is created by arranging the location information of the mobile terminal according to the communication time and indicates the movement route of the user carrying the mobile terminal;
a step of obtaining ETC usage details indicating expressway usage records, including information regarding the location and passing time of the interchange used, and information regarding the vehicle type of the vehicle;
identifying the user's movement data corresponding to the travel log indicated by the usage details by comparing the usage details and the movement data;
A method of performing the steps of: referring to a combination of a travel log and travel data for which a correspondence relationship has already been identified, and supplementing corresponding user information for a travel log for which no corresponding travel data has been identified; .

(Appendix 17)
A system comprising a computer with a processor, the system comprising:
The program allows the processor to
means for acquiring movement data that is created by arranging location information of mobile terminals according to communication time and indicates a movement route of a user carrying the mobile terminal;
means for obtaining ETC usage details indicating expressway usage records, including information on the point and passing time of the interchange used, and information on the vehicle type of the vehicle;
means for identifying the user's movement data corresponding to the travel log indicated by the usage details by comparing the usage details and the movement data;
A system comprising means for referencing a combination of a travel log and travel data for which a correspondence relationship has already been identified and supplementing corresponding user information with respect to a travel log for which no corresponding travel data has been identified.

(Appendix 18)
A program executed by a system having a computer equipped with a processor,
The program is sent to the processor
obtaining movement data that is created by arranging the location information of the mobile terminal according to the communication time and indicates the movement route of the user carrying the mobile terminal;
Obtaining ticket gate details of the IC card ticket indicating the usage history of the railway transportation facility and including information about the station points and ticket gate times at which the passenger boarded and alighted, and information about the passenger;
identifying movement data of the user corresponding to the ride log indicated by the ticket gate details by comparing the ticket gate details and the movement data;
A program that executes a step of referencing a combination of a ride log and movement data for which a correspondence relationship has already been identified, and supplementing corresponding user information for a ride log for which corresponding movement data has not been identified. .

(Appendix 19)
A method for causing a system having a computer with a processor to perform the steps,
The method is that the processor
obtaining movement data that is created by arranging the location information of the mobile terminal according to the communication time and indicates the movement route of the user carrying the mobile terminal;
Obtaining ticket gate details of the IC card ticket indicating the usage history of the railway transportation facility and including information about the station points and ticket gate times at which the passenger boarded and alighted, and information about the passenger;
identifying movement data of the user corresponding to the ride log indicated by the ticket gate details by comparing the ticket gate details and the movement data;
A method of performing the steps of: referencing a combination of a ride log and travel data for which a correspondence relationship has already been identified, and supplementing corresponding user information for a ride log for which no corresponding travel data has been identified; .

(Additional note 20)
A system that causes a system having a computer with a processor to execute,
The program allows the processor to
a module that acquires movement data that is created by arranging location information of mobile terminals according to communication time and indicates a movement route of a user carrying a mobile terminal;
A module that obtains ticket gate details of an IC card ticket, which shows the usage history of a railway transportation facility, and includes information about the station points and ticket gate times at which the passenger boarded and alighted, and information about the passenger;
a module that identifies user movement data corresponding to the ride log indicated by the ticket gate details by comparing the ticket gate details and the movement data;
A system comprising: a module that refers to a combination of a ride log and movement data for which a correspondence relationship has already been specified, and supplements corresponding user information for a ride log for which no corresponding movement data has been specified.

1 People flow analysis system 10 User terminal 30 Information processing server 40 Base station database 50 Transportation network database 80 Network 81 Fixed positioning equipment

Claims (20)

A program executed by a system having a computer equipped with a processor,
The program causes the processor to:
Travel data that is created by arranging location information of mobile terminals according to communication time and indicates a travel route of a user carrying the mobile terminal , and is identification information of the user that is set when using the mobile terminal. obtaining the movement data including the user ID ;
a step of obtaining ETC usage details indicating expressway usage records, including information regarding the location and passing time of the interchange used, and information regarding the vehicle type of the traveling vehicle;
By comparing the usage details and the movement data, identifying the movement data corresponding to the driving log indicated by the usage details, and linking the vehicle identification information of the driving log and the user ID of the movement data. and,
Referring to the combination of the travel log and the travel data for which a correspondence relationship has already been identified, complementing the corresponding user ID with respect to the travel log for which the corresponding travel data has not been identified; A program to run. In the step of identifying the movement data,
selecting a plurality of movement candidate data, which are candidates for movement data corresponding to a travel log of the vehicle, from among the plurality of movement data, based on the usage details and the degree of coincidence of passing times of passing nodes in each of the movement data;
By comparing the selected group of movement candidate data with the travel logs indicated by the plurality of usage details of one or more vehicles, the user's movement data corresponding to the travel log indicated by the specific usage details is determined. The program according to claim 1, causing the program to execute the step of specifying. In the step of selecting a plurality of movement candidate data,
In the case where the movement data passes through a passing node adjacent to each of the approach interchange and exit interchange of the expressway in the travel log indicated by the usage details, the passing time of each of the approach interchange and exit interchange indicated by the usage details 3. The program according to claim 2, which selects the movement data as the movement candidate data when the time of passage of each passing node indicated by the movement data is within a predetermined time difference. 4. The program according to claim 3, wherein the time difference is set to different values depending on roadside conditions at an entrance interchange and an exit interchange. In the step of identifying the movement data of the user,
If a travel log indicated by a plurality of the usage details regarding one vehicle matches a plurality of the travel candidate data regarding the same user, the travel log indicated by the plurality of usage details is used as the travel candidate data corresponding to the travel log indicated by the plurality of usage details. 3. The program according to claim 2, wherein the program specifies the plurality of movement candidate data. In the step of identifying the movement data of the user,
If the travel logs indicated by the plurality of usage details regarding a plurality of vehicles match the plurality of movement candidate data regarding a plurality of users, the travel logs indicated by the plurality of usage details are adjusted according to the time difference between passing times. 3. The program according to claim 2, wherein each of the plurality of movement candidate data is identified as the corresponding movement candidate data. The step of identifying the user's movement data includes:
If the travel log indicated by one of the usage details for the same section on the same day matches the travel candidate data for one or more users, the travel log corresponding to the travel log indicated by the usage detail is used as the travel candidate data. 3. The program according to claim 2, wherein the program specifies the movement candidate data for one or more users. In the step of identifying the movement data of the user,
If the travel log indicated by one or more of the usage details in the same section matches the movement candidate data for one or more users, the travel log indicated by the usage details in accordance with the time difference between passing times. 3. The program according to claim 2, wherein the program specifies the movement candidate data for one or more users as movement candidate data corresponding to the movement candidate data. In the step of supplementing the user ID , the processor further includes:
If the first user ID is already linked to the vehicle specific information related to the two usage details arranged in chronological order regarding one vehicle, the first user ID is already linked between the two usage details in chronological order. The program according to claim 1, which complements the first user ID with vehicle identification information related to the usage details located therein. In the step of supplementing the user ID , the processor further includes:
If the second user ID is already linked to the vehicle identification information related to more than half of the usage details on the same day among the plurality of usage details on the same day, the other usage details on the same day The program according to claim 1, which complements the second user ID with respect to vehicle identification information. In the step of supplementing the user ID , the processor further includes:
If the third user ID is already linked to the vehicle identification information related to two usage details arranged in chronological order among the plurality of usage details on the same day regarding one passenger vehicle, 2. The program according to claim 1, wherein the third user ID is supplemented for vehicle specific information related to the usage details located between the two usage details along the line. The processor further includes:
Displays the amount of travel for each starting point and ending point for each vehicle type using information regarding the vehicle type and information on the starting point and ending point in trip data, which is a collection of the user's movement data linked to the vehicle. The program according to claim 1, causing the program to execute the step of creating an OD table shown in the format. The processor further includes:
2. The method according to claim 1, wherein the vehicle identification information linked to the user information is used to estimate a vehicle used in the movement data when the user moves on a general road. program. In the step of estimating the used vehicle,
In the case where the general road movement data to be evaluated constitutes one trip data together with the expressway movement data, and the number of vehicles linked to the above expressway movement data on the same day for the same user is one; In this case, the vehicle is estimated as the vehicle used in the general road movement data that is the subject of evaluation, and if there are multiple vehicles, the frequently used vehicle is estimated as the vehicle that was used in the general road movement data that is the subject of evaluation. The program according to claim 13, which estimates as a vehicle. In the step of estimating the used vehicle,
If the general road movement data to be evaluated does not constitute one trip data together with the expressway movement data, only one vehicle is associated with the expressway movement data within a predetermined period for the same user. In some cases, the vehicle is estimated to be the vehicle used in the trip data to be evaluated, and if there are multiple vehicles, the most frequently used vehicle within a predetermined period is estimated to be the vehicle used in the trip data to be evaluated. The program according to claim 13, which estimates as a vehicle. A method performed by a system having a computer with a processor, the method comprising:
The method includes the processor:
Travel data that is created by arranging location information of mobile terminals according to communication time and indicates a travel route of a user carrying the mobile terminal , and is identification information of the user that is set when using the mobile terminal. obtaining the movement data including the user ID ;
a step of obtaining ETC usage details indicating expressway usage records, including information regarding the location and passing time of the interchange used, and information regarding the vehicle type of the traveling vehicle;
By comparing the usage details and the movement data, the movement data of the user corresponding to the driving log indicated by the usage details is specified, and the vehicle identification information of the driving log and the user ID of the movement data are identified. The step of linking,
Referring to the combination of the travel log and the travel data for which a correspondence relationship has already been identified, complementing the corresponding user ID with respect to the travel log for which the corresponding travel data has not been identified; How to do it. A system comprising a computer with a processor, the system comprising:
In the system, the processor:
Travel data that is created by arranging location information of mobile terminals according to communication time and indicates a travel route of a user carrying the mobile terminal , and is identification information of the user that is set when using the mobile terminal. means for acquiring the movement data including a user ID ;
means for obtaining ETC usage details that indicate the usage history of the expressway and include information regarding the location and passing time of the interchange used, and information regarding the vehicle type of the traveling vehicle;
By comparing the usage details and the movement data, the movement data of the user corresponding to the driving log indicated by the usage details is specified, and the vehicle identification information of the driving log and the user ID of the movement data are identified. A means of linking,
means for complementing the corresponding user ID with respect to the travel log for which the corresponding travel data has not been identified, with reference to a combination of the travel log and the movement data for which a correspondence relationship has already been specified; A system equipped with. A program executed by a system having a computer equipped with a processor,
The program causes the processor to:
Travel data that is created by arranging location information of mobile terminals according to communication time and indicates a travel route of a user carrying the mobile terminal , and is identification information of the user that is set when using the mobile terminal. obtaining the movement data including the user ID ;
Obtaining ticket gate details of the IC card ticket indicating the usage history of the railway transportation facility and including information about the station points and ticket gate times at which the passenger boarded and alighted, and information about the passenger;
By comparing the ticket gate details and the movement data, the user's movement data corresponding to the ride log indicated by the ticket gate details is identified, and the identification information of the IC card ticket in the ride log and the movement data in the movement data are identified . a step of linking the user ID;
Referring to a combination of the ride log and the travel data for which a correspondence relationship has already been identified, complementing the corresponding user ID with respect to the ride log for which the corresponding travel data has not been identified; A program to run. A method for causing a system having a computer with a processor to perform the steps,
The method includes the processor:
Travel data that is created by arranging location information of mobile terminals according to communication time and indicates a travel route of a user carrying the mobile terminal , and is identification information of the user that is set when using the mobile terminal. obtaining the movement data including the user ID ;
Obtaining ticket gate details of the IC card ticket indicating the usage history of the railway transportation facility and including information about the station points and ticket gate times at which the passenger boarded and alighted, and information about the passenger;
By comparing the ticket gate details and the movement data, the user's movement data corresponding to the ride log indicated by the ticket gate details is identified, and the identification information of the IC card ticket in the ride log and the movement data in the movement data are identified . a step of linking the user ID;
Referring to a combination of the ride log and the travel data for which a correspondence relationship has already been identified, complementing the corresponding user ID with respect to the ride log for which the corresponding travel data has not been identified; How to do it. A system that causes a system having a computer with a processor to execute,
In the system, the processor:
Travel data that is created by arranging location information of mobile terminals according to communication time and indicates a travel route of a user carrying the mobile terminal , and is identification information of the user that is set when using the mobile terminal. a module that acquires the movement data including a user ID ;
A module that obtains ticket gate details of an IC card ticket, which shows the usage history of a railway transportation facility, and includes information about the station points and ticket gate times at which the passenger boarded and alighted, and information about the passenger;
By comparing the ticket gate details and the movement data, the user's movement data corresponding to the ride log indicated by the ticket gate details is identified, and the identification information of the IC card ticket in the ride log and the movement data in the movement data are identified . A module that links the user ID,
a module that refers to a combination of the ride log and the movement data for which a correspondence relationship has already been identified, and complements the corresponding user ID for the ride log for which the corresponding movement data is not specified; A system equipped with