JP7475958B2 - Server device, management system and program - Google Patents

Description

Embodiments of the present invention relate to a server device, a management system, and a program.

In recent years, thin client systems have become known that are configured to centralize the processing that is distributed among various terminals (client terminals) on the server device side. Specifically, thin client systems have a centralized system structure that limits the processing executed on the terminals actually used by users to the bare minimum, and has the server device execute most of the processing.

Here, we consider a case where such a thin client system is applied to a railway business (a business that operates trains). In this case, for example, an automatic ticket gate installed at a station acquires information stored on an IC card carried by a user, and the acquired information is transmitted from the automatic ticket gate to a server device. The server device determines whether or not to allow the user to pass (i.e., to allow the user to enter or exit the station) based on the information transmitted from the automatic ticket gate, and transmits the determination result to the automatic ticket gate. The automatic ticket gate performs an operation such as allowing the user to pass based on the determination result transmitted from the server device.

When a thin client system is applied to railway operations in this way, there is no need to install a mechanism in the automated ticket gate to determine whether or not to let a user through, which brings about benefits such as reduced maintenance costs for the automated ticket gate.

However, thin client systems have an issue when a communication failure occurs. Specifically, when a communication failure occurs between the server device and the automated ticket gate, the server device is unable to determine whether or not to allow the user to pass through, which becomes a factor that impedes convenience for the user.

On the other hand, if a communication failure occurs, it is conceivable that passengers could be allowed to pass through the automated ticket gates unconditionally. In such a case, however, it is conceivable that the railway operator would not be able to collect the fares that it should have received, which could result in a disadvantage to the railway operator.

JP 2017-107481 A

The problem that this invention aims to solve is to provide a server device, management system, and program that can maintain user convenience even when a communication failure occurs and prevent disadvantages to the operator.

According to an embodiment, a server device is provided that is installed at each of a plurality of stations and configured to be capable of acquiring first identification information assigned to a user who passes through the station, the first identification information being stored in an information recording medium carried by the user, and that is communicatively connected to an information terminal device used by the user. The server device includes a receiving means, a identifying means, and a notification processing means. The receiving means receives the first identification information acquired by the station equipment while a communication failure occurs between the station equipment and the station equipment, from the station equipment after the communication failure is restored. The identifying means identifies a user who passed through the station equipment while the communication failure occurs, based on the received first identification information. The notification processing means includes a notification processing means that transmits a notification regarding the occurrence of the communication failure to an information terminal device used by the identified user.

FIG. 1 is a diagram showing a network configuration of a management system according to an embodiment. FIG. 2 is a diagram illustrating an example of a hardware configuration of a server device. FIG. 2 is a diagram showing an example of a functional configuration of a server device. FIG. 4 is a diagram showing an example of a data structure of user information stored in a user information storage unit. FIG. 4 is a diagram showing an example of a data structure of ticket information stored in a ticket information storage unit. 10 is a sequence chart showing an example of a processing procedure executed in the management system when no communication failure occurs between the server device and the automated ticket gate. 11 is a sequence chart showing an example of a processing procedure executed in the management system when a communication failure occurs between the server device and the automated ticket gate. FIG. 4 is a diagram for specifically explaining the operation of the management system. FIG. 4 is a diagram for specifically explaining the operation of the management system. FIG. 4 is a diagram for specifically explaining the operation of the management system. FIG. 4 is a diagram for specifically explaining the operation of the management system. FIG. 4 is a diagram for specifically explaining the operation of the management system. FIG. 4 is a diagram for specifically explaining the operation of the management system. FIG. 4 is a diagram for specifically explaining the operation of the management system. 11 is a sequence chart showing an example of a processing procedure of the management system when executing a settlement process.

Hereinafter, an embodiment will be described with reference to the drawings.
1 shows a network configuration of a management system according to this embodiment. The management system according to this embodiment is used by, for example, a railway operator that operates trains (electric trains), and has a function of managing the purchase of passenger tickets by users who use the trains, and the entry or exit of the users to or from stations. Note that this embodiment assumes a case in which a user purchases a passenger ticket and a limited express ticket for a train such as a Shinkansen, for which the boarding section (boarding station and disembarking station) and boarding time are specified, but the following explanation will be given assuming that the user simply purchases a passenger ticket.

As shown in FIG. 1, the management system 1 includes an information terminal device 10, a server device 20, and an automated ticket gate 30. The information terminal device 10, the server device 20, and the automated ticket gate 30 are communicatively connected via a network 40.

The information terminal device 10 is a terminal device used by a pre-registered user, and includes, for example, a smartphone, a tablet terminal, a personal computer, etc. The user can purchase the above-mentioned ticket by operating the information terminal device 10.

For the sake of convenience, one information terminal device 10 is shown in FIG. 1, but if there are multiple pre-registered users, the management system 1 according to this embodiment may include multiple information terminal devices 10 used by each of the multiple users.

The server device 20 manages various information such as information about the user (hereinafter referred to as user information) and information about the ticket purchased by the user (hereinafter referred to as ticket information). Note that the server device 20 may operate as a server device that executes various cloud computing services, for example.

The automated ticket gates 30 are station service equipment installed at each of the stations where trains stop. That is, although only one automated ticket gate 30 is shown in FIG. 1 for the sake of convenience, the management system 1 includes multiple automated ticket gates 30.

The automated ticket gate 30 also has a gate (mechanism) that opens and closes, and by opening and closing this gate, it operates to allow only users who have purchased a ticket that can use the train to pass through. To achieve this operation, the automated ticket gate 30 is configured to be able to obtain identification information (identification information assigned to the user) held on an IC card 31 held by a user who passes through the automated ticket gate 30.

In this embodiment, the automated ticket gate 30 is described as acquiring the identification information from the IC card 31, but the IC card 31 may be a smartphone (information terminal device 10) that holds the identification information, or may be another information recording medium.

In addition, in this embodiment, the identification information stored in the IC card 31 includes, for example, a number capable of uniquely identifying the IC card 31 (hereinafter referred to as the IC card number), but may be other information (for example, a user ID, etc.) that can identify the IC card 31 (or the user who possesses it).

The management system 1 according to this embodiment is realized as a thin client system having a centralized system structure. In this case, the IC card number acquired at the automated ticket gate 30 as described above is transmitted from the automated ticket gate 30 to the server device 20, and the process of determining whether or not to allow the user to pass through the automated ticket gate 30 is executed by the server device 20.

