Computer system, computer-implemented method, and computer program

Abstract

To provide new technology for providing transportation-related services to users of transportation facilities. [Solution] The disclosed computer system includes a database in which spots in the vicinity of a plurality of stops on a transportation route are associated with each of the stops, and first attribute information indicating attributes of the spots is associated with the spots. A processor of the computer system performs operations including identifying a stop or a route that matches a user's preference based on second attribute information of the stop or the route determined according to the first attribute information of the spots in the vicinity of the stop, and preference information indicating the user's preference regarding the spots.

Description

[Technical Field]

[0001] The present disclosure relates to a computer system, a computer-implemented method, and a computer program product for providing transportation-related services. [Background technology]

[0002] Patent Document 1 discloses a railway advertisement distribution system that transmits and displays advertisement data automatically inside a train. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2005-275233 Summary of the Invention

[0004] The present disclosure aims to provide a new technology for providing transportation-related services to users of transportation facilities.

[0005] One aspect of the present disclosure is a computer system. In one embodiment, the disclosed computer system may include a processor and a database in which spots in the vicinity of a plurality of stops on a transportation route are associated with each of the stops, and first attribute information indicating attributes of the spots is associated with the spots. The processor may be a computer system that performs operations including identifying a stop or a route that matches a user's preference based on second attribute information of the stop or the route determined according to the first attribute information of the spots in the vicinity of the stop, and preference information indicating the user's preference regarding the spots.

[0006] Another aspect of the present disclosure is a method or computer program.

[0007] Further details will be described in the following embodiments. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a configuration diagram of a computer system according to an embodiment. [Figure 2] FIG. 2 is a flowchart showing the procedure of the service providing process. [Figure 3] FIG. 3 is a diagram showing the data structure of the database. [Figure 4] FIG. 4 is an explanatory diagram of a railway-related database. [Figure 5] FIG. 5 is an explanatory diagram of a database related to spots. [Figure 6] FIG. 6 is an explanatory diagram of the user database. [Figure 7] FIG. 7 is an explanatory diagram of the calculation of the degree of agreement and the matching score. [Figure 8] FIG. 8 is an explanatory diagram of the display modes. [Figure 9] FIG. 9 is a data flow diagram of a computer system. [Figure 10] FIG. 10 is an explanatory diagram of an intelligent route map system and a vacant asset matching system. [Figure 11] FIG. 11 is an explanatory diagram of the screen in the first mode. [Figure 12] FIG. 12 is an explanatory diagram of the screen in the second mode. [Figure 13] FIG. 13 is an explanatory diagram of the screen in the second mode. [Figure 14] FIG. 14 is an explanatory diagram of various screens. [Figure 15] FIG. 15 is an explanatory diagram of the screen in the third mode. [Figure 16] FIG. 16 is an explanatory diagram of the screen in the third mode. [Figure 17] FIG. 17 is an explanatory diagram of the filter screen. [Figure 18] FIG. 18 is an explanatory diagram of a database related to landscape impressions. DETAILED DESCRIPTION OF THE INVENTION

[0009] 1. Overview of the Computer System, Computer-Implemented Method, and Computer Program

[0010] (A1) The computer system according to the embodiment includes: a processor; a database in which spots in the vicinity of a plurality of stops on a transportation route are associated with the stops, and first attribute information indicating attributes of the spots is associated with the spots; Equipped with The processor: second attribute information of the stop or the line determined according to the first attribute information of the spot around the stop; preference information indicating the user's preferences regarding the spot, identifying stops or routes that match the user's preferences; performing an action including It may be a computer system.

[0011] (A2) The operation is presenting the identified stops or the identified routes to a user; further comprising: The computer system may be the computer system described in (A1).

[0012] (A3) The operation is presenting the second attribute information of the identified boarding / alighting stop or the second attribute information of the identified route to a user; further comprising: The computer system may be the computer system described in (A1).

[0013] (A4) The operation is presenting to the user the spots associated with the identified stops or the spots associated with stops included in the identified route; further comprising: The computer system may be the computer system described in (A1).

[0014] (A5) The spot presented to the user is The first attribute information of the spot associated with the identified boarding / alighting area, or the first attribute information of the spot associated with the boarding / alighting stop included in the identified route; determined based on The computer system may be the computer system described in (A4).

[0015] (A6) The spot presented to the user is Determined based on preference information indicating a user's preference regarding the spot and the first attribute information of the spot associated with the identified boarding / deboarding stop, or is determined based on preference information indicating a user's preference regarding the spot and the first attribute information of the spot associated with the boarding / alighting stop included in the identified route. The computer system may be the computer system described in (A4).

[0016] (A7) The operation is presenting the spot associated with the identified stop or the spot associated with the stop included in the identified route to the user on a map while indicating the relationship between the spot and the stop; further comprising: (A1) The computer system according to (A1).

[0017] (A8) The boarding and alighting point that matches the user's preference is determined based on a degree of match; and The degree of match indicates a degree of match between second attribute information of each of the plurality of boarding and alighting stations and preference information of the user. The computer system may be the computer system described in (A1).

[0018] (A9) The operation is acquiring the first attribute information of the spot from a user; obtaining second attribute information indicating attributes of the boarding / alighting area associated with the spot from the acquired first attribute information; The second attribute information is stored in association with the boarding / alighting station or the route. further comprising: The computer system may be the computer system described in (A1).

[0019] (A10) the transportation means is a railway, The boarding / alighting area is a railway station. The computer system may be the computer system described in (A1).

[0020] (A11) The method according to the embodiment comprises: A computer-implemented method executed by a computer including a database in which spots in the vicinity of a plurality of stops on a transportation route are associated with the stops, and first attribute information indicating attributes of the spots is associated with the spots, second attribute information of the stop or the line determined according to the first attribute information of the spot around the stop; preference information indicating the user's preferences regarding the spot, identifying stops or routes that match the user's preferences; Including, It may be a computer-implemented method.

[0021] (A12) A computer program according to an embodiment includes: A computer includes a database in which a plurality of stops on a transportation route are associated with spots in the vicinity of the stops, and first attribute information indicating attributes of the spots is associated with the spots, second attribute information of the stop or the line determined according to the first attribute information of the spot around the stop; preference information indicating the user's preferences regarding the spot, identifying stops or routes that match the user's preferences; performing an action including It may be a computer program.

[0022] (B1) The computer system according to the embodiment includes: a processor; a database in which attribute information indicating attributes of a plurality of stops on a transportation route is associated with each of the stops; Equipped with The processor: determining a product related to a stop or a route that matches the user's preference based on the attribute information of each of the plurality of stops and preference information indicating the user's preference; presenting the determined product to the user; performing an action including It may be a computer system.

[0023] (B2) The product is a product that uses transportation available on a route to the stop or the route that matches the user's preference, The computer system may be the computer system described in (B1).

[0024] (B3) The product is a product that uses a transportation facility that allows the user to get off at the stop that matches the user's preference or at any stop included in the identified route. The computer system may be the computer system described in (B1).

[0025] (B4) The product is a product that uses a means of transportation that allows the user to get off at the stop that matches the user's preferences or any stop included in the route that matches the user's preferences, and that allows the user to board at the stop determined from the user's location information. The computer system may be the computer system described in (B1).

[0026] (B5) The product is a service that can be used at the stop that matches the user's preferences or at a spot near any stop included in the route that matches the user's preferences. The computer system may be the computer system described in (B1).

[0027] (B6) The operations further include presenting to the user a price for the product that is determined based on availability of the product. The computer system may be any one of the computer systems described in (B1) to (B5).

[0028] (B7) the transportation means is a railway, The platform is a railway station. The computer system may be the computer system described in (B1).

[0029] (B8) The preference information includes information indicating the user's preferences regarding spots in the vicinity of the boarding and alighting area. The computer system may be the computer system described in (B1).

[0030] (B9) the attribute information indicating the attribute of the boarding / alighting station is determined according to the attribute of the spot in the vicinity of the boarding / alighting station; (B8) The computer system according to (B8).

[0031] (B10) The method according to the embodiment comprises: A computer-implemented method executed by a computer including a database in which attribute information indicating attributes of a plurality of stops on a transportation route is associated with each of the stops, the method comprising: determining a product related to a stop or a route that matches the user's preference based on the attribute information of each of the plurality of stops and preference information indicating the user's preference; presenting the determined product to the user; Including, It may be a computer-implemented method.

[0032] (B11) A computer program according to an embodiment includes: a computer including a database in which attribute information indicating attributes of a plurality of stops on a transportation route is associated with each of the stops; determining a product related to a stop or a route that matches the user's preference based on the attribute information of each of the plurality of stops and preference information indicating the user's preference; presenting the determined product to the user; performing an action including It may be a computer program.

[0033] (C1) The computer system according to the embodiment includes: a database in which a plurality of spots in the vicinity of each of a plurality of stops on a transportation route are associated with the respective stops; a processor; Equipped with The processor: acquiring first attribute information indicating attributes of the spot; obtaining second attribute information indicating attributes of the boarding / alighting area associated with the spot from the acquired first attribute information; The second attribute information is stored in association with the boarding / alighting station or the route. performing an action including It may be a computer system.

