Mobile devices

Abstract

To provide a portable terminal capable of preventing a user who visits an event site by public transportation, from missing the last service.SOLUTION: A portable terminal 100 includes a processor 101 (a notification device) that performs a last service notification (a first notification) for prompting a user to get on a public transportation 800 of a last service for the user to return home. The processor 101 performs the last service notification when an event 910 is continuing at a predetermined time before departure time at which the last service departs.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to mobile terminals. [Background technology]

[0002] Japanese Patent Laid-Open Publication No. 2016-114430 (Patent Document 1) discloses an information processing system that determines whether or not final route information needs to be output when route information is acquired based on route search conditions. [Prior art documents] [Patent documents]

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

[0004] A user who is attending an event such as a concert needs to pay attention to the time so as not to miss the last train. However, the user may become so engrossed in the event that they forget about the last train. In this case, the user will miss the last train and have difficulty getting home.

[0005] The present disclosure has been made to solve the above problem, and its purpose is to provide a mobile terminal that can prevent users who are arriving at an event venue by public transportation from missing the last flight. [Means for solving the problem]

[0006] According to one aspect of the present disclosure, a mobile terminal is carried by a user who has arrived at an event venue by public transport, and includes a notification device that issues a first notification to urge the user to board the last public transport to return home. The notification device issues the first notification if the user remains at the event venue a predetermined time before the departure time of the last public transport.

[0007] In a mobile device according to one aspect of the present disclosure, as described above, if a user remains at an event venue a predetermined time before the departure time of the last flight, a first notification is issued to prompt the user to board the last flight. This makes it possible to remind (make aware of) the user who remains at the event venue of the departure time of the last flight. As a result, it is possible to prompt the user to leave the event venue. This makes it possible to prevent the user from missing the last flight.

[0008] In the mobile terminal according to the above aspect, the notification device preferably issues the first notification when an event is ongoing a predetermined time before the departure time. With this configuration, even if the user is engrossed in an event a predetermined time before the departure time of the last flight, the user can be reminded of the departure time of the last flight.

[0009] In this case, the notification device preferably issues the first notification when the time before the departure time by a predetermined amount is before the scheduled end time of the event. With this configuration, the first notification can be easily issued based on the scheduled end time of the event.

[0010] In the mobile terminal according to the above aspect, the notification device preferably, when issuing the first notification, also issues a second notification to urge the user to board a flight earlier than the last flight. This configuration can increase the number of users leaving the event venue to board not only the last flight but also a flight earlier than the last flight. As a result, it is possible to easily spread out the times at which multiple users leave the event venue.

[0011] In the mobile terminal according to the above aspect, the events preferably include a first event held at a first event venue and a second event held at a second event venue. The predetermined time includes a first predetermined time corresponding to the first event and a second predetermined time corresponding to the second event. The notification device issues the first notification when the user remains at the first event venue the first predetermined time before the departure time, and issues the first notification when the user remains at the second event venue the second predetermined time before the departure time. This configuration makes it possible to appropriately adjust the timing of the first notification depending on the type of event. As a result, it is possible to prevent the user from missing the last flight regardless of the type of event.

[0012] According to the present disclosure, it is possible to prevent users who are coming to an event venue by public transportation from missing the last train. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a notification system according to an embodiment. [Figure 2] FIG. 10 illustrates a mobile device displaying a last flight notification according to one embodiment. [Figure 3] FIG. 10 is a diagram showing the relationship between the departure time of the last flight corresponding to each event and the notification time of the last flight notification according to one embodiment. [Figure 4] FIG. 10 is a sequence diagram illustrating control of a notification system according to an embodiment. [Figure 5] FIG. 10 is a diagram illustrating a display screen of an application used in a notification system according to one embodiment. [Figure 6] FIG. 10 is a sequence diagram illustrating control of a notification system according to a modified example of an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals, and description thereof will not be repeated.

[0015] <Notification system configuration> 1 is a diagram schematically illustrating the overall configuration of a notification system 1 according to an embodiment of the present disclosure. The notification system 1 includes a mobile terminal 100 and a server 200.

[0016] <User terminal configuration> The mobile terminal 100 is a terminal carried by a user, and is, for example, a smartphone, a tablet, or a smartwatch.

[0017] The mobile terminal 100 includes, for example, a processor 101, a memory 102, a storage 103, a communication module 104, a GPS (Global Positioning System) module 105, and a display 106. The processor 101 is an example of a "notification device" of the present disclosure.

[0018] The processor 101 is a microprocessor such as a CPU or an MPU. The memory 102 is a volatile memory such as a RAM. The processor 101 loads system programs and control programs read from the storage 103 into the memory 102 and executes them to realize various processes.

