JP7374678B2 - notification system - Google Patents

Description

The present invention relates to a notification system that notifies users of a facility that has a managed area that can be entered by using a ticket.

When using a transportation facility using an IC card, ticket, or other voucher, the transportation user freely selects a travel route according to his/her intention. Techniques have been proposed for effectively providing services to mobile users (for example, see Patent Document 1).

The technology described in Patent Document 1 is a technology that provides content linkage information to railway users. This technology calculates the user's stay time in the station based on the boarding time and alighting time of the identified confirmed travel route pattern and the standard travel time. This technology then identifies content where part of the calculated stay time in the station premises overlaps at least part of the display time of display history information stored in the content display history database, and Deliver related information to users' devices.

Japanese Patent Application Publication No. 2009-187329

However, although the technique described in Patent Document 1 allows the provider to efficiently provide video content to the user, it does not take into account whether the provided video content is what the user wants. In recent years, amidst the abundance of advertising information, consideration has been given to providing users with the exact information they are looking for. It is not easy to provide. Furthermore, these issues are common not only to users of public transportation, but also to users of facilities that have managed areas that users can enter and exit by using tickets, such as theme parks where users can move freely.

The present invention was made in view of the above-mentioned circumstances, and its purpose is to enable notification of information that meets the needs of users of a facility that has a managed area that allows entry and exit by using a usage ticket. The goal is to provide a notification system.

A notification system that solves the above problem includes a control unit that is configured to be able to communicate with an identification number acquisition device that acquires an identification number that is individually set for each ticket for the facility when entering and exiting a managed area within the facility. The communication system includes: an identification number registration unit in which user information regarding the user of the identification number is registered in association with the identification number; and services available to the user at the facility. and a detection unit that detects service information including at least one of the services used by the user in the facility, and when a notification condition based on the acquisition of the identification number by the identification number acquisition device is satisfied, the user information and a notification unit that notifies the service information to notification destinations included in the service information.

According to the present invention, it is possible to notify information that meets the needs of users of a facility that has a management area that allows entry and exit by using a usage ticket.

FIG. 1 is a block diagram showing a schematic configuration of a first embodiment of a notification system. (a) A diagram showing a display example of a user menu in the first embodiment, and (b) a diagram showing a display example of a user information input screen in the first embodiment. FIG. 3 is a diagram showing a display example of an administrator menu in the first embodiment. FIG. 2 is a diagram showing information used for the notification service in the first embodiment, in which (a) is a diagram showing an example of the service set at each station and its notification time, and (b) is a diagram showing an example of the service set at each station and its notification time, and (b) is a diagram showing the information used for the notification service in the first embodiment. The figure which shows an example of a service, (c) is a figure which shows an example of the notification message for text notifications, and (d) is a figure which shows an example of the notification message for voice notifications. FIG. 3 is a diagram showing information used for the notification service in the first embodiment, in which (a) is a diagram showing an example of user information associated with IDi, and (b) is a rental locker, which is one of the services. (c) is a diagram showing an example of reservation purchase information; (d) is a diagram showing an example of ticket gate usage history. FIG. 3 is a diagram showing an example of notification of service information based on usage prediction when the boarding section and the limited express section are the same in the first embodiment, and (a) is a diagram showing an example when the limited express ticket is a non-reserved seat limited express ticket. , (b) is a diagram showing an example in which the limited express ticket is a reserved seat limited express ticket, (c) is a diagram showing another example in which the limited express ticket is a reserved seat limited express ticket, and (d) is a diagram showing an example in which the limited express ticket is a reserved seat limited express ticket. The figure which shows an example when arrival time is shifted. FIG. 3 is a diagram showing an example of notification of service information based on usage prediction when the boarding section and the limited express section are different in the first embodiment, and (a) is a diagram showing an example when the limited express ticket is a non-reserved seat limited express ticket. , (b) is a diagram showing an example in which the limited express ticket is a reserved seat limited express ticket. FIG. 3 is a diagram showing an example where a part of the riding section is a regular section in the first embodiment. FIG. 2 is a block diagram showing a schematic configuration of a second embodiment of a notification system. In the second embodiment, (a) is a diagram showing a display example of the administrator menu, (b) is a diagram showing an example of notification setting conditions, (c) is a diagram showing an example of notification determination time, and (d) is a diagram showing an example of notification setting conditions. FIG. 7(e) is a diagram illustrating an example of an email notification message when notifying service information; FIG. In the second embodiment, (a) is a diagram showing locker usage information associated with IDi, (b) is a diagram showing an example of free passage time, and (c) is a diagram for e-mail when notifying free passage information. (d) is a diagram showing an example of a voice notification message when notifying free passage information. 7 is a flowchart of a process for determining whether condition A is satisfied or not in the second embodiment. 7 is a flowchart of a process for determining whether condition B is satisfied in the second embodiment. 2 is a flowchart for determining whether conditions C to G are satisfied in the second embodiment. FIG. 7 is a diagram illustrating an example of a pattern in which notification conditions are satisfied in the second embodiment. FIG. 7 is a diagram illustrating an example of a pattern in which notification conditions are satisfied in the second embodiment. FIG. 7 is a diagram illustrating an example of a pattern in which notification conditions are satisfied in the second embodiment.

(First embodiment)
A first embodiment of the notification system will be described with reference to FIGS. 1 to 8. In the first embodiment, a notification system will be described using an example in which a user uses a railway, which is a means of transportation. In railways, the area within the ticket gate of each station, that is, the area where passengers can get on and off the train, is set as the management area within the facility.

As shown in FIG. 1, in the notification system 10, a railway user pre-purchases a ticket at a reservation purchase terminal 11, and the ticket is used at a ticket gate 12 to allow entry into the area inside the ticket gate. Then, the server device 13 predicts the user's destination and the time of arrival at the destination. In this system, the server device 13 transmits service information 15, which is information about services available at the destination, to the user's mobile terminal 14 in accordance with the arrival time at the destination.

The usage ticket is a portable user identification medium that can identify the user, and is an IC card C1 containing an IC chip having a unique identification number IDi. The IC card C1 is a name-registered IC card, and each IDi is associated with an individual or a corporation. The IC card C1 can be used as a train ticket or commuter pass through short-range communication with the ticket gate 12, and can also be used for fares, commuter passes, payments at stores, etc. through short-range communication with a device equipped with a dedicated reader. It has electronic money and credit functions that can be used for.

The mobile terminal 14 is a computer terminal configured to be able to communicate with the server device 13, and is a terminal such as a smartphone, a mobile phone, or a tablet that can be carried while the user is on the move.
In the notification system 10, the server device 13 is configured to be able to communicate with an operation information providing device 16 that provides railway operation information such as train delays and suspensions. The server device 13 is configured to acquire operation information from the operation information providing device 16 at any time and to update the arrival time at the destination when the operation information regarding the travel route to the destination is changed.

In the notification system 10, the server device 13 is configured to be able to communicate with a service management device 17 that provides service management information indicating the status of services available to the user at the user's destination. An example of the service management information is locker information 18 that indicates the availability of rental lockers installed at the destination. The server device 13 transmits service information that reflects the service management information acquired from the service management device 17 to the mobile terminal 14.

