program

Abstract

The goal is to allow users to learn about congestion on their usual routes when using their commuter passes. [Solution] A program that outputs ticket information regarding the validity of a pass-type digital ticket, which has a predetermined usage period and allows free boarding and alighting of public transportation within that period, upon request, causes a computer to perform the following actions: determine whether or not congestion occurs on public transportation, and if congestion is determined to occur, present congestion information to the user.

Description

Technical Field

[0001] The present disclosure relates to a program.

Background Art

[0002] Patent Document 1 discloses an automatic ticket vending machine that, when there is a traffic regulation on a route from a departure station to a destination station, displays a detour route and whether there is a traffic regulation on the detour route.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of Invention

Problems to be Solved by the Invention

[0004] When using a regular commuter pass, users normally do not perform route searches. Even in a situation where congestion occurs on the usual route due to factors such as events, users have no way of knowing the situation, making it difficult to select a route that avoids the congestion.

[0005] An object of the present disclosure is to enable a user to know about congestion on the usual route when using a commuter pass.

Means for Solving the Problems

[0006] A program according to the present disclosure is: A program that outputs ticket information related to the validity of a commuter pass type digital ticket, for which a usage period is preset and which allows free boarding and alighting on public transportation within the usage period, in response to a request, determining whether congestion occurs on the public transportation; and upon determining that the congestion occurs, presenting congestion information related to the congestion to a user. To have the computer perform an action that includes [this]. [Effects of the Invention]

[0007] According to this disclosure, users will be able to find out about congestion on their usual routes when using their commuter passes. [Brief explanation of the drawing]

[0008] [Figure 1] This figure shows the configuration of a system according to some embodiments of this disclosure. [Figure 2] This is a block diagram showing the configuration of a terminal device according to some embodiments of the present disclosure. [Figure 3] This is a flowchart showing the operation of the terminal device according to the first embodiment. [Figure 4] This figure shows an example of the screen of a terminal device according to the first embodiment. [Figure 5] This is a flowchart showing a modified example of the operation of the terminal device according to the first embodiment. [Figure 6] This is a flowchart showing the operation of the terminal device according to the second embodiment. [Figure 7] This figure shows an example of the screen of a terminal device according to the second embodiment. [Figure 8] This is a flowchart showing an example of the operation of the terminal device according to the second embodiment. [Modes for carrying out the invention]

[0009] Several embodiments of this disclosure will be described below with reference to the figures.

[0010] In each figure, identical or corresponding parts are denoted by the same reference numerals. In the description of each embodiment, the description of identical or corresponding parts will be omitted or simplified as appropriate.

[0011] A first embodiment, which is one of the embodiments of this disclosure, will be described.

[0012] With reference to Figure 1, the configuration of the system 10 according to the present embodiment will be described.

[0013] The system 10 according to the present embodiment includes a terminal device 20 of a user 11 and a server device 30. The terminal device 20 is a smartphone in the present embodiment, but may be another type of mobile terminal such as a tablet. The server device 30 may be a cloud server or an on-premises server.

[0014] The terminal device 20 can communicate with the server device 30 via a network 40. The network 40 includes a mobile communication network, the Internet, or both.

[0015] The terminal device 20 outputs ticket information related to the validity of a commuter pass type digital ticket in response to a request. The commuter pass type digital ticket refers to a digital ticket as shown in Figure 4, in which a usage period 52 is preset, and which allows free boarding and alighting of public transport P within the usage period 52. Hereinafter, the commuter pass type digital ticket is simply referred to as "commuter pass". The public transport P is, for example, a bus or a train.

[0016] In the present embodiment, the ticket information is output in response to a request from the user 11, but may be output in response to a request from a reader. The reader is installed at a ticket gate of a station, or at a boarding / alighting gate of a transport facility such as a bus. The reader may authenticate the commuter pass by reading a code such as a two-dimensional code displayed on the screen by the terminal device 20, or may authenticate the commuter pass by receiving an identifier such as a credit card number or an IC (integrated circuit) card number transmitted from the terminal device 20 via short-range wireless communication. As the short-range wireless communication scheme, any scheme such as NFC-A (Near Field Communication Type A), NFC-B (Near Field Communication Type B), or NFC-F (Near Field Communication Type F) may be adopted.

[0017] The terminal device 20 determines whether congestion occurs in the public transportation P. When determining that congestion occurs, the terminal device 20 presents congestion information 55 related to the congestion to the user 11, as shown in FIG. 4. This allows the user 11 to be aware of the congestion on their usual route when using a commuter pass.

