Commuter pass management device, commuter pass management method, and commuter pass management program

Abstract

To ensure that infrequent railroad users can recognize the benefits of commuter passes and services for users can be improved.SOLUTION: A counting unit counts by day type the number of days of the commuter pass usage with a defined validity period and validity section. A storage unit stores a value table that sets the usage value of the commuter pass usage for each day type. A calculation unit calculates the total usage value of the commuter pass based on the number of days of use for each day type counted by the counting unit and the usage value for each day type set in the value table. A determination unit determines whether the commuter pass is valid or invalid according to the total usage value of the commuter pass calculated by the calculation unit.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a technique for limiting the period during which a commuter pass can be used. [Background technology]

[0002] Traditionally, railway companies sell commuter passes (hereinafter simply referred to as commuter passes) as a service to their users. As is well known, a commuter pass is a ticket with a set validity period and valid area, and can be used to travel on railways within the valid area any number of times during the validity period. Commuter passes are sold for a price determined according to the validity period and valid area. In other words, the more times a user uses a commuter pass, the more effective it is at reducing the costs (fares) associated with traveling by railway (the benefit of a commuter pass).

[0003] There was also a system that sought to improve service for users by extending the validity period of a commuter pass if it had not been used for a long period within its validity period, depending on the period of non-use (see Patent Document 1). [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2006-59289 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, with the promotion of teleworking in companies, many employees are now only going to work one or two days a week. Railway companies are finding it difficult to convince users who have reduced the number of days they go to work due to the use of telework that there is any benefit to purchasing a commuter pass.

[0006] For this reason, railway companies are looking to improve services for users by providing new services that will enable those who have reduced the number of days they go to work due to the use of telework to feel the benefits of commuter passes.

[0007] To provide a technique for improving services to users by making even those who use railways infrequently aware of the benefits of commuter passes. [Means for solving the problem]

[0008] In order to achieve the above object, the commuter ticket management device of the present invention is configured as follows.

[0009] The counting unit counts the number of days for which a commuter pass with a validity period and a validity section is used by day type. The day type referred to here may be, for example, a day of the week, a day of the week and a holiday, or other days.

[0010] The storage unit stores a value table in which the value of a commuter pass is set by day. The value table is, for example, a table in which the number of points, which is the value of a commuter pass, is set by day of the week, or by day of the week and holiday.

[0011] The calculation unit calculates the total usage value of the commuter pass based on the number of days of use by day type counted by the counting unit and the usage value by day type set in the value table. The total usage value of the commuter pass here is, for example, the total value (sum) of the usage value of the commuter pass for each usage day.

[0012] The determination unit determines whether the commuter pass is valid or invalid according to the total utilization value of the commuter pass calculated by the calculation unit. For example, the determination unit determines that the commuter pass is valid if the total utilization value of the commuter pass calculated by the calculation unit does not reach the upper limit value. In other words, the determination unit determines that the commuter pass is invalid if the total utilization value of the commuter pass calculated by the calculation unit reaches the upper limit value.

[0013] According to this configuration, whether a commuter pass is valid or invalid is determined according to the number of days of use counted by day type of the commuter pass. Therefore, for a user who uses the commuter pass only about 1-2 days a week, the period during which the commuter pass is determined to be valid (the period during which the commuter pass can be used) is longer than for a user who uses the commuter pass almost every day. This allows users who, for example, have reduced the number of days they go to work due to the use of telework, to feel the benefits of purchasing a commuter pass.

[0014] In addition, the value table is set with additional use values ​​for using a commuter pass on a predetermined day type and time period, The calculation unit may be configured to calculate the total utilization value of the commuter pass, including the additional utilization value.

[0015] For example, if the additional value is set for rush hour periods on weekdays (e.g., 7:00 a.m. to 10:00 a.m.), it will be possible to increase the number of users who refrain from using the service during rush hours. This will help to alleviate congestion during rush hours.

[0016] Also, there may be set days, such as Sundays and holidays, whose value is 0. This makes it easier for users to use their commuter passes when going out on holidays, and further improves user services. Effect of the Invention

[0017] According to this invention, even users who use railways infrequently can feel the benefits of commuter passes, thereby improving service to users. [Brief description of the drawings]

[0018] [Figure 1] FIG. 1 is a schematic diagram showing a ticket gate system of this example. [Diagram 2] FIG. 13 is a diagram showing a value table. [Diagram 3] 2 is a block diagram showing the configuration of a main part of a commuter pass management device. FIG. [Figure 4] 10 is a diagram showing usage history data stored in a usage history storage unit for a certain commuter pass. FIG. [Diagram 5] 2 is a block diagram showing the configuration of the main parts of an automatic ticket gate; [Figure 6] 4 is a flowchart showing the operation of an automatic ticket gate. [Figure 7] 4 is a flowchart showing the operation of the commuter pass management device. [Figure 8] FIG. 13 is a diagram showing a value table of the third modified example. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] Hereinafter, an embodiment of the present invention will be described.

