JP2006048260A - Itinerary preparation support method and system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To prepare an itinerary with a focus on popular sightseeing spots without placing a burden on a person who prepares the itinerary. <P>SOLUTION: An itinerary preparation support device 10 analyzes actually popular sightseeing spots based on the behavioral history of travellers collected through mobile terminals or the like, and prepares an itinerary based on it. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a technology for supporting creation of a travel plan.

  Conventionally, when a travel plan is generated, a travel plan is created by combining knowledge possessed by a plan creator and information obtained through marketing. As a system to support these travel planners, there was a content-based system that provided abundant content to travel planners by creating a database of travel destinations, means of transportation, and inns at various locations. However, these were intended to broaden the choices of travel creators, and ultimately the travel planners had to pick them up and assemble the trip. For this reason, in order to solve these problems, a system is being studied in which static information such as customer attributes, travel attributes, and keywords registered in advance is accessed and a plan more suitable for the user is recommended.

  In addition, there exists a technique etc. which were described in patent document 1, for example as a thing relevant as this kind of technique.

JP 2002-245132 A

  The above-described conventional travel plan creation support method has the following problems. In the conventional travel plan creation support method, the following two problems occur, and an optimal plan cannot always be generated.

  The first problem is that since a plan is created based on static information, a plan that is actually sold at that time cannot be directly generated. In order to generate a more accurate plan, the person in charge of creating a travel plan must always register the latest information, resulting in a large amount of work for the person in charge of creating the travel plan. For example, if a popular travel location is newly created, a plan that includes a popular travel location will not be generated at the time of plan generation unless the information is entered by the plan creator, which is not suitable as a recommended plan for travelers. You might end up missing out on a business opportunity.

  The second problem is that actions other than logic set in the system cannot be analyzed, and plans other than certain logic cannot be generated. For example, for travelers who like visiting temples, the logic of including popular temples in the plan can be realized, but since there is no actual data feedback, users who like temples actually sushi after visiting temples It is not possible to find relevant behavioral logic such as many people who eat and automatically reflect it in the plan. As a result, if the knowledge of the person in charge of plan creation is immature, the travel information and the plan setting logic are also incomplete, and an appropriate plan cannot always be generated.

  The present invention is characterized by a technique for analyzing a travel spot that is actually popular based on an action history of a traveler collected via a mobile terminal or the like, and creating a travel plan based on the analysis.

  According to the present invention, since the travel plan is generated from the actual behavior of the traveler, it is possible to easily create a popular plan without knowledge of the location and purpose of the travel. Further, the travel plan creator does not need to apply a work load because the plan is automatically generated only by inputting the attribute of the target traveler and the attribute of the travel plan.

  Hereinafter, an embodiment of a method for automatically generating a travel plan using information acquired from a mobile terminal held by a traveler will be described in detail.

  In this embodiment, from the mobile terminal owned by the traveler who is traveling on the free plan, the location information that the traveler has acted, the time information at that time and the necessary travel information are acquired, and based on that information at that time The configuration and operation of a travel plan creation support apparatus that automatically creates popular travel plans will be described. In the present embodiment, traveler attributes and travel plan attributes are registered in advance in the mobile terminal. In particular, the plan total amount, the number of destinations in the schedule, the number of plan days, the outbound / return traffic departure / arrival as travel plan attributes It is assumed that the land has been transmitted to the travel plan creation support system. In addition, the travel plan creation support system stores travel information and destination information to be provided to travelers, transportation means / movement time between destinations, transportation means / time for the return trip, lunch area / lunch cost, etc. And always updated with the latest information.

  FIG. 1 is a block diagram showing a configuration of a travel plan creation support system according to an embodiment of the present invention. As shown in FIG. 1, the system of this embodiment includes a travel plan creation support device 10.

  The travel plan creation support device 10 is a device that acquires real-time location information of a traveler and automatically generates and displays a recommended travel plan according to information input by a travel plan creation person.

  The travel plan creation support device 10 is a computer having a communication control unit 11, an input device 12, a display device 14, a memory 15, and a control device 40. The control device 40 includes a CPU and a mechanism that performs interface control with the communication control unit 11, the input device 12, the display device 14, and the memory 15. The CPU controls the operation of these mechanisms and devices.

  The communication control unit 11 is a mechanism for acquiring information about a traveler from the mobile terminal 50 or the kiosk terminal 51 and controlling communication with these terminals when providing travel information according to a request from the traveler. The input device 12 is a device for inputting information about a user group and plan attributes that are targets of a travel plan that a travel plan creation person wants to automatically generate. The input device 12 is also used as a device for inputting information when a table related to various travel information is updated to the latest information. The display device 14 is a device for displaying the automatically generated recommendation plan.

  The memory 15 includes a traveler attribute table 16, a travel plan attribute table 17, a travel history table 18, a transmission travel information table 19, a destination table 21, an in-process traffic table 22, a terminal-destination traffic table 23, an accommodation area-purpose For storing a local transportation table 24, an outbound and return transportation means table 25, a lunch area to a destination transportation table 26, a lunch area to a terminal transportation table 27, a lunch area to an accommodation area transportation table 28, and a lunch area table 29. Device. The memory 15 also includes a travel history table corresponding ID extraction program 30, a travel destination analysis table generation program 32, a travel plan mining table generation program 34, a travel destination setting program 35, an outward trip traffic setting program 36, and an accommodation destination setting program 37. The lunch spot setting program 38 and the intra-stroke traffic setting program 39 are stored.

  The traveler attribute table 16 is a table that accumulates information about personal attributes of each traveler, and is generated by receiving information registered by the traveler in the portable terminal 50 or the kiosk terminal 51 via the communication control unit 11. Is done.

  The travel plan attribute table 17 is a table that accumulates attribute information of a travel plan in which each traveler has acted. The travel plan attribute table 17 receives information registered by the traveler in the portable terminal 50 or the kiosk terminal 51 via the communication control unit 11. Is generated by

  The travel history table 18 is a table for accumulating the time of arrival at the travel destination and the location information of the destination for each traveler, and the communication control unit 11 transmits information transmitted from the mobile terminal 50 or the kiosk terminal 51 by the traveler. It is generated by receiving it via.

  The transmission travel information table 19 is a table that accumulates travel information necessary for each traveler together with the time and place where the information is required, and is received from the portable terminal 50 or the kiosk terminal 51 via the communication control unit 11. Generated based on travel information log.

  The destination table 21 is a table for accumulating information on landmarks that are considered to be travel destinations by travelers, and is registered by a travel information maintenance person via the input device 12.

  The intra-stroke traffic table 22 is a table that accumulates information related to traffic between landmarks registered in the destination table 21, and is registered by a travel information maintenance person via the input device 12.

  The terminal-destination traffic table 23 is a table for accumulating information relating to traffic between landmarks registered in the destination table 21 from the terminal station (including airport and port) for outbound and inbound traffic, via the input device 12. Registered by the travel information maintenance staff.

  The accommodation-destination traffic table 24 is a table for accumulating information relating to traffic from the landmark registered in the destination table 21 to the accommodation facility, and is registered by a travel information maintenance person via the input device 12. .

  The outbound / return transportation means table 25 is a table for accumulating information relating to traffic from the departure terminal station of the traveler to the terminal station of the travel destination, and is registered by the person in charge of travel information maintenance via the input device 12.

  The lunch area-destination traffic table 26, the lunch area-terminal traffic table 27, and the lunch area-accommodation area traffic table 28 are information on traffic between landmarks registered in the destination table 21 from the lunch area. This is a table for accumulating information related to traffic between terminal stations for outbound and inbound and outbound traffic, and information related to traffic between lunch and accommodation, and is registered by a travel information maintenance person via the input device 12.

  The lunch table 29 is a table that stores information on restaurants where the traveler is likely to have lunch, and is registered by a travel information maintenance person via the input device 12.

  The travel history table corresponding ID extraction program 30 is a program for extracting an ID of a record having a target traveler attribute and a travel plan attribute from the travel history table 18 and generating an extracted travel history table 511. . Further, the travel history table corresponding ID extraction program 30 counts the destination where the traveler has acted from the extracted travel history table 511 for each hour, and generates the hourly destination use frequency table 541.

  The travel destination analysis table generation program 32 is a program for generating a travel destination analysis table 561 by calculating the usage rate of the destination by time using the hourly destination use frequency table 541. Further, the travel destination analysis table generation program 32 generates the same plan setting number table 641 by combining the destinations accumulated in the extracted travel history table 511 and counting the number of destinations traveling together in the same plan. To do.

  The travel plan mining table generation program 34 is a program for calculating the same plan setting ratio based on the same plan setting frequency table 641 and generating the travel plan mining table 661.

  The travel destination setting program 35 is a program for determining a travel destination in the plan and generating a travel destination setting plan 821.

  The outbound / return traffic setting program 36 is a program for automatically determining information about the outbound / return transportation in the plan and generating the outbound / return traffic setting plan 1011.

  The accommodation place setting program 37 is a program for automatically determining information about the accommodation place in the plan and generating the accommodation place setting plan 1191.

  The lunch spot setting program 38 is a program for automatically determining information on the lunch spot in the plan and generating the lunch spot setting plan 1421.

  The in-stroke traffic setting program 39 is a program for automatically determining information about in-stroke traffic in the plan and generating a recommended travel plan 1561.

  The CPU in the control device 40 implements a travel plan creation support process by executing the program stored in the memory 15.

  FIG. 2 is a diagram illustrating an example of the traveler attribute table 16. Each record of the traveler attribute table 16 has data items such as ID, name, sex, traveler age, number of accompanying persons, and hobbies. The ID is a traveler ID number assigned to each traveler. It is issued when the traveler attribute information is registered in advance. The name is the name of the traveler. The gender is the gender of the traveler. The number of accompanying persons is the number of persons accompanying the trip. A hobby is a hobby that travelers like.

  FIG. 3 is a diagram illustrating an example of the travel plan attribute table 17. Each record of the travel plan attribute table 17 has data items such as an ID, a departure place, an arrival area, the number of staying days, a plan maximum amount, and a plan purpose. ID is a traveler's ID. A departure place is an area where a traveler leaves for a trip. The arrival area is an area where the traveler travels. The number of stays is the number of stays that the traveler stays. The maximum amount of the plan is the total cost excluding the outbound and return transportation costs for the trip. The purpose of the plan is the purpose that the traveler went on a trip.

  FIG. 4 is a diagram illustrating an example of the travel history table 18. Each record of the travel history table 18 has each record of ID, arrival time, and destination. ID is a traveler's ID. The arrival time is the time when the traveler arrives at the destination. The destination is the destination where the traveler actually acted.

  FIG. 5 is a diagram illustrating an example of the destination table 21. Each record of the destination table 21 has a record of destination, average stay time, and usage fee. A destination is a landmark that a traveler is supposed to go as a travel purpose. Average stay time is the average time spent at a landmark. The usage fee is a cost for using the landmark.

  FIG. 6 is a diagram illustrating an example of the intra-stroke traffic table 22. Each record in the in-stroke traffic table 22 has data items of destination 1, destination 2, transportation means, and travel time. The destination 1 and the destination 2 are extracted from landmarks included in the destination table 21. The transportation means is a transportation means when moving between the destination 1 and the destination 2. The travel time is a reference time spent when traveling between the destination 1 and the destination 2.

  FIG. 7 is a diagram illustrating an example of the terminal to destination traffic table 23. Each record of the terminal-destination traffic table 23 has data items of destination 1, terminal, transportation means, and travel time. The destination 1 is extracted from landmarks included in the destination table. The terminal is the terminal station for outbound return traffic. The transportation means is a transportation means when moving between the destination 1 and the terminal. The travel time is a reference time spent when moving between the destination 1 and the terminal.

  FIG. 8 is a diagram illustrating an example of an accommodation place-destination traffic table 24. Each record in the accommodation-destination traffic table 24 has data items for destination, accommodation, transportation, and travel time. The destination is extracted from landmarks included in the destination table. The accommodation area is a list of accommodation areas where the traveler can select accommodation. The transportation means is a transportation means when moving between the destination and the accommodation. The travel time is a reference time spent when moving between the destination and the accommodation.

  FIG. 9 is a diagram illustrating an example of the outbound / return traffic table 25. Each record of the outbound / return transportation means table 25 has data items of a departure terminal, an arrival terminal, a transportation facility, a transportation flight, a departure time, and an arrival time. The departure terminal is a terminal station where a traveler departs on the outward or return journey. The arrival terminal is a terminal station where a traveler arrives on the outward or return journey. A transportation means is a means of transportation when moving between a departure terminal and an arrival terminal. Transportation is a specific name of transportation. The departure time is the time when the transportation flight leaves the departure terminal. The arrival time is the time when the traffic arrives at the arrival terminal.

  FIG. 10 is a diagram illustrating an example of a lunch area to a destination traffic table 26. Each record of the lunch area-destination traffic table 26 has data items of destination, lunch area, transportation means, and travel time. The destination is extracted from landmarks included in the destination table. The lunch spot is extracted from the lunch spot table 29. The transportation means is a transportation means when moving between the destination and the lunch area. The travel time is a rough time spent when moving between the destination and the lunch spot. The lunch area to terminal traffic table 27 is a traffic table in which terminals are set instead of destinations. The lunch area-accommodation area traffic table 28 is a traffic table in which accommodation areas are set instead of destinations.

  FIG. 11 is a diagram illustrating an example of the lunch area table 29. Each record of the lunch place table 29 has data items of a lunch place and an average usage fee. The lunch spot is a list of restaurants where the traveler is supposed to have lunch. The average usage fee is an average usage fee spent at lunch.

  FIG. 12 is a diagram illustrating a schematic processing procedure of the travel plan creation support device 10 that creates the recommended travel plan of the present embodiment. The travel history table corresponding ID extraction program 30 receives the attribute information of the target traveler input from the travel plan creation person via the input device 12 (step 400). The input attribute information includes gender, age range, number of accompanying persons, hobbies, and the like. Next, the travel history table corresponding ID extraction program 30 receives the attribute information of the target travel plan inputted from the travel plan creation person (step 410). The attribute information to be input includes the plan maximum amount, the plan purpose, the number of staying days, the number of plan days, the number of destinations in the schedule of each travel day, the departure and arrival points of the trip.

  Next, the travel history table corresponding ID extraction program 30 refers to the traveler attribute table 16 and the travel plan attribute table 17 to extract a traveler ID that matches both of the input attribute information, and the corresponding ID table 421. Is generated (step 420). FIG. 13 is a diagram illustrating an example of data in the corresponding ID table 421.

  Next, the programs 32 to 39 create a recommended travel plan using the corresponding ID table 421 and display the created travel plan on the display device 14 (step 430). Details thereof will be described with reference to FIG. 14 and subsequent drawings.

  The person in charge of creating a travel plan looks at the created travel plan and determines whether the travel cost, the arrival and departure time, etc. of the plan meet the attribute conditions. The travel history table corresponding ID extraction program 30 returns to step 410 and repeats the above process if it is determined that the plan attribute condition is not met according to the instruction from the person in charge of creating the travel plan (NO in step 440). If it is determined that the plan attribute condition is met, the process ends.

  FIG. 14 is a diagram showing a schematic processing procedure for creating a recommended travel plan in Step 430. First, the travel destination analysis table generation program 32 generates a travel destination analysis table from traveler history information based on the corresponding ID table 421 (step 500). Next, the travel plan mining table generation program 34 creates a travel plan mining table (step 600). Next, the travel destination setting program 35 determines a travel destination and creates a travel destination setting plan (step 700). Next, the outbound / return traffic setting program 36 determines the outbound / return traffic means and creates an outbound / return traffic setting plan (step 900). Next, the accommodation location setting program 37 determines an accommodation location and creates an accommodation location setting plan (step 1100). Next, the lunch spot setting program 38 determines the lunch spot and creates a lunch spot setting plan (step 1200). Finally, the intra-stroke traffic setting program 39 determines the intra-stroke traffic and creates a recommended travel plan (step 1500).