[0018] For example, the terminal device 20 runs an application having a route guidance function and a digital ticket function. The terminal device 11 issues an alert regarding the congestion status to the user 11 based on the degree of congestion caused by an event held within the commuter pass coverage area. According to this example, the user 11 can travel while avoiding congestion. When there is an event such as a baseball game or a concert within the commuter pass coverage area, the public transportation P may be congested in certain time periods, but the user 11 can avoid being caught in the congestion. In the case where the commuter pass is a train commuter pass with fixed routes and specified boarding and alighting stations, the user 11 can receive guidance to avoid congestion time periods, and thus can consider traveling while avoiding the congestion time periods.

[0019] When the user 11 performs a route search that covers the congestion time period alerted on the application, the terminal device 20 may propose a detour route within the commuter pass coverage area to avoid the congestion. In the case where the commuter pass is a bus area-limited commuter pass that allows flexible selection of routes and boarding and alighting stops, the user 11 can receive guidance to avoid congestion time periods, and can also receive a proposal for a detour route that avoids the congestion time periods or congested routes. The same applies to the case where the commuter pass is an area-limited commuter pass that allows use of both buses and trains.

[0020] In the example shown in Figure 4, the terminal device 20 requests congestion information 55 within the commuter pass area from the server device 30 for a commuter pass that allows free boarding and alighting on any line and route within the pass area. If there is no congestion information 55 within the pass area, the terminal device 20 displays the regular commuter pass on the screen. If there is congestion information 55, it displays the congestion information 55 along with the commuter pass on the screen. According to this example, congestion information 55 can be supplemented when congestion information 55 is available when user 11 uses their commuter pass.

[0021] The terminal device 20 requests congestion information 55 from the server device 30 as a trigger when it receives an instruction from user 11 to display the commuter pass. Alternatively, the terminal device 20 may request congestion information 55 from the server device 30 as a trigger when it determines, based on location information, that user 11 is approaching a station or bus stop within the range of the commuter pass. Alternatively, the terminal device 20 may request congestion information 55 from the server device 30 during times when user 11 is likely to leave school, work, or home, based on the user's past behavior history.

[0022] In the example shown in Figure 4, if congestion information 55 is available, the terminal device 20 identifies the start and end points of the user's (user's) commuter pass usage. The terminal device 20 searches for the shortest route connecting the identified start and end points, or a route that avoids congestion, and identifies it as a recommended route 56. The terminal device 20 displays the recommended route 56 on the screen along with the congestion information 55. In this example, by identifying the start and end points, the recommended route 56 can be accurately determined.

[0023] If information about user 11's home and workplace or school exists, terminal device 20 identifies the nearest locations to each as the starting and ending points. If such information does not exist, terminal device 20 identifies the locations where user 11 most frequently gets on and off public transport as the starting and ending points, based on user 11's past activity history stored in system 10.

[0024] If congestion information 55 is available, the terminal device 20 may request information from the server device 30 regarding the estimated time when congestion is likely to end, and display the estimated time on the screen. Such an example would improve convenience for the user 11.

[0025] The server device 30 functions as the issuer of transportation tickets, including commuter passes. For example, the server device 30 issues transportation tickets purchased by user 11 on the application and manages them in digital format. If transportation tickets are provided as 2D codes, the server device 30 generates the 2D codes or receives and manages them from external devices such as the transportation operator's server. If the ABT (Account Based Ticketing) method is adopted, the server device 30 manages identification numbers such as credit card numbers or IC card numbers linked to transportation tickets. The server device 30 performs payment processing when transportation tickets are purchased, in cooperation with external payment services. The server device 30 manages coupons or discount information available when purchasing transportation tickets and applies them as needed. The server device 30 tracks the expiration date and usage status of each transportation ticket in real time, such as whether it has been used or not.

[0026] Referring to Figure 2, the configuration of the terminal device 20 according to this embodiment will be described.

[0027] The terminal device 20 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, an output unit 25, and a positioning unit 26.

[0028] The control unit 21 includes at least one processor, at least one programmable circuit, at least one dedicated circuit, or any combination thereof. The processor is a general-purpose processor such as a CPU (central processing unit) or GPU (graphics processing unit), or a dedicated processor specialized for a specific process. The programmable circuit is, for example, an FPGA (field-programmable gate array). The dedicated circuit is, for example, an ASIC (application-specific integrated circuit). The control unit 21 controls each part of the terminal device 20 and executes processes related to the operation of the terminal device 20.