Figure 2 shows an example of the hardware configuration of the server device 20 shown in Figure 1. The server device 20 includes a CPU 21, a non-volatile memory 22, a RAM 23, and a communication device 24. In the server device 20, the CPU 21, the non-volatile memory 22, the RAM 23, and the communication device 24 are connected to a bus 25 that interconnects them.

The CPU 21 is a processor for controlling the operation of each component in the server device 20. The CPU 21 may be a single processor or may be composed of multiple processors. The CPU 21 executes various programs loaded from the non-volatile memory 22 to the RAM 23. In this embodiment, the programs executed by the CPU 21 include a management program 23a for managing the purchase of tickets by users who use the above-mentioned trains and the entry or exit of such users to or from stations.

The non-volatile memory 22 is a storage medium used as an auxiliary storage device. The RAM 23 is a storage medium used as a main storage device. Although only the non-volatile memory 22 and the RAM 23 are shown in FIG. 2, the server device 20 may also include other storage devices, such as a hard disk drive (HDD) and a solid state drive (SSD).

The communication device 24 is a device configured to perform wireless communication with external devices (such as the information terminal device 10 and the automated ticket gate 30).

Figure 3 shows an example of the functional configuration of the server device 20. As shown in Figure 3, the server device 20 includes a user information storage unit 201, a ticket information storage unit 202, an information management unit 203, a matching processing unit 204, and a notification processing unit 205.

In this embodiment, the user information storage unit 201 and the ticket information storage unit 202 are realized by the non-volatile memory 22 shown in FIG. 2 or other storage device.

In addition, in this embodiment, some or all of the information management unit 203, the matching processing unit 204, and the notification processing unit 205 are realized by, for example, the CPU 21 (i.e., the computer of the server device 20) executing the management program 23a, that is, by software. This management program 23a may be distributed by being stored in a computer-readable storage medium, or may be downloaded to the server device 20 via the network 40.

Note that some or all of the above-mentioned units 203 to 205 may be realized by hardware such as an integrated circuit (IC), or may be realized by a combination of software and hardware.

The information management unit 203 is a functional unit for managing the above-mentioned user information and ticket information.

Specifically, the information management unit 203 receives from the information terminal device 10 information that is input by the user to the information terminal device 10 when the user registers with the management system 1, and generates user information based on the received information. The user information generated by the information management unit 203 in this manner is registered in the user information storage unit 201.

The information management unit 203 also receives from the information terminal device 10 information that is input by the user to the information terminal device 10 when the user purchases a ticket, and generates ticket information based on the received information. The ticket information generated by the information management unit 203 in this manner is registered in the ticket information storage unit 202.

When a change occurs in the user information stored in the user information storage unit 201 and the ticket information stored in the ticket information storage unit 202, the information management unit 203 may execute a process to change (update) the user information and the ticket information.

Here, in order for a user to use a train, the user must enter the station by passing through an automated ticket gate 30 installed at the station. In this case, the automated ticket gate 30 obtains the IC card number stored in the IC card 31 held by the user from the IC card 31. The IC card number thus obtained by the automated ticket gate 30 is transmitted from the automated ticket gate 30 to the server device 20.

The matching processor 204 receives the IC card number transmitted from the automated ticket gate 30. The matching processor 204 matches the received IC card number with the ticket information stored in the ticket information storage unit 202, and determines whether or not to allow the user holding the IC card 31 identified by the IC card number to pass through.

The result of the determination by the matching processing unit 204 is transmitted to the automated ticket gate 30, which then controls the opening and closing of the gate based on the result of the determination.

Here, in the above-mentioned management system 1 (thin client system), the server device 20 (matching processor 204) is configured to match the IC card number with the ticket information, but if a communication failure occurs between the server device 20 and the automated ticket gate 30, the server device 20 cannot receive the IC card number acquired by the automated ticket gate 30. In this case, the matching process in the matching processor 204 cannot be executed, and the automated ticket gate 30 (the gates provided at the automated ticket gate 30) cannot be controlled appropriately.

For this reason, in this embodiment, the matching process is not performed while a communication failure is occurring, and the user is allowed to pass through unconditionally.

However, in this case, passengers will be able to enter or exit stations outside the travel area specified in their pre-purchased ticket, which may result in the railway operator not collecting fares appropriately.

Here, if a communication failure occurs between the server device 20 and the automated ticket gate 30, the automated ticket gate 30 cannot transmit the IC card number to the server device 20, but the automated ticket gate 30 can still obtain the IC card number.

For this reason, the automated ticket gate 30 will hold the IC card number obtained from the IC card 31 held by the user who passed through the automated ticket gate 30 while a communication failure is occurring. This allows the automated ticket gate 30 to transmit the IC card number held in the automated ticket gate 30 to the server device 20 after the communication failure is restored.

In this case, the matching processing unit 204 receives the IC card number sent from the automated ticket gate 30 after the communication failure is restored, and performs matching processing using the IC card number. This allows the matching processing unit 204 to identify users who passed through the automated ticket gate 30 while the communication failure was occurring, based on the received IC card number.

The notification processing unit 205 sends a notification regarding the occurrence of a communication failure to the information terminal device 10 used by the user identified by the matching processing unit 204.

Figure 4 shows an example of the data structure of user information stored in the user information storage unit 201 shown in Figure 3.

As shown in FIG. 4, the user information includes information such as name, gender, telephone number, email address, credit card number, and IC card number, associated with the user ID.

As mentioned above, user information is information about a user, and the user ID included in the user information is identification information for identifying the user.

Name is the name of the user identified by the user ID. Gender is the gender of the user identified by the user ID.

The telephone number is the telephone number of the user identified by the user ID. The email address is the email address of the user identified by the user ID.

The credit card number is the number of the credit card held by the user identified by the user ID.

The IC card number is a number (identification information assigned to the IC card 31) used to identify the IC card 31 held by the user identified by the user ID.

In the example shown in FIG. 4, the user information storage unit 201 stores multiple pieces of user information including user information 201a and 201b.

The user information 201a includes the name "XXX", gender "male", telephone number "xxx-xxx-xxx", email address "xx@xx.co.jp", credit card number "credit card number 1", and IC card number "IC card number 1" in association with the user ID "001".

According to this user information 201a, the name of the user identified by the user ID "001" is XXX, the gender is male, the telephone number is xxx-xxxx-xxxx, and the email address is xx@xx.co.jp.

Furthermore, according to the user information 201a, it is shown that the number of the credit card held by the user identified by the user ID "001" is credit card number 1, and the number for identifying the IC card 31 held by the user is IC card number 1.