[0034] 2. Examples of computer systems, computer-implemented methods, and computer programs

[0035] Hereinafter, the embodiments will be described in more detail with reference to the drawings.

[0036] <2.1 Hardware configuration example>

[0037] 1 shows a computer system 10 according to an embodiment. The system 10 is configured to execute information processing (service provision processing 111) for providing transportation-related services. The system 10 may be configured with one or more computers 100, 200.

[0038] 1 may include a server 100 (server computer). The server 100 provides services to other computers 200 (client computers) via a network 50 such as the Internet. The server 100 may also be called a service providing device.

[0039] The system 10 may include a client 200. The client 200 is a computer used by a user. Hereinafter, the client 200 will be referred to as a user terminal 200.

[0040] The user terminal 200 is, for example, a smartphone, a tablet, a personal computer, etc. The user operates the user terminal 200 to access the server 100 and can receive transportation-related services from the server 100.

[0041] The server 100 is composed of one or more computers. The computer constituting the server 100 may include a processor 110 and a storage device 120 connected to the processor 110. The computer constituting the user terminal 200 may also include a processor 210 and a storage device 220 connected to the processor 210.

[0042] The processor 110, 210 may be a CPU, a GPU, or another type of processor. The storage device 120, 220 may include, for example, a primary storage device and a secondary storage device. The primary storage device may be, for example, a RAM. The secondary storage device may be, for example, a hard disk drive (HDD) or a solid-state drive (SSD). The storage device 120, 220 may include a computer program 121, 221 executed by the processor 110, 210. The processor 110, 210 reads and executes the computer program 121, 221 stored in the storage device 120, 220.

[0043] The computer program 121 of the server 100 has program code that indicates instructions for causing the processor 110 to execute the service provision process 111. When the computer program 121 is executed by the computer (processor), the computer operates as the server 100 (service provision device) according to the embodiment and executes each step of the service provision process 111.

[0044] A database 300 is constructed in the storage device 120 of the server 100. The database 300 has various data used in the service provision process 111. Details of the database 300 will be described later.

[0045] The computer program 221 of the user terminal 200 is, for example, a native application program such as a mobile application. The computer program 221 is downloaded from a computer (app store) on the network 50 and installed in the user terminal 200. The computer program 221 cooperates with the server 100 to cause the user terminal 200 to execute information processing related to the service provision processing 111.

[0046] The computer program 221 of the user terminal 200 has program code that indicates instructions for causing the processor 210 to execute processing related to the service provision processing 111 in the user terminal 200. The processing related to the service provision processing 111 is, for example, processing related to the user interface in the user terminal 200, and may include input / output processing such as screen display and data input. Execution of the computer program 221 by a computer (processor) enables the computer to operate as the user terminal 200 according to the embodiment.

[0047] If the computer program 121 of the server 100 is configured as a web application that uses a web browser, the user terminal 200 can receive services provided by the service provision processing 111 if it has a web browser application. Therefore, the computer program 221 for the service provision processing 111 may be omitted.

[0048] The user terminal 200 may include an input / output device 230. The input / output device 230 has an input function for inputting data and an output function. The input / output device 230 is, for example, a touch panel display. The touch panel display can output screen display and the like, as well as accept input of data such as characters and accept operations such as user selections. The display of the user terminal 200 can be used to display on the screen a user interface provided by the applications 121, 221 of the system 10. The input function and the output function may each be configured by separate devices.

[0049] The user terminal 200 may include a location information acquirer 240. The location information acquirer 240 is, for example, a GNSS receiver such as a GPS. The location information acquirer 240 may acquire location information by a method other than GNSS, such as by using a Wi-Fi access point or by receiving location information input from a user.

[0050] <2.2 Example of service provision process>

[0051] 2 shows an example of the procedure for a service provision process 111 provided by the computer system 10 according to the embodiment. In the service provision process 111, a service related to transportation facilities is provided.

[0052] Here, "transportation" refers to a means of transportation that passengers can use to travel, such as trains and buses. Here, we consider transportation that has routes. "Routes" refer to transportation lines such as roads and railway lines that the transportation passes through.

[0053] A route has multiple stops. A "stop" is a place where passengers can get on and off, such as a train station or a bus stop. In the following, as an example, the transportation facility is a train, the route is a train line, and the stop is a train station.

[0054] The service provision process 111 according to the embodiment provides a service related to railways, as an example. In the embodiment, to provide the service, first, a database 300 of spots associated with the nearest station is created (step S21). Furthermore, to understand the user's preferences, the user's favorite spots are collected on the user interface of the application 121, 221 (step S22). The spots may be stores, factories, facilities, parks, tourist attractions, etc., and can be understood as any point on a map. In the database 300 according to the embodiment, spots in the vicinity of each station are associated with each of multiple stations. Then, based on the user's favorite spots (user preference information), stations / lines (areas) of interest to the user are estimated. Available assets may be recommended (presented) according to the stations / lines (areas) of interest (step S23). Furthermore, spots or stations that match the user's preferences may be presented to the user (step S24). Each of these steps S21 to S24 will be described in detail below.

[0055] <2.2.1 Database and its construction (Step S21)>

[0056] FIG. 3(A) shows the structure of data related to stations and spots in database 300. A transportation operator such as a railway company operates one or more lines. Accordingly, in database 300 according to the embodiment, an operator is associated with one or more lines. In database 300 of FIG. 3(A), as an example, "JR West Japan" is associated with lines such as "Kosei Line" and "JR Kyoto Line." Note that there may be multiple transportation operators.

[0057] Each line has multiple stations. Correspondingly, in the database 300 according to the embodiment, multiple stations are associated with each line. In the database 300 of FIG. 3(A), as an example, stations such as "Settsu Tomida" and "Takatsuki" are associated with a line called "JR Kyoto Line." Note that one station does not necessarily have to be associated with only one line, and one station may be associated with multiple lines.

[0058] Around stations, there are spots such as shops, factories, facilities, parks, and tourist attractions. Correspondingly, in the database 300 according to the embodiment, one or more spots are associated with each station. In the database 300 of FIG. 3(A), as an example, "Takatsuki" is associated with spots around the station such as "** Sake Brewery Co., Ltd.", "Aman Ruins Park," and "Settsu Gorge." Note that one spot does not have to be associated with only one station, and one spot may be associated with multiple stations. In other words, a certain spot may be associated with one or more stations (e.g., the nearest station) in the vicinity of that spot.

[0059] In the database 300 according to the embodiment, one or more pieces of attribute information are associated with each spot. Attribute information is information indicating the attributes of an object such as a spot, and is information added to the object in order to classify the object or distinguish between objects of the same type. The object to which attribute information is added may be a spot, or a station or a train line, as described below. Attribute information may also be called tag information. Attribute information associated with a spot may also be called "first attribute information" or "first tag information."

[0060] In the database 300 of FIG. 3(A), as an example, first attribute information of "#sake" is associated with "**Sake Brewery Co., Ltd." The first attribute information "#sake" indicates that "**Sake Brewery Co., Ltd." is a spot related to sake. Furthermore, first attribute information of "#ruins" is associated with "Aman Ruins Park." The first attribute information "#ruins" indicates that "Aman Ruins Park" is a spot related to ruins. "Settsu Gorge" is associated with first attribute information of "#cherry blossom spot." The first attribute information "#cherry blossom spot" indicates that "Settsu Gorge" is a cherry blossom spot.

[0061] The association of first attribute information with each spot may be performed with the cooperation of a user. For example, a user who visits a certain spot can operate the user terminal 200 to appropriately input tag information for that spot on the user interface of the system 10 according to the embodiment. The input tag information may be subjectively selected by the user. The system 10 registers the input tag information in association with the spot.

[0062] That is, a processor of system 10 having a database 300 in which multiple stations are each associated with multiple spots around the station may perform an operation of acquiring first attribute information (from a user, etc.) indicating the attributes of the spot, and storing the first attribute information in database 300 in association with the spot.

[0063] The system 10 may acquire data associated with attribute information for spots from an external system without relying on the user's cooperation and register the data in the database 300. The system 10 may also acquire other first attribute information related to the first attribute information acquired from the user's cooperation or an external system, and register the other first attribute information in the database 300. The other first attribute information may be, for example, a similar concept, a related concept, a superordinate concept, or a subordinate concept of the first attribute information acquired from the user's cooperation or an external system. The system 10 may refer to a knowledge base (concept base) containing many concepts that can be the first attribute information, and acquire similar concepts, etc., as the other first attribute information from the first attribute information acquired from the user's cooperation or an external system. For example, the system 10 may infer, from the first attribute information of "camping" and "park," the superordinate concept of these, as the other first attribute information. Furthermore, the system 10 can infer, from the first attribute information of "fireflies" and "astronomical observation," "starry sky," which is a related concept to these, as another piece of first attribute information.