[0029] The storage unit 22 includes at least one semiconductor memory, at least one magnetic memory, at least one optical memory, or any combination thereof. The semiconductor memory is, for example, RAM (random access memory), ROM (read-only memory), SSD (solid-state drive), or flash memory. The magnetic memory is, for example, HDD (hard disk drive). The storage unit 22 functions, for example, as a main memory, auxiliary memory, or cache memory. The storage unit 22 stores information used for the operation of the terminal device 20 and information obtained by the operation of the terminal device 20.

[0030] The communication unit 23 includes at least one communication module. The communication module is, for example, a module compatible with mobile communication standards such as LTE (Long Term Evolution), 4G (4th generation) standards, or 5G (5th generation) standards, or wireless LAN (local area network) standards such as IEEE (Institute of Electrical and Electronics Engineers) 802.11. The communication unit 23 communicates with the server device 30. The communication unit 23 receives information used for the operation of the terminal device 20 and transmits information obtained through the operation of the terminal device 20.

[0031] The input unit 24 includes at least one input device. The input device may be, for example, a physical key, a capacitive key, a pointing device, a touchscreen integrated with a display, a camera, or a microphone. The input unit 24 accepts operations to input information used for the operation of the terminal device 20. Instead of being integrated into the terminal device 20, the input unit 24 may be connected to the terminal device 20 as an external input device. For connection interfaces, interfaces compatible with standards such as USB (Universal Serial Bus), HDMI® (High-Definition Multimedia Interface), or Bluetooth® can be used.

[0032] The output unit 25 includes at least one output device. The output device is, for example, a display such as an LCD (liquid crystal display) or an organic EL (electroluminescent) display, or a speaker. The output unit 25 outputs information obtained by the operation of the terminal device 20. Instead of being provided in the terminal device 20, the output unit 25 may be connected to the terminal device 20 as an external output device. As a connection interface, an interface compatible with standards such as USB, HDMI (registered trademark), or Bluetooth (registered trademark) can be used.

[0033] The positioning unit 26 includes at least one GNSS (global navigation satellite system) receiver. The positioning unit 26 measures the position of the terminal device 20.

[0034] The functions of the terminal device 20 are realized by executing the program according to this embodiment on the processor acting as the control unit 21. In other words, the functions of the terminal device 20 are realized by software. The program causes the computer to perform the operations of the terminal device 20, thereby causing the computer to function as the terminal device 20. That is, the computer functions as the terminal device 20 by performing the operations of the terminal device 20 according to the program. The program can be stored on a non-temporary computer-readable medium. Examples of non-temporary computer-readable media include flash memory, magnetic recording devices, optical discs, magneto-optical recording media, or ROM.

[0035] Some or all of the functions of the terminal device 20 may be implemented by a programmable circuit or a dedicated circuit as the control unit 21. In other words, some or all of the functions of the terminal device 20 may be implemented by hardware.

[0036] The operation of the terminal device 20 according to this embodiment will be explained with reference to Figure 3.

[0037] For example, when an application corresponding to the program according to this embodiment is launched, the step in S101 is executed.

[0038] In S101, the control unit 21 waits until it detects an indication S that the commuter pass will be used by user 11 during a time period T included in the usage period 52. The time period T is a fixed time range from the current time or the current time plus a delay time. The delay time may be set as a fixed time such as 1 minute, or it may be set based on the actual time taken in the past from when indication S was detected until user 11 started using public transport P. The length of the time period T may be set as a fixed length such as 1 hour, or it may be set based on the actual time taken in the past from when user 11 started using public transport P until they finished using it.

[0039] In this embodiment, the indication S includes a request from user 11 for the display of ticket information regarding the validity of the commuter pass. Therefore, the control unit 21 waits until it receives an operation requesting the display of ticket information, such as tapping a commuter pass display button or a pop-up, via an input unit 24 such as a touchscreen.

[0040] If symptom S is detected in S101, the step in S102 is executed.

[0041] In S102, the control unit 21 outputs ticket information. Specifically, the control unit 21 displays the following information via the display, which acts as the output unit 25: the name of the transportation ticket 51, such as "Commuter Pass for All Lines within Area F", the period of use 52, such as "1 month", "2025", and "Until 5.24", the guidance message 53, such as "Tap the screen and show it to the crew when you get off", and the remaining period 54, such as "Valid for 15 days remaining". However, not all of the information exemplified here is required to be displayed on the same screen, and some of it may not be displayed. Congestion information 55 and recommended routes 56 are not displayed at this point.

