History creation apparatus and history creation program

Abstract

To provide a technique for providing a sightseeing service which is more appropriate for a user.SOLUTION: A history creation apparatus 40 includes: a history data acquisition unit 41 which acquires entire history data including a combination of details of usage of an application used in a terminal device with the application installed thereon and location information indicating a location of the terminal device that uses the application; and a history creation unit 42 which creates sightseeing history data in which a combination including details of usage related to sightseeing is specified, out of combinations included in the entire history data.SELECTED DRAWING: Figure 6

Description

[Technical Field]

[0001] The present disclosure relates to history creation techniques. [Background technology]

[0002] A technology has been disclosed for providing a communication terminal, a control method for a communication terminal, and a computer program that enables a communication terminal having multiple applications installed to create a more detailed location history of the communication terminal by combining the location history of the communication terminal for each of the multiple applications (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-049049 Summary of the Invention [Problem to be solved by the invention]

[0004] A technology is envisioned that uses a user's route history to provide a user with a tourism service, such as setting a route to a destination for sightseeing.

[0005] However, in the conventional technology described in Patent Document 1, the route history of the application used is recorded regardless of whether it is useful as information. Therefore, when providing a service to a user using the route history recorded using the conventional technology described in Patent Document 1, information unnecessary for the service may be used. As a result, an appropriate service may not be provided to the user.

[0006] In view of the above, an object of the present disclosure is to provide a technology for providing more appropriate tourism services to users. [Means for solving the problem]

[0007] A history creation device according to one aspect of the present disclosure includes a history data acquisition unit that acquires overall history data including pairs of usage details when an application is used on a terminal device on which the application is installed and location information indicating the location of the terminal device at the time of use, and a history creation unit that creates tourism history data in which pairs of the pairs included in the overall history data that include usage details related to tourism are identified.

[0008] Another aspect of the history creation program of the present disclosure causes a computer to acquire overall history data including pairs of usage details when an application was used on a terminal device on which the application is installed and location information indicating the location of the terminal device at the time of use, and create tourism history data in which pairs of the pairs included in the overall history data that include usage details related to tourism are identified. [Effects of the Invention]

[0009] According to certain aspects of the present disclosure, a technology can be provided for providing more appropriate tourism services to users. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a block diagram showing the overall configuration of a tourism service providing system according to an embodiment. [Figure 2] FIG. 2 is a block diagram illustrating an example of the configuration of a server according to the embodiment. [Figure 3] FIG. 1 is a block diagram illustrating an example of the configuration of a mobile terminal device according to an embodiment. [Figure 4] 10 is a flowchart illustrating an example of an application execution process in a processing unit of the mobile terminal device according to the embodiment. [Figure 5] FIG. 10 is a diagram illustrating an example of overall history data. [Figure 6] FIG. 2 is a functional block diagram of a processing unit of a server according to the embodiment. [Figure 7]FIG. 10 is a sequence diagram illustrating an example of a history creation process of the tourism service providing system according to the embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of sightseeing history data. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of a route setting process of the tourism service providing system according to the embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of an input screen for inputting a destination area and an expected arrival time. [Figure 11] 10 is a flowchart of a candidate extraction process performed by a processing unit of a server. [Figure 12] FIG. 10 is a diagram illustrating an example of a tourist spot database. [Figure 13] FIG. 10 is a diagram illustrating an example of a candidate selection input screen. [Figure 14] FIG. 10 is a diagram illustrating an example of a route information screen. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Specific numerical values ​​and the like shown in the embodiments are merely examples for facilitating understanding of the invention, and do not limit the present disclosure unless otherwise specified. Elements not directly related to the present disclosure are omitted from the drawings.

[0012] 1 is a block diagram showing the overall configuration of a tourism service providing system 1 according to an embodiment. The tourism service providing system 1 is constructed using a server 10 and a mobile terminal device 30. The server 10 and the mobile terminal device 30 can be interconnected via a network 5.

[0013] The server 10 is installed in a facility or a data center of a service provider that provides tourism services. The server 10 may be a server owned by the service provider, or may be a cloud server used based on a cloud service.

[0014] The mobile terminal device 30 is a terminal device carried by a user. For example, a smartphone, a feature phone, or a tablet equipped with a communication function can be used as the mobile terminal device 30. In the following, an example in which a smartphone is used as the mobile terminal device 30 is assumed.

[0015] Network 5 is a general term for communication paths such as the Internet, dedicated lines, and VPNs (Virtual Private Networks), regardless of the communication medium or protocol. For example, a mobile phone network (cellular network), wireless LAN, wired LAN, optical fiber network, ADSL network, or CATV network can be used as the communication medium.

[0016] 2 is a block diagram showing an example of the configuration of the server 10 according to the embodiment. The server 10 includes a processing unit 11, a storage unit 12, and a communication unit 13.

[0017] The processing unit 11 performs overall control of the processing of the server 10. The processing unit 11 is realized by a combination of hardware resources and software resources, or by hardware resources alone. The hardware resources may include a CPU, ROM, RAM, GPU, ASIC, FPGA, and other LSIs. The software resources may include programs such as an operating system, middleware, and applications. Hereinafter, applications may be abbreviated to "apps."

[0018] The storage unit 12 has a non-volatile recording medium (for example, HDD, SSD) and stores various programs and various data. The storage unit 12 stores a program for executing the processing according to this embodiment. The storage unit 12 stores a map database 121. The storage unit 12 of this embodiment stores timetables for public transportation. The storage unit 12 of this embodiment also stores a tourist spot database in which categories are assigned to each tourist spot across the country. The tourist spots here are places that are frequently visited by tourists, and may be facilities or natural features such as mountains, rivers, and the sea. The tourist spot database will be described later.

[0019] The communication unit 13 executes signal processing for connecting to the network 5. For example, when the server 10 is connected to a router device via a LAN cable, the communication unit 13 executes signal processing in accordance with Ethernet (registered trademark).

[0020] 3 is a block diagram showing an example of the configuration of a mobile terminal device 30 according to an embodiment. The mobile terminal device 30 includes a processing unit 31, a storage unit 32, a wireless communication unit 33, an operation unit 34, a display unit 35, and a GPS receiving unit 36. An application is installed in the mobile terminal device 30.

[0021] The processing unit 31 comprehensively controls the processing of the mobile terminal device 30. The processing unit 31 is realized by a combination of hardware resources and software resources, or by hardware resources alone. The hardware resources may include a CPU, ROM, RAM, GPU, ASIC, FPGA, and other LSIs. The software resources may include an operating system, middleware, applications, and other programs.

[0022] The storage unit 32 has a non-volatile recording medium (e.g., a NAND flash memory) and stores various programs and data. The storage unit 32 stores programs for multiple applications. For example, the storage unit 32 stores a program for an application that has a function of storing the location of the mobile terminal device 30 in the storage unit 32 when the application is used, a program for an application that executes the route setting process according to this embodiment, and other programs. The storage unit 32 also stores a usage history for each application that chronologically indicates the usage details. This usage details indicate the details of the functions realized by executing the process related to the used application. The usage details are determined appropriately depending on the application. The storage unit 32 also stores overall history data D1, which will be described later.

[0023] The wireless communication unit 33 has a modem and executes signal processing for wirelessly connecting to the network 5 via the antenna 33a. Examples of wireless communication networks that the mobile terminal device 30 can connect to include a mobile phone network (4G / 5G), Wi-Fi (registered trademark), and Bluetooth (registered trademark).

[0024] The operation unit 34 includes a user interface such as a touch panel and physical buttons. The operation unit 34 accepts user operations and outputs an operation signal corresponding to the user's operation to the processing unit 31. The display unit 35 includes a touch panel display such as a liquid crystal display, an organic EL display, or a mini LED display. The GPS receiving unit 36 ​​detects the current location information of the mobile terminal device 30 using latitude and longitude, and outputs the detected location information to the processing unit 31.

[0025] FIG. 4 is a flowchart showing an example of the application execution process S100 in the processing unit 31 of the mobile terminal device 30 according to the embodiment.

[0026] In step S101, the processing unit 31 determines whether or not a launch operation for a predetermined application has been received from the user via the operation unit 34. The predetermined application here has a function of storing location information indicating the location of the mobile terminal device 30 in the storage unit 32 when the application is being used. The launch operation here refers to, for example, touching the icon of the application displayed on the display unit 35 of the mobile terminal device 30. If the launch operation for the application has been received (Yes in step S101), the process S100 proceeds to step S102. If the launch operation for the application has not been received (No in step S101), the process S100 returns to step S101.

[0027] In step S102, the processing unit 31 starts the application for which the start operation has been accepted, and an operation screen corresponding to the started application is displayed on the mobile terminal device 30.

[0028] In step S103, the processing unit 31 determines whether or not an operation to use the application has been accepted from the user via the operation unit 34. The operation to use the application here refers to, for example, touching an operation button for executing a process to realize the function of the application displayed on the touch panel display of the mobile terminal device 30. If an operation to use the application has been accepted (Yes in step S103), the process S100 proceeds to step S104. If an operation to use the application has not been accepted (No in step S103), the process S100 returns to step S103.

[0029] In step S104, the processing unit 31 executes processing according to the application that has been operated to use. For example, when an operation to use an application for electronic payment is received, the processing unit 31 executes electronic payment processing related to that application.

[0030] In step S105, the processing unit 31 acquires location information indicating the location of the mobile terminal device 30 via the GPS receiving unit .

[0031] In step S106, the processing unit 31 acquires the usage details of the application. For example, the processing unit 31 reads the usage history of the used application from the storage unit 32, and extracts and acquires the usage details at the time of use from the usage history.

[0032] In step S107, the processing unit 31 stores or updates the overall history data D1 including the acquired combination of location information indicating the location of the mobile terminal device 30 and the usage details of the application in the storage unit 32. For example, the processing unit 31 updates the overall history data D1 by storing the acquired combination of location information indicating the location of the mobile terminal device 30 and the usage details of the application in the storage unit 32.

[0033] FIG. 5 shows an example of the overall history data D1. The overall history data D1 shown in FIG. 5 indicates, for each item, the name of the application used, the location of the mobile terminal device 30 when the application was used, and the usage details of the application. For example, in item 1, the name of the application used is "Walking App X," the location of the mobile terminal device 30 when the application was used is "Chiyoda-ku, Tokyo··O-×-△," and the usage details of the application are "Start recording steps." For example, if items 1 through 9 are stored in the overall history data D1 and an electronic payment for food and drink is made using electronic payment app Y at restaurant T located at "×-△-×, Kamakura City, Kanagawa Prefecture," the name of the application used, "Electronic Payment App Y," the location of the mobile terminal device 30 when the application was used, "×-△-×, Restaurant T, Kamakura City, Kanagawa Prefecture," and the usage details "Electronic Payment (Food and Drink)" are added to item 10, thereby updating the overall history data D1.

[0034] In step S108, the processing unit 31 determines whether or not an operation to terminate the application has been accepted from the user via the operation unit 34. The termination operation here refers to, for example, operating a predetermined termination button on the mobile terminal device 30. If an operation to terminate the application has been accepted (Yes in step S108), the process S100 proceeds to step S109. If an operation to terminate the application has not been accepted (No in step S108), the process S100 returns to step S103.

[0035] In step S109, the processing unit 31 ends the application. After step S109, the process S100 ends.

[0036] FIG. 6 is a functional block diagram of the processing unit 11 of the server 10. The processing unit 11 includes a history creation device 40 and a route setting device 50. The configuration shown in FIG. 6 is realized in hardware by a CPU, memory, other LSIs, etc. of any computer, and in software by a program loaded into memory, but the functional blocks shown here are realized by the cooperation of these components. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms, such as hardware alone or a combination of hardware and software. The history creation device 40 includes a first acquisition unit 41 and a history creation unit 42. First, the history creation process by the history creation unit 42 in the processing unit 11 will be described, and the route setting process in the route setting device 50 will be described later.

[0037] The first acquisition unit 41 acquires overall history data D1 including a pair of usage details when an application was used on the mobile terminal device 30 and location information indicating the location of the mobile terminal device 30 at the time of use. The first acquisition unit 41 of the present embodiment is an example of a history data acquisition unit.

[0038] The history creation unit 42 creates sightseeing history data D2 in which groups that include sightseeing-related usage details are identified from among the groups included in the overall history data D1. The sightseeing history data D2 of this embodiment includes only groups that include sightseeing-related usage details from among the groups included in the overall history data D1. The sightseeing history data D2 will be described later.

[0039] FIG. 7 is a sequence diagram showing an example of the history creation process S200 of the tourist service providing system 1 according to the embodiment.

[0040] In step S201, the processing unit 31 of the mobile terminal device 30 determines whether a predetermined transmission timing has arrived. For example, the predetermined transmission timing may be a predetermined time set at a predetermined time interval (e.g., every hour), when a predetermined application is terminated, or when the user performs a predetermined operation via the operation unit 34.

[0041] In step S202, the processing unit 31 of the mobile terminal device 30 transmits the entire history data D1 to the server 10. For example, the processing unit 31 reads out the entire history data D1 stored from the previous transmission timing to the current transmission timing from the storage unit 32, and transmits the read entire history data D1 via the wireless communication unit 33. As a result, the first acquisition unit 41 of the server 10 receives and acquires the entire history data D1.

[0042] In step S203, the history creation unit 42 of the server 10 identifies groups that include tourism-related usage content from among the groups included in the acquired overall history data D1. Tourism-related usage content is, for example, at least one of electronic payments for boarding or disembarking at public transportation stops such as trains and buses, electronic payments for souvenirs, electronic payments for food and drink, and social networking service (SNS) posts with hashtags attached to tourist spot names. For example, the history creation unit 42 of the server 10 searches the overall history data D1 for specific tourism-related keywords to identify groups that include specific tourism-related keywords in their usage content. Specific keywords include, for example, boarding, disembarking, hashtags (#), names of public transportation stops (such as trains and buses) (such as station names and bus stop names), tourist spot names, area names, names of local products, names of souvenir products, and food and drink. The names of the tourist spot names, area names, local product names, names of souvenir products, and the like are set appropriately, for example. For example, in the overall history data of Fig. 5, the usage details of items 3, 4, and 6 to 8 include keywords for getting on and off, tourist spots, or place names, and the usage details of items 9 and 10 include keywords for product names of souvenirs or eating and drinking. Therefore, the history creation unit 42 identifies the sets of items 3, 4, and 6 to 10 in the overall history data of Fig. 5 as sets that include usage details related to sightseeing.

[0043] In step S204, the history creation unit 42 of the server 10 creates sightseeing history data D2 that includes only the groups that include sightseeing-related usage content from among the groups included in the acquired overall history data D1, based on the identification result. Figure 8 shows an example of the sightseeing history data D2. The sightseeing history data D2 includes the groups of items 3, 4, and 6 to 10 that were identified in the overall history data D1 as groups that include sightseeing-related usage content.

[0044] In step S205, the history creation unit 42 of the server 10 stores or updates the sightseeing history data D2 in the storage unit 12. After step S205, the process S200 ends.

[0045] Next, a description will be given of the route setting process in the route setting device 50. Returning to Fig. 6, the route setting device 50 includes a second acquisition unit 51, an identification unit 52, an extraction unit 53, an output unit 54, and a route information creation unit 55. The route setting device 50 of this embodiment is an example of an information output device.

[0046] The second acquisition unit 51 acquires sightseeing history data, user input including a destination area and an expected arrival time, and a departure point. The identification unit 52 identifies tourist spots that have been visited in the destination area based on the sightseeing history data. The extraction unit 53 extracts tourist spots in the destination area that are different from tourist spots that have been visited as tourist spot candidates. Details of how the extraction unit 53 extracts tourist spot candidates will be described later. The output unit 54 outputs the extracted tourist spot candidates. The route information creation unit 55 creates route information indicating routes to the extracted tourist spot candidates. The route information creation unit 55 of this embodiment creates route information indicating routes to the extracted tourist spot candidates when using a passenger car.

[0047] FIG. 9 is a sequence diagram showing an example of the route setting process S300 of the tourist service providing system 1 according to the embodiment.

[0048] In step S301, the processing unit 31 of the mobile terminal device 30 determines whether or not an operation to start a route setting application according to the embodiment has been accepted from the user via the operation unit 34. If an operation to start the application has been accepted (Yes in step S301), the process S300 proceeds to step S302. If an operation to start the application has not been accepted (No in step S301), the process S300 returns to step S301.

[0049] In step S302, the processing unit 31 of the mobile terminal device 30 starts the application for which the start operation has been accepted. By starting the application, an input screen for inputting the destination area and the expected arrival time is displayed on the display unit 35 of the mobile terminal device 30.

[0050] FIG. 10 illustrates an input screen DP1 for inputting a destination area and a scheduled arrival time. The input screen DP1 in FIG. 10 has input fields 61-62 for inputting a destination area and a scheduled arrival time. Operating a pull-down button 63 provided for each input field 61-62 displays a list of selectable destination areas and scheduled arrival times in a pull-down format. For example, when the pull-down button 63 in the input field 61 for the destination area is operated, destination areas such as the "Yokohama area," the "Kamakura area," the "Enoshima area," and the "Hakone area" are displayed, as shown in FIG. 10. These destination areas and their ranges are set appropriately. Furthermore, for example, when the pull-down button 63 in the input field 62 for the scheduled arrival time is selected, times at predetermined time intervals, such as "16:00" and "16:15," are displayed. These times can also be set appropriately. The user selects a desired item from the displayed list to input the desired destination area and scheduled arrival time into each input field 61-62.

[0051] In step S303, the processing unit 31 of the mobile terminal device 30 determines whether or not user input regarding the destination area and expected arrival time has been accepted from the user via the operation unit 34. If user input has been accepted (Yes in step S303), the process S300 proceeds to step S304. If user input has not been accepted (No in step S303), the process S300 returns to step S303.

[0052] In step S304, the processing unit 31 of the mobile terminal device 30 transmits the user input regarding the destination area and the expected arrival time and the current location of the mobile terminal device 30 from the GPS receiving unit 36 ​​to the server 10. The second acquisition unit 51 of the server 10 acquires the user input regarding the destination area and the expected arrival time, and acquires the current location of the mobile terminal device 30 as the departure point.

[0053] In step S305, the processing unit 11 of the server 10 executes a candidate extraction process. The candidate extraction process S305 by the processing unit 11 of the server 10 will be described below with reference to Fig. 11. Fig. 11 is a flowchart of the candidate extraction process S305 by the processing unit 11 of the server 10.

[0054] In step S401, the second acquisition unit 51 acquires the sightseeing history data D2. For example, the second acquisition unit 51 reads out the sightseeing history data D2 from the storage unit 12 to acquire the sightseeing history data D2.

[0055] In step S402, the identification unit 52 identifies tourist spots that have been visited in the destination area based on the sightseeing history data D2. For example, if the Kamakura area is selected as the destination area in the user input, the identification unit 52 identifies tourist spots located within the Kamakura area, such as Kamakura City, Kanagawa Prefecture, based on the location of the mobile terminal device 30 in the sightseeing history data D2. In the example of the sightseeing history data D2 in Fig. 8, the identification unit 52 identifies Kamakura Station, temple A1, souvenir shop S, and restaurant T, which are located in Kamakura City, Kanagawa Prefecture, as tourist spots that have been visited.

[0056] In step S403, the identification unit 52 identifies the category of a tourist spot that the user has visited in the destination area. For example, the identification unit 52 reads out a tourist spot database from the storage unit 12 and identifies the category of the tourist spot identified in step S402 based on the tourist spot database.

[0057] FIG. 12 illustrates an example of the tourist spot database D3. The tourist spot database D3 in FIG. 12 stores tourist spot names and categories assigned to the tourist spots. For example, "Temple A1," "Shrine A2," and "Temple A3" are assigned the category "religious facility." For example, "Amusement Park B1" is assigned the category "theme park." For example, "Mountain F1" is assigned the category "mountain." For example, "Kamakura Station" is assigned the category "stop facility." For example, "Restaurant T1" is assigned the category "restaurant." For example, "souvenir shop S1" is assigned the category "souvenir shop." For example, if the tourist spots that have been visited in the destination area "Kamakura Area" are "Kamakura Station," "Temple A1," "souvenir shop S1," and "restaurant T1," the identification unit 52 identifies the categories as "religious facility," "stop facility," "souvenir shop," and "restaurant."

[0058] In step S404, the identification unit 52 identifies tourist spots in the destination area that belong to the identified category, excluding tourist spots that the user has visited. For example, the identification unit 52 identifies, from the tourist spot database D3, tourist spots located in the destination area that are different from tourist spots that the user has visited and that belong to the identified category. For example, if the identified categories are "religious facilities," "bus stops," "souvenir shops," and "restaurants," the identification unit 52 identifies, from the tourist spot database D3, tourist spots located in the destination area that belong to "religious facilities," "bus stops," "souvenir shops," and "restaurants," excluding tourist spots that the user has visited.

[0059] In step S405, the extraction unit 53 selects one of the identified tourist spots.

[0060] In step S406, the extraction unit 53 determines whether the selected tourist spot is reachable by public transportation. For example, if the selected tourist spot is located within walking distance of the nearest public transportation stop, the extraction unit 53 determines that the selected tourist spot is reachable by public transportation. For example, in the tourist spot database D3, it may be determined in advance whether each tourist spot is located within walking distance of the nearest public transportation stop. Here, the walking distance is, for example, a range that requires 30 minutes on foot, but is not limited to this and may be set appropriately. If the tourist spot is reachable (Yes in step S406), the candidate extraction process S305 proceeds to step S407. If the tourist spot is not reachable (No in step S406), the candidate extraction process S305 proceeds to step S409.

[0061] In step S407, the extraction unit 53 determines whether there is a public transportation service within walking distance of the selected tourist spot that will arrive by the scheduled arrival time when the current location is set as the departure point. For example, the extraction unit 53 reads out a public transportation service timetable from the storage unit 12 and compares the public transportation service timetable with the scheduled arrival time. For example, if the comparison shows that there is a public transportation service that will arrive at the nearest public transportation facility to the selected tourist spot before the scheduled arrival time, the extraction unit 53 determines that there is a service that will arrive at the selected tourist spot at the scheduled arrival time. If there is an arriving service (Yes in step S407), the candidate extraction process S305 proceeds to step S408. If there is no arriving service (No in step S407), the candidate extraction process S305 proceeds to step S409.

[0062] In step S408, the extraction unit 53 excludes the selected tourist spot from the candidates. Thereafter, the candidate extraction process S305 proceeds to step S409.

[0063] In step S409, the extraction unit 53 determines whether or not there are any tourist spots among the identified tourist spots that have not been selected in step S405 and step S410 (described later). If there are any tourist spots that have not been selected (Yes in step S409), the candidate extraction process S305 proceeds to step S410. If there are no tourist spots that have not been selected (No in step S409), the candidate extraction process S305 proceeds to step S411.

[0064] In step S410, the extraction unit 53 selects tourist spots that have not yet been selected from the identified tourist spots. Thereafter, the candidate extraction process S305 returns to step S406. Thereafter, steps S406 to S410 are repeatedly executed until all of the identified tourist spots have been selected. As a result, it is determined whether or not all of the identified tourist spots can be included as destination candidates.

[0065] In step S411, the extraction unit 53 extracts, from the identified tourist spots, tourist spots that have not been excluded from the candidates in step S408 as destination candidates. After step S411, the candidate extraction process S305 ends, and the process S300 proceeds to step S306.

[0066] Returning to FIG. 9, in step S306, the output unit 54 of the server 10 transmits the extracted candidates to the mobile terminal device 30, thereby outputting the extracted candidates.

[0067] In step S307, the processing unit 31 of the mobile terminal device 30 displays a candidate selection input screen showing the extracted candidates on the display unit 35 of the mobile terminal device 30. The processing unit 31 can accept selection input of the extracted candidates via the candidate selection input screen. FIG. 13 illustrates a candidate selection input screen DP2. The candidate selection input screen DP2 in FIG. 13 displays candidate presentation items 71 and a "reselect" item 72. Each candidate presentation item 71 displays a candidate for the extracted tourist spot. In the example of FIG. 13, each candidate presentation item 71 displays, from top to bottom, the following candidate destinations: "Shrine A2," "Temple A3," "Temple A4," "Restaurant T2," and "Souvenir Shop S2." A desired candidate can be selected from these candidates by operating the candidate presentation item 71. The "reselect" item 72 is operated when there is no candidate to be selected as a destination in each candidate presentation item 71.

[0068] In step S308, the processing unit 31 of the mobile terminal device 30 determines whether or not a selection instruction to select one of the extracted tourist spot candidates as a destination has been received via the candidate selection input screen DP2. For example, if the candidate presentation item 71 indicating "Shrine A2" is operated, the processing unit 31 determines that a selection instruction to select "Shrine A2" as a destination has been received. Also, for example, if the "Reselect" item 72 on the candidate selection input screen DP2 is operated, the processing unit 31 determines that a selection instruction has not been received. If a selection instruction has been received (Yes in step S308), the process S300 proceeds to step S309. If a selection instruction has not been received (No in step S308), the process S300 returns to step S303, and steps S303 to S308 are repeatedly executed until the desired destination is presented and selected on the candidate selection input screen DP2.

[0069] In step S309, the processing unit 31 of the mobile terminal device 30 transmits the received selection instruction to the server 10.

[0070] In step S310, the route information creation unit 55 of the server 10 creates route information indicating a route to the destination selected in the selection instruction. For example, the route information creation unit 55 searches for a route by car from the current location of the mobile terminal device 30 to the selected destination based on the map D121 using a well-known method, and creates route information based on the search results. By creating route information in this manner, when the user travels again by car to the same destination area as a previous trip using public transportation, the user can know the route by car to tourist spots that the user has not visited before.

[0071] In step S311, the output unit 54 of the server 10 transmits the route information to the mobile terminal device 30, thereby outputting the route information.

[0072] In step S312, the processing unit 31 of the mobile terminal device 30 displays a route information screen on the display unit 35. Fig. 14 shows an example of the route information screen DP3 when "Shrine A2" is selected as the destination. For example, the route information screen DP3 shows a route by car from the current location to "Shrine A2."

[0073] In step S313, the processing unit 31 of the mobile terminal device 30 determines whether an operation to terminate the route setting application has been accepted. For example, the processing unit 31 determines that an operation to terminate has been accepted when a predetermined end button on the mobile terminal device 30 is operated. If an operation to terminate has been accepted (Yes in step S313), the process S300 proceeds to step S314. If an operation to terminate has not been accepted (No in step S313), the process S300 returns to step S312.

[0074] In step S314, the processing unit 31 of the mobile terminal device 30 ends the route setting application. After step S314, the process S300 ends.

[0075] In an embodiment, the history creation device 40 includes a first acquisition unit 41 (history data acquisition unit) that acquires overall history data including pairs of usage details when an application was used on a terminal device on which the application is installed and location information indicating the location of the terminal device at the time of use, and a history creation unit 42 that creates sightseeing history data in which pairs including usage details related to sightseeing are identified from among the pairs included in the overall history data. With this configuration, it is possible to create sightseeing history data specialized for sightseeing, and by using this sightseeing history data, it is possible to provide more appropriate sightseeing services to the user.

[0076] In the embodiment, the usage details included in the overall history data D1 are usage details of an application that has a function of storing location information of the mobile terminal device 30 in the storage unit 32 of the mobile terminal device 30 when the application is used. According to this configuration, by creating the overall history data D1 using only the usage details of the application that has a function of storing location information, it is possible to suppress an increase in the volume of the overall history data D1.

[0077] In the embodiment, the history creation unit 42 creates the sightseeing history data by storing only the sets including the sightseeing-related usage details in the storage unit 12 of the history creation device 40. With this configuration, it is possible to suppress an increase in the capacity of the sightseeing history data D2.

[0078] The route setting device 50 (information output device) of the embodiment includes a second acquisition unit 51 that acquires sightseeing history data, which identifies pairs of sightseeing-related usage details among pairs of usage details when an application is used on a mobile terminal device 30 on which an application is installed and location information indicating the location of the mobile terminal device 30 at the time of use, and a destination area; an identification unit 52 that identifies tourist spots that the user has visited in the destination area based on the sightseeing history data; an extraction unit 53 that extracts tourist spots in the destination area that are different from the tourist spots the user has visited as tourist spot candidates; and an output unit 54 that outputs the extracted tourist spot candidates. This configuration allows the user to identify tourist spots that the user has not visited before in a destination area that the user has visited before. Furthermore, by using the sightseeing history data, it is possible to accurately present tourist spot candidates that the user has not visited before.

[0079] In this embodiment, the extraction unit 53 extracts tourist spots in the destination area that are not within walking distance of public transportation as tourist spot candidates. This configuration makes it possible to extract tourist spots that can be reached only by car.

[0080] In this embodiment, the second acquisition unit 41 further acquires the departure point and the expected arrival time, and the extraction unit 53 extracts as tourist spot candidates those tourist spots within walking distance of public transportation in the destination area, but for which there is no public transportation within walking distance that arrives by the expected arrival time when departing from the departure point. This configuration makes it possible to more appropriately extract tourist spots that can be reached only by passenger car.

[0081] The identification unit 52 further identifies the category of the visited tourist spot, and the extraction unit 53 extracts, from the tourist spots in the destination area, tourist spots that belong to the identified category of the visited tourist spot as tourist spot candidates. With this configuration, it is possible to extract tourist spots in a category that the user is interested in from tourist spots in the destination area that the user has not visited.

[0082] Several variations of the present disclosure will be described below.

[0083] In the embodiment, the sightseeing history data D2 includes only the sets that include sightseeing-related usage content from among the sets included in the overall history data D1, but is not limited to this. For example, the sightseeing history data D2 may be such that the sets that include sightseeing-related usage content are identified by marking the sets in the overall history data D1 that include sightseeing-related usage content.

[0084] In the embodiment, the history creation unit 42 identifies sets whose usage details include specific tourism-related keywords by searching the entire history data D1 using specific tourism-related keywords, but this is not limiting. For example, even sets whose usage details include the above keywords may be excluded from sets whose usage details include tourism-related usage details if they satisfy a predetermined condition. For example, even if the usage details include keywords for getting on or off, if the user gets on or off public transportation at the same stop facility a predetermined number of times (e.g., five times) or more, the set whose usage details include tourism-related usage details may be excluded from sets whose usage details include tourism-related usage details. This is because frequently used stop facilities are likely to be used for daily commuting or schooling, and not for tourism.

[0085] Priorities may be assigned to each type of tourism-related usage content. In this case, the history creation unit 42 may not identify, among pairs of locations within a predetermined distance in the overall history data D1, pairs containing usage content with a priority below a predetermined standard as pairs containing tourism-related usage content. For example, tourism-related usage content may be classified into types according to the usage content. For example, the types of usage content may be electronic payments for boarding or disembarking at a bus stop, electronic payments for souvenirs, electronic payments for food and drink, or social media posts with hashtags attached to tourist spots. For example, for each pair in the overall history data D1 whose usage content includes the specific keywords described above in step S203, the history creation unit 42 may determine the type of usage content based on the specific keywords included in the usage content and determine the priority based on the determination result. For example, consider a case where a lower priority is assigned to a type of usage content that is electronic payments for boarding or disembarking at a bus stop than to other types of usage content. In this case, if the above-mentioned set in the overall history data D1 includes usage details related to electronic payments for boarding or disembarking at a stop facility, and there is another set whose usage details include the above-mentioned specific keyword and include a location within a predetermined distance (e.g., several hundred meters) from the location of the stop facility where the boarding or disembarking occurred, the set including usage details related to electronic payments for boarding or disembarking at the stop facility does not need to be identified as a set including usage details related to tourism. For example, if a user disembarks at Tokyo Station and an electronic payment for eating and drinking is made within a predetermined distance from Tokyo Station, the set including usage details related to the electronic payment at Tokyo Station may be excluded from the set including usage details related to tourism. This configuration makes it possible to create tourism history data D2 that identifies usage details that are more important for tourism services while suppressing an increase in data volume.

[0086] In the embodiment, the second acquisition unit 51 acquires the current location as the departure location, and the route information creation unit 55 creates route information indicating the route from the current location to the selected destination, but this is not limiting. For example, the second acquisition unit 51 may acquire departure location information specifying an arbitrary departure location, and the route information creation unit 55 may create route information indicating the route from the specified departure location to the selected destination.

[0087] In the above embodiment, the history creation device 40 and the route setting device 50 are provided in the server 10, but this is not limiting, and the history creation device 40 and the route setting device 50 may be provided in the mobile terminal device 30.

[0088] In the embodiment, the mobile terminal device 30 is taken as an example of the terminal device, but the present invention is not limited to this, and a stationary terminal device such as a desktop personal computer may also be used.

[0089] The present disclosure has been described above with reference to the above-mentioned embodiments, but the present disclosure is not limited to the above-mentioned embodiments, and appropriate combinations or substitutions of the configurations shown in the embodiments are also included in the present disclosure. [Explanation of symbols]

[0090] 1...tourism service provision system, 10...server, 30...mobile terminal device, 40...history creation device, 41...first acquisition unit, 42...history creation unit, 50...route setting device, 51...second acquisition unit, 52...identification unit, 53...extraction unit, 54...output unit, 55...route information creation unit.

Claims

1. a history data acquisition unit that acquires overall history data including a combination of usage details when an application is used on a terminal device on which the application is installed and location information indicating the location of the terminal device at the time of use; a history creation unit that creates sightseeing history data in which the group including the usage content related to sightseeing is identified from the group included in the entire history data; A history creation device comprising:

2. Priorities are set for each type of tourism-related usage content, the history creation unit does not identify, among the pairs whose positions are within a predetermined distance in the entire history data, a pair including the usage content whose priority is equal to or lower than a predetermined standard as a pair including the usage content related to sightseeing; The history creation device according to claim 1 .

3. the usage details included in the overall history data are usage details of an application that has a function of storing the location information of the terminal device in a storage unit of the terminal device when the application is used; The history creation device according to claim 1 .

4. the history creation unit creates the sightseeing history data by storing only the set including the sightseeing-related usage content in a storage unit of the history creation device. The history creation device according to any one of claims 1 to 3.

5. On the computer, acquiring overall history data including a pair of usage details when the application was used on a terminal device on which the application was installed and location information indicating the location of the terminal device at the time of use; creating tourism history data in which the set including the usage content related to tourism is specified from the sets included in the entire history data; A history creation program that executes the following.

Images