Computer systems, computer implementation methods, and computer programs

The system addresses the lack of personalized transportation services by associating boarding points with surrounding spots and user preferences, offering tailored route suggestions that enhance user engagement and interest in transportation services.

JP2026115874AActive Publication Date: 2026-07-09JR WEST INNOVATIONS CO LTD

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
JR WEST INNOVATIONS CO LTD
Filing Date
2024-12-27
Publication Date
2026-07-09

AI Technical Summary

Technical Problem

Existing transportation services lack the ability to personalize recommendations based on user preferences for boarding and alighting points and surrounding spots, failing to enhance user experience through tailored transportation options.

Method used

A computer system and method that associates boarding/alighting points with surrounding spots, using attribute information to identify and present routes and stations that match user preferences, incorporating user input and external data to dynamically update and suggest relevant transportation products.

Benefits of technology

Enhances user experience by providing personalized transportation services that align with individual preferences, increasing interest in and utilization of transportation routes and surrounding areas.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026115874000001_ABST
    Figure 2026115874000001_ABST
Patent Text Reader

Abstract

We will provide new technologies to offer transportation-related services to users of public transportation. [Solution] The disclosed computer system includes a database in which each of a plurality of boarding and alighting stations on a transportation route is associated with a spot in the vicinity of the boarding and alighting station, and each spot is associated with first attribute information indicating the attributes of the spot. The processor of the computer system performs an operation that includes identifying a boarding or alighting station or route that matches the user's preferences, based on second attribute information of the boarding or alighting station or the route determined according to the first attribute information of the spot in the vicinity of the boarding or alighting station, and preference information indicating the user's preferences regarding the spot.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0004]

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

Background Art

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

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

[0004] An object of the present disclosure is to provide a new technology for providing services related to transportation to users who use transportation.