[0042] In S103, the control unit 21 determines whether or not congestion occurs in the public transport P during the time period T. Specifically, the control unit 21 notifies the server device 30 of the public transport P and the time period T via the communication unit 23 and inquires about the presence or absence of congestion. The server device 30 collects event information regarding events that may cause congestion in the public transport P during the time period T. Based on the collected event information, the server device 30 estimates whether or not congestion occurs. The control unit 21 receives the obtained estimation result from the server device 30 via the communication unit 23. The control unit 21 refers to the received estimation result and determines whether or not congestion occurs. Alternatively, the control unit 21 may independently collect event information and independently estimate whether or not congestion occurs based on the collected event information. The server device 30 or the control unit 21 may calculate the estimated time when congestion will end based on the event information.

[0043] Event information collected includes, for example, the type of event, such as a baseball game or a concert, as well as the date, time, and location. If public transport P is a bus, event information may also include road construction information, street tree pruning information, or other information that may affect bus operations. The procedure for collecting event information can be, for example, to search for one or more large facilities located within the area where the commuter pass is usable, identify events held at those facilities, and search for information on similar events held at those facilities in the past, but other procedures may be used. AI (artificial intelligence) may be used to collect event information. Event information may be collected before S103, such as when purchasing a commuter pass or every night. If event information is collected in advance and stored in the storage of the server device 30 or the memory unit 22, it is possible to quickly determine whether or not congestion will occur.

[0044] As a procedure for estimating whether or not congestion will occur, for example, a procedure can be used to extract congestion information from past events held in the area where the commuter pass is usable, and predict the degree of congestion associated with the current travel of user 11. However, other procedures may also be used. For example, the degree of congestion in time period T can be calculated based on the start or end time of the event. Sources for extracting congestion information include, for example, information on the flow of cars or people, whether paid or free, or information on congestion on buses or trains. Whether or not congestion will occur may be estimated before S103, such as when the commuter pass is purchased or every night. If the estimation results are obtained in advance and stored in the storage of the server device 30 or the memory unit 22, the presence or absence of congestion can be determined even faster.

[0045] When estimating the occurrence of congestion, various external data such as traffic probe data, historical traffic data, weather data, operational data, or demographic data may be used in conjunction with event information. Traffic probe data is data collected from GPS (Global Positioning System) receivers or sensors installed in vehicles and includes information such as vehicle position, speed, or acceleration. Historical traffic data includes congestion patterns found by analyzing past traffic volume or congestion conditions. Weather data includes weather forecasts or meteorological data. Operational data includes train or bus timetables, operating status, or delay information. Demographic data includes regional population density or commuting or schooling patterns. By combining these various types of data, the occurrence of congestion can be accurately estimated using AI or simulation technology.

[0046] If congestion is determined to occur in S103, steps S104 to S106 are executed. If congestion is not determined to occur, the flow terminates.

[0047] In S104, the control unit 21 predicts the points where the use of the commuter pass will begin and end during the time period T as the start point and end point, respectively. Specifically, the control unit 21 obtains personal information about the user 11's home and the user 11's workplace or school from the storage unit 22. Alternatively, the control unit 21 may obtain similar personal information from the server device 30 via the communication unit 23. Based on the obtained personal information, the control unit 21 predicts the start point and end point. For example, the control unit 21 predicts the nearest bus stop or station to the user 11's home as the start point and the nearest bus stop or station to the user 11's workplace or school as the end point. Instead of personal information, the control unit 21 may obtain the user 11's travel history prior to time period T and predict the start point and end point based on the obtained travel history. For example, the control unit 21 may predict the bus stops or stations that the user 11 uses to get on and off with a certain frequency or more from past logs as the start point and end point, respectively. Alternatively, when the control unit 21 receives a search operation performed by the user 11 to search for a route from the departure point to the destination by specifying the departure point and destination, it may predict the start point and end point based on the departure point and destination. For example, when the control unit 21 receives a search operation via an input unit 24 such as a touchscreen, it predicts the nearest bus stop or station to the departure point as the start point and the nearest bus stop or station to the destination as the end point. In such an example, the indication S may include the user 11 searching for a route instead of the user 11 requesting a screen display of ticket information.

[0048] In S105, the control unit 21 searches for a recommended route 56 that uses public transport P to travel between the start and end points predicted in S104, which is either the shortest time or avoids congestion. It is desirable that the recommended route 56 is a route within the area where a commuter pass can be used. The procedure for searching for the recommended route 56 can be the same as that of a known shortest route search or detour route search. The process of searching for the recommended route 56 may be performed by the server device 30 in response to a request from the control unit 21.