The reservation/purchase terminal 11 is configured to be capable of making reservations for railway use, that is, reservations and purchases of train tickets and limited express tickets (non-reserved seat limited express tickets and reserved seat limited express tickets). The reservation purchase terminal 11 is comprised of a computer terminal that can be operated by a user, and is configured to be capable of short-range communication with the IC card C1. The reservation purchase terminal 11 is a ticket vending machine installed at a station or the like. The reservation purchase information 20, which is information regarding train tickets and limited express tickets, includes not only the purchase method but also boarding section information and limited express section information indicating usage conditions. The boarding section information is information indicating the boarding section, and includes the boarding station, the getting off station, the transfer station, and the date and time of use. The limited express section information is information indicating the limited express section in the boarding section. The limited express section information includes the type of limited express train, the limited express boarding station, the limited express getting off station, and the date and time of use. The station where the user gets off the train, such as an alighting station or a transfer station, is the user's destination. The reservation purchase terminal 11 acquires the user's IDi through short-range communication with the IC card C1 at the time of reservation purchase of the usage ticket, associates the IDi with the reservation purchase information 20, and transmits the association to the server device 13. Note that the reservation purchase terminal 11 may be, for example, a terminal that can access a reservation purchase site provided by a reservation purchase server, such as the mobile terminal 14. In this case, the user identification medium is the terminal, and entry and exit is possible by having the ticket gate 12 read the image transmitted by the reservation purchase server, for example.

The ticket inspection machine 12 is an identification number acquisition device, and is configured to be able to communicate with the server device 13. The ticket gate machine 12 is installed at the entrance/exit of the area inside the ticket gate set at each station. The ticket inspection machine 12 acquires the user's IDi through short-range communication with the IC card C1, and determines permission to enter or exit the area within the ticket gate based on the usage conditions of the IC card C1. When the ticket gate 12 allows entry and exit to the area within the ticket gate using the IC card C1, the ticket gate 12 records the installation location of the ticket gate 12 (installation station, ticket gate position, machine number, etc.) and acquisition date and time based on the acquired IDi. The ticket gate usage information 26 associated with (date and time of entry or date and time of exit) etc. is transmitted to the server device 13. In addition, when the IC card C1 has a function as a commuter pass, the ticket gate 12 uses information indicating whether the station where the ticket gate 12 is installed is in a commuter pass as information regarding the commuter pass. It is added to the information 26 and transmitted to the server device 13.

The server device 13 includes an authentication server 30 and a processing server 31, and functions as a control section.
The authentication server 30 performs IDi authentication based on the reservation purchase information 20 and the ticket gate usage information 26. The authentication server 30 is a device including a computer, and includes a management section 33, a database 34, and an authentication section 35.

Upon receiving the reservation purchase information 20, the management section 33 associates the reservation purchase information 20 with IDi and registers it in the database 34. When the authentication unit 35 receives the ticket gate usage information 26 indicating entry into the area within the ticket gate, it performs an authentication determination regarding the IDi of the ticket gate usage information 26. In the authentication determination, the authentication unit 35 authenticates IDi on the condition that the reservation purchase information 20 is registered in the database 34. For the IDi authenticated by the authentication unit 35, the management unit 33 transmits the reservation purchase information 20 and ticket gate usage information 26 along with the IDi to the processing server 31. For IDi that has not been authenticated by the authentication section 35, the management section 33 transmits the ticket inspection machine usage information 26 to the processing server 31 on the condition that information regarding the regular section is added to the ticket inspection machine usage information 26.

The processing server 31 executes a notification service that notifies the user of service information, which is information about services that the user can use, based on the information sent by the authentication server 30. Specifically, the notification service is, for example, a service that notifies the user of service information about the user's destination based on the reservation purchase information 20 in accordance with the arrival time of the destination. Such a notification service requires notification destination registration in which a user's notification destination is registered in advance in the processing server 31, and service registration in which service information of each station is registered in advance in the processing server 31. Registration of the notification destination is performed through a computer terminal that can be operated by the user, for example, the mobile terminal 14. Service registration is performed through the management terminal 36, which is a computer terminal that can be operated by the notification service provider and is configured to be able to communicate with the processing server 31.

As shown in FIG. 2A, notification destination registration is performed by accessing a user menu site provided by the processing server 31 from the mobile terminal 14. The user menu site is a portal site for users to configure and confirm notification services. When the user menu site is accessed, a user menu 38 is displayed on the mobile terminal 14.

As shown in FIG. 2(b), on the user information input screen 39 for "notification destination, etc.", in addition to the card ID (IDi) of the IC card C1 held by the user, the e-mail address and phone number of the notification destination are displayed. A number is set as an input item. On the user information input screen 39, gender, date of birth, hobbies, etc. are set as input items. After entering various input items, when the "Register" button on the user information input screen 39 is operated, the user information including the information input on the user information input screen 39 is processed as part of the notification destination information. It is sent to the server 31.

Notification destination registration is configured such that the user can select a notification method for service information in "Notification method". The notification method is configured so that email or telephone can be selected. The selected notification method is transmitted to the processing server 31 as part of the notification destination information when the user performs a transmission operation. Note that if the notification method is not selected during notification destination registration, the processing server 31 is configured to select notification by email.

The notification destination registration is configured so that the user can set the desired notification service for which the user wishes to be notified in "Notification Service Settings." The user sets the desired notification service, for example, by selecting a service from a service list. The desired notification service is transmitted to the processing server 31 as part of the notification destination information by the user's transmission operation.

Note that if the desired notification service is not set, the processing server 31 is not limited to the configuration that notifies the user of all services, but may select a service based on the user's hobbies, or notify other users of the service. You may select a service that has a high notification frequency. Furthermore, for example, when comparing on-demand buses and taxis as means of transportation, the processing server 31 may be configured to preferentially notify individuals of on-demand buses and preferentially notify corporations of taxis. .

When the processing server 31 receives notification destination information from the mobile terminal 14, it registers the notification destination information in the database 41, which is an identification number registration section. Upon receiving the notification destination information of the registered IDi, the processing server 31 updates the notification destination information registered in the database 41.

"Modify notification timing" is operated when the user wants to modify the notification timing based on the user's usage prediction, which will be described later, such as when the user misses the limited express train they were scheduled to board. The user inputs the time of arrival at the destination and performs a sending operation. As a result, modification information for modifying the notification timing of service information based on the reservation purchase information 20 is transmitted to the processing server 31.

As shown in FIG. 3, service registration is performed by the management terminal 36 accessing the administrator menu site provided by the processing server 31. The administrator menu site is a portal site where the business operator sets and confirms various menus. When the administrator menu site is accessed, an administrator menu screen 43 is displayed on the management terminal 36. Various menu information is stored in the database 41 of the processing server 31.

As shown in FIG. 4(a), "Settings for each station equipment, etc." is configured to allow the operator to set and confirm available services and their notification times. In "Each Station Facility Settings," information on available service equipment, facilities, and stores is set for each station. Examples of services include rental lockers, restaurants, massages, taxis, on-demand buses, drug stores, and popular ramen restaurants. The notification time is a relative time to the arrival time; for example, if it is "-10 minutes", the notification timing is set to 10 minutes before the arrival time. The notification time can be set to vary depending on the size of the destination and the time of arrival. For example, for a restaurant, it can be set to notify you earlier if you arrive at your destination during a busy time or if the destination station is larger. Service registration by the operator is completed by setting the service and notification time for each station.