[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 a plurality of boarding / alighting points on a route of a transportation vehicle are each associated with spots around the boarding / alighting point, and the spots are associated with first attribute information indicating attributes of the spots. The processor may execute an operation including identifying a boarding / alighting point or a route that matches the user's preference based on second attribute information of the boarding / alighting point or the route determined according to the first attribute information of the spots around the boarding / alighting point and preference information indicating the user's preference regarding the spots.

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

[0007] Further details will be described in the embodiments below. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 is a diagram showing the configuration of a computer system according to an embodiment. [Figure 2] Figure 2 is a flowchart showing the procedure for providing the service. [Figure 3] Figure 3 is a diagram of the database's data structure. [Figure 4] Figure 4 is an explanatory diagram of a database related to railways. [Figure 5] Figure 5 is an explanatory diagram of the database related to the spot. [Figure 6] Figure 6 is an explanatory diagram of the user database. [Figure 7] Figure 7 is an explanatory diagram of the calculation of the degree of match and the matching score. [Figure 8] Figure 8 is an explanatory diagram of the display modes. [Figure 9] Figure 9 is a data flow diagram of a computer system. [Figure 10] Figure 10 is an explanatory diagram of the intelligent route map system and the vacant asset matching system. [Figure 11] Figure 11 is a diagram illustrating the screen of the first mode. [Figure 12] Figure 12 is a diagram illustrating the screen of the second mode. [Figure 13] Figure 13 is a diagram illustrating the screen of the second mode. [Figure 14] Figure 14 shows various screen diagrams. [Figure 15] Figure 15 is a diagram illustrating the screen of the third mode. [Figure 16] Figure 16 is a diagram illustrating the screen of the third mode. [Figure 17] Figure 17 is an explanatory diagram of the filter screen. [Figure 18] Figure 18 is an explanatory diagram of a database related to landscape impressions.

Mode for Carrying Out the Invention

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

[0010] (A1) The computer system according to the embodiment is a processor, and a database in which a plurality of boarding / alighting points on a route of a transportation facility are each associated with spots around the boarding / alighting point, and first attribute information indicating the attributes of the spots is associated with the spots, and includes wherein the processor the second attribute information of the boarding / alighting point or the route determined according to the first attribute information of the spots around the boarding / alighting point, and preference information indicating the user's preference regarding the spots, and based on identifies a boarding / alighting point or a route that matches the user's preference, and executes an operation including It can be a computer system.

[0011] (A2) The operation further includes presenting the identified boarding / alighting point or the identified route to the user, and can be the computer system according to (A1). (A1) The computer system described in

[0012] (A3) The operation further includes presenting the second attribute information of the identified boarding / alighting point or the second attribute information of the identified route to the user, and can be the computer system according to (A1). (A1) The computer system described in

[0013] (A4) The operation Presenting to the user the spot associated with the identified boarding / alighting station, or the spot associated with the boarding / alighting station included in the identified route. This further includes, This could 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 station included in the identified route, Determined based on, This could be the computer system described in (A4).

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

[0016] (A7) The aforementioned operation is, The spot associated with the identified boarding / alighting station, or the spot associated with the boarding / alighting station included in the identified route, is presented to the user on a map, showing its relationship to the boarding / alighting station. This further includes, The computer system described in (A1).

[0017] (A8) The boarding / alighting area that matches the user's preferences is determined based on the degree of matching. The degree of matching indicates the degree to which the second attribute information of each of the multiple boarding / alighting locations matches the user's preference information. This could be the computer system described in (A1).

[0018] (A9) The aforementioned operation is, The first attribute information of the spot is obtained from the user, From the acquired first attribute information, a second attribute information indicating the attributes of the boarding / alighting area associated with the spot is obtained, The second attribute information is stored in association with the boarding / alighting station or the route. This further includes, This could be the computer system described in (A1).

[0019] (A10) The aforementioned mode of transport is a railway. The aforementioned boarding / alighting area is a station on the aforementioned railway. This could be the computer system described in (A1).

[0020] (A11) The method according to the embodiment is A computer implementation method that is executed by a computer having a database in which each of a plurality of boarding and alighting points on a transportation route is associated with a spot in the vicinity of the boarding and alighting point, and each of the spots is associated with first attribute information indicating the attributes of the spot, The second attribute information of the boarding / alighting area or the route, which is determined according to the first attribute information of the spot in the vicinity of the boarding / alighting area, Based on preference information indicating the user's preferences regarding the aforementioned spot, Identifying boarding / alighting stations or routes that match the user's preferences, Including, This could be a computer implementation method.

[0021] (A12) The computer program according to the embodiment is: A computer has a database in which each of the multiple boarding and alighting points on a transportation route is associated with a spot in the vicinity of the boarding or alighting point, and each spot is associated with first attribute information indicating the attributes of the spot. The second attribute information of the boarding / alighting area or the route, which is determined according to the first attribute information of the spot in the vicinity of the boarding / alighting area, Based on preference information indicating the user's preferences regarding the aforementioned spot, Identifying boarding / alighting stations or routes that match the user's preferences, To perform an action that includes the following: It could be a computer program.

[0022] (B1) The computer system according to the embodiment is: Processor and A database in which attribute information indicating the attributes of each of the multiple boarding and alighting points on a transportation route is associated, Equipped with, The aforementioned processor, Based on the attribute information of each of the multiple aforementioned boarding / alighting stations and preference information indicating the user's preferences, a product related to a boarding / alighting station or route that matches the user's preferences is determined. The determined product is presented to the user. Perform an action that includes the following: It could be a computer system.

[0023] (B2) The aforementioned product is a product that utilizes transportation available on the route to the aforementioned boarding / alighting point or the aforementioned route, which matches the user's preferences. This could be the computer system described in (B1).

[0024] (B3) The aforementioned product is a product that utilizes transportation that allows the user to disembark at a stop that matches the user's preferences or at any stop included in the identified route. This could be the computer system described in (B1).

[0025] (B4) The aforementioned product is a product that utilizes transportation that allows the user to disembark at a stop that matches the user's preferences or at any stop included in the aforementioned route that matches the user's preferences, and allows the user to board at a stop determined from the user's location information. This could be the computer system described in (B1).

[0026] (B5) The aforementioned product is a service that can be used at a spot near a boarding / alighting station that matches the user's preferences or any boarding / alighting station included in the aforementioned route that matches the user's preferences. This could be the computer system described in (B1).

[0027] (B6) The operation further includes presenting the user with the price of the product, which is determined according to the availability of the product. It may be a computer system as described in any one of items (B1) to (B5).

[0028] (B7) The aforementioned mode of transport is a railway. The aforementioned boarding / alighting area is a station of the aforementioned railway. This could be the computer system described in (B1).

[0029] (B8) The aforementioned preference information includes information indicating the user's preferences regarding spots around the boarding / alighting area. This could be the computer system described in (B1).

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

[0031] (B10) The method according to the embodiment is A computer implementation method that is performed by a computer having a database in which attribute information indicating the attributes of each of several boarding and alighting stations on a transportation route is associated with the said boarding and alighting station, Based on the attribute information of each of the multiple aforementioned boarding / alighting stations and preference information indicating the user's preferences, a product related to a boarding / alighting station or route that matches the user's preferences is determined. The determined product is presented to the user. Including, This could be a computer implementation method.

[0032] (B11) The computer program according to the embodiment is: A computer equipped with a database in which attribute information indicating the attributes of each of the multiple boarding and alighting points on a transportation route is associated, Based on the attribute information of each of the multiple aforementioned boarding / alighting stations and preference information indicating the user's preferences, a product related to a boarding / alighting station or route that matches the user's preferences is determined. The determined product is presented to the user. To perform an action that includes the following: It could be a computer program.

[0033] (C1) The computer system according to the embodiment is: A database in which multiple spots in the vicinity of each of the multiple boarding and alighting points on a transportation route are associated, Processor and Equipped with, The aforementioned processor, First attribute information indicating the attributes of the aforementioned spot is obtained, From the acquired first attribute information, a second attribute information indicating the attributes of the boarding / alighting area associated with the spot is obtained, The second attribute information is stored in association with the boarding / alighting station or the route. Perform an action that includes the following: It could be a computer system.

[0034] <2. Examples of computer systems, computer implementation methods, and computer programs>

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

[0036] <2.1 Hardware Configuration Example>

[0037] Figure 1 shows a computer system 10 according to an embodiment. System 10 is configured to perform information processing (service provision processing 111) for providing services related to transportation. System 10 may consist of one or more computers 100, 200.

[0038] The system 10 shown in Figure 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 provider.

[0039] 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 the user terminal 200.

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

[0041] Server 100 is comprised of one or more computers. The computers comprising Server 100 may include a processor 110 and a storage device 120 connected to the processor 110. The computers comprising User Terminal 200 may also include a processor 210 and a storage device 220 connected to the processor 210.

[0042] Processors 110,210 are CPUs, GPUs, or other types of processors. Storage devices 120,220 include, for example, primary and secondary storage devices. Primary storage devices are, for example, RAM. Secondary storage devices are, for example, hard disk drives (HDDs) or solid-state drives (SSDs). Storage devices 120,220 may contain computer programs 121,221 executed by processors 110,210. Processors 110,210 read and execute computer programs 121,221 stored in storage devices 120,220.

[0043] The computer program 121 of the server 100 contains program code that indicates instructions for 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 built on the storage device 120 of the server 100. The database 300 contains various types of data used in the service provision process 111. Details of the database 300 will be described later.

[0045] The computer program 221 on 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 on the user terminal 200. The computer program 221 works in cooperation with the server 100 to execute information processing related to the service provision process 111 on the user terminal 200.

[0046] The computer program 221 of the user terminal 200 contains program code that indicates instructions to the processor 210 to execute processing related to the service provision process 111 in the user terminal 200. Processing related to the service provision process 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. When the computer program 221 is executed by the computer (processor), the computer can operate as the user terminal 200 according to the embodiment.

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

[0048] The user terminal 200 may be equipped with an input / output device 230. The input / output device 230 has input and output functions for data, etc. The input / output device 230 is, for example, a touch panel display. The touch panel display can output screen displays, accept data input such as characters, and accept user operations such as selections. The display of the user terminal 200 may be used to display user interfaces provided by applications 121 and 221 of the system 10. Note that the input function and the output function may each be configured by separate devices.

[0049] The user terminal 200 may be equipped with 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 means other than GNSS, such as by using a WiFi access point to acquire location information, or by accepting location information input from the user.

[0050] <2.2 Example of service provision process>

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

[0052] Here, "transportation" refers to means of transport that passengers can use for travel, such as trains and buses. This assumes transportation that operates on a route. "Route" refers to the transportation lines, such as roads and railway lines, that the transportation passes through.

[0053] A railway line has multiple boarding and alighting points. A "boarding and alighting point" is a place for passengers to get on and off, such as a train station or a bus stop. In the following explanation, we will use the example that the mode of transport is a railway, the line is a railway line, and the boarding and alighting points are train stations.

[0054] The service provision process 111 according to the embodiment provides, as an example, a service related to railways. In this embodiment, in order to provide the service, first, a database 300 of spots associated with the nearest station is created (step S21). In addition, in order to understand the user's preferences, the user's favorite spots are collected on the user interface of applications 121 and 221 (step S22). Spots include shops, factories, facilities, parks, tourist spots, etc., and can be identified as some kind of point on a map. In the database 300 of this embodiment, spots in the vicinity of each station are associated with each of the multiple stations. Based on the user's favorite spots (user preference information), stations / lines (areas) of interest to the user are estimated. Depending on the stations / lines (areas) of interest, available assets may be recommended (presented) (step S23). Also, spots or stations that match the user's preferences may be presented to the user (step S24). The following describes each of these steps S21 to S24 in detail.

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

[0056] Figure 3(A) shows the structure of data related to stations and spots in database 300. Transportation operators, such as railway companies, operate one or more lines. Correspondingly, in the database 300 according to this embodiment, one or more lines are associated with each operator. In the database 300 in Figure 3(A), for example, lines such as "Kosei Line" and "JR Kyoto Line" are associated with "JR West Japan." Note that there may be multiple transportation operators.

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

[0058] Around a train station, there are various spots such as shops, factories, facilities, parks, and tourist attractions. Correspondingly, in the database 300 according to this embodiment, one or more spots are associated with each station. In the database 300 in Figure 3(A), as an example, "Takatsuki" is associated with spots around the station such as "**Sake Brewery Co., Ltd.", "Ama Ruins Park", and "Settsukyo Gorge". Note that a single spot does not have to be associated with only one station; a single spot may be associated with multiple stations. In other words, a given spot may be associated with one or more stations (for example, the nearest station) in its vicinity.

[0059] In the database 300 according to this embodiment, one or more attribute information is associated with each spot. Attribute information is information that indicates the attributes of an object such as a spot, and is information that is attached to the object in order to classify the object or to identify similar objects. In addition to spots, the objects to which attribute information is attached may be stations or lines, as described later. Attribute information may also be called tag information. Furthermore, attribute information associated with a spot may be called "first attribute information" or "first tag information".

[0060] In database 300 in Figure 3(A), as an example, "**Sake Brewery Co., Ltd." is associated with the primary attribute information "#Japanese Sake". The primary attribute information "#Japanese Sake" indicates that "**Sake Brewery Co., Ltd." is a spot related to Japanese sake. Also, "Ama Ruins Park" is associated with the primary attribute information "#Ruins". The primary attribute information "#Ruins" indicates that "Ama Ruins Park" is a spot related to ruins. "Settsukyo Gorge" is associated with the primary attribute information "#Famous Cherry Blossom Spot". The primary attribute information "#Famous Cherry Blossom Spot" indicates that "Settsukyo Gorge" is a famous cherry blossom spot.

[0061] The association of first attribute information to each spot may be performed with the cooperation of the user. For example, a user who visits a 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 selected subjectively by the user. The system 10 registers the input tag information in association with that spot.

[0062] In other words, the processor of system 10, which has a database 300 in which multiple spots around each station are associated with multiple stations, can obtain first attribute information indicating the attributes of a spot (from a user, etc.) and perform the operation of storing that first attribute information in the database 300 in association with that spot.

[0063] System 10 may, without utilizing user cooperation, acquire data associated with attribute information for spots from an external system and register it in database 300. Alternatively, System 10 may obtain other first attribute information related to the first attribute information obtained from user cooperation or an external system, and register this other first attribute information in database 300. Other first attribute information may include, for example, similar concepts, related concepts, higher-level concepts, or lower-level concepts of the first attribute information obtained from user cooperation or an external system. System 10 can refer to a knowledge base (concept base) containing numerous concepts that can become first attribute information, and obtain similar concepts, etc., as other first attribute information from the first attribute information obtained from user cooperation or an external system. For example, System 10 can infer "outdoor," which is a higher-level concept of "camping" and "park," as other first attribute information from the first attribute information of "camping" and "park." Furthermore, system 10 can infer "starry sky," a related concept, from the first attribute information of "fireflies" and "astronomical observation" as another first attribute information.

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

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

[0066] Thus, the processor of the system 10 according to this embodiment may perform an operation that includes obtaining second attribute information from the first attribute information, which indicates the attributes of a station (boarding / alighting place) or route associated with a spot, and storing the second attribute information in association with the station or route. The system 10 may also obtain other second attribute information related to the second attribute information obtained as described above, and associate this other second attribute information with the station or route. Other second attribute information may be, for example, similar concepts, related concepts, higher-level concepts, or lower-level concepts of the already obtained second attribute information. The method for obtaining other second attribute information may be the same as the method for obtaining other first attribute information.

[0067] The secondary attribute information of a station is obtained as all or part of the set of primary attribute information of the spots associated with that station. For example, the spots associated with the station "Takatsuki," namely "**Sake Brewery Co., Ltd.," "Ama Ruins Park," and "Settsukyo Gorge," each have the primary attribute information "#Japanese Sake," "#Ruins," and "#Famous Cherry Blossom Spot," respectively. Therefore, the secondary attribute information of the station "Takatsuki" may be all or part of the set of primary attribute information of multiple spots such as "#Japanese Sake," "#Ruins," and "#Famous Cherry Blossom Spot."

[0068] The secondary attribute information of a route is obtained as all or part of the set of primary attribute information of spots associated with stations associated with that route. For example, the secondary attribute information of a route called "JR Kyoto Line" may be all or part of the primary attribute information of multiple spots (such as "**Sake Brewery Co., Ltd.", "Ama Ruins Park", "Settsukyo Gorge", etc.) associated with multiple stations (such as Settsu-Tomita, Takatsuki, etc.) included in the JR Kyoto Line.

[0069] The secondary attribute information of a station obtained as described above represents the image / atmosphere of the station, formed from the spots around the station. In other words, the secondary attribute information of a station represents the image / atmosphere of the area surrounding the station. Similarly, the secondary attribute information of a railway line represents the image / atmosphere of the entire line, formed from the spots around each station on that line. In other words, the secondary attribute information of a railway line represents the image / atmosphere of the broader surrounding area along that line.

[0070] Here, we assume that many of the spots around the station "Takatsuki" have one of two primary attribute pieces attached to it: "#JapaneseSake" or "#Ruins". In this case, for example, the secondary attribute piece for the station "Takatsuki" can be limited to just "#JapaneseSake" and "#Ruins", and other primary attribute pieces attached to the spots around "Takatsuki" do not need to be included in the secondary attribute piece for "Takatsuki". For example, as shown in Figure 3(B), the secondary attribute piece that represents the image of the station "Takatsuki" can be limited to just "#JapaneseSake" and "#Ruins". In this way, by extracting secondary attribute pieces that are characteristic of the station, the image of the station can be made clearer.

[0071] Similarly, the second attribute information of a route can be obtained in the same way. For example, as shown in Figure 3(B), the only second attribute information that represents the image of the "JR Kyoto Line" can be "#Japanese Sake".

[0072] System 10 can extract characteristic secondary attribute information of a station or railway line by selecting, based on predetermined selection criteria, the primary attribute information attached to many surrounding spots from among all the primary attribute information attached to multiple spots around the station, and using that information as the secondary attribute information of that station. This makes it possible to extract the strong image / atmosphere of the area surrounding the station / railway.

[0073] Furthermore, the image / atmosphere of an area surrounding a station / railway line can change due to changes in the spots within that area. For example, redevelopment around a station may cause older spots to disappear and new spots to emerge. Therefore, in this embodiment, as an example, the image (second attribute information) of an area surrounding a station / railway line is obtained from the first attribute information (image / atmosphere) of individual spots within that area. As a result, even if the image / atmosphere of an area surrounding a station / railway line changes in response to changes in spots, the second attribute information of the station / railway line will be updated if the first attribute information of the changed spot is obtained. Thus, it becomes easier to respond to changes in spots. Moreover, if the first attribute information of spots is obtained with the cooperation of the user, it becomes even easier to respond to those changes.

[0074] In this embodiment, the image / atmosphere of each station / line is registered in the database 300 as second attribute information. Therefore, the system 10 can suggest to its users information about stations / lines that have an image / atmosphere that matches the user's preferences. For example, the system 10 can suggest stations / lines that match the user's preferences to the user, or provide the user with information related to those stations / lines. Furthermore, if the user's preference is for 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 Figure 3(B). Note that "Mozu" is one of the nearest stations to the Oyama Kofun (ancient burial mound), and "Tarumi" is one of the nearest stations to the Goshikizuka Kofun (ancient burial mound), and both are stations related to archaeological sites. Similarly, the system 10 can also extract lines that match the user's preferences based on the user's preferences.

[0075] Furthermore, by providing users with the image and atmosphere of the area surrounding a station / railway line through System 10, users can grasp the image and atmosphere of the area surrounding a station / railway line they have not visited. Therefore, it is possible to gain the user's interest in that area. Users who become interested in that area are expected to use the railway, get off at a station in that area, and visit the area. Therefore, by using System 10, it is possible to provide users with a new travel experience using the railway.

[0076] Figures 4 and 5 show examples of multiple database groups used to realize the structure of database 300 shown in Figure 3. Figure 4 shows a database group related to railways, and Figure 5 shows a database group related to spots. Hereafter, the database groups shown in Figures 4 and 5 will be collectively referred to as "content database 310". Content database 310 constitutes a part of database 300.

[0077] Figure 4(A) shows the route database. As an example, Figure 4(A) shows routes where JR West is the railway operator. As shown in Figure 4(A), the route database includes the following items: route ID, route name, railway operator, station IDs belonging to the route, and express train ID.

[0078] "Route ID" and "Route Name" are data used to identify a route, and in Figure 4(A), the Kyoto Line (ID=L1), Kobe Line (ID=L2), and Osaka Loop Line (ID=L3) are shown as examples. "Railway Operator" indicates the railway operator of the route. "Station ID belonging to the route" indicates the ID (identifier) ​​of a station associated with the route (a station included in the route), and can be used by System 10 to identify stations associated with the route, etc. "Limited Express ID" indicates the ID (identifier) ​​of a limited express train (a train requiring a limited express ticket) that passes through that route, and can be used by System 10 to identify a limited express train that passes through that route, etc.

[0079] Figure 4(B) shows the station database. As an example, Figure 4(B) shows several 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 Train ID".

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

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

[0082] Furthermore, the "Spot Tag ID" in Figure 4(B) also indicates the ID of one or more tag information associated with the route. The set of multiple spot tag IDs (ID=T1, T55, T2, T13, T6, T9) of multiple stations (ID=ST1~ST3) included in the Kyoto Line (ID=L1) may represent the second attribute information of the route.

[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 where passengers can board or alight.

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

[0085] "Express ID" and "Train Name" are data used to identify express trains. In Figure 4(C), examples include Thunderbird (ID=EX1), Shirasagi (ID=EX2), Kuroshio (ID=EX3), and Haruka (ID=EX3). "Route ID" indicates the ID of the route the express train travels on and can be used to identify express trains that travel on each route. "Station ID" can be used to identify stations where the express train stops and where passengers can board and alight. "Vehicle ID" indicates the ID of the vehicle used for the express train. "Remarks" indicates remarks information about the express train.

[0086] Figure 5(A) shows the spot information database. As shown in Figure 5(A), the spot information database includes the following items: "Spot ID", "Spot Name", "Latitude and Longitude", "Address", "Nearest Station ID" (Nearby Station ID), and "Spot Tag ID".

[0087] In Figure 5(A), "Spot ID" and "Spot Name" are data used to identify a spot, and Figure 5(A) shows several spots located in Takatsuki City, Osaka Prefecture as examples. "Latitude and Longitude" indicates the latitude and longitude of the spot. The latitude and longitude of a spot may 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 that spot.

[0088] The "Spot Tag ID" in Figure 5(A) indicates the ID of one or more tag information (spot tags) associated with that spot. In other words, the "Spot Tag ID" in Figure 5(A) indicates the primary attribute information of that spot. As mentioned above, the "Spot Tag ID" (primary attribute information) can be associated with a spot with the cooperation of the user.

[0089] Figure 5(B) shows the spot tag database. The spot tag database displays a list of spot tags (tag information). The spot tag database shown in Figure 5(B) includes the following items: "Spot Tag ID", "Tag Name", "User ID", "Tag Description", and "Spot ID".

[0090] In Figure 5(B), "Spot Tag ID" 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. Users can associate a spot tag with a spot tag that is already registered in the spot tag database, or they 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] In Figure 5(B), the "Spot ID" indicates the ID of one or more spots to which that spot tag (tag information; primary attribute information) is associated.

[0092] Figure 5(C) shows the spot review database. The spot review database displays a list of reviews, comments, and experience reports posted by users for each spot via the user interface of System 10. The spot review database in Figure 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 the text describing the review, etc. "Posting Date and Time" indicates the date and time the review was posted. "Related Links" includes the URL of related links, etc.

[0094] <2.2.2 Gathering user preference information (Step S22)>

[0095] Returning to Figure 2, System 10 collects the user's favorite spots and other information on the user interface of the application the user uses, in order to understand the user's preferences (Step S22).

[0096] Figure 6 shows a user database 320 that lists users of system 10. The user database 320 contains preference information for each user. For example, a user registered in database 320 has installed a computer program 221 on their user terminal 200, and can use the installed computer program 221 (application) to register their favorite spots, etc. System 10 stores the user's favorite spots, etc., in the user database 320, associating them with the user. Based on the user's favorite spots, etc., System 10 obtains preference information that indicates the user's preferences.

[0097] Furthermore, user preference information may be obtained based on the user's favorite spots, or it may be obtained by analyzing user-submitted reviews / messages and other text using natural language processing or artificial intelligence such as neural networks. The method of obtaining user preference information is not particularly limited.

[0098] The user database 320 shown in Figure 6 includes the following items: "User ID", "Username", "Gender", "Age Group", "Favorite Spot ID", "Presumed Favorite Spot Tag ID", "Presumed Favorite Station ID", "Transportation IC Card ID", "Travel History", and "Point Balance".

[0099] "User ID" and "Username" are data that identifies the user, while "Gender" and "Age Group" 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 System 10 interface. In other words, the "Favorite Spot ID" indicates the ID of a spot that the user has determined to match their preferences. The "Favorite Spot ID" is an example of the user's preference information. Note that the "Favorite Spot ID" may also include the ID of a favorite station / route. In other words, a spot here may include a station or a route.

[0101] The "Presumed Favorite Spot Tag ID" indicates the ID of a spot tag (attribute information) associated with a specific spot that the user has selected as a favorite, or the ID of a spot tag that the user has selected as a favorite. Users may select a spot as a favorite, or they may select a spot tag as a favorite.

[0102] The "Favorite Spot ID" indicates the 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 (or estimated value) for attributes that a spot may possess (e.g., "Sake"). The "Presumed Favorite Spot Tag ID" is another example of user preference information. In Figure 6, for example, for a user named "Yamada," the "Presumed Favorite Spot Tag ID" is "T1(0.7), T5(1.0)." The numbers in parentheses following the spot tag IDs T1 and T5 indicate the estimated degree of the user's preference for that spot tag. In the case of "T1(0.7), T5(1.0)," the preference for spot tag T1 is 0.7, and the preference for spot tag T5 is 1.0, indicating that spot tag T5 has a higher estimated preference. The estimated preference is calculated so that, for example, the more spots that the user has favorited, the higher the estimated value of the spot tag. Furthermore, system 10 may obtain other "spot tags" related to the "spot tags suspected to be favorites" obtained as described above, and associate the IDs of these other "spot tags" with the user. These other "spot tags" are, for example, spot tags that represent similar concepts, related concepts, higher-level concepts, or lower-level concepts of "spot tags" already associated with the user. The method for obtaining these 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 their general interests and preferences, separate from their preference for specific locations. Therefore, by utilizing a user's preference for an attribute (e.g., "sake"), system 10 can identify locations / stations / lines that have attributes matching 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 sake breweries in Tomita and Hokkaido as favorite locations is a sake lover. Furthermore, system 10 can infer that other locations / stations / lines with the sake attribute are favorites of the user and present them to the user as recommendations.

[0104] The "presumed favorite station IDs" indicate the IDs of stations that System 10 has determined to match the user's preferences. In Figure 6, as an example, for a user named Yamada (ID=U1), ST1 and ST2 are associated as "presumed favorite station IDs." In other words, for user Yamada (ID=U1), the stations presumed to be favorites are Kyoto (ID=ST1) and Nishioji (ID=ST2).

[0105] In Figure 6, the "presumed favorite station IDs" for a user named "Yamada" are given as "ST1(0.7),ST2(0.4)". The numbers in parentheses following the station IDs ST1 and ST2 indicate the estimated degree of the user's preference for the station (degree of match). In the case of "ST1(0.7),ST2(0.4)", the preference for Kyoto (ID=ST1) is 0.7, and the preference for Nishioji (ID=ST2) is 0.4, indicating that Kyoto has a higher estimated preference (higher degree of preference). The methods for predicting favorites and calculating the estimated degree of preference (degree of match) will be explained later.

[0106] The user database 320 may also contain "route IDs presumed to be favorites" or "spot IDs presumed to be favorites."

[0107] "Transportation IC Card ID" indicates the ID of the user's transportation IC card, and "Travel History" shows the user's travel history using public transportation. "Point Balance" indicates the balance of points awarded to the user based on their use of System 10.

[0108] <2.2.3 Recommendation of stations, tickets, spots, etc. according to user preferences (Step S23)>

[0109] Returning to Figure 2, System 10 estimates stations, routes, or spots that the user may be interested in, based on the user's preference information, such as the user's favorite spots (Step S23). System 10 may simply recommend (present) the estimated stations, routes, or spots to the user, but in this embodiment, System 10 also recommends (presents) tickets such as express train tickets or other available assets according to the estimated stations or routes (Step S23).

[0110] For example, as shown in Figure 2, suppose a user lives in Wakayama Prefecture, has registered the tags "#JapaneseSake" and "#Nature" as favorites, and has also registered "Higashi Honganji Temple" near Kyoto Station as a favorite spot. Furthermore, suppose that "Higashi Honganji Temple" has the tag information "#Temples and Shrines" (first attribute information). In this case, system 10 refers to the content database 310 based on the user's preference information and estimates stations that match the user's preferences. For example, based on the fact that this user has registered "#JapaneseSake" as a favorite, system 10 can identify (predict) "Momoyama Station" (a JR Nara Line station in Fushimi Ward, Kyoto City, with many sake breweries in the surrounding area) which has the second attribute information "#JapaneseSake" as a station that matches the user's preferences. Furthermore, system 10 can identify (predict) one or more spots (sake breweries around Momoyama Station) that have "#JapaneseSake" among the spots associated with the identified "Momoyama Station" as spots that match the user's preferences.

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

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

[0113] Furthermore, system 10 can present (recommend) to the user, via the application interface, a product such as a reserved seat (available asset) on the Limited Express Kuroshio (Wakayama to Kyoto) to go to the identified station (Momoyama Station or Tofukuji Station). To determine the product to present to the user, system 10, for example, uses the user's location information and the location information of the identified station (such as latitude, longitude, or address in the station database) to find a route using transportation such as a railway from the user's location to the identified station. The requested route is, for example, a railway 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 from the user database 320, or location information obtained by the location information acquisition device of the user terminal 200. The user's location information may also be obtained from the user's travel history. The process of finding a route (route search) may be performed by API linkage with an external system for route search. Also, there may be one route or multiple routes. Since there may be multiple starting points associated with the user's location information, route searches may be performed for each of these starting points. Similarly, since there may be multiple destinations, route searches may be performed for each of these destinations.

[0114] The system 10 then refers to the express train database shown in Figure 4(C) to identify express trains available on the routes included in the specified route. For example, the identified express train is the "Kuroshio Express," which is available on the route between Wakayama Station and Kyoto Station.

[0115] Furthermore, System 10 refers to the vacant seat database 330 (vacant asset database) which shows the availability of seats on express trains, checks for the presence of vacant reserved seats (vacant assets) on the identified express train, and if there are vacant reserved seats (vacant assets), presents (recommends) the ticket for that vacant reserved seat to the user for sale. This promotes the sale of tickets to users who are interested in the presented station / spot.

[0116] Furthermore, when deciding which products (such as tickets) to present to a user, the user's location information does not necessarily need to be considered. For products that are unrelated to the user's location information, the user's location information is not required. Examples of products unrelated to the user's location information include hotel accommodations near an identified station, or travel passes that can be used in a specific area including an identified station / route, regardless of the departure point.

[0117] When System 10 presents (recommends) products such as tickets to a user, it may determine the price of the product according to its availability (for example, the availability of reserved seats on an express train (occupancy rate)). System 10 can determine a price according to availability (for example, a 30% discount on a reserved seat on the Kuroshio express train) based on dynamic pricing or other pricing algorithms that increase the discount rate as the occupancy rate increases. In this case, it can further promote the sale of products that match the user's interests. System 10 may also consider the user's preferences when deciding which products to present to the user. For example, conditions related to the user's preferences (preference conditions) may include the type of train (express train / local train), the type of seat (ordinary / green car), whether or not there are transfers and the number of transfers, the type of ticket (unlimited rides, etc.), the time of year, date and time of travel, the number of travelers, and the price range.

[0118] The products recommended by System 10 are not limited to train tickets; they may also include hotel accommodations, or travel packages that combine train tickets and hotel accommodations.

[0119] For example, System 10 can recommend travel products related to sake and nature at a discount to users who like sake and nature. As mentioned above, suppose a user lives in Wakayama Prefecture, has registered the tags "#sake" and "#nature" as favorites, and has also registered "Higashi Honganji Temple" near Kyoto Station as a favorite spot. In this case, System 10 can present the user with a list of sake breweries in the Fushimi area of ​​Kyoto City based on the user's preferences, and can also present, sell, and accept the purchase of a one-night, two-day travel product that allows the user to "hop" between Momoyama Station and Tofukuji Station, which are identified stations, on the JR Nara Line.

[0120] Furthermore, by matching user preference information with the station database, it is possible to develop travel products such as tickets tailored to users with specific preferences (for example, users who like Japanese sake). System 10 may also direct users to external e-commerce sites (EC sites) that sell travel products or tickets after matching. This can be done, for example, by presenting a link to the EC site to user 10 within the application. By sending users to EC sites and other websites, it is possible to receive a commission payment from those sites.

[0121] The following explains the degree of matching between user preferences and stations. As explained in Figure 6 regarding the "Station IDs Presumed to be Favorites" in the user database, System 10 predicts "Stations Presumed to be Favorites" based on the estimated degree of user preference (degree of matching) for each station.

[0122] The degree of matching is calculated, for example, from station vectors and user vectors. Here, station vectors are composed of tag information associated with stations, and user vectors are composed of tag information associated with users.

[0123] For example, the station vector for each station registered in the station database in Figure 4(B) is represented as (tag01, tag02, tag03, ...) = (sake, burial mound, park, ...). Tag01, tag02, tag03, ... indicate the presence or absence of each of the spot tags registered in the spot tag database in Figure 5(B), and can take values ​​of 1 or 0 as an example. For example, the station vector for Takatsuki Station is represented as (1,1,1,0,0, ...), indicating that Takatsuki Station is associated with the spot tags sake, burial mound, and park, but not with any other spot tags. Similarly, the station vector for Sakai Station is represented as (0,1,1,0,0, ...), indicating that Sakai Station is associated with the spot tags burial mound and park, but not with any other spot tags. Note that each element of the station vector is not limited to 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 that station is associated with the corresponding spot tag. Each element of the station vector (each spot tag) represents the weight (importance) of each spot tag at that station. For example, suppose a station is associated with about one spot tag with the "park" spot tag (number of spot tags = 1) and about ten spots tagged with the "sake" spot tag (number of spot tags = 10). In this case, "sake" is more important to that station than "park".

[0124] Furthermore, for each user registered in the user database 320 in Figure 6, the user vector is represented as (tag01, tag02, tag03, ...) = (sake, ancient tomb, park, ...). Tag01, tag02, tag03, ... indicate the presence or absence of each spot tag registered in the spot tag database in Figure 5(B), and can take values ​​of 1 or 0 as an example. For example, user U1 is represented as (1, 1, 1, 0, 0, ...), and for user U1, sake, ancient tomb, and park are the spots indicated by user U1's "favorite spot tag ID". Note that each element of the user vector is not limited to 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; degree of favorite) of each spot tag for that user. For example, if a user has registered about five spots tagged with "ancient burial mounds" as their favorite spots, and about ten spots tagged with "Japanese sake," then for that user, "Japanese sake" is more important than "ancient burial mounds."

[0125] System 10 performs vector operations using the station vectors and user vectors as described above, and calculates the similarity of the vectors as the degree of match. For example, for user U1, Takatsuki Station has a higher vector similarity than Sakai Station. Therefore, a higher degree of match is required for Takatsuki Station.

[0126] For a given user U1, the degree of match (estimated level of interest in stations) is calculated for each of several stations. System 10 identifies stations where the degree of match exceeds a predetermined standard as stations that the user is likely to be interested in. System 10 registers the IDs of the identified stations as "presumed favorite station IDs" in the user database 320 shown in Figure 6.

[0127] Here, let's consider a scenario where System 10 presents a product called the "Osaka Loop Line Pass" to a user. The more stations that the user has a high degree of compatibility with (stations that match the user's preferences) among the stations that can be reached with this pass (multiple stations included in the Osaka Loop Line), the higher the likelihood that the user will purchase this pass. Furthermore, among multiple users, the more stations that have a high degree of compatibility, the higher the likelihood of purchase. Therefore, System 10 calculates the degree of compatibility for each station for each of the multiple users. Then, System 10 calculates a matching score between the user and the product, such as the "Osaka Loop Line Pass," based on the degree of compatibility with the stations, and can prioritize selling the product to users with high matching scores or determine the price according to the matching score. The method for calculating the matching score will be further explained below using Figure 7.