[0049] In S106, the control unit 21 presents the recommended route 56 found in S105 to the user 11, along with congestion information 55 regarding congestion that was determined to occur in S103, as shown in Figure 4. Specifically, the control unit 21 displays the transportation ticket name 51, usage period 52, guidance message 53, remaining period 54, congestion information 55, and recommended route 56 on the screen via the display, which acts as the output unit 25, as shown in Figure 4. However, not all of the information exemplified here is required to be displayed on the same screen, and some of it may not be displayed. The congestion information 55 may include, for example, information regarding the event causing the congestion. The control unit 21 may also present the user 11 with the time when the congestion is expected to subside, i.e., the estimated time when the congestion will end, along with the congestion information 55. The control unit 21 may also notify the user 11 of the travel time or fare when the recommended route 56 is applied.

[0050] After S106, the flow ends.

[0051] Instead of step S102 being executed before S103, a step similar to step S102 may be executed after S103. That is, if congestion is determined to occur in S103, a step similar to step S102 may be executed, encompassed within step S106. If it is determined that no congestion will occur, a step similar to step S102 may be executed before the flow terminates.

[0052] Steps S104 and S105 may be omitted. That is, if congestion is determined to occur in S103, in S106 the control unit 21 may present only the congestion information 55 to the user 11 without presenting the recommended route 56.

[0053] Steps S103 and S104 may be performed in reverse order. For example, after the start and end points are predicted in S104, in S103 the control unit 21 may determine whether or not congestion occurs in the public transport P during the time period T and between the start and end points predicted in S104.

[0054] According to this embodiment, when user 11 requests to display their commuter pass, if congestion occurs within the commuter pass area due to factors such as an event, user 11 can be informed of this situation. Therefore, user 11 can make decisions regarding their travel, such as whether to shift the timing of their travel or change their travel route, before using their commuter pass.

[0055] Referring to Figure 5, a modified example of the operation of the terminal device 20 according to this embodiment will be described.

[0056] In this modified example, instead of user 11 requesting to see ticket information on a screen, indicator S includes user 11 approaching a point where they can board or alight from public transport P. Alternatively, indicator S may include the time of day when user 11 is likely to leave school, work, or home, based on user 11's past behavioral history.

[0057] In S201, the control unit 21 recognizes the position measured in real time by the positioning unit 26 as the user 11's current location. The control unit 21 waits until the recognized location is within a certain distance from a point where the user 11 can get on or off public transport P, such as a bus stop or station within the area where the commuter pass can be used, either by referring to map information stored in the memory unit 22 or by using an external GIS (geographic information system). Alternatively, the control unit 21 may estimate the time when the user 11 will leave school, work, or home based on the user 11's past activity history, and wait until the estimated time has passed.

[0058] If symptom S is detected in S201, the step in S202 is executed.

[0059] Steps S202 to S205 are the same as steps S103 to S106 shown in Figure 3, so their explanation is omitted. However, if it is determined in S202 that no congestion will occur, ticket information may be output before the flow ends, similar to step S102 shown in Figure 3.

[0060] Information such as congestion information 55 output by S205 may be presented to the user 11 as a push notification in the form of an in-application message or a pop-up.

[0061] According to this modification, when user 11 approaches a bus stop or station within the commuter pass area, or when user 11 is likely to leave school, work, or home, if congestion occurs within the commuter pass area due to an event or other factor, user 11 can be aware of this situation. As a result, user 11 can make decisions regarding their travel, such as whether to shift their travel timing or change their travel route, without having to perform any action to display their commuter pass.

[0062] A second embodiment, which is another embodiment of the present disclosure, will be described.

[0063] The configuration of the system 10 according to this embodiment is the same as that of the system 10 according to the first embodiment, which was described with reference to Figure 1, so its description is omitted. The configuration of the terminal device 20 according to this embodiment is also the same as that of the terminal device 20 according to the first embodiment, which was described with reference to Figure 2, so its description is omitted.

[0064] In this embodiment, the commuter pass is a digital ticket, as shown in Figure 7, with a pre-set usage section 57, allowing free boarding and alighting of public transportation P within the usage period 52 and within the usage section 57. The terminal device 20 determines whether or not congestion occurs on public transportation P, similar to the first embodiment. If the terminal device 20 determines that congestion occurs, it presents congestion information 55 to the user 11, as shown in Figure 7. As a result, the user 11 can learn about congestion on their usual route when using the commuter pass.

