JP2021082230A - Travel plan management system - Google Patents

Abstract

To provide a travel plan management system that, when an obstacle occurs, performs appropriate support for a user who is traveling.SOLUTION: A travel plan management system, when a management server communicable with a user's portable terminal device registers the user's travel plan (S1) and receives obstacle information after the start of a travel and before the end of the travel in the travel plan (S4), determines whether the travel plan can be continued based on the obstacle information (YES in S4), when determining that the travel plan cannot be continued (NO in S6), derives a homecoming plan from the user's current position to the user's home (S7), and transmits the homecoming plan to the portable terminal device (S8).SELECTED DRAWING: Figure 2

Description

The present invention relates to a travel plan management system.

A travel plan creation support device creates a travel plan from information input by the user and graphically presents it to the user (see, for example, Patent Document 1).

In addition, one travel arrangement system re-proposes another travel plan that avoids the effects of the disaster or accident when a disaster or accident occurs during the trip (see, for example, Patent Document 2).

JP-A-2010-146129 Japanese Unexamined Patent Publication No. 2004-054563

In the above-mentioned travel arrangement system, if a disaster or accident occurs during the trip, the travel plan is re-proposed on the assumption that the trip will be continued, but the user considers the scale of obstacles such as disasters and accidents. However, if you want to stop the trip immediately during the trip, you may not be able to provide appropriate support to the user during the trip.

The present invention has been made in view of the above problems, and an object of the present invention is to obtain a travel plan management system that provides appropriate support to a user in the middle of a trip when a failure occurs.

The travel plan management system according to the present invention includes a management server capable of communicating with a user's mobile terminal device. When the management server (a) registers the travel plan of the user and (b) receives the trouble information after the start of the trip in the travel plan and before the end of the trip, the travel plan continues based on the trouble information. If it is determined whether or not it is possible, (c) if it is determined that the travel plan cannot be continued, a return plan from the user's current position to the user's home is derived, and (d) the return plan is described as described above. Send to the mobile terminal device.

According to the present invention, it is possible to obtain a travel plan management system that provides appropriate support to a user during a trip when a failure occurs.

The above or other objects, features and advantages of the present invention will be further clarified from the following detailed description along with the accompanying drawings.

FIG. 1 is a block diagram showing a configuration of a travel plan management system according to an embodiment of the present invention. FIG. 2 is a flowchart illustrating the operation of the travel plan management system shown in FIG. FIG. 3 is a diagram illustrating a return home plan derived in the travel plan management system shown in FIG.

Hereinafter, embodiments of the present invention will be described with reference to the drawings.

Embodiment 1.

FIG. 1 is a block diagram showing a configuration of a travel plan management system according to an embodiment of the present invention. The travel plan management system shown in FIG. 1 includes a management server 1 and one or a plurality of mobile terminal devices 2.

The management server 1 is connected to the network 3 and can perform data communication with the mobile terminal device 2 of each user connected to the network 3.

The network 3 is a WAN (Wide Area Network) such as the Internet, a LAN (Local Area Network), or the like.

The mobile terminal device 2 is a terminal device (smartphone or the like) carried by each user, and is connected to the network 3 via a mobile phone communication network or connected to the network 3 via a public wireless LAN. It is possible.

The mobile terminal device 2 includes a display device such as a liquid crystal display that displays various screens, an input device that accepts user operations, an input device such as a mouse and a keyboard, and a position detection device that detects the current position by GPS (Global Positioning System) or the like. Be prepared.

For example, the mobile terminal device 2 has a built-in computer, and an application that functions as a user interface, a communication processing unit that communicates with the management server 1, and the like is installed in the computer.

The management server 1 shown in FIG. 1 manages the travel plans of each user. The management server 1 includes a communication device 11, a storage device 12, and an arithmetic processing unit 13.

The communication device 11 is a device such as a network interface that can be connected to the network 3.

The storage device 12 is a non-volatile storage device such as a hard disk drive, an SSD (Solid State Drive), or a disk array.