[0064] In the database 300 according to the embodiment, each station is associated with a spot that is associated with first attribute information (first tag information). Therefore, it is possible to obtain second attribute information for a station from the first attribute information of a spot associated with the station. Therefore, in the database 300 shown in FIG. 3(A), it can be said that station attribute information is associated with the station. The second attribute information may also be called "second tag information."

[0065] Furthermore, in the database 300 according to the embodiment, spots are associated with stations associated with each line, and first attribute information is associated with the spots. Therefore, second attribute information of a line can be obtained from the first attribute information of a spot associated with the line via a station. Therefore, it can be said that attribute information of the line is associated with the line in the database 300. Note that in the database 300, stations associated with second attribute information (second tag information) are associated with the line, so that second attribute information of the line can also be obtained from the second attribute information of a station associated with the line.

[0066] In this way, the processor of the system 10 according to the embodiment may perform operations including obtaining, from the first attribute information, second attribute information indicating attributes of a station (boarding / deboarding platform) or line associated with the spot, and storing the second attribute information in association with the station or line. Furthermore, the system 10 may obtain, from the second attribute information obtained as described above, other second attribute information related to the second attribute information, and associate the other second attribute information with the station or line. The other second attribute information may be, for example, a similar concept, related concept, superordinate concept, or subordinate concept of the second attribute information already obtained. The method for obtaining the other second attribute information may be the same as the method for obtaining the other first attribute information.

[0067] The second attribute information of a station can be obtained as all or part of the set of first attribute information of spots associated with the station. For example, the spots associated with the station "Takatsuki," "** Sake Brewery Co., Ltd.", "Aman Ruins Park," and "Settsu Gorge," are assigned the first attribute information of "#Sake," "#Ruins," and "#FamousCherryBlossomSpots," respectively. Therefore, the second attribute information of the station "Takatsuki" can be all or part of the set of first attribute information of multiple spots, "#Sake," "#Ruins," and "#FamousCherryBlossomSpots."

[0068] The second attribute information of a line is obtained as all or part of the set of first attribute information of spots associated with stations associated with the line. For example, the second attribute information of a line called "JR Kyoto Line" may be all or part of the first attribute information of multiple spots (such as "** Sake Brewery Co., Ltd.", "Amano Ruins Park," and "Settsu Gorge") associated with multiple stations (such as Settsu Tomida and Takatsuki) included in the JR Kyoto Line.

[0069] The second attribute information of a station obtained as described above indicates the image / atmosphere of the station formed by the spots around the station. In other words, the second attribute information of a station indicates the image / atmosphere of the area around the station. Similarly, the second attribute information of a line indicates the image / atmosphere of the entire line formed by the spots around each station on the line. In other words, the second attribute information of a line indicates the image / atmosphere of the wide area surrounding the line.

[0070] Here, we assume that many of the spots surrounding the station "Takatsuki" are assigned either one of two first attribute information items: "#sake" or "#ruins." In this case, as an example, the second attribute information for the station "Takatsuki" can be limited to "#sake" and "#ruins." The other first attribute information assigned to the spots surrounding "Takatsuki" does not need to be included in the second attribute information for "Takatsuki." For example, as shown in Figure 3(B), the second attribute information representing the image of the station "Takatsuki" can be limited to "#sake" and "#ruins." In this way, by extracting second attribute information characteristic of the station, the image of the station can be more clearly defined.

[0071] Similarly, the second attribute information of the line can be obtained in the same way. For example, as shown in Figure 3(B), the second attribute information representing the image of the "JR Kyoto Line" can be simply "#Sake."

[0072] To extract characteristic second attribute information of a station or line, the system 10 can select, based on predetermined selection criteria, first attribute information that is attached to many of the surrounding spots from all of the first attribute information attached to multiple surrounding spots around the station, as the second attribute information of the station. This makes it possible to extract a strong image / atmosphere of the area around the station / line.

[0073] Furthermore, the image / atmosphere of an area around a station / line can change depending on changes in the spots in that area. For example, redevelopment around a station can cause old spots to disappear and new spots to appear. Therefore, in this embodiment, as an example, the image (second attribute information) of the area around a station / line is obtained from the first attribute information (image / atmosphere) of each spot within that area. As a result, even if the image / atmosphere of the area around a station / line changes in response to changes in the spots, once the first attribute information of the spots after the change is obtained, the second attribute information of the station / line can be updated. This makes it easier to respond to changes in spots. Furthermore, if the first attribute information of spots is obtained with the cooperation of users, it becomes even easier to respond to those changes.

[0074] In the embodiment, the image / atmosphere of a station / railway is registered in the database 300 as second attribute information. Therefore, the system 10 can suggest to a user of the system 10 information about stations / railways that match the user's preferences. For example, the system 10 can suggest to the user stations / railways that match the user's preferences and provide the user with information related to the stations / railways. Furthermore, if the user's preference is archaeological sites, the system 10 can refer to the database 300 and extract "Mozu" and "Tarumi" as stations associated with the attribute information "#Archaeological Sites," as shown in FIG. 3(B). Note that "Mozu" is one of the stations closest to the Oyama Tomb, and "Tarumi" is one of the stations closest to the Goshikizuka Tomb, both of which are associated with archaeological sites. Similarly, the system 10 can also extract railroad lines that match the user's preferences based on the user's preferences.

[0075] Furthermore, by providing the user with the image / atmosphere of the area surrounding the station / line using the system 10, the user can grasp the image / atmosphere of the area surrounding the station / line that he / she has never visited. This can thus gain the user's interest / concern for the area. A user who has an interest / concern for the area is expected to use the train, get off at a station in the area, and visit the area. Therefore, by using the present system 10, a new travel experience using the train can be provided to the user.

[0076] 4 and 5 show examples of a group of databases for realizing the structure of database 300 shown in FIG. 3. FIG. 4 shows a group of databases related to railways, and FIG. 5 shows a group of databases related to spots. Hereinafter, the group of databases shown in FIGS. 4 and 5 may be collectively referred to as "content database 310." Content database 310 constitutes a part of database 300.

[0077] Fig. 4(A) shows a route database. Fig. 4(A) shows, as an example, a route for which JR West is the railway operator. As shown in Fig. 4(A), the route database includes the following items: route ID, route name, "railway operator," "station ID belonging to the route," and "limited express ID."

[0078] The "line ID" and "line name" are data for identifying the line, and in Figure 4(A) the Kyoto Line (ID = L1), Kobe Line (ID = L2), and Osaka Loop Line (ID = L3) are shown as examples. The "railway operator" indicates the railway operator of the line. The "station ID belonging to the line" indicates the ID (identifier) ​​of a station associated with the line (a station included in the line), and can be used by the system 10 to identify a station associated with the line, etc. The "limited express ID" indicates the ID (identifier) ​​of a limited express train (a train that requires a limited express ticket) that runs on the line, and can be used by the system 10 to identify a limited express train that runs on the line, etc.

[0079] Figure 4(B) shows the station database. As an example, Figure 4(B) shows multiple stations associated with the JR Kyoto Line (ID=L1). As shown in Figure 4(B), the station database includes the following items: "Station ID," "Station Name," "Latitude and Longitude," "Address," "Railway Company Website," "Line ID," "Spot Tag ID," and "Limited Express ID that Stops at."

[0080] The "Station ID" and "Station Name" in Figure 4(B) are data for identifying stations, and Figure 4(B) shows Kyoto (ID=ST1), Nishioji (ID=ST2), and Mukomachi (ID=ST3), which belong to the JR Kyoto Line, as examples. "Latitude and Longitude" indicates the latitude and longitude of the station. The latitude and longitude of the station can be used to display the station on a map on the user interface of system 10, for example. "Address" indicates the address of the station. "Railway Company Website" indicates the URL of the railway company's website (homepage) that introduces information about the station.

[0081] The "Line ID" in Figure 4(B) indicates the ID of one or more lines associated with the station. For example, the Kyoto Line (ID=L1) is associated with the station "Nishioji." The "Spot Tag ID" indicates the ID of one or more pieces of tag information associated with the spot associated with the station. In other words, the "Spot Tag ID" in Figure 4(B) indicates the second attribute information of the station. For example, the spot tag IDs T6 and T9 are associated with the station "Mukomachi." Therefore, the image / atmosphere / characteristics of the station "Mukomachi" are indicated by the tag information T6 and T9.

[0082] 4(B) also indicates the ID of one or more pieces of tag information associated with a line. A collection of multiple spot tag IDs (IDs T1, T55, T2, T13, T6, T9) of multiple stations (IDs ST1 to ST3) included in the Kyoto Line (ID L1) can indicate second attribute information of the line.

[0083] The "Stopping express train ID" in Figure 4(B) indicates the ID of the express train that stops at that station, and can be used to identify express trains that stop at that station and allow passengers to board and disembark at that station.