FIG. 4B shows notification request information 45 indicating a desired notification service for an example of IDi registered in the database 41. As shown in FIG. 4(b), for this IDi user, rental lockers and on-demand buses at each station are set as notification desired services, and taxis and restaurants are set as notification refusal services.

As shown in FIG. 4C, "Notification Message 1" is configured so that the business operator can set and confirm a notification message 46 for text notification when notifying the user of service information by email. For example, the notification message 46 is a message based on the locker information 18 at the destination station, and includes the name of the station, the installation location, the size of the locker, the number of vacancies, and the like. Note that the notification message 46 regarding rental lockers may be configured to send a link to a reservation site where vacant lockers can be reserved together with the message.

As shown in FIG. 4(d), "notification audio 1" is configured to allow the operator to set and confirm an audio notification message 47 when notifying the user of service information by audio. For example, the notification message 47 is a message based on the locker information 18 at the destination station, and includes the name of the station, the installation location, the size of the locker, the number of vacancies, and the like.

As shown in FIG. 5(a), "notification destination etc." is the user information 48 of each user, that is, the information entered by the user on the user information input screen 39 of FIG. Constructed so that it can be checked. In "Notification destination, etc.", for example, by inputting the IDi to be confirmed, the user information 48 associated with that IDi, that is, notification destination email address, notification destination phone number, gender, date of birth, and hobbies. The system is configured so that operators can confirm the following information.

As shown in FIG. 5(b), the "vacant locker information" is configured to enable the operator to check the availability of rental lockers at each station. The empty locker information 49 is based on the locker information 18 sent from the service management device 17 to the processing server 31. In the "vacant locker information", for example, by inputting the name of the station to be confirmed, the operator can confirm the locker information 18 of that station. The empty locker information 49 includes the locker position indicating the location where the locker is installed, as well as the size of the locker and the number of empty lockers. Note that the service management device 17 updates the locker information 18 every time the locked state of the locker changes, and transmits the updated locker information 18 to the processing server 31.

As shown in FIG. 5C, the "reservation purchase information" is configured so that the business operator can check the reservation purchase information 20 registered in the database 41. In "reservation purchase information", for example, by inputting an IDi to be confirmed, the reservation purchase information 20 associated with that IDi is displayed.

As shown in FIG. 5(d), the "ticket gate information" is configured so that the operator can check the usage history of the ticket gate 12 by each IDi. In "Ticket Check Machine Information", for example, by inputting an IDi to be checked, a ticket check machine usage history 51 indicating the ticket check machine usage information 26 of that IDi is displayed. The ticket gate usage history 51 is composed of the ticket gate location, which is the location of the ticket gate 12 that has allowed entry and exit, the machine number of the ticket gate 12, the date and time of entry, and the date and time of exit.

The "notification history information" is configured so that the business operator can check the notification history for each user who has registered the notification destination for each IDi. In the "notification history information", for example, by inputting an IDi to be checked, it is possible to check the notification history information, which includes services actually notified for that IDi, notification date and time, and the like.

The configuration of the processing server 31 will be explained in detail.
As shown in FIG. 1, the processing server 31 includes an acquisition section 55, a prediction section 56, a detection section 57, and a notification section 58, in addition to a database 41 in which notification destination information including IDi and user information is registered. ing. Note that the database 41 stores various menu information as well as diagram information indicating a railway diagram.

The acquisition unit 55 acquires various information and registers it in the database. The acquisition unit 55 acquires the IDi, reservation purchase information 20, and ticket gate usage information 26 transmitted by the authentication server 30. The acquisition unit 55 acquires notification destination information and modification information transmitted by the mobile terminal 14. The acquisition unit 55 acquires various menu information transmitted from the management terminal 36. The acquisition unit 55 serves as an operation information acquisition unit and acquires operation information provided by the operation information providing device 16. The acquisition unit 55 acquires service management information, such as locker information 18, transmitted by the service management device 17.

When the acquisition unit 55 acquires the reservation purchase information 20 together with the ticket gate usage information 26, the prediction unit 56 predicts the usage of IDi included therein. In the usage prediction, the prediction unit 56 predicts the user's travel route based on the reservation purchase information 20, ticket gate usage information 26, diagram information, and operation information, and predicts the time on the predicted travel route.

Specifically, the prediction unit 56 calculates the required time from the station where the ticket gate 12 is installed to the station where the ticket gate 12 is installed, which is indicated by the ticket gate usage information 26, taking into consideration the travel speed of the user and the railway operation status based on the operation information. The travel route is predicted by selecting the route and transit station that the user will use to ensure the shortest route. The prediction unit 56 predicts the train that the user will board, and calculates the predicted departure time and arrival time of the train, thereby predicting the time. The prediction unit 56 performs a new usage prediction every time the operation information related to the usage prediction is changed.

The detection unit 57 detects service information to be notified to the user at each destination based on usage prediction. The detection unit 57 detects service information by selecting a service to be notified to the user at each destination for each notification time based on the destination based on the usage prediction and the notification destination information registered in the database 41. do. That is, the detection unit 57 detects services with different notification times as separate service information even if the services are available at the same destination.

The notification unit 58 sets a notification timing for each service information detected by the detection unit 57 based on the arrival time of each destination and notification destination information registered in the database 41. When the acquisition unit 55 acquires the modification information, the notification unit 58 modifies the notification timing based on the modification information. When the current time reaches the notification timing, the notification unit 58 determines that the notification condition has been met and transmits service information reflecting the latest service management information to the mobile terminal 14.

Further, when the acquisition unit 55 acquires the ticket gate usage information 26 to which information regarding the regular section is added, the detection unit 57 detects service information when the exit station based on the ticket gate usage information 26 is outside the regular section. . The notification unit 58 transmits the detected service information to the mobile terminal 14. Note that notification destination registration may be configured to allow individual stations to be notified of service information regardless of regular intervals, or may be configured such that only service information based on usage predictions is sent. .

The operation of the notification system 10 will be described with reference to FIGS. 6 to 8, with specific examples focusing on the processing executed by the processing server 31. In the following example, it is assumed that the acquisition unit of the processing server 31 acquires reservation purchase information as well as ticket gate usage information.

FIG. 6A is an example of notification of service information based on usage prediction, and shows an example where the boarding section and the limited express section are the same, and the limited express section is a non-reserved seat section.
As shown in FIG. 6(a), in the processing server 31, when the acquisition unit 55 acquires ticket gate usage information 26 based on entry to Tokyo Station (12:30), the prediction unit 56 predicts usage. In the usage prediction, since the limited express section is a non-reserved seat section, the prediction unit 56 selects the limited express train that will arrive at the exit station earliest from among the limited express trains whose departure times are set after the entry time to Tokyo Station. do. The prediction unit 56 then calculates the departure time (13:20) and arrival time (16:43) of the selected limited express train. The notification unit 58 sets the notification timing 6a to be a notification time earlier than the arrival time (16:43) calculated by the prediction unit 56. The notification unit 58 transmits the service information of Shin-Aomori Station to the mobile terminal 14 at notification timing 6a.