[0065] In the example shown in Figure 7, the terminal device 20 requests congestion information 55 within the commuter pass route from the server device 30 for commuter passes in which the start and end points of use and the commuter pass route are predetermined. If there is no congestion information 55 within the commuter pass route, the terminal device 20 displays the regular commuter pass on the screen, and if there is congestion information 55, it displays the congestion information 55 on the screen along with the commuter pass. According to this example, when user 11 uses a commuter pass with a fixed start and end point, congestion information 55 can be obtained if it is available.

[0066] In the example shown in Figure 7, if congestion information 55 is available, the terminal device 20 searches for an alternative route 58 that connects the starting point and the ending point, separate from the regular pass route. If an alternative route 58 is available, the terminal device 20 displays the alternative route 58 on the screen along with the congestion information 55. According to this example, the user 11 can receive suggestions for alternative routes even when using a regular pass with fixed starting and ending points.

[0067] The terminal device 20 may search for discounted transportation tickets available on the alternative route 58, and if discounted transportation tickets are available, it may display information about the discounted transportation tickets on the screen, or it may prompt the user 11 to purchase discounted transportation tickets on the screen. In such an example, the user 11 can use the alternative route 58 more conveniently by knowing that transportation tickets are available on the alternative route 58.

[0068] The operation of the terminal device 20 according to this embodiment will be explained with reference to Figure 6.

[0069] For example, when an application corresponding to the program according to this embodiment is launched, the step in S301 is executed.

[0070] Step S301 is the same as step S101 shown in Figure 3, so its explanation will be omitted.

[0071] If symptom S is detected in S301, the step in S302 is executed.

[0072] In S302, the control unit 21 outputs ticket information. Specifically, the control unit 21 displays the transportation ticket name 51, usage period 52, guidance message 53, and remaining period 54, as well as the usage section 57 such as "bus stop Y to bus stop Z," on the screen via the display, which acts as the output unit 25, as shown in Figure 7. However, not all of the information exemplified here is required to be displayed on the same screen, and some of it may not be displayed. Congestion information 55 and alternative routes 58 are not displayed at this point.

[0073] In S303, the control unit 21 determines whether or not congestion occurs in public transport P during the time period T and the travel section 57. Specifically, the control unit 21 notifies the server device 30 via the communication unit 23 of public transport P, time period T, and travel section 57, and inquires about the presence or absence of congestion. The server device 30 collects event information regarding events that may cause congestion in public transport P during the time period T and the travel section 57. Based on the collected event information, the server device 30 estimates whether or not congestion occurs. The control unit 21 receives the obtained estimation result from the server device 30 via the communication unit 23. The control unit 21 refers to the received estimation result and determines whether or not congestion occurs. Alternatively, the control unit 21 may independently collect event information and independently estimate whether or not congestion occurs based on the collected event information. The server device 30 or the control unit 21 may calculate the estimated time of end of congestion based on the event information.

[0074] The event information collected is the same as that of the first embodiment. The procedure for collecting event information can be, for example, to search for one or more large facilities located near bus stops or stations on routes where commuter passes can be used, to identify events held at those large facilities, and to search for information on similar events held at those large facilities in the past, but other procedures may be used. AI may be used to collect event information. Event information may be collected before S303, such as when purchasing a commuter pass or every night. If event information is collected in advance and stored in the storage of the server device 30 or the memory unit 22, it is possible to quickly determine whether or not congestion is occurring.

[0075] As a procedure for estimating whether or not congestion will occur, for example, one could extract congestion data from past events held on routes where the commuter pass is usable, and predict the degree of congestion associated with the current user 11's travel. However, other procedures may also be used. For example, the degree of congestion in the time period T and travel section 57 can be calculated based on the start or end time of the event. Sources for extracting congestion data include, for example, information on the flow of cars or people, whether paid or free, or information on bus or train congestion. Whether or not congestion will occur may be estimated before S303, such as at the time of commuter pass purchase or every night. If the estimation results are obtained in advance and stored in the storage of the server device 30 or the memory unit 22, the presence or absence of congestion can be determined even faster.

[0076] When estimating whether or not congestion will occur, various external data similar to those in the first embodiment may be used in conjunction with event information.

[0077] If congestion is detected in S303, the step in S304 is executed. If congestion is not detected, the flow terminates.