The arithmetic processing device 13 includes a computer including a CPU (Central Processing Unit), a ROM (Read Only Memory), a RAM (Random Access Memory), and the like, loads various programs into the RAM, executes them, and operates as various processing units. ..

A server program (not shown) is stored in the storage device 12. Further, the storage device 12 stores the user data 21 and the travel plan data 22.

The user data 21 includes a user ID, user personal information (name, home address, telephone number, emergency contact information, etc.), a travel plan ID of a travel plan registered by the user, and the like. Further, the user data 21 may include current position information indicating the current position of the user, which is repeatedly updated during the trip.

For each travel plan, the travel plan data 22 includes a travel plan ID, a user ID that registered the travel plan, location information of the home and one or more waypoints, and from home to home via the one or more waypoints. Includes route information indicating the return route and the means of transportation of the route between points (car, rail, airplane, ship, walk, bicycle, etc.), schedule information indicating the departure date and time and arrival date and time of each point (home or waypoint), etc. ..

The departure date and time from home is the travel start date and time, and the arrival date and time at home is the travel end date and time.

By executing the above-mentioned server program, the arithmetic processing unit 13 operates as a front-end processing unit 31, a travel plan management unit 32, a failure information acquisition unit 33, a homecoming plan proposal unit 34, and a database server 35.

The front-end processing unit 31 uses the communication device 11 to perform data communication with the mobile terminal device 2 using a predetermined protocol, and (a) receives various requests and transmits a response corresponding to the requests. , (B) Send various requests and receive a response corresponding to the request, and (c) Send a notification.

For example, the front-end processing unit 31 has a built-in web server, and the mobile terminal device 2 has a built-in application or web browser described above, and the web is used by using the application or web browser described above. Access the server. In that case, the front-end processing unit 31 transmits screen data to the mobile terminal device 2 that has accessed according to HTTP (Hyper Text Transfer Protocol), and causes the mobile terminal device 2 to display the screen. The screen data is described in HTML (HyperText Markup Language) or the like. Further, when the mobile terminal device 2 detects a user operation on the screen, the mobile terminal device 2 transmits a request based on the user operation or the like to the front-end processing unit 31 by the above-mentioned application or web browser. In this way, the mobile terminal device 2 functions as a user interface in the system.

The travel plan management unit 32 uses (a) the front-end processing unit 31 and the communication device 11, and travel plan information (the above-mentioned point information, route information, schedule information, etc.) designated by the user from the mobile terminal device 2 or the like. ) Is received, (b) the travel plan information is registered in the travel plan data 22 on the database server 35 as a travel plan, and (c) the travel plan is changed in the return home plan described later as necessary. Further, the travel plan management unit 32 periodically acquires the current position of the user from the mobile terminal device 2 and registers it in the user data 21 during the period from the start of the trip to the end of the trip in the travel plan.

Using the communication device 11, the failure information acquisition unit 33 uses the communication device 11, weather conditions, weather forecasts, operation status of public transportation means (including accident information of public transportation means), disaster information (information such as typhoons and large earthquakes), Acquire incident information such as demonstrations and violent incidents as failure information from a predetermined external server. The failure information includes the type of failure, the area where the failure occurred, the date and time when the failure occurred, and the like.

When the failure information acquisition unit 33 receives the failure information for each travel plan registered by each user, (a) after the start of the trip in the travel plan and before the end of the trip, the return plan proposal unit 34 provides the failure information. Based on this, it is determined whether or not the travel plan can be continued, and (b) if it is determined that the travel plan of a user cannot be continued, the return plan from the user's current position to the user's home is derived, and ( c) The homecoming plan and failure information are transmitted to the user's mobile terminal device 2 by the communication device 11. When the user's mobile terminal device 2 receives the homecoming plan and the failure information, it immediately displays it to the user.

The current position of the user may be the latest user's position recorded in the user data 21, or may be acquired from the user's mobile terminal device 2 when deriving the homecoming plan. Good.