On the other hand, user information 201b includes the name "xxx", gender "female", telephone number "yyy-yyyy-yyyy", email address "yy@yy.co.jp", credit card number "-" and IC card number "IC card number 2" in association with user ID "002".

This user information 201b shows that the name of the user identified by the user ID "002" is XXX, the gender is female, the telephone number is yyy-yyy-yyyy, and the email address is yy@yy.co.jp.

Note that user information 201b indicates that the credit card number held by the user identified by user ID "001" is not registered. Thus, in this embodiment, the credit card number does not have to be registered (i.e., the user information does not have to include the credit card number).

Furthermore, according to the user information 201b, it is shown that the number for identifying the IC card 31 held by the user identified by the user ID "002" is IC card number 2.

Although only user information 201a and 201b have been described here, the user information storage unit 201 stores user information on all users who have been preregistered to purchase tickets, etc., using, for example, the information terminal device 10. Note that the data structure of user information other than user information 201a and 201b is the same as that of user information 201a and 201b.

In addition, in FIG. 4, the user information is described as including the user ID, name, gender, telephone number, email address, credit card number, and IC card number, but some of this information may be omitted from the user information, and other information may be included in addition to these.

Figure 5 shows an example of the data structure of ticket information stored in the ticket information storage unit 202 shown in Figure 3.

As shown in FIG. 5, the ticket information includes information such as the date, train ID, boarding station, disembarking station, departure time, and arrival time, associated with the IC card number.

As described above, the ticket information is information about a ticket purchased in advance by the user, and the IC card number included in the ticket information is a number for identifying the IC card 31 held by the user.

The date is the date on which the train specified in the ticket purchased by the user who holds the IC card 31 identified by the IC card number (i.e., the train for which the user has purchased a ticket) will operate.

The train ID is identification information used to identify the train specified in the ticket purchased by a user who holds an IC card 31 identified by an IC card number.

The boarding station is the boarding station specified in the ticket purchased by the user who holds the IC card 31 identified by the IC card number (i.e., the station where the user boards the train identified by the train ID). The disembarking station is the disembarking station specified in the ticket purchased by the user who holds the IC card 31 identified by the IC card number (i.e., the station where the user disembarks from the train identified by the train ID).

The departure time is the time when the train identified by the train ID departs from the boarding station. The arrival time is the time when the train identified by the train ID arrives at the disembarking station.

In the example shown in FIG. 5, the ticket information storage unit 202 stores multiple pieces of ticket information including ticket information 202a and 202b.

The ticket information 202a includes the date "2020/04/01", the train ID "01", the boarding station "Station A", the disembarking station "Station B", the departure time "12:30", and the arrival time "16:00" in association with the IC card number "IC card number 1".

This ticket information 202a shows that a user holding an IC card 31 identified by IC card number 1 has purchased a ticket for travel on a train identified by train ID "01" operating on April 1, 2020, from station A to station B.

The ticket information 202a also indicates that the train used by a user holding an IC card 31 identified by IC card number 1 (the train identified by train ID "01") departs from station A at 12:30 and arrives at station B at 16:00.

On the other hand, ticket information 202b includes the date "2020/04/02", train ID "02", boarding station "Station C", disembarking station "Station D", departure time "10:00", and arrival time "11:30" in association with IC card number "IC card number 3".

This ticket information 202b shows that a user holding IC card 31 identified by IC card number 3 has purchased a ticket for travel on the train identified by train ID "02" operating on April 2, 2020, from station C to station D.

Furthermore, according to the ticket information 202b, it is shown that the train used by the user holding the IC card 31 identified by the IC card number 3 (the train identified by the train ID "02") departs from Station C at 10:00 and arrives at Station D at 11:30.

Although only the passenger ticket information 202a and 202b has been described here, the passenger ticket information storage unit 202 stores passenger ticket information for all tickets purchased using the information terminal device 10. Note that the data structure of passenger ticket information other than the passenger ticket information 202a and 202b is the same as that of the passenger ticket information 202a and 202b.

In addition, in FIG. 5, the IC card number, date, train ID, boarding station, disembarking station, departure time, and arrival time are described as being included in the ticket information, but some of this information may be omitted from the ticket information, and other information may also be included.

Next, the operation of the management system 1 according to this embodiment will be described. Here, the operation of the management system 1 when a user (hereinafter referred to as the target user) purchases a train ticket and uses the train will be mainly described. Note that it is assumed that user information regarding the target user who purchases the train ticket is stored (registered) in advance in the user information storage unit 201.

First, referring to the sequence chart in FIG. 6, an example of a processing procedure executed in the management system 1 when no communication failure occurs between the server device 20 and the automated ticket gate 30 will be described.

When a target user purchases a train ticket, the target user operates the information terminal device 10 used by the target user to input information about the train for which the ticket is to be purchased into the information terminal device 10 (step S1). In step S1, for example, the user ID, date, train ID (train name), boarding station, and disembarking station are input.

When the processing of step S1 is executed, the train information entered in step S1 is transmitted from the information terminal device 10 to the server device 20 (step S2).

The information management unit 203 included in the server device 20 receives the train information transmitted from the information terminal device 10. The information management unit 203 generates ticket information based on the received train information, and stores the generated ticket information in the ticket information storage unit 202 (step S3).

The ticket information stored in the ticket information storage unit 202 includes the IC card number, date, train ID, boarding station, disembarking station, departure time, and arrival time, as described in FIG. 5 above. The IC card number included in the ticket information can be obtained from the user information stored in the user information storage unit 201 based on the user ID transmitted from the information terminal device 10. The departure time and arrival time can be obtained, for example, from timetable information, based on the date, train ID, boarding station, and disembarking station transmitted from the information terminal device 10. The timetable information may be managed in advance in the server device 20, or may be obtained from another external server device, etc. Furthermore, the departure time and arrival time may be obtained from an external server device, etc.

When using a train, the target user must pass through an automatic ticket gate 30 (hereinafter referred to as the first automatic ticket gate 30) to enter the station. In this case, the first automatic ticket gate 30 obtains the IC card number stored in the IC card 31 held by the target user (step S4).

In this embodiment, the IC card 31 held by the target user is, for example, a contactless IC card, and the first automated ticket gate 30 (including multiple automated ticket gates 30) is equipped with a reading device using contactless IC card technology. In this case, the first automated ticket gate 30 can obtain the IC card number from the IC card 31 held up (close to) the reading device of the first automated ticket gate 30 through communication based on contactless IC card technology. The IC card number may also be obtained using other proximity wireless communication or short-distance wireless communication.