FIG. 15 is a flowchart showing a processing procedure of the travel destination analysis table generation program 32 for creating a travel destination analysis table. The travel destination analysis table generation program 32 extracts a record whose ID matches the ID of the corresponding ID table 421 from the travel history table 18 and generates an extracted travel history table 511 (step 510). FIG. 16 is a diagram illustrating a data example of the extracted travel history table 511. Next, the travel destination analysis table generation program 32 determines whether or not there are remaining records that are not counted in the extracted travel history table 511 (step 520). If there are remaining records, the next record is extracted from the extracted travel history table 511 (step 530), and the number of times of use of the record in the hourly destination use count table 541 that matches the time and destination of the extracted record is one. Is added (step 540). If there is no matching record, a record having the time and destination of the extracted record and the usage count of 1 is added to the hourly destination usage count table 541. FIG. 17 is a diagram showing an example of data in the hourly destination use count table 541. When all the records in the extracted travel history table 511 are counted (step 520 NO), the travel destination analysis table generating program 32 The utilization rate of the destination is calculated for each hour with reference to the different destination use frequency table 541 (step 550). Next, the travel destination analysis table generation program 32 generates a travel destination analysis table 561 that stores the usage rate of the destination by time (step 560). FIG. 18 is a diagram illustrating an example of data in the travel destination analysis table 561.

  FIG. 19 is a flowchart showing a processing procedure of the travel plan mining table generation program 34 for creating a travel plan mining table. The travel plan mining table generation program 34 extracts all the groups of records having the same ID from the extracted travel history table 511 and places them in the memory (step 610). Next, the travel plan mining table generation program 34 creates all combinations of destinations for the extracted records and stores them in the memory (step 620). If there are combinations of the same destination, the same number of the same combinations are stored in the memory. Next, if there is a remaining combination that is not counted (YES in step 630), the travel plan mining table generation program 34 adds 1 to the set number of records having the same destination combination in the same plan set number table 641 (step 640). . If there is no matching record, a record having the extracted combination destination and the set number of times is added to the same plan set number of times table 641. FIG. 20 is a diagram illustrating an example of data in the same plan setting number table 641.

  When all destination combinations on the memory have been counted (step 630 NO), the travel plan mining table generation program 34 refers to the same plan setting frequency table 641 and calculates the same plan setting ratio for each destination combination pattern. (Step 650). Next, the travel plan mining table generation program 34 generates a travel plan mining table 661 that stores the same plan setting ratio for each combination pattern of destinations (step 660). FIG. 21 is a diagram illustrating a data example of the travel plan mining table 661.

  FIG. 22 is a flowchart showing a processing procedure of the travel destination setting program 35 for setting a travel destination. The travel destination setting program 35 refers to the travel destination analysis table 561 and extracts a destination having the highest utilization rate from destinations that have not yet been set (step 710). Next, the travel destination setting program 35 obtains the usage fee for the destination extracted with reference to the destination table 21, and the sum of the amount of the extracted destination and the amount of the destination set so far is set. It is determined whether or not the plan maximum amount is exceeded (step 720). When the total amount of destinations exceeds the plan maximum amount (step 720 NO), the travel destination setting program 35 refers to the travel destination analysis table 561 and among the destinations that are not set, A destination with a high utilization rate is extracted and the process returns to step 720 (step 730).

  If it is within the range of the plan maximum amount (step 720 YES), the travel destination setting program 35 sets the extracted destination as the basic destination in the schedule for the set time of the destination from the set time (step 740). The schedule for the set time is a travel schedule set in the memory, and stores the stay time zone of the set destination. The average stay time of the set destination is obtained from the destination table 21.

  Next, the travel destination setting program 35 refers to the travel plan mining table 661 and extracts a destination most relevant to the set basic destination among the destinations not yet set (step 750). . Among the combinations of the set basic destination and other destinations, other destinations in the combination having the highest same plan setting ratio are targeted. Next, the travel destination setting program 35 obtains the usage fee of the related destination extracted by referring to the destination table 21, and the sum of the amount of the extracted destination and the amount of the destination set up to now is calculated. Then, it is determined whether or not the set plan maximum amount is exceeded (step 760). When the total amount of the destination exceeds the plan maximum amount (step 760 NO), the travel destination setting program 35 refers to the travel plan mining table 661 and next to the destinations that are not set. The other destinations in the combination having the same plan setting ratio of the combination are extracted, and the process returns to Step 760 (Step 770).

  If it is within the range of the plan maximum amount (step 760 YES), the travel destination setting program 35 refers to the intra-stroke traffic table 22 and determines the travel time between the already set destination and the extracted destination. It is determined whether there is another combination with a short travel time (step 780). Another combination is a combination of an already set destination and another destination. If there are other combinations that meet the conditions, the process returns to step 770 to search for the next most relevant destination.

  If there is no combination in which the travel time between the destinations is shorter (step 780 NO), the travel destination setting program 35 sets the extracted destination as a destination following the basic destination in the schedule for the set time of the destination. (Step 790). At this time, the travel time obtained from the intra-stroke traffic table 22 and the average stay time of the extracted destination obtained from the destination table 21 are incorporated into the schedule.

  Next, the travel destination setting program 35 determines whether or not the number of set destinations has reached the upper limit of one schedule (step 800). The number of destinations in one schedule is input when registering a plan attribute. If the target number of destinations has not yet been reached, the process returns to step 750 and the above processing is repeated. When the number of set destinations reaches the number of destinations of one schedule (step 800 YES), the travel destination setting program 35 determines whether or not the number of set schedules has reached the designated number of plan days. (Step 810). When the number of schedules has not reached the number of plan days, the process returns to step 710 and the above processing is repeated. When the set number of schedules reaches the number of plan days (YES in step 810), the travel destination setting program 35 generates a travel destination setting plan in which a schedule is set for each travel day (step 820). FIG. 23 is a diagram illustrating a data example of the created travel destination setting plan 821.

  FIG. 24 is a flowchart showing the processing procedure of the outbound / return traffic setting program 36 for setting the outbound / return traffic means. The outbound / return traffic setting program 36 extracts the destination set at the beginning of the first day schedule of the travel destination setting plan 821 (step 910). Next, the outbound / return traffic setting program 36 refers to the terminal-destination traffic table 23 and extracts the terminal having the shortest travel time from the extracted destination (step 920). Next, the outbound / return traffic setting program 36 calculates the terminal departure time from the extracted arrival time of the first destination and the travel time from the terminal (step 930).

  Next, the outbound / return traffic setting program 36 refers to the outbound / return traffic means table 25, and the traffic which coincides with the departure place where the departure terminal is input and arrives 30 minutes to 1 hour before the calculated terminal departure time. Means are extracted (step 940). Next, the outbound / return traffic setting program 36 sets the extracted outbound transportation means, the departure time from the arrival terminal, and the transportation means from the terminal to the first destination in the schedule of the first day of the plan stored in the memory. (Step 950). The moving means from the terminal to the first destination is extracted using the terminal-destination traffic table 23.

  Next, the outbound / return traffic setting program 36 extracts the destination set at the end of the last day schedule of the plan (step 960). Next, the outbound / return traffic setting program 36 refers to the terminal-destination traffic table 23 and extracts the terminal having the shortest travel time from the extracted destination (step 970). Next, the outbound / return traffic setting program 36 calculates the arrival time at the terminal from the extracted departure time of the last destination and the extracted travel time to the terminal (step 980).

  Next, the outbound / return traffic setting program 36 refers to the outbound / return transportation means table 25, and finds the means of transportation that coincides with the input arrival location and departs 30 to 1 hour after the calculated terminal arrival time. Extract (step 990). Next, the outbound / return traffic setting program 36 sets the extracted outbound transportation means, arrival time at the departure terminal, and transportation means from the last destination to the terminal in the schedule of the last day of the plan stored in the memory. (Step 1000). The outbound / return traffic setting program 36 generates the outbound / return traffic setting plan 1011 from the schedule on the memory (step 1010). FIG. 25 is a diagram illustrating a data example of the outbound / return traffic setting plan 1011.

  FIG. 26 is a flowchart showing a processing procedure of the accommodation place setting program 37 for setting an accommodation place. The accommodation location setting program 37 extracts the first day schedule of the plan with reference to the outbound / return traffic setting plan 1011 (step 1110). Next, the accommodation location setting program 37 extracts the last destination set in the schedule (step 1120). Next, the accommodation place setting program 37 refers to the accommodation place-destination traffic table 24 and extracts all accommodation places whose travel time is within 2 hours from the extracted destination (step 1130). Next, the accommodation location setting program 37 determines whether or not the total amount of destinations set so far and the total usage fee of the extracted accommodation facilities do not exceed the plan maximum amount (step 1140). When the total amount exceeds the plan maximum amount, the accommodation location setting program 37 displays no corresponding plan on the display device 14.

  If the total amount is within the plan maximum amount, the accommodation place setting program 37 refers to the accommodation place-destination traffic table 24 and is set in the schedule of the next day from each accommodation place among the extracted accommodation places. Several facilities are extracted in order from the shortest travel time to the first destination (step 1150). Next, the accommodation location setting program 37 sets the extracted accommodation location, the arrival time of the accommodation location, the next sunrise departure time, and the transportation means between the destination and the accommodation location in the schedule on the memory (step 1160). ). Next, the accommodation location setting program 37 determines whether or not accommodation locations have been set for the designated number of accommodation days (step 1170). If there is a schedule in which no accommodation place is set (NO in step 1170), the schedule for the next day is extracted (step 1180), the process returns to step 1120, and the above process is repeated. When accommodation places are set for the number of stay days, the accommodation place setting program 37 generates the accommodation place setting plan 1191 from the schedule on the memory (step 1190). FIG. 27 is a diagram illustrating a data example of the accommodation place setting plan 1191.

  FIG. 28 is a flowchart showing the processing procedure of the lunch spot setting program 38 for setting the lunch spot. The lunch spot setting program 38 extracts the first day schedule of the plan on the memory (step 1210). The lunch place setting program 38 determines whether or not a scheduled destination that leaves the destination before 12:00 is set for the schedule (step 1220). If it is set, the lunch spot setting program 38 extracts the destination closest to 12:00 before 12:00 (step 1240). Next, the lunch spot setting program 38 determines whether the lunch spot is close to the destination (step 1270). That is, the lunch place setting program 38 refers to the lunch place-destination traffic table 26, and determines whether or not the time from the departure time of the extracted destination to 12:00 is longer than the travel time from the destination to the lunch place. judge. If the lunch spot is close, the lunch spot is extracted from the lunch spot-destination traffic table 26 (step 1300). This is a candidate for at least one lunch spot.

  If the destination has not been set before 12:00 (NO at step 1220), the lunch spot setting program 38 determines whether the accommodation place has been set before 12:00 of the schedule (step 1260). If the accommodation place is set before 12:00, the lunch place setting program 38 interprets the accommodation place as the destination and regards the departure time from the accommodation place as the departure time from the nearest destination at 12:00 ( Step 1250), go to Step 1240. However, in step 1270, the lunch area to the accommodation area traffic table 28 is referred to instead of the lunch area to the destination traffic table 26. If the accommodation place has not been set before 12:00, the terminal has been set, so the lunch place setting program 38 will read the terminal as the destination and set the departure time from that terminal to the nearest destination at 12:00. It is regarded as the departure time from the ground (step 1280), and the process goes to step 1240. However, in step 1270, the lunch area to the terminal traffic table 27 is referred to instead of the lunch area to the destination traffic table 26. If the lunch location is far from the destination (NO at step 1270), the lunch location is not set (step 1290) and the process goes to step 1230.

  Next, the lunch place setting program 38 determines whether or not a scheduled destination that will arrive at the destination after 13:00 is set for the schedule (step 1310). If it is set, the lunch place setting program 38 extracts the destination having the closest arrival time after 13:00 and after 13:00 (step 1320). Next, the lunch spot setting program 38 determines whether the lunch spot is close to the destination (step 1350). That is, the lunch spot setting program 38 refers to the lunch spot-destination traffic table 26 to determine whether the time from 13:00 to the arrival time of the destination is longer than the travel time from the destination to the lunch spot. . If the lunch spot is close, the lunch spot is extracted from the lunch spot-destination traffic table 26 (step 1380). This is another candidate for lunch.

  When the destination is not set after 13:00 (NO in step 1310), the lunch place setting program 38 determines whether or not an accommodation place is set after 13:00 of the schedule (step 1340). If the accommodation place is set after 13:00, the lunch place setting program 38 interprets the accommodation place as the destination and regards the arrival time at the accommodation place as the arrival time of the nearest destination at 13:00 (step 1330). ), Go to step 1320. However, in step 1350, the lunch area to the accommodation area traffic table 28 is referred to instead of the lunch area to the destination traffic table 26. If no lodging place has been set after 13:00, the terminal has been set, so the lunch place setting program 38 will read the terminal as the destination and the arrival time at that terminal will be the nearest destination at 13:00. (Step 1360) and go to step 1320. However, in step 1350, instead of the lunch area to the destination traffic table 26, the lunch area to the terminal traffic table 27 is referred to. If the lunch place is far from the destination (NO in step 1350), the lunch place is not set (step 1370) and the process goes to step 1230.

  Next, the lunch spot setting program 38 determines whether or not the sum total of the plan total amount so far plus the lunch fee does not exceed the plan maximum amount (step 1390). The lunch spot setting program 38 refers to the lunch spot table 29 and acquires the lunch fee. If there are multiple lunch spot candidates, the lunch fee is set to the highest average usage fee. Next, the lunch spot setting program 38 sets the lunch spot candidates extracted in the schedule on the memory and the means of transportation between the lunch spot and the destination (step 1400). Refer to the lunch-destination traffic table 26 for the transportation means and travel time between the lunch site and the destination. In the case of a terminal and an accommodation area instead of the destination, the lunch area to the terminal transportation table 27 and the lunch area to the accommodation area transportation table 28 are referred to, respectively. Next, the lunch spot setting program 38 determines whether the lunch spot has been set for the designated number of plan days (step 1410). If there is a remaining schedule, the lunch spot setting program 38 extracts the schedule for the next day (step 1230), and returns to step 1220. When lunch spots for the number of plan days are set, the lunch spot setting program 38 creates a lunch spot setting plan 1421 (step 1420). FIG. 29 is a diagram illustrating a data example of the lunch setting plan 1421. As illustrated in FIG.

  FIG. 30 is a flowchart showing the processing procedure of the in-stroke traffic setting program 39 for determining in-stroke traffic. The intra-stroke traffic setting program 39 extracts the first day schedule of the plan on the memory (step 1510). Next, the intra-stroke traffic setting program 39 determines whether or not a transportation means between destinations is set for the schedule (step 1520). If it has been set, go to Step 1530. If there is a destination not set, the intra-stroke traffic setting program 39 refers to the intra-traffic traffic table 22 and sets the means of transportation between the destinations (step 1540). Next, the in-stroke traffic setting program 39 determines whether or not the in-stroke traffic has been set for the designated number of plan days (step 1550). If there is a remaining schedule, the intra-stroke traffic setting program 39 extracts the schedule for the next day (step 1530) and returns to step 1520. When the in-stroke traffic is set for the number of plan days, the in-stroke traffic setting program 39 completes the recommended travel plan 1561 (step 1560). FIG. 31 is a diagram illustrating a data example of the recommended travel plan 1561.

  FIG. 32 is a diagram illustrating a data example of the transmission travel information table 19. Each record of the transmission travel information table 19 has data items of ID, name, time, place, and transmission information. The ID and name are the sender's ID and name. The time and place are the place where the sender is traveling and the transmission time. The transmission information is information that the sender needs at the location. The transmission information is sent to the travel plan creator through a form telephone or the like.

  The travel plan creation support device 10 receives the name, time, location, and transmission time input via the input device 12 and stores them in the transmission travel information table 19. When the data amount of the transmission travel information table 19 is accumulated, the travel plan creation support device 10 aggregates necessary transmission information for each place, time, or time zone of the transmission travel information table 19 and requires transmission information. The transmission travel information analysis table 20 is created by calculating the percentage of travelers and stored in the storage device. FIG. 33 is a diagram illustrating an example of data in the transmission travel information analysis table 20. The travel plan creation support device 10 refers to the transmitted travel information analysis table 20 and provides information desired by a predetermined percentage or more of travelers at a specific location.

  With the configuration and processing procedure described above, it is possible to reduce the work load of the travel plan creator by automatically generating the most popular plans now, and it is also necessary for travelers when necessary. It is possible to provide information.