[0128] Figure 7(A) shows an example of a station vector table that displays the station vector for each station. In Figure 7(A), each element of the station vector is represented by a non-negative integer N, rather than 1 or 0. N represents the number of spot tags associated with that station. The larger the N, the greater the contribution of spot tags to the station's image formation.

[0129] Figure 7(B) shows an example of a user vector table representing each user's user vector. In Figure 7(B), each element of the user vector takes a value between 0 and 1, but as in Figure 7(A), it may also be represented by the number of spot tags N associated with that user. Spot tags with larger element values ​​are more strongly related to the user's preferences (interests). Note that each element of the user vector may also take a binary value of 1 or 0.

[0130] Figure 7(C) shows an example of the degree of match (degree of match between user and station) obtained by vector operations from the station vectors in Figure 7(A) and the user vectors in Figure 7(B). In Figure 7(C), the degree of match for each of the multiple stations is shown for each user.

[0131] Figure 7(D) shows ticket vectors representing 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. In Figure 7(D), "Origin" indicates the departure point of the ticket, and the departure point of the ticket and the user's location information may be considered during matching as needed.

[0132] System 10 can calculate vector similarity as a matching score between a ticket (product) and a user by performing vector operations on the matching degree vector in Figure 7(C) and the ticket vector in Figure 7(D). System 10 can then prioritize selling products to users with high matching scores or determine prices according to the matching scores.