[0078] In S304, the control unit 21 searches for an alternative route 58 that uses public transport P or another public transport to travel between the start and end points of the travel section 57, and that is at least partially different from the travel section 57. Specifically, the control unit 21 searches for alternative routes connecting the start and end points as detour route candidates in order of shortest route, either by referring to map information stored in the memory unit 22 or by using an external GIS. The control unit 21 determines whether or not congestion occurs during the time period T and in the detour route candidates, using the same procedure as in step S303. If the control unit 21 determines that no congestion occurs, it selects the detour route candidate as the alternative route 58. The control unit 21 may repeat the search for detour route candidates until it determines that no congestion occurs, or it may determine that no alternative route 58 exists if the number of searches for detour route candidates reaches an upper limit of the number of attempts, such as 5, without determining that no congestion occurs. Alternatively, the procedure for searching for an alternative route 58 may be the same as a known detour route search procedure. The process of searching for an alternative route 58 may be performed by the server device 30 in response to a request from the control unit 21.

[0079] If an alternative route 58 exists in S304, the steps in S305 are executed. If an alternative route 58 does not exist, the steps in S306 are executed.

[0080] In S305, the control unit 21 presents the alternative route 58 found in S304 to the user 11, along with congestion information 55 regarding congestion determined to occur in S303, as shown in Figure 7. Specifically, the control unit 21 displays the transportation ticket name 51, usage period 52, guidance message 53, remaining period 54, congestion information 55, usage section 57, and alternative route 58 on the screen via the display, which acts as the output unit 25, as shown in Figure 7. However, not all of the information exemplified here is required to be displayed on the same screen, and some of it may not be displayed. The congestion information 55 may include, for example, information about the event causing the congestion. The control unit 21 may also present the user 11 with the time when the congestion is expected to subside, i.e., the estimated time when the congestion will end, along with the congestion information 55. The control unit 21 may also notify the user 11 of the travel time or fare when the alternative route 58 is applied. The control unit 21 may further present the user 11 with information about digital tickets available for the alternative route 58. Information regarding digital tickets available for alternative route 58 may include the travel time or cost associated with using such digital tickets.

[0081] After S305, the flow ends.

[0082] In S306, the control unit 21 presents the user 11 with congestion information 55 related to the congestion that was determined to occur in S303, as shown in Figure 7. Specifically, the control unit 21 displays the transportation ticket name 51, usage period 52, guidance message 53, remaining period 54, congestion information 55, and usage section 57 on the screen via the display, which acts as the output unit 25, as shown in Figure 7. However, not all of the information exemplified here is required to be displayed on the same screen, and some of it may not be displayed. The alternative route 58 is not displayed because it does not exist. The congestion information 55 may include, for example, information about the event causing the congestion. The control unit 21 may also present the user 11 with the time when the congestion is expected to be resolved, i.e., the expected end time of congestion, along with the congestion information 55.

[0083] After S306, the flow ends.

[0084] Instead of the S302 step being executed before S303, a step similar to the S302 step may be executed after S303. That is, if congestion is determined to occur in S303, a step similar to the S302 step may be executed, encompassed within the S305 or S306 step. If it is determined that no congestion will occur, a step similar to the S302 step may be executed before the flow terminates.

[0085] Steps S304 and S305 may be omitted. That is, if congestion is determined to occur in S303, in S306 the control unit 21 may present only the congestion information 55 to the user 11 without presenting an alternative route 58.

[0086] According to this embodiment, when user 11 requests to display their commuter pass, if congestion occurs on the commuter pass route due to factors such as an event, user 11 can be informed of this situation. Therefore, user 11 can make decisions regarding their travel, such as whether to shift the timing of their travel or change their travel route, before using their commuter pass.

[0087] Referring to Figure 8, a modified example of the operation of the terminal device 20 according to this embodiment will be described.

[0088] In this modified example, instead of user 11 requesting to see ticket information on a screen, indicator S includes user 11 approaching a point where they can board or alight from public transport P. Alternatively, indicator S may include the time of day when user 11 is likely to leave school, work, or home, based on user 11's past behavioral history.

[0089] In S401, the control unit 21 recognizes the position measured in real time by the positioning unit 26 as the user 11's current position. The control unit 21 waits until the recognized position is within a certain distance from a point where the user 11 can get on or off public transport P, such as a bus stop or station on a route where a commuter pass can be used, either by referring to map information stored in the memory unit 22 or by using an external GIS. Alternatively, the control unit 21 may estimate the time when the user 11 will leave school, work, or home based on the user 11's past activity history, and wait until the estimated time has passed.