The IC card number acquired in step S4 is transmitted from the first automated ticket gate 30 to the server device 20 as entry data together with, for example, identification information (hereinafter referred to as the ticket gate ID) for identifying the first automated ticket gate 30 that acquired the IC card number (step S5).

As mentioned above, the automated ticket gates 30 are installed at multiple stations, and the ticket gate ID is used to identify the station where the automated ticket gate 30 identified by the ticket gate ID is installed.

Here, it has been explained that the ticket gate ID is transmitted together with the IC card number, but it is sufficient if the server device 20 is able to identify the station in which the automated ticket gate 30 that obtained the IC card number is installed. For this reason, the automated ticket gate 30 may be configured to transmit a station ID or the like that identifies the station in which the automated ticket gate 30 is installed, instead of the ticket gate ID.

When the processing of step S5 is executed, the matching processing unit 204 included in the server device 20 receives the entrance data (IC card number and ticket gate ID) transmitted from the first automated ticket gate 30 in step S5, and executes a matching process using the entrance data (step S6).

In step S6, the matching processing unit 204 matches the received IC card number with the ticket information stored in the ticket information storage unit 202, and determines whether or not to allow the target user (the user who holds the IC card 31 identified by the IC card number) to pass through.

In this case, the matching processor 204 obtains the ticket information including the received IC card number from the ticket information storage unit 202. The matching processor 204 also identifies the station where the first automated ticket gate 30 (i.e., the automated ticket gate 30 that obtained the IC card number) is installed based on the received ticket gate ID. The station where this first automated ticket gate 30 is installed can be identified using ticket gate installation information that includes, for example, a station ID for identifying each of all stations and a ticket gate ID for identifying the automated ticket gate 30 installed at that station, in association with each other. This ticket gate installation information may be managed in advance in the server device 20, for example.

Next, the matching processing unit 204 matches the boarding station included in the ticket information obtained from the ticket information storage unit 202 with the station identified from the ticket gate ID as described above, and if the two stations match, it determines to allow the target user to pass.

On the other hand, if the boarding station included in the ticket information acquired from the ticket information storage unit 202 does not match the station identified from the ticket gate ID, the matching processing unit 204 determines that the target user will not be allowed to pass. The same applies if the ticket information including the IC card number received by the server device 20 does not exist in the ticket information storage unit 202.

The date included in the ticket information obtained from the ticket information storage unit 202 may be further compared with today's date (i.e., the date the IC card number was obtained by the automated ticket gate 30), and if the two dates match, it may be determined that the target user is to be allowed to pass.

The result of the matching process in step S6 described above (the result of the determination as to whether or not to allow the target user to pass) is transmitted from the server device 20 to the first automated ticket gate 30 (the automated ticket gate 30 that obtained the IC card number in step S4) (step S7).

The first automated ticket gate 30 controls the gate provided at the first automated ticket gate 30 based on the result of the matching process sent from the server device 20 in step S7 (step S8). Specifically, if the matching process determines that the target user should be allowed to pass, the first automated ticket gate 30 executes control to open the gate and allows the target user to pass.

On the other hand, if the matching process determines that the target user should not be allowed to pass, the first automated ticket gate 30 executes control to close the gate and does not allow the target user to pass. In this case, the first automated ticket gate 30, for example, prompts the target user to purchase an appropriate ticket.

The above-mentioned processing of steps S4 to S8 allows the target user to enter the station appropriately according to the ticket purchased in advance.

In addition, in step S6, even if the automated ticket gate 30 is installed at a station other than the boarding station specified in the ticket purchased in advance by the target user (i.e., the boarding station included in the ticket information obtained from the ticket information storage unit 202 does not match the station identified from the ticket gate ID), a matching process may be performed so that the target user can pass through (enter) the automated ticket gate 30, as long as it is installed at a station located within the section from the boarding station to the disembarking station specified in the ticket (i.e., the boarding section).

Here, we have explained the case where the target user enters a station, but the same processing as steps S4 to S8 is also performed when the target user leaves a station.

Specifically, the target user who has disembarked from the train must pass through an automated ticket gate 30 (hereinafter referred to as the second automated ticket gate 30) to exit the station. In this case, the second automated ticket gate 30 acquires the IC card number stored in the IC card 31 held by the target user (step S9). Note that the process of step S9 is the same as the process of step S4 described above, and therefore a detailed explanation of it will be omitted here.

The IC card number obtained in step S9 is transmitted from the second automated ticket gate 30 to the server device 20 as entry data together with a ticket gate ID for identifying the second automated ticket gate 30 that obtained the IC card number (step S10).

When the processing of step S10 is executed, the matching processing unit 204 included in the server device 20 receives the exit data (IC card number and ticket gate ID) transmitted from the second automated ticket gate 30 in step S10, and executes a matching process using the exit data (step S11).

The matching process executed in step S11 corresponds to the matching process executed in step S6, and the matching processor 204 matches the received IC card number with the ticket information stored in the ticket information storage unit 202, and determines whether or not to allow the target user (the user who holds the IC card 31 identified by the IC card number) to pass through.

In this case, the matching processor 204 obtains the ticket information, including the received IC card number, from the ticket information storage unit 202. The matching processor 204 also identifies the station where the second automated ticket gate 30 (i.e., the automated ticket gate 30 that obtained the IC card number) is located based on the received ticket gate ID.

Next, the matching processing unit 204 matches the disembarking station included in the ticket information obtained from the ticket information storage unit 202 with the station identified from the ticket gate ID described above, and if the two stations match, it determines to allow the target user to pass.

On the other hand, if the disembarking station included in the ticket information obtained from the ticket information storage unit 202 does not match the station identified from the ticket gate ID, the matching processing unit 204 determines that the target user should not be allowed to pass.

The result of the matching process in step S11 described above (the result of the determination as to whether or not to allow the target user to pass) is transmitted from the server device 20 to the second automated ticket gate 30 (the automated ticket gate 30 that obtained the IC card number in step S9) (step S12).

Based on the result of the matching process transmitted from the server device 20 in step S12, the second automated ticket gate 30 controls the gate provided in the second automated ticket gate 30 (step S13). Note that the process of step S13 is the same as the process of step S8 described above, and therefore a detailed description thereof will be omitted here.

The above-mentioned processing of steps S9 to S13 allows the target user to exit the station appropriately according to the ticket purchased in advance.