Specifically, when the failure information acquisition unit 33 receives the failure information, the homecoming plan proposal unit 34 first creates a database of the travel plan, which is the state after the start of the trip and before the end of the trip, from the travel plan data 22. For each of the travel plans extracted by the server 35, the travel plan is created based on the type of failure indicated by the failure information, the area where the failure occurred, the date and time when the failure occurred, and the route information and schedule information of the travel plan. Determine if it is possible to continue.

For example, the homecoming plan proposal unit 34 specifies the expected failure end date and time corresponding to the type of failure when the failure information does not include the estimated failure end date and time. The estimated failure end date and time corresponding to the type of failure is specified based on the data (table or the like) that is implemented in advance and indicates the correspondence between the two. Then, if any point (waypoint) in the travel plan is included in the area where the disability occurs during the period from the present time to the expected date and time of the end of the disability, it is determined that the travel plan cannot be continued.

When deriving the homecoming plan, the homecoming plan proposal unit 34 derives and derives one or more routes (including transportation means) and schedule from the user's current position to the user's home by an existing method. Of one or more routes, the route passing through the area where the failure occurs is excluded, and the remaining at least one route and the schedule for the route are set as the return plan.

As described above, in this embodiment, the registered travel plan includes the location information indicating the user's home, and the management server 1 determines the current position detected by the position detection device of the user's mobile terminal device 2. , Acquire as the user's current position, and derive a return plan by a route that avoids the area where the failure indicated by the failure information is currently occurring.

In this embodiment, the homecoming plan proposal unit 34 sends a homecoming plan approval request to the mobile terminal device 2 together with the homecoming plan, and the mobile terminal device 2 displays the homecoming plan and then the user approves the operation. Is detected, a response indicating approval of the return plan is sent to the management server 1. Then, when the homecoming plan proposal unit 34 receives a response indicating approval of the homecoming plan from the mobile terminal device 2 after (a) transmitting the homecoming plan to the mobile terminal device 2, the travel plan is changed by the homecoming plan. Then, (b) if obstacle information is newly received before the end of the trip in the changed travel plan, it is determined whether or not the travel plan can be continued based on the obstacle information, and (c) the travel plan can be continued. If it is determined that this is not the case, a new homecoming plan from the user's current position to the user's home is derived again, and (d) the new homecoming plan is transmitted to the mobile terminal device 2. After that, until the user arrives at home, a new homecoming plan is similarly derived and presented to the user as needed.

The database server 35 receives various requests according to a protocol such as SQL, and performs database operations on the database including data 21 and 22 according to the requests.

Next, the operation of the travel plan management system will be described. FIG. 2 is a flowchart illustrating the operation of the travel plan management system shown in FIG.

In the management server 1, the travel plan management unit 32 registers the user's travel plan in the travel plan data 22 in response to the request from the user (step S1).

After registering the travel plan, the travel plan management unit 32 periodically arrives at the user's current status until the travel start date and time of the travel plan arrives (step S2) and the travel end date and time of the travel plan arrives (step S5). The user's movement is detected by acquiring the position (step S3).

During that period, when the failure information acquisition unit 33 receives the failure information (step S4), the homecoming plan proposal unit 34 determines whether or not the current travel plan can be continued (step S6), and the current travel plan is changed. When it is determined that it is not possible to continue, the return home plan is derived as described above (step S7), and the return home plan is transmitted to the user's mobile terminal device 2 and presented to the user (step S8). If it is determined that the current travel plan can be continued, the homecoming plan proposal unit 34 does not derive and present the homecoming plan.

After that, when the approval response of the return plan is received from the user's mobile terminal device 2, the travel plan management unit 32 determines that the return plan is applied (step S9), and changes the current travel plan in the return plan. (Step S10). After the change, the same processing (steps S3 to S10) is repeatedly executed until the travel end date and time arrives (step S5). If the user does not approve the return plan and the return plan is not applied, the travel plan will not be changed.

FIG. 3 is a diagram illustrating a return home plan derived in the travel plan management system shown in FIG. For example, as shown in FIG. 3, when the waypoints in the travel plan are points A, B, C, and A, and the user is at point B and an obstacle occurs in the area including point C, points C and A For example, a return plan that allows the user to return home in the shortest time is derived and presented to the user without going through.