[0019] The storage 103 is a rewritable nonvolatile memory such as a flash memory, and stores the above-mentioned system program including the OS and the above-mentioned control program including computer-readable code necessary for control calculations.

[0020] The communication module 104 includes a communication interface that complies with a wireless communication standard. The wireless communication standard may be LTE (Long Term Evolution) such as 4G or 5G, or a wireless LAN (Local Area Network) such as Wi-Fi (Wireless Fidelity), or both. The communication module 104 is configured to enable bidirectional communication with the server 200.

[0021] GPS module 105 acquires information (GPS information) indicating the current location of mobile terminal 100 based on signals from multiple artificial satellites, and outputs the GPS information to processor 101. Note that mobile terminal 100 may include a beacon receiver (not shown) instead of or in addition to GPS module 105.

[0022] The display 106 is a mobile display such as an organic electroluminescence (EL) display or a liquid crystal display. The display 106 is configured to display various information in accordance with control commands from the processor 101. In this example, the display 106 is a display with a touch panel that can accept input operations from the user.

[0023] <Server configuration> The server 200 includes, for example, a processor 201, a memory 202, a communication unit 203, and a storage 204.

[0024] The processor 201 is a microprocessor such as a CPU (Central Processing Unit) or an MPU (Micro-Processing Unit). The memory 202 is a volatile memory such as a RAM (Random Access Memory). The processor 201 loads system programs and control programs read from the storage 204 into the memory 202 and executes them to realize various processes.

[0025] The communication unit 203 includes a communication interface with a network such as the Internet. The communication unit 203 is configured to enable two-way communication with an external device (such as the mobile terminal 100) of the server 200. The communication unit 203 receives, for example, location information of the mobile terminal 100 based on the GPS module 105 or the like.

[0026] The storage 204 is a rewritable nonvolatile memory such as a hard disk drive (HDD), a solid state drive (SSD), a flash memory, etc. The storage 204 stores system programs including an operating system (OS).

[0027] In this embodiment, the mobile terminal 100 is a terminal carried by a user who is attending an event venue 900 where an event 910 is being held.

[0028] Here, a user watching an event at an event venue may become so engrossed in the event that they forget about the last train (hereinafter simply referred to as the "last train") they can take to get home (for example, a train or bus). In this case, the user will miss the last train and have difficulty getting home.

[0029] Therefore, in this embodiment, the processor 101 issues a notification (hereinafter referred to as "last flight notification") to prompt the user to board the last flight. Specifically, the processor 101 issues the last flight notification when the event 910 is ongoing a predetermined time before the departure time of the last flight (hereinafter referred to as "last departure time").

[0030] A specific example will be shown with reference to Figure 2. Assume that the last departure time is, for example, 12:03. Also, assume that the predetermined time is 30 minutes. In this case, if event 910 is ongoing at 11:33, processor 101 performs control to display a last flight notification on display 106. Specifically, a message saying "30 minutes left until the last flight" is displayed on display 106.

[0031] In the above example, when the event 910 is ongoing at 11:33, the processor 101 notifies the user of the last train and also notifies the user of the train before the last train (hereinafter referred to as the "last train notification"). Specifically, the processor 101 displays a message saying "20 minutes before the train before the last train" on the screen of the display 106 where the last train notification is displayed. For example, the last train notification is displayed lower than the last train notification. The last train notification may also be displayed smaller than the last train notification.

[0032] Also, depending on the type of event 910, some events have a scheduled end time set. In this case, the processor 101 issues a last flight notification if the time a predetermined time before the last departure time is earlier than the scheduled end time. Note that in this case, the last flight notification is issued a predetermined time before the last departure time.

[0033] The predetermined time is set individually for each event 910. Fig. 3 is a diagram showing the relationship between the latest departure time of users attending each event and the time of the last flight notification.

[0034] For example, users A to C who are attending a live concert venue where live concert X is being held are notified of the last flight 30 minutes before the final departure time. That is, processor 101 notifies the last flight 30 minutes before the final departure time if the live concert is still ongoing. Note that the above 30 minutes is an example of the "first predetermined time" in the present disclosure. The live concert venue and live concert X are examples of the "first event venue" and the "first event" in the present disclosure, respectively.

[0035] Furthermore, for users D to F who are visiting a baseball stadium where a professional baseball game is being held, a notification of the last flight is sent, for example, one hour before the final departure time. That is, processor 101 sends the last flight notification if a professional baseball game is still ongoing one hour before the final departure time. Note that the one hour mentioned above is an example of a "second predetermined time" in the present disclosure. The baseball stadium and the professional baseball game are examples of a "second event venue" and a "second event" in the present disclosure, respectively.