FIG. 6(b) is an example of notification of service information based on usage prediction, and shows an example where the boarding section and the limited express section are the same, and the limited express section is a reserved seat section.
As shown in FIG. 6(b), the processing server 31 performs usage prediction based on entrance to Tokyo Station (12:00). In the usage prediction, since the entry time is earlier than the departure time of the reserved express train, this limited express train is selected as the limited express train on which the user will board, and the arrival time (15:29) is calculated. The notification unit 58 sets the notification timing 6b to be a notification time earlier than the arrival time (15:29). The notification unit 58 transmits the service information of Shin-Aomori Station to the mobile terminal 14 at notification timing 6b.

FIG. 6C is an example of notification of service information based on usage prediction, and shows an example where the boarding section and the limited express section are the same and the user has missed the reserved limited express train (reserved seat).
As shown in FIG. 6(c), the processing server 31 performs usage prediction based on entry to Tokyo Station (12:30). In the usage prediction, since the entry time is later than the departure time of the reserved express train, the prediction unit 56 predicts the travel route assuming that the user has missed the limited express train. In this case, the prediction unit 56 selects the limited express train on which the user will board from among the limited express trains whose departure time is set after the entry time to Tokyo Station, with the limited express section as the non-reserved seat section. The prediction unit 56 calculates the predicted departure time (13:20) and arrival time (16:43) of the limited express train. The notification unit 58 sets the notification timing 6c to be a notification time earlier than the arrival time (16:43). The notification unit 58 transmits the service information of Shin-Aomori Station to the user's mobile terminal 14 at notification timing 6c.

FIG. 6(d) is an example of notification of service information based on usage prediction, and shows an example where the boarding section and the express section are the same and the arrival time is shifted by the user.
As shown in FIG. 6(d), the processing server 31 performs usage prediction based on entrance to Tokyo Station (12:00). In the usage prediction, since the entry time (12:00) is earlier than the departure time (12:20) of the reserved limited express train, the prediction unit 56 selects the limited express train as the limited express train for the user to board. The prediction unit 56 then calculates the arrival time (15:29) of the selected express train. The notification unit 58 sets the notification timing 6d to be a notification time earlier than the arrival time (15:29).

However, the user actually missed the 12:20 limited express train departing from Tokyo, and boarded the 13:20 limited express train departing from Tokyo. Therefore, the user sent correction information to shift the arrival time through the mobile terminal 14. In the processing server 31 that has acquired the modification information, the notification unit 58 corrects the notification timing 6d to a notification timing 61d that is a notification time earlier than the arrival time based on the modification information. The notification unit 58 transmits the service information of Shin-Aomori Station to the user's mobile terminal 14 at notification timing 61d.

FIG. 7A is an example of notification of service information based on usage prediction, and shows an example where the boarding section is longer than the limited express section and the limited express section is a non-reserved seat section.
As shown in FIG. 7A, the processing server 31 performs usage prediction based on entry to Shinjuku Station (11:40). In the usage prediction, since the limited express section is a non-reserved section, the prediction unit 56 calculates the travel route and various times so that the time required from Shinjuku Station, the departure station, to Hirosaki Station, the alighting station, is the shortest. Predict. Specifically, the prediction unit 56 predicts the departure time at Shinjuku Station (11:50), the arrival time at Tokyo Station (12:03), the departure time at Tokyo Station (12:20), and the train departure time at Shin-Aomori Station. Predict the arrival time (15:29). The prediction unit 56 also predicts the departure time at Shin-Aomori Station (15:40) and the arrival time at Hirosaki Station (16:16). The notification unit 58 sets notification timings 7a, 7b, and 7c earlier than each arrival time predicted by the prediction unit 56 by the notification time. The notification unit 58 transmits the service information of Tokyo Station to the mobile terminal 14 at notification timing 7a.

At Tokyo Station, users use a ticket gate 12 for transfer when transferring to a limited express train. As a result, new ticket gate usage information 26 is input from the authentication server 30 to the processing server 31, and usage prediction is performed based on the new ticket gate usage information 26. As a result, the time prediction is updated, and the notification timings 7b and 7c are corrected to the notification timings 71b and 71c. In other words, even if the entry time (12:30) included in the ticket gate usage information 26 from the transfer ticket gate 12 at Tokyo Station is past the originally predicted departure time (12:20), the actual The notification timing is set to match the entrance time (12:30).

The notification unit 58 transmits the service information of Shin-Aomori Station to the mobile terminal 14 at notification timing 71b. In addition, if the entry based on the ticket gate usage information 26 at the time of transfer at Shin-Aomori Station is earlier than the departure time of the conventional line (17:37), the notification unit 58 carries the service information of Hirosaki Station at the notification timing 71c. It is transmitted to the terminal 14.

FIG. 7(b) is an example of notification of service information based on usage prediction, and shows an example where the boarding section is longer than the limited express section and the user misses the reserved express train (reserved seat).
As shown in FIG. 7(b), the processing server 31 performs usage prediction based on the ticket gate usage information 26 indicating entry to Shinjuku Station (11:40). In the usage prediction, since the limited express section is a reserved seat section, the prediction unit 56 uses the departure time at Tokyo Station (12:20) and the arrival time at Shin-Aomori Station (15:29) as reference times, and uses Shinjuku as the reference time. The travel route and various times are predicted so that the time required from the station to Hirosaki Station is the shortest. Specifically, the prediction unit 56 predicts the departure time at Shinjuku Station (11:50), the arrival time at Tokyo Station (12:03), the departure time at Tokyo Station (12:20), and the train departure time at Shin-Aomori Station. Calculate the arrival time (15:29). The prediction unit 56 also calculates the departure time at Shin-Aomori Station (15:40) and the arrival time at Hirosaki Station (16:16). The notification unit 58 sets the notification timings 7d, 7e, and 7f to times before the arrival time predicted by the prediction unit 56 by the notification time. The notification unit 58 transmits the service information of Tokyo Station to the user's mobile terminal 14 at the notification timing 7d.

At Tokyo Station, users use a ticket gate 12 for transferring to a limited express train. As a result, new ticket gate usage information 26 is input from the authentication server 30 to the processing server 31, and usage prediction is performed based on the new ticket gate usage information 26.

In this case, the entry date and time (12:30) included in the ticket gate usage information 26 of the transfer ticket gate 12 at Tokyo Station has passed the originally predicted departure time of the limited express train (12:20). There is. Therefore, the prediction unit 56 determines the time required to reach Hirosaki Station from limited express trains whose departure times are set after the entry time to the transfer ticket gate 12 at Tokyo Station (12:30), with the limited express sections as non-reserved seat sections. Select the express train to take the shortest time. The prediction unit 56 then calculates the predicted departure time of the limited express train at Tokyo Station (13:20) and arrival time at Shin-Aomori Station (16:43). Furthermore, the prediction unit 56 selects a train (conventional line) on which the user will board based on the arrival time at Shin-Aomori Station (16:43), and selects the train (conventional line) on which the user will board based on the arrival time at Shin-Aomori Station (16:43) and the departure time at Shin-Aomori Station (17:43). 37) and the arrival time at Hirosaki Station (18:12). The notification unit 58 sets the notification timings 71e and 71f to times before each arrival time updated by the prediction unit 56 by the notification time. The notification unit 58 transmits the service information of Shin-Aomori Station to the mobile terminal 14 at notification timing 71e. Furthermore, if the date and time of entry to the conventional line at Shin-Aomori Station is earlier than the departure time (17:37), the notification unit 58 transmits service information of Hirosaki Station to the mobile terminal 14 at notification timing 71f.