[0084] FIG. 4(C) shows the express train database. The express train database can be used by the system 10 to search for express trains that use stations / lines that match the user's preferences. The system 10 can present products such as tickets for the searched express trains to the user. As shown in FIG. 4(C), the express train database includes the following fields: "Express Train ID," "Train Name," "Line ID," "Station IDs that Stop," "Vehicle ID," and "Remarks."

[0085] "Limited express ID" and "train name" are data for identifying limited express trains, and in Figure 4(C) Thunderbird (ID=EX1), Shirasagi (ID=EX2), Kuroshio (ID=EX3), and Haruka (ID=EX3) are shown as examples. "Route ID" indicates the ID of the route on which the limited express train runs, and can be used to identify limited express trains that run on each route. "Station ID where the train stops" can be used to identify stations where the limited express train stops and where passengers can board and disembark. "Vehicle ID used" indicates the vehicle ID used for the limited express train. "Notes" indicates note information about the limited express train.

[0086] Fig. 5(A) shows the spot information database. As shown in Fig. 5(A), the spot information database includes the following items: "spot ID," "spot name," "latitude and longitude," "address," "nearest station ID" (surrounding station ID), and "spot tag ID."

[0087] The "spot ID" and "spot name" in Figure 5(A) are data for identifying spots, and Figure 5(A) shows examples of several spots in Takatsuki City, Osaka Prefecture. "Latitude and longitude" indicates the latitude and longitude of the spot. The latitude and longitude of the spot can be used to display the spot on a map on the user interface of system 10, etc. "Address" indicates the address of the spot. "Nearest station ID" indicates the ID of one or more stations associated with the spot.

[0088] The "spot tag ID" in FIG. 5(A) indicates the ID of one or more tag information (spot tags) associated with the spot. That is, the "spot tag ID" in FIG. 5(A) indicates the first attribute information of the spot. As described above, the "spot tag ID" (first attribute information) can be associated with the spot with the cooperation of the user.

[0089] Fig. 5(B) shows a spot tag database. The spot tag database shows a list of spot tags (tag information). The spot tag database shown in Fig. 5(B) includes the following items: "spot tag ID," "tag name," "user ID," "tag description," and "spot ID."

[0090] "Spot tag ID" in Figure 5(B) indicates the ID of the spot tag (tag information). "Tag name" indicates the name of the spot tag. "User ID" indicates the ID of the user who (first) created the spot tag. A user can associate a spot tag that is already registered in the spot tag database with a spot, or can create an unregistered spot tag and associate it with a spot. Any user can associate a registered spot tag with a spot. "Tag description" includes a description of the spot.

[0091] The "spot ID" in FIG. 5(B) indicates the ID of one or more spots associated with the spot tag (tag information; first attribute information).

[0092] Fig. 5(C) shows a spot review database. The spot review database shows a list of reviews, comments, experiences, etc. posted by users about spots via the user interface of the system 10. The spot review database in Fig. 5(C) includes the following items: "review ID," "spot ID," "user ID," "spot tag ID," "review content," "posting date and time," and "related links."

[0093] "Review ID" indicates the ID of the review. "Spot ID" in Figure 5(C) indicates the ID of the spot to which the review is associated. "User ID" indicates the user who posted the review. "Spot tag ID" indicates the ID of the spot tag that the user attached to the spot along with the review. "Review content" includes text indicating the review, etc. "Posting date and time" indicates the posting date and time of the review. "Related links" include the URL of related links, etc.

[0094] <2.2.2 Collecting User Preference Information (Step S22)>

[0095] Returning to FIG. 2, the system 10 collects the user's favorite spots and the like on the user interface of the application used by the user in order to understand the user's preferences (step S22).

[0096] FIG. 6 shows a user database 320 that lists users who use the system 10. The user database 320 contains preference information for each user. As an example, a user registered in the database 320 has a computer program 221 installed on their own user terminal 200, and can register favorite spots and the like using the installed computer program 221 (application). The system 10 associates the user's favorite spots and the like with the user and stores them in the user database 320. The system 10 acquires preference information indicating the user's preferences based on the user's favorite spots and the like.

[0097] The user's preference information may be acquired based on the user's favorite spots, or may be acquired by analyzing text such as reviews / messages posted by the user using natural language analysis or artificial intelligence such as a neural network. The method for acquiring the user's preference information is not particularly limited.

[0098] The user database 320 shown in Figure 6 includes the following items: "User ID," "User name," "Gender," "Age," "Favorite spot ID," "Spot tag ID assumed to be favorite," "Station ID assumed to be favorite," "Transportation IC card ID," "Travel history," and "Point balance."

[0099] "User ID" and "user name" are data that identify a user, and "gender" and "age" are data related to the user.

[0100] The "favorite spot ID" indicates the ID of a favorite spot that the user has selected as a favorite on the interface of the system 10. In other words, the "favorite spot ID" indicates the ID of a spot that the user has determined matches their preferences. The "favorite spot ID" is an example of user preference information. The "favorite spot ID" may also include the ID of a favorite station / line. In other words, the "spot" here may include a station or a line.

[0101] The "spot tag ID presumed to be a favorite" indicates the ID of the spot tag (attribute information) associated with a specific spot or the like selected by the user as a favorite, or the ID of the spot tag selected by the user as a favorite. The user may select a spot as a favorite, or may select a spot tag as a favorite.

[0102] The "favorite spot ID" indicates a user's preference for a specific spot (e.g., ** Sake Brewery Co., Ltd.), while the "presumed favorite spot tag ID" indicates the user's preference (estimated value) for an attribute that a spot may have (e.g., "sake"). The "presumed favorite spot tag ID" is another example of user preference information. In FIG. 6, the "presumed favorite spot tag ID" for a user named "Yamada" is, for example, "T1 (0.7), T5 (1.0)." The numbers in parentheses following the spot tag IDs T1 and T5 indicate the estimated value of the user's favorite degree for the spot tag. In the case of "T1 (0.7), T5 (1.0)," the favorite degree of the spot tag T1 is 0.7, and the favorite degree of the spot tag T5 is 1.0, indicating that the estimated value of the favorite degree of the spot tag T5 is higher. For example, the estimated value of the favorite degree is calculated so that the more spot tags that the user has registered as favorites that share them in common, the higher the estimated value of the favorite degree. Furthermore, the system 10 may obtain other "spot tags" related to the "spot tag presumed to be a favorite" obtained as described above, and associate the IDs of the other "spot tags" with the user. The other "spot tags" are, for example, spot tags expressed as similar concepts, related concepts, superordinate concepts, or subordinate concepts of the "spot tag" already associated with the user. The method for obtaining other "spot tags" may be the same as the method for obtaining other first attribute information.

[0103] A user's preference for an attribute (e.g., "sake") indicates the user's preferences (interests) separate from preferences for specific spots. Therefore, by utilizing the user's preference for an attribute (e.g., "sake"), system 10 can identify spots / stations / railways, etc. that have attributes that match the user's preferences but that the user has not registered as favorites. For example, system 10 can infer that a user who has registered a sake brewery in Tomita and a sake brewery in Hokkaido as favorite spots is a sake lover. Furthermore, system 10 can infer that other spots / stations / railways that have the attribute of sake are also the user's favorites and present (recommend) them to the user as recommendations.

[0104] The "presumed favorite station ID" indicates the ID of a station that the system 10 determines matches the user's preferences. In FIG. 6, as an example, a user named Yamada (ID=U1) is associated with ST1 and ST2 as "presumed favorite station IDs." In other words, the stations that are presumed to be favorites for the user named Yamada (ID=U1) are Kyoto (ID=ST1) and Nishioji (ID=ST2).

[0105] In FIG. 6, for example, the "station IDs estimated to be favorites" for a user named "Yamada" are "ST1 (0.7), ST2 (0.4)." The numbers in parentheses following the station IDs ST1 and ST2 indicate the estimated favorite level (matching level) of the user for the station. In the case of "ST1 (0.7), ST2 (0.4)," the favorite level of Kyoto (ID=ST1) is 0.7, and the favorite level of Nishioji (ID=ST2) is 0.4, indicating that Kyoto has a higher estimated favorite level (higher favorite level). Note that how to estimate favorites and calculate the estimated favorite level (matching level) will be described later.

[0106] The user database 320 may also have a "route ID presumed to be a favorite" or a "spot ID presumed to be a favorite."

[0107] "Transportation IC card ID" indicates the ID of the transportation IC card held by the user, "Travel history" indicates the history of travel by the user using transportation, and "Point balance" indicates the balance of points awarded to the user in accordance with their use of the system 10.

[0108] 2.2.3 Recommending stations, tickets, spots, etc. according to user preferences (Step S23)

[0109] 2 again, the system 10 estimates stations, lines, or spots that the user is interested in based on the user's preference information such as the user's favorite spots (step S23). The system 10 may simply recommend (present) the estimated stations, lines, or spots to the user, but the system 10 according to the embodiment recommends (presents) tickets such as express tickets or other available assets according to the estimated stations or lines (step S23).