As described above, according to the first embodiment, the management server 1 capable of communicating with the user's mobile terminal device 2 registers (a) the user's travel plan, and (b) after the start of the trip in the travel plan. If the obstacle information is received before the end of the trip, it is determined whether or not the travel plan can be continued based on the obstacle information. (C) If it is determined that the travel plan cannot be continued, the user's current position is used. The return plan to the user's home is derived, and (d) the return plan is transmitted to the mobile terminal device 2.

As a result, it is possible to cancel the trip in the middle and return home directly according to the return home plan, and appropriate support is provided to the user in the middle of the trip in the event of a failure.

Embodiment 2.

In the travel plan management system according to the second embodiment, the return plan proposal unit 34 of the management server 1 considers the change prediction based on the change prediction of the failure occurrence area indicated by the above-mentioned failure information, and considers the change prediction. Is derived.

The homecoming plan proposal unit 34 determines whether or not the area where the failure occurs fluctuates based on the type of failure, and if it determines that the area where the failure occurs fluctuates, predicts the change in the area where the failure occurs. Or get it from an external server. For example, when the failure is a typhoon, the area where the failure occurs fluctuates, and the above-mentioned fluctuation prediction is obtained from an external server (such as an enemy information server that provides typhoon route prediction).

For example, the homecoming plan proposal unit 34 identifies the failure-occurring area at each time point in the homecoming plan based on the fluctuation prediction, and compares the identified failure-occurring area with the user's position in the homecoming plan at that time. , If the user's location is included in the specified failure area, the return plan is excluded.

For example, in the case of a railway equipment failure, the failure area does not change (that is, the failure does not move or spread to another area), so the homecoming plan proposal unit 34 moves to the current failure area. Derive a homecoming plan based on this.

Since other configurations and operations of the travel plan management system according to the second embodiment are the same as those of the first embodiment, the description thereof will be omitted.

As described above, according to the second embodiment, since the fluctuation prediction of the area where the failure occurs is taken into consideration, a more appropriate return home plan is derived and presented to the user.

It should be noted that various changes and modifications to the above-described embodiments will be apparent to those skilled in the art. Such changes and modifications may be made without departing from the intent and scope of the subject and without diminishing the intended benefits. That is, such changes and amendments are intended to be included in the claims.

The present invention is applicable to, for example, a travel plan management system.

1 Management server 2 Mobile terminal device 3 Network

Claims (5)

Equipped with a management server that can communicate with the user's mobile terminal device
When the management server (a) registers the travel plan of the user and (b) receives the trouble information after the start of the trip in the travel plan and before the end of the trip, the travel plan continues based on the trouble information. If it is determined whether or not it is possible, (c) if it is determined that the travel plan cannot be continued, a return plan from the user's current position to the user's home is derived, and (d) the return plan is described as described above. Sending to a mobile terminal device,
A travel plan management system featuring. The travel plan includes location information indicating the user's home.
The management server acquires the current position detected by the position detection device of the mobile terminal device of the user as the current position of the user.
The travel plan management system according to claim 1. The travel plan management system according to claim 1, wherein the management server derives the return plan by a route avoiding the area where the failure indicated by the failure information is currently occurring. The trip according to claim 1 or 3, wherein the management server derives the homecoming plan in consideration of the fluctuation prediction based on the fluctuation prediction of the failure occurrence area indicated by the failure information. Plan management system. When (a) the management server receives a response indicating approval of the homecoming plan from the mobile terminal device after transmitting the homecoming plan to the mobile terminal device, the management server changes the travel plan in the homecoming plan. (B) If the obstacle information is received before the end of the trip in the changed travel plan, it is determined whether or not the travel plan can be continued based on the obstacle information, and (c) the travel plan cannot be continued. If it is determined that, a new homecoming plan from the user's current position to the user's home is derived again, and (d) the new homecoming plan is transmitted to the mobile terminal device. The travel plan management system according to any one of claims 4.

Images