For example, if the target user attempts to pass the disembarking station specified in the pre-purchased ticket and exit from another station, the station at which the user attempts to exit will not match the disembarking station (the disembarking station included in the ticket information), and the target user will not be able to pass through the second automated ticket gate 30. In this case, the second automated ticket gate 30 executes control to close the gate as described above, and, for example, prompts the target user to settle the fare for passing the train. Settlement refers to the payment of additional fares (charges) for using a train outside the riding section specified in the ticket purchased by the target user.

In addition, in step S13, even if the automated ticket gate 30 is installed at a station other than the disembarking station specified in the ticket purchased in advance by the target user (i.e., the disembarking station included in the ticket information obtained from the ticket information storage unit 202 does not match the station identified from the ticket gate ID), a matching process may be performed so that the target user can pass through (exit) if the automated ticket gate 30 is installed at a station located within the section from the boarding station to the disembarking station specified in the ticket (i.e., the boarding section).

As described above, when no communication failure occurs between the server device 20 and the automated ticket gates 30 (first and second automated ticket gates 30), the server device 20 and the automated ticket gates 30 work in conjunction with each other, making it possible to appropriately control (manage) the entry and exit of target users.

Next, referring to the sequence chart in FIG. 7, an example of a processing procedure executed in the management system 1 when a communication failure occurs between the server device 20 and the automated ticket gate 30 will be described.

First, when a target user purchases a ticket, steps S21 to S23 are executed, which correspond to steps S1 to S3 shown in FIG. 6.

Here, when using a train, the target user needs to pass through the first automated ticket gate 30 to enter the station, but we will assume that a communication failure occurs between the server device 20 and the first automated ticket gate 30 at this point.

The first automated ticket gate 30 (including the multiple automated ticket gates 30) periodically sends inquiries, etc. to the server device 20, and if a response to the inquiry is not received from the server device 20 within a predetermined period of time, the first automated ticket gate 30 can detect that a communication failure has occurred with the server device 20. The communication failure may also be detected by other methods.

If a communication failure with the server device 20 is detected at the first automated ticket gate 30 as described above at the time the target user passes through the first automated ticket gate 30, the first automated ticket gate 30 acquires the IC card number stored in the IC card 31 held by the target user (step S24).

Due to the occurrence of the communication failure described above, the first automated ticket gate 30 is unable to transmit the IC card number acquired in step S24 to the server device 20 (i.e., the server device 20 is unable to execute the matching process). In this case, the first automated ticket gate 30 stores the IC card number acquired in step S24 inside the first automated ticket gate 30, for example, in association with the date and time when the IC card number was acquired, and executes control to open the gate (step S25).

In other words, in this embodiment, if a communication failure occurs at the time the target user enters the station, the first automated ticket gate 30 operates to allow the target user to pass unconditionally. This allows the target user to smoothly pass through the first automated ticket gate 30 and enter the station even if a communication failure occurs.

Here we have described the case where the target user enters the station, but if the communication failure has not been restored, the same processing as steps S24 and S25 is executed when the target user leaves the station.

Specifically, if a communication failure between the second automated ticket gate 30 and the server device 20 is detected at the second automated ticket gate 30 when the target user passes through the second automated ticket gate 30, the second automated ticket gate 30 acquires the IC card number stored in the IC card 31 held by the target user (step S26).

Here, due to a communication failure, the second automated ticket gate 30 is unable to transmit the IC card number acquired in step S26. In this case, the second automated ticket gate 30 associates the IC card number acquired in step S26 with the date and time when the IC card number was acquired and stores it inside the second automated ticket gate 30, and executes control to open the gate (step S27).

In other words, in this embodiment, if a communication failure occurs when the target user exits the station, the second automated ticket gate 30 operates to allow the target user to pass unconditionally, in the same way as in the case where the target user described above enters the station (i.e., the first automated ticket gate 30). This allows the target user to smoothly pass through the second automated ticket gate 30 and exit even if a communication failure occurs.

Although not illustrated in FIG. 6, each of the multiple automated ticket gates 30, including the first and second automated ticket gates 30, may be configured to internally retain the IC card number acquired when a user enters or exits a station, even when no communication failure occurs.

Here, assume that the communication failure is resolved after the processing of step S27 is executed (i.e., after the target user leaves the station).

In this case, the automated ticket gates 30 installed at each of the multiple stations transmit to the server device 20 the IC card numbers (i.e., IC card numbers for identifying IC cards 31 held by multiple users, including the target user who passed through the automated ticket gate 30 while the communication failure was occurring) stored internally in association with the date and time corresponding to the time period during which the communication failure occurred, together with a ticket gate ID for identifying the automated ticket gate 30.

Specifically, the first automated ticket gate 30 transmits the IC card number for identifying the IC card 31 held by the target user (the IC card number acquired in step S24) and the ticket gate ID for identifying the first automated ticket gate 30 as entry data to the server device 20 (step S28).

The second automated ticket gate 30 also transmits the IC card number for identifying the IC card 31 held by the target user (the IC card number acquired in step S26) and the ticket gate ID for identifying the second automated ticket gate 30 to the server device 20 as entry data (step S29).

When the processes of steps S28 and S29 are executed, the matching processing unit 204 included in the server device 20 receives the entrance data transmitted from the first automated ticket gate 30 in step S28 and the exit data transmitted from the second automated ticket gate 30 in step S29, and executes a matching process using the entrance data and the exit data (step S30).

In the matching process executed in step S30, the user (or the user ID for identifying the user) who passed through the automated ticket gate 30 while the above-mentioned communication failure was occurring is identified based on the IC card number contained in the entry data and exit data received by the matching processing unit 204.

Next, the notification processing unit 205 transmits a notification regarding the occurrence of the above-mentioned communication failure to the information terminal device 10 owned by the user identified by executing the processing of step S30 (step S31).

In this case, the notification processing unit 205 acquires user information including a user ID for identifying the user identified by executing the processing of step S30 from the user information storage unit 201, and sends a notification using the email address (or telephone number) included in the acquired user information.

The notification sent to the information terminal device 10 in step S31 includes, for example, a notification regarding the settlement of the fare for the train use. The necessity of settlement for the train use (whether settlement is necessary or not) is determined based on the ticket gate ID (i.e., the station where the first and second automatic ticket gates 30 that the target user passed through are installed) received together with the IC card number and the ticket information (including the boarding station and disembarking station) that includes the IC card number.

In addition, the content of the notification may vary depending on the timing of the occurrence or recovery of the communication failure, as will be described in more detail below.

When the processing of step S31 is executed, the information terminal device 10 displays the notification sent in step S31 (step S32).