FIG. 8 shows an example where part of the riding section is a regular section. As shown in FIG. 8, if you enter from Tsurumi Station within the regular section (Tsurumi Station to Shinjuku Station) and exit from Ikebukuro Station, which is outside the regular section, the regular section becomes a no-notification section. Then, at timing 8a when the acquisition unit 55 acquires the ticket gate usage information 26 indicating participation at Ikebukuro Station outside the scheduled section, the notification unit 58 transmits the service information of Ikebukuro Station to the mobile terminal 14.

The effects of the first embodiment will be explained.
(1-1) The notification system 10 predicts the arrival time of the destination by predicting usage based on the reservation purchase information 20 and the ticket gate usage information 26, and adjusts the arrival time of each destination to the predicted arrival time. The service information of the destination will be notified to the user. That is, the user is notified of information on services available at the destination in accordance with the arrival time at the destination. This makes it possible to notify the user of information about services that meet the user's needs. Moreover, by notifying the user of information on how to reserve a service available at the destination at the time of notification, the convenience of the notification system 10 can be improved and the use of the service can be promoted.

(1-2) The notification system 10 is configured so that the user can select the service for which he/she desires notification. Thereby, the user can be notified of service information that accurately captures the user's needs, and the convenience of the notification system 10 for the user is improved.

(1-3) The notification system 10 is configured to allow notification time for each service to be set individually. Therefore, for example, for services that can be reserved, the more complicated the reservation procedure is, the earlier the notification can be made. As a result, the user's convenience of the notification system 10 is improved.

(1-4) The notification system 10 is configured so that the arrival time can be shifted by the user. Therefore, even if an event that cannot be recognized by the notification system 10, such as a missed train, occurs, service information can be notified at an appropriate timing.

(1-5) In the notification system 10, when the operating status of the train on the predicted travel route changes, the usage prediction is performed again and the notification timing is reset to match the arrival time according to the usage prediction. Therefore, for example, even if a train on the travel route is delayed, service information can be notified to the user at a timing that takes the delay into consideration. This increases the convenience of the notification system 10 for users.

A second embodiment of the notification system will be described with reference to FIGS. 9 to 17. Note that in the second embodiment, the same parts as in the first embodiment are given the same reference numerals, and a detailed explanation thereof will be omitted.

As shown in FIG. 9, the notification system 100 allows the user to enter and exit the area within the ticket gate using the ticket gate 12 while using the service managed by the service management device 101, and when a predetermined condition is met, the notification system 100 updates the service being used. This is a system that transmits service information 102 indicating the information to the mobile terminal 14.

The service management device 101 manages the use of services using the IC card C1. The service management device 101 acquires the IDi of the IC card C1 through short-range communication with the IC card C1 when using the service, and sends service usage information that associates the acquired IDi with the usage status of the service to the server device 103. do. In this embodiment, the service managed by the service management device 101 is a rental locker. The rental locker is configured to enable locking/unlocking of the locker, payment of fees, etc. based on IDi through short-range communication with the IC card C1. When the locker is locked or unlocked, the service management device 101 transmits locker usage information 104 indicating the location of the locker as well as the date and time of use according to IDi to the server device 103 as service usage information. Note that the service usage information may be, for example, reservation information for restaurants, taxis, etc. that are associated with a station as an installation location.

The server device 103 includes a processing server 105 and functions as a control unit. The processing server 105 executes a notification service that notifies the user of service information indicating the service that the user is using, based on the ticket gate usage information 26 and the service usage information. Such a notification service requires notification destination registration, in which a user's notification destination is registered in advance in the processing server 105, and notification condition registration, in which notification conditions, which are conditions for notifying service information, are registered in advance in the processing server 105. be. Registration of notification conditions is performed through the management terminal 106, which is a computer terminal that can be operated by the notification service provider and is configured to be able to communicate with the processing server 105.

As shown in FIG. 10A, notification condition registration is performed by accessing the notification condition setting site provided by the processing server 105 through the management terminal 106. The notification condition setting site is a portal site where business operators can set and check various notification conditions. When the management terminal 36 is accessed, an administrator menu screen 108 is displayed on the management terminal 106. Various menu information is stored in the database 107 of the processing server 105.

As shown in FIG. 10(b), in "Notification settings", notification/non-notification is set according to the conditions based on the combination of the installation location of the rental locker and the entry/exit based on the ticket gate usage information 26 of the installation location. be done.

As shown in FIG. 10(c), the "notification judgment time" is configured so that the operator can set and check the notification judgment time for determining whether notification is necessary according to the elapsed time from the start of service usage. There is. The notification determination time is set to 60 minutes, for example.

As shown in FIGS. 10(d) and 10(e), "Notification Message 1" is configured so that the operator can set and check the notification message 112 used when notifying the user of service information by email. There is. "Voice Notification 1" is configured to allow the business operator to set and confirm the notification message 113 used when notifying the user of service information by voice. The notification messages 112 and 113 are messages based on the locker usage information 104, and are messages indicating the station name, installation location, and the presence of luggage in the locker.

"Notification destination, etc." is configured so that the business operator can confirm the user information 48 of each user, that is, the information input by the user on the user information input screen 39 shown in FIG. 2(b).
As shown in FIG. 11(a), the "locker information" is configured so that, for example, by inputting the IDi to be confirmed, the operator can set and confirm the locker usage information 104 associated with the IDi. .

The "ticket gate information" is configured so that the operator can check the ticket gate usage information 26 registered in the database 107.
The "notification history information" is configured so that the business operator can check the notification history for each user who has registered the notification destination for each IDi.

As shown in FIG. 11(b), the "time for free passage through the ticket gate" is configured so that the operator can set and confirm the free passage time, which is the time during which the user can pass through the ticket gate 12 for free. The free passage time is, for example, 30 minutes.

As shown in FIGS. 11(c) and 11(d), "notification message 2" is the notification message 116 used when notifying the user via email of free passage information indicating that the user can pass through the ticket gate 12 for free. It is configured so that it can be set and confirmed by the business operator. "Notification voice 2" is configured so that the operator can set and confirm the notification message 117 used when notifying the user of free passage information indicating that the user can pass through the ticket gate 12 for free. The notification messages 116 and 117 are composed of a message indicating that the locker can pass through the ticket gate 12 for free and the time in addition to the station name, installation location, and message indicating that the locker contains luggage based on the locker usage information 104. ing.