[0133] The following is an example of a scenario in which a product (ticket) is recommended to a user. Here, we will describe a scenario in which an express train is recommended based on the user's favorite spot tags (tag information). First, the user selects tag information of interest (for example, a botanical garden) on the user interface of the system 10 according to the embodiment. When the user selects that tag information (botanical garden), the system 10 saves that tag information in association with the user. The system 10 also displays a list of stations associated with the spot (for example, XX Botanical Garden) associated with that tag information on the user interface. The station list is, for example, "Station A, Station B, Station C". Along with the display of the list of stations, the tag information (second attribute information) associated with those stations or the spots (botanical garden or other spots) associated with the stations may also be displayed.

[0134] The user adds several spots (for example, the XX Botanical Garden at Station A and the YY Botanical Garden at Station B) associated with the displayed stations to their favorites list. System 10 saves the favorited spots and their tag information, associating them with the user.

[0135] System 10 selects an express train (for example, the Thunderbird express train) that passes through Station A or Station B, which is the nearest station to the user's favorite spot (e.g., Botanical Garden XX or Botanical Garden YY). System 10 calculates a discount rate based on the time of day when the express train is less available (occupancy rate) and presents the user with a discounted ticket.

[0136] Next, let's describe a scenario in which an unlimited ride ticket is recommended. Here, we assume 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, system 10 can recommend to the user an unlimited ride ticket that covers the area around Kyoto Station, including Kyoto Station. System 10 may also sell the ticket at the regular price, or it may offer the unlimited ride ticket to the user for free or at a discounted price if the user purchases an express train ticket to Kyoto Station.