[0036] The predetermined time may be set for each type of event 910 (sports, concerts, etc.). The predetermined time may be set based on the location of the event venue where the event 910 is held (for example, the distance from the nearest station). The greater the distance between the event venue and the nearest station, the longer the predetermined time may be set. The predetermined time may be set based on the number of visitors (or the expected number of visitors) who will attend the event 910. The greater the number of visitors, the longer the predetermined time may be set. This makes it possible to appropriately set the predetermined time even if the time required to get from the event venue 900 to the transportation 800 or the timing for deciding to end the event 910 differs for each event 910.

[0037] <Notification system sequence> The above-mentioned notification of the last flight is performed at the mobile terminal 100 based on a command signal transmitted from the server 200 to the mobile terminal 100. A specific sequence between the mobile terminal 100 and the server 200 (the sequence of the notification system 1) will be described with reference to FIG.

[0038] In step S1, processor 101 of mobile terminal 100 (hereinafter referred to simply as "mobile terminal 100") accepts input of information about event 910 and information about the user's destination (home, lodging, etc.) in a predetermined application. Fig. 5 is an example of a display screen 106a of the application.

[0039] As shown in FIG. 5, the display screen 106a includes an input field 106b for inputting an event 910. The display screen 106a also includes an input field 106c for inputting the nearest station (including a bus stop) to the destination. Each of the input fields 106b and 106c is, for example, a pull-down input field. Note that instead of the nearest station to the destination, the name of the accommodation or the address of the user's home may be input. The mobile terminal 100 may acquire information about the event 910 when the user reserves a digital ticket for the event. The mobile terminal 100 may acquire information about the destination to return home when the user reserves a place to stay.

[0040] 4 again, in step S2, processor 201 of server 200 (hereinafter simply referred to as "server 200") calculates the final departure time based on the information about event 910 and the information about the destination of return home input by the user in step S1. Specifically, server 200 calculates the final departure time based on the location of event venue 900 where event 910 is held and the location of the destination of return home input in step S1.

[0041] In step S3, the server 200 calculates the time to issue the last flight notification based on the last departure time calculated in step S2. Specifically, the time to issue the last flight notification (hereinafter referred to as "notification time") is calculated based on the last departure time and information about the event 910 in which the user is participating. For example, if the user is participating in Live X, the notification time is 30 minutes before the last departure time.

[0042] Note that information about the predetermined time corresponding to the type of event 910 (for example, a table showing the relationship between the event 910 and the predetermined time) is stored in the storage 204 of the server 200. The server 200 calculates the notification time based on the information.

[0043] In step S4, the server 200 determines whether or not a scheduled end time has been set for the event 910 in which the user is participating. The server 200 acquires information about the scheduled end time of the event 910 via the Internet or the like through the communication unit 203. If a scheduled end time has been set (Yes in S4), the process proceeds to step S5. If a scheduled end time has not been set (No in S4), the process proceeds to step S6.

[0044] In step S5, server 200 determines whether the notification time calculated in step S3 is before the scheduled end time of event 910 acquired in step S4. If the notification time is before the scheduled end time of event 910 (Yes in S5), the process proceeds to step S8. If the notification time is after the scheduled end time of event 910 (No in S5), the process ends.

[0045] In step S6, server 200 determines whether the current time has reached the notification time. If the current time has reached the notification time (Yes in S6), the process proceeds to step S7. If the current time has not reached the notification time (No in S6), the process of step S6 is repeated.

[0046] In step S7, the server 200 determines whether the event 910 is ongoing at the time of notification. For example, the server 200 checks whether the event 910 is ongoing at the time of notification via the Internet or the like through the communication unit 203. If the event 910 is ongoing at the time of notification, the process proceeds to step S8. If the event 910 has ended at the time of notification, the process ends.

[0047] In step S8, the server 200 transmits a command (signal) to the mobile terminal 100 to notify the mobile terminal 100 of the last flight.

[0048] In step S9, the mobile terminal 100 displays the last flight notification on the display 106. Then, the process ends. Note that the server 200 may send a command to the mobile terminal 100 before the notification time to cause the mobile terminal 100 to notify the last flight at the notification time. This also allows the mobile terminal 100 to notify the last flight when the notification time arrives.

[0049] As described above, in this embodiment, the processor 101 of the mobile terminal 100 notifies the user of the last flight if the event 910 is ongoing a predetermined time before the departure time of the last flight. This allows the user to know (remember) the time of the last flight before the event ends. Furthermore, since each user uses a different means of transportation or has a different destination, the time of the last flight varies for each user, so the times at which users leave the event venue can be spread out. Furthermore, since the last flight notification is displayed a predetermined time before the time of the last flight, the user can be given time to consider when to end the event 910. Furthermore, by encouraging the user to return home relatively earlier than the time of the last flight, it is possible to prevent the user from getting caught in a congestion caused by other users returning home by the last flight.