It is a block diagram of the travel plan creation assistance system of embodiment. It is a figure which shows an example of the traveler attribute table 16 of embodiment. It is a figure which shows an example of the travel plan attribute table 17 of embodiment. It is a figure which shows an example of the travel history table 18 of embodiment. It is a figure which shows an example of the destination table 21 of embodiment. It is a figure which shows an example of the intra-stroke traffic table 22 of embodiment. It is a figure which shows an example of the terminal-destination traffic table 23 of embodiment. It is a figure which shows an example of the accommodation place-destination traffic table 24 of embodiment. It is a figure which shows an example of the outward trip return transportation means table 25 of embodiment. It is a figure which shows an example of the lunch place-destination traffic table 26 of embodiment. It is a figure which shows an example of the lunch place table 29 of embodiment. It is a figure which shows the schematic process sequence of the system of embodiment. It is a figure which shows an example of the applicable ID table 421 of embodiment. It is a figure which shows the schematic procedure of the preparation process of the travel plan of embodiment. It is a flowchart which shows the process sequence which produces | generates the travel destination analysis table of embodiment. It is a figure which shows an example of the extraction travel log | history table 511 of embodiment. It is a figure which shows an example of the frequency | count destination use frequency table 541 of embodiment. It is a figure which shows an example of the travel destination analysis table 561 of embodiment. It is a flowchart which shows the process sequence which produces | generates the travel plan mining table of embodiment. It is a figure which shows an example of the same plan setting frequency table 641 of embodiment. It is a figure which shows an example of the travel plan mining table 661 of embodiment. It is a flowchart which shows the process sequence which determines the travel destination of embodiment. It is a figure which shows an example of the travel destination setting plan 821 of embodiment. It is a flowchart which shows the process sequence which determines the outward trip return traffic of embodiment. It is a figure which shows an example of the outward trip return traffic setting plan 1011 of embodiment. It is a flowchart which shows the process sequence which determines the accommodation place of embodiment. It is a figure which shows an example of the accommodation place setting plan 1191 of embodiment. It is a flowchart which shows the process sequence which determines the lunch place of embodiment. It is a figure which shows an example of the lunch place setting plan 1421 of embodiment. It is a flowchart which shows the process sequence which determines the traffic in a process of embodiment. It is a figure which shows an example of the recommended travel plan 1561 of embodiment. It is a figure which shows an example of the transmission travel information table 19 of embodiment. It is a figure which shows an example of the transmission travel information analysis table 20 of embodiment.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 10 ... Travel plan creation assistance apparatus, 16 ... Traveler attribute table, 17 ... Travel plan attribute table, 18 ... Travel history table, 19 ... Transmission travel information table, 21 ... Destination table, 22 ... Traffic table in process, 23 ... Terminal-Destination traffic table, 24 ... Accommodation-Destination traffic table, 25 ... Outbound return transportation means table, 26 ... Lunch destination destination traffic table, 27 ... Lunch location-Terminal traffic table, 28 ... Lunch destination-Destination Traffic table, 29 ... lunch place table, 30 ... travel history table corresponding ID extraction program, 32 ... travel destination analysis table generation program, 34 ... travel plan mining table generation program, 35 ... travel destination setting program, 36 ... return trip Traffic setting program, 37 ... Accommodation place setting program, 38 ... Lunch place setting program Gram, 39 ... stroke in traffic configuration program.