[0020] <1. Application Examples> 1 is a schematic diagram showing the ticket gate system of this example. As shown in FIG. 1, the ticket gate system of this example has a commuter pass management device 1 and an automatic ticket gate 2.

[0021] The commuter pass management device 1 is installed at a center. For each commuter pass (hereinafter simply referred to as a commuter pass), the commuter pass management device 1 counts up the number of days (number of days of use) that a user has used the commuter pass at the ticket gate processing by day type. In this example, there are eight types of days: days of the week and holidays. A commuter pass is a passenger ticket with a set validity period and validity area. In this example, the commuter pass management device 1 may determine that a commuter pass is invalid according to the number of days of use counted by day type, even if the commuter pass is within its validity period. Whether a commuter pass is valid or invalid refers to whether the commuter pass can be used as a passenger ticket.

[0022] The day types may be seven types including only days of the week, eight types including days of the week and holidays, two types including weekdays (Monday to Friday) and Saturdays, Sundays and holidays, or other classifications other than those mentioned above.

[0023] As is well known, the automated ticket gates 2 are installed at the ticket gates of stations. The automated ticket gates 2 include an entrance automated ticket gate 2 that performs ticket screening for users entering the station premises, and an exit automated ticket gate 2 that performs ticket screening for users leaving the station premises.

[0024] The ticket gate system in this example has not only the automated ticket gates 2 installed at the ticket gates of the two stations, X Station and Y Station, shown in Fig. 1, but also automated ticket gates 2 installed at the ticket gates of other stations not shown. The automated ticket gates 2 installed at each station are configured to be able to perform data communication with the commuter pass management device 1 via a network 5.

[0025] In addition, the automatic ticket gate 2 and the commuter pass management device 1 may be configured to be able to communicate data directly via the network 5, or may be configured to be able to communicate data via one or more other devices (such as a station server installed at each station).

[0026] The automated ticket gate 2 accepts the ticket medium 3 held by the user and reads the ticket information recorded on the ticket medium 3. Based on the read ticket information, the automated ticket gate 2 determines whether or not the user is permitted to pass through the ticket gate passage.

[0027] Tickets that can be used in the ticket gate process at the automated ticket gate 2 include commuter passes, tickets, coupon tickets, and SF (Stored Fare) tickets. The ticket medium 3 may be an IC card, a mobile terminal such as a smartphone, or a medium on which a magnetic card or an optically readable code (for example, a two-dimensional barcode such as a QR code (registered trademark)) is printed. FIG. 1 only illustrates one user who owns the ticket medium 3, but does not mean that there is only one user who owns the ticket medium 3.

[0028] In this example, the ticket inspection process will be described for a user who owns a ticket medium 3 whose type of ticket is a commuter pass. Explanations of the ticket inspection process for users who own other types of tickets, such as tickets, coupon tickets, and SF tickets, will be omitted here.

[0029] In the ticket gate system of this example, when a user uses a commuter pass in a ticket gate process, an automatic ticket gate 2 notifies a commuter pass management device 1 of the identification number of the commuter pass.

