Information processing systems, information processing methods, and programs
The information processing system enhances ticket usability by using a large-scale language model to generate proposal content from ticket and context information, improving the convenience of transportation service information.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- RYDE INC
- Filing Date
- 2026-02-13
- Publication Date
- 2026-04-28
AI Technical Summary
There is a need to improve the convenience of information regarding tickets for using transportation services.
An information processing system that acquires ticket and context information, and uses a large-scale language model to generate proposal content for presentation to users, enhancing the usability of ticket information.
The system improves the usability of ticket information by providing tailored suggestions based on user context and ticket details, facilitating easier understanding and utilization of transportation services.
Smart Images

Figure 0007852978000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to an information processing system, an information processing method, and a program.
Background Art
[0002] Patent Document 1 discloses an information processing system and the like that can improve the distribution of advertisements to users of transportation services. Patent Document 1 discloses an information processing system including a control unit configured to execute the following steps. In an acquisition step, advertisement performance information and ticket identification information associated with the advertisement performance information are acquired from a plurality of user terminals. The advertisement performance information includes information for determining an advertisement performance regarding an advertisement displayed in association with a ticket for a user to use a transportation service in a user terminal. The ticket identification information includes information for identifying which of a plurality of tickets the ticket with the advertisement displayed in association therewith is in the user terminal. In a determination step, a ticket contribution degree including the contribution degree of each of the plurality of tickets to the advertisement performance is determined based on the acquired advertisement performance information and ticket identification information.
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] However, there is room for improvement in the convenience of information regarding tickets for using transportation services.
[0005] In view of the above circumstances, the present invention aims to provide a technique for improving the convenience of information regarding tickets for using transportation services.
Means for Solving the Problems
[0006] According to one aspect of the present invention, an information processing system is provided, comprising at least one processor, the processor configured to perform the following steps by reading a program, wherein in the acquisition step, ticket information and context information are acquired, the ticket information being information about a digital ticket usable to use a transport service, the digital ticket being associated with a user or configured to be associated with a user, the context information being information about a user using the digital ticket, and in the presentation step, the system is made to present proposal information including predetermined proposal content to the user, the proposal content being output by inputting the ticket information and context information into a large-scale language model.
[0007] This configuration may improve the convenience of information regarding tickets for using transportation services. [Brief explanation of the drawing]
[0008] [Figure 1] This is a diagram showing the configuration of the information processing system 1 according to this embodiment. [Figure 2] This is a block diagram showing the hardware components of Information Processing System 1. [Figure 3] This is a block diagram showing the functions realized by the control unit 33 and other components in the information processing device 3. [Figure 4] This is a flowchart outlining the information processing in this embodiment. [Figure 5] This is an activity diagram showing the information processing flow of this embodiment. [Figure 6] This figure shows an example of a data structure for information that is appropriately referenced in the information processing of this embodiment. [Figure 7] This figure shows an example of the TOP screen 700 displayed on the display unit 24 of the user terminal 2. [Figure 8]This figure shows an example of a list screen 800 displayed on the display unit 24 of the user terminal 2. [Figure 9] This figure shows an example of a ticket screen 900 displayed on the display unit 24 of the user terminal 2. [Figure 10] This figure shows an example of a dialogue screen 1000 displayed on the display unit 24 of the user terminal 2. [Modes for carrying out the invention]
[0009] Embodiments of the present invention will be described below with reference to the drawings. The various features shown in the embodiments below can be combined with each other.
[0010] Incidentally, the program for implementing the software appearing in one embodiment may be provided as a non-transitory computer-readable medium, or it may be provided as a downloadable medium from an external server, or it may be provided so that the program is launched on an external computer and its functions are realized on a client terminal (so-called cloud computing).
[0011] Furthermore, in various information processing according to one embodiment, an input and an output corresponding to the input can be realized. Here, as long as an output is obtained as a result of the input, the form of the information referenced in such information processing (hereinafter referred to as "reference information") is not limited. The reference information may be, for example, rule-based information such as a database, a lookup table, or a predetermined function (including a decision formula such as a regression equation constructed by a statistical method), or a trained model that has been pre-trained to learn the correlation between input and output, or a generative AI such as a large-scale language model that can output a desired result by inputting a prompt (these models include parameters that construct the correlation relationship between input and output) or a visual language model.
[0012] Furthermore, in one embodiment, "part" may include, for example, hardware resources implemented by a circuit in a broad sense, and the information processing of software that can be specifically realized by these hardware resources. Also, in one embodiment, various types of information are handled, and this information can be represented, for example, by the physical values of signal values representing voltage and current, the high or low values of signal values as a set of binary bits composed of 0s or 1s, or by quantum superposition (so-called qubits), and communication and calculations can be performed on a circuit in a broad sense.
[0013] Furthermore, a circuit in a broad sense is a circuit realized by combining at least a suitable combination of circuits, circuits, processors, and memory. The processor may be a general-purpose processor or a dedicated circuit. In other words, it includes application-specific integrated circuits (ASICs), programmable logic devices (for example, simple programmable logic devices (SPLDs), complex programmable logic devices (CPLDs), and field programmable gate arrays (FPGAs)), etc.
[0014] 1. Hardware Configuration This section describes the hardware configuration of this embodiment.
[0015] Figure 1 is a diagram showing the configuration of the information processing system 1 according to this embodiment. The information processing system 1 comprises a user terminal 2 and an information processing device 3, which are connected via a network 4.
[0016] The user terminal 2 and the information processing device 3 are assumed to be computers such as smartphones, tablet terminals, personal computers, and workstations, for example, but the details are not limited. In FIG. 1, the user terminal 2 is described as an aggregate of individual smartphones (2-1, 2-2, ··· 2-n), but in this specification, the individual terminal may also be referred to as the user terminal 2.
[0017] In one embodiment, the information processing system 1 is composed of one or more devices or components. For example, if it consists only of the user terminal 2, the information processing system 1 can be the user terminal 2. Also, if it consists only of the information processing device 3, the information processing system 1 can be the information processing device 3. More specifically, the information processing system 1 may include elements selected from the group consisting of the user terminal 2 and the information processing device 3. Even if the unselected elements are not included in the information processing system 1, they may be electrically connected to the selected elements as external elements. These components will be described below.
[0018] FIG. 2 is a block diagram showing the hardware constituting the information processing system 1. As shown in FIG. 2(A), the user terminal 2 has a communication unit 21, a storage unit 22, a control unit 23, a display unit 24, and an input unit 25, and these components are electrically connected via a communication bus 20 inside the user terminal 2. The descriptions of the communication unit 21, the storage unit 22, and the control unit 23 are substantially the same as those of the communication unit 31, the storage unit 32, and the control unit 33 in the information processing device 3 described later, so repeated descriptions will not be given.
[0019] The display unit 24 may be, for example, included in the casing of the user terminal 2, or it may be an external component. The display unit 24 displays a graphical user interface (GUI) screen that can be operated by the user. This is preferably done by using a display device such as a CRT display, liquid crystal display, organic EL display, and plasma display, depending on the type of user terminal 2. Here, the display unit 24 will be described as being included in the casing of the user terminal 2.
[0020] The input unit 25 may be included in the casing of the user terminal 2, or it may be an external component. For example, the input unit 25 may be integrated with the display unit 24 and implemented as a touch panel. If it is a touch panel, the user can input tap operations, swipe operations, etc. Of course, a switch button, mouse, QWERTY keyboard, etc. may be used instead of a touch panel. In other words, the input unit 25 receives operation input made by the user. This input is transmitted as a command signal to the control unit 23 via the communication bus 20, and the control unit 23 can perform predetermined controls and calculations as needed.
[0021] Furthermore, the user terminal 2 may be equipped with a function to transmit latitude and longitude information. Specifically, the user terminal 2 may be equipped with a function to transmit signals such as GPS (Global Positioning System) (positioning system). In addition, the user terminal 2 may be equipped with devices to detect the user's state, such as a voice recognition device to acquire voice, a gesture detection device to detect the posture or movement of an object, a gaze detection device to detect the direction of the user's gaze, and a biosignal detection device to detect various biosignals of the user.
[0022] As shown in Figure 2(B), the information processing device 3 has a communication unit 31, a storage unit 32, and a control unit 33, and these components are electrically connected within the information processing device 3 via a communication bus 30.
[0023] The communication unit 31 preferably uses wired communication methods such as USB, IEEE1394, Thunderbolt®, and wired LAN network communication, but may also include wireless LAN network communication, mobile communication such as 3G / LTE / 5G, and Bluetooth® communication as needed. In other words, it is more preferable to implement it as a collection of these multiple communication methods. Specifically, the information processing device 3 communicates various information with the user terminal 2 via the network 4 through the communication unit 31.
[0024] The storage unit 32 stores various types of information as defined above. This can be implemented, for example, as a storage device such as a solid-state drive (SSD) that stores various programs related to the information processing device 3 executed by the control unit 33, or as memory such as random access memory (RAM) that stores temporarily necessary information (arguments, arrays, etc.) related to program calculations. A combination of these may also be used. In particular, the storage unit 32 stores various programs related to the information processing device 3 executed by the control unit 33.
[0025] The control unit 33 performs processing and control of the overall operation related to the information processing device 3. The control unit 33 is, for example, a Central Processing Unit (CPU) (not shown). The control unit 33 realizes various functions related to the information processing device 3 by reading predetermined programs stored in the memory unit 32. That is, information processing by software stored in the memory unit 32 is concretely realized by the control unit 33, which is an example of hardware, and can be executed as each functional unit included in the control unit 33. These will be described in more detail in the next section. Note that the control unit 33 is not limited to being a single unit, and may be implemented with multiple control units 33 for each function, or a combination thereof.
[0026] 2. Functional Configuration This section describes the functional configuration of this embodiment. As mentioned above, the information processing system 1 includes at least one processor, and the processor is configured to include the following parts by reading a program. In other words, the program makes the computer function as the various parts of the information processing system 1.
[0027] Figure 3 is a block diagram showing the functions realized by the control unit 33 and other components in the information processing device 3. An example of the information processing system 1, the information processing device 3, comprises an acquisition unit 331, a specification unit 332, a presentation unit 333, and an artificial intelligence unit 334.
[0028] The acquisition unit 331 is configured to perform the acquisition step. In the acquisition step, the acquisition unit 331 is configured to acquire various information from an external source.
[0029] The identification unit 332 is configured to execute a specific step. In the specific step, the identification unit 332 identifies various pieces of information used for information processing based on the information acquired by the acquisition unit 331.
[0030] The presentation unit 333 is configured to execute the presentation step. In the presentation step, the presentation unit 333 controls the process for displaying various information on the display unit 24 of the user terminal 2. The presentation step may include a first presentation step and a second presentation step, which will be described later.
[0031] The presentation unit 333 may draw various screens to be displayed on the display unit 24 and send them to the user terminal 2, or it may send display information including still images or videos, icons, messages, and other visual information to the user terminal 2 so that the user terminal 2 can draw various screens. Alternatively, the presentation unit 333 may generate only the various parameters for displaying the visual information on the display unit 24 and send them to the user terminal 2.
[0032] The control unit 23 of the user terminal 2 draws a screen to be displayed on the display unit 24 based on the received display information and information such as parameters that define various visual information stored in the storage unit 22. For example, the control unit 23 may draw a screen that includes various images and visual information based on the display information, or it may execute a process to display various screens drawn by the presentation unit 333 on the display unit 24. It may also generate visual information such as graphs that show parameters based on various numerical information and other parameters. In other words, at least a part of the functions provided by the presentation unit 333 may be executed by the control unit 23 of the user terminal 2.
[0033] The artificial intelligence unit 334 is configured to receive input from each functional unit and return the instructed output. The artificial intelligence unit 334 receives a predetermined input and instructs the artificial intelligence module to return the instructed output. The artificial intelligence module used by the artificial intelligence unit 334 may be stored in the storage unit 32 and storage unit 22, or it may be stored in an external artificial intelligence server different from the information processing device 3 and the user terminal 2. The artificial intelligence unit 334 inputs predetermined input information to the artificial intelligence module and causes the artificial intelligence module to output predetermined output information. The artificial intelligence module used by the information processing device 3 may be common, or it may be individually provided for each functional unit.
[0034] The artificial intelligence module used by the artificial intelligence unit 334 includes reference information configured to return a predetermined output for a given input. The reference information is configured to identify the correspondence between input information and output information, and may include, for example, information regarding the correlation between the two. The reference information may also include tables, functions, simple algorithms, etc.
[0035] The artificial intelligence module is an AI (Artificial Intelligence) equipped with learning models such as transformers (including GPT (Generative Pretrained Transformer), BERT (Bidirectional Encoder Representations from Transformers), etc.) and language models (such as Recurrent Neural Networks (RNNs)), and may be a generative AI or an AI agent.
[0036] In reference information, a correlation between input and output information can be constructed by statistically analyzing data that records input information and corresponding output information. Reference information may be a trained model, language model, etc., that has been trained to produce output information for given input information. In these, parameters calculated and tuned through training constitute the correlation of the reference information. Note that in reference information, the correspondence between input and output information is not limited to correlation; any predetermined correspondence is sufficient. In the following explanation, redundant explanations regarding the method of constructing reference information will not be repeated.
[0037] A trained model can be configured to perform a specific task through learning methods such as supervised learning, unsupervised learning, or self-supervised learning. In supervised learning, machine learning is performed using training data. Training data consists of pairs of input data and output data (correct answer data) for training.
[0038] Language models are an example of learning models using machine learning algorithms. Specific machine learning algorithms include nearest neighbors, naive Bayes, decision trees, support vector machines, and deep learning using neural networks. Artificial intelligence modules can apply these algorithms as appropriate. Furthermore, language models may not only be those trained for specific tasks, but also general-purpose models that can be used universally for a wide range of tasks (for example, large language models (LLMs) trained on vast amounts of data).
[0039] Generative AI performs various tasks using language models. Specifically, it is configured to respond to given inputs (prompts) by processing a wide range of tasks such as understanding sentence patterns and contexts, answering questions, and generating text, images, and audio, and returning the instructed output. Prompts may be given in any format, including text, images, and audio. Tasks may also be processed interactively, with input reception and information generation and output alternating.
[0040] The AI agent performs various tasks using a language model. Specifically, when a predetermined instruction is input, the AI agent is configured to break down the processes necessary to achieve the specified task into subtasks, actions, etc., and to perform necessary data collection and analysis, program generation and execution, etc. The AI agent may autonomously plan and execute tasks, and evaluate the results of its execution, thereby autonomously learning to achieve its goals.
[0041] The artificial intelligence module may be stored in multiple artificial intelligence servers. The artificial intelligence servers may be servers that provide services using a language model as a learning model, or servers that perform language processing tasks using a language model. The artificial intelligence service server may be built using an LLM and may accept prompt input in the form of text, images, audio, etc., and generate and respond to the prompt.
[0042] 3. Information Processing This section describes each step of the information processing method executed by the information processing system 1. The information processing method is executed by a processor in at least one of the user terminal 2 and the information processing device 3 reading a program.
[0043] 3.1 Overview of Information Processing Figure 4 is a flowchart illustrating the information processing overview of this embodiment. As shown in Figure 4, the acquisition unit 331 acquires ticket information and context information (step S1). The ticket information is information about a digital ticket that can be used to use the transportation service. The context information is information about the user using the digital ticket. The presentation unit 333 presents the user with proposal information containing predetermined proposal content (step S2). The proposal content is output by inputting the ticket information and context information into a large-scale language model. This configuration improves the usability of the ticket information. 3.2 Details of Information Processing
[0044] Figure 5 is an activity diagram showing the information processing flow of this embodiment. Figure 6 is a diagram showing an example of the data structure of information that is referenced as appropriate in the information processing of this embodiment. The various information and data shown in Figure 6 may be stored in the storage unit 32 of the information processing device 3, the storage unit 22 of the user terminal 2, or in a predetermined storage area including an external storage device. In this embodiment, as an example, it is shown that each table T1 to T3 is stored in the storage unit 32 of the information processing device 3. Furthermore, each table T1 to T3 may be configured separately, or they may be configured as an integrated database.
[0045] In the information processing system 1, digital tickets (hereinafter sometimes simply referred to as "tickets") for various transportation services provided by transportation operators are provided. Users can use transportation services by displaying the tickets on their own user terminal 2.
[0046] User terminal 2 is a terminal device owned by a user who uses transportation services. Information processing device 3 is an information processing device that provides a platform for acquiring and using tickets for various transportation services provided by multiple transportation operators. Information processing device 3 enables the user to acquire and use tickets in response to user terminal 2 accessing the platform by executing a predetermined application. Hereinafter, the operator that provides the functions of the said platform may be referred to as the platform provider.
[0047] In this embodiment, when a user acquires and uses a ticket on the above platform, predetermined suggestion information is presented to the user via the user terminal 2. The suggestion information includes suggestion content, which is generated based on the ticket information related to the above ticket and contextual information about the user. This makes it possible to provide the user with useful information by utilizing the ticket information, thereby improving the usability of the ticket information.
[0048] The suggestion information actually presented to the user may be the suggestion content itself, information composed by appropriately editing the suggestion content (such as using the user's preferred writing style), or information with additional information added to the suggestion content. For example, the suggestion information may be generated based on the suggestion content in a manner that the user would prefer to see, based on the user's contextual information. In other words, the presentation unit 333 may generate and present suggestion information suitable for the user based on the acquired suggestion content.
[0049] For example, the proposed content may include the user's destination. This allows the user to easily understand the facilities and other places they should visit using their ticket. Another example is that the proposed content may include countermeasures for disasters. These countermeasures may include methods to avoid or mitigate the effects of a disaster, such as providing evacuation sites or alternative routes to avoid sections of transportation that have become unusable due to the disaster. This allows the user to easily understand disaster countermeasures using their ticket.
[0050] As shown in Figure 5, first, the acquisition unit 331 acquires ticket information (activity A101). The ticket information is information about a digital ticket that can be used to use the transportation service. The ticket information is information about a ticket associated with the user, and may include information about tickets that the user can currently use, and information about tickets that the user was able to use in the past (tickets included in the usage history). The ticket information may also be information indicating that no particular ticket is associated with the user, or information about tickets that are not associated with the user. In other words, the digital ticket is configured to be associated with a user, or to be able to be associated with a user.
[0051] The tickets include so-called visually inspected tickets and tear-off tickets, which become usable when displayed on the display unit 24 of the user terminal 2. This allows the user to use the transportation by showing the displayed ticket to the crew. Alternatively, the ticket may become usable when an image acquired by a camera connected to the user terminal 2 is displayed on the display unit 24. This allows the user to use the transportation by reading a code installed in the vehicle, etc., with the camera. Furthermore, the ticket may be a coupon offering discounts or other benefits that can be used when purchasing or using other tickets.
[0052] Figure 6(A) shows the ticket information table T1, which manages ticket information. The ticket information table T1 records ticket information associated with each user. In the ticket information table T1, the ticket ID (ticket name), type, section, validity period, usage history, and availability are recorded in association with the user ID.
[0053] A user ID is information that uniquely identifies each user and is composed of a string of characters or the like. A ticket ID is information that uniquely identifies each ticket and is composed of a string of characters or the like. Instead of a ticket ID, a ticket name composed of a string of characters that a person can uniquely recognize may be used. The type is information that indicates the type of ticket and is information that is set in advance based on the purpose and manner of use of the ticket. Types based on manner of use may include, for example, a one-time "regular ticket," a "multi-ride ticket" with a set number of uses, a "free pass" that can be used any number of times on a section predetermined by the transportation company for a specified period, and a "commuter pass" that can be used any number of times on a section selected by the user for a specified period. Types based on purpose may include information that identifies the user who can acquire and use the ticket, such as "commuter" or "schooler," information that indicates the purpose of use, such as "tourism," and information that indicates the type of transportation, such as "bus" or "train." Types based on manner of use and types based on purpose may be set independently as ticket types, or they may be set in combination as ticket types.
[0054] The "section" indicates the range of transportation that can be used with the ticket. The section includes information indicating the starting and ending points, and shows that boarding and alighting are possible at any point (station, stop, etc.) between the starting and ending points. Furthermore, if no section is specified, or if the section is "free," it indicates that the user can board and alight at any point.
[0055] The validity period is information indicating the period during which the ticket can be used on the transportation in question. For example, the validity period includes information indicating the start date and end date.
[0056] The usage history is information indicating that the ticket has been used by the user. The usage history includes, for example, information such as the date and time of boarding, the boarding location, the date and time of alighting, and the alighting location. For example, the date and time of boarding and the boarding location may be determined based on the date and time when the ticket was first displayed on the display unit 24 of the user terminal 2 (on an odd-numbered number of times) and the location information of the user terminal 2, and the date and time of alighting and the alighting location may be determined based on the date and time when the ticket was displayed next (on an even-numbered number of times) and the location information of the user terminal 2. In addition, if the ticket is used by having the ticket displayed on the display unit 24 read by a reader installed in the vehicle or ticket gate, the usage history may be determined based on the date and time and location information when the ticket was read. In this case, the usage history may also be determined based on information transmitted from the vehicle or ticket gate, and information indicating at least one of the date and time and location may be determined by the vehicle or ticket gate.
[0057] The usability status indicates whether or not the ticket can be used to travel at the present time. Usability may be determined by whether or not the usability conditions set for the ticket or ticket type are met. For example, if the current date and time deviate from the ticket's validity period, the ticket will be deemed unusable. Also, if the number of times the ticket has been used, as determined based on the usage history, has reached the number of times it can be used, the ticket will be deemed unusable.
[0058] Returning to Figure 5, the acquisition unit 331 acquires context information (Activity A102). Context information is information about the user using the digital ticket. In other words, context information is various pieces of information that can identify the user's state, the environment and circumstances in which the user is located, etc. Context information may include at least one of the following: information entered by the user via the input unit 25, information acquired at the user terminal 2, and information managed by the information processing device 3 in relation to these.
[0059] Figure 6(B) shows the context information table T2, which manages context information. The context information table T2 records context information associated with each user. In the context information table T2, attribute information, specified information, time information, location information, and weather information are recorded in association with the aforementioned user ID.
[0060] Attribute information is information that describes a user's characteristics and may include, for example, the user's address, age, gender, occupation, financial status, family structure, nationality, language spoken, etc. Attribute information may be entered by the user when creating an account on the platform, or it may be identified based on the user's behavioral history, etc. Attribute information may also include various historical information such as past information browsing history, past product purchase history, past location information history, device type used, and IP address. Furthermore, attribute information may include information indicating the user's planned activities, such as appointments and tasks, such as the user's calendar information.
[0061] The specified information is information entered by the user to specify the content of the suggestion. The specified information may be information identified from the question entered by the user. For example, from a question such as "Please tell me some recommended tourist spots," it may be identified that the type of destination the user is seeking in the suggestion is a "tourist spot." The specified information may be the question entered by the user itself, or it may be keywords extracted through natural language processing of the question. Furthermore, the specified information may be selected by the user from multiple options. Specific examples will be given later.
[0062] Time information indicates the date and time at which the context information was acquired. For example, time information is the date and time when the acquisition unit 331 acquired the specified information from the user. If the specified information has not been acquired from the user (for example, when the suggested content is generated without user input), it may be a predetermined date and time, or the date and time at which the suggested content is scheduled to be generated.
[0063] Location information is information that indicates a location associated with a user. The location associated with a user may be at least one of the user's current location and destination at the date and time specified by the time information mentioned above. In other words, if the user's destination is specified based on the specified information, the location information may be the location information of the destination. Location information is, for example, latitude and longitude information obtained by the GPS or other device on the user terminal 2. In other words, context information includes location information to identify the user's current location.
[0064] Weather information is observational or forecast data regarding atmospheric conditions and changes therein at a location associated with the user. The location associated with the user may be at least one of the user's current location and destination at the date and time specified by the time information above. That is, if the user's destination is specified based on the specified information, the weather information may be the weather information for the destination. The weather information may also cover a wide area within a predetermined range that includes at least one of the user's current location and destination.
[0065] Returning to Figure 5, the acquisition unit 331 acquires further external information (activity A103). The external information may be acquired from a predetermined storage area in an external device of the information processing system 1. The external device may include multiple information processing devices, each of which may be configured to provide different types of external information.
[0066] Figure 6(C) shows the external information table T3, which manages external information. The external information table T3 records external information acquired from the outside by the information processing device 3. In the external information table T3, the type, content, time information, location information, and proposed conditions are recorded in association with the external information ID.
[0067] The external information ID is information that uniquely identifies the external information acquired by the acquisition unit 331, and is composed of a string of characters or the like. The type is information that indicates the type of external information, and is information that is pre-set according to the content of the external information. Examples of external information types include "events" indicating that an event will be held, "tourism" indicating recommended tourist destinations, "sales" indicating discounts on goods or the provision of special goods, and "disasters" indicating that the use of public transportation is restricted at a specified location due to earthquakes, fires, transportation delays, etc. In other words, the external information includes disaster information related to disasters relevant to the user.
[0068] The content describes the nature of the external information; for example, it details the information corresponding to the type of external information mentioned above. Further details will be provided later.
[0069] Time information indicates the date and time at which the external information was acquired. Time information may also indicate the date and time when an event related to the content of the external information occurred.
[0070] Location information is information that indicates a location related to the external information in question, for example, latitude and longitude information indicating the location where an event related to the content of the external information occurred. Location information only needs to be information that can identify the location, and may include the name of a facility or information indicating the operating section of a transportation service. Location information may include, for example, information indicating a facility where an "event" is being held, a recommended tourist spot, a store where a "sale" is being held, or the location where a "disaster" has occurred. It may also include information indicating sections where the use of transportation services is restricted due to a "disaster".
[0071] The proposal conditions are information that indicates the conditions under which the external information will be presented to the user as part of the proposal. For example, the external information will be presented to users who satisfy the conditions specified in the proposal conditions, in such a way that it is included in the proposal. Whether or not the proposal conditions are satisfied can be determined based on the ticket information and context information associated with the user.
[0072] Returning to Figure 5, the identification unit 332 identifies the type of destination desired by the user based on the ticket information (Activity A104). In other words, the ticket information includes information that can identify the type of destination desired by the user. The type of destination may be identified, for example, based on the type of ticket. For example, if the ticket type is "free pass," "sightseeing" may be identified, and if it is a "(commuter) pass," "restaurants" may be identified.
[0073] Furthermore, the type of destination may be determined based on the user's contextual information. For example, if the specified information includes "place to go for fun" and the ticket information is "(commuter) pass," then "live event" may be determined. In addition, the type of destination may be determined based on various other pieces of information recorded in the contextual information table T2.
[0074] For example, the type of destination may be determined based on ticket information and time information associated with the user. Specifically, if the ticket type is a "(commuter) pass," then depending on whether the time information is for the morning commute, destination types such as "cafe" or "restaurant that serves breakfast" may be determined, and depending on whether the time information is for the evening / night commute, destination types such as "izakaya" or "restaurant" may be determined. This makes it possible to narrow down the types of destinations to suit the user's situation.
[0075] Furthermore, for example, the type of destination may be identified based on ticket information and weather information associated with the user. For instance, if the ticket type is a "(student) commuter pass," and the weather information is "rain," then destinations such as a "cafe" or "library" where one can read or study may be identified. This allows for the selection of destination types that are more appropriate to the user's situation.
[0076] Furthermore, the external information acquired by the acquisition unit 331 may be a broad collection of information without being associated with a specific user, or it may be external information associated with a specific user. That is, the external information acquired by the acquisition unit 331 may be identified based on at least one of ticket information and context information. For example, the system may be configured to acquire external information corresponding to the type of destination identified as described above.
[0077] Furthermore, the type of destination may be determined based on acquired external information. For example, if information regarding "disaster" is acquired as external information, evacuation sites or detour routes may be identified as the type of destination, regardless of ticket information.
[0078] Next, the artificial intelligence unit 334 generates a prompt to be input to the artificial intelligence module (activity A105). In this embodiment, the artificial intelligence module includes a large-scale language model. The prompt includes a textual instruction, such as in natural language, to cause the large-scale language model to output a predetermined suggestion. The prompt is also generated to include at least ticket information, context information, and, if necessary, external information.
[0079] A prompt may include all of the ticket information for a given ticket and the context information for a given user, or it may be configured to selectively include the ticket information and context information based on information specified by the user. Similarly, external information to be included in the prompt may be identified based on information specified by the user. Furthermore, if the conditions for suggesting external information are met based on the user's ticket information and context information, that external information may be included in the prompt. The prompt may include, for example, an instruction statement such as, "Using the 'ticket information,' 'context information,' and 'external information' identified above, suggest destinations to recommend the user to visit."
[0080] Furthermore, the type of destination identified by the identification unit 332 may be configured to be input to the artificial intelligence module as ticket information or designation information. On the other hand, the artificial intelligence unit 334 may generate a prompt to cause the artificial intelligence module to identify the type of destination based on the ticket type. That is, activity A104 may be executed as activity A105.
[0081] The artificial intelligence unit 334 inputs the generated prompt to the artificial intelligence module equipped with a large-scale language model (activity A106). This causes the artificial intelligence unit 334 to have the artificial intelligence module output a predetermined suggestion. The artificial intelligence unit 334 records the outputted suggestion in the storage unit 32, and the acquisition unit 331 then acquires the suggestion.
[0082] In other words, the proposed content is output by inputting at least ticket information and context information into a large-scale language model. Furthermore, the proposed content is output by inputting ticket information, context information, and external information into a large-scale language model. In addition, if the proposed content includes countermeasures that indicate measures against a disaster, the countermeasures are output by inputting ticket information, context information, and external information into a large-scale language model.
[0083] The presentation unit 333 presents the user with proposal information that includes predetermined proposal content. Based on the proposal content acquired by the acquisition unit 331, the presentation unit 333 executes a process to display a display screen containing the proposal information on the display unit 24 of the user terminal 2. This ensures that the proposal content is presented in a manner that is easy for the user to understand.
[0084] Here, we will explain specific examples of the identified ticket information, context information, and external information, and the proposals presented based on them. The following shows (1) the usage scenario, (2) the specified information entered by the user, (3) the ticket information, (4) other context information, (5) external information, and (6) the proposal content for each specific example.
[0085] (1) Suggested sightseeing course for the afternoon (2) "Where would you recommend going with the ticket you are currently using or have available?" (Question from the user) (3) Sightseeing pass (in use), multi-ride ticket (3 rides remaining) (4) Current location, current weather (sunny), time (13:00) (5) Event Information (Illuminations are being held at point C at night) (6) "From now on, the smoothest way to travel is to use a free pass to go from point A to point B, and then use a multi-ride ticket to go from point B to point C. In the evening, I recommend the illuminations held at point C." In this example, suggestions are presented using the user's current location and weather information for that location. This allows for suggestions tailored to the user's situation at that particular time, even with the same ticket information.
[0086] <Recommendations for efficient use of commuter passes> (1) Information on eating, drinking, and entertainment on the way home (2) "I'd like to stop somewhere on the way home." (User question) (3) Commuter pass (4) Time (Friday night) (5) Information on congestion at public transportation and stores, and information on sales events. (6) "Happy hour is currently being held at △△ Bar near ○○ Station. You can stop by on your way home." In this example, destinations are suggested using ticket type and time information. This allows for suggestions tailored to the user's needs at that particular time, even with the same ticket information.
[0087] <Recommendations for disaster preparedness methods> (1) Proposal of alternative routes in case of train service suspension (2) None (3) Commuter passes, multi-ride tickets (4) Attribute information (occupation, meeting schedule), current location, time (current time) (5) Earthquake alerts, information on delays and cancellations of public transportation (6) "Train service is currently suspended around XX Station. Here is an alternative route that you can use with your commuter pass from your current location. Although it is not covered by the alternative route, using your multi-ride ticket will increase your chances of arriving on time for the △△ meeting." In this example, suggestions are presented using disaster information and other relevant data. Furthermore, suggestions are presented regardless of the user's input of specified information. This allows for the rapid presentation of the most suitable countermeasures based on the ticket information available to the user.
[0088] <Personalized suggestions based on ticket usage history> (1) Travel planning support (2) None (3) History of past use of tourist passes (4) Attribute information (single, no plans for the weekend in two weeks), (5) Event information (that the autumn leaves are at their peak in tourist areas) (6) "In two weeks, when I have no plans, the autumn leaves will be at their peak at △△ Station, a place I didn't visit last time using the ○○ bus free pass." In this example, suggestions are presented based on the user's past ticket usage history. This can stimulate user demand for new tickets.
[0089] 3.3 Specific Examples of Information Processing This section further describes specific examples of processes performed in Information Processing System 1. For each specific example, the related processes will be explained with reference to the activity diagram shown in Figure 5 as appropriate. In other words, each specific example of a process may be included within the scope defined in the overview and details of the information processing described above.
[0090] Figures 7 to 9 are examples of screens whose display is controlled by the presentation unit 333 in the information processing system 1. FIG. 7 is a diagram showing an example of the TOP screen 700 displayed on the display unit 24 of the user terminal 2. FIG. 8 is a diagram showing an example of the list screen 800 displayed on the display unit 24 of the user terminal 2. FIG. 9 is a diagram showing an example of the ticket screen 900 displayed on the display unit 24 of the user terminal 2.
[0091] <TOP screen> The TOP screen 700 is the screen first displayed on the display unit 24 when the user operates the user terminal 2 to access the platform. As shown in FIG. 7, the TOP screen 700 includes a ticket purchase area 710, a ticket usage area 720, an interaction area 730, and a presentation area 740.
[0092] The ticket purchase area 710 is an area for receiving an operation for the user to search for and purchase a desired ticket. The ticket purchase area 710 includes a search area 711. The user can search for a desired ticket by inputting a predetermined keyword into the search area 711. The user can purchase the ticket by causing the information indicating the details of the ticket hit by the search to be displayed on the display unit 24 and executing a settlement process. The purchased ticket is recorded in the ticket information table T1 in association with the user.
[0093] The ticket usage area 720 is an area for receiving an operation for the user to use the acquired ticket. The ticket usage area 720 includes transition buttons 721 to 723, and information indicating the type of ticket is associated with each of them. When any one of the transition buttons 721 to 723 is operated by the user, the list screen 800 including the tickets of the type corresponding to the selected transition button 721 to 723 is displayed on the display unit 24. In the present embodiment, FIG. 8 shows the list screen 800 when the transition button 721 for displaying all types of tickets is operated.
[0094] The dialogue area 730 is an area that receives user-specified information and displays suggested information. The dialogue area 730 includes an input area 731 and a presentation area 732. The input area 731 accepts a question from the user as specified information. The presentation area 732 displays suggested information indicating the suggested content acquired by the acquisition unit 331. As an example, the input area 731 and the presentation area 732 show a question and suggested information corresponding to the aforementioned <recommendation for efficient use of commuter passes>.
[0095] The presentation area 740 is the area where the suggestion information is displayed. The presentation area 740 displays suggestion information that indicates the suggestion content acquired by the acquisition unit 331 without receiving any information specified by the user. In other words, the presentation unit 333 may present the suggestion content to the user regardless of whether the context information includes specified information or not. As an example, the presentation area 740 displays suggestion information corresponding to the aforementioned <personalized suggestion based on ticket usage history>.
[0096] For example, the system may be configured to display proposal information in the presentation area 740 when at least one of the ticket information and context information satisfies predetermined conditions. Furthermore, the system may be configured to update the proposal information displayed in the presentation area 740 at predetermined intervals. Additionally, the system may be configured to display proposal information based on external information when external information is acquired that satisfies the proposal conditions for at least one of the user's ticket information and context information.
[0097] Furthermore, in the dialogue area 730 and the presentation area 740, suggestion information is presented based on ticket information for all tickets associated with the user. This allows the user to see suggestions that comprehensively consider all tickets.
[0098] <List screen> The list screen 800 is a screen that displays a list of at least one of the tickets acquired or used by the user, and the tickets that the user can acquire or use. As shown in Figure 8, the list screen 800 includes a ticket area 810, a ticket area 820, a dialogue area 830, and a presentation area 840.
[0099] Ticket area 810 is an area where one or more tickets associated with the transportation service provider "XX City Transportation" are displayed, with ticket 811 being an example. Ticket area 820 is an area where one or more tickets associated with the transportation service provider "XX Railway" are displayed, with ticket 821 being an example. Tickets 811 and 821 display information indicating the ticket's contents, such as the ticket name, type of transportation, validity period, and valid section. The information indicating the ticket's contents is displayed based on the ticket information recorded in ticket information table T1.
[0100] Here, tickets 811 and 821 may be tickets that the user has already purchased on the platform. In this case, ticket 811 is associated with display button 812 and displayed, and ticket 821 is associated with display button 822. When at least one of display buttons 812 or 822 is operated, the display on the display unit 24 transitions to the ticket screen 900, which will be described later.
[0101] Thus, as the first presentation step, the presentation unit 333 presents the user with a list screen 800 in which multiple digital tickets are displayed in a list.
[0102] The dialogue area 830 is an area that receives user-specified information and displays suggested information. The dialogue area 830 includes an input area 831 and a presentation area 832. The input area 831 accepts a question from the user as specified information. The presentation area 832 displays suggested information indicating the suggested content acquired by the acquisition unit 331. As an example, the input area 831 and the presentation area 832 show a question and suggested information corresponding to the aforementioned <recommendation for efficient use of commuter passes>.
[0103] The presentation area 840 is the area where the suggested information is displayed. The presentation area 840 displays suggested information that the acquisition unit 331 has acquired, without accepting any information specified by the user. In other words, the presentation unit 333 may present the suggested information to the user regardless of whether the context information includes specified information or not. As an example, the presentation area 840 displays suggested information corresponding to the aforementioned <recommendation of disaster countermeasures method>.
[0104] Thus, as a second presentation step, the presentation unit 333 presents at least one of the following on the list screen 800: an input screen for receiving contextual information from the user and suggested information.
[0105] Furthermore, if proposal information is presented in at least one of the presentation area 832 and presentation area 840, the acquisition unit 331 may acquire ticket information relating to at least one of the multiple digital tickets displayed on the list screen 800. This allows the user to be presented with proposal information that covers the ticket information relating to the tickets presented on the list screen 800. In addition, the user can intuitively understand that the proposal information covers the ticket information relating to the tickets presented on the list screen 800.
[0106] Furthermore, when the user selects a predetermined ticket on the list screen 800, the acquisition unit 331 may be configured to acquire ticket information related to the selected ticket, rather than all tickets presented on the list screen 800. This allows suggested information based on the ticket information related to the selected ticket to be presented in at least one of the presentation area 832 and presentation area 840, potentially improving user convenience.
[0107] For example, even if the same question is entered in input area 831 as in input area 731, the suggested information in suggested area 832 may differ from that in suggested area 732 due to the different ticket information being referenced. In addition, suggested information that can be presented to suggested area 740 may be presented in suggested area 840, or suggested information based on ticket information relating to at least one of the tickets displayed on list screen 800 may be presented. That is, the system may be configured so that suggested information based on ticket information of tickets that are not currently available is not presented. Conversely, in the ticket purchase screen (not shown) accessed from ticket purchase area 710, since tickets not owned by the user are displayed in a list, the system may be configured to present suggested information based on ticket information of tickets that are not currently available.
[0108] <Ticket screen> The ticket screen 900 is an example of a screen displayed on the display unit 24 when at least one of the display buttons 812 and 822 is operated. As shown in Figure 9, the ticket screen 900 includes a ticket area 910, a dialogue area 920, and a presentation area 930.
[0109] The ticket area 910 includes ticket information 911 and a ticket frame 912. The ticket information 911 displays at least a portion of the information indicating the contents of the selected ticket. The information indicating the contents of the ticket is displayed based on the ticket information recorded in the ticket information table T1. The ticket frame 912 is the area where the ticket face is displayed, for example, code 913 is displayed. Users can use public transportation by having the ticket read by a reader installed in the vehicle when boarding and alighting from the transportation.
[0110] Thus, as the first presentation step, the presentation unit 333 causes the user to see a ticket screen 900 on which a predetermined digital ticket is displayed.
[0111] The dialogue area 920 is an area that receives user-specified information and displays suggested information. The dialogue area 920 includes an input area 921 and a presentation area 922. The input area 921 accepts a question from the user as specified information. The presentation area 922 displays suggested information indicating the suggested content acquired by the acquisition unit 331. As an example, the input area 921 and the presentation area 922 show a question and suggested information corresponding to the aforementioned <recommendation for efficient use of commuter passes>.
[0112] The presentation area 930 is the area where the suggested information is displayed. The presentation area 930 displays suggested information that the acquisition unit 331 has acquired, without accepting any information specified by the user. In other words, the presentation unit 333 may present the suggested information to the user regardless of whether the context information includes specified information or not. As an example, the presentation area 930 shows suggested information corresponding to the aforementioned <recommendation of disaster countermeasures method>.
[0113] Thus, as a second presentation step, the presentation unit 333 presents at least one of the following on the ticket screen: an input screen for receiving contextual information from the user and suggested information.
[0114] Furthermore, if suggestion information is presented in at least one of the presentation area 922 and presentation area 930, the acquisition unit 331 acquires ticket information relating to the digital ticket displayed on the ticket screen 900. This allows the user to be presented with suggestion information based on the ticket information relating to the ticket presented on the ticket screen 900. In addition, the user can intuitively understand that the suggestion information is based on the ticket information relating to the ticket presented on the ticket screen 900.
[0115] For example, even if the same question is entered in input area 921 as in input areas 731 and 831, the suggested information in suggested area 922 may differ from that in suggested areas 732 and 832 due to the different ticket information being referenced. Furthermore, suggested information that can be presented in suggested area 740 may be presented in suggested area 930, or suggested information based on ticket information relating to at least one of the tickets displayed on the ticket screen 900 may be presented. In other words, the system may be configured so that suggested information based on ticket information other than the displayed ticket is not presented.
[0116] 4. Variations The following embodiments may be adopted for the information processing system 1 according to this embodiment.
[0117] In the embodiments described above, the specified information is exemplified as a question entered by the user, but it is not limited to this. The specified information may be identified based on the options selected by the user. For example, icons representing "weather," "current location," etc., may be displayed in the input areas shown on the TOP screen 700, the list screen 800, and the ticket screen 900, and at least one of these may be selected by the user. Then, information such as "weather information" and "location information" corresponding to the selected icon may be associated with the user as context information. Alternatively, an icon for "ticket" may be displayed in the input area, and the system may be configured to accept the selection of a predetermined ticket from the user, and ticket information related to the selected ticket may be identified. The artificial intelligence unit 334 may generate prompts to be input to the large-scale language model based on the identified ticket information and context information.
[0118] Furthermore, while it has been illustrated that the input area for receiving specified information and the presentation area for presenting suggested information are displayed on the TOP screen 700, the list screen 800, and the ticket screen 900, the explanation is not limited to these. The input area and the presentation area may be displayed on at least one of the TOP screen 700, the list screen 800, and the ticket screen 900. Alternatively, at least one of these may be configured to display only the input area or the presentation area. For example, the TOP screen 700 may display only the input area 731, and the suggested information based on the specified information entered in the input area 731 may be displayed on at least one of the presentation areas 832 and 840 on the list screen 800, or the presentation areas 922 and 930 on the ticket screen 900.
[0119] Furthermore, while the above-described embodiment primarily illustrates the acquisition of context information in parallel with ticket information by the acquisition unit 331, it is not limited to this. The acquisition unit 331 may acquire context information together with ticket information, or it may acquire context information by extracting it from ticket information, for example.
[0120] For example, the acquisition unit 331 may extract each item of ticket information recorded in the ticket information table T1 (e.g., type, validity period, usage history, etc.). The identification unit 332 may identify user attribute information as at least part of context information based on the type of ticket (including types based on purpose) included in the extracted ticket information. Specifically, the identification unit 332 may identify that the user is a student if the ticket type is a student commuter pass, that the user is employed if the ticket type is a commuter pass, and that the purpose of use is tourism if the ticket type is a tourist pass.
[0121] Furthermore, the identification unit 332 may identify at least one of the time information and location information relating to the user based on at least one of the boarding date and time, boarding location, alighting date and time, and alighting location included in the usage history. Here, the time information may be information indicating the date and time when the context information was acquired, or information indicating the boarding date and time or alighting date and time included in the usage history. The location information may be information indicating the current location based on the positioning result of the user terminal 2, or information indicating the boarding location or alighting location included in the usage history. The identification unit 332 may record at least one of the identified attribute information, time information, and location information in the context information table T2.
[0122] Furthermore, the identification unit 332 may identify the correspondence between ticket information and context information by using predetermined reference information. The reference information may be a lookup table or determination rule that associates items of ticket information with items of context information. Alternatively, the reference information may be an artificial intelligence model (trained model, general-purpose model, etc.) configured to take items of ticket information as input and output items of context information.
[0123] The acquisition unit 331 may acquire status information regarding the subject of use reserved or contracted by the user, associate this status information with the user ID, and record it in the context information table T2 as an example of context information. The status information may be recorded, for example, as attribute information (including scheduled information) in the context information table T2. The subject of use is the subject for which the user has secured the right to use, and may be goods (including movable and immovable property) or services provided by a specified business operator or individual. The subject of use may include reserved subjects that the user reserves, or contract subjects that the user contracts.
[0124] The acquisition unit 331 may acquire information as status information relating to the reservation target, including at least one of the following: whether or not a reservation is made, the date and time of the reservation or the period of use, the name of the use target, and information that can identify the location of the place related to the reservation target. The acquisition unit 331 may also acquire information as status information relating to the contract target, including at least one of the following: whether or not a contract exists, the type of contract, the contract period or validity period, a name or identifier that can identify the contract target, and information that can identify the location of the place related to the contract target. The type of contract may include at least one of the following: membership contract, usage contract, employment contract, contract related to attending school or cram school, tenancy contract, membership contract, service provision contract, lease contract for real estate, sublease contract, loan for use contract, sales contract, transfer contract, and contracts incidental thereto (such as management consignment contract, parking lot usage contract, etc.).
[0125] The identification unit 332 may identify first location information as part of context information based on information that can identify the location of the subject of use included in the situation information. The first location information is information about a place related to the subject of use that the user reserves or contracts for. In this example, the subject of use may be based on the premise that the user will visit the place of provision in order to receive the goods or services related to the subject of use, and as the subject of use is specified by the user or as the identification unit 332 identifies the subject of use based on the situation information, the first location information associated with the subject of use becomes identifiable. For example, the place related to the subject of use may be the place where the goods or services related to the reserved subject are provided, and the place where at least part of the matters stipulated in the contract subject are performed. The first location information may also be information that can identify the place by latitude and longitude, address, facility name, or a combination thereof.
[0126] Locations related to the reservation subject may include, for example, theme parks, amusement parks, zoos, aquariums, swimming pools, bathing facilities, parks, gardens, entertainment facilities such as concert halls and live music venues, cafes and restaurants and other dining establishments, cultural facilities such as art museums, museums and exhibition facilities, sports facilities such as baseball stadiums and stadiums, temples and shrines, educational institutions, and facilities that provide users with a specified experience. In addition, locations related to the reservation subject may be the pick-up location for the specified product reserved by the user.
[0127] The location related to the subject matter of the contract may include at least one of the following: the location where the goods or services under the contract are provided, the location where the subject matter of the contract exists, the location designated as the contractual address, or the location designated as the delivery address. The subject matter of the contract may be the location of real estate that the user wishes to occupy, or it may be the use of facilities, etc., corresponding to a place that the user intends to visit regularly for a specific purpose. A place that the user intends to visit regularly may be, for example, a nursing home, a care facility, or a place where the user regularly meets with family members, etc. Furthermore, "a place where the user intends to do XX" may be a place where the user intends to cause another person to perform the action corresponding to XX. For example, if the user is a parent and intends to have their child attend a specific school, that school may correspond to "a place where the user intends to have their child attend school."
[0128] The identification unit 332 may identify the proposed content based on the first location information, etc. The artificial intelligence unit 334 may include the first location information related to the identified target of use as context information in the prompt, and output the proposed content by inputting the prompt into the large-scale language model. In other words, the context information may include the first location information.
[0129] The proposed content may include information indicating transportation services available to the user to travel to the location indicated by the first location information, and candidate tickets available to the user to use said transportation services. The candidate tickets may be identified by the identification unit 332 from among the tickets included in the ticket information table T1 based on the ticket information and the first location information, or they may be identified by the large language model based on the ticket information and the first location information included in the prompt. In other words, the proposed content may include information about digital tickets available to use transportation services related to the first location information.
[0130] Furthermore, the acquisition unit 331 may acquire second location information associated with the user. The second location information is information that can identify the departure point from which the user begins using the transportation service, and may be the current location based on the positioning results of the user terminal 2, the place of residence (address) or place of work registered in the account, etc. The second location information may also be the departure point (the nearest station on the identified transportation service, etc.) when moving to the location indicated by the first location information, which is identified from these locations. The identification unit 332 may identify candidate tickets for the user to move to the location indicated by the first location information based on the first location information and the second location information (and any context information included in the context information table T2 as needed). The artificial intelligence unit 334 may input the first location information and the second location information as context information along with the ticket information into a prompt and have the large-scale language model output a proposal content including candidate tickets.
[0131] Figure 10 shows an example of a dialogue screen 1000 displayed on the display unit 24 of the user terminal 2. The dialogue screen 1000 is an example of a screen for presenting suggested information to the user based on information related to the target of use, and corresponds to the dialogue areas 730, 830, and 920 shown in Figures 7 to 9. In the dialogue screen 1000, the specified information entered by the user and the response text and suggested information generated in response to that specified information are displayed in a dialogue format. The input field 1030 is an area that accepts input of specified information by the user. The send button 1040 is an object that accepts an operation to send the specified information entered in the input field 1030 to the information processing device 3. The information presented to the user, such as the response text, suggested information, and various objects, may be output by inputting ticket information, context information, and specified information entered or specified by the user into predetermined reference information (such as a large-scale language model).
[0132] Specified information 1010 is specified information entered by the user and includes a suggestion to present recommended tickets.
[0133] Response 1020 is a statement that provides a response to specified information 1010. Response 1020 includes content that prompts the user to enter information regarding the aforementioned target of use (reservation target).
[0134] The presentation unit 333 may present an input button 1021 for prompting the user to input information about the subject of use. The input button 1021 may be configured to transition to a web page where information about the subject of use can be obtained when the user operates it. For example, when the input button 1021 is operated, the presentation unit 333 may prompt the user to link information about the subject of use between the web page where the user manages information about the subject of use and the platform provided by the information processing device 3. As a result, the acquisition unit 331 can obtain status information about the subject of use from the linked source.
[0135] The designated information 1011 displays at least a portion of the information regarding the target of use, which is identified based on the status information acquired by the acquisition unit 331. The designated information 1011 includes the name of the target of use and the first location information. The designated information 1011 also includes second location information acquired from the user terminal 2 or the information processing device 3. The designated information 1011 may be entered by the user, or it may be configured to automatically display acquired information.
[0136] Furthermore, the acquisition unit 331 may acquire information about the target of use without relying on user input operations. The artificial intelligence unit 334, as an AI agent, may generate access procedures (procedures for acquiring status information stored in an external device) for collecting information about the target of use based on a generating AI (such as a large-scale language model). The artificial intelligence unit 334 may identify the target web page (e.g., reservation site, contract management site, etc.) based on the user terminal 2's information browsing history (including web browsing history), location information history, and behavioral history such as usage history recorded in the ticket information table T1. The artificial intelligence unit 334 may execute the above access procedures using authentication information or linkage information previously authorized by the user, causing the acquisition unit 331 to acquire information about the target of use. Alternatively, the artificial intelligence unit 334 may input information entered by the user into the generating AI, similarly causing the acquisition unit 331 to acquire information about the target of use.
[0137] Proposal information 1022 displays "Bus Ticket 2" as proposal information identified based on the acquired information regarding the target user. In addition to proposal information 1022, a display button 1023 and an execution button 1024 are also displayed.
[0138] The display button 1023 is an object that accepts an operation to display detailed information about the identified "bus ticket 2" on the user terminal 2. When the display button 1023 is operated, it may be configured so that at least a portion of the ticket information for "bus ticket 2" is displayed on the user terminal 2.
[0139] The execute button 1024 is an object that accepts user input regarding the execution of the purchase process for "Bus Ticket 2". When the execute button 1024 is operated, the user terminal 2 may be configured to activate a payment method for purchasing the ticket. The payment method may be a credit card, electronic money, code payment, etc. Furthermore, when the execute button 1024 is operated, the system may be configured to transition to the ticket purchase screen, which can be accessed from the ticket purchase area 710 on the TOP screen 700. Note that the price (special price) when purchasing the ticket via the execute button 1024 on the dialogue screen 1000 may be set lower than the price (regular price) when transitioning from the ticket purchase area 710, etc.
[0140] The proposed information 1025 includes a notification that payment for the ticket has been completed and the user can now use the ticket. The display unit 333 may also display a display button 1026 along with the proposed information 1025. The display button 1026 is an object that accepts an operation to display the ticket on the dialogue screen 1000 for use with the ticket.
[0141] When the display button 1026 is operated, the display unit 333 displays the ticket area 1027. The ticket area 1027 has the same configuration as the ticket area 910 shown on the ticket screen 900. At this time, the artificial intelligence unit 334 may output an instruction to display code 1028 by inputting information about the identified "bus ticket 2" into predetermined reference information. Based on this instruction, the display unit 333 may display code 1028 in the ticket area 1027. The user can use the ticket to use public transport by having code 1028 read by a reader installed in the vehicle, etc., when boarding (or alighting) the transport. Thus, the proposed information (ticket area 1027) may include ticket information (code 1028) used to use the digital ticket.
[0142] The candidate tickets presented in the proposed information 1022 may be tickets that the user has not yet purchased (configured to be associated with the user) or tickets that the user has already purchased (already associated with the user). In the latter case, the presentation unit 333 may present a display button 1026 instead of the execute button 1024.
[0143] Thus, according to the dialogue screen 1000, the presentation unit 333 presents suggestion information including ticket candidates, and the purchase and usage operations for the candidate tickets are executed collectively based on the dialogue with the user. This can improve user convenience.
[0144] Furthermore, the dialogue screen 1000 is not limited to displaying proposal information based on the designation of the target user. The presentation unit 333 may display proposal information on the dialogue screen 1000 that includes proposal content identified based on arbitrary context information, ticket information, and external information.
[0145] Furthermore, advertisements relevant to the proposed content may be displayed in the presentation area. Advertisements may be in any format, including text, still images, videos, and audio. Preferably, advertisements are displayed in a way that distinguishes them from the proposed content using color tones, dividing lines, or other indicators. Display conditions may be set for advertisements, and advertisements that satisfy these conditions based on the information included in the proposed content may be displayed. Display conditions may include, for example, ticket information, types and sections of transportation services, transportation service providers, types and locations of destinations, etc. For example, if a service is suspended in a designated section of a transportation service, the presentation area may display alternative routes along with sale information from stores located around those alternative routes.
[0146] Furthermore, the acquisition unit 331 may acquire advertising information relating to advertisements presented as proposed information, as an example of the external information described above. For example, the acquisition unit 331 may acquire advertising information from an external device such as an advertising distribution server, including the content of the advertisement (including text, still images, videos, and audio), display conditions associated with the advertisement, and sponsor information indicating whether or not advertising fees have been paid or the priority of the advertisement's placement. The acquisition unit 331 may record the acquired advertising information as external information in the external information table T3. In the external information table T3, the acquisition unit 331 may record the type as "advertisement," include the content of the advertisement and sponsor information in the content, and include display conditions in the proposed conditions.
[0147] The identification unit 332 may identify information that can identify a route based on the section and transportation service provider included in the ticket information. Based on the identified route information, the identification unit 332 may extract advertising information associated with stores or facilities along the route from the external information table T3 and identify it as an advertising candidate. Based on the sponsor information, the identification unit 332 may adjust the probability or presentation order (priority) of which of the advertising candidates will be selected as a candidate to be presented to the user. The artificial intelligence unit 334 may input advertising information indicating advertising candidates, along with ticket information and context information, into a prompt and cause the large-scale language model to output proposal information that includes advertisements as suggested content (proposal information in which all or part of the suggested content is an advertisement).
[0148] Specifically, the presentation unit 333 may display advertisements along with tickets presented on the dialogue screen 1000. The acquisition unit 331 may acquire advertisement information including sponsor information indicating that advertising fees have been paid (e.g., information indicating whether or not advertising fees have been paid and the priority of advertisement placement). The identification unit 332 may select or rearrange advertisement candidates based on the sponsor information to increase the probability or priority of advertisement candidates being placed. When the presentation unit 333 displays an advertisement containing sponsor information, it may add indications such as "Sponsored" or "Advertisement" to the advertisement to clearly indicate that it contains sponsor information. Furthermore, advertisements containing sponsor information may be displayed in a way that distinguishes them from other content (content that does not contain sponsor information) using color tones, dividing lines, etc.
[0149] Furthermore, in the list screen 800 where tickets provided by multiple transportation operators are displayed, it is preferable that the display conditions be set so that advertisements from operators that compete with at least one of the transportation operators providing the displayed tickets are not displayed. In addition, if transportation operators have reviewed the advertisement content in advance and a whitelist of approved advertisements or a blacklist of rejected advertisements is stored in the storage unit 32, it is preferable that advertisements that have not been approved (or rejected) by at least one of the transportation operators providing the displayed tickets are not displayed. This prevents advertisements that are not intended by the transportation operators from being displayed.
[0150] The ticket may be configured to be usable by holding the IC card over the ticket gate without displaying the ticket face on the display unit 24. For example, an NFC (Near Field Communication) tag can be used. That is, this NFC tag may be installed on the ticket gate of a transportation system, and the user may read this tag with an NFC reader installed on the user terminal 2.
[0151] The presentation unit 333 is exemplified by displaying an image containing the proposed information on the display unit 24, but is not limited to this. The presentation unit 333 may present the proposed information in a way that the user can perceive through their five senses. For example, the user terminal 2 may be equipped with an output interface that outputs various information in a way that the user can perceive through their five senses. The output interface outputs various stimuli in a way that the user can perceive based on instructions from the presentation unit 333. For example, the various stimuli may be output as sound, tactile stimuli, smells, tastes, etc. The output interface is configured to output various stimuli individually or in combination, and these may be output together with the image displayed on the display unit 24. The output interface may be included in the housing of the user terminal 2 or it may be externally attached.
[0152] Furthermore, the output interface may be, for example, an audio output device such as a speaker, headphones, bone conduction earphones, hearing aid, or cochlear implant capable of outputting sound. The output interface may also be a tactile output device that provides contact stimuli such as vibration or temperature changes, or non-contact stimuli such as spraying air. The output interface may also be an olfactory output device that provides changes in smell by spraying aromas into the air, for example. The output interface may also be a gustatory output device that induces changes in taste in the user through electrical stimulation, for example.
[0153] In this embodiment, the transportation service available using the ticket may be any means of transport, and may be a mode of transport that operates along a predetermined route based on a timetable, such as a bus, train (railway), tram, subway, airplane, ship, ferry, sightseeing boat, water bus, cable car, monorail, etc. Alternatively, the transportation service may be an on-demand mode of transport that operates according to the user's demand, and may be a taxi, car (including rental cars and car sharing, etc.), bicycle (including rental bicycles and shared bicycles), electric scooter, drone, helicopter, motorcycle, etc.
[0154] 5. Others In the above embodiment, the acquisition unit 331, the identification unit 332, the presentation unit 333, and the artificial intelligence unit 334 are described as functional units realized by the control unit 33 of the information processing device 3. However, at least a part of these may be implemented as functional units realized by components other than the information processing device 3. Furthermore, although the user terminal 2 and the information processing device 3 controlled the storage and processing of various information, multiple external devices may be used instead of either of these. That is, various information and programs may be stored in a distributed manner across multiple external devices using blockchain technology or the like. In addition, at least one of the devices included in the information processing system 1 may be located outside the country in which the functions of the information processing system 1 are performed.
[0155] Furthermore, they may be provided in the following embodiments.
[0156] (1) An information processing system comprising at least one processor, the processor configured to perform the following steps by reading a program, wherein in the acquisition step, ticket information and context information are acquired, where the ticket information is information relating to a digital ticket usable to use a transport service, the digital ticket is associated with a user or configured to be associated with a user, the context information is information relating to the user using the digital ticket, and in the presentation step, the system causes the user to be presented with proposal information including predetermined proposal content, where the proposal content is output by inputting the ticket information and the context information into a large-scale language model.
[0157] This configuration improves the convenience of ticket information.
[0158] (2) An information processing system as described in (1) above, wherein the presentation step includes a first presentation step and a second presentation step, wherein in the first presentation step, the system presents the user with a ticket screen on which a predetermined digital ticket is displayed, or a list screen on which a plurality of digital tickets are displayed in a list, and in the second presentation step, the system presents at least one of the input screen for receiving input of the context information from the user and the proposed information on at least one of the ticket screen and the list screen.
[0159] This configuration improves the convenience for users who utilize ticket information.
[0160] (3) An information processing system as described in (2) above, wherein in the first presentation step, the ticket screen is presented to the user; in the second presentation step, at least one of the input screen and the proposed information is presented on the ticket screen; and in the acquisition step, the ticket information relating to the digital ticket displayed on the ticket screen is acquired.
[0161] This configuration improves the convenience for users who utilize ticket information.
[0162] (4) An information processing system as described in (2) above, wherein in the first presentation step, the list screen is presented to the user; in the second presentation step, at least one of the input screen and the proposed information is presented to the list screen; and in the acquisition step, the ticket information relating to at least one of the multiple digital tickets displayed on the list screen is acquired.
[0163] This configuration improves the convenience for users who utilize ticket information.
[0164] (5) An information processing system described in any one of (1) to (4) above, wherein the context information includes location information for identifying the user's current location, and the proposed content includes the user's destination.
[0165] In this manner, suggestions tailored to the user's situation are provided.
[0166] (6) An information processing system described in any one of (1) to (5) above, wherein the proposed content includes the user's destination, and the ticket information includes information that can identify the type of destination desired by the user.
[0167] This configuration improves the convenience of ticket information.
[0168] (7) An information processing system as described in (6) above, wherein the type of destination is identified based on the ticket information and the time information associated with the user.
[0169] In this manner, suggestions tailored to the user's situation are provided.
[0170] (8) An information processing system as described in (6) or (7) above, wherein the type of destination is identified based on the ticket information and the weather information associated with the user.
[0171] In this manner, suggestions tailored to the user's situation are provided.
[0172] (9) An information processing system described in any one of (1) to (8) above, wherein the acquisition step further acquires external information, wherein the external information includes disaster information relating to a disaster related to the user, and the proposed content includes countermeasures indicating countermeasures against the disaster, wherein the countermeasures are output by inputting the ticket information, the context information, and the external information into a large-scale language model.
[0173] This configuration improves the convenience of ticket information.
[0174] (10) An information processing system according to any one of (1) to (9) above, wherein in the acquisition step, external information is further acquired, wherein the acquired external information is identified based on at least one of the ticket information and the context information, and the proposed content is output by inputting the ticket information, the context information, and the external information into a large-scale language model.
[0175] This configuration improves the convenience of ticket information.
[0176] (11) An information processing system described in any one of (1) to (10) above, wherein in the presentation step, the user is made to present the proposed content regardless of whether the context information includes specified information, and the specified information is information entered by the user for specifying the proposed content.
[0177] This configuration improves the convenience for users who utilize ticket information.
[0178] (12) An information processing system described in any one of (1) to (11) above, wherein in the acquisition step, the context information is acquired by being extracted from the ticket information.
[0179] This configuration improves the convenience for users who utilize ticket information.
[0180] (13) An information processing system described in any one of (1) to (12) above, wherein the context information includes first location information, where the first location information is information about a location related to the object of use reserved or contracted by the user.
[0181] In this configuration, user convenience is improved by utilizing the user's target audience.
[0182] (14) An information processing system as described in (13) above, wherein the proposed content includes information relating to the digital ticket that can be used to use the transportation service related to the first location information.
[0183] In this configuration, a highly convenient digital ticket related to the user's intended use is provided.
[0184] (15) An information processing system described in any one of (1) to (14) above, wherein the proposed information includes ticket information used to use the digital ticket.
[0185] This configuration improves user convenience.
[0186] (16) An information processing method comprising each step of the information processing system described in any one of (1) to (15) above.
[0187] (17) A program that causes a computer to perform each step of the information processing system described in any one of (1) to (15) above. Of course, this is not always the case.
[0188] Finally, various embodiments of the present invention have been described, but these are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be implemented in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents. [Explanation of Symbols]
[0189] 1: Information Processing System 2: User terminal 3: Information Processing Device 33: Control Unit 331: Acquisition Department 332: Specific part 333: Presentation part 334: Artificial Intelligence Department 4: Network 5: Artificial Intelligence Server 700 :TOP screen 710: Ticket purchase area 720: Ticket usage area 730: Dialogue Domain 731: Input area 732: Presentation area 740: Presentation area 800: List screen 810: Ticket area 820: Ticket area 830: Dialogue Domain 831: Input area 832: Presentation area 840: Presentation area 900: Ticket screen 910: Ticket surface area 920: Dialogue Domain 921: Input area 922: Presentation area 930: Presentation area 1000: Dialogue screen 1022: Proposal Information 1025: Proposal Information 1027: Ticket surface area 1028: Code 1030: Input field 1040: Send button T1: Ticket Information Table T2: Context Information Table T3: External Information Table
Claims
1. An information processing system, The system comprises at least one processor, the processor configured to perform the following steps by reading a program: In the retrieval step, ticket information and context information are retrieved, and here, The aforementioned ticket information is information about digital tickets that can be used to use transportation services. The context information is information about the user using the digital ticket, In the presentation step, the user is asked to present proposal information containing predetermined proposal content, and here, The proposed content is output when the ticket information and the context information are input into a large-scale language model. An information processing system in which the context information is obtained by extracting it from the ticket information in the acquisition step.
2. In the information processing system described in claim 1, The aforementioned presentation step includes a first presentation step and a second presentation step, In the first presentation step, the user is presented with a ticket screen displaying a predetermined digital ticket, or a list screen displaying multiple digital tickets in a list. An information processing system that, in the second presentation step, presents at least one of the following on at least one of the ticket screen and the list screen: an input screen for receiving the context information from the user and the proposed information.
3. In the information processing system described in claim 2, In the first presentation step, the ticket screen is presented to the user. In the second presentation step, at least one of the input screen and the proposed information is displayed on the ticket screen. The acquisition step involves an information processing system that acquires the ticket information relating to the digital ticket displayed on the ticket screen.
4. In the information processing system described in claim 2, In the first presentation step, the list screen is presented to the user, In the second presentation step, at least one of the input screen and the proposed information is displayed on the list screen. The information processing system acquires the ticket information relating to at least one of the multiple digital tickets displayed on the list screen in the acquisition step.
5. In the information processing system described in claim 1, The aforementioned context information includes location information for identifying the user's current location. The proposed solution is an information processing system that includes the user's destination.
6. In the information processing system described in claim 1, The aforementioned proposal includes the user's destination, The ticket information includes an information processing system that can identify the type of destination desired by the user.
7. In the information processing system described in claim 6, An information processing system that identifies the type of destination based on the ticket information and the time information associated with the user.
8. In the information processing system described in claim 6, An information processing system that identifies the type of destination based on the ticket information and weather information associated with the user.
9. In the information processing system described in claim 1, In the aforementioned acquisition step, external information is further acquired, and here, The aforementioned external information includes disaster information relating to the user, The aforementioned proposal includes measures to address the aforementioned disaster, and here, The aforementioned countermeasure is an information processing system in which the ticket information, context information, and external information are input into a large-scale language model and output.
10. In the information processing system described in claim 1, In the aforementioned acquisition step, external information is further acquired, and here, The external information to be acquired is identified based on at least one of the ticket information and the context information. The proposed system is an information processing system in which the ticket information, context information, and external information are input into a large-scale language model and output.
11. In the information processing system described in claim 1, In the presentation step, regardless of whether the context information includes specified information, the user is asked to present the proposed content, and here, The aforementioned designated information is information entered by the user to specify the proposed content in an information processing system.
12. An information processing system, The system comprises at least one processor, the processor configured to perform the following steps by reading a program: In the retrieval step, ticket information and context information are retrieved, and here, The aforementioned ticket information is information about digital tickets that can be used to use transportation services. The context information is information about the user using the digital ticket, In the presentation step, the user is asked to present proposal information containing predetermined proposal content, and here, The proposed content is output when the ticket information and the context information are input into a large-scale language model. The aforementioned context information includes first location information, where, An information processing system in which the first location information is information about a location related to the object of use that the user reserves or contracts for.
13. In the information processing system according to claim 12, The proposed system includes information relating to a digital ticket that can be used to use the transportation service associated with the first location information.
14. An information processing system, The system comprises at least one processor, the processor configured to perform the following steps by reading a program: In the retrieval step, ticket information and context information are retrieved, and here, The aforementioned ticket information is information about digital tickets that can be used to use transportation services. The context information is information about the user using the digital ticket, In the presentation step, the user is asked to present proposal information containing predetermined proposal content, and here, The proposed content is output when the ticket information and the context information are input into a large-scale language model. The proposed information includes an information processing system that includes ticket information used to use the digital ticket.
15. Information processing method, A method comprising each step of the information processing system described in any one of claims 1 to 14.
16. It is a program, A program that causes a computer to perform each step of the information processing system described in any one of claims 1 to 14.
Citation Information
Patent Citations
Station service apparatus, control method for station service apparatus, and control program for station service apparatus
JP2021168059A
Ticket display program and ticket management device
JP2021174144A
Information processing system, information processing method, and program
JP2023078589A
Information processing system, information processing method, and program
JP7521859B1
Information processing system, information processing method, and program
JP7715442B1