According to the process shown in FIG. 7 above, even if a communication failure occurs, the user can smoothly pass through the automated ticket gate 30, and by sending the user a notification regarding the occurrence of the communication failure, the user can be prompted to settle the fare for the train ride (settlement for excess travel) if necessary.

Below, we will specifically explain the operation of the management system 1 when the above-mentioned communication failure occurs. Here, we will mainly explain the timing of the occurrence and recovery of the communication failure, and an overview of the notification sent to the information terminal device 10 according to that timing. In the following explanation, the station where the target user actually entered (boarded the train) when using the train will be called the entry station, and the station where the target user actually exited (disembarked from the train) will be called the exit station.

First, referring to Figure 8, we will explain a case where a communication failure occurs before the target user enters as described above in Figure 7, and the communication failure is restored after the target user exits. Note that in Figure 8, "entry" indicates the timing when the target user enters the entry station, and "exit" indicates the timing when the target user exits the exit station. The same applies to the following similar figures.

When the communication failure is restored, the matching processing unit 204 included in the server device 20 receives the entry data and exit data from each automated ticket gate 30 and executes a matching process. In this matching process, the entry station and exit station of the target user are identified based on, for example, the entry data and exit data (IC card number and ticket gate ID) received from the first and second automated ticket gates 30 (automated ticket gates 30 installed at the entry station and exit station). Specifically, the matching processing unit 204 acquires the entry data and exit data including, for example, an IC card number for identifying the IC card 31 held by the target user, and can identify the station identified based on the ticket gate ID included in the entry data and exit data as the entry station and exit station of the target user.

Next, the matching processing unit 204 obtains ticket information including an IC card number for identifying the IC card 31 held by the target user from the ticket information storage unit 202, and obtains the boarding station and disembarking station included in the ticket information (hereinafter referred to as the boarding station and disembarking station of the target user).

The matching processing unit 204 sends a notification to the information terminal device 10 used by the target user based on the entry station and exit station of the target user identified as described above and the boarding station and disembarking station of the target user obtained from the ticket information.

If the target user's entrance station is different from the boarding station or the target user's exit station is different from the disembarking station, it is determined that payment is required for the train use because the train is used in a section other than the section from the target user's boarding station to the disembarking station (i.e., the section from the boarding station to the disembarking station specified in the ticket purchased by the target user).

In this case, the notification processing unit 205 sends a notification to the information terminal device 10 used by the target user, including information that payment is required. This notification may include a guidance message such as, for example, "An automated ticket gate was used during a communication failure. Please make payment at the automated ticket machine or at the counter. If you do not make payment, you will not be able to use your IC card." Note that the guidance message described here is only an example, and the guidance message included in the notification may be, for example, one that urges payment via a client terminal (such as an automated ticket machine).

Furthermore, the notification may include the settlement amount. This settlement amount can be calculated based on the amount if the target user uses the train for the section from the entrance station to the exit station and the amount of the ticket purchased in advance by the target user (i.e., the amount if the target user uses the train for the section from the boarding station to the disembarking station). The settlement amount may be calculated within the server device 20 based on fare information or the like that specifies the amount for each section, or may be obtained from an external server device or the like.