[0030] The commuter pass management device 1 stores a value table in which the points for using a commuter pass are set by day type. For example, as shown in Fig. 2, the value table is a table in which the points for using a commuter pass are set by day type: Monday 2 points, Tuesday 1 point, Wednesday 1 point, Thursday 1 point, Friday 2 points, Saturday 0.5 points, Sunday 0 points, and public holiday 0 points. In this example, the value table is uniformly defined for commuter passes purchased by all users.

[0031] The value table may be one in which each user sets usage points by day according to the situation of his / her daily life. In this case, for example, the user may specify two types of days (weekdays) for which the usage points are two points. The value table shown in FIG. 2 is merely an example, and the distribution of usage points by day can be freely decided by the railway company.

[0032] As described above, the commuter pass management device 1 also counts the number of days that the commuter pass was used (number of days of use) by day for each commuter pass. In this counting, if the day that the commuter pass was used is a public holiday, the number of days of use on the public holiday is counted as 1 day, and the number of days of use for the corresponding day of the week is not counted as 1 day.

[0033] In addition, when counting the number of days of use by day type, no matter how many times a commuter pass is used on the same day, the number of days of use for the corresponding day type will be counted as one day. In other words, a day on which a commuter pass is used once and a day on which a commuter pass is used two or more times will both be counted as one day.

[0034] The commuter pass management device 1 calculates the product of the total number of days of use and the usage points for each day as the day-specific usage points. The commuter pass management device 1 calculates the sum of the day-specific usage points as the total usage points (corresponding to the total usage value in this invention). The commuter pass management device 1 determines that a commuter pass whose total usage points has reached a predetermined upper limit is invalid. In addition, a commuter pass is also determined to be invalid if it is outside its validity period.

[0035] In this way, in the ticket gate system of this example, whether a commuter pass is valid or invalid is determined based on the total usage points calculated according to the use of the commuter pass. For this reason, with the promotion of teleworking, etc., a user who commutes to work by train one or two days a week will have a longer period during which their commuter pass is determined to be valid (period during which the commuter pass can be used) than a user who uses the train almost every day. This allows, for example, a user who has reduced the number of days he or she commutes to work due to the use of teleworking to feel the benefits of purchasing a commuter pass. Therefore, even users who use trains infrequently can be made to feel the benefits of a commuter pass, improving service to users.

[0036] In addition, railway companies can decide the price at which they sell commuter passes based not only on the validity period and validity section, but also on the maximum points.

[0037] <2. Configuration example> FIG. 3 is a block diagram showing the configuration of the main part of the commuter pass management device of this example. 3 As shown in FIG. 1, the system includes a control unit 11, a communication unit 12, a usage history storage unit 13, and a value table storage unit 14.

[0038] The control unit 11 controls the operation of each part of the main body of the commuter pass management device 1. The control unit 11 also has a tallying unit 11a, a calculation unit 11b, and a judgment unit 11c. The tallying unit 11a, the calculation unit 11b, and the judgment unit 11c of the control unit 11 will be described later.

[0039] The communication unit 12 controls data communication with other devices such as the automated ticket gate 2 via the network 5. The communication unit 12 has a receiving section 12a and a transmitting section 12b.

[0040] The usage history storage unit 13 stores usage history data for each commuter pass that registers whether the commuter pass has been used. FIG. 4 is a diagram showing usage history data stored in the usage history storage unit for a certain commuter pass. As shown in FIG. 4, the usage history data is data that associates the commuter pass identification number, the maximum number of points for that commuter pass, and a value indicating whether the commuter pass was used or not for each day during the commuter pass's validity period. In FIG. 4, "1" indicates that the commuter pass has been used, and "0" indicates that the commuter pass has not been used.

[0041] For the usage history data, for days when it cannot be determined whether the commuter pass was used or not (today, when it is unused, and from tomorrow onwards), for example, "0" may be registered as shown in Fig. 4. The usage history storage unit 13 may be, for example, a hard disk drive (HDD), a solid state drive (SSD), or other storage medium.

[0042] The value table storage unit 14 stores the value table shown in Fig. 2. The value table storage unit 14 may use a part of the storage area of ​​the memory provided in the control unit 11, or may use a part of the storage area of ​​the usage history storage unit 13.