The configuration of the processing server 105 will be explained in detail.
As shown in FIG. 1, the processing server 105 includes a database 107 that registers notification destination information including IDi and user information as an identification number registration unit, an acquisition unit 120, a detection unit 121, a notification unit 122, and a permission unit. 123.

The acquisition unit 120 acquires various information and registers it in the database 107. The acquisition unit 55 acquires the ticket gate usage information 26 transmitted by the ticket gate 12 and the notification destination information transmitted by the user's mobile terminal 14. The acquisition unit 120 acquires various menu information transmitted by the management terminal 106. The acquisition unit 120, as a usage information acquisition unit, acquires the service usage information transmitted by the service management device 101.

The detection unit 121 detects, as service information, service usage information for which the use of the service has not been completed, regarding IDi of the ticket gate usage information 26 acquired by the acquisition unit 120. The service information in this embodiment is locker usage information 104. Locker usage information 104 registered in the database 107 is deposit information indicating whether a rental locker is in use.

The notification unit 122 determines whether notification conditions are met for the service information detected by the detection unit 121, and if the notification conditions are met, transmits a message regarding the service information to the user's mobile terminal 14. The notification unit 122 determines that the notification condition is satisfied when any one of conditions A, B, C, D, E, F, or G, which will be described later, is satisfied.

As shown in FIGS. 12 to 14, in the process of determining whether the notification condition is met, the processing server 105 acquires the ticket gate usage information 26 (step S10), and deposits the IDi of the ticket gate usage information 26. The presence or absence of information is determined (step S11). If there is no deposit information (step S11: NO), the processing server 105 ends the series of processing, and if there is deposit information (step S11: YES), it determines whether various conditions are met.

As shown in FIG. 12, condition A is that the notification setting conditions set in "notification settings" are satisfied. If the notification setting condition is satisfied (step S12: YES), the notification unit 122 selects the notification condition based on condition A to be satisfied (step S13) and ends the series of processes. On the other hand, if the notification setting condition is not satisfied (step S12: NO), the processing server 105 ends the series of processing.

As shown in FIG. 13, condition B is that the notification determination time has elapsed since the user started using the rental locker. Based on the acquisition time of the ticket gate usage information 26 and the locker usage information 104, the notification unit 122 determines that the notification condition based on condition B is set if the notification determination time has elapsed since the start of service usage (step S21: YES). It is determined that this has been established (step S22), and the series of processing ends. On the other hand, if the notification determination time has not elapsed (step S21: NO), the notification unit 122 ends the series of processes.

As shown in FIG. 14, condition C is such that entry into the area inside the ticket gate and exit from the area inside the ticket gate are matched for the IDi who is using the service at the ticket gate 12 of the locker-installed station where the rental locker in use is installed. It is obtained as follows. If condition C is satisfied (step S31: YES), the notification unit 122 determines that the notification condition is satisfied (step S32). On the other hand, if condition C is not satisfied (step S31: NO), the notification unit 122 determines whether condition D is satisfied or not (step S33).

Condition D is entering the area inside the ticket gate at the first station, using a rental locker installed inside the ticket gate at the first station, exiting from the area inside the ticket gate at the second station, and entering the area inside the ticket gate at the second station. admissions, these are obtained in chronological order. The notification unit 122 determines that the notification condition is satisfied when condition D is satisfied (step S33: YES) (step S32), and determines whether condition E is satisfied when condition D is not satisfied (step S33: NO). is determined (step S34).

Condition E is the use of rental lockers installed outside the ticket gate area at the first station, entry into the ticket gate area at the first station, exit from the ticket gate area at the second station, and the inside ticket gate area at the second station. entry, these are obtained in chronological order. The notification unit 122 determines that the notification condition is satisfied when condition E is satisfied (step S34: YES) (step S32), and determines whether condition F is satisfied when condition E is not satisfied (step S34: NO). is determined (step S35).

Condition F is exiting from the area inside the ticket gate at the first station, using a rental locker installed outside the area inside the ticket gate at the first station, entering the area inside the ticket gate at the first station, and entering the area inside the ticket gate at the second station. Participation from, these are obtained in chronological order. The notification unit 122 determines that the notification condition is satisfied when condition F is satisfied (step S35: YES) (step S32), and determines whether condition G is satisfied when condition F is not satisfied (step S35: NO). is determined (step S36).

Condition G is the use of rental lockers installed within the ticket gate area of the first station, exit from the ticket gate area of the first station, entry to the ticket gate area of the first station, and the inside ticket gate area of the second station. Participation from, these are obtained in chronological order. The notification unit 122 determines that the notification condition is satisfied when condition G is satisfied (step S36: YES), and executes a series of processes when condition G is not satisfied (step S36: NO). It will end once.

When the permission condition based on the ticket gate usage information 26 and the locker usage information 104 is satisfied, the permission unit 123 allows the user to temporarily enter and exit the area within the ticket gate of the station where the locker is installed. When condition C is satisfied due to entry from the area inside the ticket gate, the permission unit 123 determines that the permission condition is satisfied if the user is using a rental locker installed in the area inside the ticket gate, and exits from the area inside the ticket gate. allow temporary entry of users. In addition, when condition C is satisfied due to admission to the area inside the ticket gate, if the user is using a rental locker installed in the area outside the ticket gate, the permission unit 123 temporarily allows the user to enter the area outside the ticket gate. Permit participation. The permission unit 123 transmits permission information for temporarily permitting the user to enter and exit the ticket gate 12 to the corresponding ticket gate 12. The ticket gate machine 12 that has received the permission information allows the user to enter and exit using the IC card C1 only during the free passage time. The notification unit 122 transmits a notification message 116 to the mobile terminal 14 indicating that temporary entry/exit to the area within the ticket gate is permitted.

Patterns in which conditions C to G are satisfied will be described with reference to FIGS. 15 to 17. Note that, in the following, "admission" indicates entry into the managed area, and "exit" indicates exit from the managed area.
Patterns 1, 2, 3, and 4 will be explained with reference to FIG. 15. In Patterns 1 to 4, the only difference is the location of the locker where the luggage is left, but the travel route of the user is the same. Therefore, first, the travel route of the user will be explained.

As shown in FIG. 15, in patterns 1 to 4, the user entered at Tsurumi Station and traveled to Tokyo Station by train. Users entered the event at Tokyo Station, completed their errands near Tokyo Station, and then re-entered at Tokyo Station. After traveling to Tsurumi Station by train, the user left his luggage in the locker and entered the race at Tsurumi Station.

In pattern 1, users deposited their luggage in a rental locker located inside the ticket gate at Tsurumi Station. In this case, entering at Tokyo Station will result in a notification based on Condition D, and exiting at Tsurumi Station will result in notification based on Condition C and notification that temporary entry is permitted at Tsurumi Station.

In pattern 2, users deposited their luggage in a rental locker located inside the ticket gate at Tokyo Station. In this case, a notification based on condition C will be given by entering at Tokyo Station, and a notice based on condition G will be given by entering at Tsurumi Station.

In pattern 3, users left their luggage in a rental locker outside the ticket gate at Tsurumi Station. In this case, a notification based on condition E will be given by entering at Tokyo Station, and a notification based on condition C will be given by entering at Tsurumi Station.

