Program, method and system
The system addresses the challenge of insufficient traffic volume data by linking vehicle and user information from mobile terminals, enabling comprehensive traffic analysis through expressway usage history and OD table generation.
Patent Information
- Application Number
- JP2023078993
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-22
- Estimated Expiration
- 2043-05-12
AI Technical Summary
Conventional traffic situation surveys face challenges in obtaining a sufficient number of samples to provide meaningful information on traffic volume.
A system that collects and processes location information from mobile terminals to acquire expressway usage history by linking vehicle identification information with user IDs, complementing missing data through comparison with travel logs, and generating OD tables for traffic analysis.
Enables the acquisition of a sufficient number of samples for expressway usage history, providing significant information on traffic volume and facilitating accurate traffic analysis.
Smart Images

Figure 2024163417000001_ABST
Abstract
Description
[Technical field]
[0001] The present disclosure relates to a program, a method, and a system. [Background technology]
[0002] In the past, the general practice in expressway management was to grasp the current traffic situation, then predict future traffic conditions, and consider the necessary maintenance plans for the future. During this process, web surveys of expressway users are periodically conducted to sample the usage of the expressway. Moreover, Patent Document 1 below discloses a system for conducting road traffic surveys by photographing traveling vehicles. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2017-138861 A Summary of the Invention [Problem to be solved by the invention]
[0004] However, in conventional traffic condition surveys, it has been difficult to obtain a sufficient number of samples that can provide meaningful information on traffic volume.
[0005] An object of the present invention is to provide a system capable of acquiring a history of expressway usage that is a sufficient number of samples that can provide meaningful information regarding traffic volume. [Means for solving the problem]
[0006] The program of the present invention causes a processor to execute the following steps: acquiring movement data, which is created by arranging the location information of the mobile terminal according to the communication time and indicates the movement route of a user carrying the mobile terminal; acquiring an ETC usage statement indicating the history of expressway usage and including information on the locations and passing times of ICs used, and information on the vehicle type; comparing the usage statement and the movement data to identify the user's movement data corresponding to the driving log indicated by the usage statement and linking the vehicle identification information in the driving log with the user ID of the movement data; and complementing the corresponding user information for driving logs for which corresponding movement data has not been identified by referring to combinations of driving logs and movement data for which a correspondence has already been identified. Effect of the Invention
[0007] According to the present invention, it is possible to obtain a sufficient number of samples of expressway usage history that can provide meaningful information regarding traffic volume. [Brief description of the drawings]
[0008] [Figure 1] 1 is a diagram showing an overview of a people flow analysis system according to an embodiment of the present invention. [Diagram 2] 2 is a block diagram showing a hardware configuration of the user terminal shown in FIG. 1. [Diagram 3] 2 is a block diagram showing a hardware configuration of the administrator terminal shown in FIG. 1. [Figure 4] 2 is a block diagram showing a hardware configuration of a server shown in FIG. 1. [Diagram 5] 5 is a block diagram showing a functional configuration of the server shown in FIG. 4. [Figure 6] FIG. 2 is a diagram showing a database managed when using a user terminal. [Figure 7] FIG. 13 is a diagram showing a database for managing a user's movement history. [Figure 8] FIG. 4 is a diagram showing a structure of trip data in the present embodiment. [Figure 9]FIG. 1 is a diagram showing a database managed in the use of expressways. [Figure 10] FIG. 13 is a diagram showing a database managed as a result of a matching process. [Figure 11] FIG. 1 is a diagram for explaining an overview of the present embodiment. [Figure 12] 2 is a flow chart showing the overall process of the present embodiment. [Figure 13] 11 is a flow diagram showing details of a process for identifying travel information corresponding to a travel log. [Figure 14] 13 is a flow chart showing details of a user information complementing process. [Figure 15] 11A and 11B are diagrams illustrating other functions of the people flow analysis system. [Figure 16] FIG. 13 is a diagram showing an example of an OD table. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In the drawings for explaining the embodiment, the same components are generally designated by the same reference numerals, and the repeated description will be omitted.
[0010] (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 below. Fig. 1 is a conceptual diagram showing an overview of the system 1 of this embodiment. As shown in Fig. 1, System 1 responds to operational instructions from an administrator by comparing and matching ETC usage details (hereinafter, sometimes simply referred to as usage details) showing the usage record of expressways with movement data obtained from the communication log of the mobile phone (user terminal 10) carried by the user, thereby providing information useful for analyzing the usage record of expressways. Here, movement data is information indicating the user's movement route (changes in location information) identified by changes over time in the location information of the mobile phone, and is subdivided by means of transportation as follows: · Highway travel data General road travel data Air travel data Walking data
[0011] Specifically, system 1 matches the driving log included in the usage details, which indicates the history of the expressway driving route, with the movement data, which indicates the history of the user's movement route, and links the vehicle identification information included in the usage details with the user ID of the user who is the subject of the movement, identified from the movement data. In this embodiment, the vehicle identification information is the vehicle-mounted device ID of the ETC vehicle-mounted device installed in the traveling vehicle, and the user ID is the identification information of the user set when using the mobile phone.
[0012] In this way, the system 1 identifies the user ID and the vehicle used by the user, tallying up the usage record of the expressway, and also performs a wide range of analysis of traffic conditions by linking the vehicle identification information to movement data (general road movement data) when using general roads through a process described later. The configuration of such a system 1 will be described.
[0013] (2) Overall configuration of System 1 As shown in FIG. 1, the system 1 includes a user terminal 10, an administrator terminal 20, and an information processing server 30 (hereinafter simply referred to as the server 30). The user terminal 10, the administrator terminal 20, and the server 30 are connected via a network 80 (for example, the Internet or an intranet). 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 .
[0014] 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 called a mobile terminal. In addition to a mobile phone, such mobile terminals include wifi beacons carried by a user, mobile antennas used for radar positioning, on-board car navigation terminals compatible with ITS spots (DSRC), and communication terminals using Bluetooth (registered trademark). The mobile terminal may be other devices that communicate while moving.
[0015] The fixed positioning device 81 refers to a device that is fixed at a fixed location and communicates with communication devices, and includes, in addition to a mobile phone base station, for example, a mobile phone base station, a positioning device that communicates with a wifi beacon, a positioning device that performs radar positioning, a positioning device in an ITSspot, etc. The fixed positioning device 81 may be any other device as long as it is fixed at a fixed location and communicates with communication devices.
[0016] The user terminal 10 may include various computers, such as a smartphone, a tablet terminal, and a wearable device (e.g., 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 taking as an example a smartphone that performs mobile communication with the fixed positioning device 81 provided with an antenna used for mobile communication of a mobile phone.
[0017] The administrator terminal 20 is an information processing device used by an administrator of the system 1. The administrator terminal 20 is a terminal where an administrator who analyzes the movement data accumulated in the base station database 40 and the ETC usage details showing the usage record of the expressway performs instruction operations required for the matching process. The administrator terminal 20 may include various computers such as a personal computer and a server computer (for example, a web server, an application server, a database server, or a combination thereof). In this embodiment, the administrator terminal 20 will be described taking as an example a personal computer used by the administrator.
[0018] The server 30 is an information processing device that performs various processes (to be described later) on the input information. The server 30 mainly executes a process of matching the location information of the user terminal 10 with the highway usage details. The server 30 may include various computers such as a personal computer, a server computer (for example, a Web server, an application server, a database server, or a combination thereof), etc. In this embodiment, the server 30 will be described taking a server computer as an example.
[0019] The base station database 40 is a database that accumulates a huge amount of location information acquired by multiple user terminals 10 through mobile communication with fixed positioning devices 81. The base station database 40 accumulates, as a communication log, user terminal information and location information at the time of communication.
[0020] When the user terminal 10 is located in a communication area in which the fixed positioning device 81 can communicate, the fixed positioning device 81 stores location information estimated from radio waves received from the user terminal 10 together with time information in the base station database 40. The base station database 40 is a database operated by a mobile phone carrier, and stores the location information acquired by the fixed positioning device 81 together with time information as a communication log for each terminal used.
[0021] The transportation network database 50 is a database that stores information on transportation means such as railroads, expressways, airways, etc. The transportation network database 50 stores the following information as information on transportation means: - Facility name, facility number, location, and applicable means of transportation for each transportation hub - Route names, road names, and air route names connecting each transportation hub Location information of transport links connecting each transport hub (including the location of roads and railways) Here, the transportation hub includes various transportation facilities that serve as passing points (passing nodes) when using each mode of transportation, such as airports, stations, express buses, and highway interchanges (hereinafter referred to as ICs).
[0022] (1-1) Configuration of User Terminal 10 The following describes the configuration of the user terminal 10. Fig. 2 is a block diagram showing the configuration of the user terminal 10 of this embodiment.
[0023] 2, the user terminal 10 includes a storage device 11, a processor 12, an input / output interface 13, and a communication interface 14. The user terminal 10 is connectable to at least one of an input device 15 and an output device 16.
[0024] The storage device 11 is configured to store programs and data. The storage device 11 is, for example, a combination of a Read Only Memory (ROM), a Random Access Memory (RAM), and a storage (for example, a flash memory or a hard disk).
[0025] The programs include, for example, the following programs: ·OS (Operating System) programs · Programs for applications that process information (e.g. web browsers)
[0026] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)
[0027] The processor 12 is configured to realize the functions of the user terminal 10 by running a program stored in the storage device 11. The processor 12 is an example of a computer.
[0028] The input / output interface 13 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 15 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 16.
[0029] The input device 15 is, for example, a keyboard, a pointing device, a touch panel, a physical button, a sensor (for example, a camera, a vital sensor, or a combination thereof), or a combination thereof.
[0030] The output device 16 is, for example, a display, a speaker, a printing device, or a combination thereof.
[0031] The communication interface 14 is configured to control communications between the user terminal 10 and external devices.
[0032] (1-2) Configuration of administrator terminal 20 The following describes the configuration of the administrator terminal 20. Fig. 3 is a block diagram showing the configuration of the administrator terminal 20 of this embodiment.
[0033] 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.
[0034] The storage device 21 is configured to store programs and data. The storage device 21 is, for example, a combination of a Read Only Memory (ROM), a Random Access Memory (RAM), and a storage (for example, a flash memory or a hard disk).
[0035] The programs include, for example, the following programs: ·OS (Operating System) programs · Programs for applications that process information (e.g. web browsers)
[0036] The data includes, for example, the following data: Databases referenced in information processing Data obtained by performing information processing (i.e., the results of performing information processing)
[0037] The processor 22 is configured to realize the functions of the administrator terminal 20 by starting a program stored in the storage device 21. The processor 22 is an example of a computer.
[0038] The input / output interface 23 is configured to receive signals (e.g., user instructions, sensing signals, or a combination thereof) from the input device 25 and output signals (e.g., image signals, audio signals, or a combination thereof) to the output device 26.
[0039] The input device 25 is, for example, a keyboard, a pointing device, a touch panel, a physical button, a sensor (for example, a camera, a vital sensor, or a combination thereof), or a combination thereof.
[0040] The output device 26 is, for example, a display, a speaker, a printing device, or a combination thereof.
[0041] The communication interface 24 is configured to control communications between the administrator terminal 20 and external devices.
[0042] (1-3) Hardware configuration of server 30 The following describes the configuration of the server 30. 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 .
[0043] The storage device 31 is configured to store programs and data, and is, for example, a combination of a ROM, a RAM, and a storage (for example, a flash memory or a hard disk).
[0044] The programs include, for example, the following programs: -OS programs Application programs that perform information processing
[0045] The data includes, for example, the following data: Databases referenced in information processing Results of information processing
[0046] The processor 32 is configured to realize the functions of the server 30 by running a program stored in the storage device 31. The processor 32 is an example of a computer.
[0047] The communication interface 34 is configured to control communications between the server 30 and external devices.
[0048] (1-4) Functional configuration of server 30 Next, a description will be given of the functional configuration of the server 30. FIG. As shown in FIG. 5, the server 30 functions as a communication unit 301, a storage unit 302, and a control unit 303.
[0049] (1-4-1) Functions of the communication unit 301 and the storage unit 302 The communication unit 301 performs processing for the server 30 to communicate with external devices.
[0050] The storage unit 302 stores data and programs used by the 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) · Vehicle-mounted device database (Vehicle-mounted device DB) · Tollgate database (tollgate DB) · Driving log database (Driving log DB) · Migration candidate database (Migration candidate DB) · Judgment result database (Judgment result DB) Complementary Result Database (Complementary Result DB)
[0051] The user DB is a database that stores information about the users who use the user terminal 10. The user DB will be described in detail later.
[0052] The terminal DB is a database that stores information about the user terminal 10. The terminal DB will be described in detail later.
[0053] The people flow node DB is a database that stores information about nodes corresponding to position information specified by a communication log among movement data obtained from position information of the user terminal 10. The people flow node DB will be described in detail later.
[0054] The people flow link DB is a database that stores information about routes (links) between nodes among movement data obtained from position information of the user terminal 10. The people flow link DB will be described in detail later.
[0055] The trip group DB is a database that stores information about a set (trip group) of nodes and links grouped for each trip mode, which is information indicating a means of transportation, among the travel data obtained from the position information of the user terminal 10. The trip group DB will be described in detail later.
[0056] The trip DB is a database that stores information on trip data indicating a travel route for each series of travel behavior from a starting point to an end point of a specific user, among travel data obtained from the position information of the user terminal 10. The trip DB will be described in detail later. Note that since the trip data is a collection of travel data for each series of travel behavior from a starting point to an end point, multiple trip data may exist in one day.
[0057] The usage details DB is a database that stores information on ETC usage details that show the actual usage of expressways. The user DB will be described in detail later.
[0058] The on-board device DB is a database that stores information about on-board devices installed in vehicles that use expressways. The details of the on-board device DB will be described later.
[0059] The toll gate DB is a database that stores information about toll gates on expressways. The toll gate DB will be described in detail later.
[0060] The travel log DB is a database that stores information about the travel logs of vehicles that use expressways. The details of the travel section DB will be described later.
[0061] The travel candidate DB is a database that stores information about travel candidate data. The travel candidate data is data that is a candidate for travel data corresponding to the vehicle's driving log among multiple travel data that constitute the trip data. The travel candidate DB will be described in detail later.
[0062] The determination result DB is a database that stores the results of a determination of matching between the highway driving log and the movement data. The details of the determination result DB will be described later.
[0063] The completion result DB is a database that stores the completion results of the user information corresponding to the highway driving log. The details of the completion result DB will be described later.
[0064] (1-4-2) Functions of the control unit 303 The control unit 303 shown in FIG. 5 functions as a transmission / reception control module 3031, an acquisition module 3032, a generation module 3033, a selection module 3034, an identification module 3035, an estimation module 3036, a creation module 3037, and an output module 3038 by the processor 32 of the server 30 performing processing according to a program.
[0065] <Functions of the transmission / reception control module 3031> The transmission / reception control module 3031 controls the processing in which the server 30 transmits and receives signals from external devices in accordance with a communication protocol.
[0066] <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 details of the ETC usage and records them as a new record in the usage details DB in the storage unit 302. The usage details include information on the points of entrance and exit points and the time of passing through the IC used, and information on the type of vehicle.
[0067] <Functions of Generation Module 3033> The generation module 3033 processes the communication logs contained in the communication log DB and generates data to be stored in each of the following DBs. - People flow node database ·People Flow Link DB Trip Group DB Trip DB These details will be described later along with the structure of each DB.
[0068] <Functions of sorting module 3034> The selection module 3034 selects a plurality of candidate travel data that are candidates for travel data corresponding to the vehicle's travel log from among the plurality of travel data based on the degree of agreement of the passing time of the passing node in the usage details and the travel data. Details of this process will be described later.
[0069] <Functions of specific module 3035> The identification module 3035 identifies the user's travel data corresponding to the travel log by comparing the usage details and the travel data. At this time, the identification module 3035 identifies the travel data corresponding to the travel log indicated by the specific usage details by comparing a group of travel candidate data selected by the selection module with the travel logs indicated by multiple usage details for one or multiple vehicles, and links the vehicle identification information of the travel log with the user ID of the travel data. Details of this process will be described later. In addition, the identification module 3035 refers to a combination of a travel log and movement data for which a correspondence has already been identified, and complements and links the corresponding user information to a travel log for which corresponding movement data has not been identified. Details of this process will be described later.
[0070] <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 vehicle-mounted device ID, which is the vehicle identification information obtained by the matching process, and the user information. Details of this process will be described later.
[0071] <Functions of Creation Module 3037> The creation module 3037 creates and outputs an OD table (Origin-Destination Table Matrix) for each vehicle type using the vehicle identification information and user information that are associated with each other. The OD table is one of the methods for investigating the statistical road usage status, and is data that shows in a table format how many vehicles are moving from which origin (origin) to which destination (destination) in order to investigate the flow of vehicles. The OD table and the details of the creation method thereof will be described later.
[0072] <Output module 3038 functions> The output module 3038 outputs to the administrator terminal 20 the results of the processing performed by the other modules.
[0073] (2) Database structure Next, an example of the structure of each database stored in the storage unit 302 will be described.
[0074] (2-1) DB managed when using the user terminal 10 First, the following DBs managed in the use of the user terminal 10 shown in FIG. 6 will be described. User DB Terminal DB ·Communication log database
[0075] (2-1-1) User DB FIG. 6A is a diagram showing a specific example of the user DB. As shown in FIG. 6A, the user DB includes the following items: "user ID," "name," "age," "gender," "place of residence," "occupation," and "contract details."
[0076] The item "user ID" stores identification information that can identify the user who uses the user terminal 10.
[0077] The item "name" stores information about the name of the user corresponding to the user ID.
[0078] The item "age" stores information about the age of the user corresponding to the user ID.
[0079] The item "gender" stores information about the gender of the user corresponding to the user ID.
[0080] The item "residence" stores information about the residence of the user corresponding to the user ID.
[0081] The item "occupation" stores information about the occupation of the user corresponding to the user ID.
[0082] The item "contract details" stores information about the details of the usage contract concluded by the user corresponding to the user ID regarding the use of the user terminal 10. For example, the contract details may include a contract ID that can identify the contract. It should be noted that these configurations are merely examples, and the user DB may include other columns.
[0083] (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 an item "terminal ID," an item "user ID," and an item "contract ID."
[0084] The item "terminal ID" stores identification information of a terminal that can identify the user terminal 10.
[0085] The item "user ID" stores identification information of the user who uses the driving log corresponding to the driving log ID.
[0086] The item "contract ID" stores the identification number of the usage contract concluded regarding the use of the driving log corresponding to the driving log ID. It should be noted that these configurations are merely examples, and the terminal DB may include other columns.
[0087] (2-1-3) Communication log database 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 "location coordinates", and an item "communication time".
[0088] The item "communication log ID" stores identification information of a communication log that can identify communication of the user terminal 10.
[0089] The item "terminal ID" stores the terminal ID of the user terminal 10 that performed the communication corresponding to the communication log ID.
[0090] The item "location coordinates" stores the location coordinates of the user terminal 10 acquired in the communication corresponding to the communication log ID.
[0091] The item "communication time" stores information about the time when communication corresponding to the communication log ID was performed. It should be noted that these configurations are merely examples, and the communication log DB may include other columns.
[0092] (2-2) A database that manages user movement history Next, the following DBs managed as the user's movement history (movement data) shown in FIG. 7 will be described. Trip DB Trip Group DB - People flow node database ·People Flow Link DB
[0093] (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 "date of action."
[0094] The item "trip ID" stores identification information of the trip data that can identify the user terminal 10 of the trip data that can specify the trip data.
[0095] 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.
[0096] The item "date of action" stores information indicating the date on which the user's movement indicated by the trip data corresponding to the trip ID was performed. It should be noted that these configurations are merely examples, and the trip DB may include other columns.
[0097] (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."
[0098] The item "trip group ID" stores identification information for identifying a trip group.
[0099] The item "trip ID" stores identification information of the trip data to which the trip group corresponding to the trip group ID belongs. It should be noted that these configurations are merely examples, and the trip group DB may include other columns.
[0100] (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".
[0101] The item "people flow node ID" stores identification information of a people flow node that can identify the people flow node.
[0102] The item "communication log ID" stores identification information of a communication log to which a people flow node corresponding to a people flow node ID applies. A communication log to which a people flow node applies refers to a communication log in which the people flow node is recorded as location information.
[0103] 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.
[0104] The item "Reference time" stores the time information that is the reference for the time series of 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 in which the people flow node is acquired as location information. Note that these configurations are merely examples, and the people flow node DB may include other columns.
[0105] (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 items “people flow link ID”, “start node ID”, “end node ID”, “trip mode ID”, “trip group ID”, and “reference time ID”.
[0106] The item "people flow link ID" stores identification information of a people flow link that can specify the people flow link.
[0107] The item "start node ID" stores the people flow node ID of the people flow node (start node) that is the start point of the people flow link corresponding to the people flow link ID.
[0108] The item "end node ID" stores the people flow node ID of the people flow node (end node) that is the end point of the people flow link corresponding to the people flow link ID.
[0109] The item "trip mode" stores information indicating the means of transportation in the people flow link corresponding to the people flow link ID.
[0110] The item "trip group ID" stores identification information of a trip group that includes a people flow link corresponding to a people flow link ID.
[0111] The item "Reference time" stores time information that is the reference for the time series of the people flow link corresponding to the people flow link ID. The reference time of a people flow link corresponds to the communication time of the communication log in which the position information of at least one of the start node or end node of the people flow link is acquired. For example, the communication times corresponding to the position information of both the start node and the end node may be managed as the first reference time and the second reference time, respectively, or only the communication time corresponding to the position information of the start node may be managed as the reference time. Note that these configurations are merely examples, and the people flow node DB may include other columns.
[0112] Next, the structure of trip data (<people flow data>) defined using four DBs that are managed as such user movement history will be described. Fig. 8 is a diagram showing the structure of trip data. As shown in FIG. 8, in the movement data including the start node n1 to the end node n21, people flow links are defined between each node. The people flow links are linked by determining the trip mode (means of transportation) based on the movement distance and the movement time. In the illustrated example, the multiple people flow links arranged in time series are classified into five trip groups based on the difference in 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, the trip group is treated as a unit of movement data corresponding to the travel log. Specifically, group B and group D are the expressway movement data to be compared with the travel log.
[0113] (2-3) Database managed for expressway use Next, the following DB, which is managed as the usage record of expressways shown in FIG. 9, will be described. ·Usage details DB ·Onboard equipment DB · Tollgate DB -Driving log database
[0114] (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 an item "usage details ID", an item "used vehicle-mounted device ID", an item "used interchange / toll gate ID", and an item "usage date and time".
[0115] The item "usage details ID" stores identification information of the usage details that can identify the usage details.
[0116] The item "Used Vehicle Unit ID" stores identification information of the ETC vehicle unit installed in the vehicle that used the expressway corresponding to the usage details ID.
[0117] The item "Interchange / Tollgate ID Used" stores the identification number of the interchange or tollgate where the expressway corresponding to the usage details ID was used.
[0118] The item "date and time of use" stores information about the date and time when the expressway corresponding to the usage detail ID was used. Note that these configurations are merely examples, and the usage details DB may include other columns.
[0119] (2-3-2) Onboard equipment DB FIG. 9B is a diagram showing a specific example of the vehicle-mounted device DB. As shown in FIG. 9B, the vehicle-mounted device DB includes an item "vehicle-mounted device ID" and an item "vehicle type."
[0120] The item "On-board unit ID" stores identification information of the on-board unit that can identify the ETC on-board unit installed in the vehicle.
[0121] The item "vehicle type" stores information indicating the vehicle type of the vehicle in which the on-board device corresponding to the on-board device ID is installed. It should be noted that these configurations are merely examples, and the vehicle-mounted device DB may include other columns.
[0122] (2-3-3) Tollgate DB FIG. 9C is a diagram showing a specific example of the toll gate DB. As shown in FIG. 9C, the toll gate DB includes an item "IC / toll gate ID", an item "facility name", an item "location", and an item "position coordinates".
[0123] The item "IC / tollgate ID" stores identification information that can identify an IC or tollgate on a highway.
[0124] The item "facility name" stores the facility name of the IC or toll gate corresponding to the IC / toll gate ID.
[0125] The item "Location" stores information about the location of the IC or toll gate corresponding to the IC / toll gate ID, for example, written in the address number format.
[0126] The item "location coordinates" stores latitude and longitude information indicating the location coordinates of the IC or toll gate corresponding to the IC / toll gate ID. It should be noted that these configurations are merely examples, and the IC / tollgate DB may include other columns.
[0127] (2-3-4) Driving log database FIG. 9D is a diagram showing a specific example of the driving log DB. As shown in FIG. 9D, the driving log DB includes an item "driving log ID", an item "vehicle device ID", an item "entry facility ID", an item "entry date and time", an item "passage facility ID", an item "passage date and time", an item "exit facility ID", and an item "exit date and time".
[0128] The item "driving log ID" stores identification information of the driving log that can identify the driving log on the expressway.
[0129] The item "on-board device ID" stores identification information of the on-board device that was installed in the vehicle that used the expressway corresponding to the driving log ID.
[0130] The item "entry facility ID" stores identification information of the IC or toll gate where the vehicle entered the expressway when using the expressway corresponding to the driving log ID.
[0131] The item "entry date and time" stores information indicating the date and time when the vehicle entered the expressway when using the expressway corresponding to the travel log ID.
[0132] The item "Passing facility ID" stores the identification information of the IC or toll gate passed during the driving section when using the expressway corresponding to the driving log ID. Note that the passing facility ID is recorded only when passing a facility (transfer point) such as a toll gate that is the boundary between the expressway management companies. This information on the transfer point is used to change the toll system in the sections before and after it.
[0133] The item "passing date and time" stores information indicating the date and time when the vehicle passed through the IC or toll gate corresponding to the passing facility ID when using the expressway corresponding to the travel log ID.
[0134] The item "Exit facility ID" stores identification information of the IC or toll gate where the vehicle exited the expressway when using the expressway corresponding to the driving log ID.
[0135] The item "Exit Date and Time" stores information indicating the date and time when the vehicle exited an IC or toll gate when using the expressway corresponding to the driving log ID. It should be noted that these configurations are merely examples, and the driving log DB may include other columns.
[0136] (2-4) Database managed as a result of matching process Next, the following DB managed as a result of the matching process shown in FIG. 10 will be described. ·Migration candidate DB ·Judgment result DB Complement result DB
[0137] (2-4-1) Migration candidate database FIG. 10A is a diagram showing a specific example of a migration candidate DB. As shown in FIG. 10A, the travel candidate DB includes an item "travel candidate ID", an item "travel log ID", and an item "trip group ID".
[0138] The item "movement candidate ID" stores identification information of the movement candidate data that can specify the movement candidate data.
[0139] The item "travel log ID" stores identification information of the travel log to be evaluated in the travel candidate data corresponding to the travel candidate ID.
[0140] The item "trip group ID" stores identification information of a trip group estimated as a candidate for travel data corresponding to the relevant travel log as travel candidate data corresponding to the travel candidate ID. It should be noted that these configurations are merely examples, and the migration candidate DB may include other columns.
[0141] (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 "vehicle-mounted device ID", and an item "user ID".
[0142] The item "determination result ID" stores identification information of the determination result that can identify the determination result of the matching process between the travel log and the movement data.
[0143] The item "vehicle-mounted device ID" stores identification information of the vehicle-mounted device that recorded the driving log that was evaluated in the judgment corresponding to the judgment result ID.
[0144] The item "user ID" stores identification information of the user terminal 10 associated with the vehicle-mounted device ID in the determination corresponding to the determination result ID. It should be noted that these configurations are merely examples, and the determination result ID may include other columns.
[0145] (2-4-3) Complementary Result DB FIG. 10C is a diagram showing a specific example of the complement 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".
[0146] The item "complementation result ID" stores identification information of the complementation result that can identify the result of the complementation process of the user information for the driving log.
[0147] The item "driving log" stores identification information of the driving log that was evaluated in the complementation process corresponding to the complementation result ID.
[0148] The item "user ID" stores the user ID associated with the corresponding driving log in the complementation process corresponding to the complementation result ID. It should be noted that these configurations are merely examples, and the complement result ID may include other columns.
[0149] (3) Overview of the embodiment The outline of this embodiment will be described. In response to an operation instruction from an administrator, the system 1 compares the user's movement data generated from the communication log of the user terminal 10 with the vehicle's travel log obtained from the expressway usage details, and identifies the movement data that corresponds to the travel log, thereby performing a matching process between the movement data and the travel log. This process will be described with a specific example.
[0150] FIG. 11 is a diagram for explaining an outline of this embodiment. 11, the people flow data generated from the communication log of the user terminal 10 indicates a series of movement routes starting from people flow node 1 and ending at people flow node 18. This series of movement routes is called the user's trip data. The trip data includes multiple people flow links, which are represented by dashed lines in the illustrated example.
[0151] This trip data includes the following trip groups: Group X (general road movement data) corresponding to people flow node 1 to people flow node 3 Group Y (expressway movement data) corresponding to people flow nodes 3 to 15 Group Z (general road movement data) corresponding to people flow nodes 15 to 18 Details of each of these movement data are managed in the four DBs shown in FIG.
[0152] On the other hand, the system 1 generates a travel log indicating passed nodes indicated by white rectangles on the map of FIG. 11 based on the usage details of the expressway. Specifically, the travel log is generated using information in Usage Detail 1 recorded when the vehicle passed through the IC that was the entrance, and information in Usage Detail 2 recorded when the vehicle passed through the IC that was the exit. If there is a transfer point, information in Usage Detail 3 recorded when the vehicle passed through the transit facility is also used. By identifying multiple transit nodes from the usage details, the route shown by the dashed line in Figure 11 can be estimated as the travel route of the vehicle.
[0153] Next, in response to an operation instruction from the administrator, the system 1 performs a process of matching the corresponding movement data with the travel log R. Although not shown in the figure, in reality, the system 1 estimates the movement data corresponding to the travel log from the degree of agreement between the position and time of each passing node from the huge amount of movement data detected on the evaluation target day and the huge amount of usage details recorded on the same day.
[0154] 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 perspective. The location of people flow node 3 is close to the location of the IC where usage details 1 is recorded. The reference time of people flow node 3 is close to the time of passing through the IC where usage details 1 was recorded. The location of the people flow node 15 is close to the location of the IC where the usage details 2 are recorded. The reference time of people flow node 3 is close to the time of passing through the IC where usage details 1 was recorded.
[0155] System 1 selects multiple pieces of travel data that are highly likely to correspond to the travel log to be evaluated as candidate travel data from the massive amounts of accumulated travel data and travel logs, based on the degree of match between the passed nodes and passing times contained in each.
[0156] From the selected travel candidate data, the system 1 selects the one with the highest probability of being relevant and specifies it as the travel data corresponding to the travel log to be evaluated. The system 1 then links the in-vehicle device corresponding to the travel log with the user ID of the user terminal 10 corresponding to the travel data. This allows the vehicle type linked to the in-vehicle device ID to be associated with the user ID. Such processing by the system 1 will be described in detail below.
[0157] (4) System 1 processing Next, the processing of the system 1 will be described.
[0158] (4-1) Overall processing of System 1 FIG. 12 is a flow chart showing the overall processing of the system 1. 12, first, the system 1 acquires a communication log (step S30). Specifically, the acquisition module 3032 of the server 30 acquires the communication log accumulated in the base station database 40. The acquisition module 3032 stores the acquired communication log in the communication log DB.
[0159] After step S30, the system 1 processes the acquired communication log to acquire trip data (step S31). Specifically, the generation module 3033 of the server 30 first sets an identification number for new trip data for each user terminal and travel date, and records it as a new record in the trip DB.
[0160] Next, the generation module 3033 defines people flow nodes on 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 the communication time. At this time, the generation module 3033 may execute a process (cleansing process) of removing part of the acquired position information. When the generation module 3033 executes the cleansing process, the generation module 3033 stores the remaining position information that has not been removed from a group of position information corresponding to a series of communication logs arranged in chronological order in the people flow node DB as a record of a new people flow node.
[0161] Next, the generation module 3033 refers to the people flow node DB and defines people flow links connecting the people flow nodes. The generation module 3033 stores the defined people flow links as new records in the people flow link DB.
[0162] Next, the generation module 3033 calculates the movement speed of each pedestrian flow link using the position information and time information in generating the trip data. The generation module 3033 determines the transportation means used in the movement route using the calculated movement speed. In determining the transportation means, various information on the transportation bases accumulated in the transportation network database 50 is used to determine the transportation means that are highly likely to be applicable. The generation module 3033 determines the mode of transportation for each people flow link, and inputs the determination result into the trip mode in the people flow link DB.
[0163] Next, the generation module 3033 refers to the people flow link DB to define a trip group. The generation module 3033 defines a group of people flow links that have the same trip mode and are arranged in chronological order as one trip group. The generation module 3033 updates the trip group ID columns 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.
[0164] After step S31, the system 1 acquires details of the ETC usage on the expressway (step S32). Specifically, the acquisition module 3032 of the server 30 acquires information on ETC usage details from, for example, an external server managed by a highway company. The acquisition server stores the acquired information on the usage details in a usage details DB. The generation module 3033 of the server 30 generates driving log data by referring to the usage details DB and the pre-stored on-board device DB and toll gate DB. The generation module 3033 stores the generated driving log data as a new record in the driving log DB.
[0165] After step S32, the system 1 identifies (matches) movement data corresponding to the travel log obtained from the usage details (step S33). The process of identifying movement data will be described in detail later.
[0166] After step S33, the system 1 complements the relevant user information for the travel log for which corresponding movement data is not specified (step S34). The details of the user ID complementation process will be described later. With the above, the entire processing of the system 1 is completed.
[0167] (4-1) Identifying travel data corresponding to the travel log Next, a detailed description will be given of the process of identifying travel data corresponding to the travel log shown in step S33 of Fig. 12. Fig. 13 is a flow chart showing the details of the matching process. As shown in FIG. 13, in the matching process, first, the server 30 selects a plurality of movement candidate data (step S331). Specifically, the selection module 3034 of the server 30 selects multiple candidate travel data from among the multiple travel data, based on the degree of match between the passing times of passed nodes in the usage details and the travel data, which are candidates for travel data corresponding to the vehicle's driving log.
[0168] At this time, the selection module 3034 judges whether the movement data passes through a passing node adjacent to each of the entrance IC and the exit IC of the expressway in the driving log shown in the usage details. When the movement data includes a passing node, the selection module 3034 judges whether the passing time of each of the entrance IC and the exit IC shown in the usage details and the passing time of each passing node shown in the movement data are within a predetermined time difference. When the passing times of both are within the predetermined time difference, the selection module 3034 selects the movement data as movement candidate data.
[0169] The time difference in passing times that serves as the basis for this judgment is set to different values depending on the differences in the road conditions of the entrance and exit ICs. In other words, if the entrance and exit ICs are in mountainous areas, the time difference that serves as the basis for judgment is set longer than if they are in urban areas. This is because the sampling frequency of location information is lower 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 migration data as a new record in the migration candidate DB.
[0170] After step S331, the server 30 identifies 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 a plurality of usage details of one or a plurality of vehicles, thereby identifying travel data corresponding to the travel log indicated by the specific usage details. Here, a method for identifying travel data by the identification module 3035 will be described.
[0171] First, when the driving log indicated by multiple usage details for one vehicle matches multiple travel candidate data for the same user, the identification module 3035 identifies the multiple travel candidate data as the travel candidate data corresponding to the driving log indicated by the multiple usage details.
[0172] Next, when the driving logs indicated by the multiple usage details for the multiple vehicles match multiple travel candidate data for the multiple users, the identification module 3035 identifies each of the multiple travel candidate data as the corresponding travel candidate data for each of the driving logs indicated by the multiple usage details according to the time difference between the passing times.
[0173] Next, if a driving log indicated in a usage detail for the same section on the same day matches travel candidate data for one or more users, the identification module 3035 identifies the travel candidate data for the one or more users as the travel candidate data corresponding to the travel log indicated by the usage detail.
[0174] Next, if the driving log indicated by one or more usage details for the same section matches the travel candidate data for one or more users, the identification module 3035 identifies the travel candidate data for the one or more users as the travel candidate data corresponding to the driving log indicated by the usage details according to the time difference between the passing times.
[0175] The identification module 3035 stores the vehicle-mounted device ID of the travel log that is the subject of evaluation and the user ID of the identified travel data as a new record in the determination result DB. This ends the identification process of travel information for the travel log.
[0176] (4-3) Complementary processing of user information Next, a detailed description will be given of the user information complementing process shown in step S34 of Fig. 12. Fig. 14 is a flow chart showing the details of the user information complementing process. As shown in Fig. 14, in the user information complementation process, user information is complemented for a travel log for which corresponding movement data is not specified. A specific complementation method will be described below.
[0177] First, as a first complementation process, when the first user information is already linked to the vehicle-mounted device ID of the driving log related to two chronologically arranged usage details related to one vehicle, the identification module 3035 performs a process of complementing the first user information for the vehicle-mounted device ID related to the usage details located between the two chronologically arranged usage details. On the other hand, when multiple pieces of user information are already linked to the vehicle-mounted device ID related to two chronologically arranged usage details related to one vehicle, the complementation process is not executed.
[0178] Next, as a second complementation process, when the second user information is already linked to the vehicle-mounted device ID of the driving log related to more than half of the usage details of the same day related to one vehicle, the identification module 3035 performs a process of complementing the second user information to the vehicle-mounted device ID related to the other usage details of the same day. On the other hand, when the number does not exceed half, the complementation process is not executed.
[0179] Next, as a third complementation process, when third user information is already linked to the vehicle-mounted device ID of the driving log related to two chronologically arranged usage details among multiple usage details for the same day related to one passenger vehicle, the identification module 3035 complements the third user information with the vehicle-mounted device ID related to the usage detail located between the two usage details in the chronological order.
[0180] For a travel log for which user information is not stored even after the above first to third complementation processes, the identification module 3035 does not complement the user information. The identification module 3035 records the trip group ID that was the subject of the complementation process and the user ID that was complemented for that trip group as a new record in the determination result DB. This completes the user information complementation process.
[0181] (5) Summary As described above, according to the system 1, the server 30 compares the usage details and the travel data to identify the user's travel data that corresponds to the driving log indicated by the usage details, and performs a process of linking the vehicle-mounted device ID with the user ID.
[0182] In addition, the server 30 refers to a combination of a travel log and movement data for which a correspondence has already been identified, and complements the relevant user information for a travel log for which corresponding movement data has not been identified, thereby linking the trip group with the user ID.
[0183] These processes make it possible to link the user ID registered as the user of the user terminal 10 with the in-vehicle device ID managed as the highway usage history, and to estimate the vehicle information used by the user on a daily basis. Therefore, it is possible to obtain a sufficient number of samples of the highway usage history that can be used as meaningful information on traffic volume.
[0184] In addition, the server 30 selects a plurality of candidate travel data that are candidates for travel data corresponding to the travel log of the vehicle, and then performs a process of identifying travel data corresponding to a specific travel log indicated by a specific usage detail by comparing the selected group of candidate travel data with travel logs indicated by a plurality of usage details of one or a plurality of vehicles. This ensures the accuracy of the process of identifying travel data corresponding to the travel log.
[0185] In addition, when the travel data passes through a passing node adjacent to each of the entrance and exit ICs of the expressway in the travel log shown in the usage details, if the passing time of each of the entrance and exit ICs shown in the usage details and the passing time of each passing node shown in the travel data are within a predetermined time difference, the server 30 selects the travel data as travel candidate data. Therefore, by evaluating whether the positions and passing times of the passing nodes in the travel log obtained from the usage details and the travel data obtained from the communication log match, it is possible to select travel data that is highly likely to correspond to the travel log.
[0186] In addition, the server 30 sets the range of the time difference between the passing times used for the selection judgment to different values depending on the difference in the road conditions of the entrance IC and the exit IC. Therefore, it is possible to set the time difference that serves as an appropriate judgment criterion, taking into consideration the sampling frequency of the position information due to the difference in the road conditions.
[0187] In addition, when identifying travel data corresponding to a travel log, if a travel log indicated by a plurality of usage details for one vehicle matches a plurality of travel candidate data for the same user, the server 30 identifies the plurality of travel candidate data as the travel candidate data corresponding to the travel log indicated by the plurality of usage details. Therefore, it is possible to identify the correspondence between a vehicle and a user, assuming that the user always uses the same vehicle.
[0188] In addition, when identifying travel data corresponding to a travel log, if the travel log indicated by a plurality of usage details for a plurality of vehicles matches a plurality of travel candidate data for a plurality of users, the server 30 identifies each of the plurality of travel candidate data as the corresponding travel candidate data for each of the travel logs indicated by the plurality of usage details according to the time difference of the passing times. Therefore, for a group traveling by a plurality of vehicles, the user ID corresponding to each vehicle can be identified with high accuracy, taking into account the passing times at the passing nodes.
[0189] Furthermore, when identifying travel data corresponding to a travel log, if a travel log indicated by one usage detail for the same section on the same day matches travel candidate data for one or more users, the server 30 identifies the travel candidate data for one or more users as the travel candidate data corresponding to the travel log indicated by the usage detail. This ensures the accuracy of the process of identifying travel data corresponding to a travel log.
[0190] In addition, when identifying travel candidate data corresponding to a travel log, if the travel log indicated by one or more usage details for the same section matches the travel candidate data for one or more users, the server 30 identifies the travel candidate data for one or more users as the travel candidate data corresponding to the travel log indicated by the usage details according to the time difference between the passing times. This ensures the accuracy of the process of identifying travel data corresponding to a travel log.
[0191] In addition, the server 30 performs the various complementing processes described above to complement user information for a travel log for which corresponding travel data is not specified, by referring to a combination of a travel log and travel data for which a correspondence has already been identified. Therefore, even if a group of selected travel candidate data is compared with a plurality of travel logs for one or a plurality of vehicles, it is possible to complement corresponding user information for a travel log for which corresponding travel data cannot be identified.
[0192] (6) Other processing Next, other processing of the system 1 will be described. Fig. 15 is a diagram for explaining the other processing. As shown in Fig. 15, the system 1 specifies or complements the correspondence between the vehicle's travel log and the movement data of the user terminal 10 as process 1. As a result, a determination result DB shown in Fig. 10C is obtained, and the vehicle-mounted device ID capable of identifying the vehicle and the user ID of the user of the user terminal 10 are linked together.
[0193] Then, the system 1 executes the following processes 2 and 3, assuming that the process 1 has been completed. Process 2: A process of estimating vehicle identification information for general road movement data using the correspondence between user ID and vehicle identification information (vehicle-mounted device ID). Process 3: Aggregating OD tables by vehicle type These processes will be described in detail below in order.
[0194] (6-1) Processing to estimate vehicle identification information from general road movement data In this process, the server 30 estimates the vehicle used in the trip data when the user traveled on general roads, based on the user information linked to the vehicle-mounted device ID, which is vehicle identification information.
[0195] Specifically, the estimation module 3036 of the server 30 refers to the trip group DB and the pedestrian 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, identifies the terminal ID of the selected trip group, and then refers to the terminal DB to identify the user ID. Next, the estimation module 3036 refers to the determination result DB to identify an in-vehicle device ID linked to the identified user ID, thereby estimating an in-vehicle device ID corresponding to the user ID.
[0196] Next, in the determination result DB, a single user ID may be associated with multiple vehicle-mounted device IDs. The estimation process for 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 piece of trip data together with the expressway movement data. In this primary determination, if general road travel data and expressway travel data coexist within a day and constitute a single trip data, the estimation module 3036 determines whether there is one or multiple vehicles linked to the expressway travel data for the same day for the same user.
[0197] In this secondary determination, if there is only one vehicle linked to one or more pieces of expressway travel data for the same day, that vehicle is presumed to be the vehicle used in the general road travel data that is the subject of evaluation. On the other hand, in the secondary determination, if there are multiple vehicles linked to one or more expressway travel data for the same day, the vehicle that is used more frequently is presumed to be the vehicle used in the general road travel data being evaluated.
[0198] In addition, in the above-mentioned primary determination, if general road travel data and expressway travel data do not coexist within a day and do not constitute a single trip data, the estimation module 3036 determines whether the same user has one or multiple vehicles linked to expressway travel data within a specified period, for example, in the same month.
[0199] In this secondary determination, if there is only one vehicle linked to one or more pieces of expressway travel data for the same month, that vehicle is presumed to be the vehicle used in the general road travel data that is the subject of evaluation. On the other hand, in the secondary determination, if there are multiple vehicles linked to one or more expressway travel data in the same month, a vehicle that is used frequently in the same month is estimated as a vehicle used in the general road travel data to be evaluated. At this time, the type of day of the week in the same month may be taken into consideration. For example, if the general road travel data to be evaluated indicates travel on weekdays, a vehicle that is used frequently may be identified from the expressway travel data on weekdays in the same month, and if the general road travel data to be evaluated indicates travel on holidays, a vehicle that is used frequently may be identified from the expressway travel data on holidays in the same month. Note that the predetermined period is not limited to the same month, and it may be determined whether the number of vehicles linked to the expressway travel data for the same user is one or multiple, with an evaluation period being within several weeks or months. This completes the process of estimating vehicle identification information for the general road movement data.
[0200] (6-2) OD table creation process In this process, the server 30 uses the data obtained by the processes up to this point to create an OD table that shows, in tabular form, the amount of movement for each start point and end point for each vehicle type. 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.
[0201] Next, the creation module 3037 refers to the four DBs that manage the user's movement history and the communication log DB to identify the positions of the start point and the end point in the extracted trip data.
[0202] Next, the creation module 3037 mainly refers to the determination result DB and the complementation result DB to identify the vehicle-mounted device ID used for the movement for the extracted trip data. The creation module 3037 refers to the vehicle-mounted device DB to identify the vehicle type corresponding to the identified vehicle-mounted device ID. Then, the creation module 3037 creates an OD table by aggregating the identified start and end points and the corresponding vehicle types for all of the trip data included in the evaluation target period.
[0203] FIG. 16 is a diagram showing a specific example of an OD table by prefecture. As shown in Figure 16, the OD table tally up the number of moving vehicles for each starting point and ending point as the usage record of general road movement data and expressway movement data during the evaluation period. In the example shown, the starting points and ending points are tallied by prefecture, but the starting points and ending points may also be tallied by city, ward, town, and village. Alternatively, a method of regional mesh statistics may be adopted in which a region is divided into a network of mesh areas based on latitude and longitude, and statistical data for each area is compiled, with the start and end points being tallied for each mesh area assigned to each region.
[0204] In this way, in system 1, by performing a process of estimating vehicle identification information for general road movement data, it is possible to utilize the correspondence between the vehicle identification information obtained by comparing the expressway usage history with the expressway movement data and the user ID, and to estimate the vehicle used for movement for the general road movement data that shows the user's movement route on general roads. This makes it possible to estimate the type of vehicle used, along with the start and end regions, for trip data that shows the route traveled in a series of user travel actions from the starting point to the end point, and efficiently compile information on road usage, including not only expressways but also general roads.
[0205] In addition, System 1 creates an OD table in which the number of vehicles moving between start and end points is compiled by vehicle type as the utilization record of general road and expressway travel data during the evaluation period. This makes it possible to compile travel trends by vehicle type between regions, and enables the acquisition of useful information not only on the maintenance and operation of general roads and expressways, but also on a wide range of fields such as urban planning.
[0206] (7) Other modifications Other variations of the system 1 are described below. In the above embodiment, the process of matching the history of expressway usage with the travel route of the user terminal 10 has been described, but this is not limiting. For example, the system 1 may match the history of IC card ticket usage indicating the history of railway usage with the travel route of the user terminal 10. In the following description, the description of the same configuration as in the above-described embodiment will be omitted.
[0207] In the system 1 according to the first modification, the structure of the database is different from the current form described above. Server 30 of system 1 according to the modified example stores the following four databases instead of the four databases stored as databases managed for expressway use in the above-described embodiment. An example of the structure of each database will be described together with the columns included in each database.
[0208] 1) Ticket gate details DB: A database that manages details of ticket gate history at ticket gates Ticket gate detail ID: Identification information that can identify the ticket gate detail - IC card ID used: Identification information of the IC card ticket that was used for the ticket gate corresponding to the ticket gate ID Ticket gate ID: Identification information of the ticket gate through which the ticket was passed, which corresponds to the ticket gate ID - Ticket gate date and time: The date and time when the ticket gate corresponding to the ticket gate ID was passed
[0209] 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: The balance deposited in the IC card corresponding to the IC card ID. Commuter pass information: Information about the commuter pass set on the IC card ticket corresponding to the IC card ID (commuter pass area and validity period)
[0210] 3) Ticket gate DB: A database that manages information about ticket gates at stations. Ticket gate ID: Identification information that can identify the ticket gate - Station name: Name of the station where the ticket gate corresponding to the ticket gate ID is located Location: Location information of the station where the ticket gate corresponding to the ticket gate ID is installed Location coordinates: typical latitude and longitude information of the station name where the ticket gate corresponding to the ticket gate ID is located
[0211] 4) Ride Log DB: A database for managing ride history -Ride log ID: Identification information that can identify the ride history IC card ID: Identification information of the IC card used in the boarding history corresponding to the boarding log ID Boarding Ticket Gate ID: Identification information of the ticket gate used at the boarding station in the boarding history corresponding to the boarding log ID Boarding ticket gate date and time: Information on the date and time when the ticket gate was opened at the boarding station in the boarding history corresponding to the boarding log ID Passage Ticket Gate ID: Identification information of the ticket gate through which the user passed when transferring between lines or transiting in the boarding history corresponding to the boarding log ID (if not applicable, it will be Null) - Date and time of passing through the ticket gate: Date and time information of the ticket gate when transferring between lines or transiting in the boarding history corresponding to the boarding log ID (if not applicable, it will be Null) - Exit ticket gate ID: Identification information of the ticket gate used at the exit station in the boarding history corresponding to the boarding log ID - Date and time of exiting the train: Date and time of exiting the train at the station where the passenger exited the train in the boarding history corresponding to the boarding log ID
[0212] In the travel candidate DB stored in the storage unit 302 of the server 30, a ride log ID is stored instead of a travel log ID. In the determination result DB stored in the storage unit 302 of the server 30, the IC card ID is stored instead of the vehicle-mounted device ID. In the complementation result DB stored in the storage unit 302 of the server 30, the IC card ID is stored instead of the vehicle-mounted device ID.
[0213] The server 30 executes the process from acquiring the communication log to completing the user information in the same manner as the process shown in Fig. 12 in the embodiment described above. At this time, the server 30 acquires the ride details instead of "acquiring the usage details" in step S32. Moreover, the server 30 specifies the movement information corresponding to the ride log, instead of "specifying the movement information corresponding to the driving log" in step S33. Through this series of processes, in the determination result DB, the IC card ID of the IC card ticket and the user ID of the user terminal 10 are linked together. In addition, in the complementation result DB, the trip group ID and the IC card ID are linked together.
[0214] As described above, the server 30 according to the modified example can link the IC card ID of the IC card ticket of the rail transport facility to the user ID registered as the user of the user terminal 10, and can estimate the rail transport facilities that the user uses on a daily basis. Therefore, it is possible to obtain a sufficient number of samples of the rail transport facility usage history that can become meaningful information regarding the use of the rail transport facility.
[0215] In the above embodiment, the vehicle-mounted device ID is used as the vehicle identification information, but this is not limiting. For example, identification information capable of identifying a vehicle body may be used as the vehicle identification information.
[0216] In the above embodiment, the generation module 3033 of the server 30 generates the trip data from the acquired communication log, but this is not the only possible example. The server 30 may acquire the trip data by accepting trip data generated in an external server.
[0217] In addition, the trip data may be generated with a data structure different from that of the embodiment described above. For example, in the people flow node DB shown in Fig. 7C, the result of traffic base determination, which is position matching with a traffic base, may be linked to each people flow node. In this case, the traffic base determination is performed, for example, by the following process.
[0218] The generation module 3033 of the server 30 performs a matching process with a transportation hub or a transportation link for each of the people flow nodes defined in step S31 shown in Fig. 12. Specifically, the generation module 3033 estimates the transportation hub or the transportation link to which the people flow node corresponds by determining whether the positional relationship between the position of the people flow node and the positions of the transportation hub and the transportation link stored in the transportation network database 50 is within a predetermined threshold value.
[0219] For example, if there is a road link within 200 m of the people flow node to be evaluated, the generation module 3033 matches the people flow node to the road link with the shortest distance. Furthermore, if the people flow node is located within an airport area, the generation module 3033 matches the people flow node to the airport. The value of the threshold used for the determination can be set arbitrarily. The generation module 3033 records information about the transportation hub estimated by such a matching process in the people flow node DB in association with the people flow node ID.
[0220] In the system 1, the information on the traffic base for the people flow node may be used to compare with the travel log obtained from the expressway usage details. In this case, a process of selecting multiple travel candidate data may be performed by determining whether or not the entrance interchange and exit interchange of the expressway in the travel log match with the traffic base (corresponding interchange) estimated by the traffic base determination for the people flow node.
[0221] In addition, in the case where the travel log data includes information on the transit facility ID indicating the transfer point and the transit date and time, the system 1 may evaluate the degree of match between the position and time of the transfer point and the transit node and the transit time in the travel data. This increases the number of matching points, thereby improving the accuracy of the determination.
[0222] Although the preferred embodiment of the present disclosure has been described above, the present disclosure is not limited to the specific embodiment, and the present disclosure includes the invention described in the claims and its equivalents. In addition, the configurations of the devices described in the above embodiments and modifications can be appropriately combined as long as no technical contradiction occurs. Furthermore, 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.
[0223] (Additional Note) The following additional notes are provided regarding the embodiments of the present invention.
[0224] (Appendix 1) A program to be executed by a system having a computer equipped with a processor, The program causes the processor to A step of acquiring 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 (step S31); A step of acquiring an ETC usage statement (step S32) showing the usage record of the expressway, including information on the location and passing time of the interchange used, and information on the vehicle type; A step of comparing the usage details and the travel data to identify the travel data corresponding to the travel log indicated by the usage details (step S33); and a step (step S34) of complementing corresponding user information for a travel log for which corresponding travel data has not been identified, by referring to a combination of the travel log and the travel data for which a correspondence has already been identified.
[0225] (Appendix 2) In the step of identifying the movement data (step S33), A step of selecting a plurality of candidate travel data which are candidates for travel data corresponding to the vehicle's travel log from among the plurality of travel data based on the degree of agreement of the passing times of the passing nodes in the usage details and the travel data (step S331); The program described in Appendix 1 executes a step (step S332) of identifying the user's travel data corresponding to the travel log indicated by a specific usage detail by comparing the selected group of travel candidate data with the travel log indicated by multiple usage details for one or more vehicles.
[0226] (Appendix 3) In the step of selecting a plurality of candidate data for movement (step S331), The program according to claim 2, wherein, when the movement data passes through passing nodes adjacent to the entrance interchange and exit interchange of a highway in the driving log shown in the usage details, if the passing times of the entrance interchange and exit interchange shown in the usage details and the passing times of each passing node shown in the movement data are within a predetermined time difference, the movement data is selected as candidate movement data.
[0227] (Appendix 4) The program according to claim 3, wherein the time difference is set to different values depending on differences in roadside conditions at the entrance interchange and the exit interchange.
[0228] (Appendix 5) In the step of identifying user movement data (step S33), The program according to claim 2, wherein when a driving log indicated by multiple usage details for one vehicle matches multiple travel candidate data for the same user, the multiple travel candidate data are identified as the travel data corresponding to the driving log indicated by the multiple usage details.
[0229] (Appendix 6) In the step of identifying user movement data (step S33), The program according to claim 2, wherein when a driving log indicated by a plurality of usage details relating to a plurality of vehicles matches a plurality of movement candidate data for a plurality of users, each of the plurality of movement candidate data is identified as corresponding movement data for each of the driving logs indicated by the plurality of usage details according to the time difference between the passing times.
[0230] (Appendix 7) In the step of identifying user movement data (step S33), The program of claim 2, wherein when a driving log indicated in a usage detail for the same section on the same day matches travel candidate data for one or more users, the travel candidate data for the one or more users is identified as the travel data corresponding to the driving log indicated in the usage detail.
[0231] (Appendix 8) In the step of identifying user movement data (step S33), The program of claim 2, wherein when the driving log indicated by one or more usage details for the same section matches the travel candidate data for one or more users, the travel candidate data for the one or more users is identified as the travel data corresponding to the driving log indicated by the usage details according to the time difference between the passage times.
[0232] (Appendix 9) In the step of complementing the user information (step S33), the processor further The program described in claim 1, wherein when the first user information is already linked to vehicle identification information relating to two usage details that are arranged in chronological order for a single vehicle, the first user information is supplemented to the vehicle identification information relating to a usage detail that is located between the two usage details in the chronological order.
[0233] (Appendix 10) In the step of complementing the user information (step S33), the processor further The program described in claim 1, wherein when the second user information is already linked to vehicle identification information relating to more than half of multiple usage details for the same day related to a single vehicle, the second user information is supplemented to the vehicle identification information relating to other usage details for the same day.
[0234] (Appendix 11) In the step of complementing the user information (step S33), the processor further The program described in claim 1, wherein when third user information is already linked to vehicle identification information relating to two chronologically arranged usage details among multiple usage details for the same day related to a single passenger vehicle, the third user information is supplemented to the vehicle identification information relating to the usage details that are located between the two usage details in the chronological order.
[0235] (Appendix 12) The processor further comprises: The program according to claim 1, which executes a step of creating an OD table showing in tabular form the amount of travel for each start point and end point for each vehicle type, using information related to the vehicle type and information on the start point and end point in trip data, which is a collection of travel data of a user linked to the vehicle.
[0236] (Appendix 13) The processor further comprises: 2. The program according to claim 1, further comprising a step of estimating a vehicle used in movement data when the user moved on a general road by using vehicle identification information linked to user information.
[0237] (Appendix 14) In the step of estimating the vehicle used, The program according to claim 13, wherein, when the general road travel data to be evaluated constitutes a single trip data together with expressway travel data for the same user, if there is only one vehicle linked to the expressway travel data for the same day, the program estimates that vehicle as the vehicle used in the general road travel data to be evaluated, and if there are multiple vehicles linked to the expressway travel data for the same user, the program estimates the vehicle used more frequently as the vehicle used in the general road travel data to be evaluated.
[0238] (Appendix 15) In the step of estimating the vehicle used, The program described in claim 13, wherein, in a case where the general road travel data to be evaluated does not constitute a single trip data set together with the expressway travel data, if there is only one vehicle linked to the expressway travel data for the same user in the same month, the program estimates that vehicle as the vehicle used in the trip data to be evaluated, and if there are multiple vehicles linked to the expressway travel data for the same user in the same month, the program estimates that the vehicle used most frequently within the same month as the vehicle used in the trip data to be evaluated.
[0239] (Appendix 16) A method executed by a system having a computer with a processor, comprising: The program is executed by the processor. acquiring movement data that is generated by arranging the location information of the mobile terminal according to the communication time and indicates a movement route of a user carrying the mobile terminal; A step of acquiring details of ETC usage indicating the usage record of the expressway, including information on the location and passing time of the interchange used, and information on the type of the vehicle; A step of comparing the usage details and the movement data to identify the user's movement data corresponding to the driving log indicated by the usage details; The method includes a step of complementing corresponding user information for a travel log for which corresponding travel data is not identified, by referring to a combination of the travel log and the travel data for which a correspondence has already been identified.
[0240] (Appendix 17) A system having a computer with a processor, The program is executed by the processor. A means for acquiring movement data which is created by arranging the location information of the mobile device according to the communication time and which indicates the movement route of the user carrying the mobile device; A means for acquiring details of ETC usage, which shows the usage record of an expressway and includes information on the location and passing time of interchanges used, and information on the vehicle type; A means for identifying the user's travel data corresponding to the driving log indicated by the usage details by comparing the usage details with the travel data; The system includes a means for complementing user information corresponding to a travel log for which corresponding travel data is not specified, by referring to a combination of the travel log and the travel data for which a correspondence has already been specified.
[0241] (Appendix 18) A program to be executed by a system having a computer equipped with a processor, The program causes the processor to acquiring movement data that is generated by arranging the location information of the mobile terminal according to the communication time and indicates a movement route of a user carrying the mobile terminal; obtaining a ticket receipt for an IC card showing the use of rail transport facilities, the ticket receipt including information on the station locations and ticket receipt times at which the passenger boarded and disembarked, and information on the passenger; A step of comparing the ticket gate details and the movement data to identify the user's movement data corresponding to the boarding log indicated by the ticket gate details; The program executes a step of complementing corresponding user information for a ride log for which corresponding movement data is not specified, by referring to a combination of the ride log and movement data for which a correspondence has already been specified.
[0242] (Appendix 19) A method for causing a system having a computer with a processor to execute the method, The method includes a processor: acquiring movement data that is generated by arranging the location information of the mobile terminal according to the communication time and indicates a movement route of a user carrying the mobile terminal; obtaining a ticket receipt for an IC card showing the use of rail transport facilities, the ticket receipt including information on the station locations and ticket receipt times at which the passenger boarded and disembarked, and information on the passenger; A step of comparing the ticket gate details and the movement data to identify the user's movement data corresponding to the boarding log indicated by the ticket gate details; The method includes a step of complementing corresponding user information for a ride log for which corresponding movement data is not identified, by referring to a combination of the ride log and movement data for which a correspondence has already been identified.
[0243] (Appendix 20) A system for causing a system having a computer with a processor to execute the program, The program is executed by the processor. a module for acquiring movement data that is created by arranging the location information of the mobile device along the communication time and indicates the movement route of the user carrying the mobile device; a module for obtaining IC card ticket details, which indicate the use of rail transport facilities and includes information on the station locations and ticket gate times at which passengers board and alight, and information on the passenger; a module for identifying user movement data corresponding to the boarding log indicated by the ticket gate details by comparing the ticket gate details and the movement data; The system includes a module that complements user information corresponding to a ride log for which corresponding movement data is not specified by referring to a combination of the ride log and movement data for which a correspondence has already been specified. [Explanation of symbols]
[0244] 1. People flow analysis system 10 User terminal 30 Data Processing Server 40 Base Station Database 50 Transportation Network Database 80 Network 81 Fixed positioning equipment
Claims
1. A program to be executed by a system having a computer equipped with a processor, The program causes the processor to: acquiring movement data that is generated by arranging location information of a mobile terminal according to a communication time and indicates a movement route of a user carrying the mobile terminal; A step of acquiring ETC usage details indicating the usage record of the expressway, including information on the location and passing time of the interchange used, and information on the type of vehicle traveling; comparing the usage details with the travel data to identify the travel data corresponding to the travel log indicated by the usage details, and linking vehicle identification information of the travel log with a user ID of the travel data; A program that executes a step of complementing corresponding user information for the driving log for which corresponding movement data has not been identified, by referring to a combination of the driving log and the movement data for which a correspondence has already been identified.
2. In the step of identifying the movement data, selecting a plurality of candidate travel data which are candidates for travel data corresponding to a travel log of a vehicle from among the plurality of travel data based on a degree of agreement between the travel time of a passing node in each of the usage details and the travel data; The program of claim 1, further comprising: a step of comparing the selected group of travel candidate data with travel logs indicated by a plurality of the usage details for one or more vehicles, thereby identifying the user's travel data that corresponds to the travel log indicated by a particular one of the usage details.
3. In the step of selecting a plurality of pieces of movement candidate data, The program according to claim 2, wherein, when the travel data passes through passing nodes adjacent to the entrance interchange and exit interchange of the expressway in the driving log shown in the usage details, the travel data is selected as the candidate travel data if the passing times of the entrance interchange and exit interchange shown in the usage details and the passing times of each passing node shown in the travel data are within a predetermined time difference.
4. The program according to claim 3 , wherein the time difference is set to a different value depending on differences in roadside conditions at the entrance interchange and the exit interchange.
5. In the step of identifying the user's movement data, The program according to claim 2, wherein when the driving logs indicated by the multiple usage details for one vehicle match multiple travel candidate data for the same user, the multiple travel candidate data are identified as the travel candidate data corresponding to the driving logs indicated by the multiple usage details.
6. In the step of identifying the user's movement data, The program of claim 2, wherein when the driving logs indicated by the multiple usage details for multiple vehicles match the multiple travel candidate data for multiple users, each of the multiple travel candidate data is identified as the corresponding travel candidate data for each of the driving logs indicated by the multiple usage details according to the time difference between the passing times.
7. In the step of identifying user movement data, The program of claim 2, wherein when a driving log indicated in 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 candidate data for one or more users is identified as the travel candidate data corresponding to the driving log indicated by the usage details.
8. In the step of identifying the user's movement data, The program of claim 2, further comprising: a program for identifying, when the driving log indicated by one or more of the usage details for the same section matches the travel candidate data for one or more users, the travel candidate data for one or more users as the travel candidate data corresponding to the driving log indicated by the usage details according to the time difference between the passage times.
9. The step of complementing the user information further comprises the processor: The program described in claim 1, wherein when first user information is already linked to vehicle identification information relating to two usage details that are arranged in chronological order for a single vehicle, the first user information is supplemented with the vehicle identification information relating to the usage details that are located between the two usage details in the chronological order.
10. The step of complementing the user information further comprises the processor: The program described in claim 1, wherein when second user information is already linked to vehicle identification information relating to more than half of the multiple usage details for the same day relating to a single vehicle, the second user information is supplemented to the vehicle identification information relating to the other usage details for the same day.
11. The step of complementing the user information further comprises the processor: The program described in claim 1, wherein when third user information is already linked to vehicle identification information relating to two of the multiple usage details for the same day related to a single passenger vehicle that are arranged in chronological order, the third user information is supplemented to the vehicle identification information relating to the usage details that are located between the two usage details in the chronological order.
12. The processor further comprises: The program according to claim 1 executes a step of creating an OD table showing in tabular form the amount of travel for each start point and end point for each vehicle type, using information regarding the vehicle type and information regarding the start point and end point in trip data, which is a collection of the travel data of the user linked to the vehicle.
13. The processor further comprises: The program according to claim 1 , further comprising: a step of estimating a vehicle used in the movement data when the user moved on a general road by using the vehicle identification information linked to the user information.
14. In the step of estimating the vehicle used, The program described in claim 13, wherein when the general road travel data to be evaluated constitutes a single trip data set together with expressway travel data, if there is only one vehicle linked to the expressway travel data for the same user on the same day, the program estimates that vehicle as the vehicle used in the general road travel data to be evaluated, and if there are multiple vehicles linked to the expressway travel data for the same user, estimates that vehicle as the vehicle used in the general road travel data to be evaluated, and if there are multiple vehicles linked to the expressway travel data for the same user, estimates that the vehicle used more frequently as the vehicle used in the general road travel data to be evaluated.
15. In the step of estimating the vehicle used, The program described in claim 13, wherein, in a case where the general road travel data to be evaluated does not constitute a single trip data set together with the expressway travel data for the same user, if there is only one vehicle linked to the expressway travel data within a specified period, the vehicle is estimated to be the vehicle used in the trip data to be evaluated, and if there are multiple vehicles linked to the expressway travel data for the same user, the vehicle that was used most frequently within the specified period is estimated to be the vehicle used in the trip data to be evaluated.
16. A method executed by a system having a computer with a processor, comprising: The method further comprises the processor: acquiring movement data that is generated by arranging location information of a mobile terminal according to a communication time and indicates a movement route of a user carrying the mobile terminal; A step of acquiring ETC usage details indicating the usage record of the expressway, including information on the location and passing time of the interchange used, and information on the type of vehicle traveling; A step of comparing the usage details and the movement data to identify the user's movement data corresponding to the driving log indicated by the usage details, and linking vehicle identification information of the driving log with a user ID of the movement data; A method for supplementing the driving log for which corresponding movement data has not been identified with relevant user information by referring to a combination of the driving log and the movement data for which a correspondence has already been identified.
17. A system having a computer with a processor, The system further comprises: A means for acquiring movement data that is created by arranging location information of a mobile terminal according to communication time and indicates a movement route of a user carrying the mobile terminal; A means for acquiring details of ETC usage, which shows the usage record of an expressway and includes information on the location and passing time of interchanges used, and information on the type of vehicle used; A means for identifying the user's movement data corresponding to a driving log indicated by the usage details by comparing the usage details with the movement data, and linking vehicle identification information of the driving log with a user ID of the movement data; A system comprising: a means for complementing corresponding user information for a traveling log for which corresponding traveling data has not been identified, by referring to a combination of the traveling log and the traveling data for which a correspondence has already been identified.
18. A program to be executed by a system having a computer equipped with a processor, The program causes the processor to: acquiring movement data that is generated by arranging location information of a mobile terminal according to a communication time and indicates a movement route of a user carrying the mobile terminal; obtaining a ticket receipt for an IC card ticket, the ticket receipt indicating the use of rail transport facilities and including information on the station locations and ticket receipt times at which the passenger boarded and disembarked, and information on the passenger; A step of identifying the user's movement data corresponding to the boarding log indicated by the ticket gate details by comparing the ticket gate details with the movement data, and linking identification information of the IC card ticket in the boarding log with a user ID of the movement data; The program executes a step of complementing the corresponding user information for the ride log for which corresponding movement data has not been identified by referring to the combination of the ride log and the movement data for which a correspondence has already been identified.
19. A method for causing a system having a computer with a processor to execute the method, The method further comprises the processor: acquiring movement data that is generated by arranging location information of a mobile terminal according to a communication time and indicates a movement route of a user carrying the mobile terminal; obtaining a ticket receipt for an IC card ticket, the ticket receipt indicating the use of rail transport facilities and including information on the station locations and ticket receipt times at which the passenger boarded and disembarked, and information on the passenger; A step of identifying the user's movement data corresponding to the boarding log indicated by the ticket gate details by comparing the ticket gate details with the movement data, and linking identification information of the IC card ticket in the boarding log with a user ID of the movement data; The method includes a step of complementing the user information for the ride log for which corresponding movement data is not identified by referring to a combination of the ride log and the movement data for which a correspondence has already been identified.
20. A system for causing a system having a computer with a processor to execute the program, The system further comprises: a module for acquiring movement data that is generated by arranging location information of a mobile device according to communication time and indicates a movement route of a user carrying the mobile device; a module for acquiring details of an IC card ticket, which indicates the use of rail transport facilities and includes information on the station locations and ticket gate times at which a passenger boards and disembarks, and information on the passenger; a module for identifying the user's movement data corresponding to the boarding log indicated by the ticket gate details by comparing the ticket gate details with the movement data, and linking the identification information of the IC card ticket in the boarding log with the user ID of the movement data; A system comprising: a module that complements corresponding user information for a ride log for which corresponding movement data has not been identified by referring to a combination of the ride log and the movement data for which a correspondence has already been identified.
Citation Information
Patent Citations
Information processor and information processing method
JP2021086386A
Charging management system, charging management method, and charging management program
JP2021129459A
Road traffic investigation system
JP2017138861A