[0050] In the above embodiment, an example was shown in which the last flight notification is issued when the event 910 is ongoing a predetermined time before the time of the last flight, but the present disclosure is not limited to this. For example, the last flight notification may be issued when it is determined that the user remains at the event venue 900 a predetermined time before the time of the last flight. A specific example will be described with reference to FIG. 6.

[0051] The modified example shown in Fig. 6 differs from the above embodiment in that step S17 is performed instead of step S7 in the sequence of the above embodiment (see Fig. 4). In step S17, server 200 determines whether the user's location based on information from GPS module 105 of mobile terminal 100 is within event venue 900 at the notification time calculated in step S3. If the user's location is within event venue 900 (if it is determined that the user remains at event venue 900) (Yes in S17), the process proceeds to step S8. If the user's location is outside event venue 900 (if it is determined that the user has left event venue 900) (No in S17), the process ends.

[0052] This allows the user to be notified (reminded) of the time of the last flight even after the event 910 has ended.

[0053] In the above embodiment, an example is shown in which a determination is made as to whether the event 910 is ongoing a predetermined time before the final departure time, and a determination is made as to whether the time before the predetermined time before the final departure time is before the scheduled end time of the event 910. However, the present disclosure is not limited to this. For example, only one of the above two determinations may be made.

[0054] In the above embodiment, an example was shown in which the departure time of the flight before the last flight was notified together with the notification of the last flight, but the present disclosure is not limited to this. Notification of a flight before the flight before the last flight may also be provided.

[0055] In the above embodiment, an example was shown in which the predetermined time period differs for each event, but the present disclosure is not limited to this. The predetermined time period may be constant between events.

[0056] In the above embodiment, an example has been described in which the last flight notification is performed based on information about the event 910 and information about the home destination input in an application on the mobile terminal 100, but the present disclosure is not limited to this. For example, the event 910 in which the user is participating may be automatically determined by the server 200 based on the user's GPS information, etc. Alternatively, the last departure time may be calculated based on the user's home address, etc., registered in advance in the server 200. Alternatively, information about the event 910 and the home destination may be acquired and the last departure time may be calculated based on the history of route searches performed by the user to arrive at the event venue 900.

[0057] In the above embodiment, an example has been shown in which the last flight notification is displayed on the mobile terminal 100 based on a command from the server 200, but the present disclosure is not limited to this. In the above embodiment, the processing performed by the server 200 (the processing of S2 to S7 in FIG. 4) may be performed by the mobile terminal 100.

[0058] In the above embodiment, an example was shown in which the last flight notification was displayed on the display 106 of the mobile terminal 100, but the present disclosure is not limited to this. For example, the last flight notification may be performed using vibration and / or sound of the mobile terminal 100.

[0059] In the above embodiment, an example was shown in which the last flight notification and the one-flight-before-flight notification were displayed on the same screen, but the present disclosure is not limited to this. The last flight notification and the one-flight-before-flight notification may be displayed at different times. The last flight notification and the one-flight-before-flight notification may be displayed consecutively or with a predetermined time interval between them.

[0060] The configurations (processing) of the above-described embodiment and the above-described modified examples may be combined with each other. For example, if the event 910 is ongoing a predetermined time before the final departure time and the user remains at the event venue 900 a predetermined time before the final departure time, the last flight notification may be sent.

[0061] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is defined by the claims, not by the description of the above embodiments, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0062] 100 Mobile terminal, 101 Processor (notification device), 800 Mobile terminal, 900 Event venue, 910 Event.

Claims

1. A mobile terminal carried by a user who is visiting an event venue where an event is being held by public transport, a notification unit that issues a first notification to prompt the user to board the last service of the transportation facility to return home; The notification unit of the mobile terminal sends the first notification when the user remains at the event venue a predetermined time before the departure time of the last flight and the event is ongoing the predetermined time before the departure time.

2. The mobile terminal according to claim 1 , wherein the notification unit issues the first notification when the time before the predetermined time before the departure time is before a scheduled end time of the event.

3. The mobile terminal according to claim 1 , wherein the notification unit, when issuing the first notification, also issues a second notification for urging the user to board a flight earlier than the last flight.

4. the events include a first event held at a first event venue and a second event held at a second event venue; the predetermined time includes a first predetermined time corresponding to the first event and a second predetermined time corresponding to the second event; The notification unit When the user remains at the first event venue for the first predetermined time before the departure time, the first notification is sent; The mobile terminal according to claim 1 , wherein the first notification is made when the user remains at the second event venue for the second predetermined time before the departure time.

Images