In pattern 4, the user left their luggage in a rental locker in the area outside the ticket gates at Tokyo Station. In this case, entering at Tokyo Station will result in a notification based on Condition C and notification that temporary entry is permitted at Tokyo Station, and entering at Tsurumi Station will result in notification based on Condition F.

Patterns 5, 6, 7, 8, 9, and 10 will be explained with reference to FIG. In patterns 5 to 10, the only difference is the location of the locker where the baggage is deposited, but the travel route of the user is the same. Therefore, first, the travel route of the user will be explained.

As shown in FIG. 16, in patterns 5 to 10, the user enters at Tsurumi Station, travels to Shinagawa Station using the No. 1 Railway, and then passes through the transfer ticket gate 12 at Shinagawa Station to the No. I transferred from the railway to the second railway. After that, users travel to Sengakuji Station using the second railway, and then compete at Sengakuji Station. Users who finished their business near Sengakuji Station entered Sengakuji Station, took the 2nd Railway to Shinagawa Station, and transferred from the 2nd Railway to the 1st Railway at Shinagawa Station. After traveling to Tsurumi Station using the First Railway, the user left his luggage in a locker and entered the race at Tsurumi Station.

In pattern 5, the user left their luggage in a rental locker inside the ticket gate at Tsurumi Station. In this case, a notification based on Condition D was given when transferring from the Second Railway to the First Railway at Shinagawa Station, and due to participation at Tsurumi Station, a notification based on Condition C and temporary admission to Tsurumi Station was granted. A notification will be given.

In pattern 6, the user left their luggage in a rental locker inside the ticket gate at Sengakuji Station. In this case, a notification based on condition C is given when entering at Sengakuji Station, and a notification based on condition G is given when changing from the second railway to the first railway at Shinagawa station.

In pattern 7, the user deposited their luggage in a rental locker outside the ticket gate at Tsurumi Station. In this case, a notification based on condition D is given when transferring from the second railway to the first railway at Shinagawa Station, and a notification based on condition C is given when the passenger exits at Tsurumi Station.

In pattern 8, the user deposited their luggage in a rental locker in the area outside the ticket gate at Sengakuji Station. In this case, a notification based on condition C will be given upon entry at Sengakuji Station, and a notification based on condition F will be given when transferring from the second railway to the first railway at Shinagawa Station.

In pattern 9, the user deposited their luggage in a rental locker located inside the ticket gate of the No. 1 Railway at Shinagawa Station. In this case, a notification based on Condition E will be given upon entry at Sengakuji Station, a notice based on Condition C will be given when transferring from the 2nd Railway to the 1st Railway at Shinagawa Station, and a notification will be given based on Condition C when transferring from the 1st Railway to the 2nd Railway at Shinagawa Station. A notice will be given that temporary access to the railway has been granted.

In pattern 10, the user left his luggage in a rental locker located inside the ticket gate of the second railway at Shinagawa Station. In this case, a notification based on condition D is given when entering at Sengakuji Station, and a notification based on condition C is given when transferring from the second railway to the first railway at Shinagawa Station.

Patterns 11, 12, 13, 14, 15, 16, and 17 will be described with reference to FIG. 17. In patterns 11 to 17, the only difference is the location of the locker where the luggage is left, but the travel route of the user is the same. Therefore, first, the travel route of the user will be explained.

As shown in FIG. 17, in patterns 11 to 17, the user entered Shibuya Station, traveled to Shinjuku Station using the First Railway, and then entered the game at Shinjuku Station. After traveling on foot along the connecting passage connecting Shinjuku Station and Shinjuku 3-chome Station, the users entered the second railway at Shinjuku 3-chome Station. After that, the users took the second railway to Ikebukuro Station, and then entered the race from Ikebukuro Station. Users who had completed their business near Ikebukuro Station entered Ikebukuro Station, took the second railway to Shinjuku 3-chome Station, and then exited from Shinjuku 3-chome Station. After starting the connecting passage on foot, the user entered the First Railway at Shinjuku Station. After traveling to Shibuya Station using the First Railway, the user left his luggage in the locker and exited from Shibuya Station.

In pattern 11, the user deposited his luggage in a rental locker located inside the ticket gate of the First Railway at Shibuya Station. In this case, entering at Shinjuku Station will result in a notification based on Condition D, and appearing at Shibuya Station will result in notification based on Condition C and notification that temporary entry to Shibuya Station is permitted.

In pattern 12, the user deposited his luggage in a rental locker installed in the area inside the ticket gate of the second railway at Ikebukuro Station. In this case, a notification based on condition C will be given by entering at Ikebukuro Station, and a notification based on condition G will be given by entering at Shinjuku 3-chome Station.

In pattern 13, the user deposited their luggage in a rental locker located outside the ticket gate at Shibuya Station. In this case, a notification based on condition E will be given by entering at Shinjuku Station, and a notification based on condition C will be given by entering at Shibuya Station.

In pattern 14, the user deposited their luggage in a rental locker installed in the area outside the ticket gate at Ikebukuro Station. In this case, by entering at Ikebukuro Station, a notification based on Condition C and a notification of temporary permission to participate at Ikebukuro Station will be issued, and by entering at Shinjuku 3-chome Station, a notification based on Condition F will be issued.

In pattern 15, the user deposited his luggage in a rental locker installed within the ticket gate area of the No. 1 Railway at Shinjuku Station. In this case, by entering at Shinjuku Station, the user receives a notification based on Condition C and a notification that temporary entry is permitted at Shinjuku Station.

In pattern 16, users deposited their luggage in rental lockers installed in the connecting passageways outside the ticket gates of Shinjuku Station and Shinjuku 3-chome Station. In this case, a notification based on condition E is given by entering the second railway at Ikebukuro Station, and a notification based on condition C is given by exiting from the second railway at Shinjuku 3-chome Station. Furthermore, a notification based on Condition C is given upon entering Shinjuku Station.

In pattern 17, the user left their luggage in a rental locker located inside the ticket gate at Shinjuku 3-chome Station. In this case, entering the Second Railway at Ikebukuro Station will result in a notification based on Condition D, and exiting from the Second Railway at Shinjuku 3-chome Station will result in a notification based on Condition C and a temporary notification regarding Shinjuku 3-chome Station. You will be notified that your participation has been approved.

The effects of the second embodiment will be explained.
(2-1) When the notification condition based on the ticket gate usage information 26 and the locker usage information 104 is satisfied, the notification system 100 transmits a message indicating that the service is being used to the mobile terminal 14. That is, the notification system 100 notifies the user of service information that is information about the service being used. This makes it possible to notify the user of information about services that meet the user's needs.

(2-2) Rental lockers are a service that requires termination of use. The notification system 100 transmits the fact that there is a rental locker in use to the mobile terminal 14 as service information. Therefore, users are less likely to forget that they are using a rental locker.

(2-3) The notification system 100 notifies the user of service information when the elapsed time from the start of use of the rental locker is equal to the notification determination time. Thereby, service information can be notified to the user according to the elapsed time from the start of use.

(2-4) The notification system 100 notifies the user of service information when the elapsed time from the start of use of the rental locker has elapsed by the notification determination time. Thereby, service information can be notified to the user according to the elapsed time from the start of use.