Claims (7)

Refer to the traveler attribute table for registering the personal attributes of the traveler and the travel plan attribute table for registering the attributes for the travel plan for each traveler, and select the traveler that matches the target personal attribute and the travel plan attribute. Extracting, and
Referring to a travel history table that registers destinations and arrival times for each traveler, and extracting the extracted traveler's travel history records;
The extracted travel history records are tabulated by time and destination, and the destination and time having the highest utilization rate are set as the destination and arrival time in the schedule of the travel plan. Travel plan creation support method. Further, referring to the travel history table, creating information of a combination of a plurality of destinations visited by the same traveler;
Calculating a ratio of the same pattern for each combination of patterns;
Extracting other destinations to be combined with respect to a combination having the highest ratio among the combinations including the destination set in the schedule;
The travel plan creation support method according to claim 1, further comprising: setting the extracted other destination as another purpose in the schedule. Further, a step of extracting a terminal having the shortest travel time from the destination set in the schedule with reference to a traffic table between destination terminals that stores the transportation means and the travel time between the destination and the terminal as each record. When,
Departure terminal, arrival terminal, transportation, transportation, departure time and arrival time are stored as each record. Extracting the means of transportation as the arrival terminal;
2. The travel plan creation support method according to claim 1, further comprising the step of setting the extracted departure terminal, arrival terminal, transportation, and transportation in the schedule. Refers to the traveler attribute table for registering the traveler's personal attributes on the computer and the travel plan attribute table for registering the attributes for the travel plan for each traveler, and matches the target personal attribute and the travel plan attribute. Extracting a traveler; and
Referencing a travel history table that registers destinations and arrival times for each traveler, and extracting the extracted traveler's travel history records;
A computer program for totalizing the extracted travel history records by time and destination, and realizing the step of setting the destination and time with the highest utilization rate as the destination and arrival time in the schedule of the travel plan . The computer further refers to the travel history table, and creates information of a combination of a plurality of destinations visited by the same traveler;
Calculating a ratio of the same pattern for each combination of patterns;
Extracting other destinations to be combined with respect to a combination having the highest ratio among the combinations including the destination set in the schedule;
The computer program according to claim 4, for realizing the step of setting the extracted other destination as another purpose in the schedule. A travel plan creation support system having a CPU and a memory,
The system includes a traveler attribute table for registering a traveler's personal attributes, a travel plan attribute table for registering attributes for a travel plan for each traveler, and a travel history for registering a destination and arrival time for each traveler. Table,
A travel history table corresponding ID extraction unit that extracts a traveler ID that matches a personal attribute and a travel plan attribute that are targeted with reference to the traveler attribute table and the travel plan attribute table;
Travel destination analysis that refers to the travel history table, extracts the extracted travel history records of the traveler, and aggregates the extracted travel history records by time and destination to generate a travel destination analysis table A table generator,
A travel destination setting unit that sets the destination and time of the highest utilization rate as the destination in the schedule of the travel plan and the arrival time;
The travel history table corresponding ID extraction unit, the travel destination analysis table generation unit, and the travel destination setting unit are programs stored in the memory and executed by the CPU. . The system further refers to the travel history table, creates information on a combination of a plurality of destinations visited by the same traveler, and creates a travel plan mining table by calculating the ratio of the same pattern for each combination pattern. A travel plan mining table generator to
The travel destination setting unit further extracts other destinations to be combined for a combination having the highest ratio among the combinations including the destinations set in the schedule, and the extracted other destinations are Set as other purpose in the schedule,
The travel plan creation support system according to claim 6, wherein the travel plan mining table generation unit is a program stored in the memory and executed by the CPU.

Images