[0043] Next, the tallying unit 11a, the calculating unit 11b, and the determining unit 11c included in the control unit 11 will be described.

[0044] The tallying unit 11a refers to the usage history data and tallies the number of days that the commuter pass was used by day type.

[0045] The calculation unit 11b calculates the day-type usage points using the results of the calculation by the calculation unit 11a by day type and the value table stored in the value table storage unit 14. The day-type usage points are the product of the number of usage days calculated for that day type and the usage points for that day type. The calculation unit 11b also calculates the sum of the calculated day-type usage points as the total usage points.

[0046] The determination unit 11c determines whether a commuter pass is valid or invalid. If the total points used calculated by the calculation unit 11b have not reached the upper limit, the determination unit 11c determines the commuter pass to be valid. In other words, if the total points used calculated by the calculation unit 11b have reached the upper limit, the determination unit 11c determines the commuter pass to be invalid.

[0047] The control unit 11 of the commuter pass management device is composed of a hardware CPU, memory, and other electronic circuits. When the hardware CPU executes the commuter pass management program of the present invention, it operates as a tallying unit 11a, a calculation unit 11b, and a judgment unit 11c. The memory also has an area for expanding the commuter pass management program of the present invention and an area for temporarily storing data generated during execution of the commuter pass management program. The control unit 11 may be an LSI that integrates the hardware CPU, memory, and the like. The hardware CPU is also a computer that executes the commuter pass management method of the present invention.

[0048] 5 is a block diagram showing the configuration of the main parts of the automatic ticket gate 2. The automatic ticket gate 2 includes a control unit 21, a proximity wireless communication unit 22, a code reading unit 23, a user detection unit 24, a display unit 25, a door opening / closing unit 26, and a higher-level communication unit 27.

[0049] The control unit 21 controls the operation of each part of the main body of the automatic ticket gate 2. The control unit 21 also has a ticket gate processing section 21a. The ticket gate processing section 21a determines whether or not a user can pass through a ticket gate passage based on ticket information and the like.

[0050] The proximity wireless communication unit 22 receives ticket information through wireless communication with the ticket medium 3 held within its communication area. The communication area of ​​the proximity wireless communication unit 22 is provided on the ticket gate passage entrance side for users. In addition, when users pass through the ticket gate passage in both directions, the automatic ticket gate 2 provides the communication area of ​​the proximity wireless communication unit 22 not only on the ticket gate passage entrance side for users passing in one direction, but also on the ticket gate passage entrance side for users passing in the other direction.

[0051] The code reader 23 captures an image of the optically readable code held up against the imaging area. The code reader 23 processes the captured image of the optically readable code to obtain ticket information indicated by the optically readable code. The imaging area is provided on the ticket gate passage entrance side for the user. In addition, when the passage of users through the ticket gate passage is bidirectional, the imaging area is provided not only on the ticket gate passage entrance side for users passing in one direction, but also on the ticket gate passage entrance side for users passing in the other direction. The imaging area is provided inside the communication area of ​​the proximity wireless communication unit 22.

[0052] The user detection unit 24 has a plurality of photoelectric sensors arranged in the direction in which users pass through the ticket gate passage. The user detection unit 24 detects the position of a user passing through the ticket gate passage with the plurality of photoelectric sensors.

[0053] The display unit 25 displays a message to a user who has entered the ticket gate passage.

[0054] The door opening / closing unit 26 opens and closes the door located on the exit side of the user based on the result of the determination as to whether the user is permitted to pass through the ticket gate passage.

[0055] The higher-level communication unit 27 performs data communication with higher-level devices such as the commuter pass management device 1 and a station server (not shown).

[0056] Although the automated ticket gate 2 in this example does not have a configuration for processing magnetic tickets, of It may be provided.

[0057] The control unit 21 of the automated ticket gate 2 is composed of a hardware CPU, memory, and other electronic circuits. When the hardware CPU executes a ticket gate processing program, it operates as a ticket gate processing unit 21a. The memory also has an area for expanding the ticket gate processing program and an area for temporarily storing data generated during execution of the ticket gate processing program. The control unit 21 may be an LSI that integrates the hardware CPU, memory, and the like.