[0110] For example, as shown in FIG. 2, a user residing in Wakayama Prefecture has registered the tag information "#sake" and "#nature" in his / her favorites, and has also registered "Higashi Honganji Temple" near Kyoto Station as a favorite spot. Furthermore, "Higashi Honganji Temple" is assigned the tag information "#temples and shrines" (first attribute information). In this case, the system 10 refers to the content database 310 based on the user's preference information and estimates stations and other information that match the user's preferences. For example, based on the user's registration of "#sake" as a favorite, the system 10 can identify (infer) "Momoyama Station" (a JR Nara Line station in Fushimi Ward, Kyoto City, with many sake breweries in the surrounding area) that has the second attribute information "#sake" as a station that matches the user's preferences. Furthermore, the system 10 can identify (infer) one or more spots (sake breweries around Momoyama Station) that have the attribute "#sake" among the spots associated with the identified "Momoyama Station" as spots that match the user's preferences.

[0111] Furthermore, based on the tag information (first attribute information) of "#Temples & Shrines" for "Higashi Honganji Temple," which is the user's favorite spot, the system 10 can also identify (infer) "Tofukuji Station," which also has tag information (second attribute information) of "#Temples & Shrines" and is another station on the JR Nara Line where the identified "Momoyama Station" is located, as a station that matches the user's preferences. Furthermore, the system 10 can identify (infer) spots associated with the identified "Tofukuji Station" that have "#Temples & Shrines" (for example, "Tofukuji Temple" as a temple) as spots that match the user's preferences.

[0112] The system 10 can then present (recommend) the identified stations (Momoyama Station, Tofukuji Station) and spots (sake breweries and Tofukuji Temple around Momoyama Station) to the user on the application interface, which is expected to encourage the user to travel to the presented stations, spots, etc.

[0113] Furthermore, the system 10 can present (recommend) to the user on the application interface a product such as a reserved seat (available asset) on the Kuroshio Limited Express (Wakayama to Kyoto) to go to the identified station (Momoyama Station or Tofukuji Station). To determine the product to be presented to the user, the system 10 calculates a route from the user's location to the identified station using public transportation such as a train, based on, for example, the user's location information and the identified station's location information (such as latitude and longitude or address in the station database). The calculated route is, for example, a train route from Wakayama Station to Momoyama Station or Tofukuji Station via Kyoto Station. The user's location information is, for example, a latitude route or address in the user database 320, or location information acquired by a location information acquirer of the user terminal 200. The user's location information may also be calculated from the user's movement history. The process of calculating the route (route search) may be executed through API integration with an external system for route search. The calculated route may be one or more routes. Since there may be multiple departure points associated with the user's location information, a route search may be performed for each of the multiple departure points. Also, since there may be multiple destinations, a route search may be performed for each of the multiple destinations.

[0114] The system 10 then refers to the express train database in Fig. 4(C) and identifies express trains that can be used on the lines included in the route. The identified express train is, for example, the "Limited Express Kuroshio," and the Limited Express Kuroshio can be used on the determined route between Wakayama Station and Kyoto Station.

[0115] Furthermore, the system 10 refers to the vacant seat database 330 (vacant asset database) that shows vacant seats on express trains, checks whether there are any vacant reserved seats (vacant assets) on the identified express train, and if there are any vacant reserved seats (vacant assets), presents (recommends) a product, a ticket for that vacant reserved seat, for sale to users. This promotes the sale of tickets to users who are interested in the presented stations / spots.

[0116] Note that when deciding on a product (such as a ticket) to present to a user, the user's location information does not necessarily need to be taken into consideration. For products that are unrelated to the user's location information, the user's location information is unnecessary. Products that are unrelated to the user's location information include, for example, a hotel stay product around the identified station, or a round-trip ticket that can be used in a specific area that includes the identified station / line, regardless of the departure point.

[0117] When presenting (recommending) a product such as a ticket to a user, the system 10 may determine the price of the product according to availability (e.g., availability of reserved seats on a limited express train (vacancy rate)). The system 10 may determine a price according to availability (e.g., a 30% discount price for a reserved seat on the Kuroshio Limited Express) based on dynamic pricing or other pricing algorithms that increase the discount rate as the vacancy rate increases. In this case, sales of products that match the user's interests can be further promoted. The system 10 may also determine the product to present to the user by taking user preferences into consideration. For example, conditions related to user preferences (preference conditions) include the type of train (express train / local train), the type of seat (local / green), whether or not there are transfers and how many times, the type of ticket (unlimited rides, etc.), the season, date, and time of travel, the number of travelers, and the price range.

[0118] The products recommended by the system 10 are not limited to tickets, but may also be hotel accommodation products, or travel products that combine tickets and hotel accommodations, etc.

[0119] For example, the system 10 can recommend travel products related to sake and nature at discounted prices to a user who likes sake and nature. As described above, assume that a user lives in Wakayama Prefecture, has registered the tag information "#sake" and "#nature" as favorites, and has also registered "Higashi Honganji Temple" near Kyoto Station as a favorite spot. In this case, the system 10 can present the user with a list of sake breweries in the Fushimi area of ​​Kyoto City based on the user's preference information, and can also present and sell to the user a two-day, one-night travel product that includes a "hopping" trip between the identified stations, Momoyama Station and Tofukuji Station, on the JR Nara Line, and accept the purchase of the product.

[0120] By matching user preference information with the station database, it is also possible to develop travel products such as tickets for users with specific preferences (for example, users who like Japanese sake). After matching, the system 10 may also direct the user to an external electronic commerce site (EC site) that sells travel products or tickets. The user can be directed, for example, by presenting a link to the EC site to the user 10 on the application. By sending the user to a site such as an EC site, it is possible to receive a brokerage fee from that site.

[0121] The degree of match between a user's preferences and a station will be explained below. As explained with regard to the "station IDs presumed to be favorites" in the user database in Fig. 6, the system 10 predicts "stations presumed to be favorites" based on the estimated value (degree of match) of the user's favorite degree for a station.

[0122] For example, the degree of match is calculated from a station vector and a user vector, where the station vector is made up of tag information associated with a station, and the user vector is made up of tag information associated with a user.

[0123] For example, the station vector for each station registered in the station database of Figure 4(B) is expressed as (Tag01, Tag02, Tag03,...) = (Sake, Kofun, Park,...). Tag01, Tag02, Tag03,... indicate the presence or absence of each of the spot tags registered in the spot tag database of Figure 5(B), and take the value of 1 or 0, for example. For example, the station vector for Takatsuki Station is expressed as (1,1,1,0,0,...), which indicates that Takatsuki Station is associated with the spot tags Sake, Kofun, and Park, but no other spot tags. Similarly, the station vector for Sakai Station is expressed as (0,1,1,0,0,...), which indicates that Sakai Station is associated with the spot tags Kofun and Park, but no other spot tags. Note that each element of the station vector is not limited to the binary values ​​of 1 or 0, but can take any value greater than or equal to 0, for example. For example, each element of the station vector may indicate the number of times the corresponding spot tag has been associated with that station. Each element (each spot tag) of the station vector represents the weight (importance) of each spot tag at that station. For example, suppose a certain station is associated with about one spot with the "park" spot tag (number of spot tags = 1) and about 10 spots with the "sake" spot tag (number of spot tags = 10). In this case, "sake" is more important to that station than "park."

[0124] Furthermore, the user vector is expressed as (tag01, tag02, tag03,...) = (sake, kofun, park,...) for each user registered in the user database 320 of FIG. 6. Tag01, tag02, tag03,... indicate the presence or absence of each of the spot tags registered in the spot tag database of FIG. 5(B), and take the value of 1 or 0, for example. For example, user U1 is represented as (1,1,1,0,0,...), and for user U1, sake, kofun, and park are the spots indicated by the "favorite spot tag ID" of that user U1. Note that each element of the user vector is not limited to the binary values ​​of 1 or 0, but can take any value between 0 and 1, for example. Each element of the user vector (each spot tag) represents the weight (importance; favorite degree) of each spot tag for that user. For example, if a user has registered about five spots with the spot tag "kofun" as their favorite spots and about 10 spots with the spot tag "sake" as their favorite spots, then "sake" is more important to that user than "kofun."

[0125] The system 10 performs vector calculations using the station vectors and user vectors described above, and calculates the vector similarity as a match. For example, for user U1, the vector similarity is higher for Takatsuki Station than for Sakai Station. Therefore, a high match is expected for Takatsuki Station.

[0126] The degree of match (an estimate of the degree of interest in stations) for a user U1 is calculated for each of a plurality of stations. The system 10 determines stations with a degree of match greater than a predetermined standard as stations likely to interest the user. The system 10 registers the IDs of the determined stations as "presumed favorite station IDs" in the user database 320 of FIG. 6.