Although the above description assumes that a notification is sent to the target user, if the target user's entrance station matches the boarding station and the target user's exit station matches the disembarking station (i.e., the section where the target user has used the train matches the section from the target user's boarding station to the disembarking station), then settlement is not required and the notification does not need to be sent. Also, if it is determined that settlement is not required because the section from the target user's entrance station to the exit station (i.e., the section where the target user has used the train) is included in the section from the target user's boarding station to the disembarking station, then the notification may not be sent.

In addition, even if the section from the target user's entrance station to the exit station is the same as the section from the target user's boarding station to the exit station (i.e., no fare adjustment is required), the target user (or the information terminal device 10 carried by the target user) may be notified that a communication failure occurred when the target user passed through the automated ticket gate 30 (i.e., entered and exited).

Next, referring to Figure 9, we will explain the case where a communication failure occurs before the target user enters and is restored before the target user exits.

When the communication failure is restored as described above, the server device 20 executes a matching process based on the entry data and exit data received from each automated ticket gate 30. In this matching process, for example, the entry station of the target user is identified based on the entry data (IC card number and ticket gate ID) received from the first automated ticket gate 30. Specifically, the matching processing unit 204 acquires entry data including, for example, an IC card number for identifying the IC card 31 held by the target user, and can identify the station identified based on the ticket gate ID included in the entry data as the entry station of the target user. Note that since the target user has not yet exited the station, the exit station of the target user cannot be identified at this point.

Next, the matching processing unit 204 obtains ticket information including an IC card number for identifying the IC card 31 held by the target user from the ticket information storage unit 202, and obtains the boarding station (the boarding station of the target user) included in the ticket information.

The matching processing unit 204 sends a notification to the information terminal device 10 used by the target user based on the entrance station of the target user identified as described above and the boarding station of the target user obtained from the ticket information.

If the target user's entrance station is different from the boarding station, the train is used in a section other than the section from the target user's boarding station to the disembarking station, and payment is required for the use of that train.

In this case, the notification processing unit 205 sends a notification to the information terminal device 10 used by the target user, including a notification that settlement is required.

On the other hand, if the target user's entrance station matches the boarding station, no notification will be sent. Even if the target user's entrance station does not match the boarding station, the notification may not be sent if it is determined that no fare adjustment is required, for example, if the entrance station is located within the section from the boarding station to the disembarking station.

As described above, if the target user's entrance station does not match the boarding station, a fare adjustment is required. The second automated ticket gate 30 can be configured to notify the target user that a fare adjustment is required when the target user exits the station. When adopting such a configuration, the system may be configured not to send a notification if the communication failure is restored before the target user exits the station, as shown in FIG. 9.

In addition, even if the boarding station of the target user is the same as the entrance station (i.e., no fare adjustment is required), the target user (or the information terminal device 10 carried by the target user) may be notified that a communication failure occurred when the target user passed through the automated ticket gate 30 (i.e., entered).

In this case, the server device 20 needs to perform a matching process for all users (entry data and exit data) who passed through the automated ticket gate 30 while the communication failure is occurring. Therefore, depending on the period during which the communication failure occurs, the amount of processing may become enormous, and it is expected that, for example, the process of determining whether or not settlement is necessary may take a long time.

Therefore, when the communication failure is restored, a notification regarding the occurrence of the communication failure may be sent first, and the verification process may be performed later. The notification in such a case may include a message such as, for example, "Because a communication failure occurred, we will confirm the use of the express ticket (passenger ticket) and collect the fare at a later date as necessary." In other words, in this embodiment, a notification may be sent including the possibility that payment for train use may be required.

If there is sufficient time before the target user leaves, it is preferable to perform the matching process as described above and then send the notification. Therefore, for example, as shown in FIG. 10, if the communication failure is restored more than M minutes (M is an integer equal to or greater than 1) before the target user's scheduled departure time, the server device 20 (matching processor 204 and notification processor 205) will operate as shown in FIG. 9 above. In FIG. 10, "Departure-M" indicates the time M minutes before the scheduled departure time. The same applies to the other figures.

On the other hand, if the communication failure is restored M minutes or more before the target user's scheduled departure time as shown in FIG. 11, the server device 20 operates to send a notification without performing the matching process as described above.

In other words, in this embodiment, the notification may be configured to send different notifications depending on whether the communication failure is restored before a predetermined time from the scheduled start time (M minutes before the scheduled start time) or after a predetermined time from the scheduled start time (i.e., the timing at which the communication failure is restored).

In this embodiment, the scheduled departure time can be the arrival time included in the ticket information stored in the ticket information storage unit 202, but the scheduled departure time can also be, for example, the arrival time plus a predetermined time (the time it is estimated that it will take for the target user to get off the train that arrives at the arrival time, pass through the automated ticket gate 30, and exit). That is, in this embodiment, the scheduled departure time can be a time calculated based on the arrival time.

In addition, in FIG. 5, the ticket information is described as including the arrival time (departure time), but if the ticket information does not include the arrival time, the scheduled departure time (arrival time) may be obtained, for example, from an external server device based on the train ID included in the ticket information.

Next, we will explain the case where a communication failure occurs after the target user enters. First, assume that a communication failure occurs after the target user enters as shown in Figure 12, and the communication failure is restored before the target user exits.

As described above, when the communication failure is restored, the server device 20 executes a matching process based on the entry data and exit data received from each automated ticket gate 30, but for the target user, no communication failure has occurred at the time of passing through the first automated ticket gate 30 installed at the entrance station, and the matching process has already been executed at the entrance station. In other words, if a communication failure occurs and is restored at the timing shown in Figure 12, the target user did not pass through the first automated ticket gate 30 while the communication failure was occurring, so no notification of the occurrence of the communication failure is sent to the target user (or to the information terminal device 10 used by the target user).

As described above, if a communication failure occurs before the target user enters, a notification with different content may be sent depending on when the communication failure is restored. However, if the target user enters without a communication failure, it is not necessary to send a notification even if the communication failure is restored M minutes or more before the target user's scheduled entry time, as shown in FIG. 13.

On the other hand, if the communication failure is restored after the target user has exited the train, as shown in Figure 14, a fare settlement may be required depending on the station where the target user exited the train.

When the communication failure is restored as described above, the server device 20 executes a matching process based on the entry data and exit data received from each automated ticket gate 30. In this matching process, the exit station of the target user is identified based on the exit data (IC card number and ticket gate ID) received from the second automated ticket gate 30.

Next, the matching processing unit 204 obtains the ticket information including the IC card number for identifying the IC card 31 held by the target user from the ticket information storage unit 202, and obtains the disembarking station (the disembarking station of the target user) included in the ticket information.

When the matching processing unit 204 determines that payment is required for train use based on the target user's exit station identified as described above and the target user's disembarking station obtained from the ticket information, it sends a notification to the information terminal device 10 used by the target user.

Note that the notification sent to the information terminal device 10 here is the same as the notification described above in FIG. 8, etc., so a detailed description of it will be omitted here.

As described above, in this embodiment, the IC card number (first identification information) acquired at the automated ticket gate 30 (station service equipment) while a communication failure occurs between the server device 20 and the automated ticket gate 30 is received from the automated ticket gate 30 after the communication failure is restored, and a user who passed through the automated ticket gate 30 while the communication failure occurred is identified based on the received IC card number, and a notification regarding the occurrence of the communication failure is sent to the information terminal device 10 used by the identified user.

In this embodiment, if a communication failure occurs between the server device 20 and the automated ticket gate 30, the automated ticket gate 30 operates to allow the user to pass when the IC card number is acquired.

In this embodiment, the above-mentioned configuration makes it possible to maintain convenience for users even when a communication failure occurs, and to prevent disadvantages to train operating companies.

Specifically, in this embodiment, a user who passed through the automated ticket gate 30 while a communication failure was occurring is identified based on the IC card number, and a notification is sent to the information terminal device 10 used by the identified user, including a notification that payment for train use is required.

The notification is sent when it is determined that payment is required for the user based on the station (entrance station and exit station) where the automated ticket gate 30 that obtained the IC card number is installed and the boarding station and disembarking station included in the ticket information in association with the IC card number.

In this embodiment, this configuration makes it possible to notify users who have passed through the automated ticket gate 30 while a communication failure is occurring that payment is required, thereby urging the users to pay and preventing them from suffering the inconvenience of not being able to collect the fare that should have been paid when they exited the station.

Furthermore, in this embodiment, a configuration may be adopted in which a user who entered through the automated ticket gate 30 while a communication failure was occurring is identified based on the IC card number, and who has not yet exited through the automated ticket gate 30 when the communication failure is restored, is identified, and a notification is sent to the information terminal device 10 used by the identified user, including information about the possibility that payment for train use may be required.

This notification is sent when the time when the communication failure is restored is before the scheduled departure time based on the arrival time of the train identified by the train ID (second identification information) included in the ticket information in association with the IC card number, and is within a predetermined time from the scheduled departure time.

In this embodiment, this configuration makes it possible to notify in advance that a communication failure has occurred and that settlement may occur, even at a point in time when it has not been determined whether settlement is necessary or not.

In addition, in this embodiment, the configuration may be such that notifications with different contents are sent depending on the timing at which the communication failure is restored. With such a configuration, it is possible to provide appropriate notifications for users' entry and exit depending on the timing at which the communication failure is restored.

In addition, in this embodiment, notifications are sent using the user's pre-registered email address (the email address included in the user information), so the user can easily check the contents of the notification. The notification may also be made available for the user to check via a message application program or the like running on the information terminal device 10.

Here, the payment for the train ride can be settled at an automatic ticket machine or at a counter, etc., but if the user's credit card number has been registered in advance (i.e., the user information relating to the user includes the credit card number), the settlement process (credit card payment process) may be performed using that credit card number. This settlement process may be performed in step S53 shown in FIG. 15, for example, in cooperation with a server device of a credit card company. Note that the processes of steps S41 to S52 shown in FIG. 15 are the same as the processes of steps S21 to S32 shown in FIG. 7. Also, the amount to be settled by the user in this settlement process is as described above, so a description thereof will be omitted here.

This configuration reduces the hassle for users who need to settle their fares, and allows the railway operator to reliably collect the fares that users should settle.

Note that in the process shown in FIG. 15, the notification sent from the server device 20 to the information terminal device 10 may include, for example, a message indicating that credit card payment processing will be performed at a later date.

Furthermore, as described above, if the user's credit card number is registered (i.e., if user information including the user's credit card number is stored in the user information storage unit 201), sending of the notification may be omitted. That is, in this embodiment, a notification may be sent to a user who does not have a registered credit card number, and a settlement process using the registered credit card number may be automatically executed for a user who has a registered credit card number.