[0058] <3. Example of operation> Fig. 6 is a flow chart showing the operation of the automatic ticket gate.Fig. 7 is a flow chart showing the operation of the commuter pass management device.

[0059] The automated ticket gate 2 waits for the proximity wireless communication unit 22 or the code reading unit 23 to acquire ticket information (s1). The automated ticket gate 2 determines whether the ticket information acquired in s1 is related to a commuter pass or something else (a regular ticket, an SF ticket, etc.) (s2).

[0060] If the automatic ticket gate 2 determines that the ticket information does not apply to a commuter pass, it determines whether the currently acquired ticket information is correct (s10). The process in s10 is the same as that of a known automatic ticket gate, so a detailed description will be omitted here. If the automatic ticket gate 2 determines that the ticket information is correct in s10, it opens the door provided on the exit side of the ticket gate passage for the user (s8) and returns to s1. If the automatic ticket gate 2 determines that the ticket information is not correct in s10, it closes the door provided on the exit side of the ticket gate passage for the user (s9) and returns to s1. As is well known, the automatic ticket gate 2 allows the user to pass through the ticket gate passage by opening the door provided on the exit side of the ticket gate passage for the user. As is well known, the automatic ticket gate 2 prohibits the user from passing through the ticket gate passage by closing the door provided on the exit side of the ticket gate passage for the user.

[0061] If the automated ticket gate 2 determines in s2 that the currently acquired ticket information is for a commuter pass, it determines whether the commuter pass is being used within its validity period (s3). If the automated ticket gate 2 determines in s3 that the commuter pass is not being used within its validity period, it closes the door provided on the exit side of the ticket gate passage for the user in s9 and returns to s1.

[0062] If the automated ticket gate 2 determines in s3 that the ticket is within the valid period, it then determines whether the ticket is being used within the valid area (s4). If the automated ticket gate 2 determines in s4 that the ticket is not being used within the valid area, it closes the door provided on the exit side of the ticket gate passage for the user in s9 and returns to s1.

[0063] It should be noted that s3 and s4 may be performed in the reverse order to that described above.

[0064] Furthermore, if the automated ticket gate 2 determines in s4 that the use is within the valid area, it transmits a determination request to the commuter pass management device 1 (s5) and waits to receive the determination result from the commuter pass management device 1 (s6). The determination request transmitted in s5 includes the identification number of the commuter pass for which the ticket information was obtained this time.

[0065] When the commuter pass management device 1 receives a determination request from the automated ticket gate 2, it updates the usage history data (s21, s22). In s22, the value of the corresponding day (today) for the usage history data of the commuter pass identification code included in the currently received determination request is set to "1." At this time, if the value of the corresponding day is already "1," no update to the usage history data is actually performed.

[0066] The commuter pass management device 1 counts the number of days of use by day type in the counting unit 11a (s23). In s23, the counting unit 11a refers to the usage history data of the commuter pass identification code included in the currently received determination request, and counts the number of days of use by day type. In other words, the number of days with a value of "1" is counted for each day of the week and each public holiday.

[0067] The calculation unit 11b of the commuter pass management device 1 calculates the total usage points for the commuter pass with the commuter pass identification code included in the currently received determination request (s24). In s24, the calculation unit 11b calculates the usage points by day type. The usage points by day type are the product of the number of usage days for that day type and the usage points for that day type. The calculation unit 11b calculates the sum of the calculated usage points by day type as the total usage points.

[0068] The commuter pass management device 1 determines in the determination unit 11c whether the total usage points calculated in s24 have reached the upper limit points (s24). If the commuter pass management device 1 determines in s24 that the upper limit points have been reached, it replies that the commuter pass is invalid as the determination result of the currently received determination request (s25). On the other hand, if the commuter pass management device 1 determines in s24 that the upper limit points have not been reached, it replies that the commuter pass is valid as the determination result of the currently received determination request (s25).