[0127] Assume that the system 10 presents a product called an "Osaka Loop Line Round Trip Ticket" to a user. The more stations (multiple stations on the Osaka Loop Line) that can be reached with this round trip ticket have a high degree of match with the user (stations that match the user's preferences), the more likely the user will purchase this round trip ticket. Furthermore, the more stations among multiple users have a high degree of match, the more likely the user will purchase the ticket. Therefore, the system 10 calculates the degree of match for each station for each of multiple users. The system 10 then calculates a matching score between a product such as the "Osaka Loop Line Round Trip Ticket" and the user based on the degree of match with the station, and can prioritize sales of the product to users with high matching scores or determine the price according to the matching score. Hereinafter, a method for calculating the matching score will be further described with reference to FIG. 7.

[0128] Fig. 7(A) shows an example of a station vector table showing the station vectors of each station. In Fig. 7(A), each element of the station vector is represented by an integer N equal to or greater than 0, rather than 1 or 0. N indicates the number of spot tags associated with the station. The larger the N, the greater the contribution the spot tag makes to forming the station's image.

[0129] FIG. 7(B) shows an example of a user vector table showing the user vector of each user. In FIG. 7(B), each element of the user vector takes a value between 0 and 1, but similar to FIG. 7(A), it may be expressed by the number N of spot tags associated with the user. The spot tag with a larger element value is more closely related to the user's preferences (interests). Note that each element of the user vector may take a binary value of 1 or 0.

[0130] Fig. 7(C) shows an example of the degree of match (the degree of match between a user and a station) calculated by vector calculation from the station vector in Fig. 7(A) and the user vector in Fig. 7(B). Fig. 7(C) shows the degree of match for each of multiple stations for each user.

[0131] Figure 7(D) shows a ticket vector that represents the relationship between tickets A, B, and C and the stations that can be reached with those tickets. In Figure 7(D), 1 indicates that the ticket can be used to reach that station, and 0 indicates that the ticket cannot be used to reach that station. Note that in Figure 7(D), "Origin" indicates the ticket's departure point, and if necessary, the ticket's departure point and the user's location information can be taken into consideration when matching.

[0132] The system 10 can calculate the vector similarity as a matching score between the ticket (product) and the user by vector calculation of the match vector in Fig. 7(C) and the ticket vector in Fig. 7(D). The system 10 can sell products preferentially to users with high matching scores and determine prices according to the matching scores.

[0133] A scenario for recommending a product (ticket) to a user may be as follows. Here, a scenario for recommending a limited express train based on a user's favorite spot tag (tag information) will be described. First, the user selects tag information of interest to the user (for example, a botanical garden) on the user interface of the system 10 according to the embodiment. When the user selects the tag information (botanical garden), the system 10 associates the tag information with the user and saves it. The system 10 also displays, on the user interface, a list of stations associated with spots associated with the tag information (for example, XX botanical garden). The station list may be, for example, "Station A, Station B, Station C." Along with the display of the list of stations, tag information (second attribute information) associated with the stations or spots associated with the stations (botanical gardens or other spots) may also be displayed.

[0134] The user registers some of the spots, such as botanical gardens, associated with the displayed stations as favorites (for example, XX Botanical Garden at Station A and △△ Botanical Garden at Station B). The system 10 stores the favorited spots and their tag information in association with the user.

[0135] The system 10 selects an express train (e.g., the Thunderbird Express) that passes through Station A or Station B, which is the nearest station to the favorited spot (XXXX Botanical Garden or △△ Botanical Garden). The system 10 calculates a discount rate according to the time when the express train has low availability (operating rate), and presents the user with a discounted ticket.

[0136] Next, a scenario for recommending an unlimited ride ticket will be described. Here, it is assumed that the user has registered spots around Kyoto Station as favorites. In this case, it can be said that the user is interested in the area around Kyoto Station. Therefore, the system 10 can recommend to the user a ticket that allows unlimited rides around Kyoto Station and its surrounding areas. The system 10 may sell tickets at a fixed price, or may provide the user with an unlimited ride ticket for free or at a discount if the user purchases a limited express ticket to Kyoto Station.

[0137] Next, a scenario will be described in which a mode of transportation or a ticket that will allow the user to travel around spots of interest to the user is recommended. Here, too, it is assumed that the user has registered spots around Kyoto Station as favorites. In this case, it can be said that the user is interested in the area around Kyoto Station. Therefore, in order to encourage the user to go to Kyoto Station, the system 10 recommends a limited express train that runs on the way from the user's nearest station to Kyoto Station. The system 10 can also suggest a round-trip ticket (unlimited rides) around Kyoto Station to travel around the surrounding area.

[0138] <2.2.4 Presentation of recommended spots / stations (Step S24)>

[0139] 2, the system 10 presents the user with spots, stations, etc. that match the user's preferences (step S24). Step S24 can be performed during a trip using the ticket, etc. presented in step S23, during other trips, before such trips, during daily use of transportation, or at any other timing.

[0140] The system 10 can display spots, stations, etc., presented to the user on a map showing railway lines on the display of the user terminal 200. As shown in Fig. 8, the system 10 has a first mode 12A and a second mode 12B for displaying spots, stations, or lines. The two modes can be switched by a user operation.

[0141] The first mode 12A may also be referred to as a current location-centered mode or an ant's eye view mode. In the first mode 12A, a map is displayed centered on the user's current location. In the first mode 12A, when the user approaches a spot registered in the database 300 while riding a train, the user is notified of this. The spots notified in the first mode 12A are, for example, spots registered in the spot information database shown in FIG. 5(A) that the system 10 determines to match the user's preferences or spots that the system 10 determines should be presented to the user.

[0142] The second mode 12B is also called a browsing mode or a bird's-eye view mode. In the second mode 12B, a map of any location selected by the user can be displayed at any scale. The second mode 12B can be used for destination exploration and trip planning.

[0143] In addition to the first mode 12A and the second mode 12B, the system 10 can also display a third mode 12C. The third mode 12C may also be referred to as a content mode. In the third mode 12C, posts, for example, may be displayed.

[0144] Further details of the first mode 12A, the second mode 12B and the third mode 12C will be described below.

[0145] <2.3 Information processing data flow for service provision processing>

[0146] FIG. 9 shows the data flow of information processing in the service provision processing described in "2.2 Example of Service Provision Processing." The system 10 determines the content (maps, spots, stations, routes, etc.) to be presented in one of the first mode 12A, second mode 12B, and third mode 12C using the presented content control unit 14, and executes the content presentation processing 12 to present the content to the user U1 in one of the modes 12A, 12B, and 12C via the user interface 11A. The content to be displayed is obtained from the content database 310. The content database 310 is managed by the database management system 17.

[0147] For example, the user U1 can view the displayed screen of the user interface 11A and operate the screen to switch the display or mode, or register a spot or spot tag as a favorite.

[0148] The user's favorite registration is accepted by the user information management unit 15 and registered in the user database 320. The presented content control unit 14 can determine content (spots, stations, etc.) that matches the user's preference information based on the user's favorite registration.

[0149] Furthermore, the vacant asset matching unit determines products (and prices) that match the user's preference information based on the user's preference information obtained based on the user's favorite registration, and provides the determined products (and prices) to the presented content control unit 14. When determining the products (and prices), the vacant seat database 330 may be referenced. The presented content control unit can present the products (and prices) to the user on the user interface 11A displayed on the user terminal 200.

[0150] The system 10 can accept postings of reviews, experiences, etc. of spots from users U2 and U3 who have visited the spots. Reviews, experiences, etc. are input through a user interface 11B displayed on the user terminal 200. The inputs of reviews, experiences, etc. are accepted by the social content processing unit 13 and registered in the content database 310.

[0151] <2.4 Intelligent Route Map System and Vacant Asset Matching System>

[0152] The system 10 according to the embodiment described above can be understood functionally as a combination of an intelligent route map system 20 and a vacant asset matching system 30, as shown in FIG.

[0153] The intelligent route map system 20 is used, for example, as a system for forming a community that motivates rail travel. The intelligent route map system 20 is based on an interactive route map 20A (objective data) corresponding to absolute positions, and further includes subjective spot data 20B by users, etc., and subjective rail-related data 20C such as station information and line information by users, etc.

[0154] The interactive route map 20A corresponding to absolute positions is composed of a map (for example, a measured map) to which objective data (spot data) such as spot names and location information, and objective data (railway data) such as stations, lines, and railway operators are added. The stations and lines indicated by the objective railway data are arranged (displayed) on the map (measured map).

[0155] The intelligent route map system 20 is capable of displaying subjective spot data 20B and subjective railway-related data 20C on an interactive route map 20A that corresponds to an absolute position.

[0156] In the intelligent route map system 20, spot data 20B is associated with railway-related data 20C (stations or lines), and spots can be displayed on the map in association with stations or lines on the map. Furthermore, the intelligent route map system 20 can refer to the user database 320 to display spots and the like that match the user's preferences on the map.

[0157] A user can use the intelligent transit map system 20 to explore / browse the map on which the transit map is located to find places the user wants to go.

[0158] The vacant asset matching system 30 executes a matching process 16 between a user's preferences and vacant seats (vacant assets) by referring to a vacant asset database such as a train vacant seat database 330 based on the user's preferences, etc. The vacant asset matching system 30 can match vacant seats according to the user's situation, which is understood as the user uses the system 10, and provide them to the user at a discount. The user's situation used for matching includes the user's preferences as well as other information in the user database 320 (such as travel history) or the user's current location.

[0159] By using the intelligent route map system 20, users of the system 10 can be motivated to travel by train, and can purchase tickets suggested by the available asset matching system 30 for the motivated trip and enjoy the trip.

[0160] <2.5 Display modes 12A, 12B, 12C>

[0161] The first mode 12A, second mode 12B, and third mode 12C described above with reference to Fig. 8 will now be described. Fig. 11 shows an example of a screen for the first mode 12A, Figs. 12 and 13 show example screens for the second mode 12B, Fig. 14 shows example screens that can be displayed by operations from the screens for the first mode 12A and second mode 12B, and Figs. 15 and 16 show example screens for the third mode 12C. Fig. 17 shows an example of a filter screen for the first mode 12C.

[0162] 11(A), in the first mode 12A, a map is displayed with the user's current location at the center. In the first mode 12A, the system 10 notifies the user on the train of content (spots) around the current location, encouraging the user to look out the window.

[0163] When the user approaches a content (spot) that exists around the user's current location (preferably in the direction of travel, i.e., ahead) by more than a certain threshold, the user receives a notification from the system 10 on the user interface (on the screen) that the content (spot) exists in the vicinity. As shown in FIG. 11(A), the spot and information about the spot may be displayed on a map. For example, as shown in FIG. 11(B), the system 10 notifies the user of the direction (e.g., left or right) where the spot is located, taking into account the user's direction of travel.

[0164] In the first mode 12A, the user may be able to select either (1) a state in which the map is rotated so that the direction of travel is at the top (north) of the screen, or (2) a state in which the map is used with the east-west, north-south, and north-south directions fixed. Furthermore, the system 10 may automatically activate the first mode 12A when it determines that the user is on a train or other form of transportation (mobile vehicle) based on the way the user's location information changes or an acceleration sensor or the like. The content to be notified is manually or automatically narrowed down to the user's preferences. Figure 17 shows a filter screen that is displayed when the user presses the filter button displayed on the first mode 12A screen. By operating the filter screen, the notified content can be filtered by spot tags. This automatically filters out only information that matches the user's preferences. On the filter screen, in addition to spot tags that are presumed to be the user's favorites, other spot tags can also be selected as filtering conditions.

[0165] As shown in FIG. 12, the second mode 12B provides an intelligent route map to help the user plan their rail journey.

[0166] As shown in Figures 12(A) and 12(B), in second mode 12B, stations and tracks on a map of Japan are highlighted, and a screen is displayed in which a route map is overlaid on the map of Japan (the map is annotated with station names, route names, and railway operator names). This makes stations and other features more prominent on the map than in a normal map application. Therefore, the intelligent route of the embodiment is suitable for planning rail travel taking stations and routes into consideration. In second mode 12B, the granularity of the displayed content (railway operator name > route name > station name) changes (the displayed information is thinned out) according to the degree of zoom and pan, as shown in Figures 13(A), (B), and (C).

[0167] When the user selects a line or station name on the screens shown in Figures 12(A) and 12(B), a station name slider indicating the "order of stations" on the line is displayed on the screen, as shown in Figure 12(C). When the user selects a line, the station name displayed in the center of the station name slider will be the nearest station to the center of the map. Also, when the user selects a station name, the station name displayed in the center of the station name slider will be the selected station. When the user slides the station name slider to change the station name displayed in the center, the map also moves in tandem, so that the station becomes the center point. When the map moves (e.g., from Osaka Station to Fukushima Station), the action can follow the track trajectory. This creates the effect of creating the feeling that the movement of the map is a train running on the tracks. Note that if one station has multiple lines, the user can switch the station name slider by operating it.

[0168] FIG. 13(D) shows the screen (station map) when the user selects (clicks or taps) a station displayed on the screen of second mode 12B (for example, the screen of FIG. 12(C)) (a spot may also be selected). FIG. 13(D) shows a state in which "Akabane Station" has been clicked and spots around Akabane Station are displayed. In this case, the selected station, "Akabane Station," is displayed at the center of the screen. Spots around Akabane Station are displayed connected by links (lines) that indicate their relationship with Akabane Station. By displaying the stations and spots connected by links, the user can understand the relationship between the stations and the spots, that is, the displayed spots are associated with the stations. In addition, the travel time from the station (for example, the required walking time) is displayed for each spot, so the user can also understand the relationship between the station and the spot from the travel time.

[0169] The screen in Figure 13(D) displays the selected station name (Akabane Station) and the spot tag (second attribute information) associated with the selected Akabane Station. In Figure 13(D), the spot tags displayed are "standing bar," "public bath," and "housing complex." By displaying these spot tags, the user can grasp the image, atmosphere, and characteristics of the selected Akabane Station.

[0170] When a user selects a spot displayed on the screen of Fig. 13(D) or the like, the screen transitions to a screen displaying spot information (Fig. 14(A)). The spot information screen shown in Fig. 14(A) is a screen that introduces detailed information about the selected spot, and displays an image of the spot, reviews posted about the spot, a spot tag (first attribute information), etc.

[0171] When a user selects a station displayed on a screen such as Figure 13(D), the screen transitions to a station portal screen (Figure 14(B)) that displays station information. The station portal screen shown in Figure 14(B) is a screen that introduces the selected station (Akabane Station), and displays an image of the station, the lines that pass through the station, tags (second attribute information) associated with the station, and so on. In Figure 14(B), the tags displayed are "standing bar," "public bath," and "housing complex." The station portal screen displays spots around the station.

[0172] When a user selects a tag (attribute information) displayed on a screen such as Figure 14(B), the screen transitions to a spot tag portal screen (Figure 14(C)). The spot tag screen is a screen that explains the selected tag (standing bar). The spot tag portal screen displays the stations associated with the selected tag (attribute information). Figure 14(C) displays Akabane Station, Namba Station, and Ishikawacho Station as stations associated with the selected "standing bar."

[0173] The Spot Tag Portal screen allows users to select a line so that they can adjust the stations that are displayed. Users can also select the display order (e.g., closest to the current location).

[0174] When the user selects a line displayed on the screen of Fig. 13(D) or the like, the screen transitions to a line information navigation screen (Fig. 14(D)) that displays line information. The line information navigation screen of Fig. 14(C) displays information such as the stations that belong to that line (along the line), the line operator, and the area surrounding that line.

[0175] As shown in Figures 15 and 16, various timelines are displayed in the third mode 12C. Figure 15(A) shows a timeline showing the content posted by the user himself, and Figure 15(B) shows the timelines of people followed by the user.

[0176] 16(A) is a timeline of posts related to spot tags. For example, when a user selects a spot tag on the screen in the second mode 12B (or the screen in the first mode 12A), posts related to spots or stations associated with the selected tag are displayed. Also, if a tag that is presumed to be a favorite of a certain user is "ocean," posts related to spots or stations associated with the tag "ocean" may be displayed.

[0177] 16(B) is a timeline of posts related to stations. For example, when a user selects a station on the screen of the second mode 12B (or the screen of the first mode 12A), posts related to the selected station or spots associated with that station are displayed. Also, if a station that is presumed to be a favorite of a certain user is "Akabane Station," posts related to "Akabane Station" or spots associated with Akabane Station (spots for which Akabane Station is the nearest station) are displayed.

[0178] <2.6 Landscape Impressions>

[0179] The following describes the view impression: The system 10 can accept registration from users regarding their impressions of a view, and can notify users of their view impressions.

[0180] Here, "scenery" refers to spots other than those that can be indicated by proper nouns such as facility names. Examples of scenery include the cherry blossom trees along the Katsura River and the night view of Maishima. Here, as an example, the scenery is the scenery seen from the train window while riding on a train. Also, as an example, the scenery is a scene that a user finds memorable while riding on a train and is posted and registered in the system 10.

[0181] As shown in FIG. 11, the system 10 can display spots near the user's current location on the screen of the first mode 12A while the user is riding on a train. In FIG. 11, in addition to spots that can be specified by proper nouns such as facility names, registered landscapes (landscape impressions) are also presented to the user. In FIG. 11, landscape impressions are indicated by heart marks (impression tags). The landscapes in this case are landscapes that can be seen from the train window while riding on the train, so the landscape impression marks (impression tags) are displayed on the line where the landscapes can be seen. Therefore, when the user's current location approaches the displayed impression tag, the user can enjoy the landscape from the train window.

[0182] Furthermore, if a user sees an impressive view while riding, the user can operate the impression tag posting button in Figure 11, which allows the system 10 to register the user's current location at that time as a view (view impression).

[0183] 18 shows a database relating to landscape impressions. The database relating to landscape impressions is an example of a database included in the database 300 of the system 10.

[0184] FIG. 18(A) shows a landscape impression posting database. The landscape impression posting database is a database for registering landscapes (landscape impressions) posted by users. The system 10 registers landscape impressions received from users in the database of FIG. 18(A). The landscape impression posting database includes the following items: "Landscape impression posting ID," "User ID," "Latitude and longitude," "Posting date and time," "Impression tag ID," "Related links," and "Public / Private." Note that the landscape impression posting database is not limited to data posted by users, and may also include data set by a system administrator or the like.

[0185] "Landscape impression posting ID" is the ID of the landscape impression posted by the user. "User ID" is the ID of the user who posted the landscape impression. "Latitude and longitude" is the location where the landscape impression was posted, which is usually a location on a route. "Posting date and time" is the date and time when the landscape impression was posted. "Impression tag ID" indicates the ID of the tag information (attribute information) of the landscape impression (see Figure 18 (C)). "Related link" indicates a link (URL) related to the landscape. "Public / Private" is setting information for whether the landscape impression is made public to others.

[0186] 18(B) shows a view impression notification database. The view impression notification database is used by the system 10 to notify users of view impressions on a screen (such as the first mode 12A in FIG. 11). The view impression notification database is generated for notifying users of view impressions based on the contents of the view impression posting database, which is based on posts from users. If a view impression matches the conditions shown in the view impression notification database, the system 10 notifies the user of the view impression (for example, displays it on the screen).

[0187] The landscape impression notification database includes the following items: "Landscape impression notification ID," "Latitude and longitude," "Impression tag ID," "Viewable period," and "Viewable time period."

[0188] The "landscape impression notification ID" indicates the ID of the landscape impression (ID for notification). Since multiple users may post about the same landscape, there may be multiple landscape impression posts (landscape impression post IDs) for the same landscape. On the other hand, the "landscape impression notification ID" may have a one-to-one correspondence with the landscape impression post ID, but is preferably an ID when multiple landscape impression posts for the same landscape are grouped together. Multiple landscape impressions for the same landscape may be extracted, for example, as those with approximately the same post location (latitude and longitude).

[0189] "Latitude and longitude" indicates the location (latitude and longitude) of the landscape indicated by the "Landscape Impression Notification ID." The "latitude and longitude" here is obtained, for example, from the "latitude and longitude" in the landscape impression post database. For example, one "latitude and longitude" for notification of that landscape can be obtained from the "latitude and longitude" of one or more posts about the same landscape (for example, by clustering).

[0190] "Impression tag ID" indicates the ID of the tag information (attribute information) of the landscape impression to be notified (see Figure 18(C)). Here, the "impression tag ID" is obtained from the "impression tag ID" of the same landscape in the landscape impression post database. For example, one or more "impression tag IDs" for notifying the landscape can be obtained from the "impression tags" of one or more posts for the same landscape (for example, by clustering).

[0191] The "time when it can be seen" and the "time period when it can be seen" indicate the timing when the landscape can be seen. The landscape may be visible only during certain times of the day or certain seasons. For example, a certain landscape may be visible only during the day, only at night, or only in spring. It is preferable to notify the user when the landscape can be seen. For this reason, the system 10 notifies the user of the landscape at a timing that matches the timing when the landscape can be seen, such as the "time when it can be seen" and the "time period when it can be seen."

[0192] The timing when the landscape is visible can be determined from the "posting date and time" of one or more posts about the same landscape (for example, by clustering). If the posting dates and times are concentrated in a particular season, time period, or day, the system 10 can determine the concentrated time period as the timing when the landscape is visible and register it in the database.

[0193] 18(C) shows the impression tag database. The impression tag database is a database related to tag information (attribute information) of landscape impressions. The impression tag database has the following fields: "impression tag ID," "impression name," and "landscape impression post ID."

[0194] "Impression tag ID" indicates the ID of the tag information of the landscape impression. "Impression name" indicates the name of the impression. "Landscape impression post ID" indicates the ID of the landscape impression post that has the impression tag ID.

[0195] The system 10 generates a landscape impression notification database from the landscape impression posting database of Fig. 18(A) and notifies the user of a landscape (landscape impression) based on the notification database. The notification is made, for example, when the user's current location approaches the "latitude and longitude" in the notification database and the timing matches the "period when the view can be seen" and "time period when the view can be seen." Note that the notification may be made at other times.

[0196] The scenic impression may be associated with a spot that the user (poster) is presumed to be looking at. For example, if a scenic impression is registered on a route near a park, the scenic impression may be associated with the spot called "park."

[0197] The present invention is not limited to the above-described embodiment, and various modifications are possible. [Explanation of symbols]

[0198] 10: Computer Systems 11A: User Interface 11B: User Interface 12: Content presentation processing 12A: First mode 12B: Second mode 12C: 3rd mode 13: Social content processing section 14: Presentation content control section 15: User information management section 16: Matching process 17: Database Management System 20: Intelligent route map system 20A: Route map 20B: Data 20C: Railway-related data 30: Vacant Asset Matching System 50: Network 100: Server 110: Processor 111: Service provision processing 120: Storage device 121: Computer Programs 200: User terminal 210: Processor 220: Storage device 221: Computer Programs 230: Input / output device 240: Location information acquisition device 300: Database 310: Content database 320: User database 330: Vacancy database

Claims

1. a processor; a database in which spots in the vicinity of a plurality of stops on a transportation route are associated with the stops, and first attribute information indicating attributes of the spots is associated with the spots; Equipped with The processor: determining second attribute information to be presented to a user of the stop or the route according to the first attribute information of the spot around the stop; Accepting registration of a favorite spot of a user, and acquiring preference information indicating a preference of the user regarding the spot based on the first attribute information of the favorite spot of the user; Identifying a stop or a route that matches the user's preference based on the second attribute information for the stop or the route obtained according to the first attribute information of the spots around the stop and the preference information; presenting the second attribute information for user presentation of the identified boarding / alighting station to the user together with the identified boarding / alighting station, or presenting the second attribute information for user presentation of the identified route to the user together with a route map including the identified route; performing an action including Computer system.

2. The operation is presenting to the user the spots associated with the identified stops or the spots associated with stops included in the identified route; further comprising:

10. The computer system of claim 1.

3. The spot presented to the user is The first attribute information of the spot associated with the identified boarding / alighting area, or the first attribute information of the spot associated with the boarding / alighting stop included in the identified route; determined based on 3. The computer system of claim 2.

4. The spot presented to the user is Determined based on the preference information and the first attribute information of the spot associated with the identified boarding / deboarding area, or is determined based on the preference information and the first attribute information of the spot associated with the boarding / alighting stop included in the identified route.

3. The computer system of claim 2.

5. The operation is presenting the spot associated with the identified stop or the spot associated with the stop included in the identified route to the user on a map while indicating the relationship between the spot and the stop; further comprising:

10. The computer system of claim 1.

6. The boarding and alighting station that matches the user's preference is determined based on a degree of match; and The degree of match indicates a degree of match between the second attribute information to be presented to the user and the preference information for each of the plurality of boarding and alighting stations.

10. The computer system of claim 1.

7. The operation is acquiring the first attribute information of the spot from a user; obtaining second attribute information to be presented to the user, which indicates an attribute of the boarding / alighting station associated with the spot, from the acquired first attribute information; The second attribute information to be presented to the user is stored in association with the boarding / alighting station or the route. further comprising:

10. The computer system of claim 1.

8. the transportation means is a railway, The boarding / alighting area is a railway station.

10. The computer system of claim 1.

9. 1. A computer-implemented method executed by a computer including a database in which spots in the vicinity of a plurality of stops on a transportation route are associated with the stops, and first attribute information indicating attributes of the spots is associated with the spots, determining second attribute information to be presented to a user of the stop or the route according to the first attribute information of the spot around the stop; Accepting registration of a favorite spot of a user, and acquiring preference information indicating a preference of the user regarding the spot based on the first attribute information of the favorite spot of the user; Identifying a stop or a route that matches the user's preference based on the second attribute information for the stop or the route obtained according to the first attribute information of the spots around the stop and the preference information; presenting the second attribute information for user presentation of the identified boarding / alighting station to the user together with the identified boarding / alighting station, or presenting the second attribute information for user presentation of the identified route to the user together with a route map including the identified route; Including, Computer-implemented methods.

10. a computer including a database in which spots in the vicinity of a plurality of stops on a transportation route are associated with the stops, and first attribute information indicating attributes of the spots is associated with the spots; determining second attribute information to be presented to a user of the stop or the route according to the first attribute information of the spot around the stop; Accepting registration of a favorite spot of a user, and acquiring preference information indicating a preference of the user regarding the spot based on the first attribute information of the favorite spot of the user; Identifying a stop or a route that matches the user's preference based on the second attribute information for the stop or the route obtained according to the first attribute information of the spots around the stop and the preference information; presenting the second attribute information for user presentation of the identified boarding / alighting station to the user together with the identified boarding / alighting station, or presenting the second attribute information for user presentation of the identified route to the user together with a route map including the identified route; performing an action including Computer program.

Images