[0137] Next, we will describe a scenario in which we recommend transportation methods or tickets that allow the user to visit spots of interest. Here, we assume 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, system 10 recommends an express train that runs from the user's nearest station to Kyoto Station. In addition, system 10 can suggest a sightseeing pass (unlimited rides) for the area around Kyoto Station in order to allow the user to travel around the suburbs.

[0138] <2.2.4 Recommended Spots / Station Information (Step S24)>

[0139] Returning to Figure 2, System 10 presents the user with spots or stations that match the user's preferences (Step S24). Step S24 can be performed during a trip using the ticket presented in Step S23, during other trips, before such trips, when using everyday transportation, or at any other time.

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

[0141] The first mode 12A may also be called the current location-centered mode or the ant's-eye view mode. In the first mode 12A, the 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 accordingly. The spots notified in the first mode 12A are, for example, spots from the spot information database shown in Figure 5(A) that the system 10 has determined to match the user's preferences or spots that the system 10 has determined should be presented to the user.

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

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

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

[0145] <2.3 Information Processing Data Flow for Service Provision Processing>

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

[0147] User U1 can, for example, view the displayed user interface 11A screen, operate the screen to switch displays or modes, or register spots or spot tags as favorites.

[0148] User favorites are registered by the user information management unit 15 and stored in the user database 320. The content display control unit 14 can determine content (spots, stations, etc.) that matches the user's preferences based on the user's favorites registration and the user's preference information obtained from that information.