[0069] When the automated ticket gate 2 receives the determination result from the commuter pass management device 1, if the received determination result is valid, it opens the door provided on the exit side of the ticket gate passage for the user (s7, s8) and returns to s1. On the other hand, if the determination result received from the commuter pass management device 1 is invalid, the automated ticket gate 2 closes the door provided on the exit side of the ticket gate passage for the user (s7, s9) and returns to s1.

[0070] In this way, in this example of the ticket gate system, the validity of a commuter pass is determined not only by the validity period of the commuter pass, but also by the total points calculated according to the use of the commuter pass. This allows even users who do not use trains often to feel the benefits of a commuter pass, improving service to users.

[0071] In addition, in this example, the points for use on Sundays and holidays are set to "0," so even if a user uses a commuter pass on a holiday, the points for use do not change. In other words, the ticket gate system in this example does not impair the user's advantage of using a commuter pass when going out on a holiday.

[0072] <4. Modifications> Variation 1 In the above example, the automatic ticket gate 2 is configured to determine at s3 and s4 whether the validity period and validity section of the used commuter pass are appropriate, but the commuter pass management device 1 may be configured to make the determinations at s3 and s4.

[0073] In addition, a configuration in which the automated ticket gate 2 determines whether the validity period and validity area of ​​the commuter pass used are appropriate reduces the frequency of communication between the commuter pass management device 1 and the automated ticket gate 2.

[0074] In addition, one of the determinations in s3 or s4 in the above example may be performed by the automated ticket gate 2, and the other may be performed by the commuter pass management device 1.

[0075] Variation 2 In the above example, the commuter pass management device 1 is configured to determine whether the commuter pass is valid or invalid, including the points used on the day (today) when the user uses the commuter pass. Day The validity or invalidity of a commuter pass may be determined without including the points used. Specifically, the counting unit 11a counts the number of days of use by day type based on the commuter pass usage history up to yesterday.

[0076] Variation 3 Also, as shown in FIG. 8, additional points may be set in the value table for the use of a commuter pass during rush hour on weekdays (7:00AM to 10:00AM). In this case, when a user uses a commuter pass during rush hour on a weekday, additional points are added to the usage points for that day. For example, if the pass is used during rush hour on Monday, the usage points will be 3 points. Also, if the pass is used during rush hour on Tuesday, the usage points will be 2 points. This allows users to refrain from using trains during rush hour, thereby easing congestion.

[0077] In this case, for days when the commuter pass is used during rush hour on weekdays for which additional points are set, the value associated with the usage history data shown in Fig. 4 can be set to "2". This allows the commuter pass management device 1 to manage whether the commuter pass was used during rush hour. Furthermore, the calculation unit 11b can reflect the additional points for use during rush hour in the calculation of the total usage points.

[0078] Variation 4 The automated ticket gate 2 may be configured to display the total points used for a commuter pass user who is permitted to pass through the ticket gate passage on the display unit 25. With this configuration, the user can check the total points used for the commuter pass when using the commuter pass. Therefore, the user can easily check how much time is left for which the commuter pass can be used.

[0079] Variation 5 The ticket gate system may be configured so that a user can operate a mobile terminal such as a smartphone to make a request to the commuter pass management device 1 to confirm the total points of the commuter passes that the user owns.

[0080] In this case, when the commuter pass management device 1 receives a confirmation request for the total points used from the user (mobile terminal), it returns the total points used calculated by performing the processes in s23 and s24 to the mobile terminal. The mobile terminal displays the total points used for the commuter pass returned from the commuter pass management device 1 on a display.

[0081] This allows users to check the total points earned on their commuter passes on their mobile devices.

[0082] Variation 6 In the above example, when the commuter pass management device 1 receives a determination request from the automated ticket gate 2, it calculates the total points used for the corresponding commuter pass and determines whether it is valid or invalid, but for commuter passes determined to be invalid, the determination result may be retained. If configured in this way, the commuter pass management device 1 will not repeatedly calculate the total points used for a commuter pass that has once been determined to be invalid. This makes it possible to reduce the processing load on the commuter pass management device 1.