The processing procedure shown in FIG. 15 is an example, and even if the timing of occurrence and recovery of a communication failure is different from that shown in FIG. 15, credit card payment processing can be executed if settlement is required. Furthermore, the settlement processing is not limited to credit card payment processing, and may be, for example, payment processing using electronic money, etc.

As described above, in this embodiment, even if the management system 1 that manages the purchase of train tickets by passengers and the entry or exit of such passengers into or out of stations is configured as a thin client system, it is possible to achieve smooth passage through the automated ticket gate 30 and reliable collection of fares (charges) regardless of the timing of the occurrence and recovery of communication failures.

Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the gist of the invention. These embodiments and their modifications are within the scope of the invention and its equivalents as set forth in the claims, as well as the scope and gist of the invention.

1...Management system, 10...Information terminal device, 20...Server device, 21...CPU, 22...Non-volatile memory, 23...RAM, 23a...Management program, 24...Communication device, 30...Automatic ticket gate (station service equipment), 31...IC card (information recording medium), 201...User information storage unit, 202...Ticket information storage unit, 203...Information management unit, 204...Matching processing unit, 205...Notification processing unit.

Claims (13)

A station service device is installed in each of a plurality of stations and configured to be capable of acquiring first identification information assigned to a user who passes through the station and stored in an information recording medium carried by the user. A server device is connected to an information terminal device used by the user so as to be capable of communicating therewith.
A receiving means for receiving, from the station service equipment after recovery from a communication failure, the first identification information acquired by the station service equipment while a communication failure occurs between the station service equipment and the station service equipment;
an identification means for identifying a user who passed through the station service equipment while the communication failure was occurring based on the received first identification information;
a notification processing means for transmitting a notification regarding the occurrence of the communication failure to an information terminal device used by the identified user. The identification means identifies a user who passed through the station service equipment and exited while the communication failure was occurring, based on the received first identification information,
The server device according to claim 1 , wherein the notification processing means transmits a notification including a notification that payment for train use is required to an information terminal device used by the identified user. further comprising a ticket information storage means for storing ticket information including the first identification information and train boarding stations and alighting stations that are specified for a ticket purchased in advance by a user to whom the first identification information is assigned, in association with each other;
The server device of claim 2, wherein the notification processing means sends the notification when it determines that payment is required for a user to whom the first identification information is assigned based on the station where the station service equipment that obtained the first identification information is installed and the boarding station and disembarking station included in the ticket information in correspondence with the first identification information. a user information storage means for storing user information including a user's credit card number in advance;
and a settlement processing means,
the notification processing means transmits the notification when user information including the credit card number of the identified user is not stored in the user information storage means;
4. The server device according to claim 3, wherein, when user information including a credit card number of the identified user is stored in the user information storage means, the settlement processing means executes the settlement processing using the credit card number. The server device according to claim 4, wherein the settlement processing means calculates the amount to be settled by the identified user based on the amount of the train fare for the section from a first station where a first station service device is installed and through which the identified user passed to enter to a second station where a second station service device different from the first station service device and through which the identified user passed to exit is installed, and the amount of the ticket purchased in advance by the user. The identification means identifies a user who has entered through the station equipment while the communication failure is occurring and has not exited through the station equipment when the communication failure is restored, based on the received first identification information;
The server device according to claim 1 , wherein the notification processing means transmits a notification including a notification that a charge for train use may be incurred to an information terminal device used by the identified user. further comprising a ticket information storage means for storing ticket information including the first identification information and a second identification information for identifying a train specified for a ticket purchased in advance by a user to whom the first identification information is assigned, in association with each other;
The server device of claim 6, wherein the notification processing means sends the notification when the time when the communication failure is restored is before the scheduled departure time based on the arrival time of a train identified by second identification information included in the ticket information in correspondence with first identification information for identifying the specified user, and is within a predetermined time from the scheduled departure time. The server device according to claim 1, wherein the content of the notification sent varies depending on the timing at which the communication failure is restored. the information recording medium includes an IC card,
The server device according to any one of claims 1 to 8, wherein the first identification information includes an IC card number assigned to the IC card. The server device according to any one of claims 1 to 9, wherein the notification is sent using the email address of the identified user. The server device according to any one of claims 1 to 10, wherein if a communication failure occurs with the station equipment, the station equipment operates to allow the user to pass when the first identification information is acquired. A management system including station service equipment installed at each of a plurality of stations and configured to be capable of acquiring first identification information assigned to a user who passes through the station and stored in an information recording medium carried by the user, and a server device communicably connected to the station service equipment,
The server device includes:
a receiving means for receiving, from the station service equipment after recovery from a communication failure, the first identification information acquired by the station service equipment during a communication failure between the station service equipment and the station service equipment;
an identification means for identifying a user who passed through the station service equipment while the communication failure was occurring based on the received first identification information;
a notification processing means for transmitting a notification regarding the occurrence of the communication failure to an information terminal device used by the identified user.
Management system. A program executed by a computer of a server device communicably connected to station service equipment installed at each of a plurality of stations and configured to be capable of acquiring first identification information assigned to a user who passes through the station and stored in an information recording medium carried by the user, and to an information terminal device used by the user, the program comprising:
The computer includes:
receiving, from the station service equipment after recovery from a communication failure, first identification information acquired by the station service equipment while a communication failure occurs between the station service equipment and the station service equipment;
identifying a user who passed through the station service equipment while the communication failure occurred based on the received first identification information;
and a step of transmitting a notification regarding the occurrence of the communication failure to an information terminal device used by the identified user.

Images