[0149] Furthermore, the available asset matching unit determines products (and prices) that match the user's preferences based on the user's favorites registration, and provides the determined products (and prices) to the presentation content control unit 14. The available seat database 330 may be referenced when determining the products (and prices). The presentation content control unit can then present the products (and prices) to the user on the user interface 11A displayed on the user terminal 200.

[0150] System 10 can receive posts such as reviews and experience reports from users U2 and U3 who have visited a spot. The input of reviews and experience reports is performed via the user interface 11B displayed on the user terminal 200. The input of reviews and experience reports is received by the social content processing unit 13 and registered in the content database 310.

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

[0152] The system 10 according to the embodiments described so far can be functionally understood as a combination of an intelligent route map system 20 and an available asset matching system 30, as shown in Figure 10.

[0153] The intelligent route map system 20 can be used, for example, as a system to form a community that motivates rail travel. The intelligent route map system 20 is based on an interactive route map 20A (objective data) that corresponds to absolute location, and further includes subjective spot data 20B provided by users, and subjective railway-related data 20C provided by users, such as station information and information along the railway line.

[0154] The interactive route map 20A, which corresponds to absolute position, is constructed by adding objective data such as spot names and location information (spot data) and objective data such as stations, lines, and railway operators (railway data) to a map (e.g., a measured map). The stations and lines indicated by the objective railway data are placed (displayed) on the map (measured map).