(2-5) If condition C is satisfied, the user can receive notification of service information at the station where the locker is installed. That is, the user can receive notification of service information at a location close to the location where the rental locker is installed. As a result, the user's convenience in using the rental locker can be improved.

(2-6) If condition D or condition E is satisfied, the user can receive notification of service information when starting to move toward the station where the locker is installed. This makes users aware of the need to take out their luggage at stations where lockers are installed.

(2-7) If condition F or condition G is satisfied, the user can receive notification of service information after moving from the station where the locker is installed. This makes it difficult for users to forget that they need to return to the locker-equipped station even if they move from the locker-equipped station.

(2-8) Users may be permitted to temporarily enter and exit from the area within the ticket gate when Condition C is met. As a result, the user who is reminded of the use of the rental locker by the notification message can enter and exit through the ticket gate 12 using the IC card C1. As a result, it is possible to reduce the burden on users and station staff, and it is also possible to increase convenience for users in case they forget to use a rental locker.

The first and second embodiments can be modified and implemented as follows. The first and second embodiments and the following modified examples can be implemented in combination with each other to the extent that they are not technically inconsistent.

- In the first and second embodiments, the notification system was explained using as an example a user of a transportation facility whose station is a facility having a management area. The facility having the management area is not limited to this, but may be an airport, a ferry terminal, a bus terminal, etc. as it relates to transportation. Further, the facility having the management area may be, for example, a theme park such as an amusement park, a venue where an event such as an exposition is held, or the like.

- In the first and second embodiments, the user identification medium may record the IDi input at the time of reservation purchase, and the recorded IDi may be acquired by the ticket gate 12. Therefore, the user identification medium may be a magnetic recording medium on which a code indicating usage conditions is written, or a print recording medium on which a bar code or the like indicating usage conditions is printed.

- In the first embodiment, the prediction unit 56 may have a configuration in which the shift of the arrival time by the user is omitted, and the notification unit 58 may have a configuration in which the service to be notified to the user is notified all at once. Good too.

C1... IC card, 10... Notification system, 11... Reservation purchase terminal, 12... Ticket gate, 13... Server device, 14... Mobile terminal, 16... Operation information providing device, 17... Service management device, 100... Notification system, 101 ...Service management device, 103...Server device.

Claims (12)

A communication system including a control unit configured to be able to communicate with an identification number acquisition device that acquires an identification number individually set for each ticket of the facility when entering and exiting a management area in the facility,
The control unit includes:
an identification number registration unit in which user information regarding the user of the identification number is registered in association with the identification number;
a detection unit that detects service information including at least one of services available to the user at the facility and services used by the user at the facility;
a notification unit that notifies a notification destination included in the user information of the service information when a notification condition based on the acquisition of the identification number by the identification number acquisition device is satisfied ;
The usage ticket is a transportation usage ticket that specifies a ride section on a transportation facility,
The identification number acquisition device is a ticket gate, and also acquires the acquisition time of the identification number,
The control unit further includes a prediction unit that predicts a destination in the riding section and an arrival time at the destination based on the acquisition time,
The detection unit detects a service available to the user at the destination as the service information,
The notification unit sets a notification timing based on the arrival time predicted by the prediction unit as the notification condition,
The notification unit sets the notification timing for each service.
Notification system. The notification system according to claim 1 , wherein the detection unit detects a service selected in advance by the user as the service information. The control unit further includes an operation information acquisition unit that acquires operation information of the transportation facility,
The prediction unit appropriately reflects operation information in the boarding section in the prediction of the arrival time,
The notification system according to claim 1 , wherein the notification unit resets the notification timing based on the changed arrival time when the prediction unit changes the arrival time. The prediction unit is configured to be able to shift the arrival time by the user,
The notification system according to any one of claims 1 to 3, wherein the notification unit resets the notification timing based on the changed arrival time when the arrival time is changed. A communication system including a control unit configured to be able to communicate with an identification number acquisition device that acquires an identification number individually set for each ticket of the facility when entering and exiting a management area in the facility,
The control unit includes:
an identification number registration unit in which user information regarding the user of the identification number is registered in association with the identification number;
a detection unit that detects service information including at least one of services available to the user at the facility and services used by the user at the facility;
a notification unit that notifies a notification destination included in the user information of the service information when a notification condition based on the acquisition of the identification number by the identification number acquisition device is satisfied ;
The usage ticket is a transportation usage ticket that allows use of transportation facilities,
The identification number acquisition device is a ticket gate,
The control unit further includes a usage information acquisition unit that acquires usage information of the service used by the user,
The detection unit detects the usage information acquired by the usage information acquisition unit as the service information,
The notification unit sets the notification condition that the identification number is acquired such that entry into the management area and exit from the management area are paired in the ticket gate installed in the same facility. Included in
Notification system. The notification system according to claim 5 , wherein the notification unit includes in the notification condition an elapsed time since the identification number was acquired at the ticket gate. A communication system including a control unit configured to be able to communicate with an identification number acquisition device that acquires an identification number individually set for each ticket of the facility when entering and exiting a management area in the facility,
The control unit includes:
an identification number registration unit in which user information regarding the user of the identification number is registered in association with the identification number;
a detection unit that detects service information including at least one of services available to the user at the facility and services used by the user at the facility;
a notification unit that notifies a notification destination included in the user information of the service information when a notification condition based on the acquisition of the identification number by the identification number acquisition device is satisfied ;
The usage ticket is a transportation usage ticket that allows use of transportation facilities,
The identification number acquisition device is a ticket gate,
The control unit further includes a usage information acquisition unit that acquires usage information of the service used by the user,
The detection unit detects the usage information acquired by the usage information acquisition unit as the service information,
The service information is information regarding rental lockers, including the location where the rental lockers are installed and the date and time when they start being used.
Notification system. The notification unit may notify the user of entry to the management area at the first facility, start of use of the rental locker installed in the management area of the first facility, and management at a second facility different from the first facility. The notification system according to claim 7, wherein the notification conditions include that exit from the area and entry to the management area at the second facility are performed in order. The notification unit may be configured to initiate use of the rental locker installed outside the management area of the first facility, to enter the management area at the first facility, to enter the management area at the second facility different from the first facility. The notification system according to claim 7 or 8, wherein the notification conditions include that exit from the management area and entry to the management area at the second facility are performed in order. The notification unit may include exit from the management area at the first facility, start of use of the rental locker installed outside the management area of the first facility, entry into the management area at the first facility, The notification system according to any one of claims 7 to 9, wherein the notification condition includes that participation from the management area is made in order at a second facility different from the first facility. The notification unit may be configured to notify the start of use of the rental locker installed in the management area of the first facility, exit from the management area from the first facility, entry into the management area at the first facility, The notification system according to any one of claims 7 to 10, wherein the notification condition includes that participation from the management area is performed in order at a second facility different from the first facility. Entry to the management area at the first facility, start of use of the rental locker installed in the management area of the first facility, and exit from the management area at the first facility are permitted in order. The notification system according to any one of claims 7 to 11, further comprising a permission unit that allows a user to temporarily enter the management area as a condition.