[0083] Variation 7 Also, for a day type for which the usage points registered in the value table are "0", the commuter pass may be used within the validity period regardless of whether the total usage points have reached the upper limit points. In other words, the commuter pass management device 1 may be configured to determine that a commuter pass is valid for a day type for which the usage points registered in the value table are "0".

[0084] It should be noted that the present invention is not limited to the above-described embodiment as it is, and the components can be modified in the implementation stage without departing from the gist of the invention. In particular, the order of the operation processing procedures in each device is not limited to the above-described order, and the order may be changed as necessary. In addition, various inventions can be formed by appropriately combining multiple components disclosed in the above-described embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, components across different embodiments may be appropriately combined.

[0085] Furthermore, the correspondence between the configuration according to the present invention and the configuration according to the above-mentioned embodiment can be described as follows. <Additional Notes> a counting unit (11a) for counting the number of days for which a commuter pass having a specified validity period and validity section is used by day; A storage unit (14) that stores a value table in which the value of the commuter pass is set by day type; a calculation unit (11b) that calculates a total usage value of the commuter pass based on the number of usage days by day type counted by the counting unit (11a) and the usage value by day type set in the value table; A commuter pass management device (1) comprising: a judgment unit (11c) that judges whether the commuter pass is valid or invalid based on the total utilization value of the commuter pass calculated by the calculation unit (11b). [Explanation of symbols]

[0086] 1… Commuter pass management device 2. Automatic ticket gates 3…Ticket media 5. Network 11…Control unit 11a…Counting section 11b...Calculation section 11c...judgment section 12...Communication unit 12a…Receiver 12b...Transmitter 13...Usage history storage unit 14...Value table storage unit 21…Control unit 21a…Ticket gate processing section 22...Proximity wireless communication unit 23…Code reader 24...User detection unit 25...Display section 26…Door opening / closing section 27…Host communication unit

Claims

1. A counting unit that counts the number of days of use by day type by referring to the usage history of a commuter pass having a specified validity period and validity section; A storage unit that stores a value table that sets a value for use of the commuter pass by day; a calculation unit that calculates a total usage value of the commuter pass based on the number of usage days by day type counted by the counting unit and the usage value by day type set in the value table; A commuter pass management device comprising: a determination unit that determines whether the commuter pass is valid or invalid based on the total utilization value of the commuter pass calculated by the calculation unit.

2. A commuter pass management device as described in claim 1, wherein the usage value is the number of usage points.

3. A commuter pass management device as described in claim 1 or 2, wherein the calculation unit calculates the product of the number of days of usage and the usage value for each day as the daily usage value, and calculates the sum of the calculated daily usage values ​​as the total usage value.

4. A commuter pass management device as described in any one of claims 1 to 3, wherein the determination unit determines that the commuter pass is valid if the total utilization value of the commuter pass calculated by the calculation unit does not reach an upper limit value.

5. In the value table, an additional use value for using the commuter pass during a predetermined day type and time period is set, The commuter pass management device according to any one of claims 1 to 4, wherein the calculation unit calculates a total utilization value of the commuter pass, including the additional utilization value.

6. The commuter pass management device according to any one of claims 1 to 5, further comprising a day type for which the use value is 0.

7. A computer of a commuter pass management device that stores in a storage unit a value table that sets the utilization value for the use of a commuter pass having a specified validity period and validity section by day, a counting step of counting the number of days of use by day type, by referring to the usage history of the commuter pass; a calculation step of calculating a total usage value of the commuter pass based on the number of usage days by day counted in the counting step and the usage value by day set in the value table; A commuter pass management method which executes a determination step of determining whether the commuter pass is valid or invalid based on the total utilization value of the commuter pass calculated in the calculation step.

8. A computer of a commuter pass management device that stores in a memory unit a value table that sets the utilization value for the use of a commuter pass with a defined validity period and validity section by day, a counting step of counting the number of days of use by day type, by referring to the usage history of the commuter pass; a calculation step of calculating a total usage value of the commuter pass based on the number of usage days by day counted in the counting step and the usage value by day set in the value table; a determination step of determining whether the commuter pass is valid or invalid based on the total utilization value of the commuter pass calculated in the calculation step.

Images