[0155] The intelligent route map system 20 can display subjective spot data 20B and subjective railway-related data 20C on an interactive route map 20A that corresponds to absolute location.

[0156] In the intelligent route map system 20, spot data 20B is associated with railway-related data 20C (stations or lines), making it possible to display spots 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 other items on the map that match the user's preferences.

[0157] The user can use the intelligent route map system 20 to explore / browse a map on which route maps are placed, and find places they want to visit.

[0158] The available asset matching system 30, based on user preferences, refers to available asset databases such as the train seat availability database 330 and performs a matching process 16 between user preferences and available seats (available assets). The available asset matching system 30 can match available seats to users at a discounted price according to the user's situation, which is understood as the user uses the system 10. The user's situation used for matching includes user preferences, other information in the user database 320 (such as travel history), or the user's current location.

[0159] Users of System 10 can be motivated to travel by rail using the Intelligent Route Map System 20, and for the motivated trip, they can purchase tickets suggested by the Available Asset Matching System 30 and enjoy their trip.

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

[0161] The following describes the first mode 12A, second mode 12B, and third mode 12C mentioned above with respect to Figure 8. Figure 11 shows an example screen for the first mode 12A, Figures 12 and 13 show example screens for the second mode 12B, Figure 14 shows example screens that can be displayed by operating from the screens of the first mode 12A and second mode 12B, and Figures 15 and 16 show example screens for the third mode 12C. Figure 17 shows an example filter screen for the first mode 12C.

[0162] As shown in Figure 11(A), in the first mode 12A, the map is displayed centered on the user's current location. In the first mode 12A, the system 10 notifies users who are on a train of content (spots) around their current location, encouraging them to look out the window.

[0163] When a user approaches content (spots) located near their current location (preferably limited to the direction of travel = forward) beyond a certain threshold, the user receives a notification from system 10 on the user interface (on the screen) that content (spots) are present in their vicinity. As shown in Figure 11(A), spots and information about them may be displayed on the map. For example, as shown in Figure 11(B), system 10 takes the user's direction of travel into consideration and notifies the user of the direction in which the spots are located (e.g., left or right).

[0164] In the first mode 12A, the user may choose 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 cardinal directions (north, south, east, west) are fixed. Furthermore, the system 10 may automatically activate the first mode 12A if it determines that the user is on public transportation (a moving object) such as a train, based on how the user's location information changes or using an acceleration sensor, etc. The notified content is filtered manually or automatically according to the user's preferences. Figure 17 shows the filter screen that appears when the user presses the filter button displayed on the screen of the first mode 12A. By operating the filter screen, the notified content can be filtered by spot tags. This automatically filters out only the information that matches the user's preferences. On the filter screen, it is possible to select spot tags that are presumed to be the user's favorites as filtering conditions, as well as other spot tags.

[0165] As shown in Figure 12, the second mode 12B provides an intelligent route map to encourage the user to plan a trip using the rail.

[0166] As shown in Figures 12(A) and 12(B), in the second mode 12B, stations and railway lines on the map of Japan are highlighted, and a screen is displayed that resembles a railway map overlaid on the map of Japan (the map is annotated with station names, line names, and railway operator names). As a result, stations and other features are highlighted on the map more prominently than in a normal map application. Therefore, the intelligent route of this embodiment is suitable for planning railway trips while considering stations and lines. In the second mode 12B, the granularity of the displayed content (railway operator name > line name > station name) changes according to the degree of zoom and pan, as shown in Figures 13(A), 13(B), and 13(C) (the displayed information is reduced).

[0167] In the screens shown in Figures 12(A) and 12(B), when the user selects a route or station name, a station name slider indicating the "order of stations" along the route appears on the screen, as shown in Figure 12(C). If the user selects a route, the station name displayed in the center of the station name slider will be the nearest station to the center point of the map. If 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 and the station name displayed in the center changes, the map also moves in conjunction, so that the station becomes the center point. The action of moving the map (e.g., from Osaka Station to Fukushima Station) allows the user to follow the railway tracks. This creates the effect of the map's movement giving the user the feeling that a train is running on the tracks. If a single station has multiple routes, the user can switch the station name slider.

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