[0090] If symptom S is detected in S401, the step in S402 is executed.

[0091] Steps S402 to S405 are the same as steps S303 to S306 shown in Figure 6, so their explanation is omitted. However, if it is determined in S402 that no congestion will occur, ticket information may be output before the flow ends, similar to step S302 shown in Figure 6.

[0092] Information such as congestion information 55 output in S404 or S405 may be presented to the user 11 as a push notification in the form of an in-application message or a pop-up.

[0093] According to this modification, when user 11 approaches a bus stop or station on their commuter pass route, or when user 11 is likely to leave school, work, or home, if congestion occurs on the commuter pass route due to an event or other factor, user 11 can be aware of this situation. As a result, user 11 can make decisions regarding their travel, such as whether to shift their travel timing or change their travel route, without having to perform any action to display their commuter pass.

[0094] This disclosure is not limited to the embodiments described above. For example, two or more blocks described in the block diagram may be combined, or one block may be divided. Instead of executing two or more steps described in the flowchart in chronological order as described, they may be executed in parallel or in a different order, depending on the processing capacity of the device performing each step, or as necessary. Other modifications are possible without departing from the spirit of this disclosure. [Explanation of Symbols]

[0095] 10 Systems 11 users 20 Terminal devices 21 Control Unit 22 Memory section 23 Communications Department 24 Input section 25 Output section 26 Positioning Unit 30 Server Devices 40 Networks 51 Transportation ticket name 52. Usage period 53 Guidance Message 54 Remaining period 55 Congestion Information 56 Recommended Route 57 Usage Sections 58 Alternative Route

Claims

1. A program that outputs ticket information regarding the validity of a pass-type digital ticket, which has a predetermined usage period and allows free boarding and alighting of public transportation within that period, upon request. To determine whether or not congestion occurs in the aforementioned public transportation, If it is determined that the aforementioned congestion occurs, the system will present the user with information regarding the congestion. A program that causes a computer to perform an action that includes [a specific action].

2. The aforementioned congestion refers to the congestion of the public transportation during the time period included in the aforementioned usage period. The program according to claim 1, wherein the operation includes determining whether or not congestion occurs when it detects an indication that the digital ticket will be used by the user during the time period.

3. The aforementioned operation is, If it is determined that the aforementioned congestion will occur, the points where the use of the digital ticket will begin and end during the aforementioned time period will be predicted as the start point and end point, respectively. Using the aforementioned public transportation, the system searches for the shortest route or a route that avoids congestion between the predicted starting point and the predicted ending point, and recommends this route as the best route. The recommended route is presented to the user along with the congestion information. The program according to claim 2, including the program described in claim 2.

4. The aforementioned operation is, To obtain personal information concerning the user's home address and the user's workplace or school, Based on the acquired personal information, predict the start point and the end point. The program according to claim 3, including the program described in claim 3.

5. The aforementioned operation is, Obtaining the user's travel history prior to the aforementioned time period, Based on the acquired movement history, predict the start point and the end point. The program according to claim 3, including the program described in claim 3.

6. The program according to claim 3, wherein the operation includes, upon receiving a search operation performed by the user to search for a route from the departure point to the destination by specifying a departure point and a destination, predicting the starting point and the ending point, respectively, based on the departure point and the destination.

7. The program according to claim 2, wherein the indication includes, as a request, the user requesting the display of the ticket information on a screen.

8. The program according to claim 2, wherein the indication includes the user approaching a point where they can board or alight from the public transport.

9. The aforementioned digital ticket is a digital ticket in which the usage section is predetermined, and which allows free boarding and alighting of the aforementioned public transportation within the usage period and within the aforementioned usage section. The aforementioned congestion refers to congestion on the aforementioned public transportation within the aforementioned usage section. The aforementioned operation is, If it is determined that the aforementioned congestion will occur, the system will search for an alternative route that uses the aforementioned public transport or another public transport to travel between the start and end points of the aforementioned travel section, and that is at least partially different from the aforementioned travel section. If an alternative route exists, the alternative route will be presented to the user along with the congestion information. The program according to claim 1, including the program described in claim 1.

10. The program according to claim 9, wherein the operation includes, if an alternative route exists, further presenting the user with information regarding a digital ticket available on the alternative route.

11. The program according to claim 1, wherein, upon determining that congestion has occurred, the program presents to the user, along with the congestion information, the time at which the congestion is expected to be resolved.

Images