[0169] Figure 13(D) shows the selected station name (Akabane Station) and the spot tags (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 a screen such as Figure 13(D), the user is taken to a screen displaying spot information (Figure 14(A)). The spot information screen shown in Figure 14(A) introduces detailed information about the selected spot, including an image of the spot, user reviews posted about the spot, and spot tags (primary attribute information).

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

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

[0173] The spot tag portal screen allows users to select routes so they can adjust which stations are displayed. Users can also choose the display order (for example, by proximity to their current location).

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

[0175] As shown in Figures 15 and 16, in the third mode 12C, various timelines are displayed. Figure 15(A) shows the timeline of the user's own posts, and Figure 15(B) shows the timelines of people the user follows.

[0176] Figure 16(A) shows a timeline of posts related to a spot tag. For example, when a user selects a spot tag on the second mode 12B screen (or the first mode 12A screen), posts about the spot or station associated with the selected tag are displayed. Also, if a user's presumed favorite tag is "sea," posts about spots or stations associated with the "sea" tag may be displayed.

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

[0178] <2.6 Landscape Impressions>

[0179] The following describes landscape impressions. System 10 can accept user registrations regarding their impressions of landscapes and send landscape impression notifications to users.

[0180] Here, "scenery" refers to spots other than those that can be identified 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. For example, here, scenery is defined as the view seen from a train window while riding a train. Also, for example, scenery is defined as something that left a lasting impression on a user while riding a train and is posted and registered in System 10.

[0181] As shown in Figure 11, when a user is riding a train, the system 10 can display spots around the user's current location on the screen of the first mode 12A. In Figure 11, in addition to spots that can be indicated by proper nouns such as facility names, registered scenery (scenery impressions) are also presented to the user. In Figure 11, scenery impressions are indicated by heart marks (impression tags). Since the scenery here is the scenery visible from the train window while riding the train, the scenery impression marks (impression tags) are displayed on the route where that scenery is visible. Therefore, when the user's current location approaches the displayed impression tag, they can enjoy the scenery from the train window.

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

[0183] Figure 18 shows a database related to landscape impressions. The database related to landscape impressions is an example of a database included in database 300, which is owned by system 10.

[0184] Figure 18(A) shows the landscape impression submission database. The landscape impression submission database is a database for registering landscapes (landscape impressions) submitted by users. System 10 registers the landscape impressions received from users in the database shown in Figure 18(A). The landscape impression submission database includes the following items: "Landscape Impression Submission ID", "User ID", "Latitude and Longitude", "Submission Date and Time", "Impression Tag ID", "Related Links", and "Public / Private". Note that the landscape impression submission database is not limited to submissions by users, but may also include data set by the system administrator or others.

[0185] The "Landscape Impression Post ID" is the ID of the landscape impression posted by the user. The "User ID" is the ID of the user who posted the landscape impression. The "Latitude and Longitude" is the location where the landscape impression was posted, which is usually a location on a route. The "Posting Date and Time" is the posting date and time of the landscape impression. The "Impression Tag ID" indicates the ID of the tag information (attribute information) of the landscape impression (see Figure 18(C)). The "Related Links" indicates links (URLs) related to the landscape. The "Public / Private" setting indicates whether the landscape impression is made public to others.

[0186] Figure 18(B) shows the landscape impression notification database. The landscape impression notification database is used by system 10 to notify users of landscape impressions on the screen (such as the first mode 12A in Figure 11). The landscape impression notification database is generated for landscape impression notifications based on the contents of the landscape impression submission database, which is based on user submissions. If the conditions shown in the landscape impression notification database are met, system 10 notifies the user of that landscape impression (for example, by displaying it on the screen).

[0187] The landscape impression notification database includes the following items: "landscape impression notification ID," "latitude and longitude," "impression tag ID," "time of viewing," and "time of viewing."

[0188] The "Landscape Impression Notification ID" indicates the ID of the landscape impression (an ID used for notifications). 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 preferably it is an ID that combines multiple landscape impression posts for the same landscape into one. Multiple landscape impressions for the same landscape can be extracted, for example, if the location (latitude and longitude) of the posts is approximately the same.

[0189] The "latitude and longitude" indicates the location (latitude and longitude) of the landscape indicated by the "landscape impression notification ID". Here, the "latitude and longitude" is obtained, for example, from the "latitude and longitude" in the landscape impression submission database. For example, one "latitude and longitude" for notification of a landscape is obtained from the "latitude and longitude" of one or more submissions for the same landscape (for example, by clustering).

[0190] The "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 posting database. For example, one or more "Impression Tag IDs" for notification of a landscape can be obtained from the "Impression Tags" of one or more posts for the same landscape (e.g., through clustering).

[0191] "Viewable period" and "Viewable time" indicate when the scenery is visible. Some scenery may be limited to specific times of day or seasons. For example, a particular scenery might only be visible during the day, only at night, or only in spring. It is preferable to notify users when the scenery is visible. Therefore, system 10 notifies users of the scenery at a time that matches the viewing conditions, such as "Viewable period" and "Viewable time."

[0192] The timing at which a 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 of day, or day, system 10 can determine the time period in which the landscape is concentrated as the timing at which it is visible and register it in the database.

[0193] Figure 18(C) shows the impression tag database. The impression tag database is a database of tag information (attribute information) for landscape impressions. The impression tag database has the following items: "Impression Tag ID", "Impression Name", and "Landscape Impression Post ID".

[0194] The "Impression Tag ID" indicates the ID of the tag information for the landscape impression. The "Impression Name" indicates the name of the impression. The "Landscape Impression Post ID" indicates the ID of the landscape impression post that has the Impression Tag ID.

[0195] System 10 generates a landscape impression notification database from the landscape impression submission database shown in Figure 18(A), and notifies users of landscapes (landscape impressions) based on this notification database. Notifications are sent, for example, when the user's current location approaches the "latitude and longitude" in the notification database, and the timing matches the "viewable period" and "viewable time slot." However, notifications may also be sent at other times.

[0196] Furthermore, landscape impressions may be associated with spots that the user (poster) is presumed to have viewed. For example, if a landscape impression is registered on a route next to a park, that landscape impression may be associated with the spot known as "the park."

[0197] The present invention is not limited to the above embodiments, and various modifications are possible. [Explanation of Symbols]

[0198] 10: Computer Systems 11A: User Interface 11B: User Interface 12: Content presentation process 12A: First mode 12B: Second Mode 12C: Third mode 13: Social Content Processing Department 14: Display Content Control Unit 15: User Information Management Department 16: Matching process 17: Database Management System 20: Intelligent Route Map System 20A: Route map 20B: Data 20C: Railway-related data 30: Empty 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 Program 230: Input / Output Devices 240: Location information acquisition device 300: Database 310: Content Database 320: User Database 330: Vacancy Database

Claims

1. Processor and A database in which each of multiple boarding and alighting points on a transportation route is associated with a spot in the vicinity of the said boarding and alighting point, and a first attribute information indicating the attributes of the said spot is associated with the said spot, Equipped with, The aforementioned processor, The second attribute information of the boarding / alighting area or the route, which is determined according to the first attribute information of the spot in the vicinity of the boarding / alighting area, Based on preference information indicating the user's preferences regarding the aforementioned spot, Identifying boarding / alighting stations or routes that match the user's preferences, Perform an action that includes the following: Computer system.

2. The aforementioned operation is, The identified boarding / alighting area or identified route is presented to the user. This further includes, The computer system according to claim 1.

3. The aforementioned operation is, The second attribute information of the identified boarding / alighting area, or the second attribute information of the identified route, is presented to the user. This further includes, The computer system according to claim 1.

4. The aforementioned operation is, Presenting to the user the spot associated with the identified boarding / alighting station, or the spot associated with the boarding / alighting station included in the identified route. This further includes, The computer system according to claim 1.

5. 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 station included in the identified route, Determined based on, The computer system according to claim 4.

6. The spot presented to the user is This is determined based on preference information indicating the user's preferences regarding the spot, and the first attribute information of the spot associated with the identified boarding / alighting area, or Determined based on preference information indicating the user's preferences regarding the spot, and the first attribute information of the spot associated with the boarding / alighting station included in the identified route, The computer system according to claim 4.

7. The aforementioned operation is, The spot associated with the identified boarding / alighting station, or the spot associated with the boarding / alighting station included in the identified route, is presented to the user on a map, showing its relationship to the boarding / alighting station. This further includes, The computer system according to claim 1.

8. The boarding / alighting area that matches the user's preferences is determined based on the degree of matching. The degree of matching indicates the degree to which the second attribute information of each of the multiple boarding / alighting locations matches the user's preference information. The computer system according to claim 1.

9. The aforementioned operation is, The first attribute information of the spot is obtained from the user, From the acquired first attribute information, a second attribute information indicating the attributes of the boarding / alighting area associated with the spot is obtained, The second attribute information is stored in association with the boarding / alighting station or the route. This further includes, The computer system according to claim 1.

10. The aforementioned mode of transport is a railway. The aforementioned boarding / alighting area is a station on the aforementioned railway. The computer system according to claim 1.

11. A computer implementation method that is executed by a computer having a database in which each of multiple boarding and alighting points on a transportation route is associated with a spot in the vicinity of the boarding and alighting point, and each spot is associated with first attribute information indicating the attributes of the spot, The second attribute information of the boarding / alighting area or the route, which is determined according to the first attribute information of the spot in the vicinity of the boarding / alighting area, Based on preference information indicating the user's preferences regarding the aforementioned spot, Identifying boarding / alighting stations or routes that match the user's preferences, Including, Computer implementation method.

12. A computer has a database in which each of the multiple boarding and alighting points on a transportation route is associated with a spot in the vicinity of the boarding or alighting point, and each spot is associated with first attribute information indicating the attributes of the spot. The second attribute information of the boarding / alighting area or the route, which is determined according to the first attribute information of the spot in the vicinity of the boarding / alighting area, Based on preference information indicating the user's preferences regarding the aforementioned spot, Identifying boarding / alighting stations or routes that match the user's preferences, To perform an action that includes the following: Computer program.